Support Environments Updates & Bulk Fetches

Right now the proof of concept will work as long as an existing ENV is set. For example, if HELLO=yall is set then the shared object hook into getenv can override that with WORLD as a value. But if HELLO were not set at all, then the current code will not return the override. Why is this important?
Let's say  you want to batch fetch many parameters using ssm_parameters:/my/application/env as a path. You could have something like this in your template.yml file:
Globals:
  Function:
    Environment:
      Variables:
        X_CRYPTEIA_ENVIRONMENTS: ssm_parameters:/my/application/env

So this could pull in DATABASE_URL, SECRET_KEY_BASE, and many more. But would fail because there was no previous DATABASE_URL set. We could treat this as a feature and encourage placeholders like so, but that feels a bit superfluous?
Globals:
  Function:
    Environment:
      Variables:
        DATABASE_URL: placeholder
        SECRET_KEY_BASE: placeholder
        X_CRYPTEIA_ENVIRONMENTS: ssm_parameters:/my/application/env

Fixed by https://github.com/customink/crypteia/pull/11


fix(npm): updated dependency semantic-release to v20

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Installation Fails - Apple M1 Chip Related?

I am trying to install owl with opam and I have not been able to get past this error.  This is a new M1 mac, and my googling shows that that may be the cause BUT this is way out of my realm of knowledge so I am not completely sure.
I tried to follow instructions from this closed issue;  https://github.com/owlbarn/owl/issues/597 but I was still unable to get past this.  Admittedly, I didn't understand most of the conversation there so if it's something I am missing I apologize.
Here's the command I run + stack trace.
Isaacs-MacBook-Pro:stocks isaacflath$ opam install owl
The following actions will be performed:
  ∗ install eigen 0.3.0 [required by owl]
  ∗ install owl   1.0.2
===== ∗ 2 =====
Do you want to continue? [Y/n] Y

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
Processing  1/6:
⬇ retrieved eigen.0.3.0  (cached)
⬇ retrieved owl.1.0.2  (cached)
[ERROR] The compilation of eigen.0.3.0 failed at "dune build -p eigen -j 9".

#=== ERROR while compiling eigen.0.3.0 ========================================#
# context     2.1.2 | macos/arm64 | ocaml-base-compiler.4.13.1 | https://opam.ocaml.org#06b23506
# path        ~/.opam/4.13.1/.opam-switch/build/eigen.0.3.0
# command     ~/.opam/opam-init/hooks/sandbox.sh build dune build -p eigen -j 9
# exit-code   1
# env-file    ~/.opam/log/eigen-86828-52f975.env
# output-file ~/.opam/log/eigen-86828-52f975.out
### output ###
# [...]
# (cd _build/default/eigen_cpp && /usr/bin/cc -O2 -fno-strict-aliasing -fwrapv -pthread -fPIC -ansi -pedantic -O3 -std=c++11 -w -Wno-invalid-partial-specialization -Ofast -march=native -funroll-loops -ffast-math -g -I /Users/isaacflath/.opam/4.13.1/lib/ocaml -I /Users/isaacflath/.opam/4.13.1/lib/bigarray-compat -I /Users/isaacflath/.opam/4.13.1/lib/ctypes -I /Users/isaacflath/.opam/4.13.1/lib/i[...]
# clang: error: the clang compiler does not support '-march=native'
# File "_build/.dune/default/eigen_cpp/dune", line 11, characters 22-33:
# 11 |   (names eigen_tensor eigen_dsmat eigen_spmat)
#                            ^^^^^^^^^^^
# (cd _build/default/eigen_cpp && /usr/bin/cc -O2 -fno-strict-aliasing -fwrapv -pthread -fPIC -ansi -pedantic -O3 -std=c++11 -w -Wno-invalid-partial-specialization -Ofast -march=native -funroll-loops -ffast-math -g -I /Users/isaacflath/.opam/4.13.1/lib/ocaml -I /Users/isaacflath/.opam/4.13.1/lib/bigarray-compat -I /Users/isaacflath/.opam/4.13.1/lib/ctypes -I /Users/isaacflath/.opam/4.13.1/lib/i[...]
# clang: error: the clang compiler does not support '-march=native'
# File "_build/.dune/default/eigen/dune", line 31, characters 27-51:
# 31 |   (names eigen_utils_stubs ffi_eigen_generated_stub)
#                                 ^^^^^^^^^^^^^^^^^^^^^^^^
# (cd _build/default/eigen && /usr/bin/cc -O2 -fno-strict-aliasing -fwrapv -pthread -D_FILE_OFFSET_BITS=64 -O2 -fno-strict-aliasing -fwrapv -pthread -O3 -Ofast -march=native -funroll-loops -ffast-math -I../eigen_cpp/lib -g -I /Users/isaacflath/.opam/4.13.1/lib/ocaml -I /Users/isaacflath/.opam/4.13.1/lib/bigarray-compat -I /Users/isaacflath/.opam/4.13.1/lib/ctypes -I /Users/isaacflath/.opam/4.13[...]
# clang: error: the clang compiler does not support '-march=native'

<><> Error report <><><><><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
┌─ The following actions failed
│ λ build eigen 0.3.0
└─
╶─ No changes have been performed

Aa an update I was able to get past this error using rosetta, but now got to the next error.  I am stuck at this point.
isaacflath@Isaacs-MacBook-Pro ~ % opam install owl

<><> Synchronising pinned packages ><><><><><><><><><><><><><><><><><><><><>  🐫
[owl.1.0.2] synchronised (no changes)

The following actions will be performed:
  ∗ install owl 1.0.2*

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
⬇ retrieved owl.1.0.2  (no changes)
[ERROR] The compilation of owl.1.0.2 failed at "dune build -p owl -j 9".

#=== ERROR while compiling owl.1.0.2 ==========================================#
# context     2.1.2 | macos/x86_64 | ocaml-base-compiler.4.13.1 | pinned(git+file:///Users/isaacflath/owl_mseri#arm64#2537f1b6)
# path        ~/.opam/4.13.1/.opam-switch/build/owl.1.0.2
# command     ~/.opam/opam-init/hooks/sandbox.sh build dune build -p owl -j 9
# exit-code   1
# env-file    ~/.opam/log/owl-6952-c247f9.env
# output-file ~/.opam/log/owl-6952-c247f9.out
### output ###
# /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_73ae1a_dune/camlasmfc609d.s:2664:2: error: invalid instruction mnemonic 'bl'
# [...]
# /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_73ae1a_dune/camlasmfc609d.s:2666:15: error: unknown token in expression
#  orr x0, xzr, #1
#               ^
# /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_73ae1a_dune/camlasmfc609d.s:2667:11: error: brackets expression not supported on this target
#  ldr x30, [sp, #24]
#           ^
# /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_73ae1a_dune/camlasmfc609d.s:2668:14: error: unknown token in expression
#  add sp, sp, #32
#              ^
# File "src/owl/config/configure.ml", line 1:
# Error: Assembler error, input left in file /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_73ae1a_dune/camlasmfc609d.s

<><> Error report <><><><><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
┌─ The following actions failed
│ λ build owl 1.0.2
└─
╶─ No changes have been performed

If you pin https://github.com/owlbarn/owl/pull/609 and https://github.com/owlbarn/eigen/pull/36, does it install fine?

No, I still get the assembler error.
isaacflath@Isaacs-MacBook-Pro ~ % arch
i386

isaacflath@Isaacs-MacBook-Pro ~ % opam install owl

<><> Synchronising pinned packages ><><><><><><><><><><><><><><><><><><><><>  🐫
[owl.1.0.2] synchronised (no changes)

The following actions will be performed:
  ∗ install owl 1.0.2*

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
⬇ retrieved owl.1.0.2  (no changes)
[ERROR] The compilation of owl.1.0.2 failed at "dune build -p owl -j 9".

#=== ERROR while compiling owl.1.0.2 ==========================================#
# context     2.1.2 | macos/x86_64 | ocaml-base-compiler.4.13.1 | pinned(git+file:///Users/isaacflath/owl#arm64#2537f1b6)
# path        ~/.opam/4.13.1/.opam-switch/build/owl.1.0.2
# command     ~/.opam/opam-init/hooks/sandbox.sh build dune build -p owl -j 9
# exit-code   1
# env-file    ~/.opam/log/owl-14881-45a05f.env
# output-file ~/.opam/log/owl-14881-45a05f.out
### output ###
# /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_eb6077_dune/camlasm1b9b95.s:2664:2: error: invalid instruction mnemonic 'bl'
# [...]
# /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_eb6077_dune/camlasm1b9b95.s:2666:15: error: unknown token in expression
#  orr x0, xzr, #1
#               ^
# /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_eb6077_dune/camlasm1b9b95.s:2667:11: error: brackets expression not supported on this target
#  ldr x30, [sp, #24]
#           ^
# /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_eb6077_dune/camlasm1b9b95.s:2668:14: error: unknown token in expression
#  add sp, sp, #32
#              ^
# File "src/owl/config/configure.ml", line 1:
# Error: Assembler error, input left in file /var/folders/vs/j71s84gs4f7d059xxqrf71wc0000gn/T/build_eb6077_dune/camlasm1b9b95.s

<><> Error report <><><><><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
┌─ The following actions failed
│ λ build owl 1.0.2
└─
╶─ No changes have been performed

isaacflath@Isaacs-MacBook-Pro ~ % opam pin
eigen.0.3.0                      git  git+file:///Users/isaacflath/eigen#fix-0.3.0
owl.1.0.2         (uninstalled)  git  git+file:///Users/isaacflath/owl#arm64
owl-base.1.0.2                   git  git+file:///Users/isaacflath/owl#arm64
owl-plplot.1.0.2  (uninstalled)  git  git+file:///Users/isaacflath/owl#arm64
owl-top.1.0.2     (uninstalled)  git  git+file:///Users/isaacflath/owl#arm64
owl-zoo.1.0.2     (uninstalled)  git  git+file:///Users/isaacflath/owl#arm64

What if you compile for M1, avoiding Rosetta?

Different error
isaacflath@Isaacs-MacBook-Pro eigen % opam install owl

<><> Synchronising pinned packages ><><><><><><><><><><><><><><><><><><><><>  🐫
[owl.1.0.2] synchronised (no changes)

The following actions will be performed:
  ∗ install owl 1.0.2*

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
⬇ retrieved owl.1.0.2  (no changes)
[ERROR] The compilation of owl.1.0.2 failed at "dune build -p owl -j 9".

#=== ERROR while compiling owl.1.0.2 ==========================================#
# context     2.1.2 | macos/arm64 | ocaml-base-compiler.4.13.1 | pinned(git+file:///Users/isaacflath/owl#arm64#2537f1b6)
# path        ~/.opam/4.13.1/.opam-switch/build/owl.1.0.2
# command     ~/.opam/opam-init/hooks/sandbox.sh build dune build -p owl -j 9
# exit-code   1
# env-file    ~/.opam/log/owl-15788-373026.env
# output-file ~/.opam/log/owl-15788-373026.out
### output ###
# [...]
# File "src/owl/dune", line 47, characters 0-2787:
#  47 | (library
#  48 |  (name owl)
#  49 |  (public_name owl)
# .....213 |   :standard
# 214 |   (:include ocaml_flags.sexp))
# 215 |  (libraries ctypes ctypes.stubs eigen owl-base npy))
# (cd _build/default && /Users/isaacflath/.opam/4.13.1/bin/ocamlmklib.opt -g -o src/owl/owl_stubs src/owl/SFMT.o src/owl/airy.o src/owl/airyf.o src/owl/bdtr.o src/owl/beta.o src/owl/btdtr.o src/owl/cbrt.o src/owl/chbevl.o src/owl/chbevlf.o src/owl/chdtr.o src/owl/const.o src/owl/constf.o src/owl/dawsn.o src/owl/dawsnf.o src/owl/ellie.o src/owl/ellik.o src/owl/ellpe.o src/owl/ellpj.o src/owl/ell[...]
# ld: warning: dylib (/opt/homebrew/opt/gcc/lib/gcc/11/libgfortran.5.dylib) was built for newer macOS version (12.2) than being linked (12.0)
# ld: warning: dylib (/opt/homebrew/opt/gcc/lib/gcc/11/libgomp.1.dylib) was built for newer macOS version (12.2) than being linked (12.0)
# ld: file not found: @rpath/libgcc_s.1.1.dylib for architecture arm64
# clang: error: linker command failed with exit code 1 (use -v to see invocation)

<><> Error report <><><><><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
┌─ The following actions failed
│ λ build owl 1.0.2
└─
╶─ No changes have been performed

This one is due to multi archs: you don’t have arm64 gcc installed or is shadowed by x86 one

Ok, I am not sure how to fix that or change the shadowing.
Is this what I should install to fix this?  https://formulae.brew.sh/cask/gcc-arm-embedded

Alright well I don't think I know enough about what's going on to know how to fix this.  I am a bit worried about changing too much here given my lack of understanding of all this, as I do not want to break anything that I don't know how to un-break.  In addition, even if I did get it figured out it's not ideal to have it working because I pinned particular versions as I can't freely just upgrade to the latest version.  Unfortunately, I am going to move forward without owl for now.
I will leave this issue open as it's an open issue on my end and maybe it's helpful information to library maintainers.
Feel free to close it out though if having this ticket open is not helpful
Thank you for all your time and help.

Sure. Hopefully the two PRs will be merged soon, then from the next version owl should work out of the box

Just as a curiosity. It you have time can you check what happens if you do
opam pin -n git+https://github.com/mseri/eigen.git#fix-0.3.0
opam pin -n git+https://github.com/mseri/owl.git#arm64
PKG_CONFIG_PATH="/opt/homebrew/opt/openblas/lib/pkgconfig" opam install owl

I think it may be openblas which is the x86 version

No luck unfortunately
[NOTE] Package eigen is currently pinned to git+file:///Users/isaacflath/eigen#fix-0.3.0 (version 0.3.0).
eigen is now pinned to git+https://github.com/mseri/eigen.git#fix-0.3.0 (version 0.3.0)
This will pin the following packages: owl-base, owl-plplot, owl-top, owl-zoo, owl. Continue? [Y/n] Y
[NOTE] Package owl-base is currently pinned to git+file:///Users/isaacflath/owl#arm64 (version 1.0.2).
owl-base is now pinned to git+https://github.com/mseri/owl.git#arm64 (version 1.0.2)
[NOTE] Package owl-plplot is currently pinned to git+file:///Users/isaacflath/owl#arm64 (version 1.0.2).
owl-plplot is now pinned to git+https://github.com/mseri/owl.git#arm64 (version 1.0.2)
[NOTE] Package owl-top is currently pinned to git+file:///Users/isaacflath/owl#arm64 (version 1.0.2).
owl-top is now pinned to git+https://github.com/mseri/owl.git#arm64 (version 1.0.2)
[NOTE] Package owl-zoo is currently pinned to git+file:///Users/isaacflath/owl#arm64 (version 1.0.2).
owl-zoo is now pinned to git+https://github.com/mseri/owl.git#arm64 (version 1.0.2)
[NOTE] Package owl is currently pinned to git+file:///Users/isaacflath/owl#arm64 (version 1.0.2).
owl is now pinned to git+https://github.com/mseri/owl.git#arm64 (version 1.0.2)

<><> Synchronising pinned packages ><><><><><><><><><><><><><><><><><><><><>  🐫
[owl.1.0.2] synchronised (git+https://github.com/mseri/owl.git#arm64)

The following actions will be performed:
  ↻ recompile eigen    0.3.0*  [upstream or system changes]
  ↻ recompile owl-base 1.0.2*  [upstream or system changes]
  ∗ install   stdio    v0.15.0 [required by owl]
  ∗ install   owl      1.0.2*
===== ∗ 2   ↻ 2 =====
Do you want to continue? [Y/n] Y

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
⬇ retrieved owl.1.0.2  (no changes)
⬇ retrieved stdio.v0.15.0  (cached)
⬇ retrieved eigen.0.3.0  (git+https://github.com/mseri/eigen.git#fix-0.3.0)
⬇ retrieved owl-base.1.0.2  (git+https://github.com/mseri/owl.git#arm64)
∗ installed stdio.v0.15.0
⊘ removed   owl-base.1.0.2
∗ installed owl-base.1.0.2
⊘ removed   eigen.0.3.0
∗ installed eigen.0.3.0
[ERROR] The compilation of owl.1.0.2 failed at "dune build -p owl -j 9".

#=== ERROR while compiling owl.1.0.2 ==========================================#
# context     2.1.2 | macos/arm64 | ocaml-base-compiler.4.13.1 | pinned(git+https://github.com/mseri/owl.git#arm64#2537f1b6)
# path        ~/.opam/4.13.1/.opam-switch/build/owl.1.0.2
# command     ~/.opam/opam-init/hooks/sandbox.sh build dune build -p owl -j 9
# exit-code   1
# env-file    ~/.opam/log/owl-20677-887acc.env
# output-file ~/.opam/log/owl-20677-887acc.out
### output ###
# [...]
# File "src/owl/dune", line 47, characters 0-2787:
#  47 | (library
#  48 |  (name owl)
#  49 |  (public_name owl)
# .....213 |   :standard
# 214 |   (:include ocaml_flags.sexp))
# 215 |  (libraries ctypes ctypes.stubs eigen owl-base npy))
# (cd _build/default && /Users/isaacflath/.opam/4.13.1/bin/ocamlmklib.opt -g -o src/owl/owl_stubs src/owl/SFMT.o src/owl/airy.o src/owl/airyf.o src/owl/bdtr.o src/owl/beta.o src/owl/btdtr.o src/owl/cbrt.o src/owl/chbevl.o src/owl/chbevlf.o src/owl/chdtr.o src/owl/const.o src/owl/constf.o src/owl/dawsn.o src/owl/dawsnf.o src/owl/ellie.o src/owl/ellik.o src/owl/ellpe.o src/owl/ellpj.o src/owl/ell[...]
# ld: warning: dylib (/opt/homebrew/opt/gcc/lib/gcc/11/libgfortran.5.dylib) was built for newer macOS version (12.2) than being linked (12.0)
# ld: warning: dylib (/opt/homebrew/opt/gcc/lib/gcc/11/libgomp.1.dylib) was built for newer macOS version (12.2) than being linked (12.0)
# ld: file not found: @rpath/libgcc_s.1.1.dylib for architecture arm64
# clang: error: linker command failed with exit code 1 (use -v to see invocation)

<><> Error report <><><><><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
┌─ The following actions failed
│ λ build owl 1.0.2
└─
┌─ The following changes have been performed
│ ↻ recompile eigen    0.3.0
│ ↻ recompile owl-base 1.0.2
│ ∗ install   stdio    v0.15.0
└─

The former state can be restored with:
    /opt/homebrew/bin/opam switch import "/Users/isaacflath/.opam/4.13.1/.opam-switch/backup/state-20220507161004.export"

Also, GCC appears to be for arm64
isaacflath@Isaacs-MacBook-Pro % which gcc
/usr/bin/gcc
isaacflath@Isaacs-MacBook-Pro % gcc -v

Apple clang version 13.1.6 (clang-13<IP_ADDRESS>)
Target: arm64-apple-darwin21.3.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

thanks for checking!

Also, GCC appears to be for arm64

yes but this is not the one that homebrew has installed and used for gfortran. The issue you face is the same as https://github.com/firedrakeproject/firedrake/issues/2320 and https://github.com/Homebrew/discussions/discussions/1490
Unfortunately, not using homebrew I have hard times figuring it out myself. But it was worth a shot

One last test, sorry. With this I may be able to figure out a way to fix things.
If you create a symlink of /opt/homebrew/opt/gcc/lib/gcc/11/libgcc_s.1.1.dylib inside /opt/homebrew/opt/openblas/lib, does the previous command work?

Wooohoo that seemed to work!  Thank you so much!
I will go through some of the owl tutorials and let you know if there's any issues, but I was able to load in owl and create an owl array, so I think I am in the clear!

Indeed, owl-top is not compatible with recent ocaml. I think @ryanrhymes is working on fixing that

Hi all is working!  Thank you all!

Works for me too, if you need more confirmation

Fantastic, thanks for checking


[BUG] Catalog that excludes packages ignores noarch packages

Describe The Bug
When importing a catalog that excludes packages for certain architectures, the will be listed later. For example:
exclude_filter {
  repo_match: "^AppStream$"
  arch {
    key: "ppc64le"
    glob_match: "seavgabios-bin"
}

package {
  name: "seabios"
  type: PACKAGE_TYPE_NORMAL_FORK
  repository {
    name: "AppStream"
    include_filter: "seabios-bin.noarch"
    include_filter: "seabios.x86_64"
    include_filter: "seavgabios-bin.noarch"
  }
}

The only fix is to set a noarch package as the architecture, which is not the proper way to do it.
Reproduction Steps

Exclude a package that is no arch from a repository
Import the catalog.
Package is still in the repository for that architecture.

Expected Behavior
Packages that are noarch that are purposely excluded should be excluded.
Version and Build Information
Current.
Additional context
This is either a bug with the tooling that converts pungi data or with peridot itself.

This is a bug in yumrepofsupdater. There is a planned fix. For 9.1, let's use the workaround to get the catalog to the state we want, and when the fix is deployed we can revert to the catalog and re-process the affected builds again with correct behavior this time.

#71 should address this. Tests run for the last 9.1 sync does show success.


How to select language english as default ?

Checklist

[X] I'm asking a question and not reporting a bug/feature request
[X] I've looked through the README
[X] I've read the guidelines for opening an issue
[X] I've searched the bugtracker for similar questions including closed ones

Question
How to select language English as default?
which argument should I include in the command line for default English audio?
site: curiositystream

Read https://github.com/yt-dlp/yt-dlp#format-selection
Atleast give more info. Show us the output of yt-dlp -vUF "YOUR_URL"

For some reason I was always getting Spanish audio when downloading from curiositystream with no format selected (I think this should be improved). I managed to make it download the en stream with this: -f 'bv+ba[language=en]' (notice it's language, not lang which is printed by -F).


Implement sophisticated draggable window functionality

Implements #241

Refactor preferences UI with a new "Window" page.

Implement sophisticated draggable window functionality, with ability to specify whether or not to remember the dragged window position.

New Window preferences UI also allows us to always open the window at a specified screen position (or to ignore this and always open in the center of the screen), or on a specified screen (for multi-screen environments).

@appetizermonster can you make me a member of the Hain organisation (https://github.com/hainproject) ?

@appetizermonster @cpriest please see latest changes


US 01.03.01 As a player, I want to remove QR codes from my account.

As a player, I want to remove QR codes from my account.
Acceptance Criteria

The player can select and remove a QR code from my account.
The player is asked to confirm it wishes to remove the QR code from the account.
The player can view the contents of the QR code they are about to remove.
The QR code is removed from the account.

app can remove individual codes and firebase will reflect that


K8SPS-212: Add validation rules

CHANGE DESCRIPTION
Problem:
Some CR fields and their values are related in the sense when one field value is specified, some other should be a certain value. For example, if we set clusterType=group-replication then haproxy.enabled should be false. Now you can set it to enabled, but HAProxy would not be started at all since it does not work with GR cluster type.
Cause:
Lack of validation when applying the CR.
Solution:
Utilise CRD Validation Rules to validate CR upon creation and reject the create request if certain rules are not met.
Now when the user wants to create a CR with GR cluster type and he enables HAProxy, he will get a response like this.
➜  k apply -f deploy/cr.yaml
The PerconaServerMySQL "cluster1" is invalid: spec: Invalid value: "object": HAProxy can not be enabled with 'group-replication' clusterType

CHECKLIST
Jira

[x] Is the Jira ticket created and referenced properly?
[x] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[x] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[ ] Is an E2E test/test case added for the new feature/change?
[ ] Are unit tests added where appropriate?

Config/Logging/Testability

[x] Are all needed new/changed options added to default YAML files?
[x] Are the manifests (crd/bundle) regenerated if needed?
[x] Did we add proper logging messages for operator actions?
[x] Did we ensure compatibility with the previous version or cluster upgrade process?
[x] Does the change support oldest and newest supported PS version?
[x] Does the change support oldest and newest supported Kubernetes version?


Godot vs2015 WindowSDKDir Cannot Compile

C:\Program Files (x86)\Microsoft Visual Studio 14.0>D:
D:>cd godot-*
D:\godot-master>scons platform=windows
scons: Reading SConscript files ...
Configuring for Windows: target=debug, bits=default
Found MSVC compiler: x86
Compiled program architecture will be a 32 bit executable. (forcing bits=32).
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str':
File "D:\godot-master\SConstruct", line 327:
detect.configure(env)
File "./platform/windows\detect.py", line 343:
configure_msvc(env, manual_msvc_config)
File "./platform/windows\detect.py", line 196:
env.Append(CPPPATH=[os.getenv("WindowsSdkDir") + "/Include"])
D:\godot-master>

You have to open the "VS2015 x86 Native Tools Command Prompt" for all the paths to resolve properly.
If you are building 64bit, then "VS2015 x64 Native Tools Command Prompt"

If you don't have these listed in your Start Menu, you have to go to Programs and Features and Modify your VS2015 install to include C++. More info can be found here: https://blogs.msdn.microsoft.com/vcblog/2015/07/24/setup-changes-in-visual-studio-2015-affecting-c-developers/

Do you you have the C++ components and the Windows SDK installed?


Checksum sidebar addresses

What it solves
Resolves #3005
How this PR fixes it
Every address used in the sidebar is checksummed.
How to test it
Add a duplicate safe to the state and check that it isn't displayed twice.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 8 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.008%) to 31.672%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/SafeListSidebar/SafeList/index.tsx
0
8
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/components/SafeListSidebar/SafeList/index.tsx
1
0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
2985

Relevant Lines:
8386

💛  - Coveralls

Seems to work, thanks Aaron!

Looks good to me.
The storage keeps updating on its own, even with ImmortalDB deleted, but by doing the changes fast enough I was able to reproduce the issue and then try the same in this PR to check that the fix was effective.
The snapshots.
Prod:

This PR:


Network Policy not working as expected with configured

Bug report

General Information

Cilium version (run cilium version)
Kernel version (run uname -a)
Orchestration system version in use (e.g. kubectl version, Mesos, ...)
Link to relevant artifacts (policies, deployments scripts, ...)
Upload a system dump (run curl -sLO https://github.com/cilium/cilium-sysdump/releases/latest/download/cilium-sysdump.zip && python cilium-sysdump.zip and then attach the generated zip file)

How to reproduce the issue

instruction 1
instruction 2

Closing, assuming it was intended to be https://github.com/cilium/cilium/issues/11096


fixed small typos

Fixed all the typos where blue was written as bluee mentioned on this issue code #177

Nice!
Let's just wait until the standard checks are done. Once that's green I'll gladly hit merge 👍

Nice!
Let's just wait until the standard checks are done. Once that's green I'll gladly hit merge +1

Okay, Thank you sir


SteamVR Fail in Linux

GTX 1660 Ti, Arch Linux

ALVR and SteamVR load fine for me:

Fedora 36
Radeon 6600 XT
SteamVR beta 1.24.3
ALVR v19.0.0-dev02+nightly.2022.09.19

Yeah, for me too with v19

But... does it work? Try to check integrity of steam vr via steam.
Working for me on:

Manjaro
Radeon 6800 XT
last version of steamvr and ALVR
Working also via usb.. just try to fix steamvr via settings on steam

Yes v19 works (h264 only)

@Espionage724 what headset are you using it with? I can't get it to work on my system with any ALVR build

Fedora 36
6900XT
SteamVR (tried various versions)
ALVR (18.2.3 +  nightly builds)


First Commit Add Credit Card Holder

Hi Sam,
My first attempt to add a Credit Card Holder. Please review.

Looks good 👍
I'll just need merge this changes with mine that contains toggleable name / cvc fields and it would be perfect

I've tested another time and noticed that the Name Field is displaying the Numeric keyboard, needs to be fixed for the full keyboard version

Most changes are in the master branch!


Modify Update command to allow only one occurrence of any prefix

Enhance update command to only accept a single occurrence of any prefix and throw ParseException if multiple occurrences found.
Original implementation picks the last occurrence if there are multiple prefixes. This is less tidy and liable to generating unintended results from user inputs.

Closed with #190


Signing transactions automatic

IMO you should not click the button on the bottom every time you complete a step and want to continue

transactions should popup automatically, as they do when buying nft and using autoteleport
make the transactions popup automatically after the preceding is completed

hmm it appears that here its automatic and next step is started once the last one is finished
https://github.com/kodadot/nft-gallery/pull/8437#issuecomment-1847117717
maybe @prury knows? 👀

hmm it appears that here its automatic and next step is started once the last one is finished
https://github.com/kodadot/nft-gallery/pull/8437#issuecomment-1847117717
maybe @prury knows? 👀

Yes, on that PR i only click the button once and wait for transaction signing pop ups to appear


Minor cleanups to module-node extra

Fix value stack index use in eval module helper
Ensure test.c exitcode is != 0 when errors occur (also add this behavior to other extras)
Other trivia

Ok, my cleanups are complete. Good stuff, it's awesome there's now an off-the-shelf solution for people wanting to use a Node.js-like loader :)
On thing I'm not very happy about is the test coverage; a lot of basic mechanics are not covered (same applies to other extras too). But it's probably best not to try to fix it here (in test.c); it's better to figure out what to do about extras and examples w.r.t. testing. Currently the only examples/extras that get some coverage are those integrated into duk and covered by tests/ecmascript but that's mostly for legacy reasons. There needs to be a proper solution for doing a lot of tests not directly related to the core stuff, and so that every example/extra doesn't need a mini testing framework.

@fatcerberus I'd like to tackle the built-in 1.x loader next -- do you still want to take that on, or should I?

Hm... since you just wanted to copy the core loader from Duktape internals, it'd probably be best for you to do it.  I'm not familiar with how everything is wired up internally w.r.t. modules.

I might revisit the Node.js loader at some point in the future, I'd like to see if I could implement module.parent and module.children to make this even more compatible with Node modules.  Well, at least the ones that don't need to call core Node.js APIs anyway.

The nrets on line 64 of duk_module_node.c is unreferenced now - you can delete it.

Added a few warning options to gcc:
duk_module_node.c: In function ‘duk__handle_require’:
duk_module_node.c:65:14: warning: variable ‘parent_id’ set but not used [-Wunused-but-set-variable]
  const char *parent_id;
              ^
duk_module_node.c:64:12: warning: unused variable ‘nrets’ [-Wunused-variable]
  duk_ret_t nrets;
            ^

parent_id is used via duk_require_string() to verify its existence but it can be cast to void.

Ok, I added a global binding assert(value, message) so that the tests can actually throw on error:

https://github.com/svaarala/duktape/blob/a5d3026f6ee01d4d8a4bd4544e529a7744e1365e/extras/module-node/Makefile

This should be enough for make test to fail with exit code if any of the tests fail. Assert-based unit tests are quite common so maybe this is a reasonable stop-gap for the extras.

Just thought of this: Might be worth adding a comment in the code that __dirname is not set because the loader can't make any assumptions about the underlying file system.

Right, could resolve/load return that because they are aware of the file system?

For example, could load set module.dirname if a directory name is applicable, and that would get passed to the module wrapper (and undefined if it isn't set)?

I assume resolve would be the better place to set it.

Why? It gets called every time a require() happens, even when the module turns out to be cached and we don't even create a module object.
Resolve callback could return both a resolved ID and a tentative dirname (in case a module gets created) but that'd mean returning an object from the resolve callback. That wouldn't necessarily be a bad idea, because it's not hard to foresee there might be interesting metadata to resolving than just getting the ID.
Another option would be to always create a module object when resolving, and throw it away in case it's already been loaded.

Ok, I'll open a pull for it today.

Hmm, so assuming resolve would be the callback where an application would most naturally figure out the __dirname, the alternatives would be:

Change resolve() return value to be an object which provides both resolved ID, dirname, and maybe something else in the future: { id: "foo", "dirname": "modules/stuff" }.
Change resolve() to return a string but use some separator to allow a dirname to be included, e.g. foo/bar.js|foo. Seems too hacky to me at least :).
Change the require() implementation to always create a tentative module object first, and give it to require(). If the module is loaded, the tentative module object gets used; otherwise it's discarded. This allows the resolve() callback to set e.g. module.dirname = "modules/stuff"; directly without changing the plumbing, and also adds some extensibility. The downside is creating a throwaway object for each require() call.
Something else? :-)

Hm, there's no module.dirname in Node (at least I don't think so), only the _dirname free variable which gets passed to the module wrapper as an argument.
Creating a fresh module for every require() might be overkill since in a large application it's possible for half (or more) of the require() calls to be already in the cache.  It wouldn't be very efficient to create a large number objects just to discard them immediately.
That said, resolve seems to be in the best position to come up with a canonical directory name, which is why it seemed awkward to me to give that responsibility to load--which might only care about getting source from the filename it was given without any concept of e.g. path format.

Following up on the throwaway module objects: It could be a concrete issue in the case of a Duktape build with refcounting and voluntary GC disabled.  Then the throwaways will only be collected in an emergency which is probably not ideal.

I proposed module.dirname just as a way of passing that information from resolve() to load() (which actually needs it) - not because it'd be the most logical place for it.
It would be cleanest IMO if resolve() returned an object containing the resolved ID and any other metadata; this intermediate result could then be consumed by load() as is so that that whatever metadata was looked up would be available without changing the compatibility related parts of the arrangement. This approach is not ideal when you just want the module ID and don't have any other metadata to pass; in this case the extra object is just extra work to deal with. OTOH you don't usually write dozens of resolve/load functions, so it's a one time thing usually and not as important as something that appears 100 times in a code base.

With automatic periodic mark-and-sweep disabled there are two situations where mark-and-sweep runs:

The user requests it.
An allocation attempt fails.

The second condition ensures that if we were to run out of memory, several rounds of mark-and-sweep are tried before actually erroring out on an out-of-memory error. This also means that even with voluntary GC disabled, no out-of-memory occurs if there is actually memory available.

My view is probably colored quite a bit by versioning concerns: almost every time you take a shortcut in API design, especially for interfaces quite likely to change, there's much more effort in dealing with versioning issues than with the actual functional changes.
Here, based on the experiences with the Duktape 1.x loader framework, it's inevitable there will be additions to the resolve/load process which one doesn't yet foresee. Some of them may be changes in the Node.js side, i.e. the public API, and others might be custom to the Duktape environment.
So the most version compatible (considering both C and Ecmascript source compatibility) would be something like:

// args = all the context related to resolving a module
function resolve(args) {
    var requestedId = args.requestedId;

    // Come up with resolved ID
    var resolvedId = ...;

    return {
        resolvedId: resolvedId,
        // ... any other metadata
    };
}

// args = all arguments related to loading the module from the loader framework
// lookup = verbatim lookup result object from resolve() call
function load(args, lookup) {
    var id = args.id;  // resolved ID

    return {
        source: sourceCode,
        // whatever additional metadata is eventually needed
    };
}

Interaction with the module loader is via objects; lookup result passes as an object from resolution to loading, and load result is an object which is easy to extend (and it's quite easy to foresee source code is not the only possible result).
I'm not suggesting we concretely do this, but just wanted to illustrate what kind of API design I think works best regards versioning when the number of changes over time is high. Using objects establishes key/value containers which can be evolved without changing the formal signatures (C prototypes, value stack conventions, etc).

The above design approach is, by the way, one of the main reasons I'd very much like to offer good multi-property get/set APIs. It would make it easier to use object-based, versionable APIs both internally and externally.

I think I would be okay with it if resolve returned an object.  I can sympathize with the compatibility issues, as I've started trying to honor semantic versioning with minisphere too and it's not always easy.

So I suggest we finish this pull so that master has a fully functional version and use a separate pull to change the mechanics if that makes sense after sleeping on it.

I agree with that sentiment.  Especially since the version in master is currently broken. ;-)

Also might make sense to reconsider the current implementation in a week or two, if I find enough time to finally complete some multi-property API calls.

Ok, I'm merging this; __dirname issue will be handled separately.


Block weak encryption types

Even though some Kerberos implementations and services may allow RC4-HMAC, this program should block those weak types.
Need to find out which types are weak.

This may not be possible. GSSAPI doesn't appear to reveal encryption type, keytab version number, or timestamp.


addNode error

addNode returns
TypeError: Cannot read property 'visible' of undefined bootstrap-treeview.js:606     at Tree._setVisible (/Volumes/ssd/git/a2ds/server/office/public/libs/treeview/dist/bootstrap-treeview.js:606:40)     at Tree.<anonymous> (/Volumes/ssd/git/a2ds/server/office/public/libs/treeview/dist/bootstrap-treeview.js:572:12)     at Object.e (/Volumes/ssd/git/a2ds/server/office/public/assets/lib/jquery/jquery.min.js:2:3556)     at Function.each (/Volumes/ssd/git/a2ds/server/office/public/assets/lib/jquery/jquery.min.js:2:2716)     at Tree._setExpanded (/Volumes/ssd/git/a2ds/server/office/public/libs/treeview/dist/bootstrap-treeview.js:571:8)     at Tree.<anonymous> (/Volumes/ssd/git/a2ds/server/office/public/libs/treeview/dist/bootstrap-treeview.js:1343:12)     at Array.e (/Volumes/ssd/git/a2ds/server/office/public/assets/lib/jquery/jquery.min.js:2:3556)     at i (/Volumes/ssd/git/a2ds/server/office/public/assets/lib/jquery/jquery.min.js:2:28018)

new node is just {text:"label"}

jquery: 3.2.1
bootstrap 4.0.0

The library doesn't support bootstrap 4 and for now there's no plan to do so.
https://github.com/patternfly/patternfly-bootstrap-treeview/issues/78

can you point me a bootstrap 4.0 treeview library, please ?

Sorry, but I have no information about such library.

ok, thanks
maybe you could add an alert on the readme that the library isn't compatible with bootstrap 4.0
because for now it's just  "works with bootstrap >= 3.0.0"


Harmonised links to NUG

Hi David,
Rather than commenting on the PR you created to the upstream repo I attempt an PR from my fork to your fork. Basically, I have changed NUG to <<NUG>> everywhere (hopefully). Maybe this is to overdo it a bit, especially where the references occur close to each other. Do feel free to cherry-pick or ignore altogether .... :-))

Hi Lars - Looks good - thanks! I think I'll add the two others. Seems like a good balance. Merging ...


Fix output directory for globs

This is a partial fix for #127.
Previously, user specified globs were placed in the root directory of dummy C project, rather than in the created folder.
Partial fix
This is a partial fix, because the glob works with wildcards like certs/*, but doesn't work with wildcards like certs*, the crate globwalk used for finding files doesn't return the right list of files when using certs*.
We have two choices:

Edit the README.md to change mentions of foo* and bar* to foor/* and bar/*
Fix the way embuild, the crate used for copying files, finds files.
https://github.com/esp-rs/embuild/blob/5e12da302f372c05d20a149b00eca1befde185f6/src/build.rs#L95-L114

Example
ESP_IDF_GLOB_CRT_BASE = { value = ".", relative = true}
ESP_IDF_GLOB_CRT_CERT = "certs/certificate.pem"

.
├── Cargo.lock
├── Cargo.toml
├── certs/
     └── certificate.pem
├── README.md
├── rust-toolchain.toml
├── sdkconfig.defaults
└── src
     └── main.rs

This will put the file certificate.pem in the directory certs at the root of the dummy C project
.
├── bindings.rs
├── build
│   └── ...
├── certs
│   └── certificate.pem
├── CMakeLists.txt
├── esp-idf-build.json
├── gen-sdkconfig.defaults
├── main.c
└── sdkconfig

Thanks for the (partial) fix!


request.getmetadata no longer returns FocusFOM

Describe the bug
My app has a live camera preview window that displays some metadata alongside. After the last Picamera2 update it crashes with KeyError: "FocusFOM"
To Reproduce
It looks like the FocusFOM value is no longer being returned by request.get_metadata(), causing the error.
Hardware :
Raspberry Pi 4, High Quality Camera, current Raspberry Pi OS
Additional context
The camera has a macro lens attached and is manually focused onto a 16mm or 8mm film frame. This was a useful metric to display, as it helps with getting critical focus - adjust the focus until the maximum value is reached. Removing the reference makes my code work, but without this useful feature.
Here's an excerpt from my previously working code:
    def preview_data_update_callback(self, request):
        m = request.get_metadata()
        text = (f'Exposure: {m["ExposureTime"]}\n' +
                f'Gain: {m["AnalogueGain"]:.2f}\n' +
                f'Focus: {m["FocusFoM"]//100}\n')

Hi, thanks for reporting this. Indeed something does seem to have got lost there. I'll look into it, but somewhat suspect we're going to have to make up a new libcamera release.

Thanks! I'm glad it wasn't an intentional feature change. :)

It's only a small fix and I've committed it to the repo. Just need to wait while the packaging/release wheels turn. Hopefully not long.

I think
sudo apt update
sudo apt install libcamera0

should fix it for you now.

Verified working. That did the trick. Thanks for your work on this!

FWIW, I encountered a similar issue ("FocusFoM" keyword missing from metadata dictionary) recently, even after a sudo apt update && sudo apt install libcamera0. However, the problem occurs for me only in the first frame captured after a .start() call. Subsequent frames' metadata contains all the expected keywords, so it is possible to "fix" the issue by just throwing away the first frame, but I figured that this may also be indicative of a larger issue and/or something that is worth investigating. Note also that despite some of the other values being wonky in the first frame(s)—e.g. #824—FocusFoM seems to be the only thing that is ever missing entirely.

Hi, thanks for reporting this. As you know, there are some difficulties particularly with the very first frame, though there are probably some other things that take a bit longer to settle as well. I'm not quite sure how it comes about that some things report default values early on, and some might be missing. It could be a bug, but we probably won't do much until we've done all Pi 5 work. Pi 5 works quite differently in some crucial respects and so we'll need to find solutions that work on both our platforms. So please bear with us... thanks!

Probably worked for me as the camera runs a short while before my code gets round to reading "FocusFoM".
I've a Pi 5 on order and am looking forward to migrating my cine film scanning project to it. The processing and storage speed improvements should really help as these are the main bottlenecks at the moment.
Looks like there might be some fun and games with picamera2/libcamera? My Python (+Cython) application is processing full resolution raw bayer data (from stills captures) from the HQ camera, with the live preview for critical focus and to obtain base exposure and colour balance data. I'm willing to help out and test as and when the Pi 5 and camera cable lands.

Mostly the Pi 5 should behave exactly the same for you. The one important difference which you may encounter is that when you ask for unpacked raw data (presumably this is what you do?) , the pixels will be delivered with one pixel per 2 bytes (as on a Pi 4), but the pixel values will be left-shifted so that all the zero bits are at the bottom and not at the top (as is the case on Pi 4).

Thanks for the heads-up. Looks simple enough - just a change to the lookup table that expands the 12bit data to the full 16bit range used in the rest of the processing.

I now have the Pi 5 and working on modifying my code for Pi5/Bookworm. The extra speed is nice.
It looks like FocusFoM takes a while to appear in the metadata after the camera starts as described by cgobat above causing my application to crash as well, and it's returning a much larger number than previously. As a workaround, I modified my metadata callback to check if it's available first:
    def preview_data_update_callback(self, request):
        m = request.get_metadata()
        text = (f'Exposure: {m["ExposureTime"]}\n' +
                f'Gain: {m["AnalogueGain"]:.2f}\n')
        if 'FocusFoM' in m:
                text += f'Focus: {m["FocusFoM"]//1000000}\n'
...
        self.controls['status_label'].setText(text)

It's not really "meant" to return a larger number, though I recall that during development it kept doing that. So we might want to fix that. It is, of course, entirely arbitrary, so can only meaningful be used in comparisons against other FoMs!

I noticed that it reduces by about a factor of 4 when going from 4056x3040 to 2028x1520 resolution. Based on the number of pixels?  Although arbitary, it's a useful metric to see when manually focussing. Though I think it'd be better if it would return a value normalized to some range independent of image size, or 0 if the FocusFoM value isn't present in the underlying metadata at all. :)

Yes, the FoM is just a summation over all the pixels (in the region or regions being counted). Normalising to the number of pixels sounds like it might be worthwhile, and it would be amusing to see which sensors seem to give best "per pixel sharpness". One for the list of things to look at!

Yes, we finally got round to posting the updates that I've been alluding to in the forums for a while now! So we did fix that oversized FoM thing, then, I was always complaining about it...
I put a post on the forum about the updated software. Mostly things should work the same, but manipulating pixels within image buffers should be faster.

Thanks - I'll check the forum. :)


Update Closure Library to fix typeblocking autocomplete

Firefox 65 no longer reports keypress events for non-printable keys. This breaks typeblock on master. This change updates the Closure Library to fix key handling in the autocomplete widget that typeblock builds upon. Note that because the autocomplete widget uses ES6 code, I needed to fork closure-library and patch it to be ES5 compatible otherwise it breaks our build because GWT 2.8 doesn't understand ES6.
Fixes #1584
Change-Id: Ia732cb6a35725ef49bb5605f1ab0bc6a808fe33b

All tests passed. +1 Verified.


An ERROR message with an ErrorCode == LargeResponse shall not be allowed in ResponseToLargeRequest.

An ERROR message with an ErrorCode == LargeResponse shall not be allowed in ResponseToLargeRequest.

Refer to paragraph 696 in DSP0274_1.2.1.

An ERROR message with an ErrorCode == LargeResponse shall not be allowed in ResponseToLargeRequest.

I have submitted one pull request to add unit test for An ERROR message with an ErrorCode == LargeResponse shall not be allowed in ResponseToLargeRequest.

Test result is fail: Put an ERROR message with an ErrorCode == LargeResponse in ResponseToLargeRequest, currently the requester take this LargeResponse ERROR message as a valid message and then send CHUNK_GET request message.
I think it is not a right behavior, the requester should take it as a invalid message.

This is somewhat related to #1207.

I think maybe we can add the check whether ErrorCode == LargeResponse is in ResponseToLargeRequest field, before libspdm_copy_mem at the following line 489 and 517.
https://github.com/DMTF/libspdm/blob/675ba03723116a6cc3e4f9eb99c78a4450b9e623/library/spdm_requester_lib/libspdm_req_send_receive.c#L483-L500
https://github.com/DMTF/libspdm/blob/675ba03723116a6cc3e4f9eb99c78a4450b9e623/library/spdm_requester_lib/libspdm_req_send_receive.c#L513-L523


Internationalization of previewers

Since internationalization of previewers (as external tool) is now possible, at least for French, it probably would be useful to add
toolName in manifest json and to add in Bundle.properties a list for each toolName
externaltools.'toolName'.displayname

Some initial steps - planning to update the curl commands in the README to include a toolName and just added a Dataverse PR (#7478) to continue showing the default displayName until the toolNames get in the Bundle.


AuthorizationCodeFlow requires scopes when empty scopes are valid.

I encountered this while trying to set up an AuthorizationCodeFlow without scopes.
According to here: https://developer.spotify.com/documentation/general/guides/authorization-guide/#authorization-code-flow

If no scopes are specified, authorization will be granted only to access publicly available information: that is, only information normally visible in the Spotify desktop, web, and mobile players.

However currently AuthorizationCodeFlow.valid() enforces scopes to be non-empty.

You are right.
In this case the scopes should not be checked.
I will remove this in the future. If you want to create a pull request, I would be happy to merge it


add matter to espressif-ide (CON-611)

how can I add matter to espressif-ide? I download Matter and tried to compile a code but the error "Please set ESP_MATTER_PATH to the path of esp-matter repo" was shown.

To resolve the error  "Please set ESP_MATTER_PATH to the path of esp-matter repo", you need to export the path of esp-matter repository.
Traverse to the esp-matter repository and run the command . ./export.sh.
For more help regarding building and trying out examples please refer https://docs.espressif.com/projects/esp-matter/en/latest/esp32/developing.html.

@amin31
You can add ESP_MATTER_PATH into espressif-ide by going on the window-->Preferences-->C/C++-->Build-->Environment the Add the following Variables:
ESP_MATTER_PATH : path/to/esp-matter
ZAP_INSTALL_PATH : path/to/esp-matter/connectedhomeip/connectedhomeip/.environment/cipd/packages/zap
Append the following lines in PATH variable by using ' : ' between each value
/path/to/esp-matter/connectedhomeip/connectedhomeip/.environment/cipd/packages/pigweed/:/path/to/esp-matter/connectedhomeip/connectedhomeip/out/host
You can also add IDF_TARGET : esp32c3 (according to your device)

tnx my problem got solved

I have done these workarounds. There is one dependency that project directory must have a .git folder else project build is failing. For testing purpose I added a dummy .git file and build process moved one step ahead (Is there anyway that we can remove .git dependency?).
I tried all fixes, still build is failing. Following is the error.
-- git rev-parse returned 'fatal: not a git repository (or any of the parent directories): .git'
ESP Insights Project commit: HEAD-HASH-NOTFOUND
CMake Error at /home/oem/esp/esp-idf-v5.2.1/tools/cmake/component.cmake:281 (message):
SRC_DIRS entry
'null:/home/oem/esp/esp-matter/connectedhomeip/connectedhomeip/zzz_generated/app-common/app-common/zap-generated/attributes'
does not exist.
Call Stack (most recent call first):
/home/oem/esp/esp-idf-v5.2.1/tools/cmake/component.cmake:443 (__component_add_sources)
/home/oem/esp/esp-matter/components/esp_matter/CMakeLists.txt:33 (idf_component_register)
-- Configuring incomplete, errors occurred!
See also "/home/oem/ec_workspaces/ec_matter_ws/light_test/build/CMakeFiles/CMakeOutput.log".
cmake --build . -- -v
ninja: error: loading 'build.ninja': No such file or directory
I have cross verified the existence of attributes directory.

@S-A-Hussaini Did you make any changes to the CMakeLists.txt of the example?

Yes I have updated the files path accordingly.

Thanks for the reference. I have followed all the steps as you mentioned. But still I am getting the same build error.
SRC_DIRS entry
'null:/home/oem/esp/esp-matter/connectedhomeip/connectedhomeip/zzz_generated/app-common/app-common/zap-generated/attributes'
does not exist.

@S-A-Hussaini
Have you installed esp-matter?
Can you build the light example from the terminal ?

YES I have installed ESP-MATTER SDK and successfully able to build the light example in Linux terminal.

@S-A-Hussaini I suspect you may have missed a '/' at the end..somewhere in configuring the environment variables. Can you please try and check.

@sayondeep Thanks a lot for guidance, issue is resolved.

how can I add matter to espressif-ide? I download Matter and tried to compile a code but the error "Please set ESP_MATTER_PATH to the path of esp-matter repo" was shown.

how can I add matter to espressif-ide? I download Matter and tried to compile a code but the error "Please set ESP_MATTER_PATH to the path of esp-matter repo" was shown.

https://github.com/espressif/esp-matter/issues/501#issuecomment-1700432298


Fix docs issues.

This PR should address 3 more of the docs issues from https://github.com/uutils/coreutils/issues/5692 , regarding more, test and vdir commands.The last issue remaining would be the one regarding the usage string of everything based on hashsum.

I would be glad to solve the hashsum issue too, but I am not sure what needs to be done exactly to the usage string.


Paco/integrate marketplace api auth

Description
integrate marketplace auth
Is this PR related with an open issue?
Related to Issue #
Types of changes

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

Checklist:

[x] Follows the code style of this project.
[x] Tests Cover Changes
[x] Documentation

The issue is that the subgraph doesn't load but I didn't touch anything there
Waiting for the subgraph (WhitelistingCondition) to be running at http://localhost:9000/subgraphs/name/neverminedio/WhitelistingCondition


Using node.js require in eel

Hello,
I am having some errors in my electron app that I believe are due to how eel deals with electron. My problems are that when I try and create my own minimise and close buttons, it says

Uncaught ReferenceError: require is not defined at index.html:137

and

Uncaught ReferenceError: require is not defined at initNodeRequire (index.js:123) at index.js:109

when the page is loaded,
then

Uncaught ReferenceError: BrowserWindow is not defined at window_minimise (index.js:113) at HTMLButtonElement.onclick (index.html:18)

when I click minimise.
I go into more detail here, and I have adapted my JS file to use the code in the answer suggested, except I removed the {} around BrowserWindow.
I tested this function without eel by changing mainWindow.loadURL('http://localhost:8000/html/index.html') to mainWindow.loadFile('web/html/index.html') and starting it with npm start. Then it worked.
I believe the issue is that node features such as require do not run in the browser, and since this is retrieving a webpage from the browser it causes the error.
Do you know any way that this can be resolved?
Thanks.

Perhaps browserify is required?

I have encountered this problem, I can't remember exactly how I solved it. I think it you have to set 'nodeIntegration: true' when you make the BrowserWindow.
I am working on "first class" Electron support but I have been massively delayed in releasing it unfortunately because been very busy

@ChrisKnott Yes I found a bunch of posts telling me to do that, and I tried it but it didn't solve it. I think it might be a fundamental issue in that node doesn't run in the browser without using something additional such as browserify. However, I'm pretty sure I had it working like it is right now on my old computer about 9 months ago which is strange.

Just to make sure it wasn't anything weird that I was doing, I combined the electron-quick-start repo with your hello world demo and it still gave the same errors.
Here are the changes I made:
mainWindow.loadURL('http://www.localhost:8000/index.html') in main.js.
<script>
	// You can also require other files to run in this process
	require('./renderer.js')
</script>
<script type="text/javascript">
	initNodeRequire();
	const BrowserWindow = nodeRequire('electron').remote;

	function window_minimise(){
	  let window = BrowserWindow.getCurrentWindow();
	  window.minimize();
	}

	function window_close(){
	  let window = BrowserWindow.getCurrentWindow();
	  window.close();
	}

	function initNodeRequire(){
	   window.nodeRequire = require;
	   delete window.require;
	   delete window.exports;
	   delete window.module;
	}
</script>

After the body tag in index.html. (note, I modified your index.html, not theirs).
And in hello.py I did
options = {
	'mode': 'custom',
	'args': ['node_modules/electron/dist/electron.exe', '.']
}
...
if __name__ == "__main__":
	eel.init('web')
	eel.start('index.html', options=options)

@04fsnape Can you try the new example I just pushed and see if it works?
Press ctrl+shift+i to open dev control, then in the JS control - you should have either require or nodeRequire defined (depending on which Eel version you have).

@ChrisKnott Works perfectly, thanks! I removed
<script>
	// You can also require other files to run in this process
	require('./renderer.js')
</script>

from index.html, and changed the other script to
const BrowserWindow = nodeRequire('electron').remote;

  function window_minimise(){
      var window = BrowserWindow.getCurrentWindow();
      window.minimize();
  }

  function window_close(){
      var window = BrowserWindow.getCurrentWindow();
      eel.quit_app_x();
      window.close();
  }

For remote to work in the latest version of Electron, you need to add the following to webPreferences:
webPreferences: { enableRemoteModule: true, nodeIntegration: true }
Also, the eel.quit_app_x(); has been used by @04fsnape for his project, hence, that should also be removed, or you might get errors. I know that it's dumb, but I was dumb enough to leave it in.

Here is a script for minimizing, maximizing, and closing:
`const BrowserWindow = nodeRequire('electron').remote;
function window_minimize(){
var window = BrowserWindow.getCurrentWindow();
window.minimize();
}
function window_maximize(){
var window = BrowserWindow.getCurrentWindow();
if(!window.isMaximized()){
window.maximize();
}else{
window.unmaximize();
}
}
function window_close(){
var window = BrowserWindow.getCurrentWindow();
window.close();
}`


fix build on node 8

Thanks for your fix. However, it appears that earlier versions of node do not support the updated version of rdf-ext (according to the Travis build check).


Which companies are using SkyWalking RocketBot

Daocloud+www.daocloud.io

Ref https://github.com/apache/incubator-skywalking/issues/443  Share the users to SkyWalking main repo. Also welcome and encourage everyone to send a pull request to add you into the official list
https://github.com/apache/incubator-skywalking/blob/master/docs/powered-by.md

Could we close and unpin this? Also remove https://github.com/TinyAllen/rocketbot#who-uses-skywalking-rocketbot .
As we are moving in Apache as primary UI, all SkyWalking users will be using this UI :)


March 6th, 2023 Community Meeting

Please add a topic in this thread and add a link to the GitHub issue associated with the topic.
Please make sure you give folks enough time to review/discuss the topic offline on GitHub before coming into the meeting
(optional) Paste the image of an animal 😸

Low attendance today, no new topics to discussed. Meeting was adjourned after a couple of minutes.


chore: update typography for smaller screens

Added typography for smaller screens

@Shurtu-gal Can you please review this?

On it


Connect Bug

I did an experiment：
1：I ran chat/main.go on the public network.
2：I also ran chat/main.go on my local intranet.
The intranet takes the initiative to connect to the public network.
and connect failure
log：
1：public network：
I0914 15:35:59.067335    5092 main.go:45] Private Key: e1c79968020ee18a725849826e7130c4bb9e4962d255b6829fd8ab64534658f85640464458ddeef9eeb93368779c7015a2a43ff374ff23b3eae23b47dbfb75e8
I0914 15:35:59.067392    5092 main.go:46] Public Key:<PHONE_NUMBER>ddeef9eeb93368779c7015a2a43ff374ff23b3eae23b47dbfb75e8
I0914 15:35:59.067700    5092 network.go:206] Listening for peers on tcp://<IP_ADDRESS>:3001.
E0914 15:38:06.366141    5092 network.go:319] dial tcp <IP_ADDRESS>:3000: connect: connection timed out
2：local intranet：
I0914 15:36:05.452905   21932 main.go:46] Private Key: 31d4fefef611b233374a1b99363eb55dd0919b383108911bc909f455de22af0d425efc07c0d7d68d203d0e3ea1c8702a2968dd3d16f34a3909648520ade5c91d
I0914 15:36:05.459852   21932 main.go:47] Public Key: 425efc07c0d7d68d203d0e3ea1c8702a2968dd3d16f34a3909648520ade5c91d
I0914 15:36:05.464287   21932 network.go:206] Listening for peers on tcp://<IP_ADDRESS>:3000.
I think the port of public network connect local intranet should‘t be 3000 ，is right？
forgive my poor English

Options have been provided when using NAT traversal to be able to specify the internal/external ports to use, alongside the external address to broadcast to other peers for Noise v2.0.


Feat: enable slinky.marketmap.v1.Query/Market

https://github.com/neutron-org/neutron-tests/actions/runs/11291070042


[Feature Request] Add .http request format import

Insomnia Version: latest
Operating System: Debian Stretch

Details
Support for WebStorm HTTP request collection

Feel free to submit a PR for this if you'd like to the internal
insomnia-importers package
https://github.com/getinsomnia/insomnia/tree/develop/packages/insomnia-importers

I am taking this

Hi @KarthikSiddarth
Any news on this?

Hi @KarthikSiddarth
Any news on this?

started working on it, will update soon


Sync API

Thanks for this great library.
I have a use case where I would like to return the results of OpenPGP.encrypt from a synchronous function. Drilling down through the code I see that a lot of internal functions are async, but it's not clear to me why.
Is it not feasible to implement the core functionality without async?

I tried removing all the async to see if there was somewhere deep in the code that required async, and I found that there was none. I guess making things async was a design choice? If so, I'm curious about the reason.
I apologize if my understanding is lacking, but as far as I know there is no benefit to making this library async:

There is no IO being waited on
Dart is single-threaded so you do not have parallelization gains
If anything there appears to be significant overhead from async: dart test is 20 seconds faster on my sync branch than on the commit I branched from (0m58s vs 1m08s)

If anything, a huge advantage of implementing in pure Dart is that you can make the logic synchronous; see e.g. flutter-openpgp that is forced to be async because it (sometimes?) uses platform channels. I think it's best left up to the library consumer whether to compute asynchronously or not.
If you would consider moving to default-synchronous, I've opened #6. Please let me know if you have feedback.

Closing because v2.0.0 is no longer async


Datetimes need a timezone

datetimes need a timezone

That would probably need a separate discussion / design. If we start this then I guess all our datetimes always will need a timezone, or we need to set it in the config.
Originally posted by @visr in https://github.com/Deltares/Ribasim/issues/887#issuecomment-1856024734

TOML support local date time and offset date time. Currently we use local. We could support offset date time for starttime and endtime, also as a way to indicate to consumers of our data on how to interpret our time zone naive times if they have to.
The GeoPackage spec confuses me a bit, it supports a DATETIME that must be in UTC, but the time columns we have right now are TIMESTAMP and of the form 2020-01-01 00:00:00, which is time zone naive.
Arrow timestamps optionally support a timezone, and are time zone naive otherwise.


MGMT-1736 Add CreatedAt column to clusters list

Depends on https://github.com/mareklibra/facet-lib/pull/63

Reverted back to not using relative time


ARROW-3517: [C++] Add a workaround for MinGW-w64 32bit crash

See also: https://sourceforge.net/p/mingw-w64/bugs/767/

Rebased to see if Windows build will run OK


chore: drop Windows 32 bit drivers and use always 64 bit

https://github.com/microsoft/playwright/issues/8045

Pavel lgtm'ed in chat - let's merge!


Checkpoint of the model

Hello, thank you very much for your excellent work. I am currently working on a ground truth system for autonomous driving, and I found your article on offline labeling and tracking extremely helpful. I would greatly appreciate it if you could provide the checkpoint for the model. Thank you very much.

After changing the code structure to OpenPCDet, we have been preparing the model under the new structure and will release it according to Waymo's requirements.
I am still busy with another DDL, so it may take some time to release.
Will update the state in README if released.


ValueError: Got dtype 'float64', which is a forbidden dtype

I am using np.ndarrays to train a model using augmented images, but I keep getting the following error:
ValueError: Got dtype 'float64', which is a forbidden dtype (bool, uint16, uint32, uint64, uint128, uint256, int8, int16, int32, int64, int128, int256, float16, float32, float64, float96, float128, float256).
What is the correct dtype for the imgaug model?

I believe it should be uint8. You can scale your array to [0, 255], then change its type with .astype(np.uint8).

I believe it should be uint8. You can scale your array to [0, 255], then change its type with .astype(np.uint8).

Yes that works. Thanks!


Refactor recording/replaying using abstract recorders/readers

Changelog:

Added reading depth from rosbag
Added support recording depth along with other streams
Make it universal so we can add foxglove .pcap file (here)

TODO:

[x] Add depth->PCL conversion when mcap and depth are enabled
[x] Add check if mcap, images have to be in jpeg format (medium/high quality, test best)
[x] Documentation

No need to review my code, it's perfect :100:


Github Languages not detecting Tsx files

The repo consists of tsx files, but not detected

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages

Which gives Javascript a whopping 99.3041022 % score.. so- it makes sense for TSX not showing up

Ohh, I think that is mainly because of the build folder also being pushed. If put in .gitignore, still it appears because of git cache. Can you try removing that if possible  @shreyass-ranganatha ?

Hey @JawHawk we have fixed this issue and opened a PR!

@mukeshmx Yes, will check it up soon

Thank you, please try and review it before 31st midnight :) @JawHawk


🔨 Refactor wolfram2desmos to align with Desmodder guidelines

Looks good! Loving that it can be enabled/disabled at will.


Update python-linting.yml to use python 3.10

Looks like python 3.7 will be deprecated in June 2023. So updating the python to 3.10 in linting workflow.

The description and title say 3.10 but the code has 3.11?


Random crash with Crop particle MC1.19 Sentimentality3 1.5.0

It happens randomly, near wheat farm. But i do have bunch of mods, haven't tried with only this mod tho.
log

Hi,
A player just reported a similar issue to me (1.19.2), and I think it might be the Growth Block in my Ward Blocks mod.  I see in the log above that they are using Ward Blocks as well.
Here is their new crash report,
crash-2022-09-13_14.45.06-server.txt
it seems to crash on the sparkleTick() method call in the CropBlockMixin.  I suspect it some how conflicts with my growCrops() method for my Growth Block
https://github.com/kwpugh/ward_blocks_fabric/blob/b4558fc93356ab5a54e56355b32ee013be48b7a5/src/main/java/com/kwpugh/ward_blocks/util/WardBlockEffects.java#L195
I'm not sure how the two relate/conflict.  Maybe you can take a look and confirm/refute my theory.
regards
kwpugh

I think it is related to your code here:  https://github.com/skylorbeck/Sentimentality3/blob/69b41eec3d7ddd199e7c82ad8bca4ccb29c84b4e/src/main/java/website/skylorbeck/minecraft/sentimentality3/mixins/Cropmixin.java#L39
but I'm not sure why.  I'm curious what you think.

I didn't get a notification about this update, sorry for the late reply.
I didn't look too deeply but when I was making that method I did have a lot of crashes when rapidly ticking so I bet it is related to that. Thank you for adding more information! @kwpugh


UX upgrade

Given some buttons better CSS
Made it so longtext uses a dialog for editing instead of resizing the field
Made bool nicer to look at
Made enums, line ref, sheet ref, and every other list elements use an autocomplete instead
Fixed Image losing aspect ratio on hover

The main reason I used autocomplete was for lineref cause when the sheet reaches hundreds of lines, the current implem becomes absolute hell to navigate
also completely unnecessary, but the new bool has a cool anim
https://user-images.githubusercontent.com/11213825/163331545-65218500-1020-4cbc-885f-d54f2781bca9.mp4
https://user-images.githubusercontent.com/11213825/163333250-8693197e-34f0-4c03-bda3-8812a948f047.mp4

Hey, any news when this will be merged?

@skymen sorry for the delay here! I never got a notification that this PR was submitted so I'm just now seeing it. We're neck deep in releasing our game on May 12th so I won't have time to check it out before then.
In the meantime, I have to say that what you added here looks incredible. I can't believe someone would take the time to do this and it's much appreciated! My only ask would be, from a feature perspective, is how hard would it be to implement this as well:
https://github.com/microsoft/vscode-webview-ui-toolkit
I've been wanting to revamp the CSS for a while and a lot of what you did feels like it moves in that direction, and I'm wondering if we can unify it with the "native" code components so it feels even better. What do you think?

Yeah basically I'm totally out of my depth on CSS, so I'd love if someone with more proficiency there was able to take that stuff on. A major issue right now for example is that the editor looks awful if not in dark mode, because all the component styles are hardcoded. Code provides CSS variables that would allow you to hook into whatever colors a use set, and I think their web components library uses them as well. Basically unifying all that stuff for Depot would be ideal.
I agree that the simple components are probably simple to implement, but I think some of your UX stuff like the expanded long text box are SUPER awesome, so I'd want to keep that in.
The BIG one is probably the data grid, as that touches sort of "all" the code instead of my hacky table view thing, but it could be worth investigating if you're up for it. It may even give us better stuff like searching / reordering / filtering / etc.

Also, I plan on working more on this in the future, as I'm probably gonna be using Depot for my own game
Awesome! Always happy to see people using the tool. Let me know if you need any help around implementation or anything. I'm about 70% done on a C# source generator for Depot, so if you're in Unity land that could be super helpful as well.

I also plan on writing a custom exporter that compiles the .dpo file into a lossy .json that's optimised for in engine implementation (with all the "editor" data removed and a bunch of duplicate data to make it MUCH easier to read the JSON, rather than writing for loops to run through entire arrays, as this will definitely cause issues at scale.

FWIW the Depot file for Cantata (our game) is like 50K lines of JSON long (all raw Depot) and we dont really have any issues. There's some lag in Code itself sometimes, but otherwise we dont have any issues on the engine side. That said, I think doing a "cleaned JSON export" is really smart, and someone even suggested something like that here (see list item 2).  Basically, the .dpo file is the "project" file (still JSON), but provides export options that let you export everything from the whole file, cleaned of schema info, single records, etc.

I'm currently on vacation, but I'll probably come back to this in June/July. I'll look into the CSS stuff when I do. Feel free to merge this branch when you want in the meantime, I'll clone again when I eventually do this.
I'm not on C#/Unity, I mainly use Construct and other JS based engines. So I planned on writing a JS lib (which makes it INFINITELY easier to work with JSON rather than using C#)

FWIW the Depot file for Cantata (our game) is like 50K lines of JSON long (all raw Depot) and we dont really have any issues.
Yeah I know I'm being overly cautious, it's mostly cause I don't like doing unnecessary work, and I can see scenarios where I'd have issues. For instance, let's say I'm making a fighting game that I plan on shipping to lower end devices, like mobile. I'll have potentially hundreds of hitboxes to describe in the depot file, and to get the hitbox data I might have to search through the entire database multiple times per moves, potentially on every frame for multiple characters.
With that, moves early in the list would be fine, so I probls wouldn't notice right away until months/years into dev and I make a move that lags in 2v2 for that reason.
Also, C# is very performant cause it's compiled, but JS on weak hardware is soooooo slow. I need every CPU cycle I can get. People will play web games with a 2008 android and complain if it doesn't run well :(

I'm currently on vacation, but I'll probably come back to this in June/July. I'll look into the CSS stuff when I do. Feel free to merge this branch when you want in the meantime, I'll clone again when I eventually do this.

Sounds good! I'm not sure when I'll get a chance to check out the changes and verify they work on my end (could also use a testing suite...), but if I get to it before then I'll give it a merge or some feedback.

I'll have potentially hundreds of hitboxes to describe in the depot file, and to get the hitbox data I might have to search through the entire database multiple times per moves, potentially on every frame for multiple characters.

This is more of an architecture issue than a database issue fwiw. Neither Depot or JSON generally are really meant to be an active database in a game. You'd deserialize your data into your game into actual objects, and do operations on those objects. You wouldn't really be reading/writing to a file. But that's a bridge we can cross whenever, happy to support you as you develop!

I never used JSON Schemas, can you explain what they're for?

It's the "standard" way of doing some of what Depot solves, namely making JSON have some type metadata attached to it for easily validation. It doesn't have anything to do with packet transfer netcode stuff.

You'd deserialize your data into your game into actual objects, and do operations on those objects.

For data that needs to change, sure. But for static data, I'd rather just fetch it from the database than copy it elsewhere. But yeah I agree it's not a huge issue in practice.

It's the "standard" way of doing some of what Depot solves

Got it

Looking forward to this, any updates?

Hey, still haven't had time to get back to this. I still plan on working on it some more but it's hard with a tight schedule

Hey, AutoComplete is AWESOME!!!! I'll take this


Proposal: Integrate preview releases in our roadmap/release schedule

I'd like to propose to integrate a single preview releases in our roadmap/release schedule 1/1.5mo before every official release that we are planning.
This would allow us to:

Iron out any (obvious) bugs that we have but are not caught by our e2e tests
Leverage more stable releases because it was already tested out by the community
Provide a simpler way to test upcoming release,s without having to rely on the main image
Get feedback faster

However, it should come with the following caveats:

It should not introduce (too much) overhead for us (for example, no dedicated doc version?)
It does not come with urgent support nor with hotfixes

I think that we can do it, but I'd like to update the docs to reflect that preview/latest release. For example, the webhook changes required the documentation and we should provide it easily if we want to release previews.

And what is your concern with our current scenario? Because end-users can already read them? Is it because it does not explicitly say "preview"?

Currently, we don't have any button to access to unreleased version. If any user wants to check something not released yet in the docs, they need to manually write the next version in the browser bar, which isn't intuitive IMO.

There is also another problem with links when you manually introduce the not released version because the menu still points to latest released version:

If we release preview versions, I'd like to have something more user-friendly to browse those features. For example, ArgoCD documentation has an option in the version selector for that and it's so much user-friendly because they can select it just clicking

Oh I thought we had an "unreleased" or "in development" version, I agree!

Oh I thought we had an "unreleased" or "in development" version, I agree!

I like this approach, to not name it latest but to "unreleased" or "in development".


[SPARK-45251] Add client_type field for FetchErrorDetails

What changes were proposed in this pull request?

Add client_type field for FetchErrorDetails

Why are the changes needed?

Provides optional information about the client sending the request. This field can be used for language or version specific information and is only intended for logging purposes and will not be interpreted by the server.

Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing tests
Was this patch authored or co-authored using generative AI tooling?

@juliuszsompolski @vicennial Please take a look

Merged to master.


Using sap.ui.core.Fragment.load with the controller property

While doing a codebase refactoring to get rid of the legacy UI5 APIs, I've faced a need to replace sap.ui.xmlfragment with the modern, async API — sap.ui.core.Fragment.load.
In the sap.ui.core.Fragment documentation, I've found several snippets how to use this API, e.g.:
sap.ui.require(["sap/ui/core/Fragment"], async function (Fragment) {
	const myFrag = await Fragment.load({
		name: "my.useful.VerySimpleUiPart",
	});
});

In my case, this snippet didn't work until I've added controller: this, following the @boghyon's  advice on SO.
In the API documentation, there is a mention of the controller property:

the Controller or Object which should be used by the controls in the Fragment. Note that some Fragments may not need a Controller while others may need one and certain methods to be implemented by it.

Since in some circumstances the code won't work without the controller-property, wouldn't be better to pay more attention to this property in this API's documentation, providing a code snippet and more detailed explanation when and why this property might be necessary, rather than just mentioning «some Fragments may not need a Controller while others may need one»?

didn't work until I've added controller: this

Better replace sap.ui.xmlfragment with this.loadFragment, as shared in "Methods assigned in XML fragment not triggered" - Stack Overflow, if this can be referred to a Controller instance which becomes the event listener of the fragment automatically.

API reference: sap/ui/core/mvc/Controller#loadFragment

Then, there is no need for an extra call of sap.ui.require with loading of sap/ui/core/Fragment!

You're right. Internally, Controller#loadFragment requires sap/ui/core/Fragment anyway.

Then perhaps it's better to mention in the documentation that this.loadFragment is the preferable alternative over sap.ui.core.Fragment.load to replace sap.ui.xmlfragment.

The topic Instantiation of Fragments includes both APIs loadFragment & Fragment.load with the explanation when to use which one. I'd say it's sufficient for the deprecation notes in sap.ui.*fragment APIs to add a link to that topic.

Implemented with UI5 1.132


add socks5 support

PR Checklist:

[ ] I have run npm test locally and all tests are passing.
[ ] I have added/updated tests for any new behavior.

[ ] If this is a significant change, an issue has already been created where the problem / solution was discussed: [N/A, or add link to issue here]

PR Description

Hi @minionymous, thanks for your contribution! Unfortunately we cannot add extra dependencies to the request project to support this one option. If you'd still like to see this support, I'd recommend writing and publishing your own request wrapper for anyone who wants socks5 support.
If you do, please come back and link to it here so that anyone searching can find it easily.


Fixed lexing of floats that end in a dot and parsing of notes that come before the opening "{" of a struct

I noticed that notes for structs apparently can come before and after the struct body, so needed to change parse_note to take an [..]*Note instead of returning a [..]*Note to be able to "resume" note parsing. This led to changes at the call sites that I hope you are okay with. The same bug may happen for other things with note I think, if they too are allowed to have them before and after the body, because the current parser does not expect this anywhere, aside from the struct code I fixed. I don't fully know the rules where notes can go in the language, so I didn't add this to any other thing that has notes.

This would fix #3 and #4

Latest commit also fixes #6 in my case by keeping all known modules-directories and going through them when resolving loads. I am unsure how the behavior change of get_module_entry affects this:
https://github.com/SogoCZE/jai_parser/pull/5/files#diff-e1e08dfe5721c01b55bdb10221e1df5311ce60bcafcda24ca2decc602fdbade5R83
I only really tested this: https://github.com/SogoCZE/jai_parser/pull/5/files#diff-e1e08dfe5721c01b55bdb10221e1df5311ce60bcafcda24ca2decc602fdbade5R79 #

Thanks!


Duplicate "date" parameter in Information template

My recent uploads have duplicate "date" parameter in the Information template, see attached image.
Same issue is observed in other users's recent files:
https://commons.wikimedia.org/wiki/File:Shinto_Taikyo.jpg
I guess we should first fix the issue and then fix the occurences as well.
Issue created as instructed in #2511

This is out in master now, should be deployed on alpha builds in a few hours. Please let us know if it works for you. :)

Very cool, thank you :) I probably fixed most if not all occurences of the error in existing files on Wikimedia Commons.

Very cool, thank you :) I probably fixed most if not all occurences of the error in existing files on Wikimedia Commons.

Thanks a lot @VojtechDostal 🎉


chore: refactor WorkspaceMemberInfoDTO to MemberInfoDTO

Description

Refactor an existing DTO called WorkspaceMemberInfoDTO to MemberInfoDTO in order to incorporate Application Members as well.

Fixes https://github.com/appsmithorg/appsmith/issues/20722
Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

New feature (non-breaking change which adds functionality)
Chore (housekeeping or task changes that don't impact user perception)

How Has This Been Tested?

All the existing test cases should pass.
New test cases will be added to the EE Pr.

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

Changes contained in https://github.com/appsmithorg/appsmith/pull/21166


DEBUG-log server request rejections

This commit logs server request rejections at the DEBUG level in an
operation's FromRequest implementation.
This commit is analogous to the one in PR #2524 for response rejections.
However, request rejections are not errors, so they shouldn't be
logged at the ERROR level. Indeed, they happen every time the server
rejects a malformed request.
Prior to this commit, the RuntimeError::NotAcceptable variant was the
only RuntimeError variant that was manually constructed. This commit
makes it so that it now results from a conversion from a new
RequestRejection::NotAcceptable variant.
We now leverage futures_util::future::TryFutureExt::map to map a future
that uses RequestRejection as its error into a future that uses
RuntimeError, and centrally log the rejection there. futures_util is
already a transitive dependency of server SDKs (via e.g. hyper and
tower), so adding it is a direct dependency is not worse.
This helps with #2521.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Oops, I realized I copy-pasted the tracing::error! from response rejection logging, contrary to what the commit message says 😅. I fixed that in https://github.com/awslabs/smithy-rs/pull/2597/commits/62fe0f13e9de4c707c17ecb0cddb2db5c4a0ec1d.

Oops, I realized I copy-pasted the tracing::error! from response rejection logging, contrary to what the commit message says sweat_smile. I fixed that in 62fe0f1.

I was wondering about that :)


stuck at agent_host.startMission( my_mission, my_mission_record)

after normal opening of malmo, I try to run tutorial_1.py.
at the first time it enters the section to try to start a mission, it raises RuntimeError.
then it sleeps 2s.
finally stuck at agent_host.startMission( my_mission, my_mission_record )
and dead loop
after reboot, nothing better.
before this time, it works just fine.
can someone know what's wrong?

Is Minecraft running or hanging? You can look at the logs in MalmoPlatform/Minecraft/run/logs.

I solved it by reseting MALMO_XSD_PATH=~/MalmoPlatform/Schemas

l am facing it again.....
l am running 2 malmo(different directory) at the same time, and let two python file connect each one .
after one pair is connected, it will fail to connect if l stop running and restart the malmo.
and if l open the third malmo, no py file can connect to it through agent_host.startMission()

l can run toturial_1, but not any of my file


A possible idea for viewing Sv at different frequencies/periods through slidebars

Questions
It's for the third in > https://github.com/OSOceanAcoustics/echoshader/issues/6#issuecomment-1064600486
In hvplot.line, we can set groupby="time.day" or groupby="time.week" to add a slidebar for selecting certain time.

But for the MVBS, which uses hvplot.image, it can't set groupby="ping_time.day". That will report errors. And setting groupby="ping_time" doesn't make any sense.

In the above picture, I just set x-axis="frequency" to show it can work, leave it.
If we want to show one day or one week's MVBS, we can add a Coordinate called "time_range" to help set a cycle we want to show. "time_range" can represent a day or a week. Its values are consistent with "ping_time".
mvbs_plot = ds_MVBS.sel(frequency=200000).hvplot.image(x='ping_time',y='depth', groupby='time_range',     color='Sv',      cmap='jet', clim=(-80, -30) ).options(invert_yaxis=True)
That may help add two sidebars to select the date and frequency

I will look for some solutions in holoviews too.

If using hvplot to draw xarray image diagram, it can only choose two coordinates for x-axis and y-axis respectively. But other coordinates that are not selected for the diagram will automatically add according sidebars. (If we pick a different, lower dimensional plot type (such as a ‘line’) it will automatically apply a groupby over the remaining dimensions.) And it cannot choose time coordinate both as x-axis and slidebar option at the same time like xarray line diagram, probably because dynamic loading will cause conflicts. So if we wanna show different days' Sv, we can add one more coordinate on behalf with the day or the week we want to check.

I have not yet studied Panel. It will combine the map and Sv diagram, I think.

It can help combine the map and Sv diagram

#18  😄

I think

After studying panel, I start to know there is no need to change Sv data structure.


ERROR about running the code of displace.py

Hi,  I run the displace.py by "python ~/alamode-1.1.0/tools/displace.py --VASP POSCAR -md vasprun.xml -e 1001:6000:50 --random --mag 0.04 --prefix disp_aimd+random_", while the error occurred as shown in the following:
"Usage: displace.py [options] file.pattern_HARMONIC file.pattern_ANHARM3 ...
file.pattern_* can be generated by 'alm' with MODE = suggest.
displace.py: error: no such option: -m"
Thank you very much!

Please upgrade alamode to the latest version (1.5.0).

Please upgrade alamode to the latest version (1.5.0).

Hi, thank you for your replay,
i have tried to installed  the latest alamode by "make -j" in the folder of alm, while the error occurred:
icpc  -O2 -xHOST -qopenmp -std=c++11 -I../include -I/lustre/home/acct-umjzhh/umjzhh-3/include -I/lustre/home/acct-umjzhh/umjzhh-3/software/spglib-1.16.0/include -c fcs.cpp
icpc  -O2 -xHOST -qopenmp -std=c++11 -I../include -I/lustre/home/acct-umjzhh/umjzhh-3/include -I/lustre/home/acct-umjzhh/umjzhh-3/software/spglib-1.16.0/include -c symmetry.cpp
icpc  -O2 -xHOST -qopenmp -std=c++11 -I../include -I/lustre/home/acct-umjzhh/umjzhh-3/include -I/lustre/home/acct-umjzhh/umjzhh-3/software/spglib-1.16.0/include -c cluster.cpp
icpc  -O2 -xHOST -qopenmp -std=c++11 -I../include -I/lustre/home/acct-umjzhh/umjzhh-3/include -I/lustre/home/acct-umjzhh/umjzhh-3/software/spglib-1.16.0/include -c input_setter.cpp
icpc  -O2 -xHOST -qopenmp -std=c++11 -I../include -I/lustre/home/acct-umjzhh/umjzhh-3/include -I/lustre/home/acct-umjzhh/umjzhh-3/software/spglib-1.16.0/include -c optimize.cpp
icpc  -O2 -xHOST -qopenmp -std=c++11 -I../include -I/lustre/home/acct-umjzhh/umjzhh-3/include -I/lustre/home/acct-umjzhh/umjzhh-3/software/spglib-1.16.0/include -c writer.cpp
icpc  -O2 -xHOST -qopenmp -std=c++11 -I../include -I/lustre/home/acct-umjzhh/umjzhh-3/include -I/lustre/home/acct-umjzhh/umjzhh-3/software/spglib-1.16.0/include -c alm.cpp
icpc  -O2 -xHOST -qopenmp -std=c++11 -I../include -I/lustre/home/acct-umjzhh/umjzhh-3/include -I/lustre/home/acct-umjzhh/umjzhh-3/software/spglib-1.16.0/include -c patterndisp.cpp
icpc: error #10106: Fatal error in /lustre/opt/cascadelake/linux-rhel8-skylake_avx512/gcc-8.5.0/intel-oneapi-compilers-2021.4.0-5lwmbv2hynurl3dz6ewqpbqoqjmrfavz/compiler/2021.4.0/linux/bin/intel64/../../bin/intel64/mcpcom, terminated by kill signal
compilation aborted for patterndisp.cpp (code 1)
make: *** [Makefile:26: patterndisp.o] Error 1
make: *** Waiting for unfinished jobs....
icpc: error #10106: Fatal error in /lustre/opt/cascadelake/linux-rhel8-skylake_avx512/gcc-8.5.0/intel-oneapi-compilers-2021.4.0-5lwmbv2hynurl3dz6ewqpbqoqjmrfavz/compiler/2021.4.0/linux/bin/intel64/../../bin/intel64/mcpcom, terminated by kill signal
compilation aborted for optimize.cpp (code 1)
make: *** [Makefile:26: optimize.o] Error 1
Could you give me some suggestions that how to solve it?

Hi.
It's difficult for me to identify the reason of the compilation error.
If you do not know how to fix it yourself, I suggest that you try the CMake option with conda environment. https://alamode.readthedocs.io/en/latest/install.html

Hi.
It's difficult for me to identify the reason of the compilation error.
If you do not know how to fix it yourself, I suggest that you try the CMake option with conda environment. https://alamode.readthedocs.io/en/latest/install.html

Thank you very much, the code worked well.
And i want to know whether the force constant (such as cBTO222.fcs in the example) can be convert into the format of dynaphopy?

I don't know the format of dynaphopy, but probably not convertible for that code.


IBM-Swift/Kitura#883 Rewrite cookie parsing implementation

Description

Rewrite Kitura cookie parsing implementation
Cookie delimiter should be semicolon followed by zero or more whitespace characters
Use first equals in cookie as name/value delimiter, remaining are treated as part of cookie value
If cookie value is quoted(starts and ends with "), remove quotes
Ensure unicode characters in cookies values are supported
Add tests for all these conditions
Cleanup: remove NSString casts that are no longer needed

Motivation and Context
Rewrite Kitura cookie parsing implementation to better match standards
Addresses IBM-Swift/Kitura#883 among other things
How Has This Been Tested?

Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

I've reviewed this but I would like @shmuelk to take a good look at the changes to cookie handling in case there's anything I've missed.

Remove regex use per discussion with @shmuelk
Also added support to unquote cookie values as per spec and added tests for it
@shmuelk @ianpartridge Could you please review this again.

This looks good to me now. @shmuelk merge if you're happy?

Sorry.

Looks ok. I'll merge after CI completes.


Route /list does not work with responsive UI

Describe the bug
the "/list" route doesn't work with responsive UI.
To Reproduce
Steps to reproduce the behavior:

Login to dashboard, resize browser to mobile view
Click list to go to List page
Resize back to desktop view
Observe duplicate list view

Expected behavior
I'm not sure how we should handle this either.
Info

Uptime Kuma Version: master
Using Docker?: No
OS: Windows 10 21H1
Browser: Firefox 91.0.2

Yes, this route is actually for mobile only. May need to redesign or route to homepage in desktop.

I am interested in working upon this , can you please guide me , how to do it , it is my first time contribution


Update NEWEPOCH transition

This is the companion to https://github.com/input-output-hk/cardano-ledger/issues/3148

This has been completed


Remove some obsolete literal handling logic

We no longer convert literals into constructor calls in Sema, SILGen emits the necessary calls.

@swift-ci please test


app:backup:create and app:backup:restore commands doesn't work

I run redmine with postgresql based on docker-compose-ssl.yml - sameersbn/redmine:4.2.9.
It works great, makes automatic backups. But I have a problem with manual backup and restore, described in https://github.com/sameersbn/docker-redmine#creating-backups

docker stop redmine-docker-redmine-1 && docker rm redmine-docker-redmine-1 - OK

When I try to restore backup with the following command:

docker run --name redmine-docker-redmine-1 -it --rm sameersbn/redmine:4.2.9 app:backup:restore

I get the following message:
Initializing logdir... Initializing datadir... chmod: cannot access '/home/redmine/data': No such file or directory
How to solve this issue?

You need to link to your sql container and well as volume mount the data directory.
Ex:
docker run --name redmine-docker-redmine-1 -it --rm --volume=/srv/docker/redmine/redmine:/home/redmine/data --link=postgresql-redmine:postgresql sameersbn/redmine:4.2.9 app:backup:create

Found another way, when using docker compose.
These commands should be executed from the folder with your docker-compose.yml.
  I've been wanting to redo all the documentation using docker compose syntax but it's a lot to change.