panic: close of closed channel

Questions / Help Build debugging
1

Hi there!

I am trying to build an app that works on heroku here, with the turboku I get several:

"v0 failed - Failed due to unhealthy allocations - no stable job version to auto revert to

* ***v0 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v1"

here is the log

https://pastebin.com/wqwLcaby

using the cli I get “panic: close of closed channel”

here is the log

https://pastebin.com/6W1yFvVR

any ideas how can I fix this?

2

I’m getting a similar issue.

[+] Building 3598.4s (0/1)
 => [internal] load remote build context                                                                                                                                                              3598.4s
DEBUG Remote builder heartbeat response: 202 Accepted
panic: close of closed channel

goroutine 88 [running]:
github.com/superfly/flyctl/internal/build/imgsrc.(*Resolver).StartHeartbeat.func2()
	github.com/superfly/flyctl/internal/build/imgsrc/resolver.go:496 +0x26c
created by github.com/superfly/flyctl/internal/build/imgsrc.(*Resolver).StartHeartbeat
	github.com/superfly/flyctl/internal/build/imgsrc/resolver.go:490 +0x578

It happens in 2 out of 5 docker builds.