Only CPU and Memory values are shown

Are there plans to show GPU Data as well?

Same issue, tried reinstalling and didn't work

"Shows the basic PC hardware parameters (CPU and GPU temperature, CPU, GPU and memory load, CPU power consumption, etc.) using data provided by Libre Hardware Monitor application."
I assume its not working as I have the same issue

I checked out the repo and made some changes locally, for me it works now. Is there any way I can get these changes up here?

I checked out the repo and made some changes locally, for me it works now. I opened a pull request: #3

That's great, but I don't understand, any help? Thanks.

@notadoctor99 needs to merge the pull request and release a new version of the plugin for it to work. I can't merge it myself as I don't have the rights.

Hi, has this been fixed? The plugin is super handy but seeing the GPU would be awesome!

the developer says it supports gpu but it doesn't work for anyone and he doesn't care to solve it either

:(

@bdux Any chance you can post your DLL somewhere?  =)
@notadoctor99 Please merge and fix this.  Why make this and not support it?

@notadoctor99 please! Can you solve this problem?

Please merge the PR or open the repo for other maintainers!

What's the etiquette or legal implication of recreating this repo since it appears to be no longer be maintained?
Just curious if those of us looking for the improved functionality have a better option.

https://github.com/notadoctor99/librehardwaremonitorplugin/blob/master/LICENSE

Hi @notadoctor99 , if you are currently not able to update the plugin, it's ok, but please just tell us. It's a little frustrating to hear/read nothing.

Plugin File - Add GPU Gauge & GPU Sensor

I cannot believe you all were able to get this done. Thanks a lot. Really appreciated

Hi @notadoctor99 , if you are currently not able to update the plugin, it's ok, but please just tell us. It's a little frustrating to hear/read nothing.

Plugin File v2 - Add GPU Gauge & GPU Sensor

Thanks for building this! Just in case there is a chance for further improvements, here are some things I found:

The new gauges do not work for me, they show "sensor not available", only the CPU gauges work.
The sensor values work, so I could add the percentage of GPU load and VRAM load that way
The labels for the different sensors are hard to understand and differentiate, but that is an LHM issue I believe
The font and graphics on the gauges are clear and look nice
The font on the sensor values is very pixelated. I would use the gauges instead, but see above

LibreHardwareMonitor-v3.zip
CPUTemp -> CPUCCD
CPUHotS -> CPUCore
fix for ryzen 9800x3d

Hi @notadoctor99 , if you are currently not able to update the plugin, it's ok, but please just tell us. It's a little frustrating to hear/read nothing.

Plugin File v2 - Add GPU Gauge & GPU Sensor

Thanks for building this! Just in case there is a chance for further improvements, here are some things I found:

The font and graphics on the gauges are clear and look nice

Most gauges show "sensor not available" even though the values can be seen in LHM;

in detail:

CPU works

CPUPow not

CPUTemp not

GPU not

GPU Pow not

GPUTemp works

Memory works

The sensor values work, so I can add the percentage of GPU load and VRAM load that way

The font on the sensor values is very pixelated. I would use the gauges instead, but see above

The labels for the different sensors are hard to differentiate: e.g. GPU Load and VRAM both only show GPU above the percentage - see image. While the name can be edited in LHM and the plugin mirrors those changes, the label of the display seems to be hard-coded

please give me your LibreHardwareMonitor.Report.txt

LibreHardwareMonitor.Report.txt

LibreHardwareMonitor-v3.zip CPUTemp -> CPUCCD CPUHotS -> CPUCore fix for ryzen 9800x3d

This is great, thank you so much! :) I was getting worried that my GPU was running too hot, until I realized that the loupedeck was displaying hotspot temperatures.
Nice to have/request: Would it be possible to have the option to display the gauge with the same visuals as the initial plugin?
 vs.

I also tried the new plugin, it showed my gpu, and after a PC restart it no longer showed, only "sensor not available" Apart from this, the cpu package temp is incorrect. Libre monitor is running loupedeck software is running

I also tried the new plugin, it showed my gpu, and after a PC restart it no longer showed, only "sensor not available" Apart from this, the cpu package temp is incorrect. Libre monitor is running loupedeck software is running

please upload your LibreHardwareMonitor.Report.txt

I also tried the new plugin, it showed my gpu, and after a PC restart it no longer showed, only "sensor not available" Apart from this, the cpu package temp is incorrect. Libre monitor is running loupedeck software is running

please upload your LibreHardwareMonitor.Report.txt

How do I do this? Sorry I don't get it.

I also tried the new plugin, it showed my gpu, and after a PC restart it no longer showed, only "sensor not available" Apart from this, the cpu package temp is incorrect. Libre monitor is running loupedeck software is running

please upload your LibreHardwareMonitor.Report.txt

you can find it in this link:
https://mab.to/t/r7ALkGoORHn/eu1

I also tried the new plugin, it showed my gpu, and after a PC restart it no longer showed, only "sensor not available" Apart from this, the cpu package temp is incorrect. Libre monitor is running loupedeck software is running

please upload your LibreHardwareMonitor.Report.txt

you can find it in this link:
https://mab.to/t/r7ALkGoORHn/eu1

There is another issue to be aware of: With V6.0.2 the Loupedeck Software enhanced the settings for buttons. Now font and font-size can be changed, and at first it seems, the text itself could as well. So I tried changing the GPU-labels in order to make more clear, which value is shown. But with whatever change in that dialog is made to a dynamic button, it becomes static. So no more %-values according to the actual data, but only the last value fixed is saved. I have found no way to reset these buttons, even after uninstalling, clearing all plugin data and reinstalling. With 6.0.3 the issue persists. I have made Loupedeck aware of the issue by email. This is a bug in the Loupedeck-software, not an issue of the plugin, as it seems, but nevertheless a heads up.

There is another issue to be aware of: With V6.0.2 the Loupedeck Software enhanced the settings for buttons. Now font and font-size can be changed, and at first it seems, the text itself could as well. So I tried changing the GPU-labels in order to make more clear, which value is shown. But with whatever change in that dialog is made to a dynamic button, it becomes static. So no more %-values according to the actual data, but only the last value fixed is saved. I have found no way to reset these buttons, even after uninstalling, clearing all plugin data and reinstalling. With 6.0.3 the issue persists. I have made Loupedeck aware of the issue by email. This is a bug in the Loupedeck-software, not an issue of the plugin, as it seems, but nevertheless a heads up.

I have version 5.8.

The CPU temperature is now displayed after a few restarts.
The CPU temperature in "gauges" does not want to be displayed.
It displays absolutely everything from the gpu in "gauges", from the cpu "gauges" it displays only the load cpu

The CPU temperature is now displayed after a few restarts. The CPU temperature in "gauges" does not want to be displayed -sensor not available. It displays absolutely everything from the gpu in "gauges", from the cpu "gauges" it displays only the load cpu

add intel cpu
LibreHardwareMonitor.zip
| +- Core Average : 48.6429 42.2857 69.2857 (/intelcpu/0/temperature/1)
Core Average -> Core
| +- CPU Package 1 : 73 45 95 (/intelcpu/0/temperature/16)
CPU Package 1 -> CCD

LibreHardwareMonitor.Report.txt

fix for LibreHardwareMonitor-0.9.2. latest version is v0.9.4.
LibreHardwareMonitor.zip
CPUPOW
|  +- CPU Power      :  56.4669  22.2387  147.914 (/intelcpu/0/power/0)
CPUCORE
|  +- Core Average   :       38    29.75    55.75 (/intelcpu/0/temperature/18)
CPUCCD
|  +- CPU Temperature :       40       32       60 (/intelcpu/0/temperature/8)
GPU
|  +- GPU Load       :    9.711    0.877   13.381 (/gpu-nvidia/0/load/4)
GPUPOW
|  +- GPU Power      :   27.634    2.651   38.277 (/gpu-nvidia/0/power/0)

LibreHardwareMonitor.Report.txt

fix for LibreHardwareMonitor-0.9.2. latest version is v0.9.4.
add intel 11th cpu
LibreHardwareMonitor.zip
CPUPOW
|  +- CPU Power      :  56.4669  22.2387  147.914 (/intelcpu/0/power/0)
CPUCORE
|  +- Core Average   :       38    29.75    55.75 (/intelcpu/0/temperature/18)
CPUCCD
|  +- CPU Temperature :       40       32       60 (/intelcpu/0/temperature/8)
GPU
|  +- GPU Load       :    9.711    0.877   13.381 (/gpu-nvidia/0/load/4)
GPUPOW
|  +- GPU Power      :   27.634    2.651   38.277 (/gpu-nvidia/0/power/0)

I see that you sent me another plugin here with a different look. Thank you! I have the one in the attached picture, it works ok except for CPU temp from gauges and the other CPU parameters from gauges, but for me it was important: CPU temp and load (load works)

LibreHardwareMonitor.Report.txt

fix for LibreHardwareMonitor-0.9.2. latest version is v0.9.4.
add intel 11th cpu
LibreHardwareMonitor.zip
CPUPOW
|  +- CPU Power      :  56.4669  22.2387  147.914 (/intelcpu/0/power/0)
CPUCORE
|  +- Core Average   :       38    29.75    55.75 (/intelcpu/0/temperature/18)
CPUCCD
|  +- CPU Temperature :       40       32       60 (/intelcpu/0/temperature/8)
GPU
|  +- GPU Load       :    9.711    0.877   13.381 (/gpu-nvidia/0/load/4)
GPUPOW
|  +- GPU Power      :   27.634    2.651   38.277 (/gpu-nvidia/0/power/0)

I see that you sent me another plugin here with a different look. Thank you! I have the one in the attached picture, it works ok except for CPU temp from gauges and the other CPU parameters from gauges, but for me it was important: CPU temp and load (load works)

The item name has changed, so you need to register it again.

With the latest plugin version and LHM 0.9.4 more gauges work for me. VRAM as a gauge is missing completely, though.

With the latest plugin version and LHM 0.9.4 more gauges work for me. VRAM as a gauge is missing completely, though.

I didn't add the VRAM gauge from the beginning because I don't use it.

With the latest plugin version and LHM 0.9.4 more gauges work for me. VRAM as a gauge is missing completely, though.

LibreHardwareMonitor.zip

|  +- GPU Memory     :  8.73659  5.01773  13.6713 (/gpu-nvidia/0/load/3)

Thank you! :) For my personal use case now everything works perfectly!

LibreHardwareMonitor.Report.txt

fix for LibreHardwareMonitor-0.9.2. latest version is v0.9.4.

add intel 11th cpu

LibreHardwareMonitor.zip

CPUPOW

|  +- CPU Power      :  56.4669  22.2387  147.914 (/intelcpu/0/power/0)

CPUCORE

|  +- Core Average   :       38    29.75    55.75 (/intelcpu/0/temperature/18)

CPUCCD

|  +- CPU Temperature :       40       32       60 (/intelcpu/0/temperature/8)

GPU

|  +- GPU Load       :    9.711    0.877   13.381 (/gpu-nvidia/0/load/4)

GPUPOW

|  +- GPU Power      :   27.634    2.651   38.277 (/gpu-nvidia/0/power/0)

I see that you sent me another plugin here with a different look. Thank you! I have the one in the attached picture, it works ok except for CPU temp from gauges and the other CPU parameters from gauges, but for me it was important: CPU temp and load (load works)

The item name has changed, so you need to register it again.

But in this new plugin, is the processor temperature the one from ‘package CPU temp’?

LibreHardwareMonitor.Report.txt

fix for LibreHardwareMonitor-0.9.2. latest version is v0.9.4.

add intel 11th cpu

LibreHardwareMonitor.zip

CPUPOW

|  +- CPU Power      :  56.4669  22.2387  147.914 (/intelcpu/0/power/0)

CPUCORE

|  +- Core Average   :       38    29.75    55.75 (/intelcpu/0/temperature/18)

CPUCCD

|  +- CPU Temperature :       40       32       60 (/intelcpu/0/temperature/8)

GPU

|  +- GPU Load       :    9.711    0.877   13.381 (/gpu-nvidia/0/load/4)

GPUPOW

|  +- GPU Power      :   27.634    2.651   38.277 (/gpu-nvidia/0/power/0)

I see that you sent me another plugin here with a different look. Thank you! I have the one in the attached picture, it works ok except for CPU temp from gauges and the other CPU parameters from gauges, but for me it was important: CPU temp and load (load works)

The item name has changed, so you need to register it again.

But in this new plugin, is the processor temperature gauge the one from ‘package CPU temp’?
Thank you! Thank you very much for your help and the work you’ve put in!

CPUCORE
| +- Core Average : 48.6429 42.2857 69.2857 (/intelcpu/0/temperature/1)
CPUCCD
| +- CPU Package 1 : 73 45 95 (/intelcpu/0/temperature/16)

LibreHardwareMonitor.zip

I just realized there may be a mix-up. There are percentage values for GPUMemory and VRAM used. In the last version, it shows GPUMemory as the value, and it is labelled as VRAM inside the button. I am not sure, what the difference is, but what I need (from experience) is the actual value of VRAM used, not GPUMemory. I preferred the visual gauges when they were different in style, btw., but either variant is fine if functional.

I just realized there may be a mix-up. There are percentage values for GPUMemory and VRAM used. In the last version, it shows GPUMemory as the value, and it is labelled as VRAM inside the button. I am not sure, what the difference is, but what I need (from experience) is the actual value of VRAM used, not GPUMemory. I preferred the visual gauges when they were different in style, btw., but either variant is fine if functional.
add gpu smalldata

LibreHardwareMonitor.zip

add fan & control

Uploading LibreHardwareMonitor.zip…

Since you quoted me, I presume my issue was supposed to be addressed?
I don't think, it is:

The gauge labelled VRAM still shows GPUMemory. The latter is always around 20% for me, I am not even sure, what it measures. VRAM used shows values between 5% and 100% depending on the actual usage, like when offloading an LLM-Modell into the VRAM.

Since you quoted me, I presume my issue was supposed to be addressed? I don't think, it is:  The gauge labelled VRAM still shows GPUMemory. The latter is always around 20% for me, I am not even sure, what it measures. VRAM used shows values between 5% and 100% depending on the actual usage, like when offloading an LLM-Modell into the VRAM.

Sensors

displayed with one decimal place

Uploading LibreHardwareMonitor.zip…

Since you quoted me, I presume my issue was supposed to be addressed? I don't think, it is:  The gauge labelled VRAM still shows GPUMemory. The latter is always around 20% for me, I am not even sure, what it measures. VRAM used shows values between 5% and 100% depending on the actual usage, like when offloading an LLM-Modell into the VRAM.

LibreHardwareMonitor.zip

Guages > VRAM

