Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Current datetime being used on %RESCAN of message areas instead of created datetime

See original GitHub issue

When requesting a rescan of messages from an FTN uplink messages are imported with the current date/time instead of the created date/time

Environment

I am using Node.js v12.x LTS or higher
npm install or yarn reports success
Actual Node.js version (node --version): v12.18.3
Operating system (uname -a on *nix systems): Linux bbs 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 GNU/Linux
Revision (git rev-parse --short HEAD): a4883f0

Expected behavior Messages/List messages - Actual date/time when message created originally should be displayed.

Actual behavior Messages/List messages - Todays or imported date/time is displayed.

Steps to reproduce Rescan an area from an uplink. Eg: %RESCAN FSX_GEN When polled and tossed/imported list the messages in the area.

Issue Analytics

State:
Created 3 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

deepthawcommented, Nov 17, 2020

I’ve attached a partial response to a %RESCAN request. This rescan was requested at approximately 11:27AM CST on November 17, 2020 and was a request for 10 days from all fsxNet echos.

0000ffe4.zip

1reaction

louisnorthmorecommented, Sep 4, 2020

@NuSkooler - I’ll take a look at this