Repository navigation
Upgrade dependencies and document llama.cpp 5.2.0 test failures - #210
Merged
Merged
Conversation
…10.3, palantir 2.99.0, NullAway 0.14.2, archunit 1.5.1
Cross-repo sweep of 2026-09-27, applied to all four Java repos together so the
tool-version matrix in workspace/crossrepostatus.md stays identical. CLAUDE.md's
dependency table follows.
Verified as far as this repo currently allows. The <llama.version>5.2.0</llama.version>
pin still does not resolve from Central (TODO.md), so the build was run against
java-llama.cpp main installed locally (-Dllama.version=5.2.0-SNAPSHOT):
- spotless:apply under palantir 2.99.0 changes no file in any of the three modules.
- srcmorph / srcmorph-cli / srcmorph-maven-plugin: 634 / 39 / 33 tests green.
- Two things stay red and are NOT caused by this change -- both reproduce on the
unmodified tree:
* 4 findsecbugs findings in LlamaCppJniProviderSupport (already in TODO.md);
* 4 failures in LlamaCppJniProviderSupportTest (buildInferenceParameters_*),
which read InferenceParameters.toString() as JSON. In the 5.2.0-SNAPSHOT core
toString() is a redacted debug view and toJson() is the request body, so those
assertions need to move to toJson() when the 5.2.0 pin is resolved.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QSXAwbXqx9u5xsMArMvgT8
bernardladenthin
had a problem deploying
to
maven-central
September 27, 2026 09:46 — with 
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
startgate
September 27, 2026 09:46 — with
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
September 27, 2026 09:46 — with
GitHub Actions
Failure
GitHub Actions
Failure
This branch had an error being 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
2 participants
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.
Summary
LlamaCppJniProviderSupportTestagainst llama.cpp 5.2.0 core, discovered 2026-09-27. The failures stem from assertions that callInferenceParameters.toString()expecting JSON, but in 5.2.0toString()is a redacted debug view; tests should calltoJson()instead.Test plan
Related issues / PRs
Refs the llama.cpp 5.2.0 core pin (documented in TODO.md as a blocking issue).
Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdhttps://claude.ai/code/session_01QSXAwbXqx9u5xsMArMvgT8