generated from ipfs/ipfs-repository-template
-
Notifications
You must be signed in to change notification settings - Fork 100
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: mega migration #206
Closed
feat: mega migration #206
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit was moved from ipfs/go-namesys@64c4398
This commit was moved from ipfs/go-namesys@cbcc19c
This commit was moved from ipfs/go-fetcher@7fc88c4
Otherwise, we'll panic. This commit was moved from ipfs/go-blockservice@39f3c34
fix: handle missing session exchange in Session This commit was moved from ipfs/go-blockservice@6f1e7bb
This commit was moved from ipfs/go-fetcher@d4187fb
This commit was moved from ipfs/go-fetcher@9362e80
Use eth.domains instead of eth.link for .eth names This commit was moved from ipfs/go-namesys@c17fc94
…lder-chooser Add NodeReifier to fetcher config This commit was moved from ipfs/go-fetcher@3290471
This commit was moved from ipfs/go-ipfs-provider@f8b63a1
This outputs a missage that blames a specific sife for not having DNSLink record. For example, the error message looks like: `could not resolve name: bad.example.net is missing DNSLink record (https://docs.ipfs.io/concepts/dnslink/)` The "could not resolve name" portion is still present because the returned error wraps the original ErrResolveFailed, allowing code to test if the error is an ErrorResolveFailed error. This commit was moved from ipfs/go-namesys@4e753ad
Co-authored-by: Marcin Rataj <lidel@lidel.org> This commit was moved from ipfs/go-namesys@3d90782
This commit was moved from ipfs/go-fetcher@69e4d9b
move block service implementation to its own package. move traversal helpers to traversal directory This commit was moved from ipfs/go-fetcher@3978480
This commit was moved from ipfs/go-fetcher@febb8de
define an interface for making new instances of the fetcher This commit was moved from ipfs/go-fetcher@571518e
update parameter names on interface to be more clear This commit was moved from ipfs/go-fetcher@5325cff
This commit was moved from ipfs/go-unixfs@77ff92d
This commit was moved from ipfs/go-unixfs@7e96bad
…fix-types Separate implementation and fix types This commit was moved from ipfs/go-fetcher@d24b660
This commit was moved from ipfs/go-fetcher@6e0ef2a
* Properly report DNSLink errors Only report that there is no DNSLink for a name when there are no DNSLink TXT records available for that name. For all other errors, such as being offline, report the more general "cannot resolve name" error. * Document that we give precedence to good results from looking up DNSLinks in TXT records from `"_dnslink."+fqdn` over results from `fqdn`. This commit was moved from ipfs/go-namesys@22432d1
…filesize-raw correct file size for raw node This commit was moved from ipfs/go-unixfs@a20f6cb
Remove ref to dag pb This commit was moved from ipfs/go-fetcher@808966e
…eadme chore: update the Usage part of readme This commit was moved from ipfs/go-ipfs-provider@f194251
This commit was moved from ipfs/go-path@32d3a4f
This commit was moved from ipfs/go-namesys@a718e16
This commit was moved from ipfs/go-namesys@1077b5a
This commit was moved from ipfs/go-namesys@ea4eec1
This commit was moved from ipfs/go-namesys@a360c66
This commit was moved from ipfs/go-ipfs-pinner@9abb80f
This commit was moved from ipfs/go-path@6793198
This commit was moved from ipfs/go-ipfs-pinner@1174ddd
Similar to blockservice.NewWriteThrough(). Currently the default blockstore trades read amplification for every write. While this is fine in cases where writes are very expensive and the datastore offers a quick Has() method, it is not always the case. Some datastore backends may be better off just getting all the writes no matter what. At least I would like to try it out. This commit was moved from ipfs/go-ipfs-blockstore@498084a
This commit was moved from ipfs/go-ipfs-blockstore@7ad322b
This commit was moved from ipfs/go-ipfs-blockstore@1323a47
* feat: use peer.String() to use a human-readable cache key * fix: use normalized key representation * fix: cache ipns key can be any format This commit was moved from ipfs/go-namesys@af35385
- updates docs link to .tech - makes it very clear what is missing This commit was moved from ipfs/go-namesys@e30a7b8
Jorropo
force-pushed
the
migrate
branch
7 times, most recently
from
March 15, 2023 20:58
a7aa5c5
to
3de0a04
Compare
Migrated repos: - github.com/ipfs/interface-go-ipfs-core => ./coreiface - github.com/ipfs/go-unixfs => ./unixfs - github.com/ipfs/go-pinning-service-http-client => ./pinning/remote/client - github.com/ipfs/go-path => ./path - github.com/ipfs/go-namesys => ./namesys - github.com/ipfs/go-mfs => ./mfs - github.com/ipfs/go-ipfs-provider => ./provider - github.com/ipfs/go-ipfs-pinner => ./pinning/pinner - github.com/ipfs/go-ipfs-keystore => ./keystore - github.com/ipfs/go-filestore => ./filestore - github.com/ipfs/go-ipns => ./ipns - github.com/ipfs/go-blockservice => ./blockservice - github.com/ipfs/go-ipfs-chunker => ./chunker - github.com/ipfs/go-fetcher => ./fetcher - github.com/ipfs/go-ipfs-blockstore => ./blockstore - github.com/ipfs/go-ipfs-posinfo => ./filestore/posinfo - github.com/ipfs/go-ipfs-util => ./util - github.com/ipfs/go-ipfs-ds-help => ./datastore/dshelp - github.com/ipfs/go-verifcid => ./verifcid - github.com/ipfs/go-ipfs-exchange-offline => ./exchange/offline - github.com/ipfs/go-ipfs-routing => ./routing - github.com/ipfs/go-ipfs-exchange-interface => ./exchange Updates #202
Jorropo
commented
Mar 20, 2023
) | ||
|
||
replace github.com/ipfs/go-merkledag => github.com/Jorropo/go-merkledag v0.3.1-0.20230320131104-a3ff80a097d8 |
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.
This was referenced Mar 21, 2023
@Jorropo : discussion tiems from 2023-03-21 about getting this landed:
@guseggert review this über migration |
Closed in favor of #220 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrated repos:
Updates #202