4.2 Beta 2: OpenXR project silently fails to run. Same project runs fine in Beta 1 and 4.1.1 Stable.

Godot version
v4.2.beta2.official [f8818f85e], v4.2.beta1.official [b1371806a], v4.1.1.stable.official [bd6af8e0e]
System information
Windows 10, Vulkan Forward+, Nvidia RTX3060Ti Game-ready driver 537.58, SteamVR 2.0.6, Windows Mixed Reality for SteamVR 1.3.73, HP Reverb G2 headset.
Issue description
When running a simple OpenXR project in Godot 4.2 Beta 2, a project that runs fine 4.1.1 Stable and 4.2 Beta 1, the project silently fails to launch and no OpenXR / Vulkan version info is printed to the console.
In the included videos I demonstrate the issue by running the project directly from the manager, but the behaviour is the same when run from the editor.
Perhaps the issue is related to the recent update to OpenXR-SDK 1.0.30 when using Windows Mixed Reality (it seems the update was mainly tested on Meta / Android)? Version 1.0.31 has just been released and mentions some compatibility improvements.
In Beta 1:
https://github.com/godotengine/godot/assets/91982860/daffb015-20f1-4b79-83c5-b2d1e1261b70
In Beta 2:
https://github.com/godotengine/godot/assets/91982860/44f208aa-3fbf-4000-8d46-c1bfafe7aef3
Steps to reproduce

Run the attached MRP in Godot 4.1.1 Stable or 4.2 Beta 1.

Observe that the project launches and runs correctly.

Run the MRP in Beta 2.

Observe that the project fails to launch.

Observe that no OpenXR / Vulkan info is printed to the console.

Minimal reproduction project
Beta 2 OpenXR Test.zip

I don't have an XR device. But simply opening this project with 4.2 beta2 does work. It takes a bit longer than I would expect, but it happens. And there is some issue logged:
ERROR: Parameter "profile_def" is null.
   at: _update_interaction_profile (modules/openxr/editor/openxr_interaction_profile_editor.cpp:261)

Though this may be just about me not having an XR device.

Perhaps the issue is related to the recent update to OpenXR-SDK 1.0.30 when using Windows Mixed Reality (it seems the update was mainly tested on Meta / Android)?

To test this hypothesis, I've made a build of 4.2-beta2 with #82582 reverted. Could you test it and let me know if that solves the issue?
https://downloads.tuxfamily.org/godotengine/testing/Godot_v4.2-beta2_windows_openxr_1.0.28.zip

@akien-mga It indeed solves the issue, so that would seem to support the hypothesis.
In custom build:
https://github.com/godotengine/godot/assets/91982860/2de69ef5-53e1-456c-96a6-642c5e9f3618

I can confirm using the Godot_v4.2-beta2_windows_openxr_1.0.28 fixes my memory corruption issue on:

Alienware M15 R7
Microsoft Windows 11 Home (10.0.22621 N/A Build 22621)
NVidia GeForce RTX 3070 TI
12th Gen Intel(R) Core(TM) i7-12700H
Oculus App Version <IP_ADDRESS>.153
Meta Quest Pro

I wonder what the source of this is as I've been using my own builds with OpenXR 10.0.30 without problems for some time now. What do we do different in our build process that would introduce this instability?
@akien-mga we should and see if the issue is fixed with OpenXR 10.0.31, we're starting to roll out extensions that require the newer OpenXR version. We can probably get away with 28 for the 4.2 release if we can't figure this out in time, but 4.3 likely will need to run a newer version of OpenXR.

Edit: Try launching Godot from the command line with the --verbose flag, which may give you some extra clues.

As @YuriSizov already mentioned, always use --verbose when diagnosing XR issues, we only output data around the startup of OpenXR if this flag is set (I should probably make that a little less strict and output some more basic info even if the flag is not set).

Edit: Try launching Godot from the command line with the --verbose flag, which may give you some extra clues.

I will keep that in mind.
This is the console output for the OpenXR 1.0.30 beta 2 version:
Details

  D:\Projects\Godot>godot_v4.2-beta2_win64_console.exe -d --verbose
  Godot Engine v4.2.beta2.official.f8818f85e - https://godotengine.org
  TextServer: Added interface "Dummy"
  TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
  Native OpenGL API detected: 3.3: NVIDIA - NVIDIA GeForce RTX 3060 Ti
  NVAPI: Init OK!
  NVAPI: Disabled OpenGL threaded optimization successfully
  Using "wintab" pen tablet driver...
  Shader 'CanvasSdfShaderGLES3' SHA256: 48d6450939fd0c3882887ad90eac03fbafb9eb69d2b47aeacb0c810dc60dd60f
  Shader 'SkeletonShaderGLES3' SHA256: 9d255e374ce0c426eb7722316805d5f32c26d6d6595350cdc749b0d85b075324
  Shader 'ParticlesShaderGLES3' SHA256: f66b9725d7d5da6d8f73bbd5da9bd9729ec7695ff4461b1743e9809ae6131a27
  Shader 'ParticlesCopyShaderGLES3' SHA256: 0051fa04202b9f23982e2ab102a167e0bbe5ad2b4e4223aa7f61a64ba82566f3
  Shader 'CopyShaderGLES3' SHA256: 37e2322858e23cdbf507d3f1d183279902d89c59698e393893b0d8a6e15deca1
  Shader 'CanvasShaderGLES3' SHA256: 62150a8b66c267e6b8b08a034f1a127ef33cbaf80242c2f915f5606fee19cad2
  Shader 'CanvasOcclusionShaderGLES3' SHA256: cfde6a4ce32c005c5bcb401cf8552b379fc2b5d23303f299586decca5ca3f3fd
  Shader 'SceneShaderGLES3' SHA256: 462e088a0eb0dc1eabf54a9fde34660df9e7313aac1f3da9bebdef47b4c82371
  Shader 'SkyShaderGLES3' SHA256: 9ee4cd2240cc70fe8860b005f4a236c35d994c6c8a68f96d333d384b3c4b5a1b
  Shader 'CubemapFilterShaderGLES3' SHA256: 6c1156fecfd6badbd0d56475f67e7d0d7250dfdcd4fb1f0e037c3fd86a909b74
  OpenGL API 3.3.0 NVIDIA 537.58 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3060 Ti
  WASAPI: Activated output_device using IAudioClient3 interface
  WASAPI: wFormatTag = 65534
  WASAPI: nChannels = 2
  WASAPI: nSamplesPerSec = 48000
  WASAPI: nAvgBytesPerSec = 384000
  WASAPI: nBlockAlign = 8
  WASAPI: wBitsPerSample = 32
  WASAPI: cbSize = 22
  WASAPI: mix_rate = 48000
  WASAPI: fundamental_period_frames = 480
  WASAPI: min_period_frames = 480
  WASAPI: max_period_frames = 480
  WASAPI: selected a period frame size of 480
  WASAPI: detected 2 channels
  WASAPI: audio buffer frames: 480 calculated latency: 10ms
TextServer: Primary interface set to: "ICU / HarfBuzz / Graphite (Built-in)".
CORE API HASH:<PHONE_NUMBER>
EDITOR API HASH:<PHONE_NUMBER>
EditorSettings: Load OK!
Scanning projects at: D:/Projects/Godot/Godot Projects
MbedTLS: Some X509 certificates could not be parsed (1 certificates skipped).
Loaded system CA certificates
EditorSettings: Save OK!
Running project: D:/Projects/Godot/Godot Projects/Beta 2 OpenXR Test
Godot Engine v4.2.beta2.official.f8818f85e - https://godotengine.org
TextServer: Added interface "Dummy"
OpenXR: Found OpenXR extension XR_KHR_vulkan_enable
OpenXR: Found OpenXR extension XR_KHR_vulkan_enable2
OpenXR: Found OpenXR extension XR_KHR_D3D11_enable
OpenXR: Found OpenXR extension XR_KHR_D3D12_enable
OpenXR: Found OpenXR extension XR_KHR_opengl_enable
OpenXR: Found OpenXR extension XR_KHR_win32_convert_performance_counter_time
OpenXR: Found OpenXR extension XR_EXT_win32_appcontainer_compatible
OpenXR: Found OpenXR extension XR_KHR_binding_modification
OpenXR: Found OpenXR extension XR_KHR_composition_layer_depth
OpenXR: Found OpenXR extension XR_KHR_visibility_mask
OpenXR: Found OpenXR extension XR_EXT_active_action_set_priority
OpenXR: Found OpenXR extension XR_EXT_dpad_binding
OpenXR: Found OpenXR extension XR_EXT_frame_composition_report
OpenXR: Found OpenXR extension XR_EXT_hand_tracking
OpenXR: Found OpenXR extension XR_EXT_hand_joints_motion_range
OpenXR: Found OpenXR extension XR_EXT_hp_mixed_reality_controller
OpenXR: Found OpenXR extension XR_EXT_palm_pose
OpenXR: Found OpenXR extension XR_FB_display_refresh_rate
OpenXR: Found OpenXR extension XR_HTC_vive_cosmos_controller_interaction
OpenXR: Found OpenXR extension XR_HTC_vive_focus3_controller_interaction
OpenXR: Found OpenXR extension XR_HTC_vive_wrist_tracker_interaction
OpenXR: Found OpenXR extension XR_MND_headless
OpenXR: Found OpenXR extension XR_VALVE_analog_threshold
OpenXR: Found OpenXR extension XR_HTCX_vive_tracker_interaction
OpenXR: Found OpenXR extension XR_EXT_debug_utils
OpenXR: Enabling extension XR_EXT_palm_pose
OpenXR: Enabling extension XR_KHR_composition_layer_depth
OpenXR: Enabling extension XR_HTC_vive_cosmos_controller_interaction
OpenXR: Enabling extension XR_HTC_vive_focus3_controller_interaction
OpenXR: Enabling extension XR_HTCX_vive_tracker_interaction
OpenXR: Enabling extension XR_FB_display_refresh_rate
OpenXR: Enabling extension XR_EXT_hp_mixed_reality_controller
OpenXR: Enabling extension XR_KHR_vulkan_enable2
Running project: D:/Projects/Godot/Godot Projects/Beta 2 OpenXR Test
Godot Engine v4.2.beta2.official.f8818f85e - https://godotengine.org
TextServer: Added interface "Dummy"
OpenXR: Found OpenXR extension XR_KHR_vulkan_enable
OpenXR: Found OpenXR extension XR_KHR_vulkan_enable2
OpenXR: Found OpenXR extension XR_KHR_D3D11_enable
OpenXR: Found OpenXR extension XR_KHR_D3D12_enable
OpenXR: Found OpenXR extension XR_KHR_opengl_enable
OpenXR: Found OpenXR extension XR_KHR_win32_convert_performance_counter_time
OpenXR: Found OpenXR extension XR_EXT_win32_appcontainer_compatible
OpenXR: Found OpenXR extension XR_KHR_binding_modification
OpenXR: Found OpenXR extension XR_KHR_composition_layer_depth
OpenXR: Found OpenXR extension XR_KHR_visibility_mask
OpenXR: Found OpenXR extension XR_EXT_active_action_set_priority
OpenXR: Found OpenXR extension XR_EXT_dpad_binding
OpenXR: Found OpenXR extension XR_EXT_frame_composition_report
OpenXR: Found OpenXR extension XR_EXT_hand_tracking
OpenXR: Found OpenXR extension XR_EXT_hand_joints_motion_range
OpenXR: Found OpenXR extension XR_EXT_hp_mixed_reality_controller
OpenXR: Found OpenXR extension XR_EXT_palm_pose
OpenXR: Found OpenXR extension XR_FB_display_refresh_rate
OpenXR: Found OpenXR extension XR_HTC_vive_cosmos_controller_interaction
OpenXR: Found OpenXR extension XR_HTC_vive_focus3_controller_interaction
OpenXR: Found OpenXR extension XR_HTC_vive_wrist_tracker_interaction
OpenXR: Found OpenXR extension XR_MND_headless
OpenXR: Found OpenXR extension XR_VALVE_analog_threshold
OpenXR: Found OpenXR extension XR_HTCX_vive_tracker_interaction
OpenXR: Found OpenXR extension XR_EXT_debug_utils
OpenXR: Enabling extension XR_EXT_palm_pose
OpenXR: Enabling extension XR_KHR_composition_layer_depth
OpenXR: Enabling extension XR_HTC_vive_cosmos_controller_interaction
OpenXR: Enabling extension XR_HTC_vive_focus3_controller_interaction
OpenXR: Enabling extension XR_HTCX_vive_tracker_interaction
OpenXR: Enabling extension XR_FB_display_refresh_rate
OpenXR: Enabling extension XR_EXT_hp_mixed_reality_controller
OpenXR: Enabling extension XR_KHR_vulkan_enable2

It simply stops after "OpenXR: Enabling extension XR_KHR_vulkan_enable2"
This is the console output for the OpenXR 1.0.28 beta 2 version:
Details

D:\Projects\Godot>godot.windows.editor.x86_64.console.exe --verbose
Godot Engine v4.2.beta2.official.3c591f53f - https://godotengine.org
TextServer: Added interface "Dummy"
TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
Native OpenGL API detected: 3.3: NVIDIA - NVIDIA GeForce RTX 3060 Ti
NVAPI: Init OK!
NVAPI: Disabled OpenGL threaded optimization successfully
Using "wintab" pen tablet driver...
Shader 'CanvasSdfShaderGLES3' SHA256: 48d6450939fd0c3882887ad90eac03fbafb9eb69d2b47aeacb0c810dc60dd60f
Shader 'SkeletonShaderGLES3' SHA256: 9d255e374ce0c426eb7722316805d5f32c26d6d6595350cdc749b0d85b075324
Shader 'ParticlesShaderGLES3' SHA256: f66b9725d7d5da6d8f73bbd5da9bd9729ec7695ff4461b1743e9809ae6131a27
Shader 'ParticlesCopyShaderGLES3' SHA256: 0051fa04202b9f23982e2ab102a167e0bbe5ad2b4e4223aa7f61a64ba82566f3
Shader 'CopyShaderGLES3' SHA256: 37e2322858e23cdbf507d3f1d183279902d89c59698e393893b0d8a6e15deca1
Shader 'CanvasShaderGLES3' SHA256: 62150a8b66c267e6b8b08a034f1a127ef33cbaf80242c2f915f5606fee19cad2
Shader 'CanvasOcclusionShaderGLES3' SHA256: cfde6a4ce32c005c5bcb401cf8552b379fc2b5d23303f299586decca5ca3f3fd
Shader 'SceneShaderGLES3' SHA256: 462e088a0eb0dc1eabf54a9fde34660df9e7313aac1f3da9bebdef47b4c82371
Shader 'SkyShaderGLES3' SHA256: 9ee4cd2240cc70fe8860b005f4a236c35d994c6c8a68f96d333d384b3c4b5a1b
Shader 'CubemapFilterShaderGLES3' SHA256: 6c1156fecfd6badbd0d56475f67e7d0d7250dfdcd4fb1f0e037c3fd86a909b74
OpenGL API 3.3.0 NVIDIA 537.58 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3060 Ti
WASAPI: Activated output_device using IAudioClient3 interface
WASAPI: wFormatTag = 65534
WASAPI: nChannels = 2
WASAPI: nSamplesPerSec = 48000
WASAPI: nAvgBytesPerSec = 384000
WASAPI: nBlockAlign = 8
WASAPI: wBitsPerSample = 32
WASAPI: cbSize = 22
WASAPI: mix_rate = 48000
WASAPI: fundamental_period_frames = 480
WASAPI: min_period_frames = 480
WASAPI: max_period_frames = 480
WASAPI: selected a period frame size of 480
WASAPI: detected 2 channels
WASAPI: audio buffer frames: 480 calculated latency: 10ms
TextServer: Primary interface set to: "ICU / HarfBuzz / Graphite (Built-in)".
CORE API HASH:<PHONE_NUMBER>
EDITOR API HASH:<PHONE_NUMBER>
EditorSettings: Load OK!
Scanning projects at: D:/Projects/Godot/Godot Projects
MbedTLS: Some X509 certificates could not be parsed (1 certificates skipped).
Loaded system CA certificates
EditorSettings: Save OK!
Running project: D:/Projects/Godot/Godot Projects/Beta 2 OpenXR Test
Godot Engine v4.2.beta2.official.3c591f53f - https://godotengine.org
TextServer: Added interface "Dummy"
OpenXR: Found OpenXR extension XR_KHR_vulkan_enable
OpenXR: Found OpenXR extension XR_KHR_vulkan_enable2
OpenXR: Found OpenXR extension XR_KHR_D3D11_enable
OpenXR: Found OpenXR extension XR_KHR_D3D12_enable
OpenXR: Found OpenXR extension XR_KHR_opengl_enable
OpenXR: Found OpenXR extension XR_KHR_win32_convert_performance_counter_time
OpenXR: Found OpenXR extension XR_EXT_win32_appcontainer_compatible
OpenXR: Found OpenXR extension XR_KHR_binding_modification
OpenXR: Found OpenXR extension XR_KHR_composition_layer_depth
OpenXR: Found OpenXR extension XR_KHR_visibility_mask
OpenXR: Found OpenXR extension XR_EXT_active_action_set_priority
OpenXR: Found OpenXR extension XR_EXT_dpad_binding
OpenXR: Found OpenXR extension XR_EXT_frame_composition_report
OpenXR: Found OpenXR extension XR_EXT_hand_tracking
OpenXR: Found OpenXR extension XR_EXT_hand_joints_motion_range
OpenXR: Found OpenXR extension XR_EXT_hp_mixed_reality_controller
OpenXR: Found OpenXR extension XR_EXT_palm_pose
OpenXR: Found OpenXR extension XR_FB_display_refresh_rate
OpenXR: Found OpenXR extension XR_HTC_vive_cosmos_controller_interaction
OpenXR: Found OpenXR extension XR_HTC_vive_focus3_controller_interaction
OpenXR: Found OpenXR extension XR_HTC_vive_wrist_tracker_interaction
OpenXR: Found OpenXR extension XR_MND_headless
OpenXR: Found OpenXR extension XR_VALVE_analog_threshold
OpenXR: Found OpenXR extension XR_HTCX_vive_tracker_interaction
OpenXR: Found OpenXR extension XR_EXT_debug_utils
OpenXR: Enabling extension XR_EXT_palm_pose
OpenXR: Enabling extension XR_KHR_composition_layer_depth
OpenXR: Enabling extension XR_HTC_vive_cosmos_controller_interaction
OpenXR: Enabling extension XR_HTC_vive_focus3_controller_interaction
OpenXR: Enabling extension XR_HTCX_vive_tracker_interaction
OpenXR: Enabling extension XR_FB_display_refresh_rate
OpenXR: Enabling extension XR_EXT_hp_mixed_reality_controller
OpenXR: Enabling extension XR_KHR_vulkan_enable2
OpenXR: Running on OpenXR runtime:  SteamVR/OpenXR   2.0.6
OpenXR: Found supported view configuration XR_VIEW_CONFIGURATION_TYPE_PRIMARY_STEREO
OpenXR: Found supported view configuration view

