[POC] Poll and Sockets #128
Draft
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
Update command to test local gem command changes
jenshenny
force-pushed
the
safari-fallback
branch
from
4ae74bc
to
ca19136
Compare
Bumps [ossf/scorecard-action](https://github.com/ossf/scorecard-action) from 2.1.3 to 2.2.0. - [Release notes](https://github.com/ossf/scorecard-action/releases) - [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md) - [Commits](ossf/scorecard-action@80e868c...08b4669) --- updated-dependencies: - dependency-name: ossf/scorecard-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [dtolnay/rust-toolchain](https://github.com/dtolnay/rust-toolchain) from fc3253060d0c959bea12a59f10f8391454a0b02d to 0e66bd3e6b38ec0ad5312288c83e47c143e6b09e. - [Release notes](https://github.com/dtolnay/rust-toolchain/releases) - [Commits](dtolnay/rust-toolchain@fc32530...0e66bd3) --- updated-dependencies: - dependency-name: dtolnay/rust-toolchain dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
…ons/dtolnay/rust-toolchain-0e66bd3e6b38ec0ad5312288c83e47c143e6b09e Bump dtolnay/rust-toolchain from fc3253060d0c959bea12a59f10f8391454a0b02d to 0e66bd3e6b38ec0ad5312288c83e47c143e6b09e
…ons/ossf/scorecard-action-2.2.0 Bump ossf/scorecard-action from 2.1.3 to 2.2.0
Small refactor for Gem::Resolver
Merge URI-0.12.2 for Bundler
Changelogs for RubyGems 3.4.15 and Bundler 2.4.15
Exclude test files from release package
When dependencies in path sources have changed, we'll be re-resolving, and we can't really know whether the resolution will be valid or invalid for the Ruby platform, so skip the removal in that case.
Minor cleanups in Bundler specs
Changelogs for RubyGems 3.4.16 and Bundler 2.4.16
…_messages Avoid printing "Using ..." messages when version has not changed
Avoid unnecessary work for private local gem installation
Previously, when sorting and comparing git Gemfile vs lockfile sources during `bundler/setup` to figure out whether we need to re-resolve or not, we would try to find the default branch if nothing more specific was specified in the Gemfile. If the git cache has been deleted thought, that would fail. The error would still be swallowed (and the branch would simply not be displayed), but trying to clone would still generate the side effect of creating the parent folder for the clone. That could affect non-writable systems that don't expect `bundler/setup` to write to the filesystem at all. To fix this, override `Bundler::Source::Git#identifier` to use exclusively static information, so it does not even try to clone the repo nor generate any side effects.
## What was the end-user or developer problem that led to this PR? The old URL https://github.com/testdouble/standard is mentioned. ## What is your fix for the problem, implemented in this PR? This PR updates to the new URL https://github.com/standardrb/standard.
Update GitHub organization of Standard Ruby
Fix `bundler/setup` unintendedly writing to the filesystem
…e-bundler Introduce bundle config set version feature
Changelogs for RubyGems 3.4.17 and Bundler 2.4.17
Fix directory of cargo test app in Dependabot
Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.58 to 0.9.79. - [Release notes](https://github.com/oxidize-rb/rb-sys/releases) - [Commits](oxidize-rb/rb-sys@v0.9.58...v0.9.79) --- updated-dependencies: - dependency-name: rb-sys dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…rubygems/test_gem_ext_cargo_builder/custom_name/ext/custom_name_lib/rb-sys-0.9.79 Bump rb-sys from 0.9.58 to 0.9.79 in /test/rubygems/test_gem_ext_cargo_builder/custom_name/ext/custom_name_lib
jenshenny
force-pushed
the
safari-fallback
branch
from
dda6243
to
dead211
Compare
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.
What was the end-user or developer problem that led to this PR?
What is your fix for the problem, implemented in this PR?
Make sure the following tasks are checked