Errors make updating and other operations impossible
complete
William Júnior Dias
Several errors occur, making it impossible to perform any operation. Data updating is also compromised by discrepancies that do not reflect reality and sometimes do not display any information.
Console:
CiV3Dbk-.js:1 https://svelte.dev/e/hydration_mismatch
$t @ CiV3Dbk-.js:1
tt @ CiV3Dbk-.js:1
Ue @ CiV3Dbk-.js:1
dr @ DWEt6XAy.js:1
$o @ BsFfBW04.js:2
child @ 0.CiQ9womg.js:7
B6mbBEu7.js:44 ⏳ Initializing AppKit...
B6mbBEu7.js:44 ✅ AppKit initialized
B6mbBEu7.js:44 Resetting wallet...
B6mbBEu7.js:44 Resetting wallet...
B6mbBEu7.js:44 Resetting wallet...
B6mbBEu7.js:44 Resetting wallet...
B6mbBEu7.js:44 ✅ Network changed from undefined to 8453
B6mbBEu7.js:44 Resetting wallet...
B6mbBEu7.js:44 Resetting wallet...
B6mbBEu7.js:44 Resetting wallet...
B6mbBEu7.js:44 ✅ Network changed from undefined to 8453
BA85qoRn.js:1 Discarding cache for address eip155:8453:0x51a5421f5439C9b6a13e3B8675eA67412c70cBb4
B6mbBEu7.js:44 ✅ Wallet changed to 0x51a5421f5439c9b6a13e3b8675ea67412c70cbb4 on 8453
deposits:1 Autofocus processing was blocked because a document already has a focused element.
B6mbBEu7.js:44 ✅ User tokens loaded (22) in 0.661 seconds
B6mbBEu7.js:44 ✅ Cover policies loaded (0) in 0.66 seconds
B6mbBEu7.js:44 ✅ User sickles loaded for 0x51a5421f5439c9b6a13e3b8675ea67412c70cbb4 on 17 chains in 0.869 seconds
B6mbBEu7.js:44 ✅ Automation setting status loaded for 0x51a5421f5439c9b6a13e3b8675ea67412c70cbb4
B6mbBEu7.js:44 ✅ Automation setting status loaded for 0x51a5421f5439c9b6a13e3b8675ea67412c70cbb4
B6mbBEu7.js:44 ✅ Wallet initialization procedure completed in 1.427 seconds
B6mbBEu7.js:44 ✅ Found 2 positions for wallet 0x51a5421f5439c9b6a13e3b8675ea67412c70cbb4 in 1.745 seconds
Invalid keyframe value for property height: NaNpx
Invalid keyframe value for property height: NaNpx
Invalid keyframe value for property height: NaNpx
Invalid keyframe value for property height: NaNpx
DZzO-y2Y.js:1
window.fetch @ DZzO-y2Y.js:1
callApi @ PY02NaDU.js:4
queryActionSteps @ BB4cDfCo.js:1
load @ PY02NaDU.js:4
preview @ PY02NaDU.js:4
POST https://mainnet.base.org/ 429 (Too Many Requests)
window.fetch @ DZzO-y2Y.js:1
Gu.errorInstance.lp.body @ B6mbBEu7.js:38
await in Gu.errorInstance.lp.body
POST https://mainnet.base.org/ 429 (Too Many Requests)
window.fetch @ DZzO-y2Y.js:1
Gu.errorInstance.lp.body @ B6mbBEu7.js:38
await in Gu.errorInstance.lp.body
POST https://mainnet.base.org/ 429 (Too Many Requests)
window.fetch @ DZzO-y2Y.js:1
Gu.errorInstance.lp.body @ B6mbBEu7.js:38
await in Gu.errorInstance.lp.body
window.fetch @ DZzO-y2Y.js:1
callApi @ PY02NaDU.js:4
queryActionSteps @ BB4cDfCo.js:1
load @ PY02NaDU.js:4
preview @ PY02NaDU.js:4
deposits:1 Access to fetch at 'https://base.llamarpc.com/' from origin 'https://vfat.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
DZzO-y2Y.js:1
POST https://base.llamarpc.com/ net::ERR_FAILED 413 (Content Too Large)
window.fetch @ DZzO-y2Y.js:1
Gu.errorInstance.lp.body @ B6mbBEu7.js:38
await in Gu.errorInstance.lp.body
POST https://mainnet.base.org/ 429 (Too Many Requests)
window.fetch @ DZzO-y2Y.js:1
Gu.errorInstance.lp.body @ B6mbBEu7.js:38
await in Gu.errorInstance.lp.body
POST https://mainnet.base.org/ 429 (Too Many Requests)
window.fetch @ DZzO-y2Y.js:1
Gu.errorInstance.lp.body @ B6mbBEu7.js:38
await in Gu.errorInstance.lp.body
inpage.js:1 MetaMask - RPC Error: Non-200 status code: '429' {code: -32603, message: "Non-200 status code: '429'", data: {…}, stack: '{\n "code": -32603,\n "message": "Non-200 status c…fbeogaeaoehlefnkodbefgpgknn/common-2.js:1:1391130'}
B6mbBEu7.js:44 ✅ Found 2 positions for wallet 0x51a5421f5439c9b6a13e3b8675ea67412c70cbb4 in 4.315 seconds
DZzO-y2Y.js:1
POST https://mainnet.base.org/ 429 (Too Many Requests)
window.fetch @ DZzO-y2Y.js:1
Gu.errorInstance.lp.body @ B6mbBEu7.js:38
await in Gu.errorInstance.lp.body
vfat.io
complete
vfat.io
Hello, there's a few different things going on here. For the first one about Svelte it can be fixed with a browser restart typically.
The RPC too many request issues are something we are actively working on, we currently use RPCs as a failsafe to load user positions, which helps in case our database is delayed for example.
For the rebalance issue this could be if the position shown is not up to date (due to RPC failure). Were you able to transact in the end?
William Júnior Dias
vfat.io I managed to perform the operation after hours of trying...