mocobeta commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1186462422
Just a status update - I ran a full migration (on a private test repo) with
the latest `main`, randomly picked issues from old to new, and checked if those
are correctly conv
mocobeta opened a new pull request, #50:
URL: https://github.com/apache/lucene-jira-archive/pull/50
A follow-up of #42.
should be
mikemccand commented on PR #50:
URL:
https://github.com/apache/lucene-jira-archive/pull/50#issuecomment-1186468500
Wooot +1!
--
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.
mikemccand commented on PR #49:
URL:
https://github.com/apache/lucene-jira-archive/pull/49#issuecomment-1186469761
+1!
I think the screen shots are backwards maybe? The top one is the new one
(what this PR is doing) and bottom is the broken/old one?
Took me a bit to understan
mikemccand commented on PR #49:
URL:
https://github.com/apache/lucene-jira-archive/pull/49#issuecomment-1186470185
Also, I tried to dedup the `created on X updated on X` duplication (where X
is the same), but I think I failed to doing the comparison after converting to
date. I'll open a s
mikemccand commented on PR #49:
URL:
https://github.com/apache/lucene-jira-archive/pull/49#issuecomment-1186471419
OK sorry for the confusion -- now I think I understand -- the images ARE
correct. Should have let the caffeine sink it a little more before this ;)
@msokolov should not
mocobeta commented on PR #49:
URL:
https://github.com/apache/lucene-jira-archive/pull/49#issuecomment-1186471506
> I think the screen shots are backwards maybe? The top one is the new one
(what this PR is doing) and bottom is the broken/old one?
No, the bottom one is the new one - th
mikemccand commented on issue #37:
URL:
https://github.com/apache/lucene-jira-archive/issues/37#issuecomment-1186471839
We may never fully solve this mystery! Cold case!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
mocobeta merged PR #49:
URL: https://github.com/apache/lucene-jira-archive/pull/49
--
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: issues-unsubscr...@lu
mocobeta merged PR #50:
URL: https://github.com/apache/lucene-jira-archive/pull/50
--
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: issues-unsubscr...@lu
mikemccand commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1186474150
> It involves lots of REST API calls via the internet with a strict rate
limit, and to make matters worse, it is not an idempotent operation.
Hmm why is the script NO
[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567599#comment-17567599
]
Michael McCandless commented on LUCENE-10557:
-
I realized that the Infra te
[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567600#comment-17567600
]
Michael McCandless commented on LUCENE-10557:
-
Though, one small wrinkle we
mocobeta commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1186480043
> Hmm why is the script NOT idempotent? It remaps a `LUCENE-` link to a
`#` GitHub link right? If you ran it again, wouldn't it have nothing to
remap?
@mikemcc
[
https://issues.apache.org/jira/browse/LUCENE-10633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567602#comment-17567602
]
Michael McCandless commented on LUCENE-10633:
-
Good grief :) It is not eve
[
https://issues.apache.org/jira/browse/LUCENE-10633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567603#comment-17567603
]
Michael McCandless commented on LUCENE-10633:
-
Should we make that change t
mocobeta commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1186484087
> If you ran it again, wouldn't it have nothing to remap?
It's difficult (or at least cumbersome) to correctly determine if there is
already a remapped cross-issue link
[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567612#comment-17567612
]
Tomoko Uchida commented on LUCENE-10557:
The migration plan takes into account
[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567612#comment-17567612
]
Tomoko Uchida edited comment on LUCENE-10557 at 7/17/22 11:43 AM:
---
[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567630#comment-17567630
]
Michael McCandless commented on LUCENE-10557:
-
{quote}Again - I don't think
[
https://issues.apache.org/jira/browse/LUCENE-10633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567649#comment-17567649
]
Adrien Grand commented on LUCENE-10633:
---
Double yes [~mikemccand] ! I plan on ope
Lu Xugang created LUCENE-10656:
--
Summary: It is unnecessary that using `limit` to check boundary
Key: LUCENE-10656
URL: https://issues.apache.org/jira/browse/LUCENE-10656
Project: Lucene - Core
LuXugang opened a new pull request, #1027:
URL: https://github.com/apache/lucene/pull/1027
Follow-up discussion in https://github.com/apache/lucene/pull/102
--
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
hcqs33 closed pull request #1026: Fix error in TieredMergePolicy
URL: https://github.com/apache/lucene/pull/1026
--
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,
hcqs33 opened a new pull request, #1028:
URL: https://github.com/apache/lucene/pull/1028
Fix error in comparing between bytes of candidates and bytes of max merge.
It's wrong to use `candidateSize` rather than `currentCandidateBytes`
comparing with `maxMergeBytes`. Minor change to fix it.
madrob commented on issue #37:
URL:
https://github.com/apache/lucene-jira-archive/issues/37#issuecomment-1186731534
Some issues were probably moved to SOLR issues?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
[
https://issues.apache.org/jira/browse/LUCENE-10656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lu Xugang updated LUCENE-10656:
---
Description: follow-up discussion in
[https://github.com/apache/lucene/pull/1021] (was: follow-up
zacharymorn commented on PR #1018:
URL: https://github.com/apache/lucene/pull/1018#issuecomment-1186772006
> I can go ahead and update the corresponding tests to make this PR ready?
I've updated / added the tests, and also tried out the idea to use a
dedicated test query to ensure the
mocobeta opened a new pull request, #51:
URL: https://github.com/apache/lucene-jira-archive/pull/51
Close #11
This tries not to create wrong re-mapped cross-link issues.
Cross-link issues are created if:
- there is a space before Jira issue key, and space or punctuation afte
mocobeta merged PR #51:
URL: https://github.com/apache/lucene-jira-archive/pull/51
--
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: issues-unsubscr...@lu
mocobeta closed issue #11: Selectively create github cross-issue link
URL: https://github.com/apache/lucene-jira-archive/issues/11
--
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
jpountz commented on code in PR #1018:
URL: https://github.com/apache/lucene/pull/1018#discussion_r922987359
##
lucene/core/src/java/org/apache/lucene/search/BooleanWeight.java:
##
@@ -191,6 +191,66 @@ public long cost() {
// or null if it is not applicable
// pkg-private
mocobeta opened a new pull request, #52:
URL: https://github.com/apache/lucene-jira-archive/pull/52
#27
After cross-issue link remapping, Linked-issues and Sub-tasks look like this.
 {
// or null if it is not applicable
// pkg-priv
49 matches
Mail list logo
