#I think I'm hitting this on main right

1 messages · Page 1 of 1 (latest)

olive magnet
#

I can't see the dagger cloud link, do you have a link to your code? So I can repro and figure out what's happening

warm ibex
#

Yeah for sure. The link took a couple minutes to load for me. Probably the same issue 🙂

#

btw it wasn't broken on 0.9.1 but I ran into a different bug and had to switch to main

olive magnet
#

Hm okay, last time this happened it was due to functions accidentally increasing the ID size, but we have integ tests for that now (modules w/ 100 functions in both SDKs). So must be something different this time.

My first guess is it might be dependencies. Your module has a relatively complicated DAG of deps. Module IDs including the IDs of their deps, which I'm now realizing is not de-duped across the DAG, which is gonna give it worst case exponential size.

#

I'll verify and fix if that's the problem

warm ibex
#

Nice yeah I think the full dependency tree unless I'm forgetting something should look something like

- backend
  - golang
- frontend
  - golang
  - hugo
    - github
#

I think each are relatively small, like 3~~-6~~ functions each

olive magnet
# warm ibex Nice yeah I think the full dependency tree unless I'm forgetting something shoul...

This fixes it for me: https://github.com/dagger/dagger/pull/6014

At least, I can run dagger functions successfully now.

Needs a little more work before mergable, but I'll do that tonight so we can merge early tomorrow morning once reviewed.

GitHub

WIP:

Add integ test coverage for big DAG of deps
Add some caching to make up for lack of memoizing dep modules in ID

Ref: #1168341591606444122 message...