Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix restore_from_stronghold_snapshot() with same source and target path #2234

Merged

Conversation

Thoralf-M
Copy link
Member

@Thoralf-M Thoralf-M commented Apr 22, 2024

Description of change

Fix restore_from_stronghold_snapshot() for the case when source and target path are the same. Without this change std::fs::copy() truncates the backup file, resulting in Error: Stronghold(Client(ClientDataNotPresent))

Port 8084 seems to be used by Mono actions/runner-images#2820, so replaced this port for the dashboard

Type of change

  • Bug fix (a non-breaking change which fixes an issue)

How the change has been tested

Added test

@Thoralf-M Thoralf-M changed the title Fix restore_from_stronghold_snapshot() for the case when source and target path are the same Fix restore_from_stronghold_snapshot() with same source and target path Apr 22, 2024
@Thoralf-M Thoralf-M force-pushed the fix/stronghold-restore-with-same-path branch from 842e583 to 1fd27b6 Compare April 22, 2024 11:48
@Thoralf-M Thoralf-M marked this pull request as ready for review April 22, 2024 12:06
Copy link

@DaughterOfMars DaughterOfMars left a comment

Choose a reason for hiding this comment

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

I guess that's fine. Wish there was a way to do this via the private tangle script or something.

@Thoralf-M Thoralf-M merged commit e046ae5 into iotaledger:2.0 Apr 22, 2024
37 checks passed
@Thoralf-M Thoralf-M deleted the fix/stronghold-restore-with-same-path branch April 22, 2024 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants