The codespace is not available.

[icecream17]

🏷️ Discussion Type

Bug

Body

codespaces created on https://github.com/icecream17/set.mm tend to stop working, generally before I even perform a single command in the terminal. When I reload, it states "The codespace is not available."

I just tried again, and now it's failing to even start up:

screen-recorder-thu-sep-03-2026-09-20-08.webm

Things like this are happening across multiple devices and browsers.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[icecream17]

Workaround

First, increase startup available memory using the AI answer:

1. On the repo page, click the green Code button -> Codespaces tab.
2. Click the three dots ... and select New with options.
3. Change the machine type from 2-core (4 GB RAM) to 4-core (16 GB RAM).

Next, there seems to be garbage files.

@icecream17 ➜ /workspaces/set.mm (patch-1) $ git count-objects -vH
warning: garbage found: .git/objects/pack/tmp_pack_4QpNFI
warning: garbage found: .git/objects/pack/tmp_pack_acY1P7
count: 0
size: 0 bytes
in-pack: 110
packs: 1
size-pack: 24.54 MiB
prune-packable: 0
garbage: 2
size-garbage: 2.64 GiB

So deleting them should relieve enough memory for things to be workable
4. rm -f .git/objects/pack/tmp_pack_*

Edit: For some reason, the garbage keeps being created. You'll have to run step 4 constantly...

As for why the bug of massive garbage exists, I have no idea.

ChatGPT idea

ChatGPT has an idea to debug this, but it will have to wait until the next time I start it up or someone else tries: https://chatgpt.com/share/6ac3f18e-7f90-83ea-8008-d5d90b5b94ea