Skip to content

Conversation

michalvavrik
Copy link
Member

@quarkus-bot quarkus-bot bot added area/core area/dependencies Pull requests that update a dependency file area/metrics area/tracing labels Jan 13, 2025
Copy link

quarkus-bot bot commented Jan 13, 2025

/cc @brunobat (micrometer,opentelemetry), @ebullient (micrometer), @radcortez (opentelemetry)

@michalvavrik michalvavrik changed the title WebSockets Next: use SPI to separate websockets from OpenTelemetry and Micrometer extensions WebSockets Next: use SPI to separate the Websockets extension from OpenTelemetry and Micrometer extensions Jan 13, 2025
Copy link

github-actions bot commented Jan 13, 2025

🎊 PR Preview dd7edc6 has been successfully built and deployed to https://quarkus-pr-main-45522-preview.surge.sh/version/main/guides/

  • Images of blog posts older than 3 months are not available.
  • Newsletters older than 3 months are not available.

This comment has been minimized.

This comment has been minimized.

Copy link
Contributor

@mkouba mkouba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good but I cannot talk about the opentelemetry/micrometer part..

@michalvavrik michalvavrik force-pushed the feature/ws-next-micrometer-tests-and-spi branch from 139641c to 8d40ce1 Compare January 13, 2025 12:10

This comment has been minimized.

This comment has been minimized.

@gsmet
Copy link
Member

gsmet commented Jan 28, 2025

Hey @brunobat , could you have a look at this one? It looks like something we would want for the next LTS.

@brunobat
Copy link
Contributor

brunobat commented Jan 28, 2025

I wish we had discussed this before implementing it because if we adopt the observation API in the future, we will need to rewrite it all again. Maybe we did, but I don't remember. Sorry.
Will review asap, but not today.

@michalvavrik
Copy link
Member Author

I wish we had discussed this before implementing it because if we adopt the observation API in the future, we will need to rewrite it all again. Maybe we did, but I don't remember. Sorry. Will review asap, but not today.

I don't mind rewriting it again @brunobat .

@michalvavrik
Copy link
Member Author

Maybe we did, but I don't remember.

no, we didn't, I didn't realize this could be improved, I am happy to meet you and rewrite this. Thanks

@cescoffier
Copy link
Member

@brunobat any news?

Copy link
Contributor

@brunobat brunobat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've decided this is good to go.
We will need to handle whatever happens after Observability.next, afterwards.

@gsmet gsmet force-pushed the feature/ws-next-micrometer-tests-and-spi branch from 8d40ce1 to 151ee9c Compare April 8, 2025 15:53
@gsmet
Copy link
Member

gsmet commented Apr 8, 2025

I rebased the PR to fix a conflict and get an updated CI run.

@gsmet gsmet added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Apr 8, 2025

This comment has been minimized.

This comment has been minimized.

Copy link
Member

@cescoffier cescoffier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks ok, however, we need to verify that:

  1. This is not a breaking change
  2. There are no split packages

@michalvavrik
Copy link
Member Author

I'll check early next week.

@brunobat
Copy link
Contributor

rifier discovered a type not marked as reachable: AnalysisType<VMOption$Origin[] -> HotSpotType<[Lcom/sun/management/VMOption$Origin;, resolved>, allocated: false, inHeap: false, reachable: false>

Any chance it is this one #46890 ?

Makes sense, but I'm intrigued why we haven't seen this failure sooner...

@michalvavrik michalvavrik force-pushed the feature/ws-next-micrometer-tests-and-spi branch from 1d7326a to 4f52cf2 Compare April 27, 2025 14:40

This comment has been minimized.

This comment has been minimized.

@michalvavrik
Copy link
Member Author

The failure is gone, MicrometerWebSocketsOnErrorTest seems flaky on Windows, but that won't be due to this PR (as it changes nothing functionally).

@michalvavrik
Copy link
Member Author

I have requested 2 other reviews because it's unclear to me what is current situation (what are we waiting for with merging).

Copy link
Member

@cescoffier cescoffier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My only concern is the URI tag in metrics. CC @brunobat
It would be great to have the review from @mkouba

Copy link
Contributor

@mkouba mkouba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The WS Next part is ok. I just added a tiny nitpicking comment ;-).

@michalvavrik michalvavrik removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label Apr 30, 2025
@michalvavrik michalvavrik force-pushed the feature/ws-next-micrometer-tests-and-spi branch from 4f52cf2 to 1e3128a Compare April 30, 2025 11:42
@mkouba mkouba requested a review from brunobat April 30, 2025 12:17

This comment has been minimized.

Copy link
Contributor

@brunobat brunobat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @michalvavrik

@mkouba mkouba added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Apr 30, 2025

This comment has been minimized.

@michalvavrik michalvavrik force-pushed the feature/ws-next-micrometer-tests-and-spi branch from 1e3128a to d1e7009 Compare May 1, 2025 13:04
@michalvavrik
Copy link
Member Author

GH CI stuck on "CI Sanity Check" (Expected - Waiting for status to be reported). I'll rebase again.

@michalvavrik michalvavrik force-pushed the feature/ws-next-micrometer-tests-and-spi branch from d1e7009 to ca75c71 Compare May 2, 2025 07:23
Copy link

quarkus-bot bot commented May 2, 2025

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit ca75c71.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

Copy link

quarkus-bot bot commented May 2, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit ca75c71.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

@geoand geoand merged commit 4c0d835 into quarkusio:main May 2, 2025
59 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.23 - main milestone May 2, 2025
@quarkus-bot quarkus-bot bot removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label May 2, 2025
@michalvavrik michalvavrik deleted the feature/ws-next-micrometer-tests-and-spi branch May 2, 2025 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants