April 2024 CPU - JDK22 Triage

Release Summary Report for release-openjdk22-pipeline
Warning: The release summary report is not yet complete. Currently, it only contains partial results.
Report generated at: Thu, 18 Apr 2024 11:42:45 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk22-pipeline/15/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk22u" build number 216 at 4/18/2024, 4:57:18 AM

✔ results in these Tables means the activity has successfully completed.
⏳ results means that we are actively working on closing off the runs needed for this version, platform, binaryType.
⛔ means there is no build planned for that version/platform combination.
⏸ means activity not yet started.

Platform
Status
Results
Actions

x86-64_mac
✔
comment

x86-64_linux
✔
comment

x86-64_windows
✔
comment

aarch64_linux
✔
comment

aarch64_mac
✔
comment
ACTIONS : https://github.com/adoptium/aqa-tests/issues/5156#issuecomment-2008018350

x86-64_alpine-linux
✔
comment

ppc64le_linux
✔
comment

s390x_linux
⏸
comment

ppc64_aix
⛔
comment
same 2 jdk_foreign testcases as failed and blocked a release in March

aarch64_alpine-Linux
✔
comment

riscv64_linux
✔
comment

Test_openjdk22_hs_extended.perf_x86-64_mac.tap.txt
Test_openjdk22_hs_sanity.perf_x86-64_mac.tap.txt

aarch64_linux
Test_openjdk22_hs_extended.openjdk_aarch64_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_aarch64_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_aarch64_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_tools_1 => deep history 0/6 passed | possible issues
jdk_build_0 => deep history 29/33 passed | possible issues
Test_openjdk22_hs_extended.openjdk_aarch64_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_jdi_0 => deep history 1/8 passed | possible issues
jdk_build_1 => deep history 3/8 passed | possible issues
jdk_jdi_1 => deep history 26/33 passed | possible issues

aarch64_mac
Test_openjdk22_hs_extended.openjdk_aarch64_mac ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_aarch64_mac_rerun ✅ SUCCESS ✅
Rerun all
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode)

x86-64_linux
sanity.openjdk with testcase failure
not ok 1 - jdk_lang_0
  ---
    output:
      |
        Failed test cases:
        TEST: java/lang/Thread/virtual/stress/GetStackTraceALotWhenPinned.java#id0
        Test results: passed: 1,009; error: 1
    duration_ms: 4384700
  ...
not ok 2 - jdk_lang_1
  ---
    output:
      |
        Failed test cases:
        TEST: java/lang/Thread/virtual/stress/GetStackTraceALotWhenPinned.java#id0
        Test results: passed: 1,009; error: 1
    duration_ms: 4596046
  ...

extended.openjdk pending
other top-level targets passing (artifacts here)

aarch64_alpine-linux
Test_openjdk22_hs_extended.openjdk_aarch64_alpine-linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_aarch64_alpine-linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_aarch64_alpine-linux_testList_0 ⚠ UNSTABLE ⚠
jdk_nio_0 => deep history 4/10 passed | possible issues
Test_openjdk22_hs_extended.openjdk_aarch64_alpine-linux_testList_2 ⚠ UNSTABLE ⚠
jdk_build_0 => deep history 0/10 passed | possible issues
jdk_nio_1 => deep history 6/15 passed | possible issues
jdk_build_1 => deep history 0/15 passed | possible issues

x86-64_mac
Test_openjdk22_hs_sanity.perf_x86-64_mac ❌ ABORTED ❌
Test_openjdk22_hs_special.functional_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode)

Test_openjdk22_hs_extended.perf_x86-64_mac ❌ ABORTED ❌
Test_openjdk22_hs_sanity.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode)

x86-64_windows
Test_openjdk22_hs_extended.openjdk_x86-64_windows ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_x86-64_windows_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

Test_openjdk22_hs_special.functional_x86-64_windows ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

MBCS_Tests_formatter_tw_windows_0 => deep history 4/24 passed | possible issues
Test_openjdk22_hs_special.functional_x86-64_windows_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

x86-64_alpine-linux
Test_openjdk22_hs_extended.openjdk_x86-64_alpine-linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_x86-64_alpine-linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_x86-64_alpine-linux_testList_2 ⚠ UNSTABLE ⚠
jdk_build_0 => deep history 0/6 passed | possible issues
jdk_nio_1 => deep history 12/19 passed | possible issues
jdk_build_1 => deep history 0/18 passed | possible issues

ppc64le_linux
Test_openjdk22_hs_extended.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_ppc64le_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

s390x_linux
Release Summary Report for release-openjdk22-pipeline
Warning: The release summary report is not yet complete. Currently, it only contains partial results.
Report generated at: Sat, 20 Apr 2024 14:56:40 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk22-pipeline/18/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk22u" build number 216 at 4/20/2024, 10:29:00 AM
Pending

ppc64_aix
Test_openjdk22_hs_sanity.openjdk_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode)

jdk_foreign_0 => deep history 3/26 passed | possible issues
jdk_foreign_1 => deep history 3/25 passed | possible issues
Test_openjdk22_hs_sanity.openjdk_ppc64_aix_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode)

Test_openjdk22_hs_sanity.perf_x86-64_mac ❌ ABORTED ❌
Test_openjdk22_hs_special.functional_ppc64_aix ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode)

MBCS_Tests_formatter_Zh_TW_aix_0 => deep history 8/25 passed | possible issues
MBCS_Tests_formatter_zh_TW_aix_0 => deep history 8/25 passed | possible issues
MBCS_Tests_formatter_ZH_TW_aix_0 => deep history 8/25 passed | possible issues
MBCS_Tests_i18n_ko_KR_aix_0 => deep history 11/25 passed | possible issues
MBCS_Tests_i18n_KO_KR_aix_0 => deep history 11/25 passed | possible issues
Test_openjdk22_hs_special.functional_ppc64_aix_rerun ✅ SUCCESS ✅
Rerun all
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode)

riscv64_linux
Test_openjdk22_hs_special.functional_riscv64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

MBCS_Tests_i18n_ko_KR_linux_0 => deep history 2/6 passed | possible issues
MBCS_Tests_formatter_zh_TW_linux_0 => deep history 2/6 passed | possible issues
Test_openjdk22_hs_special.functional_riscv64_linux_rerun ✅ SUCCESS ✅
Rerun all
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

Test_openjdk22_hs_sanity.openjdk_riscv64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

jdk_lang_1 => deep history 3/6 passed | possible issues
jdk_util_0 => deep history 2/6 passed | possible issues
jdk_util_1 => deep history 5/6 passed | possible issues
Test_openjdk22_hs_sanity.openjdk_riscv64_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_riscv64_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_riscv64_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-22.0.1+8 (build 22.0.1+8)
OpenJDK 64-Bit Server VM Temurin-22.0.1+8 (build 22.0.1+8, mixed mode, sharing)

Test_openjdk22_hs_extended.openjdk_riscv64_linux_testList_0 ⚠ UNSTABLE ⚠
hotspot_serviceability_jvmti_0 => deep history 1/6 passed | possible issues
jdk_tools_0 => deep history 2/3 passed | possible issues
Test_openjdk22_hs_extended.openjdk_riscv64_linux_testList_1 ⚠ UNSTABLE ⚠
jdk_security3_1 => deep history 3/6 passed | possible issues
jdk_jfr_1 => deep history 1/3 passed | possible issues
Test_openjdk22_hs_extended.openjdk_riscv64_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_jmx_0 => deep history 1/2 passed | possible issues
jdk_jfr_0 => deep history 1/2 passed | possible issues

s390x_linux
Release Summary Report for release-openjdk22-pipeline
Report generated at: Tue, 23 Apr 2024 11:01:21 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk22-pipeline/21/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk22u" build number 216 at 22/04/2024, 13:31:35

jdk22u-release-linux-s390x-temurin ⚠ UNSTABLE ⚠
refactor_openjdk_release_tool ❌ undefined ❌
sign_temurin_gpg ❌ undefined ❌

Test_openjdk22_hs_extended.openjdk_s390x_linux ⚠ UNSTABLE ⚠
Test_openjdk22_hs_extended.openjdk_s390x_linux_rerun ✅ SUCCESS ✅
Rerun all
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (build 22.0.1+1)
OpenJDK 64-Bit Server VM Temurin-<IP_ADDRESS>+1 (build 22.0.1+1, mixed mode, sharing)

Test_openjdk22_hs_sanity.openjdk_s390x_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (build 22.0.1+1)
OpenJDK 64-Bit Server VM Temurin-<IP_ADDRESS>+1 (build 22.0.1+1, mixed mode, sharing)

jdk_foreign_0 => deep history 15/25 passed | possible issues
jdk_foreign_1 => deep history 18/24 passed | possible issues
Test_openjdk22_hs_sanity.openjdk_s390x_linux_rerun ✅ SUCCESS ✅
Rerun all
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (build 22.0.1+1)
OpenJDK 64-Bit Server VM Temurin-<IP_ADDRESS>+1 (build 22.0.1+1, mixed mode, sharing)

Test_openjdk22_hs_sanity.system_s390x_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (build 22.0.1+1)
OpenJDK 64-Bit Server VM Temurin-<IP_ADDRESS>+1 (build 22.0.1+1, mixed mode, sharing)

TestJlmRemoteClassAuth_0 => deep history 18/25 passed | possible issues
TestJlmRemoteClassAuth_1 => deep history 18/25 passed | possible issues
TestJlmRemoteClassNoAuth_0 => deep history 18/25 passed | possible issues
TestJlmRemoteClassNoAuth_1 => deep history 18/25 passed | possible issues
TestJlmRemoteMemoryAuth_0 => deep history 18/25 passed | possible issues
TestJlmRemoteMemoryAuth_1 => deep history 18/25 passed | possible issues
TestJlmRemoteMemoryNoAuth_0 => deep history 18/25 passed | possible issues
TestJlmRemoteMemoryNoAuth_1 => deep history 18/25 passed | possible issues
TestJlmRemoteNotifierProxyAuth_0 => deep history 18/25 passed | possible issues
TestJlmRemoteNotifierProxyAuth_1 => deep history 18/25 passed | possible issues
TestJlmRemoteThreadAuth_0 => deep history 18/25 passed | possible issues
TestJlmRemoteThreadAuth_1 => deep history 18/25 passed | possible issues
TestJlmRemoteThreadNoAuth_0 => deep history 18/25 passed | possible issues
TestJlmRemoteThreadNoAuth_1 => deep history 18/25 passed | possible issues
NioLoadTest_5m_0 => deep history 18/25 passed | possible issues
NioLoadTest_5m_1 => deep history 18/25 passed | possible issues
Test_openjdk22_hs_sanity.system_s390x_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (build 22.0.1+1)
OpenJDK 64-Bit Server VM Temurin-<IP_ADDRESS>+1 (build 22.0.1+1, mixed mode, sharing)

Test_openjdk22_hs_special.functional_s390x_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (build 22.0.1+1)
OpenJDK 64-Bit Server VM Temurin-<IP_ADDRESS>+1 (build 22.0.1+1, mixed mode, sharing)

MBCS_Tests_formatter_zh_TW_linux_0 => deep history 12/23 passed | possible issues
MBCS_Tests_i18n_ko_KR_linux_0 => deep history 13/23 passed | possible issues
Test_openjdk22_hs_special.functional_s390x_linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment Temurin-<IP_ADDRESS>+1 (build 22.0.1+1)
OpenJDK 64-Bit Server VM Temurin-<IP_ADDRESS>+1 (build 22.0.1+1, mixed mode, sharing)

@Haroon-Khel re: https://github.com/adoptium/aqa-tests/issues/5235#issuecomment-2072010551
sanity.system for s390x failing on test-marist-rhel7-s390x-2 with "No route to host issues", suggest rerunning on machine that is configured properly.
special.functional 2 MBCS testcase failures are known (same ones seen in March) and should have been excluded or fixed before the April release, considered non-blocking

Noting as Grinders will disappear.
The SuspendResume1 failure on ppc64le is curious. It worked in a full suite run but failed in the CUSTOM run due to missing library. I think the library should be available, but need to understand where it should come from and then why it's missing.
[2024-04-19T13:49:11.821Z] command: main -Djava.util.concurrent.ForkJoinPool.common.parallelism=1 -agentlib:SuspendResume1 SuspendResume1
[2024-04-19T13:49:11.821Z] reason: User specified action: run main/othervm/native/timeout=600 -Djava.util.concurrent.ForkJoinPool.common.parallelism=1 -agentlib:SuspendResume1 SuspendResume1
[2024-04-19T13:49:11.821Z] started: Fri Apr 19 13:49:11 UTC 2024
[2024-04-19T13:49:11.821Z] Mode: othervm [/othervm specified]
[2024-04-19T13:49:11.821Z] finished: Fri Apr 19 13:49:11 UTC 2024
[2024-04-19T13:49:11.821Z] elapsed time (seconds): 0.01
[2024-04-19T13:49:11.821Z] configuration:
[2024-04-19T13:49:11.821Z] STDOUT:
[2024-04-19T13:49:11.821Z] Error occurred during initialization of VM
[2024-04-19T13:49:11.821Z] Could not find agent library SuspendResume1 on the library path, with error: libSuspendResume1.so: cannot open shared object file: No such file or directory
[2024-04-19T13:49:11.821Z] STDERR:

re: https://github.com/adoptium/aqa-tests/issues/5235#issuecomment-2075693321, @jiekang - can you raise a new aqa-tests issue for this, also seen in March, likely a framework problem, when we run individual native testcases via JDK_CUSTOM that need the native testlibrary in order to run, and even though it is present, they are not able to see/find it.  See also https://github.com/adoptium/aqa-tests/issues/5156#issuecomment-2008023190.

re: #5235 (comment), @jiekang - can you raise a new aqa-tests issue for this, also seen in March, likely a framework problem, when we run individual native testcases via JDK_CUSTOM that need the native testlibrary in order to run, and even though it is present, they are not able to see/find it. See also #5156 (comment).

Sure; raised as https://github.com/adoptium/aqa-tests/issues/5264


GitHub's Community profile recommendations

https://github.com/dbazhenov/awesome-pmm/community

Checklist passed.


danger-py-cov v0.1

Warnings

:warning:
Please add the changelog entry to CHANGELOG.md file

Current coverage is 100.00%
No source changes affecting the coverage found

  Generated by :no_entry_sign: danger-python against c86d807ae71a9633c8c93e34af498c35307718a6


1.10.2 Farming station does not pick up apples with Dark Oak

Issue Description:
When attempting to farm Dark Oak with Farming station it does not collect the apples.
What happens:
Farming station does not collect Dark Oak apples
What you expected to happen:
Farming station collects apples and exports them
Steps to reproduce:

Create farming station
Farm Dark Oak

Affected Versions (Do not use "latest"):

EnderIO: 3.1.190
EnderCore: <IP_ADDRESS>-beta
Minecraft: 1.10.2
Forge: 1.10.2-<IP_ADDRESS>1-universal.jar

Your most recent log file where the issue was present:
http://puu.sh/wiHfg/50425f51bf.log

This

Still Occurs
Also applies to normal oak trees


Payload for Action too long (because measureands are queried that are not in the list)

Describe the bug
OCPP integration generates error in home assistant log. Measurands are updated but are then invalidated as soon as the error occurs, leading to unavailable values. Charge can not be started or stopped.
To Reproduce

Install OCPP 0.5.8
Configure using GUI with measurands "Power.Active.Import,Power.Offered,Current.Import,Current.Offered"
Reboot.
Entities will update after a while, then become unavailable quickly after. Log shows error (see below)

Expected behavior
Values should not become "unavailable" after update.
Additional context
The Log:
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/ocpp/messages.py", line 226, in validate_payload
    validator.validate(message.payload)
  File "/usr/local/lib/python3.12/site-packages/jsonschema/validators.py", line 435, in validate
    raise error
jsonschema.exceptions.ValidationError: 'Current.Export.L1,Current.Export.L2,Current.Export.L3,Current.Import.L1,Current.Import.L2,Current.Import.L3,Current.Offered,Energy.Active.Export.Interval,Energy.Active.Export.Register,Energy.Active.Import.Interval,Energy.Active.Import.Register,Energy.Reactive.Export.Interval,Energy.Reactive.Export.Register,Energy.Reactive.Import.Interval,Energy.Reactive.Import.Register,Frequency,Power.Active.Export,Power.Active.Import,Power.Factor,Power.Offered,Power.Reactive.Export,Power.Reactive.Import,RPM,SoC,Temperature,Voltage.L1-N,Voltage.L2-N,Voltage.L3-N' is too long

Failed validating 'maxLength' in schema['properties']['configurationKey']['items']['properties']['value']:
    {'maxLength': 500, 'type': 'string'}

On instance['configurationKey'][0]['value']:
    'Current.Export.L1,Current.Export.L2,Current.Export.L3,Current.Import.L1,Current.Import.L2,Current.Import.L3,Current.Offered,Energy.Active.Export.Interval,Energy.Active.Export.Register,Energy.Active.Import.Interval,Energy.Active.Import.Register,Energy.Reactive.Export.Interval,Energy.Reactive.Export.Register,Energy.Reactive.Import.Interval,Energy.Reactive.Import.Register,Frequency,Power.Active.Export,Power.Active.Import,Power.Factor,Power.Offered,Power.Reactive.Export,Power.Reactive.Import,RPM,SoC,Temperature,Voltage.L1-N,Voltage.L2-N,Voltage.L3-N'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/ocpp/api.py", line 1023, in run
    await asyncio.gather(*self.tasks)
  File "/config/custom_components/ocpp/api.py", line 468, in post_connect
    chgr_measurands = await self.get_configuration(key)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/ocpp/api.py", line 890, in get_configuration
    resp = await self.call(req)
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/ocpp/charge_point.py", line 422, in call
    validate_payload(response, self._ocpp_version)
  File "/usr/local/lib/python3.12/site-packages/ocpp/messages.py", line 240, in validate_payload
    raise TypeConstraintViolationError(
ocpp.exceptions.TypeConstraintViolationError: TypeConstraintViolationError: Payload for Action is syntactically correct but at least one of the fields violates data type constraints (e.g. “somestring”: 12),  {'cause': "'Current.Export.L1,Current.Export.L2,Current.Export.L3,Current.Import.L1,Current.Import.L2,Current.Import.L3,Current.Offered,Energy.Active.Export.Interval,Energy.Active.Export.Register,Energy.Active.Import.Interval,Energy.Active.Import.Register,Energy.Reactive.Export.Interval,Energy.Reactive.Export.Register,Energy.Reactive.Import.Interval,Energy.Reactive.Import.Register,Frequency,Power.Active.Export,Power.Active.Import,Power.Factor,Power.Offered,Power.Reactive.Export,Power.Reactive.Import,RPM,SoC,Temperature,Voltage.L1-N,Voltage.L2-N,Voltage.L3-N' is too long", 'ocpp_message': <CallResult - unique_id=33442100-6423-4b2d-888e-d36289e18866, action=GetConfiguration, payload={'unknownKey': [], 'configurationKey': [{'readonly': False, 'key': 'MeterValuesSampledData', 'value': 'Current.Export.L1,Current.Export.L2,Current.Export.L3,Current.Import.L1,Current.Import.L2,Current.Import.L3,Current.Offered,Energy.Active.Export.Interval,Energy.Active.Export.Register,Energy.Active.Import.Interval,Energy.Active.Import.Register,Energy.Reactive.Export.Interval,Energy.Reactive.Export.Register,Energy.Reactive.Import.Interval,Energy.Reactive.Import.Register,Frequency,Power.Active.Export,Power.Active.Import,Power.Factor,Power.Offered,Power.Reactive.Export,Power.Reactive.Import,RPM,SoC,Temperature,Voltage.L1-N,Voltage.L2-N,Voltage.L3-N'}]}>}

I also tried:
As per  #1150  I have edited the "monitored_variables" in /config/.storage/core.config_entries to only include the above mentioned measurands. But as the log shows, far more measureands seem to be called for than listed in this variable. For example Current.Export.L3 even though there are no Export measureands in the list.
I wanted to try editing the max length as stated in #1155 but I can't find where to edit the code:
"chargeBoxSerialNumber": {
        "type": "string",
        "maxLength": 33
    },

(of course, in my case, that would probably be "ocpp_message" not "chargeBoxSerialNumber")
Does anyone have any idea how to work around this for now? I tried installing an old version (0.4.42) in the hope that the automatic detection of supported measurands that was added with 0.5. was the culprit. But that install did not work as i hoped.

Okay, after digging a bit further here are my new findings:

The error seems to occur due to the length limit of the GetConfigurationRequest (see here: GitHub:ocpp/GetConfiguration ). It is limited to 50 characters. The request made is 551 characters long.
Changing this manually requires either changing the request made by this integration (as far as I understand, I might be wrong) or changing the max accepted length in the python module schema description. (See link above)

I am going to try to change this manually in the definition for now to see if that is a temporary fix.

Have a look at https://github.com/djiesr/ocpp which makes various changes to support incompatible ocpp1.6 firmware

You can comment out line 468, and define accepted_measurands with the measurands your charger supports.

Thanks @drc38 that workaround does indeed work.
I did have to uncomment another line of code where the additional measureands were appended, but with a few changes to the code it now works.
I do wonder if I am the only user that has this problem. To me, this looks like something everyone should encounter, after all it's not like I put in too many measurands. Even the "default" measurands are too many for the string lenght limit, set by the ocpp Python Module (if I understand this correctly).
(Maybe I am the only one who updates a running system. "Never change a running system" and all.)

As far as I can see, the error is due to the charger reporting a configured set of measurands that exceed the length limit of 500 characters in the spec. Maybe that is the default setting for the charger. This exception could simply be caught, I don't see a reason why that would cause any issue.

If caught another error would be thrown as the measurands reported are also not correct. See https://github.com/mobilityhouse/ocpp/blob/master/ocpp/v16/enums.py eg current.import vs current.import.L1

If caught another error would be thrown as the measurands reported are also not correct. See https://github.com/mobilityhouse/ocpp/blob/master/ocpp/v16/enums.py eg current.import vs current.import.L1

Aren't the erroneous measurands simply reconfigured here, so afterwards the reports are fine?

If caught another error would be thrown as the measurands reported are also not correct. See https://github.com/mobilityhouse/ocpp/blob/master/ocpp/v16/enums.py eg current.import vs current.import.L1

Ignore this, I see in the spec it is valid to append the phase to the measurand.

v0.5.12 supports manual configuration of the measurands which will then avoid this.


fix maintainerId to match githubId

See failing test in https://github.com/helm/charts/pull/7039 .
The id of the maintainer does not match the githubid and thus tests fail: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/helm_charts/7039/pull-charts-e2e/12136/

/assign @shashidharatd

Was fixed in #7039


ADBDEV-4533: gpbackup does not use shared snapshot for first table in worker processes

gpbackup does not use shared snapshot for first table in worker processes
gpbackup:

creates a connection pool
opens transactions for each connection
takes and exports a shared snapshot of the first connection
spawns worker processes for all connections (except the first one),
which perform the following actions:
a) if the transaction is not yet open, then it is opened and
the shared snapshot from step 3 is imported into it
b) the table is copied using the COPY command
c) if there is a shared snapshot, then the transaction is closed
d) go to step 4.a

As a result, the first time step 4.a is skipped when copying the first
table in the worker process, because the transaction was opened in step 2.
The solution is to close the open transaction (after step 4 and before step
4.a) to open a new transaction with the shared snapshot below (at step 4.a).
A check has been added to the tests to ensure that the first table is also
processed in the shared snapshot.

small remarks:
1. `gpbackup don't use` -> `gpbackup doesn't use`

2. `if a transaction isn't started, will start new once and import snapshot` -> `if a transaction isn't started, it will be start new once and snapshot will be import ` ? (I don't understand the end of sentence)

3. `The solution is close opened transaction` -> `The solution is to close open transaction`

I updated description


Remove access to Sprigs env and expandenv functions

What happened?
Excluding Sprig's functions related to accessing the pod/host environment could enhance the security posture.
The current approach integrates all of Sprig's offerings, notably the "env" and "expandenv" functions. However, it's worth noting that other projects leveraging Sprig, such as Helm and ArgoCD, consciously omit these particular functions.
The Sprig documentation itself cautions against the potential for information leakage through these functions, as detailed here: Sprig Documentation.
Considering that typical use cases involving GoTemplate doesn't require fetching runtime environment variables, it seems prudent to reconsider including these capabilities.
I'd appreciate your thoughts on this matter. Thank you!

I've sent a small fix in #68

I believe there is less risk here because the code being executed should have been written by a Composition author or another highly privileged user. However, I do think it would be better not to encourage such practices too.

Only allowing prefixed variable names (like FN_GO_TPL_MY_VAR) would be an alternative that's more secure but doesn't remove the possibility of using env vars. What do you think?

@j2L4e That approach sounds like an interesting middle-ground.
For reference, here you can see Helm explicitly removing these two:
https://github.com/helm/helm/blob/c7f318ca4c0687292e258474134afec691054cd1/pkg/engine/funcs.go#L46
And so does ArgoCD (argo also removes getHostByName):
https://github.com/argoproj/argo-cd/blob/3cc02779ca8c9711934f38ee43f612e18c756d0e/server/deeplinks/deeplinks.go#L24
It might be valuable to align with these and do a similar thing here. Are there any valid use cases for this function sourcing values from the environment?
@phisco I agree that usually it's a highly (highest?) privileged user doing the deployment. Might not be the case always though and then it's possible to use the composition function pod as a way of learning more about the compute environment.
I'm wondering if there's an example architectural use case of wanting to source things from the environment of the functions pod? It would be helpful to find some to reason about this more.


Other matrices

Won't get to it now, but it'll probably be useful at some point to have

InfRandTridiagonal
InfRandSymTridiagonal
InfRandBidiagonal

with a LazyBandedMatrices extension

Why would these be needed? Just use Tridiagonal with InfRandomVector

Convenience mostly.

You could add these as type aliases with constructors

When the types of the bands are the same you can also just use LinearAlgebra.SymTridiagonal.


GitHub integration

Current work in progress.
Adding Github sync support.

Already have the sync functionality built it but the setup UI looks a little "clunky", due to the added fields, and I would like to address that prior to submitting the PR for review.

Hi, that's very nice work! Didn't got notified of the PR but will have a look in the evening!

Sounds great!  Sorry, I kept it as a draft PR because I wanted to cleanup the Setup UI.  If you want me to submit it as an actual request regardless let me know.

@riedeljan I made a few extra changes, and separated out the logic some more.  Please have a look and if any changes need to be made feel free to let me know!

Thank you so much, the changes look good to me so far! They go straight in the direction I wanted to refactor the code anyway - will review later! (: Really busy rn but love them!

Btw: if you'd like to chat about this MR, the plugin or programming in general: feel free to hit me up via the address in the package.json (:

All changes that were requested have since been implemented as of https://github.com/riedeljan/insomnia-universal-git/pull/5/commits/e1fd661a848b7153a6efb2932402e7f5216c6e84

Are the buttons broken for you too? Screenshotted with :dev build.

The Setup-Layout looks a bit broken to me rn, but I can quickly fix that later. Been there done that

Any updates from that review? @riedeljan


Meshlibrary not saving CollisionShape3D when exported

Godot version
4.0.2.stable
System information
Arch Linux, AMD 3900X, AMD Radeon RX 570
Issue description
I have created a mesh scene called "cube" with nodes as follows:

StaticBody3D (root node)

MeshInstance3D
CollisionShape3D

After saving the "cube" scene, I converted it into a MeshLibrary and imported that MeshLibrary into a GridMap scene.
The issue is that collision detection does not work for the imported MeshInstance3D objects into the GridMap scene. Collisions are only detected if I manually go to the GridMap scene, click on the MeshLibrary, go to the MeshInstance3D node, and re-add a BoxShape3D to the shapes array.
Or
Go to the MeshLibrary itself and add the BoxShape to it if it is missing.
Steps to reproduce

Create a "cube" scene with the following node structure:

StaticBody3D (root node)
- MeshInstance3D
- CollisionShape3D

Save the "cube" scene.

4.0 Convert the "cube" scene to a MeshLibrary.
4.0.1 Import the MeshLibrary into a GridMap scene.
4.0.2 Instantiate a mesh object from the MeshLibrary in the GridMap scene.
4.0.3 Test collision detection with the instantiated object in the GridMap scene.
or
4.1 Open the MeshLibrary directly and look for the shapes in the inspector.
Minimal reproduction project
N/A

See MeshLibrary and GridMap documentation that you can find here
The MeshLibrary scene export expects the StaticBody3D nodes to be a direct child of the MeshInstance3D
Sme with NavigationRegion3D in case you want to scene export NavigationMeshes as well.

Cool, thanks, this worked out. Funnily enough I was already looking at the linked doc before coming back here to close the issue.
Was following a slightly old post about this and it didn't mention the static body being the child of the mesh instead.
Closing the issue. Thanks for the help.


mmseqs2 createdb crashes "Illegal instruction"

Hi there,
I encountered a weird behavior when trying to run createdb on an HPC cluster (see below). It looks like machines with less than <= 64GB RAM are unable to run createdb properly while higher RAM machines are (the input file is attached). Does it make sense or maybe I'm missing something? What are the minimum RAM requirements for running mmseqs2 (couldn't find it in the program docs)? Btw, these 2 machines use the same storage so it shouldn't be the issue.
I appreciate your assistance. Thanks!
This is the exact command I'm trying to run:
[64GB RAM machine]$ mmseqs createdb ~/test/outputs/01_ORFs/GCF_000481805.1_Pseu_aeru_JJ692_V1_genomic.01_ORFs.txt ~/test/outputs/02_dbs/GCF_000481805.1_Pseu_aeru_JJ692_V1_genomic -v 3
MMseqs Version:       	3513001d33301f7eaaf58e60a1376488ff017354
Database type         	0
Shuffle input database	true
Createdb mode         	0
Offset of numeric ids 	0
Compressed            	0
Verbosity             	3
Converting sequences
[6162] 0s 561ms
Illegal instruction
[128GB RAM machine]$ mmseqs createdb ~/test/outputs/01_ORFs/GCF_000481805.1_Pseu_aeru_JJ692_V1_genomic.01_ORFs.txt ~/test/outputs/02_dbs/GCF_000481805.1_Pseu_aeru_JJ692_V1_genomic -v 3
MMseqs Version:       	3513001d33301f7eaaf58e60a1376488ff017354
Database type         	0
Shuffle input database	true
Createdb mode         	0
Offset of numeric ids 	0
Compressed            	0
Verbosity             	3
Converting sequences
[6162] 0s 651ms
Time for merging to GCF_000481805.1_Pseu_aeru_JJ692_V1_genomic_h: 0h 0m 0s 356ms
Time for merging to GCF_000481805.1_Pseu_aeru_JJ692_V1_genomic: 0h 0m 0s 489ms
Database type: Nucleotide
Time for merging to GCF_000481805.1_Pseu_aeru_JJ692_V1_genomic.lookup: 0h 0m 0s 14ms
Time for processing: 0h 0m 1s 861ms
GCF_000481805.1_Pseu_aeru_JJ692_V1_genomic.01_ORFs.txt

Could you please run cat /proc/cpuinfo or lscpu on the 64GB node?
If you were using the binary with the wrong instruction set (e.g. AVX2 on a CPU that does not support AVX2) it should give an error message way earlier.

[bioseq@compute-0-294 ~]$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                24
On-line CPU(s) list:   0-23
Thread(s) per core:    1
Core(s) per socket:    12
Socket(s):             2
NUMA node(s):          4
Vendor ID:             AuthenticAMD
CPU family:            16
Model:                 9
Model name:            AMD Opteron(tm) Processor 6172
Stepping:              1
CPU MHz:               800.000
CPU max MHz:           2100.0000
CPU min MHz:           800.0000
BogoMIPS:              4200.23
Virtualization:        AMD-V
L1d cache:             64K
L1i cache:             64K
L2 cache:              512K
L3 cache:              5118K
NUMA node0 CPU(s):     0-5
NUMA node1 CPU(s):     6-11
NUMA node2 CPU(s):     18-23
NUMA node3 CPU(s):     12-17
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc art rep_good nopl nonstop_tsc extd_apicid amd_dcm pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save pausefilter

Your CPU does not support the minimum requirements of MMseqs2. However once this PR (https://github.com/soedinglab/MMseqs2/pull/309) is merged SSE2 will also be supported.
If you have a Debian based machine you could install the mmseqs2 package from the debian-med apt. It already contains a precursor of this patch and should already work correctly on your CPU.

We finished the SIMDe integration yesterday. Please use the main MMseqs2 git. I am happy for any feedback since this is fresh from the oven, but please make a new issue.

Thanks.
Will check


Move GNU projects under appropriate publisher directory

This repository contains quite a few GNU projects, but they all live under different publisher directories. I think for the sake of consistency they should be moved under one publisher directory, such as manifests/GNU.
Here's a quick overview:

GNU Emacs, Gforth, GNU Octave and GNU Solfege are already in the right place.
GNU Radio is currently under manifests/GNURadio not manifests/GNU.
GIMP is currently under manifests/GIMP, manifests/GNU might be more suitable.
GnuPG should live under manifests/GNU not manifests/gnupg. Gpg4win seems to be a separate effort entirely, so perhaps manifests/Gpg4win would be best.
Curiously, Gnuplot is not a GNU project, so it's in the right place.

I've used the software list on the GNU website as my main source of information about what software is "a GNU package".
Of course, I tried my best to be thorough, but chances are I'm missing something.

I've taken the liberty of opening a PR (#1956) for this issue.
Note that I did not make separate PRs for every commit, because I felt that would be silly. The down side of this is that the bot will fail to validate the PR. Manual review is required.

Maybe you have to creat 14 pr's...

Also GnuWin32 should be merged? Now it should take 20 pr's. :-/

Also GnuWin32 should be merged?

I don't think it should. GnuWin32 is a port just like Cygwin or MinGW. Probably best to keep it separate.

Seems like GnuCash should be under manifests/GNU too. I've added it to the PR.

GNUCash and GNUradio are not actually part of the gnu project, which is why I did not include them in that namespace. Please research whether each one of them is involved with GNU/FSF before making PRs.

GIMP isn't part of the GNU Project either.

GNUCash and GNUradio are not actually part of the gnu project, which is why I did not include them in that namespace.
GIMP isn't part of the GNU Project either.
That's entirely debatable, but I do get your point. Both GnuCash and GIMP are listed under GNU packages. As far as I can tell, they both have as much as to do with the GNU Project and FSF as any other GNU project. That is, they have "GNU" in the name and are licensed under the GPL. Development is usually separate. Do you have evidence of the contrary?

Please research whether each one of them is involved with GNU/FSF before making PRs.
I did. Also, I don't see that as an issue. After all, PRs don't need to be merged as per the "request" part of "pull request".

We shouldn't "group up" packages just for convenience sake.
Shouldn't we? I'm thinking maybe we should, but that's not for me to decide. Alas, there does not seem to be guidelines on this. This is partly why I opened this issue.

Also, there's the issue of what does "publisher" even mean. Is GNU a publisher? Wikipedia calls it a mass collaboration project.

The language on the GIMP website is unclear. Although, GNU claims that GIMP is a "GNU Project". @MarNicGit, perhaps you know more about this?

Also GnuWin32 should be merged?

I don't think it should. GnuWin32 is a port just like Cygwin or MinGW. Probably best to keep it separate.

Thanks. (I searched a bit and got lost in information. Maybe I should quit the talk :-)

@mattiasmarka
https://www.gnu.org/philosophy/categories.html#GNUsoftware
From what I understand is that "GNU Software" is just software that follow the GNU ideologies/licenses and not necessary software that's published/developed by the GNU Project.
Current packages either use the publisher, the developer, the name of the app (in the case of a team effort like GIMP for example) or the name of a person (usually single-dev projects) as the publisher field.

From what I understand is that "GNU Software" is just software that follow the GNU ideologies/licenses and not necessary software that's published/developed by the GNU Project.

@MarNicGit, that's not strictly true. You also need to go through a legal process in which you give your software to the GNU Project. The GNU Project seems to act as a sort of umbrella organization, so I think it's fair to call them the publisher.  Also, all GNU Projects are part of the GNU system, whatever that means.
Maintainers can't choose to leave the GNU Project, as far is I understand. They can fork the project if they wish, but then it becomes a separate project. I think this is what happened with Nano at some point.

Current packages either use the publisher, the developer, the name of the app (in the case of a team effort like GIMP for example) or the name of a person (usually single-dev projects) as the publisher field.

Fair enough. But there's also directories like manifests/Microsoft and manifests/ubuntu. So the question remains: what constitutes a "publisher"? I'd be happy to follow whatever guidelines the repo maintainers think are best.

@MarNicGit, that's not strictly true. You also need to go through a legal process in which you give your software to the GNU Project. The GNU Project seems to act as a sort of umbrella organization, so I think it's fair to call them the publisher. Also, all GNU Projects are part of the GNU system, whatever that means.

That's an interesting link you post there - The things they describe there fit the role of a publisher quite well actually. Looks like we're going to need some input from MS maintainers on this before continuing. I still think that GIMP.GIMP should keep that package name, because in the end it's still the "GIMP project" doing all the work, even though it's GNU appointing the people who are in that team.

Fair enough. But there's also directories like manifests/Microsoft and manifests/canonical. So the question remains: what constitutes a "publisher"? I'd be happy to follow whatever guidelines the repo maintainers think are best.

To be fair the Microsoft and Canonical folders both contain software developed by MS and Canonical. If they contain packages where this isn't the case, please correct me and look into correcting those packages as well.
As for guidelines regarding naming, we don't really have any set in stone - Someone should probably raise an issue about that, same with tagging and other manifest stuff, haha. I've been planning on publishing my own workflow on my own fork sometime and asking people to take a look at it to see how things can be improved and to learn from it.

@MarNicGit, I think we're more or less on the same page then. I'm not sure who's in charge, so I don't know who to tag for input.

We asked ourselves some similar questions when the project started. I'm glad to see the community chiming in here. One of the concepts we're considering is how we can streamline the publish/approval process. Part of that would likely mean we're going to want to leverage the directory structure as a way to identify a publisher/owner for a package.  It seems like different  folders make sense when there is a GitHub team we can take advantage of.  I was working on a Gist a while back. I'll see if I can dig it up and link it to this Issue.

https://gist.github.com/denelon/0285ade55410f118b92d03e883a24c5e

@denelon
Could CODEOWNERS not be used for this?
Instead of closing a PR, if we use CODEOWNERS, then the bot could be updated to require approval from one CODEOWNERS and one MS representative.
This would allow the community to continue contributing, and suggesting to the CODEOWNERS on what packages/features they may be interested in supporting.

@denelon, so am I to understand in the future the publisher parent directory should be representative of who's in charge of the package? In that case perhaps "publisher" isn't the best name for this. The word "publisher" is more to do with where the package came from. Then again, I can't think of a better word.


Allow modification for bytes affected by relocations

Currently, if a memory byte is affected by a relocation, there is no way to edit its value. It would be better to also support editing the byte value of such bytes.
We need to figure out a way to do it in a proper way -- the user either needs to take care of the relocation (probably with some help from BN), or declare to blacklist the relocation at the place. This will make the implementation more complicated than it appears to be initially.

Related to https://github.com/Vector35/binaryninja-api/issues/920

It seems to me that we do support editing bytes with relocation applied. I do have a binary that has some bytes cannot be edited, and there are relocations on it, but this might be the actual cause of the issue.
I am closing this issue first, and I will reopen it if I have more information on it


Document our non-functional requirements

Approach to logging/monitoring/availability/scalability etc.
This is a good candidate for a guide on Stacks.

Closing as out of date.


fix:snowflake-key-pair-auth-private-key-does-not-get-removed-upon-rem…

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Enhanced file upload process in the FilePickerControl component.
Added base64 file representation for better file handling.
Exported the RenderFilePicker function for use in other parts of the application.

Bug Fixes

Improved handling of state resets when no file is selected or when a file is removed.

Tests

Introduced new test suite for FilePickerControl to validate rendering and functionality, including user interactions and file uploads.

Fixes https://github.com/appsmithorg/appsmith/issues/34763

/build-deploy-preview skip-tests=true

Hi, I'm curios what happened in this PR that we have many already existing files recreated?


Fail to open a file with an error for an attached storage account

OS: Win10/M1
Azure Resource Extension Build Version: 20220523.7
Azure Storage Extension Build Version: 20220523.2
Regression: Not a regression
Repro Steps:

Expand an attached storage account -> Create a file share -> Upload a file to it.
Click the file to open it.
Check whether succeeds to open the file.

Expect:
Succeed to open the file.
Actual:
Fail to open the file with an error.

More Info:

This issue doesn't reproduce for the blob container.
This issue doesn't reproduce for a normal storage account.

Seems like we can wait for after //Build for this.


feat: support react v18

Add support for react 18.

Upgrade react to v18.
Add react v18 as a peer dependency.

@juliencrn Can you please review this and merge it? I am currently getting the following error while running npm I:

+1

Added in<EMAIL_ADDRESS>(https://github.com/juliencrn/usehooks-ts/releases/tag/usehooks-ts%402.7.1)
Thanks again! :)

Thanks for the quick replay and fix @juliencrn, the new release works perfectly for me :+1:


Code block new line ignored

Code block are rendered with oneline

Instead of :

Multiline code-blocks seem to work fine for me, can you provide the source code of the above code block?

Let me know if it's not enough

@JanoschDeurer with the material theme it's working
I propose to close that issue

I'm having the same issue, the code blocks are fine on website but the pdf is rendered as same as the first post of this issue.
It's rendered fine if I use material theme but I want to keep using readthedocs theme. ( It is not a supported theme, but I'm getting the best result with this theme at the moment.)
Do you think is it possible to fix this issue by adding few lines to pdf-print.css ? If yes, any suggestions?

I am experiencing the same issue with readthedocs theme, as described by @canerbulduk

Hello @canerbulduk @scampion @JanoschDeurer I don't know if it's still useful for you but I found a workaround to display new lines in code blocks of PDF output when using readthedocs theme:
I specify a css extra file in my mkdocs.yml:
# Theme configuration
theme:
  name: 'readthedocs'
  highlightjs: true
  hljs_languages:
      - yaml
  locale: en
  titles_only: false
  collapse_navigation: true
extra_css:
    - css/extra.css

In my css file (docs/css/extra.css):
code.hljs {
  display: block;
  white-space: pre-wrap
}

And then, code blocks are well displayed in my PDF output :)


