Alec Rosenbaum

Can we open this issue back up? I know it's old, but the contents of #149 are still relevant today. Particularly the great comment here: https://github.com/rollbar/pyrollbar/pull/149#issuecomment-264643449, which also lays out...

I don't know if there's a clean way of using GitHub Pages with Sphinx, which I'm assuming we want to use. I think if we wanted to use GitHub Pages,...

Another use case that could create execution history issues is for a task that has many retries before failing. For example, say there's a queue that delivers many small payloads...

@sauravmahuri2007 I don't think there's currently a way to do this. Please create a new issue with this feature request. I don't think this request is relevant to this issue,...

I've run into a tangentially related issue recently while updating old dependencies (including an old version of `flask-wtf`). For us, it broke forms dynamically generated and used by `Flask-SuperAdmin`. Here's...

To my knowledge we haven't had a need for it, so it's not part of any development plans at the moment. cc @jkemp101 in case I'm wrong here

@jkimbo Here's our use case for what it's worth: Basically, there should never be anything within `errors` except for maybe a uuid that links it to a log message. The...

It doesn't currently work with async Redis. We'll likely work on that at some point, but don't have any immediate plans / priority for it.

I'll leave this open to track the request

For the record, I'm still seeing this issue in Django 1.11 with `django-assets==0.12`. It's only intermittent, and only seems to effect integration testing using pytest and Django's [StaticLiveServerTestCase](https://docs.djangoproject.com/en/1.11/ref/contrib/staticfiles/#django.contrib.staticfiles.testing.StaticLiveServerTestCase). I will...