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

Unable to save report due to Add button not enable #28149

Open
2 of 3 tasks
badf007 opened this issue Apr 19, 2024 · 4 comments
Open
2 of 3 tasks

Unable to save report due to Add button not enable #28149

badf007 opened this issue Apr 19, 2024 · 4 comments
Assignees

Comments

@badf007
Copy link

badf007 commented Apr 19, 2024

Bug description

While filling in all the required information there is still an error in the Notification method section where it shows that a recipient is missing even when valid emails are provided.

How to reproduce the bug

  1. Go to alerts and reports.
  2. Go to the report section
  3. Click Add report
  4. Fill all required fields.

What should happen:

  • The ADD button is enabled and the report can be saved

What is happening:

  • The ADD button is not enabled and a red asterisk is shown in the EMAIL RECIPIENTS field.

Screenshots/recordings

image

image

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
@cmartinezdnn
Copy link

Same issue happening to me. It looks like there is bug in new superset 4.0 version.

@sfirke
Copy link
Contributor

sfirke commented May 8, 2024

Someone in Slack is seeing this too. I am running 4.0.0 in production and can successfully create a new alert, so this is not universally broken. My best guess is that there's something in the recipients validation checker that succeeds on my instance but fails for these people without telling them why. CC @fisjac as I believe they wrote some of this new validation.

@alexkyurtev
Copy link

please contact me if further information is needed , i`m also seeing this bug on my side

@fisjac
Copy link
Contributor

fisjac commented May 8, 2024

Looking into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants