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
I'm not sure if that is an intentional behavior of the tool and I'm missing something, but I'm trying to link the score of a peer with its related graft and prunes and I'm unable to locate the actual score in the peer_score_event table.
The schema of the table looks like this:
CREATETABLEIF NOT EXISTS peer_score_event (
id INT GENERATED ALWAYS AS IDENTITY,
peer_id TEXTNOT NULL,
timestampTIMESTAMPTZNOT NULL,
other_peer_id TEXTNOT NULL,
app_specific_score FLOAT8 NOT NULL,
ip_colocation_factor FLOAT8 NOT NULL,
behaviour_penalty FLOAT8 NOT NULL,
PRIMARY KEY (id)
);
meanwhile, the actual trace does record the score as a float64
Description
Hey @iand , great work on this trace-catcher.
I'm not sure if that is an intentional behavior of the tool and I'm missing something, but I'm trying to link the score of a peer with its related graft and prunes and I'm unable to locate the actual
score
in thepeer_score_event
table.The schema of the table looks like this:
meanwhile, the actual trace does record the score as a
float64
Let me know if I'm missing anything here or if I can help you out with anything :)
The text was updated successfully, but these errors were encountered: