#✨ v0.14.0 - 8th November 2024

1 messages · Page 1 of 1 (latest)

acoustic thorn
#

v0.14.0 Milestone: https://github.com/dagger/dagger/milestone/59

cc <@&785926252749651978> please ensure anything you want in v0.14.0 is part of the milestone. I'm prioritizing reviewing everything there and getting it all merged.

Immediate TODOs:

Follow ups:

  • daggerverse preview workflow never ran
  • fix enum error hit during sdk publishes
  • fix python publish error that had to be worked around manually
  • fix broken TS docs link that is included in autogenerated release notes by default
shy wraith
arctic sapphire
#

Yeah rebasing the PAT support right now -- feel free to reivew too once done 🙏

acoustic thorn
acoustic thorn
narrow river
next bolt
narrow river
#

We forgot metrics!

#

It's right there in the TUI. In all its glory...

#

😭 so beautiful

onyx zodiac
acoustic thorn
#

Couple last few PRs in the milestone to review and merge, will start release ASAP after

acoustic thorn
# narrow river We forgot metrics!

Ah yeah I still consider it to be "soft-launched" since it's hidden under high verbosity, TUI only (not cloud), the display is quite rough (though @manic willow helped a lot yesterday with human readable units), etc. etc.

It's being actively iterated on though so good candidate for the next release blog post

manic willow
manic willow
#

not yet 🙂

#

oh prolly just doesn't repro on orb then, huh

acoustic thorn
narrow river
acoustic thorn
dreamy meteor
#

Eek the enums

#

Happy with either option - to fix the failing tests, or to remove the removal

acoustic thorn
# dreamy meteor Eek the enums

Ya was just typing a message about that to give everyone else context, but if you're here 🙂, do you agree it makes sense to delay rm'ing them entirely until v0.15?

dreamy meteor
#

I tried to do the deprecation and removal in one, as an experiment, clearly that's a bit bleh

#

I really wanted to get rid of them asap, since they have the possibilty to claim things in the global namespace

#

And can result in huge clashes, if multiple modules you consume define the same values

acoustic thorn
#

Yeah it's tricky, but the main thing for me is that they have only been deprecated for like a week and it went under the radar because it was automagical, so we didn't have time to prep any extra notes on migrating

#

I think there's a good chance it won't be too long until v0.15, we already have a few things lined up for it

dreamy meteor
#

Yeah, I'm happy to push it out - I thought I fixed the failing tests though, that's surprising

acoustic thorn
dreamy meteor
#

Ahhhh okay phew

#

Yeah let's push it out 🙏 should be pretty easy, just needs to bump the schema dagql and the future_test.go test

#

Thanks 🙏 good timing, I literally just opened this up curiously while waiting for lunch 😂

acoustic thorn
dreamy meteor
#

Maybe worth not doing deprecations and removals in one for the future? (Back to pto 🫡)

turbid quail
acoustic thorn
#

Engine+CLI published successfully but hitting errors on all the SDKs: https://github.com/dagger/dagger/actions/runs/11749969983

Mostly:

error: parse selections: parse field "create": init arg "latest" value as dagql.DynamicOptional (GhLatest) using dagql.DynamicOptional: cannot create enum name from bool

Seeing where they were in the workflow when they failed. Should all be dealable with by hand either way

GitHub

An engine to run your pipelines in containers. Contribute to dagger/dagger development by creating an account on GitHub.

#

Though interestingly Python is slightly different:

Error uploading to repository: https://upload.pypi.org/legacy/ - Client error '400 license-expression introduced in metadata version 2.4, not 2.3. See https://packaging.python.org/specifications/core-metadata for more information.' for url 'https://upload.pypi.org/legacy/'

(cc @magic arch in case you are still online)

magic arch
#

I know what the error is saying, but not sure why it's happening at this moment in the time flux.

acoustic thorn
magic arch
#

Yeah, it's complaining about the format of "license" in the pyproject.toml file.

acoustic thorn
#

This is unfortunately a bit more annoying to deal with since we can't just manual dispatch a new python publish with a fix in place... might need to resort to running it manually locally

acoustic thorn
magic arch
acoustic thorn
magic arch
#

Yeah, but don't have access to the vault anymore.

acoustic thorn
magic arch
acoustic thorn
dreamy meteor
acoustic thorn
dreamy meteor
#

Ah dynamicoptional doesn't have the method that gets called in that pr (I'll look into this next week)

acoustic thorn
manic willow
#

anybody know what's up with

Error: failed to serve module: Post "http://dagger/query": command [docker exec -i dagger-engine.dev buildctl dial-stdio] has exited with exit status 137, make s
ure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=

? I just updated the cli, rebased, and then this started failing in my ./hack/dev builds. possible it's something on my end though. I already reset my docker engine. The build looks like it's hanging on loadPackage, codegenning php?

● Container.withExec(args: ["codegen", "--output", "/src", "--module-context-path", "/src/sdk/php/runtime", "--module-name", "php-sdk", "--introspect
            ┃ go: downloading github.com/google/go-cmp v0.6.0
            ┃ go: downloading github.com/andreyvit/diff v0.0.0-20170406064948-c7f18ee00883
            ┃ go: downloading gopkg.in/yaml.v3 v3.0.1
            ┃ go: downloading github.com/davecgh/go-spew v1.1.1
            ┃ go: downloading github.com/pmezard/go-difflib v1.0.0
            ┃ go: downloading github.com/sergi/go-diff v1.3.2-0.20230802210424-5b0b94c5c0d3
            ┃ needs another pass...
            ┃ starting GOROOT= GOPATH=/go GO111MODULE=off GOPROXY= PWD=/src/sdk/php/runtime go list -e -f {{context.ReleaseTags}} -- unsafe
            ┃ starting GOROOT= GOPATH=/go GO111MODULE= GOPROXY= PWD=/src/sdk/php/runtime go list -f "{{context.GOARCH}} {{context.Compiler}}" -- unsafe
            ┃ 1.169823ms for GOROOT= GOPATH=/go GO111MODULE=off GOPROXY= PWD=/src/sdk/php/runtime go list -e -f {{context.ReleaseTags}} -- unsafe
            ┃ starting GOROOT= GOPATH=/go GO111MODULE= GOPROXY= PWD=/src/sdk/php/runtime go list -e -json=Name,ImportPath,Error,Dir,GoFiles,IgnoredGoFiles,Ignore
            ┃ dOtherFiles,CFiles,CgoFiles,CXXFiles,MFiles,HFiles,FFiles,SFiles,SwigFiles,SwigCXXFiles,SysoFiles,CompiledGoFiles,DepOnly,Imports,ImportMap,Export,
            ┃ Module -compiled=true -test=false -export=true -deps=true -find=false -pgo=off -- .
            ┃ 1.628778ms for GOROOT= GOPATH=/go GO111MODULE= GOPROXY= PWD=/src/sdk/php/runtime go list -f "{{context.GOARCH}} {{context.Compiler}}" -- unsafe
            ┃ 621.894484ms for GOROOT= GOPATH=/go GO111MODULE= GOPROXY= PWD=/src/sdk/php/runtime go list -e -json=Name,ImportPath,Error,Dir,GoFiles,IgnoredGoFile
            ┃ s,IgnoredOtherFiles,CFiles,CgoFiles,CXXFiles,MFiles,HFiles,FFiles,SFiles,SwigFiles,SwigCXXFiles,SysoFiles,CompiledGoFiles,DepOnly,Imports,ImportMap
            ┃ ,Export,Module -compiled=true -test=false -export=true -deps=true -find=false -pgo=off -- .
              ● loadPackage 4m56.5s
              ✔ creating dagger metadata 0.0s
              ● exec codegen --output /src --module-context-path /src/sdk/php/runtime --module-name php-sdk --introspection-json-path /schema.json 
acoustic thorn
manic willow
#

ah, it's my engine

#

nm

magic arch
#

Expected to see the same error.

#

@magic arch, want me to try publishing locally from main to prod and send a PR later?

acoustic thorn
acoustic thorn
#

Automating this step didn't quite make it this release, so still need to manual ping @onyx zodiac @serene tiger @arctic sapphire et. al. for updating cloud+daggerverse

magic arch
#

There's a github release thing in sdk_python.go that I'm not familiar with, is that needed?

acoustic thorn
#

I will create the release by hand

#

Just let me know once it's on pypi and I'll do that

magic arch
#

Just got a flash of 500 on dagger cloud

arctic sapphire
acoustic thorn
magic arch
acoustic thorn
#

Okay mostly there, listed remaining immediate term TODOs in the top message of this thread

#

Also listed fixes needed for various issues hit this time around separately

turbid quail
magic arch
# acoustic thorn Hate it when the external world state mutates <:oldmanyellsatoldman:10762724098...

This PEP is provisional, so I didn't miss the deadline: https://peps.python.org/pep-0639/#deprecate-license-field.
I suppose hatch may be adding License-Expression on top of our License, which would explain why pypi would throw that error.

#

In any case, I'm removing hatch as a tool in favor of uv. Only the build backend remains, but uv is working on that so its days are numbered too. 😄

#

I was right. Hatch is producing this metadata:

License-Expression: Apache-2.0
License-File: LICENSE

While uv is producing just:

License-File: LICENSE
acoustic thorn
magic arch
dreamy meteor
#

however - i think there's some ambiguity about how we should handle an arg explicitly set to null (so going to continue that discussion there)

acoustic thorn
vocal tangle
acoustic thorn
vocal tangle
#

Working on the function that will bump Daggerverse now.

turbid quail
magic arch
manic willow