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 Cache (Restarts) 1
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E
No changes in the build
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
Hi,
Just ss a heads up, I added the button to the online docs template and
rebuilt the latest version & 3.0.0a docs.
Please let me know if you have any questions or suggestions.
Best,
Mauricio Stekl
On Fri, Aug 6, 2021 at 12:17 PM Denis Magda wrote:
> There is no such a way. Notifications
A new feedback has been added, go to bugyard.io to see all the details...
https://bugyard.io
A new feedback has been added
"Testing the new documentation feedback tool on the website. " by
mauriciostekl
View feedback
https://app.bugyard.io/web/app/rycqZJDyY/f/610d8fd8b6fe3f0014ecf92d
Hi, Dmitry. We also have released pyignite 0.5.1
пт, 6 авг. 2021 г. в 16:36, Dmitry Pavlov :
> Hi Igniters,
>
> It's time to submit ASF Board report, so, as usual, I encourage every
> community member to suggest some addition to that report.
>
> What was the most recognizable (releases,
There is no such a way. Notifications are always sent to an email address
used by a bugyard account. Anyway, I don’t see any harm in this - usually
you’ll get a 1-2 notifications a week. Plus, many more community members
prepare documentation for features they build these days, thus, it’s good
to
Is there an easy way to subscribe personally for such notifications? I
forsee complaints that the majority of developers are not interested
in documentation feedback notifications.
2021-08-04 12:40 GMT+03:00, Denis Magda :
> Nikita,
>
> We created a bugyard account for the Ignite community. I'm
Hi Igniters,
It's time to submit ASF Board report, so, as usual, I encourage every community
member to suggest some addition to that report.
What was the most recognizable (releases, decisions, etc) during past quarter,
since May (~ Ignite Summit):
Draft you can find at:
Hi, all!
It's a gentle reminder. There is a PR for the new Index API [1]. It was
approved by Alex Plekhanov. Does anybody want to review this API too? If
there won't be objections we're going to merge it Monday, 16th of August.
Thanks!
[1] https://github.com/apache/ignite/pull/9118
On Fri, May
Zhenya,
> But there is no restrictions from running ignite server nodes from some
other code with it`s own guava version seems we obtain fast path to jar
hell here?
I'm not sure if I fully understand your question, but it looks like we are
in this situation already, because we have some
Thank you for the reply, Courtney!
> We use Ignite entirely as a thick client and already have Guava version
conflicts from other projects
AFAIK and as Ivan wrote before, there are no plans of providing the thick
client functionality in Ignite 3, so this may not be an issue.
> Even Calcite
Alexander, first of all looks like Ivan Daschinsky approach about thin client
use only and shadow plugin are cover all Andrey Mashenkov listing problems.
But there is no restrictions from running ignite server nodes from some other
code with it`s own guava version seems we obtain fast path to
Zhenya,
My intentions are the following:
1. Remove some copy-pasted code (like the "bytecode" module or some utility
methods). Please see my original message for the links to the code.
2. Explicitly pin the Guava version to avoid conflicts in the runtime.
About allowing to use Guava in the
13 matches
Mail list logo
