~williewillus

Seattle, WA

https://www.vincent-lee.net/

Interests: systems programming, Minecraft modding, Touhou Project

Trackers

~williewillus/racket-libraries

Last active 30 days ago

~williewillus/r16

Last active 30 days ago

~williewillus/general

Last active 1 year, 5 months ago

#11 Retry when websocket connection goes down 30 days ago

Comment by ~williewillus on ~williewillus/r16

This was a racket-cord issue and seems to be fixed by the gateway code refactor.

Originally resolved on 2021-02-28 02:48 UTC

REPORTED RESOLVED FIXED

#11 Retry when websocket connection goes down 30 days ago

Ticket created by ~williewillus on ~williewillus/r16

When internet connection hiccups, gateway websocket thread crashes and the bot is useless until restarted. It should attempt to reconnect with some sort of exponential backoff.

Import from another tracker. Originally reported on 2021-02-11 03:13 UTC.

#10 Add statistics for trick invocation counts 30 days ago

Comment by ~williewillus on ~williewillus/r16

Resolved on 2021-02-28 02:48 UTC

REPORTED RESOLVED IMPLEMENTED

#10 Add statistics for trick invocation counts 30 days ago

Ticket created by ~williewillus on ~williewillus/r16

Make sure to segment per-guild, and clear stats on deletion.

Import from another tracker. Originally reported on 2021-02-19 07:40 UTC

#9 Handle Ctrl-C properly 4 months ago

Ticket created by ~williewillus on ~williewillus/r16

Frontends should have an opportunity to gracefully disconnect from their service instead of just dying because the process exits.

#8 Implement console frontend 4 months ago

Ticket created by ~williewillus on ~williewillus/r16

Not very useful but nice for debugging

#7 Implement IRC frontend 4 months ago

Ticket created by ~williewillus on ~williewillus/r16

#6 Improve emote cache handling 4 months ago

on ~williewillus/r16

REPORTED RESOLVED IMPLEMENTED

#85 Allow patches to specific their base commit and dependencies 4 months ago

Comment by ~williewillus on ~sircmpwn/hub.sr.ht

This ticket encompasses ticket #82 as well.

#85 Allow patches to specific their base commit and dependencies 4 months ago

Ticket created by ~williewillus on ~sircmpwn/hub.sr.ht

Mostly copied from a conversation on sr.ht-discuss 0.

Currently, patchsets sent to lists are assumed to apply directly to trunk, and builds will attempt to do so.

This doesn't really work when you have patchsets that depend on other patchsets, e.g. if you're working on a large, complex feature that requires multiple patchsets each containing multiple commits.

GitHub fails miserably at this, forcing contributors to make multiple pull-requests out of the same branch (which makes review difficult as commits of the earlier PR's show up in the later PR's as well), or give up and make one massive monster PR.

Phabricator handles this well by allowing each Revision (patchset) to specify which ones it depends upon.

It would be great to have a way to mark a patchset as depending on another one, and builds would apply all of the prerequisite patchsets before applying the current one for testing.

Fortunately, @emersion pointed out on IRC that Git already has a built-in feature called the "Base Tree Information" 1 whereby you send along with a given patch the public ancestor commit hash, plus the "patch id's" of all the dependencies. Patch-ID's are simply a hashed form of the patch contents.

It would be cool if lists and builds could make use of this to implement dependencies between patches.