Re: Question: network issues of single node.

2020-06-05 Thread Vladimir Steshin
Denis, I have no nodes that I'm unable to interconnect. This case is simulated in IgniteDiscoveryMassiveNodeFailTest.testMassiveFailSelfKill() Introduced in [1]. I’m asking if it is real or supposed problem. Where it was met? Which network configuration/issues could be? [1] https://issues.

[jira] [Created] (IGNITE-13120) Move control.sh to a separate module and add framework for command autocompletion

2020-06-05 Thread Kirill Tkalenko (Jira)
Kirill Tkalenko created IGNITE-13120: Summary: Move control.sh to a separate module and add framework for command autocompletion Key: IGNITE-13120 URL: https://issues.apache.org/jira/browse/IGNITE-13120

Re: [DISCUSSION] Add autocompletion for commands in control.sh

2020-06-05 Thread ткаленко кирилл
Folks have created a ticket [1]. 1 - https://issues.apache.org/jira/browse/IGNITE-13120 02.06.2020, 16:48, "ткаленко кирилл" : > Maxim I suggested moving control.sh in a separate module, are we talking > about the same thing? > > 02.06.2020, 16:15, "Maxim Muzafarov" : >>  Folks, >> >>  +1 >> >>

[jira] [Created] (IGNITE-13121) Incorrect "Completed partition exchange" message triggered by client node (dis)connect.

2020-06-05 Thread Stanilovsky Evgeny (Jira)
Stanilovsky Evgeny created IGNITE-13121: --- Summary: Incorrect "Completed partition exchange" message triggered by client node (dis)connect. Key: IGNITE-13121 URL: https://issues.apache.org/jira/browse/IGNITE-

[jira] [Created] (IGNITE-13122) Snapshot task may throw NullPointerException on concurrent stop

2020-06-05 Thread Maxim Muzafarov (Jira)
Maxim Muzafarov created IGNITE-13122: Summary: Snapshot task may throw NullPointerException on concurrent stop Key: IGNITE-13122 URL: https://issues.apache.org/jira/browse/IGNITE-13122 Project: Ig

[jira] [Created] (IGNITE-13123) Move control.sh to a separate module

2020-06-05 Thread Kirill Tkalenko (Jira)
Kirill Tkalenko created IGNITE-13123: Summary: Move control.sh to a separate module Key: IGNITE-13123 URL: https://issues.apache.org/jira/browse/IGNITE-13123 Project: Ignite Issue Type: I

[jira] [Created] (IGNITE-13124) Implement autocompletion for control.sh

2020-06-05 Thread Kirill Tkalenko (Jira)
Kirill Tkalenko created IGNITE-13124: Summary: Implement autocompletion for control.sh Key: IGNITE-13124 URL: https://issues.apache.org/jira/browse/IGNITE-13124 Project: Ignite Issue Type

[jira] [Created] (IGNITE-13125) SQL regressions framework: Random query generation

2020-06-05 Thread Roman Kondakov (Jira)
Roman Kondakov created IGNITE-13125: --- Summary: SQL regressions framework: Random query generation Key: IGNITE-13125 URL: https://issues.apache.org/jira/browse/IGNITE-13125 Project: Ignite I

Re: Incorrect example in Pull Request checklist: comma after ticket name in commit message

2020-06-05 Thread Ilya Kasnacheev
Hello! I think we have consensus here. Can you merge it? Thanks, -- Ilya Kasnacheev ср, 3 июн. 2020 г. в 16:38, Andrey Gura : > I've prepared PR [1] > > I already tried to discuss commit message format [2] but stumbled upon > some criticism. I still believe that we have to follow only one >

[jira] [Created] (IGNITE-13126) Refactor of Continuous Query buffers to reduce heap usage

2020-06-05 Thread Maxim Muzafarov (Jira)
Maxim Muzafarov created IGNITE-13126: Summary: Refactor of Continuous Query buffers to reduce heap usage Key: IGNITE-13126 URL: https://issues.apache.org/jira/browse/IGNITE-13126 Project: Ignite

Re: [CVE-2020-1963] Apache Ignite access to file system disclosure vulnerability

2020-06-05 Thread Denis Magda
Yury, Could you please update the CVE with the details from this announcement? Nick, to my knowledge, there are no any plans to propagate this fix to the downstream versions such as 2.7, etc. - Denis On Wed, Jun 3, 2020 at 8:10 AM Nick Popov wrote: > Are you going to provide CVE-2020-1964 pa

Re: Incorrect example in Pull Request checklist: comma after ticket name in commit message

2020-06-05 Thread Maxim Muzafarov
Folks, It seems that the PR title mentioned above [1] does not satisfy both of the discussed patterns (with colon and without it). Is it correct? Am I missing something previously discussed? [1] https://github.com/apache/ignite/pull/7894 On Fri, 5 Jun 2020 at 16:55, Ilya Kasnacheev wrote: > >

Re: Incorrect example in Pull Request checklist: comma after ticket name in commit message

2020-06-05 Thread Andrey Gura
I just didn't create JIRA issue. But it will be created. Is there any other comments about change? On Fri, Jun 5, 2020 at 7:31 PM Maxim Muzafarov wrote: > > Folks, > > It seems that the PR title mentioned above [1] does not satisfy both > of the discussed patterns (with colon and without it). >

Re: Incorrect example in Pull Request checklist: comma after ticket name in commit message

2020-06-05 Thread Maxim Muzafarov
+1 to change, Actually it doesn't matter if we have consistency between PR pattern and coding guidelines. Sorry, if I've missed something during the PR pattern preparation. On Fri, 5 Jun 2020 at 19:37, Andrey Gura wrote: > > I just didn't create JIRA issue. But it will be created. > > Is there a

[jira] [Created] (IGNITE-13127) Master key change can produce exception in discovery notyfier worker when WAL is disabled.

2020-06-05 Thread Pavel Pereslegin (Jira)
Pavel Pereslegin created IGNITE-13127: - Summary: Master key change can produce exception in discovery notyfier worker when WAL is disabled. Key: IGNITE-13127 URL: https://issues.apache.org/jira/browse/IGNITE-1