Close description can be un-initialized at time

[machinezone]

Close description can be un-initialized at time

[bsergean]

Doing it now ... :)

…

On Apr 18, 2019, at 10:12 AM, Kumamon38 ***@***.***> wrote: Just 2 parameters to add; you can if you want to :) — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC2O6UIIA6G54ZGFRCJ66KLPRCTXNANCNFSM4HGYRNRQ>.

[bsergean]

I'll take a look when I have time but if you have an idea for a fix please go ahead :)

[bsergean]

ps: I should say that I am not positive that it is a regression, but it is still a bug.

[AlexandreK38]

I had a look and created a PR to fix this, but in fact this was nothing to do with the 935e679

• First, when we receive the close code / reason remotely, the reason had 2 characters more than it needed (that why we could see "ac" or "%" or whatever randomnly read from memory)
• Second, when we used the close() method, we sent the code but not the reason, so we can't expect to read it on the other side
• Not directly linked, but we can call the _onCloseCallback(_closeCode, _closeReason, _closeWireSize); with not really initialized value (0, "", 0) in the case we call setReadyState(CLOSED) outside the close() method

All of this should be fixed in PR #34

[AlexandreK38]

So is the issue fixed as you wanted with last PR?

[bsergean]

make ws_test seems to behave now !

[bsergean]

I think that the next step here is to add the ability to specify a reason and a code when calling websocket.close, but that might be very easy.

[AlexandreK38]

Just 2 parameters to add; you can if you want to :)