lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Itamar Syn-Hershko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENENET-496) System.NotImplementedException occurred in Microsoft.VisualStudio.QualityTools.Common.dll
Date Sat, 21 Dec 2013 21:56:09 GMT

    [ https://issues.apache.org/jira/browse/LUCENENET-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13854945#comment-13854945
] 

Itamar Syn-Hershko commented on LUCENENET-496:
----------------------------------------------

Simon, I think this is left-overs from the Java version - I also don't think using Console.Out
makes any sense whatsoever.

I'm thinking we should move to using log4net to do those things, as a rule. Objections?

> System.NotImplementedException occurred in Microsoft.VisualStudio.QualityTools.Common.dll
> -----------------------------------------------------------------------------------------
>
>                 Key: LUCENENET-496
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-496
>             Project: Lucene.Net
>          Issue Type: Bug
>          Components: Lucene.Net Core
>    Affects Versions: Lucene.Net 2.9.4g
>         Environment: VS2010sp1 + mstest on win7 64-bit
>            Reporter: Nicklas Norling
>            Priority: Minor
>
> When enabling parallel tests in VS2010 one of our tests failed consistently with a weird
NotImplementedEsxception inside the MS tool.
> The following code is use Lucene.NET 2.9.4.1 from NuGet:
>             analyzer = new StandardAnalyzer(Lucene.Net.Util.Version.LUCENE_29);
>             parser = new QueryParser(Lucene.Net.Util.Version.LUCENE_29, "All", analyzer);
> The exception is thrown inside the new QueryParser call. This is the call stack:
> System.NotImplementedException was unhandled by user code
>   Message=The method or operation is not implemented.
>   Source=Microsoft.VisualStudio.QualityTools.Common
>   StackTrace:
>        at Microsoft.VisualStudio.TestTools.Common.EqtStringPerThreadWriter.get_Encoding()
>        at Lucene.Net.QueryParsers.QueryParserTokenManager.InitBlock()
>        at Lucene.Net.QueryParsers.QueryParserTokenManager..ctor(CharStream stream)
>        at Lucene.Net.QueryParsers.QueryParser..ctor(CharStream stream)
>        at Lucene.Net.QueryParsers.QueryParser..ctor(Version matchVersion, String f, Analyzer
a)
>        at AuthoringServer.SearchEngine.Searcher..ctor(SearchSettings settings) in [Our
code path]\Searcher.cs:line 45
>        at BuildUp_AuthoringServer.SearchEngine.Searcher(IBuilderContext )
>        at Microsoft.Practices.ObjectBuilder2.DynamicMethodBuildPlan.BuildUp(IBuilderContext
context)
>        at Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext
context)
>        at Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext
context)
> Do not know if this is a MS bug or if Lucene.NET should behave in a different way when
logging. Registering here for your judgement.
> Regards,
> Nicke



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message