amarc-sudo/sentry-enhanced-tracing
^6.4|^7.0|^8.0; validated against Symfony 8.1, lexik 3.2, sentry-symfony 5.10 and API Platform 4.x, down to Symfony 6.4 / sentry-symfony 5.0 (--prefer-lowest).composer test script, phpunit.xml.dist, and a test step in both workflows (tests existed but were never run).symfony/config, symfony/event-dispatcher and symfony/yaml runtime dependencies (previously relied on transitively).readonly class already used by the listeners (the >=8.1 constraint could not actually run the code).services.yaml, removing the redundant #[AsEventListener] attributes (see fixes below).messaging.destination.name convention and the publish-side logic.composer psalm runs green (it previously could not pass and never ran clean).#[AsEventListener] attributes and services.yaml tags. On Symfony 7+ this registered every listener twice (duplicated spans); on Symfony 6.4 the non-repeatable AsEventListener attribute caused a fatal error.Symfony\Component\Messenger\Stamp\UuidStamp and Symfony\Component\Messenger\Event\DispatchEvent, which do not exist in Symfony Messenger. The phantom DispatchEvent subscription never fired, so user propagation to workers was silently broken; trace/user stamping now runs on the real SendMessageToTransportsEvent.getTransportNames() (always empty); it now uses SendMessageToTransportsEvent::getSenders().Sentry\continueTrace(), a redundant non-null check on getThrowable(), and an int/float operand in the receive-latency calculation.phpstan.neon referenced non-existent tests/bootstrap.php and tests/console-loader.php, which crashed PHPStan.queue.publish span on dispatch and queue.process transaction on workers.sentry_enhanced_tracing.messenger.propagate_user.examples/messenger-queue-monitoring.php.symfony/messenger as a runtime dependency.__invoke() controllerslexik_jwt_authentication.on_jwt_authenticatedHow can I help you explore Laravel packages today?