GoPro Hero9 control via USB issue

I'm trying to control the webcam via USB (I got it to work via Wifi).
I tried a lot of things and I can't seem to get it to work via USB.
I should note that I've downgraded my firmware to v1.22.
Here is the ip of my Hero9:

I'm also aware of these tickets, and they did help to some extent (because I was doing some things wrong): #168  and #151.
Here is my code:
from goprocam import GoProCamera
from goprocam import constants

gopro = GoProCamera.GoPro(ip_address="<IP_ADDRESS>")
gopro.take_photo()

Here is my output of my code:
Waking up...
Waking up...
Waking up...
/bin/sh: vlc: command not found
Waking up...
Error, camera not defined.

Then I get an exception at the line gopro.take_photo():
Exception has occurred: TypeError
argument of type 'NoneType' is not iterable

What should I try next?

Hi, what version of gopro-py-api are you using?

4.1.0 installed with pip

Python is not my main programming language, so bear with me :D.
I went step by step with the pycharm debugger and it seems that it gets stuck somewhere in whichCam. This line throws an exception and then it goes downhill:
response_raw = self._request("gp/gpControl")
It builds the following uri 'http://<IP_ADDRESS>/gp/gpControl'. If I try to make the request manually I get an exception like
urllib.error.URLError: <urlopen error [Errno 61] Connection refused>

Then it's not the correct IP... Have you tried with <IP_ADDRESS>?
It's very important you look at the examples, look how I did it, you pass an interface name to getWebcamIP as well as setting webcam_device to the interface name. Then it should work.

With <IP_ADDRESS> it works... but why?

Because the GoPro listens on the 51 octet of the IP.


Scanning from HEAD to first commit of feature branch scans the entire history up to HEAD.

Describe the bug
In our team, when we develop a new feature, we create the feature branch off of master, and then have individual sub-feature branches off of the feature branch where individuals do their work. This normally results in a feature branch that is nothing but merge commits, which is then merged into master.
We are trying to set up gitleaks to scan each branch from branch head to where it branches off from master (ideally, this would be the first commit to the first sub-branch that was merged into the feature branch). For our feature branches, however, this results in gitleaks scanning almost the entire repository history before finding the --commit-to hash.
To Reproduce
The following bash script, when called with a directory location, creates a repository at said location, with a history that can replicate this issue.
make_leaker.sh leaker/
#!/bin/bash
# make_leaker.sh

REPO="$1"

if [ -z "$REPO" ]; then
    echo "First argument must be new repo location" >&2
    exit 1
fi

git init "$REPO"
cd "$REPO"

COMMIT=1

make_commit() {
    msg="$1"

    branch_name="$(git symbolic-ref HEAD 2>/dev/null)" || branch_name="unnamed_branch"
    branch_name=${branch_name##refs/heads/}
    file="${branch_name}_file.txt"

    echo "$COMMIT" > $file
    ((COMMIT+=1))
    git add $file
    git commit -m "$msg"
    # Put at least 1 second between each commit to keep the git graphlog pretty
    sleep 1
}

make_branch() {
    name="$1"
    git checkout -b "$name"
}

get_branch() {
    name="$1"
    git checkout "$name"
}

make_commit "master 1"
make_commit "master 2"
make_commit "master 3"
make_commit "master 4"
make_commit "master 5"
make_commit "master 6"

make_branch feature_branch
make_branch sub_feature_branch
make_commit "branch2 1"
make_commit "branch2 2"
make_commit "branch2 3"

get_branch feature_branch
git merge --no-ff -m "merge sub_feature_branch" sub_feature_branch

get_branch master
make_commit "master 7"
make_commit "master 8"
make_commit "master 9"

The repository will have a history that looks like this:
$ git log --no-color --graph --pretty=format:'changeset:   %H%d %an <%ae> %ci%nsummary:     %s%n' --all
* changeset:   4a80e4e15c72d58bd81ffc8f13cf0fcadf8a70dc (HEAD -> master) Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:26 -0400
| summary:     master 9
|
* changeset:   b98ae921f109c6837b4cc95fc79560dd549f098f Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:25 -0400
| summary:     master 8
|
* changeset:   6ea2ed9ac4a1973234392e2c5bc04245b4ea0fe1 Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:24 -0400
| summary:     master 7
|
| *   changeset:   a9f16cb8d8d5de499c877df95782f70237ee91f1 (feature_branch) Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:24 -0400
| |\  summary:     merge sub_feature_branch
|/ /
| |
| * changeset:   d853e6d7453630aad8a3d5df4377db8f84a86e26 (sub_feature_branch) Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:23 -0400
| | summary:     branch2 3
| |
| * changeset:   2e5c124fac798e07df1128e0d5abf88aace7d95a Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:22 -0400
| | summary:     branch2 2
| |
| * changeset:   786dff1eccc6c0cd9b807a3d019bb2bd985a34ee Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:21 -0400
|/  summary:     branch2 1
|
* changeset:   6332a4302192c8651b46bac03e518d30e492b27f Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:20 -0400
| summary:     master 6
|
* changeset:   00fae103eca74cb75d962edee9d958ab005635b7 Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:19 -0400
| summary:     master 5
|
* changeset:   58d4d8d766b332a3d539f3de01ed81cc12980c9d Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:18 -0400
| summary:     master 4
|
* changeset:   1a3c08855e42ca46aee6a8160e1b39dc9318b068 Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:17 -0400
| summary:     master 3
|
* changeset:   df00fcbdd5d99a507c2b613fab556abbd4737917 Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:16 -0400
| summary:     master 2
|
* changeset:   71e63ac13e3ee23264bb7e977f0a973689bd16c5 Andrew Rowls<EMAIL_ADDRESS>2020-07-09 10:08:15 -0400
  summary:     master 1

To scan feature_branch, we use git rev-list master..feature_branch | tail -1, which yields the hash 786dff1eccc6c0cd9b807a3d019bb2bd985a34ee (the first commit on sub_feature_branch), and subsequently pass that hash to gitleaks as the --commit-to, as well as --branch=feature_branch.
docker run --rm --name=gitleaks --volume "$(pwd)":/code zricethezav/gitleaks --verbose --pretty --repo-path=/code/ --commit-to="$(git rev-list master..feature_branch | tail -1)" --branch=feature_branch

While we would like this to result in four commits scanned, we get this line at the end:
INFO[2020-07-09T14:18:01Z] No leaks detected. 10 commits audited in 5 milliseconds 364 microseconds

Indicating that gitleaks has scanned the above four commits, as well as the six commits before that on master.
Furthermore...
Using the most recent common parent, 6332a430, causes gitleaks to stop before it has scanned any commits in the feature branches:
$ docker run --rm --name=gitleaks --volume "$(pwd)":/code zricethezav/gitleaks --verbose --pretty --repo-path=/code/ --commit-to="6332a4302192c8651b46bac03e518d30e492b27f" --branch=feature_branch
INFO[2020-07-09T15:51:19Z] No leaks detected. 2 commits audited in 1 millisecond 338 microseconds

Expected behavior
In the first case, ideally, gitleaks will scan the commits a9f16cb8, d853e6d7, 2e5c124f, and 786dff1e, and stop.
Minimally, I'd expect gitleaks to see 786dff1e and stop long before it reaches 71e63ac1, the beginning of the history.
In the second case, I'd expect gitleaks to scan all 5 commits between the feature_branch HEAD and common parent 6332a430, inclusive.
Basic Info (please complete the following information):

OS: ubuntu linux
Gitleaks Version: v4.3.1

cc @zricethezav

Gitleaks uses go-git as it's git library and doesn't provide a branch filter. Instead it will attempt to find the reference with the branch name and use that commit as the starting point. The problem with this is branches that have been merged in create a merge commit which has two parents. Git log will traverse the commit prior to branching first, then the commits within the branch before continuing. This is why you're getting more commits scanned than you intend.
The inclusion of a9f16cb8d8d5de499c877df95782f70237ee91f1 in your case is the problem. Adding the branch option is somewhat contentious and there is an argument that it should be removed as it will always be overzealous when scanning.
I recommend you manually set the commit-to and commit-from as is demonstrated in gitleaks-action.
I'll be looking more into this but that's what I got for now.
cc @eternicode

Closing this, reopen if my answer did not provide you with enough information


numpy error when running go_web.bat

RuntimeError: module compiled against API version 0x10 but this version of numpy is 0xf

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "H:\blah blah had to move these\X\RVC\RVC-beta-v2-0528\infer-web.py", line 84, in <module>
    from vc_infer_pipeline import VC
  File "H:\blah blah had to move these\X\RVC\RVC-beta-v2-0528\vc_infer_pipeline.py", line 5, in <module>
    import pyworld, os, traceback, faiss, librosa,torchcrepe
  File "H:\blah blah had to move these\X\RVC\RVC-beta-v2-0528\runtime\lib\site-packages\pyworld\__init__.py", line 7, in <module>
    from .pyworld import *
  File "pyworld\pyworld.pyx", line 6, in init pyworld.pyworld
  File "__init__.pxd", line 944, in numpy.import_array
ImportError: numpy.core.multiarray failed to import```

Is there another python runtime in your system?

I faced the same issue and it turns out there IS another python runtime, I went to "C:\Users\user\AppData\Roaming\Python" and removed Python39 and it works. It was an installation from an old project so yeah.

all i had to do to fix it was remove numpy from a python 3.9 i also had on
my system that i dont know where i used it
On Thu, Jun 8, 2023 at 11:07 AM Rajendayo @.***> wrote:

I faced the same issue and it turns out there IS another python runtime, I
went to "C:\Users\user\AppData\Roaming\Python" and removed Python39 and it
works. It was an installation from an old project so yeah.
—
Reply to this email directly, view it on GitHub
https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI/issues/464#issuecomment-1582769126,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHENGQYPSUTHDSHOIN6W2M3XKHTC7ANCNFSM6AAAAAAY5QDLL4
.
You are receiving this because you authored the thread.Message ID:
<RVC-Project/Retrieval-based-Voice-Conversion-WebUI/issues/464/1582769126@
github.com>


Allow to customize flags for file decoders

E.g. to append to an existing file.

Yeah, I went through the same thought process on this one. At least it's not default args 🙃

My only hesitation with this style of overload in general is that they are a nuisance for partial application.  This breaks source compatibility.  But I doubt very many people are using it that way here.


fix : HBASE-28585. Add namespace handling method in copy_tables_desc.rb

When utilizing the copy_tables_desc.rb script to duplicate tables to a target cluster, if the specified table's namespace is nonexistent in the target cluster, the script fails to execute successfully. It is recommended to incorporate logic within the script for detecting and handling scenarios where the namespace does not exist.
and fix spelling errors.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m  9s
Docker failed to build run-specific yetus/hbase:tp-13365}.

 U: .

 U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5884/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
spotless
0m 45s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

-0 :warning:
rubocop
0m  4s
The patch generated 4 new + 3 unchanged - 1 fixed = 7 total (was 4)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
spotless
0m 39s
patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 11s
The patch does not generate ASF License warnings.

3m 19s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5884/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5884

Optional Tests
dupname asflicense spotless rubocop

uname
Linux d29cd940d8e8 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 23fa363d36

rubocop
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5884/1/artifact/yetus-general-check/output/diff-patch-rubocop.txt

Max. process+thread count
43 (vs. ulimit of 30000)

modules
C: . U: .

 U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5884/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
spotless
1m  3s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
rubocop
0m  5s
/results-rubocop.txt
The patch generated 4 new + 3 unchanged - 1 fixed = 7 total (was 4)

+1 :green_heart:
spotless
0m 58s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 16s

The patch does not generate ASF License warnings.

4m 21s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5884/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5884

Optional Tests
dupname asflicense codespell detsecrets rubocop spotless

uname
Linux 5b1422f33920 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / db9a3bbc181783a37a149c47666d6f18202d49fd

Max. process+thread count
45 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5884/1/console

versions
git=2.34.1 maven=3.9.8 rubocop=1.37.1

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m  0s

Docker mode activated.

-1 :x:
patch
0m  6s

https://github.com/apache/hbase/pull/5884 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/5884

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5884/2/console

versions
git=2.17.1

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m  0s

Docker mode activated.

-1 :x:
patch
0m  7s

https://github.com/apache/hbase/pull/5884 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/5884

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5884/2/console

versions
git=2.25.1

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

Merged to master. Could you please raise backports for branches where you want to push this? Also we follow a practice please ensure to keep JIRA title and PR title in sync.

💔 -1 overall
Vote	Subsystem	Runtime	Logfile	Comment
+0 🆗	reexec	0m 0s		Docker mode activated.
-1 ❌	patch	0m 7s		#5884 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.
Subsystem	Report/Notes
GITHUB PR	#5884
Console output	https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5884/2/console
versions	git=2.25.1
Powered by	Apache Yetus 0.15.0 https://yetus.apache.org
This message was automatically generated.

Oops did not realize that the build had not completed. let me build master locally to ensure no issues!

JIRA title

Okay, I will update the JIRA title later.

Okay, I will update the JIRA title later.

Hey I had sync'ed it for this particular one. No actions needed from your end for the title.

Oops did not realize that the build had not completed. let me build master locally to ensure no issues!

Built code locally. All good.
[INFO] Reactor Summary for Apache HBase 4.0.0-alpha-1-SNAPSHOT:
[INFO]
[INFO] Apache HBase ....................................... SUCCESS [  5.440 s]
[INFO] Apache HBase - Checkstyle .......................... SUCCESS [  1.450 s]
[INFO] Apache HBase - Annotations ......................... SUCCESS [  1.963 s]
[INFO] Apache HBase - Build Configuration ................. SUCCESS [  0.185 s]
[INFO] Apache HBase - Logging ............................. SUCCESS [  2.515 s]
[INFO] Apache HBase - Shaded Protocol ..................... SUCCESS [01:23 min]
[INFO] Apache HBase - Common .............................. SUCCESS [ 20.177 s]
[INFO] Apache HBase - Metrics API ......................... SUCCESS [  4.258 s]
[INFO] Apache HBase - Metrics Implementation .............. SUCCESS [  4.218 s]
[INFO] Apache HBase - Hadoop Compatibility ................ SUCCESS [  8.100 s]
[INFO] Apache HBase - Client .............................. SUCCESS [ 21.260 s]
[INFO] Apache HBase - Zookeeper ........................... SUCCESS [  6.259 s]
[INFO] Apache HBase - Replication ......................... SUCCESS [  5.371 s]
[INFO] Apache HBase - Balancer ............................ SUCCESS [  8.504 s]
[INFO] Apache HBase - Resource Bundle ..................... SUCCESS [  0.474 s]
[INFO] Apache HBase - HTTP ................................ SUCCESS [ 12.876 s]
[INFO] Apache HBase - Asynchronous FileSystem ............. SUCCESS [  9.745 s]
[INFO] Apache HBase - Procedure ........................... SUCCESS [  7.499 s]
[INFO] Apache HBase - Server .............................. SUCCESS [01:36 min]
[INFO] Apache HBase - MapReduce ........................... SUCCESS [ 16.681 s]
[INFO] Apache HBase - Testing Util ........................ SUCCESS [ 10.163 s]
[INFO] Apache HBase - Thrift .............................. SUCCESS [ 25.576 s]
[INFO] Apache HBase - Shell ............................... SUCCESS [  9.543 s]
[INFO] Apache HBase - Coprocessor Endpoint ................ SUCCESS [ 10.109 s]
[INFO] Apache HBase - Backup .............................. SUCCESS [ 10.252 s]
[INFO] Apache HBase - Integration Tests ................... SUCCESS [ 13.574 s]
[INFO] Apache HBase - Rest ................................ SUCCESS [ 11.045 s]
[INFO] Apache HBase - Examples ............................ SUCCESS [ 13.298 s]
[INFO] Apache HBase - Shaded .............................. SUCCESS [  0.526 s]
[INFO] Apache HBase - Shaded - Client (with Hadoop bundled) SUCCESS [ 51.967 s]
[INFO] Apache HBase - Shaded - Client ..................... SUCCESS [ 22.635 s]
[INFO] Apache HBase - Shaded - MapReduce .................. SUCCESS [ 40.895 s]
[INFO] Apache HBase - Extensions .......................... SUCCESS [  0.106 s]
[INFO] Apache HBase - OpenSSL support for TLS RPC ......... SUCCESS [  0.138 s]
[INFO] Apache HBase - External Block Cache ................ SUCCESS [  6.373 s]
[INFO] Apache HBase - HBTop ............................... SUCCESS [  4.570 s]
[INFO] Apache HBase - Compression ......................... SUCCESS [  0.109 s]
[INFO] Apache HBase - Compression - Aircompressor ......... SUCCESS [  6.908 s]
[INFO] Apache HBase - Compression - Brotli ................ SUCCESS [  5.480 s]
[INFO] Apache HBase - Compression - LZ4 ................... SUCCESS [  5.499 s]
[INFO] Apache HBase - Compression - Snappy ................ SUCCESS [  5.601 s]
[INFO] Apache HBase - Compression - ZStandard ............. SUCCESS [  5.926 s]
[INFO] Apache HBase - Assembly ............................ SUCCESS [02:50 min]
[INFO] Apache HBase - Shaded - Testing Util ............... SUCCESS [01:48 min]
[INFO] Apache HBase - Shaded - Testing Util Tester ........ SUCCESS [  8.194 s]
[INFO] Apache HBase Shaded Packaging Invariants ........... SUCCESS [  6.801 s]
[INFO] Apache HBase Shaded Packaging Invariants (with Hadoop bundled) SUCCESS [  3.309 s]
[INFO] Apache HBase - Archetypes .......................... SUCCESS [  0.111 s]
[INFO] Apache HBase - Exemplar for hbase-client archetype . SUCCESS [  6.281 s]
[INFO] Apache HBase - Exemplar for hbase-shaded-client archetype SUCCESS [  7.828 s]
[INFO] Apache HBase - Archetype builder ................... SUCCESS [  1.602 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  14:54 min
[INFO] Finished at: 2024-09-27T07:28:53Z
[INFO] ------------------------------------------------------------------------


Split build steps

It was first a response to: https://github.com/esy-ocaml/hello-reason/pull/66#issuecomment-633743594 And I have added some explanations why we use low-level command.

ping @ulrikstrid


return node ID during launch failure

If a workload fails to launch due to a launcher failure, return the node ID along with the existing information.

@markdryan this would make my life so much easier right now. I started trying to do this myself, and realized it would probably be something really fast for you to do, and I'm having a hard time figuring out where you store node id. Probably all the launcher failures could do to have the nodeid tacked onto them.

Yep, I'll do this right now.  I'm trying to work out whether its worth including the node-id when there are other failures.  Strictly, speaking it isn't necessary as you've got the instance id and so you could   use this to find out the node-id.  Having said that, you won't be able to do this if the instance has already been deleted, or stopped, so maybe it's best to include it in all node generated errors.


Add a Github Action that will validate that latest headless shell always with docker

See: Issue #1476
This github action clearly demonstrates the failure mode running the latest headless-shell release with docker.
It also clearly shows that release 125.0.6422.142 works using docker.
As per the comments from Brad Peabody in #1476, the latest release listens on localhost:9222 where as release 125.0.6422.142 listens on <IP_ADDRESS>:9222. This github actions shows exactly the same behaviour - i.e. the newer release is listening on the wrong network.
As sample run can be seen in my fork:
https://github.com/owenwaller/chromedp/actions/runs/9548695344/job/26316470829

I was able to reproduce this problem with podman on MacOS:
Older version, works:
bradgp@Brads-MacBook-Pro ~ % podman run -d -t -p 19222:9222 --name chromedp-125.0.6422.142 chromedp/headless-shell:125.0.6422.142
cf77899d0331abb69df19e70999339577896dd8ce408bc9e575a1fd309a86843
bradgp@Brads-MacBook-Pro ~ % podman exec -it chromedp-125.0.6422.142 bash -c 'apt -qq update && apt install -qq -y iproute2 > /dev/null 2>&1 && ss -a | grep 9222'
All packages are up to date.
tcp   LISTEN    0      0                                                       <IP_ADDRESS>:9222                   <IP_ADDRESS>:*
bradgp@Brads-MacBook-Pro ~ % curl http://localhost:19222/json/version
{
   "Browser": "Chrome/125.0.6422.142",
   "Protocol-Version": "1.3",
   "User-Agent": "Mozilla/5.0 (X11; Linux aarch64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.6422.142 Safari/537.36",
   "V8-Version": "<IP_ADDRESS>",
   "WebKit-Version": "537.36 (@018a22c382fa9eec68d3d658f380093ecfe34d28)",
   "webSocketDebuggerUrl": "ws://localhost:19222/devtools/browser/87523ffe-e39b-4b27-8270-3f183712f880"
}

Newer version, does not work:
bradgp@Brads-MacBook-Pro ~ % podman run -d -t -p 29222:9222 --name chromedp-126.0.6478.26 chromedp/headless-shell:126.0.6478.26
e580ab3a307939a41cf0d6a8ad06ffd3e003cb0ec867bac75ff957ac741fe942
bradgp@Brads-MacBook-Pro ~ % podman exec -it chromedp-126.0.6478.26 bash -c 'apt -qq update && apt -qq install -y iproute2 > /dev/null 2>&1 && ss -a | grep 9222'
All packages are up to date.
tcp   LISTEN    0      0                                                     <IP_ADDRESS>:9222                   <IP_ADDRESS>:*
bradgp@Brads-MacBook-Pro ~ % curl http://localhost:29222/json/version
curl: (52) Empty reply from server

In case it helps, it looks like Chromium may have vaporized the --remote-debugging-address=<IP_ADDRESS> option upstream: https://issues.chromium.org/issues/41487252


Ordinal Dimensions: Status are alphabetically ordered, and not according to their schema:position

Describe the bug
I opened the Red List dataset and created this visualization: https://test.visualize.admin.ch/fr/v/Xs3DEBS67IGw But the status are alphabetically ordered, and not according to their schema:position. Or do I have a mistake in the data ?
To Reproduce
Steps to reproduce the behavior:

Go to '. https://test.visualize.admin.ch/fr/v/Xs3DEBS67IGw'
The name of the dataset in visualize is: "Listes Rouges (from INT) tst"

For information, here is the "ORDERING" for the status (second column):
CODE_ID;Order;Description_DE;Description_FR
EX;7;weltweit ausgestorben;éteint à l'échelle mondiale
RE;6;ausgestorben in der Schweiz;éteint en Suisse
CR;5;vom Aussterben bedroht;au bord de l’extinction
EN;4;stark gefährdet;en danger;fortemente minacciato
VU;3;verletztlich;vulnérable;vulnerabile;vulnerable
NT;2;potenziell gefährdet;potentiellement menacé
LC;1;nicht gefährdet;non menacé;non minacciato
DD;0;ungenügende Datengrundlage;données insuffisantes
Expected behavior
The ordering should be according to the schema:position above and not alphabetical
Screenshots

Environment (please complete the following information):

Visualize environment and version: TEST

Additional context
https://gitlab.ldbar.ch/bafu/umweltdatenkiosk-planning/-/issues/317

@sosiology I assume thats because the order is selected here:

I've forced the sorting to consider the position attribute if the dimension is nominal. I did not see your previous comment @AnninaWalker , I guess the most obvious thing here so that the user can either sort by name or by position in case of nominal dimension, would be to add a new option to this select "Position", and have it automatically chosen for Nominal dimensions. Does it make sense to you ?

Yes I thinks that makes total sense ;-)

In fact, the ordinal dimensions do not have the Sorting options enabled as they already have defined order.


RoundRobin multi-asset coin-selection integration in cardano-wallet

Issue Number

ADP-506 / ADP-605
Overview

395b9542449c832178c51a1179440c6001510983
:round_pushpin: remove migration selection handlers until rework
Most of the code doesn't apply anymore because of the way we've changed how coin-selection works. So I've simply thrown everything away. It'll be possible to look at git later when re-implementing this to get some inspiration. It is also very likely that we may want to do things slightly differently, the problem and context being now different.

bc3d0a600832499cd40347bd5a82fbaae8dbb987
:round_pushpin: rework 'TransactionLayer' to play well with RoundRobin MA selection algs.
The main change compared to before is the unification of all 'mkStdTx', 'mkDelegationJoinTx' and 'mkDelegationQuitTx' under one single interface 'mkTransaction'. We know for sure that this is possible because that's exactly how things are implemented behind the scene in the cardano-wallet package. This is a quite disruptive change, but should help really help simplifying the coin selection code which has grown large and complex over the past months with many pitfalls and logic duplication here and there.
Another major change is the introduction of a 'TransactionCtx' type which should help unifying the caller interface in a more elegant way, instead of having to hand-craft every single argument by hand depending on the function to call. The main idea behind this 'TransactionCtx' is that it contains details about the transaction that are known prior to constructing the transaction. Typically, they'd come from the surrounding context (e.g. the current time) or, be user-provided.

84465c5c601544f55a60e240def3b3e722b5ed26
:round_pushpin: parameterize 'SelectionResult' over the change's inner type
The reason for this is to be able to re-use the 'SelectionResult' at various stages in the wallet layer, before and after having assigned change address to each change output.
It opens room for writing nice functions such as: 'assignChangeAddress :: SelectionResult TokenBundle -> s -> (s, SelectionResult TxOut)' which, from its type signature informs
nicely about what it is doing.

fc7260badb5fc30bb005c0ccf16a475fde7a3b38
:round_pushpin: add 'extraCoinSource' to 'SelectionResult'
So that we can fully construct transaction metadata from a 'SelectionResult' and need not to re-do any extra computation or pass extra arguments about withdrawals and reclaims.

0a99a26ed61e76aaa6b85246d260c4b8f09f354a
:round_pushpin: add outputsCovered to 'performSelection', to make it possible to fully reconstruct a tx from a result
Adding it as a list to cope with delegation selections which have no outputs.

09b9b14ca2e3a63a98982319a81cf8419f521cdf
:round_pushpin: decouple deposits from 'estimateFee'
Fees and deposits are closely related but that aren't the same thing. So it's better to keep the fee estimation about fees, and leave deposits out of it.

8486593f9f35c52af1975ad3adc4c9945b331785
:round_pushpin: integrate RoundRobin Multi-Asset selection and new transaction layer in the wallet layer

1a48de27d4c983ae0602e4770cb4c0afe6313ab9
:round_pushpin: upgrade the server handlers to use the upgraded multi-asset wallet layer.

b1a09c472e17210f5090f8cb245d2748a5a0a8b0
:round_pushpin: add simple conversion function to '../Types/Coin.hs' from Coin to integrals

524d5b5df0fd5e91f752cfe4a2f4f7d74cc995ef
:round_pushpin: move 'calcSelectionDelta' to '.../MA/RoundRobin' and make it work for all 'SelectionResult' types
We need this in two places, on 'SeletionResult TxOut' and 'SelectionResult TokenBundle'.

7e49ff1d49dd6b187c649da992d2d22de7c6b5d2
:round_pushpin: Upgrade cardano-wallet package to work with new TransactionLayer

fda6581a16193ee3a2e83cf2549e90003d6ae6b3
:round_pushpin: Adjust error messages assertions in integration tests
To match new errors generated from the multi-assets selection.

2eb1e7b06d767bf25e362683bac2a449ed914d61
:round_pushpin: return and catch required cost with 'UnableToConstructChangeError'
So that we can still return a value when users want to estimate fees but there's not enough money to run a full selection. Though, what we really need is a complete rework of the how transaction are created which does not rely on fee estimation.

8fc5683a25beea31a7729465fa8816f0b72580b0
:round_pushpin: run 'coinSelector' last in the multi-asset selection.

aee4f87c299bfa5a8f7418d56b03d6e177da5890
:round_pushpin: implement pure version of 'selectionToUnsignedTx' for external coin selections
Did rework a bit how 'selectAssets' also work and allowed callers to pass an extra transformation function on the result as argument, using the state with which the selection was calculated. This allows for callers to run some extra computations on the exact same state. We have two use-cases for this particular argument:

Fee estimation functions, which transform the selection result into a 'Coin'
So-called external selections ran for read-only wallets, which transform the selection into an 'UnsignedTx' with fully qualified (i.e. with derivation paths) inputs and change.

61c48723812acd3b415bc22372b38a0d7661cd4f
:round_pushpin: Update types in RoundRobinSpec test suite.
This change updates various types within the RoundRobinSpec test suite in
light of recent changes to the RoundRobin module, allowing it to compile.

6c595e90f63e1a6fd82f83b7b290b76622b9cf5d
:round_pushpin: Test the value of outputsCovered returned by performSelection.
In particular, we wish to ensure the following property holds:

outputsCovered == outputsToCover

2650cfff2d87dcfce912e393f8ba2ccbad4c35ba
:round_pushpin: remove now obsolete coin-selection modules.

b34a575a344d92fb9a7db3dc87fce02cdb72aaa3
:round_pushpin: rename 'missingCoins' field to 'shortfall' in the MA selection change error

5264ba9da52f7af56bd75a5a3b064deca24739f9
:round_pushpin: introduce 'defaultTransactionCtx' to avoid repetition of empty contexts in various situation

e6319b176395ce832be2dbe5b38d10f4c90f7b99
:round_pushpin: update benchmarks & shelley transaction specs to work with new transaction layer.

6080b021fd311e8744f141cb4ad36827bc99f863
:round_pushpin: do not count external withdrawals as 'ours' when constructing tx metadata

64629400dd3415f267a453ebf6e2a51c7e7d61db
:round_pushpin: make sure to count user-specified outputs that are ours when constructing tx meta

3ff070ffcdeb4bd98818e40a4bfb101b041fef03
:round_pushpin: finish implementation of 'calcMinimumCoinValue' to also account for multi-assets

ebde06041a3a0864a476c80484a1661b97a8231b
:round_pushpin: fix stake pool tests and transaction metadata reporting

581309db1149e5172c434e9eb931744dd782ba30
:round_pushpin: remove now obsolete 'TransactionSpecShared' module.

a606ca9b03c20493626d4e7148c1d6ae3af8bb52
:round_pushpin: make 'estimateMaxNumberOfInputs' aware of multi-assets outputs.
And adjust unit tests accordingly.

9b9bd2f989f1c26f856b86e3ce3f63cefad71c05
:round_pushpin: use current mainnet value as tx max size in unit test
So that we get some order good of magnitudes when it comes to what can be expected for Mainnet.

971cd17a61a7adf087be680743eca445aaa18ffd
:round_pushpin: remove integration coin selection scenarios that are no-longer applicable.
Indeed, the wallet now always create a change output. The only way
to empty a wallet is to use the migration / swapping endpoints.

805e95210102d036f6f60e8697565fc878feb134
:round_pushpin: temporarily disable test integration migration scenarios
Until the endpoints handlers are re-implemented.

Comments

Known issues / remaining work so far:

[x] 1. Transactions with withdrawals from an external wallet are wrongly labeled as "Incoming".

[x] 2. calcMinUTxOValue needs to be properly implemented (see PR #2461)

[x] 3. Some picky tests regarding stake pools which work from very precise fee amounts needs to be updated because expected fees are no longer matching.

[x] 4. estimateMaxNumberOfInputs only consider ada-only assets, resulting in estimation that can be way above the real one. Needs to account for the actual output shape.

[x] 5. The equivalent of amount for multi-assets on transaction is currently always blank, instead of being assigned with the delta between inputs and outputs.

[ ] 6. assets are missing from the external selections API, although the underlying code is already capable of running multi-asset external selections

[ ] 7. assets are missing from the Byron API endpoints, whereas it is actually completely possible to have a Byron wallet with native assets.

[ ] 8. Wallet migrations / swapping has been disabled

bors try

bors try

bors try

bors try

bors r-

bors r-

bors r+

bors r+

bors r-

bors r-

bors try
ffs.

bors try
ffs.

What was happening with bors? The other day it seemed like the GitHub CI status and commit notifications APIs were really slow. Bors relies on notifications from github to trigger builds.

What was happening with bors? The other day it seemed like the GitHub CI status and commit notifications APIs were really slow.


newt: 0.52.20 -> 0.52.21

https://pagure.io/newt/blob/134326743ac8063f79b6b34eb9d80ffdd55e6540/f/CHANGES#_1

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

staging version of #62181 .


Support for Finnish language and tiny size setting

This pull request adds support for Finnish language and also a smaller than small size ("tiny"), as Finnish words are quite long and the clock would not fit to my screen even on small setting.

@jannekalliola the pipelines fail on two linter errors. If fix those I'll merge the PR!


MudSelect Multiselect throws compile error in 5.2.0

Bug type
Component
Component name
MudSelect
What happened?
After upgrading from MudBlazor 5.1.5 to 5.2.0 I'm getting the following error when building for all my pages/components where there is a multi select MudSelect
error CS1503: Argument 2: cannot convert from 'Microsoft.AspNetCore.Components.EventCallback<System.Collections.Generic.HashSet<MyModel>>' to 'Microsoft.AspNetCore.Components.EventCallback'
Happens on all multi select instances
It was T="MyModel" SelectedValuesChanged="OnRolesSelected" before and that fails, I changed the function definition from HashSet to IEnumerable and still I have the same issue.
I even tried  T="MyModel" SelectedValuesChanged="@(roles=> OnRolesSelected(roles))"
I've searched through the issues and I found this snippet in #2462  https://try.mudblazor.com/snippet/QkQlkCFPwqLRjuIj
Its the exact same error I am getting in my current project

Expected behavior
EventCallback signatures should match
Reproduction link
https://try.mudblazor.com/snippet/GOcFaNmedLtnLmDA
Reproduction steps

Upgrade MudBlazor from 5.1.5 to 5.2.0
Leave all MultiSelects unchanged, which were working in 5.1.5
Compile/Build. Error is shown when a build is run

Relevant log output
No response
Version (bug)
5.2.0
Version (working)
5.1.5
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

I missed 3 very important changes in the release notes, i am really sorry for that and have updated them now.
https://github.com/MudBlazor/MudBlazor/releases/tag/v5.2.0

@Garderoben Thanks for the update, but I am still getting the same error when I change from HashSet<T> to IEnumerable<T> or ICollection<T>
This is from the build output
7>D:\Projects\New\src\Client\Microsoft.NET.Sdk.Razor.SourceGenerators\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\Pages_Core_AddEditMemberModal_razor.g.cs(309,168,309,183): error CS1662: Cannot convert lambda expression to intended delegate type because some of the return types in the block are not implicitly convertible to the delegate return type 7>D:\Projects\New\src\Client\Pages\Company\AddEditIndividualModal.razor(52,109,52,124): error CS1503: Argument 2: cannot convert from 'method group' to 'EventCallback'
as an example this is a multi select I am implementing
<MudSelect  T="GetAllRoleTypesResponse"  ToStringFunc="@_funcRoleToName" MultiSelection="true" SelectedValuesChanged="OnRolesSelected" SelectedValues="@_selectedRoles" Dense="true" Label="Select Roles in Organization">
	@foreach (var role in _roles)
	{
		<MudSelectItem Disabled="@(role.Code=="EMPL")"  Value="@role" />
	}
</MudSelect>

private void OnRolesSelected(ICollection<GetAllRoleTypesResponse> roles)
		{
			_selectedRoles = roles.ToHashSet(); //I have to use ToHashSet because I've used HashSet everywhere in compliance with 5.1.5
			AddEditIndividualModel.Roles = _selectedRoles.ToList();
		}

I can't seem to figure it out what exactly I am missing here.

If possible can you show a simple working implementation in the sandbox? Thanks!

Adding another comment as Update, since I figured out what I was doing wrong, in some cases I am using @bind-SelectedValues="_myVariable"
and in some cases I am using  SelectedValuesChanged="@OnRolesSelected" SelectedValues="@_selectedRoles" callback,
the issue here is in the first case, _myVariable was HashSet. I had to change this to IEnumberable for it to build without errors (and then convert it to HashSet in my code elsewhere because everything is handled as HashSet)
In the Second case _selectedRoles works even if its HashSet
ngl, this is a bit confusing

After updating to MudBlazor 6.02 the "@bind-SelectedValues" now returns this compile time error.

I can work around it by using SelectedValuesChanged instead but it was an unpleasant surprise.

I'm working with MudBlazor for the first time in a while. @bind-SelectedValues is still broken, as described above, in 6.8.0.


[collapsible-menu-view] Expose additional styling, alignment options for collapsible-menu-view

Summary
Expose additional styling, alignment options for collapsible-menu-view.  Exposing 5 new props to allow for additional customization:  menuItemButtonVariant, menuItemDropdownButtonIsIconOnly, menuItemDropdownButtonIcon, menuItemDropdownButtonVariant, horizontalAlign.
Closes #1444
Deployment Link
https://terra-framework-deployed-pr-1444.herokuapp.com/
Testing
Have tested with the exampled created
Additional Details
This is still missing exposing the variant style for button groups as well.  The current examples with the different variants only apply for terra-buttons.

Thank you for contributing to Terra.
@cerner/terra

Closing and team will implement what they need within their project. Can be reviewed again later if UX allows for more flexibility with button-groups(terra-core/pull/3477)variants and including them in collapsible-menu-view.


Work flow

Still need to update documentation for running tests instructions

This is good work.  It is also a lot ;)
I spot checked what is going on, but I would also like to dig in further after I eat some protein :rofl:
I think there is a great opportunity to add some further refactoring to the tests here, and it might be beneficial to do all of that in one go.
There are various architectures that could be used now that there is a Makefile.  For example:
solution.scm
Makefile
tests/test.scm
tests/test.sls

@jitwit how do feel about putting this in feature or another base branch for a little while, so we can make some more substantial changes before launching? It would seem advantageous to me if a couple iterations of upgrades to our testing framework happened in isolation before getting sent out to students.
Let me know if you are down to handle it this way.
PS. I am not glued to the example architecture. It was just a convenient example :smile:

I'd prefer to incorporate this sooner rather than later just because it makes adding problems a lot more natural. It also makes for better student development.
It would be great to start another branch to explore more complicated exercise architectures as you say though!


Gaze evaluation in MPIIGaze(Normalized data)

Hello,  I use the ELG_i6036_f6036_n32_m2 model to get landmarks, method estimate_gaze_from_landmarks in models.elg to get gaze angle. Then I test in MPIIGaze data selected from Evaluation Set, ground truth and eye images  are  in normalized space.
I got a mean angular error(degrees) 9.56. It seem that model-based method performance not so good in MPIIGaze data.
Does the methods in code for gaze estimation only has Model-based Estimation? I can't find the model about SVR trained in MPIIGaze.
Maybe I need to train a SVR model in MPIIGaze data that will performance better than model-based? Does you manually annotated eyelid and iris landmarks in MPIIGaze to train the SVR?
In case I made a wrong evaluation. I post one MPIIGaze normalized sample tested used gazeML, for pitch angle ,up is positive, for yaw angle, left is positive.
#img_name#  p00/day14/0326.jpg
#eye_side#:  left
#3D gaze_vector#:  -0.01114 0.25135 0.9678
#true gaze angle(degrees) [pitch,yaw]#:  [-14.5578 0.6596]
#gazeML pre gaze angle(degrees)[pitch,yaw]#:  [-5.7414 0.9097]
#angular error(degrees)#: 8.8198

The ELG_i6036_f6036_n32_m2 is trained on UnityEyes Dataset. If you want to evaluate on MPIIGaze dataset, you can check cross dataset evaluation section in the paper.

@MinjingLin Have you solved the problem? I want to test the model for gaze estimation too but can't find the code. Besides, I guess the # angular error # used in the paper is # mean angular error # which should be 8.8 / 2 = 4.4? I'm not sure about it.

Update, I found how to compute the angular error (gaze estimation error) in this paper: He, Z., Spurr, A., Zhang, X., & Hilliges, O. (n.d.). Photo-Realistic Monocular Gaze Redirection Using Generative Adversarial Networks. 6932–6941. (Page 5)


Windhelm NPC stuck

First time going in windhelm and this npc is just stuck on a rock stepping forward once and backwards repeatedly

Quick update I've actually just interacted with him and he doesn't have a voice.

Are you able to click him in the console and get the information from there?

Of course here it is

What plugin is the NPC added by?

He's gone now. Just disappeared. It was an imperial guy though. When I interacted with him I can respond with- "what is an imperial doing in windhelm" so I assume it's a plugin of imperial NPC's in stormcloak cities not sure

Yeah, that's weird. Some odd pathing issue possibly and the NPC teleported away. I can say I've never seen an NPC on that rock in the picture in either of my playthroughs.

I'll go ahead and close this for now, in the event this happens again we can address it further.


allow vscode.open to be called with a string in additon to an Uri

This PR helps with https://github.com/microsoft/vscode/issues/140907 by allowing to call vscode.open with strings in addition to uri-instances. That helps to avoid encoding issues

We probably already have tests for vscode.open, so maybe we can add one for a string argument.

I think that test fails for web integration tests.

Yeah... Took me really long to understand, the issue that we don't transform that uri scheme, e.g we continue with file. I will tweak the command to only support http-links as strings, and I will remove the test because we cannot test http link opening


audioDataList WIth No Json

How to made it read from the file audio and not include the json file?
@rutvik110

this will only work for uncompressed audio file data like PCM/WAV as depicted here:
List calculateJson(
{int PCMformat, int bits, int channels, int sampleRate, Uint8List PCMamplitudesData, int blockSize,}) {
List filteredData = [];
List rawSamples = [];
int amplitude = 0;
if (bits == 24) {
// https://wiki.multimedia.cx/index.php/PCM
int sample = 0;
Map<int, List> LPCM = {};
while (sample + 6 * channels < PCMamplitudesData.length) {
amplitude = 0;
for (int c = 0; c < channels * 2; c++) {
List LPCMc = [];
LPCMc.add(PCMamplitudesData[sample + c * 2]);
LPCMc.add(PCMamplitudesData[sample + c * 2 + 1]);
LPCMc.add(PCMamplitudesData[sample + 2 * channels * 2 + c]);
LPCM[c] = LPCMc;
}
for (int c = 0; c < channels * 2; c++) {
amplitude = LPCM[c][0] * 256 * 256 + LPCM[c][1] * 256 + LPCM[c][2];
}
rawSamples.add(amplitude);
sample = sample + 6 * channels;
}
} else {
// 8 Bit, 16 Bit, 32 Bit
for (int sample = 0; sample < PCMamplitudesData.length; sample = sample + bits ~/ 8 * channels) {
amplitude = 0;
switch (bits) {
case 8:
for (int i = 0; i < channels; i++)
amplitude = (ByteData.sublistView(PCMamplitudesData).getInt8(sample + i) - 128);
break;
case 16:
if (sample + 4 < PCMamplitudesData.length) {
for (int i = 0; i < channels; i++)
amplitude = ByteData.sublistView(PCMamplitudesData).getInt16(sample + i * 2, Endian.little);
}
break;
case 32:
if (PCMformat == WAV_FORMAT_PCM) {
// PCM
if (sample + 8 < PCMamplitudesData.length) {
for (int i = 0; i < channels; i++)
amplitude = ByteData.sublistView(PCMamplitudesData).getInt32(sample + i * 4, Endian.little);
}
} else if (PCMformat == WAV_FORMAT_IEEEFLOAT32) {
// IEEE Float 32
if (sample + 8 < PCMamplitudesData.length) {
for (int i = 0; i < channels; i++)
amplitude = ByteData.sublistView(PCMamplitudesData).getFloat32(sample + i * 4, Endian.little).toInt();
}
}
break;
}
rawSamples.add(amplitude);
};
}
int totalSamples = (rawSamples.length / blockSize).toInt();
for (int i = 0; i < totalSamples; i++) {
final double blockStart =
(blockSize * i).toDouble(); // the location of the first sample in the block
int sum = 0;
for (int j = 0; j < blockSize; j++) {
sum = sum +
rawSamples[(blockStart + j).toInt()]
.toInt(); // find the sum of all the samples in the block
}
filteredData.add((sum / blockSize)
    .round() // take the average of the block and add it to the filtered data
    .toInt()); // divide the sum by the block size to get the average

}
final maxNum = filteredData.reduce((a, b) => max(a.abs(), b.abs()));
final double multiplier = pow(maxNum, -1).toDouble();
final samples = filteredData.map((e) => (e * multiplier)).toList();
return samples;
}

I didn't got ur concern. Could u please elaborate a little on ur concern?

this will only work for uncompressed audio file data like PCM/WAV as depicted here:
List calculateJson( {int PCMformat, int bits, int channels, int sampleRate, Uint8List PCMamplitudesData, int blockSize,}) {
List filteredData = []; List rawSamples = [];
int amplitude = 0;
if (bits == 24) { // https://wiki.multimedia.cx/index.php/PCM int sample = 0; Map<int, List> LPCM = {}; while (sample + 6 * channels < PCMamplitudesData.length) { amplitude = 0; for (int c = 0; c < channels * 2; c++) { List LPCMc = []; LPCMc.add(PCMamplitudesData[sample + c * 2]); LPCMc.add(PCMamplitudesData[sample + c * 2 + 1]); LPCMc.add(PCMamplitudesData[sample + 2 * channels * 2 + c]); LPCM[c] = LPCMc; } for (int c = 0; c < channels * 2; c++) { amplitude = LPCM[c][0] * 256 * 256 + LPCM[c][1] * 256 + LPCM[c][2]; } rawSamples.add(amplitude); sample = sample + 6 * channels; } } else { // 8 Bit, 16 Bit, 32 Bit for (int sample = 0; sample < PCMamplitudesData.length; sample = sample + bits ~/ 8 * channels) { amplitude = 0; switch (bits) { case 8: for (int i = 0; i < channels; i++) amplitude = (ByteData.sublistView(PCMamplitudesData).getInt8(sample + i) - 128); break; case 16: if (sample + 4 < PCMamplitudesData.length) { for (int i = 0; i < channels; i++) amplitude = ByteData.sublistView(PCMamplitudesData).getInt16(sample + i * 2, Endian.little); } break; case 32: if (PCMformat == WAV_FORMAT_PCM) { // PCM if (sample + 8 < PCMamplitudesData.length) { for (int i = 0; i < channels; i++) amplitude = ByteData.sublistView(PCMamplitudesData).getInt32(sample + i * 4, Endian.little); } } else if (PCMformat == WAV_FORMAT_IEEEFLOAT32) { // IEEE Float 32 if (sample + 8 < PCMamplitudesData.length) { for (int i = 0; i < channels; i++) amplitude = ByteData.sublistView(PCMamplitudesData).getFloat32(sample + i * 4, Endian.little).toInt(); } } break; } rawSamples.add(amplitude); }; }
int totalSamples = (rawSamples.length / blockSize).toInt();
for (int i = 0; i < totalSamples; i++) { final double blockStart = (blockSize * i).toDouble(); // the location of the first sample in the block int sum = 0; for (int j = 0; j < blockSize; j++) { sum = sum + rawSamples[(blockStart + j).toInt()] .toInt(); // find the sum of all the samples in the block
}
filteredData.add((sum / blockSize)
    .round() // take the average of the block and add it to the filtered data
    .toInt()); // divide the sum by the block size to get the average

} final maxNum = filteredData.reduce((a, b) => max(a.abs(), b.abs()));
final double multiplier = pow(maxNum, -1).toDouble();
final samples = filteredData.map((e) => (e * multiplier)).toList();
return samples; }

I'm not clearly able to understand ur concern. Could you please elaborate a little on it?

Sure. Your package is an excellent solution if you have the jason data already. If not you need to create the jason file as a first step.
The question was if your package provides a way to create the json data.
My answer was no. However if you want to display an uncompressed audio file like wav there is a way to create the json data within the flutter app.

Ah ok. As I said, I don't plan to support json data creation through package. May be in future but nothing planned right now. Any contributions are welcome if you plan to work on something like that.
Also, wdym by "this will only work for uncompressed audio file data like PCM/WAV as depicted here:" in above message? Am I missing something?

To extract the JSON Data you need to have access to the uncompressed and raw data.
This is easy with respect to WAV.
MP3 or OGG is a compressed file format. Hence you have to decompress first. This is a rathe complex topic.
Sent from MailDroid
-----Original Message-----
From: Rutvik Tak @.>
To: rutvik110/flutter_audio_waveforms @.>
Cc: Thomas @.>, Comment @.>
Sent: Mi., 25 Jan. 2023 5:30
Subject: Re: [rutvik110/flutter_audio_waveforms] audioDataList WIth No Json (Issue #25)
Ah ok. As I said, I don't plan to support json data creation through package. May be in future but nothing planned right now. Any contributions are welcome if you plan to work on something like that.
Also, wdym by "this will only work for uncompressed audio file data like PCM/WAV as depicted here:" in above message? Am I missing something?
--
Reply to this email directly or view it on GitHub:
https://github.com/rutvik110/flutter_audio_waveforms/issues/25#issuecomment-1403084355
You are receiving this because you commented.
Message ID: @.***>

ah ohk. This could be critical for some people. Give me some time, I'll have to think abt how we can better support this.
Till then I believe u can access json data for any audio files using the just waveforms package. I'vent tried it myself yet but it seems to work fine from what I heard from others. Let me know if this solution works for you or if its something we might have to update to support.
https://pub.dev/packages/just_waveform

Hi, any consideration add unit8list from url support built-in or any guidance to do this? Really need!


16 byte cmpxchg

I think there are two points to improve in current cmpxchg support for 16 byte data structures:

consider arm lse
consider using __sync_bool_compare_and_swap to force gcc emit inlined instructions.

#include <atomic>

#if defined(__aarch64__) && defined(__clang__)
#  pragma clang attribute push(__attribute__((target("lse"))),apply_to=function)
#  define PLATFORM_SPECIFIC_OPTIONS_ENDING _Pragma("clang attribute pop")
#elif defined(__aarch64__) && defined(__GNUC__)
#  pragma GCC push_options
#  pragma GCC target("arch=armv8-a+lse")
#  define PLATFORM_SPECIFIC_OPTIONS_ENDING _Pragma("GCC pop_options")
#elif defined(__x86_64__) && defined(__clang__)
#  pragma clang attribute push(__attribute__((target("cx16"))),apply_to=function)
#  define PLATFORM_SPECIFIC_OPTIONS_ENDING _Pragma("clang attribute pop")
#elif defined(__x86_64__) && defined(__GNUC__)
#  pragma GCC push_options
#  pragma GCC target("cx16")
#  define PLATFORM_SPECIFIC_OPTIONS_ENDING _Pragma("GCC pop_options")
#else
#  define PLATFORM_SPECIFIC_OPTIONS_ENDING
#endif

template<class T>
__attribute__((always_inline)) inline bool cas(std::atomic<T> &src,
                T const& __restrict cmp,
                T const& __restrict with)
{
    auto inline_copy = [](__int128 * dst, const void * __restrict src) {
#if __has_builtin(__builtin_inline_memcpy)
    __builtin_inline_memcpy(dst, src, sizeof(__int128));
#elif __has_builtin(__builtin_memcpy)
    __builtin_memcpy(dst, src, sizeof(__int128));
#else
    ::memcpy(dst, src, sizeof(__int128));
#endif
    };
    __int128 cmp_value;
    __int128 with_value;
    inline_copy(&cmp_value, &cmp);
    inline_copy(&with_value, &with);
    return __sync_bool_compare_and_swap(reinterpret_cast<__int128 *>(&src), cmp_value, with_value);
}

struct A {
    int64_t a, b;
};

bool cas_test(std::atomic<__int128> &src,
                __int128 const& cmp,
                __int128 const& with)
{
    return cas(src, cmp, with);
}

bool cas_test(std::atomic<A> &src,
                A const& cmp,
                A const& with)
{
    return cas(src, cmp, with);
}

PLATFORM_SPECIFIC_OPTIONS_ENDING

bool cas_test2(std::atomic<__int128> &src,
                __int128 & cmp,
                __int128 & with)
{
    return src.compare_exchange_weak(cmp, with);
}

I'm not sure why we'd need anything on Arm.  Arm has load-reserved, store-exclusive, so doesn't need a second word for ABA.
The only platforms where we have a problem have the following combination of things:

An architecture with a CAS instruction but not ll/sc, so no ABA-proof primitive (i.e. x86, this is not a problem on any other architecture).
A standard library that use a compiler builtin for 128-bit CAS.
A compiler that doesn't expand that builtin to a single instruction.

This means that you need the combination of x86, libstdc++, and gcc to see the problem.  GCC has an open bug report about it and so, presumably, will fix it eventually.
That said, the ABA code isn't used on any hot paths in snmalloc, so the cost of a libcall is unlikely to be noticeable.
This combination of things (bug in a single compiler, doesn't affect hot paths) means that I'm very hesitant to do something ad-hoc as a work around for that compiler.
Looking at the code, we seem not to be doing LL/SC for non-x86 architectures.  I thought @nwf added that a while ago?

Hi,
I initiated this issue because I found that LLVM and GCC would behave quite differently on whether to inline atomic ops. This may deliver extra linkage with libatomic.so for rust.
For example, on x86, we are requiring the compiled target to have -mcx16 but gcc will still emitting outline atomic ops.

For DW LL/SC, maybe https://github.com/taiki-e/portable-atomic/blob/main/src/imp/aarch64.rs can be considered as a reference?


rename crates/lang_srv to crates/language_server

This is more consistent with other uses and this name is not significantly longer.

Just double checking, this looks solved now right ?

Yes, thanks for notifying us @glensargent :)


Abstract YouTube API using Playtube

You can remove a lot of the code if you use https://github.com/gajus/playtube component. That'd reduce the bug surface and make the component easier to maintain. If playtube is missing any features, I will happily update it.

That's a really good idea, i'll make that change... thanks @gajus ;)


Add etcdRecovery maintenance type for admin update - ARO-1534

Which issue this PR addresses:
Fixes
https://issues.redhat.com/browse/ARO-1534
What this PR does / why we need it:
In the event that a master node changes IP addresses (or NIC's) the etcd quorum will become degraded. The node with the change will then have it's etcd pod in a crashloop. This is due to the hardcoded etcd spec.
This PR adds the remediation type EtcdRecovery maintenance task to remediate this issue.
How it works:

Verify this is the issue by comparing etcd's env variables to the node's IP address. a degradedEtcd object is returned with relevant information.
Create a batch job to backup etcd's data directory and move the etcd manifest to stop the pod from crash looping.
A batch job is created to run a pod that ssh's into the peer etcd container's to remove the failing node from it's member list.
Secret's for the failing pod are deleted
Etcd is patched

Test plan for issue:

Is there any documentation that needs to be updated for this PR?
Yes, ADO Wiki Admin Update page once merged.

@cadenmarchese Certianly, here are the steps to reproduce.

Create this script#!/bin/bash

main() {
    if [[ -z $1 ]]; then
        abort "node name must be provided"
    fi

    node="$1"
    nic2="${node}-nic-$((1 + $RANDOM % 10))"

    subnetID="$(az network vnet subnet show -n $CLUSTER-master --vnet-name dev-vnet --query id)" || abort "failed to get subnet ID"
    aro="aro-${CLUSTER}"
    az network nic create --name "$nic2" --subnet "$( tr -d \" <<< "$subnetID")" -g "$aro" || abort "failed to create nic $nic2"

    az vm deallocate -g "$aro" -n "$node" || abort "failed to deallocate $node"

    az vm nic add --nics "$nic2" --vm-name "$node" --primary-nic "$nic2" -g "$aro" || abort "failed to add $nic2 to $node"

    az vm start -n "$node" -g "$aro" || abort "failed to start $node"
}

abort() {
    echo "$1"
    echo "Exiting"
    exit 1
}

Run it by providing the name of a master node: change_vm_nic.sh steven-cluster-gbv5x-master-1
Run PUCM: curl -X PATCH -k "https://localhost:8443/subscriptions/$AZURE_SUBSCRIPTION_ID/resourceGroups/$RESOURCEGROUP/providers/Microsoft.RedHatOpenShift/openShiftClusters/$CLUSTER?api-version=admin" --header "Content-Type: application/json" -d '{"properties": {"maintenanceTask": "EtcdRecovery"}}'
Watch the RP logs and pods in namespace openshift-etcd

@facchettos I can convert it back to draft, I've been adding unit tests, hence the active pushes. Some of the code has changed some while adding tests as you've pointed out.

@kimorris27 Thanks! Let me know if you have any questions when testing out locally.

Thank you @tony-schndr @kimorris27 for your extra testing and validation here, and thanks @facchettos for your review!
Regarding e2e test coverage, I am tempted to say we don't need it because this action doesn't encompass normal functionality of an ARO cluster (which is what e2e is meant to test). I'm tempted to approve as-is but open to other opinions on that.

@tony-schndr @cadenmarchese I haven't looked into e2e tests, maybe some good practice. But if the purpose is to test normal functionality then maybe it's overkill. Also FYI my last force push just a rebase from master.

Regarding e2e test coverage, I am tempted to say we don't need it because this action doesn't encompass normal functionality of an ARO cluster (which is what e2e is meant to test). I'm tempted to approve as-is but open to other opinions on that.

It was never super clear to me on exactly what e2e is supposed to cover so if this is outside the normal test case I get it.  I was just thinking along the lines of catching cases where this procedure may fail from some external change like ocp version changes and etcd operator changes.

@cadenmarchese My last push should address your latest review, let me know if I missed anything.

Closed in favor of implementation in PR #2880


Python OpenEye check is broken

@nathanmlim - in the getting started info (https://github.com/MobleyLab/drug-computing/blob/master/uci-pharmsci/getting-started.md) you have something like:
Verify the installation with:

python oecheminfo.py
The output should look something like:

I get a "can't open file" message when I do that. :) Probably you're missing a step about paths?

Somehow missed this notification. It looks like the installation verification test use to work with python oecheminfo.py. Now, it's just oecheminfo.py according to the latest docs

Resolved.


nixos/consul: add types

Motivation for this change
#76184
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Looks like you also added services.bind types in here. Mind separating the commits? I'm fine with them both being in this PR, as long as the commits themselves are separate. (Or you can make a separate PR, up to you.)

I didnt want to add bind here there is a seperate pr for that thanks for letting me know

Looks like you also added services.bind types in here. Mind separating the commits? I'm fine with them both being in this PR, as long as the commits themselves are separate. (Or you can make a separate PR, up to you.)

I didnt want to add bind here there is a seperate pr for that thanks for letting me know


feature: proto transport

Reason for This PR
closes: https://github.com/roadrunner-server/roadrunner/issues/1840
closes: https://github.com/roadrunner-server/roadrunner/issues/1859
closes: https://github.com/roadrunner-server/roadrunner/issues/1696
closes: https://github.com/roadrunner-server/roadrunner/issues/1812
closes: https://github.com/roadrunner-server/roadrunner/issues/1634
closes: https://github.com/roadrunner-server/roadrunner/issues/1698
Description of Changes

Use proto transport and real raw_body.

License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

[x] All commits in this PR are signed (git commit -s).
[x] The reason for this PR is clearly provided (issue no. or explanation).
[x] The description of changes is clear and encompassing.
[x] Any required documentation changes (code and docs) are included in this PR.
[x] Any user-facing changes are mentioned in CHANGELOG.md.
[x] All added/changed functionality is tested.

Summary by CodeRabbit
Summary by CodeRabbit

Chores

Updated .gitignore to ignore specific test files and directories.

Refactor

Removed a linter from the project configuration for improved code quality checks.
Enhanced attribute handling with support for multiple values per key.
Improved request and response handling with new pooling strategy and protobuf integration for efficiency and performance.
Adjusted tests and configurations to align with the latest code changes and removed outdated settings.

New Features

Introduced structured conversion for HTTP headers, cookies, and MIME headers to improve request and response processing.
Added support for HTTP/2 push headers and trailers, enhancing protocol support.

Tests

Updated test configurations and assertions to reflect new version numbers and handling logic.
Introduced context handling in HTTP request creation within tests for better request management.

Oh my god it's happening!!


test case is not stable

Here is a stack trace for a failure:
[2021-06-17T08:16:25.075Z] test raftstore::test_stats::test_query_stats ... thread 'main' panicked at 'assertion failed: check_query_num_write(&cluster, store_id, QueryKind::Put, 1)', tests/integrations/raftstore/test_stats.rs:339:9
[2021-06-17T08:16:25.075Z] stack backtrace:
[2021-06-17T08:16:25.333Z]    0: rust_begin_unwind
[2021-06-17T08:16:25.333Z]              at /rustc/16bf626a31cb5b121d0bca2baa969b4f67eb0dab/library/std/src/panicking.rs:493:5
[2021-06-17T08:16:25.333Z]    1: core::panicking::panic_fmt
[2021-06-17T08:16:25.333Z]              at /rustc/16bf626a31cb5b121d0bca2baa969b4f67eb0dab/library/core/src/panicking.rs:92:14
[2021-06-17T08:16:25.333Z]    2: core::panicking::panic
[2021-06-17T08:16:25.333Z]              at /rustc/16bf626a31cb5b121d0bca2baa969b4f67eb0dab/library/core/src/panicking.rs:50:5
[2021-06-17T08:16:25.333Z]    3: integrations::raftstore::test_stats::test_query_num::{{closure}}
[2021-06-17T08:16:25.333Z]              at /home/jenkins/tikv-src/tests/integrations/raftstore/test_stats.rs:339:9
[2021-06-17T08:16:25.333Z]    4: integrations::raftstore::test_stats::test_query_num
[2021-06-17T08:16:25.333Z]              at /home/jenkins/tikv-src/tests/integrations/raftstore/test_stats.rs:380:5
[2021-06-17T08:16:25.333Z]    5: integrations::raftstore::test_stats::test_query_stats
[2021-06-17T08:16:25.333Z]              at /home/jenkins/tikv-src/tests/integrations/raftstore/test_stats.rs:268:5
[2021-06-17T08:16:25.333Z]    6: integrations::raftstore::test_stats::test_query_stats::{{closure}}
[2021-06-17T08:16:25.333Z]              at /home/jenkins/tikv-src/tests/integrations/raftstore/test_stats.rs:135:1
[2021-06-17T08:16:25.333Z]    7: core::ops::function::FnOnce::call_once
[2021-06-17T08:16:25.333Z]              at /rustc/16bf626a31cb5b121d0bca2baa969b4f67eb0dab/library/core/src/ops/function.rs:227:5
[2021-06-17T08:16:25.333Z]    8: test_util::runner::run_test_with_hook::{{closure}}::{{closure}}
[2021-06-17T08:16:25.333Z]              at /home/jenkins/tikv-src/components/test_util/src/runner.rs:64:21
[2021-06-17T08:16:25.333Z]    9: core::ops::function::FnOnce::call_once{{vtable.shim}}
[2021-06-17T08:16:25.333Z]              at /rustc/16bf626a31cb5b121d0bca2baa969b4f67eb0dab/library/core/src/ops/function.rs:227:5
[2021-06-17T08:16:25.333Z]   10: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
[2021-06-17T08:16:25.333Z]              at /rustc/16bf626a31cb5b121d0bca2baa969b4f67eb0dab/library/alloc/src/boxed.rs:1546:9
[2021-06-17T08:16:25.333Z] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[2021-06-17T08:16:25.333Z] FAILED

I have no idea why it fails. Could you take look or re-dispatch it @lhy1024 ?


[BUG]Fix VPC flow Integration's Vega visualization

What is the bug?
Currently the VPF-Flow integration has a broken vega visualization, the aggregation target index is not taken from the user given name .

What is the expected behavior?
Fix Vega's visualization - simply replace the index name in the aggregation query to match the user defined index
    	index: flint_zero_etl_amazons3_default_vpcflow_mview*

Do you have any screenshots?

Do you have any additional context?
Add any other context about the problem.

fixed in vpc flow  and in HTTP flow visualization


Add CI builds

A CI system should be setup to perform builds of dnsbench for releases. Travis may be a good option.

Going to setup github actions to provide CI.


[SFAYTZ] Yahtzee - No Instructions displayed when you type "I" from the Main Menu

Module Information

SFAYTZ
Yahtzee

Describe the bug
When trying to display instructions, nothing is displayed and it hangs until you hit enter.
To Reproduce

Enter the Module
Hit I
Observe blank output
Hit enter to return to main menu

Expected behavior
Instructions should appear
** Technical Information **
It appears SFAYTZ does an open of SFAYTZ.INS and should output the content but it is not. The loop is the module going into deferred execution by calling btuinj for status 240. This is how it monitors for "Enter" before re-displaying the menu.
It opens the file successfully and saves the pointer, but it's not displaying the contents.

Fixed - confirmed in Build 100720-7
@enusbaum please close


Epson 201401w init at 1.0.0

Motivation for this change
This adds the epson-201401 printer driver which supports the following printers L456, L455, L366, L365, L362, L360, L312, L310, L222, L220, L132, L130
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.05 Release Notes (or backporting 21.11 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.

I rebased to master, it looks like qt is busted not the package

The diff now contains unrelated reverts

Please squash maintainers: fix typo in github username and maintainers: add lunarequest together
Also can you change epson-201401w init at 1.0.0 (commit and title) to epson-201401w: init at 1.0.0

I can rename the commit however, I can am not sure how to squash  maintainers: fix typo in github username and maintainers: add lunarequest without squashing   maintainers: fix typo in github username into  epson-201401w init at 1.0.0

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 155464 run on x86_64-linux 1

1 package built:

epson-201401w


[Check_rec] Report if a climbing site is created without any associated routes.

In the check_rec procedure, add a report when a waypoint of the type "wtyp=climbing_outdoor " is created but no route associated. There should always be a route called "pedestrian access", to allow creating an outing without precising all the routes.

I am happy to work on this one.

#22

Arf, unfortunately, I had to revert this: assocciation data are not present in the history service, so the test will never work (and actually, it crashes, I didn't looked close enough to the code...).
I re-open the issue, as it's possible, but it's a bit more difficult...

OK, let's look at this.


Feature request: Subscribe alongside Rip

The way I use ripme, and I'm sure I can't be the only one, is to actually manage and update my reddit pic collection. I put the url in to rip and then re-rip to update new photos in the following days.
It would be nice to press subscribe and have the account entered into a list separate from regular the history. After that there could be an update where it would only download new photos. It should only be available to certain urls, like reddit and flickr.
While the functionality is very similar to history, it could offer certain protections from events such as accidentally clearing your history. There could additionally be auto updating features where you can set a time to update daily or weekly.
I'm not 100% certain that this is the intended use. I just ask that 4pr0n and others be aware that there's a need in the software world for something that could be the heart of their collection like this. I use ripme every day and it's become part of my routine.

While the functionality is very similar to history, it could offer certain protections from events such as accidentally clearing your history.

I've added a feature that re-populates your history if there is no history.json file found. Only some sites are supported (like reddit), check out #166 for more info.

There could additionally be auto updating features where you can set a time to update daily or weekly.

That's a feature request and that's possible. I've also created something similar for reddit users: https://github.com/4pr0n/gonewilder
That project constantly scrapes reddit for specific users that you specify. It's not very user-friendly, though, and requires knowledge of the command-line.

Sounds like integrating gonewilder functionality into ripme is potentially a very good idea.


storage bucket being created by tf despite being manually created due to requirements of tf backend block

I'm using AWS.
The backend block uses the same bucket which is referenced by var.storage_bucket. The bucket used by the backend block needs to exist before tf is kicked in.

Store Terraform state in S3`
terraform {
backend "s3" {
# The bucket name is a variable defined in 'terraform.tfvars' (as 'storage_bucket'), but variables are not allowed in this block. If you change this, you will need to change that.
bucket = "mox-opencti-storage"
key    = "terraform.tfstate"
# Again, no variable interpolation in this block so make sure this matches the region defined in 'terraform.tfvars'. Default 'us-east-1'.
region = "ap-southeast-1"
}
}

When tf runs the var.storage_bucket is again created which results in the following error during apply.

Error: Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
status code: 409, request id: 8Z941E8XX87E8B2V, host id: bZnhhA0Wqgx1NpnCqZtT08+ut0z67ReihQmFBB4ER6CSYlIqDZP+nLKUu7rGpf5TsDqfysXDDZM=
on storage.tf line 2, in resource "aws_s3_bucket" "opencti_bucket":
2: resource "aws_s3_bucket" "opencti_bucket" {

The offending block is:

S3 bucket to store install and connectors scripts.
resource "aws_s3_bucket" "opencti_bucket" {
bucket = var.storage_bucket
acl    = "private"
//Turn on bucket versioning. We'll be storing the Terraform state in S3 and versioning will help protect against human error.
versioning {
enabled = true
}
}

Please remove this offending block and re-arrange the code.

+1

Running into the same issue -- Do you have a fix?

2022-04-11T16:00:13.569-0400 [DEBUG] [aws-sdk-go]
╷
│ Warning: Argument is deprecated
│
│   with aws_s3_bucket.opencti_bucket,
│   on storage.tf line 2, in resource "aws_s3_bucket" "opencti_bucket":
│    2: resource "aws_s3_bucket" "opencti_bucket" {
│
│ Use the aws_s3_bucket_versioning resource instead
│
│ (and one more similar warning elsewhere)
╵
╷
│ Error: error creating S3 Bucket (opencti-storage): BucketAlreadyExists: The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.


feat(icons): add new document icons

Describe pull-request
Added new PDF, PPT, XLS and DOC icons to Storybook. Icons have also been published to our webfont CDN solution and are prepared for our next website release.
Solving issue
Fixes: DTS-1336 and  DTS-1483
How to test

Go to Storybook link below
Check in Foundations -> Icons -> Native and Web Components
In the list of icons, choose "document_doc", "document_pdf", "document_ppt" and "document_xls"
Make sure the right icon is displayed

Nice work! It looks like the new icons are a bit bigger than the old ones, are we aware of that?

Nice work! It looks like the new icons are a bit bigger than the old ones, are we aware of that? The new ones use the full width of their box.

@EmelieLitwin and @charlottelorensson  - Please double-check it. I think you said it has to be like it due to more space that file formats take on SVGs artboard. If any problem, maybe it is easier to update "document eye" icon to have the same sizing (no padding on top/bottom) as newer document icons do.

Nice work! It looks like the new icons are a bit bigger than the old ones, are we aware of that? The new ones use the full width of their box.

@EmelieLitwin and @charlottelorensson - Please double-check it. I think you said it has to be like it due to more space that file formats take on SVGs artboard. If any problem, maybe it is easier to update "document eye" icon to have the same sizing (no padding on top/bottom) as newer document icons do.

Just to give us an idea, this image has them side-by-side and the same size.


mat-datepicker behaviour

Hi.
There are two bugs.
https://stackblitz.com/edit/components-issue-pv5czm?file=src%2Fmain.ts
Expected Behavior

I expect that mat-datepicker will not change my manual input data
Open the datepicker without bluring the input

Actual Behavior

In russian locale we use dd.mm.yyyy format. And when I try to type the date myself, sometimes it swaps the day and the month. For instance if you type 12.11.2003 , after the blur it changes to 11.12.2003.
If I will try to open the datepicker on the focus event like this (focus)="picker.open()", it will blur the input and required error will appear.

Environment

Angular: 9
CDK/Material: 9
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10

Ad 1: You should read this.
Looking at the source Material uses Date.parse() method, which treats first digit as month.
You can override this method or use MatMomentDateModule (recommended).

@domsew Thank You. It is my fault.

But what about the second issue? I have already read lots of other issues about it. But none of them has mention about the validators, like Validators.required.

I would not say that this is a bug. I think that this is expected behaviour, because MatDatepicker listens to user interactions, so it needs to have focus when is created. Think about whether you really need open datepicked on input focus. Maybe MatDatepickerToogle is sufficient?
If you really want it, you could try to write custom validator which will check if datepicker is opened.

I got it. Thank you

{ provide: MAT_DATE_FORMATS, useValue: dateFormats } seems to make no change...
adding
{
  parse: {
    dateInput: ['DD/MM/YYYY'],
  },
  display: {
    dateInput: 'DD/MM/YYYY',
    monthYearLabel: 'MM/YYY',
    dateA11yLabel: 'DD/MM/YYYY',
    monthYearA11yLabel: 'MM/YYY',
  },
}

it still changing the format after the input change where DD/MM/YYYY it will become MM/DD/YYYY

@rochapablo the propper solution


Add eventIndex and firstEventTimestamp properties to client sessions (close #517)

There was a small issue in the Util.getDateTimeFromTimestamp() method implementation – it didn't consider the timezone and thus could return local time although the timestamp was acting like it was UTC (it ended with Z). So I made a small change and added this on line 70 in Util.java:
        dateFormat.setTimeZone(TimeZone.getTimeZone("UTC"));

Thanks @AlexBenny! It's only that one line, sorry for the difficult to read changes.


Add support for CDN in libraries

Make it possible to declare a library as a CDN origin and add the capability to replace URLs of assets with the URL of the CDN origin.

Do we want to configure file types, too? Or is it enough to make a library Public/Private CDN Origin?

It can be done just using a bunch of PowerShell or a custom engine extension.


Toggle view blocked pull requests

Overview:

CR/QA Notes:

CR: Review to https://github.com/iFixit/pulldasher/pull/334/commits/eccc964f61a33cdf419052e74c0ec6f3cac5d3d2

QA: https://pulldasher-dev.cominor.com/
I updated Pulldasher-Dev, so you should just be able to click the link above.
If the changes aren't present, here is a reference for testing

cr_req 2
Closes #333

QA :no_entry_sign:

Externally blocked filter toggle works as expected :heavy_check_mark:

deploy_block :thinking: on a consideration

By default, externally blocked pulls are not shown. I think blocked pulls should be shown by default, and they should be filtered out when the user selects the filter

QA :+1: carryover and un_deploy_block :+1: on changing initial state

QA 🟢 Carry-over
un_deploy_block 🟩
Updated variable names

QA 🟢 Carry-over
Updated the button behavior for a cleaner UI

QA 🟢 Carry-over
Only changed button attributes

Looks great!  CR :+1:
dev_block :+1: on a few function renames though.

Hmm.. Also, I think the eye icon isn't appropriate here cause several other icons also hide and show a set of pulls. We want the icon to loosely represent which pulls are hidden / shown. The "external block" term doesn't lend itself to easy translation to an icon though.
Maybe it's time to turn this into a drop-down list like the author and repo filters...

Maybe it's time to turn this into a drop-down list like the author and repo filters...

What do you think about a button box instead of using the external_block icon?

What do you think about a button box instead of using the external_block icon?

That looks quite verbose (takes up a lot of room) and I think the button always showing text that's opposite to the current state is confusing. Maybe a dropdown like the others called Filters or something and has Externally Blocked and Cryogenic Storage entries ?

Maybe a dropdown like the others called Filters or something and has Externally Blocked and Cryogenic Storage entries

Hmm..  this may work better if we reverse the terminology and use Hide Externally Blocked?
Trying to imagine how this works:
X Show All
 - Hide Externally Blocked
 - Hide Frozen

Clicking Hide Frozen should hide the Frozen pulls and uncheck it, so it then looks like this?
 - Show All
 - Hide Externally Blocked
 X Hide Frozen

Then clicking "Hide externally blocked" will check that box:
 - Show All
 X Hide Externally Blocked
 X Hide Frozen

Then clicking "Show All" will go back to the initial state with "Show All" checked.

@danielbeardsley
How about something like this?

It will keep the default state of the two label variables so Cryogenic will be hidden initially like before, and externally block will be shown until toggled off here

How about something like this?

That's looking good! I'd still opt for using a menu list with checks like the other dropdowns so you can see the state, but that looks great.

I'd still opt for using a menu list with checks like the other dropdowns so you can see the state
@danielbeardsley

I figured out how to get this working using the Chakra Menu component
The only roadblock I see now is that the external_block should be checked initially
<MenuList>
   <MenuOptionGroup type="checkbox">
      <MenuItemOption isChecked={showCryo} value="cryogenic" onClick={toggleShowCryo} paddingLeft="184px" iconSpacing="-180px">Cryogenic Storage</MenuItemOption>
      <MenuItemOption isChecked={showExtBlocked} value="external_block" onClick={toggleShowExtBlocked} paddingLeft="184px" iconSpacing="-180px">External Block</MenuItemOption>
   </MenuOptionGroup>
 </MenuList>

The two ways I'm thinking of resolving this are:
1.) Switch external_block to not be shown initially (this may not be the best idea since CR is still necessary for these pulls)
2.) Figure out how to set the initial state of this MenuOptionGroup to the external_block value

un_dev_block 🟩
Updated function names + new drop down with state indicators

Functionally, it works great! Stylistically, it's different enough from the other dropdowns that it seems... off. How do you feel about pulling out some re-usable styled pieces so it looks cohesive?

Functionally, it works great! Stylistically, it's different enough from the other dropdowns that it seems... off. How do you feel about pulling out some re-usable styled pieces so it looks cohesive?

I do agree that there are some distinct differences between the other dropdowns, and I am open to adjusting to that styling.
I'll adjust the button itself to match the looks of the other ones, and I'm looking into getting the hover effect

un_dev_block 🟩
Updated styling for the dropdown component

QA :+1:

By default, external_block is initially selected/active :heavy_check_mark:
Filters behave as expected :heavy_check_mark:

I tried using MenuItemOption so the styling would match the other menus exactly. Looks great and a bit less custom styling!\
CR :+1:

QA 🟢 Carry-over

I tried using MenuItemOption so the styling would match the other menus exactly

Thank you!


Duplicate Contacts created when Lightning Sync is enabled

Do you want to request a feature or report a bug?
There's possibly a bug between the behavior of Lightning Sync for Outlook and the EDA Contact triggers. Customers are reporting duplicate contacts and accounts being created.

What is the current behavior?
Duplicate Contacts and accounts are being created.

What is the expected behavior?
The Lightning Sync should create contacts in Salesforce without duplication.

**lurch: add

Tracking W-040709

@aligeez fyi

This was determined to be a bug with Lightning Sync, not EDA. Closing.


Ignore bootstrap replicas when checking for unavailability

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

Project coverage is 18.64%. Comparing base (52ba813) to head (c03368d).
Report is 36 commits behind head on master.

Files
Patch %
Lines

...om/github/ambry/router/SimpleOperationTracker.java
0.00%
9 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (52ba813) and HEAD (c03368d). Click for more details.
HEAD has 2 uploads less than BASE
| Flag | BASE (52ba813) | HEAD (c03368d) |
|------|------|------|
||3|1|

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2813       +/-   ##
=============================================
- Coverage     64.24%   18.64%   -45.60%
+ Complexity    10398     2916     -7482
=============================================
  Files           840      842        +2
  Lines         71755    72327      +572
  Branches       8611     8701       +90
=============================================
- Hits          46099    13487    -32612
- Misses        23004    57601    +34597
+ Partials       2652     1239     -1413

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


wip

wip for interactive online stuff

now that we're doing online learning without any hacks, we can completely get rid of interactive_known_predicates and should use the existing excluded_predicates infrastructure instead. i've done that in this PR
removed hacks surrounding predicate stripping from interactive_learning_approach, now there's no way it can cheat. the initial predicates that are passed into __init__ are the known predicates. the ones to be learned are extracted from the offline dataset at the start of learn_from_offline_dataset (note their classifiers were stripped during dataset construction, so there's no way to cheat)
there's one functional difference that i wrote a "TODO" comment for, we should discuss and make a decision

@tomsilver @amburger66 read this before looking at the diffs!

TODO: we realized that ground-truth predicate classifiers are leaking into the interactive learning approach for goal predicates, through train tasks. we'll need to fix this either here or in a separate PR.

There are a number of functional changes I'd like to make after we merge this PR, I'm putting them here so I don't forget:

Change the annotations from positive only to positive/negative, and put the negative results from active learning into negative
Implement an option to use a different kind of trivial score function for selecting atoms to ask about, one that just asks about everything. (Maybe change to >= instead of > in this step)
Allow falling back to random policy if no goal can be found
Figure out if we want the agent to be able to ask a different kind of query like "tell me everything in this state" or "tell me something in this state", which we would need to pure active learning, because otherwise it doesn't know what the universe of predicates is
Test that active learning alone works

@amburger66 @ronuchit I think this is ready for review now.
After we merge, we should launch supercloud experiments to identify if we've introduced any major regressions. (@amburger66 , could you do this? thanks!)

After we merge, we should launch supercloud experiments to identify if we've introduced any major regressions. (@amburger66 , could you do this? thanks!)

yup

lgtm


Static Range Request Creating Multiple Sessions and Clobbering Cookie

I have a GET that stores some data to a session (req.session.token = token) and responds with a page that loads a video (809k) using HTML5's video tag.
The video is served up via static middleware as a range request (status code 206). Interestingly, it appears on each chunk Connect seems to be creating a new session in Redis and clobbering the original cookie in the user's browser.
Since the user's cookie is clobbered with the most recent session key created we no longer have access to the original session data.
Using:
node 0.4.12
├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
app.js
/**
 * Module dependencies.
 */

var express = require('express'),
  redis = require("redis"),
  RedisStore = require('connect-redis')(express);

var app = module.exports = express.createServer();

// Configuration

app.configure(function(){
  app.set('views', __dirname + '/views');
  app.set('view engine', 'jade');
  app.use(express.bodyParser());
  app.use(express.methodOverride());
  app.use(express.cookieParser());
  app.use(express.session({ secret: "alkjaslkfjslkdfjdf", store: new RedisStore(),  key: 'express.sid' }));
  app.use(app.router);
  app.use(express.static(__dirname + '/public'));
});

app.configure('development', function(){
  app.use(express.errorHandler({ dumpExceptions: true, showStack: true }));
});

app.configure('production', function(){
  app.use(express.errorHandler());
});

// Routes

app.get('/', function(req, res){
  req.session.token = 'Hello Token';
  res.render('index', {
    title: 'Express'
  });
});

app.listen(3000);
console.log("Express server listening on port %d in %s mode", app.address().port, app.settings.env);

index.jade
h1= title
p Welcome to #{title}
video(src="/videos/3.mp4", autoplay="yes", loop="loop", preload="auto", poster="/videos/3.jpg")
  source(src="/videos/3.mp4")

HTML output
<!DOCTYPE html>

    <title>Express</title>
    <link rel="stylesheet" href="/stylesheets/style.css"/>

Express

Welcome to Express

    <video src="/videos/3.mp4" autoplay="yes" loop="loop" preload="auto" poster="/videos/3.jpg">
      <source src="/videos/3.mp4"></source>
    </video>

KEYS * in Redis before request:
redis <IP_ADDRESS>:6379> keys *
(empty list or set)

KEYS * in Redis after 1 request:
redis <IP_ADDRESS>:6379> keys *
1) "sess:1at93LcqrZiFAbJDj4Xdgjvk.VxUwdqRxeQDepllW763Q5xzdwWgPiXV3h7W+ktlyLJs"
2) "sess:cbf0k5BjIXgMrNoQWGaPLg2z.HdQxyfsBNAwLKcsirMxlNAGhQGQbGslBAhZB+i3c0vw"
3) "sess:rJHmen3u910vUC5L7HculveC.l++B9kqO35sEUQp79+rKaGl4nLAoNECmnE5TtQ8Ua/I"

