| 26 Sep 2024 |
 wirdo12398 | 
Download image.png | 07:30:22 |
| wirdo12398 | It is working now, I just deleted the device (from sessions tab) then re-signed in and verified the new session and everything worked fine.
This is to help others if someone faced the same issue | 08:45:39 |
| 29 Sep 2024 |
 nex (she/it) | Redacted or Malformed Event | 20:58:34 |
| 1 Oct 2024 |
|  Robert Imschweiler changed their profile picture. | 09:09:13 |
| 2 Oct 2024 |
| nex (she/it) | Hey, would anyone be able to help me out with https://github.com/matrix-nio/matrix-nio/issues/525 ? | 12:00:35 |
| nex (she/it) changed their profile picture. | 19:58:05 |
| 22 Oct 2024 |
|  @captain_grossbeard:pancrypticon.net left the room. | 09:22:16 |
| 4 Oct 2024 |
 Paarth Shah - Github Maintainer | Read through; would definitely like to take a look soon when I get a free moment | 07:51:21 |
| Paarth Shah - Github Maintainer changed the room topic to "The nio matrix python library | Latest stable release 0.25.2 | https://pypi.org/project/matrix-nio/ | Documentation: https://matrix-nio.readthedocs.io/en/stable/" from "The nio matrix python library | Latest stable release 0.25.1 | Latest release candidate 0.25.2rc1 | https://pypi.org/project/matrix-nio/ | Documentation: https://matrix-nio.readthedocs.io/en/stable/". | 07:51:50 |
| nex (she/it) | See I was under the assumption that storing the sync token to resume from later would also store the sync data | 11:31:03 |
| nex (she/it) | Because without that, if you start the process again, you don't backfill the state, meaning your data is incomplete | 11:31:23 |
| nex (she/it) | Which leads to, for example, the client not seeing that anyone has power levels | 11:31:36 |
| nex (she/it) | I'm not entirely sure how other clients do this, because there's no way they're storing every single sync given they can be many megabytes | 11:32:10 |
| nex (she/it) | And a full sync is far too expensive at that point too. In my case, a full initial sync takes 5 minutes on my bot now | 11:32:40 |
| 7 Oct 2024 |
 Mooling | 木泠 | I try to run message sender in a sub thread, and when Internet is bad, messages were sent more than once. | 15:12:00 |
| Mooling | 木泠 | 
Download 屏幕截图_20241007_231212.png | 15:12:26 |
| Mooling | 木泠 | Decorator @new_thread is from MCDReforged: https://docs.mcdreforged.com/en/latest/code_references/decorators.html#new-thread | 15:15:54 |
| Mooling | 木泠 | * I try to run message sender in a sub thread, and when Internet is bad, messages would be sent more than once. | 15:21:30 |
| 8 Oct 2024 |
| Mooling | 木泠 | And another question: how do these "Timed out" errors appear?
| 14:18:47 |
| Mooling | 木泠 | 
Download 屏幕截图_20241008_221714.png | 14:18:53 |
 ifiguero | It's a warning from the async client. From the looks is on the send method.
for loggername in ["nio.responses", "nio.client.async_client", "asyncio", "nio.events.misc"]: loggerloop = logging.getLogger(loggername) if debug: loggerloop.setLevel(logging.INFO) else: loggerloop.setLevel(logging.CRITICAL)
To disable it. I increase the logger level so it doesn't show any of it. Critical mostly disable all of them IMHO | 16:33:54 |
| ifiguero | * It's a warning from the async client. From the looks is on the send method.
for loggername in ["nio.responses", "nio.client.async_client", "asyncio", "nio.events.misc"]:
loggerloop = logging.getLogger(loggername)
if debug: loggerloop.setLevel(logging.INFO) else: loggerloop.setLevel(logging.CRITICAL)
To disable it. I increase the logger level so it doesn't show any of it. Critical mostly disable all of them IMHO
| 17:31:58 |
| ifiguero | * It's a warning from the async client. From the looks is on the send method.
for loggername in ["nio.responses", "nio.client.async_client", "nio.events.misc"]:
loggerloop = logging.getLogger(loggername)
if debug:
loggerloop.setLevel(logging.INFO)
else:
loggerloop.setLevel(logging.CRITICAL)
To disable it. I increase the logger level so it doesn't show any of it. Critical mostly disable all of them IMHO
| 17:32:28 |
| nex (she/it) changed their display name from nex (she/it) to public static void main string args. | 23:11:31 |
| 9 Oct 2024 |
| Mooling | 木泠 | In reply to @ifiguero:matrix.org
It's a warning from the async client. From the looks is on the send method.
for loggername in ["nio.responses", "nio.client.async_client", "nio.events.misc"]:
loggerloop = logging.getLogger(loggername)
if debug:
loggerloop.setLevel(logging.INFO)
else:
loggerloop.setLevel(logging.CRITICAL)
To disable it. I increase the logger level so it doesn't show any of it. Critical mostly disable all of them IMHO
If the client does not receive any message for a long time, will this timed out warning be triggered? | 03:51:36 |
| Mooling | 木泠 | Or is there another reason for this timed out warning? | 03:52:07 |
| nex (she/it) | If you set a limit on your sync timeout then yes, not receiving a sync response in x milliseconds will give you that warning
You will also get that warning if you try to perform an operation that either the homeserver takes forever to respond to, or you have a poor network connection and the connection is dropped | 11:06:35 |
| nex (she/it) | That warning means that the previous request will be retried iirc. There's some related config options in [Async]ClientConfig
| 11:07:02 |
| nex (she/it) changed their display name from public static void main string args to #include<stdio.h>. | 11:21:08 |
| 10 Oct 2024 |
| nex (she/it) changed their display name from #include<stdio.h> to using System;. | 05:05:04 |
