polls, voting, staking: Enhance voting consensus rules to allow for changeable magnitude weight factor and enhance CBR #3159
Annotations
1 error and 11 warnings
|
test
Process completed with exit code 1.
|
|
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
|
|
install-packages
macOS's Gatekeeper has been disabled for this Cask
|
|
install-packages
autoconf 2.72 is already installed and up-to-date.
To reinstall 2.72, run:
brew reinstall autoconf
|
|
install-packages
automake 1.17 is already installed and up-to-date.
To reinstall 1.17, run:
brew reinstall automake
|
|
install-packages
boost 1.86.0 is already installed and up-to-date.
To reinstall 1.86.0, run:
brew reinstall boost
|
|
install-packages
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
install-packages
libzip 1.11.1 is already installed and up-to-date.
To reinstall 1.11.1, run:
brew reinstall libzip
|
|
install-packages
openssl@1.1 1.1.1w is already installed and up-to-date.
To reinstall 1.1.1w, run:
brew reinstall openssl@1.1
|
|
install-packages
pkg-config 0.29.2_3 is already installed and up-to-date.
To reinstall 0.29.2_3, run:
brew reinstall pkg-config
|
|
install-packages
python@3.12 3.12.6 is already installed and up-to-date.
To reinstall 3.12.6, run:
brew reinstall python@3.12
|
|
install-packages
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|
Loading