Disclosure: I maintain the experimental open-source project DiagSift mentioned below. This is a request for pilot feedback, not a product promotion.
I am testing whether a small project-neutral diagnostic manifest could be useful in real rclone troubleshooting, and I am looking for 1-2 maintainers or experienced contributors willing to try one short pilot.
The pilot is deliberately narrow. The manifest only:
runs rclone version
records OS and architecture
reads one explicitly named diagnostic log file
Before anything is collected, DiagSift shows the exact resolved plan, limits and paths. Collection creates an ordinary ZIP locally. There is no upload or telemetry, and the user can inspect the ZIP locally before deciding whether to share it.
I am not proposing that rclone adopt or integrate DiagSift. I am simply trying to learn whether this workflow would make a real support case clearer or safer, or whether it is unnecessary or too restrictive.
A pilot would involve running validate, plan, collect, and inspect against one real troubleshooting scenario and reporting only non-sensitive observations. No diagnostic bundle needs to be sent to me. Redaction reduces risk but is not a guarantee.
Source / pre-release:
Pilot tracking:
If anyone is willing to test it, I have a small three-file pilot package and instructions ready. Feedback that the idea is unnecessary or poorly scoped is equally useful. Thanks.