chore: update examples for v13

Please describe the changes this PR makes and why it should be merged:
This PR updates examples for Discord.js v13. Additionally, it fixes a documentation error.
Closes #170.
Status and versioning classification:

This PR only includes non-code changes, like changes to documentation, README, etc.

@Fyko could you remove the unnecessary intent mentioned above and also move command deployment to its own script that can be run separately?

Why it's not getting merged?


edtlib: Apply Werror to address mismatches

When running gen_defines.py with --edtlib-Werror, this change causes address mismatches to be treated as errors.
For now, this change will fail in CI due to preexisting, so far not discovered/cleaned up issues.
This PR can (should) be merged only once the following command does not yield any issue anymore:
twister --cmake-only

Current (v3.7.0-5004-ga2f2dc9ad11) result:
- 19453 of 74544 test configurations passed (98.88%), 0 built (not run), 0 failed, 220 errored, 54871 skipped with 0 warnings in 8176.27 seconds

The following issues have been identified as blockers for this PR:

[ ] #72273
[ ] #78251

If anyone knows another way to resolve/work around those issues, please let me know.
Already resolved blockers:

[x] #78437
[x] #78438
[x] #78439
[x] #78440
[x] #78441
[x] #78442
[x] #78443
[x] #78444
[x] #78445
[x] #78446
[x] #78447
[x] #78451
[x] #78452

@rettichschnidi  can you rebase so that we see where CI is that on this one?

@rettichschnidi can you rebase so that we see where CI is that on this one?

Just done. Will run twister --cmake-only locally and report back once I am again sitting at a powerful machine.

@kartben Just updated the initial issue description.

@rettichschnidi are we now out of blockers, potentially? :)


Shopify theme list command to find exact match by theme name

What area(s) will this request affect?
Theme
What type of change do you want to see?
New feature
Overview
Example shopify theme list --environment='development_eu' --name="dev" --json currently outputs:
[
  {
    "id":<PHONE_NUMBER>43,
    "name": "dev",
    "processing": false,
    "createdAtRuntime": false,
    "role": "unpublished"
  },
  {
    "id":<PHONE_NUMBER>19,
    "name": "dev",
    "processing": false,
    "createdAtRuntime": false,
    "role": "unpublished"
  },
  {
    "id":<PHONE_NUMBER>31,
    "name": "Development (a0ffa7-MacBook-Pro-2)",
    "processing": false,
    "createdAtRuntime": false,
    "role": "development"
  },
  {
    "id":<PHONE_NUMBER>39,
    "name": "Development (229622-Andrews-MacBook-Pro)",
    "processing": false,
    "createdAtRuntime": false,
    "role": "development"
  }
]

It would be nice to have a flag that looks for an exact match such that the output returns
[
  {
    "id":<PHONE_NUMBER>43,
    "name": "dev",
    "processing": false,
    "createdAtRuntime": false,
    "role": "unpublished"
  }
]

Motivation
The above impacts our CI/CD pipeline to view preview links from main against dev due to the multiple matches from the list command above.

Hey @Jay-Plumb
Could you clarify what you have in mind to determine whether to return<PHONE_NUMBER>19 or<PHONE_NUMBER>43 in the example you provided?
Would specifying the theme ID via the --theme flag, or using a unique name work for your use case?

Hey @Jay-Plumb
Could you clarify what you have in mind to determine whether to return<PHONE_NUMBER>19 or<PHONE_NUMBER>43 in the example you provided?
Would specifying the theme ID via the --theme flag, or using a unique name work for your use case?

Thanks for the suggestion! I'll share this with the team to see if this is something we have the bandwidth to build
Not sure about the specifics of your workflow, but an idea I have for the meantime is to avoid conflicts with your development theme by using a different namespace such as preview
I understand that the workaround is imperfect. Feel free to share more about your workflow as well if you'd like us to see if there are any other workarounds or existing features that could address your problem :)


Saving networks fails for large gene numbers

This was reported by @speromelior. Evidence view can generate networks for many genes, in this case it was 44 wheat genes. Save Knetwork request fails. Console error shows the network API has a upper limit of 256 char for gene field. We should increase this to maybe 10,000 or so? I guess this needs to be changed in knetspace.
POST error: {"readyState":4,"responseText":"{\"gene\":[\"Ensure this field has no more than 256 characters.\"]}","responseJSON":{"gene":["Ensure this field has no more than 256 characters."]},"status":400,"statusText":"Bad Request"}

Is a knetspace bug (character limit in postgresDB). fixed in codebase now, yet to add fix/patch in live knetspace

will update here when this is fixed in our internal test knetspace and live knetspace's postgres DB's

Same issue exists for any network where the gene or keyword fields exceed 256 characters.

This has been patched now on the production knetspace and also fixed in the latest code.


Add all_nano option to the device parameter in the base conftest

Codecov Report
Patch coverage: 83.33% and project coverage change: +0.20 :tada:

Comparison is base (1b4f6bd) 74.70% compared to head (a54bf7f) 74.90%.

:exclamation: Current head a54bf7f differs from pull request most recent head d4f58e8. Consider uploading reports for the commit d4f58e8 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #143      +/-   ##
==========================================
+ Coverage   74.70%   74.90%   +0.20%
==========================================
  Files          34       34
  Lines        1609     1606       -3
==========================================
+ Hits         1202     1203       +1
+ Misses        407      403       -4

Impacted Files
Coverage Δ

src/ragger/conftest/base_conftest.py
76.74% <83.33%> (+2.50%)
:arrow_up:

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


[Bug] Replacing npm - database is always blank

Current Behavior
I have a working version of npm. Every time i try to replace the image with this one, it seems like the database it not being read properly. It resets completely, and i have to login with<EMAIL_ADDRESS>Expected Behavior
drop-in replacement
Steps To Reproduce
No response
Environment

OS: Ubuntu 22.04

Container creation
    version: '3.7'
    services:
      nginx:
        #    privileged: true
        restart: always
        environment:
          - TZ=Europe/London
        #      - PUID=0
        #      - PGID=0
        hostname: 'nginx'
        container_name: nginx
        #image: 'jc21/nginx-proxy-manager:latest'
        image: 'lepresidente/nginx-proxy-manager:latest'
        ports:
          - '80:80'
          - '81'
          - '443:443'
          - '8181:8181'
        volumes:
          - ./static-files:/static
          - ./data:/data
          - ./letsencrypt:/etc/letsencrypt
          - /var/log/nginx-proxy-manager:/data/logs

Container log
nginx-test  | [init        ] container is starting...
nginx-test  | [cont-env    ] loading container environment variables...
nginx-test  | [cont-env    ] APP_NAME: loading...
nginx-test  | [cont-env    ] APP_VERSION: loading...
nginx-test  | [cont-env    ] DOCKER_IMAGE_PLATFORM: loading...
nginx-test  | [cont-env    ] DOCKER_IMAGE_VERSION: loading...
nginx-test  | [cont-env    ] HOME: loading...
nginx-test  | [cont-env    ] TAKE_CONFIG_OWNERSHIP: loading...
nginx-test  | [cont-env    ] XDG_CACHE_HOME: loading...
nginx-test  | [cont-env    ] XDG_CONFIG_HOME: loading...
nginx-test  | [cont-env    ] XDG_DATA_HOME: loading...
nginx-test  | [cont-env    ] XDG_RUNTIME_DIR: loading...
nginx-test  | [cont-env    ] XDG_STATE_HOME: loading...
nginx-test  | [cont-env    ] container environment variables initialized.
nginx-test  | [cont-secrets] loading container secrets...
nginx-test  | [cont-secrets] container secrets loaded.
nginx-test  | [cont-init   ] executing container initialization scripts...
nginx-test  | [cont-init   ] 10-check-app-niceness.sh: executing...
nginx-test  | [cont-init   ] 10-check-app-niceness.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-clean-logmonitor-states.sh: executing...
nginx-test  | [cont-init   ] 10-clean-logmonitor-states.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-clean-tmp-dir.sh: executing...
nginx-test  | [cont-init   ] 10-clean-tmp-dir.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-init-users.sh: executing...
nginx-test  | [cont-init   ] 10-init-users.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-pkgs-mirror.sh: executing...
nginx-test  | [cont-init   ] 10-pkgs-mirror.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-set-tmp-dir-perms.sh: executing...
nginx-test  | [cont-init   ] 10-set-tmp-dir-perms.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-xdg-runtime-dir.sh: executing...
nginx-test  | [cont-init   ] 10-xdg-runtime-dir.sh: terminated successfully.
nginx-test  | [cont-init   ] 15-install-pkgs.sh: executing...
nginx-test  | [cont-init   ] 15-install-pkgs.sh: terminated successfully.
nginx-test  | [cont-init   ] 54-db-upgrade.sh: executing...
nginx-test  | [cont-init   ] 54-db-upgrade.sh: terminated successfully.
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: executing...
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: Enabling IPV6 in hosts in: /etc/nginx/conf.d
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/ssl-ciphers.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/proxy.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/block-exploits.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/assets.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/log.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/force-ssl.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/default.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/production.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/crowdsec_openresty.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: Enabling IPV6 in hosts in: /config/nginx
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /config/nginx/ip_ranges.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /config/nginx/resolvers.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: terminated successfully.
nginx-test  | [cont-init   ] 85-take-config-ownership.sh: executing...
nginx-test  | [cont-init   ] 85-take-config-ownership.sh: terminated successfully.
nginx-test  | [cont-init   ] 89-info.sh: executing...
nginx-test  |     ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
nginx-test  |     │                                                                      │
nginx-test  |     │ Application:           Nginx Proxy Manager                           │
nginx-test  |     │ Application Version:   2.11.3                                        │
nginx-test  |     │ Docker Image Version:  n/a                                           │
nginx-test  |     │ Docker Image Platform: linux/amd64                                   │
nginx-test  |     │                                                                      │
nginx-test  |     ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
nginx-test  | [cont-init   ] 89-info.sh: terminated successfully.
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: executing...
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: Deploy Crowdsec Openresty Bouncer..
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: Deploy new crowdsec-openresty-bouncer.conf ..
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: Deploy Crowdsec Templates ..
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: terminated successfully.
nginx-test  | [cont-init   ] all container initialization scripts executed.
nginx-test  | [init        ] giving control to process supervisor.
nginx-test  | [supervisor  ] loading services...
nginx-test  | [supervisor  ] loading service 'default'...
nginx-test  | [supervisor  ] loading service 'logmonitor'...
nginx-test  | [supervisor  ] service 'logmonitor' is disabled.
nginx-test  | [supervisor  ] loading service 'app'...
nginx-test  | [supervisor  ] loading service 'nginx'...
nginx-test  | [supervisor  ] loading service 'logrotate'...
nginx-test  | [supervisor  ] service 'logrotate' is disabled.
nginx-test  | [supervisor  ] loading service 'cert_cleanup'...
nginx-test  | [supervisor  ] all services loaded.
nginx-test  | [supervisor  ] starting services...
nginx-test  | [supervisor  ] starting service 'nginx'...
nginx-test  | [nginx       ] nginx: [alert] [lua] init_by_lua:9: [Crowdsec] Bouncer Disabled
nginx-test  | [supervisor  ] starting service 'app'...
nginx-test  | [app         ] [11/16/2024] [7:15:50 AM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
nginx-test  | [app         ] [11/16/2024] [7:15:50 AM] [Global   ] › ℹ  info      Creating a new JWT key pair...
nginx-test  | [supervisor  ] all services started.
nginx-test  | [cert_cleanup] ----------------------------------------------------------
nginx-test  | [cert_cleanup] Let's Encrypt certificates cleanup - 2024/11/16 07:15:50
nginx-test  | [cert_cleanup] ----------------------------------------------------------
nginx-test  | [cert_cleanup] 0 file(s) kept.
nginx-test  | [cert_cleanup] 0 file(s) deleted.
nginx-test  | [app         ] [11/16/2024] [7:15:57 AM] [Global   ] › ℹ  info      Wrote JWT key pair to config file: /data/keys.json
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      Current database version: none
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] auth Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] user Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] user_permission Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] proxy_host Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] redirection_host Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] dead_host Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] stream Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] access_list Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] certificate Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] access_list_auth Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [initial-schema] audit_log Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [websockets] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [websockets] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [forward_host] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [forward_host] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [http2_support] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [http2_support] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [http2_support] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [http2_support] dead_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [forward_scheme] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [forward_scheme] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [disabled] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [disabled] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [disabled] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [disabled] dead_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [disabled] stream Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [custom_locations] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [custom_locations] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [hsts] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [hsts] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [hsts] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [hsts] dead_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [settings] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [settings] setting Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [access_list_client] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [access_list_client] access_list_client Table created
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [access_list_client] access_list Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [access_list_client_fix] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [access_list_client_fix] access_list Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [pass_auth] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [pass_auth] access_list Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [redirection_scheme] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [redirection_scheme] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [redirection_status_code] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [redirection_status_code] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [stream_domain] stream Table altered
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:15:58 AM] [Setup    ] › ℹ  info      Creating a new user<EMAIL_ADDRESS>with password: changeme
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [Setup    ] › ℹ  info      Initial admin setup completed
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [Setup    ] › ℹ  info      Default settings added
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [Global   ] › ⬤  debug     CMD: logrotate -s /config/logrotate.status /etc/logrotate.d/nginx-proxy-manager
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [Setup    ] › ℹ  info      Logrotate completed.
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [SSL      ] › ℹ  info      Renewing SSL certs expiring within 30 days ...
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [Global   ] › ℹ  info      Backend PID 409 listening on port 3000 ...
nginx-test  | [app         ] [11/16/2024] [7:15:59 AM] [SSL      ] › ℹ  info      Completed SSL cert renew process

Container inspect
No response
Anything else?
No response

The first time i start the container, it seems to work. but if i do a docker compose restart, the container then starts totally fresh and all my settings are gone:
nginx-test  | [init        ] container is starting...
nginx-test  | [cont-env    ] loading container environment variables...
nginx-test  | [cont-env    ] APP_NAME: loading...
nginx-test  | [cont-env    ] APP_VERSION: loading...
nginx-test  | [cont-env    ] DOCKER_IMAGE_PLATFORM: loading...
nginx-test  | [cont-env    ] DOCKER_IMAGE_VERSION: loading...
nginx-test  | [cont-env    ] HOME: loading...
nginx-test  | [cont-env    ] TAKE_CONFIG_OWNERSHIP: loading...
nginx-test  | [cont-env    ] XDG_CACHE_HOME: loading...
nginx-test  | [cont-env    ] XDG_CONFIG_HOME: loading...
nginx-test  | [cont-env    ] XDG_DATA_HOME: loading...
nginx-test  | [cont-env    ] XDG_RUNTIME_DIR: loading...
nginx-test  | [cont-env    ] XDG_STATE_HOME: loading...
nginx-test  | [cont-env    ] container environment variables initialized.
nginx-test  | [cont-secrets] loading container secrets...
nginx-test  | [cont-secrets] container secrets loaded.
nginx-test  | [cont-init   ] executing container initialization scripts...
nginx-test  | [cont-init   ] 10-check-app-niceness.sh: executing...
nginx-test  | [cont-init   ] 10-check-app-niceness.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-clean-logmonitor-states.sh: executing...
nginx-test  | [cont-init   ] 10-clean-logmonitor-states.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-clean-tmp-dir.sh: executing...
nginx-test  | [cont-init   ] 10-clean-tmp-dir.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-init-users.sh: executing...
nginx-test  | [cont-init   ] 10-init-users.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-pkgs-mirror.sh: executing...
nginx-test  | [cont-init   ] 10-pkgs-mirror.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-set-tmp-dir-perms.sh: executing...
nginx-test  | [cont-init   ] 10-set-tmp-dir-perms.sh: terminated successfully.
nginx-test  | [cont-init   ] 10-xdg-runtime-dir.sh: executing...
nginx-test  | [cont-init   ] 10-xdg-runtime-dir.sh: terminated successfully.
nginx-test  | [cont-init   ] 15-install-pkgs.sh: executing...
nginx-test  | [cont-init   ] 15-install-pkgs.sh: terminated successfully.
nginx-test  | [cont-init   ] 54-db-upgrade.sh: executing...
nginx-test  | [cont-init   ] 54-db-upgrade.sh: terminated successfully.
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: executing...
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: Enabling IPV6 in hosts in: /etc/nginx/conf.d
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/ssl-ciphers.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/proxy.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/block-exploits.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/assets.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/log.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/include/force-ssl.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/default.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/production.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /etc/nginx/conf.d/crowdsec_openresty.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: Enabling IPV6 in hosts in: /config/nginx
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /config/nginx/ip_ranges.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: - /config/nginx/resolvers.conf
nginx-test  | [cont-init   ] 55-nginx-proxy-manager.sh: terminated successfully.
nginx-test  | [cont-init   ] 85-take-config-ownership.sh: executing...
nginx-test  | [cont-init   ] 85-take-config-ownership.sh: terminated successfully.
nginx-test  | [cont-init   ] 89-info.sh: executing...
nginx-test  |     ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
nginx-test  |     │                                                                      │
nginx-test  |     │ Application:           Nginx Proxy Manager                           │
nginx-test  |     │ Application Version:   2.11.3                                        │
nginx-test  |     │ Docker Image Version:  n/a                                           │
nginx-test  |     │ Docker Image Platform: linux/amd64                                   │
nginx-test  |     │                                                                      │
nginx-test  |     ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
nginx-test  | [cont-init   ] 89-info.sh: terminated successfully.
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: executing...
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: Deploy Crowdsec Openresty Bouncer..
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: Deploy new crowdsec-openresty-bouncer.conf ..
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: Deploy Crowdsec Templates ..
nginx-test  | [cont-init   ] 99_crowdsec-openresty-bouncer.sh: terminated successfully.
nginx-test  | [cont-init   ] all container initialization scripts executed.
nginx-test  | [init        ] giving control to process supervisor.
nginx-test  | [supervisor  ] loading services...
nginx-test  | [supervisor  ] loading service 'default'...
nginx-test  | [supervisor  ] loading service 'logmonitor'...
nginx-test  | [supervisor  ] service 'logmonitor' is disabled.
nginx-test  | [supervisor  ] loading service 'app'...
nginx-test  | [supervisor  ] loading service 'nginx'...
nginx-test  | [supervisor  ] loading service 'logrotate'...
nginx-test  | [supervisor  ] service 'logrotate' is disabled.
nginx-test  | [supervisor  ] loading service 'cert_cleanup'...
nginx-test  | [supervisor  ] all services loaded.
nginx-test  | [supervisor  ] starting services...
nginx-test  | [supervisor  ] starting service 'nginx'...
nginx-test  | [nginx       ] nginx: [alert] [lua] init_by_lua:9: [Crowdsec] Bouncer Disabled
nginx-test  | [supervisor  ] starting service 'app'...
nginx-test  | [app         ] [11/16/2024] [7:36:45 AM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
nginx-test  | [app         ] [11/16/2024] [7:36:45 AM] [Global   ] › ℹ  info      Creating a new JWT key pair...
nginx-test  | [supervisor  ] all services started.
nginx-test  | [cert_cleanup] ----------------------------------------------------------
nginx-test  | [cert_cleanup] Let's Encrypt certificates cleanup - 2024/11/16 07:36:45
nginx-test  | [cert_cleanup] ----------------------------------------------------------
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-27/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-27/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-27/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-27/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-38/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-38/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-38/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-38/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-39/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-39/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-39/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-39/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-46/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-46/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-46/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-46/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-28/fullchain7.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-28/cert7.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-28/privkey7.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-28/chain7.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-41/cert4.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-41/chain4.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-41/fullchain4.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-41/privkey4.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-37/cert5.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-37/chain5.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-37/fullchain5.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-37/privkey5.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-40/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-40/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-40/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-40/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-77/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-77/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-77/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-77/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-25/cert3.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-25/fullchain3.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-25/privkey3.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-25/chain3.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-47/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-47/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-47/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-47/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-29/fullchain7.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-29/cert7.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-29/privkey7.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-29/chain7.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-74/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-74/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-74/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-74/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-45/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-45/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-45/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-45/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-72/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-72/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-72/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-72/cert1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-83/fullchain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-83/chain1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-83/privkey1.pem.
nginx-test  | [cert_cleanup] Keeping /etc/letsencrypt/archive/npm-83/cert1.pem.
nginx-test  | [cert_cleanup] 64 file(s) kept.
nginx-test  | [cert_cleanup] 0 file(s) deleted.
nginx-test  | [app         ] [11/16/2024] [7:36:52 AM] [Global   ] › ℹ  info      Wrote JWT key pair to config file: /data/keys.json
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      Current database version: none
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] auth Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] user Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] user_permission Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] proxy_host Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] redirection_host Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] dead_host Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] stream Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] access_list Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] certificate Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] access_list_auth Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [initial-schema] audit_log Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [websockets] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [websockets] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [forward_host] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [forward_host] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [http2_support] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [http2_support] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [http2_support] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [http2_support] dead_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [forward_scheme] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [forward_scheme] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [disabled] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [disabled] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [disabled] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [disabled] dead_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [disabled] stream Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [custom_locations] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [custom_locations] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [hsts] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [hsts] proxy_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [hsts] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [hsts] dead_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [settings] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [settings] setting Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [access_list_client] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [access_list_client] access_list_client Table created
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [access_list_client] access_list Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [access_list_client_fix] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [access_list_client_fix] access_list Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [pass_auth] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [pass_auth] access_list Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [redirection_scheme] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [redirection_scheme] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [redirection_status_code] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [redirection_status_code] redirection_host Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [stream_domain] stream Table altered
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
nginx-test  | [app         ] [11/16/2024] [7:36:53 AM] [Setup    ] › ℹ  info      Creating a new user<EMAIL_ADDRESS>with password: changeme
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [Setup    ] › ℹ  info      Initial admin setup completed
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [Setup    ] › ℹ  info      Default settings added
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [Global   ] › ⬤  debug     CMD: logrotate -s /config/logrotate.status /etc/logrotate.d/nginx-proxy-manager
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [Setup    ] › ℹ  info      Logrotate completed.
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [SSL      ] › ℹ  info      Renewing SSL certs expiring within 30 days ...
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [Global   ] › ℹ  info      Backend PID 409 listening on port 3000 ...
nginx-test  | [app         ] [11/16/2024] [7:36:54 AM] [SSL      ] › ℹ  info      Completed SSL cert renew process

Turns out npm uses /data and this one uses /config.
I mounted /data to /config in the container and it works now.


feat(MeasureTheory): generalize instance ContinuousInv.measurableInv

Weaken the hypotheses of the instance ContinuousInv.measurableInv and change its name (it was called TopologicalGroup.measurableInv before).

The code change looks straightforward. I cannot tell if this is needed later (and am not expert on the measure theory part of the library), but it seems ready for a look by a maintainer:
maintainer merge

!bench

Thanks!
bors merge


feat: allow to see the command prompt followed by the executed command in the output image

It would be great if it was possible to get the command executed in the final image (using --execute), that way it will look like a "real" screenshot of a terminal.
If for limitation it isnt possible to capture the prompt, even a prompt as simple as:
$ <cmd>
<output>

would be amazing already.

Hey totally agree! We're working on this one in https://github.com/charmbracelet/freeze/issues/44


Ninja Cursor alters mouse clicks in Obsidian ribbon

I use the following CSS to create a drag handlebar in the ribbon:
body:not(.is-popout-window) div.side-dock-actions:before {
    content: "\2723";
    font-size: 30px;
    -webkit-app-region: drag;
    text-align: center;
    margin-top:  -9px;
    margin-left: 0px;
}

In a new vault with only Ninja Cursor installed and only the above snippet enabled, dragging/moving the Obsidian window doesn't work. I tried looking for .workspace-ribbon in Ninja Cursor's default CSS and anything to do with the ribbon the main.js, but couldn't find anything. I'm not sure why Ninja Cursor would affect mouse events in the ribbon, but it does. Any advice on a fix or workaround? Thanks!
Windows 11 Pro 22H2; Obsidian 1.2.6 (installer 1.1.16), Ninja Cursor 0.0.11

Thank you for asking me!
Ninja-cursor is dashing on the invisible layer. I have not been sure why an invisible layer affects window dragging, but thanks to your question, I now understand.
All we need to do is reset this -webkit-app-region.
It has been addressed and fixed at v0.0.12. Would you mind if I ask you to try the latest version, please?

WOW! That was fast.
Updated to 0.0.12 and my handlebar window dragging works again! Thank you so much for the fix and the fun plugin! 🙏

This is your contribution! However, I am really honoured by your grateful words.
I would like to thank you once again!

Just noticed you are based in Osaka. I'm in Kobe. :D ⛩⚓ Thanks again!


Allow MemGPTs to read/write from a file(s)

Enable workflow where MemGPT + user can co-edit a document together.
Add write_to_text_file function and read_to_text_file function.

@cpacker Please elaborate the feature request with some examples. I am interested to implement this feature.

Allowing the Aider CLI tool to work with memGPTs is probably the way to go here
https://github.com/cpacker/MemGPT/issues/62

Use Cases:

Document generation - "Create an outline for a business presentation, etc."
HTML interface presentation - "Create a UI for navigating a MemGPT managed set of documents"
Co-editing with MemGTP - "Create a set of documents I can edit in a word processor of my choice, which MemGPT can notice changes to and react over time to."

Added in #174 (still needs a preset toggle via the CLI, coming in the next release).
@genericrich @Yash-Ambekar please feel free to open new PRs / issues with more feature requests.


Redirect stderr to the temp file used in the install script.

Hi,
if stderr is not redirected to the tmp file the output the script tries to match in the else clause will never be there.

You seem to be right. Not quite sure how I missed that when testing o_O
Thanks! :+1:

Looks good, thanks @dzan!


Add secret authentication

Please add secret authentication

Can you be a bit more specific?

Using the current authentication method I get 405.
I would like to have other authentication options. For example, like here https://github.com/pederhan/harborapi#authentication

Hello! Can you add a new authentication method?

we'll look into that


Add ArgoCD Integration

Description
Added support for ArgoCD projects, applications and deployment resources
What -
Why -
How -
Type of change

[ ] New feature (non-breaking change which adds functionality)

Is there any way to subscribe to events in ArgoCD so we can listen to realtime changes? @PeyGis


Error loading agora_node_ext

It's me again) I've got these error while starting my electron app:

@keenoptical
please follow steps:

Check if the file exists.
Check if the webpack.config is configured correctly. (If you are using others build tools, pls check externals settings)
Check if asar.unpacked is configured correctly.

After following these steps i finally can require agora-electron-sdk:
Adding section to package.json:
"agora_electron": {
    "platform": "win32",
    "prebuilt": true,
    "arch": "ia32"
  },

Reinstall electron dependency:
npm install -D --arch=ia32 electron
Now dependency requires correctly.


Sticky when not "window" is the one that scrolls

I am using Angular Material, and a part of that layout makes my content element the one that scrolls, not the "window" itself. My header, and left/right menues all stays in place.
So, angular.element(window).on('scroll', function() { console.log('scrolled')(); }) gives no output when scrolling, but angular.element(document.getElementById("myStickyID")).on('scroll', function() { console.log('scrolled')(); }) does.
Is it possible to add more dynamic of what to watch when scrolling, or will that possible break other things?

+1 for this functionality.

I'm currently working for a client that desires this behavior and is open to forking the project.  Expect it in the coming weeks.

@xeor @blindenvy
This functionality should be in place as of #86.  Let me know if you have any problems.

@EnigmaticCode thats great! I am not currently working on the same project anymore, but I will def keep in mind that ngSticky supports this now. It will be useful in a lot of upcoming projects :)


ListFileHistory can deadlock

Concurrently writing to a file and calling ListFileHistory on it can get into a deadlocked state. Here is a minimal, reproducible test: https://github.com/pachyderm/pachyderm/compare/list-file-history-test
Observed on k8s on docker for mac.

^ I have committed the cardinal sin of mixing tabs and spaces in that branch, sorry

This appears to have been fixed in the mean-time. I'll open a PR with the regression test.

I spoke too soon. It passed the first few times, but is now failing again.

I'm still seeing the issue - deadlocks occur when calling View on *bolt.DB.

Holding on continued investigation of this. Our intention is to no longer use BoltDB for filesets, which would obviate the need for a fix.

@Tryneus not sure if I heard right, but did @brycemcanally mention that you fixed this already?

Could not reproduce this error with the given test, so I think it is safe to assume the problem has been fixed.  Ported the test forward to our current PFS unit tests and merged it in #5045.


Build promote: Display environment

With drone 1.1.0 I can promote (previously called deploy) a build with:
drone build promote [command options] <repo/name> <build> <environment>

where I can specify a target environment.
In the web interface however, I can't seem to find out which environment a build has been promoted to.
I only see:
user-xxx promoted `branch`

I would like instead:
user-xxx promoted `branch` to `env`

(or any other way to display that info.)
I remember drone 0.8 used to display target environments when running a drone deploy.
Thanks

we have existing issue https://github.com/drone/drone-ui/issues/276 for this


feat: add close_range for glibc

This PR adds close_range(2) for Linux/glibc:
#include <linux/close_range.h>

       int close_range(unsigned int first, unsigned int last,
                       unsigned int flags);

musl and uClibc don't have wrappers for this syscall

@bors r+

:pushpin: Commit 7b9e367f67a899b319da7020d0d836f515f492f2 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 7b9e367f67a899b319da7020d0d836f515f492f2 with merge 017bf5f6b30abcdf59fc2a09997da79cb5a1cd29...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 017bf5f6b30abcdf59fc2a09997da79cb5a1cd29 to main...


Bump the queue

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 28.7%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
797

Relevant Lines:
2777

💛  - Coveralls


Add downloadable binaries

Using github's action and versions to build binaries. go-releaser will that for us, if only we can rewrite our C code in go

I did it

I did it

💪🏽

💪🏽


Use double spaces instead of Chatterino character when possible

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description

No issue. Can help eliminate issues with users noticing the Chatterino character. Double spaces are way less noticeable (Chatterino, Chatty and webchat don't even render those!) than a space and U+E0000.

when possible

Am I missing soemthing or are you straight-up removing our old solution instead?

If there is no space, there is nothing to replace with a double space.

I didn't even know this was a feature, until I saw this change.
Always considered this behaviour a bug I wanted to fix eventually, as it happens seemingly randomly, breaks building SE pyramids, and was just a nuisance all around (to various people).
Where is this setting (getSettings()->allowDuplicateMessages) in the UI, so I can turn it off? Or is it not exposed in the UI (for reasons)?
I'd vote for it to be off by default for the mentioned reasons. At least I can't recall enabling something like that?
Or maybe I did? The name "allowDuplicateMessages" is something I'd associate with 'r9k' more than with what it does.

Where is this setting (getSettings()->allowDuplicateMessages) in the UI, so I can turn it off?

here


Pattern: Update the Logo grid functional specifications for the Solutions page changes

User Story

As a [user role below]:
DDS developer

I need to:
have the Logo grid functional specs

so that I can:
so that I can properly code the Logo grid component that meets the Solution template requirements

Additional information

Design Issue (#  )
Development issue (# )

Acceptance criteria

[ ] Documented Logo grid Link functional specifications
[ ] Sent and/or presented the specs to Design, Content Strategy and Dev for their review and comments
[ ] Additional stories are created, if needed, for any work to be done in future sprints
[ ] Send a message to Jeff to let him know that the functional specs are ready for a developer by tagging him in the dev issue.

duplicate of issue (#645).  closing


[ms-gltf] Disable feature samples on macOS, iOS, and Android

Fixes #30675

ms-gltf[samples] will build failed on high version of macOS, according the upstream to disable the build of this feature on macOS, iOS, and Android.
The patch fix-apple-filesystem.patch is fixing the build of ms-gltf[samples] on macOS, so remove it.
The upstream codes link:
https://github.com/microsoft/glTF-SDK/blob/master/CMakeLists.txt#:~:text=%23 Disable the,endif()
# Disable the samples on macOS, iOS, and Android since the experimental features they use
# do not yet build with XCode or clang on these platforms.
if(APPLE OR ANDROID_OS_PLATFORM)
    option(ENABLE_SAMPLES "ENABLE_SAMPLES" OFF)
else()
    option(ENABLE_SAMPLES "ENABLE_SAMPLES" ON)
endif()

[x] Changes comply with the maintainer guide
[ ] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks!


Install does not work

Hey, I ran into this issue while installing the cli.
Running cargo install bore-cli gives the following error :
error: there is no argument named `message`
  --> /Users/theaupoulat/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.3/src/client.rs:47:73
   |
47 |             Some(ServerMessage::Error(message)) => bail!("server error: {message}"),
   |                                                                         ^^^^^^^^^

error: there is no argument named `to`
  --> /Users/theaupoulat/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.3/src/client.rs:55:29
   |
55 |         info!("listening at {to}:{remote_port}");
   |                             ^^^^

error: there is no argument named `remote_port`
  --> /Users/theaupoulat/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.3/src/client.rs:55:34
   |
55 |         info!("listening at {to}:{remote_port}");
   |                                  ^^^^^^^^^^^^^

error: there is no argument named `to`
   --> /Users/theaupoulat/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.3/src/client.rs:120:52
    |
120 |     .with_context(|| format!("could not connect to {to}:{port}"))
    |                                                    ^^^^

error: there is no argument named `port`
   --> /Users/theaupoulat/.cargo/registry/src/github.com-1ecc6299db9ec823/bore-cli-0.2.3/src/client.rs:120:57
    |
120 |     .with_context(|| format!("could not connect to {to}:{port}"))
    |                                                         ^^^^^^

error: could not compile `bore-cli` due to 5 previous errors
warning: build failed, waiting for other jobs to finish...
         Building [=======================> ] 109/111: tokio                                                       error: failed to compile `bore-cli v0.2.3`, intermediate artifacts can be found at `/var/folders/bs/_r3q6dsd6wq0d9fbw1t8pk_r0000gn/T/cargo-installwSAvMU`

Caused by:
  build failed

Running it on macOS Monterey v12.1

Duplicate of #7 — please update your Rust version! :)

Thanks @ekzhang  😍


How to add complex footers?

Hey,
I am thinking about writing invoices using asciidoctor-web-pdf. For this, I need to set a complex multiline footer on my document.
I found this issue: #128
And I am able to put some text into the footer like this:
@page {
    size: A4;
    @bottom-center {
        content: "Hello world";
    }
}

But how can I put more complex content into it? Issue #128 talks about the passthrough syntax:
++++

  ...

++++

But I do not understand how I can put this into the footer.

Hello @RudolfVonKrugstein
I think the important part is:

It appears that if you declare the header content in CSS with element() instead of the counter method, and create the necessary named HTML in the body and add the running CSS attribute to it, it will be removed from the body and put in the header instead.

I didn't try but you will most likely need to declare something like:
@page {
  margin: 1.5cm;
  size: A4;
  @bottom-center {
    content: element(bottom-title-block);
  }
}
.bottom-title-block {
   position: running(bottom-title-block);
}

To use custom styles, please read the "Custom styles" second in https://github.com/Mogztter/asciidoctor-web-pdf#configuration
If you make it work, and since this feature can be useful in many cases, please feel free to contribute documentation, I will gladly review it :hugs:

I can confirm that this approach is working.
There was a few annoying issues but I took care of them. In the upcoming version, you will be able to provide running elements in a docinfo file. You can then position then position them in the bottom margin of the page (footer).
Here's an example (not yet released):
report.adoc
= 2021 Annual Report
:docinfo: private

report-docinfo-running-pdf.html*
<address class="contact-us">
  Handicap International

  138, avenue des Frères Lumière

  69008 Lyon - France
</address>

style.css
.contact-us {
  width: 6cm;
  position: running(runningContact)
}

@page {
  margin: 1cm 2cm 4cm 2cm;
}

@page :right {
  @bottom-left {
    content: element(runningContact)
  }

  @bottom-right {
    content: counter(page);
    margin: 10pt 10pt 30pt 0;
  }
}

@page :left {
  @bottom-right {
    content: element(runningContact)
  }

  @bottom-left {
    content: counter(page);
    margin: 10pt 0 30pt 10pt;
  }
}

$ asciidoctor-web-pdf report.adoc -a stylesheet="+style.css"


unintuitive Scrolling Object Collection behavior when using a controller

Describe the bug
When scrolling an Scrolling Object Collection with a Controller in VR the the items are only moved by the lateral movement of the controller.

To reproduce
Steps to reproduce the behavior:

Open a scene with an  Scrolling Object Collection (for example the Demo Scene) in VR headset.
Scroll with VR-Controller ( I used a Microsoft MR-Controller

Expected behavior
I would expect to content to move relative to my "grab point" on the list. ( where my pointer touched the list when i selected it)
So that it can be  also be scrolled by the rotation of the controller.

This behavior would be more inline with other common VR Experiences. For example scrolling thru a Microsoft Store Page in the Microsoft Mixed Reality-Portal default Lobby room.
Your setup (please complete the following information)

Unity Version v19.4LTS
MRTK Version 2.5

Target platform
Microsoft MR VR-Headset

Retested with MRTK 6.2:
The behavior feels especial awkward when scrollen a list with a large canvas size ( for example same same height as the user)  from further away. Scrolling requires very large tiring arm movements.

@MaxWang-MS Do you know if you've looked at this in any of your SOC investigations? I think several of our interactive components (the sliders as well, i think?) assume they should move according to the actual movement of the source, which makes sense on HL2 where the hand ray isn't affected by the hand rotation, but feels awkward with controllers where the rays are rotated easily

(keeping issue from going stale) will retest once MRTK v3 is released.

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visithttps://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


Server links not working on OS X

I installed dasht through homebrew, however, I find that the dasht-server links do nothing.  For example, the link for numpy.add points to file:///Users/myusername/.local/share/dasht/docsets/NumPy.docset/Contents/Resources/Documents/doc/reference/generated/numpy.add.html#//apple_ref/Method/numpy.add.  If I manually remove everything after and including the # from this then I am sent to the correct page.

What browser are you using?  It works correctly for me in both w3m(1) and Firefox 46.

I've tried the most recent versions of both Chrome and Safari.  Both showed the same problem for me, but w3m seems to work fine...

Ah then I suspect the problem is this: Webkit browsers don't follow file links.  It wasn't the removal of the URI fragment that made the page load for you in those browsers, but rather it was the fact that you manually submitted a file URL that made the difference. :neckbeard:

Ah.  That make sense. 😃   My apologies for not noticing that in the documentation.
Thanks for the quick follow up and the great tool!


Update Documentation about Engine Specification

In the main README, clarify that the engine specification file is created in a separate .m file but must be called from the aircraft specification file.

Resolved in #30


RFC: Include python3.def itself in the Rust source

All parsing and processing is done in the CI so that the crate itself includes the python3.def file itself instead of creating it on the fly.
Based on the idea voiced in https://github.com/PyO3/python3-dll-a/pull/9#issuecomment-1113238455
I did try to keep the existing semantics in place and just moved things around to a Python script running in the CI. I just chose Python because I assume that the ubuntu-latest image contains a reasonably up-to-date version. (The updated CI workflow is untested, but I used the script locally the produce the definition file committed here.)
One could try using the upstream script to do the parsing and generating, but I think that should be evaluated separately.

I agree with this change in principle, but I'd like to see at least some test coverage to ensure that the number of Stable ABI exports is non-decreasing with each definitions update PR. The Rust version had something like that.
You should also update LICENSE to remove all mentions of Python sources.

Also note that the automatically created PR will contain a diff of the generated definitions file this way, so we can also review that before merging.

The switch to TOML will happen today or early next week.

CPython just switched to TOML.
If you stick with Python for parsing, beware that toml is unmaintained/outdated.
Consider tomli is a little, correct TOML parser, which is being added into the Python 3.11 standard library as tomllib. (Full disclosure: I helped)
If you happen to know another project that needs a python3.def (or could use it), please let me know. I could probably generate it and keep it updated in CPython itself to reduce duplication of effort.

I think we can merge this now (?). I'll wait for @messense to take a look.

Had to switch to installing python3-pip via apt-get and tomli via pip as ubuntu-latest is 20.04 which does not yet contain the python3-tomli package introduced in 22.04.

TBH I was surprised that Ubuntu had up to date Python packages, but I'm mostly using official Rust docker images based on Debian Buster, so pip install was my go-to choice.


Html.Attributes.batch

This is a continuation and summary of the discussion from elm-dev.
Specifically this is about Attributes.batch, which combines multiple attributes into one attribute.
Html.Attributes.batch : List (Attribute msg) -> Attribute msg
Performance
Attributes.batch would save on allocations.  It's not clear how impactful this would be, but saving allocations is always nice.
Design Opportunities

Accessibility

Accessibility is often skipped, even by accessibility-minded devs.
Built-in accessibility is vastly better.  If it's even remotely a pain, the work will likely be skipped completely.
Richard's full example of using Attributes.batch to include accessibility attributes in a theme.

Svg Property Animation

Any animation library that wants to animate svg attributes will always return a list of attributes.
The current syntax is frustrating when animating a large number of different things.

Current, standard way of rendering an animation:

div
    (List.concat
        [ Animation.render model.style
        , [ style
                [ ( "position", "absolute" )
                , ( "border-style", "dotted" )
                ]
           ]
        ]
    )
    [ text "This is being Animated!" ]

Simplified with Attributes.batch.
div
    [ Animation.render model.style
    , style
        [ ( "position", "absolute" )
        , ( "border-style", "dotted" )
        ]
    ]
    [ text "This is being Animated!" ]

Style and Animation

Problem Stylesheets and inline styles both allow for different capabilities.  For example: stylesheets allows for pseudoelements and media queries, while inline styles are the only practical way of rendering an animation that is based in Elm.   There's also a separation of data leading to duplication of style states.
Solution A potential solution is to have a library that renders both inline and stylesheet styles and dynamically switches between the two as necessary.  Specifically this would be an Elm CSS library that allows the embedding of Elm based animations and rendering the output as a class and an inline style.  This goes a long way towards making animation more accessible.

Initial animation states are implicitly present.
The only wiring required is allowing the stylesheet to have a subscription to animationFrame, which is only active when animations are running.

In contrast to now where each animation has to be wired up to a subscription and to the model separately.

Small Example This approach hinges on Attributes.batch because a class and an inline style need to be rendered at the same time.  So: button [ styleClass MyButton ] [] renders with class "myButton" and style myButtonAnimatedStyle when the animation is running.

Summary Attribute.batch allows for building accessibility into a theme and making Elm a more compelling animation platform.
One of the most common pieces of feedback I get for elm-style-animation is "it looks complicated". I'm currently working to address this as much as possible, but Attr.batch would help significantly.  I want to make animation trivial for Elm beginners.
In adding Attr.batch we lose a code smell for potentially bizarre organization of attributes.  This sucks and I'm generally a fan of Elm's ability to cultivate best practices through it's language design.
However, currently I'm of the mind that the benefits mentioned above lead to solving real pain points.  Animation and accessibility can be strong selling points for Elm.  I personally think a simplified experience with regards to these areas would be a solid win for Elm as a platform, even at the cost of a code smell.  YMMV, of course :)

I'm closing this because I realized a feature request or even a feature request summary probably isn't appropriate for the issues area, which explicitly says issues are for bugs.
A better approach in the future would have been to cultivate discussion on the mailing-list or somewhere else.
Thanks for your patience :)

In this case, further discussion is not progress on this topic. Eventually I'll do another batch on this library, and this will come into consideration. Until that time, I can't do anything with the discussions. Also, code samples are way more valuable than discussion and opinion anyway, so more discussion is not even what is needed when it is time.

Good to know and thanks again.


Add Bullet train (TGV) and Monorail as "Mode de transport"

I think adding a TGV icon could be good (and easy, since the logo already exists) for connection on stations.
The monorail is more for another network since it doesn't exist in Paris (maybe OrlyVAL?), so a logo has to be found I think.

Yup! Definitely have to look into these.


Add Roadmaps as a way to encourage contributions file

This is the output of a google docs collaberation.
All comments in the doc was resolved and closed.
fixes: #329

@TheFoxAtWork @dzolotusky
This is a band new document, can you please review with you TOC hats on.

There is a lot of wonderful content here. I've made several suggestions and have open questions of a few items for enhanced clarity.

Thank you @TheFoxAtWork  for the thorough review. I believe I have addressed all of your review comments. Please let me know if any further updates are needed, or if I have misinterpreted anything.


Doc: Clean up README

Rewrite readme to reflect the change from PowerShell to Python + Docker

This is done


Should xstate-wallet export functionality

At the moment, the simple-hub relies on xstate-wallet types and message serialization utilities. Should these be exported from the xstate-wallet? Should a separate package hold these? Or do we think that these are xstate-wallet internals that should not be exposed outside of the package?

Since the workflows are now being defined in xstate-wallet, it makes sense for some things to be exported from xstate-wallet right now.

@andrewgordstewart Do you have any specific exports in mind?

support-state, depositing, virtual-funding-as-hub, etc

I'm of the "duplication over premature abstraction" school of thought. I'd rather see these types and utilities copied across, rather than introduce dependencies between packages, or deal with the overhead of pulling them out into a new package. That way, teams working in different packages can code to their own use-cases, without having to worry about other consumers (e.g avoiding issues like https://github.com/statechannels/monorepo/pull/1168#discussion_r390485798).
When we're not developing so quickly, and the dust settles, it should be clearer which utilities etc. should be pulled up into a shared package.


Unable to update Lambda function in USGovCloudWest1

Describe the bug
When publishing an update to an existing Lambda function, it fails with the message, "Error creating function url config for function : Unable to determine service/operation name to be authorized".  Upon researching online, I found the issue at https://github.com/aws/aws-lambda-dotnet/issues/1188.  It appears that this process requires the permission "GetFunctionURLConfig", but this permission/feature does not exist in USGovCloudWest1.
To Reproduce
In the VS Solution Explorer, right-click on the Lambda project and select Publish to AWS Lambda.  Verify that the inputs are all correct (they are), and click on the Upload button.
-->
Expected behavior
The Lambda function gets updated.
Computer (please complete the following information):

Windows Version:  Windows 10 Enterprise 21H2
Visual Studio Version:  Enterprise 2022 64-bit 17.3.6
AWS Toolkit for Visual Studio Version:  <IP_ADDRESS>

Thank you for reaching out @brpekin - it looks like we need to propagate the changes from https://github.com/aws/aws-extensions-for-dotnet-cli/pull/221 (referenced by the issue you mentioned) into the Toolkit.

Thanks for the update @awschristou . I'm glad I could provide the information to hopefully make this as easy as possible.

Version <IP_ADDRESS> of the Toolkit is available, with a fix for the issue preventing Lambda deployments to GovCloud regions.


Is there any way to add some light or shadow to segmentation

Is there any way to add some light or shadow to segmentation, or to make segmentation three-dimensional?

Do you have an image you can share?


Change min version to Lollipop

SDK 21 or 22 I think

Decided to use version 25 as the minimum (7.1) because there's some stuff I'd have to replace if I support any lower versions. Can always consider this in future, though, so feel free to open an issue if you really want support on a particular older version.


Next Generation sampler using chemical environments

I'm working on generalizing the sampler that we were using for smarty to work with chemical environments. I don't have details to discuss now, but it seemed like there should be an issue for this.

@davidlmobley
The sampler now exists which was the point of this issue, there are enhancements that I think need their own issues?
I think we should just close this and write more specific ones for the changes being made.

Yes, agreed @bannanc


netadaptercx problem with LSOv2: On/Ipv6 Extension: On  in windows11 24H2 build no 26100

Hi
I am a developer for netadapter  driver . the netadapter driver have pass the WHLK test in windows os  22H2 and 23H2. now we want pass the whlk test in 24H2. when LSOV2 on and IPV6  extension on of whlk offloadlso test  in  24h2,  we get net packet parameter NET_PACKET_LAYOUT from NET_PACKET in  EVT_PACKET_QUEUE_ADVANCE  callback function. find the Layout.Layer3HeaderLength and Layer4HeaderLength is not right length compare to  test  case of WHLK offloadlso and wireshark .the offloadlso whlk test report  "The miniport has not finished the LSOv1/v2 send correctly for 30 packets. The reason for this failure may be that the miniport has not set the send complete OOB correctly.Tcp module expected to get 30 reassembled packets, but only got 0. There are 30 missing packets" error.  example :the actual value is Layer2HeaderLength = 14, Layer3HeaderLength = 56 , Layer4HeaderLength = 20,but  get from NET_PACKET is  Layout.Layer2HeaderLength = 14, Layout.Layer3HeaderLength = 0 , Layout.Layer4HeaderLength = 0.

I try to Parser netpacket header in  driver , use the actual layout parameter to  send larget pacet and can send right fragment packet. but  the offloadlso whlk test still report  "The miniport has not finished the LSOv1/v2 send correctly for 30 packets. The reason for this failure may be that the miniport has not set the send complete OOB correctly" error.

     can you help me find the failure reason for the WHLK test  offloadlso?

Please contact the CSS team using the instructions here to obtain an errata for this bug while we work on a fix for this issue in 24H2: https://learn.microsoft.com/en-us/windows-hardware/test/hlk/user/windows-hlk-support

addition information: ndis driver can pass  whlk offloadlso test in 24h2。
windows hlk support need to creat support request and i need to apply  from  my boss.


Results on cifar10 very bad even if trained for over 1000 epochs

Dear authors,
I used the default parameters and trained it on Cifar10 datasets for over 1000 epochs, but the results are not very good looking. It is blurry and can hardly recognize the category. Did you use another set of parameters for cifar10?
Looking forward to your reply. Thanks.

We have no CIFAR10 results in the paper so I'm not sure what you're referring to. You may want to take a look at https://github.com/igul222/improved_wgan_training where we provide a very good CIFAR10 model.
Cheers :)
Martin


Set Emitter's threads name for easier debugging (close #280)

Gives the Emitter threads names to help with debugging.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


Better logging/debugging in test

Changes

:bug: Fix filing tests on Windows related to incorrect process livenes detection.
:broom: Change symlink from being absolute to being relative.
:broom: Better test output + the test does not hang on Windows.

@lkingland PTAL

=== RUN   TestBuilder_Concurrency
mkdir -p C:\Users\mvasek\AppData\Local\Temp\TestBuilder_Concurrency3717259113\001\.func\builds\by-hash\8cf6addafdcbc49
5ab800c0a8210f7ca4c486ee17f5cac9cc8be10ed51f7a3f3
mkdir -p C:\Users\mvasek\AppData\Local\Temp\TestBuilder_Concurrency3717259113\001\.func\builds\by-pid
ln -s ..\by-hash\8cf6addafdcbc495ab800c0a8210f7ca4c486ee17f5cac9cc8be10ed51f7a3f3 C:\Users\mvasek\AppData\Local\Temp\T
estBuilder_Concurrency3717259113\001\.func\builds\by-pid\23056
→ /func
→ /func/README.md
→ /func/func.yaml
→ /func/go.mod
→ /func/handle.go
→ /func/handle_test.go
mv .\datalayer.tar.gz .\oci\blobs\sha256\17d96d33daa25c79f1086a5d848c8cdceba9e590721c70c48e45176fb1c018ab
→ /etc/ssl/certs/ca-certificates.crt
→ /etc/pki/tls/certs/ca-certificates.crt
mv .\certslayer.tar.gz .\oci\blobs\sha256\6d9104c57ada84f79fdaf1ee171d35c60a98c576776dbe5d409153bbd172310d
rm -rf C:\Users\mvasek\AppData\Local\Temp\TestBuilder_Concurrency3717259113\001\.func\builds\by-hash\8cf6addafdcbc495a
b800c0a8210f7ca4c486ee17f5cac9cc8be10ed51f7a3f3
    builder_test.go:118: test build error: remove C:\Users\mvasek\AppData\Local\Temp\TestBuilder_Concurrency3717259113
\001\.func\builds\by-hash\8cf6addafdcbc495ab800c0a8210f7ca4c486ee17f5cac9cc8be10ed51f7a3f3\config.json: The process ca
nnot access the file because it is being used by another process.
mv .\config.json .\oci\blobs\sha256\979f5a8533d239b98f596c2333c02d8ae75568b93f227e71fdf89954e034c745
rm C:\Users\mvasek\AppData\Local\Temp\TestBuilder_Concurrency3717259113\001\.func\builds\by-pid\23056
rm C:\Users\mvasek\AppData\Local\Temp\TestBuilder_Concurrency3717259113\001\.func\builds\by-hash\8cf6addafdcbc495ab800
c0a8210f7ca4c486ee17f5cac9cc8be10ed51f7a3f3
    builder_test.go:101: test build error: rename C:\Users\mvasek\AppData\Local\Temp\TestBuilder_Concurrency3717259113
\001\.func\builds\by-hash\8cf6addafdcbc495ab800c0a8210f7ca4c486ee17f5cac9cc8be10ed51f7a3f3\config.json C:\Users\mvasek
\AppData\Local\Temp\TestBuilder_Concurrency3717259113\001\.func\builds\by-hash\8cf6addafdcbc495ab800c0a8210f7ca4c486ee
17f5cac9cc8be10ed51f7a3f3\oci\blobs\sha256\979f5a8533d239b98f596c2333c02d8ae75568b93f227e71fdf89954e034c745: The syste
m cannot find the path specified.
--- FAIL: TestBuilder_Concurrency (0.09s)
FAIL

This is the error I am getting on my Windows machine now. Previously the test just hanged till timeout.

This looks like a legitimate bug to me; it appears the test was exiting when a single builder returned on the done channel, rather than waiting for both
/lgtm !

@lance please override the failing test.

@lance  PTAL

@lkingland PTAL


0049 - Group Anagrams

Description of the Problem
Given an array of strings strs, group the anagrams together. You can return the answer in any order.
An Anagram is a word or phrase formed by rearranging the letters of a different word or phrase, typically using all the original letters exactly once.
Example 1:
Input: strs = ["eat","tea","tan","ate","nat","bat"]
Output: [["bat"],["nat","tan"],["ate","eat","tea"]]

Example 2:
Input: strs = [""]
Output: [[""]]

Example 3:
Input: strs = ["a"]
Output: [["a"]]

Constraints:

1 <= strs.length <= 104
0 <= strs[i].length <= 100
strs[i] consists of lower-case English letters.

Code
class Solution:
    def groupAnagrams(self, strs: List[str]) -> List[List[str]]:

Link To The LeetCode Problem
LeetCode

@vJechsmayr I would like to work on this

I shall work on this in python. Could you assign me this.I love solving problems


Add support for immutable timestamps

When Laravel is configured to use CarbonImmutable when generating date objects (e.g. Carbon instances for model timestamps), this package fails as Carbon is type hinted.
This PR updates the typehint to CarbonInterface so that both Carbon and CarbonImmutable are supported.

Thanks! Released in 1.4.1.


volume and youtube search doesnt work

Describe the bug
When i type =volume 90 or less the bot will just leave and when i try typing =play darude sandstorm, it wont find the song but when i paste the link then it will work.

You need to have 64bit java installed & selected as the default binary for java.
You have to use 0.2.10 for having a working YouTube search afaik

As stated, you are likely using an outdated version of the bot or an incorrect java version. Regardless, please use the bug report form with debug info in the future, as there isn't enough information in your description to find the cause of the problem.


⚠ ClamAV has degraded performance

In 8d89d47, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 136 ms

Resolved: ClamAV performance has improved in 6828a89 after 10 minutes.


XEP-0423: XMPP Compliance Suites 2020

Please add support of https://xmpp.org/extensions/xep-0423.html
Which replace:

XEP-0412: XMPP Compliance Suites 2019: https://xmpp.org/extensions/xep-0412.html
XEP-0387: XMPP Compliance Suites 2018: https://xmpp.org/extensions/xep-0387.html
XEP-0375: XMPP Compliance Suites 2016: https://xmpp.org/extensions/xep-0375.html
XEP-0302: XMPP Compliance Suites 2012: https://xmpp.org/extensions/xep-0302.html
XEP-0270: XMPP Compliance Suites 2010: https://xmpp.org/extensions/xep-0270.html
XEP-0243: XMPP Server Compliance 2009: https://xmpp.org/extensions/xep-0243.html
XEP-0242: XMPP Client Compliance 2009: https://xmpp.org/extensions/xep-0242.html
XEP-0216: XMPP Intermediate Server 2008: https://xmpp.org/extensions/xep-0216.html
XEP-0212: XMPP Basic Server 2008: https://xmpp.org/extensions/xep-0212.html
XEP-0211: XMPP Basic Client 2008: https://xmpp.org/extensions/xep-0211.html
XEP-0073: Basic IM Protocol Suite: https://xmpp.org/extensions/xep-0073.html

Have you looked for RFCs and XEPs listed in?

Just found out about Jackal so i thought i'd take a few minutes to make a list of the XEPs to implement the 2020 Compliance Suite.
The compliance suite is divded into 4 categories (core, web, IM, mobile) and each category has criteria for a basic server, and for an advanced server. I ticked the boxes of the specs marked as implemented on the README
Core server featues

core

[x] 0030
-[ ] 0114

web
-[ ] 0206
IM

[x] 0054
-[ ] 0280
-[ ] 0045
-[ ] 0249
-[ ] 0363

mobile
-[ ] 0198
-[ ] 0352

Advanced server features

core
-[ ] 0368
-[ ] 0115

[x] 0163

IM
-[ ] 0398
-[ ] 0153

[x] 0191
-[ ] 0048
-[ ] 0313
-[ ] 0410
-[ ] 0411
-[ ] 0223
[x] 0049
-[ ] 0198
-[ ] 0313

mobile
-[ ] 0357

Plus the future development section has some optional yet interesting proposals. Good luck on your project!


Check and block sensitive words in the topic and reply contents

The admin portal should support to add some sensitive words to the blacklist. If anyone wants to post a topic or reply, in which some words are in the blacklist, we should block them from posting.

Working on this.


windows_task isn't idempotent

I observed this running chef-zero; I will try to reproduce it using chef-client.
Changing the command attribute in a recipe did not result in the task being updated.

I need more information here. Can you provide a recipe and the log of what chef-client did

The windows task isn't designed to be idempotent. It needs to be updated. The code shows the provider exiting if the task exists without checking the attributes. There is also a :change action that does update the task. :create and :change should be merged into a single action in my opinion.

@Tech356 agreed

@jdmundrawala do you still want an example?

example would be nice

Example recipe:
windows_task "Test task" do
  command "echo Something"
  action [:create, :run]
end

Results of running chef-client -z -o windows_task-is-not-idempotent:
[2015-02-09T11:06:46-05:00] INFO: Starting chef-zero on port 8889 with repositor
y at repository at C:/@Kiln/chef
  One version per cookbook

[2015-02-09T11:06:46-05:00] WARN:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
attacks.

...

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Starting Chef Client, version 11.12.8
[2015-02-09T11:06:49-05:00] INFO: *** Chef 11.12.8 ***
[2015-02-09T11:06:49-05:00] INFO: Chef-client pid: 4756
[2015-02-09T11:06:54-05:00] WARN: Run List override has been provided.
[2015-02-09T11:06:54-05:00] WARN: Original Run List: []
[2015-02-09T11:06:54-05:00] WARN: Overridden Run List: [recipe[windows_task-is-n
ot-idempotent]]
[2015-02-09T11:06:54-05:00] INFO: Run List is [recipe[windows_task-is-not-idempo
tent]]
[2015-02-09T11:06:54-05:00] INFO: Run List expands to [windows_task-is-not-idemp
otent]
[2015-02-09T11:06:54-05:00] INFO: Starting Chef Run for kenny-evitt
[2015-02-09T11:06:54-05:00] INFO: Running start handlers
[2015-02-09T11:06:54-05:00] INFO: Start handlers complete.
[2015-02-09T11:06:54-05:00] INFO: HTTP Request Returned 404 Not Found : Object n
ot found: /reports/nodes/kenny-evitt/runs
resolving cookbooks for run list: ["windows_task-is-not-idempotent"]
[2015-02-09T11:06:55-05:00] INFO: Loading cookbooks [windows_task-is-not-idempot
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Synchronizing Cookbooks:
[2015-02-09T11:06:55-05:00] INFO: Storing updated cookbooks/windows_task-is-not-
idempotent/metadata.rb in the cache.
  - windows_task-is-not-idempotent
  - windows
  - chef_handler
Compiling Cookbooks...
Converging 1 resources
Recipe: windows_task-is-not-idempotent::default
  * windows_task[Test task] action create[2015-02-09T11:06:59-05:00] INFO: Proce
ssing windows_task[Test task] action create (windows_task-is-not-idempotent::def
ault line 10)
[2015-02-09T11:06:59-05:00] INFO: windows_task[Test task] task created

  * windows_task[Test task] action run[2015-02-09T11:06:59-05:00] INFO: Processi
ng windows_task[Test task] action run (windows_task-is-not-idempotent::default l
ine 10)
[2015-02-09T11:07:00-05:00] INFO: windows_task[Test task] task ran

[2015-02-09T11:07:00-05:00] WARN: Skipping final node save because override_runl
ist was given
[2015-02-09T11:07:00-05:00] INFO: Chef Run complete in 5.994599 seconds

Running handlers:
[2015-02-09T11:07:00-05:00] INFO: Running report handlers
Running handlers complete
[2015-02-09T11:07:00-05:00] INFO: Report handlers complete
Chef Client finished, 2/2 resources updated in 14.013401 seconds

Change recipe:
windows_task "Test task" do
  command "echo Something else"
  action [:create, :run]
end

Results of re-running chef-client -z -o windows_task-is-not-idempotent:
[2015-02-09T11:15:06-05:00] INFO: Starting chef-zero on port 8889 with repositor
y at repository at C:/@Kiln/chef
  One version per cookbook

[2015-02-09T11:15:06-05:00] WARN:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
attacks.

...

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Starting Chef Client, version 11.12.8
[2015-02-09T11:15:10-05:00] INFO: *** Chef 11.12.8 ***
[2015-02-09T11:15:10-05:00] INFO: Chef-client pid: 14196
[2015-02-09T11:15:15-05:00] WARN: Run List override has been provided.
[2015-02-09T11:15:15-05:00] WARN: Original Run List: []
[2015-02-09T11:15:15-05:00] WARN: Overridden Run List: [recipe[windows_task-is-n
ot-idempotent]]
[2015-02-09T11:15:15-05:00] INFO: Run List is [recipe[windows_task-is-not-idempo
tent]]
[2015-02-09T11:15:15-05:00] INFO: Run List expands to [windows_task-is-not-idemp
otent]
[2015-02-09T11:15:15-05:00] INFO: Starting Chef Run for kenny-evitt
[2015-02-09T11:15:15-05:00] INFO: Running start handlers
[2015-02-09T11:15:15-05:00] INFO: Start handlers complete.
[2015-02-09T11:15:15-05:00] INFO: HTTP Request Returned 404 Not Found : Object n
ot found: /reports/nodes/kenny-evitt/runs
resolving cookbooks for run list: ["windows_task-is-not-idempotent"]
[2015-02-09T11:15:16-05:00] INFO: Loading cookbooks [windows_task-is-not-idempot
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Synchronizing Cookbooks:
[2015-02-09T11:15:16-05:00] INFO: Storing updated cookbooks/windows_task-is-not-
idempotent/recipes/default.rb in the cache.
  - windows_task-is-not-idempotent
  - windows
  - chef_handler
Compiling Cookbooks...
Converging 1 resources
Recipe: windows_task-is-not-idempotent::default
  * windows_task[Test task] action create[2015-02-09T11:15:19-05:00] INFO: Proce
ssing windows_task[Test task] action create (windows_task-is-not-idempotent::def
ault line 10)
[2015-02-09T11:15:19-05:00] INFO: windows_task[Test task] task already exists -
nothing to do
 (up to date)
  * windows_task[Test task] action run[2015-02-09T11:15:19-05:00] INFO: Processi
ng windows_task[Test task] action run (windows_task-is-not-idempotent::default l
ine 10)
[2015-02-09T11:15:19-05:00] INFO: windows_task[Test task] task ran

[2015-02-09T11:15:19-05:00] WARN: Skipping final node save because override_runl
ist was given
[2015-02-09T11:15:19-05:00] INFO: Chef Run complete in 4.264427 seconds

Running handlers:
[2015-02-09T11:15:19-05:00] INFO: Running report handlers
Running handlers complete
[2015-02-09T11:15:19-05:00] INFO: Report handlers complete
Chef Client finished, 1/2 resources updated in 12.874287 seconds

The task action Details or Program/script remain echo Something instead of being updated to echo Something else.

Thanks.
I think the right course of action here is to do what @Tech356 said. :create should make sure the task is in the state specified, not just that it exists. We should probably leave :change alone for now, but I don't really see a reason for it to noop of the task does not exist. It should either error, because you've said that it exists and it does not, or we should just create it.
cc @btm @smurawski

@jdmundrawala @Tech356 Agreed.  We should validate that the task as specified exists, not just that a task of that name exists, and if it needs to be brought into compliance - do it.
So :+1:

yeah :+1:. my only concern would be consistency around create really being "create_or_modify." It looks like the user resource in core chef will create or modify a user when the action is create. So this seems right.

If there is a use case for the current way :create works, a :create_if_missing action can be added.

IIRC, some of us talked a while back about how a create_if_missing action just duplicates create with a not_if/only_if conditional, and so it mostly creates unnecessary code to maintain.

:create has been updated to update the existing task if the user or command has changed, or completely if force is specified. via #204


DTZ005 false postitive for tz=None

import datetime

datetime.datetime.now(tz=None)
# The use of `datetime.datetime.now()` without `tz` argument is not allowed Ruff DTZ005

ruff 0.1.9

I think this is arguably a true positive, since tz=None is equivalent to omitting it, in that it won't produce a timezone-aware object. Perhaps the documentation and message need to be tweaked to reflect that?

I think it’s arguable. No arguments could be a mistake (and is a common one). Explicitly passing None is acknowledging that you actually want None. In my case I want to use UTC everywhere except in a helper script.
But yes at least an error message tweak would be nice.

Yeah I also view it as borderline. I could definitely be convinced to ignore it. May need more opinions. @AlexWaygood, what do you think?

It seems like we're following what the original flake8 rule does here, which is explicitly going out of its way to make sure that calls are still flagged when None is passed to this argument: https://github.com/pjknkda/flake8-datetimez/blob/1bcda18963ef61861a57c86f83741172884aadd1/flake8_datetimez.py#L96-L110. (But that's obviously not decisive -- if this is bad behaviour, we shouldn't do it!)
I... am sort-of inclined to leave this rule as it is, though. It's simple to explain currently: "aware datetimes are good; naive datetimes are bad". Keeping a rule simple to explain to users and easy to describe in documentation is valuable. Moreover, if we changed the behaviour here, it's possible people who don't understand the rationale behind the ruule might think that they're "fixing" the issue by passing None (since linter stops complaining at them). That wouldn't necessarily be true.
I feel like if you're working in a domain where you don't need aware timezones, you can probably just not enable this rule on your project. And if you have a specific script in a larger project where it's just that script that doesn't need aware timezones, you can probably just put # ruff: noqa: DTZ005 somewhere near the top of the file.

it's possible people who don't understand the rationale behind the ruule might think that they're "fixing" the issue by passing None (since linter stops complaining at them)

That's a fair point, I hadn't thought of that.
I guess the other recommendation is to do:
datetime.now(tz=timezone.utc).astimezone()

Which I think gives you the local timezone, although it's not as simple as tz=None
Either way, whatever you choose is fine by my, I just wanted to bring it to attention.

I think we should just improve the rule documentation and recommendation here


Enrich default corfu command line

Enrich the default Corfu command line by the cmd line we have in tanuki

done #199


outline-fix

Outlines in Kicad are really messed up in the latest revision of corne-cherry, so 3d renderer (Alt+3) doesn't work.
---------------------------
kicad Information
---------------------------
Unable to find segment with an endpoint of (181.3 mm, 151.775 mm).

Cannot determine the board outline.
---------------------------
OK
---------------------------

If you start gradualy move points to match there are a few dozens of those messages so it takes a while to fix. I don't know if it makes sense to post as a pull request because you should really trust me but all I did is moved connecting lines a little but to match the corners (I didn't move corners).

Closing for now, I could've messed it up but the idea should be clear.

I'm still fairly n00by with Kicad but I've seen these errors/warnings too. Thanks for fixing them, I might grab your commit :+1:


[docs] CToSwift: Add section on methods

There's a lot here, so I might have missed something, but I think this document is complete!

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test macOS

@swift-ci Please smoke test macOS

@swift-ci Please smoke test macOS


dump-tables and load-tables --tables flag does not work

When running either of those commands with the --tables flag, the tables get passed into the function as a list of strings (as per the function signature), but the code was previously written with the tables being passed as a comma separated list.
Please update those functions to support the list of strings when --tables is specified at the command-line.

Also test if those commands even work... If not, get rid of them. If yes, include them in our integration testing.


Updating 5-logging to use py.test

@waprin this is identical to the last one, as the tests do not change between step 4 and 5.

lgtm


move cloud and test dependencies to "extras"

Most downstream users are not on multiple cloud providers, nor do they need to run the tests.  Allowing the option to select only what they need simplifies downstream dependency resolutions and prevents conflicts.
(I went with the dev- pattern tests instead of poetry groups, as the CONTRIBUTING instructions pointed towards using pip/requirements and not mandating poetry directly.)

We use Python (surprise!) and support development on multiple CPU architectures (x86_64, arm64 and Operating Systems (Mac, Linux) and in turn support deployment to Linux on multiple CPU architectures.  To interact with the wider Python packaging ecosystem  we could:

(A) Say that everyone needs multiple native code compilers and library headers installed on their workstation, maintaining package lists for both Mac and a hodgepodge of Linux distros.
(B) Require all 3rd party python packages to be available as wheels, building the missing ones ourselves.

(A) perhaps a more common choice but also an endless series of "IT" style support tarpits while (B) is closer to a problem amendable to software engineering, so we went with (B).  We are happy to spin up CI workers and build wheels as needed but in the case of things like test dependencies the idiomatic thing to do is usually  not to require them at all. (pytest-parametrization does not provide a wheel if that context was unclear.)
For the cloud provider case, due to the dynamic nature of python packaging pip uses a backtracking resolver with somewhat unpredictable performance characteristics.  Having less packages in the transitive graph thus always has marginally benefit and since most companies always use a single cloud provider, that's usually low hanging fruit for limiting scope.
Let me know that helps or if other context would be helpful.

Hi @cburroughs !
Sorry for the huge delay in our response, and thanks for your explanation above.
I think the points you made make sense. That being said, my primary concern is the same that @elongl brought above - which is breaking setup for existing Elementary users.
We may do this separation eventually with an appropriate heads-up to users, but right now I feel the risk outweighs the benefit.
That being said, for test packages the decision is more straightforward, so I added only this change to a separate PR:
https://github.com/elementary-data/elementary/pull/1537
Closing this one.


Vertical scroll not work?

Hi, it's a great view controller and very useful. I really love it.
Just a quick question. My content size is over the screen height so I add a scrollview on my view then add the banner on it. It looks like scroll not work anymore. Is it because that swipe gesture blocks the scroll gesture?
Thanks!

Thanks for your feedback.
I've add a scrollview test in the example project and it works well. You can clone the project and take a look and I use the PageViewController make banner startRolling without using custom gesture code. So, the problem maybe because of your scroll view's content size.

Works perfect, thx!!!!!