Conversation
Co-authored-by: Codex <codex@openai.com>
Fixed NOR extended cache size validation
Co-authored-by: Codex <codex@openai.com>
Invalidate extended cache entries that end exactly at the erased block boundary and cover the last-sector case in the zero-base regression test. Co-authored-by: Codex <codex@openai.com>
Fixed NOR extended cache zero base handling
The per-edit disclosure named the product and model, so every tool and every
model version appended another line rather than recognising the one already
there. Deduplication was by exact string, which a version bump defeats.
Every file now carries exactly one line, fixed text naming no product:
Portions of this file were generated with AI assistance.
written with the comment character that file already uses. Precise attribution
stays on the commit, where the Assisted-by trailer is dated and attached to the
diff it describes. A header line cannot keep that record honest, because the
code it names gets rewritten and the line stays.
Comment-only, 15 files: every removed line was a disclosure line, every added
line is the fixed text, and no file is left with zero or more than one. Nested
repositories were excluded, so no submodule content or gitlink is touched.
Assisted-by: Claude Code (Opus 5) <noreply@anthropic.com>
* Updated LevelX contribution guide for current workflows The existing contributor guide omitted LevelX build, test, and submission practices. The guide now covers C99, pinned dependencies, all ten Linux regression configurations, merged coverage gates, flash hardware verification, attribution, and release practices. Local Markdown links resolve and git diff --check passed. Build tests were not run for this documentation change. Assisted-by: Codex (gpt-6-sol) <noreply@openai.com>
The LevelX README sent readers to archived Markdown documentation. I linked the overview to its published HTML guide and the general documentation entry to the latest release. Both replacement URLs returned HTTP 200; git diff --check passed. Assisted-by: Codex (gpt-6-astra) <noreply@openai.com>
…d form (#87) Nothing enforced the disclosure convention. In the sibling repositories the drift it exists to prevent returned twice, once when a port merged after the normalisation pass carrying the older per-edit form, and once because that pass had covered source files only. This repository is currently clean, and this keeps it so. Added scripts/check_ai_disclosure.sh, which rejects the superseded per-edit form, a doubled comment marker, more than one disclosure line in a file, and any spelling of the line that is not exact. It runs from repo_checks.yml, a workflow with no path filter, because a source-path filter is what hid the build files elsewhere. The check passes on this repository as it stands. Each of its four rules was confirmed to fail on a tree with that defect reintroduced, and to pass once it was removed. Assisted-by: Claude Code (Opus 5) <noreply@anthropic.com>
#86) Running git blame on a file header returns a tree-wide copyright, disclosure or version-constant pass rather than the commit that last touched the code. There have been 4 such passes in this repository since 2024, and every header line in the tree now points at one of them. Added .git-blame-ignore-revs listing those commits. GitHub applies the file to its blame view automatically; locally it takes one git config command, which the file documents in its own header. Additive. No source file is touched, and every listed commit was verified to be an ancestor of dev. Assisted-by: Claude Code (Opus 5) <noreply@anthropic.com>
Regression CI only covered master, fetched moving dependencies, and measured only the default configuration. The legacy collector could select gcov from a different compiler version. Pinned compatible ThreadX and FileX revisions, enabled the dev gate on Ubuntu 24.04 with GCC 14, and merged all ten coverage profiles. Added exhaustive single-bit page ECC tests and coverage-input checks. Enforced measured floors of 68.0% lines and 65.4% branches while retaining uncovered sources. GCC 14 baseline: 30/30 tests, 95.38 seconds summed across configurations. Final matrix: 40/40 tests; complete runner 72.68 seconds. Coverage: 1632/2400 lines and 1596/2439 branches. An injected test failure returned 8 with coverage retained; a missing input returned 1. Empty and unmeasured inputs were rejected. actionlint, ShellCheck and whitespace checks passed. Assisted-by: Codex (GPT-6) <noreply@openai.com>
The mapped-sector initialization fix reached master while dev still used an uninitialized count when obsolete counts came from cache or block metadata. The merge carries the source fix and simulator regression into dev. The cache test keeps dev's existing disclosure comment. GCC 14 CMake/Ninja: 40/40 regression tests passed across ten configurations. Merged coverage reached 1,634/2,402 lines (68.03%) and 1,596/2,439 branches (65.44%). Not run on hardware.
The disclosure check treated any mention of AI assistance as a malformed source comment, so two sentences in CONTRIBUTING.md failed every dev check. Limit the near-miss check to comment lines shaped like a file disclosure. This keeps documentation prose out of the check while retaining typo detection. The check passed on dev content and rejected a malformed disclosure comment. Assisted-by: Codex (GPT-6) <noreply@openai.com>
The branch's repository check failed because the dev script mistook two CONTRIBUTING.md sentences for malformed source comments. Merge the corrected dev check into the NOR fix branch so CI evaluates the current integration state. The check and full regression job passed for the script correction. The NOR fix branch's earlier regression job passed before this merge. Assisted-by: Codex (GPT-6) <noreply@openai.com>
The NOR erase search fix from #83 landed on master while dev still used an uninitialized mapped count when obsolete counts came from cache or block metadata. Merge the master fix and its simulator regression into dev while preserving dev's newer cache tests. Repository checks, ECA, and the full regression job passed on the updated branch. Local GCC 14 CMake/Ninja tests passed 40/40 across ten configurations. Not run on hardware. Assisted-by: Codex (GPT-6) <noreply@openai.com>
On allocation failure, NOR block reclaim compared a null sector address with block pointers before reporting the error; in direct read builds, the old return could also use an uninitialized status. Return LX_SYSTEM_ALLOCATION_FAILED and skip address comparisons when allocation leaves its output null. A regression checks failures on the initial allocation and retry in buffered and direct read builds. Thanks to @jiri-novotny for identifying the status defect in #21. GCC 14 CMake/Ninja tests passed 50/50 across ten configurations with #83 on dev. Merged coverage reached 1,646/2,404 lines (68.47%) and 1,614/2,451 branches (65.85%). GitHub repository checks, ECA, and the full regression job passed. Not run on hardware. Assisted-by: Codex (GPT-6) <noreply@openai.com>
prepare_release.sh committed the version passes with a Co-authored-by trailer naming an AI. That trailer asserts authorship an AI cannot hold: the human contributor signs the ECA and is solely responsible for the contribution. It is already in the published history, on the 6.5.1.202602 version pass. The commit now carries its subject alone. A version pass is mechanical sed output, so no agent produces it at run time; an agent that runs the script records its own Assisted-by trailer on that run instead. The script also gains the AI disclosure line it was missing. Ran the patched script against a scratch clone targeting 6.5.2.202603. The commit comes out with an empty trailer block, and the version constants update as before. Assisted-by: Claude Code (Opus 5) <noreply@anthropic.com>
Test Results50 tests 50 ✅ 14m 13s ⏱️ Results for commit 1b24479. ♻️ This comment has been updated with latest results. |
Minimum allowed line rate is |
This branch has not been deployed
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
2 participants
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.
No description provided.