-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
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
Clarify cdk parity test behavior #37407
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @erohmensing and the rest of your teammates on |
if constructor == _concurrent_stream: | ||
assert hasattr(stream._cursor, "state") | ||
assert str(stream._cursor.state) == "{'__ab_full_refresh_state_message': True}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weirdly enough you can even check this in the beginning before the _read
because the cursor has a constant state. but we can check it here at the end
Later when we switch to incremental checkpointing as it wants, if we give it the right cursor, we should get proper state messages with the right cursor
c72651f
to
7cf265c
Compare
A small change to clarify that the check for "we get a state message from the stream" is not a temporary test behavior, it is permanent for the short term (in the long term, we'd want everything to work as concurrent does) as concurrent streams don't emit state messages, the concurrent source does.
Changes the test to check the state at the end of the test for concurrent sources, which is about the best we can do right now.