Re:Migrating the main Zig repository from GitHub to Codeberg
by magicalhippo on Thursday November 27, 2025 @01:40AM
(#46066405)
Clearly the job for a microservice. Accept number of seconds to wait as url, return content after that many seconds. Then just use curl in runner.
[ Parent
| on HN ]
Re:Migrating the main Zig repository from GitHub to Codeberg
by xp84 on Thursday November 27, 2025 @02:30AM
(#46066688)
Brb founding a SaaS startup. I’ll call it cloudsleep dot io of course. After our Series B I’ll buy the .com.
Only task to do before lining up investors is how can I weave AI into our product?
Re:Migrating the main Zig repository from GitHub to Codeberg
by debugnik on Thursday November 27, 2025 @03:29AM
(#46067055)
Describe the task you're waiting for as text, and let an LLM pick the number of seconds for each request. More expensive the better model you clearly need for this. There, your AI pitch.
Re:Migrating the main Zig repository from GitHub to Codeberg
by xp84 on Thursday November 27, 2025 @02:46PM
(#46072628)
Excellent, welcome aboard, Chief Product Officer!
Re:Migrating the main Zig repository from GitHub to Codeberg
by wmanley on Thursday November 27, 2025 @02:41AM
(#46066755)
Retries won’t work in that case. Would be better to have two endpoints: get the time in x seconds and wait until time passed. That way retrying the wait endpoint will work fine and if time hasn’t elapsed it can just curl itself with the same arguments.
Re:Migrating the main Zig repository from GitHub to Codeberg
by dpkirchner on Thursday November 27, 2025 @09:05AM
(#46069371)
If you have curl (but not sleep) sure, but if not maybe you can use bash's wacky /dev/tcp. The microservice could listen on ports 1 through 64k to let you specify how many seconds to sleep.