You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@superset.apache.org by mi...@apache.org on 2024/03/04 20:31:42 UTC
(superset) branch test-ci updated (e71d12f672 -> a34aec10cd)
This is an automated email from the ASF dual-hosted git repository.
michaelsmolina pushed a change to branch test-ci
in repository https://gitbox.apache.org/repos/asf/superset.git
discard e71d12f672 chore: test
omit f59498fcb9 fix(helm): Include option to use Redis with SSL (#26663)
omit 595c6ce3e6 chore: Add granular permissions for actions in Dashboard (#27029)
omit 13915bbb54 feat(docker): allow for docker release builds to be multi-platform (#27055)
omit 5951f6ceb6 fix(ephemeral): last try fixing this GH action (#27060)
omit ee69ac97c8 fix(ephemeral): point to the full tag name (#27058)
omit 6f402991e5 fix(plugins): missing currency on small number format in table chart (#27041)
omit cf84f36a6c chore: prevent prophet from logging non-errors as errors (#27053)
omit 81301ee54e fix(ephemeral): fix tagging command for ECR (#27057)
omit 3700326c35 fix(ephemeral): fix ephemeral builds in PR (#27056)
omit fd06ff3745 fix(explore): allow free-form d3 format on custom column formatting (#27023)
omit c222464d05 chore(docs): bump version number in docs example (#27038)
omit 66b4670300 fix(actions): correcting malformed labeler configs (#27048)
omit daaf657d47 build(deps-dev): bump @types/jest from 26.0.24 to 29.5.12 in /superset-frontend/plugins/plugin-chart-handlebars (#26973)
omit e986a1746f fix(webpack-dev-server): parse env args (#19744)
omit 686ce33ea5 fix: safer error message in alerts (#27019)
omit c77fc7dbaf fix(ci): fix action script v7 breaking changes v3 (#27042)
omit f8c75ca50b chore(dashboard): migrate enzyme to RTL (#26260)
omit 918057e6c7 fix(ci): fix action script v7 breaking changes v2 (#27040)
omit 01e2f8ace3 fix(security manager): Users should not have access to all draft dashboards (#27015)
new a34aec10cd chore: test
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (e71d12f672)
\
N -- N -- N refs/heads/test-ci (a34aec10cd)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.github/labeler.yml | 8 +-
.github/workflows/check_db_migration_confict.yml | 6 +-
.github/workflows/docker-release.yml | 16 +-
.github/workflows/ephemeral-env.yml | 17 +-
.github/workflows/update-monorepo-lockfiles.yml | 13 +-
CONTRIBUTING.md | 8 +-
docs/docs/installation/alerts-reports.mdx | 10 +-
helm/superset/Chart.yaml | 2 +-
helm/superset/README.md | 7 +-
helm/superset/templates/_helpers.tpl | 39 +--
helm/superset/templates/secret-env.yaml | 7 -
helm/superset/values.yaml | 10 +-
scripts/build_docker.py | 42 +--
superset-frontend/package-lock.json | 24 +-
.../superset-ui-chart-controls/src/types.ts | 1 -
.../plugins/plugin-chart-handlebars/package.json | 2 +-
.../plugin-chart-table/src/utils/formatValue.ts | 6 -
.../plugin-chart-table/test/TableChart.test.tsx | 42 ---
.../Chart/ChartContextMenu/ChartContextMenu.tsx | 12 +-
.../Chart/ChartContextMenu/useContextMenu.test.tsx | 38 +--
.../components/Chart/DrillBy/DrillByModal.test.tsx | 2 +-
.../Chart/DrillDetail/DrillDetailModal.test.tsx | 2 +-
.../dashboard/components/DashboardGrid.test.jsx | 125 ++++-----
.../components/FiltersBadge/FiltersBadge.test.tsx | 197 +++++++------
.../PropertiesModal/PropertiesModal.test.jsx | 22 +-
.../components/RefreshIntervalModal.test.tsx | 210 ++++++++------
.../SliceHeaderControls.test.tsx | 78 +-----
.../components/SliceHeaderControls/index.tsx | 34 ++-
.../components/gridComponents/Chart.test.jsx | 305 +++++++++-----------
.../components/gridComponents/Column.test.jsx | 275 +++++++++---------
.../components/gridComponents/Row.test.jsx | 227 +++++++--------
.../components/gridComponents/Tabs.test.jsx | 311 +++++++++++----------
.../gridComponents/new/NewColumn.test.jsx | 37 ++-
.../gridComponents/new/NewDivider.test.jsx | 37 ++-
.../gridComponents/new/NewHeader.test.jsx | 37 ++-
.../components/gridComponents/new/NewRow.test.jsx | 37 ++-
.../components/gridComponents/new/NewTabs.test.jsx | 37 ++-
.../dashboard/components/menu/HoverMenu.test.tsx | 10 +-
.../components/menu/WithPopoverMenu.test.jsx | 107 +++----
.../FiltersConfigModal/FiltersConfigModal.tsx | 2 +-
.../FiltersConfigModal/NativeFiltersModal.test.tsx | 127 ++++++---
.../controls/ColumnConfigControl/constants.tsx | 1 -
superset-frontend/webpack.proxy-config.js | 12 +-
superset/commands/report/alert.py | 9 +-
...d83218_migrate_can_view_and_drill_permission.py | 85 ------
superset/security/manager.py | 34 +--
superset/utils/decorators.py | 19 --
superset/utils/pandas_postprocessing/prophet.py | 7 +-
.../dashboards/security/security_rbac_tests.py | 24 +-
...migrate_can_view_and_drill_permission__tests.py | 61 ----
tests/integration_tests/security_tests.py | 6 +-
tests/unit_tests/scripts/docker_build.py | 60 ++--
tests/unit_tests/utils/test_decorators.py | 45 ---
53 files changed, 1241 insertions(+), 1651 deletions(-)
delete mode 100644 superset/migrations/versions/2024-02-07_17-13_87d38ad83218_migrate_can_view_and_drill_permission.py
delete mode 100644 tests/integration_tests/migrations/87d38ad83218_migrate_can_view_and_drill_permission__tests.py
(superset) 01/01: chore: test
Posted by mi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
michaelsmolina pushed a commit to branch test-ci
in repository https://gitbox.apache.org/repos/asf/superset.git
commit a34aec10cd9c8ff2f0ff67af4711849ce5f982d5
Author: Michael S. Molina <mi...@gmail.com>
AuthorDate: Mon Mar 4 15:31:27 2024 -0500
chore: test
---
CONTRIBUTING.md | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e95a766dc7..b0739dfc4e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -35,7 +35,7 @@ little bit helps, and credit will always be given.
- [Improve Documentation](#improve-documentation)
- [Add Translations](#add-translations)
- [Ask Questions](#ask-questions)
- - [Pull Request Guidelines](#pull-request-guidelines)
+ - [Pull Requesst Guidelines](#pull-request-guidelines)
- [Protocol](#protocol)
- [Authoring](#authoring)
- [Reviewing](#reviewing)
@@ -217,7 +217,7 @@ Security team members must:
- Have an [ICLA](https://www.apache.org/licenses/contributor-agreements.html) signed with Apache Software Foundation.
- Not reveal information about pending and unfixed security issues to anyone (including their employers) unless specifically authorised by the security team members, e.g., if the security team agrees that diagnosing and solving an issue requires the involvement of external experts.
-A release manager, the contributor overseeing the release of a specific version of Apache Superset, is by default a member of the security team. However, they are not expected to be active in assessing, discussing, and fixing security issues.
+A release manager, the contributor overseeing the release of a specific version of Apache Superset, is by default a member of the security team. However, they are not expected to be active in assessing, discussing, and fixing security issues.
Security team members should also follow these general expectations:
@@ -374,8 +374,8 @@ Triaging goals
First, add **Category labels (a.k.a. hash labels)**. Every issue/PR must have one hash label (except spam entry). Labels that begin with `#` defines issue/PR type:
-| Label | for Issue | for PR |
-| --------------- | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Label | for Issue | for PR |
+| --------------- | ----------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `#bug` | Bug report | Bug fix |
| `#code-quality` | Describe problem with code, architecture or productivity | Refactor, tests, tooling |
| `#feature` | New feature request | New feature implementation |
@@ -648,22 +648,28 @@ If while using the above commands you encounter an error related to the limit of
```bash
Error: ENOSPC: System limit for number of file watchers reached
```
+
The error is thrown because the number of files monitored by the system has reached the limit.
You can address this this error by increasing the number of inotify watchers.
The current value of max watches can be checked with:
+
```bash
cat /proc/sys/fs/inotify/max_user_watches
```
+
Edit the file /etc/sysctl.conf to increase this value.
The value needs to be decided based on the system memory [(see this StackOverflow answer for more context)](https://stackoverflow.com/questions/535768/what-is-a-reasonable-amount-of-inotify-watches-with-linux).
Open the file in editor and add a line at the bottom specifying the max watches values.
+
```bash
fs.inotify.max_user_watches=524288
```
+
Save the file and exit editor.
To confirm that the change succeeded, run the following command to load the updated value of max_user_watches from sysctl.conf:
+
```bash
sudo sysctl -p
```