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
What is really valuable information when debugging anything Neighbourhood, LinkLanguage and Holochain related is the diff graph in Perspective-diff-sync DHTs. But logging it automatically on every call bloats the log way too much.
It would be really great to have a mechanism to retrieve the graph (in dot-graph format) when needed.
An idea would be:
adding a debug(): string function to the LinksAdapter interface
implementing that function inside PDiff-sync to return the current graph
adding a function to the GraphQL interface (and Ad4mClient): ad4m.neighbourhoods.debug(pID)
adding a button to the Launcher (in expert mode - on neighbourhoods) to trigger this new function and display the graph (in text format, and if easy also rendered..)
The text was updated successfully, but these errors were encountered:
What is really valuable information when debugging anything Neighbourhood, LinkLanguage and Holochain related is the diff graph in Perspective-diff-sync DHTs. But logging it automatically on every call bloats the log way too much.
It would be really great to have a mechanism to retrieve the graph (in dot-graph format) when needed.
An idea would be:
debug(): string
function to theLinksAdapter
interfaceAd4mClient
):ad4m.neighbourhoods.debug(pID)
The text was updated successfully, but these errors were encountered: