Arnaud Jeansen

Hello @manusa Yes that is debatable, this is indeed only an INFO message. ```bash helm create foo ``` generates the following default chart ```yaml apiVersion: v2 name: foo description: A...

OK this ticket is close enough, hopefully I'm not hijacking it. Here is how I'm currently doing [helm tests](https://helm.sh/docs/helm/helm_test/) in a maven project. I added a kubernetes fragment in `src/main/jkube/test-prometheus.yml`...

@smbea Unfortunately, I didn't even manage to run the existing tests (step 1 of @barmac directions). ```shell npm test ``` ```log > [email protected] test > karma start karma.config.js 06 03...

@barmac that's complicated :) ```shell node -v && npm -v ``` returns ``` v16.18.1 8.19.2 ``` but `npm ci` fails on my Ubuntu 22.04 with ``` ... npm WARN deprecated...

@bdshadow I took care of 3 comments, and replied on the big comment regarding redis data migration.

> @ajeans one more comment for discussion here. Jan has already written these concerns about multiple jobs per projects: > > > When implementing this I wanted to prevent some...

> @ajeans thank you for the clarification. As far as i remember, the main problem you were trying to solve is that the batch translation of a huge number of...

> @ajeans thank you very much for a detailed explanation. > Hi @bdshadow > I understand your motivation behind these changes. However, it will affect lots of other batch processes,...

@JanCizmar Thank you for the detailed response. I'd like to provide more context on why increasing global TOLGEE_BATCH_CONCURRENCY alone doesn't solve the scalability issue for our production workload. I also...

> I've made a draft of the refactored batch job processing. Although i like it more :), the processing perfomance was just a little bit better (meanwhile i think it's...