Deadlock while obtaining lock

Thread gets stuck while obtaining lock.
prio=5 os_prio=0 tid=0x00007fa1201d1000 nid=0x7f5a in Object.wait() [0x00007fa0bedd3000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at io.netty.util.concurrent.DefaultPromise.await(DefaultPromise.java:254)
- locked <0x00000006052c40b0> (a io.netty.util.concurrent.DefaultPromise)
at io.netty.util.concurrent.DefaultPromise.sync(DefaultPromise.java:218)
at io.netty.util.concurrent.DefaultPromise.sync(DefaultPromise.java:32)
at org.redisson.RedissonLock.lockInterruptibly(RedissonLock.java:112)
at org.redisson.RedissonLock.lock(RedissonLock.java:86)
The same lock name was likely concurrently obtained and held by another thread possibly on another jvm, and then released.
Observed intermittently.
Redisson Version used : 3.4.3

Is there any way to reproduce this?
Here is my concurrency test
https://github.com/redisson/redisson/blob/master/redisson/src/test/java/org/redisson/RedissonLockHeavyTest.java

Couldn't reproduce but observed the above situation when we got below exception, checked the memory utilization of reddis server, but memory utilization was normal.
org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [api] in context with path [] threw exception [Request processing failed; nested exception is org.redisson.client.RedisConnectionException: Can't aquire connection from pool! [[freeSubscribeConnectionsAmount=0, freeSubscribeConnectionsCounter=49, freeConnectionsAmount=239, freeConnectionsCounter=246, freezed=true, freezeReason=RECONNECT, client=x, nodeType=MASTER, failedAttempts=6]]] with root cause
org.redisson.client.RedisConnectionException: Can't aquire connection from pool! [[freeSubscribeConnectionsAmount=0, freeSubscribeConnectionsCounter=49, freeConnectionsAmount=239, freeConnectionsCounter=246, freezed=true, freezeReason=RECONNECT, client=x, nodeType=MASTER, failedAttempts=6]]
at org.redisson.misc.ConnectionPool.get(ConnectionPool.java:124)
at org.redisson.connection.MasterSlaveEntry.connectionWriteOp(MasterSlaveEntry.java:184)
at org.redisson.connection.MasterSlaveConnectionManager.connectionWriteOp(MasterSlaveConnectionManager.java:563)
at org.redisson.command.CommandAsyncService.async(CommandAsyncService.java:352)
at org.redisson.command.CommandAsyncService$5.run(CommandAsyncService.java:401)
at io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:581)
at io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:655)
at io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:367)
at java.lang.Thread.run(Thread.java:748)

Could you share your code with lock object usage?


Create a proper sfinv page and remove the dependency to sfinv_buttons

This way, the bags look better integrated in the default inventory and it is easier to use, since you don't need an additional dependency (sfinv is in the default game).
This PR also seperates the inventory logic into different files to keep the code more tidy.

Nice! I want to test this out.

Thanks!


ZALLY-113 Introduce PMD in CLI

Based on #119
Related to #113
🔋
Introduces PMD tool.
⚠ Please only check cb1f139 , needs to be rebased later.

Restarted builds after #118 got merged

👍


rbenv failed to install ruby 2.4.3

rbenv install 2.4.3
Downloading ruby-2.4.3.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.4/ruby-2.4.3.tar.bz2
error: failed to download ruby-2.4.3.tar.bz2
BUILD FAILED (Ubuntu 16.04 using ruby-build 20171215-2-g5481719)

The download failure is indicative of a network problem and not something we can help with. The download target itself exists:
$ curl -I https://cache.ruby-lang.org/pub/ruby/2.4/ruby-2.4.3.tar.bz2
HTTP/2 200


Not able to exectue cancellation transactions

We only allow to execute the most recent transaction. However, as we currently display cancellation transactions as seperate transaction, it's not possible to execute these. #304 will resolve this. But if #304 does not resolve this for cancellations made before the change or if it takes a lot more time to be implemented we need a hotfix for this.

We should only block from executing if the nonce of the transaction is not LAST EXECUTED NONCE +1. I think we currently do the check by transaction ID, which leads to this wrong behaviour.

After research it turned out that this is only applicable for cancelling transactions with nonce 0. The fix is very easy and included there: https://github.com/gnosis/safe-react/pull/432


JBEHAVE-1342 Set minimal required JDK to 1.8

The changes have been added to master branch: af740d589d82d4d5ca7887df5bfb0ece943d3e52


Consider merging and removing redundant text and spans when reading IMSC documents

https://github.com/sandflow/imscJS/blob/6039c0ab2fe89c4ae35332aa438441e3b06d580f/src/main/js/doc.js#L98

Closed by https://github.com/sandflow/ttconv/pull/138


Outline display is incomplete

