You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit df3e889
Browse filesBrowse the repository at this point in the historyBrowse files
easonLiangWorldedtech
committed
config-eslint,api: close the escaped-group hole and reach the ignored workflow tests
abortSubstringSelector consumed escaped dots and anchors but stopped at an inline
non-capturing group, so toThrow(/^Request was aborted\.$/) and toThrow(/abort(?:ed)?/i)
fell through the rule while the same message written as a string was flagged. The pattern
branch now consumes a (?:ed|ion|al)? group verbatim, and the four workflow tests that are
exempt from the path-traversal selectors get the abort rule back instead of losing the
whole block.
Assertions tightened where they were blind: Requesty's normalised completion message
instead of a substring that the unwrapped SDK error also satisfies, the model-lookup
rejection by object identity, the ask abort message by task and instance id, and a case
where only the per-request timeout may abort while the caller signal stays live.
Controls, each run and reverted: rule suite 90/90 with the new tail, 89/90 with the old
one and with the workflow mapping removed; requesty spec fails on the exact message when
handleOpenAIError is bypassed at both catch sites, fails on Object.is when the lookup
assertion takes a copy, and times out in the settle guard at timeoutMs 100_000; the ask
assertion fails against foreign task ids. eslint over src is 0 findings before and after,
the repo-wide abort-rule count stays 11, the four workflow files score 0 under the
selector alone, and the mutation selection is 46 executable lines against main tip / 0
packages against head^1 (cap 500).
0 commit comments