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:24:54 UTC
(superset) branch test-ci updated (4f1efca0a1 -> 0f4d04b092)
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 4f1efca0a1 chore: test
add efdeb9df05 feat(embedded+async queries): support async queries to work with embedded guest user (#26332)
add ff025b78f3 fix(post-processing): handle missing values in cumulative operator (#26429)
new 0f4d04b092 test: a
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 (4f1efca0a1)
\
N -- N -- N refs/heads/test-ci (0f4d04b092)
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:
CONTRIBUTING.md | 4 +-
superset/async_events/async_query_manager.py | 26 ++++++-
superset/common/query_context_processor.py | 10 ++-
superset/tasks/async_queries.py | 37 ++++++----
superset/utils/pandas_postprocessing/cum.py | 1 +
tests/integration_tests/query_context_tests.py | 1 +
.../async_events/async_query_manager_tests.py | 79 +++++++++++++++++++++-
tests/unit_tests/fixtures/dataframes.py | 5 ++
tests/unit_tests/pandas_postprocessing/test_cum.py | 14 ++++
9 files changed, 156 insertions(+), 21 deletions(-)
(superset) 01/01: test: a
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 0f4d04b092ac54a7b737b7538bb7dddbbe4a1020
Author: Michael S. Molina <mi...@gmail.com>
AuthorDate: Mon Mar 4 15:24:37 2024 -0500
test: a
---
CONTRIBUTING.md | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index de40865edc..bb449cc735 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -30,7 +30,7 @@ little bit helps, and credit will always be given.
- [Types of Contributions](#types-of-contributions)
- [Report Bug](#report-bug)
- [Submit Ideas or Feature Requests](#submit-ideas-or-feature-requests)
- - [Fix Bugs](#fix-bugs)
+ - [Fisx Bugs](#fix-bugs)
- [Implement Features](#implement-features)
- [Improve Documentation](#improve-documentation)
- [Add Translations](#add-translations)
@@ -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
```