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

Web GUI is the only way to review "Failed Files" #789

Open
seniorm0ment opened this issue May 9, 2021 · 3 comments
Open

Web GUI is the only way to review "Failed Files" #789

seniorm0ment opened this issue May 9, 2021 · 3 comments

Comments

@seniorm0ment
Copy link

Description of the issue

There is no way to review files that are stuck/failed in the sync process for whatever reason, unless you enter through the Web GUI.
To be clear by failed files, I mean files that fail to sync due to various reasons such as naming schemes, storage space, etc.

Reproduction Steps

Wait/force a file to get stuck/failed, the file is now stuck and you cannot view why it is failed unless you go to the web gui (which is a bit tedious on mobile).

Version Information

  • App Version: Syncthing-Fork 1.15.1.0 (F-Droid)
  • Syncthing Version: v1.15.1
  • Android Version: Android 10
  • Device manufacturer: LG
  • Device model: v40

Device platform info

Can't get this atm, I don't think it's needed though but if so lmk I can grab it when I have time.

Android Log

Can't get this atm, I don't think it's needed though but if so lmk I can grab it when I have time.

@Catfriend1
Copy link
Owner

Yes , can be improved. Currently, we only show critical "big" system failures with a red text in the folder view but don't have an UI to review failed items. This should be easy to do and has to placed in the right place of the screens to not clutter the interface.

@Catfriend1 Catfriend1 changed the title No Way To Review Failed Files Web GUI is the only way to review "Failed Files" Sep 12, 2021
@Catfriend1
Copy link
Owner

"There is a way", so the title "No way..." wasn't correct.

@xeruf
Copy link
Contributor

xeruf commented Nov 19, 2022

Maybe they can be intermediately listen in "Recent changes"? That's where I searched intuitively.
This issue is bugging me right now actually ^^

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