1. 15 Jan, 2018 1 commit
  2. 12 Jan, 2018 1 commit
  3. 11 Jan, 2018 2 commits
  4. 08 Jan, 2018 1 commit
  5. 02 Jan, 2018 6 commits
  6. 19 Dec, 2017 1 commit
  7. 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>
  8. 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)
  9. 11 Dec, 2017 1 commit
  10. 08 Dec, 2017 4 commits
  11. 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>
  12. 30 Nov, 2017 1 commit
  13. 29 Nov, 2017 1 commit
  14. 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>
  15. 22 Nov, 2017 2 commits
  16. 20 Nov, 2017 2 commits
  17. 18 Nov, 2017 1 commit
  18. 17 Nov, 2017 1 commit
  19. 15 Nov, 2017 2 commits
  20. 14 Nov, 2017 3 commits
  21. 09 Nov, 2017 3 commits
    • Mats Wichmann's avatar
      Prepare for scons3: change prints and more · 630bb71b
      Mats Wichmann authored
      A previous change updated all the scons scripts:
      This change picks up the semi-external scripts that are called
      by the build, and thus are run in the scons context and need updating.
      Print statements are surrounded with parens so they look like function
      calls.  This is an scons3 syntax requirement even if still using Python 2.
      The old exception format "except FooErr, err" is no longer supported
      in Python 3; since the Python 3 format "except FooErr as err" has been
      available since Python 2.6, there is no problem switching these and it
      makes sense to remove one way things could fail if Py3 is used.
      A few comparisons which used <> are changed to the preferred != form.
      Reformatted Builder call without changing it, and added a comment in the
      forked version to help explain why there are two copies of UnpackAll.py.
      With these changes, a full build completes successfully using scons3.0.
      Change-Id: Ia8df28d12c6504d6466dcf793779535d1ad3aa8b
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      (cherry picked from commit b34da4aa)
    • Habib Virji's avatar
      Delete links lazily when TTL is reached. · 231614df
      Habib Virji authored
      Add ttl parameter to RD client APIs.
      Bug: https://jira.iotivity.org/browse/IOT-1935
      Change-Id: Ic189cebebbcf8127bea1d127dd11a116e09743bb
      Signed-off-by: default avatarHabib Virji <habib.virji@samsung.com>
      Signed-off-by: default avatarTodd Malsbary <todd.malsbary@intel.com>
    • Nathan Heldt-Sheller's avatar
      /pstat Resource CBOR fix · a2b20dc4
      Nathan Heldt-Sheller authored
      Fix for a binary->CBOR marshaling case, where payload
      is to contain "dos", but not "p".  This in in turns causes
      the next Property to be incorrectly placed inside the "dos"
      CBOR map (and then skipped over by the CBOR->binary
      un-marshaling code).
      Also improved logging.
      Change-Id: Ib28fc1e30fdaf1e639afa940ee2626ba14e77584
      Signed-off-by: Nathan Heldt-Sheller's avatarNathan Heldt-Sheller <nathan.heldt-sheller@intel.com>
  22. 08 Nov, 2017 1 commit
    • Ibrahim Esmat's avatar
      Cherry Pick change to enable building with SCons3 · e5418f06
      Ibrahim Esmat authored
      Cherry Pick Mats change from master to enable building with SCons 3.0
      in 1.3-rel branch. This change and the change in review
      https://gerrit.iotivity.org/gerrit/#/c/22809 will be needed to merge
      With these 2 changes merged to 1.3-rel, you can successfully build
      IoTivity with SCons 3.0. Which will also allow you to build the
      UWP versions of the libraries needed for UWP Apps.
      Change in master:
      Prepare for scons3: change prints and others
      In preparation for scons3, recently released, modify remaining print
      statements by surrounding them with parens so they look like function
      calls. That takes care of the scons3 syntax requirement.
      The remaining instances of the sequence "print FOO; Exit(1)" were
      changed to "msg = FOO; Exit(msg)" - this helps with the change by
      not even using the print statement, and by giving the message to
      the output function, it is sent to the error stream rather than
      the output stream.
      Calls to dictionary keys() and values() are now wrapped in list(),
      on Python 3 these return special objects, not the expected list.
      That's harmless to Python 2 usage.
      The old exception format "except FooErr, err" is no longer supported;
      since the Python 3 format "except FooErr as err" has been available
      since Python 2.6, there is no problem switching these.
      Some instances of using the commands module in extlibs changes to use
      subprocess module. Change is transparent.
      A couple of instances of filter(lambda ...)) were changes to
      a python list comprehension, this is considered preferred for
      Python 3 (change was suggested by a conversion tool)
      Note on print() change:
        When running with Python2, the print statement is still used. That
        has a bit of an impact: print(a) is just prints the argument, but
        print(a, b, c) is interpreted as printing a tuple (a, b, c), so we
        could see:
        >>> print "This", "is", "a", "test"
        This is a test
        >>> print("This", "is", "a", "test")
        ('This', 'is', 'a', 'test')
        The second is not pretty.  You can make Python2 code use the function
        instead of the statement:
        >>> from __future__ import print_function
        >>> print("This", "is", "a", "test")
        This is a test
        but that's a pain, so the small number of existing prints which
        used a comma as argument separators were updated to use addition,
        so now we're concatenating a string to produce one arg instead
        of supplying multiple "arguments" that would be misinterpreted
        as a tuple in print().  It's fine to add the import statement
        if it's needed.
      Change-Id: Idac00e1389b79ee65da4a2eb6ef3246551b66843
      Signed-off-by: default avatarMats Wichmann <mats@linux.com>
      Signed-off-by: default avatarIbrahim Esmat <iesmat@microsoft.com>
  23. 07 Nov, 2017 1 commit