Let TypeError propagate from tile functions #11805 #11807
Conversation
Catching this could cause other functions to not run.
|
@jacobtylerwalls - A key thing for us it to be able to trace function failure through logging as we have quite a few functions that interface other internal services. I suspect that this was changed to ensure we could see this clearer in our monitoring when the ArcGIS add-in failed to write through the nodevalue api. I'm happy for the typeerror to be explicitly removed, but could there be a level of logging on unhandled errors to allow the issue to be traced? |
|
Great idea. We could just |
|
I'll test it, I have a feeling it might be duplicative with the existing logging to arches.log configured in LOGGING setting. |
|
I'll bounce this idea to a new issue, I'm surprised we didn't have it configured by default. |
|
See #11813 |
Catching this could cause other functions to not run by breaking out of the loop.
Closes #11805
👋 @aj-he you might be interested as I see in #8472 you elevated the info log to a warning. A hard fail would be nice here, no?