Skip to content

Conversation

@Charles-Gagnon
Copy link
Contributor

This was broken in #376 (copypaste typo)

It wasn't caught by the test because the default values were changed but the tests hadn't been updated with the new values. I fixed them to use the default values defined in the trigger code directly so this doesn't happen again if those are changed in the future.

I also added another check to watch for the log message we send to indicate what the batchSize/pollingInterval values are as a secondary verification.

/// Creates a DataReceievedEventHandler that will wait for the specified regex and then check that
/// the matched group matches the expected value.
/// </summary>
/// <param name="taskCompletionSource">The task completion source to signal when the value is receieved</param>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: received

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is seriously one of my least favorite words - my fingers just always want to spell it recieved.

@Charles-Gagnon Charles-Gagnon merged commit a150c9f into triggerbindings Oct 14, 2022
@Charles-Gagnon Charles-Gagnon deleted the chgagnon/fixPollingSize branch October 14, 2022 22:19
PBBlox pushed a commit to PBBlox/azure-functions-sql-extension that referenced this pull request Apr 6, 2025
Fix polling size override using wrong configuration value
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants