-
Notifications
You must be signed in to change notification settings - Fork 672
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(artifacts): raise for invalid artifact names #8773
base: main
Are you sure you want to change the base?
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @tonyyli-wandb and the rest of your teammates on Graphite |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8773 +/- ##
==========================================
- Coverage 70.34% 70.34% -0.01%
==========================================
Files 547 547
Lines 58097 58107 +10
==========================================
+ Hits 40868 40873 +5
- Misses 16565 16574 +9
+ Partials 664 660 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
|
e010d25
to
26c094c
Compare
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.
lgtm!
(non-blocking question): The ArtifactCollection
class also has a name
setter:
wandb/wandb/apis/public/artifacts.py
Lines 539 to 540 in 8a345e6
def name(self, name: List[str]) -> None: | |
self._name = name |
I think we can use the same validator to check the artifact name there since the validator for artifact.name is also for sequence name. Wdyt?
Good point -- I think so too. Thanks for the catch! |
26c094c
to
9a77eeb
Compare
9a77eeb
to
109f339
Compare
109f339
to
1db7461
Compare
Description
Validates
Artifact
names on instantiation, raising aValueError
if the name is expected to be invalid (i.e. the artifact cannot be logged).Testing
How was this PR tested?