Fixes regex matching bug #473
Merged
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
nickchadwick-noaa
approved these changes
Jun 15, 2023
Merged
nickchadwick-noaa
pushed a commit
that referenced
this pull request
Jun 16, 2023
I found and fixed two additional issues preventing RnR from completing successfully. These, just like the last fixes I created a PR for a few days ago (#473), must have been hard-coded in place on TI resources when developing and were never added back to the committed code-base. ----------------- * Fixes regex matching bug * Fixes a few more issues preventing rnr's success
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.
The replace and route execution of the
initialize_pipelinelambda began failing in TI a few days ago. I'm guessing I must have had a hard-coded in-place change directly on TI from back when I was developing and testing the replace and route code. Again as my guess, it's likely that TI was just redeployed a couple of days ago with the rnr code that had been recently merged into it.Anyhow, this small change will fix the issue.