It would be nice if when you attempt to change a shipment safety level to "yellow" with queued containers, it reverted to "green" after clicking OK. This is in complement to the warning message, since users might not see it as it fades out.

When creating a sample from a yellow protein in a container in a yellow shipment (such as NS_PGO in mx37045), the POST request for sample creation goes through, return 200, but doesn't seem to create any samples. In fact, an empty array is returned as the response body

Is this intended?

When creating a sample from a yellow protein in a container in a yellow shipment (such as NS_PGO in mx37045), the POST request for sample creation goes through, return 200, but doesn't seem to create any samples. In fact, an empty array is returned as the response body

Is this intended?

That's weird, it creates samples for me, and the response body is an array of the created samples.

It would be nice if when you attempt to change a shipment safety level to "yellow" with queued containers, it reverted to "green" after clicking OK. This is in complement to the warning message, since users might not see it as it fades out.

Yep, good point. Have added a new option to the Editable class to revert the value displayed if the server gives an error. So now you get the warning at the top, and the value reverts as well.

When creating a sample from a yellow protein in a container in a yellow shipment (such as NS_PGO in mx37045), the POST request for sample creation goes through, return 200, but doesn't seem to create any samples. In fact, an empty array is returned as the response body
Is this intended?

That's weird, it creates samples for me, and the response body is an array of the created samples.

Seems like this is part of a recurring issue I mentioned in other PR, it started working this morning, even though I cleared data yesterday a couple of times. That's definitely odd, and possibly a bit of undefined behaviour