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
Avoid spurious api change warnings from automated release PRs	jack-berg	❌	✅	2d
Update dependency org.jetbrains.kotlin:kotlin-gradle-plugin to v2.3.21	app/renovate	❌	✅	55d

Waiting on approvers

PR	Author	CI	Conflicts	Activity
Deprecate opentracing shim public API	ADITYA-CODE-SOURCE	✅	❌	4d
Merge colliding Prometheus label values	ADITYA-CODE-SOURCE	✅	✅	4d
profiles: improve JFR export example	jhalliday	✅	✅	10d
Update prometheusServerVersion to v1.6.1	app/renovate	❌	✅	?
Move otlp utilities to otlp package	jack-berg	✅	❌	4d
Protect against index out of bounds exception	jack-berg	❌	✅	17d
Use setup-gradle w/ cache-provider: basic to use more permissive MIT …	jack-berg	✅	❌	34d
Add JSON pretty-print to logging-otlp exporters	lucacavenaghi97	✅	✅	59d
Add a ConfigProvider callback for runtime instrumentation option changes	jackshirazi	❌	✅	4d
Make StandardComponentId constructor public	brunobat	✅	❌	193d

Waiting on authors

PR	Author	CI	Conflicts	Activity
Collect async exemplars when exemplar filter is always_on	ADITYA-CODE-SOURCE	✅	✅	2d
Limit exemplar label characters to conform to Prometheus limits	anuq	✅	✅	1d
Move delta record/collect coordination from instrument to series level	jack-berg	❌	✅	2d
Make snakeyaml-engine and jackson-databind optional at runtime	zeitlinger	✅	❌	19d
Update dependency java to v26	trask	✅	✅	32d
Add missing set value attribute shortcuts	trask	✅	✅	0d
Replace ArrayBlockingQueue with park/unpark for BatchSpanProcessor$Worker	Khepu	✅	✅	18d
[DO NOT MERGE] JFR API usage	jhalliday	❌	✅	38d
Limit prometheus exemplar labels	harshitrjpt	✅	❌	1d

Waiting on external

PR	Author	CI	Conflicts	Activity
Update junit-framework monorepo	app/renovate	❌	✅	3d
Update dependency java to v26	app/renovate	❌	✅	19d
Add fallback endpoint support for OTLP exporters	sridharsurvi1	❌	❌	25d

Diagnostics

PR #8387
facts: approved=True conflicts=no days_since_last_activity=2
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: maintainer

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

PR #8373
facts: approved=False conflicts=yes days_since_last_activity=4
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: approver

PR #8364
facts: approved=False conflicts=no days_since_last_activity=4
threads: author=0 reviewer=0 external=0 none=1 unclear=0
llm: pr-conversation -> none (The reviewer asked to park the PR because of overlap with #8346, and the author agreed to wait; no immediate follow-up is needed on this thread.)
route: approver

PR #8363
facts: approved=False conflicts=no days_since_last_activity=2
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86Avr6A -> author (The approver requested additional test coverage and default-case assertions, so the PR author needs to make those code changes.)
route: author

PR #8362
facts: approved=False conflicts=no days_since_last_activity=1
threads: author=2 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86A2FZf -> author (A reviewer-side comment requests a code change: use `codePointCount` instead of `length`, so the PR author needs to address or respond to the suggestion.)
llm: PRRT_kwDOCkv3g86A2G81 -> author (An outsider asked the author to change the added unit tests into parameterized tests, so the thread is waiting on the PR author to respond or implement that request.)
route: author

PR #8349
facts: approved=False conflicts=no days_since_last_activity=10
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The author is explicitly asking profiling maintainers for input on spec changes and unresolved contradictions, so the next action is on the reviewers/maintainers.)
route: approver

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

PR #8326
facts: approved=False conflicts=yes days_since_last_activity=4
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The author is asking `@open-telemetry/java-approvers` to take a look, so the next step is reviewer review/response.)
route: approver

PR #8313
facts: approved=False conflicts=no days_since_last_activity=2
threads: author=1 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g858njQs -> reviewer (The author has already explained their rationale for splitting cumulative and delta code paths; no new implementation request is stated, so the reviewer needs to respond or decide whether to accept it.)
llm: PRRT_kwDOCkv3g858nkV1 -> author (The author left a TODO to revert or make the test configurable before merging, so the next step is on the author to implement that change.)
llm: PRRT_kwDOCkv3g86AVPvC -> reviewer (The author explains a test change to address the sleep-precision issue, so the next step is for a reviewer to re-check whether the updated approach is acceptable.)
route: author

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

PR #8270
facts: approved=False conflicts=yes days_since_last_activity=19
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g857PtCt -> author (The reviewer asked for the implementation to move to an internal package / be handled in a follow-up, and the author replied that they would keep this PR as that follow-up.)
route: author

PR #8261
facts: approved=True conflicts=no days_since_last_activity=32
threads: author=1 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g855XQ2Y -> none (The author asked whether Zulu would work, and the approver replied "Fine with me," making it informational with no follow-up requested.)
llm: PRRT_kwDOCkv3g855rwM4 -> author (The approver asked "What's this?" on the code change, so the author needs to explain or adjust it.)
route: author

PR #8256
facts: approved=False conflicts=yes days_since_last_activity=34
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The author answered the reviewer’s question with evidence about Gradle’s TOU, so the thread is back in the reviewer’s court to review that explanation.)
route: approver

PR #8255
facts: approved=True conflicts=no days_since_last_activity=0
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g857fR2F -> author (The author requested a change in the thread, and the latest response is just a ping to the author, so the next action is for the author to respond or update the code/comments.)
route: author

PR #8240
facts: approved=False conflicts=no days_since_last_activity=18
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The reviewer requested benchmark results, and the author followed up by saying they will investigate why the relevant benchmarks report zero metrics and try again.)
route: author

PR #8232
facts: approved=False conflicts=no days_since_last_activity=19
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (CI is blocked by GraalVM lacking a Java 26 artifact, so the next step depends on upstream support rather than a repo-local change.)
route: external

PR #8197
facts: approved=False conflicts=yes days_since_last_activity=25
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The reviewer already agreed to keep this PR as a reference implementation, and the author’s last reply only points to the related spec issue, so the remaining work is outside this repository.)
route: external

PR #8164
facts: approved=False conflicts=no days_since_last_activity=59
threads: author=0 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85z-n0C -> reviewer (The latest comment is from a reviewer asking for input from approvers on the proposed config naming change, so the thread is waiting on reviewer-side feedback/approval.)
llm: pr-conversation -> reviewer (The author says they are waiting for approver feedback before updating, so the next move is on a reviewer/approver.)
route: approver

PR #8076
facts: approved=False conflicts=no days_since_last_activity=4
threads: author=0 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85-kTBF -> reviewer (The reviewer raised a performance concern, and the author replied “added,” indicating they made the requested adjustment; the thread is now back in reviewer court for re-review.)
llm: pr-conversation -> reviewer (The latest comment is from the author asking how to call `setConfig` from an extension and raising a design concern, so the thread is waiting on reviewer input.)
route: approver

PR #7924
facts: approved=True conflicts=no days_since_last_activity=55
threads: author=0 reviewer=0 external=0 none=0 unclear=0
route: maintainer

PR #7763
facts: approved=False conflicts=yes days_since_last_activity=193
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The reviewer asked why the change was needed, and the author answered; the next step is for the reviewer to assess that explanation and continue the review.)
route: approver

PR #7741
facts: approved=False conflicts=no days_since_last_activity=38
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The reviewer provided implementation options, and the latest outsider comment is just a suggestion/link with “Let me know what you think,” so the author needs to decide and act.)
route: author

PR #6791
facts: approved=False conflicts=yes days_since_last_activity=1
threads: author=2 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g85aSnGV -> author (The reviewer asks whether the change is based on a specification, so the PR author needs to जवाब/respond with that source or rationale.)
llm: PRRT_kwDOCkv3g85aSnh9 -> author (The approver asked the PR author to add a test covering the change, so the next action is on the author.)
llm: pr-conversation -> none (The only comment is an informational FYI linking another PR, with no explicit request for action or response.)
route: author

Generated 2026-05-11 11:11 UTC