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

Boost retrieval does not adhere output path #1570

Closed
7 of 12 tasks
cryptowhizzard opened this issue Jul 17, 2023 · 0 comments · Fixed by #1574
Closed
7 of 12 tasks

Boost retrieval does not adhere output path #1570

cryptowhizzard opened this issue Jul 17, 2023 · 0 comments · Fixed by #1574
Labels

Comments

@cryptowhizzard
Copy link
Contributor

Checklist

  • This is not a question or a support request. If you have any boost related questions, please ask in the discussion forum.
  • This is not a new feature request. If it is, please file a feature request instead.
  • This is not an enhancement request. If it is, please file a improvement suggestion instead.
  • I have searched on the issue tracker and the discussion forum, and there is no existing related issue or discussion.
  • I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
  • I did not make any code changes to boost.

Boost component

  • boost daemon - storage providers
  • boost client
  • boost UI
  • boost data-transfer
  • boost index-provider
  • Other

Boost Version

1.7.3

Describe the Bug

Boost does not adhere the output path when storing files.

For example :
/usr/local/bin/boost retrieve --provider f02201020 bafykbzacean7oshht7ragxv4lr5pqveubu4dwtaowh5mxh2x3uupapr6wjlb6 -o /root/downloadedcarfiles/2050-f02227756-f02201020-46514981-baga6ea4seaqnaeu43m2je4rayyxcjy4srqvfcqprbz5jfluljsgskejxi2bemgq

leads to the file saved in the path where this command was executed and not in the requested path with the -o flag.

Logging Information

n.a.

Repo Steps

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants