Is your feature request related to a problem? Please describe.

It seems the CRUD views (Charts and Dashboards) remember search filters in URL, but it does not allow using back and forward buttons to return to previous filters. This causes frustration when I searched something, didn't find I want, then clicked on the browser's "Back" button to return to previous list or to start a new search

In recent versions (can't say from exactly when), there seems to be an off-by-one error in dcc.DatePickerRange. I set max_date_allowed = datetime.today().date(), but in the calendar, yesterday is the maximum date allowed. I see it in my apps, and it is also present in the first example on the DatePickerRange documentation page.

E

It has been a pleasure for me to contribute to all of you 2 versions of this tool.

I've been working on other open source projects that I'm about to release for you, so I haven't finished trape version 3.0.

But, I invite you and the entire community that has used this project, to collaborate with some lines of code, implementing your own ideas and improving trape, turning it into a project o

Hey! When I was reading the docs and I saw api.background.task, the first thing that popped into my head was "but you can just use asyncio.create_task or loop,.run_in_executor for that without inventing something new!". But then I noticed that it also passes the context vars to the synchronous backround stuff, which is nice. Wonder why that's not the case in the stdlib, cause it would be nic

Werkzeug 2.0 is changing how Local is implemented to use a ContextVar instead. This means that the ident_func is no longer relevant (and probably shouldn't have been used externally before either). Currently, it raises a RuntimeError, but soon it will show a DeprecationWarning. Either way, Flask-SQLAlchemy shouldn't try to use Werkzeug's implementation anymore.

Since Flask-SQLAlchemy

Environment:

• CTFd Version/Commit: 3.1.1

• Operating System: Linux linux 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

• Web Browser and Version: `Google Chrome 86.0.424

ujson is no more actively maintained and specially for some critical bugs not present in json package.

one example forcing us to revert ujson usage:
ultrajson/ultrajson#325 (2 days ago, mine)
ultrajson/ultrajson#301 (same but 1 year ago and no answer)