Repository navigation
[publish] fix test fixtures, last_redefined RFC 1123 GMT in payload, APINotFound - #78
Merged
Merged
Conversation
Document get_free_clouds as the canonical free-cloud API: server-side semantics (no active assignment, future-scheduled clouds excluded via their active assignment, spare pool excluded via server config), the response contract including the last_redefined reservation-lock field, and APINotFound on servers older than 2.1 lacking /clouds/free/. Pin the contract in tests (full payload passthrough, 404 handling) and add a usage docs section with the reservation-lock hint recipe. Version bump to 0.1.18. fixes: #76
docs: make free-cloud detection canonical in get_free_clouds
Codecov Report✅ All modified and coverable lines are covered by tests.
🚀 New features to boost your workflow:
|
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.
0.1.9" claim was quads-client's dependency floor, not the introduction. Docstring says 0.1.0.
"pre-3.x" claims were caught by the refute team and corrected after independent verification against tags v2.0.5 (lacks) /
v2.1.0-v2.2.6 (has).
assignment-active detection; PR #194's client-side current+future fold reintroduces the exact logic that commit removed. The
terminate_assignment edge (future schedules surviving active=False) is a server-side gap, noted in the PR body as tracked in
quads.
returns only a version string), so the recipe documents it as client-side config.