#Engine Panic on `v0.15.4` with gc disabled

1 messages · Page 1 of 1 (latest)

jagged umbra
#

I've got an engine.toml I'm mounting to my ephemeral dagger engine on startup, with gc disabled as the docs suggest:

[worker.oci]
gc = false

It looks like func getGCPolicy is returning a nil slice or zero length slice:

panic: runtime error: index out of range [-1]
goroutine 1 [running, locked to thread]:
github.com/dagger/dagger/engine/server.getDefaultGCPolicy(...)
         /app/engine/server/gc.go:176
github.com/dagger/dagger/engine/server.NewServer({0x257f8a8, 0x40001f8690}, 0x40003bedf0)
         /app/engine/server/server.go:415 +0x37b0
main.main.func2(0x40001c2160)
         /app/cmd/engine/main.go:400 +0x146c
github.com/urfave/cli.HandleAction({0x1c0f200?, 0x40001b8228?}, 0x40004a56c0?)
         /go/pkg/mod/github.com/urfave/cli@v1.22.16/app.go:524 +0x58
github.com/urfave/cli.(*App).Run(0x40004a56c0, {0x400004c0f0, 0x3, 0x3})
         /go/pkg/mod/github.com/urfave/cli@v1.22.16/app.go:286 +0x578
main.main()
         /app/cmd/engine/main.go:485 +0x1bc
jagged umbra
#

The same panic occurs when using engine.json:

{
    "gc": {
        "enabled": false
    }
}
magic moss
magic moss
jagged umbra
#

nice! fwiw, my intention is to disable garbage collection, not disable local cache.

magic moss
jagged umbra