-
Notifications
You must be signed in to change notification settings - Fork 9
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
Function call never yields result #6
Comments
The handlers you registered directly are - under working conditions - unnecessary but I am sure you already knew this. You are using the right syntax and it should actually work. Did you try the ws example already? I only tested gentle_rpc on Linux yet but it should work on Windows, too. Please let me know if the examples don't work on your machine neither (with the exception of the Otherwise, is there another way to replicate this behavior without the microphone? Thanks! EDIT: Does the server respond with a valid RPC response object with an id? You should be able to check this with your |
Oh, good call on the response, I just checked the payload that returns and it seems to have That said, I did attempt to run the examples and they do not seem to work on Windows (at least on my machine) but that's something I can look into and PR separately :) |
I have an Elgato WaveLink microphone, and the user-space software for that exposes a JSON-RPC interface to control the microphone. Using the following code, I can connect and attempt to issue a command against the software. The handler I directly register on the socket will log the message coming back just fine, but the
await
ed call never resolves. Any idea what could be causing this?The text was updated successfully, but these errors were encountered: