Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Katex: file name too long #1015

Closed
aneziac opened this issue Feb 23, 2025 · 1 comment
Closed

Katex: file name too long #1015

aneziac opened this issue Feb 23, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@aneziac
Copy link

aneziac commented Feb 23, 2025

Issue description

When trying to write a post with a simple Katex example, I got the following error.

It seems like the length of the hash exceeds the 255 character limit for paths in Linux. I found a couple posts about the same issue suggesting to change the hash function to SHA256 rather than SHA512 for example, but I'm unsure how to properly do this.

Theme version

v. 2.10.0

Hugo version

hugo v0.144.1-a79d63a44659b6bc76dcdf223de1637e0bd70ff6+extended linux/amd64 BuildDate=2025-02-18T12:14:07Z VendorInfo=snap:0.144.1

Which browser rendering engines are you seeing the problem on?

No response

URL to sample repository or website

No response

Hugo output or build error messages

❯ hugo server
Watching for changes in /home/nate/code/aneziac.github.io/{archetypes,assets,content,data,i18n,layouts,static}
Watching for config changes in /home/nate/code/aneziac.github.io/config/_default, /home/nate/code/aneziac.github.io/go.mod
Start building sites … 
hugo v0.144.1-a79d63a44659b6bc76dcdf223de1637e0bd70ff6+extended linux/amd64 BuildDate=2025-02-18T12:14:07Z VendorInfo=snap:0.144.1

Built in 53 ms
Error: error building site: open /home/nate/code/aneziac.github.io/public/lib/katex/auto-render.min.6095714e3aadb63b14ddc4af69346ab12974c1b460654345f8d1860a0b68fcc51b22f68b757433193090bb80afc8965b65cb607e5541d0f5f0f4b2e64d69b9ff.js: file name too long
@aneziac aneziac added the bug Something isn't working label Feb 23, 2025
@jpanther
Copy link
Owner

Thanks for raising this issue. It looks like I missed a couple of references to the fingerprinting algorithm in the vendor bundle. I'll fix this in the next release so that these correctly pick up on the fingerprintAlgorithm site parameter so you can pick the best algorithm for your deployment scenario.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants