Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unicode characters and empty names in exported .yaml files #20331

Open
3 tasks done
magicarm22 opened this issue Jun 9, 2022 · 5 comments
Open
3 tasks done

Unicode characters and empty names in exported .yaml files #20331

magicarm22 opened this issue Jun 9, 2022 · 5 comments
Assignees
Labels
#bug Bug report

Comments

@magicarm22
Copy link

magicarm22 commented Jun 9, 2022

When I try to export dashboard with Russian names from the Apache superset, I got an archive without name in the dashboard and charts folders. Also in .yaml files I can find \u symbols: dashboard_title: "\u041A\u0443\u0440\u0441\u043A"

How to reproduce the bug

  1. Create a new dashboard with russian symbols (for example "Тест")
  2. Also you can create a charts with russian names too.
  3. Save the dashboard
  4. Export that dashboard
  5. Check that the name of the dashboard.yaml file like .yaml
  6. Check that you got undecoded unicode symbols inside the yaml file

Expected results

Yaml files with name and correct strings

Actual results

Yaml file without name (just extension), and with \u characters

Screenshots

image
image
image

Environment

(please complete the following information):

  • Windows 10
  • superset version: latest docker container
  • python version: Python 3.9.1
  • node.js version: v14.16.1
  • any feature flags active:

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@magicarm22 magicarm22 added the #bug Bug report label Jun 9, 2022
@d9k
Copy link

d9k commented Nov 22, 2022

I got following errors after importing dashboard with russian names charts to another Superset instance:

  • sorry there is no chart definition trying to be added
  • There is no chart definition associated with this component, could it have been deleted?

Charts not working

Temporary solution

  1. Open charts one by one, rename all charts names to new names with english characters only.
  2. (Optionally) Open dashboard, press pencil icon. You can click on chart titles and rename visible captions. Chart names must remain the same (english characters only)

Version info

Superset v. 1.5.1

@CeelamkotiVinod
Copy link

I have exported dashboard from test instance and imported in production instance.
And when I open dashboard and see charts in production then I got this

"There is no chart definition associated with this component, could it have been deleted?
Delete this container and save to remove this message."

I tried by renaming and save & goto dashboard. But the chart is not added in dashboard.

I installed superset using pip and version is 2.0.1.

Thanks in advance

@zakaryanla
Copy link

zakaryanla commented Dec 13, 2023

I had a similar problem that the Cyrillic alphabet was removed and the file began with _$number.yaml, such files were not imported.
In version 3 of SS the problem is not reproduced.

xyb added a commit to xyb/superset that referenced this issue Apr 12, 2024
xyb added a commit to xyb/superset that referenced this issue Apr 12, 2024
xyb added a commit to xyb/superset that referenced this issue Apr 17, 2024
@rusackas
Copy link
Member

Is this still being seen in Superset 3.1/4.0?

@rusackas
Copy link
Member

Seems possibly related to #19982, even if tangentially.

xyb added a commit to xyb/superset that referenced this issue May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

7 participants