Re: [DISCUSS] Links to commercial version resources in community wiki
https://issues.apache.org/jira/browse/IGNITE-12422 пт, 6 дек. 2019 г. в 10:27, Alexei Scherbakov : > Maxim, > > Yes, I think I could help. > > чт, 5 дек. 2019 г. в 19:52, Maxim Muzafarov : > >> Alexey, >> >> Thank you so much! Can you help with the other issues? >> It would be great to clean up them and enable checkstyle pattern for >> such TODOs [1]. >> >> Here is the full list of issues: >> >> GG-1075 >> GG-1314 >> GG-2311 >> GG-2329 >> GG-2852 >> GG-3946 >> GG-3997 >> GG-4368 >> GG-4440 >> GG-4911 >> GG-6460 >> GG-6879 >> GG-8123 >> GG-8768 >> GG-8884 >> GG-9141 >> GG-10884 >> GG-11141 >> GG-11148 >> GG-11220 >> GG-11241 >> GG-11480 >> GG-11640 >> GG-11768 >> GG-12292 >> GG-13223 >> GG-17396 >> >> >> [1] https://checkstyle.sourceforge.io/config_misc.html#TodoComment >> >> On Thu, 5 Dec 2019 at 19:18, Alexei Scherbakov >> wrote: >> > >> > This is a contribution artifact and was not done intentionally. >> > I'll remove it in subsequent contributions. >> > >> > ср, 4 дек. 2019 г. в 16:57, Dmitriy Pavlov : >> > >> > > I agree that 'TODO: please, fix me GG-X' Should be definitely >> avoided >> > > in the code in all cases. A number of community members don't have >> access >> > > to these tickets. >> > > >> > > This is the same as linking to GG's private documentation or internal >> > > network servers. It doesn't make sense. >> > > >> > > ср, 4 дек. 2019 г. в 14:53, Ivan Pavlukhin : >> > > >> > > > Maxim, >> > > > >> > > > References to GG tickets have definitely no meaning for community. >> But >> > > > references to documentation on the other hand can be very useful, >> > > > actually it is very similar to references to Wikipedia or >> > > > aforementioned Oracle resources. >> > > > >> > > > ср, 4 дек. 2019 г. в 14:40, Maxim Muzafarov : >> > > > > >> > > > > Folks, >> > > > > >> > > > > In general case, 3rd party resource links look for me absolutely >> > > > > normal e.g. we could have some links on Oracle's documentation >> pages. >> > > > > >> > > > > But let's add a little accuracy. We are talking about links to >> > > > > GridGain documentation pages. For me, it's the same as comments >> `TODO: >> > > > > please, fix me GG-X` in the source code (e.g. like this one >> [1]). >> > > > > Looks a bit strange :-) >> > > > > >> > > > > >> > > > > [1] >> > > > >> > > >> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/PartitionUpdateCounter.java#L43 >> > > > > >> > > > > On Tue, 3 Dec 2019 at 20:13, Dmitriy Pavlov >> > > wrote: >> > > > > > >> > > > > > Hi Igniters, >> > > > > > >> > > > > > It is not good if we'll made a tradition of linking to company >> > > websites >> > > > > > from the community website / wiki / lists. But if it makes >> sense to >> > > > mention >> > > > > > something useful for users, why not. >> > > > > > >> > > > > > And in this particular case it may be ok, if it is relevant. >> Just >> > > > remember, >> > > > > > community resources are not Nascar cars. >> > > > > > >> > > > > > See also https://www.apache.org/foundation/marks/linking >> > > > > > >> > > > > > Sincerely, >> > > > > > Dmitriy Pavlov >> > > > > > >> > > > > > вт, 3 дек. 2019 г. в 19:50, Denis Magda : >> > > > > > >> > > > > > > Hi Ivan, >> > > > > > > >> > > > > > > If an author of an article believes that there is a 3rd party >> > > > resource that >> > > > > > > is handy and helpful for his/her work then there is nothing >> wrong >> > > to >> > > > refer >> > > > > > > to it. Based on Alexey's response in another thread, that >> GridGain >> > > > page >> > > > > > > brings more clarity to the topic, thus, don't see any issue >> with >> > > > that. >> > > > > > > >> > > > > > > >> > > > > > > - >> > > > > > > Denis >> > > > > > > >> > > > > > > >> > > > > > > On Tue, Dec 3, 2019 at 6:41 AM Ivan Pavlukhin < >> vololo...@gmail.com >> > > > >> > > > wrote: >> > > > > > > >> > > > > > > > Folks, >> > > > > > > > >> > > > > > > > In a thread about a document describing data consistency >> [1] in >> > > > Ignite >> > > > > > > > it was identified that there is a link to GridGain >> documentation. >> > > > > > > > >> > > > > > > > I do not have strong arguments against having such links in >> > > > community >> > > > > > > > wiki. But it interesting to me to discuss the subject with >> > > > community. >> > > > > > > > Might be there is some common practice in ASF communities >> about >> > > the >> > > > > > > > subject. >> > > > > > > > >> > > > > > > > Please, share your thoughts. >> > > > > > > > >> > > > > > > > [1] >> > > > https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency >> > > > > > > > -- >> > > > > > > > Best regards, >> > > > > > > > Ivan Pavlukhin >> > > > > > > > >> > > > > > > >> > > > >> > > > >> > > > >> > > > -- >> > > > Best regards, >> > > > Ivan Pavlukhin >> > > > >> > > >> > >> > >> > -- >> > >> > Best regards, >> > Alexei Scherbakov >> > > > -- > > Best regards, > Alexei Scherbakov > -- Best
[jira] [Created] (IGNITE-12422) Clean up GG-XXX internal ticket references from code base.
Alexei Scherbakov created IGNITE-12422: -- Summary: Clean up GG-XXX internal ticket references from code base. Key: IGNITE-12422 URL: https://issues.apache.org/jira/browse/IGNITE-12422 Project: Ignite Issue Type: Improvement Reporter: Alexei Scherbakov Assignee: Alexei Scherbakov Fix For: 2.9 Replace with Apache Ignite equivalent if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [TeamCIty] Issues with the disc space
Ivan, And another one. Starting the build on the agent "aitc-lin08_01" Failed to download file 'ignite.zip': No space left on device [1] https://ci.ignite.apache.org/viewLog.html?buildId=4815786=IgniteTests24Java8_ThinClientPython=buildLog_IgniteTests24Java8=%3Cdefault%3E&_focus=59 On Thu, 5 Dec 2019 at 16:57, Maxim Muzafarov wrote: > > Ivan, > > Starting the build on the agent "aitc-lin12_03" > Failed to download file 'ignite.zip': No space left on device > > [1] > https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=4814624 > > On Thu, 5 Dec 2019 at 15:13, Ivan Pavlukhin wrote: > > > > Folks, > > > > Agent aitc-lin07 was cleaned. Please check that everything is working > > fine now. If you observe other agents experiencing same problems > > please write in this thread. > > > > чт, 5 дек. 2019 г. в 14:20, Anton Vinogradov : > > > > > > Main problem here that TC Bot ignores such failures for feature branches > > > (since they also happen in master). > > > So, you may gain green VISA without any checks. > > > > > > Everyone, > > > Please make sure you VISAs are legal before the merge. > > > > > > On Thu, Dec 5, 2019 at 2:10 PM Maxim Muzafarov wrote: > > > > > > > Igniters, > > > > > > > > > > > > It seems the issue is still actual. Do we have any idea what's going on? > > > > It's hard to work on the 2.8 release stabilization when we don't have > > > > stable mater branch [1]. > > > > > > > > > > > > [1] > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv > > > > > > > > On Tue, 3 Dec 2019 at 20:36, Николай Ижиков wrote: > > > > > > > > > > Hello, Igniters. > > > > > > > > > > Looks like we have an issues with the TC agents disc space [1] > > > > > Can someone take a look? > > > > > > > > > > [1] > > > > https://ci.ignite.apache.org/viewLog.html?buildId=4809938=buildResultsDiv=IgniteTests24Java8_PlatformCPPLinuxClang > > > > > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin
Re: [DISCUSS] Links to commercial version resources in community wiki
Maxim, Yes, I think I could help. чт, 5 дек. 2019 г. в 19:52, Maxim Muzafarov : > Alexey, > > Thank you so much! Can you help with the other issues? > It would be great to clean up them and enable checkstyle pattern for > such TODOs [1]. > > Here is the full list of issues: > > GG-1075 > GG-1314 > GG-2311 > GG-2329 > GG-2852 > GG-3946 > GG-3997 > GG-4368 > GG-4440 > GG-4911 > GG-6460 > GG-6879 > GG-8123 > GG-8768 > GG-8884 > GG-9141 > GG-10884 > GG-11141 > GG-11148 > GG-11220 > GG-11241 > GG-11480 > GG-11640 > GG-11768 > GG-12292 > GG-13223 > GG-17396 > > > [1] https://checkstyle.sourceforge.io/config_misc.html#TodoComment > > On Thu, 5 Dec 2019 at 19:18, Alexei Scherbakov > wrote: > > > > This is a contribution artifact and was not done intentionally. > > I'll remove it in subsequent contributions. > > > > ср, 4 дек. 2019 г. в 16:57, Dmitriy Pavlov : > > > > > I agree that 'TODO: please, fix me GG-X' Should be definitely > avoided > > > in the code in all cases. A number of community members don't have > access > > > to these tickets. > > > > > > This is the same as linking to GG's private documentation or internal > > > network servers. It doesn't make sense. > > > > > > ср, 4 дек. 2019 г. в 14:53, Ivan Pavlukhin : > > > > > > > Maxim, > > > > > > > > References to GG tickets have definitely no meaning for community. > But > > > > references to documentation on the other hand can be very useful, > > > > actually it is very similar to references to Wikipedia or > > > > aforementioned Oracle resources. > > > > > > > > ср, 4 дек. 2019 г. в 14:40, Maxim Muzafarov : > > > > > > > > > > Folks, > > > > > > > > > > In general case, 3rd party resource links look for me absolutely > > > > > normal e.g. we could have some links on Oracle's documentation > pages. > > > > > > > > > > But let's add a little accuracy. We are talking about links to > > > > > GridGain documentation pages. For me, it's the same as comments > `TODO: > > > > > please, fix me GG-X` in the source code (e.g. like this one > [1]). > > > > > Looks a bit strange :-) > > > > > > > > > > > > > > > [1] > > > > > > > > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/PartitionUpdateCounter.java#L43 > > > > > > > > > > On Tue, 3 Dec 2019 at 20:13, Dmitriy Pavlov > > > wrote: > > > > > > > > > > > > Hi Igniters, > > > > > > > > > > > > It is not good if we'll made a tradition of linking to company > > > websites > > > > > > from the community website / wiki / lists. But if it makes sense > to > > > > mention > > > > > > something useful for users, why not. > > > > > > > > > > > > And in this particular case it may be ok, if it is relevant. Just > > > > remember, > > > > > > community resources are not Nascar cars. > > > > > > > > > > > > See also https://www.apache.org/foundation/marks/linking > > > > > > > > > > > > Sincerely, > > > > > > Dmitriy Pavlov > > > > > > > > > > > > вт, 3 дек. 2019 г. в 19:50, Denis Magda : > > > > > > > > > > > > > Hi Ivan, > > > > > > > > > > > > > > If an author of an article believes that there is a 3rd party > > > > resource that > > > > > > > is handy and helpful for his/her work then there is nothing > wrong > > > to > > > > refer > > > > > > > to it. Based on Alexey's response in another thread, that > GridGain > > > > page > > > > > > > brings more clarity to the topic, thus, don't see any issue > with > > > > that. > > > > > > > > > > > > > > > > > > > > > - > > > > > > > Denis > > > > > > > > > > > > > > > > > > > > > On Tue, Dec 3, 2019 at 6:41 AM Ivan Pavlukhin < > vololo...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > In a thread about a document describing data consistency [1] > in > > > > Ignite > > > > > > > > it was identified that there is a link to GridGain > documentation. > > > > > > > > > > > > > > > > I do not have strong arguments against having such links in > > > > community > > > > > > > > wiki. But it interesting to me to discuss the subject with > > > > community. > > > > > > > > Might be there is some common practice in ASF communities > about > > > the > > > > > > > > subject. > > > > > > > > > > > > > > > > Please, share your thoughts. > > > > > > > > > > > > > > > > [1] > > > > https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency > > > > > > > > -- > > > > > > > > Best regards, > > > > > > > > Ivan Pavlukhin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > > > > > > > -- > > > > Best regards, > > Alexei Scherbakov > -- Best regards, Alexei Scherbakov
Re: [MTCGA]: new failures in builds [4815611] needs to be handled
Slava, Could you please comment about it? I hope we should not worry, should we? пт, 6 дек. 2019 г. в 06:36, : > > 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 your contribution. > Could you respond to this email and indicate if you wish to continue and fix > test failures or step down and some committer may revert you commit. > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheLoaderTest.shouldNotLoadWithNullKeyUsingGetAll > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8927098818965879550=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldWriteThoughUsingPutSingleEntry > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3790886423672221427=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingInvokeAll_setValue_RemoveEntry > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2681498318389082369=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughRemove_SingleEntry > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8793298117642492084=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheLoaderTest.shouldNotLoadMultipleNullEntriesUsingLoadAll > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3328558920428027253=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.expiry.CacheExpiryTest.invokeGetValueWithReadThroughForNonExistentEntryShouldCallGetExpiryForCreatedEntry > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7337820668787439799=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheLoaderTest.shouldLoadWhenCacheMissUsingGet > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6018543995721112425=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.expiry.CacheExpiryTest.loadAllWithReadThroughEnabledShouldCallGetExpiryForCreatedEntry > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9105662735191801339=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldNotInvokeWriteThroughCallingGetOnExistingEntry > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7272172525770006458=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingInvoke_setValue_CreateEntryGetValue > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4683130203309250975=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughReplaceExisting_SingleEntryMultipleTimes > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7891852646072948353=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingGetAndReplace_SingleEntryMultipleTimes > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4406977921763919013=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldNotWriteThroughReplaceNonExistentKey > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3426932562911147972=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingPutOfDifferentEntries > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2531906639751001464=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingGetAndRemove_ExistingSingleEntry > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7108917504324815378=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheLoaderTest.shouldNotLoadUsingPutAll > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4433421382246508548=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master >
[MTCGA]: new failures in builds [4815611] 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 your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *Recently contributed test failed in master org.jsr107.tck.integration.CacheLoaderTest.shouldNotLoadWithNullKeyUsingGetAll https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8927098818965879550=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldWriteThoughUsingPutSingleEntry https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3790886423672221427=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingInvokeAll_setValue_RemoveEntry https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2681498318389082369=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughRemove_SingleEntry https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8793298117642492084=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheLoaderTest.shouldNotLoadMultipleNullEntriesUsingLoadAll https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3328558920428027253=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.expiry.CacheExpiryTest.invokeGetValueWithReadThroughForNonExistentEntryShouldCallGetExpiryForCreatedEntry https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7337820668787439799=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheLoaderTest.shouldLoadWhenCacheMissUsingGet https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6018543995721112425=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.expiry.CacheExpiryTest.loadAllWithReadThroughEnabledShouldCallGetExpiryForCreatedEntry https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9105662735191801339=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldNotInvokeWriteThroughCallingGetOnExistingEntry https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7272172525770006458=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingInvoke_setValue_CreateEntryGetValue https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4683130203309250975=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughReplaceExisting_SingleEntryMultipleTimes https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7891852646072948353=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingGetAndReplace_SingleEntryMultipleTimes https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4406977921763919013=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldNotWriteThroughReplaceNonExistentKey https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3426932562911147972=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingPutOfDifferentEntries https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2531906639751001464=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingGetAndRemove_ExistingSingleEntry https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7108917504324815378=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheLoaderTest.shouldNotLoadUsingPutAll https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4433421382246508548=%3Cdefault%3E=testDetails *Recently contributed test failed in master org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingGetAndPut_SingleEntryMultipleTimes https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-626845466517712470=%3Cdefault%3E=testDetails *Recently contributed test failed in master
[jira] [Created] (IGNITE-12421) Update pom depencencies to 2.9.0-SNAPSHOT version
Maxim Muzafarov created IGNITE-12421:
Summary: Update pom depencencies to 2.9.0-SNAPSHOT version
Key: IGNITE-12421
URL: https://issues.apache.org/jira/browse/IGNITE-12421
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Since the {{ignite-2.8}} the release branch created all version dependencies
must be updated to {{2.9.0-SNAPSHOT}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [DISCUSS] Links to commercial version resources in community wiki
Alexey, Thank you so much! Can you help with the other issues? It would be great to clean up them and enable checkstyle pattern for such TODOs [1]. Here is the full list of issues: GG-1075 GG-1314 GG-2311 GG-2329 GG-2852 GG-3946 GG-3997 GG-4368 GG-4440 GG-4911 GG-6460 GG-6879 GG-8123 GG-8768 GG-8884 GG-9141 GG-10884 GG-11141 GG-11148 GG-11220 GG-11241 GG-11480 GG-11640 GG-11768 GG-12292 GG-13223 GG-17396 [1] https://checkstyle.sourceforge.io/config_misc.html#TodoComment On Thu, 5 Dec 2019 at 19:18, Alexei Scherbakov wrote: > > This is a contribution artifact and was not done intentionally. > I'll remove it in subsequent contributions. > > ср, 4 дек. 2019 г. в 16:57, Dmitriy Pavlov : > > > I agree that 'TODO: please, fix me GG-X' Should be definitely avoided > > in the code in all cases. A number of community members don't have access > > to these tickets. > > > > This is the same as linking to GG's private documentation or internal > > network servers. It doesn't make sense. > > > > ср, 4 дек. 2019 г. в 14:53, Ivan Pavlukhin : > > > > > Maxim, > > > > > > References to GG tickets have definitely no meaning for community. But > > > references to documentation on the other hand can be very useful, > > > actually it is very similar to references to Wikipedia or > > > aforementioned Oracle resources. > > > > > > ср, 4 дек. 2019 г. в 14:40, Maxim Muzafarov : > > > > > > > > Folks, > > > > > > > > In general case, 3rd party resource links look for me absolutely > > > > normal e.g. we could have some links on Oracle's documentation pages. > > > > > > > > But let's add a little accuracy. We are talking about links to > > > > GridGain documentation pages. For me, it's the same as comments `TODO: > > > > please, fix me GG-X` in the source code (e.g. like this one [1]). > > > > Looks a bit strange :-) > > > > > > > > > > > > [1] > > > > > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/PartitionUpdateCounter.java#L43 > > > > > > > > On Tue, 3 Dec 2019 at 20:13, Dmitriy Pavlov > > wrote: > > > > > > > > > > Hi Igniters, > > > > > > > > > > It is not good if we'll made a tradition of linking to company > > websites > > > > > from the community website / wiki / lists. But if it makes sense to > > > mention > > > > > something useful for users, why not. > > > > > > > > > > And in this particular case it may be ok, if it is relevant. Just > > > remember, > > > > > community resources are not Nascar cars. > > > > > > > > > > See also https://www.apache.org/foundation/marks/linking > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > вт, 3 дек. 2019 г. в 19:50, Denis Magda : > > > > > > > > > > > Hi Ivan, > > > > > > > > > > > > If an author of an article believes that there is a 3rd party > > > resource that > > > > > > is handy and helpful for his/her work then there is nothing wrong > > to > > > refer > > > > > > to it. Based on Alexey's response in another thread, that GridGain > > > page > > > > > > brings more clarity to the topic, thus, don't see any issue with > > > that. > > > > > > > > > > > > > > > > > > - > > > > > > Denis > > > > > > > > > > > > > > > > > > On Tue, Dec 3, 2019 at 6:41 AM Ivan Pavlukhin > > > > > wrote: > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > In a thread about a document describing data consistency [1] in > > > Ignite > > > > > > > it was identified that there is a link to GridGain documentation. > > > > > > > > > > > > > > I do not have strong arguments against having such links in > > > community > > > > > > > wiki. But it interesting to me to discuss the subject with > > > community. > > > > > > > Might be there is some common practice in ASF communities about > > the > > > > > > > subject. > > > > > > > > > > > > > > Please, share your thoughts. > > > > > > > > > > > > > > [1] > > > https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency > > > > > > > -- > > > > > > > Best regards, > > > > > > > Ivan Pavlukhin > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Best regards, > > > Ivan Pavlukhin > > > > > > > > -- > > Best regards, > Alexei Scherbakov
Re: Check Code Style suite fails on master
Slava, thanks for noticing! Fixed. чт, 5 дек. 2019 г. в 18:57, Nikita Amelchev : > Hello, Thank you. My bad. > > I have created issue to fix it. [1] > > [1] https://issues.apache.org/jira/browse/IGNITE-12420 > > чт, 5 дек. 2019 г. в 18:41, Вячеслав Коптилин : > > > > > Hello Nikita, > > > > It seems that this commit breaks "Check Code Style" suite at TeamCity. > > [ERROR] > /opt/buildagent/work/7bc1c54bc719b67c/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/index/AbstractIndexingCommonTest.java:28:8: > Unused import - org.apache.ignite.IgniteException. [UnusedImports] > > > > Could you please take a look at this? I think it would be good to create > a separate ticket and resolve the issue. > > > > Thanks, > > S. > > > > -- > Best wishes, > Amelchev Nikita >
Re: [DISCUSS] Links to commercial version resources in community wiki
This is a contribution artifact and was not done intentionally. I'll remove it in subsequent contributions. ср, 4 дек. 2019 г. в 16:57, Dmitriy Pavlov : > I agree that 'TODO: please, fix me GG-X' Should be definitely avoided > in the code in all cases. A number of community members don't have access > to these tickets. > > This is the same as linking to GG's private documentation or internal > network servers. It doesn't make sense. > > ср, 4 дек. 2019 г. в 14:53, Ivan Pavlukhin : > > > Maxim, > > > > References to GG tickets have definitely no meaning for community. But > > references to documentation on the other hand can be very useful, > > actually it is very similar to references to Wikipedia or > > aforementioned Oracle resources. > > > > ср, 4 дек. 2019 г. в 14:40, Maxim Muzafarov : > > > > > > Folks, > > > > > > In general case, 3rd party resource links look for me absolutely > > > normal e.g. we could have some links on Oracle's documentation pages. > > > > > > But let's add a little accuracy. We are talking about links to > > > GridGain documentation pages. For me, it's the same as comments `TODO: > > > please, fix me GG-X` in the source code (e.g. like this one [1]). > > > Looks a bit strange :-) > > > > > > > > > [1] > > > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/PartitionUpdateCounter.java#L43 > > > > > > On Tue, 3 Dec 2019 at 20:13, Dmitriy Pavlov > wrote: > > > > > > > > Hi Igniters, > > > > > > > > It is not good if we'll made a tradition of linking to company > websites > > > > from the community website / wiki / lists. But if it makes sense to > > mention > > > > something useful for users, why not. > > > > > > > > And in this particular case it may be ok, if it is relevant. Just > > remember, > > > > community resources are not Nascar cars. > > > > > > > > See also https://www.apache.org/foundation/marks/linking > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > вт, 3 дек. 2019 г. в 19:50, Denis Magda : > > > > > > > > > Hi Ivan, > > > > > > > > > > If an author of an article believes that there is a 3rd party > > resource that > > > > > is handy and helpful for his/her work then there is nothing wrong > to > > refer > > > > > to it. Based on Alexey's response in another thread, that GridGain > > page > > > > > brings more clarity to the topic, thus, don't see any issue with > > that. > > > > > > > > > > > > > > > - > > > > > Denis > > > > > > > > > > > > > > > On Tue, Dec 3, 2019 at 6:41 AM Ivan Pavlukhin > > > wrote: > > > > > > > > > > > Folks, > > > > > > > > > > > > In a thread about a document describing data consistency [1] in > > Ignite > > > > > > it was identified that there is a link to GridGain documentation. > > > > > > > > > > > > I do not have strong arguments against having such links in > > community > > > > > > wiki. But it interesting to me to discuss the subject with > > community. > > > > > > Might be there is some common practice in ASF communities about > the > > > > > > subject. > > > > > > > > > > > > Please, share your thoughts. > > > > > > > > > > > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency > > > > > > -- > > > > > > Best regards, > > > > > > Ivan Pavlukhin > > > > > > > > > > > > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > > -- Best regards, Alexei Scherbakov
Re: Check Code Style suite fails on master
Hi Nikita, Thanks a lot! чт, 5 дек. 2019 г. в 18:57, Nikita Amelchev : > Hello, Thank you. My bad. > > I have created issue to fix it. [1] > > [1] https://issues.apache.org/jira/browse/IGNITE-12420 > > чт, 5 дек. 2019 г. в 18:41, Вячеслав Коптилин : > > > > > Hello Nikita, > > > > It seems that this commit breaks "Check Code Style" suite at TeamCity. > > [ERROR] > /opt/buildagent/work/7bc1c54bc719b67c/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/index/AbstractIndexingCommonTest.java:28:8: > Unused import - org.apache.ignite.IgniteException. [UnusedImports] > > > > Could you please take a look at this? I think it would be good to create > a separate ticket and resolve the issue. > > > > Thanks, > > S. > > > > -- > Best wishes, > Amelchev Nikita >
Re: Check Code Style suite fails on master
Hello, Thank you. My bad. I have created issue to fix it. [1] [1] https://issues.apache.org/jira/browse/IGNITE-12420 чт, 5 дек. 2019 г. в 18:41, Вячеслав Коптилин : > > Hello Nikita, > > It seems that this commit breaks "Check Code Style" suite at TeamCity. > [ERROR] > /opt/buildagent/work/7bc1c54bc719b67c/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/index/AbstractIndexingCommonTest.java:28:8: > Unused import - org.apache.ignite.IgniteException. [UnusedImports] > > Could you please take a look at this? I think it would be good to create a > separate ticket and resolve the issue. > > Thanks, > S. -- Best wishes, Amelchev Nikita
[jira] [Created] (IGNITE-12420) Fix broken the Check Code Style suite
Amelchev Nikita created IGNITE-12420:
Summary: Fix broken the Check Code Style suite
Key: IGNITE-12420
URL: https://issues.apache.org/jira/browse/IGNITE-12420
Project: Ignite
Issue Type: Task
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
The Check Code Style suite fails with error:
{noformat}
[ERROR]
/opt/buildagent/work/7bc1c54bc719b67c/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/index/AbstractIndexingCommonTest.java:28:8:
Unused import - org.apache.ignite.IgniteException. [UnusedImports]
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Check Code Style suite fails on master
Hello Nikita, It seems that this commit breaks "Check Code Style" suite at TeamCity. [ERROR] /opt/buildagent/work/7bc1c54bc719b67c/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/index/AbstractIndexingCommonTest.java:28:8: Unused import - org.apache.ignite.IgniteException. [UnusedImports] Could you please take a look at this? I think it would be good to create a separate ticket and resolve the issue. Thanks, S.
[jira] [Created] (IGNITE-12419) JCache TCK fails with NullPointerException
Vyacheslav Koptilin created IGNITE-12419:
Summary: JCache TCK fails with NullPointerException
Key: IGNITE-12419
URL: https://issues.apache.org/jira/browse/IGNITE-12419
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.7.6
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin
Fix For: 2.8
It seems a long period of time, JCache suite did not run TCK tests and for now,
more than 90 tests are broken with the following exception:
{code:java}
class org.apache.ignite.IgniteCheckedException: Cannot enable read-through
(loader or store is not provided) for cache: cache-loader-testclass
org.apache.ignite.IgniteCheckedException: Cannot enable read-through (loader or
store is not provided) for cache: cache-loader-test at
org.apache.ignite.internal.processors.cache.ValidationOnNodeJoinUtils.validate(ValidationOnNodeJoinUtils.java:348)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1190)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:1984)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1915)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$55a0e703$1(GridCacheProcessor.java:1790)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCachesIfPossible$9(GridCacheProcessor.java:1760)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1787)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCachesIfPossible(GridCacheProcessor.java:1758)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:968)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:854)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1281)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:811)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3172)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3021)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{code}
It looks like, the root cause of the failure is IGNITE-1903. At first glance,
it can be easily fixed.
I think that cache configuration initialization should be done before it is
split by {{CacheConfigurationSplitter -
GridCacheProcessor.prepareCacheChangeRequest()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [TeamCIty] Issues with the disc space
Ivan, Starting the build on the agent "aitc-lin12_03" Failed to download file 'ignite.zip': No space left on device [1] https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=4814624 On Thu, 5 Dec 2019 at 15:13, Ivan Pavlukhin wrote: > > Folks, > > Agent aitc-lin07 was cleaned. Please check that everything is working > fine now. If you observe other agents experiencing same problems > please write in this thread. > > чт, 5 дек. 2019 г. в 14:20, Anton Vinogradov : > > > > Main problem here that TC Bot ignores such failures for feature branches > > (since they also happen in master). > > So, you may gain green VISA without any checks. > > > > Everyone, > > Please make sure you VISAs are legal before the merge. > > > > On Thu, Dec 5, 2019 at 2:10 PM Maxim Muzafarov wrote: > > > > > Igniters, > > > > > > > > > It seems the issue is still actual. Do we have any idea what's going on? > > > It's hard to work on the 2.8 release stabilization when we don't have > > > stable mater branch [1]. > > > > > > > > > [1] > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv > > > > > > On Tue, 3 Dec 2019 at 20:36, Николай Ижиков wrote: > > > > > > > > Hello, Igniters. > > > > > > > > Looks like we have an issues with the TC agents disc space [1] > > > > Can someone take a look? > > > > > > > > [1] > > > https://ci.ignite.apache.org/viewLog.html?buildId=4809938=buildResultsDiv=IgniteTests24Java8_PlatformCPPLinuxClang > > > > > > > -- > Best regards, > Ivan Pavlukhin
Re: Non-blocking PME Phase One (Node fail)
Igniters, Solution ready to be reviewed TeamCity is green: https://issues.apache.org/jira/browse/IGNITE-9913?focusedCommentId=16988566=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16988566 Issue: https://issues.apache.org/jira/browse/IGNITE-9913 Relevant PR: https://github.com/apache/ignite/pull/7069 In brief: Solution allows avoiding PME and running transactions waiting on node left. What done/changed: Extended Late Affinity Assignment semantic: from "guarantee to switch when ideal primaries rebalanced" to "guarantee to switch when all expected owners rebalanced". This extension provides the ability to perform PME-free switch on baseline node left when cluster fully rebalanced, avoiding a lot of corner-cases possible on a partially rebalanced cluster. The PME-free switch does not block or cancel or wait for current operations. It's just recover failed primaries and once cluster-wide recovery finished it finishes exchange future (allows new operations). So in other words, now new-topology operations allowed immediately after cluster-wide recovery finished (which is fast), not after previous-topology operations finished + recovery + PME, as it was before. Limitations: Optimization works only when baseline set (alive primaries require no relocation, recovery required for failed primaries). BTW, PME-free code seems to be small and simple, most of the changes related to the "rebalanced cluster guarantee". It will be nice if someone will check the code and tests. Test coverage proposals are welcome! P.s. Here's a benchmark used to check we have performance improvements listed above https://github.com/anton-vinogradov/ignite/blob/426f0de9185ac2938dadb7bd2cbfe488233fe7d6/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/Bench.java P.p.s. We also checked the same case on the real environment and found no latency degradation. On Thu, Sep 19, 2019 at 2:18 PM Anton Vinogradov wrote: > Ivan, > > The useful profile can be produced only by the reproducible benchmark. > We're working on such benchmark to analyze duration and measure the > improvement. > > Currently, only the typical overall duration from prod servers is known. > > On Thu, Sep 19, 2019 at 12:09 PM Павлухин Иван > wrote: > >> Anton, folks, >> >> Out of curiosity. Do we have some measurements of PME execution in an >> environment similar to some real-world one? In my mind some kind of >> "profile" showing durations of different PME phases with an indication >> where we are "blocked" would be ideal. >> >> ср, 18 сент. 2019 г. в 13:27, Anton Vinogradov : >> > >> > Alexey, >> > >> > >> Can you describe the complete protocol changes first >> > The current goal is to find a better way. >> > I had at least 5 scenarios discarded because of finding corner cases >> > (Thanks to Alexey Scherbakov, Aleksei Plekhanov and Nikita Amelchev). >> > That's why I explained what we able to improve and why I think it works. >> > >> > >> we need to remove this property, not add new logic that relies on it. >> > Agree. >> > >> > >> How are you going to synchronize this? >> > Thanks for providing this case, seems it discards #1 + #2.2 case and >> #2.1 >> > still possible with some optimizations. >> > >> > "Zombie eating transactions" case can be theoretically solved, I think. >> > As I said before we may perform "Local switch" in case affinity was not >> > changed (except failed mode miss) other cases require regular PME. >> > In this case, new-primary is an ex-backup and we expect that old-primary >> > will try to update new-primary as a backup. >> > New primary will handle operations as a backup until it notified it's a >> > primary now. >> > Operations from ex-primary will be discarded or remapped once >> new-primary >> > notified it became the primary. >> > >> > Discarding is a big improvement, >> > remapping is a huge improvement, >> > there is no 100% warranty that ex-primary will try to update >> new-primary as >> > a backup. >> > >> > A lot of corner cases here. >> > So, seems minimized sync is a better solution. >> > >> > Finally, according to your and Alexey Scherbakov's comments, the better >> > case is just to improve PME to wait for less, at least now. >> > Seems, we have to wait for (or cancel, I vote for this case - any >> > objections?) operations related to the failed primaries and wait for >> > recovery finish (which is fast). >> > In case affinity was changed and backup-primary switch (not related to >> the >> > failed primaries) required between the owners or even rebalance >> required, >> > we should just ignore this and perform only "Recovery PME". >> > Regular PME should happen later (if necessary), it can be even delayed >> (if >> > necessary). >> > >> > Sounds good? >> > >> > On Wed, Sep 18, 2019 at 11:46 AM Alexey Goncharuk < >> > alexey.goncha...@gmail.com> wrote: >> > >> > > Anton, >> > > >> > > I looked through the presentation and the ticket but did not find any >> new >> > >
Re: Hello Ignite Community!
Hi Wang Cheng, I merged your fix into master. Thank you! чт, 5 дек. 2019 г. в 12:35, Ilya Kasnacheev : > > Hello! > > I have added you to Contributors role, now you should be able to assign > issues to yourself. > > Please make sure to read > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > Regards, > -- > Ilya Kasnacheev > > > чт, 5 дек. 2019 г. в 12:23, 王成 : > > > Hello Ignite Community! > > > > My name is Wang Cheng, I'm Java developer from China, I want to contribute > > to Apache Ignite and want to start with this issue - IGNITE-12303, my JIRA > > username hadoop1024. Any help on this will be appreciated. > > > > Btw,I have used ignite for real online systems and I find it really good. > > So, I want to learn more about it by contributing code. > > > > Thanks! > > > > Wang Cheng > > -- Best regards, Ivan Pavlukhin
Re: [TeamCIty] Issues with the disc space
Folks, Agent aitc-lin07 was cleaned. Please check that everything is working fine now. If you observe other agents experiencing same problems please write in this thread. чт, 5 дек. 2019 г. в 14:20, Anton Vinogradov : > > Main problem here that TC Bot ignores such failures for feature branches > (since they also happen in master). > So, you may gain green VISA without any checks. > > Everyone, > Please make sure you VISAs are legal before the merge. > > On Thu, Dec 5, 2019 at 2:10 PM Maxim Muzafarov wrote: > > > Igniters, > > > > > > It seems the issue is still actual. Do we have any idea what's going on? > > It's hard to work on the 2.8 release stabilization when we don't have > > stable mater branch [1]. > > > > > > [1] > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv > > > > On Tue, 3 Dec 2019 at 20:36, Николай Ижиков wrote: > > > > > > Hello, Igniters. > > > > > > Looks like we have an issues with the TC agents disc space [1] > > > Can someone take a look? > > > > > > [1] > > https://ci.ignite.apache.org/viewLog.html?buildId=4809938=buildResultsDiv=IgniteTests24Java8_PlatformCPPLinuxClang > > -- Best regards, Ivan Pavlukhin
Re: [TeamCIty] Issues with the disc space
Main problem here that TC Bot ignores such failures for feature branches (since they also happen in master). So, you may gain green VISA without any checks. Everyone, Please make sure you VISAs are legal before the merge. On Thu, Dec 5, 2019 at 2:10 PM Maxim Muzafarov wrote: > Igniters, > > > It seems the issue is still actual. Do we have any idea what's going on? > It's hard to work on the 2.8 release stabilization when we don't have > stable mater branch [1]. > > > [1] > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv > > On Tue, 3 Dec 2019 at 20:36, Николай Ижиков wrote: > > > > Hello, Igniters. > > > > Looks like we have an issues with the TC agents disc space [1] > > Can someone take a look? > > > > [1] > https://ci.ignite.apache.org/viewLog.html?buildId=4809938=buildResultsDiv=IgniteTests24Java8_PlatformCPPLinuxClang >
Re: [TeamCIty] Issues with the disc space
Igniters, It seems the issue is still actual. Do we have any idea what's going on? It's hard to work on the 2.8 release stabilization when we don't have stable mater branch [1]. [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv On Tue, 3 Dec 2019 at 20:36, Николай Ижиков wrote: > > Hello, Igniters. > > Looks like we have an issues with the TC agents disc space [1] > Can someone take a look? > > [1] > https://ci.ignite.apache.org/viewLog.html?buildId=4809938=buildResultsDiv=IgniteTests24Java8_PlatformCPPLinuxClang
Re: Hello Ignite Community!
Hello! I have added you to Contributors role, now you should be able to assign issues to yourself. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev чт, 5 дек. 2019 г. в 12:23, 王成 : > Hello Ignite Community! > > My name is Wang Cheng, I'm Java developer from China, I want to contribute > to Apache Ignite and want to start with this issue - IGNITE-12303, my JIRA > username hadoop1024. Any help on this will be appreciated. > > Btw,I have used ignite for real online systems and I find it really good. > So, I want to learn more about it by contributing code. > > Thanks! > > Wang Cheng >
Hello Ignite Community!
Hello Ignite Community! My name is Wang Cheng, I'm Java developer from China, I want to contribute to Apache Ignite and want to start with this issue - IGNITE-12303, my JIRA username hadoop1024. Any help on this will be appreciated. Btw,I have used ignite for real online systems and I find it really good. So, I want to learn more about it by contributing code. Thanks! Wang Cheng
