#Is it no longer possible to install dagger `v0.12.4`?

1 messages · Page 1 of 1 (latest)

safe prairie
#

I'm getting a 403 for it on the install script, and brew can't find that version in the tap. I upgraded to v0.12.5 and suddenly one of my functions stopped working (unexpected nil source on a WithMountedFile) - I also noticed I'm hitting a 60s timeout on "calling import cache" reliably. I wanted to rule out the upgrade, but I'm struggling to rollback. I've got two functions that do things in their constructors; one function that still works and another one that is broken. I've got a root module Cicd with several methods that return child structs:

  • cicd.Build() *Build
  • cicd.Test() *Test
  • cicd.Package() *Package
  • cicd.Stacks() *Stacks

In their constructors, the Package and Stacks structs consume a field from the parent Cicd struct:

type Package struct {
  // +private
  File *dagger.File
}

func (m *Cicd) Package() *Package {
  file := m.Build().MyFile()
  return &Package{
    File *dagger.File
  }
}

func (m *Package) Services() *dagger.Container {
  return dag.Container().
    From("golang:latest").
    WithMountedFile("/usr/local/bin/myfile", m.File)
}

I'm seeing the spans for the m.Build().MyFile() call in both Stacks and Package commands, but i'm getting an NPE in the internal/dagger gen only for the Stacks commands:

func (r *Container) WithMountedFile(path string, source *File, opts ...ContainerWithMountedFileOpts) *Container {
    assertNotNil("source", source)

🤯 ... Literally as I was typing this out, I thought "I already uninstalled 0.12.5 with brew, install script couldn't find 0.12.4, but let me use the install script to install 0.12.5 and give it another whirl" and to my surprise, it worked.

I checked the engine logs, and it looks like after many minutes of gateway timeout on import cache, it finally succeeded. Difficult to determine if the remote cache issues were responsible... Nvm, i did a restart of the engine and the import cache is still timing out.

safe prairie
#

Is it no longer possible to install dagger v0.12.4?

#

facepalm this is 100% me. i was looking at the stack trace wrong and was off by two lines, i marked an argument // +optional without handling nil cases. Forgive me! 🙏

#

Still weird behavior with the cache import tho

muted verge
#

@safe prairie Can you please share more details around the cache import, a copy of a trace if you can, or a cloud URL if you're using that would be even better 🙂

safe prairie
#

Sure, here is a trace from last night representing the import cache timeout after 60s: https://dagger.cloud/Tallied-Technologies-Inc/traces/96fed394321831828b44c92744edf0a6 Repro steps for me are:

  1. delete existing dagger engine containers and volumes locally
  2. set dagger cloud token env var
  3. dagger call to start a fresh engine without running a specific function in my module
  4. dagger connect finishes after ~60s, no indication of failure in CLI
  5. inspect dagger engine logs, observe import cache context deadline exceeded
  6. iterate and wait some time, inspect dagger engine logs, observe 504 gateway timeout on import cache and export cache
safe prairie
#

Just tried it again, same deal unfortunately.

2024-08-19 17:12:49 time="2024-08-20T00:12:49Z" level=debug msg="importing cache"
2024-08-19 17:12:49 time="2024-08-20T00:12:49Z" level=debug msg="calling import cache"
2024-08-19 17:13:49 time="2024-08-20T00:13:49Z" level=debug msg="finished importing cache in 1m0.053208819s"
2024-08-19 17:13:49 time="2024-08-20T00:13:49Z" level=error msg="failed to import cache at startup" error="Get \"https://api.dagger.cloud/magicache/import\": context deadline exceeded"
#

There is also the unexpected error running a dagger v0.12.4 module with dagger v0.12.5 CLI

#

Seeing a variety of these, not sure if related:

2024-08-19 17:18:59 time="2024-08-20T00:18:59Z" level=warning msg="failed to release network namespace \"lc290pqwesnyk4xw4n8yzz1e2\" left over from previous run: plugin type=\"loopback\" failed (delete): unknown FS magic on \"/var/lib/dagger/net/cni/lc290pqwesnyk4xw4n8yzz1e2\": ef53"

I'm unable to sync new caches to dagger.cloud, unfortunately.

#

Our CI is still using v0.12.4, but locally I'm unable to rollback to it.

safe prairie
#

It would be great if I could delete caches and not just disable them. Would help in troubleshooting.

muted verge
#

Yeah for sure @low cape if you get a chance, do you know if there is a way to delete the cache for this org?

#

@safe prairie for goign back to 0.12.4 could you try just pulling the binary from github release?

We may have an issue here. But that should get you unblocked.

https://github.com/dagger/dagger/releases/tag/v0.12.4

GitHub

v0.12.4 - 2024-08-01
Changed

Deprecate old pipeline APIs by @jedevc in #8064
These operations have been no-ops since v0.11.0, and will be removed in v0.13.0.

Fixed

Fix errors when using Dockerf...

low cape
gleaming pendant
#

On it!

#

@muted verge done! I'll add a method to magiclean's module that does this for us, should be quite quick to include

muted verge
gleaming pendant
safe prairie
#

Thanks for the help folks. I'm not sure I understand where we're at on this: was a cache deleted? If so, which?

low cape
#

I can see some cache has been uploaded since yesterday though