Support BSD sed and older bash in test rule.#112
Merged
varshaprasad96 merged 1 commit intooperator-framework:mainfrom Nov 18, 2021
Merged
Support BSD sed and older bash in test rule.#112varshaprasad96 merged 1 commit intooperator-framework:mainfrom
varshaprasad96 merged 1 commit intooperator-framework:mainfrom
Conversation
BSD sed (as shipped with MacOS) does not support `+` nor `\+` in regular expressions.
However it does support `\{1,\}` which does the same thing and is also supported by GNU sed.
Moreover, bash 3.2 (as shipped with MacOS) does not seem to support `source <(...)`, it seems to just do nothing.
Using plain eval seems to do the trick though.
Member
Author
|
/assign @fabianvf |
Pull Request Test Coverage Report for Build 1439360561
💛 - Coveralls |
fabianvf
approved these changes
Nov 17, 2021
Member
fabianvf
left a comment
There was a problem hiding this comment.
/lgtm
This is working for me on Fedora as well
6 tasks
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
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.
BSD sed (as shipped with MacOS) does not support
+nor\+in regular expressions.However it does support
\{1,\}which does the same thing and is also supported by GNU sed.Moreover, bash 3.2 (as shipped with MacOS) does not seem to support
source <(...), it seems to just do nothing.Using plain eval seems to do the trick though.
Symptom of the former issue is:
And of the latter:
(even though the binaries are fetched by
setup-envtest)Fixes: #117