Closed MaceWindu closed 1 month ago
Currently resolved configuring options from here https://github.com/datalust/seq-tickets/issues/2086#issuecomment-2005697748 to bigger numbers
Thanks for the heads-up. This one is by design, the expression complexity limit is a safety mechanism to avoid instability when processing very deeply nested expressions (essentially a "soft" stack overflow exception).
Increasing the limit is not harmful but may increase the likelihood of crashes. Is there any way to "garbage collect" these very complex filters to produce simpler ones, e.g. by removing duplicated or redundant clauses?
We cleanup signals from time to time from obsoleted filters, but I don't think it will provide any noticeable reduction in size of filter.
In any case, I think I'm fine with limits change workaround, so I will close it.
Describe the bug
I've created a group for signals to be able to work with UNION of signals and it didn't worked out well as it gives following error when all signals in group selected:
Deselecting several signals helps, but defeat purpose of using group.
To Reproduce
I suspect it is easy to reproduce with several signals with big set of filters, but if needed I can provide some. I suspect all signal filters ORed into single filter, which doesn't work well with filter expression size limits.
Expected behavior
As group query size expected to be a sum of sizes of contained signals, probably it doesn't make sense to enforce limits here?
Environment (please complete the following information):