Skip to content

Pull Request Dashboard #8375

@github-actions

Description

@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 3d

Waiting on approvers

PR Author CI Conflicts Activity
Bound OkHttp sender dispatchers and surface rejections ADITYA-CODE-SOURCE 0d
Update dependency org.mock-server:mockserver-netty to v6 app/renovate ?
Fix Groovy OpenTelemetrySdk builder loading ADITYA-CODE-SOURCE 4d
profiles: improve JFR export example jhalliday 3d
Make snakeyaml-engine and jackson-databind optional at runtime zeitlinger 31d
Use setup-gradle w/ cache-provider: basic to use more permissive MIT … jack-berg 46d
Add a ConfigProvider callback for runtime instrumentation option changes jackshirazi 16d
Make StandardComponentId constructor public brunobat 206d

Waiting on authors

PR Author CI Conflicts Activity
Finish adding OSGi support jack-berg 0d
Commit declarative config schema pojos to git jack-berg 8d
Merge colliding Prometheus label values ADITYA-CODE-SOURCE 9d
Limit exemplar label characters to conform to Prometheus limits anuq 4d
Update dependency java to v26 trask 44d
Replace ArrayBlockingQueue with park/unpark for BatchSpanProcessor$Worker Khepu 30d
Add JSON pretty-print to logging-otlp exporters lucacavenaghi97 3d
[DO NOT MERGE] JFR API usage jhalliday 50d
Limit prometheus exemplar labels harshitrjpt 13d

Waiting on external

PR Author CI Conflicts Activity
Update junit-framework monorepo - abandoned app/renovate 15d
Update dependency java to v26 app/renovate 32d
Add fallback endpoint support for OTLP exporters sridharsurvi1 37d
Diagnostics
PR #8422
facts: approved=False conflicts=no days_since_last_activity=0
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=0
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The latest comment asks the author whether they plan to open follow-up OSGi PRs for instrumentation and semconv, so the next response is on jack-berg.)
route: author

PR #8413
facts: approved=True conflicts=no days_since_last_activity=3
threads: author=0 reviewer=0 external=0 none=2 unclear=0
llm: PRRT_kwDOCkv3g86C7dSe -> none (The only comment is the author explaining that the test covers the remaining gap; it does not request review or action, and no follow-up is implied.)
llm: PRRT_kwDOCkv3g86Dgb4W -> none (The author is just giving an FYI with a reference link; no explicit reply, review, or code change is requested in this thread.)
route: maintainer

PR #8408
facts: approved=False conflicts=no days_since_last_activity=8
threads: author=2 reviewer=2 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g86CKKVv -> none (The author’s comment is just a clarification about what to review and doesn’t ask for a specific follow-up or change.)
llm: PRRT_kwDOCkv3g86CKMLE -> reviewer (The author answered the concern by explaining the suppressed boxed comparison and why it is safe, so the thread is back with the reviewer to acknowledge or continue review.)
llm: PRRT_kwDOCkv3g86CKN7v -> reviewer (The author is asking whether Jackson’s constructor-based deserialization should be changed, so the next step is reviewer input rather than an author action.)
llm: PRRT_kwDOCkv3g86CKPJM -> author (The latest comment is from the PR author noting the methods behave like setters and suggesting they should investigate renaming them to `set*`, so the next step is on the author to make that change or confirm it.)
llm: PRRT_kwDOCkv3g86CKPwd -> author (The author flagged the `toString` output as undesirable and said they should look into changing it, so the next step is for the author to implement a fix.)
route: author

PR #8407
facts: approved=False conflicts=no days_since_last_activity=4
threads: author=0 reviewer=1 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g86CMfQS -> reviewer (The author responded to the requested clarification by adding the explanation comment, so the thread is now back in the reviewer’s court to confirm and resolve it.)
llm: PRRT_kwDOCkv3g86CMnfF -> none (The author answered the question by explaining the reflective loading rationale, and no further change or follow-up was requested in the thread.)
route: approver

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

PR #8364
facts: approved=False conflicts=no days_since_last_activity=9
threads: author=3 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g86BhQsA -> author (The approver asked for code/test changes: add a clarifying comment and adjust the implementation to avoid the extra allocation by using a no-collision-first strategy.)
llm: PRRT_kwDOCkv3g86BhVsZ -> author (The reviewer flagged a required code change: collisions must account for normalized labels from resource, scope, and additionalAttributes too, so the author needs to update the implementation.)
llm: pr-conversation -> author (The author committed to make the requested code changes and re-request review; the only blocker mentioned is another in-repo PR, not an external dependency.)
route: author

