You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @netomi@ashbeitz@mbarbero@mrybczyn,
I am facing this issue while try to build freyja using the command:
RUST_BACKTRACE=1 cargo run -p freyja
can anyone help me to fix this?
/freyja$ RUST_BACKTRACE=1 cargo run -p freyja
Compiling core-protobuf-data-access v0.1.0 (/home/sari/EclipseIF/freyja/proto/core_protobuf_data_access)
Compiling samples-protobuf-data-access v0.1.0 (/home/sari/EclipseIF/freyja/proto/samples_protobuf_data_access)
Compiling service_discovery_proto v0.1.0 (/home/sari/EclipseIF/freyja/proto/service_discovery_proto)
Compiling mqtt-data-adapter v0.1.0 (/home/sari/EclipseIF/freyja/adapters/data/mqtt_data_adapter)
error: failed to run custom build command for samples-protobuf-data-access v0.1.0 (/home/sari/EclipseIF/freyja/proto/samples_protobuf_data_access)
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
Caused by:
process didn't exit successfully: /home/sari/EclipseIF/freyja/target/debug/build/samples-protobuf-data-access-7ee66b3bc2d96d44/build-script-build (exit status: 101)
--- stderr
thread 'main' panicked at 'Unable to retrieve remote proto file: https://raw.githubusercontent.com/eclipse-ibeji/ibeji/0.1.1/samples/interfaces/sample_grpc/v1/digital_twin_consumer.proto: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer', build_common/src/lib.rs:80:19
stack backtrace:
0: rust_begin_unwind
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
1: core::panicking::panic_fmt
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
2: freyja_build_common::compile_remote_proto
at /home/sari/EclipseIF/freyja/build_common/src/lib.rs:80:19
3: build_script_build::main
4: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for service_discovery_proto v0.1.0 (/home/sari/EclipseIF/freyja/proto/service_discovery_proto)
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
Caused by:
process didn't exit successfully: /home/sari/EclipseIF/freyja/target/debug/build/service_discovery_proto-7edcb5e22016edbf/build-script-build (exit status: 101)
--- stderr
thread 'main' panicked at 'Unable to retrieve remote proto file: https://raw.githubusercontent.com/eclipse-chariott/chariott/0.2.1/service_discovery/proto/core/v1/service_registry.proto: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer', build_common/src/lib.rs:80:19
stack backtrace:
0: rust_begin_unwind
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
1: core::panicking::panic_fmt
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
2: freyja_build_common::compile_remote_proto
at /home/sari/EclipseIF/freyja/build_common/src/lib.rs:80:19
3: build_script_build::main
4: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
error: failed to run custom build command for core-protobuf-data-access v0.1.0 (/home/sari/EclipseIF/freyja/proto/core_protobuf_data_access)
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
Caused by:
process didn't exit successfully: /home/sari/EclipseIF/freyja/target/debug/build/core-protobuf-data-access-242d973d14e150c6/build-script-build (exit status: 101)
--- stderr
thread 'main' panicked at 'Unable to retrieve remote proto file: https://raw.githubusercontent.com/eclipse-ibeji/ibeji/0.1.1/interfaces/invehicle_digital_twin/v1/invehicle_digital_twin.proto: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer', build_common/src/lib.rs:80:19
stack backtrace:
0: rust_begin_unwind
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
1: core::panicking::panic_fmt
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
2: freyja_build_common::compile_remote_proto
at /home/sari/EclipseIF/freyja/build_common/src/lib.rs:80:19
3: build_script_build::main
4: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
The text was updated successfully, but these errors were encountered:
Hi @netomi @ashbeitz @mbarbero @mrybczyn,
I am facing this issue while try to build freyja using the command:
RUST_BACKTRACE=1 cargo run -p freyja
can anyone help me to fix this?
/freyja$ RUST_BACKTRACE=1 cargo run -p freyja
Compiling core-protobuf-data-access v0.1.0 (/home/sari/EclipseIF/freyja/proto/core_protobuf_data_access)
Compiling samples-protobuf-data-access v0.1.0 (/home/sari/EclipseIF/freyja/proto/samples_protobuf_data_access)
Compiling service_discovery_proto v0.1.0 (/home/sari/EclipseIF/freyja/proto/service_discovery_proto)
Compiling mqtt-data-adapter v0.1.0 (/home/sari/EclipseIF/freyja/adapters/data/mqtt_data_adapter)
error: failed to run custom build command for
samples-protobuf-data-access v0.1.0 (/home/sari/EclipseIF/freyja/proto/samples_protobuf_data_access)
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
Caused by:
process didn't exit successfully:
/home/sari/EclipseIF/freyja/target/debug/build/samples-protobuf-data-access-7ee66b3bc2d96d44/build-script-build
(exit status: 101)--- stderr
thread 'main' panicked at 'Unable to retrieve remote proto file: https://raw.githubusercontent.com/eclipse-ibeji/ibeji/0.1.1/samples/interfaces/sample_grpc/v1/digital_twin_consumer.proto: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer', build_common/src/lib.rs:80:19
stack backtrace:
0: rust_begin_unwind
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
1: core::panicking::panic_fmt
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
2: freyja_build_common::compile_remote_proto
at /home/sari/EclipseIF/freyja/build_common/src/lib.rs:80:19
3: build_script_build::main
4: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with
RUST_BACKTRACE=full
for a verbose backtrace.warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for
service_discovery_proto v0.1.0 (/home/sari/EclipseIF/freyja/proto/service_discovery_proto)
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
Caused by:
process didn't exit successfully:
/home/sari/EclipseIF/freyja/target/debug/build/service_discovery_proto-7edcb5e22016edbf/build-script-build
(exit status: 101)--- stderr
thread 'main' panicked at 'Unable to retrieve remote proto file: https://raw.githubusercontent.com/eclipse-chariott/chariott/0.2.1/service_discovery/proto/core/v1/service_registry.proto: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer', build_common/src/lib.rs:80:19
stack backtrace:
0: rust_begin_unwind
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
1: core::panicking::panic_fmt
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
2: freyja_build_common::compile_remote_proto
at /home/sari/EclipseIF/freyja/build_common/src/lib.rs:80:19
3: build_script_build::main
4: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with
RUST_BACKTRACE=full
for a verbose backtrace.error: failed to run custom build command for
core-protobuf-data-access v0.1.0 (/home/sari/EclipseIF/freyja/proto/core_protobuf_data_access)
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.
Caused by:
process didn't exit successfully:
/home/sari/EclipseIF/freyja/target/debug/build/core-protobuf-data-access-242d973d14e150c6/build-script-build
(exit status: 101)--- stderr
thread 'main' panicked at 'Unable to retrieve remote proto file: https://raw.githubusercontent.com/eclipse-ibeji/ibeji/0.1.1/interfaces/invehicle_digital_twin/v1/invehicle_digital_twin.proto: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer', build_common/src/lib.rs:80:19
stack backtrace:
0: rust_begin_unwind
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
1: core::panicking::panic_fmt
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
2: freyja_build_common::compile_remote_proto
at /home/sari/EclipseIF/freyja/build_common/src/lib.rs:80:19
3: build_script_build::main
4: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with
RUST_BACKTRACE=full
for a verbose backtrace.The text was updated successfully, but these errors were encountered: