Allow PNI in PendingMember #973
Annotations
122 errors and 83 warnings
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L97
error[E0599]: no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:97:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_pni` not found for this struct
...
97 | ServiceAddress::from_pni(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
97 | ServiceAddress::from(service_id.into())
| ~~~~
|
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L94
error[E0599]: no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:94:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_aci` not found for this struct
...
94 | ServiceAddress::from_aci(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
94 | ServiceAddress::from(service_id.into())
| ~~~~
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L96
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:96:13
|
96 | ServiceId::Pni(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
96 | DeviceId::Pni(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L93
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:93:13
|
93 | ServiceId::Aci(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
93 | DeviceId::Aci(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L91
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:91:25
|
91 | fn from(service_id: ServiceId) -> Self {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
91 | fn from(service_id: DeviceId) -> Self {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L90
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:90:11
|
90 | impl From<ServiceId> for ServiceAddress {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
90 | impl From<DeviceId> for ServiceAddress {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L97
error[E0599]: no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:97:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_pni` not found for this struct
...
97 | ServiceAddress::from_pni(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
97 | ServiceAddress::from(service_id.into())
| ~~~~
|
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L94
error[E0599]: no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:94:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_aci` not found for this struct
...
94 | ServiceAddress::from_aci(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
94 | ServiceAddress::from(service_id.into())
| ~~~~
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L96
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:96:13
|
96 | ServiceId::Pni(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
96 | DeviceId::Pni(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L93
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:93:13
|
93 | ServiceId::Aci(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
93 | DeviceId::Aci(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L91
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:91:25
|
91 | fn from(service_id: ServiceId) -> Self {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
91 | fn from(service_id: DeviceId) -> Self {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L90
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:90:11
|
90 | impl From<ServiceId> for ServiceAddress {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
90 | impl From<DeviceId> for ServiceAddress {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
Clippy (libsignal-service, unsend-futures)
Clippy had exited with the 101 exit code
|
Clippy (libsignal-service)
Clippy had exited with the 101 exit code
|
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L97
error[E0599]: no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:97:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_pni` not found for this struct
...
97 | ServiceAddress::from_pni(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
97 | ServiceAddress::from(service_id.into())
| ~~~~
|
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L94
error[E0599]: no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:94:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_aci` not found for this struct
...
94 | ServiceAddress::from_aci(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
94 | ServiceAddress::from(service_id.into())
| ~~~~
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L96
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:96:13
|
96 | ServiceId::Pni(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
96 | DeviceId::Pni(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L93
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:93:13
|
93 | ServiceId::Aci(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
93 | DeviceId::Aci(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L91
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:91:25
|
91 | fn from(service_id: ServiceId) -> Self {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
91 | fn from(service_id: DeviceId) -> Self {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L90
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:90:11
|
90 | impl From<ServiceId> for ServiceAddress {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
90 | impl From<DeviceId> for ServiceAddress {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service, Rust stable)
could not compile `libsignal-service` (lib) due to 6 previous errors
|
Build (libsignal-service, Rust stable)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L97
error[E0599]: no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:97:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_pni` not found for this struct
...
97 | ServiceAddress::from_pni(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
97 | ServiceAddress::from(service_id.into())
| ~~~~
|
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L94
error[E0599]: no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:94:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_aci` not found for this struct
...
94 | ServiceAddress::from_aci(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
94 | ServiceAddress::from(service_id.into())
| ~~~~
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L96
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:96:13
|
96 | ServiceId::Pni(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
96 | DeviceId::Pni(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L93
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:93:13
|
93 | ServiceId::Aci(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
93 | DeviceId::Aci(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L91
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:91:25
|
91 | fn from(service_id: ServiceId) -> Self {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
91 | fn from(service_id: DeviceId) -> Self {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L90
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:90:11
|
90 | impl From<ServiceId> for ServiceAddress {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
90 | impl From<DeviceId> for ServiceAddress {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service, Rust stable):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service, Rust stable)
could not compile `libsignal-service` (lib) due to 6 previous errors
|
Build (libsignal-service, Rust stable)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Clippy (libsignal-service-hyper)
Clippy had exited with the 101 exit code
|
Build (libsignal-service, Rust beta):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service, Rust beta):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service, Rust beta):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service, Rust beta):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service, Rust beta):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service, Rust beta):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service, Rust beta)
could not compile `libsignal-service` (lib) due to 6 previous errors
|
Build (libsignal-service, Rust beta)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Build (libsignal-service, Rust nightly):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service, Rust nightly):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service, Rust nightly):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service, Rust nightly):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service, Rust nightly):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service, Rust nightly):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service, Rust nightly)
could not compile `libsignal-service` (lib) due to 6 previous errors
|
Build (libsignal-service, Rust nightly)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Clippy (libsignal-service-actix)
Clippy had exited with the 101 exit code
|
Build (libsignal-service-hyper, Rust nightly):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-hyper, Rust nightly):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-hyper, Rust nightly):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-hyper, Rust nightly):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-hyper, Rust nightly):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-hyper, Rust nightly):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-hyper, Rust nightly)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-hyper, Rust stable)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-hyper, Rust stable):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-hyper, Rust stable)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Build (libsignal-service-hyper, Rust beta):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-hyper, Rust beta):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-hyper, Rust beta):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-hyper, Rust beta):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-hyper, Rust beta):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-hyper, Rust beta):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-hyper, Rust beta)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Build (libsignal-service-actix, Rust stable):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-actix, Rust stable):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-actix, Rust stable):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-actix, Rust stable):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-actix, Rust stable):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-actix, Rust stable):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-actix, Rust stable)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Build (libsignal-service-actix, Rust beta):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-actix, Rust beta):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-actix, Rust beta):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-actix, Rust beta):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-actix, Rust beta):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-actix, Rust beta):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-actix, Rust beta)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L97
error[E0599]: no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:97:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_pni` not found for this struct
...
97 | ServiceAddress::from_pni(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
97 | ServiceAddress::from(service_id.into())
| ~~~~
|
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope:
libsignal-service/src/service_address.rs#L94
error[E0599]: no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
--> libsignal-service/src/service_address.rs:94:33
|
18 | pub struct ServiceAddress {
| ------------------------- function or associated item `from_aci` not found for this struct
...
94 | ServiceAddress::from_aci(service_id.into())
| ^^^^^^^^ function or associated item not found in `ServiceAddress`
|
note: if you're trying to build a new `service_address::ServiceAddress` consider using one of the following associated functions:
service_address::ServiceAddress::new_aci
service_address::ServiceAddress::new_pni
--> libsignal-service/src/service_address.rs:51:5
|
51 | pub fn new_aci(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
58 | pub fn new_pni(uuid: Uuid) -> Self {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: there is an associated function `from` with a similar name
|
94 | ServiceAddress::from(service_id.into())
| ~~~~
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L96
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:96:13
|
96 | ServiceId::Pni(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
96 | DeviceId::Pni(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
failed to resolve: use of undeclared type `ServiceId`:
libsignal-service/src/service_address.rs#L93
error[E0433]: failed to resolve: use of undeclared type `ServiceId`
--> libsignal-service/src/service_address.rs:93:13
|
93 | ServiceId::Aci(service_id) => {
| ^^^^^^^^^ use of undeclared type `ServiceId`
|
help: a struct with a similar name exists
|
93 | DeviceId::Aci(service_id) => {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L91
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:91:25
|
91 | fn from(service_id: ServiceId) -> Self {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
91 | fn from(service_id: DeviceId) -> Self {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
cannot find type `ServiceId` in this scope:
libsignal-service/src/service_address.rs#L90
error[E0412]: cannot find type `ServiceId` in this scope
--> libsignal-service/src/service_address.rs:90:11
|
90 | impl From<ServiceId> for ServiceAddress {
| ^^^^^^^^^
|
::: /home/runner/.cargo/git/checkouts/libsignal-e5ca3c64ee2f7cbe/e46841e/rust/core/src/address.rs:671:1
|
671 | pub struct DeviceId(u32);
| ------------------- similarly named struct `DeviceId` defined here
|
help: a struct with a similar name exists
|
90 | impl From<DeviceId> for ServiceAddress {
| ~~~~~~~~
help: consider importing one of these enums
|
1 + use crate::protocol::ServiceId;
|
1 + use libsignal_protocol::ServiceId;
|
|
Clippy (libsignal-service-hyper, unsend-futures)
Clippy had exited with the 101 exit code
|
Build (libsignal-service-actix, Rust nightly):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-actix, Rust nightly):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-actix, Rust nightly):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-actix, Rust nightly):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-actix, Rust nightly):
libsignal-service/src/service_address.rs#L94
no function or associated item named `from_aci` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-actix, Rust nightly):
libsignal-service/src/service_address.rs#L97
no function or associated item named `from_pni` found for struct `service_address::ServiceAddress` in the current scope
|
Build (libsignal-service-actix, Rust nightly)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Build (libsignal-service-actix, Rust 1.75):
libsignal-service/src/service_address.rs#L90
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-actix, Rust 1.75):
libsignal-service/src/service_address.rs#L91
cannot find type `ServiceId` in this scope
|
Build (libsignal-service-actix, Rust 1.75):
libsignal-service/src/service_address.rs#L93
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-actix, Rust 1.75):
libsignal-service/src/service_address.rs#L96
failed to resolve: use of undeclared type `ServiceId`
|
Build (libsignal-service-actix, Rust 1.75)
could not compile `libsignal-service` (lib) due to 4 previous errors
|
Build (libsignal-service-actix, Rust 1.75)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Check code formatting
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Clippy (libsignal-service, unsend-futures)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Clippy (libsignal-service, unsend-futures)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Clippy (libsignal-service)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Clippy (libsignal-service)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service, Rust stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service, Rust stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service, Rust stable)
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/
|
Build (libsignal-service, Rust stable)
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/
|
Build (libsignal-service, Rust stable)
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/
|
Build (libsignal-service, Rust stable)
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/
|
Build (libsignal-service, Rust stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service, Rust stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service, Rust stable)
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/
|
Build (libsignal-service, Rust stable)
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/
|
Build (libsignal-service, Rust stable)
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/
|
Build (libsignal-service, Rust stable)
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/
|
Clippy (libsignal-service-hyper)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Clippy (libsignal-service-hyper)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service, Rust beta)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service, Rust beta)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service, Rust beta)
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/
|
Build (libsignal-service, Rust beta)
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/
|
Build (libsignal-service, Rust beta)
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/
|
Build (libsignal-service, Rust beta)
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/
|
Build (libsignal-service, Rust nightly)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service, Rust nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service, Rust nightly)
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/
|
Build (libsignal-service, Rust nightly)
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/
|
Build (libsignal-service, Rust nightly)
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/
|
Build (libsignal-service, Rust nightly)
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/
|
Clippy (libsignal-service-actix)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Clippy (libsignal-service-actix)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-hyper, Rust nightly)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service-hyper, Rust nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-hyper, Rust nightly)
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/
|
Build (libsignal-service-hyper, Rust nightly)
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/
|
Build (libsignal-service-hyper, Rust nightly)
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/
|
Build (libsignal-service-hyper, Rust nightly)
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/
|
Build (libsignal-service-hyper, Rust stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service-hyper, Rust stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-hyper, Rust stable)
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/
|
Build (libsignal-service-hyper, Rust stable)
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/
|
Build (libsignal-service-hyper, Rust stable)
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/
|
Build (libsignal-service-hyper, Rust stable)
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/
|
Build (libsignal-service-hyper, Rust stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service-hyper, Rust stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-hyper, Rust stable)
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/
|
Build (libsignal-service-hyper, Rust stable)
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/
|
Build (libsignal-service-hyper, Rust stable)
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/
|
Build (libsignal-service-hyper, Rust stable)
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/
|
Build (libsignal-service-hyper, Rust beta)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service-hyper, Rust beta)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-hyper, Rust beta)
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/
|
Build (libsignal-service-hyper, Rust beta)
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/
|
Build (libsignal-service-hyper, Rust beta)
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/
|
Build (libsignal-service-hyper, Rust beta)
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/
|
Build (libsignal-service-actix, Rust stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service-actix, Rust stable)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-actix, Rust stable)
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/
|
Build (libsignal-service-actix, Rust stable)
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/
|
Build (libsignal-service-actix, Rust stable)
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/
|
Build (libsignal-service-actix, Rust stable)
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/
|
Build (libsignal-service-actix, Rust beta)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service-actix, Rust beta)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-actix, Rust beta)
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/
|
Build (libsignal-service-actix, Rust beta)
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/
|
Build (libsignal-service-actix, Rust beta)
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/
|
Build (libsignal-service-actix, Rust beta)
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/
|
Clippy (libsignal-service-hyper, unsend-futures)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Clippy (libsignal-service-hyper, unsend-futures)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-actix, Rust nightly)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service-actix, Rust nightly)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-actix, Rust nightly)
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/
|
Build (libsignal-service-actix, Rust nightly)
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/
|
Build (libsignal-service-actix, Rust nightly)
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/
|
Build (libsignal-service-actix, Rust nightly)
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/
|
Build (libsignal-service-actix, Rust 1.75)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Build (libsignal-service-actix, Rust 1.75)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Build (libsignal-service-actix, Rust 1.75)
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/
|
Build (libsignal-service-actix, Rust 1.75)
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/
|
Build (libsignal-service-actix, Rust 1.75)
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/
|
Build (libsignal-service-actix, Rust 1.75)
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/
|