Hi Igniters,
Inspired by a neighbor thread about PR checks [1]. It brought my
attention that now we have a neat Travis badge and a strange TC badge
which is not very useful from a first glance.
What do you think, is it ought to completely remove TC badge from readme?
[1]
https://lists.apache.or
Ivan Pavlukhin created IGNITE-12980:
---
Summary: Use Apache Ignite logo with registered trade mark symbol
in README.md
Key: IGNITE-12980
URL: https://issues.apache.org/jira/browse/IGNITE-12980
Project
Folks,
As you might know, not long ago Apache Ignite became a registered
trademark. I noticed that we still have (TM) symbol in
https://github.com/apache/ignite/blob/master/README.md
I prepared a ticket [1] and PR. I feel that the used approach might be
improved, but I tried to do my best in a la
Hi, Igniters!
I'd like to share a new small feature in AI [1].
Current rebalance logging does not allow you to quickly answer following
questions:
1)How long was the balance(divided by supplier)?
2)How many records and bytes per supplier were rebalanced?
3)How many times did rebalance restart?
Maxim,
Thanks again for doing great things!
Out of curiosity, could you please shed a light why there are 2 travis
checks for PR [1]? I am about checks named
continuous-integration/travis-ci/pr and
continuous-integration/travis-ci/push.
Best regards,
Ivan Pavlukhin
вс, 3 мая 2020 г. в 13:08, Pa
Pavel,
> I think this thread is a good opportunity to discuss commit message
> guidelines.
We had a thread about it recently [1].
[1]
https://lists.apache.org/thread.html/rde6e8258537704433286a60e1d0142485c25228a46561544d35b9704%40%3Cdev.ignite.apache.org%3E
Best regards,
Ivan Pavlukhin
пн,
Maxim Muzafarov created IGNITE-12981:
Summary: Snapshot operation fails on exchange if coordinator left
the cluster
Key: IGNITE-12981
URL: https://issues.apache.org/jira/browse/IGNITE-12981
Projec
Maxim Muzafarov created IGNITE-12982:
Summary: NullPointerException on TcpCommunicationMetricsListener
for some of the cases
Key: IGNITE-12982
URL: https://issues.apache.org/jira/browse/IGNITE-12982
Igniters,
I've spent a couple of days in debug mode and found that some of the
configured ExecutorServices of an Ignite instance completely hide
assertion errors without any logging and node killing. This may
violate some internal guarantees and hide serious errors.
Let's consider, for instance,
Ivan, thanks for the catch. Please go ahead and merge the changes.
-
Denis
On Mon, May 4, 2020 at 12:30 AM Ivan Pavlukhin wrote:
> Folks,
>
> As you might know, not long ago Apache Ignite became a registered
> trademark. I noticed that we still have (TM) symbol in
> https://github.com/apache/i
Denis,
Thank your for the review. Merged to master.
Best regards,
Ivan Pavlukhin
пн, 4 мая 2020 г. в 20:11, Denis Magda :
>
> Ivan, thanks for the catch. Please go ahead and merge the changes.
>
> -
> Denis
>
>
> On Mon, May 4, 2020 at 12:30 AM Ivan Pavlukhin wrote:
>
> > Folks,
> >
> > As you
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
12 matches
Mail list logo