this is probably a two-part problem. a) we Set-Cookie always right now, which really needs to be changed (I have an issue open), b) perhaps the browser is not sending the cookie for these requests, causing connect to generate a new one. I'll see if I can reproduce this

I setup a repo you can clone:
https://github.com/seanabrahams/cookieclobber

awesome thanks, appreciate it

seems fine to me, I tried your repo and my own

Looks like it may be specific to Safari...

@frank06 Unfortunately I did not. We switched directions and this became a non-issue.

Ok found it (applies at least to Safari 5.0.3)
It's the default fingerprint function in Connect that makes the comparison fail and therefore triggers new session creation upon mp4 requests from Safari.
This is because mp4 requests do not send the real user agent, and the default fingerprint relies on it.
For any standard request, Safari will send something like: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-us) AppleWebKit/533.19.4 (KHTML, like Gecko) Version/5.0.3 Safari/533.19.4
For mp4 files, it will send: Apple Mac OS X v10.6.4 CoreMedia v<IP_ADDRESS>F569.
@visionmedia You may want to either change the default fingerprint function (at the moment I don't know to what, really) or put a big notice that it will make mp4 requests fail.

Nice!

It took me a long time to debug my way here but I'm pretty sure I've hit the same issue with just using static .wav and .mp3's in Safari 5.1.3 (works fine in Chrome 18.0.1025.45 beta).
That is: executing new Audio('/sound/hello.wav'); in the client gets you a new session id.
The reason seems to be that Safari hits the .wav twice. First using the regular user-agent string:
"Mozilla/5.0 (Macintosh; Intel Mac OS X 1073) AppleWebKit/534.53.11 (KHTML, like Gecko) Version/5.1.3 Safari/534.53.10"

and the second time (through a plugin?) with another user-agent string:
"AppleCoreMedia/<IP_ADDRESS>D50b (Macintosh; U; Intel Mac OS X 1073; en_us)"

As I'm using express 2.5.8 which depends on 1.8.5, I resorted to the following workaround:
app.use(express.session({
  fingerprint: function (req) {
    return "hello";
  }
}));


How to configure SVGR in a tsup package inside a turborepo

So I was working on a project where I wanna setup svgr inside a tsup package in turborepo.
This is my tsup config
import type { Options } from "tsup";
import { defineConfig } from "tsup";

export default defineConfig((options: Options) => ({
  plugins: [],
  treeshake: true,
  splitting: true,
  entryPoints: ["./**/*.tsx"],
  // format: ["esm"],
  dts: true,
  minify: true,
  clean: true,
  externals: ["react"],
  ...options,
}));

and this is my folder structure
my-turborepo-project/
|-- app/
|   |-- web/
|   |-- docs/
|-- packages/
|   |-- ui/
|   |   |-- components/
|   |   |-- tsup.config.ts
|   |   |-- tailwind.config.mjs
|   |   |-- tsconfig.json
|   |-- tailwind-config/
|   |-- tsconfig/
|   |-- eslint-config/
|-- tsconfig.json
|-- turbo.json
|-- pnpm-workspace.yaml
|-- pnpm-lock.yaml
|-- package.json
|-- .gitignore

@kriptonian1 I was having issues using the next.js webpack loader for @svgr/webpack. I have a frontend/packages/icons package from which I'd only like to export svg files, but when I tried to import those in my frontend/apps/subscriptions app I got the error that react couldn't be resolved. I assumed adding react to the peerDependencies of the icons package would resolve the issue, but it didn't. Adding react to the dependencies of the icons package did resolve the issue, but that kind of stings because I would've liked to keep the icons package to only export svg files. It works this way though, for me.


feat: lazy load esm

blocker for https://github.com/denoland/deno/pull/20812

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

Pretty much stuck on how to handle primordials now...

Opened https://github.com/denoland/deno_core/issues/363 to solve the primordials problem.