Val,
> Basically, what I'm suggesting is to accept non-nullable as default
Sounds good for me. Then it should be clearly stated in code
guidelines and regular static analysis for this should be organized
from the beginning.
2021-12-21 20:35 GMT+03:00, Valentin Kulichenko :
> Ivan,
>
> I agree wi
The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.11.1.
Apache Ignite® is a Distributed Database For High-Performance
Computing With In-Memory Speed.
https://ignite.apache.org
This is an emergency release that fixes the log4j2 dependencies.
Please check the detail
Ivan,
I agree with you. Basically, what I'm suggesting is to accept non-nullable
as default, but if a parameter must be nullable for whatever reason, mark
it with the @Nullable annotation.
Regarding "a user can put anything there without much thinking": I
understand what you mean, but I believe t
Yes, please create an issue. I will think about updating the instructions
and using the latest file.
On Tue, Dec 21, 2021 at 7:56 PM Maxim Muzafarov wrote:
> Erlan,
>
> > Lastly, would you please change version 2.11 to 2.11.1 for the button
> from the header?
> >
> https://github.com/apache/igni
Erlan,
> Lastly, would you please change version 2.11 to 2.11.1 for the button from
> the header?
> https://github.com/apache/ignite-website/blob/master/_src/_components/header.pug
Can we also use the 'latest' file [1] version to pick up it instead of
manual updating the page 'header.pug' each t
May be just add instruction how to build site using docker? As for ignite
documentation?
вт, 21 дек. 2021 г. в 16:10, Maxim Muzafarov :
> Folks,
>
> Thank you for helping me. Sorry for the 'spam' from my side :-)
>
>
> I've reinstalled Node.js. The following version was installed 'Node.js
> v17.x
Folks,
Thank you for helping me. Sorry for the 'spam' from my side :-)
I've reinstalled Node.js. The following version was installed 'Node.js
v17.x' using this guide [1].
Now the error is the following:
mario@mario:~/IdeaProjects/ignite-website$ gulp
SyntaxError: Unexpected token ':'
at ESM
Erlan, thanks for stepping in. Could you please update the instruction once
Maxim succeeds with all the steps on his end? It's important that community
members such as Maxim know exactly how to work with the new website.
https://cwiki.apache.org/confluence/display/IGNITE/Website+Development#Website
Hi Maxim,
What version of node js version did you use?
On Tue, Dec 21, 2021 at 6:47 PM Maxim Muzafarov wrote:
> Folks,
>
>
> Building the website becomes more and more complicated :-)
> Can we update the documentation [1] with more details for the folks
> who are not familiar with node.js?
>
>
Folks,
Building the website becomes more and more complicated :-)
Can we update the documentation [1] with more details for the folks
who are not familiar with node.js?
Actually, I'm stuck on the error below with compiling the project.
However, it seems to me that node.js require ES modules that
Ops, yes, seems that we messed up with the releases dates. It originates
from the PUG files like this one:
https://github.com/apache/ignite-website/blob/master/_src/_components/download-binary.pug
Would you be able to correct the dates? We can find the dates in a previous
version of download.html:
Denis,
Thanks for the update.
I've just recently found that all releases on the download page [1]
have the same release date. Is it correct?
[1] https://ignite.apache.org/download.cgi
On Tue, 21 Dec 2021 at 14:47, Denis Magda wrote:
>
> Hi Maxim,
>
> Just a reminder that since the release of th
A new feedback has been added, go to bugyard.io to see all the details...
https://bugyard.io
A new feedback has been added
"Thanks you for contacting us " by sabelopaulos816
View feedback
https://app.bugyard.io/web/app/rycqZJDyY/f/61c14f1639632e001464046a
Hi Maxim,
Just a reminder that since the release of the new website, we need to
update the download.pug [1] file in case of a release and then generate the
HTML version following this updated instruction. If you have any questions,
please reach out to Erlan (CC-ed).
[1] https://github.com/apache/
Also, zookeeper ip finder depends on good old log4j 1.x
вт, 21 дек. 2021 г. в 13:32, Ivan Daschinsky :
> As for me, I am +1 for removing ZookeeperIpFinder from ignite-zookeeper.
>
>
> вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev :
>
>> Folks,
>>
>> What do you think about fixing vulnerability log
As for me, I am +1 for removing ZookeeperIpFinder from ignite-zookeeper.
вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev :
> Folks,
>
> What do you think about fixing vulnerability log4j dependencies in
> rest-http, zookeeper modules in 2.12?
>
> The issue is in progress and can be resolved in a fe
Folks,
What do you think about fixing vulnerability log4j dependencies in
rest-http, zookeeper modules in 2.12?
The issue is in progress and can be resolved in a few days. [1]
I suggest including it to the scope.
[1] https://issues.apache.org/jira/browse/IGNITE-13464
пт, 17 дек. 2021 г. в 16:2
Hello, Igniters!
Thanks to everyone. The vote is closed.
The emergency Apache Ignite 2.11.1 release (RC2) has been accepted.
I will continue on with the release.
5 - "+1" votes received and no "0", "-1" votes.
Here are the votes received:
- Ilya Kasnacheev (binding)
- Pavel Tupitsyn (binding)
18 matches
Mail list logo