DuckCorp Projects: Issueshttps://projects.duckcorp.org/https://projects.duckcorp.org/favicon.ico?16699090422024-02-04T14:36:07ZDuckCorp Projects
Redmine Bip - Enhancement #807 (New): Add IRCv3 capabilitieshttps://projects.duckcorp.org/issues/8072024-02-04T14:36:07ZLoïc Gomez
<p><a class="external" href="https://ircv3.net/specs/extensions/capability-negotiation.html">https://ircv3.net/specs/extensions/capability-negotiation.html</a></p> Bip - Bug #805 (New): bipmkpw fails compilation (sometimes only?)https://projects.duckcorp.org/issues/8052024-02-04T14:33:13ZLoïc Gomez
<p>While fixing bip/adding code, I've stumbled upon these but not all the time:<br /><pre>
/usr/bin/ld: libbip.a(libbip_a-bip.o):/home/loic/code/bip/src/bip.c:60: multiple definition of `conf_log_system'; bipmkpw-bipmkpw.o:/home/loic/code/bip/src/bipmkpw.c:28: first defined here
/usr/bin/ld: libbip.a(libbip_a-bip.o):/home/loic/code/bip/src/bip.c:43: multiple definition of `conf_log_level'; bipmkpw-bipmkpw.o:/home/loic/code/bip/src/bipmkpw.c:26: first defined here
/usr/bin/ld: libbip.a(libbip_a-bip.o):/home/loic/code/bip/src/bip.c:64: multiple definition of `conf_global_log_file'; bipmkpw-bipmkpw.o:/home/loic/code/bip/src/bipmkpw.c:27: first defined here
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:485: bipmkpw] Error 1
</pre></p> Bip - Bug #803 (New): /bip list connections/all_connections/all_links crashes biphttps://projects.duckcorp.org/issues/8032024-02-04T14:29:06ZLoïc Gomez
<p>In 9.4, listing connections, links crashes bip when there is a long line for on_connect_send option.<br />A fix is available.</p> Bip - Enhancement #801 (New): Update base64 codehttps://projects.duckcorp.org/issues/8012024-02-04T07:32:50ZLoïc Gomez
<p>We need to update the base64 code (and copyright)</p> Bip - Bug #793 (New): AC_PROG_LEX without either yywrap or noyywrap is obsoletehttps://projects.duckcorp.org/issues/7932024-02-02T16:48:56ZLoïc Gomez
<pre>
configure.ac:16: warning: AC_PROG_LEX without either yywrap or noyywrap is obsolete
./lib/autoconf/programs.m4:716: _AC_PROG_LEX is expanded from...
./lib/autoconf/programs.m4:709: AC_PROG_LEX is expanded from...
aclocal.m4:1072: AM_PROG_LEX is expanded from...
configure.ac:16: the top level
</pre> Bip - Bug #792 (New): Handle CAP request/reply on client connectionshttps://projects.duckcorp.org/issues/7922024-02-02T16:43:52ZLoïc Gomez
<p>Some clients will expect BIP to send a CAP reply on client connect.<br />For example, Goguma on Android will send something like this:<br /><pre>
02-02-2024 17:45:21 DEBUG: "CAP LS 302"
02-02-2024 17:45:21 DEBUG: "NICK kyoshiro"
02-02-2024 17:45:21 DEBUG: "USER kyoshiro 0 * kyoshiro"
02-02-2024 17:45:21 DEBUG: "CAP REQ sasl"
02-02-2024 17:45:21 DEBUG: "AUTHENTICATE PLAIN"
02-02-2024 17:45:21 DEBUG: "AUTHENTICATE REDACTED_B64"
02-02-2024 17:45:21 DEBUG: "CAP END"
</pre></p> Bip - Bug #763 (New): Backlog is being lost on unstable connectionshttps://projects.duckcorp.org/issues/7632022-03-16T19:03:53ZLoïc Gomez
<p><a class="external" href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595408">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595408</a></p>
<p>Per Arnaud's comment there:</p>
<blockquote>
<p>Tcp will detect such connection breakage only when bip sends data to<br />your ADSL ip and times out waiting for ACKs. So bip indeed<br />approximates when the connection is lost. The blreset_on_talk should<br />be useful to you as bip will replay logs as long as you did not reply<br />anything.</p>
<p>I don't see any trivial way to implement a better connection loss<br />detection for backlog reset. It should be feasible to delay backlog<br />resetting to only when we receive any data from client, which would<br />prevent some errors of the type you described (but not all).<br />Another way would be to poll the tcp buffer size and to reset logs<br />only when it's down to 0. It's probably the best solution.</p>
</blockquote> Bip - Bug #762 (New): Systemctl integration does not actually stop biphttps://projects.duckcorp.org/issues/7622022-03-16T18:55:17ZLoïc Gomez
<p><a class="external" href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963907">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963907</a></p>
<p>Checked up on this but could not reproduce on Ubuntu/hirsute with a fresh start. Although, on Debian stable, it indeed shows up as dead even though restart had occurred less than 2d ago, and I remember having such issue stopping bip:<br /><pre><code>
● bip.service - Bip IRC Proxy
Loaded: loaded (/lib/systemd/system/bip.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/bip.service.d
└─custom.conf, override.conf
Active: inactive (dead) since Thu 2022-03-10 21:29:43 CET; 5 days ago
Main PID: 5508 (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 4668)
Memory: 11.4M
CPU: 1d 4h 57min 33.009s
CGroup: /system.slice/bip.service
└─5509 /usr/bin/bip -f /etc/bip/bip.conf -s /var/lib/bip
Warning: journal has been rotated since unit was started, output may be incomplete.
</code></pre></p>
<p>Couldn't find any difference in systemctl unit</p> Bip - Bug #749 (New): bip doesn't create ~/.bip/ directory when using default PID filehttps://projects.duckcorp.org/issues/7492022-01-03T11:29:06ZLoïc Gomez
<p>30-12-2021 14:34:11 Default pid file: /home/kyoshiro/.bip/bip.pid<br />30-12-2021 14:34:11 FATAL: Cannot write to PID file (/home/kyoshiro/.bip/bip.pid.redacted.3764810) No such file or directory</p> Bip - Enhancement #733 (New): Error message is unclear when SSL server is unresponsivehttps://projects.duckcorp.org/issues/7332021-09-16T13:55:42ZLoïc Gomez
<p>It seems we get these when bip is unable to connect at all to a server using SSL:</p>
<blockquote>
<p>WARNING: mySSL_get_cert() SSL server supplied no certificate !<br />ERROR: No certificate in SSL write_socket</p>
</blockquote>
<p>We need to find a way to make it clear there is a connect() issue and not an SSL related problem.</p> Bip - Enhancement #730 (New): Update /bip backlog [n] to make it backlog private messages toohttps://projects.duckcorp.org/issues/7302021-09-03T12:36:27ZLoïc Gomez
<p>Current /bip backlog command does not backlog private messages.<br />I think it is related to bip not being aware of which private messages to look for, as they're scattered in multiple files.</p>
<p>Maybe it does work with an in-memory backlog setup though (to be tested).</p>
<p>We could probably list changed files in the logdir and backlog the ones matching the [n] parameter.</p> Bip - Enhancement #715 (New): Backlog one channel onlyhttps://projects.duckcorp.org/issues/7152020-12-17T09:34:26ZPierre-Louis Bonicolipierre-louis.bonicoli@ir5.eu
<p>The backlog command only allows to backlog all the channels from one network.</p>
<p>It would be nice to fetch backlog from one channel only.</p>
<p>From: Debian bug <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668420" class="external">#668420</a>.</p> Bip - Bug #641 (New): /who replies aren't routed to correct clienthttps://projects.duckcorp.org/issues/6412018-12-30T12:02:40ZJohn Levon
<p>Using bip on freenode, with two hexchat clients, I get regular noise to the channels<br />corresponding to the output of a /who command. This seems to be from hexchat's /away<br />tracking, which periodically sends this command. It appears that bip doesn't know which<br />client to route the response to, so you get this noise.</p>
<p>In znc, it seems this is fixed by enabling route_replies, but I can't find such a thing<br />in bip.</p> mkcert - Bug #597 (New): Please review Ansible Vault supporthttps://projects.duckcorp.org/issues/5972017-09-24T06:21:13ZMarc Dequènesduck@duckcorp.org
<p>It has been made as less intrusive as possible to avoid introducing bugs. Most probably a rework of the path variables would be better but this is not the goal of this PR,</p> mkcert - Review #579 (New): Please review error handling fixeshttps://projects.duckcorp.org/issues/5792017-07-24T10:51:36ZMarc Dequènesduck@duckcorp.org