-
Notifications
You must be signed in to change notification settings - Fork 97
Create 2018-09-10--js-core-dev-team-weekly.md #695
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,144 @@ | ||
# ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 September 10, 2018 | ||
|
||
- **Lead:** Alan Shaw | ||
- **Notetaker:** @jacobheun | ||
- **Attendees:** | ||
- @alanshaw | ||
- @achingbrain | ||
- @travisperson | ||
- @jacobheun | ||
- @vasco-santos | ||
- @vmx | ||
- **Recording:** https://youtu.be/KhsdFb_b8Yo | ||
|
||
## Agenda | ||
|
||
- Ask everyone to put their name into the list of attendees | ||
- Round of updates | ||
- What have you accomplished since the last Weekly? | ||
- Were there any blockers? If so, which ones? Is it still blocked? Why? | ||
- What is the next important thing you should focus on? | ||
- Ask for general questions. Could be things like: | ||
- I'm stuck with something, I don't know who to ask. Who knows who to ask? | ||
- Who can help me with xyz? | ||
- Plan this week | ||
- Select issues to work on | ||
- Review remaining issues if there is time left | ||
|
||
## Notes | ||
|
||
### Week Update | ||
|
||
@alanshaw | ||
- Done: | ||
- Published release candidate for `js-ipfs` 0.32.0-rc.1 and 0.32.0-rc.2 | ||
- Test stabilisation work [#1541](https://github.com/ipfs/js-ipfs/pull/1541) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nice! We should avoid the global flags though, they will hide tests that are slow when they shouldn't be. |
||
- Sent PR for faster startup time when using CLI with no daemon running [#1542](https://github.com/ipfs/js-ipfs/pull/1542) | ||
- Many fixes to API docs [#1538](https://github.com/ipfs/js-ipfs/pull/1538) | ||
- Made progress adding `--cid-base` option to _all_ relevant `js-ipfs` commands (working in branch [feat/cid-base-option](https://github.com/ipfs/js-ipfs/tree/feat/cid-base-option)) | ||
- Blocked: | ||
- Jenkins npm errors frequent [#51](https://github.com/ipfs/testing/issues/51) | ||
- Jenkins windows workers out of space [#135](https://github.com/ipfs/testing/issues/135) | ||
- Next: | ||
- Release js-ipfs 0.32 | ||
- Finish `--cid-base` option | ||
- Create interop tests for block store get by CIDv0/1 | ||
- Implement block store get by CIDv0/1 | ||
|
||
@achingbrain | ||
- Done: | ||
- Spun up npm registry at https://registry.js.ipfs.io | ||
- Play along at home with `npm i --registry=https://registry.js.ipfs.io` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Wooot!! :D This is nice :D @achingbrain, Does it have the whole registry? What's the repo size? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. At the moment it's configured to only fetch individual tarballs when they've been requested by a client and aren't present locally as the EC2 instance it's running on doesn't have enough storage to eagerly fetch the whole thing. This issue is to sort out a more scalable storage solution, once that's in place we can hold whole the whole repo: ipfs/infra#432 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Did you have the chance to download the entire registry locally to see the size it took? |
||
- Fixed flaky pubsub tests https://github.com/ipfs/interop/pull/33 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👏🏽👏🏽👏🏽 |
||
- Made pin tests less flaky https://github.com/ipfs/interop/pull/34 | ||
- Consolidated HTTP API https://github.com/ipfs-shipyard/js-ipfs-http | ||
- Blocked: | ||
- Create S3 backend for npm-on-ipfs: https://github.com/ipfs/infrastructure/issues/432 | ||
- Remove password requirement from libp2p-keychain? https://github.com/libp2p/js-libp2p-keychain/pull/25 | ||
- Support OTP in Aegir: https://github.com/ipfs/aegir/pull/260 | ||
- Next: | ||
- Continue HTTP API https://github.com/ipfs-shipyard/js-ipfs-http | ||
|
||
@jacobheun | ||
- Done: | ||
- Added core state machine logic for libp2p-switch. Started working on the connection state machine logic. Reviewed several existing issues surrounding the [state machine issue for libp2p](https://github.com/libp2p/js-libp2p/issues/98) to make sure that is incorporated. | ||
- Have a basic demo of delegated routing working against a local instance of the supporting go-ipfs branch. Will demo today at IPFS All Hands. | ||
- I believe there is a performance issue here when the numbner of providers is low. The http query stays open until at least 20 providers are found. I've seen this stay open for 30+ minutes. | ||
- Patch release for libp2p-switch (0.40.8) for dependency updates, including multistream-select already piped fix version bump. | ||
- Blocked: | ||
- Delegated routing support in [go-ipfs#4594](https://github.com/ipfs/go-ipfs/pull/4595). | ||
- Next: | ||
- libp2p-tcp transport isnt currently dialble over dns, looking into this (mafmt needs to be updated for this to work) | ||
- Continue with state machine updates for libp2p connections | ||
|
||
@vasco-santos | ||
- Done: | ||
- IPNS over Pubsub OKR | ||
- Created `js-datastore-pubsub` module | ||
- Initial implementation of [ipfs/js-datastore-pubsub#1](https://github.com/ipfs/js-datastore-pubsub/pull/1) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @vasco-santos, This design is incorrect. We don't want a datastore to publish every key that gets stored. Do you have a diagram of how things get plugged together? The IPNS system (module) should use PubSub to publish and subscribe to the new keys and then make the decision of storing them in the DataStore. @vasco-santos do you have a diagram of your architecture? We can workshop this together if you need. |
||
- `js-ipns` | ||
- Added records validator [js-ipns#5](https://github.com/ipfs/js-ipns/pull/5) | ||
- Added routing key format [js-ipns#7](https://github.com/ipfs/js-ipns/pull/7) | ||
- PRs approved, merged and released | ||
- `js-ipfs` | ||
- Implementation almost done | ||
- fix: libp2p records for IPNS should be signed | ||
- https://github.com/ipfs/js-ipfs/pull/1543 | ||
- Blocked: | ||
- IPNS | ||
- [interop#26](https://github.com/ipfs/interop/pull/26) | ||
- Needs js-ipfs new release with IPNS, and to be reviewed | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does it work locally? |
||
- IPNS over Pubsub | ||
- [interface-ipfs-core#361](https://github.com/ipfs/interface-ipfs-core/pull/361) | ||
- Needs to be approved, merged and released | ||
- [js-ipfs-api](https://github.com/ipfs/js-ipfs-api/pull/846) | ||
- Needs the previous PR released, followed by being approved, merged and released | ||
- Next: | ||
- Fix code review for `js-datastore-pubsub` | ||
- Add tests for `js-ipfs` implementation of `IPNS over Pubsub` and create PR | ||
- Fix IPNS over Pubsub PRs feedback | ||
- Create interop tests for `IPNS over Pubsub` | ||
- Create tests for testing DHT interop | ||
|
||
@hugomrdias | ||
- Done | ||
- ipfs chunked add | ||
- [#1540](https://github.com/ipfs/js-ipfs/pull/1540) | ||
- ipfs-api chunked add | ||
- [#851](https://github.com/ipfs/js-ipfs-api/pull/851) | ||
- [stream-http/tree/fix/body-handling](https://github.com/hugomrdias/stream-http/tree/fix/body-handling) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @hugomrdias Does this break/change interop with go-ipfs? |
||
- Blocked | ||
- Next | ||
- finish add chunked | ||
- fix `stream-http` | ||
- Doesn't work inside a service-worker on Firefox [848#issuecomment-419887279](https://github.com/ipfs/js-ipfs-api/issues/848#issuecomment-419887279) | ||
- add api add chunked to big data tests | ||
- finish chore/improve-docs branch documentation.js for some reason doesn't find `factory-daemon`. `npx documentation serve ./js-ipfsd-ctl/src/index.js -w -f html` | ||
- PR aegir to update documentation.js | ||
|
||
|
||
@travisperson | ||
- Done: | ||
- iptb [go/js/browser demo](https://asciinema.org/a/zn07AUFgZ5RWzAwit7mjpdqvW) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👏🏽👏🏽👏🏽👏🏽👏🏽 |
||
- Blocked: | ||
- Next: | ||
- Merge iptb browser plugin | ||
- Build test harness | ||
|
||
@vmx | ||
- Done: | ||
- Conference (FOSS4G) and travels in Tanzania | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a url to the talk?? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's not easy to link to it, here's the best one I could find: https://fkih7q.attendify.io/schedule.html#9YYK6haD49GaQsORLc |
||
- Blocked: Nope | ||
- Next: | ||
- Recording my FOSS4G talk at ahome | ||
- GraphSync, GraphSync, GraphSync! | ||
|
||
|
||
### Questions | ||
|
||
### Other notes | ||
|
||
- Alex away 14th-17th September | ||
- Alan away 1st-5th October | ||
|
||
<!-- After each call, the notetaker submits a PR to ipfs/pm to store the notes on the meeting-notes folder --> |
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.
@alanshaw, releasing RC is an aegir step or is it done manually?
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.
Manual step at the moment until aegir supports it.
Details: ipfs/js-ipfs#1533
PR adding step to release doc: ipfs/js-ipfs#1536
Tracking issue in AEgir: ipfs/aegir#261