C# glue error (not binding related, macOS deprecation error)

Godot version:
Latest, last merge: https://github.com/godotengine/godot/pull/37554
OS/device including version:
2017 MacBook Pro, macOS Catalina, 10.15.4
Issue description:
macOS related deprecation error:
[ 27%] Compiling ==> modules/mono/utils/osx_utils.cpp
modules/mono/utils/osx_utils.cpp:44:20: error: 'LSFindApplicationForInfo' is deprecated: first deprecated in macOS 10.10 - Use LSCopyApplicationURLsForBundleIdentifier instead.
      [-Werror,-Wdeprecated-declarations]
        OSStatus result = LSFindApplicationForInfo(kLSUnknownCreator, bundle_id, nullptr, nullptr, &app_url);
                          ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Headers/LSInfoDeprecated.h:765:1: note:
      'LSFindApplicationForInfo' has been explicitly marked deprecated here
LSFindApplicationForInfo(
^
1 error generated.
scons: *** [modules/mono/utils/osx_utils.osx.tools.64.o] Error 1
scons: building terminated because of errors.

Steps to reproduce:
(Probably) get a macOS with version 10.10 or up and run this:
scons p=osx tools=yes module_mono_enabled=yes mono_glue=no

Minimal reproduction project:
Doesn't need one.

This was fixed by 5d54c015b2dd0a26237c00788be25b3da4cfe3dd.

Fixed by #40261.


Update material template link, version bump

Maybe it's just me, but I find it odd to PR the version changes. That's what the npm version (major|minor|patch) && npm publish is for IMO


[COLLECTIONS-774] - Bump version maven-antrun-plugin 3.0.0

Coverage remained the same at 90.117% when pulling 7021532fab23590b6323e12f7d5ceda5ab47a8a7 on arturobernalg:feature/COLLECTIONS-774 into 979d2727ae8df615292524b0b0ae0ff03ab261a9 on apache:master.

Coverage remained the same at 90.117% when pulling 7021532fab23590b6323e12f7d5ceda5ab47a8a7 on arturobernalg:feature/COLLECTIONS-774 into 979d2727ae8df615292524b0b0ae0ff03ab261a9 on apache:master.

p.s. @arturobernalg good to see you around here again! :wave: I thought it was one of the PR's generated by dependabot :smile:

Hi @kinow
i'm glad to contribute.

Duplicates #170


[XR] set _framebuffer even when "falsy"

This prevented the WebXR Emulator from working.

I can not get why.... :-)

You and me both. We either check somewhere for "null" instead of "false" (which i couldn't find), or the emulator itself expects something that I simply can't explain.
The emulator works locally when this is set. that's all I can say ;-)


discord: 0.0.17 -> 0.0.18

Description of changes
New Discord update on x86-64 Linux.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

 Discord is refusing to launch without updating.

@lincolnauster That's already mostly automated, forgot to trigger it though. Thanks for the reminder (^:


Add GodSoul To Modlinks

If you have any questions or need to message me: Nexade#4250. (This is my first time so I have no idea what I do or don't need to do)

What is this supposed to do? Increase the enemy count and remove healing? I had random beams in one room and a geo chest in another but not much else. Also, I'd recommend using the actual preloading system instead of loading them after someone loads a save.

~What is this supposed to do? Increase the enemy count and remove healing? I had random beams in one room and a geo chest in another but not much else.~ Nevermind, I found some of the area effects. A list or something in the README would be really nice though. Also, I'd recommend using the actual preloading system instead of loading them after someone loads a save.

Sorry about all the weird inconveniences, it's my first time. Do I need to change anything before the mod is added to the API?

Your SHA256 is off, but the rest seems fine. You don't need to change anything but using your own preloading system is going to be more error prone and there's still a lot of exceptions being thrown when I use the mod. I can merge it anyways though.

Thanks! I probably won't change anything, I'll just take on the feedback for my next project. :)

You do need to change the SHA256 in this PR though, it's invalid.

... and how do I do that? I went to the GodSoul github page and went to 'commit' the zip file. Then I copied the last part of the url which looked like the other SHA256 things. As you've probably found out by now I have no idea what I'm doing

Put the zip through something like this or right click -> CRC-1 -> SHA256 if you have 7-Zip.

I think I did it. I've just edited my edit, but if it doesn't work here it is: AC7D27A1F9E286C4F533BDDCFAFACC4971608FDBF2B06DB6E5586839C9E82DB7

Also, just asking, if I update my mod in the future, will I need to change anything here, or will it not matter?

If you update your mod in the future, you need to PR a change to the SHA1, download link (to the newest release), and the version (so it gets updated for the users).

Thanks :)


redis-plus-plus pkgconfig doesn't match actual install location

Description
When installing redis++ through the normal build instructions, a redis++.pc file is created. Sometimes, CMake decides to install it's libraries into lib64 rather than the usual lib directory, but the redis++.pc file will still point to the lib directory. Why it decides that, I don't know. But I've run into it.
I've submitted an issue to https://github.com/sewenew/redis-plus-plus/issues/474 (which also contains more info about the above issue). This has now been fixed, but to have that apply for smartredis installs, the redis++ version in this repo needs to be updated.
As seen in the above-linked issue, I've requested that redis++ have a new release to include the fix so y'all can simply change the version associated with the redis-plus-plus install. I wanted to go ahead and submit an issue on it before I forget, or if y'all are willing to pin the redis++ version to the current master commit at redis++.

@jrwrigh Thanks for posting this issue.  If a new version of redis++ doesn't get tagged soon, we can temporarily pin the SmartRedis develop branch to the specific commit.  Let us know if you need help with anything else.


support changing pool slots on cron schedules

What does your PR do?
Introducing the scheduled pool implementation enables sync functionality to bump or reduce the number of pool slots on a specific recurrence.
Checklist
For all Pull Requests

[x] Commits are signed off
[x] Commits have semantic messages
[x] Documentation updated
[x] Passes ct linting

For releasing ONLY

[ ] Chart.yaml version bumped
[ ] CHANGELOG.md updated

Hi @thesuperzapper, I would like to introduce the scheduled pools to enable scheduled autoscaling policies to the sync pools. The code is very simple just like its interface as shown below:
- name: "pool"
   description: "example pool with 10 slots"
   slots: 10
   schedules:
     - name: "ScaleUp"
        slots: 28
        recurrence: 0 19 * * *
     - name: "ScaleDown"
        slots: 10
        recurrence: 0 6 * * *

Hi @thesuperzapper could you take another look at the PR?
Thank you


SQL Injection flagged when concatenating strings

Describe the bug
It seems that when concatenating strings in a cur.execute() call, it flags up sql injection possibilities, even though all the string arguments are being passed into the execute() call. So, this looks safe to me.
Reproduction steps
See the # noqa: S608 lines in this file: https://github.com/aio-libs/aiohttp-session/blob/master/examples/postgres_storage.py#L68
Expected behavior
No errors from concatenating string literals.
Bandit version
1.7.0 (Default)
Python version
3.7
Additional context
No response

Please check this example: https://github.com/1n40/bandit/blob/master/examples/sql_statements-py36.py
According to this example, concatenation is a bad practice and the query should not be concatenated.

@1n40 Not sure what I'm looking for in that example. I don't see any that match what I've said or back up your claim that concatenation is bad practice...

In the above mentioned example, at line number 21,  under "Bad" formats, there is this line:
cur.execute("SELECT * FROM foo WHERE id = '" + identifier + "'")
This might mean that string concatenation is considered a bad practice by the program.
Your program  https://github.com/aio-libs/aiohttp-session/blob/master/examples/postgres_storage.py#L68 shows similar type of string concatenation and hence, program raises a flag.
I know generally, string concatenation within query should not raise a flag but according to the program and documented example it is a possible vulnerability.

No, the use of a variable in the string is a possible vulnerability.
Concatenating string literals is not a vulnerability.
If the program is checking purely for concatenation, then it is wrong, hence why this is a bug report.

It might get a little more tricky on whether it can detect literals assigned to variables, with something like:
select = "SELECT ..."
where = "WHERE ..."
cur.execute(select + where, args)

Which should ideally still pass. But, at the very least it should allow literals to be concatenated:
cur.execute("SELECT ..."
                   + "WHERE ...")


Showing connect wallet button on submit page when no wallet is connected

Fixes #1320
Changes proposed in this PR:

Showing connect wallet button on submit page when no wallet is connected

for me, the Connect Wallet is always present, no matter if I have wallet connected or not. Also without wallet connected, then clicking button connecting my wallet, the button also doesn't change

Ok, I see the issue. That was happening when a form field wasn't valid. Should be working ok now


GW2 Radial not loading?

Hey guys i just installed the manager with d912pxy (v 2.2.1) and GW2 Radial ( v 1.2.4al ) and is super cool, but every time i login the GW2 radial is not working, i have to close the game go to the addon manager select the gw2 radial and click update to work. Is this a know bug? Does anyone have the same problem?
The d912pxy works great, only the radial is acting strange.

i think theres a bug with d912pxy. I saw there was a commit on the radial repo that says "d912pxy" workaround.
Unfortunately they have no released a new version of the radial for over a year. Hopefully a new update is coming soon with that fix merged in.


cmd/go: checksum mismatch for<EMAIL_ADDRESS>

What version of Go are you using (go version)?
Go 1.11
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
darwin
amd64
What did you do?
go build ./...
reproduction is difficult because including the package k8s.io/client-go causes incompatible dependencies to be pulled in which is something I have to solve manually.
What did you expect to see?
A repeat of successful builds from the day before.
What did you see instead?
A checksum mismatch this morning after cloning the project to my personal laptop and attempting a build.
go: verifying<EMAIL_ADDRESS>checksum mismatch
        downloaded: h1:7Zl+OVXn0bobcsi4NEZGdoQDTE9ij1zPMfM21+yqQsM=
        go.sum:     h1:2pUaSg2x6iEHr8cia6zmWhoCXG1EDG9TCx9s//Aq7HY=

Okay so the workaround is to manually go get the correct version and then run the build again.  This is a little unpredictable IMO.  I'm guessing this stuff will clear up as more packages add module support and semantic versioning.

@jharshman is there further investigation that needs to be done for this issue? Is there documentation that you are suggesting should be updated? If not, it sounds like this issue can be closed.

