Python job run error messages are unreadable

[stinodego]

This has been going on for some time now; all errors look like this (note the weird `[0;34m` marks everywhere). How can we fix this?

We're not doing anything crazy, this is just the latest runtime with pretty much the simplest possible hello world program.

[Anonymous]

Could you give your scenario, your code and which dbr runtime you executed that code​?

[Md_Tamim_Hosen]

yeah

[Anonymous]

Could you try on the other web browsers? Or clear cookies, check library installed or not?

[stinodego]

Tried this, but no change. Anyone looking at these logs sees the same thing.

[UmaMahesh1]

Hi @Stijn de Gooijer​ 

Could you please tell the DBR runtime you executed that code on.

Assuming that you are doing basic stuff and not importing any other python packages. If not, please paste what all packages are imported.

Cheers.

[stinodego]

DBR is 11.3 LTS (non-ML). Not sure about packages, I'll try to work out a minimum example.

I was hoping one of you had seen this before and knows what's going on.

[Anonymous]

@Stijn de Gooijer​ did you try downgrade or upgrade new version python in your cluster? base on ur screenshoot look like bug python version 3.9

[VaibB]

Have you tried detaching and reattaching the notebook? Or Cluster restart?

Did you check you are not importing any specific library someone else with the right access might have installed some library with install to all clusters as checked.