[jira] [Created] (IGNITE-9027) Web console: "Tried to load angular more than once" in unit tests

Ilya Borisov created IGNITE-9027: Summary: Web console: "Tried to load angular more than once" in unit tests Key: IGNITE-9027 URL: https://issues.apache.org/jira/browse/IGNITE-9027 Project: Ignite

[jira] [Created] (IGNITE-9026) Two levels of Peer class loading fails in CONTINUOUS mode

David Harvey created IGNITE-9026: Summary: Two levels of Peer class loading fails in CONTINUOUS mode Key: IGNITE-9026 URL: https://issues.apache.org/jira/browse/IGNITE-9026 Project: Ignite

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

Hi Ignite Developer, I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I hope you can help. *New Critical Failure in master Data Structures https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv No

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

Odd flaky tests notifications were fixed. If test changes its status more than 6 times in last 50 runs, than it is required to fail 7 times in a row to be considered as new failure. Normal test can be considered as new failure if it fails 3 times. I would appreciate any feedback and proposals of

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

Same as for previous notification, this is another 3 timeouts in a row occurred. I hope soon we will be able to fix all timeouts, so such notifications will not appear. вт, 17 июл. 2018 г. в 22:17, : > Hi Ignite Developer, > > I am MTCGA.Bot, and I've detected some issue on TeamCity to be

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

Hi Ignite Developer, I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I hope you can help. *New Critical Failure in master Data Structures https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv

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

Hi Igniters, The Bot was updated to handle timeouts & JVM crashes in suites in a special way. These type of failures are named Critical. If 3 or more (timeouts/JMV crashes) occured several times in a row, such notification will be send. Also it is required that last run was completed with

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

Hi Ignite Developer, I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I hope you can help. *New Critical Failure in master Data Structures https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv No

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

Andrey G., As a PMC member and release manager of 2.6, could you please help the folks to finish this step? -- Denis On Tue, Jul 17, 2018 at 9:58 AM Pavel Tupitsyn wrote: > I think it makes sense that only PMCs have rights to do so, > especially because publishing a package can not be undone

[GitHub] ignite pull request #4376: IGNITE-9024 Wrong usage of idxLatch in DynamicInd...

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/4376 IGNITE-9024 Wrong usage of idxLatch in DynamicIndexAbstractConcurrent… …SelfTest You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #4377: IGNITE-9025 "PDS 1" TC configuration could hang b...

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/4377 IGNITE-9025 "PDS 1" TC configuration could hang because of SegmentedR… …ingByteBufferTest Signed-off-by: EdShangGG You can merge this pull request into a Git repository by running:

[jira] [Created] (IGNITE-9025) "PDS 1" TC configuration could hang because of SegmentedRingByteBufferTest

Eduard Shangareev created IGNITE-9025: - Summary: "PDS 1" TC configuration could hang because of SegmentedRingByteBufferTest Key: IGNITE-9025 URL: https://issues.apache.org/jira/browse/IGNITE-9025

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

I think it makes sense that only PMCs have rights to do so, especially because publishing a package can not be undone of re-done, only a new version can be published if there is some issue. Also, restricted SVN area is the only feasible way to share secrets with the team that I know of. Another

[jira] [Created] (IGNITE-9024) Wrong usage of IdxLatch in DynamicIndexAbstractConcurrentSelfTest

Dmitriy Sorokin created IGNITE-9024: --- Summary: Wrong usage of IdxLatch in DynamicIndexAbstractConcurrentSelfTest Key: IGNITE-9024 URL: https://issues.apache.org/jira/browse/IGNITE-9024 Project:

[GitHub] ignite pull request #4375: tests for ignite 5980

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/4375 tests for ignite 5980 You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite IGNITE-5980 Alternatively you can review and apply these

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

Oh, I see. I have no access there. I guess only PMC can upload packages to nuget.org … > On 17 Jul 2018, at 18:21, Pavel Tupitsyn wrote: > > Oh sorry I missed the question. > * The build script '[Prepare Vote #3] Build NuGet packages' produces the > artifacts (.nupkg

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

Petr, there is an SVN link in my previous message, can you please check again? Thanks On Tue, Jul 17, 2018 at 6:41 PM Petr Ivanov wrote: > Pavel, > > > Can you help with API key, please? > Where it can be obtained. > > Also I did not get it right — while issuing nuget push the packages will >

Re: Async cache groups rebalance not started with rebalanceOrder ZERO

Yakov, But we already have DFLT_SEND_RETRY_CNT and DFLT_SEND_RETRY_DELAY for configuring our CommunicationSPI behavior. What if user configure this parameters his own way and he will see a lot of WARN messages in log which have no sense? May be we use

[jira] [Created] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.

Ivan Daschinskiy created IGNITE-9023: Summary: LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request. Key: IGNITE-9023 URL:

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

Pavel, Can you help with API key, please? Where it can be obtained. Also I did not get it right — while issuing nuget push the packages will be deployed to some default host or host should be specified manually somehow? > On 17 Jul 2018, at 18:21, Pavel Tupitsyn wrote: > > Oh sorry I

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

Oh sorry I missed the question. * The build script '[Prepare Vote #3] Build NuGet packages' produces the artifacts (.nupkg files). * Then we have to manually upload them to NuGet org, which requires an API key or an account with access to these packages API key can be found in [1] (which is

[GitHub] ignite pull request #4369: Ignite-9013

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4369 ---

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

Just tell us please HOW it should be done, please. With what build or script or other procedure? > On 17 Jul 2018, at 17:44, Pavel Tupitsyn wrote: > > Peter, > > I can do it anytime when we confirm the right Artifacts build. > Can you please clarify what " Before uploading, please check

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

Peter, I can do it anytime when we confirm the right Artifacts build. Can you please clarify what " Before uploading, please check this [1] build. " is about? Thanks, Pavel On Tue, Jul 17, 2018 at 8:36 AM Peter Ivanov wrote: > Pavel, > > > Can you give a cue where can be uploaded Nuget

[GitHub] ignite pull request #4367: IGNITE-9012 Test IgniteServiceReassignmentTest.te...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4367 ---

[GitHub] ignite pull request #4362: IGNITE-9004 rollback formatFile changes

Github user akalash closed the pull request at: https://github.com/apache/ignite/pull/4362 ---

[jira] [Created] (IGNITE-9022) [ML] Implement class labels mapping for SVM binary classifier

Alexey Platonov created IGNITE-9022: --- Summary: [ML] Implement class labels mapping for SVM binary classifier Key: IGNITE-9022 URL: https://issues.apache.org/jira/browse/IGNITE-9022 Project: Ignite

[GitHub] ignite pull request #4373: IGNITE-9018 PDS1 TC configuration hangs periodica...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4373 ---

[GitHub] ignite pull request #4345: IGNITE-8975: Correct handling compressed archived...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4345 ---

[jira] [Created] (IGNITE-9021) [ML] Refactor vectors to dence/sparse

Yury Babak created IGNITE-9021: -- Summary: [ML] Refactor vectors to dence/sparse Key: IGNITE-9021 URL: https://issues.apache.org/jira/browse/IGNITE-9021 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #4287: IGNITE-8684 fix partition state exchange during r...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4287 ---

Re: Upgrading Ignite to JCache 1.1

Pavel, Could you chime in please? -- Denis On Tue, Jul 17, 2018 at 6:43 AM Nikita Amelchev wrote: > Hi, Igniters. > > I'm implementing new version TCK 1.1 and I found the problem [1] in the > .NET module. > > In brief, .NET creates cache entry event based on values exist checking. > > TCK 1.1

Re: Upgrading Ignite to JCache 1.1

Hi, Igniters. I'm implementing new version TCK 1.1 and I found the problem [1] in the .NET module. In brief, .NET creates cache entry event based on values exist checking. TCK 1.1 says that getValue() not null for REMOVE/EXPIRED events if old value required and it breaks logic. I'm looking for

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

These tests were intentionally failed with link to https://issues.apache.org/jira/browse/IGNITE-9004 ticket. This avoids suite timeout. вт, 17 июл. 2018 г. в 16:36, : > Hi Ignite Developer, > > I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. > I hope you can help. > >

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

Hi Ignite Developer, I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I hope you can help. *New test failure in master IgniteChangeGlobalStateTest.testStopPrimaryAndActivateFromServerNode

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

Hi Igniters, this test was intentionally failed with link to https://issues.apache.org/jira/browse/IGNITE-9004 ticket. I hope Igniters will figure out why it was failing suite. Sincerely, Dmitriy Pavlov вт, 17 июл. 2018 г. в 16:22, : > Hi Ignite Developer, > > I am MTCGA.Bot, and I've

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

Hi Ignite Developer, I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I hope you can help. *New test failure in master IgniteChangeGlobalStateTest.testConcurrentActivateFromClientNodeAndServerNode

[jira] [Created] (IGNITE-9020) .NET: Creating CacheEntry events regardless of values.

Amelchev Nikita created IGNITE-9020: --- Summary: .NET: Creating CacheEntry events regardless of values. Key: IGNITE-9020 URL: https://issues.apache.org/jira/browse/IGNITE-9020 Project: Ignite

[jira] [Created] (IGNITE-9019) Ignite prints redundant warnings on node start

Evgenii Zhuravlev created IGNITE-9019: - Summary: Ignite prints redundant warnings on node start Key: IGNITE-9019 URL: https://issues.apache.org/jira/browse/IGNITE-9019 Project: Ignite

[GitHub] ignite pull request #4361: IGNITE-9002: Fixed C++ thin client crash when use...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4361 ---

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

Hi, Stanislav L. replied in ticket https://issues.apache.org/jira/browse/IGNITE-9005 пн, 16 июл. 2018 г. в 18:15, kcheng.mvp : > I checked the source code and found that this issue may be caused by this > line > > org.apache.ignite.internal.processors.cache.GridCacheProcessor #1452 > >

[GitHub] ignite pull request #4373: IGNITE-9018 PDS1 TC configuration hangs periodica...

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/4373 IGNITE-9018 PDS1 TC configuration hangs periodically Signed-off-by: EdShangGG You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-9018) PDS1 TC configuration hangs periodically

Eduard Shangareev created IGNITE-9018: - Summary: PDS1 TC configuration hangs periodically Key: IGNITE-9018 URL: https://issues.apache.org/jira/browse/IGNITE-9018 Project: Ignite Issue

Re: Neighbors exclusion

Hi Yakov, Not sure if it's a good idea, because if we remove that flag, it will mean that left only one way to set previous logic - implement backup filter. And I don't know how it will influence persistence. I think it's a good candidate for 3.0 as it's not so urgent. Thanks! 16.07.2018

[jira] [Created] (IGNITE-9017) .NET: Clear cache statistics

Denis Garus created IGNITE-9017: --- Summary: .NET: Clear cache statistics Key: IGNITE-9017 URL: https://issues.apache.org/jira/browse/IGNITE-9017 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-9016) Byte arrays are not working as cache keys

Evgenii Zhuravlev created IGNITE-9016: - Summary: Byte arrays are not working as cache keys Key: IGNITE-9016 URL: https://issues.apache.org/jira/browse/IGNITE-9016 Project: Ignite Issue

[GitHub] ignite pull request #4372: IGNITE-8929 test reproducer + simple fix.

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/4372 IGNITE-8929 test reproducer + simple fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8929-2

[GitHub] ignite pull request #4371: IGNITE-9014: Thin С++ client included in binary ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4371 ---

[GitHub] ignite pull request #4305: IGNITE-8929 WAL should not disable for the group ...

Github user DmitriyGovorukhin closed the pull request at: https://github.com/apache/ignite/pull/4305 ---

[GitHub] ignite pull request #4273: IGNITE-809 test run 200 times

Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/4273 ---

[GitHub] ignite pull request #4371: IGNITE-9014: Thin С++ client included in binary ...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/4371 IGNITE-9014: Thin С++ client included in binary release You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9014

[jira] [Created] (IGNITE-9014) CPP Thin: Thin client is not present in binary release

Igor Sapego created IGNITE-9014: --- Summary: CPP Thin: Thin client is not present in binary release Key: IGNITE-9014 URL: https://issues.apache.org/jira/browse/IGNITE-9014 Project: Ignite Issue

Re: Neighbors exclusion

Hi Dmitry, I agree with Val. It seems to me that this flag does not make sense and we can get rid of it. The most important thing that you mentioned (at least for me) is the following: > 2. if there are not enough backup nodes (or no backupFilter) - try to distribute according to

Re: Ignite guide for community developes

Colleges, thanks for your assistance, I'm very interested in Ignite participation. I made registration in Jira and Wiki, user: vgrigorev in both sites, e-mail: vgri...@mail.ru Also, please give me reference how to work in proposed process or make short instructions -- Sent from:

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

Hi Igniters, Seems this test is flaky: it has frequent changes of its status. This can be detected in Bot. and I'll update Bot once issue https://github.com/dspavlov/ignite-teamcity-helper/issues/14 is completed. So please ignore this failure for now, as it is not new. Of course if you know how