k8s-triage-robot
commented
5 months ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
mrueg
rexagod
At the moment, there is no option to avoid logging certain errors, which also prevents dependent repositories from operating on these errors in a way that would make more sense to the user-facing side of things. IIUC, it makes sense to use
HandleErrorfor all non-user-facing facets, but not so much in cases where this ends up adding to the confusion of the user since the caller had no way to deal with these errors.A bit of context; at the moment, I'm using reflectors to update stores which are dynamic in nature, in the sense that these can be operated on to add or drop certain resources. This however, leads to
reflector.gologging whenever a previously-found resource goes "missing". Is there a possible workaround to this, or maybe something that I'm completely failing to see?