You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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]>
returnerrors.Wrap(err, "failed to parse oci-max-parallelism, should be positive integer, 0 for unlimited, or 'num-cpu' for setting to the number of CPUs")
645
+
returnfmt.Errorf("failed to parse oci-max-parallelism, should be positive integer, 0 for unlimited, or 'num-cpu' for setting to the number of CPUs: %w", err)
0 commit comments