online bug search in Uniface.info

Author: adrian.gosbell@synapse-i.jp (Adrian Gosbell)

After a false start, we are close to getting the known bug list, with a search engine hosted on Uniface.info. I'm hoping Tim will set it live this week.  Those of us who have been around Uniface for a while will remember this used to be available on previous sites, and even delivered in the product. It's something we wanted to make available here but we had to work through a number of challenges.  Access will require the user to be a registered member of Uniface.info and to be logged in.  The source of the lists will be updated on a Saturday evening (Amsterdam time zones) and the re-indexing will take a number of hours and could cause the site to slow down. We determined Saturday evening is probably the minimal impact time to do this.  The lists are will go back to the Uniface 7 era, but there isn't a hard cut off separating between a particular version, we just wanted to ensure we had Uniface 9 covered. If the re-indexing or overall performance of the search starts to drop, we'll purge the older issues.  We think the search engine, and the results are working pretty well based on our testing,  I think I've mentioned this previously, but we're trying to stay with out of the box functionality for this site so that we don't run into issues with upgrades. One thing we did tweak within the search was the display sequence is from the highest to the lowest bug number. This implies that newer issues will be listed first.  The data comes from one of our internal systems, and we know some of the text might not be completely perfect, for most of the team, English is the second (or third) language, for example at the moment I can only think of one native English speaker in development, and knowing where he comes from, even that's open to debate. Feedback is welcome, we'll fix up blatant errors, but trivial things won't be treated as a priority. 

