[TASK] Increase size of database field extra_warning #195
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
georgringer
approved these changes
Jul 21, 2021
peterkraume
added a commit
to peterkraume/t3monitoring
that referenced
this pull request
Sep 22, 2021
* [BUGFIX] Return proper type in Symfony console commands Fixes: georgringer#183 * [TASK] Increase size of database field extra_warning
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
2B59
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.
If there are too many warnings in the reports module of the client, there might occur an error when client data is updated because the database field
extra_warningis too small.This happens especially when there are many warnings about files flagged as missing and/or conflicting redirects.
This patch increases the size from
texttomediumtext.