Release v0.13.0 #9023
Merged
Release v0.13.0 #9023
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
It's still possible to disable signing. However, it's no longer possible to enable signing _and_ disable strict signature verification.
…igning-option feat: remove strict signing pubsub option.
…rs.i.ipfs.io fixes 1) of #7343
…_quic_listening default config: add QUIC listening ports + quic to mars.i.ipfs.io
…p_peers fix boostrap peers
…move_config_option QUIC: remove experimental config option
fix: include key size in key init method
Co-authored-by: Will <will.scott@protocol.ai>
feat: add peering service config section
We should have a more permanent way to configure security transports, but experimental flags are a quick and unstable way to do this without making any promises.
…xperiments feat: add an option for security transport experiments
There's no reason to give the group access to these files by default.
fix: remove group permissions
These let us zero-encode "default" to "null" (and omit it with "omitempty") so we don't have to hard code the default in the config.
…/prioritizing transports
This was never included in a release, and has been replaced by a flexible transport prioritization system.
This makes it easier to resolve these fields.
Co-authored-by: Adin Schmahmann <adin.schmahmann@gmail.com>
Co-authored-by: Adin Schmahmann <adin.schmahmann@gmail.com>
It's not a part of the JSON spec.
feat: add a transports section for enabling/disabling transports
(cherry picked from commit 4798777)
https://github.com/libp2p/go-libp2p/releases/tag/v0.19.2 (cherry picked from commit 657d4f4)
fix(node/libp2p): disable rcmgr checkImplicitDefaults (cherry picked from commit e23a461)
It works only on some platforms, and does not work reliably. This corrects our error of not setting expectations right. (cherry picked from commit 53299e8)
Fixes #8957 The context was only checked while reading data. Not while writing data to the http connection. So since the data flow through an io.Pipe the closing didn't flowed through and left the writer open hanging. Co-authored-by: Antonio Navarro Perez <antnavper@gmail.com> (cherry picked from commit 7892cc9)
(cherry picked from commit a72753b)
This fix safelists additional headers allowing JS running on websites to read them when IPFS resource is downloaded via Fetch API. These headers provide metadata necessary for making smart caching decisions when IPFS resources are downloaded via Service Worker or a similar middleware on the edge. (cherry picked from commit 650bc24)
This periodically logs how many times Resource Manager limits were exceeded. If they aren't exceeded, then nothing is logged. The log levels are at ERROR log level so that they are shown by default. The motivation is so that users know when they have exceeded resource manager limits. To find what is exceeding the limits, they'll need to turn on debug logging and inspect the errors being logged. This could collect the specific limits being reached, but that's more complicated to implement and could result in much longer log messages. (cherry picked from commit 5615715)
* Do not connect to external nodes on ipfs as a lib example. It was causing some build timeouts error because CircleCI was throttling WAN connections. It closes #8956 * style: rename node vars since this is example, this should make things easier to follow Co-authored-by: Marcin Rataj <lidel@lidel.org> (cherry picked from commit e8f1ce0)
(cherry picked from commit f720172)
* fix: adjust rcmgr limits for accelerated DHT client rt refresh The Accelerated DHT client periodically refreshes its routing table, including at startup, and if Resource Manager throttling causes the client's routing table to be incomplete, then content routing may be degraded or broken for users. This adjusts the default limits to a level that empirically doesn't cause Resource Manager throttling during initial DHT client bootstrapping. Ideally the Accelerated DHT client would handle this scenario more gracefully, but this works for now to unblock the 0.13 release. * Set default outbound conns unconditionally This also sets the default overall conns as a function of the outbound and inbound conns, since they are adjusted dynamically, and it makes the intention of the value clear. * increase min FD limit (cherry picked from commit b8617b9)
* feat: disable resource manager by default We are disabling this by default for v0.13 as we work to improve the UX around Resource Manager. It is still usable and can be enabled in the IPFS config with "ipfs config --bool Swarm.ResourceMgr.Enabled true". We intend to enable Resource Manager by default in a subsequent release. * docs(config): Swarm.ResourceMgr disabled by default Co-authored-by: Marcin Rataj <lidel@lidel.org> (cherry picked from commit b1c051d)
(cherry picked from commit 0a01574)
* feat: upgrade to go-libp2p-kad-dht@v0.16.0 * rename "cid format --codec" to "cid format --mc" * refactor(test): from --codec to --mc Co-authored-by: Marcin Rataj <lidel@lidel.org> (cherry picked from commit 8d7ed00)
(cherry picked from commit 2e170a4)
(cherry picked from commit 9db6641)
Closed
Jorropo
approved these changes
Jun 8, 2022
aschmahmann
approved these changes
Jun 8, 2022
|
@guseggert this looks right, but why can't this branch be rebased? We should be merging here anyway, but this seems a bit off. Is it a version.go thing or something else? |
|
@aschmahmann IIUC, it can't be rebased because the commits can't be applied individually without a conflict, probably due to all those old commits from go-ipfs-config |
|
Could also be from the sheer size of this, e.g. https://github.community/t/weird-problem-with-cannot-be-rebased-due-to-conflicts/178433/4 |
|
This is just a Git defaults (or GitHub depending on how you look at it) thing. Basically git rebase drops all merge commits even if there is stuff in the merge commit (which happens for version.go when we merge In any event using merge commits into @guseggert merge and continue the release dance (signing the tag in release, merging back into master, etc.) tomorrow 🙏. |
|
I believe you have the wrong Gus :)
…On Wed, Jun 8, 2022 at 5:05 PM Adin Schmahmann ***@***.***> wrote:
@gus <https://github.com/gus> Eggert this looks right, but why can't this
branch be rebased? We should be merging here anyway, but this seems a bit
off. Is it a version.go thing or something else?
—
Reply to this email directly, view it on GitHub
<#9023 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAA6PHXNQH3UL23ZEKLVU3VOEDI5ANCNFSM5YHXOYOQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Justin "Gus" Knowlden
|
hacdias
pushed a commit
to ipfs/boxo
that referenced
this pull request
Jan 27, 2023
Release v0.13.0 This commit was moved from ipfs/kubo@c9d51bb
gammazero
pushed a commit
to ipfs/boxo
that referenced
this pull request
Sep 28, 2023
Release v0.13.0 This commit was moved from ipfs/kubo@c9d51bb
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.
No description provided.