Crash report: `Error: invalid decimal value (argument="value", value="0,077", code=INVALID_ARGUMENT, version=bignumber/5.6.2)`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
URL
https://app.uniswap.org/#/nfts/profile
Error
Error: invalid decimal value (argument="value", value="0,077", code=INVALID_ARGUMENT, version=bignumber/5.6.2)
Stacktrace
Error: invalid decimal value (argument="value", value="0,077", code=INVALID_ARGUMENT, version=bignumber/5.6.2)
at e.value (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:102827)
at e.value (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:102971)
at e.value (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:103050)
at v (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:2048905)
at s (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:474654)
at c (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:474721)
at https://app.uniswap.org/static/js/main.3752d112.chunk.js:1:1431697
at Array.map (<anonymous>)
at f (https://app.uniswap.org/static/js/main.3752d112.chunk.js:1:1431548)
at ue (https://app.uniswap.org/static/js/main.3752d112.chunk.js:1:1354319)
Device data
{
"ua": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36",
"browser": {
"name": "Chrome",
"version": "107.0.0.0",
"major": "107"
},
"engine": {
"name": "Blink",
"version": "107.0.0.0"
},
"os": {
"name": "Mac OS",
"version": "10.15.7"
},
"device": {},
"cpu": {}
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash at https://app.uniswap.org/#/nfts/profile using the reported Chrome and macOS environment, then trace the minified stack entries in the reported JavaScript chunks back to the source. The issue is resolved when the NFT profile no longer crashes on the decimal value "0,077" and a regression check covers the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100