I would love to see some airflow_testing package which will be useful for
testing airflow-related projects and involve independently.
Certainly, it's not a good thing to have tests import something from tests.
New packages as projects are cheap and provide more flexibility and are
useful from outs
I'd like to second this. If there is something wrong with caplog then maybe
it is better to fix it rather than move to a self maintained alternative?
Newcomers still will be prefered to use common capsys before they faced
some local specifics and wonder why it still exists.
--
,,,^..^,,,
On Fri,
Hi Jarek!
I understand the reasons for opt-out from a project view. I just suddenly
imagined the situation when an upgrade happens and here comes the data to
some third party service - that's a view from a user side of some big
company.
There could be good alternatives to handle this:
1. Short op
-0 But it has to be:
1. Opt-in by default to not trigger security guys about new unplanned
activity after regular upgrade.
2. It should not affect anything if access to the internet is restricted
which is default for many companies.
3. Be transparent about what it will send to for review. Separate
I share Andrey's skepticism. It's just yet another tool which has an
unclear development strategy. Should you make it a free testing suite? What
project would receive in exchange? A lot of words about being faster, but
how much? Are these milliseconds worth to change the stable tool with a new
one?
On Fri, Feb 9, 2024 at 1:35 AM Jarek Potiuk wrote:
> ...
> #first-pr-support
Why a special channel for the first PR? Feels like I should move to another
channel if it's my second one while I still could be first-pr-mistakes just
because of different context. Maybe some better naming here?
--
>
>
>
> On Sun, Dec 17, 2023 at 7:06 PM Alexander Shorin
> wrote:
>
> > According the docs
> >
> >
> >
> https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/listeners.html
> >
> > It's not clear what will ma
According the docs
https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/listeners.html
It's not clear what will make it public and how to use it. Examples would
be nice otherwise it will remain private as "read the code to learn how to
use it right".
Just a notice,
Hi!
This looks like sugar without any practical difference from explicitly
defined setup/teardown operators in dag. And the example doesn't add any
automatic'sation except to set you free from defining explicit relations
between setup, teardown and regular operators, but why all of this when you
a
as it diverges from the main
> topic. So the comment was mainly to myself as I was diverging from the
> main topic.
>
> On Tue, Nov 22, 2022 at 1:34 PM Alexander Shorin wrote:
> >
> > Jarek,
> >
> > I'm probably not ready to introduce this topic and push
mentioned) is adding
> extra work just to keep them out of sync. A basic common sense would be not
> to take extra steps to self sabotage.
> >
> > Thanks,
> > Abhishek
> >
> > On 22-Nov-2022 at 4:35:09 PM, Alexander Shorin wrote:
> >>
> >> On Tu
On Tue, Nov 22, 2022 at 1:37 PM Jarek Potiuk wrote:
> BTW. "Workers from 2.2" used with "Airflow 2.4" is not even a thing.
> This is something that you should never, ever, try to do.
> This is even more common sense, and there are of course limits of what
> you can describe in the docs (whatever
The rule of breaking changes also applies to database schema as well,
right? Because currently, almost every minor release is breaking since you
cannot run workers from 2.2.x with a database from 2.4.x.
--
,,,^..^,,,
On Tue, Nov 22, 2022 at 12:32 PM Jarek Potiuk wrote:
> Hello everyone,
>
> We
> improved airflow version as soon as possible.
>
> The help of our users in getting Airflow better is really invaluable and
> we love to get this kind of help from them,
>
> Thank you in advance for helping us!
>
> J.
>
> On Wed, Sep 21, 2022 at 4:02 AM Alexander Sho
Great release! Thanks you all for dataset feature!
But for this time I had to revert
https://github.com/apache/airflow/commit/36eea1c8e0 change for our
production since it completely broke the grid view for all our dags - it
thought that the last dagrun was somewhere at 2021.11 dates while all the
How should your idea work on systems without docker? Like FreeBSD? And why
you made such leaky tasks which couldn't be isolated with common tools like
system packages, venv, etc.
--
,,,^..^,,,
On Fri, Dec 17, 2021 at 2:53 AM Ping Zhang wrote:
> Hi Airflow Community,
>
> This is Ping Zhang from
It's such a pity.
--
,,,^..^,,,
On Tue, Jun 1, 2021 at 1:06 PM Ash Berlin-Taylor wrote:
> Hi everyone,
>
> This rename has now happened, and the default brach for apache/airflow is
> now "main".
>
> If you have a local checkout you can update the local default branch by
> running the following
17 matches
Mail list logo
