[brettheap]

Lane: openreposhape-5 (openRepoShape-5)
Claim: #692 (comment)

What changed and why

#622's folder refusals printed a path as it was. family.py init --into <a file named wd-ESC[31mRED> --dry-run gave REFUSED family-folder-cannot-be-made: the family folder .../wd-^[[31mRED/Orbit cannot be made: ... through cat -v. A name with a line break and then WARNING forged-line: pwned printed that line as a line of its own. R612's family-operation-in-progress printed the mark's path across two lines for a holder whose path holds a newline.

Each path is now spelled as shape_materialize.shown_source spells a --pin-source: as it is, and as Python's repr spells it where a character in it is not printable.

• scripts/shape_materialize.py: both answers of folder_cannot_be_made (a file or a bad stat in the way, and a folder this user cannot write in), the folder in refuse_unmakeable_folder, and the folder in make_folder.
• scaffold-project.py: scaffold-target-exists.
• scripts/family.py: family-target-exists, and the mark's path in family-operation-in-progress (where.as_posix()).

A printable path is named byte for byte, so no existing row changes and why.endswith(CANNOT_WRITE_IN) in refuse_unmakeable_folder still holds. No help text changed, so docs/cli.md is untouched. No README, handbook or template sentence says how a refusal names a path (git grep of shown_source, target-exists and folder-cannot-be-made in AGENTS.md, README.md, docs/handbook.html and the templates found none), so no doc changes.

Decisions and their evidence

• shown_source, not shown_path. Since Pinned shape copies: one bump, so AGENTS-shape.md is true of every root, the scaffold's chain WARNING offers only its own sources and spells --pin-source, the root's not-used note spells it too, and THE LOCKSTEP RULE's bump runs (#610) #634, shape_materialize.shown_source returns repo_shape.shown_path(source) (scripts/shape_materialize.py: return shown_path(source)), so the seven call sites this change adds (four in shape_materialize.py, one in scaffold-project.py and two in family.py) spell a path as shown_path does. Renaming them to shown_path stays out of this PR: it would only move imports in scaffold-project.py and family.py and reword docstrings in family.py, shape_materialize.py and the test file, and the review's N1 left it optional. I did not take it. The predicted merge with main works with the alias: family.py --help and scaffold-project.py --help exit 0 on it, and shown_source and shown_path return the same string for an ESC name, a line-break name and a plain path.
• shown_source is imported by name into each file's existing from shape_materialize import (...) block. The first commit put it on a line of its own after the block; lane 4's the Free-plan hint's reads: a public reused holder gets the "private" NOTE and hint, an unread root is taken as the run's visibility, and an unread plan is silent #660, family.py init: --created-by and GIT_AUTHOR_NAME are never asked whether the manifest can hold them, a whitespace-only GIT_AUTHOR_NAME fails after the remote exists, and a --family a Windows disk cannot hold exactly is accepted #688 and --local-remote-dir: family.py add takes a directory whose name is not UTF-8 into .gitmodules, the clone-URL refusal's remedy misses a link's target and a lone surrogate, and the READMEs' clone line is rendered unquoted #693 add an import at that same place, and merge-tree reported add/add conflicts in scripts/family.py and scaffold-project.py. The second commit moves the name into the block, and those conflicts are gone.
• "The holder in the other refusals of the same block" is one refusal. The # What the holder is in the middle of, and what its sparse checkout leaves out block holds family-operation-in-progress, family-sparse-excluded and member-path-unaddable. Only the first prints a path of the holder's. family-sparse-excluded names members/<Project> and .gitmodules, and member-path-unaddable names members/<Project>.
• No scaffold row for --local-remote-dir. A control character there is refused earlier as scaffold-unwritable-value, which already names the path with repr. The unit test covers make_folder, which only a race reaches by the command line.

Tests

tests/test_dry_run_parity.py:

• SCAFFOLD_CASES gains five rows: ESC and line break in the --work-dir name, ESC in a folder name above it, and ESC and line break in a work dir that holds a file named Atlas (scaffold-target-exists).
• FAMILY_CASES gains five rows: ESC and line break in --work-dir, ESC in --into (the family folder), and ESC and line break in a work dir that holds a file named Orbit (family-target-exists).
• Two rows join UNWRITABLE_FOLDER_AT (ESC in the scaffold's and in init's --work-dir, a folder this user cannot write in).
• Rows named ESC-... and line-break-... are skipped on Windows, whose file names cannot hold them (POSIX_NAMES, case_params). Every expectation spells the path with repr, and not with shown_source.
• assert_refused now fails any stderr line that starts with WARNING forged-line.
• Three unit tests: test_each_folder_question_spells_a_name_that_is_not_printable (ESC, line break; folder_cannot_be_made, refuse_unmakeable_folder and make_folder by themselves), test_a_folder_this_user_cannot_write_in_is_spelled_safe_to_show, and test_a_printable_name_is_named_byte_for_byte (a name with a space and an accented letter stays unquoted).

