Tom Birdsong

cc @jcfr @thewtex

Note: recently observed by @PranjalSahu via `pip install itk` in Slicer.

Hi @thewtex , I am starting to take a look at this PR, it seems there is still an issue with connecting an ARM runner with the Github workflow. I...

> you can see that in the Cirun check run Oh neat, that's much easier, thank you @aktech 😃 It looks like this is indeed an AMI permissions error: >"An...

Thanks for updating @thewtex, the new image can be found and the AWS runner launches as expected. It looks like the image is running out of space. ~, will create...

@thewtex I think the failure is due to only supporting `_2_28` for `aarch64` builds, hence switching the default from `_2_28` to `2014` fails on `aarch64`. Given the roadmap we discussed...

I agree that the issue may lie in ITK Python. I am able to reproduce in VS Code. [https://github.com/InsightSoftwareConsortium/ITK/pull/3200](https://github.com/InsightSoftwareConsortium/ITK/pull/3200) was intended to generate ITK stub files to help with this...

> After multiple restarts, arm64 builds always time out. Depending on how strong the motive for Python packages is, we may need to look into self-hosting ARM builds with CIRun...

@thewtex @dzenanz are there particular guidelines / design constraints that need to be considered for ITK remote modules depending on other ITK remote modules? In this case of `ITK ->...

Thanks @dzenanz . It sounds like it would cause issues to have `ITKUltrasound` depend on `ITKVkFFTBackend` without making `ITKVkFFTBackend` available as an ITK remote module. But, `ITKVkFFTBackend` is still under...