Process completed with exit code 1.

error: unused `async` for function with no await statements --> src/driver/listener.rs:354:5 | 354 | / async fn listen(&mut self) -> RustPSQLDriverPyResult<()> { 355 | | let Some(client) = self.connection.db_client() else { 356 | | return Err(RustPSQLDriverError::BaseConnectionError("test".into())); 357 | | }; ... | 402 | | Ok(()) 403 | | } | |_____^ | = 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:370:83 | 370 | call_listen(&is_listened_clone, &listen_query_clone, &client).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:196:5 | 196 | / async fn __aexit__<'a>( 197 | | slf: Py<Self>, 198 | | _exception_type: Py<PyAny>, 199 | | exception: Py<PyAny>, ... | 226 | | return Err(RustPSQLDriverError::ListenerClosedError) 227 | | } | |_____^ | = 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:192:5 | 192 | / async fn __aenter__<'a>(slf: Py<Self>) -> RustPSQLDriverPyResult<Py<Self>> { 193 | | Ok(slf) 194 | | } | |_____^ | = 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:503:5 | 503 | / pub async fn add_listener( 504 | | self_: pyo3::Py<Self>, 505 | | ) -> RustPSQLDriverPyResult<Listener> { 506 | | let (pg_config, ca_file, ssl_mode) = pyo3::Python::with_gil(|gil| { ... | 515 | | Ok(Listener::new(pg_config, ca_file, ssl_mode)) 516 | | } | |_____^ | = 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: docs for function returning `Result` missing `# Errors` section --> src/driver/utils.rs:219:1 | 219 | / pub fn is_coroutine_function( 220 | | function: Py<PyAny>, 221 | | ) -> RustPSQLDriverPyResult<bool> { | |_________________________________^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#missing_errors_doc

error: unneeded late initialization --> src/driver/utils.rs:206:5 | 206 | 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 | 206 ~ 207 ~ let mgr: Manager = match configured_tls { 208 | ConfiguredTLS::NoTls => { 209 ~ Manager::from_config(pg_config, NoTls, mgr_config) 210 | } 211 | ConfiguredTLS::TlsConnector(connector) => { 212 ~ Manager::from_config(pg_config, connector, mgr_config) 213 | } 214 ~ }; |

error: docs for function returning `Result` missing `# Errors` section --> src/driver/utils.rs:178:1 | 178 | / pub fn build_tls( 179 | | ca_file: &Option<String>, 180 | | ssl_mode: Option<SslMode>, 181 | | ) -> 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:794:27 | 794 | pub async fn pipeline<'py>( | ^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_lifetimes

error: question mark operator is useless here --> src/driver/transaction.rs:356:20 | 356 | return Ok(db_client.batch_execute(&querystring).await?); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try removing question mark and `Ok()`: `db_client.batch_execute(&querystring).await` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_question_mark

error: this lifetime isn't used in the function definition --> src/driver/transaction.rs:225:24 | 225 | 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:170:25 | 170 | 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: unneeded `return` statement --> src/driver/listener.rs:226:9 | 226 | return Err(RustPSQLDriverError::ListenerClosedError) | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_return help: remove `return` | 226 | Err(RustPSQLDriverError::ListenerClosedError) |

error: this lifetime isn't used in the function definition --> src/driver/listener.rs:196:24 | 196 | 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:192:25 | 192 | 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: variables can be used directly in the `format!` string --> src/driver/listener.rs:168:17 | 168 | format!("LISTEN {};", channel_name).as_str() | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#uninlined_format_args = note: `-D clippy::uninlined-format-args` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::uninlined_format_args)]` help: change this to | 168 - format!("LISTEN {};", channel_name).as_str() 168 + format!("LISTEN {channel_name};").as_str() |

error: calling `Arc::default()` is more clear than this expression --> src/driver/listener.rs:153:27 | 153 | listen_query: Default::default(), | ^^^^^^^^^^^^^^^^^^ help: try: `Arc::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:152:23 | 152 | 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:150:35 | 150 | 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 `Arc::default()` is more clear than this expression --> src/driver/listener.rs:149:32 | 149 | channel_callbacks: Default::default(), | ^^^^^^^^^^^^^^^^^^ help: try: `Arc::default()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#default_trait_access

error: this argument is passed by value, but not consumed in the function body --> src/driver/listener.rs:47:52 | 47 | fn clear_channel_callbacks(&mut self, channel: String) { | ^^^^^^ help: consider changing the type to: `&str` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_pass_by_value

error: this argument is passed by value, but not consumed in the function body --> src/driver/listener.rs:43:51 | 43 | fn retrieve_channel_callbacks(&self, channel: String) -> Option<&Vec<ListenerCallback>> { | ^^^^^^ help: consider changing the type to: `&str` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_pass_by_value = note: `-D clippy::needless-pass-by-value` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::needless_pass_by_value)]`

error: calling `HashMap::default()` is more clear than this expression --> src/driver/listener.rs:27:26 | 27 | ChannelCallbacks(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 `impl` can be derived --> src/driver/listener.rs:25:1 | 25 | / impl Default for ChannelCallbacks { 26 | | fn default() -> Self { 27 | | ChannelCallbacks(Default::default()) 28 | | } 29 | | } | |_^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#derivable_impls = note: `-D clippy::derivable-impls` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::derivable_impls)]` = help: remove the manual implementation... help: ...and instead derive it | 23 + #[derive(Default)] 24 | struct ChannelCallbacks(HashMap<String, Vec<ListenerCallback>>); |

error: this lifetime isn't used in the function definition --> src/driver/cursor.rs:588:37 | 588 | 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:554:33 | 554 | 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:521:36 | 521 | 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:487:33 | 487 | 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:453:33 | 453 | 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:426:29 | 426 | 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:399:30 | 399 | 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:372:30 | 372 | 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:345:29 | 345 | 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:301:24 | 301 | 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:168:24 | 168 | 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:140:25 | 140 | 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:503:5 | 503 | / pub async fn add_listener( 504 | | self_: pyo3::Py<Self>, 505 | | ) -> RustPSQLDriverPyResult<Listener> { | |_________________________________________^ | = 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/connection_pool.rs:440:24 | 440 | 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:371:26 | 371 | 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:525:28 | 525 | 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:297:31 | 297 | 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: question mark operator is useless here --> src/driver/connection.rs:280:20 | 280 | return Ok(db_client.batch_execute(&querystring).await?); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try removing question mark and `Ok()`: `db_client.batch_execute(&querystring).await` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_question_mark

error: this lifetime isn't used in the function definition --> src/driver/connection.rs:163:24 | 163 | 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:136:25 | 136 | 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: unneeded `return` statement --> src/driver/connection.rs:124:9 | 124 | return self.db_pool.clone() | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_return help: remove `return` | 124 | self.db_pool.clone() |

error: this method could have a `#[must_use]` attribute --> src/driver/connection.rs:123:5 | 123 | pub fn db_pool(&self) -> Option<Pool> { | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: add the attribute: `#[must_use] pub fn db_pool(&self) -> Option<Pool>` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#must_use_candidate

error: unneeded `return` statement --> src/driver/connection.rs:120:9 | 120 | return self.db_client.clone() | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_return = note: `-D clippy::needless-return` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::needless_return)]` help: remove `return` | 120 | self.db_client.clone() |

error: this method could have a `#[must_use]` attribute --> src/driver/connection.rs:119:5 | 119 | pub fn db_client(&self) -> Option<Arc<InnerConnection>> { | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: add the attribute: `#[must_use] pub fn db_client(&self) -> Option<Arc<InnerConnection>>` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#must_use_candidate = note: `-D clippy::must-use-candidate` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::must_use_candidate)]`

error: docs for function returning `Result` missing `# Errors` section --> src/driver/connection.rs:87:5 | 87 | / pub async fn copy_in<T, U>( 88 | | &self, 89 | | statement: &T 90 | | ) -> RustPSQLDriverPyResult<CopyInSink<U>> 91 | | where 92 | | T: ?Sized + ToStatement, 93 | | U: Buf + 'static + Send | |_______________________________^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#missing_errors_doc

error: docs for function returning `Result` missing `# Errors` section --> src/driver/connection.rs:70:5 | 70 | / pub async fn query_one<T>( 71 | | &self, 72 | | statement: &T, 73 | | params: &[&(dyn ToSql + Sync)], 74 | | ) -> RustPSQLDriverPyResult<Row> 75 | | where T: ?Sized + ToStatement | |_________________________________^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#missing_errors_doc

error: docs for function returning `Result` missing `# Errors` section --> src/driver/connection.rs:59:5 | 59 | pub async fn batch_execute(&self, query: &str) -> RustPSQLDriverPyResult<()> { | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#missing_errors_doc

error: docs for function returning `Result` missing `# Errors` section --> src/driver/connection.rs:43:5 | 43 | / pub async fn query<T>( 44 | | &self, 45 | | statement: &T, 46 | | params: &[&(dyn ToSql + Sync)], 47 | | ) -> RustPSQLDriverPyResult<Vec<Row>> 48 | | where T: ?Sized + ToStatement { | |_________________________________^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#missing_errors_doc

error: docs for function returning `Result` missing `# Errors` section --> src/driver/connection.rs:29:5 | 29 | / pub async fn prepare_cached( 30 | | &self, 31 | | query: &str 32 | | ) -> RustPSQLDriverPyResult<Statement> { | |__________________________________________^ | = 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: question mark operator is useless here --> src/common.rs:131:9 | 131 | Ok(self.batch_execute(querystring.as_str()).await?) | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try removing question mark and `Ok()`: `self.batch_execute(querystring.as_str()).await` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_question_mark = note: `-D clippy::needless-question-mark` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::needless_question_mark)]`

error: fields `process_id`, `channel`, `payload`, and `connection` are never read --> src/driver/listener.rs:77:5 | 76 | struct ListenerNotificationMsg { | ----------------------- fields in this struct 77 | process_id: i32, | ^^^^^^^^^^ 78 | channel: String, | ^^^^^^^ 79 | payload: String, | ^^^^^^^ 80 | connection: Connection, | ^^^^^^^^^^

error: fields `process_id` and `payload` are never read --> src/driver/listener.rs:60:5 | 59 | pub struct ListenerNotification { | -------------------- fields in this struct 60 | process_id: i32, | ^^^^^^^^^^ 61 | channel: String, 62 | payload: String, | ^^^^^^^ | = note: `ListenerNotification` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis

error: method `clear_channel_callbacks` is never used --> src/driver/listener.rs:47:8 | 31 | impl ChannelCallbacks { | --------------------- method in this implementation ... 47 | fn clear_channel_callbacks(&mut self, channel: String) { | ^^^^^^^^^^^^^^^^^^^^^^^ | = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: unexpected `cfg` condition value: `gil-refs` --> src/exceptions/python_errors.rs:142:1 | 142 | 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:142:1 | 142 | 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:136:1 | 136 | / create_exception!( 137 | | psqlpy.exceptions, 138 | | MacAddrConversionError, 139 | | RustPSQLDriverPyBaseError 140 | | ); | |_^ | = 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:136:1 | 136 | / create_exception!( 137 | | psqlpy.exceptions, 138 | | MacAddrConversionError, 139 | | RustPSQLDriverPyBaseError 140 | | ); | |_^ | = 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:130:1 | 130 | / create_exception!( 131 | | psqlpy.exceptions, 132 | | UUIDValueConvertError, 133 | | RustPSQLDriverPyBaseError 134 | | ); | |_^ | = 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:130:1 | 130 | / create_exception!( 131 | | psqlpy.exceptions, 132 | | UUIDValueConvertError, 133 | | RustPSQLDriverPyBaseError 134 | | ); | |_^ | = 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:124:1 | 124 | / create_exception!( 125 | | psqlpy.exceptions, 126 | | PyToRustValueMappingError, 127 | | RustPSQLDriverPyBaseError 128 | | ); | |_^ | = 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:124:1 | 124 | / create_exception!( 125 | | psqlpy.exceptions, 126 | | PyToRustValueMappingError, 127 | | RustPSQLDriverPyBaseError 128 | | ); | |_^ | = 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:119:1 | 119 | / create_exception!( 120 | | psqlpy.exceptions, 121 | | RustToPyValueMappingError, 122 | | RustPSQLDriverPyBaseError 123 | | ); | |_^ | = 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:119:1 | 119 | / create_exception!( 120 | | psqlpy.exceptions, 121 | | RustToPyValueMappingError, 122 | | RustPSQLDriverPyBaseError 123 | | ); | |_^ | = 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:116:1 | 116 | create_exception!(psqlpy.exceptions, ListenerCallbackError, BaseListenerError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = 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:116:1 | 116 | create_exception!(psqlpy.exceptions, ListenerCallbackError, BaseListenerError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = 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:115:1 | 115 | create_exception!(psqlpy.exceptions, ListenerClosedError, BaseListenerError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = 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:115:1 | 115 | create_exception!(psqlpy.exceptions, ListenerClosedError, BaseListenerError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = 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!(psqlpy.exceptions, ListenerStartError, BaseListenerError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = 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!(psqlpy.exceptions, ListenerStartError, BaseListenerError); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = 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 | | BaseListenerError, 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 | | BaseListenerError, 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)

error: unneeded unit return type --> src/driver/listener.rs:159:40 | 159 | async fn update_listen_query(&self) -> () { | ^^^^^^ help: remove the `-> ()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unused_unit = note: `-D clippy::unused-unit` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::unused_unit)]`

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/