View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005527||SUMo||Bug||public||2019-06-02 20:47||2020-06-03 17:59|
|Target Version||Short term|
|Summary||0005527: SUMo server looses Strawberry Perl product name and version records within less than 3 hours|
|Description||I've installed the public domain distribution Strawberry Perl and the open source distribution Lyx which includes Strawberry Perl as a component. SUMo detects both. (It doesn't detect Lyx itself as Lyx has its version information not in a standard Windows version info format except for its uninstaller but otherwise in folder name. A bug report has been entered on the LyX project too.) I further updated of Strawberry Perl version 184.108.40.206 to 220.127.116.11 in 64 bit edition. A look at the SUMo report reveals that while I've installed the 64 bit edition on my 64 bit operating system edition, Lyx has installed a 32 bit edition of itself and its component Strawberry Perl. A closer look at this report, version info and SUMo server showed that SUMo check updates SUMo server records accordingly including user flag and as reported in the related issue. |
When keeping SUMo client open for hours, and either refreshing SUMo server lookup or repeating SUMo server lookup, it shows that the versions and editions already detected almost 3 hours before are no longer known by SUMo server claiming that NO SUMo user has a 32 bit edition installed, this publisher has only a SUMo user with the 64 bit edition of the product installed and NO SUMo user has the actual version in 64 bit installed that SUMo server had reported just after SUMo client check and still reported in SUMo client! Accordingly, SUMo server doesn't attach the user flag although the query was started off my SUMo Pro installation within this report!
Please fix reporting of the 32 bit edition by turning to the product name instead of file description for SUMo!
When SUMo server looses its product information (probably due to some expiration) a lookup doesn't provide an error message nor does it retain the query as prefilled value for the standard query page. I perfer if this behaviour of SUMo server changes to provide a one line warning which query didn't find any results above or below the form field of SUMo server standard query page and prefill this editable form field with the unsuccessful query. It makes sense to modify the query which is easier when prefilled.
|Additional Information||As opposed to the related issue, the loss of record is not only for the 32 bit edition but also for the 64 bit edition and in even less time as observed in the related issue.|
|Tags||No tags attached.|
|2019-06-02 20:47||wolf||New Issue|
|2019-06-02 20:47||wolf||Issue generated from: 0005524|
|2019-06-02 20:47||wolf||Relationship added||related to 0005524|
|2019-06-02 21:00||Kyle_Katarn||Relationship added||related to 0004278|
|2019-06-02 21:00||Kyle_Katarn||Assigned To||=> Kyle_Katarn|
|2019-06-02 21:00||Kyle_Katarn||Status||new => acknowledged|
|2019-06-02 21:00||Kyle_Katarn||Target Version||=> Short term|
|2020-06-03 17:59||Kyle_Katarn||Status||acknowledged => feedback|
|2020-06-03 17:59||Kyle_Katarn||Note Added: 0003955|