Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restart of Syncthing with receive-encrypted folder creates sync-conflicts, adds as unexpected items #7152

Closed
calmh opened this issue Nov 24, 2020 · 0 comments
Labels
bug A problem with current functionality, as opposed to missing functionality (enhancement) frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion
Milestone

Comments

@calmh
Copy link
Member

calmh commented Nov 24, 2020

  1. Share a folder with encryption from A to B
  2. On B, in the accept dialog, set the folder to receive-encrypted and disable watching, scan only once a day
  3. Let files sync (this required a restart, because the other side has the "doesn't start index sender" bug.)
  4. Observe everything is beautiful.
  5. Restart Syncthing on B.

Screenshot 2020-11-24 at 23 21 45

Screenshot 2020-11-24 at 23 23 57

It seems every restart adds about one new folder content as sync conflicts and then unexpected items.

(In this, A is v1.12.0-rc.3.dev.22.g5d2c83a7 and B is v1.12.0-rc.3.dev.27.ge6595c1a)

@calmh calmh added bug A problem with current functionality, as opposed to missing functionality (enhancement) needs-triage New issues needed to be validated labels Nov 24, 2020
@calmh calmh changed the title Restart of Syncthing with receive-encrypted folder discovers all items as "unexpected" Restart of Syncthing with receive-encrypted folder creates sync-conflicts, adds as unexpected items Nov 24, 2020
imsodin added a commit to imsodin/syncthing that referenced this issue Nov 25, 2020
@imsodin imsodin removed the needs-triage New issues needed to be validated label Nov 25, 2020
@calmh calmh closed this as completed in bf7d03d Nov 25, 2020
@calmh calmh added this to the v1.12.1 milestone Nov 27, 2020
SimonPickup added a commit to MobiusSync/syncthing that referenced this issue Jan 18, 2021
v1.12.1

Bugfixes:

- syncthing#7075: Invalid names are allowed and "auto accepted" in folder root path on Windows
- syncthing#7122: Sometimes indexes for some folders aren't sent after starting Syncthing
- syncthing#7137: [Untrusted] Remove Unexpected Items leaves things behind
- syncthing#7138: Wrong theme on selection
- syncthing#7144: Quic spamming address resolving
- syncthing#7152: Restart of Syncthing with receive-encrypted folder creates sync-conflicts, adds as unexpected items
- syncthing#7153: Deleted locally changed items still shown as locally changed

Enhancements:

- syncthing#4824: Allow specifying remote expected web UI port which would generate a href somewhere
- syncthing#7117: Ignore fsync errors when saving ignore files
@st-review st-review added the frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion label Nov 26, 2021
@syncthing syncthing locked and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug A problem with current functionality, as opposed to missing functionality (enhancement) frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion
Projects
None yet
Development

No branches or pull requests

4 participants
@calmh @imsodin @st-review and others