Correct issue with updateConfig.js - Seed Peers Overwriting #83

Closed
Isabello opened this Issue Mar 10, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@Isabello
Contributor

Isabello commented Mar 10, 2017

When updating seed peers, the existing implementation overwrites the new peers with the old. This needs to be corrected to allow peers to be updated with the client correctly.

@karmacoma karmacoma added the bug label Mar 10, 2017

@karmacoma karmacoma added this to Ready in Version 0.7.0 Mar 10, 2017

Isabello pushed a commit that referenced this issue Mar 10, 2017

Isabello

@Isabello Isabello self-assigned this Mar 10, 2017

@karmacoma karmacoma closed this in #84 Mar 12, 2017

karmacoma added a commit that referenced this issue Mar 12, 2017

Merge pull request #84 from LiskHQ/83-updateConfig-fix
Correct seed peers update - Closes #83

@karmacoma karmacoma moved this from Ready to In Progress in Version 0.7.0 Mar 12, 2017

@karmacoma karmacoma removed this from In Progress in Version 0.7.0 Mar 12, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment