Repository navigation
menu: use Tails desktop interfaces - #260
BenWestgate wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4e0da7dcb4
ℹ️ 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".
|
don't remove the empty Donate URI lets fill it in correctly with a donation address. There are 3+ places in the software that have addresses. |
BenWestgate
left a comment
There was a problem hiding this comment.
lets put our real donation address in the project finally and remove the dead link
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8e77ada570
ℹ️ 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".
|
Tails 7.13 runtime check at 8e77ada: the main, Settings, and Help dialogs now render wide/compact with the 520px width hint; the earlier tall/narrow layout no longer reproduces. |
This comment has been minimized.
This comment has been minimized.
ac43ede to
bbb2b4d
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bbb2b4d9d0
ℹ️ 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".
| "About") zenity --info --icon=bails128 --title="About CipherStick" \ | ||
| --text="$($XDG_DATA_HOME/bails/b --version)\n\nCopyright © 2023–2026 Ben Westgate\n\nPlease contribute if you find CipherStick useful. Visit <a href='https://github.com/BenWestgate/Bails'>https://github.com/BenWestgate/Bails</a> for further information about the software.\nThe source code is included with CipherStick.\n\nThis is experimental software.\nDistributed under the MIT software license, see the accompanying file COPYING or <a href='https://opensource.org/licenses/MIT'>https://opensource.org/licenses/MIT</a>"; exec "$0" ;; | ||
| "Online Help") open_url 'https://t.me/Bails_support'; exec "$0" ;; | ||
| "Update Bitcoin Core") install-core; exec "$0" ;; |
There was a problem hiding this comment.
Keep the core updater cancellable during network failures
When Tor or the network is unavailable, this direct call runs from the Terminal=false desktop launcher with no visible progress or cancellation UI, while install-core's retry_on_fail loop (lines 96–101, first used at line 116) retries indefinitely and reports only to terminal output. The menu therefore disappears and cannot return until connectivity recovers or the user externally kills the process; replace the removed terminal with a cancellable progress dialog or bound the retries and surface an error.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Valid blocker. #260 has already used its two code rounds (22becc4, ac43ede), so I am leaving this unresolved for human direction. The next fix should preserve a visible/cancellable update boundary without reintroducing a hard-coded terminal application—either make install-core surface/bound network retry itself or wrap it in a supported cancellable desktop interface.
BenWestgate
left a comment
There was a problem hiding this comment.
AI-generated review, posted at the maintainer's request.
ACK bbb2b4d code. Keeping the successful update checkout in amnesic /tmp fixes the asynchronous-copy race; supported-Tails menu validation remains the merge gate.
03134e7 to
fddc710
Compare
bbb2b4d to
91c4121
Compare
This comment has been minimized.
This comment has been minimized.
|
AI-assisted response: the Donate feedback is still unresolved at |
BenWestgate
left a comment
There was a problem hiding this comment.
Current-head AI re-review: NACK 91c4121 on the existing updater P2. Update Bitcoin Core still calls install-core from the non-terminal menu path while its network retry loop is unbounded and terminal-only, so a Tor/network failure remains invisible and not cancellable. Per CONTRIBUTING, fixing that shared install-core boundary is preferable to hard-coding another terminal app. No additional finding.
BenWestgate
left a comment
There was a problem hiding this comment.
Codex current-head review at 91c4121: one existing P2 remains. Update Bitcoin Core still calls install-core directly from the non-terminal launcher while its network retry loop is unbounded and terminal-only, so an outage leaves no visible/cancellable update boundary.
Open links with xdg-open and show the URL if that fails, return to the menu after Help and Settings actions, use zenity --icon, and drop the stale Slack and Twitter links. Updates keep running in GNOME Console as master does since #294, so a user can watch and cancel them. Closes #252 Refs #249, #269
91c4121 to
21c7150
Compare
This comment has been minimized.
This comment has been minimized.
BenWestgate
left a comment
There was a problem hiding this comment.
AI-assisted current-head review (21c7150): prior hidden-update P2 is addressed by opening a terminal. Remaining P2: kgx hardcodes a desktop terminal, contrary to CONTRIBUTING's dependency policy; use a supported terminal capability adapter and verify update failure/cancellation on Tails. Not ACKing yet.
Requested by Ben · project thread
Status
Waiting for human direction after two code rounds. Do not merge as-is. The desktop-application coupling is removed, but the direct Bitcoin Core update action can disappear into
install-core's unbounded network retry loop with no visible/cancellable UI when Tor/network is unavailable.What
xdg-openfor Help/Report-a-Bug/Donate URLs instead of direct browser commandsgnome-terminalWhy
The #230 Tails 7.13 review found menu actions coupled to desktop applications that are no longer present. The remaining review finding shows the updater still needs a supported visible/cancellable boundary rather than an invisible direct call.
Closes #252
Refs #249, #269
Human decision needed
Choose the smallest upstream-compatible way to keep Bitcoin Core updates visible and cancellable during network failure without hard-coding
kgx,gnome-terminal, or another incidental terminal application. The preferred boundary is forinstall-coreitself to surface or bound retry behavior if practical.No further code round should be started on this PR until that direction is given.
Testing already completed
bash -n bails/.local/bin/bails-menugnome-terminalor directtor-browserlaunchIf the PR proceeds, supported-Tails runtime validation should exercise Update Bitcoin Core with working Tor and with Tor/network unavailable, plus Update CipherStick, Donate, Online Help, Report a Bug, About, and menu return behavior.