Type: Bug
The following code recognizes that both opening parentheses are valid, causing the outline to fail to display the following functions.
....................................
#if defined(TEST)
{
#else
{
#endif
}
...................................
VS Code version: Code 1.73.1<PHONE_NUMBER>f055b99068d3688932416f2346dd3b, 2022-11-09T04:27:29.066Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info
|Screen Reader|no|
|VM|50%|
Extensions (20)

Extension
Author (truncated)
Version

rainbow-brackets
2gu
0.0.6

include-autocomplete
ajs
0.0.4

vscode-translate
chu
0.1.5

EnglishChineseDictionary
Cod
1.1.0

doxdocgen
csc
1.4.0

githistory
don
0.6.19

prettier-vscode
esb
9.9.0

vscode-drawio
hed
1.6.4

c-cpp-flylint
jbe
1.12.1

plantuml
jeb
2.17.4

better-cpp-syntax
jef
1.16.3

cmake-tools
ms-
1.12.27

cpptools
ms-
1.12.4

cpptools-extension-pack
ms-
1.3.0

code-settings-sync
Sha
3.4.3

markdown-preview-enhanced
shd
0.6.5

tabnine-vscode
Tab
3.6.23

cmake
twx
0.0.17

markdown-pdf
yza
1.4.4

linkerscript
Zix
1.0.2

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1:30587005
2e4cg342:30602488
gswce1:30612156
3d0df643:30613357
dbltrim-noruby:30604474
89544117:30613380

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!


During discovery, traverse links

Summary of the new feature / enhancement
Exe's published to the MSStore as msix packages have a link to the exe in PATH.  However, if they are resources, then their resource manifests won't be found as they are not actually in PATH.
Proposed technical implementation details (optional)
When an exe which is a link is found, dsc should traverse the link to the home of the exe to find a resource manifest.  Separately, some caching might make sense if this turns out to be too expensive.

Related issue #559 .


Puritan room version for extreme high latency and high reliability use cases

Suggestion
The room versions 1 through 7 all have various state reset vulnerabilities. I propose a room version, subtracting the features that cause authorisation reversals, hence stopping almost all the possible ways to achieve state resets:

The join rule will not be allowed to be made into more permissive (hence, in the progression of public-knock-invite-private, backwards transition will not be allowed)
No user will be allowed to gain more powers than it has at the time of first join (initial power levels on the invite event will still be allowed) or a previous power adjustment on the user
Kick=ban (if wanted, [join→leave]=[join→ban] could also be added to those constraints)

That room version would be useful in high latency use cases such as interplanetary and/or interstellar communication, and high reliability use cases where state resets are absolutely undesirable.

This is worded as a proposal but isn't a proposal. Closing in favour of discussion elsewhere as part of the pre-MSC recommend process.


refactor(starknet_api): gas vector to contain fields of type GasAmount

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1177
#1176  👈
#1175
#1174
#1173
#1172
main

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

Join @dorimedini-starkware and the rest of your teammates on  Graphite

Merge activity

Oct 9, 6:06 AM EDT: @dorimedini-starkware started a stack merge that includes this pull request via Graphite.


Build a career ladder for devrel engineer

Build a career ladder for devrel engineer. One very good example I may just have to adapt to Mindee is the one https://career-ladders.dev/engineering/

Not needed anymore


Support selecting additional components (and targets) at install time

When installing a toolchain, it might be nice to select additional components to install such that they will be immediately available.
For example, editors might auto-install toolchains if needed, and request rls rust-analyzer rust-src etc. without having to override the chosen profile from the user.
In addition, if you know you're going to need a particular target, it'd be nice to preinstall with that too (e.g. if I download some embedded code and know I'll need the thumbv6m-none-eabi target)
Perhaps something like:
rustup toolchain install nightly -c rls -c clippy -t thumbv6m-none-eabi

Note to self to re-enable clippy in https://github.com/crate-ci/azure-pipelines/pull/59 once this lands.

This has landed and is in 1.20


fix frontend to respect permissions, backend still wip

Thank you so much for all of your assistance on this @imorland !


WeArt Touch-Diver yarp device driver

This PR brings the WeArt Touch-Diver YARP device driver.

Hi @EhsanRanjbari  thanks for the great work. I took a quick look (and we tested it together) so it looks ok for me. One comment is to update the readme to reflect if this is repo can be installed and used on Linux (the SDK repo to my knowledge doesn't work there).

I think this PR is ready. I just need to confirm it by testing the gloves on Monday.

With https://github.com/ami-iit/element_haptic-gloves/issues/211#issuecomment-2255821092 into consideration, I am going forward to merge this PR.
Thank you all!


Function pickup modified to allow child-ing to other scene nodes

-Update function pickup to allow selection of controller node from anywhere in scene tree, allowing function pickup to be child of a node other than the controller
-This may be useful for using the XR Avatar project, other full body projects, "physics body" projects or projects where the meshes for interactions are more obscure such as a claw object, such that objects being "held" by the controllers directly rather than as a child of the mesh may create a "floaty" effect to the object pickup.  In other words, where the pickup point may meaningfully diverge from the controller location, being able to set the function pickup to the intended location is helpful, such as to a hand bone attachment on a body mesh or the exact intended point of a moving claw.
-Because default functionality still assumes function pickup is a child of the controller, this change does not damage any pre-existing projects and is non-breaking.  Someone who does not select a controller node but has the function_pickup as a child to the controller does not have to do anything else for this to work out of the box (that is, choosing a node path is purely optional).
-There is an output warning statement if the dev mistakenly does not child the function pickup to a controller and also does not choose a nodepath for a controller, and in that event the function pickup is disabled.

I'm on the fence with this one.
On the one hand the whole idea is to keep things simple and make sure objects are children based on what they operate on. Malcolm and I have done a lot of work in simplifying this. Adding this nodepath will confuse new users of the toolkit who don't understand that this is an alternative use case and are going to wonder how they should set this up. Sadly people hate reading manuals.
The flip side is that I get the use case. Due to the nature of skeletons and full body meshes this will often be a separate node tree alongside the ARVROrigin tree, which means there is a disjoint between where functions that have a visual impact are, and where the controller nodes they operate on are.
A better approach may be that instead for us checking if the parent node is an ARVRController node, we check if the parent node has an get_is_active and get_joystick_axis method and if so we allow it.
Now you can add a bone attachment node for each hand in the avatar model and child the function to that. Just implement the two methods there and have them just call the methods on the relevant ARVRController nodes, those are I assume already known with the avatar as the IK targets will be following those.
This way we hide the complexity of the solution from the end user, and probably open a few other doors where we have objects that follow the hands instead of being direct children

Note that this is similar to #326 and there is further discussion on the subject there.


I don't seem to have seen the dataset, do I need to download it myself？

Yes, the dataset information is presented in the README files of experiments folder.


Add coefficients to foreign field add and mul gates

Closes #12864 12864

!ci-build-me

!ci-build-me

!ci-build-me


Naming items via Explorer interface still fails to claim focus if the application was inactive when the naming was initiated

VS Code Version: 1.72.0
OS Version: MacOS 12.6

Steps to Reproduce:

Have VSCode Open, but click into another window (e.g. a terminal or browser)
Right click a file in the Explorer (without first bringing focus to VSCode)
Try to type the name of the file -- you will be typing in your terminal instead.

I appreciate this issue has been raised a dozen times; it has been closed claiming it is a duplicate of a three year old issue that was marked as wontfix.  This issue is very real and represents my biggest frustration with VSCode; I'm hit with this multiple times per week since I use multiple monitors and often am moving between application contexts.
I beg the team to consider this a real issue that warrants a fix!

Thank you @VSCodeTriageBot -- confirmed this also applies to 1.72.2 (updating the issue to use that version)

\duplicate https://github.com/microsoft/vscode/issues/149818

Ah thank you!  (Sorry for missing that one)


jetson-inference on jetson agx orin L4T 20.04,  jetpack 5.1

Greetings
Trying to get jetson-inference docker container working on a jetson agx orin runing ubuntun 20.04 and jetpack 5.1.  I flashed the L4T system and jetpack on an NVME drive (not the emm drive).  On boot root is associated with the NVME drive.  I've tried pulling the most recent jetson-inference container from your docker site and cloned the jetson-inference distro from github.  When I run docker/run.sh from ~/jetson-inference I get an indication that there is no local installation of jetsion-inference 3.5.1 found.
Thanks much

Hi @malcolmcapel, the container images for JetPack 5.1 are in-progress, for now you still use:  docker/run.sh -c dustynv/jetson-inference:r35.1.0

are there any issues with having the root file system installed on an NVME rather than EMMC memory?

@malcolmcapel I haven't put the rootfs on NVME before, but I don't think so - I routinely put the docker root and my git repos on NVME

Dusty...many thanks for the help!
I just tried to install R35.1 via the method you suggested.
After the installation completed I get:
....
V4L2_DEVICES:
localuser:root being added to access control list
Unable to find image 'dusty/jetson-inference:r35.10' locally
docker: Error respone from daemon: mainfest fo rdustynv/jetson-inference:r35.10 not found: manifest unknown: manifest:unknown
See 'codker run --help'
thanks,
M

I stupidly presumed that the run.sh script would pull the correct docker container.  I manually pulled r35.0.1 and now run.sh succeeded in starting the container.  Thanks again.
M

@malcolmcapel okay great - run.sh typically does pull the correct container by querying your JetPack version, but the jetson-inference container for JetPack 5.1 hasn't been released yet, so it's not working.  Sorry about that - glad you got it working!

  The retraining completed in about 4.5 hours.  I was able to invoke detectnet using the test fuit image set and got great statisitical detection results (as expected with this many epochs).
However, anything inside the jetson-inference containter  that uses gstreamer for video camera access and control fails.  I have a HD Pro webcam C920 attached (logitech) and  v4l2-ctl –list-devices shows:
          HD Pro Webcam C920 (usb-3610000.xhci-4.2):
                         /dev/video0
                         /dev/video1
                         /dev/media1

Along with some devices associated with NV Tegra input.
Anyway,
Detectnet –model=models/fruit/ssd-mobilenet.onnx –labels=models/fruit/labels.txt
--input-blob=input_0 –output-cvg=score –output-bbox=boxes
/dev/video
Results in a bunch of errors indicating the nonfunctionality of the gstreamer handling of the webcam.
at the end of processing the test images.
In contrast, outside of the jetson-inference container gstreamer seem to be functional:
          nvgstcapture-1.0 –camsrc=0  results in a functioning gstreamer video stream from the webcam in a window.

Any idea about how to repair-reinstall-etc gstreamer components within the context of the jetson-inference docker container?
From: Dustin Franklin @.>
Sent: Monday, February 6, 2023 10:12 AM
To: dusty-nv/jetson-inference @.>
Cc: Capel, Malcolm S. @.>; Mention @.>
Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
@malcolmcapelhttps://github.com/malcolmcapel okay great - run.sh typically does pull the correct container by querying your JetPack version, but the jetson-inference container for JetPack 5.1 hasn't been released yet, so it's not working. Sorry about that - glad you got it working!
—
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/1556#issuecomment-1419340337, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5V4EI5DGOEWQBL7U6B5IW3WWEPEBANCNFSM6AAAAAAURXQMKY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Can you post the error log here please?
Also, until the updated container is released, you could build jetson-inference from source and run it outside of docker.

 The retraining completed in about 4.5 hours. I was able to invoke detectnet using the test fuit image set and got great statisitical detection results (as expected with this many epochs).
However, anything inside the jetson-inference containter that uses gstreamer for video camera access and control fails. I have a HD Pro webcam C920 attached (logitech) and v4l2-ctl –list-devices shows:
HD Pro Webcam C920 (usb-3610000.xhci-4.2):
/dev/video0
/dev/video1
/dev/media1
Along with some devices associated with NV Tegra input.
Anyway,
Detectnet –model=models/fruit/ssd-mobilenet.onnx –labels=models/fruit/labels.txt
--input-blob=input_0 –output-cvg=score –output-bbox=boxes
/dev/video
Results in a bunch of errors indicating the nonfunctionality of the gstreamer handling of the webcam.
at the end of processing the test images.
In contrast, outside of the jetson-inference container gstreamer seem to be functional:
nvgstcapture-1.0 –camsrc=0 results in a functioning gstreamer video stream from the webcam in a window.
Any idea about how to repair-reinstall-etc gstreamer components within the context of the jetson-inference docker container?
From: Dustin Franklin @.>
Sent: Monday, February 6, 2023 10:12 AM
To: dusty-nv/jetson-inference @.>
Cc: Capel, Malcolm S. @.>; Mention @.>
Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
@malcolmcapelhttps://github.com/malcolmcapel okay great - run.sh typically does pull the correct container by querying your JetPack version, but the jetson-inference container for JetPack 5.1 hasn't been released yet, so it's not working. Sorry about that - glad you got it working!
—
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/1556#issuecomment-1419340337, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5V4EI5DGOEWQBL7U6B5IW3WWEPEBANCNFSM6AAAAAAURXQMKY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-inference%2Fissues%2F1556%23issuecomment-1419902561&data=05|01|dustinf%40nvidia.com|b0f7629be96d4e1e53e608db0895cfc5|43083d15727340c1b7db39efd9ccc17a|0|0|638113211765103968|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=GRY8BYshakaqetvzbRSYorp0NSiyzWdt1HdSXP%2BYBQ4%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGK47U2G5LU33Z6ORW73WWF65JANCNFSM6AAAAAAURXQMKY&data=05|01|dustinf%40nvidia.com|b0f7629be96d4e1e53e608db0895cfc5|43083d15727340c1b7db39efd9ccc17a|0|0|638113211765103968|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=79FWSXLdG7y1vhKdBXJzNSW5WT6YMUYVQd7MM%2BISoxE%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>

Dustin
Do you mean the dmesg output or does the container run an error log?
Thanks
M
From: Dustin Franklin @.>
Sent: Monday, February 6, 2023 5:16 PM
To: dusty-nv/jetson-inference @.>
Cc: Capel, Malcolm S. @.>; Mention @.>
Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
Can you post the error log here please?
Also, until the updated container is released, you could build jetson-inference from source and run it outside of docker.

From: malcolmcapel<EMAIL_ADDRESS>Sent: Monday, February 6, 2023 5:59:32 PM
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Dustin Franklin<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
Dustin
I’ve exercised a bunch of stuff in the jetson-inference container…including retraining SSD-mobilenet with the fruit image subset (all 6000 or so) and 150 epochs, bastch-size of 4 and workers=4. The retraining completed in about 4.5 hours. I was able to invoke detectnet using the test fuit image set and got great statisitical detection results (as expected with this many epochs).
However, anything inside the jetson-inference containter that uses gstreamer for video camera access and control fails. I have a HD Pro webcam C920 attached (logitech) and v4l2-ctl –list-devices shows:
HD Pro Webcam C920 (usb-3610000.xhci-4.2):
/dev/video0
/dev/video1
/dev/media1
Along with some devices associated with NV Tegra input.
Anyway,
Detectnet –model=models/fruit/ssd-mobilenet.onnx –labels=models/fruit/labels.txt
--input-blob=input_0 –output-cvg=score –output-bbox=boxes
/dev/video
Results in a bunch of errors indicating the nonfunctionality of the gstreamer handling of the webcam.
at the end of processing the test images.
In contrast, outside of the jetson-inference container gstreamer seem to be functional:
nvgstcapture-1.0 –camsrc=0 results in a functioning gstreamer video stream from the webcam in a window.
Any idea about how to repair-reinstall-etc gstreamer components within the context of the jetson-inference docker container?
From: Dustin Franklin<EMAIL_ADDRESS>Sent: Monday, February 6, 2023 10:12 AM
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Capel, Malcolm S<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
@malcolmcapelhttps://github.com/malcolmcapel okay great - run.sh typically does pull the correct container by querying your JetPack version, but the jetson-inference container for JetPack 5.1 hasn't been released yet, so it's not working. Sorry about that - glad you got it working!
—
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/1556#issuecomment-1419340337, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5V4EI5DGOEWQBL7U6B5IW3WWEPEBANCNFSM6AAAAAAURXQMKY.
You are receiving this because you were mentioned.Message ID: @.@.mailto:***<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-inference%2Fissues%2F1556%23issuecomment-1419902561&data=05|01|dustinf%40nvidia.com|b0f7629be96d4e1e53e608db0895cfc5|43083d15727340c1b7db39efd9ccc17a|0|0|638113211765103968|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=GRY8BYshakaqetvzbRSYorp0NSiyzWdt1HdSXP%2BYBQ4%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGK47U2G5LU33Z6ORW73WWF65JANCNFSM6AAAAAAURXQMKY&data=05|01|dustinf%40nvidia.com|b0f7629be96d4e1e53e608db0895cfc5|43083d15727340c1b7db39efd9ccc17a|0|0|638113211765103968|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=79FWSXLdG7y1vhKdBXJzNSW5WT6YMUYVQd7MM%2BISoxE%3D&reserved=0.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/1556#issuecomment-1419923056, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5V4EI5WVTSW2HCZQKOT7GDWWGA3ZANCNFSM6AAAAAAURXQMKY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi @malcolmcapel, I mean the terminal output from when you run the camera with detectnet or video-viewer program, to show what is going wrong with the camera

Dustin..sorry for the delay
When I run: video-viewer /dev/video0 (within the jetson-inference container) I get the following output:
The output is obviously truncated….it ends with a looping “[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame”
looks like the module “nvidia” isn’t loaded.
Thanks,
Malcolm
modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.10.104-tegra
[gstreamer] initialized gstreamer, version <IP_ADDRESS>
[gstreamer] gstCamera -- attempting to create device v4l2:///dev/video0
[gstreamer] gstCamera -- found v4l2 device: HD Pro Webcam C920
[gstreamer] v4l2-proplist, device.path=(string)/dev/video0, udev-probed=(boolean)false, device.api=(string)v4l2, v4l2.device.driver=(string)uvcvideo, v4l2.device.card=(string)"HD\ Pro\ Webcam\ C920", v4l2.device.bus_info=(string)usb-3610000.xhci-4.2, v4l2.device.version=(uint)330344, v4l2.device.capabilities=(uint)2225078273, v4l2.device.device_caps=(uint)69206017;
[gstreamer] gstCamera -- found 53 caps for v4l2 device /dev/video0
[gstreamer] [0] video/x-raw, format=(string)YUY2, width=(int)2304, height=(int)1536, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)2/1;
[gstreamer] [1] video/x-raw, format=(string)YUY2, width=(int)2304, height=(int)1296, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)2/1;
[gstreamer] [2] video/x-raw, format=(string)YUY2, width=(int)1920, height=(int)1080, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)5/1;
[gstreamer] [3] video/x-raw, format=(string)YUY2, width=(int)1600, height=(int)896, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2, 5/1 };
[gstreamer] [4] video/x-raw, format=(string)YUY2, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1, 15/2, 5/1 };
[gstreamer] [5] video/x-raw, format=(string)YUY2, width=(int)960, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [6] video/x-raw, format=(string)YUY2, width=(int)1024, height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [7] video/x-raw, format=(string)YUY2, width=(int)800, height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [8] video/x-raw, format=(string)YUY2, width=(int)864, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [9] video/x-raw, format=(string)YUY2, width=(int)800, height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [10] video/x-raw, format=(string)YUY2, width=(int)640, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [11] video/x-raw, format=(string)YUY2, width=(int)640, height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [12] video/x-raw, format=(string)YUY2, width=(int)432, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [13] video/x-raw, format=(string)YUY2, width=(int)352, height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [14] video/x-raw, format=(string)YUY2, width=(int)320, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [15] video/x-raw, format=(string)YUY2, width=(int)320, height=(int)180, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [16] video/x-raw, format=(string)YUY2, width=(int)176, height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [17] video/x-raw, format=(string)YUY2, width=(int)160, height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [18] video/x-raw, format=(string)YUY2, width=(int)160, height=(int)90, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [19] image/jpeg, width=(int)1920, height=(int)1080, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [20] image/jpeg, width=(int)1600, height=(int)896, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [21] image/jpeg, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [22] image/jpeg, width=(int)960, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [23] image/jpeg, width=(int)1024, height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [24] image/jpeg, width=(int)800, height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [25] image/jpeg, width=(int)864, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [26] image/jpeg, width=(int)800, height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [27] image/jpeg, width=(int)640, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [28] image/jpeg, width=(int)640, height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [29] image/jpeg, width=(int)432, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [30] image/jpeg, width=(int)352, height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [31] image/jpeg, width=(int)320, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [32] image/jpeg, width=(int)320, height=(int)180, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [33] image/jpeg, width=(int)176, height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [34] image/jpeg, width=(int)160, height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [35] image/jpeg, width=(int)160, height=(int)90, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [36] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1920, height=(int)1080, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [37] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1600, height=(int)896, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [38] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [39] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)960, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [40] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1024, height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [41] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)800, height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [42] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)864, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [43] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)800, height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [44] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)640, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [45] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)640, height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [46] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)432, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [47] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)352, height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [48] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)320, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [49] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)320, height=(int)180, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [50] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)176, height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [51] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)160, height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [52] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)160, height=(int)90, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] gstCamera -- selected device profile:  codec=h264 format=unknown width=1280 height=720
[gstreamer] gstCamera pipeline string:
[gstreamer] v4l2src device=/dev/video0 do-timestamp=true ! video/x-h264, width=(int)1280, height=(int)720 ! nvv4l2decoder ! video/x-raw(memory:NVMM) ! nvvidconv flip-method=0 ! video/x-raw ! appsink name=mysink
modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.10.104-tegra
[gstreamer] gstCamera successfully created device v4l2:///dev/video0
[video]  created gstCamera from v4l2:///dev/video0
gstCamera video options:
-- URI: v4l2:///dev/video0
- protocol:  v4l2
- location:  /dev/video0
-- deviceType: v4l2
-- ioType:     input
-- codec:      h264
-- width:      1280
-- height:     720
-- frameRate:  30.000000
-- bitRate:    0
-- numBuffers: 4
-- zeroCopy:   true
-- flipMethod: none
-- loop:       0
-- rtspLatency 2000
[OpenGL] glDisplay -- X screen 0 resolution:  1920x1080
[OpenGL] glDisplay -- X window resolution:    1920x1080
[OpenGL] glDisplay -- display device initialized (1920x1080)
[video]  created glDisplay from display://0
glDisplay video options:
-- URI: display://0
- protocol:  display
- location:  0
-- deviceType: display
-- ioType:     output
-- codec:      raw
-- width:      1920
-- height:     1080
-- frameRate:  0.000000
-- bitRate:    0
-- numBuffers: 4
-- zeroCopy:   true
-- flipMethod: none
-- loop:       0
-- rtspLatency 2000
[gstreamer] opening gstCamera for streaming, transitioning pipeline to GST_STATE_PLAYING
Opening in BLOCKING MODE
[gstreamer] gstreamer changed state from NULL to READY ==> mysink
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter2
[gstreamer] gstreamer changed state from NULL to READY ==> nvvconv0
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter1
[gstreamer] gstreamer changed state from NULL to READY ==> nvv4l2decoder0
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter0
[gstreamer] gstreamer changed state from NULL to READY ==> v4l2src0
[gstreamer] gstreamer changed state from NULL to READY ==> pipeline0
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter2
[gstreamer] gstreamer changed state from READY to PAUSED ==> nvvconv0
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter1
[gstreamer] gstreamer changed state from READY to PAUSED ==> nvv4l2decoder0
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter0
[gstreamer] gstreamer stream status CREATE ==> src
[gstreamer] gstreamer changed state from READY to PAUSED ==> v4l2src0
[gstreamer] gstreamer changed state from READY to PAUSED ==> pipeline0
[gstreamer] gstreamer message new-clock ==> pipeline0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter2
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> nvvconv0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter1
[gstreamer] gstreamer stream status ENTER ==> src
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> nvv4l2decoder0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> v4l2src0
NvMMLiteOpen : Block : BlockType = 261
NVMEDIA: Reading vendor.tegra.display-size : status: 6
NvMMLiteBlockCreate : Block : BlockType = 261
[gstreamer] gstreamer message stream-start ==> pipeline0
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
^Creceived SIGINT
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
video-viewer:  shutting down...
[gstreamer] gstCamera -- stopping pipeline, transitioning to GST_STATE_NULL
[gstreamer] gstCamera -- pipeline stopped
video-viewer:  shutdown complete
@.***:/jetson-inference#
From: Dustin Franklin @.>
Sent: Tuesday, February 7, 2023 8:37 AM
To: dusty-nv/jetson-inference @.>
Cc: Capel, Malcolm S. @.>; Mention @.>
Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
Hi @malcolmcapelhttps://github.com/malcolmcapel, I mean the terminal output from when you run the camera with detectnet or video-viewer program, to show what is going wrong with the camera
—
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/1556#issuecomment-1420880975, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5V4EI3PK7IAYQHQDV2GK23WWJMZVANCNFSM6AAAAAAURXQMKY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.10.104-tegra

