Pull Request Dashboard

[github-actions]

Note

Open PRs are grouped by deterministic routing over per-thread LLM classifications. CI, conflicts, and activity age are computed deterministically and are shown as facts, not used as standalone routing reasons.

Waiting on maintainer (approved)

PR	Author	CI	Conflicts	Activity
Remove all shared internal code refs from zipkin exporter	jack-berg	✅	✅	5d

Waiting on approvers

PR	Author	CI	Conflicts	Activity
Update weekly update	app/renovate	✅	✅	?
Update all patch and minor versions	app/renovate	✅	✅	?
Bound OkHttp sender dispatchers and surface rejections	ADITYA-CODE-SOURCE	✅	✅	3d
Update dependency org.mock-server:mockserver-netty to v6	app/renovate	❌	✅	?
Fix Groovy OpenTelemetrySdk builder loading	ADITYA-CODE-SOURCE	✅	✅	7d
Limit exemplar label characters to conform to Prometheus limits	anuq	✅	✅	2d
profiles: improve JFR export example	jhalliday	✅	✅	6d
Make snakeyaml-engine and jackson-databind optional at runtime	zeitlinger	✅	❌	34d
Use setup-gradle w/ cache-provider: basic to use more permissive MIT …	jack-berg	✅	❌	49d
Add fallback endpoint support for OTLP exporters	sridharsurvi1	❌	❌	40d
Add a ConfigProvider callback for runtime instrumentation option changes	jackshirazi	❌	❌	19d
Make StandardComponentId constructor public	brunobat	✅	❌	208d

Waiting on authors

PR	Author	CI	Conflicts	Activity
Finish adding OSGi support	jack-berg	✅	✅	2d
Commit declarative config schema pojos to git	jack-berg	❌	✅	11d
Merge colliding Prometheus label values	ADITYA-CODE-SOURCE	✅	✅	11d
Update dependency java to v26	trask	✅	✅	47d
Replace ArrayBlockingQueue with park/unpark for BatchSpanProcessor$Worker	Khepu	✅	✅	32d
Add JSON pretty-print to logging-otlp exporters	lucacavenaghi97	✅	✅	6d
[DO NOT MERGE] JFR API usage	jhalliday	❌	✅	53d
Limit prometheus exemplar labels	harshitrjpt	✅	❌	16d

Waiting on external

PR	Author	CI	Conflicts	Activity
Update junit-framework monorepo - abandoned	app/renovate	❌	❌	18d
Update dependency java to v26	app/renovate	❌	✅	34d

Diagnostics

PR #8424
facts: approved=False conflicts=no days_since_last_activity=None
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver

PR #8423
facts: approved=False conflicts=no days_since_last_activity=None
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver

PR #8422
facts: approved=False conflicts=no days_since_last_activity=3
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver

PR #8418
facts: approved=False conflicts=no days_since_last_activity=None
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver

PR #8417
facts: approved=False conflicts=no days_since_last_activity=2
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The latest comment asks the PR author for release timing and whether they plan follow-up PRs in related repos, so the thread is waiting on jack-berg to respond.)
route: author

PR #8413
facts: approved=True conflicts=no days_since_last_activity=5
threads: author=0 reviewer=0 external=0 none=2 unclear=0
llm: PRRT_kwDOCkv3g86C7dSe -> none (The author is just explaining a test’s purpose; there’s no explicit request, question, or required follow-up in the thread.)
llm: PRRT_kwDOCkv3g86Dgb4W -> none (The author’s comment is just an FYI to another team with a search link; it does not ask for a response or request a concrete change in this thread.)
route: maintainer

PR #8408
facts: approved=False conflicts=no days_since_last_activity=11
threads: author=3 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86CKKVv -> reviewer (The author is pointing reviewers to the relevant build.gradle.kts changes and asking them to review that file, so the next step is with a reviewer.)
llm: PRRT_kwDOCkv3g86CKMLE -> reviewer (The author has already responded with an explanation for the suppressed boxed-primitive comparison, so the ball is back in the reviewer’s court to accept that explanation or raise another concern.)
llm: PRRT_kwDOCkv3g86CKN7v -> author (The only comment is from the PR author, and it says they want to investigate whether to change the constructor behavior, so the next step is on the author to decide and implement any change.)
llm: PRRT_kwDOCkv3g86CKPJM -> author (The only comment is from the PR author and identifies a possible follow-up change (“Should investigate whether we can configure to name the set* instead”), so the thread is still on the author to investigate or adjust the code.)
llm: PRRT_kwDOCkv3g86CKPwd -> author (The author’s latest comment says the `toString` implementation should be revisited for configurability and consistency, which implies follow-up work is still on the author to make.)
route: author

