Re: [PR] Better diagnosis when skipping packages when generating back references [airflow]

2025-05-16 Thread via GitHub


potiuk merged PR #50714:
URL: https://github.com/apache/airflow/pull/50714


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



[PR] Better diagnosis when skipping packages when generating back references [airflow]

2025-05-16 Thread via GitHub


potiuk opened a new pull request, #50714:
URL: https://github.com/apache/airflow/pull/50714

   When you generate back-references, and skip missing directories the mesage 
was not very corect/useful - it mentioned provider but it could be any package 
(apache-airflow for exanple) and it did not show the missing path - which made 
it difficult to diagnose things. It also mentioned that the provider is not 
released (which was not realy this - it was about package dir missing).
   
   This PR fixes those issues.
   
   
   
   
   
   
   
   
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
   


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