Skip to content

[BUG] - always reporting "No prediction jobs finished. Waiting before retry 1.0s" #240

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

Open
AnqiXiong opened this issue Feb 17, 2025 · 1 comment
Labels
probable bug Marks bug reports where the reported issue has not yet been confirmed/reproduced

Comments

@AnqiXiong
Copy link

Bug description
I'm having an issue with the SIRIUS software. The interface has become unresponsive. I checked the log file, and it keeps showing messages like "No prediction jobs finished. Waiting before retry 1.0s", indicating that the software is waiting for prediction tasks to complete but they seem to be stuck. I've tried waiting for a while, checking my computer's performance, and using shortcut keys, but none of these have resolved the problem. I also considered that network - related issues might be causing this, such as an unstable or interrupted connection since some prediction tasks may require online data access. I'm not sure what to do next and would appreciate any help or advice.

Image

Image

Image

@AnqiXiong AnqiXiong added the probable bug Marks bug reports where the reported issue has not yet been confirmed/reproduced label Feb 17, 2025
@mbiscotti-hub
Copy link

I am having the same issue. I'm running a job with high molecular weight compounds that has taken several days. I am worried that cancelling the job will lead to losing all of the information. My job is frozen at 99% so I would very much like to figure this out without rerunning the job

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
probable bug Marks bug reports where the reported issue has not yet been confirmed/reproduced
Projects
None yet
Development

No branches or pull requests

2 participants