Revert "upgrade rabbitmq always to the latest management version"

Reverting:

#1099

I've tested it too quickly. Submissions does not work anymore both on my local instance and on the test server.
codabench-rabbit-1       | BOOT FAILED
codabench-rabbit-1       | ===========
codabench-rabbit-1       | Error during startup: {error,
codabench-rabbit-1       |                           {schema_integrity_check_failed,
codabench-rabbit-1       |                               [{table_attributes_mismatch,rabbit_user,
codabench-rabbit-1       |                                    [username,password_hash,tags,
codabench-rabbit-1       |                                     hashing_algorithm,limits],
codabench-rabbit-1       |                                    [username,password_hash,tags,
codabench-rabbit-1       |                                     hashing_algorithm]},
codabench-rabbit-1       |                                {table_missing,rabbit_topic_permission},
codabench-rabbit-1       |                                {table_attributes_mismatch,rabbit_vhost,
codabench-rabbit-1       |                                    [virtual_host,limits,metadata],
codabench-rabbit-1       |                                    [virtual_host,dummy]},
codabench-rabbit-1       |                                {table_missing,rabbit_index_route},
codabench-rabbit-1       |                                {table_attributes_mismatch,
codabench-rabbit-1       |                                    rabbit_durable_exchange,
codabench-rabbit-1       |                                    [name,type,durable,auto_delete,internal,
codabench-rabbit-1       |                                     arguments,scratches,policy,
codabench-rabbit-1       |                                     operator_policy,decorators,options],
codabench-rabbit-1       |                                    [name,type,durable,auto_delete,internal,
codabench-rabbit-1       |                                     arguments,scratches,policy,decorators]},
codabench-rabbit-1       |                                {table_attributes_mismatch,rabbit_exchange,
codabench-rabbit-1       |                                    [name,type,durable,auto_delete,internal,
codabench-rabbit-1       |                                     arguments,scratches,policy,
codabench-rabbit-1       |                                     operator_policy,decorators,options],
codabench-rabbit-1       |                                    [name,type,durable,auto_delete,internal,
codabench-rabbit-1       |                                     arguments,scratches,policy,decorators]},
codabench-rabbit-1       |                                {table_attributes_mismatch,
codabench-rabbit-1       |                                    rabbit_durable_queue,
codabench-rabbit-1       |                                    [name,durable,auto_delete,exclusive_owner,
codabench-rabbit-1       |                                     arguments,pid,slave_pids,sync_slave_pids,
codabench-rabbit-1       |                                     recoverable_slaves,policy,operator_policy,
codabench-rabbit-1       |                                     gm_pids,decorators,state,policy_version,
codabench-rabbit-1       |                                     slave_pids_pending_shutdown,vhost,options,
codabench-rabbit-1       |                                     type,type_state],
codabench-rabbit-1       |                                    [name,durable,auto_delete,exclusive_owner,
codabench-rabbit-1       |                                     arguments,pid,slave_pids,sync_slave_pids,
codabench-rabbit-1       |                                     recoverable_slaves,policy,gm_pids,
codabench-rabbit-1       |                                     decorators,state,policy_version]},
codabench-rabbit-1       |                                {table_attributes_mismatch,rabbit_queue,
codabench-rabbit-1       |                                    [name,durable,auto_delete,exclusive_owner,
codabench-rabbit-1       |                                     arguments,pid,slave_pids,sync_slave_pids,
codabench-rabbit-1       |                                     recoverable_slaves,policy,operator_policy,
codabench-rabbit-1       |                                     gm_pids,decorators,state,policy_version,
codabench-rabbit-1       |                                     slave_pids_pending_shutdown,vhost,options,
codabench-rabbit-1       |                                     type,type_state],
codabench-rabbit-1       |                                    [name,durable,auto_delete,exclusive_owner,
codabench-rabbit-1       |                                     arguments,pid,slave_pids,sync_slave_pids,
codabench-rabbit-1       |                                     recoverable_slaves,policy,gm_pids,
codabench-rabbit-1       |                                     decorators,state,policy_version]}]}}
codabench-rabbit-1       |
codabench-rabbit-1       |
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>   crasher:
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     initial call: application_master:init/4
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     pid: <0.229.0>
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     registered_name: []
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     exception exit: {{schema_integrity_check_failed,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                          [{table_attributes_mismatch,rabbit_user,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [username,password_hash,tags,hashing_algorithm,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                limits],
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [username,password_hash,tags,hashing_algorithm]},
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                           {table_missing,rabbit_topic_permission},
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                           {table_attributes_mismatch,rabbit_vhost,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [virtual_host,limits,metadata],
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [virtual_host,dummy]},
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                           {table_missing,rabbit_index_route},
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                           {table_attributes_mismatch,rabbit_durable_exchange,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [name,type,durable,auto_delete,internal,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                arguments,scratches,policy,operator_policy,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                decorators,options],
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [name,type,durable,auto_delete,internal,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                arguments,scratches,policy,decorators]},
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                           {table_attributes_mismatch,rabbit_exchange,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [name,type,durable,auto_delete,internal,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                arguments,scratches,policy,operator_policy,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                decorators,options],
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [name,type,durable,auto_delete,internal,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                arguments,scratches,policy,decorators]},
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                           {table_attributes_mismatch,rabbit_durable_queue,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [name,durable,auto_delete,exclusive_owner,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                arguments,pid,slave_pids,sync_slave_pids,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                recoverable_slaves,policy,operator_policy,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                gm_pids,decorators,state,policy_version,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                slave_pids_pending_shutdown,vhost,options,type,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                type_state],
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [name,durable,auto_delete,exclusive_owner,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                arguments,pid,slave_pids,sync_slave_pids,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                recoverable_slaves,policy,gm_pids,decorators,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                state,policy_version]},
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                           {table_attributes_mismatch,rabbit_queue,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [name,durable,auto_delete,exclusive_owner,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                arguments,pid,slave_pids,sync_slave_pids,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                recoverable_slaves,policy,operator_policy,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                gm_pids,decorators,state,policy_version,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                slave_pids_pending_shutdown,vhost,options,type,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                type_state],
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                               [name,durable,auto_delete,exclusive_owner,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                arguments,pid,slave_pids,sync_slave_pids,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                recoverable_slaves,policy,gm_pids,decorators,
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                                state,policy_version]}]},
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>                      {rabbit,start,[normal,[]]}}
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>       in function  application_master:init/4 (application_master.erl, line 142)
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     ancestors: [<0.228.0>]
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     message_queue_len: 1
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     messages: [{'EXIT',<0.230.0>,normal}]
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     links: [<0.228.0>,<0.44.0>]
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     dictionary: []
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     trap_exit: true
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     status: running
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     heap_size: 2586
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     stack_size: 28
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>     reductions: 197
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>   neighbours:
codabench-rabbit-1       | 2023-08-22 13:54:19.005245+00:00 [error] <0.229.0>
codabench-rabbit-1       | 2023-08-22 13:54:19.008063+00:00 [notice] <0.44.0> Application rabbit exited with reason: {{schema_integrity_check_failed,[{table_attributes_mismatch,rabbit_user,[username,password_hash,tags,hashing_algorithm,limits],[username,password_hash,tags,hashing_algorithm]},{table_missing,rabbit_topic_permission},{table_attributes_mismatch,rabbit_vhost,[virtual_host,limits,metadata],[virtual_host,dummy]},{table_missing,rabbit_index_route},{table_attributes_mismatch,rabbit_durable_exchange,[name,type,durable,auto_delete,internal,arguments,scratches,policy,operator_policy,decorators,options],[name,type,durable,auto_delete,internal,arguments,scratches,policy,decorators]},{table_attributes_mismatch,rabbit_exchange,[name,type,durable,auto_delete,internal,arguments,scratches,policy,operator_policy,decorators,options],[name,type,durable,auto_delete,internal,arguments,scratches,policy,decorators]},{table_attributes_mismatch,rabbit_durable_queue,[name,durable,auto_delete,exclusive_owner,arguments,pid,slave_pids,sync_slave_pids,recoverable_slaves,policy,operator_policy,gm_pids,decorators,state,policy_version,slave_pids_pending_shutdown,vhost,options,type,type_state],[name,durable,auto_delete,exclusive_owner,arguments,pid,slave_pids,sync_slave_pids,recoverable_slaves,policy,gm_pids,decorators,state,policy_version]},{table_attributes_mismatch,rabbit_queue,[name,durable,auto_delete,exclusive_owner,arguments,pid,slave_pids,sync_slave_pids,recoverable_slaves,policy,operator_policy,gm_pids,decorators,state,policy_version,slave_pids_pending_shutdown,vhost,options,type,type_state],[name,durable,auto_delete,exclusive_owner,arguments,pid,slave_pids,sync_slave_pids,recoverable_slaves,policy,gm_pids,decorators,state,policy_version]}]},{rabbit,start,[normal,[]]}}
codabench-rabbit-1       | {"Kernel pid terminated",application_controller,"{application_start_failure,rabbit,{{schema_integrity_check_failed,[{table_attributes_mismatch,rabbit_user,[username,password_hash,tags,hashing_algorithm,limits],[username,password_hash,tags,hashing_algorithm]},{table_missing,rabbit_topic_permission},{table_attributes_mismatch,rabbit_vhost,[virtual_host,limits,metadata],[virtual_host,dummy]},{table_missing,rabbit_index_route},{table_attributes_mismatch,rabbit_durable_exchange,[name,type,durable,auto_delete,internal,arguments,scratches,policy,operator_policy,decorators,options],[name,type,durable,auto_delete,internal,arguments,scratches,policy,decorators]},{table_attributes_mismatch,rabbit_exchange,[name,type,durable,auto_delete,internal,arguments,scratches,policy,operator_policy,decorators,options],[name,type,durable,auto_delete,internal,arguments,scratches,policy,decorators]},{table_attributes_mismatch,rabbit_durable_queue,[name,durable,auto_delete,exclusive_owner,arguments,pid,slave_pids,sync_slave_pids,recoverable_slaves,policy,operator_policy,gm_pids,decorators,state,policy_version,slave_pids_pending_shutdown,vhost,options,type,type_state],[name,durable,auto_delete,exclusive_owner,arguments,pid,slave_pids,sync_slave_pids,recoverable_slaves,policy,gm_pids,decorators,state,policy_version]},{table_attributes_mismatch,rabbit_queue,[name,durable,auto_delete,exclusive_owner,arguments,pid,slave_pids,sync_slave_pids,recoverable_slaves,policy,operator_policy,gm_pids,decorators,state,policy_version,slave_pids_pending_shutdown,vhost,options,type,type_state],[name,durable,auto_delete,exclusive_owner,arguments,pid,slave_pids,sync_slave_pids,recoverable_slaves,policy,gm_pids,decorators,state,policy_version]}]},{rabbit,start,[normal,[]]}}}"}
codabench-rabbit-1       | Kernel pid terminated (application_controller) ({application_start_failure,rabbit,{{schema_integrity_check_failed,[{table_attributes_mismatch,rabbit_user,[username,password_hash,tags,hashing_algorithm,limits],[username,password_hash,tags,hashing_algorithm]},{table_missing,rabbit_topic_permission},{table_attributes_mismatch,rabbit_vhost,[virtual_host,limits,metadata],[virtual_host,dummy]},{table_missing,rabbit_index_route},{table_attributes_mismatch,rabbit_durable_exchange,[name,type,durable,auto_delete,internal,arguments,scratches,policy,operator_policy,decorators,options],[name,type,durable,auto_delete,internal,arguments,scratches,policy,decorators]},{table_attributes_mismatch,rabbit_exchange,[name,type,durable,auto_delete,internal,arguments,scratches,policy,operator_policy,decorators,options],[name,type,durable,auto_delete,internal,arguments,scratches,policy,decorators]},{table_attributes_mismatch,rabbit_durable_queue,[name,durable,auto_delete,exclusive_owner,arguments,pid,slave_pids,sync_slave_pids,recove
codabench-rabbit-1       |
codabench-rabbit-1       | Crash dump is being written to: /var/log/rabbitmq/erl_crash.dump...done

codabench-site_worker-1  | [2023-08-21 16:43:15,266: ERROR/Beat] beat: Connection error: failed to resolve broker hostname. Trying again in 32.0 seconds...
codabench-site_worker-1  | [2023-08-21 16:43:45,521: ERROR/MainProcess] consumer: Cannot connect to amqp://rabbit-codabench-test:**@rabbit:5672//: [Errno 111] Connection refused.
codabench-site_worker-1  | Trying again in 32.00 seconds...
codabench-site_worker-1  |
codabench-site_worker-1  |
codabench-site_worker-1  | [2023-08-21 16:43:47,317: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 32.0 seconds...
codabench-site_worker-1  | [2023-08-21 16:44:17,604: ERROR/MainProcess] consumer: Cannot connect to amqp://rabbit-codabench-test:**@rabbit:5672//: failed to resolve broker hostname.
codabench-site_worker-1  | Trying again in 32.00 seconds...
codabench-site_worker-1  |
codabench-site_worker-1  |
codabench-site_worker-1  | [2023-08-21 16:44:19,390: ERROR/Beat] beat: Connection error: failed to resolve broker hostname. Trying again in 32.0 seconds...
codabench-site_worker-1  | [2023-08-21 16:44:49,687: ERROR/MainProcess] consumer: Cannot connect to amqp://rabbit-codabench-test:**@rabbit:5672//: failed to resolve broker hostname.
codabench-site_worker-1  | Trying again in 32.00 seconds...
codabench-site_worker-1  |
codabench-site_worker-1  |
codabench-site_worker-1  | [2023-08-21 16:44:51,463: ERROR/Beat] beat: Connection error: failed to resolve broker hostname. Trying again in 32.0 seconds...
codabench-site_worker-1  | [2023-08-21 16:45:21,775: ERROR/MainProcess] consumer: Cannot connect to amqp://rabbit-codabench-test:**@rabbit:5672//: failed to resolve broker hostname.
codabench-site_worker-1  | Trying again in 32.00 seconds...
codabench-site_worker-1  |
codabench-site_worker-1  |
codabench-site_worker-1  | [2023-08-21 16:45:23,534: ERROR/Beat] beat: Connection error: failed to resolve broker hostname. Trying again in 32.0 seconds...
codabench-site_worker-1  | [2023-08-21 16:45:53,855: ERROR/MainProcess] consumer: Cannot connect to amqp://rabbit-codabench-test:**@rabbit:5672//: failed to resolve broker hostname.
codabench-site_worker-1  | Trying again in 32.00 seconds...
codabench-site_worker-1  |
codabench-site_worker-1  |
codabench-site_worker-1  | [2023-08-21 16:45:55,601: ERROR/Beat] beat: Connection error: failed to resolve broker hostname. Trying again in 32.0 seconds...
codabench-site_worker-1  | [2023-08-21 16:46:25,918: ERROR/MainProcess] consumer: Cannot connect to amqp://rabbit-codabench-test:**@rabbit:5672//: failed to resolve broker hostname.
codabench-site_worker-1  | Trying again in 32.00 seconds...
codabench-site_worker-1  |
codabench-site_worker-1  |
codabench-site_worker-1  | [2023-08-21 16:46:27,675: ERROR/Beat] beat: Connection error: failed to resolve broker hostname. Trying again in 32.0 seconds...
codabench-site_worker-1  | [2023-08-21 16:46:57,993: ERROR/MainProcess] consumer: Cannot connect to amqp://rabbit-codabench-test:**@rabbit:5672//: failed to resolve broker hostname.
codabench-site_worker-1  | Trying again in 32.00 seconds...

@dtuantran

Maybe it's because your rabbitmq didn't stop proprely, then the rabbit database was crashed. You can remove all data in var/rabbit/ then execute docker compose down docker compose up -d again, it should works.


Music service integration / widgets

We have a very basic implementation of Spotify and Tidal widgets. Tidal supports OEmbed and that's something we should look into to better improve the integrations we have: https://oembed.com/

Reference: https://github.com/v0l/snort/pull/191


Where is the training code

Hello,i'm interested in this work，but i can't find the training code in your train.py.When will you submit your whole  training code ?it will be so grateful for me if you can share it public.Thanks!!

Hi! Thanks so much! train.py is complete. Feel free to use it with the mvd_train.yaml in the configs, but you may need to adjust the paths of the weights and dataset.


undefined reference to void mxnet::op::ElemwiseBinaryOp::DnsCsrDnsOp for GPU

Description
After switching to Ubuntu 22.04 with latest gcc/g++ v11 and CUDA 11.7 with NVIDIA driver 515.65.01 for Tesla V100S GPU cards I tried to compile mxnet 1.9.1 for our new environment because we need to get the R-package installed/updated as well. However, while most of the mxnet build seem to suceed fine, the build unfortunately stops right at trying to link img2rec with an error message mentioned in the next section. Trying to skip the img2rec build ends up in similar linker errors for other tools for which I could not find any solution. Also looking at similar issue tickets like https://github.com/apache/incubator-mxnet/pull/18761 and https://github.com/apache/incubator-mxnet/pull/18357 did not end up in a fix we could apply for the issue.
Any help in trying to solve this issue would be highly appreciated.
Error Message
$ cmake --build . --parallel 1
Consolidate compiler generated dependencies of target objects
[  8%] Built target objects
[  8%] Built target libzmq-static
Consolidate compiler generated dependencies of target dnnl_cpu_x64
[ 27%] Built target dnnl_cpu_x64
Consolidate compiler generated dependencies of target dnnl_common
[ 32%] Built target dnnl_common
Consolidate compiler generated dependencies of target dnnl_cpu
[ 41%] Built target dnnl_cpu
[ 41%] Built target dnnl
Consolidate compiler generated dependencies of target intgemm
[ 41%] Built target intgemm
[ 42%] Built target libomp-needed-headers
Consolidate compiler generated dependencies of target omp
[ 45%] Built target omp
Consolidate compiler generated dependencies of target dmlc
[ 46%] Built target dmlc
[ 46%] Built target proto_python
Consolidate compiler generated dependencies of target pslite
[ 47%] Built target pslite
Consolidate compiler generated dependencies of target mxnet
[ 94%] Built target mxnet
Consolidate compiler generated dependencies of target customop_lib
[ 94%] Built target customop_lib
Consolidate compiler generated dependencies of target transposecsr_lib
[ 94%] Built target transposecsr_lib
Consolidate compiler generated dependencies of target transposerowsp_lib
[ 95%] Built target transposerowsp_lib
Consolidate compiler generated dependencies of target subgraph_lib
[ 95%] Built target subgraph_lib
Consolidate compiler generated dependencies of target pass_lib
[ 95%] Built target pass_lib
Consolidate compiler generated dependencies of target customop_gpu_lib
[ 95%] Built target customop_gpu_lib
Consolidate compiler generated dependencies of target im2rec
[ 95%] Linking CXX executable im2rec
/usr/bin/ld: libmxnet.so: undefined reference to `void mxnet::op::ElemwiseBinaryOp::DnsCsrDnsOp<mxnet::op::mshadow_op::plus>(mshadow::Stream<mshadow::gpu>*, nnvm::NodeAttrs const&, mxnet::OpContext const&, mxnet::NDArray const&, mxnet::NDArray const&, mxnet::OpReqType, mxnet::NDArray const&, bool)'
/usr/bin/ld: libmxnet.so: undefined reference to `void mxnet::op::ElemwiseBinaryOp::DnsCsrDnsOp<mxnet::op::mshadow_op::minus>(mshadow::Stream<mshadow::gpu>*, nnvm::NodeAttrs const&, mxnet::OpContext const&, mxnet::NDArray const&, mxnet::NDArray const&, mxnet::OpReqType, mxnet::NDArray const&, bool)'
collect2: error: ld returned 1 exit status
gmake[2]: *** [CMakeFiles/im2rec.dir/build.make:130: im2rec] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:749: CMakeFiles/im2rec.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2

To Reproduce
This is the config.cmake file we are using to build mxnet 1.9.1 in our ubuntu 22.04 environment:
set(CMAKE_BUILD_TYPE "Distribution" CACHE STRING "Build type")
set(CFLAGS "-mno-avx" CACHE STRING "CFLAGS")
set(CXXFLAGS "-mno-avx" CACHE STRING "CXXFLAGS")
set(USE_CUDA ON CACHE BOOL "Build with CUDA support")
set(USE_CUDNN ON CACHE BOOL "Build with CUDA support")
set(USE_NCCL ON CACHE BOOL "Build with NCCL support")
set(USE_OPENCV ON CACHE BOOL "Build with OpenCV support")
set(USE_OPENMP ON CACHE BOOL "Build with Openmp support")
set(USE_MKL_IF_AVAILABLE OFF CACHE BOOL "Use Intel MKL if found")
set(USE_MKLDNN ON CACHE BOOL "Build with MKL-DNN support")
set(USE_LAPACK ON CACHE BOOL "Build with lapack support")
set(USE_TVM_OP OFF CACHE BOOL "Enable use of TVM operator build system.")
set(USE_SSE ON CACHE BOOL "Build with x86 SSE instruction support")
set(USE_F16C OFF CACHE BOOL "Build with x86 F16C instruction support")
set(USE_LIBJPEG_TURBO ON CACHE BOOL "Build with libjpeg-turbo")
set(USE_DIST_KVSTORE ON CACHE BOOL "Build with DIST_KVSTORE support")
set(MXNET_CUDA_ARCH "5.0;6.0;7.0;8.0;8.6" CACHE STRING "Cuda architectures")
set(CMAKE_CUDA_COMPILER "/usr/local/cuda-11.7/bin/nvcc" CACHE STRING "Cuda compiler")
set(OPENMP_FILECHECK_EXECUTABLE "/usr/lib/llvm-14/bin/FileCheck")
set(OPENMP_LLVM_LIT_EXECUTABLE "/usr/lib/llvm-14/build/utils/lit/lit.py")
set(USE_CPP_PACKAGE ON CACHE BOOL "Build C++ Package")
set(NCCL_ROOT "/usr/local/nccl" CACHE BOOL "NCCL install path. Supports autodetection.")

Steps to reproduce
(Paste the commands you ran that produced the error.)

cmake -DCMAKE_INSTALL_PREFIX=/usr/local/mxnet-1.9.1 ..
cmake --build . --parallel 20

What have you tried to solve it?

Tried to apply similar fixes like in https://github.com/apache/incubator-mxnet/pull/18357 or https://github.com/apache/incubator-mxnet/pull/18761 but to no avail.

Environment
n/a

Please note, that I am seeing the same/similar issue when trying to compile the older mxnet 1.9.0 in the same environment:
$ cmake --build . --parallel 1
Consolidate compiler generated dependencies of target objects
[  9%] Built target objects
[  9%] Built target libzmq-static
Consolidate compiler generated dependencies of target dnnl_cpu_x64
[ 25%] Built target dnnl_cpu_x64
Consolidate compiler generated dependencies of target dnnl_common
[ 28%] Built target dnnl_common
Consolidate compiler generated dependencies of target dnnl_cpu
[ 35%] Built target dnnl_cpu
[ 36%] Built target dnnl
Consolidate compiler generated dependencies of target intgemm
[ 36%] Built target intgemm
[ 37%] Built target libomp-needed-headers
Consolidate compiler generated dependencies of target omp
[ 40%] Built target omp
[ 40%] Built target proto_python
Consolidate compiler generated dependencies of target pslite
[ 40%] Built target pslite
Consolidate compiler generated dependencies of target mxnet_static
[ 91%] Built target mxnet_static
Consolidate compiler generated dependencies of target dmlc
[ 92%] Built target dmlc
Consolidate compiler generated dependencies of target mxnet
[ 92%] Built target mxnet
Consolidate compiler generated dependencies of target customop_lib
[ 92%] Built target customop_lib
Consolidate compiler generated dependencies of target transposecsr_lib
[ 92%] Built target transposecsr_lib
Consolidate compiler generated dependencies of target transposerowsp_lib
[ 93%] Built target transposerowsp_lib
Consolidate compiler generated dependencies of target subgraph_lib
[ 93%] Built target subgraph_lib
Consolidate compiler generated dependencies of target pass_lib
[ 94%] Built target pass_lib
Consolidate compiler generated dependencies of target customop_gpu_lib
[ 94%] Built target customop_gpu_lib
Consolidate compiler generated dependencies of target im2rec
[ 94%] Linking CXX executable im2rec
/usr/bin/ld: libmxnet.a(elemwise_binary_broadcast_op_basic.cu.o): in function `void mxnet::op::BinaryBroadcastComputeDenseEx<mshadow::gpu, mxnet::op::mshadow_op::minus>(nnvm::NodeAttrs const&, mxnet::OpContext const&, std::vector<mxnet::NDArray, std::allocator<mxnet::NDArray> > const&, std::vector<mxnet::OpReqType, std::allocator<mxnet::OpReqType> > const&, std::vector<mxnet::NDArray, std::allocator<mxnet::NDArray> > const&)':
tmpxft_001b66c6_00000000-6_elemwise_binary_broadcast_op_basic.compute_80.cudafe1.cpp:(.text._ZN5mxnet2op29BinaryBroadcastComputeDenseExIN7mshadow3gpuENS0_10mshadow_op5minusEEEvRKN4nnvm9NodeAttrsERKNS_9OpContextERKSt6vectorINS_7NDArrayESaISE_EERKSD_INS_9OpReqTypeESaISJ_EESI_[_ZN5mxnet2op29BinaryBroadcastComputeDenseExIN7mshadow3gpuENS0_10mshadow_op5minusEEEvRKN4nnvm9NodeAttrsERKNS_9OpContextERKSt6vectorINS_7NDArrayESaISE_EERKSD_INS_9OpReqTypeESaISJ_EESI_]+0x34c): undefined reference to `void mxnet::op::ElemwiseBinaryOp::DnsCsrDnsOp<mxnet::op::mshadow_op::minus>(mshadow::Stream<mshadow::gpu>*, nnvm::NodeAttrs const&, mxnet::OpContext const&, mxnet::NDArray const&, mxnet::NDArray const&, mxnet::OpReqType, mxnet::NDArray const&, bool)'
/usr/bin/ld: libmxnet.a(elemwise_binary_broadcast_op_basic.cu.o): in function `void mxnet::op::BinaryBroadcastComputeDenseEx<mshadow::gpu, mxnet::op::mshadow_op::plus>(nnvm::NodeAttrs const&, mxnet::OpContext const&, std::vector<mxnet::NDArray, std::allocator<mxnet::NDArray> > const&, std::vector<mxnet::OpReqType, std::allocator<mxnet::OpReqType> > const&, std::vector<mxnet::NDArray, std::allocator<mxnet::NDArray> > const&)':
tmpxft_001b66c6_00000000-6_elemwise_binary_broadcast_op_basic.compute_80.cudafe1.cpp:(.text._ZN5mxnet2op29BinaryBroadcastComputeDenseExIN7mshadow3gpuENS0_10mshadow_op4plusEEEvRKN4nnvm9NodeAttrsERKNS_9OpContextERKSt6vectorINS_7NDArrayESaISE_EERKSD_INS_9OpReqTypeESaISJ_EESI_[_ZN5mxnet2op29BinaryBroadcastComputeDenseExIN7mshadow3gpuENS0_10mshadow_op4plusEEEvRKN4nnvm9NodeAttrsERKNS_9OpContextERKSt6vectorINS_7NDArrayESaISE_EERKSD_INS_9OpReqTypeESaISJ_EESI_]+0x14de): undefined reference to `void mxnet::op::ElemwiseBinaryOp::DnsCsrDnsOp<mxnet::op::mshadow_op::plus>(mshadow::Stream<mshadow::gpu>*, nnvm::NodeAttrs const&, mxnet::OpContext const&, mxnet::NDArray const&, mxnet::NDArray const&, mxnet::OpReqType, mxnet::NDArray const&, bool)'
collect2: error: ld returned 1 exit status
gmake[2]: *** [CMakeFiles/im2rec.dir/build.make:125: im2rec] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:783: CMakeFiles/im2rec.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2

Perhaps anyone has a clue where this might originate from!?!?

After some further investigation I actually found the config option that seems to trigger the mentioned undefined reference linker error. It is the USE_DIST_KVSTORE config option that - if enabled - seem to trigger these error messages within the environment. Thus, setting it to OFF...
set(USE_DIST_KVSTORE OFF CACHE BOOL "Build with DIST_KVSTORE support")

seem to help and the linker error goes away. However, it is still unclear why this config option seem to trigger the mentioned linker error.


(kitty) Add "00" postfix to version

Description
Kitty uses the fourth version part. Add "00" so we can issue updates, in accordance with https://github.com/chocolatey/choco/wiki/CreatePackages#versioning-recommendations
How Has this Been Tested?
Ran update.ps1 locally
Screenshot (if appropriate, usually isn't needed):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[ ] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

Thank you for the interest of updating this package.
Unfortunately this change won't really do much, as a maintainer with write access to the repository would need to force the update instead (and using a helper to set the correct fix version).
I will be closing this PR, as I am almost ready with a few changes to the updater and will then force a new package update.


Allow keeping stdout/stderr separated when rendering helm templates

We have some use cases where rendering helm charts with overridden values causes helm to produce warnings on stderr, but otherwise finishes successfully. We use the helm.RenderTemplate() method to perform this rendering. Unfortunately, the method only supports returning the combined stdout+stderr and this causes our subsequent UnmarshalK8SYaml() call to fail because the text is no longer valid YAML.
It would be nice if the method could be called while keeping the two output streams separated. A couple of ideas are to either create a second method that works this way, or perhaps passing an option to the current method to allow this behavior.

That's a good point. Is returning stderr ever useful with the RenderTemplate method? Or is that just a bug, and only stdout should be returned? A PR to improve/fix this is very welcome!


[new-rule-option] no-space-keywords for comment-format

PR checklist

[x] Addresses an existing issue: #3951
[x] New feature, bugfix, or enhancement

[x] Includes tests

[ ] Documentation update

Overview of change:
You can add a new object in comment-format to add some exceptions for checking special keywords that can ignore the check-space option
e.g.:
{"comment-format": [true, "check-space", {"no-space-keywords": ["TODO", "FIXME"]}]}

// some comment
//TODO: my todo

There is a check that allows an optional colon at the end of the keyword
Is there anything you'd like reviewers to focus on?

Using of in on line 183
Line 241 to 248

CHANGELOG.md entry:

[new-rule-option] no-space-keywords in comment-format

The formatting in my last push was prettier #4012

Please see #4141 before you contribute to this project. Thank you!

Will look into the conflict in the next few days

Hmm, looks like the changes in this PR are actually already resolved by the ignore-pattern option in #3583. There are some pretty substantial merge conflicts here that are otherwise nontrivial to resolve as well. Closing this PR for housekeeping.
Please comment here or in #3951 if you think that's a mistake and you'd like this PR to be re-opened!

I'm with your desicion.


DOC: fix evaluate_all_bspl example.

the first argument of evaluate_all_bspline need to be an array and
not a list, or it crashes:
File "_bspl.pyx", line 163, in scipy.interpolate._bspl.evaluate_all_bspl
File "stringsource", line 658, in View.MemoryView.memoryview_cwrapper
File "stringsource", line 349, in View.MemoryView.memoryview.cinit
TypeError: a bytes-like object is required, not 'list'

So fix it.

The initial values were I believe wrong (2 was present twice)

Matplotlib default are sane-er now, so use default color, and reduce
lw a bit.

Also add label for basis element

[ci skip]
[skip azp]
[skip circle]

Give this when run separately FYI.

Note that I don't think this function is exposed in the docs ?

Thanks Matthias! This is what happens when examples are not refguide-checked, thanks for fixing it and for modernizing the mpl incantations.


Support XIAOMI MIJIA Temp and Humidity Sensor v2

Support for the recently announced Temp and Humidity Sensor of Xiaomi with Bluetooth and LCD display.
I did not want to duplicate all the back-end code, thus added support for an extra sensor in this package.
To be fully used, it needs a file called site-packages/homeassistant/components/sensor/mitemp.py that is just a slightly amended version of the miflora.py, available here: https://gist.github.com/ratcashdev/2060fd95158dacae93a80a92ae7083a4

Coverage decreased (-1.2%) to 91.517% when pulling b87cf2d630ed684a212c962ea9c24f62db1d3e0d on ratcashdev:master into 4cca1a25e7e9dadd5727fe936c260278935eb92b on open-homeautomation:master.

please advice how to make this code mergeable.

@ThomDietrich , @open-homeautomation
Does it make sense to add support for the "XIAOMI MIJIA Temp and Humidity Sensor v2" into this library? From looking at the code there are quite a few similarities, but it would certainly extend the scope of this library from the plant sensors.

IMHO, the best solution would be to extract all the back-end code into a separate package and then make both miflora and mitemp require those. I assume a lot of other sensor offering bluetooth and their implementation would benefit from a common back-end providing 3 different implementation options (bluepy, pygatt, gatttool).

@ratcashdev
I started extracting the backend funktionality: https://github.com/ChristianKuehnel/btlewrap
This is from the current master branch, without your notification extensions...

Lovely! Let me know when that is merged and I will submit a separate PR for the notification enhancements.

I had the same idea, but 16 days later...:-) Anyway, I would like to help. My Home assistant installation has already my version of the mitemp_bt Sensor (so I called it) and I've putted all in a single python file using only gatttool

@ratcashdev
The bluetooth backend library is ready to get your notifications merged: https://github.com/ChristianKuehnel/btlewrap
And you can use it to build a new library to the Xiaomi Mijia sensors

PR submitted: https://github.com/ChristianKuehnel/btlewrap/pull/1

I got the mitemp implementation ready with btlewrap==0.0.2 (https://github.com/ratcashdev/mitemp)
A couple of notes though:

This is my very first python package, I have no account on travis, pypi, coverage, etc. I was wondering, if anyone is willing to do the publishing?
I am still undecided on the naming. @flavio20002 's mitemp_bt sounds better, honestly as is mitemp_ble
What do you suggest?

Hi, thank you very much. I like both names, but I prefer "bt" beacuse it's more known. Once published, I will test in my Home-asssistant. Did you update the Hass component with the right dependence (the gist version has still miflora)? Thanks

repo and gist updated. See the readme for the gist's link.
The new name is mitemp_bt

so back to the publishing question: Is anyone volunteering to publish?

All right. mitemp_bt==0.0.1 is available and can be integrated into hass using https://gist.github.com/ratcashdev/28253bb2c220788e4961f213fe87ff33

Thank you very much. Are you pllaing to PR to Home Assistant? Some notes:

I would put a default median of 1, since the Mijia Temperature Sensor doesn't have spikes like miflora.
My own implementation works very good (I have used it in production for 1 month), but I always got warning in my log Update of sensor.mijia is taking over 10 seconds Does your implementation suffer of the same problem, or did you manage to solve it?
I'm available to test your implementation in my environment, if you plan to make it the official Home Assistant one.
Thanks

@flavio20002

I'd rather leave it. while I haven't encountered cases when it would have spikes, batter safe than sorry
I am using it for more than a month. However, I can confirm, I have the same log entries like you (>10s). It seems to me that sometimes the device is too slow to respond to connection requests.
I am afraid i am not the one to make it official, but I will for sure create a PR.

The PR is here https://github.com/home-assistant/home-assistant/pull/13955


Image download issue

I have a strong internet connection.
I don't know what to do, to fix that.
Downloaded never end.
Version: 2
May this help: https://github.com/gatsbyjs/gatsby/issues/14173#issuecomment-500702399 ?

Add GATSBY_CONCURRENT_DOWNLOAD before gatsby develop
GATSBY_CONCURRENT_DOWNLOAD=1 gatsby develop

@RobinHerzog I tried but the problem is still here. Any Hint?


multi: switch over all imports to depend on btcsuite proper, no longer the roasbeef forks

A small step for roasbeef, a giant leap for mankind!
Looks like one of the wallet tests is failing though:
--- FAIL: TestLightningWallet/btcwallet/neutrino:transaction_details (0.93s)
    	interface_test.go:1002: unable to create burn tx: Transaction fbdd22fc6dd3c773f18f9e21c5fc7337630b53444d19f4d9035669fe3af398f4 rejected by <IP_ADDRESS>:16260: already have transaction fbdd22fc6dd3c773f18f9e21c5fc7337630b53444d19f4d9035669fe3af398f4

A call to SendOutputs produces the error. Is there a difference between the forks how the tx is created?

Hmm, will look into that. First will get in a few of these mostly read PRs as it'll be a pain to rebase on top of this.


Fixed an issue where DV Hydrograph was incorrectly requiring report…

…data to include a station name.

Coverage decreased (-0.0003%) to 99.039% when pulling 60880e2a986b04103ae58082727e7e7634c6180d on zmoore-usgs:hotfix-1.2.2 into 4281ac6f6db8e9bf45e947c9fd58fc74c03341ff on USGS-R:hotfix-1.2.2.


Check PersistentVolumeLabel admission controller status for kube-apiserver

Rancher versions:
rancher/server: v1.6.11
Infrastructure Stack versions:
kubernetes (if applicable): v1.8.3-rancher2
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes
Steps to Reproduce:

Add a host to Kubernetes environment

Results:
kube-apiserver will log:
PersistentVolumeLabel admission controller is deprecated. Please remove this controller from your configuration files and scripts.

References:
https://github.com/kubernetes/kubernetes/pull/44680
https://github.com/kubernetes/features/issues/88
https://kubernetes.io/docs/admin/admission-controllers/#persistentvolumelabel

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Cannot load example file

Thanks for the great HDA!I enjoy using it very much!
I installed HDA and downloaded your sample file from Github, but I get an error.
The Hpaint SOP comes up, but I get an error when I load it.
What should I do?

Hey @taec12 thanks for submitting this issue! It looks like the HPaint HDA version in the example hasn't been updated from 1.2 to 2.0, so I think you will have to download and install 1.2 in order to get it working. I'll have a look at updating the examples :)

Thank you for your quick response!!
I'll try to get the same version of HPaint.
I would be very happy if you could upgrade examples as well!
Thanks for developing this interesting HDA :))


Building tcc with pnut

In the readme file it indicates that pnut.exe is capable of building tcc. I can't seem to figure out how to actually do that though. Can you please advise whether this is possible? Simply passing --cc=pnut.exe to the tcc configure script won't work:
configure: error: 'pnut.exe' failed to compile conftest.c

If I try this (which works with gcc after the configure script has been run):
pnut.exe tcc.c

I get the following error:
codegen_glo_decl: unexpected declaration

I'm using a stock tcc 0.9.27 release from 2017 (rather than a random version of their mob branch). Same issue when i use the i386 backend.

We're still working on TCC support. I'll update the README because pnut-exe is not yet able to compile it.

Thanks, it's good to know that tcc is one of your aims. It will be good to have another C compiler that is capable of bootstrapping tcc.
Are you aware of the live-bootstrap project (https://github.com/fosslinux/live-bootstrap/)? They bootstrap from a couple of hundred bytes of commented machine code all the way up to modern versions of GCC. tcc is part of their bootstrap chain. They use a "bootstrapable" version of tcc 0.9.26 (https://gitlab.com/janneke/tinycc (mes-0.27 branch I think) which is actually closer to 0.9.27 than 26). This version of tcc can be built by mescc (which is a C compiler written in scheme). I mention this because their bootstrapable version can be built by simplified C compilers and is used as a stepping stone to a stock 2017 era tcc-0.9.27 release (and then on to modern versions of gcc).
Live Bootstrap actually goes through several C compilers on its way to tcc:
cc_x86 (a C compiler written in a simple macro assembly language. There are also other arch versions)
M2-Planet (a C compiler written in the cc_x86 dialect)
mescc (a C compiler written in scheme that is run in a scheme interpreter (mes.c) written in the M2-Planet dialect of C)
I have also been working on a means of bootstrapping tcc but replacing mescc with a chain of previous versions of tcc (plus some cut down versions of tcc). My project is very i386 specific, but it can bootstrap from nothing up to tcc 0.9.27 much more quickly than live-bootstrap (by eliminating the use of mescc). https://github.com/cosinusoidally/tcc_bootstrap_alt . The thing that got me interested in pnut is potentially allowing me to eliminate some intermediate versions of tcc from my project.


feat: add lazy loading to images

use native web lazy load attribute to optionally enable lazy loading all images for better performance
https://web.dev/native-lazy-loading/

hi! updated docs, version number and generated new build. let me know if there is anything else thats needed. i think it will be useful for everyone, might even be worth turning on be default for the good of web performance :)

Thank you!


Add MariaDB addon

This PR adds MariaDB addon, based on instructions given at https://downloads.mariadb.org/mariadb/repositories/#mirror=digitalocean-nyc&distro=Ubuntu&distro_release=precise&version=10.0.
Versions 5.5, 10.0, and 10.1 can be specified in .travis.yml; e.g.,
addons:
  mariadb: "10.0"

Note that MariaDB is installed with the package-provided configuration file -o Dpkg::Options::='--force-confnew', so that it is run on disk, not ramfs, so it can be potentially slow.
User travis needs to be set up, but for some reason root cannot.
travis@debug-BanzaiMan-playing-around-php-1412545209:~$ mysql -u root
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 252
Server version: 10.0.14-MariaDB-1~precise-log mariadb.org binary distribution

Copyright (c) 2000, 2014, Oracle, SkySQL Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> CREATE USER 'travis'@'%' IDENTIFIED BY '';          GRANT ALL PRIVILEGES ON *.* TO 'travis'@'%';
ERROR 1396 (HY000): Operation CREATE USER failed for 'travis'@'%'
Query OK, 0 rows affected (0.00 sec)

' CREATE USER 'travis'@'%' IDENTIFIED BY '';' failing would indicate that the travis user already exists supported by the fact the grant succeeded.
What does 'but for some reason root cannot.' mean? it appears you have a root user. Can you show select user,host,password from mysql.user and show grants in the test buiild?

also mysql_upgrade might be running in the background (/etc/mysql/debian-start) meaning some of the system table structure may not be fully ready for changes.

Picked this up again, and it seems to work with my limited testing.
https://staging.travis-ci.org/BanzaiMan/travis_staging_test/builds/433699#L205 (10.0.20)
https://staging.travis-ci.org/BanzaiMan/travis_staging_test/builds/433701#L214 (10.1.5)
I don't have an app to run it through more rigorous testing, though.
I do not like it that the Ubuntu release code name is hard coded at the moment.

Provided the following return the right user and a mariadb version it should be ok

mysql -u root -e 'SELECT VERSION(); SELECT CURRENT_USER();'
mysql -u travis -e 'SELECT VERSION(); SELECT CURRENT_USER();'

I do not like it that the Ubuntu release code name is hard coded at the moment.

sh.cmd "add-apt-repository 'deb http://#{MARIADB_MIRROR}/mariadb/repo/#{mariadb_version}/ubuntu ${TRAVIS_UBUNTU_RELEASE} main'", sudo: true

TRAVIS_UBUNTU_RELEASE is in a single quote when run so its not interpolated.

@grooverdan Yay. User creds seem to work. https://staging.travis-ci.org/BanzaiMan/travis_staging_test/builds/433703
I'll revisit the release code name tomorrow.

thanks for revisiting this. Looks good.

Cool. it worked.

https://staging.travis-ci.org/BanzaiMan/travis_staging_test/builds/433803#L221

By rough accounting, it adds about 30 seconds to the build.

@henrikhodne @meatballhat can you review the PR pretty please

@grooverdan Hello! We have deployed this to production (both .org and .com; not yet documented). Could you test this and see if it works to your satisfaction? We would like to get documentation ready, very much like what we have for MySQL. Could you review the documentation, and see if there are any notable differences between MySQL and MariaDB? (Please open a separate issue if you find any!)
Thank you for your help!

@BanzaiMan :+1: thank you
basic support on 5.5, 10.0 and 10.1 looks great.
single list form resulted in [5.5] as the version and hence didn't install 5.5.
multiple list form seemed to ignore all repos and resort to mysql.
My guess on a matrix form was silently ignored.
A multiple list form would be really nice to test an application against multiple versions.
Is having none as a item in a list acceptable to revert to the installed MySQL so an application can be test against mariadb versions and mysql.
Minor note, Is the exclude/include syntax of travis-ci/travis-ci/issues/1492 supported somehow? It will be useful when multiple MySQL versions to exclude a matrix where MariaDB and MySQL versions get installed.
For container builds having /etc/mysql writeable would be useful - its currently root owned. To protect against users running items as root a check will need to be done to ensure there isn't user= set in a [mysqld_safe] or [safe_mysqld] section (its the OS user that mysqld will start at and by pushing user plugins they could effectively escalate to root). Look for --user= in the output of my_print_defaults --loose-verbose mysqld_safe safe_mysqld mariadb_safe. Using the MySQL version of my_print_defaults is sufficient for this test.
Is there a stage where custom config files can be pushed into /etc/mysql/ so they are there when the package is installed and hence the service started? Its quite possible to install config files there that will affect mariadb and not mysql (putting config files having sections [mariadb] [mariadb-10.0], [mariadb-5.5], [mariadb-10.1] (which is something that would be useful to document).
Exporting in an environment variable which mariadb version was installed would enable a user to do specific scripts/actions/configs/tests for mariadb that might not be accessible on MySQL (or vise versa).
Apart from the minor tip on introducing mariadb specific configuration I can't see anything that would be useful to include in travis documentation.
Sorry if this contains a little too many feature requests. Its a great capability to start with so thank you.

think I worked out to do matrix builds, not perfect but getting closer

@BanzaiMan  did you want the above broken up to separate feature requests?

@grooverdan Yes, please. This is a PR, and feature requests tend to be lost here.

#4552  #4553  #4554  #4555 refers. Thanks again.

Just wanted to say thanks, I've started testing this with WordPress, works as expected :+1:


improve test coverage.  Restore channels based on uploads

Codecov Report

Merging #24 into master will decrease coverage by 5.1%.
The diff coverage is 64%.

@@           Coverage Diff            @@
##           master     #24     +/-   ##
========================================
- Coverage    85.2%   80.1%   -5.1%
========================================
  Files           6       6
  Lines         690     690
========================================
- Hits          588     553     -35
- Misses        102     137     +35

Impacted Files
Coverage Δ

conda_concourse_ci/uploads.py
95.3% <0%> (+5.8%)
:arrow_up:

conda_concourse_ci/execute.py
68.2% <66.7%> (-6.6%)
:arrow_down:

conda_concourse_ci/compute_build_graph.py
88.1% <80%> (-9.2%)
: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 2a3455e...77e8f4d. Read the comment docs.

Codecov Report

Merging #24 into master will decrease coverage by 5.1%.
The diff coverage is 64%.

@@           Coverage Diff            @@
##           master     #24     +/-   ##
========================================
- Coverage    85.2%   80.1%   -5.1%
========================================
  Files           6       6
  Lines         690     690
========================================
- Hits          588     553     -35
- Misses        102     137     +35

Impacted Files
Coverage Δ

conda_concourse_ci/uploads.py
95.3% <0%> (+5.8%)
:arrow_up:

conda_concourse_ci/execute.py
68.2% <66.7%> (-6.6%)
:arrow_down:

conda_concourse_ci/compute_build_graph.py
88.1% <80%> (-9.2%)
: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 2a3455e...77e8f4d. Read the comment docs.


Fixed typo in the event handler example.

@tim-weis : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Align fmt_hex_exact and Display impls

fmt_hex_exact accounts for precision.
DisplayArray and DisplayByteSlice add the "0x" prefix if the '#' (alternate) flag is set.
Close #83

I set it in draft for now - this is where I am currently, but I understand there may be concerns with this direction.
I keep the core display engines of fmt_hex_exact and DisplayArray / DisplayByteSlice separate: fmt_hex_exact takes advantage of operating on a known length array, and DisplayArray / DisplayByteSlice take advantage of operating on a &[u8].
write_pad_left and write_pad_right implement the common padding functionality in both cases.

Hello, here I've split the PR into likely too many commits - happy to squash later, but I hope this helps clarify what I'm doing.
    if pad_right > 0 {
        write_pad_right(/* ... */)?;
    }

I prefer to keep that if statement inside the write_pad_right function to guard against division by 0. Otherwise, we could do as show above, and add an assert statement inside the function ?
write_data(/* ... */)?;

Here I prefer to avoid creating a new function if that function only gets called in a single place throughout the codebase.

Man this is awesome, super easy to review now. Well done. Since you've made it this far how abouth throwing a unit test after each of the last 2 patches that test the changes. We put the unit test after the patch that does the fix so that reviewers can re-order the patch set and verify that the unit test is actually broken.

This is a nice patch set, top effort. You even made all the test code uniform, my man!

I thank you for your encouragement and guidance.
Happy to help push this library to 1.0.


Register custom ValueConverter for implicit conversion

The docs mention there is no need to specify a converter explicitly when there is a built-in converter. Is it possible to somehow register custom converters to behave the same way?
For example, I have a custom UriToStringConverter class that I would like to use for multiple Uri properties. Currently, I register the converter for every Uri property separately. I don't know if this is something that's possible but missing from the docs (clearly, it works for built-in converters) or if this is a missing feature.

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

ID: 03dfe9f6-e831-ac3f-0b90-acb9b4c0f828
Version Independent ID: a26156d1-a4b3-7df0-e63e-b8e9f804abbf
Content: Value Conversions - EF Core
Content Source: entity-framework/core/modeling/value-conversions.md
Product: entity-framework
GitHub Login: @ajcvickers
Microsoft Alias: divega

@Vivelin This is being tracked by https://github.com/aspnet/EntityFrameworkCore/issues/10784


Python bugs are not supported

When trying to build a .bugzoo.yml file for a bug with language python (or py), and then running bugzoo source update, the command fails.
No errors are printed to the console, but the log file contains the following error.
ERROR:bugzoo.mgr.source:2018-07-05 15:41:28,390: missing property in bug description: 'PYTHON'
Traceback (most recent call last):
  File "/home/andre/robust/lib/python3.5/site-packages/bugzoo/mgr/source.py", line 211, in __parse_file
    bug = self.__parse_bug(source, fn, description)
  File "/home/andre/robust/lib/python3.5/site-packages/bugzoo/mgr/source.py", line 183, in __parse_bug
    [Language[lang] for lang in d['languages']],
  File "/home/andre/robust/lib/python3.5/site-packages/bugzoo/mgr/source.py", line 183, in <listcomp>
    [Language[lang] for lang in d['languages']],
  File "/home/andre/robust/lib/python3.5/site-packages/bugzoo/core/language.py", line 6, in __getitem__
    return super().__getitem__(name.upper())
  File "/usr/lib/python3.5/enum.py", line 277, in __getitem__
    return cls._member_map_[name]
KeyError: 'PYTHON'

Is it safe to use cpp as a workaround, or does it influence the outcome?

For reference, the problematic bug is robust:5ee65b0.

It's fine to use cpp as a workaround for now. The only area where language has any influence is on the generation of coverage information, which isn't currently supported for Python programs. I'll get BugZoo to report a reasonable error message to the terminal. Do you mind sharing the complete command that you passed to BugZoo so that I can quickly test a fix? :)

It's fine to use cpp as a workaround for now.

Alright. Will try that.
I just ran bugzoo source update, after having already a local repository registered as a source.

And here is the manifest I was trying to add, if it matters.
version: '1.0'

blueprints:
  - type: docker
    tag: robustrosin/robust:5ee65b0
    file: ../../Dockerfile
    arguments:
      IS_BUILD_FAILURE: "no"
      USE_APT_OLD_RELEASES: "no"
      UBUNTU_VERSION: trusty
      ROS_DISTRO: indigo
      CATKIN_PKG: kobuki_dashboard
      REPO_FORK_URL: https://github.com/robust-rosin/kobuki_desktop
      REPO_BUG_COMMIT: 37a1eee5ce2642144735102ffcd4c3736c4b2850
      REPO_FIX_COMMIT: d852bd6dbc24c7096bd6f042739725b894359494

bugs:
  - name: robust:5ee65b0
    image: robustrosin/robust:5ee65b0
    program: kobuki_dashboard
    dataset: robust
    languages:
      - python
    source-location: /ros_ws/src
    test-harness:
      type: empty
    compiler:
      type: catkin
      workspace: /ros_ws/src
      time-limit: 300


Fix the nanopb's header include issue

Several files in C core includes nanopb in the quote fashion:
#include "third_party/nanopb/xxx.h"

This works locally when we have nanopb in third_party directory as a submodule, but does not work if the pod is downloaded remotely because there is not a directory structure third_party/....
This PR changes all these include sentences into bracket fashion when Cocoapods downloads the files:
#include <nanopb/xxx.h>

This corrects the build problem, and only affects Objective C build.

test this please

Test failures:
gRPC_interop_pull_requests - all tests passed


Sign up

Lets a user sign up

[] Username
[] Email
[] Password
[] Confirm Password
[] Returns a unique token.

add assigne


include: don't erroneously remove headings if hidefirstheading=true

# Titel

## Heading

Text

### Subheading

Some more text

Heading will be erroneously removed using hidefirstheading=true

Ah, I understand better why I didn't see included pages' titles and this bugged me. Will update and enjoy.

Just to be clear: If you want to include the file unmodified, just omit the second parameter.
https://mcshelby.github.io/hugo-theme-relearn/shortcodes/include/index.html

Well, there is something I still don't understand. I omit parameter yet but neither the title nor a # or ## heading shows up when the page is included. In my case it's a cascading inclusion like this:
Main page:
https://github.com/poesieland/poesieland.github.io/blob/7c71980cae32a4c8d9dcb94eece99942b14d95c9/content/fr/_index.md?plain=1#L8-L10
First inclusion:
https://github.com/poesieland/poesieland.github.io/blob/ba387b39631ff5bbf243452d869265774b25eea1/content/fr/includes/last_thought.md?plain=1#L2-L4
Included file:
https://github.com/poesieland/poesieland.github.io/blob/main/content/fr/thoughts/20240911.md?plain=1
In this last file, I tried adding a # or ## or ### heading but nothing shows on main page. Do you have time to play with it?

Hi Barbara! In https://github.com/poesieland/poesieland.github.io/blob/7c71980cae32a4c8d9dcb94eece99942b14d95c9/content/fr/_index.md?plain=1#L8-L10 you are still calling the include shortcode with the second parameter. If you  remove that, you should see all headings.


feat: Add author and category to WorkOS preset

Making it a little bit more dynamic ;)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.436%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
68

Relevant Lines:
68

💛  - Coveralls


sendDigits

Hi there. I'm a total newbie in programming so I'd like some help. I'm developing an IOS app and I've followed the Twilio Voice Quickstart for iOS tutorial.
Everything is fine and the app is working, but I'm not sure if what I did is correct as to how to send DTMF signals.
In my code when the user taps a button the signal is sent, as in the example bellow:
@IBAction func sendTwo(_ sender: UIButton) {
	if let call = self.activeCall {
        call.sendDigits("2")
    }
}

But in another post (https://github.com/twilio/voice-quickstart-ios/issues/216), this action was recommended:

(void)provider:(CXProvider *)provider performPlayDTMFCallAction:(CXPlayDTMFCallAction *)action {
[self.call sendDigits:action.digits];
[action fulfill];
}

Although my app seems to be working fine, I'd like to know if I have to do something different, like using the following delegate method of the CXProviderDelegate protocol. And, if yes, how should I code it?
func provider(_ provider: CXProvider, perform action: CXPlayDTMFCallAction) {

}

Hi @vpcunha
Thanks for reaching out and it's nice that you were able to follow the guide and built your working Voice app!
The method you implemented is correct. The implementation in the CXProvider callback method is to fulfill the action when the user taps on the system call UI when the call is integrated with the CallKit framework.

Ok.
Thanks a lot for the prompt answer!


Dependency repository

I have all this repositories in my gradle config and still can't find the artifact
allprojects {
  repositories {
    jcenter()
    google()
    maven { url 'https://zendesk.artifactoryonline.com/zendesk/repo' }
  }
}

And i'm getting
> Could not find com.zendesk:ratemyapp:1.0.0.
  Searched in the following locations:
      file:/Users/robert/software/android-sdk/extras/m2repository/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.pom
      file:/Users/robert/software/android-sdk/extras/m2repository/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.jar
      file:/Users/robert/software/android-sdk/extras/google/m2repository/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.pom
      file:/Users/robert/software/android-sdk/extras/google/m2repository/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.jar
      file:/Users/robert/software/android-sdk/extras/android/m2repository/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.pom
      file:/Users/robert/software/android-sdk/extras/android/m2repository/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.jar
      https://jcenter.bintray.com/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.pom
      https://jcenter.bintray.com/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.jar
      https://dl.google.com/dl/android/maven2/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.pom
      https://dl.google.com/dl/android/maven2/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.jar
      https://jitpack.io/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.pom
      https://jitpack.io/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.jar
      https://zendesk.artifactoryonline.com/zendesk/repo/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.pom
      https://zendesk.artifactoryonline.com/zendesk/repo/com/zendesk/ratemyapp/1.0.0/ratemyapp-1.0.0.jar

Where is the library artifact hosted?

Hey @robertoestivill, see the referenced PR, that should do it. Artifactory changed to Jfrog back in June or thereabouts, and it looks like this repo slipped through without being updated. Can you try running that branch and see if it works as expected for you?

Hi @robertoestivill, that's been merged to master now. Have you gotten a chance to try it out yet?

@brendan-fahy I am having the same issue "Error:Failed to resolve: com.zendesk:ratemyapp:1.0.0"

@brendan-fahy I finally got time to revisit this and it is still failling.
There's no com.zendesk:ratemyapp:1.0.0 artifact on the repo:
../
belvedere/          13-Nov-2015 09:48    -
belvedere2/         30-Jan-2017 18:09    -
core/               08-Nov-2017 13:43    -
java-common/        03-Jun-2015 15:20    -
java-common-test/   09-Aug-2016 09:23    -
sdk/                13-Jun-2014 14:11    -
sdk-core/           19-Oct-2016 14:04    -
sdk-providers/      13-Oct-2015 15:33    -
support/            15-Dec-2017 15:50    -
support-providers/  15-Dec-2017 15:49    -
surgeon/            16-Feb-2017 13:04    -

Hey @robertoestivill, apologies for this. It looks like our artifact was pruned from our repo at some point - not sure how that happened. I've re-uploaded it and put in a PR to add our deployment code in case we need to do another one sometime.

Going to close the issue as the PR has been merged.


Move rust sys calls to new repo

@Ughuuu There are some conflicts.

I don't mind changing my workflow - just wanted something that had working Github Actions before completing the move.

Can I close the pull request if we're not thinking of merging it in the near future? It's ok to merge too!

Sure, let's wait then until the api stabilizes a bit and then we can move everything to the new repo.


Ground slope angle for tracking and fixed-tilt PV systems

See #457, #460 for corresponding backtracking algorithm improvements. Need to expose ground slope input, which requires consideration of angle of incidence and self-shading calculations for fixed-tilt and tracking systems.

Not sure this is high priority, removing from release milestone for now


wip: proposal: Falco API

What type of PR is this?
/kind design
/kind documentation
Any specific area of the project related to this PR?
/area proposals
What this PR does / why we need it:
Writes down a proposal as the outcome of various discussions between me, @fntlnz, @kris-nova, and the whole community about giving Falco an API.
Which issue(s) this PR fixes:
will link to issues later
Special notes for your reviewer:
WIP
In the coming days me and @fntlnz are going to complete it.
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: leodido
If they are not already assigned, you can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kris-nova
If they are not already assigned, you can assign the PR to them by writing /assign @kris-nova in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: b15034adeafa0366c7f9d5dc15adb32564db6ceb

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kris-nova
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [kris-nova]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

My comment applies to any configuration API on k8s. Everything going towards gitops right now, because it's easier to use, it's auditable (e.g. SOC2, PCI), there's governance (GH protected branches), history and so on.
The falco flow with API will eventually be:
User -> git repo -> terraform CI job -> terraform falco provider -> falco API -> falco configuration engine -> falco.
Where API and terraform provider is a huge chunk of work because it's network interaction and it has to be properly secured, throttled and instrumented.
I think the much easier k8s flow would be:
User -> git repo -> gitops (e.g. flux-cd) -> CRD object on a cluster -> falco configuration engine (e.g. falco-operator) -> falco.
This already fits into all our existing pipelines, it's actually already built and so on.
Speaking of 3rd party dynamic rules providers. Any security product which will support falco will run it's agent in k8s anyways (already do), and they will have the communication with their agent anyways, so it will be much easier for them to just inject CRDs, and it will be much easier to me just to set RBAC for CRDs instead of thinking of another API.

I think this day configuration management of anything in k8s is pretty much solved, I'd be much more interested to see record-n-replay, a development of falco-rules catalog (e.g. the hub), adoption within security vendors, smarter rules and so on.

Hey @max-lobur
So I think you bring up some valid topics here, and to be clear the pipeline you suggested would completely work with this proposal.
This work defines very clear, rigid, and secure-by-default interfaces for working with Falco. Regardless of higher level implementation (such as Kubernetes, or gitops) users would now have a clean way of plumbing data into and out of Falco.
Once we have a contract for interfacing with Falco via C/C++ building things out like CRDs are a natural next step that we plan on taking. Or in a perfect world, that the community could help us with.

I see, so it's mostly for C/C++ interface rather than for configuration management over network

Yes exactly @max-lobur
Right now we have logic in C/C++ that deals with pulling data from a source directly.
This proposal attempts to standardize the input/output mechanisms for the C/C++ code so that we can build on top of it.
One of the big features here is that we are run mutual TLS by default :sunglasses: and are building tools around making that process as user friendly as possible
So the pipeline you proposed is a fantastic examples of how this new API would be useful

Clarification about where/how we plan to track and version the .proto files.
cc @kris-nova
Since it is very likely that also the engine (userspace/engine) and not only userspace/falco will use some of the proto definitions (eg., schema.proto) my plan is to mainly experiment with two approaches:

create a root level directory in Falco repository responsible to contain the proto files used across the repository (API, engine, etc.)
create another repository in the falcosecurity organization

I have not made a decision on this since I would like to investigate it hands-on while writing the code. But it will be option 1 or option 2.
Do you have suggestions/ideas/preferences about it?

@leodido,
Sounds good to me 👌🏻


load namespace and context from compute properties

#1590  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


fix: 10527 Google Sheet crud generation header issue v2

Description
The CRUD operation cannot be performed when there are no rows in the google sheet even though headers are present.
A fix was made so that even if there are no data rows but headers are present, then the button to initiate crud operation is enabled and crud operation can be done. If no rows are found including headers, then button is not enabled.
Fixes #10527
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?
Manual Tests Done

Test Case
Actions
Result
Status

Created a new Sheet through application
Create CRUD interface
Button not enabled
Pass

Above steps + Added headers in row 1
Create CRUD interface
Button enabled
Pass

Above steps +  Moved headers to row 2
Create CRUD interface
Button NOT enabled
Pass

Above steps +  Changed 'table header Index' in app to 2
Create CRUD interface
Button enabled
Pass

Above steps +  Added rows to the sheet
Create CRUD interface
Button enabled
Pass

Manually created empty sheet and created datasource
Create CRUD interface
Button not enabled
Pass

Above step + Added another sheet Sheet2
Create CRUD interface
Button not enabled
Pass

Above steps + Added header in Sheet1
Create CRUD interface
Button enabled
Pass

Above steps + Added row in Sheet1
Create CRUD interface
Button enabled
Pass

Above steps + Changed table header Index' in app to 2
Create CRUD interface
Button enabled **
Pass

Above steps + Selected the Sheet2
Create CRUD interface
Button not enabled
Pass

Above steps + Added row in Sheet2
Create CRUD interface
Button enabled
Pass

Above steps + Inserted 3 row above headers in Sheet2
Create CRUD interface
Button Not enabled
Pass

Above steps + Changed 'table header Index' in app to 4
Create CRUD interface
Button enabled
Pass

** - App created with data as headers

Unit Tests Added
|----|
|com.external.config.GetStructureMethodTest.testTransformResponse_missingJSON_throwsException()|
|com.external.config.GetStructureMethodTest.testTransformResponse_missingValues_returnsEmpty()|
|com.external.config.GetStructureMethodTest.testTransformResponse_singleRowJSON_returnsEmpty()|
|com.external.config.GetStructureMethodTest.testTransformResponse_emptyJSON_returnsEmpty()|
|com.external.config.GetStructureMethodTest.testTransformResponse_emptyStartingRows_toListOfObjects()|
|com.external.config.GetStructureMethodTest.testTransformResponse_emptyRows_returnsIndices()|
|com.external.config.GetStructureMethodTest.testTransformResponse_VerifyEndResult()|
Checklist:

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

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: Fix10527_GS_Crud_Generation_Header_Isssue_V2

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
55.88 (0)
37.23 (-0.01)
35.22 (0)
56.19 (0)

:red_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.71 (-0.23)
40.83 (-0.84)
36.21 (0)
56.74 (-0.25)

/ok-to-test sha=46b7860

/ok-to-test sha=46b7860

/ok-to-test sha=4eb950a

/ok-to-test sha=4eb950a


osX build broken in 1.10.x branch

Expected Behavior

Should build on macOS.
Current Behavior

Doesn't seem to be building.
Steps to Reproduce

Here a ROS2 CI job:
https://ci.ros2.org/job/ci_osx/8432/console.
The problem seems to have been introduced in https://github.com/eProsima/Fast-RTPS/pull/1147.
System information

Fast-RTPS version: 1.10.x
OS: osX Mojave.
Network interfaces:

ROS2:  Foxy  (master)

Additional context

Additional resources

Wireshark capture
XML profiles file

I see another job passing here: http://ci.ros2.org/job/ci_osx/8433/, so I'm a bit confused.
I will check tomorrow and comment here.

I had that same problem yesterday with these two jobs:
https://ci.ros2.org/job/ci_osx/8427/console
https://ci.ros2.org/job/ci_osx/8431/console

@richiprosima It would be good if this can be fixed.
Our results are currently confusing, osX builds are failing on some of our CI machines but not in others.
Details:

mini3 successes to build https://ci.ros2.org/job/ci_osx/8452/consoleFull#console-section-18, CLANG v<IP_ADDRESS>00039
lore successes to build https://ci.ros2.org/job/ci_osx/8453/consoleFull#console-section-247, CLANG v<IP_ADDRESS>10046
mini2 fails to build https://ci.ros2.org/job/ci_osx/8454/console#console-section-34, CLANG v<IP_ADDRESS>10046

I originally thought there was a mismatch in CLANG version, but that doesn't seem to be the case in the last two machines.
I'm trying to investigate what's the difference in the environments.
From the failure output in the third build, I guess this could be fixed without understanding why the build is failing in some machines and note in others.

@ivanpauno Could you check with #1169?

@MiguelCompany It seems to be failing with the same error https://ci.ros2.org/job/ci_osx/8458/consoleFull#console-section-165, I checked and bug/pr1147_build_fail was correctly checked out in the job.

I've looked into the Xcode version on each one:

mini3 successes to build https://ci.ros2.org/job/ci_osx/8452/consoleFull#console-section-18, CLANG v<IP_ADDRESS>00039

Xcode 9.2 Build version 9C40b

lore successes to build https://ci.ros2.org/job/ci_osx/8453/consoleFull#console-section-247, CLANG v<IP_ADDRESS>10046

Xcode 10.2.1 Build version 10E1001

mini2 fails to build https://ci.ros2.org/job/ci_osx/8454/console#console-section-34, CLANG v<IP_ADDRESS>10046

Xcode 10.3. Build version 10G8
A first impression could be that 10.3 is the responsible for breaking the build but the release notes did not help too much to me.

@ivanpauno We have updated PR #1169 with an additional fix

I tried again with the last changes in #1169, and now it's working well:
https://ci.ros2.org/job/ci_osx/8478/
Let me know when that PR is merged, thanks!

Let me know when that PR is merged, thanks!

@ivanpauno done!

Thanks @MiguelCompany !!


Don't use a stale extent for a non-global base layer

Broken logic could leave a rectangle in _createTileImagerySkeletons with stale data.  Mostly this was harmless-ish, but if the stale data happened to lie outside the valid bounds of the imagery layer's tiling scheme, it could cause the exception seen in #2815.
Fixes #2815

Commented-out code is gone.

Tests and Sandcastle example are good, thanks.


🐞[Bug]: Animation not covering the entire div

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Animation doesn't cover the whole div element as expected, there could be several underlying issues related to CSS properties, animation settings, or the structure of the HTML/CSS.

Expected behavior
The expected behavior is that it should cover the whole div while we are hovering over it
It should be like this

Add ScreenShots
No response
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Assigning

Hey, can I make some contribution to this issue?


Remove educator searchbar precomputing from nightly task

Notes

@jhilde had the right idea about this from the beginning; this should run as its own nightly task
The educator searchbar precomputing sometimes takes more than 20 hours to run for reasons we don't fully understand yet
That throws an import error email which is high-urgency; put precomputing this JSON to optimize the searchbar endpoint is not high-urgency because it doesn't block educator login. So this should get its own, less urgent error report.

Just set this up as a scheduled task on Heroku; merging in now.


How to evaluate?

Is there a cli command for evaluating an utterance using one of the trained models?

@NHQ sorry, haven't yet. Wait for some time..I would give more performance result.


Updated editor config to use space characters. maintain 2 space chara…

…cters per indent

Sanity check: this fixes issue 8?

@phuchle

Sanity check: this fixes issue 8?

Yes it does

We clear to merge?

@jwu910 merged.


In need of stylex for deno fresh

this is a feature/plugin request.
Stylex is a css in js solution that builds css in compile time,
this issue is created so please people with knowledge pave the way to make it happen in fresh.
please provide the way this plugin needs to be implemented.

Please create an issue on the StyleX repo as well so we can help make this happen. What bundler is Fresh based on?

Please create an issue on the StyleX repo as well so we can help make this happen. What bundler is Fresh based on?

I started looking at this (without knowing about this issue) but didn't make a whole bunch of progress last week: https://discord.com/channels/684898665143206084/1189565451664117760/1189681460932788254. For simplicity, the summarized version is:
1) they use babel instead of esbuild. Not a huge issue, other than I don't know anything about babel
2) need to perform some sort of compilation , because the functions throw errors if actually invoked
3) fresh doesn't have the idea of compiling source files and then running them
4) would likely need more changes to the plugin api to modify fresh.gen.ts (or some other solution). This relates back to point 1, but when we try to import everything for the manifest, this ends up running variables declared with stylex.create, which throws the error

@nmn, the key issue I see is number 2, in that fresh doesn't currently have a spot to perform some sort of compilation. I started investigating what it would look like if fresh plugins could create "processed" files, and then would use these files instead of the original source files. This all seemed to work just fine, assuming the modified source can be produced (i.e. remove stylex.create and generate some .css).
The stumbling block I had was how to integrate with babel easily, although I must admit I didn't spend a large amount of time trying. Fresh has the concept of https://fresh.deno.dev/docs/concepts/ahead-of-time-builds to run esbuild on the islands that get sent to the browser. Ideally there would be an esbuild plugin provided by stylex that fresh could simply use.
@marvinhagemeister can speak about the entire picture more intelligently, since he has a more complete view of node/react/babel/etc. (I basically just know about deno/fresh 😅 )

The overall issue is the same as in https://github.com/denoland/fresh/issues/1622 . The crux of the problem is that we don't compile the server code at the moment. We only transpile the code that is used for islands via esbuild. Adding the necessary babel pass is trivial, but for as long as we don't transpile the server code it wouldn't help much.
I've been advocation for adding some sort of loader API to Deno for enabling those workflows over the past months, but it looks like that won't come anytime soon. At least not support for custom loaders. That means the only other option is to transpile everything ourselves with Fresh, but then you run into the problem that deno test won't work anymore. I'm not sure yet what's the best way to solve that is.

For context, here's how StyleX is supposed to work:

Transform all source JS files using the Babel plugin.
The babel plugin produces JSON styles from each of the JS files as metadata
Collect all the styles from all the files and generate a single CSS file for the whole app.

This approach doesn't seem to fit in with the way Deno works at the moment. Not only do we need to collect styles from both server and client code. We also need to avoid any kind of bundle splitting of the generated CSS. Generated a single small CSS file is a core performance reason to use StyleX.
The other problem seems to be the way Deno handles imports. StyleX needs to compile imported packages that may contain StyleX too.
It sounds like the only possible solution here is to have a "source" folder that gets compiled wholesale into a "src" folder. This compilation can happen while you author code.
I'm already looking into this, but even with node_modules I need a tool to figure out dependency trees while not bundling to make this possible.


Update Cosmos DB naming in diagram

Fixes #554

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/guide/architecture-styles/images/web-queue-worker-physical.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Deployment fails with 'AzCli' object has no attribute 'cli_ctx'

This is autogenerated. Please review and update as needed.
Describe the bug
Exception after step az ad app permission grant
Command Name
az tc deploy Extension Name: tc. Version: 0.7.0.
Errors:
'AzCli' object has no attribute 'cli_ctx'
Traceback (most recent call last):
Temp\pip-unpacked-wheel-2lthyver\knack\cli.py, ln 215, in invoke
cli\core\commands\__init__.py, ln 654, in execute
cli\core\commands\__init__.py, ln 717, in _run_jobs_serially
cli\core\commands\__init__.py, ln 710, in _run_job
Local\Temp\pip-unpacked-wheel-o9e7nicr\six.py, ln 703, in reraise
cli\core\commands\__init__.py, ln 688, in _run_job
...
cliextensions\tc\azext_tc\_deploy_utils.py, ln 174, in deploy_arm_template_at_resource_group
    mode='Incremental')
cli\command_modules\resource\custom.py, ln 846, in _prepare_deployment_properties_unmodified
AttributeError: 'AzCli' object has no attribute 'cli_ctx'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az tc deploy -n {} --pre -l {} -g {}

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.15.1

Extensions:
aks-preview 0.4.66
azure-devops 0.18.0
resource-graph 1.1.0
tc 0.7.0

Additional Context

closed because of solution redesign


rowsMax on TextField

Is your feature request related to a problem? Please describe.
I want to make it so that a text field expands as the content takes up to much space in the TextField, and not have a scroll-bar.
Describe the solution you'd like
Include rowsMax on TextField.
Describe alternatives you've considered
Switch to TextField from material-ui, which is boring to have to do just for rowsMax.
Demo how I want it to work
https://codesandbox.io/s/material-demo-forked-us7hp

@wigsnes We have release this feature now and it can be found in the latest version of eds-core-react (0.12.0)!

Thanks, this will work. I see some improvements that can be made if you have time, you can see codesandbox here.


[WIP] Add approximation tensor network contraction subpackage

Still need to get some more tests working, but most of the parts are done.
Package transferred from https://github.com/ITensor/ITensorNetworkAD.jl

Will just close this one since updates are merged gradually in other PRs.


MAINT: make the data loading apis more consistent.

Changes BcolzDailyBarWriter to not be an abc, data is passed as an
iterator of (sid, dataframe) pairs to the write method.
Changes the AssetsDBWriter to be a single class which accepts an engine
at construction time and has a write method for writing dataframes for
the various tables. We no longer support writing the various other data
types, callers should coerce their data into a dataframe themselves. See
zipline.assets.synthetic for some helpers to do this.
Adds a lot of test fixtures and updates many tests to use these. This
was done in the process of updating the tests that used one of the
writers above.
ref:  #1108. #1100

Coverage decreased (-0.09%) to 84.131% when pulling 9f2bd48a76290cef8d92d7e0890e410e41e4b38d on make-loader-apis-more-clear into 34f47da033c4f3beb55b464515007a98b9a22e69 on master.

Comments for the files that github won't show because of the diff size:
zipline.utils.compat

Nothing is using the newly-added mappingproxy.

zipline.utils.control_flow

Nothing is using invert_unique.

zipline.utils.functional

I don't think any of the additions here are being used.

zipline.dispatch
I'm a little confused about what this module is for.  I understand generally
that it's defining a namespace for multiple-dispatched functions, but I don't
follow why we're using the module's globals as the namespace.

mappingproxy was added for the quandl stuff
I can kill invert_unique.
I am using unzip (I think), if not I have usages in my other branch, sorry I did a poor job isolating these pieces
re dispatch: I can make it not use the globals as the namespace, but I think it is nice to be able to import from that single module if you intend on adding a dispatch to an already existing dispatcher with register.

Coverage decreased (-0.3%) to 84.022% when pulling c96262dfe7c4b7224fd05d8f904aca17693ead37 on make-loader-apis-more-clear into 85a2f6fe007a2a22fe29cc9586d8da247e8883f1 on master.

Coverage decreased (-0.3%) to 84.026% when pulling 38ce51f9798c6e3f023d56cad664f97353ae62c5 on make-loader-apis-more-clear into 85a2f6fe007a2a22fe29cc9586d8da247e8883f1 on master.

Coverage decreased (-0.2%) to 84.03% when pulling d9061240ab4f67f80c9b1512fa93b4c651097413 on make-loader-apis-more-clear into 85a2f6fe007a2a22fe29cc9586d8da247e8883f1 on master.

Coverage decreased (-0.2%) to 84.049% when pulling bc0b117dc94b8e93081818964e3b1bdbf9b33abb on make-loader-apis-more-clear into 8c64cc80ec61e5a46155cb37b235bdc1289661e1 on master.


Add cargoDenyCheckExtraArgs

Is your feature request related to a problem? Please describe.
I want to run cargo check --hide-inclusion-graph.
cargoDenyExtraArgs is passed before check in cargo check, so it doesn't work. cargoDenyChecks is about selecting checks, so adding --hide-inclusion-graph there works, but requires duplicating default checks.
Describe the solution you'd like
cargoDenyCheckExtraArgs that goes after check next to cargoDenyChecks would be ideal.

Hi @dpc thanks for the report!
Generally I've tried to keep these APIs from growing too many options, especially ones with subtle differences that require the caller to understand the implementation details (ordering of arguments) if they're mostly doing the same thing. Generally we've stuck with cargoExtraArgs so that various common argument inheritance can work, and cargoDenyExtraArgs is following the pattern of per-command extensions.
Given that we also have a third cargoDenyChecks for tweaking the actual check parameters, I'd say it would be overkill to have a fourth. Yes, specifying an additional parameter would require duplicating the default value, but IMO that's not such a bad thing: given that you are diverging from the defaults, it's probably worth being a bit more explicit in re-specifying exactly what checks should be included (the default value we currently have is a nice default, but definitely not the case that we should be authoritative on a default everyone sticks to)
Going to close this out since I don't think we need to go in this direction, but let me know if you disagree.