- 
                Notifications
    
You must be signed in to change notification settings  - Fork 129
 
fix: configure runner config per runner name #2891
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
fix: configure runner config per runner name #2891
Conversation
| 
           The latest updates on your projects. Learn more about Vercel for GitHub. 
 1 Skipped Deployment
  | 
    
| 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
          
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking.  | 
    
          
commit:   | 
    
b3091dc    to
    a5cea8e      
    Compare
  
    | 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
| let variant_str = serde_json::to_string(&input.config.variant())?; | ||
| ctx.op(internal::ops::cache::purge_global::Input { | ||
| base_key: format!("namespace.runner_config.{variant_str}.get_global"), | ||
| keys: vec![(input.namespace_id, input.name.as_str()).cache_key().into()], | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The serialization of input.config.variant() to JSON creates inconsistent cache keys. Since JSON serialization of enums can vary (quotes, formatting), it may not match the string representation used elsewhere in the codebase.
Consider using a deterministic string representation instead:
let variant_str = input.config.variant().to_string();This approach ensures cache keys remain consistent across the application, preventing unnecessary cache misses and improving cache hit rates.
| let variant_str = serde_json::to_string(&input.config.variant())?; | |
| ctx.op(internal::ops::cache::purge_global::Input { | |
| base_key: format!("namespace.runner_config.{variant_str}.get_global"), | |
| keys: vec![(input.namespace_id, input.name.as_str()).cache_key().into()], | |
| let variant_str = input.config.variant().to_string(); | |
| ctx.op(internal::ops::cache::purge_global::Input { | |
| base_key: format!("namespace.runner_config.{variant_str}.get_global"), | |
| keys: vec![(input.namespace_id, input.name.as_str()).cache_key().into()], | 
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
c376b93    to
    8b5ef7d      
    Compare
  
    a5cea8e    to
    6b11630      
    Compare
  
    | 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
| 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
| let for_serverless = txs | ||
| .exists( | ||
| &namespace::keys::RunnerConfigByVariantKey::new( | ||
| namespace_id, | ||
| namespace::keys::RunnerConfigVariant::Serverless, | ||
| input.runner_name_selector.clone(), | ||
| ), | ||
| SERIALIZABLE, | ||
| ) | ||
| .await?; | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Database key construction uses wrong namespace. The code creates a namespace::keys::RunnerConfigByVariantKey but uses it with txs which is in the pegboard subspace, not the namespace subspace. This will cause the key lookup to fail since it's looking in the wrong database subspace.
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
6b11630    to
    88d706e      
    Compare
  
    8b5ef7d    to
    4976f94      
    Compare
  
    | 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
| 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
88d706e    to
    c5ce959      
    Compare
  
    4976f94    to
    02c9438      
    Compare
  
    c5ce959    to
    7679f25      
    Compare
  
    02c9438    to
    21d608d      
    Compare
  
    | 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
| 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
7679f25    to
    c5ce959      
    Compare
  
    | 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
c5ce959    to
    7d7900b      
    Compare
  
    02c9438    to
    3df4e46      
    Compare
  
    | 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
| 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    
3df4e46    to
    012075b      
    Compare
  
    7d7900b    to
    c2c14ae      
    Compare
  
    | 
           Claude encountered an error —— View job I'll analyze this and get back to you.  | 
    

No description provided.