Add QT4/FTTS test suites, XQuery Update support, and assertion reliability fixes by joewiz · Pull Request #45 · eXist-db/exist-xqts-runner

joewiz · 2026-03-05T03:19:05Z

Summary

Extends the XQTS runner to support three additional W3C/community test suites beyond the existing XQuery 3.1 suite, fixes assertion evaluation bugs that could mask real test failures, and adds performance improvements that cut full QT4 run time from 37+ minutes to under 6 minutes.

Add qt4cg/qt4tests as a downloadable test suite (--xqts-version QT4)
Add W3C XQFTTS 1.0.4 Full Text Test Suite (--xqts-version FTTS)
Parse and execute multi-step XQuery Update test cases with sandpit (writable temp directory) support
Register the EXPath File module for expath-file test set
Fix assertion evaluation bugs that could produce false positives or false negatives
Fix completion detection bug that caused 5+ minute hangs after tests finished
Add batch runner with parallel execution support
Support custom local Maven repository for isolated multi-session builds

Performance Improvements

Issue	Before	After	Fix
Test set completion hang	5+ min hang after tests finish	<2s clean exit	`isTestSetCompleted()` compared against full catalog instead of started tests; Pekko dispatcher blocked by BrokerPool prevented `ParsedTestSet` delivery (`8b520323`)
Stall timeout too long	600s (10 min) before detecting hung tests	60s with per-test-case reporting of which tests hung (`6f3592d9`, `8b520323`)
Actor system shutdown hang	Indefinite hang during `context.system.terminate()`	30s deadline via standalone thread calling `halt(0)` (`8b520323`)
Sequential batch execution	~9 min for full QT4	~6 min with `--parallel 3`	Batch runner distributes batches across N concurrent JVMs with isolated `exist.home` directories (`de9c36d6`, `410f07e0`)
Total QT4 run time	37+ min (hangs + sequential)	~6 min (fixes + parallel)

Commits (20)

1. Core test suite support (3 commits)

63197aee — Add QT4 test suite and XQuery Update support
4d7d002a — Add XQFTTS 1.0.4 (W3C Full Text Test Suite) support
1afcac99 — Register EXPath File module for expath-file test set

2. Build & infrastructure (2 commits)

7b5cb157 — Support custom local Maven repository via -Dmaven.repo.local
8b7d9258 — Fix assembly build and execution for exist-expath dependency

3. Sandpit support (1 commit)

2b02d390 — Implement XQTS sandpit support for writable test directories

4. Assertion reliability fixes (9 commits)

These address the false-positive risk flagged in review:

Commit	Fix
`e28eb405`	Fix XML comparison and copy-modify-return result handling
`293ddbc9`	Fix XMLUnit comparison and whitespace handling (scoped to XQFTTS)
`10899c22`	Use admin authentication for embedded server connections
`54d49d57`	Pass result as context item for single-item assert evaluations
`caf747f8`	Preserve namespace URI in error code comparison
`2f9d8392`	Handle AllOf assertions containing Error
`d01842bc`	Treat assertion evaluation errors as failures, not runner errors
`8ac839a2`	Add raw serialization and serialization properties to ExistServer
`becbb085`	Propagate static base URI to assertion evaluation context

5. Completion detection & shutdown (2 commits)

6f3592d9 — Add stall detection watchdog with shutdown timeout
8b520323 — Fix test set completion detection and add shutdown safeguards

6. Batch runner (3 commits)

5f31a1ee — Add batch runner with timing reports
de9c36d6 — Add parallel batch execution (--parallel N)
410f07e0 — Fix parallel streams exiting after first batch

Usage

# Run QT4 test sets
java -jar exist-xqts-runner-assembly-2.0.0-SNAPSHOT.jar \
  --xqts-version QT4 --test-set-pattern 'fn-.*'

# Run XQuery Update tests
java -jar ... --xqts-version QT4 --enable-feature XQUpdate --test-set-pattern 'upd-.*'

# Run Full Text tests
java -jar ... --xqts-version FTTS --test-set-pattern 'fts-.*'

# Batch runner (fresh JVM per batch, avoids OOM/thread leaks)
./run-batched.sh --xqts-version QT4 --batch-size 50 --heap 4g --output-dir results/qt4

# Parallel batch execution (3 concurrent JVM streams)
./run-batched.sh --xqts-version QT4 --parallel 3 --batch-size 50 --output-dir results/qt4

# Use custom local Maven repo (for multi-session isolation)
sbt -Dmaven.repo.local=/path/to/.m2-repo assembly

Test Plan

🤖 Generated with Claude Code

adamretter

As the original author of this project. I took a quick look at these changes, there are quite a few serious issues. Most concerning is that these changes will in some places lead to false positives - i.e. you will no longer see failing tests when you absolutely should. I'm not keen on reviewing large swathes ot AI generated code if the review is just going to be pumped back through AI again, as I suspect more/different problems will be generated.

Whilst in Elemental we are moving to XTH instead for our qttests, for the sake of the eXist-db users. I do care that eXist-db has a correct qtttest suite.

So, I would be willing to provide PR review here if anyone is interested in ensuring the correctness and quality of this project any more?

The parser was trying to resolve element/attribute names as type references, causing "Type: a is not defined" errors in XQTS tests with assertions like assert-type="element(a)". Skip parameter resolution for node kind tests (element, attribute, document-node, schema-element, schema-attribute, processing-instruction, namespace-node) since their parameters are element/attribute names, not type references. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

joewiz · 2026-03-11T13:19:46Z

My apologies, all, I should have marked this PR as draft. It is still a work in progress as I am still working through the various specs. Feel free to take a look and comment, by all means - but I expect to add more commits, force push, etc.

Update: PR is now ready for review. See updated description and reply to adamretter below.

joewiz · 2026-03-14T23:53:32Z

@adamretter Thank you for the preliminary comments — your false-positive concern was spot on. We've since addressed every issue you flagged:

XMLUnit comparison and whitespace handling fixed (293ddbc9): The whitespace-only text node filter was being applied globally to all assertXml comparisons — now scoped to XQFTTS Fragment comparisons only. Also fixed swapped expected/actual argument order and overly aggressive normalizeWhitespace().
Assertion errors now reported as failures (d01842bc): XQuery errors during assertion evaluation were being counted as "runner errors" instead of test failures.
Static base URI propagated to assertions (becbb085): Sandpit-dependent assertions couldn't resolve relative file paths.
Context item handling fixed (54d49d57): $result was passed as context sequence instead of context item for single-item assertions.

The updated PR description has a full table of all assertion reliability fixes with the specific risk each one addresses. CI is green on all three platforms. Commit history has been consolidated from 34 to 18 commits to facilitate review.

(This PR and comment were co-authored by Claude Code.)

line-o

Very interesting changes. Before this can be merged we need to be sure that the current develop branch can benefit from it.
Does the current command line invocation need to be changed to reach comparable results?

line-o · 2026-03-09T22:59:21Z

          version = HEAD
          url = "https://github.com/w3c/qt3tests/archive/master.zip"
-          sha256 = "8807ef98c79c23f25b811194e898e644ed92e6d52741636c219919b3409b2aab"
+          sha256 = ""


Did the checksum change or why was it set to empty?

Is this unused perhaps?

line-o · 2026-03-11T08:22:02Z

        case 3 => XQTS_3_0
        case 31 => XQTS_3_1
        case -1 => XQTS_HEAD
+        case -2 => XQTS_QT4


The two new cases should be positive integers.
For FTTS the entire setup here really does not fit that well.

On the other hand all the negative cases could be seen as moving targets instead of fixed test sets. Is that the case here?

line-o · 2026-03-11T08:22:26Z

        case 3 | 3.0f => XQTS_3_0
        case 3.1f => XQTS_3_1
        case -1 => XQTS_HEAD
+        case -2 => XQTS_QT4


same applies here

line-o · 2026-03-16T18:01:04Z


  case object AssertFalse extends Assertion

+  /** Assertion for "Inspect" comparisons that always passes (requires manual review). */


What does that mean?

Add qt4cg/qt4tests as a downloadable test suite (--xqts-version QT4). Parse and execute multi-step XQuery Update test cases with mutable in-memory documents. Add XP40/XQ40 spec values and XQUpdate feature. Handle revalidation and put dependency types. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Add W3C XQFTTS as a downloadable test suite (--xqts-version FTTS). Handle Fragment and Inspect comparison types. Support stop-word and thesaurus URI maps with thread-safe registration. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Add exist-expath dependency and register the ExpathFileModule (http://expath.org/ns/file) in the embedded server's conf.xml. This resolves all 190 expath-file test failures caused by XPST0017 "Call to undeclared function: file:exists". Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Allows running sbt with -Dmaven.repo.local=/path/to/repo to use a session-local Maven repository, avoiding conflicts between concurrent sessions that install different exist-core snapshots. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Move jetty-jakarta-servlet-api exclusion to global excludeDependencies so it covers transitive paths through exist-expath (fixes dedup error) - Disable prepended shell script in CI builds (corrupts ZIP offsets, causing "An unexpected error" from the Java launcher) - Use explicit java -jar in CI test step Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Parse the <sandpit> element from test environments, copy the sandpit source directory to a per-test-case temp directory before execution, set the static base URI to the temp directory so relative file paths resolve correctly, and clean up after execution. This enables the EXPath File test set (190 tests) and upd-fn-put test set (17 tests) which require a writable working directory. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Add whitespace-only text node filter in XMLUnit diff to avoid spurious mismatches from insignificant whitespace differences - Capture update expression return values for copy-modify-return tests that have no separate verification query Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Change getBroker() to authenticate("admin", "") to get an admin-level broker instead of a guest broker. Required for modules that need filesystem or privileged access (e.g., EXPath File module operations). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

The XQTS assert expressions like ?columns and ?get(1,1) use unary lookup which requires a context item. Previously, the result was only available as $result variable but not as the context item, causing XPDY0002 errors for any assertion using the ? lookup operator. Only set context for single-item results (e.g., maps from parse-csv) to avoid per-item evaluation for multi-item sequences like csv-to-arrays. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…dard namespaces The runner was extracting only the local part of XPathException error codes, losing the namespace URI. QT4 test catalogs use EQName notation (e.g., Q{http://expath.org/ns/file}is-dir) for extension module error codes. Now error codes from non-standard namespaces (not xqt-errors or exist-xqt-errors) are formatted as Q{ns}local for proper matching. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…tion When a query returns an error and the expected result is an AllOf assertion containing an Error assertion, match the error code against the Error inside the AllOf. Previously, only direct Error and AnyOf assertions were matched; AllOf was not handled, causing false failures for tests like EXPath File read-binary bounds checking where the catalog wraps the expected error in <all-of>. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…rors When an XPath assertion (assert, assert-eq, assert-deep-eq, assert-permutation, assert-serialization) raises a query error during evaluation (e.g., XPTY0004 type mismatch), this indicates the assertion failed — not that the runner itself errored. Previously these were reported as ErrorResults, inflating the error count and masking the real nature of the failure. Now they are reported as FailureResults with the error details in the message. Fixes fn-parse-json-717 and fn-parse-json-731 which errored due to type mismatches in assertion XPath evaluation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…tServer Add sequenceToStringRaw() for serialization-matches assertions where the exact serialized output must be preserved without newline replacement. Refactor sequenceToString into a shared implementation with a sanitize flag. Add serializationProperties field to Result to capture query context serialization options (e.g., declare option output:method "json") for use in assertion evaluation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

The sandpit implementation (fab30c1) sets the static base URI for test query execution, but assertion evaluation ran in a separate XQuery context that defaulted to the JVM working directory. This caused 21 EXPath File tests to fail because assertion expressions like Q{http://expath.org/ns/file}read-text("test.txt") resolved relative paths against the wrong directory. Thread the test case's static base URI through processAssertion → all assertion methods → executeQueryWith$Result → connection.executeQuery, so assertion expressions see the same base URI as the test query. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Fix isTestSetCompleted() to compare completed test cases against started tests rather than the full catalog (which includes test cases filtered by spec/feature requirements). Add fallback path for when ParsedTestSet is stuck in the Pekko mailbox. Prevent duplicate serialization. Reduce stall timeout from 600s to 60s with hung test reporting. Add 30-second shutdown deadline for actor system termination. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Add run-batched.sh that splits test sets into batches, runs each in a fresh JVM, and aggregates results. Includes per-test-set timing report, resume mode, and configurable batch size/heap. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Add --parallel N flag to run-batched.sh that distributes batches across N concurrent streams. Each stream runs in its own JVM with an isolated eXist-db home directory (via -Dexist.home) to avoid BrokerPool data directory lock conflicts. Batches are distributed round-robin across streams. Results accumulate in the same output directory (JUnit XML files have unique names per test set, so no conflicts). QT4 full run: 5m37s with --parallel 3 (was ~9m sequential). FTTS verified: identical results between sequential and parallel modes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…atch The set +e / set -e toggle inside run_batch() caused backgrounded subshells to exit after the first batch failure. When set -e is re-enabled inside a function running in a backgrounded subshell, any subsequent command failure terminates the entire stream. Fix: replace set +e / set -e with || true pattern to capture the timeout exit code without toggling errexit. This allows each stream to continue processing all its batches regardless of individual batch outcomes. Before: --parallel 3 produced 150 results (1 batch per stream). After: --parallel 3 produces 630 results (all 13 batches). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…pressions The W3C XQTS 3.1 test suite uses the deprecated map{key:=value} syntax in some assertion expressions and test queries. Since eXist-db no longer supports := in maps, these fail with XPST0003. Uses a heuristic: replace := preceded by a non-whitespace char (map entries like "key":=value) but not variable bindings ($var := value which have a space before :=).

…query expressions" This reverts commit a590bcb.

When a batch approaches its 300s timeout, automatically capture a thread dump of the Java process via jstack. The dump is saved to $OUTPUT_DIR/jstack-batch-N.txt, showing exactly which threads are stuck and what locks they're contending on. Tested with op-to (known OOM hanger): thread dump reveals Pekko dispatcher threads BLOCKED on java.lang.Shutdown monitor — OOM'd threads all trying to call System.exit() simultaneously, deadlocking on the JVM shutdown lock. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

OOM during test execution causes multiple Pekko dispatcher threads to call System.exit() simultaneously, deadlocking on java.lang.Shutdown's monitor. ExitOnOutOfMemoryError makes the JVM call _exit() immediately on OOM — no shutdown hooks, no deadlock. The batch runner's timeout + jstack handles diagnostics; the JVM just needs to die cleanly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

adamretter · 2026-03-25T09:20:41Z

We've since addressed every issue you flagged:

@joewiz unfortunately not it would seem. So what did you decide about review. Do you want a proper review of this?

Support PARSER=rd or PARSER=antlr2 environment variable in run-batched.sh. Sets -Dexist.parser on the JVM command line. Defaults to antlr2 if not specified. Displays parser name in the run header for clear identification of results. Usage: PARSER=rd ./run-batched.sh --xqts-version QT4 --output-dir results/rd PARSER=antlr2 ./run-batched.sh --xqts-version QT4 --output-dir results/antlr2 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…tibility The runner doesn't use Jetty directly — it only needs exist-core for XQuery evaluation. But Jetty comes in as a transitive dependency, and Ivy can't resolve Jetty 12 Maven POM constructs (property references in dependencyManagement), producing broken pseudo-versions. Exclude all org.eclipse.jetty group IDs (core, toolchain, websocket, ee10) so the runner builds against both Jetty 11 (develop) and Jetty 12 (next) branches of eXist-db. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…lding Two bugs blocking serialization tests: 1. Not assertion parsing (9 tests): stepOutAssertions only handled Assertions (AllOf/AnyOf) on the stack, not Not. When </not> triggered stepOutAssertions with a Not(Some(...)) on top, it threw "Unable to associate non-assertions object". Also consolidated the duplicate ALL_OF end-element handler — ALL_OF, ANY_OF, and NOT are now handled in a single case. 2. serializationMatches query building (4 tests): The method embedded the expected regex in a backtick string constructor ``[...]``, but patterns containing <? (e.g., <?xml) trigger an eXist parser bug where <? is interpreted as a processing instruction start inside the string constructor (XPST0003). Fixed by passing the regex and flags as external variables. Note: The eXist parser bug with <? inside backtick string constructors should be investigated separately — ``[<?xml]`` should be valid XQuery. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Bug 1: Not(None) inside AllOf/AnyOf — When <not> is a child of <all-of> or <any-of>, addAssertion() appended Not() to the Assertions list, then appended the inner assertion as a sibling instead of nesting it inside the Not. Fix: check if the last element of an Assertions container is Not(None) and fill it with the new assertion. Bug 2: Serialization options lost after context.reset() — The runner called the 3-arg XQuery.execute() which passes null for outputProperties. eXist's execute() calls context.checkOptions(null) (no-op) then context.reset(), clearing declared serialization options before the runner could read them. Fix: pass a Properties object to execute() so eXist extracts options BEFORE resetting the context. This restores declare option output:method "html" etc. for serialization tests. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- Add --timeout flag (default 180s, was hardcoded 300s) for faster recovery when BrokerPool shutdown hangs - Kill lingering Java processes after each batch via pkill -9 matching the batch's unique exist.home directory - Adjust jstack capture timing relative to the configurable timeout The FLWOR fix increased rd parser test execution by ~4,483 tests, overwhelming the batch runner with BrokerPool shutdown hangs on 13/13 batches. Shorter timeout + process cleanup allows the runner to recover and continue. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

180s was too short for rd parser batches — the rd parser legitimately takes longer on some test sets (FLWOR parsing complexity), causing 32/32 batches to timeout during test execution. Keep the configurable --timeout flag and process cleanup, just set the default higher. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Exit code 1 from the XQTS runner means "some test failures found" — normal expected behavior. Only count timeout (124/137) and crashes (exit > 1, not 255) as batch failures. Exit 255 is a runner error (non-fatal, produces partial results). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

joewiz · 2026-04-13T19:42:54Z

[This response was co-authored with Claude Code. -Joe]

Closing in favour of PR #49 (feature/saxon-12-runner), which is a strict superset of this branch — it contains all commits here plus the Saxon 12 upgrade. PR #49's description has been updated to cover the full scope of both PRs.

joewiz mentioned this pull request Mar 5, 2026

Implement EXPath Binary Module 4.0 eXist-db/exist#6101

Closed

3 tasks

line-o self-requested a review March 9, 2026 22:58

joewiz force-pushed the feature/qt4-xquery-update branch from f437c59 to 656bc51 Compare March 11, 2026 07:39

adamretter reviewed Mar 11, 2026

View reviewed changes

joewiz marked this pull request as draft March 11, 2026 13:19

joewiz force-pushed the feature/qt4-xquery-update branch 3 times, most recently from 3999a07 to c8ddd90 Compare March 14, 2026 03:51

joewiz changed the title ~~Add QT4 test suite and XQuery Update test support~~ Add QT4/FTTS test suites, XQuery Update support, and assertion reliability fixes Mar 14, 2026

joewiz marked this pull request as ready for review March 14, 2026 23:53

joewiz force-pushed the feature/qt4-xquery-update branch from c8ddd90 to c137d86 Compare March 15, 2026 03:35

joewiz mentioned this pull request Mar 15, 2026

Sandpit directory structure doesn't support relative parent paths #47

Open

duncdrum approved these changes Mar 16, 2026

View reviewed changes

duncdrum self-requested a review March 16, 2026 12:23

line-o reviewed Mar 16, 2026

View reviewed changes

joewiz and others added 12 commits March 16, 2026 15:31

[bugfix] Fix XMLUnit comparison and whitespace handling in assertions

293ddbc

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

joewiz and others added 6 commits March 16, 2026 15:31

[feature] Add stall detection watchdog with shutdown timeout

6f3592d

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

joewiz force-pushed the feature/qt4-xquery-update branch from 523c0cb to 5f31a1e Compare March 16, 2026 19:31

joewiz and others added 6 commits March 19, 2026 19:29

Revert "[bugfix] Normalize old map syntax (:=) in XQTS assertion and …

c8eef45

…query expressions" This reverts commit a590bcb.

joewiz and others added 7 commits March 26, 2026 16:04

joewiz mentioned this pull request Apr 6, 2026

Extend XQTS runner: QT4/FTTS/Update suites, assertion fixes, batch runner, Saxon 12 #49

Open

10 tasks

line-o mentioned this pull request Apr 13, 2026

release a v7 compatible xqts runner #43

Open

2 tasks

joewiz closed this Apr 13, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add QT4/FTTS test suites, XQuery Update support, and assertion reliability fixes#45

Add QT4/FTTS test suites, XQuery Update support, and assertion reliability fixes#45
joewiz wants to merge 32 commits intoeXist-db:developfrom
joewiz:feature/qt4-xquery-update

joewiz commented Mar 5, 2026 •

edited

Loading

Uh oh!

adamretter left a comment

Uh oh!

joewiz commented Mar 11, 2026 •

edited

Loading

Uh oh!

joewiz commented Mar 14, 2026 •

edited

Loading

Uh oh!

line-o left a comment

Uh oh!

line-o Mar 9, 2026

Uh oh!

line-o Mar 16, 2026

Uh oh!

line-o Mar 11, 2026

Uh oh!

line-o Mar 16, 2026

Uh oh!

line-o Mar 11, 2026

Uh oh!

line-o Mar 16, 2026

Uh oh!

adamretter commented Mar 25, 2026 •

edited

Loading

Uh oh!

joewiz commented Apr 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants


		case object AssertFalse extends Assertion

		/** Assertion for "Inspect" comparisons that always passes (requires manual review). */

Uh oh!

Conversation

joewiz commented Mar 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Performance Improvements

Commits (20)

1. Core test suite support (3 commits)

2. Build & infrastructure (2 commits)

3. Sandpit support (1 commit)

4. Assertion reliability fixes (9 commits)

5. Completion detection & shutdown (2 commits)

6. Batch runner (3 commits)

Usage

Test Plan

Uh oh!

adamretter left a comment

Choose a reason for hiding this comment

Uh oh!

joewiz commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

joewiz commented Mar 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

line-o left a comment

Choose a reason for hiding this comment

Uh oh!

line-o Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

line-o Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

line-o Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

line-o Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

line-o Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

line-o Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

adamretter commented Mar 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

joewiz commented Apr 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

joewiz commented Mar 5, 2026 •

edited

Loading

joewiz commented Mar 11, 2026 •

edited

Loading

joewiz commented Mar 14, 2026 •

edited

Loading

adamretter commented Mar 25, 2026 •

edited

Loading