PR #8407
facts: approved=False conflicts=no days_since_last_activity=7
threads: author=0 reviewer=1 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g86CMfQS -> reviewer (The reviewer asked for justification comments, and the author says they added them in a follow-up commit, so the ball is back with the reviewer to inspect the change.)
llm: PRRT_kwDOCkv3g86CMnfF -> none (The author answered the question directly and no further follow-up or change was requested in the thread.)
route: approver

PR #8377
facts: approved=False conflicts=yes days_since_last_activity=18
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: PRRT_kwDOCkv3g86Ab-gj -> external (The reviewer says to wait for the real 7.3.0 release before merging, so this thread is blocked on an external upstream release rather than work in this repo.)
route: external

PR #8364
facts: approved=False conflicts=no days_since_last_activity=11
threads: author=3 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86BhQsA -> author (The latest review comment asks for a code change to reduce allocation overhead, so the PR author needs to update the test/implementation.)
llm: PRRT_kwDOCkv3g86BhVsZ -> author (The approver flagged a likely gap in the implementation: collisions from `resource`, `scope`, and `additionalAttributes` also need to be considered, so the PR author needs to update the code.)
llm: pr-conversation -> author (The author said they will rebase, apply the requested changes, and re-request review once the blocking issue settles, so the next step is on the author.)
route: author

PR #8362
facts: approved=False conflicts=no days_since_last_activity=2
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver

PR #8349
facts: approved=False conflicts=no days_since_last_activity=6
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver

PR #8270
facts: approved=False conflicts=yes days_since_last_activity=34
threads: author=0 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g857PtCt -> none (The reviewer answered the design question and the author acknowledged deferring this work to a follow-up, so no one needs to act further on this thread right now.)
route: approver

PR #8261
facts: approved=True conflicts=no days_since_last_activity=47
threads: author=1 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g855XQ2Y -> none (The author asked an informational question about using Zulu, and the approver replied "Fine with me" without requesting any further change, so no follow-up is needed.)
llm: PRRT_kwDOCkv3g855rwM4 -> author (The approver asked a direct question (“What’s this?”) about the code, so the PR author needs to explain or adjust the change.)
route: author

PR #8256
facts: approved=False conflicts=yes days_since_last_activity=49
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The author answered the benefit question and followed up with supporting evidence, so the thread is back in the reviewer’s court to react to that explanation.)
route: approver

PR #8240
facts: approved=False conflicts=no days_since_last_activity=32
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The last substantive message is from the author saying they will investigate why the benchmark metrics are zero, so the thread is waiting on the author to do more work before reviewers can proceed.)
route: author

PR #8232
facts: approved=False conflicts=no days_since_last_activity=34
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The reviewer says the PR is blocked by upstream GraalVM setup not supporting Java 26 yet, so the next action depends on an external artifact becoming available.)
route: external

PR #8197
facts: approved=False conflicts=yes days_since_last_activity=40
threads: author=0 reviewer=0 external=0 none=1 unclear=0
llm: pr-conversation -> none (The reviewer already agreed to keep the PR as a reference, and the author’s last comment only links the external spec issue without asking for another reply or change in this thread.)
route: approver

PR #8164
facts: approved=False conflicts=no days_since_last_activity=6
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85z-n0C -> author (A reviewer requested a code change to add a spec-aligned config name guardrail, and the author hasn’t applied it yet. The follow-up approver comment is only supportive, not a completion signal.)
route: author

PR #8076
facts: approved=False conflicts=yes days_since_last_activity=19
threads: author=0 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85-kTBF -> reviewer (The reviewer raised an optimization suggestion, and the author replied "added," indicating they acted on it; the thread is now back in reviewer court for re-review.)
llm: pr-conversation -> reviewer (The latest comment is the author asking how to access `setConfig` from an extension and raising a design concern, so the next step is for a reviewer/maintainer to answer or clarify the API path.)
route: approver

PR #7763
facts: approved=False conflicts=yes days_since_last_activity=208
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The reviewer asked for justification, and the author replied with an explanation. The thread is now back in the reviewer’s court to decide whether that answer is sufficient.)
route: approver

PR #7741
facts: approved=False conflicts=no days_since_last_activity=53
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (Reviewer explained why the build still fails and suggested fixes (disable animal-sniffer, split the JFR code, or use a separate source set); the thread is still waiting on the author to choose and implement one of those options.)
route: author

PR #6791
facts: approved=False conflicts=yes days_since_last_activity=16
threads: author=2 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g85aSnGV -> author (The approver asked for a specification source supporting the change, so the PR author needs to जवाब/justify the implementation or update it accordingly.)
llm: PRRT_kwDOCkv3g85aSnh9 -> author (The approver asked the PR author to add a test covering this code path, so the next action is on the author.)
llm: pr-conversation -> none (The comment is only an informational FYI linking another PR and does not request any change or response.)
route: author

Generated 2026-05-26 09:21 UTC

[trask]

Replaced by #8425