fix(rust-v2): Context extraction mapping and add decorator benchmarks#65
Open
fix(rust-v2): Context extraction mapping and add decorator benchmarks#65
Conversation
This PR resolves the missing context injection across the Rust FFI boundary, preventing mapped values in the @kest_verified decorator from accurately reaching Policy Engines (Cedar). It also adds robust multi-threaded decorator benchmark testing and a new synchronous/asynchronous FastAPI execution benchmark to precisely graph GIL scaling under various workloads.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes the bug preventing user context from correctly being evaluated natively in rust-v2 Kest pipelines by fetching the dict explicitly via the PyDict FFI.
Updates
req_dict["context"].v2::PipelineRequest::newto fetch and map context to the globalenvironment.bench_decorator_throughput.py.