Created confirm_thread_creation_timeout config #3304
Merged
Conversation
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
|
Seems like there's a merge conflict. I don't have permission to make the necessary changes, but it looks like this could be fixed by changing |
v4.1.0 Release
* Update Dockerfile * Use the slim-bookworm image, refactored some steps * Disable user login * Capitalize comment --------- Co-authored-by: Taku <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This PR adds a config variable allowing users to set their own timeout for the confirm_thread_creation.
This required the addition of an
intscategory of configs for conversion as well.To make the lower and upper limits work, I have added a new system allowing the setting of limits. This will be compared by a python statement like
lower <= value <= upperonly for keys specified. It will be tested when the value is set, and reverts to the previous value if invalid.I have added a description in the json file, along with adding this config to the notes of all other related configs.