Re: Code inspection

2018-12-09 Thread Vyacheslav Daradur
Hi, Maxim, Nikolay, I have the following questions regarding inspections: Should 'gnite_inspections_teamcity.xml' been imported into IDEA, since 'ignite_inspections.xml' has been removed in actual master? Also, I've faced mismatching: if I use '@SuppressWarnings("ErrorNotRethrown")' in code, then

[GitHub] ignite pull request #5615: IGNITE-10177 cleanup Junit 3 from the project

2018-12-09 Thread oignatenko
GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/5615 IGNITE-10177 cleanup Junit 3 from the project You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10177 Alternati

[GitHub] ignite pull request #5616: IGNITE-10537

2018-12-09 Thread gvvinblade
GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/5616 IGNITE-10537 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10537 Alternatively you can review and apply the

Re: Default failure handler was changed for tests

2018-12-09 Thread Dmitrii Ryabov
Agree, it is reasonable to revert. пт, 7 дек. 2018 г. в 18:44, Dmitriy Pavlov : > > Hi Ilya, > > thank you for noticing. > > Calling to fail is equal to re-throw, > > throw new AssertionFailedError(message); > > So, yes, for now it is absolutely valid reason to revert and rework fix > > - a

[MTCGA]: new failures in builds [2481986] needs to be handled

2018-12-09 Thread dpavlov . tasks
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

[jira] [Created] (IGNITE-10609) Failed to remove cache from service configuration.

2018-12-09 Thread Alexey Kuznetsov (JIRA)
Alexey Kuznetsov created IGNITE-10609: - Summary: Failed to remove cache from service configuration. Key: IGNITE-10609 URL: https://issues.apache.org/jira/browse/IGNITE-10609 Project: Ignite

[jira] [Created] (IGNITE-10610) Change error to warning in VisorMultiNodeTask when no mapped jobs found.

2018-12-09 Thread Alexey Kuznetsov (JIRA)
Alexey Kuznetsov created IGNITE-10610: - Summary: Change error to warning in VisorMultiNodeTask when no mapped jobs found. Key: IGNITE-10610 URL: https://issues.apache.org/jira/browse/IGNITE-10610

Re: Support service on inactive cluster

2018-12-09 Thread Alexey Kuznetsov
Vyacheslav, Thanks for detailed explanation. As far as I see, we CAN support services on deactivated cluster, but it does not seems a good idea from end user perspective. I'm thinking that in my case (sending telemetry from cluster) I will go another way. -- Alexey Kuznetsov

[jira] [Created] (IGNITE-10611) Web Console: Refactor ActivitiesService to use uer object instead of id.

2018-12-09 Thread Alexey Kuznetsov (JIRA)
Alexey Kuznetsov created IGNITE-10611: - Summary: Web Console: Refactor ActivitiesService to use uer object instead of id. Key: IGNITE-10611 URL: https://issues.apache.org/jira/browse/IGNITE-10611

[jira] [Created] (IGNITE-10612) java.lang.IllegalAccessError: tried to access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class org.apache.ignite.internal.processors.query.h2.H2DatabaseType

2018-12-09 Thread kcheng.mvp (JIRA)
kcheng.mvp created IGNITE-10612: --- Summary: java.lang.IllegalAccessError: tried to access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class org.apache.ignite.internal.processors.query.h2.H2DatabaseType Key: IGNITE-10612

[jira] [Created] (IGNITE-10613) Web console: Failed to open import from database dialog in special case.

2018-12-09 Thread Vasiliy Sisko (JIRA)
Vasiliy Sisko created IGNITE-10613: -- Summary: Web console: Failed to open import from database dialog in special case. Key: IGNITE-10613 URL: https://issues.apache.org/jira/browse/IGNITE-10613 Projec

java.lang.IllegalAccessError: tried to access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class org.apache.ignite.internal.processors.query.h2.H2DatabaseType

2018-12-09 Thread kcheng.mvp
There are total 82 unite test for my system. this unit test works well in ignite 2.6. when I switch to ignite 2.7, I got below error for my unit tests I logged a ticket here https://issues.apache.org/jira/browse/IGNITE-10612 java.lang.IllegalAccessError: tried to access field org.h2.util.Lo

Re: [RESULT] [VOTE] Apache Ignite 2.7.0 Release (RC2)

2018-12-09 Thread Roman Shtykh
Nikolay, Do you know when npm (and other thin client) package will be uploaded? - $ npm i apache-ignite-client --save - npm ERR! code E404 - npm ERR! 404 Not Found: apache-ignite-client@lates -- Roman On Thursday, December 6, 2018, 7:20:33 a.m. GMT+9, Prachi Garg wrote:

[jira] [Created] (IGNITE-10614) investigate blocking of WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync at stopping grids when migrating from JUnit 3 to 4

2018-12-09 Thread Oleg Ignatenko (JIRA)
Oleg Ignatenko created IGNITE-10614: --- Summary: investigate blocking of WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync at stopping grids when migrating from JUnit 3 to 4 Key: IGNITE-10614 URL: ht

[GitHub] ignite pull request #5589: IGNITE-10382: Move datasets from example to ml mo...

2018-12-09 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5589 ---

Re: [RESULT] [VOTE] Apache Ignite 2.7.0 Release (RC2)

2018-12-09 Thread Nikolay Izhikov
Hello, Roman. Do we have release procedure for this pacakage? Let's develop one. Thin client developers, please,let me know, which artifacts should be uploaded to which package manager system. В Пн, 10/12/2018 в 04:30 +, Roman Shtykh пишет: > Nikolay, > Do you know when npm (and other thin

[GitHub] ignite pull request #5609: IGNITE-10589

2018-12-09 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5609 ---