mirror of
https://github.com/jlengrand/bugsink.git
synced 2026-03-10 08:01:17 +00:00
a2f3ad900b
this error has shown up for one of our users; I can't reproduce yet, but I can make it better: * log-don't-crash: not worth failing for this (drops the event, and also rolls back the transaction such that nothing is achieved regarding eviction) * provide more info on-error (various counts) NB: I've also changed the < into a <=, and combined it with a check on "loop not done". I _think_ they are functionally equivalent, and that the new version is simply more clear as well as slightly more efficient. In my understanding: the old version simply looped one more time before giving up (because it was < it needed one more iteration, and because there was no explicit check on 'loop done' that inefficiency was needed in the old formulation). I say "I think" because I don't have a test specific to the edge-case.
Bugsink: Self-hosted Error Tracking
Bugsink offers real-time error tracking for your applications with full control through self-hosting.
Screenshot
This is what you'll get:
Installation & docs
The quickest way to evaluate Bugsink is to spin up a throw-away instance using Docker:
docker pull bugsink/bugsink:latest
docker run \
-e SECRET_KEY={{ random_secret }} \
-e CREATE_SUPERUSER=admin:admin \
-e PORT=8000 \
-p 8000:8000 \
bugsink/bugsink
Visit http://localhost:8000/, where you'll see a login screen. The default username and password
are admin.
Now, you can set up your first project and start tracking errors.
Detailed installation instructions are on the Bugsink website.