dimas-b opened a new pull request, #1817:
URL: https://github.com/apache/polaris/pull/1817

   * Avoid propagating request contexts into threads running background tasks.
   
   * Use fresh request context for each task instead.
   
   * Manually propagate realm context into a task from the request that submits 
the task.
   
   * Update DefaultConfigurationStore to cross-check realm IDs in request 
context and explicit method parameters.
   
   * Fix tests to set thread-local data to match CDI context data.
   
   Next step: Simplify DefaultConfigurationStore API to remove contextual 
arguments and use CDI context instead.
   
   <!--
       Possible security vulnerabilities: STOP here and contact 
[email protected] instead!
   
       Please update the title of the PR with a meaningful message - do not 
leave it "empty" or "generated"
       Please update this summary field:
   
       The summary should cover these topics, if applicable:
       * the motivation for the change
       * a description of the status quo, for example the current behavior
       * the desired behavior
       * etc
   
       PR checklist:
       - Do a self-review of your code before opening a pull request
       - Make sure that there's good test coverage for the changes included in 
this PR
       - Run tests locally before pushing a PR (./gradlew check)
       - Code should have comments where applicable. Particularly 
hard-to-understand
         areas deserve good in-line documentation.
       - Include changes and enhancements to the documentation (in 
site/content/in-dev/unreleased)
       - For Work In Progress Pull Requests, please use the Draft PR feature.
   
       Make sure to add the information BELOW this comment.
       Everything in this comment will NOT be added to the PR description.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to