comparison with http-shutdown

Hello,
I was wondering if maybe you could provide some element of comparison with other modules that tackle the same problem. In particular I see http-shutdown that looks pretty similar. Is there some more corner cases that are better covered by graceful-http ?
Also can you tell me what level of confidence you have that this module is production ready ?

The library that you mentioned seems really old, has fewer tests, and seems to be missing some features/options. Of course, highly apprecieted any open-source libraries that tries to solve issues. In the past I also did a library like this that also didn't work properly for all cases: like-server
This is the main difference, and this is what truly achieves a graceful http server close:
https://github.com/LuKks/graceful-http/blob/d74cdcb42e1719a7b7ad21ba7c752d3aa72200ef/index.js#L49
Besides other tweaks, but that header is the most important part.

Also, read this blog, which is the only one that I found that explains the problem and solution perfectly: https://blog.dashlane.com/implementing-nodejs-http-graceful-shutdown/
That is the source of the code, besides I added more things, tests, etc.

Thanks. In the meantime I found this module that looks pretty good too http-terminator. I think this one properly closes the connection as you do.


Can't get "npx create-divi-extension my-extension" to work

Problem Description
Running npx create-divi-extension my-extension currently results in the following output:
Aborting installation.
Unexpected error. Please report it as a bug:
Error: Cannot find module '/Users/example/projects/divi-local-dev/app/public/wp-content/plugins/example-divi-extension/node_modules/divi-scripts/package.json'
Require stack:
- /Users/example/.npm/_npx/11760/lib/node_modules/create-divi-extension/createDiviExtension.js
- /Users/example/.npm/_npx/11760/lib/node_modules/create-divi-extension/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._load (internal/modules/cjs/loader.js:746:27)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:101:18)
    at checkNodeVersion (/Users/example/.npm/_npx/11760/lib/node_modules/create-divi-extension/createDiviExtension.js:552:23)
    at /Users/example/.npm/_npx/11760/lib/node_modules/create-divi-extension/createDiviExtension.js:340:7
    at processTicksAndRejections (internal/process/task_queues.js:95:5) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/example/.npm/_npx/11760/lib/node_modules/create-divi-extension/createDiviExtension.js',
    '/Users/example/.npm/_npx/11760/lib/node_modules/create-divi-extension/index.js'
  ]
}

Steps To Reproduce
Local: v6.5.2
Node: v14.21.1
NPM: 6.14.17
Yarn (via NPM): 3.3.0
I tried the latest LTS version of Node (as described in the How To Create A Divi Extension tutorial, but then I got the following error in a pack.log:
Packing grunt-po2mo@https://github.com/elegantthemes/grunt-po2mo.git#commit=26eca7c892db50837b58fdcf3771c5eb331a2ead from sources
Using Yarn Classic for bootstrap. Reason: "__metadata" key not found in yarn.lock, must be a Yarn classic lockfile

➤ YN0000: Retrieving https://classic.yarnpkg.com/latest.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-1.22.19.cjs
➤ YN0000: Done in 1s 391ms

yarn install v1.22.19
[1/5] Validating package.json...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "12.x || 14.x". Got "18.12.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

I'm stuck. Really frustrating, as I'm really motivated to dive into the Divi Extension world :)
Appreciate any hint! What version work for you?

@ekesto Sorry for the late response and for the issue you experienced with.
Unfortunately, it only supports Node 14.x at this moment. Divi builder itself is still using Node 14.x as well as the other ET products like Extra theme and Bloom plugin. So, I will suggest you to use switch to Node 14.x on your project extension.

@ayubadiputra, thanks for your feedback.
As noted in my post, I did change the versions to the following:
Local: v6.5.2
Node: v14.21.1
NPM: 6.14.17
Yarn (via NPM): 3.3.0
With this setup I get the error described in Problem Description above.. Any clue on what that could be?

We just fixed the incompatible Grunt and Node versions issue here Package :: Update grunt-wp-i18n dependency to fix incompatible grunt and node version. It should work now. However, it's still require Node 14 (i.e. 14.17.0) due to Divi Builder 4 still use Node 14 as well.
Here the video how the latest update works:
https://user-images.githubusercontent.com/9313128/229263392-c9b987fc-4b7d-46ad-80bc-1716fa910cfd.mp4


cant make pdfs (on some computers)

hi David,
on 3 of 5 computers we get this exception, however it works on the last two. any ideas?

works fine on your build on food4rhino but not when we build ourselves.
Crashes here:
https://github.com/interopxyz/PdfPlus/blob/0b32ed9027619f9e94ba5ce1fc0f91c046255f6d/PdfPlus/Classes/Page.cs#L169
I tried putting breakpoints inside the render method with no luck.
Doesnt even fire the method.

I've added all of the projects you uploaded with zip, but only referenced PdfSharp and PdfSharp.Charting.
Should I reference something else instead?

works for making empty pdfs with no objects..  but still failing in the .render somehow

fixed when we reference the GDI libraries and not the standard ones!'


Added checkImages() trigger

I created a trigger to run the image check manually. Issue: https://github.com/Pentiado/angular-lazy-img/issues/5

+1 for this feature

I feel it's not totally ok to use $rootScope for this purpose but...well after all better something than nothing. Thanks for pull request!

yeah, had no better solution for a quick fix ;)


Generalize the OCI metrics integration, using qualified injection of Config

Description
Configuration for the OCI metrics integration might come from different sources. This PR slightly generalizes how the Config is injected into the bean which starts up the integration.
The "start-up" bean now injects a @Qualified Config instance and provides a default producer for that qualified Config which is the normally-injected Config itself. There is no change in the behavior of this library when used as in the past.
The change is if another library includes a higher-priority bean which also produces the qualified Config bean, in which case this library uses that config instance instead.
Documentation
No functional change, and we do not intend for users to take advantage of this generalization themselves.
No doc impact.

Closing - this PR is obsolete in favor of superseding PR #8419


Can't change to another account on login

When I'm trying to log in to facebook Its jsut suggest the old user and dosent let the option of change account/add another account
🐛 Bug Report
When user try to log in to another account its remember the last user and dosent let to connect to another user
To Reproduce
When user log in to facebook
Expected Behavior
Expected Behavior so user can change between accounts of facebooks

I think it is not related to the package. Just use your browser to log out from your old account. Then you can enter new credentials after click on the Facebook login button.

Hi there!
https://stackoverflow.com/help/minimal-reproducible-example
https://stackoverflow.com/help/minimal-reproducible-example
No information on versions in use or a minimal app.js that has code which would show the problem, so no help is really possible thus I'll close
may just be that you are not logging the user out correctly, but who can say with the information provided...

I think it is not related to the package. Just use your browser to log out from your old account. Then you can enter new credentials after click on the Facebook login button.

So, how can I improve the user experience and disconnect him from the previous user from the broswer?


Normalize values schema

What this PR does / why we need it
Towards https://github.com/giantswarm/roadmap/issues/2099
This PR applies schemalint normalize to the schema. The effect is that key order and white space get normailzed and subsequent PRs will not contain such purely cosmetic changes.
This has no logical effect on the chart.
Checklist

[ ] Update changelog in CHANGELOG.md.

Trigger e2e tests

/test create
/test upgrade

acceptance-tests fails with this error:
helm upgrade --install test /home/circleci/project/helm/rendered/cluster-gcp --set gcp.project="test-project" --set organization="test" --set baseDomain="example.com"
Release "test" does not exist. Installing it now.
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Cluster" in version "cluster.x-k8s.io/v1beta1", unable to recognize "": no matches for kind "GCPCluster" in version "infrastructure.cluster.x-k8s.io/v1beta1", unable to recognize "": no matches for kind "GCPMachineTemplate" in version "infrastructure.cluster.x-k8s.io/v1beta1", unable to recognize "": no matches for kind "KubeadmConfigTemplate" in version "bootstrap.cluster.x-k8s.io/v1beta1", unable to recognize "": no matches for kind "KubeadmControlPlane" in version "controlplane.cluster.x-k8s.io/v1beta1", unable to recognize "": no matches for kind "MachineDeployment" in version "cluster.x-k8s.io/v1beta1"]
make: *** [Makefile.custom.mk:15: deploy-rendered-chart] Error 1


Update programs_to_target_by_GUID.bat

Updated HP GUID's thanks to /u/RockaiE
https://www.reddit.com/r/TronScript/comments/42bjoh/hp_preloaded_software_not_considered_bloat/

Just manually added these, wish I'd seen this PR before doing that! Thanks kamakazechickn :P


Memory model image operands

Validates new memory model image operands: NonPrivateTexelKHR, MakeTexelAvailableKHR and MakeTexelVisibleKHR.

Rebased, squashed, and pushed into master as  1c128aa9ef


Unit | Component | sl tab panel: setActiveTab() does so correctly

Second tab now has active class@ 48 ms
Expected:
true
Result:
false
Source:
    at Object.<anonymous> (http://localhost:4200/assets/tests.js:28305:16)
    at Object.wrapper (http://localhost:4200/assets/test-support.js:38237:29)
    at runTest (http://localhost:4200/assets/test-support.js:2750:28)
    at Object.Test.run (http://localhost:4200/assets/test-support.js:2735:4)
    at http://localhost:4200/assets/test-support.js:2877:11

@notmessenger taking this.


Struct Generation

Adds support for generating structs and struct fields. There are four types of structs:

RefStruct (simple C-style structure)
OpaqueStruct (non-introspectable structure)
PublicClassStruct (GObject type class for vfuncs)
PrivateClassStruct (same as above, but private)

So far, only the first type is fully generated. Opaque structures are generated as before, by creating a class. We can extend this with automatic IntPtr support later. Class structures are out of scope for this PR (I'll work on those along with vfuncs later).
This PR is mostly complete, but it needs a few changes to the type resolution code (few compile errors in the generated code), so it's a draft PR for now.
Edit: Note to myself for future reference, should probably make 'OpaqueStruct' the default in the switch statement, otherwise  we might get errors for some corner cases.

That was more straightforward than I thought it'd be.
Everything compiles under CI other than the samples, so I think this is good to go.


TEST:add roipoint_pool3d api check cases

Thanks for your contribution and we appreciate it a lot.
1. Motivation
添加roipoint_pool3d防呆测例
2. Modification
1.roipoint_pool3d.cpp文件：
检查描述符指针：handle、points_desc、 point_features_desc、boxes3d_desc、pooled_features_desc、pooled_empty_flag_desc为空防呆；
检查指针：points、point_features、boxes3d、workspace、pooled_features、pooled_empty_flag为空防呆
2.roipoint_pool3d_workspace.cpp文件：
检查描述符指针：handle、points_desc、 point_features_desc、boxes3d_desc、pooled_features_desc、pooled_empty_flag_desc为空防呆；
检查指针：size为空防呆
3.roipoint_pool3d_general.cpp文件：
对输入输出支持的 dtype、layout 以及 shape 进行防呆
0 元素检查防呆，VLOG(5)打印信息，返回MLUOP_STATUS_BAD_PARAM
large tensor防呆

测试报告：添加roipoint_pool3d防呆测例

测试结果：
Note: Google Test filter = *roipoint_pool3d*
[==========] Running 53 test cases from 16 test suites.
[----------] Global test environment set-up.
[----------] 12 tests from roipoint_pool3d
[ RUN      ] roipoint_pool3d.BAD_PARAM_handle_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: handle != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_handle_null (357 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_points_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: points_desc != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_points_desc_null (0 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_points_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: points != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_points_null (0 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_point_features_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: point_features_desc != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_point_features_desc_null (0 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_point_features_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: point_features != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_point_features_null (1 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_boxes3d_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: boxes3d_desc != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_boxes3d_desc_null (0 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_boxes3d_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: boxes3d != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_boxes3d_null (0 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_pooled_features_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: pooled_features_desc != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_pooled_features_desc_null (0 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_pooled_features_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: pooled_features != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_pooled_features_null (0 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_pooled_empty_flag_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: pooled_empty_flag_desc != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_pooled_empty_flag_desc_null (0 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_pooled_empty_flag_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: pooled_empty_flag != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_pooled_empty_flag_null (0 ms)
[ RUN      ] roipoint_pool3d.BAD_PARAM_workspace_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: workspace != NULL.
[       OK ] roipoint_pool3d.BAD_PARAM_workspace_null (0 ms)
[----------] 12 tests from roipoint_pool3d (358 ms total)

[----------] 7 tests from roipoint_pool3d_workspace
[ RUN      ] roipoint_pool3d_workspace.BAD_PARAM_handle_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: handle != NULL.
[       OK ] roipoint_pool3d_workspace.BAD_PARAM_handle_null (0 ms)
[ RUN      ] roipoint_pool3d_workspace.BAD_PARAM_points_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: points_desc != NULL.
[       OK ] roipoint_pool3d_workspace.BAD_PARAM_points_desc_null (0 ms)
[ RUN      ] roipoint_pool3d_workspace.BAD_PARAM_point_features_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: point_features_desc != NULL.
[       OK ] roipoint_pool3d_workspace.BAD_PARAM_point_features_desc_null (0 ms)
[ RUN      ] roipoint_pool3d_workspace.BAD_PARAM_boxes3d_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: boxes3d_desc != NULL.
[       OK ] roipoint_pool3d_workspace.BAD_PARAM_boxes3d_desc_null (0 ms)
[ RUN      ] roipoint_pool3d_workspace.BAD_PARAM_pooled_features_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: pooled_features_desc != NULL.
[       OK ] roipoint_pool3d_workspace.BAD_PARAM_pooled_features_desc_null (0 ms)
[ RUN      ] roipoint_pool3d_workspace.BAD_PARAM_pooled_empty_flag_desc_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: pooled_empty_flag_desc != NULL.
[       OK ] roipoint_pool3d_workspace.BAD_PARAM_pooled_empty_flag_desc_null (0 ms)
[ RUN      ] roipoint_pool3d_workspace.BAD_PARAM_size_null
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: size != NULL.
[       OK ] roipoint_pool3d_workspace.BAD_PARAM_size_null (0 ms)
[----------] 7 tests from roipoint_pool3d_workspace (0 ms total)

[----------] 1 test from zero_element_1/roipoint_pool3d_general
[ RUN      ] zero_element_1/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: element num zero.
[       OK ] zero_element_1/roipoint_pool3d_general.api_test/0 (0 ms)
[----------] 1 test from zero_element_1/roipoint_pool3d_general (0 ms total)

[----------] 1 test from zero_element_2/roipoint_pool3d_general
[ RUN      ] zero_element_2/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: element num zero.
[       OK ] zero_element_2/roipoint_pool3d_general.api_test/0 (0 ms)
[----------] 1 test from zero_element_2/roipoint_pool3d_general (0 ms total)

[----------] 1 test from zero_element_3/roipoint_pool3d_general
[ RUN      ] zero_element_3/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: element num zero.
[       OK ] zero_element_3/roipoint_pool3d_general.api_test/0 (0 ms)
[----------] 1 test from zero_element_3/roipoint_pool3d_general (0 ms total)

[----------] 1 test from zero_element_4/roipoint_pool3d_general
[ RUN      ] zero_element_4/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: element num zero.
[       OK ] zero_element_4/roipoint_pool3d_general.api_test/0 (0 ms)
[----------] 1 test from zero_element_4/roipoint_pool3d_general (0 ms total)

[----------] 1 test from zero_element_5/roipoint_pool3d_general
[ RUN      ] zero_element_5/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: element num zero.
[       OK ] zero_element_5/roipoint_pool3d_general.api_test/0 (0 ms)
[----------] 1 test from zero_element_5/roipoint_pool3d_general (0 ms total)

[----------] 5 tests from bad_points_dtype_dim_shape/roipoint_pool3d_general
[ RUN      ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (points_desc->dtype == MLUOP_DTYPE_FLOAT) || (points_desc->dtype == MLUOP_DTYPE_HALF).
[       OK ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/0 (0 ms)
[ RUN      ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/1
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: points_desc->dim == 3.
[       OK ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/1 (0 ms)
[ RUN      ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/2
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: points_desc->dims[2] == 3.
[       OK ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/2 (0 ms)
[ RUN      ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/3
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (points_desc->dims[0] == pooled_features_desc->dims[0]) && (point_features_desc->dims[0] == pooled_features_desc->dims[0]) && (boxes3d_desc->dims[0] == pooled_features_desc->dims[0]) && (pooled_empty_flag_desc->dims[0] == pooled_features_desc->dims[0]).
[       OK ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/3 (0 ms)
[ RUN      ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/4
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: points_desc->dims[1] == point_features_desc->dims[1].
[       OK ] bad_points_dtype_dim_shape/roipoint_pool3d_general.api_test/4 (0 ms)
[----------] 5 tests from bad_points_dtype_dim_shape/roipoint_pool3d_general (0 ms total)

[----------] 5 tests from bad_point_features_dtype_dim_shape/roipoint_pool3d_general
[ RUN      ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (points_desc->dtype == pooled_features_desc->dtype) && (point_features_desc->dtype == pooled_features_desc->dtype) && (boxes3d_desc->dtype == pooled_features_desc->dtype).
[       OK ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/0 (0 ms)
[ RUN      ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/1
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: point_features_desc->dim == 3.
[       OK ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/1 (1 ms)
[ RUN      ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/2
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (points_desc->dims[0] == pooled_features_desc->dims[0]) && (point_features_desc->dims[0] == pooled_features_desc->dims[0]) && (boxes3d_desc->dims[0] == pooled_features_desc->dims[0]) && (pooled_empty_flag_desc->dims[0] == pooled_features_desc->dims[0]).
[       OK ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/2 (0 ms)
[ RUN      ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/3
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: points_desc->dims[1] == point_features_desc->dims[1].
[       OK ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/3 (0 ms)
[ RUN      ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/4
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: point_features_desc->dims[2] + 3 == pooled_features_desc->dims[3].
[       OK ] bad_point_features_dtype_dim_shape/roipoint_pool3d_general.api_test/4 (0 ms)
[----------] 5 tests from bad_point_features_dtype_dim_shape/roipoint_pool3d_general (1 ms total)

[----------] 5 tests from bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general
[ RUN      ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (points_desc->dtype == pooled_features_desc->dtype) && (point_features_desc->dtype == pooled_features_desc->dtype) && (boxes3d_desc->dtype == pooled_features_desc->dtype).
[       OK ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/0 (0 ms)
[ RUN      ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/1
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: boxes3d_desc->dim == 3.
[       OK ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/1 (0 ms)
[ RUN      ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/2
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (points_desc->dims[0] == pooled_features_desc->dims[0]) && (point_features_desc->dims[0] == pooled_features_desc->dims[0]) && (boxes3d_desc->dims[0] == pooled_features_desc->dims[0]) && (pooled_empty_flag_desc->dims[0] == pooled_features_desc->dims[0]).
[       OK ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/2 (0 ms)
[ RUN      ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/3
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (pooled_features_desc->dims[1] == boxes3d_desc->dims[1]) && (pooled_empty_flag_desc->dims[1] == boxes3d_desc->dims[1]).
[       OK ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/3 (0 ms)
[ RUN      ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/4
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: boxes3d_desc->dims[2] == 7.
[       OK ] bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general.api_test/4 (0 ms)
[----------] 5 tests from bad_boxes3d_dtype_dim_shape/roipoint_pool3d_general (0 ms total)

[----------] 6 tests from bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general
[ RUN      ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (points_desc->dtype == pooled_features_desc->dtype) && (point_features_desc->dtype == pooled_features_desc->dtype) && (boxes3d_desc->dtype == pooled_features_desc->dtype).
[       OK ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/0 (0 ms)
[ RUN      ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/1
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: pooled_features_desc->dim == 4.
[       OK ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/1 (0 ms)
[ RUN      ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/2
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (points_desc->dims[0] == pooled_features_desc->dims[0]) && (point_features_desc->dims[0] == pooled_features_desc->dims[0]) && (boxes3d_desc->dims[0] == pooled_features_desc->dims[0]) && (pooled_empty_flag_desc->dims[0] == pooled_features_desc->dims[0]).
[       OK ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/2 (0 ms)
[ RUN      ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/3
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (pooled_features_desc->dims[1] == boxes3d_desc->dims[1]) && (pooled_empty_flag_desc->dims[1] == boxes3d_desc->dims[1]).
[       OK ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/3 (0 ms)
[ RUN      ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/4
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: sampled_pts_num == pooled_features_desc->dims[2].
[       OK ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/4 (0 ms)
[ RUN      ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/5
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: point_features_desc->dims[2] + 3 == pooled_features_desc->dims[3].
[       OK ] bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general.api_test/5 (0 ms)
[----------] 6 tests from bad_pooled_features_dtype_dim_shape/roipoint_pool3d_general (0 ms total)

[----------] 4 tests from bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general
[ RUN      ] bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: pooled_empty_flag_desc->dtype == MLUOP_DTYPE_INT32.
[       OK ] bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general.api_test/0 (0 ms)
[ RUN      ] bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general.api_test/1
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: pooled_empty_flag_desc->dim == 2.
[       OK ] bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general.api_test/1 (0 ms)
[ RUN      ] bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general.api_test/2
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (points_desc->dims[0] == pooled_features_desc->dims[0]) && (point_features_desc->dims[0] == pooled_features_desc->dims[0]) && (boxes3d_desc->dims[0] == pooled_features_desc->dims[0]) && (pooled_empty_flag_desc->dims[0] == pooled_features_desc->dims[0]).
[       OK ] bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general.api_test/2 (0 ms)
[ RUN      ] bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general.api_test/3
[2023-4-4 15:9:30] [MLUOP] [Error]:[mluOpRoiPointPool3d] Check failed: (pooled_features_desc->dims[1] == boxes3d_desc->dims[1]) && (pooled_empty_flag_desc->dims[1] == boxes3d_desc->dims[1]).
[       OK ] bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general.api_test/3 (0 ms)
[----------] 4 tests from bad_pooled_empty_flag_dtype_dim_shape/roipoint_pool3d_general (0 ms total)

[----------] 1 test from bad_large_tensor_1/roipoint_pool3d_general
[ RUN      ] bad_large_tensor_1/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Warning]:[mluOpSetTensorDescriptor]: overflow max tensor num.Currently, mluOp supports tensor num smaller than 2^31,now tensor dims:(14800,48367,3), data_width:4.
[2023-4-4 15:9:30] [MLUOP] [Error]:[[mluOpRoiPointPool3d]]: overflow max supported tensor num.<PHONE_NUMBER>, now tensor's total num is<PHONE_NUMBER>.
[       OK ] bad_large_tensor_1/roipoint_pool3d_general.api_test/0 (1 ms)
[----------] 1 test from bad_large_tensor_1/roipoint_pool3d_general (1 ms total)

[----------] 1 test from bad_large_tensor_2/roipoint_pool3d_general
[ RUN      ] bad_large_tensor_2/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Warning]:[mluOpSetTensorDescriptor]: overflow max tensor num.Currently, mluOp supports tensor num smaller than 2^31,now tensor dims:(14800,48367,7), data_width:4.
[2023-4-4 15:9:30] [MLUOP] [Warning]:[mluOpSetTensorDescriptor]: overflow max tensor num.Currently, mluOp supports tensor num smaller than 2^31,now tensor dims:(14800,48367,1,4), data_width:4.
[2023-4-4 15:9:30] [MLUOP] [Error]:[[mluOpRoiPointPool3d]]: overflow max supported tensor num.<PHONE_NUMBER>, now tensor's total num is<PHONE_NUMBER>.
[       OK ] bad_large_tensor_2/roipoint_pool3d_general.api_test/0 (2 ms)
[----------] 1 test from bad_large_tensor_2/roipoint_pool3d_general (2 ms total)

[----------] 1 test from bad_large_tensor_3/roipoint_pool3d_general
[ RUN      ] bad_large_tensor_3/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Warning]:[mluOpSetTensorDescriptor]: overflow max tensor num.Currently, mluOp supports tensor num smaller than 2^31,now tensor dims:(14800,1,1451001), data_width:4.
[2023-4-4 15:9:30] [MLUOP] [Warning]:[mluOpSetTensorDescriptor]: overflow max tensor num.Currently, mluOp supports tensor num smaller than 2^31,now tensor dims:(14800,1,1,1451004), data_width:4.
[2023-4-4 15:9:30] [MLUOP] [Error]:[[mluOpRoiPointPool3d]]: overflow max supported tensor num.<PHONE_NUMBER>, now tensor's total num is<PHONE_NUMBER>0.
[       OK ] bad_large_tensor_3/roipoint_pool3d_general.api_test/0 (0 ms)
[----------] 1 test from bad_large_tensor_3/roipoint_pool3d_general (0 ms total)

[----------] 1 test from bad_large_tensor_4/roipoint_pool3d_general
[ RUN      ] bad_large_tensor_4/roipoint_pool3d_general.api_test/0
[2023-4-4 15:9:30] [MLUOP] [Warning]:[mluOpSetTensorDescriptor]: overflow max tensor num.Currently, mluOp supports tensor num smaller than 2^31,now tensor dims:(14800,1,48367,4), data_width:4.
[2023-4-4 15:9:30] [MLUOP] [Error]:[[mluOpRoiPointPool3d]]: overflow max supported tensor num.<PHONE_NUMBER>, now tensor's total num is<PHONE_NUMBER>.
[       OK ] bad_large_tensor_4/roipoint_pool3d_general.api_test/0 (0 ms)
[----------] 1 test from bad_large_tensor_4/roipoint_pool3d_general (0 ms total)

[----------] Global test environment tear-down
[==========] 53 test cases from 16 test suites ran. (419 ms total)
[  PASSED  ] 53 test cases.


Some figures are cropped

Due to an upstream issue in matplotlib https://github.com/matplotlib/matplotlib/issues/6084

Not that there is still an issue when using very large linewidth.
with replot.Figure(xlabel="some x label",
                     ylabel="some y label",
                     title="A title for the figure",
                     legend=True) as figure:
    figure.plot(np.sin, linewidth=20)

Might be interesting https://github.com/mwaskom/seaborn/issues/875.

See as well https://stackoverflow.com/questions/19394505/matplotlib-expand-the-line-with-specified-width-in-data-unit/35501485#35501485.


Update Backend trait to use &mut self rather than &self

Problem
Currently in https://github.com/noir-lang/aztec_backend/pull/117 we're planning on merging the Plonk and Barretenberg structs so that only the Backend trait methods remains public while any other methods remain private to the crate. The benefit of this is that we'll no longer need to spin up a new wasm instance for call to the AVCM interop methods.
When interacting with WASM we need to mutate the Barretenberg struct when allocating/freeing memory so the current usage of immutable references prevents us from doing this.
Proposed solution
We should then update the following methods to use mutable references:
solve
solve_black_box_function_call
get_exact_circuit_size
preprocess
prove_with_pk
verify_with_vk
eth_contract_from_vk

Alternatives considered
No response
Additional context
No response
Submission Checklist

[X] Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.

Changing from &self to &mut self results in the following error:
error[E0053]: method `get_exact_circuit_size` has an incompatible type for trait
  --> acvm_backend_barretenberg/src/acvm_interop/proof_system.rs:13:31
   |
13 |     fn get_exact_circuit_size(&mut self, circuit: &Circuit) -> u32 {
   |                               ^^^^^^^^^
   |                               |
   |                               types differ in mutability
   |                               help: change the self-receiver type to match the trait: `self: &Barretenberg`
   |
   = note: expected signature `fn(&Barretenberg, &common::acvm::acir::circuit::Circuit) -> _`
              found signature `fn(&mut Barretenberg, &common::acvm::acir::circuit::Circuit) -> _`

I think the way that Blaine is saying is to have the trait use self and you define the implementation of the trait on &mut T -- this is opposed to having the trait use &mut self and then defining the implementation on T

@kevaundray I was unaware of the difference between self and &self in respect to mut but I'm intrigued by your comment. What would that look like in practice?

I was thinking about something like this:
pub trait NumberPrinter {
    fn print_number(self) -> String;
}

pub struct Foo{
    num : u32
}

impl NumberPrinter for &mut Foo {
    fn print_number(self) -> String {
        format!("my number is : {}", self.num)
    }
}

fn main() {
    let mut foo = Foo{num : 10};
    println!("{}",foo.print_number());
    println!("{}",(&mut foo).print_number());
}

The trait definition takes a self but since I implemented the trait on &mut Foo , self is really &mut self

Nice, some light hacking seems to seem that pub trait NumberPrinter would be need to be where Self: Sized. Is that right?

Closing this as some core methods didn't actually need &mut self at all so it's moot.


enhance: Support removing import job

Dry run:

Run:

Verify:

related to: https://github.com/milvus-io/milvus/issues/38313


[2pt]  Display reserved rockets in My profile - Filters

Render a list of all reserved rockets (use filter()) on the "My profile" page.

Task successfully completed


NodeJS SDK: Execute dagger sdk from within a container: spawn Unknown system error -8

What are you trying to do?
Execute nodejs sdk example from https://github.com/dagger/dagger/pull/3823 inside of a container that mounts /var/run/docker.sock (so called Docker Outside of Docker (DooD) setup).
To reproduce, use the following Dockerfile:
FROM node:18.12.1-alpine3.16

RUN apk update \
    && apk add docker-cli \
    && rm -rf /var/cache/apk/*

RUN apk update \
    && apk add shadow docker-cli \
    && rm -rf /var/cache/apk/*
RUN addgroup -S docker && adduser node docker

WORKDIR /app

CMD ["sleep", "infinity"]

and run:
docker rm -f dagger
docker build -t dagger:latest .
docker run -d --rm --name dagger -v /var/run/docker.sock:/var/run/docker.sock dagger:latest sleep infinity
docker exec -it dagger sh -c "groupmod -g \$(stat -c '%g' /var/run/docker.sock) docker"
docker exec -it dagger sh -c "docker run hello-world"
docker exec -it dagger sh -c "npm install ts-node"
docker exec -it dagger sh -c "npm pkg set type=module"
# Need tsconfig.json, otherwise getting "ReferenceError: exports is not defined in ES module scope"
# the https://github.com/dagger/dagger/pull/3823 doc may be incomplete/untested
docker exec -it dagger sh -c "echo '{\"compilerOptions\":{\"moduleResolution\":\"Node\",\"module\":\"ESNext\"}}' > tsconfig.json"
docker exec -it dagger sh -c "npm install<EMAIL_ADDRESS>docker exec -it dagger sh -c "echo 'import Client, { connect } from<EMAIL_ADDRESS>> build.ts"
docker exec -it dagger sh -c "echo 'connect(async (client: Client) => {})' >> build.ts"
docker exec -it dagger sh -c "node --loader ts-node/esm ./build.ts"

Output:
(node:97) ExperimentalWarning: Custom ESM Loaders is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Error: Command failed with Unknown system error -8: /root/.cache/dagger/dagger-engine-session-666b958a2f716c0d --remote docker-image://ghcr.io/dagger/engine:v0.3.4@sha256:666b958a2f716c0d6b22d869c585d6fe07954133ec769bb3d1f310e931cb118f --workdir /app
spawn Unknown system error -8
    at ChildProcess.spawn (node:internal/child_process:413:11)
    at Object.spawn (node:child_process:743:9)
    at execa (file:///app/node_modules/execa/index.js:84:26)
    at execaCommand (file:///app/node_modules/execa/index.js:229:9)
    at DockerImage.<anonymous> (file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:183:31)
    at Generator.next (<anonymous>)
    at file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:7:71
    at new Promise (<anonymous>)
    at __awaiter (file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:3:12)
    at DockerImage.runEngineSession (file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:175:16) {
  errno: -8,
  code: 'Unknown system error -8',
  syscall: 'spawn',
  originalMessage: 'spawn Unknown system error -8',
  shortMessage: 'Command failed with Unknown system error -8: /root/.cache/dagger/dagger-engine-session-666b958a2f716c0d --remote docker-image://ghcr.io/dagger/engine:v0.3.4@sha256:666b958a2f716c0d6b22d869c585d6fe07954133ec769bb3d1f310e931cb118f --workdir /app\n' +
    'spawn Unknown system error -8',
  command: '/root/.cache/dagger/dagger-engine-session-666b958a2f716c0d --remote docker-image://ghcr.io/dagger/engine:v0.3.4@sha256:666b958a2f716c0d6b22d869c585d6fe07954133ec769bb3d1f310e931cb118f --workdir /app',
  escapedCommand: '"/root/.cache/dagger/dagger-engine-session-666b958a2f716c0d" --remote "docker-image://ghcr.io/dagger/engine:v0.3.4@sha256:666b958a2f716c0d6b22d869c585d6fe07954133ec769bb3d1f310e931cb118f" --workdir "/app"',
  exitCode: undefined,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr: '',
  all: '',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

The host environment:
cat /etc/*release | grep PRETTY
PRETTY_NAME="Ubuntu 20.04.5 LTS"

docker version
Client: Docker Engine - Community
 Version:           20.10.18
 API version:       1.41
 Go version:        go1.18.6
 Git commit:        b40c2f6
 Built:             Thu Sep  8 23:11:45 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.18
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.6
  Git commit:       e42327a
  Built:            Thu Sep  8 23:09:37 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.8
  GitCommit:        9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Why is this important to you?
The dagger sdk documentation provides a traditional path with developer managing a given programming language environment on the machine.  When configuring developer machines it may be preferable that no software is installed, except for docker, graphical programs and possibly single binaries, and all commands to be executed inside of containers. Another use case of DooD is when executing CI pipelines from custom containers.
How are you currently working around this?
Unknown

With<EMAIL_ADDRESS>I'm getting:
(node:97) ExperimentalWarning: Custom ESM Loaders is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:149
            throw new Error(`failed to copy engine session binary: ${e}`);
                  ^
Error: failed to copy engine session binary: Error: Command failed with exit code 1: docker run --rm --entrypoint /bin/cat ghcr.io/dagger/engine:v0.3.4@sha256:666b958a2f716c0d6b22d869c585d6fe07954133ec769bb3d1f310e931cb118f /usr/bin/dagger-engine-session-linux-x64
cat: can't open '/usr/bin/dagger-engine-session-linux-x64': No such file or directory
    at DockerImage.pullEngineSessionBin (file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:149:19)
    at DockerImage.<anonymous> (file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:83:22)
    at Generator.next (<anonymous>)
    at file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:7:71
    at new Promise (<anonymous>)
    at __awaiter (file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:3:12)
    at DockerImage.Connect (file:///app/node_modules/@dagger.io/dagger/dist/provisioning/docker-provision/image.js:79:16)
    at file:///app/node_modules/@dagger.io/dagger/dist/connect.js:24:36
    at Generator.next (<anonymous>)
    at file:///app/node_modules/@dagger.io/dagger/dist/connect.js:7:71

With<EMAIL_ADDRESS>I'm getting:

Sorry @marcindulak you keep hitting issues as we hit them and fix them in parallel, that issue was fixed here and should be out in a new alpha soon https://github.com/dagger/dagger/pull/3858

My original example works now when installing the latest docker exec -it dagger sh -c "npm install @dagger.io/dagger", however only after some adjustements to the nodejs sdk docs https://github.com/dagger/dagger/pull/3823. I'll open an additional issue.
I see that<EMAIL_ADDRESS>has been removed, 0.1.0-alpha.2 (a new upload?) is still present, and this step fails:
docker exec -it dagger sh -c "npm install<EMAIL_ADDRESS>...
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

Can you check whether there is something wrong with versioning of the package?

I was not able to reproduce the additional issue in https://github.com/dagger/dagger/pull/3823 I mentioned above: the problem was due to skipping of npx create-react-app my-app --template typescript so tsconfig.json was missing, as can be seen in my original example.

The new docker exec -it dagger sh -c "npm install<EMAIL_ADDRESS>is installable, and it looks like the originally reported spawn Unknown system error -8 issue is fixed.

Closing this issue as fixed. @marcindulak Feel free to reopen it if needed. Thanks


 Start: 0, stop: 0 2022-11-08T12:16:13.673Z [V4L2:USB VIDEO: USB] (Grabber.cpp:145) Set new width: 1024, height: 768 for capture 2022-11-08T12:16:13.673Z [V4L2:USB VIDEO: USB] (Grabber.cpp:322) setWidthHeight preparing to restarting video grabber 0 2022-11-08T12:16:13.674Z [V4L2:USB VIDEO: USB] Delayed restart of the grabber due to change of the capturing resolution 2022-11-08T12:16:13.674Z [V4L2:USB VIDEO: USB] Delayed restart of the grabber due to change of the framerate 2022-11-08T12:16:13.675Z [V4L2:USB VIDEO: USB] (Grabber.cpp:259) setBrightnessContrastSaturationHue nothing changed 2022-11-08T12:16:13.675Z [V4L2:USB VIDEO: USB] setHdrToneMappingMode to: enable, but the LUT file is currently unloaded 2022-11-08T12:16:13.675Z [V4L2:USB VIDEO: USB] (Grabber.cpp:168) setFpsSoftwareDecimation to: 1 2022-11-08T12:16:13.676Z [SIGNAL_OLD] (DetectionManual.cpp:85) Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000 2022-11-08T12:16:13.676Z [SIGNAL_OLD] (DetectionManual.cpp:75) Signal threshold set to: {0, 0, 0} and frames: 50 2022-11-08T12:16:13.677Z [SIGNAL_AUTO] (DetectionAutomatic.cpp:382) Automatic signal detection -> errorTolerance: 9, modelTolerance: 90, sleepTime: 1000, wakeTime: 0 2022-11-08T12:16:13.677Z [V4L2:USB VIDEO: USB] (Grabber.cpp:367) setDeviceVideoStandard preparing to restart video grabber. Old: '' new: 'USB Video: USB Video (video0)' 2022-11-08T12:16:13.677Z [V4L2:USB VIDEO: USB] Delayed restart of the grabber due to change of selected device 2022-11-08T12:16:13.678Z [V4L2:USB VIDEO: USB] (Grabber.cpp:186) Force encoding to: mjpeg (old: NO_CHANGE) 2022-11-08T12:16:13.678Z [V4L2:USB VIDEO: USB] Delayed restart of the grabber due to change of the video encoding format 2022-11-08T12:16:13.679Z [V4L2:USB VIDEO: USB] setQFrameDecimation is now: disabled 2022-11-08T12:16:13.679Z [V4L2:USB Video: USB] (GrabberWrapper.cpp:545) Frame cache is: enabled 2022-11-08T12:16:13.682Z [PIPEWIRE_SYSTEM:AUTO] Cropping image: width=0 height=0; crop: left=0 right=0 top=0 bottom=0  2022-11-08T12:16:13.695Z [PIPEWIRE_SYSTEM:AUTO] Could not load Pipewire proxy library. Error: libpipewire-0.3.so.0: cannot open shared object file: No such file or directory 2022-11-08T12:16:13.696Z [DAEMON] The system doesn't support the Pipewire/Portal grabber 2022-11-08T12:16:13.696Z [X11_SYSTEM:AUTO] Cropping image: width=0 height=0; crop: left=0 right=0 top=0 bottom=0  2022-11-08T12:16:13.741Z [X11_SYSTEM:AUTO] Loaded X11 proxy library for screen capturing 2022-11-08T12:16:13.753Z [DAEMON] The system doesn't support the X11 grabber 2022-11-08T12:16:13.754Z [FRAMEBUFFER_SYSTEM:AUTO] Cropping image: width=0 height=0; crop: left=0 right=0 top=0 bottom=0  2022-11-08T12:16:13.755Z [DAEMON] The system doesn't support the FrameBuffer grabber 2022-11-08T12:16:13.956Z [SETTINGSMGR] Settings database initialized 2022-11-08T12:16:13.977Z [BLACKBORDER] Set mode to: default 2022-11-08T12:16:13.978Z [IMAGETOLED0] (ImageProcessor.cpp:161) Set LED mapping type to advanced 2022-11-08T12:16:13.979Z [IMAGETOLED0] (ImageProcessor.cpp:145) setSparseProcessing to 0 2022-11-08T12:16:13.982Z [RGB_TRANSFORM0] RGB transform classic_config: 1, saturationGain: 1.000000, luminanceGain: 1.000000, backlightThreshold: 1 2022-11-08T12:16:13.983Z [RGB_TRANSFORM0] setBacklightThreshold: 1 2022-11-08T12:16:13.983Z [ADJUST_RED0] Set correction to 255 2022-11-08T12:16:13.983Z [ADJUST_BLUE0] Set correction to 255 2022-11-08T12:16:13.983Z [ADJUST_GREEN0] Set correction to 255 2022-11-08T12:16:14.017Z [JSONSERVER] (JsonServer.cpp:24) Created instance 2022-11-08T12:16:14.041Z [JSONSERVER] Started on port 19444 2022-11-08T12:16:14.085Z [PIPEWIRE_SYSTEM:auto] (SystemWrapper.cpp:75) Closing grabber: PIPEWIRE_SYSTEM:auto 2022-11-08T12:16:14.087Z [X11_SYSTEM:auto] (SystemWrapper.cpp:75) Closing grabber: X11_SYSTEM:auto 2022-11-08T12:16:14.088Z [FRAMEBUF_SYSTEM:auto] (SystemWrapper.cpp:75) Closing grabber: FRAMEBUF_SYSTEM:auto 2022-11-08T12:16:13.992Z [HYPERHDR0] Led strip RGB order is: rgb 2022-11-08T12:16:13.993Z [DB] Database opened: /root/.hyperhdr/db/hyperhdr.db 2022-11-08T12:16:14.014Z [SMOOTHING0] High resolution clock is NOT STEADY! 2022-11-08T12:16:14.014Z [SMOOTHING0] Clearing queued colors before: enabling 2022-11-08T12:16:14.014Z [SMOOTHING0] Smoothing queue is cleared 2022-11-08T12:16:14.014Z [COMPONENTREG0] Smoothing: enabled 2022-11-08T12:16:14.014Z [SMOOTHING0] Creating config (0) => type: Alternative, dirMode: false, pause: false, settlingTime: 150ms, interval: 20ms (50Hz), antiFlickTres: 0, antiFlickStep: 2, antiFlickTime: 0 2022-11-08T12:16:14.014Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer. 2022-11-08T12:16:14.015Z [SMOOTHING0] Smoothing queue is cleared 2022-11-08T12:16:14.015Z [SMOOTHING0] Selecting config (0) => type: Alternative, dirMode: false, pause: false, settlingTime: 150ms, interval: 20ms (50Hz), antiFlickTres: 0, antiFlickStep: 2, antiFlickTime: 0 2022-11-08T12:16:14.015Z [SMOOTHING0] Selecting config (0) => type: Alternative, dirMode: false, pause: false, settlingTime: 150ms, interval: 20ms (50Hz), antiFlickTres: 0, antiFlickStep: 2, antiFlickTime: 0 2022-11-08T12:16:14.016Z [LEDDEVICE_WS281X] Start LedDevice 'ws281x'. 2022-11-08T12:16:14.017Z [LEDDEVICE_WS281X] (LedDevice.cpp:162) deviceConfig: [{"colorOrder":"rgb","currentLedCount":333,"dma":5,"gpio":18,"invert":false,"leds":333,"pwmchannel":0,"refreshTime":0,"rgbw":false,"type":"ws281x","whiteAlgorithm":"subtract_minimum"}] 2022-11-08T12:16:14.018Z [LEDDEVICE_WS281X] (LedDevice.cpp:226) RefreshTime updated to 0ms 2022-11-08T12:16:14.018Z [LEDDEVICE_WS281X] (LedDeviceWS281x.cpp:59) ws281x strip type : 1050624 2022-11-08T12:16:14.019Z [LEDDEVICE_WS281X] (LedDevice.cpp:100) Enable device 2022-11-08T12:16:14.020Z [MUXER0] Register new input 'System/VIDEOGRABBER' with priority 240 as inactive 2022-11-08T12:16:14.020Z [COMPONENTREG0] Video capture device: enabled 2022-11-08T12:16:14.089Z [V4L2:USB VIDEO: USB] Multithreading for V4L2 is enabled. Available thread's count 4 2022-11-08T12:16:14.090Z [V4L2:USB VIDEO: USB] Found capture device: /dev/video14 2022-11-08T12:16:14.091Z [V4L2:USB VIDEO: USB] Found capture device: /dev/video22 2022-11-08T12:16:14.093Z [V4L2:USB VIDEO: USB] Found capture device: /dev/video15 2022-11-08T12:16:14.095Z [V4L2:USB VIDEO: USB] Found capture device: /dev/video21 2022-11-08T12:16:14.097Z [V4L2:USB VIDEO: USB] Found capture device: /dev/video0 2022-11-08T12:16:14.097Z [V4L2:USB VIDEO: USB] (V4L2Grabber.cpp:402) Device has 'brightness' control => min: -128, max: 127, default: -11 2022-11-08T12:16:14.098Z [V4L2:USB VIDEO: USB] (V4L2Grabber.cpp:408) Device has 'contrast' control => min: 0, max: 255, default: 148 2022-11-08T12:16:14.098Z [V4L2:USB VIDEO: USB] (V4L2Grabber.cpp:414) Device has 'saturation' control => min: 0, max: 255, default: 180 2022-11-08T12:16:14.099Z [V4L2:USB VIDEO: USB] (V4L2Grabber.cpp:420) Device has 'hue' control => min: -128, max: 127, default: 0 2022-11-08T12:16:14.102Z [V4L2:USB VIDEO: USB] (V4L2Grabber.cpp:212) Searching for USB Video: USB Video (video0) 1024 x 768 @ 30 fps, input: -1 (mjpeg) 2022-11-08T12:16:14.103Z [V4L2:USB VIDEO: USB] ************************************************************************************************* 2022-11-08T12:16:14.103Z [V4L2:USB VIDEO: USB] Starting V4L2 grabber. Selected: USB Video: USB Video (video0) [/dev/video0] 1024 x 768 @ 30 fps mjpeg 2022-11-08T12:16:14.104Z [V4L2:USB VIDEO: USB] ************************************************************************************************* 2022-11-08T12:16:14.104Z [V4L2:USB VIDEO: USB] (V4L2Grabber.cpp:807) Hardware cropping is not supported: ignoring 2022-11-08T12:16:14.105Z [V4L2:USB VIDEO: USB] Set device input to: Camera 1 2022-11-08T12:16:14.106Z [V4L2:USB VIDEO: USB] Set resolution to: 1024 x 768 2022-11-08T12:16:14.108Z [V4L2:USB VIDEO: USB] Set framerate to 30 FPS 2022-11-08T12:16:14.108Z [V4L2:USB VIDEO: USB] Brightness set to: -11 (default) 2022-11-08T12:16:14.109Z [V4L2:USB VIDEO: USB] Contrast set to: 148 (default) 2022-11-08T12:16:14.110Z [V4L2:USB VIDEO: USB] Saturation set to: 180 (default) 2022-11-08T12:16:14.110Z [V4L2:USB VIDEO: USB] Hue set to: 0 (default) 2022-11-08T12:16:14.111Z [V4L2:USB VIDEO: USB] (V4L2Grabber.cpp:105) LUT folder location: '/usr/share/hyperhdr/lut' 2022-11-08T12:16:14.112Z [V4L2:USB VIDEO: USB] LUT file is not found here: /root/.hyperhdr/lut_lin_tables.3d 2022-11-08T12:16:14.113Z [V4L2:USB VIDEO: USB] (Grabber.cpp:445) LUT file found: /usr/share/hyperhdr/lut/lut_lin_tables.3d 2022-11-08T12:16:14.114Z [V4L2:USB VIDEO: USB] (Grabber.cpp:455) Index 1 for HDR YUV 2022-11-08T12:16:16.404Z [V4L2:USB VIDEO: USB] Found and loaded LUT: '/usr/share/hyperhdr/lut/lut_lin_tables.3d' 2022-11-08T12:16:16.404Z [V4L2:USB VIDEO: USB] Video pixel format is set to: MJPEG 2022-11-08T12:16:16.418Z [V4L2:USB VIDEO: USB] Started 2022-11-08T12:16:14.021Z [LEDDEVICE_WS281X] (LedDevice.cpp:308) Switch on 2022-11-08T12:16:14.021Z [LEDDEVICE_WS281X] (LedDevice.cpp:384) Power On 2022-11-08T12:16:16.419Z [HYPERMANAGER] HyperHDR instance 'First LED instance' has been started 2022-11-08T12:16:16.421Z [DAEMON] Unload CEC 2022-11-08T12:16:14.022Z [COMPONENTREG0] HDR (global): enabled 2022-11-08T12:16:14.022Z [COMPONENTREG0] LED device: enabled 2022-11-08T12:16:14.023Z [EFFECTENGINE0] Run effect "Rainbow swirl fast" on channel 0 2022-11-08T12:16:14.043Z [FLATBUFSERVER] Started on port 19400 2022-11-08T12:16:14.044Z [FLATBUFSERVER] Started local domain socket server: 'hyperhdr-domain' 2022-11-08T12:16:14.092Z [EFFECTENGINE0] (EffectEngine.cpp:174) Start the effect: name [Rainbow swirl fast], smoothCfg [2] 2022-11-08T12:16:14.093Z [MUXER0] Register new input 'System/EFFECT' with priority 0 as inactive 2022-11-08T12:16:14.093Z [HYPERHDR] Initial foreground effect 'Rainbow swirl fast' started 2022-11-08T12:16:14.094Z [SMOOTHING0] Using alternative smoothing input (0) 2022-11-08T12:16:14.094Z [SMOOTHING0] Using alternative smoothing procedure (0) 2022-11-08T12:16:14.118Z [EFFECT0(Rainbo...)] Begin playing the effect with priority: 0 2022-11-08T12:16:14.196Z [MUXER0] Priority 0 is now active 2022-11-08T12:16:14.196Z [MUXER0] Set visible priority to 0 2022-11-08T12:16:14.196Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer. 2022-11-08T12:16:14.197Z [SMOOTHING0] Smoothing queue is cleared 2022-11-08T12:16:14.197Z [SMOOTHING0] Selecting config (2) => type: Linear, dirMode: false, pause: false, settlingTime: 200ms, interval: 40ms (25Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0 2022-11-08T12:16:14.197Z [SMOOTHING0] Using linear smoothing input (2) 2022-11-08T12:16:14.197Z [HYPERHDR0] New priority[0], previous [255] 2022-11-08T12:16:14.198Z [HYPERHDR0] New source available -> switch LED-Device on 2022-11-08T12:16:14.198Z [SMOOTHING0] Clearing queued colors before: enabling 2022-11-08T12:16:14.198Z [SMOOTHING0] Smoothing queue is cleared 2022-11-08T12:16:14.201Z [LEDDEVICE_WS281X] (LedDevice.cpp:100) Enable device 2022-11-08T12:16:14.204Z [IMAGETOLED0] Total index number is: 1116 (memory: 1116). User sparse processing is: disabled, image size: 80 x 45, area number: 333 2022-11-08T12:16:14.205Z [SMOOTHING0] Using linear smoothing input (2) 2022-11-08T12:16:14.239Z [SMOOTHING0] Using linear smoothing procedure (2) 2022-11-08T12:16:16.422Z [WEBSERVER] Initialize Webserver 2022-11-08T12:16:16.423Z [WEBSERVER] Initialize Webserver 2022-11-08T12:16:16.499Z [V4L2:USB VIDEO: USB] (V4L2Grabber.cpp:1145) Worker's thread count  = 4 2022-11-08T12:16:16.564Z [V4L2:USB Video: USB] Detected the video frame size changed (1024x768). Cache buffer was cleared. 2022-11-08T12:16:16.565Z [MUXER0] Priority 240 is now active 2022-11-08T12:16:16.726Z [WEBSERVER] Apply Webserver settings 2022-11-08T12:16:16.727Z [WEBSERVER] Set document root to: :/webconfig 2022-11-08T12:16:16.727Z [WEBSERVER] Apply Webserver settings 2022-11-08T12:16:16.730Z [WEBSERVER] Set document root to: :/webconfig 2022-11-08T12:16:16.733Z [WEBSERVER] Started on port 8090 name 'HyperHDR Webserver' 2022-11-08T12:16:16.803Z [WEBSERVER] Setup SSL certificate 2022-11-08T12:16:16.805Z [WEBSERVER] Setup private SSL key 2022-11-08T12:16:16.808Z [WEBSERVER] Started on port 8092 name 'HyperHDR Webserver' 2022-11-08T12:16:17.118Z [EFFECT0(Rainbo...)] The effect quits with priority: 0 2022-11-08T12:16:17.120Z [MUXER0] Removed source priority 0 2022-11-08T12:16:17.121Z [MUXER0] Set visible priority to 240 2022-11-08T12:16:17.123Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer. 2022-11-08T12:16:17.124Z [SMOOTHING0] Smoothing queue is cleared 2022-11-08T12:16:17.126Z [SMOOTHING0] Selecting config (0) => type: Alternative, dirMode: false, pause: false, settlingTime: 150ms, interval: 20ms (50Hz), antiFlickTres: 0, antiFlickStep: 2, antiFlickTime: 0 2022-11-08T12:16:17.127Z [SMOOTHING0] Using alternative smoothing input (0) 2022-11-08T12:16:17.127Z [HYPERHDR0] New priority[240], previous [0] 2022-11-08T12:16:17.130Z [EFFECTENGINE0] Effect 'Rainbow swirl fast' has finished. 2022-11-08T12:16:17.131Z [EFFECT0(Rainbo...)] Deleting effect named: 'Rainbow swirl fast' 2022-11-08T12:16:17.133Z [EFFECT0(Rainbo...)] Effect named: 'Rainbow swirl fast' is deleted 2022-11-08T12:16:17.188Z [IMAGETOLED0] Total index number is: 172544 (memory: 172544). User sparse processing is: disabled, image size: 1024 x 768, area number: 333 2022-11-08T12:16:17.202Z [SMOOTHING0] Using alternative smoothing procedure (0) 2022-11-08T12:16:35.120Z [WEBSOCKET] (WebSocketClient.cpp:30) New connection from ::ffff:<IP_ADDRESS> 2022-11-08T12:16:35.124Z [WEBSOCKET] (JsonAPI.cpp:97) Client '::ffff:<IP_ADDRESS>' switch to HyperHDR instance 0 2022-11-08T12:16:35.465Z [DB] Database opened: /root/.hyperhdr/db/hyperhdr.db 2022-11-08T12:16:35.866Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:<IP_ADDRESS> 2022-11-08T12:18:24.877Z [PERFORMANCE] [USB capturing: FPS = 30.03, decoding = 29ms, frames = 1802, invalid = 0], [INSTANCE0: FPS = 30.02, processed = 1801], [LED0: FPS = 50.00, send = 3000, processed = 3000] 2022-11-08T12:18:24.877Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 5, hits: 3474, needed: 1, cleanup: 0, limit: 8 2022-11-08T12:18:24.937Z [WEBSOCKET] (JsonAPI.cpp:1259) log streaming deactivated for client  ::ffff:<IP_ADDRESS> 2022-11-08T12:19:22.139Z [PERFORMANCE] Under-voltage detected. The system is not stable. Please fix it! 2022-11-08T12:19:24.857Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 4, hits: 1800, needed: 0, cleanup: 0, limit: 8 2022-11-08T12:19:24.877Z [PERFORMANCE] [USB capturing: FPS = 29.99, decoding = 29ms, frames = 1799, invalid = 0], [INSTANCE0: FPS = 30.01, processed = 1801], [LED0: FPS = 50.00, send = 3000, processed = 3000] 2022-11-08T12:20:22.129Z [PERFORMANCE] Under-voltage detected. The system is not stable. Please fix it! 2022-11-08T12:20:24.870Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 3, hits: 1801, needed: 0, cleanup: 1, limit: 8 2022-11-08T12:20:24.885Z [PERFORMANCE] [USB capturing: FPS = 30.01, decoding = 35ms, frames = 1801, invalid = 0], [INSTANCE0: FPS = 30.01, processed = 1801], [LED0: FPS = 50.00, send = 3000, processed = 3000] 2022-11-08T12:21:22.135Z [PERFORMANCE] Under-voltage detected. The system is not stable. Please fix it! 2022-11-08T12:21:24.881Z [PERFORMANCE] [USB capturing: FPS = 30.03, decoding = 31ms, frames = 1802, invalid = 0], [INSTANCE0: FPS = 30.01, processed = 1800], [LED0: FPS = 50.00, send = 3000, processed = 3000] 2022-11-08T12:21:24.881Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 4, hits: 1801, needed: 1, cleanup: 0, limit: 8 2022-11-08T12:22:22.132Z [PERFORMANCE] Under-voltage detected. The system is not stable. Please fix it! 2022-11-08T12:22:24.885Z [PERFORMANCE] [USB capturing: FPS = 30.01, decoding = 31ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.02, processed = 1802], [LED0: FPS = 50.00, send = 3000, processed = 3000] 2022-11-08T12:23:22.137Z [PERFORMANCE] Under-voltage detected. The system is not stable. Please fix it! 2022-11-08T12:23:24.869Z [PERFORMANCE] [USB capturing: FPS = 30.01, decoding = 35ms, frames = 1801, invalid = 0], [INSTANCE0: FPS = 30.01, processed = 1800], [LED0: FPS = 50.00, send = 3000, processed = 3000] 2022-11-08T12:24:22.127Z [PERFORMANCE] Under-voltage detected. The system is not stable. Please fix it! 2022-11-08T12:24:24.882Z [PERFORMANCE] [USB capturing: FPS = 30.01, decoding = 32ms, frames = 1801, invalid = 0], [INSTANCE0: FPS = 30.01, processed = 1801], [LED0: FPS = 50.00, send = 3000, processed = 3000] 2022-11-08T12:25:22.131Z [PERFORMANCE] Under-voltage detected. The system is not stable. Please fix it! 2022-11-08T12:25:24.861Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 3, hits: 1800, needed: 0, cleanup: 0, limit: 8 2022-11-08T12:25:24.884Z [PERFORMANCE] [USB capturing: FPS = 29.99, decoding = 34ms, frames = 1799, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 50.00, send = 3000, processed = 3000] 2022-11-08T12:26:22.132Z [PERFORMANCE] Under-voltage detected. The system is not stable. Please fix it! 2022-11-08T12:26:24.873Z [PERFORMANCE] [USB capturing: FPS = 30.01, decoding = 32ms, frames = 1801, invalid = 0], [INSTANCE0: FPS = 30.01, processed = 1800], [LED0: FPS = 50.00, send = 3000, processed = 3000] 2022-11-08T12:26:24.874Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 3, hits: 1801, needed: 1, cleanup: 0, limit: 8 2022-11-08T12:27:18.260Z [LEDDEVICE_WS281X] (LedDevice.cpp:63) Stop device 2022-11-08T12:27:18.261Z [LEDDEVICE_WS281X] (LedDevice.cpp:134) Disable device 2022-11-08T12:27:18.261Z [LEDDEVICE_WS281X] (LedDevice.cpp:334) Switch off 2022-11-08T12:27:18.261Z [LEDDEVICE_WS281X] (LedDevice.cpp:370) Power Off 2022-11-08T12:27:18.261Z [LEDDEVICE_WS281X] (LedDevice.cpp:292) Set LED strip to black/power off 2022-11-08T12:27:18.297Z [LEDDEVICE_WS281X]  Stopped LedDevice 'ws281x' 2022-11-08T12:27:18.299Z [LEDDEVICE_WS281X] Start LedDevice 'ws281x'. 2022-11-08T12:27:18.299Z [COMPONENTREG0] LED device: disabled 2022-11-08T12:27:18.299Z [PERFORMANCE] [USB capturing: FPS = 30.01, decoding = 32ms, frames = 1801, invalid = 0], [INSTANCE0: FPS = 30.01, processed = 1800] 2022-11-08T12:27:18.299Z [LEDDEVICE_WS281X] (LedDevice.cpp:162) deviceConfig: [{"colorOrder":"rgb","currentLedCount":333,"dma":5,"gpio":18,"hardwareLedCount":null,"invert":false,"leds":333,"pwmchannel":0,"refreshTime":1000,"rgbw":false,"type":"ws281x","whiteAlgorithm":"subtract_minimum"}] 2022-11-08T12:27:18.300Z [LEDDEVICE_WS281X] (LedDevice.cpp:216) Refresh interval = 1000ms 2022-11-08T12:27:18.300Z [LEDDEVICE_WS281X] (LedDevice.cpp:191) Device is not ready to start a timer 2022-11-08T12:27:18.300Z [LEDDEVICE_WS281X] (LedDevice.cpp:226) RefreshTime updated to 1000ms 2022-11-08T12:27:18.300Z [LEDDEVICE_WS281X] (LedDeviceWS281x.cpp:59) ws281x strip type : 1050624 2022-11-08T12:27:18.301Z [LEDDEVICE_WS281X] (LedDevice.cpp:100) Enable device 2022-11-08T12:27:18.302Z [LEDDEVICE_WS281X] (LedDevice.cpp:308) Switch on 2022-11-08T12:27:18.303Z [LEDDEVICE_WS281X] (LedDevice.cpp:384) Power On 2022-11-08T12:27:18.303Z [LEDDEVICE_WS281X] (LedDevice.cpp:185) Starting timer with interval = 1000ms 2022-11-08T12:27:18.312Z [COMPONENTREG0] LED device: enabled 2022-11-08T12:27:26.346Z [HYPERHDR0] New RGB order is: gbr 2022-11-08T12:27:26.375Z [IMAGETOLED0] Total index number is: 172544 (memory: 172544). User sparse processing is: disabled, image size: 1024 x 768, area number: 333 2022-11-08T12:27:26.376Z [LEDDEVICE_WS281X] (LedDevice.cpp:63) Stop device 2022-11-08T12:27:26.376Z [LEDDEVICE_WS281X] (LedDevice.cpp:134) Disable device 2022-11-08T12:27:26.377Z [LEDDEVICE_WS281X] (LedDevice.cpp:199) Stopping timer 2022-11-08T12:27:26.377Z [LEDDEVICE_WS281X] (LedDevice.cpp:334) Switch off 2022-11-08T12:27:26.377Z [LEDDEVICE_WS281X] (LedDevice.cpp:370) Power Off 2022-11-08T12:27:26.377Z [LEDDEVICE_WS281X] (LedDevice.cpp:292) Set LED strip to black/power off 2022-11-08T12:27:26.409Z [LEDDEVICE_WS281X]  Stopped LedDevice 'ws281x' 2022-11-08T12:27:26.411Z [LEDDEVICE_WS281X] Start LedDevice 'ws281x'. 2022-11-08T12:27:26.411Z [COMPONENTREG0] LED device: disabled 2022-11-08T12:27:26.411Z [LEDDEVICE_WS281X] (LedDevice.cpp:162) deviceConfig: [{"colorOrder":"gbr","currentLedCount":333,"dma":5,"gpio":18,"hardwareLedCount":null,"invert":false,"leds":333,"pwmchannel":0,"refreshTime":1000,"rgbw":false,"type":"ws281x","whiteAlgorithm":"subtract_minimum"}] 2022-11-08T12:27:26.412Z [LEDDEVICE_WS281X] (LedDevice.cpp:216) Refresh interval = 1000ms 2022-11-08T12:27:26.412Z [LEDDEVICE_WS281X] (LedDevice.cpp:191) Device is not ready to start a timer 2022-11-08T12:27:26.412Z [LEDDEVICE_WS281X] (LedDevice.cpp:226) RefreshTime updated to 1000ms 2022-11-08T12:27:26.413Z [LEDDEVICE_WS281X] (LedDeviceWS281x.cpp:59) ws281x strip type : 1050624 2022-11-08T12:27:26.413Z [LEDDEVICE_WS281X] (LedDevice.cpp:100) Enable device 2022-11-08T12:27:26.415Z [LEDDEVICE_WS281X] (LedDevice.cpp:308) Switch on 2022-11-08T12:27:26.415Z [LEDDEVICE_WS281X] (LedDevice.cpp:384) Power On 2022-11-08T12:27:26.415Z [LEDDEVICE_WS281X] (LedDevice.cpp:185) Starting timer with interval = 1000ms 2022-11-08T12:27:26.426Z [COMPONENTREG0] LED device: enabled 2022-11-08T12:27:30.680Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:<IP_ADDRESS> 2022-11-08T12:29:24.876Z [PERFORMANCE] [USB capturing: FPS = 30.03, decoding = 31ms, frames = 1802, invalid = 0], [INSTANCE0: FPS = 30.02, processed = 1801], [LED0: FPS = 1.00, send = 60, processed = 3000] 2022-11-08T12:29:24.876Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 4, hits: 1801, needed: 0, cleanup: 0, limit: 8 2022-11-08T12:29:24.942Z [WEBSOCKET] (JsonAPI.cpp:1259) log streaming deactivated for client  ::ffff:<IP_ADDRESS> 2022-11-08T12:30:24.857Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 3, hits: 1799, needed: 0, cleanup: 1, limit: 8 2022-11-08T12:30:24.884Z [PERFORMANCE] [USB capturing: FPS = 29.99, decoding = 27ms, frames = 1799, invalid = 0], [INSTANCE0: FPS = 29.99, processed = 1800], [LED0: FPS = 1.00, send = 60, processed = 3000] 2022-11-08T12:31:24.869Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 2, hits: 1801, needed: 1, cleanup: 0, limit: 8 2022-11-08T12:31:24.898Z [PERFORMANCE] [USB capturing: FPS = 29.99, decoding = 35ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.01, processed = 1801], [LED0: FPS = 1.00, send = 60, processed = 3000] 2022-11-08T12:32:02.436Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:<IP_ADDRESS> 2022-11-08T12:32:24.880Z [PERFORMANCE] [USB capturing: FPS = 30.03, decoding = 27ms, frames = 1802, invalid = 0], [INSTANCE0: FPS = 30.03, processed = 1801], [LED0: FPS = 1.00, send = 60, processed = 3000] 2022-11-08T12:32:24.880Z [V4L2:USB VIDEO: USB] Video cache: enabled, size: 3, hits: 1801, needed: 1, cleanup: 0, limit: 8

Hi
Please set "refreshTime" to zero and test it again using HyperHDR effects. The log looks OK.


[INLONG-1975][Bug]error occurs when deleting a data access

Title Name: [INLONG-1975][Bug]error occurs when deleting a data access
Fixes #1975
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[X] Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Documentation

Does this pull request introduce a new feature? no

Codecov Report

Merging #1976 (4a8dfb0) into master (973958f) will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1976      +/-   ##
============================================
+ Coverage     12.24%   12.27%   +0.03%
- Complexity     1155     1157       +2
============================================
  Files           413      413
  Lines         35225    35225
  Branches       5542     5542
============================================
+ Hits           4312     4325      +13
+ Misses        30149    30129      -20
- Partials        764      771       +7

Impacted Files
Coverage Δ

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
34.07% <0.00%> (+1.10%)
:arrow_up:

.../inlong/tubemq/corebase/policies/FlowCtrlItem.java
38.88% <0.00%> (+2.22%)
:arrow_up:

...nlong/tubemq/corebase/policies/FlowCtrlResult.java
60.00% <0.00%> (+60.00%)
:arrow_up:

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 973958f...4a8dfb0. Read the comment docs.


chore: bump nuxt to rc13

Closes #13.
This PR:

bumps all nuxt deps to rc.13,
fixes new TS-errors that come from stricter TS + stricter schemas
switches to using the nuxt-native useFetch options, which removes a lot of duplicated interface code

Checklist:

[x] issue number linked above after pound (#)

replace "Closes " with "Contributes to" or other if this PR does not close the issue

[x] manually checked my feature / checking not applicable
[x] wrote tests / testing not applicable
[x] attached screenshots / screenshot not applicable

closed in favor of #57


numTokens query: provide optional owner

This way query can check how many an NFTs an owner holds

already covered in Tokens query.


add transparent background feature

assign None to the background of segments in themes, so as to make background transparent. This is for the integrated terminals of text editors like VScode.
Not a graceful way however.

I don't quite understand what's going on with this one here. Sorry it never got looked at. Feel free to re-open with conflicts resolved if you want to start a discussion.


Imu Data orientation using ENU

Hi,
I try the new parameters included in the version 3.0.0 and I didn't get a good configuration for the Ellipse D used.
The linear acceleration is inverted in Z.

Please find below the configuration file used under ROS.
I already check the configuration of the Ellipse with sbgCenter and a binary log, the orientation is fine.
Should I inverse Y axis in sbgCenter ? Will it invalidate all the computation done onboard the Ellipse ?
# Configuration file for SBG device through an Uart interface.

driver:
  # Node frequency (Hz)
  # Note: The frequency should be at least two times higher than the highest
  #       output frequency.
  #       The frequency can be reduced in order to reduce CPU consumption but
  #       it can lead to miss data frame and less accurate time stamping.
  frequency: 400

# Configuration of the device with ROS.
confWithRos: false

# Uart configuration
uartConf:
  # Port Name
  portName: "/dev/ttyS0"

  # Baude rate (4800 ,9600 ,19200 ,38400 ,115200 [default],230400 ,460800 ,921600)
  baudRate: 115200

  # Port Id
  # 0 PORT_A: Main communication interface. Full duplex.
  # 1 PORT_B: Auxiliary input interface for RTCM
  # 2 PORT_C: Auxiliary communication interface. Full duplex.
  # 3 PORT_D: Auxiliary input interface
  # 4 PORT_E: Auxiliary input/output interface
  portID: 0

# Sensor Parameters
sensorParameters:
  # Initial latitude (°)
  initLat: 48.419727
  # Initial longitude (°)
  initLong: -4.472119
  # Initial altitude (above WGS84 ellipsoid) (m)
  initAlt: 100.0
  # Year at startup
  year: 2021
  # month in year at startup
  month: 08
  # day in month at startup
  day: 05

  # Montion profile ID
  # 1 GENERAL_PURPOSE Should be used as a default when other profiles do not apply
  # 2 AUTOMOTIVE      Dedicated to car applications
  # 3 MARINE          Used in marine and underwater applications
  # 4 AIRPLANE        For fixed wings aircraft
  # 5 HELICOPTER      For rotary wing aircraft
  motionProfile: 2

# IMU_ALIGNMENT_LEVER_ARM
imuAlignementLeverArm:
  # IMU X axis direction in vehicle frame
  # 0 ALIGNMENT_FORWARD   IMU Axis is turned in vehicle's forward direction
  # 1 ALIGNMENT_BACKWARD  IMU Axis is turned in vehicle's backward direction
  # 2 ALIGNMENT_LEFT      IMU Axis is turned in vehicle's left direction
  # 3 ALIGNMENT_RIGHT     IMU Axis is turned in vehicle's right direction
  # 4 ALIGNMENT_UP        IMU Axis is turned in vehicle's up direction
  # 5 ALIGNMENT_DOWN      IMU Axis is turned in vehicle's down direction
  axisDirectionX: 0
  # IMU Y axis direction in vehicle frame
  # 0 ALIGNMENT_FORWARD   IMU Axis is turned in vehicle's forward direction
  # 1 ALIGNMENT_BACKWARD  IMU Axis is turned in vehicle's backward direction
  # 2 ALIGNMENT_LEFT      IMU Axis is turned in vehicle's left direction
  # 3 ALIGNMENT_RIGHT     IMU Axis is turned in vehicle's right direction
  # 4 ALIGNMENT_UP        IMU Axis is turned in vehicle's up direction
  # 5 ALIGNMENT_DOWN      IMU Axis is turned in vehicle's down direction
  axisDirectionY: 2  # Residual roll error after axis alignment rad
  misRoll: 0
  # Residual pitch error after axis alignment rad
  misPitch: 0
  # Residual yaw error after axis alignment rad
  misYaw: 0
  # X Primary lever arm in IMU X axis (once IMU alignment is applied) m
  leverArmX: 0
  # Y Primary lever arm in IMU Y axis (once IMU alignment is applied) m
  leverArmY: 0
  # Z Primary lever arm in IMU Z axis (once IMU alignment is applied) m
  leverArmZ: 0

# AIDING_ASSIGNMENT
# Note: GNSS1 module configuration can only be set to an external port on Ellipse-E version.
# Ellipse-N users must set this module to MODULE_INTERNAL. On the other hand, rtcmModule is only
# available for Ellipse-N users. This module must be set to MODULE_DISABLED for other users.
aidingAssignment:
  # GNSS module port assignment:
  # 255 Module is disabled
  # 1 Module connected on PORT_B
  # 2 Module connected on PORT_C
  # 3 Module connected on PORT_D
  # 5 Module is connected internally
  gnss1ModulePortAssignment: 5
  # GNSS module sync assignment:
  # 0 Module is disabled
  # 1 Synchronization is done using SYNC_IN_A pin
  # 2 Synchronization is done using SYNC_IN_B pin
  # 3 Synchronization is done using SYNC_IN_C pin
  # 4 Synchronization is done using SYNC_IN_D pin
  # 5 Synchronization is internal
  # 6 Synchronization is done using SYNC_OUT_A pin
  # 7 Synchronization is done using SYNC_OUT_B pin

  # RTCM input port assignment for Ellipse-N DGPS
  rtcmPortAssignment: 4
  # Odometer module pin assignment
  # 0 Odometer is disabled
  # 1 Odometer connected only to ODO_A (unidirectional).
  # 2 Odometer connected to both ODO_A (signal A) and ODO_B (Signal B or direction) for bidirectional odometer.
  odometerPinAssignment: 2

magnetometer:
  # Magnetometer model ID
  # 201 Should be used in most applications
  # 202 Should be used in disturbed magnetic environment
  magnetometerModel: 201
  # Magnetometer rejection mode
  # 0 Measurement is not taken into account
  # 1 Measurement is rejected if inconsistent with current estimate (depending on error model)
  # 2 Measurement is always accepted
  magnetometerRejectMode: 0

  # Theses parameters are only used for a calibration run
  calibration:
    # 1 2D Tell the device that the magnetic calibration will be performed with limited motions.
    #     This calibration mode is only designed to be used when roll and pitch motions are less than ± 5°.
    #     To work correctly, the device should be rotated through at least a full circle.
    # 2 3D Tell the device to start a full 3D magnetic calibration procedure. The 3D magnetic calibration offers the best accuracy
    mode: 2

    # 0 LOW_BW Use this parameter in case of strong magnetic noise during calibration.
    #     Motion during calibration is then limited to slow rotations.
    # 1 MEDIUM_BW Tell the device that medium dynamics will be observed during the magnetic calibration process.
    #     It can be used in case of medium magnetic noise during calibration process. Medium dynamics are used during calibration.
    # 2 HIGH_BW This parameter is suitable to most applications. It can be used when the dynamics during calibration are relatively high.
    bandwidth: 2

# GNSS configuration
# Note: Secondary level arms should only be considered in case of dual antenna GNSS receiver. It can be left to 0 otherwise.
gnss:
  # Gnss Model Id
  # 101 Used on Ellipse-N to setup the internal GNSS in GPS+GLONASS
  # 102 Default mode for Ellipse-E connection to external GNSS
  # 103 Used on Ellipse-N to setup the internal GNSS in GPS+BEIDOU
  # 104 Used on Ellipse-E to setup a connection to ublox in read only mode.
  # 106 Used on Ellipse-E to setup a connection to Novatel receiver in read only mode.
  # 107 Used on Ellipse-D by default
  gnss_model_id: 107

  #GNSS primary antenna lever arm in IMU X axis (m)
  primaryLeverArmX: -0.025
  #GNSS primary antenna lever arm in IMU Y axis (m)
  primaryLeverArmY: -0.034
  #GNSS primary antenna lever arm in IMU Z axis (m)
  primaryLeverArmZ: -0.455
  #GNSS primary antenna precise. Set to true if the primary lever arm has been accurately entered and doesn't need online re-estimation.
  primaryLeverPrecise: true

  #GNSS secondary antenna lever arm in IMU X axis (m)
  secondaryLeverArmX: -1.559
  #GNSS secondary antenna lever arm in IMU Y axis (m)
  secondaryLeverArmY: -0.247
  #GNSS secondary antenna lever arm in IMU Z axis (m)
  secondaryLeverArmZ: -0.350

  # Secondary antenna operating mode.
  # 1 The GNSS will be used in single antenna mode only and the secondary lever arm is not used.
  # 2 [Reserved] The GNSS dual antenna information will be used but the secondary lever arm is not known.
  # 3 The GNSS dual antenna information will be used and we have a rough guess for the secondary lever arm.
  # 4 The GNSS dual antenna information will be used and the secondary lever arm is accurately entered and doesn't need online re-estimation.
  secondaryLeverMode: 4

  # Rejection mode for position
  # 0 Measurement is not taken into account
  # 1 Measurement is rejected if inconsistent with current estimate (depending on error model)
  # 2 Measurement is always accepted
  posRejectMode: 1
  # Rejection mode for velocity (see posRejectMode values)
  velRejectMode: 1
  # Rejection mode for true heading (see posRejectMode values)
  hdtRejectMode: 1

# Odometer configuration
odom:
  # Odometer's gain Pulses/m
  gain: 652
  # User gain average error (%)
  gain_error: 90
  # Odometer's direction
  # 0: positive
  # 1: negative
  direction: 1

  # Odometer lever arm in IMU X axis (m)
  leverArmX: -1.32
  # Odometer lever arm in IMU Y axis (m)
  leverArmY: -0.48
  # Odometer lever arm in IMU Z axis (m)
  leverArmZ: 2

  # Odometer rejection mode
  # 0 Measurement is not taken into account
  # 1 Measurement is rejected if inconsistent with current estimate (depending on error model)
  # 2 Measurement is always accepted
  rejectMode: 1

# ToDo: event & CAN configuration

############################### Output configuration ###############################
# 0 Output is disabled
# 1 Output is generated at 200Hz
# 2 Output is generated at 100Hz
# 4 Output is generated at 50Hz
# 8 Output is generated at 25Hz
# 10 Output is generated at 20Hz
# 20 Output is generated at 10Hz
# 40 Output is generated at 5Hz
# 200 Output is generated at 1Hz
# 10000 Pulse Per Second. Same mode as above.
# 10001 Output sent when a new data is available.
# 10002 Output is generated when a new virtual odometer event occurs
# 10003 Output is generated on a Sync In A event
# 10004 Output is generated on a Sync In B event
# 10005 Output is generated on a Sync In C event
# 10006 Output is generated on a Sync In D event
output:
  # Time reference:
  # Note: Set the time reference used to timestamp the header of the published
  #       messages.
  #       The header of the ROS standard message sensor_msgs:TimeReference is
  #       not effected by this parameter and it will be timestamped by the ROS time.
  #
  # "ros" : ROS time (default)
  # "ins_unix" : INS absolute time referenced to UNIX epoch (00:00:00 UTC on 1 January 1970)
  time_reference: "ros"

  # Ros standard output:
  # Note: If true publish ROS standard messages.
  ros_standard: true

  # Frame convention:
  # Note: If true messages are expressed in the ENU convention.
  #
  # true : ENU convention (X east, Y north, Z up)
  # false (default): NED convention (X north, Y east, Z down)
  use_enu: true

  # Frame ID:
  # Note: If the frame convention is NED so the default frame ID is (imu_link_ned)
  #       else if the convention is ENU so the default frame ID is (imu_link)
  frame_id: "imu_link"

  # Status general, clock, com aiding, solution, heave
  log_status: 200
  # Includes IMU status, acc., gyro, temp delta speeds and delta angles values
  log_imu_data: 200 #8
  # Includes roll, pitch, yaw and their accuracies on each axis
  log_ekf_euler: 0
  # Includes the 4 quaternions values
  log_ekf_quat: 200 #8
  # Position and velocities in NED coordinates with the accuracies on each axis
  log_ekf_nav: 20
  # Heave, surge and sway and accelerations on each axis for up to 4 points
  log_ship_motion: 0
  # Provides UTC time reference
  log_utc_time: 200
  # Magnetic data with associated accelerometer on each axis
  log_mag: 0
  # Magnetometer calibration data (raw buffer)
  log_mag_calib: 0
  # GPS velocities from primary or secondary GPS receiver
  log_gps1_vel: 10
  # GPS positions from primary or secondary GPS receiver
  log_gps1_pos: 10 #0
  # GPS true heading from dual antenna system
  log_gps1_hdt: 10
  # GPS 1 raw data for post processing.
  log_gps1_raw: 10
  # Provides odometer velocity
  log_odo_vel: 10
  # Event A/B/C/D Event markers sent when events are detected on a sync in pin
  log_event_a: 0
  log_event_b: 0
  log_event_c: 0
  log_event_d: 0
  # Air data
  log_air_data: 0
  # Short IMU data
  log_imu_short: 200 #8

After some tests, I confirm that the ENU convention is respected.


Add Assistant#tool_resources example to README

The README needs a brief example of how to use tool_resources with Assistants, see here

Fixed in #469


Changed bevy-hid to bevy_hid

Great plugin with a lot of potentials! 🚀 As mentioned here by Alice, cargo is really poor at handling -, so using an underscore for the crate name eliminates the possibility of the same mishaps https://github.com/Leafwing-Studios/leafwing-input-manager/issues/160#issuecomment-1179759110. Also, the imports for the crate will be use bevy_hid::... either way, as rust doesn't support - in its import statement.

cargo is really poor at handling -

I think this is perhaps vague/misleading.
Cargo handles it fine, the concern is just that you have to remember to use the name of the package in Cargo.toml and not the name of the lib (they are allowed to be different). If you use dashes in your package name the lib name will automatically use underscores because dashes are not allowed in lib names (If they did, would a-b be subtracting a from b? or a package name? Harder to tell)
Note that if you put the package name in your cargo.toml file incorrectly, cargo will suggest the correct name for you.

It's not a bad idea to have the package name match the lib name to be consistent, I just don't think we need to make it sound like it will cause more problems than it does and the fact that cargo suggests the correct fix for you makes this less of an issue imo.

¯_(ツ)_/¯

Wasn't saying it was a bad idea, just wanted fishykins to know if he still wants to use dashes after having considered it, it's not going to cause any major issues, and plenty of people use dashes.
Might have to help a new comer here or there if they use the wrong name and don't read the cargo error is what this PR might prevent.

Oh, I wasn't looking at your username, thought you were @fishykins 😅.
Personally, I think that executables (bin) should be - and crates _.
As most crates (plugins) already uses it and bevy's other repos bevy-website & bevy-assets uses -


SVG billboard doesn't draw in Firefox

Reported on the forum: https://groups.google.com/forum/?hl=en#!topic/cesium-dev/eiFCPPlR19c
var viewer = new Cesium.Viewer('cesiumContainer');

var svg ='data:image/svg+xml,' +
           '<svg width="100%" height="100%" viewBox="0 0 48 48" version="1.1" xmlns="http://www.w3.org/2000/svg">';
svg += '<circle cx="24" cy="24" r="10" style="fill:#ff141e;stroke-width:2px;stroke:#ececec;" />';
svg += '</svg>';

var image = new Image();
image.src = svg;

viewer.entities.add({
   position : Cesium.Cartesian3.fromDegrees(-85, 40),
   billboard :{
       image : image
   }
});

This is almost certainly a problem in the SVG itself (or a bug in Firefox, but doubtful).  I'll see if I can dig up the forum conversation where I've discussed this in the past.

See #2907, which shows that svg billboard render in firefox just fine.  So this is most likely a problem with the svg or a bug in Firefox.
Keep in mind that IE will not load this either for security reasons they mark SVGs (at least hard coded ones) as tainted canvases that can't be used in WebGL.
@emackey might have some thoughts on why Firefox is barfing on the image; but otherwise I would file a bug with them.

This does appear to be a Firefox issue, because creating an SVG img tag in this fashion does not work in Firefox even on a page without Cesium.js.
Looks like the workaround for Firefox is to base-64 encode it, and wait for the onload event.
var viewer = new Cesium.Viewer('cesiumContainer');

var svg = '<svg width="48" height="48" viewBox="0 0 48 48" version="1.1" xmlns="http://www.w3.org/2000/svg">';
svg += '<circle cx="24" cy="24" r="10" style="fill:#ff141e;stroke-width:2px;stroke:#ececec;" />';
svg += '</svg>';

svg = 'data:image/svg+xml;base64,' + window.btoa(svg);

var image = new Image();

image.onload = function() {
    viewer.entities.add({
       position : Cesium.Cartesian3.fromDegrees(-85, 40),
       billboard :{
           image : image
       }
    });
};

image.src = svg;

Also the width="100%" and likewise the height is not valid in SVG, I changed this to width="48px".

Thanks @emackey!

Thanks @emackey


Support sub-second transitionTimes

Currently, transitionTime is documented to be in seconds (1). But the bridge is capable of handling transitions in 100-milliseconds resolution (2). Looking at the implementation in HueMagic it seems that the value is parsed as integer (3). Therefore, sub-second transition-times are not supported with HueMagic.
Expected behavior: This value should be parsed as fractional number, so that fragments of seconds can be specified. This should already be supported by HueJay (4).

This is correct and will be possible in the next update!
I’ll let you know when it’s ready :)!

Took almost a year but now finally possible from version 2+! :P


Design enhancement: Misc design changes to sensors page

@benardcharumbira requested first, but thank you @MohsinNajmuddin.
@benardcharumbira -- let us know if you have any trouble getting everything setup, and please join our slack channel.

@rdkelley noted thank you


Tuning for LM2 comp bot

Configuration:
Motors:
Port 0: frontRight
Port 1: frontLeft
Port 2: backRight
Port 3: backLeft


Fixed Documentation for MessageAction#reference

Pull Request Etiquette

[X] I have checked the PRs for upcoming features/bug fixes.
[X] I have read the contributing guidelines.

Changes

[ ] Internal code
[ ] Library interface (affecting end-user code)
[X] Documentation
[ ] Other: _____

Closes Issue: NaN
Description
This pull request syncs the documentation of MessageAction#reference and MessagesAction#referenceById

This needs to be rebased on docs/development.

I fixed your commit history. You can use the following commands to update your local repository:
git fetch --all
git reset --hard origin/patch-1


Cant' get it to work

On this system:
`PS D:\Users\eigil> wsl --status
Default Distribution: Ubuntu
Default Version: 2
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.33
MSRDC version: 1.2.2924
Direct3D version: 1.601.0
Windows version: 10.0.22610.1
PS D:\Users\eigil> wsl --list --all -v
NAME              STATE           VERSION

Ubuntu            Stopped         2
UbuntuTstGenie    Stopped         2
Ubuntu-22.04      Stopped         2
UbuntuDvlGenie    Running         2
UbuntuDvl         Stopped         2
UbuntuGenie       Stopped         2
UbuntuTst         Stopped         2
PS D:\Users\eigil>
`

I can't get it to work.

I tried
pwsh.exe -NonInteractive -NoProfile -ExecutionPolicy Bypass  -File "D:\Users\eigil\projects\myCommands\WSL_Div\one-script-wsl2-systemd\install.ps1"

That didn't do anything (as far as I could see).

Tried
pwsh.exe -NonInteractive -NoProfile -ExecutionPolicy Bypass -File "D:\Users\eigil\projects\myCommands\WSL_Div\one-script-wsl2-systemd\install.ps1" -distro UbuntuDvlGenie

That didn't do anything either (as far as I could see).

Then I tried the

Minimal manual installation

Now I get this errer

: command not found
-bash: /etc/profile.d/00-wsl2-systemd.sh: line 21: syntax error near unexpected token $'in\r'' 'bash: /etc/profile.d/00-wsl2-systemd.sh: line 21:             case "$0" in

when the distro is started.
--
Eigil

Please redownload the latest install.ps1 script and execute the command with -Debug appending to the commandline.
If it still doesn't work try without the pwsh.exe wrapper as in:
./install.ps1 -distro UbuntuDvlGenie -Debug


Fixes broken tests, adds experiment length to carbon impact statement, fixes abrupt stopping issue #37

Fixes #37 and adds test for it

Now also fixes #49

Now also fixes #49


How could I use remix-i18next inside my CatchBoundary and ErrorBoundary placed at root.ts

Hi,
I've tried to use useTranslation inside my CatchBoundary and ErrorBoundary placed at my root.ts so I could translate some of the text messages, but I can't. What would be the best strategy to use translations inside my boundaries in root.ts and in some other routes?
Thanks in advance

For boundaries inside root it's not possible right now, maybe there could be some hacky way, but I'm not aware.
For boundaries in other routes, load their translations in the root or another parent route and it should work.

Thanks a lot for your answer. Closing.


version GLIBCXX_3.4.21 not defined in file libstdc++.so.6

Hi,
This might be due to me being a noob, but I've installed from latest .deb package and I'm unable to start arkclient; when I try to do so from terminal, it outputs this:
$ arkclient
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /tmp/.org.chromium.Chromium.B43Fvq: symbol _ZTVNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEE, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:173:20)
    at Object.Module._extensions..node (module.js:598:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:187:18)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/opt/ArkClient/resources/app.asar/node_modules/node-hid/nodehid.js:9:15)
    at Object.<anonymous> (/opt/ArkClient/resources/app.asar/node_modules/node-hid/nodehid.js:109:3)

My system:
$ cat /etc/*-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=17.3
DISTRIB_CODENAME=rosa
DISTRIB_DESCRIPTION="Linux Mint 17.3 Rosa"
NAME="Ubuntu"
VERSION="14.04.5 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.5 LTS"
VERSION_ID="14.04"

Take a look here: https://github.com/typora/typora-issues/issues/504
Hope it helps you!

I gave it a read but I don't know what to do instead of this:
sudo cp node_modules/spellchecker/build/Release/spellchecker.node  /usr/share/typora/resources/app/node_modules/spellchecker/build/Release/

It seems that your error comes from Chromium so try reinstalling it.

Still nothing :(

No idea then, sorry.

@rpolve have you tried the solutions from https://askubuntu.com/questions/777803/apt-relocation-error-version-glibcxx-3-4-21-not-defined-in-file-libstdc-so-6#792471 ?

Yes, I've tried now, but it didn't help (actually they broke apt-get, I spent the last half hour fixing it -- now it seems ok).

@rpolve Could you try the Linux version that isn't a deb package (https://github.com/ArkEcosystem/ark-desktop/releases)?

Yes, I tried, but still no luck; I've installed it on a different machine though, so that's it for now.
However I thank you all for trying to help me :)


Add GEE task checker funciton(s) to make sure that all tasks successfully completed.

This arose out of PR #24.
Because we can send tasks to GEE and that is considered 'success' on our end, we also need to know if all the tasks completed successfully or not. As outlined in the PR, this is a multistep process:

wait some amount of time for all tasks to be completed
check the status of all the tasks to see what (if anything) failed
create an output of failed tasks
create a quick vis for the run_targets.Rmd readme to show how many tasks completed successfully or not.

completed in template repo


Invalidated link in "Prerequisites"

The link for setting up a Windows development environment is invalid.
P.s. the title "Prerequistes" misses its "i". ;)

Should be set - thank you, RRoodselaar!


False alert in AWS::EC2::LaunchTemplate

When I created a LaunchTemplate I saw and error in TagSpecifications with the Cloudformation Linter, but when I run the template in cloudformation works fine
LtXXXXXX:
Type: AWS::EC2::LaunchTemplate
Properties:
LaunchTemplateName: LtXXXXXX
LaunchTemplateData:
DisableApiTermination: true
ImageId: !Ref LtXXXXXXAmi
InstanceType: !Ref InstanceType
KeyName: !Ref KeyPair
TagSpecifications:
- ResourceType: instance
Tags:
- Key: Name
Value: XXXXXX

What version of cfn-lint are you using and what error are you getting?
This template is not giving me any errors.  The formatting is a little lost in yours so not sure if I have it set correctly.
LtXXXXXX:
    Type: AWS::EC2::LaunchTemplate
    Properties:
      LaunchTemplateName: LtXXXXXX
      LaunchTemplateData:
        DisableApiTermination: true
        ImageId: !Ref LtXXXXXXAmi
        InstanceType: !Ref InstanceType
        KeyName: !Ref KeyPair
      TagSpecifications:
        - ResourceType: instance
          Tags:
            - Key: Name
              Value: XXXXXX


[BUG]: global option

Version
The version you are currently using
OS
macOS
Describe the bug
vfox use java@21 --global

执行后没有报错，只是当前会话生效
必须使用下面这个才可以
vfox use --global java@21

Screenshots[optional]
If applicable, add screenshots to help explain your problem.

感谢反馈!
vfox使用的是urfave/cli库,  这个是库的问题.  只能命令后面紧接着跟flag才能生效.

urfave/cli support this feature on v3.0
https://github.com/urfave/cli/pull/1568

urfave/cli support this feature on v3.0
urfave/cli#1568
just add a property to the flag to make it work

Wow, I'll fix this later. 👍

Oh damn, we are currently using v2, and it seems like a lot of things need to be changed when upgrading to v3 which it's still alpha.
So I suggest that we wait until v3 is released before fixing this issue.


bug fix chucking

Hi @pc365, thanks a million for your pull-request. This has already been fixed. Are you using an old branch?
Greetings Damien


oracle-manager-update-arbitrum-mainnet

Hey @dbeal-eth if you can please check out the error in the build once possible, thank you


ENH: Change DollarVolume to AverageDollarVolume.

@ssanderson Made one minor comment, but otherwise looks good to me


Surface mining usecase notebook

Proposed changes
Addition of surface mining notebook to notebooks repository. Note that some cells have output cleared to enable the notebook to be saved.
Checklist (replace [ ] with [x] to check off)

[X] Remove any unused Python packages from Load packages
[X] Remove any unused/empty code cells
[X] Remove any guidance cells (e.g. General advice)
[X] Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended).
[X] Include relevant tags in the final notebook cell and re-use tags if possible
[X] Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated

@caitlinadams I've noted you said "some cells have output cleared to enable the notebook to be saved", I managed to run/save/upload the full notebook but should I not have?
I also added the /results folder which was causing the plot_possible_mining function to fail.
@nanaboamah89 you have the final review and approval


Reformat with black

Coverage remained the same at 82.471% when pulling 0461e747ba1eeb57ef7203b953cad3f5b6ef79b4 on iksaif:black into 243351f04ad166d54bd836595449afe9ce6add00 on criteo:master.


The base URL in the metron.json config file needs to be configurable by outside systems/libraries

Could just override the global variable in the app code when needed.