[DISCUSSION] Remove VS project from C++
Igniters! Currently we have CMake build system, that works on Windows, Linux and MacOs flawlessly 1. CMake is supported natively in VS 2019 2. CMake can generate VS projects for about 20 years flawlessly. 3. Sometimes even maintainers forget to add test sources to VS projects [1] 4. Currently on TC we build Ignite C++ on windows and linux flawlessly using CMake 5. VS projects are not backward compatible. We have to add manually (or by sed or patch) some dependencies in order to build current VS projects on newer versions of VS. So I suggest simpy to remove VS projects because of reasons I've written above. WDYT? [1] -- https://issues.apache.org/jira/browse/IGNITE-15511
Re: [DISCUSSION] Remove VS project from C++
completely support ! >Igniters! > >Currently we have CMake build system, that works on Windows, Linux and >MacOs flawlessly > >1. CMake is supported natively in VS 2019 >2. CMake can generate VS projects for about 20 years flawlessly. >3. Sometimes even maintainers forget to add test sources to VS projects [1] >4. Currently on TC we build Ignite C++ on windows and linux flawlessly >using CMake >5. VS projects are not backward compatible. We have to add manually (or by >sed or patch) some dependencies in order to build current VS projects on >newer versions of VS. > >So I suggest simpy to remove VS projects because of reasons I've written >above. > >WDYT? > > > >[1] -- https://issues.apache.org/jira/browse/IGNITE-15511
Re: [DISCUSSION] Remove VS project from C++
-1 This may become an obstacle for some of the users and I'm not sure how it improves anything. > 3. Sometimes even maintainers forget to add test sources to VS projects [1] We can add an automatic check for this (in form of a test). On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky wrote: > > > completely support ! > > >Igniters! > > > >Currently we have CMake build system, that works on Windows, Linux and > >MacOs flawlessly > > > >1. CMake is supported natively in VS 2019 > >2. CMake can generate VS projects for about 20 years flawlessly. > >3. Sometimes even maintainers forget to add test sources to VS projects > [1] > >4. Currently on TC we build Ignite C++ on windows and linux flawlessly > >using CMake > >5. VS projects are not backward compatible. We have to add manually (or by > >sed or patch) some dependencies in order to build current VS projects on > >newer versions of VS. > > > >So I suggest simpy to remove VS projects because of reasons I've written > >above. > > > >WDYT? > > > > > > > >[1] -- https://issues.apache.org/jira/browse/IGNITE-15511 > > > >
Re: [DISCUSSION] Remove VS project from C++
+1 > 15 сент. 2021 г., в 11:57, Pavel Tupitsyn написал(а): > > -1 > > This may become an obstacle for some of the users and I'm not sure how it > improves anything. > >> 3. Sometimes even maintainers forget to add test sources to VS projects > [1] > We can add an automatic check for this (in form of a test). > > On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky > wrote: > >> >> >> completely support ! >> >>> Igniters! >>> >>> Currently we have CMake build system, that works on Windows, Linux and >>> MacOs flawlessly >>> >>> 1. CMake is supported natively in VS 2019 >>> 2. CMake can generate VS projects for about 20 years flawlessly. >>> 3. Sometimes even maintainers forget to add test sources to VS projects >> [1] >>> 4. Currently on TC we build Ignite C++ on windows and linux flawlessly >>> using CMake >>> 5. VS projects are not backward compatible. We have to add manually (or by >>> sed or patch) some dependencies in order to build current VS projects on >>> newer versions of VS. >>> >>> So I suggest simpy to remove VS projects because of reasons I've written >>> above. >>> >>> WDYT? >>> >>> >>> >>> [1] -- https://issues.apache.org/jira/browse/IGNITE-15511 >> >> >> >>
Re: [DISCUSSION] Remove VS project from C++
+1 for removing VS project 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov : > +1 > >> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn >> написал(а): >> >> -1 >> >> This may become an obstacle for some of the users and I'm not sure how it >> improves anything. >> >>> 3. Sometimes even maintainers forget to add test sources to VS projects >> [1] >> We can add an automatic check for this (in form of a test). >> >> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky >> wrote: >> >>> >>> >>> completely support ! >>> Igniters! Currently we have CMake build system, that works on Windows, Linux and MacOs flawlessly 1. CMake is supported natively in VS 2019 2. CMake can generate VS projects for about 20 years flawlessly. 3. Sometimes even maintainers forget to add test sources to VS projects >>> [1] 4. Currently on TC we build Ignite C++ on windows and linux flawlessly using CMake 5. VS projects are not backward compatible. We have to add manually (or by sed or patch) some dependencies in order to build current VS projects on newer versions of VS. So I suggest simpy to remove VS projects because of reasons I've written above. WDYT? [1] -- https://issues.apache.org/jira/browse/IGNITE-15511 >>> >>> >>> >>> > > -- Best regards, Ivan Pavlukhin
Re: [DISCUSSION] Remove VS project from C++
+1 Let's keep the project clean and on the verge of preferable tech stack. > On 15 Sep 2021, at 12:02, Ivan Pavlukhin wrote: > > +1 for removing VS project > > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov : >> +1 >> >>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn >>> написал(а): >>> >>> -1 >>> >>> This may become an obstacle for some of the users and I'm not sure how it >>> improves anything. >>> 3. Sometimes even maintainers forget to add test sources to VS projects >>> [1] >>> We can add an automatic check for this (in form of a test). >>> >>> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky >>> wrote: >>> completely support ! > Igniters! > > Currently we have CMake build system, that works on Windows, Linux and > MacOs flawlessly > > 1. CMake is supported natively in VS 2019 > 2. CMake can generate VS projects for about 20 years flawlessly. > 3. Sometimes even maintainers forget to add test sources to VS projects [1] > 4. Currently on TC we build Ignite C++ on windows and linux flawlessly > using CMake > 5. VS projects are not backward compatible. We have to add manually (or > by > sed or patch) some dependencies in order to build current VS projects > on > newer versions of VS. > > So I suggest simpy to remove VS projects because of reasons I've > written > above. > > WDYT? > > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-15511 >> >> > > > -- > > Best regards, > Ivan Pavlukhin
Re: [DISCUSSION] Remove VS project from C++
>> This may become an obstacle for some of the users and I'm not sure how it improves anything. Please specify more correctly. What is an obstacle? Current VS projects (odbc) cannot be build on VC 2015+ without modification. CMake is an industry standard now. >> I'm not sure how it improves anything. It makes development much more easier. >> We can add an automatic check for this (in form of a test). I can hardly imagine how it can be done. And even if it is possible, this is a sisyphus job. ср, 15 сент. 2021 г. в 12:11, Petr Ivanov : > +1 > > Let's keep the project clean and on the verge of preferable tech stack. > > > > On 15 Sep 2021, at 12:02, Ivan Pavlukhin wrote: > > > > +1 for removing VS project > > > > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov : > >> +1 > >> > >>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn > >>> написал(а): > >>> > >>> -1 > >>> > >>> This may become an obstacle for some of the users and I'm not sure how > it > >>> improves anything. > >>> > 3. Sometimes even maintainers forget to add test sources to VS > projects > >>> [1] > >>> We can add an automatic check for this (in form of a test). > >>> > >>> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky > >>> wrote: > >>> > > > completely support ! > > > Igniters! > > > > Currently we have CMake build system, that works on Windows, Linux > and > > MacOs flawlessly > > > > 1. CMake is supported natively in VS 2019 > > 2. CMake can generate VS projects for about 20 years flawlessly. > > 3. Sometimes even maintainers forget to add test sources to VS > projects > [1] > > 4. Currently on TC we build Ignite C++ on windows and linux > flawlessly > > using CMake > > 5. VS projects are not backward compatible. We have to add manually > (or > > by > > sed or patch) some dependencies in order to build current VS projects > > on > > newer versions of VS. > > > > So I suggest simpy to remove VS projects because of reasons I've > > written > > above. > > > > WDYT? > > > > > > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-15511 > > > > > >> > >> > > > > > > -- > > > > Best regards, > > Ivan Pavlukhin > > -- Sincerely yours, Ivan Daschinskiy
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
+1 Checked sha512 and sign of archives, built from sources, started a cluster with a few nodes. вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn : > Ilya, > > > I'm still confused by this publish/ directory. Why are we shipping > > something which is not for publishing in our binary package? I've also > not > > heard of it before. > > I think this was introduced in 2.8.0 as part of [1]. > It is how the build process works by default and we just copy the entire > bin directory to the package, > while only publish subdir is actually required. > > We can probably drop support for legacy (unsupported) .NET versions in the > next release and simplify our build process, I'll look into this. > > [1] https://issues.apache.org/jira/browse/IGNITE-11805 > > On Tue, Sep 14, 2021 at 6:12 PM Ilya Kasnacheev > > wrote: > > > Hello! > > > > + 0.5 > > > > I have got it to run with the following command: > > % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 > > Apache.Ignite.dll > > > > I'm still confused by this publish/ directory. Why are we shipping > > something which is not for publishing in our binary package? I've also > not > > heard of it before. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn : > > > > > Ilya, > > > > > > > When I have also installed 3.1 and 2.0 > > > Please try .NET SDK 2.1 to run tests. > > > Yes, it went out of support last month, I've created a ticket [1]. > > > > > > > > > > dotnet Apache.Ignite.dll > > > That's correct, but should be done > > > in platforms/dotnet/bin/netcoreapp2.0/publish, please try again. > > > We should deal with duplicate binaries, I've created another ticket [2] > > > > > > > > > > Why do we still ship Apache.Ignite.exe if it does not run? > > > It runs on Windows. For Linux we ship Apache.Ignite.dll. > > > > > > > > > I don't think any of this is a blocker for the current release. > > > - Out-of-support SDK only affects those who build from source, and it > > went > > > out of support only recently > > > - Duplicate binaries are there for a long time and no one was > complaining > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15504 > > > [2] https://issues.apache.org/jira/browse/IGNITE-15505 > > > > > > On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev < > > > ilya.kasnach...@gmail.com> > > > wrote: > > > > > > > Hello! > > > > > > > > - 0.5 > > > > > > > > Installed DEB package, built binary from source, ran sqlline, built > > .NET. > > > > > > > > I have failed to run .NET tests though. > > > > > > > > If I only install Current .NET, I get the following: > > > > It was not possible to find any compatible framework version > > > > The framework 'Microsoft.NETCore.App', version '2.0.0' was not found. > > > > > > > > > > > > - The following frameworks were found: > > > > > > > > > > > > 5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App] > > > > > > > > > > > > You can resolve the problem by installing the specified framework > > and/or > > > > SDK. > > > > > > > > > > > > The specified framework can be found at: > > > > > > > > > > > > - > > > > > > > > > > > > > > https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=2.0.0&arch=x64&rid=ubuntu.21.04-x64 > > > > > > > > When I have also installed 3.1 and 2.0, now I see: > > > > > > > > The active test run was aborted. Reason: Test host process crashed : > No > > > > usable version of the libssl was found > > > > > > > > It looks like we have to bump the permitted .NET version. > > > > > > > > From the slim binary package I also can't run .NET: > > > > > > > > ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0% > > > > dotnet Apache.Ignite.dll > > > > Error: > > > > An assembly specified in the application dependencies manifest > > > > (Apache.Ignite.deps.json) was not found: > > > >package: 'System.Configuration.ConfigurationManager', version: > > '4.4.0' > > > >path: > > > 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll' > > > > > > > > Do we have any instructions on how to run it under Linux? Why do we > > still > > > > ship Apache.Ignite.exe if it does not run? > > > > > > > > Regards, > > > > -- > > > > Ilya Kasnacheev > > > > > > > > > > > > вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>: > > > > > > > > > check again, 15503 not cherry-pick, right? > > > > > > > > > > 在 2021/9/14 15:55, Shishkov Ilya 写道: > > > > > >> Should the following two issue be merged into the ignite-2.11 > > > branch? > > > > > > Hi, as I see, both tickets are fixed in 2.10 and 2.11. > > > > > > > > > > > > вт, 14 сент. 2021 г. в 04:13, 18624049226<18624049...@163.com>: > > > > > > > > > > > >> Should the following two issue be merged into the ignite-2.11 > > > branch? > > > > > >> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-14404 > > > > > >> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-15503 > > > > > >> > > > > > >> 在
Re: [DISCUSSION] Remove VS project from C++
>> Please specify more correctly. Sorry, typo, more concretely. ср, 15 сент. 2021 г. в 12:22, Ivan Daschinsky : > >> This may become an obstacle for some of the users and I'm not sure how > it improves anything. > Please specify more correctly. What is an obstacle? Current VS projects > (odbc) cannot be build on VC 2015+ > without modification. CMake is an industry standard now. > >> I'm not sure how it improves anything. > It makes development much more easier. > > >> We can add an automatic check for this (in form of a test). > I can hardly imagine how it can be done. And even if it is possible, this > is a sisyphus job. > > > ср, 15 сент. 2021 г. в 12:11, Petr Ivanov : > >> +1 >> >> Let's keep the project clean and on the verge of preferable tech stack. >> >> >> > On 15 Sep 2021, at 12:02, Ivan Pavlukhin wrote: >> > >> > +1 for removing VS project >> > >> > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov : >> >> +1 >> >> >> >>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn >> >>> написал(а): >> >>> >> >>> -1 >> >>> >> >>> This may become an obstacle for some of the users and I'm not sure >> how it >> >>> improves anything. >> >>> >> 3. Sometimes even maintainers forget to add test sources to VS >> projects >> >>> [1] >> >>> We can add an automatic check for this (in form of a test). >> >>> >> >>> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky >> >>> wrote: >> >>> >> >> >> completely support ! >> >> > Igniters! >> > >> > Currently we have CMake build system, that works on Windows, Linux >> and >> > MacOs flawlessly >> > >> > 1. CMake is supported natively in VS 2019 >> > 2. CMake can generate VS projects for about 20 years flawlessly. >> > 3. Sometimes even maintainers forget to add test sources to VS >> projects >> [1] >> > 4. Currently on TC we build Ignite C++ on windows and linux >> flawlessly >> > using CMake >> > 5. VS projects are not backward compatible. We have to add manually >> (or >> > by >> > sed or patch) some dependencies in order to build current VS >> projects >> > on >> > newer versions of VS. >> > >> > So I suggest simpy to remove VS projects because of reasons I've >> > written >> > above. >> > >> > WDYT? >> > >> > >> > >> > [1] -- https://issues.apache.org/jira/browse/IGNITE-15511 >> >> >> >> >> >> >> >> >> > >> > >> > -- >> > >> > Best regards, >> > Ivan Pavlukhin >> >> > > -- > Sincerely yours, Ivan Daschinskiy > -- Sincerely yours, Ivan Daschinskiy
Re: [DISCUSSION] Remove VS project from C++
> It makes development much more easier. How? > I can hardly imagine how it can be done 1. Get all files in the directory 2. Filter by TestSuite suffix 3. Check if all of them are present in VS files Am I missing something? We have checks like this for Ignite.NET [1] [1] https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/ProjectFilesTest.cs On Wed, Sep 15, 2021 at 12:22 PM Ivan Daschinsky wrote: > >> This may become an obstacle for some of the users and I'm not sure how > it improves anything. > Please specify more correctly. What is an obstacle? Current VS projects > (odbc) cannot be build on VC 2015+ > without modification. CMake is an industry standard now. > >> I'm not sure how it improves anything. > It makes development much more easier. > > >> We can add an automatic check for this (in form of a test). > I can hardly imagine how it can be done. And even if it is possible, this > is a sisyphus job. > > > ср, 15 сент. 2021 г. в 12:11, Petr Ivanov : > > > +1 > > > > Let's keep the project clean and on the verge of preferable tech stack. > > > > > > > On 15 Sep 2021, at 12:02, Ivan Pavlukhin wrote: > > > > > > +1 for removing VS project > > > > > > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov : > > >> +1 > > >> > > >>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn > > >>> написал(а): > > >>> > > >>> -1 > > >>> > > >>> This may become an obstacle for some of the users and I'm not sure > how > > it > > >>> improves anything. > > >>> > > 3. Sometimes even maintainers forget to add test sources to VS > > projects > > >>> [1] > > >>> We can add an automatic check for this (in form of a test). > > >>> > > >>> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky > > >>> wrote: > > >>> > > > > > > completely support ! > > > > > Igniters! > > > > > > Currently we have CMake build system, that works on Windows, Linux > > and > > > MacOs flawlessly > > > > > > 1. CMake is supported natively in VS 2019 > > > 2. CMake can generate VS projects for about 20 years flawlessly. > > > 3. Sometimes even maintainers forget to add test sources to VS > > projects > > [1] > > > 4. Currently on TC we build Ignite C++ on windows and linux > > flawlessly > > > using CMake > > > 5. VS projects are not backward compatible. We have to add manually > > (or > > > by > > > sed or patch) some dependencies in order to build current VS > projects > > > on > > > newer versions of VS. > > > > > > So I suggest simpy to remove VS projects because of reasons I've > > > written > > > above. > > > > > > WDYT? > > > > > > > > > > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-15511 > > > > > > > > > > >> > > >> > > > > > > > > > -- > > > > > > Best regards, > > > Ivan Pavlukhin > > > > > > -- > Sincerely yours, Ivan Daschinskiy >
Re: [DISCUSSION] Remove VS project from C++
> How? Currently user must add sources in 2 different places. One of this places is not specified and not intended to be edit outside VC. CMake can generate VS projects easily and without any problem. I've done this even in 2008 when I was C++/Qt developer. >> 1. Get all files in the directory >> 2. Filter by TestSuite suffix >> 3. Check if all of them are present in VS files First of all, BOOST_TEST is not NUnit :) Secondly, we can do that, but it is not so easy as it is in .NET. Yes, we can use boost libraries in tests, but why we should do it? Why we should invest our time in this activity? ср, 15 сент. 2021 г. в 12:30, Pavel Tupitsyn : > > It makes development much more easier. > > How? > > > I can hardly imagine how it can be done > > 1. Get all files in the directory > 2. Filter by TestSuite suffix > 3. Check if all of them are present in VS files > Am I missing something? We have checks like this for Ignite.NET [1] > > [1] > > https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/ProjectFilesTest.cs > > > On Wed, Sep 15, 2021 at 12:22 PM Ivan Daschinsky > wrote: > > > >> This may become an obstacle for some of the users and I'm not sure how > > it improves anything. > > Please specify more correctly. What is an obstacle? Current VS projects > > (odbc) cannot be build on VC 2015+ > > without modification. CMake is an industry standard now. > > >> I'm not sure how it improves anything. > > It makes development much more easier. > > > > >> We can add an automatic check for this (in form of a test). > > I can hardly imagine how it can be done. And even if it is possible, this > > is a sisyphus job. > > > > > > ср, 15 сент. 2021 г. в 12:11, Petr Ivanov : > > > > > +1 > > > > > > Let's keep the project clean and on the verge of preferable tech stack. > > > > > > > > > > On 15 Sep 2021, at 12:02, Ivan Pavlukhin > wrote: > > > > > > > > +1 for removing VS project > > > > > > > > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov : > > > >> +1 > > > >> > > > >>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn > > > >>> написал(а): > > > >>> > > > >>> -1 > > > >>> > > > >>> This may become an obstacle for some of the users and I'm not sure > > how > > > it > > > >>> improves anything. > > > >>> > > > 3. Sometimes even maintainers forget to add test sources to VS > > > projects > > > >>> [1] > > > >>> We can add an automatic check for this (in form of a test). > > > >>> > > > >>> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky > > > >>> wrote: > > > >>> > > > > > > > > > completely support ! > > > > > > > Igniters! > > > > > > > > Currently we have CMake build system, that works on Windows, > Linux > > > and > > > > MacOs flawlessly > > > > > > > > 1. CMake is supported natively in VS 2019 > > > > 2. CMake can generate VS projects for about 20 years flawlessly. > > > > 3. Sometimes even maintainers forget to add test sources to VS > > > projects > > > [1] > > > > 4. Currently on TC we build Ignite C++ on windows and linux > > > flawlessly > > > > using CMake > > > > 5. VS projects are not backward compatible. We have to add > manually > > > (or > > > > by > > > > sed or patch) some dependencies in order to build current VS > > projects > > > > on > > > > newer versions of VS. > > > > > > > > So I suggest simpy to remove VS projects because of reasons I've > > > > written > > > > above. > > > > > > > > WDYT? > > > > > > > > > > > > > > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-15511 > > > > > > > > > > > > > > > >> > > > >> > > > > > > > > > > > > -- > > > > > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > > > > -- > > Sincerely yours, Ivan Daschinskiy > > > -- Sincerely yours, Ivan Daschinskiy
Re: [DISCUSSION] Remove VS project from C++
>> Currently user Sorry typo, I meant developer. ср, 15 сент. 2021 г. в 12:35, Ivan Daschinsky : > > How? > Currently user must add sources in 2 different places. One of this places > is not specified and not intended to be edit outside VC. > CMake can generate VS projects easily and without any problem. I've done > this even in 2008 when I was C++/Qt developer. > > >> 1. Get all files in the directory > >> 2. Filter by TestSuite suffix > >> 3. Check if all of them are present in VS files > First of all, BOOST_TEST is not NUnit :) Secondly, we can do that, but it > is not so easy as it is in .NET. > Yes, we can use boost libraries in tests, but why we should do it? Why we > should invest our time in this activity? > > > > > > ср, 15 сент. 2021 г. в 12:30, Pavel Tupitsyn : > >> > It makes development much more easier. >> >> How? >> >> > I can hardly imagine how it can be done >> >> 1. Get all files in the directory >> 2. Filter by TestSuite suffix >> 3. Check if all of them are present in VS files >> Am I missing something? We have checks like this for Ignite.NET [1] >> >> [1] >> >> https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/ProjectFilesTest.cs >> >> >> On Wed, Sep 15, 2021 at 12:22 PM Ivan Daschinsky >> wrote: >> >> > >> This may become an obstacle for some of the users and I'm not sure >> how >> > it improves anything. >> > Please specify more correctly. What is an obstacle? Current VS projects >> > (odbc) cannot be build on VC 2015+ >> > without modification. CMake is an industry standard now. >> > >> I'm not sure how it improves anything. >> > It makes development much more easier. >> > >> > >> We can add an automatic check for this (in form of a test). >> > I can hardly imagine how it can be done. And even if it is possible, >> this >> > is a sisyphus job. >> > >> > >> > ср, 15 сент. 2021 г. в 12:11, Petr Ivanov : >> > >> > > +1 >> > > >> > > Let's keep the project clean and on the verge of preferable tech >> stack. >> > > >> > > >> > > > On 15 Sep 2021, at 12:02, Ivan Pavlukhin >> wrote: >> > > > >> > > > +1 for removing VS project >> > > > >> > > > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov : >> > > >> +1 >> > > >> >> > > >>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn >> > > >>> написал(а): >> > > >>> >> > > >>> -1 >> > > >>> >> > > >>> This may become an obstacle for some of the users and I'm not sure >> > how >> > > it >> > > >>> improves anything. >> > > >>> >> > > 3. Sometimes even maintainers forget to add test sources to VS >> > > projects >> > > >>> [1] >> > > >>> We can add an automatic check for this (in form of a test). >> > > >>> >> > > >>> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky >> > > >>> wrote: >> > > >>> >> > > >> > > >> > > completely support ! >> > > >> > > > Igniters! >> > > > >> > > > Currently we have CMake build system, that works on Windows, >> Linux >> > > and >> > > > MacOs flawlessly >> > > > >> > > > 1. CMake is supported natively in VS 2019 >> > > > 2. CMake can generate VS projects for about 20 years flawlessly. >> > > > 3. Sometimes even maintainers forget to add test sources to VS >> > > projects >> > > [1] >> > > > 4. Currently on TC we build Ignite C++ on windows and linux >> > > flawlessly >> > > > using CMake >> > > > 5. VS projects are not backward compatible. We have to add >> manually >> > > (or >> > > > by >> > > > sed or patch) some dependencies in order to build current VS >> > projects >> > > > on >> > > > newer versions of VS. >> > > > >> > > > So I suggest simpy to remove VS projects because of reasons I've >> > > > written >> > > > above. >> > > > >> > > > WDYT? >> > > > >> > > > >> > > > >> > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-15511 >> > > >> > > >> > > >> > > >> > > >> >> > > >> >> > > > >> > > > >> > > > -- >> > > > >> > > > Best regards, >> > > > Ivan Pavlukhin >> > > >> > > >> > >> > -- >> > Sincerely yours, Ivan Daschinskiy >> > >> > > > -- > Sincerely yours, Ivan Daschinskiy > -- Sincerely yours, Ivan Daschinskiy
Re: [DISCUSSION] Remove VS project from C++
Ivan, Ok, I've got your point. What's your assessment on the following: 1. What percentage of our users rely on existing VS projects? 2. How much time (in minutes) does it take to switch from using existing VS projects to CMake-generated ones? On Wed, Sep 15, 2021 at 12:37 PM Ivan Daschinsky wrote: > >> Currently user > Sorry typo, I meant developer. > > ср, 15 сент. 2021 г. в 12:35, Ivan Daschinsky : > > > > How? > > Currently user must add sources in 2 different places. One of this places > > is not specified and not intended to be edit outside VC. > > CMake can generate VS projects easily and without any problem. I've done > > this even in 2008 when I was C++/Qt developer. > > > > >> 1. Get all files in the directory > > >> 2. Filter by TestSuite suffix > > >> 3. Check if all of them are present in VS files > > First of all, BOOST_TEST is not NUnit :) Secondly, we can do that, but it > > is not so easy as it is in .NET. > > Yes, we can use boost libraries in tests, but why we should do it? Why we > > should invest our time in this activity? > > > > > > > > > > > > ср, 15 сент. 2021 г. в 12:30, Pavel Tupitsyn : > > > >> > It makes development much more easier. > >> > >> How? > >> > >> > I can hardly imagine how it can be done > >> > >> 1. Get all files in the directory > >> 2. Filter by TestSuite suffix > >> 3. Check if all of them are present in VS files > >> Am I missing something? We have checks like this for Ignite.NET [1] > >> > >> [1] > >> > >> > https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/ProjectFilesTest.cs > >> > >> > >> On Wed, Sep 15, 2021 at 12:22 PM Ivan Daschinsky > >> wrote: > >> > >> > >> This may become an obstacle for some of the users and I'm not sure > >> how > >> > it improves anything. > >> > Please specify more correctly. What is an obstacle? Current VS > projects > >> > (odbc) cannot be build on VC 2015+ > >> > without modification. CMake is an industry standard now. > >> > >> I'm not sure how it improves anything. > >> > It makes development much more easier. > >> > > >> > >> We can add an automatic check for this (in form of a test). > >> > I can hardly imagine how it can be done. And even if it is possible, > >> this > >> > is a sisyphus job. > >> > > >> > > >> > ср, 15 сент. 2021 г. в 12:11, Petr Ivanov : > >> > > >> > > +1 > >> > > > >> > > Let's keep the project clean and on the verge of preferable tech > >> stack. > >> > > > >> > > > >> > > > On 15 Sep 2021, at 12:02, Ivan Pavlukhin > >> wrote: > >> > > > > >> > > > +1 for removing VS project > >> > > > > >> > > > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov >: > >> > > >> +1 > >> > > >> > >> > > >>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn > > >> > > >>> написал(а): > >> > > >>> > >> > > >>> -1 > >> > > >>> > >> > > >>> This may become an obstacle for some of the users and I'm not > sure > >> > how > >> > > it > >> > > >>> improves anything. > >> > > >>> > >> > > 3. Sometimes even maintainers forget to add test sources to VS > >> > > projects > >> > > >>> [1] > >> > > >>> We can add an automatic check for this (in form of a test). > >> > > >>> > >> > > >>> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky > >> > > >>> wrote: > >> > > >>> > >> > > > >> > > > >> > > completely support ! > >> > > > >> > > > Igniters! > >> > > > > >> > > > Currently we have CMake build system, that works on Windows, > >> Linux > >> > > and > >> > > > MacOs flawlessly > >> > > > > >> > > > 1. CMake is supported natively in VS 2019 > >> > > > 2. CMake can generate VS projects for about 20 years > flawlessly. > >> > > > 3. Sometimes even maintainers forget to add test sources to VS > >> > > projects > >> > > [1] > >> > > > 4. Currently on TC we build Ignite C++ on windows and linux > >> > > flawlessly > >> > > > using CMake > >> > > > 5. VS projects are not backward compatible. We have to add > >> manually > >> > > (or > >> > > > by > >> > > > sed or patch) some dependencies in order to build current VS > >> > projects > >> > > > on > >> > > > newer versions of VS. > >> > > > > >> > > > So I suggest simpy to remove VS projects because of reasons > I've > >> > > > written > >> > > > above. > >> > > > > >> > > > WDYT? > >> > > > > >> > > > > >> > > > > >> > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-15511 > >> > > > >> > > > >> > > > >> > > > >> > > >> > >> > > >> > >> > > > > >> > > > > >> > > > -- > >> > > > > >> > > > Best regards, > >> > > > Ivan Pavlukhin > >> > > > >> > > > >> > > >> > -- > >> > Sincerely yours, Ivan Daschinskiy > >> > > >> > > > > > > -- > > Sincerely yours, Ivan Daschinskiy > > > > > -- > Sincerely yours, Ivan Daschinskiy >
Re: [DISCUSSION] Remove VS project from C++
>> 1. What percentage of our users rely on existing VS projects? It is impossible to answer, but I suppose not so much. And, again, these projects needs some tweaks in order to work properly in VS 2015+ Moreover, you cannot use VS as is, you should tweak them or download dependencies in specific location. >> How much time (in minutes) does it take to switch from using existing VS projects to CMake-generated ones? If you use VS 2017 and later -- just a second, they already support CMake out of box https://devblogs.microsoft.com/cppblog/cmake-support-in-visual-studio/ If you use VS2015 and earlielr -- just download cmake and use bundled gui app and generate projects in few clicks. And don't forget about vcpkg [1]. Even microsoft goes towards cmake and make even package manager for it. And it works great, I've tried with Ignite C++. [1] -- https://github.com/microsoft/vcpkg ср, 15 сент. 2021 г. в 12:46, Pavel Tupitsyn : > Ivan, > > Ok, I've got your point. > What's your assessment on the following: > > 1. What percentage of our users rely on existing VS projects? > 2. How much time (in minutes) does it take to switch from using existing VS > projects to CMake-generated ones? > > > > On Wed, Sep 15, 2021 at 12:37 PM Ivan Daschinsky > wrote: > > > >> Currently user > > Sorry typo, I meant developer. > > > > ср, 15 сент. 2021 г. в 12:35, Ivan Daschinsky : > > > > > > How? > > > Currently user must add sources in 2 different places. One of this > places > > > is not specified and not intended to be edit outside VC. > > > CMake can generate VS projects easily and without any problem. I've > done > > > this even in 2008 when I was C++/Qt developer. > > > > > > >> 1. Get all files in the directory > > > >> 2. Filter by TestSuite suffix > > > >> 3. Check if all of them are present in VS files > > > First of all, BOOST_TEST is not NUnit :) Secondly, we can do that, but > it > > > is not so easy as it is in .NET. > > > Yes, we can use boost libraries in tests, but why we should do it? Why > we > > > should invest our time in this activity? > > > > > > > > > > > > > > > > > > ср, 15 сент. 2021 г. в 12:30, Pavel Tupitsyn : > > > > > >> > It makes development much more easier. > > >> > > >> How? > > >> > > >> > I can hardly imagine how it can be done > > >> > > >> 1. Get all files in the directory > > >> 2. Filter by TestSuite suffix > > >> 3. Check if all of them are present in VS files > > >> Am I missing something? We have checks like this for Ignite.NET [1] > > >> > > >> [1] > > >> > > >> > > > https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/ProjectFilesTest.cs > > >> > > >> > > >> On Wed, Sep 15, 2021 at 12:22 PM Ivan Daschinsky > > > >> wrote: > > >> > > >> > >> This may become an obstacle for some of the users and I'm not > sure > > >> how > > >> > it improves anything. > > >> > Please specify more correctly. What is an obstacle? Current VS > > projects > > >> > (odbc) cannot be build on VC 2015+ > > >> > without modification. CMake is an industry standard now. > > >> > >> I'm not sure how it improves anything. > > >> > It makes development much more easier. > > >> > > > >> > >> We can add an automatic check for this (in form of a test). > > >> > I can hardly imagine how it can be done. And even if it is possible, > > >> this > > >> > is a sisyphus job. > > >> > > > >> > > > >> > ср, 15 сент. 2021 г. в 12:11, Petr Ivanov : > > >> > > > >> > > +1 > > >> > > > > >> > > Let's keep the project clean and on the verge of preferable tech > > >> stack. > > >> > > > > >> > > > > >> > > > On 15 Sep 2021, at 12:02, Ivan Pavlukhin > > >> wrote: > > >> > > > > > >> > > > +1 for removing VS project > > >> > > > > > >> > > > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov < > nizhi...@apache.org > > >: > > >> > > >> +1 > > >> > > >> > > >> > > >>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn < > ptupit...@apache.org > > > > > >> > > >>> написал(а): > > >> > > >>> > > >> > > >>> -1 > > >> > > >>> > > >> > > >>> This may become an obstacle for some of the users and I'm not > > sure > > >> > how > > >> > > it > > >> > > >>> improves anything. > > >> > > >>> > > >> > > 3. Sometimes even maintainers forget to add test sources to > VS > > >> > > projects > > >> > > >>> [1] > > >> > > >>> We can add an automatic check for this (in form of a test). > > >> > > >>> > > >> > > >>> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky > > >> > > >>> wrote: > > >> > > >>> > > >> > > > > >> > > > > >> > > completely support ! > > >> > > > > >> > > > Igniters! > > >> > > > > > >> > > > Currently we have CMake build system, that works on Windows, > > >> Linux > > >> > > and > > >> > > > MacOs flawlessly > > >> > > > > > >> > > > 1. CMake is supported natively in VS 2019 > > >> > > > 2. CMake can generate VS projects for about 20 years > > flawlessly. > > >> > > > 3. Sometimes even maintainers forget to add test sources to > VS > > >> > > proje
Re: [DISCUSSION] Remove VS project from C++
Ivan, thanks for the answers! I retract my "-1". No objections. On Wed, Sep 15, 2021 at 12:58 PM Ivan Daschinsky wrote: > >> 1. What percentage of our users rely on existing VS projects? > It is impossible to answer, but I suppose not so much. And, again, these > projects needs some tweaks in order to work properly in VS 2015+ > Moreover, you cannot use VS as is, you should tweak them or download > dependencies in specific location. > > >> How much time (in minutes) does it take to switch from using existing VS > projects to CMake-generated ones? > If you use VS 2017 and later -- just a second, they already support CMake > out of box > https://devblogs.microsoft.com/cppblog/cmake-support-in-visual-studio/ > If you use VS2015 and earlielr -- just download cmake and use bundled gui > app and generate projects in few clicks. > > And don't forget about vcpkg [1]. Even microsoft goes towards cmake and > make even package manager for it. > And it works great, I've tried with Ignite C++. > > [1] -- https://github.com/microsoft/vcpkg > > ср, 15 сент. 2021 г. в 12:46, Pavel Tupitsyn : > > > Ivan, > > > > Ok, I've got your point. > > What's your assessment on the following: > > > > 1. What percentage of our users rely on existing VS projects? > > 2. How much time (in minutes) does it take to switch from using existing > VS > > projects to CMake-generated ones? > > > > > > > > On Wed, Sep 15, 2021 at 12:37 PM Ivan Daschinsky > > wrote: > > > > > >> Currently user > > > Sorry typo, I meant developer. > > > > > > ср, 15 сент. 2021 г. в 12:35, Ivan Daschinsky : > > > > > > > > How? > > > > Currently user must add sources in 2 different places. One of this > > places > > > > is not specified and not intended to be edit outside VC. > > > > CMake can generate VS projects easily and without any problem. I've > > done > > > > this even in 2008 when I was C++/Qt developer. > > > > > > > > >> 1. Get all files in the directory > > > > >> 2. Filter by TestSuite suffix > > > > >> 3. Check if all of them are present in VS files > > > > First of all, BOOST_TEST is not NUnit :) Secondly, we can do that, > but > > it > > > > is not so easy as it is in .NET. > > > > Yes, we can use boost libraries in tests, but why we should do it? > Why > > we > > > > should invest our time in this activity? > > > > > > > > > > > > > > > > > > > > > > > > ср, 15 сент. 2021 г. в 12:30, Pavel Tupitsyn : > > > > > > > >> > It makes development much more easier. > > > >> > > > >> How? > > > >> > > > >> > I can hardly imagine how it can be done > > > >> > > > >> 1. Get all files in the directory > > > >> 2. Filter by TestSuite suffix > > > >> 3. Check if all of them are present in VS files > > > >> Am I missing something? We have checks like this for Ignite.NET [1] > > > >> > > > >> [1] > > > >> > > > >> > > > > > > https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/ProjectFilesTest.cs > > > >> > > > >> > > > >> On Wed, Sep 15, 2021 at 12:22 PM Ivan Daschinsky < > ivanda...@gmail.com > > > > > > >> wrote: > > > >> > > > >> > >> This may become an obstacle for some of the users and I'm not > > sure > > > >> how > > > >> > it improves anything. > > > >> > Please specify more correctly. What is an obstacle? Current VS > > > projects > > > >> > (odbc) cannot be build on VC 2015+ > > > >> > without modification. CMake is an industry standard now. > > > >> > >> I'm not sure how it improves anything. > > > >> > It makes development much more easier. > > > >> > > > > >> > >> We can add an automatic check for this (in form of a test). > > > >> > I can hardly imagine how it can be done. And even if it is > possible, > > > >> this > > > >> > is a sisyphus job. > > > >> > > > > >> > > > > >> > ср, 15 сент. 2021 г. в 12:11, Petr Ivanov : > > > >> > > > > >> > > +1 > > > >> > > > > > >> > > Let's keep the project clean and on the verge of preferable tech > > > >> stack. > > > >> > > > > > >> > > > > > >> > > > On 15 Sep 2021, at 12:02, Ivan Pavlukhin > > > > >> wrote: > > > >> > > > > > > >> > > > +1 for removing VS project > > > >> > > > > > > >> > > > 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov < > > nizhi...@apache.org > > > >: > > > >> > > >> +1 > > > >> > > >> > > > >> > > >>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn < > > ptupit...@apache.org > > > > > > > >> > > >>> написал(а): > > > >> > > >>> > > > >> > > >>> -1 > > > >> > > >>> > > > >> > > >>> This may become an obstacle for some of the users and I'm > not > > > sure > > > >> > how > > > >> > > it > > > >> > > >>> improves anything. > > > >> > > >>> > > > >> > > 3. Sometimes even maintainers forget to add test sources to > > VS > > > >> > > projects > > > >> > > >>> [1] > > > >> > > >>> We can add an automatic check for this (in form of a test). > > > >> > > >>> > > > >> > > >>> On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky > > > >> > > >>> wrote: > > > >> > > >>> > > > >> > > > > > >> > > > > > >> > > completely support ! > > > >>
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
+1 (binding) > 15 сент. 2021 г., в 12:24, Alex Plehanov написал(а): > > +1 > > Checked sha512 and sign of archives, built from sources, started a cluster > with a few nodes. > > вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn : > >> Ilya, >> >>> I'm still confused by this publish/ directory. Why are we shipping >>> something which is not for publishing in our binary package? I've also >> not >>> heard of it before. >> >> I think this was introduced in 2.8.0 as part of [1]. >> It is how the build process works by default and we just copy the entire >> bin directory to the package, >> while only publish subdir is actually required. >> >> We can probably drop support for legacy (unsupported) .NET versions in the >> next release and simplify our build process, I'll look into this. >> >> [1] https://issues.apache.org/jira/browse/IGNITE-11805 >> >> On Tue, Sep 14, 2021 at 6:12 PM Ilya Kasnacheev >> >> wrote: >> >>> Hello! >>> >>> + 0.5 >>> >>> I have got it to run with the following command: >>> % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 >>> Apache.Ignite.dll >>> >>> I'm still confused by this publish/ directory. Why are we shipping >>> something which is not for publishing in our binary package? I've also >> not >>> heard of it before. >>> >>> Regards, >>> -- >>> Ilya Kasnacheev >>> >>> >>> вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn : >>> Ilya, > When I have also installed 3.1 and 2.0 Please try .NET SDK 2.1 to run tests. Yes, it went out of support last month, I've created a ticket [1]. > dotnet Apache.Ignite.dll That's correct, but should be done in platforms/dotnet/bin/netcoreapp2.0/publish, please try again. We should deal with duplicate binaries, I've created another ticket [2] > Why do we still ship Apache.Ignite.exe if it does not run? It runs on Windows. For Linux we ship Apache.Ignite.dll. I don't think any of this is a blocker for the current release. - Out-of-support SDK only affects those who build from source, and it >>> went out of support only recently - Duplicate binaries are there for a long time and no one was >> complaining [1] https://issues.apache.org/jira/browse/IGNITE-15504 [2] https://issues.apache.org/jira/browse/IGNITE-15505 On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev < ilya.kasnach...@gmail.com> wrote: > Hello! > > - 0.5 > > Installed DEB package, built binary from source, ran sqlline, built >>> .NET. > > I have failed to run .NET tests though. > > If I only install Current .NET, I get the following: > It was not possible to find any compatible framework version > The framework 'Microsoft.NETCore.App', version '2.0.0' was not found. > > > - The following frameworks were found: > > > 5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App] > > > You can resolve the problem by installing the specified framework >>> and/or > SDK. > > > The specified framework can be found at: > > > - > > >>> >> https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=2.0.0&arch=x64&rid=ubuntu.21.04-x64 > > When I have also installed 3.1 and 2.0, now I see: > > The active test run was aborted. Reason: Test host process crashed : >> No > usable version of the libssl was found > > It looks like we have to bump the permitted .NET version. > > From the slim binary package I also can't run .NET: > > ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0% > dotnet Apache.Ignite.dll > Error: > An assembly specified in the application dependencies manifest > (Apache.Ignite.deps.json) was not found: > package: 'System.Configuration.ConfigurationManager', version: >>> '4.4.0' > path: 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll' > > Do we have any instructions on how to run it under Linux? Why do we >>> still > ship Apache.Ignite.exe if it does not run? > > Regards, > -- > Ilya Kasnacheev > > > вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>: > >> check again, 15503 not cherry-pick, right? >> >> 在 2021/9/14 15:55, Shishkov Ilya 写道: Should the following two issue be merged into the ignite-2.11 branch? >>> Hi, as I see, both tickets are fixed in 2.10 and 2.11. >>> >>> вт, 14 сент. 2021 г. в 04:13, 18624049226<18624049...@163.com>: >>> Should the following two issue be merged into the ignite-2.11 branch? https://issues.apache.org/jira/browse/IGNITE-14404 https://issues.apache.org/jira/browse/IGNITE-15503 在 2021/9/13 17:12, Pavel Tupitsyn 写道: > +
A new feedback has been added : 8
A new feedback has been added, go to bugyard.io to see all the details... https://bugyard.io A new feedback has been added "this procedure is not working, also the following item is not completed 3.c " by ibrahim.altun View feedback https://app.bugyard.io/web/app/rycqZJDyY/f/6141f7cb8d3cd70014f5a7e7
Re: Request for new TC suite
Hi, Petr! I closed the ticket, Anton Vinogradov (thanks!) helped me and created the suite fast. It successfully ran. https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_IndexQuery?mode=branches On Tue, Sep 14, 2021 at 6:13 PM Maksim Timonin wrote: > Hi, Petr! > > Thanks for the response. I created a ticket [1] and assigned it to you. > Please have a look at it. If you have any questions please let me know. > > [1] https://issues.apache.org/jira/browse/IGNITE-15509 > > On Tue, Sep 14, 2021 at 6:05 PM Petr Ivanov wrote: > >> Hi, Maksim. >> >> >> File a ticket please and I will see it through. >> >> > On 14 Sep 2021, at 17:24, Maksim Timonin >> wrote: >> > >> > Hi, Igniters! >> > >> > This is a request for a new TC suite. This PR [1] introduces new >> > functionality (IndexQuery API). I've prepared a suite [1] with tests >> > related to this API. I'd like to have an opportunity to run those tests >> in >> > a separate TC suite. Currently for my PR only, and after merge it >> should be >> > enabled for the master branch. >> > >> > How can I do this? >> > >> > Thanks! >> > >> > [1] https://github.com/apache/ignite/pull/9118 >> > [2] Path is >> > >> ./modules/indexing/src/test/java/org/apache/ignite/cache/query/IndexQueryTestSuite.java >> >>
Re: Request for new TC suite
Actually, Index Query API suite is not part of RunAll. Let's fix this. On Wed, Sep 15, 2021 at 5:12 PM Maksim Timonin wrote: > Hi, Petr! > > I closed the ticket, Anton Vinogradov (thanks!) helped me and created the > suite fast. It successfully ran. > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_IndexQuery?mode=branches > > On Tue, Sep 14, 2021 at 6:13 PM Maksim Timonin > wrote: > > > Hi, Petr! > > > > Thanks for the response. I created a ticket [1] and assigned it to you. > > Please have a look at it. If you have any questions please let me know. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15509 > > > > On Tue, Sep 14, 2021 at 6:05 PM Petr Ivanov wrote: > > > >> Hi, Maksim. > >> > >> > >> File a ticket please and I will see it through. > >> > >> > On 14 Sep 2021, at 17:24, Maksim Timonin > >> wrote: > >> > > >> > Hi, Igniters! > >> > > >> > This is a request for a new TC suite. This PR [1] introduces new > >> > functionality (IndexQuery API). I've prepared a suite [1] with tests > >> > related to this API. I'd like to have an opportunity to run those > tests > >> in > >> > a separate TC suite. Currently for my PR only, and after merge it > >> should be > >> > enabled for the master branch. > >> > > >> > How can I do this? > >> > > >> > Thanks! > >> > > >> > [1] https://github.com/apache/ignite/pull/9118 > >> > [2] Path is > >> > > >> > ./modules/indexing/src/test/java/org/apache/ignite/cache/query/IndexQueryTestSuite.java > >> > >> > -- Best regards, Andrey V. Mashenkov
Re: Request for new TC suite
It has not to be before merge. After merge we will add it to RunAll. On Wed, Sep 15, 2021 at 5:25 PM Andrey Mashenkov wrote: > Actually, Index Query API suite is not part of RunAll. > Let's fix this. > > On Wed, Sep 15, 2021 at 5:12 PM Maksim Timonin > wrote: > > > Hi, Petr! > > > > I closed the ticket, Anton Vinogradov (thanks!) helped me and created the > > suite fast. It successfully ran. > > > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_IndexQuery?mode=branches > > > > On Tue, Sep 14, 2021 at 6:13 PM Maksim Timonin > > wrote: > > > > > Hi, Petr! > > > > > > Thanks for the response. I created a ticket [1] and assigned it to you. > > > Please have a look at it. If you have any questions please let me know. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15509 > > > > > > On Tue, Sep 14, 2021 at 6:05 PM Petr Ivanov > wrote: > > > > > >> Hi, Maksim. > > >> > > >> > > >> File a ticket please and I will see it through. > > >> > > >> > On 14 Sep 2021, at 17:24, Maksim Timonin > > >> wrote: > > >> > > > >> > Hi, Igniters! > > >> > > > >> > This is a request for a new TC suite. This PR [1] introduces new > > >> > functionality (IndexQuery API). I've prepared a suite [1] with tests > > >> > related to this API. I'd like to have an opportunity to run those > > tests > > >> in > > >> > a separate TC suite. Currently for my PR only, and after merge it > > >> should be > > >> > enabled for the master branch. > > >> > > > >> > How can I do this? > > >> > > > >> > Thanks! > > >> > > > >> > [1] https://github.com/apache/ignite/pull/9118 > > >> > [2] Path is > > >> > > > >> > > > ./modules/indexing/src/test/java/org/apache/ignite/cache/query/IndexQueryTestSuite.java > > >> > > >> > > > > > -- > Best regards, > Andrey V. Mashenkov >
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
+0.5 From me 1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16 a. build from source -- passed b. run examples -- passed 2. windows 10 x86_64 visual studio 2017 cmake 3.21 a. build from source using cmake --passed b. build odbc driver using cmake -- passed c. run examples -- passed Installing shipped ODBC 64 bit driver from binary install wizard -- passed Running odbc-example on it -- failed. If changed dll from step 2 -- passed. I suppose that something wrong with shipped ODBC driver binary. Please, could someone check it? ср, 15 сент. 2021 г. в 16:31, Nikolay Izhikov : > +1 (binding) > > > 15 сент. 2021 г., в 12:24, Alex Plehanov > написал(а): > > > > +1 > > > > Checked sha512 and sign of archives, built from sources, started a > cluster > > with a few nodes. > > > > вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn : > > > >> Ilya, > >> > >>> I'm still confused by this publish/ directory. Why are we shipping > >>> something which is not for publishing in our binary package? I've also > >> not > >>> heard of it before. > >> > >> I think this was introduced in 2.8.0 as part of [1]. > >> It is how the build process works by default and we just copy the entire > >> bin directory to the package, > >> while only publish subdir is actually required. > >> > >> We can probably drop support for legacy (unsupported) .NET versions in > the > >> next release and simplify our build process, I'll look into this. > >> > >> [1] https://issues.apache.org/jira/browse/IGNITE-11805 > >> > >> On Tue, Sep 14, 2021 at 6:12 PM Ilya Kasnacheev < > ilya.kasnach...@gmail.com > >>> > >> wrote: > >> > >>> Hello! > >>> > >>> + 0.5 > >>> > >>> I have got it to run with the following command: > >>> % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 > >>> Apache.Ignite.dll > >>> > >>> I'm still confused by this publish/ directory. Why are we shipping > >>> something which is not for publishing in our binary package? I've also > >> not > >>> heard of it before. > >>> > >>> Regards, > >>> -- > >>> Ilya Kasnacheev > >>> > >>> > >>> вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn : > >>> > Ilya, > > > When I have also installed 3.1 and 2.0 > Please try .NET SDK 2.1 to run tests. > Yes, it went out of support last month, I've created a ticket [1]. > > > > dotnet Apache.Ignite.dll > That's correct, but should be done > in platforms/dotnet/bin/netcoreapp2.0/publish, please try again. > We should deal with duplicate binaries, I've created another ticket > [2] > > > > Why do we still ship Apache.Ignite.exe if it does not run? > It runs on Windows. For Linux we ship Apache.Ignite.dll. > > > I don't think any of this is a blocker for the current release. > - Out-of-support SDK only affects those who build from source, and it > >>> went > out of support only recently > - Duplicate binaries are there for a long time and no one was > >> complaining > > > [1] https://issues.apache.org/jira/browse/IGNITE-15504 > [2] https://issues.apache.org/jira/browse/IGNITE-15505 > > On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> > wrote: > > > Hello! > > > > - 0.5 > > > > Installed DEB package, built binary from source, ran sqlline, built > >>> .NET. > > > > I have failed to run .NET tests though. > > > > If I only install Current .NET, I get the following: > > It was not possible to find any compatible framework version > > The framework 'Microsoft.NETCore.App', version '2.0.0' was not found. > > > > > > - The following frameworks were found: > > > > > > 5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App] > > > > > > You can resolve the problem by installing the specified framework > >>> and/or > > SDK. > > > > > > The specified framework can be found at: > > > > > > - > > > > > > >>> > >> > https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=2.0.0&arch=x64&rid=ubuntu.21.04-x64 > > > > When I have also installed 3.1 and 2.0, now I see: > > > > The active test run was aborted. Reason: Test host process crashed : > >> No > > usable version of the libssl was found > > > > It looks like we have to bump the permitted .NET version. > > > > From the slim binary package I also can't run .NET: > > > > ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0% > > dotnet Apache.Ignite.dll > > Error: > > An assembly specified in the application dependencies manifest > > (Apache.Ignite.deps.json) was not found: > > package: 'System.Configuration.ConfigurationManager', version: > >>> '4.4.0' > > path: > 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll' > > > > Do we have any instructions on how to run it und
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
Ok, found issue -- need to install VC++ 2010 redistributable package. Currently, it is not available on windows 10. I suppose, that this is a blocker. ср, 15 сент. 2021 г. в 20:07, Ivan Daschinsky : > +0.5 From me > 1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16 > a. build from source -- passed > b. run examples -- passed > > 2. windows 10 x86_64 visual studio 2017 cmake 3.21 > a. build from source using cmake --passed > b. build odbc driver using cmake -- passed > c. run examples -- passed > > Installing shipped ODBC 64 bit driver from binary install wizard -- passed > Running odbc-example on it -- failed. If changed dll from step 2 -- passed. > > I suppose that something wrong with shipped ODBC driver binary. > Please, could someone check it? > > ср, 15 сент. 2021 г. в 16:31, Nikolay Izhikov : > >> +1 (binding) >> >> > 15 сент. 2021 г., в 12:24, Alex Plehanov >> написал(а): >> > >> > +1 >> > >> > Checked sha512 and sign of archives, built from sources, started a >> cluster >> > with a few nodes. >> > >> > вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn : >> > >> >> Ilya, >> >> >> >>> I'm still confused by this publish/ directory. Why are we shipping >> >>> something which is not for publishing in our binary package? I've also >> >> not >> >>> heard of it before. >> >> >> >> I think this was introduced in 2.8.0 as part of [1]. >> >> It is how the build process works by default and we just copy the >> entire >> >> bin directory to the package, >> >> while only publish subdir is actually required. >> >> >> >> We can probably drop support for legacy (unsupported) .NET versions in >> the >> >> next release and simplify our build process, I'll look into this. >> >> >> >> [1] https://issues.apache.org/jira/browse/IGNITE-11805 >> >> >> >> On Tue, Sep 14, 2021 at 6:12 PM Ilya Kasnacheev < >> ilya.kasnach...@gmail.com >> >>> >> >> wrote: >> >> >> >>> Hello! >> >>> >> >>> + 0.5 >> >>> >> >>> I have got it to run with the following command: >> >>> % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 >> >>> Apache.Ignite.dll >> >>> >> >>> I'm still confused by this publish/ directory. Why are we shipping >> >>> something which is not for publishing in our binary package? I've also >> >> not >> >>> heard of it before. >> >>> >> >>> Regards, >> >>> -- >> >>> Ilya Kasnacheev >> >>> >> >>> >> >>> вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn : >> >>> >> Ilya, >> >> > When I have also installed 3.1 and 2.0 >> Please try .NET SDK 2.1 to run tests. >> Yes, it went out of support last month, I've created a ticket [1]. >> >> >> > dotnet Apache.Ignite.dll >> That's correct, but should be done >> in platforms/dotnet/bin/netcoreapp2.0/publish, please try again. >> We should deal with duplicate binaries, I've created another ticket >> [2] >> >> >> > Why do we still ship Apache.Ignite.exe if it does not run? >> It runs on Windows. For Linux we ship Apache.Ignite.dll. >> >> >> I don't think any of this is a blocker for the current release. >> - Out-of-support SDK only affects those who build from source, and it >> >>> went >> out of support only recently >> - Duplicate binaries are there for a long time and no one was >> >> complaining >> >> >> [1] https://issues.apache.org/jira/browse/IGNITE-15504 >> [2] https://issues.apache.org/jira/browse/IGNITE-15505 >> >> On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev < >> ilya.kasnach...@gmail.com> >> wrote: >> >> > Hello! >> > >> > - 0.5 >> > >> > Installed DEB package, built binary from source, ran sqlline, built >> >>> .NET. >> > >> > I have failed to run .NET tests though. >> > >> > If I only install Current .NET, I get the following: >> > It was not possible to find any compatible framework version >> > The framework 'Microsoft.NETCore.App', version '2.0.0' was not >> found. >> > >> > >> > - The following frameworks were found: >> > >> > >> > 5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App] >> > >> > >> > You can resolve the problem by installing the specified framework >> >>> and/or >> > SDK. >> > >> > >> > The specified framework can be found at: >> > >> > >> > - >> > >> > >> >> >>> >> >> >> https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=2.0.0&arch=x64&rid=ubuntu.21.04-x64 >> > >> > When I have also installed 3.1 and 2.0, now I see: >> > >> > The active test run was aborted. Reason: Test host process crashed : >> >> No >> > usable version of the libssl was found >> > >> > It looks like we have to bump the permitted .NET version. >> > >> > From the slim binary package I also can't run .NET: >> > >> > >> ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0% >> > dotnet Apache.Ignite.dl
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
>> Currently, it is not available on windows 10. I mean that it is impossible to download this redist package from official site, it was removed. It is weird to make user search this on suspicious sites over the internet. The main issue that we still build C++ packages on TC using Visual Studion 2010. ср, 15 сент. 2021 г. в 20:46, Ivan Daschinsky : > Ok, found issue -- need to install VC++ 2010 redistributable package. > Currently, it is not available on windows 10. > I suppose, that this is a blocker. > > ср, 15 сент. 2021 г. в 20:07, Ivan Daschinsky : > >> +0.5 From me >> 1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16 >> a. build from source -- passed >> b. run examples -- passed >> >> 2. windows 10 x86_64 visual studio 2017 cmake 3.21 >> a. build from source using cmake --passed >> b. build odbc driver using cmake -- passed >> c. run examples -- passed >> >> Installing shipped ODBC 64 bit driver from binary install wizard -- passed >> Running odbc-example on it -- failed. If changed dll from step 2 -- >> passed. >> >> I suppose that something wrong with shipped ODBC driver binary. >> Please, could someone check it? >> >> ср, 15 сент. 2021 г. в 16:31, Nikolay Izhikov : >> >>> +1 (binding) >>> >>> > 15 сент. 2021 г., в 12:24, Alex Plehanov >>> написал(а): >>> > >>> > +1 >>> > >>> > Checked sha512 and sign of archives, built from sources, started a >>> cluster >>> > with a few nodes. >>> > >>> > вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn : >>> > >>> >> Ilya, >>> >> >>> >>> I'm still confused by this publish/ directory. Why are we shipping >>> >>> something which is not for publishing in our binary package? I've >>> also >>> >> not >>> >>> heard of it before. >>> >> >>> >> I think this was introduced in 2.8.0 as part of [1]. >>> >> It is how the build process works by default and we just copy the >>> entire >>> >> bin directory to the package, >>> >> while only publish subdir is actually required. >>> >> >>> >> We can probably drop support for legacy (unsupported) .NET versions >>> in the >>> >> next release and simplify our build process, I'll look into this. >>> >> >>> >> [1] https://issues.apache.org/jira/browse/IGNITE-11805 >>> >> >>> >> On Tue, Sep 14, 2021 at 6:12 PM Ilya Kasnacheev < >>> ilya.kasnach...@gmail.com >>> >>> >>> >> wrote: >>> >> >>> >>> Hello! >>> >>> >>> >>> + 0.5 >>> >>> >>> >>> I have got it to run with the following command: >>> >>> % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 >>> >>> Apache.Ignite.dll >>> >>> >>> >>> I'm still confused by this publish/ directory. Why are we shipping >>> >>> something which is not for publishing in our binary package? I've >>> also >>> >> not >>> >>> heard of it before. >>> >>> >>> >>> Regards, >>> >>> -- >>> >>> Ilya Kasnacheev >>> >>> >>> >>> >>> >>> вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn : >>> >>> >>> Ilya, >>> >>> > When I have also installed 3.1 and 2.0 >>> Please try .NET SDK 2.1 to run tests. >>> Yes, it went out of support last month, I've created a ticket [1]. >>> >>> >>> > dotnet Apache.Ignite.dll >>> That's correct, but should be done >>> in platforms/dotnet/bin/netcoreapp2.0/publish, please try again. >>> We should deal with duplicate binaries, I've created another ticket >>> [2] >>> >>> >>> > Why do we still ship Apache.Ignite.exe if it does not run? >>> It runs on Windows. For Linux we ship Apache.Ignite.dll. >>> >>> >>> I don't think any of this is a blocker for the current release. >>> - Out-of-support SDK only affects those who build from source, and >>> it >>> >>> went >>> out of support only recently >>> - Duplicate binaries are there for a long time and no one was >>> >> complaining >>> >>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-15504 >>> [2] https://issues.apache.org/jira/browse/IGNITE-15505 >>> >>> On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev < >>> ilya.kasnach...@gmail.com> >>> wrote: >>> >>> > Hello! >>> > >>> > - 0.5 >>> > >>> > Installed DEB package, built binary from source, ran sqlline, built >>> >>> .NET. >>> > >>> > I have failed to run .NET tests though. >>> > >>> > If I only install Current .NET, I get the following: >>> > It was not possible to find any compatible framework version >>> > The framework 'Microsoft.NETCore.App', version '2.0.0' was not >>> found. >>> > >>> > >>> > - The following frameworks were found: >>> > >>> > >>> > 5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App] >>> > >>> > >>> > You can resolve the problem by installing the specified framework >>> >>> and/or >>> > SDK. >>> > >>> > >>> > The specified framework can be found at: >>> > >>> > >>> > - >>> > >>> > >>> >>> >>> >>> >> >>> https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_ver
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
Ivan, Can you please clarify in detail what exactly should be fixed? I'm not familiar with running something from Ignite under the Windows environment. It's weird if something is not available on the official site, however available on mirrors. It's not good but not a crime but doesn't sound like a release blocker. Should we at least mentioned it on documentation pages? On Wed, 15 Sept 2021 at 20:50, Ivan Daschinsky wrote: > > >> Currently, it is not available on windows 10. > I mean that it is impossible to download this redist package from official > site, it was removed. > It is weird to make user search this on suspicious sites over the internet. > > The main issue that we still build C++ packages on TC using Visual > Studion 2010. > > ср, 15 сент. 2021 г. в 20:46, Ivan Daschinsky : > > > Ok, found issue -- need to install VC++ 2010 redistributable package. > > Currently, it is not available on windows 10. > > I suppose, that this is a blocker. > > > > ср, 15 сент. 2021 г. в 20:07, Ivan Daschinsky : > > > >> +0.5 From me > >> 1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16 > >> a. build from source -- passed > >> b. run examples -- passed > >> > >> 2. windows 10 x86_64 visual studio 2017 cmake 3.21 > >> a. build from source using cmake --passed > >> b. build odbc driver using cmake -- passed > >> c. run examples -- passed > >> > >> Installing shipped ODBC 64 bit driver from binary install wizard -- passed > >> Running odbc-example on it -- failed. If changed dll from step 2 -- > >> passed. > >> > >> I suppose that something wrong with shipped ODBC driver binary. > >> Please, could someone check it? > >> > >> ср, 15 сент. 2021 г. в 16:31, Nikolay Izhikov : > >> > >>> +1 (binding) > >>> > >>> > 15 сент. 2021 г., в 12:24, Alex Plehanov > >>> написал(а): > >>> > > >>> > +1 > >>> > > >>> > Checked sha512 and sign of archives, built from sources, started a > >>> cluster > >>> > with a few nodes. > >>> > > >>> > вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn : > >>> > > >>> >> Ilya, > >>> >> > >>> >>> I'm still confused by this publish/ directory. Why are we shipping > >>> >>> something which is not for publishing in our binary package? I've > >>> also > >>> >> not > >>> >>> heard of it before. > >>> >> > >>> >> I think this was introduced in 2.8.0 as part of [1]. > >>> >> It is how the build process works by default and we just copy the > >>> entire > >>> >> bin directory to the package, > >>> >> while only publish subdir is actually required. > >>> >> > >>> >> We can probably drop support for legacy (unsupported) .NET versions > >>> in the > >>> >> next release and simplify our build process, I'll look into this. > >>> >> > >>> >> [1] https://issues.apache.org/jira/browse/IGNITE-11805 > >>> >> > >>> >> On Tue, Sep 14, 2021 at 6:12 PM Ilya Kasnacheev < > >>> ilya.kasnach...@gmail.com > >>> >>> > >>> >> wrote: > >>> >> > >>> >>> Hello! > >>> >>> > >>> >>> + 0.5 > >>> >>> > >>> >>> I have got it to run with the following command: > >>> >>> % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 > >>> >>> Apache.Ignite.dll > >>> >>> > >>> >>> I'm still confused by this publish/ directory. Why are we shipping > >>> >>> something which is not for publishing in our binary package? I've > >>> also > >>> >> not > >>> >>> heard of it before. > >>> >>> > >>> >>> Regards, > >>> >>> -- > >>> >>> Ilya Kasnacheev > >>> >>> > >>> >>> > >>> >>> вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn : > >>> >>> > >>> Ilya, > >>> > >>> > When I have also installed 3.1 and 2.0 > >>> Please try .NET SDK 2.1 to run tests. > >>> Yes, it went out of support last month, I've created a ticket [1]. > >>> > >>> > >>> > dotnet Apache.Ignite.dll > >>> That's correct, but should be done > >>> in platforms/dotnet/bin/netcoreapp2.0/publish, please try again. > >>> We should deal with duplicate binaries, I've created another ticket > >>> [2] > >>> > >>> > >>> > Why do we still ship Apache.Ignite.exe if it does not run? > >>> It runs on Windows. For Linux we ship Apache.Ignite.dll. > >>> > >>> > >>> I don't think any of this is a blocker for the current release. > >>> - Out-of-support SDK only affects those who build from source, and > >>> it > >>> >>> went > >>> out of support only recently > >>> - Duplicate binaries are there for a long time and no one was > >>> >> complaining > >>> > >>> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-15504 > >>> [2] https://issues.apache.org/jira/browse/IGNITE-15505 > >>> > >>> On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev < > >>> ilya.kasnach...@gmail.com> > >>> wrote: > >>> > >>> > Hello! > >>> > > >>> > - 0.5 > >>> > > >>> > Installed DEB package, built binary from source, ran sqlline, built > >>> >>> .NET. > >>> > > >>> > I have failed to run .NET tests though. > >>> > > >>> > If I only install Current
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
>> Can you please clarify in detail what exactly should be fixed? Sure. The ODBC driver is a native shared library, it depends on C++ runtime. We ship one builded using Visual C++ 2010, so runtime libraries should be installed first. These runtime libraries are usually shipped in so called redistributable packages. Visual C++ 2010 is deprecated and currently it is quite hard even to find even a redistributable package on official sites. Usually, google returns a list of malware suspicious warez sites. Fortunately, I've found the download link on official visual studio site, but it was not trivial to find it [1] So, 1. Shipped in binary distribution driver works, if redistributable package is installed [1] 2. We should mention this fact in documentation 3. We should consider switching to Visual C++ 2017 [1] -- https://visualstudio.microsoft.com/vs/older-downloads/#visual-studio-2010-vc-redistributable чт, 16 сент. 2021 г. в 00:42, Maxim Muzafarov : > Ivan, > > Can you please clarify in detail what exactly should be fixed? I'm not > familiar with running something from Ignite under the Windows > environment. It's weird if something is not available on the official > site, however available on mirrors. It's not good but not a crime but > doesn't sound like a release blocker. Should we at least mentioned it > on documentation pages? > > On Wed, 15 Sept 2021 at 20:50, Ivan Daschinsky > wrote: > > > > >> Currently, it is not available on windows 10. > > I mean that it is impossible to download this redist package from > official > > site, it was removed. > > It is weird to make user search this on suspicious sites over the > internet. > > > > The main issue that we still build C++ packages on TC using Visual > > Studion 2010. > > > > ср, 15 сент. 2021 г. в 20:46, Ivan Daschinsky : > > > > > Ok, found issue -- need to install VC++ 2010 redistributable package. > > > Currently, it is not available on windows 10. > > > I suppose, that this is a blocker. > > > > > > ср, 15 сент. 2021 г. в 20:07, Ivan Daschinsky : > > > > > >> +0.5 From me > > >> 1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16 > > >> a. build from source -- passed > > >> b. run examples -- passed > > >> > > >> 2. windows 10 x86_64 visual studio 2017 cmake 3.21 > > >> a. build from source using cmake --passed > > >> b. build odbc driver using cmake -- passed > > >> c. run examples -- passed > > >> > > >> Installing shipped ODBC 64 bit driver from binary install wizard -- > passed > > >> Running odbc-example on it -- failed. If changed dll from step 2 -- > > >> passed. > > >> > > >> I suppose that something wrong with shipped ODBC driver binary. > > >> Please, could someone check it? > > >> > > >> ср, 15 сент. 2021 г. в 16:31, Nikolay Izhikov : > > >> > > >>> +1 (binding) > > >>> > > >>> > 15 сент. 2021 г., в 12:24, Alex Plehanov > > >>> написал(а): > > >>> > > > >>> > +1 > > >>> > > > >>> > Checked sha512 and sign of archives, built from sources, started a > > >>> cluster > > >>> > with a few nodes. > > >>> > > > >>> > вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn >: > > >>> > > > >>> >> Ilya, > > >>> >> > > >>> >>> I'm still confused by this publish/ directory. Why are we > shipping > > >>> >>> something which is not for publishing in our binary package? I've > > >>> also > > >>> >> not > > >>> >>> heard of it before. > > >>> >> > > >>> >> I think this was introduced in 2.8.0 as part of [1]. > > >>> >> It is how the build process works by default and we just copy the > > >>> entire > > >>> >> bin directory to the package, > > >>> >> while only publish subdir is actually required. > > >>> >> > > >>> >> We can probably drop support for legacy (unsupported) .NET > versions > > >>> in the > > >>> >> next release and simplify our build process, I'll look into this. > > >>> >> > > >>> >> [1] https://issues.apache.org/jira/browse/IGNITE-11805 > > >>> >> > > >>> >> On Tue, Sep 14, 2021 at 6:12 PM Ilya Kasnacheev < > > >>> ilya.kasnach...@gmail.com > > >>> >>> > > >>> >> wrote: > > >>> >> > > >>> >>> Hello! > > >>> >>> > > >>> >>> + 0.5 > > >>> >>> > > >>> >>> I have got it to run with the following command: > > >>> >>> % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 > > >>> >>> Apache.Ignite.dll > > >>> >>> > > >>> >>> I'm still confused by this publish/ directory. Why are we > shipping > > >>> >>> something which is not for publishing in our binary package? I've > > >>> also > > >>> >> not > > >>> >>> heard of it before. > > >>> >>> > > >>> >>> Regards, > > >>> >>> -- > > >>> >>> Ilya Kasnacheev > > >>> >>> > > >>> >>> > > >>> >>> вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn < > ptupit...@apache.org>: > > >>> >>> > > >>> Ilya, > > >>> > > >>> > When I have also installed 3.1 and 2.0 > > >>> Please try .NET SDK 2.1 to run tests. > > >>> Yes, it went out of support last month, I've created a ticket > [1]. > > >>> > > >>> > > >>> > dotnet Apache.Ignite.dll > > >>> That's correct, but s
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
So +1 for me, checked all C++ and ODBC drivers on ubuntu 20.04 and windows 10 x86_64 чт, 16 сент. 2021 г. в 09:35, Ivan Daschinsky : > >> Can you please clarify in detail what exactly should be fixed? > Sure. The ODBC driver is a native shared library, it depends on C++ > runtime. > We ship one builded using Visual C++ 2010, so runtime libraries should be > installed first. > These runtime libraries are usually shipped in so called redistributable > packages. > Visual C++ 2010 is deprecated and currently it is quite hard even to find > even a redistributable package on official sites. > Usually, google returns a list of malware suspicious warez sites. > > Fortunately, I've found the download link on official visual studio site, > but it was not trivial to find it [1] > > So, > 1. Shipped in binary distribution driver works, if redistributable package > is installed [1] > 2. We should mention this fact in documentation > 3. We should consider switching to Visual C++ 2017 > > > [1] -- > https://visualstudio.microsoft.com/vs/older-downloads/#visual-studio-2010-vc-redistributable > > чт, 16 сент. 2021 г. в 00:42, Maxim Muzafarov : > >> Ivan, >> >> Can you please clarify in detail what exactly should be fixed? I'm not >> familiar with running something from Ignite under the Windows >> environment. It's weird if something is not available on the official >> site, however available on mirrors. It's not good but not a crime but >> doesn't sound like a release blocker. Should we at least mentioned it >> on documentation pages? >> >> On Wed, 15 Sept 2021 at 20:50, Ivan Daschinsky >> wrote: >> > >> > >> Currently, it is not available on windows 10. >> > I mean that it is impossible to download this redist package from >> official >> > site, it was removed. >> > It is weird to make user search this on suspicious sites over the >> internet. >> > >> > The main issue that we still build C++ packages on TC using Visual >> > Studion 2010. >> > >> > ср, 15 сент. 2021 г. в 20:46, Ivan Daschinsky : >> > >> > > Ok, found issue -- need to install VC++ 2010 redistributable package. >> > > Currently, it is not available on windows 10. >> > > I suppose, that this is a blocker. >> > > >> > > ср, 15 сент. 2021 г. в 20:07, Ivan Daschinsky : >> > > >> > >> +0.5 From me >> > >> 1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16 >> > >> a. build from source -- passed >> > >> b. run examples -- passed >> > >> >> > >> 2. windows 10 x86_64 visual studio 2017 cmake 3.21 >> > >> a. build from source using cmake --passed >> > >> b. build odbc driver using cmake -- passed >> > >> c. run examples -- passed >> > >> >> > >> Installing shipped ODBC 64 bit driver from binary install wizard -- >> passed >> > >> Running odbc-example on it -- failed. If changed dll from step 2 -- >> > >> passed. >> > >> >> > >> I suppose that something wrong with shipped ODBC driver binary. >> > >> Please, could someone check it? >> > >> >> > >> ср, 15 сент. 2021 г. в 16:31, Nikolay Izhikov : >> > >> >> > >>> +1 (binding) >> > >>> >> > >>> > 15 сент. 2021 г., в 12:24, Alex Plehanov > > >> > >>> написал(а): >> > >>> > >> > >>> > +1 >> > >>> > >> > >>> > Checked sha512 and sign of archives, built from sources, started a >> > >>> cluster >> > >>> > with a few nodes. >> > >>> > >> > >>> > вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn < >> ptupit...@apache.org>: >> > >>> > >> > >>> >> Ilya, >> > >>> >> >> > >>> >>> I'm still confused by this publish/ directory. Why are we >> shipping >> > >>> >>> something which is not for publishing in our binary package? >> I've >> > >>> also >> > >>> >> not >> > >>> >>> heard of it before. >> > >>> >> >> > >>> >> I think this was introduced in 2.8.0 as part of [1]. >> > >>> >> It is how the build process works by default and we just copy the >> > >>> entire >> > >>> >> bin directory to the package, >> > >>> >> while only publish subdir is actually required. >> > >>> >> >> > >>> >> We can probably drop support for legacy (unsupported) .NET >> versions >> > >>> in the >> > >>> >> next release and simplify our build process, I'll look into this. >> > >>> >> >> > >>> >> [1] https://issues.apache.org/jira/browse/IGNITE-11805 >> > >>> >> >> > >>> >> On Tue, Sep 14, 2021 at 6:12 PM Ilya Kasnacheev < >> > >>> ilya.kasnach...@gmail.com >> > >>> >>> >> > >>> >> wrote: >> > >>> >> >> > >>> >>> Hello! >> > >>> >>> >> > >>> >>> + 0.5 >> > >>> >>> >> > >>> >>> I have got it to run with the following command: >> > >>> >>> % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 >> > >>> >>> Apache.Ignite.dll >> > >>> >>> >> > >>> >>> I'm still confused by this publish/ directory. Why are we >> shipping >> > >>> >>> something which is not for publishing in our binary package? >> I've >> > >>> also >> > >>> >> not >> > >>> >>> heard of it before. >> > >>> >>> >> > >>> >>> Regards, >> > >>> >>> -- >> > >>> >>> Ilya Kasnacheev >> > >>> >>> >> > >>> >>> >> > >>> >>> вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn < >> ptupit...@apache.org>: >>
[RESULT] [VOTE] Release pyignite 0.5.2-rc0
Hello, Igniters! Release pyignite-0.5.2-rc0 has been accepted The votes received: 3 "+1" binding votes 3 "+1" votes There is neither "+0" nor "-1" Here the votes received: - +1 Pavel Tupitsyn (binding) - +1 Nickolay Izhikov (binding) - +1 Maxim Muzafarov (binding) - +1 Ilya Shishkov - +1 Aleksandr Nikolaev - +1 Ivan Daschinsky New release will be announced soon
