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.

Sign up for GitHub

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

Jump to bottom

"Unexpected GraphQL Error" popup when selecting asset groups from top left hamburger menu - Fragment 'SensorSwitchFragment' is never used #19292

Closed
chriscomeau79 opened this issue Jan 18, 2024 · 0 comments · Fixed by #19293
Closed

"Unexpected GraphQL Error" popup when selecting asset groups from top left hamburger menu - Fragment 'SensorSwitchFragment' is never used #19292

chriscomeau79 opened this issue Jan 18, 2024 · 0 comments · Fixed by #19293
Labels
type: bug Something isn't working

Comments

@chriscomeau79
Copy link

Dagster version

1.6.1

What's the issue?

When navigating to an asset group under a code location using the tree under the hamburger menu, we briefly see an error popup in red in the upper right:

Unexpected GraphQL error

Details:
Operation name: AssetGroupMetadataQuery
Message: Fragment 'SensorSwitchFragment' is never used.
Path:
Locations: [{"line":11,"column":1}]

What did you expect to happen?

No response

How to reproduce?

Navigating to any asset group using the tree under the hamburger icon in the upper left. URLs will look like this:

https://dagster/locations/.../asset-groups/...
same for
https://dagster/locations/.../asset-groups/.../lineage

Deployment type

Local

Deployment details

running on Ubuntu with Python 3.10

Additional information

This doesn't happen in the global asset lineage, or in other asset graph views like the upstream/downstream with URLs like this:
https://dagster/assets/...?view=lineage
Seems to be something specific to that code location navigation panel on the left.

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
@chriscomeau79 chriscomeau79 added the type: bug Something isn't working label Jan 18, 2024
@salazarm salazarm mentioned this issue Jan 18, 2024
Merged
salazarm added a commit that referenced this issue Jan 18, 2024
@salazarm
Remove unused "SensorSwitchFragment" (#19293)
5f6e2c6 
## Summary & Motivation

broken in #19083

Fixes #19292

## How I Tested These Changes

Loaded the page after removing
ei-grad pushed a commit to ei-grad/dagster that referenced this issue Jan 19, 2024
@salazarm @ei-grad
Remove unused "SensorSwitchFragment" (dagster-io#19293)
b57345f 
## Summary & Motivation

broken in dagster-io#19083

Fixes dagster-io#19292

## How I Tested These Changes

Loaded the page after removing
dpeng817 pushed a commit that referenced this issue Jan 26, 2024
@salazarm @dpeng817
Remove unused "SensorSwitchFragment" (#19293)
dd284e9 
## Summary & Motivation

broken in #19083

Fixes #19292

## How I Tested These Changes

Loaded the page after removing
@alangenfeld alangenfeld mentioned this issue Jan 26, 2024
Closed
aroig pushed a commit to aroig/dagster that referenced this issue Jan 28, 2024
@salazarm @aroig
Remove unused "SensorSwitchFragment" (dagster-io#19293)
af4c157 
## Summary & Motivation

broken in dagster-io#19083

Fixes dagster-io#19292

## How I Tested These Changes

Loaded the page after removing
@elliottower elliottower mentioned this issue Dec 21, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove unused "SensorSwitchFragment" dagster-io/dagster
1 participant
@chriscomeau79