You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did this a few times to confirm that 0x10563306 indicates the value of p.nextExprID passed to Value. Clearly the break condition of that loop in nextID is never happening.
The text was updated successfully, but these errors were encountered:
Describe the bug
It's possible to get an infinite loop when calling ResidualAst with certain inputs.
To Reproduce
Check which components this affects:
Sample expression and input that reproduces the issue:
Test setup:
Expected behavior
The call to ResidualAst should return in a resonable time.
Additional context
I got this with cel-go version 0.7.2, Go version 1.16 on
darwin/amd64
, and haven't tried with any other versions.Here's a stack trace, obtained via SIGQUIT of the above test after a few seconds:
I did this a few times to confirm that
0x10563306
indicates the value ofp.nextExprID
passed toValue
. Clearly the break condition of that loop innextID
is never happening.The text was updated successfully, but these errors were encountered: