ziglang/ziglang.org
14
29
Fork
You've already forked ziglang.org
31

update URL for Mach's Zig mirror #599

Merged
mlugg merged 1 commit from emidoots/www.ziglang.org:main into main 2026年04月08日 01:41:02 +02:00
Contributor
Copy link

Previously, Mach's Zig mirror pkg.machengine.org was written in Go as part of a larger tool that did unrelated things.

We rewrote Mach's mirror in Zig, making a tailor-fit pkgmirror service for just this purpose so that others can host Zig mirrors more easily.

pkg.machengine.org will remain online, but redirects to https://pkg.hexops.org

Signed-off-by: Emi emi@hexops.com

Previously, Mach's Zig mirror pkg.machengine.org [was written in Go](https://github.com/hexops/wrench) as part of a larger tool that did unrelated things. We rewrote Mach's mirror in Zig, making a tailor-fit [pkgmirror](https://code.hexops.org/hexops/pkgmirror) service for just this purpose so that others can host Zig mirrors more easily. pkg.machengine.org will remain online, but redirects to https://pkg.hexops.org Signed-off-by: Emi <emi@hexops.com>
update URL for Mach's Zig mirror
Some checks failed
test website / build (pull_request) Successful in 55s
check mirrors / check (pull_request) Failing after 12m49s
73930b1874
Previously, Mach's Zig mirror pkg.machengine.org [was written in Go](https://github.com/hexops/wrench) as part of a larger tool that did unrelated things.
We rewrote Mach's mirror in Zig, making a tailor-fit [pkgmirror](https://code.hexops.org/hexops/pkgmirror) service for just this purpose so that others can host Zig mirrors more easily.
pkg.machengine.org will remain online, but redirects to https://pkg.hexops.org
Signed-off-by: Emi <emi@hexops.com>
Author
Contributor
Copy link

FYI: pkg.machengine.org is now just a redirect to pkg.hexops.org which has been running nicely :)

FYI: pkg.machengine.org is now just a redirect to pkg.hexops.org which has been running nicely :)
Owner
Copy link

Thank you! FYI, there was one failure in the CI for this mirror, but it may well have been a bug in std.http.Client rather than in your mirror. Still, in case you are able to look into it at all, it was fetching zig-x86_64-netbsd-0.16.0-dev.3006+94355f192.tar.xz, and had this error trace:

/home/ci/deps/zig-x86_64-linux-0.15.2/lib/std/http.zig:594:53: 0x124c1e8 in chunkedReadEndless (std.zig)
 if (rn[0] != '\r' or rn[1] != '\n') return error.HttpChunkInvalid;
 ^
/home/ci/deps/zig-x86_64-linux-0.15.2/lib/std/http.zig:552:17: 0x1227e01 in chunkedStream (std.zig)
 return error.ReadFailed;
 ^
/home/ci/deps/zig-x86_64-linux-0.15.2/lib/std/Io/Reader.zig:178:15: 0x10b6fc2 in stream (std.zig)
 const n = try r.vtable.stream(r, w, limit);
 ^
/home/ci/deps/zig-x86_64-linux-0.15.2/lib/std/Io/Reader.zig:259:25: 0x10eec6c in streamRemaining (std.zig)
 else => |e| return e,
 ^
/home/ci/.cache/act/0894ecd6da11e11a/hostexecutor/check-mirrors/main.zig:574:29: 0x11c35c8 in httpClientFetch (main.zig)
 error.ReadFailed => return response.bodyErr() orelse req.connection.?.getReadError().?,
 ^

No worries if you don't have any way to look into that, I'd probably be willing to put money on it being our fault :P

Thank you! FYI, there was one failure in the CI for this mirror, but it may well have been a bug in `std.http.Client` rather than in your mirror. Still, in case you are able to look into it at all, it was fetching `zig-x86_64-netbsd-0.16.0-dev.3006+94355f192.tar.xz`, and had this error trace: ``` /home/ci/deps/zig-x86_64-linux-0.15.2/lib/std/http.zig:594:53: 0x124c1e8 in chunkedReadEndless (std.zig) if (rn[0] != '\r' or rn[1] != '\n') return error.HttpChunkInvalid; ^ /home/ci/deps/zig-x86_64-linux-0.15.2/lib/std/http.zig:552:17: 0x1227e01 in chunkedStream (std.zig) return error.ReadFailed; ^ /home/ci/deps/zig-x86_64-linux-0.15.2/lib/std/Io/Reader.zig:178:15: 0x10b6fc2 in stream (std.zig) const n = try r.vtable.stream(r, w, limit); ^ /home/ci/deps/zig-x86_64-linux-0.15.2/lib/std/Io/Reader.zig:259:25: 0x10eec6c in streamRemaining (std.zig) else => |e| return e, ^ /home/ci/.cache/act/0894ecd6da11e11a/hostexecutor/check-mirrors/main.zig:574:29: 0x11c35c8 in httpClientFetch (main.zig) error.ReadFailed => return response.bodyErr() orelse req.connection.?.getReadError().?, ^ ``` No worries if you don't have any way to look into that, I'd probably be willing to put money on it being our fault :P
Author
Contributor
Copy link

@mlugg took a quick look, and yeah am suspecting a bug in std.http.Client somehow - at least Firefox can fetch it and it extracts fine:

https://pkg.hexops.org/zig/zig-x86_64-netbsd-0.16.0-dev.3006+94355f192.tar.xz

Also checked logs on the server but nothing relevant. Definitely let me know if you continue seeing anything like this.

@mlugg took a quick look, and yeah am suspecting a bug in `std.http.Client` somehow - at least Firefox can fetch it and it extracts fine: https://pkg.hexops.org/zig/zig-x86_64-netbsd-0.16.0-dev.3006+94355f192.tar.xz Also checked logs on the server but nothing relevant. Definitely let me know if you continue seeing anything like this.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
bounty
https://ziglang.org/news/announcing-donor-bounties
bug
Observed behavior contradicts documented or intended behavior.
contributor-friendly
This issue is limited in scope and/or knowledge of project internals.
downstream
An issue with a third-party project that uses this project.
enhancement
Solving this issue will likely involve adding new logic or components to the codebase.
infra
An issue related to project infrastructure, e.g. continuous integration.
optimization
A task to improve performance and/or resource usage.
question
No questions on the issue tracker; use a community space instead.
regression
Something that used to work in a previous version stopped working
upstream
An issue with a third-party project that this project uses.
use case
Describes a real use case that is difficult or impossible, but does not propose a solution.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ziglang/ziglang.org!599
Reference in a new issue
ziglang/ziglang.org
No description provided.
Delete branch "emidoots/www.ziglang.org:main"

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?