Follow basic instruction from readme but still not able to deploy

I am new to gen3 and followed instruction to deploy the most basic one using helm. I installed ranch desktop and postgreSQL@13, but stll cannot reach website at https://localhost/. Here is my values.yaml:
global:
  hostname: localhost
  # hostname: example-commons.com

# fence:
  FENCE_CONFIG:
    # Any fence-config overrides here. ]

arborist:
  postgres:
    dbCreate: true
    username: gen3_arborist
    password: gen3_arborist

And when I run helm upgrade --install gen3 gen3/gen3 -f ./values.yaml  and check the status of pod, it seem like some pod is not working or pend:
kubectl get pod
NAME                                              READY   STATUS             RESTARTS          AGE
wts-deployment-57ff756898-hc6tz                   0/1     Pending            0                 2d17h
fence-deployment-6f8489fb88-v4xlp                 0/1     Pending            0                 2d17h
portal-deployment-6c7f86d4f8-dkvbn                0/1     Pending            0                 2d17h
hatchery-deployment-7fcb68fb65-phpf7              1/1     Running            0                 2d17h
wts-oidc-job-52gzp                                0/2     Init:0/1           0                 2d17h
revproxy-deployment-9764957cd-cl5n5               1/1     Running            0                 2d17h
gen3-postgresql-0                                 1/1     Running            0                 2d17h
sower-85597bddbf-j5s86                            1/1     Running            0                 2d17h
manifestservice-deployment-6c74479448-tnrbs       1/1     Running            0                 2d17h
indexd-dbcreate-d86wl                             0/1     Completed          0                 2d17h
metadata-dbcreate-qvb88                           0/1     Completed          0                 2d17h
audit-dbcreate-k6gkf                              0/1     Completed          0                 2d17h
peregrine-dbcreate-rj5xf                          0/1     Completed          0                 2d17h
wts-dbcreate-twg8k                                0/1     Completed          0                 2d17h
arborist-dbcreate-ghqzv                           0/1     Completed          0                 2d17h
sheepdog-dbcreate-m6v8g                           0/1     Completed          0                 2d17h
fence-dbcreate-95kgz                              0/1     Completed          0                 2d17h
gen3-elasticsearch-master-0                       1/1     Running            0                 2d17h
arborist-deployment-77645d555-ch4tv               1/1     Running            0                 2d17h
indexd-deployment-b845d4565-flk9p                 1/1     Running            0                 2d17h
metadata-deployment-559bbdd459-86ptb              1/1     Running            0                 2d17h
audit-deployment-54c96847c8-696x8                 1/1     Running            0                 2d17h
indexd-userdb-4lnc7                               0/1     Completed          0                 2d17h
presigned-url-fence-deployment-6d657f9cfd-kbrsf   1/1     Running            0                 2d17h
ambassador-deployment-6cd65d48d6-dljsz            0/1     Running            52 (26h ago)      2d17h
sheepdog-deployment-746959d756-l27vz              0/1     CrashLoopBackOff   337 (3m32s ago)   2d17h
argo-wrapper-deployment-85f5d4b756-mv2l5          0/1     ImagePullBackOff   0                 2d17h
peregrine-deployment-6d9b6b584b-9dgnn             0/1     CrashLoopBackOff   222 (22s ago)     2d17h
pidgin-deployment-b9c7c5b7d-rdgzs                 0/1     CrashLoopBackOff   219 (21s ago)     2d17h

And here is some logs for crashed pods:
(base) FDSIT-7000-M7:config minghao.zhou$ kubectl logs pidgin-deployment-b9c7c5b7d-rdgzs
Got configuration:
GEN3_DEBUG=False
GEN3_UWSGI_TIMEOUT=45s
GEN3_DRYRUN=False
Running update-ca-certificates
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Running mkdir -p /var/run/gen3
Running nginx -g daemon off;
Running uwsgi --ini /etc/uwsgi/uwsgi.ini
[uWSGI] getting INI configuration from /app/uwsgi.ini
[uWSGI] getting INI configuration from /etc/uwsgi/uwsgi.ini
open("./python3_plugin.so"): No such file or directory [core/utils.c line 3732]
!!! UNABLE to load uWSGI plugin: ./python3_plugin.so: cannot open shared object file: No such file or directory !!!
*** Starting uWSGI 2.0.20 (64bit) on [Mon Apr  1 16:29:58 2024] ***
compiled with version: 8.3.0 on 14 March 2022 16:22:45
os: Linux-6.6.14-0-virt #1-Alpine SMP Fri, 26 Jan 2024 11:08:07 +0000
nodename: pidgin-deployment-b9c7c5b7d-rdgzs
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 4
current working directory: /var/www/pidgin
detected binary path: /usr/local/bin/uwsgi
chdir() to /pidgin/
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
lock engine: pthread robust mutexes
!!! it looks like your kernel does not support pthread robust mutexes !!!
!!! falling back to standard pthread mutexes !!!
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /var/run/gen3/uwsgi.sock fd 3
setgid() to 102
set additional group 101 (ssh)
setuid() to 102
Python version: 3.9.10 (main, Mar  2 2022, 04:40:14)  [GCC 8.3.0]
2024/04/01 16:29:58 [notice] 2011#2011: using the "epoll" event method
2024/04/01 16:29:58 [notice] 2011#2011: nginx/1.21.1
2024/04/01 16:29:58 [notice] 2011#2011: built by gcc 8.3.0 (Debian 8.3.0-6)
2024/04/01 16:29:58 [notice] 2011#2011: OS: Linux 6.6.14-0-virt
2024/04/01 16:29:58 [notice] 2011#2011: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2024/04/01 16:29:58 [notice] 2011#2011: start worker processes
2024/04/01 16:29:58 [notice] 2011#2011: start worker process 2017
2024/04/01 16:29:58 [emerg] 2017#2017: io_setup() failed (38: Function not implemented)
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0x4000171d60
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 304776 bytes (297 KB) for 2 cores
*** Operational MODE: preforking ***
added /usr/local/lib/python3.9/site-packages/ to pythonpath.
WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x4000171d60 pid: 2013 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 2013)
spawned uWSGI worker 1 (pid: 2019, cores: 1)
spawned uWSGI worker 2 (pid: 2021, cores: 1)
[2024-04-01 16:30:08,527][pidgin.app][  ERROR] Peregrine not available; returning unhealthy
[2024-04-01 16:30:18,526][pidgin.app][  ERROR] Peregrine not available; returning unhealthy
(base) FDSIT-7000-M7:config minghao.zhou$ kubectl logs peregrine-deployment-6d9b6b584b-9dgnn
Got configuration:
GEN3_DEBUG=False
GEN3_UWSGI_TIMEOUT=600
GEN3_DRYRUN=False
Running update-ca-certificates
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Running mkdir -p /var/run/gen3
Running nginx -g daemon off;
Running uwsgi --ini /etc/uwsgi/uwsgi.ini
[uWSGI] getting INI configuration from /app/uwsgi.ini
[uWSGI] getting INI configuration from /etc/uwsgi/uwsgi.ini
open("./python3_plugin.so"): No such file or directory [core/utils.c line 3732]
!!! UNABLE to load uWSGI plugin: ./python3_plugin.so: cannot open shared object file: No such file or directory !!!
*** Starting uWSGI 2.0.20 (64bit) on [Mon Apr  1 16:29:47 2024] ***
compiled with version: 8.3.0 on 11 November 2021 18:25:57
os: Linux-6.6.14-0-virt #1-Alpine SMP Fri, 26 Jan 2024 11:08:07 +0000
nodename: peregrine-deployment-6d9b6b584b-9dgnn
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 4
current working directory: /var/www/peregrine
detected binary path: /usr/local/bin/uwsgi
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
lock engine: pthread robust mutexes
!!! it looks like your kernel does not support pthread robust mutexes !!!
!!! falling back to standard pthread mutexes !!!
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /var/run/gen3/uwsgi.sock fd 3
setgid() to 102
set additional group 101 (ssh)
setuid() to 102
Python version: 3.6.15 (default, Oct 13 2021, 09:49:57)  [GCC 8.3.0]
2024/04/01 16:29:47 [notice] 2011#2011: using the "epoll" event method
2024/04/01 16:29:47 [notice] 2011#2011: nginx/1.21.1
2024/04/01 16:29:47 [notice] 2011#2011: built by gcc 8.3.0 (Debian 8.3.0-6)
2024/04/01 16:29:47 [notice] 2011#2011: OS: Linux 6.6.14-0-virt
2024/04/01 16:29:47 [notice] 2011#2011: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2024/04/01 16:29:47 [notice] 2011#2011: start worker processes
2024/04/01 16:29:47 [notice] 2011#2011: start worker process 2017
2024/04/01 16:29:47 [emerg] 2017#2017: io_setup() failed (38: Function not implemented)
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0x4000172420
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 45 seconds
mapped 304776 bytes (297 KB) for 2 cores
*** Operational MODE: preforking ***
added /var/www/peregrine/ to pythonpath.
added /peregrine/ to pythonpath.
added /usr/local/lib/python3.6/site-packages/ to pythonpath.
failed to open python file /var/www/peregrine/wsgi.py
unable to load app 0 (mountpoint='') (callable not found or import error)
*** no app loaded. going in full dynamic mode ***
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 2013)
spawned uWSGI worker 1 (pid: 2019, cores: 1)
spawned uWSGI worker 2 (pid: 2021, cores: 1)
--- no python application found, check your startup logs for errors ---
--- no python application found, check your startup logs for errors ---
--- no python application found, check your startup logs for errors ---
(base) FDSIT-7000-M7:config minghao.zhou$ kubectl logs argo-wrapper-deployment-85f5d4b756-mv2l5
Error from server (BadRequest): container "argo-wrapper" in pod "argo-wrapper-deployment-85f5d4b756-mv2l5" is waiting to start: trying and failing to pull image
(base) FDSIT-7000-M7:config minghao.zhou$ kubectl logs sheepdog-deployment-746959d756-l27vz
Defaulted container "sheepdog" out of: sheepdog, sheepdog-init (init)

Any suggestions on this?

And when I reinstall gen3 and get logs from "default/portal-deployment-6c7f86d4f8-brqjn" like this:
                                                                                │
│ ><EMAIL_ADDRESS>schema                                                                                │
│ > node ./data/getSchema                                                                                │
│                                                                                │
│ Fetching http://revproxy-service/api/v0/submission/getschema                                                                                │
│ Fetching http://revproxy-service/api/v0/submission/_dictionary/_all                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 2214 then retry http://revproxy-service/api/v0/submission/getschema                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 2922 then retry http://revproxy-service/api/v0/submission/_dictionary/_all                                                                                │
│ Retrying http://revproxy-service/api/v0/submission/getschema after sleep - 1                                                                                │
│ Re-fetching http://revproxy-service/api/v0/submission/getschema - retry no 1                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 4652 then retry http://revproxy-service/api/v0/submission/getschema                                                                                │
│ Retrying http://revproxy-service/api/v0/submission/_dictionary/_all after sleep - 1                                                                                │
│ Re-fetching http://revproxy-service/api/v0/submission/_dictionary/_all - retry no 1                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 4409 then retry http://revproxy-service/api/v0/submission/_dictionary/_all                                                                                │
│ Retrying http://revproxy-service/api/v0/submission/getschema after sleep - 2                                                                                │
│ Re-fetching http://revproxy-service/api/v0/submission/getschema - retry no 2                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 9668 then retry http://revproxy-service/api/v0/submission/getschema                                                                                │
│ Retrying http://revproxy-service/api/v0/submission/_dictionary/_all after sleep - 2                                                                                │
│ Re-fetching http://revproxy-service/api/v0/submission/_dictionary/_all - retry no 2                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 8286 then retry http://revproxy-service/api/v0/submission/_dictionary/_all                                                                                │
│ Retrying http://revproxy-service/api/v0/submission/_dictionary/_all after sleep - 3                                                                                │
│ Re-fetching http://revproxy-service/api/v0/submission/_dictionary/_all - retry no 3                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 16252 then retry http://revproxy-service/api/v0/submission/_dictionary/_all                                                                                │
│ Retrying http://revproxy-service/api/v0/submission/getschema after sleep - 3                                                                                │
│ Re-fetching http://revproxy-service/api/v0/submission/getschema - retry no 3                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 17910 then retry http://revproxy-service/api/v0/submission/getschema                                                                                │
│ Retrying http://revproxy-service/api/v0/submission/_dictionary/_all after sleep - 4                                                                                │
│ Re-fetching http://revproxy-service/api/v0/submission/_dictionary/_all - retry no 4                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 16509 then retry http://revproxy-service/api/v0/submission/_dictionary/_all                                                                                │
│ Retrying http://revproxy-service/api/v0/submission/getschema after sleep - 4                                                                                │
│ Re-fetching http://revproxy-service/api/v0/submission/getschema - retry no 4                                                                                │
│ failed fetch - non-200 from server: 502, sleeping 17043 then retry http://revproxy-service/api/v0/submission/getschema                                                                                │
│ Retrying http://revproxy-service/api/v0/submission/_dictionary/_all after sleep - 5                                                                                │
│ Re-fetching http://revproxy-service/api/v0/submission/_dictionary/_all - retry no 5                                                                                │
│ Error:  failed fetch non-200 from server: 502, max retries 4 exceeded for http://revproxy-service/api/v0/submission/_dictionary/_all                                                                               │
│ Stream closed EOF for default/portal-deployment-6c7f86d4f8-brqjn (portal)

I have solved problem by myself, I think I delete pvc and change values.yaml to persistent solved this issues, but not sure the reason for it.
delete pvc
kubectl delete pvc --all
change values.yaml to this?
global:
  dev: true
  hostname: localhost

# configuration for fence helm chart. You can add it for all our services.
fence:
  # Fence config overrides
  FENCE_CONFIG:
    OPENID_CONNECT:
      google:
        client_id: ""
        client_secret: ""

    AWS_CREDENTIALS:
      'fence-bot':
        aws_access_key_id: ''
        aws_secret_access_key: ''

    S3_BUCKETS:
      # Name of the actual s3 bucket
      jq-helm-testing:
        cred: 'fence-bot'
        region: us-east-1

    # This is important for data upload.
    DATA_UPLOAD_BUCKET: 'jq-helm-testing'

portal:
  image:
    repository: quay.io/cdis/data-portal-prebuilt
    tag: brh.data-commons.org-feat-pr_comment
  resources:
    requests:
      cpu: 0.2
      memory: 500Mi

postgresql:
  primary:
    persistence:
      enabled: true

Hello @scymz1
Thanks for reporting this issue.
I'll try to take a look into this today.
If deleting the PVC's helped, the issue might have been that your postgresql pod had gen3 users created from a previous deployment, and the new deployment will try to generate new credentials and you run into a mismatch of passwords. You should see that in the logs of the failing pods.

Hi @jawadqur I still got errors for deployment when I uninstalled and reinstalled using helm. Even through I delete pvc before reinstall.
My current values.yaml file:
global:
  dev: true
  hostname: localhost

# configuration for fence helm chart. You can add it for all our services.
fence:
  # Fence config overrides
  FENCE_CONFIG:
    OPENID_CONNECT:
      google:
        client_id: ""
        client_secret: ""

    AWS_CREDENTIALS:
      'fence-bot':
        aws_access_key_id: ''
        aws_secret_access_key: ''

    S3_BUCKETS:
      # Name of the actual s3 bucket
      jq-helm-testing:
        cred: 'fence-bot'
        region: us-east-1

    # This is important for data upload.
    DATA_UPLOAD_BUCKET: 'jq-helm-testing'

portal:
  image:
    repository: quay.io/cdis/data-portal-prebuilt
    tag: brh.data-commons.org-feat-pr_comment
  resources:
    requests:
      cpu: 0.2
      memory: 500Mi

postgresql:
  primary:
    persistence:
      enabled: true

