Thanks for reporting this. I've attempted to reproduce the workflow related
error you're seeing, but have been unable to do so. Do you know what revision
your galaxy instance is running?
You should not have to avoid special characters in dataset names. If you do
run into this issue again, please let me know.
On Jun 9, 2011, at 5:31 AM, Sarah Diehl wrote:
> Hello everybody,
> currently I have some trouble with the following kind of error:
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 155:
> ordinal not in range(128)
> We have encountered it twice now. The first time it was related to a shared
> library, which could not be opened anymore because of this error. So we
> deleted the library and set it up again.
> The second time it was related to a workflow. Clicking on "Run" caused this
> error to appear, while editing still worked. This time I saved the error
> message and you can find it attached to this mail. The cause of the error was
> a < sign in a renaming step inside the workflow (the < was part of the new
> name). After removing the < everything worked again.
> However, when using the < in a history item, it works without a problem.
> Unfortunately I cannot reproduce the error currently on my machine. The
> computer that caused it was a Mac.
> Should we just try to avoid any special characters or is this actually a bug
> which could be fixed?
> Best regards,
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at: