Update the matlab visualizer to the iDynTree one

This PR introduces the visualization based on the iDynTree visualizer bindings.
To use it, matlab should be run with export MESA_LOADER_DRIVER_OVVERRIDE=i965.
There is also a condition on the maximum fps of the visualization (default 25 fps). In this way, the visualization should not be a bottleneck.
It should not require any modification in the existing models.
I don't know if export MESA_LOADER_DRIVER_OVVERRIDE=i965 is too extreme as a requirement.
In this case, feel free to drop away this PR! :)

Let's call  them C++-Irrlicht-Visualizer and Pure-Matlab-Visualizer, otherwise we start getting confused.
Is this PR removing the Pure-Matlab-Visualizer option and force users to use  C++-Irrlicht-Visualizer  ? In that case, that may be a bit too extreme as C++-Irrlicht-Visualizer does not work in some scenarios, for example macOS (see https://github.com/robotology/idyntree/issues/221) or on MATLAB Online. Can we leave the choice of the visualizer as an option?

To use it, matlab should be run with export MESA_LOADER_DRIVER_OVVERRIDE=i965.

This is only true on Linux and with Intel cards, I don't think it is true in general.

Let's call  them C++-Irrlicht-Visualizer and Pure-Matlab-Visualizer, otherwise we start getting confused.
Is this PR removing the Pure-Matlab-Visualizer option and force users to use  C++-Irrlicht-Visualizer  ? In that case, that may be a bit too extreme as C++-Irrlicht-Visualizer does not work in some scenarios, for example macOS (see https://github.com/robotology/idyntree/issues/221) or on MATLAB Online. Can we leave the choice of the visualizer as an option?

Yes, I agree! This PR as it is removes the Pure-Matlab-Visualizer but it is more to ask which is the best solution between totally substituting or just adding another option.

Let's call  them C++-Irrlicht-Visualizer and Pure-Matlab-Visualizer, otherwise we start getting confused.
Is this PR removing the Pure-Matlab-Visualizer option and force users to use  C++-Irrlicht-Visualizer  ? In that case, that may be a bit too extreme as C++-Irrlicht-Visualizer does not work in some scenarios, for example macOS (see robotology/idyntree#221) or on MATLAB Online. Can we leave the choice of the visualizer as an option?

Yes, I agree! This PR as it is removes the Pure-Matlab-Visualizer but it is more to ask which is the best solution between totally substituting or just adding another option.

Ack! I think @CarlottaSartore may have also something to say on this, but I guess having the two options probably make sense.

I will add an option in the mask in order to choose the preferred visualizer then!

Adding an option will break all the simulink models using the Matlab-visualizer since I should add a mask to the block.
I just created a new matlab system and added a new element in the simulink library. I believe it is the cleanest solution, for now.

Adding an option will break all the simulink models using the Matlab-visualizer since I should add a mask to the block.
I just created a new matlab system and added a new element in the simulink library. I believe it is the cleanest solution, for now.

Good point!

Some tests
I've replaced the Pure-Matlab-Visualizer with the C++-Irrlicht-Visualizer in the model test_matlab_system_2020b.mdl, and although it compiled, the simulation run fails immediately with the following error:

--------------------------------------------------------------------------------
           Illegal instruction detected at 2021-05-27 11:55:18 +0200
--------------------------------------------------------------------------------

Configuration:
  Crash Decoding           : Disabled - No sandbox or build area path
  Crash Mode               : continue (default)
  Default Encoding         : UTF-8
  Deployed                 : false
  Graphics Driver          : Unknown hardware
  Java Version             : Java 1.8.0_202-b08 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
  MATLAB Architecture      : maci64
  MATLAB Entitlement ID    : 6829974
  MATLAB Root              : /Applications/MATLAB_R2020b.app
  MATLAB Version           : <IP_ADDRESS>0001 (R2020b) Update 4
  OpenGL                   : hardware
  Operating System         : Mac OS Version 10.15.7 (Build 19H1030)
  Process ID               : 46340
  Processor ID             : x86 Family 6 Model 158 Stepping 13, GenuineIntel
  Session Key              : eb5c8402-12eb-4a1b-b074-48a00cfb77ce
  Window System            : Quartz

Fault Count: 1

Abnormal termination:
Illegal instruction

Current Thread: 'MCR 0 interpreter thread' id 0x70000fd2a000

Register State (from fault):
  RAX = 00007f81d5e06200  RBX = 00007f815b595060
  RCX = a8f95d9d29da008e  RDX =<PHONE_NUMBER>000101
  RSP = 000070000fd1fdc0  RBP = 000070000fd1fdd0
  RSI =<PHONE_NUMBER>0065a5  RDI = 000070000fd1f960

   R8 =<PHONE_NUMBER>006400   R9 = 00007f81d5e0c7a5
  R10 =<PHONE_NUMBER>0001a5  R11 = 000070000fd1f7aa
  R12 = 00007f8236795da0  R13 = 00007f8159953c40
  R14 = 00007fff70c98800  R15 = 00007f8237185d60

  RIP = 00007fff35400373  RFL =<PHONE_NUMBER>010202

   CS =<PHONE_NUMBER>00002b   FS =<PHONE_NUMBER>000000   GS =<PHONE_NUMBER>000000

Stack Trace (from fault):
[  0] 0x0000000108d3f9e9 /Applications/MATLAB_R2020b.app/bin/maci64/libmwfl.dylib+00006633 _ZN10foundation4core4diag15stacktrace_base7captureERKNS1_14thread_contextEm+00000057
[  1] 0x0000000108d452fa /Applications/MATLAB_R2020b.app/bin/maci64/libmwfl.dylib+00029434 _ZN10foundation4core4test17terminate_handledERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEE+00011546
[  2] 0x0000000108d42325 /Applications/MATLAB_R2020b.app/bin/maci64/libmwfl.dylib+00017189 _ZN10foundation4core4diag13terminate_logEPKcPK17__darwin_ucontext+00000149
[  3] 0x0000000110531d8b /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcr.dylib+00560523 _Z19mnPrintErrorMessageRKNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEE+00012427
[  4] 0x000000011052f81d /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcr.dylib+00550941 _Z19mnPrintErrorMessageRKNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEE+00002845
[  5] 0x000000011052d250 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcr.dylib+00541264 mnFatalSignalHandler+00000144
[  6] 0x00007fff720465fd           /usr/lib/system/libsystem_platform.dylib+00013821 _sigtramp+00000029
[  7] 0x00007f81f63af620                                   <unknown-module>+00000000
[  8] 0x00007fff35400256 /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit+04338262 -[NSApplication reportException:]+00000901
[  9] 0x00007fff3500f308 /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit+00205576 -[NSApplication finishLaunching]+00003049
[ 10] 0x0000000190137289 /Users/nunoguedelha/dev/superbuild-soft-eng/robotology-superbuild/build/install/lib/libidyntree-visualization.dylib+02179721 _ZN3irr16CIrrDeviceMacOSXC1ERKNS_27SIrrlichtCreationParametersE+00000457
[ 11] 0x00000001900cdb8e /Users/nunoguedelha/dev/superbuild-soft-eng/robotology-superbuild/build/install/lib/libidyntree-visualization.dylib+01747854 createDeviceEx+00000046
[ 12] 0x000000018ff2852d /Users/nunoguedelha/dev/superbuild-soft-eng/robotology-superbuild/build/install/lib/libidyntree-visualization.dylib+00021805 _ZN8iDynTree10Visualizer4initERKNS_17VisualizerOptionsE+00000317
[ 13] 0x000000018fc5346a /Users/nunoguedelha/dev/superbuild-soft-eng/robotology-superbuild/build/install/mex/iDynTreeMEX.mexmaci64+01070186 _Z21_wrap_Visualizer_initiPP11mxArray_tagiS1_+00000170
[ 14] 0x000000018fc70ec0 /Users/nunoguedelha/dev/superbuild-soft-eng/robotology-superbuild/build/install/mex/iDynTreeMEX.mexmaci64+01191616 mexFunction+00026672
[ 15] 0x00000001110026b7 /Applications/MATLAB_R2020b.app/bin/maci64/libmex.dylib+00394935 _ZNK18C_DispatchStrategy8dispatchEiPP11mxArray_tagiS2_+00000279
[ 16] 0x00000001110025f0 /Applications/MATLAB_R2020b.app/bin/maci64/libmex.dylib+00394736 _ZNK18C_DispatchStrategy8dispatchEiPP11mxArray_tagiS2_+00000080
[ 17] 0x0000000111002ffd /Applications/MATLAB_R2020b.app/bin/maci64/libmex.dylib+00397309 _ZNK24SCCompatDispatchStrategy8dispatchEiPP11mxArray_tagiS2_+00000061
[ 18] 0x000000011100245c /Applications/MATLAB_R2020b.app/bin/maci64/libmex.dylib+00394332 _ZN7Mfh_mex30dispatch_file_with_protectionsEiPP11mxArray_tagiS2_+00000428
[ 19] 0x0000000110fe6f1f /Applications/MATLAB_R2020b.app/bin/maci64/libmex.dylib+00282399 _ZN7Mfh_mex13dispatch_fileEiPP11mxArray_tagiS2_+00000159
[ 20] 0x00000001106838de /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00665822 _ZN8Mfh_file20dispatch_file_commonEMS_FviPP11mxArray_tagiS2_EiS2_iS2_+00000142
[ 21] 0x00000001106840fb /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00667899 _ZN8Mfh_file8dispatchEiPNSt3__110unique_ptrI11mxArray_tagN6matrix6detail17mxDestroy_deleterEEEiPPS2_+00000379
[ 22] 0x00000001116f8489 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+06591625 _ZN9MathWorks3lxe17LxeDispatcherImpl12apply_handleEPNS0_29DispatcherFunctionHandleTokenEmPNS0_6xvalueEmPKS4_RKNS0_12LxeTypesBaseENS0_9ApplyTypeE+00001337
[ 23] 0x000000011182d814 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+07858196 _ZN9MathWorks3lxe20apply_handle_nargoutEPvNS_2ts4TypeEPKvS1_S1_+00000404
[ 24] 0x00000001117a93fe /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+07316478 _ZN9MathWorks3lxe38cpp_primitive_template_fn_with_contextIXadL_ZNS0_20apply_handle_nargoutEPvNS_2ts4TypeEPKvS2_S2_EEEEbS2_S4_S6_S2_S2_+00000014
[ 25] 0x000000011126f0ab /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01835179 _ZN9MathWorks3lxe13IrInterpreter17ApplyCppPrimitiveEPN2ir4termES4_RKNS_2ts4TypeES8_+00000603
[ 26] 0x000000011126ddaf /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01830319 _ZN9MathWorks3lxe13IrInterpreter31process_application_of_constantEPN2ir4termE+00003951
[ 27] 0x000000011126b938 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01820984 _ZN9MathWorks3lxe13IrInterpreter13applyConstantEPN2ir4termE+00000072
[ 28] 0x00000001112670d8 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01802456 _ZN9MathWorks3lxe12IRTreeWalker11getNextIRPCENS0_9irpc_typeE+00000216
[ 29] 0x000000011126b6b7 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01820343 _ZN9MathWorks3lxe13IrInterpreter9tree_walkERKNS0_9irpc_typeES4_+00000215
[ 30] 0x000000011126b58c /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01820044 _ZN9MathWorks3lxe13IrInterpreter9InterpretEv+00000108
[ 31] 0x00000001113bb430 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03195952 _ZN9MathWorks3lxe15ExecutionDriver9ThreadRunEv+00005520
[ 32] 0x00000001113bffad /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03215277 _ZN9MathWorks3lxe12IrEngineImpl5ApplyERKN2ir4termEPvS6_+00000301
[ 33] 0x00000001115f3df8 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+05524984 _ZN9MathWorks3lxe17IrEngineDecorator5ApplyERKN2ir4termEPvS6_+00000152
[ 34] 0x00000001116ed70f /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+06547215 _ZN9MathWorks3lxe27FileBasedMatlabCodeFunction16DispatchFunctionEiPP11mxArray_tagiS4_+00001215
[ 35] 0x00000001116ee0c2 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+06549698 _ZN9MathWorks3lxe27FileBasedMatlabCodeFunction12DispatchFileEiPP11mxArray_tagiS4_b+00000178
[ 36] 0x00000001106838de /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00665822 _ZN8Mfh_file20dispatch_file_commonEMS_FviPP11mxArray_tagiS2_EiS2_iS2_+00000142
[ 37] 0x0000000110683a24 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00666148 _ZN8Mfh_file8dispatchEiPP11mxArray_tagiS2_+00000228
[ 38] 0x000000011cea6601 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+02479617 _ZN4mcos26invokeMMethodWithReuseFlagEPNS_13COSMethodInfoEbPKNS_9COSClientERiPNS_8COSValueEiPKS6_+00002177
[ 39] 0x000000011ce2b397 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+01975191 _ZN24OpaqueMethodCallMetaData11callMMethodEPN4mcos13COSMethodInfoEPP11mxArray_tagPKNS0_9COSClientEb+00000567
[ 40] 0x000000011ce2fac3 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+01993411 _ZN24OpaqueMethodCallMetaData23callMethodOrConstructorEP11mxArray_tagbiPS1_iPPKS0_bPKN4mcos9COSClientEPS9_PPNS6_13COSMethodInfoEbb+00000291
[ 41] 0x000000011ce31a20 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+02001440 _Z19omIsPackageFunctionPK11mxArray_tag+00007168
[ 42] 0x000000011ce2cffa /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+01982458 _Z18mcosCallMethodImplN4mcos15COSInternedBaseINS_8internal13IdEmptyPolicyEEES3_PKNS_9COSClientEiPP11mxArray_tagiPPKS7_bb+00000186
[ 43] 0x000000011ce2da1f /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+01985055 _ZN4mcos4impl12omCallMethodENS_15COSInternedBaseINS_8internal13IdEmptyPolicyEEES4_PKNS_9COSClientEiPP11mxArray_tagiPPKS8_b+00000031
[ 44] 0x000000011cee94d5 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+02753749 _ZN4mcos4impl18omDirectCallMethodERKNS_15COSInternedBaseINS_8internal13IdEmptyPolicyEEES6_S6_iPP11mxArray_tagiPPKS7_+00000101
[ 45] 0x000000011cf1ff7b /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+02977659 _ZN4mcos7plugins13PluginManagerD1Ev+00001963
[ 46] 0x000000010b99a22b /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos.dylib+00053803 _Z18omDirectCallMethodRKN4mcos15COSInternedBaseINS_8internal13IdEmptyPolicyEEES5_S5_iPP11mxArray_tagiPPKS6_+00000043
[ 47] 0x0000000115028531 /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+00304433 _ZNK9MathWorks3lxe26MatrixModuleImplementation23CreateStaticMethodArrayEPKc+00012673
[ 48] 0x00000001150d3c4c /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+01006668 _ZN9MathWorks3lxe32count_ldot_guarantee_id_no_checkEPvNS_2ts4TypeEPKvRNS0_15ILxeEnvironmentE+00015228
[ 49] 0x000000011503d343 /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+00389955 _ZN9MathWorks3lxelsERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEERKNS0_10MultiValueE+00003875
[ 50] 0x000000011503d343 /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+00389955 _ZN9MathWorks3lxelsERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEERKNS0_10MultiValueE+00003875
[ 51] 0x0000000115063083 /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+00544899 _ZN9MathWorks3lxe21at_paren_pointer_mcosEPvNS_2ts4TypeEPKvS1_S1_+00006355
[ 52] 0x000000011500d4ba /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+00193722 _ZN9MathWorks3lxe17at_rparen_nargoutEPvNS_2ts4TypeEPKvS1_S1_+00000762
[ 53] 0x00000001117a83ce /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+07312334 _ZN9MathWorks3lxe38cpp_primitive_template_fn_with_contextIXadL_ZNS0_17at_rparen_nargoutEPvNS_2ts4TypeEPKvS2_S2_EEEEbS2_S4_S6_S2_S2_+00000014
[ 54] 0x000000011126f0ab /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01835179 _ZN9MathWorks3lxe13IrInterpreter17ApplyCppPrimitiveEPN2ir4termES4_RKNS_2ts4TypeES8_+00000603
[ 55] 0x000000011126ddaf /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01830319 _ZN9MathWorks3lxe13IrInterpreter31process_application_of_constantEPN2ir4termE+00003951
[ 56] 0x000000011126b938 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01820984 _ZN9MathWorks3lxe13IrInterpreter13applyConstantEPN2ir4termE+00000072
[ 57] 0x00000001112670d8 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01802456 _ZN9MathWorks3lxe12IRTreeWalker11getNextIRPCENS0_9irpc_typeE+00000216
[ 58] 0x000000011126b6b7 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01820343 _ZN9MathWorks3lxe13IrInterpreter9tree_walkERKNS0_9irpc_typeES4_+00000215
[ 59] 0x000000011126b58c /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+01820044 _ZN9MathWorks3lxe13IrInterpreter9InterpretEv+00000108
[ 60] 0x00000001113bb430 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03195952 _ZN9MathWorks3lxe15ExecutionDriver9ThreadRunEv+00005520
[ 61] 0x00000001113bffad /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03215277 _ZN9MathWorks3lxe12IrEngineImpl5ApplyERKN2ir4termEPvS6_+00000301
[ 62] 0x00000001115f3df8 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+05524984 _ZN9MathWorks3lxe17IrEngineDecorator5ApplyERKN2ir4termEPvS6_+00000152
[ 63] 0x000000011158966f /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+05088879 _ZN9MathWorks3lxe9Evaluator15ApplyStatementsERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEERKN2ir4termERNS0_18IEvaluationContextE+00000495
[ 64] 0x000000011158da2b /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+05106219 _ZN9MathWorks3lxe9Evaluator17EvalStatementImplERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEERNS0_18IEvaluationContextE+00000331
[ 65] 0x000000011158dafe /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+05106430 _ZN9MathWorks3lxe9Evaluator13EvalStatementERKNSt3__112basic_stringIDsNS2_11char_traitsIDsEENS2_9allocatorIDsEEEERNS0_18IEvaluationContextE+00000110
[ 66] 0x0000000111578ebb /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+05021371 _ZNK9MathWorks3lxe20BuiltinSubsFunctions11SubsrefImplEiRK11mxArray_tagS4_PKNS0_29DispatcherFunctionHandleTokenE+00000235
[ 67] 0x000000011157909c /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+05021852 _ZN9MathWorks3lxe20BuiltinSubsFunctions7SubsrefEiPP11mxArray_tagiPKPKS2_+00000140
[ 68] 0x0000000110d084e0 /Applications/MATLAB_R2020b.app/bin/maci64/libmwbuiltin.dylib+00013536 _ZNK9MathWorks7builtin10BuiltinFcn6invokeEiPP11mxArray_tagiS4_+00000944
[ 69] 0x0000000110601c24 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00134180 _ZN10builtinlog9getLoggerEv+00002324
[ 70] 0x00000001105e5af6 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00019190 _ZN18Mfh_MATLAB_fn_impl8dispatchEiPP11mxArray_tagiS2_+00000214
[ 71] 0x000000011cf9ab30 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+03480368 _ZN19Mobject_system_impl11callBuiltinEPKciPP11mxArray_tagiS4_+00001088
[ 72] 0x000000011067d769 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00640873 _Z21mdBuiltinAsBuiltinFcniPP11mxArray_tagiS1_+00000313
[ 73] 0x0000000110d084e0 /Applications/MATLAB_R2020b.app/bin/maci64/libmwbuiltin.dylib+00013536 _ZNK9MathWorks7builtin10BuiltinFcn6invokeEiPP11mxArray_tagiS4_+00000944
[ 74] 0x0000000110601c24 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00134180 _ZN10builtinlog9getLoggerEv+00002324
[ 75] 0x00000001105e6332 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00021298 _ZN18Mfh_MATLAB_fn_impl8dispatchEiPNSt3__110unique_ptrI11mxArray_tagN6matrix6detail17mxDestroy_deleterEEEiPPS2_+00000370
[ 76] 0x00000001116f8489 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+06591625 _ZN9MathWorks3lxe17LxeDispatcherImpl12apply_handleEPNS0_29DispatcherFunctionHandleTokenEmPNS0_6xvalueEmPKS4_RKNS0_12LxeTypesBaseENS0_9ApplyTypeE+00001337
[ 77] 0x000000011182d814 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+07858196 _ZN9MathWorks3lxe20apply_handle_nargoutEPvNS_2ts4TypeEPKvS1_S1_+00000404
[ 78] 0x00000001117a93fe /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+07316478 _ZN9MathWorks3lxe38cpp_primitive_template_fn_with_contextIXadL_ZNS0_20apply_handle_nargoutEPvNS_2ts4TypeEPKvS2_S2_EEEEbS2_S4_S6_S2_S2_+00000014
[ 79] 0x00000001113d3ee7 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03296999 callPrimitiveWrapper+00000263
[ 80] 0x00000001113ba05d /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03190877 _ZN9MathWorks3lxe15ExecutionDriver9ThreadRunEv+00000445
[ 81] 0x00000001113bffad /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03215277 _ZN9MathWorks3lxe12IrEngineImpl5ApplyERKN2ir4termEPvS6_+00000301
[ 82] 0x00000001115f3df8 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+05524984 _ZN9MathWorks3lxe17IrEngineDecorator5ApplyERKN2ir4termEPvS6_+00000152
[ 83] 0x00000001116ed130 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+06545712 _ZN9MathWorks3lxe27FileBasedMatlabCodeFunction25DispatchFunctionWithReuseEiPP11mxArray_tagiS4_+00001568
[ 84] 0x00000001116ee0ac /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+06549676 _ZN9MathWorks3lxe27FileBasedMatlabCodeFunction12DispatchFileEiPP11mxArray_tagiS4_b+00000156
[ 85] 0x00000001106838de /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00665822 _ZN8Mfh_file20dispatch_file_commonEMS_FviPP11mxArray_tagiS2_EiS2_iS2_+00000142
[ 86] 0x0000000110683d44 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00666948 _ZN8Mfh_file19dispatch_with_reuseEiPP11mxArray_tagiS2_+00000228
[ 87] 0x000000011cea65ec /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+02479596 _ZN4mcos26invokeMMethodWithReuseFlagEPNS_13COSMethodInfoEbPKNS_9COSClientERiPNS_8COSValueEiPKS6_+00002156
[ 88] 0x000000011ce2b397 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+01975191 _ZN24OpaqueMethodCallMetaData11callMMethodEPN4mcos13COSMethodInfoEPP11mxArray_tagPKNS0_9COSClientEb+00000567
[ 89] 0x000000011ce2fac3 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+01993411 _ZN24OpaqueMethodCallMetaData23callMethodOrConstructorEP11mxArray_tagbiPS1_iPPKS0_bPKN4mcos9COSClientEPS9_PPNS6_13COSMethodInfoEbb+00000291
[ 90] 0x000000011ce31a20 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+02001440 _Z19omIsPackageFunctionPK11mxArray_tag+00007168
[ 91] 0x000000011ce2de20 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+01986080 _Z22omCallMethodWithClientP11mxArray_tagbS0_iPS0_iPPKS_PKN4mcos9COSClientEbPS8_PPNS5_13COSMethodInfoE+00000272
[ 92] 0x000000011cfb42da /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+03584730 _ZN25Mfh_MCOS_dynamic_all_args15dispatch_opaqueEiPP11mxArray_tagiS2_b+00000298
[ 93] 0x000000011cfb2e34 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+03579444 _ZN10Mfh_opaque22dispatch_mf_with_reuseEiPP11mxArray_tagiS2_+00000068
[ 94] 0x00000001105e5ec6 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00020166 _ZN18Mfh_MATLAB_fn_impl19dispatch_with_reuseEiPP11mxArray_tagiS2_+00000214
[ 95] 0x000000011504abfb /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+00445435 _ZN9MathWorks3lxelsERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEERKNS0_10MultiValueE+00059355
[ 96] 0x000000011503d343 /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+00389955 _ZN9MathWorks3lxelsERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEERKNS0_10MultiValueE+00003875
[ 97] 0x0000000115060360 /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+00533344 _ZN9MathWorks3lxe36DereferenceRplaceToXvalueZeroOutputsERKNS_3utl10attach_ptrIKNS0_7IRplaceEEE+00000032
[ 98] 0x000000011500cf87 /Applications/MATLAB_R2020b.app/bin/maci64/libmwlxeindexing.dylib+00192391 _ZN9MathWorks3lxe10at_rparen0EPvNS_2ts4TypeEPKvS1_S1_+00000727
[ 99] 0x00000001117a86ee /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+07313134 _ZN9MathWorks3lxe38cpp_primitive_template_fn_with_contextIXadL_ZNS0_10at_rparen0EPvNS_2ts4TypeEPKvS2_S2_EEEEbS2_S4_S6_S2_S2_+00000014
[100] 0x00000001113d3ee7 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03296999 callPrimitiveWrapper+00000263
[101] 0x00000001113ba05d /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03190877 _ZN9MathWorks3lxe15ExecutionDriver9ThreadRunEv+00000445
[102] 0x00000001113bffad /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+03215277 _ZN9MathWorks3lxe12IrEngineImpl5ApplyERKN2ir4termEPvS6_+00000301
[103] 0x00000001115f3df8 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+05524984 _ZN9MathWorks3lxe17IrEngineDecorator5ApplyERKN2ir4termEPvS6_+00000152
[104] 0x00000001116ed70f /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+06547215 _ZN9MathWorks3lxe27FileBasedMatlabCodeFunction16DispatchFunctionEiPP11mxArray_tagiS4_+00001215
[105] 0x00000001116ee0c2 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_lxe.dylib+06549698 _ZN9MathWorks3lxe27FileBasedMatlabCodeFunction12DispatchFileEiPP11mxArray_tagiS4_b+00000178
[106] 0x00000001106838de /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00665822 _ZN8Mfh_file20dispatch_file_commonEMS_FviPP11mxArray_tagiS2_EiS2_iS2_+00000142
[107] 0x0000000110683a24 /Applications/MATLAB_R2020b.app/bin/maci64/libmwm_dispatcher.dylib+00666148 _ZN8Mfh_file8dispatchEiPP11mxArray_tagiS2_+00000228
[108] 0x000000011cea6601 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+02479617 _ZN4mcos26invokeMMethodWithReuseFlagEPNS_13COSMethodInfoEbPKNS_9COSClientERiPNS_8COSValueEiPKS6_+00002177
[109] 0x000000011cea297f /Applications/MATLAB_R2020b.app/bin/maci64/libmwmcos_impl.dylib+02464127 _ZN4mcos18MEnumConstructorMI19convertFromEnumNameEPNS_9COSClassIEPNS_8COSValueEPKS3_+00000799
[110] 0x00000001757004bf /Applications/MATLAB_R2020b.app/bin/maci64/libmwsystemobject_mcos.dylib+00709823 _ZN6somcos16callMethodDirectEPNS_4impl8InstanceERiPN4mcos8COSValueEiPKS5_PKcRPKNS4_13COSMethodInfoE+00000111
[111] 0x00000001756e043b /Applications/MATLAB_R2020b.app/bin/maci64/libmwsystemobject_mcos.dylib+00578619 _ZN6somcos13callSetupImplEPNS_4impl8InstanceEiPKN4mcos8COSValueE+00001851
[112] 0x00000001756dff91 /Applications/MATLAB_R2020b.app/bin/maci64/libmwsystemobject_mcos.dylib+00577425 _ZN6somcos13callSetupImplEPNS_4impl8InstanceEiPKN4mcos8COSValueE+00000657
[113] 0x00000001756d74bc /Applications/MATLAB_R2020b.app/bin/maci64/libmwsystemobject_mcos.dylib+00541884 _ZN6somcos13callSetupImplEiPKN4mcos8COSValueE+00000092
[114] 0x00000001d0a3f13a /Applications/MATLAB_R2020b.app/bin/maci64/libmwmatlabsystemblock.dylib+00651578 _ZN12SysBlockBase17MSysObjDispatcher22invokeSysObjMethodImplENS0_14ImplMethodTypeERiPN4mcos8COSValueEiPKS4_+00000458
[115] 0x00000001d0a32b5e /Applications/MATLAB_R2020b.app/bin/maci64/libmwmatlabsystemblock.dylib+00600926 _ZN12SysBlockBase17MSysObjDispatcher18invokeSysObjMethodENS0_14ImplMethodTypeERiPN4mcos8COSValueEiPKS4_+00000142
[116] 0x00000001d0a51538 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmatlabsystemblock.dylib+00726328 _ZN12SysBlockBase17MSysObjDispatcher13callSetupImplEP11SLExecBlockP11mxArray_tagPN6sysobj6SysObjE+00000696
[117] 0x00000001d0a51f91 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmatlabsystemblock.dylib+00728977 _ZN12SysBlockBase17MSysObjDispatcher9callStartEP11SLExecBlock+00000177
[118] 0x00000001d0a057a6 /Applications/MATLAB_R2020b.app/bin/maci64/libmwmatlabsystemblock.dylib+00415654 _ZN20MLSysExecBlockNormal21SetupRuntimeResourcesEv+00000070
[119] 0x00000001b7aa2678 /Applications/MATLAB_R2020b.app/bin/maci64/libmwsimulink.dylib+15439480 _Z26BlockSetupRuntimeResourcesP10slSimBlock+00000168
[120] 0x00000001b7345d3d /Applications/MATLAB_R2020b.app/bin/maci64/libmwsimulink.dylib+07720253 _Z14BdSystemOutputP10bdExecInfoP8SLExecBDP7SLBlockP10slSimBlock+00001853
[121] 0x00000001b7343af2 /Applications/MATLAB_R2020b.app/bin/maci64/libmwsimulink.dylib+07711474 _Z29BdSystemSetupRuntimeResourcesP10bdExecInfoP8SLExecBD+00000290
[122] 0x00000001b6de9f1f /Applications/MATLAB_R2020b.app/bin/maci64/libmwsimulink.dylib+02101023 _ZN18SubsystemExecBlock21SetupRuntimeResourcesEv+00000655
[123] 0x00000001b7aa2678 /Applications/MATLAB_R2020b.app/bin/maci64/libmwsimulink.dylib+15439480 _Z26BlockSetupRuntimeResourcesP10slSimBlock+00000168
[124] 0x00000001b7345d3d /Applications/MATLAB_R2020b.app/bin/maci64/libmwsimulink.dylib+07720253 _Z14BdSystemOutputP10bdExecInfoP8SLExecBDP7SLBlockP10slSimBlock+00001853
[125] 0x00000001b7343af2 /Applications/MATLAB_R2020b.app/bin/maci64/libmwsimulink.dylib+07711474 _Z29BdSystemSetupRuntimeResourcesP10bdExecInfoP8SLExecBD+00000290
[126] 0x000000019c7a0a5c /Applications/MATLAB_R2020b.app/bin/maci64/libmwsl_engine_classes.dylib+00576092 _ZN8SLExecBD26modelSetupRuntimeResourcesEv+00000108
[127] 0x000000018b5e04ad /Applications/MATLAB_R2020b.app/bin/maci64/libmwsl_link_bd.dylib+00509101 _Z32SLLinkModelSetupRuntimeResourcesP8SLExecBDP14CmdlSimInpInfo+00000061

Program State:

Most Recent Simulink Activity:
playSimulationAction : OK in editor 1 at Thu May 27 11:54:54 2021
		updateDiagramAction : OK in editor 1 at Thu May 27 11:54:31 2021
		Ctrl+D : OK in editor 1 at Thu May 27 11:54:31 2021

This error was detected while a MEX-file was running. If the MEX-file
is not an official MathWorks function, please examine its source code
for errors. Please consult the External Interfaces Guide for information
on debugging MEX-files.

Not solved by export MESA_LOADER_DRIVER_OVVERRIDE=i965.
Seems to be a different issue than https://github.com/robotology/idyntree/issues/221 .

Seems to be a different issue than robotology/idyntree#221 .

Why do you think so? The problem is indeed the same: you can't create windows on a non-main Thread on macOS.

For the future, note that MESA_LOADER_DRIVER_OVVERRIDE is a Linux-specific environment variable.

Probably it is worth to avoid further confusion to clearly document that the C++-Irrlicht-Visualizer block (I don't remember its name) does not work on macOS.

Probably it is worth to avoid further confusion to clearly document that the C++-Irrlicht-Visualizer block (I don't remember its name) does not work on macOS.

I agree. I add a comment in the class description but maybe it is worth adding it also in a more visible place.
Where? In the readme?

Probably it is worth to avoid further confusion to clearly document that the C++-Irrlicht-Visualizer block (I don't remember its name) does not work on macOS.

I agree. I add a comment in the class description but maybe it is worth adding it also in a more visible place.
Where? In the readme?

Probably the most visible place for the Simulink user is in the mask documentation? @nunoguedelha do you have any opinion?

So the comment in the class description should be enough since it appears in the mask.

Why do you think so? The problem is indeed the same: you can't create windows on a non-main Thread on macOS.

Sorry @traversaro , I didn't read well the error report, it's not very human friendly 😄 . So indeed it fails in the lines 10, 11, 12
IrrDeviceMacOSX ... IrrlichtCreationParameters
createDeviceEx
Visualizer.init ... VisualizerOptions

For the future, note that MESA_LOADER_DRIVER_OVVERRIDE is a Linux-specific environment variable.

I had the wrong impression you were not sure about it just working for Linux, so I gave a quick try.

So the comment in the class description should be enough since it appears in the mask.
image

Yes it should be enough. There is no section in the README dedicated to the robotSensor nor visualizers libraries. When there is, we can then include the disclamer (just in case people don't pay attention to the block description).

I suggest doing a "squash merge" as already selected.

Thanks! @nunoguedelha @traversaro in view of https://github.com/dic-iit/matlab-whole-body-simulator/issues/52 do you want me to merge in master or in devel?

@nunoguedelha feel free to merge :)

Since #52 has an outcome now, merging in master!


Xbox controller trigger input is wrong.

Godot version:
4.0 master
3.2.3 stable
OS/device including version:
WIN 10, using Wired Xbox 360 controller.
Issue description:
Godot treats trigger input incorrectly.
The for the Right trigger, first half of the trigger pull is "Joystick 2 Up", and the second half if "Joystick 2 Down", but you can only set one of these axes as the input value. This means that the first half of the trigger pull is ignored, and you essentially always have a deadzone of 50%...
Here is an example with a utility that reads what the actual input is. As you can see, Godot thinks the input starts at 50%. Note I have the deadzone set to 0% here (does deadzone even work anway??).

Steps to reproduce:
Make an input action with a joystick input event.
Print or set a label text to Input.get_action_strength("my_action")
Play the scene and press the right trigger.
The label will only go above 0 when the trigger is half pressed.
Minimal reproduction project:
For 3.2
XboxTriggersWrong.zip

https://github.com/godotengine/godot/blob/706c38ab2a69fa36aff6ff7d0ba2ca4517c5dcd6/core/input/input.cpp#L897
Here is where the value gets reversed. The controller does input a value 0 to 255, which then goes through a bunch of different conversions.
I don't know why it was done like this... Why were triggers split into 2 axes where you can only use half of them?

I don't know why it was done like this... Why were triggers split into 2 axes where you can only use half of them?

See https://github.com/godotengine/godot/pull/42799.

Why were triggers split into 2 axes where you can only use half of them?

Originally, Microsoft used a single axis for the two triggers. The -ve and +ve were split into the two triggers. To get around the problem of only being able to use one trigger at a time, they were split into two axes, but the range wasn't changed. Actually, the complexity goes back further, because originally triggers were buttons not even axes; so having a axis with a range was an enahancement.

@madmiraal Ok, so can this be fixed?
This is like having a deadzone of 50% all the time. This is not how it works in other engines.

The for the Right trigger, first half of the trigger pull is "Joystick 2 Up", and the second half if "Joystick 2 Down"

The left trigger should map to the positive half of axis 4 (Joystick 2 Right) and the right trigger should map to the positive half of axis 5 (Joystick 2 Down).
I don't have an XBox controller so I can't test it and confirm that this is a bug, but the values are provided by Windows XInput. In the case of triggers these are bytes. The byte values are converted to a positive value between 0 and 1 here:
https://github.com/godotengine/godot/blob/d94bf9f7b66c7e5ec4c7438025fbcc59110cb4e7/platform/windows/joypad_windows.cpp#L457-L462
There should never by negative values provided by triggers.

I have an Xbox One controller (Win 64). When I map the trigger buttons (L2,R2 - not the shoulder buttons) to left_trigger and right_trigger and
func _physics_process(_delta):
	print("right: ",Input.get_action_strength("right_trigger"))
	print("left: ",Input.get_action_strength("left_trigger"))

it will print

left: 0
right: 0
left: 0
right: 0
left: 0
right: 1
left: 1
right: 1
left: 1
right: 1

This is strange, for one because deadzone was set to 0 yet the button press was only registered after it has already been pressed halve way through, and second, because I seem to remember successfully using strength on this very Xbox One controller some time back without problems. I get strength from my analog sticks on the same controller just fine.

I have an Xbox One controller (Win 64). When I map the trigger buttons (L2,R2 - not the shoulder buttons) to left_trigger and right_trigger and
func _physics_process(_delta):
	print("right: ",Input.get_action_strength("right_trigger"))
	print("left: ",Input.get_action_strength("left_trigger"))

it will print

left: 0
right: 0
left: 0
right: 0
left: 0
right: 1
left: 1
right: 1
left: 1
right: 1

This is strange, for one because deadzone was set to 0 yet the button press was only registered after it has already been pressed halve way through, and second, because I seem to remember successfully using strength on this very Xbox One controller some time back without problems. I get strength from my analog sticks on the same controller just fine.

Yeah from memory testing this problem deadzone doesn't do anything it seems.
It is quite counterintuitive due to the way it is set up with the 2 different axes representing the 2 halves of the trigger pressed level. Currently you can only bind to one of these axes, so you get either the first half or the second half of the trigger movement.

Yeah from memory testing this problem deadzone doesn't do anything it seems.
It is quite counterintuitive due to the way it is set up with the 2 different axes representing the 2 halves of the trigger pressed level. Currently you can only bind to one of these axes, so you get either the first half or the second half of the trigger movement.

@EricEzaM Is this still an issue for you? @golddotasksquestions, in his edited comment, says "On the joy axis the triggers work fine, deadzone included." with a Xbox One Controller. I have now tested this on Windows with a PS3 controller and it (including the dead zone) works fine for me too.
The only thing I can think of is the Action Deadzone, which despite you saying "I have the deadzone set to 0% here", in your MRP it is set to the default 50%; so the behaviour you're seeing would be expected.
BTW See https://github.com/godotengine/godot-proposals/issues/3709 for a proposal on making the axes dead zone configurable and changing the default to a more reasonable value of 5%.

I will try and test, thanks @madmiraal
Might be in the new year tho

@EricEzaM I've just tested this on master and I can confirm that it is a problem on master for all controllers. On 3.x it works as expected.

@madmiraal I don't have access to a controller right now, but will test this again as soon as I can.


print_tree UPat +fix

print Upat and let const 0 uops be displayed correctly

Can you add tests to CI for print_tree that no behavior regressed?

fyi had slight behaviour changes
for uop const zero is printing out as CONST 0
for LazyOp ADD is printing as BinaryOps.ADD


up, down for uicollectionview swift 5

UIcollectionviewcell in i need up, down and show options
delete or edit.
can i change direction in this lib ?

I don’t understand the question.

Only left and right swipe. No vertical swipe.


Create an easy way to set up new roles and serviceaccounts for user applications

Right now when someone wants to create a new application and give it access to something in AWS we give them instructions on how to do it using "IRSA", the new mechanism for granting access to pods, but there's still quite a bit of manual work and confusion. I think we could simplify it by writing some terraform that would allow them to supply a list of service account names and corresponding AWS IAM policies, and we can create all the required resources. We can either just leave the list blank to start or maybe we could use it to create some of the service accounts we need for stuff we set up like external-dns.
I imagine this could look like another file in infrastructure/terraform/environments/<env>/ maybe application_iam_policy where they can specify policy blocks like:
data "aws_iam_policy_document" "my_application" {
  statement {
    actions = [
      "whatever",
    ]

    resources = ["*"]
  }
}

And then in infrastructure/terraform/environments/<env>/main.tf in the vars we pass to environment we add a map of serviceaccount to policy like:
  application_iam_policies = {
    service_account = my_application
    namespace       = app_namespace
    policy          = aws_iam_policy_document.my_application
  }

Then in the background we create the role for them. We can do something similar in infrastructure/kubernetes and accept a list of serviceaccounts and namespaces and create the service accounts for them.

This feature is called "IAM Role for Service Accounts" (aka: IRSA). I have gone through two articles
IAM roles for service accounts
and Introducing fine-grained IAM roles for service accounts
Confirmed with @bmonkman  that this should be a common module under infrastructure/kubernetes/terraform/modules/ side.

PR: https://github.com/commitdev/zero-aws-eks-stack/pull/74


Log facade integration

It seems to me as Log::error for example doesn't get reported at all, would like to use it to enhance a few errors with more informations. Isn't it integrated yet or am I just missing something ?

Hey,
Log::error() is a logging utility that writes to the log file. It is not an exception, and it does not reach the ExceptionHandler. If you want to collect these as well consider throwing exceptions when they occur. Or create an event listener that listens for the illuminate.log event, and call
$handler = app('Illuminate\Contracts\Debug\ExceptionHandler');
$handler->report(new SomeCustomException('message from log'));

to manually send the error.


JSON.SET supports NX and XX

Search before asking

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

Motivation
From the https://github.com/RedisJSON/RedisJSON/blob/master/docs/commands/json.set.md
We only support JSON.SET without NX and XX.
Solution
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

@mapleFU is this finished? If you are not working on it, can I take over on it?


Another ${aws:username} issue

cfn-lint version: 0.8.1
Description of issue.
Reference Issue #401 , ${aws:username} is also used in the AWS::IAM::ManagedPolicy resource type and needs the same fix.

Looking into this it just appears that the fix isn't included in 0.8.1. I manually patched in my venv and it works against ManagedPolicy. Doesn't look to be resource type specific, but field specific.
Not sure when they plan another release.

I'll do one today.

0.8.2 works for me.

Great to hear! Shutting this one down.


Pokedisplay not dropping when broken with a silk touch netherite pickaxe

I was fiddling with it to test how to actually use it, when i was done i attempted to break it with my silk touch netherite pick, after doing so it didnt drop the item on the floor, leaving us unable to get it back.

Fixed for the next server restarts! Thank you for your ticket!


WFCORE-6584 Upgrade wildfly-common to 1.7.0.Final

https://issues.redhat.com/browse/WFCORE-6584

Core -> Full Integration Build 12973 outcome was UNKNOWN using a merge of ff42f85dcde31fdabc6cfbd386abe4e6589f5424
Summary: Canceled Build time: 00:01:03

Core -> WildFly Preview Integration Build 13048 outcome was UNKNOWN using a merge of ff42f85dcde31fdabc6cfbd386abe4e6589f5424
Summary: Canceled Build time: 00:01:04

Core -> Full Integration Build 13197 outcome was UNKNOWN using a merge of ff42f85dcde31fdabc6cfbd386abe4e6589f5424
Summary: Canceled Build time: 00:01:04

Thanks @pferraro


Support columnset/column in package card

Lark now supports adding multiple columns in card, which is very useful when illustrating data tables. https://open.feishu.cn/document/common-capabilities/message-card/message-cards-content/column-set

Thanks for your advice. Card with I18N is now being under development. And then column and columnset will be added ASAP.


Change from address on comment notification emails to<EMAIL_ADDRESS>

Deployed to production.


Support OCSP check via HTTP GET on non-Darwin platforms

Motivation:
OCSP check can be done via HTTP POST or GET. The current code only does
POST and gives up if that fails.
Modification:
Try GET if POST fails.
rdar://90280783

@swift-ci please smoke test

not sure if we can also add a test?

@swift-ci please smoke test linux

not sure if we can also add a test?

There is but needs real cert to run: https://github.com/apple/swift-package-manager/blob/main/Tests/PackageCollectionsSigningTests/CertificatePolicyTests.swift#L116


Add support of the command EXPIRETIME

Refer to https://redis.io/commands/expiretime/

Can you assign it to me?

@kay011 Assigned, thank you!


Would love to be a member of this community

Name
shadesherif
Discord Username (if applicable) E.g John#412
No response
Questions & suggestions?
Are you a programmer too ? 😅

Welcome to the community @shade234sherif , we're pleased to have you!🥳

@Mannuel25 I appreciate that 🙂
I'm glad to be a member of this organizations


Handle null values encountered in CLPDecodeTransformFunction

The CLP message decoder in CLPDecodeTransformFunction does not correctly handle null values. While null is a valid value in Pinot, it is unsupported by CLP. This PR introduces null value handling before invoking the message decoder to ensure the expected user behavior is properly implemented.

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

Project coverage is 0.00%. Comparing base (59551e4) to head (a279940).
Report is 1277 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (a279940). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (a279940)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
0

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14364       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
0.00% <ø> (-27.73%)
:arrow_down:

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


fix endpoints for ciraconfig RPS APIs

Update endpoints and provide example method/apikey for all ciraconfig apis.  Based on feedback from MPS Issue #33.

@bwendlandt-intel this addresses open-amt-cloud-toolkit/mps#33 right?

Yes, that is correct Mike.


Fixes errors on retrieval models evaluation in graph mode

After the recent refactory, errors like below one were being raised during evaluation on retrieval models because the targets
had shape undefined. That caused errors when using pairwise losses (e.g. bpr-max) and for custom metrics that use tf.boolean_mask() and require the mask tensor to have at most one dim undefined.
y_pred_valid_rows = tf.boolean_mask(y_pred, valid_rows_with_positive_mask)

    ValueError: Number of mask dimensions must be specified, even if some dimensions are None.  E.g. shape=[None] is ok, but shape=None is not.

rerun tests

rerun tests


fix: dojo.JIRA_Instance.default_issue_type: (fields.E005) 'choices'

Described in https://github.com/DefectDojo/django-DefectDojo/issues/10825
Mentioned in https://owasp.slack.com/archives/C2P5BA8MN/p1725469527708379?thread_ts=1725355658.824789&cid=C2P5BA8MN

Can confirm this works on my dev stack.  Built the container images fine, started the containers fine, can run the manage python scripts in the containers.  No longer receive any errors as mentioned before.
Previous errors:
(manage python script for reconciliation of jira issues)
"SystemCheckError: System check identified some issues:ERRORS:
dojo.JIRA_Instance.defauilt_issue_type: (fields.E005) 'choices' must be a mapping of actual values to human readable names or an iterable containing (actual value, human readable name) tuples.
This would result in 500 errors when clicking anything in DefectDojo that had 'jira' for a configuration.  This no longer errors and I can add / view / edit jira configurations just fine now.

@kiblik Approved with the merge conflict because I have no concern about you addressing that when it comes time to merge. :+1:


Parameterized Embedding Composite

This is a cute way to have completely parameterized embedding Composites.
An embedding_method can be any object with a find_embedding(S, T, **params) method.
Where S and T are edgelists or NetworkX Graphs.
It relates to minorminer/#82 since it would benefit from having parameters visible from the embedding_method.
It also relates to #100, in that, it's an idea on how to pass complex objects/methods to a composite.
And it would easily allow the inclusion of other methods, as well as more control over minorminer's
features.
# Example usage
import minorminer
import dwave_networkx as dnx

from dwave.system import DWaveSampler, ParamEmbeddingComposite
from dimod import StructureComposite, SimulatedAnnealingSampler

Tg = dnx.chimera_graph(4)
structsampler = StructureComposite(SimulatedAnnealingSampler(), Tg.nodes, Tg.edges)

sampler = ParamEmbeddingComposite(structsampler, minorminer, random_seed=42)
# Same as:
# sampler = ParamEmbeddingComposite(structsampler, random_seed=42)

h = {'a': -1., 'b': 2}
J = {('a', 'b'): 1.5}
response = sampler.sample_ising(h, J)
for sample in response.samples():    # doctest: +SKIP
       print(sample)

sampler.embedding

Codecov Report

Merging #175 into master will decrease coverage by 6.43%.
The diff coverage is 14.89%.

@@            Coverage Diff             @@
##           master     #175      +/-   ##
==========================================
- Coverage   93.55%   87.11%   -6.44%
==========================================
  Files          16       16
  Lines         667      714      +47
==========================================
- Hits          624      622       -2
- Misses         43       92      +49

Impacted Files
Coverage Δ

dwave/system/composites/embedding.py
71.06% <14.89%> (-26.26%)
:arrow_down:

dwave/system/samplers/dwave_sampler.py
69.56% <0%> (-4.35%)
:arrow_down:

dwave/system/flux_bias_offsets.py
81.48% <0%> (-3.71%)
:arrow_down:

dwave/system/cache/database_manager.py
96.18% <0%> (-0.77%)
: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 86a1698...956cb0a. Read the comment docs.


Feature/101 - improve results node performance when includes are present on populates

Fixes #101
Discussion

the two forms of the mongo $lookup are supposed to be equivalent, but they clearly don't use indexes the same way because as noted on the issue changing the form can massively impact performance
change here always uses the fast form of the $lookup when doing includes for a results node populate
works under the hood by omitting from the populated base record rather than projecting during the lookup pipeline. Luckily the presence of the schema makes this optimization possible

Fails

:no_entry_sign:
The version was not updated. Please update the version.

:no_entry_sign:
The changelog has not been updated. Please update the changelog.

Warnings

:warning:
The README has not been updated. Please update the README.

Messages

:book:
We were able to automatically fix some formatting issues in this PR for you!

:book:
Could not find any browser results.

:book:
You reduced the total lines of code! Awesome! :+1:

Some things that were possibly fixed:

Code that could be fixed via the --fix flag
Formatting that could be fixed by prettier

Take a look at this commit to see what happened in detail: 69c79756115e1d3813dcaac9214e6b3be6567a4c
And look at this wiki page to see the reasoning behind the ESLint rules: https://github.com/smartprocure/eslint-config-smartprocure/wiki/Rules-and-Why-We-Chose-Them

  Generated by :no_entry_sign: dangerJS against 229e3d3b9dcb8bebffbe81a98581e51349e90e74

@ccalbaugh @stellarhoof I'm seeing the in-project queries we discussed go back to normal speeds with this

@daedalus28 this is good to go.

@daedalus28 this is good to go.

Updated with a comment to make clearer why we're diffing the populate includes with the schema and then omitting in place
@stellarhoof @daedalus28 ready for review

Updated with a comment to make clearer why we're diffing the populate includes with the schema and then omitting in place
@stellarhoof @daedalus28 ready for review

it'll be good to get one more review on this

it'll be good to get one more review on this


Translations

@MomomomoLiu can you please review these additional lines?
https://github.com/PoonLab/covizu/blob/d168753d31dc78bc7695ef496355870dddeed3dc/index-zh.html#L43-L50
https://github.com/PoonLab/covizu/blob/d168753d31dc78bc7695ef496355870dddeed3dc/index-zh.html#L59-L79

line 62 vedge_support: "支持",
line 65 hedge_unique_dates: "独特的收集日期",
it is a bit weird :(
I would like to double-check these lines meaning with you before merging

line 62 vedge_support: "支持",
line 65 hedge_unique_dates: "独特的收集日期",
it is a bit weird :(
I would like to double-check these lines meaning with you before merging

Yes those are fresh out of Google Translate, so I'm not surprised they sound weird :-)
Please refer to index.html for original English terms.

Need to add this to i18n_text JSON:
https://github.com/PoonLab/covizu/blob/e678f0ca1ea486a9381af226b39781d8c4ba2e5f/js/search.js#L46-L48

@RouxCil suggests moving the template into the JSON:
function update_search_stats(stats) {
   $('#search_stats').text(i18n_text.placeholder);
 }

in index.html:
i18n_text = {
  placeholder: `${stats.current_point+1} foo ${stats.total_points} bar`;
}

@GopiGugan - It would be better to zero the counts in the template string instead of having a zero_points placeholder

Looks good, thanks @GopiGugan and @MomomomoLiu


Sidecar .c files not compiled with cgo when building c archives

Go 1.5.1 on OS X 10.10.5 with Xcode 7

According to the official documentation for cgo:

When the Go tool sees that one or more Go files use the special import "C", it will look for other non-Go files in the directory and compile them as part of the Go package. Any .c, .s, or .S files will be compiled with the C compiler. Any .cc, .cpp, or .cxx files will be compiled with the C++ compiler.

This doesn't seem to be the case anymore or something there's a bug somewhere related to c archives: my source directory contains:

main.go
common.h
common.c

main.go starts with:
package main

/*
#include "common.h"
*/
import "C"
import "unsafe"
[...]

When compiling the .go file, it does find common.h but does not compile common.c:
go build -pkgdir=/Users/pol/Source/Go-Bridge/go-1.5.1/pkg_cross/MacOSX_x86_64 -v -x -buildmode=c-archive -o /Users/pol/Source/Go-Bridge/build/macosx/main.a main.go
WORK=/var/folders/mm/pqphm2md7k56y5tshf1s9jyr0000gp/T/go-build081061024
github.com/satori/go.uuid
mkdir -p $WORK/github.com/satori/go.uuid/_obj/
mkdir -p $WORK/github.com/satori/
cd /Users/pol/Source/Go-Bridge/go/src/github.com/satori/go.uuid
/Users/pol/Source/Go-Bridge/go-1.5.1/pkg/tool/darwin_amd64/compile -o $WORK/github.com/satori/go.uuid.a -trimpath $WORK -p github.com/satori/go.uuid -complete -buildid b2a6d969e469e8bf1b75c0bf64f31f75330dcf86 -D _/Users/pol/Source/Go-Bridge/go/src/github.com/satori/go.uuid -I $WORK -I /Users/pol/Source/Go-Bridge/go-1.5.1/pkg_cross/MacOSX_x86_64 -pack ./uuid.go
command-line-arguments
mkdir -p $WORK/command-line-arguments/_obj/
mkdir -p $WORK/command-line-arguments/_obj/exe/
cd /Users/pol/Source/Go-Bridge/go
CGO_LDFLAGS="-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk" "-arch" "x86_64" "-mmacosx-version-min=10.8" .-1.5.1/pkg/tool/darwin_amd64/cgo -objdir $WORK/command-line-arguments/_obj/ -importpath command-line-arguments -exportheader=$WORK/command-line-arguments/_obj/_cgo_install.h -- -I $WORK/command-line-arguments/_obj/ -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -arch x86_64 -mmacosx-version-min=10.8 main.go
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -print-libgcc-file-name
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I $WORK/command-line-arguments/_obj/ -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -arch x86_64 -mmacosx-version-min=10.8 -o $WORK/command-line-arguments/_obj/_cgo_main.o -c $WORK/command-line-arguments/_obj/_cgo_main.c
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I $WORK/command-line-arguments/_obj/ -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -arch x86_64 -mmacosx-version-min=10.8 -o $WORK/command-line-arguments/_obj/_cgo_export.o -c $WORK/command-line-arguments/_obj/_cgo_export.c
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I $WORK/command-line-arguments/_obj/ -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -arch x86_64 -mmacosx-version-min=10.8 -o $WORK/command-line-arguments/_obj/main.cgo2.o -c $WORK/command-line-arguments/_obj/main.cgo2.c
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -o $WORK/command-line-arguments/_obj/_cgo_.o $WORK/command-line-arguments/_obj/_cgo_main.o $WORK/command-line-arguments/_obj/_cgo_export.o $WORK/command-line-arguments/_obj/main.cgo2.o -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -arch x86_64 -mmacosx-version-min=10.8
# command-line-arguments
Undefined symbols for architecture x86_64:
  "_CBridge", referenced from:
      __cgo_97887027ee28_Cfunc_CBridge in main.cgo2.o
     (maybe you meant: __cgo_97887027ee28_Cfunc_CBridge)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Command /bin/sh failed with exit code 2

You don't need to explicit list main.go on the go build command line. Put
all files in a directory and go build will do the right thing.
I suggest you ask questions like this on the irc or golang-nuts mailing
list first.
Thanks.

You are correct, this fixes it. I got confused and thought this was a bug since the documentation does not state that this automatic behavior does not apply if explicitly passing in a .go file.

@swisspol in general you should always present packages, not files to the go tool. The fact that the go tool accepts both is a confusing exception that should not be considered the rule.


Add WGPU_BACKEND environment variable

#787 #207
Inspired by Bevy’s source code.
You can explicitly specify the render backend when you run your app by setting the WGPU_BACKEND environment variable. If this environment variable does not exist, the default is the wgpu::BackendBit::PRIMARY.
If you use cargo with version 1.52 or later, you can easily set your environment variables.
First create a folder called .cargo in your project directory, then create a config.toml file in the .cargo folder:
before:
.
├── Cargo.lock
├── Cargo.toml
└── src
    └── main.rs

after:
.
├── Cargo.lock
├── .cargo
│   └── config.toml
├── Cargo.toml
└── src
    └── main.rs

.cargo/config.toml:
[env]
WGPU_BACKEND = "dx12"

Specific configuration method can be seen here.

Running after setting through .cargo/config.toml requires cargo run -Zconfigurable-env instead of cargo run.If you set the environment variable on your system, rather than through .cargo/config.toml, you do not need to add this -Zconfigurable-env.

Is an environment variable the proper way to introduce this kind of configuration? Should it always be a user choice?

I think the ideal situation is the compiled iced program, you can choose their own internal rendering back-end, just need to restart the program can switch back-end, but it seems difficult to achieve. Environment variables make it easy for developers to specify which backend should be used for the compiled version, but users have no choice.

Is an environment variable the proper way to introduce this kind of configuration? Should it always be a user choice?

I would say yes: sometimes because of a driver issue with some backend, sometimes just for testing.
At any rate I did something similar (though WGPU_BACKEND is a better env var name): https://github.com/kas-gui/kas/blob/master/kas-wgpu/src/options.rs#L50

Should it always be a user choice?

If by user you mean the end-user of an iced application, I don't think so. I think it should be up to the developer using iced to decide if they want support X backend.
I'd include a new field under iced::Settings which exposes an enum to currently supported Backends.
In doing so, we would allow developers to create a "backend fallback strategy",
where they can request for some backend and fallback if that backend is not supported
(e.g. using Application::runs Error::GraphicsAdapterNotFound to try using other Backend).
This would allow any developer to add a WGPU_BACKEND flag if they wish to do so (we could also add to iceds example if convinient)
and would help me on my current work to add support for previous OpenGl versions on the glow backend :wink: (which would fallback on runtime).
This is certainly requires more work, but in my opinion, would make backend selection more flexible.
pub enum GlowBackend{
    Modern,
    Compatibility,
    Legacy,
}

pub enum Backend{
    #[cfg(feature="wgpu")]
    Wgpu(wgpu::BackendBit),
    #[cfg(feature="glow")]
    Glow(GlowBackend)
}

Maybe we should move this to a discussion?

@derezzedex Backend fallback is in the roadmap, but I believe solves a different kind of use case.


Transfer to moby/moby

It was brought up on the maintainers chat that we should probably merge libnetwork back into moby/moby.
This would simplify vendoring/import issues and contributions.
/cc @thaJeztah @justincormack @AkihiroSuda

We should think about how we can migrate issues/PR's (and what should just be closed/merged before doing so).
@AkihiroSuda mentioned that we could transfer libnetwork to the moby org first, this would allow us to transfer the issues to the moby/moby repo after the codebase is re-integrated with moby/moby.

PTAL @mavenugo

Yes. This is a good idea. am a 👍 to this proposal.

been talking about it for very long time.  It will save lot of time.

generally 👍
first moving the repo to the moby org sounds good.
we should spend some time to go through pull requests that are open to see if there's ones that we want to have
before integrating the code into moby/moby;

I'd love to see https://github.com/docker/libnetwork/pull/2509 (and related) in, so that we have less technical debt from the start
we need to see what integration tests are in this repo, and if we need to rewrite those so that they can run in moby CI (or if they're already covered otherwise)
we may keep the repository around (as in "not archived") as long as 19.03 is still actively maintained
What works best for Mirantis (enterprise releases)? Keep this repo around, or create a fork in the Mirantis org and do backporting there?

I noticed that kubernetes is vendoring libnetwork, so we need to make sure we don't break them (and make it easy to vendor the parts they need)

Nothing should break in short term due to redirects. Why is k8s vendoring libnetwork anyway!!
I am going to mover this to moby org.

It's importing ipvs code from here.

Done.

/cc @dims (for kubernetes)

🙏 @thaJeztah

yep, we use it for ipvs - https://cs.k8s.io/?q=github.com%2Fdocker%2Flibnetwork&i=nope&files=^pkg&repos=kubernetes/kubernetes

Seems like a good candidate to move to separate repo.

@cpuguy83 @thaJeztah @mavenugo @justincormack - so for a while, in kubernetes/kubernetes we have been trying to remove direct references to docker/docker (or moby/moby), splitting out the dockershim (or at least limiting its use in specific packages optionally imported) would take a whole bunch of references out, So that was our main thrust. But we still had a whole bunch of references to docker/docker. Over a period of time we have been able to prune the usage. Doing what is proposed here would be going backwards for us unfortunately.
I'd go further to request that we split out additional stuff from docker/docker (or moby/moby) into a library namely the sysinfo/parsers:
└── pkg
    ├── parsers
        ├── kernel
        └── operatingsystem

used by cadvisor (https://cs.k8s.io/?q=pkg%2Fparsers&i=nope&files=.*\.go&repos=kubernetes/kubernetes)
and another package for terminal stuff:
└── pkg
    └── term
        └── windows

used directly by kubernetes CLI (https://cs.k8s.io/?q=pkg%2Fterm&i=nope&files=.*\.go&repos=kubernetes/kubernetes)
cc @liggitt

@dims If we move ipvs out of libnetwork to a separate repo, you should be able to consume just the ipvs package.

@cpuguy83 yep, that works!


updated thanos.md, fixed indent of thanos spec config

after fixed the indent, it works for me

Thanks!


I have a few quick questions for the family

Hello thank you for this tool and amazing scripts
I am blessed doing some Lora training for flux models but wanted to see if there is a few things I can improve on workflow
so first off is there a way to use wandb in the config to repot and keep track of stuff in real time.

Blessed for this and future of AI and tech

Most of these things are planned/in PR/ in the works. The churp thing may not happen. However, it is east to build custom plugins to do things like that. I will try to document this further in the near future.


P/R/F1 scores reported in results.json and paper

Hi,
I ran your model on the provided SciERC data and get results very close to the ones reported in Table 3 of the paper.
I would now like to know how the precision, recall, and F1 scores are calculated given there are multiple entity classes/relation types. Specifically, I’m wondering

Is the number reported in the paper and in results.json a macro average or a weighted average?
Is NIL/NOTA (i.e. a token that is no entity/an entity pair with no relation) part of the calculation?

Thanks :)

weighted average (micro-F1)
NIL/NOTA is a part of denominator of the precision calculation .

thanks for the super fast reply

Quick follow-up question, just to make sure I understand correctly.
Regarding

NIL/NOTA is a part of denominator of the precision calculation

if we think of a scenario where we have entity classes A and B, then we have a false positive for class A not only when a B-entity is classified as A, but also when a token that is not an entity is classified as A, correct?
What is not clear to me is if you treat NIL/NOTA as a class itself. I.e, if a token that is not an entity is correctly predicted as not an entity, does this count as a true positive?
Thanks again for the clarification.

@YeDeming ping (just in case there’s not no notifications for comments)


When no text is selected, clicking a color palette item should copy a link to the page

e.g. [[file.pdf#page=<PAGE>]]. The same applies to the hotkey command as well.

Addressed in e650f4e5b66e and will be made available in v0.24.0


Mavenize this project

would it be possible to make this project into maven one? It would greatly improve this lib-s usability

Yes! Why don't you do it yourself? Some forks already did this but none created a pull request.


resource_user refresh performance improvement

Our Infrastructure has over a 1500 user resources, and we want to start using Terraform to manage these, but because we also have a lot of teams it is taking a lot of time to refresh the resources when running terraform plan/apply. Whenever user resource refresh is initiated it starts searching for all "teams" it is part of, but since there isn't a direct api call to query all "invitations" for this users email, it starts going through all team in our organisation and for us it takes ~1 min per user. So based on this calculated it would take us over 1500 minutes, which is too long.
This is the function where all teams are being checked to find the invitations for one user:
https://github.com/rollbar/terraform-provider-rollbar/blob/be38bdcbb44f814454559d5340d58c9cdda106d7/client/invitation.go#L238
Would be nice if there was an API endpoint that was used to get all invitations for an email, then only one request is needed to be called out, instead of 180+ requests (for our organisation). Based on what the current API endpoint returns it should be possible to implement a search/query by passing along an email.
Similar improvement (https://github.com/rollbar/terraform-provider-rollbar/pull/357) was done for projects with the provider-version update to 1.12.0. (Projects teams are now queryable by ProjectID instead of going through all teams projects to find the teams one project is part of). And this really helped us, making our 1500+ project resources refreshed in 18 minutes.

Hey @JJaakson, We're working on this fix. I'll update you when it's ready.

Hey @JJaakson, We released the performance improvement recently. I'll close this ticket. Let me know if you need further assistance.


Final logo with inter bold

@phalem Just to be sure, the idea is to merge this PR or the other one https://github.com/OpenBioML/chemnlp/pull/163 or should we keep both logo versions?

Closed in favor of https://github.com/OpenBioML/chemnlp/pull/163


Sample color

Okay, I fixed the issues I saw during our meeting. This PR contains the current code for empress; however, I did not include the animation code I am currently working on. Also tests still need to be written for some of the functions. But this will at least get the most recent code on the main branch so everyone will have access to it.

@kwcantrell, in addition to the remaining changes would you mind also pulling from upstream to add the recent changes that @fedarko pushed?


Limits API

Is your feature request related to a problem? Please describe.
There is currently no way to impose artificial limits (rooms-as-type per user, users per room-as-type, child rooms per parent room) and communicate them in a portable manner. We need a way to impose and communicate those limits. Those kinds of limits are useful in company, government, school and limited traffic cloud use cases. Several MSCs need to be drafted for each of those three kinds of limits.
Describe the solution you'd like

Per-room limits (which might be different for each room type), where room members with tombstone permissions can change.
Rooms-per-user (which might be different for each room type) limits, where server admins can change.
Child rooms per room limits, where the members of parent room having both tombstone and attach/detach room permissions can change.
A reliable limit query API, where any user can query the limits applicable in a given situation.

Part 1: #3021


support write page index

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
(This section helps Arrow developers understand the context and why for this feature, in addition to  the what)
From the issue https://github.com/apache/arrow-rs/issues/1705, the feature page index is important for arrow-rs reading and writing.
@Ted-Jiang is working on the reading path for the page index https://github.com/apache/arrow-rs/issues/1749.
I will work on the writing path for page index in the parquet-rs.
@alamb
@tustvold
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

One thing I stumbled across whilst reviewing the read side, is that the ColumnIndex has a hard-coded assumption that semantic records don't span page boundaries. That is the first repetition level of each page is 0. I think we may need to enforce this when writing file with a column index.

@tustvold
I have read the write path in the https://github.com/apache/parquet-mr and am very familiar with the write path of parquet.
Diff column chunk in the same row group may contain diff number of pages.
A value just can be encoded into only one page.

 * For example:
 *
 * <pre>
 * rows   col1   col2   col3
 *      ┌──────┬──────┬──────┐
 *   0  │  p0  │      │      │
 *      ╞══════╡  p0  │  p0  │
 *  20  │ p1(X)│------│------│
 *      ╞══════╪══════╡      │
 *  40  │ p2(X)│      │------│
 *      ╞══════╡ p1(X)╞══════╡
 *  60  │ p3(X)│      │------│
 *      ╞══════╪══════╡      │
 *  80  │  p4  │      │  p1  │
 *      ╞══════╡  p2  │      │
 * 100  │  p5  │      │      │
 *      └──────┴──────┴──────┘

In the current parquet writer for rust version:
start row group
start a column
write data to the column
end the column and will get the column chunk metadata
end row group
before flush the filemetadata to the disk, we should edit the column chunk metadata and add the index offset and index length metadata.

this issue can't be closed.


Add missing syntax and similarity section fields of config page

Resolve #
Description:
Checklist:
You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

[x] ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
[x] PRE-COMMIT. You ran pre-commit on all commits, or else, you
ran pre-commit run --all-files at the end.
[x] USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
our users.
[x] DEV CHANGES.

Update the documentation if this PR changes how to develop/launch on the app.
Update the README files and our wiki for any big design decisions, if relevant.
Add unit tests, docstrings, typing and comments for complex sections.

closing this PR as the changes are handled here


Headers of 404 page vs static pages

The default 404 page returns a header
["Content-Type" => "text/html, charset=utf-8"]

The static page handler, when serving plain text files returns
["Content-Type" => "text/plain;charset=UTF-8"];

Besides the expected difference of text/html vs text/plain there are 2 more differences that IMHO should not be. , vs. ;   and utf-8 vs UTF-8.
I think it would be better if this was unified across the whole Bailador.

According to https://tools.ietf.org/html/rfc2616#section-3.7 error handlers return the same charset notation as the static page handler

My point is that in Bailador they are different. Similar, but not exactly the same. See the two cases in my original comment. I think it would be better if they were exactly the same.

aye! i missed text/plain vs text/html, sorry.

I am going to revert this commit, because rendering string like Not found or Internal Server Errors are in fact plain text instead of html, as soon as you use a custom error (e.g. template or error_handler) the content type would be text/html.

$ curl -I https://google.com/abc/def | grep Content-Ty
Content-Type: text/html; charset=UTF-8

So maybe the default of Bailador should be also some nicer HTML.

Aye. I've created #188 for this so we can close this issue.

There is another issue here I have not addressed yet. Please look closely in the original comment. There is also a difference in ; vs , and lowercase vs uppercase UTF. I think it would be better to unify those as well even if both are acceptable by the standards.

I tought I've changed all occurances of , and lowercase to ; with uppercase in https://github.com/Bailador/Bailador/commit/9ac2bd64892409823630fa0f4d3b532cfc20e95d.
Did i miss something?

If I now run grep Content t/* I get lines like these:
t/11-error-templates.t:    is-deeply %resp<response>, [500, ["Content-Type" => "text/plain;charset=UTF-8"], 'Internal Server Error' ], '500 - without error template';
t/11-error-templates.t:    is-deeply %resp<response>, [500, ["Content-Type" => "text/html;charset=UTF-8"], 'muerte' ], '500 - with error template';
t/12-duplicate.t:is-deeply get-psgi-response('GET', '/foo'),  [200, ["Content-Type" => "text/html"], "hello"],              'route GET /foo exists';

so as I can see in some cases we get charset in some cases we don't. I think when we don't send the charset then it appears differently.

I see! Will fix that :)


retest this project with the Lean data set

@robertylewis I just merge a series of commits, inspired by some work the rust-lang folks did in integrating this, that moves a bunch of the configuration settings to live in the zuliprc file.  Docs are present in the README.md.  Can you test it out and make sure it didn't break anything for Lean?
Also you may want to look at the Rust folks changes: https://github.com/zulip/zulip_archive/commits/rust-remaining to see if any of those you'd like for Lean as well.  Here are my notes to them on next steps:

The "move CSS to separate file" commit we should just rebase to the bottom and merge.
For sort order, was the previous sort order "by last update"?  I think both are potentially useful, so I wouldn't want to unconditionally apply that change.  Ideally we'd just include something simple like sortable.js that allows the user to pick, and maybe have a config option for which is the default.  So I'd probably tweak the commit to be an option for the default view and merge it, and then we can open an issue for adding JS sorting.
For the "Reformat" commit, we may need to split it.  I suspect some of the styling changes may just be better for everyone.  I don't fully understand the "last_updated" change; I think the intent of the previous model was to avoid needing to rewrite all the HTML/markdown when run in incremental mode, and I'm not sure if your restructuring loses that.  Maybe it makes sense to open issues/small PRs for each independent change so we can see what the lean folks' original author thinks?

On question I had for you:

Would it make sense to move the code for pushing this to a GitHub Pages site to a separate script?  The Rust folks removed that functionality in their branch I think mostly to declutter things, and I think I agree it'd be cleaner if that was a separate script in this repo that just pushed the archive.

I had to change line 181 to site_url / html_root instead of os.path.join since Python complained about joining Path objects. Otherwise it seems to work fine.

The "move CSS to separate file" commit we should just rebase to the bottom and merge.

I'm not sure the script needs to generate CSS at all. We could provide a default (static) css file for the generated pages.

For sort order, was the previous sort order "by last update"?

It was by number of topics, which is a pretty stable measure of "importance." JS sorting sounds great (as long as the default order is customizable).

Would it make sense to move the code for pushing this to a GitHub Pages site to a separate script?

Yeah, we could just add it to the shell script that calls the Python script, no need for it to be in here.

think the intent of the previous model was to avoid needing to rewrite all the HTML/markdown when run in incremental mode

This was the intent, but I never actually got around to doing it. Right now, all the HTML/markdown gets regenerated each time, even when you update the archive incrementally.

The remaining 3 commits from rust-remaining branch that have yet to be reconciled with master branch:

Put style in style.css (https://github.com/zulip/zulip_archive/commit/1373f6c5591ae39c1aba8d998cea452e8b865398)
Sort index.html list alphabetically instead of by number of topics (https://github.com/zulip/zulip_archive/commit/a63a677ff5d1d3d25e11b15a793a8af08aa42fd2)
Show topic lists more compactly (https://github.com/zulip/zulip_archive/commit/87918e9fccebfffe8027df133d7fb24e0d7cb880)

What should be done for each of the 3?

Put style in style.css (1373f6c)

This should just be merged unconditionally; it should be simply a better arrangement.

Sort index.html list alphabetically instead of by number of topics (a63a677)

Hmm, this one is a bit more interesting.  I think ultimately one will want sort order to be something users can control dynamically with JavaScript.  Maybe we should turn this into an issue?

Show topic lists more compactly (87918e9)

Can you post screenshots of the two versions?  I think we might just want to figure out which version looks nicer and merge that.

Can you post screenshots of the two versions? I think we might just want to figure out which version looks nicer and merge that.

With double newlines: https://leanprover-community.github.io/archive/113488general/index.html
With single newline: https://zulip-archive.rust-lang.org/122651general/index.html

I think probably the right model is single newlines, and if one wants to do wider spacing between entries, that can be done with CSS.  Does that make sense to you @robertylewis?

Ah, I didn't think that newline actually had any effect on the HTML output, but apparently it does. It gets compiled to

...

 in the two-line case, and
...
 with one line. Yes, seems like a reasonable change, the spacing should be handled in the css for list environments.

OK, I think we've integrated everything from the Rust/Lean branches except for sort order, which I feel like should probably be made available as a JavaScript UI option.  @robertylewis @Mark-Simulacrum do you have a chance to test the latest code?

I will try to resync the rust-lang repository this weekend with this repository.

% include is emitted into the markdown files which isn't Markdown -- I think we should avoid doing so in the official tool, since it presumes you're using something like Jekyll or a similar markdown renderer which is a superset of markdown.

% include is emitted into the markdown files which isn't Markdown -- I think we should avoid doing so in the official tool, since it presumes you're using something like Jekyll or a similar markdown renderer which is a superset of markdown.

Opened #12 to address this.

Thanks everyone for testing!


Chinese translation is confusing

I tried to follow the translated instruction of README and appendix but I was totally confused by the wording in the documents. They look like a copy/paste from google translate..
Do you accept PRs? If so, I would like to correct some wordings in those docs and make them more readable.
Thanks.

Hi @yizhiheng thanks for reaching out :) @neal1991 has been leading the Chinese translation of this document. I can't read or write in Mandarin or Cantonese, so I'm not much of a judge as too what is and is not confusing (sorry about that). Would the two of you be interested in discussing updates? I will definitely accept PRs :+1:

My first priority is certainty to include a translation that is easy to understand and helpful to as many readers as possible :smile_cat:

@brannondorsey Thanks for the reply.
Cool. I will find some time to work on this later this week, and request a review from @neal1991 !

Wonderful. I appreciate the contribution!

@yizhiheng @brannondorsey To be honest, it is really annoying to hear that my translation is copy/paste form google translation. I do have utilized google translation, but not copy/paste. Most of the article is translate myself word by word. It really hurt me for my work. You can access my translation. If I translate this tutorial just by google translation. What is the significance? I am really not so boring to do nonsense.
So, please express your opinion with your responsibility. You have done nothing, and you mustn't to judge other's work with no evidence. If there is something confusing, you can contact me for discussion.

Hey @neal1991 and @yizhiheng. First off I want to make it very clear that I am incredibly appreciative to @neal1991 for the work that he has done and the initiative that he has taken in providing this contribution. I am sympathetic to criticism of his work. Unfortunately I am not in a position to edit/read any of the Chinese content submitted as a PR, but I do want to help mitigate any tensions and help facilitate a respectful conversation. @neal1991, thank you again for the work that you have done. @yizhiheng I am indeed open to suggestions and edits but lets make sure that it is done so in a way that is respectful to the work that has already been done.

I welcome specific discussion for the translation. You can point out where is the problem. I will try my best to modify. However, I can never accept irresponsible criticism.

@neal1991 I do apologize for what I said above. 😞
I did find some confusions in the translated docs when I tried to follow the steps. As result, I had to read the English docs to figure out.
I'm closing this issue for now and will issue a PR on those docs so that we can have more discussions there.

@neal1991 Thanks for your hard work. But there are indeed some confusions in the Chinese version.
For example, in the appendix.zh.md:
...
2. Now you'll need to wait for a device to connect to the target network. If you are testing this on your network (which you should be), reconnect a wireless device to capture a handshake.
...

should be translated into:
...
现在，你需要等待有一个设备去连接该目标网络。如果你现在正在你自己的网络上测试（按理说应该如此），请用一个无线设备连接以捕获握手。
...

to make it clear, I think.
Also, the following step:
...
Convert the capture file to .hccapx by uploading it to https://hashcat.net/cap2hccapx/.
...

should be:
...
将捕获文件上传到 https://hashcat.net/cap2hccapx/ 以转换成 .hccapx 格式。
...

Your translation:将捕获文件转换为.hccapx，将其上传到https://hashcat.net/cap2hccapx/。  confused me that I thought it is a two-step stuff.
Thanks for your work anyway, but I think this can be improved a lot. :)

Hi @Songkeys, thank you for the suggested edits. Discussion about proposed edits to the Chinese translation has moved to #26. Would you mind proposing these edits there? Cheers :smile_cat:


Added support for additional AWS and Sentry environment settings

Add a note to the readme about the new config parameters

This has been addressed in the latest commit.


[Question] How to uninstall thingsboard edge from ubuntu ?

Component

Installation

Description
A clear and concise details.
Environment

OS:  Linux rpi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
ThingsBoard: tb-edge-<IP_ADDRESS>

Do you have uninstall.sh?

@sirapol
To remove Edge from Ubuntu please execute next command:
sudo dpkg --purge tb-edge


When will this be uploaded onto nuget?

Wanted to use this library but could not find when I searched on nuget. Search

Oh my god I completely forgot about NuGet! It's currently midnight in the UK, but I'll upload it tomorrow 👍

Oh my god I completely forgot about NuGet!


Sort is not working

This is my code:
I include the libraries:

and then I created the datatable like this:
$('#MyTable').datatable({
                data: filterList,
                pageSize: itemsPerPage,
                sort:'*',
                lineFormat: function (id, data) {
                    var res = $('

');
                    for (var key in data) {
                        if (key != "GroupId" && key != "GroupName"  && key != "Number")
                            if(key==="Name")
                                res.append('' + data[key] + '	');
                            else
                                res.append('' + data[key] + '	');
                    }
                    $(res).attr('id', data['Id']);
                    $(res).dblclick(function () {
                        window.location.href = "/Project/Details/" + $(this).attr('id');
                    });
                    return res;
                },
                pagingDivSelector: '#projectPaging',
                pagingNumberOfPages: 10
            });

Can you please tell me what am I doing wrong? the datable is created and the arrows to sort the table are shown but when you click on it it just do nothing.
Thanks,
Alex Fernandez

Forget about it I just needed to add the data-sort="key" with the key to the table header column to be sorted.
Thanks


⚠ ClamAV has degraded performance

In 712c54b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 75 ms

Resolved: ClamAV performance has improved in 4d5881f.


Fix uglify issue in build process

Background
Fix issue in gulp build process in uglify library
Changes done
Add error paremeter in catch clausule
Pending to be done
N/A
Notes
N/A
Demo

Good catch @cristiangiagante ! Thanks!


Abstract date attributes out of DateOfBirth class

Date class can be abstracted out for other classes' usage

@kthSim I will take charge of this. Please assign it to me, and label it as type.Task, priority.Medium, and v1.2. Thanks!


Serve: JSON Body Handling

Not sure if anyone else if having the same issue but the Lambda Proxy integration functions I have setup when deployed do not parse the JSON and thus the events body property requires parsing in my lambda function (e.g. https://github.com/craftship/yith/blob/master/src/user/put.js#L8) when a request is sent with Content-Type application/json.
In order to replicate the same functionallity when running the webpack serve command I had to do the following:
https://github.com/elastic-coders/serverless-webpack/compare/master...craftship:use-text-parser
I have not raised a PR yet as wanted to see if I was missing anything obvious / missed something I should test further.
Let me know, thanks for the awesome plugin has really helped our project long!

I'm having the same problem.
This is a quote from the serverless documentation regarding lambda-proxy.
https://serverless.com/framework/docs/providers/aws/events/apigateway/

Note: When the body is a JSON-Document, you must parse it yourself

Just looked at your change. I think you need to do a little bit more. I think you only want to switch to text parser if the integration type is lambda-proxy.

Will amend and raise the PR thanks for confirming this and taking a look into it :D

@jonsharratt @anozaki If you use the serve functionality, it would be great if you could comment in #135 .

serve will be removed in the next v3.0.0 release in favor of serverless-offline (see #152 ). No efforts will be spent on the function anymore. So I'll close this issue.


Updated to Django 2.2.23.

Codecov Report

Merging #2376 (ceac74d) into main (6b5ffe5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2376   +/-   ##
=======================================
  Coverage   81.84%   81.84%
=======================================
  Files         614      614
  Lines       22126    22126
=======================================
  Hits        18110    18110
  Misses       4016     4016

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 6b5ffe5...ceac74d. Read the comment docs.


Enable automatic build of plugin using Travis

Update also its Readme page to state information about the plugin and how it can be installed.
Also for each JAR library which will finally appear in the installed plugin lib folder we need a license text file next to it stating the license for the JAR.

Fixed in: f985671cac1b16fbfc2ee6a53595d3dbd4e05454


Translation Details in reactjs

I have implemented translation details: Language Code, Version & Path to Folder Location  value added in DB after click on save button.

Defunct.


Plan for June 2021

Plan Items
UX

[ ] Improve suggestion to index the remote repository https://github.com/microsoft/vscode-remote-repositories-github/issues/17 @JacksonKearl

Fundamentals

[ ] Ensure a smooth flow between the Remote Repositories and the GHPR extensions @eamodio @alexr00
[ ] Easily accessible creation of remote links @eamodio @alexr00
[ ] :muscle: Explore command line support like code github.com/org/repo @eamodio
[ ] :muscle: Consolidate pickers with the GH core extension and make pickers available for other extensions @eamodio

Easily accessible creation of remote links

@eamodio I think think that the built in github extension makes the most sense for this, but it still doesn't have a web entry point.  The permalink commands in GHPRI now work without sign in, so that's an improvement. Should we just defer this until the github extension is web-ready? Do you know what it will take to get the github extension ready for web?


salmon: init at 1.10.2

Description of changes
Add new package: Salmon
Resolves: https://github.com/NixOS/nixpkgs/issues/252992
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Can you use the new by-name convention

Thanks for sharing the link to the docs. I wanted to do this after seeing the talk at NixCon. But couldn't find the description. Ready for review now.

Thanks for your time and for picking up this PR, Flying Sausage!

@FliegendeWurst looks like borg is stuck on something. I remember it took some time last time around, but not this long. Is this a problem?

@FliegendeWurst looks like borg is stuck on something. I remember it took some time last time around, but not this long. Is this a problem?

Yeah ARM Mac has been stuck the last few days. Not really a problem for this package.

What else can I do to get this merged? @ambroisie @FliegendeWurst

Unfortunately I don't have the merge bit.
So posting it to the "PRs already reviewed" thread on Discourse and/or waiting for a wandering merge-enabled-reviewer is the usual solution.

Can you resolve the outstanding changes to unblock the merge?

Ah, I missed the 2nd comment. Will do right away

Should be OK now, pending ofborg eval

@jbedo I added all the improvements by a-n-n-a-l-e-e. I wasn't entirely sure about excluding bzip2 and lzma, but anyway, I only ever saw fq or fq.gz files, so it should be fine. Pls let me know if I forgot something still, and whether it's ready to be merged.

I wasn't entirely sure about excluding bzip2 and lzma, but anyway, I only ever saw fq or fq.gz files, so it should be fine.

I agree, I've only seen gzipped fqs in the wild.


corpus_merge.sh: make macOS compatible

Tried running corpus_merge.sh and ran into some issues due to quirks of macOS.

When getting the number of inputs via wc -l, it would include whitespace. Now it gets piped to xargs to strip the whitespace.
When running the fuzz tests via measure_coverage, the current working directory was included along with the coverage bits.  sed is used to strip the non-numerical characters

cc @morehouse

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

@crypt-iq, remember to re-request review from reviewers when ready

Closing due to inactivity

Closing due to inactivity

Closing due to inactivity

!lightninglabs-deploy mute


[format] update orc version to support schema evolution filter push down, refactory OrcReaderFactory to combine "shema evolution" and "selected fields push down"

Purpose

Refactory OrcReaderFactory  to combine orc schema evolution and orc selected fields push down.
Orc version of 1.5.6 has problem in supporting filter push down while have a schema evolution(read schema is not compitable with orc file schema) This is a bug of orc version 1.5.6.  related issue: https://github.com/apache/orc/pull/452

Documentation
No influence to user in theory.
iceberg user 1.8.3 too

Done simple compatible test. It could read the data before.


Renamed cml to theta

Tested the change by adding a small model to a repository and pushing it to remote.

How did the git knows the file name has changed when you renamed? I thought it would tell git_cml files are deleted and git_theta files are added.

git knows the file name has changed when you renamed?

If you do git mv then git tracks it as a rename instead of a delete and add. I think sometimes it will also automatically do it sometimes but git mv is the most reliable way.

Thanks Brian for clarifying


Bump version in package.json to 0.2.0

cc: @dmajda @demmer
What do you think about adding a change log?


Feature/cluster management

This PR incorporates both the cluster registry and the distributed state registry. It'd be good to get it into master as soon as possible and add the unique provider on top of it a bit later

Coverage decreased (-62.5%) to 34.026% when pulling 56e30d9197b714207e64f7eeec43bf3783c2356d on feature/cluster-management into b026f5454834ec627cecd9740484f4e260f45cb1 on master.

Only found 3 small code improvs. Can merge