search

fluree / core

Fluree releases and public bug reports
0 stars 0 forks source link

Add Testing Capacity for IPFS #79

Open aaj3f opened 5 months ago

aaj3f commented 5 months ago

Description

We've recently seen some regression on IPFS/IPNS support, largely because we don't have support for testing those configurations. @bplatz has fixed most (maybe all) of those regressions, but the issue of creating a test suite for the capabilities still stands

The issue is a bit complex, because to test, there needs to exist an IPFS node and, for IPNS, there needs to be some private key management. This means a some more involved bootstrapping as part of the test suite.

This ticket solely describes the need to architect that kind of test chassis and ensure that supported IPFS/IPNS config/features are testable and included in the tests for the code

cap10morgan commented 5 months ago

Blocked pending resolution of how to handle IPNS TTLs. See discussion in Slack.

cap10morgan commented 5 months ago

I think this is going to require at least https://github.com/fluree/core/issues/85 to be implemented first, and then use another name service as primary / only to be able to run automated tests against IPFS storage.

aaj3f commented 3 months ago

Unblocking this now that the nameservice work it depended on is complete. Let's restrict this to IPFS & the default (i.e. non-IPNS name service) for now, and I'll make a separate ticket for IPNS-specific tests

cap10morgan commented 2 months ago

Is this unblocked? #85 is still "in progress"

aaj3f commented 2 months ago

Should be unblocked w/ the PR of fluree/db#758

May want to wait confirmation from @JaceRockman on QS/CT implementation of db after that PR