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] About vercel develop #1657

Closed
EzriLem opened this issue Mar 20, 2024 · 6 comments · Fixed by #1658
Closed

[Bug] About vercel develop #1657

EzriLem opened this issue Mar 20, 2024 · 6 comments · Fixed by #1658
Labels
🐛 Bug Something isn't working | 缺陷

Comments

@EzriLem
Copy link

EzriLem commented Mar 20, 2024

💻 Operating System

macOS

📦 Environment

Vercel / Zeabur / Sealos

🌐 Browser

Chrome

🐛 Bug Description

20:50:59.419 Running build in Washington, D.C., USA (East) – iad1
20:50:59.585 Cloning github.com/Azhizzz/lobe-chat (Branch: main, Commit: 5efb0b4)
20:51:00.016 Previous build cache not available
20:51:00.205 Cloning completed: 619.903ms
20:51:00.680 Running "vercel build"
20:51:01.191 Vercel CLI 33.6.1
20:51:01.695 Running "install" command: npx bun@1.0.31 install...
20:51:06.960 npm WARN exec The following package was not found and will be installed: bun@1.0.31
20:51:09.661 bun install v1.0.31 (e2567512)
20:51:09.664 Resolving dependencies
20:51:24.235 Resolved, downloaded and extracted [8910]
20:51:24.236 warn: incorrect peer dependency "stylelint@15.11.0"
20:51:24.236  
20:51:24.236 warn: incorrect peer dependency "stylelint@15.11.0"
20:51:24.237  
20:51:24.237 warn: incorrect peer dependency "stylelint@15.11.0"
20:51:24.237  
20:51:24.237 warn: incorrect peer dependency "stylelint@15.11.0"
20:51:24.237  
20:51:24.237 warn: incorrect peer dependency "@octokit/core@5.1.0"
20:51:24.238  
20:51:24.238 warn: incorrect peer dependency "@octokit/core@5.1.0"
20:51:24.238  
20:51:24.238 warn: incorrect peer dependency "stylelint@15.11.0"
20:51:24.238  
20:51:24.238 warn: incorrect peer dependency "stylelint@15.11.0"
20:51:24.238  
20:51:24.239 warn: incorrect peer dependency "@octokit/core@5.1.0"
20:51:24.239  
20:51:24.239 warn: incorrect peer dependency "@octokit/core@5.1.0"

It's been stuck in this process for 10 or 20 minutes with no change to go forward

🚦 Expected Behavior

Successful deployment

📷 Recurrence Steps

No response

📝 Additional Information

No response

@EzriLem EzriLem added the 🐛 Bug Something isn't working | 缺陷 label Mar 20, 2024
@lobehubbot
Copy link
Member

👀 @Azhizzz

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

@lirtual
Copy link

lirtual commented Mar 20, 2024

#1654 I have encountered the same issue as well. The new fix doesn't seem to have resolved the deployment problem. During deployment, the progress has been stuck at "warn: incorrect peer dependency "@octokit/core@5.1.0".

@arvinxx
Copy link
Contributor

arvinxx commented Mar 20, 2024

Ok, actually there is another problem with bun@1.0.31 , so i guess need to downgrade to 1.0.30 again😨

@EzriLem
Copy link
Author

EzriLem commented Mar 20, 2024

#1654 I have encountered the same issue as well. The new fix doesn't seem to have resolved the deployment problem. During deployment, the progress has been stuck at "warn: incorrect peer dependency "@octokit/core@5.1.0".#1654 我也遇到了同样的问题。新的修复程序似乎没有解决部署问题。在部署期间,进度一直停留在“警告:不正确的对等依赖项”@octokit/core@5.1.0”。

Yes, I deployed for 54 minutes with a hint at the end: Your deployment's build step did not complete within the maximum of 45min

@lobehubbot
Copy link
Member

✅ @Azhizzz

This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题,可以留言并回复。

@sadokx
Copy link

sadokx commented Apr 25, 2024

This happened to me just now, how to fix it?

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
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants