andig
I've opened https://github.com/simonvetter/modbus/pull/21 if you want to take a look. I've not rewritten the server tests yet as I'd need to migrate them to the grid-x client (or use simonvetter/modbus...
@simonvetter I'd be happy to open a PR for `gofmt` and maybe `golangcilint`- that would already make the diff much smaller.
Seems it is almost impossible to figure out which tool might be causing the issue. It seems it is _not_ the tool invoked but actually _a_ tool that is part...
Invalid, sorry for the noise.
In my specific case the schema was indeed invalid by missing $ref'ed objects. The Claude Error message is crap since it doesn't tell you which tool it is having problems...
Gute Idee- Konsequenz wäre aber dennoch analog https://github.com/evcc-io/evcc/issues/15239#issuecomment-2268448639: - mehrere circuits per Loadpoint - mehrere root circuits (grid, lpc)
> I wouldn't want to publicly compare real and forecasted power values. I would still like to see the currently forecasted value or, alternatively, have a Y axis as guidance....
It looks as if the memory consumption comes from growing `interp.roots` (https://github.com/traefik/yaegi/blob/master/interp/ast.go#L938). Is this something that could be eliminated?
Unfortunately, this will eventually OOM our application and breakes Yaegi usage for our purpose of long-running application.
> I see that you found a solution Unfortunately not. This is a showstopper for us.