-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calling CelRuntimeBuilder.setStandardEnvironmentEnabled(false)
does not disable standard functions
#255
Comments
copybara-service bot
pushed a commit
that referenced
this issue
Feb 27, 2024
Fixes #255 PiperOrigin-RevId: 610809925
This is most definitely unintended. #256 should fix this when it lands. Thanks for reporting. |
copybara-service bot
pushed a commit
that referenced
this issue
Feb 27, 2024
Fixes #255 PiperOrigin-RevId: 610809925
copybara-service bot
pushed a commit
that referenced
this issue
Feb 27, 2024
Fixes #255 PiperOrigin-RevId: 610809925
copybara-service bot
pushed a commit
that referenced
this issue
Feb 28, 2024
Fixes #255 PiperOrigin-RevId: 610809925
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note
I see
StandardFunctions.add()
being called twice inCelRuntimeLegacyImpl.build()
, once inDefaultDispatcher.create()
unconditionally, and another whenstandardEnvironmentEnabled
is true.Are these intended? Or how can I disable the standard functions completely to achieve something like cel-go's
NewCustomEnv
?cel-java/runtime/src/main/java/dev/cel/runtime/CelRuntimeLegacyImpl.java
Lines 230 to 233 in 4f8f455
cel-java/runtime/src/main/java/dev/cel/runtime/DefaultDispatcher.java
Lines 76 to 80 in 4f8f455
The text was updated successfully, but these errors were encountered: