aptos aptos-cli-v2.3.1

[aptos-bot]

Created by https://github.com/mislav/bump-homebrew-formula-action

From CLI release run https://github.com/aptos-labs/aptos-core/actions/runs/6789767888

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

[banool]

I'm not sure why this build is failing, the commit it refers to exists: aptos-labs/aptos-core@14c8813.

[banool]

SO implies this is due to a faulty registry, though idk if brew does any caching in their build pipeline: https://stackoverflow.com/questions/41093530/cargo-build-results-in-no-match-for-id.

I wonder if the depth of repo cloning is the issue. When you build the CLI in aptos-core, it depends on the processor crate from aptos-indexer-processors, which depends on the aptos-protos crate in aptos-core. We never have issues with this in our own build pipeline but maybe brew has a different setup.

[banool]

The jobs that failed before and after the label are different, could this be a problem with the brew build environment? Everything I see implies that this error is due to some kind of bad cache.

[banool]

@chenrui333 could you please re run the failing job? It seems like it must be transient because the same job passes on MacOS 12 and MacOS 14 on x86.

[banool]

cc @p-linnane who helped me with the aptos formula last time.

[chenrui333]

@chenrui333 could you please re run the failing job? It seems like it must be transient because the same job passes on MacOS 12 and MacOS 14 on x86.

yeah, i saw it, it would be yank the release and create a new one next time.

rerunning the job now

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.