When sharing+cloning histories between users, the "stderr" information is not
cloned (in the database).
Steps to reproduce:
1. as one user, run a tool that will generate error (e.g. "Compute" with an
invalid python expression)
The dataset is red, it's STDERR information contains the python error (see first
attached image, "user_1").
2. Share the history with another user.
3. switch to the other user, clone the shared history.
4. The failed (red) dataset will not have the STDERR information (see second attached
Note that the "peek" information is properly cloned, so the beginning of the
error messag appears in the peek window, but not the entire error message.
Not a critical bug, but slightly annoying when users share history with me to show me
Show replies by date