Stephen Wicklund issues

Results 189 issues of


                                            Stephen Wicklund

Fix whatever was causing the db volume-claim to run out of space. (perhaps raise PVC size, or fix some misconfiguration)

Update: Around 2024-06-25, the db volume-claim ran out of space again. When we looked into it, it appeared to be due to the `pg_wal` folder growing very large (something like...

backend

Once done evaluating Rancher Desktop, possibly mark that as the new Windows/Mac preference (replacing docker-desktop)

Annoyances with Docker Desktop: * https://github.com/microsoft/WSL/issues/8725 * This issue may be just a problem with WSL; to be seen if Rancher Desktop surfaces the same problem.

Fix that pgbackrest sometimes stops operating in prod cluster (at least add alerts!)

Make-so when in a skin with skin-specific map-prefix, and user is admin, there is give some visual indicator on map entries that will not be visible in the current-skin when viewing as a non-admin

Rework the skins to be based on config objects that are user-editable

Add "In map" checkbox to search panel; when enabled, search only in the current map, and signal the existence of matches within each subtree (ie. at deepest visible node)

Get scripts/configs and instructions set up for having local app-server run "on host" (ie. outside of k8s), and with vscode debugging enabled

Core things to solve: * Adjust the app-server's code so that it can detect when it is running outside of docker/k8s, and connect through a k8s proxy to the database...

Fix that after a while, docker-desktop has deploys fail, with error "Docker is not responding. Maybe Docker is out of disk space? [...]"; seems to be memory issue

Likely related to WSL memory limits being reached. Notes: * On my desktop, the WSL memory limit is 8gb. ### Possibly related posts/issues Related to memory: * Has tip that...

Fix concurrent-update error on "editCount" field for user (at least for case of claim-miner's map generations)

Modify nginx to have a higher query timeout (seems 60s atm)

This task would be reasonably straightforward to achieve with access to the full NGINX configuration syntax. This is not currently possible using nginx-gateway-fabric, however: https://github.com/nginxinc/nginx-gateway-fabric/issues/2417 So to achieve this right...