[GitHub] [lucene-jira-archive] ovalhub opened a new pull request, #71: Update account-map.csv.20220722.verified

2022-07-24 Thread GitBox
ovalhub opened a new pull request, #71: URL: https://github.com/apache/lucene-jira-archive/pull/71 Added mapping for va...@apache.org -- 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

[GitHub] [lucene-jira-archive] mocobeta merged pull request #71: Update account-map.csv.20220722.verified

2022-07-24 Thread GitBox
mocobeta merged PR #71: URL: https://github.com/apache/lucene-jira-archive/pull/71 -- 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

[GitHub] [lucene-jira-archive] mocobeta commented on pull request #71: Update account-map.csv.20220722.verified

2022-07-24 Thread GitBox
mocobeta commented on PR #71: URL: https://github.com/apache/lucene-jira-archive/pull/71#issuecomment-1193261692 Thank you @ovalhub -- 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

[GitHub] [lucene-jira-archive] mikemccand commented on issue #61: Should we carry over Jira "labels"?

2022-07-24 Thread GitBox
mikemccand commented on issue #61: URL: https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193281812 Thanks @mocobeta ! -- 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 spe

[GitHub] [lucene-jira-archive] mikemccand commented on issue #70: {{ X }} did not convert to backticks correctly?

2022-07-24 Thread GitBox
mikemccand commented on issue #70: URL: https://github.com/apache/lucene-jira-archive/issues/70#issuecomment-1193281961 OK weird but this is likely rare so let's do nothing? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [lucene-jira-archive] mikemccand closed issue #70: {{ X }} did not convert to backticks correctly?

2022-07-24 Thread GitBox
mikemccand closed issue #70: {{ X }} did not convert to backticks correctly? URL: https://github.com/apache/lucene-jira-archive/issues/70 -- 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

[GitHub] [lucene-jira-archive] mikemccand commented on issue #70: {{ X }} did not convert to backticks correctly?

2022-07-24 Thread GitBox
mikemccand commented on issue #70: URL: https://github.com/apache/lucene-jira-archive/issues/70#issuecomment-1193282048 Thanks for explaining it @mocobeta. -- 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

[GitHub] [lucene-jira-archive] mocobeta commented on issue #61: Should we carry over Jira "labels"?

2022-07-24 Thread GitBox
mocobeta commented on issue #61: URL: https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193285953 > But I think that is Search problem. And what we consider noise might be signal to people. Maybe people want to search for bugs related to `jvm` and they want `jvm bugs` t

[GitHub] [lucene-jira-archive] mocobeta commented on issue #61: Should we carry over Jira "labels"?

2022-07-24 Thread GitBox
mocobeta commented on issue #61: URL: https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193286815 Well, GitHub search result is not ranked by relevancy ("newest" sort is the default). -- This is an automated message from the Apache Git Service. To respond to the messa

[GitHub] [lucene-jira-archive] mikemccand commented on issue #61: Should we carry over Jira "labels"?

2022-07-24 Thread GitBox
mikemccand commented on issue #61: URL: https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193287224 > Well, GitHub search result is not ranked by relevancy ("newest" sort is the default). Ugh LOL. Maybe it will improve with time? If only it were open-source! I

[GitHub] [lucene-jira-archive] mikemccand commented on issue #61: Should we carry over Jira "labels"?

2022-07-24 Thread GitBox
mikemccand commented on issue #61: URL: https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193287560 > There are some Jira metadata that are not ported at all to GitHub labels such as `Priority`, `Resolution`, `Lucene Fields`. Thanks @mocobeta. I've been looking a

[GitHub] [lucene-jira-archive] mikemccand opened a new issue, #72: Should we migrate Legacy Jira Resolution?

2022-07-24 Thread GitBox
mikemccand opened a new issue, #72: URL: https://github.com/apache/lucene-jira-archive/issues/72 Spinoff of #61. I think Resolution has value. I wrote a quick Python script to count/sort them across all Jira issues: ``` import os import glob import json with_re

[GitHub] [lucene-jira-archive] mikemccand commented on issue #60: Invalid unicode character in conversion of comment

2022-07-24 Thread GitBox
mikemccand commented on issue #60: URL: https://github.com/apache/lucene-jira-archive/issues/60#issuecomment-1193288954 Sorry, I erased and regenerated my repo, breaking the above comment link. It is now [here](https://github.com/mikemccand/stargazers-migration-test/issues/329#issuecommen

[GitHub] [lucene-jira-archive] mikemccand commented on issue #60: Invalid unicode character in conversion of comment

2022-07-24 Thread GitBox
mikemccand commented on issue #60: URL: https://github.com/apache/lucene-jira-archive/issues/60#issuecomment-1193290388 > I'm not yet sure exactly how that `\u0010` is supposed to be interpreted - OK it looks like [it is hexadecimal](https://tools.ietf.org/id/draft-ietf-json-rfc4627b

[GitHub] [lucene-jira-archive] mikemccand commented on issue #60: Invalid unicode character in conversion of comment

2022-07-24 Thread GitBox
mikemccand commented on issue #60: URL: https://github.com/apache/lucene-jira-archive/issues/60#issuecomment-1193291103 Indeed, I can see that we converted it "correctly" (preserving the U+0010 character): ``` "body": "Patch is available but it involves a binary file change

[GitHub] [lucene-jira-archive] mikemccand commented on issue #60: Invalid unicode character in conversion of comment

2022-07-24 Thread GitBox
mikemccand commented on issue #60: URL: https://github.com/apache/lucene-jira-archive/issues/60#issuecomment-1193291357 Let's see what happens if I try to add this character myself: Patch is available but it involves a binary file change. So no easy to review and not easy to chec

[GitHub] [lucene-jira-archive] mikemccand commented on issue #60: Invalid unicode character in conversion of comment

2022-07-24 Thread GitBox
mikemccand commented on issue #60: URL: https://github.com/apache/lucene-jira-archive/issues/60#issuecomment-1193291405 Whoa, indeed, even if you try to enter this character, GitHub remaps it. I wonder what else they remap? -- This is an automated message from the Apache Git Service. To

[GitHub] [lucene-jira-archive] mocobeta opened a new pull request, #73: Port 'Resolution' as a label

2022-07-24 Thread GitBox
mocobeta opened a new pull request, #73: URL: https://github.com/apache/lucene-jira-archive/pull/73 Close #72 Resolved issue: ![Screenshot from 2022-07-24 19-42-11](https://user-images.githubusercontent.com/1825333/180643472-4b4f8c92-1ed3-406f-a25e-5a391a89c236.png) For

[GitHub] [lucene-jira-archive] mocobeta commented on issue #72: Should we migrate Legacy Jira Resolution?

2022-07-24 Thread GitBox
mocobeta commented on issue #72: URL: https://github.com/apache/lucene-jira-archive/issues/72#issuecomment-1193292176 > Maybe we could add `legacy-jira-resolution:X`? I opened #73, will merge this soon. -- This is an automated message from the Apache Git Service. To respond to the

[GitHub] [lucene-jira-archive] mocobeta merged pull request #73: Port 'Resolution' as a label

2022-07-24 Thread GitBox
mocobeta merged PR #73: URL: https://github.com/apache/lucene-jira-archive/pull/73 -- 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

[GitHub] [lucene-jira-archive] mocobeta closed issue #72: Should we migrate Legacy Jira Resolution?

2022-07-24 Thread GitBox
mocobeta closed issue #72: Should we migrate Legacy Jira Resolution? URL: https://github.com/apache/lucene-jira-archive/issues/72 -- 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.

[GitHub] [lucene-jira-archive] mocobeta commented on issue #60: Invalid unicode character in conversion of comment

2022-07-24 Thread GitBox
mocobeta commented on issue #60: URL: https://github.com/apache/lucene-jira-archive/issues/60#issuecomment-1193293896 Regarding to "\u0010", fortunately it's relatively rare. ``` migration $ find jira-dump -name "*.json" | xargs -I{} cat {} | grep "\u0010" | wc -l 13 ``` Not

[GitHub] [lucene-jira-archive] mikemccand commented on issue #72: Should we migrate Legacy Jira Resolution?

2022-07-24 Thread GitBox
mikemccand commented on issue #72: URL: https://github.com/apache/lucene-jira-archive/issues/72#issuecomment-1193299188 Wow, thanks @mocobeta!! -- 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 th

[GitHub] [lucene-jira-archive] mikemccand commented on issue #60: Invalid unicode character in conversion of comment

2022-07-24 Thread GitBox
mikemccand commented on issue #60: URL: https://github.com/apache/lucene-jira-archive/issues/60#issuecomment-1193300994 > Regarding to "\u0010", fortunately it's relatively rare. Phew, thanks for checking. Kinda crazy this exotic character occurs that many time in our Jira issues!

[GitHub] [lucene-jira-archive] mikemccand opened a new pull request, #74: Polish a few sharp edges that hit me when running remap_cross_issue_links.py

2022-07-24 Thread GitBox
mikemccand opened a new pull request, #74: URL: https://github.com/apache/lucene-jira-archive/pull/74 Just changed words presented to humans ;) No actual code change for the machines. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [lucene-jira-archive] mikemccand commented on issue #61: Should we carry over Jira "labels"?

2022-07-24 Thread GitBox
mikemccand commented on issue #61: URL: https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193307444 I was curious about the `Lucene Fields`, so I wrote up a quick aggregator of all populated fields on our Jira issues: ``` import os import glob import json

[GitHub] [lucene-jira-archive] mocobeta commented on issue #61: Should we carry over Jira "labels"?

2022-07-24 Thread GitBox
mocobeta commented on issue #61: URL: https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193312929 I think "Lucene Fields" has only two values - "New" and "Patch Available". ![Screenshot from 2022-07-24 21-49-22](https://user-images.githubusercontent.com/1825333/18064

[GitHub] [lucene-jira-archive] mocobeta commented on a diff in pull request #74: Polish a few sharp edges that hit me when running remap_cross_issue_links.py

2022-07-24 Thread GitBox
mocobeta commented on code in PR #74: URL: https://github.com/apache/lucene-jira-archive/pull/74#discussion_r928254467 ## migration/src/remap_cross_issue_links.py: ## @@ -68,11 +68,11 @@ def remap_issue_link_in_comments(issue_number: int, issue_id_map: dict[str, str] check

[GitHub] [lucene-jira-archive] mocobeta commented on pull request #74: Polish a few sharp edges that hit me when running remap_cross_issue_links.py

2022-07-24 Thread GitBox
mocobeta commented on PR #74: URL: https://github.com/apache/lucene-jira-archive/pull/74#issuecomment-1193314053 I'd merge this, thank you. -- 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 sp

[GitHub] [lucene-jira-archive] mocobeta merged pull request #74: Polish a few sharp edges that hit me when running remap_cross_issue_links.py

2022-07-24 Thread GitBox
mocobeta merged PR #74: URL: https://github.com/apache/lucene-jira-archive/pull/74 -- 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

[GitHub] [lucene] luyuncheng opened a new pull request, #1046: Reduce mem copy byte store2

2022-07-24 Thread GitBox
luyuncheng opened a new pull request, #1046: URL: https://github.com/apache/lucene/pull/1046 ### Description (or a Jira issue link if you have 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 ab

[GitHub] [lucene] luyuncheng closed pull request #1046: Reduce mem copy byte store2

2022-07-24 Thread GitBox
luyuncheng closed pull request #1046: Reduce mem copy byte store2 URL: https://github.com/apache/lucene/pull/1046 -- 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

[GitHub] [lucene] luyuncheng opened a new pull request, #1047: LUCENE-10661: Reduce memory copy in BytesStore

2022-07-24 Thread GitBox
luyuncheng opened a new pull request, #1047: URL: https://github.com/apache/lucene/pull/1047 This is derived from [LUCENE-10627](https://github.com/apache/lucene/pull/987) AND [LUCENE-10657](https://github.com/apache/lucene/pull/1034) The abstract method copyBytes in DataOutput have

[jira] [Created] (LUCENE-10661) Reduce memory copy in BytesStore

2022-07-24 Thread LuYunCheng (Jira)
LuYunCheng created LUCENE-10661: --- Summary: Reduce memory copy in BytesStore Key: LUCENE-10661 URL: https://issues.apache.org/jira/browse/LUCENE-10661 Project: Lucene - Core Issue Type: Improvem