Event types are wrongly reported #3

New Issue

CJ_Clippy · 2023-09-06T00:08:32Z

CJ_Clippy commented

2023-09-06 00:08:32 +00:00

0|scout daemon  | debug: [ ] room is passworded {"service":"futureporn/scout","timestamp":"2023-09-05T23:59:57.383Z"}
0|scout daemon  | debug: [STREAM STATUS] {"name":"room:grouped:G0TWFS5:12","id":"ZXp64Ptvuk:0:0","encoding":null,"data":{"tid":"16939584622:46627","ts":1693958462.2441168,"_topic":"RoomMessageTopic","message":"Offline CB tip shenanigans to test the toy can work and escape.","font_family":"default","font_color":"","id":"RK68G6C0NL2ZC5","background":"","from_user":{"username":"sonic_slades","gender":"m","is_broadcaster":false,"in_fanclub":false,"is_following":true,"is_mod":false,"has_tokens":true,"tipped_recently":false,"tipped_alot_recently":false,"tipped_tons_recently":false},"method":"lazy","pub_ts":1693958462.2594786}} {"service":"futureporn/scout","timestamp":"2023-09-05T23:59:57.474Z"}

This is showing up as a status event when it's actually a message event. What's going wrong here?

Also, the room is NOT passworded, but I'm getting a password event. ???

``` 0|scout daemon | debug: [ ] room is passworded {"service":"futureporn/scout","timestamp":"2023-09-05T23:59:57.383Z"} 0|scout daemon | debug: [STREAM STATUS] {"name":"room:grouped:G0TWFS5:12","id":"ZXp64Ptvuk:0:0","encoding":null,"data":{"tid":"16939584622:46627","ts":1693958462.2441168,"_topic":"RoomMessageTopic","message":"Offline CB tip shenanigans to test the toy can work and escape.","font_family":"default","font_color":"","id":"RK68G6C0NL2ZC5","background":"","from_user":{"username":"sonic_slades","gender":"m","is_broadcaster":false,"in_fanclub":false,"is_following":true,"is_mod":false,"has_tokens":true,"tipped_recently":false,"tipped_alot_recently":false,"tipped_tons_recently":false},"method":"lazy","pub_ts":1693958462.2594786}} {"service":"futureporn/scout","timestamp":"2023-09-05T23:59:57.474Z"} ``` This is showing up as a status event when it's actually a message event. What's going wrong here? Also, the room is NOT passworded, but I'm getting a password event. ???

CJ_Clippy added the

bug

label 2023-09-06 00:08:45 +00:00

CJ_Clippy commented

2023-09-06 19:09:35 +00:00

Looks like this is caused in part by changes in CB's Ably room names.

See the following example.

  'RoomMessageTopic#RoomMessageTopic:9AEMAGV': 'room:grouped:9AEMAGV:9',
  'RoomStatusTopic#RoomStatusTopic:9AEMAGV': 'room:grouped:9AEMAGV:9',

Status and messages events are now grouped, where previously they were in their own channels.

Looks like this is caused in part by changes in CB's Ably room names. See the following example. ``` 'RoomMessageTopic#RoomMessageTopic:9AEMAGV': 'room:grouped:9AEMAGV:9', 'RoomStatusTopic#RoomStatusTopic:9AEMAGV': 'room:grouped:9AEMAGV:9', ``` Status and messages events are now grouped, where previously they were in their own channels.

CJ_Clippy commented

2023-09-06 20:19:16 +00:00

12:08:13.248 Ably: Channel state for channel "room_unsessioned:grouped:9AEMAGV": failed; reason: [ErrorInfo: Channel denied access based on given capability; channelId = room_unsessioned:grouped:9AEMAGV; statusCode=401; code=40160; see https://help.ably.io/error/40160 ]
node:internal/process/promises:288

I'm guessing this is because we are attempting to double subscribe to a grouped channel.

``` 12:08:13.248 Ably: Channel state for channel "room_unsessioned:grouped:9AEMAGV": failed; reason: [ErrorInfo: Channel denied access based on given capability; channelId = room_unsessioned:grouped:9AEMAGV; statusCode=401; code=40160; see https://help.ably.io/error/40160 ] node:internal/process/promises:288 ``` I'm guessing this is because we are attempting to double subscribe to a grouped channel.

CJ_Clippy referenced this issue from a commit

2023-09-06 23:13:14 +00:00

fix https://gitea.futureporn.net/futureporn/futureporn-scout/issues/3

CJ_Clippy closed this issue

2023-09-06 23:13:14 +00:00

Sign in to join this conversation.