Login in is broken with glib2 >2.68 about bitlbee-discord

[sm00th]

Please try 607f988 with glib2.70.

[sm00th]

Interesting. Since you have the environment set up, could you please try running (with debug enabled) a build with eb768b4 included with both glib versions and see if there are any differences in requests bitlbee-discord sends?

[Thaodan]

I can. Just as a note: I build the bitllbee- discord package I currently use with glib2 2.70 installed, downgrading to 2.68 before or aftter building doesn't seem to make a difference.

[sm00th]

Yeah, makes sense. No need to rebuild it the second time, just make sure that commit is included and then you can switch glib versions without a rebuild.

[Thaodan]

2.68: `[17:29:33] >>> ((null)) discord_ws_connected_cb 254` 2.70: `[17:40:21] >>> ((null)) discord_ws_connected_cb 235`

[sm00th]

After these lines there should be a request body starting with "GET blabla HTTP/1.1", thats the important part

[Thaodan]

2.68: [17:41:46] >>> ((null)) discord_ws_connected_cb 254 GET /?encoding=json&v=6 HTTP/1.1 Host: gateway.discord.gg Connection: keep-alive, Upgrade Upgrade: websocket Origin: discordapp.com Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Version: 13 Sec-WebSocket-Key: foobar 2.70: [17:41:07] >>> ((null)) discord_ws_connected_cb 235 GET HTTP/1.1 Host: gateway.discord.gg Connection: keep-alive, Upgrade Upgrade: websocket Origin: discordapp.com Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Version: 13 Sec-WebSocket-Key: foobar

[sm00th]

Apparently starting with glib 2.69 g_match_info_fetch() now returns an empty string instead of NULL on failed match. https://gitlab.gnome.org/GNOME/glib/-/issues/229

This throws discord_http_gateway_cb() off.

[Wibjarm]

Just saw this and tested, that commit fixes it on 2.70 for me.

[drshapeless]

Just tested, it works flawlessly with glib 2.70 on Arch.

[sm00th]

Thanks for the feedback. Going to close this issue now.