search

aisstream / issues

7 stars 3 forks source link

[Bug][Fix Deployed] MSSI always value '0' #36

Closed andergoros closed 1 year ago

andergoros commented 1 year ago

Good morning:

My program has been working correctly (javascript/websockets) but now I am receiving always '0' at metadata/MMSI and 0 at a new field named MMSI_String.

Thank you

jay-tux commented 1 year ago

Happens here as well - with both the Python example(s) and our own C# backend

jay-tux commented 1 year ago

Probably related - some vessels have an empty name

fgorina commented 1 year ago

Happens the same. Also in headers has appeared a field MMSI_String with also integer value 0

EiniusHeinius commented 1 year ago

For me the same .... MetaData.MMSI is just 0

aisstream commented 1 year ago

This looks like a bug on our end. When was this first observed ? That will help us correlate it to a deployment.

EiniusHeinius commented 1 year ago

For me between July 25th 5:37 AM and July 25th 5:57 AM

Should be GMT

aisstream commented 1 year ago

We have identified the issue. Two of our services had incompatible versions running causing MMSI to not not be correctly parsed when sent between the services. The issue should be mitigated but we will leave this issue open for now, until we observe the fix for the next few hours.

jliebrand commented 1 year ago

Out of interest, how does the MMSI relate to the UserID which appears to be the same thing? Is it always the same thing?

aisstream commented 1 year ago

@jliebrand Yes they are always equal. That is due to a weird naming decision that we cannot undue to ensure we do not break anyones clients.