Support multiple subcontexts per context#468
Conversation
Benchmarks gccBenchmark execution time: 2025-10-21 15:21:26 Comparing candidate commit 15be03e in PR branch Found 0 performance improvements and 1 performance regressions! Performance is the same for 0 metrics, 0 unstable metrics. scenario:global-benchmark.random.gcc
|
Benchmarks clangBenchmark execution time: 2025-10-21 15:21:00 Comparing candidate commit 15be03e in PR branch Found 1 performance improvements and 0 performance regressions! Performance is the same for 0 metrics, 0 unstable metrics. scenario:global-benchmark.random.clang
|
Benchmarks clang-pgoBenchmark execution time: 2025-10-21 15:35:51 Comparing candidate commit 15be03e in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 1 metrics, 0 unstable metrics. |
9d7e8d7 to
a53b45c
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #468 +/- ##
==========================================
+ Coverage 84.91% 84.97% +0.05%
==========================================
Files 190 189 -1
Lines 9820 9716 -104
Branches 4293 4223 -70
==========================================
- Hits 8339 8256 -83
+ Misses 612 602 -10
+ Partials 869 858 -11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
a82571d to
1d5a34b
Compare
1d5a34b to
c4572a3
Compare
Artifact Size Comparison 📦
|
b2ece19 to
fba2627
Compare
efd9443 to
607c244
Compare
607c244 to
4cbbd85
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting
* Share user data with subcontext * Prevent context evaluation while subcontexts are active * Update evaluation engine tests to use context / subcontext instead
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting
e869b45 to
809aa37
Compare
809aa37 to
ee72a8b
Compare
7cdfc0b to
aaf16ce
Compare
aaf16ce to
15be03e
Compare
This PR changes the way subcontexts are used and created, they are now a "copy" of the context, allowing the creation and use of many subcontexts at the same time, although not in a thread-safe manner without user-provided synchronisation. This iteration has some caveats:
All of the logic to distinguish contexts and subcontexts internally has been removed for simplification, albeit some of it may come back in the future to address the caveats above.
Remaining work (to be addressed in a future PR):
Related Jiras: APPSEC-59671