Eterna2

u need to fix the version of `mistune` to `0.8.*` because they just release `v2`.

Yeah. I mean u need to make sure u are using 0.8 rather than 2.0. U can look at #43 for what I meant. Currently there are no version lock...

Hmmm. Then u probably have a diff error from me. Cuz I was searching for the same question when my Travis for 3.6 failed while 3.7 passed. Then I updated...

@kachkaev @adrianmroz Sorry for the long wait. Was busy with another project. I have migrated to v3, but it is based on lit-element rather than polymer-element. I have not migrated...

I have found out the problem. This error only happens when there are async data request. The gist demonstrate a sync and an async version. https://gist.github.com/eterna2/2c18ff296bc093ced3af

I probably can make a PR soon. Cuz I needed the verbosity to debug to get it to work with cluster autoscaler. I got it to work on my cluster....

Should not be a problem to upgrade ur Argo. If u look at the manifest for this repo (instead of kubeflow/manifest) it is on Argo 2.7.5.

hmmm. I will try to look at it soon. Sorry was quite busy with work.

Hey @mkit This is a polymer based webcomponent. It is not a vaadin component. Aka u cannot use it inside a Java application - there are no Java bindings to...

Ok. I went and have a look at how pple use vaadin. U will need to do something like this. Using vaadin java methods to mimic what we would do...