Skip to content
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

GitHub Actions: periodic flyctl: not found #57

Open
seeARMS opened this issue Apr 18, 2024 · 6 comments
Open

GitHub Actions: periodic flyctl: not found #57

seeARMS opened this issue Apr 18, 2024 · 6 comments

Comments

@seeARMS
Copy link

seeARMS commented Apr 18, 2024

We have a GitHub action workflow that deploys our Fly instance upon git push.

Periodically and seemingly randomly, the workflow quickly fails with the following error:

Run superfly/[email protected]
  with:
    args: deploy --remote-only --strategy immediate --wait-timeout 360 --config ./packages/api/fly.staging.toml --dockerfile ./packages/api/Dockerfile --ignorefile .dockerignore --app paragraph-feature-par-[2](https://github.com/paragraph-xyz/monorepo/actions/runs/8740055948/job/23982824117#step:5:2)645 -e COMMIT=${GITHUB_SHA} --vm-size shared-cpu-2x
  env:
    FLY_API_TOKEN: ***

sh: flyctl: not found

Flyctl should never not be found, so I don't know why this is occurring.

@matthewlehner
Copy link

@seeARMS it looks like you're pinned to v1.1 of the action which was released almost 4 years ago. We've made some improvements since then!

Could you try updating to the latest version, either v1, which will automatically pick up minor versions, or v1.5 if you want to lock to a specific version. I think this will fix things up for you.

specifically this line in your workflow:

      - uses: superfly/flyctl-actions/setup-flyctl@v1

@matthewlehner
Copy link

I'm going to close this for now, if you're still running into this in the future, feel free to bump it!

@seeARMS
Copy link
Author

seeARMS commented Apr 25, 2024

I upgraded to v1 but still encountering this:

image

@seeARMS
Copy link
Author

seeARMS commented Jun 13, 2024

Still continuing to happen:

image

A restart of the workflow fixes it, so this seems to happen intermittently.

@seeARMS
Copy link
Author

seeARMS commented Jul 5, 2024

Happening about once a day now.

@matthewlehner matthewlehner reopened this Jul 7, 2024
@matthewlehner
Copy link

@seeARMS I haven't been able to reproduce this, do you have any other context that might help me see what's happening?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants