runtime: Rekey p-token feature gate#9979
Conversation
|
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #9979 +/- ##
=======================================
Coverage 82.5% 82.5%
=======================================
Files 846 846
Lines 316799 316799
=======================================
+ Hits 261573 261608 +35
+ Misses 55226 55191 -35 🚀 New features to boost your workflow:
|
t-nelson
left a comment
There was a problem hiding this comment.
damn how'd i miss this...
in the future try to rekey in the pr that makes the change to gated logic. this makes it more difficult for us to botch backports
Rekey p-token feature (cherry picked from commit 804c089)
Problem
p-token feature needs a rekey to go with the changes in SIMD-0444 (#9891).
Summary of Changes
Rekey it. This PR also rekeys the expected program buffer key for the migration.