Skybell Task Exception

Home Assistant release (hass --version):
0.62
Python release (python3 --version):
3.6
Component/platform:
skybell / docker
Description of problem:
Getting this traceback every few seconds or so ..   But the component seems to work.
Expected:
no tracebacks.
Traceback (if applicable):

2018-01-27 21:50:55 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/usr/src/app/homeassistant/helpers/entity.py", line 220, in async_update_ha_state
    device_attr = self.device_state_attributes
  File "/usr/src/app/homeassistant/components/binary_sensor/skybell.py", line 85, in device_state_attributes
    attrs['event_date'] = self._event.get('createdAt')
AttributeError: 'NoneType' object has no attribute 'get'

Additional info:

I'm having the same issue, the camera component is working fine, but the binary_sensor.skybell_front_door_button is not loading.
Looks like others are having a similar problem:
https://community.home-assistant.io/t/binary-sensor-skybell-py/40029
Maybe skybell broke something?
I'm currently running 0.62.1

Same problem here!

same issue here
2018-02-09 15:59:13 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved Traceback (most recent call last):   File "/usr/lib/python3.6/asyncio/tasks.py", line 180, in _step     result = coro.send(None)   File "/usr/local/lib/python3.6/dist-packages/homeassistant/helpers/entity.py", line 220, in async_update_ha_state     device_attr = self.device_state_attributes   File "/usr/local/lib/python3.6/dist-packages/homeassistant/components/binary_sensor/skybell.py", line 85, in device_state_attributes     attrs['event_date'] = self._event.get('createdAt') AttributeError: 'NoneType' object has no attribute 'get'

This error still persists even with the last upgrade. :(   It is just spamming the logs continuously.
2018-02-11 15:58:12 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/usr/src/app/homeassistant/helpers/entity.py", line 220, in async_update_ha_state
    device_attr = self.device_state_attributes
  File "/usr/src/app/homeassistant/components/binary_sensor/skybell.py", line 85, in device_state_attributes
    attrs['event_date'] = self._event.get('createdAt')
AttributeError: 'NoneType' object has no attribute 'get'
2018-02-11 15:58:18 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/usr/src/app/homeassistant/helpers/entity.py", line 220, in async_update_ha_state
    device_attr = self.device_state_attributes
  File "/usr/src/app/homeassistant/components/binary_sensor/skybell.py", line 85, in device_state_attributes
    attrs['event_date'] = self._event.get('createdAt')
AttributeError: 'NoneType' object has no attribute 'get'
2018-02-11 15:58:24 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/usr/src/app/homeassistant/helpers/entity.py", line 220, in async_update_ha_state
    device_attr = self.device_state_attributes
  File "/usr/src/app/homeassistant/components/binary_sensor/skybell.py", line 85, in device_state_attributes
    attrs['event_date'] = self._event.get('createdAt')
AttributeError: 'NoneType' object has no attribute 'get'
2018-02-11 15:58:30 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/usr/src/app/homeassistant/helpers/entity.py", line 220, in async_update_ha_state
    device_attr = self.device_state_attributes
  File "/usr/src/app/homeassistant/components/binary_sensor/skybell.py", line 85, in device_state_attributes
    attrs['event_date'] = self._event.get('createdAt')
AttributeError: 'NoneType' object has no attribute 'get'

As a temp measure, I just commented out the offending line.  You can add this to your custom_component directory to at least get rid of all the spammy errors.
https://github.com/CCOSTAN/Home-AssistantConfig/blob/master/custom_components/binary_sensor/skybell.py#L85

This may be related.
I have 2 Skybell HD Doorbells.
Issue Found:
Second Skybell - Button Sensor does not load
Camera, Both motion sensors, and first Skybell button sensor confirmed working.

Confirmed @CCOSTAN solution works. I found the actual file was here.

Hi @jshank, I'm using docker and I cannot find the correct folder. Could you tell me which was the folder you installed the file in? Thanks

@jolaca01 I am using Docker as well. I was very pleased to find that creating a custom_components/binary_sensor directory under my configuration folder worked to override the offending component. I have my configuration folder mapped below. the full path is ./config/custom_components/binary_sensor/skybell.py (the modified version). I reloaded home assistant and it picked up the new file.
volumes:
       - "./config:/config"

Yes.  Same here.  My docker yaml file can be found here as well.
https://github.com/CCOSTAN/Docker_Support
The custom component works perfectly for me.

Thank you so much, @jshank and @CCOSTAN . I have created the folder ./config/custom_components/binary_sensor/ and placed the modified skybell.py inside. However, after restarting the home assistant container I still get this message once or twice per minute:

Updating skybell binary_sensor took longer than the scheduled update interval 0:00:05
8:40 AM helpers/entity_platform.py (WARNING)

Sorry but what I think I didn't get was the part @jshank told about mapping the folder. Should I include this?:

volumes:
- "./config:/config"

...inside my configuration.yaml?? or where? The problem is that I really don't know what I need to do in docker in order to get the new folder and file recognised. Thank you for bearing with me, sorry guys.
This is my container configuration:

Thanks again!!

@jolaca01 that is a different error message than this patch addresses. The file that @CCOSTAN modified only fixes the Error doing job: Task exception that sets the createdAt attribute. Based on you configuration screenshot, you'll want to copy that file to docker/homeassistant/custom_components/binary_sensor/skybell.py since you are mapping /config to docker/homeassistant.

@jolaca01 - What @jshank said. :)  You don't need to worry about the took too long messages.  If you really want to get rid of those, you can add in a logger.yaml file.  Here's mine :
https://github.com/CCOSTAN/Home-AssistantConfig/blob/master/config/logger.yaml#L33

Thank you again!! @jshank, that's the exact path I've used:   the path I was talking about was from inside the container, but indeed, it is actually located in docker/homeassistant/custom_components/binary_sensor/skybell.py
So I understand I was doing it correctly. However, I thought we were having all the same issue, but I don't think I had this error, only the warning. Is this possible?
Anyway, thank you again, and as @CCOSTAN  suggested I will limit them setting properly my logger file.
BTW, have you read the final part of this thread:
https://community.home-assistant.io/t/skybell-hd-component/21200/23
Skybell support staff seemed willing to help in improving their integration and the problem with the huge delay when the skybell button is pressed till it reflects in the binary sensor. As I see all your knowledge on the subject maybe you could take a look at it or contact Mosses from Skybell support to try improving the current skybell component. Just saying, just in case. ;-)

@CCOSTAN  - would you please confirm where I can grab your modified skybell.py please?   The original link you posted is not working.        Thanks!

@GaryOkie  - It was in my repo (https://github.com/CCOSTAN/Home-AssistantConfig#logo) but I got rid of it at one point after an update.  I no longer have this issue with the latest versions of HA.

@CCOSTAN - That's interesting you no longer have this issue.   I just installed a new Skybell HD a few days ago with Hass.io version 66.1, and don't recall seeing any errors either, but I may not have even looked at the log since the add-on was working fine.
I've updated to Hass.io 67.0 and am getting the following errors.   Aren't they the errors your patched skybell.py addressed, or is it something different now?
``2018-04-15 09:44:54 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 215, in async_update_ha_state
state = self.state
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 379, in state
return STATE_ON if self.is_on else STATE_OFF
File "/usr/lib/python3.6/site-packages/homeassistant/components/switch/skybell.py", line 75, in is_on
return getattr(self._device, self._switch_type)
File "/usr/lib/python3.6/site-packages/skybellpy/device.py", line 206, in do_not_disturb
return bool(distutils.util.strtobool(str(self._settings_json.get(
AttributeError: module 'distutils' has no attribute 'util'

I think this is something new.  I haven't jumped to 0.67 yet though.

Just an FYI that I have submitted a new bug report on this:  #13922 .
Looks like this particular error has cropped up in other components and fixed - refer to #75


How to include the user documentation in the console

How to include the user documentation in the console.
Ex: a "?" icon that opens a popup explaning the graph in more details that just the legend?

Hi, I'm looking for feedback on this task (KIALI-1456).   What kind of format and info are we looking to include?
Here's  the question mark (?) icon next to the Graph title

From the patternfly tour design, maybe there should also be a 'Guided Tour' option in the help menu of the masthead: https://www.patternfly.org/pattern-library/communication/tour/#design

@serenamarie125 @cshinn can you please advise on this one?

From the patternfly tour design, maybe there should also be a 'Guided Tour' option in the help menu of the masthead: https://www.patternfly.org/pattern-library/communication/tour/#design

@mwringe wasn't tour added in https://github.com/kiali/kiali-ui/pull/740?
is this issue still relevant?

@abonas we can close this as it looks like you are ok with what the developers came up with.


No usable progress bar when using fetch stream

STR:

Open the latest version of the PDF.js Chrome extension (v2.0.301) - https://chrome.google.com/webstore/detail/pdf-viewer/oemmndcbldboiebfnladdacbdfmadadm
Visit https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf
To simulate the behavior of the previous published version of the extension, open the debugger and put a breakpoint at the start of content/build/pdf.js (in the main thread) and refresh the page. When the breakpoint is hit, run Response = undefined; to disable fetch and fall back to XHR.

Result:

After step 2, the progress bar is in an indeterminate state.
After step 3, the progress bar grows as expected.

In both cases the Content-Length response header is present, so I would expect a meaningful progress bar.

It appears that this may be related to, or even a duplicate of, issue #9103.

I pinned this bug down to the following:
fetch makes a CORS request by default, so that the response is of type cors instead of basic. Consequently, many headers are not exposed to the JS code. "type" is elaborated here: https://developer.mozilla.org/en-US/docs/Web/API/Response/type
To see the difference, run the following snippet from the console, first in the extension, and then from https://www.adobe.com/favicon.ico (same-origin):
fetch('https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf', {mode:'cors'})
.then(res=>console.log(res, Array.from(res.headers).map(v=>v.join(': ')).join('\n')))

When run from chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf
Response {type: "cors", url: "https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf", redirected: false, status: 200, ok: true, …}
cache-control: max-age=21600
content-type: application/pdf
expires: Tue, 06 Feb 2018 18:29:38 GMT
last-modified: Tue, 06 Feb 2018 01:54:38 GMT

When run from https://www.adobe.com/favicon.ico
Response {type: "basic", url: "https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf", redirected: false, status: 200, ok: true, …}
accept-ranges: bytes
cache-control: max-age=21600
connection: keep-alive
content-length: 55779577
content-type: application/pdf
date: Tue, 06 Feb 2018 12:28:57 GMT
etag: "35320f9-5648176131fc9"
expires: Tue, 06 Feb 2018 18:28:57 GMT
last-modified: Tue, 06 Feb 2018 01:54:38 GMT
server: Apache
strict-transport-security: max-age=900
x-adobe-content: AEM,acom
x-adobe-loc: ew1
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN

Ideally, the fetch API should be called with {mode: 'same-origin'} from the extension, but that seems to be blocked by Chrome.
The next possible things to try is to expose the headers by using the webRequest extension API to augment the Access-Control-Expose-Headers response header.
Or, use the webRequest API to extract these header values directly, by adding a temporary listener for the webRequest.onHeadersReceived event, or via the initial request. I did something in the past for PDF streams on ChromeOS (#4229), perhaps the same logic can also be applied to fetch streams?
(Just thinking out aloud)

This is the bug for exposing "headers" in fetch to extensions:
https://bugs.chromium.org/p/chromium/issues/detail?id=784528


remove redundant cast

ContainerWrapper.download_blob returns bytes, which makes this call redundant.
Found via the latest version of mypy.

This is merged into #408

This is merged into #408


Live

Test PR

Docs Build status updates of commit 5e5d2d3:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[fix] Circular json error for LoggingInterceptor with useGlobalInterceptors

Sometimes there is a problem with using useGlobalInterceptors when the object has a complex structure
I had a circular json error for graphql subscriptions using redis
I just add a function to "break" the circularity and show the values

What about using instead of fast-safe-stringify?, it takes cares of circular stuff
https://github.com/davidmarkclements/fast-safe-stringify#readme

Please check a possible generic solution which prevent logging extra information for circular referenced object using replacer:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/Cyclic_object_value
Possible solution:
const getCircularReplacer = () => {
  const seen = new WeakSet();
  return (key, value) => {
    if (typeof value === "object" && value !== null) {
      if (seen.has(value)) {
        return;
      }
      seen.add(value);
    }
    return value;
  };
};

JSON.stringify(circularReference, getCircularReplacer());

Yes surely a better solution to do it like that
On the other hand I encounter the problem of circular JSON when connecting by WebSocket
The only place I have found to sort this out is here because it is not related to my code but to the ws connection:
 return next.handle().pipe(
      tap({
        next: (value) => {
          this.logger.log(`${JSON.stringify({ Response: value })}`); <= Here
        },
      }),
    );
``

What about using instead fast-safe-stringify?, it takes cares of circular stuff
https://github.com/davidmarkclements/fast-safe-stringify#readme

Great this package I did not know, it solves my problem


Need guidance on proper use of rows.StructScan() for a "has many" join

This is a fantastic package but I must misunderstand how to use rows.StructScan() for a has many join.
My database features a typical has many relation where my element_anchors table has element_id FK pointing to the PK in elements table. Each Element record has a handful of ElementAnchor records.
Models:
type Element struct {
	Cmod           string          `json:"cmod"`
	Name           string          `json:"name"`
	IDescription   string          `json:"description" db:"i_description"`
	ElementAnchors []ElementAnchor `json:"anchors"`
}

type ElementAnchor struct {
	Statement string `json:"statement"`
	Level     int    `json:"level"`
	ElementID int    `json:"-" db:"element_id"`
}

Relevant query stuff:
sqlStatement := `SELECT
e.cmod, e.name, e.i_description, ea.statement, ea.level
FROM elements e
	INNER JOIN element_anchors ea
	ON e.id = ea.element_id
ORDER BY e.cmod;`

rows, err := db.Queryx(sqlStatement)

Relevant row scanning stuff:
elements := make([]Element, 0)
for rows.Next() {
	var e Element
	err = rows.StructScan(&e)
	if err != nil {
		log.Fatalf("Scan error: %s\n", err)
	}
	elements = append(elements, e)
}

To clarify, my objective is this JSON structure:
[{
"cmod": "a cmod",
"name": "a name",
"description": "a description",
"anchors": [{
	"statement": "a statement",
	"level": 42
    }, {
	"statement": "another statement",
	"level": 84
    }]
},{
 <more like the above>
}]

I've searched open and closed issues and studied the Illustrated Guide to SQLX but have not found sufficient guidance for what I imagine is a common use case. I am unsure if my problem is within the Models, the query or within the StructScan or??

The resulting SQL rows will look like:
|  cmod  |  name  |  description   | statement   | level |
| a cmod | a name | a description  | a statement |   42  |

Your struct will have to match this format, you can achieve this by embedding:
type CombinedElement struct {
   Element
   ElementAnchor
}

One recommendation is to use the canonical name of the column, i.e. table_name.column_name during joins to avoid ambiguity in case two or more tables have a column with the same name:
SELECT
  e.cmod AS 'element.cmod',
  e.name AS 'element.name',
  e.i_description AS 'element.i_description',
  ea.statement AS 'anchor.statement',
  ea.level AS 'anchor.level',
FROM elements e
JOIN elements_anchors ea
  ON e.id = ea.element_id
ORDER BY e.cmod;

Then you would use this prefixes as the db tag in the combined struct:
type CombinedElement struct {
   Element       `db:"element"`
   ElementAnchor `db:"anchor"`
}

You can scan the result rows into a slice of CombinedElement, then map the result into an Element by collecting all anchors of an element:
var rows []CombinedElement
// query and scan into rows here

// Collect all anchors belonging to the same element in a single slice
anchorsByElementID := make(map[int][]ElementAnchor, 0)
for _, row := range rows {
   anchorsByElementID[row.Element.ID] = append(anchorsByElementID[row.Element.ID], row.ElementAnchor)
}

// construct our actual result
var res []Element
for _, row := range rows {
  row.Element.ElementAnchors = anchorsByElementID[row.Element.ID]
  res = append(res, row.Element)
}

You could probably do it in a single pass over rows by indexing pointers to Element.

Thank you very much @yousseftelda for the response, however I can't make this work.
I've added the third struct as recommended:
type Element struct {
	Cmod         *string `json:"cmod"`
	Name         *string `json:"name"`
	IDescription *string `json:"description" db:"i_description"`
}

type ElementAnchor struct {
	Statement string  `json:"statement"`
	Level     float64 `json:"level"`
}

type CombinedElement struct {
	Element       `db:"elements"`
	ElementAnchor `db:"element_anchors"`
}

I've reformatted the query:
(My table names are plural, lower case)
	sqlStatement := `SELECT
		e.cmod AS "elements.cmod",
		e.name AS "elements.name",
		e.i_description AS "elements.i_description",
		ea.statement AS "element_anchors.statement",
		ea.level AS "element_anchors.level"
	FROM elements e
	JOIN element_anchors ea
		ON e.id = ea.element_id
	ORDER BY e.cmod;`

I've initialized the variables as per your response and issued the query:
	var rows []CombinedElement
	var err error

	rows, err = db.Queryx(sqlStatement)

Unfortunately, I have a complier error:
cannot assign *sqlx.Rows to rows (type []CombinedElement) in multiple assignment
As you stressed the order of the 5 rows across the two tables aligns. Accordingly, I'm unsure what to do with this multiple assignment error.

db.Queryx returns sql Rows, what we want is to map the sql Rows into our slice of CombinedElement, to achieve this you can use:
var rows []CombinedElement
if err := db.Select(&rows, sqlStatement); err != nil {
  // handle err
}

// rest of the logic

db.Select is doing a db.Queryx under the hood, followed by scanning the result into the passed pointer.

Success!
Thank you again @yousseftelda for the kind assistance. Your inputs, plus a couple of lessons learned have helped me wrap my head around how to handle has many joins with SQLX. In case this can help others, here are some basic rules of thumb I'll use going forward:
Lessons I learned include:

The query rows returned must align with the three structs (pretty obvious!)
db.Select does a great job of filling the "parent struct" providing a set of scannable rows. (Thank you @jmoiron, I see now the fantastic power of StructScan!)
The rows which are scanned must include necessary PK and FK in order for SQLX to properly associate related records. (This was key for me:, I needed to add Element.ID and ElementAnchor.ElementID to the query in order to properly map the ElementAnchor rows to the Element.)

The Stucts with the addition of PK, FK:
type Element struct {
	ID           int     `json:"-"`
	Cmod         *string `json:"cmod"`
	Name         *string `json:"name"`
	IDescription *string `json:"description" db:"i_description"`
	ElementAnchors []ElementAnchor `json:"anchors"`
}

type ElementAnchor struct {
	Statement string  `json:"statement"`
	Level     float64 `json:"level"`
	ElementID int     `json:"-" db:"element_id"`
}

type CombinedElement struct {
	Element       `db:"elements"`
	ElementAnchor `db:"element_anchors"`
}

The revised query (with PK, FK) to produce rows that align with the above:
	sqlStatement := `SELECT
		e.id AS "elements.id",
		e.cmod AS "elements.cmod",
		e.name AS "elements.name",
		e.i_description AS "elements.i_description",
		ea.statement AS "element_anchors.statement",
		ea.level AS "element_anchors.level",
		ea.element_id AS "element_anchors.element_id"
	FROM elements e
	JOIN element_anchors ea
		ON e.id = ea.element_id
	ORDER BY e.cmod;

Having added the Element.ID and ElementAnchor.ElementID, the two stage scanning as you outlined worked perfectly. Viewing the relevant source, I see the role StructScan plays. Good stuff!

An update: The result was containing duplicate Elements.
With the two loops, each Element is added to result multiple times.
The desired result is:

Element 1, (Anchors 1.1 , 1.2, 1.3)
Element 2, (Anchors 2.1, 2l2, 2.3)
...

But the result has duplicated Elements:

Element 1, (Anchors 1.1 , 1.2, 1.3)
Element 1, (Anchors 1.1 , 1.2, 1.3)
Element 1, (Anchors 1.1 , 1.2, 1.3)
Element 2, (Anchors 2.1, 2l2, 2.3)
Element 2, (Anchors 2.1, 2l2, 2.3)
Element 2, (Anchors 2.1, 2l2, 2.3)
...

The solution was checking for duplicates and conditionally appending:
	var res []Element
	for _, row := range rows {
		row.Element.ElementAnchors = anchorsByElementID[row.Element.ID]

		// if we have not seen this Element, add it to our result
		if _, exists := duplicateChecker[row.Element.ID]; !exists { // this ID doesn't exist, add it to res.
			// add the element to the map
			duplicateChecker[row.Element.ID] = struct{}{} // set up for next time through the loop
			res = append(res, row.Element)
		}
	}

Mark. A helpful issue for me.


Update JS flags representation

Updates the representation of flags in JS to match the component model explainer.
Previously, flags were represented as bitfields in JS. This PR changes them to be represented as objects with boolean fields for each flag instead, matching the component model explainer.

Got the merge order right this time which makes this view much cleaner. Again sorry I forgot about this!


[FEATURE] add content to the create project API [BE]

Description
Requirement:
We are adding new field called content to the create project submit form. For that we need to update our existing create project API.
FYI the content field will be markdown.

Can you assign me?

Hey can I work on this issue?

@rohitdasu if this issue is still not taken I can work on this.

@rohitdasu if this issue is still not taken I can work on this.

sure

@rohitdasu pls assign this to me

done @titusjoyson


Not downloading the model

[whisper-node] Enter model name (e.g. 'base.en') or 'cancel' to exit
(ENTER for base.en):
[whisper-node] Going with base.en
Downloading ggml model base.en...
Invoke-WebRequest : Invalid username or password.
At line:1 char:1
+ Invoke-WebRequest -Uri https://huggingface.co/datasets/ggerganov/whis ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
Failed to download ggml model base.en
Please try again later or download the original Whisper model files and convert them yourself.
[whisper-node] Attempting to compile model...
'make' is not recognized as an internal or external command,
operable program or batch file.

wrong link in ./node_modules/whisper-node/lib/whisper.cpp/models/download-ggml-model.sh (line 9)
src="https://huggingface.co/datasets/ggerganov/whisper.cpp"

it should be:
src="https://huggingface.co/ggerganov/whisper.cpp"

Any updates?

When trying to download the model:
[whisper-node] Attempting to compile model...
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:4: pipe: No error
process_begin: CreateProcess(NULL, uname -p, ...) failed.
Makefile:8: pipe: No error
process_begin: CreateProcess(NULL, uname -m, ...) failed.
Makefile:12: pipe: No error
process_begin: CreateProcess(NULL, which nvcc, ...) failed.
Makefile:16: pipe: No error
'cc' is not recognized as an internal or external command,
operable program or batch file.
'head' is not recognized as an internal or external command,
operable program or batch file.
I whisper.cpp build info:
I UNAME_S:
I UNAME_P:
I UNAME_M:
I CFLAGS:   -I.              -O3 -DNDEBUG -std=c11   -fPIC -D_XOPEN_SOURCE=600 -pthread
I CXXFLAGS: -I. -I./examples -O3 -DNDEBUG -std=c++11 -fPIC -D_XOPEN_SOURCE=600 -pthread
I LDFLAGS:
I CC:
I CXX:

cc  -I.              -O3 -DNDEBUG -std=c11   -fPIC -D_XOPEN_SOURCE=600 -pthread   -c ggml.c -o ggml.o
process_begin: CreateProcess(NULL, cc -I. -O3 -DNDEBUG -std=c11 -fPIC -D_XOPEN_SOURCE=600 -pthread -c ggml.c -o ggml.o, ...) failed.
make (e=2): The system cannot find the file specified.
make: *** [Makefile:299: ggml.o] Error 2


[UI] Plan Selector

Overview
ui plans
A view for presenting choices between pricing plans for a website.
Content

Plan: A group of plans can contain individual plan choices
Features: A plan can contain a list of features
Action: A plan can contain a button linking to a follow up action

Types

Vertical: A plan picker that is formatted vertically to show lists of options in a table

Variations

Size (Plans): A plan picker can vary in size
Featured (Plan): A plan can be featured to show it is the emphasized plan choice

Examples
https://proto.io/en/signup/
http://useqwitter.com/
http://demo.designwall.com/dw-simplex/?page_id=493
http://www.trunkclub.com/features
http://bootsnipp.com/snipps/pricing-table-example
http://bootsnipp.com/snipps/crowdfunding-grid

So waiting for this!

:+1:

+1

+1

http://codepen.io/alirezaaa/pen/rabbQG

+1
I like this one https://proto.io/en/pricing/, really in the spirit of semantic

When will we be able to see this?

+1 yes please

Is it coming?

http://codepen.io/j-w-v/pen/DIcJx

:+1:

:100:

+1

I created an example with cards, labels and dividers:
https://codepen.io/romanzipp/pen/XKvGXz

@romanzipp Looks awesome! :smile_cat:

@romanzipp Looks great! I've added .link class to the cards, so it more interactive with user

There's also this one: https://codepen.io/caiosantossp/pen/vNazJy
It would be great if this was built into Semantic-UI though.

I just made my own with a UI grid, Statistic and Segments. Very easy.
https://codepen.io/rlingineni/pen/vRrpmq/


Don't pass the annotations and labels to the managed resources

Removed the patchsets that pass all annotations and labels
Removed patchset functions as they provide not much benefit when using jsonnet

This removes the user's ability to set any annotations and labels on the managed resources. This resolves security problems with the external-name.
Resolves #92
Checklist

[X] The PR has a meaningful title. It will be used to auto generate the
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
[X] PR contains a single logical change (to build a better changelog).
[X] Update the documentation.
[X] Categorize the PR by adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.
[X] Link this PR to related issues or PRs.

looks ok


CAMEL-11074: Unable to load Schematron XSLT templates on windows

https://issues.apache.org/jira/browse/CAMEL-11074

Thanks for the PR it has been merged. Do you mind closing this?

Thanks!


Storyboards can't find styles all of a sudden

This happened all of a sudden, everything was working fine before. All of the components in the storyboard are now red (which I'm used to seeing when it can't find the style). The project doesn't appear to have any errors and I've tried trimming down the styles file to rule out any errors in it, but nothing works. Is there any way to debug why this may be happening?
I should note that when I run the application it shows all the styles just fine. If I start a fresh project or open the Stylish example project, the storyboards display styles just fine.

Hi Matthew — thanks for reporting this issue!  My initial suggestion is to see if this is just an intermittent issue with IBDesignable in Xcode (which I’ve noticed can be flaky sometimes).  Have you tried:

Clear derived data / clean build folder
Quit and restart Xcode
Build and run your app target
Go to your storyboard and select Editor -> Refresh All View

These steps will often get IBDesignable back into a good state.  If you still encounter the same issue after those steps, it is usually due to the stylesheet not being loaded during the IBDesignable phase, perhaps because of missing the prepareForInterfaceBuilder() extensions on UIView & StyleableUIView/Label/Button shown in the sample project, or an issue locating or loading the stylesheet.json.
Let me know if none of these ideas resolve your issue or if you have any follow up questions!

OK, this ended up being my own issue, but it's great knowledge for others. I had a private framework that I had only compiled for ARM devices, not a universal framework that included x86 for simulators.
I assume that for some reason Interface Builder requires your project to compile fully for simulator to be able to properly render Stylish styles.

Ah yes!  Storyboard previews are rendered in the simulator under the hood.  Thanks for sharing the resolution.


Are there any detailed tutorials available? I would like to add some interactive components like element plus and naiveui. Thank you

Describe the feature
Are there any detailed tutorials available? I would like to add some interactive components like element plus and naiveui. Thank you
Relevant code
No response

There are the basic tutorials on the website, such as the tic-tac-toe tutorial. There is also the basics section on the website, in addition to the advanced section, which might have some useful information for you.
If none of those pages have the information you need, I would be glad to give you tips on whatever you are trying to do. I am also planning to improve the advanced section soon (#1082).


Minor: F5 Couldn't get key from code: BrowserHome

Trivial loose end.
Pressing F5 to tempt a page refresh in tauri window, spawns x3 messages to terminal as
Couldn't get key from code: BrowserHome
Would expect unavailable behaviour to produce null. So, unclear if there is a behaviour not working as wanted.

$ cargo tauri info
Operating System - Linux, version 19.3 X64
Node.js environment
Node.js - 17.1.0
@tauri-apps/cli - 1.0.0-beta.10
Global packages
npm - 8.1.2
yarn - Not installed
Rust environment
rustc - 1.56.1
cargo - 1.56.0

Are you using menus with accelerators ? do you have a non usual keyboard or something ? Also please run xev command in a terminal and press F5 while focusing xev window and get me the output .

The only oddity I'm aware of is being via vncviewer but I can't see why that would be a factor.
xev gives
MotionNotify event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (168,2), root:(763,296),
    state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,2), root:(764,296),
    state 0x0, is_hint 0, same_screen YES

KeyPress event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,2), root:(764,296),
    state 0x0, keycode 180 (keysym 0x1008ff18, XF86HomePage), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,2), root:(764,296),
    state 0x0, keycode 180 (keysym 0x1008ff18, XF86HomePage), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,2), root:(764,296),
    state 0x0, keycode 180 (keysym 0x1008ff18, XF86HomePage), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,2), root:(764,296),
    state 0x0, keycode 180 (keysym 0x1008ff18, XF86HomePage), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,2), root:(764,296),
    state 0x0, keycode 180 (keysym 0x1008ff18, XF86HomePage), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,2), root:(764,296),
    state 0x0, keycode 180 (keysym 0x1008ff18, XF86HomePage), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

MotionNotify event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,1), root:(764,295),
    state 0x0, is_hint 0, same_screen YES

MotionNotify event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,0), root:(764,294),
    state 0x0, is_hint 0, same_screen YES

LeaveNotify event, serial 38, synthetic NO, window 0x3c00001,
    root 0x17c, subw 0x0, time<PHONE_NUMBER>, (169,-1), root:(764,293),
    mode NotifyNormal, detail NotifyAncestor, same_screen YES,
    focus YES, state 0

ClientMessage event, serial 38, synthetic YES, window 0x3c00001,
    message_type 0xee (WM_PROTOCOLS), format 32, message 0xef (WM_DELETE_WINDOW)

This doesn't seem right, the logs shows you are pressing a different key,F5 has key code of 71 while your logs have 180, perhaps you have F5 remapped to another key ?

It seems I do!.. checking in a normal browser I see the laptop is doing some BrowserHome = default browser page instead. Perhaps more of a user error oddity then.


Messaging: should polling time be included in duration of "receive" spans

See https://github.com/open-telemetry/opentelemetry-demo/pull/1538
The messaging semantic conventions describe "Receive" operations as follows:

"Receive" spans SHOULD be created for operations of passing messages to the application when those operations are initiated by the application code (pull-based scenarios).

However, those operations initiated by the application code can include time for polling messages. It needs to be confirmed whether it is desirable to include the polling time in "Receive" durations.
For example, Consume  on an auto-instrumented .NET Kafka client is called. This call blocks until a message is available. If it takes 10 minutes until a message is available, this results in a "Receive" operation with a duration of 10 minutes. As the .NET Kafka auto-instrumentation retroactively sets the start time of a "Receive" span to the time when the Consume call was made, this can result in a "Receive" operation that starts before the corresponding "Publish" operation, which can be misleading for users.

There should be then polling idle time metrics, otherwise the change is going to reduce information amount... and I think this is still important metric to fine tune polling time.

This was discussed in the messaging workgroup.
This is how "Receive" spans are described in the semantic conventions:

"Receive" spans SHOULD be created for operations of passing messages to the application when those operations are initiated by the application code (pull-based scenarios).

This makes it clear that the span refers to the operation as initiated by the application code. In the current example it means that the polling time should be included in the duration of the receive span.
To avoid misleading traces, the "Receive" span shouldn't be a child of the corresponding producer span, but it should be a link:

For each message it accounts for, the "Process" or "Receive" span SHOULD link to the message's creation context.

Messaging instrumentations can create additional parent/child relationships, however, that's either mandated nor recommended by semantic conventions. As it yields sub-optimal results in this case, there should only be link.
Possibly parent/child relationships could be added as an opt-in capability, similar to how it's done here.


The callback to Builtin.once is a C function, not a Swift one

If we want it to be a Swift function, we'll have to thunk in the
runtime when using a system implementaton like dispatch_once_f,
since the function pointer ABIs could be different, depending on
the target.  Dealing with that, or avoiding it on a per-target basis,
is more complexiity than a micro-optimization of the slow path of
this builtin could possibly be worth.

@swift-ci Please test.

Build failed
Swift Test Linux Platform
Git Sha - b808ba349875b6d26bd09f11a9941eae6438d329

Build failed
Swift Test OS X Platform
Git Sha - b808ba349875b6d26bd09f11a9941eae6438d329

@swift-ci Please test.

Build failed
Swift Test OS X Platform
Git Sha - b808ba349875b6d26bd09f11a9941eae6438d329

Build failed
Swift Test Linux Platform
Git Sha - b808ba349875b6d26bd09f11a9941eae6438d329


Update UnoApplicationTemplate packages to latest stable version + quick fixes

PR Type
What kind of change does this PR introduce?

Bugfix

Description
I've basically updated UnoApplicationTemplate packages to latest version which means the following:

Update firebase sdk to latest stable version (without fabric)
Update several packages to its latest stable version

I also did fix bugs that I've found while working on a project which started from this template

FirebaseHandler was crashing for specific request (POST), because the request is disposed after it's completed
Cannot build on iOS, because AddFirebaseHandler does not return something on other platform

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Interface members are XML documented
[ ] Documentation (XML or comments) has been added and/or existing documentation has been updated
[ ] Architecture documents have been updated
[x] Tested on all relevant platforms

Other information

Internal Issue (If applicable):

I saw a new UI bug on android. I think it may be related to the version of Uno. To be validated

I saw a new UI bug on android. I think it may be related to the version of Uno. To be validated

I saw a new UI bug on android. I think it may be related to the version of Uno. To be validated

I don't see this bug on 3.4.0. I don't see any new bugs either so that's why I'm updating to this version instead
CC @MatFillion @jcantin-nventive

I saw a new UI bug on android. I think it may be related to the version of Uno. To be validated

I don't see this bug on 3.4.0. I don't see any new bugs either so that's why I'm updating to this version instead
CC @MatFillion @jcantin-nventive

don't forget to update other nventive package before merging

don't forget to update other nventive package before merging


typo in env var BACKUP_GLOBALRESTORES3ACCESKEYID

There's an s missing in the Acces*s* part. Unsure what implications this has, but might be unpleasant 😄

🤦♂
Well fixing that one would probably break a few operator configurations. But if we mark it in the changelog as a breaking change it should be fine.

Won't do, will be fixed in #121

While testing I found that this typo doesn't seem to be in the legacy K8up releases. So we should fix it or we'll actually break backwards compatibility :D

Can confirm it: https://github.com/vshn/k8up/blob/v0.1.10/config/global.go#L43
However, the documentation states otherwise: https://github.com/vshn/k8up/blob/v0.1.10/docs/modules/ROOT/pages/advanced-config.adoc

This is fixed now in master, it was a documentation issue.
The config refactoring itself is in a separate PR


Custom instruction

How I can link my custom gpt assistant for line chat ? Because chatgpt doesnt know my product info what kinda solution is there any?

Hi
You can use APP_INIT_PROMPT env key and set your instructions as value.
Ref: https://memochou1993.github.io/gpt-ai-assistant-docs/en/environments.html


Minor server cleanup

Pulling out some minor server cleanup from this PR: https://github.com/medplum/medplum/pull/1350

Coverage: 93.739% (-0.0004%) from 93.74% when pulling ffc9eeab02a34f3bfa2ae9dab8f2a880732687f2 on cody-minor-server-cleanup into 61f7b3c90494a0e49647c7623ad6b5b219312bef on main.


can we add tool tip on uproxy app ?

a proper tool tip can make uProxy app more user friendly, @zahoriea  any thoughts ?

One of the user said he do not understand what this button do ( when he was getting access ) on the UI , it hides the user list , a tool tip would say what this button do before he clicks :)

Which button? Please elaborate this in the bug description above; and maybe add a screenshot? Thanks!

closing this since tool tip has been implemented .


CXXCBC-517:  Add HTTP session retries

Motivation
The client does not currently attempt to retry if the HTTP session fails to resolve or connect.  Adding retries will help to improve user experience.
Changes

Add retries if resolve or connect fails.
If connect fails, and resolve provided multiple endpoints, attempt to connect to next endpoint in list of provided endpoints.
If ping() fails due to resolve/connect issue, list "attempted" hostname and port in remote_address property of endpoint_ping_info

I will update CXXCBC-517 tomorrow w/ details from my testing.


Feature Request: AdaDelta optimizer

AdaDelta (http://arxiv.org/abs/1212.5701) is a popular training algorithm for Neural Network. It is available in most other libraries I have used, like Torch or chainer.
In my small personal experience (and at least for the Neural Networks I have used), AdaDelta is often the optimizer that works best out of the box (RMSProp working quite well as well, while Adam, Adagrad and SGD typically being not as good)
Therefore, it would be nice if AdaDelta could be added to the set of available optimizers.

I tried to give it a shot in this branch
I tried to follow as much as possible the paper and the other training operations, but as Is my first tensorflow operator I would like some feedback and guidelines if anyone has time to review the code.

@martinwicke I think we can close this issue. The adadelta operator is in the codebase

thank you!


custom label in package.json config

I have greenkeeper enabled on a few public repos and it works well, but the issues and PRs use a greenkeeper label that doesn't fit with my other labels. The rest are conventionally named with a category and standard-commit tag, like type-deps, type-feat, status-fixed, etc.
The docs show ways to customize the commit and PR messages, but I don't see a way to use a different label. Is that supported, or if not, would it be possible?

Hi @ssube, just found this comment: https://github.com/greenkeeperio/greenkeeper/issues/153#issuecomment-232732350
Customizing the label is already possible, however, there is no documentation for it.


Failed to resolve System.String SQLitePCL.raw::sqlite3_column_name(SQLitePCL.sqlite3_stmt,System.Int32)

Xamarin.Forms, using Microsoft.Azure.Mobile.Client.SQLiteStore, version 4.1.1 and SQLitePCLRaw.core version 2.0.0, build in Release mode causes exception:
error MSB4018: Mono.Linker.MarkException: Error processing method: 'Newtonsoft.Json.Linq.JObject Microsoft.WindowsAzure.MobileServices.SQLiteStore.MobileServiceSQLiteStore::ReadRow(Microsoft.WindowsAzure.MobileServices.SQLiteStore.TableDefinition,SQLitePCL.sqlite3_stmt)' in assembly: 'Microsoft.Azure.Mobile.Client.SQLiteStore.dll' ---> Mono.Cecil.ResolutionException: Failed to resolve System.String SQLitePCL.raw::sqlite3_column_name(SQLitePCL.sqlite3_stmt,System.Int32) [/Users/vsts/agent/2.155.1/work/1/s/ScsNtClient/Client.Droid/Client.Droid.csproj]

SQLitePCLRaw 2.x is not compatible with Azure Mobile Apps.  You should stay with 1.1.14.

Hello Eric,
thanx for your answer, but in our solution we use following packages
SQLitePCLRaw.provider.e_sqlite3
SQLitePCLRaw.provider.dynamic_cdecl
these packages have no version 1.1.14 available in nuget.org repo anymore, and they have dependency set to SQLitePCLRaw.core (>= 2.0.0)
Any suggestion?

Those probably showed up when you tried to upgrade SQLitePCLRaw to 2.0.  Those packages IDs were new in 2.0 and never existed as part of 1.1.14.
(That probably means you are using packages.config -- life is much better if you get rid of that and switch to PackageReference, which handles transitive dependencies much better.)
Assuming you have some kind of version control, you should diff your packages.config file against the version before you tried to upgrade SQLitePCLRaw to 2.0.

I just removed SQLitePCLRaw.provider.e_sqlite3 and SQLitePCLRaw.provider.dynamic_cdecl from solution, then downgraded SQLitePCLRaw.bundle_green to version 1.1.14 and during build I got following
Can not resolve reference: SQLitePCLRaw.provider.e_sqlite3, referenced by SQLitePCLRaw.batteries_green. Please add a NuGet package or assembly reference for SQLitePCLRaw.provider.e_sqlite3, or remove the reference to SQLitePCLRaw.batteries_green.	Client.Droid
I wanted to add SQLitePCLRaw.provider.e_sqlite3 again but in repo is only version 2.x, which requires SQLitePCLRaw.core 2.x, which is not compatible with Microsoft.Azure.Mobile.Client.SQLiteStore

Was this working before you tried upgrading SQLitePCLRaw to 2.0?  You just need to get back to that state.
One option is to remove all the SQLitePCLRaw packages and the Azure mobile apps packages and then re-add the Azure Mobile App package, and it will add just the dependencies it needs.
If you post your packages.config file here I can take a look at it.

thanks for answer, I'll get back to this issue next week, then I'll let you know

@ericsink Any idea when the dependency will be updated? and thank you for the solution! I saw the other post about the current contributor falling off.

@lazmeister Can you make that question more specific?  Which dependency?

@lazmeister Can you make that question more specific? Which dependency?

Sorry, this might pertain to Azure mobile client dependency. We were getting link assemblies error until we downgraded to 1.1.14 SQLitePCLRaw packages.

Ah, yes.  I rather doubt that Azure Mobile Apps will be updated for compatibility with SQLitePCLRaw 2.x.  I have gotten the impression that the Azure Mobile Apps libraries are no longer being actively developed.
See the README on their main page:
https://github.com/Azure/azure-mobile-apps

Yes sadly. Thank you anyway

I encountered this issue also in a Windows Console app after updating SQLitePCLRaw.bundle_green to v2.0.2.    Creating a new Windows Console app and upgrading to v1.1.14 cleared up all errors and work great.  Does this mean that I should not upgrade the SQLite packages beyond v1.1.14?

@tebo02 I can't answer that question without more info.  What packages got installed?  What errors?  etc.
Version 2.x contained some breaking changes from 1.1.14, so the upgrade does need to be done carefully in many cases.

Closing old/stale issue.


update Meteor support

Since Meteor has already drop Npm.require style (Deprecate Npm.require in favor of import/require #6464)
So In file src/15utility.js, all 'fs = Npm.require('fs')' should be replaced with 'fs = require('fs')'

Thanks for fixing this bug. Wiki is ok, I use Alasql with meteor just as wiki's instruction.


Dev environment

Hi!
I don't know how you normally develop in PgCat, but I found it a bit cumbersome when I had to debug a ruby test that was failing. Running the entire test suite using the tests/docker docker-compose file is simple, but when you encounter an issue, fixing it is not as easy as it could be, mainly because:

PgCat id compiled from scratch every time you run the tests
Postgres dbs are also set up every run
Ruby gems are also downloaded
There is a chicken egg issue in the docker-compose because postgres dbs need to use the main network, so if you want to leave postgres containers running and rerun main to test changes, it won't work most of the times.

I understand that those heavily developing in this project have all these things set up in their own boxes, but I did want to have a development environment close enough to the test one so I can debug issues easier.
This PR adds a simple dev environment that works by running:
./dev/script/console

This leads you to a container similar with what is used in CI, but ENV vars configured to save build artifacts and ruby gems  into dev/cache directory, so removing this container and running it again won't delete those files, making it faster to do test driven development. As the cache directory is inside dev it does not interfere with what you have outside.
A run example would be like:

In the end, this change is just a new docker-compose file and some bash configuration so the user running inside the container shared UID:GID from that running in the host, also, the container has strace, ngrep, psql and some networking tools to make it easier debugging.
Using it, I actually spotted the bug I was hitting in like minutes, instead of the 3 hours wasted before.

This is really great, thank you for building this!


Open sourcing the model?

I've noticed that for Replicate the model version is hard-coded. Is there any chance to release the model, so that I can push my own version? Or is it a public model only?

It's a public model on Replicate called ControlNet!


"--config mkl" => mkl_version.h: No such file or directory

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Red Hat Enterprise Linux 7.6
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source
TensorFlow version: master
Python version: 3.6
Installed using virtualenv? pip? conda?: N/A
Bazel version (if compiling from source): 0.26.1
GCC/Compiler version (if compiling from source): 8.2.1
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the problem
Building TF master with "--config mkl" fails because it is looking for Intel MKL (not MKL-DNN).
Provide the exact sequence of commands / steps that you executed before running into the problem
bazel build --config opt --config mkl //tensorflow/tools/pip_package:build_pip_package
Any other info / logs
In file included from external/mkl_dnn/src/cpu/rnn/ref_rnn.hpp:28,
from external/mkl_dnn/src/cpu/rnn/cell_gru_lbr.cpp:24:
external/mkl_dnn/src/cpu/rnn/../gemm/os_blas.hpp:33:10: fatal error: mkl_version.h: No such file or directory
#include "mkl_version.h"
^~~~~~~~~~~~~~~
compilation terminated.
Note that mkl_version.h is an Intel MKL header, not an MKL-DNN header. It looks like the current MKL-DNN binary blob requires MKL by default.

Update:
If I add these lines (back) to .bazelrc:
build --spawn_strategy=standalone
build --strategy=Genrule=standalone

...my build works again.
(Somehow, the "mkl_linux" tree does not make its way into processwrapper-sandbox. I do not know enough about Bazel to understand what the underlying problem is here.)

It looks like commit 7a2ce469a70e55855b09030a96d2f6eeb825e253 is the reason for this issue.

@nhasabni Thanks. So you could reproduce the problem? I was not sure whether it was somehow my environment.
P.S. Could I convince you to take a peek at (the unrelated) issue 30383 ?

@plopresti Yes we could reproduce the issue. Also, for 30383, we are looking into it.

@plopresti, can you confirm if you are still experiencing this issue? BTW  #30383 is fixed in 1.15

@preethivenkatesh This issue is resolved.
Initial testing on #30383 looks good; we are trying other cases and will update soon. Thanks!


Help link

Fixes #1392
Duplicate #1458 just redirected to a new branch
@satu0king there was no conflict so I moved the same pr.

@shubhankarsharma00 , the new UI uses code in public/src. Also add this as a custom shortcut please. Thanks!

👀 I knew I was forgetting something. On it.

@satu0king this is done and working fine.

Merged via #1743


Implement CLI adapter for config store

For debugging purposes, we need a CLI adapter to directly manipulate the config store. This should be a simple tool that talks directly to the same store backend as Pilot components with minimal processing. All the user-facing work should instead be done on istio/galley as part of the new config backend/frontend.

cc @sebastienvas @frankbu
I'll call it autopilot (credits to @douglas-reid )


[vm/ffi] Write test for behavior of allocation of size-0 structs.

Currently, it might succeed or throw an exception, depending on the behavior of malloc.

https://github.com/dart-lang/sdk/issues/37250 changes the Pointer.allocate() semantics to be consistent with malloc as well.
Semantics are malloc(sizeOf<T>() * count) where count and T are the argument and type argument passed to Pointer.allocate.
So I think the current semantics are fine.
We should probably add a test which is similar to https://dart-review.googlesource.com/c/sdk/+/107503/3/tests/ffi/data_test.dart

I'm fine with the current semantics.

Obsolete after https://github.com/dart-lang/sdk/issues/37265


Bump a new version

Is it possible to release a new version? The master brunch has the changes we need.

@gilv ^^

@sergii-mamedov @JosepSampe sorry for delay. will handle it

@gilv I think you can already move it to v3.0.0 due to the huge amount of additions and changes, and new Python3.11 support.

@gilv Any updates?

@gilv can you please follow up on this and release the new version? Thank you very much!

@theodev @JosepSampe @sergii-mamedov done

Thank you @gilv !


Provide a big endian example

Right now, we fill up our inner field from the right, i.e.
struct A {
  a: u2,
  b: u16,
  c: bool
}
let a = A::new(1, 2, true);

will be saved as: 0b1_00000000_00000010_01 on little endian and afaik 0b1_00000010_00000000_01 on big endian.
Since we get/set the whole field, this should just work.
So, provide an example for big endian (implement an actual usecase).

@hecatia-elegua Hello! I came across this crate recently and it looks nice & tidy.
Kudos for all your hard work in documenting and actually creating this.
Big endian reading (left to right, Msb to Lsb) would be very useful indeed.
Being a successor for modular-bitfield in a way that this can be swapped in, in binread would be perfecto.

@v1gnesh hey, thank you :)
I would love to support it, but need to see usecases on what is exactly wanted.
Where does it need to be handled inside bilge?
See also: https://www.reddit.com/r/rust/comments/13ic0mf/comment/jkc1fq9/
Most useful would be if you'd use bilge in a project with BE, fiddle around if it doesn't work and report it here.
Besides that, linking to some spec document with BE fields which won't work under bilge would be cool.

It's for use in reading a file... like this.
What happens with mo bi is that the bits are in reverse (Msb and Lsb positions).
So I either have to define the struct fields in reverse, or serialize them in reverse in order to get it in the 'correct' order.

and that's unefficient? got it.
from the binrw usage example:
let mut reader = Cursor::new(b"DOG\x02\x00\x01\x00\x12\0\0Rudy\0");
let dog: Dog = reader.read_ne().unwrap();

would .read_be() work here for bilge?

I have #[br(big)] coded atop my main struct, so it's (read_be is) inferred in the binrw derives for bytes.
It's just for bits that it needs reversing.
So something in either of these places would be nice:
#[bitsize(32)]
#[derive(FromBEBits)]

Don't know if it's possible in the bitsize() one, but in the derive seems.. possible?
FromBEBits, FromLEBits, FromNEBits

Hmm, I've seen binrw map can be helpful https://github.com/Robbepop/modular-bitfield/issues/46#issuecomment-802596776.
We'll definitely add a/multiple derive/s for from_be_bytes and so on. This would solve byte-level endian.
Then we still have bit-level endian / bit-numbering.
Still not sure which one you need. Still would be nice if you'd code up your small example with bilge so I can see what it spits out and should spit out.

@hecatia-elegua, I hope this example with modular_bitfield is sufficient to convey what I'm trying.
Things to note:
1 - Need a serialize impl to print out bits for easy troubleshooting
2 - Need accessor function to bits in order to conditionally parse other fields in this or in other related structs/enums
3 - Using the field names in reverse in the macro to cater for BE
#[macro_export]
macro_rules! serialize_bitfield {
    ( $struct_name:ident { $($field_name:ident),*  } ) => {
        impl Serialize for $struct_name {
            fn json_write<W>(&self, writer: &mut W) -> simd_json_derive::Result
            where W: std::io::Write,
            {
                $(
                self.$field_name().json_write(writer)?;
                )*
                writer.write_all(b"")
            }
        }
    };
}

serialize_bitfield!(Flags { b7, b6, b5, b4, b3, b2, b1, b0, });
#[bitfield]
#[derive(Debug, BinRead)]
#[br(map = Self::from_bytes)]
pub struct Flags {
    b0: B1,
    b1: B1,
    b2: B1,
    b3: B1,
    b4: B1,
    b5: B1,
    b6: B1,
    b7: B1,
}

#[derive(Debug, BinRead, Serialize)]
#[br(big)]
pub struct Outside {
    a: u16,
    b: u16,
    c: Flags,
    #[br(if(c.b1() == 1))]
    d: u8,
}

fn main() {
    let data = [0x01, 0xB0, 0x00, 0x00, 0x1E, 0x0E];
    let value = Outside::read(&mut Cursor::new(data)).unwrap();
    let val = value.json_string().unwrap();

    println!("\n{}", &val);
}

Output:
{"a":432,"b":0,"c":00011110,"d":14}

@hecatia-elegua, It seems that reverse_bits will come in handy.

@v1gnesh

1 - Need a serialize impl to print out bits for easy troubleshooting

Are you just using json because you want to print? Then you don't need Serialize, but Debug, or Binary printing.
And right now, if you just derive Serialize, your thing would print "c":30 in our case, since we don't use a byte-array.
Otherwise, if you really need Serialize, I think more inline with normal rust would be:
"c":{"b0":0,"b1":0,...}

but it actually doesn't matter a lot, since you can extend bilge with your own SerializeBits proc macro, similar to this:
https://github.com/hecatia-elegua/bilge/blob/main/tests/custom_bits/custom_bits_derive/src/lib.rs

3 - Using the field names in reverse in the macro to cater for BE

The Serialize implementation you provide with SerializeBits would call self.value.reverse_bits().
Also, can you not reverse_bits with binrw?

2 - Need accessor function to bits in order to conditionally parse other fields in this or in other related structs/enums

We do have accessor functions (.b0(), .set_b0(), ...).

this does it:
#[br(map = |x: [u8; 1]| Self::from_bytes(x.map(|b| b.reverse_bits())))]

now we just need the impl Serialize

Are you just using json because you want to print?

I'm looking to convert from a custom binary format to a universal format; so started with json (simd-json-derive).
But I may not want to stick to json, because the output is 45x the size of the input (it gzips down to the same input file size though).

... if you just derive Serialize, your thing would print "c":30

Yeah, that's what I get.
Need to print bits Msb to Lsb in the output json, and the crate specified above allows custom impl; so I stick the bit-printing there.
Accessor functions will help in custom parsing, but in the final output, just printing bits is fine.
They're unlikely to be used once the output is in json (or whatever target file format).
But, I think I still need them shown as bits to visually differentiate it easily (when reviewing etc.).

We do have accessor functions (.b0(), .set_b0(), ...).

Yup, so in the post above, you'll see I'm passing the field names in reverse to the macro (for impl).
If there's a way for bilge to natively read in BE bit-order, I wouldn't need to specify fields in reverse.

reverse_bits in binrw

Thanks for this example, I'm pretty slow in getting things when it comes to programming.
So with this, in the serialize_bitfield macro above, I'd just need to do something like:
writer.write_all(format!("{:b}", self.value).as_ref())

... ah but I can't get self.value in the custom impl, because it sees the accessor functions and not the value.
At least that's what happens with modular-bitfield.

in bilge it should just be #[br(map = |x: u8| x.reverse_bits())]

This has nothing to do with binrw. It worked for modular_bitfield: https://github.com/hecatia-elegua/bilge/issues/7#issuecomment-1666474917.
There must be a typo somewhere, or some other thing wrong.
Any repro?

Try this? -- https://gist.github.com/rust-play/08742b3d2a5ac8b7eba6b2919bd2b310

ah sorry I completely missed putting x into the struct, see:
https://gist.github.com/hecatia-elegua/bb27b969ddc610f687bd8cd33eae0749

Thank you for showing me.
I'm assuming self.value and self.bytes[] are undocumented, because when I type self., the IDE doesn't suggest them 😛 ? It only shows b1, b2, etc.

It should show it, but it was pretty low on the autocomplete list for me.
For bilge at least, you should not really directly touch the inner value anyways, though.
Right here it's alright, otherwise you could convert it with uN::from(thing) and Thing::from(uN) like I've done for the br(map).


Upload Speed Innacurate

Testing a Google Fiber 1G connection, I was seeing higher download speeds than before, but upload speeds of around 200M instead of the over 800 speed I've seen before.  I tested using two different hosts, different versions of Debian, different connections to the local net, different versions of the client (Debian native and current GitHub.)  On the basis of these tests, I successfully engaged the support technicians at Google, and got very cooperative responses.  As a last step to make sure the ticket would not be pushed back when it was escalated to the engineers, I did an official web-based test using Google's own speed test (http://speedtest.googlefiber.net/).  That test showed close to 900M upload speeds.
Google's speed test has not been shown to be biased.  I had been using the local Google Fiber speedtest host for the cli tests.
This is really embarassing.  I realize that not many developers can afford a symmetrical link, let alone a gigabit, but I think there may be serious bias in the test toward asymmetrical connections and a lower expectation for uploads that precludes accuracy.
There are not many alternatives to this program.  It appears to fill a niche without much competition.   As such, a higher attention to accuracy should be expected.
I am happy to offer my services testing the client on a symetrical gigabit connection if someone can identify the problem and update the code.

On Tue, December 22, 2015 3:57 pm, Matt Martz wrote:

Closed #211.

Care to share any details on why you closed this?  I'd be happy to help
resolve it if I can, or to report it elsewhere if that's apropriate.


Launch with RealSense fail

Platform: Jetson Orin Nano & Ubuntu 22.04 & Isaac ROS 3.0.0
Run example:
ros2 launch isaac_ros_examples isaac_ros_examples.launch.py launch_fragments:=realsense_stereo_rect,ess_disparity \
  engine_file_path:=${ISAAC_ROS_WS}/isaac_ros_assets/models/dnn_stereo_disparity/dnn_stereo_disparity_v4.0.0/ess.engine \
  threshold:=0.35 realsense_config_file:=$(ros2 pkg prefix isaac_ros_ess --share)/config/realsense.yaml

Crash with log:
[component_container_mt-1] 2024-06-13 16:13:24.950 WARN  gxf/std/entity_warden.cpp@464: Component of type nvidia::gxf::EventBasedScheduler, cid 290 failed to deinitialize with code GXF_FAILURE
[component_container_mt-1] 2024-06-13 16:13:24.950 ERROR gxf/core/runtime.cpp@751: Could not deinitialize entity 'TXEAAHPWIS_WVOLORXTUG' (E288): GXF_FAILURE
[component_container_mt-1] 2024-06-13 16:13:24.950 ERROR gxf/std/program.cpp@576: Deactivation failed.
[component_container_mt-1] 2024-06-13 16:13:24.950 ERROR gxf/core/runtime.cpp@1476: Graph wait failed with error: GXF_FAILURE
[component_container_mt-1] [ERROR] [1718266404.951001751] [ess_disparity]: [NitrosContext] GxfGraphWait Error: GXF_FAILURE
[component_container_mt-1] [INFO] [1718266404.951022711] [ess_disparity]: [NitrosNode] Application termination done
[component_container_mt-1] [INFO] [1718266405.001189836] [right_resize]: [NitrosNode] Terminating the running application
[component_container_mt-1] [INFO] [1718266405.002332748] [right_resize]: [NitrosContext] Interrupting GXF...
[component_container_mt-1] [INFO] [1718266405.004440007] [right_resize]: [NitrosContext] Waiting on GXF...
[component_container_mt-1] [INFO] [1718266405.004485736] [right_resize]: [NitrosContext] Deinitializing...

...

[INFO] [component_container_mt-1]: process has finished cleanly [pid 149755]

Hello,
I am running the docker container on agx orin with jetpack 6.0, librealsense version v2.55.1 and ros wrapper v4.51.1
, following the official tutorial for issac ros3 .
ros2 launch isaac_ros_examples isaac_ros_examples.launch.py launch_fragments:=realsense_stereo_rect,ess_disparity    engine_file_path:=/workspaces/isaac_ros-dev/isaac_ros_assets/models/dnn_stereo_disparity/dnn_stereo_disparity_v4.0.0/ess.engine    threshold:=0.35 realsense_config_file:=$(ros2 pkg prefix isaac_ros_ess --share)/config/realsense.yaml

[component_container_mt-1] [INFO] [1719932327.884995060] [isaac_ros_examples.container]: Load Library: /workspaces/isaac_ros-dev/install/realsense2_camera/lib/librealsense2_camera.so
[component_container_mt-1] [INFO] [1719932328.055273900] [isaac_ros_examples.container]: Found class: rclcpp_components::NodeFactoryTemplate<realsense2_camera::RealSenseNodeFactory>
[component_container_mt-1] [INFO] [1719932328.056217372] [isaac_ros_examples.container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<realsense2_camera::RealSenseNodeFactory>
[component_container_mt-1] [INFO] [1719932328.286434515] [realsense2_camera]: RealSense ROS v4.51.1
[component_container_mt-1] [INFO] [1719932328.286574192] [realsense2_camera]: Built with LibRealSense v2.55.1
[component_container_mt-1] [INFO] [1719932328.286616559] [realsense2_camera]: Running with LibRealSense v2.55.1
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/realsense2_camera' in container '/isaac_ros_examples/container'
[component_container_mt-1] [INFO] [1719932328.291844153] [isaac_ros_examples.container]: Load Library: /opt/ros/humble/lib/libimage_format_converter_node.so
[component_container_mt-1] [INFO] [1719932328.366366597] [isaac_ros_examples.container]: Found class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::image_proc::ImageFormatConverterNode>
[component_container_mt-1] [INFO] [1719932328.366484099] [isaac_ros_examples.container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::image_proc::ImageFormatConverterNode>
[component_container_mt-1] [INFO] [1719932328.373242131] [image_format_left]: [NitrosNode] Initializing NitrosNode
[component_container_mt-1] [WARN] [1719932328.373317778] [realsense2_camera]: No RealSense devices were found!
[component_container_mt-1] [INFO] [1719932328.374010246] [NitrosContext]: [NitrosContext] Loading extension: gxf/lib/std/libgxf_std.so
[component_container_mt-1] [INFO] [1719932328.379443116] [NitrosContext]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_gxf_helpers.so
[component_container_mt-1] [INFO] [1719932328.386190172] [NitrosContext]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_sight.so
[component_container_mt-1] [INFO] [1719932328.393839997] [NitrosContext]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_atlas.so
[component_container_mt-1] 2024-07-02 10:58:48.412 WARN  gxf/std/program.cpp@532: No GXF scheduler specified.
[component_container_mt-1] [INFO] [1719932328.412995936] [image_format_left]: [ImageFormatConverterNode] Set output data format to: "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932328.413123838] [image_format_left]: [NitrosNode] Starting NitrosNode
[component_container_mt-1] [INFO] [1719932328.425895114] [image_format_left]: [NitrosNode] Loading extensions
[component_container_mt-1] [INFO] [1719932328.426255172] [image_format_left]: [NitrosContext] Loading extension: gxf/lib/multimedia/libgxf_multimedia.so
[component_container_mt-1] [INFO] [1719932328.431127251] [image_format_left]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_message_compositor.so
[component_container_mt-1] [INFO] [1719932328.433084883] [image_format_left]: [NitrosContext] Loading extension: gxf/lib/cuda/libgxf_cuda.so
[component_container_mt-1] [INFO] [1719932328.437802628] [image_format_left]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_tensorops.so
[component_container_mt-1] [INFO] [1719932328.446244632] [image_format_left]: [NitrosNode] Loading graph to the optimizer
[component_container_mt-1] [INFO] [1719932328.448346390] [image_format_left]: [NitrosNode] Running optimization
[component_container_mt-1] [INFO] [1719932328.522600166] [image_format_left]: [NitrosNode] Obtaining graph IO group info from the optimizer
[component_container_mt-1] [INFO] [1719932328.531022523] [image_format_left]: [NitrosPublisherSubscriberGroup] Pinning the component "sink/sink" (type="nvidia::isaac_ros::MessageRelay") to use its compatible format only: "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932328.535811979] [image_format_left]: [NitrosNode] Starting negotiation...
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/image_format_left' in container '/isaac_ros_examples/container'
[component_container_mt-1] [INFO] [1719932328.538964343] [isaac_ros_examples.container]: Found class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::image_proc::ImageFormatConverterNode>
[component_container_mt-1] [INFO] [1719932328.539027638] [isaac_ros_examples.container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::image_proc::ImageFormatConverterNode>
[component_container_mt-1] [INFO] [1719932328.544584922] [image_format_right]: [NitrosNode] Initializing NitrosNode
[component_container_mt-1] [INFO] [1719932328.545201359] [image_format_right]: [ImageFormatConverterNode] Set output data format to: "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932328.545271854] [image_format_right]: [NitrosNode] Starting NitrosNode
[component_container_mt-1] [INFO] [1719932328.557730976] [image_format_right]: [NitrosNode] Loading extensions
[component_container_mt-1] [INFO] [1719932328.558519187] [image_format_right]: [NitrosNode] Loading graph to the optimizer
[component_container_mt-1] [INFO] [1719932328.560583248] [image_format_right]: [NitrosNode] Running optimization
[component_container_mt-1] [INFO] [1719932328.657233262] [image_format_right]: [NitrosNode] Obtaining graph IO group info from the optimizer
[component_container_mt-1] [INFO] [1719932328.669746334] [image_format_right]: [NitrosPublisherSubscriberGroup] Pinning the component "sink/sink" (type="nvidia::isaac_ros::MessageRelay") to use its compatible format only: "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932328.671850395] [image_format_right]: [NitrosNode] Starting negotiation...
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/image_format_right' in container '/isaac_ros_examples/container'
[component_container_mt-1] [INFO] [1719932328.676483726] [isaac_ros_examples.container]: Load Library: /opt/ros/humble/lib/libresize_node.so
[component_container_mt-1] [INFO] [1719932328.687512887] [isaac_ros_examples.container]: Found class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::image_proc::ResizeNode>
[component_container_mt-1] [INFO] [1719932328.687641429] [isaac_ros_examples.container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::image_proc::ResizeNode>
[component_container_mt-1] [INFO] [1719932328.699595183] [left_resize]: [NitrosNode] Initializing NitrosNode
[component_container_mt-1] [INFO] [1719932328.701507663] [left_resize]: [NitrosNode] Starting NitrosNode
[component_container_mt-1] [INFO] [1719932328.732059381] [left_resize]: [NitrosNode] Loading extensions
[component_container_mt-1] [INFO] [1719932328.733791160] [left_resize]: [NitrosNode] Loading graph to the optimizer
[component_container_mt-1] [INFO] [1719932328.742728452] [left_resize]: [NitrosNode] Running optimization
[component_container_mt-1] [INFO] [1719932328.942714416] [left_resize]: [NitrosNode] Obtaining graph IO group info from the optimizer
[component_container_mt-1] [INFO] [1719932328.956454828] [left_resize]: [NitrosNode] Starting negotiation...
[component_container_mt-1] [INFO] [1719932328.957566137] [image_format_left]: Negotiating
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/left_resize' in container '/isaac_ros_examples/container'
[component_container_mt-1] [INFO] [1719932328.959547736] [left_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932328.959615319] [left_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932328.959648503] [left_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932328.959666934] [left_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932328.960958177] [isaac_ros_examples.container]: Found class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::image_proc::ResizeNode>
[component_container_mt-1] [INFO] [1719932328.961041312] [isaac_ros_examples.container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::image_proc::ResizeNode>
[component_container_mt-1] [INFO] [1719932328.971920171] [right_resize]: [NitrosNode] Initializing NitrosNode
[component_container_mt-1] [INFO] [1719932328.974023144] [right_resize]: [NitrosNode] Starting NitrosNode
[component_container_mt-1] [INFO] [1719932329.002244372] [right_resize]: [NitrosNode] Loading extensions
[component_container_mt-1] [INFO] [1719932329.004070582] [right_resize]: [NitrosNode] Loading graph to the optimizer
[component_container_mt-1] [INFO] [1719932329.014388459] [right_resize]: [NitrosNode] Running optimization
[component_container_mt-1] [INFO] [1719932329.230318895] [right_resize]: [NitrosNode] Obtaining graph IO group info from the optimizer
[component_container_mt-1] [INFO] [1719932329.243705521] [right_resize]: [NitrosNode] Starting negotiation...
[component_container_mt-1] [INFO] [1719932329.244832734] [image_format_right]: Negotiating
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/right_resize' in container '/isaac_ros_examples/container'
[component_container_mt-1] [INFO] [1719932329.247940779] [right_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.248029097] [right_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932329.248082792] [right_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.248112904] [right_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932329.249046584] [isaac_ros_examples.container]: Load Library: /workspaces/isaac_ros-dev/install/isaac_ros_ess/lib/libess_disparity_node.so
[component_container_mt-1] [INFO] [1719932329.276469137] [isaac_ros_examples.container]: Found class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::dnn_stereo_depth::ESSDisparityNode>
[component_container_mt-1] [INFO] [1719932329.276622415] [isaac_ros_examples.container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::dnn_stereo_depth::ESSDisparityNode>
[component_container_mt-1] [INFO] [1719932329.289977490] [ess_disparity]: [NitrosNode] Initializing NitrosNode
[component_container_mt-1] [INFO] [1719932329.292309387] [ess_disparity]: [NitrosNode] Starting NitrosNode
[component_container_mt-1] [INFO] [1719932329.304922778] [ess_disparity]: [NitrosNode] Loading extensions
[component_container_mt-1] [INFO] [1719932329.306380546] [ess_disparity]: [NitrosContext] Loading extension: gxf/lib/serialization/libgxf_serialization.so
[component_container_mt-1] [INFO] [1719932329.312163746] [ess_disparity]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_video_buffer_utils.so
[component_container_mt-1] [INFO] [1719932329.317051953] [ess_disparity]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_messages.so
[component_container_mt-1] [INFO] [1719932329.321330922] [ess_disparity]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_sgm.so
[component_container_mt-1] [INFO] [1719932329.327346854] [ess_disparity]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_messages_throttler.so
[component_container_mt-1] [INFO] [1719932329.335519550] [ess_disparity]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_ess.so
[component_container_mt-1] [INFO] [1719932329.382829806] [ess_disparity]: [NitrosNode] Loading graph to the optimizer
[component_container_mt-1] [INFO] [1719932329.391788217] [ess_disparity]: [NitrosNode] Running optimization
[component_container_mt-1] [INFO] [1719932329.536939475] [image_format_left]: [NitrosNode] Starting post negotiation setup
[component_container_mt-1] [INFO] [1719932329.537740613] [image_format_left]: [NitrosNode] Getting data format negotiation results
[component_container_mt-1] [INFO] [1719932329.537807620] [image_format_left]: [NitrosPublisher] Use the negotiated data format: "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932329.537890595] [image_format_left]: [NitrosSubscriber] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932329.537918786] [image_format_left]: [NitrosSubscriber] Use the compatible subscriber: topic_name="/infra1/image_rect_raw_mono", data_format="nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932329.538382779] [image_format_left]: [NitrosNode] Exporting the final graph based on the negotiation results
[component_container_mt-1] [INFO] [1719932329.568844450] [image_format_left]: [NitrosNode] Wrote the final top level YAML graph to "/tmp/isaac_ros_nitros/graphs/EPFWPYKFGJ/EPFWPYKFGJ.yaml"
[component_container_mt-1] [INFO] [1719932329.569874865] [image_format_left]: [NitrosNode] Loading application
[component_container_mt-1] [INFO] [1719932329.593915234] [image_format_left]: [ImageFormatConverterNode] postLoadGraphCallback().
[component_container_mt-1] [INFO] [1719932329.594128126] [image_format_left]: [NitrosNode] Initializing and running GXF graph
[component_container_mt-1] [INFO] [1719932329.672460716] [image_format_right]: [NitrosNode] Starting post negotiation setup
[component_container_mt-1] [INFO] [1719932329.673392764] [image_format_right]: [NitrosNode] Getting data format negotiation results
[component_container_mt-1] [INFO] [1719932329.673421404] [image_format_right]: [NitrosPublisher] Use the negotiated data format: "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932329.673435867] [image_format_right]: [NitrosSubscriber] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932329.673444443] [image_format_right]: [NitrosSubscriber] Use the compatible subscriber: topic_name="/infra2/image_rect_raw_mono", data_format="nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932329.674541289] [image_format_right]: [NitrosNode] Exporting the final graph based on the negotiation results
[component_container_mt-1] [INFO] [1719932329.691896905] [image_format_right]: [NitrosNode] Wrote the final top level YAML graph to "/tmp/isaac_ros_nitros/graphs/KWNQJXJSFS/KWNQJXJSFS.yaml"
[component_container_mt-1] [INFO] [1719932329.691999720] [image_format_right]: [NitrosNode] Loading application
[component_container_mt-1] [INFO] [1719932329.693874057] [ess_disparity]: [NitrosNode] Obtaining graph IO group info from the optimizer
[component_container_mt-1] [INFO] [1719932329.727308926] [ess_disparity]: [NitrosNode] Starting negotiation...
[component_container_mt-1] [INFO] [1719932329.729610456] [right_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.729690839] [right_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932329.729709526] [left_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.729769685] [left_resize]: Could not negotiate
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/ess_disparity' in container '/isaac_ros_examples/container'
[component_container_mt-1] [INFO] [1719932329.729974738] [right_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.730006321] [right_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932329.730337036] [left_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.730383691] [left_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932329.732850626] [isaac_ros_examples.container]: Load Library: /opt/ros/humble/lib/libdisparity_to_depth_node.so
[component_container_mt-1] [INFO] [1719932329.742265126] [isaac_ros_examples.container]: Found class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::stereo_image_proc::DisparityToDepthNode>
[component_container_mt-1] [INFO] [1719932329.742367557] [isaac_ros_examples.container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<nvidia::isaac_ros::stereo_image_proc::DisparityToDepthNode>
[component_container_mt-1] [INFO] [1719932329.743655407] [image_format_left]: [NitrosNode] Node was started
[component_container_mt-1] [INFO] [1719932329.744687582] [image_format_left]: Negotiating
[component_container_mt-1] [INFO] [1719932329.745328787] [image_format_right]: [ImageFormatConverterNode] postLoadGraphCallback().
[component_container_mt-1] [INFO] [1719932329.745416498] [image_format_right]: [NitrosNode] Initializing and running GXF graph
[component_container_mt-1] [INFO] [1719932329.745641102] [image_format_left]: Negotiating
[component_container_mt-1] [INFO] [1719932329.754721496] [image_format_right]: [NitrosNode] Node was started
[component_container_mt-1] [INFO] [1719932329.755148689] [image_format_right]: Negotiating
[component_container_mt-1] [INFO] [1719932329.755240943] [DisparityToDepthNode]: [NitrosNode] Initializing NitrosNode
[component_container_mt-1] [INFO] [1719932329.755879621] [image_format_right]: Negotiating
[component_container_mt-1] [INFO] [1719932329.756051906] [DisparityToDepthNode]: [NitrosNode] Starting NitrosNode
[component_container_mt-1] [INFO] [1719932329.760477656] [DisparityToDepthNode]: [NitrosNode] Loading extensions
[component_container_mt-1] [INFO] [1719932329.761246924] [DisparityToDepthNode]: [NitrosContext] Loading extension: gxf/lib/libgxf_isaac_utils.so
[component_container_mt-1] [INFO] [1719932329.777037830] [DisparityToDepthNode]: [NitrosNode] Loading graph to the optimizer
[component_container_mt-1] [INFO] [1719932329.778823784] [DisparityToDepthNode]: [NitrosNode] Running optimization
[component_container_mt-1] [INFO] [1719932329.782172657] [DisparityToDepthNode]: [NitrosNode] Obtaining graph IO group info from the optimizer
[component_container_mt-1] [INFO] [1719932329.785737877] [DisparityToDepthNode]: [NitrosNode] Starting negotiation...
[component_container_mt-1] [INFO] [1719932329.786732421] [ess_disparity]: Negotiating
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/DisparityToDepthNode' in container '/isaac_ros_examples/container'
[component_container_mt-1] [INFO] [1719932329.787027040] [right_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.787077759] [left_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.787087455] [right_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932329.787142750] [left_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932329.787894866] [right_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.787935857] [left_resize]: Negotiating
[component_container_mt-1] [INFO] [1719932329.788108942] [right_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932329.788153293] [left_resize]: Could not negotiate
[component_container_mt-1] [INFO] [1719932329.957399639] [left_resize]: [NitrosNode] Starting post negotiation setup
[component_container_mt-1] [INFO] [1719932329.957535413] [left_resize]: [NitrosNode] Getting data format negotiation results
[component_container_mt-1] [INFO] [1719932329.957571220] [left_resize]: [NitrosPublisher] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932329.957599348] [left_resize]: [NitrosPublisher] Use only the compatible publisher: topic_name="/left/image_resize", data_format="nitros_image_bgr8"
[component_container_mt-1] [INFO] [1719932329.957623891] [left_resize]: [NitrosPublisher] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932329.957642035] [left_resize]: [NitrosPublisher] Use only the compatible publisher: topic_name="/left/camera_info_resize", data_format="nitros_camera_info"
[component_container_mt-1] [INFO] [1719932329.957668243] [left_resize]: [NitrosSubscriber] Use the negotiated data format: "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932329.957739954] [left_resize]: [NitrosSubscriber] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932329.957765265] [left_resize]: [NitrosSubscriber] Use the compatible subscriber: topic_name="/left/camera_info_rect", data_format="nitros_camera_info"
[component_container_mt-1] [INFO] [1719932329.957812176] [left_resize]: [NitrosPublisherSubscriberGroup] Adjusted the compatible format of the component "image_sink/sink" (type="nvidia::isaac_ros::MessageRelay") from "nitros_image_bgr8" to "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932329.958141547] [left_resize]: [NitrosNode] Exporting the final graph based on the negotiation results
[component_container_mt-1] [INFO] [1719932329.984453303] [left_resize]: [NitrosNode] Wrote the final top level YAML graph to "/tmp/isaac_ros_nitros/graphs/RNVDYBEQDC/RNVDYBEQDC.yaml"
[component_container_mt-1] [INFO] [1719932329.984576885] [left_resize]: [NitrosNode] Loading application
[component_container_mt-1] [INFO] [1719932329.997575997] [left_resize]: [ResizeNode] postLoadGraphCallback().
[component_container_mt-1] [INFO] [1719932329.998076373] [left_resize]: [NitrosNode] Initializing and running GXF graph
[component_container_mt-1] [INFO] [1719932330.019546641] [left_resize]: [NitrosNode] Node was started
[component_container_mt-1] [INFO] [1719932330.245073398] [right_resize]: [NitrosNode] Starting post negotiation setup
[component_container_mt-1] [INFO] [1719932330.245218227] [right_resize]: [NitrosNode] Getting data format negotiation results
[component_container_mt-1] [INFO] [1719932330.245258067] [right_resize]: [NitrosPublisher] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932330.245288050] [right_resize]: [NitrosPublisher] Use only the compatible publisher: topic_name="/right/image_resize", data_format="nitros_image_bgr8"
[component_container_mt-1] [INFO] [1719932330.245318578] [right_resize]: [NitrosPublisher] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932330.245447184] [right_resize]: [NitrosPublisher] Use only the compatible publisher: topic_name="/right/camera_info_resize", data_format="nitros_camera_info"
[component_container_mt-1] [INFO] [1719932330.245483983] [right_resize]: [NitrosSubscriber] Use the negotiated data format: "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932330.245550734] [right_resize]: [NitrosSubscriber] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932330.245579597] [right_resize]: [NitrosSubscriber] Use the compatible subscriber: topic_name="/right/camera_info_rect", data_format="nitros_camera_info"
[component_container_mt-1] [INFO] [1719932330.245631245] [right_resize]: [NitrosPublisherSubscriberGroup] Adjusted the compatible format of the component "image_sink/sink" (type="nvidia::isaac_ros::MessageRelay") from "nitros_image_bgr8" to "nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932330.245935016] [right_resize]: [NitrosNode] Exporting the final graph based on the negotiation results
[component_container_mt-1] [INFO] [1719932330.271191589] [right_resize]: [NitrosNode] Wrote the final top level YAML graph to "/tmp/isaac_ros_nitros/graphs/LEFHEDKYHP/LEFHEDKYHP.yaml"
[component_container_mt-1] [INFO] [1719932330.271326371] [right_resize]: [NitrosNode] Loading application
[component_container_mt-1] [INFO] [1719932330.285149245] [right_resize]: [ResizeNode] postLoadGraphCallback().
[component_container_mt-1] [INFO] [1719932330.285524727] [right_resize]: [NitrosNode] Initializing and running GXF graph
[component_container_mt-1] [INFO] [1719932330.307535690] [right_resize]: [NitrosNode] Node was started
[component_container_mt-1] [INFO] [1719932330.729837265] [ess_disparity]: [NitrosNode] Starting post negotiation setup
[component_container_mt-1] [INFO] [1719932330.729968591] [ess_disparity]: [NitrosNode] Getting data format negotiation results
[component_container_mt-1] [INFO] [1719932330.730010446] [ess_disparity]: [NitrosPublisher] Use the negotiated data format: "nitros_disparity_image_32FC1"
[component_container_mt-1] [INFO] [1719932330.730041422] [ess_disparity]: [NitrosPublisher] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932330.730064973] [ess_disparity]: [NitrosPublisher] Use only the compatible publisher: topic_name="/camera_info", data_format="nitros_camera_info"
[component_container_mt-1] [INFO] [1719932330.730087597] [ess_disparity]: [NitrosSubscriber] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932330.730106317] [ess_disparity]: [NitrosSubscriber] Use the compatible subscriber: topic_name="/left/image_resize", data_format="nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932330.730127468] [ess_disparity]: [NitrosSubscriber] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932330.730143884] [ess_disparity]: [NitrosSubscriber] Use the compatible subscriber: topic_name="/right/image_resize", data_format="nitros_image_rgb8"
[component_container_mt-1] [INFO] [1719932330.730162124] [ess_disparity]: [NitrosSubscriber] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932330.730177227] [ess_disparity]: [NitrosSubscriber] Use the compatible subscriber: topic_name="/left/camera_info_resize", data_format="nitros_camera_info"
[component_container_mt-1] [INFO] [1719932330.730195819] [ess_disparity]: [NitrosSubscriber] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932330.730211467] [ess_disparity]: [NitrosSubscriber] Use the compatible subscriber: topic_name="/right/camera_info_resize", data_format="nitros_camera_info"
[component_container_mt-1] [INFO] [1719932330.730632132] [ess_disparity]: [NitrosNode] Exporting the final graph based on the negotiation results
[component_container_mt-1] [INFO] [1719932330.786850624] [DisparityToDepthNode]: [NitrosNode] Starting post negotiation setup
[component_container_mt-1] [INFO] [1719932330.786974878] [DisparityToDepthNode]: [NitrosNode] Getting data format negotiation results
[component_container_mt-1] [INFO] [1719932330.787003165] [DisparityToDepthNode]: [NitrosPublisher] Negotiation ended with no results
[component_container_mt-1] [INFO] [1719932330.787024221] [DisparityToDepthNode]: [NitrosPublisher] Use only the compatible publisher: topic_name="/depth", data_format="nitros_image_32FC1"
[component_container_mt-1] [INFO] [1719932330.787044317] [DisparityToDepthNode]: [NitrosSubscriber] Use the negotiated data format: "nitros_disparity_image_32FC1"
[component_container_mt-1] [INFO] [1719932330.787346456] [DisparityToDepthNode]: [NitrosNode] Exporting the final graph based on the negotiation results
[component_container_mt-1] [INFO] [1719932330.791297398] [DisparityToDepthNode]: [NitrosNode] Wrote the final top level YAML graph to "/tmp/isaac_ros_nitros/graphs/AVGEPHNPPX/AVGEPHNPPX.yaml"
[component_container_mt-1] [INFO] [1719932330.791442740] [DisparityToDepthNode]: [NitrosNode] Loading application
[component_container_mt-1] [INFO] [1719932330.794354691] [DisparityToDepthNode]: [NitrosNode] Initializing and running GXF graph
[component_container_mt-1] [INFO] [1719932330.837553111] [DisparityToDepthNode]: [NitrosNode] Node was started
[component_container_mt-1] [INFO] [1719932331.382459694] [ess_disparity]: [NitrosNode] Wrote the final top level YAML graph to "/tmp/isaac_ros_nitros/graphs/WMKKTJPWLQ/WMKKTJPWLQ.yaml"
[component_container_mt-1] [INFO] [1719932331.382572108] [ess_disparity]: [ESSDisparityNode] preLoadGraphCallback().
[component_container_mt-1] [INFO] [1719932331.382672299] [ess_disparity]: [ESSDisparityNode] Setting tensorrt_plugin: /workspaces/isaac_ros-dev/isaac_ros_assets/models/dnn_stereo_disparity/dnn_stereo_disparity_v4.0.0/plugins/aarch64/ess_plugins.so.
[component_container_mt-1] [INFO] [1719932331.382689642] [ess_disparity]: [NitrosNode] Loading application
[component_container_mt-1] [INFO] [1719932331.389657911] [ess_disparity]: [ESSDisparityNode] Setting engine_file_path: /workspaces/isaac_ros-dev/isaac_ros_assets/models/dnn_stereo_disparity/dnn_stereo_disparity_v4.0.0/ess.engine.
[component_container_mt-1] [INFO] [1719932331.389748917] [ess_disparity]: [ESSDisparityNode] postLoadGraphCallback() with image [576 x 960]
[component_container_mt-1] [INFO] [1719932331.389763957] [ess_disparity]: [ESSDisparityNode] postLoadGraphCallback() block_size = 2211840.
[component_container_mt-1] [INFO] [1719932331.389774261] [ess_disparity]: [NitrosNode] Initializing and running GXF graph
[component_container_mt-1] [INFO] [1719932331.418477113] [ess_disparity]: [NitrosNode] Node was started
[component_container_mt-1] Using an engine plan file across different models of devices is not recommended and is likely to affect performance or even cause errors.
[component_container_mt-1] [WARN] [1719932334.604459414] [realsense2_camera]: No RealSense devices were found!
[component_container_mt-1] [WARN] [1719932340.828126246] [realsense2_camera]: No RealSense devices were found!
[component_container_mt-1] [WARN] [1719932347.051671398] [realsense2_camera]: No RealSense devices were found!
[component_container_mt-1] [WARN] [1719932353.279603624] [realsense2_camera]: No RealSense devices were found!
[component_container_mt-1] [WARN] [1719932359.503491991] [realsense2_camera]: No RealSense devices were found!
[component_container_mt-1] [WARN] [1719932365.731891972] [realsense2_camera]: No RealSense devices were found!

It cannot find the intelrealsense device I think it is a sdk and the realsense ros wrapper compatibility issue.
But any help or suggestions to fix this issue would be helpful.
Thank you.