width: 3240
height: 3240
sample count: 1
recommended render width: 3040
recommended render height: 2972
recommended render sample count: 1
OpenXR: Found supported view configuration view
width: 3240
height: 3240
sample count: 1
recommended render width: 3040
recommended render height: 2972
recommended render sample count: 1
OpenXR: Found environmental blend mode XR_ENVIRONMENT_BLEND_MODE_OPAQUE
TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
OpenXR: XrGraphicsRequirementsVulkan2KHR:
minApiVersionSupported:  1.0.0
maxApiVersionSupported:  1.2.0
Vulkan API 1.3.242 - Forward+ - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce RTX 3060 Ti
Optional extension VK_KHR_incremental_present not found
Optional extension VK_GOOGLE_display_timing not found
Vulkan Variable Rate Shading supported:
Pipeline fragment shading rate
Primitive fragment shading rate
Attachment fragment shading rate, min texel size: (16, 16), max texel size: (16, 16)
Vulkan multiview supported:
max view count: 32
max instances: 134217727
Vulkan subgroup:
size: 32
min size: 32
max size: 32
stages: STAGE_VERTEX, STAGE_TESSELLATION_CONTROL, STAGE_TESSELLATION_EVALUATION, STAGE_GEOMETRY, STAGE_FRAGMENT, STAGE_COMPUTE, STAGE_RAYGEN_KHR, STAGE_ANY_HIT_KHR, STAGE_CLOSEST_HIT_KHR, STAGE_MISS_KHR, STAGE_INTERSECTION_KHR, STAGE_CALLABLE_KHR, STAGE_TASK_NV, STAGE_MESH_NV
supported ops: FEATURE_BASIC, FEATURE_VOTE, FEATURE_ARITHMETIC, FEATURE_BALLOT, FEATURE_SHUFFLE, FEATURE_SHUFFLE_RELATIVE, FEATURE_CLUSTERED, FEATURE_QUAD, FEATURE_PARTITIONED_NV
quad operations in all stages
Startup PSO cache (3.1 MiB)
Using "wintab" pen tablet driver...
Creating VMA small objects pool for memory type index 1
Shader 'CanvasSdfShaderRD' (group 0) SHA256: 2da4555da166e3fa2e34bc5bc7ff39bbe878b1459ddeb5f33fe42edd113a0f4d
Shader 'SkeletonShaderRD' (group 0) SHA256: 6b9e0a7aa1f71e57994d8b2d2e6815c03af301e18e2d4701486f4cd29e97405e
Shader 'SortShaderRD' (group 0) SHA256: 98720c565cf8cb2f4022b78554a01f34fb32dd7f4a2e5f5e5e1ab97278132a2d
Shader 'ParticlesShaderRD' (group 0) SHA256: 89510620c9e4d2781a14914c1213dbbafe6f9893ce26d57371f65a2dcd5a37b5
Shader 'ParticlesCopyShaderRD' (group 0) SHA256: 4dcc13f169089ddbc6d75b184c54c3e98f2d7bf741523fef8a817138eb19c1da
Shader 'CanvasShaderRD' (group 0) SHA256: 4143b4698ce66f67e06f0fb8b8f7813a39660f9460b2bbda137426534886f003
Shader 'CanvasOcclusionShaderRD' (group 0) SHA256: 227df8b9a6456251e33c505f36da0cbd4000a05d29227bf973b49774b197afdb
Shader 'ClusterRenderShaderRD' (group 0) SHA256: 672a09dc45372af8284cded345858cad489466bc759e1161f15262c524cc3f1c
Shader 'ClusterStoreShaderRD' (group 0) SHA256: b2063042c8b8cf654b13df64d2420602157854edaec486f20c5f8bc18f4776ac
Shader 'ClusterDebugShaderRD' (group 0) SHA256: b03c7d2c1b71b5330821201056c515077a259f8c42d9e39145bf36a184888eea
Shader 'SceneForwardClusteredShaderRD' (group 0) SHA256: 7088645c89a2949fa1a43a4712e834f190888be543d2b6e1bcc938b677804653
Shader 'SceneForwardClusteredShaderRD' (group 1) SHA256: ca3295fd3ed73df4d6d3b24d76372f0b9fc221f6469ec6cc88e62127a9a3f821
Shader 'SceneForwardClusteredShaderRD' (group 2) SHA256: 21b6898b4cbca3459e781b5354135d61c01edad9e94b3373bba0c313a6dceb1f
Shader 'SceneForwardClusteredShaderRD' (group 3) SHA256: a83f0eab0e898b1d008d950556e4b05cc12fab3083f7dbf3d89a8c791adc5c1d
Shader 'ResolveShaderRD' (group 0) SHA256: 49384ddea718dc4da28e5fe827b955a84101d20e5d07eca5e633c260ba6d4e90
Shader 'TaaResolveShaderRD' (group 0) SHA256: b6cf7b762e8cf60fb5e4b7c2fc009f1529f6e80db0cc0a9ef931ad0e94666082
Shader 'Fsr2DepthClipPassShaderRD' (group 0) SHA256: c060051a4ef6a0fd5154c8e12fe8cd98a8a8e63ac9be0d2b09b58aa753dcf495
Shader 'Fsr2ReconstructPreviousDepthPassShaderRD' (group 0) SHA256: 776ee8664d7b419b84a4f27d29ddbcd5329fb04ab3168d9631176f42309e0f58
Shader 'Fsr2LockPassShaderRD' (group 0) SHA256: 44ab3abcf076d258bd3fe38bafea525c71ddd175a48410975bde6a06a1bf6952
Shader 'Fsr2AccumulatePassShaderRD' (group 0) SHA256: 51db1f43d74b159bd8ad69995d8516f18d2bf5c8d3f7816cd6cd21573f2d90e1
Shader 'Fsr2RcasPassShaderRD' (group 0) SHA256: 300032d0d24a71b3a65c2951d426328564f518bb19f1ef8d39a381cab6cc87ed
Shader 'Fsr2ComputeLuminancePyramidPassShaderRD' (group 0) SHA256: fcacaec243e9e6ab0f9a8923abe05ec4745500faa21d045f83e16474e43a9821
Shader 'Fsr2AutogenReactivePassShaderRD' (group 0) SHA256: d3bca818f02507adb6caf9527244e3bdf036e396110291c37ed2b2a24a4d791d
Shader 'Fsr2TcrAutogenPassShaderRD' (group 0) SHA256: 65c9f2476634ce0b820445295544dff7c4175e769a25882a5535e9e44303ed37
Shader 'SsEffectsDownsampleShaderRD' (group 0) SHA256: 055e88d7f6eb9e0f8da6c58130e70d3e676878a4e945c8f2e596aa1e72fee85b
Shader 'SsilShaderRD' (group 0) SHA256: 488d840e8d74655cb9c661fb041d951906ed2028a0f51d43d2e4dcd52acf853b
Shader 'SsilImportanceMapShaderRD' (group 0) SHA256: 347eead47d11729e0444095f01b9c5387d745aebd47e45eb17a82a3e3e4a47b9
Shader 'SsilBlurShaderRD' (group 0) SHA256: e9856c23b783473b55c1944e06523ba830c687f113bc9f5e27980b7094ca3ace
Shader 'SsilInterleaveShaderRD' (group 0) SHA256: ecb805b60dcd291a6b2ef45c9c265c235c1e144cc7e5797d049286ca5a485cf0
Shader 'SsaoShaderRD' (group 0) SHA256: 5d9b80f46c69c0d700d7db92d40ec2e9d03204747c9e3589ad8faff94e58be80
Shader 'SsaoImportanceMapShaderRD' (group 0) SHA256: 9840a995f2583a6a23766c18fd8a161584b8081a6d171f4977c9a719708a76ff
Shader 'SsaoBlurShaderRD' (group 0) SHA256: c91b993a755002fc08552273ce547e8deec4f86b588c44f18e30f447b60f9e08
Shader 'SsaoInterleaveShaderRD' (group 0) SHA256: 8ec73e745560f3db2d18232101c4e47d980712b64dbd1b5151c4c083faad0d62
Shader 'ScreenSpaceReflectionScaleShaderRD' (group 0) SHA256: dba4f9192462502cdcb0f323fb21a84ed1270b4368ba7dbf31294533db639676
Shader 'ScreenSpaceReflectionShaderRD' (group 0) SHA256: f09e89c0d5720d4571f4f57d367bffb6ff5676ae36c765b17d33143894b9dc75
Shader 'ScreenSpaceReflectionFilterShaderRD' (group 0) SHA256: e6dc3be1f3d8c1e08d9a402fbf92ad3c52c3b3c3b57bbec08f323409bcb392ea
Shader 'SubsurfaceScatteringShaderRD' (group 0) SHA256: dfe039cec02ad04859eb8aec6b0a296e69f86b36a15856012091c8c469ec52de
Shader 'SkyShaderRD' (group 0) SHA256: dc3e2524c490950b274c8670842ed04e5108850e6b15baeec800f04a51bf2531
Shader 'VoxelGiShaderRD' (group 0) SHA256: 2b5cdda1273a60c357fe053d7c4d535a1c27c50cfc741bfb4312789e386df8dc
Shader 'VoxelGiDebugShaderRD' (group 0) SHA256: 0cfb7708cfcb2cf6375e27ddb340b12e2288fa5783ea3cd3707f7fe9e4bc5606
Shader 'SdfgiPreprocessShaderRD' (group 0) SHA256: d4d6726993848d12e76aee95e4bc5e722e5023ad942f11416fe669d926016ca8
Shader 'SdfgiDirectLightShaderRD' (group 0) SHA256: cbfc6e45216786419a94b73fef9538d56e97556d1e46e7dea936b1acf587ce02
Shader 'SdfgiIntegrateShaderRD' (group 0) SHA256: 822fc4af8c21186ee0fbf9bb2536df91645b4395ca59c31e351c28948a243922
Shader 'GiShaderRD' (group 0) SHA256: 7fa8ea0eb00ab9b7f5df1b2d7b0c05bf7af51b30e197445383222aa14063bbb8
Shader 'SdfgiDebugShaderRD' (group 0) SHA256: 70fca7c15e07817a5c11395a874a9834362739206041005ca9912d3c7696acef
Shader 'SdfgiDebugProbesShaderRD' (group 0) SHA256: ad2a30f8f75708cc698ab6b1cf31342e0e4d63df616431d1b639d1f1dc3374cd
Shader 'VolumetricFogShaderRD' (group 0) SHA256: f513e25cf6d57305b7fe835d2121eb4f7d457ea77b48abb82834b0760c36451d
Shader 'VolumetricFogProcessShaderRD' (group 0) SHA256: e208d78942dd90e93a90bdc0ec3a1c1faa86e6b07d32c806f7747beb97726168
Shader 'BokehDofShaderRD' (group 0) SHA256: 3ef5405c3e52c7799fd3149ff0e8391f9786ebe415e5f9354df595b081b161d4
Shader 'CopyShaderRD' (group 0) SHA256: c72fe82c2e6bf0b2b31d489f3650875f7019311af5e1f7902da11ef63c3f6670
Shader 'CopyToFbShaderRD' (group 0) SHA256: 071d8808c4f83ba962d4735bbdce43a7509660bfba0b4743fff3daf4a55b3f4e
Shader 'CubeToDpShaderRD' (group 0) SHA256: 36a72391b8152dd95ce067cd621a371b944703880abf7bba25306ebf06e6ecee
Shader 'CubemapDownsamplerShaderRD' (group 0) SHA256: 0f6c73b336c33ecee026cf6231fd5b4913ede54c27be5d2e0650734003fa2014
Shader 'CubemapFilterShaderRD' (group 0) SHA256: daa1f8507840e5a5b93cb7e87c0f4a684b8197631071cb9e4e7eea2293bef280
Shader 'CubemapRoughnessShaderRD' (group 0) SHA256: 6b1d40eaad996bbad18549bbe06d67c5b9fb661acfd8f987e00d6c611ce8c3d7
Shader 'SpecularMergeShaderRD' (group 0) SHA256: 6d3fb44c69b02aa2eb6c78ad2ba737f22645386344990b9cf91d182682aaef2d
Shader 'ShadowFrustumShaderRD' (group 0) SHA256: c5a0b09d5fe957f31b3616a177feb7aa644f494eea72f6626bed713b52596bcd
Shader 'MotionVectorsShaderRD' (group 0) SHA256: aae06cfd6b7b38784afecddc38336db062c8cc827b083eae29cfb88cdd0fbd4f
Shader 'LuminanceReduceShaderRD' (group 0) SHA256: bd5680efdafda3d18ed0ffb5f233cd9bbcc61deb54af5f6108e42bd44ac530d8
Shader 'TonemapShaderRD' (group 0) SHA256: 63b9095ca8841894f9deed09ed769c839ccd2ad64107a4fd60be893e60da09f4
Shader 'VrsShaderRD' (group 0) SHA256:<PHONE_NUMBER>77969f64eded7a0d877598e52eaa63b1eb27543c48f2f61a8adc21
Shader 'FsrUpscaleShaderRD' (group 0) SHA256: ed7395341be9a9c52d2aa2e4e47ef30bc936687e8ebbbada0bd73adf7bb070e1
Shader 'BlitShaderRD' (group 0) SHA256: 4cee5d78da9b45a66dd09108f6bf8ab2177b92aba5e8f6178a4041af93d857b5
WASAPI: Activated output_device using IAudioClient3 interface
WASAPI: wFormatTag = 65534
WASAPI: nChannels = 2
WASAPI: nSamplesPerSec = 48000
WASAPI: nAvgBytesPerSec = 384000
WASAPI: nBlockAlign = 8
WASAPI: wBitsPerSample = 32
WASAPI: cbSize = 22
WASAPI: mix_rate = 48000
WASAPI: fundamental_period_frames = 480
WASAPI: min_period_frames = 480
WASAPI: max_period_frames = 480
WASAPI: selected a period frame size of 480
WASAPI: detected 2 channels
WASAPI: audio buffer frames: 480 calculated latency: 10ms

