OSAD Integration

Rework of the RPC deploy to consume OSAD as a sub-repository.
Introduces an RPC deploy script.
RPC Upgrade concerns excluded from this PR to break down the size of the reviews.

we might want one more commit changing the pin of osad to 11.0.1

other then that :+1:
upgrade will be in another pr

updated osad to current head of master (not 11.x), we can get the kilo branch of extras set to the appropriate point in osad when we get there.

Merge conflict

no conflict on command line
$ git status
On branch master
nothing to commit, working directory clean
$ git checkout -b merger
Switched to a new branch 'merger'
$ git merge --no-ff osad-integration
Auto-merging rpcd/playbooks/roles/rpc_maas/tasks/raxmon_agent_install.yml
Auto-merging rpcd/playbooks/roles/rpc_maas/defaults/main.yml
Auto-merging rpcd/playbooks/group_vars/all.yml
Auto-merging rpcd/playbooks/ansible.cfg
Auto-merging rpcd/etc/openstack_deploy/user_extras_variables.yml
Merge made by the 'recursive' strategy.
 .gitmodules                                                                            |   3 +++
 README.md                                                                              |  70 +++++++++++++++-----------------------------------------
 os-ansible-deployment                                                                  |   1 +
 {etc => rpcd/etc}/openstack_deploy/env.d/elasticsearch.yml                             |   0
 {etc => rpcd/etc}/openstack_deploy/env.d/kibana.yml                                    |   0
 {etc => rpcd/etc}/openstack_deploy/env.d/logstash.yml                                  |   0
 rpcd/etc/openstack_deploy/user_apt_packages.yml                                        |  11 +++++++++
 {etc => rpcd/etc}/openstack_deploy/user_extras_secrets.yml                             |   0
 {etc => rpcd/etc}/openstack_deploy/user_extras_variables.yml                           |  26 ++-------------------
 {playbooks => rpcd/playbooks}/ansible.cfg                                              |   8 +++----
 {playbooks => rpcd/playbooks}/elasticsearch.yml                                        |   0
 {playbooks => rpcd/playbooks}/group_vars/all.yml                                       |   2 +-
 {playbooks => rpcd/playbooks}/haproxy.yml                                              |   0
 {playbooks => rpcd/playbooks}/horizon_extensions.yml                                   |   0
 {playbooks => rpcd/playbooks}/kibana.yml                                               |   0
 {playbooks => rpcd/playbooks}/logstash.yml                                             |   0
 {playbooks/roles/logstash => rpcd/playbooks/roles/elasticsearch}/CONTRIBUTING.rst      |   0
 {playbooks/roles/rpc_support => rpcd/playbooks/roles/elasticsearch}/LICENSE            |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/README.rst                           |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/defaults/main.yml                    |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/handlers/main.yml                    |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/meta/main.yml                        |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/tasks/elasticsearch_install.yml      |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/tasks/elasticsearch_post_install.yml |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/tasks/elasticsearch_pre_install.yml  |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/tasks/main.yml                       |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/templates/elasticsearch              |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/templates/elasticsearch.yml          |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/templates/logging.yml                |   0
 {playbooks => rpcd/playbooks}/roles/elasticsearch/templates/mapping.sh.j2              |   0
 {playbooks/roles/kibana => rpcd/playbooks/roles/haproxy_rpc}/CONTRIBUTING.rst          |   0
 {playbooks/roles/rpc_maas => rpcd/playbooks/roles/haproxy_rpc}/LICENSE                 |   0
 {playbooks => rpcd/playbooks}/roles/haproxy_rpc/README.rst                             |   0
 rpcd/playbooks/roles/haproxy_rpc/defaults/main.yml                                     |  14 ++++++++++++
 {playbooks => rpcd/playbooks}/roles/haproxy_rpc/handlers/main.yml                      |   0
 {playbooks => rpcd/playbooks}/roles/haproxy_rpc/meta/main.yml                          |   0
 {playbooks => rpcd/playbooks}/roles/haproxy_rpc/tasks/main.yml                         |   0
 {playbooks => rpcd/playbooks}/roles/haproxy_rpc/templates/elasticsearch.j2             |   0
 {playbooks => rpcd/playbooks}/roles/haproxy_rpc/templates/kibana_ssl.j2                |   0
 {playbooks => rpcd/playbooks}/roles/horizon_extensions/defaults/main.yml               |   0
 {playbooks => rpcd/playbooks}/roles/horizon_extensions/files/favicon.ico               | Bin
 {playbooks => rpcd/playbooks}/roles/horizon_extensions/files/logo-splash.png           | Bin
 {playbooks => rpcd/playbooks}/roles/horizon_extensions/files/logo.png                  | Bin
 {playbooks => rpcd/playbooks}/roles/horizon_extensions/handlers/main.yml               |   0
 {playbooks => rpcd/playbooks}/roles/horizon_extensions/meta/main.yml                   |   0
 {playbooks => rpcd/playbooks}/roles/horizon_extensions/tasks/main.yml                  |   0
 {playbooks => rpcd/playbooks}/roles/horizon_extensions/templates/_50_rackspace.py      |   0
 {playbooks => rpcd/playbooks}/roles/horizon_extensions/templates/solutions.yaml        |   0
 {playbooks/roles/haproxy_rpc => rpcd/playbooks/roles/kibana}/CONTRIBUTING.rst          |   0
 {playbooks/roles/logstash => rpcd/playbooks/roles/kibana}/LICENSE                      |   0
 {playbooks => rpcd/playbooks}/roles/kibana/README.rst                                  |   0
 {playbooks => rpcd/playbooks}/roles/kibana/defaults/main.yml                           |   0
 {playbooks => rpcd/playbooks}/roles/kibana/handlers/main.yml                           |   0
 {playbooks => rpcd/playbooks}/roles/kibana/meta/main.yml                               |   0
 {playbooks => rpcd/playbooks}/roles/kibana/tasks/kibana_install.yml                    |   0
 {playbooks => rpcd/playbooks}/roles/kibana/tasks/kibana_post_install.yml               |   0
 {playbooks => rpcd/playbooks}/roles/kibana/tasks/kibana_pre_install.yml                |   0
 {playbooks => rpcd/playbooks}/roles/kibana/tasks/main.yml                              |   0
 {playbooks => rpcd/playbooks}/roles/kibana/templates/000-kibana.conf                   |   0
 {playbooks => rpcd/playbooks}/roles/kibana/templates/Event-Dashboard.json              |   0
 {playbooks => rpcd/playbooks}/roles/kibana/templates/config.js                         |   0
 {playbooks => rpcd/playbooks}/roles/kibana/templates/ports.conf                        |   0
 {playbooks/roles/elasticsearch => rpcd/playbooks/roles/logstash}/CONTRIBUTING.rst      |   0
 {playbooks/roles/kibana => rpcd/playbooks/roles/logstash}/LICENSE                      |   0
 {playbooks => rpcd/playbooks}/roles/logstash/README.rst                                |   0
 {playbooks => rpcd/playbooks}/roles/logstash/defaults/main.yml                         |   0
 {playbooks => rpcd/playbooks}/roles/logstash/handlers/main.yml                         |   0
 {playbooks => rpcd/playbooks}/roles/logstash/meta/main.yml                             |   0
 {playbooks => rpcd/playbooks}/roles/logstash/tasks/logstash_install.yml                |   0
 {playbooks => rpcd/playbooks}/roles/logstash/tasks/logstash_post_install.yml           |   0
 {playbooks => rpcd/playbooks}/roles/logstash/tasks/logstash_pre_install.yml            |   0
 {playbooks => rpcd/playbooks}/roles/logstash/tasks/logstash_web_disable.yml            |   0
 {playbooks => rpcd/playbooks}/roles/logstash/tasks/main.yml                            |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/01-input.conf                   |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/02-general.conf                 |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/03-openstack.conf               |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/04-routes.conf                  |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/05-cinder.conf                  |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/06-nova.conf                    |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/07-sqlalchemy.conf              |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/08-swift.conf                   |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/09-apache.conf                  |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/10-mysql.conf                   |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/11-neutron.conf                 |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/98-mutate.conf                  |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/99-output.conf                  |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/extras                          |   0
 {playbooks => rpcd/playbooks}/roles/logstash/templates/logstash                        |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/CONTRIBUTING.rst                          |   0
 {playbooks/roles/haproxy_rpc => rpcd/playbooks/roles/rpc_maas}/LICENSE                 |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/README.rst                                |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/defaults/main.yml                         |   3 +--
 {playbooks => rpcd/playbooks}/roles/rpc_maas/handlers/main.yml                         |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/meta/main.yml                             |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/cdm.yml                             |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/cdm_setup.yml                       |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/create_my_cnf.yml                   |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/dell.yml                            |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/filesystem_autosetup.yml            |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/filesystem_setup.yml                |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/hardware_setup.yml                  |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/hp.yml                              |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/keystone_user.yml                   |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/local.yml                           |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/local_setup.yml                     |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/main.yml                            |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/network.yml                         |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/package_install.yml                 |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/raxmon_agent_install.yml            |  11 +++++----
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/raxmon_cli_config.yml               |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/remote.yml                          |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/remote_setup.yml                    |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/repo_setup.yml                      |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/ssl_check.yml                       |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/swift.yml                           |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/templates/client.my.cnf.j2                |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/templates/openrc                          |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/templates/rackspace-monitoring-agent.cfg  |   0
 {playbooks => rpcd/playbooks}/roles/rpc_maas/templates/raxrc.j2                        |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/CONTRIBUTING.rst                       |   0
 {playbooks/roles/elasticsearch => rpcd/playbooks/roles/rpc_support}/LICENSE            |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/README.rst                             |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/defaults/main.yml                      |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/handlers/main.yml                      |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/meta/main.yml                          |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/bashrc.yml                       |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/distribute_auth_key.yml          |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/histformat.yml                   |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/holland_config.yml               |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/holland_preinstall.yml           |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/host_kernel_modules.yml          |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/host_kernel_tuning.yml           |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/main.yml                         |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/motd.yml                         |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/pccommon_get.yml                 |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/retrieve_auth_key.yml            |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/rpc_release.yml                  |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/spice_console.yml                |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/support_key_pair.yml             |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/support_preinstall.yml           |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/support_sec_group.yml            |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/templates/20-openstack.j2              |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/templates/histformat.sh.j2             |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/templates/holland-xtrabackup.conf.j2   |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/templates/holland.conf.j2              |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/templates/rpc-release.j2               |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/templates/spice.css.j2                 |   0
 {playbooks => rpcd/playbooks}/roles/rpc_support/templates/spice_auto.html.j2           |   0
 {playbooks => rpcd/playbooks}/rpc-support.yml                                          |   0
 {playbooks => rpcd/playbooks}/setup-logging.yml                                        |   0
 {playbooks => rpcd/playbooks}/setup-maas.yml                                           |   0
 {playbooks => rpcd/playbooks}/site.yml                                                 |   0
 scripts/deploy.sh                                                                      |  50 ++++++++++++++++++++++++++++++++++++++++
 153 files changed, 112 insertions(+), 87 deletions(-)
 create mode 100644 .gitmodules
 create mode 160000 os-ansible-deployment
 rename {etc => rpcd/etc}/openstack_deploy/env.d/elasticsearch.yml (100%)
 rename {etc => rpcd/etc}/openstack_deploy/env.d/kibana.yml (100%)
 rename {etc => rpcd/etc}/openstack_deploy/env.d/logstash.yml (100%)
 create mode 100644 rpcd/etc/openstack_deploy/user_apt_packages.yml
 rename {etc => rpcd/etc}/openstack_deploy/user_extras_secrets.yml (100%)
 rename {etc => rpcd/etc}/openstack_deploy/user_extras_variables.yml (75%)
 rename {playbooks => rpcd/playbooks}/ansible.cfg (80%)
 rename {playbooks => rpcd/playbooks}/elasticsearch.yml (100%)
 rename {playbooks => rpcd/playbooks}/group_vars/all.yml (94%)
 rename {playbooks => rpcd/playbooks}/haproxy.yml (100%)
 rename {playbooks => rpcd/playbooks}/horizon_extensions.yml (100%)
 rename {playbooks => rpcd/playbooks}/kibana.yml (100%)
 rename {playbooks => rpcd/playbooks}/logstash.yml (100%)
 rename {playbooks/roles/logstash => rpcd/playbooks/roles/elasticsearch}/CONTRIBUTING.rst (100%)
 rename {playbooks/roles/rpc_support => rpcd/playbooks/roles/elasticsearch}/LICENSE (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/README.rst (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/defaults/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/handlers/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/meta/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/tasks/elasticsearch_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/tasks/elasticsearch_post_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/tasks/elasticsearch_pre_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/tasks/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/templates/elasticsearch (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/templates/elasticsearch.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/templates/logging.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/elasticsearch/templates/mapping.sh.j2 (100%)
 rename {playbooks/roles/kibana => rpcd/playbooks/roles/haproxy_rpc}/CONTRIBUTING.rst (100%)
 rename {playbooks/roles/rpc_maas => rpcd/playbooks/roles/haproxy_rpc}/LICENSE (100%)
 rename {playbooks => rpcd/playbooks}/roles/haproxy_rpc/README.rst (100%)
 create mode 100644 rpcd/playbooks/roles/haproxy_rpc/defaults/main.yml
 rename {playbooks => rpcd/playbooks}/roles/haproxy_rpc/handlers/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/haproxy_rpc/meta/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/haproxy_rpc/tasks/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/haproxy_rpc/templates/elasticsearch.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/haproxy_rpc/templates/kibana_ssl.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/horizon_extensions/defaults/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/horizon_extensions/files/favicon.ico (100%)
 rename {playbooks => rpcd/playbooks}/roles/horizon_extensions/files/logo-splash.png (100%)
 rename {playbooks => rpcd/playbooks}/roles/horizon_extensions/files/logo.png (100%)
 rename {playbooks => rpcd/playbooks}/roles/horizon_extensions/handlers/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/horizon_extensions/meta/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/horizon_extensions/tasks/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/horizon_extensions/templates/_50_rackspace.py (100%)
 rename {playbooks => rpcd/playbooks}/roles/horizon_extensions/templates/solutions.yaml (100%)
 rename {playbooks/roles/haproxy_rpc => rpcd/playbooks/roles/kibana}/CONTRIBUTING.rst (100%)
 rename {playbooks/roles/logstash => rpcd/playbooks/roles/kibana}/LICENSE (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/README.rst (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/defaults/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/handlers/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/meta/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/tasks/kibana_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/tasks/kibana_post_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/tasks/kibana_pre_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/tasks/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/templates/000-kibana.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/templates/Event-Dashboard.json (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/templates/config.js (100%)
 rename {playbooks => rpcd/playbooks}/roles/kibana/templates/ports.conf (100%)
 rename {playbooks/roles/elasticsearch => rpcd/playbooks/roles/logstash}/CONTRIBUTING.rst (100%)
 rename {playbooks/roles/kibana => rpcd/playbooks/roles/logstash}/LICENSE (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/README.rst (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/defaults/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/handlers/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/meta/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/tasks/logstash_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/tasks/logstash_post_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/tasks/logstash_pre_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/tasks/logstash_web_disable.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/tasks/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/01-input.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/02-general.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/03-openstack.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/04-routes.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/05-cinder.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/06-nova.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/07-sqlalchemy.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/08-swift.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/09-apache.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/10-mysql.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/11-neutron.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/98-mutate.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/99-output.conf (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/extras (100%)
 rename {playbooks => rpcd/playbooks}/roles/logstash/templates/logstash (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/CONTRIBUTING.rst (100%)
 rename {playbooks/roles/haproxy_rpc => rpcd/playbooks/roles/rpc_maas}/LICENSE (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/README.rst (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/defaults/main.yml (98%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/handlers/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/meta/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/cdm.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/cdm_setup.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/create_my_cnf.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/dell.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/filesystem_autosetup.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/filesystem_setup.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/hardware_setup.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/hp.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/keystone_user.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/local.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/local_setup.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/network.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/package_install.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/raxmon_agent_install.yml (92%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/raxmon_cli_config.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/remote.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/remote_setup.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/repo_setup.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/ssl_check.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/tasks/swift.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/templates/client.my.cnf.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/templates/openrc (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/templates/rackspace-monitoring-agent.cfg (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_maas/templates/raxrc.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/CONTRIBUTING.rst (100%)
 rename {playbooks/roles/elasticsearch => rpcd/playbooks/roles/rpc_support}/LICENSE (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/README.rst (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/defaults/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/handlers/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/meta/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/bashrc.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/distribute_auth_key.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/histformat.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/holland_config.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/holland_preinstall.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/host_kernel_modules.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/host_kernel_tuning.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/main.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/motd.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/pccommon_get.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/retrieve_auth_key.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/rpc_release.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/spice_console.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/support_key_pair.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/support_preinstall.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/tasks/support_sec_group.yml (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/templates/20-openstack.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/templates/histformat.sh.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/templates/holland-xtrabackup.conf.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/templates/holland.conf.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/templates/rpc-release.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/templates/spice.css.j2 (100%)
 rename {playbooks => rpcd/playbooks}/roles/rpc_support/templates/spice_auto.html.j2 (100%)
 rename {playbooks => rpcd/playbooks}/rpc-support.yml (100%)
 rename {playbooks => rpcd/playbooks}/setup-logging.yml (100%)
 rename {playbooks => rpcd/playbooks}/setup-maas.yml (100%)
 rename {playbooks => rpcd/playbooks}/site.yml (100%)
 create mode 100755 scripts/deploy.sh
$

:+1:

I'm +1. However, I don't have much knowledge of the logging filters.

if logging isn't like it appears in master right now, it's probably wrong... time to make a hit list of issues.

gonna open a new PR since this has just become a mess


DTSAM-163 Test PR for broken CCD integration but with FTA skip

JIRA link (if applicable)
DTSAM-163 "RAS FTAs may fail if CCD Data-Store is unvailable. Add EV flag option to disable those FTAs when needed."
Change description
This is 2nd of 2 test PRs for #2170.  Scenario is: broken CCD integration but with FTA skip.
(see also #2171 for 1st scenario)
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

This is a test PR and it can now be closed as primary PR has been released.


Cycle Unified adapt singleton?

I've looked how cycle unified implements compatibility with other libraries using singleton adapt, setAdapt and I think it is a really arguable idea. I understand that the idea behind this is to simplify things for driver developers, in this case, it is done by imposing bad design and architecture in general.
I think adapt should go as before the second argument to a driver as runSA before, without introducing this weird global dependency:
import {adapt} from '@cycle/run/lib/adapt';

What was the reasoning behind the decision over using adapt as an argument to a driver? Yes it may make driver a code a bit trickier but at least it would be correct won't introduce any potential conflicts.

You should have risen this concern when we were discussing #425 (it lasted months) or while Unified was in release candidate.
The reason we did it like that is we want to optimize Cycle.js for people building apps with Cycle, not for people maintaining Cycle. In a different example, one could argue that OOP is bad design and architecture, but we use OOP all over the place internally in Cycle.js, because we're not optimizing the framework code in the same way we are optimizing userland code.

You should have risen this concern when we were discussing #425 (it lasted months) or while Unified was in release candidate.

The last couple of months I had no time to track how unified is implemented. I'm not here to just criticize current solution but try to justify it or to think about better approach.

In a different example, one could argue that OOP is bad design and architecture, but we use OOP all over the place internally in Cycle.js, because we're not optimizing the framework code in the same way we are optimizing userland code.

This was discussed before, this is the matter of internal library design, it is going to cause any potential conflicts, and OOP for this stuff is a better choice anyway. Singleton pattern itself is not safe from being a source of external conflicts and always looks like a clumsy hack so it should be avoided if possible (sometimes it is really not possible, that it is ok to use it).

The reason we did it like that is we want to optimize Cycle.js for people building apps with Cycle, not for people maintaining Cycle.

People who developing drivers or other components for others as well should be fully aware of the architecture and understand what they are doing. And such code should be safe. Introducing this singleton imposes some assumptions, that should be considered too.
For example, from docs:

Note that adapt is always imported from as @cycle/run/lib/adapt, not from @cycle/rxjs-run/lib/adapt nor @cycle/most-run/lib/adapt. Before returning a single-stream source from the driver, make sure to call adapt:

So simplification is arguable, but using bad pattern is quite obvious.
Another thing too:

It is usually better to write drivers in xstream, since you don’t need to convert the sink, and given xstream’s tiny size as a dependency.

Even if sink comming to driver was not always xstream it would not be a big deal of converting it with xs.fromObservable (for xstream based drivers), so this thing is too arguable simplification. And the whole core could not depend on xstream, in my view it would be just more clean and abstract design of cycle's run core. And still would allow to position xstream as first class citizen while doing the same thing for other stream libs.
I'm not saying that it is all critical just a food for thoughts about better design.

(Labeled discussion because there are no suggestions in this thread yet)
something-to-xstream conversion is easy to handle, you just need to do xs.from(something).
xstream-to-something conversion is the job of adapt, and it's needed:

In (xstream-based) drivers when returning a source stream
In @cycle/run to convert sink proxies when passing them to non-xstream-based drivers

setAdapt is the only mutation of the singleton, and it's called once, when @cycle/something-run is imported.
The only case so far where mutation of the singleton expresses itself is when you have a test case for a driver which tests the same driver using multiple different @cycle/something-run, which is rare. That is the only real problem that happens due to the singleton. Ugliness is not a problem, it's an aesthetic preference. We wanted adapt to be available in the global context without worrying about passing arguments around. And that's not a problem at all, what makes it a singleton is not adapt (it's just a function, like makeDOMDriver is), what makes it a singleton is setAdapt.
This singleton-based solution as opposed to passing adapters as arguments is an improvement for code maintenance both in Cycle.js code and driver code. Remember that with adapters we had to do myDriver.streamAdapter = XStreamAdapter; which is also arguably weird.
The important thing is that the new version removes adapters and base, making it easier for driver authors and Cycle.js maintainers, and that was only possible because:

xstream is the engine everywhere
ES Observable interop for conversion something-to-xstream
adapt for conversion xstream-to-something

If this discussion is all about "setAdapt is mutable and this mutability can theoretically bring some problem in some corner case", it's not worth doing a re-architecture at this stage where Unified is already out, and the real consequences of the mutability are already known and rare. We have many more important issues to work on.

Ok, I understand your point. The thing is that there is a strict limitation: one stream library for run function per runtime environment. Other cases are not officially supported. (this may be mentioned in docs explicitly).


swipe layout programmatically

How can I swipe layout programmatically?

Open
swipeLayout.open(true);
Close
swipeLayout.close(true);
true to swipe animation
false to disabled animation

it works well, thanks.

Thanks @afiqiqmal .

@daimajia : How can we swipe programmatically with a specific leftOffset value?

@harishvishwakarma did you find any solution for that?


Google Analytics GA4

I'm using Google Analytics for the website using GA4 id starting with G-xxxxxxxx, but in my account it is not logging anything and Google Analytics not working. Can you solve this please?

I was able to get it to work by using the package nextjs-google-analytics.
// file: components/analytics/index.tsx

/* eslint-disable @typescript-eslint/no-explicit-any */
import Plausible from './Plausible';
import SimpleAnalytics from './SimpleAnalytics';
import Umami from './Umami';
import siteMetadata from '@/data/siteMetadata';
import { GoogleAnalytics } from 'nextjs-google-analytics';

declare global {
  interface Window {
    gtag?: (...args: any[]) => void;
    plausible?: (...args: any[]) => void;
    sa_event?: (...args: any[]) => void;
  }
}

const isProduction = process.env.NODE_ENV === 'production';

const Analytics = () => {
  return (
    <>
      {isProduction && (
        <>
          {siteMetadata.analytics.plausibleDataDomain && <Plausible />}
          {siteMetadata.analytics.simpleAnalytics && <SimpleAnalytics />}
          {siteMetadata.analytics.umamiWebsiteId && <Umami />}
          {siteMetadata.analytics.googleAnalyticsId && (
            <GoogleAnalytics
              trackPageViews
              gaMeasurementId={siteMetadata.analytics.googleAnalyticsId}
            />
          )}
        </>
      )}
    </>
  );
};

export default Analytics;

I just checked any verified that the script works for GA4. Have you add https://*.googletagmanager.com to the CSP as specified in https://developers.google.com/tag-platform/tag-manager/web/csp? Otherwise, it would be blocked.

Thanks guys it worked

Thank for your sharing, @PaulMest @timlrx!
Do you the have a javascript of your typescript code snippet? I'm facing an issue with the window object
Thanks

You can just remove the declare block entirely. Everything else should work just fine.
// file: components/analytics/index.js

import Plausible from './Plausible';
import SimpleAnalytics from './SimpleAnalytics';
import Umami from './Umami';
import siteMetadata from '@/data/siteMetadata';
import { GoogleAnalytics } from 'nextjs-google-analytics';

const isProduction = process.env.NODE_ENV === 'production';

const Analytics = () => {
  return (
    <>
      {isProduction && (
        <>
          {siteMetadata.analytics.plausibleDataDomain && <Plausible />}
          {siteMetadata.analytics.simpleAnalytics && <SimpleAnalytics />}
          {siteMetadata.analytics.umamiWebsiteId && <Umami />}
          {siteMetadata.analytics.googleAnalyticsId && (
            <GoogleAnalytics
              trackPageViews
              gaMeasurementId={siteMetadata.analytics.googleAnalyticsId}
            />
          )}
        </>
      )}
    </>
  );
};

export default Analytics;


Support SSH in multi-app

When running platform ssh nothing happens, whereas running platform ssh -v, I got the available methods.
That'd be great if the CLI would automatically propose the available options.

We'd need an API to find this information

see https://platformsh.atlassian.net/browse/PF-4 (internal)

Improved in v2.7.0. I'm going to amalgamate various multi-app related issues into a new follow-up.


Get a Shell to a Running Container - unable to upgrade connection: container not found ("nginx")

When I run
kubectl exec --stdin --tty shell-demo -- /bin/sh or bash
after creating the pod, I get right away

error: unable to upgrade connection: container not found ("nginx")

when I do kubectl get pods, I see pod in bad shape
NAME         READY   STATUS             RESTARTS      AGE
shell-demo   0/1     CrashLoopBackOff   5 (31s ago)   3m52s

Thanks for your help

Page: https://kubernetes.io/docs/tasks/debug/debug-application/get-shell-running-container/

/kind support

Hi @eliassal
It is working for me.
$ kubectl get pod shell-demo
NAME         READY   STATUS    RESTARTS   AGE
shell-demo   1/1     Running   0          48s

Could you please describe the pod by running kubectl describe pod shell-demo and check the events to find the error

OK, here are the steps and the outputs, it is not possible to access the pod interactively
kubectl apply -f https://k8s.io/examples/application/shell-demo.yaml
pod/shell-demo created
kubectl get pod shell-demo
NAME         READY   STATUS    RESTARTS     AGE
shell-demo   1/1     Running   1 (4s ago)   10s

 kubectl exec --stdin --tty shell-demo -- /bin/bash

error: Internal error occurred: error executing command in container: failed to exec in container: failed to create exec "6574a42960f423a29ebaa6c9e8113a88f19033f4913a55e9e59bc82480c5ae48": task 7ba47042ab56fc8005759d4007f83fe31c57eddaf056fe251120f55de8e47d38 not found: not found

I reexecuted
kubectl get pod shell-demo
get

NAME         READY   STATUS             RESTARTS      AGE
shell-demo   0/1     CrashLoopBackOff   4 (67s ago)   3m3s

Here is the output of describe
 kubectl describe pod shell-demo
Name:             shell-demo
Namespace:        default
Priority:         0
Service Account:  default
Node:             chef-u16desk/<IP_ADDRESS>
Start Time:       Wed, 19 Apr 2023 14:45:51 +0200
Labels:           <none>
Annotations:      <none>
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:  <IP_ADDRESS>
Containers:
  nginx:
    Container ID:   containerd://12e697e542a27c623b1cfb6c81e14e45782a4b091b440a712bfb412e6006574c
    Image:          nginx
    Image ID:       docker.io/library/nginx@sha256:63b44e8ddb83d5dd8020327c1f40436e37a6fffd3ef2498a6204df23be6e7e94
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 19 Apr 2023 14:49:18 +0200
      Finished:     Wed, 19 Apr 2023 14:49:20 +0200
    Ready:          False
    Restart Count:  5
    Environment:    <none>
    Mounts:
      /usr/share/nginx/html from shared-data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-wvbbr (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  shared-data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  kube-api-access-wvbbr:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  3m56s                  default-scheduler  Successfully assigned default/shell-demo to chef-u16desk
  Normal   Pulled     3m55s                  kubelet            Successfully pulled image "nginx" in 1.201357776s (1.201371576s including waiting)
  Normal   Pulled     3m49s                  kubelet            Successfully pulled image "nginx" in 1.121165211s (1.121183511s including waiting)
  Normal   Pulled     3m33s                  kubelet            Successfully pulled image "nginx" in 1.152851079s (1.152861479s including waiting)
  Normal   Pulled     3m1s                   kubelet            Successfully pulled image "nginx" in 1.121056111s (1.121065611s including waiting)
  Normal   Created    3m (x4 over 3m55s)     kubelet            Created container nginx
  Normal   Started    3m (x4 over 3m54s)     kubelet            Started container nginx
  Warning  BackOff    2m18s (x7 over 3m45s)  kubelet            Back-off restarting failed container nginx in pod shell-demo_default(6debe1d4-c051-4f0a-8dc6-6c5a54a2b0fc)
  Normal   Pulling    2m6s (x5 over 3m56s)   kubelet            Pulling image "nginx"
  Normal   Pulled     2m5s                   kubelet            Successfully pulled image "nginx" in 1.111654751s (1.111672451s including waiting)

Hi @eliassal
Do you have some other process or nginx pod using the same port 80? Because this error occurred when the port is being used by another nginx or some other process because the nginx container image is configured to run in port 80. (https://hub.docker.com/_/nginx)

I reproduced this one by deploying 2 nginx pods, I noticed that the second one gave the same error. i resolved this by deleting the first pod, by doing so second pod came into the running stage. See the below observation:
Deploy First Pod
apiVersion: v1
kind: Pod
metadata:
  name: shell-demo
spec:
  volumes:
  - name: shared-data
    emptyDir: {}
  containers:
  - name: nginx
    image: nginx
    volumeMounts:
    - name: shared-data
      mountPath: /usr/share/nginx/html
  hostNetwork: true
  dnsPolicy: Default

$ kubectl get pod
NAME         READY   STATUS    RESTARTS   AGE
shell-demo   1/1     Running   0          22s

$ kubectl exec --stdin --tty shell-demo -- /bin/bash
root@minikube-vpa-0:/#

Deploy Second pod
apiVersion: v1
kind: Pod
metadata:
  name: shell-demo-second
spec:
  volumes:
  - name: shared-data
    emptyDir: {}
  containers:
  - name: nginx
    image: nginx
    volumeMounts:
    - name: shared-data
      mountPath: /usr/share/nginx/html
  hostNetwork: true
  dnsPolicy: Default

$ kubectl get pod
NAME                READY   STATUS             RESTARTS      AGE
shell-demo          1/1     Running            0             3m32s
shell-demo-second   0/1     CrashLoopBackOff   4 (20s ago)   2m32s

$ kubectl delete pod shell-demo
pod "shell-demo" deleted

After deleting it was running
$ kubectl get pod
NAME                READY   STATUS    RESTARTS       AGE
shell-demo-second   1/1     Running   5 (104s ago)   3m56s

$ kubectl exec --stdin --tty shell-demo-second -- /bin/bash
root@minikube-vpa-0:/#

So you have to check your cluster that is there any nginx pod / process using the port 80, then you have to delete that pod or kill that process.

Also if you want to change the default port used by nginx image rather than deleting the process/pod then you have to use cmd and args to update the default value of the port.
I tried the one which is mentioned under this: https://stackoverflow.com/questions/62637067/how-to-configure-an-echo-pod-on-different-port-instead-of-port-80-in-kubernetes
Please take a look at the above stackoverflow link.

@Shubham82 , you are correct, yesterday, after adding

containerPort: 82

which did not help, I deleted

hostNetwork: true
dnsPolicy: Default

in the yml file and I was able to accedd the pod. So why/what this hostNetwork and dnsPolicy  param are there and why they are used?
Thanks

@eliassal GitHub may not be the most suitable platform to seek support assistance. You could consider posting your question on alternative forums such as the Kubernetes Slack (http://slack.k8s.io/) or the Discuss Kubernetes (https://discuss.kubernetes.io/) forum, as they may provide more comprehensive and helpful responses.

@dipesh-rawat , slack is not a good idea as you get lost very quickly and communication is not easy and cant explain an issue coirrectly, I have used https://discuss.kubernetes.io/ in the past but either responses never come or come very late.
Anyway, the link to create an issue page is found on the page itself on the mentioned page

@Shubham82, I reverted back to the original yaml file with

hostNetwork: true
dnsPolicy: Default

it does not work

So why/what this hostNetwork and dnsPolicy param are there and why they are used?

For hostNetwork and dnsPolicy please see the following k8s API page for pod: https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/

/close
This looks like a request for assistance. Nothing to fix in k8s docs.
Also, refer: https://github.com/kubernetes/kubernetes/blob/master/SUPPORT.md

hi,  I have too "unable to upgrade connection: container not found" question, and message have "killing container faild" log at node, and 1 zombie with the container，but I restart kubelet and kill zombie , pod restart  my question be gone，I want to know what causes this problem

hi, I have too "unable to upgrade connection: container not found" question, and message have "killing container faild" log at node, and 1 zombie with the container，but I restart kubelet and kill zombie , pod restart my question be gone，I want to know what causes this problem

My pod's  status is running with container


Remove OneOfBlock label

Remove label of OneOfBlock

PR Checklist

[x] Verify if the change requires a changeset. See CONTRIBUTING.md
[x] Link to the respective task if one exists: COM-863
[x] Provide screenshots/screencasts if the change contains visual changes

Screenshots/screencasts
Hidden label:

@johnnyomair  Instead of making the label editable it was decided to remove it


Cannot use Array.prototype.includes()

Type of Issue
[x] Bug Report
[ ] Feature Request

Description
If I use Array.prototype.includes() in my library I get errors with ng-packagr. ng serve works flawlessly.
How To Reproduce
Just use Array.prototype.includes() into your library. You can use this one if you want to mimic my very same environment: https://github.com/darkbasic/ngx-selectable-list/tree/packagr
Expected Behaviour
Should be able to use Array.prototype.includes().
Version Information
ng-packagr: ^2.0.0-rc.5
@angular/*: ^5.0.0
typescript: ~2.4.2
rxjs: ^5.5.2
node: 9.2.0
npm/yarn: 5.6.0

https://github.com/darkbasic/ngx-selectable-list/blob/packagr/package.json

Hi @darkbasic,
do you like to open a PR for #354?


Filter Fun

Description 📜
A web app taking its base from openCV concepts like, hsv filet rgb2gray, average filets, Gaussian filters and more to apply filter to images when uploaded.
Fixes #<issue_number_here>

Type of change 📝
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x] Add a new project

Domain of Contribution 📊
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x] Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Recommended) 📸
https://user-images.githubusercontent.com/82095877/166000404-628b976f-52b0-422c-bc13-2e283f5d5bfb.mp4

@gurjeetsinghvirdee please review this PR, and the video is in this format, because screen recording could not capture the shifted page while taking image.

fetch upstream @AnIkeT126

fetch upstream @AnIkeT126

Fetched.

Description 📜
A web app taking its base from openCV concepts like, hsv filet rgb2gray, average filets, Gaussian filters and more to apply filter to images when uploaded.
Fixes #1047
Type of change 📝
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x]  Add a new project

Domain of Contribution 📊
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x]  Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x]  I have performed a self-review of my own code or work.
[x]  I have commented on my code, particularly in hard-to-understand areas.
[x]  My changes generates no new warnings.
[x]  I'm GSSoC'22 contributor

Screenshots / Gif (Recommended) 📸
video.mp4

Description 📜
A web app taking its base from openCV concepts like, hsv filet rgb2gray, average filets, Gaussian filters and more to apply filter to images when uploaded.
Fixes #1047
Type of change 📝
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x]   Add a new project

Domain of Contribution 📊
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x]   Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x]   I have performed a self-review of my own code or work.
[x]   I have commented on my code, particularly in hard-to-understand areas.
[x]   My changes generates no new warnings.
[x]   I'm GSSoC'22 contributor

Screenshots / Gif (Recommended) 📸
video.mp4

?

Description 📜
A web app taking its base from openCV concepts like, hsv filet rgb2gray, average filets, Gaussian filters and more to apply filter to images when uploaded.
Fixes #1047
Type of change 📝
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x]    Add a new project

Domain of Contribution 📊
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x]    Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x]    I have performed a self-review of my own code or work.
[x]    I have commented on my code, particularly in hard-to-understand areas.
[x]    My changes generates no new warnings.
[x]    I'm GSSoC'22 contributor

Screenshots / Gif (Recommended) 📸
video.mp4

?

by  mistake bhai..nvm


what's the relationship between moe and decode ensemble model in transformer model?

I observe the 'transformer_moe.py' file and read the paper about moe (mixture of experts). moe trains the model with an ensemble layer in both encode and decode parts. It is different from the ensemble model when decode (train multi-models and average the probability every step of decode). Is there any relationship between the two ways? Do they work independently? or could I understand that the ensemble model of decoding is a special case of moe?

There is a fundamental difference: a MoE model only runs 1 or 2 paths through the graph (experts), while an ensemble model runs them all and averages. It can be worthwhile to do ensembles of MoE models too, but of course ensembles are costly, while MoE can be computationally very efficient.
These are all interesting things to discuss, but I'd suggest to use our discussion group (https://groups.google.com/forum/#!forum/tensor2tensor) for that and keep this for issues with the code. Thanks!


[modify][cms][rss] stop creating history trash

Coverage increased (+0.1%) to 84.839% when pulling fcf2385f96585fac123b3d978fd54b09801e502c on feature/stop-creating-history-trash into c874691301c81d735d8e4979310775897e2772f3 on master.

Coverage increased (+0.1%) to 84.839% when pulling fcf2385f96585fac123b3d978fd54b09801e502c on feature/stop-creating-history-trash into c874691301c81d735d8e4979310775897e2772f3 on master.

Coverage increased (+0.1%) to 84.839% when pulling fcf2385f96585fac123b3d978fd54b09801e502c on feature/stop-creating-history-trash into c874691301c81d735d8e4979310775897e2772f3 on master.

Coverage increased (+0.1%) to 84.839% when pulling fcf2385f96585fac123b3d978fd54b09801e502c on feature/stop-creating-history-trash into c874691301c81d735d8e4979310775897e2772f3 on master.

Coverage increased (+0.1%) to 84.839% when pulling fcf2385f96585fac123b3d978fd54b09801e502c on feature/stop-creating-history-trash into c874691301c81d735d8e4979310775897e2772f3 on master.


ChangeLog creation 1.0.0 RC1

DRAFT - Update needed due to latest merges
@evegufy working on an update asap ;)


Use css-minimizer-webpack-plugin for optimizing bundle

This is a follow up from https://github.com/konveyor/forklift-ui/pull/847.
I believe we can keep using css-minimizer-webpack-plugin instead of restoring optimize-css-assets-webpack-plugin to bundle css for production.
This reduces the bundle to 7.2 MB (from 7.4).
Effectively the former is more accurate and works by default since Webpack 5.
The original issue (see https://github.com/konveyor/forklift-ui/pull/646) is related to https://github.com/cssnano/cssnano/issues/675 and the work around for either plugin is to set mergeLonghand: false to cssnano processing (The flag to be  removed once addressed).

@seanforyou23, @mturley.
This is 500KB short from the 6.9MB mentioned in the related PR.
Not sure if that worth moving back to optimize-css-assets-webpack-plugin.
What do you think?

Wow, that was fast.
Honestly, as long as our CSS output is accurate, the dev experience is the same and everything looks right in prod, I don't really have any strong opinions about our webpack plugins. I'm curious which package is more prominently used by the community (sounds like css-minimizer-webpack-plugin?)
IMO the accuracy and stability outweighs a savings of 500KB, but I'm fine with either.
@gildub do you have other work that will depend on this one or are you ok with leaving it open until @seanforyou23 is back?

@mturley,
Thanks for the prompt feedback!
It was fast 'cause I fiddled around it in previous PR ;)
No deps upon it. Can definitely wait.


Bug, changing manage page, keeps current selected object in dropdown

Bug:
When an item is chosen from a dropdown (ie manage organisation) and the user changes to another mange page, the currently selected item from the dropdown persists to the new page.
organisation:

changed to pipeline:

This was fixed in the last PR


feat: update user details endpoint

What does the PR do?
This PR is about updating a user
How should this be manually tested?
Send a PATCH request to /api/v1/users/:userId with a request body as below
{
   "first_name": "String",
   "last_name": "String",
   "phone_number": "String"
}

Checklist of what you did

[x] Implemented endpoint to update a user.
[x] Validated request body and returned validation errors when validation fails.
[x] Implemented user authentication to ensure only authenticated users can update a user.
[x] Requests to the endpoint must include a valid authentication token in the Authorization header.
[x] Returned success message with response payload.
[x] Added unit tests for update user service

Test Screenshot

Reference Issue
[FEAT] Update user API

@buka4rill Kindly review my PR. It has two approvals.


[Accordion] Migrate to emotion

This PR migrates the Accordion component to emotion, as a part of #24405.

[X] I have followed (at least) the PR section of the contributing guide.

Alright, last thing remaining is the prop: children custom tests for this -- since Accordion.Naked is no longer defined, the tests crash:
  1) <Accordion />
       prop: children
         first child
           requires at least one child:
     TypeError: Cannot read property 'propTypes' of undefined
      at callback (packages/material-ui/src/Accordion/Accordion.test.js:125:29)
      at Proxy.matcher (test/utils/initMatchers.ts:497:11)
      at Proxy.toErrorDev (node_modules/chai/lib/chai/utils/addMethod.js:57:25)
      at Context.<anonymous> (packages/material-ui/src/Accordion/Accordion.test.js:130:12)
      at processImmediate (node:internal/timers:463:21)

  2) <Accordion />
       prop: children
         first child
           needs a valid element as the first child:
     TypeError: Cannot read property 'propTypes' of undefined
      at callback (packages/material-ui/src/Accordion/Accordion.test.js:136:29)
      at Proxy.matcher (test/utils/initMatchers.ts:497:11)
      at Proxy.toErrorDev (node_modules/chai/lib/chai/utils/addMethod.js:57:25)
      at Context.<anonymous> (packages/material-ui/src/Accordion/Accordion.test.js:141:12)
      at processImmediate (node:internal/timers:463:21)

I can't find any other components with similar tests, so I'm not really sure how to proceed with this?  (This is most likely my lack of knowledge of MUI's, and React's, inner workings getting in the way...)

Alright, last thing remaining is the prop: children custom tests for this -- since Accordion.Naked is no longer defined, the tests crash:
  1) <Accordion />
       prop: children
         first child
           requires at least one child:
     TypeError: Cannot read property 'propTypes' of undefined
      at callback (packages/material-ui/src/Accordion/Accordion.test.js:125:29)
      at Proxy.matcher (test/utils/initMatchers.ts:497:11)
      at Proxy.toErrorDev (node_modules/chai/lib/chai/utils/addMethod.js:57:25)
      at Context.<anonymous> (packages/material-ui/src/Accordion/Accordion.test.js:130:12)
      at processImmediate (node:internal/timers:463:21)

  2) <Accordion />
       prop: children
         first child
           needs a valid element as the first child:
     TypeError: Cannot read property 'propTypes' of undefined
      at callback (packages/material-ui/src/Accordion/Accordion.test.js:136:29)
      at Proxy.matcher (test/utils/initMatchers.ts:497:11)
      at Proxy.toErrorDev (node_modules/chai/lib/chai/utils/addMethod.js:57:25)
      at Context.<anonymous> (packages/material-ui/src/Accordion/Accordion.test.js:141:12)
      at processImmediate (node:internal/timers:463:21)

I can't find any other components with similar tests, so I'm not really sure how to proceed with this?  (This is most likely my lack of knowledge of MUI's, and React's, inner workings getting in the way...)

@vinyldarkscratch We do no longer need to look into .Naked. I have removed it. CI is green.

Awesome, thanks @oliviertassinari!


feat: update QuestionPage.js

Please check it out! Thank you!

I checked your modified code, and this is really good!


Docker setup for running nodejs agents and instructions

Cancelling this PR as it was not signed.  An additional PR is properly signed and includes the same content as this one.


May I suggest to use dicts as the input param for all functions?

I would like to suggest that all input parameters in the function/method be changed to a dictionary. This would allow me to create a dictionary with key-value pairs that need to be overridden and benefit from the update() method to quickly override default values without affecting other defaults. This approach would make the code more flexible and extensible, and would also make it easier to read and understand the meaning of each parameter. Additionally, using a dictionary for input parameters would allow for named parameters, which is a more flexible way of passing arguments to a function or method. I believe this change would greatly improve the usability and maintainability of the code. Thank you for considering my suggestion.

I don't want to have breaking api changes.
You can use ** to unpack dictionary to arguments:
d = {"prompt": "photo of a pretty girl",
     "height":768, "seed":1001}

r = api.txt2img(**d)
r.image

Sure, thanks for your reply!


Route does not match double-dash flag

This is my simple route definition:
'[--flag|-f] <arg>'

Only "-f" and "-flag" match, "--flag" does not. According to the documentation, "--flag" should match, which would also follow common conventions.

Originally posted by @hschletz at https://github.com/zendframework/zend-console/issues/6

What OS are you observing this on? We have used these flags successfully on
zf-deploy (see its route configuration).
One note: if the glad should allow an argument, you need to use special
notation:
[--flag|-f]:flag

I suggest looking at the tests,
as those demonstrate the full range of options supported — which include
the scenario you indicated. I cannot reproduce the issue you present on
Linux, which leads me to believe it may be an environmental issue.
On Nov 14, 2015 1:12 PM, "hschletz"<EMAIL_ADDRESS>wrote:

This is my simple route definition:
'[--flag|-f] '
Only "-f" and "-flag" match, "--flag" does not. According to the
documentation, "--flag" should match, which would also follow common
conventions.
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/zend-console/issues/6.

Originally posted by @weierophinney at https://github.com/zendframework/zend-console/issues/6#issuecomment-156759781

I forgot to test with real application. The problem only occurs during unit tests for my controller. It is caused by the command line parser regex in AbstractControllerTestCase::run():
preg_match_all('/(--\S+[= ]"[^\s"]*\s*[^\s"]*")|(--\S+=\S+|--\S+\s\S+|\S+)/', $url, $matches);

If I dispatch "arg --flag", the command line gets broken down correctly:
array(2) {
  [0]=>
  string(15) "arg"
  [1]=>
  string(10) "--flag"
}

but with "--flag arg" I get:
array(1) {
  [0]=>
  string(26) "--flag arg"
}

This would be correct in case of value parameters, but not with simple flags. But even with value parameters, this would not work as documented in practice, as demonstrated by this simple script:
<?php
var_dump($_SERVER['argv']);

Run it with given arguments:
php test.php --flag arg
array(3) {
  [0]=>
  string(8) "test.php"
  [1]=>
  string(6) "--flag"
  [2]=>
  string(3) "arg"
}

The arguments are passed according to my route specification, which is why the script works as expected when run from the command line, but the unit test fails.
Out of curiosity, I changed the route to "--flag=". It turns out that "--flag=arg" works as expected, but "--flag arg" is still treated as separate parameters due to the way the OS parses command lines (I ran it on Linux BTW).
So either the request params must be concatenated if argv contains a single "--flag" instead of "--flag=arg", or the "--flag arg" variant should be removed from the documentation.
The command line parser in AbstractControllerTestCase needs to be fixed too. I doubt that a single regex will be able to handle all edge cases the same way as the OS does, like escaped quotes. For complex command lines that get parsed incorrectly, it would be nice to pass parameters as an array in the third argument to dispatch(), but currently this gets unconditionally replaced with the parsed command line for console tests.

Originally posted by @hschletz at https://github.com/zendframework/zend-console/issues/6#issuecomment-156814850

This package is abandoned and will receive no further development!
We recommend using laminas/laminas-cli.


ERROR: Signature extraction failed:

Checklist

[ x] I'm reporting a broken site support issue
[x ] I've verified that I'm running youtube-dl version 2021.06.06
[ x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x ] I've searched the bugtracker for similar bug reports including closed ones
[x ] I've read bugs section in FAQ

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--extract-audio', u'--audio-format', u'mp3', u'--verbose', u'https://www.youtube.com/watch?v=z1tTIDkEy5g']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.06.06
[debug] Python version 2.7.16 (CPython) - Linux-5.0.0-38-generic-x86_64-with-Ubuntu-19.04-disco
[debug] exe versions: ffmpeg 4.1.3, ffprobe 4.1.3
[debug] Proxy map: {}
[youtube] z1tTIDkEy5g: Downloading webpage
[youtube] z1tTIDkEy5g: Downloading player f3c4e04d
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1349, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1262, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1331, in _parse_sig_js
initial_function = jsi.extract_function(funcname)
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 245, in extract_function
raise ExtractorError('Could not find JS function %r' % funcname)
ExtractorError: Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1349, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1262, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1331, in _parse_sig_js
initial_function = jsi.extract_function(funcname)
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 245, in extract_function
raise ExtractorError('Could not find JS function %r' % funcname)
ExtractorError: Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 815, in wrapper
return func(self, *args, **kwargs)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 836, in __extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 534, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1623, in _real_extract
signature = self._decrypt_signature(sc['s'][0], video_id, player_url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1359, in _decrypt_signature
'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1349, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1262, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1331, in _parse_sig_js
initial_function = jsi.extract_function(funcname)
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 245, in extract_function
raise ExtractorError('Could not find JS function %r' % funcname)
ExtractorError: Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Description

fails

me too

Same

Same issue happened to me.
Here's the verbose log that I collected:
Log in pastebin

Appears to be same as everyone reporting above... details follow
sudo youtube-dl -U
youtube-dl is up-to-date (2021.06.06)
$ youtube-dl https://www.youtube.com/watch?v=rvnE6IJZugA --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'https://www.youtube.com/watch?v=rvnE6IJZugA', u'--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.06.06
[debug] Python version 2.7.18 (CPython) - Linux-5.4.0-91-generic-x86_64-with-Ubuntu-20.04-focal
[debug] exe versions: ffmpeg 4.2.4, ffprobe 4.2.4, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] rvnE6IJZugA: Downloading webpage
[youtube] rvnE6IJZugA: Downloading player f3c4e04d
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1349, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1262, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1331, in _parse_sig_js
initial_function = jsi.extract_function(funcname)
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 245, in extract_function
raise ExtractorError('Could not find JS function %r' % funcname)
ExtractorError: Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1349, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1262, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1331, in _parse_sig_js
initial_function = jsi.extract_function(funcname)
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 245, in extract_function
raise ExtractorError('Could not find JS function %r' % funcname)
ExtractorError: Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 815, in wrapper
return func(self, *args, **kwargs)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 836, in __extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 534, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1623, in _real_extract
signature = self._decrypt_signature(sc['s'][0], video_id, player_url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1359, in _decrypt_signature
'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1349, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1262, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1331, in _parse_sig_js
initial_function = jsi.extract_function(funcname)
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 245, in extract_function
raise ExtractorError('Could not find JS function %r' % funcname)
ExtractorError: Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Could not find JS function u'na'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Duplicate of #30363, with fix.
Also, follow the instructions for posting a Broken site support issue which would have led you to review the existing issue and not create a new one. As it is, @jheled, kindly close this issue.

I will close, but a fix is not a fix until 'youtube-dl -U' works.

That is not a problem that can be solved without maintainer access, and there hasn't been any, unfortunately. I expect that #30363 will remain open until closed by merging a fix.


pandas_profiling wont work, even after updating

Describe the bug
getting error code after ProfileReport was working fine previously.
 66         description_set = describe(df, **kwargs)
 67
 68         self.html = to_html(sample,

C:\ProgramData\Anaconda3\lib\site-packages\pandas_profiling\describe.py in describe(df, bins, check_correlation, correlation_threshold, correlation_overrides, check_recoded, pool_size, **kwargs)
390             if name not in names:
391                 names.append(name)
--> 392     variable_stats = pd.concat(ldesc, join_axes=pd.Index([names]), axis=1)
393     variable_stats.columns.names = df.columns.names
394
TypeError: concat() got an unexpected keyword argument 'join_axes'
-->
To Reproduce
<!--

_Data:_
any dataframe

_Code:_ Preferably, use this code format:
```pandas_profiling.ProfileReport(df)
"""
Test for issue XXX:
"""
import pandas as pd
import pandas_profiling
pandas_profiling.ProfileReport(df)

Hi,
i too faced the same issue
Regards

Hi,
Also running into the same issue. I upgraded to pandas 1.0 yesterday. Likely related.

Same here. I'm also getting the same issue.

For me the same. Pandas 1.0 is installed.

Note that pandas 1.0 is not yet stable and is not supported:
https://github.com/pandas-profiling/pandas-profiling/issues/367#issuecomment-583389681

how to solve the version betwon pandas and pandas-profiling, this question

It would fix your problem
!pip3 install pandas_profiling --upgrade
Cheers!


fix: add CORS support for simdata-api

What new features does this PR implement?
in a deployed environment, the browser was getting CORS errors.  This PR adds CORS (Cross-origin Resource Sharing) to the new simdata-api service using FastAPI's CORSMiddleware.  The allowed origins were set to the same list used by combine-api.

:tada: This PR is included in version 9.55.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update Google2FA.php

fix for Unsupported operand types: string + int

Like I said this never an issue before upgrading project dependents today. And making sure this $oldTimestamp converted to int is not a bad idea, but if you felt otherwise you can ignore the pull request
Sent from my iPhone

On Jan 21, 2022, at 9:24 PM, Markus Podar @.***> wrote:

@mfn commented on this pull request.
In src/Google2FA.php:

@@ -231,7 +231,7 @@ private function makeStartingTimestamp($window, $timestamp, $oldTimestamp = null
{
return is_null($oldTimestamp)
? $timestamp - $this->getWindow($window)

       : max($timestamp - $this->getWindow($window), $oldTimestamp + 1);

       : max($timestamp - $this->getWindow($window), intval($oldTimestamp) + 1);

I understand, but the whole code base documents it as int, so why are you having a string?
If the library moves to types, this would have to be removed because then it's not possible to have non-ints pass in so I asked, why do you have string in the first place?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

Yes, closing, thank you!


Update traefik.md

Quick clarification
https://github.com/benphelps/homepage/discussions/818

Thanks, its optional though so I clarified that


How to configure proxy

How in this starter kit to setup proxy for api? Which is running on different instance and port. In original JavaScript we have this solution
But how to setup in this typescript starter kit? Any advice, example, solution?

This starter kit uses custom next.config.js which is used next command(eg, ./node_mobules/.bin/node next start) for typescript compile process with webpack.
according to https://github.com/zeit/next.js/#custom-server-and-routing
proxy setup issue is out of next environment, so you can't use next's compile environment.
If you want to setup proxy, basically there are two ways

write custom server code in js.
write in ts and manually compile to js.

I recommend you second way. because you need to extra setup(babel) to use es2015+ syntax.


Docs: Improve contributing.md to be more useful for contributors INTER-758

Hey there :) I tried expanding CONTRIBUTING.MD to make it easier for people across the company to contribute schema changes. Please let me know what else is missing based on your experience. Thanks!

I did not know that this file existed...had I known, it could have saved some time. Maybe, we should market it better :-)

I did not know that this file existed...had I known, it could have saved some time. Maybe, we should market it better :-)

My bad :( It's mentioned and linked to in the Readme now

Merging, if you have more improvement ideas later on, feel free to ping me or open your own PR, thanks!


Multiply Strings

Given two non-negative integers num1 and num2 represented as strings, return the product of num1 and num2, also represented as a string.
Note: You must not use any built-in BigInteger library or convert the inputs to integer directly.
Example 1:
Input: num1 = "2", num2 = "3"
Output: "6"
Example 2:
Input: num1 = "123", num2 = "456"
Output: "56088"

Piyusha Ghodake.
Sy Comp.
I would like to work on this issue.

Piyusha Ghodake. Sy Comp. I would like to work on this issue.

You have already been assigned one issue. You can work only on one issue at a time . Once you complete it you may work on this issue if no one else comments on it.

Okk

I am Arti Tambade, TY IT.
I would like to work on this issue
can you please assign this Issue to me?

This Issue is repeated issue.


Feature: avoid downloading third-party assets

Hi there! I would love to use this component but I have not been able to config it to prevent downloading some assets from a CDN, which forces me preconnect / dns-prefetch resources from https://cdn.jsdeliver.net as lighthouse performance recommendation.

To "fix" that, I made some small changes to the code that avoid downloading these third-party assets if a local path is specified (it works nicely in the project I am working on) and I wonder if this functionality could be useful for the general purpose of the project, or just for anyone else.
Basically now a prop can be used to specify the local folder of the resources. If the prop is not set, the assets will be downloaded from the original URL_ASSETS constant (requiring silently those link tags to be implemented!).
This is my working example:
<template>
  <SocialChat
    icon
    :url-assets=“assetsPath”
    :attendants="attendants"
  >
  <!-- here the slots -->
  </SocialChat>
</template>

<script>
import { SocialChat } from 'vue-social-chat'

export default {
  name: 'SocialChat',

  components: {
    SocialChat,
  },

  data: () => ({
    assetsPath: '/images/vue-social-chat', // from the `static` folder
    attendants: [
      // ...
    ],
  }),
}
</script>

@ktquez is there a plan to merge this PR or support images from the static folder?

@galaxy79
Thanks for reminding me, I'll add it in the next version.
When it's published, I'll let you know here.
@whoisjorge Thanks for the PR

@ktquez was this change pushed to npm ?


change infos to dokumente

change "Mehr Infos" to "Dokumentation"

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


🐛 [BUG]: Change the position of the connection handle of the node. The connection line does not change

Is there an existing issue for this?

[X] I have searched the existing issues and this is a new bug.

Current Behavior
When I change the connection handle position of the node, the connection line does not change, and the line through the connection handle is also wrong

Expected Behavior
I wanted the connection line to be updated when I modified the handle, but that didn't happen
Steps To Reproduce
Please refer to the code below to reproduce the bug
Relevant log output
const onChangeTS = () => {
  const node: any = nodes.value.find((n) => n.selected)
  if (!node) return
  node.targetPosition = node.targetPosition === 'left' ? 'top' : 'left'
  node.sourcePosition = node.sourcePosition === 'right' ? 'bottom' : 'right'
}

Anything else?
No response

Two things, both aren't a bug here.

If you wanna have a an edge that just connects to the same node, you'll have to use a custom edge and adjust the path, otherwise the edge will run through the node - default edges aren't meant for self-loops.
If you update the position of your handles, you need to notify your node about this. This is documented right here: https://vueflow.dev/guide/node.html#working-with-dynamic-handle-positions-adding-handles-dynamically
So in your case

const onChange = () => {
  const node: any = nodes.value.find((n) => n.selected)

  if (!node) return

  node.targetPosition = node.targetPosition === 'left' ? 'top' : 'left'
  node.sourcePosition = node.sourcePosition === 'right' ? 'bottom' : 'right'

  setTimeout(() => {
    updateNodeInternals(['1'])
  }, 0)
}

Here's an example: https://codesandbox.io/p/devbox/sleepy-ritchie-p4yn9m?file=%2Fsrc%2FApp.vue%3A36%2C1-38%2C8

Thank you, boss.

This is a ReactFlow example for a self-connecting node but you can use the same concept for VueFlow: https://codesandbox.io/p/sandbox/sharp-orla-vyjqen


Change in referenced file not propagating

Let's say I have two files child.html and parent.html and the child.html file is referenced in the  parent.html file. Now I run cache bust on those files and they both get renamed to some filenames child.{a}.html and parent.{b}.html (with a and b as the hash values).
If I now change the child.html and run cache bust again, only the child file will get the new filename child.{a'}.html. The parent file will remain with it's old filename parent.{b}.html.
I prepared a small example: https://github.com/BastianHofmann/grunt-cachebust-test (just to npm install and run grunt, you can use the change branch to change the child.html file)
I would expect the filename of the parent to change as well.
When using angular's ng-include feature (see my example). The parent.html file is requested first, which will in turn request child.html. A client who has both files cached will not receive the change in the child.html file, because the parent.html file did not change.
To resolve this issue, the plugin could create a tree structure for the dependencies in the files and cache bust the tree from the leaves to the root. Loops in the tree may occur (a references b and b references a), but could easily be resolved by choosing a random node as the root (cache bust b -> replace filename in a -> cache bust a -> replace filename in b).

I'm seeing the same phenomena, but with JavaScript files instead of HTML files.


amplify-cli generate a package.json file with a non existent cli-extensibility-helper version

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.17.0
Amplify CLI Version
10.3.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
We override auth generated resources using amplify override as described in the documentation
Amplify Categories
auth
Amplify Commands
push
Describe the bug
Using the latest amplify versions 10.3.0 and 10.3.1 on CI/CD, the build process failed with the following error.
2022-10-25T08:05:55.459Z [INFO]: 🛑 Build error : Packaging overrides failed with the error:
                                 Command failed with exit code 1: yarn install
                                 warning package.json: No license field
                                 warning<EMAIL_ADDRESS>No license field
                                 error Couldn't find any versions for "@aws-amplify/cli-extensibility-helper" that matches "2.3.33-signinUpdate.1"
                                 yarn install v1.22.0
                                 info No lockfile found.
                                 [1/4] Resolving packages...
                                 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
2022-10-25T08:05:55.460Z [WARNING]: - Building resource storage/demos

We tried to search for that version 2.3.33-signinUpdate.1 on npmjs and we didn't find it, however, we found the 2.3.33-signinUpdate.0 version instead
We have also tried to reproduce the same behaviour on local machine using amplify push and we got the same error when we removed the existing amplify/backend/package.json file which was using ^2.0.0 version for cli-extensibility-helper.
Checking amplify-cli sourcecode, it seems that the version for the generated file has changed recently
https://github.com/aws-amplify/amplify-cli/blob/v10.3.1/packages/amplify-cli-core/resources/overrides-resource/package.json#L11
Expected behavior
Amplify push and CI/CD should proceed as normal with no errors
Reproduction steps

On an amplify project, delete existing amplify/backend/package.json
Override auth using amplify override auth
Run amplify push
Check the generated amplify/backend/package.json file

GraphQL schema(s)
No response
Project Identifier
No response
Log output
No response
Additional information
No response

Thanks for reporting this and adding so much context in the description!
As a workaround, I suggest updating the dependency in your package.json to depend on the latest 2.x version: "@aws-amplify/cli-extensibility-helper": "^2.0.0"


Improve documentation and legibility in 3.x.

Did a pass for every place we were writing Polymer.foo.
Basic cleanup of a number of places for legibility by both humans and polymer-analyzer.

Oh, and I removed all the now incorrect @memberof annotations.

Noting that this is part of https://github.com/Polymer/docs/issues/2379


added repo links in the table

Only added to contributing.mdx since it is the only visible version on the website for now but can also update index.mdx if you like. Index.mdx has the same table but the page is not currently reachable through the current navigation
Signed-off-by: John ODwyer<EMAIL_ADDRESS>

Can make text in each link look like this? Otherwise its not clear what each repo is for.. special  delta and connectors


When docker pull callback is called, tags are not all downloaded

shopmedia@staging3:~$ docker images | grep kafka
registry:5000/kafka                  <IP_ADDRESS>-24              825b925e65cc        6 minutes ago       519.8 MB
registry:5000/kafka                  latest                  825b925e65cc        6 minutes ago       519.8 MB

A new version is created and pushed on registry:5000/kafka and tagged with 'latest' and '<IP_ADDRESS>-25'
We can query the private registry to make sure everything have been pushed

http://registry:5000/v1/repositories/kafka/tags
{
    "<IP_ADDRESS>-24": "825b925e65cce5a08de8ac7901fdeed7bc51c272b3a0bcc4bd671187b4f7f8ea",
    "<IP_ADDRESS>-25": "bfd84b3cb6d023f7d74084c4232a3471fc0d6352f39375105f58b519becfc4d3",
    "latest": "bfd84b3cb6d023f7d74084c4232a3471fc0d6352f39375105f58b519becfc4d3"
}

I launch the script

3-1) It pulls all the tags registry:5000/kafka. I should get the latest and the new <IP_ADDRESS>-25 tags
3-2) It inspects the latest and its still showing version <IP_ADDRESS>-24 even though all the tags have been pulled
C:\dev\apps\deploy>node test.js
Pulling registry:5000/kafka
Successfully Pulled registry:5000/kafka
kafka version registry:5000/kafka:latest 825b925e65cce5a08de8ac7901fdeed7bc51c272b3a0bcc4bd671187b4f7f8ea

If I launch the script again, the correct version is showing up
Pulling registry:5000/kafka
Successfully Pulled registry:5000/kafka
kafka version registry:5000/kafka:latest bfd84b3cb6d023f7d74084c4232a3471fc0d6352f39375105f58b519becfc4d3

Simplified code to reproduce the issue:

var Docker = require('dockerode');
var docker = new Docker({host: 'http://staging3', port: 4243});
var kafka = {"image": "registry:5000/kafka"};

var pull = function(target) {

	console.log(" Pulling "+target.image);
	docker.pull(target.image,
		function(err, stream) {
			if(!err) {
				console.log("Successfully Pulled "+target.image);
				handler();
			}
		}
	 );
}

var handler = function() {

	docker.getImage(kafka.image+":latest").inspect(
		function(err, data) {
			if(!err) {
				console.log("kafka version "+  kafka.image + ":latest "+data.Id);
			}
		}
	);
}

pull(kafka);

Do you have any idea ?

@florentvaldelievre, when isStream == true, as in this case, the callback is called with a readable stream representing output of the command. The command is not completed at this moment, it will be completed when it's output ends.
The output is a newline-delimited JSON stream with a certain format (see Docker remote API docs).
So you need to wait for the stream to end. Also it is a useful practice to register a listener for stream errors too, because otherwise your app will crash when a stream error is encountered.
This should work:
var Docker = require('dockerode'),
    docker = new Docker({ socketPath: '/var/run/docker.sock' }),
    JSONStream = require('JSONStream');

function pullImage(tag, cb, onProgress)
{
  docker.pull(tag, function(err, cmdOutStream)
  {
    if (err) return cb(err);

    var parser = JSONStream.parse(),
        output = [];

    parser.on('root', onStreamEvent);
    parser.on('error', onStreamError);
    parser.on('end', cb);

    cmdOutStream.pipe(parser);

    function onStreamEvent(evt)
    {
      output.push(evt);

      if (evt.error)
        return onStreamError(evt.error, output);

      onProgress && onProgress(evt);
    }

    function onStreamError(err)
    {
      parser.removeListener('root', onStreamEvent);
      parser.removeListener('error', onStreamError);
      parser.removeListener('end', cb);
      cb(err);
    }

    function onStreamEnd() {
      cb(null, output);
    }
  });
}

pullImage('registry:5000/kafka:latest',
  function onCompleted(err, output)
  {
    if (err)
      return console.error('cannot pull image:', err);

    console.log('done!');

    // useful when you are not passing onProgress callback
    // console.log('full output:', output.map(JSON.stringify).join('\n'));

    checkImage();
  },
  function onProgress(evt)
  {
    console.log('pulling progress:', evt);
  }
);

function checkImage()
{
  docker.getImage("registry:5000/kafka:latest").inspect(function(err, data)
  {
    if (err)
      return console.error('error ingpecting image: ' + err);

    console.log("kafka:latest:" + data.Id);
  );
}

It uses JSONStream module to parse progress messages. Put it in a pull-test.js file, run npm install dockerode JSONStream and then node pull-test.js :)

@apocas, maybe we should make isStream an option of docker.pull() and similar functions, to simplify their usage when the caller is not concerned with the in-progress output and only needs the end result of an operation?

Really nice @skozin , thanks a lot for that ! Sorry for the response delay

Yeah I definitely have been hearing about this one a lot.
My idea to solve this, is similar to what it was done with stream multiplexing.
I will test this and see how the usage ends up.
Will update the status of this issue and will ping you guys about it later.

@florentvaldelievre, no problem :)
@apocas, thank you for considering this! I like the idea of providing a helper function similar to container.modem.demuxStream. I see something like this:
// get just the end result

docker.pull(tag, function(err, stream) {
  docker.followProgress(err, stream, onFinished);
});

function onFinished(err, output) {
  // pull completed successfully <=> err == null
  // output is full stream body (or maybe an array of parsed JSON events)
}

// get the end result and progress updates

docker.pull(tag, function(err, stream) {
  docker.followProgress(err, stream, onFinished, updateProgress);
});

function updateProgress(evt) {
  // evt is already parsed (plain object)
}

function onFinished(err, output) {
  // pull completed successfully <=> err == null
  // output is full stream body (or maybe an array of parsed JSON events)
}

Hi guys,
Sorry for the delay.
As been discussed, check this out:
https://github.com/apocas/dockerode/blob/master/test/docker.js#L167
and
https://github.com/apocas/dockerode/blob/master/test/docker.js#L149
Going to publish this soon.

Published on v2.1.0


Fixing typo's

Fixing typo's

@DarrylvanderPeijl : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good. Thanks @DarrylvanderPeijl.


regression test for #1554

Current coverage is 92.79%

Merging #1560 into master will increase coverage by +0.02% as of fdfd216

@@            master   #1560   diff @@
======================================
  Files           87      87
  Stmts         5484    5484
  Branches      1019    1019
  Methods          0       0
======================================
+ Hit           5088    5089     +1
  Partial          9       9
+ Missed         387     386     -1

Review entire Coverage Diff as of fdfd216

Powered by Codecov. Updated on successful CI builds.


SSX Release v1.2.3

Description
This PR has the version bump for ssx-sdk v1.2.3

Codecov Report
Base: 90.34% // Head: 90.34% // No change to project coverage :thumbsup:

Coverage data is based on head (cf07023) compared to base (aa228bc).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #89   +/-   ##
=======================================
  Coverage   90.34%   90.34%
=======================================
  Files          25       25
  Lines        3336     3336
  Branches      270      270
=======================================
  Hits         3014     3014
  Misses        322      322

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.