OK yes, it appears to be an issue from running the older container, sorry about that.  I hope to have the updated container soon.  In the meantime you could run it outside of container (sorry about that)

I stupidly presumed that the run.sh script would pull the correct docker container. I manually pulled r35.0.1 and now run.sh succeeded in starting the container. Thanks again.
M

Hello, may I ask how you manually pull the correct docker container? I tried cloning the L4T-R35.1.0 branch, but I still have the same issue you described. Is it just me or is it that cumbersome to get the Jetson AGX Orin Kit working on some basic demos??? Thank you!

Hello, may I ask how you manually pull the correct docker container? I tried cloning the L4T-R35.1.0 branch, but I still have the same issue you described. Is it just me or is it that cumbersome to get the Jetson AGX Orin Kit working on some basic demos??? Thank you!

Ok, found out on my own: sudo docker pull dustynv/jetson-inference:r35.1.0

OK, the jetson-inference container for JetPack 5.1 / R35.2.1 is now uploaded at dustynv/jetson-inference:r35.2.1
You should just now be able to run docker/run.sh on JetPack 5.1 and it should pull the correct container 👍

Thanks!
Can you provide a procedure for upgrading to R35.2.1 from R35.1.0 that doesn't disturb the data contained on ./jetson-inference at the time of upgrade?

It won't delete any data unless you do docker/build.sh

From: malcolmcapel @.>
Sent: Friday, February 10, 2023 5:27:35 PM
To: dusty-nv/jetson-inference @.>
Cc: Dustin Franklin @.>; Comment @.>
Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
Thanks!
Can you provide a procedure for upgrading to R35.2.1 from R35.1.0 that doesn't disturb the data contained on ./jetson-inference at the time of upgrade?
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-inference%2Fissues%2F1556%23issuecomment-1426421093&data=05|01|dustinf%40nvidia.com|607baa6bb8f64649f3c608db0bb602aa|43083d15727340c1b7db39efd9ccc17a|0|0|638116648593595069|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=41PgJwANppDBQWFCsAal1x1oW3Dw8ZgPZi%2FkTw7D4zI%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGK6Z5VWOBQS35Z6JM73WW26FPANCNFSM6AAAAAAURXQMKY&data=05|01|dustinf%40nvidia.com|607baa6bb8f64649f3c608db0bb602aa|43083d15727340c1b7db39efd9ccc17a|0|0|638116648593595069|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=rsFUOVxs6RW%2BH0noFQ5rvreFI%2F0%2FL499nTVOdDroz5o%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>

sorry to belabor this but should we do a docker ri on the old container to recover disk space?

Sure yea, you could do that

From: malcolmcapel @.>
Sent: Friday, February 10, 2023 6:24:10 PM
To: dusty-nv/jetson-inference @.>
Cc: Dustin Franklin @.>; Comment @.>
Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
sorry to belabor this but should we do a docker ri on the old container to recover disk space?
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-inference%2Fissues%2F1556%23issuecomment-1426485894&data=05|01|dustinf%40nvidia.com|d73453d6570d40fb55f108db0bbdea62|43083d15727340c1b7db39efd9ccc17a|0|0|638116682527429453|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=sdSvY7GjW2puxY8B%2FvqKTfIVCdGuU%2BEYBN4ndtEQ%2Fmc%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGK275GLOP44H24P3UF3WW3EZVANCNFSM6AAAAAAURXQMKY&data=05|01|dustinf%40nvidia.com|d73453d6570d40fb55f108db0bbdea62|43083d15727340c1b7db39efd9ccc17a|0|0|638116682527429453|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=ZoA9P13MHwOoJlwN%2FHewejQCVC4iTc7EIDOsd0IiPDE%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>

confirmed...a simple docker/run.sh pulled R35.2.1 under jetpack 5.1 on my orin....thanks much for the help!

Dustin:
Sorry to report still getting the NVIDIA module not loaded indicated by modprobe under R35.2.1 on my orin:
root@ubuntu:/jetson-inference/build# cd aarch64/bin
root@ubuntu:/jetson-inference/build/aarch64/bin# ./video-viewer /dev/video0
modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.10.104-tegra
[gstreamer] initialized gstreamer, version <IP_ADDRESS>
[gstreamer] gstCamera -- attempting to create device v4l2:///dev/video0
[gstreamer] gstCamera -- found v4l2 device: HD Pro Webcam C920
[gstreamer] v4l2-proplist, device.path=(string)/dev/video0, udev-probed=(boolean)false, device.api=(string)v4l2, v4l2.device.driver=(string)uvcvideo, v4l2.device.card=(string)"HD\ Pro\ Webcam\ C920", v4l2.device.bus_info=(string)usb-3610000.xhci-4.2, v4l2.device.version=(uint)330344, v4l2.device.capabilities=(uint)2225078273, v4l2.device.device_caps=(uint)69206017;
[gstreamer] gstCamera -- found 53 caps for v4l2 device /dev/video0
[gstreamer] [0] video/x-raw, format=(string)YUY2, width=(int)2304, height=(int)1536, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)2/1;
[gstreamer] [1] video/x-raw, format=(string)YUY2, width=(int)2304, height=(int)1296, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)2/1;
[gstreamer] [2] video/x-raw, format=(string)YUY2, width=(int)1920, height=(int)1080, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)5/1;
[gstreamer] [3] video/x-raw, format=(string)YUY2, width=(int)1600, height=(int)896, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2, 5/1 };
[gstreamer] [4] video/x-raw, format=(string)YUY2, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1, 15/2, 5/1 };
[gstreamer] [5] video/x-raw, format=(string)YUY2, width=(int)960, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [6] video/x-raw, format=(string)YUY2, width=(int)1024, height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [7] video/x-raw, format=(string)YUY2, width=(int)800, height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [8] video/x-raw, format=(string)YUY2, width=(int)864, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [9] video/x-raw, format=(string)YUY2, width=(int)800, height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [10] video/x-raw, format=(string)YUY2, width=(int)640, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [11] video/x-raw, format=(string)YUY2, width=(int)640, height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [12] video/x-raw, format=(string)YUY2, width=(int)432, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [13] video/x-raw, format=(string)YUY2, width=(int)352, height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [14] video/x-raw, format=(string)YUY2, width=(int)320, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [15] video/x-raw, format=(string)YUY2, width=(int)320, height=(int)180, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [16] video/x-raw, format=(string)YUY2, width=(int)176, height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [17] video/x-raw, format=(string)YUY2, width=(int)160, height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [18] video/x-raw, format=(string)YUY2, width=(int)160, height=(int)90, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [19] image/jpeg, width=(int)1920, height=(int)1080, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [20] image/jpeg, width=(int)1600, height=(int)896, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [21] image/jpeg, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [22] image/jpeg, width=(int)960, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [23] image/jpeg, width=(int)1024, height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [24] image/jpeg, width=(int)800, height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [25] image/jpeg, width=(int)864, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [26] image/jpeg, width=(int)800, height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [27] image/jpeg, width=(int)640, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [28] image/jpeg, width=(int)640, height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [29] image/jpeg, width=(int)432, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [30] image/jpeg, width=(int)352, height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [31] image/jpeg, width=(int)320, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [32] image/jpeg, width=(int)320, height=(int)180, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [33] image/jpeg, width=(int)176, height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [34] image/jpeg, width=(int)160, height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [35] image/jpeg, width=(int)160, height=(int)90, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [36] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1920, height=(int)1080, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [37] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1600, height=(int)896, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [38] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1280, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [39] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)960, height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [40] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)1024, height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [41] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)800, height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [42] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)864, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [43] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)800, height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [44] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)640, height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [45] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)640, height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [46] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)432, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [47] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)352, height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [48] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)320, height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [49] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)320, height=(int)180, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [50] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)176, height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [51] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)160, height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] [52] video/x-h264, stream-format=(string)byte-stream, alignment=(string)au, width=(int)160, height=(int)90, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 24/1, 20/1, 15/1, 10/1, 15/2, 5/1 };
[gstreamer] gstCamera -- selected device profile:  codec=h264 format=unknown width=1280 height=720
[gstreamer] gstCamera pipeline string:
[gstreamer] v4l2src device=/dev/video0 do-timestamp=true ! video/x-h264, width=(int)1280, height=(int)720 ! nvv4l2decoder ! video/x-raw(memory:NVMM) ! nvvidconv flip-method=0 ! video/x-raw ! appsink name=mysink
modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.10.104-tegra
[gstreamer] gstCamera successfully created device v4l2:///dev/video0
[video]  created gstCamera from v4l2:///dev/video0
gstCamera video options:
-- URI: v4l2:///dev/video0
- protocol:  v4l2
- location:  /dev/video0
-- deviceType: v4l2
-- ioType:     input
-- codec:      h264
-- width:      1280
-- height:     720
-- frameRate:  30.000000
-- bitRate:    0
-- numBuffers: 4
-- zeroCopy:   true
-- flipMethod: none
-- loop:       0
-- rtspLatency 2000
[OpenGL] glDisplay -- X screen 0 resolution:  1920x1080
[OpenGL] glDisplay -- X window resolution:    1920x1080
[OpenGL] glDisplay -- display device initialized (1920x1080)
[video]  created glDisplay from display://0
glDisplay video options:
-- URI: display://0
- protocol:  display
- location:  0
-- deviceType: display
-- ioType:     output
-- codec:      raw
-- width:      1920
-- height:     1080
-- frameRate:  0.000000
-- bitRate:    0
-- numBuffers: 4
-- zeroCopy:   true
-- flipMethod: none
-- loop:       0
-- rtspLatency 2000
[gstreamer] opening gstCamera for streaming, transitioning pipeline to GST_STATE_PLAYING
Opening in BLOCKING MODE
[gstreamer] gstreamer changed state from NULL to READY ==> mysink
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter2
[gstreamer] gstreamer changed state from NULL to READY ==> nvvconv0
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter1
[gstreamer] gstreamer changed state from NULL to READY ==> nvv4l2decoder0
[gstreamer] gstreamer changed state from NULL to READY ==> capsfilter0
[gstreamer] gstreamer changed state from NULL to READY ==> v4l2src0
[gstreamer] gstreamer changed state from NULL to READY ==> pipeline0
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter2
[gstreamer] gstreamer changed state from READY to PAUSED ==> nvvconv0
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter1
[gstreamer] gstreamer changed state from READY to PAUSED ==> nvv4l2decoder0
[gstreamer] gstreamer changed state from READY to PAUSED ==> capsfilter0
[gstreamer] gstreamer stream status CREATE ==> src
[gstreamer] gstreamer changed state from READY to PAUSED ==> v4l2src0
[gstreamer] gstreamer changed state from READY to PAUSED ==> pipeline0
[gstreamer] gstreamer message new-clock ==> pipeline0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter2
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> nvvconv0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter1
[gstreamer] gstreamer stream status ENTER ==> src
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> nvv4l2decoder0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> capsfilter0
[gstreamer] gstreamer changed state from PAUSED to PLAYING ==> v4l2src0
NvMMLiteOpen : Block : BlockType = 261
NVMEDIA: Reading vendor.tegra.display-size : status: 6
NvMMLiteBlockCreate : Block : BlockType = 261
[gstreamer] gstreamer message stream-start ==> pipeline0
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
^Creceived SIGINT
[gstreamer] gstDecoder -- failed to retrieve next image buffer
video-viewer:  failed to capture video frame
video-viewer:  shutting down...
[gstreamer] gstCamera -- stopping pipeline, transitioning to GST_STATE_NULL
[gstreamer] gstCamera -- pipeline stopped
video-viewer:  shutdown complete

on the main system (outside of the jetson-inference container) there is an nvdia.ko on /lib/modules/5.10.104-tegra/extra/opensrc-disp

I get that message too, but my Logitech C920 works okay with the same command.    Just for debugging purposes, could you try setting --input-codec=raw ?
You could try mounting that /lib/modules/5.10.104-tegra directory into the container to see if it makes any difference...

Dustin
Would you mind telling me how to mount /lib/modules/5.10.104-tegra into the container? I’m a total newbee with respect to docker.
Thanks,
M
From: Dustin Franklin @.>
Sent: Friday, February 10, 2023 7:23 PM
To: dusty-nv/jetson-inference @.>
Cc: Capel, Malcolm S. @.>; Mention @.>
Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
I get that message too, but my Logitech C920 works okay with the same command. Just for debugging purposes, could you try setting --input-codec=raw ?
You could try mounting that /lib/modules/5.10.104-tegra directory into the container to see if it makes any difference...
—
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/1556#issuecomment-1426555788, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5V4EIYUCJKUMFPC2JS3H23WW3SVNANCNFSM6AAAAAAURXQMKY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

I just tried doing docker/run.sh -v /lib/modules/5.10.104-tegra:/lib/modules/5.10.104-tegra and that got rid of that error message.  It didn't change anything else about the way it ran for me though.

Dustin
--input-codec=raw worked in getting video-viewer to work under the jetson-inference container.  I had also invoked the docker container with the option "v /lib/modules/5.10.104-tegra:/lib/modules/5.10.104-tegra".  If I leave off the input-codec option then video-viewer fails as before.
M

bye the way --input-codec=mjpeg also worked for this webcam  (Logitech HD Pro C920 )

Hmm okay, thanks.  For some reason my C920 only has raw and mjpeg modes, no h264.  I guess h264 was added in a later revision of the camera?

From: malcolmcapel @.>
Sent: Saturday, February 11, 2023 2:07:30 PM
To: dusty-nv/jetson-inference @.>
Cc: Dustin Franklin @.>; Comment @.>
Subject: Re: [dusty-nv/jetson-inference] jetson-inference on jetson agx orin L4T 20.04, jetpack 5.1 (Issue #1556)
bye the way --input-codec=mjpeg also worked for this webcam (Logitech HD Pro C920 )
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-inference%2Fissues%2F1556%23issuecomment-1426855692&data=05|01|dustinf%40nvidia.com|69ea84efa8d24c03121e08db0c6339b5|43083d15727340c1b7db39efd9ccc17a|0|0|638117392533101552|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=xBCxMd%2FsxWRRoOpTczYxrdEuVnvBpEbwZ3lNgU7gaFs%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGK3KLIXRBJV5DYYN7NTWW7PPFANCNFSM6AAAAAAURXQMKY&data=05|01|dustinf%40nvidia.com|69ea84efa8d24c03121e08db0c6339b5|43083d15727340c1b7db39efd9ccc17a|0|0|638117392533257793|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=oYfCDuXtCukMuVmZVy%2BQ0BsYXXcMVwGL2qcBRnrqxnw%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>


What's the meaning of segment_ids in the dataset?

Hello,
I check the segment_ids in your dataset:
(Pdb) train_dataset.segment_ids[960:1050]
memmap([341, 341, 341, 341, 341, 341, 341, 341, 301, 301, 341, 341, 341,
        341, 341, 341, 341, 341, 301, 301, 341, 341, 341, 341, 341, 341,
        341, 341, 301, 301, 341, 341, 341, 341, 341, 341, 341, 341, 301,
        301, 341, 341, 341, 341, 341, 341, 341, 301, 301, 301, 341, 341,
        341, 341, 341, 341, 341, 301, 301, 301, 341, 341, 341, 341, 341,
        341, 341, 301, 301, 301, 341, 341, 341, 341, 341, 341, 341, 301,
        301, 301, 341, 341, 341, 341, 341, 341, 341, 301, 301, 301],
       dtype=uint16)

If I understand correctly, it means the sample comes from episode 341 and 301, respectively. The samples come from episode 341 are continuous, even if some samples from episode 301 are among them. Is my understanding correct here?
Best,
StarCycle

Hi StarCycle,
Thanks for the question. I believe the RawTokenDataset we provide does not have a segment_ids field, so I assume you have modified some code. It looks like your "segment_ids" are actions, as the values from your code snippet match the actions at those indices.
The actual segment ids -- segment_ids.bin in data/train_v0 and data/val_v0 -- should be nondecreasing. Frames with the same segment id are continuous and part of the same episode.
See seg_ids in RawTokenDataset.__init__ for an example of loading segment ids, note that it is int32.

Hi @kev-zhao,
I see. Sorry there is an error in my code...Thanks!


Port forwarding?

Is it possible to setup port forwarding along with this crate? I see in your source code that you're just calling the ssh command, which is perfect because then we can just add a -R 80:localhost:80 or a -L 80:localhost:80 to the ssh command based on what ports needs to be forwarded.
Would you be open to implementing that? Additionally, just out of curiosity, I see in other issues that you've not found time to work on this recently. As of today, does the library still work or are there any pitfalls in the library that prevent it from working for a production use?

It should be totally possible to add — want to give writing a PR a try? I'd be happy to review!
As far as I'm aware, this library still works well, and doesn't have any known pitfalls :) It's only a wrapper around ssh after all, so it's sort of limited how badly wrong it can be!

Haha okay. Sounds good. I'd be happy to try and implement this in a PR. Where would I start with? What should I look into to get an understanding of the code?

Nice! I would start out looking at how Sftp is implemented, starting here:
https://github.com/jonhoo/openssh-rs/blob/bdb9e34cad2438ba5e243999c80b0fa0973d9e83/src/lib.rs#L311
and extending into https://github.com/jonhoo/openssh-rs/blob/master/src/sftp.rs. Port forwarding should be even easier than that. I'm thinking something like a method on Session that returns a struct OpenPort, where dropping that then closes the port again.

So I'm a little confused. How does this work with sftp with the same session? Doesn't sftp require you to run a separate command altogether than ssh? How does this open an ssh connection and subsequently open an sftp connection on the same ssh connection? I'm wondering because port forwarding requires you to run a bunch of args while calling the ssh command, and I'm wondering how I can do that after I've opened a connection. Maybe I don't know enough about ssh, but I'm confused how it's structured. Any help would be appreciated.

Ah! We're pulling a little trick using SSH's support for multiplexing. Basically, we run one ssh command that is the main connection to the server, and then we tell subsequent invocations of the ssh command to re-use that same connection, and just open another "channel" on top of it. You can read a bunch more details at https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Multiplexing. Most of the details are hidden from you by the internals of the library — you basically just have to invoke the ssh command, and the library will take care that it re-uses the existing connection behind the scenes.

Oh nice! That sounds fancy. So I just need to take care of opening an ssh connection, with the required parameters, yeah? Sounds simple enough. I'll try coming up with a PR. Thanks!

@rakshith-ravi #26 adds port forwarding functionality and integration test for it.


https://github.com/reduxjs/redux/tree/master/examples/todos-flow Is outdated

What docs page needs to be fixed?
https://github.com/reduxjs/redux/tree/master/examples/todos-flow
What is the problem?
redux no longer exports the Store and Dispatch (or any) Flow types. Additionally, the version of flow-bin in this example is very far behind the latest version of flow-bin (0.142.0).
Second to this, actually running npm flow on a fresh build of this project results in 63 Flow errors.
What should be changed to fix the problem?
This example should be updated or removed if redux no longer intends to provide examples of using redux with Flow.

Yeah, I don't really know Flow and that was only added by contribution. We should probably remove it, given Flow's waning popularity.

Yeah, I don't really know Flow and that was only added by contribution. We should probably remove it, given Flow's waning popularity.

Yeah, this issue is really a dupe of #3917 .

Yeah, this issue is really a dupe of #3917 .


Malware Warning in Godot 3.2 (Mono) RC2 and RC3 Export Templates

Godot version:
Godot 3.2 (Mono) RC3
OS/device including version:
Windows 10 64bit
Issue description:
I am getting an Malware warning when downloading and installing the export templates for the recent RC of 3.2.mono.
The files "windows_32_release.exe" and "windows_32_debug.exe" in "Godot/templates/3.2.rc3.mono" are suspected to contain the Malware: BDS/ZeroAccess.Gen7
It only appears for the mono Version.
Steps to reproduce:
Install avira and download export templates
Minimal reproduction project:
any

Closing as there's nothing else to do from our end, there's no malware whatsoever in Godot binaries, so antiviruses have to fix their false positives.

You should submit them to AVG too


Stg94 Snapshot management support via REST for NFS shares

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure:azure-storage-file-share


Configure default retries matching Istio

Every so often we see a failure like this, where we get:
    util.go:131: Saw unexpected response "upstream connect error or disconnect/reset before headers. reset reason: connection failure" 1 times.

(thanks to @vagababov for the improved instrumentation!)
It turns out that when we dropped the explicit retries in the kingress spec, we allowed Istio's default retry policy to kick in, which insulates net-istio from this sort of thing, but Contour doesn't have similar defaults.  With this change, we explicitly configure a default similar to Istio's.

Also updated networking to pull in the change to address 404s.


Catch errors in Reader.js to prevent halting due to badly formatted pager messages

Description
As described in error #346  catches any errors during the parsing of pager messages, thus preventing any sudden exiting of the script.  I expect the issue is recurring due to unexpected characters in messages. I've had this personally happen in pager messages where there are line breaks.
Fixes # (issue)
Try/catch wrapped around the main line.match parsing section. Logs to console.error.
** Parsing itself should be expanded upon to accommodate unusually formatted pages. **
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Ran the reader with the same messages fed through to replicate the cause of "TypeError: Cannot read property '1' of null" killing the script.

I'd say pop them in another pull request, as its your contribution....
Also, in re to multi-line, better to use a JS solution rather than relying on the system to do new line replacements. Could maybe separate each line into multiple messages, but that may require more work than its worth.

The problem is that thats typically not how Linux piping works. The script executes every line individually. You could delay sending the message to see if theres another line, but then multiple messages sent together would end up as a single message. You would be better to remove the line break and execute reader.js once for one message, than treating every line as though there might be another coming. Especially when the line break will get stripped out by the time it makes it to the client anyway by the browser, because browsers dont render newlines in html anyway.

As I said, more work to refactor it for an uncommon use-case.
Here, I was referring to using JS for stripping the newlines rather than using a linux command,

Also, in re to multi-line, better to use a JS solution rather than relying on the system to do new line replacements.

Js doesnt see the newlines is my point. Js never sees "message body \n more message body". Js just gets "process this", followed by "now process this".
Im not sure what the issue with not using JS is, given that the reader.js file is specifically made to read the output of a linux command (multimon-ng) anyway, which is being fed from another (rtl-fm). If you eliminate the non js commands, you also eliminate the need for the js.

if (address.length > 2 && trimMessage.length > 1)

Here probably should be:

if (address.length > 1 && trimMessage.length > 1)

since 9 is already valid pocsag address if I remember correctly

if (address.length > 2 && trimMessage.length > 1)

Here probably should be:

if (address.length > 1 && trimMessage.length > 1)

since 9 is already valid pocsag address if I remember correctly

If 9 is valid then >1 wont catch it either.
I should have explained the 2 though. The erroneous messages from memory contained a single space or an arbitrary character, and were coming from an address of 99.
I actually wasnt aware that that was a valid address. Nonetheless, if you change it to >1 it will still filter the empty messages that were causing the issue. It wont filter the arbitrary characters, but thats what filters are for, so that works for me.

I did already completely rewrite reader.sh in #434, but no-one that originally had the problem did participate in testing, and since it's an edge case ...

Can we confirm this is still needed?
Drop back into non-wip if so plz :)


add blosc and bloscpack args

