MCPcopy Create free account

hub / github.com/PerpetualSoftware/pad / functions

Functions28,840 in github.com/PerpetualSoftware/pad

FunctionTestRelationDoors_WhitespaceOnlyRelationIsNotRefused
A whitespace-only relation value is "no reference", not a bad one. The store resolver trims and ignores it. The server wrapper checked the UNTRIMMED
internal/server/relation_referents_doors_test.go:761
FunctionTestRelationDoors_WrongCollectionDoesNotDiscloseExistence
`wrong_collection` names a LIVE item, so its message tells the caller the value exists — distinguishable from the `not_found` a nonexistent value gets
internal/server/relation_referents_doors_test.go:666
FunctionTestRelationFeedersPassTheRequesterVisibility
TestRelationFeedersPassTheRequesterVisibility is the guard the fail-closed pass relies on to stay unreachable. Every store function that takes a Relat
internal/server/relation_unjudged_fail_closed_test.go:64
FunctionTestRelationFieldTypes_AgreesWithIsRelation
RelationFieldTypes must agree with IsRelation. Two expressions of one fact drift, and this is the only place that can notice.
internal/models/relation_field_types_test.go:47
FunctionTestRelationIndex_BackfillCoversMultiRelationArrays
ROW 21: the BACKFILL handles the array form, not just the write hook. The two paths derive edges differently enough to be worth separating — the writ
internal/store/relation_links_multi_test.go:116
FunctionTestRelationIndex_MultiRelationIndexesEveryElementWithItsOrdinal
ROW 20: a multi_relation write indexes ONE ROW PER ELEMENT, with the array position in `ordinal`.
internal/store/relation_links_multi_test.go:62
FunctionTestRelationIndex_RetypeReindexesWhatIsStored
ROW 22: a scalar->array RETYPE reindexes against what is STORED, not against what the new schema says the shape should be. A garbage retype could loo
internal/store/relation_links_multi_test.go:177
FunctionTestRelationKeysPresent_AnEmptyListIsNotCallerInput
(t *testing.T)
internal/store/relation_multi_defaults_test.go:280
FunctionTestRelationLinks_ASourceInADeletedCollectionIsNotCounted
TestRelationLinks_ASourceInADeletedCollectionIsNotCounted guards a disclosure case. DeleteCollection soft-deletes the COLLECTION and leaves its items
internal/store/relation_links_test.go:537
FunctionTestRelationLinks_AnInterruptedBackfillIsRetriedNotSkipped
TestRelationLinks_AnInterruptedBackfillIsRetriedNotSkipped guards an interrupted backfill being retried rather than skipped. The guard used to be "do
internal/store/relation_links_test.go:451
FunctionTestRelationLinks_BackfillClearsAStaleEdge
TestRelationLinks_BackfillClearsAStaleEdge guards a stale edge being cleared by the backfill. The backfill used to SKIP an item whose blob carries no
internal/store/relation_links_test.go:502
FunctionTestRelationLinks_BackfillDerivesRowsWrittenBeforeTheIndexExisted
TestRelationLinks_BackfillDerivesRowsWrittenBeforeTheIndexExisted is Q3's backfill leg. The table is emptied to simulate a pre-migration database.
internal/store/relation_links_test.go:257
FunctionTestRelationLinks_BacklinkCarriesTheFieldLabel
TestRelationLinks_BacklinkCarriesTheFieldLabel pins that a backlink carries the field label, which was a field declared, documented, consumed by the U
internal/store/relation_links_test.go:619
FunctionTestRelationLinks_ChangingTheValueMovesTheEdge
TestRelationLinks_ChangingTheValueMovesTheEdge is Q3's BOTH HALVES leg. A writer that only ever INSERTs passes "the new target counts it". Only the o
internal/store/relation_links_test.go:99
FunctionTestRelationLinks_HardDeleteCascadesTheEdges
TestRelationLinks_HardDeleteCascadesTheEdges pins a claim the input matrix makes and nothing else checked. The matrix says a hard delete needs no hoo
internal/store/relation_links_test.go:584
FunctionTestRelationLinks_ImportIndexesTheRemappedIDs
TestRelationLinks_ImportIndexesTheRemappedIDs covers the import hook, which none of the legs above reach. Two things have to be true and only one is
internal/store/relation_links_test.go:305
FunctionTestRelationLinks_MoveReindexesAgainstTheDestinationSchema
TestRelationLinks_MoveReindexesAgainstTheDestinationSchema. A move is the one write where the blob and the SCHEMA change together. The same stored va
internal/store/relation_links_test.go:180
FunctionTestRelationLinks_RestoreAfterASchemaChangeReindexes
TestRelationLinks_RestoreAfterASchemaChangeReindexes guards a restore that follows a schema change: it is a hole a site enumeration could not have fou
internal/store/relation_links_test.go:397
FunctionTestRelationLinks_SchemaChangeReindexesTheCollection
TestRelationLinks_SchemaChangeReindexesTheCollection encodes the D2 decision as a test. Declaring a relation field over values that already exist mus
internal/store/relation_links_test.go:214
FunctionTestRelationLinks_SoftDeletedSourceDropsOutAndRestoreBringsItBack
TestRelationLinks_SoftDeletedSourceDropsOutAndRestoreBringsItBack. store/items.go documents that a restore resurrects an item's relationships; the re
internal/store/relation_links_test.go:129
FunctionTestRelationLinks_SoftDeletedTargetKeepsItsRows
TestRelationLinks_SoftDeletedTargetKeepsItsRows asserts on the STORE's answer rather than on a chip's wording. Q3's row phrases this leg as "the sour
internal/store/relation_links_test.go:161
FunctionTestRelationLinks_WriteThenReadCountsTheSource
TestRelationLinks_WriteThenReadCountsTheSource is the first half of Q3's property: a written relation value shows up on the target's reverse side.
internal/store/relation_links_test.go:61
FunctionTestRelationRefDoesNotResolveByNumberAcrossALivePrefix
BUG-4119: a prefix miss needs the item's move log, not merely an absent live collection. Prefix renames alone, deleted unrelated collections, and fore
internal/server/relation_ref_prefix_test.go:15
FunctionTestRelationReindexCost
TestRelationReindexCost measures ReindexCollectionRelationLinks at scale. This number was asked for on TASK-2997's trail before accepting the reindex
internal/store/relation_links_cost_test.go:24
FunctionTestRelationTargetSet_ListMarshalsAsAnArrayInOrder
(t *testing.T)
internal/models/relation_target_set_test.go:39
FunctionTestRelationTargetSet_RoundTripsBothShapes
Both shapes must ROUND-TRIP, because the CLI decodes item JSON the server produced. A marshaller without a matching unmarshaller is how a shape change
internal/models/relation_target_set_test.go:83
FunctionTestRelationTargetSet_ScalarIsByteIdenticalToTheOldShape
RelationTargetSet's wire shape (PLAN-2857 U4). The compatibility claim for this type is that a SCALAR entry marshals exactly as v0.31 emitted it, and
internal/models/relation_target_set_test.go:15
FunctionTestRelationTargetSet_ZeroValueMarshalsAsNull
A set with NEITHER shape set marshals as null. It is a state no constructor produces, and the alternative — `{}` — would read as a target with an empt
internal/models/relation_target_set_test.go:69
FunctionTestRelationTitleCopy_OverrideResolvesForACallerWhoSeesOneTwin
TestRelationTitleCopy_OverrideResolvesForACallerWhoSeesOneTwin covers this: the copy re-resolved the raw title inside its transaction and saw `ambiguo
internal/server/relation_titles_copy_test.go:48
FunctionTestRelationTitleCopy_PreflightAndCopyAgreeOnANarrowedTitle
TestRelationTitleCopy_PreflightAndCopyAgreeOnANarrowedTitle covers this, and it is the one a per-door test cannot make: agreement between two doors is
internal/server/relation_titles_copy_test.go:74
FunctionTestRelationTitleDoors_AmbiguityIsCountedOverVISIBLEMatchesOnly
(t *testing.T)
internal/server/relation_titles_doors_test.go:284
FunctionTestRelationTitleDoors_HydrationUsesITEMVisibilityNotCollectionVisibility
TestRelationTitleDoors_HydrationUsesITEMVisibilityNotCollectionVisibility is the read-side half of the same trap, and it is a leak a collection-level
internal/server/relation_titles_doors_test.go:354
FunctionTestRelationTitleDoors_LateDefaultResolvesForACallerWhoSeesOne
TestRelationTitleDoors_LateDefaultResolvesForACallerWhoSeesOne pins a leak through the OUTCOME rather than the message. A relation DEFAULT declared a
internal/server/relation_titles_doors_test.go:508
FunctionTestRelationTitleDoors_LegacyTargetWithoutRefIsRedacted
BUG-3366: a LEGACY target, whose item_number is NULL, hydrates with a title but no ref. Redaction used to key on the ref alone, so an ungranted legacy
internal/server/relation_titles_doors_test.go:623
FunctionTestRelationTitleDoors_ProbeFindsAVisibleMatchNotAnArbitraryOne
TestRelationTitleDoors_ProbeFindsAVisibleMatchNotAnArbitraryOne covers the property failing in the other direction. When nothing in the declared coll
internal/server/relation_titles_doors_test.go:570
FunctionTestRelationTitleDoors_ReadDoesNotHydrateAnInvisibleTarget
TestRelationTitleDoors_ReadDoesNotHydrateAnInvisibleTarget is the read-side mirror of the disclosure rule above. The write side collapses `wrong_coll
internal/server/relation_titles_doors_test.go:189
FunctionTestRelationTitleDoors_ReadHydratesTheTarget
TestRelationTitleDoors_ReadHydratesTheTarget is the hydration half's binding claim: the read door returns relation_targets, and a dangling value comes
internal/server/relation_titles_doors_test.go:136
FunctionTestRelationTitleDoors_ThreeSpellingsAgreeThroughTheCreateDoor
(t *testing.T)
internal/server/relation_titles_doors_test.go:48
FunctionTestRelationTitleDoors_TitleWrongCollectionDoesNotDiscloseExistence
TestRelationTitleDoors_TitleWrongCollectionDoesNotDiscloseExistence is the existence-disclosure check on the TITLE path, and it is the leg the addendu
internal/server/relation_titles_doors_test.go:84
FunctionTestRelationTitleDoors_UpdateDoorAppliesTheSameNarrowing
TestRelationTitleDoors_UpdateDoorAppliesTheSameNarrowing answers a coverage gap: the three ambiguity legs only drove CREATE, and each door reaches the
internal/server/relation_titles_doors_test.go:468
FunctionTestRelationTitleDoors_VisibilityNarrowingHasNoCountBoundary
TestRelationTitleDoors_VisibilityNarrowingHasNoCountBoundary is the regression test for an earlier defect: the first fix bounded the candidate list at
internal/server/relation_titles_doors_test.go:413
FunctionTestRelationTitle_ANullItemNumberCandidateStillCounts
TestRelationTitle_ANullItemNumberCandidateStillCounts guards the case: it is the reason the candidate walk pages on `id`. The first paging shape used
internal/store/relation_titles_test.go:327
FunctionTestRelationTitle_AmbiguousRefusesWithItsOwnReason
TestRelationTitle_AmbiguousRefusesWithItsOwnReason covers the ambiguity decision: two live items in the TARGET collection sharing a title name no sing
internal/store/relation_titles_test.go:103
FunctionTestRelationTitle_RefWinsOverAnItemTitledLikeARef
TestRelationTitle_RefWinsOverAnItemTitledLikeARef pins the ladder's order and the shadowing case the resolver's doc comment names: UUID, then ref, the
internal/store/relation_titles_test.go:147
FunctionTestRelationTitle_ScopeIsTheDeclaredCollection
TestRelationTitle_ScopeIsTheDeclaredCollection is the store half of the scope decision and the R11 guard: a title unique in the WORKSPACE but living o
internal/store/relation_titles_test.go:65
FunctionTestRelationTitle_SoftDeletedTitleDoesNotResolve
TestRelationTitle_SoftDeletedTitleDoesNotResolve: a deleted item's title is not a handle. The control is the same title on a live item, so the leg can
internal/store/relation_titles_test.go:185
FunctionTestRelationTitle_SuppliedValueStillObeysVisibility
TestRelationTitle_SuppliedValueStillObeysVisibility is the other half, and it is what stops the fix above from being "visibility was switched off". A
internal/store/relation_titles_test.go:411
FunctionTestRelationTitle_ThreeSpellingsOfOneItemStoreTheSameID
TestRelationTitle_ThreeSpellingsOfOneItemStoreTheSameID is the design row's proving test: the same relation written by ref, by exact title and by raw
internal/store/relation_titles_test.go:42
FunctionTestRelationValueStoredAsText_SharedVectors
TestRelationValueStoredAsText_SharedVectors pins the Go predicate to the table the web's copy is pinned to. KEEP IN SYNC with web/src/lib/items/relati
internal/store/relation_stored_as_text_test.go:160
FunctionTestRelationVisibility_ControlAVisibleElementStillResolves
(t *testing.T)
internal/store/relation_visibility_rungs_test.go:94
FunctionTestRelationVisibility_ControlWrongCollectionSurvivesForASeenTarget
(t *testing.T)
internal/store/relation_visibility_rungs_test.go:141
FunctionTestRelationVisibility_EveryMultiElementIsJudged
(t *testing.T)
internal/store/relation_visibility_rungs_test.go:61
FunctionTestRelationVisibility_NoPredicateMeansNoJudgement
(t *testing.T)
internal/store/relation_visibility_rungs_test.go:164
FunctionTestRelationVisibility_ScalarRefToAnInvisibleTargetIsNotFound
(t *testing.T)
internal/store/relation_visibility_rungs_test.go:37
FunctionTestRelationVisibility_WrongCollectionIsCollapsedForAnUnseenTarget
(t *testing.T)
internal/store/relation_visibility_rungs_test.go:118
FunctionTestRelativeTimeOldDateInZone
(t *testing.T)
internal/cli/zone_test.go:27
FunctionTestRelayAppendStoresAStep2AsNonContent
The relay's append path (AppendSyncFrame) applies the same rule: the step2 is stored, so joining tabs still replay it, but not counted.
internal/store/bug3136_step2_twin_test.go:246
FunctionTestReleaseCloudOwnership
release-cloud: refused while billing state remains, unless forced; once released the conversion runs (taking the source over, as the primitive does);
internal/store/task3551_instance_mode_test.go:94
FunctionTestReleaseItemLease_AbsentOrExpiredIsNoop
Releasing an absent or expired lease is a no-op, never an error — cleanup code must not special-case "did I still hold this".
internal/store/item_lease_test.go:185
FunctionTestReleaseItemLease_ForeignLiveRefused
Releasing another holder's LIVE lease is refused with LeaseHeldError — refuse-on-ambiguity, not last-writer-wins.
internal/store/item_lease_test.go:205
FunctionTestReleaseItemLease_HolderReleases
Release by the holder clears the lease; the item is claimable again.
internal/store/item_lease_test.go:164
FunctionTestReleaseNotifications_SkipsAtFive
Kills: attempts not incremented; the cap changed (5 -> 6 or 4); the skip not in the same statement as the fifth release; the claim not cleared.
internal/store/task3939_push_dispatch_test.go:299
FunctionTestReleaseWorkflow_PinsThePluginWithoutFailingTheRelease
The release job runs the pin after the release and never fails the run.
internal/buildtools/pin_plugin_marketplace_test.go:163
FunctionTestReleasedSkillFormattingMatchesToday
The reconstruction assumes every tag formatted output with today's StripFrontmatter and frontmatter literals. Check that per tag rather than assume it
internal/cli/skill_legacy_hashes_gen_test.go:203
FunctionTestRemapAttachmentReferencesLeavesSearchIndexConsistent
The remap is the second caller the rebuild had, and a bundle with attachments always reaches it. The import is asserted clean FIRST, so this leg fails
internal/store/import_fts_test.go:116
FunctionTestRemapAttachmentReferences_DoesNotStampUnreferencedClones
A clone that nothing ends up referencing must NOT be stamped. Stamping the whole id map would vouch for rows no text points at, keeping genuinely unre
internal/store/attachments_document_refs_test.go:270
FunctionTestRemapAttachmentReferences_RewritesCommentBodies
BUG-2615. The remap is what makes an imported bundle's references point at the destination's cloned attachment rows. It walked items only, so a refere
internal/store/attachments_document_refs_test.go:197
FunctionTestRemapAttachmentReferences_StampsTheRewrittenTarget
The remap must leave the destination's stamps correct, not just its text. The import stamps each comment body at insert, but the body still holds the
internal/store/attachments_document_refs_test.go:236
FunctionTestRemapAttachmentRefsTokenizesLikeThePlanner
--- The attachment-ref rewrite (TASK-2365) --------------------------------- TestRemapAttachmentRefsTokenizesLikeThePlanner pins the property that mak
internal/store/items_cross_workspace_copy_test.go:1213
FunctionTestRemapPartialError_IsPlainAndKeepsItsCause
(t *testing.T)
internal/store/attachments_remap_chunk_test.go:515
FunctionTestRemap_ConcurrentItemEditIsNotOverwritten
BUG-2797. RemapAttachmentReferencesInWorkspace (run by bundle import, while the imported workspace is already visible to its owner) is a read-modify-
internal/store/attachments_remap_lost_update_test.go:50
FunctionTestRemap_ItemCapBoundsAChunk
The item cap alone bounds a chunk when the clock never advances.
internal/store/attachments_remap_chunk_test.go:480
FunctionTestRemap_SingleChunkEquivalence
A workspace small enough for one chunk must come out byte-identical to what the single-transaction remap produced. The golden file was captured from t
internal/store/attachments_remap_chunk_test.go:22
FunctionTestRemap_StopAfterFirstChunk
Stopped after the first chunk (the fault seam), a part-done remap must (1) resolve every item it did process FULLY, content, fields, its comments, its
internal/store/attachments_remap_chunk_test.go:255
FunctionTestRemap_ThousandRewritesEveryChunkUnderOneSecond
The same 1,000 rewrites on the injected clock: every chunk's lock hold is under 1 s whatever the box does, and the work is split.
internal/store/attachments_remap_chunk_test.go:664
FunctionTestRemap_ThousandRewritesLockHoldAndInterleavedWrites
At 1,000 rewrites the remap must (a) hold the workspace seq lock for under 1 s per chunk, measured on the injected clock so the figure is deterministi
internal/store/attachments_remap_chunk_test.go:561
FunctionTestRemap_TimeBudgetEndsChunksAndNothingIsSkipped
The chunk boundary is the clock's, and the stop is an item boundary: with a clock that makes every reading cost 100 ms the time budget (not the item c
internal/store/attachments_remap_chunk_test.go:441
FunctionTestRemindAckOccurrenceSelection
(t *testing.T)
cmd/pad/schedule_ack_test.go:9
FunctionTestRemindAcknowledgedAgendaAttribution
(t *testing.T)
cmd/pad/schedule_ack_test.go:59
FunctionTestRemindAcknowledgedAgendaKeepsColumns
The attribution rides in the last column, so the rows after an acknowledged entry keep the table's alignment.
cmd/pad/schedule_ack_test.go:76
FunctionTestRemindAgendaMatchesTheEndpoint
(t *testing.T)
cmd/pad/task4356_remind_test.go:324
FunctionTestRemindArgsAcceptRearmWithoutARef
TestRemindArgsAcceptRearmWithoutARef. `--rearm` addresses a reminder by id and needs no item ref, but ExactArgs(1) forced one and the rearm branch th
cmd/pad/stale_overdue_test.go:54
FunctionTestRemindAtRefusals
(t *testing.T)
cmd/pad/task4356_remind_test.go:158
FunctionTestRemindAtServerRefusalsPassThrough
(t *testing.T)
cmd/pad/task4356_remind_test.go:178
FunctionTestRemindBothFormsAreIdentical
(t *testing.T)
cmd/pad/task4356_remind_test.go:81
FunctionTestRemindDeadlineNone
(t *testing.T)
cmd/pad/task4105_remind_schedule_test.go:94
FunctionTestRemindDismiss
(t *testing.T)
cmd/pad/schedule_end_test.go:202
FunctionTestRemindDoneAtActualCompletion
(t *testing.T)
cmd/pad/task4356_remind_test.go:127
FunctionTestRemindDoneCloseItemFlow
(t *testing.T)
cmd/pad/schedule_end_test.go:57
FunctionTestRemindDoneCloseItemJSON
(t *testing.T)
cmd/pad/schedule_end_test.go:223
FunctionTestRemindDoneCloseItemScheduleContinues
TestRemindDoneCloseItemScheduleContinues: when a concurrent edit gives the schedule another occurrence before the end_schedule retry, the retry does n
cmd/pad/schedule_end_test.go:264
FunctionTestRemindDoneCloseItemWithoutClosingValue
(t *testing.T)
cmd/pad/schedule_end_test.go:243
FunctionTestRemindEndScheduleFlags
(t *testing.T)
cmd/pad/schedule_end_test.go:143
FunctionTestRemindFlagsDoNotLeakBetweenForms
The two instances share no flag state.
cmd/pad/task4356_remind_test.go:70
FunctionTestRemindItemStillOpenHints
(t *testing.T)
cmd/pad/schedule_end_test.go:168
FunctionTestRemindOneShotUnchanged
The plain reminder is pinned: its requests, its output and its errors.
cmd/pad/task4105_remind_oneshot_test.go:42
FunctionTestRemindParseTable
(t *testing.T)
internal/schedule/commitment_flags_test.go:10
FunctionTestRemindPastDeadlineFeedback
(t *testing.T)
cmd/pad/schedule_past_deadline_test.go:24
FunctionTestRemindPastDeadlineFlag
(t *testing.T)
cmd/pad/schedule_past_deadline_test.go:8
FunctionTestRemindPastDeadlineFlagCombinations
(t *testing.T)
cmd/pad/schedule_past_deadline_test.go:40
← previousnext →23,301–23,400 of 28,840, ranked by callers