net/http: server permits handlers to write headers with newlines

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

$ go version
go version go1.17rc1 linux/amd64

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="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17rc1"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/go/src/crlfpoc/go.mod"
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-build2202782937=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.17rc1 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.17rc1
uname -sr: Linux 5.10.52-1-MANJARO
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Debian GLIBC 2.28-10) stable release version 2.28.

What did you do?
Consider the following code:
package main

import (
	"fmt"
	"log"
	"net/http"
)

func main() {
	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		headerName := r.URL.Query().Get("name")
		headerValue := r.URL.Query().Get("value")
		w.Header().Set(headerName, headerValue)
		fmt.Fprintf(w, "Hello World")
	})

	fmt.Printf("Starting server at port 3000\n")
	if err := http.ListenAndServe(":3000", nil); err != nil {
		log.Fatal(err)
	}
}

When requesting http://localhost:3000/?name=%0a%0a%3Chtml%3E%3Cscript%3Ealert(%27not%20supposed%20to%20happen%27)%3C/script%3Easd&value=a%0aasd,  the name parameter's value (name=%0a%0a<html><script>alert('not supposed to happen')</script>) is set as the header's name. But due to no sanitization, %0a can be used to inject new headers or arbitrary HTML content.
What did you expect to see?
%0a in the header's value is sanitized and causes no CRLF. The same could be expected in the case of header's name.
What did you see instead?
Proper sanitization of the header's name.

Thanks. A better repro, as the query param part is fine and a bit of a distraction:
https://play.golang.org/p/v7ghPz4CfxT
func main() {
	ts := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		w.Header().Set("Foo", "Bar")
		w.Header().Set("Xxx: xxxx\nSmuggle", "smuggleval")
	}))
	res, err := http.Get(ts.URL)
	if err != nil {
		log.Fatal(err)
	}
	res.Write(os.Stdout)
	fmt.Printf("%v", res.Header)
}

Produces:
HTTP/1.1 200 OK
Date: Tue, 10 Nov 2009 23:00:00 GMT
Foo: Bar
Smuggle: smuggleval
Xxx: xxxx
Content-Length: 0

map[Content-Length:[0] Date:[Tue, 10 Nov 2009 23:00:00 GMT] Foo:[Bar] Smuggle:[smuggleval] Xxx:[xxxx]]

@Az3z3l @bradfitz Is this new in Go 1.17?
CC @neild via https://dev.golang.org/owners

@Az3z3l @bradfitz Is this new in Go 1.17?

Also present in 1.16.

Thanks for this fix ;-)


Add support for XDP/TC and other types of BPF program.

Now we usually use bpftrace to write tracepoint or kprobe programs, but it does not support XDP, TC and many other types of BPF program. We have to write XDP programs in C, which is not so convenient. I think it would be more efficiency to write short XDP/TC program with a script language.
Is there any plan to support XDP ot TC in the future?

Hi, xdp/tc/tcx support is an interesting idea. I see there was some old discussion in #319. However, I worry that this is outside bpftrace's core use case and it'll end up causing us basically re-develop C, as packet processing really lends itself to C.
Do you have more specific use cases you can share?


Build multi-arch Docker image

Based on https://medium.com/@tonistiigi/faster-multi-platform-builds-dockerfile-cross-compilation-guide-part-1-ec087c719eaf
A sample image built on Mac M1 with Docker Desktop is at https://hub.docker.com/r/solsson/kafka-consumers-prometheus. The build command can, I think, list any platforms supported by golang.
docker buildx build --platform=linux/amd64,linux/arm64/v8 -t solsson/kafka-consumers-prometheus --push .

I've tested the image on k3s running on Ubuntu ARM.

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

Hey @solsson , good to hear from you! Thank you for the PR. I'm a bit hesitant to merge it right now, because I'm unsure how it would affect the existing build pipelines (e.g. unsure if we use buildkit), so I'll have a look and get back to this.

Agreed. It affects workflows quite significantly, in particular buildx can no longer do --load.

Great!


ValueError: output of generator should be a tuple (x, y, sample_weight) or (x, y). Found: None

when running python train.py s1(overlapped_speakers),
I met this problem:

could anyone know this and tell me the way to solve this problem, thanks!

@riya-maan I encountered same issue ,can you help me ?

I encountered same issue ,can you help me? Did you manage to resolve it? Thanks

I solved it, and I am converting from python 2.7 to 3.6 code

@jeonsanghun  Can you please explain how you resolved the issue?


az vmss update-instances not working

I am having an issue.
az vmss update-instances --instance-ids * --name server_scaleset --resource-group web_rg
the error I get is this: The provided instanceId data.tf is invalid. It must be a non-negative integer or the character "*".
data.tf is actually the first file in the PWD where the command was run from on the terminal.
Tried same on Portal CLI and the error was: The provided instanceId clouddrive is invalid. It must be a non-negative integer or the character "*".
AZ CLI version: 2.11.1
All I can do is run the command for all instances one at a time like so
az vmss update-instances --instance-ids 2 --name server_scaleset --resource-group web_rg
az vmss update-instances --instance-ids 3 --name server_scaleset --resource-group web_rg
And i dont think this makes sense

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

ID: 0408c294-207a-2b72-7b93-e09121602b75
Version Independent ID: 852cb67b-70c6-b811-3b0a-5d5b84b8a911
Content: az vmss
Content Source: src/azure-cli/azure/cli/command_modules/vm/_help.py
Service: virtual-machine-scale-sets
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

hi @qwordy could you pls have a look?

I think * is translated by your terminal. Please add " around *. --instance-ids "*"

@sysadmin-exe Do I solve your problem?

Oh yea please @qwordy thanks.

Oh yea please @qwordy thanks.

Cool! I will close this issue.


Handling different image sizes?

For this challenge I am trying to use CNN's as you did. But I am facing difficulty in handling different image sizes in training data. I am interested to know how did you handle this issue?
PS : I am trying it in keras and I am not familiar with torch, so I am not able to figure it out from code.

Sorry my bad. It was simple image resizing.


Select codec type lazily

This is a stub to support dynamically selected encoder.

I think this should work.
diff --git a/alvr/server/cpp/platform/linux/EncodePipelineSW.cpp b/alvr/server/cpp/platform/linux/EncodePipelineSW.cpp
index ea13827b..149fe849 100644
--- a/alvr/server/cpp/platform/linux/EncodePipelineSW.cpp
+++ b/alvr/server/cpp/platform/linux/EncodePipelineSW.cpp
@@ -35,14 +35,9 @@ void x264_log(void *, int level, const char *fmt, va_list args)

 alvr::EncodePipelineSW::EncodePipelineSW(Renderer *render, uint32_t width, uint32_t height)
 {
+  Settings::Instance().m_codec = ALVR_CODEC_H264;
   const auto& settings = Settings::Instance();

-  if (settings.m_codec == ALVR_CODEC_H265)
-  {
-    // TODO: Make it work?
-    throw std::runtime_error("HEVC is not supported by SW encoder");
-  }
-
   x264_param_default_preset(&param, "ultrafast", "zerolatency");
   x264_param_apply_profile(&param, "high");

Hmm, are you able to pass the codec parameter along? I don't like modifying settings themselves, they are supposed to be immutable.

Sure, that was quick&dirty solution since it only applies to software encoder anyway.
ParseFrameNals can take codec parameter.

Can I merge this PR as is and you take it from here in another PR?

Yes


ZK Client Doesn't Recover Session on Reconnect

We're seeing an issue with the library where we lose the session when running into an error talking to a Zookeeper node.  We discovered this when an ephemeral node kept disappearing when we had a partition between client and server, even though we reconnect within the sessionTimeout.
Here are the logs from an event:
Recv loop terminated: err=read tcp <IP_ADDRESS>:55201-><IP_ADDRESS>:2181: i/o timeout
Send loop terminated: err=<nil>
received zk event: {EventSession StateDisconnected  <nil> <IP_ADDRESS>:2181}
received zk event: {EventSession StateConnecting  <nil> <IP_ADDRESS>:2181}
Connected to <IP_ADDRESS>:2181
received zk event: {EventSession StateConnected  <nil> <IP_ADDRESS>:2181}
Authenticated: id=311955325020296318, timeout=4000
received zk event: {EventSession StateHasSession  <nil> <IP_ADDRESS>:2181}

sendLoop calls conn.Close()
https://github.com/samuel/go-zookeeper/blob/master/zk/conn.go#L322-L324
conn.Close() sends a CloseRequest
https://github.com/samuel/go-zookeeper/blob/master/zk/conn.go#L231
CloseRequest terminates the session
https://zookeeper.apache.org/doc/r3.2.1/zookeeperProgrammers.html
The behavior we're expecting is re-connecting to the zookeeper server and re-establishing the same session.  Still trying to understand the code better to see if there's an obvious fix.

sendLoop calls c.conn.Close() and not c.Close().
c.conn.Close() closes net.Conn not zk.Conn.

Facing a similar issue where ephemeral nodes are lost on session reconnect. Anyone having any thoughts on the fix for this?

seems not fixed

To update this followers, we did find that our session timeouts were mismatched between zookeeper and the client.  Updating that helped some.

The problem still exists: when some client timeout, the ephemeral nodes created by the client are lost. hope
fix the bug as soon as possible.

Please update on this 3 year old issue...


Only first link in the note is previewed

As described in the title, when you are composing note, only first link will be previewed.
Steps to reproduce

Start composing message
Enter two links, like:

https://m.primal.net/HQHe.mp4
and
https://m.primal.net/HQHe.mp4
3. Only first link will be previewed
Expected behavior
Both links are previewed
Additional context
Here is a video that illustrates the bug:
https://github.com/PrimalHQ/primal-web-app/assets/5191402/ef364fed-01d6-4035-b2cd-bc39ddf7d60d

I believe this is fixed. Closing


Please add iOS platform support

Hi, currently there is no plan to support iOS platform yet, could you please try building it for platform linux with AOT mode disabled:
cd product-mini/platforms/linux
mkdir build && cd build
cmake .. -DWAMR_BUILD_INTERP=1 -DWAMR_BUILD_AOT=0
make

or porting the platform by yourself? Here is the reference porting guide. Thanks.


Enhance Documentation for Setting resource_processor_number_processes_per_instance

Description
At present we can set the number of processes that are running on each resource processor instance, but there isn't any clear documentation on how to pick a "good" number for this.
The .env (and new .yaml config) sets this to a default of 5.
The code has a default of 1 if not config is set.
However, in neither location do we say how to set this value.
e.g.

Is it OK to set this to 1?
Is it OK to set this value to 10?
Do the number of CPUs on an instance have some bearing on this value?
What value ranges (if any) have we tested?

Some guidance (even if it's vague and simply says "set between X and Y") would be good.

FWIW, I ran some scaling tests in the summer, and increased the number of processes allowed on the resource processor, I doubled it. I then found I was getting errors from Azure API rate limits. So this is a point of potentially limited scalability.


Solved Simple Text editor in C++

Related Issue
Solved issue number: #310
Describe the changes you've made
Added source code for Simple Text Editor in C++
Describe if there is any unusual behavior of your code(Write NA if there isn't)
NA
Language used for coding
C++
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] New and existing unit tests pass locally with my changes.

Please review my code ;)


WIP: [Notebook Scale] LTS improvements

This PR introduces multiple lts payload improvements for the notebook scale test.

/test notebooks-light

/test notebooks-light

/test notebooks-light

pydantic.error_wrappers.ValidationError: 1 validation error for NotebookScalePayload
$schema
  string does not match regex "^urn:rhods-notebooks:(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$" (type=value_error.str.regex; pattern=^urn:rhods-notebooks:(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$)
---

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/797/pull-ci-openshift-psap-ci-artifacts-main-notebooks-light/1671417674673950720/artifacts/light/test/artifacts/003__plots/_matbench_generate_lts.log

Missed a character in  the schema field
/test notebooks-light

/test notebooks-light

/test notebooks-light

/test notebooks-light

/test notebooks-light

test passed

thanks @kdvalin , looks good :)
I suggested a minor change, can you apply it, rebase, and remove the WIP flag? I'll merge when that's ready :)

@kpouget Done, test field is still not getting populated.  Will investigate tomorrow.

/test notebooks-light

/test notebooks-light

@kdvalin , I think the LTS payload of this PR has the expected value: unspecified
if you want to have something different, you need to override the default value, one way or another.
One way is with:
/var tests.notebooks.identifier=my_custom_test

the other way would be to modify eg the light profile, but we don't need it here.
I'll merge this PR. Can you open another PR with a WIP file, and launch this test: notebook_gating_scale_test_light so that we can confirm how the identifier field of each of the payloads is defined?
I'll guess we'll have to update the gating preset with something like this:
notebook_gating_scale_test:
    'ci_presets.notebook_scale_test["tests.notebooks.identifier"]': "notebook_gating_test:scale_test"
    'ci_presets.notebook_performance["tests.notebooks.identifier"]': "notebook_gating_test:performance_test"


investigate using oxy

Should take a look at the Oxy project as a replacement for the standard net.http.httputil reverse proxy. The project also comes with a few extra middleware worth perhaps looking at

an alternative is goproxy ...


SuperStream

Source name
SuperStream
Source URL
https://www.showbox.media/
Package type
bangumi
Source language
en
Other details
using showbox.media
https://codeberg.org/cloudstream/cloudstream-extensions/src/branch/master/SuperStream
from movie-web.app (ts version derived from cloudstream version): https://github.com/movie-web/movie-web/tree/dev/src/backend/providers/superstream
from flixquest-api (ts version using and importing from movi-web.app codes): https://github.com/BeamlakAschalew/flixquest-api/blob/main/src/routes/superstream.ts
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.

https://github.com/movie-web/providers/tree/dev/src/providers/sources


Navbar spacing is inconsistent in rtl languages

As seen in the comments of https://github.com/electron/electronjs.org/pull/1254, particularly https://github.com/electron/electronjs.org/pull/1254#issuecomment-390864119:
Spacing between the navbar links is still set by left margin instead of right margin despite the rtl layout.

Closed via #1316


Fix C2S VPN in parallel to S2S VPN

Description
PR #5375, introduced in version <IP_ADDRESS>, removed parameter %any of VPNs client-to-site (C2S) IPSec secrets:

previous structure:
<IP> %any : PSK "<PSK>"
structure after the change:
<IP> : PSK "<PSK>"

Because of that, when a VPN site-so-site (S2S) is created in parallel to a VPN C2S in the same network, the C2S will not handle any IP (%any) anymore and, as the network is being tunneled to the other VPN, the connection will be handled by the final peer. This way, when a VPN S2S is created in parallel to a VPN C2S in the same network, it is only possible to connect to the C2S with the S2S PSK.
As ACS is only able to implement a single C2S per network (ACS allows setting more than one IP of the network as VPN, however, only the first will be implemented) and every S2S has its own secret file, the secrets structure of C2S was changed to contain only the PSK (: PSK "<PSK>"). By doing that, StrongSwan will handle correctly C2S connections from any IP and still will use the correct PSK for S2S.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

How Has This Been Tested?
I created 3 networks (A, B, and C) and a VM in each network. In networks B and C I enabled the VPN. From VM in network A, I configured both VPNs and successfully connected to them with their respective PSK. Then, from B to C I established a S2S VPN. Without this change, when I was trying to connect again to C2S B with B PSK, the connection was refused; however, when tried to connect to C2S B with C PSK, the connection was successful. After the changes, I tried to connect again to C2S B with B PSK and the connection was successful.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 4624

(manually fired smoketest)

@GutoVeronezi
as you said, PR #5375 changed the structure from
<IP> %any : PSK "<PSK>"
to
<IP> : PSK "<PSK>"
With this PR, the structure is changed to
: PSK "<PSK>"
I have few questions

Have you ever tested the result by reverting #5375 ?
Since public IP is removed from the configuration in this PR, might it be potential security issue ?

@weizhouapache, yes, I have tested reverting #5375, and it works as well. The problem was that, by removing %any and enabling S2S, the request would be redirected to the final peer because the source (right) was not being handled by the VPN C2S. Removing the destination (left) makes the C2S handle the connection with the PSK, independent of the source.
Since only a single VPN C2S is configured for each network/VPC, I do not see how it could be a security issue.

@rohityadavcloud, and @weizhouapache, since the user's problem (https://github.com/apache/cloudstack/issues/4281#issue-684586236) was observed in 4.14.0, with another version of StrongSwan, and I could not reproduce it, the change was made in order to honor their comment. However, if we can confirm that it was only a problem with the StrongSwan version and #5375 change was not necessary, I think we could revert #5375.

@weizhouapache, yes, I have tested reverting #5375, and it works as well. The problem was that, by removing %any and enabling S2S, the request would be redirected to the final peer because the source (right) was not being handled by the VPN C2S. Removing the destination (left) makes the C2S handle the connection with the PSK, independent of the source.
Since only a single VPN C2S is configured for each network/VPC, I do not see how it could be a security issue.
@rohityadavcloud, and @weizhouapache, since the user's problem (#4281 (comment)) was observed in 4.14.0, with another version of StrongSwan, and I could not reproduce it, the change was made in order to honor their comment. However, if we can confirm that it was only a problem with the StrongSwan version and #5375 change was not necessary, I think we could revert #5375.

@GutoVeronezi
Thanks for your explanation.
I am ok with this pr or reverting #5375. We need to make sure both #6907 and #4281 are fixed.

@blueorangutan test

@rohityadavcloud a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@GutoVeronezi can you cherry-pick or rebase your PR to 4.17 branch and edit PR base branch to 4.17?

Ping @weizhouapache @harikrishna-patnala can you help review this?

Sorry, @harikrishna-patnala, I did not catch what you meant. There were no changes in the code, the branch was only rebased to 4.17.

@GutoVeronezi I'm just asking about the structure mentioned in the description.
structure after the change:
 : PSK ""
I think now it is only
: PSK ""
right!

Thanks @GutoVeronezi I’ll kick tests
@blueorangutan package

@rohityadavcloud a Jenkins job has been kicked to build packages. It will be bundled with  SystemVM template(s). I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_multiplication_x: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 4681

@blueorangutan test

@harikrishna-patnala, that part of the description is an introduction to the problem, explaining why it was happening. The changes I am doing in this PR is in the third paragraph. I made a little change to make it more explicit, thanks.

Thanks @GutoVeronezi for the change

Trillian test result (tid-5295)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 40046 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6907-t5295-kvm-centos7.zip
Smoke tests completed. 100 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL
Failure
467.85
test_vpc_redundant.py


Breaks with bash redirections

For example, the following bash will give a permissions fail:
sudo-prompt.exec("echo 'some text' > /Library/some-file.txt")

It's easily fixed by doing:
sudo-prompt.exec("bash -c \"echo 'some text' > /Library/some-file.txt\"")

Perhaps sudo-prompt should do this (bash -c) at the module level instead? String escaping may need a little bit of thought but should be ok.

The idea behind sudo-prompt is to prefix a command with "sudo" but show an os dialog if permissions would be necessary.
So, sudo-prompt at the moment would take your command above and run:
sudo echo 'some text' > /Library/some-file.txt

...but it would also take care of the os prompt along the way.
The issue at the moment if I understand correctly is that calling that command using sudo also fails:
 $ sudo echo 'some text' > /Library/some-file.txt
-bash: /Library/some-file.txt: Permission denied

The echo 'some text' is run using sudo, but the redirection to /Library is not.
The bash -c trick is a good idea. I am not sure how this would affect propagating command errors out of the bash shell. I will give it a try and see if we can make the changes.

Yup that's it.
After some basic testing, stdout and stderr both propagate up to the node callback exactly as expected.
If you like I can make a PR?

Thanks that would be great.

Does the exit code also propagate?

I presume so but I haven't tested that, I'll give it a test when I have a few spare minutes.

Just tried bash -c 'exit 0'; and it doesn't seem to propagate.

Did a bit more testing, this does propagate signals: exec "bash -c 'exec exit 0'"

The more I test this, perhaps it's best to leave it out of the lib, unless there's a straightforward way to do it. I'm not familiar enough with the intricacies of bash.

Thanks for trying, at least the bash -c is documented here for those that need to redirect sudo output.

Using -e flag on bash will exit immediately on error.
@davej Zero is the code for successful exists. If you want to "throw" an error you must exit with something different than zero.
http://unix.stackexchange.com/questions/15998/what-does-the-e-do-in-a-bash-shebang


Added CHAT file reader

Reads and converts .cha files to lists of script lines for use in SenseLab

we'd need a .cha file for that. not sure what a minimal file might look like. also this currently won't work as I didn't add pylangacq to the requirements because as discussed offline, my poetry is currently broken.

Codecov Report
Attention: Patch coverage is 0% with 26 lines in your changes missing coverage. Please review.

Project coverage is 62.79%. Comparing base (9b7209f) to head (0f7178a).
Report is 73 commits behind head on main.

Files with missing lines
Patch %
Lines

...enselab/utils/data_structures/talk_bank_helpers.py
0.00%
26 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #174      +/-   ##
==========================================
- Coverage   68.32%   62.79%   -5.53%
==========================================
  Files          95      112      +17
  Lines        3283     3497     +214
==========================================
- Hits         2243     2196      -47
- Misses       1040     1301     +261

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

we'd need a .cha file for that. not sure what a minimal file might look like. also this currently won't work as I didn't add pylangacq to the requirements because as discussed offline, my poetry is currently broken.

feel free to create a basic .cha file starting from some you find on CHILDES
I would recommend cloning the repo from scratch. I have tested the installation today and it works for me

