WIP: fix(vk): cut a texture cache far over the VRAM rules to 7/8 of their budget #519

Draft
Amateurwizrd wants to merge 1 commit from Amateurwizrd/Longshot:fix/vram-excess-cut into main
Contributor

Type: fix · Risk: low · Tested on: Windows 11, RTX 5070 Ti 16 GB (game-free) · Needs: a 10 GB card, Linux

Why

When an area keeps the texture cache far over the 90% rule's or the driver's limit, the rules let go of only the excess
and 64 MB more, so the cache sits at the line and every pass is another eviction, with what went uploaded again: a
stutter that does not stop while the player stays there. Searched the tracker: no issue covers it.

How to reproduce

Seen on: the game-free check below, Windows 11, RTX 5070 Ti, driver 621.01; in the game it was reported in Hookshot-old (030b4e9a) for Lake Hylia on a 10 GB card, 383 MB over at each pass, and not reproduced here (a 16 GB card never got that far over the line)
Settings and switches: defaults
Steps: run tests/test_vram_compact.py (this PR's cases) against main's gpu/vk/vram_compact.h; in the game, a 10 GB card at Lake Hylia for a few minutes
Expected: a 383 MB excess over a 3639 MB rule budget cuts the cache to 7/8 of that budget, and the eviction lines stop repeating
Actual: the excess and 64 MB more go, the cache stays at the line, and each pass evicts again

What changed

A cache only a little over the line is still trimmed by the excess, as now; one far over it (more than a sixteenth of
the rule's budget) is cut to 7/8 of that budget at once, so the passes stop evicting again and again.

  • vk: vram_compact::rule_target in gpu/vk/vram_compact.h keeps the trim for an excess of up to a sixteenth of the
    rule's budget (kExcessSmall), so a cache a few MB over the line still does not lose an eighth of its textures; a
    larger excess is cut to 7/8 of that budget, as before the trim. The budget's own size still asks for its 7/8, and
    RX_VK_EVICT_EXCESS=0 (the cut on any excess) is unchanged.
  • tests: tests/test_vram_compact.cpp checks the large excess, a grid of budgets and excesses around the edge, and a
    zero budget.
  • docs: docs/development.md's RX_VK_EVICT_EXCESS row says what the default does now.

The rule was first seen in Hookshot-old's 030b4e9a; the code and the edge cases are written for Longshot.

Measurements

Verdict: it passes: the new check fails on main @ 13e8b6da in both runs and passes on this PR @ cc6a0eaf in both.

Hardware: Windows 11 Pro 26200, RTX 5070 Ti 16 GB, driver 621.01, Ryzen 7 7800X3D, 32 GB
Scene: none (game-free check)
Method: the new test cases, run 2 times on each side, interleaved (main, this PR, main, this PR); main gets this PR's tests/test_vram_compact.cpp with kExcessSmall written as its value, 16, since main has no such constant
How to reproduce: python -I -B tests/run_all.py vram_compact on this branch, and on main with the test file copied in and b / kExcessSmall replaced by b / 16

Before: main @ 13e8b6da After: this PR @ cc6a0eaf
tests/test_vram_compact.py (run 1 / run 2) FAIL / FAIL pass / pass

Flags and settings

No new switch; the documented default of the existing RX_VK_EVICT_EXCESS changes.

Flag What it is Before this PR After this PR Effect Helps / doesn't help / untested Recommendation
RX_VK_EVICT_EXCESS=0 The rules cut to 7/8 on any excess, as before the trim unset: every excess trimmed by itself and 64 MB unset: an excess up to 1/16 of the budget trimmed, a larger one cut to 7/8 a cache far over the line is cut once instead of evicting every pass helps caches far over the line on short cards; caches a few MB over unchanged; untested in the game on 8 and 10 GB cards keep unset

Testing

Tested: on Windows 11 with the pinned llvm-mingw, the 3 checks that read this diff, one at a time, on this PR @ cc6a0eaf (main @ 13e8b6da): 3 pass; none fails here that passes on main. The renderer was not built at this head.

Not tested: the game on a card whose cache goes far over the line (a 16 GB card never got there in the scenes
tried).

Must be tested:

  • Windows, a 10 GB NVIDIA or AMD card: Lake Hylia for a few minutes on main and on this PR, expecting the eviction lines in longshot_log.txt to stop repeating each pass once the cache is cut on this PR, where main evicts again each pass (Test Farm: @Beanstalk windows, a 10 GB card)
  • Linux (Test Farm: @Beanstalk linux, build the renderer): the renderer builds with this PR, expecting no error in gpu/vk/vram_compact.h

Risks

What could break: a cache far over the line loses an eighth of its textures at once again, as before the trim:
one larger burst of uploads instead of an eviction every pass.

Turning it off: RX_VK_EVICT_EXCESS=0 cuts on any excess; reverting the commit restores the trim for every excess.

Compatibility: Nothing changes.

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why. Not ticked yet: Testing says game-free checks only, and the game was not run on a card whose cache goes far over the line.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks. Not ticked yet: Risks names a larger one-time burst of uploads, and the 8 and 10 GB cards are not measured in the game.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value.
  • A game-free test added for the fix, failing on main and passing here.
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. (Windows here; Linux is in Must be tested)
  • Docs updated.
**Type:** fix · **Risk:** low · **Tested on:** Windows 11, RTX 5070 Ti 16 GB (game-free) · **Needs:** a 10 GB card, Linux ## Why When an area keeps the texture cache far over the 90% rule's or the driver's limit, the rules let go of only the excess and 64 MB more, so the cache sits at the line and every pass is another eviction, with what went uploaded again: a stutter that does not stop while the player stays there. Searched the tracker: no issue covers it. ## How to reproduce **Seen on:** the game-free check below, Windows 11, RTX 5070 Ti, driver 621.01; in the game it was reported in Hookshot-old (030b4e9a) for Lake Hylia on a 10 GB card, 383 MB over at each pass, and not reproduced here (a 16 GB card never got that far over the line) **Settings and switches:** defaults **Steps:** run `tests/test_vram_compact.py` (this PR's cases) against main's `gpu/vk/vram_compact.h`; in the game, a 10 GB card at Lake Hylia for a few minutes **Expected:** a 383 MB excess over a 3639 MB rule budget cuts the cache to 7/8 of that budget, and the eviction lines stop repeating **Actual:** the excess and 64 MB more go, the cache stays at the line, and each pass evicts again ## What changed A cache only a little over the line is still trimmed by the excess, as now; one far over it (more than a sixteenth of the rule's budget) is cut to 7/8 of that budget at once, so the passes stop evicting again and again. - vk: `vram_compact::rule_target` in `gpu/vk/vram_compact.h` keeps the trim for an excess of up to a sixteenth of the rule's budget (`kExcessSmall`), so a cache a few MB over the line still does not lose an eighth of its textures; a larger excess is cut to 7/8 of that budget, as before the trim. The budget's own size still asks for its 7/8, and `RX_VK_EVICT_EXCESS=0` (the cut on any excess) is unchanged. - tests: `tests/test_vram_compact.cpp` checks the large excess, a grid of budgets and excesses around the edge, and a zero budget. - docs: `docs/development.md`'s `RX_VK_EVICT_EXCESS` row says what the default does now. The rule was first seen in Hookshot-old's 030b4e9a; the code and the edge cases are written for Longshot. ## Measurements **Verdict:** it passes: the new check fails on main @ 13e8b6da in both runs and passes on this PR @ cc6a0eaf in both. Hardware: Windows 11 Pro 26200, RTX 5070 Ti 16 GB, driver 621.01, Ryzen 7 7800X3D, 32 GB Scene: none (game-free check) Method: the new test cases, run 2 times on each side, interleaved (main, this PR, main, this PR); main gets this PR's `tests/test_vram_compact.cpp` with `kExcessSmall` written as its value, 16, since main has no such constant How to reproduce: `python -I -B tests/run_all.py vram_compact` on this branch, and on main with the test file copied in and `b / kExcessSmall` replaced by `b / 16` | | Before: main @ 13e8b6da | After: this PR @ cc6a0eaf | |---|---|---| | `tests/test_vram_compact.py` (run 1 / run 2) | FAIL / FAIL | pass / pass | ### Flags and settings No new switch; the documented default of the existing `RX_VK_EVICT_EXCESS` changes. | Flag | What it is | Before this PR | After this PR | Effect | Helps / doesn't help / untested | Recommendation | |---|---|---|---|---|---|---| | `RX_VK_EVICT_EXCESS=0` | The rules cut to 7/8 on any excess, as before the trim | unset: every excess trimmed by itself and 64 MB | unset: an excess up to 1/16 of the budget trimmed, a larger one cut to 7/8 | a cache far over the line is cut once instead of evicting every pass | helps caches far over the line on short cards; caches a few MB over unchanged; untested in the game on 8 and 10 GB cards | keep unset | ## Testing **Tested:** on Windows 11 with the pinned llvm-mingw, the 3 checks that read this diff, one at a time, on this PR @ cc6a0eaf (main @ 13e8b6da): 3 pass; none fails here that passes on main. The renderer was not built at this head. **Not tested:** the game on a card whose cache goes far over the line (a 16 GB card never got there in the scenes tried). **Must be tested:** - Windows, a 10 GB NVIDIA or AMD card: Lake Hylia for a few minutes on main and on this PR, expecting the eviction lines in `longshot_log.txt` to stop repeating each pass once the cache is cut on this PR, where main evicts again each pass (Test Farm: @Beanstalk windows, a 10 GB card) - Linux (Test Farm: @Beanstalk linux, build the renderer): the renderer builds with this PR, expecting no error in `gpu/vk/vram_compact.h` ## Risks **What could break:** a cache far over the line loses an eighth of its textures at once again, as before the trim: one larger burst of uploads instead of an eviction every pass. **Turning it off:** `RX_VK_EVICT_EXCESS=0` cuts on any excess; reverting the commit restores the trim for every excess. **Compatibility:** Nothing changes. ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [ ] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. Not ticked yet: Testing says game-free checks only, and the game was not run on a card whose cache goes far over the line. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [ ] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. Not ticked yet: Risks names a larger one-time burst of uploads, and the 8 and 10 GB cards are not measured in the game. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value. - [x] A game-free test added for the fix, failing on `main` and passing here. - [ ] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. (Windows here; Linux is in Must be tested) - [x] Docs updated.
HumanBean force-pushed fix/vram-excess-cut from bf3637f22e
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 4s
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
to 4a39da2cde
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 4s
CI / Conventional Commit title (pull_request) Successful in 2s
CI / Workflow lint (actionlint) (pull_request) Successful in 5s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 6s
Third-party parts / As their notes say (pull_request) Successful in 8s
Website / Website on Cloudflare (pull_request_target) Has been skipped
2026-11-15 18:43:35 +00:00
Compare
Owner

Rebased onto main @ bbe6fdf2. No tests were run here; the test boxes stay yours. One conflict in docs/development.md: main rewrote the commit-reserve rows next to the RX_VK_EVICT_EXCESS row, so main's rows are kept and only the RX_VK_EVICT_EXCESS text is this PR's.

Rebased onto `main` @ bbe6fdf2. No tests were run here; the test boxes stay yours. One conflict in docs/development.md: main rewrote the commit-reserve rows next to the `RX_VK_EVICT_EXCESS` row, so main's rows are kept and only the `RX_VK_EVICT_EXCESS` text is this PR's.
Amateurwizrd force-pushed fix/vram-excess-cut from 4a39da2cde
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 4s
CI / Conventional Commit title (pull_request) Successful in 2s
CI / Workflow lint (actionlint) (pull_request) Successful in 5s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 6s
Third-party parts / As their notes say (pull_request) Successful in 8s
Website / Website on Cloudflare (pull_request_target) Has been skipped
to cc6a0eafe4
Some checks failed
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval waiting for a BigBean's 👍 on the request
PR description / Description follows the template (pull_request_target) Successful in 4s
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
Website / Website on Cloudflare (pull_request) Has been cancelled
2026-11-15 21:11:42 +00:00
Compare
Author
Contributor

Rebased onto main @ 13e8b6da (cc6a0eaf); one conflict in docs/development.md, where main had reverted the RX_VK_EVICT_BY_PRESENTS row: only this PR's RX_VK_EVICT_EXCESS row is kept. Re-measured on this main and the description moved to the current template: the new cases fail on main twice and pass here twice; the 3 checks that read this diff pass.

Rebased onto main @ 13e8b6da (cc6a0eaf); one conflict in `docs/development.md`, where main had reverted the `RX_VK_EVICT_BY_PRESENTS` row: only this PR's `RX_VK_EVICT_EXCESS` row is kept. Re-measured on this main and the description moved to the current template: the new cases fail on main twice and pass here twice; the 3 checks that read this diff pass.
Author
Contributor

@Beanstalk linux, build the renderer at this head: it should build with no error in the files this PR changes; no change in play expected from the build alone.

@Beanstalk linux, build the renderer at this head: it should build with no error in the files this PR changes; no change in play expected from the build alone.
Member

@Amateurwizrd only members of BigBeans can start the farm.

One of them can approve this request by reacting 👍 to it or to this comment. This request was for cc6a0ea, and the PR has changed since (8f94099), so a 👍 no longer approves it. Comment @Beanstalk again to ask for the new commit.

@Amateurwizrd only members of `BigBeans` can start the farm. ~~One of them can approve this request by reacting 👍 to it or to this comment.~~ This request was for `cc6a0ea`, and the PR has changed since (`8f94099`), so a 👍 no longer approves it. Comment `@Beanstalk` again to ask for the new commit.
Author
Contributor

@Beanstalk windows, a 10 GB card: Lake Hylia for a few minutes on main and on this PR, expecting the eviction lines in longshot_log.txt to stop repeating each pass on this PR where main evicts again each pass.

@Beanstalk windows, a 10 GB card: Lake Hylia for a few minutes on main and on this PR, expecting the eviction lines in longshot_log.txt to stop repeating each pass on this PR where main evicts again each pass.
Member

@Amateurwizrd only members of BigBeans can start the farm.

One of them can approve this request by reacting 👍 to it or to this comment. This request was for cc6a0ea, and the PR has changed since (8f94099), so a 👍 no longer approves it. Comment @Beanstalk again to ask for the new commit.

@Amateurwizrd only members of `BigBeans` can start the farm. ~~One of them can approve this request by reacting 👍 to it or to this comment.~~ This request was for `cc6a0ea`, and the PR has changed since (`8f94099`), so a 👍 no longer approves it. Comment `@Beanstalk` again to ask for the new commit.
Author
Contributor

Merged main @ f88e6e3a (8f94099d): it no longer merged clean. One conflict, in docs/development.md: main's new target pool row (RX_VK_TARGET_POOL_MB, RX_VK_DEAD_EVERY, ...) kept, and this PR's RX_VK_EVICT_EXCESS row in place of main's. #637's VRAM changes (dynamic floor, three-step target pool) do not touch vram_compact::rule_target or its callers, so the cut works as described. Game-free checks for the changed files: no failure that main does not also have on this PC.

Merged main @ f88e6e3a (8f94099d): it no longer merged clean. One conflict, in docs/development.md: main's new target pool row (RX_VK_TARGET_POOL_MB, RX_VK_DEAD_EVERY, ...) kept, and this PR's RX_VK_EVICT_EXCESS row in place of main's. #637's VRAM changes (dynamic floor, three-step target pool) do not touch `vram_compact::rule_target` or its callers, so the cut works as described. Game-free checks for the changed files: no failure that main does not also have on this PC.
Owner

Brought up to the ready-for-review standard (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know).

  • Tested on my own PC: not ticked: Testing says game-free checks only, and the game was not run on a card whose cache goes far over the line. Run it yourself on your PC (in the game, for a change the game runs) and say where and what you saw in Testing's Tested; or, when the fix's own case can't be run by hand, add a **Not testable by hand:** line saying why and what stands in for it. Then tick it.
  • Nothing gets worse that I know of: not ticked: Risks names a larger one-time burst of uploads, and the 8 and 10 GB cards are not measured in the game. Measure that cost and state it in Risks, then tick it.
Brought up to the [ready-for-review standard](https://git.magicbean.dev/MagicBeanDev/Longshot/src/branch/main/CONTRIBUTING.md#ready-for-review-out-of-wip) (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know). - *Tested on my own PC*: not ticked: Testing says game-free checks only, and the game was not run on a card whose cache goes far over the line. Run it yourself on your PC (in the game, for a change the game runs) and say where and what you saw in Testing's *Tested*; or, when the fix's own case can't be run by hand, add a `**Not testable by hand:**` line saying why and what stands in for it. Then tick it. - *Nothing gets worse that I know of*: not ticked: Risks names a larger one-time burst of uploads, and the 8 and 10 GB cards are not measured in the game. Measure that cost and state it in Risks, then tick it.
Amateurwizrd force-pushed fix/vram-excess-cut from 8f94099de2
Some checks failed
beanstalk/approval changed since the request: ask again
PR description / Description follows the template (pull_request_target) Successful in 7s
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
Website / Website on Cloudflare (pull_request) Has been cancelled
to d301477f89
Some checks are pending
beanstalk/approval changed since the request: ask again
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
PR description / Description follows the template (pull_request_target) Successful in 7s
2026-11-18 19:33:18 +00:00
Compare
Some checks are pending
beanstalk/approval changed since the request: ask again
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
PR description / Description follows the template (pull_request_target) Successful in 7s
This pull request is marked as a work in progress.
Some workflows are waiting to be reviewed.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'fix/vram-excess-cut:Amateurwizrd-fix/vram-excess-cut'
git switch 'Amateurwizrd-fix/vram-excess-cut'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!519
No description provided.