Closed Bug 271604 Opened 20 years ago Closed 14 years ago

Talkback site should allow search by date only

Categories

(mozilla.org :: Talkback Server & Webtool, task, P1)

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: netdragon, Assigned: jay)

Details

(Whiteboard: [quicksearch 2.0])

On http://talkback-public.mozilla.org/ if I fill out nothing but start date and
end date, it should accept the query. Let's say I want to search for crash
reports in the last hour. It should be able to do that.
Taking bug.  This is something that I've been wanting to implement.  So I will
get started on it when I find some time.
Status: NEW → ASSIGNED
Marking fixed.  

You can now do queries by vendor+product+platform+build or date range without
specifying a stack signature, comment or url string.  You have to at least
specify a build id or a date range...to make sure we don't query for ALL the
incidents (which will most likely hang the browser or take down the app right
now becuase there are over 1 million incidents in the db).  Give it a shot and
let me know if you see any problems.  If you do, reopen the bug.  Thanks!
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
It shouldn't clear the form if it finds nothing between certain dates. That
makes it hard to change a tiny bit of the date.

It also seems to take a long time to search for ALL between 11/22/2004 and
11/23/2004, then I get:

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from
fulfilling this request.

exception

javax.servlet.ServletException
	org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:867)
	org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:800)
	org.apache.jsp.fastfind_jsp._jspService(fastfind_jsp.java:469)
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:133)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:311)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:856)

root cause

java.lang.OutOfMemoryError

note The full stack trace of the root cause is available in the Tomcat logs.
Apache Tomcat/5.0.19
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Clearing the form is another issue, log a separate bug on that.

In terms of the error you saw, I am not seeing it.  Might have just been a temp.
server overload.  Try it again... 

NOTE: The Talkback tools are something I orginally created for myself to help do
topcrash analysis...but we decided to open it up to the public so others may
look into the Talkback data.  I have not spent a lot of time optimizing the
code, so it will have a few glitches.  If you ever run into an error, just wait
a bit and refresh or go to the main page and run the query again.  If something
bad is happening a lot and is easily reproducible, please log a bug on it and I
will try my best to fix the problem. Thanks!
Brian:  Also, the query you were trying to run returned ~55,000 incidents for
me, try narrowing it down a little more by specifying the product (e.g.
Firefox10, MozillaTrunk), that will help avoid memory issues.  I don't see why
you would need to be looking at that many incidents at once.
I don't think the clearing the forms issue is a problem because you can hit back.

Ouch. I was just testing, actually. I did a shorter timespan and it worked fine :-)

Is there any way it could give a warning if there are going to be a lot of
incidents returned?
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
Sorry Brian... it's been a long day.  Anyway, after my last post, I realized
that the tool itself was broken... I'll be fixing it tomorrow.  And yes, we need
to figure out a good way to deal with large numbers of results (I think that is
the reason I originally stayed away from such simplified queries)...but now that
others are using it, I must deal with such scenerios.  

Thanks again for all your help.  Since I'm the only one working on the Talkback
tools, I'm trying my best to keep up with all your latest findings! :-)  Let me
know if you want to help out with the development.  I've been meaning to get the
code checked into CVS somewhere so others can start adding features and help
clean up my code (it's getting messy).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Ok, I'm going to spend some time on this in the next week or so while I revamp
the Talkback website, so I'll see what I can do.
Status: REOPENED → ASSIGNED
Product: Core → mozilla.org
Version: Trunk → other
(this would be nice)
Adding [quicksearch 2.0] to status whiteboard to track features I'm going to try
to get into the next version of th query tools.
Priority: -- → P1
Whiteboard: [quicksearch 2.0]
Talkback isn't used anymore:
R.Invalid now.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.