Code
Hub
Workspaces
Following
Trending
Connect
MCP
copy
Create free account
hub
/
github.com/PerpetualSoftware/pad
/ functions
Functions
28,840 in github.com/PerpetualSoftware/pad
⨍
Functions
28,840
◇
Types & classes
3,245
Function
TestScheduleAllDayFiresAtNineLocalMinusLead
(t *testing.T)
internal/store/schedules_test.go:133
Function
TestScheduleArchiveStopsFireAndRestoreCatchesUp
Archiving stops the fire; restoring resumes it with one catch-up fire.
internal/store/schedule_fire_test.go:570
Function
TestScheduleAssigneeHookResetsADeferredFloatingRow
Reassigning before the fire changes the zone the fire reads, and the assignee hook pulls an already-deferred row back to the bound.
internal/store/schedule_fire_test.go:391
Function
TestScheduleBrokenFloatingRuleRecordsErrorCodeWithoutDeferral
A broken floating rule records error_code on the FIRST fire attempt: the compile runs before the floating deferral, so the row is not deferred (and re
internal/store/schedule_fire_test.go:897
Function
TestScheduleCascadeOnItemDeleteStopsFiring
Deleting the item removes the schedule, its managed row and its occurrences, and nothing fires afterwards.
internal/store/schedule_fire_test.go:595
Function
TestScheduleCascadeOnItemHardDelete
Hard-deleting the item cascades through the composite key to the schedule, its managed reminder and its occurrences.
internal/store/schedules_test.go:692
Function
TestScheduleChanges_AppendOnlyBySource
(t *testing.T)
internal/store/commitment_journal_test.go:393
Function
TestScheduleClosedItemArbiterDoesNotFire
The scan can hand over a candidate just before the item closes. The arbiter must recheck terminality in its fire UPDATE, independently of the scan.
internal/store/schedule_fire_closed_test.go:106
Function
TestScheduleClosedItemDoesNotFire
TASK-4585: a closed item's recurring schedule stays live (the force close in TASK-4538 keeps next_at), and the occurrence must not fire while it is cl
internal/store/schedule_fire_closed_test.go:11
Function
TestScheduleClosedItemTakesNoBatchSlot
(t *testing.T)
internal/store/schedule_fire_closed_test.go:66
Function
TestScheduleCommandsExposeWhatMCPSends
TASK-4105: pad_item's schedule actions dispatch to `pad item remind` and its subcommands on stdio, and BuildCLIArgs emits only the positionals and fla
cmd/pad/task4105_mcp_commands_test.go:14
Function
TestScheduleConcurrentFiresWriteOneEvent
Passes racing for one managed row (two ticks on two instances): exactly one wins, one event, one notification.
internal/store/schedule_fire_test.go:170
Function
TestScheduleConcurrentPatchVsFire
A schedule PATCH racing the tick: no deadlock, no error, exactly one event. The patch changes the lead on a row whose occurrence is long past, so the
internal/store/schedule_fire_test.go:218
Function
TestScheduleCreateAnRDateRescuesARuleThatNeverFires
An RDATE can give a rule that never fires its one occurrence: accepted.
internal/store/schedule_bounds_test.go:499
Function
TestScheduleCreateArmsOneManagedReminder
(t *testing.T)
internal/store/schedules_test.go:101
Function
TestScheduleCreateIsAtomic
Both rows or neither: a failure inserting the managed reminder leaves no schedule behind. The failure is injected with a trigger on item_reminders (SQ
internal/store/schedules_test.go:337
Function
TestScheduleCreateItemDeletedAfterLivenessCheck
An item removed after the locked liveness check must not leave a half-row: the INSERT is refused by the item foreign key and reported as item-gone.
internal/store/schedules_test.go:367
Function
TestScheduleCreateNeverOccursAndRareRules
A rule that never occurs is refused at create, and a rare one that does occur is not (TASK-4236). The refusals come from Compile's satisfiability chec
internal/store/schedule_bounds_test.go:173
Function
TestScheduleCreateOfAPassedRuleKeepsItsRefusal
Create keeps its documented refusal of a rule whose occurrences have all passed, with the exhausted message and not the never-occurs one.
internal/store/schedule_bounds_test.go:302
Function
TestScheduleCreateRefusesASetEveryOccurrenceOfWhichIsExcluded
Rule plus RDATEs less EXDATEs is the set judged: excluding every occurrence leaves nothing, and create says so.
internal/store/schedule_bounds_test.go:510
Function
TestScheduleDeleteRemovesRowsAndOccurrences
(t *testing.T)
internal/store/schedules_test.go:673
Function
TestScheduleDismissParity
(t *testing.T)
internal/mcp/schedule_end_test.go:55
Function
TestScheduleDtendOnlyEditIsNotATimingEdit
dtend is not timing: a dtend-only edit on a fired one-shot window writes the dtend and leaves the fire state, override and anchor alone; it does not e
internal/store/schedules_test.go:513
Function
TestScheduleDtendOnlyEditOnArmedWindowLeavesArmingAlone
A dtend-only edit on an armed window moves nothing the tick reads.
internal/store/schedules_test.go:861
Function
TestScheduleDtendOnlyEditOnBrokenRuleSucceeds
A dtend-only edit never compiles: it works on a schedule whose rule is broken and leaves error_code set.
internal/store/schedules_test.go:882
Function
TestScheduleDtendWithUnchangedTimingFieldDoesNotRearm
A dtend change sent with a timing field whose value is unchanged is not a timing edit: a fired window stays fired.
internal/store/schedules_test.go:899
Function
TestScheduleEndDismissBundleRoundTrip
(t *testing.T)
internal/store/schedule_end_guard_test.go:353
Function
TestScheduleEndDismissMigration
(t *testing.T)
internal/store/schedule_end_guard_test.go:336
Function
TestScheduleEndErrorParity
(t *testing.T)
internal/mcp/schedule_end_test.go:70
Function
TestScheduleEndImportDismissalPresence
(t *testing.T)
internal/store/schedule_end_guard_test.go:394
Function
TestScheduleEndMigrationBackfillsDismissal
(t *testing.T)
internal/store/schedule_end_migration_test.go:10
Function
TestScheduleErrorCode
(t *testing.T)
internal/store/schedules_test.go:841
Function
TestScheduleErrorCodeSetIsComplete
The writer stores whatever ScheduleErrorCode says, and the set is the ten schedule codes plus the five caps.
internal/store/schedule_fire_test.go:550
Function
TestScheduleFarRDateOnADailyRuleIsAccepted
A plain daily rule with an RDATE a century out is fine: the daily scan limit is thousands of years, and the walk is cheap. The time of the floor check
internal/store/schedule_bounds_test.go:435
Function
TestScheduleFireWaitsOnTheScheduleBeforeTheReminder
Postgres: the lock order is deterministic, not just lucky. A writer holding the schedule row (as UpdateSchedule does) and then writing the reminder ro
internal/store/schedule_fire_test.go:276
Function
TestScheduleFireWithABrokenRuleSetsErrorCodeAndDoesNotLoop
A stored rule that stops compiling leaves the row fired with no event and an error_code, and the next tick does not touch it again.
internal/store/schedule_fire_test.go:508
Function
TestScheduleFireWritesExactlyOneOutboxEvent
One fire writes one event whose payload names the schedule and the occurrence, and a managed row's notification is keyed on the occurrence.
internal/store/schedule_fire_test.go:114
Function
TestScheduleFloatingArmsAtTheEarliestBound
(t *testing.T)
internal/store/schedules_test.go:143
Function
TestScheduleFloatingFiresInTheNewZoneWhenTheTimezoneHookFails
The recipient hook is an optimisation, not a dependency: with it failing (or never running, e.g. a crash between the user commit and the hook), the zo
internal/store/schedule_fire_test.go:810
Function
TestScheduleFloatingFiresInTheRecipientZoneWithDeferral
A floating schedule fires in the recipient's zone: armed at the UTC+14 bound, the tick finds it early for a recipient further west and defers it to th
internal/store/schedule_fire_test.go:318
Function
TestScheduleFloatingOccurrenceIsPickedInTheRecipientZone
(t *testing.T)
internal/store/schedules_test.go:211
Function
TestScheduleFloatingUnsetZoneAndAllDay
An unset recipient zone is UTC, and an all-day floating occurrence fires at 09:00 local minus the lead.
internal/store/schedule_fire_test.go:373
Function
TestScheduleFloorAppliesToUpdate
The floor applies to an update too, and a refused update leaves the stored schedule as it was.
internal/store/schedule_bounds_test.go:97
Function
TestScheduleFloorNamesRDatesWhenTheRuleAloneCannotBeMeasured
The floor names rdates when the RDATEs close the gap, even when the rule alone cannot be measured (a rule that never fires needs an RDATE to compile).
internal/store/schedule_bounds_test.go:333
Function
TestScheduleFloorRefusesSubFifteenMinuteSchedules
A schedule that fires more often than every 15 minutes is refused, never thinned. The interval is the shortest gap between two consecutive instants of
internal/store/schedule_bounds_test.go:48
Function
TestScheduleFloorSeesAnRDateBeyondTheRuleSample
An RDATE far past the rule's first few thousand occurrences can still sit inside the floor of a rule instant: every RDATE is checked against its neigh
internal/store/schedule_bounds_test.go:202
Function
TestScheduleFloorSeesTheGapAfterTheLastRDate
The floor sees an RDATE one minute BEFORE a rule instant when it is the last RDATE and lies past the first 2000 occurrences.
internal/store/schedule_bounds_test.go:463
Function
TestScheduleJournalEndedDismissal
(t *testing.T)
internal/store/schedule_journal_dismissal_test.go:10
Function
TestScheduleLeadEditLeavesAFiredRowAlone
A lead edit on a fired row leaves remind_at, fired_at and acked_at alone.
internal/store/schedules_test.go:454
Function
TestScheduleLeadWriteDoesNotUnfireARowFiredInBetween
The lead write is conditional on the row still being armed. Interleave: the instant is computed from an armed row, the row then fires, then the write
internal/store/schedules_test.go:473
Function
TestScheduleMissedCountsPassedInstancesAfterTheOutstandingOne
The missed count excludes the outstanding occurrence and counts the instances strictly after it up to now-1s (an instance exactly at now-1s counts, on
internal/store/schedule_outstanding_test.go:131
Function
TestScheduleMissedFloatingTokyoFiredLARead
A floating row is walked by WALL in the reader's zone: O is next_wall resolved in the reader's zone, not the recipient's stored instant. RED (TASK-410
internal/store/schedule_outstanding_test.go:263
Function
TestScheduleMissedFloatingWestRecipientEastReader
The reverse: the recipient is west of the reader. Walls after O's wall that resolve BEFORE O's stored instant in the reader's zone are counted, not dr
internal/store/schedule_outstanding_test.go:288
Function
TestScheduleMissedInstanceCapIsATruncatedFloor
More than the instance cap passed: a floor of 500, flagged truncated, no error.
internal/store/schedule_outstanding_test.go:183
Function
TestScheduleMissedIsZeroWhenNothingPassed
A healthy future schedule, an ended one and a broken one cost nothing and report nothing.
internal/store/schedule_outstanding_test.go:219
Function
TestScheduleMissedNeverWalksBeforeTheAnchor
The walk starts at anchor_wall, never at dtstart (TASK-4102 PR1b r1, H-q2): a rule that is only affordable near its re-anchor still counts. From the 2
internal/store/schedule_outstanding_test.go:197
Function
TestScheduleOccurrencesKeyedOnAt
The occurrence identity is the UTC instant, not the wall: a bare HOURLY rule repeats a wall across a fall-back. An all-day date is an identity too.
internal/store/schedules_test.go:791
Function
TestScheduleOnePerItemAndLiveItemOnly
(t *testing.T)
internal/store/schedules_test.go:309
Function
TestScheduleOneShotInThePastIsExhausted
(t *testing.T)
internal/store/schedules_test.go:228
Function
TestScheduleRDateAndExDateLimits
At most 1000 RDATE and 1000 EXDATE entries per schedule, refused with a MalformedError that names the part.
internal/store/schedule_bounds_test.go:117
Function
TestScheduleRDateWindowScanCapIsRefused
A cap on an RDATE window is never a pass. The scan cap is deterministic, so it is the cap's own refusal; the work budget depends on load, so it is a C
internal/store/schedule_bounds_test.go:381
Function
TestScheduleRDateWorkBudgetIsBusyNotInvalid
(t *testing.T)
internal/store/schedule_bounds_test.go:397
Function
TestScheduleReadsCarryScheduleIDAndOccurrenceAt
The reads fill occurrence_at: stored for a pinned schedule, read in the recipient's zone for an armed floating one, and the instant it fired for on a
internal/store/schedule_fire_test.go:617
Function
TestScheduleReanchorAvoidsCapScan
A wall-clock sub-daily rule started years back cannot be walked from its dtstart (CapScan); the re-anchored start can.
internal/store/schedule_fire_test.go:779
Function
TestScheduleReanchorOnFire
Re-anchoring: after a fire the start moves to the fired occurrence where that provably changes nothing, and the rules that cannot move it do not.
internal/store/schedule_fire_test.go:673
Function
TestScheduleRecipientZone
The recipient's zone is the assignee's, else the creator's, else UTC.
internal/store/schedules_test.go:176
Function
TestScheduleRecipientZoneIsTheAssigneeElseTheCreator
D3 r2-1: the live read of a floating schedule's zone is the item's assignee, else its creator, in one statement. (The interleaving the single statemen
internal/store/schedule_copy_test.go:1249
Function
TestScheduleRefusalsPersistNothing
(t *testing.T)
internal/store/schedules_test.go:243
Function
TestScheduleReopenMCPParity
(t *testing.T)
internal/mcp/schedule_reopen_test.go:12
Function
TestScheduleReopenMigration
(t *testing.T)
internal/store/schedule_reopen_migration_test.go:8
Function
TestScheduleReopenedItemFiresCaughtUpOccurrence
(t *testing.T)
internal/store/schedule_fire_closed_test.go:40
Function
TestScheduleResolveAckErrorParity
(t *testing.T)
internal/mcp/schedule_ack_test.go:40
Function
TestScheduleResolveAckTransportParity
(t *testing.T)
internal/mcp/schedule_ack_test.go:12
Function
TestScheduleResolveEndScheduleParity
TASK-4537: end_schedule on schedule-resolve and the schedule-dismiss action.
internal/mcp/schedule_end_test.go:14
Function
TestScheduleSnapshotCoversAnchorEndAndError
(t *testing.T)
internal/store/commitment_journal_test.go:531
Function
TestScheduleSurvivesArchive
Archiving keeps the rows; the tick's reminderFireable already gates the managed row, so nothing fires while the item is archived.
internal/store/schedules_test.go:708
Function
TestScheduleTimezoneHooksResetArmedFloatingRows
The users.timezone writers pull the user's armed floating rows back to the bound and touch nothing else.
internal/store/schedule_fire_test.go:433
Function
TestScheduleUpdateAndDeleteOfNone
(t *testing.T)
internal/store/schedules_test.go:661
Function
TestScheduleUpdateClearsErrorOnlyOnATimingEditThatCompiles
(t *testing.T)
internal/store/schedules_test.go:637
Function
TestScheduleUpdateErrorCodeClearsOnlyWhenMergedSpecCompiles
error_code clears only when the merged spec compiles: re-sending a rule that is still broken keeps it and returns the compile error.
internal/store/schedules_test.go:396
Function
TestScheduleUpdateExhaustingEndsAndAReviveReArms
(t *testing.T)
internal/store/schedules_test.go:613
Function
TestScheduleUpdateLeadMovesAnArmedRowOnly
(t *testing.T)
internal/store/schedules_test.go:595
Function
TestScheduleUpdateNoOccurrenceRows
TASK-4236, through PATCH. A rule with no occurrence from its dtstart is refused with "this schedule never occurs"; a cap hit with nothing found keeps
internal/store/schedule_bounds_test.go:234
Function
TestScheduleUpdateNonTimingKeepsTheOutstandingOccurrence
(t *testing.T)
internal/store/schedules_test.go:574
Function
TestScheduleUpdateNonTimingNeverRecompiles
A non-timing edit never recompiles: it works on a schedule whose stored rule no longer compiles, and leaves error_code and the rule as they are.
internal/store/schedules_test.go:419
Function
TestScheduleUpdateOfAnExhaustedRuleSavesANonTimingEdit
An existing schedule whose COUNT has run out stays valid: a title-level edit (no timing field) saves, and the checks do not run.
internal/store/schedule_bounds_test.go:288
Function
TestScheduleUpdateOfLegacyRowsOnlyRechecksTheRuleFields
The checks re-run only when the rule, dtstart, RDATEs or EXDATEs change. A tz-only or anchor-only PATCH of a row stored under the floor, or one that n
internal/store/schedule_bounds_test.go:347
Function
TestScheduleUpdateTimingEditRearmsAFiredRow
(t *testing.T)
internal/store/schedules_test.go:545
Function
TestScheduleUpdateWaitsOnTheItemBeforeTheSchedule
Postgres: an update takes the item before the schedule, like every other writer: pinScheduleTx locks the item, the workspace and the schedule in one s
internal/store/schedule_fire_test.go:847
Function
TestScheduleWritesAnswer409ForAnArchivedItemAnd404ForAMissingOne
D3 fix1-e: a schedule write on an ARCHIVED item answers 409 archived and on a missing one 404, for create, PATCH and resolve alike (the door's pre-che
internal/server/handlers_items_copy_schedule_test.go:307
Function
TestSchemaForMigratedFields
A grandfathered schema may still declare a reserved key. Validating the MIGRATED map against that FieldDef would reject the system-owned value Migrate
internal/items/migrate_test.go:394
Function
TestSchemaTypeBrief_Nil
(t *testing.T)
internal/urlimport/openapi_test.go:258
Function
TestSchemaVersionFrozenUntilSetAsideEditsAreRecoverable
(t *testing.T)
internal/collab/schema_version_guard_test.go:21
Function
TestSchemaVersionMatchesWebClient
(t *testing.T)
internal/collab/schema_version_guard_test.go:48
Function
TestSchemaVersionMismatchRefused
(t *testing.T)
internal/materialize/materialize_test.go:105
Function
TestScopeCollectionIDIsAScopeNotAPermission
(t *testing.T)
internal/store/bug2631_scope_collection_test.go:68
Function
TestScopeCollectionIDSurvivesSlugReuse
The race itself, made deterministic by doing its two halves in order: a caller resolves Alpha, Alpha is renamed away from its slug, and another collec
internal/store/bug2631_scope_collection_test.go:123
Function
TestScopePopulation_WriteActionsAreRefusedForReadTokens
TestScopePopulation_WriteActionsAreRefusedForReadTokens is the population table behind the /mcp insufficient_scope pre-check (TASK-2308). The pre-chec
internal/mcp/scope_population_test.go:34
Function
TestScreenDialAddr
TestScreenDialAddr is the dial-time guard that closes the DNS-rebind TOCTOU: it validates the resolved ip:port the socket is about to connect to, rega
internal/webhooks/dispatcher_test.go:277
Function
TestScrubOnlyEverShrinksAPayload
(t *testing.T)
internal/store/event_outbox_bounds_test.go:731
← previous
next →
24,101–24,200 of 28,840, ranked by callers