text:
worker pod crashing

I deployed airflow webserver, scheduler, postgres, redis, worker, flower on different openshift pods.
webserver, scheduler, postgres, redis, flower are successfully deployed & running.
Scheduler is performing LPUSH into redis queue with task instance.
Can see airflow UI with dags, dag runs & task instance.
Status of Dagruns remains running & task instance queued.
Worker deployment is crashing shows only following logs in the log terminal of worker pod:
[2019-05-28 14:04:36,401] {{settings.py:174}} INFO - settings.configure_orm(): Using pool settings. pool_size=5, pool_recycle=1800, pid=1
| [2019-05-28 14:04:37,401] {{init.py:51}} INFO - Using executor CeleryExecutor
Logs on webserver's log terminal are:
[2019-05-28 13:15:15,595] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags
| [2019-05-28 13:15:16,765] {{settings.py:174}} INFO - settings.configure_orm(): Using pool settings. pool_size=5, pool_recycle=1800, pid=192
  | [2019-05-28 13:15:17 +0000] [192] [INFO] Starting gunicorn 19.9.0
  | [2019-05-28 13:15:17 +0000] [192] [INFO] Listening at: http://0.0.0.0:8081  (192)
  | [2019-05-28 13:15:17 +0000] [192] [INFO] Using worker: sync
  | [2019-05-28 13:15:17 +0000] [197] [INFO] Booting worker with pid: 197
  | [2019-05-28 13:15:17 +0000] [198] [INFO] Booting worker with pid: 198
  | [2019-05-28 13:15:17 +0000] [199] [INFO] Booting worker with pid: 199
  | [2019-05-28 13:15:17 +0000] [200] [INFO] Booting worker with pid: 200
  | Running the Gunicorn Server with:
  | Workers: 4 sync
  | Host: 0.0.0.0:8081
  | Timeout: 120
  | Logfiles: - -
  | =================================================================
  | [2019-05-28 13:15:18,036] {{init.py:51}} INFO - Using executor CeleryExecutor
  | [2019-05-28 13:15:18,529] {{init.py:51}} INFO - Using executor CeleryExecutor
  | [2019-05-28 13:15:18,743] {{init.py:51}} INFO - Using executor CeleryExecutor
  | [2019-05-28 13:15:18,929] {{init.py:51}} INFO - Using executor CeleryExecutor
  | [2019-05-28 13:15:20,740] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags
  | [2019-05-28 13:15:21,029] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags
  | [2019-05-28 13:15:21,047] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags
  | [2019-05-28 13:15:21,132] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags......
Anybody can assist on fixing this up.
Thanks In Advance.
Hitesh

I am facing the same issue
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: apache-airflow[google_auth] in /home/airflow/.local/lib/python3.6/site-packages (1.10.15)
Requirement already satisfied: python-daemon>=2.1.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.2.4)
Requirement already satisfied: json-merge-patch==0.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.2)
Requirement already satisfied: cached-property~=1.5 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.5.2)
Requirement already satisfied: flask-swagger<0.3,>=0.2.13 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.2.14)
Requirement already satisfied: pygments<3.0,>=2.0.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.7.2)
Requirement already satisfied: flask-login<0.5,>=0.3 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.4.1)
Requirement already satisfied: pendulum==1.4.4 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.4.4)
Requirement already satisfied: tabulate<0.9,>=0.7.5 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.8.7)
Requirement already satisfied: dill<0.4,>=0.2.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.3.3)
Requirement already satisfied: lazy-object-proxy<1.5.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.4.3)
Requirement already satisfied: pandas<2.0,>=0.17.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.1.4)
Requirement already satisfied: psutil<6.0.0,>=4.2.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (5.7.3)
Requirement already satisfied: croniter<0.4,>=0.3.17 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.3.36)
Requirement already satisfied: cryptography>=0.9.3; python_version >= "3.0" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (3.2.1)
Requirement already satisfied: packaging in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (20.7)
Requirement already satisfied: iso8601>=0.1.12 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.1.13)
Requirement already satisfied: importlib-metadata~=2.0; python_version < "3.9" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.1.0)
Requirement already satisfied: sqlalchemy~=1.3 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.3.20)
Requirement already satisfied: cattrs<1.1.0,>=1.0; python_version <= "3.6" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.0.0)
Requirement already satisfied: colorlog==4.0.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (4.0.2)
Requirement already satisfied: email-validator in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.1.2)
Requirement already satisfied: funcsigs<2.0.0,>=1.0.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.0.2)
Requirement already satisfied: python-dateutil<3,>=2.3 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.8.1)
Requirement already satisfied: configparser<3.6.0,>=3.5.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (3.5.3)
Requirement already satisfied: jsonschema~=3.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (3.2.0)
Requirement already satisfied: werkzeug<1.0.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.16.1)
Requirement already satisfied: flask-appbuilder~=2.2; python_version >= "3.6" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.3.4)
Requirement already satisfied: argcomplete~=1.10 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.12.2)
Requirement already satisfied: markdown<3.0,>=2.5.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.6.11)
Requirement already satisfied: thrift>=0.11.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.13.0)
Requirement already satisfied: future<0.19,>=0.16.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.18.2)
Requirement already satisfied: setproctitle<2,>=1.1.8 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.2)
Requirement already satisfied: attrs<21.0,>=20.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (20.3.0)
Requirement already satisfied: marshmallow-sqlalchemy<0.24.0,>=0.16.1; python_version >= "3.6" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.23.1)
Requirement already satisfied: pep562~=1.0; python_version < "3.7" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.0)
Requirement already satisfied: flask-admin==1.5.4 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.5.4)
Requirement already satisfied: jinja2<2.12.0,>=2.10.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.11.2)
Requirement already satisfied: python-slugify<5.0,>=3.0.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (4.0.1)
Requirement already satisfied: flask-caching<1.4.0,>=1.3.3 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.3.3)
Requirement already satisfied: alembic<2.0,>=1.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.4.3)
Requirement already satisfied: importlib-resources~=1.4 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.5.0)
Requirement already satisfied: flask-wtf<0.15,>=0.14.2 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.14.3)
Requirement already satisfied: zope.deprecation<5.0,>=4.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (4.4.0)
Requirement already satisfied: typing-extensions>=3.7.4; python_version < "3.8" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (3.7.4.3)
Requirement already satisfied: tzlocal<2.0.0,>=1.4 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.5.1)
Requirement already satisfied: requests<2.24.0,>=2.20.0; python_version >= "3.0" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (2.23.0)
Requirement already satisfied: gunicorn<21.0,>=19.5.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (20.0.4)
Requirement already satisfied: flask<2.0,>=1.1.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (1.1.2)
Requirement already satisfied: tenacity==4.12.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (4.12.0)
Requirement already satisfied: graphviz>=0.12 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.15)
Requirement already satisfied: python-nvd3~=0.15.0 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.15.0)
Requirement already satisfied: unicodecsv>=0.14.1 in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.14.1)
Requirement already satisfied: sqlalchemy-jsonfield~=0.9; python_version >= "3.5" in /home/airflow/.local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.9.0)
Requirement already satisfied: Flask-OAuthlib<0.9.6,>=0.9.1; extra == "google_auth" in /usr/local/lib/python3.6/site-packages (from apache-airflow[google_auth]) (0.9.5)
Collecting requests-oauthlib==1.1.0; extra == "google_auth"
  Downloading requests_oauthlib-1.1.0-py2.py3-none-any.whl (21 kB)
Collecting oauthlib!=2.0.3,!=2.0.4,!=2.0.5,<3.0.0,>=1.1.2; extra == "google_auth"
  Downloading oauthlib-2.1.0-py2.py3-none-any.whl (121 kB)
Requirement already satisfied: docutils in /home/airflow/.local/lib/python3.6/site-packages (from python-daemon>=2.1.1->apache-airflow[google_auth]) (0.15.2)
Requirement already satisfied: setuptools in /usr/local/lib/python3.6/site-packages (from python-daemon>=2.1.1->apache-airflow[google_auth]) (54.1.1)
Requirement already satisfied: lockfile>=0.10 in /home/airflow/.local/lib/python3.6/site-packages (from python-daemon>=2.1.1->apache-airflow[google_auth]) (0.12.2)
Requirement already satisfied: PyYAML>=5.1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-swagger<0.3,>=0.2.13->apache-airflow[google_auth]) (5.3.1)
Requirement already satisfied: pytzdata>=2018.3.0.0 in /home/airflow/.local/lib/python3.6/site-packages (from pendulum==1.4.4->apache-airflow[google_auth]) (2020.1)
Requirement already satisfied: numpy>=1.15.4 in /home/airflow/.local/lib/python3.6/site-packages (from pandas<2.0,>=0.17.1->apache-airflow[google_auth]) (1.19.4)
Requirement already satisfied: pytz>=2017.2 in /home/airflow/.local/lib/python3.6/site-packages (from pandas<2.0,>=0.17.1->apache-airflow[google_auth]) (2020.4)
Requirement already satisfied: natsort in /home/airflow/.local/lib/python3.6/site-packages (from croniter<0.4,>=0.3.17->apache-airflow[google_auth]) (7.1.0)
Requirement already satisfied: six>=1.4.1 in /home/airflow/.local/lib/python3.6/site-packages (from cryptography>=0.9.3; python_version >= "3.0"->apache-airflow[google_auth]) (1.15.0)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in /home/airflow/.local/lib/python3.6/site-packages (from cryptography>=0.9.3; python_version >= "3.0"->apache-airflow[google_auth]) (1.14.4)
Requirement already satisfied: pyparsing>=2.0.2 in /home/airflow/.local/lib/python3.6/site-packages (from packaging->apache-airflow[google_auth]) (2.4.7)
Requirement already satisfied: zipp>=0.5 in /home/airflow/.local/lib/python3.6/site-packages (from importlib-metadata~=2.0; python_version < "3.9"->apache-airflow[google_auth]) (3.4.0)
Requirement already satisfied: dnspython>=1.15.0 in /home/airflow/.local/lib/python3.6/site-packages (from email-validator->apache-airflow[google_auth]) (1.16.0)
Requirement already satisfied: idna>=2.0.0 in /home/airflow/.local/lib/python3.6/site-packages (from email-validator->apache-airflow[google_auth]) (2.8)
Requirement already satisfied: pyrsistent>=0.14.0 in /home/airflow/.local/lib/python3.6/site-packages (from jsonschema~=3.0->apache-airflow[google_auth]) (0.17.3)
Requirement already satisfied: click<8,>=6.7 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (6.7)
Requirement already satisfied: PyJWT>=1.7.1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.7.1)
Requirement already satisfied: marshmallow<3.0.0,>=2.18.0 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (2.21.0)
Requirement already satisfied: Flask-Babel<2,>=1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.0.0)
Requirement already satisfied: Flask-SQLAlchemy<3,>=2.4 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (2.4.4)
Requirement already satisfied: apispec[yaml]<2,>=1.1.1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.3.3)
Requirement already satisfied: Flask-OpenID<2,>=1.2.5 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.2.5)
Requirement already satisfied: Flask-JWT-Extended<4,>=3.18 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (3.25.0)
Requirement already satisfied: marshmallow-enum<2,>=1.4.1 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (1.5.1)
Requirement already satisfied: colorama<1,>=0.3.9 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (0.4.4)
Requirement already satisfied: sqlalchemy-utils<1,>=0.32.21 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (0.36.8)
Requirement already satisfied: prison<1.0.0,>=0.1.3 in /home/airflow/.local/lib/python3.6/site-packages (from flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (0.1.3)
Requirement already satisfied: wtforms in /home/airflow/.local/lib/python3.6/site-packages (from flask-admin==1.5.4->apache-airflow[google_auth]) (2.3.3)
Requirement already satisfied: MarkupSafe>=0.23 in /home/airflow/.local/lib/python3.6/site-packages (from jinja2<2.12.0,>=2.10.1->apache-airflow[google_auth]) (1.1.1)
Requirement already satisfied: text-unidecode>=1.3 in /home/airflow/.local/lib/python3.6/site-packages (from python-slugify<5.0,>=3.0.0->apache-airflow[google_auth]) (1.3)
Requirement already satisfied: Mako in /home/airflow/.local/lib/python3.6/site-packages (from alembic<2.0,>=1.0->apache-airflow[google_auth]) (1.1.3)
Requirement already satisfied: python-editor>=0.3 in /home/airflow/.local/lib/python3.6/site-packages (from alembic<2.0,>=1.0->apache-airflow[google_auth]) (1.0.4)
Requirement already satisfied: itsdangerous in /home/airflow/.local/lib/python3.6/site-packages (from flask-wtf<0.15,>=0.14.2->apache-airflow[google_auth]) (1.1.0)
Requirement already satisfied: certifi>=2017.4.17 in /home/airflow/.local/lib/python3.6/site-packages (from requests<2.24.0,>=2.20.0; python_version >= "3.0"->apache-airflow[google_auth]) (2020.11.8)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /home/airflow/.local/lib/python3.6/site-packages (from requests<2.24.0,>=2.20.0; python_version >= "3.0"->apache-airflow[google_auth]) (1.25.11)
Requirement already satisfied: chardet<4,>=3.0.2 in /home/airflow/.local/lib/python3.6/site-packages (from requests<2.24.0,>=2.20.0; python_version >= "3.0"->apache-airflow[google_auth]) (3.0.4)
Requirement already satisfied: typing>=3.6; python_version < "3.7" in /home/airflow/.local/lib/python3.6/site-packages (from sqlalchemy-jsonfield~=0.9; python_version >= "3.5"->apache-airflow[google_auth]) (3.7.4.3)
Requirement already satisfied: pycparser in /home/airflow/.local/lib/python3.6/site-packages (from cffi!=1.11.3,>=1.8->cryptography>=0.9.3; python_version >= "3.0"->apache-airflow[google_auth]) (2.20)
Requirement already satisfied: Babel>=2.3 in /home/airflow/.local/lib/python3.6/site-packages (from Flask-Babel<2,>=1->flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (2.9.0)
Requirement already satisfied: python3-openid>=2.0 in /home/airflow/.local/lib/python3.6/site-packages (from Flask-OpenID<2,>=1.2.5->flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (3.2.0)
Requirement already satisfied: defusedxml in /home/airflow/.local/lib/python3.6/site-packages (from python3-openid>=2.0->Flask-OpenID<2,>=1.2.5->flask-appbuilder~=2.2; python_version >= "3.6"->apache-airflow[google_auth]) (0.6.0)
Installing collected packages: oauthlib, requests-oauthlib
  Attempting uninstall: oauthlib
    Found existing installation: oauthlib 3.1.0
    Uninstalling oauthlib-3.1.0:
      Successfully uninstalled oauthlib-3.1.0
  Attempting uninstall: requests-oauthlib
    Found existing installation: requests-oauthlib 1.3.0
    Uninstalling requests-oauthlib-1.3.0:
      Successfully uninstalled requests-oauthlib-1.3.0
Successfully installed oauthlib-2.1.0 requests-oauthlib-1.1.0
WARNING: You are using pip version 20.2.4; however, version 21.2.4 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
  ____________       _____________
 ____    |__( )_________  __/__  /________      __
____  /| |_  /__  ___/_  /_ __  /_  __ \_ | /| / /
___  ___ |  / _  /   _  __/ _  / / /_/ /_ |/ |/ /
 _/_/  |_/_/  /_/    /_/    /_/  \____/____/|__/
[2021-08-15 15:22:37,380] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:39,337] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:39,338] {dagbag.py:417} INFO - Filling up the DagBag from /dev/null
[2021-08-15 15:22:39,969] {security.py:478} INFO - Start syncing user roles.
[2021-08-15 15:22:40,349] {security.py:388} INFO - Fetching a set of all permission, view_menu from FAB meta-table
[2021-08-15 15:22:40,507] {security.py:331} INFO - Cleaning faulty perms
[2021-08-15 15:22:42 +0000] [36] [INFO] Starting gunicorn 20.0.4
[2021-08-15 15:22:42 +0000] [36] [INFO] Listening at: http://0.0.0.0:8080 (36)
[2021-08-15 15:22:42 +0000] [36] [INFO] Using worker: sync
[2021-08-15 15:22:42 +0000] [40] [INFO] Booting worker with pid: 40
[2021-08-15 15:22:42 +0000] [41] [INFO] Booting worker with pid: 41
[2021-08-15 15:22:42 +0000] [42] [INFO] Booting worker with pid: 42
[2021-08-15 15:22:42,201] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:42 +0000] [43] [INFO] Booting worker with pid: 43
[2021-08-15 15:22:42,252] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:42,344] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:42,468] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:22:43,483] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:43,485] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:22:43,558] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:43,559] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:22:43,585] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:43,587] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:22:43,676] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:22:43,678] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:24:42 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:40)
[2021-08-15 15:24:42 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:41)
[2021-08-15 15:24:42 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:42)
[2021-08-15 15:24:42 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:43)
[2021-08-15 15:24:43 +0000] [112] [INFO] Booting worker with pid: 112
[2021-08-15 15:24:43 +0000] [113] [INFO] Booting worker with pid: 113
[2021-08-15 15:24:43 +0000] [114] [INFO] Booting worker with pid: 114
[2021-08-15 15:24:43 +0000] [115] [INFO] Booting worker with pid: 115
[2021-08-15 15:24:43,597] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:24:43,616] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:24:43,646] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:24:43,691] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:24:44,848] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:24:44,850] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:24:44,933] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:24:44,935] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:24:44,935] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:24:44,937] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:24:44,973] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:24:44,975] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:26:43 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:112)
[2021-08-15 15:26:43 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:113)
[2021-08-15 15:26:43 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:114)
[2021-08-15 15:26:43 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:115)
[2021-08-15 15:26:44 +0000] [184] [INFO] Booting worker with pid: 184
[2021-08-15 15:26:44 +0000] [185] [INFO] Booting worker with pid: 185
[2021-08-15 15:26:44 +0000] [186] [INFO] Booting worker with pid: 186
[2021-08-15 15:26:44 +0000] [187] [INFO] Booting worker with pid: 187
[2021-08-15 15:26:44,914] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:26:44,924] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:26:44,973] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:26:45,059] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:26:46,167] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:26:46,169] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:26:46,192] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:26:46,194] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:26:46,194] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:26:46,196] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:26:46,250] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:26:46,252] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:28:44 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:184)
[2021-08-15 15:28:44 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:185)
[2021-08-15 15:28:44 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:186)
[2021-08-15 15:28:44 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:187)
[2021-08-15 15:28:45 +0000] [256] [INFO] Booting worker with pid: 256
[2021-08-15 15:28:46 +0000] [257] [INFO] Booting worker with pid: 257
[2021-08-15 15:28:46 +0000] [258] [INFO] Booting worker with pid: 258
[2021-08-15 15:28:46 +0000] [259] [INFO] Booting worker with pid: 259
[2021-08-15 15:28:46,200] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:28:46,243] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:28:46,271] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:28:46,277] {logging_config.py:47} INFO - Successfully imported user-defined logging config from logging_config.LOGGING_CONFIG
[2021-08-15 15:28:47,398] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:28:47,400] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:28:47,559] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:28:47,561] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:28:47,636] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:28:47,638] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags
[2021-08-15 15:28:47,648] {__init__.py:50} INFO - Using executor KubernetesExecutor
[2021-08-15 15:28:47,650] {dagbag.py:417} INFO - Filling up the DagBag from /opt/airflow/dags/dags/dags

The airflow webserver workers keeps timing out

repo: puckel/docker-airflow


text:
Internal Server Error on Import

I've not been able to upload my names. I've got a csv with 2 columns (UniqueID & Name) and ~110,000 rows. I've tried with scv, tab, and excel. Is it just too many entities?

Can you give me some detail: what site are you uploading to? The newest version at opennames.org was taken down, so I assume you mean the one at OKFNLabs?

Hi, and thanks. I was trying to upload here
http://nomenklatura.okfnlabs.org/.
David
On Tue, Jul 7, 2015 at 1:26 AM, Friedrich Lindenberg <
notifications@github.com> wrote:

Can you give me some detail: what site are you uploading to? The newest
version at opennames.org was taken down, so I assume you mean the one at
OKFNLabs?
—
Reply to this email directly or view it on GitHub
https://github.com/pudo/nomenklatura/issues/45#issuecomment-119075993.

I am having exactly the same problem, with an entity list of ~700 rows.  Was there ever a resolution to this?

source: gharchive/issue

authors: disneycorporation pudo shrouta

repo: pudo/nomenklatura

license: mit

license_type: permissive

license_source: bigquery


text:
tutorials on how to integrate gentelella to a wordpress website?

Hi!
I'm currently working on a school project where we have to design a  peer-to-peer dashboard for a website. I have developed the website but now I wanted to integrate gentelella admin to the site and it has been giving me a hard time. Do you have any tutorial I might follow where I can learn more about this subject?

Hi there,
Unfortunately we do not have any guide for it, you need back-end skills. This is a HTML ( front-end ) project only.

repo: puikinsh/gentelella


text:
[WIP] use curation concern base view partials for geo file manager

Closes #892. Uses the curation concerns gem base partials for the geo-specific models.

Needs a rebase against geo_concerns.

Coverage remained the same at 100.0% when pulling 05900aa8fb706c36db96db5667af570be2e50d18 on 892-geo-file-manager into 0f2a72e4e6d9a91cfeb72c23dc61d1014cef7c78 on geo_concerns.

source: gharchive/pull-request

authors: coveralls eliotjordan tampakis

repo: pulibrary/plum


text:
Rerun mktutorial

Pull in latest changes from pulumi/examples (fixed-up links). https://github.com/pulumi/examples/pull/398

Going to merge as this is simply changes that are the result of running mktutorial.

repo: pulumi/docs

license_source: github-api


text:
BucketLifecycleConfigurationV2 has no nonCurrent version action configuration

Describe what happened
When creating an aws.s3.BucketLifecycleConfigurationV2 resource, one would expect to control what happens to objects once they expire. The only "rule type" that is allowed is an expiration rule.  If you go into your bucket lifecycle rule in the AWS console and check the box that says "Permanently delete noncurrent versions of objects", a new noncurrent version action is created in the console. When running a pulumi preview after checking the "Permanently delete noncurrent versions of objects" box, the stack shows a diff in the rules configuration.

Sample program
const bucketName = "superdupermegatestbucketforpulumi"
const bucketLifeCycle = new aws.s3.BucketLifecycleConfigurationV2(`${name}-bucket-lifecycle`, {
                        bucket: bucketName,
                        rules: [{
                            id: "DeleteObjects",
                            status: "Enabled",
                            filter: {
                                prefix: "",
                            },
                            expiration: {
                                days: 3,
                                expiredObjectDeleteMarker: true,
                            },

                        }],
                    });

Log output
 aws:s3:BucketLifecycleConfigurationV2 [redacted]-bucket-lifecycle update [diff: ~rules]
Affected Resource(s)
aws.s3.BucketLifecycleConfigurationV2
Output of pulumi about
Plugins
KIND      NAME        VERSION
resource  aws         6.57.0
resource  awsx        2.16.1
resource  cloudflare  5.42.0
resource  docker      4.5.7
resource  docker      3.6.1
resource  eks         2.8.1
resource  kubernetes  4.18.3
language  nodejs      unknown

Host
OS       debian
Version  bookworm/sid
Arch     x86_64

This project is written in nodejs: executable='/home/dj/.nvm/versions/node/v21.7.2/bin/node' version='v21.7.2'

[redacted stack resources]

Found no pending operations associated with development

Backend
Name           pop-os
URL            file://~
User           dj
Organizations
Token type     personal

Dependencies:
NAME                VERSION
@pulumi/awsx        2.16.1
@pulumi/kubernetes  4.18.3
typescript          4.9.5
@pulumi/pulumi      3.137.0
@types/node         18.19.63
npm-upgrade         3.1.0
prettier            3.3.3
zod                 3.23.8
@pulumi/aws         6.57.0
@pulumi/cloudflare  5.42.0
@pulumi/eks         2.8.1

Additional context
I would want to be able to configure what happens to objects once they expire with Pulumi. It seems this might just be a missing type in the typescript package? Essentially, the end goal is after x number of days, expire the objects in the bucket, then after those x days, delete all expired objects.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hey @davidfries, BucketLifecycleConfigurationV2  has two nonCurrent related actions available.

noncurrentVersionExpiration: Can be used to delete non-current object versions
noncurrentVersionTransitions: Can be used to move non-current objects to other storage classes

This example shows both of them at play.
You should be able to use the noncurrentVersionExpiration option for your usecase.

Hey @flostadler that did the trick! I guess the of noncurrentVersionTransitions was a little confusing in-regards to whether it deletes or does something else. I'll go ahead and mark this closed, thanks for your time and help!

authors: davidfries flostadler

repo: pulumi/pulumi-aws


text:
[WIP] Support for capturing secrets in CallbackFunction

Secrets are captured as environment variables instead of being serialied into program text.  This ensures they are encrypted at rest, do not show up in the state file, and are decrypted and provided to the running Lambda function via environment variables function implicitly by the Lambda runtime infrastructure.
An alternative we are considering, which could be added as opt-in in the future, is to go a step further and create SecretsManager secrets for each captured secret, then inject code to decrypt these using SecretsManager at runtime inside the Lambda.  This involves adding non-trivial additional infrastructure, but would provide an even stronger level of protection (for example, the secrets would not be visible in the Lambda console, and would not be decrypted until/unless actually accessed within the Lambda function).
Part of https://github.com/pulumi/pulumi/issues/2718.

Builds on https://github.com/pulumi/pulumi/pull/3050.

This was addressed in #1282 and #1525. Closing this one out.


text:
EMR Cluster configurationsJSON not rendering language chooser

What happened?
https://www.pulumi.com/registry/packages/aws/api-docs/emr/cluster/ contains examples in the Arguments section, specifically under configurationsJson property. These do render on the page, however unfortunately they do not respect the language chooser.
The schema for the property has the following description which seems to correctly have the PulumiCodeChooser annotation. So I expect that the data is clean but there is some issue with the website rendering. Please let me know if the data needs to look differently.
> $schema Resources aws:emr/cluster:Cluster inputProperties configurationsJson description
JSON string for supplying list of configurations for the EMR cluster.

> **NOTE on `configurations_json`:** If the `Configurations` value is empty then you should skip the `Configurations` field instead of providing an empty list as a value, `"Configurations": []`.

