[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415881#comment-16415881
]
Hoss Man commented on SOLR-10338:
---------------------------------
{quote}And the order of test execution can be randomized.
{quote}
I now have a better understanding of what you ment by "randomly occurs" – the
inference i drew from your earlier comments was that you were frustrated by
some "randomized situation" that was _deliberately_ {{random()}}-ized.
However, this increased understanding does not fundamentally change my primary
concern: If you feel like a change should be made, then this conversation
should be moved to a new (linked) jira, with a specific example of situations
where the current code is problematic, ideally with a proposed change.
I don't feel that the comments of an issue resolved almost a year ago (that's
already been in 3 released versions of Solr) is the appropriate place to
discuss improvements to how it works.
> Configure SecureRandom non blocking for tests.
> ----------------------------------------------
>
> Key: SOLR-10338
> URL: https://issues.apache.org/jira/browse/SOLR-10338
> Project: Solr
> Issue Type: Sub-task
> Reporter: Mihaly Toth
> Assignee: Mark Miller
> Priority: Major
> Fix For: 7.1, master (8.0)
>
> Attachments: SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch,
> SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch,
> SOLR-10338.patch
>
>
> It would be best if SecureRandom could be made non blocking. In that case we
> could get rid of random entropy exhaustion issue related to all usages of
> SecureRandom.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
