Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
uranusjr commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1742525961 Is there log of a failing run? I think the new release has a bug. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and u

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
Lee-W commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1742532327 @uranusjr Not sure whether this is the log you're looking for. But these are the logs for my failing breeze run on ci, https://github.com/apache/airflow/actions/runs/6377228541/job

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
uranusjr commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1742543039 Hmm that doesn’t seem to be related to packaging. And it’s failing with the same error here too, so maybe there are two separate issues here. -- This is an automated message from the

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
hussein-awala commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1742554233 > Hmm that doesn’t seem to be related to packaging. And it’s failing with the same error here too, so maybe there are two separate issues here. Some CI jobs load the scripts

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
uranusjr commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1742631252 So is _neither_ of the errors above is related to what you’re trying to fix here? -- This is an automated message from the Apache Git Service. To respond to the message, please log o

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
uranusjr commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1742648359 OK looks like this is the error ``` Breeze should only be installed with -e flag Please go to Airflow sources and run breeze self-upgrade --force ```

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
hussein-awala commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1742678037 I will merge to check if the main CI will be fixed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the UR

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
hussein-awala merged PR #34701: URL: https://github.com/apache/airflow/pull/34701 -- 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...@ai

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
hussein-awala commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1742686769 Looks like it works :tada: -- 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 spe

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-02 Thread via GitHub
uranusjr commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1742719414 The fix in pipx also seems to work for me (`breeze ci-image build`) so as soon as that gets released we can switch to that instead. -- This is an automated message from the Apache Gi

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-06 Thread via GitHub
potiuk commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1751325319 > Some CI jobs load the scripts files from main ( @hussein-awala (and others) for the future - the way for committers to test such a PR is to make PR from "airflow" repo, not from

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-06 Thread via GitHub
Joffreybvn commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1751399961 Had the same issue today on a fresh Fedora system, installing pipx via `brew`. ``` (airflow) [joffreybvn@fedora airflow]$ breeze Traceback (most recent call last): F

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-07 Thread via GitHub
hussein-awala commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1751668317 > > Some CI jobs load the scripts files from main ( > > @hussein-awala (and others) for the future - the way for committers to test such a PR is to make PR from "airflow" re

Re: [PR] Fix broken breeze by fixing packaging version [airflow]

2023-10-08 Thread via GitHub
potiuk commented on PR #34701: URL: https://github.com/apache/airflow/pull/34701#issuecomment-1752052790 > I see the CI fails in https://github.com/apache/airflow/pull/34775 although it cherry-pick this commit and source branch is in Apache repository, do you have any idea? Yes. We c