[MTCGA]: new failures in builds [5978497] 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. *New test failure in master ZookeeperDiscoveryCommunicationFailureTest.testDefaultCommunicationFailureResolver4 https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6616602384015824771=%3Cdefault%3E=testDetails Changes may lead to failure were done by - pavel tupitsyn https://ci.ignite.apache.org/viewModification.html?modId=923755 - 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 01:10:19 24-04-2021
CFP for ApacheCon 2021 closes in ONE WEEK
[You are receiving this because you're subscribed to one or more dev@ mailing lists for an Apache project, or the ApacheCon Announce list.] Time is running out to submit your talk for ApacheCon 2021. The Call for Presentations for ApacheCon @Home 2021, focused on Europe and North America time zones, closes May 3rd, and is at https://www.apachecon.com/acah2021/cfp.html The CFP for ApacheCon Asia, focused on Asia/Pacific time zones, is at https://apachecon.com/acasia2021/cfp.html and also closes on May 3rd. ApacheCon is our main event, featuring content from any and all of our projects, and is your best opportunity to get your project in front of the largest audience of enthusiasts. Please don't wait for the last minute. Get your talks in today! -- Rich Bowen, VP Conferences The Apache Software Foundation https://apachecon.com/ @apachecon
Re: [DISCUSSION] Documentation of thin clients (python, php, nodejs)
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: NodeJS thin client: full API
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: [DISCUSSION] Documentation of thin clients (python, php, nodejs)
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 >
Re: [VOTE][EXTENSION] Release Apache Ignite performance-statistics-ext, spring-data-all-ext and spring-tx-ext extensions 1.0.0 RC1
Petr,
Module names in settings of the suite [1] should be changed.
[1]
https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_OldRunAllTests?mode=builds#all-projects
чт, 22 апр. 2021 г. в 11:49, Petr Ivanov :
>
> Looks good.
>
>
> What suites are in question, these ones [1]?
>
>
>
> [1] https://ci.ignite.apache.org/project/IgniteExtensions_Tests
> > On 22 Apr 2021, at 10:42, Nikita Amelchev wrote:
> >
> > Hi, guys.
> >
> > I have prepared PR to fix module names [1, 2]. Could you take a look
> > and recheck TC integration, please?
> >
> > Note that module names in TC suites should be changed as well.
> >
> > [1] https://github.com/apache/ignite-extensions/pull/58
> > [2] https://issues.apache.org/jira/browse/IGNITE-14621
> >
> > чт, 22 апр. 2021 г. в 00:08, Nikita Amelchev :
> >
> >>
> >> I have created the issue to fix modules names:
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-14621
> >>
> >> ср, 21 апр. 2021 г. в 11:46, Nikita Amelchev :
> >>>
> >>> +1 to formalize extension modules names:
> >>> ignite-{directory-name}
> >>>
> >>> The release script has this issue too. It will work fine with that name.
> >>>
> >>> ср, 21 апр. 2021 г. в 10:37, Petr Ivanov :
>
> I checked the modules and there is misnaming issue which I think is
> critical to test integration automation on TC.
> Can we change maven module names sping-data-2.x-ext to align with
> directory name? Currently there is underscore in maven module name,
> which is hyphen in directory name.
>
>
> > On 21 Apr 2021, at 10:22, Nikita Amelchev wrote:
> >
> > +1 to postpone the spring-tx-ext extension release.
> >
> > So, the following extensions will be released now:
> >
> > spring-data-ext
> > spring-data-2.0-ext
> > spring-data-2.2-ext
> > spring-data-commons
> > performance-statistics-ext
> >
> > вт, 20 апр. 2021 г. в 14:49, Mikhail Petrov :
> >>
> >> Igniters,
> >>
> >> Changing the scope of Spring dependencies to "provided" in Ignite
> >> Spring
> >> extensions does not currently work as expected:
> >> some versions of Spring that a user can specify via maven configuration
> >> for Spring extensions may conflict with the hard-coded version of
> >> Spring
> >> dependencies that the ignite-spring module relies on.
> >>
> >> The issue mentioned above affects the Ignite Spring Transactions
> >> integration. And since this integration is included in the Ignite 2.10
> >> release, I suggest postponing the release of the Ignite Spring
> >> Transactions integration until the above issue is properly fixed.
> >>
> >> Any objections?
> >>
> >> On 16.04.2021 09:15, Ivan Daschinsky wrote:
> >>> -1 From me. There is an absence of NOTICE and LICENSE files in binary
> >>> package. Also, there is no source package. These is a violation of
> >>> apache
> >>> release policy [1]
> >>> [1] https://www.apache.org/legal/release-policy.html
> >>>
> >>> чт, 15 апр. 2021 г. в 23:23, Nikita Amelchev :
> >>>
> According to ASF release policy [1] non-PMC committers can sign
> artifacts:
>
> > all artifacts placed in their directory must be signed by a
> > committer,
> preferably by a PMC member.
>
> [1] https://www.apache.org/legal/release-policy.html
>
> чт, 15 апр. 2021 г. в 23:05, Dmitriy Pavlov :
> > My best guess that since PMCs have a binding vote in voting in
> > release, a
> > PMC member should sign binaries as well. And I suppose that in the
> > past
> > only PMC members were signing the release.
> >
> > Meanwhile, https://infra.apache.org/release-signing.html does not
> contain
> > any mention of PMC role and only committers are mentioned there. It
> > might be not an answer, since a lot of projects have PMC=Committer
> > and
> just
> > one election.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 15 апр. 2021 г. в 22:05, Ivan Daschinsky :
> >
> >> I'm sorry, but is it OK, that artifacts are signed with signature
> >> of
> >> non-PMC?
> >>
> >> чт, 15 апр. 2021 г. в 19:26, Nikita Amelchev
> >> :
> >>
> >>> 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
> >>> spring-tx-ext
> >>>
> >>> The release candidate of the performance-statistics-ext extension:
> >>>
> >>>
>
