perf(vk): the pipeline cache file not read on Windows with NVIDIA's driver and 20 GB of RAM or less, as on Linux #1845

Merged
HumanBean merged 1 commit from GummiNaomi/Longshot:perf/pcache-windows-small-ram into main 2026-11-20 06:45:17 +00:00
Member

Summary

The pipeline cache's file (cache/longshot_vk_pipelines.bin, 1.2 GB after a preparation) is handed whole to vkCreatePipelineCache at every start, and NVIDIA's Windows driver keeps its copy in the game's private memory for the session: 1,563 MB in a Market stand on my PC. Linux has skipped the file since #416 with NVIDIA's own driver, 20 GB of RAM or less, programs loaded at create and NVIDIA's own shader cache warm, where that cache answers the pipelines. This applies the same rule on Windows, with the folder NVIDIA's Windows driver files its Vulkan pipelines in, %LOCALAPPDATA%\NVIDIA\GLCache. On my 32 GB PC, with the file left unread on purpose: working set 1.0 GB and private memory 1.2 GB lower, steady frames the same, but each load at create took 3.4-3.8 ms instead of 0.9 and draws ran about 40 loads themselves instead of 14. So, as on Linux, only with 20 GB of RAM or less, where that gigabyte is what makes the game page; this PC still reads the file, and no PC of 20 GB or less has run it yet (WIP). RX_VK_PCACHE_LOAD=1 reads it whatever the rule says.

Why: a temporary census of the process's allocations by call stack (not in this PR) put 1,563 MB under vkCreatePipelineCache <- pcache_init <- precompile_run: the driver's copy of the file. NVIDIA's own disk cache holds the same pipelines (4.7 GB on this PC), and with programs loaded at create every pipeline the load builds is asked of it then. Not reading the file moves that work from a memory copy to NVIDIA's disk cache: cheaper in RAM, dearer per load.

What changes: pcache_load::choose (gpu/vk/pcache_load.h) gets a Windows-with-NVIDIA arm: not read with 20 GB of RAM or less (GlobalMemoryStatusEx), programs loaded at create, and NVIDIA's folder holding 512 MB or more (nvidia_cache_windows); read where the RAM is more or not known, the folder nearly empty, missing or not readable, programs loaded before the title, and in a --prepare-shaders run. needs_cache walks the folder only where everything else already says not to read. pcache_load_off (gpu/vk/vk_draw.cpp) asks Windows for the RAM and the folder, and the log's vk: pipeline cache file read / not read line names the reason. Unchanged: Linux's rule, AMD and Intel (read), RX_VK_PCACHE_LOAD, and what happens when the file is not read (as on Linux).

Read first: choose and nvidia_cache_windows in gpu/vk/pcache_load.h, pcache_load_off in gpu/vk/vk_draw.cpp, then tests/test_pcache_load.py.

Testing

Tested: Windows 11, RTX 4070 SUPER (NVIDIA 617.42), Ryzen 9 9950X3D with SMT off, 32 GB: on a build of main @ f505340b with #1810-#1813's changes, this one and #1844, two Market stands from the kokiri-start save, whose log said pipeline cache file read: more than 20 GB of RAM, or the RAM not known (31620 MB of RAM), the rule's answer on this PC; the unread side on a build whose Windows arm had no RAM limit yet: two Market stands and a 7-area teleport tour, the log saying not read: Windows with NVIDIA's own driver, ... with the folder's 4,729 MB, every area drawn, the tour's pictures alike in all 7 areas against a tour with the file read and the modules kept.
Checks: tests/test_pcache_load.py (the rule's table with the Windows cases; pcache_load_off run on Windows against a LOCALAPPDATA folder of each kind: warm, 32 GB, RAM not known, nearly empty, empty, DirectX's cache only, no LOCALAPPDATA, AMD, programs loaded before the title, a preparation, the switch either way) passes on this head on Windows (clang), and on Linux (g++ 13.3, WSL Ubuntu 24.04) with Linux's folder cases; tests/test_switch_table.py passes.
Suite: tests/run_all.py with every check on main @ 068fb8eb in WSL Ubuntu 24.04 (740 pass, 61 fail, 69 skipped: no clang or spirv-val there), then this head's --changed checks in WSL (156 pass, 12 fail, 4 skipped) and on Windows (167 run, 27 fail). Every failure also fails on main @ 068fb8eb on the same OS: in WSL and on Windows test_crash_dialog, test_dev_ab, test_dev_packs, test_draw_stream_visibility, test_frame_overlap, test_fsr_uniform_ownership, test_linux_pressure, test_pipeline_play_cache, test_prepare_cache_save, test_present_queue_default, test_upscaler_rows, test_vk_occlusion_queries; on Windows only test_draw_binds, test_driver_env_choose, test_image_arrays, test_linux_driver_fault_guard, test_mesh_fallback_layout, test_pass_hazard, test_pipeline_tour, test_precompile_compute_guard, test_push_state, test_same_draw, test_same_dyn, test_shader_module_guard, test_table_track, test_tracy_funcs, test_vertex_bind. (On Windows most of them are compile errors with this PC's compiler wrapper, on main as here.) These ran on the head as it was on main @ 068fb8eb; it was then rebased onto main @ 3f2c9b3c, whose two new commits change only the NFC menu (gpu/vk/menu/nfc.cpp and its test), none of this PR's files.

