[GitHub] [zeppelin] alexott commented on issue #3428: [ZEPPELIN-4305] LocalStorageConfig.atomicWriteToFile throws exception

alexott commented on issue #3428: [ZEPPELIN-4305] LocalStorageConfig.atomicWriteToFile throws exception URL: https://github.com/apache/zeppelin/pull/3428#issuecomment-528225806 @zjffdu I've opened #3439 that should fix this problem - I believe that it's caused by fact that destination dire

[GitHub] [zeppelin] alexott opened a new pull request #3439: [HOTFIX] [ZEPPELIN-4305] make sure that destination directory exists

alexott opened a new pull request #3439: [HOTFIX] [ZEPPELIN-4305] make sure that destination directory exists URL: https://github.com/apache/zeppelin/pull/3439 ### What is this PR for? This is a fix for issue reported in #3428 - this may happen when destination directory doesn't exi

Re: [VOTE] Creating feature branch for zeppelin new ui initiative

+1 Excellent, this was long overdue. On Thu, 5 Sep 2019 at 08:43, Jeff Zhang wrote: > Sure, we should definitely run CI before merging such large feature. > > Jongyoul Lee 于2019年9月5日周四 上午11:01写道： > > > Hello, > > > > Additionally, if we make a PR and check the CI properly before we merge > > th

[GitHub] [zeppelin] ShamsUlAzeem commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export

ShamsUlAzeem commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export URL: https://github.com/apache/zeppelin/pull/2649#issuecomment-528188568 @zjffdu Cool! But I haven't resolved the issues yet. I'll let you know when they're resolved. I just did a random commit to check the CI status

[GitHub] [zeppelin] zjffdu commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export

zjffdu commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export URL: https://github.com/apache/zeppelin/pull/2649#issuecomment-528187541 Thanks @ShamsUlAzeem Seems the CI is still running, let's wait for the CI result. T

[GitHub] [zeppelin] ShamsUlAzeem commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export

ShamsUlAzeem commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export URL: https://github.com/apache/zeppelin/pull/2649#issuecomment-528185967 @zjffdu yup I configured it a long time ago and it's working now as well. I'll do a couple of changes and run some tests before notifying you f

[GitHub] [zeppelin] zjffdu commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export

zjffdu commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export URL: https://github.com/apache/zeppelin/pull/2649#issuecomment-528184942 @ShamsUlAzeem Have you configured your travis to enable the CI ? https://zeppelin.apache.org/contribution/contributions.html#continuous-integration

[GitHub] [zeppelin] zjffdu commented on issue #3428: [ZEPPELIN-4305] LocalStorageConfig.atomicWriteToFile throws exception

zjffdu commented on issue #3428: [ZEPPELIN-4305] LocalStorageConfig.atomicWriteToFile throws exception URL: https://github.com/apache/zeppelin/pull/3428#issuecomment-528182716 @alexott CI of master branch is failed due to this PR, could you help take a look at it ? Thanks https://api.tr

Re: [VOTE] Creating feature branch for zeppelin new ui initiative

Sure, we should definitely run CI before merging such large feature. Jongyoul Lee 于2019年9月5日周四 上午11:01写道： > Hello, > > Additionally, if we make a PR and check the CI properly before we merge > that branch to master, I agree to make a new branch, and I'll help to > change backend sides as well. >

Re: [VOTE] Creating feature branch for zeppelin new ui initiative

Hello, Additionally, if we make a PR and check the CI properly before we merge that branch to master, I agree to make a new branch, and I'll help to change backend sides as well. JL On Thu, Sep 5, 2019 at 11:33 AM Jeff Zhang wrote: > Hi all, > > There's one thread [1] discussing about the new

[VOTE] Creating feature branch for zeppelin new ui initiative

Hi all, There's one thread [1] discussing about the new zeppelin ui initiative. It looks like the community have reach consensus on this. Considering this is a large effort and most of work is on frontend, I would suggest to create a new feature branch for this initiative. So that the development

[GitHub] [zeppelin] santosh1994 opened a new pull request #3438: [ZEPPELIN-4320] fix packages to bundle list

santosh1994 opened a new pull request #3438: [ZEPPELIN-4320] fix packages to bundle list URL: https://github.com/apache/zeppelin/pull/3438 ### What is this PR for? Enabled Helium packages are not getting installed/bundled on zeppelin startup. Instead getting bundled later on paragraph w

[GitHub] [zeppelin] ShamsUlAzeem commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export

ShamsUlAzeem commented on issue #2649: [ZEPPELIN-3033] IPYNB import/export URL: https://github.com/apache/zeppelin/pull/2649#issuecomment-527828390 @zjffdu ah alright. on it This is an automated message from the Apache Git Ser

[GitHub] [zeppelin] santosh1994 opened a new pull request #3437: [ZEPPELIN-4319] Fix spell interpreter parse text logic

santosh1994 opened a new pull request #3437: [ZEPPELIN-4319] Fix spell interpreter parse text logic URL: https://github.com/apache/zeppelin/pull/3437 ### What is this PR for? Spell interpreter returns incorrect results when paragraph having magic in between text, with current approach t

[jira] [Created] (ZEPPELIN-4320) Enabled Helium packages are not getting bundled on zeppelin start

santosh k created ZEPPELIN-4320: --- Summary: Enabled Helium packages are not getting bundled on zeppelin start Key: ZEPPELIN-4320 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4320 Project: Zeppelin

[jira] [Created] (ZEPPELIN-4319) Spell Interpreter returns incorrect results when magic is present in paragraph text

santosh k created ZEPPELIN-4319: --- Summary: Spell Interpreter returns incorrect results when magic is present in paragraph text Key: ZEPPELIN-4319 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4319