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

[config] clarifications around SUPERSET_WEBSERVER_TIMEOUT #6840

Merged
merged 1 commit into from Feb 11, 2019

Conversation

mistercrunch
Copy link
Member

Closes #6836

@codecov-io
Copy link

codecov-io commented Feb 8, 2019

Codecov Report

Merging #6840 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #6840   +/-   ##
=======================================
  Coverage   56.32%   56.32%           
=======================================
  Files         527      527           
  Lines       23528    23528           
  Branches     2782     2782           
=======================================
  Hits        13251    13251           
  Misses       9866     9866           
  Partials      411      411
Impacted Files Coverage Δ
superset/config.py 93.67% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e14c0cf...138d493. Read the comment docs.

@kristw kristw merged commit 73e119a into apache:master Feb 11, 2019
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 0.34.0 labels Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 0.34.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[question] SUPERSET_WEBSERVER_TIMEOUT deprecated but what is the alternative?
3 participants