Tfx: AttributeError: Cannot set unknown property 'run_id' on artifact Artifact(type_name: Examples, uri: , id: 0).

[hanneshapke]

I am testing the latest 0.21rc and I noticed that the ExampleGen components fail with

AttributeError: Cannot set unknown property 'run_id' on artifact Artifact(type_name: Examples, uri: , id: 0).

I tried two ExampleGen components. The pipeline setup was working fine under 0.15.

Colab to reproduce: https://colab.research.google.com/drive/1Lod4ll5cW-VPMBmwmTlqBqLiCCNG_umE

Is anyone else experiencing this issue under 0.21rc?

[gowthamkpr]

@hanneshapke I am running into a bunch of errors with your code. Please take a look at it here. Thanks!

[hanneshapke]

@gowthamkpr Did you restart the Colab runtime engine after installing the required pip packages? If you don't restart the runtime engine, you'll run into the errors. If you restart it, you'll reproduce my initial error.

I think I read that packages installed from inside a Colab session aren't immediately available. Maybe the Python path doesn't update under the hood, not sure.

[gowthamkpr]

Yes. I did restart the colab runtime and installed all the dependencies. Here's my gist.

[hanneshapke]

Hey @gowthamkpr
Thank you for looking into this error. I made a little screencast of executing the Colab notebook. It shows that the notebook needs to run twice to be correctly executed.
Your gist showed this error: NameError: name 'InteractiveContext' is not defined
Since you imported InteractiveContext above, but the object can't be found in the next cell, that is an indication that the import failed.

[gowthamkpr]

Its showing that video is unavailable as it is private @hanneshapke. Can you Please take a look at it?

[hanneshapke]

Please try again: https://youtu.be/ml1oPSFmAIk

[gowthamkpr]

@hanneshapke I have run into the same error too but this time with chicago taxi example. Heres my gist. I think the error is arising from def run() in the class InteractiveContext(object): not setting the run_id(timestamp) to the artifact. Thanks for reporting this!

[hanneshapke]

@jiyongjung0 @rcrowe-google Just tried the 0.21.0 release and the bug seems to be fixed!
Thank you!