一直显示这个

[soul6sss]

🏷️ Discussion Type

Bug

Body

[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. ⭐

[samus-aran]

Hi @soul6sss, thanks for participating!

Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting to ensure discussions are adhering to our Code of Conduct.

We’ll be locking this post for now, but please feel encouraged to create a new discussion in English if you still need support.

[JulyanXu]

Based on your screenshot (a Codespaces creation screen that is stuck loading), this is a common issue with several known causes. I have verified the most likely solutions:

Cause 1: Storage quota exceeded (most common)

GitHub Codespaces gives you:

• Free plan: 120 core-hours/month + 15 GB storage/month
• Pro plan: 180 core-hours/month + 20 GB storage/month

If your storage is full from old codespaces, new ones cannot be created.

Fix: Delete old codespaces:

# List all your codespaces
gh codespace list

# Delete codespaces you no longer need
gh codespace delete CODESPACE-NAME

# Or delete all stopped codespaces
gh codespace list --stop-status -q ".[].name" | xargs -I {} gh codespace delete {}

Or go to github.com/codespaces and manually delete old ones.

Cause 2: devcontainer.json configuration error

If your repo has a .devcontainer/devcontainer.json that references:

• An invalid or unavailable Docker image
• A broken postCreateCommand that hangs
• Features that fail to install

The codespace will get stuck during creation.

Fix:

1. Go to github.com/codespaces/new
2. Select your repo
3. Click the 3-dot menu > "View devcontainer.json"
4. Check for errors in the configuration

Or create a blank codespace with a minimal devcontainer:

{
  "image": "mcr.microsoft.com/devcontainers/base:ubuntu"
}

Cause 3: Browser cache or extension conflict

Fix:

1. Open Codespaces in an incognito/private window
2. Disable all browser extensions (especially ad blockers and VPNs)
3. Clear your browser cache for github.com
4. Try the VS Code Desktop option instead of the browser editor

Cause 4: Network restriction (China, corporate firewall)

If you are in China or behind a corporate firewall, Codespaces may fail to connect to the WebSocket that streams the VS Code server.

Fix:

# Use the GitHub CLI instead
gh codespace create -r YOUR-REPO
gh codespace ssh -c CODESPACE-NAME

# Or use port forwarding
gh codespace port-forward CODESPACE-NAME

Verify your billing status

Check your usage at github.com/settings/billing. If you see that your included usage is at 100%, you need to either:

• Delete old codespaces to free up storage
• Set a spending limit (for paid plans)
• Wait for the monthly reset

Nuclear option: Reset all codespaces

# Delete ALL your codespaces
gh codespace list -q ".[].name" | xargs -I {} gh codespace delete --force {}

Then try creating a new one.