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

"In Use" and "Not In Use" suspension preferences could prevent computing indefinitely #4939

Open
2 of 3 tasks
Vulpine05 opened this issue Sep 29, 2022 · 4 comments · Fixed by #4955 or #5270
Open
2 of 3 tasks

Comments

@Vulpine05
Copy link
Contributor

Vulpine05 commented Sep 29, 2022

Describe the bug
BOINC has the option to suspend computer usage in two ways: When the computer is in use (IU), and when it is not in use (NIU). It is possible to enable suspension for both IU and NIU at the same time. It is also possible to set the values for each such that BOINC will never work on any tasks.

Steps To Reproduce

  1. Open BOINC Manager->Options->Preferences.
  2. Set IU time to 0.08, and NIU to 0.05 minutes. Save changes.

Expected behavior
A message should let the user know to change the settings, and these settings should not be saved.

System Information

  • OS: Windows 10
  • BOINC Version: 7.20.2, but I have seen this in earlier versions.

Additional context
This bug can occur in three locations:

@Vulpine05
Copy link
Contributor Author

I had started working on the Manger change via #4634. I should be able to fix this in the Manager and Client. I think the fix for the client will prevent any web preferences from propagating to a client, but having an error message when saving web preferences would be better.

With that said, I am not familiar with php. Also, even if I figure out how to fix it via web, I don't know how to test and verify. If anyone is willing and able to do one or the other, please let me know.

@davidpanderson
Copy link
Contributor

I don't think this is necessary.

@Vulpine05
Copy link
Contributor Author

This issue has one more item that hasn't been completed. I cannot reopen the issue. @davidpanderson, could you reopen please?

@RichardHaselgrove
Copy link
Contributor

Happened to catch your message while I was at a screen.

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