You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The discussions test is currently failing due to RPC timeouts when accessing both https://free.rpc.fastnear.com and https://rpc.mainnet.near.org. These RPC endpoints do not fetch data older than a certain timestamp. The test was functional until now because the queried transaction was within the supported timeframe. However, as the transaction aged, the test started failing. To address this, we need to use an archival RPC, which supports querying historical data.
Describe the solution you'd like
Switch to an archival RPC (https://archival-rpc.mainnet.near.org) to ensure historical data can be queried reliably.
Revisit the design and usage of the API proxy for tests to ensure stability, especially for local development and widget-related features like the "Don't ask again" checkbox.
Describe alternatives you've considered
Modify the test to use an archival RPC endpoint (ARCHIVAL_RPC_URL).
Use a local proxy solution for archival RPC requests (MOCK_ARCHIVAL_RPC_URL).
Additional context
The RPC proxy is used to serve widgets locally, ensuring features like the "Don't ask again" checkbox appear in the transaction confirmation modal. Standard BOS-workspace setups lack this feature without the proxy.
Switching to archival RPCs is necessary to handle the historical data required by this test.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The discussions test is currently failing due to RPC timeouts when accessing both
https://free.rpc.fastnear.com
andhttps://rpc.mainnet.near.org
. These RPC endpoints do not fetch data older than a certain timestamp. The test was functional until now because the queried transaction was within the supported timeframe. However, as the transaction aged, the test started failing. To address this, we need to use an archival RPC, which supports querying historical data.Describe the solution you'd like
https://archival-rpc.mainnet.near.org
) to ensure historical data can be queried reliably.Describe alternatives you've considered
ARCHIVAL_RPC_URL
).MOCK_ARCHIVAL_RPC_URL
).Additional context
The text was updated successfully, but these errors were encountered: