| 2 Feb 2024 |
 GitHub | [mautrix/meta] af913337456 opened
issue
#8: Can not receive new message from Meta-Messenger
Can not receive new message from Meta-Messenger.
- Login facebook, open the messenger web page in facebook;
- Copy the cookies and login this application;
- Watching the log output.
when new message comming in messenger, the app can't receive it.
bug
| 06:38:58 |
| GitHub | [mautrix/meta] af913337456 commented on
issue
#8: Can not receive new message from Meta-Messenger:
@tulir Hi, please help me.
| 06:40:05 |
| GitHub | [mautrix/meta] af913337456 edited
issue
#8: Can not receive new message from Meta-Messenger
| 06:41:05 |
 Nico | Further investigation, it's here https://github.com/mautrix/meta/blob/ee8c84d0d7a36cf8fcb5916889d99c569764bbe9/messagix/threads.go#L30 that drops the messages | 16:16:41 |
| Nico | i.e. my messages have no Topics set, but still arrives | 16:17:00 |
 tulir | no, the message just doesn't arrive | 16:19:46 |
| tulir | the library is badly written (not by me) and returns an empty object on timeout | 16:19:56 |
| GitHub | [mautrix/meta] NicolasDerumigny edited
issue
#5: Messages are not transferred from Matrix to meta
| 16:20:41 |
| tulir | that's also whst the commit you found earlier added a todo for | 16:20:52 |
| tulir | previously it would treat the empty timeout object as a success and wonder why it's empty | 16:21:25 |
| Nico | In reply to @tulir:maunium.net
no, the message just doesn't arrive It does, I receive it 🙂 | 16:21:30 |
| Nico | It is bridged from meta -> matrix | 16:21:56 |
| tulir | I meant responses to requests by the bridge, that's what that code handles | 16:23:03 |
| Nico | Oh well, maybe not? I will test further then. Because there were several issues then
- on latest versions, nothing happens after bridging, except if I remove the else condition
| 16:23:44 |
| Nico | With it removed, I can at least bridge meta -> matrix (which is not the cas with) | 16:23:48 |
| Nico | I assume this is because the empty message time outs and then prevent the rest of the events to be triggered? | 16:24:21 |
| tulir | there's a request it makes on startup that fails now that timeouts aren't ignored | 16:24:56 |
| tulir | that failing makes it disconnect, but requests never worked | 16:25:11 |
| Nico | Makes sense then. Still, it is really strange that the request timeouts but receiving messages still works. I will look at it when I have time, but not now. Thanks for the explanation! | 16:27:28 |
| tulir | oh yeah, both responses and new messages are sent as /ls_resp 🤔
| 16:54:14 |
| tulir | it could be something wrong with the mqtt implementation, for some reason the library also implements mqtt itself | 16:54:40 |
| Nico | It may be, as former python bridges worked fine | 18:41:52 |
| 3 Feb 2024 |
|  Gabriel R. joined the room. | 05:48:27 |
|  G joined the room. | 05:52:13 |
| GitHub | [mautrix/meta] marcodiversi starred the repo | 07:16:29 |
| GitHub | [mautrix/meta] kapsikkum starred the repo | 07:47:46 |
|  rootz159 joined the room. | 22:08:37 |
| 4 Feb 2024 |
|  hdaop joined the room. | 02:45:11 |
| GitHub | [mautrix/meta] af913337456 commented on
issue
#8: Can not receive new message from Meta-Messenger:
@tulir any suggestions？
| 15:55:34 |
| GitHub | [mautrix/meta] tulir commented on
issue
#8: Can not receive new message from Meta-Messenger:
That user_id field in the logs is suspicious, did you modify the bridge somehow?
| 16:35:31 |
