Skip to content
Test

Fix NPE and lost trace context of reactive Lettuce commands when tracing is enabled #2479

Sign in to view logs

Fix NPE and lost trace context of reactive Lettuce commands when tracing is enabled

Fix NPE and lost trace context of reactive Lettuce commands when tracing is enabled #2479

Run time

Learn about OS pricing on GitHub Actions
Job Run time
Build
6m 32s
influxdb-scenario
2m 51s
httpclient-4.3.x-scenario
2m 34s
httpclient-5.x-scenario
2m 52s
h2-scenario
1m 42s
sentinel-scenario
2m 53s
jedis-3.1.x-plus-scenario
2m 50s
lettuce-6.5.x-scenario
2m 52s
jetty-scenario
2m 59s
hystrix-scenario
2m 52s
httpasyncclient-scenario
2m 30s
mongodb-3.x-scenario
2m 47s
mongodb-4.x-scenario
2m 54s
jdk-http-scenario
1m 51s
kafka-scenario
2m 48s
jedis-2.x-scenario
2m 50s
jdk-threading-scenario
1m 41s
lettuce-scenario
2m 51s
mongodb-5.x-scenario
2m 17s
jedis-3.3.x-plus-scenario
2m 51s
jedis-2.x-3.x-cluster-scenario
3m 1s
hutool-http-5.x-scenario
2m 53s
kotlin-coroutine-scenario
2m 51s
postgresql-above9.4.1207-scenario
2m 39s
httpclient-3.x-scenario
2m 16s
mybatis-3.x-scenario
2m 50s
lettuce-webflux-5x-scenario
2m 52s
resteasy-4.x-scenario
2m 59s
netty-socketio-scenario
1m 17s
mssql-jdbc-scenario
2m 53s
netty-http-4.1.x-scenario
2m 52s
mssql-jtds-scenario
2m 53s
jedis-4.x-scenario
2m 51s
1h 31m 24s