David James Sherman

Can you show the error that you are seeing in the console log? I don't understand how you are performing this test. Could you be more specific in the steps?...

We would want this information associated with the target and made available using Zeroconf. As with #724, we need to define what node description data needs to be associated with...

I think that the proper place to put the name, is in the entity that will be handling Zeroconf responses. For the Thymio IIs this is the Switch (although it...

Note that there isn't a easy workaround in Calrissian itself. Because of the way that [`parse_arguments`](https://github.com/Duke-GCB/calrissian/blob/1252f4161415a98090e1e2b9be3f3f9178e9039e/calrissian/main.py#L58) handles defaults, the complete list of unparsed arguments isn't available to be passed as...

@fabricebrito would you prefer the Calrissian-specific unit test in a separate file, or folded into [tests/test_job.py](../blob/master/tests/test_job.py)?

@fabricebrito Yes, but making the PR has unfortunately been sitting in our backlog. I'll see whether I can nudge that along

@fabricebrito I'm trying to understand the underlying use case here, since it seems obvious that `CALRISSIAN_POD_NAME` should always be the pod name as defined in the pod metadata, and never...

It seems that we aren't looking for a general mechanism for inspecting volumes, but for finding the specific volumes that play specific roles in Calrissian's pods. If that is true,...