diff options
author | Bryan Newbold <bnewbold@robocracy.org> | 2020-11-20 18:39:53 -0800 |
---|---|---|
committer | Bryan Newbold <bnewbold@robocracy.org> | 2020-11-20 18:39:57 -0800 |
commit | 1fca5a9822944d0646d2dcba6cf54f27a0ffe5c0 (patch) | |
tree | 675954b8b34324fe22fc5a00f3fbb99a21a77a21 /notes/performance/kafka_pipeline.txt | |
parent | db4e3898de5859f257606058379ceed784b51f86 (diff) | |
download | fatcat-1fca5a9822944d0646d2dcba6cf54f27a0ffe5c0.tar.gz fatcat-1fca5a9822944d0646d2dcba6cf54f27a0ffe5c0.zip |
cargo: update sentry to fix memory initialization issue
Older sentry had an unsafe memory initialization error, which wasn't
caught by older compilers. Rust 1.48 catches the problem at runtime and
raises a panic. This meant that new builds (eg, on QA machine after
update) were panic-ing.
Newest versions of sentry have modern dependencies, which breaks our
crufty old 'iron' dependency tree. Work-around is to only partially
update (v0.12 to v0.15).
This is a fairly frustrating situation. I'm hopeful that when we update
to a different web framework and openapi generator 5.0 (not yet
released), many of these dependency issues will be resolved, but i'm not
certain. I did notice that if we entirely remove Sentry, which has not
really been used much (only a small handful of issues reported over
several years), we might be able to resolve openssl dependency issues.
Diffstat (limited to 'notes/performance/kafka_pipeline.txt')
0 files changed, 0 insertions, 0 deletions