Retry (w/ back-off) downloading the installer binary #46
Loading…
Reference in a new issue
No description provided.
Delete branch "retries"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
node-fetch
with node's builtin fetchfetch-retry
as a new depfetch-retry
to retry and exponentially back-off on downloading the installerTested by running the GH CI workflow in my private repo, and it should run here again.
I don't do a lot of JS/TS and that's being generous to me. Please feel free to review harshly, happy to learn anything, even if nit-y. 🙏
Additional context, per
fetch-retry
readme:retryOn
network failures by defaultChecklist
@ -423,8 +434,10 @@ class NixInstallerAction {
}
I'd really like to not use
any
here...Once the
any
use is resolved, I think it looks fine?@ -423,8 +434,10 @@ class NixInstallerAction {
}
Ack, I looked at this again and slightly have a better feel for what's going on. I can convert the fileStream be Web-y and then I don't have to cast, and don't have to use
any
.New commit, more node-y naming for
fetchRetry
and fixed the aforementioned casting/any issue.Huh. It's a bit tricky having
dist/
checked in, one has to be careful to ensure that it gets rebuilt after rebasing, and it probably means that it's "wrong" for inbetween commits. Huh.Yeah it's just 'great'.