You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@texera.apache.org by GitBox <gi...@apache.org> on 2026/06/06 23:07:00 UTC
[GH] (texera/fix/jwt-eager-401): Workflow run "Required Checks" is working again!
The GitHub Actions job "Required Checks" on texera.git/fix/jwt-eager-401 has succeeded.
Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run:
01c641ac4218e8ea86f2ede63bb4bc4b59ba3e80 / Yicong Huang <17...@users.noreply.github.com>
fix(auth): keep mapper spec in access-control-service to avoid namespace clash
Moving UnauthorizedExceptionMapperSpec into common/auth required adding
jersey-common 3.0.16 (jakarta namespace) as a test-scope dep to bring
in a RuntimeDelegate provider. That worked locally but broke amber's
HuggingFaceModelResourceSpec on CI: sbt's cross-module classloader
cache mixed the jakarta artifact added here with the javax.ws.rs-api
2.1.1 that amber/HuggingFaceModelResource pulls in (via its
`import javax.ws.rs._` — that file is the one outlier in the codebase),
which surfaced as `LinkageError: ClassCastException` on Response.status
inside amber's tests.
Revert to leaving the spec next to access-control-service, where
dropwizard-testing already provides a RuntimeDelegate. We lose
attribution of the mapper's coverage to Auth's jacoco report, but the
mapper is 50 lines with one method — a small follow-up if we ever care.
`Auth/jacoco` stays in the CI workflow so JwtAuthFilterSpec coverage is
reported.
HuggingFaceModelResource's `javax.ws.rs._` imports are a real bug worth
fixing separately, but doing it inside an auth PR is scope creep.
Report URL: https://github.com/apache/texera/actions/runs/27076180923
With regards,
GitHub Actions via GitBox