Hi Sara, Strange.. Is that output from the Network tab? Was that tab open when initially making the request?
Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On September 9, 2014 at 2:30:26 PM, Sara Rayburn (sararayb...@gmail.com) wrote: > Hi Christian, > > Well, as it happens, the error only occurs while using Firefox (v. 30). The > user having troubles was relieved to find Chrome as a temporary workaround. > I was able to unminify the code, but it didn't point me to a specific line. > Maybe a firefox thing? I looked for a 500 error, but I don't really even > see a relevant looking request. Here is the log in question, but there's > not much to it. Clicking on the type error gets the big nasty block from > before. > > GET http://www.gravatar.com/avatar/e3a6e9470514467a04cbc94da028458e > [HTTP/1.1 304 Not Modified 796ms] > GET > http://reviewboard.cctechnol.com/static/rb/images/icons.2eed2f830119.png > [HTTP/1.1 304 Not Modified 6ms] > GET > http://reviewboard.cctechnol.com/static/rb/images/l...@2x.4e25cc3cacef.png > [HTTP/1.1 304 Not Modified 6ms] > Use of getPreventDefault() is deprecated. Use defaultPrevented instead. > jquery-1.8.2.min.cfa9051cc0b0.js:2 > GET > http://reviewboard.cctechnol.com/static/rb/images/spinner.73e57937304d.gif > [HTTP/1.1 304 Not Modified 5ms] > The non-standard sendAsBinary method is deprecated and will soon be > removed. Use the standard send(Blob data) method instead. > jquery-1.8.2.min.cfa9051cc0b0.js:2 > TypeError: rsp is null > > On Tuesday, September 9, 2014 4:09:29 PM UTC-5, Christian Hammond wrote: > > > > Hi Sara, > > > > We minify our files by default, making the context less than useful. If > > you’re using Chrome, you should be able to click the error, see that big > > minified file, and then click the little “{}” at the bottom of the window. > > That will un-minify it, updating the error in the console to point to the > > actual line where things failed. If you could then paste that line (and the > > lines surrounding it), that will help narrow things down. > > > > We are getting ready for Review Board 2.0.7, which will display more > > useful errors in the New Review Request page when things go wrong. > > Hopefully it will help with this case as well. > > > > It would also be helpful to see the request/response payloads invoked by > > that page, in order to see where things went wrong. I’d expect one of the > > responses will be a HTTP 500. > > > > Christian > > > > -- > > Christian Hammond - chri...@beanbaginc.com > > Review Board - https://www.reviewboard.org > > Beanbag, Inc. - https://www.beanbaginc.com > > > > > > -- > Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ > --- > Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ > --- > Happy user? Let us know at http://www.reviewboard.org/users/ > --- > You received this message because you are subscribed to the Google Groups > "reviewboard" > group. > To unsubscribe from this group and stop receiving emails from it, send an > email to reviewboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
