-
Notifications
You must be signed in to change notification settings - Fork 0
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
A target's configured values are read by the tests that check them, never written into them
l5Filed by the l5 harnessFiled by the l5 harnessl5-cross-path-parityl5 brief category: cross-path-parityl5 brief category: cross-path-parityStatus: Open.#226 In jerodw/level-five;A merge on this repository closes the brief its story was planned from
l5Filed by the l5 harnessFiled by the l5 harnessl5-featurel5 brief category: featurel5 brief category: featureStatus: Open.#225 In jerodw/level-five;The key the sweep's drift check asks about is the key its transport reads
l5Filed by the l5 harnessFiled by the l5 harnessl5-structural-duplicationl5 brief category: structural-duplicationl5 brief category: structural-duplicationStatus: Open.#223 In jerodw/level-five;A run whose sync command moved says so where a reader of that run will meet it
l5Filed by the l5 harnessFiled by the l5 harnessl5-correctnessl5 brief category: correctnessl5 brief category: correctnessStatus: Open.#222 In jerodw/level-five;One rule decides what may be written after the completion commit, and every post-completion reporter obeys it
l5Filed by the l5 harnessFiled by the l5 harnessl5-cross-path-parityl5 brief category: cross-path-parityl5 brief category: cross-path-parityStatus: Open.#221 In jerodw/level-five;Every statement item_update.py makes about a failed publish says what it leaves on the item
l5Filed by the l5 harnessFiled by the l5 harnessl5-docs-driftl5 brief category: docs-driftl5 brief category: docs-driftStatus: Open.#219 In jerodw/level-five;The item-update contract and its reference implementation agree on what a zero exit claims
l5Filed by the l5 harnessFiled by the l5 harnessl5-cross-path-parityl5 brief category: cross-path-parityl5 brief category: cross-path-parityStatus: Open.#218 In jerodw/level-five;The l5-plan header states the cost of sharing one invocation the way it was realised
l5Filed by the l5 harnessFiled by the l5 harnessl5-docs-driftl5 brief category: docs-driftl5 brief category: docs-driftStatus: Open.#217 In jerodw/level-five;A batched search the tracker does not read as an OR is reported as dedupe not having run
l5Filed by the l5 harnessFiled by the l5 harnessl5-robustnessl5 brief category: robustnessl5 brief category: robustnessStatus: Open.#215 In jerodw/level-five;Every record a post-story inspection writes carries whether dedupe ran
l5Filed by the l5 harnessFiled by the l5 harnessl5-coverage-gapl5 brief category: coverage-gapl5 brief category: coverage-gapStatus: Open.#214 In jerodw/level-five;The filed-query contract tells a script author that one bounded question carries the whole scope
l5Filed by the l5 harnessFiled by the l5 harnessl5-docs-driftl5 brief category: docs-driftl5 brief category: docs-driftStatus: Open.#213 In jerodw/level-five;A status option's name resolves however the board capitalises it
l5Filed by the l5 harnessFiled by the l5 harnessl5-cross-path-parityl5 brief category: cross-path-parityl5 brief category: cross-path-parityStatus: Open.#212 In jerodw/level-five;