That is the "GPU Memory used" under "data" in MB, which corresponds to the GPU Memory %-value under "load" (in my case 25% load, 4000 (of 16000)MB used. So it is the same value, just in MB, that I can't really make sense of.
As a gauge corresponding to the Memory/RAM used, it would be the first %-value under load. I might have renamed it at some point, but it should be the first value under load within the GPU section. (See my screenshot above)

That is the "GPU Memory used" under "data" in MB, which corresponds to the GPU Memory %-value under "load" (in my case 25% load, 4000 (of 16000)MB used. So it is the same value, just in MB, that I can't really make sense of.
As a gauge corresponding to the Memory/RAM used, it would be the first %-value under load. I might have renamed it at some point, but it should be the first value under load within the GPU section. (See my screenshot above)

add Guages > CPUMonitor, GPUMonitor

LibreHardwareMonitor.zip


Replace confirmed-date with issued-date

Follow-up from https://github.com/metanorma/metanorma-ieee/issues/88

From https://github.com/metanorma/metanorma-ieee/issues/88:

The "Date approved: " value should be the issued-date, not the confirmed-date


Incorrect sensor detection on two test cameras

<IP_ADDRESS># ./ipc_chip_info
Chip: HiSilicon 3516cv300
Sensor: Sony IMX323

<IP_ADDRESS># ./ipc_chip_info
Chip: HiSilicon 3516cv300
Sensor: Sony IMX323

cat /proc/umap/sys on both shows ar0237 type but Sofia detects as SC2235:
[DEBUG]: mirror=0
[DEBUG]: Flip=0
[DEBUG]: ~~~~~~~~~~SC2235_init  JJ ~~~~~~~~~
[DEBUG]: Denoise level:  Day[3]      Night[3]
[DEBUG]: Denoise level:  Day[3]      Night[3]
[DEBUG]: IR: 65

Checked once again (this time both cameras are on OpenIPC firmware) and it's confirmed that the real sensor name is IMX323:
sensors:
- vendor: Sony
  model: IMX323
  control:
    bus: 0
    type: i2c
    addr: 0x34
  data:
    type: DC
  clock: 27MHz

I have the same issue:
`# cat /proc/umap/sys
[SYS] Version: [Hi3516CV300_MPP_V<IP_ADDRESS> B050 Release], Build Time[Jun  3 2018, 21:42:04]
-----MODULE PARAM---------------------------------------------------------------
vi_vpss_online  en_online_delayint  sensor0   sensor1  mem_total
0                   0ar0237_i2c_dc        NA        64`
# ipcinfo --long-sensor imx323_i2c


Validate nested fields

Summary
This PR closes #467, picks up where #1675 left off. This fix works for both list and object widgets field and fields Validations.

Deploy preview for netlify-cms-www ready!
Built with commit 37f1751bb106903eb48d263ac40854e321b142aa
https://deploy-preview-1873--netlify-cms-www.netlify.com

Deploy preview for cms-demo ready!
Built with commit b0aa64f8cefc730bb00ba407bdf80ffd51f51743
https://deploy-preview-1873--cms-demo.netlify.com

@barthc great work!! Good solution, too - offloading nested validation to the widgets is probably our best approach at the moment.
I'd feel more confident with merging if some tests were added - can you get some in place that help describe the new behavior?

@erquhart some tests as requested.

As I've noted on a few other larger PRs, we're going to hold this while we're implementing tests across the repo to ensure against breaks. Thanks for adding tests, that will definitely help!


Missing npm install tips in "To get started" message

When choosing to run npm commands manually, the message doesn't tell user to run npm install
# Project initialization finished!
# ========================

To get started:

  cd vue-test
  npm run lint -- --fix
  npm run dev

npm install is missing in the get started steps.
BTW, last commits are great :+1:

Oh, thought I had tested that thoroughly enough. Will take a look, thanks.

BTW, last commits are great

Thanks :)

@Toilal Try this branch:
vue init webpack#fix_complete_msg_1157

It's OK. for yarn, you can omit run keyword. (yarn lint --fix)

Will change that.


Count Selected Text Attribute

Added trivial realization of 'count-selected-text' attribute to be shown, when selected-text-format presents.

Would you please show me a demo for this feature?
According to the document of Bootstrap-select . This feature is for define the format of displayed text for toggle button when selectedTextFormat attribute is count>x or count. But your commit seems simply add the count-selected-text attribute into the button.
This wouldn't help for format the text.
In fact, there are a way to customize the format for selected-text-format.
See http://nya.io/nya-bootstrap-select/#!/api/nya-bs-config-provider

When modifying the provider in config method, it'd be applied globally across all the nya-bs-select elements. But in some cases it may be required to set particularly text for each element while keeping all other to behave as expected.
As an example I don't need to now the number of selected elements, some custom text is required when all elements are selected, e.g.

{{items.length-1}}" multiple>

{{item}}

I think use data-binding in select-text-format attribute will fail. Your `count>{{items.length-1}} won't work.
But your commit doesnt' make the feature fully functional as it described in Bootstrap-select. It just provide a text for, and will confuse the user who ever used the Bootstrap-select.


Unable to install through composer

Laravel 5.4

Hello, could you detail what is happening to you?
Can you attach any log or screenshot?

Also, an example of a DSN would be very welcome :)

Hola WrongWay,
According to the picture above, please add this code to your composer.json after "config" section:
"minimum-stability": "dev", "prefer-stable": true

Still doesn't work

Hola @WrongWay,
Hmm, that's weird.
This is my composer.json, can you post your composer.json screenshot?

How about the DSN, is it work?

@rizaldywirawan it works fine now, thanks for the help :) But I also encountered another problem with the encoding. Instead of Cédric I get C?dric. Any way to fix this ?

Hola @WrongWay,
Can you post a picture about that? Haven't heard about that before.
Just a note here, do you uncomment extension=php_pdo_odbc.dll at php.ini file? You will face error in the future if you haven't uncomment it.

@rizaldywirawan this is a problem with the ODBC connection itself, not the display (I have utf8 set everywhere). I don't know how to set the encoding of the database and/or the connection. I don't even know which encoding is used in the Access database.

Hola @WrongWay,
Aw, sorry about that.
Did you succeed to show data from database?
I guess, the only one who can answer this is @zoilomora.

@rizaldywirawan yes, I uncommented the extension and the connection works well (except the encoding, of course). Looks like I will need to export everything as CSV to get proper encoding :(

Hola @WrongWay,
Aw, sorry to hear that, i hope you will get the solution soon, of course without export to CSV.

@rizaldywirawan for a one-time export/import csv is not a problem for a small database. Although it would be a lot better to use this package for that :)

Hola @WrongWay,
I agree with you, straight to the db is the best option, at least for me :p.
I guess your main problem (install this package) already solved, how about close this issues?

@rizaldywirawan yeah, sure. Thanks for help :)

Hola @WrongWay,
You're welcome, success for your project ;), and i hope @zoilomora will find and way to fix the encoding problem.

Hello, I have been indisposed this weekend, sorry for the absence.
Thank you very much @rizaldywirawan for your great help.
@WrongWay I'm sorry that this package did not work for you. Could you send me an example database where it happens to you to analyze the problem?

@zoilomora Hi, the package works fine, I can select anything from the database, but there is a problem with the diacritics being converted to question marks. The text in the database is french. Laravel is all set up to use UTF-8.

@WrongWay I will write it down in the TODO file to take it into account for the next version. ;)

test.zip
Here are some string examples.


Add fix for supporting offline models

A small fix so offline local models can also be used as otherwise cocolm defaults to downloading from huggingface . This is useful for kaggle competitions as an example

Thanks. I've merged the change.


Text size on table cells

When upgrading to a newer version I can no longer find a way to set the size of the text inside a table.
This is the code that was previously working:
row := table.AddRow()
row.AddCell().AddParagraph("").AddText("1").Size(tableTextSize)
row.AddCell().AddParagraph("").AddText("2").Size(tableTextSize)
row.AddCell().AddParagraph("").AddText("3").Size(tableTextSize)
row.AddCell().AddParagraph("").AddText("4").Size(tableTextSize)
row.AddCell().AddParagraph("").AddText("5").Size(tableTextSize)

I tried to set the size property in other ways but did not find a way.
thx for the library btw very useful

The public API get broken when i restructured to get style prop for para.


Webpack Error while loading assets

Hi,
I made a fresh clone of your repo to give it a try. However I have the following error while running npm run server:dev
ERROR in ./assets/atlases/preload_sprites_array.png Module parse failed: e:\MyFolder\assets\atlases\preload_sprites_array.png Unexpected character '�' (1:0) You may need an appropriate loader to handle this file type. (Source code omitted for this binary file)  @ ./src/assets.ts 30:65-116  @ ./src/states/boot.ts  @ ./src/app.ts  @ multi (webpack)-dev-server/client?http://localhost:9000 ./src/app.ts
My node version is v6.9.5 and I'm using windows 7
Any idea ?

Hi, sorry you're having an issue.
I'm going to assume it's due to some incompatibility between at least one of the modules/plugins and node 6.9.5, I developed with 7.5.0 and after downgrading to 6.9.5 I see the same issue...
I'll can take a look tonight and see what I can do.

Thanks,
I have been browsing the web for similar issues but I didn't find anything  ...
My guess was something around file-loader ...

This will load assets
{ test: /\.(jpg|png|xml|mp3|ogg|m4a|fnt|ac3)$/, loader: 'file-loader?name=assets/[hash].[ext]' },
but example breaks with:
ncaught TypeError: url.match is not a function     at Phaser.Loader.transformUrl (game.js:72307)     at Phaser.Loader.fileComplete (game.js:72934)     at HTMLImageElement.file.data.onload (game.js:72452)

It's a Windows thing.
change the file-loader test from /assets\//
to /assets\\/
Now it works.

Awesome. Thanks @ProfitWarning and @lejeremy. I haven't had a chance to look at it the last couple days like I thought. I'll get that change in.

Now working like a charm. Thank you guys !


Upgrade dependencies

Coverage remained the same at 100.0% when pulling 290faeca3e13ec43bc98f4f825cbe4b5cea33644 on dependencies into f797cd3c4dcb9765e59a2c01a14a4be254d280dd on master.


Remove default attributes ['config']['owner'] and ['config']['group']

These attributes are redundant in the default.rb attribute file because they cause
a confusion about how the default values of consul_config's owner and group params are actually determined.
Due to Poise inversion options, the node's attribute will always have a precedence.
They are designed to be used by cookbook end-users in their wrapper cookbooks.
We already have default values defined in the resource itself:
https://github.com/johnbellone/consul-cookbook/blob/eebc1299cefb6d766218904ea372566cc84bf373/libraries/consul_config.rb#L21-L26
Default values of ['service_owner'] and ['service_group'] are "consul" too, so we can
remove  ['config']['owner'] and ['config']['group'] without any effect.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@eebc129). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #446   +/-   ##
=========================================
  Coverage          ?   55.15%
=========================================
  Files             ?        7
  Lines             ?      359
  Branches          ?        0
=========================================
  Hits              ?      198
  Misses            ?      161
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eebc129...dfe2945. Read the comment docs.


Cloud-init package installation cause  error 100

Hi, i know that 100 is mostly safe failure and send run will go ok, but i think it is necessary to implement check if apt/apt-get/yum whatever is currently running or cloud-init completely finished its tasks and only then start what hetzner_kube want to do.
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

This error just means, that apt already running and doing its dirty hacks, also cloud-init writing output log where pretty simple catch that all tasks finished or at least execution finished regardless succeed or failed.

according to docs from cloud-init we can hook on /var/lib/cloud/instance/boot-finished
I did fast check and this file touched with some info only when cloud-init finished its tasks:
cat /var/lib/cloud/instance/boot-finished
159.53 - Sun, 10 Feb 2019 18:46:03 +0000 - v. 18.4-0ubuntu1~18.04.1

I;ll try to do PR with simple check, because otherwise this tool hard to use in case you need to run something with cloud-init.


BUG - Position Cache

When you change the position of the node, the cache is not updated, there are data that were cached when initializing

diagram.js
this.cola.on('end', () => {
      this.save_position(group, node, link, data, pop);
    });

saving every time you drag a node

So are you interested in an option to save positions after moving nodes?
Even if we had the option, your team would see an initial diagram because the modified position cache was stored only in your browser. Is it operationally acceptable?

in my decision the problem is not completely solved. therefore even the problem remains.

@codeout  when i drag the node, chang its position, then refresh page. the node will out of the group bound sometimes, or not same as the position of refreshing page before.  @evgarik Did you have the same problem, and how did you fix it? thanks a lot..

I also save graph postion like this :
this.cola.on('end', () => {    this.save_position(group, node, link, data, pop); });

Hi MGTfang. Thank you for the report.
I can introduce an experimental option for you (positionCache: "fixed" for example) to do this:

inet-henge automatically calculates a layout if there is no position cache
If there is a position cache, inet-henge loads it and doesn't move any more
inet-henge flushes the cache when any change is detected on json data

But the position cache will be stored in your browser. It won't be shared with others.
Is it actually acceptable in you case ? I'd thought that it would be a problem sometimes because the same json can render totally different layout.

@codeout thank you for your replay. In my case, sometimes need to beautify the layout(changes its position). so i offer a public method to save graph positions to database and save it by external method call, not as before saving every time when drag node.  i found when problem happened i drag a node little bit, graph will render, it will be ok. so i make cola tick once during duration time at end of render function:
const duration = 2 // tick duration time
d3.timer(function (elapsed) {
  // re-calculate the layout.
  // invoke tick() once
  self.cola.start()
  self.ticksForward(1)
  // Terminate the timer
  // when the desired duration has elapsed
  return elapsed >= duration
})

Could you try origin/save-positions branch when you have time?
git fetch
git checkout origin/save-positions

and update your html like this:
--- a/example/index.html
+++ b/example/index.html
@@ -13,7 +13,7 @@
   </body>

   <script>
-   var diagram = new Diagram('#diagram', 'index.json', {pop: /^([^\s-]+)-/, bundle: true});
+   var diagram = new Diagram('#diagram', 'index.json', {pop: /^([^\s-]+)-/, bundle: true, positionCache: 'fixed'});
    diagram.init('loopback', 'interface');
   </script>
 </html>

This branch includes positionCache: 'fixed' option to save every time when dragging nodes, and some other fixes.

i offer a public method to save graph positions to database

It sounds great, but not easy for now because of scope of variables. We can easily call save_position() within render() method but not out of there. So I implemented the option above this time.
I hope the branch helps you.

@codeout
Follow your advice and try, it works!
Set experimental option can make position saved when dragging node.
You are so kind, thank you very much!!

Did you update example/shownet.html ?
It works in my environment.
--- a/example/shownet.html
+++ b/example/shownet.html
@@ -14,7 +14,7 @@

   <script>
    var distance = function(force) { force.jaccardLinkLengths(100, 0.2); }
-   var diagram = new Diagram('#diagram', 'shownet.json', {pop: /^([^\s-]+)-/, distance: distance});
+   var diagram = new Diagram('#diagram', 'shownet.json', {pop: /^([^\s-]+)-/, distance: distance, positionCache: 'fixed'});
    diagram.init('interface');
   </script>
 </html>

Yes, Its my mistake， because of not make example/shownet.html updated.
It perfect works now.  ：） ：）

Thanks for your testing. I will be merging the branch into master.


[TACHYON-1284] make security socket timeout configurable.

as the title.

Can one of the admins verify this patch?

I don't think your commit is associated with your github account. Could you follow the instructions here: https://help.github.com/articles/setting-your-email-in-git/
Thanks!

Thanks @csliu I left a few comments.

Jenkis, test this please

addressed review comments.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6779/
Test PASSed.

fix another review and pass local full test.

@gpang updated the email setting, let me know if there still any issue.

+1 LGTM

ok to test

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/6786/
Test PASSed.

there seems still email issue. I will close this and redo it in another pr.


Ignore if sub belongs to user during existence check

While working on #897, I noticed that subExists additionally checks if the territory belongs to the user. The only reference to this function that I found was in territorySchema and subSelectSchemaMembers. This means it gets only called in the territory and post forms.
This might be a relict of 10203f565c6305df36d4189a6e42671f9521761c and is actually no longer needed. At least I can't tell why it should be. I think we used to redirect users to the territory if it already existed? But at least now, it simply throws an error after payment using JIT invoices.
So I propose to remove this check.

Ah I found why this is there. With this change territory founders can't edit their territory.

I fixed it in 1385a51e.
I also noticed that the previous logic failed if you tried to enter the name for another territory you own. Then validation was successful on the client (since it ignored all territories that you own) but then hit the unique name constraint on the server.


chore: generate CHANGELOG during release

It would be nice to have some kind of changelog generated during a release, either as a markdown file or in the release notes.

Closed with https://github.com/biosustain/potion-node/commit/6fb5101845a5cd770cd3af8d9c26920f05bc68d2.


Unirest in Wordpress plugin development

I have a client who needs something that I think Unirest would work fantastic - I haven't been able to get Unirest to work on a Wordpress install - is this because the HTTP headers can't be modified once Wordpress is instantiated, am I on the right track?

@whiteb0x @ssx this has been open for well over a year, please re-open if you have further issues.


feat: support custom api names and operation names

The following OpenAPI extensions are supported to define api names and operation names:

x-sap-cloud-sdk-api-name
x-sap-cloud-sdk-operation-name

api name logic
x-sap-cloud-sdk-api-name exists?

Y. Use it.
N. tags exists?

Y. Use tags.
N. Use defaultApi

operation name logic
x-sap-cloud-sdk-operation-name exists?

Y. Use it.
N. operationId exists?

Y. Use operationId.
N. Generate operation name by using path and method.

I will get involved once @marikaner changes are included and discussed and we have already some convergence.


Remove meter color-awareness information from P4Info

There doesn't seem to be any point in keeping this in P4Info at the
moment. First the semantics are murky because in PSA each execute call
on a meter is either color-aware or color-blind (i.e. it is not an
attribute of the meter object itself). Second, at the moment this
information cannot be leveraged in any way by a P4 client since
P4Runtime does not expose any knob to enable / disable color-awareness
on a per meter entry basis at runtime. Even if there was such a knob, it
would be hard to reconciliate it with PSA semantics: in PSA the same
meter can be "executed" in 2 different actions, in color-aware mode in
one and in color-blind mode in the other; these 2 action can use the
same indirect meter entry.
Fixes #58

@ccascone this fixes an inconsistency between P4Runtime & PSA that you pointed out a while back


Grid-like artifact detection is run on the 4x4 downsampled ssim map.

When the grid-like artifact detection is run for the first time, its input is not the full-sized ssim map of the image, as the comment on line 305 would suggest, but the 4x4 downsampled ssim map. The downsampling happens in line 293, in-place, for the purpose of computing the worst-ssim-block, and it is not changed after that.
Is this the expected behavior? If yes, perhaps there could be a comment explaining the reason behind it. Note that in the second iteration, the edgediff map is the same size as the full image.

Good catch! This is indeed not the intended behavior, and we should get a better grid-like artifact detection if we fix this. Might need to recalibrate worst_grid_weight after this is fixed.
Thanks for noticing this!


Multiple conformer generation

When generating structures from SMILES (or INCHI, when supported) - by default we only generate a single conformer, but should an an option to build a trajectory with multiple conformers.
Will also need easy mechanisms for

creating a new molecule object from a specific frame of animation, and
applying a trajectory frame to a pre-existing molecule object

Closing as not done for now - will reopen if necessary


⚠ Bofrost.fr has degraded performance

In 10dea61, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1079 ms

Resolved: Bofrost.fr performance has improved in 3fc7984 after 8 minutes.


Activate a script?

How do I activate a script when a response is selected?

Press the third bubble on the response to open a script editor. That script will run when the response is selected.


Display App version in footer

In order to identify the deployed the version of the app in the specific environment, let's display the application version/tag on footer.

In Test and Prod the version is displayed in regular version notation:

In Dev it is displayed as a deploy Tag from the Repository:


Allow only persisted queries to be executed

Is your feature request related to a problem? Please describe.
While writing documentation for persisted queries (#3616) it came up that there is currently no good way of allowing only persisted queries to be executed.
Describe the solution you'd like
There should be a new option in the server configuration users can set to refuse any "dynamic" queries and only execute requests which contain a query id:
app.UseEndpoints(endpoints =>
{
    endpoints.MapGraphQL().WithOptions(new GraphQLServerOptions
    {
        AllowOnlyPersistedRequests = true
    });
});

AllowOnlyPersistedRequests is of course just an idea and nothing final.

Could this option be changed dynamically, for example if it was based on the ClaimsPrincipal? Or would you just implement that more manually, with middleware or something?


[CI][Issue 1424][gfx900/906] Skip test_bn_3d_spatial_test

As per Issue #1424
This test is not stable in CI, but consistenly cannot be reproduced by local dev system.
Skip to allow CI tests to pass, only impact legacy systems

@JehandadKhan  and @shurale-nkn : I am still monitoring CI stability, this PR could be on hold for now.


Fix to KeyError for tables without TableType

Description
I got an KeyError exception during dbt-athena run.
In rare cases, such as tables not migrated to the AWS Glue Data Catalog, Get Tables API returns TableList without TableType attribute.
So I suggest ignoring such tables in this PR.
Another option is assuming it is EXTERNAL_TABLE.
However, since we don’t know detail of tables without TableType attribute, I think any assumption shouldn’t be appropriate.
Here is a stacktrace of KeyError on dbt-core==1.3.1 dbt-athena-community==1.3.2:
22:44:30  Encountered an error: 'TableType'
22:44:30  Traceback (most recent call last):
  File "/project/.venv/lib/python3.9/site-packages/dbt/main.py", line 135, in main
    results, succeeded = handle_and_check(args)
...
...
  File "/project/.venv/lib/python3.9/site-packages/dbt/utils.py", line 480, in connected
    return func(*args, **kwargs)
  File "/project/.venv/lib/python3.9/site-packages/dbt/adapters/athena/impl.py", line 254, in list_relations_without_caching
    _type = table["TableType"]
KeyError: 'TableType'

Models used to test - Optional

Checklist

[x] You followed contributing section
[x] You added unit testing when necessary
[ ] You added functional testing when necessary

@t-yuki Could you verify that this solution works when table type is ICEBERG?

@t-yuki Could you verify that this solution works when table type is ICEBERG or if in general we don't have breaking changes.

I've checked Glue API response and dbt run command works well with this PR.
Glue API response for iceberg table has 'EXTERNAL_TABLE' TableType attribute like:
{
  "TableList": {
    ...
    "TableType": "EXTERNAL_TABLE",
    "Parameters": {
        "metadata_location": "s3://my-bucket/metadata/00000-0a57eaa2-5c95-4229-90cd-097153b46b6d.metadata.json",
        "table_type": "ICEBERG"
    }
  }
}

So this PR doesn't break functions for iceberg table.

We are also experiencing this error and need this fix released :)


Colordict dictionary

This app contain ads and non free proprietary (gms) also this app is depending on gms how you can say they respecting user privacy? 🗿🤦

By that I mean it doesn't depend on web service to function, dictionaries are files sit in your phone, no server would know what words you are looking up. As for ads, ColorDict has not been updated for years, it's ads link is quite easy to, might already been, blocked by common ad blocker. GMS? I use it in a ROM with no GMS  and it runs perfectly fine.
Of couse, you have every single right to challenge me on this statement. And I feel sorry if you found yourself being cheated. However, no matter what, it's your choice to use it or drop it.

By that I mean it doesn't depend on web service to function, dictionaries are files sit in your phone, no server would know what words you are looking up. As for ads, ColorDict has not been updated for years, it's ads link is quite easy to, might already been, blocked by common ad blocker. GMS? I use it in a ROM with no GMS and it runs perfectly fine.
Of couse, you have every single right to challenge me on this statement. And I feel sorry if you found yourself being cheated. However, no matter what, it's your choice to use it or drop it.

why you recommend non free proprietary software inside setter app? There is one foss app that i know but idk can fully replace google translate or not:
https://f-droid.org/packages/com.sbeve.jada
You can replace those recommendation if you want to ^_°

App not found.

App not found.

Huh f droid are getting weird and worst at the same time i found this app from f droid app but not found on their website???? 🥴🥴🥴🥴
Yeah me have same experience 🤦🤦🤦🤦🤦🤦🤦

@NSTAdventure

Huh f droid are getting weird and worst at the same time i found this app from f droid app but not found on their website????

not available on the official f-droid repo yet
found it on izzy repo https://apt.izzysoft.de/fdroid/index/apk/com.sbeve.jada

@NSTAdventure

Huh f droid are getting weird and worst at the same time i found this app from f droid app but not found on their website????

not available on the official f-droid repo yet
found it on izzy repo https://apt.izzysoft.de/fdroid/index/apk/com.sbeve.jada

hmm? 😳
Did i add repo without i am realizing it? 😳
Uh okay....

one of the main the reason i choose colordict is offline feature. online api can track your look up history no matter how free and open they sound. i believe it's much more worst than ad.

one of the main the reason i choose colordict is offline feature. online api can track your look up history no matter how free and open they sound. i believe it's much more worst than ad

Uh maybe other FOSS dictionary? That are just a example :-/

yes. offline dictionary is the key feature requirement, another better to have is the popup window mode, which save the hassle of app switching. i make this app mainly for my own use, what i try to do is to mimic the working environment of desktop

if i remember right, i think it work with Aard 2 out of the box.

@NSTAdventure

Huh f droid are getting weird and worst at the same time i found this app from f droid app but not found on their website????

not available on the official f-droid repo yet
found it on izzy repo https://apt.izzysoft.de/fdroid/index/apk/com.sbeve.jada

Official source repo @ https://github.com/sbeve72/JADA

Is there really no decent libre English dictionary that works offline?

There are some, but none of them provide an Intent which other apps like Setter can call.

@scubajeff Sounds like a good feature request to make for those apps, then.


fix e2e

Integration tests must be data agnostic (ie if a test needs data it has to create it before using it and delete it after using it)

Disable non data agnostics e2e tests

Changes Unknown when pulling 96736fbe527d10a5bbe69ca7ca43ea865b7a0673 on acr/fix-e2e into ** on zenika-dev**.


metering-code-refactored

Can one of the admins verify this patch?

ok to test

retest this please


Add Black badge + some cleanup

Just some organizing.
@ashjbarnes, what does regional_model_scripts.py includes? What's the difference from the mom6-regiona.py?

I'm not sure it makes sense to move that into the library. Probably better to just delete it, we can excavate it from history if ever needed.

Oh, you said the magic word!

The only reason the legacy mom6_regional_scripts.py is still there is I've not incorporated the Regrid Runoff step. Perhaps we could delete it for now, and then alter the data table in the default rundirs so they're not expecting runoff at all? Make a note that runoff will / might be included at some point

@ashjbarnes, feel free to alter the data table in the default run directory in this PR?

@ashjbarnes shall I merge and you deal w runoff in a different PR?

Oh good point - I think we should deal with it now because otherwise the demo notebooks won't work after merging.
How do I modify within the PR?

Ok I'm going to draw this one out a bit to make sure that on merging the demo notebooks work. I'll remove the runoff from the runs, modify notebook accordingly, and ensure that the demo still produces a runnable mom6 configuration

Yeah, do that!

I moved the black badge to a different PR; see #36

@ashjbarnes I'll let you merge this PR as soon as you have tested that the demo notebook run or whenever you are happy.

Thanks Navid! I'm happy with this now. The demo notebooks could do with some more (or better thought out) markdown but they work fine for now. I'll save this for a future PR


Add most-redis-docker example.

I think it's hard to provide an example that is easy to run and is also somewhat close to a "real world" scenario.  By allowing users to run this example by installing docker or installing redis, I hope to make it a bit easier.
I'm very open to suggestions and improvements:  coding style, README contents, variable names, etc.
Honestly, composing the most.js streams felt clunky without formal function composition tools.  Am I doing it right?  Could I do it better?

Sorry about the confusion wrt mostjs/examples repo vs mostjs/core examples dir.  I had kinda forgotten that both exist.  We need to figure out which one is canonical.

composing the most.js streams felt clunky without formal function composition tools

Yeah, it's not as simple as one would like.  Variadic left-to-right composition, like ramda's pipe, helps.  There's also the experimental @most/fluent.  In the type-to-search example, we used the proposed ES pipeline operator, which is fairly pleasant, but requires a compile step.

mostjs/examples repo vs mostjs/core examples dir

Quick note specifically on this: the team discussed via slack and we're going with the mostjs/core examples dir as canonical.  So, this PR is in the right spot 🎉

🎉 Thanks, everyone!

Thank you for this example @unscriptable !

Got any other ideas for server-side examples? 😄

I feel anything with web sockets would make a good example - if that sounds interesting to you 😄
Maybe we should make some more issues to track the examples move into this repo and discuss some possible example additions we could create.


v0.8.207 immediate exception on start up, 20.04, has not recurred

PharoDebug.log

Strange. For whatever reason, the scale factor was nil. Please reopen if you see it again.


Listing Rite Aid location that doesn’t exist on Rite Aid appointment site

A search for “10011” is yielding a listing for “Rite Aid - 501 6th Avenue, New York, NY, 10011” with appointments supposedly available. Yet, searching for “10011” on the Rite Aid site doesn’t yield any location at that address, not even one that has no appointment slots.

@avidrissman did some digging for you and unfortunately it looks like this might be an issue out of our hands.
I'm not an active contributor (yet) but it appears that the data comes in through an internal RiteAid API
https://github.com/GUI/covid-vaccine-spotter/blob/ef2007436a5d2ea26001aec1089b62a19eb9b0dd/src/providers/riteAid/appointments.js#L66
I grabbed the storename from @Lynne-Daniels comment (thank you!) and got the following
https://www.riteaid.com/services/ext/v2/vaccine/checkSlots?storeNumber=04261

I can only guess what slot 1&2 mean (I'm guessing dose one vs two), but it appears that they're reporting this store has vaccines. Hence the vaccine spotter is too.
Unfortunately not sure there's much we can do about this one :(
(P.S. Did some digging on the RiteAid side of things and when you search the zip 10011 on their site it doesn't even show you any locations, which there definitely are since if you add one and search 10012 you get 10 stores. So I'd imagine there's some weirdness in the 10011 twilight zone. Maybe just give the pharmacy a call and see if they're offering appointments)

It may be outside the scope of this project but if that "messing around in the console" is something we can package up (maybe as a bookmark) we could probably help people get more appointments

FYI we have more data. The appointments are real, but the reason the Rite Aid store isn’t listed is because it’s being closed in two weeks. All the remaining appointment slots are filled up, so I’m not sure any project to help people “mess around in the console” will be a good use of time.

To see if slots **may be ** available go to your browser and put in this url https://www.riteaid.com/services/ext/v2/vaccine/checkSlots?storeNumber=####
where #### is the store number you are interested in.
You will see either:
{"Data":{"slots":{"1":true,"2":false}},"Status":"SUCCESS","ErrCde":null,"ErrMsg":null,"ErrMsgDtl":null}
OR
{"Data":{"slots":{"1":false,"2":false}},"Status":"SUCCESS","ErrCde":null,"ErrMsg":null,"ErrMsgDtl":null}
OR
blank
if you get the first one with Data.slots[1] = true
then appointments may be available.
if you get either of the other two, appointments are **definitely not *** available and not waste your time going through the riteaid.com website process.
Of course, just write a script to poll this url to make life even easier.  Worked great for me!  I polled for three days then suddenly got the Data.slots[1]=true and went to the riateaid website....mission accomplished!

Closing this as fixed by https://github.com/GUI/covid-vaccine-spotter/commit/a5d064d7167298fd0d73a567dd996be2d0f3021d. Now that we refresh the store's locations, we should be reflecting what Rite Aid's own site says for appointments.


FromIterator for Vec

Is it possible to implement IntoIterator for Vec and maybe other?
It is needed for .collect().

IntoIterator<Item = &'a T> and IntoIterator<Item = &'a mut T> are already implemented for Vec<T, ..>. However it might indeed be useful to implement IntoIterator<Item = T> which would have move semantics while iterating over the vector. This would gradually move all elements out of the vector and could drop the underlaying buffer once the collection is empty.
The trait that needs to be implemented to allow the usage of .collect<heapless::Vec<T, ...>> is FromIterator. It is currently not implemented for Vec<T, ...>. It can however in general by unsafe to collect an iterator with arbitrary many items into an Vec, which has a fixed size, statically allocated buffer for storage. As a user of the collect method you would need to specify how large this buffer is. But since from_iter() does not return a result, we could panic! if the buffer runs full, or simply drop al extra items.

Yes, you are right. I mean FromIterator

closed in #38 and #39


Add new fuction

If I want to add some new function on the APP. The APP is a prototype design, and I want to add some new function on this APP. What I should do. Thanks.

Yes, I have completed a login part which is new function in this APP. We can use the login system to store music in the APP for future software development. I will test this part, if this part work well in my computer, I will create a pull request. Cheers.

That sounds fine to me. Open a PR if you decide to contribute your changes back to the project.
I'll close this issue since it doesn't seem to actually be an issue. :)


Edit UI for Homepage And Add Signup Signin Form #GSSOC24

Hi, I would like to work on this issue, please can you assign this to me.

Hello, I would like to work on this issue, could you please assign it to me.

Please provide labels also

Hello, I would like to work on this issue, could you please assign it to me

Hello, I would like to work on this issue, please assign me this task

Hello, I would like to work on this issue, please assign me this task as i have already done this type of work previously in my project .I have also a knowledge about UI/UX design

Hello, I would like to work on this issue, please assign me this task


[BUG] Weird Behaviour when replaying an ZED2 SVO in realtime

Describe the bug
A clear and concise description of what the bug is.
Device information:

OS: container based on Jetpack 4.4
CPU: Jetson Xavier NX
GPU Nvidia: Jetson Xavier NX
ZED SDK Version: 3.3.3 for Jetpack 4.4
ROS Wrapper version: latest master (678bb3b)

To Reproduce
Steps to reproduce the behavior:

Use the following parameters:/**:
  general:
    debug_mode: true
    sdk_verbose: true
    svo_file: path/to/svo_file
    svo_loop: false
    svo_realtime: true
    camera_model: zed2
    camera_name: zed2
    camera_flip: true
    resolution: 2
    self_calib: false
    grab_frame_rate: 30
    pub_frame_rate: 15.0
  video:
    img_downsample_factor: 0.5
  depth:
    quality: 1
    min_depth: 1.0
    max_depth: 10.0
    depth_downsample_factor: 0.5
    point_cloud_freq: 15.0
  pos_tracking:
    publish_tf: false
    publish_map_tf: false
    base_frame: base_link

Launch withros2 launch zed_wrapper zed2.launch.py

See the log below for when running on a Jetson Xavier NX. When I do the same on my personal laptop, the node initially publishes topics but stops publishing at random. The SVO file is still being replayed, though, as I was able to see from the SVO reached the end. The node has been stopped message in the logs. Note, when I change svo_realtime to True, everything works just fine.

Expected behavior
The node starts without camera error.
ROS log
[robot_state_publisher-1] Initialize urdf model from file: /workspaces/eloquent/install/zed_wrapper/share/zed_wrapper/urdf/zed2.urdf
[robot_state_publisher-1] Parsing robot urdf xml string.
[robot_state_publisher-1] Link zed2_camera_center had 2 children
[robot_state_publisher-1] Link zed2_left_camera_frame had 1 children
[robot_state_publisher-1] Link zed2_left_camera_optical_frame had 0 children
[robot_state_publisher-1] Link zed2_right_camera_frame had 1 children
[robot_state_publisher-1] Link zed2_right_camera_optical_frame had 0 children
[robot_state_publisher-1] got segment base_link
[robot_state_publisher-1] got segment zed2_camera_center
[robot_state_publisher-1] got segment zed2_left_camera_frame
[robot_state_publisher-1] got segment zed2_left_camera_optical_frame
[robot_state_publisher-1] got segment zed2_right_camera_frame
[robot_state_publisher-1] got segment zed2_right_camera_optical_frame
[robot_state_publisher-1] Adding fixed segment from base_link to zed2_camera_center
[robot_state_publisher-1] Adding fixed segment from zed2_camera_center to zed2_left_camera_frame
[robot_state_publisher-1] Adding fixed segment from zed2_left_camera_frame to zed2_left_camera_optical_frame
[robot_state_publisher-1] Adding fixed segment from zed2_camera_center to zed2_right_camera_frame
[robot_state_publisher-1] Adding fixed segment from zed2_right_camera_frame to zed2_right_camera_optical_frame
[zed_wrapper-2]<PHONE_NUMBER>.148992223 [zed24388529.zed_node] [INFO] ********************************
[zed_wrapper-2]<PHONE_NUMBER>.149339584 [zed24388529.zed_node] [INFO]       ZED Camera Component
[zed_wrapper-2]<PHONE_NUMBER>.149460801 [zed24388529.zed_node] [INFO] ********************************
[zed_wrapper-2]<PHONE_NUMBER>.149567649 [zed24388529.zed_node] [INFO]  * namespace: /zed24388529
[zed_wrapper-2]<PHONE_NUMBER>.149644513 [zed24388529.zed_node] [INFO]  * node name: zed_node
[zed_wrapper-2]<PHONE_NUMBER>.149700833 [zed24388529.zed_node] [INFO] ********************************
[zed_wrapper-2]<PHONE_NUMBER>.150225667 [zed24388529.zed_node] [INFO] *** Debug Mode enabled ***
[zed_wrapper-2]<PHONE_NUMBER>.150917317 [zed24388529.zed_node] [DEBUG] [ROS2] Using RMW_IMPLEMENTATION = rmw_cyclonedds_cpp
[zed_wrapper-2]<PHONE_NUMBER>.151105414 [zed24388529.zed_node] [INFO] *** GENERAL parameters ***
[zed_wrapper-2]<PHONE_NUMBER>.151439911 [zed24388529.zed_node] [INFO]  * Camera model: zed2 - ZED 2
[zed_wrapper-2]<PHONE_NUMBER>.151724551 [zed24388529.zed_node] [INFO]  * SDK Verbose: 1
[zed_wrapper-2]<PHONE_NUMBER>.151975432 [zed24388529.zed_node] [INFO]  * SVO: /workspaces/ssd/recording/ds20210409_sn24388529_ts052613.svo
[zed_wrapper-2]<PHONE_NUMBER>.152241193 [zed24388529.zed_node] [INFO]  * SVO Loop: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.152446058 [zed24388529.zed_node] [INFO]  * SVO Realtime: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.152643274 [zed24388529.zed_node] [INFO]  * Camera name: zed2
[zed_wrapper-2]<PHONE_NUMBER>.152902539 [zed24388529.zed_node] [INFO]  * Camera ID: 0
[zed_wrapper-2]<PHONE_NUMBER>.153110316 [zed24388529.zed_node] [INFO]  * Camera SN: 0
[zed_wrapper-2]<PHONE_NUMBER>.153302316 [zed24388529.zed_node] [INFO]  * Camera timeout [sec]: 5
[zed_wrapper-2]<PHONE_NUMBER>.153503597 [zed24388529.zed_node] [INFO]  * Camera reconnection temptatives: 5
[zed_wrapper-2]<PHONE_NUMBER>.153704173 [zed24388529.zed_node] [INFO]  * Camera framerate: 30
[zed_wrapper-2]<PHONE_NUMBER>.153912526 [zed24388529.zed_node] [INFO]  * GPU ID: -1
[zed_wrapper-2]<PHONE_NUMBER>.154190351 [zed24388529.zed_node] [INFO]  * Camera resolution: 2 - HD720
[zed_wrapper-2]<PHONE_NUMBER>.154393935 [zed24388529.zed_node] [INFO]  * Camera self calibration: FALSE
[zed_wrapper-2]<PHONE_NUMBER>.154624048 [zed24388529.zed_node] [INFO]  * Camera flip: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.154810193 [zed24388529.zed_node] [INFO]  * [DYN] Publish framerate [Hz]: 15
[zed_wrapper-2]<PHONE_NUMBER>.154898481 [zed24388529.zed_node] [INFO] *** VIDEO parameters ***
[zed_wrapper-2]<PHONE_NUMBER>.155074322 [zed24388529.zed_node] [INFO]  * Use old extrinsic parameters: 0
[zed_wrapper-2]<PHONE_NUMBER>.155255378 [zed24388529.zed_node] [INFO]  * [DYN] Image downsample factor: 0.5
[zed_wrapper-2]<PHONE_NUMBER>.155514323 [zed24388529.zed_node] [INFO]  * [DYN] Brightness: 4
[zed_wrapper-2]<PHONE_NUMBER>.155703315 [zed24388529.zed_node] [INFO]  * [DYN] Contrast: 4
[zed_wrapper-2]<PHONE_NUMBER>.155886388 [zed24388529.zed_node] [INFO]  * [DYN] Hue: 0
[zed_wrapper-2]<PHONE_NUMBER>.157565593 [zed24388529.zed_node] [INFO]  * [DYN] Saturation: 4
[zed_wrapper-2]<PHONE_NUMBER>.157825178 [zed24388529.zed_node] [INFO]  * [DYN] Sharpness: 4
[zed_wrapper-2]<PHONE_NUMBER>.158121051 [zed24388529.zed_node] [INFO]  * [DYN] Gamma: 8
[zed_wrapper-2]<PHONE_NUMBER>.158326043 [zed24388529.zed_node] [INFO]  * [DYN] Auto Exposure/Gain: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.158569084 [zed24388529.zed_node] [INFO]  * [DYN] Exposure: 80
[zed_wrapper-2]<PHONE_NUMBER>.158781757 [zed24388529.zed_node] [INFO]  * [DYN] Gain: 80
[zed_wrapper-2]<PHONE_NUMBER>.158982685 [zed24388529.zed_node] [INFO]  * [DYN] Auto White Balance: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.159200222 [zed24388529.zed_node] [INFO]  * [DYN] White Balance Temperature: 42
[zed_wrapper-2]<PHONE_NUMBER>.159403839 [zed24388529.zed_node] [INFO]  * Video QoS History: KEEP_LAST
[zed_wrapper-2]<PHONE_NUMBER>.159617311 [zed24388529.zed_node] [INFO]  * Video QoS History depth: 1
[zed_wrapper-2]<PHONE_NUMBER>.159810976 [zed24388529.zed_node] [INFO]  * Video QoS Reliability: RELIABLE
[zed_wrapper-2]<PHONE_NUMBER>.159989632 [zed24388529.zed_node] [INFO]  * Video QoS Durability: VOLATILE
[zed_wrapper-2]<PHONE_NUMBER>.160074689 [zed24388529.zed_node] [INFO] *** DEPTH parameters ***
[zed_wrapper-2]<PHONE_NUMBER>.160265409 [zed24388529.zed_node] [INFO]  * Depth downsample factor: 0.5
[zed_wrapper-2]<PHONE_NUMBER>.160481634 [zed24388529.zed_node] [INFO]  * Depth quality: 1 - PERFORMANCE
[zed_wrapper-2]<PHONE_NUMBER>.160699267 [zed24388529.zed_node] [INFO]  * Min depth [m]: 1
[zed_wrapper-2]<PHONE_NUMBER>.161513189 [zed24388529.zed_node] [INFO]  * Max depth [m]: 10
[zed_wrapper-2]<PHONE_NUMBER>.161732678 [zed24388529.zed_node] [INFO]  * Depth Sensing Mode: 0 - STANDARD
[zed_wrapper-2]<PHONE_NUMBER>.161907718 [zed24388529.zed_node] [INFO]  * Depth Stabilization: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.162087655 [zed24388529.zed_node] [INFO]  * OpenNI mode (16bit point cloud): FALSE
[zed_wrapper-2]<PHONE_NUMBER>.162598152 [zed24388529.zed_node] [INFO]  * [DYN] Point cloud rate [Hz]: 15
[zed_wrapper-2]<PHONE_NUMBER>.162899689 [zed24388529.zed_node] [INFO]  * [DYN] Depth Confidence: 50
[zed_wrapper-2]<PHONE_NUMBER>.163102090 [zed24388529.zed_node] [INFO]  * [DYN] Depth Texture Confidence: 100
[zed_wrapper-2]<PHONE_NUMBER>.163282250 [zed24388529.zed_node] [INFO]  * Depth QoS History: KEEP_LAST
[zed_wrapper-2]<PHONE_NUMBER>.163450123 [zed24388529.zed_node] [INFO]  * Depth QoS History depth: 1
[zed_wrapper-2]<PHONE_NUMBER>.163660364 [zed24388529.zed_node] [INFO]  * Depth QoS Reliability: RELIABLE
[zed_wrapper-2]<PHONE_NUMBER>.163837196 [zed24388529.zed_node] [INFO]  * Depth QoS Durability: VOLATILE
[zed_wrapper-2]<PHONE_NUMBER>.163907340 [zed24388529.zed_node] [INFO] *** POSITIONAL TRACKING parameters ***
[zed_wrapper-2]<PHONE_NUMBER>.164083501 [zed24388529.zed_node] [INFO]  * Base frame id: base_link
[zed_wrapper-2]<PHONE_NUMBER>.164272141 [zed24388529.zed_node] [INFO]  * Map frame id: map
[zed_wrapper-2]<PHONE_NUMBER>.164465838 [zed24388529.zed_node] [INFO]  * Odometry frame id: odom
[zed_wrapper-2]<PHONE_NUMBER>.164679055 [zed24388529.zed_node] [INFO]  * Broadcast Odometry TF: FALSE
[zed_wrapper-2]<PHONE_NUMBER>.164880815 [zed24388529.zed_node] [INFO]  * [DYN] Path publishing rate: 2
[zed_wrapper-2]<PHONE_NUMBER>.165063504 [zed24388529.zed_node] [INFO]  * Path history lenght: -1
[zed_wrapper-2]<PHONE_NUMBER>.165267184 [zed24388529.zed_node] [INFO]  * Initial pose: [0,0,0,0,0,0,]
[zed_wrapper-2]<PHONE_NUMBER>.165474193 [zed24388529.zed_node] [INFO]  * Area Memory: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.165667154 [zed24388529.zed_node] [INFO]  * Area Memory DB:
[zed_wrapper-2]<PHONE_NUMBER>.165846738 [zed24388529.zed_node] [INFO]  * IMU Fusion [not for ZED]: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.166071187 [zed24388529.zed_node] [INFO]  * Floor Alignment: FALSE
[zed_wrapper-2]<PHONE_NUMBER>.166250547 [zed24388529.zed_node] [INFO]  * Init Odometry with first valid pose data: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.166429684 [zed24388529.zed_node] [INFO]  * 2D mode: FALSE
[zed_wrapper-2]<PHONE_NUMBER>.166698517 [zed24388529.zed_node] [INFO]  * Pose/Odometry QoS History: KEEP_LAST
[zed_wrapper-2]<PHONE_NUMBER>.166867669 [zed24388529.zed_node] [INFO]  * Pose/Odometry QoS History depth: 1
[zed_wrapper-2]<PHONE_NUMBER>.167026486 [zed24388529.zed_node] [INFO]  * Pose/Odometry QoS Reliability: RELIABLE
[zed_wrapper-2]<PHONE_NUMBER>.167195830 [zed24388529.zed_node] [INFO]  * Pose/Odometry QoS Durability: VOLATILE
[zed_wrapper-2]<PHONE_NUMBER>.167287382 [zed24388529.zed_node] [INFO] *** SENSORS STACK parameters ***
[zed_wrapper-2]<PHONE_NUMBER>.168104633 [zed24388529.zed_node] [INFO]  * Sensors Camera Sync: FALSE
[zed_wrapper-2]<PHONE_NUMBER>.168321786 [zed24388529.zed_node] [INFO]  * Sensors publishing rate: 400 Hz
[zed_wrapper-2]<PHONE_NUMBER>.168508986 [zed24388529.zed_node] [INFO]  * Sensors QoS History: KEEP_LAST
[zed_wrapper-2]<PHONE_NUMBER>.168681979 [zed24388529.zed_node] [INFO]  * Sensors QoS History depth: 1
[zed_wrapper-2]<PHONE_NUMBER>.168866427 [zed24388529.zed_node] [INFO]  * Sensors QoS Reliability: RELIABLE
[zed_wrapper-2]<PHONE_NUMBER>.169041884 [zed24388529.zed_node] [INFO]  * Sensors QoS Durability: VOLATILE
[zed_wrapper-2]<PHONE_NUMBER>.169110716 [zed24388529.zed_node] [INFO] *** Spatial Mapping parameters ***
[zed_wrapper-2]<PHONE_NUMBER>.169286813 [zed24388529.zed_node] [INFO]  * Spatial Mapping Enabled: FALSE
[zed_wrapper-2]<PHONE_NUMBER>.169491357 [zed24388529.zed_node] [INFO]  * Spatial Mapping resolution [m]: 0.05
[zed_wrapper-2]<PHONE_NUMBER>.169687518 [zed24388529.zed_node] [INFO]  * 3D Max Mapping range [m]: 10
[zed_wrapper-2]<PHONE_NUMBER>.170536256 [zed24388529.zed_node] [INFO]  * Map publishing rate [Hz]: 1
[zed_wrapper-2]<PHONE_NUMBER>.170746593 [zed24388529.zed_node] [INFO]  * Sensors QoS History: KEEP_LAST
[zed_wrapper-2]<PHONE_NUMBER>.170938338 [zed24388529.zed_node] [INFO]  * Sensors QoS History depth: 1
[zed_wrapper-2]<PHONE_NUMBER>.171114562 [zed24388529.zed_node] [INFO]  * Sensors QoS Reliability: RELIABLE
[zed_wrapper-2]<PHONE_NUMBER>.171284899 [zed24388529.zed_node] [INFO]  * Sensors QoS Durability: VOLATILE
[zed_wrapper-2]<PHONE_NUMBER>.171363107 [zed24388529.zed_node] [INFO] *** OBJECT DETECTION parameters ***
[zed_wrapper-2]<PHONE_NUMBER>.171546787 [zed24388529.zed_node] [INFO]  * Object Detection enabled: FALSE
[zed_wrapper-2]<PHONE_NUMBER>.171739588 [zed24388529.zed_node] [INFO]  * OD min. confidence: 40
[zed_wrapper-2]<PHONE_NUMBER>.171943237 [zed24388529.zed_node] [INFO]  * Object Detection model: 0 - MULTI CLASS BOX
[zed_wrapper-2]<PHONE_NUMBER>.172127941 [zed24388529.zed_node] [INFO]  * MultiClassBox people: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.172308134 [zed24388529.zed_node] [INFO]  * MultiClassBox vehicles: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.172490278 [zed24388529.zed_node] [INFO]  * MultiClassBox bags: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.172683239 [zed24388529.zed_node] [INFO]  * MultiClassBox animals: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.172872583 [zed24388529.zed_node] [INFO]  * MultiClassBox electronics: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.173157064 [zed24388529.zed_node] [INFO]  * MultiClassBox fruits and vegetables: TRUE
[zed_wrapper-2]<PHONE_NUMBER>.173348297 [zed24388529.zed_node] [INFO]  * Skeleton fitting: FALSE
[zed_wrapper-2]<PHONE_NUMBER>.173523113 [zed24388529.zed_node] [INFO]  * Obj. Det. QoS History: KEEP_LAST
[zed_wrapper-2]<PHONE_NUMBER>.173744682 [zed24388529.zed_node] [INFO]  * Obj. Det. QoS History depth: 1
[zed_wrapper-2]<PHONE_NUMBER>.173953547 [zed24388529.zed_node] [INFO]  * Obj. Det. QoS Reliability: RELIABLE
[zed_wrapper-2]<PHONE_NUMBER>.174168011 [zed24388529.zed_node] [INFO]  * Obj. Det. QoS Durability: VOLATILE
[zed_wrapper-2]<PHONE_NUMBER>.174267468 [zed24388529.zed_node] [INFO] *** SERVICES ***
[zed_wrapper-2]<PHONE_NUMBER>.176047441 [zed24388529.zed_node] [INFO]  * '/zed24388529/zed_node/reset_odometry'
[zed_wrapper-2]<PHONE_NUMBER>.177686038 [zed24388529.zed_node] [INFO]  * '/zed24388529/zed_node/reset_pos_tracking'
[zed_wrapper-2]<PHONE_NUMBER>.180907776 [zed24388529.zed_node] [INFO]  * '/zed24388529/zed_node/set_pose'
[zed_wrapper-2]<PHONE_NUMBER>.181757250 [zed24388529.zed_node] [INFO]  * '/zed24388529/zed_node/enable_obj_det'
[zed_wrapper-2]<PHONE_NUMBER>.182249572 [zed24388529.zed_node] [INFO]  * '/zed24388529/zed_node/enable_mapping'
[zed_wrapper-2]<PHONE_NUMBER>.184054793 [zed24388529.zed_node] [INFO]  * '/zed24388529/zed_node/start_svo_rec'
[zed_wrapper-2]<PHONE_NUMBER>.184750059 [zed24388529.zed_node] [INFO]  * '/zed24388529/zed_node/stop_svo_rec'
[zed_wrapper-2]<PHONE_NUMBER>.185279309 [zed24388529.zed_node] [INFO]  * '/zed24388529/zed_node/toggle_svo_pause'
[zed_wrapper-2]<PHONE_NUMBER>.185401901 [zed24388529.zed_node] [INFO] ***** STARTING CAMERA *****
[zed_wrapper-2]<PHONE_NUMBER>.185475309 [zed24388529.zed_node] [INFO] SDK Version: 3.3.3 - Build 21849_cf84d4fa
[zed_wrapper-2]<PHONE_NUMBER>.196785872 [zed24388529.zed_node] [INFO] *** SVO OPENING ***
[zed_wrapper-2] Opening in BLOCKING MODE
[zed_wrapper-2] NvMMLiteOpen : Block : BlockType = 261
[zed_wrapper-2] NVMEDIA: Reading vendor.tegra.display-size : status: 6
[zed_wrapper-2] NvMMLiteBlockCreate : Block : BlockType = 261
[zed_wrapper-2] [ZED][Init] Depth mode: PERFORMANCE
[zed_wrapper-2] libv4l2_nvvidconv (0):(802) (INFO) : Allocating (11) OUTPUT PLANE BUFFERS Layout=1
[zed_wrapper-2] libv4l2_nvvidconv (0):(818) (INFO) : Allocating (11) CAPTURE PLANE BUFFERS Layout=0
[zed_wrapper-2] [ZED][Init] Self-calibration disabled
[zed_wrapper-2]<PHONE_NUMBER>.299870919 [zed24388529.zed_node] [DEBUG] Opening successfull
[zed_wrapper-2]<PHONE_NUMBER>.300253640 [zed24388529.zed_node] [INFO] ZED SDK running on GPU #0
[zed_wrapper-2]<PHONE_NUMBER>.300377256 [zed24388529.zed_node] [INFO]  * Camera Model      -> ZED 2
[zed_wrapper-2]<PHONE_NUMBER>.300454025 [zed24388529.zed_node] [INFO]  * Serial Number     -> 24388529
[zed_wrapper-2]<PHONE_NUMBER>.300578793 [zed24388529.zed_node] [INFO]  * Input type        -> SVO input type
[zed_wrapper-2]<PHONE_NUMBER>.300790058 [zed24388529.zed_node] [INFO]  * SVO resolution    -> 1280x720
[zed_wrapper-2]<PHONE_NUMBER>.300948490 [zed24388529.zed_node] [INFO]  * SVO framerate     -> 30
[zed_wrapper-2]<PHONE_NUMBER>.301085963 [zed24388529.zed_node] [DEBUG] Camera-IMU Transform:
[zed_wrapper-2]  55A7879C60
[zed_wrapper-2] 1.000000 0.000000 0.000000 0.000000
[zed_wrapper-2] 0.000000 1.000000 0.000000 0.000000
[zed_wrapper-2] 0.000000 0.000000 1.000000 0.000000
[zed_wrapper-2] 0.000000 0.000000 0.000000 1.000000
[zed_wrapper-2]
[zed_wrapper-2]<PHONE_NUMBER>.301172587 [zed24388529.zed_node] [DEBUG] Camera Frame size : 1280x720
[zed_wrapper-2]<PHONE_NUMBER>.301246763 [zed24388529.zed_node] [DEBUG] Image Mat size : 640x360
[zed_wrapper-2]<PHONE_NUMBER>.301350059 [zed24388529.zed_node] [DEBUG] Depth Mat size : 640x360
[zed_wrapper-2]<PHONE_NUMBER>.301600044 [zed24388529.zed_node] [INFO] *** TF FRAMES ***
[zed_wrapper-2]<PHONE_NUMBER>.301674252 [zed24388529.zed_node] [INFO]  * Map                       -> map
[zed_wrapper-2]<PHONE_NUMBER>.301745645 [zed24388529.zed_node] [INFO]  * Odometry                  -> odom
[zed_wrapper-2]<PHONE_NUMBER>.301796557 [zed24388529.zed_node] [INFO]  * Base                      -> base_link
[zed_wrapper-2]<PHONE_NUMBER>.301846093 [zed24388529.zed_node] [INFO]  * Camera                    -> zed2_camera_center
[zed_wrapper-2]<PHONE_NUMBER>.301897837 [zed24388529.zed_node] [INFO]  * Left                      -> zed2_left_camera_frame
[zed_wrapper-2]<PHONE_NUMBER>.301985517 [zed24388529.zed_node] [INFO]  * Left Optical              -> zed2_left_camera_optical_frame
[zed_wrapper-2]<PHONE_NUMBER>.302075694 [zed24388529.zed_node] [INFO]  * RGB                       -> zed2_left_camera_frame
[zed_wrapper-2]<PHONE_NUMBER>.302168078 [zed24388529.zed_node] [INFO]  * RGB Optical               -> zed2_left_camera_frame
[zed_wrapper-2]<PHONE_NUMBER>.302266798 [zed24388529.zed_node] [INFO]  * Right                     -> zed2_right_camera_frame
[zed_wrapper-2]<PHONE_NUMBER>.302322254 [zed24388529.zed_node] [INFO]  * Right Optical             -> zed2_right_camera_optical_frame
[zed_wrapper-2]<PHONE_NUMBER>.302373294 [zed24388529.zed_node] [INFO]  * Depth                     -> zed2_left_camera_frame
[zed_wrapper-2]<PHONE_NUMBER>.302424655 [zed24388529.zed_node] [INFO]  * Depth Optical             -> zed2_left_camera_optical_frame
[zed_wrapper-2]<PHONE_NUMBER>.302531407 [zed24388529.zed_node] [INFO]  * Point Cloud               -> zed2_left_camera_optical_frame
[zed_wrapper-2]<PHONE_NUMBER>.302588719 [zed24388529.zed_node] [INFO]  * Disparity         -> zed2_left_camera_frame
[zed_wrapper-2]<PHONE_NUMBER>.302646031 [zed24388529.zed_node] [INFO]  * Disparity Optical -> zed2_left_camera_optical_frame
[zed_wrapper-2]<PHONE_NUMBER>.302697199 [zed24388529.zed_node] [INFO]  * Confidence                -> zed2_left_camera_frame
[zed_wrapper-2]<PHONE_NUMBER>.302864944 [zed24388529.zed_node] [INFO]  * Confidence Optical        -> zed2_left_camera_optical_frame
[zed_wrapper-2]<PHONE_NUMBER>.302928240 [zed24388529.zed_node] [INFO]  * IMU                       -> zed2_imu_link
[zed_wrapper-2]<PHONE_NUMBER>.303032784 [zed24388529.zed_node] [INFO]  * Barometer         -> zed2_camera_center
[zed_wrapper-2]<PHONE_NUMBER>.303095409 [zed24388529.zed_node] [INFO]  * Magnetometer              -> zed2_imu_link
[zed_wrapper-2]<PHONE_NUMBER>.303161969 [zed24388529.zed_node] [INFO]  * Left Temperature          -> zed2_left_camera_frame
[zed_wrapper-2]<PHONE_NUMBER>.303236689 [zed24388529.zed_node] [INFO]  * Right Temperature -> zed2_right_camera_frame
[zed_wrapper-2]<PHONE_NUMBER>.304430133 [zed24388529.zed_node] [INFO] *** PUBLISHED TOPICS ***
[zed_wrapper-2]<PHONE_NUMBER>.308419201 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/rgb/image_rect_color
[zed_wrapper-2]<PHONE_NUMBER>.312610125 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/rgb/image_rect_color
[zed_wrapper-2]<PHONE_NUMBER>.312834766 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/rgb/image_rect_gray
[zed_wrapper-2]<PHONE_NUMBER>.313903761 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/rgb/image_rect_gray
[zed_wrapper-2]<PHONE_NUMBER>.314061298 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/rgb/camera_info
[zed_wrapper-2]<PHONE_NUMBER>.314251634 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/rgb_raw/image_raw_color
[zed_wrapper-2]<PHONE_NUMBER>.316396921 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/rgb_raw/image_raw_color
[zed_wrapper-2]<PHONE_NUMBER>.316659642 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/rgb_raw/image_raw_gray
[zed_wrapper-2]<PHONE_NUMBER>.317699101 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/rgb_raw/image_raw_gray
[zed_wrapper-2]<PHONE_NUMBER>.317792189 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/rgb_raw/camera_info
[zed_wrapper-2]<PHONE_NUMBER>.317939613 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/left/image_rect_color
[zed_wrapper-2]<PHONE_NUMBER>.318955873 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/left/image_rect_color
[zed_wrapper-2]<PHONE_NUMBER>.319102113 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/left/image_rect_gray
[zed_wrapper-2]<PHONE_NUMBER>.322751404 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/left/image_rect_gray
[zed_wrapper-2]<PHONE_NUMBER>.322991565 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/left/camera_info
[zed_wrapper-2]<PHONE_NUMBER>.323145325 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/left_raw/image_raw_color
[zed_wrapper-2]<PHONE_NUMBER>.324184080 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/left_raw/image_raw_color
[zed_wrapper-2]<PHONE_NUMBER>.324343921 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/left_raw/image_raw_gray
[zed_wrapper-2]<PHONE_NUMBER>.326366391 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/left_raw/image_raw_gray
[zed_wrapper-2]<PHONE_NUMBER>.326568216 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/left_raw/camera_info
[zed_wrapper-2]<PHONE_NUMBER>.326723192 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/right/image_rect_color
[zed_wrapper-2]<PHONE_NUMBER>.327696891 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/right/image_rect_color
[zed_wrapper-2]<PHONE_NUMBER>.327842203 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/right/image_rect_gray
[zed_wrapper-2]<PHONE_NUMBER>.328709438 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/right/image_rect_gray
[zed_wrapper-2]<PHONE_NUMBER>.328807486 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/right/camera_info
[zed_wrapper-2]<PHONE_NUMBER>.328913663 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/right_raw/image_raw_color
[zed_wrapper-2]<PHONE_NUMBER>.329860354 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/right_raw/image_raw_color
[zed_wrapper-2]<PHONE_NUMBER>.330021634 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/right_raw/image_raw_gray
[zed_wrapper-2]<PHONE_NUMBER>.331021253 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/right_raw/image_raw_gray
[zed_wrapper-2]<PHONE_NUMBER>.331124325 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/right_raw/camera_info
[zed_wrapper-2]<PHONE_NUMBER>.331292998 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/depth/depth_registered
[zed_wrapper-2]<PHONE_NUMBER>.332356585 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/depth/depth_registered
[zed_wrapper-2]<PHONE_NUMBER>.332474281 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/depth/camera_info
[zed_wrapper-2]<PHONE_NUMBER>.332589610 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/stereo/image_rect_color
[zed_wrapper-2]<PHONE_NUMBER>.333052363 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/stereo/image_rect_color
[zed_wrapper-2]<PHONE_NUMBER>.333163948 [zed24388529.zed_node] [DEBUG] getTopicToAdvertise: /zed24388529/zed_node/stereo_raw/image_raw_color
[zed_wrapper-2]<PHONE_NUMBER>.333612109 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/stereo_raw/image_raw_color
[zed_wrapper-2]<PHONE_NUMBER>.334049198 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/confidence/confidence_map
[zed_wrapper-2]<PHONE_NUMBER>.335707571 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/disparity/disparity_image
[zed_wrapper-2]<PHONE_NUMBER>.337702233 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/point_cloud/cloud_registered
[zed_wrapper-2]<PHONE_NUMBER>.339099453 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/pose
[zed_wrapper-2]<PHONE_NUMBER>.340114369 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/pose_with_covariance
[zed_wrapper-2]<PHONE_NUMBER>.342530184 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/odom
[zed_wrapper-2]<PHONE_NUMBER>.343433323 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/path_map
[zed_wrapper-2]<PHONE_NUMBER>.344353741 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/path_odom
[zed_wrapper-2]<PHONE_NUMBER>.345354864 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/imu/data
[zed_wrapper-2]<PHONE_NUMBER>.346147091 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/imu/data_raw
[zed_wrapper-2]<PHONE_NUMBER>.347230582 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/temperature/imu
[zed_wrapper-2]<PHONE_NUMBER>.347961816 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/imu/mag
[zed_wrapper-2]<PHONE_NUMBER>.348830011 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/atm_press
[zed_wrapper-2]<PHONE_NUMBER>.350619520 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/temperature/left
[zed_wrapper-2]<PHONE_NUMBER>.351304130 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/temperature/right
[zed_wrapper-2]<PHONE_NUMBER>.352423782 [zed24388529.zed_node] [INFO] Advertised on topic: /zed24388529/zed_node/left_cam_imu_transform [LATCHED]
[zed_wrapper-2]<PHONE_NUMBER>.352505094 [zed24388529.zed_node] [INFO] Camera-IMU Translation:
[zed_wrapper-2]  0 0 0
[zed_wrapper-2]<PHONE_NUMBER>.352617318 [zed24388529.zed_node] [INFO] Camera-IMU Rotation:
[zed_wrapper-2]  7FF68A1138
[zed_wrapper-2] 1.000000 0.000000 0.000000
[zed_wrapper-2] 0.000000 1.000000 0.000000
[zed_wrapper-2] 0.000000 0.000000 1.000000
[zed_wrapper-2]
[zed_wrapper-2]<PHONE_NUMBER>.352797063 [zed24388529.zed_node] [INFO] Published static TF: 'zed2_imu_link' -> 'zed2_left_camera_frame'
[zed_wrapper-2]<PHONE_NUMBER>.422183929 [zed24388529.zed_node] [DEBUG] Point Cloud thread started
[zed_wrapper-2]<PHONE_NUMBER>.422624250 [zed24388529.zed_node] [DEBUG] Grab thread started
[zed_wrapper-2]<PHONE_NUMBER>.433411675 [zed24388529.zed_node] [INFO] *** Starting Positional Tracking ***
[zed_wrapper-2]<PHONE_NUMBER>.433633691 [zed24388529.zed_node] [INFO]  * Waiting for valid static transformations...
[zed_wrapper-2]<PHONE_NUMBER>.433733596 [zed24388529.zed_node] [DEBUG] Getting static TF from 'zed2_left_camera_frame' to 'base_link'
[zed_wrapper-2]<PHONE_NUMBER>.433980732 [zed24388529.zed_node] [INFO] Static transform Sensor to Base [zed2_left_camera_frame -> base_link]
[zed_wrapper-2]<PHONE_NUMBER>.434067581 [zed24388529.zed_node] [INFO]  * Translation: {0.000,-0.060,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.434171517 [zed24388529.zed_node] [INFO]  * Rotation: {0.000,-0.000,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.434283709 [zed24388529.zed_node] [DEBUG] Getting static TF from 'zed2_left_camera_frame' to 'zed2_camera_center'
[zed_wrapper-2]<PHONE_NUMBER>.434531646 [zed24388529.zed_node] [INFO] Static transform Sensor to Camera Center [zed2_left_camera_frame -> zed2_camera_center]
[zed_wrapper-2]<PHONE_NUMBER>.434658078 [zed24388529.zed_node] [INFO]  * Translation: {0.000,-0.060,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.435311648 [zed24388529.zed_node] [INFO]  * Rotation: {0.000,-0.000,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.435883426 [zed24388529.zed_node] [DEBUG] Getting static TF from 'zed2_camera_center' to 'base_link'
[zed_wrapper-2]<PHONE_NUMBER>.435994050 [zed24388529.zed_node] [INFO] Static transform Camera Center to Base [zed2_camera_center -> base_link]
[zed_wrapper-2]<PHONE_NUMBER>.436051555 [zed24388529.zed_node] [INFO]  * Translation: {0.000,0.000,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.436111523 [zed24388529.zed_node] [INFO]  * Rotation: {0.000,-0.000,0.000}
[zed_wrapper-2]<PHONE_NUMBER>.488482977 [zed24388529.zed_node] [DEBUG] Video Depth callback called
[zed_wrapper-2]<PHONE_NUMBER>.536341938 [zed24388529.zed_node] [DEBUG] Time required to get valid static transforms: 0.002 sec
[zed_wrapper-2]<PHONE_NUMBER>.536644243 [zed24388529.zed_node] [INFO] Initial ZED left camera pose (ZED pos. tracking):
[zed_wrapper-2]<PHONE_NUMBER>.536779699 [zed24388529.zed_node] [INFO]  * T: [0,0.06,0]
[zed_wrapper-2]<PHONE_NUMBER>.536919668 [zed24388529.zed_node] [INFO]  * Q: [0,0,0,1]
[zed_wrapper-2]<PHONE_NUMBER>.915591036 [zed24388529.zed_node] [ERROR] Camera error: CAMERA NOT INITIALIZED
[zed_wrapper-2]<PHONE_NUMBER>.915790972 [zed24388529.zed_node] [DEBUG] Grab thread finished

Hi @kevinanschau
I'm sorry, but it's not clear when the error Camera error: CAMERA NOT INITIALIZED appears.
Can you explain better what happens on the Xavier NX and what happens instead on the laptop PC?

Hi @Myzhar
Sure. I previously recorded an SVO file with my ZED2 camera. Now I wanted to replay said SVO file with the zed_wrapper node on a Jetson Xavier NX. I set the general.svo_file to the SVO file path and also set the parameter general.svo_realtime to True because I wanted a replay in real-time. Unfortunately, this results in the Camera error: CAMERA NOT INITIALIZED.
On my laptop PC, though, when general.svo_realtime is True, the node starts without any error but stops publishing messages after some time (randomly).
In contrast, when I set general.svo_realtime to False, the node starts without any issues on both devices and replays the SVO till the end.


Improve spawn fail error message

Add some logs to address :

https://github.com/cta-epfl/flux-jh/issues/45

hm, 100% test failure rate! :)

Test were already failing on master.

Test were already failing on master. But I can make another PR to address those.

Indeed, let's do it separately https://github.com/cta-epfl/batchspawner/issues/22

Shall we merge this now ?


Fix package.json, Fix syslog formatting to use day-of-month instead of day-of-week

As it is, the syslog formatter uses d instead of D, which will log the day of the week instead of the day of the month, giving us nonsense like:
Aug 0 05:38:31 localhost node /var/www/project/index.js[5798]: severity=warn file=/var/www/project/file.js line=27 hostname=localhost userAgent="Mozilla/5.0 (X11; CrOS x86_64 8350.68.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36" message="test" data=null now=19630.170000000002 userTime=2016-08-27T22:39:01.440-07:00 state=null

I also updated package.json to use the proper path to the Bristol.js (this is currently broken in the master branch).

This can be closed, it was fixed in https://github.com/TomFrost/Bristol/pull/27

Is there a reason this PR was ignored and the other was accepted? I'd like to know so I can contribute better in the future. Thanks.

@slester I think Tom is just busy and missed it. There's nothing wrong with the PR IMO.

Apologies @slester! I was going top-down and didn't realize it was a duplicate, otherwise I'd have favored yours since it was first. I'm working on polishing up a 2.0-rc1 release for next week, so this will be in there.

It's OK! I just wanted to make sure that I did things in the proper way; we've been using my fork in production so it'll be nice to be able to switch back to 1.0 when it's fully vetted!


Result and exception handlers: names and signatures

Naming

handleResult/handleException
complete/unhandledException
resultHandler/exceptionHandler

Parameters
We could omit passing a continuation parameter to such handlers, because the coroutine can not be resumed any more. But it could be reset (#29)  or introspected (#28), so it may make sense to pass a Continuation<Nothing> to termination handlers.
Return types
Only Unit for now. If we find use cases for non-unit returns, we'll reconsider this.
Syntax
Should we have a special modifier for handlers?
handler fun handleResult(...) { ... }
handler fun handleException(...) { ... }

Or re-use operator?
operator fun handleResult(...) { ... }
operator fun handleException(...) { ... }

Should we allow non-Unit return type for handlers?
I can't see any bad consequences if we do, but at the same time I have no pragmatic use cases either

@dzharkov I'd prohibit them for now. If we find use cases for it, we'll lift this restriction

Closed. Obsolete.


same issue with msfs

im having same issue on hp reverb g2 MSFS wont launch into vr unless i disable the toolkit.i get a message that i dont have open xr installed.worked fine until i upgraded to 3080ti and did a clean windows 11 install
Originally posted by @mbucchia in https://github.com/mbucchia/OpenXR-Toolkit/issues/262#issuecomment-1068687724

Do you have EVGA software? Their software is breaking ours.
Try deleting file C:\Windows\system32\fw1fontwrapper.dll

The issue cause by EVGA is fixed in the 1.0.5 release that was just published. Please re-open if your issue persist.

Hi yes I have an evga 3080ti the only software I have is precision x1.my last card was an evga 2080ti and worked flawlessSent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Matthieu Bucchianeri @.> Date: 4/2/22  11:57 PM  (GMT-05:00) To: mbucchia/OpenXR-Toolkit @.> Cc: Rageinthecage77 @.>, Author @.> Subject: Re: [mbucchia/OpenXR-Toolkit] same issue with msfs  (Issue #294)
Do you have EVGA software? Their software is breaking ours.
Try deleting file C:\Windows\system32\fw1fontwrapper.dll
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I updated to the 1.05 release works perfectly now thank you so much been trying everything for days pulling my hair out before I found the forum thanks again....                                                        TimSent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Matthieu Bucchianeri @.> Date: 4/3/22  4:03 AM  (GMT-05:00) To: mbucchia/OpenXR-Toolkit @.> Cc: Rageinthecage77 @.>, Author @.> Subject: Re: [mbucchia/OpenXR-Toolkit] same issue with msfs  (Issue #294)
The issue cause by EVGA is fixed in the 1.0.5 release that was just published. Please re-open if your issue persist.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Data stewardship

Data stewardship is about keeping your data hosted on the Swarm network. For more detailed background see this issue.
In the context of the swarm-cli tool this would mean:

[x] be able to pin content when uploading
[x] pin in retrospect (https://github.com/ethersphere/swarm-cli/issues/59)
[x] pin feed update and upload (https://github.com/ethersphere/swarm-cli/issues/58)
[x] get the list of current pins (https://github.com/ethersphere/bee/issues/1302)
[ ] reupload to network (https://github.com/ethersphere/bee/issues/1051)
[ ] reupload pinned chunks (https://github.com/ethersphere/bee/issues/852)

I think the only missing thing from this list is to reupload pinned chunk. I imagine that it could work by having an option to the pinning reupload command to upload all the pinned content. For example:
swarm-cli pinning reupload -a
vs.
swarm-cli pinning reupload <address>
@Cafe137 What do you think?

@agazso Good idea, I am working on it.


For GTEA and BEOID

Hello, thanks for your excellent job. I am interested in your work so much!
May I ask if the extracted features on ActivityNet, GTEA and BEOID will be released？

Hello, thanks for your interest!
For the experiments on GTEA and BEOID, we utilized the features provided by SF-Net and you can find them here.
On the other hand, we extracted the features of ActivityNet videos by ourselves, but they are not supposed to be publicly available due to some internal issues.
As far as I know, there are several public repositories that provide the features for ActivityNet, and you may want to use them.

Hello, thanks for your interest! For the experiments on GTEA and BEOID, we utilized the features provided by SF-Net and you can find them here. On the other hand, we extracted the features of ActivityNet videos by ourselves, but they are not supposed to be publicly available due to some internal issues. As far as I know, there are several public repositories that provide the features for ActivityNet, and you may want to use them.

Thanks a lot!
Can you realease the code of dataset and data_loader class (like the thumos_features.py) for GTEA and BEOID?

Hello, thanks for your interest! For the experiments on GTEA and BEOID, we utilized the features provided by SF-Net and you can find them here. On the other hand, we extracted the features of ActivityNet videos by ourselves, but they are not supposed to be publicly available due to some internal issues. As far as I know, there are several public repositories that provide the features for ActivityNet, and you may want to use them.

Thanks a lot! Can you realease the code of dataset and data_loader class (like the thumos_features.py) for GTEA and BEOID?

Do you reproduce the result of GTEA and BEOID? Thank you.

@PHDJieFu Can you reproduce the result of GTEA and BEOID? I try but  there is a big gap between the results and the paper


JwtSecurityTokenHandler wrong message on exception

Just hit this today, there seems to be a bug with this line:
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/e4f8a0c3cd1d7d0e62a2e48be7bdc91a7fdddb24/src/System.IdentityModel.Tokens.Jwt/JwtSecurityTokenHandler.cs#L1437
Where it prints the object type instead of the actual message in the StringBuilder.
Microsoft.IdentityModel.Tokens.SecurityTokenInvalidSignatureException: IDX10503: Signature validation failed. Keys tried: 'System.Text.StringBuilder'.
Exceptions caught:
 'System.Text.StringBuilder'.
token: 'System.IdentityModel.Tokens.Jwt.JwtSecurityToken'.
   at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignature(String token, TokenValidationParameters validationParameters)
   at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, TokenValidationParameters validationParameters, SecurityToken& validatedToken)

The fix should be as simple as calling .ToString() before:
throw LogHelper.LogExceptionMessage(new SecurityTokenDecryptionFailedException(LogHelper.FormatInvariant(TokenLogMessages.IDX10603, keysAttempted.ToString(), exceptionStrings.ToString(), jwtToken.RawData)));

@theolivenbaum thanks for reporting this, sorry for the hassle.

It happens on expired tokens as well
IDX10223: Lifetime validation failed. The token is expired. ValidTo: 'System.DateTime', Current time: 'System.DateTime'
Any time frame on a fix?

I agree.  I am having the same issue too.

@AaronKoller @senylity @theolivenbaum this is currently marked for the next release, we have a planning on Monday and we will set a realistic date for the release.

@AaronKoller @senylity @theolivenbaum the issue here is that IdentityModelEventSource.ShowPII is false by default. In this case, we apply filtering sensitive items are filtered.
see: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/5810cd81dd3d7a802f111005f42990dc8ebb0aa7/src/Microsoft.IdentityModel.Logging/IdentityModelEventSource.cs#L303
We recognize the need to adjust this for an application that is running.
We have these issues that address this:
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/1274
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/1452
If you would like us to consider these in next months release, please put a mark on those issues.

It happens on expired tokens as well
IDX10223: Lifetime validation failed. The token is expired. ValidTo: 'System.DateTime', Current time: 'System.DateTime'
Any time frame on a fix?

FYI, I was able to work around this with:
Microsoft.IdentityModel.Logging.IdentityModelEventSource.ShowPII = true;
in the first line of ConfigureServices in my Startup.cs file.  I'm using .NET 5.

It happens on expired tokens as well
IDX10223: Lifetime validation failed. The token is expired. ValidTo: 'System.DateTime', Current time: 'System.DateTime'
Any time frame on a fix?

It happens on expired tokens as well
IDX10223: Lifetime validation failed. The token is expired. ValidTo: 'System.DateTime', Current time: 'System.DateTime'
Any time frame on a fix?

FYI, I was able to work around this with:
Microsoft.IdentityModel.Logging.IdentityModelEventSource.ShowPII = true;
in the first line of ConfigureServices in my Startup.cs file. I'm using .NET 5.

.Net 6
在 Program.cs 中 builder 声明之后添加 或者在配置 JWT 之后添加 均无效


Unable to link Homebrew's Cassandra to CCM

Hello there,
I've installed Cassandra using Homebrew. Everything's working fine, I can create keyspace, tables, I am able to run Spark on Cassandra and the like.
Since I've got another Macbook, I was trying to build a Cassandra cluster. So I've installed Cassandra on the other Macbook as well using Homebrew and I've installed ccm using Homebrew.
Ready for the "create" command, though using the -v flag installs Cassandra again, which I don't fancy. Using the "--install-dir" leads  nowhere since I'm experiencing errors of the form
"PATH HERE is not a valid cassandra directory. You must define a cassandra dir or version."
I've tried many paths, all starting from the Homebrew folder (which is "/usr/local/Cellar/cassandra/3.7") so I was wondering whether it is possible to declare Homebrew's Cassandra in Homebrew's CCM.
Kindest Regards

Hmm. I expect then, the issue is ccm not understanding the set up of the homebrew cassandra directory. I'm about to travel for Cassandra summit, so I won't be able to look into this until next week at the earlier.

So, I don't handle the homebrew bottle for ccm (I have no idea who does). To answer your direct question, I know of no way to declare Brew's C* in Brew's CCM. However, I can help you look into the install-dir option not working. Can you confirm which version of ccm you have installed, and give me the full command you are passing, that isn't working?

I'll continue this thread as I'm having similar issue. Here's the info requested:
ccm: stable 2.1.6 (bottled), HEAD
ccm create localDC --install-dir=/usr/local/Cellar/cassandra/3.7 -n 3 -s

I'll continue this thread as I'm having similar issue. Here's the info requested:
ccm: stable 2.1.6 (bottled), HEAD
ccm create localDC --install-dir=/usr/local/Cellar/cassandra/3.7 -n 3 -s

Is there a particular reason you can't do ccm create localDC -v 3.7 -n 3 -s instead?

Because I have a running standalone cassandra installation which I want to make a cluster out of.

That's not at all a designed-for use case of ccm