chore: bump sdk to 0.8.1, release 0.7.1 - #2
Merged
Merged
Conversation
Picks up the SDK fix for the 202 the API returns when a job is known but its result is not readable yet. No source change here: the SDK's Backtest abstraction absorbs that distinction, so this repo never sees the raw response. The effect is still user-visible. A backtest driven through the MCP tools could report an empty result for a run that had actually completed; it now polls until the result is readable. Verified against the artifact published on JitPack, not a local build.
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.
Picks up the SDK fix for the
202the API returns when a job is known but its result is not readable yet.No source change here. The SDK's
Backtestabstraction absorbs the 202-vs-terminal distinction, so this repo never touches the raw response — confirmed by audit: nothing insrc/importsBacktestingApiorBacktestJobResult, and the only.state()call site reads the SDK's ownAtomicReference, which is never null.The effect is still user-visible: a backtest driven through the MCP tools could report an empty result for a run that had actually completed, and now polls until the result is readable.
Validation
mvn clean verifygreen (36 unit + 5 IT). The SDK dependency resolved from JitPack (sdk-java-0.8.1.jar>jitpack.io), not from a local install — so this verifies the published artifact end to end.