Phil Clay

Results 60 comments of Phil Clay

I wouldn't restrict anything other than null. Just keep logstash-logback-encoder lightweight and unopinionated and allow anything that jackson allows.

Hi @Mumeii, The current behavior is as designed. Any change would be an enhancement. There is not really a "great" way to consistently convert a logstash-logback-encoder marker to a string...

For some background... The primary purpose of logstash-logback-encoder is to produce JSON payloads (or other data types producible by jackson). The primary purpose for Markers and StructuredArguments is to add...

> The SyslogAppender however is still using a Layout but does not allow to set it by configuration. `AbstractLogstashUdpSocketAppender` extends `SyslogAppenderBase`, and allows the layout to be configured. It's typically...

Just want to +1 here to say that I encountered the same problem. I have implemented a solution that builds upon the approach from @a701440. Specifically, it supports a callback...

@OlegDokuka / @simonbasle The [blog post](https://spring.io/blog/2023/10/31/what-new-is-coming-in-reactor-core-3-6-0#virtual-threads-support) mentions (*emphasis mine*): > we introduce support for the `VirtualThread` class in the new ThreadPerTaskBoundedElasticScheduler, ***which is going to be automatically used as implementation...

I want to offer a possible example of how stacktraces could be customized. The [logstash-logback-encoder](https://github.com/logfellow/logstash-logback-encoder) library (of which I am a maintainer) contains a [really powerful way of customizing how...

That is not exactly correct. The `jackson-bom` is used in logstash-logback-encoder's `dependencyManagement` section. Not its `dependencies` section. Therefore logstash-logback-encoder does not depend on, or require, `jackson-module-jaxb-annotations`. This can be confirmed...

Also somewhat related, I filed https://github.com/redis/lettuce/issues/2837 to request an enhancement to verification modes to better secure connecting to redis in cluster mode from cloud providers.

I believe [logstash-logback-encoder](https://github.com/logfellow/logstash-logback-encoder/pull/960) is running into this same problem. Here's a small project ([mockito-parameterized-type-injection.zip](https://github.com/mockito/mockito/files/11645910/mockito-parameterized-type-injection.zip)) with a unit tests that fails to inject a mock with mockito 5.3.1. The test works...