8.3.7.5
Bug fixes
[RS-1410] Server Connectivity After Incorrect Password Entry
In this release, we have successfully addressed an issue that prevented the Client from reconnecting after an incorrect password entry. Previously, an overzealous security logic terminated the connection and closed the socket, hindering the Client’s ability to re-establish connection in case of a wrong password entry.
Technical details
Issue: The server’s aggressive security logic shut down the socket, thereby preventing the Client from reconnection attempts after an incorrect password entry.
Resolution
To resolve this issue, we have modified the connection failure logic, ensuring improved handling of incorrect password attempts while allowing the Client to reconnect successfully.
Additionally:
Addressed a bug that allowed connections between different versions of the Server and the Client without warning the user. For example, the Server Version 8.3.6.35(2023.06.29) previously allowed connections from Client versions 8.3.6.0 (2021.01.13) – 8.3.6.34 (2023.05.26) without warning, potentially leading to compatibility issues.
[RS-1429] Preventing Data Corruption in Team Downloads
In this release, we have successfully resolved a critical issue that previously led to database corruption during team downloads. The problem arose specifically when the race comprised both regular participants and teams. In this scenario, while the entire team was expected to cover the same distance, each team member ran a shorter individual distance.
Technical details
Issue: The oversight occurred regarding the usage of teams alongside regular participants within the database. The assumption that the database would exclusively contain team records was incorrect.
Resolution
To address this issue, we have overhauled the logic governing the team download operation. The updated logic now appends the team data to the existing database rather than replacing it entirely. This modification enables teams to coexist seamlessly with regular participant data, ensuring that both types of records are accommodated within the database without compromising integrity.
[RS-1432] Display Issue with Last Lap Time on Announcer Screen
In this release, we have successfully resolved an issue that affected the display of theLast Lap Time on the announcer screen specifically when a back color background was used.
Technical details
Issue: The text color for Last Lap Time, Fastest Lap Time and Average Lap Time was set as the default back color when the when the Average Lap Time was not specified by the user. This caused the Last Lap Time text color to blend with the background, rendering it invisible on a back-colored background.
Resolution
To rectify this issue, we have enhanced the logic by specifically assigning the text color for each individual element based on user input. This ensures that the color of each text element is displayed according to the user’s preferences, thereby resolving the visibility issue experienced with the Last Lap Time on back-colored backgrounds.
[RS-1437] Fix for File Lookup Crash
In this release, we have successfully addressed and resolved an application crash associated with file lookup. The crash was caused by insufficient parameter sanitization before invoking a Windows fileapi.h function, where the input parameter was derived from user input.
Technical details
Issue: The specific Windows function involved, FindFirstFileA (from fileapi.h), necessitates that the input parameter should not be NULL, an invalid string (e.g., an empty string or a string lacking the terminating null character), or end in a trailing backslash. The existing code lacked adequate sanitization for a few cases, leading to the application crash.
Resolution
To rectify this issue, we have implemented additional parameter sanitization checks before invoking the Windows API function. These checks ensure that the input parameters meet the required criteria, thereby preventing the occurrence of a crash during file lookup.
[RS-1439] Fix for Chip Data Processing Crash
In this release, we have successfully addressed an issue that previously resulted in a potential crash during chip data processing. This crash occurred when the external timer reported a runner time on a location that was not mapped to the corresponding RunScore time events.
Technical details
Issue: The issue stemmed from chip time information linked to a location that lacked mapping within the RunScore time events. This situation caused the code to encounter a null pointer, consequently leading to a crash.
Resolution
To resolve this issue, we have implemented changes in the code handling instances where the location information is missing. These alterations prevent null pointer access, thereby eliminating the possibility of a crash during chip data processing.
[RS-1447] Crash on Invalid Entries.ini [Control] Section
In this release, we have successfully resolved a critical issue that caused a crash within the application when encountering an error in the [control] section of the Entries.ini file. Previously, if a user had a SELECT field without an argument, the application would crash instead of providing an informative error message: “Can’t find SELECT field: <argument>.”
Technical details
Issue: The crash stemmed from incorrect initialization of the argument within the [control] section, leading to an access violation in the deblank() method.
Resolution
To address this issue, we have corrected the initialization of the argument by setting it to an empty string upon encountering such instances in the [control] section. This modification ensures that the application handles such errors gracefully by preventing crashes and provides a clear error message to the user indicating the absence of the required argument for the SELECT field.
Improvements:
[RS-1448] Improved Error Message for Missing Include Files.
In this release, we have augmented the error message handling for missing files within the .include command. Previously, if listing files contained commented lines or comments, the displayed line number did not correspond accurately to the editor line, and the path to the problematic file was truncated.
Description
The error message associated with missing files on the .include command inaccurately presented the file name, line number, and failed command when encountering a missing RSM or other files within the .include command. This issue particularly occurred if there were any commented lines or comments in the listing file.
The error message has been refined to include the following details:
– The missing file would include the race subdirectory information
– The specific command argument that failed
– The complete file path in which the .include command encountered the failure.
– The exact line number.
[RS-1449] Prevention of Heap Corruption for Printer-Specific-Information Class.
In this release, we have implemented additional logic aimed at preventing potential heap corruption for the Printer-specific-information class.
Description
In certain rare cases, when the listing file initiated an email or SMS campaign, it could inadvertently delete the printer-specific-information pointer twice. This action resulted in heap corruption, leading to system crashes or freezes. To mitigate this issue, we have refactored the code to adhere to modern C++ coding best practices, effectively eliminating the possibility of heap corruption within this specific class.
[RS-1466] Improved Handling of Connection Loss Between RunScore and MyLaps.
In this release, we have introduced additional logic to streamline the display of error messages, ensuring the presentation of only one error message for lost connections between MyLaps and RunScore.
Description
This enhancement addresses the issue commonly observed in remote areas with low internet quality, where high traffic or an unstable connection could lead to a dropped TCP/IP connection between MyLaps and RunScore. Previously, each occurrence of a lost connection triggered an error message, resulting in multiple error notifications. This situation was particularly challenging for users, especially when away for an extended period.
Enhancements
We have implemented logic that now ensures the display of a single error message even in the event of multiple occurrences of lost connections. This enhancement aims to streamline user experience by presenting a concise and singular notification, alleviating the burden of managing multiple error messages.
[RS-1473] Auto-Recovery for Socket Interruptions from Windows OS.
In this release, we have introduced a valuable enhancement aimed at addressing socket closures initiated by the Windows operating system. This often results in a connection loss between the Server and Client, especially on systems protected by advanced firewalls or experiencing network corruption.
Description
The issue arises when Windows OS forcibly closes the established connection using an internal function. This is typically observed on networks with corruption or systems with stringent firewall settings.
Enhancements
To mitigate this challenge, we have implemented additional logic to ensure the server can auto-recover from interruptions caused by Windows OS-initiated socket closures. In the event of a failure, the application will now provide users with informative messages, detailing actions that can be taken to resolve the issue. These messages will be based on error codes associated with the interruption.