the Internet


Natural intelligence with inherited memory dated back to Web 2.0. 100% made on Earth.

#20 Incremental upload a month ago

Ticket created by ~iacore on ~sircmpwn/pages.sr.ht

When the website is around 5MiB, it takes awhile to upload, and sometimes just hang. It would be better if srht.site supports incremental upload.

Some choices: rsync https://docs.itch.ovh/wharf/master/ git

#120 Support multiple email aliases 2 months ago

Comment by ~iacore on ~sircmpwn/meta.sr.ht

Hello ~sircmpwn, what's the status on this?

#58 Implement build caches 5 months ago

Comment by ~iacore on ~sircmpwn/builds.sr.ht

~adnano Thanks. I revoked it yesterday. It only needs JOBS:R anyway.

#58 Implement build caches 5 months ago

on ~sircmpwn/builds.sr.ht

~iacore: you should revoke your personal access token, it's no longer a secret. See https://man.sr.ht/builds.sr.ht/#keeping-your-secrets-a-secret

#58 Implement build caches 5 months ago

Comment by ~iacore on ~sircmpwn/builds.sr.ht

I made a very flaky prototype.

two builds: https://builds.sr.ht/~iacore/job/826339 https://builds.sr.ht/~iacore/job/826341

notice the "build 0 -> 1" and "1 -> 2" in final task's log


  • it only looks for previous build artifact on first page of result
  • it uses tag to find which build job is from the same repo. Therefore, it doesn't trigger on resubmitted job. A more robust solution might be to parse the build manifest (YAML).

Unrelated question: how does 'hut' get access token in CI? I don't know how, so I added my own personal token as secret for the above demo.

#58 Implement build caches 5 months ago

Comment by ~iacore on ~sircmpwn/builds.sr.ht

I can probably make something based on build artifact. A task upload "build cache" as build artifact, and later tasks query previous build jobs and fetch the "build cache".

I use Rust in my pipeline, and rebuilding from scratch waste CPU time.