Commit graph

12 commits

Author SHA1 Message Date
abd422edb7
changes for zig 0.16.0
Some checks failed
aws-zig nightly build / build-zig-nightly (push) Failing after 23m34s
2026-04-16 16:22:48 -07:00
a3d0718e7b
Merge branch 'master' into zig-develop 2026-04-16 09:30:43 -07:00
6e34e83933
do not emit null optional fields
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 15m4s
2026-02-01 17:47:51 -08:00
3f5d9d9542
updates for PR 25592 (std.Io interface) and 25706 (remove Oracle Solaris)
Some checks failed
aws-zig nightly build / build-zig-nightly (push) Failing after 26s
2025-11-06 12:05:49 -08:00
10a0e0ab99
adjust stack trace changes in zig 0.16.0-dev.565+f50c64797
Some checks failed
aws-zig nightly build / build-zig-nightly (push) Failing after 20m56s
2025-10-02 08:15:38 -07:00
5ba3be2cc4
move off of deprecated APIs 2025-09-03 14:00:36 -07:00
cfc8aee1a6
a lot of test code, plus a one line ".deinit()" fix
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m39s
2025-08-25 14:14:15 -07:00
214c580db4
get failing live request under unit test 2025-08-25 13:07:46 -07:00
e29829f2a0
fix failing s3 test
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Failing after 6m25s
Not quite sure the problem I saw earlier in aws.zig, but the data
entering that switch prong is []const u8, so it is fine for what we are
doing
2025-08-25 10:00:50 -07:00
74704506d8
update tests for zig 0.15.1
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Failing after 1m41s
This removes the need to spin up a web server for each test, instead,
mocking the necessary methods to do everything in line. This will make
the tests much more resilient, and with the remaining WriterGate changes
expected in zig 0.16, I suspect the mocking will be unnecessary in the
next release.

There are several test issues that remain:

* Two skipped tests in signature verification. This is the most
  concerning of the remaining issues
* Serialization of [][]const u8 was probably broken in zig 0.14.1, but
  the new version has surfaced this issue. Warning messages are being
  sent, and this needs to be tracked down
* One of the tests is failing as S3 storage tier extra header is not
  being offered. I'm not sure what in the upgrade might have changed
  this behavior, but this needs to be investigated
2025-08-24 15:56:36 -07:00
90c5efcace
clean up all the basic things 2025-08-23 09:44:34 -07:00
0a0933e38f
move test suite to its own file 2025-08-23 09:20:22 -07:00