GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/5493
IGNITE-10399 Fix inspection error.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10399
Alternatively
Sergey Antonov created IGNITE-10399:
---
Summary: Fix inspection failures
Key: IGNITE-10399
URL: https://issues.apache.org/jira/browse/IGNITE-10399
Project: Ignite
Issue Type: Bug
GitHub user dgovorukhin opened a pull request:
https://github.com/apache/ignite/pull/5494
Ignite-2.5.1-p152
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p152
Alternatively you can review
Hi Vladimir,
Regarding fault tolerance. It seems that it is not a problem for
edge-chasing approaches. A found deadlock is identified by a message
returned to a detection initiator with initiator's identifier. If
there is no deadlock then such message will not come. If some node
containing a
asfgit closed pull request #82: Ignite 9542 remove unused code
URL: https://github.com/apache/ignite-teamcity-bot/pull/82
This is an automated message from the Apache Git Service.
To respond to the message, please log on
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/5496
IGNITE-9980 Modify ./control.sh --cache idle_verify --dump print to dâ¦
â¦iff mode (user persistant only/user not-persistent only/system only)
cache
You can merge this pull request into a
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/5495
IGNITE-9275: WIP communication spi socket creation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-9275
Alternatively you
asfgit closed pull request #83: Ignite 9542 unit test for blockers detection
URL: https://github.com/apache/ignite-teamcity-bot/pull/83
This is an automated message from the Apache Git Service.
To respond to the message,
dspavlov opened a new pull request #83: Ignite 9542 unit test for blockers
detection
URL: https://github.com/apache/ignite-teamcity-bot/pull/83
This is an automated message from the Apache Git Service.
To respond to the
Dmitry,
Great, checked, now all things woks well
Hope that Igor made review for this PR
But what about Maps? Looks like different ticket? or it can be done in same
ticket scope?
пт, 23 нояб. 2018 г. в 23:58, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com>:
> Stepan,
>
> Sorry, I forgot to
dspavlov opened a new pull request #84: IGNITE-9542 new invocation history
implementation
URL: https://github.com/apache/ignite-teamcity-bot/pull/84
to provide separated base/current branch history for PR page
This is an
Stepan,
AFAIK Map type did always behave correctly on client side, as it does
now. This is a corresponding piece of my test suite:
```
def test_put_get_map(client):
cache = client.get_or_create_cache('test_map_cache')
cache.put(
'test_map',
(
12 matches
Mail list logo
