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 cd22b5c
Browse filesBrowse the repository at this point in the historyBrowse files
These suites are characterization tests: they assert current behavior so
the SDK v2 migration can show it changed nothing. Some of that behavior
is wrong. Each test that pins a known bug now carries a one-line marker
directly above it (above any decorators):
# KNOWN BUG #<issue>: pins current (wrong) behavior; the fix changes this assertion.
or, where no issue is filed:
# KNOWN BUG (no issue): <what is wrong>; the fix changes this assertion.
`git grep "KNOWN BUG"` lists exactly the bug-pinning tests. Tests that
guard fixed behavior, check correct behavior, or pin a design a feature
request wants changed (e.g. #4448's fixed timeouts) are left unmarked.
Comments only; no assertion changes.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: cliffhall <[email protected]>
# KNOWN BUG (no issue): an empty page without Node reports "No more content available" at start_index 0 instead of a simplification failure; the fix changes this assertion.
0 commit comments