Ilya Selivanau

Working example with [A+A mode](https://github.com/bloc97/Anime4K/blob/master/md/GLSL_Instructions_Advanced.md) for [lower-end GPU](https://github.com/bloc97/Anime4K/blob/master/md/GLSL_Instructions_Linux.md): ``` mpv input.mp4 \ --glsl-shaders="~~/shaders/Anime4K_Clamp_Highlights.glsl:~~/shaders/Anime4K_Restore_CNN_M.glsl:~~/shaders/Anime4K_Upscale_CNN_x2_M.glsl:~~/shaders/Anime4K_Restore_CNN_S.glsl:~~/shaders/Anime4K_AutoDownscalePre_x2.glsl:~~/shaders/Anime4K_AutoDownscalePre_x4.glsl:~~/shaders/Anime4K_Upscale_CNN_x2_S.glsl" \ --vf=gpu -vf scale=2560:1440 --o=output.mp4 ```

Hello, in my case I have set the correct external-url and public-host for my docker container, but when I call fake-gcs from the local machine, I also get a 404...

> Is that something you still want to contribute? @nathanielc I still want to contribute elastic source. And if you give me a couple of tips, I will continue to...

@johnrengelman its example of problem https://github.com/OrangeFlag/issue_427_shadow_jar_example Simple handler for aws lambda with log4j2 To use log4j2 we should add custom appender from aws(`com.amazonaws:aws-lambda-java-log4j2`). But as say @MacTrophy in `/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat` there...

Test different version On shadow 4.0.0 with TheBoegl plugin ver 2.2.0 - all is normal But when disable plugin - bug manifests itself

Something strange, now recheck with ` transform(com.github.jengelman.gradle.plugins.shadow.transformers.Log4j2PluginsCacheFileTransformer()) ` And it seems everything works. Maybe I just forgot to add a call to this transformer🤦

v1.6.0 - same behaviour

> While we can't utilize the metric API in trace components at this time, that should be the way forward here IMO. Maybe something has changed in 2 years?

> it needs to always return gRPC status codes even in error situations. It returns the grpc status, but the retry code ignores it

Maybe it's possible to simplify and not check http code in grpc retrier?