[Feature] [Helm] Work out versioning and release story for Helm charts

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
KubeRay master helm charts are hosted in a helm repo as of https://github.com/ray-project/kuberay/pull/545!
Now, we need to figure out versioning and release processes.
We need to do the following for the 0.4.0 KubeRay release (whenever that will be):

Version the charts following standard practices
Establish processes for releasing a versioned chart for each KubeRay release
Document instructions for pulling released charts

Use case
Basic best practices!
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

See #557 for more details.

See #557 for more details.

That strategy makes sense -- we can revisit this when it's time for the 0.4.0 release.

I think we have a plan for this -- I'll set the priority to P2 for now and we'll revisit when we do the 0.4.0 release.

TODO: Host stable charts in a separate repo.

The release is approaching. We need to document a procedure for hosting the charts and carry it out for the 0.4.0 release.

should we delete existing charts which are duplicated as existing tag release?

Yes.

What's the separate repo we will use?

We need to make one.

Based on this post, we can create a separate repository to host Helm charts and link the charts in GitHub pages to ArtifactHUB.
@DmitriGekhtman Do you have the write access to create a new repository? Thank you! cc @Jeffwan

Sounds like we need to open a new git repository whether we use Artifact Hub or not? In that case maybe we don't need to both with Artifact Hub for now?

Sounds like we need to open a new git repository whether we use Artifact Hub or not? In that case maybe we don't need to both with Artifact Hub for now?

The next step is to host Helm charts on GitHub pages. We can discuss whether we need Artifact Hub or not in the future.

Ok, sgtm -- let's open a new rayproject repo on Monday.

@DmitriGekhtman Are there any remaining action items for this issue? Thank you!

The remaining item is to release the charts with KubeRay 0.4.0.
I don't think keeping this issue around is helping anything, so will close.


gen_l10n/app_localizations.dart is not recognized

I am following https://docs.flutter.dev/development/accessibility-and-localization/internationalization#introduction-to-localizations-in-flutter
I got app_localizations.dart generated, but import of gen_l10n/app_localizations.dart is not recognized.
My pubspec:
dependencies:
  flutter:
    sdk: flutter
  flutter_localizations:
    sdk: flutter
  intl: ^0.18.0

flutter --version
Flutter 3.8.0-7.0.pre • channel flutter-3.8-candidate.7 • https://github.com/flutter/flutter.git
Framework • revision 1e6e6d41e3 (5 days ago) • 2023-02-07 20:18:32 -0800
Engine • revision f310ffd146
Tools • Dart 3.0.0 (build 3.0.0-204.0.dev) • DevTools 2.21.1

Hi @polina-c
Does it show any suggestions when clicking on Quick Fix?
Please provide a completed and minimal reproducible code sample so that we may verify this.

Added you as contributor to https://github.com/polina-c/flutter-chat
Issues are:

What I follow adding-your-own-localized-messages step 2 to add generate: true to pubspec.,yaml, pub get is unhappy:

For step 6, it says to remove l10n.yaml, that i created in step 3

polinach-macbookpro3:flutter-chat polinach$ flutter gen-l10n
Because l10n.yaml exists, the options defined there will be used instead.
To use the command line arguments, delete the l10n.yaml file in the Flutter project.

Attempted to generate localizations code without having the flutter: generate flag turned on.
Check pubspec.yaml and ensure that flutter: generate: true has been added and rebuild the project. Otherwise, the
localizations source code will not be importable.

If i delete the file, generation succeeds, but then I get issue with import described begore

Does it help?

And no meaningful suggestions with Quick Fix

@polina-c

What I follow adding-your-own-localized-messages step 2 to add generate: true to pubspec.yaml, pub get is unhappy:

You should add generate: true to the end flutter as the document mentioned (and usually comes later in the pubspec file.), not in flutter's dependencies; for eg:
dependencies:
  flutter:
    sdk: flutter
  flutter_localizations:
    sdk: flutter
  flutter_markdown: ^0.6.14
  intl: ^0.18.0
  url_launcher: ^6.1.9

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_lints: ^2.0.0

flutter:
  uses-material-design: true
  generate: true

If i delete the file, generation succeeds, but then I get issue with import described begore

The correct import should be:
import 'package:flutter_gen/gen_l10n/app_localizations.dart';

Please try the above changes and confirm if they work.

Honestly, I think this isn't an issue to fix since you can see instructions from step 2 and step 7 respectively.

Then in the pubspec.yaml file, enable the generate flag. This is added to the section of the pubspec that is specific to Flutter, and usually comes later in the pubspec file.

Add the import statement on app_localizations.dart and AppLocalizations.delegate in your call to the constructor for MaterialApp.

I will be closing this issue as solved. If you disagree, please write in the comments and I will reopen it. Thanks!

Sorry to be late here. I still think instructions in generated file should not be misleading.
If they are hard to maintain up-to-date, there should not be instructions at all.

I checked the documentation again, looks like the 2nd step has been updated since it's different than the content I posted at https://github.com/flutter/flutter/issues/120561#issuecomment-1430726314.
Currently, the 2nd step stated:
Open the pubspec.yaml file and enable the generate flag. This flag is found in the flutter section in the pubspec file.

# The following section is specific to Flutter.
flutter:
  generate: true # Add this line

I agree it should be more detailed. But I think it's best suited on Website repository than here. I would suggest you open an issue there for this request.


revert signature change of sqlite3_snapshot_cmp

This PR fixes #144. Commit 519a33b changed the function signature of sqlite3_snapshot_cmp which causes a compiler error when compiled with -DSQLITE_ENABLE_SNAPSHOT
Reverting this function signature back to int sqlite3_snapshot_cmp clears up the compiler error.
I've rebuilt this locally and done a make test and all the tests pass.
% grep SNAPSHOT Makefile
OPT_FEATURE_FLAGS =  -DSQLITE_ENABLE_MATH_FUNCTIONS -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_GEOPOLY -DSQLITE_ENABLE_RTREE -DSQLITE_ENABLE_SESSION -DSQLITE_ENABLE_PREUPDATE_HOOK -DSQLITE_ENABLE_SNAPSHOT
% make test
# .. skipped lots of output
Time: snapshot.test 19 ms
Time: snapshot2.test 11 ms
Time: snapshot3.test 5 ms
Time: snapshot4.test 5 ms
Time: snapshot_up.test 6 ms
# ... skipped more output
SQLite 2023-04-19 20:29:26 48505ad950bc0902d58210be066d4672e6085eb27c525ba2bc663fde7e93alt1
0 errors out of 263631 tests on cft.local Darwin 64-bit little-endian
All memory allocations freed - no leaks
Maximum memory usage: 9330592 bytes
Current memory usage: 0 bytes

ouch! You're right, that was a very unfortunate omission... I must have changed this signature along with all the other ones, not noticing that it isn't part of the virtualized API. Thanks for noticing!


Add IgammaGradA

Adds gradient of Igamma with respect to the first parameter (using XLA client).

It looks like there's a float32/float64 test failure.

@srvasude Mind finishing this off? I know at least one other user wanted it! Thanks!

Sorry, should be fixed now!


Automated cherry pick of #716: fix baremetal disk config auto extend not work and ipmi_info not record

Cherry pick of #716 on release/2.8.0.
#716: fix baremetal disk config auto extend not work and ipmi_info not record

/lgtm
/approve


AttributeError: 'Sequential' object has no attribute 'prediction'

from flask import Flask
from flask_restful import Api, Resource, reqparse
app = Flask(name)
api = Api(app)
import os
import json
import matplotlib.pyplot as plt
import matplotlib.image as mpimg
import logging
from collections import Counter
import pandas as pd
import numpy as np
from keras.models import load_model
from keras import backend as K
from keras.preprocessing.image import array_to_img, img_to_array, load_img
from scipy.misc import imresize
from PIL import Image
users = [
{
"name": "Nicholas",
"age": 42,
"occupation": "Network Engineer",
},
{
    "name": "Elvin",
    "age": 32,
    "occupation": "Doctor"

},
{
    "name": "Jass",
    "age": 22,
    "occupation": "Web Developer"

}

]
K.clear_session()
class User(Resource):
def get(self, name):
for user in users:
if(name == user["name"]):
return user, 200
return "User not found", 404
def post(self, name):
    parser = reqparse.RequestParser()
    parser.add_argument("image")
    #get the image
    model = load_model('C:/Users/ASUS/Downloads/mse-04-0.0877.h5')
    img_height, img_width, channels = 350, 350, 3

    img = load_img('C:/xampp/htdocs/faceDetection/image/logo.png')

    img = imresize(img, size=(img_height, img_width))
    test_x = img_to_array(img).reshape(img_height, img_width, channels)
    test_x = test_x / 255.
    test_x = test_x.reshape((1,) + test_x.shape)
    predicted = model.prediction(test_x)
    self.graph = tf.get_default_graph()

    return{
    "name": "Nicholas",
    "age": 42,
    "occupation": "Network Engineer",
    "prediction": str(predicted[0][0])

}, 201

def put(self, name):
    parser = reqparse.RequestParser()
    parser.add_argument("age")
    parser.add_argument("occupation")
    args = parser.parse_args()

    for user in users:
        if(name == user["name"]):
            user["age"] = args["age"]
            user["occupation"] = args["occupation"]
            return user, 200

    user = {
        "name": name,
        "age": args["age"],
        "occupation": args["occupation"]

    }
    users.append(user)
    return user, 201

def delete(self, name):
    global users
    users = [user for user in users if user["name"] != name]
    return "{} is deleted.".format(name), 200

api.add_resource(User, "/user/string:name")
app.run(debug=True)
Here is the error...
Using TensorFlow backend.

