-
Notifications
You must be signed in to change notification settings - Fork 1.2k
π 0.22.0 Release #756
Comments
@kumavis how is the testing on ipld/js-ipld#78 going? I'm really tempted in cutting this release and enable people to experiment the DAG API plus not have troubles installing it from npm and then releasing a patch version with all the ethereum resolvers. Thoughts? |
Extra two issues to handle: |
eth-resolvers are ready to go |
Last mile for this release, Orbit testing with the new js-ipfs :)orbit-dbCurrently, not every test of orbit-db passes on master, before the link
orbit-coreIt fails on test:
This is due to the change on IPFS creation, now when you create an instance, you have to do:
@haadcode could you prepare orbit-core for the new version? ipfs-logSame problem as orbit-core
|
Working on it |
@diasdavid I updated all repos for this. You should be able to run the tests with latest
I ran tests for all the above repos with |
just need to bump dep |
@haadcode that is an easy fix, pubsub is now behind an EXPERIMENTAL boolean as recommended by @whyrusleeping Let me know if you have success after enabling PubSub, which is disabled by default. As for the rest, AWESOME ππ½π€π½ |
@diasdavid I added the flag to the IPFS init sequence as described in the doc: https://github.com/haadcode/ipfs-daemon/blob/master/src/ipfs-node-daemon.js#L40. Did I miss something? |
Oh, that means something is broken. What does |
Empty array, |
It means that your peers are not connected. Where is the swarm.connect call? Can you verify that it returns with success? |
There's no swarm.connect call. Previously, the peers always found each other automatically. |
Can you do a |
Found the issue, you were subscribing to a topic and waiting for peers in another topic, that is why there was peers in the swarm but never in the topic pool:
Removing the |
Got greenlight from @haadcode β³οΈ |
\o/ https://github.com/ipfs/js-ipfs/releases
|
π "Wow" π |
We are close to cut a 0.22.0 release that includes a ton of bug fixes and new features in IPLD land.
Highlights
β New API: DAG - Manipulate all your IPLD format objects
Now you can use a new DAG API to create dag-pb, dag-cbor or any IPLD Format compatible node really! Consult https://github.com/ipfs/interface-ipfs-core/tree/master/API/dag to learn how to use this new API.
β Test codebase refactor
We've removed a lot of duplicated and dead code from tests in js-ipfs and js-ipfs-api, tests now run faster and are more easy to write. This refactor also fixed a release bug on js-ipfs-api that would make the process run out of memory when running aegir-release.
β WebWorker support. π @dryajov
β Documentation
The README was updated to make it more clear where the project roadmap lives and how the codebase is structured. You can now find a diagram for the code architecture too.
Examples were updated and polished.
β
--hashAlg
and--format
support on the Block API. π @kumavisβ Railing is now optional
Enable Railing (connecting to the bootstrapers) is now an 'experimental' feature, enable it with the
BOOTSTRAP
env variable. This enables you to fetch content with js-ipfs that is available on the gateways.β Bug fixes
Release check list
~
instead of^
Fails on .init()Β #755What you can do to help get release done faster
Test your code against js-ipfs master and let us know if you find any hiccups?
The text was updated successfully, but these errors were encountered: