Yury Zhuravlev
Yury Zhuravlev
You can use OpenCL
I can confirm as well.
In legacy we never saw this behavior. If the response process returns something we should ignore any errors here.
Hmm seems like any normal HTTP response with 200 code is closed as exception. We set exception to the protocol during send response - https://github.com/python-websockets/websockets/blob/main/src/websockets/asyncio/server.py#L193 inside response here: https://github.com/python-websockets/websockets/blob/main/src/websockets/server.py#L543 after...
I found one workaround: before return `response` form `process_response` you should do `connection.logger.setLevel(logging.CRITICAL)` because it's usually needed for health check or metrics it's fine to do it, we can catch...
@ljharb seems like flat config as well now.
I agree, even more I am using Svelte and I don't need all these React things.
I agree; it should be done somehow. Keeping it in legacy with "deprecated" is also not really good. Here https://svelte.dev/docs/svelte/v5-migration-guide#Event-changes-Event-modifiers, I disagree with the argument: > Adding things like event.preventDefault()...
It's basically bug in #4430 implementation.
Firstly, thank you for the extra workaround. Second, I understand the current design and why it's happened, but it still has bad UX and unexpected/undocumented behavior. I suppose a materialization...