-
Notifications
You must be signed in to change notification settings - Fork 7
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: add blob protocol to infra integration tests #369
feat: add blob protocol to infra integration tests #369
Conversation
View stack outputs
|
5d2baf9
to
c034c3a
Compare
c034c3a
to
95e7adb
Compare
// Register the index with the service | ||
await Index.add(serviceProps.conf, indexLink, { connection: serviceProps.connection }) | ||
// Register an upload with the service | ||
await Upload.add(serviceProps.conf, root, shards, { connection: serviceProps.connection }) |
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 are we not using the @web3-storage/w3up-client
for this?
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.
See comment above
// Add blob using custom client to be able to access receipts
I want to have the CIDs for the Receipts so that I can make sure they exist. The upload client is fully used on integration.test.js
, this is a more internal testing. Also, this way, I have access to the CID of the index that I can also check is written
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 will improve docs though
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.
probably, I could also do a follow up where in the client we export a function that does this that client also uses internally so that we do not need to maintain this code here
t.is(shards.length, 1) | ||
|
||
// Invoke upload/add | ||
await Upload.add(serviceProps.conf, root, shards, { connection: serviceProps.connection }) |
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 not use an older version of the client for this?
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 attempted to do so, but there were some dependencies collision and I opted to get this similarly to blob
tersts
d952e87
to
a258a88
Compare
d5f51b9
to
678c2d7
Compare
678c2d7
to
b45289d
Compare
quick follow up from #369
Adds integration tests for blob implementation started on #353 .
This test aims to test all the main flows that MUST happen once a Blob is written:
w3up-client
filecoin/offer
In addition,
store-add
tests are added independently to make sure old clients keep operation for writes + reads!Follow ups:
w3s.link
hostname