Edition of Thursday 12 November 2026

A Schema Named Hash Sent Our Ruby SDK into Infinite Recursion

Comments on “A Schema Named Hash Sent Our Ruby SDK into Infinite Recursion”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Emad Khair of octri.dev describes how a test schema named Hash sent the company's generated Ruby SDK into infinite recursion. Inside the SDK's module, Ruby resolved Hash to the generated class rather than the built-in, so a helper never matched real hashes. A 150-name fixture of standard-library types also broke five other languages' builds. The fixes were explicit qualification, renaming models, and keeping separate internal and public names. Reserved-keyword tables were not enough. The account is the team's own, with no outside verification.

Read the original at octri.dev. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 14 of 106 with a score of 0.65. The panel rated it highest on new information (0.89) and technical depth (0.86), lowest on audience breadth (0.48). Placed No. 14, No. 22 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed, concrete engineering write-up on SDK generator naming collisions with reproducible examples across languages; useful to builders of codegen tools, narrower audience, not a landmark.}
AI judgeJudge 3gpt-5.6-luna
A detailed, reproducible engineering account of cross-language SDK naming collisions, with concrete failures, fixes, scope-resolution principles, and regression-testing practices. It is highly actionable for code-generator and SDK developers, though narrower than broad platform news.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.65total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.49
  • Reader interest0.76
  • Audience breadth0.48
  • Practical relevance0.75
  • Substantiated0.82
  • Technical depth0.86
  • New information0.89
  • Counts against: Promotional0.04
  • Counts against: Overclaim0.13

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.550.350.580.490.23+0.24+0.118
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.730.700.860.760.16+0.26+0.198
Audience breadthHow many people who build technology does it concern?0.520.400.520.480.12+0.13+0.063
Practical relevanceHow useful is it to someone who builds software or tech products?0.820.650.780.750.17+0.22+0.165
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.940.700.820.820.24+0.05+0.041
Technical depthHow technically substantive is it?0.990.800.780.860.21+0.05+0.043
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.840.850.990.890.15+0.05+0.045
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.030.050.030.040.02−0.19−0.007
OverclaimDo the headline or conclusions claim more than the body supports?0.190.150.050.130.14−0.11−0.014
Sum of contributions+0.651
Claim-check penalty0.000
Total, as published0.651

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #14 on Rubric, 12 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-12/14/"><img src="https://rubric.hrih.si/badge/2026-11-12/14.svg" alt="Ranked #14 on Rubric, 12 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenNumber

    The generator's test fixture included 150 schemas named after standard-library, framework or runtime types, and a schema named Hash sent the Ruby SDK into infinite recursion.

    The article gives no link or citation for it.

    The article says

    “It was one of 150 standard-library names we had put into a single test document”

    The source says

    No source to compare with.

  2. No source givenGeneralization

    Across the ten target languages, TypeScript, Rust, Kotlin, Python and Go failed type checks or compiles straight away, while Ruby loaded fine and failed at runtime.

    The article gives no link or citation for it.

    The article says

    “TypeScript, Rust, Kotlin, Python and Go failed their type checks or compiles straight away. Ruby loaded fine and failed at runtime instead”

    The source says

    No source to compare with.

  3. No source givenVersion

    On Ruby 3.4.9, the reduced deep_to_h helper raised SystemStackError: stack level too deep when a generated class named Hash existed in the module.

    The article gives no link or citation for it.

    The article says

    “On Ruby 3.4.9, this raised”

    The source says

    No source to compare with.

  4. No source givenCausal conclusion

    Inside module Sdk, Ruby resolves the unqualified constant Hash to the generated Sdk::Hash rather than the built-in ::Hash, so the helper's to_h call recurses forever.

    The article gives no link or citation for it.

    The article says

    “Inside module Sdk, Ruby resolves the unqualified constant Hash to Sdk::Hash”

    The source says

    No source to compare with.

  5. No source givenDate

    The expanded fixture was added on October 3, and it passed in all ten target languages on October 8, five days later.

    The article gives no link or citation for it.

    The article says

    “On October 8, the fixture passed in all ten target languages”

    The source says

    No source to compare with.

  6. No source givenVersion

    With TypeScript 6.0.2, using globalThis.Record lets a generated interface named Record coexist with the built-in utility type Record<string, string>.

    The article gives no link or citation for it.

    The article says

    “We verified the alternative with TypeScript 6.0.2”

    The source says

    No source to compare with.

  7. No source givenCausal conclusion

    Using one naming function for both the Python module-level function and the public client method caused the public method to be renamed to list_(), changing the public API.

    The article gives no link or citation for it.

    The article says

    “Unfortunately, we'd used the same naming logic for the public client method”

    The source says

    No source to compare with.

  8. No source givenGeneralization

    Handling reserved keywords alone is not enough to make generated identifiers safe, because standard-library names that are not keywords also collide.

    The article gives no link or citation for it.

    The article says

    “our assumption that handling reserved keywords was enough to make generated identifiers safe”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 12 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “A Schema Named Hash Sent Our Ruby SDK into Infinite Recursion”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.67

    Semver Trick