Files
Warp/server/test/complement/run.sh
T
tajniak81andClaude Opus 5.5 92836f8dcd
CI / Test (ubuntu-latest) (push) Canceled after 0s
CI / Test (windows-latest) (push) Canceled after 0s
CI / Storage tests on PostgreSQL (push) Canceled after 0s
CI / Complement (federation off) (push) Canceled after 0s
CI / golangci-lint (push) Canceled after 0s
CI / Smoke test the binary (push) Canceled after 0s
Phase 6: media
Implements PLAN.md Phase 6: the media repository. Clients upload files,
reserve an mxc:// URI and upload to it later, download and ask for
thumbnails, all through the authenticated media endpoints of Matrix 1.11;
other servers download this server's media through the federation media
endpoints, and media uploaded elsewhere is fetched over federation on
first use and kept.

internal/mediaapi is the component. Content goes into a BlobStore named
by its SHA-256, so the same file uploaded twice is stored once and the
hash doubles as the ETag; the metadata that maps an mxc:// URI onto a
blob is in media_repository and media_thumbnails. The local-filesystem
store writes to a temporary file and renames it into place once hashed,
so nothing ever refers to half a file. A storage driver can bring its own
store through storage.BlobProvider, which is where PocketBase's
filesystem abstraction (local or S3) plugs in with Phase 10.

Reserved uploads belong to the user who made them, take one upload,
lapse after a day, and are capped per user; a download of one waits for
its content, woken in memory the moment it arrives, for as long as
timeout_ms allows.

Thumbnails come from a fixed set of configured sizes, so a thousand
requested sizes cannot mean a thousand resizes. They are made on first
request and kept, never enlarge, honour a JPEG's EXIF orientation, and
point at the original when it already fits. The pixel count is checked
from the header before anything is decoded, at most four resizes run at
once, and concurrent requests for the same thumbnail share one.

Remote media is fetched through the signed client: the multipart/mixed
answer of Matrix 1.11, with a fallback to the legacy download endpoint
for servers that answer M_UNRECOGNIZED, and Location redirects followed
by a dialer that refuses loopback, private and link-local addresses.
Concurrent requests share one fetch, detached from the request that
started it. With federation off nothing is fetched, and what was cached
before is still served.

Downloads carry a sandboxing CSP, nosniff, inline Content-Disposition
only for the types the spec lists as safe, and private immutable caching.
The unauthenticated legacy download endpoints are off by default behind
media.legacy_unauthenticated_downloads.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 21:26:49 +02:00

96 lines
4.7 KiB
Bash
Executable File

#!/usr/bin/env bash
# Run Complement against a freshly built Warp image.
#
# server/test/complement/run.sh # the C-S test set, federation off
# COMPLEMENT_PROFILE=federation server/test/complement/run.sh # the federation test set
# server/test/complement/run.sh TestLogin # one test
# COMPLEMENT_TESTS='Test.*' server/test/complement/run.sh
#
# Complement is a separate Go module, so it has to be checked out and run on
# its own. This script keeps that checkout in a cache directory rather than
# vendoring it: it is a test harness we track, not a dependency we pin.
set -euo pipefail
REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/../../.." && pwd)"
: "${COMPLEMENT_REPO:=https://github.com/matrix-org/complement.git}"
: "${COMPLEMENT_REF:=main}"
: "${COMPLEMENT_DIR:=${REPO_ROOT}/.complement}"
: "${COMPLEMENT_IMAGE:=complement-warp}"
: "${COMPLEMENT_PROFILE:=csapi}"
# The target sets for the phases that are done, from PLAN.md section 7. Add
# to them as phases land rather than switching to the whole suite: a pass
# count that goes down because a later phase is missing is noise.
#
# csapi: the Client-Server tests, with federation off. Phase 4 added the
# stream tests: /sync in all its forms, /messages, /context, filters,
# typing, receipts and to-device messaging. What is still out is anything
# needing a later phase — the notification counts of the push rules
# (Phase 8) and the device lists of the keyserver (Phase 7). Phase 6 added
# the media tests: uploads, async uploads, downloads with their file names
# and thumbnails. The remote-media tests are in the federation set, which
# TestRemote.* already covers.
CSAPI_TESTS='TestMedia.*|TestContent.*|TestLocalPngThumbnail|TestAsyncUpload.*|TestUploadLimit|TestRegistration|TestLogin|TestDeviceManagement|TestRoomCreate|TestRoomState|TestRoomAlias|TestRoomForget|TestMembership.*|TestRedaction.*|TestJoinRoom.*|TestLeaveRoom.*|TestKickRoom.*|TestBanRoom.*|TestPublicRoom.*|TestSync.*|TestMessages.*|TestContext.*|TestFilter.*|TestTyping.*|TestReceipt.*|TestToDevice.*|TestRoomCreationReportsEventsToMyself|TestLazyLoading.*|TestWriteMDirectAccountData'
# federation: Phase 5. Joins, leaves and invites across servers, keys,
# transactions, missing events, server ACLs and the queries. Partial-state
# joins (MSC3706, TestPartialStateJoin*) are not implemented and are left
# out; so is anything needing an application service (Phase 9) or device
# lists (Phase 7).
FEDERATION_TESTS='TestFederation.*|TestJoinViaRoomIDAndServerName|TestJoinFederatedRoom.*|TestBannedUserCannotSendJoin|TestCannotSendNon.*Via.*|TestCannotSendKnockViaSend.*|TestOutboundFederation.*|TestInboundFederation.*|TestInboundCanReturnMissingEvents|TestRemoteAliasRequestsUnderstandUnicode|TestNetworkPartitionOrdering|TestACLs|TestGetMissingEventsGapFilling|TestEventAuth|TestUnbanViaInvite|TestJoinRoomWithFederation.*|TestRemote.*'
case "$COMPLEMENT_PROFILE" in
csapi)
: "${COMPLEMENT_TESTS:=$CSAPI_TESTS}"
PACKAGES=(./tests/csapi/...)
FEDERATION_ENABLED=false
;;
federation)
: "${COMPLEMENT_TESTS:=$FEDERATION_TESTS}"
PACKAGES=(./tests/... )
FEDERATION_ENABLED=true
;;
*)
echo "complement: unknown COMPLEMENT_PROFILE '$COMPLEMENT_PROFILE' (want csapi or federation)" >&2
exit 2
;;
esac
if [[ $# -gt 0 ]]; then
COMPLEMENT_TESTS="$(IFS='|'; echo "$*")"
fi
docker="${DOCKER:-docker}"
if ! command -v "$docker" >/dev/null 2>&1; then
echo "complement: $docker is not installed; Complement needs a container runtime" >&2
exit 1
fi
echo "complement: building $COMPLEMENT_IMAGE"
"$docker" build -t "$COMPLEMENT_IMAGE" -f "${REPO_ROOT}/server/test/complement/Dockerfile" "$REPO_ROOT"
if [[ ! -d "$COMPLEMENT_DIR" ]]; then
echo "complement: cloning $COMPLEMENT_REPO into $COMPLEMENT_DIR"
git clone --depth 1 --branch "$COMPLEMENT_REF" "$COMPLEMENT_REPO" "$COMPLEMENT_DIR"
else
git -C "$COMPLEMENT_DIR" fetch --depth 1 origin "$COMPLEMENT_REF"
git -C "$COMPLEMENT_DIR" checkout -q FETCH_HEAD
fi
echo "complement: running '${COMPLEMENT_TESTS}' (profile ${COMPLEMENT_PROFILE}, federation ${FEDERATION_ENABLED})"
cd "$COMPLEMENT_DIR"
# COMPLEMENT_SPAWN_HS_TIMEOUT_SECS is generous because the first container
# of a run has to apply the migrations on a cold SQLite file.
#
# COMPLEMENT_SHARE_ENV_PREFIX hands every host variable starting with
# PASS_ to the homeserver containers, prefix removed: it is how the profile
# reaches the entrypoint's federation switch.
COMPLEMENT_BASE_IMAGE="$COMPLEMENT_IMAGE" \
COMPLEMENT_SPAWN_HS_TIMEOUT_SECS="${COMPLEMENT_SPAWN_HS_TIMEOUT_SECS:-60}" \
COMPLEMENT_DEBUG="${COMPLEMENT_DEBUG:-0}" \
COMPLEMENT_SHARE_ENV_PREFIX=PASS_ \
PASS_WARP_FEDERATION_ENABLED="$FEDERATION_ENABLED" \
go test -count=1 -v -timeout 30m -run "^(${COMPLEMENT_TESTS})$" "${PACKAGES[@]}"