Conversation
in such way we are always notified that context was cancelled when calling csaf_downloader
Conventional Commits Report😢 No conventional commits found. 👉 Learn more about the conventional commits usage at Greenbone. |
Modver resultThis report was generated by Modver, This PR does not require a change in your module’s version number. |
|
There is a second csaf_distribution/cmd/csaf_downloader/downloader.go Lines 298 to 305 in a830852 I think it is the safest to also send the context error to the error channel as well. In the end we can end up with many of those cancel errors in the error ultimately returned (one per worker + one in place mentioned above). But I think that is acceptable and better than possibly missing error feedback in edge cases. |
What
Return error on canceled download context
Why
in such way we are always notified that context was cancelled when calling csaf_downloader through error channel, rather than silently stopping the download process.
References
VTI-705