Do not run CatchUpSubscriptionEngine for _wdt and _profiler requests

[fritz-gerneth]

Would it make sense to not run the in these kind of requests for the Profiler UI and requests related to the toolbar?

• When a subscription fails the error blocks requests (and therefore) access to the profiler or requests related to the wdt
• When the subscription catches up, makes it hard to trace the request where this actually happend, as this could happen in a request related to the wdt/profiler (e.g. when we want to look at the profiled data for a caught up run)

I would suggest to not run the catchup engine when detecting either kind of request. Not sure though what the best way would be do so (except matching url prefix, but that seems wonky)

[DavidBadura]

It makes perfect sense that the Subscription Engine is not running in Profiler/Toolbar requests. However, CatchUpSubscriptionEngine is not directly related to this. Our RequestListeners are most likely the trigger:

https://github.com/patchlevel/event-sourcing-bundle/tree/3.15.x/src/RequestListener

Have you enabled auto_setup or rebuild_after_file_change in your environment?

Instead of checking the URL, you can also check the route name. That should be more stable.