Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1262
Thanks @jongyoul !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@kavinkumarks So sorry for the late reply. I'll merge it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1262
Could someone take care of merging this? NOTE that the review was over.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@jongyoul could you please take merging this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1262
The latest CI build is green
https://travis-ci.org/apache/zeppelin/builds/150722171 and also rebased the
branch with the latest master. @jongyoul could you please merge and close this
Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1262
Reopened to trigger travis build.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1262
You can do it by closing and re-opening this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@jongyoul I dont see the option to restart the build in travis since I
don't have the write access to repo.And I didn't find any way other than doing
some hacks.Could you please let me know
Github user doanduyhai commented on the issue:
https://github.com/apache/zeppelin/pull/1262
By the way, those issues are all related to the fact that we are running
our software factory on a shared/mutualized infrastructure (Travis). I have the
same issue of random failures due to
Github user doanduyhai commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@jongyoul The only way to avoid this failure is to block the unit tests
until the embedded Cassandra server is up, which can take time and sometimes
end in a dead-lock situation.
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@doanduyhai Thanks for the quick response. I see what happened. Is there
any way to avoid this failure by conservative code?
---
If your project is set up for it, you can reply to this email
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@doanduyhai I've found an error that I've never seen it while testing
CassandraInterpreter. Can you check that file :
https://s3.amazonaws.com/archive.travis-ci.org/jobs/150544950/log.txt ?
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@kavinkumarks Your changes LGTM, but could you please trigger the CI again?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1262
Have updated the title, please let me know if I am missing anything else.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1262
Could you please revise the title first?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@jongyoul Added the unit test and updated docs.Also reverted the UI
code.Could you please check them?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1262
In the backend part, it looks good. But I suggest you add unit test for
that api and docs for it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@corneadoug thanks for the update.I will remove the changes done for
it.Could someone review the other change that I have done as part of this?
---
If your project is set up for it, you can
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1262
@kavinkumarks Thanks for the contribution, the Paragraph ID is actually
already shown in the UI
19 matches
Mail list logo
