ipfs/kubo

gateway: better error exposing in logs from gateway code

Open

#2,972 opened on Jul 15, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/bugstatus/deferredtopic/gateway

Description

re: https://github.com/ipfs/go-ipfs/pull/2971#discussion_r70961908

Contributor guide

Tech stack
go
Domain
backend
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
GoIPFSgateway code
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue references a code review discussion about error handling in the gateway. First, examine the current gateway logging implementation in go ipfs (e.g., core/corehttp/gateway.go). Identify where errors are logged and what information is missing. The goal is to improve error messages to aid debugging without leaking sensitive information. Consider adding structured logging or wrapping errors with context.