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

Hey @mamourgroupe-ctrl

When a Codespace hangs on initialization or hits a connection timeout, it almost always comes down to either a stuck container build step or a network/WebSocket block.

Here is a quick checklist to get you unstuck:

1. Check the Creation Logs

While the loading screen is spinning, look for a button or link near the bottom/middle that says "View Creation Log" (or click the gear icon if available).

• Why: If there's a broken script or infinite loop in the repository's .devcontainer/devcontainer.json (like a hanging postCreateCommand or npm install), the logs will show you exactly where it's stalling out.

2. Try a Full Container Rebuild

If you can access the command palette (or if you open the stuck Codespace from https://github.com/codespaces:

• Click the ... menu next to the stuck Codespace $\rightarrow$ Rebuild container.
• If you modified devcontainer configs recently, select Full Rebuild to flush any bad cached layers.

3. Check for Network / Firewall / VPN Blocks

Codespaces rely heavily on persistent WebSockets.

• Try opening the Codespace in an Incognito / Private Window with all browser extensions (especially ad-blockers or security suites) disabled.
• If you are on a corporate network, university Wi-Fi, or running a VPN, try toggling the VPN off. Restricted networks often block the port or protocol Codespaces uses to establish the web-socket connection.

4. Test with the Default Image

To figure out if the issue is with this specific repo or Codespaces in general:

1. Try launching a Codespace on a blank/simple public repo.
2. If another repo works, the issue is almost certainly a broken setup in this repo’s .devcontainer/ folder or a heavy Dockerfile taking longer than the default connection timeout.

5. Check Service Status

Head over to https://www.githubstatus.com/ and check the status of Codespaces. If the backend service is having issues in your region, creating and connecting to instances will time out until GitHub resolves the incident.

💡 Quick Workaround: If you have VS Code installed locally, try opening the Codespace directly inside VS Code Desktop via the GitHub Codespaces extension instead of the browser. It often handles connection retries much better than the web client.

If you can check the Creation Log and share any specific error lines where it gets stuck, that'll make it way easier to pin down!