When I look at a queued/running container request, I get "00" in an off-brand font where the "Container Cost" label & field normally go. I suspect this is because the cost fields are zero, and "true && 0 && 'foo'" evaluates to 0 in js. Maybe we need "container.cost != 0" here?
{container && container.cost && <Grid item xs={12} md={mdSize}>
Sometimes the cost fields appear when the process page first renders, then disappear. Sometimes they are missing at first and then appear after a few seconds. Is there a cache update race? Do we need to add the cost fields to a select param somewhere?
The capitalization of the existing field labels in the process panel seems haphazard ("Docker Image locator", "Output Collection", "Container run time") so it's impossible to make this one's capitalization match its neighbors. Personally I would choose "Docker image locator", "Output collection", "Container run time", "Container cost", etc., but anything consistent would be fine.
Come to think of it, the word "container" seems redundant -- can we just call it "Cost"?
I think it would be useful to also show the per-subprocess costs in the subprocess table down below, and show the cumulative costs in "all processes" and project views, but the way this issue is worded I guess those things are out of scope.
Updated by 
Updated by 
Updated by