chore: release 0.8.1 - #4
Merged
Merged
Conversation
Ships the execute-poll fix for the 202 the API returns when a job is known but its result is not readable yet. api-client-java stays at 0.6.0: the generated signature does not move, because openapi-generator takes the 200 type and ignores the 202 schema, and at runtime any 2xx is a success. A 202 therefore arrives as a BacktestJobResult with a null state, which is exactly what the fix in this release handles. Verified against the live API serving that spec: full verify green, live integration included.
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.
Ships the execute-poll fix for the
202the API returns when a job is known but its result is not readable yet.Why api-client-java stays at 0.6.0
The generated signature does not move: openapi-generator takes the 200 type and ignores the 202 schema, and at runtime any 2xx is a success (
statusCode()/100 != 2is the error test). A 202 therefore arrives as aBacktestJobResultwith a nullstate— exactly the case the fix in this release handles. No client release was needed.Validation
mvn clean verifygreen (49 tests), including the live integration test run against the API serving spec 0.99.2.