[Bug] vercel部署失败

[davaded]

📦 Environment

Vercel

📌 Version

最新

💻 Operating System

Other

🌐 Browser

Chrome

🐛 Bug Description

✓ (serwist) Bundling the service worker script with the URL '/sw.js' and the scope '/'...
✓ Compiled successfully
Linting and checking validity of types ...
Collecting page data ...
node:buffer:1294
throw lazyDOMException(
^
InvalidCharacterError: The string to be decoded is not correctly encoded.
at atob (node:buffer:1294:13)
at u (/vercel/path0/.next/server/edge-chunks/17.js:1:25526)
at /vercel/path0/.next/server/edge-chunks/17.js:5:38344
at /vercel/path0/.next/server/edge-chunks/17.js:5:38393
at /vercel/path0/.next/server/edge-chunks/17.js:5:38664
at 9891 (/vercel/path0/.next/server/edge-chunks/17.js:5:38918)
at t (/vercel/path0/.next/server/edge-runtime-webpack.js:1:143)
at 7290 (/vercel/path0/.next/server/app/(backend)/trpc/edge/[trpc]/route.js:5:5757)
at t (/vercel/path0/.next/server/edge-runtime-webpack.js:1:143)
at t (/vercel/path0/.next/server/app/(backend)/trpc/edge/[trpc]/route.js:378:70492)

Build error occurred
Error: Failed to collect page data for /trpc/edge/[trpc]
at /vercel/path0/node_modules/next/dist/build/utils.js:1268:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
type: 'Error'
}
error: script "build" exited with code 1
Error: Command "bun run build" exited with 1

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

[lobehubbot]

👀 @davaded

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot]

Hello, @davaded! I'm here to assist you with any bugs or questions you have. If you need help, feel free to ask.

I found a similar issue related to Vercel deployment errors. In a closed issue, it was suggested to try redeploying, as builds sometimes fail initially but succeed upon retrying. The normal build process takes about 6 minutes, while failed builds take over 45 minutes ^[1].

The error you're encountering, "InvalidCharacterError: The string to be decoded is not correctly encoded," might be related to the atob function used in the urlSafeBase64Decode method of the StrCompressor class. This function decodes a base64-encoded string, and the error suggests that the string being decoded is not properly encoded ^[2].

To address this, you might want to check the encoding of the strings being passed to atob and ensure they are correctly base64-encoded. Additionally, reviewing recent changes to the edge-chunks/17.js file or the StrCompressor class might provide insights, although specific recent changes were not found in the available data.

To continue talking to Dosu, mention @dosu.

[davaded]

我自己处理吗？

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Do I handle it myself?