Repository navigation
air: include container environment variables in preflight validation - #7614
Draft
caroline-db wants to merge 2 commits into
Draft
caroline-db wants to merge 2 commits into
caroline-db wants to merge 2 commits into
Conversation
Collaborator
✅ Integration test reportCommit: ccd8d25
Top 3 slowest tests (at least 2 minutes):
|
This branch has not been deployed
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
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.
Changes
ValidateConfigrequest.Why
Container environment variables were omitted from preflight, allowing malformed names to fail only during process creation after a Jobs run and GPU workload existed. Sending the existing field lets AI Training reject them during
air run --dry-run.Tests
ai-compute-managerLiteSwap deployment.This PR was written with Codex.