master fails testCompile: LineHttpSenderTokenProviderServerTest needs a client API the pinned java-questdb-client lacks
Since #7331 (chore(core): OIDC sign-in via device flow - OSS tandem, merged 2026-08-31) master does not compile its own tests against the java-questdb-client commit it pins.
Symptom
core/src/test/java/io/questdb/test/cutlass/http/line/LineHttpSenderTokenProviderServerTest.java:[79,24]
error: cannot find symbol
symbol: method httpTokenProvider(()->"ROTAT[...]Get())
location: class LineSenderBuilderSame error at line 122.
Cause
The test calls httpTokenProvider(Supplier), but the client commit master pins provides only httpToken(String):
git rev-parse origin/master:java-questdb-client |
0b9b5766c2c895321faa394c5ed31c0496e46e81 |
| that commit | feat(core): add OIDC sign-in via device flow (RFC 8628) (#52) |
javap io.questdb.client.Sender$LineSenderBuilder on a jar built from it |
public Sender$LineSenderBuilder httpToken(java.lang.String) — no httpTokenProvider |
Why CI is affected too
core/pom.xml declares <questdb.client.version>1.3.10-SNAPSHOT</questdb.client.version>, and ci/templates/detect-local-client.yml activates -P local-client for any -SNAPSHOT version, then builds the client from the submodule at that gitlink. So CI builds the very client the failure reproduces against, rather than resolving a newer one from Maven Central.
Reproduce
git checkout mastergit submodule update --init java-questdb-client- build and install the client module with the
local-clientprofile, skipping tests - run
test-compileon thecoremodule
Fix, one of
- Bump the
java-questdb-clientgitlink to a client commit that exposeshttpTokenProvider, or - hold the core-side test until the tandem client change lands.
Found while merging master into feat/covering-index-parquet (#7562); that merge is clean and every other gate passes (main sources compile, cargo fmt/clippy clean on all three crates), so this is not specific to that branch.
Source: questdb/questdb