Fix devcontainer-utils-vault-s3-init for [email protected]#229
Merged
trxcllnt merged 3 commits intorapidsai:branch-24.04from Feb 9, 2024
Merged
Conversation
trxcllnt
added a commit
to trxcllnt/devcontainers
that referenced
this pull request
Feb 9, 2024
trxcllnt
added a commit
to trxcllnt/devcontainers
that referenced
this pull request
Feb 9, 2024
trxcllnt
added a commit
that referenced
this pull request
Feb 9, 2024
* Update to sccache v0.7.7 (#228) * Fix `devcontainer-utils-vault-s3-init` for `[email protected]` (#229)
trxcllnt
added a commit
that referenced
this pull request
Feb 9, 2024
* Update to sccache v0.7.7 (#228) * Fix `devcontainer-utils-vault-s3-init` for `[email protected]` (#229) * login to dockerhub so we don't hit rate limits (#224) * fix oneapi feature tests * fix bad merge
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[email protected]no longer blocks the client until the server is started, sosccache --show-statsdoesn't measure whether the server was able to successfully authenticate.[email protected]also doesn't seem to be able to access read-only buckets, so I've removed our fallback that detects this case and setsSCCACHE_NO_CREDENTIALS=1. Users will have to use the local cache if the bucket isn't read/write.