Masaki Muranaka

> So, we need a solution that will provide all required libraries to a user's container. Well. And it can be solved by ... * Adding some shared libs to...

I read https://github.com/che-incubator/che-code/pull/332 also. I suppose I can add some contributions to che-code, as some of my customers will want to use Ubuntu based images. BTW... I guess there are...

I checked to build Node with CosmoCC. I couldn't build the master branch of Node. Because the version of gcc/g++ in CosmoCC is too fresh to build Node. I suppose...

Maybe `.idea/externalDepencies.xml` is. An example: https://github.com/JetBrains/intellij-community/blob/master/.idea/externalDependencies.xml

ping? I created a PoC. Is it acceptable? https://github.com/monami-ya/che-operator/commit/26818123f669054964a2a28e41fa368e0e4dcabc

@tolusha Thanks for your check. I suppose that some additional docs are required. I'll set them up within a couple of weeks.

I suppose this can be closed as eclipse-che/che-operator#1864 was merged. @ibuziuk

`registry.access.redhat.com/ubi9/openjdk-17:1.17-1.1705573248` is used by "Maven Java" from devfile.io ``` $ kubectl run --image registry.access.redhat.com/ubi9/openjdk-17:1.17-1.1705573248 delme -- tail -f /dev/null pod/delme created $ kubectl exec -it delme -- bash [default@delme ~]$...

Workaround for now: setting sessionStore explicitly. Like ```typescript export class ApiModule { private sessionStore = new MemoryStore(); configure(consumer: MiddlewareConsumer) { ExpressSessionMiddleware.configure({ store: this.sessionStore, ```

In bazelbuild/bazel-buildfarm#1718, > Technically, I can work around this by using reclient's racing or local fallback mode, which is likely to be the production configuration. I had a similar issue....