TextServer: Primary interface set to: "ICU / HarfBuzz / Graphite (Built-in)".
ERROR: OpenXR: Unsupported toplevel path /user/eyes_ext
at: (modules/openxr/openxr_api.cpp:200)
OpenXR: Interaction profile /interaction_profiles/bytedance/pico4_controller requires extension XR_BD_controller_interaction
OpenXR: Interaction profile /interaction_profiles/samsung/odyssey_controller requires extension XR_EXT_samsung_odyssey_controller
OpenXR: Interaction profile /interaction_profiles/huawei/controller requires extension XR_HUAWEI_controller_interaction
ERROR: OpenXR: Unsupported interaction profile /interaction_profiles/ext/eye_gaze_interaction
at: (modules/openxr/openxr_api.cpp:220)
OpenXR: Found supported reference space XR_REFERENCE_SPACE_TYPE_VIEW
OpenXR: Found supported reference space XR_REFERENCE_SPACE_TYPE_LOCAL
OpenXR: Found supported reference space XR_REFERENCE_SPACE_TYPE_STAGE
OpenXR: Found supported swapchain format VK_FORMAT_R8G8B8A8_SRGB
OpenXR: Found supported swapchain format VK_FORMAT_B8G8R8A8_SRGB
OpenXR: Found supported swapchain format VK_FORMAT_R32G32B32A32_SFLOAT
OpenXR: Found supported swapchain format VK_FORMAT_R32G32B32_SFLOAT
OpenXR: Found supported swapchain format VK_FORMAT_R16G16B16A16_SFLOAT
OpenXR: Found supported swapchain format VK_FORMAT_A2B10G10R10_UNORM_PACK32
OpenXR: Found supported swapchain format VK_FORMAT_D32_SFLOAT
OpenXR: Found supported swapchain format VK_FORMAT_D16_UNORM
OpenXR: Found supported swapchain format VK_FORMAT_D24_UNORM_S8_UINT
OpenXR: Found supported swapchain format VK_FORMAT_D32_SFLOAT_S8_UINT
XR: Primary interface set to: OpenXR
CORE API HASH:<PHONE_NUMBER>
EDITOR API HASH:<PHONE_NUMBER>
MbedTLS: Some X509 certificates could not be parsed (1 certificates skipped).
Loaded system CA certificates
OpenXR EVENT: session state changed to XR_SESSION_STATE_IDLE
On state idle
OpenXR EVENT: session state changed to XR_SESSION_STATE_READY
On state ready
Using color swap chain format:VK_FORMAT_R8G8B8A8_SRGB
OpenXR View pose became valid
OpenXR EVENT: session state changed to XR_SESSION_STATE_SYNCHRONIZED
On state synchronized
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/left_foot changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/right_foot changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/left_shoulder changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/right_shoulder changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/left_elbow changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/right_elbow changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/left_knee changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/right_knee changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/waist changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/chest changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/camera changed to /interaction_profiles/htc/vive_tracker_htcx
OpenXR: Interaction profile for /user/vive_tracker_htcx/role/keyboard changed to /interaction_profiles/htc/vive_tracker_htcx
OpenVR Head pose now tracking with high confidence

PS: Thanks to everone involved for their hard work and dedication towards making this the great engine that it is.

I wonder what the source of this is as I've been using my own builds with OpenXR 10.0.30 without problems for some time now. What do we do different in our build process that would introduce this instability?

Official builds are made with mingw-gcc, and LTO. So they can have different compilation/optimization bugs than MSVC. Seems like openxr 1.0.30 added something that triggers a compiler bug.

I've made a couple more builds to test whether upgrading mingw-gcc (with versions from Fedora 39 instead of Fedora 36) or OpenXR helps. Could you test both and let me know if they work?

https://downloads.tuxfamily.org/godotengine/testing/Godot_v4.2-beta2_windows_openxr_1.0.30_fedora39.zip
https://downloads.tuxfamily.org/godotengine/testing/Godot_v4.2-beta2_windows_openxr_1.0.31_fedora39.zip

All three of those test builds crash at the same point right after the OpenXR: Enabling extension XR_KHR_vulkan_enable2.

Thanks! I'll make a test build with openxr 1.0.29 tomorrow, and based on the results roll back to 1.0.28 or 1.0.29 for 4.2.
Then we can see why it crashes in newer versions and report it upstream.

All three test versions also crash right after "OpenXR: Enabling extension XR_KHR_vulkan_enable2" for me.

Another test build with openxr 1.0.29, built on Fedora 36 (same as all previous 4.2 builds):
https://downloads.tuxfamily.org/godotengine/testing/Godot_v4.2-beta2_windows_openxr_1.0.29_fedora36.zip
The diff between 1.0.29 and 1.0.30 isn't big, so I don't have high hopes this version works. But it's worth testing to know if we should revert to 1.0.28 or 1.0.29.

Unfortunately, I get the same result as with the other test builds.

Yup - same with me - the new one crashes at the same spot.

I'm reverting to 1.0.28 with #83829, so this should solve the issue for 4.2 beta 3 and later.
I'll keep this issue open to further investigate why it crashes, so we can get it fixed and eventually update to a newer openxr SDK.

Just tested this build running all three renderers and using godot-xr-template as a testing project and runs fine.
Windows 10, AMD Ryzen 87, NVidia 4070 Ti, Running PCVR Quest Pro over Airlink

The new build runs the original MRP just fine on my system.


DOC: Adding auto_comment.yml file

What's wrong with the existing documentation
We need to add an auto-comment.yml that will automatically welcome, greet and provide necessary information to the contributors when they create new issues, PR, and when these will get assigned or merged respectively. This will promote motivation and performance
@nikhil25803 Please assign me this issue under gssoc'23
Add ScreenShots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC 23 contributor
[X] I want to work on this issue

Really not looking for that many bots  action for now, though I want some automation on every PR merge which I also discussed in issue #251 |
What I want is that on every PR merged, I want the bot to send this message
Great work  @{user_name} !!
Do not forget to
+ Share your contribution on socials(Twitter mainly), tag us and Clueless 🫂
+ Give this repository a star ✨
+ Follow Clueless Community on GitHub ✅

Do let me know if that is possible, I will assign you the issue.

Hey @nikhil25803 Please Review my PR I have Alreedy Created This PR: https://github.com/Clueless-Community/scrape-up/pull/346


Overwrite (true) should be a configurable option

Perhaps "overwrite=true" should be our default behavior, but we should give user a command line option to turn this off for all entities.
See issue where we changed default behavior for Triggers (as an example).  https://github.com/apache/incubator-openwhisk-wskdeploy/pull/377

At the time of this issue being opened here are all the places we hardcoded the default:
Matt$ grep -r "Insert" . *.g
./deployers/servicedeployer.go:	_, _, err := deployer.Client.Packages.Insert(packa, true)
./deployers/servicedeployer.go:	_, _, err := deployer.Client.Packages.Insert(packa, true)
./deployers/servicedeployer.go:	_, _, err := deployer.Client.Triggers.Insert(trigger, true)
./deployers/servicedeployer.go:	_, _, err := deployer.Client.Triggers.Insert(t, false)
./deployers/servicedeployer.go:	_, _, err := deployer.Client.Rules.Insert(rule, true)
./deployers/servicedeployer.go:	_, _, err := deployer.Client.Actions.Insert(action, true)
./deployers/servicedeployer.go:	_, _, err := deployer.Client.Apis.Insert(api, nil, true)
Binary file ./wskdeploy matches

Its still the same ...


cloudfirestore/CloudFirestorePlugin.java

Is your feature request related to a problem? Please describe.
I'm always frustrated when when attempting to load my application and I get the red text that states the following:
Note: /Users/user/flutter/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.5/android/src/main/java/io/flutter/plugins/firebase/cloudfirestore/CloudFirestorePlugin.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
warning: [options] source value 1.5 is obsolete and will be removed in a future release
warning: [options] target value 1.5 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
3 warnings

How did you solved this today?
I'm using Flutter 1.18.0-11.pre SDK

Hi @ram231
can you please provide your flutter doctor -v ,
your flutter run --verbose,
your pubspec.yaml
and a reproducible minimal code sample.
Thank you

@iapicca , Here is the result in the separate issue here #2611
I closed it due to duplicate issues.

Hi @taracell
I see there's an open issue addressing the case you described.
Please follow up on that issue, I'm closing the current one as duplicate.
If you disagree, please write in the comments and I will reopen it.
Thank you

I have the same error on Flutter 1.20.0-7.3.pre
Note: /Users/user/flutter/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.7/android/src/main/java/io/flutter/plugins/firebase/cloudfirestore/CloudFirestorePlugin.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

I ran the commands below but no luck.
flutter pub cache repair
flutter clean


First launch time is different in pre and post 21 Android

For periodic alarms in pre-21 android library is using AlarmManager through setRepeating method.
  alarmManager.setRepeating(AlarmManager.RTC_WAKEUP, System.currentTimeMillis() + request.getIntervalMs(), request.getIntervalMs(), pendingIntent);
Second parameter is triggerAtMillis. Documentation says that this is time when alarm will be started first time :

time in milliseconds that the alarm should first go off, using the appropriate clock (depending on the alarm type).

So, this is guarantee that it couldn't start before this time. Because it set to System.currentTimeMillis() + request.getIntervalMs() .
But, for post 21 android it isn't guarantee when job will be executed first time. It even could start at the same time when job is scheduled. But in pre 21 android it definitely wouldn't.
So, we have a slightly different first launch time in different android versions.

Android 5+ is using the JobScheduler. But that's the whole purpose of this project. The platform should decide, when it's the best time to run your job. Normal and repeating jobs should be inexact like here.
If you need an exact repeating job, then you should use an exact job and reschedule it yourself.

I agree with this completely. That's the point that it should decide when start it. But at pre-5 android task is definitely wouldn't run before this period is passed. Because time, when it should run firs time, is set to System.currentTimeMillis() + request.getIntervalMs().
Problem is in initialization of AlarmManager tasks, not in JobScheduler.

What would you do instead? I could either change the start interval to maybe current time + interval / 2 or use setInexactRepeating. What would you prefer?

@Kpeved Any response?

What about setting the interval to current time + constant ?

The constant needs to be dynamic and now it's the interval

Is this still an issue?


Merge tag 'swift-DEVELOPMENT-SNAPSHOT-2019-08-05-a' into tensorflow

Friend PR: https://github.com/apple/swift/pull/26562

When testing lldb, I ran into the same problem as @dan-zheng: https://github.com/apple/swift-lldb/pull/1837#issuecomment-517067410. Since this is not considered a regression, let's get this thing merged.


update zh-CN translation

Hi,
I have fixed the Chinese translation(zh-CN).
Mezzanine is awesome, I like it.
Thank you.

Thank you!


ChoiceManager refactoring

ChoiceManager is unwieldy. It is gigantic. I split it into three separate files:
ChoiceManager.java
This contains the various control flow variables - ChoiceManager.handlingChoice, ChoiceManager.lastChoice, ChoiceManager.lastResponseText, and so on - we are familiar with.
It contains the various methods called by GenericRequest - preChoice, postChoice0, postChoice1, postChoice2, visitChoice, registerRequest - to update those variables appropriately.
It also contains the code for automating choices via CHOICE_HANDLER.
All of the choice-specific code has been moved to ChoiceControl, with the exception of the automation code that knows how to choose "appropriate" decisions for specific choices based on current play state.
ChoiceControl.java
This contains the massive switch statements which used to be in postChoice1, visitChoice,  and the other control flow methods called by GenericRequest.
ChoiceAdventures.java
This contains the data for all the choices we support in the GUI (with "whichchoiceXXXX" properties - used for automation) or in the Relay Browser (choice spoilers).
In addition to refactoring the massive file into three coherent modules, I made the following improvements:

No more storing & passing data around in Object[] and Object[][] structures. We now have actual classes.
No more array searches of large arrays to locate the choice data for a particular choice number. HashMaps work well.

My testing looks good, so far. The GUI for choices is unchanged. I see choice spoilers in the Relay Browser. I'm going to test more tomorrow (well, today. After I sleep. :)
I'm marking this ready to review, in case anybody wants to get a head start with it and give me comments.

I think this is good to go.


Integrate Dependency Checker Plugin into pom.client.xml

This PR integrates the dependency checker's Maven plugin into pom.client.xml. The analyses pipeline will no longer need to checkout the source code from GitHub and install the checker locally. A new profile was added into pom.client.xml so this check won't be triggered by default and the plugin will only run for pom.client.xml and none of the inheriting projects.
Additionally, this PR also fixes the improperly configured dependency checker plugin used in the azure-sdk-bom project and revs the version being used.

/azp run java - aggregate-reports

/azp run java - aggregate-reports

/azp run java - aggregate-reports

How will this change socialize if we remove the list of modules from pom.client.xml which is one of the changes landing with the POM restructuring. Will dependency checker continue to work in that secnario.
Note ... that for the core pipeline we'll be running tests with the -am and -amd switches which means it should build the full graph of track 2 libraries. Take a look at this PR to see what the incoming changes look like:
https://github.com/Azure/azure-sdk-for-java/pull/8242

@mitchdenny That is a good question, I'll need to review what is being changed in that PR. If there is still a parent that lists all modules this change is still possible and can be ported to the new pom, if not this change will basically be a moot point.


[PeerReview] System test for MeasureMultiple API in dcpower

What does this Pull Request accomplish?
Added system test for MeasureMultiple API for ni-dcpower
Why should this Pull Request be merged?
MeasureMultiple API is custom implemented. This test will catch any issues in case the API breaks because of any future changes.
What testing has been done?
Executed the test locally

@doshirohan , Jonathan had asked to target PRs to feature branch before sending to owners. So can you change target to feature branch and add a comment that this PR will be submitted after other PR goes in before adding owners?


Popup breaks with some css resets

The visbug popup seems to depend on some styles that can get reverted with some newer css resets, causing it to appear beneath the page content, full width, and in the document flow.
Steps to reproduce:

Create a react app that uses https://github.com/elad2412/the-new-css-reset
Open visbug

confirmed here https://stackblitz.com/edit/react-ts-bmgkzm?file=style.css,new-reset.css
curious that selector has higher specificity than a constructed stylesheet in a shadow :host. will investigate. thanks for reporting!

after some research, it appears that my :host styles need an !important in order to win over a style like this.
ToDo:

[ ] all light dom shadow styles should use !important


Create my-career-change-to-teaching-ian-wallace

title: My career change to teaching
date: "2022-01-31"
author: Ian Wallace
image:

thumbnail:

description: Ian Wallace had always wanted to be a teacher but didn’t feel ready when he finished university. After several different jobs and careers he finally took the plunge and hasn’t looked back.
keywords:

teacher training
trainee teacher course
SCITT
career change
tags:
becoming a teacher
career change to teaching

Looks good to me :)


Too many not_load_example.

In general, how many examples are expected to be not loaded? The number of examples not loaded in my case seems to be excessive.

Hello, there are two possible cases that may lead to not loading. The first case is that the relevant video lacks subtitle files. Considering that this baseline method relies on subtitle information, it will be unable to process videos that completely lack subtitle files, so they will be discarded. The second case is that the subtitle information is too long. Considering that the current GPU memory can hardly process excessively long text, max_len=2500 is preset in the CFG. When a video exceeds the subtitle length limit, it will be discarded.
If you want to reduce the number of unloaded videos, you can do so by increasing max_len (recommended 4000 or above), but on the premise that the GPU memory will not exceed the limit.

在运行test.py时
0%|                                                                                | 0/2937 [00:00<?, ?it/s[2]+  Killed                  python test.py
Killed
shape已经对齐了，检查了很多环节，不清楚是什么问题，您能帮我解答一下吗

就是main我是跑通了的，按道理说不应该是设备问题，test中检查了很多断点，数据也应该是读进去了，所使用的设备是4090。出现了以上的问题，test没有给出参数，想请问一下test的参数，以及您使用的设备条件。


FeatureRequest: Using the immediate window without building

VSCode Version: 14.0.24720.00 Update 1
OS Version: Windows 10

I want to run simple commands in the immediate window without building the solution.  For example I might want to type something like "Double.Parse("0.1")"; but currently I will get the error "Build Failed. For a list of build errors see the Error List. For detailed information about a build error select an item and press F1.".

@StratThinker pls provide information that allows us to reproduce your problem. What extensions do you have installed? What file is open? etc. Thanks!

I have EditorConfig, "End of the Line", various F# packages installed.  Every thing else looks like the default packages.  Although these are probably not the problem.
To reproduce the problem:

create a new console application.
Inside the Main method write some text that will not compile, for example "asdf"
Open up the immediate window
Type something simple like ""+0.1
Press enter
Instead of doing this calculation, it will try to build my solution, which will fail, and it will give the error "Build Failed. For a list of build errors see the Error List. For detailed information about a build error select an item and press F1."

  My feature request is to be able use the Immediate window like a command line application without building the solution, to test some simple calculations (for anything more complex I use a test solution).  Note that I am requesting something similar to Matlab's command line.

Sorry I see that I confused "visual studio" with "visual studio code".


Feature request: separate AST explorer into its own extension

I'm a programming language developer, and I've been looking for an extension exactly like the AST explorer. I'd love if it were possible to parse the AST from a file of some sort (likely just in the same format that r-a outputs) and explore it visually with a generalized AST, not just for Rust's AST. This would likely be its own extension, but I'm not exactly... good enough... at writing VSCode extensions to do this.

(If something like this does actually already exist, please let me know!)

https://astexplorer.net/ ?

@jhgg As far as I know, you can't do arbitrary ASTs with that, you'd have to modify the site and implement a parser interop within JS, which looks like it could be a pain. I'm mostly talking about just printing an AST in the RAST format and exploring it in vscode using that AST file and its source


[Event Request] Codeunit 442 "Sales-Post Prepayments" - OnBeforePrepmtAmount in BC22

Describe the request
Hello, I raised case #26088 which is approved for the current version, or it will be applied in the next major release. What I missed checking is if that publisher can also be created in BC22?
As I understand the reply from Mr. Schulz the publisher will be published in the current version (BC23) or the next major release (BC24).
Did I get this right(regarding BC versions)? And if I did, my question is can this publisher also be created for BC22, or should I adjust the extensibility request?
Best regards,
Marko
Additional context
We also need this publisher in BC22.
Internal work item: AB#506770

Availability update: We will publish a fix for this issue in the next update for release 22.
Build ID to track: 64685.

Availability update: We will publish a fix for this issue in the next update for release 23.
Build ID to track: 21893.


Indicate there are no upcoming events on the outside of a programs accordion.

Currently, if there are no future events for a program but there are past events we have an accordion that a user has to open up to see there is nothing to see. We should add an indicator on the outside of the accordion, to the right of the Program Name, letting users know there are no upcoming events. Possibly just "0 upcoming events." or "Currently, there are no more events planned."

 Indicate there are no upcoming events on the outside of a programs accordion. #1040


Add support for SwiftPM

Hi,
I'm using MagazineLayout in my library example app.
Thanks for the awesome library.
Details

Simply add a Package.swift file.
Related Issue

N/A
Motivation and Context

I want to use MagazineLayout via SwiftPM integrated with Xcode11.
How Has This Been Tested

No unit test.
I checked that my app can be installed this lib via SwiftPM.
Types of changes

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

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

this would be a very welcome addition

Can you please release a new tag?

@ra1028 ah thanks for the reminder, done! v1.5.2 should have it


Glowsquid Fix

fixes #22 by removing hard-coded values and implements the ones in the config.
Not tested, but looks correct. Needs verification.

also, is the biome whitelist found in the config actually do anything yet? I looked into your code and saw some more hard-coded biomes for every mob.


Stop directing the user to deleted branches

The project list page directs users to the last branch they were on, even if it no longer exists - let's change that logic to only direct them there if the branch still exists.
IMO we should also redirect users to the production branch if they try to go directly to a deleted branch.

Moved from dataform-co/dataform-co#1938
/cc @BenBirt

There is already a redirect in place for a branch that doesn't exist (or is deleted) to the user default, e.g. ...40720/b/asd is redirected to ...40720/overview. This redirect does not happen for child routes, e.g. ...40720/b/asd/overview is not redirected.
This is likely to do with the <IndexRedirect/> for branches, but I do not know enough about react routing to fix.


fix: update required ibm provider version to < 1.7

/run pipeline

:tada: This PR is included in version 1.21.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


How to scope a rails model against an actor gate

So I have a feature. I have setup an actor gate against the User model. It looks like this, when my user has the feature:

Any thoughts on the best approach for scoping this? How do I find all Users which have the "thing" feature?

Is it as simple as this?
irb(main):011:0> pp MyApp.flipper[:thing].actors_value
  Flipper::Adapters::ActiveRecord::Gate Load (0.3ms)  SELECT "flipper_gates".*  I wouldn't recommend trying to setup a has many relationship or anything as flipper really isn't designed to work that way.
MyApp.flipper[:thing].actors_value.map { |flipper_id|
  class_name, separator, id = flipper_id.rpartition(":")
  class_name.constantize.find_by_id(id)
}


Websocket connection to mosquitto broker fails

I am trying to setup a websocket client for a mosquitto broker.
The config for the broker is:
port 1883
protocol mqtt

listener 9001
protocol websockets

When using the no_tls_client.cpp example, everything works as expected. With the no_tls_ws_client.cpp example, it simply hangs with the following backtrace:
epoll_wait 0x00007f448a27d5ca
boost::asio::detail::epoll_reactor::run epoll_reactor.ipp:471
boost::asio::detail::scheduler::do_run_one scheduler.ipp:431
boost::asio::detail::scheduler::run scheduler.ipp:200
boost::asio::io_context::run io_context.ipp:63
main no_tls_ws_client.cpp:125
__libc_start_main 0x00007f448a1a5153
_start 0x0000561afb702bee

The broker does not report any incoming connection.
A similar client in Python, using the paho library works:
import paho.mqtt.client as mqtt
import ssl

def on_connect(client, userdata, flags, rc):
    print("Connected with result code "+str(rc))
    client.subscribe("$SYS/#")

def on_message(client, userdata, msg):
    print(msg.topic+" "+str(msg.payload))

client = mqtt.Client(client_id='test', clean_session=True, transport='websockets')
client.on_connect = on_connect
client.on_message = on_message

client.connect("localhost", 9001, 60)
client.loop_forever()

Any advice on fixing this issue?

debugging
Unfortunately, mqtt_cpp doesn't have logging functionality yet. So you need to use a debugger or insert debug print code.
I set up the mosquitto environment and got the same result.
It seems that websocket handshake is successfully finished at least on the client side.
Then the client send MQTT CONNECT packet.
You can check the following code:
https://github.com/redboltz/mqtt_cpp/blob/8f2fa503f11eb6b52b94b55727c7aecb2046b1fe/include/mqtt/endpoint.hpp#L8077-L8115
And successfully write to boost asio:
https://github.com/redboltz/mqtt_cpp/blob/8f2fa503f11eb6b52b94b55727c7aecb2046b1fe/include/mqtt/endpoint.hpp#L8525-L8533
So from the client side, start waiting MQTT CONNACK packet but doesn't received.
The receiving code is as follows:
https://github.com/redboltz/mqtt_cpp/blob/8f2fa503f11eb6b52b94b55727c7aecb2046b1fe/include/mqtt/endpoint.hpp#L3935 -L3945
This function is called but the lambda expression (receiving handler) is not called.
Other server
I tested mqttjs/mqtt-server instead of mosquitto.
https://github.com/mqttjs/mqtt-server
test_server.js
var mqttServer = require('mqtt-server');

var servers = mqttServer({
  mqtt: 'tcp://localhost:1883',
  mqtts: 'ssl://localhost:8883',
  mqttws: 'ws://localhost:1884',
  mqtwss: 'wss://localhost:8884'
}, {
  emitEvents: true // default
}, function(client){
  client.connack({
    returnCode: 0
  });
});

servers.listen(function(){
  console.log('listening!');
});

package.json
{
  "name": "mqtt-server-example",
  "version": "0.1.0",
  "description": "test server",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "mqtt-server": "0.1.0"
  }
}

Run command:
> npm install
> node test_server.js

It works as I expected.
So the results are

server
client
result

mosquitto
mqtt_cpp
ng

mqtt_cpp
mqtt_cpp
ok

mqttjs
mqtt_cpp
ok

I think that the next step is analyzing mosquitto behavior.
Does mosquitto receive CONNECT packet? And then send CONNACK packet?

is this issue still open? recently consider to use this with mosquitto for my new app

I'm not sure. I think that it depends on mosquitto. mqtt_cpp works well with mqtt_cpp server and MQTT.js server.
At least, mqtt_cpp doesn't receive CONNACK packet from mosquiito, at that time.

Finally, I found the solution. mosquitto websocket seems to require subprotocol mqtt.
See #735


winch: Implement Fuel-Based Interruption

Closes: https://github.com/bytecodealliance/wasmtime/issues/8090
This commit introduces the initial implementation of fuel-based interruption in Winch.
To maintain consistency with existing fuel semantics, this implementation closely follows the Wasmtime/Cranelift approach, with the following exception:

Local Fuel Cache: Given Winch's emphasis on compilation speed, this implementation does not optimize for minimizing loads and stores. As a result, checking and incrementing fuel currently requires explicit loads and stores. Future optimizations may be considered to improve this aspect.

This commit also includes a small refactoring in the visitor, which introduces more generic "visitor hook" which enable handling the invariants that need to happen before and after emitting machine code for each Wasm operator.

Thanks for the review @alexcrichton.

One thought I had reading over this was that this should probably update some documentation somewhere around enabling fuel that Winch is supported. I don't think that's quite right though since we don't exhaustively document Winch's support on all other Config options, so documenting this as a one-off doesn't feel right. That being said it led me to another thought though that there was no change here associated with "ok actually allow Winch to use fuel". This means that it looks like we were silently accepting fuel-enabled-Config even though Winch didn't support it.

I think it's reasonable to audit the Config options and be explicit in the documentation regarding those options that are not fully supported by Winch. I'll do that in a separate PR paired with the change to perform winch-specific configuration validation in set_tunables in Winch's compiler implementation.

@alexcrichton I've opened https://github.com/bytecodealliance/wasmtime/pull/9490 -- once https://github.com/bytecodealliance/wasmtime/pull/9490 lands, I'll rebase and land this change.


Moving pkg-config and header files to libglib output?

At https://github.com/conda-forge/r-gdtools-feedstock/pull/17 I had to add glib to requirements/host because cairo.pc has GLib libraries in its Requires.private listings.
cairo pulls in libglib so those libraries are in place, but only glib holds the pkg-config definitions for them which is why pkg-config --cflags cairo doesn't work unless one explicitly installs glib alongside cairo.
(Apart from r-gdtools there might be around 40 other recipes affected.)
We don't really have clear cut definitions on how to split packages on conda-forge (and no perfect tooling, i.e., only run_exports but not "devel" exports) and thus no libglib/libglib-devel split (with the latter explicitly for pkg-config and header files).
For other library packages we just ship the -devel part with the library itself, i.e., libglib here. Could we do the same here?

Similar issue over in https://github.com/conda-forge/r-rgtk2-feedstock/pull/6, adding glib to requirements/host fixed it there too.

Relevant changes can be seen in https://github.com/conda-forge/glib-feedstock/pull/74 I did ❌ that at the time as the discussions in https://github.com/conda-forge/cfep/pull/39 pointed to not including pkg-config files in the libXX package. I still think this makes sense long-term but only seems practicable when all the downstream dependencies also have a libXX-XX-devel split. Then the -devel packages can depend on each other. Currently, we don't have -devel packages for gtk2 or cairo. Thus I would be 👍 if someone opened a PR in the fashion of #74
cc @hmaarrfk

glad to see this getting revived. thanks for pulling the relevant information @xhochy

This is dangerous to have. If glib is not added as a dependency in host, then run_exports will not be applied. I think we should revert #101.

Or we can keep #101, but remove libglib.so output to glib and keep only libglib.so.<ver> in libglib.

In the case of r-cairo and friends, should the run_exports be enforced on things that actually only depend directly on cairo? The issue with pkg-config is that it is looking for indirect dependencies, too.

Or we can keep #101, but move libglib.so file to glib and keep only libglib.so.<ver> in libglib.

That sounds like a good idea!

Made a PR: https://github.com/conda-forge/glib-feedstock/pull/102


dijkstra algorithm