PR #8362
facts: approved=False conflicts=no days_since_last_activity=4
threads: author=1 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g86C-hHG -> none (An outsider offered an optional test readability suggestion (use Named arguments) without requesting a required change, so no follow-up is needed for this thread.)
llm: PRRT_kwDOCkv3g86C-jIw -> author (A reviewer/outside commenter requested a code change (“Rename `short` to `short_attr`”), so the author would need to act on it.)
route: author

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

PR #8270
facts: approved=False conflicts=yes days_since_last_activity=31
threads: author=0 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g857PtCt -> none (The reviewer clarified the preferred direction, and the author acknowledged it and agreed to keep this work as a follow-up. No further response or decision is requested in the thread.)
route: approver

PR #8261
facts: approved=True conflicts=no days_since_last_activity=44
threads: author=1 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g855XQ2Y -> none (The author asked an optional compatibility question about using zulu, and the approver replied “Fine with me,” so there’s no remaining action required in this thread.)
llm: PRRT_kwDOCkv3g855rwM4 -> author (The approver asked a direct question about the code change (“What’s this?”), so the author needs to explain or adjust the thread.)
route: author

PR #8256
facts: approved=False conflicts=yes days_since_last_activity=46
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 that the TOU differ by cache provider, so the thread is back in the reviewer’s court for acknowledgment or further review.)
route: approver

PR #8240
facts: approved=False conflicts=no days_since_last_activity=30
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The last comment is from the author and says they will investigate why the benchmark metrics are zero, so the next step is on the author to follow up with that work or results.)
route: author

PR #8232
facts: approved=False conflicts=no days_since_last_activity=32
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The approver says the PR is blocked by GraalVM lacking a usable Java 26 artifact, so the issue depends on upstream support outside this repository.)
route: external

PR #8197
facts: approved=False conflicts=yes days_since_last_activity=37
threads: author=0 reviewer=0 external=1 none=0 unclear=0
llm: pr-conversation -> external (The discussion was moved to an OpenTelemetry specification issue, so the next step depends on that external spec decision rather than action inside this PR.)
route: external

PR #8164
facts: approved=False conflicts=no days_since_last_activity=3
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85z-n0C -> author (A reviewer requested changing the config key to the declarative config naming convention, and another approver agreed; the remaining step is for the PR author to make that code change.)
route: author

PR #8076
facts: approved=False conflicts=yes days_since_last_activity=16
threads: author=0 reviewer=2 external=0 none=0 unclear=0
llm: PRRT_kwDOCkv3g85-kTBF -> reviewer (The reviewer suggested adding a TODO for a later optimization, and the author replied “added,” so the thread is back in reviewer court to confirm the change is acceptable.)
llm: pr-conversation -> reviewer (The latest comment is from the author asking how to call `setConfig` from an extension and whether `GlobalOpenTelemetry.get()` can be cast, so the thread is waiting on reviewer guidance/input.)
route: approver

PR #7763
facts: approved=False conflicts=yes days_since_last_activity=206
threads: author=0 reviewer=1 external=0 none=0 unclear=0
llm: pr-conversation -> reviewer (The author answered the reviewer’s question with a rationale, so the thread is back in reviewer court for follow-up or approval.)
route: approver

PR #7741
facts: approved=False conflicts=no days_since_last_activity=50
threads: author=1 reviewer=0 external=0 none=0 unclear=0
llm: pr-conversation -> author (The latest comment is an outsider suggesting an external bridge library and explicitly asks the author to weigh in, so the next response is on the PR author.)
route: author

PR #6791
facts: approved=False conflicts=yes days_since_last_activity=13
threads: author=2 reviewer=0 external=0 none=1 unclear=0
llm: PRRT_kwDOCkv3g85aSnGV -> author (A reviewer asked whether the change is based on a specification, so the author needs to जवाब/justify the implementation or update the code accordingly.)
llm: PRRT_kwDOCkv3g85aSnh9 -> author (The reviewer asked for an additional test coverage change, so the PR author needs to implement it.)
llm: pr-conversation -> none (The comment only points to another PR for the same issue and does not request any change or reply, so it is informational only.)
route: author

Generated 2026-05-23 16:26 UTC

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions