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

revert single implicit asset job #23607

Merged
merged 2 commits into from
Aug 13, 2024
Merged

revert single implicit asset job #23607

merged 2 commits into from
Aug 13, 2024

Conversation

sryza
Copy link
Contributor

@sryza sryza commented Aug 13, 2024

Summary & Motivation

It turns out this breaks some functionality in the launch modal. Working with @bengotow to fix that functionality, but I don't think it will land in time for this week's release.

How I Tested These Changes

Copy link

Deploy preview for dagster-docs ready!

Preview available at https://dagster-docs-91ui4ukjn-elementl.vercel.app
https://revert-single-implicit.dagster.dagster-docs.io

Direct link to changed pages:

Copy link
Member

@gibsondan gibsondan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we were relying on this to fix #23163 - is it worth digging into that separately to see if there is a faster fix for that?

@sryza sryza merged commit 35f00aa into master Aug 13, 2024
2 checks passed
@sryza sryza deleted the revert-single-implicit branch August 13, 2024 20:05
@sryza
Copy link
Contributor Author

sryza commented Aug 13, 2024

Faster fix here: #23623

clairelin135 pushed a commit that referenced this pull request Aug 13, 2024
## Summary & Motivation

It turns out this breaks some functionality in the launch modal. Working
with @bengotow to fix that functionality, but I don't think it will land
in time for this week's release.

## How I Tested These Changes
PedramNavid pushed a commit that referenced this pull request Aug 14, 2024
## Summary & Motivation

It turns out this breaks some functionality in the launch modal. Working
with @bengotow to fix that functionality, but I don't think it will land
in time for this week's release.

## How I Tested These Changes
sryza added a commit that referenced this pull request Aug 20, 2024
sryza added a commit that referenced this pull request Aug 21, 2024
This reverts commit 35f00aa.

## Summary & Motivation

We had reverted the single implicit asset job stack after discovering
that it caused problems in the UI. Those problems are fixed by the stack
ending in [this GraphQL
change](#23494) and [this
frontend change](#23747).

So this unreverts. It shouldn't be merged until that frontend change
makes it in.

## How I Tested These Changes
jmsanders pushed a commit that referenced this pull request Aug 21, 2024
This reverts commit 35f00aa.

## Summary & Motivation

We had reverted the single implicit asset job stack after discovering
that it caused problems in the UI. Those problems are fixed by the stack
ending in [this GraphQL
change](#23494) and [this
frontend change](#23747).

So this unreverts. It shouldn't be merged until that frontend change
makes it in.

## How I Tested These Changes

(cherry picked from commit 2616f6d)
cmpadden pushed a commit that referenced this pull request Aug 21, 2024
This reverts commit 35f00aa.

## Summary & Motivation

We had reverted the single implicit asset job stack after discovering
that it caused problems in the UI. Those problems are fixed by the stack
ending in [this GraphQL
change](#23494) and [this
frontend change](#23747).

So this unreverts. It shouldn't be merged until that frontend change
makes it in.

## How I Tested These Changes
jmsanders added a commit that referenced this pull request Aug 21, 2024
jmsanders pushed a commit that referenced this pull request Aug 22, 2024
This reverts commit 35f00aa.

## Summary & Motivation

We had reverted the single implicit asset job stack after discovering
that it caused problems in the UI. Those problems are fixed by the stack
ending in [this GraphQL
change](#23494) and [this
frontend change](#23747).

So this unreverts. It shouldn't be merged until that frontend change
makes it in.

## How I Tested These Changes

(cherry picked from commit 2616f6d)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants