Implossible to track meteora position due to 429 error

[chaotic-cat]

Describe the bug

I've launched gateway locally using certs from humming bot. Added wallet and tried to open meteora position. Position opened, but I've got 500 error. Gateway showed this [partial output]:

Server responded with 429 Too Many Requests.  Retrying after 1000ms delay...
Server responded with 429 Too Many Requests.  Retrying after 2000ms delay...
Server responded with 429 Too Many Requests.  Retrying after 500ms delay...
Server responded with 429 Too Many Requests.  Retrying after 4000ms delay...
2025-04-03 06:10:12 | error |   unhandledRejection: 429 Too Many Requests:  {"jsonrpc":"2.0","error":{"code": 429, "message":"Too many requests for a specific RPC call"}, "id": "5274851a-7166-40fd-b487-305524308864" } 

Error: 429 Too Many Requests:  {"jsonrpc":"2.0","error":{"code": 429, "message":"Too many requests for a specific RPC call"}, "id": "5274851a-7166-40fd-b487-305524308864" } 

Steps to reproduce

1. Add solana wallet
2. Try to open meteora position

Release version

2.4.0

Type of installation

Source

Attach required files

No response

[mlguys]

This error meant you got rate limit from your RCP node, are you using public node or paid node from other providers like Quicknode?

[chaotic-cat]

I don't use any paid providers. Anyway, I expect this code to be able to handle errors like this.

[mlguys]

I don't use any paid providers. Anyway, I expect this code to be able to handle errors like this.

Public nodes are very easy to get rate limited, I would recommend you get a paid node instead