-
Notifications
You must be signed in to change notification settings - Fork 642
Tracking issue for cargo update
#1805
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
Labels
C-tracking-issue
Category: A tracking issue for an RFC, an unstable feature, or an issue made of many parts
Comments
This list is only the direct dependencies that were updated, not transitive dependencies, right? |
I basically did a 3-way diff of the lines at the bottom of |
jtgeibel
added a commit
to jtgeibel/crates.io
that referenced
this issue
Aug 23, 2019
Docopt is only used directly in the `render_readme` binary, though this does transitively update some crates that are used in production. Refs rust-lang#1265, rust-lang#1805
smarnach
pushed a commit
to smarnach/crates.io
that referenced
this issue
Aug 26, 2019
Docopt is only used directly in the `render_readme` binary, though this does transitively update some crates that are used in production. Refs rust-lang#1265, rust-lang#1805
jtgeibel
added a commit
to jtgeibel/crates.io
that referenced
this issue
Oct 5, 2019
This commit bumps a few additional packages that could be related to the segfaults seen in production. See rust-lang#1805 for more info. `cargo update -p backtrace -p rustc-demangle` ``` Updating backtrace v0.3.3 -> v0.3.38 Updating backtrace-sys v0.1.16 -> v0.1.31 Removing dbghelp-sys v0.2.0 Updating rustc-demangle v0.1.5 -> v0.1.16 ```
bors
added a commit
that referenced
this issue
Nov 7, 2019
Bump `backtrace` and `rustc-demangle` This commit bumps a few additional packages that could be related to the segfaults seen in production. See #1805 for more info. `cargo update -p backtrace -p rustc-demangle` ``` Updating backtrace v0.3.3 -> v0.3.38 Updating backtrace-sys v0.1.16 -> v0.1.31 Removing dbghelp-sys v0.2.0 Updating rustc-demangle v0.1.5 -> v0.1.16 ```
bors
added a commit
that referenced
this issue
Nov 7, 2019
Bump `backtrace` and `rustc-demangle` This commit bumps a few additional packages that could be related to the segfaults seen in production. See #1805 for more info. `cargo update -p backtrace -p rustc-demangle` ``` Updating backtrace v0.3.3 -> v0.3.38 Updating backtrace-sys v0.1.16 -> v0.1.31 Removing dbghelp-sys v0.2.0 Updating rustc-demangle v0.1.5 -> v0.1.16 ```
jtgeibel
added a commit
to jtgeibel/crates.io
that referenced
this issue
Nov 15, 2019
Refs: rust-lang#1805
Merged
bors
added a commit
that referenced
this issue
Nov 22, 2019
Bump r2d2 `cargo update -p r2d2` Refs: #1805
jtgeibel
added a commit
to jtgeibel/crates.io
that referenced
this issue
Nov 23, 2019
bors
added a commit
that referenced
this issue
Nov 25, 2019
Update chrono, dotenv, num-*, migrations_macros, and derive_deref Overall, this drops 16 old versions of dependencies. The `num-*` crates are on the list at #1805, but overall I think this is low risk to deploy together. * `cargo update -p num -p num-iter -p num-traits --aggressive` * `cargo update -p chrono` * `cargo update -p migrations_macros -p derive_deref` * Update to latest `dotenv`
bors
added a commit
that referenced
this issue
Jan 6, 2020
Bump a few more backend dependencies Bumping a few more dependencies from #1805. * `utf-8` from 0.7.1 to 0.7.5 * `maplit` 1.0.0 to 1.0.2 * `filetime` from 0.1.14 to 0.1.15 r? @carols10cents
This was referenced Feb 19, 2020
bors
added a commit
that referenced
this issue
Feb 23, 2020
Aggressively update conduit-hyper and reqwest This series does an aggressive update for `conduit-hyper` and then `reqwest`. This portion of the dependency tree has been updated recently and we aren't using `conduit-hyper` in production yet, so this should be fairly low risk even though it bumps a lot of crates. The commit messages show the detailed output of each command. cc #1805 r? @JohnTitor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-tracking-issue
Category: A tracking issue for an RFC, an unstable feature, or an issue made of many parts
We've tried twice now to land a broad
cargo update
against the backend, but both attempts resulted in segfaults in production. This was first attempted in #1263 (April 2018), and again in #1756 (June 2019).I've been examining the differences between that first attempt, current master, and their common ancestor. Following is a list of crates which were bumped in that first attempt but which have not yet been superseded by a more recent version on master. My hope is that the problematic change will be within this set of crates.
I've added columns to capture the version bump from the 2nd attempt, and the most recent (possibly semver incompatible) published version. I've highlighted in bold the places where the version bump in the 2nd attempt was identical to the first.
aho-corasickbacktracedocoptfiletimelazy_staticmaplitnumnum-integernum-iteropenssl-prober2d2regexregex-syntaxrustc-demanglethread_localutf-8I plan to start bumping crates on this list in an attempt to track down this old bug.
The text was updated successfully, but these errors were encountered: