Failsafe in case config for transaction_processing_store is incorrect

[kneeyo1]

If the transactions configuration is wrong for any reason, fall back to the default processing memorystore.

[codecov]

Codecov Report

Attention: Patch coverage is 16.66667% with 5 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/sentry/eventstore/processing/__init__.py	16.66%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #80463      +/-   ##
==========================================
- Coverage   78.36%   78.36%   -0.01%     
==========================================
  Files        7207     7207              
  Lines      318765   318770       +5     
  Branches    43918    43918              
==========================================
+ Hits       249787   249790       +3     
- Misses      62611    62615       +4     
+ Partials     6367     6365       -2     

[lynnagara]

Can you provide more context about the rationale for this? Is this intended to be temporary? Why does it only cover the transaction store and not invalid config of the event store

If this is intended as a validation mechanism, I think it would make more sense to build a proper validation that covers both events and transactions processing stores instead of this fallback which is quite unexpected.

[kneeyo1]

Can you provide more context about the rationale for this? Is this intended to be temporary? Why does it only cover the transaction store and not invalid config of the event store

If this is intended as a validation mechanism, I think it would make more sense to build a proper validation that covers both events and transactions processing stores instead of this fallback which is quite unexpected.

Yes, this is intended to be temporary, I think the proper fix would be fixing how the eventstores are properly initalized, but out of scope for this project :(