alexbegg edited a comment on issue #10434:
URL: https://github.com/apache/airflow/issues/10434#issuecomment-681195969


   @kaxil I can't reproduce this with Breeze. I ran `master` branch, 
`v1-10-stable` branch (with `rbac = True`), and even 1.10.11 tag (with `rbac = 
True`, to match my Kubernetes deployment) with Breeze and this issue does not 
come up, even though the issue does come up in my Kubernetes deployment.
   
   I am going to have to recreate the same setup in breeze and see if I can 
reproduce this issue...
   
   Here is what I found so far after clicking the "Last Run" link:
   - :x: : status is `None` - Airflow 1.10.11 in my Kubernetes cluster, with 
execution_date **not URL-encoded** in the URL: 
   ![Screen Shot 2020-08-26 at 5 21 10 
PM](https://user-images.githubusercontent.com/45696489/91370333-ec28f400-e7c2-11ea-8d78-53d9619bd32b.png)
   
   - :white_check_mark: : status is `success` - Airflow 1.10.11 in my 
Kubernetes cluster, with execution_date **_manually_ URL-encoded** in the URL:
   ![Screen Shot 2020-08-26 at 5 20 27 
PM](https://user-images.githubusercontent.com/45696489/91370340-f0551180-e7c2-11ea-9679-5c5b32a1c65f.png)
   
   - :white_check_mark: : status is `success` - Airflow 1.10.12 running with 
Breeze on `v1-10-stable` branch, with execution_date **not URL-encoded** in the 
URL:
   ![Screen Shot 2020-08-26 at 5 21 40 
PM](https://user-images.githubusercontent.com/45696489/91370344-f3500200-e7c2-11ea-8c1e-a86dab5d3e03.png)
   
   - :white_check_mark: : status is `success` - Airflow 1.10.11 running with 
Breeze on `1.10.11` tag, with execution_date **not URL-encoded** in the URL:
   ![Screen Shot 2020-08-26 at 6 14 52 
PM](https://user-images.githubusercontent.com/45696489/91372413-7162d780-e7c8-11ea-9efb-94f991df9197.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.

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


Reply via email to