Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Context Propagation performance issue and init issue #39988

Merged
merged 4 commits into from
Apr 15, 2024

Commits on Apr 8, 2024

  1. Make a custom ContextManagerProvider with a single manager

    Because Quarkus doesn't care about one-per CL and Franz said this is a
    bottleneck for some reason
    FroMage committed Apr 8, 2024
    Configuration menu
    Copy the full SHA
    eb6b1ff View commit details
    Browse the repository at this point in the history

Commits on Apr 9, 2024

  1. Make sure OIDC is set up after CP

    It uses Mutiny, which requires CP to be initialised
    FroMage committed Apr 9, 2024
    Configuration menu
    Copy the full SHA
    ad06f24 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    b9cc3c2 View commit details
    Browse the repository at this point in the history

Commits on Apr 10, 2024

  1. CP: set up a temporary no-context/no-executor ContextManagerProvider …

    …during boot
    
    Because some extensions (only known one is spring-cloud-config-client)
    use Vert.x via Mutiny before runtime init is done. Mutiny and CP are
    both not set up yet, due to missing executor, but I'm starting CP with
    zero contexts and an executor which throws with an explicit error
    message, which should be enough to boot until runtime is properly set
    up.
    FroMage committed Apr 10, 2024
    Configuration menu
    Copy the full SHA
    08ba1d1 View commit details
    Browse the repository at this point in the history