panic: nested instrument span!

[wsvincent]

I suspect this is something deep within the flyctl but I’m this morning getting the following error messages when I try to run fly launch. I’m on v0.0.554 darwin/arm64 Commit: aa9b9ad3 BuildDate: 2023-05-05T03:45:30Z.

$ fly launch
Creating app in /Users/wsv/Sites/Github-Tutorial-Code/fly-helloworld
Scanning source code
Detected a Django app
? Choose an app name (leave blank to generate one): django-helloworld-example
automatically selected personal organization: Will Vincent
panic: nested instrument span!

goroutine 26 [running]:
github.com/superfly/flyctl/internal/instrument.(*ApiInstrumenter).Begin(0x12e38e9e8?)
        github.com/superfly/flyctl/internal/instrument/call.go:61 +0xd0
github.com/superfly/flyctl/api.(*Client).RunWithContext(_, {_, _}, _)
        github.com/superfly/flyctl/api@v0.0.0-20220708073423-b6d7c3cf5161/client.go:121 +0x6c
github.com/superfly/flyctl/api.(*Client).GetOrganizationBySlug(0x14000ccd7c0?, {0x105dacca8, 0x14000b88060}, {0x14000b20748, 0x8})
        github.com/superfly/flyctl/api@v0.0.0-20220708073423-b6d7c3cf5161/resource_organizations.go:77 +0x164
github.com/superfly/flyctl/internal/build/imgsrc.EagerlyEnsureRemoteBuilder({0x105dacca8, 0x14000b88060}, 0x0?, {0x14000b20748, 0x8})
        github.com/superfly/flyctl/internal/build/imgsrc/docker.go:484 +0x50
created by github.com/superfly/flyctl/internal/command/launch.run
        github.com/superfly/flyctl/internal/command/launch/launch.go:166 +0x604

[syx]

I’ve been having the same issue as well, this afternoon. Any solutions so far?

[MatthewIngwersen]

Hey @wsvincent and @syx, that’s a bug introduced in flyctl v0.0.554. The change causing it was reverted soon after and released in v0.0.555. If you upgrade, I think it will get sorted out.

(If you’re using Homebrew, I think v0.0.554 is still the newest version available, unfortunately. If it’s not possible to temporarily downgrade through Homebrew, you could grab a binary release from GitHub for the time being.)

Sorry you ran into this!

[wsvincent]

Thanks for the quick reply @MatthewIngwersen . Figured as such.

[syx]

thank you for the speedy solution, works now!