kuro icon indicating copy to clipboard operation
kuro copied to clipboard

Published 20 hours ago • verified publisher icon davidsmorais

[Bug 🐞]: Syncing Frequently Pauses

Open Alexhuszagh opened this issue 2 years ago • 8 comments

Bug Title 🐞

Describe the bug When using Kuro for a long period, it frequently says "Your changes were saved but syncing is paused. Refresh this page to sync your changes." However, clicking refresh does not sync the changes, and only logging out and logging back in (or rebooting) seems to refresh syncing.

Reproduction Steps

  1. Use Kuro for a long period (I believe on multiple devices as well).

Expected Behavior Syncing should not break, even over long sessions.

Screenshots Syncing Issue

Technical Info (please complete the following information)

  • OS: Fedora 36
  • Kuro Version: 8.1.0

cc: @davidsmorais

Alexhuszagh avatar May 27 '22 14:05 Alexhuszagh

Thanks for reporting @Alexhuszagh

I've been praying to reproduce this for 2 days now and I never get this pop up message :cry:

How long would you say you leave Kuro open before this message pops ?

davidsmorais avatar Jun 01 '22 08:06 davidsmorais

It's weird, it's very unusual but it normally happens when I'm also syncing between different devices and when it's open for more than say, 30 min.

Alexhuszagh avatar Jun 01 '22 13:06 Alexhuszagh

I'll see if I can get a more reproducible test case, because I understand this is very much like finding a needle in a haystack (and very difficult for you, as a maintainer, to fix until then).

Alexhuszagh avatar Jun 01 '22 14:06 Alexhuszagh

I'll see if I can get a more reproducible test case, because I understand this is very much like finding a needle in a haystack (and very difficult for you, as a maintainer, to fix until then).

And the fact that I'm 98% sure that this is on To-Do's web client managed my Microsft themselves :upside_down_face:

davidsmorais avatar Jun 01 '22 15:06 davidsmorais

Just wondering: has this been patched or is this still an upstream issue?

Alexhuszagh avatar Jul 27 '22 20:07 Alexhuszagh

I've closed it because:

  • No activity in the issue, assumed it was fixed in 8.1.3
  • From your screenshot, this looks like something happening on Microsoft's side and there's not much I can to here...

davidsmorais avatar Jul 27 '22 21:07 davidsmorais

Can you re-open this then and add an upstream label, signifying that there's nothing to be done but waiting on Microsoft to fix their end? Because this is still an issue I believe (my laptop is currently in the shop, so I can't test it currently, currently doing all my dev work on WSL2).

Alexhuszagh avatar Jul 27 '22 21:07 Alexhuszagh

Yeah, makes sense to leave this as a future heads up for other users and to avoid repeated issues

Done :heavy_check_mark:

davidsmorais avatar Jul 28 '22 10:07 davidsmorais