Exporting the settings

Is your feature request related to a problem? Please describe.
Currently, there's no way to transfer ChatGPTBox settings between different browsers or devices. This can be frustrating when setting up the extension on a new browser or when trying to maintain consistent settings across multiple devices.
Describe the solution you'd like
I propose adding an export/import feature for ChatGPTBox settings. This would allow users to:

Export their current settings to a file (e.g., JSON format)
Import these settings on another browser or device

This feature would greatly improve user experience by:

Saving time when setting up the extension on new devices
Ensuring consistency of settings across multiple browsers/devices
Providing an easy way to backup and restore configurations

Additional context
This feature is common in many browser extensions and would align ChatGPTBox with user expectations for customizable tools. It would be particularly useful for users who frequently switch between work and personal devices, or for organizations deploying the extension across multiple workstations.

First of all, thank you for your effort to develop the feature to transfer ChatGPTBox settings between different browsers or devices.
This feature has now been implemented! I recently tested the new export/import functionality, and I’m happy to report that it works seamlessly. Now, transferring settings between browsers or devices is a breeze. (Test between ArcBrowser to Vivaldi, Vivaldi to Firefox Nigtly on MacOS)
Best regards


May I ask if it's possible to apply for a CVE for this project if a security vulnerability is found?

Description

Yes of course, what is involved to apply for CVE?

GitHub can assign us one if we have a disclosure we need to file


feature: add support for OpenID Connect

I'm using this module for auth since at this time there seems to be no alternative.  (Thanks for leading the way!)
However, I ultimately need to support Google Auth to provide a real Single-SignOn experience for folks at my company.
I was just checking out caddy-auth-SAML - I wanted to see if that could support Google Auth?  One thread there
mentioned you may bring that functionality into this module.
Can I ask if supporting Google Auth is on your Roadmap?  If not, (or if not anytime soon) maybe you have some ideas on how I might get Google Auth to work in some way?

However, I ultimately need to support Google Auth to provide a real Single-SignOn experience for folks at my company.

@rayjlinden , what do you call SSO? OpenID Connect? something else? Screenshots of existing authentication flows would help. Is your company open to support my development with $$$? If so, please ping me in LinkedIn.

We have tied Google Auth into a bunch of things.  OpenID Connect is how we
do it on our nginx proxies we have in front of a couple of different
systems.  I know we have also used SAML in a couple of other integrations.
Here is a snippet from our nginx config that does this.  It relies on a
open-resty plugin:
(https://github.com/zmartzone/lua-resty-openidc)

location / {
set $session_name remoteproxy_session;
set $session_storage redis;
set $session_redis_host {{REDIS_HOST}};
set $session_redis_port {{REDIS_PORT}};
set $session_secret {{SESSION_SECRET}};
set $session_check_ssi off;
access_by_lua '
local opts = {
-- the full redirect URI must be protected by this script and becomes:
-- ngx.var.scheme.."://"..ngx.var.http_host..opts.redirect_uri_path
-- unless the scheme is overridden using opts.redirect_uri_scheme or an
X-Forwarded-Proto header in the incoming request
redirect_uri_path = "/redirect-uri",
discovery = "https://accounts.google.com/.well-known/openid-configuration",
client_id = "{{CLIENT_ID}}",
client_secret = "{{CLIENT_SECRET}}",
{{#MULTI_DOMAIN}}
authorization_params = { hd="*" },
{{/MULTI_DOMAIN}}
{{#LL_DOMAIN}}
authorization_params = { hd="lindenlab.com" },
{{/LL_DOMAIN}}
scope = "openid email profile",
iat_slack = 3600,
redirect_uri_scheme = "https",
--logout_path = "/logout",
token_endpoint_auth_method = "client_secret_post",
--ssl_verify = "no"
}
-- call authenticate for OpenID Connect user authentication
local res, err = require("resty.openidc").authenticate(opts)
if err then
ngx.status = 500
ngx.say(err)
ngx.exit(ngx.HTTP_INTERNAL_SERVER_ERROR)
end
-- at this point res is a Lua table with 3 keys:
-- id_token : a Lua table with the claims from the id_token (required)
-- access_token: the access token (optional)
-- user : a Lua table with the claims returned from the user info endpoint
(optional)
{{#MULTI_DOMAIN}}
if res.id_token.hd ~= "lindenlab.com" and res.id_token.hd ~= "
linden-external.com" then
ngx.exit(ngx.HTTP_FORBIDDEN)
end
{{/MULTI_DOMAIN}}
{{#LL_DOMAIN}}
if res.id_token.hd ~= "lindenlab.com" then
ngx.exit(ngx.HTTP_FORBIDDEN)
end
{{/LL_DOMAIN}}
-- set headers with user info (overwriting any existing!)
ngx.req.set_header("X-USER", res.id_token.sub)
ngx.req.set_header("X-LLRP-USER-EMAIL", res.id_token.email)
{{#ADD_GRAF_HEADER}}
-- set header for Grafana auth
ngx.req.set_header("OIDC_CLAIM_email", res.id_token.email)
{{/ADD_GRAF_HEADER}}
{{#ADD_VVM_HEADER}}
-- set header for VVM auth
ngx.req.set_header("OIDC_CLAIM_email", res.id_token.email)
{{/ADD_VVM_HEADER}}
ngx.var.oidc_email = res.id_token.email
';
proxy_set_header Host $host;
set $proxy_upstream "{{BACKEND_URL}}";
proxy_pass $proxy_upstream;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

On Tue, Sep 22, 2020 at 8:26 AM Paul Greenberg<EMAIL_ADDRESS>wrote:

However, I ultimately need to support Google Auth to provide a real
Single-SignOn experience for folks at my company.
@rayjlinden https://github.com/rayjlinden , what do you call SSO?
OpenID Connect? something else? Screenshots of existing authentication
flows would help. Is your company open to support my development with $$$?
If so, please ping me in LinkedIn.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/greenpau/caddy-auth-portal/issues/37#issuecomment-696795077,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKE5LWTTQYZ4UXIZAT7NI2TSHC63XANCNFSM4RV5FAYQ
.

I can't message you on linkedin because I don't have a Pro account.  You can reach me at<EMAIL_ADDRESS> I might be able to find so $$

location / {
set $session_name remoteproxy_session;
set $session_storage redis;
set $session_redis_host {{REDIS_HOST}};
set $session_redis_port {{REDIS_PORT}};
set $session_secret {{SESSION_SECRET}};
set $session_check_ssi off;
access_by_lua '
local opts = {
-- the full redirect URI must be protected by this script and becomes:
-- ngx.var.scheme.."://"..ngx.var.http_host..opts.redirect_uri_path
-- unless the scheme is overridden using opts.redirect_uri_scheme or an
X-Forwarded-Proto header in the incoming request
redirect_uri_path = "/redirect-uri",
discovery = "https://accounts.google.com/.well-known/openid-configuration",
client_id = "{{CLIENT_ID}}",
client_secret = "{{CLIENT_SECRET}}",
{{#MULTI_DOMAIN}}
authorization_params = { hd="*" },
{{/MULTI_DOMAIN}}
{{#LL_DOMAIN}}
authorization_params = { hd="lindenlab.com" },
{{/LL_DOMAIN}}
scope = "openid email profile",
iat_slack = 3600,
redirect_uri_scheme = "https",
--logout_path = "/logout",
token_endpoint_auth_method = "client_secret_post",
--ssl_verify = "no"
}
-- call authenticate for OpenID Connect user authentication
local res, err = require("resty.openidc").authenticate(opts)
if err then
ngx.status = 500
ngx.say(err)
ngx.exit(ngx.HTTP_INTERNAL_SERVER_ERROR)
end
-- at this point res is a Lua table with 3 keys:
-- id_token : a Lua table with the claims from the id_token (required)
-- access_token: the access token (optional)
-- user : a Lua table with the claims returned from the user info endpoint
(optional)
{{#MULTI_DOMAIN}}
if res.id_token.hd ~= "lindenlab.com" and res.id_token.hd ~= "
linden-external.com" then
ngx.exit(ngx.HTTP_FORBIDDEN)
end
{{/MULTI_DOMAIN}}
{{#LL_DOMAIN}}
if res.id_token.hd ~= "lindenlab.com" then
ngx.exit(ngx.HTTP_FORBIDDEN)
end
{{/LL_DOMAIN}}
-- set headers with user info (overwriting any existing!)
ngx.req.set_header("X-USER", res.id_token.sub)
ngx.req.set_header("X-LLRP-USER-EMAIL", res.id_token.email)
{{#ADD_GRAF_HEADER}}
-- set header for Grafana auth
ngx.req.set_header("OIDC_CLAIM_email", res.id_token.email)
{{/ADD_GRAF_HEADER}}
{{#ADD_VVM_HEADER}}
-- set header for VVM auth
ngx.req.set_header("OIDC_CLAIM_email", res.id_token.email)
{{/ADD_VVM_HEADER}}
ngx.var.oidc_email = res.id_token.email
';
proxy_set_header Host $host;
set $proxy_upstream "{{BACKEND_URL}}";
proxy_pass $proxy_upstream;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

@rayjlinden , you can now test this. Release: https://github.com/greenpau/caddy-auth-portal/releases/tag/v1.1.6
Here are the snippets from my Caddyfile:
        google_oauth2_backend {
          method oauth2
          realm google
          provider google
          client_id XXXXXXXXXXXXXXXXX.apps.googleusercontent.com
          client_secret YYYYYYYYYYYYYYYYYY
          scopes openid email profile
        }

...

  route /sso/oauth2/google* {
    jwt {
      auth_url /auth/oauth2/google
    }
    respond * "google oauth2 sso" 200
  }

If you want to modify the behavior, please open a separate issue.


x/net/http2: RST_STREAM ErrCode=CANCEL sent to a closed stream

What version of Go are you using (go version)?

$ go version
go version go1.15.2 linux/amd64

$ vegeta --version
Version: 12.8.3
Commit: d9b795aec8585a0fb435072f68d842d596c332de
Runtime: go1.14 linux/amd64
Date: 2020-03-25T11:03:54Z"

Does this issue reproduce with the latest release?
Yes!
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/martin/.cache/go-build"
GOENV="/home/martin/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/martin/golang-path/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/martin/golang-path"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build611792435=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I am load testing Apache Tomcat web server with Vegeta
Together with Tomcat's developers we have found that Golang sends RST_STREAM + CANCEL after reading the DATA frame of a response.
Initially I thought it is a problem in Vegeta (issue) but after some investigation I've
found https://github.com/golang/go/issues/27208 and its fix.
I've exported GODEBUG="http2debug=2" and re-run Vegeta. It doesn't fail always but just for some HTTP2 streams. The debug information for a problematic stream looks like:
/tmp/vegeta-debug.txt:410:2020/09/23 11:11:36 http2: Framer 0xc000360000: wrote HEADERS flags=END_STREAM|END_HEADERS stream=443 len=10
/tmp/vegeta-debug.txt:520:2020/09/23 11:11:36 http2: Framer 0xc000360000: read HEADERS flags=END_HEADERS stream=443 len=35
/tmp/vegeta-debug.txt:525:2020/09/23 11:11:36 http2: Transport received HEADERS flags=END_HEADERS stream=443 len=35
/tmp/vegeta-debug.txt:526:2020/09/23 11:11:36 http2: Framer 0xc000360000: read DATA flags=END_STREAM stream=443 len=12 data="Hello world!"
/tmp/vegeta-debug.txt:527:2020/09/23 11:11:36 http2: Transport received DATA flags=END_STREAM stream=443 len=12 data="Hello world!"
/tmp/vegeta-debug.txt:536:2020/09/23 11:11:36 http2: Framer 0xc000360000: wrote RST_STREAM stream=443 len=4 ErrCode=CANCEL

What did you expect to see?
I expect to see error message explaining what kind of problem there is with the DATA frame.
I do not expect Golang HTTP2 library to send more frames to a closed stream. The server sends DATA with END_STREAM then Golang http2 fails for some reason and tries to send new frames to the server
What did you see instead?
I see Golang trying to send new frames to a closed stream and errors in the server logs explaining that the client is trying to use a closed stream.
Steps to Reproduce
I guess the following steps won't be very friendly to a Golang developer (or any non-Java developer) but I wasn't able to find a way to make it smaller.
There is a lenghtly discussion at https://lists.apache.org/thread.html/r6f9ce1521346d5ced72c82a4b5d882a624514c9a7b308ad54f064ba1%40<users.tomcat.apache.org> where I explained that I have tried with other HTTP2 servers (Golang, Rust, Node.js and Netty) - there is no such issue with them!
So I guess Tomcat produces problematic DATA frames in some cases.
I'd be very grateful if someone helps me to find out what exactly causes Golang net library to decide to send the RST_STREAM + CANCEL frame, for example by adding more debug statements to http2debug=2.
Steps:

Download Tomcat from https://tomcat.apache.org/download-90.cgi
Unzip/Untar it
Edit /path/to/tomcat/conf/server.conf and remove the comments around this connector: https://github.com/apache/tomcat/blob/27c4109a7a686b71454205faab909e5e1f041b18/conf/server.xml#L102-L113
Generate self-signed certificate and update the paths for certificateKeyFile and certificateFile attributes. The certificateChainFile attribute could be removed.
Start Tomcat with: cd /path/to/tomcat/, ./bin/startup.sh
Check ./logs/catalina.out that there are no errors
Run Vegeta against Tomcat:

echo -e '{"method": "GET", "url": "https://localhost:8443/examples/index.html"}' | vegeta attack -format=json -http2 -rate=0 -max-workers=100 -insecure -duration=5s | vegeta encode > /tmp/http2.json; and vegeta report -type=json /tmp/http2.json | jq .

cc @fraenkel

/cc @tombergan

So I won't comment on the setup but its not exactly trivial and the above well, wasn't enough.
What I ended up seeing were 2 types of reasons for the RST_STREAM:

context cancelled
missing stream end when the response body was closed

@fraenkel Could I provide you more debug information that will help you say why the CANCEL is being send ?
Here
/tmp/vegeta-debug.txt:527:2020/09/23 11:11:36 http2: Transport received DATA flags=END_STREAM stream=443 len=12 data="Hello world!"

I see all required data: the stream id, the END_STREAM flag and the body/data. But for some reason Golang net::Transport marks it as insufficient/incorrect and sends back the RST_STREAM+CANCEL.

I told you why. I added debug to see why cancel was sent. I can give you the line numbers. Again, the client is cancelling the context or the response body is closed before we finishing reading the body.

Sorry, I am not so familiar with Golang net internals and I didn't (I still don't) understand whether the problem is in the client (Golang) or in the server (Tomcat).
Please just let me know if you want me to retest with a nightly build of Golang or to change something at the server side!

Could you cc the Vegeta folks on this, since their client is apparently the cause?

Actually I first created an issue at Vegeta but then I've found  https://github.com/golang/go/issues/27208 and decided this is a problem in the library.
@tsenart Ping!

@martin-g: It's possible your requests are timing out, since you're sending at max rate. There's a default timeout of 30s. Do you see the same thing when you set -timeout=0?

The default timeout is 30s but the load test runs for just 5s. I think this excludes this possibility. But I will test it anyway!

Confirmed! Same behavior with -timeout=0.

This same issue (RST_STREAM + CANCEL sent by HTTP2 client to server after reading the DATA frame of a response) was reported with regard to exchange between restic backup and rclone utility: https://github.com/rclone/rclone/issues/2598
The root cause in that case was that restic (client) read exactly the number of response bytes it requested but did not wait for stream EOF.  Not waiting for EOF after reading full response body never posed a problem with HTTP/1.1 but results in sporadic RST_STREAM issues with HTTP/2.
@fraenkel
Can this difference between HTTP/1.1 and HTTP/2 implementations be considered a BUG??
The issue was investigated here: https://github.com/ivandeex/rclone/tree/stream-reset/stream-reset#premature-stream-reset-between-restic-and-rclone
and can be reproduced by running a simple test https://github.com/ivandeex/rclone/blob/stream-reset/stream-reset/http2test.go
go run http2test.go http1 nodrain 10

runs successfully
go run http2test.go http2 nodrain 10

prints error messages
go run http2test.go http2 drain 10

is successful again.


Cannot resolve name devicePixelRatio

If I try to use devicePixelRatio without window. in front I get this error:

Cannot resolve name devicePixelRatio. [cannot-resolve-name]  infer

https://github.com/facebook/flow/blob/main/lib/dom.js#L4157
If anyone wants to, it should be a pretty simple fix to add it somewhere around here as
declare var devicePixelRatio: number;


Added Update for Mockito Library

Description:
Added Update for the Mockito library from version 3.4.4 to version 3.7.0 which was released on January 05, 2021. Also tested and verified on various scenarios while running the android application. Mockito mock objects library is for core API and implementation

Library update was addressed in #166 . Closing this PR as per comment in #151 .


[ARM] az bicep install: Support additional process architectures with Bicep CLI

Related command
az bicep
Description
Support additional process architectures with Bicep CLI. Closes #27333.
Testing Guide
az bicep install
History Notes

[ARM] az bicep install: Support additional process architectures with Bicep CLI

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

ARM

I didn't intend to add the "breaking change" title - must have copy+pasted that from another PR.

@shenglol Could you please help review this Bicep related PR?


[Bug]: show-secrets replaces shared DB URL

What happened?
cargo-shuttle resource list prints …project:********@db.shuttle.rs:5432/…
The password is correctly redacted.
cargo-shuttle resource list --show-secrets doesn't just show the password, it also yields another host, which makes it impossible to simply copy the URL:
…project:password@postgres:5432/…
Why is db.shuttle.rs replaced with postgres?
Version
0.31.0
Which operating system(s) are you seeing the problem on?
Linux
Which CPU architectures are you seeing the problem on?
x86_64
Relevant log output
$ cargo-shuttle resource list
postgres://user-project:********@db.shuttle.rs:5432/db-project

$ cargo-shuttle resource list --show-secrets
postgres://user-project:password@postgres:5432/db-project

Duplicate declaration

[X] I have searched the issues and there are none like this.

Thanks for the report! This was resolved in https://github.com/shuttle-hq/shuttle/pull/1368 and released in 0.32.0.


Add the total rb quantity to reviewed RB count.

Fixes #4505

@aaronschachter ahh, yis yis, good call. fixed!

:+1:


Need hook for when multiselect/dropdown/combobox opens

A while ago, I wrote this issue about the dropdown opening outside the viewport and it was closed as being out of scope:
https://github.com/carbon-design-system/carbon-components/issues/618
How about a callback when the dropdown opens so that we could scroll it into view ourselves?
Since everyone is going to have this issue, I think it makes more sense to put the functionality inside the component instead of individual teams having to do it, but we could live with a hook in the meantime.

Note when you manually scroll it into view, the dropdown closes and you need to re-open it.

@kglickman One quick question - Is onOpen() in <Dropdown> closed to what you are requesting for?

@asudoh Yes.  That seems like it would do the trick.


Rubocop fixes

This makes the :cop: be happy.
A lot of this is just:

rubocop -a (auto-fix)
rubocop --auto-gen (generate todo config)

But, the good part about this is that we can now run Rubocop on each Travis build, to ensure that new code follows the Rubocop rules as defined in .rubocop.yml

Great job!
We will items in .rubocop_todo.yml one by one in the future, right?

I was about to ask if we already have a decision on style because of the code climate complains.

In my opinion, if possible, we should fix each code climate complains for each PR.
Because code climate complains only for modified lines of PR.

In my opinion, if possible, we should fix each code climate complains for each PR.
Because code climate complains only for modified lines of PR.

The code climate may check only modified files. Not lines.

Thanks to you both!
@scepticulous

Great job! I was about to ask if we already have a decision on style because of the code climate complains. This really enables us to have a solid base.

Well, we don't really have a decision other than using the defaults as provided by Rubocop. I think most of these make sense, but there are cases where I typically deviate (you saw it mentioned in the PR in the .rubocop.yml change).
@junaruga

We will items in .rubocop_todo.yml one by one in the future, right?

Yes, that'd be the idea. If people have spare time and want to work on cleaning these issues up, they are very welcome to do so.
With this change in place, the Rubocop rules will run:

On Travis
On CodeClimate

That's of course a bit silly, but we can live with it for now. (It seems the codeclimate settings use a different version of Rubocop - if someone knows how to fix that, please do. OTOH, we could disable Rubocop on codeclimate since we already run it on Travis anyway.)


flutter sdk

when do you provide flutter sdk?

To use Flutter, you need to install the Flutter SDK, which includes the Flutter framework, Dart programming language, and various command-line tools for development. To get the latest information on Flutter SDK releases, it's recommended to check the official Flutter website or GitHub repository.


Reorder the pipelines in the bootstrap concourse

Concourse lists the pipelines in the side menu in the order they were
added. It also shows the first pipeline in the list when you visit the
root URL.  Given the first pipeline that's normally used is the
create-deployer one, it makes sense for this one to be first in the
list.

Deployed my vagrant machine and pipelines loaded as expected


Automatic copyright[Documentation Update]:

Is there an existing issue for this?

[X] I have searched the existing issues

Issue Description
The current copyright is manual and the year needs to change every year manually.
Suggested Change
I can make the copyright automatic which does not need to change every year manually, but will be changed automatically.
Rationale
This update is necessary to reduce human labor every year, and can be handled automatically by js.
Urgency
High
Record

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

@dishathakurata You can only complete the issue under any one program, which one do you want SSOC or GSSOC?

GSSoC

@dishathakurata Assigned you the issue, Best of Luck :)


Why taking a picture takes such a long time?

I recently came to realize that camera.takePhoto() takes a long time until we get the delegate call back.
I'm curious why it's taking a long time when camea continuously shows the latest texture.
all it might need is just to get that texture?
Is there a way to get a instant photo from camera? or.. is there something i'm missing?
Thank you in advance!

it was other issues... sorry guys! i will close it out.


Fixed issues with PK filter and implicit cast

Minor code improvements

Remove minNodeVersion from symbol Optimizer
minNodeVersion has been introduced with: #10076 to implement a logic that checked the minimum version of the nodes currently in a CrateDB cluster, and use it to skip applying any symbol optimization rules that were introduced after that minNodeVersion. Since this mechanism hasn't been actually used since it was introduced (CrateDB: 4.2.0), remove it, since it makes it difficult to call the symbol Optimizer from other parts of the code.

Fixed issues with PK filter and implicit cast
Given the following situation:
CREATE TABLE tbl(a string PRIMARY KEY);
INSERT INTO tbl(a) VALUES ('t');
REFRESH TABLE t;
SELECT * FROM tbl WHERE a = true;

Previously, when trying to filter on the PK column with equality
operator, but using a value of a different type (in this example
boolean), then no results where returned because the dockeys where
built incorrently. ExpressionAnalyzer creates an implicit cast on the
column a, to match the type of the value (see: #10076 which introduced
this concept). So the query of the WHERE clause becomes:
a::boolean = true

Because of that the value added to the dockeys is true, instead of t.
To resolve this, we need to call optimizeCasts() before extracting
the pkMatches with the use of EqualityExtractor, so that the cast is
moved to the value:
a = true::'string'

and the EqualityExtractor normalizes the value to t which then
is added to the list of dockeys.
Fixes: #15326

If we normalize the query with the optimizer - are then the unwrapReferenceFromCast calls still needed?

I've tried that, but it breaks the explicit cast situations, for example: https://github.com/crate/crate/blob/master/server/src/test/java/io/crate/analyze/where/EqualityExtractorTest.java#L336
as in those cases optimizeCasts() doesn't swap.


Removed System.IO.Pipelines from TcpTransportActor

Don't need them and it created some pausing / stuttering problems on the client when dealing with larger message sizes:
This PR
BenchmarkDotNet v0.13.12, Windows 11 (10.0.22631.3447/23H2/2023Update/SunValley3)
12th Gen Intel Core i7-1260P, 1 CPU, 16 logical and 12 physical cores
.NET SDK 8.0.101
  [Host]     : .NET 8.0.1 (<IP_ADDRESS>001), X64 RyuJIT AVX2
  Job-TLZLUR : .NET 8.0.1 (<IP_ADDRESS>001), X64 RyuJIT AVX2

InvocationCount=1  LaunchCount=10  RunStrategy=Monitoring
UnrollFactor=1  WarmupCount=10

Method
QoSLevel
PayloadSizeBytes
ProtocolVersion
Mean
Error
StdDev
Median
Req/sec

PublishAndReceiveMessages
AtMostOnce
10
V3_1_1
6.026 μs
0.1940 μs
0.5721 μs
5.939 μs
165,960.60

PublishAndReceiveMessages
AtLeastOnce
10
V3_1_1
33.725 μs
2.4049 μs
7.0910 μs
31.595 μs
29,651.75

PublishAndReceiveMessages
ExactlyOnce
10
V3_1_1
50.183 μs
1.5227 μs
4.4898 μs
49.550 μs
19,927.02

dev

BenchmarkDotNet v0.13.12, Windows 11 (10.0.22631.3447/23H2/2023Update/SunValley3)
12th Gen Intel Core i7-1260P, 1 CPU, 16 logical and 12 physical cores
.NET SDK 8.0.101
  [Host]     : .NET 8.0.1 (<IP_ADDRESS>001), X64 RyuJIT AVX2
  Job-NIUSFI : .NET 8.0.1 (<IP_ADDRESS>001), X64 RyuJIT AVX2

InvocationCount=1  LaunchCount=10  RunStrategy=Monitoring
UnrollFactor=1  WarmupCount=10

Method
QoSLevel
PayloadSizeBytes
ProtocolVersion
Mean
Error
StdDev
Median
Req/sec

PublishAndReceiveMessages
AtMostOnce
10
V3_1_1
6.268 μs
0.3773 μs
1.113 μs
6.055 μs
159,528.99

PublishAndReceiveMessages
AtLeastOnce
10
V3_1_1
32.415 μs
1.2695 μs
3.743 μs
31.313 μs
30,849.70

PublishAndReceiveMessages
ExactlyOnce
10
V3_1_1
50.991 μs
2.7430 μs
8.088 μs
49.193 μs
19,611.16

Didn't really affect QoS 1 and 2 much.

If it ain't broke, don't fix it. Going to keep our code as-is for now.


Doc: Add links to iteratee. Fix #2052

A proposal for #2052. Not sure it's the way to go, but just to get the ball rollin'

Here's a link if would help anyone review: https://rawgit.com/Florian-R/underscore/iteratee-doc/index.html

The code might look cleaner if you re-wrapped the paragraphs.

Thanks for your suggestion @captbaritone. The PR have been updated accordingly. Let me know if you want the commits to be squashed.

@akre54: want to rule here? Seems fine to me, but I don't handle any of the docs.

Looks cool to me. Do we need to shore up the difference between predicate and iteratee?

Added 45607a8 with some copy-editing for test purpose. This commit mainly remove predicate in favour of iteratee

Nice, looks like a better version of my proposed patch a while ago https://github.com/jashkenas/underscore/pull/1864

I'm fine with predicate. It tells me in just a word that its result is truthy or falsey. A predicate is a kind of iteratee just as an iteratee is a kind of callback.

Sorry @megawac, I missed #1864 when I opened this PR. This has been updated per your suggestion and @craigmichaelmartin 's one.
@jdalton Did you mean you'd prefer to totally drop 45607a8?

@Florian-R

Did you mean you'd prefer to totally drop 45607a8?

Yep. I don't mind links or notes, but I dig how descriptive predicate is.

Any progress on this? @Florian-R Are you blocked on anything?

Yap I was waiting for input from @megawac on the adjustments about the wording and somehow totally forgot this PR. If you've got some idea I'll be happy to move forward with this one.

@Florian-R Apologies for the continued delays.
How about we leave the descriptions of all the predicate functions alone and instead add to the end of each one:

predicate is transformed through iteratee to facilitate shorthand syntaxes.

@captbaritone I like it. There have been several change in the doc recently IIRC so I'll need to take a look at the changes to see if this PR is always 100% accurate. Not quite the time right now but I'll try to tackle this next week.

Coverage remained the same at 96.863% when pulling 16a26da3d070c5627771cb63e44b83716963879f on Florian-R:iteratee-doc into 5500925f9f6d4b30f02d24196364735532624ba9 on jashkenas:master.

Coverage remained the same at 96.863% when pulling 12072c82431a9f3eae3439c68ba462e182d0309b on Florian-R:iteratee-doc into 5500925f9f6d4b30f02d24196364735532624ba9 on jashkenas:master.

Coverage remained the same at 96.863% when pulling 900d7b2066080b1a8ca924f7db264f794ab17592 on Florian-R:iteratee-doc into 5500925f9f6d4b30f02d24196364735532624ba9 on jashkenas:master.

OK, I have removed  45607a8 (which changed wording from predicate to iteratee) and updated with the suggestion from @captbaritone
I have mixed feeling on this one, this is cleared but the wording seems very redundant.
@captbaritone thoughts?

Coverage remained the same at 96.763% when pulling e78f6609aa7bef473599f4e79c76e65a44bdf402 on Florian-R:iteratee-doc into c2e2eff828f73eaf4490353f83724c357acb7fdf on jashkenas:master.

Coverage remained the same at 96.763% when pulling bec53d3ba7768262286048ee6fd56db0e9fb76a9 on Florian-R:iteratee-doc into 314eb0389c741f813fb1c9513d6572196e7531e6 on jashkenas:master.

Coverage remained the same at 96.763% when pulling 489c050d8c586680763c4950b6a51275a1896fec on Florian-R:iteratee-doc into 314eb0389c741f813fb1c9513d6572196e7531e6 on jashkenas:master.

Coverage remained the same at 96.763% when pulling 489c050d8c586680763c4950b6a51275a1896fec on Florian-R:iteratee-doc into 314eb0389c741f813fb1c9513d6572196e7531e6 on jashkenas:master.

Coverage remained the same at 96.763% when pulling 089b93094a5f34277bf29790402a400516e22d15 on Florian-R:iteratee-doc into 314eb0389c741f813fb1c9513d6572196e7531e6 on jashkenas:master.

@captbaritone Finally took some time to force push some edit. I think this is in a good shape, but I've probably missed something.
I've removed some previous re-wrapping when lines weren't that much long. Hopefully it will help to review, and it could be addressed in another PR if needed.

Thanks for sticking with this one! This is a much needed improvement to our docs. If you think there are other places we could make improvements, please feel free to open pull requests.


Need to update auto-deploy config for new location

@mechanicjay did you get to this? If not, what's required? I'm happy to help out.

Sorry, turns out this was already done, I must have been looking at an old checkout or something.   Nothing to do here.


Successfully connected to the air conditioner, but there was a problem connecting to the TV

**Home Assistant version 2021.7.4
**SmartIR version 1.17.0
manifest.json
{
"domain": "smartir",
"name": "SmartIR",
"documentation": "https://github.com/smartHomeHub/SmartIR",
"dependencies": [],
"codeowners": ["@smartHomeHub"],
"requirements": ["aiofiles==0.6.0"],
"homeassistant": "0.115.0",
"version": "1.17.0",
"updater": {
"version": "1.17.0",
"releaseNotes": "-- Add play_media service",
"files": [
"init.py",
"climate.py",
"media_player.py",
"fan.py",
"controller.py",
"manifest.json",
"services.yaml"
]
}
}
SmartIR configuration

Add configuration here

configuration.yaml
smartir:
  check_updates : false

climate:
  - platform: smartir
    name: Air Conditioner(Bedroom)
    unique_id: bedroom_ac
    device_code: 1960
    controller_data: remote.broadlink_remote
    temperature_sensor: sensor.temp_bedroom
    humidity_sensor: sensor.humid_bedroom
    power_sensor: binary_sensor.ac_power

media_player:
  - platform: smartir
    name: Bedroom Box
    unique_id: living_room_box
    device_code: 1380
    controller_data: remote.broadlink_remote
    power_sensor: binary_sensor.tv_power

1380.json
{
    "manufacturer": "Unknown",
    "supportedModels": [
      "Unknown"
    ],
    "supportedController": "Broadlink",
    "commandsEncoding": "Base64",
    "commands": {
        "on": "JgBQAAABKpUUEhIUEhIUERQSExITFBITEjcUNxM3FTUVNhMSFBITNxQ2FDcTOBISFTYUEhM3FBEUExISFREUNhQRFTYTEhQ3EwAFawABLEoSAA0FAAAAAAAAAAA=",
        "off": "JgBIAAABKZUUERQRFBMSEhYQExIUEhMSFTcSNxQ3EzcUNhUQFRITNhQ4FDUVNhMSEzcVEhI4ExIUERQRFBIVNRQSEzgTERU2EwANBQ==",
        "volumeDown": "JgBEABQSFBITEhURFBEUEhQRFBEVNRQ3FDYVNxM2FBIVEBQ3EzcUERU2FDYUNxMSFDYWEBUQFDgUEBURExMTOBMRFDgTAA0FAAAAAA==",
        "volumeUp": "JgBUAAABK5MUExQQFREUERQTExITExISFTYTOBQ1FDcUNhQUEhETNxQ3FDcUNhM3FDYUOBI3EzcVEhQTERITExMSExMUERMTFAAFagABKkoUAAqoCwANBQAAAAA=",
        "sources": {
            "UP": "JgBEABMSFBITEhQRFBMTEhQRFRAUNxQ2FTUVNxI3FBIUERU1FDcVNRQTExEUERQTEjgUERQRFBITOBM2FTYTOBISFDcUAA0FAAAAAA==",
            "DOWN": "JgBIAAABK5MUEhMSExMTERQSExMUEhQQFTYTNxQ4EjgTNxMTEhMTNhYRFDUUEhQ2FRAUEhQRFBMSOBMRFDcTEhQ3FTYTNhU2EwANBQ==",
            "LEFT": "JgBMAAABLJMVERMUEhMSEhMUEhITExMTEjcTNxQ3FTUTNxQTEhMUNRQTEzYUNxMSFBIUEhMSExIUNxMSFRAUNhY1FTUVNRU2FAAJAg0ADQUAAAAAAAAAAAAAAAA=",
            "RIGHT": "JgBIAAABKpQTFBISExQSEhMSFBITExMRFDcUNhQ2FDcUNhQSExIVNhMSFTUUNxM3FBEVERQRFBITNxQTFBAUERQ3FDcTNhQ3FAANBQ==",
            "OK": "JgBIAAABKpYSEhQRFBEVERURExITExMTEzYUNhQ4FDYUNRQTExEUNxQRFDYUEhMTExEUEhQRFBITNxQSEzcUNhU2FDYUNhQ2FgANBQ==",
            "HOME": "JgBQAAABKpQTEhQTEhIVEBQSExIVEhISFTYTOBI3FDYVNhQRFBITNxM3FDgSOBITExITEhQ2FhAUERQSFRIUNBQ3EzcUExM2EwAFawABK0oSAA0FAAAAAAAAAAA=",
            "BACK": "JgBYAAABK5QUEBMSFRETFBISExIUEhMTEzgSOBI3FTUUNxQRFBMSNxQ2FDYUNxM4ExITEhU1FRISEhQSExMTExI3EzcUEhQ2EwAFbAABKUoTAAJ1DAAM2QwADQU="
        }
    }
}

**Describe the bug**
My device is a Tmall Magic Box which is very similar to MiBox.
There is only the power key on the ”media_player " card, but when you click the power key, the status on the card is always displayed as off, and no other keys appear. When you click the power button on the card, you can actually control the TV on and off.
![image](https://user-images.githubusercontent.com/42339509/126905695-155701af-08e1-42b8-856f-d893c15e67f9.png)

**Debug log**

```text

Add your logs here.

Additional context
Add any other context about the problem here.

@vassilis-panos
@dgomes

Boss, please help me to make it work. Thank you so much

Don't know why I got called in, but I would say binary_sensor.tv_power is not working properly

Don't know why I got called in, but I would say binary_sensor.tv_power is not working properly

How can I fix it?

You must first debug the situation, is the binary_sensor ON ?

Actually I didn’t create this bin_sensor but I didn’t create the ac bin sensor too. AC can be remoted correctlly.
发自我的iPhone

在 2021年7月26日，04:18，Diogo Gomes @.***> 写道：

You must first debug the situation, is the binary_sensor ON ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

just remove the line:
   power_sensor: binary_sensor.tv_power

Ok, I will try it
发自我的iPhone

在 2021年7月26日，04:44，Diogo Gomes @.***> 写道：

just remove the line:
power_sensor: binary_sensor.tv_power
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

It is still not working. The power button can remote this box and tv. It still shows off on HA card
发自我的iPhone

在 2021年7月26日，04:44，Diogo Gomes @.***> 写道：

just remove the line:
power_sensor: binary_sensor.tv_power
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

have you restarted HA 😄  ?

Yes , I edit yaml and restart ha
发自我的iPhone

在 2021年7月26日，05:17，Diogo Gomes @.***> 写道：

have you restarted HA 😄 ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yes I edit yaml and restart Ha
发自我的iPhone

在 2021年7月26日，05:17，Diogo Gomes @.***> 写道：

have you restarted HA 😄 ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

It is ok now!!! Thank you so much. But the button up/down/right/left are sources now, it can not be click repeatedly.
发自我的iPhone

在 2021年7月26日，05:17，Diogo Gomes @.***> 写道：

have you restarted HA 😄 ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


luci-app-keepalived: VRRP preempting option not being reflected on the configuration

Please note: I'm really new to GitHub, I apologize for any mistakes.
Maintainer: if I'm not mistaken the maintainer should be Florian @feckert
Environment: Belkin RT1800 (MT7621, mipsel_24kc), running OpenWrt 23.05.3. Same result when running OpenWrt snapshot r26235-0d74b2a1e5 from 2024-05-08.
I've also reported this on the forum: https://forum.openwrt.org/t/keepalived-vrrp-preempting-not-working/197133
Steps to reproduce:
Two nodes, both starting in VRRP backup mode. The one meant to become the master (R1) has a priority of 120 and the other (R2) of 100. On the LAN VRRP instances, configure weighted tracking of the WAN interface with a weight of 80. When the WAN cable is disconnected at R1, R2 should become the master also for the LAN instances, preempting R1 due to its now higher priority, but that's not happening.
Below is an example instance from R2's /tmp/keepalived.conf
It seems that no matter what settings I change on the luci-app-keepalived (specifically the Disable Preempt option is turned off, but I've tried various other combinations of settings), the nopreempt line never goes away from the configuration.
vrrp_instance iot {
	authentication {
		auth_type PASS
		auth_pass xxxxxxxx
	}
	state BACKUP
	interface br-lan.501
	unicast_src_ip <IP_ADDRESS>
	virtual_router_id 151
	version 3
	priority 100
	advert_int 5
	preempt_delay 30
	garp_master_delay 1
	garp_master_refresh 1
	garp_master_repeat 1
	garp_master_refresh_repeat 1
	nopreempt
	notify_backup "/bin/busybox env -i ACTION=NOTIFY_BACKUP TYPE=INSTANCE NAME=iot /sbin/hotplug-call keepalived"
	notify_master "/bin/busybox env -i ACTION=NOTIFY_MASTER TYPE=INSTANCE NAME=iot /sbin/hotplug-call keepalived"
	notify_fault "/bin/busybox env -i ACTION=NOTIFY_FAULT TYPE=INSTANCE NAME=iot /sbin/hotplug-call keepalived"
	notify_stop "/bin/busybox env -i ACTION=NOTIFY_STOP TYPE=INSTANCE NAME=iot /sbin/hotplug-call keepalived"
	virtual_ipaddress {
		<IP_ADDRESS> dev br-lan.501 label br-lan.501:v501 scope global
	}
	track_interface {
		wan weight 80
	}
	unicast_peer {
		<IP_ADDRESS>
	}
}

The logs also report that VRRP is running in nopreempt mode.
Thu May  9 12:37:01 2024 daemon.info Keepalived_vrrp[3360]: (wan) preempt_delay is incompatible with nopreempt mode - resetting
Thu May  9 12:37:01 2024 daemon.info Keepalived_vrrp[3360]: (lan) preempt_delay is incompatible with nopreempt mode - resetting
Thu May  9 12:37:01 2024 daemon.info Keepalived_vrrp[3360]: (iot) preempt_delay is incompatible with nopreempt mode - resetting

Expected behavior:
Being able to run VRRP in preempt mode, so that the node with the highest priority would become master.
Additional Information:
OpenWrt version information from system /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='23.05.3'
DISTRIB_REVISION='r23809-234f1a2efa'
DISTRIB_TARGET='ramips/mt7621'
DISTRIB_ARCH='mipsel_24kc'
DISTRIB_DESCRIPTION='OpenWrt 23.05.3 r23809-234f1a2efa'
DISTRIB_TAINTS=''

@grifos Thank you for your bug report. Should be fixed.

Thank you so much Florian. Up to you if you want to backport it, though it would probably just be for one user, eg. me, then I can easily just upgrade to snapshot.


E2E test for Azure Activity Logs source is flaky, fails to receive event after 10 min

Right now, it takes on average ~5 attempts before the e2e test suite completes, and this source is often the culprit.
Either we generate our activity ("new resource group") too early and it's never sent to the destination, or we don't wait long enough for it to be received.
I'll first try to increase the timeout to 15 min, run this specific test in continuous mode, and see whether I'm still getting errors.
If yes, I'll check whether pausing before generating the activity helps to stabilize the test.

What I noticed so far is that the test completes (rarely) in ~200 seconds, more often in ~400 seconds, and sometimes still hasn't completed after 900 seconds, in which case I think we can assume the activity log wasn't sent at all.
I have a feeling timing could be involved here.
Maybe the problem is similar to the one we saw with the Google Cloud Audit Logs source (#472), where we would sometimes have to wait up to 150 secs between the moment the log router is set up and the moment we generate a log for it to be propagated.

I tried to add a delay between the moment the source is created and the Resource Group is created, as explained above, and this didn't seem to have any effect on the flakiness of the test.
My next assumption would be that the Diagnostic Settings are created too quickly after the creation of the Event Hubs instance, and sometimes that instance might now be fully created yet (eventual consistency?).
In which case the issue wouldn't be fixable in the E2E test, but rather in the reconciler.


bug(v2): unable to build site when swizzling components (when src/theme/NotFound.js is present)

🐛 Bug Report
If a user swizzles NotFound.js as src/theme/NotFound.js, yarn build will fail.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

Use this branch
In website-build-fail, run yarn build

OR

Create a new Docusaurus 2 site
Add src/theme/NotFound.js
Use this content:

import React from 'react';
import Layout from '@theme/Layout';

function NotFound() {
  return <Layout title="Page Not Found">Not Found</Layout>;
}

export default NotFound;

Run yarn build
Expected behavior
Site builds
Actual Behavior
Get the error:
# yangshun @ yangshun-mbp in ~/Developer/tech-interview-handbook/website on git:master x [1:39:54]
$ yarn build
yarn run v1.16.0
$ docusaurus build
Creating an optimized production build...

✔ Client
  Compiled successfully in 22.34s

✖ Server
  Compiled with some errors in 24.70s

Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade`

TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at Array.reduce (<anonymous>)TypeError: Cannot convert undefined or null to object
    ...
(undefined) TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at main:24269:12
    at Array.reduce (<anonymous>)
    at getBundles (main:24268:20)
    at render (main:49334:113)
    at <anonymous>
(undefined) TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at main:24269:12
    at Array.reduce (<anonymous>)
    at getBundles (main:24268:20)
    at render (main:49334:113)
    at <anonymous>
    ...
Error: Failed to compile with errors.
    at compiler.run (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/@docusaurus/core/lib/commands/build.js:37:24)
    at finalCallback (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/MultiCompiler.js:254:12)
    at runWithDependencies.err (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/MultiCompiler.js:277:6)
    at done (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/neo-async/async.js:2931:13)
    at runCompilers (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/MultiCompiler.js:181:48)
    at err (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/MultiCompiler.js:188:7)
    at compiler.run (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/MultiCompiler.js:270:7)
    at finalCallback (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/Compiler.js:257:39)
    at hooks.done.callAsync.err (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/Compiler.js:273:13)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:42:1)
    at AsyncSeriesHook.lazyCompileHook (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/tapable/lib/Hook.js:154:20)
    at onCompiled (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/Compiler.js:271:21)
    at hooks.afterCompile.callAsync.err (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/Compiler.js:681:15)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/tapable/lib/Hook.js:154:20)
    at compilation.seal.err (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/Compiler.js:678:31)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
    at AsyncSeriesHook.lazyCompileHook (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/tapable/lib/Hook.js:154:20)
    at hooks.optimizeAssets.callAsync.err (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/webpack/lib/Compilation.js:1423:35)
    at _err0 (eval at create (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:16:1)
    at tryCatcher (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/@endiliey/static-site-generator-webpack-plugin/node_modules/bluebird/js/release/util.js:16:23)
    at Promise.successAdapter [as _fulfillmentHandler0] (/Users/yangshun/Developer/tech-interview-handbook/website/node_modules/@endiliey/static-site-generator-webpack-plugin/node_modules/bluebird/js/release/nodeify.js:23:30)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Observations

Happens for all swizzled components, not just src/theme/NotFound. src/theme/Footer can result in the same issue
The crash is in react-loadable-ssr-addon/lib/getBundles.js. I suspect this problem is related to https://github.com/themgoncalves/react-loadable-ssr-addon/issues/8

I am using it in my doc website (a custom NotFound.js) where the docusaurus is in the root of my repo and it works just fine. Before, when I had my website folder, I had the same issue.

I ran into this error only after I swizzled the DocPage component (had previously swizzled DocItem, Navbar, and CodeBlock).
After some troubleshooting, I landed on this issue and decided to try swizzling the NotFound component (in addition to DocPage). This resolved the issue for me.

Similar to @sserrata , I had to swizzle all three of DocItem, DocPage, and NotFound to avoid the build error.

I'm hitting this issue as well.

Is there any workaround other than swizzling more components?
Is there a way to build without SSR?

@yangshun could we close this issue if there is no way to reproduce it?

could we close this issue if there is no way to reproduce it?

Repro is here https://github.com/facebook/docusaurus/tree/repro-2244/website-build-fail

Fixed in https://github.com/facebook/docusaurus/pull/2854


support targets with file-based DescriptorSetGenerator

Follow-up of https://github.com/scalapb/protoc-bridge/pull/85

I'll will add a commit with a scripted test using DescriptorSetGenerator shortly

commit amended with a scripted test

Thank you!


Fatal error

Whenever i launch the game i get an error which says that the mod encountered a fatal error
LogOutput.log

This is a common issue with pirated copies.


Deploy NSG and VM public IPs when internal standard LB selected

This PR deploys a Network Security Group when a Standard SKU internal Load Balancer is selected and the loadBalancerType is internal. Each VM in ther backend pool is also dynamically assigned a Standard SKU public IP address to allow outbound traffic, which is prevented by default when a Standard SKU load balancer is in front of the VMs.
Fixes #308

before merging, run
npm run links -- --branch master

LGTM, tad sad this is something we even need to consider and does not work out of the box though.

Agreed


Hydrogen stopped working after updating Atom

After updating Atom 1.47.0 Hydrogen stopped working. I followed Hydrogen troubleshooting guide but still do not work: https://nteract.gitbooks.io/hydrogen/docs/Troubleshooting.html#hydrogen-stopped-working-after-updating-atom
Thanks,
Marcos

follow our issue template otherwise we can't help


[nrf fromtree] mgmt: mcumgr: Add SMP SVC and CHR UUIDs to header

Added the SMP service and characteristic UUIDs to the smp_bt module header and used those definitions.
Signed-off-by: Mateusz Kapala<EMAIL_ADDRESS>(cherry picked from commit 77555898de6cb2b0a1933edd35e97c7d55ac26e2)
manifest-pr-skip

Rebase only


Do not allow combination of --context with (project, app and component) flags

based on: https://github.com/openshift/odo/issues/2387#issuecomment-553866802_
It can be confusing when --context flag is used together with one or more --project --app --context flags.
We should add a check that doesn't allow the use of --context with --app or --project or --context.

/kind feature
/priority medium


Add Flexible Font Path

Summary
Adds alternate font path for when SDK installation methods flatten the resource folder.

Current dependencies on/for this PR:

main

PR #94   👈

This comment was auto-generated by Graphite.

@lucillebenoit started a stack merge that includes this pull request via Graphite.

@lucillebenoit merged this pull request with Graphite.


Allow fetching Resources with zero parameter

Using different column then id to fetch Resources breaks if numbers starts from zero.

Any news on that?

Thanks for the prompt!


Clustering enabled, but Metrics still being double collected

What's wrong?

I have clustering enabled and I am only collecting pod metrics currently for simplicity, but I metrics are still being double collected leading to out of order errors in my alloy and mimir pod

Steps to reproduce
Here is my helm configuration:
alloy:
  alloy:
    clustering:
      enabled: true
    configMap:
      content: |-
        logging {
          level = "info"
          format = "logfmt"
        }

        remote.kubernetes.secret "credentials" {
          namespace = "monitoring"
          name = "prom-basic-auth-secret"
        }

        discovery.kubernetes "alloyPodsDiscovery" {
          role = "pod"
        }

         discovery.relabel "replace_instance" {
          targets = discovery.kubernetes.alloyPodsDiscovery.targets
          rule {
            action        = "replace"
            source_labels = ["instance"]
            target_label  = "instance"
          replacement   = "alloy-cluster"
          }
        }

        prometheus.scrape "pods" {
          targets    = discovery.relabel.replace_instance.output
          forward_to = [prometheus.remote_write.mimir.receiver]
          scrape_interval = "60s"
           clustering{
            enabled = true
          }
        }

        prometheus.remote_write "mimir" {
          external_labels = {
            cluster = "<redacted>",
          }
          endpoint {
            url = "<redacted>"
            remote_timeout = "2m"
            queue_config {
              capacity = 2500
              max_samples_per_send = 500
              max_shards = 5
            }
            write_relabel_config{
              action = "drop"
              regex = "container_network.*|container_fs.*|container_blkio_device_usage_total|csi_operations_seconds_bucket|rest_client_request_duration_seconds_bucket|apiserver_request_duration_seconds_bucket|etcd_request_duration_seconds_bucket|storage_operation_duration_seconds_bucket|container_ulimits_soft"
              source_labels = ["__name__"]
            }
            basic_auth {
              username = nonsensitive(remote.kubernetes.secret.credentials.data["username"])
              password = remote.kubernetes.secret.credentials.data["password"]
            }
          }
        }

System information
No response
Software version
Grafana alloy v1.3.1
Configuration
alloy:
alloy:
clustering:
enabled: true
configMap:
content: |-
logging {
level = "info"
format = "logfmt"
}
    remote.kubernetes.secret "credentials" {
      namespace = "monitoring"
      name = "prom-basic-auth-secret"
    }

    discovery.kubernetes "alloyPodsDiscovery" {
      role = "pod"
    }

     discovery.relabel "replace_instance" {
      targets = discovery.kubernetes.alloyPodsDiscovery.targets
      rule {
        action        = "replace"
        source_labels = ["instance"]
        target_label  = "instance"
      replacement   = "alloy-cluster"
      }
    }

    prometheus.scrape "pods" {
      targets    = discovery.relabel.replace_instance.output
      forward_to = [prometheus.remote_write.mimir.receiver]
      scrape_interval = "60s"
       clustering{
        enabled = true
      }
    }

    prometheus.remote_write "mimir" {
      external_labels = {
        cluster = "<redacted>",
      }
      endpoint {
        url = "<redacted>"
        remote_timeout = "2m"
        queue_config {
          capacity = 2500
          max_samples_per_send = 500
          max_shards = 5
        }
        write_relabel_config{
          action = "drop"
          regex = "container_network.*|container_fs.*|container_blkio_device_usage_total|csi_operations_seconds_bucket|rest_client_request_duration_seconds_bucket|apiserver_request_duration_seconds_bucket|etcd_request_duration_seconds_bucket|storage_operation_duration_seconds_bucket|container_ulimits_soft"
          source_labels = ["__name__"]
        }
        basic_auth {
          username = nonsensitive(remote.kubernetes.secret.credentials.data["username"])
          password = remote.kubernetes.secret.credentials.data["password"]
        }
      }
    }

Logs
ts=2024-09-04T16:21:21.005501451Z level=error msg="non-recoverable error" component_path=/ component_id=prometheus.remote_write.mimir subcomponent=rw remote_name=1c21e0 url=<redacted> count=500 exemplarCount=0 err="server returned HTTP status 400 Bad Request: failed pushing to ingester: user=anonymous: the sample has been rejected because another sample with a more recent timestamp has already been ingested and out-of-order samples are not allowed (err-mimir-sample-out-of-order). The affected sample has timestamp 2024-09-04T16:21:19.73Z and is from series {__name__=\"response_latency_ms_bucket\", authz_kind=\"default\", authz_name=\"all-unauthenticated\", client_id=\"prometheus.linkerd-viz.serviceaccount.identity.linkerd.cluster.local\", cluster=\"<redacted>\", direction=\"inbound\", instance=\"alloy-cluster\", job=\"prometheus.scrape.pods\", le=\"300\", route_kind=\"default\", route_name=\"default\", srv_kind=\"default\", srv_name=\"all-unauthenticated\", status_code=\"200\", target_addr=\"<redacted>1\", target_ip=\"<IP_ADDRESS>\", target_port=\"4191\", tls=\"true\"}"

I'm having the same issue.  Using a daemonset with clustering.  I don't see any errors that indicate any alloy instance is failing to send metrics but somehow getting out of order results.  With clustering enabled I'd expect the target to be handled by a single alloy instance and it never change and that a previous failed write would be tried before sending a new metric.  Though like I said I don't even see any failed writes.

According to docs clustering is only supported in statefulset


Data science integration

Current Situation
ReactPy currently requires too much web development knowledge for data scientists applications.
Proposed Actions
Create reactpy-data-science which contains pre-styled, self-contained components.
A few target goals we should have are:

Package should not require hooks to operate
Can easily be deployed to our cloud hosting architecture (see: #1065)
Contains a simplified version of reactpy.run that sets up a deployment ready ASGI configuration.

Blocked on #1065

I would like to work on this issue. Can you assign me to this issue?

@JaynouOliver We generally do not use the GitHub issue assignment feature.
Priority is given to the first person to open a PR.

sure!


deps: update images to 0.94

We need a new version of images to make sure we don't build non-Final Fedora 41 images.

Need to wait for the Go proxy to update and then force push, it currently selected 0.93.


Abuse sensor

#262

This is one for https://github.com/BYU-PCCL/holodeck-configs but do we want to add these sensors to some scenarios? I would say at least the UAV scenarios.


Severe problem when passing big payload

I am running into a rather severe issue when trying to send a message payload containing a 200.000+ JSON object Array. Once the sending node actually sends the message, the receiving node receives the message after 3 to 10 minutes (!). In the meantime, node-red server is almost dead…
In some cases, the node-red server hangs after a while. It seems not to be a matter of memory.
The behavior is rather odd – as it does NOT happen, when the receiving node is “in the same domain” as the sending node, example:
When an http in-node receives a request, processes the request (e.g. in a function node that generates a big payload) and sends it to the http-out node then the http-out node will receive the message without delay. However, when there is another node linked to the sending node (e.g. a function node), then the described problem occurs.
Below, I have added a sample flow that reproduces the problem...

[x] Node-RED version: 0.18.7
[x] node.js version: 10.8.0
[ ] npm version:
[x] Platform/OS: Windows 10 X64 (tested on various machines)
[ ] Browser:

Flow:
[{"id":"8f6c2f3e.c9ce2","type":"function","z":"ad2eb039.e69a5","name":"create docs","func":"var p = [];\nfor (var i = 0; i < 500000; i++) {\n    p.push(\n        {\n        "valueName" : "cycleExecution",\n        "value" : "started",\n        "duration" : 442,\n        "tsStart" :<PHONE_NUMBER>000.0,\n        "tsEnd" :<PHONE_NUMBER>000.0,\n        "msgType" : "bucket",\n        count: i\n        });\n}\n\nmsg.payload = "payload created: " + p.length + " JSON objects";\nnode.send(msg, null);\n\nsetTimeout(function () {\n    msg.payload = p;\n    node.send([null, msg]);    \n}, 500)\n","outputs":2,"noerr":0,"x":307,"y":108,"wires":[["1d0b8c57.00ed94"],["ba763974.935e48","f971b8ed.1fd5e8"]]},{"id":"9f54b732.5d58c8","type":"inject","z":"ad2eb039.e69a5","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"x":137,"y":108,"wires":[["8f6c2f3e.c9ce2"]]},{"id":"1d0b8c57.00ed94","type":"debug","z":"ad2eb039.e69a5","name":"","active":true,"console":false,"complete":"false","x":517,"y":103,"wires":[]},{"id":"ba763974.935e48","type":"function","z":"ad2eb039.e69a5","name":"Reveiving msg???","func":"msg.payload = "Function-node received OK";\nreturn msg;","outputs":1,"noerr":0,"x":522,"y":203,"wires":[["4ad250a0.e845b"]]},{"id":"4ad250a0.e845b","type":"debug","z":"ad2eb039.e69a5","name":"","active":true,"console":false,"complete":"false","x":712,"y":198,"wires":[]},{"id":"f971b8ed.1fd5e8","type":"change","z":"ad2eb039.e69a5","name":"","rules":[{"t":"set","p":"hello","pt":"msg","to":"world","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":522,"y":153,"wires":[[]]}]

I have done a bit more testing:
It seems that when the flow is a one by one flow (every node is only linked to one node), then there is no problem. Only when the "big payload node" has more than one connections then the problem comes up.

when a flow forks we have to clone the message rather than pass by references (so that actions on the other leg of the flow do not modify the object in the first) - cloning an object the size you have mentioned will a) take at least 2x the memory and b) time !

@pelis as Dave describes, if you have a flow that branches, it has to clone the message to prevent one
branch modifying the message in another branch.
Do you need to send the full 200,000 element array down each branch? Can you optimise your flow to avoid sending the full payload where it isn't needed?
There isn't much we can do about this in the core of Node-RED.

OK, I can certainly modify the flow (which I already did).
I just thought that the behavior itself might be worth mentioning and looking at.
Looking at it, redUtil.cloneMessage(m) is a rather long-lasting method. Just for testing purposes I have replaced that with “var clonedmsg = JSON.parse(JSON.stringify(m));” On my machine this is about 100 times faster, I am sure you have good reasons why it is as it is, but I consider that very important to know when designing flows. So when a flow is dealing with heavy load data, whether it comes in as a stream or a bulk array, you better do not fork the output…
We actually have had similar issues before, when we had streaming scenarios with heavy data loads. We ran into back pressure problems and had to solve it with different approaches.
However, thanks for replying

Thanks for the update. I've been poking around to see if we can make any further optimisations to avoid cloning... but all the obvious things have already been done.
The problem with the JSON.parse/stringify technique is that it only works for JSON encodable data For other types, such as Date and Buffer, they get transformed by the stringify step and not properly restored by the parse step. Some other types are silently dropped.
Optimising the message path is something we always need to consider - but I'm not sure having a perennially open issue on the matter will benefit us. I'm going to close.


Boundary conditions plotting

Implementation for plotting boundary conditions.
So far, only nodes are allowed, and only some loads/constrains are allowed.
ToDo's

[x] Add documentation
[x] Add unit tests

Related

Closes #741

Pyvista legends do not work very well. The icon do not fit the real glyph.

Agreed.

But this is quite a lot of work, and I'm not sure the whole plotting thing is priority.

I think that it's great as is. Let's merge this (as soon as we have an example), and improve it in a follow-up.

I have added some docs too:

Not much since this is kind of beta work

Not much since this is kind of beta work

Beta is better than none.

I'm going to work in #731 at the same time as this (regular merges from here to there), so we can use that tech_demo as example for this feature.
I believe tech_demo 28 is more suitable that tech_demo 15. We can also add the pyvista charts.

Hi @koubaa Thank you for your comments!
I agree totally with you. This is fine for now, but if plotting gather attention, we might need to re-think the whole general_plotter function and make it more OO. I believe the way to go is subclassing Pyvista Plotter. But again, since there are many things to do, let's see this feature traction first.

DO NOT MERGE
I'm preparing at the same time #731 so the changes demanded by that tech_demo will be included in this PR.

@germa89, let's get this merged to have the tech demos and 0.62.0 out. I'm looking forward to having this finally merged.


TypeError: Cannot read property 'getFieldErrorMsg' of undefined

Version
1.0.0-beta.20
Reproduction link
https://codesandbox.io/s/lp77x68139
Steps to reproduce
run test
What is expected?
not having error "Cannot read property 'getFieldErrorMsg' of undefined"
What is actually happening?
my componont extends an other component wich contain a method called getFieldErrorMsg. On normal running, all works, on testing, method isn't found.

Can you provide a full reproduction, with a working example. The code you provided fails when run in a browser, as well as when it runs in a test.

Closing due to inactivity. I'm happy to reopen if you provide a reproduction.


Debug fails to detect launch targets in remote

This is the vscode folder in WSL:

I can not reproduce this with Docker + a repository with launch.json. Does this only repro for VS Code for you?
Unfortunately docker + VS Code repository does not work for me - I have informed @chmarti and he is investigating this issue.
It smells like some file reading is incorrect and the launch configuration does not get read or a file event is missing.
Best would be to put a breakpoint here and check what the debugUx  context gets set to. It should be default but probably for you it gets set to simple.
I can also investigate once vscode repo can be opened in docker.

@dbaeumer is also seeing this
@sandy081 did we change anything with regards to how configurations are read from a remote in the last couple of days?

@isidorn Yes, I changed reading of configuration files to be atomic (#117869)
https://github.com/microsoft/vscode/blob/bc444ac379788b2eb7453f85c16011ececc6fb8b/src/vs/workbench/services/configuration/browser/configuration.ts#L111-L111
@bpasero Does this change affects remote fs operations?

I pushed a try to get this fixed, not sure if it helps...
Will know more once I can repro on my machine.

The only thing atomic: true does is to wait for pending writes to finish and block new writes from starting before that finishes, nothing else.

@isidorn I can't repro today:
Version: 1.55.0-insider (user setup)
Commit: 5d80c30e5b6ce8b2f5336ed55ad043490b0b818f
Date: 2021-03-08T05:13:14.184Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

@joaomoreno thanks for letting me know. Maybe @sandy081 pushed something
Would be interesting to see if @dbaeumer still see this

Works for me today.

Then it seems somebody pushed a fix for this. Maybe @sandy081
Closing and let me know if you see it again and I can reopen.
Thank you and sorry about the breakage

Still seeing it in a different flow now. Reopening

Still seeing it in a different flow. Will create a screen cast.

@isidorn I have not pushed any changes.

I just found this issue... opened a similar one here:
https://github.com/microsoft/vscode-remote-release/issues/4628
I will dupe that to this one

I just tried this following nice steps from https://github.com/microsoft/vscode-remote-release/issues/4628
And I still can not reproduce.
@TylerLeonhardt @dbaeumer @joaomoreno can you still reproduce this issue with latest? If someone can reproduce can you please ping me so we try to do a debugging session together? Thanks!

I can't reproduce.

Thanks Dirk.
Closing for now. If somebody still sees this please let me know and I will reopen


Grafana Minified React Error #321

I was previously using this plugin and had absolutely no problems with it. However since updating my Backstage backend to match the new backend version, I have now encountered this error which has confused me greatly as it's not even in the backend. I've been back through the instructions for adding it to my app, and everything looks the same as before and I can't see any differences with the example and what I have (apart from the DNS etc). I have been through my react and react-dom versions, and they match everywhere.
This is the full error message:
Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

I get this error when I try to run it locally with the example data with the grafana plugin