Vaughn Dice

It appears the ability to `glide up ` is being tracked upstream/in glide by https://github.com/Masterminds/glide/issues/252

A first attempt at following the resources mentioned in the description didn't pan out very well, but it looks like there has been more activity on https://issues.jenkins-ci.org/browse/JENKINS-31155 which might be...

Both @michelleN and @endocrimes are right :) Yup, release automation ensures the correct versions for artifacts. However, if the chart is installed from source, currently, regardless of revision, it'll use...

Selection via RuntimeClass is probably sufficient for my general use case, which is having control over which subset of nodes in a cluster SpinApps can run on. I don't currently...

Via executor config could work. Use case would be to isolate all SpinApps for a given executor to a subset of nodes. I don't currently envision needing finer-grained toleration/scheduling control...

I'll let @jsturtevant and/or other maintainers chime in re: generic wasmtime or spin runtime configurability but I did want to mention that there happens to be a recent PR in...

@devigned That indeed makes sense. I was thrown off by `run_wasi ERROR` thinking it was somewhere further up but looking at it again, I agree, that must be the Spin...

Thanks @devigned! Meanwhile, curious as to what we can add in CI to catch this? Did it slip by the tests due to the tested Spin Apps still being wrapped...

(An update to mention that Spin apps now run on the shim built from main after the revert, as expected. Thanks again!)

Are all the follow-ups/tangential issues filed for this one? I'd be fine with closing now that we have https://github.com/spinkube/containerd-shim-spin/pull/90 in place as a safeguard for catching this in the future,...