Pre AQAvit Triage for jdk20

JDK20 jenkins build pipeline https://ci.adoptium.net/job/build-scripts/job/openjdk20-pipeline/161/ + Grid
Release Summary Report for openjdk20-pipeline
Report generated at: Mon, 13 Mar 2023 19:28:42 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/openjdk20-pipeline/161/
Started by upstream project "build-scripts/weekly-openjdk20-pipeline" build number 36 at 3/11/2023, 6:30:08 PM

Platforms with AQA Failures
Triage Details/Actions
Post-triage Status

details

details

details

details

details

details

details

details

details

details

details

Sanity.openjdk_aarch64_linux:
Running on [test-docker-ubuntu2004-armv8l-3](https://ci.adoptium.net/computer/test-docker-ubuntu2004-armv8l-3/) in /home/jenkins/workspace/Test_openjdk20_hs_sanity.openjdk_aarch64_linux

23:52:07  ERROR: Cannot delete workspace :Malformed input or input contains unmappable characters: /home/jenkins/workspace/Test_openjdk20_hs_sanity.openjdk_aarch64_linux/aqa-tests/TKG/output_16761595797474/jdk_lang_0/work/scratch/2/TestLambdaFileEncodingSerialization$ABC������.class

Test should be excluded on all platforms https://github.com/adoptium/infrastructure/issues/2630#issuecomment-1184718299, not sure for jdk20 it's only excluded on arm. Will update.

Release Summary Report for openjdk20-pipeline
Report generated at: Tue, 14 Mar 2023 20:13:59 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/openjdk20-pipeline/161/
Started by upstream project "build-scripts/weekly-openjdk20-pipeline" build number 36 at 3/11/2023, 6:30:08 PM

create_installer_mac ❌ undefined ❌
create_installer_windows ❌ undefined ❌
jdk20-aix-ppc64-temurin ❌ ABORTED ❌
jdk20-aix-ppc64-temurin_SmokeTests ⚠ UNSTABLE ⚠
jdk20-alpine-linux-x64-temurin ⚠ UNSTABLE ⚠
jdk20-linux-aarch64-temurin ❌ FAILURE ❌
jdk20-linux-arm-temurin ⚠ UNSTABLE ⚠
jdk20-linux-ppc64le-temurin ⚠ UNSTABLE ⚠
jdk20-linux-riscv64-temurin ❌ ABORTED ❌
jdk20-linux-riscv64-temurin_SmokeTests ❌ ABORTED ❌
jdk20-linux-s390x-temurin ❌ ABORTED ❌
jdk20-linux-x64-temurin ⚠ UNSTABLE ⚠
jdk20-mac-aarch64-temurin ❌ FAILURE ❌
jdk20-mac-x64-temurin ❌ FAILURE ❌
jdk20-windows-x64-temurin ❌ FAILURE ❌
sign_build ❌ undefined ❌
sign_installer ❌ undefined ❌
sign_temurin_gpg ❌ undefined ❌

Test_openjdk20_hs_extended.openjdk_aarch64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_security3_1 => deep history 0/3 passed | possible issues
jdk_security_infra_1 => deep history 0/3 passed | possible issues
jdk_security_infra_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_aarch64_mac ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_aarch64_mac_testList_0 ⚠ UNSTABLE ⚠
jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_security3_1 => deep history 0/3 passed | possible issues
jdk_management_0 => deep history 0/3 passed | possible issues
jdk_management_1 => deep history 0/3 passed | possible issues
jdk_security_infra_0 => deep history 0/3 passed | possible issues
jdk_security_infra_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_arm_linux ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_arm_linux_testList_1 ⚠ UNSTABLE ⚠
jdk_other_2 => deep history 0/3 passed | possible issues
jvm_compiler_2 => deep history 0/3 passed | possible issues
jdk_security3_2 => deep history 0/3 passed | possible issues
jdk_security_infra_2 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_ppc64_aix ❌ ABORTED ❌
Test_openjdk20_hs_extended.openjdk_ppc64_aix_testList_0 ❌ ABORTED ❌
jdk_other_0 => deep history 0/3 passed | possible issues
jdk_net_0 => deep history 0/3 passed | possible issues
jdk_net_1 => deep history 0/3 passed | possible issues
jdk_security2_1 => deep history 0/3 passed | possible issues
jdk_security3_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_ppc64_aix_testList_1 ⚠ UNSTABLE ⚠
jdk_other_1 => deep history 0/3 passed | possible issues
jdk_nio_0 => deep history 0/3 passed | possible issues
jdk_nio_1 => deep history 0/3 passed | possible issues
jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_security4_0 => deep history 0/3 passed | possible issues
jdk_security4_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_ppc64le_linux_testList_0 ⚠ UNSTABLE ⚠
jvm_compiler_0 => deep history 2/3 passed | possible issues
jvm_compiler_1 => deep history 2/3 passed | possible issues
jdk_security_infra_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_ppc64le_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_security3_1 => deep history 0/3 passed | possible issues
jdk_management_0 => deep history 1/3 passed | possible issues
jdk_management_1 => deep history 1/3 passed | possible issues
jdk_tools_0 => deep history 1/3 passed | possible issues
jdk_security_infra_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_riscv64_linux ❌ ABORTED ❌
Test_openjdk20_hs_extended.openjdk_riscv64_linux_testList_0 ❌ ABORTED ❌
jvm_compiler_1 => deep history 0/2 passed | possible issues
jvm_compiler_0 => deep history 0/2 passed | possible issues
jdk_security4_1 => deep history 1/2 passed | possible issues
Test_openjdk20_hs_extended.openjdk_riscv64_linux_testList_1 ❌ ABORTED ❌
Test_openjdk20_hs_extended.openjdk_riscv64_linux_testList_2 ❌ ABORTED ❌
Test_openjdk20_hs_extended.openjdk_s390x_linux ❌ ABORTED ❌
Test_openjdk20_hs_extended.openjdk_s390x_linux_testList_0 ⚠ UNSTABLE ⚠
jvm_compiler_0 => deep history 0/3 passed | possible issues
jvm_compiler_1 => deep history 0/3 passed | possible issues
jdk_tools_1 => deep history 0/3 passed | possible issues
jdk_other_0 => deep history 0/3 passed | possible issues
jdk_security_infra_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_s390x_linux_testList_1 ❌ ABORTED ❌
jdk_other_1 => deep history 0/3 passed | possible issues
jdk_net_1 => deep history 2/3 passed | possible issues
jdk_nio_1 => deep history 2/3 passed | possible issues
jdk_rmi_0 => deep history 2/3 passed | possible issues
jdk_jfr_0 => deep history 2/3 passed | possible issues
jdk_jfr_1 => deep history 2/3 passed | possible issues
jdk_jdi_1 => deep history 2/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_s390x_linux_testList_2 ❌ FAILURE ❌
Test_openjdk20_hs_extended.openjdk_x86-64_alpine-linux ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_x86-64_alpine-linux_testList_0 ⚠ UNSTABLE ⚠
jdk_security4_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_x86-64_alpine-linux_testList_1 ⚠ UNSTABLE ⚠
jdk_security3_0 => deep history 0/2 passed | possible issues
jdk_build_1 => deep history 0/2 passed | possible issues
jdk_build_0 => deep history 0/2 passed | possible issues
jdk_security_infra_0 => deep history 0/2 passed | possible issues
jdk_security4_0 => deep history 0/2 passed | possible issues
jdk_security_infra_1 => deep history 0/2 passed | possible issues
Test_openjdk20_hs_extended.openjdk_x86-64_alpine-linux_testList_2 ⚠ UNSTABLE ⚠
jdk_net_0 => deep history 1/2 passed | possible issues
jdk_security3_1 => deep history 0/2 passed | possible issues
Test_openjdk20_hs_extended.openjdk_x86-64_linux ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_x86-64_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_security_infra_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_x86-64_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_net_0 => deep history 0/3 passed | possible issues
jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_security_infra_0 => deep history 0/3 passed | possible issues
jdk_security3_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_x86-64_mac ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_x86-64_mac_testList_1 ⚠ UNSTABLE ⚠
jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_security_infra_0 => deep history 0/3 passed | possible issues
jdk_security_infra_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_x86-64_mac_testList_2 ⚠ UNSTABLE ⚠
jdk_security3_1 => deep history 0/3 passed | possible issues
jdk_management_0 => deep history 0/3 passed | possible issues
jdk_management_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_x86-64_windows ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_x86-64_windows_testList_0 ⚠ UNSTABLE ⚠
jdk_security_infra_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_x86-64_windows_testList_2 ⚠ UNSTABLE ⚠
jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_tools_0 => deep history 0/3 passed | possible issues
jdk_security3_1 => deep history 0/3 passed | possible issues
jdk_security_infra_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.system_aarch64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MiniMix_5m_0 => deep history 0/8 passed | possible issues
MiniMix_5m_1 => deep history 0/8 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/8 passed | possible issues
HCRLateAttachWorkload_previewEnabled_0 => deep history 2/8 passed | possible issues
HCRLateAttachWorkload_previewEnabled_1 => deep history 0/8 passed | possible issues
Test_openjdk20_hs_extended.system_aarch64_mac ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode)

MiniMix_5m_0 => deep history 0/9 passed | possible issues
MiniMix_5m_1 => deep history 0/9 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_0 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_1 => deep history 0/9 passed | possible issues
Test_openjdk20_hs_extended.system_arm_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MiniMix_5m_2 => deep history 0/8 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/8 passed | possible issues
Test_openjdk20_hs_extended.system_ppc64le_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

HCRLateAttachWorkload_previewEnabled_1 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_0 => deep history 0/9 passed | possible issues
Test_openjdk20_hs_extended.system_riscv64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MiniMix_5m_0 => deep history 0/5 passed | possible issues
MiniMix_5m_1 => deep history 0/5 passed | possible issues
HCRLateAttachWorkload_previewEnabled_1 => deep history 0/5 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/5 passed | possible issues
Test_openjdk20_hs_extended.system_s390x_linux ❌ FAILURE ❌
Test_openjdk20_hs_extended.system_x86-64_alpine-linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MiniMix_5m_0 => deep history 0/7 passed | possible issues
MiniMix_5m_1 => deep history 0/7 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/7 passed | possible issues
HCRLateAttachWorkload_previewEnabled_0 => deep history 2/7 passed | possible issues
HCRLateAttachWorkload_previewEnabled_1 => deep history 0/7 passed | possible issues
Test_openjdk20_hs_extended.system_x86-64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MiniMix_5m_0 => deep history 0/9 passed | possible issues
MiniMix_5m_1 => deep history 0/9 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_0 => deep history 1/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_1 => deep history 2/9 passed | possible issues
Test_openjdk20_hs_extended.system_x86-64_mac ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MiniMix_5m_0 => deep history 0/9 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_0 => deep history 2/9 passed | possible issues
MiniMix_5m_1 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_1 => deep history 1/9 passed | possible issues
Test_openjdk20_hs_extended.system_x86-64_windows ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MiniMix_5m_0 => deep history 0/9 passed | possible issues
MiniMix_5m_1 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_0 => deep history 4/9 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_1 => deep history 0/9 passed | possible issues
Test_openjdk20_hs_sanity.functional_riscv64_linux ❌ ABORTED ❌
Test_openjdk20_hs_sanity.functional_s390x_linux ❌ FAILURE ❌
Test_openjdk20_hs_sanity.openjdk_aarch64_linux ❌ FAILURE ❌
Test_openjdk20_hs_sanity.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode)

jdk_foreign_1 => deep history 0/9 passed | possible issues
jdk_foreign_0 => deep history 0/9 passed | possible issues
Test_openjdk20_hs_sanity.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

jdk_lang_0 => deep history 6/9 passed | possible issues
jdk_lang_1 => deep history 7/9 passed | possible issues
Test_openjdk20_hs_sanity.openjdk_riscv64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

jdk_math_0 => deep history 0/4 passed | possible issues
jdk_math_1 => deep history 0/4 passed | possible issues
Test_openjdk20_hs_sanity.openjdk_s390x_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

jdk_util_0 => deep history 5/9 passed | possible issues
jdk_util_1 => deep history 5/9 passed | possible issues
Test_openjdk20_hs_sanity.system_riscv64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MauveSingleThrdLoad_HS_5m_0 => deep history 0/4 passed | possible issues
MauveSingleThrdLoad_HS_5m_1 => deep history 0/4 passed | possible issues
MauveSingleInvocLoad_HS_5m_0 => deep history 0/4 passed | possible issues
MauveSingleInvocLoad_HS_5m_1 => deep history 0/4 passed | possible issues
MauveMultiThrdLoad_5m_0 => deep history 0/4 passed | possible issues
MauveMultiThrdLoad_5m_1 => deep history 0/4 passed | possible issues
Test_openjdk20_hs_special.functional_aarch64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MBCS_Tests_unicode_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_codepoint_linux_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_aarch64_mac ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode)

MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_arm_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_unicode_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_codepoint_linux_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode)

MBCS_Tests_codepoint_aix_0 => deep history 0/3 passed | possible issues
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_unicode_aix_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_ppc64le_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MBCS_Tests_codepoint_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_compact_number_format_ja_JP_linux_0 => deep history 1/3 passed | possible issues
MBCS_Tests_unicode_linux_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_riscv64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MBCS_Tests_unicode_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_codepoint_linux_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_s390x_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MBCS_Tests_compact_number_format_ja_JP_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_unicode_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_codepoint_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_x86-64_alpine-linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MBCS_Tests_unicode_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_codepoint_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_x86-64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_unicode_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_codepoint_linux_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_x86-64_mac ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_special.functional_x86-64_windows ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "20" 2023-03-21
OpenJDK Runtime Environment Temurin-20+36 (build 20+36)
OpenJDK 64-Bit Server VM Temurin-20+36 (build 20+36, mixed mode, sharing)

MBCS_Tests_codepoint_windows_0 => deep history 0/3 passed | possible issues
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_unicode_windows_0 => deep history 0/3 passed | possible issues

RiscV is not on the list for being released for March, so it can be removed from triage

I am also going to remove the 'undefined' stuff from the report, because it clutters the view (and its a bug that needs addressing via https://github.com/adoptium/ci-jenkins-pipelines/issues/236).

aarch64_mac:
Test_openjdk20_hs_extended.openjdk_aarch64_mac ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_aarch64_mac_testList_0 ⚠ UNSTABLE ⚠
jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_security3_1 => deep history 0/3 passed | possible issues
jdk_management_0 => deep history 0/3 passed | possible issues
jdk_management_1 => deep history 0/3 passed | possible issues
jdk_security_infra_0 => deep history 0/3 passed | possible issues
jdk_security_infra_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.system_aarch64_mac ⚠ UNSTABLE ⚠
Rerun failed
java -version
MiniMix_5m_0 => deep history 0/9 passed | possible issues
MiniMix_5m_1 => deep history 0/9 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_0 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_1 => deep history 0/9 passed | possible issues
Test_openjdk20_hs_special.functional_aarch64_mac ⚠ UNSTABLE ⚠
Rerun failed
java -version
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues

arm_linux:
Test_openjdk20_hs_extended.system_arm_linux ⚠ UNSTABLE ⚠ https://github.com/adoptium/aqa-tests/issues/4428
Rerun failed
java -version
MiniMix_5m_2 => deep history 0/8 passed | possible issues
MiniMix_aot_5m_0 => deep history 0/8 passed | possible issues
Test_openjdk20_hs_special.functional_arm_linux ⚠ UNSTABLE ⚠.  https://github.com/adoptium/aqa-tests/issues/4424
Rerun failed
java -version
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_unicode_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_codepoint_linux_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_arm_linux ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_arm_linux_testList_1 ⚠ UNSTABLE ⚠
jdk_other_2 => deep history 0/3 passed | possible issues
jvm_compiler_2 => deep history 0/3 passed | possible issues
jdk_security3_2 => deep history 0/3 passed | possible issues
jdk_security_infra_2 => deep history 0/3 passed | possible issues

ppc64_aix:
Test_openjdk20_hs_extended.openjdk_ppc64_aix ❌ ABORTED ❌
Test_openjdk20_hs_extended.openjdk_ppc64_aix_testList_0 ❌ ABORTED ❌
jdk_other_0 => deep history 0/3 passed | possible issues
jdk_net_0 => deep history 0/3 passed | possible issues
jdk_net_1 => deep history 0/3 passed | possible issues
jdk_security2_1 => deep history 0/3 passed | possible issues
jdk_security3_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_ppc64_aix_testList_1 ⚠ UNSTABLE ⚠
jdk_other_1 => deep history 0/3 passed | possible issues
jdk_nio_0 => deep history 0/3 passed | possible issues
jdk_nio_1 => deep history 0/3 passed | possible issues
jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_security4_0 => deep history 0/3 passed | possible issues
jdk_security4_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_sanity.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
jdk_foreign_1 => deep history 0/9 passed | possible issues
jdk_foreign_0 => deep history 0/9 passed | possible issues
Test_openjdk20_hs_special.functional_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
MBCS_Tests_codepoint_aix_0 => deep history 0/3 passed | possible issues
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_unicode_aix_0 => deep history 0/3 passed | possible issues

ppc64le_linux
Test_openjdk20_hs_extended.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Test_openjdk20_hs_extended.openjdk_ppc64le_linux_testList_0 ⚠ UNSTABLE ⚠
jvm_compiler_0 => deep history 2/3 passed | possible issues
jvm_compiler_1 => deep history 2/3 passed | possible issues
jdk_security_infra_1 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.openjdk_ppc64le_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_security3_0 => deep history 0/3 passed | possible issues
jdk_security3_1 => deep history 0/3 passed | possible issues
jdk_management_0 => deep history 1/3 passed | possible issues
jdk_management_1 => deep history 1/3 passed | possible issues
jdk_tools_0 => deep history 1/3 passed | possible issues
jdk_security_infra_0 => deep history 0/3 passed | possible issues
Test_openjdk20_hs_extended.system_ppc64le_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
HCRLateAttachWorkload_previewEnabled_1 => deep history 0/9 passed | possible issues
HCRLateAttachWorkload_previewEnabled_0 => deep history 0/9 passed | possible issues
Test_openjdk20_hs_sanity.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
jdk_lang_0 => deep history 6/9 passed | possible issues
jdk_lang_1 => deep history 7/9 passed | possible issues
Test_openjdk20_hs_special.functional_ppc64le_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
MBCS_Tests_codepoint_linux_0 => deep history 0/3 passed | possible issues
MBCS_Tests_datetime_formatter_0 => deep history 0/3 passed | possible issues
MBCS_Tests_compact_number_format_ja_JP_linux_0 => deep history 1/3 passed | possible issues
MBCS_Tests_unicode_linux_0 => deep history 0/3 passed | possible issues

All sanity.system mauve failures on all platforms are reported https://github.com/adoptium/aqa-tests/issues/4341. Fix is in the aqa-systemtest master. Release is running with v0.9.6 and corresponding aqa-systemtest tag v0.9.6, which doesn't have fixes. @smlambert suggestions?
MauveSingleThrdLoad_HS_5m_0 => deep history 9/12 passed | possible issues
MauveSingleThrdLoad_HS_5m_1 => deep history 9/12 passed | possible issues
MauveSingleInvocLoad_HS_5m_1 => deep history 9/12 passed | possible issues
MauveMultiThrdLoad_5m_0 => deep history 9/12 passed | possible issues
MauveSingleInvocLoad_HS_5m_0 => deep history 9/12 passed | possible issues
MauveMultiThrdLoad_5m_1 => deep history 9/12 passed | possible issues

Yes, we create a new tag for aqa-systemtest (https://github.com/adoptium/aqa-systemtest/releases/tag/v<IP_ADDRESS>) and then reference it in the testenv.properties file to pick up that change.

I'd like to update v<IP_ADDRESS> to have the fix https://github.com/adoptium/aqa-systemtest/pull/483 for the release run. @smlambert is that ok?

I've done it shows it (new diff: https://github.com/adoptium/aqa-systemtest/compare/v0.9.6...v<IP_ADDRESS>)

Close it. s390x will be triage during the release


Feature/animated splashscreen

I try to create an animated splashscreen. However I can't seem to find a way to center it. Help and thoughts on this would be appreciated.

Thank you for the suggestion. While it didn't solve the problem, I still found a way to apply the correct Style.


messages should have a context-menu on long-touch

items needed (among others) are "share message", and the possibility to select (for copy/paste) text and so forth.

On Cyanogen, Chatsecure 13.1.2 : I cannot find how to Copy a text sent to me. When I 'long press' on text/link, it's no menu. From the Menu availabe when I push on the 3dots(or lines) , I get only "Settings" and "End chat" (no "Share" or something similar). Is there a solution for that? thanks


Add i.MX RT LCD display controller support

Adds a new mcux shim driver for the eLCDIF display controller, and enables it on rt1050 and rt1060 boards. Updates the lvgl sample application to support these boards.
Tested on rt1050 and rt1060.
@ioannisg @agansari I cheated a little to configure the mpu for the frame buffer, and just made all ram write through instead of write back. We need a way to partition the ram such that the only the frame buffer is write through (or noncacheable). The ethernet driver needs this too.
@galak Please have a look at the dts.

Rebased to latest master and reworked the dts. @galak, please have another look.

Can we just have it be the display type and have all the param's defined based on a display single Kconfig?

Sure, done.

@vanwinkeljan 	Please revisit. I think I've addressed most of your issues except for userspace and flushing, which I'd like to postpone to future PRs.


Change touchstart and mousedown to prevent unexpected swipe opening

I try to fix trouble with scrolling on iOS: if I start dragging by touch for scrolling the page, the select will open if my first touch was over the select box.

Closing this off because while this is inconvenient, the behavior is expected in 3.5.
In 4.0.0, we no longer listen to the touchstart event.


reset ML config

Codecov Report

Merging #15 (761099b) into master (25f7b24) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #15   +/-   ##
=======================================
  Coverage   86.48%   86.48%
=======================================
  Files           3        3
  Lines         222      222
=======================================
  Hits          192      192
  Misses         30       30

Continue to review full report at Codecov.

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


convert to long int for direct comparison

self._data_shapes[0].shape is int based shape, and data_batch.data is long int base shape result.
The change converts both shape variables into long int for direct comparison.

1 == 1L
True

(i for i in range(2))==(i for i in range(2))
False

This is due to (...) returns a generator.
I think the right fix is to change to tuple(...)
>>> tuple(i for i in range(2)) == tuple(i for i in range(2))
True

Agree, ideally solved the problem.


Implementation of ?++ command for users with Admin Roles (Core, Maintainer, and Admin)

1.Describe the changes made:
-Added regex to detect '?++' command
-Verified that the user is able to use '?++' command by checking their roles, only admin, maintainer, or core roles are able to use this command.
-Bot outputs appropriate message if user is not an admin/core/maintainer user
-If user does have an admin role, the API request to the award Points API is populated with an argument of 2 to award 2 points
-Resolved UnhandledPromiseRejectionWarning: DiscordAPIError: Cannot send an empty message that was being caused in some use cases because we were passing empty Promises in points.js to botEngine.js. We would then try to message.channel.send that empty response, causing the warning above.
-Added test cases in points.test.js for the ?++ command

If this PR is related to an open issue please reference it with the # operator and the issue number below:
#176

For future reference, here's the original thread:
https://github.com/TheOdinProject/odin-bot-v2/pull/185

You need to be sure that you're on the branch that has your features :)

Are you on Discord? The fix is going to be a bit involved and it will be easier to communicate in real time.

yes, ill send you a dm


Load track from url

Changes are made as far forward as possible to make them obvious
track is lz-string compressed and uri safe base64 encoded

url hash is prefixed with plopdown:

Possible future simplifications

Drop Saved in favor of their base implementations
(Track and VideoRef)

the aspects added by the Saved<> interfaces aren't being from
this point up.

URILoaderService or SubService to mimic BackgroundSubService

A common interface for Track loading services

#23

Manual testing resources: https://gist.github.com/whytheplatypus/db6f316b1a740b5786159a666e178d22

Perfect! I love it

@whytheplatypus is this good to merge? I imagine we need some UI to generate/export the current plopdown?

@spaceribs should be good, the behavior(s) that generates the links makes sense as it's own set of work


raftstore/store: calibrate tick with mono clock time

Fix issue #964.
This PR adds tick calibration using the system's monotonic raw clock time.
Everytime when Store::tick() triggers, the monotonic raw clock time will be used to calculate the passed time and the actual tick number it should run.
A config option is added for turning on/off this calibration.
PTAL @siddontang @BusyJay

What we want to solve here is to check whether leader is valid or not when we supply lease read. So I think we don't need to calibrate tick.
I think another way, but maybe not correct.
When the peer become the leader, it can set a leader_check_time, then for every election_timeout / 2 tick, the leader can propose a command to check whether it is still the leader, the leader will update the leader_check_time in the callback.
For lease check, if we find now - leader_check_time > election_timeout, we can't use the lease read even the peer is still the leader.
Of course, this is approximate and not accurate.

@siddontang
If leader_check_time is tick numbers, then it is essentially the same with what it's right now to set leader_check_time to be a 1/2 election_timeout. If the leader ticks slower, there still time windows(1/2 election_timeout) that leader serves lease read but its lease has expired indeed.
If leader_check_time is monotonic raw clock, then it is essentially the same as what's in this PR. which calibrate lease(or ticks, since now lease is measured by ticks) using clocktime.

Of course, the leader_check_time is monotonic clock.
As I said before, what we focus is to solve the lease stale read problem, so I don't think calibrating tick is necessary, and it can't avoid stale lease read too.

PTAL @xiang90

PTAL @ngaut

I think if we can support safe read index and the performance is acceptable. We can use it directly for leader/follower read and won't care the stale problem anymore.

Follow leader_check_time.
What we really want to solve is to supply a safe lease read. So we should know when we can use lease read, and when we must use safe read. If we use safe read, how can we switch to lease read again.
If the leader election timeout is 5s, let's consider clock drift bound, I think 1s is enough. So if a peer becomes leader at t1, it can supply lease read in [t1, t1 + 4s). After t1 + 4s, it must use safe read.
We can set t1 to leader_check_time, so we can supply lease read in [leader_check_time, leader_check_time + 4s).
The next problem is to how to update leader_check_time. Let's assume that the leader proposes a write( including safe read) command at t2, applied the command and calls the callback at t3, if t3 - t2 < 1s, we can think the leader is still leader, and we can set t2 to leader_check_time, and the next lease time range is [t2, t2 + 4s). If t3 - t2 >= 1s, we can think there is something wrong, so we don't update leader_check_time until another raft command execution' time < 1s.
We may meet a case that the leader has no write command for a long time, so for every 2s, we send a NOOP raft command(or using safe ReadIndex) to update the leader_check_time.
briefly, the simple solution is:
1, If a peer becomes leader, set leader_check_time and supply lease read in [leader_check_time, leader_check_time + 4s).
2. For every write command, check its execution time (propose t1 -> callback t2), if < 1s, think the leader is still the leader, update leader_check_time with t1.
3. With 2, if t2 - t1 > 1s, don't update leader_check_time.
4. After leader_check_time + 4s, supply safe read until condition 2 is met.
5. Use a 2s tick to send command to update leader_check_time.
Of course, above time like 1s, 2s is configured. We can test and determine a better value.
/cc @ngaut @BusyJay @hhkbp2

This PR will substituted by #1296


@click="method1" handling

What problem does this feature solve?
On :{click:} why the implementation is copying method1 to click instead of on:{click: staticMethod('method1')}
I want use directive to proxy click method:
like
Vue.directive('autoload', {
bind(el, bind, vnode){
const method = bind.expression;
console.log(vnode.context.$options.methods);
if(vnode.context.$options.methods[method]){
vnode.context[method] = vnode.context.$options.methods[method] = proxyMethod(method, vnode.context.$options.methods[method], vnode.context);
}
}
});
What does the proposed API look like?
on:{click: staticMethod('method1')}
thx

As described in the issue helper:

Explain your use case, context, and rationale behind this feature request. More importantly, what is the end user experience you are trying to build that led to the need for this feature?
An important design goal of Vue is keeping the API surface small and straightforward. In general, we only consider adding new features that solve a problem that cannot be easily dealt with using existing APIs (i.e. not just an alternative way of doing things that can already be done). The problem should also be common enough to justify the addition.

Please elaborate on your use case so that we can understand it better.


Use concurrency to cancel previous CI runs

Ref: https://github.com/FuelLabs/fuels-ts/pull/361

I can take this, but I'll wait on #890

This is now unblocked @iofq!


fix: node 18 network interfaces support

While I was running the bridge on the latest version of node I did not get any interfaces to show up in the output.
It seems like I ran in the same issue as described here.
https://github.com/nodejs/node/issues/42787
I added a simple else to keep backwards compatiblity.

Since this tool is supposed to be used as a standalone binary with the bundled runtime (v16 currently) and nodejs fortunately reverted the change in 18.4 https://github.com/nodejs/node/commit/70b516e4dbdfdfea2183995ec3b368dacaa38183, this change shouldn't be needed in any setup
Thanks though


Obj gen and enums

Couple changes to the object defs to make the object gen and enum support work.  Found out the hard way the ISO spec for geographic data sets has field names that don't translate to valid python identifiers.  Updated the sample yaml to reflect the new enum format.

This pull request is OK. Can you delete the geographicdataset.yml completely?
Also this pull should probably only be done when the new code is in place for generate_interfaces. Otherwise wouldn't it break for everyone. Please go ahead and merge it in when ready

This pull request was for comment only.  I'm closing it out because it is now superseded by other changes.


Migration to CodeQL

Description
The sig-security team announced, that licensing for Veracode will expire and a migration to CodeQL should be done.

and remove veracode, it's not used anymrore by TX


slow initial render

I have a site that was using polymer < 1.0. That sites index page loaded quickly. After upgrading, the header loads slowly and finally renders. I expected performance to improve but it actually got slower. What would cause this? It's quite annoying because we spent 2 weeks upgrading and now we have a slower site.

After upgrading to what? What browser? What does the code do? Can you provide a repo project?
With this little information it's not possible to do any diagnosis.

Had similar suspicions. Tried to do some rough load time measurements with Chrome, comparing JS polymer with dart polymer. This was done to identify the overhead introduced by the dart environment. All on localhost web server.
JS polymer project
https://www.polymer-project.org/1.0/start/first-element/intro
Measured with Chrome. Finished 358ms, Loaded 431ms
Dart polymer project
Example project generated by dev environment. Dart2js builds with Chrome.
Finised 728ms, Loaded 728ms
Since the fonts.google.api is an external request, these are removed. Which gives
Finised 472ms, Loaded 676ms
This includes a 'Not Found' request to index.bootstrap.initialize.dart
Which is measured to 74ms
Comparision
With some loose estimate the load time is increased from 450ms to 650ms going from JS to Dart. So at max 200ms, so not huge. Maybe this difference increases, when the project grows, this is not measured here.

I will provide more information in a few. Just got into the office.

Maybe an issue here. On phone the initialization locks up the app for like a seconds. At the moment sustainable, but there is a concern, when the project grows.
Measured with Chrome Timeline tool on desktop. On a phone with weaker cpu this should scale linear.
Minimal project Evaluate(index.bootstrap.initialize.dart.js) 210ms
Small project - Four custom element, max 500 lines dart aside the elements, no references to external frameworks
Evaluate(index.bootstrap.initialize.dart.js) 470ms
I interpretate this as extra time added to the plain Polymer startup time. And that this comes from the treeshaken dart2js code. The concern is that this will grow from several contributions.

Dart code source code added to project.
New polymer library elements are referenced, the dart parts of these contributes.
External packages are included and referenced like the intl package.

For this project only negligible improvements by processing with vulcanize. All js code is needed, but the compact evaluation degrades user experience at start.

@aslanvaroqua what are your findings on this? At the moment I don't suspect extra startup time has been added at 1.0, so maybe we should consider to close this issue. If new info/data comes up it could be reopened.

Have digged a little deeper into this. The initial startup time consist of two major contributions.
a) From js Polymer the initial population of elements. Pr. element type this is the call to Polymer({..}) e.g. https://github.com/dart-lang/polymer_elements/blob/master/lib/src/iron-collapse/iron-collapse.html#L81
This trigger a significant amount of processing pr. element type.
b) The load/parse/evaluate of the index.html and index.bootstrap.initialize.dart.js
The both scales with the size of the project, while a) maybe of most concern, since it scales linear with the number of element types.
For desktop app not a concern, but for mobile apps the startup time have to be trade of with the size of the app. Every new element type slows down the start. Anyhow for a) hard to do better, than what is provided by js Polymer.


remove() to complement add() ?

Hello, @jeancroy I LOVE your library! It's fantastic. So much better than the many other popular fuzzy search libraries.
A lot of your writing on the theory and algorithms implementation goes over my head and I don't have time to get into that, but I love that it's there. The mere presence of extensive intellectual stuff gives me extra confidence in your library, plus I can tell you really value the things you create, and aim to produce stuff that works well. So I give your library many stars! ⭐ ⭐ ⭐ ⭐ ⭐ ⭐
I also LOVE how you have an add method, it fits my use case perfectly. My use case is adding documents (and queries, but they are shorter, and are easier to handle), to an index inside of a desktop app that archives your browsing history so you can read it when you are offline. I recently added full text search to this (using flexsearch and ndx), but while these are good (and serializedable, to save time on restarting the app), they do not support typos. So I went searching for a fuzzy library, and after a few false starts, ended up here (actually via the GitHub search, not by npm search nor by Google search). I'm really thankful I did end up here.
Even if you can't implement any of these things (such as serialization, or remove), I am still immensely grateful for your library. Thank you for crafting such a thing of beauty and releasing into the world for all to use!
Anyway, I'd like there to be a remove, but I know it's not your job to make it, and I am sure you are in any case super busy. But let me just describe it here for the sake of the issue.
If I added a document to the index using add(), and then later removed() that document from the index, the document would not show up in search results, nor in serializations (such as they may be) of the index.
My particular motivation for this feature is that very often, a webpage (with the same URL) will add additional content (such as comments on a story), and my archiver would like to index those so that the person using the archiver can get (and search for) the most up-to-date version of the content they have seen.
Right now my solution is simply to discard all fz-search results that are older duplicates, but I am worried about the scalability of this, so have delayed deploying it to production. This is because people may re-index a page on the change of its content many times, but if I never remove those pages from the fuzzy search index, my index will end up dominated by pages that I no longer need and are out of date. So you can see I'm very scared of this possibility! It would be terrible!
But it's OK. If that's the case that you cannot implement a remove (or even serialization--I commented on another issue #21 ), I will still use your wonderful fz-search library for providing typeahead and suggestion for search queries (just like Google search), rather than on results. It will be a little sad to not be able to search with typos, but I'm sure I can figure out another way to do it somehow.
Please delete this issue if you already have this functionality (how embarrassing! 😱 )

So the main complication is that a lot of data is matched by position index in array.
So a temporary removal could be
this.source[idx] = null
this.index[idx] = null
this.store => iterate over all field to remove idx
this.index_map => get unique id of item to remove, then invalidate this using -1, null ?
Then a lot of null check and invalid check.
A more complete removal would require to map all old position to new position.
I'm not sure if this is worth the trouble if rebuilding the index take less than say 200ms
Even if rebuilding the index take like a full second I'd invest in a low priority background worker instead of the complexity of patching the index to new position.
The add() method I can see useful where a client is being drip fed documents.
The remove() I'm not sure of the use case.

As I said right now I gravitate invalidate & rebuild cache.
But I'm interested in your rebuild time.
And if they are unacceptable I'll see if it's worth to properly patch the cache.


Return indexes of selected points

Is there a way to get the indexes of points selected by the lasso or box selector for use later on in a notebook?

Yes, try the Selection1D stream, there's a number of examples using it, see:
http://holoviews.org/reference/streams/bokeh/Selection1D_points.html
http://holoviews.org/reference/streams/bokeh/Selection1D_paired.html


[json] schema path not resolved properly for multi-root workspaces

Issue Type: Bug
I have a multi-root VSC workspace with three folders:

A/
./subfolderOfA
<external abs path>

In A/, there is a .code-workspace file and in there, there are the following settings:
"files.associations": {
    "*.rq*": "json"
},
"json.schemas": [
    {
        "fileMatch": [
            "*.rqw"
        ],
        "url": "./samples/schemas/rqwSchema.json"
    }
]

When I edit some .rqx file somewhere inside A/, it seems like this JSON schema file path is only properly resolved If I remove folders  ./subfolderOfA and <external abs path> from my multi-root workspace. Shouldn't this work?
VS Code version: Code 1.56.2 (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T17:13:13.157Z)
OS version: Windows_NT x64 10.0.19042

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.92GB (8.65GB free)

Process Argv
--crash-reporter-id 919e0ed9-46f3-4ad4-9e28-f35755bf8266

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

bracket-pair-colorizer-2
Coe
0.2.0

xml
Dot
2.5.1

tortoise-svn
fan
0.1.1

python
ms-
2020.9.114305

vscode-pylance
ms-
2021.5.3

jupyter
ms-
2021.6.832593372

cpptools
ms-
1.3.1

code-spell-checker
str
1.10.2

open-in-browser
tec
2.0.0

vscodeintellicode
Vis
1.2.14

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30291414
vspre833cf:30267465
pythonptprofiler:30281270
vshan820:30294714
vscorecescf:30290706
pythondataviewer:30285071
vscus158cf:30286554
vscgsv2:30301612
vscorehov:30302759
bridgeflight:30302069
vscod805:30301674

Hi @aeschli
Unfortunately, I am not familiar with your planning process but I wanted to ask if this bug will be solved in the near future?

Sorry, I don't know when I will find time for looking at this.

It's honestly quite a shame that this feature is missing. Unless you want to modify the json file structure to include the "$schema" property you are stuck having to open the given sub-folders directly which is a significant detrement to the DX when working in multi-root workspaces.

It seems like relative schema path resolution does not work on Windows, even when not in a multi-root workspace. Schemas always try to resolve in C:/ rather than the workspace folder.

Note: relative path can not be used in user settings. But they should work in workspace files, where I could reproduce the problem, thanks @connor4312 !

Now I get Unable to load schema from 'c:\Users\raymondzhao\work\emmet-work\testworkspace3': EISDIR: illegal operation on a directory, read. in the Problems view with the following setup:
In a non-multi-root workspace:
.vscode/settings.json
    "json.schemas": [
        {
            "fileMatch": [
                "*.json"
            ],
            "url": "./catboost_info/la.json"
        }
    ]

catboost_info/la.json
{
}

myfile.json
{
	"$schema": ""
}

I created a separate issue to investigate....

To verify:

clone https://github.com/aeschli/test-schema-in-workspace
open workspace test-schema-in-workspace/test-schema.code-workspace
look at the workspace settings: all files ws.json are associated with schema ./folder2/ws-schema.json. Note that this is a relative path to the workspace file
open both files ws.json and check that code completion gives back property ws-folder2. You can also click on the JSON language selector ({ } next to JSON in the status bar) to see the schema that is associated
look at the folder setings:  foo.json is associated with schema ./folder1/foo-schema.json. Note that this is a relative path to the folder
open both files foo.json files and check that code completion gives back property foo-folder1, but only when in folder1. You can also click on the JSON language selector ({ } next to JSON in the status bar) to see the schema that is associated

I tried to verify this using build
Version: 1.76.0-insider (user setup)
Commit: 92da9481c0904c6adfe372c12da3b7748d74bdcb
Date: 2023-02-28T11:50:30.886Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22623
Sandboxed: Yes

but the schemas are not used. Here is what I see in the UI:

@aeschli please advise which build I should use for verification.

Looks like it is still not working on Windows due to to an URI encoding issue.

I tested as described in the "test-schema-in-workspace" repro with VS Code 1.76.0 on Windows.
I observed the following for foo.json and bar.json in VS Code:

no schema-defined code completion is offered
there is no schema offered when clicking on the language selector

I then tested folder-only settings by opening VS Code to folder1.  I observed the same as above for foo.json.
FWIW, this stackoverflow question describes another repro with only folder settings (not workspace settings).
Is there a known workaround to get validation working using fileMatch on Windows for 1.76.0?

@alx9r the fix for Windows is coming: https://github.com/microsoft/vscode/issues/176296

https://github.com/microsoft/vscode/issues/176296 is now also fixed (and verified)


use motw for chat attachment downloads

Maybe you could try this to make sure it works @zanderz? Thanks!

cc @maxtaco

Check!

LGTM, still builds on Windows


htop: 3.0.5 -> 3.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/htop-dev/htop/releases.
meta.description for htop is: "An interactive process viewer for Linux"
meta.homepage for htop is: "https://htop.dev"
meta.changelog for htop is: "https://github.com/htop-dev/htop/blob/3.1.0/ChangeLog"
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/mn1l675lglvhrxbi7gpkyw65gv2qfndw-htop-3.1.0/bin/htop passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 3.1.0 with grep in /nix/store/mn1l675lglvhrxbi7gpkyw65gv2qfndw-htop-3.1.0

found 3.1.0 in filename of file in /nix/store/mn1l675lglvhrxbi7gpkyw65gv2qfndw-htop-3.1.0

directory tree listing: https://gist.github.com/2b51dfcda9b85e5550f08d393d82609d

du listing: https://gist.github.com/7fcc743e0059d32e18de491224abcc71

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
htop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mn1l675lglvhrxbi7gpkyw65gv2qfndw-htop-3.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A htop https://github.com/r-ryantm/nixpkgs/archive/c1313e30fb12bec0e06a5460ef2a57e28707ea8f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mn1l675lglvhrxbi7gpkyw65gv2qfndw-htop-3.1.0
ls -la /nix/store/mn1l675lglvhrxbi7gpkyw65gv2qfndw-htop-3.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

htop

Maintainer pings
cc @rbvermaa @relrod for testing.

Result of nixpkgs-review pr 139036 run on x86_64-linux 1

1 package built:

htop


Track headset battery level

SteamVR exposes wireless HMD battery levels now, so it should be added to the Devices list. It could be used for other things too, I want to get an alarm when my HMD battery falls below 25% so I can wake up and plug it in.

That's good to know! I'll have a look to see if I can integrate that.


PHP executable not found. Install PHP 7 and add it to your PATH or set the php.executablePath setting

Issue Type: Feature Request
PHP executable not found. Install PHP 7 and add it to your PATH or set the php.executablePath setting
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363

In my case, I have XAMPP installed ...
I opened the VSCode
I went to Settings
I searched for "php.validate.executablePath"
and in the setting.json link I typed:
"C: /xampp/php/php.exe" in "php.validate.executablePath": "",

Issue Type: Feature Request
PHP executable not found. Install PHP 7 and add it to your PATH or set the php.executablePath setting
VS Code version: Code 1.51.1 (e5a624b, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363

In my case, I have XAMPP installed ...
I opened the VSCode
I went to Settings
I searched for "php.validate.executablePath"
and in the setting.json link I typed:
"C: /xampp/php/php.exe" in "php.validate.executablePath": "",


Infinispan - migrate deprecated configuration properties

Summary
Replace deprecated properties.
Please check the relevant options

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[x] Refactoring
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[ ] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[x] Example scenarios has been updated / added
[x] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

I'll debug CI. Also I found couple more deprecated properties to migrate.

@fedinskiy CI is green


Add recipe for using Granted with WSL and Windows Credential Manager

The following setting works out of the box for Windows Credential Manager when running Granted in WSL, as reported by a community member.
[Keyring]
  Backend = "wincred"

We should document this so that other WSL users can easily discover it.

Unfortunately this is not actually working correctly. While with this config, it no longer prompts for a password for the file-based cred-store, it authenticates to SSO every time instead of caching the token.
❯ assume --verbose -c ...
DEBUG: starting update check
2022/09/08 16:27:02 [keyring] Considering backends: [wincred]
DEBUG: GetValidCachedToken: opening keyring: Specified keyring backend not available

The workaround I found for this is to use pass instead of wincred. This approach requires gpg, but is otherwise working smoothly for me.
Per some guidance from @chrnorm, you can create a gpg key to use with granted-cli:
sudo apt install pass
gpg --full-generate-key
pass init E7BF4FFE628F18FCFC3A6C8DC5E556A9DB95E5E5 # your public key ID from previous step
export GPG_TTY=$(tty)

I also add the export command to my .bashrc so it set automatically:
❯ grep GPG_TTY ~/.bashrc
export GPG_TTY=$(tty)

And then because WSL can open the browser from the windows path just fine, you can setup your granted config like this:
❯ cat ~/.granted/config
DefaultBrowser = "FIREFOX"
CustomBrowserPath = "/c/Program Files/Mozilla Firefox/firefox.exe"
CustomSSOBrowserPath = ""
LastCheckForUpdates = 3
Ordering = ""
ExportCredentialSuffix = ""

[Keyring]
  Backend = "pass"

The exact path to the browser may be different on your WSL, depending on how you setup WSL and on how/where you installed the browser. I am using firefox installed to the default path, but in WSL I mount /c instead of the default /mnt/c...

Thanks for your instructions @lorengordon, however I'm still having issues - maybe someone could help here?
I've installed pass, generated a key and exported GPG_TTY (echo returns /dev/pts/0).
calling pass  also returns the password store:
Password Store
└── granted-aws-sso-tokens
    └── https:
        └── d-XXXXXXXXX.awsapps.com
            └── start#

Assuming a role works as well, however it seems the authentication token is not being cached. Every time I assume the (same) role, I get prompted for a browser authentication:
$ assume -c --verbose
[DEBUG] profile registry not configured. Skipping auto sync.

? Please select the profile you would like to assume: role_xyz
2022/12/12 15:35:41 [keyring] Considering backends: [pass]
[DEBUG] GetValidCachedToken: The specified item could not be found in the keyring

[i] If the browser does not open automatically, please open this link:
[i] https://device.sso.eu-central-1.amazonaws.com/?user_code=AAAA-BBBB
[i] Awaiting authentication in the browser...

calling granted sso-tokens list only returns one (incorrect - only one "/" after the https:/) URL that doesn't seem to be linked to any profile
$ granted sso-tokens list
https:/d-XXXXXXXXX.awsapps.com/start# ()

meanwhile, when calling the same command in PowerShell (for testing purposes), I do get a cached token after I authenticated once:
> granted sso-tokens list
https://d-XXXXXXXXX.awsapps.com/start#/ (role_xyz)

I did use the granted sso-tokens remove --all command mentioned in the docs (https://docs.commonfate.io/granted/configuration/), but even then this "invalid" token persists.
Also granted uninstall doesn't change anything here, after adding the keyring to the config again the issue is the same as before.
The .aws config file is exactly the same in both the WSL and Windows environment:
[profile role_xyz]
credential_process=aws-sso-util credential-process --profile role_xyz
sso_start_url=https://d-XXXXXXXXX.awsapps.com/start#/
sso_region=eu-central-1
sso_account_id=YYYYYYYYYYYY
sso_role_name=AWSAdministratorAccess
region=eu-central-1
cli_history=enabled
max_attempts=10
retry_mode=standard

Would really appreciate if someone could help me get that setup running, happy to provide further details if needed (WSL runs Ubuntu 20.04.5 LTS if that is of relevance)!

This worked for me immediately. All I did was add the following snippet to the end of my ~/.granted/config (in WSL)
[Keyring]
Backend = "wincred"

Thanks for uploading the workaround!
Would be really nice to get this working with the "wincred" backend as well!

Could you please provide some more info on getting this workaround working or help with resetting the token? I need to restart WSL each time my AWS token expires which is a pain!

Another option I just got working is to use WSLg, and enable systemd in wsl. Then setup gnome-keyring, and configure granted to use it:
[Keyring]
  Backend = "secret-service"


IPAM driver name should not be required in network create

- What I did
This fix tries to address the issue raise in #25735 and https://github.com/docker/engine-api/issues/368
where currently IPAM driver name is required in NetworkCreate ('/networks/create').
- How I did it
This fix (together with engine-api update) changes the type of IPAM in NetworkCreate
to be a pointer so that by default IPAM driver name is not needed.
- How to verify it
This fix has been tested manually, as is specified in https://github.com/docker/engine-api/issues/368.
- Description for the changelog
This fix fixes #25735.
This fix is related to #25735 and https://github.com/docker/engine-api/issues/368.
A pull request in engine-api has been created separately:
https://github.com/docker/engine-api/pull/372
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

PTAL @mrjana
First pass on the code looks good. Will take a second pass after @mrjana approves.

ping @mrjana

@yongtang Can you please rebase?

@yongtang engine-api moved into docker/api . You may have to fix adjust this PR accordingly.

Thanks @mrjana. I tried to rebase and found out that this PR has been completely covered in #26200 and there is no further change needed. So I will just close this PR for now. Again, thanks for the help!


added flappy bird

🛠 Fixes Issue #421

✅ Check List (Check all the applicable boxes)

[x] My code doesn't break any part of the project (Zero Octave-Javascript-Projects).
[x] This PR does not contain plagiarized content.
[x] My Addition/Changes works properly and matches the overall repo pattern.
[x] The title of my pull request is a short description of the requested changes.

📷 Screenshots

update your forked repo

@NOiR-07 merge conflict resolved, should I change something else?

sorry for the delay, there are some changes In the file structure of website so i would suggest you to make the same or push a new pr

update your project on cards.json alphabetically and README after updating fork

@TsarPrince  You still have time till evening. After that I will be closing this PR.


iOS - cordova-plugin-local-notifications compatibility

Bug report
Current behavior:
This plugin works correctly. I have the problem when adding cordova-plugin-local-notifications (https://github.com/katzer/cordova-plugin-local-notifications), after adding it the "onMessageReceived" event does not fire.
If the application is in the background, the notification is received but when touching it "onNotification" does not fire. When the App is in foreground, it seems that the push do not arrive because the event in question is not triggered.
Expected behavior:
Necesito que convivan ambos plugins debido que debo enviar notificaciones locales y desde el servidor. Con cordova-plugin-firebase ambos funcionaban perfectamente.
Environment information

Cordova CLI version

cordova -v 9.0.0<EMAIL_ADDRESS>

Cordova platform version

cordova platform ls ios 5.0.1

Plugins & versions installed in project (including this plugin)

cordova plugin ls
cordova-plugin-firebasex 6.0.7 "Google Firebase Plugin"
cordova-plugin-local-notification 0.9.0-beta.2 "LocalNotification"

iOS build issue:

Node JS version

node -v10.10.0
npm -v6.10.3

XCode version 10.3

Other information:
I will publish the compatibility issue with the other plugin, but I turn here first because it seems more updated and because with cordova-plugin-firebase I did not have this problem.
Anyone used both plugins and managed to make them work?
Thanks in advance, regards.

I implemented this branch of the plugin: https://github.com/Steffaan/cordova-plugin-local-notifications
The local notifications and push firebase function worked correctly.

This fork not working with cordova-plugin-firebasex 10.0.0 and upper

Hello
@fgarcia5 @dpa99c
We are using  https://github.com/Steffaan/cordova-plugin-local-notifications(0.9.3)  and cordova-plugin-firebasex(13.0.0-cli) plugins in our cordova project. when iOS app in foreground and sent local notification, it throw error message
FirebasePlugin[native]: willPresentNotification: foreground notification not set
can you please help us to solve this?
Thanks

Hello,
are there any updates for the problem? I also want to use both - local notifications and the firbeasex plugin.
Can anybody help me?
Thank you!

Hello,
are there any updates for the problem? I also want to use both - local notifications and the firbeasex plugin. Can anybody help me?
Thank you!

resolved in
https://github.com/dpa99c/cordova-plugin-firebasex/pull/573


Implemented Landing/Home Page as per the provided figma file

Changes

Implemented the home.jsx as per the figma file.
Page is responsive to all devices.

Note

The text under the "feature" section is dummy.
The login page seen in the first GIF is in under process and not a part of this commit.

Great work @sumit-kumar-jha1709 .

Can you fix the padding in the get started button and the image on the left?

sure @sikehish working on this

Hey @sikehish can you please tell me on what screen size this problem of padding is occurring as I've checked it on different screen sizes but it worked absolutely fine.

@sikehish I've done some changes in the padding, can you please check it now.

@sikehish can you please check it now, I've updated the necessary padding of "feature" section and the "get started" button and also updated the flex properties for better responsiveness.

It looks fine to me. Good job!


Add check for Object_replacement_character

https://github.com/jessesquires/JSQMessagesViewController/issues/1323 fixed

I saw you had this error in your CI: "The command "brew update" failed and exited with 1 during ."
Since I had the same issue, you need to add a workaround to cope with this issue in Homebrew:
https://github.com/marco1981/JSQMessagesViewController/commit/3e718c1022b97e1a90b1fe4c1e52880bf3d85937
Basically you need to change line 23 in .travis.yml:
brew update || brew update

Hey @azonov ! :smile:
Sorry it took so long to answer here. Are you still interested in supporting this PR?

[Current coverage][cc-pull] is 66.34%

Merging [#1324][cc-pull] into [develop][cc-base-branch] will increase coverage by +1.58%

@@           develop   #1324   diff @@
======================================
  Files           55      59     +4
  Lines         1966    2148   +182
  Methods          0       0
  Branches         0       0
======================================
+ Hits          1273    1425   +152
- Misses         693     723    +30
  Partials         0       0

2 files (not in diff) in ...Controller/Factories were created. more
2 files (not in diff) in ...ssagesViewController were created. more

[][cc-pull]

Powered by Codecov. Last updated by de044c4
[cc-base-branch]: https://codecov.io/gh/jessesquires/JSQMessagesViewController/branch/develop?src=pr
[cc-pull]: https://codecov.io/gh/jessesquires/JSQMessagesViewController/pull/1324?src=pr

Hey @azonov - one last ping before we close this and manually apply the fix.
Can you resolve conflicts and update the PR?
Also, there's a bunch of unrelated work here, right? We only want the changes in NSString+JSQMessages.m, correct?

// cc @eliburke

We only want the changes in NSString+JSQMessages.m, correct – yes
Can you resolve conflicts and update the PR? - after weekends
Thanks,
Andrey Zonov

Senior iOS Developer
DataArthttp://www.dataart.ru/
https://htmlsig.com/skype?username=andry-zonov
skype:  https://htmlsig.com/skype?username=andry-zonov andry-zonov
<EMAIL_ADDRESS>From: Jesse Squires <notifications<EMAIL_ADDRESS>Reply-To: jessesquires/JSQMessagesViewController <reply<EMAIL_ADDRESS>Date: Friday 29 April 2016 at 19:03
To: jessesquires/JSQMessagesViewController <JSQMessagesViewController<EMAIL_ADDRESS>Cc: Andrey Zonov <Andrey.Zonov<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [jessesquires/JSQMessagesViewController] Add check for Object_replacement_character (#1324)
Hey @azonovhttps://github.com/azonov - one last ping before we close this and manually apply the fix.
Can you resolve conflicts and update the PR?
Also, there's a bunch of unrelated work here, right? We only want the changes in NSString+JSQMessages.m, correct?
// cc @eliburkehttps://github.com/eliburke
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/jessesquires/JSQMessagesViewController/pull/1324#issuecomment-215779460

thanks @azonov !
sometimes it's easier to just submit a new PR. let me know if that works better for you 😄

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


Error running for a single image

Hello,
I installed caffe and autocolarize, but when I try to run for a png image(512x512) I get the following error.
F0417 13:52:09.999788  2561 hdf5.cpp:79] Check failed: blob_dims == blob->shape() Cannot load blob from hdf5; shape mismatch. Source shape is 4096 25088 (102760448) target shape is 4096 512 7 7 (102760448)
This causes the code to abort. Does anyone know how to solve this issue?

I am receiving this as well.

I believe that in my personal Caffe I have relaxed the shape match requirements, allowing implicit reshapes. A quick fix is to take the HDF5 file and simply reshape the fc6 filters so that they agree with Caffe. I will look into how best I can fix this on my end.

The Caffe source code about shape match changed in release v1.0: #4630. Maybe the previous Caffe version works well.

met the same issue as GMNetto. @GMNetto Do you fix the issue with the latest caffe version?

Hello, I am currently trying to use autocolorize and I am having this problem as well. Can anyone tell me what they did in order to get it to work?

@gustavla I'm also running into this issue. Would you mind expanding a bit on your "quick fix" so I can get the code running -- I'm not sure what you mean exactly.

I have updated the weights file on the server to have shapes that should work without modifying Caffe. You just have to remove the cached weights file and the new will be automatically downloaded:
rm ~/.autocolorize/autocolorize.caffemodel.h5

Really sorry this took so long.


Bugfix: add memory-safe Vertex.SetCoords() method.

Fixes Issue #129
This is a minimal way to fix the issue, but it may be cleaner to only have one method vertex.SetCoords(int dim, double *p) instead of two, and change all the existing references to SetCoords().

Thanks Andrew!
I think the best thing is to leave the old version of SetCoords() for now, mark (it with a comment) as deprecated, and replace all its uses in the library with the new version.


Refactor App.vue

Issue description
Describe your issue in detail here
App.vue needs to be refactored in its entirety.

[ ] Session Settings are not supposed to be part of App.vue AT ALL
[ ] Naviagtion as its own component
[ ] Make Notifications a simpler component
[ ] Session Settings Popup a simpler Component integrated in the navigation

Definition Of Ready (DoR)
This issue can be worked on if

[ ] a developer is assigned
[x] the issue is labeled
[ ] the issue is assigned to the current sprint
[ ] the issue is estimated
[x] a meaningful title has been set
[x] the issue is described in detail

This maybe correlates with #162


o365-solutions

[Enter feedback here]

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

ID: ab55fc7e-f0eb-684a-cf8f-dd89990937c5
Version Independent ID: 6d7e6627-cc17-853c-6563-420e02f87f45
Content: Desktop Deployment Center - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/desktop-deployment-center-home.md
Service: o365-solutions
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

Hello @rupamcc. Can you please give us a little more information in your feedback?

@rupamcc We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if you see an improvement is required in the specific area of this documentation. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


SASS with Rollup

Hi!
Thank you for the project! It is more usefull. I migrated my factory of WebComponents to your software from WebComponentFactory. Your project is simplier. However, I have to doubts according to WCFactory:
First
Is it possible separate HTML, CSS, JS and properties in diferentes files? I think that it is better for programming. It is the model of Angular's Components. But it is not essential.
Second
I want to use SCSS. I saw the module rollup-plugin-scss and I tried to include in my rollup.config.js with this format.
 import createDefaultConfig from '@open-wc/building-rollup/modern-config';
 import scss from 'rollup-plugin-scss';

 const config = createDefaultConfig({ zinput: './src/index.html' });
 config.plugins.push(scss());

 export default config;

But fails: in ./src/style.scss 1:0; Module parse failed: Unexpected token (1:0); You may need an appropriate loader to handle this file type.

I am a bit confused, because that sounds like a webpack error. When are you seeing this error?

When I import a rollup module for CSS Processor, it fails. My question is: Is it possible to add SASS in open-wc?

This should work:
import createDefaultConfig from '@open-wc/building-rollup/modern-config';
import scss from 'rollup-plugin-scss';

const config = createDefaultConfig({ input: './src/index.html'});

export default {
  ...config,
  plugins: [
    ...config.plugins,
    scss({
      output: 'dist/styles.css'
    }),
  ],
};

If that works, lets add it to the readme 😁

It's pretty much what's under extending-the-rollup-config though, so it would be duplicate

OK, and how to use in a Web Component? It means...

the correct import in the main.js: static get styles() or render().
check in development: it generates .css in dist, when you run yarn build.

In the other hand, why doesn't open-wc bring it by default?

open-wc is very strict about build tools, we recommend that your code should run as is in the browser without any build tool requirements. Then build tools can be used for optimizing for production.
We did document how to add custom plugins to the build tools, but from there on we can't offer much help in how to configure these plugins.

Ok, thanks! But I think that SASS adds a huge valor to your framework. But it is your decision, not mine. Despite of, thanks for all!
If you don't know how to configure and use SASS in open-wc, close the issue and thanks for the comment: https://github.com/open-wc/open-wc/issues/419#issuecomment-490170656.

https://github.com/web-padawan/aybolit/ is a SASS-based WC framework alternative.

hey, I'm closing this as it seems the question has been answered.
Feel free to reopen or create another issue if there are still questions 🤗

FYI:
I found this magic library: https://github.com/bennypowers/rollup-plugin-lit-css
Why don't you integrate with your framework? Indeed, you could adding support to SASS.
I see this integration in the follow example: https://github.com/web-padawan/aybolit

We're not a framework, only a collection of tools.
We don't include it by default because your code will no longer run in the browser without building, which is what we don't recommend. For power users we do explain it in the readme: https://open-wc.org/building/building-rollup.html#import-css-files-in-lit-html

Jajaja, really thank you @LarsDenBakker !
I read your docummentacion, but not this section.
No comments in longer.


[explorer] Groups Owned Objects by Type

When viewing addresses and objects, the owned objects are first grouped by type. Upon clicking this leads to an individual object view.

https://user-images.githubusercontent.com/76067158/166522663-aa5d9c00-ecac-4909-9358-3832dfee2baf.mp4
Thanks for working on this! Here're a few high-level feedback(and synced with @bwann52 ):

we should have two sections for owned objects:
one section should be called Coins(placeholder, we might change it to Fungible Tokensor something else in the future, that contains all objects with type Coin<T>. We should aggregate by the T by default
The other section should be called Owned object(placeholder value) that contains all objects with other types. We SHOULD NOT aggregate them by default.

@bwann52 Could you add more feedback on content and other things if any?

no additional comments at this time. Thanks @666lcz @Andrew47

I've gone through the feedback and updated the PR.


Use non-cryptographic hash functions for fingerprinting

I propose to use fast non-cryptographic hash algorithms in the current implementation of shash (meaning stable/string/source/ any-other-s-word hash), which are not only fast but also more appropriate for fingerprinting.
I suggest to use the python bindings (https://github.com/Cyan4973/xxHash) to xxHash project (https://cyan4973.github.io/xxHash/), which seem to be the most efficient and up-to-date python and c implementations.

Still relevant?

Still relevant but mostly a small and not very important optimization. I think it can be safely close.


Prevent job failure when github workflows are cancelled

What does this PR do?
Handle the possible cancelled state raising from github as we will allow workflow cancellation to remove pressure on builds.

Merge the repack task with the test trigger: we must repack when a tarball is generated but bypass when we have no tarball in case of anticipated cancellation. To pass the information between workflow triggering and tarball generation it's easier to do this in a single task. Besides this task is purely ci-related (no need to launch it manually)
factorize the different trigger_macos_xxx task to handle the Exit code once for all. And Exit(1) only on failures

Motivation
We want to enable github workflow cancellation. As such we must handle situations where tarball is not generated during the test workflow. And allow cancelled jobs for build or linting.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


chore(browserify): de-yarn tests

This removes usages of "yarn" from browserify tests. Dep "throat" is no longer needed.

I thought this looked familiar.  Closed in lieu of #698


The virtual node of each element in the development environment is not updated

Version
3.0.5
Reproduction link
https://jsfiddle.net/tzhbwvjy/4/
Steps to reproduce
What is expected?
Console output should be false
What is actually happening?
Output true

const patchElement = (
n1: VNode,
n2: VNode,
parentComponent: ComponentInternalInstance | null,
parentSuspense: SuspenseBoundary | null,
isSVG: boolean,
optimized: boolean
) => {
const el = (n2.el = n1.el!)
if (DEV || FEATURE_PROD_DEVTOOLS) {
el.__vnode = n2
}
......

let a = {}
let b = a

expect(a === b).toBe(true)

let a = {}
let b = a

expect(a === b).toBe(true)

When the component is updated,n1 is not equal to n2

When the component is updated,n1 is not equal to n2

You shouldn't rely on __vnode as it's internal

You shouldn't rely on __vnode as it's internal

When the component is updated,n1 is not equal to n2

reference

When the component is updated,n1 is not equal to n2

reference


Add Copyrights information to cse-collector.go

The rule is if there is header in orginal one then keep it , if there is no header, then still keep it still, do not add any header, just mention in NOTICE like go- chassis

@wangkirin , Thanks for your suggestion, added the Copyrights in the NOTICE file


documentation formatting is broken for crds

some sections of the generated crd documentation are not being generated / formatted correctly, this can be seen here:
https://github.com/open-feature/open-feature-operator/blob/main/docs/crds.md#featureflagconfigurationspecflagdspecenvsindex

I can take this one !


Create _spark_metadata

Background
A tool that helps us to create _spark_metadata  folder and metadata files.
First version assumes checkpoint for data exists and contains at least one microbatch.
How spark structured streaming works:

Spark structured streaming runs in microbatch fashion
In every microbatch spark reads portion of data and process them
Every non-empty microbatch is numbered. Microbatches are monotonically increasing even between job restarts starting with 0
In every non-empty microbatch spark creates multiple files in different folders:

checkpoint folder with commits, metadata, offsets, sources subfolders:

offsets folder: For every microbatch: creates file with microbatch number name that contains offsets from which job read data
commits folder: For every successfully written offsets creates files with microbatch number name.

data destination folder (in case of file data writer) - along with written data spark creates files in _spark_metadata subfolder: /destinatnion/_spark_metadata/0 ,  /destinatnion/_spark_metadata/1, ... (for every microbatch creates file with microbatch number name):

every file contains references to written data and always starts with v1. Example:
v1 {"path":"hdfs://absolutePathToFile/fileName1.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632046,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://absolutePathToFile/fileName1.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"}
During writing metadata spark does metadata file compaction for N last files (by default 10, can be changed). Example with metadata compaction set to 3: 0, 1, 2.compact, 3, 4, 5.compact, 6, 7, 8.compact, 9, 10, 11.compact, 12, 13

Files 0, 1, 2.compact, 3, 4, 5.compact, 6, 7, 8.compact, 9, 10 are irrelevant and will be eventually deleted by spark
11.compact file contains all records from previous files: 8.compact, 9, 10 compacted into it and newly written data files references.
12, 13 files contains newly written data files references

Feature
Goal of this feature is to create tool that creates _spark_metadata folder under destination folder.
It should fail if:

destination folder does not exist or destination folder is empty
_spark_metadata folder already exists

Input should be:

Data folder path
Max microbatch number
Compaction number

Example 1:
Data folder path: /destination/
Data folder contains files: f1.snappy.parquet, f2.snappy.parquet, f3.snappy.parquet, f4.snappy.parquet, f5.snappy.parquet, f6.snappy.parquet, f7.snappy.parquet, f8.snappy.parquet, f9.snappy.parquet, f10.snappy.parquet
Tool input:

Data folder path: /destination
Max microbatch number: 9
Compaction number: 3

Tool result:
It will create _spark_metadata folder with following files (no need to create files: 0, 1, 2.compact 3 4 5.compact 6 7):
8.compact, 9
Content of files:

8.compact:

v1 {"path":"hdfs://destination/f1.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632046,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f2.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f3.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f4.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f5.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f6.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f7.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f8.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f9.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"}

9:

v1 {"path":"hdfs://destination/f10.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"}

Example 2:
Data folder path: /destination/
Data folder contains files: f1.snappy.parquet, f2.snappy.parquet, f3.snappy.parquet
Tool input:

Data folder path: /destination
Max microbatch number: 2
Compaction number: 3

Tool result:
It will create _spark_metadata folder with following files:
0, 1
Content of files:

0:

v1 {"path":"hdfs://destination/f1.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632046,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f2.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"}

1:

v1 {"path":"hdfs://destination/f3.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"}

Example 3:
Data folder path: /destination/
Data folder contains files: f1.snappy.parquet, f2.snappy.parquet, f3.snappy.parquet, f4.snappy.parquet, f5.snappy.parquet, f6.snappy.parquet, f7.snappy.parquet, f8.snappy.parquet, f9.snappy.parquet, f10.snappy.parquet
Tool input:

Data folder path: /destination
Max microbatch number: 8
Compaction number: 3

Tool result:
It will create _spark_metadata folder with following files (no need to create files: 0, 1, 2.compact 3 4 5.compact 6 7):
8.compact
Content of files:

8.compact:

v1 {"path":"hdfs://destination/f1.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632046,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f2.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f3.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f4.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f5.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f6.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f7.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f8.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f9.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"} {"path":"hdfs://destination/f10.snappy.parquet","size":8884,"isDir":false,"modificationTime":1672752632047,"blockReplication":3,"blockSize":134217728,"action":"add"}

It's tested and it works on all storages, however I have question about the --max-micro-batch-number. How should the tool behave when the number doesn't match the number of files in directory? Current implementation trims the size of files to provided max microbatch number and then adds all the files up to last compaction number to _spark_metadata/<last_compaction_number>.compact and the rest is written in non compacted metadata files.
However this feels horribly wrong.
Wouldn't it be much better ignore the max micro batch number option? Or should I rather create metadata files up to max compaction number and rest should be written in compacted metadata? Wouldn't there be issue when compacted metadata are empty?
Lets have 25 data files in directory. Here are options, that came to my mind with some counter examples:
Option 1 (Ignore --max-micro-batch-number)
max micro batch number is derived from number of part files in directory. Everything should work as expected, only one disadvantage is that you are unable to change max-micro-batch-number if you need to. Which is not really an counter example.
Option 2 (aligned to --max-micro-batch-number)
There is guarantee that we have always latest metadata file with name _spark_metadata/<max_micro_batch_number>. There is also sequence of metadata files from <last_compaction>.compat .. <max_micro_batch_number>,
where each metadata file contains exactly one entry and compaction file contains the rest (which might be 0 entries).
Counter example: let's set --compaction-number 50 --max-micro-batch-number 80. This will create non compacted metadata files 55 .. 80. There would be no compacted metadata file, even there should be.


harmonyMap configs stored in query cache

the result is that once a harmonyMap is applied to a query, it is retained for all subsequent executions.  this can be easily resolved with cache manipulation, or by interrogating the query prior to (re)caching

It is probably the case that all post-retrieval processing artifacts, e.g., YADAQueryResult objects are retained in the query objects in the cache as well.

This could also create concurrency problems. short term workaround...turning off the cache for now.

Actually, Finder already does what it's supposed to, creating a new YADAQuery object with the constructor call public YADAQuery(YADAQuery yq) which sets the new object vitals to the old object vales.  It is easiest to omit any request-specific parameter values like harmonyMap here in this constructor.


Create resolver that will fill in Reference Block ID automatically if not present for transactions.

Create resolver that will fill in Reference Block ID automatically if not present for transactions.
Expected Outcomes

[ ] A Resolver is created which fills in Reference block IDs if they're not present.
[] Resolver is added to FCL

handled in #254


[Feature Request] Adding a few consoles and handhelds from lr-mess

I was wondering if it would be possible to add these consoles with lr-mess via Retroarch. I'm mainly testing the consoles on the Android side using a RG353V device. I did put some results below.
TimeTop GameKing - lr-mess Android OK
TimeTop GameKing 3 - lr-mess Android NG, works on standalone MAME4droid 2024 (0.268)
Hartung Game Master - lr-mess Android OK
Epoch Game Pocket Computer - lr-mess Android OK
Casio PV-1000 - lr-mess Android NG, does work on AmberElec
Bit Corp Gamate - lr-mess Android OK
Casio PV-2000 - lr-mess Android OK, needs special controls
For Casio PV-2000 specifically, it emulates a keyboard on MAME/MESS, but I've figured out the controls for both players:
PLAYER 1
Enter > START
Yen > SELECT
Attack 0 > ATTACK 0
Attack 1 > ATTACK 1
Cursor Up > UP
Cursor Down > DOWN
Cursor Left > LEFT
Cursor Right > RIGHT
PLAYER 2
IN4_1 > START
IN4_2 > SELECT
IN8_2 > ATTACK 0
IN8_3 > ATTACK 1
IN7_3 > UP
IN6_2 > DOWN
IN7_2 > LEFT
IN6_3 > RIGHT
It's quite a big request, but thanks for taking the time to read it.

Have you tested any of these under ArkOS and confirmed functionality?

Is there an easy way to test the roms under ArkOS? I could test them and provide results.

Run them through retroarch directly.  There should be a retroarch and retroarch32 option under the retroarch system menu option.

Tested the systems via lr-mess on ArkOS:
TimeTop GameKing - OK
TimeTop GameKing 3 - NG
Hartung Game Master - OK
Epoch Game Pocket Computer - crackly audio
Casio PV-1000 - screen resolution incorrect, otherwise sound and controls OK
Bit Corp Gamate - OK
Casio PV-2000 - have to set up controls but otherwise OK


Validation error

The current version of aurelia-breeze 2.2.0 does not work correctly with this example (https://plnkr.co/edit/XMmSqT?p=preview), it validates but does not render the error. Is there any fix that I can do? Any other example with a more current version? Do you have any other way to show your mistakes? thank you
Obs: the last version that I managed to make it work was 1.0.0

I noticed the same thing. Maybe this functionality has been removed but the documentation hasn't been updated.
Chris

form validation was removed from aurelia-breeze but you can add the breeze-validation custom attribute directly to your project:
https://github.com/jdanyow/aurelia-breeze/tree/ef682ff95d4fe89d22788449185715b03776d823/src/validation

@jdanyow
Is this the best way? I tried to integrate with aurelia-validation but I had problems see:
Http://stackoverflow.com/questions/43232972/implement-aurelia-breeze-validation?noredirect=1#comment73544257_43232972