Adopt MyOwnMesh v0.1.3 (fast recovery after a node freeze)#211
Merged
Conversation
Bumps the bundled myownmesh substrate from v0.1.2 to v0.1.3. That release makes a node which was frozen — e.g. while loading a model, which can stall the whole box and the colocated daemon — re-announce on wake and clear its own stale peer sessions, so neighbors reconnect in ~1-2s instead of waiting out the multi-minute advertisement cadence. - src-tauri/Cargo.toml: myownmesh-core git tag v0.1.2 -> v0.1.3 - .myownmesh-rev: v0.1.2 -> v0.1.3 (daemon sidecar pinned by build.rs) - src-tauri/Cargo.lock: refreshed (myownmesh-core + myownmesh-signaling) https://claude.ai/code/session_017UZ6AKBqV2ae2E6XbyoAgq
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adopt MyOwnMesh v0.1.3 — the fast-recovery fix for the model-load freeze.
src-tauri/Cargo.toml:myownmesh-coregit tagv0.1.2→v0.1.3(also corrected the stale "pinned tomain" comment)..myownmesh-rev:v0.1.2→v0.1.3(drivesbuild.rsto fetch the matching daemon sidecar).src-tauri/Cargo.lock: refreshed —myownmesh-core+myownmesh-signalingnow resolve tov0.1.3#47e36655, all 63 other deps unchanged.Why
When loading a model freezes the machine, the colocated
myownmesh servedaemon is starved too, so peers tear this node down after the ~90 s heartbeat grace. Before v0.1.3, the woken node didn't re-advertise and kept stale sessions, so it only reappeared on the next steady-state advertisement — up to 5 minutes later. MyOwnMesh v0.1.3 (mrjeeves/MyOwnMesh#19) makes the node re-announce on wake and clear its own zombie sessions, so neighbors reconnect in ~1–2 s.Verification
cargo updateresolved the new tag cleanly (only the two mesh crates changed; identical dependency graph), and all daemon sidecar assets (linux x86_64/aarch64, windows x86_64, macOS x86_64/aarch64) are published on the v0.1.3 release, sobuild.rscan fetch the sidecar on every CI target. Full build/test is left to CI, which has the Tauri/webkit toolchain.https://claude.ai/code/session_017UZ6AKBqV2ae2E6XbyoAgq
Generated by Claude Code