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
Integrate dag store into mount implementation #565
Merged
aarshkshah1992
merged 1 commit into
feat/mount-implementation
from
feat/mount-implementation-dagstore
Jul 9, 2021
Merged
Integrate dag store into mount implementation #565
aarshkshah1992
merged 1 commit into
feat/mount-implementation
from
feat/mount-implementation-dagstore
Jul 9, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dirkmc
force-pushed
the
feat/mount-implementation-dagstore
branch
7 times, most recently
from
July 8, 2021 12:26
fea026e
to
bcc6fc6
Compare
6 tasks
dirkmc
force-pushed
the
feat/mount-implementation-dagstore
branch
2 times, most recently
from
July 9, 2021 09:32
db723d7
to
d6ed761
Compare
dirkmc
force-pushed
the
feat/mount-implementation-dagstore
branch
from
July 9, 2021 09:42
d6ed761
to
c61c717
Compare
aarshkshah1992
added a commit
that referenced
this pull request
Jul 11, 2021
* dagstore lotus mount impl * refactor: nicer error messages * mount api tests * refactor: integrate dag store (#565) Co-authored-by: Dirk McCormick <dirkmdev@gmail.com>
raulk
reviewed
Jul 11, 2021
Comment on lines
+56
to
+62
// TODO: Can I rely on AcquireShard to return an error if the context times out? | ||
//select { | ||
//case <-ctx.Done(): | ||
// return ctx.Err() | ||
//case res := <-resch: | ||
// return nil, res.Error | ||
//} |
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.
Not yet. If you need this feature we need to prioritise this: filecoin-project/dagstore#39
Comment on lines
+91
to
+97
// TODO: Can I rely on RegisterShard to return an error if the context times out? | ||
//select { | ||
//case <-ctx.Done(): | ||
// return ctx.Err() | ||
//case res := <-resch: | ||
// return res.Error | ||
//} |
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.
Same as above!
dirkmc
added a commit
that referenced
this pull request
Jul 13, 2021
* refactor: integrate dag store into retrieval market * fix all tests and the padding issue * refactor: move mount from shared testutil to dagstore dir * refactor: add tests for lazy blockstore * refactor: code cleanup * feat: update go-car to latest * Dagstore lotus mount Implementation with tests (#564) * dagstore lotus mount impl * refactor: nicer error messages * mount api tests * refactor: integrate dag store (#565) Co-authored-by: Dirk McCormick <dirkmdev@gmail.com> * some storage market fixes by aarsh * fix: better error messages in DAG store wrapper * refactor: simplify mock dag store wrapper * fix: TestBounceConnectionDealTransferOngoing * refactor: remove some commented out code * refactor: closable blockstore interface to use full blockstore * fix: TestBounceConnectionDealTransferUnsealing * refactor: add comment explaining lotus mount template * test: verify that the lazy blockstore is only initialized once * fix: comment * fix: always finalize blockstore before reaching complete state (#567) Co-authored-by: aarshkshah1992 <aarshkshah1992@gmail.com>
aarshkshah1992
added a commit
that referenced
this pull request
Jul 13, 2021
* dag store lotus mount * storage client code complete-tests remain * storage miner first draft * second draft * provider state tests are now working * most unit tests working and more unit tests * refactor: car store trackers (#559) * Apply suggestions from code review Co-authored-by: dirkmc <dirkmdev@gmail.com> * nits and review * integration testing changes * storage test harness changes * added more TODOs * fix itests for storage * get offline deal tests working * tests work * more tests * integration tests * fix blockstore finalize * Integrate CARv2 blockstore in the retrieval market (#560) * refactor: integrate dag store into retrieval market * fix all tests and the padding issue * refactor: move mount from shared testutil to dagstore dir * refactor: add tests for lazy blockstore * refactor: code cleanup * feat: update go-car to latest * Dagstore lotus mount Implementation with tests (#564) * dagstore lotus mount impl * refactor: nicer error messages * mount api tests * refactor: integrate dag store (#565) Co-authored-by: Dirk McCormick <dirkmdev@gmail.com> * some storage market fixes by aarsh * fix: better error messages in DAG store wrapper * refactor: simplify mock dag store wrapper * fix: TestBounceConnectionDealTransferOngoing * refactor: remove some commented out code * refactor: closable blockstore interface to use full blockstore * fix: TestBounceConnectionDealTransferUnsealing * refactor: add comment explaining lotus mount template * test: verify that the lazy blockstore is only initialized once * fix: comment * fix: always finalize blockstore before reaching complete state (#567) Co-authored-by: aarshkshah1992 <aarshkshah1992@gmail.com> Co-authored-by: dirkmc <dirkmdev@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.