[jira] [Created] (IGNITE-10031) REST: Introduce "caches" param for "top" command.

Alexey Kuznetsov created IGNITE-10031: - Summary: REST: Introduce "caches" param for "top" command. Key: IGNITE-10031 URL: https://issues.apache.org/jira/browse/IGNITE-10031 Project: Ignite

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

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

Re: Code inspection

Hi Maxim, thank you for your efforts to make this happen. Keep the pace! Could you please provide an example of how Inspections can fail, so I or another contributor could implement support of these failures validation in the Tc Bot. Sincerely, Dmitriy Pavlov пт, 26 окт. 2018 г. в 18:27, Yakov

[GitHub] ignite pull request #5094: Ignite-2.5.1-master-7196

GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/5094 Ignite-2.5.1-master-7196 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-master-7196 Alternatively yo

[jira] [Created] (IGNITE-10030) [TC Bot] Background upload of changes, problems, and statistics

Dmitriy Pavlov created IGNITE-10030: --- Summary: [TC Bot] Background upload of changes, problems, and statistics Key: IGNITE-10030 URL: https://issues.apache.org/jira/browse/IGNITE-10030 Project: Igni

[GitHub] asfgit closed pull request #43: IGNITE-9848 load all builds

asfgit closed pull request #43: IGNITE-9848 load all builds URL: https://github.com/apache/ignite-teamcity-bot/pull/43 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub

[jira] [Created] (IGNITE-10029) Node attributes are not restored from metastore after node restart.

Alexei Scherbakov created IGNITE-10029: -- Summary: Node attributes are not restored from metastore after node restart. Key: IGNITE-10029 URL: https://issues.apache.org/jira/browse/IGNITE-10029 Pro

Re: Thin clients all in one

Stepan! TL/DR: what you got with Python client in your gist is an intended behavior. Explanation: As per docs, Object array contains of type ID (which is defaults to -1) and an array of objects. https://apacheignite.readme.io/docs/binary-client-protocol-data-format#section-object-array Your

[GitHub] ignite pull request #5093: IGNITE-10028

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5093 IGNITE-10028 Incorrect handling of page on replacement You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-10028

[jira] [Created] (IGNITE-10028) Incorrect handling of page on replacement

Vladislav Pyatkov created IGNITE-10028: -- Summary: Incorrect handling of page on replacement Key: IGNITE-10028 URL: https://issues.apache.org/jira/browse/IGNITE-10028 Project: Ignite Issu

[GitHub] ignite pull request #5090: IGNITE-10026: [ML] Broken example: GaussianNaiveB...

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

[GitHub] ignite pull request #5092: TDR-93 Several WAL compressor fixes.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/5092 TDR-93 Several WAL compressor fixes. For test purposes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite tdr-93

Re: Code inspection

Maxim, Thanks for response, let's do it the way you suggested. Please consider adding more checks - line endings. I think we should only have \n - ensure blank line in the end of file All these are code reviews issues I pointed out many times when reviewing conributions. It would be cool if we h

Re: Thin clients all in one

Oh, now i finally understand (PHP and JS). And more, just found tests with usage example (don't now why im just missed it) Thank you Waiting for Dmitry пт, 26 окт. 2018 г. в 18:00, Alexey Kosenchuk < alexey.kosenc...@nobitlost.com>: > thanks, now it's clear. > > For NodeJs and PHP clients: >

Re: Pre-touch for Ignite off-heap memory

Andrey, Probability of a OOM kill will be much lower if offheap is pretouched. What do you mean by JVM internal needs? In my understanding if user enables option to pretouch heap and fixes the heap to prevent jvm releasing memory back to OS, then OOM killing is very unlikely. I would agree that p

Re: Code inspection

Pert, > As new way of testing code, this process will take it’s time to become common, and then there will be no obsolete branches. I tend to agree with you. Let's stabilize the solution first. Yakov, > Maxim, what are our next steps? Can we add check for > - line length > - indents (tabs vs s

Re: Thin clients all in one

thanks, now it's clear. For NodeJs and PHP clients: You cannot use OBJECT_ARRAY constant to specify a field type. This is true for all non-primitive types. That's why you get ""type" argument has incorrect value" exception. Non-primitive types can be specified using special objects. In this

[GitHub] ignite pull request #5091: IGNITE-8873 Test fix

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/5091 IGNITE-8873 Test fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8873 Alternatively you can review and

[GitHub] ignite pull request #5090: IGNITE-10026: [ML] Broken example: GaussianNaiveB...

GitHub user YuriBabak opened a pull request: https://github.com/apache/ignite/pull/5090 IGNITE-10026: [ML] Broken example: GaussianNaiveBayesTrainerExample fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-igni

Re: Code inspection

Also, let me note that currently only modules/core/** is under inspection. And in spite of the fact that core is the “heaviest" module in project. it seems that adding new inspections should be 2-way: new inspections and new modules (builds). > On 26 Oct 2018, at 17:41, Yakov Zhdanov wrote: >

Re: Can't use array as a cache key from thin clients (ignite-9991)

I don't see a major issue here. Set priority to a minor. Best Regards, Igor On Fri, Oct 26, 2018 at 5:07 PM Alexey Kosenchuk < alexey.kosenc...@nobitlost.com> wrote: > The problem is reproduced with Java, NodeJs, PHP, Python thin clients. > > This seems the server's issue. > > Can an expert in

[jira] [Created] (IGNITE-10027) Optimistic transaction doesn't throw TransactionTimeoutException on lock acquisition timeout.

Alexei Scherbakov created IGNITE-10027: -- Summary: Optimistic transaction doesn't throw TransactionTimeoutException on lock acquisition timeout. Key: IGNITE-10027 URL: https://issues.apache.org/jira/browse/IGN

[jira] [Created] (IGNITE-10026) [ML] Broken example: GaussianNaiveBayesTrainerExample

Yury Babak created IGNITE-10026: --- Summary: [ML] Broken example: GaussianNaiveBayesTrainerExample Key: IGNITE-10026 URL: https://issues.apache.org/jira/browse/IGNITE-10026 Project: Ignite Issue

Re: Code inspection

Agree with Petr. Maxim, what are our next steps? Can we add check for - line length - indents (tabs vs spaces) This may require some efforts (will it and how much?), but can we add check for: - log messages structure - log.warn() vs U.warn() - abbreviations for local variables and fields. And la

[GitHub] ignite pull request #5089: IGNITE-8902 One-phase commit race on tx timeout

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/5089 IGNITE-8902 One-phase commit race on tx timeout You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8902 Altern

[jira] [Created] (IGNITE-10025) CPP: Runtime code deployment

Igor Sapego created IGNITE-10025: Summary: CPP: Runtime code deployment Key: IGNITE-10025 URL: https://issues.apache.org/jira/browse/IGNITE-10025 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #5065: Limit test execution time to 10 sec

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

Re: Thin clients all in one

No Now tried code and output - https://gist.github.com/pilshchikov/4c02057e624baa54326a1e75b4ee3f46 And it looks like it works пт, 26 окт. 2018 г. в 17:10, Alexey Kosenchuk < alexey.kosenc...@nobitlost.com>: > Hi Stepan, > > Have you tried the same with Java and .net thin clients as well and > e

Re: Thin clients all in one

Hi Stepan, Have you tried the same with Java and .net thin clients as well and everything work fine? Thanks, -Alexey 26.10.2018 16:57, Stepan Pilschikov пишет: Hi, everyone Create new thread to centralize cross compatibility and others common problems between thin clients Tying to use Ob

Can't use array as a cache key from thin clients (ignite-9991)

The problem is reproduced with Java, NodeJs, PHP, Python thin clients. This seems the server's issue. Can an expert in the server have a look, please? The details are in the jira [1] Thanks, -Alexey [1] https://issues.apache.org/jira/browse/IGNITE-9991

Thin clients all in one

Hi, everyone Create new thread to centralize cross compatibility and others common problems between thin clients Tying to use Object array to exchange different data between JS, PHP and Python thin clients JS and PHP simply can't put any type of arrays Python can put data, but if you take it, da

Re: Unreliable checks in tests for string presence in GridStringLogger contents

Thanks for comments, I have filed a ticket [1] and will implement it if you don't mind. 1. https://issues.apache.org/jira/browse/IGNITE-10023 пт, 26 окт. 2018 г. в 15:56, Dmitrii Ryabov : > > > waitForCondition(lsnr::check, timeout); > Agree, it is more convenient to use. > пт, 26 окт. 2018 г. в

[jira] [Created] (IGNITE-10024) MVCC TX: Stackoverflow during DhtEnlistFuture mapping

Roman Kondakov created IGNITE-10024: --- Summary: MVCC TX: Stackoverflow during DhtEnlistFuture mapping Key: IGNITE-10024 URL: https://issues.apache.org/jira/browse/IGNITE-10024 Project: Ignite

[jira] [Created] (IGNITE-10023) Improve ListeningTestLogger for wait conditions.

Amelchev Nikita created IGNITE-10023: Summary: Improve ListeningTestLogger for wait conditions. Key: IGNITE-10023 URL: https://issues.apache.org/jira/browse/IGNITE-10023 Project: Ignite I

[jira] [Created] (IGNITE-10022) JS, PHP thin clients: a more meaningful exception when ENUM type is not registered

Alexey Kosenchuk created IGNITE-10022: - Summary: JS, PHP thin clients: a more meaningful exception when ENUM type is not registered Key: IGNITE-10022 URL: https://issues.apache.org/jira/browse/IGNITE-10022

[GitHub] ignite pull request #5088: IGNITE-10004: Add test.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5088 IGNITE-10004: Add test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10004 Alternatively you can review an

[GitHub] ignite pull request #5028: IGNITE-9910: Move the static copy-pasted datasets...

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

Re: Unreliable checks in tests for string presence in GridStringLogger contents

> waitForCondition(lsnr::check, timeout); Agree, it is more convenient to use. пт, 26 окт. 2018 г. в 13:01, Pavel Pereslegin : > > Nikita, > personally, I don’t like that "check()" throws an AssertionError, but in > the case of a composite listener, it will indicate which of the conditions > did no

[jira] [Created] (IGNITE-10021) IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange

Oleg Ignatenko created IGNITE-10021: --- Summary: IgniteInterruptedCheckedException: sleep interrupted in GridServiceProcessorBatchDeploySelfTest#testCancelAllTopologyChange Key: IGNITE-10021 URL: https://issues.ap

[GitHub] ignite pull request #4442: IGNITE-7165: skip rebalance if assigns not change...

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

[GitHub] ignite pull request #4097: IGNITE-7165: suggesstions by AV

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

[GitHub] ignite pull request #4833: Ig 7196 retest

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

[GitHub] ignite pull request #4851: Ig 7196 changes without master PME optimizations

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

[GitHub] ignite pull request #4520: IGNITE-7196 Exchange stucks on reading WAL

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

[GitHub] SomeFire commented on a change in pull request #38: IGNITE-9849 Remove invalid builds from the selection

SomeFire commented on a change in pull request #38: IGNITE-9849 Remove invalid builds from the selection URL: https://github.com/apache/ignite-teamcity-bot/pull/38#discussion_r228498911 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTes

[GitHub] SomeFire commented on a change in pull request #38: IGNITE-9849 Remove invalid builds from the selection

SomeFire commented on a change in pull request #38: IGNITE-9849 Remove invalid builds from the selection URL: https://github.com/apache/ignite-teamcity-bot/pull/38#discussion_r228497136 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildCondi

[GitHub] SomeFire commented on a change in pull request #38: IGNITE-9849 Remove invalid builds from the selection

SomeFire commented on a change in pull request #38: IGNITE-9849 Remove invalid builds from the selection URL: https://github.com/apache/ignite-teamcity-bot/pull/38#discussion_r228495040 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/condition/BuildCondi

[GitHub] asfgit closed pull request #38: IGNITE-9849 Remove invalid builds from the selection

asfgit closed pull request #38: IGNITE-9849 Remove invalid builds from the selection URL: https://github.com/apache/ignite-teamcity-bot/pull/38 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As t

[GitHub] ignite pull request #5087: IGNITE-10020 control.sh error: Comparison method ...

GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/5087 IGNITE-10020 control.sh error: Comparison method violates its general contract! You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/

Re: Code inspection

> On 26 Oct 2018, at 12:02, Maxim Muzafarov wrote: > > Petr, > >> Disclaimer: currently, on branches with no inspections file there is > default inspections file with all inspections turned off > > I'd suggest another approach: > - we should use the default inspection configuration file only

[jira] [Created] (IGNITE-10020) control.sh error: Comparison method violates its general contract!

Alexand Polyakov created IGNITE-10020: - Summary: control.sh error: Comparison method violates its general contract! Key: IGNITE-10020 URL: https://issues.apache.org/jira/browse/IGNITE-10020 Projec

Re: Documentation: dead links

25.10.2018 18:25, Artem Budnikov пишет: Hi Pavel, 1) I fixed the broken link. Thanks for pointing out. Thank you! 2) Yes, that is a common problem, and as far as I know, we don't have such a check, but we will when we adopt the new docs publishing process (markdown-to-html-pulled-from-g

[jira] [Created] (IGNITE-10019) Documentation: partition preloading

Alexei Scherbakov created IGNITE-10019: -- Summary: Documentation: partition preloading Key: IGNITE-10019 URL: https://issues.apache.org/jira/browse/IGNITE-10019 Project: Ignite Issue Type

[GitHub] ignite pull request #5053: IGNITE-8873 Preload cache partition into page mem...

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

[GitHub] ignite pull request #5086: IGNITE-9982: SQLLine: can't run with option --aut...

GitHub user pavlukhin opened a pull request: https://github.com/apache/ignite/pull/5086 IGNITE-9982: SQLLine: can't run with option --autoCommit=false or true You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Unreliable checks in tests for string presence in GridStringLogger contents

Nikita, personally, I don’t like that "check()" throws an AssertionError, but in the case of a composite listener, it will indicate which of the conditions did not work. Btw, your case can be solved with custom listener, but I think it's good improvement, let's do it. чт, 25 окт. 2018 г. в 21:31,

[GitHub] ignite pull request #5085: IGNITE-10017: Fix for infinite loop with 3rd part...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/5085 IGNITE-10017: Fix for infinite loop with 3rd party persistency, keepB… …inary and no value for the key. You can merge this pull request into a Git repository by running: $ git pull https:/

[jira] [Created] (IGNITE-10018) Docuementation: manage SQL (ODBC\JDBC\Thin) clients via JMX.

Andrew Mashenkov created IGNITE-10018: - Summary: Docuementation: manage SQL (ODBC\JDBC\Thin) clients via JMX. Key: IGNITE-10018 URL: https://issues.apache.org/jira/browse/IGNITE-10018 Project: Ign

[jira] [Created] (IGNITE-10017) Infinite loop with 3rd party persistency, keepBinary and no value for the key

Roman Shtykh created IGNITE-10017: - Summary: Infinite loop with 3rd party persistency, keepBinary and no value for the key Key: IGNITE-10017 URL: https://issues.apache.org/jira/browse/IGNITE-10017 Pro

Re: Pre-touch for Ignite off-heap memory

Hi Alex, 1. Pre-touch will not save from killing node by OS if there will not enough memory for JVM internal needs, anyway. Ignite data region setting has MIN and MAX sizes. Ignite split memory region into segments, first segment is size of MIN. Next segments are allocated on demand (up to MAX) an

[jira] [Created] (IGNITE-10016) Web Console: ClusterLoginService should return credentials modal as singelton

Alexey Kuznetsov created IGNITE-10016: - Summary: Web Console: ClusterLoginService should return credentials modal as singelton Key: IGNITE-10016 URL: https://issues.apache.org/jira/browse/IGNITE-10016

[GitHub] ignite pull request #5059: IGNITE-9983: add ignite inspections config for te...

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

Re: Code inspection

Petr, > Disclaimer: currently, on branches with no inspections file there is default inspections file with all inspections turned off I'd suggest another approach: - we should use the default inspection configuration file only for old release branches like (2.5, 2.6 etc.); - the other branches

Re: Code inspection

Hello, Maxim! Good job! пт, 26 окт. 2018 г. в 0:47, Maxim Muzafarov : > Igniters, > > The new `Inspections: Core` suite [2] configured on TeamCity (pass > successfully with - Inspections total: 0, errors: 0 ). > The next rules are enabled for this suite: > - `Missorted modifiers`; > - `'size()

[GitHub] ignite pull request #5066: IGNITE-9454 Support CACHE_CREATE, CACHE_DESTROY, ...

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

[jira] [Created] (IGNITE-10015) Sprodic JVM crash due to restart nodes

Sergey Kozlov created IGNITE-10015: -- Summary: Sprodic JVM crash due to restart nodes Key: IGNITE-10015 URL: https://issues.apache.org/jira/browse/IGNITE-10015 Project: Ignite Issue Type: Bu

Re: Problem with reading incomplete payload - IGNITE-7153

Hi, Thanks for your reply. I think current implementation (based on R2.6) does exactly what you mentioned as of in GridNioServer . The problem is that in redis

[jira] [Created] (IGNITE-10014) MVCC usability: Improve description for concurrent operation exceptions

Stepan Pilschikov created IGNITE-10014: -- Summary: MVCC usability: Improve description for concurrent operation exceptions Key: IGNITE-10014 URL: https://issues.apache.org/jira/browse/IGNITE-10014

Re: Code inspection

Added -> Run :: IntelliJ IDEA Inspections [1] to Run All Disclaimer: currently, on branches with no inspections file there is default inspections file with all inspections turned off [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections > On 2

Re: Code inspection

+1 On Fri, Oct 26, 2018 at 9:45 AM Nikolay Izhikov wrote: > Hello, Maxim. > > Great job! Thank you! > Igniters, let's add this suite to the Run All! > > It can help us improve code quality and check code style without human > eyes. > > > В Пт, 26/10/2018 в 00:47 +0300, Maxim Muzafarov пишет: > >

Re: Apache Ignite 2.7. Last Mile

Hi Nikolay, I do not know. We need to investigate them first. These are all regressions, so decision about impact and urgency should be made separately for every ticket. On Fri, Oct 26, 2018 at 9:57 AM Nikolay Izhikov wrote: > Hello, Igniters. > > We have *9* tickets mapped to 2.7 today > > Vla