Skip to content

Flatpak GNOME runtime 50 (47/48 EOL) + surface peer fetch errors#93

Merged
johnjazzi merged 3 commits into
mainfrom
dev
Jun 15, 2026
Merged

Flatpak GNOME runtime 50 (47/48 EOL) + surface peer fetch errors#93
johnjazzi merged 3 commits into
mainfrom
dev

Conversation

@johnjazzi

Copy link
Copy Markdown
Contributor

Summary

Follow-ups after 0.2.8 testing. Not in any release yet.

Flatpak / installer (Alpine reports)

  • GNOME runtime 47 → 50. Branches 47 and 48 are both end-of-life; 50 is current and still ships webkit2gtk-4.1 (Tauri v2's dependency). Bumped in lockstep: flatpak/ai.canonic.app.yml + the runtime install in release.yml. Takes effect on the next release build (the bundle embeds the runtime ref).
  • install.sh: flatpak install --noninteractive. Over a curl | sh pipe, flatpak's animated progress UI emitted terminal cursor-position queries whose replies weren't consumed and leaked as ^[[..R noise at the end; --noninteractive disables that UI and auto-answers the EOL prompt.

Peer "can't get files"

The fetch path is correct (host/port/token come from the live share + mDNS), so cross-machine "can't get files" is reachability (firewall / unreachable host), not a code bug. But the UI hid the reason behind a generic "Could not load files":

  • Surface the real error (e.g. Could not reach 192.168.x:port — connection refused) in the peer-files area.
  • Add an 8s timeout to the manifest fetch so a dropping firewall fails fast instead of hanging.

All 311 tests pass; cargo check clean; version synced to 0.2.8.

🤖 Generated with Claude Code

john and others added 3 commits June 15, 2026 10:55
- GNOME runtime 47 (and 48) are end-of-life; bump to 50, which still provides
  webkit2gtk-4.1 that Tauri v2 links against. Updated in lockstep:
  flatpak/ai.canonic.app.yml runtime-version and the runtime install in
  release.yml.
- install.sh: pass --noninteractive to `flatpak install`. Over a curl|sh pipe
  flatpak's animated progress UI emitted terminal cursor-position queries whose
  replies weren't consumed and leaked as `^[[..R` noise at the end; it also
  auto-answers the EOL/migration prompt.

Takes effect on the next release build (the bundle embeds the runtime ref).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…uests

"Can't get files" from a discovered peer was shown as a generic "Could not load
files" — the actual reason (connection refused / timeout = firewall or
unreachable host) was discarded. Now the peer files error shows the real message
("Could not reach 192.168.x:port — …"). Added an 8s timeout to the manifest
fetch so a firewall that DROPs the share port fails fast instead of hanging.

The fetch path itself was already correct (host/port/token come from the live
share + mDNS), so cross-machine "can't get files" is reachability, not a code
bug — this makes that obvious in the UI.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@johnjazzi johnjazzi merged commit 6425f18 into main Jun 15, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant