1. 29 Jan, 2018 1 commit
  2. 25 Jan, 2018 2 commits
    • Mats Wichmann's avatar
      Build gtest output paths correctly · a4e14b93
      Mats Wichmann authored
      Currently, when the run_tests function is called twice from the
      the same scons script (that is, the script has more than one unit
      test binary to register), the GTEST_OUTPUT environment variable
      becomes malformed.  This is because the string to add is added
      to a list instead of just being appended as a string.  The result
      is that while all the test output binaries are expected to go to
      BUILD_DIR/test_out, in these cases they go deep down underneath
      that directory.  Here are the unexpected paths in an unmodified
      testing run:
      The :xml: is intended as a tag used to signal gtest, it is never
      supposed to be part of the real filesystem path.
      Note fix was already proposed as part of
      https://gerrit.iotivity.org/gerrit/#/c/22275/ but since it's a
      distinct error with a very simple fix, wanted to get it pushed
      through by itself while that one is under consideration.
      Change-Id: I05c57d54034686a7c77c783eab758e7f501e86ea
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      (cherry picked from commit 0d010e4b)
    • Sushil Yadav's avatar
      Remove unused TIZEN package capi-network-wifi. · de6c5089
      Sushil Yadav authored
      The following change has been merged in the master.
      Pushing the change one the 1.3-rel branch as suggested by Phil.
      Change-Id: I8d4b8b97d93521174273e08aa9202e6008e6abfe
      Signed-off-by: default avatarSushil Yadav <sushil.ky@samsung.com>
      Reviewed-by: default avatarJooseok Park <jooseok.park@samsung.com>
      Reviewed-by: default avatarPhil Coval <philippe.coval@osg.samsung.com>
      Reviewed-by: default avatarUze Choi <uzchoi@samsung.com>
      Reviewed-by: default avatarAshok Babu Channa <ashok.channa@samsung.com>
      Origin: https://gerrit.iotivity.org/gerrit/#/c/23347/
  3. 24 Jan, 2018 1 commit
  4. 19 Jan, 2018 2 commits
  5. 18 Jan, 2018 1 commit
  6. 17 Jan, 2018 1 commit
  7. 15 Jan, 2018 1 commit
  8. 12 Jan, 2018 1 commit
  9. 11 Jan, 2018 2 commits
  10. 08 Jan, 2018 1 commit
  11. 02 Jan, 2018 6 commits
  12. 19 Dec, 2017 1 commit
  13. 18 Dec, 2017 1 commit
    • George Nash's avatar
      IOT-582 Android build generate universal APK · 4b4a289f
      George Nash authored
      Two major modifications:
      1) The aar file no longer adds the TARGET_ARCH to the
      name of the file. The aar file contains all of the
      architectures that were built upto that point. This
      has been the case for quite a while so the architecture
      in the name only indicated the build that created the
      aar file not the contents of the aar file.
      2) When APK files are built it will try to build all
      possible architectures as well as the universal APK
      Bug: https://jira.iotivity.org/browse/IOT-582
      Change-Id: I11f5db9f4cb8c634afe4417b280e5feec6c3d7e9
      Signed-off-by: George Nash's avatarGeorge Nash <george.nash@intel.com>
  14. 13 Dec, 2017 1 commit
    • Philippe Coval's avatar
      resource: Fix occlientbasicops to support coaps · 0f2ae826
      Philippe Coval authored
      The fix is to do querry only on resource's address (to use CoAPs channel)
      Observed issue was:
        ./occlientbasicops -u 0 -c 0 -d 1 -p 0 -t 2
        INFO: occlientbasicops: Callback Context for GET query recvd successfully
        INFO: occlientbasicops: StackResult: OC_STACK_UNAUTHORIZED_REQ
        INFO: occlientbasicops: SEQUENCE NUMBER: 16777216
        INFO: PayloadLog: NULL Payload
        INFO: occlientbasicops: =============> Get Response
      I fixed it to:
        INFO: occlientbasicops: StackResult: OC_STACK_OK (...)
        INFO: PayloadLog: Payload Type: Representation (...)
        INFO: PayloadLog:     URI:/a/led (...)
        INFO: PayloadLog:             state(bool):false (...)
      Extra note, it look like the parse function is never returning false.
      Change-Id: Id3e48c8a04453e87a09e7636ead9a9f64c499d44
      Bug: https://jira.iotivity.org/browse/IOT-2390
      Origin: https://gerrit.iotivity.org/gerrit/#/c/23637/Signed-off-by: default avatarPhilippe Coval <philippe.coval@osg.samsung.com>
      (cherry picked from commit f6394a48)
  15. 11 Dec, 2017 1 commit
  16. 08 Dec, 2017 4 commits
  17. 04 Dec, 2017 1 commit
    • Senthil Kumar G S's avatar
      [ES] Changes in Easysetup for spec compliance. · 36c7f823
      Senthil Kumar G S authored
      It includes the following:-
      1. [IOT-2909] Exclude read-only properties.
      Read-Write interface response for "/WiFiConfResURI" is currently
      including the read-only properties ("swat" and "swet") which is incorrect.
      These read-only properties should not be added in the "oic.if.rw" response
      for '/WiFiConfResURI'.
      2. [IOT-2910] Handling post request to "/WiFiConfResURI" with baseline
      interface when there is no interface in the query paramter.
      3. [IOT-2911] Remove "href" from the baseline response for "/WiFiConfResURI".
      Change-Id: I730efa70cedda4dbdb1f21df6e38fec657bc9bb7
      Signed-off-by: default avatarSenthil Kumar G S <senthil.gs@samsung.com>
  18. 30 Nov, 2017 1 commit
  19. 29 Nov, 2017 1 commit
  20. 23 Nov, 2017 2 commits
    • Senthil Kumar G S's avatar
      [IOT-2906][ES] Remove "href" from child response. · d698f81a
      Senthil Kumar G S authored
      For requests which come directly to child resources
      (/WiFiConfResURI, /CoapCloudConfResURI and /DevConfResURI),
      this patch will remove the "href" property from the response
      as spec doesn't mandate the addition of "href" in the response.
      And also, CTT expects the response from direct request to any child
      to be same as the response which comes for the same child
      through collection.
      For example:
      Properties in "rep" for '/WiFiConfResURI' should be same as
      the properties in the direct response for GET from '/WiFiConfResURI' resource.
      Currently "href" is not included in "rep" for child resources.
      But it is included in the direct response for GET/POST.
      When CTT compares both responses, it finds them different due of "href".
      This patch resolves the issue and still conforms to spec.
      Change-Id: I017bed18d3e0ad568b662a03d9bd80134538a8c0
      Signed-off-by: default avatarSenthil Kumar G S <senthil.gs@samsung.com>
    • Senthil Kumar G S's avatar
      [IOT-2904][ES] Fix for issues found through CTT. · fb2e25fc
      Senthil Kumar G S authored
      1. If one of the resources in the POST request over batch
      has invalid properties, then the response should include an
      empty "rep" for those resources.
      For all other resources with valid properties in the request,
      "rep" should include all the properties.
      2. Allowing "cn" property to be set to ES_CONNECT_NONE.
      Change-Id: Ib819bed7a126717cc56df0fb32b3d9f3ec570682
      Signed-off-by: default avatarSenthil Kumar G S <senthil.gs@samsung.com>
  21. 22 Nov, 2017 2 commits
  22. 20 Nov, 2017 2 commits
  23. 18 Nov, 2017 1 commit
  24. 17 Nov, 2017 1 commit
  25. 15 Nov, 2017 2 commits