I thought you found that the solution was to not use relative paths?

I thought you found that the solution was not to use relative paths?

If this is completed, I will merge it then!


Update Quick and Nimble with Swift 3 support

The swift-3.0 branch of Quick no longer exists which causes creating a new project to fail. Update the Carthage.private files to use the latest stable versions for Swift 3 support.

Can you update the Cartfile.private instead?

@gfontenot Cartfile.private is the file I updated. Unless I'm missing something.

Oh woops, I misread. Can you also run carthage update so that we update the Cartfile.resolved then?

@gfontenot updated to pin the release versions to actual releases instead of tags.

Oh woops, I misread. Can you also run carthage update so that we update the Cartfile.resolved then?

It looks like as of https://github.com/thoughtbot/ios-template/pull/7 we started ignoring the Cartfile.resolved file in the project directory

Oh, right, my bad again. I forgot about that. 👍  thanks for being patient with my idiocy!

Thanks @gfontenot!


Build Markdown Document?

Hello! Thanks for a great list. Would it be possible to build a markdown with checkboxes for easy copy-paste to git repos? I'd like to not maintain my own version for that :)

Hi @dakl ! Great idea - I was initially using markdown for the list, but couldn't get magicbook to work properly with it. I'll have a look at it again and will keep you updated.

I've added the markdown list as the README file. I'll go ahead and close this issue.

Awesome, thanks!


I have a Dreo Smart Pedestal Circulator Fan Model DR-HAOO3S

Works with fan speed. Oscilate Horizontally (on/off) only via scene or automation. Has a temperature sensor with temp.
Describe Your Problem:
There is no oscilate control in main fan control or any vertical oscillate control anywhere. Also NO TURBO fan speed.
I could not find a way to contact you like you asked if I had another fan that works or not. You don't have an email.

Thanks, I just updated the readme with your model. You should be able to control the oscillation if you go Device settings > Accessories > Fan > Settings. See updated readme images for a better visual representation. If you have the temperature sensor enabled it makes the layout a bit more complicated and it's not something we really have control over on the device side.
HomeKit doesn't support turbo mode or vertical oscillation so there aren't any plans to support those at this time.

Odd I didn’t see the ocillation but thanks.Note: Model DR-HAF003S (which I misspelled) but looks like you figured that out. However, this is a PEDESTAL fan not table fan.Sent from my iPhoneOn Jan 3, 2024, at 12:39 PM, Gavin Zyonse @.***> wrote:
Thanks, I just updated the readme with your model. You should be able to control the oscillation if you go Device settings > Accessories > Fan > Settings. See updated readme images for a better visual representation. If you have the temperature sensor enabled it makes the layout a bit more complicated and it's not something we really have control over on the device side.
HomeKit doesn't support turbo mode or vertical oscillation so there aren't any plans to support those at this time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Oscillation is still missing? Can you send a screenshot of the settings page I referenced above?

Yes it’s there, I just failed to find it the first time I asked.And this model (HAF003S) is actually a PEDESTAL fan, not a table fan.Sent from my iPhoneOn Jan 4, 2024, at 10:51 AM, Gavin Zyonse @.***> wrote:
Oscillation is still missing? Can you send a screenshot of the settings page I referenced above?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

@Grapplerone Can you let me know if it's still working with v3.2.5? I made some critical changes that might break it since the device isn't a traditional tower fan.

I just updated it and yes it’s working fine.Sent from my iPhoneOn Feb 5, 2024, at 8:10 PM, Gavin Zyonse @.***> wrote:
@Grapplerone Can you let me know if it's still working with v3.2.5? I made some critical changes that might break it since the device isn't a traditional tower fan.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


PostgreSQL table DDL generation - missed tablespace

dBeaver 4.3.0 PostgreSQL9.6 / 10.1
Tablespace information missed in the output script while DDL generarion.
Stesp to reproduce
CREATE some TABLESPACE. Let it be arch_data
CREATE TABLE sy_test
(
F1 int
)
WITH (
OIDS = FALSE
)
TABLESPACE arch_data;
Right click on sy_test chose generate SQL->DDL
tablespace info is missed in the output script

Yep, thanks for noticing.
See fix in the next version.


Fix group key type and move GroupLimit to GroupedSearchParameters

I had to painfully discover this morning that the API may also send ints back in the GroupKey crashing the JSON deserialization so I changed the type to IReadOnlyList<object>.
I also took the liberty to move the GroupLimit parameter to the GroupedSearchParameters; I'd argue similarly to the GroupBy change, that this should not be breaking, since the parameter had no effect prior to 4.7.0 anyway and after 4.7.0 has no effect unless used with GroupedSearchParameters.

@geisterfurz007 no problem, C# really could use sum types in situations like this. :)
I'll have to think about the change from IReadOnlyList<string> to IReadOnlyList<object> since I really want to avoid using the object type if I can, I'm not sure if it would be better to create a custom converter and always convert it to a string, what do you think?
Here is an example of a converter in the project.
https://github.com/DAXGRID/typesense-dotnet/blob/master/src/Typesense/Converter/MatchedTokenConverter.cs
I approve of the GroupLimit change.

Fair argument; done!

Looks great, thanks! :) I'll merge it in and make a new patch release.

https://github.com/DAXGRID/typesense-dotnet/releases/tag/4.7.1


set-super does not verify validity of arguments

I accidentally set id and version to something random, and it let me do that without complaint, but gave a 404 on access (unsurprisingly then).

Thanks for highlighting this. There's functionality that needs to be implemented (as part of the goal to implement multiple new and refactored datalad-catalog commands, see https://github.com/datalad/datalad-catalog/issues/245#issuecomment-1477051454) to report on the existence (or not) of a particular metadata record with id and version in a catalog. This would be a useful place to make use of that functionality.

Closed by https://github.com/datalad/datalad-catalog/pull/309


Extension documentation

Hi, Could You add to note information about what is need n=in model in case of using --model option.
I had model previously generated with artisan.

So you don't want to generate model, and you dont know what to add to model to make it work, right?

Yes, You right.


quick edit

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit b21cc63d119381726e363bbddbbb5f330e6db1da
https://deploy-preview-7561--docsdocker.netlify.com


CI: Fix Broken Tests

Monika Pull Request (PR)
What feature/issue does this PR add
Fix broken tests when releasing Monika

https://github.com/hyperjumptech/monika/actions/runs/6009497869/job/16299052049
https://github.com/hyperjumptech/monika/actions/runs/6009497871/job/16299051850
https://github.com/hyperjumptech/monika/actions/runs/6009497865/job/16299052069

How did you implement / how did you fix it
Set environment variable NODE_OPTIONS to '--no-experimental-fetch' when running test
How to test
Run NODE_OPTIONS='--no-experimental-fetch' npm test

BTW, instead of using NODE_OPTIONS, how about changing the implementation of fetch to axios? because we also need to add the NODE_OPTIONS when running the npm start, otherwise it will show error for parts that using fetch
I implemented that in the mailgun PR:

16d3418
9a32ec8

This is a workaround for this issue on MSW. I can't change the implementation inside the MSW library.
It won't happen if you run npm start because MSW only used when running test.

BTW, instead of using NODE_OPTIONS, how about changing the implementation of fetch to axios? because we also need to add the NODE_OPTIONS when running the npm start, otherwise it will show error for parts that using fetch
I implemented that in the mailgun PR:

16d3418
9a32ec8

This is a workaround for this issue on MSW. I can't change the implementation inside the MSW library.
It won't happen if you run npm start because MSW only used when running test.

No, I mean change the implementation in the monika, not the msw. Since ther is only 3 places that use fetch

BTW, instead of using NODE_OPTIONS, how about changing the implementation of fetch to axios? because we also need to add the NODE_OPTIONS when running the npm start, otherwise it will show error for parts that using fetch
I implemented that in the mailgun PR:

16d3418
9a32ec8

This is a workaround for this issue on MSW. I can't change the implementation inside the MSW library.
It won't happen if you run npm start because MSW only used when running test.

No, I mean change the implementation in the monika, not the msw. Since ther is only 3 places that use fetch
And yes, I am not talking about the test, but when developing. It will show error when npm start using config that uses fetch such as pagerduty, mailgun.

Ok. I got your point.

This PR only fix the broken release pipeline
There is a problem with fetch when run the npm start command, you should create an issue for this
We're in the middle of replacing Axios with fetch, changing fetch with Axios is going backward

Could we agree on this?

BTW, instead of using NODE_OPTIONS, how about changing the implementation of fetch to axios? because we also need to add the NODE_OPTIONS when running the npm start, otherwise it will show error for parts that using fetch
I implemented that in the mailgun PR:

16d3418
9a32ec8

This is a workaround for this issue on MSW. I can't change the implementation inside the MSW library.
It won't happen if you run npm start because MSW only used when running test.

No, I mean change the implementation in the monika, not the msw. Since ther is only 3 places that use fetch
And yes, I am not talking about the test, but when developing. It will show error when npm start using config that uses fetch such as pagerduty, mailgun.

Ok. I got your point.

This PR only fix the broken release pipeline
There is a problem with fetch when run the npm start command, you should create an issue for this
We're in the middle of replacing Axios with fetch, changing fetch with Axios is going backward

Could we agree on this?

I could agree for now, just looks a little dirty since it's a workaround and need to add NODE_OPTION for every npm test command

BTW, instead of using NODE_OPTIONS, how about changing the implementation of fetch to axios? because we also need to add the NODE_OPTIONS when running the npm start, otherwise it will show error for parts that using fetch
I implemented that in the mailgun PR:

16d3418
9a32ec8

This is a workaround for this issue on MSW. I can't change the implementation inside the MSW library.
It won't happen if you run npm start because MSW only used when running test.

No, I mean change the implementation in the monika, not the msw. Since ther is only 3 places that use fetch
And yes, I am not talking about the test, but when developing. It will show error when npm start using config that uses fetch such as pagerduty, mailgun.

Ok. I got your point.

This PR only fix the broken release pipeline
There is a problem with fetch when run the npm start command, you should create an issue for this
We're in the middle of replacing Axios with fetch, changing fetch with Axios is going backward

Could we agree on this?

I could agree for now. It's just looks a little dirty since it's a workaround and need to add NODE_OPTION for every npm test command

Ok. So, I close this PR because it will be fixed by PR https://github.com/hyperjumptech/monika/pull/1105


Couldn't set up Serenity due to uncompatible .NET Core versions

I'm following this document to install Serenity:
https://serenity.is/Docs/getting_started/instaling-serene-aspnet-core-version-with-serin
I've tried this on my Windows 10 machine and also Linux (Ubuntu 18.04).
Document says we need to install .NET Core 2.0 SDK which is end of the life. We should use 2.1, i guess.
However, after installed serin with npm and run serin, I got this error:

When I look at .csproj file, I see that project targeting 3.1. But document says 2? Anyway I changed this to 2.1

Then I run 'dotnet restore', another error comes up:

I started thinking Serenity has terrible documentation and led us to wrong ways.
Well .. I am really tired. When I test Serene at last year, just download it on nuget and that's it.
By the way documents doesnt say but you have to install VS2019. Not VS2017 or 2015. The page I have followed has an SS may confuse people. In SS it says MVC but in the page it says .NET Core.
Serene MVC seems obsolete and says we should prefer .NET Core.

Serenity uses .NET Core 3.1, that's what you should install as shown in error message

Documentation should be updated though

If you are so tired and think Serenity leds you wrong ways, take a break, find a better tool etc.

Yes it is. That's why I changed my mind. I'll go forward with Django. Besides, I like to do everything manually.
I don't think that I'll ever never get into serenity and .net


React Native Support

Hey,
I've gotten turbine running on React Native with a few minor amends but I'm waiting on your latest changes described in another issue to send it as a pull request.
Have you idea when you're looking to push it to GitHub? I'm using it in a production app and I'm eager to help out where needed.

Hey Luke,That's great!
We're probably going to push new stuff early next week.
I think you can create a PR right away if you have it publishable.

@urbanappetite Could you please submit the PR, so we can get it working for us?


AWS SDK seems to have failed to poison S3 connections after today's outage

Describe the bug
At @MaterializeInc we run a number of clusterd processes that continually read and write from S3. (We make a streaming database that's in the business of reading data from S3, transforming it, and writing it back to S3.)
During today's AWS outage, these clusterd processes all experienced an outage. Almost all of the clusterd processes recovered, except for two that continually produced error messages like the following:
clusterd no loader was set :-/
clusterd {"timestamp":"2023-06-14T02:21:42.407205Z","level":"INFO","fields":{"message":"external operation rollup::set failed, retrying in 16s: indeterminate: request has timed out"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-14T02:21:42.407274Z","level":"INFO","fields":{"message":"external operation rollup::set failed, retrying in 16s: indeterminate: request has timed out"},"target":"mz_persist_client::internal::machine"}
clusterd no loader was set :-/
clusterd no loader was set :-/
clusterd {"timestamp":"2023-06-14T02:21:42.407345Z","level":"INFO","fields":{"message":"external operation rollup::set failed, retrying in 16s: indeterminate: request has timed out"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-14T02:21:42.407427Z","level":"INFO","fields":{"message":"external operation rollup::set failed, retrying in 16s: indeterminate: request has timed out"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-14T02:21:42.409267Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-14T02:21:42.409623Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 16s: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-14T02:21:42.413165Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-14T02:21:42.413439Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 16s: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-14T02:21:42.416520Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-14T02:21:42.416801Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 16s: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-14T02:21:42.473353Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-14T02:21:42.473688Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 16s: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd no loader was set :-/
clusterd {"timestamp":"2023-06-14T02:21:42.475366Z","level":"INFO","fields":{"message":"external operation rollup::set failed, retrying in 16s: indeterminate: request has timed out"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-14T02:21:42.475470Z","level":"INFO","fields":{"message":"external operation rollup::set failed, retrying in 16s: indeterminate: request has timed out"},"target":"mz_persist_client::internal::machine"}
clusterd no loader was set :-/
clusterd no loader was set :-/
clusterd {"timestamp":"2023-06-14T02:21:42.475532Z","level":"INFO","fields":{"message":"external operation rollup::set failed, retrying in 16s: indeterminate: request has timed out"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-14T02:21:42.476895Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-14T02:21:42.477315Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 16s: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-14T02:21:42.480570Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-14T02:21:42.480894Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 16s: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}

AIUI, rollup::set is attempting to write to S3, while s3 get meta is attempting to read from S3. The following error message (request has timed out) or (failed to construct request) comes straight from the AWS SDK, AFAICT.
Expected Behavior
We expected our S3 reads/writes to eventually succeed on retry.
Current Behavior
The S3 reads/writes continued failing forever.
We validated that the two affected containers did in fact have access to S3—logging in to the containers and manually issuing S3 requests was successful at the time shown in the S3 logs.
Reproduction Steps
So sorry, but we have no reproduction of this. We run chaos tests in our CI that interrupt network connections but we've never seen anything like this. I think it's unlikely we'll see this again until another wide AWS outage.
I wonder if it's something specific about interrupting the IAM connections in the way that the AWS outage did. We don't test that chaos extensively in our CI.
Possible Solution
The reason I wanted to file this issue is because of this println that we're seeing in the output:
https://github.com/awslabs/smithy-rs/blob/312d190535b1c77625d662d18313b90af64cb448/rust-runtime/aws-smithy-http/src/connection.rs#L85
This looks like a stray debugging println. It was added in https://github.com/awslabs/smithy-rs/pull/2445. I'm just spitballing, but I'm wondering if this println is related to the issue. Perhaps connections in this process weren't getting poisoned properly because the connection metadata wasn't available?
I've never seen this println in our logs while debugging before. Unfortunately I can't say that we've truly never seen this log on the unaffected processes because as a println rather than a tracing log it doesn't get picked up by our logging infrastructure. It's possible that this println is actually a normal occurrence when there are S3 connectivity issues, and not indicative of a failure to poison broken connections.
If nothing else, seems like the debugging println ought to be removed!
 We see STS errors around 4pm ET (as expected) that continue for a bit and then clear right up:
clusterd {"timestamp":"2023-06-13T20:09:02.084937Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:02.774907Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:02.802298Z","level":"WARN","fields":{"message":"STS returned an error assuming web identity role","error":"service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:02 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }))"},"target":"aws_config::web_identity_token","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:02.802611Z","level":"WARN","fields":{"message":"provider failed to provide credentials","provider":"WebIdentityToken","error":"an error occurred while loading credentials: service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ProviderError(ProviderError { source: ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:02 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }) }))"},"target":"aws_config::meta::credentials::chain","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:02.815222Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:03.383098Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.116729Z","level":"WARN","fields":{"message":"STS returned an error assuming web identity role","error":"service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }))"},"target":"aws_config::web_identity_token","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.117057Z","level":"WARN","fields":{"message":"provider failed to provide credentials","provider":"WebIdentityToken","error":"an error occurred while loading credentials: service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ProviderError(ProviderError { source: ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }) }))"},"target":"aws_config::meta::credentials::chain","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.138912Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.228762Z","level":"WARN","fields":{"message":"STS returned an error assuming web identity role","error":"service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:04 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }))"},"target":"aws_config::web_identity_token","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.229078Z","level":"WARN","fields":{"message":"provider failed to provide credentials","provider":"WebIdentityToken","error":"an error occurred while loading credentials: service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ProviderError(ProviderError { source: ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:04 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }) }))"},"target":"aws_config::meta::credentials::chain","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.229290Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 32ms: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-13T20:09:04.266399Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.290968Z","level":"WARN","fields":{"message":"STS returned an error assuming web identity role","error":"service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }))"},"target":"aws_config::web_identity_token","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.291272Z","level":"WARN","fields":{"message":"provider failed to provide credentials","provider":"WebIdentityToken","error":"an error occurred while loading credentials: service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ProviderError(ProviderError { source: ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }) }))"},"target":"aws_config::meta::credentials::chain","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.291716Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 64ms: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-13T20:09:04.364927Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.394375Z","level":"WARN","fields":{"message":"STS returned an error assuming web identity role","error":"service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }))"},"target":"aws_config::web_identity_token","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.394685Z","level":"WARN","fields":{"message":"provider failed to provide credentials","provider":"WebIdentityToken","error":"an error occurred while loading credentials: service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ProviderError(ProviderError { source: ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }) }))"},"target":"aws_config::meta::credentials::chain","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.394893Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 128ms: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-13T20:09:04.533256Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.560945Z","level":"WARN","fields":{"message":"STS returned an error assuming web identity role","error":"service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }))"},"target":"aws_config::web_identity_token","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.561244Z","level":"WARN","fields":{"message":"provider failed to provide credentials","provider":"WebIdentityToken","error":"an error occurred while loading credentials: service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ProviderError(ProviderError { source: ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }) }))"},"target":"aws_config::meta::credentials::chain","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.561451Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 256ms: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-13T20:09:04.813752Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.840466Z","level":"WARN","fields":{"message":"STS returned an error assuming web identity role","error":"service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }))"},"target":"aws_config::web_identity_token","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.840796Z","level":"WARN","fields":{"message":"provider failed to provide credentials","provider":"WebIdentityToken","error":"an error occurred while loading credentials: service error: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements: InvalidIdentityTokenException: Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements (ProviderError(ProviderError { source: ServiceError(ServiceError { source: InvalidIdentityTokenException(InvalidIdentityTokenException { message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), meta: ErrorMetadata { code: Some(\"InvalidIdentityToken\"), message: Some(\"Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements\"), extras: Some({\"aws_request_id\": \" 00000000-0000-0000-0000-000000000000\"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {\"x-amzn-requestid\": \" 00000000-0000-0000-0000-000000000000\", \"content-type\": \"text/xml\", \"content-length\": \"390\", \"date\": \"Tue, 13 Jun 2023 20:09:03 GMT\", \"connection\": \"close\"}, body: SdkBody { inner: Once(Some(b\"<ErrorResponse xmlns=\\\"https://sts.amazonaws.com/doc/2011-06-15/\\\">\\n  <Error>\\n    <Type>Sender</Type>\\n    InvalidIdentityToken\\n    <Message>Couldn't retrieve verification key from your identity provider,  please reference AssumeRoleWithWebIdentity documentation for requirements</Message>\\n  </Error>\\n  <RequestId> 00000000-0000-0000-0000-000000000000</RequestId>\\n</ErrorResponse>\\n\")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag, poisoned: false, .. }) } }) }))"},"target":"aws_config::meta::credentials::chain","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:04.841011Z","level":"INFO","fields":{"message":"external operation fetch_batch::get failed, retrying in 512ms: indeterminate: s3 get meta err: failed to construct request"},"target":"mz_persist_client::internal::machine"}
clusterd {"timestamp":"2023-06-13T20:09:05.324239Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T20:09:05.363141Z","level":"INFO","fields":{"message":"credentials cache miss occurred; added new AWS credentials (took 43.184745ms)"},"target":"aws_credential_types::cache::lazy_caching","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T21:09:29.655483Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T21:09:29.691265Z","level":"INFO","fields":{"message":"credentials cache miss occurred; added new AWS credentials (took 39.945721ms)"},"target":"aws_credential_types::cache::lazy_caching","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T22:09:39.545786Z","level":"INFO","fields":{"message":"credentials cache returned CredentialsNotLoaded, ignoring"},"target":"aws_http::auth","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T22:09:39.714404Z","level":"INFO","fields":{"message":"credentials cache miss occurred; added new AWS credentials (took 172.900715ms)"},"target":"aws_credential_types::cache::lazy_caching","span":{"name":"lazy_load_credentials"},"spans":[{"name":"lazy_load_credentials"}]}
clusterd {"timestamp":"2023-06-13T23:07:49.226265Z","level":"INFO","fields":{"message":"poisoning connection: SmithyConnection { is_proxied: false, remote_addr: Some(<IP_ADDRESS>:443) }"},"target":"aws_smithy_client::poison"}
clusterd {"timestamp":"2023-06-13T23:07:49.226334Z","level":"INFO","fields":{"message":"smithy connection was poisoned"},"target":"aws_smithy_http::connection"}

Hi @benesch , thank you for reporting this issue & providing an analysis in the description. We'll add this to our backlog. @rcoh may have some insights into this. It's conceivable that the outage use case may have exposed a code execution path that was not originally considered when PR2445 was created. In the meantime, if you happen to discover a simpler reproduction step, kindly share it with us.

Are you running with non-stock connectors of some kind? That could cause connection metadata to fail to work 🤔

Are you running with non-stock connectors of some kind? That could cause connection metadata to fail to work 🤔

Not as far as I know! This is our configuration: https://github.com/MaterializeInc/materialize/blob/bfbebe04a7d181f1bac91f01785309a52cf2de34/src/persist/src/s3.rs#L111-L180

In the meantime, if you happen to discover a simpler reproduction step, kindly share it with us.

Will do, but I'm afraid it'll be pretty unlikely that we do. To be honest, if the only outcome of this issue is the removal of the debugging println!, that's pretty much what I expect! I just figured I'd file in case it sparked insight for someone—e.g. about some multi-threaded credential connection cache or something like that.

coming back here as I prepare to close this ticket—it seems like in most of your pods, connection poisoning worked as intended and through out the bad connections but in one pod maybe a race condition of some kind caused us to fail to get the poisoning to work. Since no loader was set, it means we never actually made it to even trying to send the request with Hyper—maybe the timeout hit during waiting for a retry or poll_ready on Hyper was pending?
In any case, the println has been replaced with a debug

Since no loader was set, it means we never actually made it to even trying to send the request with Hyper—maybe the timeout hit during waiting for a retry or poll_ready on Hyper was pending?

Yeah, could be. In any case, thanks for removing that println!!


Implementation of cryptographic functions

As given in the specification of builtin reductions of Plutus Core, Plutus Core features sha2_256 and sha3_256 as built-in functions.
I believe we will have to implement these in K since we want to be able to reason about them. This should not be hard to do. If you have any questions or concerns about this, let us carry out the discussion here so everyone is on the same page.

For now, we will be using the hooks.


♿ AVT3 ♿ Date picker - User can't select date

User tested with latest version of JAWS 2018, Windows 7, Chrome latest version
User cannot select date and must entered date manually.
"It is a problem when the user wants to know which day of the week or month is the particular date"

The date picker should also have a fully functioning validation alert so it can be tested with a fully tested with a screen reader. See WCAG Guidelines 3.3

keyboard affordances are there but they are undocumented so discoverability is clumsy. 👍


Edit MDE URLs - Microsoft Support

Hello team, this is Adel from Microsoft Support.
Please edit the Commercial URLs sheet to include the following for Linux:
•	go.microsoft.com
•	definitionupdates.microsoft.com
These are needed for engine V2 signature updates when behavior monitoring is enabled.
We're getting a lot of cases regarding this.
Thank you!

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

ID: 28a4997c-0029-be57-24a3-7aa10dadda53
Version Independent ID: 98227b02-39e2-03f6-c947-23317abb818f
Content: Configure device proxy and Internet connection settings
Content Source: microsoft-365/security/defender-endpoint/configure-proxy-internet.md
Product: m365-security
Technology: mde
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@adelaldabbas Thank you for your feedback. The Sheet is hosted in a different site, I will be working with the author to add the URL's to the sheet.
Thanks
Sri

@mjcaparas Please help. Email sent. Thanks

Hello @msbemba ,
Just checking the status here, are you planning to implement the change?
Thank you,
Adel

This has been added row 76 & 77 in the MDE URLs tab


Get s2CellId from ApiResponse object

How to get s2CellId from ApiResponse object.
my response.subresponses is :
[ mapCells[0] {    s2CellId:<PHONE_NUMBER>525216768     currentTimestampMs:<PHONE_NUMBER>119  }  status: .Success ]

The library has been updated quite a bit and you should be all set now, let me know if you're still having any issues.

@lsapan I'm curious about the same thing. How do I interact with the GeneratedMessage that is returned from the protocol buffers object?

You need to cast the subresponse using as!. If you send me your request I can write up an example.

I'm just using the current example and trying to parse the getMapObjects resposne

@nbwar
let r = response.subresponses[0] as! Pogoprotos.Networking.Responses.GetMapObjectsResponse
let cell = r.mapCells[0]
print(cell.nearbyPokemons)
print(cell.wildPokemons)
print(cell.catchablePokemons)

Exactly what i was looking for. thanks!!

No problem!


Page gets re-rendered while clicking links.

The dashboard does not works like SPA(Single Page Application) for every links the page gets reload and then contents are rendered to the DOM.

@ani4aniket this is due to the use of anchor tag in the code , we can change it to the link from the react-router-dom

@aryamanpuri Yes, I am working on it.

Created a PR for the above-mentioned enhancement with replacing the anchor tag with Link tag from 'react-router-dom'. Also for jumping to various routes used this.props.history.push(<route to push>) with the help of withRouter from 'react-router-dom' instead of Setting.openLink().
https://github.com/casbin/casbin-dashboard/pull/5/commits/d1dafd70da736987204b39e417021b7f50a7c835


Device heath attestation - typo

Within the Device health attestation section there is a typo for the word health - it currently reads heath
From here: https://docs.microsoft.com/en-nz/windows/whats-new/whats-new-windows-10-version-1507-and-1511#trusted-platform-module

Thank you for catching the typo.  It has been fixed.


Calendar View Should Display Month as Header

Pretty self-explanatory -- I think that the calendar view should display the month in a header bar (eg right above the days of the week), and should offer an option to switch months (like PCR does).
Great work, by the way! I'm very impressed.

also, is there a way to use end date only (w/o range)?

Thank you for the compliment and suggestions!
As for the first one, I definitely think that's a good idea, but it will take some time to do.
For the second suggestion, I presume you mean having the calendar view have boxes only on the end dates. In that case, it is currently not possible, but should be fairly easy to implement when I have time.


Support GenesisQC As HighQC in Incoming Timeout Messages

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

feature/pos-syncing-and-steady-state

PR #936

PR #935

PR #937

PR #938

PR #939

PR #940   👈

This stack of pull requests is managed by Graphite.


Write a Python program to print character of an ascii value

Description
Write a Python program to print character of an ascii value
ASCII value is the numeric representation of a character. For example, the ASCII value of the character 'A' is 65. The ASCII value of the character 'a' is 97. The ASCII value of the character '0' is 48. The ASCII value of the character ' ' is 32.
Input  : 65
Output : A

How to contribute

Save the solution in print-character-of-an-ascii-value.py file
Add print-character-of-an-ascii-value.py file in print-character-of-an-ascii-value folder

!assign


http trigger compatible to lambda function url

see https://github.com/refunc/refunc/commit/cedc3b1bea6d807f19a8e18e8f4a6960602f65ec


Sync fork

In an effort to get rid of the deprecated usages of ::set-output (Trello ticket), this is the sync to the original repo where it has been fixed already.
I'm adding an info to the README as well on why we went for the fork (see also slack discussion).

Test pipeline seems to fail because of this being a fork. At least there's no change to the original repo that could cause it.

Teardown for a test PR in push-api repo worked well (CircleCI run). Could still be we have weird edge cases but normal use-case seems to be fine. So I'd merge it soon.

I mainly checked the entrypoint.sh for issues as that's the executed code.
You have a very good point though. There's a few third-party-dependencies in the GitHub workflows that run in this repo if we work on the code (e.g. the linter you mentioned; so not if the actual action gets executed). I'll just delete them as we indeed don't need them. That should still allow for easy updating in the future.
But overall it's indeed a big repo now for the simple use case we have. I'd still suggest to not manually maintain this in the future - at least at this point.


ID is always added to output even input message doesn't have id

Describe the bug
When a message string converted from JSON to XML or XML to JSON, ID is always added to output even input message doesn't have id. I don't see anywhere in FHIR specification to mention that ID is mandatory.
To Reproduce

Create a JSON/XML message string without ID string
Parse the message with hapi library
Output contains ID tag

Expected behavior
Output should not contain ID tag
Environment (please complete the following information):

HAPI FHIR Version -2.5
all os
Additional context
It looks like ID is always extracted from fullURL based on following code:
https://github.com/jamesagnew/hapi-fhir/blob/a952663dc323c727436c4218f70bd13f8421604f/hapi-fhir-base/src/main/java/ca/uhn/fhir/parser/BaseParser.java#L697

I'm not sure I follow- Could you please provide a code snippet which demonstrates this issue?

import odl.ca.uhn.fhir_2_5.context.FhirContext;
import odl.org.hl7.fhir_2_5.dstu3.model.Bundle;
import odl.ca.uhn.fhir_2_5.parser.IParser;

public class HapiSetIdTest {

	public static void main(String[] args) throws Exception {
		FhirContext ctxDstu2 = FhirContext.forDstu3();

		String input = "<Bundle xmlns=\"http://hl7.org/fhir\"><id value=\"bundle-example\" /><entry><fullUrl value=\"https://example.com/base/MedicationRequest/3123\"/>"
				+ "<resource><MedicationRequest></MedicationRequest></resource></entry></Bundle>";
		IParser parser = ctxDstu2.newXmlParser();

		Bundle output = (Bundle) parser.parseResource(input);

		System.out.println(parser.encodeResourceToString(output));

	}

}

Question is why output has id tag  <id value="3123"></id> while input doesn't have?
Output
<Bundle xmlns="http://hl7.org/fhir"><id value="bundle-example"></id><entry><fullUrl value="https://example.com/base/MedicationRequest/3123"></fullUrl><resource><MedicationRequest xmlns="http://hl7.org/fhir"><id value="3123"></id></MedicationRequest></resource></entry></Bundle>

Input
<Bundle xmlns="http://hl7.org/fhir"><id value="bundle-example"/><entry><fullUrl value="https://example.com/base/MedicationRequest/3123"/><resource><MedicationRequest></MedicationRequest></resource></entry></Bundle>

That 3123 comes from the fullUrl tag. It is by design, since that is the purpose of that field.

Thanks, when I look at FHIR spec identity is still optional (0..1) - https://www.hl7.org/fhir/medicationrequest-definitions.html#MedicationRequest.identifier

FYI: MedicationRequest.identifier is different from MedicationRequest.id
The id field is optional too, but certainly in this specific use case, if you're parsing a Bundle that provides an ID via the fullUrl field, I believe it's the right behaviour to respect it. Can you not just clear it if manually after parsing you need different behaviour?


Pessimistic deletes do not remove entity from entity collection

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Configure an Entity with all dispatcher options set to pessimistic:

    entityDispatcherOptions: {
      optimisticAdd: false,
      optimisticDelete: false,
      optimisticUpdate: false,
    },

Call the delete function on the entityService:

    this.locationsEntityService.delete(location.id);

Observe that the network request is made to delete the entity.
Observe that the entity still remains in the collection.

Any log messages given by the failure
Two actions are dispatched when using the delete function on the EntityService:
{
  type: '[Location] ngrx-data/save/delete-one',
  entityName: 'Location',
  op: 'ngrx-data/save/delete-one',
  payload: 'b2632b51-ab9d-4e79-bf0d-9a622f31be62'
}

{
  type: '[Location] ngrx-data/save/delete-one/success',
  entityName: 'Location',
  op: 'ngrx-data/save/delete-one/success',
  payload: null
}

Expected/desired behavior
On a successful delete from the server, the entity should be removed from the collection.
OS and Version?
Windows 10
Versions

1.0.0-beta.9

Mention any other details that might be useful
My assumption is that the second action listed above should have a payload containing the id of the entity.
We have also implemented a custom DataService. Our delete function there looks like this:
  delete(id: string): Observable<null> {
    return this.apiUrl$.pipe(exhaustMap(apiUrl => this.httpClient.delete(`${apiUrl}(${id})`)), map(response => null));
  }

The Observable return on the interface stuck out as odd to us. It seems like it should be returning the id of the entity so that it can be dispatched as part of the success action.
Are we making any bad assumptions with our expected behavior?

Thanks! We'll be in touch soon.

  I missed this one and didn't have a test for it.
I will do something about this tomorrow.
TBH, I'm not fond of the current protocol because it doesn't support undo for optimistic failures. So I may try to address that deficiency at the same time.
I'll let you know.
Thanks for catching this.


[1.18.2] Inconsistent Recipes

Sieve has different Percentages of several items in REI.

I did not change the chance, but if I do the problem still remains.

I made a change that might fix this. Can you give 0.1.7 a try and see if the issue persists?

I can confirm, it was fixed.

I think I found the source of the bug:
If multiple sieving recipes for the same item show up in REI, the tooltip shows the chance of the last recipe rendered.
For example: The prismarine sieving recipe in Sky FABRICation 3:
Its chances should be:

5% chance for the Iron Mesh,
30% chance for the Diamond Mesh,
40% chance for the Netherite Mesh.

Window maximized, shows 3 recipes with Iron Mesh one being the last one:

Window minimized, shows only a Netherite Mesh sieving recipe:


Listview jagging on fast scroll

I have successfully implemented this drag and drop in Xamarin.Forms listview but when I scroll quite fast (than normal slow scroll), it is jaggin/ startling. But if I use the listiew normally without this drag & drop (after removing it), the listview scrolls fine on fast scroll like I did previously. There seems to be clear problem with this drag & drop implementation I believe..
This occurs in all different android versions I tried
Can anyone assist?

Jaggin/ startling means.. in other words the whole listview shakes

Hello,
I'm not sure if you're still in need, but I've had the same issues and it was bugging me since.
I've found the fix though (atleast, it works for me)
Original code:
anim.SetDuration(100);
anim.Start();
return correctedPosition;
However, it never stops. Replace it with:
anim.SetDuration(100);
anim.Start();
anim.End();
return correctedPosition;
Enjoy

Oh really..! Thanks for posting the fix, others may get this error..

Hi there guys, for those of you who experience issues with ListView with your swipe very fast while dragging which results in 2 items being on top of each other, Wilcoo1's fix also resolve that issue. Might be worth making a pull request.