We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The following test cases show unintuitive behavior when running on "buffer": b"0123"
"buffer": b"0123"
"patterns": [ "/(1 & 2)/C", "/01/H", "/23/H", ], "result": [1, 2]
"patterns": [ "/(1 & 2)/HC", "/01/H{max_offset=2}", "/23/H", ], "result":[1, 2]
"patterns": [ "/(1 & 2)/C", "/01/H{max_offset=2}", "/23/H", ], "result": [1, 2]
Expected behavior:
"patterns": [ "/(1 & 2)/HC", "/01/H", "/23/H", ], "result": [1, 2, 0],
The text was updated successfully, but these errors were encountered:
Proposed fix:
diff --git a/src/rose/stream.c b/src/rose/stream.c index 26268dd..33e29db 100644 --- a/src/rose/stream.c +++ b/src/rose/stream.c @@ -534,16 +534,20 @@ int can_never_match(const struct RoseEngine *t, char *state, return 0; } if (mmbit_any(getActiveLeafArray(t, state), t->activeArrayCount)) { DEBUG_PRINTF("active leaf\n"); return 0; } + if (t->ckeyCount) { + return 0; + } + return 1; } void roseStreamExec(const struct RoseEngine *t, struct hs_scratch *scratch) { DEBUG_PRINTF("OH HAI [%llu, %llu)\n", scratch->core_info.buf_offset, scratch->core_info.buf_offset + (u64a)scratch->core_info.len); assert(t); assert(scratch->core_info.hbuf);
Sorry, something went wrong.
No branches or pull requests
The following test cases show unintuitive behavior when running on
"buffer": b"0123"
"patterns": [ "/(1 & 2)/C", "/01/H", "/23/H", ], "result": [1, 2]
"patterns": [ "/(1 & 2)/HC", "/01/H{max_offset=2}", "/23/H", ], "result":[1, 2]
"patterns": [ "/(1 & 2)/C", "/01/H{max_offset=2}", "/23/H", ], "result": [1, 2]
Expected behavior:
"patterns": [ "/(1 & 2)/HC", "/01/H", "/23/H", ], "result": [1, 2, 0],
The text was updated successfully, but these errors were encountered: