Repository navigation
Pin bundled JacoDB startup and field-attribution fixes - #516
Merged
Merged
Conversation
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.
Pin JacoDB to the exact public commit
58c1928c2a0fae6a34632413e966d7105916a6c9, a clean linear combination of UnitTestBot/jacodb#438 and UnitTestBot/jacodb#439. Its bundled TypeScript frontend completes optional-chain branches with explicit unsupported boundaries and attributes real instance/static field stores to their PropertyDeclaration source spans.The independent JacoDB fixes pass 89 and 55 focused checks; all 15 new regressions also pass together on the combined source. Frontend generation succeeds on the nine untouched graphs that exposed unplaced labels, and the three original Sandstone graphs now retain checked source spans for their real field stores (3, 3, and 4 fields). Synthetic prologues/implicit returns stay unmapped. This MR changes only the dependency constant and requires no external frontend override.
Public dependency resolution is blocked by JitPack's build failure: Maven Central returned HTTP 429 for a Gradle hook plugin's
kotlin-stdlib-jdk8:1.8.22dependency, before frontend compilation began. Consequently the new public artifacts are not available yet.The clean exact combined JacoDB source was separately built and published into an isolated local Maven repository, without global repository/config changes. USVM
:usvm-ts:compileKotlinpasses against those ordinary artifacts. Thejacodb-etsjar SHA-256 isef131cbeebc99e229d37ea6780ed9a4eeeea2730427692a7048567e39d6f2e31; it embeds frontend SHA-2560c2792ec2df4c244cd6387e7e3e50f5b13ac1ffc35f3be4bc69cf3854745a712and 86 standard library files. Source tree, artifacts, recipe, and compile-log hashes are retained in the experiment receipt. NoETS_FRONTEND_DIRoverride was used. CI/public dependency availability remains outstanding.