Just a little improvement: Currently, the old "Patch(es):" is replaced by "Solution available in patch(es):" For lengthy descriptions, this will cause that the patches info will not he shown in the head-info (as in Issue 31765) 8. Issue 31766

9. Issue 31765

  Perhaps cutting it down to the old text would improve the information provided. TIA, Uli P.S. To get the head-info, the phrase-search has to be started with "issue 3" (watch the lowercase I)

Uli, I'm not getting what the problem is.  Maybe it's been corrected by the indexing job on Sunday night, but I've had a check through both searching keywords and looking at the bug listing. 

Hi Adrian,

When I enter today (following Giannis post) "issue" to get all recent issues, I get the following result-list where the info provided is not so helpful as before: 1. Issue

2. Issue

3. Issue

4. Issue

5. Issue

6. Issue

7. Issue

8. Issue

9. Issue

10. Issue

Sorry, I don't understand how you are getting to this. Can you give some clear instructions. 

Hi Adrian, After last manipulation/reindex, unfortunately "reported issues" list is less usable... :-( Now all issues have title "Issue" while before only the generic ones I mentioned already in my previous request were so generic, as Uli reported. Not knowing details on underlying database and to help you a better understanding I list my usual use cases. What I am usually looking for: 1) Latest issues recorded with whatever status (searching: issue) 2) Latest issues recorded, not yet recognized as bug, usually marked as "Under review" (searching: under review) 3) Latest issues recorded, already recognized as bug, usually marked with "BUG:", including solution timeframe (searching: bug:) 4) All issues related to a specific context, usually a driver (searching: PGS | Postgres | Postgresql | Postgre) or a specific functionality (searching: $columnsyntax) 5) Bugs related to a specific context, usually a driver (searching: PGS | Postgres | Postgresql | Postgre) or a specific functionality (searching: $columnsyntax), including solution timeframe These basic searches could/would be refined using: - Specific Uniface version (example: 9 versus 10) - Specific platform identification (example: Windows versus Linux | Unix versus VMS) - Sorting from older to younger and viceversa The following entries are less important to me but sometimes are needed: - List of bug solved in a specific release - List of patches included in a service pack or in a release Hope it helps... Regards, Gianni

Gents, we are not going to make any significant changes to the site. As previously mentioned, it's going to be replaced with the portal from the Atlassian products which we use internally. I understand that is coming in the coming few months.  I am not understanding what is the 'real problem', what has changed from before and the steps to actually see it.

Hi Adrian - go to Support -> Reported Issues - select "show 100" per page - enter "issues" - press "Search"   Since last sunday, the returned information is not too useful, compared to the one a week before.

Thanks Uli.  Is this a real use case?  When I search something like PostgresSQL, which is what I would call a specific search profile, then I see results that I would expect. 

Hi Adrian, I think you have seen 100 issues with just the same boilerplate text in the meantime. further investigation revealed that your indexer seems to scan the php pages; and there is a pretty significant change in the structure which may have caused the problem. Here are my findings: last week, the unifaceinfo.com/fixes/issuelist/31765.php read BUG: 31765 - UNIFACE debugger shows only the first character of an error message Status: Planned for resolution in 9.7.04 Patch(es): Symptoms: UNIFACE debugger shows only the first character of an error message An error is displayed when the udbg.exe is not in the bin folder and the 4gl contains a debug statement. The error message between bracket < T > contains only one character. This makes it hard to solve the issue.   The format of the issue is now:

Issue 31765  —   Uniface Debugger only shows the first character of a startup error message

Status:   Planned for resolution in 9.7.04 Solution available in patch(es):     Description:

 Summary: Uniface Debugger only shows the first character of a
          startup error message

 Environment:
 +Uniface Version  : 9.x / 10.x
 +Operating System : Windows
 +Database         : DBMS independent

 Reproduction:
 1. Force a debugger startup error, for instance by renaming
    the file udbg.exe. The file udbg.exe resides in folder
    <Uniface installation folder>\\common\\bin.
 2. Start a form containing a ProcScript debug statement.
 3. Start the Debugger.
 4. Press Gold + M to open the Message Frame.

 Actual Result:
 The error message between bracket < T > contains only one
 character; this makes it hard to analyze and solve the
 issue.

 Expected Result:
 The error message should be complete.

