Tisa Akhter

What an agent can do with the goflow corpus

webdomain0126/goflow: Distributed job processing engine in Go: PostgreSQL queue (SKIP LOCKED), worker pools, retries, Redis rate limiting

• Look up how goflow implements distributed-systems, docker, go, with answers cited to file and line.
• Reuse a worked example: the commit “Build GoFlow job engine (M1-M9)” (46 files · Go, SQL).
• Answer from goflow's real Go source instead of memory (Databases and storage engines).

• Where does goflow handle “Build GoFlow job engine (M1-M9)”?
• How does goflow implement distributed-systems?
• What does internal/worker do in goflow?

Search the GitHub repository webdomain0126/goflow with XERJ (https://hub.xerj.org/corpus/webdomain0126--goflow).
Run these in a shell, in order, and check each result before the next:
1. xerj --help  (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh
2. git clone https://github.com/webdomain0126/goflow goflow && git -C goflow checkout 07124303012edcd3711ed47f6908a2caa6b17a0f
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./goflow --url http://127.0.0.1:9200 --prefix goflow --progress plain
5. xerj autoindex map --url http://127.0.0.1:9200
Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt
Licence: MIT. Keep the copyright notice and credit the authors.

corpus webdomain0126--goflow · Databases and storage engines
Related corpora: goss, nats-server, hitesh22rana/chronoverse, omnomkar/event-driven-orders
Case study: reference coding for agents