You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
featureIssues that represent new features or improvements to existing features.t-toolingIssues with this label are in the ownership of the tooling team.
The retryHistogram behaves similarly to the bugged retries in that it only updates once the request is handled (succeeds or fails). Unlike with retries, I don't consider this a clear bug because mixing together handled requests and in-progress requests in the histogram could be confusing, especially since new requests that were not even started are coming in.
On the other hand, I still think it is very useful to get the live breakdown of retries. This provides a very good feedback to the developer if the retries are caused by a large number of requests having 1-2 retries or actually few requests hitting a very large retryCount.
I will leave up for discussion if we should figure out how to rework the current retryHistogram or if we should implement a new field e.g..liveRetryHistorgram (bad name). If we go for the new field, I can imagine we would not show the 0 retries case as we get that already from retryHistogram.
featureIssues that represent new features or improvements to existing features.t-toolingIssues with this label are in the ownership of the tooling team.
Which package is the feature request for? If unsure which one to select, leave blank
None
Feature
This is a follow up on my bug report with statistics.state.requestsRetries.
The retryHistogram behaves similarly to the bugged retries in that it only updates once the request is handled (succeeds or fails). Unlike with retries, I don't consider this a clear bug because mixing together handled requests and in-progress requests in the histogram could be confusing, especially since new requests that were not even started are coming in.
On the other hand, I still think it is very useful to get the live breakdown of retries. This provides a very good feedback to the developer if the retries are caused by a large number of requests having 1-2 retries or actually few requests hitting a very large
retryCount
.I will leave up for discussion if we should figure out how to rework the current
retryHistogram
or if we should implement a new field e.g..liveRetryHistorgram
(bad name). If we go for the new field, I can imagine we would not show the 0 retries case as we get that already fromretryHistogram
.See also run on Apify https://console.apify.com/view/runs/cbHWZTetxgehJuK3b
Motivation
See Feature description
Ideal solution or implementation, and any additional constraints
See Feature description
Alternative solutions or implementations
No response
Other context
No response
The text was updated successfully, but these errors were encountered: