Re: [PR] Migrate to connexion v3 [airflow]

Thu, 14 Mar 2024 06:09:05 -0700 


vincbeck commented on PR #37638:
URL: https://github.com/apache/airflow/pull/37638#issuecomment-1997426495

   > Apart form `ValueError: The name '/auth/fab/v1' is already registered for 
a different blueprint. Use 'name=' to provide a unique name.` we also get the 
following error which does not occur locally.
   > 
   > `E RuntimeError: Directory 
'/opt/airflow/airflow/www/static/dist/swagger-ui' does not exist ` <img 
alt="image" width="865" 
src="https://private-user-images.githubusercontent.com/32765701/312637913-c9e6004b-ea0d-4068-81f9-94bb06adf8a8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTA0MjExMzksIm5iZiI6MTcxMDQyMDgzOSwicGF0aCI6Ii8zMjc2NTcwMS8zMTI2Mzc5MTMtYzllNjAwNGItZWEwZC00MDY4LTgxZjktOTRiYjA2YWRmOGE4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAzMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMzE0VDEyNTM1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ2NTIzNTFhYTUyODdkNjE4MTBhZTdhYjA5ZWJkYzJiNmFmNTVlN2E1NDZkMGQzMTY3YzkxY2EyOWFhMDU1ZTYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.7HZ4Us90Se6vfFc7CAfgN6Jxe2kxbguwPYsCR4ctoTM";>
   > 
   > I think this is because Swagger UI is not installed inside the test 
environment. We can run ` yarn --cwd airflow/www/ run build` to install swagger 
UI dist in the runner environment but I am not sure where exactly we need to do 
that in GitHub workflow.
   
   I have not given up and will give it another shot next week to try to 
resolve the `ValueError: The name '/auth/fab/v1' is already registered for a 
different blueprint. Use 'name=' to provide a unique name.`. I am still trying 
to find the root cause.


-- 
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