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

Auto Synchronisation every 2-3 mins [Don't know if its a bug or a feature] #4465

Closed
soorajsprakash opened this issue Feb 3, 2021 · 7 comments
Labels
stale An issue that hasn't been active for a while...

Comments

@soorajsprakash
Copy link

soorajsprakash commented Feb 3, 2021

Environment

Joplin version: 1.7.10 (tested with previous release too.)
Platform: Linux
OS specifics: Manjaro gnome 20.2.1

Steps to reproduce

  1. Set Synchronisation Interval as per your desire from Options > Synchronisation > Synchronisation Interval (I've set it to 30mins)
  2. Create a note, do something.
  3. You get to see that it starts Syncing about every 2mins [ Don't know if it was intentional or a bug, as Syncing is healthy ]
    Initially I thought it was syncing locally, as auto save in wordprocessors, But then I synced my Android joplin app, and the latest changes I made in note on joplin-desktop was right there.

2min

3min

See, the pic shows auto sync of notes in 2 & 3 mins.

Describe what you expected to happen

Although Syncing frequently is healthy, it defeats the purpose of setting the Synchronisation Interval.

Logfile

log.txt
(attached log file, but the screenshots are taken before during class, so time wont match.)

@soorajsprakash soorajsprakash added the bug It's a bug label Feb 3, 2021
@laurent22 laurent22 removed the bug It's a bug label Feb 3, 2021
@soorajsprakash
Copy link
Author

so, if it isn't a bug, shall I close the issue?

@alexanderadam
Copy link

so, if it isn't a bug, shall I close the issue?

I wanted to know the same once and nowadays I believe the removal of the tag is required to enable 🤖 stalebot-spamming (i.e. here, here, here, here, here, here or here).

I guess since bugs (issues with the bug label) usually wouldn't magically disappear, stalebot wouldn't automatically close them.
But the maintainers would like to have issues automatically closed anyway — even if the bugs aren't fixed yet.
So this way they can have both (at least if no one wrote something in this issue for a while — which is easy if your issue will be ignored).

This is not a complain (just a possible explanation) and I can understand this in a way, since it requires manpower and time to development or fix something and the amount of sponsors is low, too.

Personally I'm happy with the app, even if that means to accept some bugs or missing features. 😉

@stale
Copy link

stale bot commented Mar 19, 2021

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@stale stale bot added the stale An issue that hasn't been active for a while... label Mar 19, 2021
@Karob2
Copy link

Karob2 commented Apr 19, 2021

I'm on 1.7.11, Windows 10, and I noticed that the app is still syncing (with Dropbox) even after setting the synchronization interval to "Disabled".

@stale stale bot removed the stale An issue that hasn't been active for a while... label Apr 19, 2021
@Karob2
Copy link

Karob2 commented Apr 20, 2021

I assume the frequent synchronization is also why I'm getting a "too_many_requests" error returned:

Last error: Error: POST files/upload: Error (429): {"error_summary": "too_many_requests/.", "error": {"reason": {".tag": "too_many_requests"}, "retry_after": 15}}

@stale
Copy link

stale bot commented Jun 2, 2021

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@stale stale bot added the stale An issue that hasn't been active for a while... label Jun 2, 2021
@stale
Copy link

stale bot commented Jun 9, 2021

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this as completed Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale An issue that hasn't been active for a while...
Projects
None yet
Development

No branches or pull requests

4 participants