Alexey Kuznetsov created IGNITE-8891:
Summary: Web Console: Replace IGNITE_MODULES with node_modules
Key: IGNITE-8891
URL: https://issues.apache.org/jira/browse/IGNITE-8891
Project: Ignite
Yes, you are right.
Thanks,
Amir
On Wed, Jun 27, 2018 at 1:15 PM Denis Magda wrote:
> Got you. If it's about redundant data duplication in onheap region then no
> any concerns from my side.
>
> Anyway, considering that the data structure will be interacting with the
> page memory directly then
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4260
---
Cross-posting to developers list.
Guys, cache locks work inconsistently: if you take a lock twice, but
release it only once, then *IgniteCache#isLocalLocked* will tell you, that
you hold a lock, but another node will be able to acquire it.
We should either make the lock non-reentrant, or not relea
Got you. If it's about redundant data duplication in onheap region then no
any concerns from my side.
Anyway, considering that the data structure will be interacting with the
page memory directly then its entries can be stored in Ignite persistence
automatically (if the latter is on). Does it mean
Anton,
It's easy to maintain committers/PMC list for now. I would leave it as is.
The changes rarely happen there. But I do agree that it's hard to track
changes related to the contributor's list. Makes sense to provide a link to
that GitHub page instead.
Prachi, could you please prepare a versio
Some OOMEs seems like infrastructure problem, one of them has failed due to 4Gb
limit to artifact size.
I think we should reconsider log and work artifacts collection after build and
try to shrink working logs even more.
Dmitriy, can you aggregate such problems at least for one week and create
Hi,
I think we have to check if all PDS tests has limited region sizes and
checkpoint buffer sizes.
Also, seems, there is a leakage when using scan query. I'll file a ticket
with details tomorrow.
ср, 27 июн. 2018 г., 18:55 Dmitry Pavlov :
> Hi Igniters,
>
> I've noticed in latest run we have ~
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4269
Revert "IGNITE-8749 Exception for "no space left" situation should beâ¦
⦠propagated to FailureHandler - Fixes #4200."
This reverts commit 3fff8a8
Signed-off-by: EdShangGG
Y
Nikolay, thank you for such fast reaction. Tests are passing now.
ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov :
> Hello, Dmitriy.
>
> I fixed this issue, already.
> Please, check it.
>
> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> > Hi Denis,
> >
> > currently anyway we have TC issue
Hi Igniters,
I've noticed in latest run we have ~ 985 test failures and 3 suites with
OOME in master.
Who knows if it is temporary or infra problem or we have some bug in code?
Could you please share ticket numbers?
https://ci.ignite.apache.org/viewLog.html?buildId=1429088
https://ci.ignite.apac
Hi.
> can we add option enables AES 128
Currently, 128 bit key used [1]
> I guess we should update environment to meet test requirements prior putting
> changes to master.
Yes.
[1]
https://github.com/apache/ignite/pull/4167/files#diff-1088ffe504f1aa300830e1ae9c030de1R80
В Ср, 27/06/2018 в
Hi Nikolay,
can we add option enables AES 128 for test mode? This should work well
without update env.
Sincerely,
ср, 27 июн. 2018 г. в 18:43, Petr Ivanov :
>
>
> > On 27 Jun 2018, at 18:06, Nikolay Izhikov wrote:
> >
> > Hello, Eduard.
> >
> >> We should make suites which are restricted by a
> On 27 Jun 2018, at 18:06, Nikolay Izhikov wrote:
>
> Hello, Eduard.
>
>> We should make suites which are restricted by agents to make as small as>
>> possible.
>
> Agree. That means we should enable java cryptography on all agents. Isn't it?
>
>> So, I strictly against adding such test (
Nikolay,
I am against new "agent restrictions", not tests.
But Petr says that this is OK (new restrictions) because these
configurations finish in 5 minutes.
On Wed, Jun 27, 2018 at 6:06 PM, Nikolay Izhikov
wrote:
> Hello, Eduard.
>
> > We should make suites which are restricted by agents to
Sure,
Hope it will be tomorrow
ср, 27 июн. 2018 г. в 18:11, Amir Akhmedov :
> Anton V,
> I put some comments into jira ticket. Can you please take a look once you
> have a chance?
>
> Thanks,
> Amir
>
> On Mon, Jun 18, 2018, 7:54 AM Anton Vinogradov wrote:
>
> > Amir,
> >
> > Everything is fine,
GitHub user 1vanan opened a pull request:
https://github.com/apache/ignite/pull/4268
IGNITE-8619 Failing testClientAtomicLongCreateCloseFailover
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1vanan/ignite IGNITE-8619
Alternati
Anton V,
I put some comments into jira ticket. Can you please take a look once you
have a chance?
Thanks,
Amir
On Mon, Jun 18, 2018, 7:54 AM Anton Vinogradov wrote:
> Amir,
>
> Everything is fine, I'll check changes this week.
>
> вс, 17 июн. 2018 г. в 6:09, Amir Akhmedov :
>
> > Anton,
> > I c
Hello, Eduard.
> We should make suites which are restricted by agents to make as small as>
> possible.
Agree. That means we should enable java cryptography on all agents. Isn't it?
> So, I strictly against adding such test (therefore restriction) to these>
> suites.>
What is wrong with tests
Hello, Dmitriy.
I fixed this issue, already.
Please, check it.
В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> Hi Denis,
>
> currently anyway we have TC issue came from spark version migrations.
>
> I also currently experiencing challenges with my local environment setup.
> So I guess we
Hi Denis,
currently anyway we have TC issue came from spark version migrations.
I also currently experiencing challenges with my local environment setup.
So I guess we have day or two to wait this fix.
Sincerely.
Dmitriy Pavlov
ср, 27 июн. 2018 г. в 16:05, Denis Magda :
> May I ask when? The c
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4267
---
Puviarasu created IGNITE-8890:
-
Summary: Ignite YARN Kerberos - Delegation Token renewal
Key: IGNITE-8890
URL: https://issues.apache.org/jira/browse/IGNITE-8890
Project: Ignite
Issue Type: Bug
May I ask when? The current status of the ticket is not clear.
--
Denis
On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey)
wrote:
> Yes, it will be in the release 2.6
>
> > 27 июня 2018 г., в 14:15, Dmitry Pavlov
> написал(а):
> >
> > Hi Igniters,
> >
> > I've returned https://issues.apache.org/j
Nikolay Izhikov created IGNITE-8889:
---
Summary: Spark examples doesn't work
Key: IGNITE-8889
URL: https://issues.apache.org/jira/browse/IGNITE-8889
Project: Ignite
Issue Type: Bug
Affect
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/4267
IGNITE-8889: Remove scala-2.10 profile from examples.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-8889
Alternative
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4266
IGNITE-8885 Failing test method explicitly.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ignite-8885
Alter
Dmitry,
I mean Chugunov, but I have questioned him. His answer was the A. Goncharuk
should now the answer.
On Wed, Jun 27, 2018 at 2:58 PM, Dmitry Pavlov
wrote:
> John, is this question still actual?
>
> пт, 22 июн. 2018 г. в 15:18, Dmitry Pavlov :
>
> > Hi Ed,
> >
> > Which Sergey do you mean?
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4237
---
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4265
IGNITE-8887 Failing test method explicitly.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ignite-8887
Alter
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4264
IGNITE-8791 Test experiments.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8791
Alternatively you can review a
John, is this question still actual?
пт, 22 июн. 2018 г. в 15:18, Dmitry Pavlov :
> Hi Ed,
>
> Which Sergey do you mean? I know a number of contributors.
>
> Sincerely,
>
>
> вт, 19 июн. 2018 г. в 22:15, Eduard Shangareev <
> eduard.shangar...@gmail.com>:
>
>> Hi,
>>
>> 1. It looks weird, yeah. N
Yes, it will be in the release 2.6
> 27 июня 2018 г., в 14:15, Dmitry Pavlov написал(а):
>
> Hi Igniters,
>
> I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
> scope because it was initially discussed to be in this reselase.
>
> Alexey Stelmak, could you please confirm f
Nikolay, Petr,
We should make suites which are restricted by agents to make as small as
possible.
So, I strictly against adding such test (therefore restriction) to these
suites.
On Wed, Jun 27, 2018 at 11:39 AM, Petr Ivanov wrote:
> IgniteSpiTestSuite is called from ’SPI’ build type and I’ve
Hi Igniters,
I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
scope because it was initially discussed to be in this reselase.
Alexey Stelmak, could you please confirm fix could be ready soon?
Also I've cherry-picked javadoc fix.
Sincerely,
Dmitriy Pavlov
вт, 26 июн. 201
Andrey Aleksandrov created IGNITE-:
--
Summary: Possible data loss durring restaring of the nodes with
empty pds
Key: IGNITE-
URL: https://issues.apache.org/jira/browse/IGNITE-
Project:
>> I see that I was added to the Commiters table, but I'm not commiter, just
>> contributor :)
One more reason to prodive commiters/PMC list using generated url [1]
[1] http://people.apache.org/phonebook.html?pmc=ignite
ср, 27 июн. 2018 г. в 12:07, Pavel Kovalenko :
> I see that I was added to t
I see that I was added to the Commiters table, but I'm not commiter, just
contributor :)
ср, 27 июн. 2018 г. в 12:02, Anton Vinogradov :
> Denis,
>
> I'm bad at html :)
> But my idea is to, at least, have such url [1] published at contributors
> page.
> In case we have non-code contributors, we c
Denis,
I'm bad at html :)
But my idea is to, at least, have such url [1] published at contributors
page.
In case we have non-code contributors, we can mention them at special
table, but code contributors can be mentioned just by this url.
[1] https://github.com/apache/ignite/graphs/contributors
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/4263
Ignite 1.7.21
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.21
Alternatively you can review and apply t
Andrey Kuznetsov created IGNITE-8887:
Summary:
IgfsLocalSecondaryFileSystemDualAsyncSelfTest.testAccessAndModificationTimeUpwardsPropagation
fails flakily on master
Key: IGNITE-8887
URL: https://issues.apache
I think a proper fix would be to reuse the logic of automatic baseline
change that is planned to be implemented and automatically activate the
cluster after a certain timeout is reached.
Note that immediate cluster activation on first node start won't work
because under concurrent nodes start and
IgniteSpiTestSuite is called from ’SPI’ build type and I’ve added agent filter
there.
IgniteKernalSelfTestSuite is not found in build types.
> On 27 Jun 2018, at 11:26, Nikolay Izhikov wrote:
>
> Well, it's a good question :)
>
> I've added encryption tests in `IgniteKernalSelfTestSuite` and
Roman Guseinov created IGNITE-8886:
--
Summary: Simultaneous using of BinaryWriter и BinaryRawWriter
leads to BinaryObjectException and OOM
Key: IGNITE-8886
URL: https://issues.apache.org/jira/browse/IGNITE-8886
Well, it's a good question :)
I've added encryption tests in `IgniteKernalSelfTestSuite` and in
`IgniteSpiTestSuite`.
Not sure, what builds on Team City runs these suites.
В Ср, 27/06/2018 в 11:18 +0300, Petr Ivanov пишет:
> Nikolay,
>
>
> What is “core” module?
>
>
> > On 27 Jun 2018, at 00
Andrey Kuznetsov created IGNITE-8885:
Summary:
GridCacheDhtPreloadMultiThreadedSelfTest.testConcurrentNodesStartStop fails
flakily
Key: IGNITE-8885
URL: https://issues.apache.org/jira/browse/IGNITE-8885
Nikolay,
What is “core” module?
> On 27 Jun 2018, at 00:42, Nikolay Izhikov wrote:
>
> Hello, Petr.
>
> Thanks a lot!
> I see success spring encryption tests now [1]
>
> I've added encryption tests to core module also.
> Can we set same rule for a core module?
>
> [1]
> https://ci.ignite.
Roman Guseinov created IGNITE-8884:
--
Summary: .NET: CachePartialUpdateException: failed to update keys
(using Cache.PutAsync)
Key: IGNITE-8884
URL: https://issues.apache.org/jira/browse/IGNITE-8884
P
48 matches
Mail list logo
