Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to show Yield Farming List And Disappeared Pairs #1

Closed
harwinvoid opened this issue May 20, 2021 · 1 comment
Closed

Failed to show Yield Farming List And Disappeared Pairs #1

harwinvoid opened this issue May 20, 2021 · 1 comment

Comments

@harwinvoid
Copy link
Owner

harwinvoid commented May 20, 2021

Basic Info

platform: Chrome of latest version and Metamask

address: 0x1e037d858131227F007f0b723cEc08c181f386BC

User Report

some body in sushi chinese tg report a problem like below
the problem has been last at least 24 hours, kind of troubled him.
it only occured when user connet to his metamask wallet.
if used a empty account, there is no problem
same problem with same account on mobile metamask

image

Analysis Process

  1. since he can open sushi.com, it means it's not a netwok problem
  2. then guide user to open the developer console of Chrome.
  3. user shared a Screenshot like be below

image

it seem a crash in JavaScript, may be there is bug when calc assets in user wallet。

Tg ScreenShot

image

One More Question

image

In the yield List, the KM/USDT/ETH disappered.

image

in the console

image

there is 4 invalid pairs , and below contain a USDT asset, I guess the disappered one is in invalid list.

address: "0x9DA0B987A14708023Fe0530272d7017C87F77840"
assetAddress: "0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2"
collateralAddress: "0xdAC17F958D2ee523a2206206994597C13D831ec7"
masterContract: "0x2cBA6Ab6574646Badc84F0544d05059e57a5dc42"

is there any relation with the disappeared pairs with the BigNumer error?

relate link: web3/web3.js#2077

@omakasebar
Copy link

omakasebar commented May 21, 2021

The first error has not been able to reproduce, ask the user to try again. There doesn't seem to be any BigNumber errors in the interface. Can the user identify the exact url he or she is on and the exact steps the user took to encounter this error? Did they click on something, etc? Is the user using a custom RPC network?

Additionally the second error seems to be a user error. I can see kmWETH/USDT just fine when I search kmWETH-. Additionally if the user has some staked on this interface the user should see the balance at the top of the table. You can reproduce user balances by going to http://app.sushi.com/yield/debug/0x1e037d858131227F007f0b723cEc08c181f386BC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants