-
Notifications
You must be signed in to change notification settings - Fork 188
fix: remove unique events logic from the ChainGetEvents API
#6286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 15 commits
069e46e
d1990da
b15c1bf
af90795
0cf17fd
b7328eb
d3f0c50
6fb70ec
51f61bf
d7775e7
2acca34
49f17a6
10e21f8
488e5c3
a3fa8f1
de08a14
c78de22
39bd1e6
eec093f
93edf96
b8976c3
8aea806
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,2 @@ | ||
| # This list contains potentially broken methods (or tests) that are ignored. | ||
| # They should be considered bugged, and not used until the root cause is resolved. | ||
|
|
||
| # Ignoring ChainGetEvents for now, as we are not sure if we should get duplicated events or not. | ||
| # TODO(forest): https://github.com/ChainSafe/forest/issues/6271. | ||
| !Filecoin.ChainGetEvents |
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -10,6 +10,7 @@ use std::{ | |||||||
| use crate::Config; | ||||||||
| use crate::db::migration::v0_22_1::Migration0_22_0_0_22_1; | ||||||||
| use crate::db::migration::v0_26_0::Migration0_25_3_0_26_0; | ||||||||
| use crate::db::migration::v0_31_0::Migration0_26_0_0_31_0; | ||||||||
| use anyhow::Context as _; | ||||||||
| use anyhow::bail; | ||||||||
| use itertools::Itertools; | ||||||||
|
|
@@ -155,6 +156,8 @@ pub(super) static MIGRATIONS: LazyLock<MigrationsMap> = LazyLock::new(|| { | |||||||
| create_migrations!( | ||||||||
| "0.22.0" -> "0.22.1" @ Migration0_22_0_0_22_1, | ||||||||
| "0.25.3" -> "0.26.0" @ Migration0_25_3_0_26_0, | ||||||||
| // v0.30.0 is the oldest supported version, and it uses the same schema as v0.26.0. | ||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
The current version is the oldest supported version, no?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually I took this to be the oldest version for DB, but you're correct the latest version will be the oldest version.
|
||||||||
| "0.30.0" -> "0.31.0" @ Migration0_26_0_0_31_0, | ||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure I get it, normally you are supposed to create LATEST_TO_NEW migration. So it should be rather
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So here is what I was thinking. The last schema change was for the
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I will change them to follow the |
||||||||
| ); | ||||||||
|
|
||||||||
| /// Creates a migration chain from `start` to `goal`. The chain is chosen to be the shortest | ||||||||
|
|
||||||||
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.
We don't put in the README things that are not visible to the user in any way.
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.
My main motivation for this was to inform the users that the
ChainGetEventsAPI will return error, if the events are not available in parity DB just like lotus.I will update my wording for more appropriate log.
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.
Reworded the log.