Skip to content
This repository was archived by the owner on Dec 8, 2025. It is now read-only.

refactor: update error capture method to disable relay connection errors to be catched - #443

Open
enesozturk wants to merge 1 commit into
mainfrom
refactor/handle-timeout-and-relay-connection-errors
Open

enesozturk wants to merge 1 commit into
mainfrom
refactor/handle-timeout-and-relay-connection-errors

Conversation

@enesozturk

@enesozturk enesozturk commented Feb 20, 2024 •

Copy link
Copy Markdown
Contributor

Description

  • Update the error handling while subscribing to dApp. Return better messages to the user so they can have feedback in case they have network-related issues.
  • Not capture the Relay connection issues to Sentry

Type of change

  • New feature (non-breaking change which adds functionality)

Fixes/Resolves (Optional)

Sentry issuef

Checklist:

  • I have performed a self-review of my own code
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules

@vercel

vercel Bot commented Feb 20, 2024

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
app-web3inbox ❌ Failed (Inspect) Feb 20, 2024 1:31pm

Comment thread src/utils/error.ts
}

switch (error?.message) {
case errorCodeMessageMap.socketStalled:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if it stalls while updating

This branch had an error being deployed

1 failed deployment
Preview — 6c79700d Deployed Feb 20, 2024 by vercel[bot]
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants