Running Cross in distrobox with custom RUSTUP_HOME fails

I am trying to build for x86_64-pc-windows-gnu from a Linux PC using Cross. I am in a distrobox environment (fedora toolbox 40) to contain the cross-compliation stuff separate from the rest of my dev environment.
my current default toolchain is stable-x86_64-unknown-linux-gnu
I have:
CARGO_HOME=/opt/rust/cargo
RUSTUP_HOME/opt/rust/rustup
the permissions on /opt/rust are my_user:my_user 755
When trying to run cross build --target x86_64-pc-windows-gnu, I get the following error:
Error: statfs /opt/rust/cargo: no such file or directory

Im not familiar with what a distrobox is.
Can you run the command with -v and post the output? Also, what version of cross are you using?

Im not familiar with what a distrobox is.

distrobox is a containerized development platform. It's a dev container, but which I have essentially symlinked podman to the host podman client (i.e. running podman ps -a from inside a distrobox actually shows the distrobox itself among the other containers)

Can you run the command with -v and post the output? Also, what version of cross are you using?

sure thing
⬢ [Speedylemon] ❯ cross build -v --target x86_64-pc-windows-gnu
+ cargo metadata --format-version 1 --filter-platform x86_64-pc-windows-gnu
+ rustc --print sysroot
+ rustup toolchain list
+ rustup target list --toolchain stable-x86_64-unknown-linux-gnu
+ rustup component list --toolchain stable-x86_64-unknown-linux-gnu
+ /usr/bin/podman
+ /usr/bin/podman run --userns host -e 'PKG_CONFIG_ALLOW_CROSS=1' -e 'XARGO_HOME=/xargo' -e 'CARGO_HOME=/cargo' -e 'CARGO_TARGET_DIR=/target' -e 'CROSS_RUNNER=' -e TERM -e 'USER=nathaniel' -v /home/nathaniel/Repos/speedylemon/beetlerank:/home/nathaniel/Repos/speedylemon/beetlerank -v /home/nathaniel/Repos/speedylemon/feotui:/home/nathaniel/Repos/speedylemon/feotui --rm -v /home/nathaniel/.xargo:/xargo:z -v /opt/rust/cargo:/cargo:z -v /cargo/bin -v /home/nathaniel/Repos/speedylemon:/home/nathaniel/Repos/speedylemon:z -v /opt/rust/rustup/toolchains/stable-x86_64-unknown-linux-gnu:/rust:z,ro -v /home/nathaniel/Repos/speedylemon/target:/target:z -w /home/nathaniel/Repos/speedylemon -i -t ghcr.io/cross-rs/x86_64-pc-windows-gnu:0.2.5 sh -c 'PATH=$PATH:/rust/bin cargo build -v --target x86_64-pc-windows-gnu'
Error: statfs /opt/rust/cargo: no such file or directory
+ rustup component list --toolchain stable-x86_64-unknown-linux-gnu

it appears it does not specifically have to do with the target
⬢ [Speedylemon] ❯ cross build
Error: statfs /opt/rust/cargo: no such file or directory

and just to be thorough:
⬢ [Speedylemon] ❯ CROSS_CONTAINER_IN_CONTAINER=true cross build
Error:
   0: `podman inspect bazzite` failed with exit status: 125

Stderr:
   Error: no such object: "bazzite"

Stdout:
   []

The name of my container is not bazzite, that's my host PC's hostname. I'm not sure where its getting bazzite from

can you try cross-util run --target x86_64-pc-windows-gnu -i -- bash and poke around the /rust and /cargo folders, check if it's empty etc.
I suspect this is an issue of redirection in filesystem. Could you also show me usr/bin/podman info and /usr/bin/podman version

can you try cross-util run --target x86_64-pc-windows-gnu -i -- bash and poke around the /rust and /cargo folders, check if it's empty etc.

⬢ [Speedylemon] ❯ cross-util run --target x86_64-pc-windows-gnu -i -- bash
error: Found argument 'run' which wasn't expected, or isn't valid in this context

USAGE:
    cross-util <SUBCOMMAND>

For more information try --help

⬢ [Speedylemon] ❯ cross-util --help
cross 0.2.5
Zero setup cross compilation and cross testing

USAGE:
    cross-util [TOOLCHAIN] <SUBCOMMAND>

ARGS:
    <TOOLCHAIN>    Toolchain name/version to use (such as stable or 1.59.0)

OPTIONS:
    -h, --help       Print help information
    -V, --version    Print version information

SUBCOMMANDS:
    clean         Clean all cross data in local storage
    containers    Work with cross containers in local storage
    help          Print this message or the help of the given subcommand(s)
    images        Work with cross images in local storage
    volumes       Work with cross volumes in local storage

I suspect this is an issue of redirection in filesystem. Could you also show me usr/bin/podman info and /usr/bin/podman version

⬢ [Speedylemon] ❯ /usr/bin/podman info
host:
  arch: amd64
  buildahVersion: 1.37.2
  cgroupControllers:
  - cpu
  - io
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.12-2.fc40.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.12, commit: '
  cpuUtilization:
    idlePercent: 94.69
    systemPercent: 1.37
    userPercent: 3.94
  cpus: 16
  databaseBackend: sqlite
  distribution:
    codename: Holographic
    distribution: bazzite
    variant: bazzite
    version: "40"
  eventLogger: journald
  freeLocks: 1975
  hostname: bazzite
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
  kernel: 6.9.12-205.fsync.fc40.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree:<PHONE_NUMBER>
  memTotal:<PHONE_NUMBER>8
  networkBackend: netavark
  networkBackendInfo:
    backend: netavark
    dns:
      package: aardvark-dns-1.12.2-2.fc40.x86_64
      path: /usr/libexec/podman/aardvark-dns
      version: aardvark-dns 1.12.2
    package: netavark-1.12.2-1.fc40.x86_64
    path: /usr/libexec/podman/netavark
    version: netavark 1.12.2
  ociRuntime:
    name: crun
    package: crun-1.15-1.fc40.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.15
      commit: e6eacaf4034e84185fd8780ac9262bbf57082278
      rundir: /run/user/1000/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
  os: linux
  pasta:
    executable: /usr/bin/pasta
    package: passt-0^20240906.g6b38f07-1.fc40.x86_64
    version: |
      pasta 0^20240906.g6b38f07-1.fc40.x86_64
      Copyright Red Hat
      GNU General Public License, version 2 or later
        <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law.
  remoteSocket:
    exists: true
    path: /run/user/1000/podman/podman.sock
  rootlessNetworkCmd: pasta
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.2-2.fc40.x86_64
    version: |-
      slirp4netns version 1.2.2
      commit: 0ee2d87523e906518d34a6b423271e4826f71faf
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 4
      libseccomp: 2.5.5
  swapFree:<PHONE_NUMBER>
  swapTotal:<PHONE_NUMBER>
  uptime: 45h 14m 32.00s (Approximately 1.88 days)
  variant: ""
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
store:
  configFile: /var/home/nathaniel/.config/containers/storage.conf
  containerStore:
    number: 4
    paused: 0
    running: 4
    stopped: 0
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /var/home/nathaniel/.local/share/containers/storage
  graphRootAllocated:<PHONE_NUMBER>904
  graphRootUsed:<PHONE_NUMBER>04
  graphStatus:
    Backing Filesystem: btrfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Supports shifting: "false"
    Supports volatile: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 15
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /var/home/nathaniel/.local/share/containers/storage/volumes
version:
  APIVersion: 5.2.2
  Built:<PHONE_NUMBER>
  BuiltTime: Tue Aug 20 18:00:00 2024
  GitCommit: ""
  GoVersion: go1.22.6
  Os: linux
  OsArch: linux/amd64
  Version: 5.2.2

⬢ [Speedylemon] ❯ /usr/bin/podman version
Client:       Podman Engine
Version:      5.2.2
API Version:  5.2.2
Go Version:   go1.22.6
Built:        Tue Aug 20 18:00:00 2024
OS/Arch:      linux/amd64

The cross package that's on crates.io does not have run. I tried installing the git version as described in the readme, and it does, even though cross's version is the same.

can you try cross-util run --target x86_64-pc-windows-gnu -i -- bash and poke around the /rust and /cargo folders, check if it's empty etc.

⬢ [Speedylemon] ❯ cross-util run -v --target x86_64-pc-windows-gnu -i -- bash
+ /usr/bin/podman
+ /usr/bin/podman version -f '{{ .Server.Os }},,,{{ .Server.Arch }}'
+ /usr/bin/podman info -f '{{ .Version.OsArch }}'
+ cargo metadata --format-version 1 --filter-platform x86_64-pc-windows-gnu
+ rustc --print sysroot
+ /usr/bin/podman
+ /usr/bin/podman version -f '{{ .Server.Os }},,,{{ .Server.Arch }}'
+ /usr/bin/podman info -f '{{ .Version.OsArch }}'
+ /usr/bin/podman run --userns host -e 'XARGO_HOME=/home/nathaniel/.xargo' -e 'CARGO_HOME=/opt/rust/cargo' -e 'CROSS_RUST_SYSROOT=/opt/rust/rustup/toolchains/stable-x86_64-unknown-linux-gnu' -e 'CARGO_TARGET_DIR=/target' -e 'CROSS_RUNNER=' -e TERM -e 'USER=nathaniel' -e 'CROSS_RUSTC_MAJOR_VERSION=1' -e 'CROSS_RUSTC_MINOR_VERSION=0' -e 'CROSS_RUSTC_PATCH_VERSION=0' -v /home/nathaniel/Repos/speedylemon/beetlerank:/home/nathaniel/Repos/speedylemon/beetlerank:z -v /home/nathaniel/Repos/speedylemon/feotui:/home/nathaniel/Repos/speedylemon/feotui:z --name cross-stable-x86_64-unknown-linux-gnu-af38f-eeb90cda1-x86_64-pc-windows-gnu-5e68f-1726588603760 --rm -v /home/nathaniel/.xargo:/home/nathaniel/.xargo:z -v /opt/rust/cargo:/opt/rust/cargo:z -v /opt/rust/cargo/bin -v /home/nathaniel/Repos/speedylemon:/home/nathaniel/Repos/speedylemon:z -v /opt/rust/rustup/toolchains/stable-x86_64-unknown-linux-gnu:/opt/rust/rustup/toolchains/stable-x86_64-unknown-linux-gnu:z,ro -v /home/nathaniel/Repos/speedylemon/target:/target:z -w /home/nathaniel/Repos/speedylemon -t -i ghcr.io/cross-rs/x86_64-pc-windows-gnu:main sh -c 'PATH="$PATH":"/opt/rust/rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin" sh -c bash'
Error: statfs /opt/rust/rustup/toolchains/stable-x86_64-unknown-linux-gnu: no such file or directory

This location does have content in it.
⬢ [Speedylemon] ❯ ls /opt/rust/rustup/toolchains/stable-x86_64-pc-windows-gnu/
bin/  etc/  lib/  libexec/  share/

I suspect this is an issue of redirection in filesystem. Could you also show me usr/bin/podman info and /usr/bin/podman version

⬢ [Speedylemon] ❯ /usr/bin/podman info
host:
  arch: amd64
  buildahVersion: 1.37.2
  cgroupControllers:
  - cpu
  - io
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.12-2.fc40.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.12, commit: '
  cpuUtilization:
    idlePercent: 94.63
    systemPercent: 1.38
    userPercent: 3.98
  cpus: 16
  databaseBackend: sqlite
  distribution:
    codename: Holographic
    distribution: bazzite
    variant: bazzite
    version: "40"
  eventLogger: journald
  freeLocks: 1975
  hostname: bazzite
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
  kernel: 6.9.12-205.fsync.fc40.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree:<PHONE_NUMBER>
  memTotal:<PHONE_NUMBER>8
  networkBackend: netavark
  networkBackendInfo:
    backend: netavark
    dns:
      package: aardvark-dns-1.12.2-2.fc40.x86_64
      path: /usr/libexec/podman/aardvark-dns
      version: aardvark-dns 1.12.2
    package: netavark-1.12.2-1.fc40.x86_64
    path: /usr/libexec/podman/netavark
    version: netavark 1.12.2
  ociRuntime:
    name: crun
    package: crun-1.15-1.fc40.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.15
      commit: e6eacaf4034e84185fd8780ac9262bbf57082278
      rundir: /run/user/1000/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
  os: linux
  pasta:
    executable: /usr/bin/pasta
    package: passt-0^20240906.g6b38f07-1.fc40.x86_64
    version: |
      pasta 0^20240906.g6b38f07-1.fc40.x86_64
      Copyright Red Hat
      GNU General Public License, version 2 or later
        <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law.
  remoteSocket:
    exists: true
    path: /run/user/1000/podman/podman.sock
  rootlessNetworkCmd: pasta
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.2-2.fc40.x86_64
    version: |-
      slirp4netns version 1.2.2
      commit: 0ee2d87523e906518d34a6b423271e4826f71faf
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 4
      libseccomp: 2.5.5
  swapFree:<PHONE_NUMBER>
  swapTotal:<PHONE_NUMBER>
  uptime: 45h 32m 6.00s (Approximately 1.88 days)
  variant: ""
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
store:
  configFile: /var/home/nathaniel/.config/containers/storage.conf
  containerStore:
    number: 4
    paused: 0
    running: 4
    stopped: 0
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /var/home/nathaniel/.local/share/containers/storage
  graphRootAllocated:<PHONE_NUMBER>904
  graphRootUsed:<PHONE_NUMBER>28
  graphStatus:
    Backing Filesystem: btrfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Supports shifting: "false"
    Supports volatile: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 16
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /var/home/nathaniel/.local/share/containers/storage/volumes
version:
  APIVersion: 5.2.2
  Built:<PHONE_NUMBER>
  BuiltTime: Tue Aug 20 18:00:00 2024
  GitCommit: ""
  GoVersion: go1.22.6
  Os: linux
  OsArch: linux/amd64
  Version: 5.2.2

⬢ [Speedylemon] ❯ /usr/bin/podman version
Client:       Podman Engine
Version:      5.2.2
API Version:  5.2.2
Go Version:   go1.22.6
Built:        Tue Aug 20 18:00:00 2024
OS/Arch:      linux/amd64

I just tried re-installing rust into the default location instead of /opt ($HOME/.cargo and $HOME/.rustup) and the build worked fine. I have a feeling that either I needed other environment variables set to make /opt/rust work, or there's something that cross expects to be in $HOME that doesn't work with custom installation locations

interesting, there shouldn't be anything like that, all paths are grabbed from rustup in path

I wonder if maybe I just didn't set enough environment variables for moving rust into /opt/rust?
Here are the variables I set (fish shell):
if test -d /opt/rust
    set -gx CARGO_HOME /opt/rust/cargo
    set -gx RUSTUP_HOME /opt/rust/rustup
    set -gx XARGO_HOME /opt/rust/xargo
    source "/opt/rust/cargo/env.fish"
end


Create Release variables

Is there a way to pass variables to az pipelines release create? I expected something similar to how you can pass variables to az pipelines run --variables Variable1=Value1

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

ID: f912b9b3-f27c-deb7-54c1-8e3f477ed26f
Version Independent ID: fb24966a-f6fb-1828-2e0e-4374ae1df3d9
Content: az pipelines release
Content Source: latest/docs-ref-autogen/ext/azure-devops/pipelines/release.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

I'm having trouble discovering what to use for --artifact-metadata-list. The descriptions on this page seem vague. It would be really helpful to have some examples, or some way to learn how to use this parameter to specify which pipeline run output I want to create a release for.

pipelines

Commented on this at https://github.com/Azure/azure-cli-extensions/issues/1632#issuecomment-751665071 with the urgent needs one has at this level - i guess the comment should have belonged here, depending on the usage.
Are there any plans or informations on how this is supposed to be done?

Is it possible utilizing --query for this purpose as a workaround for the time being?

@bvandre Currently in azure cli service we don't have any way to pass variables as we checked in az pipelines release create API we did not found the information related to variables.
Thanks,
Anjali


Secure Boot can not used (IDFGH-4040)

Environment

Development Kit: none
Module or chip used: ESP32-WROOM-3D
IDF version : ESP-IDF v4.1
Build System: idf.py
Compiler version : (crosstool-NG esp-2020r2) 8.2.0
Operating System: windows10
Using an IDE?: no，just idf
Power Supply: USB

Problem Description
According to https://docs.espressif.com/projects/esp-idf/en/v4.1/security/secure-boot-v1.html#keys

open “Secure Boot Configuration”

change offset partition table to 0x9000

generate a new signing key by running the following command:
espsecure.py generate_signing_key secure_boot_signing_key.pem
like this

-----BEGIN EC PRIVATE KEY-----
MHcCAQEEIOKPC6iYY1JNJsQuW/PgED1oExu/Q/PC5yq3MIFfXDhvoAoGCCqGSM49
AwEHoUQDQgAEoXIYmV5NGzFauQ9SOTVT8w36j5kPyH7ptZB6N5alqhgXBE84p/dd
y57TgJ+LsLqTbVJLQtiSTsSnZRLQmmXRgA==
-----END EC PRIVATE KEY-----

falsh bootloader by running following commands

idf.py bootloader
idf.py -p com3  bootloader-flash

everything look like fine
[2/4] Performing build step for 'bootloader'
ninja: no work to do.
Executing action: bootloader-flash
Running esptool.py in directory d:\esp32_tool\down\esp-idf\test\hello_world\build
Executing "C:\Users\yudukai\.espressif\python_env\idf4.1_py3.7_env\Scripts\python.exe D:\ESP32_TOOL\down\esp-idf\components/esptool_py/esptool/esptool.py -p com3 -b 460800 --before default_reset --after no_reset --chip esp32 write_flash @flash_bootloader_args"...
esptool.py -p com3 -b 460800 --before default_reset --after no_reset --chip esp32 write_flash --flash_mode dio --flash_size detect --flash_freq 80m 0x1000 bootloader/bootloader.bin
esptool.py v2.9-dev
Serial port com3
Connecting........_____....._____....._
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: a4:cf:12:64:5f:7c
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 34784 bytes to 21764...
Wrote 34784 bytes (21764 compressed) at 0x00001000 in 0.5 seconds (effective 560.3 kbit/s)...
Hash of data verified.

Leaving...
Staying in bootloader.
Done

falsh by the running following command

idf.py -p com3 all flash monitor
or
idf.py -p com3 flash monitor
but it not working
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:4
load:0x3fff0034,len:9780
load:0x40078000,len:20328
load:0x40080400,len:4568
0x40080400: _init at ??:?

i try check efuse by the running following command

espefuse.py -p com3 summary
I found that bootLoader didn't seem to be working
FLASH_CRYPT_CNT        Flash encryption mode counter                     = 0 R/W (0x0)
UART_DOWNLOAD_DIS      Disable UART download mode (ESP32 rev3 only)      = 0 R/W (0x0)
FLASH_CRYPT_CONFIG     Flash encryption config (key tweak bits)          = 0 R/W (0x0)
CONSOLE_DEBUG_DISABLE  Disable ROM BASIC interpreter fallback            = 1 R/W (0x1)
ABS_DONE_0             secure boot enabled for bootloader                = 0 R/W (0x0)
ABS_DONE_1             secure boot abstract 1 locked                     = 0 R/W (0x0)
JTAG_DISABLE           Disable JTAG                                      = 0 R/W (0x0)
DISABLE_DL_ENCRYPT     Disable flash encryption in UART bootloader       = 0 R/W (0x0)
DISABLE_DL_DECRYPT     Disable flash decryption in UART bootloader       = 0 R/W (0x0)
DISABLE_DL_CACHE       Disable flash cache in UART bootloader            = 0 R/W (0x0)
BLK1                   Flash encryption key
  = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W
BLK2                   Secure boot key
  = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W
BLK3                   Variable Block 3
  = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W

I couldn't find where it was wrong. Can you help me?
Thank you so much.

If the bootloader is 34784 bytes and starts at 0x1000 it will end at 0x97e0 so you can't put the partition table at 0x9000

@poisonousfish @negativekelvin
I was worried about a similar error.
The solution was to change the offset partition table to 0xA000.
Thank you!

Closing as this seems to be resolved by moving the partition table.
More information about this can be found in the Secure Boot docs:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/security/secure-boot-v1.html#bootloader-size


Support default arguments, keyword arguments, varargs, kwargs

This adds support for:

Default arguments: def f(x=1, y=2)
Varargs: def f(*args)
Keyword-only arguments: def f(*, x, y)
Kwargs: def f(**kwargs)
Calling with varargs: f(*args, *more_args)
Calling with keyword arguments: f(x=1, y=2)
Calling with kwargs: f(**kwargs, **more_kwargs)
Any combination of these features that's valid in Python

There are mild limitations on these features:

*args are resolved statically so they must always be a tuple
f(a, b), f(x=a, y=b) and f(y=b, x=a) are all considered different call signatures by the inferrer, and if the monomorphizer cannot statically resolve f, it will not be able to compile the code if more than one signature is found

Nonetheless, this PR should support 99% of use cases.
This PR is based on #242

I'm not super happy about hijacking return_ either, but it's not necessarily terrible: it's a way to keep extra nodes reachable for cloning/managing purposes, and the inferrer will raise an error if we ever forget to get rid of them. Possibly a different "primitive" than P.return_ could be used.


ddmmyy regression in 1.0.0 version

in 0.7.6 all works:
>>> from dateparser import parse
>>> parse("100120")
datetime.datetime(2020, 10, 1, 0, 0)

however in 1.0.0 it's none

Hi @manycoding,
This breaking change is documented in the changelog (https://github.com/scrapinghub/dateparser/releases/tag/v1.0.0). The no-spaces-time parser was disabled by default because it was generating false positives and a lot of results weren't intuitive.
You can recover the old behavior by using the PARSERS setting:
# dateparser 1.0.0
>>> from dateparser import parse
>>> from dateparser_data.settings import default_parsers
>>> parse("100120",  settings={'PARSERS': default_parsers + ['no-spaces-time']})
datetime.datetime(2020, 10, 1, 0, 0)

I will close this issue, feel free to comment or reopen it if you have any other doubt.
Cheers!


refactored session lifecycle in pool

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report

Merging #332 (9d7433b) into master (a1ff0c1) will decrease coverage by 15.00%.
The diff coverage is 84.61%.

:exclamation: Current head 9d7433b differs from pull request most recent head e2e332d. Consider uploading reports for the commit e2e332d to get more accurate results

@@             Coverage Diff             @@
##           master     #332       +/-   ##
===========================================
- Coverage   62.69%   47.68%   -15.01%
===========================================
  Files         182      182
  Lines       20222    20200       -22
===========================================
- Hits        12678     9633     -3045
- Misses       6812     9810     +2998
- Partials      732      757       +25

Flag
Coverage Δ

1.14.x
35.55% <84.61%> (-26.82%)
:arrow_down:

1.18.x
45.68% <84.61%> (-16.69%)
:arrow_down:

1.19.x
45.80% <84.61%> (-16.82%)
:arrow_down:

connection
?

discovery
?

e2e
47.68% <84.61%> (-0.92%)
:arrow_down:

macOS-latest
?

ratelimiter
11.51% <0.00%> (+0.01%)
:arrow_up:

scripting
12.63% <0.00%> (+0.05%)
:arrow_up:

table
34.21% <84.61%> (-0.24%)
:arrow_down:

topic
25.16% <82.69%> (+0.26%)
:arrow_up:

ubuntu-latest
47.68% <84.61%> (-14.95%)
:arrow_down:

unit
?

windows-latest
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

table/table.go
69.17% <ø> (ø)

internal/table/client.go
61.17% <78.94%> (-20.91%)
:arrow_down:

internal/table/session.go
67.33% <100.00%> (-10.14%)
:arrow_down:

trace/table_gtrace.go
64.55% <100.00%> (+0.35%)
:arrow_up:

sugar/dsn.go
0.00% <0.00%> (-100.00%)
:arrow_down:

sugar/params.go
0.00% <0.00%> (-100.00%)
:arrow_down:

internal/scheme/options.go
0.00% <0.00%> (-100.00%)
:arrow_down:

balancers/config.go
0.00% <0.00%> (-95.09%)
:arrow_down:

retry/retryable_error.go
0.00% <0.00%> (-83.34%)
:arrow_down:

table/types/types.go
10.81% <0.00%> (-78.38%)
:arrow_down:

... and 56 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


MINOR: prefix topics if internal config is set

In order to move a topology to another runtime without having to copy over the internal topics it would be good to have the option to not prefix the internal topics with the application ID. So this change will introduce a new config that if set will be the internal topic prefix
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ableegoldman This should make it so we can have topics prefixed with whatever is needed

Though this comment is not for AK, I'd have to raise to our attention: in ksql we have hard-coded rules to detect internal topics to be cleaned when terminating a query, which is like this today:
  private static boolean isInternalTopic(final String topicName, final String applicationId) {
    final boolean prefixMatches = topicName.startsWith(applicationId + "-");
    final boolean suffixMatches = topicName.endsWith(KsqlConstants.STREAMS_CHANGELOG_TOPIC_SUFFIX)
        || topicName.endsWith(KsqlConstants.STREAMS_REPARTITION_TOPIC_SUFFIX)
        || topicName.matches(KsqlConstants.STREAMS_JOIN_REGISTRATION_TOPIC_PATTERN)
        || topicName.matches(KsqlConstants.STREAMS_JOIN_RESPONSE_TOPIC_PATTERN);
    return prefixMatches && suffixMatches;
  }

With this change we have to remember updating this function otherwise the cleanup logic would break.

@guozhangwang yes that is a good point. When we go to use this we will have to set the config and we can updated the clean up logic then

LGTM! Re-triggering the jenkins tests.

@wcarlson5 could you double check if the failed tests are relevant?

@guozhangwang Yeah I needed update a few tests. It should be good now.


Spawn error after packaging

Hi,
Just after compilation with electron-builder,
I get this error in my app from ffprobe
Uncaught Error: spawn C:\Users\Anymord\AppData\Local\Temp\nsuFBDD.tmp\app\resources\app.asar\node_modules\ffprobe-static\bin\win32\x64\ffprobe.exe ENOENT
    at exports._errnoException (util.js:1022)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193)
    at onErrorNT (internal/child_process.js:359)
    at _combinedTickCallback (internal/process/next_tick.js:74)
    at process._tickCallback (internal/process/next_tick.js:98)

Here is my setup :
From my package.json
  "dependencies": {
   ...
    "ffprobe": "^1.1.0",
    "ffprobe-static": "^2.0.0",
...
}

In a script called by index.html
const ffprobe = require('ffprobe')
const ffprobeStatic = require('ffprobe-static')

and the call
    ffprobe(item.filePath, {
      path: ffprobeStatic.path
    }, function (err, info) {

What did I missed ?
Thanks for your support !

Hmm just read the log more carefully, it seems the problem is more with ffprobe-static...


Multiple sensors

This is a great initiative - thanks!
It would be great if there can be multiple entries (i.e. multiple sensors) so that different areas can be responded to differently. An example use case might be to flash lights for one area but only have a silent notification for a different area.

@mbrevda please let me know if you need help with your specific configuration, and I'll be happy to help.

yeah, I guess it's possible that way, too. Thanks and thank you again for making this!


Support SonarQube 7.9 LTS

Now that the new SonarQube LTS version is out (https://www.sonarqube.org/sonarqube-7-9-lts/), it would be nice to support it. I haven't tried yet to run it on this version, but according to the release notes at https://github.com/Cognifide/AEM-Rules-for-SonarQube/releases even the newest 1.0RC2 is only compatible with SonarQube up to version 7.7.

Hi @kwin,
I think it should be compatible, but we'll make sure. We were kind of waiting for this to happen to release the full version into the update center.
Thanks!

@kwin @chutch were you successful with getting this working?

Hi! @chutch @kwin @josephrignanese v1.0-RC2 uses API that is compatible with 7.9 version. I've test it with following Dockerfile:
FROM sonarqube:7.9-community AS aemrulesqube81

RUN curl -Lk -o $SONARQUBE_HOME/extensions/plugins/aemrules-1.0-RC2.jar https://github.com/Cognifide/AEM-Rules-for-SonarQube/releases/download/v1.0-RC2/aemrules-1.0-RC2.jar

Version 1.1 has been released but there's a little blunder that needs fixing before it can be downloaded from the Marketplace https://github.com/SonarSource/sonar-update-center-properties/pull/117
I'm on it.


Global location for maid file

If there is not a maidfile.md in the current directory then look in the user's root for a file something like .maidfile.md

that's neat but I'm afraid that it will cause confusion.

Potentially, but it also means I could create a set of scripts that I could use from anywhere in my system.

what about something like maid global build which will run build task from the maidfile in user's home dir 🤔

This is a pretty common convention.  Hashicorp's vagrant and docker-compose will scan down each of the parent directories of the current directory to find its manifest (Vagrantfile and docker-compose.yml respectively), presumably halting at the user's home directory.

I like @gthole idea even better. Just look up a directory until you find a maid file or give up at the home directory.

I'm against maid global, try to not pollute tasks namespace as much as possible, and also this will allow calling multiple commands/tasks in series/parallel (btw would be flags) - like gulp.

Even best would be to drop support for other files and support only .?maidfile.md from cwd to home. I like that it allows to use README.md, but it may complicate the things exactly because it is common file.
Actually i'm playing with some implementations and may pr if i've done something.

Implemented in #37. If merged you add ~/.maidfile.md and just start using maid without passing any flags.


Feature request: Line breaks after separators in code formatting

Option to insert a line break after separators in PowerShell code formatting:
I am suggesting an option for the PowerShell code formatter that allows to insert line breaks after each separator. For example, the following code:
$foo=9;$bar=10;

currently becomes formatted as follows with the default settings:
$foo = 9; $bar = 10;

Enabling line breaks after separators should produce the following result instead:
$foo = 9;
$bar = 10;

Sounds good to me, I think we'd accept a PR for that

I concur, a config option seems preferable. I am not very familiar with either VSCode add-ons or the PSScriptAnalyzer code base, so I don't want to say with a lot of confidence that I'll implement this - but I will certainly pull the repo and try. Still, if anyone considers this a trivial code change ... don't hesitate :-).

This should probably include the job separator & as well ?
(not a great example)
$foo=9&$bar=10&

Looks like these are presently missed by the formatter:
$foo = 9&$bar = 10&


Possibility to read the input value from a fillable()

Being able to fill and then read the value from an input is a scenario I've met several times during testing and it would be really great if there was a way to be able to do this with just a fillable() (or possibly named something else).
The built-in .fillIn() and .value for components are great but limits the fluid-ness of your code.
Example:
const page = create({
  name: {
    scope: 'input',
  },
  submit: clickable('button')
});

// calling `fillIn()` on `name` returns the context of `name` so there is no
// access to `.submit()`. Therefor you have to write the code on two lines:
page.visit().name.fillIn('Christoffer');
page.submit();

// read the value
page.name.value;

An existing alternative would be to define a fillable() along with a value() like this:
const page = create({
  name: fillable('input'),
  nameValue: value('input'),
  submit: clickable('button')
});

// calling `name()` returns the root context and you can easily call `.submit()`:
page.visit().name('Christoffer').submit();

// read the value
page.nameValue;

This works but seems a bit redundant that you have to specify the same selector twice.
Mimicking jQuery's .val() it would be nice if a single fillable() would allow you to fill the value by passing a parameter and read the value by omitting parameters.
Example:
const page = create({
  name: fillable('input'),
  submit: clickable('button')
});

// calling `name()` returns the root context and you can easily call `.submit()`:
page.visit().name('Christoffer').submit();

// read the value
page.name();

Another example proposed by @san650 in the Ember Slack is that ember-cli-page-object automatically defines an accompanying xyzValue property for reading the value (just like the second example in this issue, but you wouldn't have to define it manually).

What if value were one of the “default attributes” of a component? Then you can fillIn and check the value. The addition of these default attributes is very useful to me and I think this would be even better.

hmm never mind, it’s actually already present! 😬
Maybe I’ll make a PR to add it to the documentation…

It would be great if this feature would be added. Something like:
address: fillable('input[data-test-input=address]'),

When inserting input:
component.render(hbs`{{my-component model=user}}`);
component.address('Street 1');

assert.equal(user.address, 'Street 1');

When reading:
component.render(hbs`{{my-component model=user}}`);
assert.equal(component.address.value(), user.address);

So basically address() would behave as the result of the fillable functions, while address would return a component scoped on the same scope. Using this component, the default attributes as specified in the documentation could be used.

@denniss17 currently fillIn and value are both available for each page object component, see "Default Attributes" section of the "Components Doc".
This allows us just to declare an address field:
  const form = create({
    address: {
      scope: 'input[data-test-input=address]'
    }
  })

and use it in your test in the following form:
  await form.address.fillIn('Street 1');
  assert.equal(form.address.value, 'Street 1');

Does it work for you?


Dataset Size Mismatch Issue Being Caused

https://github.com/pytorch/fairseq/blob/98ebe4f1ada75d006717d84f9d603519d8ff5579/fairseq/data/nested_dictionary_dataset.py#L63
Hey
I've been trying to replicate the code from https://github.com/machelreid/lewis using a custom dataset and it worked well for the first few steps then in one of the steps it throws an error from the referenced line saying mismatch in sizes and when I try to print out I see the sizes are different but I can't figure out what can cause this as the datasets have same length on manual inspection.
Also I tried to see what happens if I move the line https://github.com/pytorch/fairseq/blob/98ebe4f1ada75d006717d84f9d603519d8ff5579/fairseq/data/nested_dictionary_dataset.py#L53 inside the for loop the error vanishes from there but reappears at https://github.com/pytorch/fairseq/blob/98ebe4f1ada75d006717d84f9d603519d8ff5579/fairseq/data/sort_dataset.py#L18 and on printing I can see the lengths causing the assertion error are the same as the lengths causing the assertion error prior to changing the code in nested_dictionary_dataset.py
Also the assertion error happens presumably with the validation dataset as one of the values is 2x the size of the validation dataset while the other is the same size if that helps
Any clues I can follow?

The issue was caused by another typo


Kurdish translation

Add Kurdish translation with support for right-to-left text.
Here is the file with the translation provided by Pah:
translation to Kurdish.txt

add flag of Iraq


manual update setup

@pipposera : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@Justinha: I'm sorry - only the author of this article, @PatAltimore, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@pipposera : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@pipposera @Justinha  Changes to articles must be done in the azure-stack-docs-pr repo (private) rather than the azure-stack-docs repo (public) so that we can have validated builds and verify content updates on staging. You should have permissions to azure-stack-docs-pr. Closing this pull request so that you can make updates in the private repo. Thank you.

Tami,
This was completely unnecessary. I just saw this email and realized that the changed that I had submitted 2 weeks ago has not made it to the public documentation, resulting in customer escalations.
Filippo
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Tami<EMAIL_ADDRESS>Sent: Monday, November 25, 2019 8:20 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-stack-docs] manual update setup (#499)
@pipposerahttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpipposera&data=02|01||d2bf4e44f4b14376ced308d771c36c17|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637102956446448015&sdata=fntyNMMJxld2X2vTiqXLthKLLR4ma0zyzKjESmwIHlI%3D&reserved=0 @Justinhahttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJustinha&data=02|01||d2bf4e44f4b14376ced308d771c36c17|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637102956446458020&sdata=PKve2POA2pulomEPGRbsSQpa9lHP%2FQI5Qbr7ejg25s0%3D&reserved=0 Changes to articles must be done in the azure-stack-docs-pr repo (private) rather than the azure-stack-docs repo (public) so that we can have validated builds and verify content updates on staging. You should have permissions to azure-stack-docs-pr. Closing this pull request so that you can make updates in the private repo. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-stack-docs%2Fpull%2F499%3Femail_source%3Dnotifications%26email_token%3DAHM3TTXD6WYVTQDW3WHBXTLQVP3NXA5CNFSM4JQX5WM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFC6QUA%23issuecomment-558229584&data=02|01||d2bf4e44f4b14376ced308d771c36c17|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637102956446468031&sdata=Fkvy%2F%2Fjv1iZX9n6hg335J32tNmG5vxIsqJ7IXxKZW4c%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHM3TTVTIDUPWKUB3K4WNHTQVP3NXANCNFSM4JQX5WMQ&data=02|01||d2bf4e44f4b14376ced308d771c36c17|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637102956446478037&sdata=2MbpDgaGsNxicy0Ujlym9iwePCKzjNJ8ZxyNmevlcig%3D&reserved=0.


Support auth

Support HTTP authentication

Hi @Secretmapper does this fix using transmission with basic auth enabled? I remember we tried that with no success, that's why we changed ajax implementation to a XMLHttpRequest based one. See https://github.com/fcsonline/react-transmission/pull/47
Maybe I'm missing something... :confused:

@Secretmapper tried again and works like a charm! Thanks for your help

:+1: This was so tricky to debug - I was pulling my hair out on why it wouldn't work while we're doing seemingly the same thing as transmission's web ui, and it just turns out jquery has it enabled as a default option (and hence why it didn't show up on transmission's codebase).

It isn't jquery. The browser does this things for you with ajax or whatever http request. The problem was the new fetch way that you need to specify all the headers you want to send.


Add U+2252 and U+2253

#15

Thanks for the contribution!
Regarding the name, eq.dots.down and eq.dots.up would probably be more consistent with the other symbols (such as dots.down for U+22F1 ⋱ and dots.up for U+22F0 ⋰).

Additionally, ≑ could be eq.dots.


Defunctionalize %LazySeries{}

Overview
This PR is an experiment. I wanted to see how hard it would be to remove the callbacks in our lazy implementations. It turned out to be more work than I expected.
Example
The gist can be found in test/explorer/new_approach_test.exs. Here's the "mutate" test from that file:
df0 = DF.new(a: [1, 2, 3])

# Mutate inline
df1 = DF.mutate(df0, b: a + 3)

# Mutate by building a lazy series with functions
b = S.col("a") |> S.add(3)
df2 = DF.mutate_with(df0, b: b)

# Mutate by building a lazy series with a macro
b = Query.new(a + 3)
df3 = DF.mutate_with(df0, b: b)

for df <- [df1, df2, df3] do
  assert DF.to_columns(df, atom_keys: true) == %{a: [1, 2, 3], b: [4, 5, 6]}
end

The Good, the Bad, and the Ugly
The Good

It removes the need for callbacks, which can be inflexible and hard to debug:# Old
DF.filter_with(df, fn ldf -> S.greater(ldf["a"], 2) end)
# New
DF.filter_with(df, S.greater(S.col("a"), 2))

Now you can pass lazy-backed serires to functions for further manipulation like you do with Ecto queries.
No more unhygenic macros.

The Bad

You cannot know a lazy-backed series has valid dtypes until it's executed.
Explorer.Backend.LazySeries is now a "pseudo-backend", but it's not part of the Explorer.Series behaviour. It feels awkward.

The Ugly

:unknown dtype. :unknown dtype everywhere.
Massively, massively breaking.

Final Thoughts
This PR is covered in hacks and TODOs. There are a few types of tests that won't pass until I refactor some error-handling. And there are some conflicts with main.
But this PR is close enough that I wanted some more eyes on it. It's time to see if the idea has merit.

Personally, I consider this to be something more like dynamic in Ecto. I wouldn't promote it as the default way of building queries, rather as an alternative. In this case, I would say it is ok to request the dtype and have something like S.col("a", :string). Or even S.string("a") to make it a bit more convenient, so we always have the dtype available. Do you think these would be fair compromises?

I really like :dtype as an arg to col. Same with the S.dtype(name) API, didn't even think of that!
But having it be required might be cumbersome. For one, the macros would be awkward:
normalized = Query.new((a - mean(a)) / standard_deviation(a))
# vs.
normalized = Query.new((col("a", {:f, 64}) - mean(col("a", {:f, 64}))) / standard_deviation(col("a", {:f, 64})))
# or
a = S.col("a", {:f, 64})
normalized = Query.new((^a - mean(^a)) / standard_deviation(^a))

For another, I don't know how much it buys us. True, it prevents me from building a lazy-series in the first place:
# works
S.col("string_column") |> S.add(5)
# raises
S.col("string_column", dtype: :string) |> S.add(5)

But the bad column would never be executed because the first thing we'd do is validate the schema:
df = DF.new(string_column: ["a", "b", "c"])
bad_sum = S.col("string_column") |> S.add(5)
# fails dtype validation
DF.mutate(sum: bad_sum)

We should definitely still have that option. But the question is: is it required?

In my mind we would keep both modes. The S.col/2 would be a convenience that you reach for in certain cases only. because, even if the dtype was not required, S.col is not cleaner than Explorer.Query, given we can use operators, across, cond, and more in queries.

In my mind we would keep both modes.

Absolutely. The real benefit of the approach IMO is the return value of Explorer.Query.query/2. Before it returned an anonymous function. Now it returns a data structure that users can introspect\manipulate. It makes the Series functions properly "monadic" over eager/lazy backings.
The S.col aspect is a sorta side benefit. Since you're now working with lazy structures, you can also make them out of band instead of having to inline everything.

I may be missing something then.
We can make query not return a function and that should be a relatively small change.  The semantics are well defined internally, we just chose to not expose them.
To me, the big change in this PR is all about :unknown, and if we don't need to do go down that route, I would recommend separating these discussions.

No I don't think you're missing anything!
If any version of this PR is to go forward, it will have to be broken up into manageable pieces. Altering the return of Query.query is a great place to start since it's the core change that sets up the other stuff.
I think the S.col/1 discussion is worthwhile to have later. I've found it to be convenient to work with in Polars and potentially worth the tradeoff. But TBH, I don't think I'd want to even consider tackling it for real without a refactor of our dtype handling. Tacking on K.or(dtype == :unknown) 100's of times is not tenable :) And I think there are wins to be had there.
To clarify though: altering the return of Query.query is the most breaking aspect. No *_with verbs will work anymore since today they expect callbacks.

It should be easy to extend the _with callbacks to deal with both functions and direct arguments by using guards. So we should start there.


⚠ Bofrost.de has degraded performance

In a2445e1, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1117 ms

Resolved: Bofrost.de performance has improved in 5d65ed5.


Scan and parse identifier token

I think it would be handy if we introduce identifier before implementing statements.

@Lai-YT updated!


Align data model/dictionary descriptions and examples with new naming standards

On the data dictionaries page, prefixes have been kept for now since the @context with URIs is shown as well.
Closes #5

Added our page for controlled term naming standards from encarta (https://github.com/neurobagel/encarta/blob/main/docs/standards.md) like we discussed.


Change default semantic to not support anytime migration

Anytime migration is not in use by any production application.  Support requires a non-trivial amount of machinery in the runtime system and creates performance overhead.  Anytime migration should be an opt-in feature.  Either in something like CkOpts, or a subclass of CkArray, or some other mechanism by which it is explicitly chosen by applications that need it.

Spring cleaning of chare array broadcasts is a repercussion of this that causes overhead in memory usage: https://github.com/UIUC-PPL/charm/issues/2045

Note that applications that use AtSync based load balancing without +LBSyncResume or some other mechanism to ensure that all objects have migrated before resumption (to be pedantic, resumption is actually alright, the real issue is if an array broadcast is delivered before an object migrates) may break if anytime migration is disabled.


[BUILD] Push Tagged Image to DockerHub

PR Checklist

[ ] Create UnityCatalog DockerHub profile and add DockerHub secrets to Github for workflow (CC: @dennyglee)
[x] A description of the changes is added to the description of this PR.
[x] If there is a related issue, make sure it is linked to this PR.
[x] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added or modified a feature, documentation in docs is updated

Description of changes
This PR modifies the docker-build.yml Github Actions workflow to enable pushing a tagged docker image, eg. unitycatalog/unitycatalog:v0.2.0, to DockerHub as an official resource. See issue #617 for more details.
An example of the successfully completed workflow can be seen on my fork.
The workflow ran on a repush of the v0.2.0 git tag to my fork. The resulting tagged image can be seen on my personal DockerHub.
The v0.2.0 tag on my fork points to the latest commit of upstream/branch-0.2 with cherry-picked commits from #551 and this PR.
The workflow also implements caching for Docker builds on pull requests, using the buildcache tag on the registry.
Running this workflow successfully will require setting up an official UnityCatalog DockerHub account, and creating and adding the DOCKERHUB_USERNAME and DOCKERHUB_TOKEN secrets to this repository for use in the workflow.
See the screenshot below for an example the added secrets from my fork:

@dennyglee 👋 Follow up to push the tagged image to DockerHub.

So sorry for the delay, @tnightengale - since you have been working on the Docker so much, can I ask that I give you access to the DockerHub so you can upload and validate?

So sorry for the delay, @tnightengale - since you have been working on the Docker so much, can I ask that I give you access to the DockerHub so you can upload and validate?

Yes, that would work! Let's coordinate over slack.

For visibility: the next steps here are to apply for UC sponsorship from DockerHub, to ensure the official image is supported for unlimited pulls.

@tnightengale does that mean the image has been published to docker hub? I can't seem to find it.

@tnightengale does that mean the image has been published to docker hub? I can't seem to find it.

The image will not be pushed to a registry until this PR is merged. It adds the pipeline to push an image. We are waiting for approval from DockerHub for unlimited image pulls, before putting up the official image.


Generalize and speed up math gradients

Fixes #335.
Comment: the gradients of all the binary functions (+, -, /, *) will not work if the sparsity patterns of the gradients are different along their sample dimensions. This was the case also before this PR and I don't think it's trivial to fix it.

:books: Documentation preview :books:: https://equistore--342.org.readthedocs.build/en/342/

Comment: the gradients of all the binary functions (+, -, /, *) will not work if the sparsity patterns of the gradients are different along their sample dimensions. This was the case also before this PR and I don't think it's trivial to fix it.

It should not be too hard to fix: everything missing can be considered 0, so the output gradient sample is the union of the input gradient samples, and one can use Labels.union_and_mapping to get the union and where to write the values corresponding to both inputs. But we can leave this to a future PR.

This PR needs to have some tests, maybe something with custom gradients having different number of components?


When printing list of lists with single entry, cannot successfully select

Bug is also encountered when selecting last list in list, implying that this is related to that, rather than just a list of a single entry issue.


Added mpd client options and updated example config

Simply added randomization and looping and added examples in the config.
Now onto some harder harder additions :D

This is a good feature to implement, however, I think it should not be a config option that is applied on startup. That would result in issues such as this:

User has not configured shuffle in the miniplayer config
User sets MPD to shuffle
User opens miniplayer
Shuffle is turned off since miniplayer turns off shuffle by default

I think this would be better implemented as keybinds (and nothing new in the config). That would result in more expected behaviour. If you want to create a new pull request with these changes, please go ahead! :frog:


Solve stochastic failure

I found a potential stochastic failure in the metadata template tests. It is solved by enforcing some sorting on the way the columns are inserted in the database, so it is easy testable.
I would appreciate a fast review on this one as it can potentially impact any future PR.

Coverage remained the same at 79.12% when pulling e0b269827d9e2774b39b4bd362068e3d6bb423b4 on josenavas:solve-stochastic-failure into 2199bdd6dc9d9b957de4c55aa34f59a603d73ef5 on biocore:master.

ping @biocore/qiita-dev

:+1:

:+1: just one minor comment.

Coverage decreased (-0.02%) to 79.1% when pulling 6270a6d9607982c70a8b10eb48c7ea45be49ecb8 on josenavas:solve-stochastic-failure into 2199bdd6dc9d9b957de4c55aa34f59a603d73ef5 on biocore:master.


Bottom spacing

Pull Request: Fix Layout and Responsiveness
Description
This pull request addresses several minor issues and improvements in the project. The changes made include:

Removed an extra blank space at the bottom of the contact page for improved aesthetics.
Enhanced the layout and responsiveness of the page to provide a better user experience.
Added a missing backslash "/" to a link in the index.html page for proper functionality.

These improvements contribute to the overall quality and usability of the project.
Changes Made

Removed blank space at the bottom of the contact page.
Enhanced layout and responsiveness of the page.
Added missing backslash "/" to a link in index.html.

Screenshots

Testing Done

Tested the page on different screen sizes: 414px, 750px, 820px, 1366px, and 2444px

Checklist

[x] I have read and followed the project's contributing guidelines.
[x] My code follows the project's coding standards.
[x] I have tested my changes and they do not introduce any new issues.
[x] I have provided a clear and concise description of the changes.

Related Issues
[Footer & Contact page layout issues] #314
Additional Notes
To enhance the project's visual appeal and user experience, I recommend wrapping the content of each page within separate div containers, maintaining consistent height and width properties. This adjustment will unify the design and layout across pages, facilitating ease of maintenance and future development. A uniform layout structure also bolsters responsiveness and adaptability for different devices. I'm eager to implement this for your review, streamlining the project's aesthetics and user-friendliness. Your consideration is greatly appreciated.
Reviewers
Thank you for considering this pull request. I look forward to your feedback and the opportunity to contribute to the project.

It's great to see your contribution to the project. Your attention to detail and the improvements you've made are much appreciated. Here's a suitable reply to the pull request:
Reply to Pull Request: Fix Layout and Responsiveness
Thank you for your pull request! We appreciate your effort in addressing these layout and responsiveness issues. Your contributions have certainly improved the overall quality and usability of the project.
The changes you've made, such as removing the extra blank space on the contact page, enhancing the layout and responsiveness, and fixing the link issue, all seem beneficial for the project.
Your comprehensive testing on various screen sizes and your adherence to our checklist and contributing guidelines are commendable. This ensures that your changes are reliable and do not introduce new issues.
Your additional suggestion to wrap the content of each page within separate div containers to maintain a consistent layout is a great idea. It will enhance the project's visual appeal, user experience, and maintainability. We appreciate your eagerness to implement this and look forward to reviewing it in a future pull request.
Our team will review your changes and provide feedback soon. Thank you for your patience and for considering this project for your contributions. I want you to know that your effort to enhance the project's aesthetics and user-friendliness is greatly appreciated.
We look forward to collaborating with you!


added include for static embree library

Hello,
This pull request adds a small section to ospray_macros.cmake to properly include Embree as a static library if it is built statically. This relies on Embree pull request 227.
This has been verified using OSPRay 1.7.x build.

Why does this need to be predicated on whether embree is static or not? Is just using the embree imported target not good enough?

@mathstuf the ospray cmake at the time of this pull request hardcoded libembree.so even when embree was built statically. I understand that the cmake config for ospray has changed considerably in 1.8.x so it might work properly now. My embree static lib fixes have been merged into the embree tree for a while, so the latest there will properly expose the static library for testing with ospray.

This is not needed any longer: OSPRay and Embree moved to modern CMake with targets.


------------ Environment ------------
Colossal-AI version: 0.2.8
PyTorch version: 1.12.1
System CUDA version: 11.3
CUDA version required by PyTorch: 11.3

Sorry for getting to your questions late. May I know why you are setting nproc_per_node=1 when you have multiple nodes on the machine and set the strategy to be ddp?

Thanks for reporting. #4023 Contains this now.


koordlet: reduce unnecessary call of Err() for better performance

func AddSeries is called frequently, it's within multiple loops.
it.Err() will take a lot of time when the data is huge, we'd better reduce calling it.

/lgtm
PTAL @zwzhang0107


Question regarding using 8 bit gptq quantized models

I built the quantized weights using 8 bit GPTQ ( python llama.py ./tmp/llama/7B/ c4 --wbits 8 --true-sequential --groupsize 128 --save_safetensors ./llama-7b-4bit-gs128.safetensors )
Now, in order to build engines from checkpoints, I need to use the tags --use_weight_only --weight_only_precision XXXX. I am required to choose from 'int8', 'int4', 'int4_awq', 'int4_gptq' . Can you let me know if int8 is the right option to use ? What is the difference between using int4 int4_gptq int4_awq ? Does the absence of int8_gptq mean that using 8 bit gptq will lead to poor results ?

For int8, we only support pure int8 only because the accuracy is good enough in our experiement. You couldn't run int8 gptq model by int8 directly.
int4, int4_gptq and int4_awq are different quantization methods.


Mitm.it DOWN

Problem Description
A clear and concise description of what the bug is.
Trying to install certificates on iOS, but when you go to http://mitm.it/ it returns: "If you can see this, traffic is not passing through mitmproxy."
:(
Steps to reproduce the behavior:

Go to http://mitm.it/

System Information
Paste the output of "mitmproxy --version" here.
If you can see this, traffic is not passing through mitmproxy.

As the error message says: You have not configured your client correctly, the traffic is not passing through mitmproxy.


Update service clients to take url instead of host and port, drop method names from ServiceException

Current coverage is 59.81%

Merging #99 into develop will increase coverage by +0.05% as of 36b2b6d

@@            develop     #99   diff @@
=======================================
  Files            15      15
  Stmts          2324    2322     -2
  Branches          0       0
  Methods           0       0
=======================================
  Hit            1389    1389
  Partial           0       0
+ Missed          935     933     -2

Review entire Coverage Diff as of 36b2b6d

Powered by Codecov. Updated on successful CI builds.


Refactor Pokedex directories, files

flow-*.yml to flows
app.py updated
README.md updated

Tested locally and confirmed working


Regression notification implemented.

Notification generated for following cases:

If number of failed tests increased. (Even when previous build was red).
If the failed tests are different than previous build (Even when the number of failed tests are same as last build).

Will not notify for

For failure that are same as previous build.

In short, will notify if the current build is worst than the previous build.

@prashant-ee can you rebase instead of merge?

Thanks for accepting the changes. Happy to contribute.


feat: add react_rearch package for react support

Port to Dart React

Sure, I will try to do all of that :)

Could you add a basic test or two for this RearchComponent? No need for a ton of tests, just a couple to test functionality (perhaps a counter).

I never do tests. Can you give me an idea of how can I do a test here? Manually create a Bootstrapper and a Component and simulate his lifecycle?

Could you add a basic test or two for this RearchComponent? No need for a ton of tests, just a couple to test functionality (perhaps a counter).

I never do tests. Can you give me an idea of how can I do a test here? Manually create a Bootstrapper and a Component and simulate his lifecycle?

Yea, things like that. Maybe one bootstrapper and two counter components. One uses a capsule that has a use.data counter, the other is a component that registers use.data directly.
For bonus points, you can also make a component that tracks how many times it’s built via use.data. That’d be good to verify as well

Per other conversations, I believe this can be closed as a "something similar may come later"


Use of unresolved identifier 'JSON'

Hey i'm in trouble installing SwiftJSON in my project.
I'm using cocoapods 0.36 and xcode 6.2, deploy target >= 8.0
I'm using Alamofire and when I i'm trying to parse the json with this piece of code:
Alamofire.request(.GET, "http://localhost:3000/products")
        .responseJSON { (req, res, json, error) in
            var json = JSON(json!)
    }

Xcode is showing the next error:
 Use of unresolved identifier 'JSON'

Why? Thanks!

Please try to use following constructor of JSON class:
public init(data:NSData, options opt: NSJSONReadingOptions = .AllowFragments, error: NSErrorPointer = nil)

i already have this constructor class

try import SwiftyJSON at the top of the file where you are using JSON.

@pekpon , I had the same issue. To resolve this just import SwiftyJSON at the top of your file in which you are using it

Thanks to all! ;)


Add UI for broken link check reports

Include the Link Checker button on the Manuals show page
Include suggested fix and summary of link problems with the broken links

This leads on from https://github.com/alphagov/manuals-publisher/pull/1230

@nickcolley I've stripped out the javascript for now as you said it wasn't really necessary in this PR, it was pulled from the same functionality in Whitehall so some of it might return in a later PR but is not required just yet


Remove/Update talks about RTD page

I think this page should be remove or updated:
http://docs.readthedocs.io/en/latest/talks.html
From my understand it's too poor and doesn't communicate anything. It doesn't have links to the talks or something like that. So, if it's too time consuming to keep it updated, I would remove it.

It looks like the purpose of the page isn't to be a comprehensive list of talks, but:

Note
This page is mainly just for showing a demo of updating docs, during a talk.

However, it hasn't been used that way in a while, so I think it could be removed now.

Ha, good point!
As you can image... I didn't read the note :P

👍 on removing. We can do live updates somewhere else.


Recommended Campaign fields to rename

Not crucial, but could be renamed for the API and then updated later to rename the actual fields in the app and maybe DB. Also trying to eliminate variables that start with is_; typically they are equal to boolean values, and naming the variable without the is_ works just fine.

active_hours ---> time_commitment
call_to_action ---> tagline (already renamed in API and app templates but not the field)
is_dark_image ---> dark_background
is_staff_pick ---> staff_pick

Already being applied in the API, but not updated in database... not crucial though so closing for now.


typo: paramter -> parameter

Hi, @nschonni the specs files are generated from our source code so we don't accept fixes to them as they would be overwritten.
However, I checked the typos you pointed out and found that some are still present even in the newer versions, I will be fixing the typos from our side so the generated specs do not have these typos. Thanks!


[KOGITO-9263] Add the new resources to workflow CR

Description of the change:
In this PR we introduce a new way to specify workflow resources.
In the CRD, there's a new Resources attribute where one can map a local ConfigMap to the given workflow:
apiVersion: sw.kogito.kie.org/v1alpha08
kind: KogitoServerlessWorkflow
metadata:
  name: serverless-workflow-service-calls-quarkus
  annotations:
    sw.kogito.kie.org/description: Serverless Workflow Service calls example on k8s!
    sw.kogito.kie.org/version: 0.0.1
    sw.kogito.kie.org/profile: dev
spec:
    flow:
       -
    resources:
      - configMaps:
         - configMap:
                name: openapi-configmap
            workflowPath: specs

The configMaps holds all these references. I decided to go this way 'cause in the future we can have other external sources such as Secrets or Volumes.
In devmode, these files can change as the developer/tooling see fit while tailoring the workflow. For builds supported by the platform, these files are mounted in the build context and added to the final immutable image as a local file system resource.
In the worklflowproj module, we are generating the ConfigMaps grouped by path. By default, the path is specs. So any file added via AddResource will be on the same CM. One can use AddResourceAt instead to group the file in a different CM. See the test case.
Motivation for the change:
User Experience. See https://issues.redhat.com/browse/KOGITO-9263
Checklist

[x] Add or Modify a unit test for your change
[x] Have you verified that tall the tests are passing?
[x] Testing on a cluster the devmode and ocp BC modes

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

Tested in my local with both simple and complete project (service)  ! Thanks Zanini!

Merged duo to the time we have. @radtriste if you spot anything, let me know.


Document the Editorial Board in this repo

PEP 732 – The Python Documentation Editorial Board was accepted last month, which formed a Documentation Editorial Board to replace the old Documentation Working Group.
Let's update this repo's docs to reflect this.

[ ] https://github.com/python/docs-community/blob/main/README.md -> PR https://github.com/python/docs-community/pull/99
[ ] https://docs-community.readthedocs.io/en/latest/workgroup/index.html

Please could the EB take care of updating https://docs-community.readthedocs.io/en/latest/workgroup/index.html?
There's lots of stuff there about (old WG) practices which the new board is best placed to update. I expect a lot can be deleted and/or replaced with a link to the PEP.

@python/editorial-board @hugovk I will take care of removing the old content and create a page for the EB.


NHL Game Recaps Not Working For 2023-2024 Season

The schedule is populating correctly but the game recaps and extended highlights links never show up for the 2023-2024 NHL season.

Hey, I had noticed but did not have time to work on it. The NHL changed their API for video content.
I just made an update, it works at the moment but I'm not sure if they use rotating tokens or something to fetch videos. Keep me posted if the site breaks again. I don't check it every day.

It broke already, I will need to do more research


Fix some small problems in the live upgrade procedure

This is to prepare for the upcoming nydusd live upgrade function.

Codecov Report
Base: 27.99% // Head: 28.03% // Increases project coverage by +0.03% :tada:

Coverage data is based on head (c1971c3) compared to base (63c4a14).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #385      +/-   ##
==========================================
+ Coverage   27.99%   28.03%   +0.03%
==========================================
  Files          40       40
  Lines        4086     4081       -5
==========================================
  Hits         1144     1144
+ Misses       2803     2798       -5
  Partials      139      139

Impacted Files
Coverage Δ

pkg/daemon/daemon.go
0.00% <0.00%> (ø)

pkg/manager/daemon_adaptor.go
0.00% <0.00%> (ø)

pkg/manager/manager.go
18.53% <0.00%> (+0.37%)
:arrow_up:

pkg/system/system.go
5.90% <0.00%> (-0.32%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


How to convert a Node.js Notebooks to  a different format ??

From the command line,  a Jupyter notebook can be converted to a different format using the following command:
$ jupyter nbconvert --to <output format> <input notebook>
Is the same possible with Node.js Notebooks??

Unfortunately no. You could

Create a notebook with the extension *.ipynb and use the same extension to run code using the same kernel in vscode.
& then convert the ipynb using jupyter.

Hope this helps, let me know if it doesn't


mirage: init at 0.5.1

Motivation for this change
Package new application mirage as attribute mirage-im (there's an existing alias, maybe I could remove it?).
This is a draft since the application doesn't work yet.
This fixes #84147.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg eval
(bot's been having a bad time recently)

If you just want to try out this app and don't feel like finishing the package, they provide an AppImage, which you can run/package through appimageTools.wrapType2.

Well, I'm making some progress at least.

This is working for me now, but it needs cleanup before it's ready for review.

The update to matrix-nio breaks pantalaimon: https://github.com/matrix-org/pantalaimon/blob/master/setup.py#L32

When running I get a black window with the message:
! 14:55:58 | qrc:/src/gui/UI.qml:7:1: module "QtGraphicalEffects" is not installed

You can include this commit for compatibility of pantalaimon with matrix-nio 0.13.
https://github.com/symphorien/nixpkgs/commit/3e84e683977d542f644a00d5b1d804f6d1060269

@symphorien I wonder if that happened after a rebase as I saw this too when installed in my system profile. I added the extra qt dependency and it seems to have fixed it. I also added your pantalaimon commit. Thank you for the testing, review, and feedback.

I tried mirage and it works, except that I cannot decrypt messages sent or received in mirage. I wonder if there is an optional dependency to enable it, or something like that, as it is advertised that it should work.
For some reason, the update of matrix-nio makes pantalaimon tests hang. (the update of pantalaimon without the upgrade of matrix-nio works fine) Can you reproduce? Unfortunately I'm a bit short on time to investigate.

It segfaults, I'm concerned I'm not getting qt wrapped properly.

It looks like my derivation is fine, but Mirage doesn't handle upgrades very well currently: https://github.com/mirukana/mirage/issues/90

I'm very new to nix packaging so I'm sorry if these questions are stupid, but reading through the mirage install manual recommends:

libjpeg-turbo
zlib
libtiff
libwebp
openjpeg2
libmediainfo

and the requirements.txt also includes pyfastcopy, for which no nix package exists yet afaik.

I'm very new to nix packaging so I'm sorry if these questions are stupid, but reading through the mirage install manual recommends:
* libjpeg-turbo

* zlib

* libtiff

* libwebp

* openjpeg2

* libmediainfo

and the requirements.txt also includes pyfastcopy, for which no nix package exists yet afaik.

not everything is a hard requirement, and in this particular case, these dependencies are meant for the pillow package to work correctly, and that is handled by the pillow python package https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/python-modules/pillow/default.nix

ah right thanks @jonringer that's kinda what I thought. and libmediainfo is installed by pymediainfo.
And pyfastcopy is apparently only interesting for python versions < 3.8
https://github.com/mirukana/mirage/blob/87d34082deb1db3c8f784876cd4aa7202471b8db/src/backend/media_cache.py#L25

you should be able to rebase on latest master to get rid of matrix and pant changes

do you mind squashing/removing some of the fixup commits, particularly:
mirage: feedback
mirage: also remove propagatedBuildInputs
Revert "mirage: also remove propagatedBuildInputs"

One way to prevent propagation of python is:
diff --git a/pkgs/applications/networking/instant-messengers/mirage/default.nix b/pkgs/applications/networking/instant-messengers/mirage/default.nix
index 1101d6f9b06..8e99ca64123 100644
--- a/pkgs/applications/networking/instant-messengers/mirage/default.nix
+++ b/pkgs/applications/networking/instant-messengers/mirage/default.nix
@@ -44,7 +44,10 @@ mkDerivation rec {
     wrapProgram $out/bin/mirage \
       --prefix PYTHONPATH : "$PYTHONPATH" \
       "''${qtWrapperArgs[@]}"
-    '';
+  '';
+  postFixup = ''
+    rm $out/nix-support -r
+  '';

   meta = with lib; {
     description = "A fancy, customizable, keyboard-operable Qt/QML+Python Matrix chat client for encrypted and decentralized communication.";


Parametrize hashes

Currently, iroha_crypto::Hash length is hardcoded to 32 bytes. It's possible that different clients would like to have hashes of different length. As discussed this isn't required to be runtime modifiable, therefore it would be most appropriate to use const generics like:
    type HashLen = usize;
    struct Hash<const LEN: HashLen> {
        ...
    }

implemented naively, this would bring a lot of changes all around codebase so some thought should be put into how this will manifest around codebase. If this cannot be done immediately it should at least be done so that it's visible in the schemas so that clients don't make unwarranted assumptions about the size of the hash

Some work done here: https://github.com/hyperledger/iroha/pull/2382


DocumentDB listConnectionStrings only lists 1 "Default MongoDB Connection String"

https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DocumentDB/databaseAccounts/{accountName}/listConnectionStrings?api-version=2015-04-08
and az cosmosdb list-connection-strings  only return 1 connection string.
From the description and the fact that the DatabaseAccountListConnectionStringsResult is described as "An array that contains the connection strings for the Cosmos DB account", I think that all 4 connection strings should be returned : 'primary', 'secondary', 'primaryReadonly', 'secondaryReadonly'.

Hi @jeremie0, thank you for bring up this request. In January of this year, we altered the response of the API request so that all 4 connection strings are included in the response.


use automatic publishing

Can we arrange for this doc to be automatically published, so we don't need to point at the editor's drafts?
If we need help, PLH is likely willing to help.

Looping in @ylafon…

At the least, can we do another versioned release in the next week or so?

Sounds good to me. I've never done this before, so I don't know where to start.

There are manual steps when publishing as the (c) section is not the usual one, so it would require some adaptation in order to do automatic publishing.

(c) section?

Any update on this?  I dislike that the published version is so very much out of date...

There are roadblocks that we are working on, expect this to use automatic publishing once the issues in getting design-principles document  to do the same will be solved.

Publishing a snapshot sounds good to me!

Publishing a snapshot sounds good to me!

Hi @ylafon any update on this? I think we are all keen to set up a process via which this can be auto-published.

Hi @ylafon any update on this? I think we are all keen to set up a process via which this can be auto-published.

Just to be clear - auto-publication would imply that joint agreement is reached between PING and TAG via the PR and PR approval mechanism. And therefore any merged PR is a-ok to auto-publish to TR space.

Just to be clear - auto-publication would imply that joint agreement is reached between PING and TAG via the PR and PR approval mechanism. And therefore any merged PR is a-ok to auto-publish to TR space.

I understand there's a Process issue. In the meantime, could we mint a new snapshot?

@wseltzer wrote, in February:

I understand there's a Process issue. In the meantime, could we mint a new snapshot?

A new snapshot got published in March.
Leaving this open as we still don't have automatic publishing set up for this document.

Tickling this issue, since people file new issues (like https://github.com/w3ctag/security-questionnaire/issues/129) that are already fixed in the editor's draft.

It should be part of implementation of process 2021 in specberus, so no progress can be made until the tool allow it.

It should be part of implementation of process 2021 in specberus, so no progress can be made until the tool allow it.

I think those updates have happened, but I'm not sure. What say you, @ylafon?

Any updates here, @ylafon @samuelweiler? We'd love to not have to think too hard about when to publish this thing.

It is making (slow) progress, I should be able to test soon, if it works, then we can make it automatic.


doesn't appear to work with PouchDB 7

no idea why, but after upgrading to PouchDB 7, sync no longer works. I can see the handshaking happening using PouchDB.debug, but no data is transferred over the wire.

it turns out to be that webpack 2 is breaking pouchdb/socket-pouch combo. No idea why


kubectl gs template cluster: Mandatory choice of --name or new --generated-name for CAPI cluster names

As discussed in SIG UX sync 2023-11-21, we want to ensure that users think of reasonable cluster names when creating workload clusters. That means that an explicit choice should be made if random, 5-letter names should still be used – which we considered a confusing and problematic default. Don't change the command for vintage since there might be production-level automation inside customers or Giant Swarm that breaks unnecessarily. Let's introduce this change for CAPI where no / very few production-grade clusters are relevant right now.
Also, document publically (here) where the cluster name is visible (e.g. DNS records) so that users can make an educated choice.

released, docs in review


[Issue 5904]Support unload all partitions of a partitioned topic

Fixes #5904
Motivation
Pulsar supports unload a non-partitioned-topic or a partition of a partitioned topic. If there has a partitioned topic with too many partitions, users need to get all partition and unload them one by one. We need to support unload all partition of a partitioned topic.

Great work, If possible, please add a more detailed description of the motivation and modification for this pull request. In addition, the test seems to have some problems. You can try to fix this and then test it with the following command. @ltamber
mvn test -Dtest=org.apache.pulsar.broker.admin.PersistentTopicsTest -pl pulsar-broker

@jiazhai @tuteng @codelipenghui please take a look

@sijie PTAL

/pulsarbot run-failure-checks

Add label release/2.5.1, due to #6339 dependency


Extreme memory usage for "rzls" in large project

Issue Type: Bug
I have a project that references several GB of source files, spread out over hundreds of thousands of files. VSCode opens the project nicely and makes it possible to work with and search through the files.
However every once in a while it crashes my computer. I've seen that a process called "rzls" seems to hog immense amounts of RAM, in the range of 80-90% of all available RAM. Today it crashed by work computer with 64GM of RAM, of which typically only 10-20% are used with common applications like Crome or Thunderbird. No compile was running at the time of the crash.
See attached screenshot.
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:32:10.090Z)
OS version: Linux x64 5.4.0-60-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 3910)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: unavailable_offvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
31.10GB (0.25GB free)

Process Argv
BDAScripts.code-workspace --no-sandbox --crash-reporter-id cfee8681-3b9d-43e6-a2b1-3c1799828d72

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Extensions (20)

Extension
Author (truncated)
Version

bracket-pair-colorizer-2
Coe
0.2.0

gitlens
eam
11.1.3

shell-format
fox
7.0.1

vscode-pull-request-github
Git
0.22.0

vscode-test-explorer
hbe
2.19.4

latex-workshop
Jam
8.15.0

autoconf
mae
0.1.0

vscode-catch2-test-adapter
mat
3.6.19

vscode-docker
ms-
1.9.0

csharp
ms-
1.23.8

python
ms-
2020.12.424452561

jupyter
ms-
2020.12.414227025

remote-containers
ms-
0.154.2

cpptools
ms-
1.1.3

bash-debug
rog
0.3.9

rewrap
stk
1.13.0

code-spell-checker
str
1.10.2

shellcheck
tim
0.12.3

cmake
twx
0.0.17

markdown-all-in-one
yzh
3.4.0

Most likely you need to report this issue in C# extension repo https://github.com/OmniSharp/omnisharp-vscode
VS Code doesn't support this kind of projects out of the box.

Most likely you need to report this issue in C# extension repo https://github.com/OmniSharp/omnisharp-vscode
VS Code doesn't support this kind of projects out of the box.


Wrong header parsing order

According to the (unofficial) spec, X-Forwarded-For format is the following:
X-Forwarded-For: client, proxy1, proxy2

https://en.wikipedia.org/wiki/X-Forwarded-For#Format
but the library will return proxy2. This contradicts the spec and behavior of other libraries like Symfony's HttpFoundation
Solution: remove array_reverse in header parsing

Hi, thanks for notify this.
One question: seems like this order is only for X-Forwarded-For header but not X-Forwarder, right?
If you want to work on a PR, I'd appreciate that. If not, don't worry, I can fix it but I don't have much free time for now.

Probably invalid issue, #11


count of single genes annotated to a term

I wanted this link:
http://pombase2.aska.gen.nz/term/FYPO%3A0001122
Single-allele genotypes associated with this term ...
http://pombase2.aska.gen.nz/term_genotypes/FYPO%3A0001122
to give me a count of genes.
Currently the count is genotypes
cdc13 (SPBC582.03)	G2/M B-type cyclin Cdc13	cdc13-117(C379Y)
.
.
.
and separated like this
cdc13 (SPBC582.03)	G2/M B-type cyclin Cdc13	cdc13+
.
.
.
cdc13 (SPBC582.03)	G2/M B-type cyclin Cdc13	cdc13Δ
need to group by gene and genotype.
Add count for gene (probably keep the count for genotype, although it is more arbitrary)

Does the other link on that page give you what you were thinking of?:
"Genes from single-allele genotypes associated with this term ..."

Doh yes,
I didn't read it properly!
I do think that for single -allele genes should precede genotypes though?
Others?

and the number is spot on ;)

Actually the number here isn't correct...

What is displayed int he list is correct, but the number is the number of annotations, not genes

Whoops, now fixed.


auto-binding now also generates vertex input location bindings

When auto-binding is enabled it will now also auto-generate layout(location = X) attributes. It works in tandem with explicit bindings provided to ShaderOutput::vertexSemantics, and it will only auto-generate locations for those not explicitly specified in that map.

I should note the reason why I added this. It's primarily useful for Vulkan, which has no way to reflect locations from SPIR-V, nor does it have any functionality to dynamically bind locations like OpenGL. This means if you don't explicitly set locations in GLSL, you need some kind of a third-party library like SPIR-V Cross. But obviously less third party dependencies are involved the better, and especially so if XShaderCompiler can solve the problem.

Sure, but currently it looks like the shader reflection does not include the auto-binding slots for the vertex input.

True, I haven't added that. glslang, which I'm using for GLSL -> SPIR-V compilation provides me with that information instead. But it could be useful for XShaderCompiler to output it as well.

I fixed that with be17931.


Increase link checker timeout

Timeout Error
We have a number of sites that persistently fail link checking with a "Timeout Error" status.  I've visited a few pages and found that although they are slow initially, they do render eventually.  I suspect that they are low traffic pages and just need a bit of time to warm up.  These errors are
frustrating as they list as broken links, but there's not much a link administrator can do about them.
We had 284 pages that failed like this last night.  If all of those took the maximum time to open a connection and the maximum response time, then this would increase the link checker time by about 45 minutes (ignoring problems with redirects).  Given that the link checker starts at 2am and usually finishes at approx 8:30am, I don't think this is too bad.
Tim L-B and I will keep an eye on this to see if it improves matters.  It's possible that we might get a really long run once in a while, but I think that's OK.
Index on Link URL
We also do at least 50,000 Link selects by url every day in link checker. It seems fair to add an index on this.  It might save enough time to eradicate any extra added by my increasing Faraday's timeouts in the previous commit.
Queries by url also exist in the Link model, so adding this might shave a little time off the edit cycle too.
Uniq vs Distinct
It seems that using .uniq on the array of urls is an order of magnitude quicker than using .distinct in the query here.  (~50ms vs ~850ms on prod) The number of URLs is likely to stay fairly static (40,000ish) and the number of unique URLs is fairly likely to stay in the 25 - 35,000 range. It doesn't matter very much relative to the length of the task, but since I
spotted it, I wanted to scratch the itch.

Looks good and sensible to me! Great PR description! 💯


model: pytorch: Change network layer name property to layer_type

solved issue #908.
Also changed the model example in docs.

 ======================================================================
ERROR: test_shell_pytorch (flower17.test_flower17.TestFLOWER17)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/dffml/dffml/dffml/util/asynctestcase.py", line 69, in run_it
    result = self.loop.run_until_complete(coro(*args, **kwargs))
  File "/usr/share/miniconda/lib/python3.7/asyncio/base_events.py", line 587, in run_until_complete
    return future.result()
  File "/home/runner/work/dffml/dffml/examples/flower17/test_flower17.py", line 77, in test_shell_pytorch
    await CLI.cli(*cmd[1:])
  File "/home/runner/work/dffml/dffml/dffml/util/cli/cmd.py", line 224, in cli
    return await cmd.do_run()
  File "/home/runner/work/dffml/dffml/dffml/util/cli/cmd.py", line 203, in do_run
    return await self.run()
  File "/home/runner/work/dffml/dffml/dffml/cli/ml.py", line 40, in run
    return await train(self.model, self.sources)
  File "/home/runner/work/dffml/dffml/dffml/high_level.py", line 379, in train
    async with sources() as sctx, model() as mctx:
  File "/home/runner/work/dffml/dffml/model/pytorch/dffml_model_pytorch/pytorch_base.py", line 89, in __aenter__
    self._model = self.createModel()
  File "/home/runner/work/dffml/dffml/model/pytorch/dffml_model_pytorch/pytorch_pretrained.py", line 64, in createModel
    for key, value in self.parent.config.layers.items()
  File "/home/runner/work/dffml/dffml/model/pytorch/dffml_model_pytorch/pytorch_pretrained.py", line 64, in <listcomp>
    for key, value in self.parent.config.layers.items()
  File "/home/runner/work/dffml/dffml/model/pytorch/dffml_model_pytorch/utils/utils.py", line 32, in create_layer
    layer_type = parameters.pop("layer_type")
KeyError: 'layer_type'

----------------------------------------------------------------------
Ran 10 tests in 484.089s

FAILED (errors=1)

Looks like we are getting an error. Let us know in the Gitter channel if you need help debugging!

Codecov Report

Merging #918 (ab4fe56) into master (eaa94f2) will decrease coverage by 0.43%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #918      +/-   ##
==========================================
- Coverage   85.01%   84.58%   -0.44%
==========================================
  Files         139      139
  Lines        9032     8886     -146
  Branches     1506     1508       +2
==========================================
- Hits         7679     7516     -163
- Misses       1048     1059      +11
- Partials      305      311       +6

Impacted Files
Coverage Δ

tests/df/test_memory.py
83.60% <0.00%> (-10.15%)
:arrow_down:

tests/operation/test_sqlite_query.py
93.33% <0.00%> (-6.67%)
:arrow_down:

tests/util/test_net.py
96.36% <0.00%> (-3.64%)
:arrow_down:

dffml/operation/math.py
80.00% <0.00%> (-1.82%)
:arrow_down:

tests/test_docstrings.py
95.65% <0.00%> (-1.77%)
:arrow_down:

dffml/cli/config.py
57.69% <0.00%> (-1.57%)
:arrow_down:

dffml/cli/dataflow.py
80.30% <0.00%> (-1.35%)
:arrow_down:

dffml/service/dev.py
71.21% <0.00%> (-0.96%)
:arrow_down:

dffml/operation/model.py
84.21% <0.00%> (-0.79%)
:arrow_down:

dffml/util/net.py
73.84% <0.00%> (-0.79%)
:arrow_down:

... and 58 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eaa94f2...ab4fe56. Read the comment docs.

@sakshamarora1 Can you give this a quick review? It looks okay to me but just to be sure.


Help configuring custom icon and sound on notification

Hey,
I could configure everything fine the CrossPushNotification, even with the Application class to receive notifications when the app is closed.
I have a doubt respect configuring the icon and the sound of the notification, I read the README and it says to configure that in the

Android project using the following properties from CrossPushNotification class:

//The sets the key associated with the value will be used to show the title for the notification
public static string NotificationContentTitleKey { get; set; }

//The sets the key associated with the value will be used to show the text for the notification
public static string NotificationContentTextKey { get; set; }

//The sets the key associated with the root value will be used to show the text inside it for the notification
public static string NotificationContentDataKey { get; set; }

//The sets the resource id for the icon will be used for the notification
public static int IconResource { get; set; }

//The sets the sound  uri will be used for the notification
public static Android.Net.Uri SoundUri { get; set; }

I get confused about the place I have to configure that settings, is in the implementation of the IPushNotificationListener? I have to put some getters to that properties in that class?
Thanks, great lib, in a few steps I configured push notifications on my application.

These are static properties on CrossPushNofication class, only available on your android project. So you will set it before or after intializing the plugin on your Android project.
CrossPushNotification.IconResource
CrossPushNotificatio.SoundUri

@rdelrosario I configured thatin the CrossPushNotification class in my Android prioject but the notification still with an empty icon
            CrossPushNotification.Initialize<Listener>("xxxxxxxx");             CrossPushNotification.IconResource = Resource.Drawable.icon;
I fire the notifications on firebase console, am I missing something?
Thanks.


Target React Components in Styled Cascade

I would love to extend the composability of styled components by being able to refer to them later by their Component names in the interpolated string. I'm unsure exactly how to approach doing this, hence no PR right now, but I find it something I want to use almost every time I'm pulling pieces together to make a UI.
Example
const SmallComponent = styled.p`
  font-color: #404040;
`

const LargerComponent = styled.div`
  width: 100%;
  font-family: 'Helvetica' sans-serif;
  ${SmallComponent}: {
    font-size: 3em;
  }
`

Now that I've actually written it out I think the variable in interpolated string could be a solid idea. Anyway, thoughts?
Cheers,
Patrick

Good look for you that this is already possible with styled-components version 2 ;)

@k15a Wait really?! Is the the syntax I used the correct one? This just made my day.

@pkrawc you'll have to remove that trailing colon, but yea it works


adding ProgressMeter iOS library

Project URL
https://github.com/khawajafarooq/ProgressMeter
Description
Following are the changes:

Adding category ProgressView under UI section
Adding ProgressMeter iOS library under ProgressView section

Why it should be included to awesome-ios (optional)
Adding value to progress view with a meter like UI and custom annotations. Everything is enabled for iOS >=9.0 and Swift 4.0. The control supports autolayout.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          2 Warnings

:warning:
Too many changes (when adding, please keep it to one project per Pull Request)

:warning:
Found 3 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

854
301
https://github.com/terflogag/FacebookImagePicker redirects tohttps://github.com/floriangbh/FacebookImagePicker

1355
301
https://github.com/SwiftOnEdge/Edge redirects tohttps://github.com/skylab-inc/Edge

2389
301
https://github.com/terflogag/OpenSourceController redirects tohttps://github.com/floriangbh/OpenSourceController

  Generated by :no_entry_sign: Danger

Thanks @khawajafarooq
Sent with GitHawk

Hi, are you going to merge it?

Sorry for the delay, @khawajafarooq!
Thank you so much for contributing and good job on the lib 👍


feat(css/lints): Implement property-no-vendor-prefix rule

Description:
Implemented property-no-vendor-prefix rule.
BREAKING CHANGE:
No.

What's the state of this PR?
Is this ready to be merged?

Maybe no.

No, I am continue working on some required stuff, sorry for delay

@g-plane Let's keep open, sorry for delay, was small busy other tasks, we should finish it and return to this

@g-plane Sorry for big delay, really a lot of tasks, I have finished, now we have public https://github.com/swc-project/swc/blob/main/crates/swc_css_prefixer/src/prefixer.rs#L92 so you can use it

Sorry I don't have enough time to go on. I'm closing now.