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: Fix retina capture download failing due to empty BLOB_URL #1206

Merged
merged 2 commits into from
Jan 13, 2025

Conversation

kamilprz
Copy link
Contributor

Description

Prior to this PR, exporting a BLOB_URL variable and running retina capture download would throw an error. This was due to Viper (the config manager package) not picking up the value correctly. This PR adds a change that corrects this behaviour.

I also added a little bit of context to the error message to make it more explicit.

Related Issue

#899

Checklist

  • I have read the contributing documentation.
  • I signed and signed-off the commits (git commit -S -s ...). See this documentation on signing commits.
  • I have correctly attributed the author(s) of the code.
  • I have tested the changes locally.
  • I have followed the project's style guidelines.
  • I have updated the documentation, if necessary.
  • I have added tests, if applicable.

Screenshots (if applicable) or Testing Completed

Current behaviour - valid token, but not recognised
image

Empty BLOB_URL
{2DCCFD6C-29C6-48BE-AE58-546099C92307}

Valid BLOB_URL
image

Additional Notes

Testing was done on my personal blob storage account.


Please refer to the CONTRIBUTING.md file for more information on how to contribute to this project.

@kamilprz kamilprz requested a review from a team as a code owner January 10, 2025 12:36
@kamilprz kamilprz added this pull request to the merge queue Jan 13, 2025
Merged via the queue into microsoft:main with commit 7673d81 Jan 13, 2025
27 checks passed
@kamilprz kamilprz deleted the capture-download branch January 13, 2025 11:22
kamilprz added a commit to kamilprz/retina that referenced this pull request Jan 16, 2025
…soft#1206)

# Description

Prior to this PR, exporting a `BLOB_URL` variable and running `retina
capture download` would throw an error. This was due to Viper (the
config manager package) not picking up the value correctly. This PR adds
a change that corrects this behaviour.

I also added a little bit of context to the error message to make it
more explicit.

## Related Issue

microsoft#899

## Checklist

- [x] I have read the [contributing
documentation](https://retina.sh/docs/contributing).
- [x] I signed and signed-off the commits (`git commit -S -s ...`). See
[this
documentation](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification)
on signing commits.
- [x] I have correctly attributed the author(s) of the code.
- [x] I have tested the changes locally.
- [x] I have followed the project's style guidelines.
- [x] I have updated the documentation, if necessary.
- [x] I have added tests, if applicable.

## Screenshots (if applicable) or Testing Completed

Current behaviour - valid token, but not recognised

![image](https://github.com/user-attachments/assets/0095f8fd-953b-4460-8da8-a707092dee0d)

Empty BLOB_URL

![{2DCCFD6C-29C6-48BE-AE58-546099C92307}](https://github.com/user-attachments/assets/5fae2bdb-3225-47a8-a915-a66b22bba052)

Valid BLOB_URL

![image](https://github.com/user-attachments/assets/1dfad7ca-1163-44e8-89b3-ef0de6e6f00a)


## Additional Notes

Testing was done on my personal blob storage account.

---

Please refer to the [CONTRIBUTING.md](../CONTRIBUTING.md) file for more
information on how to contribute to this project.

Signed-off-by: Kamil <[email protected]>
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.

2 participants