Action recently stopped installing about hasura-action HOT 9 CLOSED

I have no idea why this is happening, we're on the same environment, using the same docker image, pulling the same script and it works for us but not you. I've pinged the hasura team at hasura/graphql-engine#5389, hopefully they'll be able to help.

from hasura-action.

Thanks for your responsiveness. The weirdest part is, it actually works if I retry it enough times.

from hasura-action.

@chrisknu does this look similar to what you faced recently? How did you debug and find the sed issue?

from hasura-action.

Possibly.

Tested it by forking the repo, switching the install location to the stable branch, and updating my action to use the fork. Its worth noting the action, in its current state, is successfully installing/running on the repo I'm working with.

Running the command line locally, committing the -n sed flag will show the output. Prior to flipping to the stable branch, the CLI command was failing.

from master:
curl -s -f -H 'Content-Type: application/json' https://releases.hasura.io/graphql-engine\?agent\=cli-get.sh\) | sed -e "s/^."$release":"([^\",}])".*$/\1/p"
yields
{"latest":"v1.2.2","prerelease":"v1.3.0-beta.4"}

from stable:
curl -s -f -H 'Content-Type: text/plain' https://releases.hasura.io/graphql-engine?agent=cli-get.sh
yields
v1.2.2%

..it didnt seem to have the % in there last time I ran this.. but does today.

Fun sidenote: the hasura/graphql-engine/cli repo lists master as the install branch but the docs list stable.

from hasura-action.

This still totally fails for me. Any ideas? did the docker image change?

from hasura-action.

It's actually working for me as well, my action is on master which is the same as latest, and uses the stable branch of hasura. Is there anything special about your setup @zallarak? Would you mind sharing the workflow configuration?

To be fair, it was also working for me when @chrisknu posted his PR. There seeem to be some inconsistencies in experience overall. Are we all running our workflows on similar setup? Mine is on Github hosted ubuntu-latest.

from hasura-action.

ubuntu-latest

 ---> Using cache
 ---> b252f417865a
Step 9/14 : RUN apk add --no-cache curl bash libstdc++
 ---> Using cache
 ---> 73e78547d5fc
Step 10/14 : RUN curl -L https://github.com/hasura/graphql-engine/raw/stable/cli/get.sh | bash
 ---> Running in e4730a8ed212
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   139  100   139    0     0    302      0 --:--:-- --:--:-- --:--:--   302

100  3482  100  3482    0     0   6895      0 --:--:-- --:--:-- --:--:--  6895
--> Getting latest version...
--> 
--> Failed while attempting to install hasura graphql-engine cli. Please manually install:
--> 
--> 2. Open your web browser and go to https://github.com/hasura/graphql-engine/releases
--> 2. Download the cli from latest release for your platform. Name it 'hasura'.
--> 3. chmod +x ./hasura
--> 4. mv ./hasura /usr/local/bin
--> 
FAILED> exiting... 
The command '/bin/sh -c curl -L https://github.com/hasura/graphql-engine/raw/stable/cli/get.sh | bash' returned a non-zero code: 1

##[error]Docker build failed with exit code 1

from hasura-action.

There seem to be an element of response on the issue I've opened in their repo. Seems like an internal thing to how the install script works. Let's wait for now I guess.

from hasura-action.

This has now been reported fixed upstream. See hasura/graphql-engine#5389 (comment). Feel free to re-open if the problem persists.

from hasura-action.