Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • M MEC Robot Test Suite
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MEC - Multi-access Edge ComputingMEC - Multi-access Edge Computing
  • MEC Robot Test Suite
  • Issues
  • #32
Closed
Open
Issue created Feb 10, 2021 by Simon Pastor@pastorsDeveloper

Plugtest 2021: MEC013: Schemas have non-valid characters preventing the validation

Some schemas have invalid characters in them preventing the validation to go through.

Example of error: 15:52:11.452 TRACE Arguments: [ 'UserList.schema.json' | {'userList': {'resourceURL': 'http://3.84.255.29/simon/location/v2/queries/users'}} ] **15:52:11.454 FAIL UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb0 in position 3615: invalid start byte ** 15:52:11.457 DEBUG Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/JSONSchemaLibrary/init.py", line 31, in validate_json schema = json.loads(open('{}/{}'.format(self.schema_location, schema_filename)).read()) File "/usr/local/lib/python3.6/codecs.py", line 321, in decode (result, consumed) = self._buffer_decode(data, self.errors, final)

This error comes from the schema file position 3615 which has a non valid character: Location latitude, expressed in the range -90� to +90�. Cardinality greater than one only if "shape" equals 7.

The error is not visible in the json file, but if looking at the file in the raw format... all there characters can be seen. They are replacing some sort of 'degree' symbol maybe or something else. The same thing has been seen when using apostophes.. so as: Structure with attributes relating to the target entity�s velocity, as defined in [14].

The files below where seen having this problem: https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite/raw/2.1.1-fix-plu/SRV/UELOCLOOK/schemas/UserList.schema.json https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite/raw/2.1.1-fix-plu/SRV/UELOCLOOK/schemas/UserInfo.schema.json https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite/raw/2.1.1-fix-plu/SRV/RLOCLOOK/schemas/AccessPointInfo.schema.json https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite/raw/2.1.1-fix-plu/SRV/RLOCLOOK/schemas/AccessPointList.schema.json https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite/raw/2.1.1-fix-plu/SRV/UELOCSUB/schemas/NotificationSubscriptionList.schema.json

Edited Feb 10, 2021 by Simon Pastor
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking