dependabot[bot] opened a new pull request, #7569:
URL: https://github.com/apache/arrow-datafusion/pull/7569

   Updates the requirements on 
[sqllogictest](https://github.com/risinglightdb/sqllogictest-rs) to permit the 
latest version.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/risinglightdb/sqllogictest-rs/releases";>sqllogictest's 
releases</a>.</em></p>
   <blockquote>
   <h2>v0.16.0</h2>
   <h2>[0.16.0] - 2023-09-15</h2>
   <ul>
   <li>
   <p>Support running external system commands with the syntax below. This is 
useful for manipulating some external resources during the test.</p>
   <pre><code>system ok
   echo &quot;Hello, world!&quot;
   </code></pre>
   <p>The runner will check the exit code of the command, and the output will 
be ignored. Currently, only <code>ok</code> is supported.</p>
   <p>Changes:</p>
   <ul>
   <li>(parser) <strong>Breaking change</strong>: Add 
<code>Record::System</code>, and corresponding <code>TestErrorKind</code> and 
<code>RecordOutput</code>. Mark <code>TestErrorKind</code> and 
<code>RecordOutput</code> as <code>#[non_exhaustive]</code>.</li>
   <li>(runner) Add <code>run_command</code> to <code>AsyncDB</code> trait. The 
default implementation will run the command with 
<code>std::process::Command::status</code>. Implementors can override this 
method to utilize an asynchronous runtime such as <code>tokio</code>.</li>
   </ul>
   </li>
   <li>
   <p>fix(runner): fix database name duplication for parallel tests by using 
the <strong>full path</strong> of the test file (instead of the file name) as 
the database name.</p>
   </li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/risinglightdb/sqllogictest-rs/blob/main/CHANGELOG.md";>sqllogictest's
 changelog</a>.</em></p>
   <blockquote>
   <h2>[0.16.0] - 2023-09-15</h2>
   <ul>
   <li>
   <p>Support running external system commands with the syntax below. This is 
useful for manipulating some external resources during the test.</p>
   <pre><code>system ok
   echo &quot;Hello, world!&quot;
   </code></pre>
   <p>The runner will check the exit code of the command, and the output will 
be ignored. Currently, only <code>ok</code> is supported.</p>
   <p>Changes:</p>
   <ul>
   <li>(parser) <strong>Breaking change</strong>: Add 
<code>Record::System</code>, and corresponding <code>TestErrorKind</code> and 
<code>RecordOutput</code>. Mark <code>TestErrorKind</code> and 
<code>RecordOutput</code> as <code>#[non_exhaustive]</code>.</li>
   <li>(runner) Add <code>run_command</code> to <code>AsyncDB</code> trait. The 
default implementation will run the command with 
<code>std::process::Command::status</code>. Implementors can override this 
method to utilize an asynchronous runtime such as <code>tokio</code>.</li>
   </ul>
   </li>
   <li>
   <p>fix(runner): fix database name duplication for parallel tests by using 
the <strong>full path</strong> of the test file (instead of the file name) as 
the database name.</p>
   </li>
   </ul>
   <h2>[0.15.3] - 2023-08-02</h2>
   <ul>
   <li>fix(bin): fix error context display. To avoid stack backtrace being 
printed, unset <code>RUST_BACKTRACE</code> environment variable, or use 
pre-built binaries built with stable toolchain instead.</li>
   </ul>
   <h2>[0.15.2] - 2023-07-31</h2>
   <ul>
   <li>fix(bin): do not print stack backtrace on error</li>
   </ul>
   <h2>[0.15.1] - 2023-07-24</h2>
   <ul>
   <li>fix <code>statement error</code> unexpectedly passed when result is a 
successful <code>query</code>. Similarly for expected <code>query error</code> 
but successful <code>statement ok</code>.</li>
   </ul>
   <h2>[0.15.0] - 2023-07-06</h2>
   <ul>
   <li>Allow multiple connections to the database in a single test case, which 
is useful for testing the transaction behavior. This can be achieved by 
attaching a <code>connection foo</code> record before the query or statement.
   <ul>
   <li>(parser) Add <code>Record::Connection</code>.</li>
   <li>(runner) <strong>Breaking change</strong>: Since the runner may 
establish multiple connections at runtime, <code>Runner::new</code> now takes a 
<code>impl MakeConnection</code>, which is usually a closure that returns a 
try-future of the <code>AsyncDB</code> instance.</li>
   <li>(bin) The connection to the database is now established lazily on the 
first query or statement.</li>
   </ul>
   </li>
   </ul>
   <h2>[0.14.0] - 2023-06-08</h2>
   <ul>
   <li>We enhanced how <code>skipif</code> and <code>onlyif</code> works. 
Previously it checks against <code>DB::engine_name()</code>, and 
<code>sqllogictest-bin</code> didn't implement it.
   <ul>
   <li>(parser) A minor <strong>breaking change</strong>: Change the field 
names of <code>Condition:: OnlyIf/SkipIf</code>.</li>
   <li>(runner) Add <code>Runner::add_label</code>. Now multiple labels are 
supported ( <code>DB::engine_name()</code> is still included). The condition 
evaluates to true if <em>any</em> of the provided labels match the 
<code>skipif/onlyif &lt;lable&gt;</code>.</li>
   <li>(bin) Add <code>--label</code> option to specify custom labels.</li>
   </ul>
   </li>
   </ul>
   <h2>[0.13.2] - 2023-03-24</h2>
   <ul>
   <li><code>Runner::update_test_file</code> properly escapes regex special 
characters.</li>
   </ul>
   <h2>[0.13.1] - 2023-03-16</h2>
   <ul>
   <li>Support postgres options.</li>
   </ul>
   <h2>[0.13.0] - 2023-02-15</h2>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/risinglightdb/sqllogictest-rs/commit/d554415e9c3c62bbcaaef01c065ea3cbbbbd52f4";><code>d554415</code></a>
 feat: run system commands (<a 
href="https://redirect.github.com/risinglightdb/sqllogictest-rs/issues/193";>#193</a>)</li>
   <li><a 
href="https://github.com/risinglightdb/sqllogictest-rs/commit/8085ab61216125bd08dd0b16f7750c4036c485fc";><code>8085ab6</code></a>
 use full file path as db name (<a 
href="https://redirect.github.com/risinglightdb/sqllogictest-rs/issues/194";>#194</a>)</li>
   <li><a 
href="https://github.com/risinglightdb/sqllogictest-rs/commit/9772a353f18331cce79a9fe90671d07b569497df";><code>9772a35</code></a>
 fix: fix type in tests. (<a 
href="https://redirect.github.com/risinglightdb/sqllogictest-rs/issues/192";>#192</a>)</li>
   <li><a 
href="https://github.com/risinglightdb/sqllogictest-rs/commit/d8e0d638718747b014de32f9643b851b7118490c";><code>d8e0d63</code></a>
 fix error context display &amp; update release workflow (<a 
href="https://redirect.github.com/risinglightdb/sqllogictest-rs/issues/190";>#190</a>)</li>
   <li><a 
href="https://github.com/risinglightdb/sqllogictest-rs/commit/42e8a224b45e1163886ad4802028a546ac798f2d";><code>42e8a22</code></a>
 fix(bin): do not print stack backtrace on error (<a 
href="https://redirect.github.com/risinglightdb/sqllogictest-rs/issues/189";>#189</a>)</li>
   <li><a 
href="https://github.com/risinglightdb/sqllogictest-rs/commit/6afd33584500de65681f44dc29b893e042bd83bb";><code>6afd335</code></a>
 fix <code>query/statement error</code> unexpected passed when result is 
`statement/query...</li>
   <li><a 
href="https://github.com/risinglightdb/sqllogictest-rs/commit/ff89483306228b38a044ff1cedba34b7e972e2a2";><code>ff89483</code></a>
 move /examples to /tests (<a 
href="https://redirect.github.com/risinglightdb/sqllogictest-rs/issues/186";>#186</a>)</li>
   <li><a 
href="https://github.com/risinglightdb/sqllogictest-rs/commit/e938269da63928b6a7089d81643268941d4dd885";><code>e938269</code></a>
 fix: correctly support command complete in postgres-extended (<a 
href="https://redirect.github.com/risinglightdb/sqllogictest-rs/issues/151";>#151</a>)</li>
   <li>See full diff in <a 
href="https://github.com/risinglightdb/sqllogictest-rs/compare/v0.15.0...v0.16.0";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
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]

Reply via email to