Re: Stop sending IGNITE Created e-mails to dev@
Ilya, INFA has apparently accomplished with the ticket [1]. Do we have plans to document somewhere how to subscribe for new ticket notifications? [1] https://issues.apache.org/jira/browse/INFRA-21762 2021-04-22 18:22 GMT+03:00, Dmitriy Pavlov : > +1 for issues > -1 for TC bot. For the latter I siggest improving analysis to avoid odd > emails and leave only relevant > > чт, 22 апр. 2021 г., 18:16 Ivan Pavlukhin : > >> > All issues notifications are also sent to iss...@ignite.apache.org so >> one can subscribe to this list in order to track the created tickets. >> >> Does not sound as useful advice. Issues list [1] looks like real >> scrapyard, I doubt that it can be usable for anyone in current flavor. >> Can we send only "Created" notifications there? >> >> [1] https://lists.apache.org/list.html?iss...@ignite.apache.org >> >> 2021-04-21 18:30 GMT+03:00, Ilya Kasnacheev : >> > Hello! >> > >> > INFRA ticket created: https://issues.apache.org/jira/browse/INFRA-21762 >> > >> > I have asked to keep sending the created issue notifications for >> > "Contributors 1" role, which is empty at present. So if you wish to >> > keep >> > getting those e-mails, please add yourself to this role or tell me to >> > do >> so >> > for you. >> > >> > Regards, >> > -- >> > Ilya Kasnacheev >> > >> > >> > ср, 21 апр. 2021 г. в 17:59, Alexey Goncharuk < >> alexey.goncha...@gmail.com>: >> > >> >> I support the idea. All issues notifications are also sent to >> >> iss...@ignite.apache.org so one can subscribe to this list in order to >> >> track the created tickets. The notifications trash the devlist archive >> UI >> >> and make it extremely difficult to navigate. >> >> >> >> вт, 20 апр. 2021 г. в 18:35, Ilya Kasnacheev >> >> > >: >> >> >> >> > Hello, Maxim! >> >> > >> >> > You are free to revert any commit which has led to any new stable >> >> > test >> >> > failure, or new flaky test that was non-flaky before. >> >> > >> >> > Just revert the change and reopen the ticket. >> >> > >> >> > The problem here is that it's very hard to detect on the spot, most >> >> > of >> >> > MTCGA e-mails are false positives and even if they are not, it is >> >> > not >> >> > relevant for most of developers. >> >> > >> >> > WDYT? I'm also still waiting for more input. >> >> > >> >> > Regards, >> >> > -- >> >> > Ilya Kasnacheev >> >> > >> >> > >> >> > ср, 14 апр. 2021 г. в 21:26, Maxim Muzafarov : >> >> > >> >> > > +1 for new JIRA issues >> >> > > -1 for MTCGA notifications >> >> > > >> >> > > Why we should hide errors from the dev-list? Who should take care >> >> > > of >> >> > > issues reported by MTCGA.Bot in this case? >> >> > > We must apply stricter rules for such issues: a commit leading to >> >> > > an >> >> > > error must be reverted. >> >> > > >> >> > > On Wed, 14 Apr 2021 at 20:00, Denis Mekhanikov >> >> > > >> >> > > wrote: >> >> > > > >> >> > > > Huge +1 to this. >> >> > > > >> >> > > > I've already brought up this topic in the past: >> >> > > > >> >> > > >> >> > >> >> >> http://apache-ignite-developers.2346864.n4.nabble.com/Bots-on-dev-list-td34406.html >> >> > > > I hope some day newcomers won't need to set up their email >> >> > > > filters >> >> when >> >> > > > they come to the developers list. >> >> > > > >> >> > > > Denis >> >> > > > >> >> > > > ср, 14 апр. 2021 г. в 18:07, Atri Sharma : >> >> > > > >> >> > > > > +1 to move issues to the issues list. >> >> > > > > >> >> > > > > For MTCGA, maybe build@? >> >> > > > > >> >> > > > > On Wed, Apr 14, 2021 at 8:35 PM Ilya Kasnacheev >> >> > > > > >> >> > > wrote: >> >> > > > > > >> >> > > > > > Hello! >> >> > > > > > >> >> > > > > > We have a discussion on how to ensure best engagement in >> >> > > > > > dev@ >> >> > list, >> >> > > and >> >> > > > > it >> >> > > > > > seems that Issue Created emails from IGNITE project consume >> >> > > > > > a >> >> > > > > > lot >> >> > of >> >> > > > > screen >> >> > > > > > space, it's hard to spot genuine discussions in >> >> > > > > > https://lists.apache.org/list.html?dev@ignite.apache.org for >> >> > > example. >> >> > > > > > >> >> > > > > > We already have issues@ mailing list. I propose that we stop >> >> > > sending any >> >> > > > > > JIRA emails to dev@. If anyone wishes to get just Created >> >> emails, >> >> > > they >> >> > > > > can >> >> > > > > > subscribe to these messages in their JIRA account settings. >> >> > > > > > I >> >> > imagine >> >> > > > > most >> >> > > > > > of you already filter these messages out, so you may need to >> >> adjust >> >> > > your >> >> > > > > > filters slightly. >> >> > > > > > >> >> > > > > > A distant second is MTCGA messages, which are also >> >> > > > > > autogenerated >> >> > and >> >> > > not >> >> > > > > > informative for most readers of the channel, since they are >> >> > > > > > at >> >> best >> >> > > > > > targeted at a single committer and at worst flaky. >> >> > > > > > >> >> > > > > > Where could we move those? What is your opinion here, on >> >> > > > > > both >> >> > issues? >> >>
Re: [DISCUSSION] Documentation of thin clients (python, php, nodejs)
Hi Ivan, Thanks for sharing the information. I'll look through the docs and share my thoughts and suggestions soon. Regards, Nikita пт, 23 апр. 2021 г. в 14:06, Ivan Daschinsky : > Hi, Nikita! Thanks for support. > > As developers of thin client, we also would try to update > documentation as soon as possible. > For example, recently I've merged to master expiry policy support for > python thin client and documentation was updated simultaneously [2][3] > > I am planning to update documentation frequently and I would > appreciate any feedback about our current documentation on > readthedocs.io > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-14595 > [2] -- > https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/examples.html#expirypolicy > [3] -- > https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/async_examples.html#expirypolicy > > > > пт, 23 апр. 2021 г. в 13:29, Никита Сафонов : > > > > Hi Ivan, > > > > Thank you for the suggestion. > > > > I agree that Ignite main docs on thin clients probably need a clean-up to > > be kept up-to-date. > > And migrating the key information to readthedocs.io is really an option. > > > > Let's see what other Igniters think about this idea. > > > > I'd be glad if Igor Gusev could share his opinion on this. > > > > Regards, > > Nikita > > > > > > > > чт, 22 апр. 2021 г. в 22:15, Ivan Daschinsky : > > > > > Igniters, there are some questions regarding the documentation state > > > of thin clients. > > > > > > Recently, we have released pyignite 0.4.0. Traditionally, > > > documentation for python thin client is autogenerated from source and > > > contains in the same git repository, as the client itself. > > > Documentation is autogenerated and hosted in familiar for python > > > developers manner -- on readthedocs.io (Namely, > > > https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/ > ) > > > > > > I suppose the same statement is true for other separately developed > > > clients (nodejs, php). > > > > > > So I'd like to discuss a current documentation approach for thin > clients. > > > 1. I strongly believe that the main documentation site for at least > > > python thin client should be readthedocs.io. > > > 2. Documentation should be maintained in the same repository as the > > > thin client itself. > > > 3. As the main documentation's version is tightly coupled with ignite > > > release cycle, it is by default outdated and doesn't resemble the > > > latest version of thin client. > > > > > > I suggest just remove all documentation from the main docs except > > > simple installation instruction (i.e. pip install pyignite) and link > > > to readthedocs.io > > > > > > Regards, Ivan Daschinsky > > > > > > > -- > Sincerely yours, Ivan Daschinskiy >
Re: [DISCUSSION] Documentation of thin clients (python, php, nodejs)
Hi, Ivan, I like your suggestion. To me it looks better than the current approach. Best Regards, Igor On Mon, Apr 26, 2021 at 11:47 AM Nikita Safonov wrote: > Hi Ivan, > > Thanks for sharing the information. > I'll look through the docs and share my thoughts and suggestions soon. > > Regards, > Nikita > > > пт, 23 апр. 2021 г. в 14:06, Ivan Daschinsky : > > > Hi, Nikita! Thanks for support. > > > > As developers of thin client, we also would try to update > > documentation as soon as possible. > > For example, recently I've merged to master expiry policy support for > > python thin client and documentation was updated simultaneously [2][3] > > > > I am planning to update documentation frequently and I would > > appreciate any feedback about our current documentation on > > readthedocs.io > > > > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-14595 > > [2] -- > > > https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/examples.html#expirypolicy > > [3] -- > > > https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/async_examples.html#expirypolicy > > > > > > > > пт, 23 апр. 2021 г. в 13:29, Никита Сафонов : > > > > > > Hi Ivan, > > > > > > Thank you for the suggestion. > > > > > > I agree that Ignite main docs on thin clients probably need a clean-up > to > > > be kept up-to-date. > > > And migrating the key information to readthedocs.io is really an > option. > > > > > > Let's see what other Igniters think about this idea. > > > > > > I'd be glad if Igor Gusev could share his opinion on this. > > > > > > Regards, > > > Nikita > > > > > > > > > > > > чт, 22 апр. 2021 г. в 22:15, Ivan Daschinsky : > > > > > > > Igniters, there are some questions regarding the documentation state > > > > of thin clients. > > > > > > > > Recently, we have released pyignite 0.4.0. Traditionally, > > > > documentation for python thin client is autogenerated from source and > > > > contains in the same git repository, as the client itself. > > > > Documentation is autogenerated and hosted in familiar for python > > > > developers manner -- on readthedocs.io (Namely, > > > > > https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/ > > ) > > > > > > > > I suppose the same statement is true for other separately developed > > > > clients (nodejs, php). > > > > > > > > So I'd like to discuss a current documentation approach for thin > > clients. > > > > 1. I strongly believe that the main documentation site for at least > > > > python thin client should be readthedocs.io. > > > > 2. Documentation should be maintained in the same repository as the > > > > thin client itself. > > > > 3. As the main documentation's version is tightly coupled with ignite > > > > release cycle, it is by default outdated and doesn't resemble the > > > > latest version of thin client. > > > > > > > > I suggest just remove all documentation from the main docs except > > > > simple installation instruction (i.e. pip install pyignite) and link > > > > to readthedocs.io > > > > > > > > Regards, Ivan Daschinsky > > > > > > > > > > > > -- > > Sincerely yours, Ivan Daschinskiy > > >
Re: Stop sending IGNITE Created e-mails to dev@
Hello! I have added you to "Contributors 1" role. Everybody in this role will still get those "issue created" e-mail. Feel free in asking me to enlist. Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 18:16, Ivan Pavlukhin : > > All issues notifications are also sent to iss...@ignite.apache.org so > one can subscribe to this list in order to track the created tickets. > > Does not sound as useful advice. Issues list [1] looks like real > scrapyard, I doubt that it can be usable for anyone in current flavor. > Can we send only "Created" notifications there? > > [1] https://lists.apache.org/list.html?iss...@ignite.apache.org > > 2021-04-21 18:30 GMT+03:00, Ilya Kasnacheev : > > Hello! > > > > INFRA ticket created: https://issues.apache.org/jira/browse/INFRA-21762 > > > > I have asked to keep sending the created issue notifications for > > "Contributors 1" role, which is empty at present. So if you wish to keep > > getting those e-mails, please add yourself to this role or tell me to do > so > > for you. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > ср, 21 апр. 2021 г. в 17:59, Alexey Goncharuk < > alexey.goncha...@gmail.com>: > > > >> I support the idea. All issues notifications are also sent to > >> iss...@ignite.apache.org so one can subscribe to this list in order to > >> track the created tickets. The notifications trash the devlist archive > UI > >> and make it extremely difficult to navigate. > >> > >> вт, 20 апр. 2021 г. в 18:35, Ilya Kasnacheev >: > >> > >> > Hello, Maxim! > >> > > >> > You are free to revert any commit which has led to any new stable test > >> > failure, or new flaky test that was non-flaky before. > >> > > >> > Just revert the change and reopen the ticket. > >> > > >> > The problem here is that it's very hard to detect on the spot, most of > >> > MTCGA e-mails are false positives and even if they are not, it is not > >> > relevant for most of developers. > >> > > >> > WDYT? I'm also still waiting for more input. > >> > > >> > Regards, > >> > -- > >> > Ilya Kasnacheev > >> > > >> > > >> > ср, 14 апр. 2021 г. в 21:26, Maxim Muzafarov : > >> > > >> > > +1 for new JIRA issues > >> > > -1 for MTCGA notifications > >> > > > >> > > Why we should hide errors from the dev-list? Who should take care of > >> > > issues reported by MTCGA.Bot in this case? > >> > > We must apply stricter rules for such issues: a commit leading to an > >> > > error must be reverted. > >> > > > >> > > On Wed, 14 Apr 2021 at 20:00, Denis Mekhanikov > >> > > > >> > > wrote: > >> > > > > >> > > > Huge +1 to this. > >> > > > > >> > > > I've already brought up this topic in the past: > >> > > > > >> > > > >> > > >> > http://apache-ignite-developers.2346864.n4.nabble.com/Bots-on-dev-list-td34406.html > >> > > > I hope some day newcomers won't need to set up their email filters > >> when > >> > > > they come to the developers list. > >> > > > > >> > > > Denis > >> > > > > >> > > > ср, 14 апр. 2021 г. в 18:07, Atri Sharma : > >> > > > > >> > > > > +1 to move issues to the issues list. > >> > > > > > >> > > > > For MTCGA, maybe build@? > >> > > > > > >> > > > > On Wed, Apr 14, 2021 at 8:35 PM Ilya Kasnacheev > >> > > > > > >> > > wrote: > >> > > > > > > >> > > > > > Hello! > >> > > > > > > >> > > > > > We have a discussion on how to ensure best engagement in dev@ > >> > list, > >> > > and > >> > > > > it > >> > > > > > seems that Issue Created emails from IGNITE project consume a > >> > > > > > lot > >> > of > >> > > > > screen > >> > > > > > space, it's hard to spot genuine discussions in > >> > > > > > https://lists.apache.org/list.html?dev@ignite.apache.org for > >> > > example. > >> > > > > > > >> > > > > > We already have issues@ mailing list. I propose that we stop > >> > > sending any > >> > > > > > JIRA emails to dev@. If anyone wishes to get just Created > >> emails, > >> > > they > >> > > > > can > >> > > > > > subscribe to these messages in their JIRA account settings. I > >> > imagine > >> > > > > most > >> > > > > > of you already filter these messages out, so you may need to > >> adjust > >> > > your > >> > > > > > filters slightly. > >> > > > > > > >> > > > > > A distant second is MTCGA messages, which are also > >> > > > > > autogenerated > >> > and > >> > > not > >> > > > > > informative for most readers of the channel, since they are at > >> best > >> > > > > > targeted at a single committer and at worst flaky. > >> > > > > > > >> > > > > > Where could we move those? What is your opinion here, on both > >> > issues? > >> > > > > > > >> > > > > > Regards, > >> > > > > > >> > > > > -- > >> > > > > Regards, > >> > > > > > >> > > > > Atri > >> > > > > Apache Concerted > >> > > > > > >> > > > >> > > >> > > > > > -- > > Best regards, > Ivan Pavlukhin >
Re: NodeJS thin client: full API
Thanks for issuing a ticket. I'll take a look at it. Best Regards, Igor On Fri, Apr 23, 2021 at 1:40 PM teligenz.dheeraj wrote: > Team, > > I have used nodejs thin client to connect ignite. With single query at time > on socket works fine. But when hit multiple request simultaneously, getting > frequent error message "Invalid response id: XXX". > > when we try to get 5-10 query per sec we getting below error random times. > > debug - Error: Invalid response id: 4122254909997320969at > /webapp/node_modules/apache-ignite-client/lib/internal/ClientSocket.js:344:28 > > at Map.forEach ()at ClientSocket._disconnect > (/webapp/node_modules/apache-ignite-client/lib/internal/ClientSocket.js:343:24) > > at Socket. > (/webapp/node_modules/apache-ignite-client/lib/internal/ClientSocket.js:170:22) > > at runMicrotasks ()at processTicksAndRejections > > I have mark complete issue detail in on https://issues.apache.org/ with > issue id IGNITE-14550 > > https://issues.apache.org/jira/browse/IGNITE-14550 > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
Re: Stop sending IGNITE Created e-mails to dev@
Hi Ilya, > I have added you to "Contributors 1" role. Everybody in this role will still > get those "issue created" e-mail. Thank you for that! Should not we mention this tweak with "Contributors 1" role somewhere in advanced how-to-contribute page? 2021-04-26 12:28 GMT+03:00, Ilya Kasnacheev : > Hello! > > I have added you to "Contributors 1" role. Everybody in this role will > still get those "issue created" e-mail. > > Feel free in asking me to enlist. > > Regards, > -- > Ilya Kasnacheev > > > чт, 22 апр. 2021 г. в 18:16, Ivan Pavlukhin : > >> > All issues notifications are also sent to iss...@ignite.apache.org so >> one can subscribe to this list in order to track the created tickets. >> >> Does not sound as useful advice. Issues list [1] looks like real >> scrapyard, I doubt that it can be usable for anyone in current flavor. >> Can we send only "Created" notifications there? >> >> [1] https://lists.apache.org/list.html?iss...@ignite.apache.org >> >> 2021-04-21 18:30 GMT+03:00, Ilya Kasnacheev : >> > Hello! >> > >> > INFRA ticket created: https://issues.apache.org/jira/browse/INFRA-21762 >> > >> > I have asked to keep sending the created issue notifications for >> > "Contributors 1" role, which is empty at present. So if you wish to >> > keep >> > getting those e-mails, please add yourself to this role or tell me to >> > do >> so >> > for you. >> > >> > Regards, >> > -- >> > Ilya Kasnacheev >> > >> > >> > ср, 21 апр. 2021 г. в 17:59, Alexey Goncharuk < >> alexey.goncha...@gmail.com>: >> > >> >> I support the idea. All issues notifications are also sent to >> >> iss...@ignite.apache.org so one can subscribe to this list in order to >> >> track the created tickets. The notifications trash the devlist archive >> UI >> >> and make it extremely difficult to navigate. >> >> >> >> вт, 20 апр. 2021 г. в 18:35, Ilya Kasnacheev >> >> > >: >> >> >> >> > Hello, Maxim! >> >> > >> >> > You are free to revert any commit which has led to any new stable >> >> > test >> >> > failure, or new flaky test that was non-flaky before. >> >> > >> >> > Just revert the change and reopen the ticket. >> >> > >> >> > The problem here is that it's very hard to detect on the spot, most >> >> > of >> >> > MTCGA e-mails are false positives and even if they are not, it is >> >> > not >> >> > relevant for most of developers. >> >> > >> >> > WDYT? I'm also still waiting for more input. >> >> > >> >> > Regards, >> >> > -- >> >> > Ilya Kasnacheev >> >> > >> >> > >> >> > ср, 14 апр. 2021 г. в 21:26, Maxim Muzafarov : >> >> > >> >> > > +1 for new JIRA issues >> >> > > -1 for MTCGA notifications >> >> > > >> >> > > Why we should hide errors from the dev-list? Who should take care >> >> > > of >> >> > > issues reported by MTCGA.Bot in this case? >> >> > > We must apply stricter rules for such issues: a commit leading to >> >> > > an >> >> > > error must be reverted. >> >> > > >> >> > > On Wed, 14 Apr 2021 at 20:00, Denis Mekhanikov >> >> > > >> >> > > wrote: >> >> > > > >> >> > > > Huge +1 to this. >> >> > > > >> >> > > > I've already brought up this topic in the past: >> >> > > > >> >> > > >> >> > >> >> >> http://apache-ignite-developers.2346864.n4.nabble.com/Bots-on-dev-list-td34406.html >> >> > > > I hope some day newcomers won't need to set up their email >> >> > > > filters >> >> when >> >> > > > they come to the developers list. >> >> > > > >> >> > > > Denis >> >> > > > >> >> > > > ср, 14 апр. 2021 г. в 18:07, Atri Sharma : >> >> > > > >> >> > > > > +1 to move issues to the issues list. >> >> > > > > >> >> > > > > For MTCGA, maybe build@? >> >> > > > > >> >> > > > > On Wed, Apr 14, 2021 at 8:35 PM Ilya Kasnacheev >> >> > > > > >> >> > > wrote: >> >> > > > > > >> >> > > > > > Hello! >> >> > > > > > >> >> > > > > > We have a discussion on how to ensure best engagement in >> >> > > > > > dev@ >> >> > list, >> >> > > and >> >> > > > > it >> >> > > > > > seems that Issue Created emails from IGNITE project consume >> >> > > > > > a >> >> > > > > > lot >> >> > of >> >> > > > > screen >> >> > > > > > space, it's hard to spot genuine discussions in >> >> > > > > > https://lists.apache.org/list.html?dev@ignite.apache.org for >> >> > > example. >> >> > > > > > >> >> > > > > > We already have issues@ mailing list. I propose that we stop >> >> > > sending any >> >> > > > > > JIRA emails to dev@. If anyone wishes to get just Created >> >> emails, >> >> > > they >> >> > > > > can >> >> > > > > > subscribe to these messages in their JIRA account settings. >> >> > > > > > I >> >> > imagine >> >> > > > > most >> >> > > > > > of you already filter these messages out, so you may need to >> >> adjust >> >> > > your >> >> > > > > > filters slightly. >> >> > > > > > >> >> > > > > > A distant second is MTCGA messages, which are also >> >> > > > > > autogenerated >> >> > and >> >> > > not >> >> > > > > > informative for most readers of the channel, since they are >> >> > > > > > at >> >> best >> >> > > > > > targeted at a single committer and at worst flak
Last boarding call for ApacheCon NA/EU and Asia .... CFP closes in a week ...
Hi folks, I am writing to your project list as there have been submissions from your project to the IoT track in the past, we have integration modules for your project in PLC4X, you are listed as "IoT" category project, or I just thought your project would be a good match for an IoT related talk ;-) I have just checked and there haven't been submissions for the IoT Tracks on your project to (both or any of) the ApacheCon CFPs ... the CFP is closing soon, and we will not accept any talks after the deadline is passed (It was open long enough and I sent enough reminders to most of you) CFP ApacheCon NA/EU: https://www.apachecon.com/acah2021/cfp.html (Closing Monday, May 3rd, 2021 8:00 AM (UTC)) CFP ApacheCon Asia: https://apachecon.com/acasia2021/cfp.html (Closing Monday, May 3rd, 2021 8:00 AM (Beijing time - UTC +8)) Looking forward to some high-quality sumbissions. Chris
[MTCGA]: new failures in builds [5981843] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master GracefulShutdownTest.testThatExcludedNodeListWithinMetastoreCleanedUpAfterUpdatingFullMap https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-4426877320301610362&branch=%3Cdefault%3E&tab=testDetails No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 21:55:19 26-04-2021
[VOTE][EXTENSION] Release Apache Ignite performance-statistics-ext and spring-data-all-ext extensions 1.0.0 RC2
Dear Ignite Community, I have uploaded a release candidate of the following extension modules: performance-statistics-ext spring-data-ext spring-data-2.0-ext spring-data-2.2-ext spring-data-commons The release candidate of the performance-statistics-ext extension: https://dist.apache.org/repos/dist/dev/ignite/ignite-performance-statistics-ext/1.0.0-rc2/ The following staging can be used for testing: https://repository.apache.org/content/repositories/orgapacheignite-1513 Tags were created: ignite-performance-statistics-ext-1.0.0-rc2 https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=26fedfad954852a59f15bbd8f5b65708901f8cfe ignite-spring-data-ext-1.0.0-rc2 ignite-spring-data-2.2-ext-1.0.0-rc2 ignite-spring-data-2.0-ext-1.0.0-rc2 ignite-spring-data-commons-1.0.0-rc2 ignite-spring-data-all-ext-1.0.0-rc2 https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=471d7f388c7ad38fc651523f3d68f271235226bd RELEASE NOTES: https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=22f8d665c194ba2dfa6167354d97ad53d5ef206f;hb=c8de80ee14d1fb76d6cbb0b18513bb70b499c3cb DOCUMENTATION: Documentation of listed extensions was updated in the following issues: https://issues.apache.org/jira/issues/?filter=-1&jql=key%20in%20(IGNITE-14417%2CIGNITE-14398%2CIGNITE-14493) The vote is formal, see voting guidelines https://www.apache.org/foundation/voting.html +1 - to accept all the Apache Ignite performance-statistics-ext and spring-data-all-ext extensions 1.0.0-rc1 listed in the thread 0 - don't care either way -1 - DO NOT accept either of the Apache Ignite performance-statistics-ext and spring-data-all-ext extensions 1.0.0-rc1 (explain why) The vote will hold for 3 days and will end on April 29 2021 20:00 UTC https://www.timeanddate.com/countdown/generic?iso=20210429T20&p0=1440&font=cursive -- Best wishes, Amelchev Nikita
[MTCGA]: new failures in builds [5982724] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master [Missing Tests] https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MissingTests?branch=%3Cdefault%3E No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 05:25:22 27-04-2021
