This is probably not a bug, but I found the behavior unintuitive when working on the source code that generated the constraint. Maybe we can improve the implementation of scrape to handle this case.
I have a code in Flux with an assert like this: assert(i < 10 && i >= 2). The code generates the following constraint that requires the qualifier x >= 2, but scrape=both fails to find it.
This is probably not a bug, but I found the behavior unintuitive when working on the source code that generated the constraint. Maybe we can improve the implementation of scrape to handle this case.
I have a code in Flux with an assert like this:
assert(i < 10 && i >= 2)
. The code generates the following constraint that requires the qualifierx >= 2
, butscrape=both
fails to find it.If I simplify the assert to
assert(x >= 2)
(or I split the assert in two), scrape does work. This is the constraint for the simplified assert.