<!--Start PulumiCodeChooser -->
```typescript
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";

const cluster = new aws.emr.Cluster("cluster", {configurationsJson: `[
{
"Classification": "hadoop-env",
"Configurations": [
{
"Classification": "export",
"Properties": {
"JAVA_HOME": "/usr/lib/jvm/java-1.8.0"
}
}
],
"Properties": {}
}
]
`});

import pulumi
import pulumi_aws as aws

cluster = aws.emr.Cluster("cluster", configurations_json="""[
{
"Classification": "hadoop-env",
"Configurations": [
{
"Classification": "export",
"Properties": {
"JAVA_HOME": "/usr/lib/jvm/java-1.8.0"
}
}
],
"Properties": {}
}
]
""")

using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Aws = Pulumi.Aws;

return await Deployment.RunAsync(() =>
{
    var cluster = new Aws.Emr.Cluster("cluster", new()
    {
        ConfigurationsJson = @"[
{
""Classification"": ""hadoop-env"",
""Configurations"": [
{
""Classification"": ""export"",
""Properties"": {
""JAVA_HOME"": ""/usr/lib/jvm/java-1.8.0""
}
}
],
""Properties"": {}
}
]
",
    });

});

package main

import (
        "github.com/pulumi/pulumi-aws/sdk/v6/go/aws/emr"
        "github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
        pulumi.Run(func(ctx *pulumi.Context) error {
                _, err := emr.NewCluster(ctx, "cluster", &emr.ClusterArgs{
                        ConfigurationsJson: pulumi.String(`[
{
"Classification": "hadoop-env",
"Configurations": [
{
"Classification": "export",
"Properties": {
"JAVA_HOME": "/usr/lib/jvm/java-1.8.0"
}
}
],
"Properties": {}
}
]
`),
                })
                if err != nil {
                        return err
                }
                return nil
        })
}

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.aws.emr.Cluster;
import com.pulumi.aws.emr.ClusterArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var cluster = new Cluster("cluster", ClusterArgs.builder()
            .configurationsJson("""
[
{
"Classification": "hadoop-env",
"Configurations": [
{
"Classification": "export",
"Properties": {
"JAVA_HOME": "/usr/lib/jvm/java-1.8.0"
}
}
],
"Properties": {}
}
]
            """)
            .build());

    }
}

resources:
  cluster:
    type: aws:emr:Cluster
    properties:
      configurationsJson: |
        [
        {
        "Classification": "hadoop-env",
        "Configurations": [
        {
        "Classification": "export",
        "Properties": {
        "JAVA_HOME": "/usr/lib/jvm/java-1.8.0"
        }
        }
        ],
        "Properties": {}
        }
        ]

### Example

See above.

### Output of `pulumi about`

N/A

### Additional context

N/A

### Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

I think this is a dup of https://github.com/pulumi/registry/issues/3935. cc @sean1588

repo: pulumi/pulumi-hugo


text:
Address overview pages that do not meet content requirements

We added a check to the registry to ensure the package overview page is not blank and also contains a minimal amount of content (at least 250 characters). We have added the current failing packages to an exceptions list for now in order to get the tests passing until these get addressed.
Here is a list of the current failures:
ERROR: The content in the overview file, themes/default/content/registry/packages/heroku/_index.md, does not meet the 250 character minimum requirement for content.
ERROR: The content in the overview file, themes/default/content/registry/packages/junipermist/_index.md, does not meet the 250 character minimum requirement for content.
ERROR: The content in the overview file, themes/default/content/registry/packages/meraki/_index.md, does not meet the 250 character minimum requirement for content.
ERROR: The content in the overview file, themes/default/content/registry/packages/packet/_index.md, does not meet the 250 character minimum requirement for content.
ERROR: The content in the overview file, themes/default/content/registry/packages/sdwan/_index.md, does not meet the 250 character minimum requirement for content.

We need to get heroku,  junipermist, meraki, packet, and sdwan addessed.

The check is here:
https://github.com/pulumi/registry/blob/13f5f8f9fdf45619d984e7e73ae15a37c82ffb66/scripts/ci/validate-packages.sh#L50-L51

Let's reconsider this as a P1. I'm not sure we should address this in the general case, but I'm doubly unsure this needs to be prioritized to the next item, having sat unaddressed and unassigned for 2 months.

repo: pulumi/registry


text:
decodeURI

i get this error when i try to get the tokens??
if(xs && xs.indexOf('%')) xs = decodeURIComponent(xs);
                               ^

URIError: URI malformed

I made it use decode because lots of users don't decode their cookies before use and reporting problems because of this.
https://github.com/pulviscriptor/agario-client/blob/master/account.js#L50
If you really need % symbol (which i think you don't and you have some problem somewhere setting xs to some wrong value) you can encode your cookies https://developer.mozilla.org/ru/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent

Using Regular Expression (in my next PR), we can try to find out if using decodeURIComponent is really necessary.
var find_hex = /\%[0-9A-F]{2}/i;
...
if(xs && xs.match(find_hex)) xs = decodeURIComponent(xs);

Updated NPM package to 1.3.7 with DRSDavidSoft's fix.

authors: DRSDavidSoft Nick8fr32 pulviscriptor

repo: pulviscriptor/agario-client


text:
2 smal thing missed in dcbcc56228

Hi,
while your big cleanup you missed 2 little things.
You left the old  upnp/src/genlib/client_table/ClientSubscription.c file after creating the new one.
In  upnp/src/genlib/net/http/httpreadwrite.c You have alloca.h included in line 58, but it's not available under win, so it has to go somewhere under line 69.
I would send an PR for that, but after the rebase, I all my stuff till now would be included.

Hi Vollstrecker,
Fixed, thanks!

authors: Vollstrecker mrjimenez

repo: pupnp/pupnp


text:
Running simultaneous tracings

The API docs states that only one tracing can be active per browser. Could someone elaborate on why this is and will this ever change in the future?
Ideally I'd like to open multiple pages and start tracing on each of them simultaneously rather than running multiple browsers in parallel.

I'd like to open multiple pages and start tracing on each of them simultaneously rather than running multiple browsers in parallel.

@paulirish is this something we can do?

If tracing was a browser level, what page would screenshots be taken of?

Tracing is designed to be browser wide. There is currently no ability to have multiple overlapping traces and I don't expect us to add it anytime soon.
There is a hack implemented to choose which rendering process we take screenshots of. It chooses the foreground tab.

Thanks, that answers the question for me. Do you have any tips on how to make the tracing a bit more lightweight though?
I'm currently trying out different approaches of measuring page speed and using Puppeteer is the most accurate solution I've found so far. The only problem I have with it is that it's hard to scale without making it costly or impacting the results. You have to be careful when running multiple browsers and tracings in parallell so that they do not hog too CPU.
Net bandwidth is also a problem of course, but that's a totally different beast which I guess is a problem with whatever solution I go with.

@paulirish

There is a hack implemented to choose which rendering process we take screenshots of. It chooses the foreground tab.

I have something like that:
const page1 = await browser.newPage();
const page1.tracing.start({ screenshots: true, path: "trace.json" });
// do stuff with page1
const page2 = await browser.newPage();
await page2.bringToFront();
// do stuff with page2
await page1.tracing.stop();

But screenshots are only taken on page 1
Is there any way of getting a recording of across multiple tabs?

Is there any way of getting a recording of across multiple tabs?

the trace by default includes ALL pages/processes. however the screenshot thing doesn't. and probably won't ever.

authors: ArnaudBarre JoelEinbinder aslushnikov paulirish simonklb

repo: puppeteer/puppeteer


text:
Add forced-colors to emulateMediaFeature

Now that forced-colors can be emulated in chromium we should add this ability to puppeteer. This will allow us to better test high contrast mode.

I’m interested in this as well, and emulation of prefers-contrast too, so had a look at what’s needed to make this work.

Here’s the code that needs updating: https://github.com/puppeteer/puppeteer/blob/e6442dd767ed5958d84eea907ee8075cb3534599/src/common/Page.ts#L2370-L2388
As far as I can see the only changes needed are to allow those media features in the validation regex, and add tests / docs, identically to what was done in #6761 / #6857 for color-gamut.

If someone needs this in the meantime, you can use a CDPSession directly and call CDP’s Emulation.setEmulatedMedia. Something like:
const client = await page.target().createCDPSession();
await client.send("Emulation.setEmulatedMedia", {
  features: [{ name: "forced-colors", value: "active" }],
})

Any updates on when this functionality will be available?

authors: axli20 jnurthen thibaudcolas


text:
Plan not running in order

Describe the Bug
When I run the plan shown below, the second target shows the prompt prior to the two out messages that are in the code before it.
Expected Behavior
I expect plans to run, and display output, in the same order as they are coded.
Steps to Reproduce
Using this plan:
  get_targets($targets).each |$target| {
    out::message('')
    $_agent_certname = run_command('puppet config print certname', $target, 'Getting agent certname').first['stdout'].rstrip()
    if $target.name != $_agent_certname {
      out::message("${target.name} has a certname of ${_agent_certname}")
    }

    run_command("ls -l ${_ca_ssl_dir}/ca/signed/${_agent_certname}.pem", $ca_server, 'Verify certificate exists')

    $_expiration_check_description = 'Getting the expiration date of the agent certificate'
    $_exiration_check_command = "cat ${_ca_ssl_dir}/ca/signed/${_agent_certname}.pem | openssl x509 -noout -enddate |cut -d '=' -f2"
    $_expiration_date = run_command($_exiration_check_command, $ca_server, $_expiration_check_description).first['stdout'].rstrip()
    out::message("${target.name}'s cert expriation: ${_expiration_date}")

    # Confirm we are good to keep going
    out::message('Shall we continue? Valid choices are:')
    $menu = { 'y' => 'yes', 'n' => 'no' }
    $selection = prompt::menu('Keep going?', $menu)
    if $selection == 'no' {
      out::message("Skipping remaining steps for ${target.name}")
    } else {
      # do other stuff
    }
  }

I get this:
$ bolt plan run ltn_sre_utils::servers::update_agent_cert --run-as root --sudo-password $boltpw --targets was-portal-web-qa-1.example.net,was-portal-web-qa-2.example.net
Starting: plan ltn_sre_utils::servers::update_agent_cert
Starting: Get ssldir path on col-ca.int.example.com
Finished: Get ssldir path with 0 failures in 1.69 sec

Starting: Getting agent certname on was-portal-web-qa-1.example.net
Finished: Getting agent certname with 0 failures in 1.05 sec
Starting: Verify certificate exists on col-ca.int.example.com
Finished: Verify certificate exists with 0 failures in 1.2 sec
Starting: Getting the expiration date of the agent certificate on col-ca.int.example.com
Finished: Getting the expiration date of the agent certificate with 0 failures in 1.22 sec
was-portal-web-qa-1.example.net's cert expriation: Oct 10 20:20:27 2028 GMT
Shall we continue? Valid choices are:
(y) yes
(n) no
Keep going?: n
Skipping remaining steps for was-portal-web-qa-1.example.net

Starting: Getting agent certname on was-portal-web-qa-2.example.net
Finished: Getting agent certname with 0 failures in 0.97 sec
Starting: Verify certificate exists on col-ca.int.example.com
Finished: Verify certificate exists with 0 failures in 1.17 sec
Starting: Getting the expiration date of the agent certificate on col-ca.int.example.com
(y) yes
(n) no
Keep going?: n
Finished: Getting the expiration date of the agent certificate with 0 failures in 1.23 sec
was-portal-web-qa-2.example.net's cert expriation: Oct  2 16:12:05 2023 GMT
Shall we continue? Valid choices are:
Skipping remaining steps for was-portal-web-qa-2.example.net
Finished: plan ltn_sre_utils::servers::update_agent_cert in 11.99 sec
Plan completed successfully with no result

Note that on the second target that the out::message()'s are showing up after the yes/no prompt.
Environment

Version 3.27.4
Platform macOS 13.5.2

Additional Context
I chatted about this in the community Slack and Nick Burgan posited this idea:

I’m guessing it has to do with the fact that the starting/finished messages are going through Bolt::Logger and prompt is writing directly to stderr

I'm also experiencing this issue with some of my plans

Thanks for the report. Will try to take a look soon.

authors: donoghuc genebean kruegerkyle95

repo: puppetlabs/bolt


text:
(CONT-234) Fix failing parameterised command test

Prior to this commit, the MVP failed a few tests. One such test expects a parameterised command (ie the command parameters are placed in an array) to detect 0 problems. The MVP failed this test as it raised a warning if an input variable was found regardless of the context in which it was found.
This commit fixes this failing test by adding a function which checks if a command is parameterised. This function returns true if an LBRACE is found directly after the FARROW.
This commit also reduces some complexity in how each command is parsed. Previously, there were leading tokens included at the start of each command that were unnecessary to check during iterations. This commit checks for the command token and starts a while loop from there to iterate over each token in the command. This makes the logic of the code more straight forward and easier to understand.

Thanks for the great context in the PR description too!

authors: GSPatton chelnak


text:
(maint) Amazon linux reports majrelease as '2018'

Currently, On AmazonLinux, every puppet run throws this warning message:
Warning: Found multiple default providers for package: yum, pip3, puppet_gem; using yum

Here is the os facts hash on Amazon Linux:
# facter -p os
{
  architecture => "x86_64",
  family => "RedHat",
  hardware => "x86_64",
  name => "Amazon",
  release => {
    full => "2018.03",
    major => "2018",
    minor => "03"
  },
  selinux => {
    enabled => false
  }
}

Here is the os facts hash on Amazon Linux 2:
# facter -p os
{
  architecture => "x86_64",
  family => "RedHat",
  hardware => "x86_64",
  name => "Amazon",
  release => {
    full => "2",
    major => "2"
  },
  selinux => {
    enabled => false
  }
}

Can one of the admins verify this patch?

first time contributor! 🎉

I made another push to try and fix the failing test for an improperly formatted commit message 😅

Hi @cabrinha ! Thank you for your contribution!
It looks like you were able to update the commit, but git got a little confused. You'll want to squash your commits (git rebase -i HEAD~2) .
That'll open an editor with the following
  1 pick 99589ac4d4 (maint) Amazon linux reports majrelease as '2018'
  2 pick e0050b0030 Amazon linux reports majrelease as '2018'

Change the second pick to either f or fixup, save the change, and exit the file.
Once you've squashed your commits, you'll have to force push to your development branch (git push -f cabrinha amazon-linux). You may have to change cabrinha to whatever your own fork of the puppet repo is named.
Let me know if that makes sense, or if you'd like more git guidance!
I also have two more questions for you. We have code for Amazon Linux to default to systemd: https://github.com/puppetlabs/puppet/commit/763d01a2083efccada8d933dc69d944ce99b333c and https://github.com/puppetlabs/puppet/commit/621e4d00bef367b8ca9e01e0222518affd0800d0
I'm personally not super familiar with Amazon Linux, but I'd like to get confirmation which package manager we should be defaulting to here. I'll try to get review from someone with more knowledge in this area than me.
Finally, we probably want to also add tests. See the above commits I linked for test examples.
@puppetlabs/platform-os can you weight in on this PR? Which package management system should we be using on Amazon Linux?

Waiting for CLA signature by @cabrinha
@cabrinha - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html

Hi @cabrinha ! Thank you for your contribution!
It looks like you were able to update the commit, but git got a little confused. You'll want to squash your commits (git rebase -i HEAD~2) .
That'll open an editor with the following
  1 pick 99589ac4d4 (maint) Amazon linux reports majrelease as '2018'
  2 pick e0050b0030 Amazon linux reports majrelease as '2018'

Change the second pick to either f or fixup, save the change, and exit the file.
Once you've squashed your commits, you'll have to force push to your development branch (git push -f cabrinha amazon-linux). You may have to change cabrinha to whatever your own fork of the puppet repo is named.
Let me know if that makes sense, or if you'd like more git guidance!

Thanks for the help @melissa! I know git rebases and merges can get pretty messy sometimes. I think I've fixed the commit now.

I also have two more questions for you. We have code for Amazon Linux to default to systemd: 763d01a and 621e4d0
I'm personally not super familiar with Amazon Linux, but I'd like to get confirmation which package manager we should be defaulting to here. I'll try to get review from someone with more knowledge in this area than me.
Finally, we probably want to also add tests. See the above commits I linked for test examples.
@puppetlabs/platform-os can you weight in on this PR? Which package management system should we be using on Amazon Linux?

The default package manager for Amazon Linux 1 and 2 should be yum.
I think we should be adding more to the :operatingsystemmajrelease => [] array as well. Under the "Release Notes" section of Amazon Linux AMI documentation, the releases range from 2011 to 2018 for Amazon Linux 1. Amazon Linux 2 reports it's operatingsystemmajrelease simply as '2'.
Amazon Linux 1 doesn't use systemd, it uses upstart/sysvinit. Amazon Linux 2 uses systemd.

Waiting for CLA signature by @cabrinha
@cabrinha - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html

I went ahead and clicked through the prompts. Let me know if anything else is needed.

CLA signed by all contributors.

Oh my gosh, I can't believe I mixed up service providers and package managers... Sorry about that confusion.
I'm having trouble getting eyes on this from the team that normally maintains these platform specific types & providers. That being said, your link to the Amazon Linux AMI documentation looks sufficient. You've convinced me.
It might be good to add a little more disambiguation between Amazon Linux and Redhat. Is there any reason we can't add a new, more specific default? Something like defaultfor :osname => :amazon, :operatingsystemmajrelease => [2018]. Again, I've never actually looked at the facter output on an AL box, so this might not be quite the right syntax.

Oh my gosh, I can't believe I mixed up service providers and package managers... Sorry about that confusion.
I'm having trouble getting eyes on this from the team that normally maintains these platform specific types & providers. That being said, your link to the Amazon Linux AMI documentation looks sufficient. You've convinced me.
It might be good to add a little more disambiguation between Amazon Linux and Redhat. Is there any reason we can't add a new, more specific default? Something like defaultfor :osname => :amazon, :operatingsystemmajrelease => [2, 2018]. Again, I've never actually looked at the facter output on an AL box, so this might not be quite the right syntax.

@melissa I've included the facter output from AMZ 1 and AMZ 2 in my first comment.
I'd love to add a new, more specific default instead of lumping Amazon together with RedHat. I'm just not sure how. I'm also stuck on writing these spec tests. They're not very similar to the systemd spec tests when it comes to syntax, so I'm not sure how to get started on that.
If someone wants to walk me through it, I'd be happy to update this PR, otherwise, I'm open to having someone else take over this PR 😄

Oh, another point, if we're moving this to it's own line, then we don't have to have an os version constraint.
defaultfor :operatingsystem => :amazon

Are you looking at add tests to spec/unit/provider/package/yum_spec.rb? I'm happy to help with that! What do you have so far?

Oh, another point, if we're moving this to it's own line, then we don't have to have an os version constraint.
defaultfor :operatingsystem => :amazon

Good point, I added a new commit for that. Not sure if it's correct though.

Are you looking at add tests to spec/unit/provider/package/yum_spec.rb? I'm happy to help with that! What do you have so far?

Yes, I think thats where the spec tests for this need to go.
I've done nothing so far besides compare yum_spec.rb to systemd_spec.rb and I'm confused 😄

In your update, you're using the example I originally gave: :osname, but I think we should use the same check they're using in systemd, which is going to be defaultfor :operatingsystem => :amazon. The tests below assume you've changed osname to operatingsystem. I have no idea which is preferable :(
I'm not sure if you only wanted a hint, but here's what I would add. Feel free to copy/modify/change/update/reword/etc as you see fit.
diff --git a/spec/unit/provider/package/yum_spec.rb b/spec/unit/provider/package/yum_spec.rb
index 53f3969c0f..59a5c18079 100644
--- a/spec/unit/provider/package/yum_spec.rb
+++ b/spec/unit/provider/package/yum_spec.rb
@@ -12,6 +12,40 @@ describe Puppet::Type.type(:package).provider(:yum) do
     expect(described_class.specificity).to be < 200
   end

+  describe "should have logical defaults" do
+    [2,2018].each do |ver|
+      it "should be the default provider on Amazon Linux #{ver}" do
+        allow(Facter).to receive(:value).with(:operatingsystem).and_return('amazon')
+        allow(Facter).to receive(:value).with(:osfamily).and_return('redhat')
+        allow(Facter).to receive(:value).with(:operatingsystemmajrelease).and_return('2018')
+        expect(described_class).to be_default
+      end
+    end
+
+    Array(4..7).each do |ver|
+      it "should not be default for redhat #{ver}" do
+        allow(Facter).to receive(:value).with(:operatingsystem).and_return('redhat')
+        allow(Facter).to receive(:value).with(:osfamily).and_return('redhat')
+        allow(Facter).to receive(:value).with(:operatingsystemmajrelease).and_return(ver.to_s)
+        expect(described_class).to be_default
+      end
+    end
+
+    it "should not be default for redhat 8" do
+      allow(Facter).to receive(:value).with(:operatingsystem).and_return('redhat')
+      allow(Facter).to receive(:value).with(:osfamily).and_return('redhat')
+      allow(Facter).to receive(:value).with(:operatingsystemmajrelease).and_return('8')
+      expect(described_class).not_to be_default
+    end
+
+    it "should not be default for Ubuntu 16.04" do
+      allow(Facter).to receive(:value).with(:operatingsystem).and_return('ubuntu')
+      allow(Facter).to receive(:value).with(:osfamily).and_return('ubuntu')
+      allow(Facter).to receive(:value).with(:operatingsystemmajrelease).and_return('16.04')
+      expect(described_class).not_to be_default
+    end
+  end

These tests, without your change, give me
$ bundle exec rspec --seed 123 --format documentation spec/unit/provider/package/yum_spec.rb:15
Run options:
  include {:locations=>{"./spec/unit/provider/package/yum_spec.rb"=>[15]}}
  exclude {:broken=>true, :benchmark=>true}

Randomized with seed 123

Puppet::Type::Package::ProviderYum
  should have logical defaults
    should not be default for redhat 4
    should not be default for redhat 8
    should be the default provider on Amazon Linux 2018 (FAILED - 1)
    should not be default for redhat 7
    should not be default for Ubuntu 16.04
    should be the default provider on Amazon Linux 2 (FAILED - 2)
    should not be default for redhat 5
    should not be default for redhat 6

Failures:

  1) Puppet::Type::Package::ProviderYum should have logical defaults should be the default provider on Amazon Linux 2018
     Failure/Error: expect(described_class).to be_default
       expected `Puppet::Type::Package::ProviderYum.default?` to return true, got false
     # ./spec/unit/provider/package/yum_spec.rb:21:in `block (4 levels) in <top (required)>'

  2) Puppet::Type::Package::ProviderYum should have logical defaults should be the default provider on Amazon Linux 2
     Failure/Error: expect(described_class).to be_default
       expected `Puppet::Type::Package::ProviderYum.default?` to return true, got false
     # ./spec/unit/provider/package/yum_spec.rb:21:in `block (4 levels) in <top (required)>'

