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

fix: Revert enabling CSP #24476

Merged
merged 1 commit into from
Jun 21, 2023
Merged

fix: Revert enabling CSP #24476

merged 1 commit into from
Jun 21, 2023

Conversation

kgabryje
Copy link
Member

SUMMARY

This reverts commit c3b5d72.
When TALISMAN_ENABLED ff is set to False, csp_nonce jinja function is undefined. Reverting until I fix this bug

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@kgabryje kgabryje changed the title Revert "chore: Enable CSP by default (#24262)" fix: Revert enabling CSP Jun 21, 2023
crossorigin="anonymous"
nonce="{{ csp_nonce() }}"></script>
<script src="{{ assets_prefix }}/static/assets/stylesheets/less/cosmo/cosmoTheme.js" nonce="{{ csp_nonce() }}"></script>
<script src="https://code.jquery.com/jquery-1.10.2.min.js"></script>

Check warning

Code scanning / CodeQL

Inclusion of functionality from an untrusted source

Script loaded from content delivery network with no integrity check.
@codecov
Copy link

codecov bot commented Jun 21, 2023

Codecov Report

Merging #24476 (716d6d6) into master (d5f88c1) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

❗ Current head 716d6d6 differs from pull request most recent head f96e032. Consider uploading reports for the commit f96e032 to get more accurate results

@@            Coverage Diff             @@
##           master   #24476      +/-   ##
==========================================
- Coverage   69.03%   69.00%   -0.03%     
==========================================
  Files        1901     1901              
  Lines       74002    74001       -1     
  Branches     8116     8116              
==========================================
- Hits        51086    51067      -19     
- Misses      20805    20823      +18     
  Partials     2111     2111              
Flag Coverage Δ
hive 53.93% <100.00%> (+<0.01%) ⬆️
mysql 79.42% <100.00%> (+<0.01%) ⬆️
postgres 79.51% <100.00%> (+<0.01%) ⬆️
presto 53.84% <100.00%> (+<0.01%) ⬆️
python 83.44% <100.00%> (-0.06%) ⬇️
sqlite ?
unit 54.68% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
.../superset-ui-core/src/models/ExtensibleFunction.ts 100.00% <ø> (ø)
superset/config.py 91.97% <100.00%> (-0.03%) ⬇️
superset/initialization/__init__.py 91.38% <100.00%> (+0.30%) ⬆️

... and 5 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@kgabryje kgabryje merged commit fb08e0e into apache:master Jun 21, 2023
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 3.0.0 labels Mar 8, 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 size/L 🚢 3.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants