Self Hosted quick install with Zitadel - Error 502 - openresty

I run the install.
No issues on screen. tells met to go to my domain with this username and password.
I get error 502. Bad Gateway.
Doing a docker PS I see my management server is restarting.
logs for management container as follows. (i replaced my domain name. with example.com
2024-05-10T13:55:18Z INFO management/cmd/management.go:455: loading OIDC configuration from the provided IDP configuration endpoint https://example.com/.well-known/openid-configuration
Error: failed reading provided config file: /etc/netbird/management.json: OIDC configuration request returned status 502 with response:
502 Bad Gateway

502 Bad Gateway
openresty

This duplicates over and over on every restart of management container.
Tried restarting the server,
Ubuntu 24.04 and tried Ubuntu 22.4.
Updated all updates.
Fixed ip on Ubuntu server running on proxmox.
I use Nginx as on a diffrent container wich portforwards https > <IP_ADDRESS> , port 443 , with a Lets encrypt  SSL through Cloudflare.
Please specify whether you use NetBird Cloud or self-host NetBird's control plane.
NetBird version
Self-hosted : latest

Hello @HybridRCG can you please share the logs from the management service? you can get them with the following command:
docker compose logs management

Hi Thanks for the help!
This is some of the log file entries there. They are all identical a few seconds apart.
management-1  | Error: failed reading provided config file: /etc/netbird/management.json: OIDC configuration request returned status 502 with response:
management-1  | 502 Bad Gateway
management-1  |
management-1  | 502 Bad Gateway
management-1  | openresty
management-1  |
management-1  |
management-1  |
management-1  | 2024-05-11T09:54:53Z INFO management/cmd/management.go:455: loading OIDC configuration from the provided IDP configuration endpoint https://nb.groblers.co.uk/.well-known/openid-configuration
management-1  | Error: failed reading provided config file: /etc/netbird/management.json: OIDC configuration request returned status 502 with response:
management-1  | 502 Bad Gateway
management-1  |
management-1  | 502 Bad Gateway
management-1  | openresty
management-1  |
management-1  |
management-1  |
management-1  | 2024-05-11T09:55:07Z INFO management/cmd/management.go:455: loading OIDC configuration from the provided IDP configuration endpoint https://nb.groblers.co.uk/.well-known/openid-configuration
management-1  | Error: failed reading provided config file: /etc/netbird/management.json: OIDC configuration request returned status 502 with response:
management-1  | 502 Bad Gateway
management-1  |
management-1  | 502 Bad Gateway
management-1  | openresty
management-1  |
management-1  |
management-1  |
management-1  | 2024-05-11T09:55:33Z INFO management/cmd/management.go:455: loading OIDC configuration from the provided IDP configuration endpoint https://nb.groblers.co.uk/.well-known/openid-configuration
management-1  | Error: failed reading provided config file: /etc/netbird/management.json: OIDC configuration request returned status 502 with response:
management-1  | 502 Bad Gateway
management-1  |
management-1  | 502 Bad Gateway
management-1  | openresty
management-1  |
management-1  |
management-1  |

It seems like there is an issue with either caddy or zitadel, can you please share all logs?
docker compose logs

logs :
WARN[0000] /home/hybrid/netbird/infrastructure_files/artifacts/docker-compose.yml: version is obsolete
dashboard-1  | + LETSENCRYPT_DOMAIN=nb.groblers.co.uk
dashboard-1  | +<EMAIL_ADDRESS>dashboard-1  | + NGINX_SSL_PORT=443
dashboard-1  | + '[' nb.groblers.co.uk-x == none-x ']'
dashboard-1  | + certbot -n --nginx --agree-tos --email<EMAIL_ADDRESS>-d nb.groblers.co.uk --https-port 443
dashboard-1  | NetBird latest version:
dashboard-1  | Saving debug log to /var/log/letsencrypt/letsencrypt.log
dashboard-1  | NetBird latest version:
dashboard-1  | Requesting a certificate for nb.groblers.co.uk
dashboard-1  |
dashboard-1  | Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
dashboard-1  |   Domain: nb.groblers.co.uk
dashboard-1  |   Type:   unauthorized
dashboard-1  |   Detail: <IP_ADDRESS>: Invalid response from https://nb.groblers.co.uk/.well-known/acme-challenge/bXtOOWgctTOU2-SPDJfxqZpxz4vk32WcuHnek0A5g94: 404
dashboard-1  |
dashboard-1  | Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.
dashboard-1  |
dashboard-1  | Some challenges have failed.
signal-1     | 2024-05-11T06:03:10Z INFO signal/cmd/run.go:110: running gRPC backward compatibility server: [::]:10000
signal-1     | 2024-05-11T06:03:10Z INFO signal/cmd/run.go:132: running gRPC server: [::]:80
signal-1     | 2024-05-11T06:03:10Z INFO signal/cmd/run.go:135: signal server version 0.27.4
signal-1     | 2024-05-11T06:03:10Z INFO signal/cmd/run.go:136: started Signal Service
signal-1     | 2024-05-11T06:10:39Z INFO signal/cmd/run.go:110: running gRPC backward compatibility server: [::]:10000
signal-1     | 2024-05-11T06:10:39Z INFO signal/cmd/run.go:132: running gRPC server: [::]:80
signal-1     | 2024-05-11T06:10:39Z INFO signal/cmd/run.go:135: signal server version 0.27.4
signal-1     | 2024-05-11T06:10:39Z INFO signal/cmd/run.go:136: started Signal Service
dashboard-1  | Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
dashboard-1  | 2024-05-11 06:03:24,805 WARN received SIGINT indicating exit request
dashboard-1  | 2024-05-11 06:03:24,805 WARN received SIGINT indicating exit request
dashboard-1  | + LETSENCRYPT_DOMAIN=nb.groblers.co.uk
dashboard-1  | +<EMAIL_ADDRESS>dashboard-1  | + NGINX_SSL_PORT=443
dashboard-1  | + '[' nb.groblers.co.uk-x == none-x ']'
dashboard-1  | + certbot -n --nginx --agree-tos --email<EMAIL_ADDRESS>-d nb.groblers.co.uk --https-port 443
dashboard-1  | NetBird latest version:
dashboard-1  | Saving debug log to /var/log/letsencrypt/letsencrypt.log
dashboard-1  | NetBird latest version:
dashboard-1  | Requesting a certificate for nb.groblers.co.uk
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:06:10:46 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03D\xC8{\x0By\x10y\xB3\xED\xB1\xB7\xA7\x1F\x05j\xB2R\x8A\x1D[j@\x90;\x03\xA6$\xB9\x92{?U\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:06:10:48 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03?w\xFC\xFE\x9Bv6i" 400 150 "-" "-" "-"
dashboard-1  |
dashboard-1  | Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
dashboard-1  |   Domain: nb.groblers.co.uk
dashboard-1  |   Type:   unauthorized
dashboard-1  |   Detail: <IP_ADDRESS>: Invalid response from https://nb.groblers.co.uk/.well-known/acme-challenge/WX7bdhcXbhNji0JqnWAWEntbWirZsuzB0FhfebNp4c8: 404
dashboard-1  |
dashboard-1  | Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.
dashboard-1  |
dashboard-1  | Some challenges have failed.
dashboard-1  | Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:06:10:53 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03\xAB\xB4\xC7\xEC\x8E\xC0D]\xBCJ\xD9\x8F\xD3\xAB\xBA<\x0EN>\xF9\x0B\xCC\xCD/+\xD5Y\x13\xC2\x09\x8F\xBB\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:06:11:02 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03e'J\x84\xFB\xEA\xE7\xF4\xA6K\xE7\xF4\x02\x89\xBB;\xD5\x1EE\xD7\x82\x9B;d`G/\xE5\x072\xD9\xB0\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:06:11:11 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03L\xAE\xA0\xE0\x9C\xF8-\x01\x04U\xF9\x88\x87\xAF\x06hI\xF4\x1F\xBB\xE0\x1C\xE3\xB6w\xA19&t\xED\xB2l\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:06:11:18 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03\xD3\xF2\xA7" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:06:59:54 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03\xE0@\xE1\x0C\xB1\x03{\x02\x9De\xFB?\xF9{IU}" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:06:59:54 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03\xA2\xE2J\x9C&\x1C\xCE\xC3%M;\xE9\xBC\xFCkF\xEB.\x89L2#D\x0F\x8C\x1E\xA4\x9C\xF6=\xB6\x9D\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:07:00:03 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03\xB4\x83Y\x97\x95r8V\xE1\x1C\xD7[o4\x1A24u\x0BZr\xA0\xB1E\xE5\x1Eu\xD2\x22\x0EB\x95\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:07:00:05 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03#\xEC3\xDD\x9F\x06w,d^X\xCB\xFC\xE6\x09\xE5\xDBT\xC5\xB8\x1A\xFC\x22\x12J9[>utt\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:07:00:07 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03B\xBF\xABNJP\xF6\xA4\xEBW\xA5\xA1\xEB\x9C2:F\x90*|'1\x00\x0F\xC2\xEC5&\x97~\xE8!\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:07:00:07 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03J\xBD\x03\xE2;\x9E\xC3\xD5\xC6RP\x09\xDA[\x04\xC1m\x15/b\xEA\xABr\x86\x1F\xE2\xE3@\xBE\x17\x0F\x1F\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"
dashboard-1  | <IP_ADDRESS> - - [11/May/2024:07:00:49 +0000] "\x16\x03\x01\x00\xB7\x01\x00\x00\xB3\x03\x03\xCC\x11&Z\x06\x1D\xEF\xE8\xA3\xDE\x9E\xF8\x1E\xFD\xDClV\x0F:\x9D)?\xED\x1F@R\x96\x9A\xD3!\x8A@\x00\x008\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 150 "-" "-" "-"

您好，您能分享管理服务的日志吗？您可以使用以下命令获取它们：
docker compose 日志管理

I'm also having issues with 502 when I'm building.
management-1  | 2024-05-11T14:14:17Z INFO management/server/telemetry/app_metrics.go:177: enabled application metrics and exposing on http://<IP_ADDRESS>:8081 management-1  | 2024-05-11T14:14:17Z INFO management/server/store.go:95: using SQLite store engine management-1  | 2024-05-11T14:14:17Z INFO management/server/migration/migration.go:114: Table for peer.Peer does not exist, no migration needed management-1  | 2024-05-11T14:14:17Z INFO management/server/migration/migration.go:114: Table for peer.Peer does not exist, no migration needed management-1  | 2024-05-11T14:14:17Z INFO management/cmd/management.go:161: update config with activity store key

您好，您能分享管理服务的日志吗？您可以使用以下命令获取它们：
docker compose 日志管理

I'm also having issues with 502 when I'm building.
management-1 | 2024-05-11T14:14:17Z INFO management/server/telemetry/app_metrics.go:177: enabled application metrics and exposing on http://<IP_ADDRESS>:8081 management-1 | 2024-05-11T14:14:17Z INFO management/server/store.go:95: using SQLite store engine management-1 | 2024-05-11T14:14:17Z INFO management/server/migration/migration.go:114: Table for peer.Peer does not exist, no migration needed management-1 | 2024-05-11T14:14:17Z INFO management/server/migration/migration.go:114: Table for peer.Peer does not exist, no migration needed management-1 | 2024-05-11T14:14:17Z INFO management/cmd/management.go:161: update config with activity store key

Not sure why you would hijack a thread if the symptoms of your problem is not the same as mine?
Apart from the 502 the errors are totally diffrent. :)

您好，您能分享管理服务的日志吗？您可以使用以下命令获取它们：
docker compose 日志管理

I'm also having issues with 502 when I'm building.
management-1 | 2024-05-11T14:14:17Z INFO management/server/telemetry/app_metrics.go:177: enabled application metrics and exposing on http://<IP_ADDRESS>:8081 management-1 | 2024-05-11T14:14:17Z INFO management/server/store.go:95: using SQLite store engine management-1 | 2024-05-11T14:14:17Z INFO management/server/migration/migration.go:114: Table for peer.Peer does not exist, no migration needed management-1 | 2024-05-11T14:14:17Z INFO management/server/migration/migration.go:114: Table for peer.Peer does not exist, no migration needed management-1 | 2024-05-11T14:14:17Z INFO management/cmd/management.go:161: update config with activity store key

Not sure why you would hijack a thread if the symptoms of your problem is not the same as mine? Apart from the 502 the errors are totally diffrent. :)

Nothing to do, he fixed it himself, and the next day he was able to access normally.

Ah ok.
Any insight one my problem? :)

I installed using NixOS and I saw the same error.
In my case it was a network issue and I had the same errors in the log as #2576


Either get CentOS 6 test build faster, or ditch it

In #412 a CentOS 6 Docker build was added to test everything in Drupal VM... and it works, but it's really really slow. Like 4-6x slower than the other environment builds.
I wonder if something in that Docker base image is screwy (a network setting?), or if it's just something crazy-slow that we won't be able to fix. So that we can get CI feedback in < 10 minutes, I vote to either disable it or fix it, and if it takes more than a couple hours' effort and we're getting nowhere, we just disable it and give everyone the caveat that only the latest OS releases have full automated test coverage.

cc @oxyc who originally mentioned the issue.

Wondering if this is what's going on:

https://www.reddit.com/r/devops/comments/3omkvm/anyone_else_have_slow_docker_builds_on_centos/
https://github.com/docker/docker/issues/10248#issuecomment-71690895

I also feel like the build started quicker when we defined python as our language. Now there's a long delay before the tests even get started. Do they have a set amount of ruby boxes (we always get a ruby box now), and a set amount of python boxes? Or maybe it's just some travis free-account limit...

Not sure... it's hard sometimes to gauge, because free accounts for OSS are always in a pool with no particular guarantees, so sometimes I've waited up to an hour for a particular instance to get going.

I vote for ditching it and merging #456. Testing it on the latest versions is good enough imo. If we decide to ditch centos 6, we need to change Ubuntu 14.04 to test the nginx scenario though.

Sounds good to me... maybe have ubuntu 14.04 (and moving forward, whatever the default is inside example.config.yml) run both the nginx and apache. Otherwise we could do both for both of the latest supported versions, but it's more important to me to make sure the defaults run across CentOS and Ubuntu.

Working on this now.


Utility macros in core + plugins

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
For end users & package maintainers
https://docs.getdbt.com/reference/dbt-jinja-functions — is this the right place, or will we want a different one?
Developers of dbt project/package code, especially ones trying to write cross-database SQL, need to know that these macros are now available for them to use. They can be called as either:
{{ dateadd(...) }}}
{{ dbt.dateadd(...) }}

They can be overridden by defining a macro named dateadd in the user's own project, or by setting up a dispatch project config to prefer versions in other installed packages.
For adapter maintainers
https://docs.getdbt.com/docs/contributing/building-a-new-adapter
They need to know:

to implement these macros for people using their plugin
to start inheriting/running the functional tests for those macros, which will live in the utils module of dbt-tests-adapter

What part(s) of the page would you like to see updated?
We're moving a bunch of "cross-db" macros from dbt-utils into dbt-core and adapter plugins. To that end, we should (hopefully) be able to "lift and shift" most of the Markdown from this section of the dbt-utils README.
Additional information
No response

Resolved by https://github.com/dbt-labs/docs.getdbt.com/pull/1619


Behavior of cp changed since 4.14.0

With cloud-files 4.13.0, if I run cloudfiles cp test_file /tmp/nonexist/, cf will create /tmp/nonexist/ and then copy the file, since 4.14.0 cf fails with a FileNotFoundError if the target folder does not exist already. With the newer version, I have to treat local operation differently, while the old behavior was more consistent with other protocols like gs and s3.

Hi Ran!
On MacOS I created the following test case:
(ig) wms:~/code/igneous/projects/fly_synapses$ cloudfiles cp hello.txt ./amazing/
(ig) wms:~/code/igneous/projects/fly_synapses$ cloudfiles cp hello.txt /tmp/notexists/
(ig) wms:~/code/igneous/projects/fly_synapses$ ls /tmp/notexists
hello.txt

Have you tried updating to the latest version?

You are right, I pinned the version to avoid issue #92. It seems that issue is also fixed after 4.18. I will close both issues.


regex

Hi,
thanks for the great tool, sadly I've got some problems with it.
Version: (i do not know how to get it while downloading it with go get ..)
md5sum /root/go/bin/cook
## output:
# 55e5ae65e1dafadb32960afb301f4349  /root/go/bin/cook

I do not understand the regular expression function. I'm trying to use the regex from here
Empty responses:
echo -e 'Job[49]\njob[49]\nJob[49]\njob[50]' | cook -d - d -m regex[^[a-z]+\[[0-9]+\]]
## outputs nothing

echo 'adam[23]\neve[7]\nJob[48]\nsnakey' | cook -d - -m regex[^[a-z]+\[[0-9]+\]] d
## output (should be adam[23] and eve[7] but is:
# adam[23]

The date function different in linux (maybe in future change it to square bracket instead of parenthesis)?
cook help usage | grep dob | cut -d '$' -f 2 | sh
## output:
# sh: 1: Syntax error: "(" unexpected

# i found the problem, should wildcard the brackets in linux:
cook help usage | grep dob | cut -d '$' -f 2 | sed -e 's/^[ \t]*//' | replace \( \\\( | replace \) \\\) | bash
elliot_17Sep1994
elliot_Sep171994
elliot_17/Sep/1994
elliot_Sep/17/1994
elliot_17-Sep-1994
elliot_Sep-17-1994
elliot_17.Sep.1994
elliot_Sep.17.1994
elliot_17.1994
elliot_Sep.1994
elliot_17.Sep
elliot-17Sep1994
elliot-Sep171994
elliot-17/Sep/1994
elliot-Sep/17/1994
elliot-17-Sep-1994
elliot-Sep-17-1994
elliot-17.Sep.1994
elliot-Sep.17.1994
elliot-17.1994
elliot-Sep.1994
elliot-17.Sep

regards,
esp0xdeadbeef.

usage for linux would be at this moment something like this:
cook help usage | cut -d '$' -f 2 | replace \( \\\( | replace \) \\\) | replace \` \\\`
## output:
# BASIC USAGE
#  cook -start admin,root  -sep _,-  -end secret,critical  / start sep end
#  cook / admin,root _,- secret,critical
#
# FUNCTIONS
#     Use functions such as date for different variations of values
#  cook -dob date\(17,Sep,1994\) elliot _,- dob
#
# RANGES
#     Use ranges like 1-100, A-Z, a-z or A-z in pattern of command
#  cook 1-999
#  cook a-z
#  cook A-Z
#  cook X-d
#
# RAW STRINGS
#     Print value without any parsing/modification.
#  cook -date \`date\(17,Sep,1994\)\` date
#
# PIPE INPUT
#     Use - as param value for pipe input
#  cook -d - d / test
#
# USING -min
#     Print value without any parsing/modification
#  cook n n n -min 1

Hi @esp0xdeadbeef,
Thanks for mentioning the issue.
Seems like there are a few issues while running cook in Linux.
I will start fixing them soon. Meanwhile, feel free to drop other bugs/issues you found.
Thanks

Gitesh

usage for linux would be at this moment something like this:
cook help usage | cut -d '$' -f 2 | replace \( \\\( | replace \) \\\) | replace \` \\\`
## output:
# BASIC USAGE
#  cook -start admin,root  -sep _,-  -end secret,critical  / start sep end
#  cook / admin,root _,- secret,critical
#
# FUNCTIONS
#     Use functions such as date for different variations of values
#  cook -dob date\(17,Sep,1994\) elliot _,- dob
#
# RANGES
#     Use ranges like 1-100, A-Z, a-z or A-z in pattern of command
#  cook 1-999
#  cook a-z
#  cook A-Z
#  cook X-d
#
# RAW STRINGS
#     Print value without any parsing/modification.
#  cook -date \`date\(17,Sep,1994\)\` date
#
# PIPE INPUT
#     Use - as param value for pipe input
#  cook -d - d / test
#
# USING -min
#     Print value without any parsing/modification
#  cook n n n -min 1

Yeah, I got that. I am an all-time window user.😅
That's why I am unaware of these issues.

Hey @esp0xdeadbeef
For just using cook help usage, do you have to use that long command?

Hey @esp0xdeadbeef
I have fixed the functions, Now functions are using square brackets
For the regex, use this
[A-Za-z]+\[[0-9]+\]


Static analyzer ignores Nullability attributes

Description
I have added your library to my WinFroms project (.NEt Framework) to use Nullability attributes with static analyzers. Even though I added the attribute, the analyzer still analyzes nulls incorrectly.
Reproduction Steps
See code below
Expected Behavior
Static analyzer do not trigger CS8602 Dereference of a possibly null reference.
Actual Behavior

System info
This section should contain useful info such as:

PolySharp 1.8.1
.NET Framework
Windows 11 22H2
Visual Studio 2022 (17.4.0)

OK. I found a solution. I put <LangVersion>11.0</LangVersion>1 into second <PropertyGroup> (with conditions) not to first one.
It is possible to work this with string.IsNullOrEmpty()?


💡[Feature]: Adding Google Authentication using Firebase

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
@sk66641 I want to add Google Authentication using Firebase. Kindly assign this issue to me.
Use Case
Using this feature will allow to login using your gmail account.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@sk66641 Kindly pls tell wheteher I should start working on this or not?


Case(1): Add a changed line

Adds a changed line

Successfully created backport PR #182 for case1-backport-target.


hashicorp-tf-password rule seems to be too wide

Describe the bug
While scanning a tons of repositories recently, I have the feeling that the hashicorp-tf-password in Gitleaks seems to be a huge source of false positive. It raises findings that were usually avoided by gitleaks (with entropy mechanisms etc).
To Reproduce
Texts with the password stopword
Expected behavior
These kind of matches should be handled by the generic-api-key rule, or at least one of the built-in rules.
Screenshots

Basic Info (please complete the following information):

OS: Ubuntu 22.04
Gitleaks Version:  8.18.0

Additional context
Maybe we could bind the rule to a specific file extension ?
cc @zricethezav

I agree, I stumbled on this issue when looking at why I got detections for hashicorp-tf-password on a repo that would enable gitleaks for the first time. All issues were in documentation example strings, just like here

I also agree that this seems a little silly. This is being picked up in nearly all of our pipelines now.
It is fairly common to have test files which have a password set to "password"


[Data Lake Performance] Test Scenarios for T2

Summary
The focus of these changes is to create the initial set of performance test scenarios for the v12.x (track two) Data Lake client library.
Last Upstream Rebase
Wednesday, December 3, 10:18am (EST)

I'm going to merge this in so that it is more easily available for others within the repository.   I'll continue to monitor for feedback and adjust as needed.


Swift 4.1 Warnings

@huynguyencong
Needs update to silence 4.1 warnings
    valuePointer.deinitialize() // 'deinitialize()' is deprecated: the default argument to deinitialize(count:) has been removed, please specify the count explicitly

    valuePointer.deallocate(capacity: 1)  //'deallocate(capacity:)' is deprecated: Swift currently only supports freeing entire heap blocks, use deallocate() instead

Fixed. Thanks for your feedback. Please update latest version


Threads, Spaces and Pages integration

Perplexity pro is providing the Users with 3 amazing Features. Are these any time soon being released ?
Threads

Individual conversation chains that contain your searches and their responses
Can be organized and grouped for easy reference
Accessible from the Library tab for quick retrieval

Collections

Folders that help organize related threads together
Allow customization of AI behavior through specific prompts
Enable collaboration through sharing links with other users

Spaces
A collaborative research and organization hub that offers:

Organization of research threads by topics or projects
File upload capabilities (up to 50 files per Space for Pro users)
Customizable search across web and personal files
Collaboration features allowing you to invite viewers and contributors

Search Options in Spaces:

Web-only search
Space files search
Combined web and files search

Pages
A content creation and publishing platform that enables:

Transformation of research into shareable content
Customizable formatting and structure
Visual enhancement with generated or uploaded images
Direct publishing to Perplexity's content library

+1. need to be able to upload my files.


Composing routers with Finagle filters/services

For now there is only way to do it: convert router into service. I was wondering if it would be useful to apply filters/service directly to router (just like we did for old-style endpoint).

Closing this since it's no longer a Finch idiomatic approach.


Error in getting started guide

As @distributorofpain pointed out, the tables of contents are messed up!
I'm looking here:

and

Where are you seeing the malformed toc?
It looks ok to me: http://docs.mantl.io/en/latest/getting_started/index.html#preparing-to-provision-cloud-hosts


After the window is published using the transparencylevelhint property, the title bar is blurred together

After the window is published using the transparencylevelhint property, the title bar is blurred together, and I have not set the extendclientareatodecorationshint property.
My code is like this:
<Window xmlns="https://github.com/avaloniaui"         xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"         xmlns:d="http://schemas.microsoft.com/expression/blend/2008"         xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"         mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="450" 		Background="Transparent" 		TransparencyLevelHint="AcrylicBlur"         x:Class="MyApp.MainWindow"         Title="MyApp"> 	<Panel> 	</Panel> </Window>
The program works very strangely.

What Windows version is that?

Probably duplicate of https://github.com/AvaloniaUI/Avalonia/issues/8705
And https://github.com/AvaloniaUI/Avalonia/issues/6028
See last issue how to solve it


Postscript name length limits

The description for name ID 6 states

must be no longer than 63 characters

Name ID 25 was added in OT1.8 for variable fonts to give a prefix for generating PS names for variable font instances. It makes reference to Adobe Technical Note #5902: “PostScript Name Generation for Variation Fonts”, but that assumes a length limit of 127 characters.
Should the length limit for name ID 6 be upped to 127?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9bc5a9d9-70e1-97b3-6926-c176e1a2401d
Version Independent ID: 1afb0f5b-d1a7-7d69-d175-a5c9382b74be
Content: name - Naming table specification - Typography
Content Source: typographydocs/opentype/spec/name.md
Product: typography
GitHub Login: @PeterCon
Microsoft Alias: PeterCon

+1 to longer limits.

We'd like to consider this for OT 1.9. This will give us time to investigate issues we are seeing (e.g. there are indications that installation of OT-CFF fonts with >63 char PostScript names fails on Windows).


test: canvas widget coverage junit

Description
Improve the coverage for Widgets in Junit
PR fixes following issue(s)
Fixes #25589

/ok-to-test


Update logos + make dropdown scrollable

Description

Fixes dropdown scroll bug
Brought in higher-res icons

Current dependencies on/for this PR:

#130  👈
main

This stack of pull requests is managed by Graphite.

@tarunkhasnavis is this good to merge?


 The main goal of a CDN is to provide fast and reliable delivery of web content to users located at different locations around the world. CDNs use a variety of techniques to cache and distribute content, such as HTTP caching, server-side caching, and client-side caching, to ensure that content is delivered quickly and efficiently to end users.",
"learn_more_URL":"https://www.cloudflare.com/learning/cdn/what-is-a-cdn/",
"tag": "web",
"abbreviation": "CDN",
"author_name": "Harshith Shetty",
"author_link": "https://github.com/Harshith-Shetty"
}

Added, thank you :)


Cannot consume data from UDP multicast

I have a power monitor that sends data as UDP multicast. I tried a lot of things and found out that Influxdb can't ingest UDP data if it is a multicast.

@quaintdev have you tried using telegraf with the socker_listener plugin to ingest the UDP data? Based on https://github.com/influxdata/telegraf/issues/5352 it looks like multicast should be supported there.


encrypted state must contain the hash of last request

In order for a newly joining worker to know where to catch up after synching with a previous worker (#35), we should write the hash of the request that caused this state update to the state itself. This way, the joining worker can scan past events for this request and catch up.

this is actually missing in #61

connected to #38

since a newly joining worker can now re-sync from ChainRelay directly, this is not necessary anymore


@template() unexpectedly processes variables

I don't understand what i doing wrong, it seems everything is working well, but for some reason the template gets [object HTMLDivElement]
HELP! I already broke my brain!
View and template

looks like you are trying to code those templates as haml templates, but they are underscore jst templates.
To understand jst templates read over the underscore docs at http://underscorejs.org/#template
for example '= artist' should become <%= artist %>

No, if i write  <%= artist %> i get: & lt;%= artist %& gt;
And I use 'haml_coffee_assets' gem.


Webpack not watching for changes on Ubuntu 15.10

Webpack is not watching for file changes.
PLatform: Ubuntu 15.10
Arch: 64
Node: v4.4.1
This whole thing used to work on Windows with nodejs 0.10. But I installed fresh ubuntu, new node v4 and now its throwing warning too.
Here is config -
{
  "name": "proto",
  "version": "1.0.0",
  "dependencies": {
    "bootstrap": "3.3.5",
    "classnames": "2.2.0",
    "font-awesome": "^4.5.0",
    "history": "1.13.0",
    "jquery": "2.1.4",
    "js-cookie": "2.0.4",
    "json-loader": "0.5.3",
    "marked": "0.3.5",
    "moment": "2.10.6",
    "moment-timezone": "0.4.1",
    "node-libs-browser": "0.5.3",
    "query-string": "2.4.2",
    "react": "^0.14.7",
    "react-addons-css-transition-group": "0.14.0",
    "react-addons-pure-render-mixin": "0.14.0",
    "react-addons-test-utils": "0.14.0",
    "react-document-title": "1.0.4",
    "react-dom": "^0.14.7",
    "react-fontawesome": "^0.3.3",
    "react-lazy-load": "2.0.1",
    "react-paginate": "^0.5.4",
    "react-router": "^2.0.0",
    "react-textarea-autosize": "3.3.0",
    "reflux": "0.3.0",
    "select2": "3.5.1",
    "lodash": "^4.6.1"
  },
  "private": true,
  "scripts": {
    "test": "node_modules/karma/bin/karma start tests/karma.conf.js --single-run",
    "test-watch": "node_modules/karma/bin/karma start tests/karma.conf.js",
    "lint": "node_modules/.bin/eslint tests/js proto/static/webapp/app --ext .jsx",
    "deploy": "set \"NODE_ENV=production\" && webpack -p --config webpack.config.js",
    "dev": "set \"NODE_ENV=development\" && node_modules/.bin/webpack -w --config webpack.config.js --devtools --progress"
  },
  "devDependencies": {
    "autoprefixer": "^6.0.3",
    "babel-core": "5.8.33",
    "babel-eslint": "5.0.0-beta9",
    "babel-gettext-extractor": "^1.0.2",
    "babel-loader": "5.3.3",
    "chai": "3.4.1",
    "copy-webpack-plugin": "^1.1.1",
    "css-loader": "^0.18.0",
    "enzyme": "^1.1.0",
    "eslint": "1.9.0",
    "eslint-plugin-getsentry": "1.0.0",
    "eslint-plugin-react": "3.11.2",
    "extract-text-webpack-plugin": "^0.8.2",
    "file-loader": "0.8.4",
    "gettext-parser": "1.1.1",
    "graceful-fs":"^4.0.0",
    "karma": "0.13.19",
    "karma-chai": "0.1.0",
    "karma-mocha": "0.1.10",
    "karma-phantomjs-launcher": "0.1.4",
    "karma-sinon": "1.0.4",
    "karma-sourcemap-loader": "0.3.6",
    "karma-webpack": "1.7.0",
    "less": "2.5.3",
    "less-loader": "2.2.1",
    "mocha": "2.3.4",
    "node-sass": "^3.4.1",
    "postcss-loader": "^0.8.0",
    "sinon": "1.17.2",
    "sinon-chai": "2.8.0",
    "sprintf-js": "^1.0.3",
    "sass-loader": "^3.1.1",
    "style-loader": "^0.12.4",
    "url-loader": "0.5.6",
    "webpack": "1.12.14"
  }
}

Warning
WARNING in /home/rskumar/Projects/proto/~/chokidar/lib/fsevents-handler.js
Module not found: Error: Cannot resolve module 'fsevents' in /home/rskumar/Projects/proto/node_modules/chokidar/lib
 @ /home/rskumar/Projects/proto/~/chokidar/lib/fsevents-handler.js 7:17-36
Child extract-text-webpack-plugin:
        + 102 hidden modules

On Linux you probably need to increase number of inotify watchers: https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers
Looks like it's watching files in node_modules and only filtering them out later, but this fills the inotify watchers limit.

@rskumar Did that solve it for you?

I don't remember how I fixed it. :(

Just remove var webpack = require('webpack');
from top of the webpack config file, and it's will fix

removing the require('webpack') just means that a globally installed webpack must be used instead, so you have less control over the version. maybe your global webpack's version avoided this problem, rather than using the version in your package.json dependency list.

removing the require('webpack') just means that a globally installed webpack must be used instead, so you have less control over the version. maybe your global webpack's version avoided this problem, rather than using the version in your package.json dependency list.

confirmed @celebro's answer solved the problem.
ubuntu 17.04
node 8.4.0

@celebro's answer solved it for me as well. Thanks!

Huge huge thanks @celebro. Worked like charm for me as well!

@celebro's answer solved the problem.
ubuntu 20.04
node 14.13.0


Liveness check fails with Grafana charm

So apparently the liveness check is failing and crashing the pod.

The issue is related to the charm container:
Containers:
  charm:
    Container ID:  containerd://6f23ccbc1c403570f0faf800fe692358f3ce488801db7db189b7126ce46ce50d
    Image:         jujusolutions/charm-base:ubuntu-20.04
    Image ID:      docker.io/jujusolutions/charm-base@sha256:e16ca5a76c033e6c48f4ae57c73d9c691c647a014925359bc435d588357d4d88
    Port:          <none>
    Host Port:     <none>
    Command:
      /charm/bin/containeragent
    Args:
      unit
      --data-dir
      /var/lib/juju
      --charm-modified-version
      0
      --append-env
      PATH=$PATH:/charm/bin
    State:          Running
      Started:      Mon, 02 Aug 2021 11:22:36 +0200
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Mon, 02 Aug 2021 11:16:11 +0200
      Finished:     Mon, 02 Aug 2021 11:17:30 +0200
    Ready:          False
    Restart Count:  33
    Liveness:       http-get http://:3856/liveness delay=30s timeout=1s period=10s #success=1 #failure=2
    Readiness:      http-get http://:3856/readiness delay=30s timeout=1s period=10s #success=1 #failure=2
    Startup:        http-get http://:3856/startup delay=30s timeout=1s period=10s #success=1 #failure=2
    Environment:

Wrong charm sorry :-)


Test in branch v2.0.x always fails

The test in branch v2.0.x always fails, complaining database dirty flag set.
It looks like this is a problem that has been fixed on the master branch, but was forgotten on the branch v2.0.x.
I have made a pull request #67 to branch v2.0.x for this.
Considering that the branch v2.0.x is currently being tracked by multiple branches as submodules in EOSIO/eos, it is desired that we fix the test error and make the test pass.

Pull request merged. I am closing this issue.


Create a Login page

Validate the user Credentials provided and validate the user using endpoint /validate
If the user is valid redirect
if user is invalid throw error

Done


FullScreen Modal ?

how to show fullscreen / large modal ?

There is no built-in full screen modal. But you can modify the size.


style(Badge): Update Badge position

Status :
Ready

Description :
Update Badge Design

Related Issues :
#287
Todos

[x] Tests
[x] Documentation

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


kaolin/cython/triangle_hash.pyx' doesn't match any files

I tried installing kaolin on both windows10 and ubuntu 16.04 and in both cases I recieve the same error

Any suggestions ?

Hi, thank you for using Kaolin! The library went through a major rewrite with the version 0.9.0, and this issue is no longer current. Please refer to our latest documentation:
https://kaolin.readthedocs.io/en/latest/


Minor cleanups to devices.py.

Just removing some lint.

@Lukasa (at random), would you mind reviewing?

LGTM! :cake:


No colors to select

I edited the bard-custom-colors.php in vendor/xndbogdan/statamic-bard-text-color/config/ but I can't select colors neither Default nor Custom. This is important for me.
Not so important but interesting, how to get the tailwind colors?

Hi.
Can you try creating the file in your application config folder?
I'll investigate this issue as soon as possible.

Issue was fixed
Sorry for fixing it so late 😅


Documents need a "refresh"

List all of the "documents" that need to be refreshed after a release.
Example: https://cenw-wscoe.github.io/sgdc-cdts/docs/index-en.html#Current_CDTS_supported_versions
Transferred from: https://gccode.ssc-spc.gc.ca/iitb-dgiit/nw-ws/sgdc-cdts/-/issues/193

#223 This can be part of the documentation.

Merged - #466


Move URI type from pion/ice to pion/stun

This PR moves the URL type from the pion/ice module to pion/stun and renames it to URI.
Hence this module gains full support for RFC7064 and RFC7065 (see #65).
The PR also adds a new function stun.DialURI(u *stun.URI, cfg *stun.DialConfig) which create the underlying connection for the client for you based on the URI Scheme and transport protocol. Hence it can also use the dtls and tls modules to establish an encrypted connection.
Currently, the connection establishment is done by hand in various places:

ICE relay candidate gathering
STUN example commands
TURN example commands

This is also related to https://github.com/pion/stun/issues/35#issuecomment-1315361580
Furthermore, we now fully support passing a custom transport.Net for testing which was previously not supported for TLS / DTLS connections.

This change currently breaks the API of the module. As we are still with v0, I dont think this is a huge deal. The breaking changes are also really minor..


Update opam-ci-check with lower bound on opam.2.3.0~alpha1

Picking up the increment of the opam version

Closed in favor of #368


add init_with_level function to pass log level explicitly

Signed-off-by: siddontang<EMAIL_ADDRESS>We found that the log body will be evaluated even in trace!, see https://github.com/tikv/tikv/issues/3537
In the origin init function, it will use max level, we need to pass the log level explicitly to avoid the above problem.
PTAL @dpc

what do you think @dpc


Release/0.4.0

Changelog

Add back-off on 100% event sending failure (#9)
Add event-level Subject (#61)
Add IP address property to Subject (#62)
Rename send_limit to batch_size in Emitter (#63)

Documentation
Documentation updates are in this PR on data-value-resources.

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.


Fixed validateExpression property not returned in sling model

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

closing this. Will fix that in rule editor since we can do that there.


[FEATURE] Add chart tooltips

Is your feature request related to a problem?
Add chart tooltips for a better user experience. Tooltips are already implemented on the Discover page.
Do you have any additional context?

As these above are outdated, the next screenshot shows the default vega-lite tooltip

@amsiglan @kamingleung what do you think, is it ok to go with the default tooltip?

Closed with PR #225

@jovancacvetkovic Sorry for a late respond, are we using the tooltip component provided by Vega-lite? https://vega.github.io/vega-lite/docs/tooltip.html
Let's style the tooltip to match the ElasticCharts style along showing the color of the trend line the data is on. For graphs with multiple datasets like your screenshots, it should show all of the data set in the same tooltip, see this page for a demo.
Also a screenshot reference on ElasticCharts:

@kamingleung Yes, we are using the default tooltip from Vega-lite, current version of vega-tooltips we are using doesn't support customizing the tooltips. I created an issue #254 to check if we can safely update the vega-tooltips version.


Added example for multiple WASM net instances

Coverage remained the same at 100.0% when pulling bf5ddbddc08fe44bd0b9c068b50b1a044c37a36e on dev into c2bfd98a7ea2e2681eff8152467c619160281ea8 on master.


WIP Integrate current status of react-geo-client-template

Integrates latest react-geo-client-template (status) to project.

IMHO the client should not contain the full history of the template client.


[cli] Update to latest entity service status api

The results command currently determines if a mapping has completed based on the http status code. However we were incorrectly returning a 503 for a mapping that is in progress - which was sometimes replaced by a genuine 503 from nginx when the client is rate limited.
Once the upstream server has released a new version, clkhash should be changed too.

rest client has been updated and is part of release 0.11.2


⚠ Processors has degraded performance

In d534440, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 67 ms

Resolved: Processors performance has improved in 9dd9025.


[ADVANCED] SVG Animation for Toggle Button

Hey! What exactly needs to be done here? There is already an animation for the toggle button. What changes need to be made? I would like to work on this issue.

Hey! What exactly needs to be done here? There is already an animation for the toggle button. What changes need to be made? I would like to work on this issue.

There is no toggle button at all currently.
Once that is resolved. I share more details on this one

Hey! What exactly needs to be done here? There is already an animation for the toggle button. What changes need to be made? I would like to work on this issue.

There is no toggle button at all currently.
Once that is resolved. I share more details on this one

Sure, np👍.

@smaranjitghose assign me this issue under LGM-SOC'21


Support a Docker image for common protos.

This commit adds support for deploying a Docker image when we issue a release.
The usefulness of this assumes a release strategy (which we more or less do not have yet), but getting this in place at least allows us to create gapic-generator-{lang} Docker images that can depend on this.

Whups. Wrong base branch.


Feat oma

Here is my new "OMA_detect" implementation to detect movements and label them as artefacts before bruxism or MEMA detection.
Important: there are 1 optimization I wish to do but, it will imply consequences:

as we made the check impedance algo optional, we should put the imp_chan input of the function as optional too. But due to our coding, it's not the case now. Currently, if we want to use preprocess, we have to put a list of channel (even empty), that's not optimal.
Making this change will have as consequence to modify on each notebook the inputs of preprocess, it's tricky.

closing and see #67


Lower AP when training retinanet_r50_fpn_1x_coco

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
I only get 36.3 AP not 36.5
Reproduction

What command or script did you run?

Did you make any modifications on the code or config? Did you understand what you have modified?
I set samples_per_gpu=4, use 4 gpus, so lr is same.

What dataset did you use?
coco2017
Environment

Please run python mmdet/utils/collect_env.py to collect necessary environment infomation and paste it here.
sys.platform: linux
Python: 3.7.7 (default, May  7 2020, 21:25:33) [GCC 7.3.0]
CUDA available: True
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 10.1, V10.1.105
GPU 0,1,2,3,4,5,6,7: GeForce GTX 1080 Ti
GCC: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609
PyTorch: 1.5.0
PyTorch compiling details: PyTorch built with:

GCC 7.3
C++ Version: 201402
Intel(R) Math Kernel Library Version 2020.0.1 Product Build 20200208 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v0.21.1 (Git Hash 7d2fd500bc78936d1d648ca713b901012f470dbc)
OpenMP 201511 (a.k.a. OpenMP 4.5)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 10.1
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_37,code=compute_37
CuDNN 7.6.3
Magma 2.5.2
Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -fopenmp -DNDEBUG -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_INTERNAL_THREADPOOL_IMPL -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_STATIC_DISPATCH=OFF,

TorchVision: 0.6.0a0+82fd1c8
OpenCV: 4.2.0
MMCV: 0.5.1
MMDetection: 2.0.0+c802b17
MMDetection Compiler: GCC 5.4
MMDetection CUDA Compiler: 10.1

You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source] conda
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Error traceback
If applicable, paste the error trackback here.
There is no bug.
But I notice that:
For me: Epoch [1][50/7330] loss_cls: 1.2075, loss_bbox: 0.7025
For you: Epoch [1][50/7330] loss_cls: 1.23362, loss_bbox: 0.68972
They are quit different.
Also, I download resnet50-19c8e357.pth as pretrained model and I got same AP when using mmdetectionv1

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!

Well, I may know the reason, warmup_ratio=1.0/3 may be still a better choice for it.


fix(elements): Fix sign-in route registration

Description
Prevents multiple route registrations and prepare calls.

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

!snapshot

Hey @tmilewski - the snapshot version command generated the following package versions:

Package
Version

@clerk/elements
0.2.2-snapshot.v2c9ad20

gatsby-plugin-clerk
5.0.0-beta.45

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/elements
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact

!snapshot

Hey @BRKalow - the snapshot version command generated the following package versions:

Package
Version

@clerk/elements
0.2.2-snapshot.v25d666f

gatsby-plugin-clerk
5.0.0-beta.45

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/elements
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact


keymutex: simplify unlocking

What type of PR is this?
/kind api-change
What this PR does / why we need it:
The common pattern is:
  mutex.LockKey(key)
  defer mutex.UnlockKey(key)

However, linters point out the the error return of UnlockKey is not checked.
It is possible and okay to suppress that because it is known that the right key
is getting passed into that function:
  mutex.LockKey(key)
  defer func() {
     _ = mutex.UnlockKey(key)
  }()

But this is rather ugly. By returning an unlock function, locking and unlocking
can be done in a single line with less code:
  defer mutex.LockKey(key)()

Special notes for your reviewer:
Strictly speaking, this is an API break because it changes the LockKey signature. But in practice, existing code continues to compile and work as intended.
Release note:
simpler keymutex: locking and unlocking in a single line

/remove-kind api-change
this label is intended for REST / config / cli API changes, not go API changes
because this repo does not maintain release branches and tags, it has a strict forward compatibility requirement on the exposed go API surface (checked by the apidiff presubmit)

adding a new function to the interface would also not be API-compatible
it's not clear to me that the _ = ... workaround is incorrect. any time an unlock is separated in from from a lock, something else could have unlocked the id, and depending on the implementation, removed knowledge of the id from the locker.

adding a new function to the interface would also not be API-compatible

True. Then it's really not worth it for a minor convenience enhancement.

it's not clear to me that the _ = ... workaround is incorrect.

It isn't incorrect, just boilerplate code that I was trying to avoid.


Infinite Loop when parsing list

I see an infinite loop here when parsing this example content:
Md.parse("test\n   - A\n  - B\n  - C\n")

Hi @chaitanyapandit,
thank you for reporting. I will check it and fix ASAP.

Package published to https://hex.pm/packages/md/0.9.6
(a4036b1e63a907e90fe2d3eda7da4144560470496db31ef90003488425b4ab6b)


chore: Move widget deprecation messages from propertyPaneView to individual Widget configurations

@rajatagrawal
Description

In this PR I have added getEditorCallout method which can also used to return deprecataed messages.
I have updated above method for these deprecated widgets:

InputWidget
DropdownWidget
DatePickerWidget
IconWidget
FilePickerWidget
MultiSelectWidget
FormButtonWidget
ProgressBarWidget
CircularProgressWidget
ListWidget

OUTPUT:

[!TIP]
Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).
Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes 26526
or
Fixes https://github.com/appsmithorg/appsmith/issues/26526

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[x] No

Rest of the changes look good.


Create 18th October,2024

Meeting folder:
I would like to provide a brief overview of our meeting today(18th October, 2024) and the changes that need to be implemented moving forward.


Fix SmoothSeekBar Ripple Effect glitch that happens while dragging fast

Closing this issue as it happens in Android 6.0 by default.


Choose Book

The user should be able to choose a book from a set of devices connected to the RPI. For now, ignore connected USB devices and use the examples folder in order to build the frontend.

[x] get a list of all books in the folder
[x] display a button at the top of the screen
[x] when pressed, Display all book titles in the folder (probably in a dialog)
[x] switch to selected book

Restructured it to be completely keyboard driven, without UI elements since for now, it is unlikely for the patient to use a touchscreen


Feature request: Please add a Base 91 decoder :)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. E.g. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Duplicate of #1213


Provide FlushSyncDefaultLive by default in Evolu

and provide a custom FlushSync layer if needed only. Not all implementations will do need such a thing, but react of course (no change for @evolu/react) and maybe @evolu/solid later (see its flushSync).
Other evolu implementations (e.g. @evolu/web or @evolu/react-native) are still using an empty callback provided by  FlushSyncDefaultLive by default.

Yeah, that makes sense, thank you.
Btw, I'm currently refactoring Evolu (check the branch), but I will merge it anyway.


Appropiately self-heal on reorgs

This is a bit of a long shot issue, mostly for when things are already set in prod.
Right now, the indexer is not really resilient to reorgs. While rare, we should make sure it can detect them and self-heal.

Hey @Evalir, we should look into this! :eyes:
Could you share your strategy for addressing this issue? Perhaps something like having a safety reorganization margin and indexing blocks up to that point?

Hmm yeah, frankly I'm not super knowledgeable on how reliable production systems like Polygonscan (which has to deal with big reorgs frequently :D) do it; but the most straightforward strategy is a having a margin to the tip.
Off the top of my head (haven't thought deeply about this) I assume another viable strategy would be to check the new block hash against the previous one to see if it hashes back to the received block (essentially, check that N-1 indeed precedes block N). If it doesn't match, a reorg happened somewhere. I guess this strategy could let the indexer be as up-to-date as possible while being able to backtrack reorgs.

Some hours ago the indexer is crashed while trying to write to postgres. A validator has sent two blocks proposals (one could slash the validator for it). Since we consider block numbers unique in the db schema, postgres complains when it tries to insert another block with the same number, and keeps retrying, so that newer blocks are not processed.
@PJColombo and I have spoken today about this issue and we are prioritizing it. It is affecting blobscan.com too (shows last indexer was 4 hours ago).
Here are the relevant transactions:

Block 1 for slot 62506
Block 2 for slot 62506
Slot 62507

From there we can see that the parent hash of slot 62507 coincides with only one of the two blocks in slot 62506. (there are no slashers running in devnet-8 at the moment so that is why they are both shown as correct (finalized).
I wonder if simply adding a check of the parent hash is enough to appropriately self-heal and discard forked blocks. @Evalir what do you think? do you think this is enough?

First of all, I really like that you've linked my explorer to demonstrate the problem ♥
There is unfortunately a small issue, which currently shows all finalized blocks as "orphaned" in the block details.
Actually, block 2 in the example above is the canonical block and shouldn't be shown as orphaned. That's a display issue only, it's correct in the backend DB.
I gonna share some thoughts I had in mind when implementing the indexer for the light-beaconchain-explorer.
It's probably not 1:1 transferable to blobscan, but might help to improve your indexer too :)
There are two possible indexing strategies.

Index the canonical chain only (I think that's the strategy you're currently trying to achieve.)
The indexer follows the block event stream.
For each block event the appropriate block header is loaded.
The parent root within the block header is checked against the block root of the last block the indexer received earlier.
If it does not match, discard all blocks that were previously indexed up to the slot number of the incoming block.
Do indexer logic for the new block and set it as last received.

The event stream will basically do all the reorg logic for you.
When a reorg happens, there are block events emitted for all reorganized blocks in correct order - so from indexer perspective it just looks like  going back x blocks, and receiving x new blocks one by one.

By discarding previously indexed blocks when going back, you could even keep your primary key on the slot number.

Note that this strategy don't necessarily gives you the canonical chain. It's just the canonical chain from the connected CL nodes perspective. If the client is forked off on a non finalizing chain, you're following that chain and you'll hit a large reorg at some time.

Index the whole chain including all orphaned blocks
That's the much more complex strategy. I've tried to achieve that via a similar way as before, but got into big troubles with handling the orphaned blocks properly. Especially when you try to grab events from multiple CL nodes (which is necessary if you want to track orphaned blocks reliably), its near impossible to get a consistent view of the canonical chain. There will be situations where the connected clients don't agree with each other and send out different head events.
For that reason, I'm not even trying to do any persistent canonical/orphaned detection before finalization. Finalization checkpoints are the only reliable way to determinate the canonical chain. Actually I'm not indexing unfinalized blocks at all, because I cannot be sure what kind of processing is needed (my orphaned processing is different than for canonical blocks).

To achieve this indexing scenario, the event streams from all clients are fetched as before. When a new block is received from any client, it is just dumped into a central cache that keeps track of all recent blocks from all nodes.
The cache is organized by block root and slot number. When the same block is received from multiple clients it gets stored once only and appropriate block header/bodies are loaded only once too (basically from the first node that sees them).

In addition to the block events, the indexer also subscribes to finalized_checkpoint events.
The indexer keeps track of that checkpoint globally. Whenever one of the clients receives a higher checkpoint, the indexer logic is triggered.

With the checkpoint, the indexer can now reliable determinate the canonical chain by iterating through the cached blocks.
It starts with the block referenced in the checkpoint and iterates back via the parent root property of each block.
The indexer logic is applied on all blocks on the way (these are all canonical blocks).

When finished, all remaining cached blocks with slot < checkpoint_slot are orphaned blocks and are now indexed as orphaned blocks as well.

This approach can lead to a high memory consumption during long non-finality time. I'm mitigating that by dumping cached block bodies into a separate database after some time (when >5 epochs are unfinalized). I have to store them somehow, because orphaned blocks are removed from CL nodes after finalization, so I can't fetch them anymore afterwards.

To show "live data" in my explorer, the unfinalized blocks are directly fetched from the indexer cache. That obviously makes these data views a lot more complex (fetching data from cache & db and combining results).

I've been using the first strategy and switched over to the second more complex strategy a week ago.
It looks like it's working quite well, but I haven't been able to see how it behaves in a real chain split scenario with long un-finality yet (devnet-8 is working too well :D)

TODO list for achieving first indexing strategy:
Indexer

[ ] Add logic to check if current fetched block is a reorg or not (we can do that by keeping the previous indexed block and check if the block parent root hash of it and the current fetched one matches).

API

[ ] Add new boolean param to index endpoint body that indicates if the current block is a re-org or not. If it is then we execute the correspondent logic which is moving all the transactions of the blocks between the re-org one and the latest one to the transaction_forks table.

DB

[ ] Create a new Prisma model called TransactionFork which will have the following fields: hash (fk), index and blockHash (fk), insertedAt and updatedAt.
[ ] Make block number field in block model not unique.


Check dependencies for Linux in bin/configure

This PR ensures we have the proper dependencies installed when running bin/configure on Linux. It's not as simple as running check_package like we do with MacOS, but grabbing the system packages with dpkg lets us know if the package is installed or not as long as we know the proper name for it.
I didn't bother too much with node because #786 is open, but we can figure out the details if we get a merge conflict later on.

@gazayas I just merged #786 and, as you predicted, there are merge conflicts on this one now.

@jagthedrummer Done!
This is what it looks like on Linux by the way. Looks like I need to update PostgreSQL :sweat_smile:


update attributes categorization in Excel export

The method used to categorize phenotypes into PATO attributes for the Excel export needs to be updated. This is because PATO now allows multiple is_a parents, and such terms get categorized as 'continuant' now. (from discussion with Jim today).

this has been fixed


”Sâncraiu de Mureș”, ”Nazna” are listed in the drop-down menu

Description:
When user writes ”Sâncraiu de Mureș”, ”Nazna” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Sâncraiu de Mureș"

Expected results
The location appears in the drop-down menu as "Sat Sâncraiu de Mureș, MUREȘ (Sâncraiu de Mureș)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Nazna"

Expected results
The location appears in the drop-down menu as "Sat Nazna, MUREȘ (Sâncraiu de Mureș)".


In Deckbuilding, please treat multicoloured cards as their left-side colour instead.

In deckbuilding, please make multicoloured cards be treated primarily as their colour on the left rather than a 7th colour category of multicolour.

Completed!


gsd-parser should return errors instead of panicking on unexpected input

Right now, the gsd-parser fails violently (=panics) whenever invalid input is received.  Instead, it should gracefully return errors to the calling code, to be processed by the application.

Related commits:

1d88a9efbd76 ("gsd-parser: Propagate number parsing errors")
41fa79fe4ec6 ("gsd-parser: Remove a few more unwrap() in number parsing")
cd32a599d0dd ("gsd-parser: Don't panic on unknown PrmText")


SP5 : why not SignalXY can use changing list,like scatter?

Suggestion: (Describe your idea here)
ScottPlot.Plot myPlot = new();
/* a code sample may improve communication */
myPlot.SavePng("bug.png");

The demo app has two interactive SignalXY examples that should help provide the information needed to achieve this.
Also the draggable scatter line demo is useful to refer to: https://scottplot.net/demo/5.0/#draggable-data-points


Apply YARN-2065

https://issues.apache.org/jira/browse/YARN-2065

Can one of the admins verify this patch?


Handle docker restart

Description
Changes proposed in this pull request.
Test plan
Outline the test plan used to test this change before merging it.

Fixes #.

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "ab297930df33779893b6c060a256eba5a8d6fcbf"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "70225a007afaf6b754ad4b55400181fd0e0ef272"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "d63b210c3414f55b3ba4ea9e872ca7cd7ab9eed5"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "0022404bd073d2e62b7f4a7495c54d882962acb6"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "a06a3bbf10ff8b89b8fdfd98bf88829a8e6ea4e2"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "a06a3bbf10ff8b89b8fdfd98bf88829a8e6ea4e2"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "7519c68e55d27763c14a937ce9a7a474cdf4738f"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "0022404bd073d2e62b7f4a7495c54d882962acb6"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "592823304fc2e6082199db5162f2237a3442038f"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "f4e3e03b361f0615010783201f7e07c15efb5589"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "aec418776853c0dd04def2a2d434409d3d11bd9f"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "c6768d358c6b9ee111d065bc4c28c7c7e1a79f4a"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "5ca8665fd61d7cb49ce92a7fca78b513602529e6"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "6e64f48d70c12a34ad6e29bdb00a8587a0afcbee"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "5ca8665fd61d7cb49ce92a7fca78b513602529e6"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "6e64f48d70c12a34ad6e29bdb00a8587a0afcbee"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "c388cb8b239bedc6dcd9d005b32d317ba0bbbbb8"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "6e64f48d70c12a34ad6e29bdb00a8587a0afcbee"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "2b725a774dcff67785136d30100de2950dc3ea9c"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "3630c77596e2f04abad3d2ee566cbcde3b01932c"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "4c526fd74f203f518b7b0642d56eea234fee996b"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "3630c77596e2f04abad3d2ee566cbcde3b01932c"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "4c526fd74f203f518b7b0642d56eea234fee996b"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1241",
    "commit-sha": "e18f7d774cc9d731d80ec20fabacabdaf9344607"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "833",
    "commit-sha": "5fba15c7ba2521ee5e379fabb23e4e83922da0f3"
  }
]


Some basic items do not seem to work

Discussed in https://github.com/calibx/msfsdeck/discussions/203

Originally posted by smoothchat December 15, 2022
Thanks for making this excellent plugin available.
Just a couple of observations with v2.3.0.
Aircraft = C172 Classic
Parking Brakes - the indicator works (when toggled via the sim), however pressing the button appears to do nothing.
Pedestral Light - doesn’t appear to work.
CabinLight - doesn’t appear to work either. I think these require a “SET” event rather than a value change.
Instrument Lights - works, but you need to set Light_Potentiometer_3 to 100 otherwise, if the lights are turned down, they don’t illuminate on the button press

Hi,
The problem with lightd doesn't come from the plugin but it rely on the aircraft implementation.
For example the 3 lights works well with the 747 but not the C172.
I will fix the parking brakes as it seems that the old event doesn't work anymore


Alluded crabb/eda

please pull this into the master thanks!

this didn't work

please pull this into master for updated README


Fix attempt to #constantize a symbolic name

Related with #146, 6c497b8.
I run into this problem when implementing a successive version of a resource.
I was using something like next in controller:
class V2::InvoiceController < V2::BaseController
  load_and_authorize_resource :invoice
end

Pretty similar to what docs suggests. But regardless of existing logic that try to compose namespaced resource. It fails due to passing a name of the resource as :invoice symbols. And rescuing with a not namespaced resource.
def namespaced_name
  [namespace, name.camelize].flatten.map(&:camelize).join('::').singularize.constantize
rescue NameError
  name
end

So instead of V2::Invoice it returns an Invoice.
This PR is about fixing that problem and get rid of rescue from almost base error class.

@Senjai would you like to share any thought about it? Can I be somehow helpful to process merge of this patch?
From my point of view, currently cancancan allows us to pass @name as a symbol value. And then trying to invoke ActiveSupport::Inflector#camelize on it. That surely fails because AS doesn't extend Symbol class. Yes, we have a rescue there but it default some logic. And generally afaik it's a bad practice to use rescue in such kind of places.
I have some concerns about using safe_constantize because it's availble only for rails >= 3.2.1. And you may want to support versions under it as well but I dunno.

@bambycha Thank you, I apologize for the delay in getting to this.


undo the breaking change introduced in 0.7.6

I should probably yank 0.7.6, too
cc @alexcrichton this should unbreak your setup, sorry about that.

Coverage remained the same at 69.051% when pulling 96cd910c92fc8102777902504a2cd0292dbfe417 on oli-obk:undo into e0bd57d63cc130f2b604ba55930932f61ae8d100 on serde-rs:master.

@homu r+

:pushpin: Commit 96cd910 has been approved by oli-obk

:zap: Test exempted - status

Oh awesome, thanks!
On Wednesday, June 1, 2016, Homu<EMAIL_ADDRESS>wrote:

⚡ Test exempted - status
https://travis-ci.org/serde-rs/serde/builds/134394869
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/serde-rs/serde/pull/349#issuecomment-222960496, or mute
the thread
https://github.com/notifications/unsubscribe/AAD95KCQgRcphEttm376-6PfjSy34q3hks5qHWangaJpZM4IrVhV
.


Lights up on sites not using svelte

Is it possible to have the badge grayscale on sites that aren't using svelte, and red when a site is using it (even in production mode -- similar to vue and react's devtools)?  It'd be a nice addition to be able to see what sites are actually using svelte

svelte-devtools doesn't watch any pages until you open it. This means it can't know if the page uses svelte beforehand. In other words, this is something that could be done but would have performance issues.


GC Sweep: Delete unreferenced content

Today, unreferenced content (data stores) are marked as such in the summary sent to server. These unreferenced data stores need to be deleted from the summary eventually. For example, after a month of content being unreferenced, they can be deleted.

Duplicate of https://github.com/microsoft/FluidFramework/issues/6330


add data file readme

Adding a file to add notes about test files
Contents so far only include a first pass at why rgba_geotiff.tiff is unique

@banesullivan You can go ahead and merge this.  We can always make modifications later.


restart too slow and too huge memory footprint

Environment

CentOS7.1 Linux Kernel 3.10.0-862.el7.x86_64
pilosa v1.1
single instance
384GB memory
pcie ssd 3.0TB
key index
519,870,337 columns
about 50,000 rows
.key file(translation map file) size about  100GB
memory usage: RES 190.4GB and SHR 99.4GB

Suffering

restart that pilosa taking 2 hours, I found only one thread load data.
too many memory footprint, about

Is there any way to improve start speed and reduce memory footprint?

related #605

I don't think we've done much testing with a key translation file that large, so that could be a factor

@zhyhang how large are your pilosa data files? (not the key translation file)
I would also like to see the golang heap profile at the end of the two hours. you can obtain this by curl pilosa:10101/debug/pprof/heap > startup.prof. If you could send that file it would be very helpful. thank you!

heap dump, please see the attachment
startup.tar.gz
following is start log snippet:
2019/01/01 16:33:35 open server
2019/01/01 18:35:42 WARNING: Tried to set open file limit to 262144, but it is 65535. You may consider running "sudo ulimit -n 262144" before starting Pilosa to avoid "too many open files" error. See https://www.pilosa.com/docs/latest/administration/#open-file-limits for more information.
2019/01/01 18:35:42 open holder path: /ssd/cache/pilosa/data
2019/01/01 18:35:42 opening index: adc
2019/01/01 18:35:42 opening index: wx
2019/01/01 18:35:42 opening index: mac
2019/01/01 18:35:42 opening index: pyc
2019/01/01 18:35:54 opening index: did
2019/01/01 18:35:59 opening index: ph
2019/01/01 18:35:59 opening index: mb
2019/01/01 18:35:59 opening index: wb
2019/01/01 18:35:59 open holder: complete
2019/01/01 18:35:59 received state READY (ae2da9e0-6c28-4b65-bcb5-a59415009b1a)
2019/01/01 18:35:59 change cluster state from STARTING to NORMAL on ae2da9e0-6c28-4b65-bcb5-a59415009b1a
2019/01/01 18:35:59 listening as http://<IP_ADDRESS>:11101
2019/01/01 18:35:59 holder sync monitor initializing (10m0s interval)
2019/01/01 18:35:59 Pilosa is currently configured to send small diagnostics reports to our team every 1h0m0s. More information here: https://www.pilosa.com/docs/latest/administration/#diagnostics

based on the timing of those log messages, it would appear that the long load time is occurring during the opening of the translate file. The memory profile with most memory being allocated by TranslateFile.applyEntry.
Will have to dig a bit more to determine what this means exactly and what we can do about it.

@jaffee Thanks!

@jaffee I would like divide the big instance to some smaller instances. Is It can reduce the total memory usage which occupied by .key file and bitmap data?

@zhyhang it will help with the bitmap data, but the translation file will be replicated to every node. Translation is something we hope to make more scalable in the future.
I'm fairly confident that we can improve the startup time that you are seeing significantly, but will have to spend some more time with it.

@jaffee I believe that!

@jaffee The translation file is a linear log so it's not easy to parallelize. Splitting it so it's per-index would help (see https://github.com/pilosa/pilosa/issues/1976) since they could load independently.
However, a separate issue is that we are storing a reverse lookup from id-to-offset. It's a map of uint64-to-uint64 so with 520M columns times 16 bytes that's 8GB and that doesn't factor in the overhead of the map. We may want to persist that to disk. We also maintain a list of elements which adds substantial memory overhead.
We may want to persist the whole index to disk using Badger or Bolt. We will definitely take a read & write performance hit compared to the RHH implementation we have now but it would scale up much further.

Moving this to in-progress since a rewrite of the translate store is underway in #2042

this was addressed by #2042


Merge https://github.com/openanthem/nimbus-core/issues/566 into 1.3.1.M4

Issue Details
Type of Issue  (check one with "X")
[X ] Bug Report => Please search GitHub for a similar issue or PR before submitting
[ ] Feature Request => Please ensure feature is not already in progress
[ ] Support Request => Please do not submit support requests here, instead see: https://discourse.oss.antheminc.com/

Current Behavior
Merged https://github.com/openanthem/nimbus-core/issues/566 into 1.3.2.M1.
Expected Behavior
Please get https://github.com/openanthem/nimbus-core/issues/566 merged into 1.3.1.M4
How to Reproduce the Issue
Steps to Reproduce

Code Snippet

Environment Details

Nimbus Version:
1.3.1.M2

Browser:
Google Chrome

1.3.1.M4 was released. I would suggest that we put this into either 1.3.1.M5 or 1.3.1, as 1.3.2.M1 has already been released. (This change is in 1.3.2.M1)

1.3.1.M5 should work.We see some issues in 1.3.2.M1 which are not in 1.3.1.M2 so we wanted this to be merged into a patch version.

This change was pushed into 1.3.1.M5.


gitGraph cut off

I know gitGraph is experimental. Yet still I wonder why it does not work.
If you open the image in a new tab, it works:

It from somewhere thinks it must be 300px.
I use it with  docusaurus.io.
Also, how could I pass mermaidCli options?
This does not seem to work:
        docs: {
          sidebarPath: require.resolve('./sidebars.js'),
          // Please change this to your repo.
          editUrl:
            'https://github.tools.sap/xeeti/docs/edit/main/',
          remarkPlugins: [
            [remarkMermaid, {gitGraphConfig: {width: '100%'}}],
            simplePlantUML
          ],
        },

Thank you 🤝

Hi, sorry for fixing this quite late!
Unfortunately, setting gitGraphConfig wouldn't work for me. In my testing, it looks like if an SVG has width 100%, your browser will just always default to width 300px when including the SVG.
Because of this, since v1.1.0, remark-mermaid-dataurl, now uses svgdom to find the width of an SVG in pixels, then sets the width to that. It seems to work now! See below:


Support Store Container

With the new Filepicker pricing changes, if you use image conversion, it's important to be able to use one API key for multiple environments. Ink has suggested that the way to do this is provide different containers and provides the data-fp-store-container option:
"The bucket or container in the specified file store where the file should end up. This is especially useful if you have different containers for testing and production and you want to use them both on the same filepicker app. If this parameter is omitted, the file is stored in the default container specified in your developer portal."
This can be added just with data: {fp_store_container: container-name}, but it would be nice to be supported directly within the field, or, better, as a global setting.

Along with this feature, the default pick/store policy should specify the storage bucket (rather than allow storage to any bucket).


Wrong variable in docker-entrypoint.sh

Hi there!
It looks like WAYID2NODEIDS_MAPPING_FILE_COMPRESSED is wrong variable here. It should be ${WAYID2NODEIDS_MAPPING_FILE}${SNAPPY_SUFFIX}
https://github.com/Telenav/osrm-backend/blob/ad0d667eb08286f85b4a0be3716105a2a1afdc17/docker-orchestration/osrm-backend/docker-entrypoint.sh#L32

Yes, you're right! It seems that we forgot to change it during refactor. It should be ${WAYID2NODEIDS_MAPPING_FILE}${SNAPPY_SUFFIX}.


Feature/labelposition

From #299, added the ability to specify the positioning of a label relative to its node. Possible positions are left, right, top, bottom, and center. To specify a position, assign the prop labelPosition with one of those strings.
For example
const graph = {
    nodes: [
        {
            id: "node 1",
            size: 300,
            labelPosition: "top",  //places the label above the node
        },
        {
            id: "node 2",
            size: 300,
            labelPosition: "left",  //places the label to the left of the node
        },
        ...
    ],
    links: [...]
};

Alternatively you can globally set the position within the config object
const myConfig = {
    ...
    node: {
        ....
        labelPosition: "bottom",  //places all labels below nodes
    },
};

The one thing I wasn't sure about was what to set for the default value. My version of placing the label to the right of the node is slightly different than the current label placement due to using dominant-baseline=middle and dy="0" instead of the current version which just specifies dy=".35em". So I have the default as labelPlacement=null which then falls back onto the original placement process for the labels. Though I think it might make sense to just have the default be labelPosition="right"
Please let me know what you all think about this. I think this is definitely a useful feature to include, and was definitely critical for my specific use case

Sorry about the conflicts on src/components/graph/graph.config.js is just some documentation that I updated there. Should not be much troublesome

Ok, I think I got everything updated correctly. @danielcaldas please let me know if anything else needs to change.

Hey @danielcaldas what's the status on getting this merged in?


Pipeline triggered twice after empty file dropped

Pipeline triggered twice after empty _SUCCESS file is generated
I believe this topic has been discussed already, however I don't believe an actual resolution has been created.
The problem occurs in Azure Data Factory when creating a storage event trigger. The trigger files on the Blob Created event and DOES NOT ignore empty files. The _SUCCESS file is empty and gets generated by a number of tools when a process is completed, including Azure Data Factory data flows.
When the trigger is started a new subscription is created in Azure Event Grid for the Blob Created event filtered by the chosen Begins With and Ends With file paths. When digging a bit deeper you can see the events that are firing when a file is dropped, which include the CreateFile and FlushWithClose events.
In past articles I have seen the solution is to remove one of the two events from the Advanced Filters in the Event Grid. This does appear to resolve the issue. However, when dealing with many triggers it does create a manual step to update all the events in your target environment, something I wouldn't expect a developer to have to do.
Introducing CI/CD
Now if you have multiple data factories and are using a CI/CD pipeline as presented by Microsoft Continuous integration and delivery in Azure Data Factory you'll have a PowerShell script to move everything from one environment to the next.
In this script is a step to stop all triggers, and if those triggers happen to be storage event triggers the subscription is deleted. All of the objects are then moved and triggers are then started again, an in the case of storage event triggers the subscription is re-created. When the trigger is re-created the original bug is reintroduced into the system forcing the developer to manually touch every event subscription every time a deployment is executed. Manual interaction is the activity you want to avoid and one of the primary purposes of a CI/CD pipeline!
I believe Microsoft needs to update the way subscriptions in the Event Grid are generated by Azure Data Factory so when empty files are not ignored only the FlushAndClose advanced filter is present and the CreateFile filter has been removed.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 237d79bb-0601-dc47-b6c4-e3f1edc1a25f
Version Independent ID: b73cce3a-18ef-fd98-f6e7-8c508f6adc13
Content: Continuous integration and delivery - Azure Data Factory
Content Source: articles/data-factory/continuous-integration-delivery.md
Service: data-factory
Sub-service: ci-cd
GitHub Login: @nabhishek
Microsoft Alias: abnarain

@PaulKlotka
Thanks for your feedback! We will investigate and update as appropriate.

@PaulKlotka
Thank you for bringing this to our attention.
I've delegated this to content author @nabhishek, who will review it and offer their insightful opinions.

@nabhishek
Could you please review add comments on this, update as appropriate.

Thanks @PaulKlotka. Can you open a ticket with our support team so they can help investigate this further? You can open a ticket directly from the Azure portal using the main menu at the top left to choose Help + Support. I will close this issue out for now but we can continue the discussion in this thread as necessary, even after the issue is closed.
#please-close


Deflect power working; though, not fully

Bug Report
Deflect power is working, as in, it blocks the incoming projectiles: Though, it doesn't deflect back.
Describe the Bug
When trying to deflect incoming projectiles, and hold right click, the projectile is blocked, but it won't fire back.
To Reproduce
Steps to reproduce the behavior:

Create a RPGItem with the deflect power.
Summon a default skeleton.
Enter gamemode survival with the RPGItem
Enter combat with the skeleton and try deflecting the arrows.
If the arrow hits you and you're deflecting, you'll hear the sound, and you won't receive damage.
Though, it doesn't fire back.

Expected Behavior
When deflecting projectiles the projectiles should be fired back/bounced back and inflict damage.
Stacktrace or log
No logs.
Environment

Java version: 8
Server software version: 1.13.2
RPGItems version: v3.6.560-mc1.13.2

Additional Context
Thanks for the fast fix for the previous bug report!

Not reproducible but noticed a thing may help.
https://github.com/NyaaCat/RPGItems-reloaded/releases/tag/v3.6.563-mc1.13.2

Current implementation of deflect is cancelling the damage event and set the shooter of projectile to player, wait the projectile to drop naturally some tick, then set the direction and velocity based on player's facing. Maybe the delay is too long.


Using Algolia with Twitter Typeahead 0.11.1

I want to use the newest version because of the new custom events it offers. When trying to use the new version, the results no longer show. I'm still seeing queries being made however.

Indeed, it seems they changed the way their callback is working. Here is the new code of Bloodhound's ttAdapter: https://github.com/twitter/typeahead.js/blob/master/dist/bloodhound.js#L825-L834
We can probably handle the backward compatibility based on the 2nd parameter (now a sync boolean and before a cb function).


Add rest-server

https://github.com/restic/rest-server
https://github.com/restic/rest-server/blob/master/examples/compose-with-grafana/docker-compose.yml

Examples
$ restic -r rest:https://host:8000/ init
$ restic -r rest:https://user:pass@host:8000/ init
$ restic -r rest:https://user:pass@host:8000/my_backup_repo/ init


param.axes check : redundant condition

Description
(Brief description on what this PR is about)
Logical condition optimization: !A || (A && B)' is equivalent to '!A || B
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-bot run ci [centos-cpu, unix-gpu, windows-cpu, windows-gpu]

@mxnet-bot run ci [unix-gpu]

@mxnet-bot run ci [unix-gpu]


[FEATURE] Prefix Mac Address

Is that possible that we can prefix the VM mac address in the harvester?
for example first 3 bytes?

hi @hghew,
Could you describe your scenario in more detail?
I check the kubevirt document, looks like kubevirt should support the custom mac address.
But we needed to dig more for it. Cc @yaocw2020 , what do you think?

connect with: https://github.com/harvester/harvester/issues/3682
If we support setting MAC address in creating VM, it will be wonderful.


Crash when loading .qml files in release-build

seems like the text-formatter caused the crash. Text formatting is now bypassed.


"dimaround" window rule perpetually dims windows with each new instance of target application

Hyprland Version
Hyprland, built from branch main at commit 1a6f961de2eff84e4725255f09d33395c4a52fcc dirty (hyprctl: Make device configs queryable (3226)). Tag: v0.29.1-35-g1a6f961d  flags: (if any)
Bug or Regression?
Bug
Description
Using the windowrule = dimaround,WINDOW will dim all other applications around WINDOW, as expected. However, spawning more than one instance of WINDOW causes the dimming boxes on other applications to compound. It causes the dimming on other applications to become darker with each new instance of WINDOW that is created.
The bug is present on both windowrule & windowrulev2.
Platform: Arch Linux x86_64

How to reproduce

Create a dimaround window rule for any application in your hyprland.conf configuration file.
Open more than one instance of the dimaround target application.

Crash reports, logs, images, videos
No response

this aint a bug tho

It seems like unexpected behavior, though. If it is indeed intended behavior, would you suggest classifying it as a feature-request to have windows only dim once?

it now is a feature request


Can I add a list item to a Contacts list with Add-PnPListItem?

I tried in several ways already. I do not get any error message. However, it does not add the item.
Add-PnPListItem -List "ListName" -Values @{
"FirstName" = $FirstName;
"Title"=$LastName;
"OrganizationalIDNumber"=$OrganizationalIDNumber;
"Email"=$Email;
"Company"=$Company;
"WorkCountry"=$WorkCountry;
"UserField1"=$UserField1;
"UserField2"=$UserField2;
"UserField3"=$UserField3;
"UserField4"=$UserField4
}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b8c4c313-d931-b106-36e7-ae44cfb2e238
Version Independent ID: a1969a78-7325-8946-c27f-8320b7bbed75
Content: Add-PnPListItem (sharepoint-pnp)
Content Source: sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPListItem.md
GitHub Login: @techwriter40
Microsoft Alias: kirks

@Markus-Hanisch Thank you for your feedback
We want to make sure your PnP issue is handled appropriately.
We have a separate repo for the PnP PowerShell issues. We want your issue to get the proper attention it deserves.
Please open your issue in this repo: https://github.com/SharePoint/PnP-PowerShell
I am going to close this issue so that we can track to correct one in the PnP PowerShell repo.


Proto server reflection

This PR depends on #6373. It contains debug files (test/cpp/util/reflection_debug) that should not be merged.

ProtoReflectionDescriptorDatabase is not thread-safe for now.

Debug files have been removed.

I think I am done with the first pass. Thanks.

Thanks a lot for the review!

Sanity is green in 9592. C/C++ are green in 9636.

LGTM


errno 7

npm ERR! code ELIFECYCLE
npm ERR! errno 7
npm ERR<EMAIL_ADDRESS>install: prebuild-install || node-gyp rebuild
npm ERR! Exit status 7
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Please provide the command that was typed and the FULL error log.
The current release is v4.0.6  https://www.npmjs.com/package/bufferutil

I'm getting this for npm install.

these are errors I'm facing

Please look thru your error log for the string gyp info using node-gyp@ and if the version number is less than the current release of node-gyp then please upgrade using the instructions at https://github.com/nodejs/node-gyp/blob/master/docs/Updating-npm-bundled-node-gyp.md and try your command again.

I was getting the same error as Priyanshi. After upgrading node-gyp to 9.1.0 Now I'm getting this error.

@DylanL826 Please upgrade bufferutil as mentioned above. https://github.com/nodejs/node-gyp/issues/2694#issuecomment-1175180929
Also, upgrade Node.js to a supported version.  https://nodejs.org/en/about/releases