I have "repl" test sprinkle in the code, but I really need to add a test system and structure all that.

This would also make adding a CI have a better ROI.

especially that I (will) have both a flake.nix and a guix.scm.

Sometimes I want to jot down an issue, it would be nice if I could just click a link in the WebUI.

caching gitlab issues and more locally, for bazingly fast search

why:

• 500s
• speed
• less clutter
• can integrate with other stuff (e.g. fzf)
• can run analysis
• maybe in the future: can [batch] edit issues

how:

• download all issues (and project)
• save (cache) them to disk
• update them intelligently every minute (in server mode)

• Show project IDs
• Button to copy project IDs
• Button to copy issue reference
• more?

https://github.com/dogsheep/github-to-sqlite

Description

I lost internet connection for a moment, but local-gitlab kept periodically trying to fetch information from GitLab. And I had slime connected to it, so I had many debugger (automatically) opened in Emacs.

Acceptance Criteria

• When GitLab's domain name cannot be resolved, don't invoke the debugger (e.g. add a handler-case)
• When multiple errors happen one after the other, when making requests to GitLab. The local-gitlab should stop making new requests for a while, only making a request from time to time in order to verify if the system recovered.
• (Optional) Show a message in the WebUI when the service is degraded. (But keep showing the data)
• In the WebUI, show the last update time