-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Exec KRM function interpreted language script shebang must be on the first line error message improvement #5501
Comments
This issue is currently awaiting triage. SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Eschewed features
What would you like to have added?
I think it will be nice to improve on current error message. At the moment if Exec KRM function trying to execute script, e.g Python or BASH with first line being empty or with the comment it will fail. It is expecting a shebang on the very first line of the script, the error message will be:
Error: couldn't execute function: fork/exec <here you'll see path to your script>: exec format error
Why is this needed?
I understand that under normal circumstances one will be expected to have a shebang on the very first line of the script. In case if it is not - the error message that has hints on shebang will improve user experience and troubleshooting. For example:
Error: couldn't execute function: fork/exec <here you'll see path to your script>: exec format error, check if shebang is on the first line
Can you accomplish the motivating task without this feature, and if so, how?
Yes! Current error message not too helpful but it doesn't prevent one from further troubleshooting
What other solutions have you considered?
None
Anything else we should know?
No response
Feature ownership
The text was updated successfully, but these errors were encountered: