This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Keep track when we try and fail to process a pulled event #13589
Keep track when we try and fail to process a pulled event #13589
Changes from 29 commits
e0d7fab
b8d55d3
f63d823
bec26e2
fee37c3
d1290be
f9119d0
f5c6fe7
16ebec0
ce07aa1
5811ba1
cf2b093
cbb4194
621c5d3
75c07bb
783cce5
54ef84b
e4192d7
7a44932
86d98ca
1464101
71c7738
df8c76d
d45b078
33ad64e
63bec99
31d7502
0b5f1db
4ce7709
d3a1f84
1347686
57182dc
e58bc65
70019d2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if this is the right place to record this? What is the failure mode you're trying to catch here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this will catch the
FederationError
whereWe can't get valid state history
,But perhaps you also mean that we should also generally look for any exceptions and record there as well? That sounds reasonable for recording whatever failure that happens 👍:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I was mostly just thinking that its not obvious that this particular spot is the right place in the handling. For example, I think by this point we've already attempted to try and refetch events that have bad signatures returned by
/backfill
.I guess this is a good first step, and we can always add it the checks in more places later.