Merge main into next after 416 (closes #497)

Conversation 1 Commits 3 Files Changed -

3 Commits

Author	SHA1	Message	Date
clawbot	7963188c1e	Merge main into next after 416 (closes #497 ) check / check (push) Successful in 6m8s Details Makes main an ancestor of next, so the milestone PR merges again. script/test conflicted and keeps next's version, which already runs without -v, caps memory with -p 4 -parallel 8, adds coverage and reruns failed tests with -v. password.go, password_test.go, export_test.go and resetpw_test.go merged on their own: main's lines there are the same as next's. The merged tree equals next's. Model: opus-5-5	2026-10-03 12:17:30 +00:00
clawbotandsneak	16ed356b68	main side of 414: cheaper test hashing, and failing tests visible in the build log (closes #414 ) (#416 ) check / check (push) Successful in 3m21s Details The `main` side of #414: the two changes that make `next` green, and nothing else from `next`. Each is its own commit, so it can be compared with its `next` counterpart. - #404, as merged to `next`: a test binary hashes passwords at a 1 MB Argon2id cost instead of 64 MB, `TestHashPassword_ShippedParameters` keeps the shipped cost covered, and `script/test` runs at most four packages and eight parallel tests at once. Every test that starts a database hashed the admin password at 64 MB, which on a busy host made `internal/handlers` overrun its application start and its 90-second timeout. That is what turned `main` red. - #415: `script/test` runs without `-v`, so the build log, which the Docker build cuts off at 2 MiB, carries one result line per package and, for a package that fails, everything its tests wrote, application log lines included, instead of only passing packages. What the diff does not show: `script/test` differs from `next` by one line. `main` has no `script/assets` yet, so it is not called. Several packages failing at once can still reach the 2 MiB limit. - Judgement call: both commits keep their subjects from `next`, including their `closes` references. - Deviation and not fixed here: the same two as on #415 (no `-v` rerun on failure, #315; remaining sensitivity to extreme CPU load, #225). Model: opus-5-5 Co-authored-by: sneak <sneak@sneak.berlin> Reviewed-on: #416 Co-authored-by: clawbot <35+clawbot@noreply.example.org>	2026-10-03 14:08:51 +02:00
sneak	f703b72ce0	Next (#364 ) check / check (push) Successful in 3m59s Details Reviewed-on: #364	2026-09-29 13:05:57 +02:00

Author

SHA1

Message

Date

clawbot

7963188c1e

Merge main into next after 416 (closes #497 )

check / check (push) Successful in 6m8s

Details

Makes main an ancestor of next, so the milestone PR merges again.
script/test conflicted and keeps next's version, which already runs
without -v, caps memory with -p 4 -parallel 8, adds coverage and reruns
failed tests with -v. password.go, password_test.go, export_test.go and
resetpw_test.go merged on their own: main's lines there are the same
as next's. The merged tree equals next's.

Model: opus-5-5

2026-10-03 12:17:30 +00:00

clawbotandsneak

16ed356b68

main side of 414: cheaper test hashing, and failing tests visible in the build log (closes #414 ) (#416 )

check / check (push) Successful in 3m21s

Details

The `main` side of #414: the two changes that make `next` green, and nothing else from `next`. Each is its own commit, so it can be compared with its `next` counterpart.

- #404, as merged to `next`: a test binary hashes passwords at a 1 MB Argon2id cost instead of 64 MB, `TestHashPassword_ShippedParameters` keeps the shipped cost covered, and `script/test` runs at most four packages and eight parallel tests at once. Every test that starts a database hashed the admin password at 64 MB, which on a busy host made `internal/handlers` overrun its application start and its 90-second timeout. That is what turned `main` red.
- #415: `script/test` runs without `-v`, so the build log, which the Docker build cuts off at 2 MiB, carries one result line per package and, for a package that fails, everything its tests wrote, application log lines included, instead of only passing packages.

What the diff does not show: `script/test` differs from `next` by one line. `main` has no `script/assets` yet, so it is not called. Several packages failing at once can still reach the 2 MiB limit.

- Judgement call: both commits keep their subjects from `next`, including their `closes` references.
- Deviation and not fixed here: the same two as on #415 (no `-v` rerun on failure, #315; remaining sensitivity to extreme CPU load, #225).

Model: opus-5-5
Co-authored-by: sneak <sneak@sneak.berlin>
Reviewed-on: #416
Co-authored-by: clawbot <35+clawbot@noreply.example.org>

2026-10-03 14:08:51 +02:00

sneak

f703b72ce0

Next (#364 )

check / check (push) Successful in 3m59s

Details

Reviewed-on: #364

2026-09-29 13:05:57 +02:00

Merge main into next after 416 (closes #497) #498