tests/test_family_refuse_up_front.py: test_a_holder_path_with_a_newline_still_shows_its_merge asserted the raw newline in the refusal ("Ink\nRouter/.git/worktrees/" in ran.stderr). It is now test_a_holder_path_with_a_control_character_still_shows_its_merge, over a line break, an ESC and a forged line, and asserts the one-line repr form (refusal() fails unless the stderr is two lines). It is the one existing test this change had to edit.

Results at head ab55c29f (Python 3.12.3, Linux):

• tests/test_dry_run_parity.py tests/test_dry_run_asks_remotes.py tests/test_family_dry_run.py tests/test_family_init_landing.py tests/test_repo_hygiene.py tests/test_pin_source_unreadable.py tests/test_scaffold_leg_path_collisions.py tests/test_scaffold_reuse_seeded_legs.py: 494 passed.
• tests/test_family.py tests/test_family_refuse_up_front.py tests/test_family_init_values.py tests/test_family_add_refusals.py: 356 passed, 19 skipped (the skips are test_family_init_values.py:219 and :291, template-quoting premises).
• Not run: the full suite (the coordinator's gate), and macOS and Windows (CI is Linux-only since ci: run the test suite on Linux only #597). The new hostile-name rows are POSIX only by design.

On the base code: the review overlaid this head's two test files on main 2fac9790 and ran tests/test_dry_run_parity.py and tests/test_family_refuse_up_front.py with -k "dry_run_parity or control_character". The result is 20 failed, 87 passed (76 deselected, 43.5 s). The 20 are exactly the new and edited tests: the 5 scaffold and 5 init rows, the 4 unwritable-folder rows, the 3 unit tests (test_each_folder_question_spells_a_name_that_is_not_printable in two cases, and test_a_folder_this_user_cannot_write_in_is_spelled_safe_to_show), and the 3 cases of the edited test_a_holder_path_with_a_control_character_still_shows_its_merge. The one new test that passes on main's code is test_a_printable_name_is_named_byte_for_byte, by design: a printable name is named byte for byte on both. An earlier draft of this body said 21 failed, 2 passed. That run was on 8062810d with a wider selection, and it held a scaffold row for ESC in the local remote dir's name (ESC-in-the-local-remote-dir-name) that this head's tests no longer have; its second pass was the existing test_the_refusal_quotes_gh_s_first_line_and_escapes_what_is_unprintable, which also passes in the new run, one of the 87.

Reproduction

family.py init and scaffold-project.py --dry-run against a file named wd-ESC[31mRED, a file named wd-\nWARNING forged-line: pwned, and a work dir with a file Atlas or Orbit in it, run with a stub gh and no real gh:

• On main, through cat -v: ... the family folder /.../wd-^[[31mRED/Orbit cannot be made: /.../wd-^[[31mRED is a file, not a folder, and a stderr line WARNING forged-line: pwned cannot be made: ... of its own.
• On this head: REFUSED family-folder-cannot-be-made: the family folder '.../wd-\x1b[31mRED/Orbit' cannot be made: '.../wd-\x1b[31mRED' is a file, not a folder, and one line for the forged name: --work-dir '.../wd-\nWARNING forged-line: pwned' cannot be made: '...' is a file, not a folder. scaffold-target-exists and family-target-exists are one line each in the same form.

Mutation probes

Each spelled site reverted alone in a throwaway clone at 19d126cd (the call sites are the same at ab55c29f); the new tests that fail for each:

• folder_cannot_be_made, the _not_a_folder answer: 8 failed (six CLI rows and the two unit tests).
• folder_cannot_be_made, the CANNOT_WRITE_IN answer: 5 failed (the four unwritable rows and the unit test).
• refuse_unmakeable_folder: 12 failed.
• make_folder: 2 failed (the unit test only).
• scaffold-target-exists: 2 failed (its two rows).
• family-target-exists: 2 failed (its two rows).
• family-operation-in-progress: 3 failed (line break, ESC, forged line).

Merge checks

git merge-tree --write-tree of this head ab55c29f against origin/main 20c8873b and against every ref on origin that could meet it, fetched 2026-10-16: the 41 branches (fix/*, l3-*, wip/*, docs/* and release/v1.0) and the 55 PR heads from #630 up. That is 96 refs. (The same list was run for #730's head 7f2bb36b.)

• origin/main 20c8873b: clean (the predicted tree 00b5b24c, which differs from main in these five files only: 216 lines added, 25 removed).
• README, AGENTS.md, docs/cli.md and the handbook: pipx install openreposhape is the second way in and the first on native Windows, git-filter-repo is installed in install.sh's order and never with a bare pip install, and a first draft of the v1.1.0 release notes (#563) #630's head 6fd33a93: clean. It conflicted with main in docs/handbook.html when this body was first drafted, and no longer does, with or without this change. This change touches no README or handbook.
• The refs that edit one of this change's five files, and so could meet it, all merge clean with this head: fix/646, fix/651, fix/654, fix/660, fix/661, fix/684, fix/686, fix/688, fix/689 and fix/693, the heads of family.py: add's refusal of a member's own gitlink held only under another spelling of its row's path moves it back to that path in the index alone, so the printed remedy no longer takes the member's gitlink away from its row (#646) #670, adopt-project.py and scaffold-project.py: a --pin naming an annotated tag's own id pins the commit the tag names, and one naming a tree or a blob is refused, so a pin file no longer records a tag's id under "A COMMIT, NEVER A TAG" (#651) #725, scaffold-project.py, adopt-project.py and family.py: the Free-plan secrets hint goes by what GitHub says of the root or holder and of its organisation's plan, and names the answer GitHub did not give, so init --reuse-empty-repo no longer calls a public holder private, an unread root is not taken as the run's visibility, and an unread plan is not silent #728, adopt-project.py: check asks this machine's git what the split stores for each file the plan keeps or moves and each pinned copy, so one it would store as other bytes no longer passes check and fails after both legs exist (#654) #743 and validate-manifest.py, the naming gate and setup-project.py: a chain link no tree answers for is offered what each caller reads, so the root's validator and setup's step (4) no longer offer --link-source, which neither takes, and the gate spells every --link-source value and path it prints #744, and the heads of the landed Pinned shape copies: one bump, so AGENTS-shape.md is true of every root, the scaffold's chain WARNING offers only its own sources and spells --pin-source, the root's not-used note spells it too, and THE LOCKSTEP RULE's bump runs (#610) #634, repo_shape.py and validate-repository-naming.py: a chain link, a declared pin and a --link-source key are one product by pin_product_key, the pin file's own fold, so a tree declaring openss no longer verifies a chain that says openß, a chain naming both is two links and not a cycle, and --link-source openss= no longer answers for openß (#444) #638, validate-family.py and family.py: a gitlink no section of HEAD's .gitmodules gives is member-gitmodules-absent, remove refuses a holder with no .gitmodules before deinit, and two gitlink remedies name what they missed (#611) #639, scaffold-project.py and family.py: a --local-remote-dir whose clone URL is not text a README can hold is refused before any remote or folder exists, --dry-run alike, so a directory named in a legacy code page no longer ends in a UnicodeEncodeError traceback after the bare remotes are made (#433) #640, scaffold-project.py and family.py: the tracking branch is pushed by its full refname, so --tracking-branch +x scaffolds and initialises instead of dying at the push after every remote exists (#421) #643 and scaffold-project.py and family.py: scaffold-bad-id and family-bad-id name an id derived from --project or --family as derived and say to change that flag, so --project North_Wind no longer says --id 'north_wind' must match and sends the person to an --id the naming policy then refuses (#659) #671. Pinned shape copies: one bump, so AGENTS-shape.md is true of every root, the scaffold's chain WARNING offers only its own sources and spells --pin-source, the root's not-used note spells it too, and THE LOCKSTEP RULE's bump runs (#610) #634 has landed (30676c90), so the fix/660 note about a conflict with it is gone.
• Four refs conflict with origin/main on their own, and so with this head: docs/release-notes-v1.0.0 and release/v1.0, and the pre-squash heads of the landed family.py and validate-family.py: where an earlier act left the branch, the switch -c remedy says to give it another name, or go back only if it holds work not merged yet, and the docs say family/add-<Project> (#607) #637 and bump-leg.py, scaffold-project.py and family.py: git status --porcelain and git config user.name are read as bytes, so a file name that is not UTF-8 is bump-leg-root-dirty or the DIRTY warning and a user.name that is not UTF-8 is refused family-unwritable-value naming --created-by, where each ended in a UnicodeDecodeError traceback (#423, #426) #641. Their conflicts do not come from this change. Every other ref, 92 of the 96 in all, is clean with this head, including the refs that conflict with main in templates/family-root/scripts/validate-family.py (bootstrap.py and validate-family.py: a member no credential would check out fails the family bootstrap, every row's gitlink is asked before any checkout, and --no-members prints the case-variant move (#648) #682, bootstrap.py and AGENTS-shape.md: a leg with an operation in progress or an ignored file in the way is refused, P9 names the branch it left, and no git is git-not-runnable, so make bootstrap loses nothing (#704) (#694) #745, validate-family.py and validate-pins.py: a staged gitlink removal says to commit it, member-gitlink-absent puts the gitlink back by hand, the variant mv is guarded, and a pin row with no path: is shape-pin-row (#681) #747, fix/648, fix/681, fix/704) or in shape-doctor.py (shape-doctor.py and update-shape.py: run from a partial clone of the standard, the shape currency row asks without fetching whether the clone holds what the comparison reads, and is CANNOT ANSWER with a fetch for a person to run where it does not, and a read that fails is refused, never a copy called both (#683) #742, l3-683) on their own. So do the old heads of the landed repo_shape.py and validate-repository-naming.py: a chain link, a declared pin and a --link-source key are one product by pin_product_key, the pin file's own fold, so a tree declaring openss no longer verifies a chain that says openß, a chain naming both is two links and not a cycle, and --link-source openss= no longer answers for openß (#444) #638 and validate-family.py and family.py: a gitlink no section of HEAD's .gitmodules gives is member-gitmodules-absent, remove refuses a holder with no .gitmodules before deinit, and two gitlink remedies name what they missed (#611) #639, and lane 3's l3-677-pins-hand-step-wip branch, and each of them merges clean with this head too.
• Tests on the predicted merge, run by the review on the merge with main 2fac9790: test_dry_run_parity, test_family_refuse_up_front, test_pinned_copy_text, test_pin_source_unreadable, test_dry_run_asks_remotes, test_family_dry_run and test_family_init_landing: 445 passed in 215 s. test_family, test_family_init_values, test_family_add_refusals, test_derived_id_refusals, test_repo_hygiene, test_naming_policy, test_scaffold_leg_path_collisions and test_scaffold_reuse_seeded_legs: 758 passed, 19 skipped in 243 s. I did not re-run them on 20c8873b; the merge is clean, and the two commits since 2fac9790 (shape-doctor.py: submodule_config and gitmodules_entry read a holder's .gitmodules through one git config -z --list, so a section name holding a space or a byte that is not UTF-8, or a url holding NEL or U+2028, gives the doctor the mount url git and make siblings use, under any locale (#668) #700 and validate-pins.py and shape-doctor.py: one leg's gitlink off its pin beside another leg's digest or workflow reference names the step that comes first, that gitlink put back by hand, and then the other leg's bump-leg.py line, so neither finding says "First clear that finding" over a finding no line can clear first (#677) #702) change only shape-doctor.py, templates/assembly-root/scripts/validate-pins.py and four test files, none of them a file of this change.
• Before the second commit, fix/660, fix/688 and fix/693 each conflicted with this head in the import region of scripts/family.py or scaffold-project.py (a separate import line each side added at the same place). That is why the import joins the existing block.

#634 is on main, and this change does not edit shown_source or its docstring in scripts/shape_materialize.py.

Review

The review approved with nits. Its S1, the stale base-run numbers and merge lines, is taken here, in this body: no code changed, and the head is still ab55c29f. Its N1, renaming the call sites to shown_path, is not taken (see "Decisions and their evidence"). It also re-ran 5 of the 7 mutation probes on ab55c29f and got the same failure counts as above (12, 2, 3, 2 and 2), and ran 144 hostile-name dry runs (16 names in 9 scenarios): on main 69 rows put a control character on stderr and 6 print a forged line of their own; on this head all 144 exit 2 with no traceback, no control character and no forged line.

Left out, and why

• scripts/family.py init's plan prints folder and landing lines with the path raw (print(f"landing {holder} ..."), print(f"folder {folder} ...")). On a dry run or a refused run the plan is on stdout before the refusal, so WARNING forged-line: pwned/Orbit (--work-dir: no family folder) still appears there. It is the plan, not a refusal, and not one of the issue's lines.
• Other refusals that name a holder or folder path raw, none of them in the issue's lines: family-holder-detached and family-on-tracking-branch ({family.root}), family-index-locked (lock.as_posix() in the detail), family-landing-in-standard ({holder}, {checkout}, {beside / family / family}), family-holder-already-here ({into}), and family-remote-exists and scaffold-remote-exists ({target}, a local remote path).

Checklist candidates

1. family.py init's plan prints the holder and folder paths raw. scripts/family.py landing and folder rows (about :1756-1759) print holder and folder as they are, so a forged line or an ESC reaches stdout in a --dry-run and in a run refused after the plan. Direction: spell them with shown_source.
2. The same raw spelling in the refusals listed above. family-holder-detached, family-on-tracking-branch, family-index-locked, family-landing-in-standard, family-holder-already-here, family-remote-exists and scaffold-remote-exists each print a path the person supplied or git keeps. Direction: the spelling this change gives its sites.

Closes #692

🤖 Generated with Claude Code

Summary by Sourcery

Prevent control characters and line breaks in user-controlled paths from reaching refusal output unsafely.

Bug Fixes:

• Safely escape non-printable characters in paths shown by folder, scaffold, and family-operation refusals so terminal control sequences and forged lines cannot be injected into output.

Enhancements:

• Preserve byte-for-byte rendering for printable paths while standardizing safe path presentation across affected refusal messages.

Tests:

• Add POSIX-focused coverage for ESC, newline, and forged-line path names across scaffold, family, folder-creation, and operation-in-progress refusals.

[brettheap]

(lane openRepoShape-5, 2026-10-16T17:23Z) @codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-16T17:27:17.172146Z	ab55c29	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[sourcery-ai]

Reviewer's Guide

The PR makes selected scaffold and family refusal paths terminal-safe by applying shown_source, preventing ESC sequences and embedded newlines from altering output, and adds focused POSIX regression tests while preserving existing printable path output.

Sequence diagram for terminal-safe path refusal

sequenceDiagram
    participant CLI
    participant Command
    participant Materializer
    participant Refusal

    CLI->>Command: run scaffold or family operation
    Command->>Materializer: folder_cannot_be_made(path)
    Materializer-->>Command: shown_source(path) plus reason
    Command->>Refusal: raise refusal with shown_source(path)
    Refusal-->>CLI: one-line terminal-safe stderr

    alt existing target
        Command->>Refusal: scaffold-target-exists or family-target-exists
        Refusal-->>CLI: shown_source(target) already exists
    else operation in progress
        Command->>Refusal: family-operation-in-progress
        Refusal-->>CLI: shown_source(where.as_posix())
    end

Loading

Flow diagram for terminal-safe folder refusal paths

flowchart TD
    A[Path supplied to scaffold or family operation] --> B{Path is printable?}
    B -->|Yes| C[shown_source returns path byte for byte]
    B -->|No| D[shown_source uses Python repr escaping]
    C --> E[Refusal message]
    D --> E
    E --> F[Single-line safe stderr output]

Loading

File-Level Changes

Change	Details	Files
Escape control characters in refusal messages by consistently using shown_source for paths.	Updated folder creation and writability refusals to safely render paths while preserving printable output and existing remediation checks. Updated scaffold and family target-exists refusals to use safe path rendering. Updated the in-progress family operation refusal to render the Git worktree path on one terminal-safe line.	scripts/shape_materialize.py scaffold-project.py scripts/family.py
Expand regression coverage for hostile path names and preserve byte-for-byte rendering of printable names.	Added POSIX-only ESC, newline, and forged-line cases across scaffold, family, target-exists, unwritable-folder, and folder-creation paths. Added assertions preventing forged warning lines and verifying one-line repr-style operation-in-progress output. Retained coverage that printable paths, including spaces and accented characters, remain unchanged.	tests/test_dry_run_parity.py tests/test_family_refuse_up_front.py

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#692	Spell every path named by the #622 folder refusals safely, including paths in folder feasibility checks, folder-creation failures, scaffold target-exists refusals, and family target-exists refusals.	✅
#692	Spell the holder path in the family-operation-in-progress refusal safely so control characters cannot reach the terminal or create additional lines.	✅

Possibly linked issues

• scaffold-project.py and family.py: both runs ask whether each folder they make can be made and take only gh's not-found answer as "absent", so --dry-run refuses a file where a folder goes, or a gh repo view that fails otherwise, by name as the real run does, and a refused init leaves no empty family folder (#609) #622: The PR uses shown_source for the issue’s folder-refusal paths and operation-in-progress holder path, preventing raw ESC and newline output.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Nice work!

Reviewed commit: ab55c29f52

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sourcery-ai]

Sorry @brettheap, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 7 hours and 35 minutes by commenting @sourcery-ai review. Upgrade to get a review now.