codeant-ai-for-open-source[bot] commented on code in PR #42054:
URL: https://github.com/apache/superset/pull/42054#discussion_r3592968182
##########
superset/utils/date_parser.py:
##########
@@ -66,6 +66,14 @@
"1st": 1,
}
+# parsedatetime does not understand "N quarters" (it leaves the source time
+# unchanged), so such phrases are rewritten to the equivalent number of months
+# before parsing. The lookbehind and the bounded repetition keep matching
+# linear on user-provided strings (every suffix of an unbounded digit run
+# would be re-scanned) and keep the int() conversion small; longer digit
+# runs fall through to parsedatetime like any other unparseable phrase.
+_QUARTERS_PATTERN = re.compile(r"(?<![0-9])([0-9]{1,10})\s+quarters?\b",
re.IGNORECASE)
Review Comment:
**Suggestion:** Add an explicit type annotation to the compiled regex
constant to satisfy the type-hint requirement for new module-level variables.
[custom_rule]
**Severity Level:** Minor ๐งน
<details>
<summary><b>Why it matters? โญ </b></summary>
The new module-level variable `_QUARTERS_PATTERN` is introduced without an
explicit type annotation, which matches the Python type-hint rule for newly
added annotatable variables.
</details>
<details>
<summary><b>Rule source ๐ </b></summary>
.cursor/rules/dev-standard.mdc (line 28)
</details>
[](https://app.codeant.ai/fix-in-ide?tool=cursor&prompt_id=02ae137f27724bb08d0b16e919d24afd&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
[](https://app.codeant.ai/fix-in-ide?tool=vscode-claude&prompt_id=02ae137f27724bb08d0b16e919d24afd&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
*(Use Cmd/Ctrl + Click for best experience)*
<details>
<summary><b>Prompt for AI Agent ๐ค </b></summary>
```mdx
This is a comment left during a code review.
**Path:** superset/utils/date_parser.py
**Line:** 75:75
**Comment:**
*Custom Rule: Add an explicit type annotation to the compiled regex
constant to satisfy the type-hint requirement for new module-level variables.
Validate the correctness of the flagged issue. If correct, How can I resolve
this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask
user if the user wants to fix the rest of the comments as well. if said yes,
then fetch all the comments validate the correctness and implement a minimal fix
```
</details>
<a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=7c3d8b4be76e05989f7683a89a162e15fdbdc4ea189d554cf89edd1a18ba064b&reaction=like'>๐</a>
| <a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=7c3d8b4be76e05989f7683a89a162e15fdbdc4ea189d554cf89edd1a18ba064b&reaction=dislike'>๐</a>
##########
tests/unit_tests/common/test_query_context_processor.py:
##########
@@ -1024,6 +1024,159 @@ def fake_query(dct: dict[str, Any]) -> MagicMock:
assert "2025-06-01" in val, f"Expected shifted-to-dttm in val, got:
{val!r}"
+def test_processing_time_offsets_quarter_offset_shifts_query_window(processor):
Review Comment:
**Suggestion:** Add explicit type hints to this test function signature,
including annotating `processor` and the return type. [custom_rule]
**Severity Level:** Minor ๐งน
<details>
<summary><b>Why it matters? โญ </b></summary>
This is a newly added Python test function in the final file state, and it
omits both the `processor` parameter type and a return type annotation. That
matches the type-hint rule violation.
</details>
<details>
<summary><b>Rule source ๐ </b></summary>
.cursor/rules/dev-standard.mdc (line 28)
</details>
[](https://app.codeant.ai/fix-in-ide?tool=cursor&prompt_id=61d009bb539643a3a75df205b4e476fb&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
[](https://app.codeant.ai/fix-in-ide?tool=vscode-claude&prompt_id=61d009bb539643a3a75df205b4e476fb&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
*(Use Cmd/Ctrl + Click for best experience)*
<details>
<summary><b>Prompt for AI Agent ๐ค </b></summary>
```mdx
This is a comment left during a code review.
**Path:** tests/unit_tests/common/test_query_context_processor.py
**Line:** 1027:1027
**Comment:**
*Custom Rule: Add explicit type hints to this test function signature,
including annotating `processor` and the return type.
Validate the correctness of the flagged issue. If correct, How can I resolve
this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask
user if the user wants to fix the rest of the comments as well. if said yes,
then fetch all the comments validate the correctness and implement a minimal fix
```
</details>
<a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=2795ef898d3983f90ac55b11053e5e118ba4fe42477aaf1016c6b6c22a8b7e7d&reaction=like'>๐</a>
| <a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=2795ef898d3983f90ac55b11053e5e118ba4fe42477aaf1016c6b6c22a8b7e7d&reaction=dislike'>๐</a>
##########
tests/unit_tests/common/test_time_shifts.py:
##########
@@ -334,19 +337,259 @@ def test_join_offset_dfs_totals_query_no_dimensions():
assert_frame_equal(expected, result)
-def test_join_offset_dfs_raises_without_time_grain():
- """Time comparison with relative offsets requires a time grain."""
+def test_join_offset_dfs_no_time_grain_aligns_relative_offset() -> None:
+ """
+ Without a time grain, a relative offset joins on the exact shifted
+ timestamps instead of raising, so saved charts without a grain render
+ with a correctly aligned comparison series.
+ """
+ df = DataFrame(
+ {
+ "ds": [Timestamp("2021-01-01"), Timestamp("2021-02-01")],
+ "D": [1, 2],
+ }
+ )
+ offset_df = DataFrame(
+ {
+ "ds": [Timestamp("2020-01-01"), Timestamp("2020-02-01")],
+ "B": [5, 6],
+ }
+ )
+ offset_dfs = {"1 year ago": offset_df}
+
+ expected = DataFrame(
+ {
+ "ds": [Timestamp("2021-01-01"), Timestamp("2021-02-01")],
+ "D": [1, 2],
+ "B": [5, 6],
+ }
+ )
+
+ result = query_context_processor.join_offset_dfs(
+ df, offset_dfs, time_grain=None, join_keys=["ds"]
+ )
+
+ assert_frame_equal(expected, result)
+
+
+def test_join_offset_dfs_no_time_grain_unmatched_timestamps_yield_nulls() ->
None:
+ """
+ Without a time grain, offset timestamps that have no exact shifted
+ counterpart in the main series produce nulls instead of raising.
+ """
+ df = DataFrame({"ds": [Timestamp("2021-01-01")], "D": [1]})
+ offset_df = DataFrame({"ds": [Timestamp("2020-06-15")], "B": [5]})
+ offset_dfs = {"1 year ago": offset_df}
+
+ result = query_context_processor.join_offset_dfs(
+ df, offset_dfs, time_grain=None, join_keys=["ds"]
+ )
+
+ assert "B" in result.columns
+ assert result["B"].isna().all()
+
+
+def test_join_offset_dfs_no_time_grain_multiple_offsets() -> None:
+ """
+ Multiple relative offsets without a time grain each align on their own
+ shifted timestamps, and no synthetic join columns leak into the result.
+ """
+ df = DataFrame({"ds": [Timestamp("2021-01-29")], "D": [1]})
+ offset_df1 = DataFrame({"ds": [Timestamp("2021-01-01")], "B": [5]})
+ offset_df2 = DataFrame({"ds": [Timestamp("2020-01-29")], "C": [7]})
+ offset_dfs = {"28 days ago": offset_df1, "1 year ago": offset_df2}
+
+ expected = DataFrame(
+ {
+ "ds": [Timestamp("2021-01-29")],
+ "D": [1],
+ "B": [5],
+ "C": [7],
+ }
+ )
+
+ result = query_context_processor.join_offset_dfs(
+ df, offset_dfs, time_grain=None, join_keys=["ds"]
+ )
+
+ assert_frame_equal(expected, result)
+
+
+def test_join_offset_dfs_no_time_grain_empty_offset_df() -> None:
+ """
+ An empty offset series materializes its join keys as NaN floats; the
+ grain-less join must not crash on the dtype mismatch.
+ """
df = DataFrame({"ds": [Timestamp("2021-01-01")], "D": [1]})
- offset_df = DataFrame({"ds": [Timestamp("2021-02-01")], "B": [5]})
+ offset_df = DataFrame({"ds": [float("nan")], "B": [float("nan")]})
offset_dfs = {"1 year ago": offset_df}
- with pytest.raises(
- QueryObjectValidationError, match="Time Grain must be specified"
- ):
- query_context_processor.join_offset_dfs(
+ result = query_context_processor.join_offset_dfs(
+ df, offset_dfs, time_grain=None, join_keys=["ds"]
+ )
+
+ assert "B" in result.columns
+ assert result["B"].isna().all()
+
+
+def test_join_offset_dfs_no_time_grain_quarter_offset() -> None:
+ """
+ Quarter offsets align without a time grain (normalize_time_delta converts
+ quarters to months, since pd.DateOffset has no quarters argument).
+ """
+ df = DataFrame({"ds": [Timestamp("2021-04-01")], "D": [1]})
+ offset_df = DataFrame({"ds": [Timestamp("2021-01-01")], "B": [5]})
+ offset_dfs = {"1 quarter ago": offset_df}
+
+ expected = DataFrame({"ds": [Timestamp("2021-04-01")], "D": [1], "B": [5]})
+
+ result = query_context_processor.join_offset_dfs(
+ df, offset_dfs, time_grain=None, join_keys=["ds"]
+ )
+
+ assert_frame_equal(expected, result)
+
+
+def test_join_offset_dfs_no_time_grain_free_form_offset() -> None:
+ """
+ Offsets outside the normalize_time_delta grammar (e.g. "one year ago")
+ are aligned with the same parser that shifted the offset query's range.
+ """
+ df = DataFrame({"ds": [Timestamp("2021-01-01")], "D": [1]})
+ offset_df = DataFrame({"ds": [Timestamp("2020-01-01")], "B": [5]})
+ offset_dfs = {"one year ago": offset_df}
+
+ expected = DataFrame({"ds": [Timestamp("2021-01-01")], "D": [1], "B": [5]})
+
+ result = query_context_processor.join_offset_dfs(
+ df, offset_dfs, time_grain=None, join_keys=["ds"]
+ )
+
+ assert_frame_equal(expected, result)
+
+
+def test_join_offset_dfs_no_time_grain_free_form_offset_tz_microseconds() ->
None:
+ """
+ Free-form offsets align timezone-aware, sub-second timestamps: each row's
+ shift is computed from a naive second-truncated copy and applied to the
+ original value, so the join keys keep their timezone and precision.
+ """
+ df = DataFrame(
+ {"ds": [Timestamp("2021-03-04 05:06:07.890123", tz="UTC")], "D": [1]}
+ )
+ offset_df = DataFrame(
+ {"ds": [Timestamp("2020-03-04 05:06:07.890123", tz="UTC")], "B": [5]}
+ )
+ offset_dfs = {"one year ago": offset_df}
+
+ result = query_context_processor.join_offset_dfs(
+ df, offset_dfs, time_grain=None, join_keys=["ds"]
+ )
+
+ assert result["B"].tolist() == [5]
+
+
+def test_join_offset_dfs_no_time_grain_uninterpretable_offset() -> None:
+ """
+ An offset that no parser can interpret falls back to joining on the raw
+ keys (an empty comparison series) instead of crashing.
+ """
+ df = DataFrame({"ds": [Timestamp("2021-01-01")], "D": [1]})
+ offset_df = DataFrame({"ds": [Timestamp("2020-01-01")], "B": [5]})
+ offset_dfs = {"not a real offset": offset_df}
+
+ result = query_context_processor.join_offset_dfs(
+ df, offset_dfs, time_grain=None, join_keys=["ds"]
+ )
+
+ assert "B" in result.columns
+ assert result["B"].isna().all()
+
+
+def test_join_offset_dfs_no_time_grain_uninterpretable_offset_subsecond(
+ caplog,
+) -> None:
Review Comment:
**Suggestion:** Add a concrete type annotation for the `caplog` test fixture
parameter in this new test function signature. [custom_rule]
**Severity Level:** Minor ๐งน
<details>
<summary><b>Why it matters? โญ </b></summary>
This new test function introduces an untyped parameter (`caplog`) even
though it can be annotated, which violates the repository rule requiring Python
type hints on new or modified code.
</details>
<details>
<summary><b>Rule source ๐ </b></summary>
.cursor/rules/dev-standard.mdc (line 28)
</details>
[](https://app.codeant.ai/fix-in-ide?tool=cursor&prompt_id=43e17b854c4248ac9076613e8982488b&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
[](https://app.codeant.ai/fix-in-ide?tool=vscode-claude&prompt_id=43e17b854c4248ac9076613e8982488b&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
*(Use Cmd/Ctrl + Click for best experience)*
<details>
<summary><b>Prompt for AI Agent ๐ค </b></summary>
```mdx
This is a comment left during a code review.
**Path:** tests/unit_tests/common/test_time_shifts.py
**Line:** 509:511
**Comment:**
*Custom Rule: Add a concrete type annotation for the `caplog` test
fixture parameter in this new test function signature.
Validate the correctness of the flagged issue. If correct, How can I resolve
this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask
user if the user wants to fix the rest of the comments as well. if said yes,
then fetch all the comments validate the correctness and implement a minimal fix
```
</details>
<a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=3a8e81a29cf948961325c15ff7015dd9e38f7c68f0a130aff76b756c5addcf91&reaction=like'>๐</a>
| <a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=3a8e81a29cf948961325c15ff7015dd9e38f7c68f0a130aff76b756c5addcf91&reaction=dislike'>๐</a>
##########
tests/unit_tests/common/test_query_context_processor.py:
##########
@@ -1024,6 +1024,159 @@ def fake_query(dct: dict[str, Any]) -> MagicMock:
assert "2025-06-01" in val, f"Expected shifted-to-dttm in val, got:
{val!r}"
+def test_processing_time_offsets_quarter_offset_shifts_query_window(processor):
+ """A quarter offset must shift the offset query's window, not just the
+ join keys. parsedatetime does not understand "1 quarter ago", so without
+ rewriting quarters to months the offset subquery silently runs against
+ the current period and the comparison series joins to nulls. The fake
+ query below derives its rows from the requested window, so the join only
+ yields the expected values when the window was actually shifted.
+ """
+ from superset.common.query_object import QueryObject
+ from superset.models.helpers import ExploreMixin
+
+ for method in (
+ "processing_time_offsets",
+ "_align_offset_without_time_grain",
+ "_coalesce_offset_index",
+ ):
+ setattr(
+ processor._qc_datasource,
+ method,
+ getattr(ExploreMixin, method).__get__(processor._qc_datasource),
+ )
+
+ df = pd.DataFrame(
+ {
+ "__timestamp": pd.to_datetime(["2024-04-01", "2024-05-01",
"2024-06-01"]),
+ "sum__num": [100, 200, 300],
+ }
+ )
+
+ query_object = QueryObject(
+ datasource=MagicMock(),
+ granularity="ds",
+ columns=[],
+ metrics=["sum__num"],
+ is_timeseries=True,
+ time_offsets=["1 quarter ago"],
+ filters=[
+ {
+ "col": "ds",
+ "op": "TEMPORAL_RANGE",
+ "val": "2024-04-01 : 2024-07-01",
+ }
+ ],
+ )
+
+ captured: list[dict[str, Any]] = []
+
+ def fake_query(dct: dict[str, Any]) -> MagicMock:
+ captured.append(dct)
+ result = MagicMock()
+ result.df = pd.DataFrame(
+ {
+ "__timestamp": pd.date_range(
+ start=dct["from_dttm"], periods=3, freq="MS"
+ ),
+ "sum__num": [1.0, 2.0, 3.0],
+ }
+ )
+ result.query = "SELECT 1"
+ return result
+
+ processor._qc_datasource.query = fake_query
+ processor._qc_datasource.normalize_df = MagicMock(
+ side_effect=lambda offset_df, _query_object: offset_df
+ )
+
+ with (
+ patch(
+ "superset.models.helpers.get_since_until_from_query_object",
+ return_value=(pd.Timestamp("2024-04-01"),
pd.Timestamp("2024-07-01")),
+ ),
+ patch(
+ "superset.common.utils.query_cache_manager.QueryCacheManager"
+ ) as mock_cache_manager,
+ patch.object(
+ processor._qc_datasource,
+ "get_time_grain",
+ return_value=None,
+ ),
+ ):
+ mock_cache = MagicMock()
+ mock_cache.is_loaded = False
+ mock_cache_manager.get.return_value = mock_cache
+
+ result = processor._qc_datasource.processing_time_offsets(
+ df, query_object, None, None, False
+ )
+
+ assert len(captured) == 1
+ assert captured[0]["from_dttm"] == pd.Timestamp("2024-01-01")
+ assert captured[0]["to_dttm"] == pd.Timestamp("2024-04-01")
+ assert result["df"]["sum__num__1 quarter ago"].tolist() == [1.0, 2.0, 3.0]
+
+
+def test_processing_time_offsets_rejects_unparseable_offset(processor):
Review Comment:
**Suggestion:** Add explicit type hints to this test function signature,
including annotating `processor` and the return type. [custom_rule]
**Severity Level:** Minor ๐งน
<details>
<summary><b>Why it matters? โญ </b></summary>
This newly added Python test function also omits type annotations for its
parameter and return value, so the custom type-hint rule is violated here as
well.
</details>
<details>
<summary><b>Rule source ๐ </b></summary>
.cursor/rules/dev-standard.mdc (line 28)
</details>
[](https://app.codeant.ai/fix-in-ide?tool=cursor&prompt_id=7a4cddd5f1194d909f09d2507c17188a&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
[](https://app.codeant.ai/fix-in-ide?tool=vscode-claude&prompt_id=7a4cddd5f1194d909f09d2507c17188a&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
*(Use Cmd/Ctrl + Click for best experience)*
<details>
<summary><b>Prompt for AI Agent ๐ค </b></summary>
```mdx
This is a comment left during a code review.
**Path:** tests/unit_tests/common/test_query_context_processor.py
**Line:** 1121:1121
**Comment:**
*Custom Rule: Add explicit type hints to this test function signature,
including annotating `processor` and the return type.
Validate the correctness of the flagged issue. If correct, How can I resolve
this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask
user if the user wants to fix the rest of the comments as well. if said yes,
then fetch all the comments validate the correctness and implement a minimal fix
```
</details>
<a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=2b82bb74fb5e69195395bdeb60a5cfaa42e6b979d13d2070266b4b7adffb5155&reaction=like'>๐</a>
| <a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=2b82bb74fb5e69195395bdeb60a5cfaa42e6b979d13d2070266b4b7adffb5155&reaction=dislike'>๐</a>
##########
superset/models/helpers.py:
##########
@@ -2369,31 +2483,13 @@ def join_offset_dfs(
time range instead of being truncated to the main series' range.
This
uses an outer join so offset-only rows (e.g. the rest of a prior
day when
the current day is still in progress) are preserved.
+ :param x_axis_label: The query's temporal x-axis label, used to pick
the
+ temporal join key when no time grain is set.
"""
join_column_producer =
app.config["TIME_GRAIN_JOIN_COLUMN_PRODUCERS"].get(
time_grain
)
-
- if not time_grain:
- has_temporal_join_key = any(
- pd.api.types.is_datetime64_any_dtype(df[key])
- for key in join_keys
- if key in df.columns
- )
- if has_temporal_join_key:
- has_relative_offset = any(
- not (
- self.is_valid_date_range(offset)
- and feature_flag_manager.is_feature_enabled(
- "DATE_RANGE_TIMESHIFTS_ENABLED"
- )
- )
- for offset in offset_dfs
- )
- if has_relative_offset:
- raise QueryObjectValidationError(
- _("Time Grain must be specified when using Time
Comparison.")
- )
+ original_columns = list(df.columns)
Review Comment:
**Suggestion:** Add an explicit type annotation for this new local variable
to satisfy the strict type-hinting requirement for relevant variables.
[custom_rule]
**Severity Level:** Minor ๐งน
<details>
<summary><b>Why it matters? โญ </b></summary>
This is a newly added local variable in Python code and its type is
inferable as a list of column names, so it can be annotated under the
type-hinting rule. The existing code omits that annotation, matching the
reported violation.
</details>
<details>
<summary><b>Rule source ๐ </b></summary>
.cursor/rules/dev-standard.mdc (line 28)
</details>
[](https://app.codeant.ai/fix-in-ide?tool=cursor&prompt_id=f32075426273469e9e2cf1669519ee4f&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
[](https://app.codeant.ai/fix-in-ide?tool=vscode-claude&prompt_id=f32075426273469e9e2cf1669519ee4f&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
*(Use Cmd/Ctrl + Click for best experience)*
<details>
<summary><b>Prompt for AI Agent ๐ค </b></summary>
```mdx
This is a comment left during a code review.
**Path:** superset/models/helpers.py
**Line:** 2492:2492
**Comment:**
*Custom Rule: Add an explicit type annotation for this new local
variable to satisfy the strict type-hinting requirement for relevant variables.
Validate the correctness of the flagged issue. If correct, How can I resolve
this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask
user if the user wants to fix the rest of the comments as well. if said yes,
then fetch all the comments validate the correctness and implement a minimal fix
```
</details>
<a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=e4b3ddbab14d248f5ef3aa01cfdf3f7db385ccc17b3f945919708b88d1a45aef&reaction=like'>๐</a>
| <a
href='https://app.codeant.ai/feedback?pr_url=https%3A%2F%2Fgithub.com%2Fapache%2Fsuperset%2Fpull%2F42054&comment_hash=e4b3ddbab14d248f5ef3aa01cfdf3f7db385ccc17b3f945919708b88d1a45aef&reaction=dislike'>๐</a>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
