-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[24.0] Extend regex groups in stdio regex matches #17016
[24.0] Extend regex groups in stdio regex matches #17016
Conversation
1b24b33
to
6c5fc79
Compare
025429a
to
7fdf763
Compare
327028a
to
6646dfb
Compare
The failing test seems relevant. Very exciting work though - this is awesome. |
Should we use CDTA in the examples? |
Thanks @mvdbeek :) @bgruening CDTA? |
I think we can't use CTATA in attributes, isn't it? |
a782c01
to
101cba0
Compare
@hujambo-dunia could you have a look at the failing client unit test? |
Co-authored-by: Marius van den Beek <m.vandenbeek@gmail.com>
lets see if this conflicts with black
615a817
to
352f18c
Compare
Agreed - I see what you're saying, including JohnC's commits from 5 days ago getting dropped in my last merge, and will make those adjustments shortly. |
352f18c
to
e311cc1
Compare
I'm sorry for being the annoying one here! Here's the thing: those 2 commits I mentioned are still present, and they take the code into a broken state. Even though it's for a short span of 3 commits, fixed in the forth, it is not ideal: the history doesn't tell a coherent story, and if anyone happens to end up on one of those commits (a checkout, a pause in a rebase, etc.), they may be confused. The fix is simple: reorder the commits, so that those two are followed by the fix. Then squash the three into one. Then you'll have one commit that handles those changes, without any do/undo parts. |
…ent upgrade) Upgraded component to Vue 3. Extra space removed. Remove index enumeration and indentation; separate multiple errors with border line instead. Prevent metadata from printing when there is no value. Rebased and edited/removed accidental 'merge conflict markers' in file
e311cc1
to
ea359c3
Compare
@hujambo-dunia The rebase look correct - thank you! |
Co-authored-by: M Bernt <m.bernt@ufz.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Waiting for the tests before merging (there may will be failures that are unrelated). Thanks again for addressing the comments and handling the rebase, @hujambo-dunia!
@jdavcs it helps to have such a great teacher! |
Can you, please, take a look at the client linting error? |
Allow to extend groups in the matching regex in the description.
Wondering where to description is shown? Is this broken? The screenshot shows the job info page which shows that the
Job Messages
are shown as dict and the job details in the history showAn error has occurred with this dataset
.How to test the changes?
(Select all options that apply)
License