chore(deps): bump the sdk-python group across 1 directory with 21 updates #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
This significantly improves initial directory upload speed, on my computer this goes from 4.8s to a much better 2.5s. *Ideally*, we could also avoid uploading the git directory. This is a bit of a pain *right now* though, so we don't do it! Signed-off-by: Justin Chadwell <[email protected]>
* Upgrade `ex_doc` to latest version. * Update documentation on the `Dagger` module. * Remove `getting_started.livemd`, it's quite out-of-date. Signed-off-by: Thanabodee Charoenpiriyakij <[email protected]>
This is a very bad default to recommend - essentially this "de-secrets" a value, and this could then be leaked accidentally: - Potentially into OTEL spans - Potentially into cache keys - Potentially into engine logs We should recommend using `WithSecretVariable` instead, which is much better - then rely on the shell to do the interpolation, which avoids all of these problems. The secret scrubber will then guarantee that we don't secrets leaked into logs. Signed-off-by: Justin Chadwell <[email protected]>
* fix gitlab before_script Fixes gitlab beore script by installing the Dagger CLI in a location that's availabe in the $PATH Signed-off-by: Marcos Nils <[email protected]>
* engine: remove ftp_proxy hack This removes the ftp_proxy hack we've had for a while for passing uncached metadata to containers (previously a lot, but recently trimmed down to just ServerID). Instead, we take advantage of the new custom executor added recently and use that to set the _DAGGER_SERVER_ID env var in containers. The plumbing passes the ServerID via job values, which get read by the solver's ResolveOp callback and used to tell the Executor for ExecOps which ServerID to set in the container. There's quite a bit more cleanup coming to everything involved here, but wanted to get this first step out since that hack, besides being annoying, was kind of dubious in nature and was a suspect in some strange behavior reported sometimes. Signed-off-by: Erik Sipsma <[email protected]> * engine: remove apparently unused opTrackingGateway I don't see that this is actually used or ends up modifying anything. Suspect it's vestigial from pre-OTEL days so removing it. Signed-off-by: Erik Sipsma <[email protected]> * engine: pass worker around instead of custom executor This fixes the problem in the previous commit where Dockerfiles with a syntax pragma hit the executor directly before a ServerID could be set. This wasn't the shortest fix, but it seems to be the best long term one. The end result is that the Worker provided to LLBSolvers is always scoped to the server, so we don't even need to be careful about ensuring the right executor is being used everywhere. It just will be now because it's the only executor available to buildkit internals we use. This required a few adjustments from the previous code: 1. The custom executor has been expanded to also be a custom worker. Fortunately, it almost entirely reuses functionality from upstream's base.Worker, so this doesn't another big chunk of code to maintain. 2. llbSolver is now created in each buildkit.Client and setup with a worker.Controller with the Worker scoped to the current ServerID. 3. Rather than passing the ServerID through job keys, we just pass the whole Worker and use that to resolve ops. 4. Some more general cleanup of worker initialization made possible by these changes. Signed-off-by: Erik Sipsma <[email protected]> * backfill integ test coverage for dockerfile w/ syntax pragma Signed-off-by: Erik Sipsma <[email protected]> * add comment pointing to original runc executor implementation Signed-off-by: Erik Sipsma <[email protected]> --------- Signed-off-by: Erik Sipsma <[email protected]>
* sdk(rust): use `load*FromID` in tests Use these newer methods instead of using `container` and `file` to load IDs, which is deprecated and *going to be removed soon*. Signed-off-by: Justin Chadwell <[email protected]> * sdk(go): use load*FromID in tests Signed-off-by: Justin Chadwell <[email protected]> * sdk(typescript): use load*FromID in tests Signed-off-by: Justin Chadwell <[email protected]> * chore: use load*FromID in tests Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Justin Chadwell <[email protected]>
Signed-off-by: Alex Suraci <[email protected]>
* ci: exclude .git dir in ci build Previously, we were using this to generate a work-tree hash, so that new builds would have a different version tag, which helped to solve some weird caching issues with nested execs. However! A problem with this was that we needed to upload *the entire* git directory every time we built - which is an expensive operation, my .git directory for dagger/dagger is 147MB. Instead of relying on git for this, we can use the ID of the input directory! Because of our use of blob sources, a different ID represents a different directory. Additionally, we prefix these new builds with a special "dev-" string to specifically indicate that these are dev builds, with no specific version passed in - these aren't commit hashes, and cannot be treated as such. Signed-off-by: Justin Chadwell <[email protected]> * ci: remove dependency on go sdk The only thing this was being used for here was the connect job - we can just use `--help` to get this info to sanity check it. Signed-off-by: Justin Chadwell <[email protected]> * ci: run linting over ci itself Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Justin Chadwell <[email protected]>
Signed-off-by: Justin Chadwell <[email protected]>
Signed-off-by: kpenfound <[email protected]>
With this typo, the yaml file was invalid and so the config failed to be applied. I *finally* found where you can check the validity of a dependabot config - see https://github.com/dagger/dagger/network/updates. Signed-off-by: Justin Chadwell <[email protected]>
* chore: run dagger develop on typescript runtime Signed-off-by: Justin Chadwell <[email protected]> * fix: top-level dagger.gen.go should have correct imports Previously it wasn't, we were missing `telemetry` and `querybuilder`. And `go mod tidy` wouldn't *always* seem to pick it up, which is a bit of a pain. Signed-off-by: Justin Chadwell <[email protected]> * fix: avoid overwriting go mod/sum files on module generation This is a bit of a mess - but essentially, what *was* happening was that we had some very strange issues with go.mod generation. When generating code, we had a couple of issues: - If we were generating on top of an existing go.{mod,sum}, we were essentially replacing its contents, and then relying on `go mod tidy` to give reasonable results - however, this meant that explicitly installed dependencies were getting lost, and that we were losing the pins in the sum file. - Additionally, if we were generating a new `dagger` subfolder in an existing monorepo, we were overriding the previous go.{mod,sum} with dagger's go.{mod,sum}, and then relying on `go mod tidy` to find all the user dependencies. The main issue with the above is that we were replacing contents of these important dependency files in weird ways that make go modules much more difficult to consume, especially in monorepos. To fix these issues, we heavily rework the logic - we explicitly find the correct go.mod file we want to work on, and then apply *the same* processing everywhere. This processing involves checking go versions, adding dependencies that aren't present, merging go.sum values, etc. However - in doing this, something becomes quite apparent - we were relying on some weird undefined behavior in the Go SDK. Generally the structure of the paths passed in was that `ModuleContextPath` was a parent to `OutputDir`, and we wouldn't modify anything outside `OutputDir`. But consider, if the output directory is `./dagger` (the default), then we may need to modify the top-level `./go.mod` (that isn't in `OutputDir`). We technically *were* doing this, but by using `go mod tidy` to get it to do this magically - but as mentioned above, we need to avoid this automatic behavior, and do some better merging ourselves. To resolve this, `OutputDir` becomes the top-level, while `ModulePath` becomes a relative sub-path in `OutputDir` that the module can be found at (in the above, that's `./dagger`). This is why this patch also needs to touch the Typescript runtime files, since we change the format of the arguments to use this new format (also the Typescript generation was confusing here, so picked up a couple of refactors as well along the way). Signed-off-by: Justin Chadwell <[email protected]> * tests: fix incorrect go.{mod,work} tests - The `go.mod` test was incorrect because prior to the commit before this one, we were actually generating a `go.mod` in the child. This was *hard* to notice, because essentially, there was a weird disparity between having a `go.mod` and having a `go.mod` *and* a `main.go` in the top-level (since `loadPackage` fails on the former, but succeeds on the latter). The test is modified to ensure we can catch this in the future, and the prior commit makes sure that this weird disparity is removed. - The `go.work` tests were incorrect because we shouldn't have been putting `go.mod`s in the children (the same `loadPackage` issue as above). Each of these test cases should only have *one* module, so we alter the tests to check for this. Signed-off-by: Justin Chadwell <[email protected]> * review comments Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Justin Chadwell <[email protected]>
* chore: fix some doc comments for daqgl to match Signed-off-by: Justin Chadwell <[email protected]> * chore: remove some unused parameters And also enable a linter to catch these in the future. `unparam` seems to be optimized more heavily to avoid false positives, and is significantly better at not bringing up weird interface cases that revive seems to love. Signed-off-by: Justin Chadwell <[email protected]> * fixups Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Justin Chadwell <[email protected]>
Signed-off-by: Justin Chadwell <[email protected]>
Signed-off-by: Helder Correia <[email protected]>
Signed-off-by: Helder Correia <[email protected]>
* cli: visual cue for required flags Append [required] to flags that are marked as required. As proposed by Helder, this follows the behavior of Typer: https://typer.tiangolo.com/tutorial/options/required/ Signed-off-by: grouville <[email protected]> * Rename template function to be more descriptive Signed-off-by: Helder Correia <[email protected]> * Simplify flagset merge Signed-off-by: Helder Correia <[email protected]> * Replace clone with mutation This preserves the `flag.Annotations` map, which is needed for validation. Signed-off-by: Helder Correia <[email protected]> * Replace string key with const The rest wasn't wrong but follows how `Command.ValidateRequiredFlags` handles these flags. Signed-off-by: Helder Correia <[email protected]> * Add change log Signed-off-by: Helder Correia <[email protected]> --------- Signed-off-by: grouville <[email protected]> Signed-off-by: Helder Correia <[email protected]> Co-authored-by: grouville <[email protected]> Co-authored-by: Helder Correia <[email protected]>
* ci: Add Wolfi base image option Signed-off-by: Adrian Mouat <[email protected]> * Simplify apk command. Signed-off-by: Adrian Mouat <[email protected]> * nit: use const for Wolfi image reference. Signed-off-by: Adrian Mouat <[email protected]> * Plumb through setting base image. Use `engine with-base image="wolfi"` etc Also fix typo in error return Signed-off-by: Adrian Mouat <[email protected]> * ci: rework gpusupport into a common WithBase function And also update mage calls to get the right base image, so we can definitely publish. Signed-off-by: Justin Chadwell <[email protected]> * ci: simplify gpu support checks into switches Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Adrian Mouat <[email protected]> Signed-off-by: Justin Chadwell <[email protected]> Co-authored-by: Justin Chadwell <[email protected]>
Goreleaser needs this :( Signed-off-by: Justin Chadwell <[email protected]>
* docs: Adds information on Dagger Cloud cache Signed-off-by: Vikram Vaswani <[email protected]> * Updated note Signed-off-by: Vikram Vaswani <[email protected]> * Added link Signed-off-by: Vikram Vaswani <[email protected]> --------- Signed-off-by: Vikram Vaswani <[email protected]>
* chore: update internal tooling to v0.11.2 Signed-off-by: Justin Chadwell <[email protected]> * docs: update docs to refer to newest v0.11.2 release Signed-off-by: Justin Chadwell <[email protected]> * ci: update to install dagger cli v0.11.2 Signed-off-by: Justin Chadwell <[email protected]> * chore: update RELEASING guide Signed-off-by: Justin Chadwell <[email protected]> * chore: Add Helm releasing instructions to RELEASING.md Also prepare the Helm chart for release right after this gets merged. Also run `go mod tidy` after rebasing. Signed-off-by: Gerhard Lazu <[email protected]> --------- Signed-off-by: Justin Chadwell <[email protected]> Signed-off-by: Gerhard Lazu <[email protected]> Co-authored-by: Gerhard Lazu <[email protected]>
* cli: conventionalize on <command> in cmd.Use Unifies the DX around usage across all commands. The convention follows the standards (gh / git CLIs) as well as the defaults from cobra. The grammar is as follow: - []: optional - <>: user input, when argument is not optional, to differenciate with static args - ...: one or more This commit applies it everywhere and unifies according to this grammar. Signed-off-by: grouville <[email protected]> * Fix incorrections Signed-off-by: Helder Correia <[email protected]> * Remove second use line Sometimes a subcommand is required (`dagger call`), and other times it's optional (`dagger config`). Best make it explicit in `Use`. Signed-off-by: Helder Correia <[email protected]> * Fix required mark when flag has no description Signed-off-by: Helder Correia <[email protected]> --------- Signed-off-by: grouville <[email protected]> Signed-off-by: Helder Correia <[email protected]> Co-authored-by: grouville <[email protected]> Co-authored-by: Helder Correia <[email protected]>
Upgrading the Erlang/OTP to fix Erlang erlang/otp#8238 bug. Signed-off-by: Thanabodee Charoenpiriyakij <[email protected]>
…ns" in `dagger call --help` (#7286) * cli: use "functions" and "arguments" instead of "commands" and "options" in `dagger call` Signed-off-by: Helder Correia <[email protected]> * Add change log Signed-off-by: Helder Correia <[email protected]> --------- Signed-off-by: Helder Correia <[email protected]>
Every section was indented except for the examples. Signed-off-by: Helder Correia <[email protected]>
Fixed generated default values for typescript SDK Signed-off-by: Bochi <[email protected]>
* chore: remove unneccessary InputType Signed-off-by: Justin Chadwell <[email protected]> * chore: format mod typedef query Signed-off-by: Justin Chadwell <[email protected]> * chore: avoid ModuleObjectType typed nil Signed-off-by: Justin Chadwell <[email protected]> * feat: add scalar typedefs to propagate scalars Signed-off-by: Justin Chadwell <[email protected]> * feat: interpret current arg to get current platform Signed-off-by: Justin Chadwell <[email protected]> * Add Python fix Signed-off-by: Helder Correia <[email protected]> * Replace ignored stdout with sync Signed-off-by: Helder Correia <[email protected]> * fix test to-platform Signed-off-by: Justin Chadwell <[email protected]> * Test return values and enum types Signed-off-by: Helder Correia <[email protected]> * Fix linter on changed function Signed-off-by: Helder Correia <[email protected]> * chore: regen rust Signed-off-by: Justin Chadwell <[email protected]> * feat: support scalar in TypeScript Signed-off-by: Tom Chauveau <[email protected]> * feat: add enum tests Signed-off-by: Tom Chauveau <[email protected]> * Remove old tests Signed-off-by: Helder Correia <[email protected]> * Add change log Signed-off-by: Helder Correia <[email protected]> --------- Signed-off-by: Justin Chadwell <[email protected]> Signed-off-by: Helder Correia <[email protected]> Signed-off-by: Tom Chauveau <[email protected]> Co-authored-by: Helder Correia <[email protected]> Co-authored-by: Tom Chauveau <[email protected]>
* Use Dagger v0.11.2 via the new CI setup for all workflows except dev-engine This one requires Docker with specific fixes that we don't yet have in the new CI setup. Signed-off-by: Gerhard Lazu <[email protected]> * Setup CI for new, legacy and vertical scaling The setup we want for production is: - For all <LANG> SDK jobs, run them on the new CI only - For testdev, run them on the docker-fix legacy CI - For test/dagger-runner, run them on both legacy CI and new CI - For all the rest, run them on the new CI and github runners for the really simple jobs Signed-off-by: Matias Pan <[email protected]> * Rename concurrency group Signed-off-by: Matias Pan <[email protected]> * Install curl on production vertical scaling runner Signed-off-by: Matias Pan <[email protected]> * Add customizable runner for separate perf tests Signed-off-by: Matias Pan <[email protected]> * Rename to _async_hack_make Signed-off-by: Matias Pan <[email protected]> * Upgrade missing workflow to v0.11.1 Signed-off-by: Matias Pan <[email protected]> * Target nvme Signed-off-by: Matias Pan <[email protected]> * CI: Default to 4CPUs & NVMe disks Otherwise the workflows are too slow on the new CI runners and are blocking the migration off the legacy CI runners. Signed-off-by: Gerhard Lazu <[email protected]> * Bump to v0.11.2 & capture extra details in comments Signed-off-by: Gerhard Lazu <[email protected]> * Debug dagger-engine.dev in large GitHub Runner Signed-off-by: Gerhard Lazu <[email protected]> * Continuer running engine:testdev in dagger-runner-docker-fix runner Large GitHub Runners are failing consistently, not worth debugging at this point since we know this works on a vanilla Ubuntu 24.04 instance with Docker - must be an issue related to GitHub Large Runners. FTR: dagger/dagger#7223 (comment) Signed-off-by: Gerhard Lazu <[email protected]> --------- Signed-off-by: Gerhard Lazu <[email protected]> Signed-off-by: Matias Pan <[email protected]> Co-authored-by: Gerhard Lazu <[email protected]> Co-authored-by: Matias Pan <[email protected]>
Signed-off-by: Erik Sipsma <[email protected]>
Changelogs summary: - symfony/deprecation-contracts updated from v3.4.0 to v3.5.0 minor See changes: symfony/deprecation-contracts@v3.4.0...v3.5.0 Release notes: https://github.com/symfony/deprecation-contracts/releases/tag/v3.5.0 - symfony/polyfill-mbstring updated from v1.28.0 to v1.29.0 minor See changes: symfony/polyfill-mbstring@v1.28.0...v1.29.0 Release notes: https://github.com/symfony/polyfill-mbstring/releases/tag/v1.29.0 - symfony/polyfill-intl-normalizer updated from v1.28.0 to v1.29.0 minor See changes: symfony/polyfill-intl-normalizer@v1.28.0...v1.29.0 Release notes: https://github.com/symfony/polyfill-intl-normalizer/releases/tag/v1.29.0 - symfony/polyfill-intl-grapheme updated from v1.28.0 to v1.29.0 minor See changes: symfony/polyfill-intl-grapheme@v1.28.0...v1.29.0 Release notes: https://github.com/symfony/polyfill-intl-grapheme/releases/tag/v1.29.0 - symfony/polyfill-ctype updated from v1.28.0 to v1.29.0 minor See changes: symfony/polyfill-ctype@v1.28.0...v1.29.0 Release notes: https://github.com/symfony/polyfill-ctype/releases/tag/v1.29.0 - symfony/string updated from v7.0.0 to v7.0.7 patch See changes: symfony/string@v7.0.0...v7.0.7 Release notes: https://github.com/symfony/string/releases/tag/v7.0.7 - symfony/service-contracts updated from v3.4.0 to v3.5.0 minor See changes: symfony/service-contracts@v3.4.0...v3.5.0 Release notes: https://github.com/symfony/service-contracts/releases/tag/v3.5.0 - symfony/console updated from v6.4.1 to v7.0.7 major See changes: symfony/console@v6.4.1...v7.0.7 Release notes: https://github.com/symfony/console/releases/tag/v7.0.7 - symfony/process updated from v6.4.0 to v7.0.7 major See changes: symfony/process@v6.4.0...v7.0.7 Release notes: https://github.com/symfony/process/releases/tag/v7.0.7 Signed-off-by: Romain Gautier <[email protected]>
This has been reported to happen intermittently by a few users. The error originates from gqlgen and suggests that something in the http request is unhandled; it basically tries to find a matching pattern for gql requests based on http method and some headers. It's unclear how this could happen only occasionally and I've never seen this myself yet, so I think our best bet is to log the parts of the request checked by gqlgen and wait for it to get hit again. Signed-off-by: Erik Sipsma <[email protected]>
Bumps [rustls](https://github.com/rustls/rustls) from 0.21.10 to 0.21.12. - [Release notes](https://github.com/rustls/rustls/releases) - [Changelog](https://github.com/rustls/rustls/blob/main/CHANGELOG.md) - [Commits](rustls/rustls@v/0.21.10...v/0.21.12) --- updated-dependencies: - dependency-name: rustls dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* close service logs too Signed-off-by: Alex Suraci <[email protected]> * telemetry: fix tunnel log draining and other missing closes I was still having to wait 5 minutes for OTEL logs to drain on some test runs that involved service tunneling. I believe there was a race condition where the tunnel code could end up writing logs after they were closed, which seems to create a leak and cause us to have to wait 5 minutes before a timeout is hit. I also saw a few other place otel logs were created and not closed, so added a close there too. Signed-off-by: Erik Sipsma <[email protected]> * unify on slog, focus draining on stdio use case * SpanLogger no longer writes to stdio streams, since it's unclear at each logging site who has responsibility to Close(); this way no one does. * switch last few holdouts to slog - for better or for worse, we should be consistent and iterate. We've started using slog for client-side logs, so we might as well adopt them server-side too. Signed-off-by: Alex Suraci <[email protected]> * propagate debug/no-color mode to server uses otel baggage, which I thankfully already went through the trouble of propagating, and hadn't used yet. neat! Signed-off-by: Alex Suraci <[email protected]> --------- Signed-off-by: Alex Suraci <[email protected]> Signed-off-by: Erik Sipsma <[email protected]> Co-authored-by: Erik Sipsma <[email protected]>
When an exec fails due to context canceled, we were dropping the cancelation error and just returning the exec error. I believe this got fat-fingered while updating the code from upstream to use fmt.Errorf instead of github.com/pkg/errors. It's not clear if this is really meaningful, but noticed it changed while attempting to debug occurances of "exit code 137" in our CI, which plausibly could be related to all of this. It's possible there's calling code that tries to handle cancelation with errors.Is, which this would have broken. This is purely hypothetical at this point though. Signed-off-by: Erik Sipsma <[email protected]>
There was a race condition where contexts get canceled after a job is sent to the netns worker but before the result got read. This caused runInNetNS to exit (due to canceled context) but the result chan to never be read from. It was crucially an unbuffered chan, which resulted in the worker never being able to exit and the whole container cleanup to block indefinitely. The fix here is just to make that chan buffered with a size of 1 so that the worker doesn't ever get blocked trying to write to it. There's a few other related changes of making some other chans buffered and explicitly closing them with a defer (to handle panic cases) which aren't needed to fix this issue but seemed worth tidying up now. Signed-off-by: Erik Sipsma <[email protected]>
* fix: ensure nested frontend builds get secret translation When doing a nested frontend build - i.e. when dockerfile.v0 calls gateway.v0 (triggered by a syntax directive), we need to ensure that the second frontend gets the same secret translation as each prior layer. To do this, we heavily refactor the filtering gateway and essentially have it pass itself into the frontend Solve - this propagates the filtering all the way down, so secrets can be correctly accessed. Signed-off-by: Justin Chadwell <[email protected]> * tests: add test for remote frontend Signed-off-by: Justin Chadwell <[email protected]> * chore: add changelog Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Justin Chadwell <[email protected]>
The tsx issue has been fixed so this isn't needed anymore. Worst case if something else pops up this SDK would still be usable by it's git commit ref, so may as well remove it now. Signed-off-by: Erik Sipsma <[email protected]>
* ci: upgrade golangci lint to v1.59 Signed-off-by: Justin Chadwell <[email protected]> * chore: fix linting issues Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Justin Chadwell <[email protected]>
* fix(ts-sdk) rollback to npm to ignore packageManager field #7096 introduced a regression by using `yarn install --production`. If the field `packagaManager` is set, it might lead to failure because yarn post v1.22.11 doesn't support the `--production` flag anymore, it has been removed in favor of `yarn workspaces focus --production`. However, depending on the yarn major version (v2, v3, v4), the options are different but also the results and the way they handle subdependencies. It seems `npm` is the only package manager that actually force install all the sub dependencies, which ensure the TS SDK runtime properly works. Signed-off-by: Tom Chauveau <[email protected]> * chore: add release note Signed-off-by: Tom Chauveau <[email protected]> * feat: move corepack init inside SDK installation Signed-off-by: Tom Chauveau <[email protected]> * fix: remove `--production` on user's install deps Signed-off-by: Tom Chauveau <[email protected]> --------- Signed-off-by: Tom Chauveau <[email protected]> Co-authored-by: Tom Chauveau <[email protected]>
* ci: enable best-effort cache reuse for nested engines We were previously always putting a random id in the cache volume used for engines created in various CI functions, which meant none of them ever had any local cache. The main reason was that two engines can't use the same local cache at the same time. We can't lift that limitation, but by using the engine version and private cache mounts we can get *best effort* re-use of these cache volumes, which is a simple enough performance improvement for some cases that we may as well take it. Signed-off-by: Erik Sipsma <[email protected]> * ci: make engine service version optional Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Erik Sipsma <[email protected]> Signed-off-by: Justin Chadwell <[email protected]> Co-authored-by: Justin Chadwell <[email protected]>
* fix(sdk/elixir): add :inets to :extra_applications `:inets` requires to start before using the SDK because of `:httpc` module. Signed-off-by: Thanabodee Charoenpiriyakij <[email protected]> * Add changie log Signed-off-by: Thanabodee Charoenpiriyakij <[email protected]> --------- Signed-off-by: Thanabodee Charoenpiriyakij <[email protected]>
* fix: don't hide quick top-level progress rows Signed-off-by: Justin Chadwell <[email protected]> * fix: always simplify internal operations on render In particular, this ensures that `blob` operations are always simplified to their source, which hugely helps to improve readability. Signed-off-by: Justin Chadwell <[email protected]> * fix: add empty line after progress before result Signed-off-by: Justin Chadwell <[email protected]> * fix: omit return type on DONE Signed-off-by: Justin Chadwell <[email protected]> * chore: extract prefix generation Signed-off-by: Justin Chadwell <[email protected]> * chore: refactor logs views into a panel Signed-off-by: Justin Chadwell <[email protected]> * feat: rework cloud progress printing For pretty progress, we add a new little message panel at the bottom containing a "Full trace at ..." message. For plain progress, in addition to the above, we also add a little fake virtual log to the "connecting to engine" span, so that it's available from the very start of the trace. Signed-off-by: Justin Chadwell <[email protected]> * tests: fixup some failing tests Signed-off-by: Justin Chadwell <[email protected]> * fix: move msgs panel to top Signed-off-by: Justin Chadwell <[email protected]> * fix: failing version test Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Justin Chadwell <[email protected]>
we're changing the default minConnectTimeout and backoff settings since in some cases, the `connect` happens before the engine is ready to accept connections, causing the client to wait for the default minConnectTimeout (20s) before retrying. This causes very long connection times when the engine is not ready to accept connections. fixes #7599 Signed-off-by: Marcos Lilljedahl <[email protected]>
Signed-off-by: Justin Chadwell <[email protected]>
* sdk: Bump engine dependency to v0.11.7 Signed-off-by: Dagger CI <[email protected]> * chore: add sdk release notes for v0.11.7 Signed-off-by: Justin Chadwell <[email protected]> * chore: bump helm dagger version to v0.11.7 Signed-off-by: Justin Chadwell <[email protected]> * docs: bump dagger version to v0.11.7 Signed-off-by: Justin Chadwell <[email protected]> --------- Signed-off-by: Dagger CI <[email protected]> Signed-off-by: Justin Chadwell <[email protected]> Co-authored-by: Dagger CI <[email protected]> Co-authored-by: Justin Chadwell <[email protected]>
Signed-off-by: Justin Chadwell <[email protected]>
Signed-off-by: Andrea Luzzardi <[email protected]>
There's an enormous amount of buildkit+containerd entities like snapshotters, various cache dbs, the solver, worker+executor, etc. which are all important to understand, but previously they were all setup all over the place which was extremely confusing to follow. This consolidates them all to be setup and stored in one place. There's quite a bit there, but at least you don't have to search far and wide to know what exists and how it's configured. Signed-off-by: Erik Sipsma <[email protected]>
This commit focuses on making sessions + associated state management
simpler:
* More comprehensible+centralized state management
* Rather than spread all over the place and tied together in random
places, all of the state associated with a given session is in a
daggerSession object and all of the state associated with a given client
in a session is a daggerClient object
* The code is also a lot more structured and "boring" in terms of
locking/mutating state/etc. Not a rube goldberg machine anymore
* The whole "pre-register a nested client's state before it calls", which
was a fountain of confusion and bugs, is gone.
* No more insane gRPC tunneling, the engine API is just an HTTP server now
* graphQL http requests are just that, don't have to tunnel them through
gRPC streams
* session attachables are still gRPC based, but over a hijacked http conn
(as opposed to a gRPC stream embedded in another gRPC stream)
* This allowed us to move off the Session method from buildkit's upstream
controller interface
* That in turn let us delete huge chunks of complicated code around
handing conns (i.e. engine/server/conn.go) and no longer need to be
paranoid about gRPC max message limits in as many places
There are more details in the PR description (7315).
Signed-off-by: Erik Sipsma <[email protected]>
The --experimental-privileged-nesting flag was broken when used with terminal due to a panic around registering clients. This was fixed by commits before this one which completely removed the need to register clients, but backfilling the coverage now. Signed-off-by: Erik Sipsma <[email protected]>
Otherwise we only use the otel spans from the initial client connect, not any per-request config. Signed-off-by: Erik Sipsma <[email protected]>
Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.3 to 3.1.4. - [Release notes](https://github.com/pallets/jinja/releases) - [Changelog](https://github.com/pallets/jinja/blob/main/CHANGES.rst) - [Commits](pallets/jinja@3.1.3...3.1.4) --- updated-dependencies: - dependency-name: jinja2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ates Bumps the sdk-python group with 21 updates in the /sdk/python directory: | Package | From | To | | --- | --- | --- | | [anyio](https://github.com/agronholm/anyio) | `4.3.0` | `4.4.0` | | [typing-extensions](https://github.com/python/typing_extensions) | `4.11.0` | `4.12.2` | | [opentelemetry-sdk](https://github.com/open-telemetry/opentelemetry-python) | `1.24.0` | `1.25.0` | | [opentelemetry-exporter-otlp-proto-grpc](https://github.com/open-telemetry/opentelemetry-python) | `1.24.0` | `1.25.0` | | [babel](https://github.com/python-babel/babel) | `2.14.0` | `2.15.0` | | [black](https://github.com/psf/black) | `23.12.1` | `24.4.2` | | [certifi](https://github.com/certifi/python-certifi) | `2024.2.2` | `2024.6.2` | | [docutils](https://docutils.sourceforge.io) | `0.20.1` | `0.21.2` | | [grpcio](https://github.com/grpc/grpc) | `1.63.0` | `1.64.1` | | [importlib-metadata](https://github.com/python/importlib_metadata) | `7.0.0` | `7.1.0` | | [opentelemetry-api](https://github.com/open-telemetry/opentelemetry-python) | `1.24.0` | `1.25.0` | | [opentelemetry-exporter-otlp-proto-common](https://github.com/open-telemetry/opentelemetry-python) | `1.24.0` | `1.25.0` | | [opentelemetry-proto](https://github.com/open-telemetry/opentelemetry-python) | `1.24.0` | `1.25.0` | | [packaging](https://github.com/pypa/packaging) | `24.0` | `24.1` | | [protobuf](https://github.com/protocolbuffers/protobuf) | `4.25.3` | `5.27.1` | | [pygments](https://github.com/pygments/pygments) | `2.17.2` | `2.18.0` | | [pytest](https://github.com/pytest-dev/pytest) | `7.4.4` | `8.2.2` | | [requests](https://github.com/psf/requests) | `2.31.0` | `2.32.3` | | [ruff](https://github.com/astral-sh/ruff) | `0.1.15` | `0.4.8` | | [zipp](https://github.com/jaraco/zipp) | `3.18.1` | `3.19.2` | | [uv](https://github.com/astral-sh/uv) | `0.1.36` | `0.2.11` | Updates `anyio` from 4.3.0 to 4.4.0 - [Release notes](https://github.com/agronholm/anyio/releases) - [Changelog](https://github.com/agronholm/anyio/blob/master/docs/versionhistory.rst) - [Commits](agronholm/anyio@4.3.0...4.4.0) Updates `typing-extensions` from 4.11.0 to 4.12.2 - [Release notes](https://github.com/python/typing_extensions/releases) - [Changelog](https://github.com/python/typing_extensions/blob/main/CHANGELOG.md) - [Commits](python/typing_extensions@4.11.0...4.12.2) Updates `opentelemetry-sdk` from 1.24.0 to 1.25.0 - [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-python@v1.24.0...v1.25.0) Updates `opentelemetry-exporter-otlp-proto-grpc` from 1.24.0 to 1.25.0 - [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-python@v1.24.0...v1.25.0) Updates `babel` from 2.14.0 to 2.15.0 - [Release notes](https://github.com/python-babel/babel/releases) - [Changelog](https://github.com/python-babel/babel/blob/master/CHANGES.rst) - [Commits](python-babel/babel@v2.14.0...v2.15.0) Updates `black` from 23.12.1 to 24.4.2 - [Release notes](https://github.com/psf/black/releases) - [Changelog](https://github.com/psf/black/blob/main/CHANGES.md) - [Commits](psf/black@23.12.1...24.4.2) Updates `certifi` from 2024.2.2 to 2024.6.2 - [Commits](certifi/python-certifi@2024.02.02...2024.06.02) Updates `docutils` from 0.20.1 to 0.21.2 Updates `grpcio` from 1.63.0 to 1.64.1 - [Release notes](https://github.com/grpc/grpc/releases) - [Changelog](https://github.com/grpc/grpc/blob/master/doc/grpc_release_schedule.md) - [Commits](grpc/grpc@v1.63.0...v1.64.1) Updates `importlib-metadata` from 7.0.0 to 7.1.0 - [Release notes](https://github.com/python/importlib_metadata/releases) - [Changelog](https://github.com/python/importlib_metadata/blob/main/NEWS.rst) - [Commits](python/importlib_metadata@v7.0.0...v7.1.0) Updates `opentelemetry-api` from 1.24.0 to 1.25.0 - [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-python@v1.24.0...v1.25.0) Updates `opentelemetry-exporter-otlp-proto-common` from 1.24.0 to 1.25.0 - [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-python@v1.24.0...v1.25.0) Updates `opentelemetry-proto` from 1.24.0 to 1.25.0 - [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-python@v1.24.0...v1.25.0) Updates `packaging` from 24.0 to 24.1 - [Release notes](https://github.com/pypa/packaging/releases) - [Changelog](https://github.com/pypa/packaging/blob/main/CHANGELOG.rst) - [Commits](pypa/packaging@24.0...24.1) Updates `protobuf` from 4.25.3 to 5.27.1 - [Release notes](https://github.com/protocolbuffers/protobuf/releases) - [Changelog](https://github.com/protocolbuffers/protobuf/blob/main/protobuf_release.bzl) - [Commits](protocolbuffers/protobuf@v4.25.3...v5.27.1) Updates `pygments` from 2.17.2 to 2.18.0 - [Release notes](https://github.com/pygments/pygments/releases) - [Changelog](https://github.com/pygments/pygments/blob/master/CHANGES) - [Commits](pygments/pygments@2.17.2...2.18.0) Updates `pytest` from 7.4.4 to 8.2.2 - [Release notes](https://github.com/pytest-dev/pytest/releases) - [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst) - [Commits](pytest-dev/pytest@7.4.4...8.2.2) Updates `requests` from 2.31.0 to 2.32.3 - [Release notes](https://github.com/psf/requests/releases) - [Changelog](https://github.com/psf/requests/blob/main/HISTORY.md) - [Commits](psf/requests@v2.31.0...v2.32.3) Updates `ruff` from 0.1.15 to 0.4.8 - [Release notes](https://github.com/astral-sh/ruff/releases) - [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md) - [Commits](astral-sh/ruff@v0.1.15...v0.4.8) Updates `zipp` from 3.18.1 to 3.19.2 - [Release notes](https://github.com/jaraco/zipp/releases) - [Changelog](https://github.com/jaraco/zipp/blob/main/NEWS.rst) - [Commits](jaraco/zipp@v3.18.1...v3.19.2) Updates `uv` from 0.1.36 to 0.2.11 - [Release notes](https://github.com/astral-sh/uv/releases) - [Changelog](https://github.com/astral-sh/uv/blob/main/CHANGELOG-PREVIEW.md) - [Commits](astral-sh/uv@0.1.36...0.2.11) --- updated-dependencies: - dependency-name: anyio dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: typing-extensions dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: opentelemetry-sdk dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: opentelemetry-exporter-otlp-proto-grpc dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: babel dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: black dependency-type: direct:production update-type: version-update:semver-major dependency-group: sdk-python - dependency-name: certifi dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: docutils dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: grpcio dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: importlib-metadata dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: opentelemetry-api dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: opentelemetry-exporter-otlp-proto-common dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: opentelemetry-proto dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: packaging dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: protobuf dependency-type: direct:production update-type: version-update:semver-major dependency-group: sdk-python - dependency-name: pygments dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: pytest dependency-type: direct:production update-type: version-update:semver-major dependency-group: sdk-python - dependency-name: requests dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: ruff dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: zipp dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python - dependency-name: uv dependency-type: direct:production update-type: version-update:semver-minor dependency-group: sdk-python ... Signed-off-by: dependabot[bot] <[email protected]>
|
The following labels could not be found: |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
dependabot
bot
deleted the
dependabot/pip/sdk/python/sdk-python-0ffeacbfe3
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps the sdk-python group with 21 updates in the /sdk/python directory:
4.3.04.4.04.11.04.12.21.24.01.25.01.24.01.25.02.14.02.15.023.12.124.4.22024.2.22024.6.20.20.10.21.21.63.01.64.17.0.07.1.01.24.01.25.01.24.01.25.01.24.01.25.024.024.14.25.35.27.12.17.22.18.07.4.48.2.22.31.02.32.30.1.150.4.83.18.13.19.20.1.360.2.11Updates
anyiofrom 4.3.0 to 4.4.0Release notes
Sourced from anyio's releases.
Changelog
Sourced from anyio's changelog.
... (truncated)
Commits
053e8f0Bumped up the versione7f750bFixed memory object stream sometimes dropping sent items (#735)9f5f14bFixed task group getting cancelled if start() gets cancelled (#717)8b648bcAdjusted the pull request template3ff5e9aRearranged changelog items541d1f8[pre-commit.ci] pre-commit autoupdate (#734)8a07690FixMemoryObjectSendStream.send(falsey)not raisingBrokenResourceErrorw...4b3de97Adjust the headings in the PR templatedfc44cfAdded__slots__toAsyncResource(#733)96920b0Fix typo in PR template (#730)Updates
typing-extensionsfrom 4.11.0 to 4.12.2Release notes
Sourced from typing-extensions's releases.
... (truncated)
Changelog
Sourced from typing-extensions's changelog.
... (truncated)
Commits
e1250ffPrepare release 4.12.2 (#426)53bcddeAvoid error if origin has a buggy eq (#422)7269638Prepare release 4.12.1 (#418)8dfcf3cFixTypeErroron nestedAnnotatedtypes where the inner type has unhashab...d76f591Switch from flake8 to ruff (#414)920d60dSupport my PEP 649 branch (#412)e792bceIgnore fewer flake8 rules when linting tests (#413)f90a8dcPrepare release 4.12.0 (#408)118e1a6Make sureisinstance(typing_extensions.ParamSpec("P"), typing.TypeVar)is u...910141aAdd security documentation (#403)Updates
opentelemetry-sdkfrom 1.24.0 to 1.25.0Changelog
Sourced from opentelemetry-sdk's changelog.
... (truncated)
Commits
257e6fe[release/v1.25.x-0.46bx] Prepare release 1.25.0/0.46b0 (#3942)c6edd0fAuto instrumentation parameters (#3864)d73593dFix prometheus metric name and unit conversion (#3924)187048aRecord links with invalid SpanContext (#3917)832e859Add OpenTelemetry trove classifiers to PyPI packages (#3913)dbf6943Fixup pylint broad exceptions warnings (#3923)808d0cePin codespell version to fix builds (#3930)8b80a28Fix class BoundedAttributes to have RLock rather than Lock (#3859)a156bf1Do not install unnecessary packages (#3896)eef2015Bump jinja2 from 3.1.3 to 3.1.4 in /docs/getting_started/tests (#3907)Updates
opentelemetry-exporter-otlp-proto-grpcfrom 1.24.0 to 1.25.0Changelog
Sourced from opentelemetry-exporter-otlp-proto-grpc's changelog.
... (truncated)
Commits
257e6fe[release/v1.25.x-0.46bx] Prepare release 1.25.0/0.46b0 (#3942)d73593dFix prometheus metric name and unit conversion (#3924)832e859Add OpenTelemetry trove classifiers to PyPI packages (#3913)dbf6943Fixup pylint broad exceptions warnings (#3923)a156bf1Do not install unnecessary packages (#3896)6e84b1fexporter: add is_remote_parent span flags to OTLP exported spans and links (#...fbbf5b5Revert modifications to Apache license (#3870)afc3aceBump black to 24.3.0 (#3871)b51a6f8Sort by label keys before generating labels key and value lists (#3698)9398f26Use a single install command for lint (#3848)Updates
babelfrom 2.14.0 to 2.15.0Release notes
Sourced from babel's releases.
Changelog
Sourced from babel's changelog.
Commits
40b194fPrepare for 2.15.0 release (#1079)c2e6c6eEncode support for the "fall back to short format" logic for time delta forma...1a03526Include Unicode license inlocale-dataand in documentation (#1074)c0fb56eAllow alternative space characters as group separator when parsing numbers (#...fe82fbcUse CLDR 44 and adjust tests to match new data (#1071)e0d1018Improve .po IO (#1068)40e60a1Upgrade GitHub Actions (#1054)2a1709aDrop support for Python 3.7 (EOL since June 2023) (#1048)Updates
blackfrom 23.12.1 to 24.4.2Release notes
Sourced from black's releases.
... (truncated)
Changelog
Sourced from black's changelog.
... (truncated)
Commits
3702ba2Prepare release 24.4.2 (#4335)e4aaa8aFix incorrect f-string tokenization (#4332)ba88fc3Simplify string tokenization regexes (#4331)5683242New release templatee7fb048Prepare release 24.4.1 (#4328)3f0f8f1Support PEP 696 (#4327)2f88085Github Action: Directly install from repo ifexport-substis skipped (#4313)12ce3dbMove changelog entry to right section (#4326)1354be2Add support to style function definitions with newlines before function stubs...f4b644bPrevent wrapping of multiline fstrings in parens (#4325)Updates
certififrom 2024.2.2 to 2024.6.2Commits
124f4ad2024.06.02 (#291)c2196ce--- (#290)fefdeecBump actions/checkout from 4.1.4 to 4.1.5 (#289)3c5fb15Bump actions/download-artifact from 4.1.6 to 4.1.7 (#286)4a9569aBump actions/checkout from 4.1.2 to 4.1.4 (#287)1fc8086Bump peter-evans/create-pull-request from 6.0.4 to 6.0.5 (#288)ad52dceBump peter-evans/create-pull-request from 6.0.3 to 6.0.4 (#283)651904fBump actions/upload-artifact from 4.3.1 to 4.3.3 (#284)84fcfbaBump actions/download-artifact from 4.1.4 to 4.1.6 (#285)46b8057Bump peter-evans/create-pull-request from 6.0.2 to 6.0.3 (#282)Updates
docutilsfrom 0.20.1 to 0.21.2Updates
grpciofrom 1.63.0 to 1.64.1Release notes
Sourced from grpcio's releases.
... (truncated)
Commits
d799491[Release] Bump version to 1.64.1 (on v1.64.x branch) (#36748)74eedcc[backport][build] Update Gazelle bazel dependency (#36745) (#36746)c0216b4[OTel] Generate pkg-config file for grpcpp_otel_plugin (#36686) (#36722)192c054[OTel] Add latency view to example (#36601) (#36720)f740f35[Python Server] Remove abstractmethod notation for add_registered_method_hand...c64a23d[OTel] Add find_package call for OTel dependency in installed gRPC configurat...fbd6f95C++20 compat: use invoke_result_t for C++17 and up (#36016) (#36690)979afe0[StatsPlugin] Fix use-after-free issue (#36664) (#36670)b8a04ac[Release] Bump version to 1.64.0 (on v1.64.x branch) (#36633)acd8b33[Release] Bump version to 1.64.0-pre2 (on v1.64.x branch) (#36573)Updates
importlib-metadatafrom 7.0.0 to 7.1.0Changelog
Sourced from importlib-metadata's changelog.
Commits
f5d6b5fFinalize2ef3b5fMerge commit '1711b2c198'1711b2cNeed to include names from test.support for py312 compat.47b14acMake MetadataPathFinder.find_distributions a classmethod for consistency with...adc4b12Ensure tests do not leak references in sys.modules.07d894dCopy backport of isolated_modules from importlib_resources.e30a16dConsolidated test support logic in jaraco.test.cpython.41ca039Moved compatibility tests to the compat package, as they're not included in C...5950f43Remove legacy logic for Python 3.7.ffa719bMoved compatibility module to compat package.Updates
opentelemetry-apifrom 1.24.0 to 1.25.0Changelog
Sourced from opentelemetry-api's changelog.