[GitHub] [lucene-jira-archive] mocobeta opened a new issue, #116: Embedded source code without markup is wrongly interpreted in Markdown
mocobeta opened a new issue, #116:
URL: https://github.com/apache/lucene-jira-archive/issues/116
I think it's impossible to address. Just wanted to raise an issue for a
heads-up.
In old issues sometimes bare source code or patches are embedded in issue
descriptions or comments without proper `{code}` markup. This causes disasters
in Markup but no way to fix it to me.
For example,
- https://github.com/mocobeta/forks-migration-test-2/issues/355
-
https://github.com/mocobeta/forks-migration-test-2/issues/356#issuecomment-1204749472
- https://github.com/mocobeta/forks-migration-test-2/issues/354
--
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...@lucene.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta closed issue #1: Fix markup conversion error
mocobeta closed issue #1: Fix markup conversion error URL: https://github.com/apache/lucene-jira-archive/issues/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. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #1: Fix markup conversion error
mocobeta commented on issue #1: URL: https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1207165658 I'm closing this - known conversion errors will be adderessed in follow-up issues (if it's possible to 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. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta closed issue #3: Create mapping on Jira user id -> GitHub account
mocobeta closed issue #3: Create mapping on Jira user id -> GitHub account URL: https://github.com/apache/lucene-jira-archive/issues/3 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #3: Create mapping on Jira user id -> GitHub account
mocobeta commented on issue #3: URL: https://github.com/apache/lucene-jira-archive/issues/3#issuecomment-1207165906 I'm closing this, but we'll accept improvements on mapping until the actual migration. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #5: Prepare complete migration script to GitHub issue from Jira (best effort)
mocobeta commented on issue #5: URL: https://github.com/apache/lucene-jira-archive/issues/5#issuecomment-1207166132 We confirmed the migration scripts generally work fine. I'm closing this. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta closed issue #5: Prepare complete migration script to GitHub issue from Jira (best effort)
mocobeta closed issue #5: Prepare complete migration script to GitHub issue from Jira (best effort) URL: https://github.com/apache/lucene-jira-archive/issues/5 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #12: Make a test set for improving markup conversion quality
mocobeta commented on issue #12: URL: https://github.com/apache/lucene-jira-archive/issues/12#issuecomment-1207166202 I'm closing this. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta closed issue #12: Make a test set for improving markup conversion quality
mocobeta closed issue #12: Make a test set for improving markup conversion quality URL: https://github.com/apache/lucene-jira-archive/issues/12 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #91: Can we strike-through issues that were resolved on migration?
mocobeta commented on issue #91: URL: https://github.com/apache/lucene-jira-archive/issues/91#issuecomment-1207166344 I'd leave this as won't 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. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #106: Inlined patches don't migrate correctly
mocobeta commented on issue #106: URL: https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-1207166962 I'd leave this as "won't fix" - these issues will be manually corrected afterward with the best effort. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #96: Some user references don't convert?
mocobeta commented on issue #96: URL: https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1207167065 Can we close this? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?
mocobeta commented on issue #104: URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1207167409 Before opening INFRA issues, I'll try to address issues I found in the latest migration test and run another full import. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene] kaivalnp commented on a diff in pull request #932: LUCENE-10559: Add Prefilter Option to KnnGraphTester
kaivalnp commented on code in PR #932:
URL: https://github.com/apache/lucene/pull/932#discussion_r939497872
##
lucene/core/src/test/org/apache/lucene/util/hnsw/KnnGraphTester.java:
##
@@ -730,4 +794,61 @@ protected int comparePivot(int j) {
return Float.compare(score[pivot], score[j]);
}
}
+
+ private static class SelectiveQuery extends Query {
+
+public float selectivity = 1f;
+private FixedBitSet selectedBits;
+private long cost;
+
+@SuppressForbidden(reason = "Uses Math.random()")
Review Comment:
@jtibshirani @msokolov Any suggestions/thoughts on this?
--
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...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta opened a new pull request, #117: Capture cross-issue link that appear at the beginning or a line
mocobeta opened a new pull request, #117: URL: https://github.com/apache/lucene-jira-archive/pull/117  In this description, "LUCENE-10654" should be remapped to github issue number `#NN` like this.  Closes #109. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta merged pull request #117: Capture cross-issue link that appear at the beginning or a line
mocobeta merged PR #117: URL: https://github.com/apache/lucene-jira-archive/pull/117 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta closed issue #109: Cross-issue link isn't remapped if it appears at the beggining of a line
mocobeta closed issue #109: Cross-issue link isn't remapped if it appears at the beggining of a line URL: https://github.com/apache/lucene-jira-archive/issues/109 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta opened a new pull request, #118: Refine regex to capture mentions before/after zenkaku punctuations
mocobeta opened a new pull request, #118: URL: https://github.com/apache/lucene-jira-archive/pull/118 I think we shouldn't apply any normalization such as full-width -> halfwidth but can try to refine the regex.  should be  -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta merged pull request #118: Refine regex to capture mentions before/after zenkaku punctuations
mocobeta merged PR #118: URL: https://github.com/apache/lucene-jira-archive/pull/118 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta closed issue #110: Mentions is not captured if it follows Zenkaku punctuations
mocobeta closed issue #110: Mentions is not captured if it follows Zenkaku punctuations URL: https://github.com/apache/lucene-jira-archive/issues/110 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta opened a new pull request, #119: Jira username can contain whitespaces
mocobeta opened a new pull request, #119: URL: https://github.com/apache/lucene-jira-archive/pull/119 The regex needs to support whitespaces.  should be  -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta merged pull request #119: Jira username can contain whitespaces
mocobeta merged PR #119: URL: https://github.com/apache/lucene-jira-archive/pull/119 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #111: Jira mention is not captured if it contains whitespace
mocobeta commented on issue #111: URL: https://github.com/apache/lucene-jira-archive/issues/111#issuecomment-1207174492 Fixed in #119 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta closed issue #111: Jira mention is not captured if it contains whitespace
mocobeta closed issue #111: Jira mention is not captured if it contains whitespace URL: https://github.com/apache/lucene-jira-archive/issues/111 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta opened a new pull request, #120: Capture jira mentions appear at the end of a line
mocobeta opened a new pull request, #120: URL: https://github.com/apache/lucene-jira-archive/pull/120 The regex needs to be fixed to properly capture mentions at the end of a line. e.g., https://github.com/mocobeta/migration-test-3/issues/535  https://github.com/mocobeta/migration-test-3/issues/536#issuecomment-1207175809  https://github.com/mocobeta/migration-test-3/issues/537#issuecomment-1207175836  Close #113 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta merged pull request #120: Capture jira mentions appear at the end of a line
mocobeta merged PR #120: URL: https://github.com/apache/lucene-jira-archive/pull/120 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta closed issue #113: Jira mention is not captured if it appears at the end of a line.
mocobeta closed issue #113: Jira mention is not captured if it appears at the end of a line. URL: https://github.com/apache/lucene-jira-archive/issues/113 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta opened a new pull request, #121: Refine regex for mentions parens
mocobeta opened a new pull request, #121:
URL: https://github.com/apache/lucene-jira-archive/pull/121
Properly capture mentions that follow `{` or `[`.
https://github.com/mocobeta/migration-test-3/issues/540
Here, `@link` in `{@link ...}` should be captured (and escaped).
Close #114
--
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...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta merged pull request #121: Refine regex for mentions parens
mocobeta merged PR #121: URL: https://github.com/apache/lucene-jira-archive/pull/121 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta closed issue #114: Avoid wrong mentions.
mocobeta closed issue #114: Avoid wrong mentions. URL: https://github.com/apache/lucene-jira-archive/issues/114 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #4: Which GitHub accont we should/can use for migration?
vlsi commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207179288 @mocobeta , can you please clarify why you have decided to do two-pass migration? Why don't you just import the issues with the proper cross-references in the first place? In other words: 1) If you import issues in ascending order, then you can statically predict the generated issue numbers 2) When doing the import, you can wait till the issue is finished, so all of them are generated in order Here's an example of an issue imported in a single go: https://github.com/vlsi/tmp-jmeter-issues/issues/1188#issue-1327437303 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #4: Which GitHub accont we should/can use for migration?
mocobeta commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207182733 We could predict the issue numbers as you pointed out, but we must prioritize safety. Importing takes 24 hours and if there are short-time GItHub outages (it's not very uncommon), the numbers would be inconsistent with the predicted issue numbers - it'd be a disaster for us. In addition, we decided to make GitHub issues available _before_ the migration is finished not to interrupt our issue system while preventing people from opening a new Jira issue; this makes it almost impossible to determine the imported issue numbers. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi opened a new issue, #122: Consider removing "Legacy Jira: by" prefix
vlsi opened a new issue, #122: URL: https://github.com/apache/lucene-jira-archive/issues/122 "Legacy Jira: by" does not seem to add much value, however, it makes it harder to read the comments (see https://github.com/mocobeta/forks-migration-test-2/issues/10595#issuecomment-1205993910) I understand you have to use "bot account" for the import, however, it looks like you could just start the comment with the real username. "legacy jira: by" is excessive. -- 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...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi opened a new issue, #123: Consider removing "Legacy JIRA" from the issue descriptions
vlsi opened a new issue, #123: URL: https://github.com/apache/lucene-jira-archive/issues/123 See https://github.com/mocobeta/forks-migration-test-2/issues/1872#issue-1328214873 Does "Legacy" add much value? I do not think so. Something like "Migrated from [LUCENE-1879](https://issues.apache.org/jira/browse/LUCENE-1879)" would probably be better -- 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...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi opened a new issue, #124: Consider using "GitHub link ( JIRA link )" cross-reference style
vlsi opened a new issue, #124: URL: https://github.com/apache/lucene-jira-archive/issues/124 If you consider GitHub issues to be primary, then it probably makes sense to put GitHub links first, and move JIRA links after GitHub ones for backup purposes only. See https://github.com/mocobeta/forks-migration-test-2/issues/1872#issue-1328214873 Current formatting: > Linked issues: > > * [LUCENE-2025](https://issues.apache.org/jira/browse/LUCENE-2025) ([Ability to turn off the store for an index [LUCENE-2025] #2018](https://github.com/mocobeta/forks-migration-test-2/issues/2018)) > * [LUCENE-2026](https://issues.apache.org/jira/browse/LUCENE-2026) ([Refactoring of IndexWriter [LUCENE-2026] #2019](https://github.com/mocobeta/forks-migration-test-2/issues/2019)) > * [SOLR-139](https://issues.apache.org/jira/browse/SOLR-139) Suggested alternative: > Linked issues: > > * https://github.com/mocobeta/forks-migration-test-2/issues/2018 ([LUCENE-2025](https://issues.apache.org/jira/browse/LUCENE-2025)) > * https://github.com/mocobeta/forks-migration-test-2/issues/2019 ([LUCENE-2026](https://issues.apache.org/jira/browse/LUCENE-2026)) > * [SOLR-139](https://issues.apache.org/jira/browse/SOLR-139) -- 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...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi opened a new issue, #125: Consider collapsing "git commit" comments by default via details-summary
vlsi opened a new issue, #125: URL: https://github.com/apache/lucene-jira-archive/issues/125 See https://gist.github.com/scmx/eca72d44afee0113ceb0349dd54a84a2 The following issue contains lots of "git commit" comments "ASF subversion and git services", and it makes it absolutely hard to read: https://github.com/mocobeta/forks-migration-test-2/issues/9956#issuecomment-1205952326 (https://issues.apache.org/jira/browse/LUCENE-10002) I believe it would be nice to collapse those technical comments via details-summary tags. -- 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...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi opened a new issue, #126: Show small attachments and images inline
vlsi opened a new issue, #126: URL: https://github.com/apache/lucene-jira-archive/issues/126 Sample issue: https://github.com/mocobeta/forks-migration-test-2/issues/10595#issue-1329388218 (https://issues.apache.org/jira/browse/LUCENE-10644) Please add the `` tag to display images inline so that users can preview the images right away The same goes for small patches, you could show them inline as the comment with regular markdown code highlighting (see https://github.com/vlsi/tmp-jmeter-issues/issues/1188#issuecomment-1204131295 ) -- 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...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #4: Which GitHub accont we should/can use for migration?
mocobeta commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207185268 There will also be pull requests (we already heavily use it) - @vlsi I'm just curious if there is a way to correctly determine the issue numbers while new issues/PRs are arrived during importing. We won't be able to stop new issues/PRs. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi opened a new issue, #127: Consider using GitHub Pages for attachments rather than raw.githubusercontent.com
vlsi opened a new issue, #127: URL: https://github.com/apache/lucene-jira-archive/issues/127 See https://github.com/mocobeta/forks-migration-test-2/issues/10159#issue-1329359180 raw.githubusercontent.com is not supposed to be used at scale, so it is better to use GitHub pages to avoid rate limits, especially if you implement https://github.com/apache/lucene-jira-archive/issues/126. Note: it makes sense to add `.nojekyll` file to the attachments repository so GitHub does not try to convert them via Jekyll (see https://github.blog/2009-12-29-bypassing-jekyll-on-github-pages/ ) See: * https://github.com/python-poetry/poetry/issues/976 -- 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...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #4: Which GitHub accont we should/can use for migration?
vlsi commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207186354 > There will also be pull requests (we already heavily use it) Just in case: I'm doing the migration for Apache JMeter (see https://github.com/vlsi/bugzilla2github). >I'm just curious if there is a way to correctly determine the issue numbers while new issues/PRs are arrived during importing I do not think so. As far as I know, the issues are allocated sequentially, and the latest assigned number can be fetched via https://api.github.com/repos/apache/lucene/issues?per_page=1 API (see `number: 1058`). With JMeter, the flow of issues and PRs is not really high, so we would just make everything read-only during the migration. --- > issue numbers while new issues/PRs are arrived during importing I assume you use bulk issue import API (https://gist.github.com/jonmagic/5282384165e0f86ef105), and if you wait for the import to complete, then it does return the assigned issue_number. However, the key need for pre-assigning the numbers is that you could generate comments that reference "issues that will be created later". If GitHub breaks, you could just continue from what you stopped. On the other hand, if you really want to allow creating issues and pull requests during the migration, then you can't easily "reference non-yet-created issues" since every PR created will shift the numbers. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #4: Which GitHub accont we should/can use for migration?
vlsi commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207186973 > We won't be able to stop new issues/PRs Do you know GitHub has "Temporary interaction limits"? I think it should be able to prevent creating issues and PRs during the import: https://docs.github.com/en/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository#about-temporary-interaction-limits By the way. I wonder if you tried contacting GitHub support somehow. Lucene is a really popular project, and it might be that you could somehow get GitHub support, so they help you with migrating the issues. For instance, when LLVM migrated their issues to GitHub, they migrated the issues to a temporary GitLab instance, and then GitHub support used a special migratory tool to migrate the issues from GitLab to GitHub. That enabled LLVM to forge commenters (see https://github.com/llvm/bugzilla2gitlab) -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #4: Which GitHub accont we should/can use for migration?
mocobeta commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207187514 Thanks for your suggestions. > I think it should be able to prevent creating issues and PRs during the import: Personally, I wish we could temporarily stop all new issues/PRs during migration, but our community is unlikely to accept it. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #122: Consider removing "Legacy Jira: by" prefix
mocobeta commented on issue #122: URL: https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207188679 I'm fine with removing "Legacy Jira" from the header - what do you think @mikemccand? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #122: Consider removing "Legacy Jira: by" prefix
mikemccand commented on issue #122: URL: https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207189001 I'm OK with shortening it somehow if we can, but I think the sentiment must remain -- we need to convey this was a migrated comment to future people who didn't even know we did this issue migration. Maybe "Prior Jira: "? "Migrated Jira: "? We could remove the `by` prefix after the : at least? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #123: Consider removing "Legacy JIRA" from the issue descriptions
mocobeta commented on issue #123: URL: https://github.com/apache/lucene-jira-archive/issues/123#issuecomment-1207189029 Relates to #122 - @mikemccand do you have thoughts on it? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #123: Consider removing "Legacy JIRA" from the issue descriptions
mikemccand commented on issue #123: URL: https://github.com/apache/lucene-jira-archive/issues/123#issuecomment-1207189274 Just repeating what I said on #122 I'm OK with shortening it somehow if we can, but I think the sentiment must remain -- we need to convey this was a migrated comment to future people who didn't even know we did this issue migration. Maybe "Prior Jira: "? "Migrated Jira: "? "Old Jira"? We could remove the by prefix after the : at least? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #122: Consider removing "Legacy Jira: by" prefix from comments
vlsi commented on issue #122: URL: https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207189627 > I think the sentiment must remain -- we need to convey this was a migrated comment to future people I just thought the comment date (and the fact it would be created by asfgit account) would be just enough to tell the comment was migrated. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #125: Consider collapsing "git commit" comments by default via details-summary
mocobeta commented on issue #125: URL: https://github.com/apache/lucene-jira-archive/issues/125#issuecomment-1207189951 Collapsing long texts with `` is a really nice feature, and I often use it. But I think we should keep it as-is; we should carry the original Jira comments without tweaks (commit comments often contain important information and are worth showing as default). -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #122: Consider removing "Legacy Jira: by" prefix from comments
mocobeta commented on issue #122: URL: https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207190807 > we need to convey this was a migrated comment to future people who didn't even know we did this issue migration. Maybe "Prior Jira: "? "Migrated Jira: "? I'm also inclined to keep suggesting "Jira" (the original source) in the issue descriptions/comments. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #122: Consider removing "Legacy Jira: by" prefix from comments
vlsi commented on issue #122: URL: https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207191411 How about changing from [Legacy Jira: by Yuting Gan (@ Yuti-G) on [Jul 10 2022](https://issues.apache.org/jira/browse/LUCENE-10644?focusedCommentId=17564642&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17564642)] to Yuting Gan (@ Yuti-G) ([migrated from JIRA commnt](https://issues.apache.org/jira/browse/LUCENE-10644?focusedCommentId=17564642&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17564642)) ? The date is already present in GitHub UI, so duplicating it does not add much. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #4: Which GitHub accont we should/can use for migration?
mikemccand commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207192249 > > I think it should be able to prevent creating issues and PRs during the import: > > Personally, I wish we could temporarily stop all new issues/PRs during migration, but our community is unlikely to accept it. Actually I think that would be fine. We could VOTE on it, but such down time is warranted if it de-risks the migration. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #122: Consider removing "Legacy Jira: by" prefix from comments
mikemccand commented on issue #122: URL: https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207192509 > The date is already present in GitHub UI, so duplicating it does not add much. +1, I like that. It can just say "migrated from Jira" (no need to say comment/description)? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #124: Consider using "GitHub link ( JIRA link )" cross-reference style
mocobeta commented on issue #124: URL: https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207192781 Thanks for your suggestion. I considered the implications and effects of this change. I'd prefer the current format - "Linked issues" or "Sub-tasks" are not GitHub features but Jira's features. We don't aim to recreate past Jira issues on GitHub, but we want to "migrate" Jira issues to GitHub while preserving the original contents as far as possible. cc @mikemccand -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #4: Which GitHub accont we should/can use for migration?
mocobeta commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207193324 Current two-pass migration is carefully considered and safe, and there is no risk; though I admit it's a bit complicated. I don't think we should change the two-pass migration plan just to shorten the total time a bit? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #126: Show small attachments and images inline
mikemccand commented on issue #126: URL: https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207193639 Whoa, I love the color on that inlined patch @vlsi! Does GitHub just auto-detect a diff/patch inside a ``` block? If the original Jira commenter/author inlined the image, it should be carried over as inlined. But if not, this is a bit tricky to just insert? Would we just append the `` at the end of the comment? Would we need to load the image and check its size before doing so? Would we thumbnail it if it's too large, or just skip it. In general we have taken the approach of preserving how the original Jira author entered the comment and not trying (too hard) to improve the comment on import. But I agree this would be nice icing on the cake. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #124: Consider using "GitHub link ( JIRA link )" cross-reference style
vlsi commented on issue #124: URL: https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207193708 > Jira issues to GitHub while preserving the original contents as far as possible In the new world, you would have GitHub issues only, and new issues would reference other issues and PRs. The habit would be: there's a link, you can click to see the details. However, if you use "JIRA first, GitHub last" style for the migrated issues, then the pattern breaks. Consider: "new issue 123 references a migrated one 42 which references yet another migrated one 21" User opens "issue 123", and sees there's a link to 42, they click and open issue 42. So far so good. However, then they see "link to 21" which breaks the flow. They suddenly have to parse the message, and deliberately click on the second link (the first link for 21 would be JIRA). That is why I suggest following the pattern: prefer in-GitHub links first, and keep JIRA links as the last resort, so cross-navigation between issues and PRs is consistent for both migrated and the new issues. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #124: Consider using "GitHub link ( JIRA link )" cross-reference style
mikemccand commented on issue #124: URL: https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207193836 +1 to make the GItHub link prominent (first link) and then legacy Jira link after. I agree we should design this for ease-of-use in a GitHub world. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #126: Show small attachments and images inline
vlsi commented on issue #126: URL: https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207194067 The markup there "diff language": Preview of ```BUG_42248.patch```: ```diff Index: src/core/org/apache/jmeter/gui/GuiPackage.java === --- src/core/org/apache/jmeter/gui/GuiPackage.java (revision 1624847) +++ src/core/org/apache/jmeter/gui/GuiPackage.java (working copy) @@ -137,7 +137,9 @@ */ private GuiPackage(JMete Here's the logic that generates that: https://github.com/vlsi/bugzilla2github/blob/61b4f9b0d94c993fea9d068918a610b61468c4d0/bugzilla-backend/src/main/kotlin/io/github/vlsi/bugzilla/dbexport/BugzillaExporter.kt#L190-L270 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #126: Show small attachments and images inline
vlsi commented on issue #126: URL: https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207194439 > Would we need to load the image and check its size before doing so? Here's a sample issue with big screenshots: https://github.com/vlsi/tmp-jmeter-issues/issues/4743 Frankly speaking, so far I generate just `` and GitHub does everything. It looks like adding image size is not really needed. I still have a TODO to add `alt="..."` message though. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #104: Should we regenerate another full export?
mikemccand commented on issue #104: URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1207194850 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 specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand closed issue #96: Some user references don't convert?
mikemccand closed issue #96: Some user references don't convert? URL: https://github.com/apache/lucene-jira-archive/issues/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 specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #96: Some user references don't convert?
mikemccand commented on issue #96: URL: https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1207194931 Yes, sorry for the delay! -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand closed issue #106: Inlined patches don't migrate correctly
mikemccand closed issue #106: Inlined patches don't migrate correctly URL: https://github.com/apache/lucene-jira-archive/issues/106 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #106: Inlined patches don't migrate correctly
mikemccand commented on issue #106: URL: https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-1207194996 +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. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #106: Inlined patches don't migrate correctly
mocobeta commented on issue #106: URL: https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-1207195204 @mikemccand sorry, I didn't mean we should close this - I think it'd be better to keep open (forever) to show what cannot be done in this migration. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #124: Consider using "GitHub link ( JIRA link )" cross-reference style
mocobeta commented on issue #124: URL: https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207195604 OK, the change would be easy - I'll update the conversion script. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #122: Consider removing "Legacy Jira: by" prefix from comments
mocobeta commented on issue #122: URL: https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207195977 OK makes sense to me, I'll change the header like this. Yuting Gan (@ Yuti-G) ([migrated from JIRA](https://issues.apache.org/jira/browse/LUCENE-10644?focusedCommentId=17564642&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17564642)) -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #126: Show small attachments and images inline
mocobeta commented on issue #126: URL: https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207198390 It's really cool to show the patch in the colored diff. As for images, we have already shown them inline in the comments (without `alt`). https://github.com/mocobeta/forks-migration-test-2/issues/10556 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #126: Show small attachments and images inline
mocobeta commented on issue #126: URL: https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207199512 The reason the image in this issue is not shown inline, the author attached the image but did not create a link to it - I think we cannot determine where to insert the image if the author does not create the link to it? https://github.com/mocobeta/forks-migration-test-2/issues/10595 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #126: Show small attachments and images inline
vlsi commented on issue #126: URL: https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207199987 > I think we cannot determine where to insert the image if the author does not create the link to it? If users do not mention the image, then the image should probably be displayed in the issue description (==first comment). -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #126: Show small attachments and images inline
mocobeta commented on issue #126: URL: https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207200567 > > I think we cannot determine where to insert the image if the author does not create the link to it? > > If users do not mention the image, then the image should probably be displayed in the issue description (==first comment). It makes sense - we need to check "If users do not mention the image," and it'd be not very trivial. I'll take a look :) -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #127: Consider using GitHub Pages for attachments rather than raw.githubusercontent.com
mocobeta commented on issue #127: URL: https://github.com/apache/lucene-jira-archive/issues/127#issuecomment-1207201764 Thanks, GitHub pages are actually scalable. I think we need to ask ASF infra (GitHub pages are per user/organization). -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #127: Consider using GitHub Pages for attachments rather than raw.githubusercontent.com
vlsi commented on issue #127: URL: https://github.com/apache/lucene-jira-archive/issues/127#issuecomment-1207202628 > I think we need to ask ASF infra I do not think so. GitHub pages is a self-service thing. See "GitHub Pages" in https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #127: Consider using GitHub Pages for attachments rather than raw.githubusercontent.com
mocobeta commented on issue #127: URL: https://github.com/apache/lucene-jira-archive/issues/127#issuecomment-1207203014 > GitHub pages is a self-service thing. See "GitHub Pages" in https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features I didn't notice it, thanks @vlsi! -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta opened a new pull request, #128: Refine jira headers in descrition and comments
mocobeta opened a new pull request, #128: URL: https://github.com/apache/lucene-jira-archive/pull/128 Suggested in #122 and #123. - Remove "Legacy Jira" header from issue description. Instead, add "Migrated from" before Jira key (link) - Shorten comment header (remove created and updated date) See https://github.com/mocobeta/migration-test-3/issues/542 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #122: Consider removing "Legacy Jira: by" prefix from comments
mocobeta commented on issue #122: URL: https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207209281 Addressed in #128. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #123: Consider removing "Legacy JIRA" from the issue descriptions
mocobeta commented on issue #123: URL: https://github.com/apache/lucene-jira-archive/issues/123#issuecomment-1207209332 Addressed in #128. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta opened a new issue, #129: Should we create links to Jira issues other than Lucene?
mocobeta opened a new issue, #129: URL: https://github.com/apache/lucene-jira-archive/issues/129 For example, there are cross-issue links such as `SOLR-`, `INFRA-`, or `LEGAL-`. At least we can/should create links to frequent projects in Lucene? -- 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...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta opened a new pull request, #130: Place github issue link first
mocobeta opened a new pull request, #130: URL: https://github.com/apache/lucene-jira-archive/pull/130 Suggested in #124 See https://github.com/mocobeta/migration-test-3/issues/544. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on pull request #130: Place github issue link first
mocobeta commented on PR #130: URL: https://github.com/apache/lucene-jira-archive/pull/130#issuecomment-1207213022 It's a trivial format change, I'd merge this. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta merged pull request #130: Place github issue link first
mocobeta merged PR #130: URL: https://github.com/apache/lucene-jira-archive/pull/130 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #124: Consider using "GitHub link ( JIRA link )" cross-reference style
mocobeta commented on issue #124: URL: https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207213143 Addressed in #130. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #129: Should we create links to Jira issues other than Lucene?
mocobeta commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207218732 I don't think we should cover all ASF Jira projects, but we can list all related projects to Lucene.   -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #129: Should we create links to Jira issues other than Lucene?
mocobeta commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207219901 - PyLucene: https://issues.apache.org/jira/projects/PYLUCENE - Open Relevance: https://issues.apache.org/jira/projects/ORP - Solr: https://issues.apache.org/jira/projects/SOLR - Hadoop: https://issues.apache.org/jira/projects/HADOOP - ManifoldCF: https://issues.apache.org/jira/projects/CONNECTORS - Lucene.NET: https://issues.apache.org/jira/projects/LUCENENET - Mahout: https://issues.apache.org/jira/projects/MAHOUT - Nutch: https://issues.apache.org/jira/projects/NUTCH - OpenNLP: https://issues.apache.org/jira/projects/OPENNLP - Tika: https://issues.apache.org/jira/projects/TIKA/ - Infra: https://issues.apache.org/jira/projects/INFRA - Legal: https://issues.apache.org/jira/projects/LEGAL -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #129: Should we create links to Jira issues other than Lucene?
vlsi commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207221618 What if you export all the ASF project names and cross-link them? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #129: Should we create links to Jira issues other than Lucene?
mocobeta commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207221972 > What if you export all the ASF project names and cross-link them? Can we export all ASF projects? I'm not really familiar with Jira APIs. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #129: Should we create links to Jira issues other than Lucene?
vlsi commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207222313 See https://issues.apache.org/jira/rest/api/latest/project -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #129: Should we create links to Jira issues other than Lucene?
mocobeta commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207222671 Thanks! I'll try to include all Jira projects - if the regex to capture issue keys is not too slow. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #129: Should we create links to Jira issues other than Lucene?
vlsi commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207222737 Just in case: the links might come in multiple flavours. For instance: * short form: `SOLR-2355` * URL: `https://issues.apache.org/jira/projects/ARTEMIS/issues/ARTEMIS-3002` * another URL: `https://issues.apache.org/jira/browse/ARTEMIS-3002` -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #129: Should we create links to Jira issues other than Lucene?
mocobeta commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207223134 For this issue, we need to consider only the "short form"; GitHub properly recognizes URLs and automatically generates links for them. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #129: Should we create links to Jira issues other than Lucene?
vlsi commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207223133
> is not too slow.
Do you mean `(?:SOLR|LUCENE|...|...)-\d+?` ?
In any case, something like `[A-Z]{2,7}-\d+` should be sufficiently fast,
and then you could double-check (via dictionary) if the prefix looks like a
valid JIRA project name.
--
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...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #129: Should we create links to Jira issues other than Lucene?
vlsi commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207223302 >GitHub properly recognizes URLs and automatically generates links for them. Just to double-check. Do you already recognize URL-links to LUCENE issues and convert them to "github issue + jira fallback"? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #129: Should we create links to Jira issues other than Lucene?
mocobeta commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207225166 > Do you already recognize URL-links to LUCENE issues and convert them to "github issue + jira fallback"? No - we do not touch URL-style links to LUCENE (or other projects) for now. This may be improved in another issue. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #129: Should we create links to Jira issues other than Lucene?
mocobeta commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207226410 If the authors just paste https://issues.apache.org/jira/browse/LUCENE-10661 in an issue, GitHub interprets it's an ordinary hyperlink. It'd be great if we replace it with `#NN` and completely remove the URL as we do for "short form" references. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] vlsi commented on issue #129: Should we create links to Jira issues other than Lucene?
vlsi commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207226888 There might be issues.apache.org/-style references, see https://github.com/vlsi/bugzilla2github/issues/7 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #106: Inlined patches don't migrate correctly
mikemccand commented on issue #106: URL: https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-120720 Ahh OK +1 then. We should note that in the known limitations of migration. I'll add it to that doc: https://docs.google.com/document/d/10m6--f7vbU9OC_SfANN6vbNDvu25COMm0Jc4wnggNV0/edit#heading=h.njfsizyml9bt -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #129: Should we create links to Jira issues other than Lucene?
mikemccand commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207233814 > If the authors just paste https://issues.apache.org/jira/browse/LUCENE-10661 in an issue, GitHub interprets it's an ordinary hyperlink. It'd be great if we replace it with `#NN` and completely remove the URL as we do so for "short form" references. Should we spin off a separate issue for this? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand merged pull request #128: Refine jira headers in descrition and comments
mikemccand merged PR #128: URL: https://github.com/apache/lucene-jira-archive/pull/128 -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #129: Should we create links to Jira issues other than Lucene?
mocobeta commented on issue #129: URL: https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207234626 > > If the authors just paste https://issues.apache.org/jira/browse/LUCENE-10661 in an issue, GitHub interprets it's an ordinary hyperlink. It'd be great if we replace it with `#NN` and completely remove the URL as we do so for "short form" references. > > Should we spin off a separate issue for this? If we know all URL patterns for issues, it'd be easy to address - I'll open another issue for this. -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #126: Show small attachments and images inline
mikemccand commented on issue #126: URL: https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207235027 > > > I think we cannot determine where to insert the image if the author does not create the link to it? > > > > > > If users do not mention the image, then the image should probably be displayed in the issue description (==first comment). > > It makes sense - we need to check "If users do not mention the image," and it'd be not very trivial. I'll take a look :) +1, this would be nice, especially since GH UI takes care of the rendering/sizing details. Should we open a separate issue to try to detect a diff/patch inside ``` and render it with that GitHub diff markup so we pretty the colors? -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
