Infinite loop: CORE_OUTDATED ( 0x6e) and missing debug info in Error msg.

[jcoffland]

Trac	Data
Ticket	1137
Reported by	@bb30994
Status	new
Component	FAHClient
Priority	5

https://foldingforum.org/viewtopic.php?f=74&t=26893#p270041
Occasionally, a WU requires a later version of a FAH_Core than it can download. The FAH Client issues an error: Fah_Core returned: CORE_OUTDATED (110 = 0x6e) and tries again, usually reporting Fah_Core has not changed since last download, aborting core update.

Apparently this process repeats forever when the problem is with the version on the server.

Most (but not all) Cores report a version number, but only if the Core is actually started, which is not possible in this case. The Client does know both version numbers, however and those values are hidden. They should be included in either of the error messages mentioned above for debugging purposes.