Skip to content

Tags: facebookincubator/reindeer

Tags

v2025.03.24.00

Toggle v2025.03.24.00's commit message
Update Blazesym to get the fix for adreno lib

Summary:
# Stack
* Fix symbolication related bugs

# Diff
* Updating Blazesym to get the fix for the adreno library
  * https://www.internalfb.com/diff/D68869307
* Fix compilation for `Source`

Reviewed By: simpleton, andreh7

Differential Revision: D71616027

fbshipit-source-id: 9c63507c88b174dcf2aa3995ed82058328d8c69a

v2025.03.17.00

Toggle v2025.03.17.00's commit message
Update platform010 & platform010-aarch64 symlinks

Summary:
Release notes:

- https://blog.rust-lang.org/2025/01/09/Rust-1.84.0.html
- https://blog.rust-lang.org/2025/01/30/Rust-1.84.1.html

Relevant changes:

- `--target wasm32-wasi` renamed to `--target wasm32-wasip1`
- `temporary_cstring_as_ptr` lint renamed and extended as `dangling_pointers_from_temporaries` to cover Vec and other types
- `feature(exposed_provenance)` stabilized
- `feature(pin_deref_mut)` stabilized
- `feature(strict_provenance)` stabilized
- `fuzzy_provenance_casts` lint is now behind `feature(strict_provenance_lints)`
- inherent methods for locking on `std::fs::File` collide with `fs2::FileExt`
  - [`.lock_exclusive()`](https://docs.rs/fs2/0.4.3/fs2/trait.FileExt.html#tymethod.lock_exclusive) -> [`.lock()`](https://doc.rust-lang.org/1.84.1/std/fs/struct.File.html#method.lock)
  - [`.lock_shared()`](https://docs.rs/fs2/0.4.3/fs2/trait.FileExt.html#tymethod.lock_shared) -> [`.lock_shared()`](https://doc.rust-lang.org/1.84.1/std/fs/struct.File.html#method.lock_shared)
  - [`.try_lock_exclusive()`](https://docs.rs/fs2/0.4.3/fs2/trait.FileExt.html#tymethod.try_lock_exclusive) -> `fs2::FileExt::try_lock_exclusive`
  - [`.try_lock_shared()`](https://docs.rs/fs2/0.4.3/fs2/trait.FileExt.html#tymethod.try_lock_shared) -> `fs2::FileExt::try_lock_shared`
  - the fs2 try-locking methods have different signature and semantics than File's [`try_lock()`](https://doc.rust-lang.org/1.84.1/std/fs/struct.File.html#method.try_lock) and [`try_lock_shared()`](https://doc.rust-lang.org/1.84.1/std/fs/struct.File.html#method.try_lock_shared); we will want to refactor to use the new standard methods, but this will entail more care than belongs in this diff
- expanded `unused_must_use` lint
- expanded `unused_parens` lint
- (leftover from 1.82) `std::panic::PanicInfo` deprecated in favor of `PanicHookInfo`
- forward-compatibility lints regarding never-type fallback
- new clippy lints:
  - `clippy::extra_unused_lifetimes`
  - `clippy::needless_as_bytes`
  - `clippy::unnecessary_map_or`

Differential Revision: D70601924

fbshipit-source-id: 10f89f92ad44564802b12e7f092e2719ba2fcd98

v2025.03.10.00

Toggle v2025.03.10.00's commit message
Update platform010 & platform010-aarch64 symlinks

Summary:
Release notes:

- https://blog.rust-lang.org/2025/01/09/Rust-1.84.0.html
- https://blog.rust-lang.org/2025/01/30/Rust-1.84.1.html

Relevant changes:

- `--target wasm32-wasi` renamed to `--target wasm32-wasip1`
- `temporary_cstring_as_ptr` lint renamed and extended as `dangling_pointers_from_temporaries` to cover Vec and other types
- `feature(exposed_provenance)` stabilized
- `feature(pin_deref_mut)` stabilized
- `feature(strict_provenance)` stabilized
- `fuzzy_provenance_casts` lint is now behind `feature(strict_provenance_lints)`
- inherent methods for locking on `std::fs::File` collide with `fs2::FileExt`
  - [`.lock_exclusive()`](https://docs.rs/fs2/0.4.3/fs2/trait.FileExt.html#tymethod.lock_exclusive) -> [`.lock()`](https://doc.rust-lang.org/1.84.1/std/fs/struct.File.html#method.lock)
  - [`.lock_shared()`](https://docs.rs/fs2/0.4.3/fs2/trait.FileExt.html#tymethod.lock_shared) -> [`.lock_shared()`](https://doc.rust-lang.org/1.84.1/std/fs/struct.File.html#method.lock_shared)
  - [`.try_lock_exclusive()`](https://docs.rs/fs2/0.4.3/fs2/trait.FileExt.html#tymethod.try_lock_exclusive) -> `fs2::FileExt::try_lock_exclusive`
  - [`.try_lock_shared()`](https://docs.rs/fs2/0.4.3/fs2/trait.FileExt.html#tymethod.try_lock_shared) -> `fs2::FileExt::try_lock_shared`
  - the fs2 try-locking methods have different signature and semantics than File's [`try_lock()`](https://doc.rust-lang.org/1.84.1/std/fs/struct.File.html#method.try_lock) and [`try_lock_shared()`](https://doc.rust-lang.org/1.84.1/std/fs/struct.File.html#method.try_lock_shared); we will want to refactor to use the new standard methods, but this will entail more care than belongs in this diff
- expanded `unused_must_use` lint
- expanded `unused_parens` lint
- (leftover from 1.82) `std::panic::PanicInfo` deprecated in favor of `PanicHookInfo`
- forward-compatibility lints regarding never-type fallback
- new clippy lints:
  - `clippy::extra_unused_lifetimes`
  - `clippy::needless_as_bytes`
  - `clippy::unnecessary_map_or`

Differential Revision: D70601924

fbshipit-source-id: 10f89f92ad44564802b12e7f092e2719ba2fcd98

v2025.03.03.00

Toggle v2025.03.03.00's commit message
vendor build time debugging binaries

Summary:
vendoring:
1. measureme summarize
2. measureme crox
3. measureme flamegraph
4. cargo-llvm-lines

which are all used to debug Rust build times (see https://fasterthanli.me/articles/why-is-my-rust-build-so-slow)

vendoring them because otherwise you'd need to go through a whole `rustup` dance on devservers, which is a pain

Reviewed By: guswynn

Differential Revision: D70274479

fbshipit-source-id: 067354cf963c8442fdba6d50bc1600eeeebf8f24

v2025.02.24.00

Toggle v2025.02.24.00's commit message
Add lock_api crate

Summary: This is a pre-req for some Oak targets (`oak-core`).

Reviewed By: henrywang8atfbdotcom

Differential Revision: D69682326

fbshipit-source-id: c4b269ad654d4f6a881245b84016458a301c2f20

v2025.02.17.00

Toggle v2025.02.17.00's commit message
Update to 0.2.100

Summary:
Update wasm-bindgen and wasm-bindgen-cli to version 0.2.100
- Will be required for integrating rerun_c 0.22

Reviewed By: dtolnay

Differential Revision: D69668716

fbshipit-source-id: c554d6d190e3b15b7a9fb5e2c4a76b128ae5c571

v2025.02.10.00

Toggle v2025.02.10.00's commit message
bump git2-rs 0.14->0.20, rusqlite -> 0.32.1, sqlx 0.7.1 -> 0.8.2, bla…

…ke 1.5.1 -> 1.5.5, cargo 0.65 -> 0.86, ...

Summary:
libgit2 fixups are driven by build.rs script in the upstream repo

https://github.com/rust-lang/git2-rs/compare/libgit2-sys-0.14.0+1.5.0..libgit2-sys-0.18.0+1.9.0

libsqlite was previously used from TP2, I'm not sure if there is any policy that require us to use that in third-party-rust as it seems there is a "mixed & match" approach throughout the codebase. I've raised this point here https://fb.workplace.com/groups/rust.foundation.team/permalink/3917712258499630/

allow-large-files

Reviewed By: edward-shen

Differential Revision: D68684463

fbshipit-source-id: 69eab7062e49ed2a7b226113831f5aaf6c4ef790

v2025.02.03.00

Toggle v2025.02.03.00's commit message
Add hyper-util 0.1.6

Summary:
`hyper-util` provides a few goodies for using hyper.

For my use case, more importantly, it allows me to use the version of hyper pulled in by my dependency tree without pulling in the ancient version in rust-third-party.

Reviewed By: zertosh

Differential Revision: D67545898

fbshipit-source-id: 04c5d135d0a92697fcce1ac981a39fe8f077fdae

v2025.01.27.00

Toggle v2025.01.27.00's commit message
upgrade to 0.22.6

Summary: Upgrade `pyo3` to [`0.22.6`](https://fburl.com/g3zxt353)

Reviewed By: zertosh

Differential Revision: D68466072

fbshipit-source-id: 9e52e76164584477fc9a21daefb8a49feaf664c1

v2025.01.20.00

Toggle v2025.01.20.00's commit message
third party: Upgrade `rustc_hash`

Summary:
To 2.1

Unfortunately, I can't remove the old version of the crate. The problem is that it appears in the [public API](https://docs.rs/tiktoken-rs/latest/tiktoken_rs/struct.CoreBPE.html#method.new) of `tiktoken_rs`, which we also import. That crate has a PR to upgrade its dependency [here](zurawiki/tiktoken-rs#95) but that has not been merged. Alternatives here are:

 1. Fork `tiktoken_rs`. This seems worse.
 2. It's strictly speaking possible to use generics combined with some other tricks to avoid needing to name v1 of `FxHashMap` in fbsource. However, that makes that code extraordinarily hard to change and work with, and doesn't seem all that clearly motivated.

If there's something else I should be doing here, all ears

Reviewed By: zertosh

Differential Revision: D68064854

fbshipit-source-id: bd1c96abbc0ebaa178a55826bc85c61eb35e8301