-
Notifications
You must be signed in to change notification settings - Fork 286
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
UX bug: Show a difference between zero args and empty args #1283
Comments
@schneems thanks for reporting this! I suspect the root issue is in pack, as pack is reading the processes information from the |
@natalieparellano thank you, if you can move it over that would be amazing! |
Instead of a count of the args (which seems a bit out of place in all but the zero args case), another option might be to show @schneems Also, I wonder if (as part of another issue) lifecycle should forbid empty string |
For my case that would be great. I think there might be another case where someone writes a bash tool that needs an empty arg. If we raised/disallowed an empty arg then also including some kind of escape valve. For example |
I want to work on this issue. @natalieparellano can you please assign this issue to me ? |
Hi @rizul2108 thanks for helping us out |
@rizul2108 before you try to fix this one, could you try to reproduce it with the latest main branch version? We just merged this PR, that I think it could be related but I didn't check. I do not want you to waste your time |
Ok sure I will check once |
so i should start work on fixing this this error? @jjbustamante |
Hi @rizul2108 , yes! I like the idea suggested by Ed here, to use |
Okk sure I will work on it |
Hi @rizul2108! Are you still working on this one? |
Hi @natalieparellano , @jjbustamante i am starting to work in this issue. |
Summary
I ran into an issue where (due to a buildpack version difference) one buildpack was working and one wasn't. I figured out the problem eventually, but the core issue that made debugging harder than it had to be was that lifecycle currently shows the same output for empty args
[]
as it does for args that contain no characters[""]
.Here's my original notes and investigation https://github.com/Malax/libcnb.rs/issues/49
Reproduction
Steps
Make a base buildpack:
Write a build script with non-empty args
Build it:
Produces:
Modify to empty args in the launch:
Build it:
Produces:
So even though the image produced is not identical, the output of
pack inspect
is.Current behavior
Pack inspect does shows identical output when there are no args versus when there are args with no characters.
Expected
I expected the two to produce an observable/inspectable difference in outputs because they are different (one executes, and the other does not).
I propose possibly adding arg count to the output such as:
Or possibly showing non-visible args:
Context
lifecycle version
Lifecycle:
Version: 0.11.4
platform version(s)
The text was updated successfully, but these errors were encountered: