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
Add Prometheus translation strategy support	zeitlinger	❌	✅	0d

Waiting on approvers

PR	Author	CI	Conflicts	Activity
Update azul/zulu-openjdk Docker tag to v26	app/renovate	❌	✅	?
Fix Groovy compatibility in OpenTelemetrySdkBuilder	ADITYA-CODE-SOURCE	✅	❌	7d
Update to opentelemetry-configuration v1.1.0	jack-berg	❌	✅	1d
profiles: improve JFR export example	jhalliday	✅	✅	29d
Make StandardComponentId constructor public	brunobat	✅	❌	231d

Waiting on authors

PR	Author	CI	Conflicts	Activity
Fix baggage parsing for invalid percent-encoded members	Vcode2407	✅	✅	0d
Fix W3CBaggagePropagator to allow empty baggage values per W3C spec	dahyvuun	✅	✅	6d
[DRAFT] Entity SDK prototype	jsuereth	✅	❌	0d
Restore compliance between Composite Samplers code and specs	PeterF778	✅	✅	1d
Enforce OTLP request size limits	ADITYA-CODE-SOURCE	❌	✅	1d
Avoid dropping metrics when forceFlush() races with the periodic export	mahitha-ada	✅	✅	7d
Use HTTP error bodies in HttpExporter warnings	ADITYA-CODE-SOURCE	✅	✅	5d
Fix Groovy OpenTelemetrySdk builder loading	ADITYA-CODE-SOURCE	✅	✅	30d
Merge colliding Prometheus label values	ADITYA-CODE-SOURCE	✅	❌	34d
Replace ArrayBlockingQueue with park/unpark for BatchSpanProcessor$Worker	Khepu	✅	✅	56d
Add JSON pretty-print to logging-otlp exporters	lucacavenaghi97	✅	❌	29d
Add a ConfigProvider callback for runtime instrumentation option changes	jackshirazi	❌	❌	1d
[DO NOT MERGE] JFR API usage	jhalliday	❌	✅	76d

Waiting on external

PR	Author	CI	Conflicts	Activity
Add fallback endpoint support for OTLP exporters	sridharsurvi1	❌	❌	63d

Workflow failure tracking issues

Issue	Comments	Updated
Workflow failed: Sonatype Guide dependency audit (daily) (#33)	15	2026-06-18

Diagnostics

PR #8480
facts: approved=False conflicts=no days_since_last_activity=0
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86J-p1w -> author (The reviewer explicitly requests a warning-level log for invalid baggage fields, and the author said they’re happy to update it if preferred, so the next implementation step is with the author.)
route: author

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

PR #8468
facts: approved=True conflicts=no days_since_last_activity=6
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86ImrO2 -> author (The approver explicitly says the requested change is still not addressed and asks for code/test updates in this PR, so the next step is for the author to make the change.)
route: author

PR #8467
facts: approved=False conflicts=yes days_since_last_activity=7
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The reviewer asked for the motivation, and the author answered with the rationale and issue link. The thread is now back in the reviewer’s court to evaluate the explanation or continue the review.)
route: approver

PR #8464
facts: approved=False conflicts=yes days_since_last_activity=0
threads: author=10 reviewer=0 external=0 none=2 unclear=0
llm: PRRT_kwDOCkv3g86I3mmm -> author (The approver’s comment is a question/request for clarification, so the PR author needs to जवाब/act next.)
llm: PRRT_kwDOCkv3g86I3oqd -> author (An approver suggested a code change (`addEntity(Entity e)`), so the PR author needs to apply or address it.)
llm: PRRT_kwDOCkv3g86I3o9g -> author (The approver asked for a code change (“Omit this sugar to start”), so the PR author needs to update the implementation before the thread can move forward.)
llm: PRRT_kwDOCkv3g86I3qPO -> author (The approver asks the author to change the implementation strategy (compute/memoize at initialization time in Resource.create), so the next action is on the PR author.)
llm: PRRT_kwDOCkv3g86I3qb_ -> author (The approver’s unresolved "???" comment signals a question/concern on the code, so the author needs to respond or clarify.)
llm: PRRT_kwDOCkv3g86I3thx -> author (The reviewer is pointing out a code change is unnecessary and suggesting an edit to the method signature, so the PR author needs to apply or consider that change.)
llm: PRRT_kwDOCkv3g86I3uKP -> author (The approver requested code and javadoc changes: rename the methods to `set<Property>` and clarify whether the behavior is set or merge semantics. That requires the PR author to update the implementation.)
llm: PRRT_kwDOCkv3g86I3wYO -> author (An approver left a code suggestion on the line, so the next step is for the PR author to apply or address it.)
llm: PRRT_kwDOCkv3g86I3wgW -> author (The approver suggested a code change (`static Entity create(`), so the author needs to update the implementation and respond.)
llm: PRRT_kwDOCkv3g86KXDhc -> author (The approver is asking a design question that needs a response from the PR author about why a new `EntityDetector` SPI is needed instead of reusing `ResourceProvider`.)
llm: PRRT_kwDOCkv3g86KXHEj -> none (The approver is giving an implementation assumption rather than requesting a concrete change, so no explicit follow-up is required in the thread.)
llm: PRRT_kwDOCkv3g86KXMcg -> none (The approver’s comment is informational and explicitly says ResourceFactory likely needs no change on this path, so there’s no follow-up action requested from either side.)
route: author

PR #8451
facts: approved=False conflicts=no days_since_last_activity=1
threads: author=0 reviewer=1 external=0 none=2 unclear=0
llm: PRRT_kwDOCkv3g86Hblrk -> reviewer (The author says they had to fix the code to add support for the new declarative config property, so the change is back for reviewer verification.)
llm: PRRT_kwDOCkv3g86HbmIQ -> none (The only visible comment is the author explaining the implementation choice; it doesn’t ask for reviewer input or request any external action, so no follow-up is implied.)
llm: PRRT_kwDOCkv3g86J9HVV -> none (The only comment is the author noting that the POJO diffs are useful to see; it does not request a change or review action.)
route: approver

PR #8450
facts: approved=True conflicts=no days_since_last_activity=1
threads: author=1 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g86IoHpI -> none (The only comment is an optional wording suggestion on a doc comment, and the approver later approved after the thread, so no follow-up is needed.)
llm: pr-conversation -> author (The author asked whether the change needs an issue, and the approver answered yes, so the next step is for the author to create/follow up on that issue.)
route: author

PR #8446
facts: approved=True conflicts=no days_since_last_activity=1
threads: author=1 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g86KBUh4 -> author (The approver asked a direct design question (“Why two methods?”), so the author is the one who needs to explain or adjust the implementation unless a later reply in-thread resolves it.)
llm: PRRT_kwDOCkv3g86KBWSq -> none (This was a non-blocking nit/suggestion from an approver, and the same approver later approved the PR, so no follow-up is needed on this thread.)
route: author

PR #8437
facts: approved=False conflicts=no days_since_last_activity=7
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The approver is questioning the PR’s implementation and whether the behavior change is needed, so the author needs to respond or revise the PR.)
route: author

PR #8428
facts: approved=False conflicts=no days_since_last_activity=5
threads: author=2 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86FNGwS -> author (An approver asked a direct question about the chosen number, so the author needs to explain or adjust the code before the thread can move forward.)
llm: PRRT_kwDOCkv3g86JKWNr -> author (The approver is asking whether the test can be simplified to `new FakeHttpResponse(500, "Internal Server Error", null)`, so the author needs to जवाब or adjust the test.)
route: author

PR #8407
facts: approved=False conflicts=no days_since_last_activity=30
threads: author=1 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86CMfQS -> reviewer (The reviewer asked for added justification, and the author responded that they added the requested comment. The thread is still unresolved, so it’s back in the reviewer’s court to verify and either approve or ask for more.)
llm: PRRT_kwDOCkv3g86CMnfF -> reviewer (The reviewer asked why the type was changed to `Object`, and the author answered with the rationale. The thread is now back in the reviewer’s court to accept or raise a follow-up concern.)
llm: pr-conversation -> author (The latest comment is a reviewer asking the author to consider `@CompileStatic` and questioning whether reflection is necessary, so the next move is for the PR author to जवाब/respond or adjust the implementation.)
route: author

PR #8364
facts: approved=False conflicts=yes days_since_last_activity=34
threads: author=2 reviewer=0 external=1 none=0 unclear=0
llm: PRRT_kwDOCkv3g86BhQsA -> author (The approver requested follow-up changes to the test setup and allocation strategy, so the PR author needs to update the code or reply with an implementation.)
llm: PRRT_kwDOCkv3g86BhVsZ -> author (The approver points out a missing case in the implementation: collisions from normalized `resource`, `scope`, and `additionalAttributes` also need to be handled. The thread is unresolved, so the PR author needs to update the code.)
llm: pr-conversation -> external (The author says they’ll make the requested changes only after #8346 settles, so this thread is currently blocked on an upstream PR dependency rather than on immediate review or implementation.)
route: author

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

PR #8346
facts: approved=True conflicts=no days_since_last_activity=0
threads: author=0 reviewer=1 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g86KC_SY -> none (The approver only suggested adding a test, and the thread fact says the same approver later approved after the thread, so this looks non-blocking and already addressed.)
llm: pr-conversation -> reviewer (The author replied “done,” indicating the requested change was addressed and the thread is back in the reviewer’s court for confirmation or any further review.)
route: maintainer

PR #8240
facts: approved=False conflicts=no days_since_last_activity=56
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The reviewer asked for benchmark before/after results, and the author responded that they need to investigate why the relevant benchmark metrics are zero before they can provide them.)
route: author

PR #8197
facts: approved=False conflicts=yes days_since_last_activity=63
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The latest author comment points to an open specification issue outside this repo, and the discussion is explicitly waiting on that spec-first path before more PR work can proceed.)
route: external

PR #8164
facts: approved=False conflicts=yes days_since_last_activity=29
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85z-n0C -> author (A reviewer requested a config-name guardrail change, and the follow-up comment only expressed support without implementing it, so the author still needs to make the code update.)
route: author

PR #8076
facts: approved=False conflicts=yes days_since_last_activity=1
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The latest comment is from the PR author saying they will test and validate the approach, so the thread is waiting on the author to follow up before review can continue.)
route: author

PR #7763
facts: approved=False conflicts=yes days_since_last_activity=231
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The reviewer asked for justification, and the author answered with rationale; the thread is now back in the reviewer’s court to accept or continue the discussion.)
route: approver

PR #7741
facts: approved=False conflicts=no days_since_last_activity=76
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The reviewer’s last substantive reply gave implementation options for the animal-sniffer/JFR problem, and the author hasn’t responded with a fix yet.)
route: author

Generated 2026-06-18 09:39 UTC