Here is my logs:
get pods
NAME                                              READY   STATUS                       RESTARTS        AGE
portal-deployment-c9d6d9776-lb78f                 0/1     Pending                      0               20m
sower-85597bddbf-fdsm6                            0/1     Pending                      0               20m
fence-deployment-6f8489fb88-lxgt4                 0/1     Pending                      0               20m
hatchery-deployment-7fcb68fb65-zcg76              0/1     Pending                      0               20m
revproxy-deployment-9764957cd-djnh7               1/1     Running                      0               20m
gen3-postgresql-0                                 1/1     Running                      0               20m
wts-oidc-job-qhwbd                                0/2     Init:0/1                     0               20m
manifestservice-deployment-6c74479448-jmznd       1/1     Running                      0               20m
peregrine-dbcreate-rswdw                          0/1     Completed                    0               20m
arborist-dbcreate-78jvw                           0/1     Completed                    0               20m
metadata-dbcreate-zc8b7                           0/1     Completed                    0               20m
sheepdog-dbcreate-p55hq                           0/1     Completed                    0               20m
wts-dbcreate-2kvvs                                0/1     Completed                    0               20m
audit-dbcreate-g7l6q                              0/1     Completed                    0               20m
fence-dbcreate-rmbrw                              0/1     Completed                    0               20m
indexd-dbcreate-mfjmz                             0/1     Completed                    0               20m
gen3-elasticsearch-master-0                       1/1     Running                      0               20m
arborist-deployment-77645d555-pzl8v               1/1     Running                      0               20m
ambassador-deployment-6cd65d48d6-xm8db            1/1     Running                      0               20m
wts-deployment-57ff756898-55d4b                   0/1     CreateContainerConfigError   0               20m
indexd-deployment-b845d4565-cjcr9                 1/1     Running                      0               20m
metadata-deployment-559bbdd459-gm88s              1/1     Running                      0               20m
audit-deployment-54c96847c8-bv8g4                 1/1     Running                      0               20m
indexd-userdb-jtxx9                               0/1     Completed                    0               20m
presigned-url-fence-deployment-6d657f9cfd-bb45d   1/1     Running                      0               20m
argo-wrapper-deployment-85f5d4b756-ft7cb          0/1     ImagePullBackOff             0               20m
useryaml-qm2qn                                    0/1     CrashLoopBackOff             7 (2m37s ago)   20m
sheepdog-deployment-746959d756-fk2pz              0/1     CrashLoopBackOff             8 (114s ago)    20m
pidgin-deployment-b9c7c5b7d-rt86d                 0/1     Running                      5 (82s ago)     20m
peregrine-deployment-6d9b6b584b-jnsc6             0/1     Running                      5 (22s ago)     20m

For pod useryaml-qm2qn :
[notice] A new release of pip is available: 23.3.1 -> 24.0                                                                                │
│ [notice] To update, run: pip install --upgrade pip                                                                                │
│ [2024-04-02 15:22:25,537][gen3config.config][   INFO] Opening default configuration...                                                                                │
│ [2024-04-02 15:22:26,196][gen3config.config][   INFO] Applying configuration: /var/www/fence/fence-config.yaml                                                                                │
│ [2024-04-02 15:22:26,606][gen3config.config][WARNING] Did not provide key(s) dict_keys(['DB', 'DB_MIGRATION_POSTGRES_LOCK_KEY', 'SESSION_COOKIE_DOMAIN', 'GA4GH_DRS_POSTED_PASSPORT_FIELD', 'PRIVACY_POLICY_URL',  │
│ [2024-04-02 15:22:26,978][fence.config][   INFO] Found environment variable 'DB': overriding 'DB' field from config file                                                                                │
│ [2024-04-02 15:22:26,978][fence.config][   INFO] Found environment variable 'INDEXD_PASSWORD': overriding 'INDEXD_PASSWORD' field from config file                                                                 │
│ WARNING:flask_cors.core:Unknown option passed to Flask-CORS: headers                                                                                │
│ WARNING:flask_cors.core:Unknown option passed to Flask-CORS: headers                                                                                │
│ [2024-04-02 15:22:31,637][gen3config.config][   INFO] Opening default configuration...                                                                                │
│ [2024-04-02 15:22:32,292][gen3config.config][   INFO] Applying configuration: /var/www/fence/fence-config.yaml                                                                                │
│ [2024-04-02 15:22:32,705][gen3config.config][WARNING] Did not provide key(s) dict_keys(['DB', 'DB_MIGRATION_POSTGRES_LOCK_KEY', 'SESSION_COOKIE_DOMAIN', 'GA4GH_DRS_POSTED_PASSPORT_FIELD', 'PRIVACY_POLICY_URL',  │
│ [2024-04-02 15:22:33,077][fence.config][   INFO] Found environment variable 'DB': overriding 'DB' field from config file                                                                                │
│ [2024-04-02 15:22:33,077][fence.config][   INFO] Found environment variable 'INDEXD_PASSWORD': overriding 'INDEXD_PASSWORD' field from config file                                                                 │
│ ERROR:gen3users:Permission 'reader' in role 'reader' in policy 'open_data_reader' has 'service = *'. This is unsecure because policy 'open_data_reader' is granted to public group 'anonymous_policies'. Fix sugge │
│ ERROR:gen3users:Permission 'storage_reader' in role 'storage_reader' in policy 'open_data_reader' has 'service = *'. This is unsecure because policy 'open_data_reader' is granted to public group 'anonymous_poli │
│ ERROR:gen3users:Permission 'reader' in role 'reader' in policy 'full_open_access' has 'service = *'. This is unsecure because policy 'full_open_access' is granted to public group 'anonymous_policies'. Fix sugge │
│ ERROR:gen3users:Permission 'storage_reader' in role 'storage_reader' in policy 'full_open_access' has 'service = *'. This is unsecure because policy 'full_open_access' is granted to public group 'anonymous_poli │
│ ERROR:gen3users:Permission 'reader' in role 'reader' in policy 'open_data_reader' has 'service = *'. This is unsecure because policy 'open_data_reader' is granted to public group 'all_users_policies'. Fix sugge │
│ ERROR:gen3users:Permission 'storage_reader' in role 'storage_reader' in policy 'open_data_reader' has 'service = *'. This is unsecure because policy 'open_data_reader' is granted to public group 'all_users_poli │
│ ERROR:gen3users:Permission 'reader' in role 'reader' in policy 'authn_open_access' has 'service = *'. This is unsecure because policy 'authn_open_access' is granted to public group 'all_users_policies'. Fix sug │
│ ERROR:gen3users:Permission 'storage_reader' in role 'storage_reader' in policy 'authn_open_access' has 'service = *'. This is unsecure because policy 'authn_open_access' is granted to public group 'all_users_po │
│ [2024-04-02 15:22:33,610][user_syncer][  ERROR] user.yaml validation failed. See errors in previous logs.                                                                                │
│ [2024-04-02 15:22:33,610][user_syncer][  ERROR] aborting early                                                                                │
│ Traceback (most recent call last):                                                                                │
│   File "/usr/local/bin/fence-create", line 6, in <module>                                                                                │
│     sys.exit(main())            File "/fence/bin/fence_create.py", line 502, in main                                                                                │
│     sync_users(                                                                                │
│   File "/fence/fence/scripting/fence_create.py", line 510, in sync_users                                                                                │
│     syncer.sync()                                                                                │
│   File "/fence/fence/sync/sync_users.py", line 1515, in sync                                                                                │
│     self._sync(s)                                                                                │
│   File "/fence/fence/sync/sync_users.py", line 1577, in _sync                                                                                │
│     user_yaml = UserYAML.from_file(                                                                                │
│   File "/fence/fence/sync/sync_users.py", line 172, in from_file                                                                                │
│     validate_user_yaml(file_contents)  # run user.yaml validation tests                                                                                │
│   File "/usr/local/lib/python3.9/site-packages/gen3users/validation.py", line 58, in validate_user_yaml                                                                                │
│     raise AssertionError(                                                                                │
│ AssertionError: user.yaml validation failed. See errors in previous logs.

For pod gen3-postgresql-0:
postgresql 15:19:06.43 INFO  ==> ** Starting PostgreSQL **                                                                                │
│ 2024-04-02 15:19:06.491 GMT [1] LOG:  pgaudit extension initialized                                                                                │
│ 2024-04-02 15:19:06.602 GMT [1] LOG:  starting PostgreSQL 14.5 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit                                                                   │
│ 2024-04-02 15:19:06.608 GMT [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432                                                                                │
│ 2024-04-02 15:19:06.608 GMT [1] LOG:  listening on IPv6 address "::", port 5432                                                                                │
│ 2024-04-02 15:19:06.611 GMT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"                                                                                │
│ 2024-04-02 15:19:06.623 GMT [367] LOG:  database system was shut down at 2024-04-02 15:19:06 GMT                                                                                │
│ 2024-04-02 15:19:06.635 GMT [1] LOG:  database system is ready to accept connections                                                                                │
│ 2024-04-02 15:19:21.054 GMT [397] FATAL:  password authentication failed for user "peregrine_gen3"                                                                                │
│ 2024-04-02 15:19:21.054 GMT [397] DETAIL:  Role "peregrine_gen3" does not exist.                                                                                │
│     Connection matched pg_hba.conf line 1: "host     all             all             <IP_ADDRESS>/0               md5"                                                                                │
│ 2024-04-02 15:19:21.703 GMT [405] FATAL:  password authentication failed for user "sheepdog_gen3"                                                                                │
│ 2024-04-02 15:19:21.703 GMT [405] DETAIL:  Role "sheepdog_gen3" does not exist.                                                                                │
│     Connection matched pg_hba.conf line 1: "host     all             all             <IP_ADDRESS>/0               md5"                                                                                │
│ 2024-04-02 15:19:22.081 GMT [407] FATAL:  password authentication failed for user "metadata_gen3"                                                                                │
│ 2024-04-02 15:19:22.081 GMT [407] DETAIL:  Role "metadata_gen3" does not exist.                                                                                │
│     Connection matched pg_hba.conf line 1: "host     all             all             <IP_ADDRESS>/0               md5"                                                                                │
│ 2024-04-02 15:19:22.654 GMT [413] FATAL:  password authentication failed for user "gen3_arborist"                                                                                │
│ 2024-04-02 15:19:22.654 GMT [413] DETAIL:  Role "gen3_arborist" does not exist.                                                                                │
│     Connection matched pg_hba.conf line 1: "host     all             all             <IP_ADDRESS>/0               md5"                                                                                │
│ 2024-04-02 15:19:22.969 GMT [417] FATAL:  password authentication failed for user "wts_gen3"                                                                                │
│ 2024-04-02 15:19:22.969 GMT [417] DETAIL:  Role "wts_gen3" does not exist.                                                                                │
│     Connection matched pg_hba.conf line 1: "host     all             all             <IP_ADDRESS>/0               md5"                                                                                │
│ 2024-04-02 15:19:32.283 GMT [501] FATAL:  password authentication failed for user "audit_gen3"                                                                                │
│ 2024-04-02 15:19:32.283 GMT [501] DETAIL:  Role "audit_gen3" does not exist.                                                                                │
│     Connection matched pg_hba.conf line 1: "host     all             all             <IP_ADDRESS>/0               md5"                                                                                │
│ 2024-04-02 15:19:32.327 GMT [503] FATAL:  password authentication failed for user "indexd_gen3"                                                                                │
│ 2024-04-02 15:19:32.327 GMT [503] DETAIL:  Role "indexd_gen3" does not exist.                                                                                │
│     Connection matched pg_hba.conf line 1: "host     all             all             <IP_ADDRESS>/0               md5"                                                                                │
│ 2024-04-02 15:19:32.618 GMT [505] FATAL:  password authentication failed for user "fence_gen3"                                                                                │
│ 2024-04-02 15:19:32.618 GMT [505] DETAIL:  Role "fence_gen3" does not exist.                                                                                │
│     Connection matched pg_hba.conf line 1: "host     all             all             <IP_ADDRESS>/0               md5"                                                                                │
│ 2024-04-02 15:19:41.918 GMT [575] ERROR:  relation "db_version" does not exist at character 21                                                                                │
│ 2024-04-02 15:19:41.918 GMT [575] STATEMENT:  select version from db_version

for peregrine-deployment-6d9b6b584b-jnsc6
*** Python threads support is disabled. You can enable it with --enable-threads ***                                                                                │
│ Python main interpreter initialized at 0x4000172420                                                                                │
│ your server socket listen backlog is limited to 100 connections                                                                                │
│ your mercy for graceful operations on workers is 45 seconds                                                                                │
│ mapped 304776 bytes (297 KB) for 2 cores                                                                                │
│ *** Operational MODE: preforking ***                                                                                │
│ added /var/www/peregrine/ to pythonpath.                                                                                │
│ added /peregrine/ to pythonpath.                                                                                │
│ added /usr/local/lib/python3.6/site-packages/ to pythonpath.                                                                                │
│ failed to open python file /var/www/peregrine/wsgi.py                                                                                │
│ unable to load app 0 (mountpoint='') (callable not found or import error)                                                                                │
│ *** no app loaded. going in full dynamic mode ***                                                                                │
│ *** uWSGI is running in multiple interpreter mode ***                                                                                │
│ spawned uWSGI master process (pid: 2013)                                                                                │
│ spawned uWSGI worker 1 (pid: 2019, cores: 1)                                                                                │
│ spawned uWSGI worker 2 (pid: 2021, cores: 1)                                                                                │
│ --- no python application found, check your startup logs for errors ---                                                                                │
│ --- no python application found, check your startup logs for errors ---                                                                                │
│ --- no python application found, check your startup logs for errors ---                                                                                │
│ --- no python application found, check your startup logs for errors ---

For wts-deployment-57ff756898-55d4b:
stream logs failed container "wts" in pod "wts-deployment-57ff756898-55d4b" is waiting to start: CreateContainerConfigError for default/wts-deployment-57ff756898-55d4b (wts)

https://github.com/uc-cdis/gen3-helm/pull/164
I merged a fix for sheepdog / peregrine issues.
For the useryaml job you need to specify a valid user yaml in your fence configuration.


IE10 Clicking "Home" from Account Settings brings user to landing page

It doesn't log you out, but actually incorrectly loads the landing page. Refreshing the page correctly reloads the home page. Tested on production, and it wasn't working this way in 4.0

Not able to reproduce this at the moment using IE11 to emulate IE10, tried both development and staging environments. Moving this to 5.1 as it's not a critical bug.

Tested on production 5.0 and still could not replicate, maybe an Apache+Turbolinks bug? Closing!


Add {CRT}: {Cryptopia Token}

[x] I understand that token listing is not required to use the Polygon Wallet with a token.

Please provide the following information for your token.
Token Name: Cryptopia Token
Token Symbol: CRT
Decimals: 18
Polygon Address: 0x7348565F0A5077252D310392C3CeCD8dB87a7704
Ethereum Address: 0xABdD22dFE5Db2be20262050523470B650E91F246
Logo URI: https://cryptopia.com/images/icons/icon_CRT.png
Project Name: Cryptopia
Project Summary: Cryptopia is a ground-breaking blockchain-driven metaverse. Join a rising nation-state where you can build either a business empire or a successful profession. Stake and collect NFTs. Buy, sell, and earn using an integrated wallet. P2E is as easy as browsing the web!
Project Contact<EMAIL_ADDRESS>Project Website: https://www.cryptopia.com
Mainnet/Testnet: Mainnet
Additonal Notes:

Included in AllTokens v1.2.0.


Need further info on "printability.txt" file

Is it possible to share the "printability.txt" file and further info on this file?
What should be in this file?
Please share some detailed info on this file.

You could find it in https://github.com/tsm55555/adversarial-yolov5/blob/main/adversarial-yolo/non_printability/30values.txt.


How can i parser the log filed when i use the rancher logging (fluentd) to efk

Useful
Info

Versions
Rancher v2.1.0 UI: v2.0.77

Route
authenticated.cluster.index

+1

Being able to customize your logging is available in v2.2.2.
Please view step #4 in cluster logging: https://rancher.com/docs/rancher/v2.x/en/cluster-admin/tools/logging/#enabling-cluster-logging
Or step #4 in project logging: https://rancher.com/docs/rancher/v2.x/en/project-admin/tools/logging/#enabling-project-logging


Add Warning popup modal for Social Login buttons

Social login buttons have been added , but they're not functional yet.
Add an attractive popup modal that says Social logins are temporarily unavailable, please register using the registration form  until the social logins are made functional

I would like to work on this issue

Can I work on this issue

Since @akshatjain1004 came first i will assign it to her, @Omkar845 i will open issues and assign it to you

test comment

@sridhar-5 , example workflow is malfunctioning 👆🏻

@akshatjain1004 are you working on this ?

Alright


Remove all references to rdd in this project

rdd doesn't work with Spark Connect.
We want this entire project to work well for both Spark Connect and "legacy Spark".
Let's just remove all the rdd references.

#188 looks like this commit addresses all usages of rdd in the repo (besides the column_to_list benchmarking doc)


Add Terms of Use page

We need a Terms of Use page similar to OncoKB (https://www.oncokb.org/terms).

Refer to https://docs.google.com/document/d/1VOclqK74Zx9_AWqzFzKQY4j_2WRAPjaEGuxe8u8pQ_A/edit


[17.07] backport fix for removing diff path

backport fix:

moby/moby#34587 Fix error removing diff path

with cherry-pick of https://github.com/moby/moby/pull/34587/commits/276b44608b04f08bdf46ce7c816b1f744bf24b7d
$ git cherry-pick -s -x -Xsubtree=components/engine 276b446

no conflicts

Known test failures:
$ ./check_failures.sh https://jenkins.dockerproject.org/job/docker-ce-pr/133/consoleText
FOR: https://jenkins.dockerproject.org/job/docker-ce-pr/133/consoleText
Passed (thought would fail):

Failed (should fail)
DockerSuite.TestRmiContainerImageNotFound
DockerSuite.TestRmiImageIDForceWithRunningContainersAndMultipleTags
DockerSuite.TestRunAttachDetachFromInvalidFlag
DockerSuite.TestRunWithNanoCPUs
DockerSuite.TestUpdateWithNanoCPUs
DockerSwarmSuite.TestServiceLogs
DockerSwarmSuite.TestSwarmNetworkPluginV2
DockerSwarmSuite.TestSwarmServicePsMultipleServiceIDs


Release v0.77.7

Issue #, if available:
Description of changes:
Release a new version of cfn-lint to include #2757
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@kddejong hey! Wondering if we can release a new patch version of cfn-lint to have the bugfix


[Chat] Add e2e tests for image gallery for different themes

What

Add e2e tests for Image gallery on dark and light themes
Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

LGTM, just wondering why is there no inline-image-gallery-modal-light-mode.png included in this PR?

@jimchou-dev Light mode is handled in the original case. This is in addition to that


dang-1095 Icons Refresh

ref: Icons list sheet
Icons Storybook Demo link

Remove unused Icons
Replace existing Icons with the new design - matched by name
Add 3 new icons (Text, InfoFilled, & ToolTipIcon) as they are used in reskin designs

qq: I see a warning icon, but no error icon. Is that ok?


Ability for specify a chunk size based on size not count

Currently the chunk size is a count of items implementing SortType, but if SortType also had a Size() it could instead use that, which would be very useful! Otherwise great package! 👍

Hello @yonderblue,
I'm not sure I fully understand what you mean. The Config struct ChunkSize field is the number of SortType items to group together into a chunk on disk. There are expected to be many chunks, each containing up to ChunkSize SortType objects in them.
Since SortType represents a single sortable item, it would not know how many other items there are to sort, let alone how many should be consolidated into a chunk.

Hi @lanrat, please see the attached PR.

Closing this issue since the PR is also closed.


allow instance selection

Hey,
thanks a lot for this project. it makes my day. I was wondering, if it would be possible, to have a more precise metrics selection, like
dashboard/script/getdash.js?host=onehost.com,anotherhost.com&metric=interface&instance=eth0

so one could control a specific interface over all hosts.
and again, thanks!

Hi @einsiedlerkrebs,
I added initial implementation to the separate branch. It supports regex inputs too.
http://localhost:3000/dashboard/script/getdash.js?host=vagrant-ubuntu-precise-32&metric=disk&instance=sda1
http://localhost:3000/dashboard/script/getdash.js?host=vagrant-ubuntu-precise-32&metric=disk&instance=sd*
http://localhost:3000/dashboard/script/getdash.js?host=vagrant-ubuntu-precise-32&metric=disk&instance=sda[0-3]

Please test and let me know what you think.

Hey anryko,
that was fast. Yes, that is what I thought it should do. Thank you
eins.

Thanks for the nice idea @einsiedlerkrebs.
Merged to master.

Hey,
i am working on support for IRQ Plugin. The interrupts are numbers. cat /proc/interrupts. The problem is, that i have trouble with the regexing. When i have a interrupt "4" it matches "47" as well. Do you have a hint how to stop the regexing?
thanks.
eins

Hi @einsiedlerkrebs,
There should be no regexp match when you don't use any special characters. instance=4 is translated to regexp /^4$/ which should match only 4 and not 47. If you need multiple values but struggle to find exact regexp to match those you can use a list notation, like instance=4,6,13,101.
for the interrupt/minute graph you should use 'apply': 'derivative(1m)' in your plugin graph configuration. Check how it is described in the getdash repository README file (// collectd disk plugin configuration).

Heh, I think i understood your issue only after posting the answer :). You are actually asking about plugin configuration regexp and not GET instance request... let me think about it and do some tests.

yes. sorry, if i did not clearify this. and now i understood you answer! ;)

one way I can think of is to use exact regexp match
'graph': {
    '/^4$/': { 'apply': 'derivative(1m)' }
}

let me know if this helps :).

yes that helps. i thought i tried this.
cool. thanks it works.
I will see, if i can build the plugin in a bit more generic and will send you a pull request.
thanks for your help

you are welcome

Thanks again. #65


Ben first cutscene softlock

Seed: R420-CR46-XNTA3LYLL52

How did it softlock?

Ada was replaced by Rebecca and when she came into the scene, she was turned around and tried walking forward forever.

I've attached a short video. This is Leon A.
https://user-images.githubusercontent.com/121004014/208536850-0b6ecb4e-f784-44cd-8080-04a79dd527a8.mp4

NPC swap for Ada has been reverted for now. Eventually a better fix will go in.


 I f**k up at too many places whenever I want to contribute something :(

There are just too many commits in this PR (which will make the git history hard to browse) and too many changes unrelated to the PR.
Here's what you should do:

start from fchollet/master.
add LRN2D, MaxPooling with strides, ZeroPadding.
commit (you can do this in 3 commits, one per feature. One commit is fine too.), and create a PR.


Copy and paste commands from tutorial doesn't work

Screenshot

Description
At https://superset.apache.org/docs/installation/installing-superset-using-docker-compose the copy command button doesn't just copy the command, it also includes the leading $  character:
$ git clone https://github.com/apache/superset.git

Pasting this in a terminal then gives this error:
% $ git clone https://github.com/apache/superset.git
zsh: command not found: $

Is it possible to change that so that only the actual command is copied?
Or alternatively just remote the leading $ ?

@cdeil Hi. Thanks for your suggestion! You are right. We actually don't need $ symbol and the fact that we need to filter out this symbol when copying.

Fix in https://github.com/apache/superset/pull/20480.


Huffman in version 1.0

Hi,
While I'm working with your tools I get an error about not supporting Huffman compression. Mean if I set value 5 for -z switch I get bellow error.

But I don't have any problem for using this compression with version 0.9.3

Looks to be a regression from commit 8471fcb0c04b2bb41e568c9eb5d65502a6f52715, an old merge from dev branch.
The latest readme still incorrectly states that -z 5 (xpress huffman) is available.

Oooo... Yes! you are right... they don't support the "xpress huffman" in newer version...
Thank you for your answer. So they should update their readme...


Allow key from qs or path segment

Spike on https://github.com/dtomlinson91/traefik-api-key-middleware/issues/5 and https://github.com/dtomlinson91/traefik-api-key-middleware/issues/6

After some testing I'm not sure path segment check is a good idea. And it doesn't seem to work with stripprefix middleware.. so I've made https://github.com/dtomlinson91/traefik-api-key-middleware/pull/8 with only query string method and will close this.


Multi-line Quote/Unquote support

It seems the plugin does not support Add Quote for multi-line
For example, I have 2 lines
A
B

I want the result like the following
"A"
"B"

or
'A',
'B',

Do you select them using multicarets?

It works when I use multicarts!
Bug sometimes I have thousands of lines. I should hold alt and need to move many lines to put the cursor on the first line.


invalid start byte \ some kind of scrambled html

Traceback (most recent call last):
  File "articlestrip.py", line 23, in <module>
    line = f.readline()
  File "/home/infominer/.pyenv/versions/3.6.8/lib/python3.6/codecs.py", line 321, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte

index.zip
idk what that file is, but it borks the program, so I had to manually try each subfolder till I found the problem.

That HTML file doesn't contain any usable information. Open it up and have a look. I'll see if I can implement an exception catch to handle scenarios like this one.

Fixed in latest commit. Also cranked up details in console printing, so try to run the program again from your main directory and let me know how it goes, if everything is savvy, I'll close the issue.

Tested this a couple times myself. Appears to be working as intended.

yes looks really nice! I just ran it, and am remembering what the heck I was even doing, have a few download directories scattered around, hehe.
have a few more places to run it, but all looks good! :D

beautiful.


Create ReauthLimiter class to handle attempts and check.

This make it more reusable if you need to bundle this on other Laravel packages.
Signed-off-by: crynobone<EMAIL_ADDRESS>

[Current coverage][cc-pull] is 100%

No coverage report found for master at 14b8386.

Powered by Codecov. Last updated by [14b8386...130892f][cc-compare]
[cc-base-branch]: https://codecov.io/gh/mpociot/reauthenticate/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/mpociot/reauthenticate/compare/14b8386b458862afbd74931b2784b2da5208304c...130892f7f423c8cbaa62b15f907286950cf51005?src=pr
[cc-pull]: https://codecov.io/gh/mpociot/reauthenticate/pull/14?src=pr

Great addition - thank you! :)


bumped version to 1.0.1

#123
bumped version to 1.0.1
updated readme / pod and Carthage instructions to include the 1.0.1 version

Codecov Report

Merging #124 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #124   +/-   ##
=======================================
  Coverage   74.12%   74.12%
=======================================
  Files          30       30
  Lines        1422     1422
=======================================
  Hits         1054     1054
  Misses        368      368

Flag
Coverage Δ

#ios
74.12% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 400ad28...3ab3a7c. Read the comment docs.


name service ports to make it work with openshift routes

Issue desc:
So if you have a kubernetes service with unnamed port and when you create a route for this service on openshift, openshift gives you a warning in the web console saying

Service web has a single, unnamed port. A route cannot specifically target an unnamed service port. If more service ports are added later, the route will also direct traffic to them.

So what this means is that if you update the service later to have multiple ports and if they are unnamed, then route traffic will be sent to all of them.
Steps to reproduce:
$ kedge version
0.2.0 (0a0b9a9)

$ oc new-project foo
Now using project "foo" on server "https://<IP_ADDRESS>:8443".

You can add applications to this project with the 'new-app' command. For example, try:

    oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git

to build a new example application in Ruby.

$ kedge init --image centos/httpd --name web -p 80
file kedge.yml created

$ cat kedge.yml
name: web
containers:
- image: centos/httpd
services:
- ports:
  - port: 80

$ kedge create -f kedge.yml
service "web" created
deployment "web" created

$ minishift console
Opening the OpenShift Web console in the default browser...

Now goto the service web and click create route button. There in the form you will see this particular warning shown:

Service web has a single, unnamed port. A route cannot specifically target an unnamed service port. If more service ports are added later, the route will also direct traffic to them.

What is expected to happen
Name the service ports, just for being on the safe side.

This will become relevant when we add support for Routes.
related to #238

So, first I created a Service with the file -
name: web
containers:
- image: centos/httpd
services:
- ports:
  - port: 80

I exposed this service like -
$ oc expose service web --name=first
route "first" exposed
$ oc describe route first
Name:                   first
Namespace:              myproject
Created:                11 seconds ago
Labels:                 app=web
Annotations:            openshift.io/host.generated=true
Requested Host:         first-myproject.<IP_ADDRESS>.nip.io
                          exposed on router router 11 seconds ago
Path:                   <none>
TLS Termination:        <none>
Insecure Policy:        <none>
Endpoint Port:          80

Service:        web
Weight:         100 (100%)
Endpoints:      <IP_ADDRESS>:80

The endpoint port is 80.
I then add a service port like -
name: web
containers:
- image: centos/httpd
services:
- ports:
  - port: 80
  - port: 81

Then -
$ kedge apply -f test.yml
service "web" configured
deployment "web" configured

The route I created earlier continues to work since it's not bound to a Service Port name, but to the port number itself, 80 in this case.
I create a new route -
$ oc expose service web --name=second
route "second" exposed
$ oc describe route second
Name:                   second
Namespace:              myproject
Created:                6 seconds ago
Labels:                 app=web
Annotations:            openshift.io/host.generated=true
Requested Host:         second-myproject.<IP_ADDRESS>.nip.io
                          exposed on router router 6 seconds ago
Path:                   <none>
TLS Termination:        <none>
Insecure Policy:        <none>
Endpoint Port:          web-80

Service:        web
Weight:         100 (100%)
Endpoints:      <IP_ADDRESS>:80, <IP_ADDRESS>:81

This route also works fine, and the endpoint is the Service Port name this time (web-80)
The earlier route also continues to work fine and route traffic to endpoint port i.e. 80.
Maybe this is a quirk with the web console, but works as expected for me.
I don't see why should we be naming all the ports?

Endpoints:      <IP_ADDRESS>:80, <IP_ADDRESS>:81

@containscafeine ^^
The warning does not say it won't work!

Hmm, so why should we be populating all names?

Right now we are auto-generating name for ports when more than one port is given, if we are doing it for more than one port why should we even wait for that why not do it anyway be it one port or multiple port. What I am trying to imply here is that if one port is given is not a special case here that we should be checking.
In other places like this where we are doing similar checks is in case of container names, where we check if container is one then not giving name is ok but if more than one containers are provided and names are not given it is not ok and since there we do not generate names automatically so we fail there. In that case whether single item is given in list without name makes a speacial case that we need to test.
But here since we are not failing but auto-populating names I think checking for single port not having name does not make any sense at all, since it is not a special case anymore.
@containscafeine

Hmm, so why should we be populating all names?

A route cannot specifically target an unnamed service port. If more service ports are added later, the route will also direct traffic to them.

I think our behavior should be consistent with the way OpenShift deals with this.
If we add more service ports to OpenShift later on, then it routes traffic to all of them, so should we.
We should not be auto naming the first port and bind the route to that port, when OpenShift does not do that.

I don't understand where is the problem if we start naming ports from begging if name is not set.

@kadel @surajssd -

User specifies one unnamed service port:

In Kedge - The generated route will be bound with that service port name. On addition of subsequent service ports, the route will not direct traffic to the newer ports.
In OpenShift - The generated route will not be bound with that particular service port. On addition of subsequent ports, the route will direct traffic to newer ports.
IMO, Kedge is behaving differently than OpenShift for the same input, which is inconsistent :(

In Kedge - The generated route will be bound with that service port name. On addition of subsequent service ports, the route will not direct traffic to the newer ports.
In OpenShift - The generated route will not be bound with that particular service port. On addition of subsequent ports, the route will direct traffic to newer ports.

It depends on how you define Route/Ingress. Nothing to do if port is named or not.
Both cases can be set to behave either way.

@containscafeine I don't really see the problem in naming ports if the name is provided.

Okay, we can move ahead with one.
I don't agree completely, but I understand your point.
Yay :tada:


Font Rendering Issue

Describe the bug
Letters are not loading properly
To Reproduce
Steps to reproduce the behavior:

Open Recaf with an old low-end Laptop (2018-ish)
See error

Exception
If applicable, add the exception/stacktrace.
No exception, happens in every screen
Screenshots

Some ideas:

Try changing the font.

https://user-images.githubusercontent.com/21371686/218890501-128bdd23-999e-4f26-b67f-429ffd7d8aaa.mp4

Provide more system specs. Not much we can do aside from google the problem since its not something we've seen thus far on our systems.

I changed the font, still happens.
CPU	Intel(R) Celeron(R) CPU  N3060  @ 1.60GHz   1.60 GHz
RAM	4,00 GB
64 bits

Welp, guess its a JavaFX issue. Kinda prevents us from doing anything about it here at the Recaf level.
Its not something I've seen anyone encounter up until now. Unless you want to look into it more nothing I can really do about it.

Forgot to add, the file names and decompiled classes (when you decompile a jar), don't appear to have the bug.

Then try to change the UI font to the one listed as the monospaced font in the video.

I did, still happens


[WIP] Feature/#2 accelerometer

Import files from Bosch BMA4 library.
Prototypes that shows step counter and sensor temperature on screen
Fixes #48
TODO:

[ ] Implement interrupt features from sensor

@endian-albin  If you wanna try on your watch.
This version is the minimum implementation. There is no interrupts/power management and other special features.
But you can already show step count on screen.

I understand that this is a work-in-progress branch, but rather than restoring the state with 7baaf2a6275cec7f5c4da19c0f36d0009621f8bf ("Remove mess from dts"), it's better to delete the commit that introduced the change in the first place.

drivers/sensor/bma421/bma421_config.h is a binary blob, unfortunately, and can thus not be used in this project, especially not without a clearly defined origin and permission to use it. It would also be impossible to upstream it.
We discussed the accelerometer in the Matrix chat today and it was mentioned that a lot of things can be done without the so-called "configuration", but not step counting for example.

drivers/sensor/bma421/bma421_config.h is a binary blob, unfortunately, and can thus not be used in this project, especially not without a clearly defined origin and permission to use it. It would also be impossible to upstream it.
We discussed the accelerometer in the PineTime Matrix chat today and it was mentioned that a lot of things can be done without the so-called "configuration", but not step counting for example.

Alright..
Boshc is not helping much on that topic but this blob is documented in the Sensor API Application note.
https://www.bosch-sensortec.com/media/boschsensortec/downloads/application_notes_1/bst-mas-an032-00.pdf
So I will write MY own blob, with credit on my name and give that to the project. All nicely documented.. Would that be okay to have that config file here then ?

I’m no lawyer, but if you could somehow, without violating copyright law, write a documented application that generates the blob, then it should be OK I think. Such a tool would also be beneficial to the other PineTime projects by the way. Using information that’s been made available without violating an NDA that you’ve signed yourself or stealing should be fine a I think. Thanks again for your efforts!

It's really cool that you've made the accelerometer work this well. It needs to be cleaned up a bit, both to conform with the coding style and to make each commit meaningful (you can use interactive rebase to fix the latter). In addition, I'd like this to be interrupt driven before merging. Right now, the step counter gets disabled if you switch between BT mode on or off. I'd be happy to have a look again after you've worked on this a bit more.

I don't get The step counter is disabled when we disable/enable BLE..
I. tried to generate a new config blob. Could you try on your side if that step counter still work for you as well ?

It's really cool that you've made the accelerometer work this well. It needs to be cleaned up a bit, both to conform with the coding style and to make each commit meaningful (you can use interactive rebase to fix the latter). In addition, I'd like this to be interrupt driven before merging. Right now, the step counter gets disabled if you switch between BT mode on or off. I'd be happy to have a look again after you've worked on this a bit more.

I don't get The step counter is disabled when we disable/enable BLE..

The physical button toggles BLE advertising (and switches between two different threads. When I tested your code the last time, step counting always worked in the initial state, before BLE had been enabled by pressing the button, but it stopped incrementing the counter after pressing it.

I. tried to generate a new config blob. Could you try on your side if that step counter still work for you as well ?

No, it always stays at 0 unfortunately. The temperature value varies though.
There were a lot of merge conflicts that I had to resolve. Then I managed to build with this single warning:
pinetime/drivers/sensor/bma421/bma421.c:81:13: warning: 'bma421_channel_accel_convert' defined but not used [-Wunused-function].

I've now tested two commits a couple of times. Checking out, building and flashing "Add custom config blob" gives me a constant 0 steps. When I do the same with "Make code Zephyr compliant", i.e. the commit just before, steps are incremented, but I can't say if they are accurate or not. I did a hard reset after programming each time (I've added a physical on/off switch to the watch).

Okay. that is what I feared:
The first 70 bytes of the configuration are documented. Because those are all the parameters necessary to fine tune all the features.
The 5000+ following bytes would then be the initialization sequence of the internal ASIC and I guess provided by Bosch Sensor Tech directly..
Is that really impossible to use a blob ?
I mean, we could directly use it from the external repo where I found it ?
Or I could create a repo or a gist putting the right credit and license on it ?
(it was retro-engineering, so there is no NDA on that..)
If you think there is no solution to get that blob in this FW, I'll make you a simple accelerometer driver.. but I really don't like the idea of computing steps directly on the main uC.

Okay. that is what I feared:
The first 70 bytes of the configuration are documented. Because those are all the parameters necessary to fine tune all the features.

I see. Would these still be useful if we excluded the undocumented bytes?

The 5000+ following bytes would then be the initialization sequence of the internal ASIC and I guess provided by Bosch Sensor Tech directly..

Right, so it's a plain blob used to obscure how the hardware works.

Is that really impossible to use a blob ?
I mean, we could directly use it from the external repo where I found it ?
Or I could create a repo or a gist putting the right credit and license on it ?
(it was retro-engineering, so there is no NDA on that..)

There are two reasons why I don't want blobs in this project: 1) for philosophical reasons (I'm a Free Software supporter); 2) I want to work with upstream projects and eventually mainline all the out-of-tree drivers. I doubt blobs can be sent to upstream Zephyr.

If you think there is no solution to get that blob in this FW, I'll make you a simple accelerometer driver.. but I really don't like the idea of computing steps directly on the main uC.

How about dropping the steps counter feature for now and focus on other acceleration features? It was mentioned in the Matrix chat that a lift-to-wake (light up the display) feature could be developed using timer interrupts every 100 ms or so that checks the XYZ values. Apparently, there is no explicit hardware support available for such a feature and so the implementation would need to be done this way anyway. Personally, I don't care about a step counter, but it would be really nice if the screen lights up by itself exactly when you want to look at it. I'm sure there are other features beside this that could be implemented without the blob. What do you think?

See also this open issue about binary blobs in the upstream Zephyr project.

More discussion took place on the PineTime chat tonight. The BMA421 blob used is apparently not under the BSD-3-Clause license but under a very restrictive license that we can certainly not redistribute. The author of the ATC1441 firmware also mentioned that he had rewritten the accelerometer library from scratch and integrated it directly with his Arduino-based project.


Max slave number

I'm making an AIO board including ESP8266 as master and Atmega328p as slave. I wonder the max number of slave is 10 in README or can be higher?  If it's more than 10, it would be better. :)

You could change the define.
#define CLIENTS 10

And set to another number, but I don't know if the ESP8266 can handle too many devices at the same time.

Got it, I'll try. Thanks :)


No way to prevent angular-cli from removing license info from minified JS

I believe this is a bug, although it's also possible that I've misunderstood the intended current behaviour and that this is in fact a feature request.
According to @IgorMinar in this comment:

It is customary to preserve licensing information in application bundles in the form of js comments marked with @license js doc and that's what Angular CLI does. We currently don't offer a way to omit the inclusion of these headers in the application bundles.

This is not the behaviour I am observing however. When I run ng build --prod using Angular CLI version 8.3.6, all third party license info is removed from the resulting minified JavaScript bundles and placed in 3rdpartylicenses.txt.
If I run the same command with --extractLicenses=false, the license info is still removed, but 3rdpartylicenses.txt is not created.
There doesn't seem to be any way to prevent Angular CLI from removing this license information from the JS that I am going to be serving in my application.

@IgorMinar - FYI - Currently with extractLicenses=false we drop licences from both bundles and 3rdpartylicenses.txt

We decided that the behavior when extractLicenses is set to false - is to leave the license headers in the JS bundle.


Add LaneLayer to layers module

Make it easier to draw lane markers:

Double lines with separate color/dashed array
Compound dashed array ([dash, gap, dash, gap])
Better dash stacking (per-path instead of per-segment)

See layer README in this PR.

@ibgreen @tsherif The v7.3 PathLayer has 14 attributes (among which 4 positions + 4 64xyLow positions) and this layer has 15. :(

There's some room to pack attributes, e.g. these 4 vec2s could become 2 vec4s: https://github.com/uber/deck.gl/blob/master/modules/layers/src/path-layer/path-layer-vertex.glsl.js#L31-L34
If many of them are generally constant, we could also consider a system to dynamically switch constant attributes to uniforms.

The vec2s will become vec3s in v8, once we support 3d 64-bit positions.
The most promising route of reducing attributes is if we can split the joint calculation into a separate render pass.


fix(easing): changed duration & easing to match ff

:tada: This PR is included in version 1.1.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Failing test

Hi,
When building prometheus 1.1.1 for Debian, I have one test failing:
=== RUN   TestTargetSetRecreatesTargetGroupsEveryRun
time="2016-09-08T09:01:12Z" level=error msg="Error refreshing DNS targets: could
 not resolve srv.name.one.example.org: No server responded" source="dns.go:118"
--- FAIL: TestTargetSetRecreatesTargetGroupsEveryRun (5.00s)
        targetmanager_test.go:36: 'dns/0/srv.name.one.example.org' should be present in TargetSet.tgroups: map[]

FAIL
exit status 1
FAIL    github.com/prometheus/prometheus/retrieval      8.587s

I don't know if this is really trying to access the network or not. In any case, it is a problem: Debian builds are forbidden from trying to access the network at all.
This is running with golang 1.7

Perhaps the test wants the negative response from the network that srv.name.one.example.org doesn't exist.
And yes, that's something we should avoid.

@dmilstein it seems you added that test. Do you have time to rewrite it to not depend on a internet connection / working DNS discovery?

Drat, didn't realize it was actually resolving. Yep, I'll take a look and fix that.
Sorry about that,
D
iPhone brevity in effect

On Sep 8, 2016, at 4:02 PM, Tobias Schmidt<EMAIL_ADDRESS>wrote:
@dmilstein it seems you added that test. Do you have time to rewrite it to not depend on a internet connection / working DNS discovery?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Fixed with #1966


feat: skip unrecognizable commits

skip unrecognizable commits, previously merge commits or commits that don't follow the message format caused an exception.

@Salzig does this occur in old Git versions? I mean, why the git command doesn't ignore this commits?

no, also happens with git 2.7.0. The problem is that git not only grep the subject, but also the body. Which matches the commit message in the body of the merge commit.
I could try to change the regex greping the git log, or we just handle the case where we can't parse the comment, which could happen for different reasons.

Oh ok, nice to know, thanks!

could you build a new release?

Yea sure... done :)

awesome, thanks a lot!


I have a question about Only explicitly refer to self when required.

I have a question about Only explicitly refer to self when required.
If you implement UIViewController class, write view or edgesForExtendedLayout... about parent class's properties and methods?
class ViewController: UIViewController {

    let label = UILabel()

    override func viewDidLoad() {
        super.viewDidLoad()
        view.backgroundColor = UIColor.blueColor()
        edgesForExtendedLayout = .None
        configure()
    }

    func configure() {
        view.addSubview(label)
    }
}

Sorry, I understand.
I see firefox


Creating scenario for replicator via CRD with Connect image and Replicator Monitoring Extension [skip secret scan]

Creating scenario for replicator via CRD with Connect image and Replicator Monitoring Extension

@rohit2b , can you check this one out please?


Facing problem while binding Payloads (recompile)

Information

Apktool Version (apktool -version) - 2.6.1
Operating System (Mac, Linux, Windows) - Nethunter
APK From? (Playstore, ROM, Other) -FbLite.apk from apkpure

Stacktrace/Logcat

Using APK template: /sdcard/fb.apk
[-] No platform was selected, choosing Msf::Module::Platform::Android from the payload
[-] No arch selected, selecting arch: dalvik from the payload
[] Creating signing key and keystore..
[] Decompiling original APK..
[] Decompiling payload APK..
[] Locating hook point..
[] Adding payload as package com.facebook.lite.gjvak
[] Loading /tmp/d20220314-29626-1xsp3wf/original/smali/com/facebook/lite/ClientApplicationSplittedShell.smali and injecting payload..
[] Poisoning the manifest with meterpreter permissions..
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[*] Rebuilding apk with meterpreter injection as /tmp/d20220314-29626-1xsp3wf/output.apk
[-] I: Using Apktool 2.6.1
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Checking whether resources has changed...
I: Building resources...
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 132): [/tmp/brut_util_Jar_69221135822979910956479523302603090470.tmp, p, --forced-package-id, 127, --min-sdk-version, 15, --target-sdk-version, 31, --version-code, 354975467, --version-name, 2<IP_ADDRESS>.114, --no-version-vectors, -F, /tmp/APKTOOL5540271027132335925.tmp, -e, /tmp/APKTOOL3082563400059542143.tmp, -0, arsc, -I, /home/kali/.local/share/apktool/framework/1.apk, -S, /tmp/d20220314-29626-1xsp3wf/original/res, -M, /tmp/d20220314-29626-1xsp3wf/original/AndroidManifest.xml]
Error: Unable to rebuild apk with apktool
Steps to Reproduce

apktool

Frameworks
If this APK is from an OEM ROM (Samsung, HTC, LG). Please attach framework files
(.apks that live in /system/framework or /system/priv-app)
APK
If this APK can be freely shared, please upload/attach a link to it.
Questions to ask before submission

Have you tried apktool d, apktool b without changing anything? Yes
If you are trying to install a modified apk, did you resign it?
Are you using the latest apktool version?
Yes

Status code 132 is commonly an architecture issue when running the native binaries. It could be 32 vs 64 bit as well.
Closing.


Acting strange

Before submitting your issue, please make sure that you've checked all of the checkboxes below.

[x] You're running the latest release version of Deployer.
[x] Ensure that you're running at least PHP 5.5.9, you can check this by running php -v
[x] You've ran composer install --no-dev from the root of your installation.
[x] You've ran npm install --production from the root of your installation.
[x] You've ran rm -rf bootstrap/cache/* from the root of your installation.
[ ] You have restarted the queue listener and node socket server.

To help us better understand your issue, please answer the following.
Expected behaviour
Deployment should be done from top to bottom
Actual behaviour
below pic explains it better

and sometimes first it displays success message with Deployment finished then after few seconds, it displays another message saying Deployment failed.
Steps to reproduce
If your issue requires any specific steps to reproduce, please outline them here.
Environment info
Operating System:
PHP Version:
Node Version:
Database System:
Database Version:
Logs (see storage/logs/) or other output that would be helpful
(If logs are large, please upload as attachment).

Ah, I thought I'd caught this. It is nothing to worry about, the deployment is done in order but occasionally the browser doesn't receive the event to update the UI for the running task

I am seeing this more and more for beanstalkd compared to redis
it happens like this

all steps top to bottom finished
displays deployment finished message at bottom
suddenly some step like a custom defined will pick up
again it displays deployment finished message at bottom

and i get 2-3 slack notifications

Hmm, it sounds almost like the jobs are being put make into the queue. What is your supervisor config like?
Stephen Ball
<EMAIL_ADDRESS>
On 4 Jun 2016, at 14:34, lorvent<EMAIL_ADDRESS>wrote:
I am seeing this more and more for beanstalkd compared to redis
it happens like this
all steps top to bottom finished
displays deployment finished message at bottom
suddenly some step like a custom defined will pick up
again it displays deployment finished message at bottom
and i get 2-3 slack notifications
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

its like in docs
$ cat /etc/supervisor/supervisord.conf produces
; supervisor config file

[unix_http_server]
file=/var/run/supervisor.sock   ; (the path to the socket file)
chmod=0700                       ; sockef file mode (default 0700)

[supervisord]
logfile=/var/log/supervisor/supervisord.log ; (main log file;default $CWD/supervisord.log)
pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
childlogdir=/var/log/supervisor            ; ('AUTO' child log dir, default $TEMP)

; the below section must remain in the config file for RPC
; (supervisorctl/web interface) to work, additional interfaces may be
; added by defining them in separate rpcinterface: sections
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface

[supervisorctl]
serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL  for a unix socket

; The [include] section can just contain the "files" setting.  This
; setting can list multiple files (separated by whitespace or
; newlines).  It can also contain wildcards.  The filenames are
; interpreted as relative to this file.  Included files *cannot*
; include files themselves.

[include]
files = /etc/supervisor/conf.d/*.conf

[program:deployer]
command=php artisan queue:work --queue=deployer-high,deployer-low --sleep=3 --tries=1 --daemon
directory=/var/www/html/deploy
process_name=queue_%(process_num)s
numprocs=3
numprocs_start=0
stdout_logfile=/var/www/html/deploy/storage/logs/supervisord-%(process_num)s-stdout.log
stderr_logfile=/var/www/html/deploy/storage/logs/supervisord-%(process_num)s-stderr.log
stderr_logfile_maxbytes=1MB
stdout_logfile_maxbytes=1MB
redirect_stderr=true
autostart=true
autorestart=true

[program:deployer-socketio]
command=node socket.js
directory=/var/www/html/deploy
numprocs=1
autostart=true
autorestart=true
environment=NODE_ENV=production
stderr_logfile=/var/www/html/deploy/storage/logs/node-stderr.log
stdout_logfile=/var/www/html/deploy/storage/logs/node-stdout.log
stderr_logfile_maxbytes=1MB
stdout_logfile_maxbytes=1MB

[program:deployer-broadcast]
command=php artisan queue:work --queue=deployer-default --sleep=3 --tries=1 --daemon
directory=/var/www/html/deploy
numprocs=1
stderr_logfile=/var/www/html/deploy/storage/logs/broadcast-stderr.log
stdout_logfile=/var/www/html/deploy/storage/logs/broadcast-stdout.log
stderr_logfile_maxbytes=1MB
stdout_logfile_maxbytes=1MB
redirect_stderr=true
autostart=true
autorestart=true

Interesting. Looking into it but it might take a while to figure out. All the queue stuff if handled by laravel so there shouldn't be any difference between the 2 unless there is a bug in laravel

Yep getting the same thing when using redis, very odd

https://github.com/laravel/framework/issues/8577 hmm, looks like it could be an issue

It seems like it is an issue with Laravel, which may be fixed in 5.3.

yeah...looks like a bug with laravel itself for ages.


Add DNF module management

On EL8 and Fedora DNF can manage modules. This is a method of providing multiple versions on the same OS. Only one DNF module can be active at the same time.

I am running this on my own server and there it appears to work well.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

fwiw, when investigating Server-2500 and a workaround which was added for this issue in the PuppetDB and Puppetserver acceptance tests I found this pr. I was able to apply the changes here to my test setup and they resolved this issue we were seeing on RHEL-8. I don't have a good sense of what else might be impacted by these changes but once some flavor of this is merged we should be able to update the puppetlabs-puppetdb module to pick up this fix.

Thanks @ekohl for your contribution as always.


Continue Work on Neural Network, and Update Main Branch README to Comply

Finished implementation, moving to testing phase

Actually closing this time, implementation complete