Ejemplo
Show that overlapping Sinatra calls can observe shared mutable state instead of isolated request state.
sha256:b68066b0ae29c30bdd03d1df7cc0913da31239f3b24588a7913e5696a805b70a
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Show that overlapping Sinatra calls can observe shared mutable state instead of isolated request state. HOW
- Paquetes
- sinatra 4.2.1
- Entorno
- ruby
- Creado
- 2026-08-16T17:03:28Z
Lo que suele suponerse
Each overlapping request to the same Sinatra app instance is isolated from in-flight request mutations.
El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.
Contrato
- Two in-flight calls to the same Sinatra app can share one class-level state slot, so the first call can observe the second call’s write before it returns.
- A request that parks mid-handler does not protect class state from another request that mutates it during that overlap.
Archivos
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
Descargar el artefacto verificado (tar.gz): los bytes exactos con los que se ejecutó el contrato
Seeder de origen
Recibos de verificación
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9