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
A draft to remove this code from worker exists here: codecov/worker#782
This does clean up quite a bit, and in particular removes the datapoints which are saved in the report, as well as tasks related to labels.
However, in particular the label-analysis task is still being invoked from the API.
As removing this would make report processing simpler, and the internal report format more lightweight, I would love to go ahead with this deprecation / removal.
The remaining question here, given that a low number of requests/tasks does happen, is how to go about this.
We need to figure out which customers are using this feature, and figure out if they get any value from it at all. We would then need to inform those customers that this feature is going away for good.
The text was updated successfully, but these errors were encountered:
A draft to remove this code from
worker
exists here: codecov/worker#782This does clean up quite a bit, and in particular removes the
datapoints
which are saved in the report, as well as tasks related to labels.However, in particular the
label-analysis
task is still being invoked from the API.As removing this would make report processing simpler, and the internal report format more lightweight, I would love to go ahead with this deprecation / removal.
The remaining question here, given that a low number of requests/tasks does happen, is how to go about this.
We need to figure out which customers are using this feature, and figure out if they get any value from it at all. We would then need to inform those customers that this feature is going away for good.
The text was updated successfully, but these errors were encountered: