eladkal commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1954916093
Thank you everyone. Providers are released.
I invite everyone to help improve providers for the next release, a list of
open issues can be found
[here](https://github.com/ap
eladkal closed issue #37534: Status of testing Providers that were prepared on
February 19, 2024
URL: https://github.com/apache/airflow/issues/37534
--
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 t
VladaZakharova commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1953867484
Hi !
#36847 and #37072 work as expected, thank you :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
pankajastro commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1953835890
@eladkal yes, we are good to go with the release. Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
pankajkoti commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1953677361
> @raphaelauv @pankajastro @pankajkoti If i get it right the resolution we
are good to go with release?
@eladkal IMO, yes, we're good to go with release.
--
This is an
eladkal commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1953673719
@raphaelauv @pankajastro @pankajkoti If i get it right the resolution we are
good to go with release?
--
This is an automated message from the Apache Git Service.
To respond to t
raphaelauv commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1953072614
@pankajastro you are correct I mixed the settings between asyn and non async
when I checked the RC.
--
This is an automated message from the Apache Git Service.
To respond to
pankajastro commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1953058108
Still not sure, `logging_interval` is a new param in 8.0.0rc and it should
not impact the sync version of the operator.
here code for the sync kpo
https://github.com/apac
pankajkoti commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1953057871
> I'm not speaking about the deferrable mode
Okay, :). The `logging_interval` param that you pointed at
[earlier](https://github.com/apache/airflow/issues/37534#issuecomme
raphaelauv commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1953031982
I'm not speaking about the deferrable mode
--
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
pankajkoti commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1953016838
> "Container logs was not available earlier regularly"
>
> That's wrong, the kpo with get_logs , get the container logs regularly
@raphaelauv It was not possible to
raphaelauv commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952970781
"Container logs was not available earlier regularly"
That's wrong, the kpo with get_logs , get the container logs regularly
--
This is an automated message from
pankajastro commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952900773
@raphaelauv I'm a bit confused now. Sorry!. Do you mean container log is not
visible regularly or the log statement something like "container is still
running/pending" when tri
pankajkoti commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952897570
Yes, I agree there will be no informative logs in RC3 from the triggerer
saying the container is still running.
However, the trigger logs are independent of get_logs (even
raphaelauv commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952582127
in 7.1.4 with only `get_logs =true `
it fetch the logs regularly when the pod is running
in 8.0.0rc3 with only `get_logs =true`
it fetch the logs only at the
vchiapaikeo commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952550848
Agree with @pankajkoti that this was also the behavior previously. For
deferrable tasks, logs were fetched and sent at the end (on pod completion) to
the task. New commits incl
pankajkoti commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952521062
@raphaelauv I believe `get_logs` was only meant to fetch logs at the end of
the pod completion and so is also the case now.
I guess what you mean is the missing logs in t
raphaelauv commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952444799
sorry I was not explicit
I was surprise to not see logs anymore in airflow for my pod during the run
of the pod cause I have the option get_logs at true
--
Thi
pankajastro commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952375618
> I was surprise to not see logs anymore in airflow for my pod
That should not be the case. If the logging interval is none then you will
see logs at the end of a task ex
raphaelauv commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952355153
logging_interval is at None by default in the 8.0.0 is that voluntary ?
would be more friendly for users that we have this , wdyt ( I was surprise
to not see logs anymore
vchiapaikeo commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952329089
https://github.com/apache/airflow/pull/37508 looks good. Thank you! 🙇
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
pankajastro commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952174977
Tested my changes. looking good. Thanks for the RC's
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use t
pankajkoti commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952150694
#37514 works as expected. Thanks Elad for quick RC3.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use th
eladkal commented on issue #37534:
URL: https://github.com/apache/airflow/issues/37534#issuecomment-1952042110
I marked all items that were tested in RC2
https://github.com/apache/airflow/issues/37504 as tested here too but feel free
to retest them.
--
This is an automated message from t
eladkal opened a new issue, #37534:
URL: https://github.com/apache/airflow/issues/37534
### Body
I have a kind request for all the contributors to the latest provider
packages release.
Could you please help us to test the RC versions of the providers?
The guidelines on how t
25 matches
Mail list logo
