NOTE - UPDATED VIDEO: The Oobabooga API has changed, so this video will not work on the latest version. If using this video, you will need to use an older version of Oobabooga. Here is the updated video: th-cam.com/video/Jg0vqEnr8n8/w-d-xo.html Anyone who would like more details on installing Oobabooga, Aitrepreneur has that base covered: th-cam.com/video/lb_lC4XFedU/w-d-xo.html
Hey there, I'm currently doing the same thing... albeit a simpler version, but I'm also getting the websockets.exceptions.ConnectionClosedError: no close frame received or sent Have you found any solutions to this problem?
Afraid not, but I honestly haven't tried terribly hard since making this. Like I mentioned in the video, I think it's ok as long as you do close the socket in the end. We could try an issue in Oobabooga and see if they know, but it's hard to say that it's on that end when it works fine with other solutions. That's why I was suspicious of it having something to do with how Python vs. C# implement it, and that would require quite a deep dive :-P. What I can mention is that depending on what order I did things in, which method used, etc... I did have it at one point where it would throw an exception, still red text and everything, but it would actually show (OK) 1000, etc... to the closed packet received & sent....but it was still throwing the exception. However, in those cases, it would actually stay open and repeat the prompt & keep generating output on the Oobabooga end, and that's not a sustainable solution either, of course. I'm not a network engineer, but I assume that the closed packet, or byte if that's what it is, is not the entire handshake process. In the code I have, I literally debug the status and see "Close Sent," while Oobabooga is there at the same time complaining it hasn't received it. There is another (NuGet) library or two that you can use for websockets in C#, so I might try that at some point. However, this one was the first one I was able to figure out the asynchronous piece and that while loop section. Of course, one could likely just use the simpler way and get the entire thing back in 1 shot, but that kinda sucks because there would be a long pause.
I've updated my pinned comment. The API has changed and when I connected to it in the newer video, this is not an issue since we don't even need websockets. Check that out and that error will be history 😀
NOTE - UPDATED VIDEO: The Oobabooga API has changed, so this video will not work on the latest version. If using this video, you will need to use an older version of Oobabooga.
Here is the updated video: th-cam.com/video/Jg0vqEnr8n8/w-d-xo.html
Anyone who would like more details on installing Oobabooga, Aitrepreneur has that base covered:
th-cam.com/video/lb_lC4XFedU/w-d-xo.html
Hey there, I'm currently doing the same thing... albeit a simpler version, but I'm also getting the websockets.exceptions.ConnectionClosedError: no close frame received or sent
Have you found any solutions to this problem?
Afraid not, but I honestly haven't tried terribly hard since making this. Like I mentioned in the video, I think it's ok as long as you do close the socket in the end. We could try an issue in Oobabooga and see if they know, but it's hard to say that it's on that end when it works fine with other solutions. That's why I was suspicious of it having something to do with how Python vs. C# implement it, and that would require quite a deep dive :-P.
What I can mention is that depending on what order I did things in, which method used, etc... I did have it at one point where it would throw an exception, still red text and everything, but it would actually show (OK) 1000, etc... to the closed packet received & sent....but it was still throwing the exception. However, in those cases, it would actually stay open and repeat the prompt & keep generating output on the Oobabooga end, and that's not a sustainable solution either, of course.
I'm not a network engineer, but I assume that the closed packet, or byte if that's what it is, is not the entire handshake process. In the code I have, I literally debug the status and see "Close Sent," while Oobabooga is there at the same time complaining it hasn't received it.
There is another (NuGet) library or two that you can use for websockets in C#, so I might try that at some point. However, this one was the first one I was able to figure out the asynchronous piece and that while loop section.
Of course, one could likely just use the simpler way and get the entire thing back in 1 shot, but that kinda sucks because there would be a long pause.
I've updated my pinned comment. The API has changed and when I connected to it in the newer video, this is not an issue since we don't even need websockets. Check that out and that error will be history 😀