Closed hossam-nasr closed 6 months ago
Label prediction was below confidence level 0.6
for Model:ServiceLabels
: 'Storage:0.24928018,Service Bus:0.24577391,Cognitive - Computer Vision:0.04792439'
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.
Author: | hossam-nasr |
---|---|
Assignees: | - |
Labels: | `Storage`, `Service Attention`, `needs-triage` |
Milestone: | - |
Label prediction was below confidence level 0.6
for Model:ServiceLabels
: 'Storage:0.24928018,Service Bus:0.24577391,Cognitive - Computer Vision:0.04792439'
thanks for reporting this @hossam-nasr Hossam, we will look into this.
Hi @hossam-nasr, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.
Hi @hossam-nasr, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.
Library name and version
Microsoft.Azure.WebJobs.Extensions.Storage v4.0.5, v5.0.0
Query/Question
In both track 1 and track 2 extensions for storage triggers, there is an internal timer,
CreateUpdateMessageVisibilityTimer
, which updates the queue message'svisibilityTimeout
property after half thevisibilityTimeout
has elapsed, as long as the function is still running and healthy, which allows a function to execute on a message for an arbitrary amount of time, without the message becoming visible again in the queue and picked up by another instance. The timer is created here and executed here for track 2, and created here and executed here for track 1.However, I see different behavior for this timer between the two tracks, when examining the
NextVisibleTime
/nextVisibleOn
of theCloudQueueMessage
/QueueMessage
object. In track 1, I see the property changes, but I don't see such a change using track 2.I have this simple queue trigger function to illustrate this behavior. Using track 1:
When triggered, I see the following output:
I can see the
NextVisibleTime
property change over time. However, when using track 2:I see the following output:
Sometimes it even causes the message to be visible and processed again, without any visible logs or warnings that updating the
visibilityTimeout
failed. For example:In either case though, I don't see the
nextVisibleOn
property updating as time passes.Is this change in behavior to be expected? Is it documented somewhere?
Environment
Windows 10.0.22000 .NET SDK v6.0.101