gbaz
I don't think this is a useful feature worth pursuing. Seems like it adds a lot of overhead to how we think about solving, with very little meaningful gain.
cc @andreasabel (who has been looking to take over some matrix maintenance from herbert, who has been too busy to deal with it) Fixing the auto-status url is a longtime...
update: one of the disks is borked. davean thinks he can restore from backup, but isn't sure about timing.
candidate replacement (not an improvement, just getting everything working again on a new box) at https://matrix.haskell.org -- we plan to swap it over soon, if anyone wants to poke it...
No updates to give -- the migrated box doesn't work right, and nobody has had time to investigate why. We need a good sysadmin volunteer to step up and work...
pr that started on notification email work: https://github.com/haskell/hackage-server/pull/622
should be resolved by https://github.com/haskell/hackage-server/pull/1110 ?
Hopefully this should all be rounded out and deployed with the other gsoc stuff at the end of summer. Good proposal about notify on failures only. @AliasQli
since the issue is fixed by https://github.com/serokell/acid-state/commit/26c9339 shouldn't this be closed?
It looks like this was the concern. > So I think it is correct that we can distinguish between a user forgetting to update their 'SafeCopy' instances the case where...