Config cache deadlock while trying to load the configuration in the WebPorcessor

[theCapypara]

The class MageSuite\ExtendedException\Processor\WebProcessor tries to load a configuration value. However this results in a deadlock if the config cache is currently being cleared while a config lock is active. This is the case when magento config:set is being executed for example.
Note how the config:set command will take at least 42 seconds, because this is the default fallback lock timeout.

The reason for this is the logging event in Magento\Framework\Cache\InvalidateLogger, which initializes the WebProcessor, which then tries to load the locked configuration.

As a solution there needs to be a check in WebProcessor which only tries to load the configuration setting when the config lock is not active and otherwise falls back to a fallback value.

[theCapypara]

For reference, here is the entire stacktrace:

The lock occurs at LockedGuardedCacheLoader:113, the logging at InvalidateLogger:46, the loading of configuration is started at WebProcessor:13, and Magento tries to load the locked configuation at LockedGuardedCacheLoader:71

[pinkeen]

Hello, thanks for the report. I am not familiar with this particular problem, however, we're aware that this extension causes various problems outside of our internal use-cases. Fortunately it's not required at all for the proper functioning of MageSuite because its only function is to attach additional information to exception logs.

While we look into this, one workaround would be to prevent its installation by adding it to the replace section of composer.json.

Can you take a look at this @diwipl?