It is reporting of an old failure. It occurs probably because of rebuilding
internal run history in the bot after cache corruption.
Now mentioned test is just rare-flaky, so please ignore.
сб, 26 янв. 2019 г. в 12:03, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled.
Done, I've added permission for Oleg Ignatenko user.
Just in case, let me share
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document with you
:)
пт, 25 янв. 2019 г. в 20:55, oignatenko :
> Hello,
>
> Is it possible to get edit access to Apache Ignite wiki?
>
> I've been working on
Who can advice if mentioned tests change their name from time to time?
The bot will not notify for such tests correctly because it is impossible
to say if a test is the same with some passing test(s).
чт, 24 янв. 2019 г. в 22:17, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to
The test is still flaky and it seems to begin failing recently. Is there
any issue for this test fix?
вт, 22 янв. 2019 г. в 22:49, :
> 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):
It seems to be passing now. Please ignore.
ср, 23 янв. 2019 г. в 00:03, :
> 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
Passing now, please ignore
вт, 22 янв. 2019 г. в 23:33, :
> 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
the FAQ first?
Sincerely,
Dmitriy Pavlov
P.S. here is an article, Apache guides have reference to
http://www.catb.org/~esr/faqs/smart-questions.html - one from required
actions from users is to search for information.
чт, 24 янв. 2019 г. в 01:55, Denis Magda :
> Another data/index corrupt
Count on my support if nobody else would like to help with the merge.
Eventually, I will pick up.
ср, 23 янв. 2019 г. в 19:53, Stanislav Lukyanov :
> Hi Igniters,
>
> Can anyone please review and merge IGNITE-10921?
> Artur Muradimov contributed the change, I did a review myself and now we
>
Hi, it is probably related to
https://issues.apache.org/jira/browse/IGNITE-10822 Test was failing before.
I've muted it.
ср, 23 янв. 2019 г. в 12:33, :
> 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
of size and keySize for cluster cache
metrics.
Roman, Sergey,
Please chime in.
Sincerely,
Dmitriy Pavlov
ср, 23 янв. 2019 г. в 12:13, :
> 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
Dmitriy Pavlov created IGNITE-11049:
---
Summary: [TC Bot] Reset Credentials is broken
Key: IGNITE-11049
URL: https://issues.apache.org/jira/browse/IGNITE-11049
Project: Ignite
Issue Type
Hi,
It seems some PMC already added your account to the list of contributors,
so now you can assign the issue.
Welcome to Apache Ignite community!
Sincerely,
Dmitriy Pavlov
вт, 22 янв. 2019 г. в 23:29, Лев Хенкин :
> Hi, folks. I'm using ignite.net and I want to try to improve it. I th
/CONTRIBUTING.md#contributing-to-apache-ignite
and full guide version
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Should you have any questions please do not hesitate to contact Ignite
developers here.
Sincerely,
Dmitriy Pavlov
вт, 22 янв. 2019 г. в 22:21, Artur Muradimov
Dmitriy Pavlov created IGNITE-11030:
---
Summary: Teamcity Bot cache is in unrecoverable state after bot
restart: need to check reasons
Key: IGNITE-11030
URL: https://issues.apache.org/jira/browse/IGNITE-11030
Dmitriy Pavlov created IGNITE-10989:
---
Summary: [TC Bot] Finalize refactoring and remove REST data
persistent caches
Key: IGNITE-10989
URL: https://issues.apache.org/jira/browse/IGNITE-10989
Project
Hi Konstantin,
Thank you for interest in Apache Ignite and welcome to the Apache Ignite
Community.
I've added you to the list of contributors, so now you can assign an issue
to yourself.
Should you have any questions please do not hesitate to contact Ignite
developers here.
Sincerely,
Dmitriy
Dmitriy Pavlov created IGNITE-10978:
---
Summary: Remove unused tests marked with unclear todo
Key: IGNITE-10978
URL: https://issues.apache.org/jira/browse/IGNITE-10978
Project: Ignite
Issue
Hi Igor,
Welcome to the Apache Ignite Community.
I've added you to the list of contributors, so now you can assign an issue
to yourself.
Should you have any questions please do not hesitate to contact Ignite
developers here.
Sincerely,
Dmitriy Pavlov
P.S. Let me share with you
Short 'How
Dmitriy Pavlov created IGNITE-10942:
---
Summary: [TC Bot] Optimize backround JIRA tickets sync
Key: IGNITE-10942
URL: https://issues.apache.org/jira/browse/IGNITE-10942
Project: Ignite
Issue
Hi Turik,
2.8 is not released, and dates were not discussed yet. So it is hard to say
when a doc package will be available.
Sincerely,
Dmitriy Pavlov
пн, 14 янв. 2019 г. в 14:18, techbysample :
> Igniters,
>
> Would you please advise on when 2.8 documentation will be available?
&
Dmitriy Pavlov created IGNITE-10930:
---
Summary: [TC Bot] Support PR-less contributions
Key: IGNITE-10930
URL: https://issues.apache.org/jira/browse/IGNITE-10930
Project: Ignite
Issue Type
Hi Andrey,
Welcome to Apache Ignite Community.
I've added you to the list of contributors, so now you can assign issues to
yourself.
Sincerely,
Dmitriy Pavlov
P.S. Let me share with you
Short 'How to start' guide
https://github.com/apache/ignite/blob/master/CONTRIBUTING.md#contributing
related to their previous contributions. A user who
reports a new issue using JIRA usually has absolutely no clue who can now
help with resolving. So this forwarding should help us to figure out any
new problems should be addressed.
Sincerely,
Dmitriy Pavlov
пт, 11 янв. 2019 г. в 12:47, oignatenko
the project. It's just wrong to force to subscribe to 2 lists, people
> won't do this, we're lazy by nature. Just use email filters, that's XXI
> century but please don't separate discussions from issues reporting.
>
> --
> Denis
>
>
> On Thu, Jan 10, 2019 at 3:55 A
est-agents are configured to use JDK 9/10/11, isn't it?
>
> On Thu, Jan 10, 2019 at 2:59 PM Dmitriy Pavlov wrote:
> >
> > I feel the first step there should be to switch our tests running on TC
> to
> > java > 8.
> >
> > After some time having newer java as defa
I feel the first step there should be to switch our tests running on TC to
java > 8.
After some time having newer java as default we can change suggestions for
users.
чт, 10 янв. 2019 г. в 14:08, Vyacheslav Daradur :
> Igniters,
>
> As you know, Ignite logs configuration tuning suggestions at
to a separate list. Please
share your vision on this topic. Should it be j...@ignite.apache.org or we
should reuse notificati...@ignite.apache.org
Sincerely,
Dmitriy Pavlov
ср, 21 нояб. 2018 г. в 15:25, Dmitriy Pavlov :
> Please start a vote according to
> https://www.apache.org/foundation/votin
In the TC Bot, I used to create the second cache with CacheV2 name and
migrate needed data from Cache V1 to V2.
After CacheV1 destroy(), files are removed and disk space is freed.
ср, 9 янв. 2019 г. в 12:04, Павлухин Иван :
> Vyacheslav,
>
> Have you investigated how other vendors (Oracle,
ix this?
>
> https://issues.apache.org/jira/browse/IGNITE-10863
>
> On Sun, Dec 30, 2018 at 1:28 AM Dmitriy Pavlov wrote:
>
>> Hi Igniters,
>>
>> Thanks to Peter and Alexey for sharing their opinion.
>>
>> I've filed https://issues.apache.org/jira/br
Hi Igniters,
Please find a free minute and fill survey:
https://s.apache.org/oxTr DEADLINE: 15 February 2019
Sincerely,
Dmitriy Pavlov
-- Forwarded message -
From: Sally Khudairi
Date: ср, 9 янв. 2019 г. в 09:13
Subject: Fwd: The ASF needs your help! "The Apache Way
Hi Saikat,
Fix itself is ok. But from the top of my head, I don't know how can we
auto-test this scenario in the future. Do you have an idea?
Sincerely,
Dmitriy Pavlov
ср, 9 янв. 2019 г. в 07:08, Saikat Maitra :
> Hi,
>
> I have raised a PR for the below issue.
>
> IGNITE-10856
/browse/IGNITE-7153
Sincerely,
Dmitriy Pavlov
пт, 2 нояб. 2018 г. в 13:20, Michael Fong :
> Hi Yakov,
>
> Thanks so much for your analysis.
>
> Parser expects chunks to be complete and has all the data to read entire
> > message, but this is not guaranteed and sing
requests from GitHub Web UI and commit files
directly to master branch via GitHub. You can run this setup here
https://gitbox.apache.org/setup/
Sincerely,
Dmitriy Pavlov
can for now simply delete empty
https://git-wip-us.apache.org/repos/asf?p=ignite-doc.git
Sincerely,
Dmitriy Pavlov
вс, 30 дек. 2018 г. в 01:28, Dmitriy Pavlov :
> Hi Igniters,
>
> Thanks to Peter and Alexey for sharing their opinion.
>
> I've filed https://issues.apache.org/jira/bro
Nikolay, thank you for fixing
чт, 27 дек. 2018 г. в 23:00, Dmitriy Pavlov :
> Thanks to Michail Petrov we have now TC Bot notifications on compilation
> failures.
>
>
> чт, 27 дек. 2018 г. в 22:07, :
>
>> Hi Igniters,
>>
>> I've detected some new issue on
Thanks to Michail Petrov we have now TC Bot notifications on compilation
failures.
чт, 27 дек. 2018 г. в 22:07, :
> 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
Dmitriy Pavlov created IGNITE-10832:
---
Summary: [TC Bot] Auto-trigger check win agents availability
before triggering a build
Key: IGNITE-10832
URL: https://issues.apache.org/jira/browse/IGNITE-10832
+1 from my side. I think it is reasonable
ср, 26 дек. 2018 г. в 19:20, Ilya Kasnacheev :
> Hello!
>
> It was recently discovered that there's some issue in H2 which leads to
> differing string encodings when they come into reducer from nodes with
> different system encoding. Even if we were able
Hi All,
Please check the commit
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=3b9c415ee2c4b6461c18f87f46f1950f324f5662
Thanks to everyone involved.
Sincerely,
Dmitriy Pavlov
вт, 25 дек. 2018 г. в 19:38, Dmitriy Pavlov :
> Hi Saikat,
>
> I'm going to slightly change
n't mind. This option allows us both to stop and does not
spin in the while.
Sincerely,
Dmitriy Pavlov
сб, 13 окт. 2018 г. в 20:37, Saikat Maitra :
> Hi Alex ,
>
> Can you please review and let me know if the PR looks good to merge.
>
> I have completed the requested changes.
>
Dmitriy Pavlov created IGNITE-10787:
---
Summary: [TC Bot] Setup TC bot profiling on the server using
SJK/stcap and prepare rules for Ignite thread groups
Key: IGNITE-10787
URL: https://issues.apache.org/jira
Hi,
Sorry for being too formal here, but IGNITE-10003
<https://issues.apache.org/jira/browse/IGNITE-10003> is in progress.
Also, I've tried to find anything related to it in the list. So according
to the list, no one was asking to include.
Sincerely,
Dmitriy Pavlov
ср, 19 дек. 2018 г. в
, which
is visible in TC.
Sincerely,
Dmitriy Pavlov
ср, 19 дек. 2018 г. в 11:59, Павлухин Иван :
> Hi Oleg,
>
> I have not quite understood who is going to call (from standpoint of
> test framework) beforeTestsStarted, beforeTest, afterTest,
> afterTestsStarted methods?
> вт, 18
Both patches were applied. Maxim, thank you!
What about 1. An `Unexpected error during build messages processing in
TeamCity`, what can we do as the next step to fix it?
Sincerely,
Dmitriy Pavlov
пн, 17 дек. 2018 г. в 18:31, Andrey Mashenkov :
> Maxim,
>
> Looks ok. Let's apply IGN
Hi Andrey,
I've updated permissions, please check.
Sincerely,
Dmitriy Pavlov
вт, 18 дек. 2018 г. в 12:34, Andrey Kuznetsov :
> Hi, Igniters.
>
> I'd like to add new wiki page with suggestions for future Ignite 3.0
> release. We can collect any ideas there and then discuss and
. If you feel your patch is
ready, please set ticket status.
Sincerely,
Dmitriy Pavlov
ср, 31 окт. 2018 г. в 06:04, Michael Fong :
> Absolutely, I am glad to see this problem solved regardless whom the
> assignee is. After all, we are suffering this Redis problem in our Ignite
> Po
1, Anton Vinogradov :
> > >
> > > Great feature!
> > >
> > > Could you please explain how to have a deal with it?
> > > How should I mite/unmute tests for now?
> > >
> > > On Fri, Dec 14, 2018 at 6:50 PM Dmitriy Pavlov
> > wrote:
/dspavlov/ignite-abbrev-plugin/commit/4b30c1a2cff4ee4a615bc0940327035705198cbc
Later we can start to create changes if other community members agree to
place their work in the ASF repo.
Sincerely,
Dmitriy Pavlov
чт, 19 июл. 2018 г. в 14:04, Dmitry Pavlov :
> Hi Vyacheslav,
>
> For Abbr
Hi Ivan,
I've merged your PR and added permissions to the wiki, please check.
I still feel we need to migrate code to ASF repo. I will try to do
something for that.
Sincerely,
Dmitriy Pavlov
пн, 17 дек. 2018 г. в 13:44, Павлухин Иван :
> Hi,
>
> I did some investigation regard
I see the same, browsers checked: Edge & Chrome. I guess it is not a layout
is broken, but a style missing.
Unfortunately, I don't know how to fix. Probably we should start research
from ignite/pom.xml:191
${basedir}/assembly/docfiles/javadoc.css
пн, 17 дек. 2018 г. в 14:32, Павлухин Иван :
>
gt; It looks like we can't make logs more verbose due to possible bug,
> >> I've create a ticket in Jetbrains Jira [1].
> >> >> > We can just publish idea logs in artefacts as suggested in this
> >> manual [2].
> >> >> >
ersion in a similar way - most
> important stuff first, old is either removed and reworked.
>
> --
> Denis
>
> On Fri, Dec 14, 2018 at 2:43 AM Dmitriy Pavlov wrote:
>
> > Thank you for sharing your vision, I also agree to have short in GH and
> > full in the wiki.
>
Looks cool, I will try
пт, 14 дек. 2018 г. в 16:46, Павлухин Иван :
> Hi Igniters,
>
> I would like to share with you that now it is possible to use IDEA
> async debugger for debugging Ignite futures. And we should thank Ivan
> Bessonov for that awesome contribution [1].
>
> Most of your might
struction to ignore test:
> Assume.assumeTrue("link-to-issue", false);
>
> On Fri, Dec 14, 2018 at 5:44 PM Dmitriy Pavlov wrote:
> >
> > Thank you, Dmitrii,
> >
> > I've started unmuting tests starting from yesterday.
> >
> > Now muted test count wa
-unmute, but hopefully,
JUnit4 & @Ignore opportunity will come earlier.
Sincerely,
Dmitriy Pavlov
пт, 14 дек. 2018 г. в 17:24, Dmitrii Ryabov :
> Hello, Igniters!
>
> Our Bot got new functionality - it shows tests muted on TeamCity and their
> ticket status [1].
>
> So, we c
Thank you for sharing your vision, I also agree to have short in GH and
full in the wiki.
Denis, I see a number of outdated info in How To Contribute, but most
sections there are for a strong reason. A lot of cases covered, and a lot
of cases could be covered in addition to existing.
Dmitriy Pavlov created IGNITE-10677:
---
Summary: [TC Bot] Include build failure on metric & exit code into
critical failures
Key: IGNITE-10677
URL: https://issues.apache.org/jira/browse/IGNITE-1
Folks, I sometimes hear complains related to metrics and its clearness for
end-users.
Would you add a couple of words related to each value to wiki/readme.io?
чт, 13 дек. 2018 г. в 17:13, Alexey Zinoviev :
> So, I agree that we should avoid ineffective metrics calculations.
> I think that in
The failure occurred a long time ago, it is outside of TC history now. The
test is still flaky.
чт, 13 дек. 2018 г. в 07:56, :
> 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
Mentioned failure is not recent, but occurred in the past. Hopefully, new
services implementation will fix the test.
чт, 13 дек. 2018 г. в 04:11, :
> 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
https://issues.apache.org/jira/browse/IGNITE-10245
ср, 12 дек. 2018 г. в 17:11, :
> 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
Impl.java:462)
> > at
> com.intellij.openapi.application.impl.ApplicationImpl.createComponents(ApplicationImpl.java:466)
> > at
> com.intellij.openapi.components.impl.ComponentManagerImpl.init(ComponentManagerImpl.java:102)
> > at
> com.intellij.openapi.application.impl.ApplicationImpl.load(ApplicationImpl.java:421)
&g
This failure bot complains was occurred in November. It is not a recent
failure. But the test is still flaky.
ср, 12 дек. 2018 г. в 03:26, :
> 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
Flaky timeout. Probably already fixed
пн, 10 дек. 2018 г. в 04:47, :
> 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
TC Bot detected some stable failure in the past. The mentioned build is
outside of TC storage now. Failure history in the latest Bot release is
longer, so this is not a recent failure. But anyway, the test needs to be
fixed as it is flaky.
ср, 12 дек. 2018 г. в 00:11, :
> Hi Igniters,
>
>
It is really recently broken test:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7945125576049372508=%3Cdefault%3E=testDetails
Now it fails stable.
Igor S, Vladimir O. please chime in.
вт, 11 дек. 2018 г. в 09:17, :
> Hi Igniters,
>
> I've detected some new issue on
Hi All, the Bot detected some stable failure in the past because failure
history in the latest Bot release is longer, so this is not a recent
failure.
But anyway both tests need to be fixed as they are flaky.
вт, 11 дек. 2018 г. в 23:34, :
> Hi Igniters,
>
> I've detected some new issue on
ried to investigate the issue related to Inspection TC
> task
> > > execution time variation (from 0.5 up to 1,5 hours)?
> > > Can we enable GC logs for this task or may be even get CPU, Disk,
> Network
> > > metrics?
> > > Can someone check if there are
t;
> > On 12 Dec 2018, at 20:21, Dmitriy Pavlov wrote:
> >
> > Hi Igniters,
> >
> > Just to inform, the very first version of the Contribution step by step
> > guide was added to GitHub. It is one more entry point for newcomers to
> find
> > out what and
;
> On Wed, Dec 12, 2018 at 9:21 AM Dmitriy Pavlov wrote:
>
> > Hi Igniters,
> >
> > Just to inform, the very first version of the Contribution step by step
> > guide was added to GitHub. It is one more entry point for newcomers to
> find
> > out what and how s
hange
> the git remote entry. Petr, Sergey, can you asses what changes are need to
> be done in order to support this migration for TC and release procedure?
>
> вт, 11 дек. 2018 г. в 19:20, Dmitriy Pavlov :
>
> > Hi All,
> >
> > The Apache Ignite still has a re
-ignite
Feel free to share with newcomers and contribute.
Sincerely,
Dmitriy Pavlov
Hi Yuri,
Would it affect users?
Ignite-code has separation of API classes (not internal) and internal
stuff. Internal classes may be changed from version to version, but API
can't be renamed/moved/and so on. What about ML?
Sincerely,
Dmitriy Pavlov
вт, 11 дек. 2018 г. в 16:56, Yuriy Babak
This notification probably came from some old TC Bot DB records, while the
test is flaky - it is not a mistake.
Now server uses time-based statistics, so bot keeps data for a longer time.
вт, 11 дек. 2018 г. в 20:11, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled.
support for the decision from a mailing list post, so
here it is.
Sincerely,
Dmitriy Pavlov
сб, 8 дек. 2018 г. в 00:16, Dmitriy Pavlov :
> Hi Igniters,
>
> What do you think about the voluntary migration of project repositories
> from git-wip to GitBox? (See details in the for
ages from the archive of the
> developers list
> to the newly-created one?
>
> Denis
>
> вт, 11 дек. 2018 г. в 10:05, Dmitriy Pavlov :
>
> > Hi Igniters,
> >
> > Infra changed notifications, so now GitHub emails are being sent to
> > notifications@
> >
Dmitriy Pavlov created IGNITE-10639:
---
Summary: Proof of concept for internal description for packages
Key: IGNITE-10639
URL: https://issues.apache.org/jira/browse/IGNITE-10639
Project: Ignite
; > big project open PR list can reflect very well the real work in
> > > progress. For bigger projects things become more complicated.
> > >
> > > Dmitriy,
> > >
> > > Do you have some cleanup automation in mind? Immediately I think that
> > > it
Hi Igniters,
Infra changed notifications, so now GitHub emails are being sent to
notifications@
Web UI: https://lists.apache.org/list.html?notificati...@ignite.apache.org
You may subscribe to the list notifications-subscr...@ignite.apache.org
Sincerely,
Dmitriy Pavlov
ср, 5 дек. 2018 г. в 12
. There can be
- an enthusiast who didn't provide correctly set up ticket
- But prepared just PR with a good addition to the product.
It is not so correct to accept such contribution (HTC requires JIRA), but
anyway, having PR open we can ask him or her to set up a ticket.
Sincerely,
Dmitriy Pavlov
Vladimir, AFAIK there will be no single change for overall migration. All
migration will be in a step-by-step manner and mostly transparent for
contributors.
Both approaches 3&4 will be available for some time.
First of all, we need an opportunity to run existing integration tests in
JUnit4.
from closed PR?
>
> > The same proposal is related to IEP statuses. If you were involved in an
> IEP, please validate its status
>
> +1. We should maintain IEP description up to date.
>
> пн, 10 дек. 2018 г., 19:15 Dmitriy Pavlov dpav...@apache.org:
>
> > Hi Ignite
/IGNITE/Active+Proposals Please
set a correct state for your IEP, as well.
Should you have any questions, please don't hesitate to ask here. Thank you
in advance!
Sincerely,
Dmitriy Pavlov
Reverted.
https://issues.apache.org/jira/browse/IGNITE-8227 reopened
пн, 10 дек. 2018 г. в 16:23, Dmitriy Pavlov :
> Anton, I was expecting that you revert, because you wanted to do it.
>
> Provided that I agree that fix could be reverted because of both
> functional and st
, Anton Vinogradov :
> Dmitriy,
>
> You confirmed that fix should be reverted and reworked last Friday.
> Why it still not reverted?
>
> On Mon, Dec 10, 2018 at 12:46 AM Dmitrii Ryabov
> wrote:
>
> > Agree, it is reasonable to revert.
> > пт, 7 дек. 2018 г. в 18:44,
Dmitriy Pavlov created IGNITE-10620:
---
Summary: [TC Bot] Implement Tracked Branches processor and
IssueDetector unit tests
Key: IGNITE-10620
URL: https://issues.apache.org/jira/browse/IGNITE-10620
@
.
It is up to us to decide if we would like to migrate sooner. Later all
repositories will be migrated anyway.
Affected repositories
- Ignite Release
- Ignite
Please share your opinion.
Sincerely,
Dmitriy Pavlov
-- Forwarded message -
From: Daniel Gruno
Date: пт, 7 дек. 2018
It seems we really need a reviewer field in JIRA. The previous discussion
was completed with consensus, and now I should create a ticket to INFRA.
пт, 7 дек. 2018 г. в 21:54, Alexey Zinoviev :
> Dear Igniters, please have a look and summarise your thougths about that PR
> here, in developer
into GridAbstractTest and
correctly failing test.
Sincerely,
Dmitriy Pavlov
пт, 7 дек. 2018 г. в 18:38, Ilya Lantukh :
> Unfortunately, this FailureHandler doesn't seem to work. I wrote a test
> that reproduces a bug and should fail. It prints the following text into
> log, but the t
to your contributions.
Sincerely,
Dmitriy Pavlov
P.S. Additional references that should boost your onboarding.
Please subscribe to both dev@ and user@ lists, optionally you may subscribe
to notifications@:
https://ignite.apache.org/community/resources.html#mail-lists
Get familiar with Apache Ignite
I've checked this patch and it looks good to me, it is really simple.
But probably we should consider auto-test it somehow. Nikolay Kulagin,
could you chime in?
Stephen, could it be a workaround for end-user code? I guess user can just
add this dependency in the pom and everything will work
to Apache Ignite 2.7 or later version
Credit:
Segu Riluvan discovered the usage of vulnerable modules in dependencies of
Apache Ignite.
Thanks for everyone who was involved into dependencies migration.
Best Regards,
Dmitriy Pavlov on behalf of Apache Ignite community
to your contributions.
Sincerely,
Dmitriy Pavlov
P.S. Additional references that should boost your onboarding.
Please subscribe to both dev@ and user@ lists, optionally you may subscribe
to notifications@:
https://ignite.apache.org/community/resources.html#mail-lists
Get familiar with Apache Ignite
s for each problem) before Friday evening,
> the code will be rolled back.
> Simple no-op is better that same but overcomplicated.
>
> On Thu, Dec 6, 2018 at 2:14 PM Dmitrii Ryabov
> wrote:
>
> > Anton, I mean `copy-paste reduce` ticket. I'll try to describe reasons
> for
> >
d. Please, tell me mail of this channel.
>
> чт, 6 дек. 2018 г., 14:13 Dmitriy Pavlov dpav...@apache.org:
>
> > Nikolay, thank you for your efforts!
> >
> > Should we announce a release in a special Apache-wide channel?
> >
> > чт, 6 дек. 2018 г. в 10:3
Nikolay, thank you for your efforts!
Should we announce a release in a special Apache-wide channel?
чт, 6 дек. 2018 г. в 10:36, Nikolay Izhikov :
> The Apache Ignite Community is pleased to announce the release of
> Apache Ignite 2.7.0.
>
> Apache Ignite [1] is a memory-centric distributed
to set of NoOp handlers test can be
hidden and the test will pass for whatever reason, e.g. poor validation of
expected behavior. So suggested analog to this is muted failures, which
runs on TC but don't signal us that something is wrong.
Sincerely,
Dmitriy Pavlov
чт, 6 дек. 2018 г. в 13:53
ot;cheap". And I meant that it is good
> that
> > > > > it cheap =). And I said it to contrast with "expensive" ~100 tests
> > > > > investigation. And if we agree (mostly I would like an opinion from
> > > > > Dmitriy Ryabov as an original autho
49900
> > >
> > > tests, and we’re still concerned about style or minor details if no-op
> was
> > > copy-pasted, aren’t we?
> > >
> > > Can you explain this idea a bit more?
> > > I don't understand what is unmuted by discussed comm
Dmitriy Pavlov created IGNITE-10562:
---
Summary: [TC Bot] DB contains invalid values for build references
ID maps to value with other ID
Key: IGNITE-10562
URL: https://issues.apache.org/jira/browse/IGNITE-10562
501 - 600 of 1052 matches
Mail list logo
