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 codespell errors #1694

Merged
merged 1 commit into from
Oct 2, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dandiapi/api/copy.py
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ class CopyObjectPart:
dest_key: str

# Whether or not to include the byte range in the request
# (exlcuded for single part copies)
# (excluded for single part copies)
include_range: bool = True

@property
Expand Down
2 changes: 1 addition & 1 deletion dandiapi/api/views/dandiset.py
Original file line number Diff line number Diff line change
Expand Up @@ -203,7 +203,7 @@ def _get_dandiset_to_version_map(dandisets):
for version in versions:
version: Version

# Annnotate with total size and asset count (with default)
# Annotate with total size and asset count (with default)
stats = version_stats.get(version.id, {'total_size': 0, 'num_assets': 0})
version.total_size = stats['total_size']
version.num_assets = stats['num_assets']
Expand Down
2 changes: 1 addition & 1 deletion doc/design/publish-1.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ This involves digesting the Version metadata into something that can be used by
See the doi-generation-1.md design document for more details.

4. For every draft Asset in the draft Version, the required publish metadata fields are injected, turning those Assets into published Assets.
Published Assets, e.g. Asssets that already have those fields from previous publishes, _are skipped_.
Published Assets, e.g. Assets that already have those fields from previous publishes, _are skipped_.
Because they describe Assets that have already been published in a past version, there is no reason to re-publish them.

5. Associate all of the publish Assets, new and old, with the new published Version.
Expand Down