Use functions coded in system, not integrator

We can simplify the relative free energy calculation driver app if we have the alchemical factory "bake" the switching functions into the system so that we only need to drive lambda in the integrator.

The system now supports this.


Added parameter without_websockets to media submit methods

Fixes #1123
Feature Summary and Justification
This feature provides the option to not use websockets when submitting an image/video/videogif. This is useful because the WebSockets might not work in restricted network environments, and it allows PRAW users in this situation to still submit media without raising an exception every time.

Solid addition.


Added support for storing data in blob fields

Previously every parameter was casted to string when inserting or updating rows, but this didn't work with blob fields. I've just added the code to check if the parameter should be treated differently if blob both on iOS and on Android. Reading the blob parameters already worked.
The other changes are only white spaces added by Visual Studio Code...

Sorry for the delay, I need time to actually look through all the changes and figure out what actually changes.    I took your blob changes out of the files; thank you for the PR.      v2.6.0 has this fix and others.


Sample OPEN API Spec 3.0 and compatible Swagger UI

Hi,
We would like to migrate from Swagger 2.0 to OPEN API Spec 3.0 as per the blog
Read Me Blog
We tried to construct OAS json and display using online petstore example, but it is not parsing 3.0 spec JSON.
Can you provide us with the sample OPEN API Specification file along with the compatible Swagger UI to host OAS.
This will help us to migrate from version 2 to 3.
Please help with us.

@kunalsmile swagger-ui does not yet support OAS 3.0 It is something we'll be working on in swagger-ui/editor/js and other open source tooling.
The specification still needs to be finalized ( @webron ? what stage of the 3.0 are we in?) before the tooling catches up.
Feel free to bug the OSS projects... so that others can find out about the status of 3.0 in tooling!

@webron ? what stage of the 3.0 are we in?

Indeed, it is a little unclear if we are at 3.0.0-RC1 or that a kind of merge-window for 3.0.0-RC1 has begun.

I think we'll be at 3.0.0-RC1 when the tag is created.

@ponelat The OAI has released an Implementer's Draft so it's a perfect time to start looking at adding support for 3.0.

A sample Petstore 3.0 would be amazing. A comprehensive example is soooo much easier to understand and follow than trying to piece together the spec.

@scotmas it's a work in progress, but there is a v3 petstore example on the dm/examples branch.

FYI: Here's the new v3 petstore example link

Would you guys be able to add an example of serializing an object into say application/json into a query parameter to the v3 petstore example? You have a simpler example described here: https://swagger.io/docs/specification/describing-parameters/#schema-vs-content, but it would be nice to see one with a #ref rather than explicitly typed structures.

https : //swagger.io/docs/specification/describing-parameters/#schema-vs-content

The 3.0 petstore example (and others) were added years ago, so I'm closing this as resolved.


Does CVE-2018-9230 effective with kong?

As title.
That issue effective with all openresty, so there's same problem in Kong right?

It's worth noting that MITRE has acknowledged a dispute with CVE-2018-9230 and that the "issue" is not a problem with OpenResty, but rather an explicitly defensive posture within the API.
That said, any security concern would arise in cases of evading a negative security model- typical use cases for header, query, and post arg fetchers within Kong are employed in a positive authentication model (e.g. token examination).

Thanks @p0pr0ck5 - well summed up.


inference on tensorrt