+incompatible versions should not cause checksum mismatches.
Is it possible that you were running more than one build concurrently? (https://github.com/golang/go/issues/26794)

@katiehockman I would say this particular issue could be closed because this seems to be a symptom of a larger issue.  But this larger problem needs to be addressed, as @bcmills mentioned, +incompatible versions should not cause checksum mismatches but in this case it has.
And @bcmills to answer your question, no this was the only build running. There were no other builds going on concurrently.

Also seeing this problem but not sure if this is due to GOOS mismatch. I am using WSL (Ubuntu x64) on Windows 10 to run go mod tidy and generate the corresponding go.sum file. I am building and testing using Gitlab CI using a Go 1.11 Alpine x64 container and I am seeing:
go: verifying<EMAIL_ADDRESS>checksum mismatch
	downloaded: h1:7Zl+OVXn0bobcsi4NEZGdoQDTE9ij1zPMfM21+yqQsM=
	go.sum:     h1:2pUaSg2x6iEHr8cia6zmWhoCXG1EDG9TCx9s//Aq7HY=

@katiehockman please remove the WaitingForInfo label unless there is more information that you are requesting.
@bcmills is there a solution in the pipe for this? It's very reproducible so I can image in is afflicting other users as well.
The best solution I have found is to go mod vendor once you have a working build.

@jharshman Could you try a Go build from source at commit 1bca6ce and see if it still reproduces?
I wonder if this is a side-effect of #27153.

Im having similar with golang master branch on my travis build. What's resolution for this?

@leakingtapan, try a go built from source at the above-mentioned commit, and let us know whether it helps.
For CI-related issues, though, you're more likely running up against #26794.

Same issue here:
go: downloading k8s.io/client-go v9.0.0+incompatible
go: downloading k8s.io/api v0.0.0-20181006043042-ded30614edd7
go: verifying<EMAIL_ADDRESS>checksum mismatch
        downloaded: h1:/PdJjifJTjMFe0G4ESclZDcwF1+bFePTJ2xf+MXjcvs=
        go.sum:     h1:NXWpDuPFeVB5lYP1fTqJUtwigjtmRXJNtndnN53ldGI=

@leakingtapan @cosmonawt @jharshman @F21
If you are running 1bca6ce your h1 hashes will, unfortunately, have to be updated once. Both kubernetes/kubernetes and kubernetes/client-go use export-subst which is disabled by this change:

https://github.com/kubernetes/kubernetes/blob/7f23a743e8c23ac6489340bbb34fa6f1d392db9d/pkg/version/base.go#L58
https://github.com/kubernetes/client-go/blob/03bfb9bdcfe5482795b999f39ca3ed9ad42ce5bb/pkg/version/base.go#L58

If you are running 1bca6ce you should get the same hash moving forward. Just delete the old hash and use the new one. Again, you should only have to do this once.
I imagine a lot of folks will run into this issue since k8s repos appear to use export-subst in various places.
If you are seeing inconsistent hashing results I recommend:

Build go from source after 1bca6ce
Delete the old h1 hash for k8s.io/kubernetes k8s.io/client-go and any other repo using export-subst.
Build your project and record the new hash

If the hash changes for you after that then please report back.

@jasonkeene thx for providing the solution. In order to not break people who is using go1.11 to build our package, I decided to stay with go1.11 for a while. This makes my travis build and mac build happy. However, when I tried build on a linux machine the issue even happen on go1.11, which is surprising. Here is the output:
mac
>> go version
go version go1.11 darwin/amd64

>> echo $GO111MODULE
on

>> make
make
mkdir -p bin
go build -o bin/aws-ebs-csi-driver ./cmd/aws-ebs-csi-driver

linux
>> go version
go version go1.11 linux/amd64

>> echo $GO111MODULE
on

>> make
mkdir -p bin
go build -o bin/aws-ebs-csi-driver ./cmd/aws-ebs-csi-driver
go: verifying<EMAIL_ADDRESS>checksum mismatch
        downloaded: h1:AAwZncqPvpeV6DPF8/z2g05/79cumA6IunGDByI1bOs=
        go.sum:     h1:2/lmzYbN17Mr23mX/p4ODMm/MBWTeu2Q1Bvsw82YC40=
make: *** [aws-ebs-csi-driver] Error 1

Thanks for the solution @jasonkeene , but building Go from source is the verification, not a long term solution.  We need to be able to build projects reliably cross platforms and in CI.
It sounds like a bug-fix release needs to be cut from this.

@jharshman For sure compiling from source was just to test to make sure this was your issue.
As far as the bug fix release, pretty sure @bcmills is on it here: https://github.com/golang/go/issues/28094
I would still like you to try the above steps to make sure you are not running into another issue and that the bug fix will actually fix your problem.

@jasonkeene sure let me verify that I don't hit any other issues 👍

I'm not sure if it's related, but this may be related to an issue we've been having with modules: https://github.com/golang/go/issues/27952
We've had situations where the incomplete project didn't compile, but we've also had times that it compiled, but had the wrong hash because files were missing.

@jasonkeene verified the fix by compiling from source after 1bca6ce.  Works after removing the older hashes.

Awesome, good to know!

OK, fixed by  1bca6ce.

This does not appear to be fixed in Go 1.11.2. I removed go.sum, generated a new one with go mod tidy using Go 1.11.2, and I still encountered a checksum error when building the project in a Docker container from image golang:1.11.2.
go: verifying<EMAIL_ADDRESS>checksum mismatch
	downloaded: h1:2kqW3X2xQ9SbFvWZjGEHBLlWc1LG9JIJNXWkuqwdZ3A=
	go.sum:     h1:NXWpDuPFeVB5lYP1fTqJUtwigjtmRXJNtndnN53ldGI=

@jasonkeene, running go clean -modcache seemed to do the trick. Thanks.

I have a project with a private dependency that looks like a regression in regards to this issue between 1.11.1 and 1.11.2.
Host: Darwin
CI: GCP Cloud Builder w/ Alpine image
If I build the container locally on Darwin, things work as expected, but GCP Cloud Builder CI  demonstrates the following behavior between go versions:
1.11: checksum mismatch
1.11.1: works are expected
1.11.2: checksum mismatch
These results hold whether or not go.sum is checked in, which means cleaning the modcache won't fix the issue in this case.
Another possible example is in this thread: https://github.com/kubernetes/kubernetes/issues/69040#issuecomment-435689500

@buckhx Could the GCP Cloud Builder be using a module cache or the proxy functionality? I do not use this service.

Even using go clean -modcache with go 1.11.2 is a bad user experience for me.  I get an error about checksums even when running the command to clear checksums (GO111MODULE=on go clean -modcache).
go: downloading k8s.io/client-go v9.0.0+incompatible
go: verifying<EMAIL_ADDRESS>checksum mismatch
	downloaded: h1:2kqW3X2xQ9SbFvWZjGEHBLlWc1LG9JIJNXWkuqwdZ3A=
	go.sum:     h1:NXWpDuPFeVB5lYP1fTqJUtwigjtmRXJNtndnN53ldGI=

To prevent this, I actually had to disable modules and run the same command (GO111MODULE=off go clean -modcache).
But even then when the clean command has completed, I still get checksum errors when I attempt to run GO111MODULE=on go mod vendor:
go: downloading k8s.io/client-go v9.0.0+incompatible
go: downloading k8s.io/apimachinery v0.0.0-20181108192626-90473842928c
go: finding google.golang.org/grpc/keepalive latest
go: verifying<EMAIL_ADDRESS>checksum mismatch
	downloaded: h1:2kqW3X2xQ9SbFvWZjGEHBLlWc1LG9JIJNXWkuqwdZ3A=
	go.sum:     h1:NXWpDuPFeVB5lYP1fTqJUtwigjtmRXJNtndnN53ldGI=

I am on MacOS Mojave, by the way.

Both 1.11.1 and 1.11.2 are failing for me in client-go. Tried all above workarounds.

1.11.1:
rm go.sum
go build
works

@integrii @buckhx Can you diff the contents of the two zipfiles? This will show you why they have different hashes and will give you a clue to what the problem is.
Also, it might be worth opening a new issue with the zipfile diff since this one has been marked as resolved.

In my case, I found that I had misplaced go.mod and go.sum files in my home directory, which go get was finding automatically and doing very strange things with.  I deleted those files and things worked great.  Thanks!

Great to see this is fixed! Any idea when it will be released? Go 1.11.4 is still affected. I've just wasted half a day because GoLand on OS X is updating the sum file automatically with checksums that don't work in Linux containers. Turning this off at least makes it possible to compile again, but without module support / code completion.
OS X (Go 1.11.4, Git 2.17.2)
github.com/kylelemons/go-gypsy v0.0.0-20160905020020-08cad365cd28 h1:SzHLOWB819X9aUXh2ct6krDIoIujoTsj5J1rDMjkRyo=
Linux (Go 1.11.4, Git 2.17.1)
github.com/kylelemons/go-gypsy v0.0.0-20160905020020-08cad365cd28 h1:mkl3tvPHIuPaWsLtmHTybJeoVEW7cbePK73Ir8VtruA=

@lastzero you're most probably hitting https://github.com/golang/go/issues/29278#issuecomment-447537558

@simonpasquier Thank you! Looks like the follow-up "bug". For those also affected: I had to change settings in GoLand (didn't automatically detect latest Go version) plus delete Go module caches locally and on Travis CI.

Using 1.11.5 and still have this impact

If your machine is macOS or WSL and your CI is Linux, you can add this command to the CI config.
sed -e '/^k8s.io\/client-go /d' -i go.sum

Here is an example for CircleCI:
version: 2
jobs:
  build:
    docker:
      - image: circleci/golang:1.11.2
    steps:
      - checkout
      # workaround for https://github.com/golang/go/issues/27925
      - run: sed -e '/^k8s.io\/client-go /d' -i go.sum
      - run: go vet

d:\xxx>go version
go version go1.12.4 windows/amd64
d:\xxx>go mod tidy
go: downloading github.com/kevinburke/go-bindata v3.11.0+incompatible
verifying<EMAIL_ADDRESS>checksum mismatch
downloaded: h1:RcC+GJNmrBHbGaOpQ9MBD8z22rdzlIm0esDRDkyxd4s=
go.sum:     h1:GiPs9jxaG2xY1B5Dt/d/yHUOMlTk14uS35VcmHrdo4I=

verifying<EMAIL_ADDRESS>che
cksum mismatch
downloaded: h1:mkl3tvPHIuPaWsLtmHTybJeoVEW7cbePK73Ir8VtruA=
go.sum:     h1:SzHLOWB819X9aUXh2ct6krDIoIujoTsj5J1rDMjkRyo=

@runner-mei Did you try go clean -modcache?

@lastzero  oooo, it is ok!


Missed attestations due to delayed block process

Describe the bug
In the last 3 days, there are 3 missed attestations on mainnet nodes, all of them are due to delayed block process, block came early enough but got processed only after 4s, validator submitted wrong heads and no aggregator/block include them

Slot 5175706: block is received 2.5s after slot but only became head after 4.4s => it took 1.9s to process

Nov-20 08:21:35.000[chain]         ^[[36mverbose^[[39m: Clock slot slot=5175706
Nov-20 08:21:38.263[network]       ^[[36mverbose^[[39m: Received gossip block slot=5175706, root=0xc7b3…8f0a, curentSlot=5175706, peerId=16Uiu2HAmAQLr32DoW9iBiNKdyLp4nCUGWvfCixZSs7eZra3GPk1C, delaySec=2.49399995803833
Nov-20 08:21:39.435[chain]         ^[[36mverbose^[[39m: New chain head headSlot=5175706, headRoot=0xc7b31a3bfa3c435f851e62b0a491489aa33ac05c344982e194889644a2df8f0a, delaySec=4.434999942779541
Nov-20 08:21:39.435[chain]         ^[[36mverbose^[[39m: Block processed slot=5175706, root=0xc7b31a3bfa3c435f851e62b0a491489aa33ac05c344982e194889644a2df8f0a, delaySec=4.434999942779541

Slot 5176963: block was received 2s after the slot but became head only after 4.9s => it took 2.9s to process

Nov-20 12:32:59.000[chain]         ^[[36mverbose^[[39m: Clock slot slot=5176963
Nov-20 12:33:01.044[network]       ^[[36mverbose^[[39m: Received gossip block slot=5176963, root=0xa68b…7508, curentSlot=5176963, peerId=16Uiu2HAkuVTNVU2stE4sg71eE8mSs9TNEg126SQbyV9VhGoP68RK, delaySec=1.997999906539917
Nov-20 12:33:03.934[chain]         ^[[36mverbose^[[39m: New chain head headSlot=5176963, headRoot=0xa68bf57f9ec614fcca59c461e25ff5801b585acbe622a540482bf80e62537508, delaySec=4.934000015258789
Nov-20 12:33:03.934[chain]         ^[[36mverbose^[[39m: Block processed slot=5176963, root=0xa68bf57f9ec614fcca59c461e25ff5801b585acbe622a540482bf80e62537508, delaySec=4.934000015258789

Slot 5177951: block was received 3.1s after the slot but became head only after 4.3s => it took 1.2s to process

Nov-20 15:50:38.317[network]       ^[[36mverbose^[[39m: Received gossip block slot=5177951, root=0xc6a1…71e5, curentSlot=5177951, peerId=16Uiu2HAkvafBgXW7xdhPk9VJqxAha8bUzA9kyh1AiLjkKB3bhfLo, delaySec=3.0920000076293945
Nov-20 15:50:39.320[chain]         ^[[36mverbose^[[39m: New chain head headSlot=5177951, headRoot=0xc6a161f431cf038c4fb60e67db537467bf32fcc9c8225c0e26ba5cd8f21d71e5, delaySec=4.319999933242798
Nov-20 15:50:39.321[chain]         ^[[36mverbose^[[39m: Block processed slot=5177951, root=0xc6a161f431cf038c4fb60e67db537467bf32fcc9c8225c0e26ba5cd8f21d71e5, delaySec=4.3210000991821

Expected behavior
Should take less delay time after we receive block to process, make sure all blocks are processed within 4s.

Right now in the queue logic there is either setTimeout() or sleep(0) code which only trigger a block process only in the next event loop, and it has to finish all micro tasks in the current event loop
@dapplion one thing we could try is to process block immediately without going through the queue if:

block slot = clock slot
we have parent root in forkchoice
optional: within 4s

this is similar to proposer boost, what do you think?

@tuyennhv You should validate your hypothesis first.

Claim: setTimeout() or sleep(0) code adds some delay of block process
To proof: Add a metric or console log to track the delay before that sleep and after

If that metric shows some delay, say > 50ms I'm okay with your proposed change

@dapplion  there are 2 queues:

Gossip validation queue: The job queue for block usually has 1 block maximum at a time so we can use jobWaitTime to measure the setTimeout() delay, in the worse case it could be up to 1s

(this is from a 100-validator mainnet node)

Block processor queue: similarly

(I captured by 1m chart to find the worse case scenarios)
that could partially explain for the "wrong head ratio" we have (this is 1h chart for 1 mainnet node in the last 30 days)

@tuyennhv I've plotted the histogram's buckets to check if the queue wait time is a major contributor to delays. To read the charts below, the query is:
12 * rate(lodestar_block_processor_queue_job_wait_time_seconds_bucket[30m])

with "Format: heatmap", so each label reads as the "le" value where it's the percent of values that are between that bucket and the next. For example the series labeled as "1" mean the rate of values in the range "0.1 - 1".
Looking below the block consistently takes ~2 seconds to process. Job wait times are high in very rare occasions < 1% of times. Also the peaks in job wait time do not correlate that clearly with wrong head metric and high block processing times.
As next steps:

First would be important to understand what step of block processing contributes the most. Add histogram metrics on each step of the block processing code paths
List points in block processing where async code is hit, which could enable the point below
Understand if queue job wait times are a result of the event loop being busy, for example due to attestation processing

Looking below the block consistently takes ~2 seconds to process

@dapplion not sure what metrics you used to measure that, the below metrics say it takes only 300ms-700ms to process block most of the time
(rate(lodestar_gossip_block_elappsed_time_till_processed_sum[$__rate_interval])/rate(lodestar_gossip_block_elappsed_time_till_processed_count[$__rate_interval]) - (rate(lodestar_gossip_block_elappsed_time_till_received_sum[$__rate_interval])) / rate(lodestar_gossip_block_elappsed_time_till_received_count[$__rate_interval]))

that's confirmed by the log
Nov-24 03:14:59.955[network]       verbose: Received gossip block slot=5202973, root=0x1151…2cd3, curentSlot=5202973, peerId=16Uiu2HAm5pzYeaL4K2BJgrHivXcTJUFSvKsdLQKsLijpbQoFtVDQ, delaySec=0.937999963760376
Nov-24 03:15:00.374[chain]         verbose: Block processed slot=5202973, root=0x1151a530b912d120dd1cdb3e5c90f7bb76d0cc010df9c3a19c2ac9f6c44d2cd3, delaySec=1.374000072479248

Nov-24 03:15:12.837[network]       verbose: Received gossip block slot=5202974, root=0x6e94…7abf, curentSlot=5202974, peerId=16Uiu2HAm5pzYeaL4K2BJgrHivXcTJUFSvKsdLQKsLijpbQoFtVDQ, delaySec=1.815000057220459
Nov-24 03:15:13.188[chain]         verbose: Block processed slot=5202974, root=0x6e94cf7eab2cfa05148b0c148a163a7f85eeb9404c1ffa7141613ae603ea7abf, delaySec=2.187999963760376

Nov-24 03:15:26.065[network]       verbose: Received gossip block slot=5202975, root=0xb84e…2d01, curentSlot=5202975, peerId=16Uiu2HAm5pzYeaL4K2BJgrHivXcTJUFSvKsdLQKsLijpbQoFtVDQ, delaySec=3.0409998893737793
Nov-24 03:15:26.396[chain]         verbose: Block processed slot=5202975, root=0xb84eee7448ab891386810cdff7469a423f1d79661e2cf5667d2ef3d8755d2d01, delaySec=3.3959999084472656

Nov-24 03:15:38.515[network]       verbose: Received gossip block slot=5202976, root=0xfbdd…2e6c, curentSlot=5202976, peerId=16Uiu2HAm5pzYeaL4K2BJgrHivXcTJUFSvKsdLQKsLijpbQoFtVDQ, delaySec=3.49399995803833
Nov-24 03:15:39.086[chain]         verbose: Block processed slot=5202976, root=0xfbddcd5c1db381428ffd4a094afe9e36d4ff1425d6c4e36b921082aefa2e2e6c, delaySec=4.085999965667725

Nov-24 03:15:49.029[network]       verbose: Received gossip block slot=5202977, root=0x2f2a…d2df, curentSlot=5202977, peerId=16Uiu2HAm5pzYeaL4K2BJgrHivXcTJUFSvKsdLQKsLijpbQoFtVDQ, delaySec=2.007999897003174
Nov-24 03:15:49.330[chain]         verbose: Block processed slot=5202977, root=0x2f2abd6e9dad6c93048ce9b7d04c365f55a399de7f2619ed635ffab0ce44d2df, delaySec=2.3299999237060547

so the block process time of ~1.2s to 2.9s in the issue is really just exceptional cases, and we should only debug those exceptional cases.

Deployed tuyen/timing_block_process to a mainnet node subscribing to all subnets, found some blocks with significant time to process a block

Dec-04 23:48:21.310[chain]         verbose: Imported block slot=5281139, recvToImportedBlock=8.513999938964844

Dec-04 23:48:12.816[network]       ^[[36mverbose^[[39m: Received gossip block slot=5281139, root=0x9464…b7d9, curentSlot=5281139, peerId=16Uiu2HAm5v688pXE3ppChqdLPF2VzWTomndrvJGi5auBFquSv9tj, delaySec=1.7960000038146973, recvToVal=0.019999980926513672
Dec-04 23:48:12.904[chain]         ^[[36mverbose^[[39m: Transitioned gossip block slot=5281139, recvToTransition=0.10800004005432129
Dec-04 23:48:12.926[chain]         ^[[36mverbose^[[39m: Verified block signatures slot=5281139, recvToSigVer=0.13000011444091797
Dec-04 23:48:17.731[chain]         ^[[36mverbose^[[39m: Verified execution payload slot=5281139, recvToVerifiedExecPayload=4.934999942779541

=> it took ~4.8s to verify execution payload and ~3.6s to import block

Dec-04 23:57:59.299[chain]         verbose: Imported block slot=5281187, recvToImportedBlock=6.884000062942505

Received gossip block slot=5281187, root=0xf597…8a73, curentSlot=5281187, peerId=16Uiu2HAmJsu4168VQNxHmNpDavXPDZo93LVPSZhbe2Q58suByrfz, delaySec=5.414999961853027, recvToVal=2.9070000648498535
Transitioned gossip block slot=5281187, recvToTransition=6.325999975204468
Verified block signatures slot=5281187, recvToSigVer=6.3480000495910645
Verified execution payload slot=5281187, recvToVerifiedExecPayload=6.829999923706055

=> it took 2.9s from receiving the block to verifying it, 3.4s for gossip validation + state transition

Dec-05 02:56:34.047[chain]         verbose: Imported block slot=5282080, recvToImportedBlock=8.204999923706055

Received gossip block slot=5282080, root=0xd65d…b147, curentSlot=5282080, peerId=16Uiu2HAmJhbjjfdguFwx3h3mjadSE8NEVps7QRgjwcfkEJZLuMsC, delaySec=2.8420000076293945, recvToVal=0.01399993896484375
Transitioned gossip block slot=5282080, recvToTransition=0.20300006866455078
Verified block signatures slot=5282080, recvToSigVer=0.22600007057189941
Verified execution payload slot=5282080, recvToVerifiedExecPayload=8.15499997138977

=> almost 8s to verify execution payload

Dec-05 02:56:45.700[chain]         verbose: Imported block slot=5282081, recvToImportedBlock=9.871999979019165

Received gossip block slot=5282081, root=0x0fde…06fc, curentSlot=5282081, peerId=16Uiu2HAm5v688pXE3ppChqdLPF2VzWTomndrvJGi5auBFquSv9tj, delaySec=0.8280000686645508, recvToVal=0.7070000171661377
Transitioned gossip block slot=5282081, recvToTransition=3.6459999084472656
Verified block signatures slot=5282081, recvToSigVer=3.6669998168945312
Verified execution payload slot=5282081, recvToVerifiedExecPayload=9.823999881744385

=> it took 0.7s from receiving the block to verifying it, 2.9s for gossip validation + state transition, ~6.1s for execution payload validation
Note that this only mean the time between tasks, it does not mean a specific task takes time at all. It's most likely the use of sleep(0) (at least in job queue) delay the task sometimes

There are some percentage of job wait time >1s when processing a gossip block, ideally they should be all 0


Trim whitespace from kycfile. Return multisig addresses from validate…

…kycfile RPC.

can we have some tests for this to make sure it works

Ok, done


[SPARK-40984][CORE][SQL] Use NON_FOLDABLE_INPUT instead of FRAME_LESS_OFFSET_WITHOUT_FOLDABLE

What changes were proposed in this pull request?
This pr aims replace FRAME_LESS_OFFSET_WITHOUT_FOLDABLE with NON_FOLDABLE_INPUT to clean up similar error subclass.
Why are the changes needed?
FRAME_LESS_OFFSET_WITHOUT_FOLDABLE and NON_FOLDABLE_INPUT look similar, but NON_FOLDABLE_INPUT is more general
Does this PR introduce any user-facing change?
Yes. The PR changes user-facing error messages.
For example, the error message will change from
Offset expression "(- nonfoldableliteral())\" must be a literal.

to
the input offset should be a foldable "INT" expression; however, got "(- nonfoldableliteral())\".

How was this patch tested?
Pass Github Actions

@MaxGekk @itholic @panbingkun Could you review this pr, thanks.

+1, LGTM. Merging to master.
Thank you, @LuciferYang.

Thanks @panbingkun @MaxGekk


APNGs should be detectable by mimetype image/apng as well as  image/png

apngs can also have as mimetype image/apng https://wiki.mozilla.org/APNG_Specification#MIME_type

This was claimed fixed by the PR above.


Sporadic browser connectivity issues

There are other similar issues reported. Issues tend to keep closing, but the problem still exists. Yes, it might be something outside TestCafe causing the issues, but retry functionality would make test runs more robust. There's apparently some half-implemented retrying for the proxy already, but what about that browser connection error?
What is your Test Scenario?
Tests cases are browsing a page on localhost dev server (create-react-app/webpack).
What is the Current behavior?
A few different sporadic errors. Increasing concurrency (-c X) seems to make the errors appear more often. The first two might appear in the middle of the test run. The last one always happens right in the beginning and no test cases are executed after that.
Failed to find a DNS-record for the resource at "http://localhost:3000/"

Failed to find a DNS-record for the resource at "http://localhost:3000/someResource.jpg"

{ Error: Unable to establish one or more of the specified browser connections. This can be caused by network issues or remote device failure.
    at /app/node_modules/testcafe/src/runner/browser-set.js:84:30
    at Generator.next (<anonymous>)
    at step (/app/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
    at /app/node_modules/babel-runtime/helpers/asyncToGenerator.js:35:14
    at new Promise (<anonymous>)
    at new F (/app/node_modules/babel-runtime/node_modules/core-js/library/modules/_export.js:36:28)
    at /app/node_modules/babel-runtime/helpers/asyncToGenerator.js:14:12
    at BrowserSet._waitConnectionsOpened (/app/node_modules/testcafe/src/runner/browser-set.js:77:37)
    at _waitConnectionsOpened (/app/node_modules/testcafe/src/runner/browser-set.js:107:35)
    at invokeCallback (/app/node_modules/pinkie/index.js:60:12)
    at Array.forEach (<anonymous>)
    at publish (/app/node_modules/pinkie/index.js:147:32)
    at Array.publishFulfillment (/app/node_modules/pinkie/index.js:152:2)
    at Immediate.asyncFlush [as _onImmediate] (/app/node_modules/pinkie/index.js:17:19)
    at runCallback (timers.js:812:20)
    at tryOnImmediate (timers.js:768:5)
    at processImmediate [as _immediateCallback] (timers.js:745:5) constructor: [Function: GeneralError] }

Your Environment details:

testcafe version:                   0.23.3
node.js version:                    8.12.0
command-line arguments:   -c 4
browser name and version:  Firefox 60 (headless), Chrome 71 (headless)
platform and version:           Jenkins/Kubernetes/Docker/Linux (not TestCafe's own Docker image)

We have been experiencing this issue for a while now too.
Slightly different app, ours is a .NET Core React app built using webpack 4.
My Environment details:
testcafe: 1.0.1,
testcafe-reporter-teamcity: 1.0.10,
testcafe-reporter-html: 1.3.0,
Browser: Chrome 72.0.3626 / Windows <IP_ADDRESS> (Issue occurs both in Headless and non-headless)
I've set it up using using the 6th parameter:
createTestCafe('localhost', undefined, undefined, undefined, true, true)
Looking at our webserver logs, I can't see any errors or anything unusual - I suspect once testcafe gets this error, the web server never receives or see a request for the page. I initially suspected it could be a timeout issue if our webserver was getting caught in a long running process, but the tests that fail only run for <3 seconds which is well short of any default timeouts. It's  seemingly random which tests fail, (even though the tests always run in the same order) sometimes early tests can fail, but they tend to usually be later in the test run, and not the last (IE tests will generally pass after them).
Is there any logs that I could take that you think might help?

The quarantine mode seems to help, some "evidence" (I'm hesitant to be call it confirmed with 4/4 successful runs in a row) that it is helping is that we have Screenshots on fail enabled, and we are getting screenshots when no tests are failing. The screenshots are from different tests too.

Concurrency definitely exacerbates the issue and have reverted back to concurrency 1. I've have had a few failures since, but its noticeably more stable.


usage of prismaObjectType from 'nexus-prisma' produces an anoying warning in vscode

dear all,
I am using prismaObjectType from 'nexus-prisma'
import { prismaObjectType } from 'nexus-prisma'
But this usage produces the following warning:
Expression produces a union type that is too complex to represent.
I have tried many things to fix this warning but without success.
Any help will be appreciated.

I got rid of the warning by specifying the model name as a string inside <> like so:
export const User = prismaObjectType<"User">({
  name: 'User',
  definition(t) {
    t.prismaFields(['id', 'email']);
  },
});

this is perfect, thank you for your valuable input


Messages not working after revel update from 0.19.0 to 0.21.0

So if I run revel with revel run app everthing is just fine.
After using revel package app prod and then using ./run.sh to run the application, all messages can't be found any longer. Everything else works just fine. The current locale is set correctly to either en-US or de-DE. Also, message files end with .en or .de and can be found at /messages/.
So since I couldn't find the error, I was wondering if there might be some error with the newer version and/or the package command. Or is there something I missed concerning the newer version?
In case revel package turm2 prod -v output is needed:
INFO  17:32:20 command_config.go:152: Returned import path                     buildpath=/home/tania/go  path=turm2
INFO  17:32:20   file.go:346: Seeking app package                      app=turm2
INFO  17:32:20   file.go:354: Seeking remote package                   using=turm2 remote=github.com/revel/revel
INFO  17:32:20 command_config.go:303: Fullpath to revel                        dir=/home/tania/go/src/
INFO  17:32:20 command_config.go:334: Parsed revel version                     version="Version: 0.21.0\nBuild Date: \n Minimium Go Version: "
INFO  17:32:20 command_config.go:161: Revel versions                           revel-tool="Version: 0.21.1\nBuild Date: \n Minimium Go Version: " Revel Framework="Version: 0.21.0\nBuild Date: \n Minimium Go Version: "
Revel executing: package a Revel application (e.g. for deployment)
INFO  17:32:20 command_config.go:241: InitGoPaths
INFO  17:32:20 command_config.go:278: Source root                               path=/home/tania/go cwd=/home/tania/go/src/turm2 gopath=/home/tania/go bestpath=
INFO  17:32:20 command_config.go:295: Set application path                     path=/home/tania/go/src/turm2
INFO  17:32:20 command_config.go:179: InitPackageResolver                      useVendor=false path=/home/tania/go/src/turm2
INFO  17:32:20   file.go:346: Seeking app package                      app=turm2
INFO  17:32:20   file.go:354: Seeking remote package                   using=turm2 remote=github.com/revel/revel
INFO  17:32:20   file.go:346: Seeking app package                       app=turm2
INFO  17:32:20   file.go:354: Seeking remote package                   remote=github.com/revel/revel  using=turm2
INFO  17:32:20  build.go:271: Cleaning dir                             dir=tmp
INFO  17:32:20  build.go:271: Cleaning dir                              dir=routes
INFO  17:32:20 reflect.go:164: Exaimining files in path                 package=/home/tania/go/src/turm2/app
INFO  17:32:20 reflect.go:164: Exaimining files in path                  package=/home/tania/go/src/turm2/app/controllers
INFO  17:32:20 reflect.go:164: Exaimining files in path                 package=/home/tania/go/src/turm2/app/database
INFO  17:32:20 reflect.go:164: Exaimining files in path                 package=/home/tania/go/src/turm2/app/jobs
INFO  17:32:20 reflect.go:164: Exaimining files in path                 package=/home/tania/go/src/turm2/app/models
INFO  17:32:20 reflect.go:164: Exaimining files in path                  package=/home/tania/go/src/github.com/revel/modules/static/app/controllers
INFO  17:32:20 reflect.go:164: Exaimining files in path                 package=/home/tania/go/src/github.com/revel/modules/static/app/model
INFO  17:32:20  build.go:271: Cleaning dir                             dir=tmp
INFO  17:32:20  build.go:271: Cleaning dir                              dir=routes
INFO  17:32:20  build.go:250: Exec:                                    args="[/usr/bin/git --git-dir=/home/tania/go/src/turm2/.git --work-tree=/home/tania/go/src/turm2 describe --always --dirty]"
INFO  17:32:20  build.go:187: Exec:                                    args="[/usr/local/go/bin/go build -i -ldflags -X turm2/app.AppVersion=git-b537bb5-dirty -X turm2/app.BuildTime=2018-11-30T16:32:20Z -tags  -o /home/tania/go/bin/revel.d/turm2/turm2 turm2/app/tmp]"
INFO  17:32:21  build.go:192: Build successful continuing
Your application has been built in: /tmp/turm2099918497
Your archive is ready: /home/tania/go/src/turm2/turm2.tar.gz

Figured this out, the default value for the app.conf  field package.folders is conf,public,app/views. It is missing messages for a temp fix you can define the field above in your app.conf to be conf,public,app/views,messages sorry this will be fixed in next release


[DOC] ML inference processor supporting local model

What do you want to do?

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
https://github.com/opensearch-project/ml-commons/issues/2499
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

@ylwu-amzn - Who is creating the doc PR for this update?

@rbhavna , Bhavana will work on this

@rbhavna is raising the doc PR. Thanks, @rbhavna!


Add finish_reason to OpenAIPrompt response

Extract finish_reason from choice in OpenAIPrompt.
Append finish_reason to delta_content if present.

I think it is better to record 'finish_reason' in the prompt structure instead of mingling it with the message content. Where and how do you need this info?


Allow puppetlabs/apt 7.x

@bastelfreak I think we should merge this, even if the Travis CI pipeline is broken.


[BEAM-2146] Disable unsupported categories for Dataflow streaming

This disables the tests failing at https://ci-beam.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Streaming/5/#showFailuresLink
They are unsupported features on Dataflow.
Confirmed that prior runs have the same failures: they are not flakes and there are not additional flakes.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @tysonjh

run dataflow validatesrunnner streaming

Run Dataflow Streaming ValidatesRunner

R: @tysonjh


Generated e2e testing files does match the style guide (Style 02-11)

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
all

Versions. Please run ng --version. If there's nothing outputted, please
run in a Terminal:
node --version
And paste the result here.
master

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
ng new

The log given by the failure. Normally this include a stack trace and some
more information.
nothing special

Mention any other details that might be useful.
Generate files have "e2e" suffix when they should have "e2e-spec" suffix

Closed via https://github.com/angular/angular-cli/pull/1013


Don't hide if the tooltip isn't ready.

I found that hide was being called-back before show (and thus readify()). This protects against that case.
I think its best simply to bail in this case, rather than call readify() and continue.

Thanks :)


fix: fix mergeWithArchivedWorkflows test data to match expected

Fixes #11815
Motivation
https://github.com/argoproj/argo-workflows/actions/runs/6166062084/job/16734921912

Modifications
The mergeWithArchivedWorkflows test data was modified to match expected.
Since mergeWithArchivedWorkflows does not return sorted within the function, sort.Sort() was used for testing to match expected.

Verification

Thank you!


Create style for Cross Leaving

Q
A

Is bugfix?
No

New feature?
No

Fixed issues
Fixes # if any

Button now looks like a real and beautiful red cross

Review Required

Review Required


Adding Hue Infuse Medium Ceiling Lamp<PHONE_NUMBER>01)

Device information

https://www.philips-hue.com/en-us/p/hue-white-and-color-ambiance-infuse-medium-ceiling-lamp/046677579845
Home Assistant Device information

Hue Infuse ceiling<PHONE_NUMBER>01)
by Signify Netherlands B.V.
Checklist

[x] I have created a single PR per device. When you have multiple submissions please create separate PR's.
[x] For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
[x] For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

Generic LED light on E27 socket was connected as a dummy load.

Thanks a lot for your contribution. Perfect PR no remarks whatsoever.


64px fails if not in mode "distance + ambient" when starting

The 64px can be configured to either produce only distance output (64 values), or distance and "ambient" output (2 * 64 values). The driver appears to require the sensor to be configured for distance and ambient before it starts. Otherwise the ros node fails to read frames:

Probably the sensor interface should explicitly set the desired mode at startup, instead of assuming that the sensor already is in the correct mode.
By the way, do you have documentation for what the "ambient values" are? I'm not sure how to interpret them.

Hi @mortenfyhn,
Thanks a lot for the feedback. Concerning the ambient, it's an arbitrary value given by the sensor which represents the intensity of light in the wavelength of the sensor. We didn't make it available (in ROS) as it has more a debug and information purpose (detect other infra-red sources for instance). You can find more info in our user manual here.
On the driver side, you are right the driver should not assume one of the two modes. To fix that, there are several ways:

Allow 141 and 256 bytes long frames -> ok as distance is always before ambient but a bit dirty
Force ambient + distance at start -> but overrides sensor/user settings
Change dynamically when ambient topic is subscribed, this would imply to rework the driver parse the ambient and publish it

We are quite busy on other products right now, so it will be hard to squeeze big changes in our schedule (I'll add it to the backlog though). I'll try to release the first fix in the next weeks to prevent the driver from hanging.
As usual, feel free to submit a pull-request if you want, we will be more than happy to review it.
Cheers,
Pierre-Louis

Thanks for the reply. I think option 2 is fine, so I'll try to submit a PR for it soon.


Update README.md

Submitting an app for your list.

Great! 😄

Coverage remained the same at 69.946% when pulling 499c8288ebac90ef656359c62dbdbd70eb685ee1 on ricktbaker:patch-1 into 313d1e6fecd98a4a5e8dddebb832a6c4c16a828d on sourcelair:v3.


why not include docs?

Why not include jekyll-docs to the official docker image?
It will allow me to browse Jekyll manual in offline.
$ docker pull jekyll/jekyll:pages
$ docker run -it -p <IP_ADDRESS>:4000:4000 jekyll/jekyll:pages
jekyll docs
You must install the 'jekyll-docs' gem to use the 'jekyll docs' command.

I can't tell if this is a request for us to include it by default?


Request - Command for forced backup in game.

I mean pretty straight forward request - love the mod by the way - saved me from hell 4 times now.

You can use /backup to start a backup in game. I'm glad that you're enjoying the mod.


Warn about broken tables, and avoid FOP crash

Signed-off-by: Robert D Anderson<EMAIL_ADDRESS>Description
We found an old DITA topic that included an invalid table -- the <tgroup> element used @cols="3", indicating three columns, but somehow an author added a fourth column. HTML output tolerates the markup and everything appears. When processing the topic for PDF, FOP crashes with a Java error. Antenna House returns a PDF, but the text of the "extra" column appears to the right of the table, in a one-character column.
The fix adds an error message when PDF2 code detects an entry beyond the specified number of columns. It operates based off of the generated @dita-ot:x and @dita-ot:morecols attributes added during preprocess. It's possible (but difficult) to get a table without those, so the code falls back to current behavior if they are not specified. When the last column of the current entry is beyond the specified number of columns, a new error message is generated. In the FOP override, the entry is dropped after generating that message.
FWIW, having too few entries in a row does not break either Antenna House or FOP, and you end up with an empty cell in the PDF.
How Has This Been Tested?
Integration tests pass. The table used to test the specific fix is a trimmed down version of the original topic. It tests a row with an extra cell (no spanning), and a row that has an extra cell due to spanned columns.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
 "task.dtd">
<task id="wonkywonk" xml:lang="en-us">
<title>Wonky Table</title>
<shortdesc>The tables are wonky. REALLY WONKY!</shortdesc>
<taskbody>
<result>

<title>Extra cell</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="1.0*"/>
<colspec colname="c2" colnum="2" colwidth="1.0*"/>

<row>
<entry>head!</entry>
<entry>Head!</entry>
</row>

<row>
<entry>a</entry>
<entry>b</entry>
</row>
<row>
<entry>a</entry>
<entry>b</entry>
<entry>THIS IS EXTRA</entry>
</row>
<row>
<entry>a</entry>
<entry>b</entry>
</row>

</tgroup>

<title>Extra cell due to spans</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="1*"/>
<colspec colname="c2" colnum="2" colwidth="1*"/>

<row>
<entry>header1</entry>
<entry>header2</entry>
</row>

<row>
<entry>normal</entry>
<entry>normal</entry>
</row>
<row>
<entry namest="c1" nameend="c2">spanned cols = next cell is invalid</entry>
<entry>This is invalid</entry>
</row>
<row>
<entry>normal</entry>
<entry>normal</entry>
</row>

</tgroup>

</result>
</taskbody>
</task>

Not sure how best to add to test suite due to general lack of PDF-specific test cases.

Made the update to add xs:integer and build now complains about item having type xs:double, so not yet ready for merge.


plan for new feature

Enhance the security of your chat app by implementing end-to-end encryption for all messages exchanged between users. This ensures that only the sender and recipient can access the content, providing stronger privacy.

That's good


chore: redefine DivInvMonoid.zpow_succ' field

This field of the class refers to Int.ofNat, but this is not (reducibly) defeq to the coercion, and not simp-normal. By using the coercion instead, we get access to all the lemmas on the coercion. This means we should be able to get rid of a few erws and simps.
We do the same for SubNegMonoid.zsmul_succ'.
An argument against this change is that the original version mirrors the definition of Int as an inductive type somewhat better. However, note that we already have a plain 0 in zpow_zero' instead of Int.ofNat 0.

[ ] depends on: #17569

Thanks :tada:
If CI passes, please remove the label awaiting-CI and merge this yourself, by adding a comment bors r+.
bors d+

bors r+

Come on, bors!
bors r+


The Need to Fix gprof Call Graph

@megakevin: Now that gprof call graph has the path of file containing the function definition, do you think we still need to fix gprof call graph with information from the cflow call graph?

You're right I don't think that's necessary anymore.


Implements RFC 7

Fixes #7, based on this work from Orta. Possible addition: translate from shorthand to longhand labels (so a commit message like [MSG] Implements inbox would match the Messaging label. I'll take a look later today.
There's probably some code golfing to do, so don't be shy about pointing out alternative syntax etc!

Strange, wonder why Peril didn't complain about no one being added to the PR?

Ah, I see the failure in the logs. I'll try to take a look.

Fixed that in #27.

This is awesome - I'm into it for sure.
My only hesitation is taking a step back and looking at all-prs.ts and wondering where this file is going. I'm seeing some duplication and maybe overthinking it, but this approach of using straight functions seems like it boxes us in. I do not have a better idea, just something that occurred to me as I was mulling this over. Has anyone else noticed this?

There's a current limitation with peril that we can't require relative files, so we're stuck with a long file ATM

Cool, going to merge, thanks @ashfurrow!!

https://github.com/artsy/emission/pull/756#event-1278271738

AWWWWWW YEAH


Speed up hsctl rebuild

I think the original issue is specific to django 1.8, and that this is the issue: https://code.djangoproject.com/ticket/23745
But, regardless, if you add a -v0 to the migrate step the migrate step is significantly faster  - especially when there are no migrations to perform at all!

Merged in #91.


Extracted files cannot be moved until a second relaunch

Sort of a minor thing but files from an extracted download cannot be moved immediately after extraction, so the game needs to be launched twice - First to download/extract the zip, second to actually move the files from the extracted zip.

Why not download the archive directly to the right place?


[WIP]fix the error when add comment between conditions

fix: #3678

@rchaser53 Pinging for triage - do you have any update?

It takes the time more for me. I close this PR and will send again.


Support navigation to category/section in getting started

Allow to navigate to builtin category and sections.

Looks good, you might consider using GettingStartedPage#selectStepLoose(id) to select the step on existing pages.


p2p: getDocumentRequest for entity

I commit the first draft.
I have some questions in general:

should RequestDocumentWithToken method be in the processor?

currently, the processor is more related to anchoring

in the service, we have a method called ReceiveAnchoredDocument

I will make a more generic method out of it. because some parts I can reuse for GetDocument.
ReceivedAnchoredDocumentValidator etc.

Currently, the differences between ReceiveAnchoredDocument and GetDocument are:

no webhook needed because GetDocument is sync
GetDocument does not always need Update for saving the document

I commit the first draft.
I have some questions in general:

should RequestDocumentWithToken method be in the processor?

couldn't we have a more generic request method which takes multiple access types, like how the receiver is set up?


x/sync/semaphore: newWeighted why n is int64

Please answer these questions before submitting your issue. Thanks!
https://github.com/golang/sync/blob/master/semaphore/semaphore.go#L25
What version of Go are you using (go version)?
1.10.4
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOBIN=""
GOCACHE="/home/sherlock/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/sherlock/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
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-build083961696=/tmp/go-build -gno-record-gcc-switches"

What did you do?
use semaphore.NewWeighted
What did you expect to see?
n should be uint64, because uint64 is large enough
What did you see instead?
n is int64

I imagine the advantages of switching to uint64 are not worth breaking the API compatibility, but @jba might have more info on why.

I discussed it with my friends, we suppose we almost won't use a number larger than maxint64. however uint64 can smaller than 0 and wet won't make n smaller than 0 so it won't panic

In general numbers should be signed unless it is important that they be unsigned.  All computer integers have strange behavior at some points.  Signed integers have strange behavior at very large absolute values.  Unsigned integers have strange behavior at zero.  Zero is much more common in real life, so on average we minimize surprises by using signed integers.


Refresh/quickstart guide

not sure what happened here. i forked, cloned my master and made a branch off of it, and there was a conflict in one file when i submitted the PR. i rebased and suddenly a mess of additional commits appeared from upstream. all of these should have already been in masterwhen i forked it, so i'm a little baffled. i'm going to close this PR and start over.


chore: update note-c add cmake support

This PR updates note-c to the current release commit.
note-c-sources.txt is a list of the C sources that make up the library. It's intended for use by automated builds.
note-c.cmake encapsulates CMake support, providing a simple way to consume the library in CMake projects.

 update note-c in note-msp430 and add cmake support


'process' error on frontend makes the library throw unsupported err

I can access window.performance.memory from console
Creating new event says it's unsupported

Should work now


Cannot print label trough webservice after doManifest

Hi,
I'm currently trying to print a label after manifesting a shipment by number, which works.
Right after manifesting the shipment, I cant print the label anymore - neither through the old url, nor by using $dhl->getShipmentLabel($shipmentNumber)`.
Is this a limitation of the sandbox or a mishandling of the API through the library?

Yes my Company has the same Problem. I solved that by saving the Base64-Label Data. It seems that you can't use the URL after the Shipment is "Done" aka after you do the Manifest or the "Shipment-Date" is over

Alright and you use it the same way in production?

Yes. I'm unsure why you can't use the URL after that. But maybe DHL try to save Disk space with this or whatever^^
Last time we need to reprint a Label and it was gone. So we just reprint it via the DHL-Portal - But this can be a pain if you have to do that with a lot of Labels, so I suggest to save the Base64-Label Data

Alright, we now use the same mechanism. Thx.


CBC fixes

Fix CBC mode decryption for aliased input/output
Also fix SHA3-224 as per #14

Coverage remained the same at 0.0% when pulling 9c6f1b152ca8349d86709d094a37962c8f6e3039 on Vestrel:main into 90f763141b7930609f1888e118064df4e836ecc8 on ctz:main.


Breaking Change: Can no longer create component with name dapr

It is now no longer possible to create a Component with the name dapr.
FATA[0000] Fatal error from runtime: process component dapr error: [INIT_COMPONENT_FAILURE]: initialization error occurred for dapr (workflow.dapr/v1): component dapr already exists  app_id=foo instance=purple scope=dapr.runtime type=log ver=unknown

We should rename the internal workflow component name to be _dapr_workflow or _dapr so that it is internally namespaced.
We should change the type of this component to be workflowbackend.dapr.
We should remove this always installed Component from the metadata endpoint Comeponent list, and instead report the workflow backend status on the workflow metadata fields.

@JoshVanL This seems to be a larger issue than workflow.dapr component having a dapr name.
For example in 1.12.4, you can have a component with name pubsub of pubsub.redis type and a component with name pubsub of statestore.redis. This seems to work at least in the init scenario (I have not verified the behavior yet(as in which component def gets the precedence), just that init works).
But in master, that is currently not possible. Any component loaded with a particular name, cannot be loaded again.
This I believe is the main issue, it is not entirely related to the workflow.dapr component since that component has existed in the code even before changes for 1.13.
cc @yaron2 @artursouza

@mukundansundar This behaviour was changed in https://github.com/dapr/dapr/pull/7195. Allowing same name different types was at best a bug, and at worst allowing users to put components in corrupted states.
This only effected self hosted mode and was considered on oversight. Kubernetes enforces uniqueness of names on resource objects already.
Without having a unique index on name, hot reloading will not work.

@JoshVanL This specific component should not be changed to workflowbackend.dapr type since it is specifically the dtf engine that is being initialized here and not the backend.
@ASHIQUEMD will provide more details on this

Hi @mukundansundar,
I appreciate your clarification, and I want to emphasize the distinction between the two types of components in the context of workflow:
workflow.dapr (Workflow Engine component):
This type represents the workflow engine component.
It is initialized by default without the need for a separate component YAML file.
workflowbackend.sqlite or workflowbackend.actor (Workflow Backend component):
This type represents the workflow backend component.
Initialization is based on the component YAML file provided by the user.
Users can configure and tailor the backend according to their specific requirements.
It's crucial to note that these two types are mutually exclusive and operate independently of each other. The growth and introduction of new components within each category will be handled independently


The Raspberry pi installation guide is confusing

In the raspberry pi installation guide it is mentioned to modify config.txt to add  Client ID, Client Secret, and Product ID. But the actual config.txt file has different entries which are device_serial_number, client_id and product_id. Now I know what the client_id is which I got when registering the device and its security but what are device_serial_number and product_id? When registering the device on amazon developer page we were hinted to save secuity_profile_id, client_id and client_secret. So what actually corresponds to the entried in config.txt. The naming of entries in the raspberry pi quick start page and the config.txt are not coherent/consistent and thus the confusion. Could someone tell me what shall I do here..?

Hi @sriranjanr.  Thanks for asking about this.
product_id is the second field under 'Product Information' if you click 'Manage' your device from the developer console.  It is a string you entered when you created the product.
'device_serial_number' may be any string you wish, for example in the SDK sample .config file we suggest '123456'.
Let us know if you need any further assistance with this.

I believe this issue is resolved.  Closing.  Please re-open if you'd like further input on this.


gesture_expression.pth.tar

Could you provide gesture_expression.pth.tar? Thanks

Yes, here is the link: https://drive.google.com/file/d/1Wm2WMlacwStFaciCh7UlhQeyA3E2yEnj/view?usp=sharing. Note that those checkpoints are only for autoencoders that compute features for Frechet Distance.


build the synonyms generator using stands4 api

Developer Checklist
Followed guidelines mentioned in the readme file.
Followed directory structure. (e.g. ProjectName/{USERNAME}/...yourfiles)
Starred ⭐ the Repo (Optional)
Summary
i have build the synonyms generator using html css and js where i have used stands4 api to get the json data so as to make the application work also i have made this project inorder to raise PR for hacktoberfest as it is my first one
Screenshot

Live Project Link
live-demo

hey @PBJI i resolved this issue under the label of hacktoberfest i don't understand why it is excluded from it if possible can you please put back it under the label of hacktoberfest as it is my first hacktober and i have really worked hard for it 🙇♂


Zh locale

Hi I've just added zh-CN locale files for Simplified Chinese. Let me know if there are more changes needed.

Thank you for your contribution! I may reach out to you in the future for more help if we decide to release the app in Simplified Chinese 🙂


Unable to launch after moving /usr/lib/x86_64-linux-gnu

Version
WSL version: <IP_ADDRESS> Kernel version: <IP_ADDRESS> WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22623.1037
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Ubuntu-20.04
Other Software
No response
Repro Steps
After executing the command
sudo mv /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu2

WSL is unable to launch, and I cannot operate on the directories from Explorer.
Expected Behavior
Being able to run WSL.
Actual Behavior
In Windows Terminal:
Processing fstab with mount -a failed.

<3>WSL (13) ERROR: CreateProcessEntryCommon:570: execvpe /bin/bash failed 2
<3>WSL (13) ERROR: CreateProcessEntryCommon:579: Create process not expected to return

[process exited with code 1 (0x00000001)]

Diagnostic Logs
No response

@gyk renaming /usr/lib/x86_64-linux-gnu is not a smart move! libc.so.6 lives there, along with many other libraries.  Now how can I restore WSL? All my attempts to rename it back fail because of either no privilege or directory being locked. Can I mount the VHD and change the directories from outside?


Reduce space taken by WIP PRs.

In order to prevent WIP PRs taking up lots of space on a board, thereby
reducing the amount of space for PRs ready for review, this adds an
option to have them show only the repo, and title lines on a single
line. It also sets the background colour to dark grey to de-emphasise
them a bit.
Before:

After:

Note: This is an alternative approach to #49. I've structured the option in this so that it's possible to extend it in future to support both approaches (with wiphandling=hide for example).

After feedback within my team, I've updated this to make the backgrounds of these PRs dark grey so that they stand out less. With this change, I'm no longer convinced that the option name and value are correct, but I'm not sure what a better values would be. Suggestions welcome.

👍 I'm not sure you even need an option for this, this behaviour seems much better than either hiding them, or showing them as prominently as other PRs.

I'm not sure you even need an option for this

Possibly. Removing the option would make it a slightly more controversial change to merge. Maybe we should leave it behind an option for now, and if most teams prefer this layout, we can make it the default in future.
I'm happy to remove the option if you think it's fine as is though.

Thinking about this further, if this is considered to be something that's useful to most teams, then I could update the parameter so that this behaviour is the default, and there's an option to request the original behaviour.

I've added a commit to make this the default behaviour as there seems to be consensus (based on Slack conversation). This leaves the query param in place so it can be turned off if desired.


Is this a bug?

/* Find pointer to \r\n. */
static char *seekNewline(char *s, size_t len) {
int pos = 0;
int _len = len-1;
/* Position should be < len-1 because the character at "pos" should be
 * followed by a \n. Note that strchr cannot be used because it doesn't
 * allow to search a limited length and the buffer that is being searched
 * might not have a trailing NULL character. */
while (pos < _len) {
    while(pos < _len && s[pos] != '\r') {
        pos++;
    }
    if (s[pos] != '\r') {
        /* Not found. */
        return NULL;
    } else {
        if (s[pos+1] == '\n') {
            /* Found. */
            return s+pos;
        } else {
            /* Continue searching. */
            pos++;
        }
    }
}
return NULL;

}
in this function, if (s[pos+1] == '\n') may access memory beyond s, may this cause illegal access?
for example, s is "$5\r", and the next byte in memory after the end of s is just '\n', this function can return non-NULL, but we expect a NULL return.

HI,KingHust.
I don't think this is true,cause the _len = len-1, so in the beginning of loop ,pos maximal value whuld be  len-2,and so pos+1 maximal  value whuld be len-1, this not exceed the string buf.


Using Cider in a team that has multiple developers

Hello! I'm using Cider, and we got two devs on the team.
I would love if Cider would allow us to either:

Allow generating files for each unreleased change (added, fixed, etc.) which are deleted and merged together when doing "cider release" to the actual CHANGELOG.md.
Setting custom path for the files, so that they can be in a subfolder instead of needing to be in the same path if pubspec.

Currently, we both work on different branches, but when we merge the branches having unreleased changes always creates a merge conflict we need to deal with. Having these features would make each change its own file before making a release, and we could set these changes to a subfolder so it doesn't look as messy.

Hey @f3ath anything new on this regard?

I understand the conflict happens in the "Unreleased" section when a feature branch get merged into "main". I also imagine that you have some sort of automation in place which runs "cider release" from the main branch after the feature branches are merged.
In this case the most straightforward approach I can imagine is to delegate the compilation of the release section to a simple bash script. You can designate a special folder for the devs to add feature-specific release notes as separate files which then will be iterated and added into the changelog with something as simple as
#!/usr/bin/env bash
categories=( "added" "changed" "deprecated" "removed" "fixed" "security" )
for category in "${categories[@]}" ; do
  for file in $(find "release_notes/$category" -name "*.md" | sort) ; do
    cider log "$category" "$(cat "$file")"
    rm $file
  done
done

The folder will look like this:
-release_notes
 |-added
 | |-feature1.md
 | |-feature2.md
 | |-feature3.md
 |-changed
 | |-feature3.md
 | |-feature1.md
 | |-feature2.md
 ...
 |-fixed
 | |-feature1.md

For more complex scenarios you might want to use change directly to modify the changelog before calling cider release.


Token support UI fixes

Description
A few fixes:

Fix the stroke width prop of SVGs.
Don't show the token symbol twice on the token balances screen.
Make the dismiss button in the NotificationBox gray4

Other changes

Remove dark mode code since it's not on-brand and won't be used as-is anymore.

Tested
Manually and updated unit tests.
How others should test
Check the token balances screen and icons and see that they all look good.
Related issues

Fixes #1455

Backwards compatibility
N/A

Hey @MuckT, We have verified this issue using Android internal build and iOS test flight build V:1.22.1 & updated observation in Gsheet
Gsheet Link:
https://docs.google.com/spreadsheets/d/1UVmYHl_g7ZWKqX3zBtc5OdO9wEmdAdj4PW9zgwJxUys/edit#gid=726255110
CC: @gnardini
Thanks..!!


docker-compose example, not expose just ports

in the readme, the example docker compose file
expose is for inner stuff I think, ports is how the browser gets inside
current:
version: '3.6'
services:
  wg-gen-web:
    image: vx3r/wg-gen-web:latest
    container_name: wg-gen-web
    restart: unless-stopped
    expose:
      - "8080/tcp"

I think it should be
version: '3.6'
services:
  wg-gen-web:
    image: vx3r/wg-gen-web:latest
    container_name: wg-gen-web
    restart: unless-stopped
    ports:
      - 8080:8080

@DoTheEvo you are right! Usually folks have a revers proxy running in the same network as the container so you expose and point RP to the exposed port on container. But to make thing simple i should change it to ports. PRs are welcome :)

Can I ask how one exposes the actual VPN port to the internet if only port 8080 is used? A similar container to this one known as "weejewel/wg-easy" has a port for the web UI management (51821) and then another port for the actual VPN access (51820). In comparison, is wg-gen-web always expected to be paired up with something like Caddy or can it work alone with straight router port forwarding?

wg-gen-web is a configuration generator, it assumes that your vpn service is correctly configured to pick up the config files.
you can expose web port directly if you want, it’s just in multi container setup you usually have one revers proxy exposing what need to be exposed, it’s juste a best practice.


tests drivers Uart async on stm32 boards requires dma channels config.

This defines an overlay for the dma channels when executing the tests/drivers/uart/uart_async_api on stm32 nucleo boards:

disco_l475_iot1
nucleo_f746zg
through overlay for this tests.

The DMA must be configured for the UART when asynch api is defined.
on disco_l475_iot1: UART 4 is used for testing : DMA 2 channel 3 & 5 and request 2 is selected (uart4 is already selected for this board)
on nucleo_f746zg: USART 6 is used for testing : DMA 2 channel 7 & 2 and request 5 is selected (usart6 and dma2 are already selected for this board)
For testing with the stm32f7 devices, the cache has not be disabled because of DMA (see https://github.com/zephyrproject-rtos/zephyr/pull/27911).
UART Tx pin must be connected to UART Rx pin on the board.
It also helps when running the test on other stm32 boards or running other test (ex. tests/drivers/spi/spi_loopback) with dma on those boards.
Signed-off-by: Francois Ramu<EMAIL_ADDRESS>

*** Booting Zephyr OS build zephyr-v2.5.0-368-g16677de24c1c  ***
Running test suite uart_async_test
===================================================================
START - test_single_read_setup
 PASS - test_single_read_setup
===================================================================
START - test_single_read
 PASS - test_single_read
===================================================================
START - test_chained_read_setup
 PASS - test_chained_read_setup
===================================================================
START - test_chained_read
 PASS - test_chained_read
===================================================================
START - test_double_buffer_setup
 PASS - test_double_buffer_setup
===================================================================
START - test_double_buffer
 PASS - test_double_buffer
===================================================================
START - test_read_abort_setup
 PASS - test_read_abort_setup
===================================================================
START - test_read_abort
 PASS - test_read_abort
===================================================================
START - test_chained_write_setup
 PASS - test_chained_write_setup
===================================================================
START - test_chained_write
 PASS - test_chained_write
===================================================================
START - test_long_buffers_setup
 PASS - test_long_buffers_setup
===================================================================
START - test_long_buffers
 PASS - test_long_buffers
===================================================================
START - test_write_abort_setup
 PASS - test_write_abort_setup
===================================================================
START - test_write_abort
 PASS - test_write_abort
===================================================================
START - test_forever_timeout_setup
 PASS - test_forever_timeout_setup
===================================================================
START - test_forever_timeout
 PASS - test_forever_timeout
===================================================================
Test suite uart_async_test succeeded
===================================================================
PROJECT EXECUTION SUCCESSFUL

rebase
enable dma2 and usart6 in the board overlay dts

adding a temporary patch to avoid using the cache of the stm32f7 when running the tests uart_async_api ( #31711)

give the commit for the disco_l475_iot1 only


Contact sensor event change triggers Alexa notification

Alarmo Version
1.9.12
HA Version
2023.10.5
Bug description
Whilst alarm is in disarmed tate, opening any contact sensor linked to Alarmo, causes notification being sent to Alexa that alarm has been disarmed. Usually notification is being sent only once whilst disarming alarm. Now it itriggers on any event change on contact sensor. Alarmo operates normally in Armed state.
Steps to reproduce
Alarmo in disarmed state.
Any contact sensor linked to Alarmo is being activated.
Notification is being sent to Alexa.
Relevant log output
No response

I have a similar issue.
This is the automation being triggered
alias: Alarm - Send notification for activation
description: ""
trigger:

platform: state
entity_id: alarm_control_panel.alarmo
action:
service: notify.mobile_app_xxxxxxxxx
data:
title: Alarm state changed to
message: "{{ trigger.to_state.state}}"
mode: single

this also triggers node red disarm events

Thank you for update @nielsfaber . I have sorted mine also. It was exactly the issue as described above. But it was like that since day one setting up Alarmo and there was no issue. So something has been updated in Alarmo updates that issue arised only now and started causing troubles for people. I believe this is exactly the place for people to talk about issues, especially that are linked to same integration, if no one will ask questions then there will be bunch of people scratching their heads on what is wrong. Not everyone is at advanced level of coding, or understanding full aspects of automations. There must be tons of people who are just reading and not commenting and trying to figure out things. Please @nielsfaber don't take it so personally or offencivelly this matter. No one is posting here anything with bad intentions on their mind. Thank you for understanding.

I have the same issue. After downgrade to 1.9.10v the issue is gone.
So i think that is not automation problem.
Something in the code make any sensor change to change alarm state.

I have just changed this attribute field from blank to Arm Mode and my issue was gone of false triggering.

I populated the "to" field on the trigger with "Any state (ignoring attribute changes)" as suggested by nielsfaber and this resolved the issue.
Home Assistant is evovling so sometimes we have to adjust our setups.
alias: Alarm - Send notification for activation
description: ""
trigger:

platform: state
entity_id:

alarm_control_panel.alarmo
to: null
action:

service: notify.mobile_xxxxxxxxx
data:
title: Alarm state changed to
message: "{{ trigger.to_state.state}}"
mode: single

I populated the "to" field on the trigger with "Any state (ignoring attribute changes)" as suggested by nielsfaber and this resolved the issue. Home Assistant is evovling so sometimes we have to adjust our setups.
alias: Alarm - Send notification for activation description: "" trigger:

platform: state
entity_id:

alarm_control_panel.alarmo
to: null
action:

service: notify.mobile_xxxxxxxxx
data:
title: Alarm state changed to
message: "{{ trigger.to_state.state}}"
mode: single

My one automation has few different outcomes, depending on Alarmo state, to avoid multiple other automations being created. There fore not assigning attribute was the cause of automation failing perform as intended.

Can anyone translate this to node-red? I use the "trigger state node" now.
Thanks.

How can I set "To" to null in the "trigger state" node within node-red? I can't find it. Sorry. Who can help me?

I've been able to get it to work for the most part.  Configure your trigger state as follows and it should get rid of the double trigger.

Hope this works for you.  Right now I am dealing with the fact that Alarmo is only allowing me to include sensors in the Alarmo zone for triggering the alarm when I have all sensors configured for both home and away modes.

I've been able to get it to work for the most part.  Configure your trigger state as follows and it should get rid of the double trigger.

Hope this works for you.  Right now I am dealing with the fact that Alarmo is only allowing me to include sensors in the Alarmo zone for triggering the alarm when I have all sensors configured for both home and away modes.

Thanks. It's working.


Un-meet cluster

Meeting cluster members is working as expected, but how can can I un-meet a node?
My cluster looks like this:
<IP_ADDRESS>:7711> hello
1) (integer) 1
2) "42bb9ed827379dc5c4acc733d8665f721aa2a8da"
3) 1) "f63620b151328c7d30c99ce3fbeb7d562663da4f"
   2) "<IP_ADDRESS>"
   3) "7711"
   4) "1"
4) 1) "42bb9ed827379dc5c4acc733d8665f721aa2a8da"
   2) "<IP_ADDRESS>"
   3) "7711"
   4) "1"
5) 1) "d5fcb2baba4357a22d5de699a0a55dd8737a8773"
   2) "<IP_ADDRESS>"
   3) "7711"
   4) "1"
<IP_ADDRESS>:7711> cluster info
cluster_state:ok
cluster_known_nodes:3
cluster_reachable_nodes:1
cluster_size:2
cluster_stats_messages_sent:5359
cluster_stats_messages_received:5395
<IP_ADDRESS>:7711> exit
ubuntu@mq:~$ cat /opt/disque/nodes.conf
42bb9ed827379dc5c4acc733d8665f721aa2a8da <IP_ADDRESS>:7711 myself 0 0 connected
d5fcb2baba4357a22d5de699a0a55dd8737a8773 <IP_ADDRESS>:7711 noflags 0<PHONE_NUMBER>124 connected

Node 1) does not exist any longer — how can I remove it :)?
When I forget an active ID I'm left with a single node — both the active node I just removed and the inactive one are gone.
Once I re-add the active node, I also get the inactive node back...

@xeraa now we have a much better nodes graceful removal feature (described in the README), however what you report is strange indeed. It looks like if, while doing the CLUSTER FORGET in this node, somebody was also modifying the configuration of <IP_ADDRESS> manually, by restarting it without a nodes.conf. Is this possible? That would exactly explain the behavior above.

One of the two currently existing nodes has had the IP <IP_ADDRESS> at some point in the past. But after a restart it changed its IP.
We'll upgrade Disque and see if we run into a similar issue. At the moment everything is working as expected.
Thanks for the update!


Support transitions between microfrontends

Not sure what the API or functionality will be for this yet. Some reading to help brainstorm - https://router.vuejs.org/guide/advanced/transitions.html

Some of the things that are critical for us is being able to use the same micro-app in different routes. We have a way of data transfer or message bus to pass information between the micro-apps to reset their states.
Right now, if there is an error the route transition doesn't happen smoothly. So, error handling should be part of this feature that happens when there is an error how to handle route transition.

Hi @helumalai, thanks for adding your perspective here.

Right now, if there is an error the route transition doesn't happen smoothly.

Could you help me understand what this means? What kind of error is happening, and how is the route transition not happening smoothly? Which framework are you using?

@joeldenning sorry for the late response. We're using Nx workspace for our root application and the code is in the simplest form of Angular. Recently I figured that its to do the data resolution before the page is displayed because we build the Html page with apps lists dynamically pulled from the DB. So, was hoping there was an error handling of message display when an app is not being able to load correctly.

At some point I'm hoping to share a github sample project with Nx workspace, Angular root application, and single spa micro apps since there isn't much help out there if we choose a framework like Angular/React for the root application.

So, was hoping there was an error handling of message display when an app is not being able to load correctly.

I see. Handling application errors is being tracked in https://github.com/single-spa/single-spa-layout/issues/49. The issue here being discussed is showing a UI while successfully transitioning between routes.


ci: Make doxygen dependent on PR being merged

Currently, the documentation will be rendered and updated whenever a PR is closed, even if the code wasn't merged. This update makes rendering and publishing the documentation conditional on the PR being merged.

Duplicate of #44


Remove references to Java 8

Do we have to run maven checks for Java 8 ?

@Praveen2112 for now, yes, as we are still building for Java 8. We'll fully switch to Java 11 soon.


contactusadded

Closes
Closes #1472
Description
i have added the contact us page and email icon is now visible when we hover on it
Screenshots

Note to reviewers

Checklist:

[x] I have linked the PR to the correct issue.
[x] I have read the Contribution Guidelines
[x] I have built and tested the changes, and they do not break or show any errors.

can you please review my pr @Vaishnavi-Patil2211

.

can you please review my pr @Vaishnavi-Patil2211


fix: restore blue10

:tada: This issue has been resolved in version @rubin-epo/epo-react-lib-v2.5.1 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


automatic mode 'connection broken' v5.6

Thank you so much for the quick response. I'm testing the newest version right now, and the 'connection broken' for the automatic mode still occurs in v5.6 version.
[] 2024-12-28 04:13:34 - Started recording for 150 seconds
[] 2024-12-28 04:13:34 - [PRESS CTRL + C ONCE TO STOP]
[!] 2024-12-28 04:15:00 - ('Connection broken: IncompleteRead(3065 bytes read, 1031 more expected)', IncompleteRead(3065 bytes read, 1031 more expected))
~/tiktok-live-recorder/src $
I'm not sure what happened, but when there were connection problems in v5.3 or v5.4 (AUTOMATIC mode), termux wouldn't stop and instead would retry (loop) to this process again: 'Started recording for 150 seconds'. It'd only stop once I pressed CTRL+C
However in v5.5 and v5.6 it'll stop completely and back to this message '~/tiktok-live-recorder/src $' eventho i didn't press CTRL+C.
Hopefully it's clear enough. Thanks again

Very strange, did the old version show you a different error/message?

Very strange, did the old version show you a different error/message?

The v5.3 and v5.4 didn't have this problem for the automatic mode. They would keep looping the prompt until I pressed CTRL+C manually to stop the process.

can you try it now?

can you try it now?

I've tried it, it works again! Thank you so much 😊


chore: Merge release v1.25.0 into main

Proposed Change

Merge release branch into main

Checklist

[ ] Changes are tested
[ ] CI has passed

Merging with the windows error, OOM in CI while building the test, unrelated.


Add a BuildPlan type to encapsulate jobs and job execution delegates

This builds on the proposed changes in https://github.com/apple/swift-driver/pull/180, but it'll require SwiftPM changes. I think it should be enough to start bringing up an IncrementalBuildJobExecutionDelegate

@swift-ci test

@swift-ci test

@swift-ci test


Fix InstallAppleCertificate on macOS 13.0 by providing the -sha1 parameter to OpenSSL

MacOS 13.0 comes with a newer version of OpenSSL, that defaults to SHA256 for the output instead of SHA1. Passing -sha1 as an argument restores the old behavior that was expected by getP12Properties()
This doesnt change a task instead it changes the ios-signing-common library
Documentation changes required: N
Added unit tests: N
Attached related issue: [InstallAppleCertificate] Unable to find the certificate SHA1 hash and common name (CN). Verify that the certificate is a valid P12. (Regression, MacOS 13.0)
Checklist:

[x] Checked that applied changes work as expected

Applied the Fix
And the Tfs tasks works now

Can someone please merge this if it's working and tested?
It's highly critical and breaking all iOS pipelines.

@microsoft-github-policy-service agree [company="Quality Bytes GmbH"]

@microsoft-github-policy-service agree company="Quality Bytes GmbH"

/azp run

Pls can someone merge this

/azp run

Thank you for merging. How long does is usually take until this is applied to the Azure Tasks?

Hi! how we can use this update on azure?

Hi,
Any idea when will the fix reflect on production pipelines?

I've just updated my self hosted agent to version 2.214.1 and it fails because of this bug. Any word on time to get this fix into the agent runners?

Hi @nzcodarnoc , could you please give more information about error? It seems you already have updated version -sha1 parameter.

We are facing the same problem causing failure in all of our pipelines.
Azure Devops (On-premise): AzureDevOpsServer_20230217.5
Agent.Version : 2.217.2
==============================================================================
Task         : Install Apple certificate
Description  : Install an Apple certificate required to build on a macOS agent machine
Version      : 2.200.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/install-apple-certificate
==============================================================================
/usr/bin/openssl pkcs12 -in /Users/******/Downloads/Agent/_work/_temp/beanbar_certificate.p12 -nokeys -passin pass:axiom | /usr/bin/openssl x509 -noout -fingerprint -subject -dates -nameopt utf8,sep_semi_plus_space
MAC verified OK
SHA256 Fingerprint=D3:56:3C:42:E2:78:67:B0:F2:AC:76:03:2E:8F:56:E2:75:60:73:1D:8A:11:0D:40:29:1F:24:13:72:5D:05:1E
subject= UID=382******; CN=iPhone Developer: Ste******  ou (2WG2******); OU=5CF8RPL35M; O=Axio******td.; C=CY
notBefore=Mar 14 07:41:24 2023 GMT
notAfter=Mar 13 07:41:23 2024 GMT
##[error]Error: Unable to find the certificate SHA1 hash and common name (CN). Verify that the certificate is a valid P12.
Finishing: Install Certificate

Hi @nzcodarnoc , could you please give more information about error? It seems you already have updated version -sha1 parameter.

Sorry for the delay in replying, I had another try today and it failed again.
What kind of diagnostic info do you want?


Small gap between sections in "Pico Producer 1.5 - Case.stl"

My friend and I found a couple issues with the 3d print file while trying to build one of these.
One is that there is a small gap between the sections of the base that causes a 3d print slicer to want to insert lots of extra supports, since it thinks the top half is free-floating. We were able to manually fill that gap before printing.

I uploaded mine to an online STL repair tool and after it did its thing, it was able to be sliced correctly.
I also had similar issue with one of the top places having a section filled in after slicing.
This is using Slic3r


[FE] subtitle and title are overlapping on small screens

[FE][Bug#7] subtitle and title are overlapping on small screens

Issue moved from Project Board to Project Issues [already resolved].


Support aggregation functions in order by clause but not in select clause

E.g.  get timestamps ordered by metrics.
SELECT SecondsSinceEpoch FROM myTable WHERE SecondsSinceEpoch >=<PHONE_NUMBER> AND SecondsSinceEpoch <<PHONE_NUMBER> GROUP BY SecondsSinceEpoch ORDER BY COUNT(*) DESC LIMIT 1000

why is this needed?

why is this needed?

SuperSet Filterbox requires this.


column header "Max network bandwidth (Mbps)" is incomplete and incorrect

The column header of "Max network bandwidth (Mbps)" on each of the tables with VM type specifications must be corrected to instead read "Max network egress bandwidth (Mbps)", or something similar which includes the key word "egress"..
The second paragraph of the documentation at "https://learn.microsoft.com/en-us/azure/virtual-network/virtual-machine-network-throughput" clarifies that "network bandwidth allocated to each virtual machine is metered on egress (outbound) traffic from the virtual machine".
This is important information for customers, and must be corrected as soon as possible, because the mistake presents a misconception that total (read and write) network bandwidth is being metered and limited, and that leads to confusion, distrust, and bad decisions.
FYI:  this is true across all the doc pages with tables specifying VM instance types, and I will try to submit feedback for several pages, but I don't expect to have time to submit for all pages.  Please know that these corrections must be made universally, and not just on this page alone?

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

ID: f8e3a20f-0d2c-494c-fc7c-8fa11d55e8b9
Version Independent ID: 21a70b47-94f4-5a0f-56d1-605a3e3d06cd
Content: Overview of Msv3 and Mdsv3 Medium Memory Series - Azure Virtual Machines
Content Source: articles/virtual-machines/msv3-mdsv3-medium-series.md
Service: virtual-machines
GitHub Login: @ayshakeen
Microsoft Alias: ayshak

@tigormanmsft
Thanks for your feedback!
We are going to close this thread as Duplicate of https://github.com/MicrosoftDocs/azure-docs/issues/114568.


Improve the Database Manager

This PR aims to improve the Database Manager.
Still a work in progress...

Really nice work 👍
Keep it up!
You may ignore StyleCI, a it will be fixed when merging

I will publish a new PR tomorrow cause this is just OVERcomplicated. It ended being a mess unfortunately with no actual benefits.

replaced by #648 :D :D :D :D


Different result for ktfmtFormat on Windows vs. OSX

Hi all 😀
We are using ktfmtFormat in Jewel (https://github.com/JetBrains/jewel) and we are seeing different behaviors on Windows and OSX.
Running ktfmtFormat on this commit https://github.com/JetBrains/jewel/actions/runs/10919605303/job/30307618757 on Windows will produce no changes to any files, and then when the CI runs check will error out with:
Execution failed for task ':ide-laf-bridge:ktfmtCheckMain'.
> [ktfmt] Found 1 files that are not properly formatted:
  src/main/kotlin/org/jetbrains/jewel/bridge/theme/IntUiBridge.kt

Running ktfmtFormat on Mac will change a couple of files, as shown in this commit https://github.com/JetBrains/jewel/pull/601/commits/c322d7b6b904eff7576d0bd13fa3f438befdf5ee?file-filters[]=.kt&show-viewed-files=true, rearranging a few import statements.
Running check on the CI will then succeed.
Thank you.

Hi @hick209 any chance y'all can take a look at this? @hamen can help you repro by providing Jewel commits where this happens. It's very annoying...

Yeah, it forced me to a very exhausting workflow where I need to:

run it on Windows
push the code
watch the CI failing
pull the branch on Linux
run it on Linux
push the code
watch the CI succeed

It's very time-consuming.