[GitHub] zeppelin issue #1879: [HOTFIX : ZEPPELIN-1932] paragraph blur error
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1879 LGTM --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: branch-0.7 cut
Cool, thanks! On Thu, Jan 12, 2017 at 1:13 AM, Mina Leewrote: > Hi Ashwin, > > we still have some issues that need to be handled before release, > hopefully most of them are in review process which will take 2-3 more days. > I am going to start release vote next week, so I expect we will be able to > deliver Apache Zeppelin 0.7.0 end of next week or a week later. > > On Thu, Jan 12, 2017 at 4:25 AM Ashwin Shankar > wrote: > > Hey Mina, > When can we expect the 0.7 release to be officially out? > > Thanks, > Ashwin > > On Tue, Jan 10, 2017 at 11:22 PM, Mina Lee > wrote: > > > I would like to inform you that branch-0.7 has cut. > > You can check it through apache git repository URL [1] but it seems like > it > > takes some time for Github mirror. > > > > PMCs/Commiters, please note that you need to merge bug fix both to master > > and branch-0.7 > > if it needs to be included in 0.7.x release. > > > > Thanks, > > Mina > > > > [1] https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=summary > > > > On Wed, Jan 11, 2017 at 3:09 PM Hyung Sung Shim > wrote: > > > > > Thanks Mina! > > > > > > 2017-01-10 18:23 GMT-08:00 Mina Lee : > > > > > > > Moon, thank you for reminding. > > > > I think it would be beneficial to community to provide public docker > > > image. > > > > I will definitely take it into account as infra part already has been > > > taken > > > > cared and Dockerfile is almost ready. > > > > > > > > On Wed, Jan 11, 2017 at 4:10 AM moon soo Lee > wrote: > > > > > > > > > Thanks Mina taking care of it. Sounds good to me. > > > > > > > > > > One thing is, shell we try have docker image in this release? > > > > > Following issues tracks the the job > > > > > https://issues.apache.org/jira/browse/ZEPPELIN-1711 > > > > > https://issues.apache.org/jira/browse/INFRA-12781 > > > > > > > > > > I don't think it need to be a blocker for 0.7.0 release, but if > they > > > can > > > > be > > > > > resolved by the time we create release candidate and have docker > > image > > > in > > > > > the release, it would be great. > > > > > > > > > > Thanks, > > > > > moon > > > > > > > > > > On Mon, Jan 9, 2017 at 10:24 PM Mina Lee > wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > It's been almost 3 month since we did 0.6.2 release and there > were > > > > number > > > > > > of improvements and bug fixes. > > > > > > Most of the items that we planned for 0.7.0 release [1] are ready > > > > > > so I am planning to cut branch-0.7 on 10th Jan 11pm(PST). > > > > > > > > > > > > After branch cut, bug fixes, documentation patches and issues > > linked > > > > as a > > > > > > blocker in jira [2] will be merged both to branch-0.7, master > > branch > > > > but > > > > > > new features will be merged only to master branch. > > > > > > > > > > > > Thanks, > > > > > > Mina > > > > > > > > > > > > [1] > > > > > https://cwiki.apache.org/confluence/display/ZEPPELIN/ > > Zeppelin+Roadmap > > > > > > [2] https://issues.apache.org/jira/browse/ZEPPELIN-1795 > > > > > > > > > > > > > > > > > > > > > > > > -- > Thanks, > Ashwin > -- Thanks, Ashwin
[GitHub] zeppelin issue #1873: [ZEPPELIN-1922] Exclude jackson-core and jackson-datab...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1873 @epahomov Thanks for the contribution. I'm trying to understand what cause this problem, because `zeppelin-zengine` shouldn't be a dependency of any interpreter and `/lib` directory supposed to not be included in the classpath of interpreter process. So excluding some library from `zeppelin-zengine` or removing jar from `lib/` directory shouldn't affect anything about classloading in interpreter. @epahomov, could you elaborate how interpreter classpath includes dependencies of `zeppelin-zengine` module? cc @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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
GitHub user cloverhearts opened a pull request: https://github.com/apache/zeppelin/pull/1896 implementation test case for connect to exists interpreter process ### What is this PR for? We need test case for remote interpreter process ( connect to exists process) ### What type of PR is it? [TEST case] ### What is the Jira issue? none (jira problem now) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloverhearts/zeppelin remoteInterpreterTEST Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1896.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1896 commit 87a5613f87b8e0e933be87a887da0206a4c6e15f Author: cloverheartsDate: 2017-01-13T02:14:40Z Implement test case for remote interpreter connect to exists process --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1884: [ZEPPELIN-1936] Fix user impersonation setting ...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1884 --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1858: [ZEPPELIN-1229] Clear browser cache with versio...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1858 --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1898: [TBD] set cron job executor to current user by ...
GitHub user khalidhuseynov opened a pull request: https://github.com/apache/zeppelin/pull/1898 [TBD] set cron job executor to current user by default ### What is this PR for? currently when executing cron job, backend doesn't know who initiated cron job (with subsequent save) unless user puts his name. This PR adds user name by default by keeping compatibility with current workflow. ### What type of PR is it? Improvement ### Todos * [x] - add user on front ### What is the Jira issue? TBD once jira back ### How should this be tested? go and set cron job ### Screenshots (if appropriate) ![cron_user](https://cloud.githubusercontent.com/assets/1642088/21919566/25330daa-d910-11e6-9373-aa3c44064f39.gif) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/khalidhuseynov/incubator-zeppelin cron-user Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1898.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1898 commit 0df35da71f1560dd4a2922ff99531ac67cb05c07 Author: Khalid HuseynovDate: 2017-01-13T05:32:02Z add logged cron executing user --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1891: [ZEPPELIN-1941] Fix cron job with release resource opt...
Github user OopsOutOfMemory commented on the issue: https://github.com/apache/zeppelin/pull/1891 @Leemoonsoo @jongyoul Any comments for 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 this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1831: [ZEPPELIN-1883] Can't import spark submitted packages ...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1831 Thanks @1ambda for the fix. Thanks @zjffdu for reviewing and verifying. It looks good to me, while it provides more consistent behavior between `PysparkInterpreter` and `SPARK_HOME/bin/pyspark`. Merge to master and branch-0.7 if no more comments. --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1842: [ZEPPELIN-1619] Load js package as a plugin visualizat...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1842 @AhyoungRyu Thanks for the review. Great to see High chart working nicely. A lot more improvements on Helium menu will be required, like search page, grouping packages by type, package list sort, etc. I'd like to address further improvements on Helium menu in separate 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 this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1891: [ZEPPELIN-1941] Fix cron job with release resource opt...
Github user OopsOutOfMemory commented on the issue: https://github.com/apache/zeppelin/pull/1891 I'm not sure, this PR is intent to fix the dead lock issue. --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1891: [ZEPPELIN-1941] Fix cron job with release resource opt...
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1891 Does this PR resolve flaky test that current master encounters? --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1890: [BUILD] Update release script
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1890 @minahlee I think `-Pr` doesn't mean anything because users cannot run R interpreter since `-Psparkr` is enabled. How about removing `-Pr` in a script? --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1861 merging if no more comment --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1894: [ZEPPELIN-1560] avoid generating minus sign in ...
GitHub user robbinspg opened a pull request: https://github.com/apache/zeppelin/pull/1894 [ZEPPELIN-1560] avoid generating minus sign in package name ### What is this PR for? using Object.hashCode() as part of the REPL wrapper class name can cause a compilation error as hashCode can validly return a negative integer. We would like this fix backported to 0.6 and later streams. ### What type of PR is it? Bug Fix ### Todos * [ ] - Task ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-1560 ### How should this be tested? regression tests with openJdk + tests with IBM jvm ### Screenshots (if appropriate) N/A ### Questions: * Does the licenses files need update? NO * Is there breaking changes for older versions? NO * Does this needs documentation? NO You can merge this pull request into a Git repository by running: $ git pull https://github.com/robbinspg/zeppelin ZPPELIN-1560 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1894.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1894 commit eeef3ad48f676da6be2248a9d6475ceb0db38917 Author: robbinsDate: 2017-01-12T15:15:29Z [ZEPPELIN-1560] avoid generating minus sign in package name --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1891: [ZEPPELIN-1941] Fix cron job with release resource opt...
Github user OopsOutOfMemory commented on the issue: https://github.com/apache/zeppelin/pull/1891 Flaky test may be another concurrency issue in scheduler execute jobs. --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1895: [HOTFIX] Improve stability of sync when get fai...
GitHub user khalidhuseynov opened a pull request: https://github.com/apache/zeppelin/pull/1895 [HOTFIX] Improve stability of sync when get fails ### What is this PR for? This is to improve the stability of sync mechanism when `get` from some backend storage fails (e.g. corrupt file, network issues). ### What type of PR is it? Bug Fix | Hot Fix ### Todos * [x] - handle exception ### What is the Jira issue? hotfix/issue when jira is back ### How should this be tested? CI green ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/khalidhuseynov/incubator-zeppelin fix-stability/sync-fail Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1895.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1895 commit 9d9656716529e5d358e67bc6d7f42f75769e3c78 Author: Khalid HuseynovDate: 2017-01-12T23:12:29Z catch failed get command --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1842: [ZEPPELIN-1619] Load js package as a plugin visualizat...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1842 @Leemoonsoo Thanks! I just suggested to have some default message like other pages (e.g. localhost:8080/#/interpreter -> there is "Manage interpreters settings. You can create / edit / remove settings. Note can bind / unbind these interpreter settings.")But it's just minor suggestion :) I tried to create new visualization package using HighCharts as you described in documentation, I didn't face any problem and it's definitely easier to create than before ð ![record](https://cloud.githubusercontent.com/assets/10060731/21900170/3a772144-d936-11e6-849d-ce047bb57ccc.gif) --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1894: [ZEPPELIN-1560] avoid generating minus sign in package...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1894 @robbinspg Great fix! CI failure looks not related. LGTM and merge to master, branch-0.7, branch-0.6 if no more comments! --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1868: [ZEPPELIN-1917] Improve python.conda interpreter
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1868 LGTM and merge to master if no more discussions --- 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 wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---