-
Notifications
You must be signed in to change notification settings - Fork 190
fix: store server used to import as peer #1311
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1311 +/- ##
===========================================
- Coverage 40.74% 40.68% -0.06%
===========================================
Files 237 237
Lines 6561 6572 +11
Branches 1303 1296 -7
===========================================
+ Hits 2673 2674 +1
- Misses 3642 3653 +11
+ Partials 246 245 -1
Continue to review full report at Codecov.
|
I think it might be worth doing |
|
Your pull request needs some changes. Please wait for a comment from one of our developers for more information. |
@luciorubeens needs changes :crazypuppyeyes: |
fix: development mode message in production (#1427) * fix: development mode message in production * fix: remove error log * chore: add script to build win x64 feat: show if voted delegate is active in wallet table (#1410) refactor: get wallet names in wallet selection/input address (#1394) fix: port used from github peer list (#1430) fix: properly format crypto currencies (#1402) * fix: properly format crypto currencies * chore: typo `precissely` -> `precisely` * test: remove `only` fix: close transaction show modal when clicking on addresses and navigate to transactions tab always (#1143) * fix: close transaction show when clicking on and address and navigate to transactions tab always * fix: close vote modal when clicking on and address and navigate to transactions tab always * fix: hide the tooltip when clicking on a wallet address
642c56d
to
49b9f5c
Compare
@alexbarnsley The peer was not being added to the list due to validation failure. Fixed by changing |
👌 thanks, will take a look after the release |
@alexbarnsley can this be reviewed and merged or does it need any changes? |
@luciorubeens you didn't do |
I mean, it loaded peers straight away so I'll merge |
Sets the server as a peer temporarily until it finds new peers.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Does this PR release a new version?
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
develop
branch, not themaster
branchIf adding a new feature, the PR's description includes: