Github user conniey closed the pull request at:
https://github.com/apache/lucenenet/pull/166
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
See here:
https://lucenenet.apache.org/docs/3.0.3/dc/dd1/_concurrent_merge_scheduler_8cs_source.html
We had to write this:
https://github.com/ayende/ravendb/blob/master/Raven.Database/Indexing/ErrorLoggingConcurrentMergeScheduler.cs
*Hibernating Rhinos Ltd *
Oren Eini* l CEO l *Mobile: +
GitHub user conniey opened a pull request:
https://github.com/apache/lucenenet/pull/166
Remove breaking projects from Portable solution
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/conniey/lucenenet removeBreakingProjects
Hi Wyatt.
Yes, there are two solutions in the move2dnx branch. The portable solution one
is at the root directory
https://github.com/conniey/lucenenet/blob/move2dnx/Lucene.Net.Portable.sln.
Just a warning, we haven't got all the projects building. We are locally
unloading projects that
Hi -- build guy checking in.
Yes, I think 2 solutions would work. No moral issues on my part about using
vs2015 for builds. Is it setup that way in the
https://github.com/conniey/lucenenet/tree/move2dnx repo? If so I can try a
few things and see how this would work over the weekend and let you
Hi Oren,
Thanks for letting me know about this! When you say "default merge scheduler",
do you mean ConcurrentMergeScheduler? Would you be able to tell me about a
scenario where the default merge scheduler would leak exceptions? Also, are
there a set of unit tests that test this?
Thanks,
Lucene.NET Community,
After spending more time with this code base we have a better idea of the best
way to approach migrating everything .NET core.
There are two types of work. The first is to removing/replacing external
dependencies that do not work on .NET Core. The second is only use
Build Lucene.NET :: Lucene.NET Core [master] #557 failed (Tests failed: 1,
passed: 2461, ignored: 107).
Agent: JetBrains-dotnet-agent02
Build results:
http://teamcity.codebetter.com/viewLog.html?buildId=214945=LuceneNet_Core
Failed Tests Summary:
Failed tests (1 test, alphabetically ordered)
Build Lucene.NET :: Lucene.NET Core Focused Tests [master] #155 successful .
Agent: JetBrains-dotnet-agent01
Build results:
http://teamcity.codebetter.com/viewLog.html?buildId=214948=LuceneNet_LuceneNetCoreFailingTests
Changes included (2 changes)
Github user asfgit closed the pull request at:
https://github.com/apache/lucenenet/pull/162
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/lucenenet/pull/161
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user synhershko commented on the pull request:
https://github.com/apache/lucenenet/pull/161#issuecomment-207031535
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user synhershko commented on the pull request:
https://github.com/apache/lucenenet/pull/162#issuecomment-207031319
Looks good, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user asfgit closed the pull request at:
https://github.com/apache/lucenenet/pull/164
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
14 matches
Mail list logo
