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

Dev Containers: Update onCreateCommand #6464

Merged
merged 1 commit into from
Jan 29, 2024
Merged

Dev Containers: Update onCreateCommand #6464

merged 1 commit into from
Jan 29, 2024

Conversation

benz0li
Copy link
Contributor

@benz0li benz0li commented Jan 29, 2024

  • Update the shell startup files from snippets
  • Separate the shell and stack configuration
  • Any changes that could be relevant to users have been recorded in ChangeLog.md.
  • The documentation has been updated, if necessary

No updates to ChangeLog.md and documentation required.

- Update the shell startup files from snippets
- Separate the shell and stack configuration
@mpilgrem mpilgrem merged commit 97e43fa into commercialhaskell:master Jan 29, 2024
12 checks passed
@mpilgrem
Copy link
Member

@benz0li, I merged that.

As an aside, the CI in recent days/weeks has been failing intermittently with:

Stderr:
Pulling image from registry: glcr.b-data.ch/ghc/ghc-musl:9.6.4.
Error response from daemon: Get "https://glcr.b-data.ch/v2/ghc/ghc-musl/manifests/sha256:7f79a0fdca1398c0cc35d0fb1290698430a3cfe26243719cab40189ed29cce60": dial tcp 51.154.68.67:443: i/o timeout
Error: [S-6092]
Could not pull Docker image:
    glcr.b-data.ch/ghc/ghc-musl:9.6.4
There may not be an image on the registry for your resolver's LTS version in
your configuration file.

My assumption is that is either a GitHub glitch or, perhaps, too much demand is being placed on glcr.b-data.ch and it is protesting. Do you have any insight?

@benz0li
Copy link
Contributor Author

benz0li commented Jan 29, 2024

My assumption is that is either a GitHub glitch or, perhaps, too much demand is being placed on glcr.b-data.ch and it is protesting. Do you have any insight?

@mpilgrem There is a rate limit in place. I just increased it.

Let us see if this improves the situation.

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 this pull request may close these issues.

2 participants