Currently, after user editing a metric in Edit dataset modal in Explore, the edited metric jump to the bottom of the metric list.
it create a few issues:

1. when the metric list is long, by dropping to the bottom, user might take a while to find it or think the most recent edited metic is lost.
2. every time users edit a single metric, they see a different order of metric list showing in the

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

I'm new to Flask, and was wondering about a feature that I think would be useful to add to the Pagination class. Unless I'm missing it, there doesn't seem to be a built-in way to get the numbers of the items you're viewing on the page itself. That is, if you want to display "387 records found; displaying 26–50", you'd have to do calculations to get the "26" and "50".

I think something along the

https://github.com/CTFd/CTFd/blob/master/CTFd/themes/core/templates/scoreboard.html#L26

This should change depending on the mode of the CTF

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)