Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sorter has been destroyed with live tasks still in queue. #542

Open
Tvde1 opened this issue Nov 14, 2018 · 2 comments
Open

Sorter has been destroyed with live tasks still in queue. #542

Tvde1 opened this issue Nov 14, 2018 · 2 comments

Comments

@Tvde1
Copy link
Contributor

Tvde1 commented Nov 14, 2018

I'm using the last tutorial but with a websocket connection. I've connected and started + stopped scanning. Then I started scanning again and I got hit with this error.

It happens at the line await client.StartScanningAsync();
I didn't get any useful stacktrace.

@Tvde1
Copy link
Contributor Author

Tvde1 commented Nov 14, 2018

I can reproduce it by spamming 1 in tutorial 7.

@qdot
Copy link
Member

qdot commented Nov 23, 2018

Hmm. I can't seem to repro this using a websocket connection and a 0.2.3 buttplug server. Is that the setup you're using?

Even without the repo, this is a problem in the example that I should fix anyways. Pretty much every awaited call in ButtplugClient should be in a try block (which I neglected to put in the examples). The reason this is throwing is that for some reason the connector is being destroyed, and taking the message sorter with it. This means anything waiting on a message back from the server will throw, as all of those outstanding actions will fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants