You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like sensor data isn't currently plumbed through any of our IP services (unless I missed one). This means we can't easily get at sensor data in release images if we don't have physical access. In #1591 Matt was able to use readvar to get around this, but that's not ideal for a bunch of reasons --- it's hard to operate, it exposes internal state (which in this case had confusing results), and it has deep dependencies on the build archive.
In the short term, we could expose sensor data through gimlet-inspector for debugging.
In the not-short-term, we're going to need a way to evacuate sensor data up through the control plane.
Filing this issue to keep track.
The text was updated successfully, but these errors were encountered:
It looks like sensor data isn't currently plumbed through any of our IP services (unless I missed one). This means we can't easily get at sensor data in release images if we don't have physical access. In #1591 Matt was able to use
readvar
to get around this, but that's not ideal for a bunch of reasons --- it's hard to operate, it exposes internal state (which in this case had confusing results), and it has deep dependencies on the build archive.In the short term, we could expose sensor data through
gimlet-inspector
for debugging.In the not-short-term, we're going to need a way to evacuate sensor data up through the control plane.
Filing this issue to keep track.
The text was updated successfully, but these errors were encountered: