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
Programs with many accounts break the UI arrow relationship indicators. Nonetheless, with our testnet marketplace, ~2000 accounts, all seem to appear correctly on the UI. I could scroll to see them all, even if the arrows didn't point right.
Additionally, when I tried with our mainnet marketplace ~0.5 MM accounts, even node.js broke when pulling the accounts. This leads me to think the underlying strategy should differ for large real-world apps.
Evidence
arrow relationship indicator breaks
node.js maximum call stack size exceeded
Proposed Solution/Improvement
I suggest modifying the UI to allow for "progressive pulling." Pull the main programs and some accounts instead of pulling every account at the start. Then, add buttons on the UI to load more optionally, populating the UI as the accounts load.
This would first make it a cleaner and unloaded UI, enabling progressive visualization of large programs and relationships while reducing the heavy load Node.js has to take at the tool startup.
Great tool!
The text was updated successfully, but these errors were encountered:
Bug Description
Programs with many accounts break the UI arrow relationship indicators. Nonetheless, with our testnet marketplace,
~2000 accounts
, all seem to appear correctly on the UI. I could scroll to see them all, even if the arrows didn't point right.Additionally, when I tried with our mainnet marketplace
~0.5 MM accounts
, even node.js broke when pulling the accounts. This leads me to think the underlying strategy should differ for large real-world apps.Evidence
Proposed Solution/Improvement
I suggest modifying the UI to allow for "progressive pulling." Pull the main programs and some accounts instead of pulling every account at the start. Then, add buttons on the UI to load more optionally, populating the UI as the accounts load.
This would first make it a cleaner and unloaded UI, enabling progressive visualization of large programs and relationships while reducing the heavy load Node.js has to take at the tool startup.
Great tool!
The text was updated successfully, but these errors were encountered: