Looks like this line is the cause
https://github.com/apache/superset/blob/94b6b29362ffec0dffc623c002a2cfd2153a6807/superset/viz.py#L1459

Expected results

Legends to show up as normal text

Actual results

chart keys show up as tuples

Screenshots

<img width="342" alt="Screen Shot 2021-02-03 at 11 11 25 PM" src="https://user-images.githubusercontent.com/20442310/1068477

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

SQLAlchemy 1.4 made some changes that are currently incompatible with this extension. Identify failing tests and make changes to fix those. We should also pin to SQLAlchemy<2, since that will be a bigger change and will be more appropriate in Flask-SQLAlchemy 3.0.

Here's some that I'm aware of so far:

• #885 URL is immutable
• bentoml/BentoML#1238, I'm no

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)