Authentication failed<EMAIL_ADDRESS>/ Smart@2012

When trying to send email from<EMAIL_ADDRESS>account I'm getting the following error:
[DEBUG] com.sun.mail.smtp - useEhlo true, useAuth true
[DEBUG] com.sun.mail.smtp - trying to connect to host "smtp.gmail.com", port 587, isSSL false
[DEBUG] com.sun.mail.smtp - connected to host "smtp.gmail.com", port: 587
[DEBUG] com.sun.mail.smtp - Found extension "SIZE", arg "35882577"
[DEBUG] com.sun.mail.smtp - Found extension "8BITMIME", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "STARTTLS", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "ENHANCEDSTATUSCODES", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "PIPELINING", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "CHUNKING", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "SMTPUTF8", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "SIZE", arg "35882577"
[DEBUG] com.sun.mail.smtp - Found extension "8BITMIME", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "AUTH", arg "LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH"
[DEBUG] com.sun.mail.smtp - Found extension "ENHANCEDSTATUSCODES", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "PIPELINING", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "CHUNKING", arg ""
[DEBUG] com.sun.mail.smtp - Found extension "SMTPUTF8", arg ""
[DEBUG] com.sun.mail.smtp - Attempt to authenticate using mechanisms: LOGIN PLAIN DIGEST-MD5 NTLM
[WARN] eu.cloudopting.service.MailService - E-mail could not be sent to user<EMAIL_ADDRESS>exception is: Authentication failed; nested exception is javax.mail.AuthenticationFailedException: 534-5.7.14 <https://accounts.google.com/ContinueSignIn?sarp=1&scc=1&plt=AKgnsbsO0
534-5.7.14 01TCt50Tz7Wnq-iBTpYA7RbKwa79Be9acBAAvMZEOQuaX7yR4G3vbScYuBiuWgfxw8w3H0
534-5.7.14 wmxxRSnVH2fjeIQd3v0B1C6alsYOo7oVzCdsWBO2fGlg4ATF0Z0Yxx5On_jwdJ52e3SsiH
534-5.7.14 bSPEvpsBfuc3OZbEv649GLldZI1d7Tz_I-nWJf2bllBo6oj2OzcgFIEXaNmEL-rPoJXz_B
534-5.7.14 eQ8HpR_qZRv8SKYaiRM2wzgiHcns> Please log in via your web browser and
534-5.7.14 then try again.
534-5.7.14  Learn more at
534 5.7.14  https://support.google.com/mail/answer/78754 d66sm18597558wma.21 - gsmtp

Duplicated: https://github.com/CloudOpting/cloudopting-manager/issues/79


Make Servers truly Thread Safe

-Rendering server now uses a split RID allocate/initialize internally, this allows generating RIDs immediately but initialization to happen later on the proper thread (as rendering APIs generally requiere to call on the right thread).
-RenderingServerWrapMT is no more, multithreading is done in RenderingServerDefault.
-Some functions like texture or mesh creation, when renderer supports it, can register and return immediately (so no waiting for server API to flush, and saving staging and command buffer memory).
-3D physics server changed to be made multithread friendly.
-Added PhysicsServer3DWrapMT to use 3D physics server from multiple threads.
-Disablet Bullet (too much effort to make multithread friendly, this needs to be fixed eventually).
Once merged, servers will be perfectly multithread-safe, so I can enable multthreaded loading by default, for editor and engine.

When enabling multithread rendering and running project - https://github.com/qarmin/RegressionTestProject/archive/4.0.zip
then I got this errors and address sanitizer log:
ERROR: Method/function failed.
   at: free (./core/templates/rid_owner.h:236)
=================================================================
==297548==ERROR: AddressSanitizer: heap-use-after-free on address 0x6160006d7360 at pc 0x000011245b1c bp 0x7f0d1b4c5660 sp 0x7f0d1b4c5650
READ of size 8 at 0x6160006d7360 thread T11
ERROR: Invalid ID.
   at: free (servers/physics_3d/physics_server_3d_sw.cpp:1319)
ERROR: Invalid ID.
   at: free (servers/physics_3d/physics_server_3d_sw.cpp:1319)
ERROR: Invalid ID.
   at: free (servers/physics_3d/physics_server_3d_sw.cpp:1319)
ERROR: Invalid ID.
   at: free (servers/physics_3d/physics_server_3d_sw.cpp:1319)
ERROR: Invalid ID.
   at: free (servers/physics_3d/physics_server_3d_sw.cpp:1319)
    #0 0x11245b1b in RendererSceneCull::instance_set_base(RID, RID) servers/rendering/renderer_scene_cull.cpp:504
    #1 0x10535b97 in CommandQueueMT::Command2<RendererScene, void (RendererScene::*)(RID, RID), RID, RID>::call() core/templates/command_queue_mt.h:320
    #2 0xfce423c in CommandQueueMT::flush_one(bool) core/templates/command_queue_mt.h:461
    #3 0xfce4c69 in CommandQueueMT::wait_and_flush_one() core/templates/command_queue_mt.h:498
    #4 0x102832a8 in RenderingServerDefault::_thread_loop() servers/rendering/rendering_server_default.cpp:362
    #5 0x102829fb in RenderingServerDefault::_thread_callback(void*) servers/rendering/rendering_server_default.cpp:348
    #6 0x11ce993d in Thread::callback(Thread*, Thread::Settings const&, void (*)(void*), void*) core/os/thread.cpp:66
    #7 0x11cecdcd in void std::__invoke_impl<void, void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*>(std::__invoke_other, void (*&&)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*&&, Thread::Settings&&, void (*&&)(void*), void*&&) /usr/include/c++/10/bits/invoke.h:60
    #8 0x11cec69b in std::__invoke_result<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*>::type std::__invoke<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*>(void (*&&)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*&&, Thread::Settings&&, void (*&&)(void*), void*&&) /usr/include/c++/10/bits/invoke.h:95
    #9 0x11cec203 in void std::thread::_Invoker<std::tuple<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*> >::_M_invoke<0ul, 1ul, 2ul, 3ul, 4ul>(std::_Index_tuple<0ul, 1ul, 2ul, 3ul, 4ul>) /usr/include/c++/10/thread:264
    #10 0x11cebe9a in std::thread::_Invoker<std::tuple<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*> >::operator()() /usr/include/c++/10/thread:271
    #11 0x11cebe52 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*> > >::_M_run() /usr/include/c++/10/thread:215
    #12 0x14378e63 in execute_native_thread_routine (/mnt/Miecz/mojgodot/bin/godot.linuxbsd.tools.64s+0x14378e63)
    #13 0x7f0d3ebbe608 in start_thread /build/glibc-eX1tMB/glibc-2.31/nptl/pthread_create.c:477
    #14 0x7f0d3e021292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)

0x6160006d7360 is located 480 bytes inside of 568-byte region [0x6160006d7180,0x6160006d73b8)
freed by thread T0 here:
    #0 0x7f0d3ef8a1b7 in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.6+0xb01b7)
    #1 0x11cd83d8 in Memory::free_static(void*, bool) core/os/memory.cpp:169
    #2 0x113257d0 in void memdelete<RendererSceneCull::Instance>(RendererSceneCull::Instance*) core/os/memory.h:118
    #3 0x112aa5ac in RendererSceneCull::free(RID) servers/rendering/renderer_scene_cull.cpp:3491
    #4 0x10277227 in RenderingServerDefault::free(RID) servers/rendering/rendering_server_default.cpp:77
    #5 0xd858799 in VisualInstance3D::~VisualInstance3D() scene/3d/visual_instance_3d.cpp:142
    #6 0xd321481 in Light3D::~Light3D() scene/3d/light_3d.cpp:359
    #7 0xd347180 in SpotLight3D::~SpotLight3D() scene/3d/light_3d.h:212
    #8 0x2bb66b9 in void memdelete<Node>(Node*) core/os/memory.h:115
    #9 0xbc7694a in Node::_notification(int) scene/main/node.cpp:169
    #10 0x2b730ef in Node::_notificationv(int, bool) scene/main/node.h:45
    #11 0x3d008ce in Node3D::_notificationv(int, bool) scene/3d/node_3d.h:52
    #12 0x12dd2bba in Object::notification(int, bool) core/object/object.cpp:793
    #13 0x12dc55f3 in Object::_predelete() core/object/object.cpp:354
    #14 0x12dfafc0 in predelete_handler(Object*) core/object/object.cpp:1824
    #15 0x1f2f85e in void memdelete<Object>(Object*) core/os/memory.h:111
    #16 0xbd74ad5 in SceneTree::_flush_delete_queue() scene/main/scene_tree.cpp:985
    #17 0xbd6376c in SceneTree::process(float) scene/main/scene_tree.cpp:453
    #18 0x1f252b4 in Main::iteration() main/main.cpp:2480
    #19 0x1dd55ea in OS_LinuxBSD::run() platform/linuxbsd/os_linuxbsd.cpp:261
    #20 0x1dc8520 in main platform/linuxbsd/godot_linuxbsd.cpp:58
    #21 0x7f0d3df260b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)

previously allocated by thread T11 here:
    #0 0x7f0d3ef8a517 in malloc (/lib/x86_64-linux-gnu/libasan.so.6+0xb0517)
    #1 0x11cd74cb in Memory::alloc_static(unsigned long, bool) core/os/memory.cpp:76
    #2 0x11cd73ca in operator new(unsigned long, char const*) core/os/memory.cpp:41
    #3 0x1123e7da in RendererSceneCull::instance_initialize(RID) servers/rendering/renderer_scene_cull.cpp:377
    #4 0x1053a1f4 in CommandQueueMT::Command1<RendererScene, void (RendererScene::*)(RID), RID>::call() core/templates/command_queue_mt.h:320
    #5 0xfce423c in CommandQueueMT::flush_one(bool) core/templates/command_queue_mt.h:461
    #6 0xfce4c69 in CommandQueueMT::wait_and_flush_one() core/templates/command_queue_mt.h:498
    #7 0x102832a8 in RenderingServerDefault::_thread_loop() servers/rendering/rendering_server_default.cpp:362
    #8 0x102829fb in RenderingServerDefault::_thread_callback(void*) servers/rendering/rendering_server_default.cpp:348
    #9 0x11ce993d in Thread::callback(Thread*, Thread::Settings const&, void (*)(void*), void*) core/os/thread.cpp:66
    #10 0x11cecdcd in void std::__invoke_impl<void, void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*>(std::__invoke_other, void (*&&)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*&&, Thread::Settings&&, void (*&&)(void*), void*&&) /usr/include/c++/10/bits/invoke.h:60
    #11 0x11cec69b in std::__invoke_result<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*>::type std::__invoke<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*>(void (*&&)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*&&, Thread::Settings&&, void (*&&)(void*), void*&&) /usr/include/c++/10/bits/invoke.h:95
    #12 0x11cec203 in void std::thread::_Invoker<std::tuple<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*> >::_M_invoke<0ul, 1ul, 2ul, 3ul, 4ul>(std::_Index_tuple<0ul, 1ul, 2ul, 3ul, 4ul>) /usr/include/c++/10/thread:264
    #13 0x11cebe9a in std::thread::_Invoker<std::tuple<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*> >::operator()() /usr/include/c++/10/thread:271
    #14 0x11cebe52 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (*)(Thread*, Thread::Settings const&, void (*)(void*), void*), Thread*, Thread::Settings, void (*)(void*), void*> > >::_M_run() /usr/include/c++/10/thread:215
    #15 0x14378e63 in execute_native_thread_routine (/mnt/Miecz/mojgodot/bin/godot.linuxbsd.tools.64s+0x14378e63)

Thread T11 created by T0 here:
    #0 0x7f0d3ef31a95 in __interceptor_pthread_create (/lib/x86_64-linux-gnu/libasan.so.6+0x57a95)
    #1 0x14379128 in std::thread::_M_start_thread(std::unique_ptr<std::thread::_State, std::default_delete<std::thread::_State> >, void (*)()) (/mnt/Miecz/mojgodot/bin/godot.linuxbsd.tools.64s+0x14379128)
    #2 0x11ce9dec in Thread::start(void (*)(void*), void*, Thread::Settings const&) core/os/thread.cpp:83
    #3 0x1027ffd2 in RenderingServerDefault::init() servers/rendering/rendering_server_default.cpp:237
    #4 0x1f030d5 in Main::setup2(unsigned long) main/main.cpp:1574
    #5 0x1efcc90 in Main::setup(char const*, int, char**, bool) main/main.cpp:1406
    #6 0x1dc8425 in main platform/linuxbsd/godot_linuxbsd.cpp:51
    #7 0x7f0d3df260b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)

SUMMARY: AddressSanitizer: heap-use-after-free servers/rendering/renderer_scene_cull.cpp:504 in RendererSceneCull::instance_set_base(RID, RID)

With default single threaded mode, it crashes in different place(both crashes doesn't occur in master Godot branch):
==302779==ERROR: AddressSanitizer: heap-use-after-free on address 0x61500014f090 at pc 0x00000fc7e9a3 bp 0x7ffeec4a6030 sp 0x7ffeec4a6020
READ of size 8 at 0x61500014f090 thread T0
    #0 0xfc7e9a2 in PhysicsServer3DSW::cone_twist_joint_set_param(RID, PhysicsServer3D::ConeTwistJointParam, float) servers/physics_3d/physics_server_3d_sw.cpp:1177
    #1 0xfd4eaa8 in PhysicsServer3DWrapMT::cone_twist_joint_set_param(RID, PhysicsServer3D::ConeTwistJointParam, float) servers/physics_3d/physics_server_3d_wrap_mt.h:369
    #2 0xd5b8c16 in ConeTwistJoint3D::_configure_joint(RID, PhysicsBody3D*, PhysicsBody3D*) scene/3d/physics_joint_3d.cpp:661
    #3 0xd588467 in Joint3D::_update_joint(bool) scene/3d/physics_joint_3d.cpp:127
    #4 0xd58bff0 in Joint3D::_notification(int) scene/3d/physics_joint_3d.cpp:195
    #5 0xd5f24e1 in Joint3D::_notificationv(int, bool) scene/3d/physics_joint_3d.h:38
    #6 0xd5fe132 in ConeTwistJoint3D::_notificationv(int, bool) scene/3d/physics_joint_3d.h:211
    #7 0x12dd2bba in Object::notification(int, bool) core/object/object.cpp:793
    #8 0xbc77e75 in Node::_propagate_ready() scene/main/node.cpp:188
    #9 0xbc776db in Node::_propagate_ready() scene/main/node.cpp:180
    #10 0xbc776db in Node::_propagate_ready() scene/main/node.cpp:180
    #11 0xbc776db in Node::_propagate_ready() scene/main/node.cpp:180
    #12 0xbcc66fc in Node::_set_tree(SceneTree*) scene/main/node.cpp:2528
    #13 0xbc9b576 in Node::_add_child_nocheck(Node*, StringName const&) scene/main/node.cpp:1214
    #14 0xbc9cbe1 in Node::add_child(Node*, bool) scene/main/node.cpp:1232
    #15 0xa64b07b in void call_with_variant_args_helper<__UnexistingClass, Node*, bool, 0ul, 1ul>(__UnexistingClass*, void (__UnexistingClass::*)(Node*, bool), Variant const**, Callable::CallError&, IndexSequence<0ul, 1ul>) core/variant/binder_common.h:196
    #16 0xa645e93 in void call_with_variant_args_dv<__UnexistingClass, Node*, bool>(__UnexistingClass*, void (__UnexistingClass::*)(Node*, bool), Variant const**, int, Callable::CallError&, Vector<Variant> const&) core/variant/binder_common.h:313
    #17 0xa63632c in MethodBindT<Node*, bool>::call(Object*, Variant const**, int, Callable::CallError&) core/object/method_bind.h:282
    #18 0x528b271 in GDScriptFunction::call(GDScriptInstance*, Variant const**, int, Callable::CallError&, GDScriptFunction::CallState*) modules/gdscript/gdscript_vm.cpp:1476
    #19 0x4e0491d in GDScriptInstance::call(StringName const&, Variant const**, int, Callable::CallError&) modules/gdscript/gdscript.cpp:1544
    #20 0x12e3bcd5 in ScriptInstance::call(StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) core/object/script_language.cpp:314
    #21 0xbc6ef29 in Node::_notification(int) scene/main/node.cpp:58
    #22 0x2b730ef in Node::_notificationv(int, bool) scene/main/node.h:45
    #23 0x2b759be in CanvasItem::_notificationv(int, bool) scene/main/canvas_item.h:164
    #24 0x2b780a8 in Control::_notificationv(int, bool) scene/gui/control.h:47
    #25 0x12dd2bba in Object::notification(int, bool) core/object/object.cpp:793
    #26 0xbd6fc09 in SceneTree::_notify_group_pause(StringName const&, int) scene/main/scene_tree.cpp:815
    #27 0xbd62d07 in SceneTree::process(float) scene/main/scene_tree.cpp:444
    #28 0x1f252b4 in Main::iteration() main/main.cpp:2480
    #29 0x1dd55ea in OS_LinuxBSD::run() platform/linuxbsd/os_linuxbsd.cpp:261
    #30 0x1dc8520 in main platform/linuxbsd/godot_linuxbsd.cpp:58
    #31 0x7f5c6c8800b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
    #32 0x1dc805d in _start (/mnt/Miecz/mojgodot/bin/godot.linuxbsd.tools.64s+0x1dc805d)

0x61500014f090 is located 16 bytes inside of 472-byte region [0x61500014f080,0x61500014f258)
freed by thread T0 here:
    #0 0x7f5c6d8e41b7 in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.6+0xb01b7)
    #1 0x11cd83d8 in Memory::free_static(void*, bool) core/os/memory.cpp:169
    #2 0xfca975a in void memdelete<Joint3DSW>(Joint3DSW*) (/mnt/Miecz/mojgodot/bin/godot.linuxbsd.tools.64s+0xfca975a)
    #3 0xfc7e736 in PhysicsServer3DSW::joint_make_cone_twist(RID, RID, Transform const&, RID, Transform const&) servers/physics_3d/physics_server_3d_sw.cpp:1171
    #4 0xfd4e05e in PhysicsServer3DWrapMT::joint_make_cone_twist(RID, RID, Transform const&, RID, Transform const&) servers/physics_3d/physics_server_3d_wrap_mt.h:367
    #5 0xd5b886d in ConeTwistJoint3D::_configure_joint(RID, PhysicsBody3D*, PhysicsBody3D*) scene/3d/physics_joint_3d.cpp:659
    #6 0xd588467 in Joint3D::_update_joint(bool) scene/3d/physics_joint_3d.cpp:127
    #7 0xd58bff0 in Joint3D::_notification(int) scene/3d/physics_joint_3d.cpp:195
    #8 0xd5f24e1 in Joint3D::_notificationv(int, bool) scene/3d/physics_joint_3d.h:38
    #9 0xd5fe132 in ConeTwistJoint3D::_notificationv(int, bool) scene/3d/physics_joint_3d.h:211
    #10 0x12dd2bba in Object::notification(int, bool) core/object/object.cpp:793
    #11 0xbc77e75 in Node::_propagate_ready() scene/main/node.cpp:188
    #12 0xbc776db in Node::_propagate_ready() scene/main/node.cpp:180
    #13 0xbc776db in Node::_propagate_ready() scene/main/node.cpp:180
    #14 0xbc776db in Node::_propagate_ready() scene/main/node.cpp:180
    #15 0xbcc66fc in Node::_set_tree(SceneTree*) scene/main/node.cpp:2528
    #16 0xbc9b576 in Node::_add_child_nocheck(Node*, StringName const&) scene/main/node.cpp:1214
    #17 0xbc9cbe1 in Node::add_child(Node*, bool) scene/main/node.cpp:1232
    #18 0xa64b07b in void call_with_variant_args_helper<__UnexistingClass, Node*, bool, 0ul, 1ul>(__UnexistingClass*, void (__UnexistingClass::*)(Node*, bool), Variant const**, Callable::CallError&, IndexSequence<0ul, 1ul>) core/variant/binder_common.h:196
    #19 0xa645e93 in void call_with_variant_args_dv<__UnexistingClass, Node*, bool>(__UnexistingClass*, void (__UnexistingClass::*)(Node*, bool), Variant const**, int, Callable::CallError&, Vector<Variant> const&) core/variant/binder_common.h:313
    #20 0xa63632c in MethodBindT<Node*, bool>::call(Object*, Variant const**, int, Callable::CallError&) core/object/method_bind.h:282
    #21 0x528b271 in GDScriptFunction::call(GDScriptInstance*, Variant const**, int, Callable::CallError&, GDScriptFunction::CallState*) modules/gdscript/gdscript_vm.cpp:1476
    #22 0x4e0491d in GDScriptInstance::call(StringName const&, Variant const**, int, Callable::CallError&) modules/gdscript/gdscript.cpp:1544
    #23 0x12e3bcd5 in ScriptInstance::call(StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) core/object/script_language.cpp:314
    #24 0xbc6ef29 in Node::_notification(int) scene/main/node.cpp:58
    #25 0x2b730ef in Node::_notificationv(int, bool) scene/main/node.h:45
    #26 0x2b759be in CanvasItem::_notificationv(int, bool) scene/main/canvas_item.h:164
    #27 0x2b780a8 in Control::_notificationv(int, bool) scene/gui/control.h:47
    #28 0x12dd2bba in Object::notification(int, bool) core/object/object.cpp:793
    #29 0xbd6fc09 in SceneTree::_notify_group_pause(StringName const&, int) scene/main/scene_tree.cpp:815

previously allocated by thread T0 here:
    #0 0x7f5c6d8e4517 in malloc (/lib/x86_64-linux-gnu/libasan.so.6+0xb0517)
    #1 0x11cd74cb in Memory::alloc_static(unsigned long, bool) core/os/memory.cpp:76
    #2 0x11cd73ca in operator new(unsigned long, char const*) core/os/memory.cpp:41
    #3 0xfc7e510 in PhysicsServer3DSW::joint_make_cone_twist(RID, RID, Transform const&, RID, Transform const&) servers/physics_3d/physics_server_3d_sw.cpp:1167
    #4 0xfd4e05e in PhysicsServer3DWrapMT::joint_make_cone_twist(RID, RID, Transform const&, RID, Transform const&) servers/physics_3d/physics_server_3d_wrap_mt.h:367
    #5 0xd5b886d in ConeTwistJoint3D::_configure_joint(RID, PhysicsBody3D*, PhysicsBody3D*) scene/3d/physics_joint_3d.cpp:659
    #6 0xd588467 in Joint3D::_update_joint(bool) scene/3d/physics_joint_3d.cpp:127
    #7 0xd58bff0 in Joint3D::_notification(int) scene/3d/physics_joint_3d.cpp:195
    #8 0xd5f24e1 in Joint3D::_notificationv(int, bool) scene/3d/physics_joint_3d.h:38
    #9 0xd5fe132 in ConeTwistJoint3D::_notificationv(int, bool) scene/3d/physics_joint_3d.h:211
    #10 0x12dd2bba in Object::notification(int, bool) core/object/object.cpp:793
    #11 0xbc77e75 in Node::_propagate_ready() scene/main/node.cpp:188
    #12 0xbc776db in Node::_propagate_ready() scene/main/node.cpp:180
    #13 0xbc776db in Node::_propagate_ready() scene/main/node.cpp:180
    #14 0xbc776db in Node::_propagate_ready() scene/main/node.cpp:180
    #15 0xbcc66fc in Node::_set_tree(SceneTree*) scene/main/node.cpp:2528
    #16 0xbc9b576 in Node::_add_child_nocheck(Node*, StringName const&) scene/main/node.cpp:1214
    #17 0xbc9cbe1 in Node::add_child(Node*, bool) scene/main/node.cpp:1232
    #18 0xa64b07b in void call_with_variant_args_helper<__UnexistingClass, Node*, bool, 0ul, 1ul>(__UnexistingClass*, void (__UnexistingClass::*)(Node*, bool), Variant const**, Callable::CallError&, IndexSequence<0ul, 1ul>) core/variant/binder_common.h:196
    #19 0xa645e93 in void call_with_variant_args_dv<__UnexistingClass, Node*, bool>(__UnexistingClass*, void (__UnexistingClass::*)(Node*, bool), Variant const**, int, Callable::CallError&, Vector<Variant> const&) core/variant/binder_common.h:313
    #20 0xa63632c in MethodBindT<Node*, bool>::call(Object*, Variant const**, int, Callable::CallError&) core/object/method_bind.h:282
    #21 0x528b271 in GDScriptFunction::call(GDScriptInstance*, Variant const**, int, Callable::CallError&, GDScriptFunction::CallState*) modules/gdscript/gdscript_vm.cpp:1476
    #22 0x4e0491d in GDScriptInstance::call(StringName const&, Variant const**, int, Callable::CallError&) modules/gdscript/gdscript.cpp:1544
    #23 0x12e3bcd5 in ScriptInstance::call(StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) core/object/script_language.cpp:314
    #24 0xbc6ef29 in Node::_notification(int) scene/main/node.cpp:58
    #25 0x2b730ef in Node::_notificationv(int, bool) scene/main/node.h:45
    #26 0x2b759be in CanvasItem::_notificationv(int, bool) scene/main/canvas_item.h:164
    #27 0x2b780a8 in Control::_notificationv(int, bool) scene/gui/control.h:47
    #28 0x12dd2bba in Object::notification(int, bool) core/object/object.cpp:793
    #29 0xbd6fc09 in SceneTree::_notify_group_pause(StringName const&, int) scene/main/scene_tree.cpp:815

SUMMARY: AddressSanitizer: heap-use-after-free servers/physics_3d/physics_server_3d_sw.cpp:1177 in PhysicsServer3DSW::cone_twist_joint_set_param(RID, PhysicsServer3D::ConeTwistJointParam, float)

@quarmin I think it should be fixed with latest commit, but let me know just in case

There is still one more thing I have to do, which is to refactor the command queue for all this to actually work properly, but I will do it in the next PR.

Crash with multithread rendering still exists(this one with physics was fixed). - RegressionTestProject.zip
Now additionally prints this lines
servers/rendering/renderer_scene_cull.cpp:440:32: runtime error: downcast of address 0x608001087fb0 which does not point to an object of type 'InstanceLightData'
0x608001087fb0: note: object is of type 'RendererSceneCull::InstanceBaseData'
 be be be be  90 6d 86 1d 00 00 00 00  0e 00 00 00 a3 50 00 00  00 00 00 00 00 00 00 00  00 00 00 00
              ^~~~~~~~~~~~~~~~~~~~~~~
              vptr for 'RendererSceneCull::InstanceBaseData'

@qarmin, cold you try the same (with multi-threaded rendering) with this patch applied?
safe_rids_patch.txt
I have the suspicion that some RID_Owners need to be thread-safe.

@RandomShaper ah man, I forgot to make those thread safe, great thing you spotted it

@RandomShaper @qarmin ok, should be fixed now.
It will probably still error (needs the rewrite of CommandQueue to truly work as intended), but should not crash.

I still have same crash
A lot of smaller project - RegressionTestProject.zip
It only adds nodes to scene and later remove them

@qarmin this seems like a bug in the command queue that I don't understand, as it looks server code is being called from different threads when it should not, so it's a bit unrelated to this PR. Currently @hpvb is rewriting the command queue, and I suggest testing this reproduction case against his new work (or opening an issue and we make sure his PR passes it).

@reduz, the last version pushed crashes for me unless I make more RID_Owners thread safe.
Specifically, I believe that every RID_Owner whose contents are subject to the allocate-initialize split need to be thread-safe, since they are accessed by both the server thread and any thread creating an object.
I've changed all the RID_Owners to thread-safe locally (as I did in the patch I posted) and the crash is gone.
Not sure if that's something that will be addressed by the MT rewrite.

Sorry, I approved by mistake. I didn't want to approve yet. I've re-asked myself for review.

@RandomShaper I already changed the rid owners to thread safe in my latest forced push, not sure which ones you believe are missing.

@qarmin nevermind I found the bug

Ok, if nothing else fails or no further changes are requested, this should be ready to merge after CI passes.

Thanks!


Fix possible error E5560 when notifying

Hi ! Hope it is fine to open a PR like this.
I started using chezmoi.nvim with the following config and rcarriga/nvim-notify as a vim.notify backend.
{
  edit = {
    watch = true,
  },
}

But I recently changed my vim.notify backend to j-hui/fidget.nvim and started to experience the following errors when saving a chezmoi managed buffer.
"~/.local/share/chezmoi/dot_config/nvim/lua/jbmorice/plugins/lspconfig.lua" 106L, 3437B written
Error detected while processing BufWritePost Autocommands for "<buffer=13>":
Error executing lua callback: ...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:499: 'chezmoi apply --source-path C:
/Users/Jean-Baptiste/.local/share/chezmoi/dot_config/nvim/lua/jbmorice/plugins/lspconfig.lua' was unable to complete in 5000 m
s
stack traceback:
        [C]: in function 'error'
        ...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:499: in function 'wait'
        ...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:453: in function 'sync'
        ...m-data/lazy/chezmoi.nvim/lua/chezmoi/commands/__base.lua:38: in function 'execute'
        ...m-data/lazy/chezmoi.nvim/lua/chezmoi/commands/__edit.lua:56: in function <...m-data/lazy/chezmoi.nvim/lua/chezmoi/c
ommands/__edit.lua:46>

Error executing luv callback:
...-data/lazy/fidget.nvim/lua/fidget/notification/model.lua:264: E5560: vimL function must not be called in a lua loop callbac
k
stack traceback:
        [C]: in function 'sort'
        ...-data/lazy/fidget.nvim/lua/fidget/notification/model.lua:264: in function 'update'
        ...l/nvim-data/lazy/fidget.nvim/lua/fidget/notification.lua:257: in function 'notify'
        ...Local/nvim-data/lazy/chezmoi.nvim/lua/chezmoi/notify.lua:8: in function 'plain'
        ...Local/nvim-data/lazy/chezmoi.nvim/lua/chezmoi/notify.lua:12: in function 'info'
        ...m-data/lazy/chezmoi.nvim/lua/chezmoi/commands/__edit.lua:62: in function '_user_on_exit'
        ...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:240: in function '_shutdown'
        ...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:47: in function <...ta/Local/nvim-data/lazy/plenary.nvim/l
ua/plenary/job.lua:38>
        [C]: in function 'wait'
        ...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:486: in function 'wait'
        ...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:453: in function 'sync'
        ...m-data/lazy/chezmoi.nvim/lua/chezmoi/commands/__base.lua:38: in function 'execute'
        ...m-data/lazy/chezmoi.nvim/lua/chezmoi/commands/__edit.lua:56: in function <...m-data/lazy/chezmoi.nvim/lua/chezmoi/c
ommands/__edit.lua:46>

I am not very experienced with lua and neovim development but here is my understanding of the issue:

sometimes the callbacks of the plenary jobs used to run chezmoi commands are executed in a "fast" event handler;
"fast" event handlers restricts vim API usage drastically, and an error E5560 occurs when an unauthorized call is made;
and a vim.notify backend may use unauthorized vim functions in its implementation (like j-hui/fidget.nvim seems to do in here).

The solution I found was to guard the vim.notify call in lua/chezmoi/notify.lua by a vim.in_fast_event() check and passing it through a vim.schedule call when it is true.
And thanks four your work on this plugin, it has greatly improved my workflow when editing my neovim config. 😃

Looks great! Thanks!


Implement ToValue trait for for RPC Reply Failure

https://github.com/rgb-org/rgb-node/blob/8850ce64797c12a928450b9e2c87be7c333bb944/src/rpc/reply.rs#L139-L140

Duplicated #61


Local Build on vs2017

i m not able to build on local server.

Please give me some more information.

You need to install the UWP SDK or use the NoUWP solution file instead.

I tried using the NoUWP solution file but same problem, can u please guide me / provide me link for UWP SDK coz i think i have installed that also...but to make sure please provide me the SDK link.

You need to select the UWP workload in VS Setup.

Can you please Guide me with Same, pretty much new to IOT

You will find all information here: https://docs.microsoft.com/en-us/windows/uwp/get-started/
But I recommend to use the MQTTnet.noUWP.sln instead. If this still fails please post the error.


Discovering a manager by only the domain name

Part of MSC1957
Similar to the .well-known discovery done by servers (and clients during login), clients which have an integrations domain (eg: "example.org") make a regular HTTPS request to https://example.org/.well-known/matrix/integrations which returns an object which looks like the following:
{
    "m.integrations_widget": {
        "url": "https://integrations.example.org/ui?displayName=$matrix_display_name",
        "data": {
            "api_url": "https://integrations.example.org"
        }
    }
}

sample https://scalar.vector.im/.well-known/matrix/integrations

De-Scoped for riot-android
Use riot web to change your integration server


Fix CSI refNameToId resolution

The current code does this in a weird way where a second invocation of index parsing adds this...

Might involve enhancement to tabix-js to allow passing refseq IDs directly into the blocksForRange

The CSI code from @gmod/tabix was pulled into this repo and does not require this structure


Handle 429 errors due to rate limiting on H1 API

The H1 API has a built-in rate limit (currently set at 600 requests per minute). If you have a large number of programs, you will hit this rate limit and it will cause some portion of your programs gathered by bbscope to falsely report NO_IN_SCOPE_TABLE when in fact what has happened is the API returned a 429 response due to rate limiting.
This change adds a simple loop with 5 second delay (up to 50 seconds) so that the total requests comes under the rate limit and full program details can be retrieved.
As I am learning Golang it is possible some of this may not be idiomatic and you are welcome to edit as necessary :)

