[GitHub] [airflow] uranusjr commented on issue #17582: DAG trigger with config params visualisation with proper deserialisation
uranusjr commented on issue #17582: URL: https://github.com/apache/airflow/issues/17582#issuecomment-920790119 I believe #17100 actually fixed this, although not sure if it’s intentional or accidental. That PR should be a part of 2.2 (including the currently available beta), so I’ll close this for now; feel free to reopen if this is still an issue in 2.2. This is how the Trigger DAG view renders for me in `main`: ![image](https://user-images.githubusercontent.com/605277/133598810-f766edf5-e87a-48c3-a328-7647a029c4f3.png) -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #17582: DAG trigger with config params visualisation with proper deserialisation
uranusjr commented on issue #17582: URL: https://github.com/apache/airflow/issues/17582#issuecomment-900825011 Those `__type` and `__val` keys are added by Airflow’s DAG serialisation logic, and the UI shouldn’t see them in the first place. I’m suspecting this is a bug in (de)serialisation, and if that’s correct this would be very deep down in the stack. -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #17582: DAG trigger with config params visualisation with proper deserialisation
uranusjr commented on issue #17582: URL: https://github.com/apache/airflow/issues/17582#issuecomment-900825011 Those `__type` and `__val` keys are added by Airflow’s DAG serialisation logic, and the UI shouldn’t see them in the first place. I’m suspecting this is a bug in (de)serialisation, and if that’s correct this would be very deep down in the stack. -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org