NightOwl888 commented on issue #827: URL: https://github.com/apache/lucenenet/issues/827#issuecomment-2566690600
> @NightOwl888 Can you provide more information on how to reproduce this one? As written, I inferred this to mean that if you have an environment variable named `tests:crashmode` that it would throw an exception, and I don't experience that behavior. The environment variable is just ignored, since it doesn't have the `lucene:` prefix. It also doesn't seem to be an issue if you accidentally request a SystemProperties key _with_ the prefix (where it should not have the prefix in code), it just won't have the value. Can you provide a stack trace of where this is coming from, or steps to reproduce? Maybe I'm just not understanding something. I took a look at this before, but I couldn't figure out how to reproduce it again. But do note that the environment variables were being specified as part of the `ProcessStartInfo` for `System.Process` when I was doing the testing in the `TestIndexWriterOnJRECrash` test. This would be retrieved using `SystemProperties.GetPropertyAsBoolean()` inside of Lucene.Net. > NOTE: System properties are currently being passed on the command line, which would need to be removed to add them as environment variables in the `ProcessStartInfo` instance. The production `IConfigurationFactory` setup is to use a custom environment variables provider (which I think works), but during testing it injects the `TestConfigurationFactory` which uses the stock `Microsoft.Extensions.Configuration.EnvironmentVariables` implementation, which in turn may have led to this error. However, feel free to close this if the error is not reproducible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@lucenenet.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