Please note you will only see this error if you have a large number of programs such that you are exceeding the rate limit of the API. Many users will not encounter this limit. An alternative fix for this would be to reduce (or make configurable) the number of threads or add a delay between requests.

Hey there, thank you for sending this PR.
This has been on my to-do list for a while but couldn't find time to add it yet.
Merging now, appreciate your help :)


Incorrect protocol in graphic

In the graphic showing replication to Azure, the incorrect protocol is shown for the VMs communicating with the Management Server.  The protocol should be HTTPS not HTPPS.
[Enter feedback here]

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

ID: 43cb8e74-332e-d1c2-2ba4-eff91806de73
Version Independent ID: cb7300cf-6aed-1deb-d36d-fdd63955b6b4
Content: Architecture for physical server disaster recovery to Azure using Azure Site Recovery
Content Source: articles/site-recovery/physical-azure-architecture.md
Service: site-recovery
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

This is now fixed. #please-close

@glecanu We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Update Temperature subcomponent with user data

Edit Temperature.js component in order to get the average temperature of all checkups the signed-in user has completed.
Acceptance Criteria:

Flow should be the user signs in with Blockstack, and is then able to see their average temperature over all their completed checkups
Data is pulled from QA environment for the logged-in user
Any addition of Temperature.js to another component is cleaned up and returned to original state so as to avoid scope creep.

Notes:

Until Temperature.js is included within DiagnosticContainer.js (which a WIP PR is out for in #90 ), then you'll have to probably update App.js to just add it in any spot for the time being, but be sure to clean up once PR is made to stay within scope.

The data is expected from the container in this solution: https://github.com/friedger/Corona-tracker/commit/c97ca57f2e717a9acff951c94226b80f47b22b30

I like the look of this a lot! I hadn't even thought about Temperature.js being class-based when it should be functional. Want to make a PR for it?


pmd: 6.43.0 -> 6.44.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pmd/versions.
meta.description for pmd is: "An extensible cross-language static code analyzer"
meta.homepage for pmd is: "https://pmd.github.io/"
meta.changelog for pmd is: "https://pmd.github.io/pmd-6.44.0/pmd_release_notes.html"
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0/bin/ast-dump.bat had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0/bin/run.sh had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0/bin/cpd.bat had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0/bin/pmd.bat had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0/bin/.run.sh-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0/bin/bgastviewer.bat had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0/bin/designerold.bat had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0/bin/designer.bat had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0/bin/cpdgui.bat had a zero exit code or showed the expected version
0 of 9 passed binary check by having a zero exit code.
0 of 9 passed binary check by having the new version present in output.
found 6.44.0 with grep in /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0
found 6.44.0 in filename of file in /nix/store/4b21gscqasqjznpba7aqq61pkirx7294-pmd-6.44.0

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

2 total rebuild path(s)

1 package rebuild(s)

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

First fifty rebuilds by attrpath
pmd

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

pmd

Maintainer pings

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

1 package built:

pmd

Superseeded by #182919.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pmd/versions.
meta.description for pmd is: "An extensible cross-language static code analyzer"
meta.homepage for pmd is: "https://pmd.github.io/"
meta.changelog for pmd is: "https://pmd.github.io/pmd-6.48.0/pmd_release_notes.html"
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.48.0 with grep in /nix/store/xyjc7i35s6mgd9x13ggxrrhzfq5d1qg8-pmd-6.48.0
found 6.48.0 in filename of file in /nix/store/xyjc7i35s6mgd9x13ggxrrhzfq5d1qg8-pmd-6.48.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pmd

Instructions to test this update (click to expand)

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

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

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

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


Prefixes and suffixes are not applied to order numbers and invoice numbers when the length field is left unspecified.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
master
Issue Description
Prefixes and suffixes are not applied to order numbers and invoice numbers when the length field is left unspecified.
Preconditions
On the admin panel, the order and invoice settings have been configured, but the length parameter has not been specified.
Steps to reproduce

Navigate to 'Admin > Configuration > Sales > Order Settings.'
Configure the "Order Number Prefix" or "Order Number Suffix" as desired and save the settings.
Similarly, visit 'Admin > Configuration > Sales > Invoice Settings' and adjust the settings accordingly.
After making these changes, create an order and generate an invoice.
Observation will reveal that the prefix and suffix are not applied as expected.

Expected Result
The prefix or suffix should have been added to the order number and invoice number.
Actual Result
Prefix or suffix not added to order number and invoice number.
Screenshots
No response
Additional context
No response

@sunarcrajneesh, Thank you for informing.

We will be happy to work on it.

@sunarcrajneesh I have assigned this issue to you. please proceed.


Openblas failed to pour the bottle on macOS

brew gist-logs <formula> link OR brew config AND brew doctor output
Your system is ready to brew.

Verification

[X] My "brew doctor output" says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.
[X] I searched for recent similar issues at https://github.com/Homebrew/homebrew-core/issues?q=is%3Aissue and found no duplicates.

What were you trying to do (and why)?
I have already installed the formula openblas and I wanted to upgrade it. I have seen a similar issue in another formula https://github.com/Homebrew/brew/pull/15805
What happened (include all command output)?
==> Upgrading openblas
  0.3.23 -> 0.3.24

Error: Parameter 'old': Expected type Pathname, got type String with value "@@HOMEBREW_PREFIX@@/opt/gc.../gcc/x86_64-apple-darwin22/13"
Caller: /usr/local/Homebrew/Library/Homebrew/extend/os/mac/keg_relocate.rb:41
Definition: /usr/local/Homebrew/Library/Homebrew/os/mac/keg.rb:40

What did you expect to happen?
Pouring of the bottle properly.
Step-by-step reproduction instructions (by running brew commands)
brew upgrade openblas

Looks like change_rpath has the wrong type signature (old and new are always String and never Pathname)

Thank you for the quick reply! Is this something I should fix in my installation or it depends on the formula?

@alazarolop Can I see your brew config output? Working on a fix, thanks.

Thank you a lot @MikeMcQuaid .

You're welcome @alazarolop!

Looks like change_rpath has the wrong type signature (old and new are always String and never Pathname and ruby-macho expects Strings)

apologies, I added that in #15980 but didn't know what I was doing. It was needed for intermediate form of the pull request, but I think the type declarations aren't needed now. Should I remove the other type signatures that I added to os/mac/keg?

@scpeters No worries, it happens! I think fine to leave other signatures in unless you know them to be wrong but, lesson learned for me I guess on being wary of these sorts of changes that aren't covered by test.


Add the ability to save the plot

Hi @joanna-janos , thanks for your contribution.
Before @davidtvs reviewing this PR, you may note that this package still needs to support Python 2.7. However, the builtin module pathlib you used was introduced since Python 3.4.
Therefore, you might need to change the code to make it compatible with Python 2.7.

Hi @NaleRaphael,
sorry for that, I have changed code to make it compatible with python 2.7 (use os instead of pathlib)

I would prefer to do this by returning the matplotlib figure and axes. The user can then choose if he wants to save and how he wants to do it. This way there's no additional parameter, no extra code on our side, and it's also more flexible for the user (plot can be manipulated and then saved in whatever way the user wants)

@davidtvs  You're right, this approach is much more flexible!

@joanna-janos thanks for bringing this to our attention. I'm closing this PR but feel free to open a new one that returns the figure and the axis from 'plot'

FYI, the commit https://github.com/davidtvs/pytorch-lr-finder/commit/70b6c1f3a2ed587f48fa0dd8bd372721cf8208a8 implements the functionality that I described above.
@joanna-janos to save the figure you can now do:
# Create the figure and axes object outside and pass the axes to lr_finder.plot
fig, ax = plt.subplots()
lr_finder.plot(ax=ax)

# ax can be further manipulated by the user after lr_finder.plot

fig.savefig("test.png")

Note that when you pass the Axes object to lr_finder.plot() the figure is not shown (no plt.show()) to avoid destroying the figure before you can save it.


[compiler] Named instantiation of template arguments

Implementation of named template arguments as described in #2340.
I added a new syntax node (TemplateArgument), and a cover grammar for this node:
<Expression> ('=' <Expression>)?
Rather than ExpressionNode, the type of a template argument is now TemplateArgumentNode.
If the = is parsed, we assert in the parser that the first Expression must be a "bare identifier"  (i.e. a TypeReference with target: Identifier) and unwrap the identifier to produce a clean AST with `name?: Identifier
Template arguments are evaluated in the order that they were declared, not in the order they are specified in the instantiation. The new template argument checker replaces the previous one, and it performs normalization of argument order and typechecking of template arguments all in one pass.
TODO:

[ ] Review templates across core libraries to ensure that template arguments have good names.
[x] Documentation of new behavior in website.
[x] Semantic/tmlanguage colorization of tokens.
[x] Validate that the AST printer produces the correct text for the new template argument nodes and that the output is well-formatted.
[x] Completion of template argument names in argument position.
[x] Hover context on template argument names in instantiation.

Closes #2340

Full example: https://cadlplayground.z22.web.core.windows.net/prs/2546/?c=LyoqCiAqIEB0ZW1wbGF0ZSBUMiBTZWNvbmQgcGFyYW1ldGVyLgogKi8KYWxpYXMgRm9vPFQxLCBUMiwgVDMgPSBzdHJpbmcsIFQ0ID0gbnVtZXJpYz4gPSBbyibEHV07CsdCSTEgPSAxO8gOMiA9IDLJDsRSM8kOxFM0OwoKbW9kZWwgQWNjZXB0IHsKICBhOuUAiUkxLCBJMiwgSTMsIEk0PjsKICBizBrFEmPQLMUWZM4W5QC%2Bx0Nl0l3MH2bPOuQAs9AkZ9VeyS3FJGjKJFTkAQXnAK9pxhfHEywgVOQBL0kxxRxqxxzJc8YczGHJSn3oATdSZWplY%2B0BN8k3x3PnATTKPO0BNcplyyDoAT%2FkAKHGFywgVDXkAgJldmVy7QFHzSMzPOYCMOQCIuUBCH0K&e=%40typespec%2Fopenapi3&options={}

Validated in the playground that this allows the required customization for Microsoft Graph - thank you!

@allenjzhang Gentle nudge on getting this into the build. It's been open quite a while.

@garethj-msft Just to give you a concrete ETA: we've got a couple of open PRs blocking this one -- just renames of template args that we've been discussing. I'm aiming to have this merged next week for release in January.


DTLS 1.2 strictly support

Hello,
How   the openssl must be configured in order to support strictly DTLS 1.2?
Not include DTLS 1.0 chiphers
I just configure the SSL_ctx using the  DTLSv1_2_server_method and
DTLSv1_2_client_method respectively
Βut analyzing  th wiresharks I detect that in the client hello dtls 1.0
chiphes are included as well.
Is this right?
Morever, how we can configure  the openssl to support fallback to lower
version if the server does not support 1.2
Thank you
George

Morever, how we can configure the openssl to support fallback to lower
version if the server does not support 1.2

Use DTLS_server_method and DTLS_client_method instead. These are the preferred "version flexible" methods that will negotiate the highest version available on both client and server.

How the openssl must be configured in order to support strictly DTLS 1.2?
Not include DTLS 1.0 chiphers

Probably you don't really want to do this. If you only configure DTLSv1.2 ciphers then you lose all the benefits of version flexibility since DTLSv1.0 will not work.
Nevertheless, the ciphersuites can be configured using SSL_CTX_set_cipher_list or SSL_set_cipher_list:
https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_cipher_list.html

Thank you for your answer


What exactly stored in "const.f64" partition?

The specification says

The value at that entry is a 64-bit floating point value

but entry_size in the partition "const.f64" produced by MSVC (IFC-version 0.40) is equal to 12.

This oddity is a remnant of the early days of MSVC's serialization of 64-bit floating point type values, and has not been updated.


Update smoltcp to 0.12.0 and embassy-net to 0.5.0

Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝

[x] I have updated existing examples or added new ones (if applicable).
[x] I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
[ ] My changes were added to the CHANGELOG.md in the proper section.
[ ] I have added necessary changes to user code to the Migration Guide.
[x] My changes are in accordance to the esp-rs API guidelines

Extra:

[x] I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖
Description
This provides an update for<EMAIL_ADDRESS>-><EMAIL_ADDRESS>and bumps embassy-net to 0.5.0 for the examples.
I've only updated the API surface and examples so it builds; perhaps new APIs introduced by<EMAIL_ADDRESS>would be worth an internal driver refactor for optimization.
Closes #2662
TODO:

[x] Find a solution for https://github.com/embassy-rs/embassy/issues/3670
https://github.com/esp-rs/esp-hal/blob/9a6afcff75dca4baf4b073b1102c149f5137014e/esp-wifi/src/wifi/mod.rs#L2684-L2690
[x] Fix example for wifi_dhcp_smoltcp_nal.rs
[ ] Write migration guide
[x] Add CHANGELOG entries.

Testing
CI needs to pass, and runtime needs to be tested.

Lets just get rid of wifi_dhcp_smoltcp_nal.rs - we plan to reorganize / rewrite examples and the example isn't that useful

I'm wondering if this needs a migration guide. The update for esp-wifi is completely transparent, and the examples only really changed to demonstrate how to use the new<EMAIL_ADDRESS>release. We don't hardly depend on embassy-net for esp-wifi.


CSS compression not working with LESS

When turning on CSS compression in any project using LESS I get the following error:
Liquid Exception: undefined method `gsub' for nil:NilClass in /_layouts/template.html

This worked on older jekyll-assets versions using yui-compressor so I asssume it's some issue with SASS...

Hi @abeMedia, can you run it again with --trace and give us the full exception?  That would better help me figure out where the problem originates and if it's an upstream problem or if it originates in our LESS plugin (which I would hope it wouldn't...)

