Hello, Igniters!
Release pyignite-0.5.0-rc1 has been accepted.
The votes received:
3 "+1" binding votes
4 "+1" votes
There are no "+0" or "-1"
Here the votes received:
- Igor Sapego (binding) +1
- Pavel Tupitsyn (binding) +1
- Nickolay Izhikov (binding) +1
- Ivan Daschinsky +1
- Alexander Surko
+1 (binding)
> 18 июня 2021 г., в 14:41, Shishkov Ilya написал(а):
>
>> in-memory cluster 3x servers
>
> I forgot to write about the Ignite version: checked with Ignite-2.10 binary
> release.
>
> пт, 18 июн. 2021 г. в 14:37, Shishkov Ilya :
>
>> +1 from me.
>>
>> Checked on Win10:
>> - Pytho
> in-memory cluster 3x servers
I forgot to write about the Ignite version: checked with Ignite-2.10 binary
release.
пт, 18 июн. 2021 г. в 14:37, Shishkov Ilya :
> +1 from me.
>
> Checked on Win10:
> - Python 3.8.8
> - pip install pyignite-0.5.0-cp38-cp38-win_amd64.whl
> - in-memory cluster 3x se
+1 from me.
Checked on Win10:
- Python 3.8.8
- pip install pyignite-0.5.0-cp38-cp38-win_amd64.whl
- in-memory cluster 3x servers
All examples from 'pyignite-0.5.0.zip' work without errors. Errors in
server logs not found.
Also checked for correct reconnection in the failover example.
пт, 18 июн.
You’re right, it’s documented and works as described. My bad.
> On 18 Jun 2021, at 11:24, Igor Sapego wrote:
>
> Well,
>
> This behaviour maybe is not obvious, but it seems to be safe and
> should not cause user issues. On the other hand, if we change this
> behavior now, it may lead to implici
Well,
This behaviour maybe is not obvious, but it seems to be safe and
should not cause user issues. On the other hand, if we change this
behavior now, it may lead to implicit disable of SSL for users that
updated their client which seems more dangerous to me.
So I'd keep the current behaviour.
I suppose that we should not cancel this release, despite the fact that
this is not obvious behaviour. This is not a regression, this behaviour is
documented and this behaviour lasts for few years. Lets remove it, if the
majority are against it, but in the next release.
пт, 18 июн. 2021 г. в 13:08
>> we explicitly set use_ssl=True.
Sorry, typo -- implicitly
пт, 18 июн. 2021 г. в 12:59, Ivan Daschinsky :
> AHA! I see, this is not a bug -- this is a feature. If you pass username
> and password, we explicitly set use_ssl=True. So if your cluster is
> configured without ssl but with authentic
And this behavior is thoroughly described in docs
https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/examples.html#password-authentication
пт, 18 июн. 2021 г. в 12:59, Ivan Daschinsky :
> AHA! I see, this is not a bug -- this is a feature. If you pass username
> and password, w
AHA! I see, this is not a bug -- this is a feature. If you pass username
and password, we explicitly set use_ssl=True. So if your cluster is
configured without ssl but with authentication,
you should explicitly pass use_ssl=False.
This behaviour is from old version and I suppose it is correct. Who
Just rechecked test on release branch, add extra check with cluster
activation and putting some data -- everything works ok. Authentication
enabled, persistence enabled,
with and without ssl. Could you please provide you ignite config and your
code.
пт, 18 июн. 2021 г. в 12:46, Ivan Daschinsky :
There is a test for it.
пт, 18 июн. 2021 г. в 12:30, Stephen Darlington <
stephen.darling...@gridgain.com>:
> Oh… can someone else check this: it appears that authenticated connections
> fail.
>
> With Ignite 2.10 the connection times-out:
>
> [10:28:58,015][WARNING][grid-timeout-worker-#22][Clie
Oh… can someone else check this: it appears that authenticated connections fail.
With Ignite 2.10 the connection times-out:
[10:28:58,015][WARNING][grid-timeout-worker-#22][ClientListenerNioListener]
Unable to perform handshake within timeout [timeout=1,
remoteAddr=/127.0.0.1:54044]
Didn’t
+1
Checked on macOS, played with the new expiry APIs and a bunch of
thefundamentals.
> On 17 Jun 2021, at 12:46, Pavel Tupitsyn wrote:
>
> +1
>
> Checked pip install from tar.gz on Python 3.8 on Ubuntu 20.04, ran some of
> the examples.
>
> On Thu, Jun 17, 2021 at 2:32 PM Igor Sapego wrote:
+ 1 for me.
Checked for Mac OS
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
+1
Checked pip install from tar.gz on Python 3.8 on Ubuntu 20.04, ran some of
the examples.
On Thu, Jun 17, 2021 at 2:32 PM Igor Sapego wrote:
> +1 from me
>
> Best Regards,
> Igor
>
>
> On Thu, Jun 17, 2021 at 12:10 PM Ivan Daschinsky
> wrote:
>
> > +1 From me
> > Checked on Ubuntu 20.04 and
+1 from me
Best Regards,
Igor
On Thu, Jun 17, 2021 at 12:10 PM Ivan Daschinsky
wrote:
> +1 From me
> Checked on Ubuntu 20.04 and windows 10
> 1. Installation from wheels for pythons 3.6 3.7 3.8 3.9
> 2. Native module work
> 3. Examples
>
> Checked on Ubuntu 20.04 building from source package a
+1 From me
Checked on Ubuntu 20.04 and windows 10
1. Installation from wheels for pythons 3.6 3.7 3.8 3.9
2. Native module work
3. Examples
Checked on Ubuntu 20.04 building from source package and correct work of
result package.
Checked all sha256 checksums and gpg signatures.
Let's extend votin
The vote will end at June, 17 15:00 UTC.
ср, 16 июн. 2021 г. в 17:33, Ivan Daschinsky :
>
> Dear Igniters!
>
> 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.5.0-rc1
>
> If you follow the link
Dear Igniters!
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.5.0-rc1
If you follow the link above, you will find source package (*.tar.gz and *.zip)
and binary packages (wheels) for windows (amd
20 matches
Mail list logo
