Module: Karst::ExecutionContext

Defined in:
lib/karst/execution_context.rb

Overview

Request-local correlation storage used by the page badge and the RSpec scenario observer to carry evidence from a notification callback (fired nested inside a Rack call or an RSpec example) back out to the code that reads it, without a global mutable variable that would let concurrent requests or examples cross-contaminate each other.

Modern Rails already solves exactly this with ActiveSupport::IsolatedExecutionState, so Karst simply delegates to it when present. Rails 6.1 does not provide that API, so Karst falls back to ThreadLocalStore, a plain per-Thread Hash reached through Thread#thread_variable_get/set -- never Thread#[]/[]=, which are fiber-local and would silently miss context under a Fiber scheduler. This mirrors ActiveSupport::IsolatedExecutionState's own default :thread isolation level: storage is shared by every Fiber running on one OS thread, not isolated per Fiber. Karst's own usage (one badge or spec correlation captured and read back within a single synchronous request/example) never spans multiple concurrently-scheduled Fibers, so this fallback has no observable effect on Karst's supported behavior. It is documented here so a future caller does not assume Fiber isolation this fallback cannot provide.

Class Method Summary collapse

Class Method Details

.[](key) ⇒ Object 



70
71
72
 
# File 'lib/karst/execution_context.rb', line 70

def [](key)
  BACKEND[key]
end

.[]=(key, value) ⇒ Object 



74
75
76
 
# File 'lib/karst/execution_context.rb', line 74

def []=(key, value)
  BACKEND[key] = value
end

.delete(key) ⇒ Object 



78
79
80
 
# File 'lib/karst/execution_context.rb', line 78

def delete(key)
  BACKEND.delete(key)
end