Linking error for diesel_cli in Alpine despite libraries being installed

Versions

Rust: 1.75.0
Diesel: 2.1.5
Database: postgres
Operating System: Alpine Linux

Feature Flags

diesel: postgres

Problem Description
Installing diesel_cli with postgres in Alpine fails, because libpgcommon, libpgport, libssl, and libcrypto are not included in the cc command.
I don't know if this problem is caused by diesel_cli itself or some dependency, but it should at least be documented somewhere.
What is the actual output?
    Updating crates.io index
  Installing diesel_cli v2.1.1
    Updating crates.io index
   Compiling proc-macro2 v1.0.79
[...]
   Compiling toml_edit v0.19.15
   Compiling diesel v2.1.5
   Compiling toml v0.7.8
   Compiling migrations_internals v2.1.0
   Compiling migrations_macros v2.1.0
   Compiling serde_regex v1.1.0
   Compiling diesel_migrations v2.1.0
   Compiling diesel_cli v2.1.1
error: linking with `cc` failed: exit status: 1
  |
  = note: LC_ALL="C" PATH="/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/bin:/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/bin/self-contained:/usr/local/cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" VSLANG="1033" "cc" "-m64" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/rcrt1.o" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crti.o" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtbeginS.o" "/tmp/rustcIjmnTk/symbols.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.00.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.01.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.02.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.03.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.04.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.05.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.06.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.07.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.08.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.09.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.10.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.11.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.12.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.13.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.14.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.diesel.50ec808d4e1e3636-cgu.15.rcgu.o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b.4z8r9slgviysewgb.rcgu.o" "-Wl,--as-needed" "-L" "/tmp/cargo-installkLXMcA/release/deps" "-L" "/usr/lib" "-L" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib" "-Wl,-Bstatic" "/tmp/cargo-installkLXMcA/release/deps/libdiffy-5e564561211e10cc.rlib" "/tmp/cargo-installkLXMcA/release/deps/libnu_ansi_term-b7d3d522e607cf87.rlib" "/tmp/cargo-installkLXMcA/release/deps/liboverload-10f7fd7880996a60.rlib" "/tmp/cargo-installkLXMcA/release/deps/liburl-00c52c647114c707.rlib" "/tmp/cargo-installkLXMcA/release/deps/libidna-373fc0b1e7957eee.rlib" "/tmp/cargo-installkLXMcA/release/deps/libunicode_normalization-1bdabd55c2c50447.rlib" "/tmp/cargo-installkLXMcA/release/deps/libtinyvec-33bc818232c96f88.rlib" "/tmp/cargo-installkLXMcA/release/deps/libtinyvec_macros-fbbe34639df0cab2.rlib" "/tmp/cargo-installkLXMcA/release/deps/libunicode_bidi-bbea6925253a10ff.rlib" "/tmp/cargo-installkLXMcA/release/deps/libform_urlencoded-37080d45b68109a0.rlib" "/tmp/cargo-installkLXMcA/release/deps/libpercent_encoding-f351235460ab9d75.rlib" "/tmp/cargo-installkLXMcA/release/deps/libdotenvy-4d43521c5b5f0a14.rlib" "/tmp/cargo-installkLXMcA/release/deps/libchrono-11afb3097fdfea49.rlib" "/tmp/cargo-installkLXMcA/release/deps/libnum_traits-a6bd0c3a7e5ee5b5.rlib" "/tmp/cargo-installkLXMcA/release/deps/libiana_time_zone-78452d5d3671e75b.rlib" "/tmp/cargo-installkLXMcA/release/deps/libheck-6b9488ca4a64be58.rlib" "/tmp/cargo-installkLXMcA/release/deps/libdiesel_table_macro_syntax-628a88e29ce4d136.rlib" "/tmp/cargo-installkLXMcA/release/deps/libsyn-4d863b0ded05edde.rlib" "/tmp/cargo-installkLXMcA/release/deps/libquote-9c3e020f36e1c9bb.rlib" "/tmp/cargo-installkLXMcA/release/deps/libproc_macro2-c9b6a44adfe30003.rlib" "/tmp/cargo-installkLXMcA/release/deps/libunicode_ident-72a946a226bf1c75.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libproc_macro-771f5f282c47560d.rlib" "/tmp/cargo-installkLXMcA/release/deps/libclap_complete-5012d61bc3f7d240.rlib" "/tmp/cargo-installkLXMcA/release/deps/libdiesel_migrations-b9f897c642d60d94.rlib" "/tmp/cargo-installkLXMcA/release/deps/libmigrations_internals-97ee7e5f27a12ce7.rlib" "/tmp/cargo-installkLXMcA/release/deps/libtoml-6d9131d55ee173ca.rlib" "/tmp/cargo-installkLXMcA/release/deps/libtoml_edit-4355af0f8a1aed22.rlib" "/tmp/cargo-installkLXMcA/release/deps/libserde_spanned-f5c66e56dc7576b8.rlib" "/tmp/cargo-installkLXMcA/release/deps/libindexmap-66807ab8984a7cc5.rlib" "/tmp/cargo-installkLXMcA/release/deps/libequivalent-3d0bf949e6f9c23b.rlib" "/tmp/cargo-installkLXMcA/release/deps/libhashbrown-935e08db9b81b1bb.rlib" "/tmp/cargo-installkLXMcA/release/deps/libwinnow-28650c353e3fb371.rlib" "/tmp/cargo-installkLXMcA/release/deps/libtoml_datetime-69c71640b0395afe.rlib" "/tmp/cargo-installkLXMcA/release/deps/libdiesel-c5dc5df1372cab52.rlib" "/tmp/cargo-installkLXMcA/release/deps/libitoa-aba3c429878fe160.rlib" "/tmp/cargo-installkLXMcA/release/deps/libbitflags-0f360508d9fd27a3.rlib" "/tmp/cargo-installkLXMcA/release/deps/libbyteorder-1b818e84aedcd24c.rlib" "/tmp/cargo-installkLXMcA/release/deps/libpq_sys-9efba9c812cd0497.rlib" "-lpq" "/tmp/cargo-installkLXMcA/release/deps/libserde_regex-79803b090beeb8c5.rlib" "/tmp/cargo-installkLXMcA/release/deps/libregex-cf8fbb6cd79bf7b7.rlib" "/tmp/cargo-installkLXMcA/release/deps/libregex_automata-4e1476ac79dc3a3b.rlib" "/tmp/cargo-installkLXMcA/release/deps/libaho_corasick-b5a969608caf3624.rlib" "/tmp/cargo-installkLXMcA/release/deps/libmemchr-9d6eb58a185199f2.rlib" "/tmp/cargo-installkLXMcA/release/deps/libregex_syntax-2225d0e3349e1761.rlib" "/tmp/cargo-installkLXMcA/release/deps/libclap-f76930904b9276e6.rlib" "/tmp/cargo-installkLXMcA/release/deps/libclap_builder-95604e29e17a0b55.rlib" "/tmp/cargo-installkLXMcA/release/deps/libstrsim-ce5e35de57c2e3c8.rlib" "/tmp/cargo-installkLXMcA/release/deps/libanstream-1b6c97fa89b0451a.rlib" "/tmp/cargo-installkLXMcA/release/deps/libanstyle_query-ba73f2a2db153ff0.rlib" "/tmp/cargo-installkLXMcA/release/deps/libcolorchoice-47516f38bca96d04.rlib" "/tmp/cargo-installkLXMcA/release/deps/libanstyle_parse-580fb861b3e7c5f4.rlib" "/tmp/cargo-installkLXMcA/release/deps/libutf8parse-8db9483a53737766.rlib" "/tmp/cargo-installkLXMcA/release/deps/libclap_lex-34b4742b4b039c0c.rlib" "/tmp/cargo-installkLXMcA/release/deps/libanstyle-c9c27cec39c04ceb.rlib" "/tmp/cargo-installkLXMcA/release/deps/libserde-4d548ce2aab7a838.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libstd-11c02606063fb1b5.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libpanic_unwind-527b1ade0207850b.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libobject-5c6479882291983e.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libmemchr-b30d7598b031e855.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libaddr2line-7bdd9f1650697dee.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libgimli-af6e6b96893335a7.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/librustc_demangle-61a774fd0ca56cef.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libstd_detect-0bdaa2154e535182.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libhashbrown-40daaa64e7b3ff16.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/librustc_std_workspace_alloc-51b0c25ea806d020.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libminiz_oxide-503b1c30e4fe986c.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libadler-0dfa15d5b98a6f2c.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libunwind-7e3d215879e752d5.rlib" "-lunwind" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libcfg_if-f91de774775af47a.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/liblibc-a172c9da7a8c39aa.rlib" "-lc" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/liballoc-05ed26095d7bae0a.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/librustc_std_workspace_core-940bcdced839ada6.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libcore-ece58c607aadf4ad.rlib" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/libcompiler_builtins-cfd03998b63f49b3.rlib" "-Wl,-Bdynamic" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-nostartfiles" "-L" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib" "-L" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained" "-o" "/tmp/cargo-installkLXMcA/release/deps/diesel-c14349dc3829848b" "-Wl,--gc-sections" "-static-pie" "-Wl,-z,relro,-z,now" "-Wl,-O1" "-nodefaultlibs" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtendS.o" "/usr/local/rustup/toolchains/1.75.0-x86_64-unknown-linux-musl/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/crtn.o"
  = note: /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: /usr/lib/libpq.a(fe-connect.o): in function `defaultNoticeProcessor':
          fe-connect.c:(.text+0x288): undefined reference to `pg_fprintf'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: /usr/lib/libpq.a(fe-connect.o): in function `sslVerifyProtocolVersion':
          fe-connect.c:(.text+0xcb1): undefined reference to `pg_strcasecmp'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: fe-connect.c:(.text+0xcc5): undefined reference to `pg_strcasecmp'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: fe-connect.c:(.text+0xcd9): undefined reference to `pg_strcasecmp'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: fe-connect.c:(.text+0xced): undefined reference to `pg_strcasecmp'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: /usr/lib/libpq.a(fe-connect.o): in function `emitHostIdentityInfo':
          fe-connect.c:(.text+0xe25): undefined reference to `pg_getnameinfo_all'
[...]
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: /usr/lib/libpq.a(fe-secure.o): in function `pqsecure_raw_write.part.0':
          fe-secure.c:(.text+0x47c): undefined reference to `pg_snprintf'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: fe-secure.c:(.text+0x549): undefined reference to `pg_strerror_r'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: fe-secure.c:(.text+0x56b): undefined reference to `pg_snprintf'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: /usr/lib/libpq.a(fe-auth.o): in function `pg_fe_sendauth':
          fe-auth.c:(.text+0x842): undefined reference to `pg_md5_encrypt'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: fe-auth.c:(.text+0x862): undefined reference to `pg_md5_encrypt'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: /usr/lib/libpq.a(fe-auth.o): in function `pg_fe_getusername':
          fe-auth.c:(.text+0xa74): undefined reference to `pg_get_user_name'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: /usr/lib/libpq.a(fe-auth.o): in function `PQencryptPassword':
          fe-auth.c:(.text+0xb78): undefined reference to `pg_md5_encrypt'
          /usr/lib/gcc/x86_64-alpine-linux-musl/13.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: /usr/lib/libpq.a(fe-auth.o): in function `PQencryptPasswordConn':
          fe-auth.c:(.text+0xc71): undefined reference to `pg_md5_encrypt'
          collect2: error: ld returned 1 exit status

  = note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname)

error: could not compile `diesel_cli` (bin "diesel") due to previous error
error: failed to compile `diesel_cli v2.1.1`, intermediate artifacts can be found at `/tmp/cargo-installkLXMcA`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Steps to reproduce

Start an alpine based container using podman run --rm -it rust:alpine
Install the dependencies using apk add --no-cache musl-dev openssl-libs-static libpq-dev
Try to install diesel_cli using cargo install diesel_cli --no-default-features --features postgres

Interim fix
The issues can be fixed manually by instructing rust to include the missing libraries using the environment variable RUSTFLAGS="-lpgcommon -lpgport -lssl -lcrypto".

Thanks for opening this bug report. This seems to be a duplicate of https://github.com/sgrif/pq-sys/issues/27, therefore I'm closing this in favor of the other bug.

To quickly elaborate, if I understand correctly, this has been fixed in pg-sys 0.5.0, which the current main branch of diesel already supports and will therefore be available in diesel's next release. Thanks alot and keep up the good work 😊

That's nearly correct. It doesn't fix statically linking the system provided libraries, as we do not have a good way to detect which libraries are actually needed. It instead provides a "bundled" feature flag that allows to build a defined version of libpq from source and statically links that version. In that way we have the required knowlegde about all the dependencies.

@weiznich do you have any timeline for the next diesel release? I've updated my Cargo.toml to pull master from the git directly which works well, but would love to pin against the released version.

@peasee As this is a free time project we generally do not give any ETA for releases other than "when it's done". You can help making this happen faster by either contributing fixes for the remaining issues marked as release blocker or by funding the development.


(How) Can I open a file's parent directory?

I'm generally fine with only having a single buffer open, but I'd like to be able to return to the parent directory in file-listing mode.
I'm fond of netrw/vinegar's - keybinding for this, but I think acme let me run .. in the tagbar to do the same.

That's odd. .. or . should work. It seems to be working from the buffer, but not from in the tagline.

that it does! odd.

Can you try with the latest build (assuming you're pressing the enter key and not using the mouse)? I just added a fix, hopefully.

woo! work for me.


Linux Nvidia driver version for video encode?

Hi, it wanted to try the video encoder sample.  I have the 535.43.22 beta driver which supports the video encode/decode extensions.  The video decode sample works but the video encode sample fails with an VK_ERROR_INCOMPATIBLE_DRIVER error.
I also tried to install the 515.49.24 driver linked to by the BUILD.md file but I can't install it on Ubuntu 22.04.  The kernel module fails to build with the 6.5.0 kernel.
Is there another beta driver that will work, or what kernel do I need to for the 515.49.24 driver?
Thanks.

Hi @brianpaul,
Can you please try the https://github.com/nvpro-samples/vk_video_samples/tree/video-encode-h264-265-alpha branch. This code base will be the one merged to main after fixing some of the outstanding issues with encoding h.264 and h.265 content. So, please keep in  mind that this branch is still a WIP preview, but at least you should be able to create video encode-enabled  devices successfully and encode content. Please refer to the list of issues in the Readme that we are working on addressing. Please also note that there are validation layer issues that need addressing.
As always, we also welcome community fixes and contributions.

brianpaul, please check the latest ToT code at main.


Updated pytorch transforms and tests

Following https://github.com/albu/albumentations/pull/318#issuecomment-527161032 and https://github.com/albu/albumentations/pull/318#issuecomment-527173032

Removed torch module as current version >= 0.3.0

@albu @ternaus what do you think ?

looks fine but we still have to preserve old behavior for all these who uses ToTensor

@albu how do you prefer to keep the old behavior :

Old ToTensor -> ToTensor_deprecated with warning about removal of the old behaviour
New ToTensor

or

Old ToTensor -> ToTensor with warning about removal of the old behaviour
New ToTensor -> ToTensorV2 and rename it ToTensor once in v0.4.0

I would prefer the second option.

second option will force developers to replace ToTensor twice. first in this release - by ToTensorV2 and in 0.4.0 ToTensorV2 -> ToTensor. it's weird

@albu

second option will force developers to replace ToTensor twice. first in this release - by ToTensorV2 and in 0.4.0 ToTensorV2 -> ToTensor. it's weird

I agree, but like that we are keeping BC. Assuming that users mostly use current version ToTensor, they are just become aware of deprecation and replacement. Others (like me) do not use ToTensor but their own version of it and they will just switch to A.ToTensorV2 and since 0.4.0 to A.ToTensor().
Otherwise, what do you think anout 1st option ?

first option does not work at all. so from two evils second is better. I just wonder if there are other better options..


Cfn-lint 0.24.1 fails to parse paths with special characters

*cfn-lint version: *
cfn-lint 0.24.1
Description of issue.
Cfn-lint fails to correctly parse paths with special characters such as [] and throws an unhandled exception while executing. For example (file contents do not matter):
$ cfn-lint error\[package-1.1\]foo/cli-strings.yml
Traceback (most recent call last):
  File "/home/user/.local/bin/cfn-lint", line 10, in <module>
    sys.exit(main())
  File "/home/user/.local/lib/python3.6/site-packages/cfnlint/__main__.py", line 28, in main
    (args, filenames, formatter) = cfnlint.core.get_args_filenames(sys.argv[1:])
  File "/home/user/.local/lib/python3.6/site-packages/cfnlint/core.py", line 146, in get_args_filenames
    if not config.templates:
  File "/home/user/.local/lib/python3.6/site-packages/cfnlint/config.py", line 538, in templates
    add_filenames = glob.glob(filename, recursive=True)
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/glob.py", line 20, in glob
    return list(iglob(pathname, recursive=recursive))
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/glob.py", line 71, in _iglob
    for dirname in dirs:
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/glob.py", line 55, in _iglob
    yield from _glob1(dirname, basename, dironly)
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/glob.py", line 83, in _glob1
    return fnmatch.filter(names, pattern)
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/fnmatch.py", line 52, in filter
    match = _compile_pattern(pat)
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/fnmatch.py", line 46, in _compile_pattern
    return re.compile(res).match
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/re.py", line 233, in compile
    return _compile(pattern, flags)
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/re.py", line 301, in _compile
    p = sre_compile.compile(pattern, flags)
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/sre_compile.py", line 562, in compile
    p = sre_parse.parse(p, flags)
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/sre_parse.py", line 855, in parse
    p = _parse_sub(source, pattern, flags & SRE_FLAG_VERBOSE, 0)
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/sre_parse.py", line 416, in _parse_sub
    not nested and not items))
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/sre_parse.py", line 765, in _parse
    p = _parse_sub(source, state, sub_verbose, nested + 1)
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/sre_parse.py", line 416, in _parse_sub
    not nested and not items))
  File "/rootdir/env/envImprovement/python3.6/lib/python3.6/sre_parse.py", line 553, in _parse
    raise source.error(msg, len(this) + 1 + len(that))
sre_constants.error: bad character range e-1 at position 16

@GeorgeArgyros I came back around to this.
We use python GLOB to expand paths when looking at directories.  Unfortunately glob also uses [] for that expansion.  To escape you are going to have to do something like this.  Not ideal but it will work.
cfn-lint "error[[]package-1.1[]]foo/cli-strings.yaml"


C# serializes enums to integers rather than strings

Generated code in c# serializes enums to numbers rather than strings.
This should be easy to fix, and just needs the data types to be tagged. See: https://stackoverflow.com/questions/2441290/net-json-serialization-of-enum-as-string

Could you provide a reproducible test case, please?

I misunderstood what was happening. Looks like we were using the built in serializer rather than the generated one.


Join table

I might be missing something obvious here, but is there a way to do a join table without having to run raw SQL?
I'd like to use the table API (find, findOne, etc2), but I'm not quite sure how to do that when I need to join the tables.
Thanks.

Massive's finders don't support looking at any relations other than the origin as yet, but as long as you have a standardized rather than an ad-hoc query you can put it in a view and use the finders on that just like you would a table.

There is not currently a way to do joins in Massive, but I personally think we may want to add that capability in v3. Up to @robconery ultimately.
In the short-term, doing a SQL script and executing that per Massive's SQL-files-as-functions is the one way to do it, or per dmfay's comment, an ad-hoc query.
Note that part of the reasoning behind Massive is to encourage the use of SQL where it is more appropriate. Since Massive is not really an ORM in the typical sense, the notion of a join falls more into the SQL realm.

Ah, as I thought. Thanks for the answers :+1:
Not that I'm adverse to using SQL, it's just feels weird seeing all these query API without having some ways to join the tables before executing the query. Association is such a common thing after all.

@xivSolutions a while back I built something to decompose results of a join query into an arbitrarily-deep nested structure. I haven't merged it in because it requires really clunky aliasing with double-underscores to separate path elements (table1__table2__fieldname etc) in the SQL script and hand-tuned definition for how to decompose the resultset in some cases, so it's not really in a publicly-releasable state imo.
It also needs Lodash, although I'm not 100% sure if I used anything not in Underscore (we might want to consider moving to that anyway, there's no reason to prefer the smaller library on the server side). But if there's interest in working out those other rough patches, that's one of the really complicated bits already done.

@dmfay could you post what you have somewhere ? would love to take a look at it, building something very similar right now !

@quinn https://gist.github.com/dmfay/c4017b8768519679e7948706fc09532e
Thoroughly unofficial, you understand :)

@dmfay yes, cool thanks :)

@dmfay any update on when we might expect to see join capabilities?

It's a pretty long-term consideration for my part, although if someone wants to take it on I'd be happy to discuss how to fit it into the project.

Another comfort solution - for now - is using the sql-bricks library to build those sql-statements, for example:
db.run(select('field.team_id', 'team.title')
    .from('field')
    .join('team')
    .on({
      'field.team_id': 'team.id'
    })
    .where({
      'team.id': '52'
    })
    .toString())

For a solution in massive, has anyone a suggestion how the api should look? I tried to make a example, but it's quite hard to find a way to fit in the existing massive api.

My feeling on this has always been to use SQL: it's the best DSL for working with the database. Given that Massive is PG-centric, there's no reason to hide SQL behind a weird abstraction that may or may not capture the nuance you're going for.
const sql = `select field.team_id, team.title
                     from field inner join team on team.id = field.team_id
                     where team_id=52`
return db.run(sql);

This is Dian's choice, of course. One reason you don't see joins in Massive is because I didn't create it to abstract SQL. I created it (among other reasons) to help when querying things, embracing SQL in PostgreSQL as a first class citizen.

Having given it a little more thought: this really isn't about providing a mechanism to emit JOIN somethingelse ON somethingelse.x = something.y as part of db.something.find(...). That's a huge departure from what Massive does; like Rob said, it's abstracting SQL instead of facilitating it. The "Massive way", if that can be said to exist, is to turn those multi-table queries into views (or functions/scripts, if you need to apply parameters directly -- for example with pivots you want to restrict the number of rows as early as possible, so a view is unsuitable).
What I am interested in with this feature is in making the results of multi-table queries immediately useful without manual post-processing. That's what the code in that gist does: given a row set, it decomposes it into an object tree based on matching named sub-rows. The problem is that in order to use it as written, you have to define those sub-rows in your select list, and that's... probably not the worst feature I could come up with, but it's pretty bad.
Something that could work would be to skip the field name to schema translation from the gist implementation and pass the desired output schema in the find options. Given a table parent with a 1:many relationship to children, which in turn has a 1:1 relationship to grandchildren:
CREATE VIEW multitableview AS
SELECT
  parent.parentid, parent.parent1, parent.parent2,
  children.childid, children.child1, children.child2,
  grandchild.grandchildid, grandchild.grandchild1, grandchild.grandchild2
FROM parent
JOIN children ON children.parentid = parent.parentid
JOIN grandchildren ON grandchildren.childid = children.childid;

db.multitableview.find({}, {
  decompose: {
    pk: 'parentid',
    columns: ['parent1', 'parent2'],
    children: [{
      pk: 'childid',
      columns: ['child1', 'child2'],
      grandchild: [{
        pk: 'grandchildid',
        columns: ['grandchild1', 'grandchild2'],
        single: true
      }]
    }]
  }
}).then(...);

Sample output:
{
  parentid: 1,
  parent1: 'abc',
  parent2: 'def',
  children: [{
    childid: 11,
    child1: 'ghi',
    child2: 'jkl',
    grandchild: {
      grandchildid: 111,
      grandchild1: 'mno',
      grandchild2: 'pqr'
    }
  }]
}

My immediate critiques of this approach are:

it assumes that nobody's going to want to do this with a field named pk or columns, or with a field named the same as a nested object/collection. This seems fair enough as long as it's documented.
it's perhaps dangerously close to introducing models, and I don't like models at all :) That said, the decomposition schema is ad hoc and definitely easier than changing field names in a view, so I don't think that's worth worrying about.

I'm open to thoughts on this & alternate suggestions, if anyone has them!


Not all links open

Describe the bug
Clicking some links does not open them.
Right clicking the link works, as seen in the second screenshot.
To Reproduce
Open https://www.giga.de/extra/html/specials/mailto-bedeutung-und-nutzung-des-e-mail-links/, which contains two links displayed in the first screenshot. Clicking one of those links with a left click does nothing.
Screenshots

Please complete the following information:

Vienna version master :099ff0fe6: (8392)
OS version: macOS 15.0.1 (24A348)

Could you check if the site hasn't changed since your last visit ?
I do not see the two link you mentioned here:
Screenshot:

OS version : macOS 15.1

Could you check if the site hasn't changed since your last visit ?
I do not see the two link you mentioned here:
Screenshot:

They are there right in the middle of your screenshot.


Maven Dependency missing from maven central repo

Trying to setup flyway with mongo using maven
https://documentation.red-gate.com/flyway/flyway-cli-and-api/supported-databases/mongodb
But not able to find the jar:

com.github.kornilova203
mongo-jdbc-driver
1.19

I tried to find out it in maven central repository, But didnt find.
Expected: Dependency should be present in maven central repo: https://repo1.maven.org/maven2/com/github/

@tjlee @kornilova203

For the nearest future, we have no plans to publish MongoDB JDBC to Maven.


Build failing due to version change

looking at this commit...
https://github.com/medikoo/timers-ext/commit/8508aa14e060bff757ad27c65f3013c03a05568b#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R19
...it appears that es5-ext dependency was revved up to ~0.10.14 which throws this error in my build...
npm ERR! notarget No compatible version found<EMAIL_ADDRESS>npm ERR! notarget Valid install targets: npm ERR! notarget 0.10.13, 0.10.12, 0.10.11, 0.10.10, 0.10.9, 0.10.8, 0.10.7, 0.10.6, 0.10.5, 0.10.4, 0.10.3, 0.10.2, 0.10.1, 0.9.2, 0.9.1, 0.9.0, 0.8.2, 0.8.1, 0.8.0, 0.7.1, 0.7.0, 0.6.3, 0.6.2, 0.6.1, 0.6.0, 0.5.1, 0.5.0, 0.4.0, 0.3.0, 0.2.1, 0.2.0, 0.1.0 npm ERR! notarget  npm ERR! notarget This is most likely not a problem with npm itself. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist. npm ERR! notarget  npm ERR! notarget It was specified as a dependency of 'timers-ext'

although... maybe it is a caching issue on my side. Feel free to close

@jmzo yes, it looks as caching issue, as v0.10.14 was published few hours before this version of timers-ext, and it appears your setup didn't recognized v0.10.14


fixed a typo in the german translation for outdated browsers

@steffenri you should run yarn i18n after the change. Please can you do that? Thanks!

@sneridagh done


Watchdog

Can we have a some kind of watchdog here? i.e. callback function when no data send to VS1053 for some time?

Hi @vladkozlov69 I am not sure what you mean.

Hi @CelliesProjects
I think we can add something like this
extern void audio_stream_stats(int eventType, int value) __attribute__((weak));
and call it from these places where we have logging "spend %lu ms stuffing %i bytes in decoder", "Stream stalled for %lu ms" etc.
This way the user application will have the info about unstable connection, can feed WDT, etc.


The sum of the max inodes for all independent file sets may not exceed the maximum possible inodes for scale0 capacity

Describe the bug
Error when creating a pvc
To Reproduce
Steps to reproduce the behavior:
Create a storageclass as follows:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
   name: ibm-spectrum-scale-csi-fileset
provisioner: spectrumscale.csi.ibm.com
parameters:
    volBackendFs: scale0
    clusterId: "10588301405191899994"
    inodeLimit: "1024"
reclaimPolicy: Delete

Create a pvc as follows:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: scale-fset-pvc
spec:
  accessModes:
  - ReadWriteMany
  resources:
    requests:
      storage: 100m
  storageClassName: ibm-spectrum-scale-csi-fileset

Getting the error:
  Warning  ProvisioningFailed    0s               spectrumscale.csi.ibm.com_ibm-spectrum-scale-csi-provisioner-0_c5ba8032-1e0b-4703-8cfd-ec3ad300e6fb  failed to provision volume with StorageClass "ibm-spectrum-scale-csi-fileset": rpc error: code = Internal desc = Unable to create fileset [pvc-4b32eff0-8edf-4f11-8db6-617ebb96c098] in FS [scale0]. Error [[EFSSG0740C There are not enough resources available to create a new independent file set. The sum of the max inodes for all independent file sets may not exceed the maximum possible inodes for scale0 capacity. EFSSG0740C There are not enough resources available to create a new independent file set. The sum of the max inodes for all independent file sets may not exceed the maximum possible inodes for scale0 capacity.]]

Expected behavior
To obtain the needed PVC
Probably there is a gpfs configuration needed that I missed.

You seem to have exhausted filesystem inodes. You need to increase the inode-limit.
https://www.ibm.com/support/knowledgecenter/STXKQY_5.0.5/com.ibm.spectrum.scale.v5r05.doc/bl1ins_maxnfle.htm


No TimeSpan support in Schema.Parse()

Hi @MarkPflug
There is no TimeSpan support in Schema.Parse(). Is that something that can be changed?
"Duration:TimeSpan"
System.ArgumentException: 'Value does not fall within the expected range.'

Yeah, the schema serialization code is... not great, and could certainly be improved. I just haven't personally had any need for it. Do you actually need to persist the schema as a string, or can you use the builder API instead?
static Schema GetSchema()
{
	return
		new Schema.Builder()
		.Add<int>("Id")
		.Add<string>("Description")
		.Add<DateTime>("StartTime")
		.Add<TimeSpan>("Duration")
		.Build();
}

The Schema type itself isn't restricted in the types it can express, only the serializer code behind the Parse method.

Thanks for the suggestion. I'm unable to use that Schema.Builder() implementation as I persist the schema in a DB then at runtime determine which schema applies to the file then build the string to pass into Schema.Parse().
However, in having another look at how it all fits together I saw that I could pass in an IEnumerable<DbColumn> to the constructor of  CsvSchema. I changed my "column details" class to inherit DBColumn and then I basically had an IEnumerable<DbColumn> ready to use. So, I've gone with that approach instead and now don't need to use Schema.Builder().


NOTICKET Corrections to README

Just some corrections to the readme.

Changed the import location to the npm module
Changed the example options argument to object.

Many thanks, much appreciated!


Registration doesn't login

When first registering, an error message appears and the system doesn't log in.

Fixed


Provide a System simulation adapter for zebra developments

One solution for providing a degree of introspection of a zebradevice on its own components.
This generalises Adapters and provides a SystemSimulationView which an adapter may use as a "device". This view allows some interaction with the SystemSimulation component while obscuring access to the component logic. The SystemSimulationView provides references to the components and the wiring of the SystemSimulationComponent, and the SystemSimulationAdapter allows basic querying of these.
There is a ZebraAdapter for @DiamondJoseph as an idea of where the zebra work with the register etc can begin. I will remove this before merging.

Closed in favour of #174


weakref / transient

the class PackedCoordinateSequence uses a transient SoftReference. This might be tricky to convert correctly with WeakRef in typescript. It would be possible to provide an alternative implementation. That being said, the jsts implementation is missing this file altogether. @bjornharrtell do you know why that is the case? Is the PackedCoordinateSequence and PackedCoordinateSequenceFactory not needed in jsts?
Also I am a little confused why this line does not cause an error because the file does not exist:
https://github.com/bjornharrtell/jsts/blob/e18f6e86c4ba9f7cda3cbce39b0e590625982c43/src/org/locationtech/jts/geom/impl/PackedCoordinateSequenceFactory.js#L6

I think PackedCoordinateSequence is an opt in alternative memory model for coordinates that I never considered. It has like you suspect probably never been in working order and I think it is rarely used also upstream.


Add JEMT code to Research

This is the code about "joint embedding for machine translation", originally in NLP model repos.

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


Add @tompohys to VOTING_MEMBERS.md

Hi, thanks!

For the voting system I will need your email. I sent you a message in the OSMUS slack...


Github preview deploy

Abstract
let's see if it works

Testing
To test this PR, it's suggested to attempt these user flows, or variations of these:

Step 1
Step 2
Step 3

If any errors are found, the PR works unexpectedly, or you have viable suggestions to improve the UX or functionality of the PR, let me know!

Closing as this was a test


feat(linter): report side effect for array element

#2684
#2683  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @mysteryven and the rest of your teammates on  Graphite

Merge activity

Mar 11, 11:04 PM EDT: @Boshen started a stack merge that includes this pull request via Graphite.


feat: Custom actions and shortcuts

This PR allows registering custom actions from anywhere: the Excalidraw React component; ExcalidrawElement subtypes; extensions; plugins, etc.  This PR also allows registering custom shortcut keys from anywhere.
Custom actions are conditionally enabled, and standard actions may be conditionally disabled.
Regression tests are included.
#5655 is used by #2993 et al.

I am thinking whether we should allow registering custom shortcuts for a specific action instead ? As shortcuts would be for some action and will also help in updating shortcuts for existing actions as well.
cc @dwelle

I am thinking whether we should allow registering custom shortcuts for a specific action instead ? As shortcuts would be for some action and will also help in updating shortcuts for existing actions as well. cc @dwelle

I updated this PR to provide custom actions as well.  @ad1992 Could you elaborate on your comment?  cc @dwelle

This is not the PR you are looking for; see #2993 instead.


Combine loggers to one

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.regression/462/
Test FAILed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.regression/463/
Test PASSed.

Current coverage is 63.09%

Merging #172 into master will increase coverage by +0.12% as of 7c95f7c

@@            master    #172   diff @@
======================================
  Files           40      40
  Stmts         2752    2742    -10
  Branches       318     316     -2
  Methods          0       0
======================================
- Hit           1733    1730     -3
- Partial         58      59     +1
+ Missed         961     953     -8

Review entire Coverage Diff as of 7c95f7c

Powered by Codecov. Updated on successful CI builds.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.regression/464/
Test PASSed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.regression/472/
Test PASSed.

!test

Refer to this link for build results (access rights to CI server needed):
http://jenkins.2gis.local/job/vmmaster.regression/473/
Test PASSed.

!test

!test

@z00sts #182 здесь объединил и переделал логгер


Mediator Load testing

Mediator load testing activities supporting/in parallel to #66

Wade got the Askar Mediator running this morning and ran a pile of tests -- great results!  He only crashed the load generator -- AFAIK -- no fails.  @WadeBarnes can fill in the details but very positive results.

Example load test results can be found here; https://github.com/bcgov/DITP-DevOps/issues/68#issuecomment-1509093290

@cvarjao @swcurran regarding the load testing exercise, @rajpalc7 indicates he has the load testing setup ready on his machine, but that is all we need for now. Would you be able to confirm whether additional testing activities are required (and what the expected outcome is)?

@usingtechnology is working on a way to run the mediator with metrics collection (ELK Stack) active, so we can learn more about what is going on within the mediator.  @Jsyro is also working on a configuration to add Redis to the mediator, and we hope to be able to combine the efforts - do an apples to apples performance comparison to an instance with/without Redis.

Thank you @swcurran. It sounds like @rajpalc7 can then stand on-hold if anything becomes necessary, but nothing specific is required from him at this time.


Deployment keys extended usage

Hello,
Maybe it would be very useful to add a feature to Gogs that would allow Profile-wide and Organization-wide deployment keys (Eg SSH keys that would have read-only access to an entity complete list of repos).
The business logic would be to allow duplicate SSH keys across entities.
What do you guys think?
Gogs version <IP_ADDRESS>6 Beta from docker image.
Still problematic in <IP_ADDRESS>7 Beta #develop.

The business logic would be to allow duplicate SSH keys across entities.

This should be a big concern according to currently implementation in Gogs.

I rechecked that Gogs does allow duplication for deploy keys.


charm not using dex-oidc-config data

Bug Description
Hi team,
I have a Kubeflow 1.9 deployment with juju 3.5. My dex-auth connectors config contains all the information and dex-auth is related to the oidc-gatekeeper. But when I try to open a page I can see in the redirect url link the default variables being used instead of the ones in the connectors config.  Initiating OIDC Authorization Code flow..." ip=<IP_ADDRESS> request=/
2024-09-25T08:45:04.951Z [oidc-authservice] time="2024-09-25T08:45:04Z" level=info msg="URI is whitelisted. Accepted without authorization." ip=<IP_ADDRESS> request="/dex/auth?client_id=authservice-oidc&redirect_uri=%2Fauthservice%2Foidc%2Fcallback&response_type=code&scope=openid+profile+email+groups&state=MTcyNzI1MzkwNHxOd3dBTkZSV1Jrb3pUa1V5UWtWSU0waFpTRlZTUkZveVVFVlZVMHhXUkVkTFJsSTNSalJYVEUxUlRsQllSVTVYVkRWUVRrUklVVUU9fE45Ffk8U5aywM0qRjlDL8TdfWsuLkJMZLUe3yVR1uJw"
2024-09-25T08:45:26.538Z [pebble] GET /v1/notices?after=2024-09-25T08%3A44%3A56.530360069Z&timeout=30s 30.000142068s 200
2024-09-25T08:45:56.539Z [pebble] GET /v1/notices?after=2024-09-25T08%3A44%3A56.530360069Z&timeout=30s 30.000625933s 200
2024-09-25T08:46:26.539Z [pebble] GET /v1/notices?after=2024-09-25T08%3A44%3A56.530360069Z&timeout=30s 30.000156663s 200
2024-09-25T08:46:56.540Z [pebble] GET /v1/notices?after=2024-09-25T08%3A44%3A56.530360069Z&timeout=30s 30.000466835s 200
2024-09-25T08:47:26.540Z [pebble] GET /v1/notices?after=2024-09-25T08%3A44%3A56.530360069Z&timeout=30s 30.000187235s 200
2024-09-25T08:47:56.542Z [pebble] GET /v1/notices?after=2024-09-25T08%3A44%3A56.530360069Z&timeout=30s 30.000832014s 200
2024-09-25T08:48:26.543Z [pebble] GET /v1/notices?after=2024-09-25T08%3A44%3A56.530360069Z&timeout=30s 30.000722127s 200
2024-09-25T08:48:56.543Z [pebble] GET /v1/notices?after=2024-09-25T08%3A44%3A56.530360069Z&timeout=30s 30.000471445s 200
2024-09-25T08:49:26.544Z [pebble] GET /v1/notices?after=2024-09-25T08%3A44%3A56.530360069Z&timeout=30s 30.000375432s 200

Additional Context
No response

After syncing with @natalytvinova, we noticed two misconfigurations that may have affected dex and the OIDC client:

issuer-url was set to value: https://kubeflow.<domain>.com/dex/callback, but it should be set to https://kubeflow.<domain>.com/dex - this resolved the first part of the issue.
@natalytvinova then reported the following message appeared after correctly setting up the issuer-url:

The recommendation there was to configure the connector type to match the specific usecase. For example, type can be oidc, google, microsoft, etc..
@natalytvinova can you confirm that after 1 and 2 you are not running into any issues? If so, please feel free to close this issue; otherwise please report back any issues.

@DnPlas yes confirmed! Thank you again

Thanks for confirming @natalytvinova ! I'm closing this issue now as there is no further action. Feel free to re-open or file a new one if you encounter more issues.


BlazeFace - How to use?

Anyhow knows how to use BlazeFace ?
Models published here return an array of 4 tensors as output:
  tf_op_layer_classificators_1: dtype: float32, shape: [1, 512, 1]
  tf_op_layer_classificators_2: dtype: float32, shape: [1, 384, 1]
  tf_op_layer_regressors_1: dtype: float32, shape: [1, 512, 16]
  tf_op_layer_regressors_2: dtype: float32, shape: [1, 384, 16]

While a model published on TFHub
and used in their example app at https://www.npmjs.com/package/@tensorflow-models/blazeface returns a single tensor:
  Identity: dtype: float32, shape: [1, 896, 17]

Why? I already have a working app using model from TFHub, but I'd like to use BlazeFace back-model as it's 4x resolution and much better with smaller faces and only model published on TFHub is front-model.

Just concat each layer. My goal is to quantize it while maintaining accuracy, so I deliberately exclude the final layer of concat.

thanks, that (sort of) worked, just had to be careful with order of concat operations.
but...using same code for front and back model (just changing image inputsize) and it seems back model is far worse than front one - i expected that it would be able to handle smaller faces as advertised by mediapipe, but it only detects faces when it fills 50% of input frame - or i'm doing something wrong (could be issue with predefined anchors?).
do you have any experience with it?

nvm, it was a problem with my math on generating anchors - blazeface-back works just fine!
i'm closing this issue - thanks for your help!


Plan for 1.20 release

@jaegertracing/jaeger-maintainers
Any objections to releasing 1.20 soon? If not, are there any issues that need to be resolved before the release?

I added a few items to the milestone 1.20.0 last week, but back then, I had a bigger time frame to address them. I would then move them to 1.21.0, if we all agree.


Failed to load nodelet and parameters with dev/external trigger branch

System Description
Camera Name and Model: BFS-PGE-13Y3C-C
Operating System: Ubuntu 18.04
Spinnaker Version: <IP_ADDRESS>
ROS Version: Melodic
Computer details
Nvidia Jetson Xavier Development Kit
Processor: ARM 64 bit (v8.2)
RAM: 32 GB
Multiple Cameras Only
How is the triggering setup? all slaves (external trigger)
For Ethernet cameras:
How busy is the network, does the system work in grayscale, at a lower resoultion (binning) and framerate? Network is working, both at lower and higher resolution (binning) and framerate.
Do the cameras work with SpinView? Yes. In particular, it also works with external trigger (1 fps) in Spinview. We can clearly see that the cameras are triggered at the same time. Both cameras set trigger mode on as well as enable line3 (pin 1) and readOut. On the hardware side, both cameras are setup as slaves using the figure under "GPIO Connections for Master/Slave config" in the README. We use an external trigger (https://www.ntnutto.no/prosjekter-items/sentiboard-2/) which act as the master to trigger both cameras. Again, the spinview application confirm that the hardware are connected correctly.
Describe the bug
I am not able to launch the camera driver with external trigger where two cameras are supposed to be slaves. We have tried both the external_trigger branch and the dev branch without luck. We followed issue #89  to compile the driver with nvidia Xavier 18.04 successfully. We have correctly setup the external_trigging_params.yaml file with correct serial numbers and updated the acquisition.launch to find this file and also set external_trigging to true. Also binning are correct. We have also tried other versions of Spinnaker (<IP_ADDRESS> and <IP_ADDRESS>) without luck.
Screenshots
First we tried using the dev branch, where the driver fail to load the nodelet as seen in the screenshot. We can also see that camera IDs and camera aliases are not found. This yields for all the cases we have tried below.

Then, we tried the same branch but now using rosrun instead of roslaunch. As seen in the screenshot below, the driver detects the cameras but segfaults after acquisition. In addition, the parameters in the acquisition.launch file are not set.

Furthermore, we tried roslaunch with external trigging branch and we get the same failure as with dev branch (using roslaunch).

Then, in the same manner, we tried external triggering branch with rosrun and it segfault also here although the cameras are connected. Also note that we have also tried to convert from hexa to integer serial number as shown in #84 with luck (not shown in the screenshot), but it will still fail.

At last, we can see that the master branch works as it should but using only test_params.yaml and a master/slave setup which is not what we want.

So, it seems to be error when loading the nodelet using roslaunch (with external trigging/dev branch). And it seems to be some error loading the parameters using rosrun (and roslaunch). Do you have some ideas what may be wrong?

@oysteinvolden thanks for the detailed bug report.  We have successfully used the external trigger with an x64 laptop. Could you try running your setup with a laptop just to isolate where it is a driver issue or a architecture / system / compile / hardware / memory issue. @jpsnir have you seen segfaults with external trigger?

@oysteinvolden thanks for the detailed bug report.  We have successfully used the external trigger with an x64 laptop. Could you try running your setup with a laptop just to isolate where it is a driver issue or a architecture / system / compile / hardware / memory issue. @jpsnir have you seen segfaults with external trigger?

I tried the dev branch with x86 laptop (Ubuntu 18.04 / ROS melodic) and it actually works after commenting a couple of lines, mostly ROS ASSERTION. This was verified by launching two rqt_image_view so we can easily see that the cameras are triggered at 1 fps. I used Spinnaker <IP_ADDRESS> at the x86 laptop as well. See screenshot below.

I retried the dev branch on the Jetson Xavier using the exact same configuration. I got however the same result as before. I looked into capture.cpp and it seems like the parameters are not set as earlier mentioned. In particular, everywhere nh_pvt_getParam() are used in the code. Hence, relevant parameters such as external trigging are not set correctly (default value) which again will propagate new errors using external trigging setup.
Do you have some ideas why the parameters from the launch file are not detected in capture.cpp? This yields for bot external trigging and dev branch, but not master branch using the Jetson Xavier.
Btw, both x86 laptop and x64 (jetson) use gcc 7.5.0 compiler.

I tried the dev branch with x86 laptop (Ubuntu 18.04 / ROS melodic) and it actually works after commenting a couple of lines, mostly ROS ASSERTION. This was verified by launching two rqt_image_view so we can easily see that the cameras are triggered at 1 fps. I used Spinnaker <IP_ADDRESS> at the x86 laptop as well. See screenshot below.

I retried the dev branch on the Jetson Xavier using the exact same configuration. I got however the same result as before. I looked into capture.cpp and it seems like the parameters are not set as earlier mentioned. In particular, everywhere nh_pvt_getParam() are used in the code. Hence, relevant parameters such as external trigging are not set correctly (default value) which again will propagate new errors using external trigging setup.
Do you have some ideas why the parameters from the launch file are not detected in capture.cpp? This yields for bot external trigging and dev branch, but not master branch using the Jetson Xavier.
Btw, both x86 laptop and x64 (jetson) use gcc 7.5.0 compiler.

Finally it works now. The main issue seems to be that "cam_aliases" and "cam_ids" are not found by the getParam() function at line 321 and 329 in capture.cpp. I ended up commenting line 321-339 in capture.cpp and hardcode the cam ids / cam aliases below line 339 in capture.cpp. See screenshot of the capture.cpp file below.

It seems like it is only the parameters from the external_trigger_params.yaml file that are not detected (without the modification above), while all the other parameters in acquisition.launch will be detected when cam ids / cam aliases are found.

Finally it works now. The main issue seems to be that "cam_aliases" and "cam_ids" are not found by the getParam() function at line 321 and 329 in capture.cpp. I ended up commenting line 321-339 in capture.cpp and hardcode the cam ids / cam aliases below line 339 in capture.cpp. See screenshot of the capture.cpp file below.

It seems like it is only the parameters from the external_trigger_params.yaml file that are not detected (without the modification above), while all the other parameters in acquisition.launch will be detected when cam ids / cam aliases are found.

@oysteinvolden roslaunch loads the config from the yaml file.  Are you sure there are no issue with the formatting in the yaml files. You can try parsing the file using python or another yaml file parser to be sure. Can you share your config file?
Also, a little nitpick, it better to copy pase code / terminal output instead of putting screenshots.  You can use code blocks <> so that it formats and scrolls correctly.  That way you can send the full information instead of just the last screen.
Glad, that you were able to get it to work.

@oysteinvolden roslaunch loads the config from the yaml file.  Are you sure there are no issue with the formatting in the yaml files. You can try parsing the file using python or another yaml file parser to be sure. Can you share your config file?
Also, a little nitpick, it better to copy pase code / terminal output instead of putting screenshots.  You can use code blocks <> so that it formats and scrolls correctly.  That way you can send the full information instead of just the last screen.
Glad, that you were able to get it to work.

Sorry for the screenshots.  The external_trigger_params.yaml file can be seen below.
`cam_ids:

19176570
19176568
cam_aliases:
cam0
cam1
skip: 20
delay: 1.0

flip_horizontal:

false

flip_vertical:

false

#Assign all the follwing via launch file to prevent confusion and conflict
#save_path: ~/projects/data
#save_type: .bmp #binary or .tiff or .bmp
#binning: 1 # going from 2 to 1 requires cameras to be unplugged and replugged
#color: false
#frames: 50
#soft_framerate: 4 # this frame rate reflects to the software frame rate set using ros::rate
#exp: 997
#to_ros: true  #When to_ros is not selected, but live is selected, pressing 'space' exports single image to ROS
`
I cannot see what is wrong with the file, but I can try to use a yaml file parser. Do you see any errors? The serial numbers are correct.

Sorry for the screenshots.  The external_trigger_params.yaml file can be seen below.
`cam_ids:

19176570
19176568
cam_aliases:
cam0
cam1
skip: 20
delay: 1.0

flip_horizontal:

false

flip_vertical:

false

#Assign all the follwing via launch file to prevent confusion and conflict
#save_path: ~/projects/data
#save_type: .bmp #binary or .tiff or .bmp
#binning: 1 # going from 2 to 1 requires cameras to be unplugged and replugged
#color: false
#frames: 50
#soft_framerate: 4 # this frame rate reflects to the software frame rate set using ros::rate
#exp: 997
#to_ros: true  #When to_ros is not selected, but live is selected, pressing 'space' exports single image to ROS
`
I cannot see what is wrong with the file, but I can try to use a yaml file parser. Do you see any errors? The serial numbers are correct.

Yes I agree, I don't see any obvious issue with the file.  It is just surprising that the code works fine on your x86 system and not on the Jetson. Just to confirm, are using roslaunch or rosrun to launch the nodes?
Also can you paste the actual output when the node fails to read the params. You can use ```  ``` for multiline code blocks.

Yes I agree, I don't see any obvious issue with the file.  It is just surprising that the code works fine on your x86 system and not on the Jetson. Just to confirm, are using roslaunch or rosrun to launch the nodes?
Also can you paste the actual output when the node fails to read the params. You can use ```  ``` for multiline code blocks.

In my final setup with external trigger in dev branch I used roslaunch to launch the node. I don't have the Nvidia device in front of me now, but they are pretty much summarized in the screenshots above. If we focus on the dev brench (which works now), you can see the actual output in the two upper screenshots of the initial issue (the first for roslaunch and the second for rosrun). Hence, we get the "failed to load nodelet" failure when the node fails to read external_trigger_params.yaml using roslaunch and a segfault after "*** ACQUISITION ***" when using rosrun.

Reading the yaml is done outside the code.  Roslaunch reads there files and loads the parameters to the ROS parameter server.  Our node reads it from the parameter server.  Does your acquisition.launch point to the correct .yaml file?  You can also check if it is read into the ros parameter server by running rosparam list, you might have to start a separate roscore before running the launch file so that the ros master doesn't close when the node seg faults.

Reading the yaml is done outside the node. Roslaunch reads the yaml file and loads the parameters to the ROS parameter server. Our node reads it from the parameter server. You could check if the file is being read into the ROS parameter server by running rosparam list, you might have to start a separate roscore before running the launch file so that the ros master doesn't close when the node seg faults.


Add a method to grab the Leaflet object from a DOMNode

This is a feature request.
Indeed, it would be great to be able to grab the Leaflet object of an existing map if you only know it's class/id and so, if you have its DOMNode.
var my_map = document.getElementById("mymap");
L.getMap(my_map).getCenter()

I don't think this is feasible right now - the implementation of _initContainer in L.Map does not store a reference to the L.Map instance in the HTMLElement. Furthermore, there is no namespace-wide index of map instances to their container HTMLElements.
I'm also afraid that such a feature might create regressions about memory leaks, i.e. circular references from a map to its container and #5774 all over again.
What's the use case for this?

We wanted to work with a map which was initialized by a WordPress plugin (code we can't edit) inside a closure (nowadays, due to jQuery and co, almost everything is thanksfully done in closures). In such a situation, there is no way to access the Leaflet object.

For example, Vue.js stores its object in DOMNode __vue__ property. This way, you can acccess the object using a simple document.getElementById('MY_ID').__vue__.

Hi @tristanleboss,
You would probably be interested in that post on SO:
https://stackoverflow.com/questions/45412056/find-leaflet-map-object-after-initialisation/45435508#45435508
The idea is to setup a map initialization hook where you can store a reference to the map.
In your case where you want to store the reference on the DOM node itself, you could do:
L.Map.addInitHook(function () {
  // Store a reference of the Leaflet map object on the map container,
  // so that it could be retrieved from DOM selection.
  // https://leafletjs.com/reference-1.3.4.html#map-getcontainer
  this.getContainer()._leaflet_map = this;
});

Live example: https://plnkr.co/edit/iCgbRjW4aymAjoVoicZQ?p=preview
As explained by @IvanSanchez, unfortunately generalizing this approach might create memory leaks in certain use cases, especially on older browsers.
Therefore I do not think we will be able to implement such feature in Leaflet core, and I am closing this Feature Request as such.
But feel free to use it for your particular case: if you never remove the map, you should not face the memory leak issue.
Or more simply, use a global variable, as done in the linked SO post, to avoid circular references.


Spelling test interpreter

This fixes some misspellings in Swift test/interpreter, it is split per https://github.com/apple/swift/pull/42421#issuecomment-1101092698

@swift-ci smoke test


Deactivate "compile" and "reload" (StackOverflowError)

"Compile" is still async (this breaks "reload")
"Compile" and "reload" should be exclusive

There's a double reload (first reload with nothing, then it gets compiled and the second reload is ok)

The compile action still triggers too much, see related issue.

"It triggers a recompilation 135 times on each triggering."

That might be a problem

Seeing how buggy this is, I'll just deactivate the feature

Let's talk money, we can pay you to fix this problem. Contact us at<EMAIL_ADDRESS>

Hello @kangarko, thank you for your offer, but I have a time problem, not a money problem. If I ever find time to do this, you'll be the first to know.

Alright thanks!

I'll release a fix in 1.8.0, based on the PR for #246. Tell me if that's what you had in mind @kangarko.

Released in 1.8.0.


Bug: Navigating by tab moves/removes characters

If I use tab to navigate back (shift + tab) and forth via the input fields, the character is moved to the left and finally dropped when they reach the start of the word.

@tmkarlsen Thanks! I just fixed that issue in https://github.com/otacke/h5p-crossword/commit/3de9f18d4310897ec2330c3dfb46063eed4a555f

@tmkarlsen The H5P core team has already released an update containing the fix today.

@otacke Thanks for the update. That is great news!


[1.2.1] Understanding Project Requirements

Issue Details
Description
This main issue is for us to analyze the initial requirements that were given to us from the Project Brief. Afterwards, we will create a list of questions that we feel is needed to asked the Client for more clarification of our requirements.
Goals

Elicitate and analyze the Initial Requirements given to us from the Project Brief.
Generate a list of Clarification Questions to ask the Client to gather more refined requirements.

Success or Completion Criteria

[x] #57
[x] #10

Allocated Time
6 Days
Start Date: 29/08/23, 1800
End Date: 07/09/23, 2359

Issue Comments
Description
Completed the necessary Sub Issues for understanding Project Requirements.
Changes to success or completion criteria? y/n (if y, describe)
No Changes, Criteria Completed.
Start Date: 29/08/23, 1800
End Date: 07/09/23, 2359


Issue with importing the resource "snowflake_database.from_share" into state file

Provider Version
0.59.0
Terraform Version
1.0.3
Describe the bug
Terraform shows difference in plans after successful importing the snowflake database from share. The plans are fine for simple database after import.
Plans looks like destroying the imported database and recreating it. The below are the changes to  "snowflake_database.from_share "
module.test_db.snowflake_database.from_share must be replaced
-/+ resource "snowflake_database" "from_share" {
+ comment                     = "Managed through Terraform.
~ data_retention_time_in_days = 0

from_share                  = {
+ "provider" = "provider.account"
+ "share"    = "share_name"
} # forces replacement
~ id                          = "database_name" -> (known after apply)
name                        = "database_name"
# (1 unchanged attribute hidden)
}

Expected behavior
Imported Database should not be changed or force replaced

Hello,
Still I am facing the issue. If anyone has any suggestions on the above issue. Please add here.

Same on my end. Could you please take a look into it? 🙏

Hey. We will look closely at the database resource in the upcoming weeks as part of https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/ROADMAP.md#our-roadmap. We will discuss how the import should work then.
Be aware that it may be not possible to import the database created from a share correctly. We are limited to SQL statements that can be run against Snowflake. If we can't get information on the database that it was created from share, then it may be impossible to set the state correctly in the current import. We will research what options we have.

Hey @sirishachaparla 👋
The new version (v0.93.0) contains the new database resources. The issue with importing the database from share shouldn't occur there. If you can, please try to migrate to/import the snowflake_shared_database. Closing the ticket as snowflake_database is now representing the standard database and the snowflake_database_old (that was previously snowflake_database) is no longer supported. If you encounter any issues with the new resources, please report a new issue. Thank You.


Uncaught exceptions are silenced if happen in timeframe of skipped test

Possibly related to https://github.com/mochajs/mocha/issues/3740
Steps to Reproduce
describe('test', () => {
  it('test1', () => {
    setTimeout(() => {
      throw new Error('Uncaught');
    }, 3);
  });
  it('test2', function () {
    this.skip();
  });
  it('test3', function () {
    this.skip();
  });
  it('test4', function () {
    this.skip();
  });
});

Expected behavior:
Tests should fail unconditionally
Actual behavior:
In most cases suite passes (there is a race condition,due to which occasionally error gets exposed)
Versions
mocha:  6.1.4
Node.js: 12.3.1
macOS: 10.14.5

Test1 should pass, though the error may get caught outside the test itself (depending on timing).
Recode as async test (using done or Promise) if you want to catch Error from setTimeout.
All other tests should be marked pending regardless.

It's a question of how mocha handles the case, when user misconfigured the test so it results with unhandled exception.
I believe the goal is to expose them to user as errors, in this case it's to doesn't happen, therefore it's a bug.

Which part of my reply are you implying Mocha does incorrectly here? Test1 or the other three?
Your "Expected Behavior" is hard to tell what you expect -- did you mean "all" tests or only the attempted fail of first one?

Which part of my reply are you implying Mocha does incorrectly here

Incorrect is assumption that developers do not make mistakes.
In discussed case, test by mistake was configured that it ends before an actual job it started ends. The left over job additionally raises an uncaught exception (currently silenced by Mocha, therefore developer is left with no clue the tests setup is broken)
I believe Test runner should not silence uncaught exceptions, no matter in what context they exploded, whether it was failed test, pending test, or maybe after all tests were registered as ended.
It general it goes down to rule: unhandled errors should not be silenced

Which is the result when you use --allow-uncaught option?

Fail to understand why you continue to create new issues over the same problem though.
We went through all this in #3917.
If you want it fixed, send a PR.

We went through all this in #3917.

No, it's a different issue.
All things I report are actually issues I discover when working with quite extensive Mocha setup in real world project (currently it comes with four Mocha bug patches, so it behaves reasonably)

Seems like another aspect of same problem -- an uncaught error occurs in asynchronous code run from a synchronous Mocha test.
Notwithstanding whether Mocha is lacking in this department, some chunk of the solution for you would be to write your tests using Mocha's asynchronous API instead...

Which is the result when you use --allow-uncaught option?

In this case it ends with output as:
  test
    ✓ test1
    1) test2

Which indicates an error in test2, but provides no details.
And process exists with 0 success code.
So it's also an invalid outcome

Can you give me a more detailed explanation?
I tested
describe('test', () => {
    it('test1', () => {
      setTimeout(() => {
        throw new Error('Uncaught');
      }, 3);
    });
    it('test2', function () {
        console.log(2)
      this.skip();
    });
    it('test3', function () {
        console.log(3)
      this.skip();
    });
    it('test4', function () {
        console.log(4)
      this.skip();
    });
  });

and result
 test
    ✓ test1
2
    - test2
3
    - test3
4
    - test4

  1 passing (7ms)
  3 pending

/Users/juhongchul/Desktop/dev/test/a.js:4
        throw new Error('Uncaught');
        ^

Error: Uncaught
    at Timeout.setTimeout [as _onTimeout] (/Users/juhongchul/Desktop/dev/test/a.js:4:15)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

is very clear, 1 passing because move to event loop and other things pending
you think 2, 3, 4, and 1 failed?

@wnghdcjfe run it few times, you'll see that in some cases test suite ends with success, not reporting the error.
It happens only when race condition (throw new Error('Uncaught'); being caught between this.skip() and following it run) occurs.
Also the more further tests going, the more likely issue is to occur, try e.g.:

describe("test", () => {
    it("test1", () => {
        setTimeout(() => {
            throw new Error("Uncaught");
        }, 3);
    });
    it("test2", function() {
        this.skip();
    });
    it("test3", function() {
        this.skip();
    });
    it("test4", function() {
        this.skip();
    });
    it("test5", function() {
        this.skip();
    });
    it("test6", function() {
        this.skip();
    });
    it("test7", function() {
        this.skip();
    });
    it("test8", function() {
        this.skip();
    });
    it("test9", function() {
        this.skip();
    });
    it("test10", function() {
        this.skip();
    });
    it("test11", function() {
        this.skip();
    });
});

I found it and i try to fix that
/Users/juhongchul/Desktop/dev/test.js:5
throw new Error("Uncaught");
^
Error: Uncaught
at Timeout.setTimeout [as _onTimeout] (/Users/juhongchul/Desktop/dev/test.js:5:17)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)

I think you sould add done parameter like this
const assert = require('assert');
describe("test", () => {
  it("test1", (done) => {
      setTimeout(() => {
          throw new Error("wow..");
          done();
      }, 3);
  });
  it("test2", function() {
      this.skip();
  });
  it("test3", function() {
      this.skip();
  });
  it("test4", function() {
      this.skip();
  });
  it("test5", function() {
      this.skip();
  });
  it("test6", function() {
      this.skip();
  });
  it("test7", function() {
      this.skip();
  });
  it("test8", function() {
      this.skip();
  });
  it("test9", function() {
      this.skip();
  });
  it("test10", function() {
      this.skip();
  });
  it("test11", function() {
      this.skip();
  });
});

I added done and I tested and the result is..
exactly this
0 passing (17ms)
10 pending
1 failing

test
test1:
Uncaught Error: wow..
at Timeout.setTimeout [as _onTimeout] (test.js:5:17)

the mocha said
ASYNCHRONOUS CODE
Testing asynchronous code with Mocha could not be simpler! Simply invoke the callback when your test is complete. By adding a callback (usually named done) to it(), Mocha will know that it should wait for this function to be called to complete the test. This callback accepts both an Error instance (or subclass thereof) or a falsy value; anything else will cause a failed test.
because setTImeout is a async
thank you your issue.


How to submit index page?

I am unable to submit the index page (ie: "/" - "https://cdn.yoursite.com/") into the Load dialog in Azure or via the API. Obviously, this page is cached by the CDN at "/", but I'm not able to proactively load it. Maybe there's another command? Clearly, the Regex checking valid URLs doesn't handle this, but it probably should.

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

ID: 78647b5d-18f1-f152-908b-b206a3f0b94a
Version Independent ID: c06049c9-91d0-3b0c-2053-57b2188944d0
Content: Pre-load assets on an Azure CDN endpoint
Content Source: articles/cdn/cdn-preload-endpoint.md
Service: cdn
GitHub Login: @mdgattuso
Microsoft Alias: magattus

@lphomiej I do not believe that this is possible, but I am following up now to make sure.

@lphomiej I have confirmed that this is not possible at this time. Typically Pre-Loading assets is for particular pages or media that you suspect are about to get a sudden high volume. Why exact do you want to pre-load your origin?
Also, if you want us to enable this feature in the future, please leave your feedback Here.

@lphomiej We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@TravisCragg-MSFT this seems like an awkward limitation.  We use CDN to cache our static web pages and not being able to load home page is a downfall.  Since localized version of the site use paths such as /en-de/, we are able to load those no problem.  Only option is to purge the root path, which now will leave some user with slower than expected performance.

@matasnizamovas please give your feedback at Azure Networking's feedback.azure.com page.


NotificationHub - server-side interference with APNS headers breaks VOIP notifications

Notification Hubs now try (and fail) to infer the value for apns-push-type
No account is taken of voip bundle ids
There is also no facility in the Test Send facility to specify the apns-push-type for the test message.
This specifically breaks the debugging of VOIP notifications.

Closed as per issue is fixed on the backend


Adds "anticipated" behaviour to lazyLoad options

Adds support for "anticipated" as lazyLoad option which was added as lazyLoad option to slick in version 1.7.1
fixes https://github.com/akiran/react-slick/issues/1939

Bump up! I so need it!

@akiran , could you give us a timeline for this?

push

Hey! Is there any update on this? The "anticipated functionality will be super helpful for us.

bump

@akiran What is the status of this feature? The lazyLoad options in @types/react-slick already incorporate it. This feature aims to improve performance while maintaining an excellent user experience, as the next image will be pre-loaded seamlessly, remaining unnoticed by the user.


docs: updated doc-site to match schema 3.0.0 requirements

#3156

Reviewers
Functional:
Readability:

Changes

updated doc site to match schema 3.0.0 requirements / links / screenshots
removed a couple of unused images
fixed dev env doc minor inconsistency

QA steps (optional)
Notes for Reviewer

@pablo-gar - you may want to take a look at the sc expression image change ...

@pablo-gar - you may want to take a look at the sc expression image change ...

Looks good, was this change just for dimensions?

Looks good, was this change just for dimensions?

No - ethnicity is being renamed to self-reported ethnicity in 3.0.0.

@nayib-jose-gloria - LGTM.


[Bugfix] Enhancement compatibility for create Materialized View

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #10318
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_admit_test

[FE PR Coverage Check]
:disappointed: fail : 9 / 18 (50.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/rule/mv/MVUtils.java
5
14
35.71%
[94, 95, 99, 101, 103, 104, 105, 106, 107]

:large_blue_circle:
com/starrocks/catalog/MaterializedIndexMeta.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/alter/RollupJobV2.java
2
2
100.00%
[]

run starrocks_admit_test

[FE PR Coverage Check]
:disappointed: fail : 9 / 18 (50.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/common/MetaUtils.java
5
14
35.71%
[111, 112, 116, 118, 120, 121, 122, 123, 124]

:large_blue_circle:
com/starrocks/catalog/MaterializedIndexMeta.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/alter/RollupJobV2.java
2
2
100.00%
[]

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

@Mergifyio backport branch-2.4 branch-2.3


Suggestion: Add geolocation bias to places search

Hey there,
The custom Mapbox implementation works great, but one thing that I'm having a bit of a hard time with is the fact that, when searching, destinations in location thousands of kilometers away from me show up, making it hard to filter out the ones close to me that I'm actually interested into.
From what I've researched I've found that mapbox can bias the search results to a certain region. I'm thinking that adding a toggle to bias the search results to the location of the user (+ a certain range, let's say 100km) would go a long way to improving the search result functionality (and also reducing the API calls maybe, due to fewer erroneus searches ?)
Alternatively,  I'm thinking that pasting a Google Maps URL somewhere and extracting the GPS coordinates from that would also work, but maybe I should make a separate issue with this
Thanks for a great app!

In fact, the code is shared and you could actually paste a Google Maps link right into the Navigation search box and it will work too.

Ah, I didn't know that - nicem will come in handy. Does pasting Google Maps links to the "Favorite Destinations" input work as well ?

If you have a (free) Mapbox account, can you play around in the api playground to see if their search api provides the expected results there? I believe I'm sending the right parameters, and the app shows the closest Starbucks for me, so I'm not sure why it's not behaving as expected for you.

I'll play around with it - for me for certain searches it is retrieving one or two POIs close to me, then something way over in Bangladesh. Maybe it's not finding anything in between and falling back on that ?

Indeed, the favorite places are just strings and should work, though ugly!
I can't guarantee the search quality of this service, I apologize 😬

Okay, then I think we can close this issue :D


Allows to change the db with an already existing db

While switching between medInria, MUSIC and MUSIC Viewer on Windows (I don't think I had this behavior on Mac), I had my db location changed every time (db directory = ../organisationName/applicationName). Since my MUSIC Viewer db was new and empty, I wanted to select an already existing db (e.g medInria). But it is impossible because, from the source code, a valid db directory is an empty one.
In this PR, I try to fix that by first checking whether the selected directory contains a db file.
I also removed the "previous db deletion" because one may want to switch between db without deleting it.
Finally, I added a label warning that the changes will be effective after restart of medInria.

Hola chicos, just passing through with my 2 cents (well 2 centavos, I'm in Bolivia): the whole business of moving DB when a new directory is selected seems a little silly. When the DB path is changed, medInria should either just use whatever is there as the new DB, or create a new empty one if nothing was there, but not move the whole DB to the new folder.
If the user wants to move the DB to a new place, he can just use his file manager from his OS, and then update the path when opening medInria the next time. Moving files around is so prone to disaster, medInria should really stay away from that. In your case, @LoicCadour, you would just start MUSIC and MUSIC Viewer, update their DB path to the medInria one, and from then on, all updates to this DB would be shared by all. Solved. Obviously, don't open more than one of these software at once. But that's either managed by @papadop use of single-instance app he implemented a while ago, or if that mecanism is not shared across Music and medInria, maybe add a lock to the DB so that only one app can open it at the time.
...Yes, I'm still watching everything. :eyes:
Well, not really, I just got curious if you lot had managed a new release in my absence, and I ended up reading some pull requests.


Revert "drivers/timer/hpet: Extend qemu workaround"

This reverts commit 4ae44dd71231abb80a45e8dd1d23127c95d61929.
Fixes #32724.  See also: https://github.com/zephyrproject-rtos/zephyr/pull/29618#issuecomment-788950966

Not opposed to merging this, but are we absolutely sure it's actually happening in master and not just on a PR branch, and that this is the sole source?   I'm concerned about voodoo here based on one or two results, basically.  Again, on my build machine this platform is absolutely rock solid; literally no visible failures at all over hundreds of trials.
This particular fix wasn't a common failure mode, but it was the source of actual observed rollover conditions in the z_clock_set_timeout() path.  I'm not opposed to reverting it, really, I just worry we're looking at the wrong thing.

I share your concerns concerns, but https://buildkite.com/zephyr/zephyr/builds/22543#185a9bbb-68d0-4c47-8b58-73e4a4d39059 shows failures on these configurations:
qemu_x86_64_nokpti        tests/kernel/workq/work/kernel.work.api
qemu_x86_64_nokpti        tests/kernel/lifo/lifo_usage/kernel.lifo.usage
qemu_x86_64_nokpti        tests/kernel/fifo/fifo_api/kernel.fifo
qemu_x86_64               tests/kernel/workq/work/kernel.work.api
qemu_x86_64               tests/kernel/smp/kernel.multiprocessing.smp
qemu_x86_64               tests/kernel/mem_slab/mslab_concept/kernel.memory_slabs.concept
qemu_x86_64               tests/kernel/lifo/lifo_usage/kernel.lifo.usage
qemu_x86_64               tests/kernel/common/kernel.common.misra
qemu_x86_64_nokpti        tests/kernel/lifo/lifo_usage/kernel.lifo.usage
qemu_x86_64_nokpti        tests/kernel/fifo/fifo_api/kernel.fifo
qemu_x86_64               tests/kernel/workq/work/kernel.work.api
qemu_x86_64               tests/kernel/smp/kernel.multiprocessing.smp
qemu_x86_64               tests/kernel/lifo/lifo_usage/kernel.lifo.usage
qemu_x86_64               tests/kernel/workq/work/kernel.work.api
qemu_x86_64               tests/kernel/smp/kernel.multiprocessing.smp
qemu_x86_64               tests/kernel/workq/work/kernel.work.api

many of which should not have been affected by the k_work changes.  They go away with this patch, and were never observed until the reverted commit was added to master.
I'd be more comfortable if we could find the similar failures on other PRs, but since they're intermittent I think people just forced a re-run and they disappeared.

FWIW: I just tried the reversion on my rig: 22 runs with one failure (seemingly timing-related thing), which seems acceptable.  I also tried a variant with the entire workaround removed (including the pre-existing one) and got no failures in 8 more runs.  So there's really no reason I can see not to merge this this given that it's just a workaround for testing configurations anyway.


[Splash Screen] Dual Screen Problem

Extension name
SplashScreen
Feature Description
Hi,
I use a dual screen setup and every time I run a game the splash screen shows up in screen #1 while the game is running on screen #2, how can I set up Splash Screen to always shows in Screen#2?
Screenshots
No response

The splash screen window will display in the current main screen in your PC, I assume that's number 1 for you? If that's the case then I or someone else would need to look and see how it can be displayed in the non primary screen.

have it show on the second screen or give the user the option to choose where to show it, that would be great!
I really don't know if this requires opening another topic, but being able to control the time SplashScreen takes to make the transition between Playnite and the emulators would also be a wonderful addition.

have it show on the second screen or give the user the option to choose where to show it, that would be great!
I really don't know if this requires opening another topic, but being able to control the time SplashScreen takes to make the transition between Playnite and the emulators would also be a wonderful addition.

Hi,
I have a monitor as my first screen and a television as my second screen. I play the games in the second screen.
I run Playnite in Fullscreen mode on the second screen but splash screen shows the splash on the first screen


[DOC] Correct warning about performance

This updates the warning in the vLLM documentation to approriately reflect the work #6612.
FIX #6653
Note: This should only be merged to update docs after vLLM 0.5.3 is released which is tomorrow according to #6434.

Is this still relevant?

Is this still relevant?

Yes.

Please resolve the merge conflicts, then I can enable auto-merge


Consider removing PR description from merge commit message

The JIRA integration didn't work, and it causes @-mentioned people to get emailed twice.

Added in https://github.com/floatplane/git_pr/pull/28 so just revert that


[e-Money] Bug fix: authority_key column prevents periodic ops from updating the table

…GasPrices and remove db.updateEMoneyGasPrices
fix #213 #202

Description

Checklist

[x] Targeted PR against correct branch.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Wrote unit tests.
[x] Re-reviewed Files changed in the Github PR explorer.

hello @MonikaCat, this morning I realized that my periodic operations handler for gas prices would not work because it only handles UPDATE table(authority_key can only be obtained from the genesis, so the periodic operations could only use UPDATE). However there is no row to be UPDATEd because genesis was not parsed... the UPDATE then will fall in error.
So I discussed with @ryuash and she confirmed that they won't need the authority_key so I removed it from the type struct as well as from the table. Now handle_genesis and handle_periodic_operations both use INSERT INTO ON CONFLICT so it will prevent the error.

@huichiaotsou Can we leave the authority_key field and still use the one_row_id? I think other people might want to have that data (i.e. if they are customizing BigDipper).
Also, will this close #202 as well? If so, can you add it to the description please?

@huichiaotsou Can we leave the authority_key field and still use the one_row_id? I think other people might want to have that data (i.e. if they are customizing BigDipper).

Sure, I will add this col in the table and still include insert of this data from handle_genesis
as for PeriodicOperations I will then leave authority_key un-updated.

Also, will this close #202 as well? If so, can you add it to the description please?
OK added!

Sure, I will add this col in the table and still include insert of this data from handle_genesis as for PeriodicOperations I will then leave authority_key un-updated.

Hmm not sure I quite understand then. Isn't this key retrieved from the querier that gets the gas prices? If not then we can leave it out. I thought that is was returned by the querier cause it would have made sense to indicate who was the last one updating the prices

Sure, I will add this col in the table and still include insert of this data from handle_genesis as for PeriodicOperations I will then leave authority_key un-updated.

Hmm not sure I quite understand then. Isn't this key retrieved from the querier that gets the gas prices? If not then we can leave it out. I thought that is was returned by the querier cause it would have made sense to indicate who was the last one updating the prices

😆  no, the query only returns gas prices

laughing no, the query only returns gas prices but no authority key

Ok then we can leave it as it is. If the work has done, you can mark this PR as "Ready for review" :smile:

laughing no, the query only returns gas prices but no authority key

Ok then we can leave it as it is. If the work has done, you can mark this PR as "Ready for review" 😄

perfect ! just switched


Content of webpage doesn't look properly

The content of Windows UWP overview webpage doesn't look properly in maximized browser window, some horizontal content of webpage is out of browsing area even webpage doesn't show horizontal scrolling bar to access that content.
Link of  Page
https://docs.microsoft.com/en-us/windows/uwp/get-started/
Make them look properly even in maximized browser window.
Maximized Browser window

OS: Windows version 1809 (17763)
Browser: Edge, Opera

@HaDayaGo I create a internal bug to track it. https://icm.ad.msft.net/imp/v3/incidents/details/89940377/home

@QuinnRadich Can you take a look at this bug?

Apologies for the delayed response to this issue. I believe this issue was always tied to larger site engineering and architecture settings on docs.microsoft.com, and wasn't related to the page in question. I've gone through and checked the page as it stands now, and I haven't been able to reproduce this issue.
If this is still noticeable now after all this time, I'd encourage you to submit a new issue stating as such, and I'll check again and inquire with our docs platform engineering team. Thank you.


Create documentation for setup of services

Documentation to easily set up a custom relay is needed. Readthedocs and github README would be good places to have it updated
Maybe some refactor to the code would also be needed to allow an easy set up

Updated issue


Regression in 2.12. Pathfinding

What version are you using?
Noticed regression in 2.12. (works fine in 2.11.)
What did you do?
Invoked /paths/strict-send in 2.12
What did you expect to see?
Results similar to /paths/strict-send in 2.11 and earlier versions
What did you see instead?
It looks like 2.12. started omitting results in which the source asset and destination asset are the same.
When invoking, e.g. https://horizon.stellar.org/paths/strict-send?destination_account=GASKYWPPQ2VSO6KNIPIRVXMSSDGZLYZQ67CDTLVXOXYDG26SPZ66EDCQ&source_asset_type=credit_alphanum4&source_asset_code=BTC&source_asset_issuer=GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF&source_amount=0.0005953 the response used to include a result with the source asset BTC:GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF being the destination asset at the same time.
The below result item is missing in 2.12. (but exists in 2.11.). The asset exists on the destination account but is missing as a corresponding result in the path finding response.
      {
        "source_asset_type": "credit_alphanum4",
        "source_asset_code": "BTC",
        "source_asset_issuer": "GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF",
        "source_amount": "0.0005953",
        "destination_asset_type": "credit_alphanum4",
        "destination_asset_code": "BTC",
        "destination_asset_issuer": "GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF",
        "destination_amount": "0.0005953",
        "path": []
      },

The above result item is included in 2.11. (compare: https://horizon.stellar.coinqvest.com/paths/strict-send?destination_account=GASKYWPPQ2VSO6KNIPIRVXMSSDGZLYZQ67CDTLVXOXYDG26SPZ66EDCQ&source_asset_type=credit_alphanum4&source_asset_code=BTC&source_asset_issuer=GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF&source_amount=0.0005953).
Unfortunately this broke a few things in our application, which currently depends on the result item being present.  Can we make the item re-appear in the list?

ok, it looks like normal payments are a subset of path payments. we can include these in the response

I can imagine that other people used this to detect arbitrage opportunities. I am almost sure that this used to find them. It's irrelevant for our individual use case though. We are happy if the path is [] for this type of pair, as long as all assets on the destination account exist in the response.


Change Private Message Reply

Any way in which we can change the PM message reply to something funny or anything really.

Only if you edit the source. Although I don't really see why wouldn't it be externalized to config.json for example.
Thanks for the suggestion

thanks for considering it


Updating Typography Examples to ES6 standards

Changes
All declarations with var have been changed to let and class syntax has been added where useful.
Issue Solved
Fixes #333

You meant adding the let statements when declaring called in the loop right? Did that.


process images and store in media bus

:tada: This issue has been resolved in version 1.3.0 :tada:
The release is available on:

v1.3.0
v1.3.0
GitHub release

Your semantic-release bot :package::rocket: