-
[Mon May 11 07:47:16.505904 2015] [:error] [pid 31589:tid 140167048685312] [remote 118.209.9.184:35410] File "/home/zookeepr/zookeepr/zkpylons/controllers/admin.py", line 1147, in rego_desk_list
[Mo…
-
I think it was @johanfylling who suggested that we should have a `style` category rule to enforce ordering of imports, as well as grouping based on the "base path" in the imports. Something along the …
-
Antoine, since a few moments I have the following message in the R console
I think the packages concerns are in the process of the level 3 and maybe we need to update them.
Best,
Mathieu
…
-
Currently when running `tracee --o option:parse-arguments` event arguments will be switched out to a string form where possible.
In order to support #2177 in REGO, it's required that rego signatures …
-
```rego
package p
import rego.v1
foo := data.foo.bar["contains"]("baz")
```
running `opa fmt` on this file rewrites the ref:
```rego
package p
import rego.v1
foo := data.foo.bar.con…
-
When I use the old grammar, the rego input file cannot be recognized correctly. Since I am a rookie and cannot modify the lexer and parser very well, I need the latest rego grammar. I am going to use …
-
Since the outside temperature went below 0, the outdoor sensor (GT2) started to report temperatures in the ~6550 range insted of the expected negative number.
![image](https://github.com/dala318/es…
-
```rego
package test
p {
resp := true
g(true) with f as resp
}
g(x) = f(x)
f(false) = true
```
opa eval -d t.rego data.test.p | -t rego | -t wasm
---|---|---
result | true | undefined
…
-
Fregot, has a var (keyword) to declare variables, but when use this keyword on opa check, it show us this error message:
rego_parse_error: var cannot be used for rule name.
-
Submitted on behalf of Nanzi Yang, a PostDoc of UMN
Ref: https://lists.nephio.org/g/sig-security/message/107
**Detailed analysis:**
The porch has a deployment called porch-server, which is bound …