MCPcopy Create free account

hub / github.com/PerpetualSoftware/pad / functions

Functions28,840 in github.com/PerpetualSoftware/pad

FunctionTestPadItemBulkUpdate_ForcePassesThroughToCLI
(t *testing.T)
internal/mcp/catalog_item_force_test.go:69
FunctionTestPadItemBulkUpdate_TranslatesRefsArray
TestPadItemBulkUpdate_TranslatesRefsArray verifies the catalog's `refs: array<string>` param becomes the CLI's repeatable positional `ref` (one positi
internal/mcp/catalog_item_test.go:203
FunctionTestPadItemCreate_FieldsObjectApplies
TestPadItemCreate_FieldsObjectApplies covers the create leg of the same contract, including merging alongside an existing `field` array.
internal/mcp/catalog_item_fields_test.go:115
FunctionTestPadItemExport_AgentOutputPassesStrictGate
TestPadItemExport_AgentOutputPassesStrictGate covers the gap that the strict input gate runs BEFORE the action handlers, and `output` is neither schem
internal/mcp/catalog_item_fields_test.go:390
FunctionTestPadItemExport_ForcesStdout
TestPadItemExport_ForcesStdout verifies action=export injects the CLI's stdout sink (`--output -`) so the artifact bytes come back as the tool result
internal/mcp/catalog_item_artifact_test.go:15
FunctionTestPadItemExport_MissingRef
TestPadItemExport_MissingRef returns a structured error rather than dispatching with an empty ref.
internal/mcp/catalog_item_artifact_test.go:71
FunctionTestPadItemExport_OverridesAgentOutput
TestPadItemExport_OverridesAgentOutput confirms an agent-supplied `output` (a local path the MCP host can't see) is overridden with `-` so export alwa
internal/mcp/catalog_item_artifact_test.go:46
FunctionTestPadItemHistory_AppliesDefaultLimit
A bare history call must be bounded. Asserting the CLI args covers the exec transport at the same time: the default only reaches stdio because BuildCL
internal/mcp/dispatch_http_history_bounds_test.go:43
FunctionTestPadItemHistory_ClampsOversizedLimit
(t *testing.T)
internal/mcp/dispatch_http_history_bounds_test.go:52
FunctionTestPadItemHistory_HonorsInRangeLimit
(t *testing.T)
internal/mcp/dispatch_http_history_bounds_test.go:60
FunctionTestPadItemImport_MissingArtifact
TestPadItemImport_MissingArtifact returns a structured error and doesn't dispatch when no artifact body is supplied.
internal/mcp/catalog_item_artifact_test.go:157
FunctionTestPadItemImport_TempFileCleanedUp
TestPadItemImport_TempFileCleanedUp confirms the temp file is removed after dispatch returns — no artifact litter left on disk.
internal/mcp/catalog_item_artifact_test.go:134
FunctionTestPadItemImport_WritesTempFileAndDispatches
TestPadItemImport_WritesTempFileAndDispatches verifies action=import spills the `artifact` body to a temp file and dispatches `item import <tmpfile>`
internal/mcp/catalog_item_artifact_test.go:97
FunctionTestPadItemLink_DispatchTable
TestPadItemLink_DispatchTable exercises every link_type ↔ cmdPath mapping in itemLinkRoutes for both action=link (create) and action=unlink (remove).
internal/mcp/catalog_item_test.go:17
FunctionTestPadItemLink_ForwardsAuxFields
TestPadItemLink_ForwardsAuxFields confirms that non-link fields (workspace, format) flow through to the dispatcher unchanged. The rename should ONLY t
internal/mcp/catalog_item_test.go:293
FunctionTestPadItemLink_MissingLinkType
TestPadItemLink_MissingLinkType returns a structured error listing the valid options. Ensures the agent gets enough signal to retry with a correct val
internal/mcp/catalog_item_test.go:92
FunctionTestPadItemLink_MissingRefOrTarget
TestPadItemLink_MissingRefOrTarget covers the other two required inputs. Failing fast at the action handler keeps BuildCLIArgs from emitting a confusi
internal/mcp/catalog_item_test.go:155
FunctionTestPadItemLink_UnknownLinkType
TestPadItemLink_UnknownLinkType rejects values outside the route table. Must surface what's valid so consumers can correct.
internal/mcp/catalog_item_test.go:125
FunctionTestPadItemList_ClampsOversizedLimit
TestPadItemList_ClampsOversizedLimit verifies an agent-supplied limit above the hard max is clamped down to mcpItemListMaxLimit rather than forwarded
internal/mcp/catalog_item_list_test.go:42
FunctionTestPadItemList_FieldsRefused
TestPadItemList_FieldsRefused: `fields` is a create/update writer. On any other action it would be silently dropped by BuildCLIArgs — the exact failur
internal/mcp/catalog_item_fields_test.go:324
FunctionTestPadItemList_ForwardsUnparentedToLocalCLI
(t *testing.T)
internal/mcp/catalog_item_list_test.go:105
FunctionTestPadItemList_InjectsDefaultLimit
TestPadItemList_InjectsDefaultLimit verifies action=list adds a default `--limit` (mcpItemListDefaultLimit) when the agent didn't ask for one, so a ba
internal/mcp/catalog_item_list_test.go:13
FunctionTestPadItemList_RejectsParentWithUnparented
(t *testing.T)
internal/mcp/catalog_item_list_test.go:88
FunctionTestPadItemList_RespectsInRangeLimit
TestPadItemList_RespectsInRangeLimit verifies a reasonable agent-supplied limit passes through untouched. TASK-2000.
internal/mcp/catalog_item_list_test.go:68
FunctionTestPadItemUpdate_AliasGuardDoesNotDependOnPromotion
...and the guard must not depend on `parent` being a promoted key. This is the mutation the both-aliases gap would have become real through: drop `par
internal/mcp/catalog_item_fields_test.go:1060
FunctionTestPadItemUpdate_AliasPairsRefusedWithoutFieldsObject
TestPadItemUpdate_AliasPairsRefusedWithoutFieldsObject: alias detection must reach the no-`fields` case too (BUG-2850). The canonical-pass restructur
internal/mcp/catalog_item_fields_test.go:1558
FunctionTestPadItemUpdate_BlankCompatIDIsAClearAndStillConflicts
...and the COMPAT ID KEYS are excluded from that rule, because for them an empty string is not absence — it is a CLEAR to NULL, the deliberate v0.16 s
internal/mcp/catalog_item_fields_test.go:1365
FunctionTestPadItemUpdate_BlankTopLevelParamDoesNotBlockFields
TestPadItemUpdate_BlankTopLevelParamDoesNotBlockFields: a zero-filled optional param must not refuse the `fields` answer to the same question (BUG-285
internal/mcp/catalog_item_fields_test.go:1326
FunctionTestPadItemUpdate_BothAliasesInOneFieldsObject
TestPadItemUpdate_BothAliasesInOneFieldsObject: a suspected gap was REFUTED — this pair was already refused — but it was refused by ACCIDENT, and the
internal/mcp/catalog_item_fields_test.go:1036
FunctionTestPadItemUpdate_CanonicalCompatDuplicateStillCollapses
...and a CANONICAL equal duplicate still collapses, so the refusal is about the padding and not about the collision.
internal/mcp/catalog_item_fields_test.go:1906
FunctionTestPadItemUpdate_CanonicalEqualDuplicateIsUntouched
...and an equal duplicate written canonically is left exactly as it was — the same assertion as before BUG-2870, when its point was that the re-emissi
internal/mcp/catalog_item_fields_test.go:950
FunctionTestPadItemUpdate_CompatExceptionNeedsATopLevelValue
TestPadItemUpdate_CompatExceptionNeedsATopLevelValue: the compat-ID exception turns on a TOP-LEVEL value being present, not on the key being a compat
internal/mcp/catalog_item_fields_test.go:2202
FunctionTestPadItemUpdate_CompatIDConflictRefused
TestPadItemUpdate_CompatIDConflictRefused: the v0.16 compat ID params conflict with `fields` like any other key (BUG-2850). `assigned_user_id` / `age
internal/mcp/catalog_item_fields_test.go:1273
FunctionTestPadItemUpdate_CompatIDEqualDuplicateCollapses
...and an EQUAL compat duplicate collapses to one form rather than being refused or sent twice — same disposition as the promoted keys.
internal/mcp/catalog_item_fields_test.go:1297
FunctionTestPadItemUpdate_CompatIDParamsStillAccepted
TestPadItemUpdate_CompatIDParamsStillAccepted: the v0.16 remote- transport clear form (`assigned_user_id: ""` / `agent_role_id: ""`) is documented and
internal/mcp/catalog_item_fields_test.go:365
FunctionTestPadItemUpdate_CompatIDSameNameCollisionRefusedWithoutFields
TestPadItemUpdate_CompatIDSameNameCollisionRefusedWithoutFields: the same-name exemption holds only where the doors provably agree, and the compat IDs
internal/mcp/catalog_item_fields_test.go:1803
FunctionTestPadItemUpdate_DifferingStructuredDuplicateRefused
...and DIFFERING structures still refuse, so the collapse did not turn into "any two structures agree".
internal/mcp/catalog_item_fields_test.go:1612
FunctionTestPadItemUpdate_DuplicateFieldEntriesKeepTheirMultiplicity
TestPadItemUpdate_DuplicateFieldEntriesKeepTheirMultiplicity: two `field` entries naming one key are two sources, and the conflict pass must see both
internal/mcp/catalog_item_fields_test.go:2010
FunctionTestPadItemUpdate_EmptyClearFormsStillConflictWithTheAlias
...and the EFFECTIVE empty forms still conflict, because they are not the same thing. `field:["parent="]` and `fields:{"parent":""}` are the documente
internal/mcp/catalog_item_fields_test.go:1177
FunctionTestPadItemUpdate_EmptyCompatIDIsStillAClearAfterTheNilFix
...and an empty-string compat ID is STILL a clear, so treating nil as absence did not swallow the v0.16 semantics that carve-out exists for.
internal/mcp/catalog_item_fields_test.go:2265
FunctionTestPadItemUpdate_EmptyHierarchyValueInFieldsRefused
TestPadItemUpdate_EmptyHierarchyValueInFieldsRefused: an empty hierarchy value inside `fields` was a SILENT NO-OP, so it is refused (BUG-2850). `fiel
internal/mcp/catalog_item_fields_test.go:1223
FunctionTestPadItemUpdate_EmptyParentIsDroppedNotDispatched
BUG-2941 made the CLI refuse `--parent ""`, and stdio MCP shells out to the CLI — so without dropInertEmptyParent, BuildCLIArgs would turn the catalog
internal/mcp/catalog_item_fields_test.go:2281
FunctionTestPadItemUpdate_EmptyParentParamIsNotAnAliasConflict
TestPadItemUpdate_EmptyParentParamIsNotAnAliasConflict: an empty top-level `parent` is NOT PROVIDED, so it must not collide with `fields.plan` (BUG-28
internal/mcp/catalog_item_fields_test.go:1156
FunctionTestPadItemUpdate_EqualDuplicateDropKeepsOtherFieldEntries
...and an unrelated `field` entry alongside an equal duplicate survives, so the drop removes exactly the duplicate and not the array.
internal/mcp/catalog_item_fields_test.go:760
FunctionTestPadItemUpdate_EqualPromotedDuplicateAppliesOnce
TestPadItemUpdate_EqualPromotedDuplicateAppliesOnce: an equal duplicate on a promoted key must be written ONCE, through its dedicated param — the arra
internal/mcp/catalog_item_fields_test.go:740
FunctionTestPadItemUpdate_EqualStructuredDuplicateCollapses
TestPadItemUpdate_EqualStructuredDuplicateCollapses: two equal STRUCTURES are one unambiguous value, not a conflict (BUG-2850). A regression the cano
internal/mcp/catalog_item_fields_test.go:1595
FunctionTestPadItemUpdate_FieldArrayClearStillDispatches
...and the `field` ARRAY clear still works, because that form does reach the server's present-but-empty detach (BUG-2013). The refusal above is about
internal/mcp/catalog_item_fields_test.go:1248
FunctionTestPadItemUpdate_FieldArrayConflictAppliesToPromotedKeys
TestPadItemUpdate_FieldArrayConflictAppliesToPromotedKeys: the `fields` vs `field: ["k=v"]` conflict guard has to cover PROMOTED keys too (BUG-2850).
internal/mcp/catalog_item_fields_test.go:545
FunctionTestPadItemUpdate_FieldArrayEqualDuplicateOnPromotedKeyAllowed
...and the equal-duplicate half, so the fix refuses ambiguity rather than refusing agreement. A promoted key with the SAME value in both places is una
internal/mcp/catalog_item_fields_test.go:582
FunctionTestPadItemUpdate_FieldArrayKeysNormalizedForConflicts
TestPadItemUpdate_FieldArrayKeysNormalizedForConflicts: the conflict index must be normalized the way the DOOR normalizes (BUG-2850). ingestFieldKVP
internal/mcp/catalog_item_fields_test.go:678
FunctionTestPadItemUpdate_FieldsConflictInFieldArrayRefused
TestPadItemUpdate_FieldsConflictInFieldArrayRefused: the same key supplied via `field: ["k=v"]` and `fields.k` with different values is the same ambig
internal/mcp/catalog_item_fields_test.go:164
FunctionTestPadItemUpdate_FieldsConflictRefused
TestPadItemUpdate_FieldsConflictRefused: conflicting values in `fields.status` and top-level `status` must refuse with a structured error and dispatch
internal/mcp/catalog_item_fields_test.go:143
FunctionTestPadItemUpdate_FieldsEmptyKeyRefused
TestPadItemUpdate_FieldsEmptyKeyRefused: `fields: {"": "v"}` used to pass the '='-in-key check and emit a malformed `field: ["=v"]` entry (bug 2). Emp
internal/mcp/catalog_item_fields_test.go:415
FunctionTestPadItemUpdate_FieldsEqualDuplicateAllowed
TestPadItemUpdate_FieldsEqualDuplicateAllowed: the same key with the SAME value in both places is unambiguous — apply once, no refusal.
internal/mcp/catalog_item_fields_test.go:184
FunctionTestPadItemUpdate_FieldsNestedValuesReachTheDispatcher
TestPadItemUpdate_FieldsNestedValuesReachTheDispatcher: a nested object or array is no longer refused on the way to the dispatcher (BUG-2850). PR #11
internal/mcp/catalog_item_fields_test.go:267
FunctionTestPadItemUpdate_FieldsNonObjectRefused
TestPadItemUpdate_FieldsNonObjectRefused: a string where the object belongs is a shape error, not a silent drop.
internal/mcp/catalog_item_fields_test.go:210
FunctionTestPadItemUpdate_FieldsNullRefused
TestPadItemUpdate_FieldsNullRefused: a null field value still has no defined write semantics and is refused with the key named. BUG-2850 lifted PR #1
internal/mcp/catalog_item_fields_test.go:235
FunctionTestPadItemUpdate_FieldsObjectApplies
TestPadItemUpdate_FieldsObjectApplies is the #1066 repro, inverted: fields.status / fields.priority must reach the CLI exactly as the dedicated params
internal/mcp/catalog_item_fields_test.go:86
FunctionTestPadItemUpdate_ForceFalse_Omitted
(t *testing.T)
internal/mcp/catalog_item_force_test.go:47
FunctionTestPadItemUpdate_ForcePassesThroughToCLI
(t *testing.T)
internal/mcp/catalog_item_force_test.go:15
FunctionTestPadItemUpdate_GuardsApplyToPromotedKeys
The guards must apply to PROMOTED keys too (BUG-2850). `tags`, `parent`, `status` and friends are handled by an earlier branch that promotes them ont
internal/mcp/catalog_item_fields_test.go:486
FunctionTestPadItemUpdate_HierarchyAliasAmbiguityRefusedWithoutFieldsObject
TestPadItemUpdate_HierarchyAliasAmbiguityRefusedWithoutFieldsObject: the alias guard must fire whichever doors the two hierarchy keys arrive through,
internal/mcp/catalog_item_fields_test.go:793
FunctionTestPadItemUpdate_HierarchyAliasConflictRefused
TestPadItemUpdate_HierarchyAliasConflictRefused: `parent` and `plan` are ONE directive, so a conflict between them has to refuse even though the key n
internal/mcp/catalog_item_fields_test.go:609
FunctionTestPadItemUpdate_LoneHierarchyKeyStillAccepted
...and a lone hierarchy key still works, so the alias guard did not make the ordinary case unreachable.
internal/mcp/catalog_item_fields_test.go:653
FunctionTestPadItemUpdate_MixedCanonicalAndPaddedDuplicatesRefused
TestPadItemUpdate_MixedCanonicalAndPaddedDuplicatesCollapse: one canonical entry does not make its padded twin harmless (BUG-2850). The earlier canon
internal/mcp/catalog_item_fields_test.go:1003
FunctionTestPadItemUpdate_NilTopLevelIsAbsentForEveryKey
TestPadItemUpdate_NilTopLevelIsAbsentForEveryKey: a nil top-level value is absence on every door and for every key (BUG-2850). topLevelValueProvided
internal/mcp/catalog_item_fields_test.go:2241
FunctionTestPadItemUpdate_NonEmptyParentStillDispatched
...and a REAL parent still reaches the CLI, so the drop is about emptiness and not about the key.
internal/mcp/catalog_item_fields_test.go:2317
FunctionTestPadItemUpdate_NonStringIdentityRefRefused
TestPadItemUpdate_NonStringIdentityRefRefused: `assign` and `role` name a person or a role, so a number is refused at the door-independent layer (BUG-
internal/mcp/catalog_item_fields_test.go:1090
FunctionTestPadItemUpdate_NonStringPriorityStillAccepted
...and a numeric value on a NON-identity promoted key is still accepted — an earlier fix, which a blanket "promoted keys must be strings" rule would h
internal/mcp/catalog_item_fields_test.go:1115
FunctionTestPadItemUpdate_PaddedEntryAloneIsRefused
...and a padded entry standing ALONE is untouched. That is BUG-2870, which is out of scope here because fixing it changes what every CLI caller receiv
internal/mcp/catalog_item_fields_test.go:1887
FunctionTestPadItemUpdate_PaddedEntryCollidingWithAParamRefused
TestPadItemUpdate_PaddedEntryCollidingWithAParamRefused: equality only licenses a collapse when both doors receive the SAME write (BUG-2850). The con
internal/mcp/catalog_item_fields_test.go:1849
FunctionTestPadItemUpdate_PaddedEntryRefusedWhenFieldsDoesNotCoverTheKey
TestPadItemUpdate_PaddedEntryRefusedWhenFieldsDoesNotCoverTheKey: whether an entry got canonicalized was a PER-KEY question (BUG-2850). The padded-en
internal/mcp/catalog_item_fields_test.go:1937
FunctionTestPadItemUpdate_PaddedEqualDuplicateIsRefused
REPLACES TestPadItemUpdate_PaddedEqualDuplicateIsCanonicalized (BUG-2850). That test asserted a padded entry equal to its `fields` twin was silently R
internal/mcp/catalog_item_fields_test.go:906
FunctionTestPadItemUpdate_PaddedHierarchyEntriesRefusedEarlier
TestPadItemUpdate_PaddedEqualDuplicateIsCanonicalized (BUG-2850) required a padded equal duplicate to be RE-EMITTED in canonical form rather than reta
internal/mcp/catalog_item_fields_test.go:878
FunctionTestPadItemUpdate_PaddedKeyWithWhitespaceValueIsRefused
REPLACES TestPadItemUpdate_ReEmittedValueKeepsItsWhitespace (BUG-2850, CONVE-28). That test drove the RE-EMISSION path — a padded key was canonicalize
internal/mcp/catalog_item_fields_test.go:2142
FunctionTestPadItemUpdate_PromotedKeysStillPromote
...and the promoted keys still work with well-formed values, so hoisting the guards did not break promotion itself.
internal/mcp/catalog_item_fields_test.go:512
FunctionTestPadItemUpdate_SemanticAliasPairsRefused
TestPadItemUpdate_SemanticAliasPairsRefused: `assign`/`assigned_user_id` and `role`/`agent_role_id` are two names for one target, exactly like `parent
internal/mcp/catalog_item_fields_test.go:1398
FunctionTestPadItemUpdate_SingleHierarchyKeyInFieldArrayStillAccepted
...and ONE hierarchy key through the array is still an ordinary call. The guard refuses ambiguity, not the feature.
internal/mcp/catalog_item_fields_test.go:834
FunctionTestPadItemUpdate_StringHierarchyKeyStillAccepted
...but a string ref still works, so the guard did not re-refuse the normal case while closing the structured one.
internal/mcp/catalog_item_fields_test.go:463
FunctionTestPadItemUpdate_StringIdentityRefStillAccepted
...and a STRING assign/role is untouched, so the refusal is about the type and not about the keys.
internal/mcp/catalog_item_fields_test.go:1131
FunctionTestPadItemUpdate_StructuredHierarchyKeyRefused
A structured `plan` or `parent` must be refused before dispatch (BUG-2850). These keys are hierarchy DIRECTIVES to the server, not ordinary fields: e
internal/mcp/catalog_item_fields_test.go:440
FunctionTestPadItemUpdate_TrimmedComparisonStillCatchesRealDifferences
...and genuinely different values are still refused. Named for the trimmed COMPARISON it was written against (BUG-2850); comparison is raw now (BUG-28
internal/mcp/catalog_item_fields_test.go:2177
FunctionTestPadItemUpdate_UndeclaredKeyRejected
TestPadItemUpdate_UndeclaredKeyRejected: an input key that is not in the tool's declared schema is refused with a structured error naming it — the str
internal/mcp/catalog_item_fields_test.go:344
FunctionTestPadItemUpdate_UnrelatedFieldsObjectDoesNotForceRefusal
TestPadItemUpdate_UnrelatedFieldsObjectDoesNotForceRefusal: a `fields` object carrying some OTHER key must not drag an unrelated duplicate into confli
internal/mcp/catalog_item_fields_test.go:2081
FunctionTestPadItemUpdate_WhitespacePreservingValuesCompareLikeWithLike
TestPadItemUpdate_WhitespacePreservingValuesCompareLikeWithLike: entry values were trimmed for COMPARISON because ingestFieldKVP trimmed them, so comp
internal/mcp/catalog_item_fields_test.go:2116
FunctionTestPadMetaTool_RegisteredInCatalog
TestPadMetaTool_RegisteredInCatalog locks the invariant that init() in catalog_meta.go appends padMetaTool to Catalog. If the registration pattern cha
internal/mcp/catalog_meta_test.go:17
FunctionTestPadMetaTool_RoundTripThroughFanOut
TestPadMetaTool_RoundTripThroughFanOut exercises the full path: register → call via the fan-out handler → assert the result. Same code path Claude Des
internal/mcp/catalog_meta_test.go:209
FunctionTestPadMetaTool_WorkspaceInSchema
TestPadMetaTool_WorkspaceInSchema confirms pad_meta's schema exposes a workspace property. Originally pad_meta was server-wide and the schema delibera
internal/mcp/catalog_meta_test.go:245
FunctionTestPadPlaybookRun_AllowDraftFalse_Omitted
(t *testing.T)
internal/mcp/catalog_playbook_draft_test.go:44
FunctionTestPadPlaybookRun_AllowDraftForwardsBareword
(t *testing.T)
internal/mcp/catalog_playbook_draft_test.go:16
FunctionTestPadTomlNeverImpliesDirection
(t *testing.T)
internal/cli/chat_direction_state_test.go:149
FunctionTestPadWorkspaceAuditLog_ForwardsWithoutFilter
TestPadWorkspaceAuditLog_ForwardsWithoutFilter exercises the no-rename path: a call with no action_filter dispatches identically to passThrough.
internal/mcp/catalog_readonly_test.go:508
FunctionTestPadWorkspaceAuditLog_RenamesActionFilter
TestPadWorkspaceAuditLog_RenamesActionFilter is the regression test for the action-flag-shadow bug: the catalog's `action_filter` input must arrive at
internal/mcp/catalog_readonly_test.go:473
FunctionTestPadddBackoff_MonotonicUntilCap
TestPadddBackoff_MonotonicUntilCap asserts the backoff grows with each attempt and is capped — the decision logic behind "padd unreachable → backoff r
cmd/pad/cmd_watch_test.go:29
FunctionTestPadddBackoff_NonPositiveAttemptTreatedAsFirst
(t *testing.T)
cmd/pad/cmd_watch_test.go:46
FunctionTestParameterRefusedMatchesTheCorpus
TestParameterRefusedMatchesTheCorpus is the store layer's leg of the differential test - the predicate answering for every shape, before any database
internal/textguard/corpus_test.go:81
FunctionTestParentReads_ExcludeSoftDeletedCollections
(t *testing.T)
internal/store/bug3434_relationship_reads_test.go:69
FunctionTestParentSkipDisarmingAChildAgainstATickDoesNotDeadlock
The mark also disarms the child's managed reminder and may record the child's miss. A tick that fires the same reminders queues on the same workspace,
internal/store/commitment_cancel_pg_test.go:92
FunctionTestParentSkipMarkingAChildAgainstACascadeDoesNotDeadlock
The parent's skip against a cascade rooted at the child it marks.
internal/store/commitment_cancel_pg_test.go:46
FunctionTestParentSkipMarkingAChildAgainstAResolveOfThatChildDoesNotDeadlock
The parent's skip marks its child while a resolve of that child waits for the workspace with the child item in hand: the mark never asks for that item
internal/store/commitment_cancel_pg_test.go:29
← previousnext →22,301–22,400 of 28,840, ranked by callers