Allow maggma to be used without Azure #837
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, 0.52.0 raises an error
```
../../../local/Caskroom/miniconda/base/envs/mp/lib/python3.9/site-packages/maggma/stores/azure.py:368: in AzureBlobStore
def _get_container(self) -> Optional[ContainerClient]:
E NameError: name 'ContainerClient' is not defined
```
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #837 +/- ##
==========================================
- Coverage 88.15% 88.13% -0.03%
==========================================
Files 44 44
Lines 3589 3590 +1
==========================================
Hits 3164 3164
- Misses 425 426 +1
☔ View full report in Codecov by Sentry. |
|
Do you have a sense of why this didn't happen before? Is it from dep upgrades? |
|
A line was commented out here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, 0.52.0 raises an error