[#13800] feat(policy): Maintenance execution peers, BuiltInType registry, and minIntervalMs defaults by lasdf1234 · Pull Request #13801 · apache/gravitino

lasdf1234 · 2026-10-13T02:25:16Z

What changes were proposed in this pull request?

Domain + DTO slice of Epic #13764 / #13800.

Carry TMS execution peers on AbstractExecutablePolicyContent (not universal PolicyContent):
- timeTrigger — cron string (syntax not validated in api)
- commitTrigger — boolean
- minIntervalMs, jobOptions, updaterOptions
Four Iceberg maintenance contents extend the abstract type; attach peers via construction-time PolicyExecutionSpec
Shared peer checks in AbstractExecutablePolicyContent.validate(); universal PolicyContent.validate() only checks supportedObjectTypes
Orphan content rejects commitTrigger == true
MaintenancePolicyDefinitions registry keyed by Policy.BuiltInType for per-type minIntervalMs server defaults; resolve() rejects negative policy values
Iceberg PolicyContentDTO + DTOConverters round-trip peers so REST alter does not drop them
Design doc §5.0: policy/BuiltInType identity vs scheduler task kinds (policy-expand / cron-job / commit-job)

Out of scope (follow-ups):

Sensitive-key rejection for option bags at server create/alter
End-to-end cron parse + timezone on the TMS / scheduler registration path
OpenAPI / user-facing policy docs polish ([#13815] feat(policy): REST/DTO/OpenAPI round-trip for TMS content peers #13814 / [Subtask] TMS: OpenAPI / user docs for content peers #13815)
Nearest-policy resolver, auth overlay

Why are the changes needed?

TMS needs shared trigger / cooldown / option-bag concepts without freezing them onto every PolicyContent. Server defaults cover omitted minIntervalMs. BuiltInType stays the single maintenance identity (no parallel task-type enum).

Fix: #13800

Does this PR introduce any user-facing change?

Yes.

New optional server config keys (with defaults):

gravitino.maintenance.compaction.minIntervalMs (3600000)
gravitino.maintenance.manifest-rewrite.minIntervalMs (3600000)
gravitino.maintenance.snapshot-expiry.minIntervalMs (3600000)
gravitino.maintenance.orphan-cleanup.minIntervalMs (86400000)

Optional JSON peer fields on Iceberg maintenance policy contents (REST/DTO):

{
  "timeTrigger": "0 0 2 * * ?",
  "commitTrigger": true,
  "minIntervalMs": 3600000,
  "jobOptions": {},
  "updaterOptions": {}
}

How was this patch tested?

./gradlew :api:test --tests 'org.apache.gravitino.policy.*' \
  :common:test --tests 'org.apache.gravitino.dto.policy.*' \
  :core:test --tests 'org.apache.gravitino.maintenance.policy.TestMaintenanceMinIntervalConfigs' \
  -PskipITs

…cy content Add TableMaintenanceContent with schedule, minIntervalMs, jobOptions, and updateOptions; wire the four Iceberg maintenance contents and PolicyContents factories; validate via TableMaintenancePolicies on PolicyEntity. Co-authored-by: Cursor <cursoragent@cursor.com>

api javadoc cannot resolve core's PolicyEntity; use {@code} instead so :api:javadoc passes in CI. Co-authored-by: Cursor <cursoragent@cursor.com>

…hedule triggers Move timeTrigger/eventTrigger/minIntervalMs/jobOptions/updateOptions onto PolicyContent as shared concepts, and drop the combined schedule object. Co-authored-by: Cursor <cursoragent@cursor.com>

Keep shared TimeTrigger/EventTrigger/PolicyExecutionFields on PolicyContent; remove TableMaintenanceContent, TaskType, and Policies without wiring peers onto Iceberg contents yet. Co-authored-by: Cursor <cursoragent@cursor.com>

…erver defaults Register gravitino.maintenance.task.*.minIntervalMs ConfigEntries with 1h/1d defaults so cooldown can be read from gravitino.conf without TaskType. Co-authored-by: Cursor <cursoragent@cursor.com>

roryqi · 2026-10-14T12:26:06Z

+    }
+
+    public Map<String, String> jobOptions() {
+      return jobOptions == null ? Collections.emptyMap() : jobOptions;


jobOptions() returns the DTO's mutable backing map, unlike rewriteOptions() above, which returns an unmodifiable defensive copy. A caller can therefore mutate the DTO after validation and also change its Lombok-generated equality/hash state. Please return an immutable defensive copy here and for updateOptions() in all four DTOs. Centralizing these fields in an immutable execution-spec DTO would also remove this repetition.

Agreed — all four Iceberg execution DTOs now return PolicyExecutionFields.copyOptions(...) for jobOptions() / updateOptions() (unmodifiable defensive copies, same idea as rewriteOptions()). Added a regression test that mutating the returned maps throws.

roryqi · 2026-10-14T12:26:09Z

    }

+    @Nullable
+    public String timeTrigger() {


These five new public accessors have no Javadocs, and the same pattern is repeated in the other execution-capable DTOs. Please document the new public API methods (including null/default semantics), or centralize them behind the proposed execution-spec abstraction.

Agreed — centralized docs on PolicyContentDTO.ExecutionPeersDTO (null/empty semantics for the five peers). The four Iceberg DTOs implement that interface so the public accessors share one Javadoc contract.

roryqi

Additional review notes:

The design document still defines triggers under policy_version_info.content.schedule and shows schedule.onCommit / schedule.crontab, while this implementation's wire contract is flat commitTrigger / timeTrigger. Please make the design document and the actual JSON contract consistent.
The same section says automated maintenance must have at least one trigger and that create/alter rejects credential-shaped option keys. Neither rule is enforced by this PR. If those are intentionally deferred, the document should clearly mark them as future behavior rather than describing them as current guarantees.
Please also make the cron syntax/example consistent with the scheduler contract when that validation is wired in.

The main blocking concern is the mutable, unchecked withExecutionFields API called out inline. An immutable PolicyExecutionSpec composed into executable policy contents would address that cleanly.

…ecutable peers Replace mutable withExecutionFields with construction-time PolicyExecutionSpec on ExecutablePolicyContent. Option map values are omitted from toString/DTO ToString to avoid leaking credentials in logs. Co-authored-by: Cursor <cursoragent@cursor.com>

Return unmodifiable option-map copies, document peers via ExecutionPeersDTO, and cover mutation attempts in TestPolicyDTO. Co-authored-by: Cursor <cursoragent@cursor.com>

Use commitTrigger/timeTrigger instead of content.schedule.*; drop the required-trigger rule; keep credential-key rejection as design intent. Co-authored-by: Cursor <cursoragent@cursor.com>

lasdf1234 · 2026-10-14T13:00:12Z

Thanks for the additional review notes — status:

Blocking withExecutionFields — done in recent pushes: immutable PolicyExecutionSpec + ExecutablePolicyContent.executionSpec(), construction-time only; option values omitted from toString / DTO @ToString; DTO option maps return unmodifiable copies + ExecutionPeersDTO Javadoc.
Design doc vs wire contract — updated design-docs/table-maintenance-service-design.md to flat peers (commitTrigger / timeTrigger / minIntervalMs / jobOptions / …), not content.schedule.*. Cron examples note that syntax is owned by the TMS / db-scheduler registration path.
“At least one trigger” — removed from the design. Triggers are optional: a policy may set commitTrigger, timeTrigger, both, or neither. We do not want create/alter to require a trigger; no-trigger policies simply are not enrolled in automated expand/commit until a trigger is added.
Credential-shaped option-key rejection — still the design intent (secrets must not live in policy content; create/alter should reject credential-shaped keys in option bags). Not implemented in this PR; that enforcement lands in a follow-up on the server create/alter boundary. Auth stays cluster-static in gravitino.conf in the meantime.

Keep flat commitTrigger/timeTrigger peers; adopt scheduled_*_tasks wording from main. Co-authored-by: Cursor <cursoragent@cursor.com>

roryqi · 2026-10-15T02:00:18Z

+  private final Map<String, String> jobOptions;
+  private final Map<String, String> updateOptions;
+
+  private PolicyExecutionSpec(


PolicyExecutionSpec is now serialized as the executionSpec field of every executable policy content, but this type has only a private constructor and no Jackson creator/default constructor. POConverters.fromPolicyPO() therefore cannot read the stored content back; the current :core:test and Maintenance IT failures both report Cannot construct instance of PolicyExecutionSpec. Please make the persisted form deserializable (for example with an appropriate @JsonCreator/property mapping or a custom persistence representation) and add a POConverters round-trip test for maintenance policy content.

Fixed — went with @JsonCreator on PolicyExecutionSpec.of(...) plus @JsonUnwrapped on AbstractExecutablePolicyContent.executionSpec, so peers stay flat on the wire (timeTrigger / commitTrigger / …) and POConverters.fromPolicyPO() can rebuild them.

Also added TestPOConverters.testFromPolicyPOIcebergCompactionWithExecutionPeers to cover the persistence round-trip (and assert the JSON is not nested under executionSpec).

@jsoncreator

…izable for POConverters Add @jsoncreator on PolicyExecutionSpec.of and @JsonUnwrapped on the content field so flat peer keys round-trip through JsonUtils.anyFieldMapper. Co-authored-by: Cursor <cursoragent@cursor.com>

roryqi · 2026-10-15T08:17:01Z

+ */
+public abstract class AbstractExecutablePolicyContent implements ExecutablePolicyContent {
+
+  @JsonUnwrapped private final PolicyExecutionSpec executionSpec;


Please do not introduce @JsonUnwrapped here. Gravitino currently has no precedent for this annotation, and it couples the public API domain model to a specific persistence JSON layout. Please follow the existing DTO/converter pattern: keep PolicyExecutionSpec Jackson-independent, flatten the execution fields explicitly in PolicyContentDTO or the persistence representation, and reconstruct the spec in DTOConverters or POConverters. The new Jackson dependency in the api module should then be removed as well.

Thanks — addressed.

Removed @JsonUnwrapped and Jackson usage from api (PolicyExecutionSpec is Jackson-independent again).

Flat peer fields live on AbstractExecutablePolicyContent for the existing POConverters content JSON layout (same flat keys as the DTOs); executionSpec() reconstructs the in-memory spec.

Dropped the jackson.annotations dependency from the api module.

roryqi · 2026-10-15T08:17:12Z

  /** Represents a typed iceberg compaction policy content DTO. */
  @EqualsAndHashCode
-  @ToString
+  @ToString(exclude = {"jobOptions", "updateOptions"})


The redaction is incomplete: rewriteOptions is still rendered by both this Lombok-generated toString() and IcebergDataCompactionContent.toString(). Sensitive-key rejection is explicitly deferred, and the design now includes rewriteOptions among the bags that must reject credential-shaped keys, so an accidentally supplied credential can still be exposed in logs. Please exclude or redact rewriteOptions as well (keys/count only, no values).

Good catch — fixed.

IcebergDataCompactionContent.toString() now prints rewriteOptionsKeys=... only (no values), consistent with jobOptions / updateOptions.

DTO @ToString excludes rewriteOptions as well (same as the other option bags).

Sensitive-key rejection on create/alter remains the planned follow-up.

roryqi · 2026-10-15T08:17:15Z

+      @JsonProperty("minIntervalMs") @Nullable Long minIntervalMs,
+      @JsonProperty("jobOptions") @Nullable Map<String, String> jobOptions,
+      @JsonProperty("updateOptions") @Nullable Map<String, String> updateOptions) {
+    if (!PolicyExecutionFields.hasAny(


hasAny treats false as unset, so PolicyExecutionSpec.of(null, false, ...) returns EMPTY and changes false to null. But if any other peer is present, the same false is retained. This makes JSON round trips and equals/hashCode behavior depend on unrelated fields. Please either normalize false to null unconditionally, or treat every non-null Boolean as an explicitly supplied value.

Agreed — fixed by treating every non-null Boolean as an explicit value (including false).

PolicyExecutionFields.hasAny / PolicyExecutionSpec.of now retain lone false instead of collapsing to EMPTY/null.

Clarified DTO Javadoc: null = unset, false = explicitly disabled, true = enabled.

…, fix false peers Store flat execution peer fields on content for persistence without Jackson in api; treat non-null commitTrigger (including false) as explicitly set; omit rewriteOptions values from toString paths. Co-authored-by: Cursor <cursoragent@cursor.com>

…TO Javadoc Co-authored-by: Cursor <cursoragent@cursor.com>

lasdf1234 · 2026-10-15T08:51:05Z

Thanks @roryqi for the follow-up review — latest push addresses the three new notes:

No @JsonUnwrapped — PolicyExecutionSpec is Jackson-independent again; flat peers on content + DTO/converter reconstruction; removed jackson.annotations from api.
rewriteOptions toString redaction — keys only on the API type; excluded from DTO @ToString (credential rejection still follow-up).
commitTrigger=false consistency — non-null Boolean is always retained; Javadoc clarified (null unset / false explicit off).

Please take another look when you have a chance.

roryqi · 2026-10-15T11:04:19Z

+  @Nullable private final Boolean commitTrigger;
+  @Nullable private final Long minIntervalMs;
+  private final Map<String, String> jobOptions;
+  private final Map<String, String> updateOptions;


updateOptions or updaterOptions?

Renamed to `updaterOptions` (JSON key + API) to align with runtime `updater_options` / `updaterOptions()`. Design doc updated in the same commit.

Got. Rename to updaterOptions.

roryqi

Please do not flatten PolicyExecutionSpec into the domain model and every concrete DTO just to match the persisted/wire JSON shape. Follow the existing JsonUtils.DistributionSerializer / DistributionDeserializer pattern instead: keep execution settings as an immutable composed value object, and use a custom serializer/deserializer in common to map its fields to/from the flat JSON keys (timeTrigger, commitTrigger, minIntervalMs, jobOptions, and updateOptions). That keeps Jackson and persistence-layout concerns out of api, avoids duplicating the same five fields/accessors across all executable policy DTOs, and preserves the current flat JSON contract. Please add REST DTO and POConverters round-trip coverage for each executable built-in policy type.

…Options Align the policy execution peer with runtime updater_options / updaterOptions naming used by the update-stats path, and update the TMS design doc. Co-authored-by: Cursor <cursoragent@cursor.com>

…ap flat JSON via SerDe Avoid flattening execution peers across domain/DTO types. Persist and wire flat keys through ExecutablePolicyContentSerde, and add REST/POConverters round-trips for each executable built-in policy. Co-authored-by: Cursor <cursoragent@cursor.com>

lasdf1234 · 2026-10-15T12:02:53Z

Split for review / merge into `branch-tms-scheduler`:

[#13800] feat(policy): Maintenance execution peers on Iceberg contents #13885 — execution peers (domain / DTO / SerDe)
[#13800] feat(policy): BuiltInType minIntervalMs defaults registry #13886 — BuiltInType `minIntervalMs` defaults registry

Closing this PR in favor of the split. Original head `feature/tms-policy-peers-13800` is preserved on the fork.

lasdf1234 · 2026-10-15T12:02:56Z

Superseded by split PRs #13885 and #13886 (base: branch-tms-scheduler).

#13885) ### What changes were proposed in this pull request? Split from #13801 (1/2). **Domain** execution peers for Epic #13764 / #13800. - `PolicyExecutionSpec` / `ExecutablePolicyContent` / `PolicyExecutionFields` - Four Iceberg maintenance contents carry peers at construction - TMS design notes on peers / `BuiltInType` identity **Follow-up (stack):** #13888 / #13887 — wire/DTO/SerDe + `minIntervalMs` registry. ### Why are the changes needed? TMS needs shared trigger / cooldown / option-bag concepts without freezing them onto every `PolicyContent`. Fix: #13800 ### Does this PR introduce _any_ user-facing change? API/domain surface for optional peers on Iceberg maintenance contents (REST wire lands in #13887). ### How was this patch tested? ```bash ./gradlew :api:test --tests 'org.apache.gravitino.policy.*' -PskipITs ``` --------- Co-authored-by: Cursor <cursoragent@cursor.com>

…s defaults (#13887) ### What changes were proposed in this pull request? Split from #13801 (2/2). **Stack on #13885** (merge that first). Tracked by #13888. Incremental scope (~1.5k vs #13885 ~1.1k): - Flat JSON mapping via `ExecutablePolicyContentSerde` + Iceberg `PolicyContentDTO` / `DTOConverters` - REST + `POConverters` round-trips for each executable built-in type - `MaintenancePolicyDefinitions` + per-type `gravitino.maintenance.*.minIntervalMs` + conf/docs Until #13885 merges, the GitHub file list includes domain files from the stack base; review the **second commit** / `common`+`core/maintenance`+`conf`+`docs` paths. ### Why are the changes needed? Preserve flat wire/persistence JSON without flattening Spec into every type; server defaults for omitted `minIntervalMs`. Fix: #13888 ### Does this PR introduce _any_ user-facing change? Yes — optional JSON peer fields on Iceberg maintenance policy contents, and: - `gravitino.maintenance.compaction.minIntervalMs` (`3600000`) - `gravitino.maintenance.manifest-rewrite.minIntervalMs` (`3600000`) - `gravitino.maintenance.snapshot-expiry.minIntervalMs` (`3600000`) - `gravitino.maintenance.orphan-cleanup.minIntervalMs` (`86400000`) ### How was this patch tested? ```bash ./gradlew :common:test --tests 'org.apache.gravitino.dto.policy.*' \ :core:test --tests 'org.apache.gravitino.storage.relational.utils.TestPOConverters' \ --tests 'org.apache.gravitino.maintenance.policy.TestMaintenanceMinIntervalConfigs' \ -PskipITs ``` --------- Co-authored-by: Cursor <cursoragent@cursor.com>

lasdf1234 self-assigned this Oct 13, 2026

lasdf1234 force-pushed the feature/tms-policy-peers-13800 branch from 9c48d64 to 33f296b Compare October 13, 2026 02:28

lasdf1234 changed the title ~~[#13800] feat(policy): Attach TMS peer fields on table-maintenance content~~ [#13800] feat(policy): Add TableMaintenanceContent peers and validation Oct 13, 2026

lasdf1234 mentioned this pull request Oct 13, 2026

[#13800] feat(policy): REST/entity round-trip for TMS peer fields #13802

Closed

lasdf1234 force-pushed the feature/tms-policy-peers-13800 branch 3 times, most recently from 1c6985e to f7e2976 Compare October 13, 2026 03:01

lasdf1234 changed the title ~~[#13800] feat(policy): Add TableMaintenanceContent peers and validation~~ [#13800] feat(policy): Add TableMaintenanceContent peers on maintenance contents Oct 13, 2026

lasdf1234 force-pushed the feature/tms-policy-peers-13800 branch from f7e2976 to ea6e1ad Compare October 13, 2026 03:22

lasdf1234 changed the title ~~[#13800] feat(policy): Add TableMaintenanceContent peers on maintenance contents~~ [#13800] feat(policy): TMS MaintenancePeerFields domain model Oct 13, 2026

lasdf1234 changed the title ~~[#13800] feat(policy): TMS MaintenancePeerFields domain model~~ [#13800] feat(policy): TMS peer fields on policy content (domain + REST) Oct 13, 2026

lasdf1234 force-pushed the feature/tms-policy-peers-13800 branch from 7f3a26c to 04e8141 Compare October 13, 2026 07:47

lasdf1234 changed the title ~~[#13800] feat(policy): TMS peer fields on policy content (domain + REST)~~ [#13800] feat(policy): Add TableMaintenanceContent peers on Iceberg contents Oct 13, 2026

lasdf1234 mentioned this pull request Oct 13, 2026

[#13815] feat(policy): REST/DTO/OpenAPI round-trip for TMS content peers #13814

Draft

lasdf1234 force-pushed the feature/tms-policy-peers-13800 branch from 04e8141 to e8f52ec Compare October 13, 2026 07:49

lasdf1234 changed the title ~~[#13800] feat(policy): Add TableMaintenanceContent peers on Iceberg contents~~ [#13800] feat(policy): Add TMS fields on table-maintenance policy content Oct 13, 2026

This was referenced Oct 13, 2026

[EPIC] TMS: Policy content schema #13764

Closed

[Subtask] TMS: Domain PolicyExecutionSpec and executable peers #13800

Closed

lasdf1234 force-pushed the feature/tms-policy-peers-13800 branch from e8f52ec to 851b289 Compare October 13, 2026 07:56

lasdf1234 requested a review from roryqi October 13, 2026 08:02

This was referenced Oct 13, 2026

[Subtask] TMS: OpenAPI / user docs for content peers #13815

Open

[#13779] feat(policy): Add TMS nearest-policy and minIntervalMs resolution #13817

Open

[Subtask] TMS: Nearest-policy selection and minIntervalMs resolution #13779

Open

lasdf1234 and others added 2 commits October 13, 2026 17:47

[apache#13800] fix(policy): Drop cross-module PolicyEntity javadoc link

7b24310

api javadoc cannot resolve core's PolicyEntity; use {@code} instead so :api:javadoc passes in CI. Co-authored-by: Cursor <cursoragent@cursor.com>

[apache#13800] refactor(policy): Generalize execution peers; split sc…

0815284

…hedule triggers Move timeTrigger/eventTrigger/minIntervalMs/jobOptions/updateOptions onto PolicyContent as shared concepts, and drop the combined schedule object. Co-authored-by: Cursor <cursoragent@cursor.com>

lasdf1234 changed the title ~~[#13800] feat(policy): Add TMS fields on table-maintenance policy content~~ [#13800] feat(policy): Add shared policy execution peers (triggers + options) Oct 13, 2026

lasdf1234 and others added 2 commits October 13, 2026 20:43

[apache#13800] feat(policy): Add per-type maintenance minIntervalMs s…

64a3461

…erver defaults Register gravitino.maintenance.task.*.minIntervalMs ConfigEntries with 1h/1d defaults so cooldown can be read from gravitino.conf without TaskType. Co-authored-by: Cursor <cursoragent@cursor.com>

lasdf1234 changed the title ~~[#13800] feat(policy): Add shared policy execution peers (triggers + options)~~ [#13800] feat(policy): Add shared execution peers and minIntervalMs defaults Oct 13, 2026

roryqi reviewed Oct 14, 2026

View reviewed changes

lasdf1234 and others added 3 commits October 14, 2026 20:51

[apache#13800] fix(policy): Harden Iceberg DTO execution peer accessors

4edb316

Return unmodifiable option-map copies, document peers via ExecutionPeersDTO, and cover mutation attempts in TestPolicyDTO. Co-authored-by: Cursor <cursoragent@cursor.com>

[apache#13800] docs(tms): Align design triggers with flat wire peers

55c215e

Use commitTrigger/timeTrigger instead of content.schedule.*; drop the required-trigger rule; keep credential-key rejection as design intent. Co-authored-by: Cursor <cursoragent@cursor.com>

[apache#13800] docs(tms): Resolve design-doc merge conflict with main

ef66637

Keep flat commitTrigger/timeTrigger peers; adopt scheduled_*_tasks wording from main. Co-authored-by: Cursor <cursoragent@cursor.com>

lasdf1234 requested a review from roryqi October 14, 2026 13:04

roryqi reviewed Oct 15, 2026

View reviewed changes

lasdf1234 requested a review from roryqi October 15, 2026 07:08

roryqi reviewed Oct 15, 2026

View reviewed changes

lasdf1234 and others added 2 commits October 15, 2026 16:35

[apache#13800] docs(policy): Clarify commitTrigger null vs false in D…

5c12c07

…TO Javadoc Co-authored-by: Cursor <cursoragent@cursor.com>

roryqi reviewed Oct 15, 2026

View reviewed changes

lasdf1234 and others added 2 commits October 15, 2026 19:12

[apache#13800] refactor(policy): Rename updateOptions peer to updater…

5eb4d1d

…Options Align the policy execution peer with runtime updater_options / updaterOptions naming used by the update-stats path, and update the TMS design doc. Co-authored-by: Cursor <cursoragent@cursor.com>

This was referenced Oct 15, 2026

[#13800] feat(policy): Maintenance execution peers on Iceberg contents #13885

Merged

[#13800] feat(policy): BuiltInType minIntervalMs defaults registry #13886

Closed

lasdf1234 closed this Oct 15, 2026

lasdf1234 mentioned this pull request Oct 15, 2026

[#13800] feat(policy): Flat peer SerDe, DTO round-trips, minIntervalMs defaults #13887

Merged

Conversation

lasdf1234 commented Oct 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

roryqi left a comment

Choose a reason for hiding this comment

Uh oh!

lasdf1234 commented Oct 14, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lasdf1234 commented Oct 15, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

roryqi left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lasdf1234 commented Oct 15, 2026

Uh oh!

lasdf1234 commented Oct 15, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

lasdf1234 commented Oct 13, 2026 •

edited

Loading

roryqi left a comment •

edited

Loading