🐛 [Frontend] Fix Automatic Shutdown = 0
#6372
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
odeimaiz
requested review from
GitHK,
pcrespov,
sanderegg and
matusdrobuliak66
matusdrobuliak66
approved these changes
Sep 16, 2024
GitHK
approved these changes
Sep 16, 2024
sanderegg
reviewed
Sep 17, 2024
Not that I know of. You would have seen a call to |
|
jsaq007
approved these changes
Sep 17, 2024
29 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
reported by @cosfor1
If, in the user preferences, the "Automatic Shutdown of Idle Instances" is set to 0, the Idling tracker should never start.
Currently, as soon as the service starts, the frontend will ask the backend if it's inactive, the backend will say, "yes, it's inactive", and the frontend will react as the user was Idle, closing the project.
Related issue/s
How to test
Dev-ops checklist