[X] I have already searched this project's issues to determine if a bug report has already been made.
What happened?
We use the pf-tunnel command in our organization to help facilitate a "local development" environment. Using pf-tunnel worked on my machine however when using it on MacOS with an ARM chip one of my team members was met with the following output:
This output was consistent whether running pf-tunnel in the context of the enclosing script or vanilla in the terminal. From inspecting the script it looks like the usage block only prints when there's an error with the inputs, so wondering if there might be some difference in the argument parsing between Linux and Mac machines
Version
main (development branch)
What primary components of the stack are you seeing the problem on?
nix
Relevant log output
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Prior Search
What happened?
We use the
pf-tunnel
command in our organization to help facilitate a "local development" environment. Usingpf-tunnel
worked on my machine however when using it on MacOS with an ARM chip one of my team members was met with the following output:This output was consistent whether running
pf-tunnel
in the context of the enclosing script or vanilla in the terminal. From inspecting the script it looks like the usage block only prints when there's an error with the inputs, so wondering if there might be some difference in the argument parsing between Linux and Mac machinesVersion
main (development branch)
What primary components of the stack are you seeing the problem on?
nix
Relevant log output
No response
Code of Conduct