Thundercloud12 commented on issue #9140:
URL: https://github.com/apache/devlake/issues/9140#issuecomment-5697896119

   @klesh Hey so if you allow, i would like to take this issue up, basically i 
have scoped the problem currently we are not handling the failure causing it to 
crash and retry for 3 times, in my proposed solution when we first time receive 
the 404 error we pass it through a custom helper which would basically tell  
the collector skip this item do not crash and move ahead, i would not like to 
mark anything in the db as closed or inactive because, metrics accuracy and i 
have noticed this how 404s are handled in other places like cicd_job_collector.
   If you think there is some other way i am happy to follow along!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to