Germany
Hi, 👋
I'm Jakob (they/them).
I talk to computers - and cats.
From Jakob Meier to ~sircmpwn/sr.ht-discuss
I've been wondering whether it might be a good idea to expose more worker options in the config file. I wrote some patches that expose the following options: - s3-location: allows the s3 storage location to be changed - max-artifacts: allows the maximum s3 artifact count to be changed - max-artifact-size: allows the maximum artifact file size to be changed - startup-timeout: allows the worker-startup timeout to be changed (as initially proposed) The names aren't final yet, and I haven't had the chance to test the patches. (My new server is faster than the old one and able to start the workers within the 2-minute default, and I don't know enough about minio to validate the server location)
From Jakob Meier to ~sircmpwn/sr.ht-discuss
I've set up my personal sourcehut instance with build.sr.ht. However, my sourcehut builds kept failing (they won't even start): > [#14] 2023/11/04 19:10:53 Booting image alpine/edge (default) on port 22113 > [#14] 2023/11/04 19:10:53 Waiting for guest to settle > [#14] 2023/11/04 19:12:53 Error: Settle timed out after 3 attempts After looking at the worker source code, I noticed that the settle timeout is hard-coded to 120 seconds [1]. Because it is hard-coded, I had to rebuild the worker and replace the binary to change it (5 minutes did the trick, because it takes about 2 1/2 minutes to spin up). > [#16] 2023/11/05 09:28:23 Booting image alpine/edge (default) on