I don't like git docs idea, it will require to follow whole
PR-review-process that requires long time. IMO it is odd work.
If readme.io provides review process, I suggest to keep it as-is.
чт, 2 нояб. 2017 г. в 9:57, Dmitriy Setrakyan :
> On Wed, Nov 1, 2017 at 11:27 PM, Vladimir Ozerov
> wrote:
Hi Pavel, thank you. Could you please do the same for this modules?
I can remove gitter but I am not sure about CI server links correctness.
чт, 2 нояб. 2017 г. в 9:38, Pavel Tupitsyn :
> Denis, Dmitry,
>
> Looks like you forgot
> https://github.com/apache/ignite/tree/master/modules/platforms/dot
Sure, done.
On Thu, Nov 2, 2017 at 10:10 AM, Dmitry Pavlov
wrote:
> Hi Pavel, thank you. Could you please do the same for this modules?
> I can remove gitter but I am not sure about CI server links correctness.
>
> чт, 2 нояб. 2017 г. в 9:38, Pavel Tupitsyn :
>
> > Denis, Dmitry,
> >
> > Looks l
Dmitry Karachentsev created IGNITE-6818:
---
Summary: In case of incoming communication connection ping the old
one if it's alive
Key: IGNITE-6818
URL: https://issues.apache.org/jira/browse/IGNITE-6818
Sergey Chugunov created IGNITE-6819:
---
Summary: Better test coverage for PagesList basic functionality
Key: IGNITE-6819
URL: https://issues.apache.org/jira/browse/IGNITE-6819
Project: Ignite
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/2971
IGNITE-6690 DiscoverySpi: Clientmode Ignite should not fail on handshake
errors
test fixes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gri
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2968
---
Alexey Goncharuk created IGNITE-6820:
Summary: Add data regions to data structures configuration
Key: IGNITE-6820
URL: https://issues.apache.org/jira/browse/IGNITE-6820
Project: Ignite
Is
Alexey Goncharuk created IGNITE-6821:
Summary: Add test for cross-cache transactions between in-memory
and persistent caches
Key: IGNITE-6821
URL: https://issues.apache.org/jira/browse/IGNITE-6821
Github user apopovgg closed the pull request at:
https://github.com/apache/ignite/pull/2971
---
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/2972
Ignite 8266 test failing
GridTcpCommunicationSpiConfigSelfTest.testLocalPortRange test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgai
Hello, Igniters.
I have removed deprecated metrics [1]. Please, review [2]. Tests look good
[3].
1. https://issues.apache.org/jira/browse/IGNITE-6679
2. https://reviews.ignite.apache.org/ignite/review/IGNT-CR-390
3.
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&tab=projectOver
Aleksey Chetaev created IGNITE-6822:
---
Summary: IgfsMapReduceExample raise exception in multi nodes run
Key: IGNITE-6822
URL: https://issues.apache.org/jira/browse/IGNITE-6822
Project: Ignite
Ksenia Rybakova created IGNITE-6823:
---
Summary: Sporadic Redis python and php examples failures
Key: IGNITE-6823
URL: https://issues.apache.org/jira/browse/IGNITE-6823
Project: Ignite
Issue
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2973
2.1.3-p6
For testing only.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.3-p6
Alternatively you can review
GitHub user kdudkov opened a pull request:
https://github.com/apache/ignite/pull/2974
Ignite 2.1.7.b1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.7.b1
Alternatively you can review and apply
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/2975
Ignite-6083
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite ignite-6083
Alternatively you can review and apply these changes as the
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/2848
---
Dmitriy,
Hello. Unfortunately, I am not sure that I fully understand your comments:
"..Is my understanding correct that GA Grid is a vertical component for
genetic algorithms? So far Ignite has been a horizontal product without any
vertical functionality. I personally would like to keep it t
Alexander Kalinin created IGNITE-6824:
-
Summary: Web Console: migrate from angularjs 1.5 to angular 1.6
Key: IGNITE-6824
URL: https://issues.apache.org/jira/browse/IGNITE-6824
Project: Ignite
Hi guys,
Yes, in my opinion genetic algorithms developed by Turik perfectly fit our ML
component as a separate package. Look, *ML* is a building block on top of
Ignite distributed storage and compute grid. Same is true about GA grid. So,
why don’t we merge GA into ML?
Nikita, Yuri and the rest
Nick, Vovan,
Have we really upgraded docker and the other images to 2.3?
—
Denis
> Begin forwarded message:
>
> From: bjason
> Subject: ignite 2.3.0 docker image contains 2.2.0 files.
> Date: November 2, 2017 at 3:37:34 PM PDT
> To: u...@ignite.apache.org
> Reply-To: u...@ignite.apache.org
>
Alexander Belyak created IGNITE-6825:
Summary: Unhandled interruption in GridH2Table
Key: IGNITE-6825
URL: https://issues.apache.org/jira/browse/IGNITE-6825
Project: Ignite
Issue Type: Bu
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2976
IGNITE-6825
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6825
Alternatively you can review and apply these
24 matches
Mail list logo
