Releases: facebookincubator/reindeer
Releases · facebookincubator/reindeer
v2024.07.01.00
buckification Summary: This commit was generated using `mgt import`. buckification for third-party libraries: third-party/pypi/pydantic-core/2.18.4 third-party/pypi/pydantic/2.7.4 uuid_1fe06b2d7bc14c85acc4926e1de8bdac Reviewed By: diliop Differential Revision: D58875150 fbshipit-source-id: 354118a2339c939566f1297734252fe8fe36897f
v2024.06.24.00
Fix typo in buildscript fixups comment (#47) Summary: My understanding is that with this flag reindeer will run the build script, grab it's stdout, assume that the stdout are rustc flags, and use those flags to build the crate. So perhaps this meant to say "Run the buildscript and _extract_ command line args"? Pull Request resolved: https://github.com/facebookincubator/reindeer/pull/47 Reviewed By: shayne-fletcher Differential Revision: D58563898 Pulled By: dtolnay fbshipit-source-id: 6cf1450b17e022049702e104fec8582d2d6cad29
v2024.06.17.00
Fix typo in buildscript fixups comment (#47) Summary: My understanding is that with this flag reindeer will run the build script, grab it's stdout, assume that the stdout are rustc flags, and use those flags to build the crate. So perhaps this meant to say "Run the buildscript and _extract_ command line args"? Pull Request resolved: https://github.com/facebookincubator/reindeer/pull/47 Reviewed By: shayne-fletcher Differential Revision: D58563898 Pulled By: dtolnay fbshipit-source-id: 6cf1450b17e022049702e104fec8582d2d6cad29
v2024.06.10.00
import surge-ping 0.8.1 Summary: import surge-ping to rust. Used in Centinela for the ping plugin. Reviewed By: leoswaldo Differential Revision: D57750591 fbshipit-source-id: ebea0bb4d1ec1fefb523e0b2af9041cfb4f15e36
v2024.06.03.00
import surge-ping 0.8.1 Summary: import surge-ping to rust. Used in Centinela for the ping plugin. Reviewed By: leoswaldo Differential Revision: D57750591 fbshipit-source-id: ebea0bb4d1ec1fefb523e0b2af9041cfb4f15e36
v2024.05.27.00
update platform010 & platform010-aarch64 symlinks Summary: updating from 1.77.1 to 1.78.0 #buildmore Reviewed By: diliop Differential Revision: D57048774 fbshipit-source-id: 3d2a2810ad8cb11b28ac00b8088e9be21ebc59a7
v2024.05.20.00
update platform010 & platform010-aarch64 symlinks Summary: updating from 1.77.1 to 1.78.0 #buildmore Reviewed By: diliop Differential Revision: D57048774 fbshipit-source-id: 3d2a2810ad8cb11b28ac00b8088e9be21ebc59a7
v2024.05.13.00
update platform010 & platform010-aarch64 symlinks Summary: updating from 1.77.1 to 1.78.0 #buildmore Reviewed By: diliop Differential Revision: D57048774 fbshipit-source-id: 3d2a2810ad8cb11b28ac00b8088e9be21ebc59a7
v2024.05.06.00
upgrade to 0.21.1 Summary: NOTE: If your `hg bisect` brings you here & the error you are seeing looks like ` expected Result<&PyAny, PyErr>, found Result<Bound<'_, PyAny>, PyErr>` then see these [migration notes](https://pyo3.rs/v0.21.0/migration.html#from-020-to-021) for the fix or click on `fbcode/security/ace/pyo3/authz.rs` or similar files from bellow to see what the fix is! In order to upgrade `pyo3` to [`0.21.1`](https://github.com/PyO3/pyo3/releases/tag/v0.21.1), the following had to take place: ## [PyO3] * Address [migration notes](https://pyo3.rs/v0.21.0/migration.html#from-020-to-021) for `Bound<'py, T>` * Address [#3595](https://github.com/PyO3/pyo3/pull/3595) - this is done in a crude way for now since there are many call sites depending on `fbcode/dba/rust/common/service_address/py/pyo3_conversion_helper.rs` which would require a more thorough review. * Address [#3821](https://github.com/PyO3/pyo3/pull/3821) - `pyo3-build-config` is now dependent on and used by PyO3 macros. Currently, the only thing that gets checked is `abi3` compatibility. To address that, we introduce a fixup for that automatically generate `pyo3-build-config*.txt` configuration files, given an `fbsource` Python version. We are tryin to stay as close to `pyo3-build-config*.txt` spec as possible even though only a single bool from that file is ever since there is validation for the other fields but also to future proof future changes. By also generating this file ourselves, we prevent PyO3 from attempting to locate a Python interpreter some other way which seems to start leaking into the PyO3 API as an implementation choice already. ## [PyPi + Rust] * Upgrade `orjson` to [`3.10.1`](https://github.com/ijl/orjson/releases/tag/3.10.1) * Added `README.md` notes for future upgrades * Upgrade `py-polars` to [`0.20.22`](https://github.com/pola-rs/polars/releases/tag/py-0.20.22) * Removed `py-polars` and `polars` from `target_os = "windows"`. The `third-party/pypi/polars` Python extension has only been supported for Mac and Linux for a while now so its only natural to do that on the Rust side as well. What is more, `polars-util` is bringing in `stacker = = "0.1.14"` which does not build on Windows mostly because its using a much more recent version of `libc` than we use in `third-party/rust` (see P1228807344) * Upgrade `pydantic-core` to [`2.18.2`](https://github.com/pydantic/pydantic-core/releases/tag/v2.18.2) * Removed old `third-party/pypi/pydantic-core` versions * Upgrade `safetensors` to [`0.4.3`](https://github.com/huggingface/safetensors/releases/tag/v0.4.3) * Patch `third-party/pypi/cryptography/41.0.7` to account for PyO3's [#2975](https://github.com/PyO3/pyo3/pull/2975) (`0.19.0`) where `pyo3::once_cell` was renamed to `pyo3::sync` (see D56826865) * Upgrade `tokenizers` and `tokenizers-python` to [`0.19.1`](https://github.com/huggingface/tokenizers/releases/tag/v0.19.1) * Removed old `third-party/pypi/tokenizers` versions * Fixed `third-party/pypi/tokenizers/BUCK` * Migrated `third-party/pypi/tokenizers/0.19.1/BUCK` to mirror other Python packages that bind to Rust crates e.g. `libcst`, `polars` etc. * Removed Windows support from `third-party/pypi/tokenizers` ## [Rust] * Upgrade `indexmap` to [`2.2.6`](https://github.com/indexmap-rs/indexmap/releases/tag/2.2.6) * Both latest `pydantic-core` and `c2pa` depend on `serde_json > 1.0.112` which brings in `indexmap = 2.2.1`. The latter has deprecated `.take` and `.remove` on both `IndexMap` and `IndexSet` leading to a bunch of errors (see bellow), all addressed: ```bash error: use of deprecated method `indexmap::set::IndexSet::<T, S>::take`: `take` disrupts the set order -- use `swap_take` or `shift_take` for explicit behavior. --> fbcode/hphp/hack/src/package/types.rs:76:16 | 76 | self.0.take(value) | ^^^^ | = note: `-D deprecated` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(deprecated)]` ``` Reviewed By: capickett Differential Revision: D56671179 fbshipit-source-id: 3ae69c069b7f005570c1a06d37194cf056282a18
v2024.05.02.00
update 'clap-4' crate to 4.5.4 Summary: version bump follow https://www.internalfb.com/intern/wiki/Rust/Third_Party_Libraries/Adding_or_Updating_Libraries/ Also updated `clap_complete` together allow-large-files Reviewed By: capickett Differential Revision: D56519704 fbshipit-source-id: deb160a682bd156c69e3f0509a54b1f6a5a85f27