'utf-8' codec can't decode byte 0x80 in position 3131: invalid start byte
Complete Stack trace:
File "/Users/agilebean/anaconda3/envs/mlflow/lib/python3.6/codecs.py", line 503, in read
newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 3131: invalid start byte
If it's of any help, I found the file causing the problem.
Deleting the file directory solved the problem but there is absolutely no hint why there was a codec problem as the logged information is exactly the same as previous runs.
291516e0411b478aa5d7b4adee327e41.zip
Hi @agilebean : I look at the run you uploaded. What sort of characters are in the artifact_uri
path?
[11/09 14:21][mani@:~/.../291516e0411b478aa5d7b4adee327e41] () $ > cat meta.yaml
artifact_uri: /Users/chaehan/Google Drive/01 Lectures/WS2018 IDAS Lectures/WS18-04
Advanced Robotics/02 Deep Learning/deep-learning-with-python/mlruns/2/291516e0411b478aa5d7b4adee327e41/artifacts
end_time: 1541683969366
Do you see this issue with other runs in experiment_id == 2
Hi
@mani,
no this is the only out of 34 runs that broke.
So I don't understand how to read the error indicating byte xxx and Unicode read error. Where in this uri or else should that happen and how can you find that character??
On 10 Nov 2018, 07:24 +0900, Mani Parkhe ***@***.***>, wrote:
Hi
@agilebean : I look at the run you uploaded. What sort of characters are in the artifact_uri path?
[11/09 14:21][mani@:~/.../291516e0411b478aa5d7b4adee327e41] () $ > cat meta.yaml
artifact_uri: /Users/chaehan/Google Drive/01 Lectures/WS2018 IDAS Lectures/WS18-04
Advanced Robotics/02 Deep Learning/deep-learning-with-python/mlruns/2/291516e0411b478aa5d7b4adee327e41/artifacts
end_time: 1541683969366
Do you see this issue with other runs in experiment_id == 2
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
The content from meta.yaml
file (excerpt pasted above) did not look right--there is a new line in artifact_uri
value. That should have affected all the other runs on the experiment, unless this file manually was edited, somehow.
If not, I am not sure how to reproduce this error. Do you possibly have a command sequence that can reproduce this error?