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
I’m using Ignite IBinarizable raw serialization in Ignite v2.6 with C#
client.
I notice there is no support for unsigned short, int and long integer types
(both single values and arrays).
I also noticed that Decimal, DateTime and Guid read/write methods only
support nullable values.
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/4928
IGNITE-8870: Example of usage of encrypted cache.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-8870
Alternatively
GitHub user Max-Pudov opened a pull request:
https://github.com/apache/ignite/pull/4927
IGNITE-9818 Fix javadoc for annotation AffinityKeyMapped
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9818
Maxim Pudov created IGNITE-9818:
---
Summary: Fix javadoc for annotation AffinityKeyMapped which cannot
be applied to a method anymore
Key: IGNITE-9818
URL: https://issues.apache.org/jira/browse/IGNITE-9818
Nikolay Izhikov created IGNITE-9817:
---
Summary: Update documentation and examples for Spark SQL Table
Specification
Key: IGNITE-9817
URL: https://issues.apache.org/jira/browse/IGNITE-9817
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4551
---
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223397571
##
File path: ignite-tc-helper-web/src/main/webapp/js/testfails-2.1.js
##
@@ -328,7
I agree that such option is hard to explain and will complicate data
storage tuning (which is already not simple).
The problem is that we don't divide pages to overflow/non-overflow so
far. We need to see benchmark results first - there's a chance that
negative effects will be insignificant and
Hi Apache Ignite Enthusiasts,
I'm happy to announce a new post about Apache Ignite
https://www.gridgain.com/resources/blog/introduction-apacher-ignitetm-community-structure
- "Introduction to the Apache® Ignite™ community structure." This post is a
translated version of the Habr post. Thanks
Dmitriy Gladkikh created IGNITE-9816:
Summary: Add FailureHandler call on binary_meta error
Key: IGNITE-9816
URL: https://issues.apache.org/jira/browse/IGNITE-9816
Project: Ignite
Issue
Can we use this mode for overflow pages and do not use for normal entries
which fir a single page?
In general users try to avoid fine-grained tuning options, as they are very
complex to understand. We should try to avoid any new configuration options.
On Mon, Oct 8, 2018 at 5:51 PM Ivan Rakov
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223392275
##
File path:
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223387780
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223329723
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223397571
##
File path: ignite-tc-helper-web/src/main/webapp/js/testfails-2.1.js
##
@@ -328,7
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223332273
##
File path: ignite-tc-helper-web/src/main/webapp/js/testfails-2.1.js
##
@@ -355,59
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223332768
##
File path: ignite-tc-helper-web/src/main/webapp/js/testfails-2.1.js
##
@@ -355,59
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223387956
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223329487
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223395846
##
File path: ignite-tc-helper-web/src/main/webapp/js/testfails-2.1.js
##
@@ -214,14
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223388354
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/TriggerBuild.java
SomeFire commented on a change in pull request #27: IGNITE-9770 Add 'Re-run
possible blockers' button
URL: https://github.com/apache/ignite-teamcity-bot/pull/27#discussion_r223329630
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/BuildsInfo.java
Huge +1.
Page dirty flag is set in PageMemoryImpl#writeUnlockPage body. Caller
passes "markDirty=true" boolean flag if he assumes that page content may
have changed (dirty flag will be set even if page content remained
intact). Instead of this, we can dump page content to thread-local
buffer
Hi, Dmitrii!
Thanks for the feedback, I will definitely add these parameters to the
table.
By the way, it would be interesting to know how many people on average use
the TC Bot every day. Does this figure increase?
With the updated UI TC Bot has become more user-friendly. And I’m sure it
will
Hi Igniters,
I see this test is still failing. Who can address this?
Vladimir,
could you please step in?
Sincerely,
Dmitriy Pavlov
чт, 4 окт. 2018 г. в 2:01, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4886
---
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/4926
IGNITE-9694 Tests that read operations are not blocked by exchange
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4925
IGNITE-9814: JDK11: HadoopClassLoader#nativeLibraries fails because has
invalid assumption for ClassLoader type
You can merge this pull request into a Git repository by running:
$
Hi Igniters,
I'd like to share a case which was implemented in the previous version of
TC Bot. It is a kind of REST responses cache :
Response {
Long tsRefreshed; // timestamp of the last call to real service
List builds; // a huge list of builds, most times it is not
changed.
}
And it seems
Nikolay Izhikov created IGNITE-9815:
---
Summary: [TC Bot] Muted tests shouldn't considered as blocker
Key: IGNITE-9815
URL: https://issues.apache.org/jira/browse/IGNITE-9815
Project: Ignite
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/4924
IGNITE-9784 Automatically adjust max WAL history size
â¦mance drop
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Taras Ledkov created IGNITE-9814:
Summary: JDK11: HadoopClassLoader#nativeLibraries fails because
has invalid assumption for ClassLoader type
Key: IGNITE-9814
URL:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4918
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4834
---
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
Taras Ledkov created IGNITE-9813:
Summary: Unstablle behaviour in
org.apache.ignite.internal.processors.query.GridQueryProcessor#processSchemaOperationLocal
Key: IGNITE-9813
URL:
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4923
IGNITE-9726 (for mass run)
Just for test running on TC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Vyacheslav,
Thanks for links, I just wanted to remind these rules for all. Not all
Igniters use these rules in work.
On Mon, Oct 8, 2018 at 12:17 PM Vyacheslav Daradur
wrote:
> Hi Igniters,
>
> Dmitriy Govorukhin, the naming of GitHub PR [1] and Upsource review
> [2] already described in the
Hi Igniters,
Dmitriy Govorukhin, the naming of GitHub PR [1] and Upsource review
[2] already described in the wiki.
About the naming of Jira issue, I'd suggest adding rules in related
part [3] in the wiki.
[1]
Dmitry,
I fully support you!
It's never too much remind these simple rules. It's not obvious at first
glance but placing comment
'why' and 'how' particular JIRA issue was done will help much for the
further code investigations.
I'm not sure that pinning `link` to the TC result is a good
Github user daradurvs closed the pull request at:
https://github.com/apache/ignite/pull/4845
---
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r223283252
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r223284955
##
File path:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r223286978
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r223271317
##
File path:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r223279959
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r223286626
##
File path:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r223274311
##
File path:
SomeFire commented on a change in pull request #25: IGNITE-9645 [TC Bot] Add
comparison of failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25#discussion_r223279740
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
Ilya Kasnacheev created IGNITE-9812:
---
Summary: Explicit tests with expired SSL certificates
Key: IGNITE-9812
URL: https://issues.apache.org/jira/browse/IGNITE-9812
Project: Ignite
Issue
GitHub user antonovsergey93 reopened a pull request:
https://github.com/apache/ignite/pull/4837
IGNITE-8717
Cache configuration was moved to meta store. Verification of cache
configuration on node joining was added.
You can merge this pull request into a Git repository by running:
Github user antonovsergey93 closed the pull request at:
https://github.com/apache/ignite/pull/4837
---
Alexey Kuznetsov created IGNITE-9811:
Summary: Web Console: Do not block "Save" button in case some
inputs are invalid
Key: IGNITE-9811
URL: https://issues.apache.org/jira/browse/IGNITE-9811
Vladimir Ozerov created IGNITE-9810:
---
Summary: Potential SQL performance drop between AI 2.6 and AI 2.7
Key: IGNITE-9810
URL: https://issues.apache.org/jira/browse/IGNITE-9810
Project: Ignite
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4922
Ignite 9560 1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite IGNITE-9560_1
Alternatively you can review and apply these changes
56 matches
Mail list logo
