You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "atul-astronomer (via GitHub)" <gi...@apache.org> on 2025/03/13 11:06:24 UTC
[I] Serialisation issue when triggering an asset decorated dag [airflow]
atul-astronomer opened a new issue, #47720:
URL: https://github.com/apache/airflow/issues/47720
### Apache Airflow version
main (development)
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
Serialisation issue is coming when triggering a dag which is asset decorated and decorator has name attribute.
INFO: 192.168.97.1:53086 - "GET /public/dags/abcd/dagRuns/manual__2025-03-13T10%3A58%3A38.178923%2B00%3A00_vNVGhOqs/taskInstances/__main__/-1 HTTP/1.1" 200 OK
/usr/local/lib/python3.9/site-packages/pydantic/type_adapter.py:527 UserWarning: Pydantic serializer warnings:
PydanticSerializationUnexpectedValue: Expected `StructuredLogMessage` but got `StructuredLogMessage` with value `StructuredLogMessage(time..._main__/attempt=1.log'])` - serialized value may not be as expected
PydanticSerializationUnexpectedValue: Expected `str` but got `StructuredLogMessage` with value `StructuredLogMessage(time..._main__/attempt=1.log'])` - serialized value may not be as expected
### What you think should happen instead?
The Dag should work fine and create an asset event.
### How to reproduce
Run the below DAG:
```python
@asset(name="abcd", uri="s3://bucket/asset1_producer", schedule=None)
def asset1_producer():
pass
```
### Operating System
Linux
### Versions of Apache Airflow Providers
_No response_
### Deployment
Other
### Deployment details
_No response_
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Serialisation issue when triggering an asset decorated dag [airflow]
Posted by "ashb (via GitHub)" <gi...@apache.org>.
ashb commented on issue #47720:
URL: https://github.com/apache/airflow/issues/47720#issuecomment-2721986829
That warning isn't an issue itself. The issue causing the task to fail is the "Runtime checks failed" which means this endpoint failed https://github.com/apache/airflow/blob/main/airflow/api_fastapi/execution_api/routes/task_instances.py#L538-L560
@amoghrajesh We should probably include more context on the error we get back from the server in the task logs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Issue running task of an asset decorated dag [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr closed issue #47720: Issue running task of an asset decorated dag
URL: https://github.com/apache/airflow/issues/47720
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Issue running task of an asset decorated dag [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr commented on issue #47720:
URL: https://github.com/apache/airflow/issues/47720#issuecomment-2722961833
Ah I think I have a guess for this specific line though. This is probably because the run is triggered to quickly after you enable the DAG. The assets are activated in the DAG parser, but the DAG is paused/unpaused in the web server, so if you hit trigger immediately after unpausing, there’s a possibility the parser does not update the asset states in time before the task is run.
Since asset activeness is also checked when the task finishes, maybe we can afford to remove this check.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org