Hi @envygeeks, Sorry about the late reply! Here is the full exception I get when turning on CSS compression:
  Liquid Exception: undefined method `gsub' for nil:NilClass in /_layouts/default.html
/home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-assets-2.2.8/lib/jekyll/assets/liquid/tag.rb:222:in `capture_and_out_error': undefined method `gsub' for nil:NilClass (NoMetho
dError)
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-assets-2.2.8/lib/jekyll/assets/liquid/tag.rb:102:in `rescue in render'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-assets-2.2.8/lib/jekyll/assets/liquid/tag.rb:91:in `render'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/block.rb:151:in `render_token'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/profiler/hooks.rb:5:in `block in render_token_with_profiling'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/profiler.rb:80:in `profile_token_render'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/profiler/hooks.rb:4:in `render_token_with_profiling'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/block.rb:135:in `block in render_all'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/block.rb:122:in `each'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/block.rb:122:in `render_all'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/block.rb:108:in `render'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/template.rb:210:in `block in render'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/template.rb:262:in `with_profiling'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/template.rb:209:in `render'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/liquid-3.0.6/lib/liquid/template.rb:222:in `render!'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/liquid_renderer/file.rb:28:in `block (2 levels) in render!'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/liquid_renderer/file.rb:40:in `measure_bytes'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/liquid_renderer/file.rb:27:in `block in render!'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/liquid_renderer/file.rb:47:in `measure_time'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/liquid_renderer/file.rb:26:in `render!'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/renderer.rb:114:in `render_liquid'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/renderer.rb:157:in `place_in_layouts'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/renderer.rb:71:in `run'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/site.rb:447:in `block (2 levels) in render_docs'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/site.rb:445:in `each'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/site.rb:445:in `block in render_docs'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/site.rb:444:in `each'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/site.rb:444:in `render_docs'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/site.rb:190:in `render'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/site.rb:69:in `process'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/command.rb:26:in `process_site'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/commands/build.rb:63:in `build'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/commands/build.rb:34:in `process'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/lib/jekyll/commands/build.rb:16:in `block (2 levels) in init_with_program'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        from /home/koding/.rvm/gems/ruby-2.3.0/gems/jekyll-3.2.1/exe/jekyll:13:in `<top (required)>'
        from /home/koding/.rvm/gems/ruby-2.3.0/bin/jekyll:23:in `load'
        from /home/koding/.rvm/gems/ruby-2.3.0/bin/jekyll:23:in `<main>'
        from /home/koding/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `eval'
        from /home/koding/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `<main>'

Hey @abeMedia,
I just encountered this same issue while using the SASS compressor v3.4.22. Some of the .css files I was including via sprockets require statements had invalid CSS constructs in them. For example, this CSS file is a surefire way to trigger the error:
/**
 * Filename: bad-media-queries.css
 */
.example-foo-ul:media(max-width: 123px) li {
    display: block;
}

I was able to identify the file(s) which were causing problems by removing all of my require statements and re-adding them one at a time. It would be nice if the console error included a file:line of the CSS token it got hung up on.

We no longer support LESS.  Less support will need to either be provided by Less through Sprockets or be unsupported by our system, we do not feel it's beneficial to support something that is rarely used, it adds extra overhead and development time.   Sorry.

Totally understand! By now the vast majority of projects I'm involved in
have been migrated to sass anyway...


Allow developer to add their own "people" field names that get the attributes handled automatically

There is some code in one of Quinten's playgrounds (hopefully still there) that identifies fields that look like people's names and treats them like labels.
Do we need to allow people to self-identify "people" prefixes? or will our automated way to do it be enough?

The big todo here is integrating the new name into the various places we check to see if it's a reserved name and transform it. It needs to be handled everywhere we call those functions and will take careful checking.

Do we want to make this a list? Or keep the person variable singular?

Closed in #229


[WIP] Serialize different message types

Done:
all primitives,
objects,
arrays,
null
To Do:
node,
regexp,
date,
map,
set,
weakmap,
weakset,
iterator,
generator,
error,
proxy,
promise,
typedarray,
arraybuffer,
dataview

everything has moved to github.com/everlastingbugstopper/chrome-devtools-rs


Add support for YAML fixer

Name: yaml
URL: https://pypi.org/project/pyaml/

Neoformat can format YAML/YML files using pyaml. I would much rather use ALE for all my linter/fixer needs. ALE has support for yaml linters via swaglint or yamllint, but no yaml fixers (a much needed functionality when writing lots of yaml files by hand).

FYI there is now prettier support for yaml.

Thank you @tomsvogel .
I was not aware of that one.
Since I am already using prettier for JS, I can also use prettier for yaml. Therefore, I have no need for pyaml at this time.

@petermbenjamin @tomsvogel How did you use prettier for yaml?
My vim file is like this
.vim/after/ftplugin/yaml.vim
" npm install -g prettier
let b:ale_fixers = ['prettier']

.vimrc
...
let g:ale_fixers = {}
let g:ale_fix_on_save = 1
let g:ale_set_loclist = 0
let g:ale_set_quickfix = 1

but it doesn't work.
JS, Python, Go, C++ are all working fine.

I am not 100% shure but i think to use prettier as yaml fixer ALE hast to be extended.

Here is what I did and it seems to work for me:
 let g:ale_fixers      = {
    \ "*": ['trim_whitespace', 'remove_trailing_lines'],
    \ 'javascript': ['prettier', 'eslint'],
    \ 'sh': ['shfmt'],
    \ 'yaml': ['prettier'],
    \}

As long as you have prettier installed (e.g. npm i -g prettier), that should work.


Grid disable checkbox but only if rows has a specific value in a column

Hy All,
I have a grid that load in a bootstrap modal after a php call, i have selectColumn true but i want that onLoad if there is a specific value in the row for a specific column only that checkbox of that row must be disabled.
I tried in onLoad and i can recover the id of row the value of the row column but i can't disabled the check box, the logic is that on onload i recover the xhr.responseText i do a jquery loop for each record and inside the loop if the value of the column of that row is PIPPO(EXAMPLE) i must disable the checkbox...But the problem is that the checkbox remain always enabled.Can someone help me?If you want the code i can paste it here....

Please submit only bugs here. All questions to w2ui.com or stackoverflow.
The best way would be to attach to onRefresh, and in onComplete loop update DOM with jQuery.


Various fixes for the CSS

more like added upon the existing css instead of properly modifying it, so it's a bit of a quick-and-dirty solution, but it improves the visuals tremendously, already. Should be integrated better with the existing css at some point in the future.

For the Sync modal, the load more buttons are now at the top (which I find counter-intuitive and because the modal spans 100% of vertical space, they these load more buttons can only be clicked at the bottom and not in the center.

And the line wrapping doesn't work as well anymore.

I made some changes in 1.3.0

I’ve reworked the css and implemented some of your suggestions, albeit a bit differently.


Example for Facebook auth

Nice work done, Silvestre!
Can you provide some example for implementing Facebook auth through passport.js?
Used
feathers generate authentication
for authentication generation, what to do next?
Thanks!

Looks like main thing to do is to put
app.configure(authentication);
before
app.configure(middleware);
at app.js


Unable to save image

This issue is a:

Bug report

Expected behavior
To be able to right click and choose Save image as for an image wrapped in Zoom
Actual behavior
I could only save the page html
Steps to reproduce behavior
Use
<Zoom>
  <img src={source} />
</Zoom>

@johanbook Thank you for reporting this. In the current version, there is a button covering the image. I will make sure this is not the case when I can circle back to the next version. https://github.com/rpearce/image-zoom/pull/244 got put on hold because of some unavoidable issues that needed to be rethought, and we've just had a baby, so I'm not doing any coding at the moment.

Congratz to the baby @rpearce and thank you for this repo. If you point me in the right direction I make an attempt in creating a PR

@johanbook It's unfotunately a bit more complicated than a simple PR, because the entire mechanism for "zooming" needs to change. THANK YOU for your offer of a PR, though.

Similarly reported issue in https://github.com/rpearce/image-zoom/issues/271. I'll track it here.

Update on v5 FYI: https://github.com/rpearce/image-zoom/discussions/274

There was no way to do this in the current version without breaking things. Here's the latest update: https://github.com/rpearce/image-zoom/discussions/274#discussioncomment-1616865

Here's the latest update about the work being done that will resolve this: https://github.com/rpearce/react-medium-image-zoom/discussions/274#discussioncomment-2946565

If anyone finds some spare time and wants to give the latest build a whirl to try this out:
npm i --save<EMAIL_ADDRESS>
And, if you aren't already,
import Zoom from 'react-medium-image-zoom'
import 'react-medium-image-zoom/dist/styles.css'

// ... your other code

<Zoom>
  <MyImage />
</Zoom>

The updated v5-dev README is here, and there are some breaking changes to the extra options passed to be aware of, if you're using the options.
Thanks for your time!

Should be closed now with the release of 5.0.0


Add guidance/rules about including non-core/undefined topics in the TH tree

As I understand it so far,

All metadata records and notification messages for core and recommended data will include a topic hierarchy.
Level 9+ sub-categories will be defined by the appropriate community for core data.
Values for core data will be proposed to and maintained by TT-WISMD.
All records for core data will use this defined TH.
Records for recommended data will include as much as possible of the defined TH that applies.

The questions are:

Can the TH include undefined topics at the end of the tree? e.g. "origin/../.../../data/recommended/weather/space-based-observations/lightning" or e.g. "origin/../.../../data/recommended/weather/ship-based-observations"
A sub-category may change from recommended to core. It would be useful to have this already defined for consistency. Where does the TT-WISMD draw the line between managing potentially all sub-categories and only core-subcategories? Is it important to make this clear?
If we allow these undefined values, what happens to them in GB and GC?

These questions arose during the NWPMetadata workshop in January.

Some elements of answer. Just my opinion...

Can the TH include undefined topics at the end of the tree?
No. The level 9 (subcategories) and potentially below MUST be defined by the relevant experts from each domain. Something that is not agreed (and then, typically fast-tracked...) can't be used.

A sub-category may change from recommended to core.
The categories should be the same for core and recommended. The "tree" below these two options are the same. Typically, the current level 8 (categories) is the same for both.

A sub-category may change from recommended to core.
For me we shouldn't. Therefore, GB should discard unapproved sub-categories. The GC will never see them.

@golfvert Thank you for your thoughts.
I think there might be scenarios where the datatype in the recommended category do not have a Level 9+ sub-category to use. Should this be a concern?

TT-WISMD 2023-03-08

allowing arbitrary subtopics under the official WMO TH:

should be allowed (principle of extensibility)
subscriptions can be used for wildcarding (+, #)
still, may be heavy on users and broker
one resource/data granule, representation agnostic
what does GB need to validate?

core levels?
core + domain levels?
the bundle (programmatically) will provide what topics are in scope

allowing arbitrary subtopics under the official WMO TH
should be allowed (principle of extensibility)

How do we ensure, that two different centers do not use the same arbitrary topic for different things?
Consider

(Center-)Local extensions?
Register new topics at some registry (codes.wmo.int?)?

@kaiwirt If two centres use the same sub-topic "extension" somewhere below the levels that are officially recognized, it will not cause any problem, because the centre ID is high in the hierarchy, thus the whole topic will still be unique. e.g:
wis2/ita/meteoam/data/core/weather/surface-based-observations/synop/my_cool_sub-category
vs
wis2/deu/dwd/data/core/weather/surface-based-observations/synop/my_cool_sub-category

@kaiwirt @josusky the risk (or benefit?!) of allowing uncontrolled is extensions is when there is a wildcard in the TH query. However, I think we need to accept this risk in favor of keeping the management of THs reasonable.
wis2/+/+/data/core/weather/surface-based-observations/synop/my_cool_sub-category

How do we ensure, that two different centers do not use the same arbitrary topic for different things?
Consider

(Center-)Local extensions?
Register new topics at some registry (codes.wmo.int?)?

@kaiwirt the idea is that only the officially approved topics will be published to the WMO codes registry. The group or data provider who wants to use "uncontrolled" values need to consider proposing new topics to this TT or managing them seperately (if they are managed at all). I'm not in favor of prefixing the local extensions with "(Center)-" or anything else.

Before wondering if there is a risk of clash between two centres each deciding to publish messages under ..../my_cool_sub-category (without the same definition of what is cool), I still don't see what would be the benefit for our community to allow those free level(s) of topic hierarchy.
I guess there must be. I don't get them, though. I can't see a user able to know that topic a exists for centre A, b for B and so on and applying subscription filters on those... The main (sole?) purpose of the topic hierarchy is to get a logic categorisation of data, enabling filtering at the MQTT level.
Can we first discuss the use cases?

The point is that a certain number of levels (nine?) in the hierarchy will be standardized central by WMO, and several more sub-level will be added by domain specialists (dedicated expert teams). It is not clear how far this needs to go and how rigid it needs to be. So the use case for allowing "free" sub-topics, in somewhere like 12th level, is flexibility and lowering of the barrier for entry to WIS.

IMHO, the main benefit of agreeing on the topic hierarchy is to allow users to subscribe (and therefore filter) on topics they are (potentially) interested in. If a topic is created locally without any consistency between WIS2 Nodes, then having those "my_super_cool-topic" is missing the filtering goal.
So, as you point out, we have defined the first 9 levels as "global" for all WMO programs and then each domain experts will have to define the sublevels (the story doesn't tell how many).
With this, I would hope that 99% of the data/datasets/API will find the place where they belong.
For data (to make it shorter) that would not fit in one of the agreed place of the topic tree, then we may want to add an agreed default option where "unclassified" data would go. This would be a temporary (for me) solution while the domain experts agree on an extra topic in their branch.
At the moment, we haven't defined this "default" place. That might be missing...

Discussion transferred from email thread about topic hierarchy for SWIC (HKO) republishing warnings...
@armstrong >

To support the pilot of sending CAP messages aggregated in SWIC2 to WIS2, I have prepared the list of topic for existing Member countries/territories of which their CAPs are aggregated in SWIC2.  I should be grateful to have your comments.

@golfvert >

Thank you for this proposal.
I will just use one country as an example.
You propose: origin/a/wis2/xxa/swic/data/core/weather/warning-AFG
That part: origin/a/wis2/xxa/swic/data/core/weather  is OK for me and is consistent with the current agreed topic hierarchy.
However, according to https://github.com/wmo-im/wis2-topic-hierarchy/tree/main/topic-hierarchy the next level for warnings in the "weather" category (look at the weather.csv file) should be advisories-warnings.
So it would be origin/a/wis2/xxa/swic/data/core/weather/advisories-warnings
And then the next question is whether we want to add a sub topic including country names so that MQTT subscription might be limited to a particular country or group of countries.
We have started a similar discussion (without clear conclusion just yet) on whether the lower topic levels could be freely chosen by members to cover a particular situation.
SWIC case falls exactly in that situation, I think.
Look at (and contribute is you want) to this github discussion https://github.com/wmo-im/wis2-topic-hierarchy/issues/30
Therefore, we have, I think, two options:

All warnings in the origin/a/wis2/xxa/swic/data/core/weather/advisories-warnings  topic level
Add a sublevel using the country name to allow such a filter, for example, origin/a/wis2/xxa/swic/data/core/weather/advisories-warnings/afg
afg must be in lower case. We decided that topic hierarchy will be lower case only.
Then if not "afg" directly it could be country_afg or we could have yet another level with the continent so origin/a/wis2/xxa/swic/data/core/weather/advisories-warnings/asia/afg
So, filtering on a continent base would be easy. The is however a bit awkward as there is no approved 3-letter code for continent...

As we are in a pilot phase where the purpose is to experiment what has been agreed and testing solutions when not yet approved, I would propose to start with origin/a/wis2/xxa/swic/data/core/weather/advisories-warnings/afg
and see how it goes and if it works for us.
This is just my opinion though :)

And my comment ...
Armstrong – I think you’ve made a great start with your proposal. And I agree with Rémy’s amendments too.
Someone could subscribe to the
origin/a/wis2/xxa/swic/data/core/weather/advisories-warnings
topic and use client-side filtering if they wanted (e.g. looking at the spatial extent).
But being able to subscribe at the country level also seems useful, e.g.:
origin/a/wis2/xxa/swic/data/core/weather/advisories-warnings/gbr
Let’s try things out in the pilot and see what users prefer.

I had a hallway conversation with @golfvert and @6a6d74 a couple weeks ago and we decided that for now the topic hierarchy shall NOT be extensible for any extra categories that are not defined in the GitHub, because at this time it will establish a baseline approach and simplifies the complexity. This can be revisited after the pilot project is over.

Discussion transferred from email thread about topic hierarchy for SWIC (HKO) republishing warnings.

@6a6d74 can you open a new issue for this topic? It's tangential to this one and I'd like to keep track of it separately. Thanks!

Decision for team to approve:
For now, all values in the topic hierarchy need to be approved and available. It is not extensible with ad-hoc values as needed. This can be revisited later after the pilot phase if needed.

TT-WISMD: 2023-05-10

+1 for a fixed hierarchy
a WIS2 Node can always publish to a higher level topic

is this an issue?  Are data producers able to do this?  How can/will brokers deal with "dangling" data at higher level topics?
should we provide documentation on this?
do not allow higher than centre id?  Can only publish data AFTER level 9

consider issues of migration (from experimental to release)

ACTION: add text to require data to be published greater than level 9.
To be continued / implemented once https://github.com/wmo-im/wis2-topic-hierarchy/issues/38#issuecomment-1542209396 is implemented.

TT-WISMD 2023-09-12:

discussed in #35

TT-WISMD 2023-09-25

closing in lieu of #35


Master to Dev merge.

Thanks!

It’s broken though 🤣

But it broke everything 🙂

It’s broken though 🤣

Yes, whyyyy😭

I think you know more about whatever is going on in the Dev branch than I do.


Set up a common workflow to push a package to npm when we issue a release

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal
Why?
To release a new version of any package, we lose a somewhat significant amount of time (checking out locally, syncing, etc.)
An example of how simple things can be: https://github.com/gurgunday/html/blob/e60791ff5f557c9eb51c75f8f80008e74bfa3ced/.github/workflows/npm-publish.yml
And the action runs automatically after a release is issued:
https://github.com/gurgunday/html/releases/tag/v7.0.0
https://github.com/gurgunday/html/actions/runs/6941110154
We just need to create an automation token on NPM and add it to GitHub
Another benefit: it also signs the commit during the workflow, so if we have any paranoid users, they can verify that the release matches to what they see on GitHub
What do you all think?
Motivation
No response
Example
No response

This is a complicated task. The OpenJSF team is going to provide some solutions around this.

Duplicates https://github.com/fastify/fastify/issues/2748
Anyway I talked about it with @mcollina and he told me that he will show us a demo about the process he would like to suggest.
The constraints I collected are:

one NPM scoped token per repo (not a GOD MASTER TOKEN than can release everything)
benefit from the npm provenance**
avoid manual steps***
bullet proof security

**) I think npm misses a feature where you force that a package MUST have a provenance from XYZ provider to be published TBH. In this case, even if the GOD MASTER TOKEN would be leaked, it would be almost useless.
***) I think the only bullet proof security is the OTP, but we don't want manual steps... so I'm a bit confused about these requirements. For this reason I'm waiting the demo

Once we have a token with the right permissions, setting up automated publish is a superset of
https://github.com/mcollina/test-publish/blob/main/.github/workflows/publish.yml
and
https://github.com/platformatic/platformatic/blob/main/.github/workflows/publish-releases.yml
Note the use of environment: main in https://github.com/platformatic/platformatic/blob/main/.github/workflows/publish-releases.yml#L17 allows us to limit the secrets to only the main branch of a repository, essentially making it secure.
You can read more about environments at https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment.

This is a complicated task. The OpenJSF team is going to provide some solutions around this.

Has there been any update on this? Been planning to set this up for another OpenJSF-project (Mocha) so I have been watching this thread

It is blocked I believe
https://github.com/fastify/fastify/pull/5386


Image and text difference

The text says "select New > Semantic model" while the picture shows "select New > Dataset"

@huiwenkong - Another way to report issues with an article is to select the No button at the bottom of the page. You can describe the issue in your feedback.

@maggiesMSFT - This appears to be an issue report rather than a change suggestion. You might want to close this PR and fix the issue via the private repo.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks! This error is fixed.


Options without configuring loader?

In the old version, I did something like this when importing the image:
import topImage from 'responsive-loader!./images/contact-us.jpg';

And then had a section with options in my webpack 2 config:
new webpack.LoaderOptionsPlugin({
	options: {
		responsiveLoader: {
			sizes: [1000, 500, 1500],
			placeholder: true,
			placeholderSize: 20,
			quality: 75,
			name: 'images/[name]-[sha512:hash:base64:5]-[width].',
		},
	},
}),

But with v1.x there are only examples specifying options when responsive-loader is configured as a loader? Is there any other way to specify default settings (without LoaderOptionsPlugin since that will be deprecated eventually)?

I'm not sure that's possible. Best is to properly configure the loader.
One useful trick is to match the loader on the resourceQuery part, e.g.
module: {
  rules: [
      {
        test: /\.(png|jpg)$/,
+       resourceQuery: /responsive/,
        loader: 'responsive-loader',
        options: {
          // ...
        }
      }
  ]
}

Then you can import responsive images like this:
import topImage from './images/contact-us.jpg?responsive';

That's a nice trick, thanks, will try that :)


describe network configuration setup in OpenEmbedded user manual

For meta-ros, the user must set up the network configuration. We would like to have a section in the OpenEmbedded user manual that describes how to do this. We can then refer to this section.
This was discussed in the abandoned pull request #258, which provides the minimal technical solution as commits.

DISTRO = ros1 or ros2 images now include connman, which means that Ethernet networking is automatically started.
@bulwahn < Can this issue be colsed?

"Silence implies consent" (see http://wiki.c2.com/?SilenceImpliesConsent).


test: update k8s versions to 1.7.16, 1.8.13, 1.9.8, 1.10.3 and 1.11.0-beta.0

Signed-off-by: André Martins<EMAIL_ADDRESS>

test-me-please

test-missed-k8s

test-me-please

test-missed-k8s

test-missed-k8s

test-me-please

test-missed-k8s

test-missed-k8s

test-missed-k8s

test-missed-k8s

test-missed-k8s

test-me-please

test-missed-k8s

possible flake https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/3439/

test-me-please

test-me-please

possible flake https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/3445/

test-me-please

test-missed-k8s

test-me-please

test-missed-k8s

test-me-please

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/3465/

test-me-please

test-me-please

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/257/

test-me-please

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/259/

test-missed-k8s


Paginator and Bootstrap 4

This is a "so we don't forget" issue.
Bootstrap 4 will likely change the expected markup for the pagination component, requiring additional classes added to child elements. There is no known release date for BS 4, so I'm not sure what Laravel version this would apply to :).
Bootstrap 3 expected markup:

            Page number

    ...

Bootstrap 4 Alpha 2 markup:

           Page number

    ...

Already possible. Please ask on the forums.

Not sure why this was closed. I wasn't indicating that this was a current issue, but something that will need to be dealt with in the future.

It has already been dealt with in the laravel core. I can't find the original issues though to link you to them.

Ok, thanks for your effort!


How to disable global middleward for some routers?

Is there any way to disable global middleware for certain routers?
I have a global middleware for auth,and use it like this:
        server := rest.MustNewServer(config.SysCfg.RestConf)
	defer server.Stop()
	server.Use(middleware.NewAuthMiddleware().Handle)

But I have some routes that don't want to use this middleware,so what should i do..

Ok,thanks for your advise, it is helpful to me.


Proposed Fix for Error when replacing swagger-tools with oas-tools #106

If x-swagger-router-controller appears in path but not in method, copy it to each method for that path.

I also set the path on the req.swagger.params to requestedSpecPath because my code needed it, and it was hardcoded to '/some/path'.  Comment says it is not used in oas-tools, so it should not interfere.


Possible race on ingress programming

Make sure that iptables operations on ingress
are serialized.
Before 2 racing routines trying to create the ingress chain
were allowed and one was failing reporting the chain as
already existing.
The lock guarantees that this condition does not happen anymore
Signed-off-by: Flavio Crisciani<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3931ba4). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #2178   +/-   ##
=========================================
  Coverage          ?   40.57%
=========================================
  Files             ?      139
  Lines             ?    22484
  Branches          ?        0
=========================================
  Hits              ?     9123
  Misses            ?    12028
  Partials          ?     1333

Impacted Files
Coverage Δ

service_linux.go
3.2% <0%> (ø)

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 3931ba4...7bb62d0. Read the comment docs.


Deprecate LessThan, GreaterThan and Between validators

Q
A

Documentation
yes

Description
These validators are deprecated in favour of the NumberComparison and DateComparison validators
See:

#272
#274
#275

Depends on #274 and #275 because the docs link to pages that don't yet exist.

Thanks @gsteel!


Add placeholder for dynamo visibilityCRUD methods

What changed?

Add placeholder for dynamo visibilityCRUD methods

Why?

Otherwise there''ll be a compile error for var _ nosqlplugin.DB = (*ddb)(nil) on L45 in dynamodb/db.go

How did you test it?
No build error.

Potential risks
N/A

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 236edea6-6285-4b1d-a02d-f3e6a260eb34

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
34 unchanged lines in 9 files lost coverage.
Overall coverage decreased (-0.007%) to 60.155%

Files with Coverage Reduction
New Missed Lines
%

service/history/queue/timer_queue_processor_base.go
1
78.6%

common/membership/rpServiceResolver.go
2
73.58%

common/task/weightedRoundRobinTaskScheduler.go
2
88.6%

service/history/queue/timer_queue_processor.go
2
58.77%

service/history/task/transfer_active_task_executor.go
2
69.31%

service/matching/taskListManager.go
2
74.72%

common/task/fifoTaskScheduler.go
3
84.54%

service/history/queue/processor_base.go
7
61.82%

common/persistence/cassandra/cassandraPersistenceUtil.go
13
88.15%

Totals

Change from base Build 0070ea5b-16ac-4631-a33f-b54e7d3684b0:
-0.007%

Covered Lines:
88650

Relevant Lines:
147369

💛  - Coveralls


[BUG] Insert video popover form validation is not enough permissive (width and height)

I'm submitting a

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Enhancement
[ ] Feature request
[ ] Documentation issue or request

Description
When adding a video on Insert Video Popover the validation form does not allow more than one number for width or height values.
Valid form:

Invalid form:

Version Information
ngx-editor: 4.1.0
angular: 8.2.14

Browser

[x] Chrome - 86.0.4240.183 (only one tested)
[ ] Mozilla Firefox - x.x.x
[ ] Opera - x.x.x
[ ] Microsoft Edge - x.x.x

Fixed in v4.1.1


Error with conda environment creation in README

In README.md:
This incorrectly attempts to build the conda environment.
conda create --name emd --file environment.yml
Change to this to fix.
conda create -f environment.yml
FIXED VERSION:
README.md

Solved with: "fix conda create bug #9"


Add a DocumentSymbolProvider for .gjs and .gts files

VS Code uses this information for multiple features (and I assume other editors will have equivalents):

go to symbol
rename symbol (F2)
entries in the "outline view"
breadcrumbs
... (?)

ELS already supports this for .js and .hbs files.
Original issue: https://github.com/lifeart/ember-language-server/issues/420

We could introduce Rename provider https://code.visualstudio.com/api/references/vscode-api#RenameProvider


Packaged .zxp file includes all the VUE panels...Why?

Hello! When I run npm run sign to make the .zxp file, it create the file, but when I open the .zxp file, I can see the "src" folder with all of my created .vue panels and the index-dev.html. Are these files supposed to be included in the .zxp file? I know maybe "src\host" folder should be included since my .jsx files are in there, but all the other non-necessary files are included in the .zxp file. Is there a way to just include the necessary files needed to make the panel work?
Thanks!

You'd add src to your ./certignore file, but you need to take care for scripts and place them in public or another location.

Thanks for the reply!
A few more questions:

What location would be best to put them in?
I can add src to ./certignore, but when I sign the app, how can I build it so it will work. Sorry, I'm having trouble understanding how it's going to work.


Philips Eyecare 2: this.setModes is not a function

There seems to be a bug in the driver for the Philips Eyecare 2 lamp. This code generates the following error.
const miio = require('./node_modules/miio/lib');

// Create a new device over the given address
miio.device({
	address: '<IP_ADDRESS>',
  token: 'xxxxxxxxxxxxxxxxxxxxxxx'
}).then(device => {
  const getData = async () => {
      try {
          const power = await device.power();
          const brightness = await device.brightness()
          const mode = await device.mode();
          const eyecare = await device.eyeCareMode();

          let result = {
              onoff: power,
              brightness: brightness,
              mode: mode,
              eyecare: eyecare
          }

          console.log(result)
      } catch (error) {
          console.log(error);
      }
  }
  getData();
}).catch(err => console.log('Error occurred:', err));

pi@iobroker:~ $ node miio.js
Error occurred: { TypeError: this.setModes is not a function
at new EyecareLamp2 (/usr/lib/node_modules/miio/lib/devices/eyecare-lamp2.js:68:8)
at network.findDeviceViaAddress.then.device (/usr/lib/node_modules/miio/lib/connectToDevice.js:25:12)
at device: null }

Same here

Still no solution :-(


Enhance/sangshuduo/td 12725 improve ci

Codecov Report

Merging #96 (e164b2f) into develop (f6363ae) will decrease coverage by 1.39%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop      #96      +/-   ##
===========================================
- Coverage    35.95%   34.56%   -1.40%
===========================================
  Files           10       10
  Lines         7862     7928      +66
  Branches       405      405
===========================================
- Hits          2827     2740      -87
- Misses        4909     5062     +153
  Partials       126      126

Impacted Files
Coverage Δ

TDengine/src/kit/taos-tools/src/taosdump.c
52.95% <0.00%> (-4.34%)
:arrow_down:

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 f6363ae...e164b2f. Read the comment docs.


The whole thing just pinwheels endlessly.

Version
v1.4.4
Areas for Improvement

[ ] UI/UX
[ ] Onboarding
[ ] Docs
[ ] Chat
[ ] Commands
[ ] Context
[ ] Response Quality
[ ] Other

What needs to be improved? Please describe how this affects the user experience.
I couldn't even get it to respond to basic requests. After a few chats, it just hung endlessly and never came back to life. The code itself also wasn't terribly helpful. Rather than helping to spot potential areas for review, it just tried to refactor the code but did so in also unhelpful and broken ways.
Describe the solution you'd like to see
.
Describe any alternatives that could be considered
No response
Additional context
No response

+1


Hostname support for StaticRoute CRDs

Background
Check if it's feasible and easy to implement to use hostnames instead of IPs for StaticRoute CRDs.

+1 here


Provide static version of "win" anaimation

On KaiOS, it shows us as just a one line turning (assuming FF48 don't support the CSS animation we are doing?)
This is also pretty motion heavy animation, so when user's preference is set to no-motion, it should display static image. (this also solves KaiOS issue because isFeaturePhone is always no-ananimation)

closed via #267


"Checking in" loads a blank modal

@afixoftrix

This modal needs to take up the whole view on desktop and mobile like the design below:

And like the actual Tripetto survey: https://tripetto.app/collect/LJ9GM8MW3X
The reason is we want the user's full attention on completing the survey, not wondering what the stuff is behind it.

@BrennenHodge can you elaborate on "like the actual Trepetto"? I thought the plan was to embed Tripetto right into the site?

Also based on what @afixoftrix wrote in the PR for the token fix, I think this issue might be for me instead:

We need to make sure the .env file on the server hosting the app has the correct variable and value.

When I did the last deploy I definitely didn't create a .env file so one may not be present on the server (or is present without the right variables).

@BrennenHodge @afixoftrix yep I just ran another deploy after creating a .env file with this value, form is no longer blank (it's the Tripetto).

Oh sry, forgot about the fullscreen part of this ticket, will re-open so we can tackle that.

@BrennenHodge can you elaborate on "like the actual Trepetto"? I thought the plan was to embed Tripetto right into the site?

The link I referenced is full screen and has the form centered.
The "large" modal size mentioned in #28 will work, but the form needs to be centered horizontally.


Performance ideas

make node type a char1
make linked list in type cache (to_abap)

make node type a char1

Does not give any improvement, In opposite - it's slightly slower. Not sure I understand why. But seems that abap string comparison is efficient enough compared to one char comparison.


Add better support for cargo-binstall

Changes in this pull request
Since users have had some issues installing from source due to building things like OpenSSL manually, this uses cargo binstall to allow users to download and install c2patool more easily using prebuilt binaries.
The main advantage with starting with this over Homebrew is that this supports all platforms, where Homebrew only supports macOS.
Checklist

[ ] This PR represents a single feature, fix, or change.
[ ] All applicable changes have been documented.
[ ] Any TO DO items (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 44.18%. Comparing base (1f28705) to head (10e3744).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #177   +/-   ##
=======================================
  Coverage   44.18%   44.18%
=======================================
  Files           7        7
  Lines         722      722
=======================================
  Hits          319      319
  Misses        403      403

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Android] Fix the display with overlayed multiple XWalkViews.

When multiple XWalkViews were set to overlay,
XWalkView.setVisibility(View.INVISIBLE) does not work, that is current
XWalkView was always showing. This patch is to fix this issue.
For the usage, please refer to the
sample:MultiXWalkViewOverlayActivity.java.
BUG=XWALK-5064
(cherry picked from commit e1199ea11b8819203af764192c21f70890246421)

@rakuco Please review and merge, thanks.


Tenant Allow/Block List link doesn't work

https://protection.office.com/tenantAllowBlockList doesnt link to anything, and the powershell command is not there.

update or remove the documentation

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

ID: 94b60171-271c-fb93-88bf-0cd9db014541
Version Independent ID: e9cd207e-0d4c-e268-dd3a-701e1e2df658
Content: Manage your allowed and blocked URLs in the Tenant Allow/Block List - Office 365
Content Source: microsoft-365/security/office-365-security/tenant-allow-block-list.md
Service: o365-seccomp
GitHub Login: @chrisda
Microsoft Alias: chrisda

@SquirrelAssassin, as it states at the top of the topic:

[!NOTE]
The features described in this topic are in Preview, are subject to change, and are not available in all organizations.

If the link doesn't work for you, then you likely aren't part of the Preview.

Use a different area of documentation for prod and preview documentation, y’all gotta start thinking more.

Let me re iterate a consulting company Microsoft owns created tickets on our side about permissions out side did not give them and wasted life hours.  Use a preview documentation url.  If you don’t have (a site to show) don’t show any site at all. Once it hits google it’s scripture and obviously it already burned real human life hours.  Be responsible for what you show and how you show it.


[Feature Request]: Implement getSessionAndUser() for SQLite

Description
The SQLite adapter currently does not implement getSessionAndUser, requiring two round trips to get get a user and session.  I don't see anything query wise that would stop this from being implemented, and it would improve performance, especially for LibSQL/Turso and D1.
I would be willing to implement the feature request.

All SQL adapters require 2 round trips since we can't differentiate between a custom field in the user and the session table. But, if you can make it so those 2 queries can be made in "parallel" like in the MySQL adapter, that'd be helpful :D (don't remember why I didn't implement it).

Wouldn't UNION ALL work to get both rows separately?
Also, what is stopping us from running the queries in parallel in the session handler itself? Promise.allResolved should work for all dbs. Then we can just use getSessionAndUser for dbs where one query can get both.

Wouldn't UNION ALL work to get both rows separately?

I don't think so? The big issue is that we can't differentiate between the user and session table.

Also, what is stopping us from running the queries in parallel in the session handler itself

Like I said, I don't remember why I didn't implement it

just played a little with the code, maybe not the most performant
            getSessionAndUser: async (sessionId) => {
                const resultStatement = db
                    .prepare(`
                        SELECT
                            u.id as __user_id, u.*,
                            s.id as __session_id, s.*
                        FROM ${ESCAPED_USER_TABLE_NAME} as u
                        INNER JOIN ${ESCAPED_SESSION_TABLE_NAME} as s
                            ON s.user_id = u.id
                        WHERE s.id = ?
                    `);
                const cols = resultStatement.columns();
                const result = resultStatement.get(sessionId);
                let userResult = null;
                let sessionResult = null;
                if (result) {
                    // 'id' col of session is overwritten
                    const sid_idx = cols.findIndex(element => element.name == '__session_id');
                    const colsUser = cols.slice(
                        0,
                        sid_idx
                    );
                    const colsSession = cols.slice(
                        sid_idx,
                        cols.length
                    );
                    userResult = Object.fromEntries(
                        colsUser.map((elem) => [elem.name, result[elem.name]])
                    );
                    userResult.id = userResult.__user_id;
                    delete userResult['__user_id'];
                    sessionResult = Object.fromEntries(
                        colsSession.map((elem) => [elem.name, result[elem.name]])
                    );
                    sessionResult.id = sessionResult.__session_id;
                    delete sessionResult['__session_id'];
                }
                return [sessionResult, userResult];
            },

This is fixed in v3, and I'm not planning to add more features to v2


[WIP] Fuse POC

Hack in Fuse Tooling Installation.

Current coverage is 76.35% (diff: 70.00%)

Merging #508 into master will decrease coverage by 3.93%

@@             master       #508   diff @@
==========================================
  Files            25         25
  Lines          2324       2415    +91
  Methods         398        396     -2
  Messages          0          0
  Branches        209        201     -8
==========================================
- Hits           1866       1844    -22
- Misses          458        571   +113
  Partials          0          0

Powered by Codecov. Last update fa87bbb...37727a4

replaced with https://github.com/redhat-developer-tooling/developer-platform-install/pull/751