Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugs are keyed by a hash on the server #73

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

davcamer
Copy link

This simplifies code dealing with previously compound keys.
It easily allows single bugs to be retrieved directly.
It makes the 'resolved' documents smaller.

In the storage database view indexing is faster and smaller.

This is required to work with acra-storage PR ACRA/acra-storage#6

This simplifies code dealing with previously compound keys.
It easily allows single bugs to be retrieved directly.
It makes the 'resolved' documents smaller.

In the storage database view indexing is faster and smaller.
@halkeye
Copy link
Contributor

halkeye commented Jan 12, 2014

ACRA/acra-storage#6

@davcamer
Copy link
Author

Fixed the jshint problems from the previous pull request.

@halkeye
Copy link
Contributor

halkeye commented Jan 12, 2014

Btw, just FYI, you don't you don't need to recreate, you can just push (even forced) again, it'll update the code.

davcamer and others added 3 commits January 11, 2014 22:59
Couch's include_docs and group_level parameters enable several
places that previously used reports-per-x to instead re-use the
recent-items-by views, but with a reduction done to get the count.

This reduces the time it takes to index, and reduces the size of
the indexes on disk.
@davcamer
Copy link
Author

(Thanks for the tip on the forcing!)

More dashboard changes that work with the acra-storage changes I added to the PR there: ACRA/acra-storage#6

I could see the stale data change being awkward for a very low traffic Acralyzer server. Should it be configurable? Should a stale request and a non-stale request with a timeout be launched at the same time? (A bit like an iOS app where you see old data from a local database after opening it back up, while the app is trying to contact the server to refresh.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants