-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Lhotse Sharding Fix #9187
Lhotse Sharding Fix #9187
Conversation
f"Mismatched entry between JSON manifest ('{manifest_path}') and tar file ('{tar_path}'). " | ||
f"Conflicting audio file names are JSON='{data['audio_filepath']}' and TAR='{tar_info.name}'" | ||
f"Cannot locate manifest entry for TAR='{tar_info.name}'" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
f"Cannot locate manifest entry for TAR='{tar_info.name}'" | |
f"Cannot locate JSON audio path '{data['audio_filepath']}' in tar file '{tar_info.name}'" |
It'd be better to mention which specific audio filepath is missing e.g. like this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That won't work here since we're iterating through data first. It also isn't informative anymore since this doesn't enforce order.
Signed-off-by: Piotr Żelasko <petezor@gmail.com>
Signed-off-by: Travis Bartley <tbartley@nvidia.com>
Signed-off-by: tbartley94 <tbartley94@users.noreply.github.com>
What does this PR do ?
Caches manifest entries during
LazyNeMoTarredIterator
in Lhotse to avoid errors from improper sorting. Allows back compatibility with webdataset behavior.Collection: [Note which collection this PR will affect]
Changelog
GitHub Actions CI
The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.
The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".
Before your PR is "Ready for review"
Pre checks:
PR Type:
If you haven't finished some of the above items you can still open "Draft" PR.
Who can review?
Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.
Additional Information