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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to