Process completed with exit code 1.

error: unused `async` for function with no await statements --> src/driver/listener.rs:183:5 | 183 | / async fn listen(&mut self) -> RustPSQLDriverPyResult<()> { 184 | | let Some(client) = self.client.clone() else { 185 | | return Err(RustPSQLDriverError::BaseConnectionError("test".into())); 186 | | }; ... | 227 | | Ok(()) 228 | | } | |_____^ | = help: consider removing the `async` from this function note: `await` used in an async block, which does not require the enclosing function to be `async` --> src/driver/listener.rs:197:18 | 197 | .await | ^^^^^ = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unused_async

error: unused `async` for function with no await statements --> src/driver/listener.rs:76:5 | 76 | / async fn __aexit__<'a>( 77 | | slf: Py<Self>, 78 | | _exception_type: Py<PyAny>, 79 | | exception: Py<PyAny>, ... | 82 | | Ok(()) 83 | | } | |_____^ | = help: consider removing the `async` from this function = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unused_async

error: unused `async` for function with no await statements --> src/driver/listener.rs:72:5 | 72 | / async fn __aenter__<'a>(slf: Py<Self>) -> RustPSQLDriverPyResult<Py<Self>> { 73 | | Ok(slf) 74 | | } | |_____^ | = help: consider removing the `async` from this function = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unused_async

error: unused `async` for function with no await statements --> src/driver/connection_pool.rs:504:5 | 504 | / pub async fn add_listener( 505 | | self_: pyo3::Py<Self>, 506 | | callback: Py<PyAny>, 507 | | ) -> RustPSQLDriverPyResult<Listener> { ... | 569 | | Ok(Listener::new(pg_config, ca_file, ssl_mode)) 570 | | } | |_____^ | = help: consider removing the `async` from this function = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unused_async = note: `-D clippy::unused-async` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::unused_async)]`

error: unneeded late initialization --> src/driver/utils.rs:205:5 | 205 | let mgr: Manager; | ^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_late_init = note: `-D clippy::needless-late-init` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::needless_late_init)]` help: move the declaration `mgr` here and remove the assignments from the `match` arms | 205 ~ 206 ~ let mgr: Manager = match configured_tls { 207 | ConfiguredTLS::NoTls => { 208 ~ Manager::from_config(pg_config, NoTls, mgr_config) 209 | } 210 | ConfiguredTLS::TlsConnector(connector) => { 211 ~ Manager::from_config(pg_config, connector, mgr_config) 212 | } 213 ~ }; |

error: docs for function returning `Result` missing `# Errors` section --> src/driver/utils.rs:177:1 | 177 | / pub fn build_tls( 178 | | ca_file: &Option<String>, 179 | | ssl_mode: Option<SslMode>, 180 | | ) -> RustPSQLDriverPyResult<ConfiguredTLS> { | |__________________________________________^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#missing_errors_doc

error: this lifetime isn't used in the function definition --> src/driver/transaction.rs:796:27 | 796 | pub async fn pipeline<'py>( | ^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/transaction.rs:227:24 | 227 | async fn __aexit__<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/transaction.rs:172:25 | 172 | async fn __aenter__<'a>(self_: Py<Self>) -> RustPSQLDriverPyResult<Py<Self>> { | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this function's return value is unnecessary --> src/driver/listener.rs:170:5 | 170 | / fn add_callback(&mut self, channel: String, callback: Py<PyAny>) -> RustPSQLDriverPyResult<()> { 171 | | match self.channel_callbacks.entry(channel) { 172 | | Entry::Vacant(e) => { 173 | | e.insert(vec![callback]); ... | 180 | | Ok(()) 181 | | } | |_____^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_wraps = note: `-D clippy::unnecessary-wraps` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::unnecessary_wraps)]` help: remove the return type... | 170 | fn add_callback(&mut self, channel: String, callback: Py<PyAny>) -> () { | ~~ help: ...and then remove returned values | 180 - Ok(()) |

error: this lifetime isn't used in the function definition --> src/driver/listener.rs:76:24 | 76 | async fn __aexit__<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/listener.rs:72:25 | 72 | async fn __aenter__<'a>(slf: Py<Self>) -> RustPSQLDriverPyResult<Py<Self>> { | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: calling `Option::default()` is more clear than this expression --> src/driver/listener.rs:55:23 | 55 | receiver: Default::default(), | ^^^^^^^^^^^^^^^^^^ help: try: `Option::default()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#default_trait_access

error: calling `Option::default()` is more clear than this expression --> src/driver/listener.rs:54:21 | 54 | client: Default::default(), | ^^^^^^^^^^^^^^^^^^ help: try: `Option::default()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#default_trait_access

error: calling `Option::default()` is more clear than this expression --> src/driver/listener.rs:53:35 | 53 | listen_abort_handler: Default::default(), | ^^^^^^^^^^^^^^^^^^ help: try: `Option::default()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#default_trait_access

error: calling `HashMap::default()` is more clear than this expression --> src/driver/listener.rs:52:32 | 52 | channel_callbacks: Default::default(), | ^^^^^^^^^^^^^^^^^^ help: try: `HashMap::default()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#default_trait_access = note: `-D clippy::default-trait-access` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::default_trait_access)]`

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:587:37 | 587 | pub async fn fetch_backward_all<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:553:33 | 553 | pub async fn fetch_backward<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:520:36 | 520 | pub async fn fetch_forward_all<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:486:33 | 486 | pub async fn fetch_relative<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:452:33 | 452 | pub async fn fetch_absolute<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:425:29 | 425 | pub async fn fetch_last<'a>(slf: Py<Self>) -> RustPSQLDriverPyResult<PSQLDriverPyQueryResult> { | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:398:30 | 398 | pub async fn fetch_first<'a>(slf: Py<Self>) -> RustPSQLDriverPyResult<PSQLDriverPyQueryResult> { | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:371:30 | 371 | pub async fn fetch_prior<'a>(slf: Py<Self>) -> RustPSQLDriverPyResult<PSQLDriverPyQueryResult> { | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:344:29 | 344 | pub async fn fetch_next<'a>(slf: Py<Self>) -> RustPSQLDriverPyResult<PSQLDriverPyQueryResult> { | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:300:24 | 300 | pub async fn fetch<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:167:24 | 167 | async fn __aexit__<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:139:25 | 139 | async fn __aenter__<'a>(slf: Py<Self>) -> RustPSQLDriverPyResult<Py<Self>> { | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: docs for function returning `Result` missing `# Errors` section --> src/driver/connection_pool.rs:504:5 | 504 | / pub async fn add_listener( 505 | | self_: pyo3::Py<Self>, 506 | | callback: Py<PyAny>, 507 | | ) -> RustPSQLDriverPyResult<Listener> { | |_________________________________________^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#missing_errors_doc = note: `-D clippy::missing-errors-doc` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::missing_errors_doc)]`

error: this lifetime isn't used in the function definition --> src/driver/connection_pool.rs:441:24 | 441 | pub async fn fetch<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/connection_pool.rs:372:26 | 372 | pub async fn execute<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/connection.rs:519:28 | 519 | pub async fn fetch_val<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/connection.rs:291:31 | 291 | pub async fn execute_many<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/connection.rs:157:24 | 157 | async fn __aexit__<'a>( | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: this lifetime isn't used in the function definition --> src/driver/connection.rs:130:25 | 130 | async fn __aenter__<'a>(self_: Py<Self>) -> RustPSQLDriverPyResult<Py<Self>> { | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes = note: `-D clippy::extra-unused-lifetimes` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::extra_unused_lifetimes)]`

error: unused import: `StreamExt` --> src/driver/connection_pool.rs:3:26 | 3 | use futures::{FutureExt, StreamExt, TryStreamExt}; | ^^^^^^^^^

error: unused import: `FutureExt` --> src/driver/connection_pool.rs:3:15 | 3 | use futures::{FutureExt, StreamExt, TryStreamExt}; | ^^^^^^^^^

error: unused import: `TryStreamExt` --> src/driver/connection_pool.rs:3:37 | 3 | use futures::{FutureExt, StreamExt, TryStreamExt}; | ^^^^^^^^^^^^ | = note: `-D unused-imports` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(unused_imports)]`

error: unused variable: `exception` --> src/driver/listener.rs:79:9 | 79 | exception: Py<PyAny>, | ^^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_exception`

error: unused variable: `slf` --> src/driver/listener.rs:77:9 | 77 | slf: Py<Self>, | ^^^ help: if this is intentional, prefix it with an underscore: `_slf`

error: unused variable: `callback` --> src/driver/connection_pool.rs:506:9 | 506 | callback: Py<PyAny>, | ^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_callback` | = note: `-D unused-variables` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(unused_variables)]`

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:132:1 | 132 | create_exception!(psqlpy.exceptions, SSLError, RustPSQLDriverPyBaseError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:132:1 | 132 | create_exception!(psqlpy.exceptions, SSLError, RustPSQLDriverPyBaseError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:126:1 | 126 | / create_exception!( 127 | | psqlpy.exceptions, 128 | | MacAddrConversionError, 129 | | RustPSQLDriverPyBaseError 130 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:126:1 | 126 | / create_exception!( 127 | | psqlpy.exceptions, 128 | | MacAddrConversionError, 129 | | RustPSQLDriverPyBaseError 130 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:120:1 | 120 | / create_exception!( 121 | | psqlpy.exceptions, 122 | | UUIDValueConvertError, 123 | | RustPSQLDriverPyBaseError 124 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:120:1 | 120 | / create_exception!( 121 | | psqlpy.exceptions, 122 | | UUIDValueConvertError, 123 | | RustPSQLDriverPyBaseError 124 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:114:1 | 114 | / create_exception!( 115 | | psqlpy.exceptions, 116 | | PyToRustValueMappingError, 117 | | RustPSQLDriverPyBaseError 118 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:114:1 | 114 | / create_exception!( 115 | | psqlpy.exceptions, 116 | | PyToRustValueMappingError, 117 | | RustPSQLDriverPyBaseError 118 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:109:1 | 109 | / create_exception!( 110 | | psqlpy.exceptions, 111 | | RustToPyValueMappingError, 112 | | RustPSQLDriverPyBaseError 113 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:109:1 | 109 | / create_exception!( 110 | | psqlpy.exceptions, 111 | | RustToPyValueMappingError, 112 | | RustPSQLDriverPyBaseError 113 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:106:1 | 106 | create_exception!(psqlpy.exceptions, CursorClosedError, BaseCursorError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:106:1 | 106 | create_exception!(psqlpy.exceptions, CursorClosedError, BaseCursorError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:105:1 | 105 | create_exception!(psqlpy.exceptions, CursorFetchError, BaseCursorError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:105:1 | 105 | create_exception!(psqlpy.exceptions, CursorFetchError, BaseCursorError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:104:1 | 104 | create_exception!(psqlpy.exceptions, CursorCloseError, BaseCursorError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:104:1 | 104 | create_exception!(psqlpy.exceptions, CursorCloseError, BaseCursorError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:103:1 | 103 | create_exception!(psqlpy.exceptions, CursorStartError, BaseCursorError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:103:1 | 103 | create_exception!(psqlpy.exceptions, CursorStartError, BaseCursorError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:98:1 | 98 | / create_exception!( 99 | | psqlpy.exceptions, 100 | | BaseCursorError, 101 | | RustPSQLDriverPyBaseError 102 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:98:1 | 98 | / create_exception!( 99 | | psqlpy.exceptions, 100 | | BaseCursorError, 101 | | RustPSQLDriverPyBaseError 102 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:91:1 | 91 | / create_exception!( 92 | | psqlpy.exceptions, 93 | | TransactionClosedError, 94 | | BaseTransactionError 95 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:91:1 | 91 | / create_exception!( 92 | | psqlpy.exceptions, 93 | | TransactionClosedError, 94 | | BaseTransactionError 95 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:86:1 | 86 | / create_exception!( 87 | | psqlpy.exceptions, 88 | | TransactionExecuteError, 89 | | BaseTransactionError 90 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:86:1 | 86 | / create_exception!( 87 | | psqlpy.exceptions, 88 | | TransactionExecuteError, 89 | | BaseTransactionError 90 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:81:1 | 81 | / create_exception!( 82 | | psqlpy.exceptions, 83 | | TransactionSavepointError, 84 | | BaseTransactionError 85 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:81:1 | 81 | / create_exception!( 82 | | psqlpy.exceptions, 83 | | TransactionSavepointError, 84 | | BaseTransactionError 85 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:76:1 | 76 | / create_exception!( 77 | | psqlpy.exceptions, 78 | | TransactionRollbackError, 79 | | BaseTransactionError 80 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:76:1 | 76 | / create_exception!( 77 | | psqlpy.exceptions, 78 | | TransactionRollbackError, 79 | | BaseTransactionError 80 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:71:1 | 71 | / create_exception!( 72 | | psqlpy.exceptions, 73 | | TransactionCommitError, 74 | | BaseTransactionError 75 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:71:1 | 71 | / create_exception!( 72 | | psqlpy.exceptions, 73 | | TransactionCommitError, 74 | | BaseTransactionError 75 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:66:1 | 66 | / create_exception!( 67 | | psqlpy.exceptions, 68 | | TransactionBeginError, 69 | | BaseTransactionError 70 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:66:1 | 66 | / create_exception!( 67 | | psqlpy.exceptions, 68 | | TransactionBeginError, 69 | | BaseTransactionError 70 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:61:1 | 61 | / create_exception!( 62 | | psqlpy.exceptions, 63 | | BaseTransactionError, 64 | | RustPSQLDriverPyBaseError 65 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:61:1 | 61 | / create_exception!( 62 | | psqlpy.exceptions, 63 | | BaseTransactionError, 64 | | RustPSQLDriverPyBaseError 65 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:54:1 | 54 | / create_exception!( 55 | | psqlpy.exceptions, 56 | | ConnectionClosedError, 57 | | BaseConnectionError 58 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:54:1 | 54 | / create_exception!( 55 | | psqlpy.exceptions, 56 | | ConnectionClosedError, 57 | | BaseConnectionError 58 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:49:1 | 49 | / create_exception!( 50 | | psqlpy.exceptions, 51 | | ConnectionExecuteError, 52 | | BaseConnectionError 53 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:49:1 | 49 | / create_exception!( 50 | | psqlpy.exceptions, 51 | | ConnectionExecuteError, 52 | | BaseConnectionError 53 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:44:1 | 44 | / create_exception!( 45 | | psqlpy.exceptions, 46 | | BaseConnectionError, 47 | | RustPSQLDriverPyBaseError 48 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:44:1 | 44 | / create_exception!( 45 | | psqlpy.exceptions, 46 | | BaseConnectionError, 47 | | RustPSQLDriverPyBaseError 48 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:37:1 | 37 | / create_exception!( 38 | | psqlpy.exceptions, 39 | | ConnectionPoolExecuteError, 40 | | BaseConnectionPoolError 41 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:37:1 | 37 | / create_exception!( 38 | | psqlpy.exceptions, 39 | | ConnectionPoolExecuteError, 40 | | BaseConnectionPoolError 41 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:32:1 | 32 | / create_exception!( 33 | | psqlpy.exceptions, 34 | | ConnectionPoolConfigurationError, 35 | | BaseConnectionPoolError 36 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:32:1 | 32 | / create_exception!( 33 | | psqlpy.exceptions, 34 | | ConnectionPoolConfigurationError, 35 | | BaseConnectionPoolError 36 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:27:1 | 27 | / create_exception!( 28 | | psqlpy.exceptions, 29 | | ConnectionPoolBuildError, 30 | | BaseConnectionPoolError 31 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:27:1 | 27 | / create_exception!( 28 | | psqlpy.exceptions, 29 | | ConnectionPoolBuildError, 30 | | BaseConnectionPoolError 31 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:22:1 | 22 | / create_exception!( 23 | | psqlpy.exceptions, 24 | | BaseConnectionPoolError, 25 | | RustPSQLDriverPyBaseError 26 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:22:1 | 22 | / create_exception!( 23 | | psqlpy.exceptions, 24 | | BaseConnectionPoolError, 25 | | RustPSQLDriverPyBaseError 26 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:19:1 | 19 | create_exception!(psqlpy.exceptions, RuntimeJoinError, RustException); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:19:1 | 19 | create_exception!(psqlpy.exceptions, RuntimeJoinError, RustException); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:18:1 | 18 | create_exception!(psqlpy.exceptions, MacAddrParseError, RustException); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:18:1 | 18 | create_exception!(psqlpy.exceptions, MacAddrParseError, RustException); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:17:1 | 17 | create_exception!(psqlpy.exceptions, DriverError, RustException); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:17:1 | 17 | create_exception!(psqlpy.exceptions, DriverError, RustException); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:16:1 | 16 | create_exception!(psqlpy.exceptions, RustException, RustPSQLDriverPyBaseError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:16:1 | 16 | create_exception!(psqlpy.exceptions, RustException, RustPSQLDriverPyBaseError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:7:1 | 7 | / create_exception!( 8 | | psqlpy.exceptions, 9 | | RustPSQLDriverPyBaseError, 10 | | pyo3::exceptions::PyException 11 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:7:1 | 7 | / create_exception!( 8 | | psqlpy.exceptions, 9 | | RustPSQLDriverPyBaseError, 10 | | pyo3::exceptions::PyException 11 | | ); | |_^ | = note: no expected values for `feature` = help: consider adding `gil-refs` as a feature in `Cargo.toml` = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration = note: `-D unexpected-cfgs` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(unexpected_cfgs)]` = note: this error originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)

Clippy had exited with the 101 exit code

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/