-
Notifications
You must be signed in to change notification settings - Fork 362
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
feat: add basic lineage MDLM link #9482
Conversation
✅ Deploy Preview for determined-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
2465d14
to
d9c1100
Compare
d9c1100
to
3b4efcf
Compare
c28259b
to
3a44ae1
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.
i don't think the config validation requires a pachyderm key if it includes integrations (that is, an empty object or an object with keys other than pachyderm is a valid integrations setup). this should take that into account.
3d962d7
to
934b673
Compare
Change base type for the integration and made necessary followup changes
…ent to display MLDM repo data.
090880a
to
87cd7c8
Compare
a682685
to
f43c708
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.
looks fine, just had one more nit
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.
i just noticed few things, so added comments. i think its a blocker
also some test file covs are under 80% or do we care about overall cov? iirc, file cov?
waitFor(() => { | ||
expect(screen.findByText('Data Input')).toBeVisible(); | ||
expect(screen.findByText(mockIntegrationData.dataset.repo)).toBeVisible(); | ||
}); | ||
}); | ||
|
||
it('should not show Data input card when pachyderm integration is missing', () => { | ||
setup(mockTrial1, mockExperiment); | ||
waitFor(() => { | ||
expect(screen.findByText('Data Input')).not.toBeVisible(); | ||
}); |
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.
i think these test cases actually dont assert values. even if text is changed to whatever values, the test cases pass. feels like this needs to be fixed before merging this PR
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.
In here I'm validating it by using the findByText
with the exact same mock data set to be the repo's name... the test for the URL that's being built based on the lineage values is being done in the integrations.test.ts
, which asserts for the exact URL as it is expected.
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.
the test cases are false negative. can we fix 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.
changed to use data-testid
in order to abstract the text values from it
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.
changed to use data-testid in order to abstract the text values from it
i cant find test cases that use data-testid
. i think its missing
waitFor(() => { | ||
expect(screen.findByText('Data Input')).toBeVisible(); | ||
expect(screen.findByText(mockIntegrationData.dataset.repo)).toBeVisible(); | ||
}); | ||
}); | ||
|
||
it('should not show Data input card when pachyderm integration is missing', () => { | ||
setup(mockTrial1, mockExperiment); | ||
waitFor(() => { | ||
expect(screen.findByText('Data Input')).not.toBeVisible(); | ||
}); |
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.
changed to use data-testid in order to abstract the text values from it
i cant find test cases that use data-testid
. i think its missing
afbe800
to
528c6ac
Compare
Ticket: ET-252
Description
Adds the MDLM link to experiments that has integrations data linked to it.
Here's the expected placements:
in the single run view when the run is based off of an MLDM model
in the checkpoint modal view when the checkpoint’s experiment is based off of an MLDM model
in the model view when the model’s checkpoint’s experiment is based off of an MLDM model
Test Plan
the easiest way to test this is to fork the experiment
core-api-stage-0
and add the following to its config:From there it should be possible to add the checkpoint and model based on the forked experiment and have the MDLM link in the experiment details page, checkpoint modal and model view.
Checklist
docs/release-notes/
.See Release Note for details.