[MTCGA]: new failures in builds [5644497] needs to be handled
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 your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master Platform C++ CMake (Win x64 | Release) https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_WiPPlatformCCMakeWinX64Release?branch=%3Cdefault%3E Changes may lead to failure were done by - igor seliverstov https://ci.ignite.apache.org/viewModification.html?modId=908121 - alexey zinoviev https://ci.ignite.apache.org/viewModification.html?modId=908120 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 07:11:19 07-10-2020
[MTCGA]: new failures in builds [5644466] needs to be handled
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 your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master Platform .NET (Long Running) https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetLongRunning?branch=%3Cdefault%3E Changes may lead to failure were done by - igor seliverstov https://ci.ignite.apache.org/viewModification.html?modId=908121 - alexey zinoviev https://ci.ignite.apache.org/viewModification.html?modId=908120 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 06:41:20 07-10-2020
[jira] [Created] (IGNITE-13539) Remove references for migrated Ignite Extensions modules from the assembly and osgi-karaf
Saikat Maitra created IGNITE-13539: -- Summary: Remove references for migrated Ignite Extensions modules from the assembly and osgi-karaf Key: IGNITE-13539 URL: https://issues.apache.org/jira/browse/IGNITE-13539 Project: Ignite Issue Type: Sub-task Reporter: Saikat Maitra Remove references for migrated Ignite Extensions modules from the assembly/dependencies-apache-ignite-slim.xml and assembly/lib/Readme.txt Also, for migrated Ignite Extensions modules the modules/osgi-karaf/src/main/resources/features.xml should refer to ignite-ext now. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]
Hi Alexey,
Thank you for your email. Yes, I can certainly use help in the release
process. I am thinking around the month of Nov for the releases after
the In-Memory Computing Summit Virtual 2020 but any of the module can be
released before that timeline. I have a tech talk coming up on Oct 28 and I
may get a little occupied for the same.
https://www.imcsummit.org/2020/virtual/agenda/schedule/day-1
Also, I have not created any ticket for the OSGI module, please feel free
to create a ticket and I can help with the migration.
Regards,
Saikat
On Tue, Oct 6, 2020 at 9:19 AM Alexey Goncharuk
wrote:
> Saikat,
>
> The plan sounds good to me! Do you have an idea for the timeline of the
> module releases? Let me know if I can help in any way.
>
> Also, I was looking into the modularization IEP and noticed that OSGI
> module is discussed to be moved to the extensions, but there is no
> corresponding ticket. Should I create one? I will be happy to help with
> moving this module to extensions.
>
> вт, 29 сент. 2020 г. в 03:03, Saikat Maitra :
>
>> Hi Alexey,
>>
>> All the modules as planned in IEP-36
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36:+Modularization
>> are migrated to ignite-extensions repository.
>>
>> We can definitely plan to release ignite-extensions modules.
>>
>> I have a pending PR related to the kafka module and the PR is in review
>> https://github.com/apache/ignite/pull/8222 but its corresponding PR has
>> been merged in ignite-extensions repository.
>>
>> My thoughts / action items for the migration efforts and releases were
>> as follows:
>>
>> 1. Merge the changes for https://github.com/apache/ignite/pull/8222
>> 2. Fix the upload nightly packages task for ignite-core to help fix the
>> travis build failure in ignite-extensions repository.
>> 3. Review and update the README.md files for the ignite-extensions
>> modules as required.
>> 4. Update the docs for ignite-extensions modules in ignite-website.
>> 5. Release each module separately and share updates.
>>
>> Please let me know if you have feedback.
>>
>> Regards,
>> Saikat
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Sep 28, 2020 at 7:36 AM Petr Ivanov wrote:
>>
>>> It seems that gitbox.apache.org is not available on CI/CD.
>>>
>>> I will try to update VCS to GitHub.
>>>
>>>
>>>
>>>
>>>
>>> > On 28 Sep 2020, at 14:07, Alex Plehanov
>>> wrote:
>>> >
>>> > Guys,
>>> >
>>> > I've tried to build release candidate using TC [1]. But:
>>> > 1. I can't choose a branch in this TC task (there is no such field).
>>> > 2. On the "default" branch I got an error: Failed to collect changes,
>>> > error: List remote refs failed:
>>> > org.apache.http.conn.ConnectTimeoutException: Connect to
>>> > gitbox.apache.org:443 [gitbox.apache.org/52.202.80.70] failed: connect
>>> > timed out, VCS root: "GitBox [asf/ignite]" {instance id=300, parent
>>> > internal id=74, parent id=GitBoxAsfIgnite, description: "
>>> > https://gitbox.apache.org/repos/asf/ignite.git#refs/heads/master"}
>>> >
>>> > Is there some problem with this TC task? What am I doing wrong?
>>> >
>>> > [1] :
>>> >
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild
>>> >
>>> > пн, 28 сент. 2020 г. в 13:15, Alexey Goncharuk <
>>> alexey.goncha...@gmail.com>:
>>> >
>>> >> Saikat, Nikolay,
>>> >>
>>> >> We have migrated a bunch of modules to ignite-extensions recently.
>>> Given
>>> >> that these modules will not be available in Ignite 2.9 anymore (will
>>> >> they?), should we also plan to release the extensions?
>>> >>
>>> >> ср, 23 сент. 2020 г. в 21:49, Alex Plehanov >> >:
>>> >>
>>> >>> Igniters,
>>> >>>
>>> >>> I've prepared release notes for the 2.9 release [1]. Can anyone
>>> review
>>> >> it,
>>> >>> please?
>>> >>>
>>> >>> [1]: https://github.com/apache/ignite/pull/8273
>>> >>>
>>> >>> вт, 22 сент. 2020 г. в 09:39, Alex Plehanov >> >:
>>> >>>
>>> Guys,
>>>
>>> I've filled the ticket with reproducer [1] for the discovery bug.
>>> This
>>> >>> bug
>>> caused by [2] ticket. We discussed with Vladimir Steshin privately
>>> and
>>> decided to revert this ticket. I will do it today (after TC bot
>>> visa)
>>> >> if
>>> there are no objections.
>>>
>>> [1]: https://issues.apache.org/jira/browse/IGNITE-13465
>>> [2]: https://issues.apache.org/jira/browse/IGNITE-13134
>>>
>>> пн, 21 сент. 2020 г. в 11:08, Alex Plehanov <
>>> plehanov.a...@gmail.com>:
>>>
>>> > Guys,
>>> >
>>> > During internal testing, we've found a critical bug with
>>> > discovery (cluster falls apart if two nodes segmented
>>> sequentially).
>>> >>> This
>>> > problem is not reproduced in 2.8.1. I think we should fix it
>>> > before release. Under investigation now. I'll let you know when we
>>> get
>>> > something.
>>> >
>>> > чт, 17 сент. 2020 г. в 00:51, Andrey Gura :
>>> >
>>> >>> So what do you think? Should we proceed with a 'hacked' version
>>> of
>>> >>> the
[jira] [Created] (IGNITE-13538) Ignite Docs: table missing horizontal scroll bar
YuJue Li created IGNITE-13538: - Summary: Ignite Docs: table missing horizontal scroll bar Key: IGNITE-13538 URL: https://issues.apache.org/jira/browse/IGNITE-13538 Project: Ignite Issue Type: Improvement Components: documentation Affects Versions: 2.9 Reporter: YuJue Li Fix For: 2.10 Attachments: image-2020-10-07-09-01-09-803.png [https://ignite.apache.org/docs/latest/clustering/network-configuration] !image-2020-10-07-09-01-09-803.png! If the table is wide, the content on the right will not be visible -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13537) Ignite Docs:codeblock (tabs) component appearance improvement
YuJue Li created IGNITE-13537: - Summary: Ignite Docs:codeblock (tabs) component appearance improvement Key: IGNITE-13537 URL: https://issues.apache.org/jira/browse/IGNITE-13537 Project: Ignite Issue Type: Improvement Components: documentation Affects Versions: 2.9 Reporter: YuJue Li Fix For: 2.10 about code block,see: [https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment] !6ccIXycaAwAAAIDfgKCMF7Qqk PNRF7DRGMbX Hl7XnBAQAAAOCfRVDGW9qmUlmWKsvq35xoDAC iaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAICBoAwAgIGgDACAgaAMAIDhf3Y0NOKTdnGDAElFTkSuQmCC! >From this screenshot, the content of code block is mixed with the doc body. We >don't know where the boundary of code block is. And the original readme.io The codeblock looks like this: !8BrzjYPW22CXEASUVORK5CYII=! It's not just the highlighted code, it has a gray background as a whole. I know that if the content of codeblock(tabs) is a code snippet, it has a background color. If it's a markdown text, it's not. In other words, the background color is the background color of the code snippet, not the background color of codeblock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[MTCGA]: new failures in builds [5644351] needs to be handled
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 your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New test failure in master CommandLinePrintPropertiesTest.testPrintProperties https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3391612310542283011=%3Cdefault%3E=testDetails Changes may lead to failure were done by - igor seliverstov https://ci.ignite.apache.org/viewModification.html?modId=908121 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 02:56:23 07-10-2020
[jira] [Created] (IGNITE-13536) .NET: Child processes become zombies when persistence is used with direct-io on Linux
Pavel Tupitsyn created IGNITE-13536: --- Summary: .NET: Child processes become zombies when persistence is used with direct-io on Linux Key: IGNITE-13536 URL: https://issues.apache.org/jira/browse/IGNITE-13536 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 2.8 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.10 Attachments: IgnitePersistenceProcessHangTest.csproj, Program.cs After using Ignite with direct-io optional module and persistence enabled, user code hangs when trying to kill a child process and wait for it to exit using base class library classes (Process). See attached reproducer: * Copy .cs and .csproj files to a folder * dotnet run The program hangs forever on the last line, and the child process becomes a zombie (defunct). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[MTCGA]: new failures in builds [5643876] needs to be handled
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-nightly Disk Page Compressions https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_DiskPageCompressions?branch=%3Cdefault%3E No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 22:26:23 06-10-2020
[jira] [Created] (IGNITE-13535) Support cluster snapshot security permissions
Maxim Muzafarov created IGNITE-13535: Summary: Support cluster snapshot security permissions Key: IGNITE-13535 URL: https://issues.apache.org/jira/browse/IGNITE-13535 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Need to add a capability to specify permissions to allow/disallow executions of cluster snapshot operation. The following permissions should be added to the SecurityPermission enum: - ADMIN_SNAPSHOT_OPS - for creating/cancelling snapshot opreation -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]
Saikat,
The plan sounds good to me! Do you have an idea for the timeline of the
module releases? Let me know if I can help in any way.
Also, I was looking into the modularization IEP and noticed that OSGI
module is discussed to be moved to the extensions, but there is no
corresponding ticket. Should I create one? I will be happy to help with
moving this module to extensions.
вт, 29 сент. 2020 г. в 03:03, Saikat Maitra :
> Hi Alexey,
>
> All the modules as planned in IEP-36
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36:+Modularization
> are migrated to ignite-extensions repository.
>
> We can definitely plan to release ignite-extensions modules.
>
> I have a pending PR related to the kafka module and the PR is in review
> https://github.com/apache/ignite/pull/8222 but its corresponding PR has
> been merged in ignite-extensions repository.
>
> My thoughts / action items for the migration efforts and releases were
> as follows:
>
> 1. Merge the changes for https://github.com/apache/ignite/pull/8222
> 2. Fix the upload nightly packages task for ignite-core to help fix the
> travis build failure in ignite-extensions repository.
> 3. Review and update the README.md files for the ignite-extensions modules
> as required.
> 4. Update the docs for ignite-extensions modules in ignite-website.
> 5. Release each module separately and share updates.
>
> Please let me know if you have feedback.
>
> Regards,
> Saikat
>
>
>
>
>
>
>
>
> On Mon, Sep 28, 2020 at 7:36 AM Petr Ivanov wrote:
>
>> It seems that gitbox.apache.org is not available on CI/CD.
>>
>> I will try to update VCS to GitHub.
>>
>>
>>
>>
>>
>> > On 28 Sep 2020, at 14:07, Alex Plehanov
>> wrote:
>> >
>> > Guys,
>> >
>> > I've tried to build release candidate using TC [1]. But:
>> > 1. I can't choose a branch in this TC task (there is no such field).
>> > 2. On the "default" branch I got an error: Failed to collect changes,
>> > error: List remote refs failed:
>> > org.apache.http.conn.ConnectTimeoutException: Connect to
>> > gitbox.apache.org:443 [gitbox.apache.org/52.202.80.70] failed: connect
>> > timed out, VCS root: "GitBox [asf/ignite]" {instance id=300, parent
>> > internal id=74, parent id=GitBoxAsfIgnite, description: "
>> > https://gitbox.apache.org/repos/asf/ignite.git#refs/heads/master"}
>> >
>> > Is there some problem with this TC task? What am I doing wrong?
>> >
>> > [1] :
>> >
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild
>> >
>> > пн, 28 сент. 2020 г. в 13:15, Alexey Goncharuk <
>> alexey.goncha...@gmail.com>:
>> >
>> >> Saikat, Nikolay,
>> >>
>> >> We have migrated a bunch of modules to ignite-extensions recently.
>> Given
>> >> that these modules will not be available in Ignite 2.9 anymore (will
>> >> they?), should we also plan to release the extensions?
>> >>
>> >> ср, 23 сент. 2020 г. в 21:49, Alex Plehanov :
>> >>
>> >>> Igniters,
>> >>>
>> >>> I've prepared release notes for the 2.9 release [1]. Can anyone review
>> >> it,
>> >>> please?
>> >>>
>> >>> [1]: https://github.com/apache/ignite/pull/8273
>> >>>
>> >>> вт, 22 сент. 2020 г. в 09:39, Alex Plehanov > >:
>> >>>
>> Guys,
>>
>> I've filled the ticket with reproducer [1] for the discovery bug.
>> This
>> >>> bug
>> caused by [2] ticket. We discussed with Vladimir Steshin privately
>> and
>> decided to revert this ticket. I will do it today (after TC bot visa)
>> >> if
>> there are no objections.
>>
>> [1]: https://issues.apache.org/jira/browse/IGNITE-13465
>> [2]: https://issues.apache.org/jira/browse/IGNITE-13134
>>
>> пн, 21 сент. 2020 г. в 11:08, Alex Plehanov > >:
>>
>> > Guys,
>> >
>> > During internal testing, we've found a critical bug with
>> > discovery (cluster falls apart if two nodes segmented sequentially).
>> >>> This
>> > problem is not reproduced in 2.8.1. I think we should fix it
>> > before release. Under investigation now. I'll let you know when we
>> get
>> > something.
>> >
>> > чт, 17 сент. 2020 г. в 00:51, Andrey Gura :
>> >
>> >>> So what do you think? Should we proceed with a 'hacked' version of
>> >>> the
>> >> message factory in 2.9 and go for the runtime message generation in
>> >>> later
>> >> release, or keep the code clean and fix the regression in the next
>> >>> releases?
>> >>> Andrey, can you take a look at my change? I think it is fairly
>> >> straightforward and does not change the semantics, just skips the
>> >>> factory
>> >> closures for certain messages.
>> >>
>> >> IMHO 2.5% isn't too much especially because it isn't actual for all
>> >> workloads (I didn't get any significant drops during benchmarking).
>> >> So
>> >> I prefer the runtime generation in later releases.
>> >>
>> >> On Mon, Sep 14, 2020 at 12:41 PM Alexey Goncharuk
>> >> wrote:
>> >>>
>> >>> Alexey, Andrey, Igniters,
>> >>>
>> >>> So what do
[jira] [Created] (IGNITE-13534) Using a Deprecated method and uninformative message in console
Ilya Kazakov created IGNITE-13534:
-
Summary: Using a Deprecated method and uninformative message in
console
Key: IGNITE-13534
URL: https://issues.apache.org/jira/browse/IGNITE-13534
Project: Ignite
Issue Type: Improvement
Reporter: Ilya Kazakov
When cluster started in INACTIVE status in console writes uninformative message:
{code:java}
>>> Ignite cluster is not active (limited functionality available). Use
>>> control.(sh|bat) script or IgniteCluster interface to activate.{code}
This message contains two words "active" and not contain word "state".
>From this message, users try use deprecated IgniteCluster.active(boolean
>active), but need to use IgniteCluster.state(ClusterState newState)
Also there are 3 calls of this deprecated method IgniteCluster.active in
IgniteKernal.class
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Security issue with control.sh and ignite.sh
Hello, Igniters! I recently got my eye on the fact that we have JMX enabled by default and it's configured in a very insecure way. Our default JMX parameters are authenticate=false and ssl=false. I propose removing default configuration of JMX altogether, as user must *consciously* and carefully configure such dangerous things. I created an issue (https://issues.apache.org/jira/browse/IGNITE-13478) and pull request for those changes (https://github.com/apache/ignite/pull/8304). Cheers, Sam.
Re: [MTCGA]: new failures in builds [5643882] needs to be handled
Wow, I've got a Files with unapproved licenses: docs/_config.yml docs/_plugins/asciidoctor-extensions.rb docs/_includes/right-nav.html docs/_includes/left-nav.html docs/_includes/header.html docs/_includes/toc.html docs/_includes/section-toc.html docs/_includes/copyright.html docs/_includes/footer.html docs/assets/js/page-nav.js docs/assets/js/code-tabs.js docs/assets/js/top-navigation.js docs/assets/js/docs-menu.js docs/assets/js/code-copy-to-clipboard.js docs/assets/js/jquery.swiftype.autocomplete.js docs/assets/js/index.js docs/assets/js/anchor.min.js docs/assets/css/styles.scss docs/assets/css/docs.scss docs/assets/css/asciidoc-pygments.css docs/assets/images/github-gray.svg docs/assets/images/left-nav-arrow.svg docs/assets/images/lines-bg-3.svg docs/assets/images/checkmark-green.svg docs/assets/images/apple-blob.svg docs/assets/images/feature-fast.svg docs/assets/images/search.svg docs/assets/images/glowing-box.svg docs/assets/images/scala.svg docs/assets/images/violent-blob.svg docs/assets/images/feature-easy-installation.svg docs/assets/images/edition-ue.svg docs/assets/images/arrow-down.svg docs/assets/images/lines-bg-4.svg docs/assets/images/cpp.svg docs/assets/images/arrow-down-white.svg docs/assets/images/menu-icon.svg docs/assets/images/copy-icon.svg docs/assets/images/background-lines.svg docs/assets/images/integrations/hibernate.svg docs/assets/images/integrations/osgi.svg docs/assets/images/integrations/oracle.svg docs/assets/images/integrations/kafka.svg docs/assets/images/integrations/spark.svg docs/assets/images/integrations/more.svg docs/assets/images/integrations/spring.svg docs/assets/images/lines-bg-2.svg docs/assets/images/java.svg docs/assets/images/watermelon-blob.svg docs/assets/images/edition-ee.svg docs/assets/images/piece-of-paper-with-folded-top-right-corner.svg docs/assets/images/feature-reliable.svg docs/assets/images/lines-bg-1.svg docs/assets/images/dotnet.svg docs/assets/images/events-nav-arrow.svg docs/assets/images/mousepad-blob.svg docs/assets/images/github-white.svg docs/assets/images/cancel.svg docs/assets/images/edition-ce.svg docs/run.sh docs/_sass/left-nav.scss docs/_sass/variables.scss docs/_sass/text.scss docs/_sass/layout.scss docs/_sass/right-nav.scss docs/_sass/header.scss docs/_sass/rouge-base16-solarized.scss docs/_sass/github.scss docs/_sass/docs.scss docs/_sass/callouts.scss docs/_sass/code.scss docs/_sass/footer.scss docs/README.adoc docs/_data/toc.yaml docs/Gemfile docs/_docs/messaging.adoc docs/_docs/understanding-configuration.adoc docs/_docs/cpp-specific/index.adoc docs/_docs/cpp-specific/cpp-serialization.adoc docs/_docs/cpp-specific/cpp-platform-interoperability.adoc docs/_docs/cpp-specific/cpp-objects-lifetime.adoc docs/_docs/events/listening-to-events.adoc docs/_docs/events/events.adoc docs/_docs/monitoring-metrics/tracing.adoc docs/_docs/monitoring-metrics/cluster-states.adoc docs/_docs/monitoring-metrics/configuring-metrics.adoc docs/_docs/monitoring-metrics/metrics.adoc docs/_docs/monitoring-metrics/system-views.adoc docs/_docs/monitoring-metrics/new-metrics.adoc docs/_docs/monitoring-metrics/cluster-id.adoc docs/_docs/monitoring-metrics/intro.adoc docs/_docs/monitoring-metrics/new-metrics-system.adoc docs/_docs/binary-client-protocol/data-format.adoc docs/_docs/binary-client-protocol/binary-type-metadata.adoc docs/_docs/binary-client-protocol/key-value-queries.adoc docs/_docs/binary-client-protocol/binary-client-protocol.adoc docs/_docs/binary-client-protocol/cache-configuration.adoc docs/_docs/binary-client-protocol/sql-and-scan-queries.adoc docs/_docs/transactions/mvcc.adoc docs/_docs/starting-nodes.adoc docs/_docs/thin-clients/nodejs-thin-client.adoc docs/_docs/thin-clients/dotnet-thin-client.adoc docs/_docs/thin-clients/java-thin-client.adoc docs/_docs/thin-clients/getting-started-with-thin-clients.adoc docs/_docs/thin-clients/cpp-thin-client.adoc docs/_docs/thin-clients/php-thin-client.adoc docs/_docs/thin-clients/python-thin-client.adoc docs/_docs/logging.adoc docs/_docs/data-modeling/affinity-collocation.adoc docs/_docs/data-modeling/data-modeling.adoc docs/_docs/data-modeling/data-partitioning.adoc docs/_docs/data-modeling/binary-marshaller.adoc docs/_docs/restapi.adoc docs/_docs/plugins.adoc docs/_docs/data-structures/semaphore.adoc docs/_docs/data-structures/countdownlatch.adoc docs/_docs/data-structures/id-generator.adoc docs/_docs/data-structures/atomic-sequence.adoc docs/_docs/data-structures/atomic-types.adoc docs/_docs/data-structures/queue-and-set.adoc docs/_docs/SQL/custom-sql-func.adoc docs/_docs/SQL/sql-transactions.adoc docs/_docs/SQL/distributed-joins.adoc docs/_docs/SQL/sql-tuning.adoc docs/_docs/SQL/sql-introduction.adoc docs/_docs/SQL/ODBC/error-codes.adoc
Re: [MTCGA]: new failures in builds [5643882] needs to be handled
Denis, folks, The mentioned commit breaks our license checks. Is someone working on the fix at the moment? If not it might be simpler to revert the commit and push a fixed version later on. Also it looks sad that so massive contribution was pushed without bot visa [1]. [1] https://issues.apache.org/jira/browse/IGNITE-7595 2020-10-06 12:11 GMT+03:00, dpavlov.ta...@gmail.com : > 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 your contribution. > Could you respond to this email and indicate if you wish to continue and > fix test failures or step down and some committer may revert you commit. > > *New Critical Failure in master [Licenses Headers] > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_LicensesHeaders?branch=%3Cdefault%3E > Changes may lead to failure were done by >- denis magda > https://ci.ignite.apache.org/viewModification.html?modId=908111 > >- Here's a reminder of what contributors were agreed to do > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute >- Should you have any questions please contact dev@ignite.apache.org > > Best Regards, > Apache Ignite TeamCity Bot > https://github.com/apache/ignite-teamcity-bot > Notification generated at 12:11:17 06-10-2020 > -- Best regards, Ivan Pavlukhin
[jira] [Created] (IGNITE-13533) [ML] Tutorial examples runs more than 300000ms
Alexey Zinoviev created IGNITE-13533: Summary: [ML] Tutorial examples runs more than 30ms Key: IGNITE-13533 URL: https://issues.apache.org/jira/browse/IGNITE-13533 Project: Ignite Issue Type: Bug Reporter: Alexey Zinoviev Assignee: Alexey Zinoviev Test has been timed out [test=testExample, timeout=30] Seems like we have a race condition in Genetic Parallel Hyper-parameter tuning -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13532) [ML] Test DatasetAffinityFunctionWrapperTest failed with UnnecessaryStubbingException
Alexey Zinoviev created IGNITE-13532: Summary: [ML] Test DatasetAffinityFunctionWrapperTest failed with UnnecessaryStubbingException Key: IGNITE-13532 URL: https://issues.apache.org/jira/browse/IGNITE-13532 Project: Ignite Issue Type: Bug Components: ml Reporter: Alexey Zinoviev Assignee: Alexey Zinoviev Fix For: 2.10 org.mockito.exceptions.misusing.UnnecessaryStubbingException: Unnecessary stubbings detected in test class: DatasetAffinityFunctionWrapperTest Clean & maintainable test code requires zero unnecessary code. Following stubbings are unnecessary (click to navigate to relevant line of code): 1. -> at org.apache.ignite.ml.dataset.impl.cache.util.DatasetAffinityFunctionWrapperTest.testPartition(DatasetAffinityFunctionWrapperTest.java:80) Please remove unnecessary stubbings or use 'lenient' strictness. More info: javadoc for UnnecessaryStubbingException class. org.mockito.exceptions.misusing.UnnecessaryStubbingException: Unnecessary stubbings detected in test class: DatasetAffinityFunctionWrapperTest Clean & maintainable test code requires zero unnecessary code. Following stubbings are unnecessary (click to navigate to relevant line of code): 1. -> at org.apache.ignite.ml.dataset.impl.cache.util.DatasetAffinityFunctionWrapperTest.testPartition(DatasetAffinityFunctionWrapperTest.java:80) Please remove unnecessary stubbings or use 'lenient' strictness. More info: javadoc for UnnecessaryStubbingException class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13531) [ML] Code cleanup in Util classes
Alexey Zinoviev created IGNITE-13531:
Summary: [ML] Code cleanup in Util classes
Key: IGNITE-13531
URL: https://issues.apache.org/jira/browse/IGNITE-13531
Project: Ignite
Issue Type: Improvement
Reporter: Alexey Zinoviev
Fix For: 2.10
*Suggest improvement to Util classes*
I suggest to add a final class modifier and to add a private constructor
to Util classes in ignite ml. This is Sonar rule RSPEC-1118 (
[https://rules.sonarsource.com/java/tag/design/RSPEC-1118]).
Motivation:
Utility classes, which are collections of static members, are not meant to
be instantiated. Even abstract utility classes, which can be extended,
should not have public constructors. Java adds an implicit public
constructor to every class which does not define at least one explicitly.
Hence, at least one non-public constructor should be defined.
We can add this to:
* DistributedMetaStorageUtil.java
* ComputeUtils.java
* IgniteModelStorageUtil.java
* MapUtil.java
* MatrixUtil.java
* Utils.java
Class JdbcThinSSLUtil.java already has a private constructor.
*Suggest add Serializable to Blas class*
I found that class Blas (org.apache.ignite.ml.math) is not Serializable but
fields f2jBlas and nativeBlas are transient. So I suggest adding
a Serializable to Blas class.
*Add final modifier to static inner fields in utils class*
Motivation:
This static field public but not final, and could be changed by malicious code
or by accident from another package. The field could be made final to avoid
this vulnerability.
For example replace:
public static IgniteDifferentiableDoubleToDoubleFunction SIGMOID = new
IgniteDifferentiableDoubleToDoubleFunction() {
}
With:
public static final IgniteDifferentiableDoubleToDoubleFunction SIGMOID = new
IgniteDifferentiableDoubleToDoubleFunction() {
}
*Inefficient use of keySet iterator instead of entrySet*
This method accesses the value of a Map entry, using a key that was retrieved
from a keySet iterator. It is more efficient to use an iterator on the entrySet
of the map, to avoid the Map.get(key) lookup.
Possible problem is expected order for set.
For example:
for (Integer bucket : hist.keySet()) {
accum += hist.get(bucket);
res.put(bucket, accum);
}
*Can be replaced with single Arrays.fill method call*
For example:
for (int i = 0; i < mins.length; i++)
mins[i] = Double.POSITIVE_INFINITY;
Can be replaced with:
Arrays.fill(mins, Double.POSITIVE_INFINITY);
Founded in:
* ImputerTrainer
* MaxAbsScalerTrainer
* MinMaxScalerTrainer
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[MTCGA]: new failures in builds [5643882] needs to be handled
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 your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master [Licenses Headers] https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_LicensesHeaders?branch=%3Cdefault%3E Changes may lead to failure were done by - denis magda https://ci.ignite.apache.org/viewModification.html?modId=908111 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 12:11:17 06-10-2020
[jira] [Created] (IGNITE-13530) Java thin: exception type is lost on rethrow
Pavel Tupitsyn created IGNITE-13530:
---
Summary: Java thin: exception type is lost on rethrow
Key: IGNITE-13530
URL: https://issues.apache.org/jira/browse/IGNITE-13530
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.10
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.10
Exception handling in TcpClientChannel is inconsistent:
* Some code is duplicated in {code}receive{code} and
{code}convertException{code}
* Some exception types, like {code}ClientAuthenticationException{code}, are
wrapped in {code}ClientException{code}
Make sure to preserve exception types when rethrowing them and deduplicate the
code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
