feat: log error activity when no stationId

[bajtos]

Example output:

❯ zinnia run main.js
[11:14:28.293 ERROR] Your Station version is outdated. Please upgrade it as soon as possible.
Getting current SPARK round details...
[11:14:28.399  INFO] SPARK started reporting retrievals

I am not convinced this is needed or a good idea, let me know what do you think.

/cc @juliangruber @PatrickNercessian

Links:

• Public Station Dashboard space-meridian/roadmap#96

[juliangruber]

I'd rather have the API reject these, so that it leads to a more noticeable error.

[bajtos]

I'd rather have the API reject these, so that it leads to a more noticeable error.

I am fine with that too.

IIRC, when the API rejects measurements, Spark will turn to the offline state. It's more noticeable but also does not explain to the user how to fix the problem.

Maybe we can implement both measures?

[juliangruber]

With Station Desktop, we have auto updates, so I don't think we need to focus on outdated nodes there. And with Station Core, it's very visible in the logs. We could improve it, but I think for Core it's not that relevant

[juliangruber]

I would instead suggest to add Watchtower documentation, so that Core nodes on Docker also have auto updates?

[bajtos]

I don't fully agree, but I also don't want us to spend too much time discussing this topic.

I am fine to focus our efforts on improving the auto-updater for both Desktop and Core.

I am closing this pull request as rejected.

I would instead suggest to add Watchtower documentation, so that Core nodes on Docker also have auto updates?

Created a new issue here: filecoin-station/core#420