fix: verify tag name length upon creation #40804
Merged
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.
Description
There is currently no input validation on the length of the tag name.
On a system using sqlite this can result in super long tag names and can result in crashes all over the place. But it is sqlite - not production critical.
On systems using other dbs we see the data being cut of (potentially exceptions?) which does not lead to crashes.
Never the less proper input validation is the way
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: