uncaugth exception causes no response #155
Assignees
Labels
Comments
robstoll
added a commit
to tegonal/datablue
that referenced
this issue
Dec 22, 2021
the /fountains endpoint now requires sw and ne query parameter instead of city moreover: - require a location for byId so that we can look it up in cache - fix TestCityBounds (water-fountains#157) - failure handling for cache populati - send 404 in case json object is undefined (and not only log error and send undefined) - catch errors and send to next middleware (water-fountains#155) - removed database.service.ts - increased REQUEST_LIMIT to 10MB as we query more fountains now - updated Api.yaml accordingly - updated express from 4.17.1 to 4.17.2 - update node-cache from 4.2.1 to 5.1.2 cleanup: - use BoundingBox instead of separate minLng, minLat... as parameter - added last_scan to FountainCollection and provide a factory function which set it automatically to new Date() - fix binding in router.ts
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Express does currently (v 4.17.x) not forward exceptions to the next middleware which means the corresponding response will never finish (until a timeout occurs from the caller side).
Wrap routes into a handlingErrors function
The text was updated successfully, but these errors were encountered: