Windows VC reports BN as synced before sync completes

[michaelsproul]

Description

Testing just now with a Windows VC connected to a Windows BN on Prater, I'm seeing the VC report the BN as synced before it finishes.

BN:

May 26 17:46:29.891 INFO Syncing                                 est_time: 3 hrs 35 mins, speed: 18.66 slots/sec, distance: 241460 slots (4 weeks 5 days), peers: 50, service: slot_notifier
May 26 17:46:41.860 INFO Syncing                                 est_time: 3 hrs 35 mins, speed: 18.67 slots/sec, distance: 241269 slots (4 weeks 5 days), peers: 50, service: slot_notifier

VC:

May 26 17:47:28.735 INFO Lighthouse started                      version: Lighthouse/v1.3.0-5d9a1bc
May 26 17:47:28.742 INFO Configured for network                  name: prater
May 26 17:47:28.744 INFO Starting validator client               validator_dir: "C:\\Users\\Michael\\.lighthouse\\prater\\validators", beacon_nodes: ["http://localhost:5052/"]
May 26 17:47:28.748 INFO HTTP metrics server is disabled
May 26 17:47:28.749 INFO Completed validator discovery           new_validators: 0
May 26 17:47:29.376 INFO Initialized validators                  enabled: 0, disabled: 0
May 26 17:47:29.475 WARN No enabled validators                   hint: create validators via the API, or the `lighthouse account` CLI command
May 26 17:47:29.688 INFO Connected to beacon node                endpoint: http://localhost:5052/, version: Lighthouse/v1.3.0-5d9a1bc/x86_64-windows
May 26 17:47:29.689 INFO Initialized beacon node connections     available: 1, total: 1
May 26 17:47:29.691 INFO Loaded validator keypair store          voting_validators: 0
May 26 17:47:29.692 INFO Pruning slashing protection DB          msg: pruning may take several minutes the first time it runs, epoch: 14341
May 26 17:47:29.693 INFO Completed pruning of slashing protection DB
May 26 17:47:29.694 INFO Genesis has already occurred            seconds_ago: 5507249
May 26 17:47:29.695 INFO Block production service started        service: block
May 26 17:47:29.695 INFO Attestation production service started  next_update_millis: 6311, service: attestation
May 26 17:47:29.696 INFO HTTP API server is disabled
May 26 17:47:51.949 INFO Connected to beacon node(s)             synced: 1, available: 1, total: 1, service: notifier
May 26 17:47:51.952 INFO No validators present                   msg: see `lighthouse account validator create --help` or the HTTP API documentation, service: notifier
May 26 17:47:54.024 INFO Connected to beacon node(s)             synced: 1, available: 1, total: 1, service: notifier
May 26 17:47:54.027 INFO No validators present                   msg: see `lighthouse account validator create --help` or the HTTP API documentation, service: notifier
May 26 17:48:06.008 INFO Connected to beacon node(s)             synced: 1, available: 1, total: 1, service: notifier
May 26 17:48:06.011 INFO No validators present                   msg: see `lighthouse account validator create --help` or the HTTP API documentation, service: notifier

Weirdly the /eth/v1/node/syncing endpoint returns true:

{
  "data": {
    "is_syncing": true,
    "head_slot": "216576",
    "sync_distance": "242352"
  }
}

Linux doesn't seem to display the same behaviour, but I'll need to do more thorough testing with the exact version.

Version

Lighthouse/v1.3.0-5d9a1bc