Skip to content

Fixed: Wait for lists to be populated. Closes #1335. - #1336

Closed
coffeedogs wants to merge 1 commit into
Bitmessage:v0.6from
coffeedogs:issue_1335
Closed

coffeedogs wants to merge 1 commit into
Bitmessage:v0.6from
coffeedogs:issue_1335

Conversation

@coffeedogs

Copy link
Copy Markdown
Contributor

This addresses two cases where non-deterministic initialisation may lead to lists being used by randomchoice() before they have been populated. Arguably we should ensure the length of the list is sufficiently large since passing a list of one undermines the point of randomchoice() and we are relying on system peculiarities to choose a random item.

However I would favour planning and implementing a more deterministic initialisation than we have currently (simple > complex > complicated).

@coffeedogs coffeedogs changed the title Fixed: Wait for lists to be populated. Closes 1335. Fixed: Wait for lists to be populated. Closes #1335. Aug 15, 2018
@PeterSurda
PeterSurda requested a review from a team August 23, 2018 14:12

@PeterSurda PeterSurda left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes would prevent incoming connections being handled while known nodes is empty. Instead, keep the exception and break from the cycle in connectionpool or something like that.

@PeterSurda PeterSurda added the bug Something isn't working as it's supposed to label Aug 23, 2018
@g1itch g1itch closed this Jul 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working as it's supposed to

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants