添加链接
link管理
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接
相关文章推荐
一直单身的手链  ·  KK Piano | Bio | 簡介·  5 月前    · 
酷酷的盒饭  ·  Why Makefile include ...·  1 年前    · 
英俊的鞭炮  ·  logitech ...·  1 年前    · 

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account
  • **OS Platform and Distribution **: OSX 14.2 (Latest release)
  • MLflow installed from (source or binary) : source
  • MLflow version (run mlflow --version ) : 0.7.0
  • Python version : 3.6
  • **npm version (if running the dev UI):
  • Exact command to reproduce :
  • Describe the problem

    After successful run, mlflow ui displays Oops! Something went wrong. page.
    The following error is thrown:

    '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

    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?