uschindler commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1202106033
@stanislawosinski it is more important to actually link the accounts!
https://gitbox.apache.org/boxer/
The process is there. The id.apache.org is only to setup th
uschindler commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1202107233
For me it looks like this:
-
mocobeta commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1202114869
@stanislawosinski thank you for your cooperation!
And thanks @uschindler for the information. I will send a follow-up email to
note about MFA.
--
This is an auto
stanislawosinski commented on issue #102:
URL:
https://github.com/apache/lucene-jira-archive/issues/102#issuecomment-1202115143
Thanks, @uschindler! I've just set up the link and see myself as Apache
member on GitHub.
--
This is an automated message from the Apache Git Service.
To respon
kaivalnp commented on code in PR #932:
URL: https://github.com/apache/lucene/pull/932#discussion_r935382898
##
lucene/core/src/test/org/apache/lucene/util/hnsw/KnnGraphTester.java:
##
@@ -730,4 +794,61 @@ protected int comparePivot(int j) {
return Float.compare(score[pivo
mocobeta commented on issue #106:
URL:
https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-1202480736
Is it possible to estimate how many issues with inlined patches we have? I
guess there are not that many?
We can manually correct critical glitches afterward if we kno
mocobeta opened a new pull request, #107:
URL: https://github.com/apache/lucene-jira-archive/pull/107
#89
This just escapes all `~` in at the last step of the markup conversion to
avoid unintentional strike-throughs in Markdown.
Also, `~username` style Jira mentions should be chan
mocobeta commented on PR #105:
URL:
https://github.com/apache/lucene-jira-archive/pull/105#issuecomment-1202681349
@mikemccand can we just commit this in main and see the result? I can run
full-import tomorrow for the next trial, and I think we can manually tweak old
issues with inlined pa
mocobeta closed pull request #107: Escape tilde to avoid wrong strike-throughs
in markdown
URL: https://github.com/apache/lucene-jira-archive/pull/107
--
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
mocobeta commented on PR #107:
URL:
https://github.com/apache/lucene-jira-archive/pull/107#issuecomment-1202720390
The conversion has to be done _before_ markdown conversion; otherwise valid
strike-throughs will break.
--
This is an automated message from the Apache Git Service.
To respo
mocobeta commented on issue #89:
URL:
https://github.com/apache/lucene-jira-archive/issues/89#issuecomment-1202747376
I found this is trickier than it looks...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL a
[
https://issues.apache.org/jira/browse/LUCENE-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved LUCENE-10457.
Lucene Fields: (was: New)
Resolution: Won't Fix
> LuceneTestCase.createTempDir could ran
[
https://issues.apache.org/jira/browse/LUCENE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved LUCENE-9412.
---
Resolution: Won't Fix
> Repro Jenkins jobs failing to fetch build output
> -
[
https://issues.apache.org/jira/browse/LUCENE-10664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574332#comment-17574332
]
Patrick Zhai commented on LUCENE-10664:
---
Can we instead make the {{queryTimeout}}
mikemccand commented on PR #105:
URL:
https://github.com/apache/lucene-jira-archive/pull/105#issuecomment-1203207723
Hi @mocobeta -- I think this PR is not worth it and too buggy to fix
properly. I'll cancel it.
--
This is an automated message from the Apache Git Service.
To respond to
mikemccand closed pull request #105: #93: insert extra newline when we see
markdown-styled quoting (>) without extra newline after
URL: https://github.com/apache/lucene-jira-archive/pull/105
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
mikemccand commented on issue #106:
URL:
https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-1203208793
I ran a simple approximate check, counting how often `\n\n` occurs
(which may undercount?), and it was small, 19. I think we should do nothing
for this?
--
This
[
https://issues.apache.org/jira/browse/LUCENE-10670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuan Xiao updated LUCENE-10670:
---
Issue Type: Improvement (was: Wish)
> Add Filter class to Codec Writer/Producer/Reader/Consumer/Fo
mocobeta commented on issue #106:
URL:
https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-1203386356
I can fix 19 issues by hand after the migration (there would be no hurry),
could you tell me the issue numbers or commands to identify the issues with
inline patches?
-
19 matches
Mail list logo
