Github Actions Not Exiting

Questions / Help
1

Hey,

I’m using the fly github action:

      - run: flyctl deploy --remote-only
        env:
          FLY_API_TOKEN: ${{ secrets.FLY_DEPLOY_TOKEN }}

and I noticed that in my recent builds (no changes) the command never exits even after a successful deploy and github kills it after 6 hours. Has anything changed with the CLI’s behavior?

2 Likes
2

I’m experiencing the same with bitbucket.

3

Same here. It keeps hanging on “[2/2] Checking that … [app] is up and running”

4

^ yeah, I noticed an unexpected number of GHA minutes wasted yesterday :money_with_wings:

Regression of flyctl v0.1.47 - Cannot deploy, clone and list machines perhaps? cc @billy

1 Like
5

Tried setting it to the current version (0.1.52) like you suggested in that topic, but that doesn’t seem to fix the problem with github actions. I can deploy locally without a problem though.

1 Like
6

Same here.

1 Like
7

Having the same issue :confused:

8

Also an issue for me!

9

Getting an error when I try to deploy via Flyctl as well:

panic: assignment to entry in nil map

goroutine 232 [running]:
github.com/getsentry/sentry-go/internal/ratelimit.Map.Merge(0x14000520cc0?, 0x140008cf500?)
	github.com/getsentry/sentry-go@v0.19.0/internal/ratelimit/map.go:43 +0xd0
github.com/getsentry/sentry-go.(*HTTPSyncTransport).SendEvent(0x1400003af80, 0x1400093bb80)
	github.com/getsentry/sentry-go@v0.19.0/transport.go:548 +0x490
github.com/getsentry/sentry-go.(*Client).processEvent(0x140008c6300, 0x1400093bb80, 0x14000126c00, {0x105c17280, 0x14001104ea0})
	github.com/getsentry/sentry-go@v0.19.0/client.go:593 +0x264
github.com/getsentry/sentry-go.(*Client).CaptureEvent(...)
	github.com/getsentry/sentry-go@v0.19.0/client.go:397
github.com/getsentry/sentry-go.(*Client).CaptureException(0x14000eb5978?, {0x105c16c40?, 0x140010f0b00?}, 0x10?, {0x105c17280, 0x14001104ea0})
	github.com/getsentry/sentry-go@v0.19.0/client.go:388 +0x58
github.com/getsentry/sentry-go.(*Hub).CaptureException(0x14000520870, {0x105c16c40?, 0x140010f0b00})
	github.com/getsentry/sentry-go@v0.19.0/hub.go:260 +0xac
github.com/getsentry/sentry-go.CaptureException(...)
	github.com/getsentry/sentry-go@v0.19.0/sentry.go:54
github.com/superfly/flyctl/internal/sentry.CaptureException.func1(0x14000520870?)
	github.com/superfly/flyctl/internal/sentry/sentry.go:81 +0x8c
github.com/getsentry/sentry-go.(*Hub).WithScope(0x14000520870, 0x14000eb5a58)
	github.com/getsentry/sentry-go@v0.19.0/hub.go:200 +0x60
github.com/getsentry/sentry-go.WithScope(...)
	github.com/getsentry/sentry-go@v0.19.0/sentry.go:95
github.com/superfly/flyctl/internal/sentry.CaptureException({0x105c16c40?, 0x140010f0b00?}, {0x0?, 0x2?, 0x2?})
	github.com/superfly/flyctl/internal/sentry/sentry.go:76 +0xd0
github.com/superfly/flyctl/flaps.sendFlapsCallMetric({0x105c2a5d0, 0x14001356c90}, {0x140010f2570, 0xf}, {{0x140007e7068?, 0x105b86000?, 0x10681d5c0?}, 0x106855390?}, 0xc8)
	github.com/superfly/flyctl/flaps/flaps.go:616 +0x1f0
github.com/superfly/flyctl/flaps.(*Client).sendRequest(0x1400094f7c0, {0x105c2a5d0, 0x14001356c90}, {0x1054784dc, 0x3}, {0x140010f2570, 0xf}, {0x0, 0x0}, {0x105b86000, ...}, ...)
	github.com/superfly/flyctl/flaps/flaps.go:596 +0x2e8
github.com/superfly/flyctl/flaps.(*Client).Get(0x3b9aca00?, {0x105c2a5d0, 0x14001356c90}, {0x140013388b0, 0xe})
	github.com/superfly/flyctl/flaps/flaps.go:325 +0xd8
github.com/superfly/flyctl/internal/command/deploy.(*blueGreen).WaitForGreenMachinesToBeHealthy.func1({0x105c358a0, 0x14000b53140})
	github.com/superfly/flyctl/internal/command/deploy/strategy_bluegreen.go:276 +0xc8
created by github.com/superfly/flyctl/internal/command/deploy.(*blueGreen).WaitForGreenMachinesToBeHealthy
	github.com/superfly/flyctl/internal/command/deploy/strategy_bluegreen.go:267 +0x2a8
10

:wave: Definitely looks like something’s up! Does reverting to flyctl v0.1.51 help?

2 Likes
11

Flyctl 0.1.52 has a bug that only showed up in production use. We’ve reverted the change that caused this issue and released a new version, Flyctl 0.1.53, that should be good to go. Sorry about this!

4 Likes
12

Looks good on my end now. Thanks!

13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.