irc: setting bot mode (+B) might not work #220

jersey commented 2026年07月06日 04:38:05 +02:00

see #219 (comment)

see https://codeberg.org/jersey/lightning/issues/219#issuecomment-18643889

RandomHuman commented 2026年07月06日 05:02:49 +02:00

i set the config option setBot to true image (had to make it a string, wouldn't boot if it were simply a bool) and it doesn't appear to be setting the mode
image

i set the config option setBot to true  (had to make it a string, wouldn't boot if it were simply a bool) and it doesn't appear to be setting the mode 

jersey commented 2026年07月06日 05:41:03 +02:00

what do your logs say?

what do your logs say?

RandomHuman commented 2026年07月06日 05:47:32 +02:00

@jersey wrote in #220 (comment):

what do your logs say?

image
nothing much really

@jersey wrote in https://codeberg.org/jersey/lightning/issues/220#issuecomment-18647288: > what do your logs say?  nothing much really

RandomHuman commented 2026年07月06日 05:50:25 +02:00

image
this is what it says when i set the config option as a bool rather than as a string

 this is what it says when i set the config option as a bool rather than as a string

user0-07161 commented 2026年07月06日 14:15:54 +02:00

@RandomHuman the option is called set_bot, not setBot

bot,_:=strconv.ParseBool(cfg["set_bot"])

@RandomHuman the option is called `set_bot`, not `setBot` ```go bot, _ := strconv.ParseBool(cfg["set_bot"]) ```

RandomHuman commented 2026年07月06日 19:10:22 +02:00

@user0-07161 wrote in #220 (comment):

@RandomHuman the option is called set_bot, not setBot

bot,_:=strconv.ParseBool(cfg["set_bot"])

that would probably be me reading client.go rather than the little comment bit for what the config options are, testing this now

@user0-07161 wrote in https://codeberg.org/jersey/lightning/issues/220#issuecomment-18667073: > @RandomHuman the option is called `set_bot`, not `setBot` > > ```go > bot, _ := strconv.ParseBool(cfg["set_bot"]) > ``` that would probably be me reading client.go rather than the little comment bit for what the config options are, testing this now

RandomHuman commented 2026年07月06日 19:15:06 +02:00

same behaviour as when i was using the wrong config option

same behaviour as when i was using the wrong config option

jersey commented 2026年07月06日 21:07:08 +02:00

it appears to work for me locally with the following config (using a local instance of ergo as an IRCd):

[[plugins]]
type = "irc"
name = "ergo"
config.server = "ergo.localhost:6667"
config.tls = "false"
config.set_bot = "true"
config.nick = "lightning"
config.timeout = "2"

here're logs from lightning

☁ ~/Documents/lightning (mautrix-fork) go run ./cmd/lightning/
14:58:19 main.go:48: bridge: bot started
14:58:19 plugin.go:58: irc: connecting to ergo.localhost:6667
14:58:19 plugin.go:64: irc: connected to ergo.localhost:6667
14:58:19 client.go:216: irc: ready, welcome message: "Welcome to the ErgoTest IRC Network lightning"

and ergo

2026年07月06日T18:57:56.988Z : info : server : ergo-2.19.0-unreleased starting
2026年07月06日T18:57:56.988Z : warn : server : You are currently running an unreleased beta version of Ergo that may be unstable and could corrupt your database.
If you are running a production network, please download the latest build from https://ergo.chat/about and run that instead.
2026年07月06日T18:57:56.988Z : info : server : Using config file : ircd.yaml
2026年07月06日T18:57:56.988Z : info : server : Using datastore : ircd.db
2026年07月06日T18:57:56.988Z : info : server : Proxied IPs will be accepted from : localhost
2026年07月06日T18:57:56.988Z : info : listeners : now listening on 127.0.0.1:6667, tls=false, proxy=false, tor=false, websocket=false.
2026年07月06日T18:57:56.988Z : info : listeners : now listening on [::1]:6667, tls=false, proxy=false, tor=false, websocket=false.
2026年07月06日T18:57:56.988Z : info : listeners : now listening on :6697, tls=true, proxy=false, tor=false, websocket=false.
2026年07月06日T18:57:56.988Z : info : server : Server running
2026年07月06日T18:57:56.988Z : info : connect-ip : s00001 : Client connecting: real IP 127.0.0.1, proxied IP <nil>
2026年07月06日T18:57:56.988Z : info : connect : s00001 : Client connected [lightning] [u:~u] [r:lightning]
2026年07月06日T18:58:11.268Z : info : connect-ip : s00002 : Client connecting: real IP ::1, proxied IP <nil>
2026年07月06日T18:58:11.370Z : info : connect : s00002 : Client connected [jersey] [u:~u] [r:jersey]
2026年07月06日T18:58:12.875Z : info : opers : jersey : opered up as : admin
2026年07月06日T18:58:18.472Z : info : connect-ip : s00001 : Disconnecting session of lightning from 127.0.0.1
2026年07月06日T18:58:18.472Z : info : quit : lightning is no longer on the server
2026年07月06日T18:58:19.222Z : info : connect-ip : s00003 : Client connecting: real IP ::1, proxied IP <nil>
2026年07月06日T18:58:19.222Z : info : connect : s00003 : Client connected [lightning] [u:~u] [r:lightning]

the user list in halloy seems to show it working, and whois does as well

image

image

could you try the latest commit on develop again?

it appears to work for me locally with the following config (using a local instance of ergo as an IRCd): ```toml [[plugins]] type = "irc" name = "ergo" config.server = "ergo.localhost:6667" config.tls = "false" config.set_bot = "true" config.nick = "lightning" config.timeout = "2" ``` here're logs from lightning ``` ☁ ~/Documents/lightning (mautrix-fork) go run ./cmd/lightning/ 14:58:19 main.go:48: bridge: bot started 14:58:19 plugin.go:58: irc: connecting to ergo.localhost:6667 14:58:19 plugin.go:64: irc: connected to ergo.localhost:6667 14:58:19 client.go:216: irc: ready, welcome message: "Welcome to the ErgoTest IRC Network lightning" ``` and ergo ``` 2026年07月06日T18:57:56.988Z : info : server : ergo-2.19.0-unreleased starting 2026年07月06日T18:57:56.988Z : warn : server : You are currently running an unreleased beta version of Ergo that may be unstable and could corrupt your database. If you are running a production network, please download the latest build from https://ergo.chat/about and run that instead. 2026年07月06日T18:57:56.988Z : info : server : Using config file : ircd.yaml 2026年07月06日T18:57:56.988Z : info : server : Using datastore : ircd.db 2026年07月06日T18:57:56.988Z : info : server : Proxied IPs will be accepted from : localhost 2026年07月06日T18:57:56.988Z : info : listeners : now listening on 127.0.0.1:6667, tls=false, proxy=false, tor=false, websocket=false. 2026年07月06日T18:57:56.988Z : info : listeners : now listening on [::1]:6667, tls=false, proxy=false, tor=false, websocket=false. 2026年07月06日T18:57:56.988Z : info : listeners : now listening on :6697, tls=true, proxy=false, tor=false, websocket=false. 2026年07月06日T18:57:56.988Z : info : server : Server running 2026年07月06日T18:57:56.988Z : info : connect-ip : s00001 : Client connecting: real IP 127.0.0.1, proxied IP <nil> 2026年07月06日T18:57:56.988Z : info : connect : s00001 : Client connected [lightning] [u:~u] [r:lightning] 2026年07月06日T18:58:11.268Z : info : connect-ip : s00002 : Client connecting: real IP ::1, proxied IP <nil> 2026年07月06日T18:58:11.370Z : info : connect : s00002 : Client connected [jersey] [u:~u] [r:jersey] 2026年07月06日T18:58:12.875Z : info : opers : jersey : opered up as : admin 2026年07月06日T18:58:18.472Z : info : connect-ip : s00001 : Disconnecting session of lightning from 127.0.0.1 2026年07月06日T18:58:18.472Z : info : quit : lightning is no longer on the server 2026年07月06日T18:58:19.222Z : info : connect-ip : s00003 : Client connecting: real IP ::1, proxied IP <nil> 2026年07月06日T18:58:19.222Z : info : connect : s00003 : Client connected [lightning] [u:~u] [r:lightning] ``` the user list in halloy seems to show it working, and whois does as well   could you try the latest commit on develop again?

RandomHuman commented 2026年07月07日 00:00:00 +02:00

still isn't working for me, using the latest commit built into a docker container with
docker buildx build . -f etc/containerfile --platform linux/amd64 --build-arg VERSION=custom --build-arg SOURCE_DATE_STR="$(date -u '+%Y-%m-%d %H:%M:%S')" -t custom-lightning --load

lightning config for IRC:
image

lightning logs
image

ergo logs
image

whois output
image

still isn't working for me, using the latest commit built into a docker container with `docker buildx build . -f etc/containerfile --platform linux/amd64 --build-arg VERSION=custom --build-arg SOURCE_DATE_STR="$(date -u '+%Y-%m-%d %H:%M:%S')" -t custom-lightning --load` lightning config for IRC:  lightning logs  ergo logs  whois output 

jersey commented 2026年07月08日 00:16:36 +02:00

@RandomHuman i'm not entirely sure why this would happen. can you try and add more logging to the IRC client in listen() to see what ergo is returning?

@RandomHuman i'm not entirely sure why this would happen. can you try and add more logging to the IRC client in [`listen()`](https://codeberg.org/jersey/lightning/src/commit/9cca7e5652b195f6e9aef14f571eaf5f9bf2b5e0/pkg/platforms/irc/client.go#L168) to see what ergo is returning?

RandomHuman commented 2026年07月08日 05:25:30 +02:00

@jersey wrote in #220 (comment):

@RandomHuman i'm not entirely sure why this would happen. can you try and add more logging to the IRC client in listen() to see what ergo is returning?

apologies, but i don't actually know how to do that, i am entirely unexperienced in Go (have literally never touched it), so i don't even know where i'd be starting for that

@jersey wrote in https://codeberg.org/jersey/lightning/issues/220#issuecomment-18767348: > @RandomHuman i'm not entirely sure why this would happen. can you try and add more logging to the IRC client in [`listen()`](https://codeberg.org/jersey/lightning/src/commit/9cca7e5652b195f6e9aef14f571eaf5f9bf2b5e0/pkg/platforms/irc/client.go#L168) to see what ergo is returning? apologies, but i don't actually know how to do that, i am entirely unexperienced in Go (have literally never touched it), so i don't even know where i'd be starting for that

RandomHuman commented 2026年07月08日 06:04:18 +02:00

i can turn on the debug logging in Ergo though

logs everything it sends to and gets from clients, might help

i *can* turn on the debug logging in Ergo though logs everything it sends to and gets from clients, might help

RandomHuman commented 2026年07月08日 06:15:33 +02:00

@RandomHuman wrote in #220 (comment):

i can turn on the debug logging in Ergo though

logs everything it sends to and gets from clients, might help

well, according to my Ergo logs, lightning isn't even trying to assign itself the +B mode

after setting the +i mode and getting the debug message, lightning and the server seem to simply not communicate further (this is without the bot actively in a channel)

if you want a photo of the logs i'll DM it, not attaching it here because of the sheer amount of stuff that gets logged while the debugging mode is on

@RandomHuman wrote in https://codeberg.org/jersey/lightning/issues/220#issuecomment-18775328: > i _can_ turn on the debug logging in Ergo though > > logs everything it sends to and gets from clients, might help well, according to my Ergo logs, lightning isn't even trying to assign itself the +B mode after setting the +i mode and getting the debug message, lightning and the server seem to simply not communicate further (this is without the bot actively in a channel) if you want a photo of the logs i'll DM it, not attaching it here because of the sheer amount of stuff that gets logged while the debugging mode is on

jersey commented 2026年07月08日 14:02:33 +02:00

could you DM those logs? i'd be interested to see that

could you DM those logs? i'd be interested to see that

jersey commented 2026年07月14日 20:18:32 +02:00

@RandomHuman could you try cdf614fae2 and seeing what logs there might relate to bot mode there?

@RandomHuman could you try cdf614fae29f0a4f5c5d2a4be55895e57caad9d1 and seeing what logs there might relate to bot mode there?