Oh man, I forgot the rush of endorphins that comes from fixing a really longstanding bug.
#FedBOX, the generic #ActivityPub service, had a heisenbug for about 6 months where integration tests for federated dispatch would randomly (and rarely when debugging) failed. I tried a couple of times to reproduce it, but it wasn't that big of a deal and it mostly went fine, so I didn't want to dedicate too much time to it.
1/2
@mariusor Marius: wanted to put this into your field of view…a number of us working on an ActivityPub test suite… would love your perspective on what would be useful there. The Frendica group can be followed here @activitypubtestsuite
Right now, early days, it is through that mastodon-compatible group above. 👆 …. Follow it and any messages mentioning it reflect to you and over 110 developers on it.
First goal: resuscitation of OLD test.ActivityPub.rocks suite… second goal, rebuild one in sustainable code, up to date to latest needs….
So today, when fixing something completely different I finally managed to trace it to a unfortunate interaction between supporting multiple HTTP signatures algorithms (ed25519 and rsa) and how go-fed/httpsig library adds the signature to the request.
Ie, if the sign request failed for one of the algorithms, the Digest header still gets appended.
So when iterating with the next algo, it fails because it can't set the already set header.
I guess a next step would be to submit a PR to httpsig to cleanup the request if signing actually fails. However I'm not so sure Cory is still watching the space for PRs. :(
Add comment