You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered situations that are unnecessarily difficult to debug because an error result from a middleware function is neither reported in the response body nor logged via tracing. For example, when the attestation_middleware returns AttestationError::CouldNotFindSigner the response just has status 500 with no body explaining what went wrong and there are no logs indicating an issue:
2025-02-11T15:43:29.023335Z INFO indexer_service_rs::metrics: Serving prometheus metrics, address: 0.0.0.0:7300
at crates/service/src/metrics.rs:39
2025-02-11T15:43:29.023364Z INFO indexer_service_rs::service: Serving requests, address: 0.0.0.0:7601
at crates/service/src/service.rs:123
Only after building the indexer-service from source with additional logging was I able to discover where in the pile of middleware something went wrong. There should be logs for middleware errors.
The text was updated successfully, but these errors were encountered:
I have encountered situations that are unnecessarily difficult to debug because an error result from a middleware function is neither reported in the response body nor logged via tracing. For example, when the
attestation_middleware
returnsAttestationError::CouldNotFindSigner
the response just has status 500 with no body explaining what went wrong and there are no logs indicating an issue:Only after building the indexer-service from source with additional logging was I able to discover where in the pile of middleware something went wrong. There should be logs for middleware errors.
The text was updated successfully, but these errors were encountered: