Unhandled error logs lack diagnostic details, making it hard for users to self-diagnose #8894

Open
opened 2026-02-16 18:11:06 -05:00 by yindo · 2 comments
Owner

Originally created by @Haoping-Xiao on GitHub (Feb 9, 2026).

Originally assigned to: @rekram1-node on GitHub.

Error logs from unhandledRejection / uncaughtException only print e.message, losing all structured context:

ERROR 2026-02-07T09:58:35 +30ms service=default e=Unable to connect. Is the computer able to access the url? rejection
ERROR 2026-02-07T08:42:41 +5ms service=mcp clientName=playwright error=MCP error -32601: Method not found failed to get prompts
ERROR 2026-02-07T08:42:43 +5ms service=default e=ProviderModelNotFoundError rejection

Users cannot tell which URL failed to connect, which provider/model was not found, or what the root cause was. This leads to duplicate issues and inability to self-diagnose.

The same pattern exists in MCP error logging where e.message is passed instead of the full error object.

Originally created by @Haoping-Xiao on GitHub (Feb 9, 2026). Originally assigned to: @rekram1-node on GitHub. Error logs from `unhandledRejection` / `uncaughtException` only print `e.message`, losing all structured context: ``` ERROR 2026-02-07T09:58:35 +30ms service=default e=Unable to connect. Is the computer able to access the url? rejection ERROR 2026-02-07T08:42:41 +5ms service=mcp clientName=playwright error=MCP error -32601: Method not found failed to get prompts ERROR 2026-02-07T08:42:43 +5ms service=default e=ProviderModelNotFoundError rejection ``` Users cannot tell which URL failed to connect, which provider/model was not found, or what the root cause was. This leads to duplicate issues and inability to self-diagnose. The same pattern exists in MCP error logging where `e.message` is passed instead of the full error object.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 9, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #11701: Empty catch blocks silently swallow errors in config and initialization
  • #11697: Missing error handling in Share API fetch calls leads to silent failures
  • #11698: Unprotected JSON.parse in provider fetch wrapper can crash requests
  • #11700: Missing array bounds checking in LLM provider response handling
  • #3989: acp-command unhandled rejection
  • #9038: Provider 520 errors surface as MessageAbortedError with no diagnostics
  • #10631: ModelNotFoundError causes UI disruption and stack trace instead of friendly error message
  • #12511: OpenCode crashes immediately on ingesting the following error

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 9, 2026): This issue might be a duplicate of existing issues. Please check: - #11701: Empty catch blocks silently swallow errors in config and initialization - #11697: Missing error handling in Share API fetch calls leads to silent failures - #11698: Unprotected JSON.parse in provider fetch wrapper can crash requests - #11700: Missing array bounds checking in LLM provider response handling - #3989: acp-command unhandled rejection - #9038: Provider 520 errors surface as MessageAbortedError with no diagnostics - #10631: ModelNotFoundError causes UI disruption and stack trace instead of friendly error message - #12511: OpenCode crashes immediately on ingesting the following error Feel free to ignore if none of these address your specific case.
Author
Owner

@Haoping-Xiao commented on GitHub (Feb 9, 2026):

For example, many issues are related to Unable to connect. This frequently occurs within internal networks. Users and developers often have limited visibility to diagnose the root cause.

ERROR 2026-02-07T09:54:12 +22ms service=default e=Unable to connect. Is the computer able to access the url? rejection
ERROR 2026-02-07T09:54:12 +0ms service=default e=Unable to connect. Is the computer able to access the url? rejection

@Haoping-Xiao commented on GitHub (Feb 9, 2026): For example, many issues are related to `Unable to connect`. This frequently occurs within internal networks. Users and developers often have limited visibility to diagnose the root cause. ERROR 2026-02-07T09:54:12 +22ms service=default e=Unable to connect. Is the computer able to access the url? rejection ERROR 2026-02-07T09:54:12 +0ms service=default e=Unable to connect. Is the computer able to access the url? rejection
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8894