Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Find assert failure #93

Merged
merged 2 commits into from
May 13, 2024
Merged

Find assert failure #93

merged 2 commits into from
May 13, 2024

Conversation

heckj
Copy link
Collaborator

@heckj heckj commented May 12, 2024

resolves #92

Don't merge until expected behavior is fully understood. I think this is falling for the "get an Unavailable message first, followed by a secondary message with data" that is resulting in a confused response, but I need to check that theory...

@heckj heckj self-assigned this May 12, 2024
@heckj heckj changed the title Find assert failure Find assert failure (DO NOT MERGE) May 12, 2024
@heckj heckj changed the title Find assert failure (DO NOT MERGE) Find assert failure May 13, 2024
@heckj heckj merged commit 7a48691 into main May 13, 2024
1 check passed
@heckj heckj deleted the findAssertFailure branch May 13, 2024 17:40
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Assert failing in WebSocketProvider.connect after repo.find
1 participant