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
The new record is app.bsky.feed.repost/3lhhvdr62cze2 down near the bottom. This is an entry on a tree node of height=1, and the creation seems to have split two nodes at height=0. One of those nodes is included in the message blocks, but the other is not.
I see one of these every few seconds on the global firehose, and so far all have come via bridgy. This is new code on my end and it is totally possible I have a bug.
I don't think isn't super urgent to fix right now. We will be making small tweaks to the firehose format soon (had a short conversation with snarfed about that yesterday), and it might make sense to hold off on diving in to the MST code until the updated specs are ready (hopefully in the next week or two).
The text was updated successfully, but these errors were encountered:
I'm writing an updated MST implementation to validate events on the firehose, and it failed on this commit message from
atproto.brid.gy
:(the content of this event is the creation of a single repost, which I don't think raises too many privacy concerns)
Here is what the partial tree (loaded from the blocks) looks like:
The new record is
app.bsky.feed.repost/3lhhvdr62cze2
down near the bottom. This is an entry on a tree node of height=1, and the creation seems to have split two nodes at height=0. One of those nodes is included in the message blocks, but the other is not.I see one of these every few seconds on the global firehose, and so far all have come via bridgy. This is new code on my end and it is totally possible I have a bug.
I don't think isn't super urgent to fix right now. We will be making small tweaks to the firehose format soon (had a short conversation with snarfed about that yesterday), and it might make sense to hold off on diving in to the MST code until the updated specs are ready (hopefully in the next week or two).
The text was updated successfully, but these errors were encountered: