Skip to content
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

Revert "feat: chainlit option to require websocket" #1547

Conversation

sandangel
Copy link
Contributor

Reverts #1379

This is not working as intended. There are some race condition between events that we are subcribing to. So just revert and then we can implement a proper PR with tests.

@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Nov 27, 2024
Copy link
Collaborator

@dokterbob dokterbob left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, this is why we do release candidates. 😅

Thanks for catching this before we release. Indeed, let's have tests.

Would you be able to replicate the issue your experiencing in an E2E or unit test with #1379? We can then use that regression test that a future patch won't contain it.

Also, a PR to remove the feature from the 2.0 changelog would be an amazing help! If not, I'll do it on release.

@dokterbob dokterbob merged commit a9f07b9 into Chainlit:main Nov 28, 2024
9 checks passed
@sandangel sandangel deleted the revert-1379-fix/chainlit-upgrade-websocket-retry branch November 28, 2024 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants