CodeSampleX

Пример

sorbet-runtime 0.6.13427: Prove that sorbet-runtime does not clear a previously computed signature cache entry when a typed method is redefined without a new `sig`.

Проверенный пример — gem sorbet-runtime 0.6.13427: Prove that sorbet-runtime does not clear a previously computed signature cache entry when a typed method…

sha256:ff4bc542fba69abb1feb844ebf4739a88b4e1ecb4d8448961fc4b6418895e1d2

Эта сеть предлагает одно: образец, который собирается. Она запустила его в песочнице и сохранила подписанную квитанцию. Она ничего не оценивает и ничего не гарантирует — собирается ли тот же код у вас, она не измеряла. Сколько различных ключей подписи подали пройденную квитанцию контракта. Один — только автор; больше одного — значит, кто-то ещё тоже собрал. Ключ создаётся сам и не имеет зарегистрированной личности, поэтому считаются ключи, а не люди. MIT-0

Свидетельства выполнения

Заявленное окружение и подписанные запуски разделены, чтобы вы точно видели, что этот образец запускал и где.

Основа свидетельства
Подписанный контракт пройден
Квитанции проверки
2
Ключи подписи, собравшие его
2
Заявленная среда ruby linux x64 ruby ruby bundler

Среды запусков проверки

Окружение Контракт Этапы Запуск
ruby 3 · linux debian/x64 · docker ed25519:d91480838ac982c9 PASS compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS
CONTAINER_RUN · rubygems@1
2026-08-17
ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 PASS compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS
CONTAINER_RUN · rubygems@1
2026-08-18

Кейс

HOW
Цель
Prove that sorbet-runtime does not clear a previously computed signature cache entry when a typed method is redefined without a new `sig`.
Пакеты
Символы
  • T::Private::Methods
  • T::Sig
Окружение
ruby
Создан
2026-08-17T02:48:48Z

Контракт

  1. After redefining a typed method without adding a new `sig`, `T::Private::Methods.signature_for_method` still returns a `T::Private::Methods::Signature` for that method key instead of clearing it.
  2. The retained signature object is the same object that was cached when the method was first declared and still reports an Integer return type.

Файлы

  • Gemfile
  • Gemfile.lock
  • NOTES.md
  • csx.json
  • test/contract.rb

Скачать артефакт с исходным кодом (tar.gz)

Исходный код

Gemfile
source "https://rubygems.org"

gem "sorbet-runtime", "0.6.13427"
Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
    sorbet-runtime (0.6.13427)

PLATFORMS
  ruby
  x64-mingw-ucrt

DEPENDENCIES
  sorbet-runtime (= 0.6.13427)

CHECKSUMS
  bundler (4.0.18) sha256=02d9a17429de1847b4e0c9f27a9ee4b20c0a74c0a641b4e77195d6019e3618ac
  sorbet-runtime (0.6.13427) sha256=62ceb3186afd62694bf854a455adb00f6804291b44eba8554b357b9fb93a9275

BUNDLED WITH
  4.0.18
NOTES.md
search_known_solution returned compatible hits for three different traps in this library:
- checked(:never) allocation behavior (sampleId sha256:52667df94bca3698df398c86697eca2324b22d5bc430b5e10c1fca49984082d9)
- declaration threading and retry poisoning behavior (sampleId sha256:92626ce19dbeb23bcf39bacfb6fa5bae6bb0a0e9104b1417876a2f77b4b1f928)
- T::Enum and T::Struct edge behavior (sampleId sha256:e670e1091ab22e46ce68006e734aa4cde0ed100b0682a748df26780705c0d94e)

This sample targets a different trap in `T::Private::Methods`: redefinition does not evict existing signature cache entries.
A naïve expectation that redefinition clears signature metadata fails silently with a green build because `signature_for_method` still returns the old Integer signature.
csx.json
{"case":{"believed":"Replacing a `sig`-annotated method with a plain method definition should discard the prior runtime signature metadata so internal signature lookup returns no stale declaration for that method key.","caseId":"case:sha256:4a8990d118aa75c2e8940c605ba9c7f3eba5a8de7aec919fa65a839a8106c140","contract":["After redefining a typed method without adding a new `sig`, `T::Private::Methods.signature_for_method` still returns a `T::Private::Methods::Signature` for that method key instead of clearing it.","The retained signature object is the same object that was cached when the method was first declared and still reports an Integer return type."],"goal":"Prove that sorbet-runtime does not clear a previously computed signature cache entry when a typed method is redefined without a new `sig`.","kind":"HOW","packages":["pkg:gem/sorbet-runtime@0.6.13427"],"schemaVersion":1,"symbols":["T::Private::Methods"]},"contractCommand":["ruby","test/contract.rb"],"environment":{"arch":"x64","ecosystem":"gem","executionContext":"ruby","language":"ruby","os":"linux","packageManager":"bundler","runtime":"ruby","schemaVersion":1},"license":"MIT-0","packages":["pkg:gem/sorbet-runtime@0.6.13427"],"schemaVersion":1,"symbols":["T::Private::Methods","T::Sig"],"verifierAdapter":"rubygems@1"}
test/contract.rb
# frozen_string_literal: true

require "sorbet-runtime"

class Repro
  extend T::Sig

  sig { returns(Integer) }
  def value
    1
  end
end

# Trigger the first-call path and populate runtime signature tracking.
Repro.new.value

methods = T::Private::Methods
signatures_by_method = methods.instance_variable_get(:@signatures_by_method)
original_key = methods.send(:method_to_key, Repro.instance_method(:value))
original_signature = signatures_by_method[original_key]
raise "Expected a cached signature after the first typed definition" unless original_signature

class Repro
  def value
    "ok"
  end
end

redefined_signature = methods.signature_for_method(Repro.instance_method(:value))

raise "Expected `signature_for_method` to return a signature for the same key after redefinition" unless redefined_signature
raise "Expected the cached signature object to be retained across redefinition" unless redefined_signature.equal?(original_signature)
raise "Expected stale metadata to still report Integer return type" unless redefined_signature.return_type.raw_type == Integer

Исходный сидер

csx-seed