Jarek Potiuk
Jarek Potiuk
> In general speaking we also might have a look at anyo for the triggerer but it is another story and another challenge Yeah. I think we should not even...
> Also (not included in this PR), the message after initialization for me looked like this (Docker-Desktop on Windows 11): > [2024-01-05T09:51:47.658+0000] {override.py:1820} INFO - Added Permission menu access on...
And just a general command @jtommi - the fact that something does not work for `you` - is not always a reason to change things - because it maybe YOU...
And also another comment - I am not 100% sure it works now - it might it be it does not and our tests simply did not catch it, it's...
BTW. By a quick look it is quite possible it does not work. The `aiflow-init` container runs `airflow version` which I think COULD in the past initialize the DB as...
Those are all good questions - and I think they need proper fixes. I think "why" it's not a good question. Better question is "how we can improve it" because...
> > And according to the dependencies it should run initialise DB after Postgres started and before scheduler/webserver/worker/triggerer > Ah ... So looks like I am still stuck in that...
So yeah. in this case I'd simply remove the "init" instructions.
> Is it possible to reopen this issue? If you have more data, information and similar error - it's better to open a new issue and provide your data/ details...
CAn you resolve conflicts and rebase please?