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

TypeError TypeError: send_file() got an unexpected keyword argument 'attachment_filename' #430

Closed
1 of 4 tasks
aitmlouk opened this issue Oct 11, 2022 · 2 comments
Closed
1 of 4 tasks
Assignees
Labels
bugfix Something isn't working

Comments

@aitmlouk
Copy link
Contributor

aitmlouk commented Oct 11, 2022

Severity

  • Critical/Blocker (select if the issue makes the application unusable or causes serious data loss)
  • High (select if the issue affects a major feature and there is no workaround or the available workaround is very complex)
  • Medium (select if the issue affects a minor feature or affects a major feature but has an easy enough workaround to not cause any major inconvenience)
  • Low (select if the issue doesn't significantly affect the user experience, like minor visual bugs)

Describe the bug
Cannot download the config file (client.yaml) from UI

Environment:

  • OS: [Linux]
  • Version: [Ubuntu 20]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Reproduction Steps
Steps to reproduce the behavior:

  1. Go to '/network'
  2. Click on 'download client config'
  3. See error 'TypeError TypeError: send_file() got an unexpected keyword argument 'attachment_filename'

Expected behavior
Download client.yaml

Screenshots
If applicable, add screenshots to help explain your problem.

Contact Details
An e-mail address in case we need to contact you for further details regarding this issue.

@ahellander ahellander added the bugfix Something isn't working label Oct 14, 2022
@ahellander
Copy link
Member

I can confirm this behavior (develop).

@ahellander
Copy link
Member

This issue affects users on Python 3.10, it is due to an update in the Flask API. Fix in PR #435

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants