#core dev architecture discussion

1 messages · Page 1 of 1 (latest)

fringe basalt
#

i also wanna try something new this time - could we try putting in a list of potential topics to discuss and upvoting them beforehand? since we seem to not get time to talk about everything, feels like we should pick-and-choose what goes in

#

cc @distant notch @tight topaz @slow temple @last yew @trim jacinth

#

✨ topic idea: cached/pending/new otel work that @tight topaz's doing

#

✨ @distant notch's metrics work, also curious about where this is going

#

✨ version compatibility? there's some maybe hard-breaks in the pipeline at the moment, maybe we should discuss how to do this cleanly and avoid breaking the daggerverse?

#

(apologies for mass pings)

trim jacinth
#

i'm personally very curious what's going on in the world of caching and disk around the engine

distant notch
#

I'll be on a plane to SF during the meeting tomorrow, but summarized OTel metrics stuff in the PR description now: https://github.com/dagger/dagger/pull/8506

  • Only thing left is that the test I added is flaky due to being inherently time based, but I think worst case I can just rm it before merge and then add a good one using Alex's framework in https://github.com/dagger/dagger/pull/8442. Or if his gets merged first will fix before merge.

Overall even though it's just mostly plumbing setup and a few basic metrics, it's already been pretty interesting. e.g. Go codegen just randomly writes hundreds of MBs to disk even when it doesn't seem to be downloading deps (afaict), occasionally. Been going on short tangents only so far, didn't root cause that one yet. But seems promising in terms of giving us good hints on what to investigate further, especially once we add more and more metrics.

proud prairie
#

Can I join the discussion? 🙂