#@Erik Sipsma, I seem to have a limit on
1 messages · Page 1 of 1 (latest)
Tried to repro on main:
package main
type Potato struct{}
func (c *Potato) AddPotato() string {
return "hi"
}
func (c *Potato) AddPotato1() string {
return "hi"
}
func (c *Potato) AddPotato2() string {
return "hi"
}
func (c *Potato) AddPotato3() string {
return "hi"
}
func (c *Potato) AddPotato4() string {
return "hi"
}
func (c *Potato) AddPotato5() string {
return "hi"
}
func (c *Potato) AddPotato6() string {
return "hi"
}
func (c *Potato) AddPotato7() string {
return "hi"
}
func (c *Potato) AddPotato8() string {
return "hi"
}
func (c *Potato) AddPotato9() string {
return "hi"
}
func (c *Potato) AddPotato10() string {
return "hi"
}
func (c *Potato) AddPotato11() string {
return "hi"
}
func (c *Potato) AddPotato12() string {
return "hi"
}
func (c *Potato) AddPotato13() string {
return "hi"
}
echo '{potato{addPotato13}}' | dagger query works for me
am I doing anything different?
Oh wait, dagger call addPotato13 does break w/ the same error
so dagger query works, dagger call doesn't
ETOOMANYPOTATOES
docker logs dagger-engine.dev doesn't show anything too interesting, so might be a CLI issue?
Could it be something as simple as us closing a client too early? Like a timing thing where we were getting lucky before, but now we are taking longer due to the numerous potatoes, and hitting a bug where the client gets closed (or garbage collected and thus inherently closed)? Just a shot in the dark guess
Oh
From strace: ```
[pid 47388] write(2, "Error: query module objects: returned error 502 Bad Gateway: http do: Post "http://dagger/query\": rpc error: code = ResourceExhausted desc = grpc: received message larger than max (13985140 vs. 4194304)\n", 20
3Error: query module objects: returned error 502 Bad Gateway: http do: Post "http://dagger/query": rpc error: code = ResourceExhausted desc = grpc: received message larger than max (13985140 vs. 4194304)
For some reason the CLI is clipping the important part of the error:
ResourceExhausted desc = grpc: received message larger than max (13985140 vs. 4194304)
Our IDs are too big I bet 
My first guess we are just accidentally embedding module and/or type def IDs in IDs or something like that and getting quadratic space complexity. I'll look into it on Monday
Oh, so it’s the load module by id part of the query that’s the issue 👍
I thought of this exact meme last night and was trying to get dalle to generate something, this was the best i got
☝️ I hit the same issue on my last function on gale. I just need one more Potato 😄
PR to fix: https://github.com/dagger/dagger/pull/5947
integ test generates go+python modules w/ 100 functions and uses dagger call, works now!