fix(linux): a restart no longer hands the game its own log as stderr, so the new run moves it and the crash window finds it #1059

Open
zeldaootr wants to merge 3 commits from zeldaootr/Longshot:restart-log into main
Contributor

Type: fix · Risk: low · Tested on: Steam Deck OLED (SteamOS 3.9.5, RADV); Linux x86-64 (game-free checks) · Needs: none

Why

On Linux, after the game restarts itself (the Insert menu's Restart now, or a restart a changed setting asks for), its log is wrong: the new run's lines go on at the end of the old run's longshot_log.txt instead of a fresh log, the old run is not kept as longshot_log.1.txt, and if the new run crashes, the crash window shows the crash without its log. That hits every player who starts the game from its icon, Steam or the launcher and restarts it, the Steam Deck included, and the log is what a bug report sends.

The tracker was searched (restart, relaunch, longshot_log, stderr): no issue or pull request is about this.

How to reproduce

Seen on: game-free, Linux (Ubuntu 24.04, x86-64, gcc 13.3 and clang 23); in the game, any Linux PC or Steam Deck.
Settings and switches: defaults; the game started with no stderr of its own (from its icon, Steam or the launcher, or 2>/dev/null from a shell).
Steps: start the game, restart it (Insert menu, Restart now; or the control bridge's relaunch), then read logs/longshot_log.txt and logs/longshot_log.1.txt in the game folder. Game-free: python -I -B tests/test_restart_log.py on main with this PR's test commit.
Expected: longshot_log.1.txt holds the first run, and the new longshot_log.txt starts with the second run's version and run_id lines.
Actual: the second run's lines follow the first run's in longshot_log.txt; longshot_log.1.txt is the run before the first (or missing).

What changed

The Linux restart becomes the game again with execve, which keeps the open stderr. A game given no stderr writes its log there, so the new run found its own log file as stderr, took it for a stderr it was given, and neither moved the log to .1 nor named it for the crash window. Now the start remembers whether the game was given a stderr, as Windows already does, and a game given none is started again with none (/dev/null); it gets its log back if the restart fails, so the failure is still logged.

  • restart: hos_relaunch_keep_env (new on Linux) and relaunch in host/hos_relaunch.c: the first notes at the start whether stderr was given, by the same test host/hos_main.c uses; the second puts /dev/null on stderr for a game given none before execve, and restores the log if both execve and execvp fail.
  • start: the Linux main in host/hos_main.c calls hos_relaunch_keep_env() before the log is opened as stderr.
  • tests: tests/test_restart_log.py (new) cuts the Linux restart and runs it with stand-ins for the exec; tests/display_startup_failure_test.cpp gets a stand-in for the new call.

Measurements

Verdict: fixed. In the game-free test, on main a restarted game given no stderr gets its own log as stderr; with this PR it gets none, a game given a stderr keeps it, and a failed restart has its log back. On a Steam Deck started as from Steam, a restart over the bridge left run 1 in longshot_log.1.txt and a fresh longshot_log.txt starting with run 2's run_id.

Hardware: game-free on Ubuntu 24.04 x86-64, gcc 13.3.0 and clang 23.1.5; in the game a Steam Deck OLED (SteamOS 3.9.5, kernel 7.2.7-valve2, Mesa 26.2.0-devel RADV)
Scene: game-free; in the game, the title screen, a restart, the title again
Method: tests/test_restart_log.py with each compiler at the test commit and at the fix (deterministic, one run each); in the game one run, the two log files read after the quit
How to reproduce: CXX=g++ python -I -B tests/run_all.py test_restart_log, then CXX=clang++; in the game, start with 2>/dev/null and the control bridge on, longshot_ctl.py relaunch, quit, read logs/

Before: main @ bbe421f5 + the test (fd0ad1b7) After: this PR @ e833a327
a game given no stderr, restarted: stderr at the exec its own longshot_log.txt none (not a regular file)
a game given a stderr, restarted (not reached) the same file
a failed exec: stderr after (not reached) its log again, the failure logged
before (fd0ad1b7, g++ and clang++):
FAIL: a game given no stderr starts again with its own longshot_log.txt as stderr: the new run takes it for a stderr it was given, appends to it unrotated, and the crash window does not find the run's log
after (e833a327, g++ and clang++):
restart log: all checks passed
PASS: a restart on Linux gives the game started again the stderr it was given

in the game (Steam Deck, run hf1-restart):
relaunched: answering again after 1.3 s (uptime 0.4 s)      (the same pid before and after)
logs/longshot_log.1.txt:2:[hos host] run_id: e4cf7408e107191622d9e404b0afd851   (run 1)
logs/longshot_log.txt:1:[hos host] longshot v3.0.0-rc.3-76-ga8c3391c (source fd724be9)
logs/longshot_log.txt:2:[hos host] run_id: 3d15486899940caea6e2571166486412   (run 2)

Flags and settings

None.

Testing

Tested:

  • In the game on a Steam Deck OLED (SteamOS 3.9.5, kernel 7.2.7-valve2, Mesa 26.2.0-devel RADV), headless, started as from Steam (setsid ./longshot </dev/null >/dev/null 2>&1, so the game opens its own log as stderr), with the control bridge on: to the title, then the bridge's relaunch, then quit. The game came back in 1.3 s as the same process; logs/longshot_log.1.txt holds run 1 (its run_id), and the new logs/longshot_log.txt starts with the version line and run 2's run_id, with no line of run 1; the quit exited 0. The build was a local test pack on an older development base (main 9c9d69ed), carrying this change's host/ diff as it is here, plus the bridge's relaunch from #97, which that base predates. Recorded in docs/tested/2026-11-16-restart-log-zeldaootr-deck-run01.md.
  • Game-free on Linux (Ubuntu 24.04, x86-64): the new test fails at the test commit and passes at the fix with g++ 13.3 and clang++ 23.1, on main bbe421f5. CXX=g++ and CXX=clang++ python -I -B tests/run_all.py --changed forge/main: 42 passed, 0 failed, 0 skipped each. The whole run, CXX=g++ python -I -B tests/run_all.py: 568 passed, 14 failed, 82 skipped; main @ bbe421f5 the same way: 567 passed, 14 failed, 82 skipped, the same 14 checks failing: test_bug_report_defaults, test_crt_options, test_guest_imported, test_link_skip, test_linux_preflight, test_linux_update, test_make_game_cache, test_missing_nup, test_mods_size_table, test_pending_guest_import, test_run_all_changed, test_vk_occlusion_queries, test_walk_key and test_pipeline_cache_save (a timing check that also fails on main under load). The skips are checks whose tools (the Vulkan headers and the like) are not on this PC. host/hos_main.c and host/hos_relaunch.c compiled whole with -fsyntax-only -Wall -Wextra for Linux (gcc and clang, with the build's -D_GNU_SOURCE) and for Windows (llvm-mingw 20261104), against the lift's generated headers of an older local build: the same warnings as main, none new.

Not tested: main in the game for comparison: the Deck's development base has no bridge relaunch (the command is refused there), so the bug itself was shown game-free only. The Insert menu's Restart now in the game (it calls the same relaunch). Windows (unchanged: its restart starts a new process and already keeps whether stderr was given).

Must be tested: None.

Risks

What could break: the restart on Linux: a game given no stderr now starts again with /dev/null there, then opens its own log as on a first start. A game given a stderr (a terminal, a pipe, a file) is restarted with it as before.

Turning it off: revert the commit.

Compatibility: Nothing changes for a player but that a restart starts a fresh log and keeps the run before as longshot_log.1.txt.

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).
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • 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.
  • A file in docs/tested/ for each new measured run (format in docs/tested-configurations.md).
  • A game-free test added for the fix, failing on main and passing here.
  • A check under tests/ that reads changed source updated in this PR, not weakened.
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths.
**Type:** fix · **Risk:** low · **Tested on:** Steam Deck OLED (SteamOS 3.9.5, RADV); Linux x86-64 (game-free checks) · **Needs:** none ## Why On Linux, after the game restarts itself (the Insert menu's Restart now, or a restart a changed setting asks for), its log is wrong: the new run's lines go on at the end of the old run's `longshot_log.txt` instead of a fresh log, the old run is not kept as `longshot_log.1.txt`, and if the new run crashes, the crash window shows the crash without its log. That hits every player who starts the game from its icon, Steam or the launcher and restarts it, the Steam Deck included, and the log is what a bug report sends. The tracker was searched (`restart`, `relaunch`, `longshot_log`, `stderr`): no issue or pull request is about this. ## How to reproduce **Seen on:** game-free, Linux (Ubuntu 24.04, x86-64, gcc 13.3 and clang 23); in the game, any Linux PC or Steam Deck. **Settings and switches:** defaults; the game started with no stderr of its own (from its icon, Steam or the launcher, or `2>/dev/null` from a shell). **Steps:** start the game, restart it (Insert menu, Restart now; or the control bridge's `relaunch`), then read `logs/longshot_log.txt` and `logs/longshot_log.1.txt` in the game folder. Game-free: `python -I -B tests/test_restart_log.py` on main with this PR's test commit. **Expected:** `longshot_log.1.txt` holds the first run, and the new `longshot_log.txt` starts with the second run's version and `run_id` lines. **Actual:** the second run's lines follow the first run's in `longshot_log.txt`; `longshot_log.1.txt` is the run before the first (or missing). ## What changed The Linux restart becomes the game again with `execve`, which keeps the open stderr. A game given no stderr writes its log there, so the new run found its own log file as stderr, took it for a stderr it was given, and neither moved the log to `.1` nor named it for the crash window. Now the start remembers whether the game was given a stderr, as Windows already does, and a game given none is started again with none (`/dev/null`); it gets its log back if the restart fails, so the failure is still logged. - restart: `hos_relaunch_keep_env` (new on Linux) and `relaunch` in `host/hos_relaunch.c`: the first notes at the start whether stderr was given, by the same test `host/hos_main.c` uses; the second puts `/dev/null` on stderr for a game given none before `execve`, and restores the log if both `execve` and `execvp` fail. - start: the Linux `main` in `host/hos_main.c` calls `hos_relaunch_keep_env()` before the log is opened as stderr. - tests: `tests/test_restart_log.py` (new) cuts the Linux restart and runs it with stand-ins for the exec; `tests/display_startup_failure_test.cpp` gets a stand-in for the new call. ## Measurements **Verdict:** fixed. In the game-free test, on main a restarted game given no stderr gets its own log as stderr; with this PR it gets none, a game given a stderr keeps it, and a failed restart has its log back. On a Steam Deck started as from Steam, a restart over the bridge left run 1 in `longshot_log.1.txt` and a fresh `longshot_log.txt` starting with run 2's `run_id`. Hardware: game-free on Ubuntu 24.04 x86-64, gcc 13.3.0 and clang 23.1.5; in the game a Steam Deck OLED (SteamOS 3.9.5, kernel 7.2.7-valve2, Mesa 26.2.0-devel RADV) Scene: game-free; in the game, the title screen, a restart, the title again Method: `tests/test_restart_log.py` with each compiler at the test commit and at the fix (deterministic, one run each); in the game one run, the two log files read after the quit How to reproduce: `CXX=g++ python -I -B tests/run_all.py test_restart_log`, then `CXX=clang++`; in the game, start with `2>/dev/null` and the control bridge on, `longshot_ctl.py relaunch`, quit, read `logs/` | | Before: main @ bbe421f5 + the test (fd0ad1b7) | After: this PR @ e833a327 | |---|---|---| | a game given no stderr, restarted: stderr at the exec | its own `longshot_log.txt` | none (not a regular file) | | a game given a stderr, restarted | (not reached) | the same file | | a failed exec: stderr after | (not reached) | its log again, the failure logged | ``` before (fd0ad1b7, g++ and clang++): FAIL: a game given no stderr starts again with its own longshot_log.txt as stderr: the new run takes it for a stderr it was given, appends to it unrotated, and the crash window does not find the run's log after (e833a327, g++ and clang++): restart log: all checks passed PASS: a restart on Linux gives the game started again the stderr it was given in the game (Steam Deck, run hf1-restart): relaunched: answering again after 1.3 s (uptime 0.4 s) (the same pid before and after) logs/longshot_log.1.txt:2:[hos host] run_id: e4cf7408e107191622d9e404b0afd851 (run 1) logs/longshot_log.txt:1:[hos host] longshot v3.0.0-rc.3-76-ga8c3391c (source fd724be9) logs/longshot_log.txt:2:[hos host] run_id: 3d15486899940caea6e2571166486412 (run 2) ``` ### Flags and settings None. ## Testing **Tested:** - In the game on a Steam Deck OLED (SteamOS 3.9.5, kernel 7.2.7-valve2, Mesa 26.2.0-devel RADV), headless, started as from Steam (`setsid ./longshot </dev/null >/dev/null 2>&1`, so the game opens its own log as stderr), with the control bridge on: to the title, then the bridge's `relaunch`, then `quit`. The game came back in 1.3 s as the same process; `logs/longshot_log.1.txt` holds run 1 (its `run_id`), and the new `logs/longshot_log.txt` starts with the version line and run 2's `run_id`, with no line of run 1; the quit exited 0. The build was a local test pack on an older development base (main 9c9d69ed), carrying this change's `host/` diff as it is here, plus the bridge's `relaunch` from #97, which that base predates. Recorded in `docs/tested/2026-11-16-restart-log-zeldaootr-deck-run01.md`. - Game-free on Linux (Ubuntu 24.04, x86-64): the new test fails at the test commit and passes at the fix with g++ 13.3 and clang++ 23.1, on main bbe421f5. `CXX=g++` and `CXX=clang++ python -I -B tests/run_all.py --changed forge/main`: 42 passed, 0 failed, 0 skipped each. The whole run, `CXX=g++ python -I -B tests/run_all.py`: 568 passed, 14 failed, 82 skipped; main @ bbe421f5 the same way: 567 passed, 14 failed, 82 skipped, the same 14 checks failing: `test_bug_report_defaults`, `test_crt_options`, `test_guest_imported`, `test_link_skip`, `test_linux_preflight`, `test_linux_update`, `test_make_game_cache`, `test_missing_nup`, `test_mods_size_table`, `test_pending_guest_import`, `test_run_all_changed`, `test_vk_occlusion_queries`, `test_walk_key` and `test_pipeline_cache_save` (a timing check that also fails on main under load). The skips are checks whose tools (the Vulkan headers and the like) are not on this PC. `host/hos_main.c` and `host/hos_relaunch.c` compiled whole with `-fsyntax-only -Wall -Wextra` for Linux (gcc and clang, with the build's `-D_GNU_SOURCE`) and for Windows (llvm-mingw 20261104), against the lift's generated headers of an older local build: the same warnings as main, none new. **Not tested:** main in the game for comparison: the Deck's development base has no bridge `relaunch` (the command is refused there), so the bug itself was shown game-free only. The Insert menu's Restart now in the game (it calls the same `relaunch`). Windows (unchanged: its restart starts a new process and already keeps whether stderr was given). **Must be tested:** None. ## Risks **What could break:** the restart on Linux: a game given no stderr now starts again with `/dev/null` there, then opens its own log as on a first start. A game given a stderr (a terminal, a pipe, a file) is restarted with it as before. **Turning it off:** revert the commit. **Compatibility:** Nothing changes for a player but that a restart starts a fresh log and keeps the run before as `longshot_log.1.txt`. ## 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). - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [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] A file in `docs/tested/` for each new measured run (format in `docs/tested-configurations.md`). - [x] A game-free test added for the fix, failing on `main` and passing here. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [x] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths.
A game given no stderr opens its longshot_log.txt as stderr; the Linux restart (execve) keeps fd 2, so the new run takes the log for a stderr it was given: it neither moves it to .1 nor names it for the crash window. Fails on main.

Assisted-by: Claude
The Linux restart becomes the game again by execve, which keeps fd 2. For a game started with no stderr (from its icon, Steam, the launcher) that was its own longshot_log.txt, which the new run took for a stderr it was given: it did not move the log to .1, appended to it, and named no log for the crash window, which then showed a crash in that run without its log. As on Windows (hos_relaunch_keep_env), the start keeps whether the game was given a stderr; a game given none is started again with /dev/null there, and gets its log back if the exec fails.

Assisted-by: Claude
docs(tested): the restart's log on a Steam Deck
Some checks are pending
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 3s
Website / Website on Cloudflare (pull_request_target) Has been skipped
e3c2e5c1c4
Assisted-by: Claude
Author
Contributor

Tested in game: Steam Deck OLED (SteamOS 3.9.5, Mesa 26.2.0-devel RADV), headless, started as from Steam with the control bridge on: to the title, then the bridge's relaunch, then quit. The game came back as the same process in 1.3 s; logs/longshot_log.1.txt holds run 1's run_id and the new logs/longshot_log.txt starts with run 2's version and run_id lines; quit exit 0. (A local test pack on an older development base with this change's host diff.)

Tested in game: Steam Deck OLED (SteamOS 3.9.5, Mesa 26.2.0-devel RADV), headless, started as from Steam with the control bridge on: to the title, then the bridge's relaunch, then quit. The game came back as the same process in 1.3 s; logs/longshot_log.1.txt holds run 1's run_id and the new logs/longshot_log.txt starts with run 2's version and run_id lines; quit exit 0. (A local test pack on an older development base with this change's host diff.)
Member

Code-only review of e3c2e5c1c4; informational findings, with final approval left to another reviewer.

No introduced correctness defect found. The startup probe uses the same stderr classification as the log-opening path, before that path replaces stderr. The saved log descriptor is close-on-exec, and the failure path restores it after both executable attempts fail; externally supplied stderr stays untouched.

The new fixture exercises the production restart body with real descriptors, checks the externally supplied file's identity, and checks restoration after failed exec. It does not perform a successful exec or exercise terminal/pipe inputs and descriptor-operation failures. The reported Steam Deck restart supplies complementary successful-exec evidence, with the older combined development-pack baseline clearly disclosed; it is not a current-head full-build comparison. I have not independently reproduced those results.

Merge coordination: the restart-in-place PR also changes this function to pass its save note. Those changes are complementary; preserve both the note handling and this stderr handling when combining them.

Read the complete diff, surrounding startup/relaunch and POSIX handle code, tests, run record and PR discussion. No builds, tests, generators or game runs performed.

Code-only review of e3c2e5c1c4bc337821594e0b66ee553e495f8f6d; informational findings, with final approval left to another reviewer. No introduced correctness defect found. The startup probe uses the same stderr classification as the log-opening path, before that path replaces stderr. The saved log descriptor is close-on-exec, and the failure path restores it after both executable attempts fail; externally supplied stderr stays untouched. The new fixture exercises the production restart body with real descriptors, checks the externally supplied file's identity, and checks restoration after failed exec. It does not perform a successful exec or exercise terminal/pipe inputs and descriptor-operation failures. The reported Steam Deck restart supplies complementary successful-exec evidence, with the older combined development-pack baseline clearly disclosed; it is not a current-head full-build comparison. I have not independently reproduced those results. Merge coordination: [the restart-in-place PR](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/61) also changes this function to pass its save note. Those changes are complementary; preserve both the note handling and this stderr handling when combining them. Read the complete diff, surrounding startup/relaunch and POSIX handle code, tests, run record and PR discussion. No builds, tests, generators or game runs performed.
TrashPanda approved these changes 2026-11-17 01:07:20 +00:00
TrashPanda left a comment

