wis2box pubsub issues

[alimand]

User story

As a wis2box message subscriber(I build wis2box A for subscribing), I want to subscribe message from another wis2box (I build wius2box B for publishing) , so that I can real test message pubsub functionality by using wis2box.

Acceptance criteria

• [ ] acceptance criteria 1 Step 1: in wis2box B: run: wis2box metadata discovery publish $WIS2BOX_DATADIR/metadata/discovery/mwi-surface-weather-observations.yml (successful) Step 2: in wis2box A: Refer to the documentation https://docs.wis2box.wis.wmo.int/en/1.0b1/user/downloading-data.html in “Downloading data from WIS2” chapter I run: a.pywis-pubsub schema sync b.pywis-pubsub subscribe --config local.yml However, I have issue like this: Message is not a valid notification {...} is not valid under any of the given schemas.

• [ ] acceptance criteria 2 Step 1: in wis2box B: run: wis2box data ingest --topic-hierarchy mwi.mwi_met_centre.data.core.weather.surface-based-observations.synop --path $WIS2BOX_DATADIR/observations/malawi Step 2: in wis2box A: Refer to the documentation https://docs.wis2box.wis.wmo.int/en/1.0b1/user/downloading-data.html in “Downloading data from WIS2” chapter I run: a.pywis-pubsub schema sync b.pywis-pubsub subscribe --config local.yml However, I have issue like this: ValidationError: "version" is a required property.

Definition of done

• [ ] unit/functional tests added/updated
• [ ] documentation updated
• [ ] live demonstration provided

[tomkralidis]

The broker to which wis2box is subscribing to is not providing valid notification messages. Is broker you are subscribing to a wis2box based broker? If yes, what version of wis2box is installed? wis2box should be emitting valid messages.

Else if the broker is not based on wis2box, suggest this issue is filed in https://github.com/wmo-im/wis2pilot/issues for discussion.

[alimand]

Hi Tom,

1.Yes,I think so. (I'm following the official documentation:https://docs.wis2box.wis.wmo.int/en/latest/user/downloading-data.html, following theses steps: a. modify local.yml like this: b.run docker-compose -f docker-compose.subscribe-download.yml up -d --build). c.follow acceptance criteria steps before, then have this issue.

2.The version of wis2box I installed is 1.0.beta1.

Looking forward to your kind reply! Really thanks.

[tomkralidis]

Thanks for the feedback @alimand. Can you copy/paste the notification messages that are being produced by wis2box?

[alimand]

Hi,Tom. Thanks for your reply! Sure. The complete notification message wis2box produces is as follows:

{
  "id": "WIGOS_0-454-2-AWSBALAKA_20211118T095500",
  "type": "Feature",
  "version": "v04",
  "geometry": {
    "type": "Point",
    "coordinates": [
      15.0,
      35.0,
      618.0
    ]
  },
  "properties": {
    "data_id": "origin/a/wis2/mwi/mwi_met_centre/data/core/weather/surface-based-observations/synop/WIGOS_0-454-2-AWSBALAKA_20211118T095500.bufr4",
    "pubtime": "2023-02-08T09:53:34Z",
    "integrity": {
      "method": "sha512",
      "value": "f247f9cccedbd60dd03d2aec028c20626dfdafd436883e528ea8188e07c1fba9b558c5ff6323702b792bd2b79161f014379f739643d022865a75e69dd5812de3"
    },
    "wigos_station_identifier": "0-454-2-AWSBALAKA"
  },
  "links": [
    {
      "rel": "canonical",
      "type": "application/x-bufr",
      "href": "http://10.0.49.23:8999/data/2021-11-18/wis/mwi/mwi_met_centre/data/core/weather/surface-based-observations/synop/WIGOS_0-454-2-AWSBALAKA_20211118T095500.bufr4",
      "length": 247
    }
  ]
}

[tomkralidis]

Hi @alimand this has been fixed in #394 and will be part of the 1.0.b2 release.