-
Notifications
You must be signed in to change notification settings - Fork 71
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
feat: Curio support #1914
feat: Curio support #1914
Conversation
ca0b4b5
to
94ec60d
Compare
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 am not sure about why need some of these changes.
@@ -167,3 +179,158 @@ func NewPieceDoctor(cfg *config.Boost) func(lc fx.Lifecycle, maddr lotus_dtypes. | |||
return doc | |||
} | |||
} | |||
|
|||
type boostPieceStoreWrapper struct { |
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.
Why do we need this wrapper in Boost?
return fmt.Errorf("getting reader over piece %s: %w", pieceCid, err) | ||
var reader types.SectionReader | ||
|
||
reader, err := os.OpenFile(inFile, os.O_RDONLY, 0) |
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.
This will result in incorrect offset for CIDs. We read from pieceReader because we need exact location in the unsealed copy to get the data back.
This PR implements some things needed for Curio to talk to boost; Not sure how I managed to not PR this before.