this some how reminds me of the container dir walker fixes that Mahati worked on [1]. The point is we need to iter the dirs and trap errors right w/o blowing up the whole loop and when we find something that we really don't know what to do with emit an error and pointer to the operator how to get rid of it:
"This thing at <path> is not great for me!"
That can be at debug, but warning is probably fine since we think these things are unexpected and not the common case!
this some how reminds me of the container dir walker fixes that Mahati worked on [1]. The point is we need to iter the dirs and trap errors right w/o blowing up the whole loop and when we find something that we really don't know what to do with emit an error and pointer to the operator how to get rid of it:
"This thing at <path> is not great for me!"
That can be at debug, but warning is probably fine since we think these things are unexpected and not the common case!
1. https:/ /review. openstack. org/#/c/ 331601/