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

Force start for n hours #1184

Open
jtagcat opened this issue Nov 29, 2024 · 3 comments
Open

Force start for n hours #1184

jtagcat opened this issue Nov 29, 2024 · 3 comments

Comments

@jtagcat
Copy link

jtagcat commented Nov 29, 2024

Description of the issue

Either I forget or I have to leave before syncing1 finishes. I have to instruct users to find hte app, go to STATUS and switch it to `FOLLOW RUN CONDITIONS'.

Proposal

Allow setting force conditions for n hours. Either by a button under STATUS (better UX) or an app setting to always revert after a period.

Footnotes

  1. The app needs the inital setup to be clicked through (next-next-next), and then continues where it left off. Or some certain devices, battery optimizations killed the radio star.

@jtagcat
Copy link
Author

jtagcat commented Nov 29, 2024

Related: #1025

@NA0341
Copy link

NA0341 commented Dec 5, 2024

Wouldn't it be a better Solution to run until Everything is synced?
In other words: Pause at first "Sync complete" status.

And an optional time interval for Syncthing to run after "Sync complete".

@jtagcat
Copy link
Author

jtagcat commented Dec 7, 2024

100% synced may never happen: a device offline, a conflict, filesystem incompatibility, other issues. On the contrary, the status may start out as 100% synced, but as the local files are scanned and peers exchange metadata, it might go down-and-100% etc.

This is meant to kickstart a was-offline-for-a-while device. Getting to 80% or 90% is success. The rest can happen as part of regular syncing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants