Issue 1:
Apache Airflow version:

2.0.0

Kubernetes version (if you are using kubernetes) (use kubectl version):

N/A

Environment:

virtualenv

Cloud provider or hardware configuration: N/A - Localhost:8080

OS (e.g. from /etc/os-release): MacOS Cataline 10.15.7

Kernel (e.g. uname -a): Kernel Version 19.6.0

Install tools: pip

Others:

What happened:

Could not fire up 'airflow webserver.' Error Message as follows:

Python version: 3.8.3

Airflow version: 2.0.0

Node: CHAAZML-T3CAMD6

Traceback (most recent call last):

File "/Users/Me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/flask/app.py", line 2447, in wsgi_app

response = self.full_dispatch_request()

File "/Users/Me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/flask/app.py", line 1953, in full_dispatch_request

return self.finalize_request(rv)

File "/Users/Me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/flask/app.py", line 1970, in finalize_request

response = self.process_response(response)

File "/Users/Me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/flask/app.py", line 2269, in process_response

self.session_interface.save_session(self, ctx.session, response)

File "/Users/Me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/flask/sessions.py", line 379, in save_session

response.set_cookie(

File "/Users/Me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/werkzeug/wrappers/base_response.py", line 468, in set_cookie

dump_cookie(

File "/Users/Me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/werkzeug/http.py", line 1217, in dump_cookie

raise ValueError("SameSite must be 'Strict', 'Lax', or 'None'.")

ValueError: SameSite must be 'Strict', 'Lax', or 'None'.

What you expected to happen:

Webserver start.

Uknown

How to reproduce it:

Anything else we need to know:

Log in Terminal says:

/Users/me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/airflow/configuration.py:324 DeprecationWarning: The statsd_on option in [scheduler] has been moved to the statsd_on option in [metrics] - the old setting has been used, but please update your config.

/Users/me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/airflow/configuration.py:324 DeprecationWarning: The logging_config_class option in [core] has been moved to the logging_config_class option in [logging] - the old setting has been used, but please update your config.

/Users/me/projects/git_stuff/pols_analytics_general/airflow/lib/python3.8/site-packages/airflow/configuration.py:324 DeprecationWarning: The task_log_reader option in [core] has been moved to the task_log_reader option in [logging] - the old setting has been used, but please update your config.

Issue 2:
Apache Airflow version

2.3.3 (latest released)

What happened

In 2.3.3

If I use https://airflow.apache.org/docs/apache-airflow/stable/plugins.html#plugins-as-python-packages feature, then I see these Error:

short:

ValueError: The name 'airs' is already registered for this blueprint. Use 'name=' to provide a unique name.

long:

i'm trying to reproduce it...

If I don't use it(workarounding by AIRFLOW__CORE__PLUGINS_FOLDER), errors doesn't occur.

It didn't happend in 2.3.2 and earlier

What you think should happen instead

Looks like plugins are import multiple times if it is plugins-as-python-packages.

Perhaps flask's major version change is the main cause.

Presumably, in flask 1.0, duplicate registration of blueprint was quietly filtered out, but in 2.0 it seems to have been changed to generate an error. (I am trying to find out if this hypothesis is correct)

Anyway, use the latest version of FAB is important. we will have to adapt to this change, so plugins will have to be imported once regardless how it defined.

How to reproduce

It was reproduced in the environment used at work, but it is difficult to disclose or explain it.

I'm working to reproduce it with the breeze command, and I open the issue first with the belief that it's not just me.

Operating System

CentOS Linux release 7.9.2009 (Core)

Versions of Apache Airflow Providers

$ SHIV_INTERPRETER=1 airsflow -m pip freeze | grep apache-
apache-airflow==2.3.3
apache-airflow-providers-apache-hive==3.1.0
apache-airflow-providers-apache-spark==2.1.0
apache-airflow-providers-celery==3.0.0
apache-airflow-providers-common-sql==1.0.0
apache-airflow-providers-ftp==3.1.0
apache-airflow-providers-http==3.0.0
apache-airflow-providers-imap==3.0.0
apache-airflow-providers-postgres==5.1.0
apache-airflow-providers-redis==3.0.0
apache-airflow-providers-sqlite==3.1.0

but I think these are irrelevant.

Deployment

Other 3rd-party Helm chart

Deployment details

docker image based on centos7, python 3.9.10 interpreter, self-written helm2 chart ....

... but I think these are irrelevant.

Anything else

No response

Are you willing to submit PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct