How to trigger an Exception correctly ?

[AlaaIssa-Epex]

Hello,

First of all i would like to thank you so much for the amazing library, my question is i am struggling to throw an exception when something fails in on_ws_frame, my target is to stop execution (raise Exception('bla bla')), how to achieve that ?

def on_ws_frame(self, transport: WSTransport, frame: WSFrame) -> None:
    """
    Triggered when a WebSocket frame is received.

    Args:
        transport (WSTransport): WebSocket transport instance.
        frame (WSFrame): Received WebSocket frame.
    """
    try:
        # Process the incoming frame
        payload_bytes, frame = self.pre_message_extension.process_incoming(frame)
        logger.info(f'Received frame: {WSFrame}')

        # Delegate message details construction to utility
        message_details = self.message_builder.build_message_details(
            username=self.username if self.username is not None else '',
            session_id=self.session_id,
            frame=frame,
            payload_bytes=payload_bytes,
        )

        # Append the processed message details
        self.messages.append(message_details)
        logger.info(f"Processed message: {json.dumps(message_details.model_dump(exclude_unset=False), indent=4)}", also_console=True)

    except Exception as e:
        raise ValueError(f"Error processing frame: {e}") from e

[tarasko]

Hi @AlaaIssa-Epex
In 1.9.0 an exception is not swallowed anymore for client side websockets, it is transferred to and re-raised by wait_disconnected.
See https://github.com/tarasko/picows/blob/master/examples/reconnecting_client.py

[AlaaIssa-Epex]

Hello Taras, Thank you so much, it's working great. Thanks a lot for the amazing work. Best Regards, Alaa Issa

…

________________________________ From: Taras Kozlov ***@***.***> Sent: Thursday, June 5, 2025 6:27 PM To: tarasko/picows ***@***.***> Cc: Alaa ISSA ***@***.***>; Mention ***@***.***> Subject: Re: [tarasko/picows] How to trigger an Exception correctly ? (Discussion #42) Hi @AlaaIssa-Epex<https://github.com/AlaaIssa-Epex> In 1.9.0 an exception is not swallowed anymore for client side websockets, it is transferred to and re-raised by wait_disconnected. See https://github.com/tarasko/picows/blob/master/examples/reconnecting_client.py — Reply to this email directly, view it on GitHub<#42 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJJAXWCOMM7JK2PYKN7MNNT3CBVXRAVCNFSM6AAAAAB4CMFQW2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMZYGE4TIMA>. You are receiving this because you were mentioned.Message ID: ***@***.***>