Finished in 0.06879 seconds (files took 1.67 seconds to load)
8 examples, 2 failures

Failed examples:

rspec ./spec/unit/provider/package/yum_spec.rb[1:3:2] # Puppet::Type::Package::ProviderYum should have logical defaults should be the default provider on Am
azon Linux 2018
rspec ./spec/unit/provider/package/yum_spec.rb[1:3:1] # Puppet::Type::Package::ProviderYum should have logical defaults should be the default provider on Am
azon Linux 2

Randomized with seed 123

which is what we want!
with your change, it's
$ bundle exec rspec --seed 123 --format documentation spec/unit/provider/package/yum_spec.rb:15
Run options:
  include {:locations=>{"./spec/unit/provider/package/yum_spec.rb"=>[15]}}
  exclude {:broken=>true, :benchmark=>true}

Randomized with seed 123

Puppet::Type::Package::ProviderYum
  should have logical defaults
    should not be default for redhat 4
    should not be default for redhat 8
    should be the default provider on Amazon Linux 2018
    should not be default for redhat 7
    should not be default for Ubuntu 16.04
    should be the default provider on Amazon Linux 2
    should not be default for redhat 5
    should not be default for redhat 6

Finished in 0.06041 seconds (files took 1.63 seconds to load)
8 examples, 0 failures

Randomized with seed 123

Full set of changes:
$ git diff upstream/master
diff --git a/lib/puppet/provider/package/yum.rb b/lib/puppet/provider/package/yum.rb
index 1a00b88424..405184ba78 100644
--- a/lib/puppet/provider/package/yum.rb
+++ b/lib/puppet/provider/package/yum.rb
@@ -22,6 +22,7 @@ Puppet::Type.type(:package).provide :yum, :parent => :rpm, :source => :rpm do
       end
   end

+defaultfor :operatingsystem => :amazon
 defaultfor :osfamily => :redhat, :operatingsystemmajrelease => (4..7).to_a

   def self.prefetch(packages)
diff --git a/spec/unit/provider/package/yum_spec.rb b/spec/unit/provider/package/yum_spec.rb
index 53f3969c0f..59a5c18079 100644
--- a/spec/unit/provider/package/yum_spec.rb
+++ b/spec/unit/provider/package/yum_spec.rb
@@ -12,6 +12,40 @@ describe Puppet::Type.type(:package).provider(:yum) do
     expect(described_class.specificity).to be < 200
   end

+  describe "should have logical defaults" do
+    [2,2018].each do |ver|
+      it "should be the default provider on Amazon Linux #{ver}" do
+        allow(Facter).to receive(:value).with(:operatingsystem).and_return('amazon')
+        allow(Facter).to receive(:value).with(:osfamily).and_return('redhat')
+        allow(Facter).to receive(:value).with(:operatingsystemmajrelease).and_return('2018')
+        expect(described_class).to be_default
+      end
+    end
+
+    Array(4..7).each do |ver|
+      it "should not be default for redhat #{ver}" do
+        allow(Facter).to receive(:value).with(:operatingsystem).and_return('redhat')
+        allow(Facter).to receive(:value).with(:osfamily).and_return('redhat')
+        allow(Facter).to receive(:value).with(:operatingsystemmajrelease).and_return(ver.to_s)
+        expect(described_class).to be_default
+      end
+    end
+
+    it "should not be default for redhat 8" do
+      allow(Facter).to receive(:value).with(:operatingsystem).and_return('redhat')
+      allow(Facter).to receive(:value).with(:osfamily).and_return('redhat')
+      allow(Facter).to receive(:value).with(:operatingsystemmajrelease).and_return('8')
+      expect(described_class).not_to be_default
+    end
+
+    it "should not be default for Ubuntu 16.04" do
+      allow(Facter).to receive(:value).with(:operatingsystem).and_return('ubuntu')
+      allow(Facter).to receive(:value).with(:osfamily).and_return('ubuntu')
+      allow(Facter).to receive(:value).with(:operatingsystemmajrelease).and_return('16.04')
+      expect(described_class).not_to be_default
+    end
+  end
+
   describe "when supplied the source param" do
     let(:name) { 'baz' }

Nice job squashing the commits!
Would you also be willing to add the facter output to the commit message? It'll help folks in the future when messing with amazon things.

Actually, we should update the commit message to be a bit more descriptive before we merge this in.
In this commit message, we don't really care that Amazon Linux reports majrelease as 2018, we care that Amazon Linux has a default package manager and that default is yum.
Something along the lines of
(maint) Default Amazon Linux to yum

Prior to this commit, Amazon Linux did not have a default package provider set. This commit ensures that all versions of Amazon Linux will default to using the yum package provider.

Users will no longer get a warning about multiple default package providers.

We should update the commit message to be a bit more descriptive before we merge this in.
In this commit message, we don't really care that Amazon Linux reports majrelease as 2018, we care that Amazon Linux has a default package manager and that default is yum.
Something along the lines of
(maint) Default Amazon Linux to yum

Prior to this commit, Amazon Linux did not have a default package provider set. This commit ensures that all versions of Amazon Linux will default to using the yum package provider.

Users will no longer get a warning about multiple default package providers.

Done and done. Thanks for all the help!

👍 Probably want to squash the two commits in this PR into a single one.  As-is, the second commit's message will fail the commit message checker in the travis tests, and since it's fixing the title of a brand new test, it may as well be added with the fixed title in the first place. 😄

👍 Probably want to squash the two commits in this PR into a single one. As-is, the second commit's message will fail the commit message checker in the travis tests, and since it's fixing the title of a brand new test, it may as well be added with the fixed title in the first place. 😄

Squashed.

@cabrinha Thanks for all your work on this!

authors: binford2k cabrinha jhelwig melissa puppetcla puppetlabs-jenkins

repo: puppetlabs/puppet


text:
Add unionWith

It's seems like it could be useful. Right now I use a couple of newtypes with different semigroup instances for this

We merged https://github.com/purescript/purescript-foreign-object/pull/19 so we could implement the Semigroup instance with append = unionWith (<>) in this pull request.
Tests should pass with a rebase once https://github.com/purescript/purescript-foreign-object/pull/22 is merged.

repo: purescript/purescript-foreign-object


text:
fix-issue75

Related Issue
Designed Add post question page using Figma
Closes: #75
Describe the changes you've made
Created the Add post question page using Figma as per the mentioned colors and sample
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Screenshots

Original
Updated

**

**

@Chadha93 have you added this to the figma design?

Yes I have added it just now you can see

Yes I have added it just now you can see

Good Work 👍
Let me merge this.

license: MIT


text:
PostgreSQL SERIAL type concerns

Hi Ian,
I was recently reading the Postgres wiki and came across this.
Looks like Cloak has the SERIAL type in a few places, is the use of it concerning?

@farazfazli Yes, good catch.
We should definitely move over to this.

authors: farazfazli ianpurton

repo: purton-tech/cloak


text:
Update XCode project setting to match Swift version with SDK

To resolve #14

Thanks @eggli, merged and published in 1.0.8.
To update, please run the following command in your root project directory:
npm install pushy-react-native@1.0.8 --save

Run the following command to relink the iOS native module to your project:
react-native unlink pushy-react-native
react-native link pushy-react-native

Then, recompile and let us know whether the issue is resolved.

authors: eggli pushy-me

repo: pushy-me/pushy-react-native


text:
🛑 PMB is down

In fb9768d, PMB (https://pmb.unmer.ac.id/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PMB is back up in 5d334a0 after 4 minutes.

repo: pusimgit/upptime


text:
Windows does not allow for a colon in the file name, and this will cause the sync to hault

Windows will not allow for a colon in a path or file name, among others. If that happens the sync errors out and grinds to a stop. Was unsure if this belonged in the putio-sync or putio-sync-desktop repo so I've posted it in both.
Two changes could be made to address this:

Remove colons.

When this error is encountered, log it, and continue to the next file

This is the full list of restricted characters that can not be in a path or file URL on Windows. In practice, all of them should be removed.

< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)

Source: https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions

For now I chose to skip syncing the files containing restricted characters because it was simple and easy. If there will be demand for it we can think of a more complex solution.

authors: bryancasler cenkalti

repo: putdotio/putio-sync


text:
🛑 Media Storage is down

In ed1a972, Media Storage ($SITES_URL_STORAGE) was down:

HTTP code: 405
Response time: 638 ms

Resolved: Media Storage is back up in 84d6f68.


text:
🛑 Plex is down

In 08c3ee3, Plex ($SITES_URL_PLEX) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Plex is back up in f2640a5.


text:
点赞

楼主好文，何不搞个博客呢？

我怕会 React 的人多了之后，就跟我抢工作机会了。
你看看就行，也千万别给别人说。

repo: puxiao/react-hook-tutorial

license: Unlicense


text:
[Safari-only] Unable to establish Slack connection – fetch error

Just tested latest build on Safari with my test Slack token – appears data isn't being fetched correctly. Seems to be the same issue as referenced here.
Scope
Safari-only, works fine in other browser environments.
Error
Can't find variable: fetch on Line 82
Involved function
function TeamInfoRequest(){
    return fetch("https://slack.com/api/team.info?token=" + slackToken, requestOptions).then((response)=>{return response.json()});
}

@yasinS Can you test if this bug is still appearing?

@pvdsp Just trying to test now but unsure on how to initialise Bower and compile. Doesn't seem like bower.json contains any packages? Will be able to add these steps to README.md when working.

@yasinS I, unfortunately, am not familiar with Bower. I'm afraid I can't help for now. I'm trying to find it out.

@yasinS Is it fixed now? I can't test atm but I changed the paths to a cdn.

Closing issue, resolved as noted here.

authors: pvdsp yasinS

repo: pvdsp/slack-statistics


text:
fix ROS2 compile error

UnitySensors 2.0.4に存在するROS2コンパイルエラーの問題に対する対処です。

ref #70

repo: pwri-opera/OperaSim-PhysX


text:
Add CDI service activity monitoring

https://diplomky.redhat.com/topic/show/401/service-activity-monitoring-for-silverware

We could use a similar strategy as in https://github.com/panossot/jboss-automated-metrics

https://github.com/astefanutti/metrics-cdi

https://groups.google.com/forum/#!topic/microprofile/rccA-oAbxcU


text:
TODO: implement kill-ring

Implement Emacs style killing and yanking text.

C-k to kill from cursor to the end of line
C-u to kill from cursor to the beginning of the line
C-y to yank (paste) the content from the kill ring

and so on.

#10 implements kill-ring


text:
Drawer Header Icon Alignment wrong

Describe the bug
the drawer header nav icon is misaligned

What is the expected behavior?
Should work
What are the steps to reproduce?

Go to...
Click on...

Screenshots or links to minimum reproduction example
Environment

Anything else to add?

might be an iOS / Safari specific issue

repo: pxblue/react-component-library


text:
fix failing tests

[ ] fix failing tests https://travis-ci.org/py4n6/pytsk/jobs/259257707

sleuthkit/tsk/fs/fs_open.c:122:9: note: use option -std=c99 or -std=gnu99 to compile your code
error: command 'gcc' failed with exit status 1

[ ] update travis configuration https://blog.travis-ci.com/2017-07-11-trusty-as-default-linux-is-coming?utm_source=web&utm_medium=banner&&utm_campaign=trusty-default

https://github.com/sleuthkit/sleuthkit/issues/880

sys/stat.h missing from sleuthkit/tsk/img/raw.c

added sys/types.h to talloc.c
remove inline definition

Linux tests passing: https://travis-ci.org/py4n6/pytsk/builds/259532056

https://travis-ci.org/py4n6/pytsk/jobs/259535371#L1426
error: invalid argument '-std=c99' not allowed with 'C++/ObjC++'
error: command 'clang' failed with exit status 1

Changed approach to patch sleuthkit code to be c89 compatible.
Added AppVeyor tests

Linux and osx tests passing: https://travis-ci.org/py4n6/pytsk/builds/259652157

https://github.com/sleuthkit/sleuthkit/issues/882

Windows test passing: https://ci.appveyor.com/project/joachimmetz/pytsk/build/9


text:
feat: categorical slider [WIP]

This adds a new QCategoricalSlider and QLabeledCategoricalSlider, when you want a slider to select from a discrete set of objects (rather than numbers).  Similar to a combobox I guess, but easier to change between all the values.
API still needs consideration
from qtpy.QtWidgets import QApplication

from superqt.sliders import QLabeledCategoricalSlider

app = QApplication([])
slider = QLabeledCategoricalSlider(
    categories=["dog", "cat", "elephant", "bird", "fish"]
)
slider.show()
slider.categoryChanged.connect(lambda category: print(category))
app.exec()

https://github.com/user-attachments/assets/43ab9ead-2282-45c2-b166-79975e37648a
edit: the label is now a combobox to allow two-way editing

Maybe also add an enum version of it?

repo: pyapp-kit/superqt


text:
Create optional out argument for transpose and copy in StencilMatrix and BlockLinearOperator

This PR implements the possibility to pass an out argument to the methods copy and transpose of classes StencilMatrix and BlockLinearOperator.
This is specially usefull to avoid creating temporaries when one copy/transpose frequently Operator for example in the case of iterative algorithm that update a matrix at every step.
Some tests were added to check the implementation.

The transpose method is an abstractmethod of the base class LinearOperator (see here).
A question therefore arises: should we add the optional out argument to LinearOperator?
CC: @jowezarek

I think it makes sense to add an out option to the copy and transpose method for all LinearOperator.
It is something I implemented in my branch because without this possibility, in the case of iterative algorithm I was not even able to run the simulation because of out of memory error.

Currently copy is not part of the abstract interface of the LinearOperator base class. Should we add it?

We can modify the base class LinearOperator in a separate PR.
For now please check that the new code works in parallel by adding the out argument to linalg.tests.test_stencil_matrix_2d_parallel_transpose

We can modify the base class LinearOperator in a separate PR.
For now please check that the new code works in parallel by adding the out argument to linalg.tests.test_stencil_matrix_2d_parallel_transpose.
Please also create a parallel test in linalg.tests.test_block.

Test created in 715eb4a

Apparently the parallel implementation needs a bit more work! 😅

Apparently the parallel implementation needs a bit more work! 😅

No I just forgot to add padding argument in one test 😅.
Everything is working now, I think we are ready for merge

authors: vcarlier yguclu

repo: pyccel/psydac


text:
Navbar

@uranusjr 語言列那邊麻煩你幫忙移一下，先把 form 註解起來了，在 nav_base.html 這個檔案。
p.s. 現在似乎到處都有 base.html，你要改名也可以。（我本來是想說這樣比較好搜尋）

Current coverage is 92.20%

Merging #87 into master will decrease coverage by -0.70% as of a29e8a0

@@            master    #87   diff @@
=====================================
  Files           28     28
  Stmts          860    860
  Branches         0      0
  Methods          0      0
=====================================
- Hit            799    793     -6
  Partial          0      0
- Missed          61     67     +6

Review entire Coverage Diff as of a29e8a0

Powered by Codecov. Updated on successful CI builds.

close #79

Please review

Sure!

authors: ccwang002 codecov-io flywindy


text:
pendulum_dt.Date can resolve to datetime.date

IIRC, the intent is the annotating a field with pendulum_dt.Date will guarantee that the field will contain a pendulum.Date object (or in this case at least a subclass of it), so callers can be confident that pendulum's methods will be available on it. Currently (as of the recent release of v2.8.0, but also prior to that), that is not the behavior:
In [1]: from pydantic_extra_types.pendulum_dt import Date; from pydantic import TypeAdapter; adapter = TypeAdapter(Date)

In [2]: adapter.validate_python("1990-07-02T00:00:00.000+0000")
Out[2]: datetime.date(1990, 7, 2)

In [3]: adapter.validate_python("1990-07-02")
Out[3]: datetime.date(1990, 7, 2)

As you can see above, a standard datetime.date object is returned.

that is correct asumption... i am adding fix and checks

fixed here

repo: pydantic/pydantic-extra-types


text:
Debian/ubuntu packages for v2

Is pydantic v2 released/maintained as a linux Debian/Ubuntu package?

I don't think so right now, I think pydantic V2 will be added to Ubuntu main soon.

Thanks @samuelcolvin for the feedback! Do you have any timeline for that? We are looking for it https://github.com/geopython/pygeoapi/pull/1366 once our dependency policy for pygeoapi release will be in place. Please let me know if it requires sponsoring

@francbartoli,
We don't yet have a concrete timeline for this change, but will update this issue when we get more info 👍

Update on this - you can track the addition of V1 to Ubuntu here: https://bugs.launchpad.net/ubuntu/+source/pydantic/+bug/2001699.
We haven't yet been notified of a timeline for when V2 will be added. Closing this issue, as tracking should be done via the above linked issue 👍

pydantic 2.8.2 is now in Debian testing (will be Debian 13) and Ubuntu oracular (will be Ubuntu 24.10).  I just uploaded 2.9.1 to Debian unstable to bring us completely up to date; it's likely too late for that to get into Ubuntu 24.10, but I'm sure it'll be in 25.04.

authors: cjwatson francbartoli samuelcolvin sydney-runkle

repo: pydantic/pydantic


text:
DEPR: warnings from style deprecation only in PY3

https://travis-ci.org/pydata/pandas/jobs/108709963
S.......S.S........................................................................./home/travis/build/pydata/pandas/pandas/core/config.py:219: FutureWarning:
mpl_style had been deprecated and will be removed in a future version.
Use `matplotlib.pyplot.style.use` instead.
  return self.__func__(*args, **kwds)

cc @TomAugspurger
prob should bump the stacklevel as well

this fixes: https://github.com/jreback/pandas/commit/ad78ce21fe0d04952eb8919cd65566d14c96b779

repo: pydata/pandas


text:
FloatingPointError on ewm().std()

I'm not sure if this is a bug, but I'm pretty sure I shouldn't be seeing these warnings. Any clarification would be a real help, as I need to ensure the accuracy of the calculations in all circumstances (including situations where the deviation is effectively zero)
Paste-ready code:
import traceback
import warnings
import sys
import pandas as pd
import numpy as np
np.seterr(all='raise')
def warn_with_traceback(message, category, filename, lineno, file=None, line=None):
    traceback.print_stack()
    log = file if hasattr(file,'write') else sys.stderr
    log.write(warnings.formatwarning(message, category, filename, lineno, line))

warnings.showwarning = warn_with_traceback

pd.Series(np.random.randn(50)).pct_change().ewm(span=35, min_periods=35).std()

Expected output:
pd.Series of exponentially weighted standard deviation.
output of pd.show_versions()
INSTALLED VERSIONS
commit: None
python: 3.5.1.final.0
python-bits: 64
OS: Linux
OS-release: 4.2.0-34-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
pandas: 0.18.1
nose: 1.3.7
pip: 8.1.2
setuptools: 23.0.0
Cython: 0.24
numpy: 1.10.4
scipy: 0.17.1
statsmodels: 0.6.1
xarray: None
IPython: 4.2.0
sphinx: 1.4.1
patsy: 0.4.1
dateutil: 2.5.3
pytz: 2016.4
blosc: None
bottleneck: 1.0.0
tables: 3.2.2
numexpr: 2.5.2
matplotlib: 1.5.1
openpyxl: 2.3.2
xlrd: 1.0.0
xlwt: 1.1.2
xlsxwriter: 0.9.2
lxml: 3.6.0
bs4: 4.4.0
html5lib: 0.999
httplib2: None
apiclient: None
sqlalchemy: 1.0.13
pymysql: None
psycopg2: None
jinja2: 2.8
boto: None
pandas_datareader: 0.2.1

you are overriding pandas by doing this: np.seterr(all='raise')
pandas by definition will catch things like operating on nans and do the right thing. see #13109
so in theory a user could eventually change this. But to be honest its not very useful.
In [3]: np.random.seed(1234)

In [4]: pd.options.display.max_rows=8

In [5]: pd.Series(np.random.randn(50)).pct_change().ewm(span=35, min_periods=35).std()
Out[5]:
0           NaN
1           NaN
2           NaN
3           NaN
        ...
46    27.070401
47    26.253511
48    27.533031
49    26.703128
dtype: float64

Thanks, that's useful insight. I just wanted to make sure I wasn't seeing something unexpected.

One further question. The reason I was investigating this is because this warning is still getting thrown out when using the ThreadPoolExecutor to do this calculation (concurrent.futures), as:
/projects/anaconda3/lib/python3.5/site-packages/pandas/core/ops.py:716: RuntimeWarning: invalid value encountered in less
  result = getattr(x, name)(y)

I do believe the numbers are coming out as expected (I haven't checked meticulously), but did not want to suppress this warning without at least checking where it's coming from.


text:
DOC: Updated drop_duplicates doc

Closes #2825.
CC @patricktokeeffe @bilderbuchi

nice, thanks!

thanks @sinhrks

authors: bilderbuchi jreback sinhrks


text:
Fontawesome 6 icons do not work

Despite the documentation stating otherwise (maybe only some) Fontawesome 6 icons do not work and show a missing icon symbol.
Specifically, this symbol did not work for me. It is available in Fontawesome 6, but not Fontawesome 5.
This was the configuration I used:
html_theme_options = {
    "icon_links": [
        {
            "name": "News",
            "url": "https://biotite.bsky.social",
            "icon": "fa-brands fa-bluesky",
            "type": "fontawesome",
        }
   ]
}

I am using pydata-sphinx-theme version 0.15.2

The linked page says "6.5.2" in small print below the icon. The theme currently has v 6.5.1:
https://github.com/pydata/pydata-sphinx-theme/blob/733d9f3264020c8a5bd3dde38f3ee3e5cdb2979a/package.json#L22
So I think we just need to update that dependency

authors: drammock padix-key

repo: pydata/pydata-sphinx-theme


text:
{full,zeros,ones}_like should return objects with the same type as the input object

What happened?
I'm getting issues using mypy with the changes to the typing of {full,zeros,ones}_like introduced in https://github.com/pydata/xarray/pull/6611.
cc: @headtr1ck
What did you expect to happen?
I think the object returned should be of the same type as the input object rather than Union[Dataset, DataArray]. For example, I don't think running mypy on the code below should return an error.
Minimal Complete Verifiable Example
import xarray as xr

def test_zeros_like(da: xr.DataArray) -> xr.DataArray:
    return xr.zeros_like(da)

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output
test.py:4: error: Incompatible return value type (got "Union[Dataset, DataArray]", expected "DataArray")
Found 1 error in 1 file (checked 1 source file

Anything else we need to know?
mypy                      0.950           py310h6c45266_0    conda-forge
mypy_extensions           0.4.3           py310h2ec42d9_5    conda-forge

Environment

INSTALLED VERSIONS
commit: None
python: 3.10.4 | packaged by conda-forge | (main, Mar 24 2022, 17:43:32) [Clang 12.0.1 ]
python-bits: 64
OS: Darwin
OS-release: 21.5.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: None
LOCALE: (None, 'UTF-8')
libhdf5: None
libnetcdf: None
xarray: 2022.3.1.dev111+g4da7fdbd
pandas: 1.4.2
numpy: 1.22.3
scipy: 1.8.1
netCDF4: None
pydap: None
h5netcdf: None
h5py: None
Nio: None
zarr: 2.11.3
cftime: None
nc_time_axis: None
PseudoNetCDF: None
rasterio: 1.2.10
cfgrib: None
iris: None
bottleneck: None
dask: 2022.05.0
distributed: 2022.5.0
matplotlib: None
cartopy: None
seaborn: None
numbagg: None
fsspec: 2022.5.0
cupy: None
pint: None
sparse: None
flox: None
numpy_groupies: None
setuptools: 62.3.2
pip: 22.1.1
conda: None
pytest: 7.1.2
IPython: None
sphinx: None

Nice find.
Was a bug in the overloads, the PR should fix it.
If the bound TypeVar support of mypy would not be so buggy we could move to a simpler solution that is less error prone...

repo: pydata/xarray


text:
Unable to use Xarray to work on RCM Dataset with xsar and safe_rcm by umr-lops

What happened?
UMR-LOPS has introduced XSAR a library to work with RCM dataset.
when working with the following code
import xsar
import geoviews as gv
import holoviews as hv
import geoviews.feature as gf
hv.extension('bokeh')
path = xsar.get_test_file('RCM1_OK1050603_PK1050605_1_SC50MB_20200214_115905_HH_HV_Z010')
meta = xsar.RcmMeta(name=path)
meta.dt

I am encountering the following error
ValueError                                Traceback (most recent call last)
<ipython-input-5-3d49b63ff406> in <cell line: 2>()
      1 #rs2meta = xsar.RadarSat2Meta(name=path)
----> 2 meta = xsar.RcmMeta(name=path)

14 frames
/usr/local/lib/python3.10/dist-packages/xsar/utils.py in wrapper(*args, **kwargs)
     93             startrss = process.memory_info().rss
     94         starttime = time.time()
---> 95         result = f(*args, **kwargs)
     96         endtime = time.time()
     97         if mem_monitor:

/usr/local/lib/python3.10/dist-packages/xsar/rcm_meta.py in __init__(self, name)
     32             self.dt = api.open_rcm(name.split(':')[1])
     33         else:
---> 34             self.dt = api.open_rcm(name)
     35         if not name.startswith('RCM_DS:'):
     36             name = 'RCM_DS:%s:' % name

/usr/local/lib/python3.10/dist-packages/safe_rcm/api.py in open_rcm(url, backend_kwargs, manifest_ignores, **dataset_kwargs)
     95         )
     96
---> 97     tree = read_product(mapper, "metadata/product.xml")
     98
     99     calibration_root = "metadata/calibration"

/usr/local/lib/python3.10/dist-packages/safe_rcm/product/reader.py in read_product(mapper, product_path)
    272     }
    273
--> 274     converted = valmap(
    275         lambda x: execute(**x)(decoded),
    276         layout,

/usr/local/lib/python3.10/dist-packages/toolz/dicttoolz.py in valmap(func, d, factory)
     83     """
     84     rv = factory()
---> 85     rv.update(zip(d.keys(), map(func, d.values())))
     86     return rv
     87

/usr/local/lib/python3.10/dist-packages/safe_rcm/product/reader.py in <lambda>(x)
    273
    274     converted = valmap(
--> 275         lambda x: execute(**x)(decoded),
    276         layout,
    277     )

/usr/local/lib/python3.10/dist-packages/toolz/functoolz.py in __call__(self, *args, **kwargs)
    302     def __call__(self, *args, **kwargs):
    303         try:
--> 304             return self._partial(*args, **kwargs)
    305         except TypeError as exc:
    306             if self._should_curry(args, kwargs, exc):

/usr/local/lib/python3.10/dist-packages/safe_rcm/product/reader.py in execute(mapping, f, path)
     29     subset = query(path, mapping)
     30
---> 31     return compose_left(f, attach_path(path=path))(subset)
     32
     33

/usr/local/lib/python3.10/dist-packages/toolz/functoolz.py in __call__(self, *args, **kwargs)
    485
    486     def __call__(self, *args, **kwargs):
--> 487         ret = self.first(*args, **kwargs)
    488         for f in self.funcs:
    489             ret = f(ret)

/usr/local/lib/python3.10/dist-packages/toolz/functoolz.py in __call__(self, *args, **kwargs)
    487         ret = self.first(*args, **kwargs)
    488         for f in self.funcs:
--> 489             ret = f(ret)
    490         return ret
    491

/usr/local/lib/python3.10/dist-packages/safe_rcm/product/reader.py in <lambda>(obj)
    126                 ),
    127                 lambda obj: obj.set_index({"stacked": ["pole", "pulse"]}),
--> 128                 lambda obj: obj.unstack("stacked"),
    129             ),
    130         },

/usr/local/lib/python3.10/dist-packages/xarray/util/deprecation_helpers.py in inner(*args, **kwargs)
    113                 return func(*args[:-n_extra_args], **kwargs)
    114
--> 115             return func(*args, **kwargs)
    116
    117         return inner

/usr/local/lib/python3.10/dist-packages/xarray/core/dataset.py in unstack(self, dim, fill_value, sparse)
   5576                 )
   5577             else:
-> 5578                 result = result._unstack_once(d, stacked_indexes[d], fill_value, sparse)
   5579         return result
   5580

/usr/local/lib/python3.10/dist-packages/xarray/core/dataset.py in _unstack_once(self, dim, index_and_vars, fill_value, sparse)
   5395         indexes = {k: v for k, v in self._indexes.items() if k != dim}
   5396
-> 5397         new_indexes, clean_index = index.unstack()
   5398         indexes.update(new_indexes)
   5399

/usr/local/lib/python3.10/dist-packages/xarray/core/indexes.py in unstack(self)
   1019
   1020         if not clean_index.is_unique:
-> 1021             raise ValueError(
   1022                 "Cannot unstack MultiIndex containing duplicates. Make sure entries "
   1023                 f"are unique, e.g., by  calling ``.drop_duplicates('{self.dim}')``, "

ValueError: Cannot unstack MultiIndex containing duplicates. Make sure entries are unique, e.g., by  calling ``.drop_duplicates('stacked')``, before unstacking.

As you can see from the last sections in the trace,the issue is with xarray/dataset.py when we unstack the dataframe.
Any ideas why this is happening.The issue doesn't occur with radarsat 2 or any other dataset.So is this an xarray problem or should I raise the issue at umr-lops?
What did you expect to happen?
the error shouldn't be there,and I should be able to view the dataframe. as shown in below link
https://cyclobs.ifremer.fr/static/sarwing_datarmor/xsar/examples/rcm.html
Minimal Complete Verifiable Example
import xsar
import geoviews as gv
import holoviews as hv
import geoviews.feature as gf
hv.extension('bokeh')
path = xsar.get_test_file('RCM1_OK1050603_PK1050605_1_SC50MB_20200214_115905_HH_HV_Z010')
meta = xsar.RcmMeta(name=path)
meta.dt

MVCE confirmation

[ ] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.
[X] Recent environment — the issue occurs with the latest version of xarray and its dependencies.

Relevant log output
No response
Anything else we need to know?
No response
Environment

commit: None
python: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
python-bits: 64
OS: Linux
OS-release: 6.1.58+
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: en_US.UTF-8
LANG: en_US.UTF-8
LOCALE: ('en_US', 'UTF-8')
libhdf5: 1.12.2
libnetcdf: None
xarray: 2023.7.0
pandas: 1.5.3
numpy: 1.25.2
scipy: 1.11.4
netCDF4: None
pydap: None
h5netcdf: 1.3.0
h5py: 3.9.0
Nio: None
zarr: None
cftime: None
nc_time_axis: None
PseudoNetCDF: None
iris: None
bottleneck: None
dask: 2023.8.1
distributed: 2023.8.1
matplotlib: 3.7.1
cartopy: None
seaborn: 0.13.1
numbagg: None
fsspec: 2023.6.0
cupy: None
pint: None
sparse: None
flox: None
numpy_groupies: None
setuptools: 67.7.2
pip: 23.1.2
conda: None
pytest: 7.4.4
mypy: None
IPython: 7.34.0
sphinx: 5.0.2
/usr/local/lib/python3.10/dist-packages/_distutils_hack/init.py:33: UserWarning: Setuptools is replacing distutils.
warnings.warn("Setuptools is replacing distutils.")

is this the same error as umr-lops/xarray-safe-rcm#75? If so, let's discuss that there.

@keewis yes it's the same issue,I was able to trace the error.But I am not sure if it's because of xarray or some other library you are using ,which is causing this error.

Thanks for your report. It's due to a change in xarray but has to be fixed downstream - see https://github.com/umr-lops/xarray-safe-rcm/issues/75#issuecomment-1953510785. I'll close here for now.

authors: keewis mathause sparshgarg23


text:
Compress PNG files

optipng -o9

Did this cause any issues or is this simply recommended?

Did this cause any issues or is this simply recommended?

I think this is connected with reducing carbon footprint. Some mor ideas: https://sustainablewebdesign.org/