-
Notifications
You must be signed in to change notification settings - Fork 50
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
Attempt to use null separation when invoking 'env' #684
Draft
cottsay
wants to merge
1
commit into
master
Choose a base branch
from
cottsay/null-sep-env
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
01e19fe
to
33b30ae
Compare
This approach eliminates the heuristics for handling newlines in environment variables on platforms where 'env' supports null separation via the '-0' flag. The 'sh' shell will first attempt to use null separation and will fall back to the prior behavior.
33b30ae
to
5fc80a7
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #684 +/- ##
==========================================
- Coverage 87.28% 87.18% -0.10%
==========================================
Files 68 68
Lines 3949 3973 +24
Branches 760 763 +3
==========================================
+ Hits 3447 3464 +17
- Misses 396 403 +7
Partials 106 106 ☔ View full report in Codecov by Sentry. |
christophebedard
pushed a commit
to christophebedard/action-ros-ci-almalinux-test
that referenced
this pull request
Jan 22, 2025
Signed-off-by: Christophe Bedard <christophe.bedard@apex.ai>
christophebedard
pushed a commit
to christophebedard/action-ros-ci-almalinux-test
that referenced
this pull request
Jan 22, 2025
Signed-off-by: Christophe Bedard <christophe.bedard@apex.ai>
christophebedard
pushed a commit
to christophebedard/action-ros-ci-almalinux-test
that referenced
this pull request
Jan 22, 2025
Signed-off-by: Christophe Bedard <christophe.bedard@apex.ai>
Just to mention it here: I tested this and it fixes ros2/rosidl_typesupport#162, see ros2/rosidl_typesupport#162 (comment) |
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.
This approach eliminates the heuristics for handling newlines in environment variables on platforms where 'env' supports null separation via the '-0' flag. The 'sh' shell will first attempt to use null separation and will fall back to the prior behavior.
The existing heuristics make some pretty critical assumptions about environment variable naming that can misbehave in extremely cryptic ways.
A specific example is that the regular expression used to determine if a line contains a valid environment variable name is based on the characters that Bourne shells accept when setting environment variables, but the set of acceptable characters in Linux is wider and the shells may still pass those variables through to subprocesses even though they don't support setting new variables with such names. The existing code will treat these variables as a continuation of the previous variable. If the previous variable is one that we depend on, such as
AMENT_PREFIX_PATH
, we can see cryptic problems during the build that don't appear to be related to colcon.The heuristics were added in #128 to handle multi-line environment variables.