docs(backlog): fix stale error() level wording in backlog index - #142
Merged
Conversation
… index entry The index line still described error(msg, 3); the fix landed as error(msg, 0) after review remediation on PR #141 (tail calls break a fixed stack level in Lua 5.1).
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates the backlog index documentation for FIX-CONFIG-NOT-LOADED-GUARD to match the merged implementation, changing the stale File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
davidp57
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.backlog/README.mdindex entry forFIX-CONFIG-NOT-LOADED-GUARDstill described the guard as usingerror(msg, 3). That was the initial implementation, but review remediation on PR fix(config): refuse getSetting() before ctld.initialize(), clearly #141 changed it toerror(msg, 0)(message-only) because a fixed stack level breaks for real tail-call call sites in Lua 5.1.Test plan
Summary by Sourcery
Documentation: