[jira] [Created] (IGNITE-8095) Web Console: Refactor components for generated code preview

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8095:


 Summary: Web Console: Refactor components for generated code 
preview
 Key: IGNITE-8095
 URL: https://issues.apache.org/jira/browse/IGNITE-8095
 Project: Ignite
  Issue Type: Task
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Vasiliy Sisko


Refactor to Angular component and remove code duplication.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8094) Web console: investigate/fix broken E2E test for basic editing

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-8094:


 Summary: Web console: investigate/fix broken E2E test for basic 
editing
 Key: IGNITE-8094
 URL: https://issues.apache.org/jira/browse/IGNITE-8094
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Ilya Borisov
Assignee: Ilya Borisov


The "Basic editing" E2E test fails if you use {{save}} page model method 
instead of {{saveWithoutDownload}}. I suspect it might be another case of 
incompatibility between some of directives (it was {{on-focus-out}} before) and 
TestCafe overlays. If fixed, restore {{saveWithoutDownload}} call back to 
{{save}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[CVE-2018-1295]: Possible Execution of Arbitrary Code Within Deserialization Endpoints of Apache Ignite

[Denis Magda]

CVE-2018-1295: Possible Execution of Arbitrary Code Within Deserialization
Endpoints of Apache Ignite

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected: Apache Ignite 2.3 or earlier

Impact:
An attacker can execute arbitrary code on Ignite nodes in the case when
Ignite classpath contains arbitrary vulnerable classes.

Description:
Apache Ignite serialization mechanism does not have a list of classes
allowed for serialization/deserialization, which makes it possible to run
arbitrary code when 3-rd party vulnerable classes are present in Ignite
classpath. The vulnerability can be exploited if the one sends a specially
prepared form of a serialized object to one of the deserialization
endpoints of some Ignite components -   discovery SPI, Ignite persistence,
Memcached endpoint, socket steamer.

Mitigation:
•All Ignite versions: make sure there are no vulnerable classes among
your custom code used in Apache Ignite.
•Ignite 2.3 or earlier users: upgrade to Ignite 2.4 and use
IGNITE_MARSHALLER_WHITELIST and/or IGNITE_MARSHALLER_BLACKLIST system
properties to define classes allowed for deserialization

Credit:
The vulnerability was discovered by Man Yue Mo of lgtm.com.

References:
* http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1295

Re: Shouldn't we merge IEP-7 with IEP-5?

[Vladimir Ozerov]

+1, have never been able to understand what is the difference between them.

On Fri, Mar 30, 2018 at 9:37 PM, Denis Magda  wrote:

> Igniters,
>
> After looking at IEP-7 [1] and IEP-5, I couldn't get the main difference
> between them. My guess that pages have to be merged in one enhancement
> proposals.
>
> Anton V., Alex G., as creators of the pages, what's your opinion on this?
>
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 7%3A+Ignite+internal+problems+detection
> [2]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74683878
>
> --
> Denis
>

[GitHub] ignite pull request #3728: IGNITE-7753: Processors are incorrectly initializ...

[slukyano]

GitHub user slukyano opened a pull request:

https://github.com/apache/ignite/pull/3728

IGNITE-7753: Processors are incorrectly initialized if a node joins d…

…uring cluster activation.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-7753

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3728.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 #3728


commit bb71ad43a62d6f0da29301af3efb9c2f1a2f0d72
Author: Stanislav Lukyanov 
Date:   2018-04-01T18:22:23Z

IGNITE-7753: Processors are incorrectly initialized if a node joins during 
cluster activation.




---

[jira] [Created] (IGNITE-8092) Put operation may hang if cache was destroyed asynchronously.

[Pavel Pereslegin (JIRA)]

Pavel Pereslegin created IGNITE-8092:


 Summary: Put operation may hang if cache was destroyed 
asynchronously.
 Key: IGNITE-8092
 URL: https://issues.apache.org/jira/browse/IGNITE-8092
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.4
Reporter: Pavel Pereslegin


If there is more than one cache in the cache group then put operation on cache 
may hang if it was destroyed asynchronously.
For now this applies to all cache modes (PARTITIONED/REPLICATED/LOCAL) and to 
all atomicity modes (ATOMIC/TRANSACTIONAL).

This problem can not be reproduced if there is only one cache in the cache 
group.

Reproducer:
{code:java}
public class DestroyCacheTest extends GridCommonAbstractTest {

private CacheConfiguration ccfg(String name, String grp) {
return new CacheConfiguration(name).setCacheMode(CacheMode.PARTITIONED)
.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL)

.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
.setGroupName(grp);
}

public void testDestroyAsync() throws Exception {
String grpName = "testGroup";

try (IgniteEx node = startGrid(0)) {
node.createCache(ccfg("cache2", grpName));

for (int n = 0; n < 100; n++) {
IgniteCache cache1 = 
node.createCache(ccfg("cache1", grpName));

AtomicInteger cntr = new AtomicInteger();

GridTestUtils.runMultiThreadedAsync(() -> {
try {
int key;

while ((key = cntr.getAndIncrement()) < 10_000) {
if (key == 1000)
cache1.destroy();

cache1.putIfAbsent(key, true);
}
}
catch (Exception ignore) {
log.warning(ignore.getMessage());
}

return null;
}, 6, "put-thread").get();
}
}
}
}
{code}

p.s. for ATOMIC cache additional cache status check in 
GridCacheGateway#onStopped busy wait resolve this problem.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: IGNITE-6879

[Дмитрий Рябов]

Dmitry, Alexey, code and tests looks good for me.

JIRA: https://issues.apache.org/jira/browse/IGNITE-6879
PR: https://github.com/apache/ignite/pull/3704
Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-541
TeamCity:
https://ci.ignite.apache.org/viewLog.html?buildId=1170373=buildResultsDiv=IgniteTests24Java8_RunAll

2018-03-22 21:48 GMT+03:00 Роман Меерсон :

> Hi all!
>
> Dmitriy thank you for review.
>
> I`ve just fixed all your comments.
>
> чт, 22 мар. 2018 г. в 20:36, Dmitry Pavlov :
>
>> HI Dmitriy, thank you!
>>
>> Roman, could you please address Dmitriy's comments?
>>
>> чт, 22 мар. 2018 г. в 19:18, Дмитрий Рябов :
>>
>>> Hi Dmitriy,
>>>
>>> I took a look for PR, it needs codestyle fixes.
>>>
>>> 2018-03-19 14:22 GMT+03:00 Dmitry Pavlov :
>>>
 Hi Alexey,

 Did you find the patch is looking good and is ready to be merged?

 Sincerely,
 Dmitriy Pavlov

 чт, 15 мар. 2018 г. в 11:19, Alexey Kukushkin <
 kukushkinale...@gmail.com>:

 > Just found the fix is ready - I will review it today or tomorrow.
 >

>>>
>>>