mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-11-02 09:01:50 -05:00
8383ee8552
If A2DP remote does not acquire its pending transport within a timeout, we won't get a write error in a2dp-sink, but instead the transport becomes idle. Currently, we continue writing to the socket as if everything was fine, even though the data won't be processed at the remote end. Handle this by stopping the node and emitting a node error event. Pipewire may then restart the node to retry. |
||
|---|---|---|
| .. | ||
| examples | ||
| include | ||
| plugins | ||
| tests | ||
| tools | ||
| meson.build | ||