Pip Install Error

Hi,
I'm trying to pip install, and getting the following error.  I also tried it from a fresh conda env with the same results.  I can install if from python setup.py install, so maybe the readme isn't available to pip at install time?  Though not really sure...
Here's the traceback:
Collecting lifetimes
  Using cached Lifetimes-0.1.1.tar.gz
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "/private/var/folders/7b/trxdysx57xz95389p87cbhqrxgb3nq/T/pip-build-XwlQNs/lifetimes/setup.py", line 18, in <module>
        long_description=read('README.md'),
      File "/private/var/folders/7b/trxdysx57xz95389p87cbhqrxgb3nq/T/pip-build-XwlQNs/lifetimes/setup.py", line 6, in read
        return open(os.path.join(os.path.dirname(__file__), fname)).read()
    IOError: [Errno 2] No such file or directory: '/private/var/folders/7b/trxdysx57xz95389p87cbhqrxgb3nq/T/pip-build-XwlQNs/lifetimes/README.md'
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

      File "<string>", line 20, in <module>

      File "/private/var/folders/7b/trxdysx57xz95389p87cbhqrxgb3nq/T/pip-build-XwlQNs/lifetimes/setup.py", line 18, in <module>

        long_description=read('README.md'),

      File "/private/var/folders/7b/trxdysx57xz95389p87cbhqrxgb3nq/T/pip-build-XwlQNs/lifetimes/setup.py", line 6, in read

        return open(os.path.join(os.path.dirname(__file__), fname)).read()

    IOError: [Errno 2] No such file or directory: '/private/var/folders/7b/trxdysx57xz95389p87cbhqrxgb3nq/T/pip-build-XwlQNs/lifetimes/README.md'

Here's the conda env.
Current conda install:

             platform : osx-64
        conda version : 3.8.3
  conda-build version : not installed
       python version : 2.7.9.final.0
     requests version : 2.5.1
     root environment : /Users/thauck/bin/miniconda  (writable)
  default environment : /Users/thauck/projects/ltv/env
     envs directories : /Users/thauck/bin/miniconda/envs
        package cache : /Users/thauck/bin/miniconda/pkgs
         channel URLs : http://repo.continuum.io/pkgs/free/osx-64/
                        http://repo.continuum.io/pkgs/pro/osx-64/
          config file : /Users/thauck/.condarc
    is foreign system : False

Thanks for the heads up @tshauck, I'll get this fixed immediately.

I just pushed a new version 0.1.2 to pypi. It install successfully for me on a clean virtualenv.


Full documentation of this API

Our goal is to build up a context driven IoT platform for energy management.
For this I'm trying to understand the NGSIv2 API for a couple of days now. But this is very difficult. Every example I can find (including the step by step guide) lacks some important points.
The main problem (for now) is that I have to register serveral devices, which are able to execute commands. Until now I haven't found any description/example how to do this.
What I've understand so far is:

the devices will act as context-provider
for this I have to implement kinds of iot-agents (transform data from/to context-broker and device)
these iot-agents have to provide the REST endpoints /v2/op/update and /v2/op/query
on startup they have to use the /v2/registration endpoint of the context-broker to self register
....

... and there isn't any description of the registration payload. I don't know how to notify the context-broker about: "Hey CB. I'm device .... I'm able to execute these commands: ...."
Can you please update your documentation/examples.

Can we share which documentation references (links) have you been using so far, please?

Sure:

https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json#/Subscriptions/Create Subscription
https://fiware-orion.readthedocs.io/en/master/user/context_providers/index.html
https://fiware-orion.readthedocs.io/en/master/user/ngsiv2_implementation_notes/index.html
https://fiware-tutorials.readthedocs.io/en/latest/context-providers/index.html
https://fiware-tutorials.readthedocs.io/en/latest/iot-sensors/index.html
https://github.com/telefonicaid/iotagent-node-lib

So, as far as I understand, your goal is to build a system that acts as an IOT Agent. In that case, I'd recommend you to use the IOTA Lib. Note that library implements the IOTA-CB interface (northbound) so you will get "for free" all that stuf about registrations and /v2/op/update and /v2/op/query endpoints implementation.
There is a document on How to build and IOTA using the library in the library repository itself and probably more tutorials and documentation about it (not sure... I'm CCing @jason-fox in the case he knows more references on this).

So, as far as I understand, your goal is to build a system that acts as an IOT Agent. In that case, I'd recommend you to use the IOTA Lib. Note that library implements the IOTA-CB interface (northbound) so you will get "for free" all that stuf about registrations and /v2/op/update and /v2/op/query endpoints implementation.
There is a document on How to build and IOTA using the library in the library repository itself and probably more tutorials and documentation about it (not sure... I'm CCing @jason-fox in the case he knows more references on this).

A simple custom IoT Agent with working commands is described in this tutorial: https://github.com/FIWARE/tutorials.Custom-IoT-Agent/tree/master
There is an up-and-coming webinar on customizing IoT Agents scheduled for the beginning of March 2021: https://www.fiware.org/community/fiware-webinars/

A simple custom IoT Agent with working commands is described in this tutorial: https://github.com/FIWARE/tutorials.Custom-IoT-Agent/tree/master
There is an up-and-coming webinar on customizing IoT Agents scheduled for the beginning of March 2021: https://www.fiware.org/community/fiware-webinars/

Thanks for this hints.
Yes, in our project we have to rebuild a custom IoT Agent. For several reasons we can not use the IoT library you are providing.
And for this I was searching for a concrete documentation about the communication between context-broker and iot-agent (and vice versa)

Thanks for this hints.
Yes, in our project we have to rebuild a custom IoT Agent. For several reasons we can not use the IoT library you are providing.
And for this I was searching for a concrete documentation about the communication between context-broker and iot-agent (and vice versa)

For NGSI-v2 you will use the /v2/registrations endpoint as described here:  https://github.com/FIWARE/tutorials.Context-Providers/tree/master#seven-request
The IoT Agent is then listening on /v2/op/update an example of processing this can be found here: https://github.com/telefonicaid/iotagent-node-lib/blob/master/lib/services/northBound/contextServer-NGSI-v2.js#L55
For NGSI-LD using Orion-LD an actuation example using registration is described here:  https://github.com/FIWARE/tutorials.LD-Subscriptions-Registrations/tree/master#forwarded-update
The final definition  of  NGSI-LD actuations within the ETSI specification is still being discussed.

For NGSI-v2 you will use the /v2/registrations endpoint as described here:  https://github.com/FIWARE/tutorials.Context-Providers/tree/master#seven-request
The IoT Agent is then listening on /v2/op/update an example of processing this can be found here: https://github.com/telefonicaid/iotagent-node-lib/blob/master/lib/services/northBound/contextServer-NGSI-v2.js#L55
For NGSI-LD using Orion-LD an actuation example using registration is described here:  https://github.com/FIWARE/tutorials.LD-Subscriptions-Registrations/tree/master#forwarded-update
The final definition  of  NGSI-LD actuations within the ETSI specification is still being discussed.

I still need further help. Here is my simple example:
There is a shallow entity
{
    _id: {
        id: 'urn:ngsi-ld:GeoHeatStorage:001',
        type: 'GeoHeatStorage',
        servicePath: '/'
    },
    attrNames: [
        'heatStorageCapacity'
    ],
    attrs: {
        heatStorageCapacity: {
            type: 'Number',
            creDate:<PHONE_NUMBER>,
            modDate:<PHONE_NUMBER>,
            value: 0,
            md: {
                unitCode: {
                    type: 'Text',
                    value: 'E14'
                }
            },
            mdNames: [
                'unitCode'
            ]
        }
    },
    creDate:<PHONE_NUMBER>,
    modDate:<PHONE_NUMBER>,
    lastCorrelator: '2b146c10-5ef3-11eb-8013-0242ac120003'
}

For regsitering a context-provider/iot-agent I used this:
POST /v2/registrations
{
  "description": "Current level of heat storage",
  "dataProvided": {
    "entities": [
      {
        "id": "urn:ngsi-ld:GeoHeatStorage:001",
        "type": "GeoHeatStorage"
      }
    ],
    "attrs": [
      "currentHeatStorageLevel"
    ]
  },
  "provider": {
      "http": {
          "url": "http://iot-agent:1880"
       },
            "supportedForwardingMode": "all"
  },
        "status": "active"
}

The resulting document within the registrations collection is:
{
    _id: ObjectId('600ec9586bcbafe46366999d'),
    description: 'Current level of heat storage',
    expiration: NumberLong(9223372036854775807),
    servicePath: '/',
    contextRegistration: [
        {
            entities: [
                {
                    id: 'urn:ngsi-ld:GeoHeatStorage:001',
                    type: 'GeoHeatStorage'
                }
            ],
            attrs: [
                {
                    name: 'currentHeatStorageLevel',
                    type: ''
                }
            ],
            providingApplication: 'http://iot-agent:1880'
        }
    ],
    status: 'active',
    format: 'normalized'
}

Know I query for this entity  GET /v2/entities/urn:ngsi-ld:GeoHeatStorage:001 and get back what is within the entities collection. In the Logs I can see that the context-broker tries to access something with the correlator id (2b146c10-5ef3-11eb-8013-0242ac120003). The response is 404 .
Of course there is an endpoint /op/query in the iot-agent. And now I stuck. I don't know how to debug what's going on. Is there any possibility to get the request the cb tries to execute?
Can you please provide a simple example (or extend the documentation) how the cb forwards the request to the context-provider/iot-agent?
But maybe there is also another issue. The registration document hasn't the same structure as yours (https://fiware-tutorials.readthedocs.io/en/latest/context-providers/index.html#context-provider-registration-actions)

I still need further help. Here is my simple example:
There is a shallow entity
{
    _id: {
        id: 'urn:ngsi-ld:GeoHeatStorage:001',
        type: 'GeoHeatStorage',
        servicePath: '/'
    },
    attrNames: [
        'heatStorageCapacity'
    ],
    attrs: {
        heatStorageCapacity: {
            type: 'Number',
            creDate:<PHONE_NUMBER>,
            modDate:<PHONE_NUMBER>,
            value: 0,
            md: {
                unitCode: {
                    type: 'Text',
                    value: 'E14'
                }
            },
            mdNames: [
                'unitCode'
            ]
        }
    },
    creDate:<PHONE_NUMBER>,
    modDate:<PHONE_NUMBER>,
    lastCorrelator: '2b146c10-5ef3-11eb-8013-0242ac120003'
}

For regsitering a context-provider/iot-agent I used this:
POST /v2/registrations
{
  "description": "Current level of heat storage",
  "dataProvided": {
    "entities": [
      {
        "id": "urn:ngsi-ld:GeoHeatStorage:001",
        "type": "GeoHeatStorage"
      }
    ],
    "attrs": [
      "currentHeatStorageLevel"
    ]
  },
  "provider": {
      "http": {
          "url": "http://iot-agent:1880"
       },
            "supportedForwardingMode": "all"
  },
        "status": "active"
}

The resulting document within the registrations collection is:
{
    _id: ObjectId('600ec9586bcbafe46366999d'),
    description: 'Current level of heat storage',
    expiration: NumberLong(9223372036854775807),
    servicePath: '/',
    contextRegistration: [
        {
            entities: [
                {
                    id: 'urn:ngsi-ld:GeoHeatStorage:001',
                    type: 'GeoHeatStorage'
                }
            ],
            attrs: [
                {
                    name: 'currentHeatStorageLevel',
                    type: ''
                }
            ],
            providingApplication: 'http://iot-agent:1880'
        }
    ],
    status: 'active',
    format: 'normalized'
}

Know I query for this entity  GET /v2/entities/urn:ngsi-ld:GeoHeatStorage:001 and get back what is within the entities collection. In the Logs I can see that the context-broker tries to access something with the correlator id (2b146c10-5ef3-11eb-8013-0242ac120003). The response is 404 .
Of course there is an endpoint /op/query in the iot-agent. And now I stuck. I don't know how to debug what's going on. Is there any possibility to get the request the cb tries to execute?
Can you please provide a simple example (or extend the documentation) how the cb forwards the request to the context-provider/iot-agent?
But maybe there is also another issue. The registration document hasn't the same structure as yours (https://fiware-tutorials.readthedocs.io/en/latest/context-providers/index.html#context-provider-registration-actions)

Which CB version are you using? How are you starting it (i.e. ps ax | grep contextBroker)?

Which CB version are you using? How are you starting it (i.e. ps ax | grep contextBroker)?

I'm using the docker image fiware/orion:2.4.0 and started it with /usr/bin/contextBroker -fg -multiservice -ngsiv1Autocast -dbhost context-broker-db

I'm using the docker image fiware/orion:2.4.0 and started it with /usr/bin/contextBroker -fg -multiservice -ngsiv1Autocast -dbhost context-broker-db

Could you upgrade to fiware/orion:2.5.2 and start it with -logLevel INFO? Orion 2.5.0 introduces a re-work of the log subsystem that could be very useful to debug your forwarding scenario.
Once you do that, please repeat your test and provide the trace associated to the GET /v2/entities/urn:ngsi-ld:GeoHeatStorage:001 operation, please.

Could you upgrade to fiware/orion:2.5.2 and start it with -logLevel INFO? Orion 2.5.0 introduces a re-work of the log subsystem that could be very useful to debug your forwarding scenario.
Once you do that, please repeat your test and provide the trace associated to the GET /v2/entities/urn:ngsi-ld:GeoHeatStorage:001 operation, please.

The log entry for the forwarded POST is:
time=2021-01-26T11:53:58.346Z | lvl=INFO | corr=2c6fb206-5fcd-11eb-8763-0242ac120004; cbfwd=1 | trans=1611660827-537-00000000080 | from=<IP_ADDRESS> | srv=<none> | subsrv=<none> | comp=Orion | op=logTracing.cpp[212]:logInfoFwdRequest | msg=Request forwarded (regId: 600ec9586bcbafe46366999d): POST http://iot-agent:1880/op/query, request payload (114 bytes): {"entities":[{"id":"urn:ngsi-ld:GeoHeatStorage:001","type":"GeoHeatStorage"}],"attrs":["currentHeatStorageLevel"]}, response payload (149 bytes): <!DOCTYPE html>

<meta charset="utf-8">
<title>Error</title>

Cannot POST //op/query

, response code: 404

This response is from the IoT Agent (based on Node-Red). In the log you can see that the response ist from another url (//op/query). Do you have any explanation where this additional slash comes from? There isn't any in the registration document. I also tried (with success) a curl to the target url from the bash of the running docker container.

The log entry for the forwarded POST is:
time=2021-01-26T11:53:58.346Z | lvl=INFO | corr=2c6fb206-5fcd-11eb-8763-0242ac120004; cbfwd=1 | trans=1611660827-537-00000000080 | from=<IP_ADDRESS> | srv=<none> | subsrv=<none> | comp=Orion | op=logTracing.cpp[212]:logInfoFwdRequest | msg=Request forwarded (regId: 600ec9586bcbafe46366999d): POST http://iot-agent:1880/op/query, request payload (114 bytes): {"entities":[{"id":"urn:ngsi-ld:GeoHeatStorage:001","type":"GeoHeatStorage"}],"attrs":["currentHeatStorageLevel"]}, response payload (149 bytes): <!DOCTYPE html>

<meta charset="utf-8">
<title>Error</title>

Cannot POST //op/query

, response code: 404

This response is from the IoT Agent (based on Node-Red). In the log you can see that the response ist from another url (//op/query). Do you have any explanation where this additional slash comes from? There isn't any in the registration document. I also tried (with success) a curl to the target url from the bash of the running docker container.

Workaround:
Extend the url of the context-provider http://iot-agent:1880 => http://iot-agent:1880/v2
So I think the context-broker isn't able to query a context-provider on it's root url. You have to add a path.

Workaround:
Extend the url of the context-provider http://iot-agent:1880 => http://iot-agent:1880/v2
So I think the context-broker isn't able to query a context-provider on it's root url. You have to add a path.

The URL used by Orion to forward requests are:

Queries: url as used in context registration + /op/query
Update: url as used in context registration + /op/update

Is this different from what you have observed in your tests?

The URL used by Orion to forward requests are:

Queries: url as used in context registration + /op/query
Update: url as used in context registration + /op/update

Is this different from what you have observed in your tests?

As you can see in the example above I POSTed a registration with the root url (http://iot-agent:8080) for my iot agent. The agent is listening on http://iot-agent:1880/op/query and http://iot-agent:1880/op/query for POST request. I tested this.
But the context-broker do not just simply add "/op/query" and "/op/update" to the provided url. It adds also a leading "/" between url and "/op/query" or "/op/update". It tries to make requests to http://iot-agent:1880//op/query.
If I extend the url of the registration to http://iot-agent:1880/v2 the context-broker generates the correct url (http://iot-agent:1880/v2/op/query & http://iot-agent:1880/v2/op/update)

As you can see in the example above I POSTed a registration with the root url (http://iot-agent:8080) for my iot agent. The agent is listening on http://iot-agent:1880/op/query and http://iot-agent:1880/op/query for POST request. I tested this.
But the context-broker do not just simply add "/op/query" and "/op/update" to the provided url. It adds also a leading "/" between url and "/op/query" or "/op/update". It tries to make requests to http://iot-agent:1880//op/query.
If I extend the url of the registration to http://iot-agent:1880/v2 the context-broker generates the correct url (http://iot-agent:1880/v2/op/query & http://iot-agent:1880/v2/op/update)

What about if you use http://iot-agent:8080/ (with final slash) instead of http://iot-agent:8080? Do CB adds double slash in that case?
(Just to fully consider all the possible cases of a potential bug in the CB)

What about if you use http://iot-agent:8080/ (with final slash) instead of http://iot-agent:8080? Do CB adds double slash in that case?
(Just to fully consider all the possible cases of a potential bug in the CB)

Same result with or without trailing slash: response is 404 (Cannot POST //op/query)

Same result with or without trailing slash: response is 404 (Cannot POST //op/query)

I have created an issue in Orion Context Broker repository with the specific issue: https://github.com/telefonicaid/fiware-orion/issues/3768
Apart from that, anything else pending? Or can this issue (https://github.com/FIWARE/specifications/issues/13) be closed?

Please extend the documentation https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json#/Registrations/Create Registration to show all possible property payload.

Please extend the documentation https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json#/Registrations/Create Registration to show all possible property payload.

That swagger document is out of my scope, but maybe @jason-fox could move this to the people in charge of that document.


TLS  encrypted password

Hy i'm using this library for a project where the password is TLS encrypted.
On first sight I can't see any info about this in de manual.
Does anyone know how to configure the client to connect with the broker ?
Thanks in advance
Jarren

There is some information on the TLS parameters in the PDF document that comes with the library, in the section MQTT_UDT_SSL_OPTIONS.
The TLS (SSL) option on the connect method are passed straight through to the corresponding parameters on the Paho MQTT Client object.
One suggestion is to use a Windows-based MQTT client like MQTT.fx to test the connection to the broker. The screen shot below shows the SSL/TLS configuration section on the free version of MQTT.fx:

Once you get the connection working with something like MQTT.fx, then you know that the broker and the certificates are all working correctly. The same certificates and settings should then work in the PLC.

I can connect with the server MQTT explorrer and node red on the plc so i'm not sure if this is the right way?
(sServerPassword is the string with the password in)

If you're using SSL options then you need at least one certificate file, like shown in the MQTT.fx screen shot above.
Exactly what MQTT parameters worked with MQTT Explorer and Node Red? Can you show a screen shot, or list the parameters and their values in MQTT Explorer or Node Red? (without giving away any private information).

This is how the MQTT Explorer is configured (encryption tls) is marked on:

And this is how the node red mqtt client is configured:

All the certificates files are blank in node red

I might be missing somethng, but I find it difficult to understand how TLS can be used without certificates.
I am thinking that these connections are not using TLS, even though the "TLS" option is selected, because there is no certificate information.
At the very least, a TLS connection needs the server certificate (as far as I know).
Are you able to confirm with the server administrator that the server is set up to use TLS on port 1884? MQTT servers typically listen on port 1883 (for TCP connections) and/or port 8883 (for TLS connections).
You could also try the same connection from MQTT Explorer/Node Red using exactly the same parameters, but without the TLS option selected. Does that also work?

Slight correction (or addition) to the above:
The Mosquitto MQTT test server also listens on port 1884, for unencrypted but authenticated connections. This seems to fit with the case you describe - the connection is authenticated (with user name and password), but I suspect it is unencrypted (i.e. not using TLS). The server administrator should be able to confirm if this is the case.

If the tls option in node red or mqtt explorer is not on then it the don't connect with the server.

But it kind works now, when the certificates are uploaded to the plc it works.
The problem is that the server administator made it so that ssl is also possible .
So we are not sure if the plc is connected on tls or ssl. I will post the answer in the near futher.
many thanks for your time Martin

OK, glad to hear that it's working.
The URL on the PLC will start with either tcp:// or ssl://
It will only be connected via SSL (aka TLS) when the URL starts with ssl://


Move log, running to Microscope object

A central "Microscope" object was created but its not in widespread use. A good first use would be to centralize logging and startup/shutdown to that object

A huge step was just made towards this: the Qt elements were broken out of the Argus threads such that its now possible to add the following to a CLI microscope object:

Motion thread
Planner thread
Joystick thread
Image processing thread

A good test would be a demo where you can jog around with a joystick. Similarly this should help revive the long broken CLI planner if necessary


Failed on running examples

start-app thrown an exception:
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'src')
    at eval (eval at default (start-app.js:6:19), <anonymous>:10:53)
    at eval (eval at default (start-app.js:6:19), <anonymous>:675:3)
    at default (start-app.js:8:17)

Thanks for reporting this!  Now fixed.
The latest wasm-bindgen seems to generate 'pkg/*.js' artifact that initializes script_src at the top of the function:
https://github.com/w3reality/wasm-mt/blob/f4314aaceaa05dca3566c3aaaa1fecba6ea9c009/examples/exec/pkg/exec.js#L1-L9
Actually, we wasm-mt does not rely on this script_src variable, so  workaround is applied to 'start-app.js' d38b224


Crashing with 0.2.3 and the lastest git version with the same errors. Removing the mod fixes it.

Using this on fabric 0.11.3 1.16.5 with java 8 with quite a bit of other mods. Heres the crashlog https://pastebin.com/gjzyx4Fe

Smithee is currently undergoing re-development. It will take a while before it is finished, so this issue will take a while to be closed. The reason for the crash is due to you using a too recent version of Harvest Scythes. The only way around this crash at the moment is to install an older version of Harvest Scythes.


Feature request: Update node/npm version in package.json when new version is released

Hi there!  One feature that I'd like to have is if Greenkeeper could update the engines.node and or engines.npm key when a new release of node or npm came out.
Thanks, and keep up the great work!

Hey @jbuck,
thanks for writing. This is something we've been thinking about from the beginning and we'd like to add this feature to Greenkeeper. Unfortunately it's not yet on top of our priorities, but we want to make it work in the future.
Best,
Stephan

Closing in favour of #710


How to include the cxx.h file in C++ files

I am trying to use some APIs in cxx.h file. However, I didn't find a way to include this file. I tried
#include "rusty_code/rust/cxx.h"

But the compiler complains that
fatal error: 'rusty_code/rust/cxx.h' file not found

So I wonder what is the correct way to include this cxx.h library in C++ files?
Thanks!

I figured out. First build the cxxbridge target then include like this
#include "rust/cxx.h"


Unit tests pass with errors

Original issue 5 created by<EMAIL_ADDRESS>on 2008-09-08T11:01:04.000Z:
The following unit tests report errors to stderr:
vcencoder_test
addrcache_test
vcdecoder_test
codetable_test
However, all these tests output "[  PASSED  ]" to stdout
The project was built from source files with VS2008, under WinXP SP2.
To reproduce the problem:

Open open-vcdiff.sln with VS2008
Have the project converted by VS
Re-build the solution
Run the unit tests (found in Release sub-dir) one by one
(they also are run automatically as a part od the build process)

I see "ERROR" lines of output. See the attached stderr files.
Platform:
Microsoft Visual Studio 2008 Version 9.0.21022.8 RTM
OS Name	Microsoft Windows XP Professional
Version	5.1.2600 Service Pack 2 Build 2600
vcdecoder_test error output mentions "VCDIFF delta file"; there's no such
file provided nor generated by another test.

Old comments:

The ERROR lines of output are expected as part of the unit tests.
When the open-vcdiff encoder or decoder encounters an error, it logs an error message to stderr and returns false from the interface -- for example, from VCDiffStreamingDecoder::DecodeChunk(), defined in vcdecoder.h.
As an example, in the following three lines of output from the build:

[ RUN      ] CodeTableTest.MissingAdd
ERROR: VCDiff: Bad code table; there is no opcode for inst ADD, size 0,  mode 0
[       OK ] CodeTableTest.MissingAdd
>
> ... the first and third line are produced by the unit test framework, while the middle ERROR line is the error message reported by open-vcdiff.  The unit test `CodeTableTest.MissingAdd` makes sure that if open-vcdiff is presented with an invalid code table, it reports an error condition.  So the error is the correct, expected result of the test.
>
> If a unit test fails, the unit test executable will return a non-zero exit code, which will cause Visual Studio to report a failure condition and stop the build. For open-vcdiff 0.2, if none of the unit tests fails, you will see the following line at the end of a complete rebuild:
> `========== Build: 18 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========`
> This is enough to assure you that none of the unit tests has failed.
>
> If you are integrating `open-vcdiff` into an environment in which you don't want any error logging information sent to `stderr`, then you can change the definition of `LogMessage` in `logging.cc` (part of the vcdcom project) to take some other action when  a message is logged. Your replacement definition must return a class that has the `<<` operator defined for strings, integers, etc., because the `LOG` macro has the same syntax as a C++ output stream like `cerr`.
>
> > vcdecoder_test error output mentions "VCDIFF delta file"; there's no such
> > file provided nor generated by another test.
>
> The term "delta file" has a particular meaning in the context of VCDIFF: it refers to the output of the encoder, or the input of the decoder.  It does not necessarily refer to a file on disk.  See Section 4 of RFC 3284 (http://www.ietf.org/rfc/rfc3284.txt), which describes the expected contents of a "delta file".  In the case of vcdecoder_test, the "delta file" is actually a static series of hard-coded bytes, which are used to confirm that the decoder produces the correct output (or the proper error message) given the delta file as input.
>
> P.S.  I thought about suppressing the ERROR messages to make the unit test output cleaner, but in most cases it is important to verify not just that the encoder or decoder produces some sort of error, but that the error message is the correct one.

Answer from reporter:
> All you say is perfectly sound. Agree. Unit tests must test as much execution paths as possible, including error handling.
> I think that makes the task less automated, because it involves looking through the output in order to verify the error messages. It somewhat counters the philosophy of automated batch testing. The strictest approach would be to have the test environment capture and verify the error messages, thus fully encapsulating the tested code. And this would make the output cleaner, too. Though I do not know if googletest facilitates that.

Reply:
> I agree with you.  Verifying the test output by hand is not ideal and can cause regressions to go unnoticed.  Currently we only have automated checks for the output of the death tests (those that are expected to crash or exit.) I'll change this defect to an enhancement request and keep it open. The goal will be to print encoder/decoder errors only if they differ from the expected output.

This issue seems to be a duplicate of #33 as the root issue is the same. We need to change the logging mechanism.
Closing.


x:DeferLoadStrategy readme.md "reference" link is pointless

https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/XamlDeferLoadStrategy
the link in the Readme.md goes to the generic Windows 10 page. Nothing useful.

Thanks for pointing this out. Will be fixed in the next refresh.


Translation platform

Idea
Since No Chat Reports is getting a lot of strings and a lot of translators, it would be wise to migrate to a translation platform to make the process easier for everyone.
Some platforms:

Crowdin - free limited plan/free unlimited FOSS plan
Transifex - free FOSS plan
Weblate - free FOSS plan/free if self-hosted

I prefer Crowdin as it has the best UI of the three and it is used by, among others, Mojang itself. At the same time, I understand that Mojang using it may be a drawback, so other options are fine too.
Reasoning

Easier collaboration on translation strings
Strings can be commented
Users get locale update notifications
All strings don't have to be translated on one go
String updates create an automatic pull request
etc.

Other Information
No response

They all suck. Someone votes "good enough" strings and forgets, then you have no chance to make a better one. That's why I use a custom resource pack to translate Minecraft to Romanian.

 Someone votes "good enough" strings and forgets, then you have no chance to make a better one. That's why I use a custom resource pack to translate Minecraft to Romanian.

I'm sorry you've had that experience, and in an older version of Minecraft, I can relate as well.
There are ways to solve it, though:

vote for the translations
discuss with the original commenter
discuss with the language proofreader
discuss with a global proofreader/project owner

So as long as we'd make the existing language contributors proofreaders, they'd get to choose which new strings get approved.

Will be happy to assist with the Crowdin integration 🙂

So as long as we'd make the existing language contributors proofreaders, they'd get to choose which new strings get approved.

Well yeah, here's the issue - too many people just drop in the translation once and then disappear. Overall I do not think translation platform is something we absolutely need at this point, not until we have more recurrent localizators.


Prompt used during pretraining

Why you have decided to use empty prompt "" when you need to use the unet to build the features from the noise image?
 input_ids_for_encoder = tokenizer(         "",         # args.prompt_template.format(placeholder_token=args.domain_class_token),         padding="max_length", truncation=True, max_length=tokenizer.model_max_length,         return_tensors="pt"     ).input_ids
We know that the image would be something like "a photo of args.domain_class_token" so I'm not sure if this can have an impact on the pretraining

@Actis92 Hi sorry for the late reply. This is actually a good point! You can definitely experiment this. In fact, you can see this line to show that I was about to try it.


Porting Ganglia collectors to diamond

Adding new collectors to fullerite's diamond collector:-
*OSDistroCollector
*NUMAZoneInfoCollector (different from the current numa
collector that runs on numactl, this one is more verbose)
This commit also patches existing diamond collector, ConnTrackCollector
to handle extra config parameters to display the hash_ratio of
the table sizes to buckets.

Everything looks good aside from the 'path' value being used as an actual path instead of a name token thing for composing metric name (from collector.get_metric_path()). Whoever thought of naming that 'path'? What do you think @tsheasha , will it cause any issues have /proc/zoneinfo as part of the metric name?

ship it!

+1


Add events command

Add a events command and related method in Project 🐯.
Events command listen to real-time events from docker (filtering for the project). It's implemented using vdemeester/docker-events library.
On the API side, Events returns a channel of Message (for engine-api) to be consumed by the client.
To do still:

[x] Some tests (integration/unit)
[x] Implement the json flag
[x] Format date like docker-compose ?
[ ] Handle error better

Note: test should be easier to implement once context.Context PR is merged (#241)
Closes #215.
/cc @joshwget @ibuildthecloud @dnephin
🐸

ping @joshwget


Paper-over Python errors

@nathanielmanistaatgoogle There are a few failures in the metadata tests, e.g.
Testing gRPC Python...
SUCCESS       unit._metadata_test.MetadataTest.testStreamStream
Running       unit._metadata_test.MetadataTest.testStreamUnary
FAILURE       unit._metadata_test.MetadataTest.testStreamUnary
Running       unit._metadata_test.MetadataTest.testUnaryStream
SUCCESS       unit._metadata_test.MetadataTest.testUnaryStream
Running       unit._metadata_test.MetadataTest.testUnaryUnary
SUCCESS       unit._metadata_test.MetadataTest.testUnaryUnary
4 tests finished:
	3 successful
	1 unsuccessful
	0 skipped
	0 expected failures
	0 unexpected successes
Interrupted Tests:
	[]

Errors/Failures:
unit._metadata_test.MetadataTest.testStreamUnary
traceback:
Traceback (most recent call last):
  File "/usr/lib/python3.4/unittest/case.py", line 58, in testPartExecutor
    yield
  File "/usr/lib/python3.4/unittest/case.py", line 577, in run
    testMethod()
  File "/usr/local/google/home/atash/src/grpc/src/python/grpcio_tests/tests/unit/_metadata_test.py", line 199, in testStreamUnary
    _SERVER_INITIAL_METADATA, call.initial_metadata()))
  File "/usr/lib/python3.4/unittest/case.py", line 654, in assertTrue
    raise self.failureException(msg)
AssertionError: False is not true

Thoughts?

unit._metadata_test is not known to be problematic; my thought would be to look into the failure?

@nathanielmanistaatgoogle I guess I wasn't clear. I made a change here: https://github.com/ctiller/grpc/pull/44/files#diff-453fbc3ace43be70e69f9fd839788ce3R579
I want to know if you have any thoughts on that change and its influence on the metadata tests.

@soltanmm-google: I'd be surprised to learn about that change having any effect on program behavior. Are there circumstances in which rpc_event.success is false but rpc_event.request_call_details.method is not None? I wouldn't have imagined any such circumstances. If so, what do they indicate?

@ctiller Will prolly' actually need to use slice duplication instead of slice borrowing-when-reading-even-though-the-refcounts-might-be-wrong. -.-'


feature: support monitoring spring gateway metrics

What's changed?
support monitoring spring-gateway
Checklist

[ ]  I hereby agree to the terms of the HertzBeat CLA
[ ]  I have read the Contributing Guide
[ ]  I have added the necessary unit tests and all cases have passed.

sorry，I missed the help document, so I'll fill it in now


Refactor out HandsProvider

First step of https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/issues/66, to reduce the boilerplate code needed to spin up a new hands provider.
Also refactors out DefaultHandJointRadius, as 0.005f was used in a couple places.
Also, some assorted formatting and slight perf updates.

Please be sure to increment the version number in the core's package.json file and any required dependencies (ex: input)

Core had already been incremented to 3.0.1 in #485 (which hasn't shipped yet), so I only incremented Input to 3.0.1 (along with its Core dependency version).
Since the changes in this PR are entirely internal, I don't think it falls under the category of a minor version bump. Once I complete #66, it will though!


Distribution plots of prediction score for binary classifiers

Hi would be nice to extend the binary classifier probabilistic report to include distribution plots (in addition to the scatter plot) of the prediction score grouped by the positive/negative true class. This way it will help identify the right cut-off point.
For the multi-label problem we can do multiple plots using 1-vs-all modeling.

Hi @joaomario-brainly,
We are about to add this visualization to our newest update release. Was wondering if that is something you meant? Let us know your thoughts!

That would be awesome yes.
If you can also have a kde interpolation you could measure the overlapping between the two curves which is the area where there are FP and FN.
Thanks. You are doing an amazing work.


Error while logging: Invalid format string

I get this message after I start it. I run it on Windows Server 2016 64-bit and Python 2.7. Was using a similar InstaBot before but it stopped working.
Log:
Error while logging: Invalid format string
Success
    Starting Bot at 14:12 2018-12-10

    Current daily count:
     - All operations: 307
     - Like news feed: 0
     - Likes: 253
     - Follows: 27
     - Unfollows: 27
     - Comments: 0

Error while logging: Invalid format string
found 64 new.
Error while logging: Invalid format string
Error: object of type 'bool' has no len()
Traceback (most recent call last):
File "C:\InstaBot-master\src\instabot.py", line 735, in main
self.main_loop()
File "C:\InstaBot-master\src\instabot.py", line 782, in main_loop
self.refill_bucket()
File "C:\InstaBot-master\src\instabot.py", line 899, in refill_bucket
(len(feed_data), len(
TypeError: object of type 'bool' has no len()
    Current daily count:
     - All operations: 307
     - Like news feed: 0
     - Likes: 253
     - Follows: 27
     - Unfollows: 27
     - Comments: 0

Error while logging: Invalid format string
Success
    --- Delaying 9.20300006866 seconds ---

Error while logging: Invalid format string
Success
    --- Delaying 71.3900001049 seconds ---

Hi @izhzz thanks for the feedback. The issue was with datetime string parsing on windows. It should be fixed now :). Let me know so I can close the issue.

Let me know so I can close the issue.
Wow, great! Everything works now :D


Fix stop the machine on close on Windows

Introduce a delay and a two-step close windows procedure to allow to receive and execute the order to stop  the machine when Kitematic closes on Windows.

Ok, I found a way to solve the issue https://github.com/docker/kitematic/issues/1369 but I have to admit it's not a very 'pretty' solution but it has the only way I found to get it working.
The problem is this:

On windows you are not using the before-quit event (I don't know why, but it doesn't work the same way than on Darwin system (MacOS X) ) but the close window event.

When you receive that event and send it a new event to the app.js to close the machine if the setting is checked, but there is no time to receive the event so the action is never executed. So, the idea here is to do it two times. The first time you send the event and set a Promise to execute again the close method and then it closes.
If you find a better idea or way to get it fixed, please, go ahead!

@alexandrev Thanks for the notes. We are working on fixes for VM issues for both Mac and Windows. That being said, it'll take us some time to test and release this.

No problem. I'm here only to help you. Have a nice day
-- Sent from my mobile phone. Please excuse any typo.
On Jan 21, 2016 12:13 AM, "Michael Chiang"<EMAIL_ADDRESS>wrote:

@alexandrev https://github.com/alexandrev Thanks for the notes. We are
working on fixes for VM issues for both Mac and Windows. That being said,
it'll take us some time to test and release this.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/kitematic/pull/1394#issuecomment-173395425.

it seems that we have to prepare a simple app to prove the issue, so this it is going to take longer than expected. Which is the normal procedure here? We freeze the PR until we have a better solution from atom/electrom API? We go forward with this until we have a better solution to solve the UX for the Windows users? /cc @FrenchBen
Thx!

I don't understand we are wasting so much time to merge so easy PR to leave it to have conflics with the master branch...

@alexandrev I thought that the last iteration made it impossible to determine the closing of a window and that an issue would be opened with Atom?
Merging code that is a 'temp' fix isn't a good solution IMHO. Unfortunately there are a lot of issues that need to be looked at first before the qa on the PR can be made accordingly.
Time is the enemy here, which causes the above conflicts unfortunately :[

Updating the branch to avoid conflicts.


Helm: publish chart for ethstats dashboard & server plus dependencies

Initial release for ethstats chart.
Currently only supports lite mode + no persistence.
Deploys ethstats-dashboard, ethstats-server and deepstream.
Check the readme for details.

Tested Lite mode with/without redis persistence. Merging this.


clean and install before bumping a version

Codecov Report

Merging #592 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #592   +/-   ##
=======================================
  Coverage   99.72%   99.72%
=======================================
  Files         259      259
  Lines        6502     6502
  Branches     1517     1517
=======================================
  Hits         6484     6484
  Misses         18       18

Continue to review full report at Codecov.

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


Bluetooth: Mesh: support BLE MESH based on PSA in mesh samples

PR with changed mesh samples configuration to be able to run then with PSA based crypto library or with timycrypt if PSA based implementation cannot fit to the platform.

Looks ok. We will have to adjust CONFIG_MINIMAL_LIBC_MALLOC_ARENA_SIZE once we integrate PSA properly so that all mesh keys fit in RAM. I think we should create a build assertion for checking this parameter.

x86 based platforms do not need this configuration. If I add static assertion that checks heap size then BabbleSim test compilation is broken. I guess it is inconvenience to have platform dependend static assertion in mesh.

Looks ok. We will have to adjust CONFIG_MINIMAL_LIBC_MALLOC_ARENA_SIZE once we integrate PSA properly so that all mesh keys fit in RAM. I think we should create a build assertion for checking this parameter.

x86 based platforms do not need this configuration. If I add static assertion that checks heap size then BabbleSim test compilation is broken. I guess it is inconvenience to have platform dependend static assertion in mesh.

We will have to deal with this somehow anyway. Customers needs to know how much memory allocate so that it doesn't become a surprise for them once they deployed a firmware which can't store number of keys configured through mesh settings. It is also unclear how much memory is needed for PSA to store keys. All this needs to be described somewhere for the customers and ideally we should have some protection against misconfiguring device.


Add process for converting merged objects to AnnData

Closes #604
⚠ Stacked on #610 (Because this is slightly dependent on decisions made in #610, I'm going to wait to request review)
This PR adds a process to convert the merged SCE objects to an AnnData object. When converting to AnnData, I chose to use the same scripts that we use in the main workflow to convert the object and then move the counts. The reason for this is I think it's probably best to be consistent in how we format our objects. In particular, with the AnnData objects, we add the sample metadata as columns in the colData and do a little bit of renaming. I don't think there's any reason we shouldn't be doing that here.
This process doesn't differ much from the conversion process in the main workflow, except here, we know that the only time we will have an altExp is if the has_adt value is true. I use that value to determine if the feature file should be created.
Also, all of the objects are considered processed objects here, so I run move_counts_anndata.py for all HDF5 files. Again, I'm doing this so that how we name things is consistent with the other AnnData objects.
The last idea I had was maybe we also want to add the sample metadata to the colData of the merged objects. That way, things like diagnosis, age, etc., would be easier to work with instead of living in a separate data frame in the metadata. What do we think?

I've gone ahead and tested this and this is ready for review!

LGTM! The only thing I am thinking is I know I saw some comment go by somewhere (github? slack?) recently from @jashapiro about updating the extension we use for hdf5 files... Should we do this? @jashapiro please weigh in!

I think if we did that then we would need to change all the individual AnnData file extensions and then dev would also have to update their code. They can have .hdf5, .h5ad, or .h5, so I don't think it's worth the headache personally.

It is in #616, which seems like the place to do it (but https://github.com/AlexsLemonade/scpcaTools/issues/244 has to happen first, as we do checks in scpcaTools)


Better Compose Box

[ ] Keyboard shown in compose box should push stream content up #180
[x] Compose box should allow choosing of topic #163
[x] Smart placeholder for compose input #594
[x] Auto complete suggestions are not being displayed outside the compose box for Android #579
[ ] Thumbs up button when no text in compose box #517 (to discuss)

Closing as mostly accomplished. Will track the list in other ways.


Notes field is being typecast incorrectly

$payment['notes'] is an instance of Razorpay\Api\Payments somehow

@captn3m0 It's because of the fill()

@captn3m0 https://github.com/razorpay/razorpay-php/pull/34


Implement about page

Reference figma design for about page and implement it using React

Note: This page will likely not have any interaction, meaning it can be rendered with SSR. Omit the "use client" directive when creating this component


[Stacked Themes] The plugin flutter_statusbarcolor_ns uses a deprecated version of the Android embedding

The plugin flutter_statusbarcolor_ns uses a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if this plugin supports the Android V2 embedding. Otherwise, consider removing it since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.
i was going to open an issue to the author but he closed the issue section.
fyi this happened in the latest flutter update 2.5

having the same issue!

same issue, should we open ticket on flutter_statusbarcolor_ns  side ?

yes go ahead

yes go ahead

not able to create ticket on git repo flutter_statusbarcolor_ns

same issue

have same issue :( after update to last version

any news ? it is possible to copy the flutter_statusbarcolor_ns package source file to stacked package ? it is only 1 file with 74 line
https://github.com/Sameerkash/flutter_statusbarcolor/tree/master/lib

I find where it is in my code. I am using the stacked_themes: ^0.3.2

The new version of flutter_statusbarcolor_ns is out and fixes this. @FilledStacks @hurbes

Yes. So basically to anyone still struggling with this, just add this to your pubspect.yaml
dependency_overrides:   flutter_statusbarcolor_ns: ^0.4.0

The new version of flutter_statusbarcolor_ns is out and fixes this. @FilledStacks @hurbes

Yes. So basically to anyone still struggling with this, just add this to your pubspect.yaml

dependency_overrides:
flutter_statusbarcolor_ns: ^0.4.0

The new version of flutter_statusbarcolor_ns is out and fixes this. @FilledStacks @hurbes

Yes. So basically to anyone still struggling with this, just add this to your pubspec.yaml
dependency_overrides:
    flutter_statusbarcolor_ns: ^0.4.0

Thank you. This filled my issue. But at the same time displayed a warning message:
Warning: You are using these overridden dependencies:
! flutter_statusbarcolor_ns 0.4.0
I guess this warning was displayed to notify me of my action

any news to release this please ? and also moving provider to latest 6.0.1

@azazadev upgrade your stacked_themes package. If you are still facing an issue upgrade then upgrade your kotlin version in build.gradle ext.kotlin_version = '1.4.20'

This will be fixed soon. Thanks for being patient with me 😄

Fixed on version: 0.3.8+2


app crashed

Describe your issue. If applicable, add screenshots to help explain your problem.
backtrace:
#00 pc<PHONE_NUMBER>035528  /apex/com.android.art/lib64/libjavacore.so (Memory_peekByte(_JNIEnv*, _jclass*, long)+0) (BuildId: 8d85311607fdef69ea901998b2a938b1)
#01 pc<PHONE_NUMBER>0f40e4  /memfd:jit-cache (deleted)
Steps to reproduce.
open camera screen many times
What is the expected result?
app is crashed
Did you try our example app?
No
Is it reproducible in the example app?
Yes
Reproducible in which OS?
Android
Flutter/Dart Version?
3.22.2
Plugin Version?
google_mlkit_text_recognition: ^0.11.0

Could you try the example app?

I tried  but latest camera latest version image format give yuv_420_888
but code is run with  nv21  so its not recognised text
thanktyou
On Thu, Oct 3, 2024 at 6:16 PM Benson Arafat @.***>
wrote:

Could you try the example app?
—
Reply to this email directly, view it on GitHub
https://github.com/flutter-ml/google_ml_kit_flutter/issues/691#issuecomment-2391331959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BD6IWLZAILRZXY5XOOP2JW3ZZU4CLAVCNFSM6AAAAABPI674BCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJRGMZTCOJVHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Okay, I have to close this. Look at this issue #684

Working Configuration:
  google_mlkit_face_detection: 0.11.0
  camera: 0.11.0+2
  camera_android_camerax: 0.6.7+2

Problem:
The issue arises when using google_mlkit_face_detection: ^0.11.0 or google_mlkit_face_detection: 0.12.0 without explicitly specifying the version camera_android_camerax: 0.6.7+2. This happens because camera: 0.11.0+2 uses camera_android_camerax: 0.6.8+2 under the hood, which causes build errors.
Solution:
By explicitly setting camera_android_camerax: 0.6.7+2 and google_mlkit_face_detection: 0.11.0. Using this config it is still the new camera_android_camerax under the hood in the camera package.


Resnet overfitting

Hi there,
I tried to implement resnet and put it into Jupyter Notebook.
https://github.com/shuuchen/pytorch_tutorials/blob/master/Deep Residual Network/drn.nbconvert.ipynb
However in the final gragh, the model got overfitting terribly, where the training loss getting nearly 0 but the testing loss getting higher and higher.
Anyone can help?

 It happened once with me, then when I normalized them, overfitting was reduced. You need to find the mean and std deviation of your images, and then provide them to the data transforms.
Hope that helps

@fawazsammani
Thanks very much !
I used BatchNorm2d layers for normalization. Don' t they do what you talked about ?

@fawazsammani
Thanks very much !
I used BatchNorm2d layers for normalization. Don' t they do what you talked about ?

Check BatchNorm parameter track_running_stats, it has to be True, by default it is False

@tooHotSpot

by default it is False
Actually, it is True by default