[GRADLE-1870] GUI "find in output" function badly broken Created: 26/Oct/11  Updated: 16/Jan/17  Resolved: 16/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-5
Fix Version/s: None

Type: Bug
Reporter: Blaine Simpson Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: PNG File gradleGuiSearch-broken.png    

 Description   

The "find in output" button does not search for the string that you tell it to search for. It doesn't seem to be searching for anything that makes any sense, regardless of the status of the "Regular Expression" checkbox.

See attached screen shot "gradleGuiSearch-broken.png". You can see that I am searching for literal string "resolution" and it has hit on "acts dl 0ms". If I hit the "Find next match" button repeatedly, it continues forward, matching garbage including "----------".

Hey, I just noticed something. The false matches actually are segments of the correct length. Doesn't know how to match the specific characters, but it knows how to match the right quantity of characters.

 Comments   
Comment by Blaine Simpson [ 26/Oct/11 ]

The search works properly on my Linux workstation:

Linux beyla 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux
Aggressively patched OpenSUSE 11.4

Comment by Blaine Simpson [ 27/Oct/11 ]

I did more testing on this. This bug is related to scrolling.

I haven't tested horizontal scrolling, and I don't know the exact criteria, but it is something like: If the searched-for expression is not now visible in the view-port and is not visible in the top view-port (i.e. if you scrolled all the way to the top), then the bug will be triggered.

I suspect that this has to do with calculation of offsets into the content of the widget, with EOLs or scrolling offsets not being calculated correctly, or in a platform-specific way.

I have only tested this scrolling stuff using "gradle" from Windows Msys and using "gradle.bat". Same symptoms either way. I don't have access to a UNIX workstation this morning.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Blaine Simpson [ 15/Nov/16 ]

This is a clear bug on Windows.

I just re-tested with Gradle 3.1 on Windows 10. To reproduce, run either "gradle --gui" or "gradlew --gui". In bottom pane, click magnifying glass and search for something that occurs (in bottom pane) but which does not occur on the first screenful.

Comment by Benjamin Muschko [ 16/Jan/17 ]

The Gradle GUI has been deprecated and is scheduled to be removed with Gradle 4.0. We are not going to work on this issue anymore.

Generated at Wed Jun 30 12:06:35 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.