i try to make a c++ version of inference, but after i trans the model to onnx and run it on tensorrt 2080ti, the inference time of each layer are as follow:
{Cast}                                   0.301ms
Conv/Conv2D__5                           0.138ms
Conv/Conv2D                              0.707ms
ReduceMean__9                            132.021ms
Sub__11                                  0.218ms
(Unnamed Layer* 10) [ElementWise] + Redu 123.283ms
ReduceProd__30:0[Constant]               0.001ms
Cast__17                                 0.004ms
Div__18                                  0.004ms
PWN((Unnamed Layer* 24) [ElementWise], P 0.235ms
Conv/BatchNorm/Const:0 + (Unnamed Layer* 0.221ms
Conv_1/Conv2D                            0.936ms
ReduceMean__23                           121.545ms
Sub__25                                  0.217ms
(Unnamed Layer* 37) [ElementWise] + Redu 120.613ms
Cast__31                                 0.004ms
Div__32                                  0.004ms
PWN((Unnamed Layer* 51) [ElementWise], P 0.221ms
Conv/BatchNorm/Const:0_1 + (Unnamed Laye 0.224ms
MaxPool2D/MaxPool                        0.140ms
Conv_2/Conv2D                            0.045ms
ReduceMean__39                           29.410ms
Sub__41                                  0.028ms
(Unnamed Layer* 65) [ElementWise] + Redu 29.799ms
ReduceProd__74:0[Constant]               0.001ms
Cast__47                                 0.004ms
Div__48                                  0.004ms
PWN((Unnamed Layer* 79) [ElementWise], P 0.031ms
Conv_2/BatchNorm/Const:0 + (Unnamed Laye 0.032ms
Conv_3/Conv2D                            0.163ms
ReduceMean__53                           29.614ms
Sub__55                                  0.055ms
(Unnamed Layer* 92) [ElementWise] + Redu 30.101ms
Cast__61                                 0.004ms
Div__62                                  0.004ms
PWN((Unnamed Layer* 106) [ElementWise],  0.057ms
Conv/BatchNorm/Const:0_4 + (Unnamed Laye 0.059ms
add                                      0.083ms
Conv_4/Conv2D                            0.467ms
ReduceMean__67                           29.748ms
Sub__69                                  0.112ms
(Unnamed Layer* 120) [ElementWise] + Red 29.792ms
Cast__75                                 0.003ms
Div__76                                  0.004ms
PWN((Unnamed Layer* 134) [ElementWise],  0.359ms
Conv_4/BatchNorm/Const:0 + (Unnamed Laye 0.114ms
MaxPool2D_1/MaxPool                      0.072ms
Conv_5/Conv2D                            0.031ms
ReduceMean__83                           7.426ms
Sub__85                                  0.013ms
(Unnamed Layer* 148) [ElementWise] + Red 7.421ms
ReduceProd__146:0[Constant]              0.002ms
Cast__91                                 0.004ms
Div__92                                  0.004ms
PWN((Unnamed Layer* 162) [ElementWise],  0.018ms
Conv/BatchNorm/Const:0_7 + (Unnamed Laye 0.013ms
Conv_6/Conv2D                            0.147ms
ReduceMean__97                           7.433ms
Sub__99                                  0.028ms
(Unnamed Layer* 175) [ElementWise] + Red 7.622ms
Cast__105                                0.004ms
Div__106                                 0.004ms
PWN((Unnamed Layer* 189) [ElementWise],  0.030ms
Conv_4/BatchNorm/Const:0_9 + (Unnamed La 0.032ms
add_1                                    0.043ms
Conv_7/Conv2D                            0.031ms
ReduceMean__111                          7.541ms
Sub__113                                 0.014ms
(Unnamed Layer* 203) [ElementWise] + Red 7.431ms
Cast__119                                0.004ms
Div__120                                 0.004ms
PWN((Unnamed Layer* 217) [ElementWise],  0.018ms
Conv/BatchNorm/Const:0_11 + (Unnamed Lay 0.012ms
Conv_8/Conv2D                            0.150ms
ReduceMean__125                          7.323ms
Sub__127                                 0.027ms
(Unnamed Layer* 230) [ElementWise] + Red 7.427ms
Cast__133                                0.003ms
Div__134                                 0.004ms
PWN((Unnamed Layer* 244) [ElementWise],  0.030ms
Conv_4/BatchNorm/Const:0_13 + (Unnamed L 0.031ms
add_2                                    0.044ms
Conv_9/Conv2D                            0.466ms
ReduceMean__139                          7.607ms
Sub__141                                 0.055ms
(Unnamed Layer* 258) [ElementWise] + Red 7.927ms
Cast__147                                0.003ms
Div__148                                 0.004ms
PWN((Unnamed Layer* 272) [ElementWise],  0.058ms
Conv_9/BatchNorm/Const:0 + (Unnamed Laye 0.059ms
MaxPool2D_2/MaxPool                      0.040ms
Conv_10/Conv2D                           0.031ms
ReduceMean__155                          1.785ms
Sub__157                                 0.009ms
(Unnamed Layer* 286) [ElementWise] + Red 1.743ms
ReduceProd__559:0[Constant]              0.001ms
Cast__163                                0.004ms
Div__164                                 0.004ms
PWN((Unnamed Layer* 300) [ElementWise],  0.010ms
Conv_4/BatchNorm/Const:0_16 + (Unnamed L 0.007ms
Conv_11/Conv2D                           0.124ms
ReduceMean__169                          1.807ms
Sub__171                                 0.013ms
(Unnamed Layer* 313) [ElementWise] + Red 1.863ms
Cast__177                                0.003ms
Div__178                                 0.004ms
PWN((Unnamed Layer* 327) [ElementWise],  0.019ms
Conv_9/BatchNorm/Const:0_18 + (Unnamed L 0.014ms
add_3                                    0.023ms
Conv_12/Conv2D                           0.032ms
ReduceMean__183                          1.743ms
Sub__185                                 0.007ms
(Unnamed Layer* 341) [ElementWise] + Red 1.743ms
Cast__191                                0.003ms
Div__192                                 0.004ms
PWN((Unnamed Layer* 355) [ElementWise],  0.010ms
Conv_4/BatchNorm/Const:0_20 + (Unnamed L 0.006ms
Conv_13/Conv2D                           0.124ms
ReduceMean__197                          1.848ms
Sub__199                                 0.013ms
(Unnamed Layer* 368) [ElementWise] + Red 1.891ms
Cast__205                                0.003ms
Div__206                                 0.004ms
PWN((Unnamed Layer* 382) [ElementWise],  0.020ms
Conv_9/BatchNorm/Const:0_22 + (Unnamed L 0.013ms
add_4                                    0.023ms
Conv_14/Conv2D                           0.032ms
ReduceMean__211                          1.830ms
Sub__213                                 0.008ms
(Unnamed Layer* 396) [ElementWise] + Red 1.743ms
Cast__219                                0.004ms
Div__220                                 0.003ms
PWN((Unnamed Layer* 410) [ElementWise],  0.011ms
Conv_4/BatchNorm/Const:0_24 + (Unnamed L 0.007ms
Conv_15/Conv2D                           0.124ms
ReduceMean__225                          1.930ms
Sub__227                                 0.013ms
(Unnamed Layer* 423) [ElementWise] + Red 1.937ms
Cast__233                                0.004ms
Div__234                                 0.003ms
PWN((Unnamed Layer* 437) [ElementWise],  0.020ms
Conv_9/BatchNorm/Const:0_26 + (Unnamed L 0.013ms
add_5                                    0.023ms
Conv_16/Conv2D                           0.032ms
ReduceMean__239                          1.745ms
Sub__241                                 0.008ms
(Unnamed Layer* 451) [ElementWise] + Red 1.743ms
Cast__247                                0.004ms
Div__248                                 0.004ms
PWN((Unnamed Layer* 465) [ElementWise],  0.011ms
Conv_4/BatchNorm/Const:0_28 + (Unnamed L 0.007ms
Conv_17/Conv2D                           0.124ms
ReduceMean__253                          1.807ms
Sub__255                                 0.013ms
(Unnamed Layer* 478) [ElementWise] + Red 1.811ms
Cast__261                                0.003ms
Div__262                                 0.004ms
PWN((Unnamed Layer* 492) [ElementWise],  0.019ms
Conv_9/BatchNorm/Const:0_30 + (Unnamed L 0.013ms
add_6                                    0.024ms
Conv_18/Conv2D                           0.442ms
ReduceMean__267                          1.945ms
Sub__269                                 0.027ms
(Unnamed Layer* 506) [ElementWise] + Red 1.910ms
Cast__275                                0.003ms
Div__276                                 0.004ms
PWN((Unnamed Layer* 520) [ElementWise],  0.034ms
Conv_18/BatchNorm/Const:0 + (Unnamed Lay 0.031ms
MaxPool2D_3/MaxPool                      0.019ms
Conv_19/Conv2D                           0.037ms
ReduceMean__283                          0.472ms
Sub__285                                 0.006ms
(Unnamed Layer* 534) [ElementWise] + Red 0.515ms
ReduceProd__500:0[Constant]              0.001ms
Cast__291                                0.004ms
Div__292                                 0.004ms
PWN((Unnamed Layer* 548) [ElementWise],  0.007ms
Conv_9/BatchNorm/Const:0_33 + (Unnamed L 0.006ms
Conv_20/Conv2D                           0.116ms
ReduceMean__297                          0.509ms
Sub__299                                 0.008ms
(Unnamed Layer* 561) [ElementWise] + Red 0.472ms
Cast__305                                0.003ms
Div__306                                 0.003ms
PWN((Unnamed Layer* 575) [ElementWise],  0.011ms
Conv_18/BatchNorm/Const:0_35 + (Unnamed  0.007ms
add_7                                    0.010ms
Conv_21/Conv2D                           0.037ms
ReduceMean__311                          0.472ms
Sub__313                                 0.005ms
(Unnamed Layer* 589) [ElementWise] + Red 0.526ms
Cast__319                                0.004ms
Div__320                                 0.004ms
PWN((Unnamed Layer* 603) [ElementWise],  0.007ms
Conv_9/BatchNorm/Const:0_37 + (Unnamed L 0.005ms
Conv_22/Conv2D                           0.116ms
ReduceMean__325                          0.509ms
Sub__327                                 0.007ms
(Unnamed Layer* 616) [ElementWise] + Red 0.471ms
Cast__333                                0.003ms
Div__334                                 0.004ms
PWN((Unnamed Layer* 630) [ElementWise],  0.011ms
Conv_18/BatchNorm/Const:0_39 + (Unnamed  0.006ms
add_8                                    0.010ms
Conv_23/Conv2D                           0.037ms
ReduceMean__339                          0.471ms
Sub__341                                 0.006ms
(Unnamed Layer* 644) [ElementWise] + Red 0.473ms
Cast__347                                0.003ms
Div__348                                 0.004ms
PWN((Unnamed Layer* 658) [ElementWise],  0.007ms
Conv_9/BatchNorm/Const:0_41 + (Unnamed L 0.005ms
Conv_24/Conv2D                           0.116ms
ReduceMean__353                          0.510ms
Sub__355                                 0.008ms
(Unnamed Layer* 671) [ElementWise] + Red 0.472ms
Cast__361                                0.003ms
Div__362                                 0.004ms
PWN((Unnamed Layer* 685) [ElementWise],  0.010ms
Conv_18/BatchNorm/Const:0_43 + (Unnamed  0.006ms
add_9                                    0.010ms
Conv_25/Conv2D                           0.037ms
ReduceMean__367                          0.472ms
Sub__369                                 0.005ms
(Unnamed Layer* 699) [ElementWise] + Red 0.538ms
Cast__375                                0.003ms
Div__376                                 0.003ms
PWN((Unnamed Layer* 713) [ElementWise],  0.008ms
Conv_9/BatchNorm/Const:0_45 + (Unnamed L 0.005ms
Conv_26/Conv2D                           0.117ms
ReduceMean__381                          0.509ms
Sub__383                                 0.007ms
(Unnamed Layer* 726) [ElementWise] + Red 0.472ms
Cast__389                                0.003ms
Div__390                                 0.004ms
PWN((Unnamed Layer* 740) [ElementWise],  0.010ms
Conv_18/BatchNorm/Const:0_47 + (Unnamed  0.006ms
add_10                                   0.010ms
Conv_27/Conv2D                           0.037ms
ReduceMean__395                          0.472ms
Sub__397                                 0.006ms
(Unnamed Layer* 754) [ElementWise] + Red 0.472ms
Cast__403                                0.003ms
Div__404                                 0.004ms
PWN((Unnamed Layer* 768) [ElementWise],  0.007ms
Conv_9/BatchNorm/Const:0_49 + (Unnamed L 0.005ms
Conv_28/Conv2D                           0.116ms
ReduceMean__409                          0.510ms
Sub__411                                 0.007ms
(Unnamed Layer* 781) [ElementWise] + Red 0.472ms
Cast__417                                0.003ms
Div__418                                 0.004ms
PWN((Unnamed Layer* 795) [ElementWise],  0.010ms
Conv_18/BatchNorm/Const:0_51 + (Unnamed  0.006ms
add_11                                   0.010ms
Conv_29/Conv2D                           0.038ms
ReduceMean__423                          0.604ms
Sub__425                                 0.006ms
(Unnamed Layer* 809) [ElementWise] + Red 0.472ms
Cast__431                                0.003ms
Div__432                                 0.003ms
PWN((Unnamed Layer* 823) [ElementWise],  0.007ms
Conv_9/BatchNorm/Const:0_53 + (Unnamed L 0.005ms
Conv_30/Conv2D                           0.116ms
ReduceMean__437                          0.509ms
Sub__439                                 0.008ms
(Unnamed Layer* 836) [ElementWise] + Red 0.472ms
Cast__445                                0.003ms
Div__446                                 0.004ms
PWN((Unnamed Layer* 850) [ElementWise],  0.011ms
Conv_18/BatchNorm/Const:0_55 + (Unnamed  0.006ms
add_12                                   0.010ms
Conv_31/Conv2D                           0.052ms
ReduceMean__451                          0.472ms
Sub__453                                 0.007ms
(Unnamed Layer* 864) [ElementWise] + Red 0.472ms
Cast__459                                0.003ms
Div__460                                 0.004ms
PWN((Unnamed Layer* 878) [ElementWise],  0.010ms
Conv_18/BatchNorm/Const:0_57 + (Unnamed  0.006ms
Conv_32/Conv2D                           0.433ms
ReduceMean__465                          0.525ms
Sub__467                                 0.013ms
(Unnamed Layer* 891) [ElementWise] + Red 0.530ms
Cast__473                                0.004ms
Div__474                                 0.004ms
PWN((Unnamed Layer* 905) [ElementWise],  0.021ms
Conv_32/BatchNorm/Const:0 + (Unnamed Lay 0.152ms
Conv_33/Conv2D                           0.095ms
ReduceMean__479                          0.472ms
Sub__481                                 0.007ms
(Unnamed Layer* 918) [ElementWise] + Red 0.473ms
Cast__487                                0.003ms
Div__488                                 0.004ms
PWN((Unnamed Layer* 932) [ElementWise],  0.010ms
Conv_18/BatchNorm/Const:0_60 + (Unnamed  0.006ms
Conv_34/Conv2D                           0.037ms
ReduceMean__493                          0.472ms
Sub__495                                 0.005ms
(Unnamed Layer* 945) [ElementWise] + Red 0.473ms
Cast__501                                0.003ms
Div__502                                 0.004ms
PWN((Unnamed Layer* 959) [ElementWise],  0.007ms
Conv_9/BatchNorm/Const:0_62 + (Unnamed L 0.005ms
Resize__505                              0.024ms
Resize__505:0 copy                       0.010ms
Conv_35/Conv2D                           0.083ms
ReduceMean__510                          1.743ms
Sub__512                                 0.013ms
(Unnamed Layer* 974) [ElementWise] + Red 1.979ms
Cast__518                                0.003ms
Div__519                                 0.004ms
PWN((Unnamed Layer* 988) [ElementWise],  0.019ms
Conv_9/BatchNorm/Const:0_64 + (Unnamed L 0.014ms
Conv_36/Conv2D                           0.442ms
ReduceMean__524                          1.898ms
Sub__526                                 0.027ms
(Unnamed Layer* 1001) [ElementWise] + Re 1.857ms
Cast__532                                0.003ms
Div__533                                 0.004ms
PWN((Unnamed Layer* 1015) [ElementWise], 0.034ms
Conv_18/BatchNorm/Const:0_66 + (Unnamed  0.031ms
Conv_37/Conv2D                           0.082ms
ReduceMean__538                          1.913ms
Sub__540                                 0.013ms
(Unnamed Layer* 1028) [ElementWise] + Re 1.810ms
Cast__546                                0.003ms
Div__547                                 0.004ms
PWN((Unnamed Layer* 1042) [ElementWise], 0.020ms
Conv_9/BatchNorm/Const:0_68 + (Unnamed L 0.013ms
Conv_38/Conv2D                           0.224ms
ReduceMean__552                          1.805ms
Sub__554                                 0.014ms
(Unnamed Layer* 1055) [ElementWise] + Re 1.807ms
Cast__560                                0.004ms
Div__561                                 0.006ms
PWN((Unnamed Layer* 1069) [ElementWise], 0.019ms
Conv_9/BatchNorm/Const:0_70 + (Unnamed L 0.013ms
Conv_39/BiasAdd                          0.052ms
Conv_39/BiasAdd__563                     0.007ms
Time over all layers: 826.180
the most time-consuming layer is always reduce_mean, how to get 20 fps when inference, thx

i have fix it by set is_traing False, now inference time is around 10ms

i have fix it by set is_traing False, now inference time is around 10ms

Hello, I am new to Tensorflow and tensorrt. I need to accelerate this model as you did. Can you please share the path how you transformed the model into tensorrt? Thanks in advance.

@rosexplorer first export the pb file from, than trans the pb to onnx model, at last,  import onnx model using tensorrt's onnx parser.

aren't there to few files in the pre trained model to export it to the pb file? I watched several tutorials and they had a checkpoint file and a pbtxt file in it and the exported it to the pb file.

@rosexplorer share you the onnx file 链接: https://pan.baidu.com/s/19yt_mmEhPjIntvfDSVu1NQ  密码: pmet

I don't want to click on a link, which I don't know where it is from. Could you please describe how you got the pb file?

@rosexplorer    only need to add some code like this, in function detect

@zttbx Thanks for the help. I tried it and a pb file was created and I wanted to convert it into a onnx model but when I execute this command:
python3 -m tf2onnx.convert --saved-model livox_detection-master/model/saved_model.pb --output model.onnx
I only get this traceback:
Illegal instruction (core dumped)
Do you know what could be the problem?

@zttbx Thanks for the help. I tried it and a pb file was created and I wanted to convert it into a onnx model but when I execute this command:
python3 -m tf2onnx.convert --saved-model livox_detection-master/model/saved_model.pb --output model.onnx
I only get this traceback:
Illegal instruction (core dumped)
Do you know what could be the problem?

I simply "solved" this problem with reinstalling tensorflow.
When I want to transform the .pb file to onnx, I get a traceback like this:
RuntimeError: MetaGraphDef associated with tags 'serve' could not be found in SavedModel. To inspect available tag-sets in the SavedModel, please use the SavedModel CLI: saved_model_cliavailable_tags: [set()]
I don't know what is wrong with this file.

@rosexplorer share you the onnx file 链接: https://pan.baidu.com/s/19yt_mmEhPjIntvfDSVu1NQ 密码: pmet

Could u pls share the onnx once more, since it’s expired. Thx a lot!

@rosexplorer Hi!
I meet the same problem,
RuntimeError: MetaGraphDef associated with tags 'serve' could not be found in SavedModel. To inspect available tag-sets in the SavedModel, please use the SavedModel CLI: saved_model_cli available_tags: [set()]
Any solution to this problem ?
@zttbx  Thanks for your work

@zttbx Hi
I want to do the same thing ! Thanks for your suggestion.
I exported the "pb" file from the code you write. Then I transferred the pb file into onnx by using "python3 -m tf2onnx". Then I transfer the onnx model into trt file by using "TensorRT-X.X.X/bin/trtexec " and got trt model.
I used this trt model in TensorRT. However, the inference is getting slower? I am using RTX3070
Any solutions ? How did you make this work ?
Thanks

I have fixed this issue. Thanks

zttbx

Hi, zttbx, thank you for your awesome job, but the baiduyun's link about the onnx model have lost, can you share it again? thank you so much!


build(snap): source metadata from central repo

The metadata kept in snapcraft.yaml is obsolete because it is being overridden on the store. This change will allow sourcing the central copy of metadata.
See https://github.com/canonical/edgex-snap-metadata/issues/2
Signed-off-by: Mengyi Wang<EMAIL_ADDRESS>

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

# clean and build:
$ snapcraft clean && snapcraft

# unpack the built snap:
$ unsquashfs name.snap

# verify that icon exists:
$ ls squashfs-root/meta/gui/icon.png
squashfs-root/meta/gui/icon.png

# verify that version, summary and description are included:
$ cat squashfs-root/meta/snap.yaml
...
version: 2.0.1-dev.71
summary: Open-source framework for IoT edge computing
description: |-
  EdgeX Foundry is a vendor-neutral, highly flexible and scalable open-source framework hosted by The Linux Foundation. It enables developers to build apps that run at the edge, acting as a middleware between the things and the cloud.

  It provides the components to develop microservices responsible for data acquisition, data analytics and cloud connectors, exposing a rich set of APIs to allow full control of the system and configuration. The reference architecture allows scaling out to thousands of devices and sensors.

  This snap is a part of EdgeX Foundry and contains the following reference services:

  **Core Services**
  * Core Data
  * Core Command
  * Core Metadata
  * Registry and Config (Consul)
  * Message Bus (Redis)

  **Supporting Services**
  * Rules Engine (eKuiper)
  * Scheduling
  * Alerts & Notifications

  **Application Services**
  * Configurable Application Service

  **Security Services**
  * API Gateway a.k.a. Reverse Proxy (Kong)
  * Secret Store (Vault)

  **Management Services**
  * Management Service Agent (deprecated)

  **Device Services**
  * Virtual

  Note that not all the above services are enabled and started by default.

  =============

  **Further Reading**
  * Getting started with snaps (v2.1): https://docs.edgexfoundry.org/2.1/getting-started/Ch-GettingStartedSnapUsers
  * Snap usage instructions: https://github.com/edgexfoundry/edgex-go/blob/main/snap/README.md
  * EdgeX documentation: https://docs.edgexfoundry.org
  * Source code: https://github.com/edgexfoundry/edgex-go

  ====================

  **Development Tool Snaps**
  * EdgeX UI: https://snapcraft.io/edgex-ui
  * EdgeX CLI: https://snapcraft.io/edgex-cli

  **Other Supported EdgeX Snaps**
  * App Service Configurable: https://snapcraft.io/edgex-app-service-configurable
  * Device Camera: https://snapcraft.io/edgex-device-camera
  * Device Modbus: https://snapcraft.io/edgex-device-modbus
  * Device MQTT: https://snapcraft.io/edgex-device-mqtt
  * Device REST: https://snapcraft.io/edgex-device-rest
  * Device SNMP: https://snapcraft.io/edgex-device-snmp
  * Device Grove: https://snapcraft.io/edgex-device-grove

  **Additional References**
  * Redis: https://github.com/redis/redis
  * Consul: https://github.com/hashicorp/consul
  * eKuiper: https://github.com/lf-edge/ekuiper
  * Kong: https://github.com/Kong/kong
  * Vault: https://github.com/hashicorp/vault
...

New Dependency Instructions (If applicable)

Codecov Report

Merging #3959 (bfd46bb) into main (ecc8587) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3959   +/-   ##
=======================================
  Coverage   46.80%   46.80%
=======================================
  Files         112      112
  Lines        9727     9727
=======================================
  Hits         4553     4553
  Misses       4787     4787
  Partials      387      387

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 ecc8587...bfd46bb. Read the comment docs.


zebra-alt (odd rows)

Sorry, but even rows looks really wierd sometimes.

Behold... <table class="table table-zebra-alt">

I don't think it's weird.
Coloring odd instead of even doesn't fix any issue or provide any advantage as far as I know.
However you can always customize and extend classnames for your own project.
And, please create an issue or discussion before opening a PR to avoid unnecessary effort.
((Contribution guideline)[https://github.com/saadeghi/daisyui/blob/master/.github/CONTRIBUTING.md#pull-requests])

I'll admit it doesn't look wierd now that I look at it (a day later).  Though the is something about the tables that is a little sub-par compared to your other components which are all exquisitely designed.  I've never felt it necessary to make a visual change before.
I'll play around with it, perhaps darkening the headers and lightening the stripes.
How does one achieve such specific customizations while staying within the daisyui framework?  I note the shading (for example) does not lend itself to easy adjustment via --var, being set to @apply bg-base-200;

How does one achieve such specific customizations while staying within the daisyui framework? I note the shading (for example) does not lend itself to easy adjustment via --var, being set to @apply bg-base-200;

What customization are you looking for exactly? Changing the background of a row?

How does one achieve such specific customizations while staying within the daisyui framework? I note the shading (for example) does not lend itself to easy adjustment via --var, being set to @apply bg-base-200;

What customization are you looking for exactly? Changing the background of a row?

Lets start with that... if it were only tailwindcss, I could do
@layer utilities {
  .striped div:nth-child(even) {
    @apply bg-gray-100
  }
}

I mean, what customization are you looking for about daisyUI tables?
Because daisyUI is using something similar for zebra table
.table-zebra tbody tr:nth-child(2n)

@saadeghi Sure... so if I wanted to use the alternate rows, how could I (as you said originally):

However you can always customize and extend classnames for your own project.

An easier example would be if I needed buttons that weren't rounded, (which I actually do need).  Rather than write "btn rounded-0" everywhere, how could I apply that automatically?


As a user I want the menu displayed properly

As a user I want the menu displayed properly.
Category:
Bug.
Where?
clariah-mediasuite project
How to reproduce:
In the menu while resizing the screen the Learn dropdown menu does go outside the screen view and a gap between the header menu and the dropdown appears as shown in:

Screencast example:
https://drive.google.com/open?id=1VJHgku_qxjtzdOcIc9uFF0FKLYVUJS4Z

@lilimelgar @jblom :
Issue reported by @lilimelgar on 18-02-2019
It's been solved in clariah-mediasuite project branch:
issue/#293-bug-when-resizing-screen-in-dropdown-menu
Github branch at:
https://github.com/beeldengeluid/clariah-mediasuite/tree/issue/%23293-bug-when-resizing-screen-in-dropdown-menu
@lilimelgar :
Please test in clariah-mediasuite :
git pull
git checkout issue/#293-bug-when-resizing-screen-in-dropdown-menu
npm run prod
run with console open and make sure the cache is been cleared.

@avlisodraude I tested in:
-clariah-mediasuite/src
-branch: issue/#293-bug-when-resizing-screen-in-dropdown-menu
-npm run prod
-cleared cached
the issue still persists: see screencast

@lilimelgar:
I checked the issue and I'm pretty sure it's a CACHE issue.
Please make sure that after switching branch and running 'npm run prod' the CACHE in your browser is cleared (with the console tool open).
In the next screencast you can see the differences between Master and the corresponding branch.
Screencast:
https://drive.google.com/open?id=1t5j_RVT82nUGT8BZFWanYNc6b3QMfIBb

@avlisodraude: Tested in the branch above, ready for pull request

@lilimelgar @avlisodraude merged, but found two more styling things for the menu. Will report them now


[fork] create service users based on hab bindings and gossip'ed config

Now, the reconfigure hook of foulkon-worker picks up service_names from
services it was bound to using the --bind argument
hab start chef/foulkon --bind service:authn-service.default --peer authn-service

The service needs to expose its desired service name via an export declared in its plan.sh:
pkg_exports=(
  [service_name]="foulkon.service_name"
)

where the string refers to the values config key in default.toml, e.g.
[foulkon]
service_name = "x-automate-authn"

This will be done in a different way, closing this.


--if was apended twice

in cloudslang runner the --if flag was appended twice.

Good catch :)
It would be also good to add a test which asserts arguments with which the cloudslang-cli is started.

@orius123 I will go ahead add the test and merge into into master.

Added a test case and merged fix into master. Thanks.


mvc, phalcon framework 4.0, PHP 7.4

Phalcon 4 will likely break things.
Run into a "Wrong number of parameters" in Phalcon\Mvc\Application->handle(), while upgrading my mac some time ago.
https://docs.phalcon.io/4.0/en/upgrade
Keeping this here for tracking purposes.

Additional dependencies:
php73-pecl-psr
php73-mbstring

% git ls-files | grep OPNsense.Base
www/nginx/src/opnsense/mvc/app/models/OPNsense/Base/Constraints/NaxsiIdentifierConstraint.php
www/nginx/src/opnsense/mvc/app/models/OPNsense/Base/Constraints/NgxBusyBufferConstraint.php

@fichtner I also need to check the firewall api plugin, for nginx I propose to add a ticket for @fabianfrz to check / modify for compatibility with Phalcon 4.1.
# grep -r Phalcon /usr/plugins
/usr/plugins/net/firewall/src/opnsense/mvc/app/models/OPNsense/Firewall/Filter.php:use Phalcon\Validation\Message;

First build based on PHP 7.4 available. Need to check runtime and https://www.php.net/manual/en/migration74.incompatible.php for good measure.


update "Message" suffix in request filenames

some python code is based on filenames ...

Good one, can't believe I missed that. 👍


profiles() doesn't handle Nprof > 1 properly

Currently throwing an error in delta_pres(P1, P2) when loading float 4902480. Works using syn = sprof(4902480), which shows the output:
>>> syn.CYCLE
Out:
array([ 1,  1,  2,  3,  4,  5,  6,  7,  8,  9, 10, 11, 12, 13, 14, 15, 16,
       17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32])

Turns out this isn't the fault of Nprof > 1, as profiles(4902480) actually works fine, but profiles(6902905) does not. I originally created this issue when profiles([4902480, 6902905]) threw an error that I incorrectly diagnosed to be because of the Nprof > 1. Looking into why this is happening with the second float, as loading the synthetic file with sprof() works fine. Issue is still in delta_pres().
Error output:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-8-f9b9387e24f9> in <module>
----> 1 prof = profiles(6902905)

~\Documents\projects\BGC-QC\bgcArgo\core.py in __init__(self, floats, cycles, mission, mode, keep_fillvalue)
    314
    315         self.__argofiles__ = get_files(ARGO_PATH, floats, cycles=cycles, mission=mission, mode=mode)
--> 316         self.__floatdict__ = load_profiles(self.__argofiles__)
    317         self.__rawfloatdict__ = self.__floatdict__
    318

~\Documents\projects\BGC-QC\bgcArgo\core.py in load_profiles(files)
    952                 floatData[v_adj] = np.append(floatData[v_adj], vertically_align(cc.variables['PRES'][:].data.flatten(), nc.variables['PRES'][:].data.flatten(), nc.variables[v_adj][:].data.flatten()))
    953
--> 954         floatData['dPRES'] = delta_pres(cc.variables['PRES'][:].data, nc.variables['PRES'][:].data)
    955
    956         for v in floatData.keys():

~\Documents\projects\BGC-QC\bgcArgo\core.py in delta_pres(P1, P2)
   1219         for i, p in enumerate(P1):
   1220                 index    = np.abs(P2 - p) == np.min(np.abs(P2 - p))
-> 1221                 dpres[i] = np.nanmean(P2[index] - p)
   1222
   1223         return dpres

ValueError: operands could not be broadcast together with shapes (249,) (121,)

Fixed by adding .flatten() to array inputs of delta_pres(). However, should be noted that profiles() runs quite slowly now, especially compared to sprof() as it loads double the files than before (with addition of core files to get S/T data). Utility will probably for individual profile files.
Fixed in dcf399a, closing issue


Void Config Option Does Not Seem to Work

Hello,
I'm working on configuring RFTools for SkyFactory 3 and can't seem to figure out how to make the void world option work in newly created dimensions. I've made sure this config entry is changed:
# Set this to true if you want to make sure RFTools can only create void dimensions
B:voidOnly=true

Is there another option I can try to make this happen so only void type worlds appear?
MC Version: 1.10.2
RFTools Version: 1.10 - 5.50
RFtools Dimention: 1.10 4.40
Forge: 2095
Thank you!!
Darkosto

I will check it out. Perhaps I forgot to implement it in 1.10.2

Fixed in 4.41


support parsing Apple System Log files (.asl files)

Summary
Support parsing Apple System Log files (.asl files).
Here is a short explanation of reading ASL files. The best I can find for Rust implementations is this crate oslog which AFAICT only writes to .asl files.
This Python tool asl binds to the shared available library on a Mac.
This Python tool ccl-asl parses ASL files.  It failed to parse .asl files under ./logs/MacOS11/asl/.  It successfully parsed ASL file ./logs/MacOS12.6/asl/2023.10.26.G80.asl.

When implemented, consider adding a comparison to ccl-asl in the README.md


feat(docs): Add cookbook example of audio manager notifications.

If you hold off on this for now, I'll do another pass over it on the weekend.

What's the source on your cowbell audio clip? I know the repo needs more cowbell, but only if it's open source cowbell. :)

@schmidtk I created it using Audacity (i.e. its original work).
ObDisclosure: It doesn't really sound like a literal cow bell. Its more like this computer-generated four-tone sequence... However the Audacity menu option (Beat sound: in https://manual.audacityteam.org/man/rhythm_track.html) for this was "Cowbell", which seemed like a good name, especially since we can upgrade it to real cowbell without changing the docs...


Broker: Specified group generation id is not valid

My project connects to a Kafka broker and consumes messages. It has been running fine for a long time , but now has started to throw exceptions and is no longer correctly working.
I keep getting "Broker: Specified group generation id is not valid"
I know this is caused by trying to commit with AutoCommit() while not being part of the group anymore, but I have no idea how/what to configure in the Kafka client in order to have it re-instate the membership to the group.
Here is an extract of the error
object(RdKafka\Exception)#1347 (7) {   ["message":protected]=>   string(50) "Broker: Specified group generation id is not valid"   ["string":"Exception":private]=>   string(0) ""   ["code":protected]=>   int(22)   ["file":protected]=>   string(72) "/var/www/vendor/mateusjunges/laravel-kafka/src/Commit/KafkaCommitter.php"   ["line":protected]=>   int(20)   ["trace":"Exception":private]=>   array(31) {     [0]=>     array(6) {       ["file"]=>       string(72) "/var/www/vendor/mateusjunges/laravel-kafka/src/Commit/KafkaCommitter.php"       ["line"]=>       int(20)       ["function"]=>       string(6) "commit"       ["class"]=>       string(21) "RdKafka\KafkaConsumer"       ["type"]=>       string(2) "->"       ["args"]=>       array(1) {         [0]=>         object(RdKafka\Message)#911 (10) {           ["err"]=>           int(0)           ["topic_name"]=>           string(19) "DeliveryTrackingLog"           ["timestamp"]=>           int(1683470753552)           ["partition"]=>           int(2)

Hi @DevHeaven ,
may I know you use which version? and what is you config file and env?

@ebrahimradi Hi. I get this issue too.

version v1.11
KAFKA_OFFSET_RESET=earliest
KAFKA_MAX_POLL_INTERVAL_MS=300000
KAFKA_MAX_PARTITION_FETCH_BYTES=1048576
$consumer = Kafka::createConsumer()
      ->withAutoCommit(false)
      ->withConsumerGroupId($consumerGroupId)
      ->subscribe($this->getTopic()->value)
      ->withHandler(function (Message $message): void {
             // handle message
      })
      ->withOptions([
            'client.id' => config('app.hostname'),
            'max.poll.interval.ms' => config('kafka.max_poll_interval_ms'),
            'max.partition.fetch.bytes' => config('kafka.max_partition_fetch_bytes'),
      ]);

if (config('kafka.enable_sasl')) {
    $consumer
        ->withOptions([
            'ssl.ca.location' => config('kafka.ssl_ca_location'),
        ])
        ->withSasl(new Sasl(
            username: config('kafka.user'),
            password: config('kafka.password'),
            mechanisms: config('kafka.mechanisms'),
            securityProtocol: config('kafka.security_protocol')
        ));
}

$this->consumer = $consumer->build();

$this->consumer->consume();

my consumer group id  - Showcase_integration_normalized-price-and-rest-v3
i tried with autocommit true its ok. but offset was not commited

as I said, hyphen char is not allowed to be in consumer group id. try with simple one like "testid" with autocommit true. and reply back please

the problem was that there were not enough resources for the supervisor Pod in k8 cluster. as a result of which the consumer stopped with SIGKILL

Unfortunately I have not yet been able to resolve this :-(
I do want to mention that this deployment is running on Nomad (Hashicorp)
I keep getting this error "Broker: Specified group generation id is not valid" . The consumer then seems alienated . It still is registered on the broker as a consumer, but it doesn't process anymore messages, it just throws this error.
The group name does not contain any spaces, underscores or other strange characters.
It has a simple name "mlceddconsumer"
I have no idea where to look further, I'd love any tips that could help


BSA detects some PCIe devices but not list them as valid device for testing

The message below showed zero BDF found but it still be able to print out the class code info for BDF 0x0, 0x100, 0x200, and all PCI device tests got skipped.
 PCIE_INFO: Number of ECAM regions    :    1
 PCIE_INFO: Number of BDFs found      :    0
   BDF Table: No RCiEP or iEP found
.....

 BDF is 0
 Class code is 2000001
 BDF is 100
 Class code is FF0000
 BDF is 200
 Class code is 1080201
 Peripheral: Num of Network ctrl      :    1
 Peripheral: Num of Storage ctrl      :    1
...
 .....
      *** No Valid Devices Found,                 Skipping remaining PCIE tests ***

Hi @sunnywang-arm,
In the SUT, there were only legacy PCI devices present. Having PCIe devices are prerequisite for running ACS PCIe tests else ACS will skip the PCIe tests with the mentioned log message.
For the peripheral info table, ACS considers both legacy and PCIe devices.
We will add log prints to list the reason of BDF skip during creation of PCIe info table to help in debugging.
Thanks,
ACS team

Hi @sunnywang-arm,
Thanks for raising this.
We have added DEBUG log prints to capture the reason of skipping a PCIe device from Info Table.
This will ensure all BDF processed by ACS are matching with uefi pci command.


Fix class-name-casing cannot recognize PascalCase containing digits

When class-name-casing is enabled, class Foo2 {} will be reported as invalid.

Thanks, @dobogo!


hide magnifier when entire toolbar overlay is hidden

Description
I have many users enjoying this feature - but have a couple dozen or so stuck magnifier complaints as well. I took a look at the code and there are a couple of paths where the selectionOverlay is dismissed via a call to hide() that takes care of the toolbar menu but not the magnifier. When hide() is called directly, not in the regular disposal path, the selectionOverlay is removed before the call to remove the magnifier. In those cases, the magnifier will be left floating on the screen. This PR fixes that scenario.
Related Issues

Fix #2379

Type of Change

[ ] ✨ Feature: New functionality without breaking existing features.
[x ] 🛠 Bug fix: Resolves an issue without altering current behavior.
[ ] 🧹 Refactor: Code reorganization, no behavior change.
[ ] ❌ Breaking: Alters existing functionality and requires updates.
[ ] 🧪 Tests: New or modified tests
[ ] 📝 Documentation: Updates or additions to documentation.
[ ] 🗑 Chore: Routine tasks, or maintenance.
[ ] ✅ Build configuration change: Build/configuration changes.

Thanks, I will review soon.


Remove unused/unpurposeful classes.

Several classes are legacy and left over from many changes in the Razor code base. This changeset removes those classes.
Also moved several corresponding test cases

#778
/cc @pranavkm

:shipit:


update unused warning

Related issue(s)
This wraps up PR #263 which added warnings for unused variables.
Description
The PR allows for specification of a development mode where circuits can be compiled with unused variables. We currently error out on any usage of unused variables which makes it difficult when debugging larger circuits, especially as we do not currently have logging functionality.
Summary of changes

This PR fixes some merge conflicts as #263 is from several months ago. This is why you see such a large amount of line additions and deletions. Almost all of these are due to the merge conflicts. This PR will be much easier to review if it is simply merged with jf/unused-warning or we change the base branch to master.

I added a --dev flag that can be called as such nargo --dev build or nargo --dev compile p. The dev flag is passed to all cmds that must build the circuit: build, compile, prove, verify, contract, gates.

nargo build acts the same:

While running nargo --dev build on the same code returns:

nargo compile p will have the same output as nargo build, while nargo --dev compile p will have:

Dependency additions / changes
N/A
Test additions / changes
I moved the test from the parent PR to build_tests_data
Checklist

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[X] I have linked this PR to the issue(s) that it resolves.
[X] I have reviewed the changes on GitHub, line by line.
[X] I have ensured all changes are covered in the description.

Additional context
I could instead have the base branch be master, but I initially set it to merge into jake's branch as I checked out off of jf/unused-warning. This PR will be much easier to review if we simply merge with jf/unused-warning or we change the base branch to master.

...I can't really review this at 12.9k lines changed so I'll follow the advice and merge this into my branch haha. We can continue the review there


Rename to slack-emoji-issues

Once we add Jira support in #11, it's probably best to change the name of the project to be less specific to GitHub. In retrospect, having "emoji" in the name probably would've been a good idea to begin with.
As they say, there are three hard problems in computer science:

Caching
Naming things
Correctly attributing original sources
Off-by-one errors

I renamed the repo to https://github.com/mbland/slack-emoji-issues some time ago, but have yet to update the package name. Soon!


⚠ Bofrost.nl has degraded performance

In d5dbd87, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1667 ms

Resolved: Bofrost.nl performance has improved in 38c041b.


When require path separator mark for directory path. Join-Path does not work

https://github.com/PowerShell/PowerShell/issues/24193

Hi @ZSkycat Thank you for the suggestion.
I am not sure how to present this issue. This trap collection is not a
PowerShell bug tracker as such, PowerShell has it's own, we do not just
duplicate issues here.
There should be a story of doing something "normal" and getting something
"unexpected" which results in problems in practice. Your case is doing
something "unusual".
Using path like \, /, \path or /path as the second argument of
Join-Path is not normal, IMHO. The normal use case is a relative path.
These paths are not relative.

From my perspective, Join-Path is simply concatenates path and path2 and adds a directory separator character between any of the path components if one is not already present. It mainly solves the problem of slash and backslash and has nothing to do with relative paths.
There is no use using it like this:
> Join-Path $PWD.ProviderPath '.\'
C:\pwd\.\

For example:
Some applications require path separator mark for directory path. Like 7z.exe -spm. "PowerShell" as a wrapper for the application, needs to correct user input.
Join-Path $UserInputPath '\' used for this purpose.
The file system supports slash and backslash paths. The user may enter a different slash than the default. This will lead to unexpected results.
Join-Path 'C:/Test/Test/' '\'
> C:/Test/Test/\

This problem only occurs when join '/' or ''.
In addition, Join-Path fails if the path drive does not exist. related issues https://github.com/PowerShell/PowerShell/issues/20011#issuecomment-1646664012

I see. And it used to works (or still works) in PS Desktop and stopped working as expected in PS Core, right? That would be a "trap" case, sure.

Yes. It works in Windows PowerShell.

@ZSkycat Here is the draft
https://github.com/nightroman/PowerShellTraps/tree/2024-10-03-0245/Cmdlets/Join-Path/With-path-separator
So far I have provided just one case, see Test-1.ps1, it is from your last comment above.
What other cases would like to see in this script? Not too many, please, and not too contrived.

# 5.1 : Test\Test\
# 7.x : Test/Test/\
Join-Path 'Test/Test/' '/'

Done, thank you for the suggestion and help
https://github.com/nightroman/PowerShellTraps/tree/main/Cmdlets/Join-Path/With-path-separator


capture time taken by validator to call BN

possibly as a metric...
Basically when the validator calls to the BN, capture the time taken for the response. this would include getting duties, and performing duties.
Similarly if we don't capture signing time, would be worth capturing the time taken to perform signing.

https://discord.com/channels/697535391594446898/697539289042649190/1036636304731033702


bb10 dev

hey alex, wondering if we could chat about bb10 dev im a developer, but I dont have access to the bb10 dev tools. need a basic app with api calls

@mathewjpotter Hello.
I would start from this page (while it's still available lol): https://developer.blackberry.com/native/
It contains all the tools, samples, tutorials, specs, etc. needed for BB10 development.
But feel free to ask specific questions if you're stuck in something

                                                                                ok ill give it a shot, is there an issue with getting a dev license?                                                                                Sent from my BlackBerry 10 smartphone on the TELUS network.                                                                                From: AlexeyGurevskySent: Saturday, October 16, 2021 11:27 AMTo: AlexeyGurevsky/bbtubeReply To: AlexeyGurevsky/bbtubeCc: Mathew; MentionSubject: Re: [AlexeyGurevsky/bbtube] bb10 dev (#2)

@mathewjpotter Hello.
I would start from this page (while it's still available lol): https://developer.blackberry.com/native/
It contains all the tools, samples, tutorials, specs, etc. needed for BB10 development.
But feel free to ask specific questions if you're stuck in something
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
[
{
@.": "http://schema.org",
@.": "EmailMessage",
"potentialAction": {
@.": "ViewAction",
"target": "https://github.com/AlexeyGurevsky/bbtube/issues/2#issuecomment-944976503",
"url": "https://github.com/AlexeyGurevsky/bbtube/issues/2#issuecomment-944976503",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
@.": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

                                                                                I was reading that with the tokens, you can set the time on your phone after they expire to install the apps, any experience with that?                                                                                Sent from my BlackBerry 10 smartphone on the TELUS network.                                                                                From: AlexeyGurevskySent: Saturday, October 16, 2021 12:43 PMTo: AlexeyGurevsky/bbtubeReply To: AlexeyGurevsky/bbtubeCc: Mathew; MentionSubject: Re: [AlexeyGurevsky/bbtube] bb10 dev (#2)

ok ill give it a shot, is there an issue with getting a dev license?
Nope, it still works, I've just checked that.
The thing is that you don't need any license or stuff like that to start the development. Just download the IDE, NDK, and, perhaps, the emulator (if you don't have a BB 10 device) and you're ready.
The only part when you need Blackberry's participation is signing your .bar-files, i.e. the apps which you are going to use/distribute. Without that signature you wouldn't be able to upload the app into App World (obviously not relevant anymore) and you're not able to sideload the app on your BB10 device.
This process (meaning signing) requires a connection to BB infrastructure, for now it works but no one knows what's going to happen in January 2022 after BB10 EOL.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
[
{
@.": "http://schema.org",
@.": "EmailMessage",
"potentialAction": {
@.": "ViewAction",
"target": "https://github.com/AlexeyGurevsky/bbtube/issues/2#issuecomment-944994797",
"url": "https://github.com/AlexeyGurevsky/bbtube/issues/2#issuecomment-944994797",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
@.": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

                                                                                cool thanks for the info, im gonna put everything down in. MD file I am planning on doing, I have a php driven api on a server to connect to my self deployed version of rocket chat. ive already prototyped calls in an android app. but would like to do it in native. defn willing to pay for a little consult / skill when I dig in, thanks for your help thus far                                                                                Sent from my BlackBerry 10 smartphone on the TELUS network.                                                                                From: AlexeyGurevskySent: Sunday, October 17, 2021 10:44 AMTo: AlexeyGurevsky/bbtubeReply To: AlexeyGurevsky/bbtubeCc: Mathew; MentionSubject: Re: [AlexeyGurevsky/bbtube] bb10 dev (#2)

@mathewjpotter
Yes, debug tokens are valid for 1 month, one needs to renew them to continue development. But those tokens are needed only to deploy the apps on your dev phone and to (surprisingly) debug :)
In theory, if for some reason a debug token is not available, you can export an app to a .bar-file and sideload it (via Sachesi for instance) on each build. Not that fast and no capability to debug but this is at least something.
For now, this infrastructure does work but it can stop working anytime soon. Presumably, it can happen in January 2022
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
[
{
@.": "http://schema.org",
@.": "EmailMessage",
"potentialAction": {
@.": "ViewAction",
"target": "https://github.com/AlexeyGurevsky/bbtube/issues/2#issuecomment-945165844",
"url": "https://github.com/AlexeyGurevsky/bbtube/issues/2#issuecomment-945165844",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
@.": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

@mathewjpotter
It builds just fine on my machine.
Here is the log:
20:40:00 **** Incremental Build of configuration Device-Debug for project databasecrud ****
make -j6 Device-Debug
make -C .//translations -f Makefile update
make[1]: Entering directory 'C:/sources/BB/databasecrud/translations'
C:/bbndk/host_10_3_1_12/win32/x86/usr/bin/lupdate databasecrud.pro
Updating 'databasecrud.ts'...
Found 33 source text(s) (0 new and 33 already existing)
make[1]: Leaving directory 'C:/sources/BB/databasecrud/translations'
make -C .//translations -f Makefile release
make[1]: Entering directory 'C:/sources/BB/databasecrud/translations'
C:/bbndk/host_10_3_1_12/win32/x86/usr/bin/lrelease databasecrud.pro
Updating 'C:/sources/BB/databasecrud/translations/databasecrud.qm'...
Generated 0 translation(s) (0 finished and 0 unfinished)
Ignored 33 untranslated source text(s)
make[1]: Leaving directory 'C:/sources/BB/databasecrud/translations'
make -C ./arm -f Makefile debug
make[1]: Entering directory 'C:/sources/BB/databasecrud/arm'
c:/bbndk/host_10_3_1_12/win32/x86/usr/bin/qmake.exe -spec ../../../../bbndk/target_10_3_1_995/qnx6/usr/share/qt4/mkspecs/blackberry-armv7le-qcc CONFIG+=debug_and_release CONFIG+=device -o Makefile ../databasecrud.pro
make -f Makefile.Debug
make[2]: Entering directory 'C:/sources/BB/databasecrud/arm'
make[2]: Nothing to be done for 'first'.
make[2]: Leaving directory 'C:/sources/BB/databasecrud/arm'
make[1]: Leaving directory 'C:/sources/BB/databasecrud/arm'
20:40:01 Build Finished (took 1s.315ms)
I don't know why it doesn't work on yours, perhaps you imported only a part of the project if that's possible.
Also go to Momentics->Project menu -> Properties -> BlackBerry API Level->Check that 'Blackberry 10 Native SDK 10.3.1' is selected

I figured it!
The Swift Team - SwiftGrid.net
Swift Media Group Ltd. - a partner to grow with
#200, 200 Carnegie Road.| St. Albert, AB | Canada | T8N 1H4
Secure and Confidential Communication
This e-mail message and any attachments to this e-mail are the privileged and confidential information of Swift Media Group Ltd. and are intended solely for the individual or entity named as the recipient.
If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication, or any attachment to this email is strictly prohibited. If you have received this communication in error, please notify the sender, and delete this message and any attachments immediately.
On Oct 20, 2021, 2:18 PM -0700, @.***, wrote:

Is this the same when you run it on the device?
Are u on discord?
Matt
The Swift Team - SwiftGrid.net
Swift Media Group Ltd. - a partner to grow with
#200, 200 Carnegie Road.| St. Albert, AB | Canada | T8N 1H4
Secure and Confidential Communication
This e-mail message and any attachments to this e-mail are the privileged and confidential information of Swift Media Group Ltd. and are intended solely for the individual or entity named as the recipient.
If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication, or any attachment to this email is strictly prohibited. If you have received this communication in error, please notify the sender, and delete this message and any attachments immediately.
On Oct 20, 2021, 10:45 AM -0700, AlexeyGurevsky @.***>, wrote:

@mathewjpotter
It builds just fine on my machine.
Here is the log:
20:40:00 **** Incremental Build of configuration Device-Debug for project databasecrud ****
make -j6 Device-Debug
make -C .//translations -f Makefile update
make[1]: Entering directory 'C:/sources/BB/databasecrud/translations'
C:/bbndk/host_10_3_1_12/win32/x86/usr/bin/lupdate databasecrud.pro
Updating 'databasecrud.ts'...
Found 33 source text(s) (0 new and 33 already existing)
make[1]: Leaving directory 'C:/sources/BB/databasecrud/translations'
make -C .//translations -f Makefile release
make[1]: Entering directory 'C:/sources/BB/databasecrud/translations'
C:/bbndk/host_10_3_1_12/win32/x86/usr/bin/lrelease databasecrud.pro
Updating 'C:/sources/BB/databasecrud/translations/databasecrud.qm'...
Generated 0 translation(s) (0 finished and 0 unfinished)
Ignored 33 untranslated source text(s)
make[1]: Leaving directory 'C:/sources/BB/databasecrud/translations'
make -C ./arm -f Makefile debug
make[1]: Entering directory 'C:/sources/BB/databasecrud/arm'
c:/bbndk/host_10_3_1_12/win32/x86/usr/bin/qmake.exe -spec ../../../../bbndk/target_10_3_1_995/qnx6/usr/share/qt4/mkspecs/blackberry-armv7le-qcc CONFIG+=debug_and_release CONFIG+=device -o Makefile ../databasecrud.pro
make -f Makefile.Debug
make[2]: Entering directory 'C:/sources/BB/databasecrud/arm'
make[2]: Nothing to be done for 'first'.
make[2]: Leaving directory 'C:/sources/BB/databasecrud/arm'
make[1]: Leaving directory 'C:/sources/BB/databasecrud/arm'
20:40:01 Build Finished (took 1s.315ms)
I don't know why it doesn't work on yours, perhaps you imported only a part of the project if that's possible.
Also go to Momentics->Project menu -> Properties -> BlackBerry API Level->Check that 'Blackberry 10 Native SDK 10.3.1' is selected
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Hey Alex, pop by the the berryfarm os telegram,
A good group of bb10 devs
https://t.me/berryfarm_org
The Swift Team - SwiftGrid.net
Swift Media Group Ltd. - a partner to grow with
#200, 200 Carnegie Road.| St. Albert, AB | Canada | T8N 1H4
Secure and Confidential Communication
This e-mail message and any attachments to this e-mail are the privileged and confidential information of Swift Media Group Ltd. and are intended solely for the individual or entity named as the recipient.
If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication, or any attachment to this email is strictly prohibited. If you have received this communication in error, please notify the sender, and delete this message and any attachments immediately.
On Oct 20, 2021, 2:29 PM -0700, @.***, wrote:

I figured it!
The Swift Team - SwiftGrid.net
Swift Media Group Ltd. - a partner to grow with
#200, 200 Carnegie Road.| St. Albert, AB | Canada | T8N 1H4
Secure and Confidential Communication
This e-mail message and any attachments to this e-mail are the privileged and confidential information of Swift Media Group Ltd. and are intended solely for the individual or entity named as the recipient.
If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication, or any attachment to this email is strictly prohibited. If you have received this communication in error, please notify the sender, and delete this message and any attachments immediately.
On Oct 20, 2021, 2:18 PM -0700, @.***, wrote:

Is this the same when you run it on the device?
Are u on discord?
Matt
The Swift Team - SwiftGrid.net
Swift Media Group Ltd. - a partner to grow with
#200, 200 Carnegie Road.| St. Albert, AB | Canada | T8N 1H4
Secure and Confidential Communication
This e-mail message and any attachments to this e-mail are the privileged and confidential information of Swift Media Group Ltd. and are intended solely for the individual or entity named as the recipient.
If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication, or any attachment to this email is strictly prohibited. If you have received this communication in error, please notify the sender, and delete this message and any attachments immediately.
On Oct 20, 2021, 10:45 AM -0700, AlexeyGurevsky @.***>, wrote:

@mathewjpotter
It builds just fine on my machine.
Here is the log:
20:40:00 **** Incremental Build of configuration Device-Debug for project databasecrud ****
make -j6 Device-Debug
make -C .//translations -f Makefile update
make[1]: Entering directory 'C:/sources/BB/databasecrud/translations'
C:/bbndk/host_10_3_1_12/win32/x86/usr/bin/lupdate databasecrud.pro
Updating 'databasecrud.ts'...
Found 33 source text(s) (0 new and 33 already existing)
make[1]: Leaving directory 'C:/sources/BB/databasecrud/translations'
make -C .//translations -f Makefile release
make[1]: Entering directory 'C:/sources/BB/databasecrud/translations'
C:/bbndk/host_10_3_1_12/win32/x86/usr/bin/lrelease databasecrud.pro
Updating 'C:/sources/BB/databasecrud/translations/databasecrud.qm'...
Generated 0 translation(s) (0 finished and 0 unfinished)
Ignored 33 untranslated source text(s)
make[1]: Leaving directory 'C:/sources/BB/databasecrud/translations'
make -C ./arm -f Makefile debug
make[1]: Entering directory 'C:/sources/BB/databasecrud/arm'
c:/bbndk/host_10_3_1_12/win32/x86/usr/bin/qmake.exe -spec ../../../../bbndk/target_10_3_1_995/qnx6/usr/share/qt4/mkspecs/blackberry-armv7le-qcc CONFIG+=debug_and_release CONFIG+=device -o Makefile ../databasecrud.pro
make -f Makefile.Debug
make[2]: Entering directory 'C:/sources/BB/databasecrud/arm'
make[2]: Nothing to be done for 'first'.
make[2]: Leaving directory 'C:/sources/BB/databasecrud/arm'
make[1]: Leaving directory 'C:/sources/BB/databasecrud/arm'
20:40:01 Build Finished (took 1s.315ms)
I don't know why it doesn't work on yours, perhaps you imported only a part of the project if that's possible.
Also go to Momentics->Project menu -> Properties -> BlackBerry API Level->Check that 'Blackberry 10 Native SDK 10.3.1' is selected
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


PlotDeformationMap routine

Created a PlotDeformationMap() routine which plots the deformation map (strainrate or stress vs. T/stress or T/strainrate) for a (composite) rheology.
It is quite customisable and you can plot either stress, strainrate or effective viscosity:
julia> v1 = SetDiffusionCreep("Dry Anorthite | Rybacki et al. (2006)")
julia> v2 = SetDislocationCreep("Dry Anorthite | Rybacki et al. (2006)")
julia> v=CompositeRheology(v1,v2)
julia> PlotDeformationMap(v, levels=100, colormap=:roma)

julia> PlotDeformationMap(v,  strainrate=false, viscosity=true, levels=Vector(18:.25:24), rotate_axes=true)

This looks very nice, but why don't you ask users to simply pass in args, instead of passing specific arguments such as grainsize and fugacity?
That would make this work for future (combined) rheologies as well

I have made a few changes compared to the initial routine, which should make this more future-proof (will also work with new rheologies and not just for diffusion/dislocation creep).
Along the way, most changes requested by Albert were implemented. Instead of using contourf to add colors in the background, we now use heatmap, as the colors are otherwise cutoff at the lower/upper boundary.

We do have a remaining issue, which is that plotting routines are only loaded once GLMakie is loaded. Similarly, documentation for those routines is only generated once this is the case. Yet, loading GLMakie does not work with CI, as the machines there do not have screens.
Not sure what the best way is to solve this.


Warnings fixed, sfreerdp allow to specify certificate

I´ll merge this and add the silence warning macro in another one.


chore(main): release 0.1.15

:robot: I have created a release beep boop
0.1.15 (2024-06-06)
🪲 Bug Fixes

build arm on macos-latest (40e8b84)
enabled cgo (#168) (0bbc037)
remove duplicated linux-arm64 from release (647abb2)

♾ Continuous Integration

fix artifacts (a88fc9d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/prgres/clickup-tui/releases/tag/v0.1.15 :sunflower:


Integrate particle source

Integrate particle source over the timestep of the simulation. It will reduce particle conservation error for noisy or fast varying impurity sources.

@fsciortino  I need the approval of this pull request. I'm not allowed to merge it before approval. All regression tests have passed, so hopefully the installation issues are fixed.

@odstrcilt I haven't been following this. Is it still relevant? The tests are passed. I can do a quick review if useful.

@fsciortino ready to be merged


Test the Update Admin and Developer AWS Roles in ECF Forge

Describe the Issue
Ticket #2255 updates this role base access to account
This ticket is to verify the new roles have been implemented and nothing has been broken
Acceptance Criteria

Test the new role implementation fill the requirement criteria
Test that nothing breaks
Create a simple test case to apply to Assembly and Live if the same upgrade is applied in these LZ

Contract ends.This task would require a dedicated QA


Update NextDNS

Description
√ Added support for pagination in Search Logs
√ Added support for adding domain to the lists from Search Logs
Screencast

Checklist

[ ] I read the extension guidelines
[ ] I read the documentation about publishing
[ ] I ran npm run build and tested this distribution build in Raycast
[ ] I checked that files in the assets folder are used by the extension itself
[ ] I checked that assets used by the README are placed outside of the metadata folder

CC @jfkisafk / @xmok


dropping nulls with masking not working like i thought it would

https://github.com/jsadler2/river-dl/blob/452d1ce5fef5d73504a76a37c2a54f2d3f715b4c/river_dl/preproc_utils.py#L265
I thought I was dropping nan values before reducing observations, but it appears that I wasn't.
TL;DR
I should have been using .dropna() and not masking using .notnull() - Still not sure why that is though

For reference:
using .notnull()
In [1]: df
Out[1]:
          0
0 -0.501162
1 -0.870652
2       NaN

In [2]: df.notnull()
Out[2]:
       0
0   True
1   True
2  False

In [3]: df[df.notnull()]
Out[3]:
          0
0 -0.501162
1 -0.870652
2       NaN

I thought that would work because this works when dealing with pandas Series and Numpy Arrays. I just assumed that it was working for pandas DF, too. 🤦
What I should be doing:
In [4]: df.dropna()
Out[4]:
          0
0 -0.501162
1 -0.870652

.dropna() seems like the best approach, but I think the issue with your .notnull() code was that you needed to extract a simple array from the DataFrame returned by .notnull():
>>> df
   vals
0   0.0
1   3.0
2   5.0
3   NaN
>>> df.notnull()
    vals
0   True
1   True
2   True
3  False
>>> df[df.notnull()]
   vals
0   0.0
1   3.0
2   5.0
3   NaN
>>> df.notnull().values.flatten()
array([ True,  True,  True, False])
>>> df[df.notnull().values.flatten()]
   vals
0   0.0
1   3.0
2   5.0

Right. The masking approach drops the masked values with either a numpy array (what you get when you call the .values attribute) or a pandas Series. With pandas DataFrames (what I was using) the shape of the data is maintained and the masked values are simply changed to nan (which in this case they were already nan so we don't see a change.)