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

add preliminary support for code spaces #46

Merged
merged 2 commits into from
Oct 16, 2024
Merged

add preliminary support for code spaces #46

merged 2 commits into from
Oct 16, 2024

Conversation

jac18281828
Copy link
Contributor

closes #45

This gets code spaces starting with an initial setup!

@jac18281828 jac18281828 added the enhancement New feature or request label Oct 15, 2024
@jac18281828 jac18281828 self-assigned this Oct 15, 2024
Copy link

vercel bot commented Oct 15, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
bonsol ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 15, 2024 10:47pm

@eureka-cpu
Copy link
Contributor

I seem to be getting this error when testing out the codespace:

This codespace is currently running in recovery mode due to a configuration error. Please review the creation logs, update your dev container configuration as needed, and run the "Rebuild Container" command to rectify.

Which prompts me to check the logs for an explanation, but doesn't seem there's any errors in the logs. Github codepsaces can be finicky, so this may just be a benign instance. I'll try again tomorrow with a fresh instance and report back.

@austbot austbot merged commit 1b93f2d into main Oct 16, 2024
5 checks passed
@austbot austbot deleted the jac/codespaces branch October 16, 2024 09:56
@jac18281828
Copy link
Contributor Author

I seem to be getting this error when testing out the codespace:

This codespace is currently running in recovery mode due to a configuration error. Please review the creation logs, update your dev container configuration as needed, and run the "Rebuild Container" command to rectify.

Which prompts me to check the logs for an explanation, but doesn't seem there's any errors in the logs. Github codepsaces can be finicky, so this may just be a benign instance. I'll try again tomorrow with a fresh instance and report back.

I was able to get it started. It took some time but I didn't see this. I was using the maximal hardware config. The build is resource intensive. Ping me when you get online and we can try to sort it out together!

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

Successfully merging this pull request may close these issues.

chore: setup GitHub codespaces
3 participants