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

[Bug] Error since v1.45.0 #5352

Open
bentwnghk opened this issue Jan 8, 2025 · 2 comments
Open

[Bug] Error since v1.45.0 #5352

bentwnghk opened this issue Jan 8, 2025 · 2 comments
Labels
🐛 Bug Something isn't working | 缺陷

Comments

@bentwnghk
Copy link

📦 Environment

Docker

📌 Version

v1.45.0

💻 Operating System

Ubuntu

🌐 Browser

Chrome

🐛 Bug Description

Docker log:
`🌐 DNS Server: [ '127.0.0.11' ]


[Database] Start to migration...

✅ database migration pass.


▲ Next.js 15.1.4

✓ Starting...

✓ Ready in 45ms

{

allowDangerousEmailAccountLinking: true,

clientId: undefined,

clientSecret: undefined,

platformType: 'WebsiteApp',

profile: [Function: profile]

}

(node:28) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.

(Use node --trace-deprecation ... to show where the warning was created)

ReferenceError: Cannot access 'm' before initialization

at Object.y (.next/server/chunks/55646.js:212:19183)

at <unknown> (.next/server/chunks/55646.js:212:23459)

at <unknown> (.next/server/chunks/48159.js:159:1345)

at o (.next/server/chunks/48159.js:159:1740)

at s (.next/server/chunks/48159.js:159:1766)

at d (.next/server/chunks/48159.js:159:1943)

at <unknown> (.next/server/chunks/55646.js:212:23405)

at t.a (.next/server/webpack-runtime.js:1:989)

at 955225 (.next/server/chunks/55646.js:212:23158)

at t (.next/server/webpack-runtime.js:1:143)

⨯ unhandledRejection: ReferenceError: Cannot access 'm' before initialization

at Object.y (.next/server/chunks/55646.js:212:19183)

at <unknown> (.next/server/chunks/55646.js:212:23459)

at <unknown> (.next/server/chunks/48159.js:159:1345)

at o (.next/server/chunks/48159.js:159:1740)

at s (.next/server/chunks/48159.js:159:1766)

at d (.next/server/chunks/48159.js:159:1943)

at <unknown> (.next/server/chunks/55646.js:212:23405)

at t.a (.next/server/webpack-runtime.js:1:989)

at 955225 (.next/server/chunks/55646.js:212:23158)

at t (.next/server/webpack-runtime.js:1:143)`

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

@bentwnghk bentwnghk added the 🐛 Bug Something isn't working | 缺陷 label Jan 8, 2025
@github-project-automation github-project-automation bot moved this to Roadmap - Chat 1.x in Lobe Chat Routine Jan 8, 2025
@lobehubbot
Copy link
Member

👀 @bentwnghk

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。我们会尽快调查此事,并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

Copy link

dosubot bot commented Jan 8, 2025

The error message "ReferenceError: Cannot access 'm' before initialization" typically indicates that a variable is being used before it has been properly initialized. This can occur due to issues in the code where the variable is referenced before its declaration or assignment.

To address this issue, you can try the following steps:

  1. Check Variable Declarations: Review the code in the .next/server/chunks/55646.js file, particularly around the line mentioned in the error (line 212). Ensure that all variables are declared and initialized before they are used.

  2. Review Recent Changes: Since this error started occurring in version v1.45.0, examine the changes made in this version. Look for any modifications related to variable declarations or initializations that might have introduced this issue.

  3. Deprecation Warning: The log also mentions a deprecation warning for the punycode module. While this may not be directly related to the initialization error, it's advisable to replace deprecated modules with recommended alternatives to avoid future issues.

  4. Debugging: Use debugging tools or add console logs to trace the execution flow and identify where the variable is being accessed before initialization.

If the issue persists, you may need to look into the specific logic or functions involved in the affected code sections to ensure proper initialization order.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

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
Status: Roadmap - Chat 1.x
Development

No branches or pull requests

2 participants