Building 70 Projects ranging from beginner to advanced so anyone can β learn from, build upon, use as a reference, or even copy directly. Owned by my cybersecurity company π
Go aicertificationcloud-engineeringcybercybersecuritycybersecurity-analystcybersecurity-certificationcybersecurity-certificationscybersecurity-educationcybersecurity-jobscybersecurity-portfoliocybersecurity-projectscybersecurity-toolsgrchackinglearningpentestingproject-repositoryprojetcspython
fix(lisdex): m2-gate matched B11's old wording, and a symbol census cannot see a gate
CarterPerez-devbcb1c52cc781
diff --git a/PROJECTS/advanced/zero-day-vulnerability-scanner/scripts/m2-gate.sh b/PROJECTS/advanced/zero-day-vulnerability-scanner/scripts/m2-gate.shindex d008f106..f5225120 100755--- a/PROJECTS/advanced/zero-day-vulnerability-scanner/scripts/m2-gate.sh+++ b/PROJECTS/advanced/zero-day-vulnerability-scanner/scripts/m2-gate.sh@@ -158,9 +158,10 @@ if OUTPUT="$("$LISDEX" build "$BAZEL_TREE" --work "$WORK/bazel-work" --jobs 1 2>FAILURES=$((FAILURES + 1))record "FAIL degradation bazel tree reported success"else- if printf '%s' "$OUTPUT" | grep -q 'bazel detected but lisdex plans no bazel build'; then- printf ' PASS bazel is detected and reported unsupported\n'- record "PASS degradation bazel detected and named unsupported"+ if printf '%s' "$OUTPUT" | grep -qF 'note: bazel detected; lisdex plans no bazel build' \+ && printf '%s' "$OUTPUT" | grep -qF 'the only one(s) present are bazel'; then+ printf ' PASS bazel is detected, named unsupported, and named as the cause\n'+ record "PASS degradation bazel detected, named unsupported and named as the cause"elseprintf ' FAIL bazel degradation was not explained:\n%s\n' "$OUTPUT"FAILURES=$((FAILURES + 1))