mocobeta opened a new pull request, #21:
URL: https://github.com/apache/lucene-jira-archive/pull/21
In `{{monospaced}}` markup, sometimes extra brackets are inserted for some
reason.
e.g. `{{{}ExitableDirectoryReader{}}}`
Although This may not be a conversion error, the rendere
mocobeta merged PR #21:
URL: https://github.com/apache/lucene-jira-archive/pull/21
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lu
mocobeta opened a new pull request, #22:
URL: https://github.com/apache/lucene-jira-archive/pull/22
#1
A line break should be inserted before a ruler (sequence of dashes with
arbitrary length); otherwise, the following paragraph is interpreted as headers.
error example:
 have
been fixed. There are
mocobeta opened a new issue, #24:
URL: https://github.com/apache/lucene-jira-archive/issues/24
Mentions are everywhere. It could be possible to map Jira mentions to GitHub
mentions (if the mapping is given).
--
This is an automated message from the Apache Git Service.
To respond to the me
[
https://issues.apache.org/jira/browse/LUCENE-10480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564565#comment-17564565
]
Adrien Grand commented on LUCENE-10480:
---
[AndMedOrHighHigh|https://home.apache.or
mocobeta opened a new pull request, #25:
URL: https://github.com/apache/lucene-jira-archive/pull/25
Close #24
Capture all `@username` in issue descriptions and comments (as far as
possible), then replace each with GitHub account if the corresponding account
is available. If there is
mocobeta merged PR #25:
URL: https://github.com/apache/lucene-jira-archive/pull/25
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lu
mocobeta closed issue #24: Re-map Jira mentions to GitHub mentions
URL: https://github.com/apache/lucene-jira-archive/issues/24
--
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.
[
https://issues.apache.org/jira/browse/LUCENE-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564577#comment-17564577
]
Michael Sokolov commented on LUCENE-10577:
--
> Please do this without adding ad
vigyasharma commented on PR #1012:
URL: https://github.com/apache/lucene/pull/1012#issuecomment-1179579087
Right, we can remove the TODO, as the calling thread in addIndexes now takes
care of cleaning up any pending non-CFS files. Updated the PR.
> did we change something that invalid
[
https://issues.apache.org/jira/browse/LUCENE-10480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564611#comment-17564611
]
Zach Chen edited comment on LUCENE-10480 at 7/9/22 7:25 PM:
[
https://issues.apache.org/jira/browse/LUCENE-10480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564611#comment-17564611
]
Zach Chen commented on LUCENE-10480:
{quote}[AndMedOrHighHigh|https://home.apache.o
vigyasharma commented on PR #948:
URL: https://github.com/apache/lucene/pull/948#issuecomment-1179603848
Rebased on main..
--
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.
T
mocobeta commented on issue #14:
URL:
https://github.com/apache/lucene-jira-archive/issues/14#issuecomment-1179645018
The root cause is unclear (the issue description may be too large for
importing). It can be manually recovered afterward.
1. set a dummy text to issue's "body" field
mocobeta commented on issue #14:
URL:
https://github.com/apache/lucene-jira-archive/issues/14#issuecomment-1179645732
The same as https://issues.apache.org/jira/browse/LUCENE-5612.
```
[2022-06-27 02:28:25,450] ERROR:github_issues_util: Failed to import issue
LockStressTest fails
mocobeta opened a new issue, #26:
URL: https://github.com/apache/lucene-jira-archive/issues/26
This may be done as post-processing:
1. [List labels in the
repository](https://docs.github.com/en/rest/issues/labels#list-labels-for-a-repository)
2. [Update each
label](https://docs.gi
mocobeta commented on issue #3:
URL:
https://github.com/apache/lucene-jira-archive/issues/3#issuecomment-1179653722
Looks like there's no way to list accounts that belong to a specific
organization. Also, it is impossible to make a mapping for non-committers
(contributors).
With Git
Yuti-G opened a new pull request, #1013:
URL: https://github.com/apache/lucene/pull/1013
Fixed `getAllChildren` unit tests to compare label and value with no
assumptions about the child ordering. This pr only fixed some of the unit
tests, and will continue to fix all of them after receiving
mocobeta commented on issue #3:
URL:
https://github.com/apache/lucene-jira-archive/issues/3#issuecomment-1179655455
If you have a better idea for this, please leave your suggestions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
[
https://issues.apache.org/jira/browse/LUCENE-10644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564642#comment-17564642
]
Yuting Gan commented on LUCENE-10644:
-
Thanks for discovering the issue with the cu
24 matches
Mail list logo