Still to test:

  • A Windows PC with 16 GB of RAM and an NVIDIA card, its GLCache warm: two Market stands and a tour a side, unset against RX_VK_PCACHE_LOAD=1, expecting the log's not read line, about 1 GB less private memory and fewer hard page faults unset, and the loads' and long frames' cost against that (by hand)
  • The same PC after NVIDIA's cache is cleared (a driver update): expecting nearly empty in the log and the file read (by hand)

Measurements

Verdict: on this 32 GB PC, where the rule keeps reading the file: leaving it unread took 1.0 GB of working set and 1.2 GB of private memory off and kept the steady frames, but made the loads at create about 4 times slower, sent about three times as many draws to run a load themselves, and gave the tour more frames of 33 ms or more (71 against 62). A trade only for a PC where the gigabyte is what makes the game page; not measured on one yet.

Setup: Windows 11 Pro 26200, RTX 4070 SUPER 12 GB (NVIDIA 617.42), Ryzen 9 9950X3D with SMT off, 32 GB; from kokiri-start, a teleport to the Market and 150 s there (the working set's median over the last third of the log's memory lines, frames over the last 100 s), and a teleport tour of 7 areas, 20 s each; 2560x1440, no window (HOS_HEADLESS=1), uncapped, 16 cores; in both arms RX_VK_LOAD=create RX_VK_ASTC_BC_ALL=1 RX_VK_IMAGE_BLOCK_MB=32 RX_VK_BC_LAYERS=8 RX_VK_LATE_FIX=1 RX_VK_TEX_MOVE=1 RX_VK_TEX_AHEAD=2 HOS_NVN_FRAME_OVERLAP=1 RX_VK_FRAME_TRACE=1, and the loaded modules let go (#1844) on.

Baseline: builds of main @ f505340b (before the tooling revamp 068fb8eb, which changes none of this code) with #1810-#1813's changes, #1844 and this change. The stands: one build whose Windows arm had no RAM limit, so it left the file unread on this PC (After), against the same build with RX_VK_PCACHE_LOAD=1 (Before, one stand); that build also held the temporary census, off. The tour: that build unset (After) against the final build, which reads the file here (Before). This PR's own default on this PC is the Before column.

Before: the file read (as main) @ f505340b After: not read (this PR at 20 GB or less) @ f505340b
Market stand: working set, median / peak (MB) 12,173 / 12,309 11,234 / 11,340; 11,134 / 11,225
Market stand: private memory (MB) 20,844 19,683; 19,592
Market stand: mean frame / p99 (ms) 11.01 / 14.86 10.89 / 14.46; 10.87 / 14.61
Market stand: late frames, frames of 33 ms or more 0.32 %, 0 0.19 %, 0; 0.18 %, 1
Market stand: a load at create, median 0.93 ms 3.76 ms; 3.39 ms
Market stand: draws that ran a load themselves (time waited) 14 (54 ms) 42 (200 ms); 38 (127 ms)
tour (7 areas): working set, peak (MB) 13,147 12,401
tour: private memory, last (MB) 21,758 20,914
tour: frames of 33 ms or more / 100 ms or more; p99 62 / 10; 17.23 ms 71 / 13; 18.58 ms

RX_VK_PCACHE_LOAD (a hw switch) keeps reading the file on every PC of more than 20 GB, as these numbers say for this one; at 20 GB or less with NVIDIA's own driver it follows Linux's rule, which was measured on Linux (#416), not yet on Windows.

Risks

What could break: on a Windows PC with NVIDIA, 20 GB of RAM or less and programs loaded at create, every load at create builds its pipelines from NVIDIA's disk cache instead of the file's copy in memory: more draws wait on a load, and an area's first moments may hitch more, in exchange for about 1 GB of RAM. NVIDIA's folder is shared by every Vulkan and OpenGL program on the PC: 512 MB of another game's pipelines reads as warm, and then the pipelines Longshot needs compile in play, as on Linux. A driver update empties it, and then the file is read again. Turning it off: RX_VK_PCACHE_LOAD=1. After updating, a player with such a PC has about 1 GB less of the game in RAM and may see slower first moments in an area; nothing changes for saves, longshot_options.ini or the caches (the file is kept for a start that reads it).

Checklist

Ready for review

  • One topic, on current main; the title is a Conventional Commit.
  • Tested on my own PC, in the game for a change the game runs, as Testing says.
  • mise run test passes (any failure that also fails on main is named).
  • Measured against main, or Measurements says why there is nothing to measure. (Not on a PC of 20 GB or less, the only one it changes; on this 32 GB PC with the rule's limit lifted: one stand read, two not, and one tour a side.)
  • No game files, build output or hand-edited generated files; third_party/ untouched; nothing GPL-incompatible.

When it applies

  • A switch added or changed: it ships at the default the measurements chose, with its row in gpu/vk/switches.def. (Its row is changed; the default at 20 GB or less follows Linux's measured rule and is not measured on Windows yet: Still to test.)
  • A check under tests/ that reads changed source is updated, not weakened.
  • Host code builds on Windows (llvm-mingw) and Linux, with UTF-8 paths. (gpu/vk/vk_draw.cpp was built on Windows for the measured builds, not yet on this head or on Linux; the test compiles pcache_load.h and pcache_load_off with clang on Windows and g++ 13.3 on WSL Ubuntu 24.04. On this head the changed files pass a syntax-only compile with the builder's own Windows flags.)
  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.

Ready to merge

  • Everything in Still to test has run, its results in Tested.
  • Tier 1 hardware it can affect is tested (docs/dev/standards.md, "Hardware tiers").
  • Approved in review, every comment answered.
  • CI passes on the head; on current main, measured again or a comment says why the numbers still hold.

🤖 Generated with Claude Code

## Summary The pipeline cache's file (`cache/longshot_vk_pipelines.bin`, 1.2 GB after a preparation) is handed whole to `vkCreatePipelineCache` at every start, and NVIDIA's Windows driver keeps its copy in the game's private memory for the session: 1,563 MB in a Market stand on my PC. Linux has skipped the file since #416 with NVIDIA's own driver, 20 GB of RAM or less, programs loaded at create and NVIDIA's own shader cache warm, where that cache answers the pipelines. This applies the same rule on Windows, with the folder NVIDIA's Windows driver files its Vulkan pipelines in, `%LOCALAPPDATA%\NVIDIA\GLCache`. On my 32 GB PC, with the file left unread on purpose: working set 1.0 GB and private memory 1.2 GB lower, steady frames the same, but each load at create took 3.4-3.8 ms instead of 0.9 and draws ran about 40 loads themselves instead of 14. So, as on Linux, only with 20 GB of RAM or less, where that gigabyte is what makes the game page; this PC still reads the file, and no PC of 20 GB or less has run it yet (WIP). `RX_VK_PCACHE_LOAD=1` reads it whatever the rule says. Why: a temporary census of the process's allocations by call stack (not in this PR) put 1,563 MB under `vkCreatePipelineCache` <- `pcache_init` <- `precompile_run`: the driver's copy of the file. NVIDIA's own disk cache holds the same pipelines (4.7 GB on this PC), and with programs loaded at create every pipeline the load builds is asked of it then. Not reading the file moves that work from a memory copy to NVIDIA's disk cache: cheaper in RAM, dearer per load. What changes: `pcache_load::choose` (`gpu/vk/pcache_load.h`) gets a Windows-with-NVIDIA arm: not read with 20 GB of RAM or less (`GlobalMemoryStatusEx`), programs loaded at create, and NVIDIA's folder holding 512 MB or more (`nvidia_cache_windows`); read where the RAM is more or not known, the folder nearly empty, missing or not readable, programs loaded before the title, and in a `--prepare-shaders` run. `needs_cache` walks the folder only where everything else already says not to read. `pcache_load_off` (`gpu/vk/vk_draw.cpp`) asks Windows for the RAM and the folder, and the log's `vk: pipeline cache file read` / `not read` line names the reason. Unchanged: Linux's rule, AMD and Intel (read), `RX_VK_PCACHE_LOAD`, and what happens when the file is not read (as on Linux). Read first: `choose` and `nvidia_cache_windows` in `gpu/vk/pcache_load.h`, `pcache_load_off` in `gpu/vk/vk_draw.cpp`, then `tests/test_pcache_load.py`. ## Testing **Tested:** Windows 11, RTX 4070 SUPER (NVIDIA 617.42), Ryzen 9 9950X3D with SMT off, 32 GB: on a build of main @ f505340b with #1810-#1813's changes, this one and #1844, two Market stands from the `kokiri-start` save, whose log said `pipeline cache file read: more than 20 GB of RAM, or the RAM not known (31620 MB of RAM)`, the rule's answer on this PC; the unread side on a build whose Windows arm had no RAM limit yet: two Market stands and a 7-area teleport tour, the log saying `not read: Windows with NVIDIA's own driver, ...` with the folder's 4,729 MB, every area drawn, the tour's pictures alike in all 7 areas against a tour with the file read and the modules kept. Checks: `tests/test_pcache_load.py` (the rule's table with the Windows cases; `pcache_load_off` run on Windows against a LOCALAPPDATA folder of each kind: warm, 32 GB, RAM not known, nearly empty, empty, DirectX's cache only, no LOCALAPPDATA, AMD, programs loaded before the title, a preparation, the switch either way) passes on this head on Windows (clang), and on Linux (g++ 13.3, WSL Ubuntu 24.04) with Linux's folder cases; `tests/test_switch_table.py` passes. Suite: `tests/run_all.py` with every check on main @ 068fb8eb in WSL Ubuntu 24.04 (740 pass, 61 fail, 69 skipped: no clang or spirv-val there), then this head's `--changed` checks in WSL (156 pass, 12 fail, 4 skipped) and on Windows (167 run, 27 fail). Every failure also fails on main @ 068fb8eb on the same OS: in WSL and on Windows `test_crash_dialog`, `test_dev_ab`, `test_dev_packs`, `test_draw_stream_visibility`, `test_frame_overlap`, `test_fsr_uniform_ownership`, `test_linux_pressure`, `test_pipeline_play_cache`, `test_prepare_cache_save`, `test_present_queue_default`, `test_upscaler_rows`, `test_vk_occlusion_queries`; on Windows only `test_draw_binds`, `test_driver_env_choose`, `test_image_arrays`, `test_linux_driver_fault_guard`, `test_mesh_fallback_layout`, `test_pass_hazard`, `test_pipeline_tour`, `test_precompile_compute_guard`, `test_push_state`, `test_same_draw`, `test_same_dyn`, `test_shader_module_guard`, `test_table_track`, `test_tracy_funcs`, `test_vertex_bind`. (On Windows most of them are compile errors with this PC's compiler wrapper, on main as here.) These ran on the head as it was on main @ 068fb8eb; it was then rebased onto main @ 3f2c9b3c, whose two new commits change only the NFC menu (`gpu/vk/menu/nfc.cpp` and its test), none of this PR's files. **Still to test:** - A Windows PC with 16 GB of RAM and an NVIDIA card, its GLCache warm: two Market stands and a tour a side, unset against `RX_VK_PCACHE_LOAD=1`, expecting the log's `not read` line, about 1 GB less private memory and fewer hard page faults unset, and the loads' and long frames' cost against that (by hand) - The same PC after NVIDIA's cache is cleared (a driver update): expecting `nearly empty` in the log and the file read (by hand) ## Measurements **Verdict:** on this 32 GB PC, where the rule keeps reading the file: leaving it unread took 1.0 GB of working set and 1.2 GB of private memory off and kept the steady frames, but made the loads at create about 4 times slower, sent about three times as many draws to run a load themselves, and gave the tour more frames of 33 ms or more (71 against 62). A trade only for a PC where the gigabyte is what makes the game page; not measured on one yet. Setup: Windows 11 Pro 26200, RTX 4070 SUPER 12 GB (NVIDIA 617.42), Ryzen 9 9950X3D with SMT off, 32 GB; from `kokiri-start`, a teleport to the Market and 150 s there (the working set's median over the last third of the log's memory lines, frames over the last 100 s), and a teleport tour of 7 areas, 20 s each; 2560x1440, no window (`HOS_HEADLESS=1`), uncapped, 16 cores; in both arms `RX_VK_LOAD=create RX_VK_ASTC_BC_ALL=1 RX_VK_IMAGE_BLOCK_MB=32 RX_VK_BC_LAYERS=8 RX_VK_LATE_FIX=1 RX_VK_TEX_MOVE=1 RX_VK_TEX_AHEAD=2 HOS_NVN_FRAME_OVERLAP=1 RX_VK_FRAME_TRACE=1`, and the loaded modules let go (#1844) on. Baseline: builds of main @ f505340b (before the tooling revamp 068fb8eb, which changes none of this code) with #1810-#1813's changes, #1844 and this change. The stands: one build whose Windows arm had no RAM limit, so it left the file unread on this PC (After), against the same build with `RX_VK_PCACHE_LOAD=1` (Before, one stand); that build also held the temporary census, off. The tour: that build unset (After) against the final build, which reads the file here (Before). This PR's own default on this PC is the Before column. | | Before: the file read (as main) @ f505340b | After: not read (this PR at 20 GB or less) @ f505340b | |---|---|---| | Market stand: working set, median / peak (MB) | 12,173 / 12,309 | 11,234 / 11,340; 11,134 / 11,225 | | Market stand: private memory (MB) | 20,844 | 19,683; 19,592 | | Market stand: mean frame / p99 (ms) | 11.01 / 14.86 | 10.89 / 14.46; 10.87 / 14.61 | | Market stand: late frames, frames of 33 ms or more | 0.32 %, 0 | 0.19 %, 0; 0.18 %, 1 | | Market stand: a load at create, median | 0.93 ms | 3.76 ms; 3.39 ms | | Market stand: draws that ran a load themselves (time waited) | 14 (54 ms) | 42 (200 ms); 38 (127 ms) | | tour (7 areas): working set, peak (MB) | 13,147 | 12,401 | | tour: private memory, last (MB) | 21,758 | 20,914 | | tour: frames of 33 ms or more / 100 ms or more; p99 | 62 / 10; 17.23 ms | 71 / 13; 18.58 ms | `RX_VK_PCACHE_LOAD` (a hw switch) keeps reading the file on every PC of more than 20 GB, as these numbers say for this one; at 20 GB or less with NVIDIA's own driver it follows Linux's rule, which was measured on Linux (#416), not yet on Windows. ## Risks What could break: on a Windows PC with NVIDIA, 20 GB of RAM or less and programs loaded at create, every load at create builds its pipelines from NVIDIA's disk cache instead of the file's copy in memory: more draws wait on a load, and an area's first moments may hitch more, in exchange for about 1 GB of RAM. NVIDIA's folder is shared by every Vulkan and OpenGL program on the PC: 512 MB of another game's pipelines reads as warm, and then the pipelines Longshot needs compile in play, as on Linux. A driver update empties it, and then the file is read again. Turning it off: `RX_VK_PCACHE_LOAD=1`. After updating, a player with such a PC has about 1 GB less of the game in RAM and may see slower first moments in an area; nothing changes for saves, `longshot_options.ini` or the caches (the file is kept for a start that reads it). ## Checklist ### Ready for review - [x] One topic, on current `main`; the title is a Conventional Commit. - [x] Tested on my own PC, in the game for a change the game runs, as Testing says. - [x] `mise run test` passes (any failure that also fails on `main` is named). - [ ] Measured against `main`, or Measurements says why there is nothing to measure. (Not on a PC of 20 GB or less, the only one it changes; on this 32 GB PC with the rule's limit lifted: one stand read, two not, and one tour a side.) - [x] No game files, build output or hand-edited generated files; `third_party/` untouched; nothing GPL-incompatible. ### When it applies - [ ] A switch added or changed: it ships at the default the measurements chose, with its row in `gpu/vk/switches.def`. (Its row is changed; the default at 20 GB or less follows Linux's measured rule and is not measured on Windows yet: Still to test.) - [x] A check under `tests/` that reads changed source is updated, not weakened. - [ ] Host code builds on Windows (llvm-mingw) and Linux, with UTF-8 paths. (`gpu/vk/vk_draw.cpp` was built on Windows for the measured builds, not yet on this head or on Linux; the test compiles `pcache_load.h` and `pcache_load_off` with clang on Windows and g++ 13.3 on WSL Ubuntu 24.04. On this head the changed files pass a syntax-only compile with the builder's own Windows flags.) - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. ### Ready to merge - [ ] Everything in Still to test has run, its results in Tested. - [ ] Tier 1 hardware it can affect is tested (docs/dev/standards.md, "Hardware tiers"). - [ ] Approved in review, every comment answered. - [ ] CI passes on the head; on current `main`, measured again or a comment says why the numbers still hold. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
perf(vk): the pipeline cache file not read on Windows with NVIDIA's driver and 20 GB of RAM or less, as on Linux
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_target) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 23s
CI / Workflow lint (actionlint) (pull_request) Successful in 33s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 27s
Third-party parts / As their notes say (pull_request) Successful in 34s
PR description / Description follows the template (pull_request_target) Failing after 4s
CI / Website build and checks (pull_request) Failing after 2m53s
7a88661415
The pipeline cache's file (cache/longshot_vk_pipelines.bin, 1.2 GB after a preparation) is handed whole to
vkCreatePipelineCache at every start, and NVIDIA's Windows driver kept its copy in the game's private memory for the
session: 1,563 MB of a Market stand on a 32 GB PC. Linux already skips the file with NVIDIA's own driver, 20 GB of RAM or
less, programs loaded at create and NVIDIA's own shader cache warm (pcache_load.h).

pcache_load::choose gets a Windows NVIDIA arm with the same rule: GlobalMemoryStatusEx's RAM, 20 GB or less, and
%LOCALAPPDATA%\NVIDIA\GLCache (where NVIDIA's Windows driver files the Vulkan pipelines it compiled) holding 512 MB or
more (nvidia_cache_windows); read as before everywhere else, and RX_VK_PCACHE_LOAD=1 reads it whatever the rule says.
On a PC of more than 20 GB nothing changes. Not read on the 32 GB PC (RX_VK_PCACHE_LOAD=0, two stands a side): working set
1.0 GB and private memory 1.2 GB lower, steady frames the same, but each load at create took its pipelines from NVIDIA's
disk cache (median 3.4-3.8 ms against 0.9-1.0) and draws ran about 40 loads themselves against 11-18. Not yet measured on
a PC of 20 GB or less. tests/test_pcache_load.py checks the rule's Windows table and runs pcache_load_off on Windows
against a LOCALAPPDATA folder of each kind.

Assisted-by: Claude Code
Co-Authored-By: Claude Opus 5.5 <[email protected]>
HumanBean changed title from WIP: perf(vk): the pipeline cache file not read on Windows with NVIDIA's driver and 20 GB of RAM or less, as on Linux to perf(vk): the pipeline cache file not read on Windows with NVIDIA's driver and 20 GB of RAM or less, as on Linux 2026-11-20 06:44:49 +00:00
HumanBean deleted branch perf/pcache-windows-small-ram 2026-11-20 06:45:18 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
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!1845
No description provided.