A Linux restart no longer keeps the game's own log as stderr. I read head e3c2e5c1. Approved.

execve keeps fd 2. A game started from its icon, Steam or the launcher has no stderr, so the first run opens longshot_log.txt there. The new run then saw a regular file, treated it as a stderr it had been given, and neither moved the log to .1 nor named it for the crash window. hos_relaunch_keep_env runs before that open and uses the same test as the log open: a terminal, a pipe or a real file counts as given; /dev/null and a socket count as none. A restart with none puts /dev/null on stderr, and puts the log back if both execs fail, so the failure is still logged. The saved descriptor is close-on-exec, so a successful exec does not keep the old log open. Windows already recorded this and is unchanged.

The check compiles that restart and runs it on real descriptors. A game given no stderr is not restarted with its log, a game given a file keeps that file, and a failed exec has the log back. It does not perform a successful exec. The Steam Deck run did: started as from Steam, one restart, run 1 in longshot_log.1.txt and a fresh longshot_log.txt for run 2. That pack was an older base plus this host/ change. #61 also edits this restart, to pass a save note. Keep both when that one is rebased.

A Linux restart no longer keeps the game's own log as stderr. I read head `e3c2e5c1`. Approved. `execve` keeps fd 2. A game started from its icon, Steam or the launcher has no stderr, so the first run opens `longshot_log.txt` there. The new run then saw a regular file, treated it as a stderr it had been given, and neither moved the log to `.1` nor named it for the crash window. `hos_relaunch_keep_env` runs before that open and uses the same test as the log open: a terminal, a pipe or a real file counts as given; `/dev/null` and a socket count as none. A restart with none puts `/dev/null` on stderr, and puts the log back if both execs fail, so the failure is still logged. The saved descriptor is close-on-exec, so a successful exec does not keep the old log open. Windows already recorded this and is unchanged. The check compiles that restart and runs it on real descriptors. A game given no stderr is not restarted with its log, a game given a file keeps that file, and a failed exec has the log back. It does not perform a successful exec. The Steam Deck run did: started as from Steam, one restart, run 1 in `longshot_log.1.txt` and a fresh `longshot_log.txt` for run 2. That pack was an older base plus this `host/` change. https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/61 also edits this restart, to pass a save note. Keep both when that one is rebased.
Some checks are pending
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 3s
Website / Website on Cloudflare (pull_request_target) Has been skipped
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
Some workflows are waiting to be reviewed.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'restart-log:zeldaootr-restart-log'
git switch 'zeldaootr-restart-log'
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!1059
No description provided.