Sergey Beryozkin
Sergey Beryozkin
@michalvavrik Thanks, it looks technically totally fine, thanks for working out how to handle it. But it feels like we are doing a workaround, which in the RestEasy Reactive security...
Hey @michalvavrik the last thing that should be of concern is if some code in PR can make me less excited :-), you keep creating good quality PRs I may...
@michalvavrik Great, sorry for a delay, can you please resolve the conflict ?
@mkouba Hi Martin, can you please have a look at the Arc related code in this PR when you are get a chance ?
@geoand Have a look please when you get a chance :-), I agree it is a much more complex solution compared to the original approach of passing the flags, but...
@knutwannheden Can you please check the last few comments from @michalvavrik and @mkouba and clarify if needed ? I think you typed it all in #26536 but it might help...
Hi @sheilamjones It looks nice, I've added a few more minor suggestions - lets try to resolve/discuss them and then I'll commit this PR and then look at integrating the...
Hi @sheilamjones It LGTM now, however the log history seems to have gone wrong, I've checkout your branch, and I see ``` commit c80628f1ed (HEAD -> QDOCS-31-OIDC-INTRO, origin/QDOCS-31-OIDC-INTRO) Merge: 61b261f6a2...
@sheilamjones Hi Sheila, apologies for a delay, I've missed your update. I've squashed the commits, and had to resolve the conflict since Michal's @michalvavrik PR affecting the same section was...
@sheilamjones Let me merge it and as I said we can always add a few more updates easily. Thanks for this PR, look forward to seeing the PR to the...