Add args for blosc and bloscpack
Turn off bloscpack offsets and checksum (I'm not sure that this is wise)
Specify blosc args per dtype.

You probably also want to make the chunk_size configurable.

I'd like to merge this soon if there are no objections.

I still think that the defaults are failry specific to the NYC-Taxi Dataset, so I'd object to those. But on the other hand there is no easy way to determine defaults. Maybe some kind of (dask-baed) hyperparameter search and cross-validation could be used to quasi-fit optimal parameters. (although I doubt that the high-dimensional parameter space will be convex and it is discrete)

Anyway, let's merge this in for now and see what happens.


Support for on-exit handler.

For more context see the slack thread here.
In speaking to the team, I understand there's no way right now to specify an on-exit task to be performed on a thread run from trains-agent. In my script, I have a signal handler that catches SIGINT and SIGTERM and saves the model. This is useful when terminating a long running experiment where I still want the model to be saved.
Unfortunately aborting the same thread from trains-agent does not produce the same outcome. The trains task not only overwrites the signal handles, it SIGKILL's (or equivalent) the script if it doesn't exit in 2 seconds, which may not be enough time to run a final validation run and save the model.
What would be great is an explicit handler that is called on exit, and an extended (or maybe configurable) grace period on exit. In many cases, the handler may signal a separate training thread to save and exit, which may take some time. Premature termination of the script will impede the proper cleanup.

Thank you @nimski this s great idea.
What I was thinking is something like:
task.add_exit_callback(callback_fn, timeout=300)

Where callback_fn will be called either on_exit or on Task abort, and timeout is the maximum number of seconds for the callback to return ( this will be prevent a deadlock situation).
The main caveat is that the callback_fn will be called from an external thread, specifically in the Abort case. This means the main thread training loop, might still be running.
I'm not sure if we could actually avoid this flow, especially with Aborting the task.
What do you think?

----- INTERNAL -----
Can it be Task.add_exit_callcack() or must it be task.add_exit_callback() ?
On Wed, May 27, 2020 at 12:36 PM Martin.B<EMAIL_ADDRESS>wrote:

Thank you @nimski https://github.com/nimski this s great idea.
What I was thinking is something like:
task.add_exit_callback(callback_fn, timeout=300)
Where callback_fn will be called either on_exit or on Task abort, and
timeout is the maximum number of seconds for the callback to return (
this will be prevent a deadlock situation).
The main caveat is that the callback_fn will be called from an external
thread, specifically in the Abort case. This means the main thread training
loop, might still be running.
I'm not sure if we could actually avoid this flow, especially with
Aborting the task.
What do you think?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/allegroai/trains-agent/issues/20#issuecomment-634546740,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AODU3UB5JQSD6JWIT6WJYN3RTTNKLANCNFSM4NLMGY4Q
.

--
Gil Westrich
VP R&D, Allegro.ai
E<EMAIL_ADDRESS>W: www.allegro.ai

@bmartinn that sounds like a great approach to it. callback_fn running from an external thread is most likely fine. I imagine the typical use case is that callback_fun signals the main thread to wrap things up, with the program terminating when it does.
I do wonder about the timeout value though. At least in my case, the exit handler requests a final validation step to be performed, which can take a variable amount of time depending on available compute resources. To set a meaningful timeout, I'd have to estimate how long it would take to do that. Practically, I'd probably just set the timeout to a very large value and rely on the script terminating normally.

@nimski I think you are correct, I guess that if you are waiting for one last step, timeout should be quite large.
The idea that you have to provide a timeout, otherwise you can end up with an experiment that although needs to be aborted, is stuck forever.
The only additional thing that comes to mind, is maybe allowing you to have another level of abort.
 This way, there is always a way to terminate a stuck experiment.
What do you think?

That is compatible with how most popular operating systems design their interfaces around terminating processes @bmartinn. One level is a "suggestion" to exit, with no real timeout. SIGTERM is an example of this. Another level is the "force quit" -- terminating the process immediately. I think a similar pattern would be very relatable and useful. It does however require some extra UI elements on the trains web app and API to separate the two types of requests.
I think the simple interface with a timeout provides 99% of the utility, though. If given a choice between the two systems I'd pick the simpler one unless they had the same development complexity :).

+1 waiting for this as well

@morcoGreen, @nimski apologies for this late response, but there is finally support for shutdown callback 🎉 🎊
You have to have both clearml >= 1.7.0 clearml-agent>=1.4.0 and clearml-server>=1.6.0
Then you can just add to your code
from clearml import Task

def abort_callback():
  print("we were aborted")

task = Task.init(...)
task.register_abort_callback(callback_function=abort_callback, callback_execution_timeout=30.)

abort_callback will be called if the Task is aborted by a user. Notice the callback_execution_timeout is the maximum time to allow the abort call back to run, in seconds. After this timeout the Task will be terminated even if the callback did not finish executing.


Issue with non-specific IP Address Binding

I understand the reasoning behind changing the binding to be non-specific and I'm okay with editing the bindings manually to the specific IP address, however, in Windows 2008/2008R2, if the certificate name does not start with *, the host name field goes blank and is greyed out. Is it possible to either a) get the ip specific bindings back or b) name the certs with an * in the front to allow editing on these older servers?

Hi Bill, both options are on the table. The ability to freely configure the FriendlyName is already on the issue list here #404. The ability to add an IP-specific binding is #217. Neither are currently high priorities because they seem to be inconveniences rather than showstoppers (correct me if I'm wrong), but they won't be forgotten. Please let your voice be heard in those issues if you have ideas about how it should be implemented, use cases, etc.!


[AMD] Improve codebase style consistency in third_party/amd

This commit improved codebase style consistency in 3 aspects

Updated namespace declaration to a nested fasion
Unified header guards
Updated comment styles following LLVM/MLIR style, focusing on the comments on the declarations of top-level function/class/struct and class members.

New contributor declaration

[x] I am not making a trivial change, such as fixing a typo in a comment.

[ ] I have written a PR description following these
rules.

[x] I have run pre-commit run --from-ref origin/main --to-ref HEAD.

Select one of the following.

[ ] I have added tests.

/test for lit tests
/unittest for C++ tests
/python/test for end-to-end tests

[x] This PR does not need a test because lint changes.

Select one of the following.

[x] I have not added any lit tests.
[ ] The lit tests I have added follow these best practices,
including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)

For record, the code snippets this PR fixed was found by the following commands:
namespace:
cd third_party/amd/
grep -nrI --exclude-dir "backend" "namespace" .

header guard:
#!/bin/bash

set -euxo pipefail

ROOT=$(cd .. && pwd)

cd ./third_party/amd/

cpplint \
    --exclude="backend/" \
    --root=${ROOT} \
    --repository=${ROOT} \
    --recursive \
    --filter=-runtime,-whitespace,-legal/copyright,-readability/todo,-build/include_what_you_use,-build/include_order,-build/include,+build/namespaces,+build/header_guard,-build/namespaces \
    --quiet \
    .

comments:
cd third_party/amd/
egrep -nrI --exclude-dir "backend" "^\ +//\ " .

And since third_party/amd/backend/ has many files ported from other codebases, it has been excluded in this PR.


Allow deletion of users with shared entities?

Pending specification
Right now you can't delete an organization user who has shared entities. Should we allow it? Maybe after a warning message?
cc @javisantana @saleiva @xavijam

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Feature/no browser testing

SonarQube analysis reported 1 issue

 1 critical

Watch the comments in this conversation to review them.


Fix DOMNesting Bug

Previously, a weird validateDOMNesting warning was appearing in console when a user navigates to the main route. This error was occurring while using the Material UI  element, which picks  as the default root component if none is specified.

Let's clean up some of the prettier issues and update the branch. But putting those aside, the code changes look good!


[Docs] It looks like everything is "experimental"

If you look at this:

It looks like everything is "experimental". Also, when you scroll to Watchtower, for example, it doesn't say that it's experimental there, and the "experimental" section is hidden.

It's mainly a

It's mainly a


fixfix compatible with hdfs HA empty prefix

Proposed changes
fix for https://github.com/apache/doris/pull/22342
support 'hdfs:/' prefix
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.46 seconds
stream load tsv:          534 seconds loaded<PHONE_NUMBER>9 Bytes, about 133 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.0 seconds inserted 10000000 Rows, about 344K ops/s
storage size:<PHONE_NUMBER>8 Bytes

run p0

run buildall

run buildall

run p0

run p0

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.75 seconds
stream load tsv:          509 seconds loaded<PHONE_NUMBER>9 Bytes, about 140 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.0 seconds inserted 10000000 Rows, about 344K ops/s
storage size:<PHONE_NUMBER>5 Bytes

run clickbench


Catapult API : initial commit

add:  get all players (x,y position) from an activity X. Also snychronises the timestamps if different start of timestamps (not tested yet)

Hi @VellaRo ,
thanks for your contribution. To be considered for merging, I'd encourage you to read our contributing guidelines and stick to the best practices we follow. I anticipate this is a rather larger addition you are planning, so maybe it makes more sense to start with an issue discussing your contribution.


chore: setup commit workflow

What this PR does / why we need it:
Automate npm run package and commit for easier maintainability of this github action.

Will fix format later, I'm overhauling how prettier run


Change the designator in transaction history

Change Validator and To to Account to avoid misleading issues inside TransactionHistory

Change Validator and To to Account to avoid misleading issues inside TransactionHistory

Perhaps it would be even better to not use the generic term Account but use the transaction's context to display a more meaningful thing.
For example, for a transfer txn where the wallet is the destination or for a reclaim escrow transaction, it would show From.
On the other had, for a transfer txn where the wallet is the source or for a add escrow transaction, it would show To.
I would also be nice if it would be unified with the Preview transaction's field names (#77).

Thank you for reporting this issue. We have updated our Oasis Wallet with bug fixes and new features which should also solve mentioned issue above.
If you still encounter same or similar issue, please check our FAQ or send an email to our support team at<EMAIL_ADDRESS>


Set default server.maxsize to the sum of segment cache

Fixes #6469 and #10007
druid.server.maxSize will now default to the sum of maxSize values defined within the druid.segmentCache.locations. User can still provide a custom value for druid.server.maxSize which will take precedence over the default value.
Since there aren't many usecases where this property needs to be different from the segmentCache size, we could gradually remove this user property in the future.

This PR has:

[x] been self-reviewed.
[x] added documentation for new or modified features or behaviors.
[x] been tested in a test Druid cluster.

@gianm Thanks for the review and I've made the changes based on your comments. I haven't touched the blurb about max_size in the system schema documentation , as it points to the  druid.server.maxSize documentation anyways.


Add pre-commit config to run checks locally

For thought and discussion.  There don't seem to be any real downsides for using local checks using pre-commit since it only adds optional configuration changes to the local dev environment.
This PR makes two changes:

Add a pre-commit configuration to run the code checks locally that are already run on PRs (https://github.com/CDCgov/prime-public-health-data-infrastructure/pull/31).  This runs black and flake8 on python code and terraform fmt on terraform code.  terraform may not be installed locally by all developers and in that case, this terraform check will pass allowing this config to be used even if terraform isn't installed.  This check was done instead the available terraform pre-commit repos because all of them I checked fail when terraform is not available.
Run test workflow on push to main, this will trigger it to run after PR merges and in any case where code is pushed directly to main

Some info about using pre-commit has been added to docs/getting_started.md to describe how to set up and use pre-commit.
If pre-commit is not installed or if you do not install the hooks, then these changes will not affect you.

is it possible to add src/notebooks to an exception list for both precommit and the github action?

Yes, definitely!  I pushed another commit into this PR that makes that change.  It adds a black configuration that applies to both the github workflow and running locally.  I went ahead and updated the workflow so it doesn't install the jupyter extras for black since it is no longer necessary.


If you would add more tiles and blocks, this would be even much better and propably more people would use this. Anyways, I think it's pretty hard to program.

There is an updated version that you can find here, PS I would've prefered if the owner of that repository forked rather than make a new repo.
Having no interest into the game I do not have more time to spend on this project. If anyone wants to bother pull requests are open.


feat: add infinite approval to execution settings

feat: add infinite approval to execution settings
test: disable failing int test

Alright it seems that more receipt tests fail here than locally. Will ignore them for now since we will move the whole receipt parsing to the BE we can simply remove all the code then (https://lifi.atlassian.net/browse/LF-442)


Duplicated context menu entries: Play/Queue/Play next

Duplicated context menu entries: Play/Queue/Play next

Looks like it's only on Firefox version without those fixes:
Bug 1275116 - documentUrlPatterns does not work in the contextMenus API
Bug 1275126 - "targetUrlPatterns" in contextMenus fails with an error if the ContextType is "image"
but with Issue #8 and #4 fixed.

Works fine in official build of Firefox 50.0
Closing


Global attention to  tokens with window_size arg

Hi!
First of all, thank you for your incredible work on this repository.
I'm wondering, if there is a way to use flash_attn_varlen_qkvpacked_func with window_size, so that first/last K tokens (CLS tokens) were performing regular (global) attention?
Such an option would be beneficial in order to implement Longformer model with flash attention.

No that's not supported.


Clean up rockspec

Using functions from a rockspec is silly.
Use a simple static table definition instead.
Things from the "platforms" section get merged in.

looks good to me

@tarruda do you have any objections with this change?

I was not aware that luarocks took care of recursively merging platform/common settings like that(In fact I simply copied from an existing rockspec). Is nil at the start of each platform-specific libraries table is a placeholder for uv?
In any case, I have no objections if nothing breaks, so LGTM


Documentation Error for Android Preferences android-minSdkVersion

For Phonegap Build, the default android-minSdkVersion is stated as 7 in the documentation. This incorrect. It should be 14.
The page I am talking about is:
Docs -> Preferences -> Android Only

android-minSdkVersion states:

Minimum Android SDK version. Corresponds to the usesSdk attributes in the AndroidManifest.xml file - more details are in the Android documentation. Defaults to 7 (Android 2.1).

This wrong as of cli-5.2.0 and version before.  It should be written Defaults to 14 (Android 4.0.0-4.0.2).
The Android SDK that is supported by cli-5.1.1 is Android API level 14

SEE: Cordova
Android Platform Guide
Related: Cordova Blog Tools Release: August 13th, 2015 (5.2.0)

@jessemonroy650 Thanks for catching the issue.
We track PhoneGap Build specific issues (including documentation) under the PhoneGap Build issue tracker. Would you mind resubmitting the above issue to phonegap/build/issues?
Thanks!
Michael

No Problem. Done.

Hi @jessemonroy650,
Sorry, I provided the wrong link. It should have been: https://github.com/phonegap/build/issues/
I've updated it in the original post.

Okay it is now issue #487

Thanks @jessemonroy650 and sorry for the roundabout confusion.


Dependency versions out of date & with security issues

I have been looking at the latest version of JMX-Trans and have noticed that some of the dependencies are out of date and they also have various security flaws.
Here is a summary of the patches that will address the CVEs included in the attached file:
org.yaml_snakeyaml version 1.23 | fixed in 1.26
com.fasterxml.jackson.core_jackson-databind version <IP_ADDRESS> | fixed in 2.10.0
com.google.guava_guava version 19 | fixed in 24.1.1
io.netty_netty-codec version 4.1.12.Final | fixed in 4.1.46
jmxtrans-security-scan.csv.zip

Jackson and Guava fixed in #787 #788 #789

Jackson and Guava fixed in #787 #788 #789


Switch dependencies to peer dependencies

ts-node and tsconfig-paths should be peer dependencies.

fixed on version 1.3.1


Broadlink cover component

I have setup my home system to include cover blind motors which are controllable by broadlink rm3. The covers have open close and stop commands avaliable.
I have then included the covers to homekit via homebridge and am able to give commands to open the blinds to %55 percent for instance. Is there a way to get similar functionality with home assistant?

This is the issue tracker. Please use the forum for feature requests. Thanks


How to search/get a cart values/item with its id not rowId

public function addCart($id)
{
$products = MarketProduct::find($id);
    $cartproduct = Cart::search(array('id' => $id, 'options' => array('available_quantity' => ?)));

     return  $cart_available_quantity = $cartproduct->options->available_quantity;

    $available_quantity = $products->product->available_quantity;

    then compare $cart_available_quantity and $available_quantity before adding more qty

    $result = Cart::add([
        'id' => $id,
        'name' => $products->title,
        'qty' => 1,
        'price' => $products->mrp(),
        'options' => [
            'image' => $products->thumbnail(),
            'available_quantity' => $available_quantity
            ]
        ]);

    return redirect()->back();

}

Use the search method

Sir your answer is not clear to me. I already used the search method. Have close look on the code
$cartproduct = Cart::search(array('id' => $id, 'options' => array('available_quantity' => ?)));

Cart::content()->where('id', $id); this code did the tricks for me...

I also can't understand how the search function works here.
But the @wasid 's solution also works for me. Thanks man.👏

Cart::content()->where('id', $id); this code did the tricks for me...

But how to get the qty ?

Sorry if i misunderstand the topic but using the search method is just Collection::filter, you should be able to iterate the returning collection or use first() and then be able to access the quantity as it is a public property of the CartItem class like this: $item->qty
https://github.com/Crinsane/LaravelShoppingcart/blob/f460ab7312cce32cb428cf39a500a2d16600b1d6/src/CartItem.php#L30
So out of my head something like that should work:
$cart->search(function($value, $key){
  return $value->id === $id;
})->first()->qty;

@bumbummen99, Its very simple ..................
$asd = Cart::content()->where('id', $request->product_id);
$cart_indqty = 0;
    foreach ($asd as $row) {
        $cart_indqty = $row->qty;
    }


Issue loading pathway v7.78

@Zethson You added this new version of pathway here: https://github.com/laminlabs/bionty/pull/329. But the ontology file isn't present on s3://bionty-assets. I tried to download it from the source but got the above error.
So I'm removing this version for the moment. Could you take a look? If you can load the file correctly, could you upload a version to s3 and add this version back?