Arkadiusz Bokowy

@borine +1 for nice investigation of this issue! > Unfortunately so far I have not been able to identify any system events that an application can listen for to know...

@borine I see that you are working on this and some CI check are failing. After my recent changes to master (added mutexes here and there), test-alsa-pcm might fail on...

Force pushed to resolved conflicts.

Sorry for such a late reply, but somehow I've missed your comment... GitHub does not send notification when comment is edited :/ > It seems like the core problem is...

I've made one check with such setup: ``` . ├── main.py # this file contains line exceeding 50 characters ├── setup.cfg # [flake8]: max-line-length = 50 └── subproject ├── extra.py...

> Perhaps flake8-requirements should take the --config directory as the "root", not just default to the repo root. What do you think? Hmm... maybe you are right. But I'm thinking...

> Until this is supported by shellcheck, I will not accept this. That's OK with me. This PR was only a PoC. So I guess I will have to learn...

Yes, I can take a look at it. You can send it on my email or submit PR for this repo with lib added to archives directory. I'm not sure...

Hmm... indeed it seems that I've forgotten about that issue... Unfortunately, right now I'm not able to test it, because, due to unexpected chain of events, I've fried my laptop...

I've done some refactoring of transport threads management. I hope that it will solve this unwanted cancellation issue. The code is pushed to https://github.com/arkq/bluez-alsa/tree/state-management branch. @ubicore if you are still...