Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate & fix wrong-commander EDSM data #1217

Merged
merged 13 commits into from
Aug 5, 2021

Conversation

Athanasius
Copy link
Contributor

This is aimed at addressing #1134 .

To start with it's adding some logging, including the new EDMarketConnector.exe --trace-on ... CL arg for activating specific TRACE logging.

This is just the parsing and storage of the options for now.
* trace-on 'edsm-cmdr-events' for how Commanders, their API keys and
  using them are handled.  See #1134
* trace-on 'edsm-locations' for what was commented-out logging to do
  with ensuring code reacted correctly to any change of system.
* mypy/types-* seem to have had changes causing extra carping, so
  addressing that.
We MUST attempt flushing pending events in case of commander change.
We need to trigger off ShutDown and Commander/LoadGame to empty pending,
so need to *see* them in the worker.
…ould_send()

* Ensure we have the discarded_events list *before* starting to consume
  events.  There's the *same* risk as before with EDSM just being down
  and us queueing up more and more, just now it will be in the worker
  queue rather than pending.

* We need to test for some events in should_send() that are in the
  discard list, and thus will never be in the `entries` (pending) passwd
  in, so pass in the name of the latest event as well.
This prevents literally sending an empty data to EDSM if we trigger
sending due to Shutdown.
@Athanasius Athanasius marked this pull request as ready for review August 5, 2021 15:41
@Athanasius Athanasius merged commit c4c859e into develop Aug 5, 2021
@Athanasius Athanasius deleted the fix/1134/edsm-wrong-balance branch August 5, 2021 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants