https://dagster.io/ logo
#ask-community
Title
# ask-community
a

Alexis Manuel

12/15/2022, 9:57 AM
Hello, I just updated Dagster to 1.1.6 version but I am now unable to materialize any asset manually using the
Materialize all / Materialize selected
button. Details in 🧵
When clicking on the button while having the console open, I see that the
LaunchAssetLoaderQuery
respond with a 502. It is probably a timeout issue because I try to load many partitions at once (around 100k).
It is a regression since the previous version I was using (1.0.17) as I can’t launch any run and backfills manually from the UI. I hope you will figure this out 🙏
Update: I just tested this locally on a fresh DB and the popup asking to select partitions for the runs is showing up. It confirms that the issue is likely related to too many partitions to fetch, thus having the server to timeout
For more context on this: I have a partitioned job built with
define_asset_job
with 6 assets and with a 15 minutes time window partition since 2022-01-01
j

jamie

12/15/2022, 3:30 PM
@sean is this is the issue that’s getting fixed this week?
s

sean

12/15/2022, 3:32 PM
I don’t think so
j

jamie

12/15/2022, 3:42 PM
ok @Alexis Manuel could you open a bug in github with the behavior you’re seeing? any error messages, screenshots from the UI of unexpected behavior, etc would all help us debug
a

Alexis Manuel

12/15/2022, 3:49 PM
Sure no problem