Martin Grigorov

Is there any workaround for this issue ? Almost half of the job runs fail because of this: https://github.com/martin-g/zeppelin/runs/4618065075?check_suite_focus=true I tried `touch`ing these files before running setup-miniconda but it does...

A workaround for my case was to use different OS user for each self-hosted Github runner.

> There is still a chance another GHA runner to move the file between the `existsSync` and `io.mv` calls. I don't see a solution for this problem except stop using...

I am not sure whether these are the problems but the following two lines look suspicious to me: ``` # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit

> * Which is the OS on the host? > can't find `cat /etc/*release*`

@umarcor The discussion first started at https://github.com/multiarch/qemu-user-static/issues/161. There I recommended dbhi/qus because @HelloGril wanted to emulate x86_64 on aarch64 host.

I've approved the workflow run! The new CI related code could be simplified. I will do it soon! I'll let the Java developers to comment on the Java changes!

We should not merge this PR for `branch-1.11` because it will definitely cause problems with the release! I guess we will have to use JDK 17 for the release process...

@ashley-taylor The PR should be reviewed and merged by a committer who knows better the Java SDK. I review most of the PRs for all SDKs but my main expertise...

> Do you have a JIRA account so we can assign this JIRA to you and ensure that it's properly taken care of? I tried to add Ashley to the...