Fix regex for Spec generation with alphanumerical data tiers #11951
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
|
Jenkins results:
|
todor-ivanov
approved these changes
Mar 28, 2024
amaltaro
approved these changes
Mar 28, 2024
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.
Fixes #11930
Status
ready
Description
While the previous changes merged in #11931 where enough to accept the final datasets and lfn of files with numbers in their data tier, it turns out workflow creation fails in the process , as the intermediate regexp of lexicon weren't updated. This fixes that.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
#11931
External dependencies / deployment changes
No