#chatnplay Bot Logged User list

Network: ChatNPlay
Modes: +lnVTrt
Last Seen: an hour ago
Topic: Welcome to ChatNPlay! - https://chatnplay.org/ - Discord: https://discord.gg/Akg5bv2GW4 - IRC Support & Help: /join #Help - Register for automatic voice
#1
Rank
14
Users

Channel Log Archive for #chatnplay

Prev
Next

* All times are UTC
Filtering by user: Sirius
Friday, December 1, 2023
[00:42:27] Sirius Me too
[00:42:49] Sirius I'll probably have to gradually add more debug statements to get closer to the issue
[01:52:42] Sirius lol
[06:49:00] Sirius Brandon what bug and semicolon do you mean?
[06:56:44] Sirius I think he means the example conf files, but I'm looking over them now and don't see any syntax errors. Unless I'm missing something
[15:37:12] Sirius Did you identify?
[15:37:35] Sirius What do Anope logs say?
[15:41:33] Sirius Try /cs voice #chatnplay
[15:41:43] Sirius What does ChanServ say?
[15:42:07] Sirius That's a weird error
[15:42:39] Sirius Does ChanServ say anything when you try /cs voice #chatnplay?
[15:43:43] Sirius Does it send a notice when you do that command?
[15:44:04] Sirius Or /cs op #chatnplay in your case since you already have voice
[15:44:57] Sirius Can you give me temp voice access so I can try? It's weird that ChanServ doesn't say anything in notice
[15:45:27] Sirius !voice
[15:45:30] Sirius Yeah
[15:46:21] Sirius We are also on the same server
[15:48:19] Sirius Anything else a few lines surrounding the earlier Anope logs when the error occurred?
[15:52:33] Sirius Maybe related to TLS, too early to tell
[16:20:40] Sirius About this issue, do you remember what happened prior to this? 16:45 <+KnownSyntax> where it was sending things to him, that were meant for me. But that was fixed with a rejoin of the channel
[16:20:57] Sirius Because I can't wrap my head around how that could happen
[16:25:04] Sirius Possible UID re-use could be a cause, I will add UID related debug logs later to see where it goes wrong
[16:36:55] Sirius A possibility is that Anope thought your UID was assigned to another user, but that begs the question how that would even happen. Because on server syncs, all correct UIDs are sent to all servers
[17:13:03] Sirius I genuinly have no idea how to start debugging this. I'm trying to place some logging statements related to UIDs, but wherever I look everything looks fine
[17:15:41] Sirius UIDs are generally used to sync data across the network, so it will not change during the entire session. So you could just change nickname or other attributes, but the UID will still be the same
[17:20:59] Sirius I pushed some that will log events related to UIDs, hopefully it will get us closer to the issue
[17:21:06] Sirius some changes*
[17:26:36] Sirius It's true that the IRCd tries to get the first available UID for a new user, but it should never assign a UID that's in use https://github.com/Y4kuzi/provisionircd-dev/blob/d4ea8699bc8e12e1a6f17f946b6bbd6311d98d6c/handle/core.py#L1944
[19:47:35] Sirius I'm tackling another issue now related to oper-host and vHost from Anope
[19:47:52] Sirius I currently have no idea how to fix that xD
[19:47:55] Sirius Even a drink doesn't help
[19:54:59] Sirius I tried to explain it clearly but it's pretty confusing, even to me still xD
[19:56:28] Sirius lmao
[19:56:45] Sirius ./chghost Aaron testing.rat
[19:57:32] Sirius Btw I forgot to add that this issue only happens upon client connect, with oper-host and vHost getting mixed up @ initial sync
[22:57:47] Sirius Last pushes have some (ground?)breaking additions. Aimed to debug the double user sync and
[22:58:05] Sirius wait, no "and"
Prev
Next