Min Chen

@hiteshsharma I don't quite get your comments. In this proposed approach, ParSeq is maintaining the cache and ask for clients to provide cache key (as you indicated above unique identifier)...

No, I don't think ParSeq-rest-client has cache built in. @karthikbalasub @junchuanwang Do we have any plans to work on this in the near future?

This is a question raised before. The problem is that there are multiple versions of @nonull and @nullable annotations, as well as several static analysis tools to handle these annotations...

How do you compare this annotation with Java Optional?

I ran into the same issue when I set up my new laptop. @mockitoguy 's upgrade of "d3" solved my problem as well. Even without your previous workaround documented in...

Thanks for the suggestions, we can look into opentracing standard to say how much work is involved as well as extra benefits we can gain compared to existing one.

> Temporarily modified the tests to ignore then new option Do you mean that this is a temporary solution or you have followup fix?

can somebody provide link to the vulnerability issue this is trying to solve?