pydantic 2.8.2 (new formula)

[chenrui333]

• [x] Have you followed the guidelines for contributing?
• [x] Have you ensured that your commits follow the commit style guide?
• [x] Have you checked that there aren't other open pull requests for the same formula update/change?
• [x] Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• [x] Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• [x] Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

package inclusions, https://repology.org/project/pydantic/versions would help remove rust deps for lots of python formulae

[daeho-ro]

Is it possible to upgrade rust from 1.79.0_1 to 1.80.1 on MacOS 12 (x86_64)?

I tried to reproduce the maturin build error on AWS with intel based MacOS 12.7, rust version 1.79.0_1, and got an error per 2-3 attempts.

cargo(12799,0x10eea0600) malloc: *** error for object 0x600003663e20: pointer being freed was not allocated
cargo(12799,0x10eea0600) malloc: *** set a breakpoint in malloc_error_break to debug
zsh: abort      cargo metadata --manifest-path Cargo.toml --format-version 1 --locked

But this is not the same error on the CI process where it shows the error code -6.

Anyway, maybe this can be gone with the most recent version of rust, because there was no error on my AWS EC2 with rust 1.80.1. So, I am just curious about are there any chance to upgrade the brew package versions on the CI process.

[p-linnane]

@daeho-ro We just need to rebase to have CI pick up the latest Rust update.

[daeho-ro]

Nice, the error is gone!

[branchv]

I think we need https://github.com/Homebrew/homebrew-core/pull/178715/files#r1694038551 to be addressed

[github-actions[bot]]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.