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

[QA] Win10 VFS: Client hangs in state Waiting #8218

Closed
jnweiger opened this issue Nov 9, 2020 · 4 comments
Closed

[QA] Win10 VFS: Client hangs in state Waiting #8218

jnweiger opened this issue Nov 9, 2020 · 4 comments
Labels
p2-high Escalation, on top of current planning, release blocker
Milestone

Comments

@jnweiger
Copy link
Contributor

jnweiger commented Nov 9, 2020

Seen with 2.7.0 on Win10 with VFS enabled

Sometimes, when a new folder appears on the server, the client is unable to sync. Hard to reproduce.
Happened while retriggerning #8217
The client enters a waiting state, no network activity for over 10 minutes before I filed the report.

image

Failed attempts to make it sync again:

  • Pause sync, resume sync
  • logout / login does not fix the state.
  • switch from virtual to physical.

Quit client, restart client succeeds in making it sync again. The missing folder appears.

@jnweiger
Copy link
Contributor Author

jnweiger commented Nov 9, 2020

logs.zip

@jnweiger jnweiger mentioned this issue Nov 9, 2020
63 tasks
@michaelstingl michaelstingl added the p2-high Escalation, on top of current planning, release blocker label Nov 10, 2020
@michaelstingl michaelstingl added this to the 2.7.0 milestone Nov 10, 2020
@michaelstingl
Copy link
Contributor

@TheOneRing any clue what happens during "Waiting"? Anything in the logs?

@TheOneRing
Copy link
Member

What is printed in the logs while the client is waiting?
(The logs don't contain lines like, now we display "Waiting..." ) :D

@TheOneRing
Copy link
Member

Can't reproduce

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2-high Escalation, on top of current planning, release blocker
Projects
None yet
Development

No branches or pull requests

3 participants