This PR does not seem relevant to this repo (maybe it's a mistake?), so I'm going ahead and closing it.


fixed WithAuthorization token expiration

Coverage decreased (-0.006%) to 86.895% when pulling 79983f8a93bce15e85350a008de14cce03c7adac on dissoupov into 6375b7547c62c8abbaee677dfe625b8b4a19d4f9 on main.


New install error

Startup code assumes previous install in multiple gateway conversion code.

Fixed in 7.3.1.


Single select doesn't restore selection correctly

If you have the single select option turned on in PBI, make a selection, switch pages, and go back, attribute slicer will restore the selection, then quickly clear it.  This does not occur with multi-selection.

not reproduce-able on the develop branch as of May 15.


feat: port Data.Finset.LocallyFinite

[ ] depends on: #1754

This PR/issue depends on:

leanprover-community/mathlib4#1754
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#1754
By Dependent Issues (🤖). Happy coding!

bors merge


Multiple shortcuts doesn't work

class GS.Lib.Shortcuts extends Backbone.Shortcuts

  shortcuts:
    'shift+/' : 'help'
    'n'       : 'quickCampaign'

  help: ->
    alert('help')
    false

  quickCampaign: ->
    alert('quick campaign')
    false

quickCampaign doesn't work here

just fixed it. Can you try it now?

fixed, thanks


Encountered an exception while running action 'action_weather_api'. Bot will continue, but the actions events are lost. Please check the logs of your action server for more information.

Rasa version:Rasa 1.10.1
Rasa SDK version (if used & relevant):
Rasa X version (if used & relevant):
Python version:3.6
Operating system (windows, osx, ...):Windows 10
Issue: I am getting error when my bot is suppose to give me reply from custom code .
Error (including full traceback):
Traceback (most recent call last):
  File "c:\users\goldy\anaconda3\envs\rasabot1\lib\site-packages\sanic\app.py", line 976, in handle_request
    response = await response
  File "c:\users\goldy\anaconda3\envs\rasabot1\lib\site-packages\rasa_sdk\endpoint.py", line 102, in webhook
    result = await executor.run(action_call)
  File "c:\users\goldy\anaconda3\envs\rasabot1\lib\site-packages\rasa_sdk\executor.py", line 387, in run
    events = action(dispatcher, tracker, domain)
  File "C:\Users\goldy\PycharmProjects\RasaBot\actions.py", line 24, in run
    city = tracker.latest_message('text')
TypeError: 'dict' object is not callable

Command or request that led to error:

**Content of python file (actions.py):
from typing import Any, Text, Dict, List

from rasa_sdk import Action, Tracker
from rasa_sdk.executor import CollectingDispatcher
from app import Weather

class ActionHelloWorld(Action):

    def name(self) -> Text:
        return "action_weather_api"

    def run(self, dispatcher: CollectingDispatcher,
            tracker: Tracker,
            domain: Dict[Text, Any]) -> List[Dict[Text, Any]]:
        city = tracker.latest_message('text')
        temp = int(Weather(city)['temp'])
        dispatcher.utter_template("utter_temp",tracker,temp = temp)

        return []

Content of domain file (domain.yml) (if relevant):
  session_expiration_time: 60
  carry_over_slots_to_new_session: true
intents:
- greet
- weather
- city
- goodbye
responses:
  utter_greet:
  - text: Hey! I am WeatherBot, How can I assist you?
  utter_city:
  - text: Tell me the city name, you want to know weather of?
  utter_temp:
  - text: Today's temperature is {temp} degree celsius
  utter_goodbye:
  - text: Bye
actions:
- utter_greet
- utter_city
- utter_goodbye
- utter_temp
- action_weather_api

Thanks for the issue, @akelad will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

Hi @goldy1987, this is more of a usage question about how to write custom actions, please ask those kinds of questions in our community forum.
I believe the issues is that it should be `tracker.latest_message.get('text')


New keys + remove frontend parsing

These keys are sent to an endpoint to get a PDF & guessed address. Right now the endpoint requires multiple sources of information (case number, county, state, etc), but since each PDF has its own "key" attribute, we need to:

create endpoints that return a PDF & guessed address with a key
an endpoint that returns a list of keys on the server
update the AddressWidget to call the endpoint with the key (e.g. remove parsing)

Implemented in this way:

firebase has a list of "firekeys" (sampleCounts).  The firekeys are not directly parseeable (hash codes from the actual keys)
added endpoints //address, //files, //pdffile64.  API will figure out correct key (state-county-year-case) based on firekey.

I am closing this issue as I think we have implemented what is needed.


Handle other IP formats from xenstore.

Example: "<IP_ADDRESS> fd09:24ef:3178::a19:11"
reported via https://twitter.com/t_grote/status/1262747002334408704

I can confirm that this fixes the issue with my Qubes installation.


fix: Fix response header issues

This PR resolves how response headers from certain APIs are not being displayed in the Headers tab.
Fixes #17279

Bug fix (non-breaking change which fixes an issue)

Cypress test
Checklist:

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

/ok-to-test sha=6f963ab

/ok-to-test

/ok-to-test sha=a915bf5

/ok-to-test sha=a915bf5

/ok-to-test sha=973ddfe

/ok-to-test sha=0a0dfad

/ok-to-test sha=1fb54d4

/ok-to-test sha=44337f3

/ok-to-test sha=ae59e54

/ok-to-test sha=12df663

/ok-to-test sha=d664edd


Ingestion Python - Work for formats other than PDF?

I have the Azure Fn webskill & all other requirements for https://github.com/Azure/cognitive-search-vector-pr/blob/main/demo-python/code/azure-search-vector-ingestion-python-sample.ipynb.
It works fine as long as the docs in the /data/documents sample folder are PDFs. If i put DOCX files in there, the notebook runs but never vectorizes or chunks the content in the DOCX. ??

hi @dkah39, this code sample is now removed, please use our new integrated vectorization feature that will allow multiple formats within the same folder.
https://github.com/Azure/cognitive-search-vector-pr/blob/main/demo-python/code/azure-search-integrated-vectorization-sample.ipynb


Doc :: Add alphabetical order convention in docs.md

Related to https://github.com/ToucanToco/vue-query-builder/pull/108

Codecov Report

Merging #109 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #109   +/-   ##
=======================================
  Coverage   84.98%   84.98%
=======================================
  Files          11       11
  Lines         293      293
  Branches       33       33
=======================================
  Hits          249      249
  Misses         38       38
  Partials        6        6

Continue to review full report at Codecov.

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


Update useIsFetching docs

isFetching: Boolean -> isFetching: Number

I'll accept a PR to update this or get around to it next time I'm in the Readme.


Issue building dpp[core] with vcpkg on windows 11

Package: dpp[core]:x86-windows -> 10.0.23
Host Environment

Host: x64-windows
Compiler: MSVC 19.35.32215.0
vcpkg-tool version: 2023-01-24-8a88d63f241d391772fbde69af9cab96c3c64c75
vcpkg-scripts version: 8daf70c56 2023-03-03 (19 hours ago)

To Reproduce
vcpkg install dpp
Failure logs
-- Downloading https://github.com/brainboxdotcc/DPP/archive/v10.0.23.tar.gz -> brainboxdotcc-DPP-v10-09666b3e.0.23.tar.gz...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
Downloading https://github.com/brainboxdotcc/DPP/archive/v10.0.23.tar.gz
error: Failed to download from mirror set
error: File does not have the expected hash:
url: https://github.com/brainboxdotcc/DPP/archive/v10.0.23.tar.gz
File: C:\Program Files (x86)\vcpkg\downloads\brainboxdotcc-DPP-v10-09666b3e.0.23.tar.gz.17264.part
Expected hash: 09666b3e05c379aa2da794aed0a59ff5f6b2dae06c6e700b2bd45486aa20003b4e6d28bd9436d1e28bf7dd1b5ca80d55e5a107fe9589587b88719caa2cecb243
Actual hash: 18bbb7d2c1385d179cac9ded31d1b11e8d24f172e7ffe2ba79071203e1e2f277657e21d660b18ee4b849bc093d350f4bc5401702400084b56c3ebd6f03ce28df
[DEBUG] D:\a\_work\1\s\src\vcpkg\base\downloads.cpp(956):
[DEBUG] Time in subprocesses: 0 us
[DEBUG] Time in parsing JSON: 2 us
[DEBUG] Time in JSON reader: 0 us
[DEBUG] Time in filesystem: 101 us
[DEBUG] Time in loading ports: 0 us
[DEBUG] Exiting after 1.863 s (1862669 us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):

      Failed to download file with error: 1
      If you are using a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
         set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
         The value set by your proxy might be wrong, or have same `https://` prefix issue.

      3. Your proxy's remote server is out of service.

      If you've tried directly download the link, and believe this is not a temporary
      download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
      to report this upstream download server failure.

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
  scripts/cmake/vcpkg_from_github.cmake:106 (vcpkg_download_distfile)
  ports/dpp/portfile.cmake:1 (vcpkg_from_github)
  scripts/ports.cmake:147 (include)

Additional context
I have tried going into my proxy settings and changing things up but im not sure exactly what and how

With and without proxy the error happen, with and without proxy the file can be downloaded manually the file by going on the link.


UniversalString with uper encoder has bugs in 0.9.28 - last characters are lost by encoder.

I have the following test program:
const char *pTest = "This is a text string.";
IA5String_t ia5;
memset(&ia5, 0, sizeof(ia5));
OCTET_STRING_fromBuf(&ia5, pTest, -1);
char buffer[512];
asn_enc_rval_t enc = uper_encode_to_buffer(&asn_DEF_UniversalString, &ia5, buffer, sizeof(buffer));
printf("len=%d bits,  %d bytes: ", (int)enc.encoded, (int)(enc.encoded+7)/8);
for (int d=0; d<(enc.encoded+7)/8; d++)
printf(" %02x", buffer[d] & 0xff);
printf("\n");
IA5String_t *dec = 0;
asn_dec_rval_t rval = uper_decode(0, &asn_DEF_UniversalString, (void **)&dec, buffer, (enc.encoded+7)/8, 0, 0);
printf("consumed: %d\n", (int)rval.consumed);
printf("back: %s\n", dec->buf);
This prints:
len=168 bits,  21 bytes:  05 54 68 69 73 20 69 73 20 61 20 74 65 78 74 20 73 74 72 69 6e
consumed: 168
back: This is a text strin
The last two characters are missing.

This code happens to violate the implicit UniversalString constraint, in which the length of it should be modulo 4.
See the commit https://github.com/vlm/asn1c/commit/4ef01a249dc92c670528016768947c88d5eb382e which outright prohibits encoding such strings.
P.S. Please use UniversalString_t instead of IA5String_t.

Thank you for the very quick followup and advice!


progress bars are broken for installations

We need to test and confirm.

I am trying to verify this issue, my last run from main:
./kubefirst local --gitops-branch main --skip-metaphor
rm: cannot remove './kubefirst': No such file or directory
2022/12/15 16:05:58 kubefirst started
Logging at: /app/logs/log_1671120358.log
Init actions: 4 expected tasks ...

Download dependencies         ... 33.3% [#########...................] [1 in 500.543ms]
Download dependencies         ... done! [3 in 6.892s]
Create SSH keys               ... done! [1 in 6.902s]
Clone and Detokenize (GitOps) ... done! [1 in 7.582s]
- initialization step is done!
Process Parameters            ... done! [1 in 7.833s]
Init actions: 7 expected tasks ...

Send Telemetry                ... 50.0% [##############..............] [1 in 45.368259s]
Setup gitops on github        ...  0.0% [............................] [0 in 45.368481s]
- Creating github resources with terraform
- Created gitops Repo in github.com/-------
- pushing local detokenized gitops content to new remote github.com/kxdroid
Setup gitops on github        ... done! [3 in 1m6.343s]
- create initial argocd repository
- helm repo add argo https://argoproj.github.io/argo-helm and helm repo update
- helm install argo and wait
- ArgoCD is running, continuing
- Setting argocd username and password credentials
- argocd username and password credentials set successfully
- Getting an argocd auth token
- argocd admin auth token set
- applying the registry application to argocd
- waiting for Vault to be ready...
- configuring vault with terraform
- vault terraform executed successfully
- Vault secret created
- applying users terraform
- executed users terraform successfully
- Welcome to local kubefirst experience
Setup base cluster            ... done! [2 in 4m24.771s]
Install apps to cluster       ... done! [4 in 4m24.771s]
- To use your cluster port-forward - argocd
- If not automatically injected, your kubeconfig is at:
- k3d kubeconfig get kubefirst
- Expose Argo-CD
- kubectl -n argocd port-forward svc/argocd-server 8080:80
- Argo User: admin
- Argo Password: --------
- Deploying metaphor applications
- waiting "atlantis plan" finish to proceed...
Send Telemetry                ... done! [2 in 4m40.707s]

All bar started were it seems to be marked as done, but there some weird total of bars:

Init actions: 4 expected tasks ...
Init actions: 7 expected tasks ...

To total doesn't match the total of bars.

Details at the PR on how the bars are updated.

Bars working as expected for local.


[Discussion]: Create new mailing list for SATRE working group

Summary
Create a JISC hosted mailing list for SATRE discusions
Source
No response
Detail
We are creating a UK TRE working group for SATRE: https://github.com/uk-tre/community-management/issues/119
As part of this we should create a new public JISC mailing list. This will provide an additional place for discussions alongside GitHub.
Possible names:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
List permissions: Restricted discussion list (public archives, restricted subscription, visible on JiscMail's A-Z catalogue)
For comparison the UK TRE community list is: Public discussion list (public archives, open subscription, visible on JiscMail's A-Z catalogue)
Application form: https://www.jiscmail.ac.uk/groups/startagroup/grouprequestform.html
Intended Output
Create a mailing list
Who can help
No response

Good idea. My preference would be for uk-tre-satre@jisc as that gives more context.
Do we need to decide who the primary list owner is? Can it be a generic mailing list (i.e. HIC)?

I've requested uk-tre-satre@, with myself and Chris Cole as list owners. Once the list is created we can add more list owners or moderators.


PULLREQ_EDITMSG sometimes shows incorrect head

% hub --version
git version 2.10.2
hub version 2.2.9

Sometimes the PULLREQ_EDITMSG shows an incorrect head branch in the top comment line. I'm not sure if this is because the PULLREQ_EDITMSG was created incorrectly, or if the PULLREQ_EDITMSG isn't being cleaned after a previous PR is opened and it is just being re-used, but occasionally I see a different head branch from the one I specified (or a different one from the currently-checked-out branch if I'm not specifying a head branch). However, I can still proceed to open the PR, and it gets opened with the correct head branch. So this is more of a cosmetic issue that causes confusion, and not a matter of hub incorrectly opening the PR.
I'm sorry that I don't have more detailed information on how to reproduce, but I haven't yet noticed a pattern to what causes this. I'm hoping the fact that there are likely only a few places where PULLREQ_EDITMSG is handled, and the fact that hub still opens the PR using the correct head branch, are together enough to help narrow it down.

Another side-effect of this is that the pull request title that is pre-filled in the PULLREQ_EDITMSG is the one from the incorrect head branch. This actually happened in this PR and I didn't notice it until now.

Thanks for reporting. Hub tries to re-use the old PULLREQ_EDITMSG file when such file exists, and this is the most likely cause for the stale head to be displayed (or stale title, for that matter). The PULLREQ_EDITMSG file, however, should always be deleted after a successful pull request. Hub only keeps it if the response from the server was something unexpected, so you don't lose everything that you've written in the file.
Have any pull requests failed for you prior to opening new ones? Do you see .git/PULLREQ_EDITMSG kept even after a successful PR opened?

I did notice a couple of PULLREQ_EDITMSG files, both in .git/ and in the worktree dirs under .git/worktrees/. I think however, that at least some of these exist because I was seeing bad info in the PULLREQ_EDITMSG and was pre-emptively killing the tmux pane in which my editor was open to avoid opening a PR with the bad info in it. I've removed all of these PULLREQ_EDITMSG files and will continue to observe whether or not this problem re-occurs.
One potential explanation could be that hub was looking for .git/PULLREQ_EDITMSG when in a git worktree (i.e. git worktree add ......), rather than in the worktree dir. Before I opened this issue I noticed that there was a stale .git/PULLREQ_EDITMSG, though I was too dumb to look at the contents before I deleted it. I almost exclusively work in git worktrees, so it is not out of the question for there to have been a stale PULLREQ_EDITMSG there for months without me noticing. I have a feeling that the cause of me forcibly killing vim to avoid opening a PR using a bad PULLREQ_EDITMSG may have been the fact that hub was still looking in .git/ instead of .git/worktrees/worktree_name. However, I just tried to reproduce this by creating a dummy .git/PULLREQ_EDITMSG and then attempted to open a PR from a worktree and hub correctly created a new PULLREQ_EDITMSG in the worktree dir and ignored .git/PULLREQ_EDITMSG. So, the stale PULLREQ_EDITMSG files in some of my old worktrees (which I should really clean out sometime :smile:) may date from a time when there was a bug in an older release of hub. https://github.com/github/hub/issues/877 and https://github.com/github/hub/issues/928 are a couple that dealt with similar issues.
The issue that caused me to open this bug report occurred in one of the rare times where I opened a PR from the "main" git clone (i.e. not from a worktree), so the explanation of hub re-using an existing PULLREQ_EDITMSG holds, since I did find one there. However, side note, it might be a good idea for hub to treat PULLREQ_EDITMSG files older than N days as stale and disregard them. If this age were tunable, that'd be even better!
Like I said, I'll continue to keep an eye out. This may indeed be a relic of an older, since-fixed issue, so you can feel free to close this if you like and we can re-open if I find specific circumstances where a PULLREQ_EDITMSG is left behind after a PR is successfully opened.

You might be on to something re: worktrees. I have no idea how this feature plays together with switching between worktrees, because I'm not a heavy user of those. 🤔

Yeah, but I couldn't even reproduce it in hub 2.2.9, so it's probably not worth chasing that thread right now.
It would definitely be nice to be able to disregard PULLREQ_EDITMSG files older than a given age, though.

Oh, one other thing I noticed, is that when a PULLREQ_EDITMSG is reused, even if you don't save the file, hub seems to continue with opening the PR. Normally, if you exit your editor without saving the file, hub will abort and not try to open a PR, but it seems like it is only doing a check for the existence of that file and deciding that if it exists, that a PR should be opened.
To fix this, when a PULLREQ_EDITMSG is being re-used, hub could os.Stat() the file before and after, and only open the PR if the modified time has changed. That would keep it from opening a PR if someone exits their editor without saving the file.
Should I open separate issues for this and the above request?

even if you don't save the file, hub seems to continue with opening the PR. Normally, if you exit your editor without saving the file, hub will abort and not try to open a PR

You noticed this correctly, but what if a person wants to post the original text that they wrote without any modifications? Maybe the first time around it failed because of a network error.

My solution of performing an os.Stat() on the file before and after (in cases where a PULLREQ_EDITMSG is being re-used) would catch this. It would allow one to exit the editor without saving, and abort opening the PR.
If one wishes to re-attempt the previously-failed PR but not change the contents of the PULLREQ_EDITMSG, they can simply save before exiting, which will change the mtime of the file. If the mtime from the os.Stat() taken after one exits the editor differs from that of the file before the editor was launched, then we know that the file was saved. Coaching users on observing this new behavior would be easy to do, a simple message can be printed to the screen saying something like "Aborted opening pull request due to unmodified buffer. If you wish to submit the pull request, save the buffer before exiting."
This, to me, would make opening a PR that previously failed act more like opening a PR for the first time, in that one would have the option of aborting by not saving the PULLREQ_EDITMSG before closing their editor. Right now, if the PR fails the first time, there is no way to back out if you run another hub pull-request and an existing PULLREQ_EDITMSG is used.

If one wishes to re-attempt the previously-failed PR but not change the contents of the PULLREQ_EDITMSG, they can simply save before exiting, which will change the mtime of the file.

That's a good idea. Want to try to code it up?

if the PR fails the first time, there is no way to back out if you run another hub pull-request and an existing PULLREQ_EDITMSG is used.

Well, if you have an editor that can exit with a nonzero status, such as :cq in vim, you can abort opening the PR. But people with graphical text editors likely don't have access to such a feature.

@mislav sure, I can give it a try. My go-fu is nowhere near as good as my Python-fu though, so anything I submit should be double and triple-scrutinized. I'll try to hack away at it this weekend.

Feel free to submit a mess and I can clean it up. Here is where I think the logic could go; there should be a check that mtime got updated after openEditor() call, otherwise assume that the person didn't save the file.
Some tests might get broken with the new logic, because they simulate a fake editor being opened, but not all of them bump the mtime. If you get lost in there, I can help out.

Cool, thanks!

I'm having the same problem, template having the wrong .Base, no matter what I pass with -b.

@mislav I did not get around to this over the weekend, and it doesn't look like I'd even have a chance to start until after the holidays. So if you have the time and want to hack at it, go for it.


add set_ingress_health_check field

Change description
add set_ingress_health_check field
Type of change

[ ] Bug fix (fixes an issue)
[x] New feature (adds functionality)

Checklists
Development

[ ] Pull requests may not be submitted to the master branch (use develop instead) - or they will be closed.
[ ] Lint rules pass locally
[ ] Application changes have been tested thoroughly
[ ] Automated tests covering modified code pass

Security

[ ] Security impact of change has been considered
[ ] Code follows company security practices and guidelines

Code review

[ ] Pull request has a descriptive title and context useful to a reviewer.
[ ] "Ready for review" label attached and reviewers assigned
[ ] Changes have been reviewed by at least one other contributor
[ ] Pull request linked to task tracker where applicable

Task linked: DUPLO-10734 [TF] Add field for ingress health checks


Challenge Id3

confirmed:ID3
DocumentType:verified
Nationality:verified
DeviceDetails:verified
Experience:verified
Screenshot:verified

confirmed:ID3
DocumentType:verified
Nationality:verified
DeviceDetails:verified
Experience:verified
Screenshot:verified


The system library alsa required by crate alsa-sys was not found.

Compiling alsa-sys v0.3.1
error: failed to run custom build command for alsa-sys v0.3.1
Caused by:
process didn't exit successfully: /tmp/cargo-installYXqqyX/release/build/alsa-sys-ed61088eca073151/build-script-build (exit status: 101)
--- stdout
cargo:rerun-if-env-changed=ALSA_NO_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG
cargo:rerun-if-env-changed=ALSA_STATIC
cargo:rerun-if-env-changed=ALSA_DYNAMIC
cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
--- stderr
thread 'main' panicked at /home/shrx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alsa-sys-0.3.1/build.rs:13:18:
pkg-config exited with status code 1

PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags alsa

The system library alsa required by crate alsa-sys was not found.
The file alsa.pc needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
The PKG_CONFIG_PATH environment variable is not set.
HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing alsa.pc.
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile ttysvr v0.3.0, intermediate artifacts can be found at /tmp/cargo-installYXqqyX.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path.

Ah, apologies, I should add some documentation around this. This uses Bevy, and so if you are building with cargo Bevy requires certain dependencies on Linux, which is described for each distro here:
https://github.com/bevyengine/bevy/blob/main/docs/linux_dependencies.md
For example, for Ubuntu this should fix it:
sudo apt-get install g++ pkg-config libx11-dev libasound2-dev libudev-dev libxkbcommon-x11-0

Thanks for the instructions!

Compilation was now successful, feel free to close this issue.

Closing now that there is now a note in the README linking to bevy's linux dependencies.


cacert: 3.77 -> 3.80

Description of changes
Contains #178809, but targeted against staging, because cacert
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Uh, well now we have two different commits doing the same nss update (on staging, later master), but it's certainly not a big deal.

Uh, well now we have two different commits doing the same nss update (on staging, later master), but it's certainly not a big deal.

Would not updating in this PR nss_latest have been the preferred option? If so, I'll try and remember to do that, next time.

Maybe, or we could've used the squash-merge button, as at merge time it was already included in staging.


Network churn Load test - Add network policy enforcement latency measurement

Integrate network policy enforcement latency measurement

@microsoft-github-policy-service agree [company="Microsoft"]

@microsoft-github-policy-service agree company="Microsoft"


Changing Provider in New Specification Dialog Has Incorrect Highlight

When a template is selected in the Create New Specification dialog, and provider is changed, the selected template is reset (As expected) but the highlight in the list is incorrect. This is a fairly minor issue as the workflow is correct but creates an incorrect visual cue for the end-user.
Steps to Reproduce

Open the dialog
Select a Vega-Lite template, e.g. Colored Scatterplot
Change provider to Vega

Expected Outcome
The Vega templates are shown, with the first template selected ([empty]).
Actual Outcome
The [empty] template is selected, but the list item is showing Connected Scatterplot, e.g.:

Resolved in build 137


versions: Update docker to 19.03

Move our supported docker version to 18.09.
This is the latest stable and the only supported for Fedora 29,
which we are going to use soon for our CI as Fedora 28 is EOL
at the end of the month. In addition docker 18.09 is the
one that our documentation says that we support.
Fixes: #1110.
Signed-off-by: Salvador Fuentes<EMAIL_ADDRESS>

/test

/test

/test

/test

/test

/retest

/test

update on this: cri-containerd test  break the CI as it does pkill containerd but continerd is also used by docker. A new fix is cri-containerd but a new release of containerd with those changes are needed.
The containerd needs to vendor a version with https://github.com/containerd/cri/commit/199ee362e8f6ffd16fcf0eed4c012f40c5fd2b4c
@Random-Liu @chavafg

@chavafg @jcvenegas - are we stuck on this one? Maybe mark as WIP or DNM (to avoid reviewers visiting it in the meantime...)

yeah, sorry, adding labels.
we need to wait for containerd/containerd project to include the cri commit that @jcvenegas mentioned above in a new release.

@chavafg any updates on this PR? Thx.  Maybe we should use a newer Docker version.

yeah, I think we can use 19.03, will take a look next week.

/test

blocked on #2314.

As this PR is marked as do-not-merge, we're assuming it won't make for the final 1.13.0 release, thus we're closing it.
In case you feel this has been wrongly closed, please, feel free to re-open it.


Terminal does not output any logs for Android

After I upgrade my tns to 3.4.3, the terminal does not output any console log for Android. It is ok for iOS.
Then I tried to downgrade the nativescript by running: npm uninstall -g nativescript and ran: npm install -g<EMAIL_ADDRESS>again but the log still does not shows.
More info:
The output of running tns --version shows: 3.4.2
Detail of my package.json file:
tns-android: 3.4.1
tns-ios: 3.4.1
Dependencies:
angular/animations: ~5.2.0,
angular/common: ~5.2.0,
angular/compiler: ~5.2.0,
angular/core: ~5.2.0,
angular/forms: ~5.2.0,
angular/http: ~5.2.0,
angular/platform-browser: ~5.2.0,
angular/platform-browser-dynamic: ~5.2.0,
angular/router: ~5.2.0,
email-validator: "^1.1.1",
nativescript-angular: "~5.2.0",
nativescript-iqkeyboardmanager: "^1.2.0",
nativescript-loading-indicator: "^2.4.0",
nativescript-localstorage: "^1.1.5",
nativescript-ngx-fonticon: "^4.0.0",
nativescript-socket.io: "^0.9.0",
nativescript-theme-core: "~1.0.4",
nativescript-toast: "^1.4.6",
nativescript-ui-listview: "^3.5.1",
nativescript-ui-sidedrawer: "^3.5.1",
reflect-metadata: "~0.1.8",
rxjs: "~5.5.2",
tns-core-modules: "^3.4.1",
zone.js: "~0.8.2"
Dev Dependencies:
"babel-traverse": "6.26.0",
"babel-types": "6.26.0",
"babylon": "6.18.0",
"lazy": "1.0.11",
"nativescript-dev-typescript": "~0.6.0",
"typescript": "~2.6.2"
Can you please assist how to get the log back on the terminal? Both real device and genymotion shows no console log

Reverted back to 3.4.2, and did a npm cache clean fixed the issue.
However, the question is still: why upgrade to 3.4.3, the terminal log does not appear

Hi @ngunhaSO,
I tested your case on a sample project while using latest NativeScript CLI and Android runtime, however, was unable to recreate the problem.
I noticed that you are using an old runtime I would suggest upgrading the NativeScirpt CLI to version(3.4.3) as well as the Android runtime(3.4.2) as follows:
tns platform remove android
tns platform add android

Is there any specific tns-core-modules needed? Previously i remember the version was like<EMAIL_ADDRESS>then i changed to 3.4.1 which is what returned by running: npm install tns-core-modules@latest --save

You should use the latest official version of tns-core-module, which now is 3.2.1. You could add it as follows:

tns plugin remove tns-core-modules
tns plugin add tns-core-modules


Protect IE8, disallow es7 class properties

Hi friends,
This PR protects ie8 support by disallowing es7 class properties (which are still experimental). These in particular break ie8 because babel must use Object.defineProperty in order to support them. They can be easily handled by the reformatting in this PR. Let me know if there is anything else I can do to match the standard of redux-form with regards to this PR!

Also it seems like I need to do some merging...

Why is this an issue? The actual lib that you get from NPM is transpiled down to ES5.

Some context can be found here: https://github.com/rackt/react-redux/issues/133. ES5 isn't 100% supported even with polyfills. So yes it gets transpiled to ES5, but this particular syntax sugar is a breaker. Here is my related PR on react-router: https://github.com/rackt/react-router/pull/2540

Hmm... Seems like the problem is really with Babel, not the libraries that use it, but it takes less force to accelerate less mass, so I guess I'm fine with this, once you merge in the changes.

Sorry for not merging this pull request, but I had already changed some of these lines when I got around to this PR, so I've just implemented your changes verbatim in my modified repo. Thanks for this!

Thanks! No worries. I'm just sorry to be the bringer of ie8 drama. Rock on!

Yeah. My favorite thing about uglify is the --screw-ie8 parameter. :smiley: