Skip to content

Releases: interuss/monitoring

v0.27.0

25 Mar 17:16
780073c

Choose a tag to compare

What's Changed

  • Reset release notes after v0.26.0 release by @BenjaminPelletier in #1372
  • [security] Update urllib3 by @BenjaminPelletier in #1374
  • [security] Update flask and werkzeug dependencies by @BenjaminPelletier in #1376
  • [uss_qualifier/scenarios] Fix scenario phase transitions by @BenjaminPelletier in #1375
  • [uss_qualifier/monitorlib] Support new flight_planning API fields by @BenjaminPelletier in #1373
  • Bump docker/login-action from 3.7.0 to 4.0.0 by @dependabot[bot] in #1381
  • [uss_qualifier] Improve check-matching by @BenjaminPelletier in #1380
  • [uss_qualifier] uss availability status: version conflict by @RustedBones in #1137
  • [uss_qualifier/reports] Add KML visualization of RID test queries to sequence view artifact by @BenjaminPelletier in #1382
  • [mock_uss] Cleanup rid database by @the-glu in #1363
  • [uss_qualifier/scenarios/utm/OpIntentValidator/expect_shared()] Check that USS op intent reference matches the DSS-published one (fix #1378) by @mickmis in #1383
  • [mock_uss] Increase start_period for healthchecks and add timeout for mock_uss healthchecks. by @the-glu in #1392
  • [uss_qualifier/astm/utm] Detect op intent details outside reference by @BenjaminPelletier in #1389
  • [docs] Add AGENTS.md based on #1377 dev experience by @BenjaminPelletier in #1384
  • [netrid] Check response validity when calling all_flights by @the-glu in #1388
  • [netrid] Fix misbehaviour tests by not using too large area for Unauthenticated / Incorrectly authenticated requests by @the-glu in #1396
  • [uss_qualifier/astm/utm] Validate operational intent changes are always published to DSS by @mickmis in #1393
  • [uss_qualifier/scenarios/utm] Cleanup extents of op intents actually created; Extend max test run duration; Introduce max scenario execution duration for 'Verify clear area' by @mickmis in #1395
  • [security] Update pyjwt, pyopenssl, pyasn1 by @BenjaminPelletier in #1397
  • [uss_qualifier] Add global timeout and run-to-completion requirement by @BenjaminPelletier in #1399

Full Changelog: interuss/monitoring/v0.26.0...interuss/monitoring/v0.27.0

v0.26.0

27 Feb 16:40
159950b

Choose a tag to compare

What's Changed

Full Changelog: interuss/monitoring/v0.25.0...interuss/monitoring/v0.26.0

Important information

  • New timing report artifact added to uss_qualifier

v0.25.0

16 Jan 15:36
a8adabe

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: interuss/monitoring/v0.24.0...interuss/monitoring/v0.25.0

v0.24.0

30 Oct 12:29
9d22e0f

Choose a tag to compare

What's Changed

  • [uss_qualifier/scenarios/utm/conflict_equal_prio_not_permitted] Fix deletion step: call tested USS instead of control USS by @mickmis in #1270
  • [uss_qualifier/scenarios/utm/conflict] Do not allow USS to close an activated flight by @mickmis in #1267
  • [uss_qualifier/scenarios/utm/conflict_equal_priority_not_permitted] Allow USS to return 'NotSupported' upon Flight 1m modification by @mickmis in #1271

Full Changelog: interuss/monitoring/v0.23.0...interuss/monitoring/v0.24.0

v0.23.0

29 Oct 12:26
dda8d19

Choose a tag to compare

What's Changed

  • [uss_qualifier/scenarios/data_exchange_validation] Fix test step expect_no_interuss_post_interactions by @mickmis in #1238
  • Bump ruff from 0.14.1 to 0.14.2 by @dependabot[bot] in #1255
  • Bump basedpyright from 1.31.7 to 1.32.1 by @dependabot[bot] in #1256
  • [uss_qualifier] safe usage of planning_area's volume resolution by @Shastick in #1248
  • [uss_qualifier] NetRID display_data_evaluator remove unused class member by @Shastick in #1258
  • [uss_qualifier] introduce distance error tolerance for some DisplayProviderBehavior by @Shastick in #1259
  • Bump actions/upload-artifact from 4 to 5 by @dependabot[bot] in #1261
  • Bump actions/download-artifact from 5 to 6 by @dependabot[bot] in #1262
  • [uss_qualifier/scenarios/utm/conflict_equal_prio] Delete Flight 1c if USS does not support modifications by @mickmis in #1268
  • [docs/mock_uss] Improve tracer documentation by @BenjaminPelletier in #1266

Full Changelog: interuss/monitoring/v0.22.0...interuss/monitoring/v0.23.0

v0.22.0

23 Oct 11:27
b352476

Choose a tag to compare

What's Changed

Full Changelog: interuss/monitoring/v0.21.0...interuss/monitoring/v0.22.0

v0.21.0

17 Oct 08:59
c38be9d

Choose a tag to compare

Release Notes for v0.21.0

Mandatory migration tasks

N/A

Optional migration tasks

N/A

Important information

N/A

What's Changed

Full Changelog: interuss/monitoring/v0.20.0...interuss/monitoring/v0.21.0

v0.20.0

13 Oct 11:31
4a99fb4

Choose a tag to compare

Release Notes for v0.20.0

Mandatory migration tasks

Update PlanningAreaResource

Resources of type resources.PlanningAreaResource now have their volume specified via a separate resource.VolumeResource resource, which needs to be passed as a dependency.

Previously, a planning area would be specified as:

planning_area:
  $content_schema: monitoring/uss_qualifier/resources/definitions/ResourceDeclaration.json
  resource_type: resources.PlanningAreaResource
  specification:
    base_url: https://testdummy.interuss.org/interuss/monitoring/uss_qualifier/configurations/dev/f3548_self_contained/planning_area
    volume:
      outline_polygon:
        vertices:
          - lat: 37.1853
            lng: -80.6140
          - lat: 37.2148
            lng: -80.6140
          - lat: 37.2148
            lng: -80.5440
          - lat: 37.1853
            lng: -80.5440
      altitude_lower:
        value: 0
        reference: W84
        units: M
      altitude_upper:
        value: 3048
        reference: W84
        units: M

The volume needs to ve moved to a separate VolumeResource, and references in the dependencies of the existing PlanningAreaResource:

# Add a new resource:
planning_area_volume:
  $content_schema: monitoring/uss_qualifier/resources/definitions/ResourceDeclaration.json
  resource_type: resources.VolumeResource
  specification:
    template:
      outline_polygon:
        vertices:
          - lat: 37.1853
            lng: -80.6140
          - lat: 37.2148
            lng: -80.6140
          - lat: 37.2148
            lng: -80.5440
          - lat: 37.1853
            lng: -80.5440
      altitude_lower:
          value: 0
          reference: W84
          units: M
      altitude_upper:
          value: 3048
          reference: W84
          units: M

# Add a dependencies section with a 'volume' to the existing resource.
planning_area:
  $content_schema: monitoring/uss_qualifier/resources/definitions/ResourceDeclaration.json
  resource_type: resources.PlanningAreaResource
  dependencies:
    volume: planning_area_volume
  specification:
    base_url: https://testdummy.interuss.org/interuss/monitoring/uss_qualifier/configurations/dev/f3548_self_contained/planning_area

Update ServiceAreaResource

Resources of type resources.ServiceAreaResource now have their volume specified via a separate resource.VolumeResource resource, which needs to be passed as a dependency.

Previously, a service area would be specified as:

kentland_service_area:
  $content_schema: monitoring/uss_qualifier/resources/definitions/ResourceDeclaration.json
  resource_type: resources.netrid.ServiceAreaResource
  specification:
    base_url: https://testdummy.interuss.org/interuss/monitoring/uss_qualifier/configurations/dev/library/resources/kentland_service_area
    footprint:
      - lat: 37.1853
        lng: -80.6140
      - lat: 37.2148
        lng: -80.6140
      - lat: 37.2148
        lng: -80.5440
      - lat: 37.1853
        lng: -80.5440
    altitude_min: 0
    altitude_max: 3048
    reference_time: '2023-01-10T00:00:00.123456+00:00'
    time_start: '2023-01-10T00:00:01.123456+00:00'
    time_end: '2023-01-10T01:00:01.123456+00:00'

The volume needs to ve moved to a separate VolumeResource, and references in the dependencies of the existing PlanningAreaResource:

kentland_service_area_volume:
  $content_schema: monitoring/uss_qualifier/resources/definitions/ResourceDeclaration.json
  resource_type: resources.VolumeResource
  specification:
    template:
      outline_polygon:
        vertices:
          - lat: 37.1853
            lng: -80.6140
          - lat: 37.2148
            lng: -80.6140
          - lat: 37.2148
            lng: -80.5440
          - lat: 37.1853
            lng: -80.5440
      altitude_lower:
        value: 0
        reference: W84
        units: M
      altitude_upper:
        value: 3048
        reference: W84
        units: M
      start_time:
        offset_from:
          starting_from:
            time_during_test: TimeOfEvaluation
          offset: 1s
      end_time:
        offset_from:
          starting_from:
            time_during_test: TimeOfEvaluation
          offset: 1h0m1s

kentland_service_area:
  $content_schema: monitoring/uss_qualifier/resources/definitions/ResourceDeclaration.json
  resource_type: resources.netrid.ServiceAreaResource
  dependencies:
    volume: kentland_service_area_volume
  specification:
    base_url: https://testdummy.interuss.org/interuss/monitoring/uss_qualifier/configurations/dev/library/resources/kentland_service_area

Do note that the altitude and time bound fields (altitude_lower, altitude_upper, start_time, end_time) require some adaptations beyond simple copy-pasting.

Optional migration tasks

N/A

Important information

What's Changed

Read more

v0.19.0

17 Sep 16:50
101c9be

Choose a tag to compare

Mandatory migration tasks

Replacement of resources.VerticesResource with resources.VolumeResource

VerticesResource is being replaced with a new VolumeResource,
which now contains a Volume4DTemplate, which can be used to define anything from a simple 2D polygon to a 3D volume to a full 4D spatio-temporal volume with dynamic time-bounds.

The old resources, defined as:

some_resource:
  $content_schema: monitoring/uss_qualifier/resources/definitions/ResourceDeclaration.json
  resource_type: resources.VerticesResource
  specification:
    vertices:
      - lat: 38
        lng: -81
      - lat: 37
        lng: -81
      - lat: 37
        lng: -80
      - lat: 38
        lng: -80

Can be straightforwardly replaced with:

planning_area:
  $content_schema: monitoring/uss_qualifier/resources/definitions/ResourceDeclaration.json
  resource_type: resources.VolumeResource
  specification:
    template:
      outline_polygon:
        vertices:
          - lat: 38
            lng: -81
          - lat: 37
            lng: -81
          - lat: 37
            lng: -80
          - lat: 38
            lng: -80

The optional fields of Volume4DTemplate (altitude_lower, altitude_upper, start_time, start_time, duration, transformations) can be safely omitted in all contexts that formerly depended on VerticesResource.

Important information

  • The RID test data of the U-Space test configuration has been adjusted to cover the Zurich area. (#1142)
  • The IDs of test flights are now generated to be unique across multiple USS. They remain consistent within the same run, but differ from those in previous release runs. (#1148)

What's Changed

  • Update release documentation following v0.18.1 release by @BenjaminPelletier in #1140
  • [typing] Set of typing fixes by @the-glu in #1141
  • [uspace] Update test data for RID to be located in the Zurich area by @barroco in #1142
  • [rid/dp_behavior] Fix misplaced end_test_case by @barroco in #1147
  • [uss_qualifier] Fix obfuscated_clusters list by @the-glu in #1149
  • [uss_qualifier] Add missing end_test_case in MSLAltitude scenario by @the-glu in #1150
  • [uss_qualifier] cleaner output for PendingCheck.describe() by @Shastick in #1152
  • [typing] Set of typing fixes by @the-glu in #1143
  • [uss_qualifier] Update US UTM Implementation mirror test configuration by @BenjaminPelletier in #1153
  • [uss_qualifier] subscription_interactions_deletion: verify secondary DSS instances are clean by @Shastick in #1131
  • [configuration/interuss] Check for OVN requests in the pooled_dss_probing configuration by @barroco in #1146
  • [uss_qualifier] Fix randomness of flights by @the-glu in #1148
  • [uss_qualifier] Fix DisplayProviderBehavior with multiple observers by @the-glu in #1151
  • [tooling] Fix format_documentation.py by @the-glu in #1158
  • [uss_qualifier] use UssAvailabilityState in dss api by @RustedBones in #1157
  • [monitorlib] Add Keycloak auth provider by @the-glu in #1162
  • [mock_uss] Fix clustering by @the-glu in #1161
  • [flight_planning] Add notification endpoint to mock uss, add helper to FlightPlannerClient to retrive notifications by @the-glu in #1155
  • [uss_qualifier] rename and generalize VerticesResource to VolumeResource by @Shastick in #1138
  • [uss_qualifier] oir/sub sync: verify secondary DSS instances are clean by @Shastick in #1132
  • [uss_qualifier] constraints sync: verify secondary DSS instances are clean by @Shastick in #1133
  • Bump sigstore/cosign-installer from 3.9.2 to 3.10.0 by @dependabot[bot] in #1163
  • [tooling] Make basedpyright fail on warnings by @the-glu in #1165
  • [utm] Add SCD0090 checks by @the-glu in #1156
  • Bump basedpyright from 1.31.3 to 1.31.4 by @dependabot[bot] in #1154
  • [utm] Add SCD0095 checks by @the-glu in #1166
  • [uss_qualifier] factorize uss availability fragment by @RustedBones in #1164
  • Update verification approach for SCD0090 and SCD0095 by @BenjaminPelletier in #1167

Full Changelog: interuss/monitoring/v0.18.1...interuss/monitoring/v0.19.0

v0.18.1

27 Aug 00:22
ca40458

Choose a tag to compare

What's Changed

  • [local-env] improve compatibility with different local dev environments by @Shastick in #1128
  • [tooling] Add venv to docker image path by @the-glu in #1139
  • [local-env] Update shebang to use bash from env by @RustedBones in #1136
  • [docs] Update release documentation following v0.18.0 release by @BenjaminPelletier in #1134
  • Bump basedpyright from 1.31.2 to 1.31.3 by @dependabot[bot] in #1135
  • [uss_qualifier] subscription_interactions: verify secondary DSS instances are clean by @Shastick in #1127

New Contributors

Full Changelog: interuss/monitoring/v0.18.0...interuss/monitoring/v0.18.1