Calling the /v1/sandbox/run interface executes the code normally, but the returned error is not empty.

sandbox version: 0.2.14
sandbox:
image: langgenius/dify-sandbox:0.2.14
restart: always
environment:
# The DifySandbox configurations
# Make sure you are changing this key for your deployment with a strong key.
# You can generate a strong key using `openssl rand -base64 42`.
API_KEY: ${SANDBOX_API_KEY:-dify-sandbox}
GIN_MODE: ${SANDBOX_GIN_MODE:-release}
WORKER_TIMEOUT: ${SANDBOX_WORKER_TIMEOUT:-15}
ENABLE_NETWORK: ${SANDBOX_ENABLE_NETWORK:-true}
HTTP_PROXY: ${SANDBOX_HTTP_PROXY:-http://ssrf_proxy:3128}
HTTPS_PROXY: ${SANDBOX_HTTPS_PROXY:-http://ssrf_proxy:3128}
SANDBOX_PORT: ${SANDBOX_PORT:-8194}
PIP_MIRROR_URL: ${PIP_MIRROR_URL:-}
volumes:
- ./volumes/sandbox/dependencies:/dependencies
- ./volumes/sandbox/conf:/conf
ports:
- "8194:8194"
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8194/health"]
#networks:
# - ssrf_proxy_network

Start by reproducing the request against the /v1/sandbox/run interface using the provided sandbox 0.2.14 configuration and inspect the returned error field when code execution succeeds. Trace the endpoint handling and response construction in the Go service; done when successful execution returns an empty error without changing failure reporting.

Written by the indexing model from the issue text.