Giters
filecoin-project
/
go-legs
Does the legwork for go-data-transfer
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
20
Watchers:
9
Issues:
38
Forks:
14
filecoin-project/go-legs Issues
`dtsync` never calls block hook if blocks are found locally
Closed
2 years ago
Comments count
2
`httpsync` does not verify that digest in CID matches the content
Closed
2 years ago
Use IPLD bind node to describe httpsync head message
Updated
2 years ago
A libp2p host cannot be a publisher and subscriber
Closed
2 years ago
Be able to have a legs publisher publish multiple chains
Updated
2 years ago
Sync from unknown peer hangs for a minute before erroring despite context timeout
Updated
2 years ago
Comments count
1
Subscriber `httppeerstore` is never updated with address from announcement messages
Closed
2 years ago
Add the ability to resume partially failed syncs from head
Updated
2 years ago
Interface hasn't been unified between HTTP and graphsync
Updated
2 years ago
Comments count
1
re-broadcast received http advertisements
Closed
2 years ago
Comments count
3
`TransportConfigurer` is only set when dtsync publisher is instantiated from existing data transfer
Closed
2 years ago
Comments count
1
Update go-legs for data transfer IPLD based Vouchers
Updated
2 years ago
Comments count
3
legs subscriber must allow datatrasfer to be optionally set
Closed
2 years ago
Comments count
4
allow config to limit maximum number of allowed concurrent connections
Updated
2 years ago
head protocol ID ends up with double `/` for topic names starting with `/`
Closed
2 years ago
Comments count
1
not fully configured host can lead to panic
Closed
2 years ago
Comments count
1
gossipsub messages should not be relayed to all peers for security reasons
Updated
2 years ago
Remove topic from head publisher protocol ID
Closed
2 years ago
Comments count
6
Expose an API to set the initial head CID without publishing it
Closed
2 years ago
Subscriber.Sync should not try to open pull request when target CID is `undef
Closed
2 years ago
manual release created (v0.2.1)
Closed
2 years ago
Comments count
1
manual release created (v0.2.0)
Closed
2 years ago
Comments count
1
make an easier api on the HTTP publisher to write out expected files, rather than needing to manually hook linksystem
Updated
2 years ago
publish/announce against an alternative multiaddr
Closed
2 years ago
Comments count
2
Subscriber can only get 32 DAG heads if a publisher publish at a high speed rate
Closed
2 years ago
Comments count
2
`QueryRootCid` fails to deserialize if there is no current head
Closed
2 years ago
`OnChange` does not get notified on explicit `Sync`
Closed
2 years ago
Comments count
1
pubsub announcements should include provider multiaddr to allow subscribers to connect
Closed
2 years ago
Comments count
1
Allow the recursion limit mode to be configurable
Closed
2 years ago
Need to document or revise use of context
Closed
2 years ago
Comments count
1
Provide control over selectors
Updated
3 years ago
Constrain allowed selectors to those in expected fetches
Updated
3 years ago
Add ability to add a validation function in the publisher to accept/reject data transfers
Closed
2 years ago
Use t.Cleanup instead of defer in tests
Closed
3 years ago
Exchange retries in subscriber
Closed
2 years ago
Comments count
3
chore: Remove test datastore and use datastore sync
Closed
3 years ago
chore: go-ipld-prime dependency
Closed
3 years ago
Update README examples
Closed
3 years ago