Skip to content

chore(NODE-6783): document keeping UTR loop and events as entities #4565

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 24, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions test/tools/unified-spec-runner/operations.ts
Original file line number Diff line number Diff line change
Expand Up @@ -456,6 +456,10 @@ operations.set('listIndexNames', async ({ entities, operation }) => {
return indexes.map(index => index.name);
});

/**
* This function was scheduled to be removed in NODE-6783, but we've decideded to keep it
* as the removal is optional and has utility for testing and debugging.
*/
operations.set('loop', async ({ entities, operation, client, testConfig }) => {
const controller = new AbortController();
// We always want the process to exit on SIGINT last, so all other
Expand Down
1 change: 1 addition & 0 deletions test/tools/unified-spec-runner/schema.ts
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,7 @@ export interface ClientEntity {
ignoreCommandMonitoringEvents?: string[];
serverApi?: ServerApi;
observeSensitiveCommands?: boolean;
// Was optionally scheduled for removal in NODE-6783, but opted to keep it for potential future use.
storeEventsAsEntities?: StoreEventsAsEntity[];
}
export interface DatabaseEntity {
Expand Down