Skip to content

Conversation

@ferd
Copy link
Owner

@ferd ferd commented Jul 5, 2025

No description provided.

ferd added 27 commits December 4, 2024 12:57
Every time a value is changed, parse it to update a value in the
background, and possibly refresh checks (eg. node connectivity).

This clarifies some phases of each argument's parsing and steps across 3
states (managed by data contents) around attributes (`unparsed` => need
to check, `val` => parsed, `line` => ready to display).

Node validation can time out after a while over the network, so do that
check with an upper boundary on execution time.

Also, to avoid inconsistencies on cursor positionment, keep label length
constant.
Because of how conflicts are transmitted file by file, there's always
potential for a delete conflict to happen, where 2 or more hosts have
concurrently deleted a file without synchronization.

We could _merge_ both deletes and bump the version, but this could run
the risk of ignoring trailing conflicts in a transfer. Instead, we go
explicit by adding deletion conflict messages to the protocol, and
creating empty conflict files when such conflicts are detected. The user
then has to delete the conflict file to resolve everything.
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.

2 participants