Open
Description
Dagster version
dagster, version 1.5.1
What's the issue?
dagster_cloud_cli.core.errors.DagsterCloudHTTPError: 413 Client Error: Request Entity Too Large for url: https://hallow.agent.dagster.cloud/graphql: <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>
</body>
</html>
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/execution/plan/execute_plan.py", line 273, in dagster_event_sequence_for_step
for step_event in check.generator(step_events):
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/execution/plan/execute_step.py", line 482, in core_dagster_event_sequence_for_step
for evt in _type_check_and_store_output(step_context, user_event):
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/execution/plan/execute_step.py", line 530, in _type_check_and_store_output
for output_event in _type_check_output(step_context, step_output_handle, output, version):
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/execution/plan/execute_step.py", line 387, in _type_check_output
yield DagsterEvent.step_output_event(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/events/__init__.py", line 825, in step_output_event
return DagsterEvent.from_step(
^^^^^^^^^^^^^^^^^^^^^^^
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/events/__init__.py", line 430, in from_step
log_step_event(step_context, event)
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/events/__init__.py", line 309, in log_step_event
step_context.log.log_dagster_event(
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/log_manager.py", line 406, in log_dagster_event
self.log(level=level, msg=msg, extra={DAGSTER_META_KEY: dagster_event})
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/log_manager.py", line 421, in log
self._log(level, msg, args, **kwargs)
File "/usr/local/lib/python3.11/logging/__init__.py", line 1634, in _log
self.handle(record)
File "/usr/local/lib/python3.11/logging/__init__.py", line 1644, in handle
self.callHandlers(record)
File "/usr/local/lib/python3.11/logging/__init__.py", line 1706, in callHandlers
hdlr.handle(record)
File "/usr/local/lib/python3.11/logging/__init__.py", line 978, in handle
self.emit(record)
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/log_manager.py", line 287, in emit
handler.handle(dagster_record)
File "/usr/local/lib/python3.11/logging/__init__.py", line 978, in handle
self.emit(record)
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/instance/__init__.py", line 222, in emit
self._instance.handle_new_event(event)
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster/_core/instance/__init__.py", line 2136, in handle_new_event
self._event_storage.store_event(event)
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster_cloud/storage/event_logs/storage.py", line 425, in store_event
self._execute_query(
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster_cloud/storage/event_logs/storage.py", line 303, in _execute_query
res = self._graphql_client.execute(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster_cloud_cli/core/graphql_client.py", line 125, in execute
raise DagsterCloudHTTPError(e) from e
The above exception was caused by the following exception:
requests.exceptions.HTTPError: 413 Client Error: Request Entity Too Large for url: https://hallow.agent.dagster.cloud/graphql
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster_cloud_cli/core/graphql_client.py", line 79, in execute
return self._execute_retry(query, variable_values, headers)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/dagster_cloud_cli/core/graphql_client.py", line 179, in _execute_retry
response.raise_for_status()
File "/venvs/acfb6f5c04c2/lib/python3.11/site-packages/requests/models.py", line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
What did you expect to happen?
I understand it was a large payload, but I would have preferred that it just did not include the metadata instead of completely erroring out the materialization. Given the nature of the asset materialization it'll be painful to re-materialize once I remove the bulk payload portion of the metadata.
How to reproduce?
No response
Deployment type
Dagster Cloud
Deployment details
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
