Re: [dev] dealing with (reported) memory leaks and valgrind

In general using ASSERT_* is not a big deal for valgrind unless the test is actually failing. Valgrind reports on what the program did not what it could have done. So if you are failing on an ASSERT_* then you have a unit test failure which you need to address. The memory leak caused by the fai

[dev] once more: gerrit submit-type setting; iotivity-node

It seemed there's no remaining disagreement to switching away from the cherry-pick strategy setting in gerrit, but it still hasn't happened. I find I'm now able to make this change - I tested that on the largely inactive iotivity-xmpp project last week and it seemed to "take". So if someone does

Re: [dev] Easy Setup functionality not working

Hi Abhishek, I have created a ticket for this with ID: IOT-2674. Also, as per Scenario A, mediator should connect to the enrollee through bluetooth and send wifi credentials acquired from Enroller right? Thanks & Regards Sandeep P Kumar -ABHISHEK PANDEY wrote: - To: Sandeep Pkumar Fr

Re: [dev] 答复: One question about client finding resouces

Hi, Have you applied the patches on 1.3-rel mentioned at bottom of https://jira.iotivity.org/browse/IOT-2443 ttps://gerrit.iotivity.org/gerrit/#/c/22293/ https://gerrit.iotivity.org/gerrit/#/c/21489/ https://gerrit.iotivity.org/gerrit/#/c/22263/

[dev] 答复: One question about client finding resouces

Hi，Dev， About ‘failed to find resources created by server’, is there any workaround for JIRA IOT-2443? Which is mentioned by Coval in below. Now, I had a server and want to verify whether my server can work well. But when I wrote a client, it shows that no playload can be found. Do you ha

Re: [dev] Easy Setup functionality not working

Hello Sandeep,   I can help with the problems you are facing related to IoTivity Easy Setup. Kindly open a JIRA ticket in jira.iotivity.org with details of your environment and iotivity code (branch / release details).   Also, please note that "Scenario A" described in your mail below, i