Reconciliation for utBotGenerationTimeoutInMillis: Long.MAX_VALUE is …#1506
Merged
Vassiliy-Kudryashov merged 1 commit intoDec 12, 2022
Merged
Conversation
…far too big for maximum, let's use Int.MAX_VALUE instead
Markoutte
approved these changes
Dec 12, 2022
Vassiliy-Kudryashov
deleted the
Vassiliy-Kudryashov/timeoutMillis_reconciliation
branch
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…far too big for maximum, let's use Int.MAX_VALUE instead
Description
Spinner model expect Int.MAX_VALUE as maximum, in settings it was limited with Long.MAX_VALUE
Fixes #1438
Type of Change
How Has This Been Tested?
Manual Scenario
See the relevant issue: utBotGenerationTimeoutInMillis=60000000000000 in settings.properties should work as Int.MAX_VALUE with no exception.
Checklist (remove irrelevant options):