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
{{ message }}
This repository has been archived by the owner on Apr 11, 2022. It is now read-only.
In certain blocks that have many name operations, it takes on the order of minutes for blockstack-cli get_nameops_at to generate a result causing our reverse proxy and/or the user's browser to timeout before the request can return.
This should be fixed once we can migrate to blockstack core http api #7.
In the meantime, I have set up https://explorer.blockstack.org to cache get_nameops_at queries in a local varnish instance. This will speed up requests after the first request but unfortunately won't help with the largest (in terms of number of name operations) of blocks.
The text was updated successfully, but these errors were encountered:
In certain blocks that have many name operations, it takes on the order of minutes for
blockstack-cli get_nameops_at
to generate a result causing our reverse proxy and/or the user's browser to timeout before the request can return.This should be fixed once we can migrate to blockstack core http api #7.
In the meantime, I have set up https://explorer.blockstack.org to cache
get_nameops_at
queries in a local varnish instance. This will speed up requests after the first request but unfortunately won't help with the largest (in terms of number of name operations) of blocks.The text was updated successfully, but these errors were encountered: