ENAMETOOLONG on long slug

[sukhcha-in]

I'm facing this issue when slug is too long, any way to fix this other than trimming slug?
What is the maximum limit for slug in this case?

Happening in production only, works fine in dev environment.

Failed to update prerender files for /en-IN/product/nakpro-perform-whey-protein-concentrate-24g-protein-5-7g-bcaa-4-7g-glutamine-helps-build-your-muscle-size-added-digestive-enzymes-easy-mixing-low-carbs-easy-digesting-fast-absorbing-raw-whey-protein-supplement-powder-for-men-women-athletes-1-kg-unflavoured-30-servings 
[Error: ENAMETOOLONG: name too long, open '/Users/sukh/Documents/Next/phnew/.next/server/pages/en-IN/product/nakpro-perform-whey-protein-concentrate-24g-protein-5-7g-bcaa-4-7g-glutamine-helps-build-your-muscle-size-added-digestive-enzymes-easy-mixing-low-carbs-easy-digesting-fast-absorbing-raw-whey-protein-supplement-powder-for-men-women-athletes-1-kg-unflavoured-30-servings.html'] 
{
  errno: -63,
  code: 'ENAMETOOLONG',
  syscall: 'open',
  path: '/Users/sukh/Documents/Next/phnew/.next/server/pages/en-IN/product/nakpro-perform-whey-protein-concentrate-24g-protein-5-7g-bcaa-4-7g-glutamine-helps-build-your-muscle-size-added-digestive-enzymes-easy-mixing-low-carbs-easy-digesting-fast-absorbing-raw-whey-protein-supplement-powder-for-men-women-athletes-1-kg-unflavoured-30-servings.html'
}

[icyJoseph]

Isn't this a Linux issue? I think in Linux file names can be up to 255 characters in size. What OS are you using locally?

[Crinchy]

Any update on this?

[icyJoseph]

Aha, this is a new take on this.

So someone requests route with these many characters, and that's causing it to error like this? Do the urls have .html extension? can you tell a bit more of the whole setup where this happens?

[Crinchy]

Heres a error log of this case:

Failed to update prerender cache for /🫲🙍🏼‍♀️👂🏻👩🏼‍💻💁🏿‍♀️😌🤑📩🍽🧑🏾‍🌾🧼👩🏻‍❤️‍💋‍👩🏻👨🏽‍🦽‍➡️🧓🏾🤹🏿🧑🏻‍❤️‍💋‍🧑🏾🧽🎾🧏🏽‍♂️🪼🪹👩🏿‍⚕️🧑🏿‍💻🪫🫷🏻.png Error: ENAMETOOLONG: name too long, open '/app/.next/server/app/🫲🙍🏼‍♀️👂🏻👩🏼‍💻💁🏿‍♀️😌🤑📩🍽🧑🏾‍🌾🧼👩🏻‍❤️‍💋‍👩🏻👨🏽‍🦽‍➡️🧓🏾🤹🏿🧑🏻‍❤️‍💋‍🧑🏾🧽🎾🧏🏽‍♂️🪼🪹👩🏿‍⚕️🧑🏿‍💻🪫🫷🏻.png.html'
at async open (node:internal/fs/promises:633:25)
at async Object.writeFile (node:internal/fs/promises:1207:14)
at async FileSystemCache.set (/app/node_modules/next/dist/server/lib/incremental-cache/file-system-cache.js:264:13)
at async IncrementalCache.set (/app/node_modules/next/dist/server/lib/incremental-cache/index.js:400:13)
at async /app/node_modules/next/dist/server/response-cache/index.js:121:25
at async /app/node_modules/next/dist/lib/batcher.js:45:32 {
errno: -36,
code: 'ENAMETOOLONG',
syscall: 'open',
path: '/app/.next/server/app/🫲🙍🏼‍♀️👂🏻👩🏼‍💻💁🏿‍♀️😌🤑📩🍽🧑🏾‍🌾🧼👩🏻‍❤️‍💋‍👩🏻👨🏽‍🦽‍➡️🧓🏾🤹🏿🧑🏻‍❤️‍💋‍🧑🏾🧽🎾🧏🏽‍♂️🪼🪹👩🏿‍⚕️🧑🏿‍💻🪫🫷🏻.png.html'
}

[Crinchy]

I have a dynamic route [slug] with ISR enabled and now, when you just hit the website with a long url, the application throws an error because through the linux limit, next.js cant write the file.

[icyJoseph]

Does the app crash upon this? What does the end user see? The dreaded 500 Internal Error page?

[Crinchy]

The end user is receiving a 404 not found, but in the background, the application is logging this error.