PrimeIntellect/SWE-rebench-V2 huggingface dataset:
Repository: sql-formatter-org/sql-formatter (ts)

Issue:
[FORMATTING] Named arguments in BigQuery
**Input data**

Which SQL and options did you provide as input?

```sql
SELECT MAKE_INTERVAL(1, day=>2, minute => 3)
```

**Expected Output**

```sql
SELECT
  MAKE_INTERVAL(1, day => 2, minute => 3)
```

**Actual Output**

```sql
SELECT
  MAKE_INTERVAL(1, day = > 2, minute = > 3)
```

**Usage**

- How are you calling / using the library?
  - `$ npx -p sql-formatter@12.2.0 sql-formatter -l bigquery file.sql`
- What SQL language(s) does this apply to?
  - BigQuery
- Which SQL Formatter version are you using? 
  - 12.2.0 (latest)

---

BigQuery supports named arguments in several functions.
https://cloud.google.com/bigquery/docs/reference/standard-sql/functions-reference#named_arguments

Named arguments are sometimes used in [JSON functions](https://cloud.google.com/bigquery/docs/reference/standard-sql/json_functions#double_for_json) and [Geography functions](https://cloud.google.com/bigquery/docs/reference/standard-sql/geography_functions).

Reading at the PostgreSQL implementation, it is not difficult to just add it to operators, so I'll try to PR it.
If the operator should work only in the function call, reject it.

Pull request:
Support named arguments for BigQuery
resolved #602 

Patch:
diff --git a/src/languages/bigquery/bigquery.formatter.ts b/src/languages/bigquery/bigquery.formatter.ts
index aef53d84..a3908130 100644
--- a/src/languages/bigquery/bigquery.formatter.ts
+++ b/src/languages/bigquery/bigquery.formatter.ts
@@ -180,7 +180,7 @@ export const bigquery: DialectOptions = {
     paramTypes: { positional: true, named: ['@'], quoted: ['@'] },
     variableTypes: [{ regex: String.raw`@@\w+` }],
     lineCommentTypes: ['--', '#'],
-    operators: ['&', '|', '^', '~', '>>', '<<', '||'],
+    operators: ['&', '|', '^', '~', '>>', '<<', '||', '=>'],
     postProcess,
   },
   formatOptions: {


Test patch:
diff --git a/test/bigquery.test.ts b/test/bigquery.test.ts
index 461a69b7..7df745ae 100644
--- a/test/bigquery.test.ts
+++ b/test/bigquery.test.ts
@@ -55,7 +55,7 @@ describe('BigQueryFormatter', () => {
     'EXCEPT DISTINCT',
     'INTERSECT DISTINCT',
   ]);
-  supportsOperators(format, ['&', '|', '^', '~', '>>', '<<', '||']);
+  supportsOperators(format, ['&', '|', '^', '~', '>>', '<<', '||', '=>']);
   supportsIsDistinctFrom(format);
   supportsParams(format, { positional: true, named: ['@'], quoted: ['@``'] });
   supportsWindow(format);
@@ -242,6 +242,17 @@ describe('BigQueryFormatter', () => {
     `);
   });
 
+  it('supports named arguments', () => {
+    expect(
+      format(`
+      SELECT MAKE_INTERVAL(1, day=>2, minute => 3)
+      `)
+    ).toBe(dedent`
+      SELECT
+        MAKE_INTERVAL(1, day => 2, minute => 3)
+    `);
+  });
+
   // Issue #279
   describe('supports FROM clause operators:', () => {
     it('UNNEST operator', () => {
Repository: dynaconf/dynaconf (python)

Issue:
Field '_bypass_evaluation' provided as part of the value of a setting
**Describe the bug**
When a BoxList containing a dictionary is created, when looking up the value of the BoxList, the field `_bypass_evaluation` is present in the dictionary.  This is unexpected.

**To Reproduce**
Steps to reproduce the behavior:

Using Dynaconf v3.2.0:

```
from dynaconf import Dynaconf

settings = Dynaconf()
settings.set("key", [{"d": "v"}])
settings.key
```
This provides the value of the key as:
`<BoxList: [{'d': 'v', '_bypass_evaluation': False}]>`

However, it is expected to be:
`<BoxList: [{'d': 'v'}]>`

**Executing under the following environment**
This happens in Ubuntu 20.04, python3, using  Dynaconf v3.2.0

**Proposed solution**
The following line:
```self._store._box_config["_bypass_evaluation"] = False```

at 
https://github.com/dynaconf/dynaconf/blob/678d29b7383f03934a47e21b1bcdf68946d5c501/dynaconf/base.py#L1174

can be replaced with:
```self._store._box_config.pop("_bypass_evaluation")```

This has the same result as setting it to False with the benefit that it is removed completely.


Pull request:
Fix: unexpected _bypass_evaluation in BoxList
Fix #965 

Patch:
diff --git a/dynaconf/base.py b/dynaconf/base.py
index f481f31..c0c6c4e 100644
--- a/dynaconf/base.py
+++ b/dynaconf/base.py
@@ -1171,7 +1171,7 @@ class Settings:
         execute_module_hooks("post", self, env, silent=silent, key=key)
         execute_instance_hooks(self, "post", self._post_hooks)
 
-        self._store._box_config["_bypass_evaluation"] = False
+        self._store._box_config.pop("_bypass_evaluation")
 
     def pre_load(self, env, silent, key):
         """Do we have any file to pre-load before main settings file?"""


Test patch:
diff --git a/tests/test_base.py b/tests/test_base.py
index 9bd59d3..6e9fae8 100644
--- a/tests/test_base.py
+++ b/tests/test_base.py
@@ -1423,3 +1423,10 @@ def test_get_with_sysenv_fallback_local_overrides():
     assert settings.sysenv_fallback_for_dynaconf is True
     assert settings.get("another_test") == "ANOTHER_VALUE"
     assert not settings.get("another_test", sysenv_fallback=False)
+
+
+# issue #965
+def test_no_extra_values_in_nested_structure():
+    settings = Dynaconf()
+    settings.set("key", [{"d": "v"}])
+    assert settings.key == [{"d": "v"}]