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

Gitpod starts with ruby 3.2.2, but bulletrain requires 3.3.0 #1427

Closed
PeterMonsson opened this issue Apr 9, 2024 · 3 comments · Fixed by #1481
Closed

Gitpod starts with ruby 3.2.2, but bulletrain requires 3.3.0 #1427

PeterMonsson opened this issue Apr 9, 2024 · 3 comments · Fixed by #1481

Comments

@PeterMonsson
Copy link
Contributor

Steps to reproduce:

  1. Click on gitpod icon on repo homepage
  2. Select default gitpod settings
  3. See errors in terminal
@PeterMonsson
Copy link
Contributor Author

Updating _ruby_version=ruby-3.3.0 in gitpod.Dockerfile seems to help, but I gitpod gets stuck during validation here:

=========================================================================================================================
[2024-04-09 19:31:04] ERROR 19:31:04: Could not load vsce-sign module Cannot find module '@vscode/vsce-sign'
[2024-04-09 19:31:04] ERROR Require stack:
[2024-04-09 19:31:04] ERROR - /ide/out/server-main.js
[2024-04-09 19:31:04] ERROR 19:31:04: Could not load vsce-sign module Cannot find module '@vscode/vsce-sign'
[2024-04-09 19:31:04] ERROR Require stack:
[2024-04-09 19:31:04] ERROR - /ide/out/server-main.js

@jagthedrummer
Copy link
Contributor

@PeterMonsson you could also try going the other direction and update your copy of BT to use the version of ruby that gitpod is trying to use. That's controlled by the .ruby-version file.

If you change that to 3.2.2 and then run bundle install that should get everything in agreement.

@jagthedrummer
Copy link
Contributor

@PeterMonsson, did you get this working? And if so, is there something that we should do on the BulletTrain side? (Basically I'm trying to figure out if there's anything to do, of if we can close this issue.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants