mikemccand merged PR #98:
URL: https://github.com/apache/lucene-jira-archive/pull/98
--
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...@
mikemccand commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1200386255
> Thank you for sending the call for help.
YW -- it's the least I could do!!
I will also send a call for help for users (not just devs) to record their
jira id
mikemccand commented on code in PR #97:
URL: https://github.com/apache/lucene-jira-archive/pull/97#discussion_r933956367
##
migration/src/jira_util.py:
##
@@ -289,34 +289,34 @@ def repl_att(m: re.Match):
return text
-def embed_gh_issue_link(text: str, issue_id_map: dict
mikemccand commented on code in PR #97:
URL: https://github.com/apache/lucene-jira-archive/pull/97#discussion_r933956494
##
migration/src/jira_util.py:
##
@@ -289,34 +289,34 @@ def repl_att(m: re.Match):
return text
-def embed_gh_issue_link(text: str, issue_id_map: dict
mikemccand opened a new pull request, #101:
URL: https://github.com/apache/lucene-jira-archive/pull/101
I am new to these type annotations so please double-check that I didn't make
things worse!
--
This is an automated message from the Apache Git Service.
To respond to the message, please
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200393717
Hmm, the thing is, this form `[~thetaphi]` seems to happen quite often:
```
(.venv) beast3:migration[main]$ grep -ri "\[\~thetaphi\]" jira-dump | wc
955
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200394506
It happens for some other users too:
```
(.venv) beast3:migration[main]$ grep -ri "\[\~" github-import-data/ | wc
331 15583 214620
```
E.g.:
mikemccand commented on issue #94:
URL:
https://github.com/apache/lucene-jira-archive/issues/94#issuecomment-1200394596
I think this is resolved now?
--
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
mikemccand closed issue #94: We need to escape #NN when it appears in Jira
comment/description
URL: https://github.com/apache/lucene-jira-archive/issues/94
--
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
mikemccand closed issue #92: Don't substitute the GitHub issue link in the
Legacy Jira header
URL: https://github.com/apache/lucene-jira-archive/issues/92
--
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 g
mikemccand commented on issue #92:
URL:
https://github.com/apache/lucene-jira-archive/issues/92#issuecomment-1200394697
OK I think we can resolve this now? Thanks @mocobeta!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub an
mikemccand commented on issue #93:
URL:
https://github.com/apache/lucene-jira-archive/issues/93#issuecomment-1200395212
We might be able to work around this by inserting an extra newline when we
detect `^> ...` at the start of a line?
So from the above issue, we would map:
```
mikemccand commented on code in PR #99:
URL: https://github.com/apache/lucene-jira-archive/pull/99#discussion_r933963119
##
migration/src/jira_util.py:
##
@@ -228,8 +228,8 @@ def extract_pull_requests(o: dict) -> list[str]:
REGEX_CRLF = re.compile(r"\r\n")
REGEX_JIRA_KEY = r
mocobeta commented on code in PR #97:
URL: https://github.com/apache/lucene-jira-archive/pull/97#discussion_r933963135
##
migration/src/jira_util.py:
##
@@ -289,34 +289,34 @@ def repl_att(m: re.Match):
return text
-def embed_gh_issue_link(text: str, issue_id_map: dict[s
mocobeta commented on code in PR #97:
URL: https://github.com/apache/lucene-jira-archive/pull/97#discussion_r933963266
##
migration/src/jira_util.py:
##
@@ -289,34 +289,34 @@ def repl_att(m: re.Match):
return text
-def embed_gh_issue_link(text: str, issue_id_map: dict[s
mocobeta commented on code in PR #97:
URL: https://github.com/apache/lucene-jira-archive/pull/97#discussion_r933963266
##
migration/src/jira_util.py:
##
@@ -289,34 +289,34 @@ def repl_att(m: re.Match):
return text
-def embed_gh_issue_link(text: str, issue_id_map: dict[s
uschindler commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200396083
"thetaphi" is "uschindler". This was changed when ASF changed to use LDAP
for committer access to JIRA. The other account was deleted (I think) or we
renamed it, but a JI
mocobeta commented on code in PR #97:
URL: https://github.com/apache/lucene-jira-archive/pull/97#discussion_r933963266
##
migration/src/jira_util.py:
##
@@ -289,34 +289,34 @@ def repl_att(m: re.Match):
return text
-def embed_gh_issue_link(text: str, issue_id_map: dict[s
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200396433
OK! Mystery explained then. Apache users (committers+) who had different
Jira id than their Apache id, got renamed in the LDAP migration.
But this left some broke
mikemccand commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200396473
Thanks for the history lesson @uschindler.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
UR
mikemccand commented on issue #95:
URL:
https://github.com/apache/lucene-jira-archive/issues/95#issuecomment-1200396809
OK I'll resolve this issue as a duplicate of #96 where more discussion has
happened. Thanks @mocobeta.
--
This is an automated message from the Apache Git Service.
To
mikemccand closed issue #95: Are we missing conversion of some ~jira-id
references?
URL: https://github.com/apache/lucene-jira-archive/issues/95
--
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 s
mikemccand commented on issue #89:
URL:
https://github.com/apache/lucene-jira-archive/issues/89#issuecomment-1200397024
OK I confirmed that we can just escape the `~` with a backslash:
Broken (copied from the Jira issue):
For Lucene 3.6.2, the timings settle down to 200~300 wit
mikemccand commented on issue #95:
URL:
https://github.com/apache/lucene-jira-archive/issues/95#issuecomment-1200397190
Duplicate of #96
--
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 speci
mikemccand commented on issue #95:
URL:
https://github.com/apache/lucene-jira-archive/issues/95#issuecomment-1200397223
Duplicate of #96
--
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 speci
mikemccand commented on issue #95:
URL:
https://github.com/apache/lucene-jira-archive/issues/95#issuecomment-1200397309
Well, I tried to mark this as duplicate not as "Completed". But, I failed.
--
This is an automated message from the Apache Git Service.
To respond to the message, pleas
uschindler commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200397331
See: https://issues.apache.org/jira/browse/INFRA-19087
There were many renames and ASF infra asked to open issues like the above.
--
This is an automated message
mocobeta commented on code in PR #97:
URL: https://github.com/apache/lucene-jira-archive/pull/97#discussion_r933964756
##
migration/src/jira_util.py:
##
@@ -289,34 +289,34 @@ def repl_att(m: re.Match):
return text
-def embed_gh_issue_link(text: str, issue_id_map: dict[s
mocobeta commented on code in PR #97:
URL: https://github.com/apache/lucene-jira-archive/pull/97#discussion_r933964769
##
migration/src/jira_util.py:
##
@@ -289,34 +289,34 @@ def repl_att(m: re.Match):
return text
-def embed_gh_issue_link(text: str, issue_id_map: dict[s
mocobeta commented on code in PR #97:
URL: https://github.com/apache/lucene-jira-archive/pull/97#discussion_r933965142
##
migration/src/jira_util.py:
##
@@ -289,34 +289,34 @@ def repl_att(m: re.Match):
return text
-def embed_gh_issue_link(text: str, issue_id_map: dict[s
mocobeta commented on code in PR #99:
URL: https://github.com/apache/lucene-jira-archive/pull/99#discussion_r933965570
##
migration/src/jira_util.py:
##
@@ -228,8 +228,8 @@ def extract_pull_requests(o: dict) -> list[str]:
REGEX_CRLF = re.compile(r"\r\n")
REGEX_JIRA_KEY = re.
mocobeta commented on issue #89:
URL:
https://github.com/apache/lucene-jira-archive/issues/89#issuecomment-1200399822
I know which code we should change - will take a look.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
mocobeta merged PR #101:
URL: https://github.com/apache/lucene-jira-archive/pull/101
--
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...@
mocobeta commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200400393
> @mocobeta if you agree, I can try to work up a PR with these "orphaned"
jira IDs by just adding to the mappings file?
Yes I think it'd be great if we could add the
mikemccand commented on issue #78:
URL:
https://github.com/apache/lucene-jira-archive/issues/78#issuecomment-1200400556
I started a very rough draft here:
https://docs.google.com/document/d/10m6--f7vbU9OC_SfANN6vbNDvu25COMm0Jc4wnggNV0/edit#
Feel free to edit.
--
This is an automat
mocobeta opened a new issue, #102:
URL: https://github.com/apache/lucene-jira-archive/issues/102
I've tried to identify committers'
(https://projects.apache.org/committee.html?lucene) GitHub accounts as far as
possible. Several accounts were found (I added them to the mapping file), but
th
mocobeta commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200406925
But the situation is not any worse than in Jira - anyway, the orphaned
mentions are not actual mentions in Jira. I don't think this has priority.
--
This is an automated
uschindler commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200411999
> But the situation is not any worse than in Jira - anyway, the orphaned
mentions are not actual mentions in Jira. I don't think this has priority in
terms of migration.
mocobeta commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1200412428
This list includes people who are/were very active in Lucene, but I gave up.
If you have any information please let me know. cc @mikemccand
--
This is an automa
mocobeta commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200412660
> I'd suggest this for my name: "thetaphi" -> "uschindler"
OK I will do this.
--
This is an automated message from the Apache Git Service.
To respond to the message
mocobeta commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200413200
I would rather try to seek help for #102 - I don't have any clues about this
and gave up.
--
This is an automated message from the Apache Git Service.
To respond to the m
mocobeta commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1200419598
> In fact, we should more generally announce our planned schedule to
java-user@ as well once we have a specific timeline planned.
I will make an announcement about the
uschindler commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1200460272
One posisbility: Grep through the whole history of the (old) lucene-solr
repository searching for their name as committer/author. If you found a hit,
copy the commit id
allnewcracksoftwares created LUCENE-10671:
-
Summary: Lucene
Key: LUCENE-10671
URL: https://issues.apache.org/jira/browse/LUCENE-10671
Project: Lucene - Core
Issue Type: Bug
mikemccand commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1200480219
Karl Wright is `daddywri` in both places (plus a couple email addresses) --
I'll push a change.
--
This is an automated message from the Apache Git Service.
To respon
mikemccand commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1200481031
> * Otis Gospodnetic
Otis is @otisg on GitHub (I recognize him) -- I'll add his mapping.
--
This is an automated message from the Apache Git Service.
To respond
msokolov commented on code in PR #1054:
URL: https://github.com/apache/lucene/pull/1054#discussion_r934048743
##
lucene/core/src/java/org/apache/lucene/codecs/lucene94/CompressingVectorValues.java:
##
@@ -0,0 +1,46 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) unde
mocobeta commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1200523814
Thank you @mikemccand.
> Otis is `@otisg` on GitHub (I recognize him) -- I'll add his mapping.
Sorry, I should have recognized it - actually the script found
mocobeta commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1200527835
> Karl Wright is daddywri in both places (plus a couple email addresses) --
I'll push a change.
For this mapping, it was impossible to detect it by the account sear
mocobeta commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1200545695
Manual account identification/verification is the most time- and
energy-consuming task in the entire work (it took two hours for me only for
<100 committers). I don't thi
mocobeta commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1200615093
> One posisbility: Grep through the whole history of the (old) lucene-solr
repository searching for their name as committer/author. If you found a hit,
copy the commit id
tang-hi commented on code in PR #1016:
URL: https://github.com/apache/lucene/pull/1016#discussion_r934125980
##
lucene/core/src/java/org/apache/lucene/util/automaton/Automaton.java:
##
@@ -616,7 +621,7 @@ public String toDot() {
appendCharString(t.max, b);
}
mocobeta commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1200718903
Seeing the case of "Karl Wright is daddywri" in #102, I feel like we have to
investigate all "orphaned" mentions. I'll try to write scripts that count the
number of occurre
tang-hi commented on PR #1016:
URL: https://github.com/apache/lucene/pull/1016#issuecomment-1200722990
> I filed #1053 to perhaps help people in figuring out where the
source/target files are. Resource regeneration is a mess but we've talked about
it before - it's not quite trivial to imple
54 matches
Mail list logo
