Skip to content
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

Update Rust crate fixedbitset to 0.5.7 #237

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nextest-bot
Copy link
Collaborator

@nextest-bot nextest-bot commented Feb 28, 2024

This PR contains the following updates:

Package Type Update Change
fixedbitset dependencies minor 0.4.2 -> 0.5.7

Release Notes

petgraph/fixedbitset (fixedbitset)

v0.5.7

Compare Source

Optimized the Clone::clone_from implementation to avoid allocations and redundant copies.

v0.5.6

Compare Source

Fixed FixedBitset not implementing Send/Sync due to the stack size shrink.

v0.5.5

Compare Source

  • #​116: Add functions for counting the results of a set operation (union_count,
    intersection_count, difference_count, symmetric_difference_count) by @​james7132.
  • #​118: Shrink the stack size of FixedBitset. There should be zero stack size overhead
    compared to a Vec.
  • #​119: Fix builds for wasm32.
  • #​120: Add more utility functions that were previously missing from the public interface:
    contains_any_in_range, contains_all_in_range, minimum, maximum, is_full, count_zeroes, and remove_range.
  • #​121: Add support for SIMD acceleration for AVX builds.

v0.5.4

Compare Source

#​112: Fix undefined behavior in IntoOnes and setup testing with MIRI by @​SkiFire13

v0.5.3

Compare Source

#​109: Fix non-x86(_64) builds by @​james7132

v0.5.2

Compare Source

v0.5.1

Compare Source

  • #​102: Added contains_unchecked, insert_unchecked, put_unchecked,
    set_unchecked, toggle_unchecked, removed_unchecked, copy_bit_unchecked unsafe variants of the safe functions, by @​james7132
  • #​103: Added into_ones which returns a owned iterator over the one
    values from a bitset, by @​james7132.
  • #​104: Implemented DoubleEndedIterator for Union, Intersection,
    Difference, and SymmetricDifference , by @​james7132.

v0.5.0

Compare Source

  • #​74: Accelerated set operations (union, intersection, difference,
    symmetric difference) by using larger blocks internally, by @​james7132.
  • #​88: Added FixedBitSet::remove by @​james7132.
  • #​89: Added FixedBitSet::zeros and the Zeros iterator by @​james7132.
  • #​92: Added FixedBitSet::grow_and_insert function, a
    non-panicking version of insert that grows the underlying storage as need, by @​shuoli84.
  • #​98: Ones now implements DoubleEndedIterator, by @​tikhu.
  • #​99: Breaking change: serde now serializes and deserializes from a little-endian encoded
    raw byte buffer. Existing stored instances of the serialized bitsets will need to be
    re-encoded.
  • Bumped MSRV to 1.56.

Configuration

📅 Schedule: Branch creation - "after 8pm,before 6am" in timezone America/Los_Angeles, Automerge - "after 8pm,before 6am" in timezone America/Los_Angeles.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@nextest-bot nextest-bot added the dependencies Pull requests that update a dependency file label Feb 28, 2024
@nextest-bot
Copy link
Collaborator Author

nextest-bot commented Feb 28, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path guppy/Cargo.toml --package [email protected] --precise 0.5.7
    Updating crates.io index
error: failed to select a version for the requirement `fixedbitset = "^0.4.0"`
candidate versions found which didn't match: 0.5.7
location searched: crates.io index
required by package `petgraph v0.6.4`
    ... which satisfies dependency `petgraph = "^0.6.4"` (locked to 0.6.4) of package `guppy v0.17.5 (/tmp/renovate/repos/github/guppy-rs/guppy/guppy)`
    ... which satisfies path dependency `guppy` (locked to 0.17.5) of package `cargo-guppy v0.1.0 (/tmp/renovate/repos/github/guppy-rs/guppy/cargo-guppy)`
perhaps a crate was updated and forgotten to be re-vendored?

@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch 2 times, most recently from 01d4ccd to d4ad4cf Compare March 1, 2024 04:49
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from d4ad4cf to cbbe19d Compare March 16, 2024 09:49
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.0 Update Rust crate fixedbitset to 0.5.1 Mar 16, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from cbbe19d to 5ee417f Compare March 19, 2024 06:35
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.1 Update Rust crate fixedbitset to 0.5.2 Mar 19, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from 5ee417f to 30844a3 Compare March 19, 2024 07:10
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.2 Update Rust crate fixedbitset to 0.5.1 Mar 19, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from 30844a3 to d9911a0 Compare March 19, 2024 07:34
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.1 Update Rust crate fixedbitset to 0.5.3 Mar 19, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from d9911a0 to 03ecfa6 Compare March 20, 2024 03:11
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.3 Update Rust crate fixedbitset to 0.5.4 Mar 20, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from 03ecfa6 to 7f50b08 Compare March 22, 2024 03:11
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.4 Update Rust crate fixedbitset to 0.5.5 Mar 22, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from 7f50b08 to 58e60ec Compare March 22, 2024 05:28
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.5 Update Rust crate fixedbitset to 0.5.6 Mar 22, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from 58e60ec to 14dc0c0 Compare April 15, 2024 04:12
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.6 Update Rust crate fixedbitset to 0.5.7 Apr 15, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch 2 times, most recently from 77518de to 209143f Compare May 5, 2024 03:11
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.7 Update Rust crate fixedbitset to 0.5.0 May 5, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from 209143f to 17fad3a Compare May 7, 2024 03:12
@nextest-bot nextest-bot changed the title Update Rust crate fixedbitset to 0.5.0 Update Rust crate fixedbitset to 0.5.7 May 7, 2024
@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from 17fad3a to 7ce8573 Compare August 1, 2024 07:24
@nextest-bot
Copy link
Collaborator Author

nextest-bot commented Aug 1, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path guppy/Cargo.toml --package [email protected] --precise 0.5.7
    Updating crates.io index
error: failed to select a version for the requirement `fixedbitset = "^0.4.0"`
candidate versions found which didn't match: 0.5.7
location searched: crates.io index
required by package `petgraph v0.6.5`
    ... which satisfies dependency `petgraph = "^0.6.5"` (locked to 0.6.5) of package `guppy v0.17.10 (/tmp/renovate/repos/github/guppy-rs/guppy/guppy)`
    ... which satisfies path dependency `guppy` (locked to 0.17.10) of package `cargo-guppy v0.1.0 (/tmp/renovate/repos/github/guppy-rs/guppy/cargo-guppy)`

@nextest-bot nextest-bot force-pushed the renovate/fixedbitset-0.x branch from 7ce8573 to cf86e3a Compare December 22, 2024 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant