Let TypeError propagate from tile functions #11805

[jacobtylerwalls]

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?

[aj-he]

@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?

[jacobtylerwalls]

Great idea. We could just logger.error(exception) inside the custom 500 view added in #11784.

[jacobtylerwalls]

I'll test it, I have a feeling it might be duplicative with the existing logging to arches.log configured in LOGGING setting.

[jacobtylerwalls]

I'll bounce this idea to a new issue, I'm surprised we didn't have it configured by default.

[jacobtylerwalls]

See #11813

[aj-he]

@jacobtylerwalls, given the associated change to catch the errors I'm happy to approve. Once we upgrade to 8 we'll see if there are any issues that reappear and address appropriately.