Skip to content

Worker loads the blob extension that finds new outbox blobs - #6

Closed
fw2568 wants to merge 1 commit into
mainfrom
fix/blob-trigger-scan
Closed

fw2568 wants to merge 1 commit into
mainfrom
fix/blob-trigger-scan

Conversation

@fw2568

@fw2568 fw2568 commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

Worker package 6.8.2 still names blob extension 5.3.8. Its container scan keeps the start time of the host's first poll, so an attachment the cloud puts into bote-outbox after that is never found and reaches the client only after a restart of the worker (Azure/azure-sdk-for-net#61660, fixed in 5.3.10). No worker package names 5.3.10 yet and the SDK takes no override, so the generated extension project is pointed at it; the build fails once the worker package names another version, and a test checks the version the host gets.

…fter its first poll

Worker package 6.8.2 names blob extension 5.3.8, whose container scan never refreshes its start
time: attachments from the cloud reached clients only after a restart of the worker
(Azure/azure-sdk-for-net#61660, fixed in 5.3.10).
@fw2568

fw2568 commented Oct 25, 2026

Copy link
Copy Markdown
Contributor Author

Not viable: blob extension 5.3.10 needs Microsoft.Extensions.Azure 1.14 → Azure.Core 1.53 → System.Memory.Data 10.0.3, which the current Functions host does not ship; the host crashes on first RequestFailedException. Replaced by an Event Grid based outbox notification.

@fw2568 fw2568 closed this Oct 25, 2026
@fw2568
fw2568 deleted the fix/blob-trigger-scan branch October 25, 2026 11:37
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.

1 participant