Hi Adrian, this excercise I do each sunday morning is "a real usecase" remember all the times where I reported missing updates of the index, missing patches info etc. I started scanning the Known Bug List in April 1993 when I worked as Head of the german Uniface Helpdesk to give our customers a better service: No need to provide a testset if the issue is already known. As Gianni has explained in his post, senior uniface consultants like me scan the "new" reported issues on a weekly base to get informed what may cause trouble (so one wouldn't suggest it to the customer) and perhaps what got a patch in the meantime or (sadly) got a Status: Will not be resolved.

Adrian Gosbell said ... it's going to be replaced with the portal from the Atlassian products which we use internally. I understand that is coming in the coming few months. ...

Adrian, That's why I've explained my use cases...to let ULab knows what usages we do. Thanks for your support! Gianni

This example is from January 2018 worked all the time ended last Saturday. Just to show what we have lost on information given with the hitlist returned: 1. Issue 31731 - Need $random proc function for use with block ciphers Issue 31731 BUG: 31731 - Need $random proc function for use with block ciphers Status: Under review by Uniface B.V. Patch(es): Symptoms: The documentation on block ciphers suggests that for https://unifaceinfo.com/fixes/issuelist/31731.php - 50.8kb 2. Issue 31730 - UF10: exception when opening migrated Form component Issue 31730 BUG: 31730 - UF10: exception when opening migrated Form component Status: Under review by Uniface B.V. Patch(es): Symptoms: Opening a migrated Form component in Uniface 10 IDE may https://unifaceinfo.com/fixes/issuelist/31730.php - 55.1kb 3. Issue 31729 - Activating a not "public web" operation from the pre-reques... Issue 31729 BUG: 31729 - Activating a not "public web" operation from the pre-request trigger fails Status: Under review by Uniface B.V. Patch(es): Symptoms: When you use the new assignment https://unifaceinfo.com/fixes/issuelist/31729.php - 50.7kb 4. Issue 31728 - Setting $NET_TIMEOUT idl=x resets the defaults of cct and s... Issue 31728 BUG: 31728 - Setting $NET_TIMEOUT idl=x resets the defaults of cct and sct to zero Status: Under review by Uniface B.V. Patch(es): Symptoms: Setting $NET_TIMEOUT idl=x resets the https://unifaceinfo.com/fixes/issuelist/31728.php - 50.4kb 5. Issue 31727 - PostgreSQL: Retrieve profile containing wildcard fails for ... Issue 31727 BUG: 31727 - PostgreSQL: Retrieve profile containing wildcard fails for VC , VW fields. Status: Under review by Uniface B.V. Patch(es): Symptoms: Summary: PostgreSQL: Retrieve https://unifaceinfo.com/fixes/issuelist/31727.php - 50.8kb 6. Issue 31726 - Retrieve profile fails for W,VW fields when starting with c... Issue 31726 BUG: 31726 - Retrieve profile fails for W,VW fields when starting with certain characters Status: Under review by Uniface B.V. Patch(es): Symptoms: Summary: Uniface: Retrieve for https://unifaceinfo.com/fixes/issuelist/31726.php - 51.7kb 7. Issue 31725 - Component with inner entity ?ENTITY migrated to Uniface 10 ... Issue 31725 BUG: 31725 - Component with inner entity ?ENTITY migrated to Uniface 10 causes exception Status: Planned for resolution in 10.3.01 Patch(es): Symptoms: Summary: Component with https://unifaceinfo.com/fixes/issuelist/31725.php - 51.4kb 8. Issue 31723 - Content type application/x-www-form-urlencoded can cause pr... Issue 31723 BUG: 31723 - Content type application/x-www-form-urlencoded can cause problem for WAF Status: Under review by Uniface B.V. Patch(es): Symptoms: Symptom Summary: Uniface: Uniface https://unifaceinfo.com/fixes/issuelist/31723.php - 51.3kb 9. Issue 31722 - Changing the index of a Struct node can cause crash Issue 31722 BUG: 31722 - Changing the index of a Struct node can cause crash Status: Under review by Uniface B.V. Patch(es): Symptoms: Summary: Changing the index of a Struct node can cause a https://unifaceinfo.com/fixes/issuelist/31722.php - 51.6kb 10. Issue 31721 - UF10: Incorrect Compiler warnings, listings and Module Info... Issue 31721 BUG: 31721 - UF10: Incorrect Compiler warnings, listings and Module Info in specific cases Status: Under review by Uniface B.V. Patch(es): Symptoms: Under the following conditions, https://unifaceinfo.com/fixes/issuelist/31721.php - 52.4kb

What is it like today? Some changes were made last night. 

The hitlist I got entering "issue" is still far away from my example which reads: 1. Issue 31731 – Need $random proc function for use with block ciphers Issue 31731 BUG: 31731 – Need $random proc function for use with block ciphers Status: Under review by Uniface B.V. Patch(es): Symptoms: The documentation on block ciphers suggests that for https://unifaceinfo.com/fixes/issuelist/31731.php – 50.8kb   8. Issue 31766

9. Issue 31765

10. Issue 31764

Hi Adrian, I just tested phrase-search "Issue 3".

But now, the hitlist returned the head-info (IssueID, Title, Status, Patches) again as: 8. Issue 31766

So we got back the comfort of having all important information directly in the hitlist. Thanks to you and your team for "bringing back the good times", Uli