dwl 0.7 branch

On Fri Dec 13, 2024 at 9:50 AM CST, ~sewn wrote:

View an image within senpai (sixel, foot) and resize the terminal using the mouse.

I can't repro using

foot version: 1.18.0-2-g62b0b65d4712 (Aug 02 2024, branch 'master') -pgo +ime +graphemes -assertions

What version, and DE/WM are you using?

-- Tim

View an image within senpai (sixel, foot) and resize the terminal using the mouse.

When senpai is ran, senpai will automatically navigate to the last seen channel by the user, but the first member of the channel will appear 'highlighted'. This is due to the fact that senpai doesn't clear the default attributes of the 'Help' menu in (home), in which, the first menu entry, 'Add a network', is automatically selected, which in senpai, becomes highlighted to signify selection.

panic: runtime error: slibounds out of range [59008:59007]

goroutine 166 [running]:
bytes.(*Buffer).Write(0xc001802450?, {0xc001d7b976?, 0x4?, 0x4
	bytes/buffer.go:181 +0xc5
github.com/mattn/go-sixel(*Encoder).Encode(0xc0003caf68, {0x8
70, 0xc000938000})
	github.com/mattn/go-sixel@v0.0.5/sixel.go:157 +0x1182
git.sr.ht/~rockorager/vaxis.(*Sixel).Resize.func1()
	git.sr.ht/~rockorager/vaxis@v0.10.3/image.go:268 +0x21

if that's the case, then I guess this issue can be closed as a 'will not fix' (not sure how sr.ht issues work). The other bugs mentioned here are either beyond the scope of soju or need proper reenactment .

With two networks sharing the same address, one with an explicit name and one without, I'd expect BouncerServ commands such as network delete <addr> to resolve to the network with no name, but instead resolves to the one with a name. It should prefer the name, and fallback to address, unclarified in the soju man page.

The errors (context deadline exceeded) only started appearing after the duplicate(?) network creations.

There also seems to be some soju bugs such as

2024/11/22 12:55:23 user "sewn": downstream "127.0.0.1:34714": failed to handle new registered connection: FAIL BOUNCER INVALID_NETID 3 :Unknown network ID

which i am not sure if it is a result from this issue.

Creating new networks, with the same addresses but different names, can cause problems with BouncerServ internals, such as network delete ircs://irc.libera.chat still being valid.

Other issues arise with a bouncer service i was using where error: context deadline exceeded started appearing when using network delete on the problematic network.

A workaround to this is to manually send SIGHUP signal to kanshi.