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
Add dark theme to experiment pane #10380
Conversation
…10372) Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com>
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com> Signed-off-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Co-authored-by: Ben Wilson <39283302+BenWilson2@users.noreply.github.com>
Signed-off-by: Daniel Lok <daniel.lok@databricks.com>
Documentation preview for db2bcbb will be available here when this CircleCI job completes successfully. More info
|
Signed-off-by: Daniel Lok <daniel.lok@databricks.com>
…ance type validation (mlflow#10379) Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com> Signed-off-by: Ben Wilson <39283302+BenWilson2@users.noreply.github.com>
Signed-off-by: Daniel Lok <daniel.lok@databricks.com>
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.
left few nits, looks well otherwise!
@@ -174,7 +174,7 @@ export class ExperimentListView extends Component<Props, State> { | |||
return ( | |||
<div | |||
css={isActive ? this.activeExperimentListItem : this.inactiveExperimentListItem} | |||
data-test-id={dataTestId} | |||
data-testid={dataTestId} |
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.
thanks 🙏
@@ -392,6 +391,11 @@ const classNames = { | |||
justifySelf: 'end', | |||
marginRight: '10px', | |||
}, | |||
icon: (theme: Theme) => ({ | |||
color: theme.colors.actionDefaultTextDefault, | |||
fontSize: 24, |
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.
(should evaluate to 24
as well)
fontSize: 24, | |
fontSize: theme.general.iconSize, |
@@ -63,8 +64,8 @@ class HomeView extends Component<HomeViewProps> { | |||
); | |||
} | |||
return ( | |||
<div css={{ display: 'flex', height: 'calc(100% - 60px)' }}> | |||
<div css={{ height: '100%', paddingTop: 24, display: 'flex' }}> | |||
<div css={styles.homeContainer}> |
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.
We've eventually stopped using automatic (theme) => styleObject
function pattern for emotion because jest
runtime hates it badly and produces super noisy logs. Whenever possible, please just get theme
object e.g. from hook and use
<div css={styles.homeContainer}> | |
<div css={styles.homeContainer(theme)}> |
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.
ah and for class components, you can use HoC
); | ||
expect(wrapper.length).toBe(1); | ||
expect(screen.getByAltText('No experiments found.')).not.toBeNull(); |
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.
expect(screen.getByAltText('No experiments found.')).not.toBeNull(); | |
expect(screen.getByAltText('No experiments found.')).toBeInTheDocument(); |
Signed-off-by: chenmoneygithub <chen.qian@databricks.com>
Signed-off-by: Daniel Lok <daniel.lok@databricks.com>
@@ -230,19 +228,21 @@ export class ExperimentListView extends Component<Props, State> { | |||
|
|||
render() { | |||
const { hidden } = this.state; | |||
const { activeExperimentIds, designSystemThemeApi } = this.props; |
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.
@hubertzub-db is this the right way to use HoC (what does it stand for btw)?
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.
yeah, it works! thanks! HoC means Higher-order-Component which is an old (pre-hook) technique for wrapping components in other (higher-order) ones to inject features within
…mlflow#10362) Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com>
Signed-off-by: Serena Ruan <serena.rxy@gmail.com>
Signed-off-by: Liang Zhang <liang.zhang@databricks.com>
Signed-off-by: Prithvi Kannan <prithvi.kannan@databricks.com>
Signed-off-by: Daniel Lok <daniel.lok@databricks.com>
…10394) Signed-off-by: chenmoneygithub <chen.qian@databricks.com>
This reverts commit 1c33add.
Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com> Signed-off-by: B-Step62 <yuki.watanabe@databricks.com> Signed-off-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Signed-off-by: Daniel Lok <daniel.lok@databricks.com> Signed-off-by: Ben Wilson <39283302+BenWilson2@users.noreply.github.com> Signed-off-by: chenmoneygithub <chen.qian@databricks.com> Signed-off-by: Serena Ruan <serena.rxy@gmail.com> Signed-off-by: Liang Zhang <liang.zhang@databricks.com> Signed-off-by: Chen Qian <chenmoney@google.com> Signed-off-by: Prithvi Kannan <prithvi.kannan@databricks.com> Co-authored-by: Haxatron <haxatron1@gmail.com> Co-authored-by: Ben Wilson <39283302+BenWilson2@users.noreply.github.com> Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Co-authored-by: Chen Qian <chenmoney@google.com> Co-authored-by: Serena Ruan <82044803+serena-ruan@users.noreply.github.com> Co-authored-by: Liang Zhang <liang.zhang@databricks.com> Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Co-authored-by: Prithvi Kannan <46332835+prithvikannan@users.noreply.github.com>
🛠 DevTools 🛠
Install mlflow from this PR
Checkout with GitHub CLI
Related Issues/PRs
What changes are proposed in this pull request?
The previous PR was getting quite large as there's a number of things to fix, so I'm going to be breaking it up into smaller PRs. This one just addresses the experiment sidebar:
I also updated the tests to move away from enzyme.
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/gateway
: AI Gateway service, Gateway client APIs, third-party Gateway integrationsarea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes