Ignoring /run and /var/run from the list of packaged directories

Description
This PR excludes /var/run and /run permissions from being modified upon package installation.
Issues Resolved
Resolves #284
Check List

[x] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[ ] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Permissions on /run are not affected after installation of the package:
[root@alma ~]# ls -lsah / | grep run
   0 drwxr-xr-x  15 root   root    440 Jun 28 17:42 run
[root@alma ~]# yum install /wazuh-indexer-4.9.0.x86_64.rpm
Last metadata expiration check: 1:37:08 ago on Fri Jun 28 16:05:32 2024.
Dependencies resolved.
======================================================================================================================================================================================
 Package                                        Architecture                            Version                                   Repository                                     Size
======================================================================================================================================================================================
Installing:
 wazuh-indexer                                  x86_64                                  4.9.0-0                                   @commandline                                  813 M

Transaction Summary
======================================================================================================================================================================================
Install  1 Package

Total size: 813 M
Installed size: 1.0 G
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                1/1
  Running scriptlet: wazuh-indexer-4.9.0-0.x86_64                                                                                1/1
  Installing       : wazuh-indexer-4.9.0-0.x86_64                                                                                1/1
  Running scriptlet: wazuh-indexer-4.9.0-0.x86_64                                                                                1/1
### NOT starting on installation, please execute the following statements to configure wazuh-indexer service to start automatically using systemd
 sudo systemctl daemon-reload
 sudo systemctl enable wazuh-indexer.service
### You can start wazuh-indexer service by executing
 sudo systemctl start wazuh-indexer.service

  Verifying        : wazuh-indexer-4.9.0-0.x86_64                                                                                1/1

Installed:
  wazuh-indexer-4.9.0-0.x86_64

Complete!
[root@alma ~]# ls -lsah / | grep run
   0 drwxr-xr-x  16 root   root    460 Jun 28 17:42 run

While testing the change to using /var/run instead of /run in Alma Linux 8, I get the following output on package installation:

[/usr/lib/tmpfiles.d/wazuh-indexer.conf:1] Line references path below legacy directory /var/run/, updating /var/run/wazuh-indexer → /run/wazuh-indexer; please update the tmpfiles.d/ drop-in file accordingly.

  Verifying        : wazuh-indexer-4.9.0-0.x86_64                                                                                1/1

Installed:
  wazuh-indexer-4.9.0-0.x86_64

Complete!

Cannot reproduce on RHEL 7
[vagrant@rhel7 ~]$ sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=SecretPassword.1234 yum install 'opensearch-2.13.0'
Failed to set locale, defaulting to C
Loaded plugins: product-id, search-disabled-repos
Resolving Dependencies
--> Running transaction check
---> Package opensearch.x86_64 0:2.13.0-1 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================================================================================================================
 Package                                        Arch                                       Version                                         Repository                                          Size
====================================================================================================================================================================================================
Installing:
 opensearch                                     x86_64                                     2.13.0-1                                        opensearch-2.x                                     799 M

Transaction Summary
====================================================================================================================================================================================================
Install  1 Package

Total download size: 799 M
Installed size: 1.1 G
Is this ok [y/d/N]: y
Downloading packages:
warning: /var/cache/yum/x86_64/7Server/opensearch-2.x/packages/opensearch-2.13.0-linux-x64.rpm: Header V4 RSA/SHA512 Signature, key ID 9310d3fc: NOKEY=========== ]  18 MB/s | 793 MB  00:00:00 ETA
Public key for opensearch-2.13.0-linux-x64.rpm is not installed
opensearch-2.13.0-linux-x64.rpm                                                                                | 799 MB  00:00:45
Retrieving key from https://artifacts.opensearch.org/publickeys/opensearch.pgp
Importing GPG key 0x9310D3FC:
 Userid     : "OpenSearch project<EMAIL_ADDRESS> Fingerprint: c5b7 4989 65ef d1c2 924b a9d5 39d3 1987 9310 d3fc
 From       : https://artifacts.opensearch.org/publickeys/opensearch.pgp
Is this ok [y/N]: y
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : opensearch-2.13.0-1.x86_64                                                                                1/1
### NOT starting on installation, please execute the following statements to configure opensearch service to start automatically using systemd
 sudo systemctl daemon-reload
 sudo systemctl enable opensearch.service
### You can start opensearch service by executing
 sudo systemctl start opensearch.service
### Create opensearch demo certificates in /etc/opensearch/
 See demo certs creation log in /var/log/opensearch/install_demo_configuration.log
### Breaking change in packaging since 2.13.0
 In 2.13.0 and later releases of OpenSearch, we have changed the permissions associated with access to installed files
 If you are configuring tools that require read access to the OpenSearch configuration files, we recommend you add the user that runs these tools to the 'opensearch' group
 For more information, see https://github.com/opensearch-project/opensearch-build/pull/4043
  Verifying  : opensearch-2.13.0-1.x86_64                                                                                1/1

Installed:
  opensearch.x86_64 0:2.13.0-1

Complete!

Can reproduce on OpenSearch 2.13.0 + ALMA 8
[vagrant@alma8 ~]$ sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-2.x.repo -o /etc/yum.repos.d/opensearch-2.x.repo
NSEARCH_INITIAL_ADMIN_PASSWORD=SecretPassword.1234 yum install 'opensearch-2.13.0'  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   242  100   242    0     0   1581      0 --:--:-- --:--:-- --:--:--  1571
[vagrant@alma8 ~]$ sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=SecretPassword.1234 yum install 'opensearch-2.13.0' -y
Failed to set locale, defaulting to C.UTF-8
AlmaLinux 8 - BaseOS                                                                                2.2 MB/s | 4.0 MB     00:01
AlmaLinux 8 - AppStream                                                                                6.7 MB/s |  11 MB     00:01
AlmaLinux 8 - Extras                                                                                31 kB/s |  21 kB     00:00
Extra Packages for Enterprise Linux 8 - x86_64                                                                                8.2 MB/s |  14 MB     00:01
OpenSearch 2.x                                                                                3.6 kB/s | 498  B     00:00
OpenSearch 2.x                                                                                58 kB/s | 4.2 kB     00:00
Importing GPG key 0x9310D3FC:
 Userid     : "OpenSearch project<EMAIL_ADDRESS> Fingerprint: C5B7 4989 65EF D1C2 924B A9D5 39D3 1987 9310 D3FC
 From       : https://artifacts.opensearch.org/publickeys/opensearch.pgp
OpenSearch 2.x                                                                                1.2 MB/s | 356 kB     00:00
Dependencies resolved.
======================================================================================================================================================================
 Package                                 Architecture                        Version                                Repository                                   Size
======================================================================================================================================================================
Installing:
 opensearch                              x86_64                              2.13.0-1                               opensearch-2.x                              799 M

Transaction Summary
======================================================================================================================================================================
Install  1 Package

Total download size: 799 M
Installed size: 1.1 G
Downloading Packages:
opensearch-2.13.0-linux-x64.rpm                                                                                48 MB/s | 799 MB     00:16
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                48 MB/s | 799 MB     00:16
OpenSearch 2.x                                                                                14 kB/s | 4.2 kB     00:00
Importing GPG key 0x9310D3FC:
 Userid     : "OpenSearch project<EMAIL_ADDRESS> Fingerprint: C5B7 4989 65EF D1C2 924B A9D5 39D3 1987 9310 D3FC
 From       : https://artifacts.opensearch.org/publickeys/opensearch.pgp
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                1/1
  Running scriptlet: opensearch-2.13.0-1.x86_64                                                                                1/1
  Installing       : opensearch-2.13.0-1.x86_64                                                                                1/1
  Running scriptlet: opensearch-2.13.0-1.x86_64                                                                                1/1
[opensearch.conf:1] Line references path below legacy directory /var/run/, updating /var/run/opensearch → /run/opensearch; please update the tmpfiles.d/ drop-in file accordingly.
### NOT starting on installation, please execute the following statements to configure opensearch service to start automatically using systemd
 sudo systemctl daemon-reload
 sudo systemctl enable opensearch.service
### You can start opensearch service by executing
 sudo systemctl start opensearch.service
### Create opensearch demo certificates in /etc/opensearch/
 See demo certs creation log in /var/log/opensearch/install_demo_configuration.log
### Breaking change in packaging since 2.13.0
 In 2.13.0 and later releases of OpenSearch, we have changed the permissions associated with access to installed files
 If you are configuring tools that require read access to the OpenSearch configuration files, we recommend you add the user that runs these tools to the 'opensearch' group
 For more information, see https://github.com/opensearch-project/opensearch-build/pull/4043

[/usr/lib/tmpfiles.d/opensearch.conf:1] Line references path below legacy directory /var/run/, updating /var/run/opensearch → /run/opensearch; please update the tmpfiles.d/ drop-in file accordingly.

  Verifying        : opensearch-2.13.0-1.x86_64                                                                                1/1

Installed:
  opensearch-2.13.0-1.x86_64

Complete!
[vagrant@alma8 ~]$

Can reproduce on OpenSearch 2.13.0 + RHEL 9
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                1/1
  Running scriptlet: opensearch-2.13.0-1.x86_64                                                                                1/1
  Installing       : opensearch-2.13.0-1.x86_64                                                                                1/1
  Running scriptlet: opensearch-2.13.0-1.x86_64                                                                                1/1
/usr/lib/tmpfiles.d/opensearch.conf:1: Line references path below legacy directory /var/run/, updating /var/run/opensearch → /run/opensearch; please update the tmpfiles.d/ drop-in file accordingly.
### NOT starting on installation, please execute the following statements to configure opensearch service to start automatically using systemd
 sudo systemctl daemon-reload
 sudo systemctl enable opensearch.service
### You can start opensearch service by executing
 sudo systemctl start opensearch.service
### Create opensearch demo certificates in /etc/opensearch/
 See demo certs creation log in /var/log/opensearch/install_demo_configuration.log
### Breaking change in packaging since 2.13.0
 In 2.13.0 and later releases of OpenSearch, we have changed the permissions associated with access to installed files
 If you are configuring tools that require read access to the OpenSearch configuration files, we recommend you add the user that runs these tools to the 'opensearch' group
 For more information, see https://github.com/opensearch-project/opensearch-build/pull/4043

/usr/lib/tmpfiles.d/opensearch.conf:1: Line references path below legacy directory /var/run/, updating /var/run/opensearch → /run/opensearch; please update the tmpfiles.d/ drop-in file accordingly.

Couldn't write '64' to 'kernel/random/read_wakeup_threshold', ignoring: No such file or directory

  Verifying        : opensearch-2.13.0-1.x86_64                                                                                1/1
Installed products updated.

Installed:
  opensearch-2.13.0-1.x86_64

Complete!
[vagrant@rhel9 ~]$

There is an issue on OpenSearch about this:

https://github.com/opensearch-project/opensearch-build/issues/2098

Tests on RPM were successful, using RHEL9.

Installed<EMAIL_ADDRESS>(no warnings)
Installed<EMAIL_ADDRESS>(upgrade - no warnings9
Installed<EMAIL_ADDRESS>(install successful)

[vagrant@rhel9 ~]$ sudo yum localinstall wazuh-indexer-4.8.0-1.x86_64.rpm -y
Last metadata expiration check: 0:02:51 ago on Tue 02 Jul 2024 11:49:22 AM UTC.
Dependencies resolved.
=================================================================================================
 Package                   Architecture       Version             Repository                Size
=================================================================================================
Installing:
 wazuh-indexer             x86_64             4.8.0-1             @commandline             743 M

Transaction Summary
=================================================================================================
Install  1 Package

Total size: 743 M
Installed size: 1.0 G
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                         1/1
  Running scriptlet: wazuh-indexer-4.8.0-1.x86_64                                            1/1
  Installing       : wazuh-indexer-4.8.0-1.x86_64                                            1/1
  Running scriptlet: wazuh-indexer-4.8.0-1.x86_64                                            1/1
Created opensearch keystore in /etc/wazuh-indexer/opensearch.keystore

Couldn't write '64' to 'kernel/random/read_wakeup_threshold', ignoring: No such file or directory

  Verifying        : wazuh-indexer-4.8.0-1.x86_64                                            1/1
Installed products updated.

Installed:
  wazuh-indexer-4.8.0-1.x86_64

Complete!
[vagrant@rhel9 ~]$ sudo yum localinstall wazuh-indexer_4.9.0-0_x86_64_49a7b40.rpm -y
Last metadata expiration check: 0:03:44 ago on Tue 02 Jul 2024 11:49:22 AM UTC.
Dependencies resolved.
=================================================================================================
 Package                   Architecture       Version             Repository                Size
=================================================================================================
Upgrading:
 wazuh-indexer             x86_64             4.9.0-0             @commandline             813 M

Transaction Summary
=================================================================================================
Upgrade  1 Package

Total size: 813 M
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                         1/1
  Running scriptlet: wazuh-indexer-4.9.0-0.x86_64                                            1/2
  Upgrading        : wazuh-indexer-4.9.0-0.x86_64                                            1/2
  Running scriptlet: wazuh-indexer-4.9.0-0.x86_64                                            1/2
### NOT starting on installation, please execute the following statements to configure wazuh-indexer service to start automatically using systemd
 sudo systemctl daemon-reload
 sudo systemctl enable wazuh-indexer.service
### You can start wazuh-indexer service by executing
 sudo systemctl start wazuh-indexer.service

  Running scriptlet: wazuh-indexer-4.8.0-1.x86_64                                            2/2
  Cleanup          : wazuh-indexer-4.8.0-1.x86_64                                            2/2
  Running scriptlet: wazuh-indexer-4.8.0-1.x86_64                                            2/2
Couldn't write '64' to 'kernel/random/read_wakeup_threshold', ignoring: No such file or directory

  Verifying        : wazuh-indexer-4.9.0-0.x86_64                                            1/2
  Verifying        : wazuh-indexer-4.8.0-1.x86_64                                            2/2
Installed products updated.

Upgraded:
  wazuh-indexer-4.9.0-0.x86_64

Complete!
[vagrant@rhel9 ~]$ sudo yum localinstall wazuh-dashboard-4.8.0-1.x86_64.rpm -y
Last metadata expiration check: 0:04:40 ago on Tue 02 Jul 2024 11:49:22 AM UTC.
Dependencies resolved.
=================================================================================================
 Package                    Architecture      Version              Repository               Size
=================================================================================================
Installing:
 wazuh-dashboard            x86_64            4.8.0-1              @commandline            275 M

Transaction Summary
=================================================================================================
Install  1 Package

Total size: 275 M
Installed size: 911 M
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                         1/1
  Running scriptlet: wazuh-dashboard-4.8.0-1.x86_64                                          1/1
  Installing       : wazuh-dashboard-4.8.0-1.x86_64                                          1/1
  Running scriptlet: wazuh-dashboard-4.8.0-1.x86_64                                          1/1
  Verifying        : wazuh-dashboard-4.8.0-1.x86_64                                          1/1
Installed products updated.

Installed:
  wazuh-dashboard-4.8.0-1.x86_64

Complete!

Tests on DEB were successful, using Ubuntu 22.04.
Installed<EMAIL_ADDRESS>(no warnings)
Installed<EMAIL_ADDRESS>(upgrade - no warnings)
Installed<EMAIL_ADDRESS>(install successful)

root@ubuntu:~# apt install /wazuh-indexer_4.9.0_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'wazuh-indexer' instead of '/wazuh-indexer_4.9.0_amd64.deb'
The following NEW packages will be installed:
  wazuh-indexer
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/851 MB of archives.
After this operation, 1077 MB of additional disk space will be used.
Get:1 /wazuh-indexer_4.9.0_amd64.deb wazuh-indexer amd64 4.9.0-0 [851 MB]
Selecting previously unselected package wazuh-indexer.
(Reading database ... 37456 files and directories currently installed.)
Preparing to unpack /wazuh-indexer_4.9.0_amd64.deb ...
Running Wazuh Indexer Pre-Installation Script
Unpacking wazuh-indexer (4.9.0-0) ...
Setting up wazuh-indexer (4.9.0-0) ...
Running Wazuh Indexer Post-Installation Script
### NOT starting on installation, please execute the following statements to configure wazuh-indexer service to start automatically using systemd
 sudo systemctl daemon-reload
 sudo systemctl enable wazuh-indexer.service
### You can start wazuh-indexer service by executing
 sudo systemctl start wazuh-indexer.service
root@ubuntu:~# ./wazuh-certs-tool.sh -A
02/07/2024 12:02:55 INFO: Generating the root certificate.
02/07/2024 12:02:55 INFO: Generating Admin certificates.
02/07/2024 12:02:55 INFO: Admin certificates created.
02/07/2024 12:02:55 INFO: Generating Wazuh indexer certificates.
02/07/2024 12:02:55 INFO: Wazuh indexer certificates created.
02/07/2024 12:02:55 INFO: Generating Filebeat certificates.
02/07/2024 12:02:56 INFO: Wazuh Filebeat certificates created.
02/07/2024 12:02:56 INFO: Generating Wazuh dashboard certificates.
02/07/2024 12:02:56 INFO: Wazuh dashboard certificates created.
root@ubuntu:~# tar -cvf ./wazuh-certificates.tar -C ./wazuh-certificates/ .

rm -rf ./wazuh-certificates
./
./wazuh-1-key.pem
./dashboard-key.pem
./root-ca.key
./node-1-key.pem
./admin.pem
./node-1.pem
./wazuh-1.pem
./dashboard.pem
./root-ca.pem
./admin-key.pem
root@ubuntu:~# NODE_NAME=node-1
root@ubuntu:~# mkdir /etc/wazuh-indexer/certs
tar -xf ./wazuh-certificates.tar -C /etc/wazuh-indexer/certs/ ./$NODE_NAME.pem ./$NODE_NAME-key.pem ./admin.pem ./admin-key.pem ./root-ca.pem
mv -n /etc/wazuh-indexer/certs/$NODE_NAME.pem /etc/wazuh-indexer/certs/indexer.pem
mv -n /etc/wazuh-indexer/certs/$NODE_NAME-key.pem /etc/wazuh-indexer/certs/indexer-key.pem
chmod 500 /etc/wazuh-indexer/certs
chmod 400 /etc/wazuh-indexer/certs/*
chown -R wazuh-indexer:wazuh-indexer /etc/wazuh-indexer/certs
root@ubuntu:~# systemctl daemon-reload
systemctl enable wazuh-indexer
systemctl start wazuh-indexer
Synchronizing state of wazuh-indexer.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable wazuh-indexer
root@ubuntu:~# /usr/share/wazuh-indexer/bin/indexer-security-init.sh
**************************************************************************
** This tool will be deprecated in the next major release of OpenSearch **
** https://github.com/opensearch-project/security/issues/1755           **
**************************************************************************
Security Admin v7
Will connect to <IP_ADDRESS>:9200 ... done
Connected as "CN=admin,OU=Wazuh,O=Wazuh,L=California,C=US"
OpenSearch Version: 2.13.0
Contacting opensearch cluster 'opensearch' and wait for YELLOW clusterstate ...
Clustername: wazuh-cluster
Clusterstate: GREEN
Number of nodes: 1
Number of data nodes: 1
.opendistro_security index does not exists, attempt to create it ... done (0-all replicas)
Populate config from /etc/wazuh-indexer/opensearch-security/
Will update '/config' with /etc/wazuh-indexer/opensearch-security/config.yml
   SUCC: Configuration for 'config' created or updated
Will update '/roles' with /etc/wazuh-indexer/opensearch-security/roles.yml
   SUCC: Configuration for 'roles' created or updated
Will update '/rolesmapping' with /etc/wazuh-indexer/opensearch-security/roles_mapping.yml
   SUCC: Configuration for 'rolesmapping' created or updated
Will update '/internalusers' with /etc/wazuh-indexer/opensearch-security/internal_users.yml
   SUCC: Configuration for 'internalusers' created or updated
Will update '/actiongroups' with /etc/wazuh-indexer/opensearch-security/action_groups.yml
   SUCC: Configuration for 'actiongroups' created or updated
Will update '/tenants' with /etc/wazuh-indexer/opensearch-security/tenants.yml
   SUCC: Configuration for 'tenants' created or updated
Will update '/nodesdn' with /etc/wazuh-indexer/opensearch-security/nodes_dn.yml
   SUCC: Configuration for 'nodesdn' created or updated
Will update '/whitelist' with /etc/wazuh-indexer/opensearch-security/whitelist.yml
   SUCC: Configuration for 'whitelist' created or updated
Will update '/audit' with /etc/wazuh-indexer/opensearch-security/audit.yml
   SUCC: Configuration for 'audit' created or updated
Will update '/allowlist' with /etc/wazuh-indexer/opensearch-security/allowlist.yml
   SUCC: Configuration for 'allowlist' created or updated
SUCC: Expected 10 config types for node {"updated_config_types":["allowlist","tenants","rolesmapping","nodesdn","audit","roles","whitelist","internalusers","actiongroups","config"],"updated_config_size":10,"message":null} is 10 (["allowlist","tenants","rolesmapping","nodesdn","audit","roles","whitelist","internalusers","actiongroups","config"]) due to: null
Done with success
root@ubuntu:~# curl -k -u admin:admin https://<WAZUH_INDEXER_IP_ADRESS>:9200
bash: WAZUH_INDEXER_IP_ADRESS: No such file or directory
root@ubuntu:~# curl -k -u admin:admin https://<IP_ADDRESS>:9200
{
  "name" : "node-1",
  "cluster_name" : "wazuh-cluster",
  "cluster_uuid" : "VwYpS9BWQ2SzAjym-FwgKQ",
  "version" : {
    "number" : "7.10.2",
    "build_type" : "deb",
    "build_hash" : "eb6e4fc0c2fbd15a5ccfae8baf1f2b2e540d774d",
    "build_date" : "2024-05-21T13:59:56.537046189Z",
    "build_snapshot" : false,
    "lucene_version" : "9.10.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}
root@ubuntu:~# apt install wazuh-dashboard
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  wazuh-dashboard
0 upgraded, 1 newly installed, 0 to remove and 12 not upgraded.
Need to get 186 MB of archives.
After this operation, 998 MB of additional disk space will be used.
Get:1 https://packages.wazuh.com/4.x/apt stable/main amd64 wazuh-dashboard amd64 4.8.0-1 [186 MB]
Fetched 186 MB in 14s (13.3 MB/s)
Selecting previously unselected package wazuh-dashboard.
(Reading database ... 38854 files and directories currently installed.)
Preparing to unpack .../wazuh-dashboard_4.8.0-1_amd64.deb ...
Creating wazuh-dashboard group... OK
Creating wazuh-dashboard user... OK
Unpacking wazuh-dashboard (4.8.0-1) ...
Setting up wazuh-dashboard (4.8.0-1) ...
root@ubuntu:~# NODE_NAME=dashboard
root@ubuntu:~# mkdir /etc/wazuh-dashboard/certs
tar -xf ./wazuh-certificates.tar -C /etc/wazuh-dashboard/certs/ ./$NODE_NAME.pem ./$NODE_NAME-key.pem ./root-ca.pem
mv -n /etc/wazuh-dashboard/certs/$NODE_NAME.pem /etc/wazuh-dashboard/certs/dashboard.pem
mv -n /etc/wazuh-dashboard/certs/$NODE_NAME-key.pem /etc/wazuh-dashboard/certs/dashboard-key.pem
chmod 500 /etc/wazuh-dashboard/certs
chmod 400 /etc/wazuh-dashboard/certs/*
chown -R wazuh-dashboard:wazuh-dashboard /etc/wazuh-dashboard/certs
root@ubuntu:~# systemctl daemon-reload
systemctl enable wazuh-dashboard
systemctl start wazuh-dashboard
root@ubuntu:~# systemctl status wazuh-dashboard
● wazuh-dashboard.service - wazuh-dashboard
     Loaded: loaded (/etc/systemd/system/wazuh-dashboard.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-07-02 12:06:24 UTC; 3min 58s ago
   Main PID: 3059 (node)
      Tasks: 11 (limit: 37682)
     Memory: 185.3M
        CPU: 5.113s
     CGroup: /system.slice/wazuh-dashboard.service
             └─3059 /usr/share/wazuh-dashboard/node/bin/node --no-warnings --max-http-header-size=65536 --unhandled-rejections=warn /usr/share/wazuh-dashboard/src/cli/dist

Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["info","savedobjects-service"],"pid":3059,"message":"Waiting until all >
Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["info","savedobjects-service"],"pid":3059,"message":"Starting saved obj>
Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["info","savedobjects-service"],"pid":3059,"message":"Creating index .ki>
Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["info","savedobjects-service"],"pid":3059,"message":"Pointing alias .ki>
Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["info","savedobjects-service"],"pid":3059,"message":"Finished in 120ms.>
Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["info","plugins-system"],"pid":3059,"message":"Starting [48] plugins: [>
Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["error","opensearch","data"],"pid":3059,"message":"[ResponseError]: Res>
Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["error","opensearch","data"],"pid":3059,"message":"[ResponseError]: Res>
Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["listening","info"],"pid":3059,"message":"Server running at https://0.0>
Jul 02 12:06:27 ubuntu opensearch-dashboards[3059]: {"type":"log","@timestamp":"2024-07-02T12:06:27Z","tags":["info","http","server","OpenSearchDashboards"],"pid":3059,"message":"ht>
root@ubuntu:~#


Weird crash that doesnt happen with FAPI

https://forum.quiltmc.org/t/quilt-fabric-api-crash/823

This is a manifestation of the mixin conflict between Satin and the Fabric core shader API, fixed in https://github.com/Ladysnake/Satin/commit/d79fe7f8a3f78afc7df38cc4ae4214afeb484d6e. Due to the load order being different between QFAPI and FAPI the mixin injection crashes immediately rather than silently failing and breaking Satin shaders - the same behaviour as FAPI can be observed using -Dloader.debug.loadLate=satin.
I noticed https://github.com/QuiltMC/quilt-standard-libraries/pull/295 for QSL; it might be a good idea to bring this to QFAPI as well, as upstream modules can also cause mixin priority issues.

https://github.com/comp500/Indium/issues/188 also shows the same crash; replicable with Satin 1.10.0 and QSL 5.0.0-beta.9+0.76.0-1.19.3


[SR-4373] shard string primary index by length to reduce memory usage

Memory usage test result:

length
8
12
16
24
32
48

capacity:62914544 size:40000000 ratio:1.6

string
2,496
2500
3725
3733
4351
4977

capacity:62914544 size:40000000 ratio:1.6

shardbylength
1,056
1300
1544
2032
2520
4977

It's better to describe the solution in annotation.

It's better to describe the solution in annotation.

what annotation?


Unable to Insert Row For Version in Schema History Table Error

Which version and edition of Flyway are you using?
I'm using the community edition Flyway version 9.9.0
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
I tried the 9.21.2 version and I get the same errors!
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
I'm using custom sbt command that runs my Scala code to perform the migrations
Which database are you using? (Type & version)
H2 version 2.1.214
Which operating system are you using?
Ubuntu 20.04
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
I have an application.conf that has the following:
my-platform.jdbc {
  driver = "org.h2.Driver"
  dbName = "my-platform-h2-test.db;DB_CLOSE_ON_EXIT=FALSE;MODE=MYSQL"
  url = "jdbc:h2:~/my-platform/database/"${my-platform.jdbc.dbName}
  user = "sa"
  migrations-table = "MyPlatformDBSchema"
  migrations-locations = [
    "classpath:h2/"
  ]
}

I'm reading that config using the Typesafe config and I traverse over the config and I run my sbt project which then results in the following error below:
INFO: Current version of schema "PUBLIC": << Empty Schema >>
Aug 28, 2023 9:33:23 PM org.flywaydb.core.internal.command.DbMigrate doMigrateGroup
INFO: Migrating schema "PUBLIC" to version "001 - baseline create initial tables"
org.flywaydb.core.internal.exception.FlywaySqlException: Unable to insert row for version '001' in Schema History table "PUBLIC"."MyPlatformDBSchema"
---------------------------------------------------------------------------------------------
SQL State  : 42S02
Error Code : 42102
Message    : Table "MyPlatformDBSchema" not found; SQL statement:
INSERT INTO "PUBLIC"."MyPlatformDBSchema" ("installed_rank", "version", "description", "type", "script", "checksum", "installed_by", "execution_time", "success") VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) [42102-214]

    at org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory.doAddAppliedMigration(JdbcTableSchemaHistory.java:177)
    at org.flywaydb.core.internal.schemahistory.SchemaHistory.addAppliedMigration(SchemaHistory.java:192)
    at org.flywaydb.core.internal.command.DbMigrate.doMigrateGroup(DbMigrate.java:402)
    at org.flywaydb.core.internal.command.DbMigrate.lambda$applyMigrations$1(DbMigrate.java:274)

I have in my src/main/resources folder a folder called h2, inside which I have my sql file called V001__baseline_create_initial_tables.sql which contains the schema that I want to use for my database like this:
--
-- Drop everything if exists
--

DROP ALL OBJECTS DELETE FILES;

--
-- Schema for my-platform
--
CREATE SCHEMA my_platform_schema AUTHORIZATION SA;
SET SCHEMA my_platform_schema;
....
....
-- The remaining create tables
....
....

What is it I'm doing wrong here?

https://github.com/flyway/flyway/issues/2877 helped me solve it!


cumcm-muban:0.3.0

I am submitting

[ ] a new package
[x] an update for a package

Description:

Change the code box style of the appendix page
Fix the issue that the title cannot be modified
Added function appendix to display appendix content
Set the stroke parameter for bold to 0.02857em

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Thank you!


Why not provided log4j？

Now，I use logback，must excludes log4j：
<dependency>
        <groupId>com.101tec</groupId>
        <artifactId>zkclient</artifactId>
        <version>${zkclient.version}</version>
        <exclusions>
          <exclusion>
            <artifactId>slf4j-log4j12</artifactId>
            <groupId>org.slf4j</groupId>
          </exclusion>
          <exclusion>
            <artifactId>log4j</artifactId>
            <groupId>log4j</groupId>
          </exclusion>
        </exclusions>
      </dependency>

+1 here.  The client should only use the slf4j api to enable consumers to provide their own log impl

Fix here: https://github.com/sgroschupf/zkclient/pull/56

Is this in a release version that is available now?  we seem to have a dependency on 0.8 of this library, is this fixed in 0.9 or an upcoming release?

+1 for a fix to this issue

Just merged #56 to master, if one of you guys could verify everything is as expected i would release that as 0.10 version! Thanks for your patience and interest!
Closing this one...


fix(types): change StringLiteral.has_escape to StringLiteral.hasEscape (#3580)

Description:

Fix the wrong typing mentioned in #3580.
Related issue (if exists):
#3580

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


Use Upstream of tools-python, Not Fork

Related to issue #28
In the course of examining a bug related to parsing, @goneall discovered that ntia-conformance-checker is using a fork, not the upstream, of tools-python.
This codebase should use the upstream to take advantage of ongoing improvements.
The only open question: Should this project switch to the upstream before the upstream accepts three commits from @linynjosh's fork? Or should the project switch to the upstream and, in the meantime, try to merge those changes? (Assuming those changes haven't been submitted and merged in the past sometime.)

The only open question: Should this project switch to the upstream before the upstream accepts three commits from @linynjosh's fork? Or should the project switch to the upstream and, in the meantime, try to merge those changes? (Assuming those changes haven't been submitted and merged in the past sometime.)

@nicoweidner @meretp Any suggestions?

The fork was last updated in August, so is quite out of date by now (since a lot of things happened in the meantime). I looked at the fork and it seemed the only addition it has compared to upstream is a PR that was rejected in tools-python. See this comment on the PR for the main reasons. The author never came back and replied.
In general, I would advise to use upstream, of course. And I also think that the changes from the PR mentioned above are not desirable. But if ntia-conformance-checker really relies on those changes, switching to upstream may cause some issues.
To save you some time: The main change from the PR was that for any given input file, all parsers (for the various formats) attempt to parse the file, regardless of its ending. This covers cases where a file was given the wrong ending (e.g. a yaml file that has a .json ending). I prefer to throw that back as a user error, though, and I would be surprised if it's important for the conformance checker to include this functionality.

Thanks @nicoweidner for the analysis.  From the description of the additional commits, it doesn't sound like it is essential to the operation of the conformance checker and we can probably just switch to the upstream.

Roger. Thank you, @nicoweidner!
I'll put in a PR to switch to the upstream.


[CVAT] Fix oracles lint workflow

Description
Installing poetry without virtualenv was always discouraged, but now it's prohibited by pip without explicit --break-system-packages flag. Instead of supplying it, I updated installation to satisfy pip and poetry recommendations.
Summary of changes

How test the changes

Related issues

https://github.com/humanprotocol/human-protocol/pull/2639

Reverting changes to oracles Dockerfiles for now. I was hoping it would be a harmless update, but faced issues that I don't have time to debug right now.


[Suggestion] Name gradle file additional options

The option to name gradle file differently require additional step of including the new module differently in settings.gradle
As the actual implementation of supporting build files with different name can vary between projects and their maintainers, it will eventually come to a function call in the settings file.
So basically what I am suggesting here is an additional option to name the include ':my-module function with a different configurable name like includeModule ':my-module

Totally makes sense! Internally on a lot of my personal and work projects, we always use a custom function for including modules which I've just always called 'includeProject' - I already have a TODO in the code (https://github.com/j-roskopf/ModuleMakerPlugin/blob/f142b379cfaf9a2abe4e5b519460adf8727f0e5c/src/main/kotlin/com/joetr/modulemaker/file/FileWriter.kt#L292) for this functionality. I think adding a custom settings field for specifying a list of 'include' keywords is probably how I'll tackle it


add new line in the tool tip

add new line in the tool tip

To do this, you'll want to use HTML to style the tooltip. Say you have a span element that you want a multi-line tooltip for. The following line would make it multi-line:
tooltip="
Hello I'm
 text!
"

The
 tag specifies a line break in HTML.


PIR: add concept of an pure term, use instead of isTermValue

For PIR, we really care about whether a term can have effects or not,
since this determines whether we can move or remove it. So we talk about
purity instead of whether the term is a "value" to avoid confusion.
Pure terms include variables and stuck builtin applications, which are cases
we care about. Handling the stuck builtins involves a lot of extra plumbing
to get the builtin info to where we need it, but this is okay as we'll
need to do some of this plumbing anyway for the typechecker.
Variables are also a little tricky, since PIR has non-strict variables
that can have effects at their use site. We have to be conservative in
many cases, but we can sometimes do better, e.g. the dependency analysis
pass now tracks the strictness of variables as it goes, so it can be
more precise.

This is a prelude to not eta-expanding builtins: I needed this first so we don't then make all the builtin bindings non-strict!
It also doesn't benefit the generated code as much as I'd hope, mostly because the Plutus Tx compiler makes (bad) strictness judgements, which could be improved.

I snuck in the change to not eta-expand builtins too, since it's easy enough.

Okay, I think I got everything.


docker:  hysteria2 without network_mode: host?

Describe the bug
I don't think this is a bug, more of a question.  How can I get this working without giving the container "host" networking mode?  I've tried added "NET_ADMIN" and/or "NET_BIND_SERVICE" to my docker-compose, as well as the appropriate ports but the container is unreachable.
  hysteria:
    image: tobyxdd/hysteria
    container_name: hysteria
    restart: always
    env_file:
      - docker.env
    cap_add:
      - NET_ADMIN
      - NET_BIND_SERVICE
    ports:
      - 993:993
    volumes:
      - ./hysteria/certs/:/certs/
      - ./hysteria/hysteria.yaml:/etc/hysteria.yaml
    command: ["server", "-c", "/etc/hysteria.yaml"]

You are publishing TCP port not UDP.
https://stackoverflow.com/questions/27596409/how-do-i-publish-a-udp-port-on-docker

Oh duh!


Add explicit lifetimes in constants

Trying to set up a development setup to start working on a simple UI and cargo suggested this fix :)
Elicit lifetimes in constants will be a compilation error in the future.
See https://github.com/rust-lang/rust/issues/115010

Thank you so much @sofiaritz! I learned something new, and ran a rustup update :)


how can i read  data  that "with totals" from clickhouse?

Your Question

The document you expected this should be explained
how can i read  data  that "with totals" from clickhouse?

Expected answer

Similar to below，
but i want to  use "[]map[string]interface{}" to receive data
<EMAIL_ADDRESS>package tests

import (
	"context"
	"github.com/stretchr/testify/require"
	"testing"

	"github.com/ClickHouse/clickhouse-go/v2"
	"github.com/stretchr/testify/assert"
)

func TestWithTotals(t *testing.T) {
	conn, err := GetNativeConnection(nil, nil, &clickhouse.Compression{
		Method: clickhouse.CompressionLZ4,
	})
	ctx := context.Background()
	require.NoError(t, err)
	const query = `
		SELECT
			number AS n
			, COUNT()
		FROM (
			SELECT number FROM system.numbers LIMIT 100
		) GROUP BY n WITH TOTALS
		`
	rows, err := conn.Query(ctx, query)
	require.NoError(t, err)
	var count int
	for rows.Next() {
		count++
		var (
			n uint64
			c uint64
		)
		require.NoError(t, rows.Scan(&n, &c))
	}
	require.Equal(t, 100, count)
	var (
		n, totals uint64
	)
	require.NoError(t, rows.Totals(&n, &totals))
	assert.Equal(t, uint64(0), n)
	assert.Equal(t, uint64(100), totals)
}

@TDTzzz this is gorm repository, nothing to do with clickhouse.


Change color of bubble card?

Maybe this has been asked before, but can your change the color of a bubble card? And if so how?
I would like to say that the new update is great, but it could be nice if there was a color option. Maybe in a future update?

Hi! This is already possible, you can take a look at that section in the documentation, I've added many examples.
https://github.com/Clooos/Bubble-Card?#styling


Breadcrumbs

Is it possible to modify SnappyGrav to show breadcrumbs?

I will add this option in the next release. Thank you for your suggestion.

Released version 1.4.0 with breadcrumbs

Thanks a lot for adding this feature. Looking forward to testing it on our installation.

I am having problems installing my snappygrav with Admin.
A command line (bin/gpm install snappygrav) is no problem even if some warning appears.
I know the reason for the error / warning.
I'm preparing a issue for grav-plugin-admin

Hi,
I noticed you had respond to the break error in another thread. I replaced with exit, but I cannot get around the invalid_response_error with this new version. As far as I can tell I have updated all the settings (which was working on your earlier version) and I can run the binary with  vendor/h4cc/wkhtmltopdf-amd64/bin/wkhtmltopdf-amd64 from the root of my grav installation
I have also checked that the absolute path is set in system.yaml and this is my console log:
Environment Name: *
info Knp\Snappy\Pdf OK
info wkhtmltopdf OK
info Cache: [true] Setting: [auto] Driver: [apcu]
info Page cache hit.

Hi,
from version v1.3.1-rc.1 the knp-snappy and wkhtmltopdf libraries are located in the vendor folder of the plugin, then your_site/user/plugins/snappygrav/vendor/*
I just improved the README

Thanks a lot iusvar. I installed wkhtmltopdf-amd64 package with composer from the plugin directory in stead of the webroot and that did the trick:-)


Exception diffing files with processing instructions

xmldiff_error.zip
When diffing the two files contained in the attached zip file, I get the following exception:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\lafarley\AppData\Local\Programs\Python\Python36\lib\site-packages\xmldiff\main.py", line 51, in diff_files
diff_options=diff_options, formatter=formatter)
File "C:\Users\lafarley\AppData\Local\Programs\Python\Python36\lib\site-packages\xmldiff\main.py", line 39, in _diff
formatter=formatter)
File "C:\Users\lafarley\AppData\Local\Programs\Python\Python36\lib\site-packages\xmldiff\main.py", line 28, in diff_trees
return list(diffs)
File "C:\Users\lafarley\AppData\Local\Programs\Python\Python36\lib\site-packages\xmldiff\diff.py", line 439, in diff
for action in self.update_node_tag(lnode, rnode):
File "C:\Users\lafarley\AppData\Local\Programs\Python\Python36\lib\site-packages\xmldiff\diff.py", line 233, in update_node_tag
left.tag = right.tag
File "src\lxml\etree.pyx", line 992, in lxml.etree._Element.tag.set
File "src\lxml\apihelpers.pxi", line 1657, in lxml.etree._getNsTag
File "src\lxml\apihelpers.pxi", line 1675, in lxml.etree.__getNsTag
File "src\lxml\apihelpers.pxi", line 1538, in lxml.etree._utf8
TypeError: Argument must be bytes or unicode, got 'cython_function_or_method'

We currently do not support XML Processing instructions. We should.

Investigating a bit, diffing does work, but the xml formatter fails. To fix this we likely do have to handle processing instructions differently in the diffing itself, specifically we should never rename a normal node to a processing instruction.


[Bug]: Public keys passed to add machine key are not stored in the database

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Environment
Self-hosted
Version
2.51.0
Database
PostgreSQL
Database Version
16
Describe the problem caused by this bug
When attempting to log in after adding a machine key as implemented in #7671, the call fails with the error message:
msg="request error" oidc_error.parent="invalid signature (error fetching keys: Not Found: ErrorType=invalid_request Description=Errors.AuthNKey.NotFound Parent=ID=QUERY-SDf32 Message=Errors.AuthNKey.NotFound Parent=(sql: no rows in result set))" oidc_error.description="assertion invalid" oidc_error.type=invalid_request status_code=400

To reproduce

Add a machine key with a locally generated private key

openssl genrsa -out key.pem 2048
openssl rsa -in key.pem -pubout > key.pub

Attempt to log in the service user using key.pem

Screenshots
No response
Expected behavior
The log in works.
Operating System
No response
Relevant Configuration
No response
Additional Context
The issue definitely stems from #7671, however I'm not sure where something is missing.
The key is added successfully and is visible in the frontend so I'm assuming that the public key isn't copied into the database. I don't know where the necessary changes would have to be made to make sure the key is synced into the database.

@livio-a do you maybe have a hunch of what might be causing this issue?

@aDogCalledSpot  do you pass the key id as kid in the header?
https://zitadel.com/docs/apis/openidoauth/authn-methods#jwt-with-private-key

Sounds more like a storage projection issue to me.
Can you check the status of the user projection please?
select projection_name, last_updated, aggregate_id, aggregate_type, sequence, event_date, position
	from projections.current_states
where projection_name = 'projections.users12'
and instance_id = '257786991247097860';

Change the instance_id to your instance ID. Also check if 'projections.users12' is in fact the highest available projection version. I'm not sure which zitadel version you are on right now.
Next, also check the latest events in the eventstore:
select event_type, created_at, sequence, position from eventstore.events2
where instance_id = '257786991247097860'
and aggregate_type = 'user'
order by position desc
limit 20;

The position of the first query should be somewhere close to the head of positions in the eventstore.

Sorry for the late reply:

Can you check the status of the projection please?:

   projection_name   |         last_updated          |    aggregate_id    | aggregate_type | sequence |          event_date           |     position
---------------------+-------------------------------+--------------------+----------------+----------+-------------------------------+-------------------
 projections.users12 | 2024-07-15 07:15:31.640598+00 |<PHONE_NUMBER>88449795 | user           |        3 | 2024-06-13 13:31:30.049053+00 |<PHONE_NUMBER>.049066

Next, also check the latest events in the eventstore

             event_type              |          created_at           | sequence |     position
-------------------------------------+-------------------------------+----------+-------------------
user.token.v2.added                 | 2024-07-12 07:32:15.843299+00 |       31 |<PHONE_NUMBER>.843440
user.human.password.check.succeeded | 2024-07-12 07:32:14.957706+00 |       30 |<PHONE_NUMBER>.957717
user.token.v2.added                 | 2024-07-12 07:31:42.961752+00 |       29 |<PHONE_NUMBER>.962257
user.token.v2.added                 | 2024-07-11 12:14:33.566238+00 |       28 |<PHONE_NUMBER>.566726
user.token.v2.added                 | 2024-07-11 09:12:30.568912+00 |       27 |<PHONE_NUMBER>.569228
user.human.mfa.init.skipped         | 2024-07-11 09:12:29.328998+00 |       26 |<PHONE_NUMBER>.329009
user.human.password.check.succeeded | 2024-07-11 09:12:27.600179+00 |       25 |<PHONE_NUMBER>.600191
user.machine.key.added              | 2024-06-13 13:31:30.160193+00 |        4 |<PHONE_NUMBER>.160207
user.deactivated                    | 2024-06-13 13:31:30.049053+00 |        3 |<PHONE_NUMBER>.049066
user.metadata.set                   | 2024-06-13 13:31:29.754356+00 |        2 |<PHONE_NUMBER>.754369
user.machine.added                  | 2024-06-13 13:31:29.655965+00 |        1 |<PHONE_NUMBER>.655978
user.token.v2.added                 | 2024-06-13 13:31:29.402314+00 |       21 |<PHONE_NUMBER>.402582
user.token.v2.added                 | 2024-06-13 08:54:57.121918+00 |       24 |<PHONE_NUMBER>.122248
user.machine.key.added              | 2024-06-13 08:46:48.51864+00  |        4 |<PHONE_NUMBER>.518651
user.deactivated                    | 2024-06-13 08:46:48.413432+00 |        3 |<PHONE_NUMBER>.413446
user.metadata.set                   | 2024-06-13 08:46:48.133849+00 |        2 |<PHONE_NUMBER>.133859
user.machine.added                  | 2024-06-13 08:46:48.037342+00 |        1 |<PHONE_NUMBER>.037353
user.token.v2.added                 | 2024-06-13 08:46:47.74643+00  |       20 |<PHONE_NUMBER>.746573
user.token.v2.added                 | 2024-06-13 08:22:29.191475+00 |       23 |<PHONE_NUMBER>.191962
user.machine.key.added              | 2024-06-12 14:52:28.201598+00 |        4 |<PHONE_NUMBER>.201609

The position of the first query should be somewhere close to the head of positions in the eventstore.

I assume you mean this line?
user.machine.key.added              | 2024-06-13 13:31:30.160193+00 |        4 |<PHONE_NUMBER>.160207

@muhlemmer Do you have any further suggestions here?

I can reproduce your issue with the following steps:

openssl genrsa -out key.pem 2048
2 openssl rsa -in key.pem -pubout > key.pub
Set the key.pub to the machine user.
Use zitadel-tools to create the JWT: export ASSERTION=$(zitadel-tools key2jwt --audience "${ISSUER}" --key="key.pem" --issuer=280270638621392898)
Use JWT profile

curl --request POST \
  --url ${ISSUER}/oauth/v2/token \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data 'grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer' \
  --data "scope=${SCOPE}" \
  --data "assertion=${ASSERTION}" | jq

Response:
{
  "error": "server_error",
  "error_description": "Errors.Internal"
}

Logs:
time=2024-08-30T09:18:20.268Z level=ERROR msg="request error" oidc_error.parent="ID=OIDC-AhX2u Message=Errors.Internal Parent=(invalid signature (error fetching keys: ID=QUERY-SDf32 Message=Errors.AuthNKey.NotFound Parent=(sql: no rows in result set)))" oidc_error.description=Errors.Internal oidc_error.type=server_error status_code=500

The created JWT:
echo $ASSERTION
eyJhbGciOiJSUzI1NiJ9.eyJpc3MiOiIyODAyNzA2Mzg2MjEzOTI4OTgiLCJzdWIiOiIyODAyNzA2Mzg2MjEzOTI4OTgiLCJhdWQiOlsiaHR0cDovL2xvY2FsaG9zdDo5MDAwIl0sImlhdCI6MTcyNTAwOTUwMCwiZXhwIjoxNzI1MDEzMTAwfQ.VnW3QP3iuzq-PEguSgPSwHS08ggO2UYoGOjQ6l1w8ClBA6NJ9Po_xtyAVhX7c_50DfKSCe2qD0fmnBe6UUf5IchsG4uNXKQ2cCXSoZxgUOhnhtAa688ohPaJjCZ1nJ-0J6kpkzgbft0eLWS7ybMm2X4uJTBw51tDClP_Zxsn1DL-UPZR1EPBdk652vKBqFJUzdZFj1Qk9CaIJFIuEzG3Q83b3tNlZH3jVDNmB-P6Ac6CdMMGaWc8WIeKIsnlFeMDlBdwBhdL8Nd3Vbbt4ZXOtDCZbRtyPshsFOsbRGD2qKFfd8xWNsxO_1hbcDszXjKYBKoUAMS6FJcyLtuFxVXpRA

Decoded:
{
  "alg": "RS256"
}

It seems the key ID is missing.

Yes, I'm sure. I've inspected the request and the JWT looks correct.

@aDogCalledSpot I must ask, how do you generate the JWT? If its zitadel-tools, the problem is clear. As a key.pem does no contain the key ID, and zitadel-tools doesn't provide an option to provide one, the resulting JWT is missing that claim. So zitadel can't find the key.
Can you please share the decoded payload of the JWT you are sure that is working?

i also get same error here, but with key.json

gen jwt

zitadel-tools key2jwt --audience=https://foobar.com --key=key.json

get token

curl  --request POST \
  --url https://foobar.com/oauth/v2/token \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data grant_type='urn:ietf:params:oauth:grant-type:jwt-bearer' \
  --data scope='openid profile email urn:zitadel:iam:org:project:id:zitadel:aud' \
  --data assertion="<token>"

will got:
{"error":"server_error","error_description":"ID=QUERY-Dfbg2 Message=Errors.User.NotFound Parent=(sql: no rows in result set)"}

but in my case the decoded jwt header contains kid
{
  "alg": "RS256",
  "kid": "12321312313123123123123" // just example
}

and my payload is something like this:
{
  "iss": "123123123123123123@foo",  // just example
  "sub": "12312312312312313@foo", // just example
  "aud": [
    "https://foobar.com"
  ],
  "iat":<PHONE_NUMBER>,
  "exp":<PHONE_NUMBER>
}

With a IAM_OWNER user, can you please look if there's anything related in the  Console, under "Default Settings" > "Failed Events".


Add pdf page column to output CSV

Would be nice to know what page to navigate to to find the matching regex.

Hey- I can definitely add that feature. I'm going to add it to my queue for our weekly project planning meeting and get started on that after I finish this OCR relate project.

@golfecholima It now works as such.


Proposal: support alternate compiler/codegen/servicebuilder setups

The project's actually well-suited for this, all I had to do was make them and put them in the same package space where the normal ones would go. This would allow developers to take advantage of the wonderful parsing support you all have already written, while being able to generate their own models/services that fit their needs.

I'm open to this.  How would these setups look, API-wise?
As you've noted, the project is split out into fine-grained modules already, and parsing support can be had by just depending on thrifty-schema (which includes parsing and linking, but no codegen).  What would you want to build on top of this?

Honestly, might be simple enough just to make methods public. Let me put together a list.

Here's what I'm thinking:

ConstantBuilder
TypeResolver
TypeNames
SimpleVisitor

Not exhaustive, but that's all I personally ended up needing. Maybe try with just that and see if other needs/cases come up?

SimpleVisitor and TypeNames, as trivial as they are, I guess are very easy to make public.
I'm reluctant to make the other two public.  They are implementation details, especially ConstantBuilder - it's hard for me to see how they could be useful as part of a public API, and I wouldn't want to commit to maintaining their interfaces going forward.  It's not an absolute no, but I'd want a large benefit from it that I just don't see right now.
At a higher level, what would you like to do?  What would these types being public enable?  You hinted at the wish for a more pluggable compilation process; what are you trying to do?

it's not very organized as I was putting it up for a coworker to look at, but basically this: https://github.com/hzsweers/thrifty/commit/5b3fd111670b8484daace84c46360396e8a324fb
Ideally, what I want is to be able to parse and load all the thrift information that schema and compiler handle, and be able to generate whatever code I want from it. In this case, I have a working implementation of generating autovalue-friendly code instead, and separately have also implemented support for the services generation and wrapped it all up in a gradle plugin.
It looks like the only things needed from ConstantBuilder are usages in the code generator's buildConst method. The TypeResolver is used in a lot of places though for its getJavaClass method. I'm not really sure what the best solution would be API-wise.

It looks like this was resolved when Warren added builders - correct?

Yep!


Add dependency updates and deployment

Should leverage current Github CI-actions

@jermnelson so do we want to have something run every Monday (similar to our Jenkins access-update-scripts) to see if any Python dependencies need to be updated? If there are changes it will submit a PR that will get merged by a person?
How should the deployments work? Are we aiming for a continuous integration like process which deploys to which environments? Do we have a model for doing this in any DLSS projects that I can crib from or are we starting fresh here?

Hi @edsu, I was thinking something similar to the access-update-scripts that would generate a weekly PR. For now it is fine if the PR requires manual merging by a person.
For deployments, something similar to SDR Deploy would be great but maybe just deploy to airflow-test and airflow-stage environments. Not sure if it would possible to do through Github Actions are not.


Adds tap-zammad extractor

Hello,
I aim to add my tap to the Meltano Hub. This tap allows to extract data from Zammad
Checklist

[x] Add/update the file in the appropriate folder (/taps or /targets). The name of the file should match the name of the tap. If there is already one, add a descriptor to the name such as -search.
[x] Add/update the PNG logo image in /assets/logos/<taps or targets>. The image name must match the YAML file name.
[x] Tag @tayloramurphy or @pnadolny13 to flag it for review. Or post to the #hub channel on Meltano slack.

Reviewer Checklist

[x] Validate file against JSON Schema. https://www.jsonschema.net/home is an option.
[x] Build website locally and validate everything works.

@tayloramurphy @pnadolny13 I have a validation error on the maintainers.yml file but I don't understand what's the problem 🤔

@Lawiss this is great, thanks! I just added 2 minor suggestions then I think we're good to merge it.


Bug fix resource collection rel hrefs

Fixes #12

Please merge with master so tests can pass

Master has been rebased but travis doesn't seem to be picking up the GROOVEHQ_ACCESS_TOKEN.

Looks like Travis does not support encryption keys for pull requests from forks

Well that kinda sucks :( Seems like I will have to run them myself before releasing new versions and disable them on travis.

@rossta please rebase again https://github.com/Fodoj/groovehq/pull/14 and then I can merge and release new version with your PRs included, thanks!

Rebased.
One idea could be to trigger the integration specs only on master using an env var like TRAVIS_BRANCH.


Workspaces

planning.md entry

#817
Replace current Workspace in huak-package-manager
Add new Workspace to huak-toolchain

Related:  #717

Started, functional, needs work. I'll flesh it out while stabilizing huak-toolchain and huak-package-manager.


fit: revert mongoose typekey

Motivation
This PR reverts a previous change that explicitly set the mongose typeKey to be $type, that was introduced in order to support properties name type.
Unfortunately, the change breaks the support for keywords on sub-schemas.
Other changes
Better @mgoose.prop() and @entity.prop() code suggestion

Hello @pierissimo.
We are wondering what is the exact reason for this revert. What was being broken?
In the organization we have many subschemas with properties named 'type'.
Is there an idea of how this problem should be addressed? Otherwise Davinci cannot currently support our schemas as they are.
Thank you
CC @joseandrespg @Sergio-Barquero

hey @adriasala124
It's been a while, and I'm jogging my memory to piece things together.
I wonder if the issue is related to the fact that the sub-schemas, to support $typeKey, must always be instantiated with new Schema.
And that probably breaks the ability to decorate fields using @mgoose.virtual in embedded objects.
Hopefully it should be easily reproducible with some unit tests


Address memory access issues

The occasional test segfaults and inconsistency hopefully can be addressed by taking care of some memory access bugs identified by valgrind. These can be obtained by:

Install valgrind
Build ITKTextureFeatures with CMAKE_BUILD_TYPE set to RelWithDebInfo
Run ctest -D ExperimentalMemCheck -R RunLengthTextureFeaturesImageFilterInstantiationTest -VV, etc. Or exclude -R to run all the tests.
Address the issues identified in Testing/Temporary/MemoryChecker.*.log

Addressed by #27 and #29


Improve overload and generic signature inference: Inference alternatives and linked inferences

With this PR, we explore multiple options within inference when comparing an overload list to a single target signature, and pick a single match out of the list of possible inferences this produces, rather than creating a combined inference that may not actually work with the source signature list. In addition, we no longer erase generics when performing inference, instead preserving them and mapping them into free type variable locations, which we also perform inference on, allowing us to link up inferences across multiple positions within a (potentially overloaded!) signature, and, eg, keep an inferred type consistent between an argument and return position.
These two changes largely serve to improve promise-like monadic inferences (as the changed baselines show), and serve as, IMO, a basis for being able to properly type the JSX constructor function without all of the internal machinery we currently have that only applies to JSX tags (without introducing any new syntax).
The simplest ask this PR fixes, which you can find in our test suite's updated baselines in this PR (which date back to the initial snapshot of the compiler), is requesting that this:
declare function doThing(x: number): number;
declare function doThing(x: string): string;

const a = Promise.resolve(0).then(doThing);

typecheck, rather than error.
Fixes #35501
Fixes #30294 (partially)

@typescript-bot test this
@typescript-bot test top100
@typescript-bot user test this
@typescript-bot user test tsserver
@typescript-bot test tsserver top100
@typescript-bot run dt
@typescript-bot perf test this
@typescript-bot pack this

RWC largely looks good, lots of improvements in fp-ts and azure, just a jquery promise + promise compat error to look in to (and if I'm lucky it'll get fixed by how I fix the single self-check new error). User suites are clean, top100 is... I dunno, it's just reporting completion entry details crashes which look suspiciously unrelated to this. I'm sure DT will come back with interesting results once it's done (should we, maybe, shard DT runs onto more workers, assuming we have more workers available? Even with 4 workers it's stretching up towards the 2hr range).

I'll probably have to see if I can do anything about the pretty major perf regression in material-ui, but generally speaking this isn't nearly as bad as I thought it could have been. Some strict limits to how many alternatives we'll try'll probably help bring that back down to reasonable.

Feel free to ignore and not rerun tsserver; I didn't mean to include it here. It's complaining because these errors are finnicky and I've mostly gotten it to be quiet, but apparently not all.

I'm sure DT will come back with interesting results once it's done (should we, maybe, shard DT runs onto more workers, assuming we have more workers available?

Note that it doesn't actually reply (unlike every other task...), so you'll have to manually go and check the results via logs, if any.

top100 is... I dunno, it's just reporting completion entry details crashes which look suspiciously unrelated to this.

Ah, misread this; there are two top100 tests, the one you actually need to look at is still pending but will reply any minute now: https://typescript.visualstudio.com/TypeScript/_build/results?buildId=147381&view=results

I might be misunderstanding some of the constraints here but initially thought that it would also resolve this issue (but it doesn't): https://github.com/microsoft/TypeScript/issues/38930

@typescript-bot pack this

The example given in the description looks a lot like a (simplified) example I ran into recently, but this change doesn't seem to allow my example to compile:
interface Wrapper<T> {
    wrapped: T;
}

function unwrap<T>(value: Wrapper<T>): T;
function unwrap<T>(value: Wrapper<T> | undefined): T | undefined;
function unwrap<T>(value: Wrapper<T> | undefined): T | undefined {
    return value?.wrapped;
}

const foo: string = await Promise.resolve<Wrapper<string>>({ wrapped: 'foo' }).then(unwrap);

Playground link for this PR build.
Which still complains that Type 'unknown' is not assignable to type 'string'. for foo. Is this case not covered or am I doing something wrong?

@typescript-bot run DT


Fixing pylints.

Pull Request Description
What issue does this change request address?
Closes #1600
What are the significant changes in functionality due to this change request?
Fixes some pylint warnings.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Board is green. The recipe on the Fedora machine needs to be fixed. It is on the TODO list and it will be performed soon


If a port is specified use that instead of finding a random one

In #220 it was found that if a user specified a port, but not the hostname, then the port setting would not be honored.
This issue should changed the behaviour to autodetect a port IF none is specified.
i.e.
https://github.com/jpogran/puppet-vscode/blob/8fdfb7894d08de673bac319991a2499050df97f6/client/src/connection.ts#L215-L219
Should be guarded on whether a port was specified.

Merged


[FEATURE]  Sesssion connections are unbalanced in the instance of the engine pool

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the feature
engine.pool.size = 4
kyuubi.engine.pool.selectPolicy=POLLING
jdbc pool size = 40
Session connections are unbalanced across instances:
engine01:

engine02:

engine03:

engine04:

Motivation
Unbalanced connections will cause unbalanced engine load.
Some engines perform a lot of calculations, while the rest are idle.
Describe the solution
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

this is a same question KYUUBI #3695, but the commiter has diffrent idea about save connection info by metric instead of zk. i am wating for the pr that save  connections by metrics.

May I submit a PR for this issue?


[Runtime] Mark swift_asprintf with attribute((format))

This gives us build-time warnings about format string mistakes, like we would get if we called the built-in asprintf directly.
Wrap TypeLookupError format string creation in a macro that uses this to provide build-time warnings for its users as well.
This reveals various mistakes in format strings and arguments in the runtime, which are now fixed.
rdar://73417805

@compnerd Thanks, fixed those.

@compnerd Thanks, fixed those.

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please smoke test os x platform

@swift-ci please smoke test os x platform


refactor: Remove deprecated normalizeWhitespace option

BREAKING
This option was never useful, as it could just break someone's markup. Instead, use a tool that specialises in minifying HTML such as html-minifier-terser.

Coverage decreased (-0.4%) to 85.185% when pulling 581dfec48e6cd7a20cc600b52876905a4707997c on refactor/rm-normalize-ws into 3b01ac7e701a33ca4e74f12ca8e4c4227d24d6cf on master.


vcs: line endings after clone

Since b2fcbae8fb1fe857c36fdb6545532dbc7d78b79d git isn't happy with the line endings after a fresh clone.
> git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   help/es/es.po
	modified:   tests/data/amz/decrypted.amz
	modified:   tests/data/xspf/xspf-1_0.2.xsd

no changes added to commit (use "git add" and/or "git commit -a")

core.autocrlf is set to input.

couple of the line ending settings in that commit may be wrong but I just tested with core.autocrlf set to input globally and it didn't occur on my system when I cloned. What's the output from git config -l?

Here you go:
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true

Odd, I retried with core.filemode set to true as I had that false but I still couldn't reproduce. What does git diff say about the difference, is it definitely line endings?

Well, just solved it by upgrading git from 2.7.4 to 2.14.2.

Cool, mind if we close this one?


Bash improvements

Some scripts used pipefail without -o, which doesn't make sense, so that's pretty much a bugfix
Many scripts had -eux -o that were merged to -euxo
I don't really like mixing set with shebang-located bash flags; for cohesion, I moved all shebang-placed flags into set commands

I also addressed one shellcheck issue in 68e3234.
Aside from these changes, I'd recommend:

using -E for scripts that use subshells (there's a lot of them)
using command/builtin where it makes sense
copying env vars to scripts using !#/usr/bin/env bash instead of !#/bin/bash where that's not breaking
not using .sh extension for Bash/other shell scripts, it's misleading

let me know if you wish some of these implemented :)

E2E tests don't run -- looks like the shebang was correct, but the flags were unnecessary.

Since we're getting some shellcheck errors here that I intentionally omitted, I'll just correct that now and see if workflows are passing.


v4.3.0 fails build with XCode 9.4.1 (swift 4.1)

What did you do?
updating to version 4.3 fails a build on XCode 9.4.1
Environment

SwiftyJSON: *4.3.0 *
Xcode Version: 9.4.1 (9F2000) (Open Xcode; In menubar: Xcode > About Xcode)
Swift Version: 4.1 (Default) (Open Xcode Preferences; Components > Toolchains. If none, use Xcode Default.)

Please also mention which package manager you used and its version. Delete the
other package managers in this list:

Carthage: 0.33.0 (Use carthage version in Terminal)

Xcode 9.4.1 doesn't support Swift 5.

So if you are committing a backward incompatible change then it should be a different major version, like 5.0

@leonid-s-usov This is not a backward incompatible change. We don't add/remove any APIs in this version.

It is backward incompatible in terms that in my Cartfile I used to have
SwiftyJSON ~> 4.0

and after carthage update, the project fails to build.
I have an example of another project which somehow manages to maintain Carthage support of different XCodes


Add full info api endpoint

This issue is imported from pivotal
https://wiki.surfnet.nl/display/surfconextdev/eduID+API

https://github.com/OpenConext/OpenConext-myconext/commit/ef5ca12ae04648845ae4f8be3b05b2e430909e10 (Okke Harsta - Sep 17, 2021)

The api-call only returns linked accounts:
[
  {
    "schac_home_organization": "readid.com",
    "validated_name": "Peter Havekes",
    "eppn"<EMAIL_ADDRESS>  },
  {
    "schac_home_organization": "example.com",
    "validated_name": "John Doe",
    "eppn"<EMAIL_ADDRESS>  },
  {
    "schac_home_organization": "demo.org",
    "validated_name": "John Doe",
    "eppn"<EMAIL_ADDRESS>  }
]

I would also expect all attributes, including the self asserted name and email-address in response for this call. Or should we rename this endpoint to /linked-accounts/? (Peter Havekes - Sep 21, 2021)

This suites the purpose eduBadges has. We can add stuff or rename. The last is the simplest. (Okke Harsta - Sep 21, 2021)

Lets rename both the endpoint and the scope to:
endpoint: /myconext/api/eduid/links
scope: eduid.nl/links (Peter Havekes - Sep 21, 2021)

https://github.com/OpenConext/OpenConext-myconext/commit/777570da6ca04093710b8db47c5f1f024084bc3c (Okke Harsta - Sep 21, 2021)


Using Karma to test Gulp Tasks

Hello,
My company uses Gulp on the front-end for our build process. We also have code quality gates we must pass before a build can be completed, such as passing unit tests. We currently test using the Karma, Mocha, Sinon, Chai, Istanbul, and Webpack stack. Because our Gulp tasks are so critical I want to extent testing to them as well, writing unit tests for them.
I am running into a lot of problems and my research points to Karma/Webpack considering these modules for the Gulp tasks to be node, not browser, environment. Can anyone point me to a configuration for Karma that enables my testing for Gulp tasks?  (I totally understand this might not be the right project to post this in but I wanted to start here at our test runner first.)
Thanks in advance!

gulp runs on nodejs, so unit tests for gulp would be unit test on nodejs: use mocha.  Karma-runner can' help you.


HOTFIX nav links and order of nav items on office page

This fixes the links in the navigation for offices and subpages on beta, and fixes the ordering of subpages in the nav on the office page.
Currently we don't know why, but the permalink feature of sheer is unstable on beta, though seems to act normally in staging. This removes that complexity and "hard-codes" the slug into the appropriate url pattern. We know the slug is available on beta, so we deem this appropriate to fix that issue. Additionally, the subpages in the navigation should be ordered based on the order given in the CMS. This is not happening when visiting an office page.
@jimmynotjim @sebworks @anselmbradford @KimberlyMunoz

LGTM

:+1:


⚠ Bofrost.fr has degraded performance

In 0cb729f, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 5814 ms

Resolved: Bofrost.fr performance has improved in e4d6bf3.


mog command

MOG RADMOS_

I assume this would just be an alias for the compare command?

I assume this would just be an alias for the compare command?

you would be correct, one line of code

you should open a PR for it :)

it's fine, go to src/message-commands/compare.ts and add a new string to array: aliases and you're good to go

soon....https://github.com/YoruNoKen/HanamiBot/assets/127623330/e47438ba-8893-4dc1-beae-b76ab988f170


Update KeyboardEvent.code to be a a string

KeyboardEvent.code is defined as a DomString whose

unitialized value must be "" (empty string)

so this changes KeyboardEvent.code from number to string.
see also mdn's KeyboardEvent.code page

Hi there, i'm also not sure if this change is exhaustive (it was the only place i found the attribute, but if i've missed something i'm happy to touch up the pr)

I don't know the history here but I agree with your interpretation. The spec definitely says it's a string, and it looks like it has always been that way. keyCode is the one that is/was a number (and is deprecated).

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


Probabilities for choices

I have seen multiple issues on this and one forked repo but can someone please clearly point me to where the code I need is to run the outlines structured inference (choices) with probabilities on the outputs.
Thanks so mcuh

Could you give us the address to the forked repo?

https://github.com/craft-ai/fork-outlines/tree/probabilities


V0.2 feature cli windows

Description
Add Windows supports for CLI - orchestration management tools.
Linked issue(s)/Pull request(s)

151

Type of Change

[ ] Non-breaking bug fix
[ ] Breaking bug fix
[X] New feature
[ ] Test
[ ] Doc update
[ ] Docker update

Related Component

[ ] Simulation toolkit
[ ] RL toolkit
[ ] Distributed toolkit

Has Been Tested

OS:

[X] Windows
[ ] Mac OS
[ ] Linux

Python version:

[X] 3.6
[ ] 3.7

Key information snapshot(s):

Needs Follow Up Actions

[ ] New release package
[ ] New docker image

Checklist

[ ] Add/update the related comments
[ ] Add/update the related tests
[ ] Add/update the related documentations
[ ] Update the dependent downstream modules usage

Codecov Report

Merging #203 (4bfee1b) into v0.2 (298c155) will decrease coverage by 1.75%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             v0.2     #203      +/-   ##
==========================================
- Coverage   71.23%   69.47%   -1.76%
==========================================
  Files          89       91       +2
  Lines        4203     4436     +233
==========================================
+ Hits         2994     3082      +88
- Misses       1209     1354     +145

Flag
Coverage Δ

unittests
69.47% <50.00%> (-1.76%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

maro/utils/logger.py
64.88% <50.00%> (+20.35%)
:arrow_up:

maro/communication/driver/zmq_driver.py
21.73% <0.00%> (-3.58%)
:arrow_down:

maro/communication/proxy.py
23.10% <0.00%> (-3.10%)
:arrow_down:

maro/communication/driver/abs_driver.py
60.00% <0.00%> (-1.54%)
:arrow_down:

maro/communication/message.py
86.84% <0.00%> (-1.40%)
:arrow_down:

maro/utils/exception/communication_exception.py
68.29% <0.00%> (-0.46%)
:arrow_down:

maro/communication/registry_table.py
94.26% <0.00%> (ø)

maro/communication/utils/default_parameters.py
100.00% <0.00%> (ø)

maro/utils/exit_code.py
100.00% <0.00%> (ø)

maro/utils/checkpoint.py
32.18% <0.00%> (ø)

... and 1 more

Continue to review full report at Codecov.

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


PIP install bat-country Breaks tensorflow in virtualenv

issue
Bat-country dependancies are out of date - thus when I ran
pip install bat-country
I got errors when you try to run tensorflow in same env because you have just downgraded all the packages... incl protobuf.
work around
pip uninstall bat-country
pip install --upgrade (all packages that just got downgraded)
or
pip install tensorflow (*should* upgrade everything that needs upgrading)

I uninstalled bat-country then re-upgraded the relevant tensorflow packages everything worked again.
then
git clone https://github.com/jrosebr1/bat-country.git
python setup.py install

and it should work...

Thanks for mentioning this. Another solution would be to create a separate Python virtual environment strictly for bat-country, that way you don't have to worry about upgrading/downgrading any packages you already have installed.

@janislejins Were you able to resolve the issue by creating a separate virtual environment and then installing the dependencies there? If so, let me know and I'll close the issue. Otherwise, I'll come up with a solution.

yeah all good. Close the issue.
On Tue, May 3, 2016 at 9:09 PM, Adrian Rosebrock<EMAIL_ADDRESS>wrote:

@janislejins https://github.com/janislejins Were you able to resolve
the issue by creating a separate virtual environment and then installing
the dependencies there? If so, let me know and I'll close the issue.
Otherwise, I'll come up with a solution.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jrosebr1/bat-country/issues/5#issuecomment-216497444

--
http://www.janislejins.com/
Janis Lejins
<EMAIL_ADDRESS>/ +61408283062
www.janislejins.com
[image: Twitter]  https://twitter.com/jlejins [image: Facebook]
https://www.facebook.com/janislejins [image: LinkedIn]
https://www.linkedin.com/in/lejins [image: Instagram]
http://instagram.com/janislejins [image: Github]
http://github.com/janislejins


Analyze Code Coverage should warn if coverage.py is not installed

Currently it warns after running the test, but we should warn in advance and help the user install the right package.

We're closing old issues with no recent activity. If this is still important, please open a new issue.


docs: fix typo in finch adapter docs

Fixes typo in finch adapter docs
checekd --> checked

Thanks!


fix: log can be an empty array

This fixes a problem when the log is empty:
[test/browserstack    ] Missing error handler on `socket`.
[test/browserstack    ] TypeError: Cannot read property 'split' of undefined
[test/browserstack    ]     at printFailures (/opt/atlassian/pipelines/agent/build/node_modules/karma-mocha-reporter/index.js:358:42)
[test/browserstack    ]     at printFailures (/opt/atlassian/pipelines/agent/build/node_modules/karma-mocha-reporter/index.js:417:17)
[test/browserstack    ]     at printFailures (/opt/atlassian/pipelines/agent/build/node_modules/karma-mocha-reporter/index.js:417:17)
[test/browserstack    ]     at self.onRunComplete (/opt/atlassian/pipelines/agent/build/node_modules/karma-mocha-reporter/index.js:621:21)
[test/browserstack    ]     at .<anonymous> (/opt/atlassian/pipelines/agent/build/node_modules/karma/lib/events.js:13:22)
[test/browserstack    ]     at emitTwo (events.js:111:20)
[test/browserstack    ]     at emit (events.js:191:7)
[test/browserstack    ]     at emitRunCompleteIfAllBrowsersDone (/opt/atlassian/pipelines/agent/build/node_modules/karma/lib/server.js:294:12)
[test/browserstack    ]     at .<anonymous> (/opt/atlassian/pipelines/agent/build/node_modules/karma/lib/server.js:325:7)
[test/browserstack    ]     at emitOne (events.js:96:13)
[test/browserstack    ]     at emit (events.js:188:7)
[test/browserstack    ]     at .<anonymous> (/opt/atlassian/pipelines/agent/build/node_modules/karma/lib/server.js:308:12)
[test/browserstack    ]     at emitTwo (events.js:111:20)
[test/browserstack    ]     at emit (events.js:191:7)
[test/browserstack    ]     at onComplete (/opt/atlassian/pipelines/agent/build/node_modules/karma/lib/browser.js:143:13)
[test/browserstack    ]     at Socket.<anonymous> (/opt/atlassian/pipelines/agent/build/node_modules/karma/lib/events.js:13:22)

Is there any way this can be integrated? I keep on seeing this popping up in tests.

Sorry for the delay. We will have a look.


Marker hitbox

Issue description
When adding an image as an icon, the bounding box is clickable instead of only the non-transparent parts of the image.
Steps to reproduce and a minimal demo of the problem

http://plnkr.co/edit/61X0XW0eLkPNuhjGddx2

Current behavior

Try clicking on the bottom left of the marker with the people (just outside).
This will open the wrong info window.

Expected/desired behavior

We want to open the info window corresponding with the clicked marker.
This can be done by adding the shape attribute to markers.

angular2 & angular-google-maps version
v1.0.0-beta.1

Is this happening only when using Google maps though this module, or is this a general problem with Google maps?


Ore veins from other mods?

I am using this mod for ore gen and was wondering if it would be possible somehow to make the drills work only on nods from this mod and output the right ore/ores depending on the chunk. Thank you for your help and sorry for issue spam, I couldn't find a discord server and that's probably intentional

The mod uses it's own chunk based ore vein system. If the Geocluster veins have their own biome then you can create a vein that only spawns in that biome.


refactor: replace requireModule with ESM imports in getPostcssConfig

📚 Description
This pull request includes the following changes:

Removed use of requireModule in favor of dynamic ESM imports
Updated sortPlugins function and plugin instantiation to be asynchronous
Ensured compatibility with existing plugin loading mechanism

This change modernizes the codebase by utilizing ES module imports and improves compatibility with ESM environments. The asynchronous handling of plugin instantiation aligns with the dynamic import approach, ensuring a smooth and efficient loading process for PostCSS plugins.
Solves this TODO Message in the Repo

We also likely want to mirror any improvements here too:
https://github.com/nuxt/nuxt/blob/2de885bab5b86d5e20103cf8c8172019cec92617/packages/vite/src/css.ts#L23-L28

(I'll take a stab at implementing those suggestions.)