Re: [VOTE][RESULT] Release pyignite 0.6.1.rc1
Sorry, the mistake -- pyignite 0.6.1.rc0 пт, 17 февр. 2023 г. в 18:04, Ivan Daschinsky : > > 5 (4 binding) +1 votes (Nickolay Izhikov, Pavel Tupitsyn, Vladimir > Steshin, Slava Koptilin, Maxim Muzafarov) > No 0 votes > No -1 votes > > Therefore, the release is accepted unanimously. > Release binaries will be uploaded soon. The release will be announced soon. > > Thank you all! > -- Sincerely yours, Ivan Daschinskiy
[VOTE][RESULT] Release pyignite 0.6.1.rc1
5 (4 binding) +1 votes (Nickolay Izhikov, Pavel Tupitsyn, Vladimir Steshin, Slava Koptilin, Maxim Muzafarov) No 0 votes No -1 votes Therefore, the release is accepted unanimously. Release binaries will be uploaded soon. The release will be announced soon. Thank you all!
Re: [VOTE] Release bug fix release pyignite-0.6.1-rc0
The vote is closed. The results will be announced soon.
ср, 15 февр. 2023 г. в 14:10, Maxim Muzafarov :
> +1
>
> On Wed, 15 Feb 2023 at 11:17, Вячеслав Коптилин
> wrote:
> >
> > +1
> >
> >
> > ср, 15 февр. 2023 г. в 10:21, Ivan Daschinsky :
> >
> > > Dear Igniters!
> > >
> > > This is a patch release that contains an important fix for users of
> > > pyignite
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-18788
> > >
> > >
> > > Release candidate binaries for subj are uploaded and ready for vote
> > > You can find them here:
> > > https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.1-rc0
> > >
> > > If you follow the link above, you will find source packages (*.tar.gz
> and
> > > *.zip)
> > > and binary packages (wheels) for windows (amd64), linux (x86_64) amd
> mac os
> > > (x86_64)
> > > for pythons 37, 38, 39, 310 and 311. Also, there are sha512 and gpg
> > > signatures.
> > > Code signing keys can be found here --
> https://downloads.apache.org/ignite
> > > /KEYS
> > > Here you can find instructions how to verify packages
> > > https://www.apache.org/info/verification.html
> > >
> > > You can install binary package for specific version of python using pip
> > > For example do this on linux for python 3.8
> > > >> pip install
> > >
> > >
> pyignite-0.6.1-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
> > >
> > > You can build and install package from source using this command:
> > > >> pip install pyignite-0.6.1.zip
> > > You can build wheel on your platform using this command:
> > > >> pip wheel --no-deps pyignite-0.6.1.zip
> > >
> > > For building C module, you should have python headers and C compiler
> > > installed.
> > > (i.e. for ubuntu sudo apt install build-essential python3-dev)
> > > In Mac OS X xcode-tools and python from homebrew are the best option.
> > >
> > > In order to check whether C module works, use following:
> > > >> from pyignite import _cutils
> > > >> print(_cutils.hashcode('test'))
> > > >> 3556498
> > >
> > > You can find documentation here:
> > >
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.6.1.rc0/
> > >
> > > You can find examples here (to check them, you should start ignite
> > > locally):
> > >
> > >
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.6.1.rc0/examples.html
> > > Also, examples can be found in source archive in examples subfolder.
> > > docker-compose.yml is supplied in order to start ignite quickly. (Use
> > > `docker-compose up -d` to start 3 nodes cluster and `docker-compose
> > > down` to shut down it)
> > >
> > > Release notes:
> > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=86448e9ce51d7223ac49cf4f95da70d3d365e8c1;hb=0d86f44e86270f4d578afbce41aa2d6c424d2615
> > >
> > > Git release tag was created:
> > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=b0ce094d7a2db3fb07471be7b37ff9edab4180a8
> > >
> > > The vote is formal, see voting guidelines
> > > https://www.apache.org/foundation/voting.html
> > >
> > > +1 - to accept pyignite-0.6.1-rc0
> > > 0 - don't care either way
> > > -1 - DO NOT accept pyignite-0.6.1-rc0
> > >
> > > The vote finishes at 02/17/2021 15:00 UTC
> > >
> > > --
> > > Sincerely yours, Ivan Daschinskiy
> > >
>
--
Sincerely yours, Ivan Daschinskiy
Re: [DISCUSSION] Add additional 3rd party libraries to Ignite 3
Hi Ivan, I'm ok to add reactive-streams.jar, because it contains just interfaces that 1:1 java-flow API and FlowAdapter to convert JDK <-> ReactiveStreams interfaces. The interfaces available in JDK >= 9 java.util.concurrent.Flow, are 1:1 > semantically equivalent to their respective Reactive Streams counterparts. > This means that there will be a migratory period, while libraries move to > adopt the new types in the JDK, however this period is expected to be short > - due to the full semantic equivalence of the libraries, as well as the > Reactive Streams <-> Flow adapter library as well as a TCK compatible > directly with the JDK Flow types. However, Project-reactor dependency (e.g. reactor.core.publisher.Flux) is what we prefer to avoid or 'shadow' somehow. On Fri, Feb 17, 2023 at 10:49 AM Ivan Gagarkin wrote: > There is a PR https://github.com/apache/ignite-3/pull/1569 > > On Fri, Feb 17, 2023 at 11:47 AM Ivan Gagarkin > wrote: > > > The wrong link is above. It returns > > > https://www.reactive-streams.org/reactive-streams-1.0.3-javadoc/org/reactivestreams/Publisher.html > > > > On Fri, Feb 17, 2023 at 11:45 AM Ivan Gagarkin > > wrote: > > > >> We have to add reactor because we should implement > >> > https://github.com/micronaut-projects/micronaut-security/blob/master/security/src/main/java/io/micronaut/security/authentication/AuthenticationProvider.java > >> which returns > >> > https://micronaut-projects.github.io/micronaut-security/2.4.0/api/io/micronaut/security/authentication/AuthenticationProvider.html > . > >> I don't see any implementations in the project right now. > >> > >> On Fri, Feb 3, 2023 at 6:18 PM Михаил Початкин > > >> wrote: > >> > >>> Hi, Ivan. > >>> > >>> I don't see any problems with adding *micronaut-security* in the > context > >>> of > >>> the IGNITE-18575 epic of security implementation. Moreover, we already > >>> have > >>> several micronaut modules in dependencies (micronaut-inject, > >>> micronaut-runtime, micronaut-validation, micronaut-http, etc) and I > think > >>> that we should not deviate from a single ecosystem. I would also like > to > >>> see the answer to Alexander's question about the reactor dependency. > >>> > >>> Thanks! > >>> > >>> пт, 3 февр. 2023 г. в 12:11, Aleksandr Pakhomov : > >>> > >>> > Hi Ivan, > >>> > > >>> > Why do we add reactor dependency? The Ignite 3 codebase > >>> > uses java async API. Just wonder to know it we could escape > >>> > the usage of third party async libraries. > >>> > > >>> > -- > >>> > Best regards, > >>> > Aleksandr > >>> > > >>> > > On 3 Feb 2023, at 10:51, Ivan Gagarkin > >>> wrote: > >>> > > > >>> > > I'd like to add a few 3rd party libraries to Ignite 3 > >>> > > > >>> > > 1. Micronaut Security > >>> > > > >>> https://micronaut-projects.github.io/micronaut-security/latest/guide/ > >>> > > 2. Micronaut Reactor > >>> > > > >>> https://micronaut-projects.github.io/micronaut-reactor/latest/guide/ > >>> > > > >>> > > We have to have them for authentication and authorization in the > >>> REST. > >>> > > https://issues.apache.org/jira/browse/IGNITE-18576 > >>> > > > >>> > > WDYT? Any objections? Also, comments on IEP-87 are welcomed. > >>> > > -- > >>> > > Best Regards, Ivan > >>> > > >>> > > >>> > >>> -- > >>> С уважением, > >>> Початкин Михаил. > >>> > >> > >> > >> -- > >> Best Regards, Ivan > >> > > > > > > -- > > Best Regards, Ivan > > > > > -- > Best Regards, Ivan > -- Best regards, Andrey V. Mashenkov
