Flask-SocketIO VS spec

Hi! I'm trying to write test cases for Flask socket io using pytest. But it seems we can't test the emitted messages from namespaces using pytest only. What would be a good approach to test it? Also, I am trying to figure out resources for flask socketio testing, I tried writing tests using some repos but there's not much explanation on what is being done. So it would be really helpful if anyone could point me towards any resources. These are the repos I was talking about 1. https://github.com/miguelgrinberg/Flask-SocketIO/blob/main/test_socketio.py 2. https://github.com/julianYaman/bitcoinPriceApp_python/tree/master

WS-Emit is based on Flask-SocketIO and sending message is as simple as in any other flask-socketio application:

https://github.com/miguelgrinberg/Flask-SocketIO might help you.

The framework is driven by the AsyncAPI specification, built on top of Flask-SocketIO. and inspired by Connexion.

I don't know what module you're using for websockets, but looking at an issue posted on one of them, the thread should periodically sleep in order for I/O to function properly.

I'm running a Flask server on my local machine and am using it to pull data from a serial port and display it in real time on a webpage with Flask-socketio. I followed the example here and am encountering an interesting behavior. I was able to replicate the results of the example, but when I alter the background_thread function to include reading and parsing data from the serial port, something seems to be blocking the socket from sending the data. My code correctly establishes a socket and opens the connection, and can even emit messages correctly at the beginning of the thread function, but once it hits a time.sleep(5), emitting doesn't work anymore. Here's the original thread function that works (and includes a time.sleep()!):

https://github.com/miguelgrinberg/Flask-SocketIO/issues/1010 looks like flask socket io does not support waitress

I have Flask application with SocketIO integration.Current user flow seems like 

I think you're having this issue. https://github.com/miguelgrinberg/Flask-SocketIO/issues/1570

Check Miguel's flask-socketio examples.

AsyncAPI: Interested in how to define your WebSocket APIs? One of the most advanced realtime specifications is the AsyncAPI specification, which comes with various generators for code and documentation, as well as renderers for the specifications.

Our journey with FastStream started when we needed to integrate our machine learning models into a customer's Apache Kafka environment. To streamline this process, we created FastKafka using AIOKafka, AsyncAPI, and asyncio. It was our first step in making message queue management easier.

Automatic Docs: Stay ahead with automatic AsyncAPI documentation

FastStream supports in-memory testing, AsyncAPI schema generation and more... If you are interested, please support our project by giving a GH start and joining our discord server.

However, in order for the system to work effectively, there must be a common understanding between the components regarding events and their data structures. This is where AsyncAPI comes in; it helps define a contract that describes how the components communicate and behave effectively.

You can also take a look at https://www.asyncapi.com/ (a spec for asynchronous APIs). It's useful for this use case, that is, building a well structured websocket interface with pub/sub.

Sure! Next step I am working on AsyncAPI scheme generation by your application code. It's also includes a project generation from scheme, scheme web view (lika the Swagger for OpanAPI), etc. It will a much difficult than just another broker implementation...

Onboarding - Enable developers to quickly learn how to consume the exposed APIs. For example, offer OpenAPI or AsyncAPI documentation and provide a portal and sandbox.