I'm so glad the new uuid package landed - it's overdue but a very welcome addition! I've already replaced github.com/google/uuid with `uuid` in several projects
More or less, but most harnesses will rely on tools such as grep to only read portions of files. For even a small sized repo, only a small portion would be tokenized and uploaded
>For even a small sized repo, only a small portion would be tokenized and uploaded
Only on a per-chat basis. Over time, it'll eventually grab the entire repo, or enough of the "secret sauce" that the rest can be reconstructed with AI.
This seems roughly similar to Google's Cloud Run gen2 instance types. My understanding is with the second generation, they are running microvms which are bootstrapped from a container image.
Interesting - I run a nearly identical set, with many TLDs configured in `/etc/resolver/X` and dnsmasq handling the resolve and I have not had a single issue.
I noticed in the author's bug report they do not include `domain`, which is documented in `man 5 resolver` as:
# The domain directive is only necessary, if your local
# router advertises something like localdomain and you have
# set up your hostnames via an external domain.
In the real world though, I've found the `domain` setting to be required nearly every time. I wonder if adding it will resolve the issue?
I've been having great success with LLMs generating Mermaid diagrams and flowcharts from a repo. Claude Code and Cursor both do consistently great jobs. For example: `generate a mermaid swimlanes diagram of the XX logic flow`.
This is what I do previously too! The problem that I realize with them is that mermaid diagrams and flowcharts are static and sometimes oversimplified.