ElastAlert 2 builds are broken due to Stomp dependency
See original GitHub issueThis issue is being raised to make others aware that the make test-docker
is failing as of April 27, 2022. This is due to a PyOpenSSL dependency conflict caused by the Stomp package. That package (version 8.0.0) requires an older PyOpenSSL package, which is no longer compatible with the underlying cryptography library.
An issue has been raised on the Stomp GitHub project: https://github.com/jasonrbriggs/stomp.py/issues/378
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:8 (3 by maintainers)
Top Results From Across the Web
️ ElastAlert is no longer maintained. We strongly ... - GitHub
⚠️ ElastAlert is no longer maintained. We strongly recommend migrating to ElastAlert2. #3241. Closed.
Read more >ElastAlert 2 Documentation
We designed ElastAlert 2 to be reliable, highly modular, and easy to set up and configure. It works by combining Elasticsearch with two...
Read more >Package 'stomp.py' requires a different Python: 2.7.12 not in ...
The error is rather clear. The package you are trying to install only supports Python 3.6+. Your options are either to install newer...
Read more >ARCHIVED: Implementing Microservices on AWS - Awsstatic
Due to the rather involved nature of various topics discussed in this ... store) and how to build it on AWS using container...
Read more >Compare Packages Between Distributions - DistroWatch.com
Comparing package versions between two distributions ... to compare the versions of different packages between two distributions. ... boost-build 1.79.0
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t have any issue with dropping it. Anecdotally, I don’t know of anyone with an alerting pipeline that uses it. Presumably – if there is anyone – they will complain and we can reevaluate then.
My workaround is to pin cryptography==36.0.2.