Debugger is active!
Debugger PIN: 301-406-345
Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
WARNING:tensorflow:From C:\ProgramData\Anaconda3\lib\site-packages\tensorflow\python\framework\op_def_library.py:263: colocate_with (from tensorflow.python.framework.ops) is deprecated and will be removed in a future version.
Instructions for updating:
Colocations handled automatically by placer.
2019-05-14 21:20:36.954666: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
WARNING:tensorflow:From C:\ProgramData\Anaconda3\lib\site-packages\tensorflow\python\ops\math_ops.py:3066: to_int32 (from tensorflow.python.ops.math_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.cast instead.
app.py:66: DeprecationWarning: imresize is deprecated!
imresize is deprecated in SciPy 1.0.0, and will be removed in 1.3.0.
Use Pillow instead: numpy.array(Image.fromarray(arr).resize()).
img = imresize(img, size=(img_height, img_width))
<IP_ADDRESS> - - [14/May/2019 21:21:13] "POST /user/Nicholas HTTP/1.1" 500 -
Traceback (most recent call last):
File "C:\ProgramData\Anaconda3\lib\site-packages\flask\app.py", line 2309, in call
return self.wsgi_app(environ, start_response)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask\app.py", line 2295, in wsgi_app
response = self.handle_exception(e)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask_restful_init_.py", line 269, in error_router
return original_handler(e)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask\app.py", line 1741, in handle_exception
reraise(exc_type, exc_value, tb)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask_compat.py", line 34, in reraise
raise value.with_traceback(tb)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask\app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "C:\ProgramData\Anaconda3\lib\site-packages\flask\app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask_restful_init_.py", line 269, in error_router
return original_handler(e)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask\app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask_compat.py", line 34, in reraise
raise value.with_traceback(tb)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask\app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "C:\ProgramData\Anaconda3\lib\site-packages\flask\app.py", line 1799, in dispatch_request
return self.view_functionsrule.endpoint
File "C:\ProgramData\Anaconda3\lib\site-packages\flask_restful_init_.py", line 458, in wrapper
resp = resource(*args, **kwargs)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask\views.py", line 88, in view
return self.dispatch_request(*args, **kwargs)
File "C:\ProgramData\Anaconda3\lib\site-packages\flask_restful_init_.py", line 573, in dispatch_request
resp = meth(*args, **kwargs)
File "C:\xampp\htdocs\faceDetection\app.py", line 70, in post
predicted = model.prediction(test_x)
AttributeError: 'Sequential' object has no attribute 'prediction'

@yensan0512  It looks like you haven't used a template to create this issue. Please resubmit your issue using a template from here. We ask users to use the template because it reduces overall time to resolve a new issue by avoiding extra communication to get to the root of the issue. We will close this issue in lieu of the new one you will create from the template. Thank you for your cooperation.

@yensan0512 Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Commenting frontpage components

Is your feature request related to a problem? Please describe.
As someone picking up this project, I may be confused by the project structure
Describe the solution you'd like
Add comments explaining the service/container/page structure
Describe alternatives you've considered
Also should to add documentation in the wiki

I approve

I approve
Cheers,
Timo
On Fri, Mar 20, 2020 at 3:54 PM Tyger Kong <notifications<EMAIL_ADDRESS>wrote:
Assigned #103https://github.com/se701-group6/se701-assignment1/issues/103 to @timovvhttps://github.com/timovv.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/se701-group6/se701-assignment1/issues/103#event-3147898800, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AANUN6TB5C7XBW6Z4QUD2PTRILLGLANCNFSM4LP5UPDQ.

I approve, we need to add this.

Be careful not to get too carried away and add unnecessary comments for the sake of having comments - those add noise to the code and could potentially make the code harder to read.

This issue has been resolved with the last 2 PRs


Add throws check

Similar to how ctx.reverts works a functionality to check for a throw would be convenient.
Open zeppelin example

ctx.throws is already included.


Last Week in Pony - July 21, 2024

We've moved the Pony development sync back 30 minutes to 2:30 eastern every Tuesday.

Office Hours:
Attendees: Joe, Adrian, Sean, Red
Lots of conversation about Petri Nets and BOC and Verona and Pony.

Version 0.2.2 of ponylang/pony-language-server has been released.
See the release notes for more details.

July 23 Sync recording: https://vimeo.com/991181964


Actualization

Hello, @lymychp! This is your first Pull Request that will be reviewed by Ebert, an automatic Code Review service. It will leave comments on this diff with potential issues and style violations found in the code as you push new commits. You can also see all the issues found on this Pull Request on its review page. Please check our documentation for more information.

Coverage remained the same at 86.652% when pulling 3e77b018b270992e1382b8d38a0bc0830d8c7d90 on lymychp-patch-1 into 968f429141061013bed9d5ed47ac67124b8f5f34 on master.


Update Remove-NavContainerSession.ps1

Currently, sessions will not be evicted correctly as sessions collection using 'containerName' as a reference in Get-NavContainerSession.ps1. This small fix will use 'containerName' as a reference to remove sessions from sessions collection.

You are right - and this bug has existed since July 21st 2020...:-(
Thanks


SWARM-1074: improve MavenPluginTest debuggability

Motivation
The MavenPluginTest is hard to debug in case of failures.
Modifications
The test:

introduces a way to manually run a single testing combination,
without modifying the test code, using a system property
provides instructions how to use the facility for running
a single combination, as a part of failing assertion message
doesn't delete the working directory of the testing project
when running in the single combination mode, because
that directory is likely to be inspected manually

Result
Improved debuggability of the MavenPluginTest.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you created a JIRA and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[ ] Have you built the project locally prior to submission with mvn clean install?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

add to whitelist


Warshall Algorithm in C

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
This is a program of war shall algorithm in C which is a shortest path algorithm.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes #6378

@ankitaggarwal23 @HarshCasper Kindly review this.Thanks.


Garurumon (X Antibody) Lvl 5?

The card Garurumon (X Antibody) is in the database as Lvl. 5 cards arranged. It would have to be a level. be 4 card.

I do get all card info from the wiki, it seems it isn't correctly entered. I will change it there.
It should reflect on my site in a day or so :)


ASP.NET Core application giving object reference not set to an instance of an object exception in production but works fine in development

Ours website is school management application built on Asp.Net Core 2.0. I've requirement to enable users to have multiple roles across different schools with same credentials.For that I used cookies to share identity(ASP.NET Core identity).But it works perfect in development environment but when I host it to azure I'm getting object reference not set to an instance of an object exception in production.
this is the error in log file.
 failfail: Microsoft.AspNetCore.Server.Kestrel[13]
 Connection id "0HLFNDU99T5DB", Request id "0HLFNDU99T5DB:00000001": An unhandled exception was thrown by the application.
 System.NullReferenceException: Object reference not set to an instance of an object.
    at Guru.Web.Controllers.AccountController.<Login>d__16.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.TaskOfIActionResultExecutor.<Execute>d__0.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeActionMethodAsync>d__12.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextActionFilterAsync>d__10.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
    at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
    at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeInnerFilterAsync>d__13.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.<InvokeNextResourceFilter>d__23.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)
    at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
    at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.<InvokeFilterPipelineAsync>d__18.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.<InvokeAsync>d__16.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.<Invoke>d__5.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Session.SessionMiddleware.<Invoke>d__9.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at Microsoft.AspNetCore.Session.SessionMiddleware.<Invoke>d__9.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at IdentityServer4.Hosting.IdentityServerMiddleware.<Invoke>d__3.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.<Invoke>d__6.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.<Invoke>d__8.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at IdentityServer4.Hosting.BaseUrlMiddleware.<Invoke>d__3.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.<Invoke>d__7.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.<Invoke>d__6.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.AspNetCore.Server.IISIntegration.IISMiddleware.<Invoke>d__13.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.<ProcessRequests>d__186`1.MoveNext()
 info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]

When I remove these lines of code from startup.cs it works absolutely fine.
  services.AddSession(options =>
        {
            options.IdleTimeout = TimeSpan.FromHours(1);
            options.Cookie.Domain = ".zipschool.com";
            options.Cookie.Name = "ZipSchoolSession";
        });

services.ConfigureApplicationCookie(options =>
        {
            options.Cookie.Name = ".AspNet.ZipschoolSharedCookie";
            options.Cookie.Domain = ".zipschool.com";

       });

.AddCookie(options =>
         {
             options.Cookie.Name = "zipcookie";
             options.Cookie.Domain = "zipschools.com";
             //options.Cookie.SameSite = SameSiteMode.Strict;
         });

This is the login method
 [HttpPost]
    [AllowAnonymous]
    [ValidateAntiForgeryToken]
    public async Task<IActionResult> Login(LoginInputModel model)
    {
        if (SessionState.TenantName.Equals(K_HOME) && model.IsHomeTenant)
        {
            //string[] homePasswordSkip = { "Password" };
            //foreach (var modelKey in ModelState.Keys)
            //{
            //    if (homePasswordSkip.Contains(modelKey))
            //    {
            //        ModelState[modelKey].Errors.Clear();
            //        ModelState[modelKey].ValidationState = ModelValidationState.Valid;
            //    }
            //}

            var url = HttpContext.Request.Host.Value;
            var identityUserId = _userManager.FindByEmailAsync(model.Email);

            var tenant = _tenantService.GetUserTenant(identityUserId.Result.Id);

            SessionState.TenantId = tenant.Id;
            SessionState.TenantName = tenant.Name;
            SessionState.EnvironmentType = tenant.EnvironmentType;
            SessionState.SchoolId = tenant.SchoolId;

            //session["LoginInput"] =

            var newPath = url.Replace(K_HOME, tenant.Name);// + "/Home/Index";

            CCACrypto ccaCrypto = new CCACrypto();
            var rediredcturl = HttpContext.Request.Scheme + "://" + newPath + "/Nav/" + ccaCrypto.Encrypt(model.Email, "Guru");

            //return RedirectPermanent(rediredcturl);
            //TempData["LoginInput"] = model;

            return Redirect(rediredcturl);

        }
        if (ModelState.IsValid)
        {
            var identityUserId = _userManager.FindByEmailAsync(model.Email);

            var activity = false;
            if (identityUserId.Result != null)
            {
                activity = _tenantService.GetUserActivity(identityUserId.Result.Id, SessionState.TenantId);
            }
            if (!activity)
            {
                ViewBag.message = "You Are UnAuthorized";
                ModelState.AddModelError(string.Empty, "Invalid login attempt.");
                return View(await GetLoginViewModel(model));
            }
            // This doesn't count login failures towards account lockout
            // To enable password failures to trigger account lockout, set lockoutOnFailure: true
            var result = await _signInManager.PasswordSignInAsync(model.Email, model.Password, model.RememberLogin, lockoutOnFailure: false);
            //var useractivity =  _guruDbContext.User.FirstOrDefault(x => x.Email == model.Email );

            if (result.Succeeded)
            {
                _logger.LogInformation(1, "User logged in.");

                return RedirectToLocal(model.Email, model.ReturnUrl);
            }
            if (result.RequiresTwoFactor)
            {
                return RedirectToAction(nameof(SendCode), new { ReturnUrl = model.ReturnUrl, RememberMe = model.RememberLogin });
            }
            if (result.IsLockedOut)
            {
                _logger.LogWarning(2, "User account locked out.");
                return View("Lockout");
            }
            else
            {
                ApplicationUser au = await _userManager.FindByEmailAsync(model.Email);
                if (au.IsNull())
                {
                    ViewBag.CredentialError = "Account does not exist. Try using a valid email id OR create new account.";
                }
                else
                {
                    ViewBag.CredentialError = "Wrong user name or password.";
                }
                ModelState.AddModelError(string.Empty, "Invalid login attempt.");
                //LoginViewModel loginViewModel = ;

                return View(await GetLoginViewModel(model));
            }
        }

        LoginViewModel loginViewModel = await GetLoginViewModel(model);
        // If we got this far, something failed, redisplay form
        return View(await GetLoginViewModel(model));
    }

Where is the exception being thrown? During request processing? On login? In that stack trace I don't see anything from asp.net identity at all, only identity server, so this might be a question for them.

We're closing this issue as no response or updates have been provided in a timely manner. If you have more details and are encountering this issue please add a new reply and re-open the issue.


The comparison part is questionable

hello author, your paper is very beautiful and enlightening, but I still have several problems that are not clearly explained in the paper. In the comparative experiment, do you reproduce the RD4AD model according to the original paper or according to your multi-category anomaly detection? It is understood that RD4AD belongs to a single class

Thank you for your interest in our work. RD4AD is designed for single-class anomaly detection tasks. We obtained our results by using the official RD4AD code to conduct experiments on multi-class anomaly detection tasks.


Issue when item is draggable and droppable

Is this feature not supported right now?
Because I marked a div as both draggable and droppable then I get the error below:
SyntaxError: Unexpected token u in JSON at position 0
at JSON.parse ()
at Droppable.drop (droppable.js:51)
at Wrapper_Droppable.handleEvent (/Ng2DragDropModule/Droppable/wrapper.ngfactory.js:74)
at View_NavverItemComponent3.handleEvent_0 (/DashboardModule/NavverItemComponent/component.ngfactory.js:708)
Thank you!

Haven't actually tried doing something like this. But I'll have a look.

@toanqc with v1.0.0 release you can't add draggable & droppable directives to the same element but it will not work since droppable explicitly disables drag on an element.
Can you explain the use case of making an element draggable and droppable at the same time?

I was wondering if the new example is what you had in mind: http://plnkr.co/edit/ki2TgX?p=preview

I have a nested folder/file structure. I want to drag and drop a folder to another folder and file also is able to drag and drop into the folder. So in this case, the folder is both draggable and droppable.

@toanqc, in the v1.2.0 release I have removed the draggable=false attribute on droppable. Now you can easily implement the required functionality.


The note in the "remarks" section of the "IsNot Operator" page is outdated

> The IsNot operator cannot be used to compare expressions returned from the TypeOf operator. Instead, you must use the Not and Is operators.
This is wrong. If you use VB 14.0 or higher, you can write TypeOf ... IsNot ....

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

ID: e4aecef0-c2d3-cc96-9068-fe2950a9c293
Version Independent ID: fb5b21e0-be1d-a9bd-474d-4b8dcd8ec328
Content: IsNot Operator (Visual Basic)
Content Source: docs/visual-basic/language-reference/operators/isnot-operator.md
Product: dotnet-visualbasic
GitHub Login: @KathleenDollard
Microsoft Alias: kdollard

I've already opened #14419 a while ago.

Thanks @Youssef1313 and @Nukepayload2. We'll follow up on the active PRs soon.

This has been fixed by #14419.


(wesnoth) Beta version support

There are beta versions of the Battle for Wesnoth game, but they're not supported by the package.
https://chocolatey.org/packages/wesnoth

I'll mark this as an up for grabs, however I doubt it will be added.
We'll need a way to tell the difference between stable and beta releases, in which case I could see no way to parse such information easily.
Feel free to point it out if you are able to see it though.

Only beta releases are hosted here: https://sourceforge.net/projects/wesnoth/files/wesnoth/
Stable releases: https://sourceforge.net/projects/wesnoth/files/

I see, I didn't notice the extra wesnoth in the path, in which case it will be added sooner or later, but I'm keeping it as an Up for grabs for now

beta versions have now been included with the version check (Latest beta should be available on chocolatey.org shortly)


Date and time in the Drawer need to collapse at smaller screen sizes

When using the provided drawer-pf-notification-info class with date & timestamps, the drawer struggles to display content meaningfully at smaller screen sizes.
Initial comment on this PR in origin-web-console.
Web console example:

Docs example, with a slightly edited message:

Initial thoughts are to make them stack at a certain point.  These issues are a little fuzzy as the content inside the drawer is "user land", but still depends on Patternfly internals.

@jeff-phillips-18

So the issue is not with the date/time per se as that is custom content. The problem is that the drawer-pf-notification-info will take up as much room as it needs and whatever is left goes for the message.
We should determine at what size these should stack. This is a core Patternfly issue.
Opened: https://github.com/patternfly/patternfly/issues/721

Correct.  It seems like the kind of problem that could be solved with a container-fluid and nesting row and columns, if we wanted to stick with bootstrap layout language.  If not, then more clearly defining primary, secondary, tertiary content columns & formalizing the patterns that they follow as space expands/collapses.

This was taken care of in https://github.com/patternfly/patternfly/pull/717
The content now stacks at a wider breakpoint to avoid narrow columns of content.


Matter regions ignored by tiling with check_tissue=True

Describe the bug
The tiling with check_tissue=True option is failing in a dramatic fashion on some easy examples of a standard dataset Camelyon16. The appearance of the errors seem to indicate a mistake on the total surface checked for tissues on the slide. However it does not always happen only some images have this behavior.
To Reproduce
Steps to reproduce the behavior:

Download the Camelyon16 slides Normal_015.tif and Normal_014.tif from https://drive.google.com/drive/folders/0BzsdkU4jWx9BNUFqRE81QS04eDg?resourcekey=0-p6LFOzRfCTfyi_JpshhoTQ
Install openslide, histolab and large image
Execute the following code:

    from histolab.slide import Slide
    from histolab.tiler import GridTiler
    grid_tiles_extractor = GridTiler(
        tile_size=(224, 224),
        level=1,
        pixel_overlap=0,
        prefix="grid/",
        check_tissue=True,
        suffix=".png",
    )
    slide = Slide("Normal_014.tif, "./tmp", use_largeimage=True)
    histolab_tiling = grid_tiles_extractor.locate_tiles(
        slide=slide,
        scale_factor=64,
        alpha=0,
        outline="#046C4C",
    )
    histolab_tiling.save("bug.png")

Expected behavior
All matter regions should be tiled.
Screenshots

Software (please complete the following information):

OS: Tested on Ubuntu 20.04
Python Version: 3.8.13
histolab version: 0.4.0

Dear @jeandut thank you for opening this issue.
The result you're showing is compatible with the default tiling behavior, i.e., extracting tiles from the biggest tissue portion in the slide. This behavior is controlled by the parameter extraction_mask in the locate_tiles or extract method of the tiler, which has histolab.masks.BiggestTissueBoxMask() as default value.
Therefore, if you want to extract tiles from all the tissue found in the slide you need to instantiate the histolab.masks.TissueMask extraction mask and pass it to extraction_mask.
from histolab.masks import TissueMask

# your code here

histolab_tiling = grid_tiles_extractor.locate_tiles(
        slide=slide,
        extraction_mask=TissueMask(),
        scale_factor=64,
        alpha=0,
        outline="#046C4C",
    )

P.S.: The decision to have BiggestTissueBoxMask as the default value is due to retro-compatibility with older projects using alpha versions of histolab, but we can definitely discuss if it still makes sense now that the project is a bit more mature. cc @ernestoarbitrio @nicolebussola

Hi @jeandut, actually we wrote this tutorial to clarify this behavior https://histolab.readthedocs.io/en/latest/tissue_masks.html
But maybe it's not clear enough!! Thank you for reaching out :)


Deleted new TDP files

Deleted new TDP files.

Docs Build status updates of commit 997aa52:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/tdp-configuration.md
:white_check_mark:Succeeded

msteams-platform/concepts/tdp-distribute.md
:white_check_mark:Succeeded

msteams-platform/concepts/tdp-tools.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[WIP] Added a lot of materials to resources

Feel free to add another materials

Not covered topics

Multinode testing
Persistence and event adapters
Persistence query
ClusterTools
Cluster Sharding

Besides possibly more materials that can be added. Can this be merged ?


JSON parse fails after updating to 2.0.0-alpha.64

🐛 Bug Report
I got this error after I updated the docusaurus version from 2.0.0-alpha.48 to 2.0.0-alpha.64.
Have you read the Contributing Guidelines on issues?
yes.
To Reproduce

Download this example repository:
test-docs.zip
run npm i
run npm run start
see JSON parse error as seen in the screenshots
comment out line 6 in docs/home/home.md
see error disappear

Expected behavior

The project should start and build as it was before updating to the new docusaurus version (2.0.0-alpha.64)
Actual Behavior

When running npm run start or npm run build I get errors related to the JSON parserin webpack (see screenshots)

Your Environment

Docusaurus version used: 2.0.0-alpha.64
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Chrome Version 85.0.4183.121 (Official Build) (64-bit)
Operating system and version (desktop or mobile): macOS Mojave 10.14.6

Hi,
You upgraded Docusaurus and likely many other deps were upgraded too in this process, so it's hard to know the problem and  if it's our fault without a repro. If you can try to create the minimal repro case that would be great.
I don't even know what is the content of this json file, and how/where it is consumed, so it's hard to solve.

Hi,
Thanks for the quick feedback. I updated the bug report descriptions and added an example repository. Hope this helps!

Thanks @nicolas-actyx
It seems we try to load your json file as a static asset like we do for images. Probably make sense. to do so but I suspect there is a conflict between assets loader (file. loader) and code loader (babel loader).
I suggest you use the pathname:// prefix as an escape hatch for such case
[This is what causes the JSON parse error](pathname:///schemas/os/node-settings.schema.json)

Thanks a lot for the quick help, just tried it and it works!


Refactor  data-pipeline FFI API.

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?

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

Project coverage is 73.36%. Comparing base (c48d94b) to head (d084b29).
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #620      +/-   ##
==========================================
+ Coverage   72.63%   73.36%   +0.72%
==========================================
  Files         246      252       +6
  Lines       34964    36124    +1160
==========================================
+ Hits        25396    26501    +1105
- Misses       9568     9623      +55

Components
Coverage Δ

crashtracker
20.53% <ø> (+0.14%)
:arrow_up:

datadog-alloc
98.73% <ø> (ø)

data-pipeline
92.33% <96.75%> (+2.21%)
:arrow_up:

data-pipeline-ffi
88.67% <96.75%> (+88.67%)
:arrow_up:

ddcommon
83.21% <ø> (+0.39%)
:arrow_up:

ddcommon-ffi
69.90% <ø> (+1.79%)
:arrow_up:

ddtelemetry
59.10% <ø> (+0.07%)
:arrow_up:

ipc
83.63% <ø> (+0.02%)
:arrow_up:

profiling
84.26% <ø> (ø)

profiling-ffi
77.42% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
40.12% <ø> (-0.01%)
:arrow_down:

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
50.36% <ø> (ø)

tinybytes
91.66% <ø> (ø)

trace-mini-agent
70.88% <ø> (ø)

trace-normalization
98.25% <ø> (ø)

trace-obfuscation
95.73% <ø> (ø)

trace-protobuf
77.67% <ø> (ø)

trace-utils
92.86% <ø> (-0.15%)
:arrow_down:


GTA IV rendering issue - black screen and visual stutter - gf 960 at win10

I tried out dxvk on fresh install of GTA IV complete edition on windows 10, and instantly after the game load the game render stopped working correctly, showing black screen with some additional artifacts, as seen here:
https://imgur.com/a/vrHH9xB
Software information
GTA IV complete, windows 10(fully updated, if it does matter), game set to 1080p, on medium settings
System information

GPU: gtx 960
Driver: 461.9.0
DXVK version: v1.7.3

Apitrace file
https://drive.google.com/file/d/1Ey1m0J8VeF2c2V0ILkxph439onqS9pSS/view?usp=sharing
Log files

d3d9.log: https://pastebin.com/pHe3bV1B

Game is more or less fine for me (even on Windows) and the trace replays without issues too.

Game is more or less fine for me (even on Windows) and the trace replays without issues too.

as per request from discord im posting second trace:
https://drive.google.com/file/d/1Gqk9_3Gn83KExeeeSIZxq2HDKzLw0vSu/view?usp=sharing

as per request from discord im posting second trace:
https://drive.google.com/file/d/1Gqk9_3Gn83KExeeeSIZxq2HDKzLw0vSu/view?usp=sharing

Windows (Crap) 10 invasion in our beatiful project :(

Windows (Crap) 10 invasion in our beatiful project :(

Try deleting dxvk.cache file and mesa_shader cache files in your .cache directory. And try again. Try 460 driver even (I assume 461 is latest).

@kluczm are you able to try again with latest dxvk and graphics driver?


[#139196683] Use latest final build of datadog-agent release

What
Use latest final build of datadog-agent release
To deploy fix for handling hostname definitions from
https://github.com/alphagov/paas-datadog-agent-boshrelease/pull/10
How to review
Deploy. Observe no no_data errors on TCP and HTTP datadog checks for your environment for say at least 4 hours.
Who can review
not @mtekel

This is duplicate of #58 , closing in favour of that one.


v2 Enhancement for platform style overrides in Config for ionic components

Short description of the problem:
This is a feature request not a bug.
Currently in the config block we have the option to override the platform styling for some elements, for example iconMode: ios, pageTransition: ios etc.
It would be really useful to be able to over ride the default platform styling for other ionic components in the same way.  For example ion-range: md, ion-segment: ios.  This would be an application wide over ride for the specific component. and it would be consistent with the way platform style over rides are currently handled for other elements like icons and transitions.

Hello all! While this is an awesome feature request it is not something that we plan on doing anytime soon. Because of this I am going to move this to our internal feature tracking repo for now as it is just "collecting dust" here. Once we decide to implement this I will move it back. Thanks everyone for using Ionic!

This issue was moved to driftyco/ionic-feature-requests#47


Contributing Guidelines

Adds contributing guidelines, a HowTo and a default code of conduct.
Curious to hear your thoughts.

@dodijk I've added contributers


Fix loading of 2nd level collections

Construction of the back reference assumed that the table holding the parent of the foreign key is the actual parent property.
This is now corrected by using the correct API to identify the ancestor which holds the id.
Closes: #1692

Merged and back ported to 3.2.x


Make severity optional in Problems API

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


Properly document CDN support

Follow-up to #309

@justin808 can you tell me if I'm missing anything here?
I've spent quite a bit of time looking through the webpacker archives & I'm still not sure why they mention using config.asset_host