22 Comments

  1. Looks like its just gone live, its the final option under the support tab. 


    Author: Adrian Gosbell (adrian.gosbell@synapse-i.jp)
  2. looks like the index isn't updated since a longer time (or at least is not transfered to production here). Maximum issue returned by a query is still 31005 as it was a couple of weeks ago.

     


    Author: ulrich-merkel (ulrichmerkel@web.de)
  3. ... another weekend passed by, but no improvement on the max. issue front. So back to the old manual "bookkeeping".


    Author: ulrich-merkel (ulrichmerkel@web.de)
  4. ulrich-merkel said looks like the index isn't updated since a longer time (or at least is not transfered to production here). Maximum issue returned by a query is still 31005 as it was a couple of weeks ago.

     

    Thanks for flagging this, it appears that there is an indexing glitch. It's being worked on, we are trying to balance this without causing any dramatic slowdowns on the site as the reindexing process is resource intensive.  I was informed this morning that we hope to have this resolved this week. 


    Author: Adrian Gosbell (adrian.gosbell@synapse-i.jp)
  5. looks like we have an updated index right now (assume it was a manual fix)., hope we weill get a recreated one by "the routines" next week.


    Author: ulrich-merkel (ulrichmerkel@web.de)
  6.  We have a fix which has been implemented and should now be part of the regular processes for reindexing. 


    Author: Adrian Gosbell (adrian.gosbell@synapse-i.jp)
  7. I was just searching for a specific topic within the known bug list. Currently I see in the result list only an issue number and some text passages. I think, instead of issue number the "Bug description" and "Status" (like: solved in 8.4.xxx) are much more informative within the result list. Thanks Wolfgang


    Author: gypsilon (wva@gypsilon.de)
  8. gypsilon said I was just searching for a specific topic within the known bug list. Currently I see in the result list only an issue number and some text passages. I think, instead of issue number the "Bug description" and "Status" (like: solved in 8.4.xxx) are much more informative within the result list. Thanks Wolfgang

     that is a good idea, not sure how easy to work on, but I'll certainly ask. 


    Author: Adrian Gosbell (adrian.gosbell@synapse-i.jp)
  9. gypsilon said Currently I see in the result list only an issue number and some text passages. I think, instead of issue number the "Bug description" and "Status" (like: solved in 8.4.xxx) are much more informative within the result list. Thanks Wolfgang

    Hi Wolfgang, the current "text passages" already show the info you asked for (Bug title, Status, Patches, and a link if you need the details): Issue 31036 BUG: 31036 - Switching off ProgressBar's "Smooth" attribute doesn't have any effect Status: Planned for resolution in 9.6.07 Patch(es): Symptoms: Doesn't matter whether the Directly returning the "long version" would drastically increase network traffic and reduce performance for all users. A dITo project ("DUI" = dITo Uniface Issues) already works on some "post processing" of the information provided. Greetings from Frankfurt/Germany, Uli


    Author: ulrich-merkel (ulrichmerkel@web.de)
  10. ulrich-merkel said
    gypsilon said Currently I see in the result list only an issue number and some text passages. I think, instead of issue number the "Bug description" and "Status" (like: solved in 8.4.xxx) are much more informative within the result list. Thanks Wolfgang
    Hi Wolfgang, the current "text passages" already show the info you asked for (Bug title, Status, Patches, and a link if you need the details): Issue 31036 BUG: 31036 - Switching off ProgressBar's "Smooth" attribute doesn't have any effect Status: Planned for resolution in 9.6.07 Patch(es): Symptoms: Doesn't matter whether the Directly returning the "long version" would drastically increase network traffic and reduce performance for all users. A dITo project ("DUI" = dITo Uniface Issues) already works on some "post processing" of the information provided. Greetings from Frankfurt/Germany, Uli

    I think I'd wait for the web site manager to determine a solution. 


    Author: Adrian Gosbell (adrian.gosbell@synapse-i.jp)
  11. May I suggest if you want to fulfill Wolfgangs wish, to do that in form of an additional  option ("current"/"verbose"). As I mentioned, all the infos Wolfgang want is in the current information string already. There is a group of people using the current format of condensed info provided with the hitlist and, with some postprocessing, are quite happy with the information they get about changes on the "Known Bug List".


    Author: ulrich-merkel (ulrichmerkel@web.de)
  12. postprocessing means: Copy the hitlist(s) to a textfile; use some filters to extract important information


    Author: ulrich-merkel (ulrichmerkel@web.de)
  13. As one output we convert the information line in some TAB-separatedd volume so in EXCEL we get columns for BugNr,Title, Status, Patch(es), Trailer Think this will be near to the request from Wolfgang   Example: Issue 31036 BUG: 31036 – Switching off ProgressBar’s “Smooth” attribute doesn’t have any effect Status: Planned for resolution in 9.6.07 Patch(es): Symptoms: Doesn’t matter whether the  Will be converted to (\t denotes a TAB): 31036\tSwitching off ProgressBar’s “Smooth” attribute doesn’t have any effect\tPlanned for resolution in 9.6.07\t\tSymptoms: Doesn’t matter whether the


    Author: ulrich-merkel (ulrichmerkel@web.de)
  14. ulrich-merkel said As one output we convert the information line in some TAB-separatedd volume so in EXCEL we get columns for BugNr,Title, Status, Patch(es), Trailer Think this will be near to the request from Wolfgang   Example: Issue 31036 BUG: 31036 – Switching off ProgressBar’s “Smooth” attribute doesn’t have any effect Status: Planned for resolution in 9.6.07 Patch(es): Symptoms: Doesn’t matter whether the  Will be converted to (\t denotes a TAB): 31036\tSwitching off ProgressBar’s “Smooth” attribute doesn’t have any effect\tPlanned for resolution in 9.6.07\t\tSymptoms: Doesn’t matter whether the

    Does this comply with the site terms and conditions? 


    Author: Adrian Gosbell (adrian.gosbell@synapse-i.jp)
  15. The bug search shows in each result an excerpt of the page where the search term has been found. This is to quickly show the context of that term on that page, and is how it's usually done (e.g. Google, Bing). For certain search terms, this means the Bug Status/Description won't be visible, because they are not close enough to the place of the search term in the text. Try searching for "property": 1. Issue 31036

    widget's "Smooth" property is set or not, the progress status is always shown as a smooth bar. Workaround: Solution:
    http://unifaceinfo.com/fixes/issuelist/31036.php - 46.2kb
     
    I've included two screenshots which show the Bug Description in the title, and either the context (old way) or the Bug Status.
     
    Let me know if any of this would be an improvement.
     
     

    Author: admin (support@tbto.nl)
  16. admin said 
    [...] which show the Bug Description in the title, and [...] the context (old way) [...].

    I personally like the first (suggested) improvement: Bug Description in the title plus the context. Thanks, Daniel


    Author: diseli (daniel.iseli@uniface.com)
  17. I agree with daniel: having the title more prominent makes searching a specific problem in the hitlist much easier and we still have the old context info.


    Author: ulrich-merkel (ulrichmerkel@web.de)
  18. All right, the current search results include the Bug Description as title, while keeping the context.


    Author: admin (support@tbto.nl)
  19. Hello admin, Thank you. This all looks good and is useable for me. Wolfgang


    Author: gypsilon (wva@gypsilon.de)
  20. ulrich-merkel said looks like we have an updated index right now (assume it was a manual fix)., hope we weill get a recreated one by "the routines" next week.

    After the "night of the blood moon", it seems we have an index up to "Issue 31071"


    Author: ulrich-merkel (ulrichmerkel@web.de)
  21. ulrich-merkel said
    ulrich-merkel said looks like we have an updated index right now (assume it was a manual fix)., hope we weill get a recreated one by "the routines" next week.
    After the "night of the blood moon", it seems we have an index up to "Issue 31071"

    why do you think we have an index issue Ulrich? 


    Author: Adrian Gosbell (adrian.gosbell@synapse-i.jp)
  22. Adrian Gosbell said  We have a fix which has been implemented and should now be part of the regular processes for reindexing. 

    Last monday max. iIssue was increased to 31071, today it's 31075: looks like the fix IS now part of the regular process.


    Author: ulrich-merkel (ulrichmerkel@web.de)