Hi everyone. I have been happily using firstname.lastname@example.org with a convenience python image for quite some time. We are now changing to a custom base image, where we manually install curl and jq, and things seem not to work anymore (see stack below). I am not really sure where to get started for troubleshoot this, any pointers would be greatly appreciated.
#!/bin/bash -eo pipefail
Workaround for Windows Support
For details, see:
eval printf ‘%s’ “$SLACK_SCRIPT_NOTIFY”
BASH_ENV file: /tmp/.bash_env-6447d8cb93d1e71ebc031dc1-0-build
Exists. Sourcing into ENV
Checking For JQ + CURL
Exited with code exit status 23
CircleCI received exit code 23
The error code indicates that there is an error with a command that is being executed within the shell. Without more detail, it is not possible to say what is generating the error or what the error means.
For curl error 23 is “Failed writing body” This can be thrown if the output of curl is being buffered and piped to another program that decides that it can close the pipe while curl is still sending data. Using curl’s -o flag can cause the same error if a file is provided that has to be created in a directory that does not yet exist.
There is no way to make the orb more verbose, but the detail you have provided now allows a good guess at the problem by looking at the orb source code.
Can you check that you have write access to /usr/local/bin, the script seems to want to use curl to download a copy of jq and place it at /usr/local/bin/jq via curl’s -o setting. As this can throw error 23 due to access issues it would be a good place to start.
If you have the time you could validate the issue by taking the code from line 211 of the source code found here
and place it in your test step to see what happens in your environment.