You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by GitBox <gi...@apache.org> on 2021/01/29 23:52:46 UTC
[GitHub] [lucenenet] NightOwl888 opened a new issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
NightOwl888 opened a new issue #405:
URL: https://github.com/apache/lucenenet/issues/405
[This change](https://github.com/apache/lucenenet/pull/381/commits/c95ac72b2a50dd4d5fc887003df82bc6e2db1fb7) diverges from Java Lucene and shouldn't be necessary.
We run tests in `Release` mode with `Verbose` set to `false`, so in that case the problem is skipped. However, in `Debug` mode the problem crops up. We need to investigate why `Term` is sometimes `null` and formulate a fix.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [lucenenet] NightOwl888 commented on issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
Posted by GitBox <gi...@apache.org>.
NightOwl888 commented on issue #405:
URL: https://github.com/apache/lucenenet/issues/405#issuecomment-770112305
I suspect that https://github.com/apache/lucenenet/commit/1fed4fb2c8d37cdca9171d30a01c26cd3035134d might be where this problem began occurring.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [lucenenet] NightOwl888 commented on issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
Posted by GitBox <gi...@apache.org>.
NightOwl888 commented on issue #405:
URL: https://github.com/apache/lucenenet/issues/405#issuecomment-771999402
I apologize, I should have specified that the change is from PR #381 that hasn't been merged to `master`.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [lucenenet] rclabo commented on issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
Posted by GitBox <gi...@apache.org>.
rclabo commented on issue #405:
URL: https://github.com/apache/lucenenet/issues/405#issuecomment-771978544
It seems like the commit for [this change](https://github.com/apache/lucenenet/pull/381/commits/c95ac72b2a50dd4d5fc887003df82bc6e2db1fb7) got rolled back since it does not appear in the [commit history for TestDocTermOrds](https://github.com/apache/lucenenet/commits/master/src/Lucene.Net.Tests/Index/TestDocTermOrds.cs). Is that a valid understanding? If so, is there any way in GitHub to actually confirm the commit was applied on date A but rolled back on date B? Or is there some other explanation for not seeing that commit in the commit history? (Sorry for these kinds of basic questions, I'm still working on better understanding GitHub )
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [lucenenet] NightOwl888 commented on issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
Posted by GitBox <gi...@apache.org>.
NightOwl888 commented on issue #405:
URL: https://github.com/apache/lucenenet/issues/405#issuecomment-771062197
Great. I have assigned the issue to you. Thanks.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [lucenenet] NightOwl888 closed issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
Posted by GitBox <gi...@apache.org>.
NightOwl888 closed issue #405:
URL: https://github.com/apache/lucenenet/issues/405
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [lucenenet] rclabo commented on issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
Posted by GitBox <gi...@apache.org>.
rclabo commented on issue #405:
URL: https://github.com/apache/lucenenet/issues/405#issuecomment-771978544
It seems like the commit for [this change](https://github.com/apache/lucenenet/pull/381/commits/c95ac72b2a50dd4d5fc887003df82bc6e2db1fb7) got rolled back since it does not appear in the [commit history for TestDocTermOrds](https://github.com/apache/lucenenet/commits/master/src/Lucene.Net.Tests/Index/TestDocTermOrds.cs). Is that a valid understanding? If so, is there any way in GitHub to actually confirm the commit was applied on date A but rolled back on date B? Or is there some other explanation for not seeing that commit in the commit history? (Sorry for these kinds of basic questions, I'm still working on better understanding GitHub )
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [lucenenet] NightOwl888 edited a comment on issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
Posted by GitBox <gi...@apache.org>.
NightOwl888 edited a comment on issue #405:
URL: https://github.com/apache/lucenenet/issues/405#issuecomment-770112305
I suspect that https://github.com/apache/lucenenet/commit/11323a515f920e8779bc0209849b3479d3243235 might be where this problem began occurring.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [lucenenet] rclabo commented on issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
Posted by GitBox <gi...@apache.org>.
rclabo commented on issue #405:
URL: https://github.com/apache/lucenenet/issues/405#issuecomment-770982896
I'll do this one
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [lucenenet] NightOwl888 commented on issue #405: Determine why Term is null in TestDocTermOrds when using SeekExact(0)
Posted by GitBox <gi...@apache.org>.
NightOwl888 commented on issue #405:
URL: https://github.com/apache/lucenenet/issues/405#issuecomment-771999402
I apologize, I should have specified that the change is from PR #381 that hasn't been merged to `master`.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org