search

ACRA / acralyzer

Open source backend for ACRA reports.
GNU General Public License v3.0
489 stars 90 forks source link

Don't see any "Bugs" / How to create Bugs #53

Closed dodgex closed 7 years ago

dodgex commented 10 years ago

Hello,

some days ago we installed Acralyzer for our App. We got some Reports, but we can't get the "Bugs" stuff to work.

Should Bugs be created by Acralyzer or is there something we need to do? the Acralyzer user manual is not very helpfull. :(

We have some Reports that are from the same user with the same device, and the exception is also the same. but there is no Bug created and we can't find a way to assign the reports to a new bug.

Thanks

KevinGaudin commented 10 years ago

Bugs are generated automatically by Acralyzer.

Do you use a customReportContent configuration ? If so, check that you include the following fields (now documented here):

dodgex commented 10 years ago

no, i don't use customReportContent

this is my configuration

@ReportsCrashes(//
formKey = "", // will not be used
httpMethod = Method.PUT, //
reportType = Type.JSON, //
formUriBasicAuthLogin = "xxxx", //
formUriBasicAuthPassword = "xxxxxx", //
formUri = "http://xxx/acra-xxx/_design/acra-storage/_update/report", //
mode = ReportingInteractionMode.SILENT)
dodgex commented 10 years ago

Any idea what else could prevent Acralyzer to generate Bugs?

KevinGaudin commented 10 years ago

Would you let me have a look at your CouchDB instance ? Please drop a mail with its URL to kevin.gaudin@gmail.com.

mndfcked commented 10 years ago

Same problem here. The Report per day etc. bars aren't showing up either. I get this messages in the couchdb.log too.

[Tue, 13 Aug 2013 22:05:26 GMT] [info] [<0.30279.0>] xxxxxxxx - - PUT /xxxxxx/_design/acra-storage/_update/report/262630bc-bf03-45b9-997b-bd9e2e1cac29 201
[Tue, 13 Aug 2013 22:05:26 GMT] [info] [<0.9008.0>] OS Process #Port<0.2750> Log :: function raised exception (new TypeError("reportDate.getTime is not a function", "", 13)) with doc._id 262630bc-bf03-45b9-997b-bd9e2e1cac29
[Tue, 13 Aug 2013 22:05:26 GMT] [info] [<0.9008.0>] OS Process #Port<0.2750> Log :: function raised exception (new TypeError("crashDate.getFullYear is not a function", "", 6)) with doc._id 262630bc-bf03-45b9-997b-bd9e2e1cac29
[Tue, 13 Aug 2013 22:05:26 GMT] [info] [<0.9008.0>] OS Process #Port<0.2750> Log :: function raised exception (new TypeError("crashDate.getFullYear is not a function", "", 6)) with doc._id 262630bc-bf03-45b9-997b-bd9e2e1cac29

But I don't know if this is connected.

dodgex commented 10 years ago

problem still present, it starts to be an ugly issue, as we have some "reports" that occur (very!) often and having them grouped would be awesome...

currently we are at 10k+ reports.

KevinGaudin commented 10 years ago

Sorry, I was on vacation and have not been able to dedicate any time to my projects.

The errors reported by @mndfcked are due to a javascript compatibility issue with date parsing.

KevinGaudin commented 10 years ago

@mndfcked, did you install couchdb on your own server? You should try to update spidermonkey.

Tyde commented 10 years ago

I am getting the same errors as @mndfcked. Now I don't know how to update spidermonkey. Is that the js.x86_64 package?

dodgex commented 10 years ago

My issue is still present... :(

KevinGaudin commented 10 years ago

I'm really sorry guys, I have very few available time to dedicate to ACRA/Acralyzer these days and it certainly won't get much better before a few months for personnal reasons.

The problem here is that on the CouchDB JS side we make a couple date/time transformations, starting by parsing an ISO date string. This parsing is not equally supported on all versions of JS engines and especially the various versions of SpiderMonkey (Mozilla's JS engine). The problem is that I can't easily find an exact version of SpiderMonkey (or another engine) from where this particular compatibility issue is solved.

Acralyzer was developed on both IrisCouch and Cloudant where there is no such issues, I made a presentation at DroidCon on a self installed Windows CouchDB where I had no such issue, I still have to test on the Debian server I have setup (with git //github.com/iriscouch/build-couchdb) to provide the distribution databases to see if I get this issue.

Another solution would be to work around these date/time transformations with a different implementation but I still have to find time for this.

davcamer commented 10 years ago

@dodgex I work with an Acralyzer instance that has millions of reports in it. It takes up to 10 minutes for the bugs to load in the tab on the dashboard, although the reports tab runs quite quickly. You could see if anything is loading by using the network tab of Chrome developer tools (or firebug, or Safari developer tools, or something in IE). I would be interested to know if your bugs are just loading very slowly, or if they are really missing.

dodgex commented 10 years ago

i just tested... both bugs & reports are currently loading for 5 minutes.

imho this is a "no go" :) but as i'm already switchted to another reporting tool, it does not realy care that much.

KevinGaudin commented 10 years ago

There is a difference in the handling of bugs and reports.

Bugs are all loaded in the browser memory whereas reports are loaded page by page. This was done this way for easier sorting and filtering for bugs as I was expecting a lower number of bugs compared to reports.

With your "millions of bugs" I guess this should be rethought... Our you could switch to a new acra-storage instance sometimes. Le 1 nov. 2013 05:52, "Dave Cameron" notifications@github.com a écrit :

@dodgex https://github.com/dodgex I work with an Acralyzer instance that has millions of reports in it. It takes up to 10 minutes for the bugs to load in the tab on the dashboard, although the reports tab runs quite quickly. You could see if anything is loading by using the network tab of Chrome developer tools (or firebug, or Safari developer tools, or something in IE). I would be interested to know if your bugs are just loading very slowly, or if they are really missing.

— Reply to this email directly or view it on GitHubhttps://github.com/ACRA/acralyzer/issues/53#issuecomment-27547656 .

KevinGaudin commented 10 years ago

There can also be a longer delay when accessing these lists for the first time after an update on a large number of reports. This is due to couchdb rebuilding its indexes. It should load faster then...

davcamer commented 10 years ago

We've already changed our local deployment to use stale=update_after for the dashboard. Have some other performance/scale tweaks that we are working on locally.

KevinGaudin commented 10 years ago

It would be really interesting to have some details about these tweaks if you can get some time to share them ;-)

davcamer commented 10 years ago

@KevinGaudin: I am working towards some pull requests with @rcarragher. The changes with the most impact effect code in both acralyzer and acra-storage. They will probably also require a "migration script" of sorts for existing repositories. (We could probably work around the requirement for a script, so far, but it would be ideal to add a field to existing documents. That is what we are planning to do for our deployment.)

Let's discuss it more once we have a pull request ready. There are some areas I would definitely appreciate your opinion, as they feel like "core" changes.