thin-edge.io
thin-edge.io copied to clipboard
The open edge framework for lightweight IoT devices
**Is your feature improvement request related to a problem? Please describe.** In a container deployment and using the built-in bridge feature, it should be possible to run two instances of...
**Describe the bug** ``` ERROR tedge_mqtt_bridge::health: MQTT bridge failed to connect to local broker: Mqtt state: Mqtt serialization/deserialization error: payload size limit exceeded: 12928 ``` The bug happens when using...
**Describe the bug** If a workflow triggers a sub operation, then the mapper is incorrectly reacting to command status changes and sending a cloud message to transition operation status. For...
**Is your feature improvement request related to a problem? Please describe.** I would like to use a serial-number as my technical device-id, but use a different/more meaningful name for the...
**Describe the bug** Flaky unit test. **Test name** `tedge::mqtt tests::test_cli_pub_basic::some_2_expects` **Failures** ```` FAIL [ 0.637s] tedge::mqtt tests::test_cli_pub_basic::some_2_expects --- STDOUT: tedge::mqtt tests::test_cli_pub_basic::some_2_expects --- running 1 test test tests::test_cli_pub_basic::some_2_expects ... FAILED failures:...
**Is your feature request related to a problem? Please describe.** Some customers with older Cumulocity IoT agents, have used SmartREST 1. Currently thin-edge.io does not support the SmartREST 1 topics,...
**Is your feature request related to a problem? Please describe.** Support Cumulocity IoT basic auth registration process to provide an upgrade path for existing customers whom use (legacy) SmartREST 1.0...
## Proposed changes ⚠️ **Do not merge this PR as it contains very rough Rust code to verify the functionality** Proof of concept / validation, that if thin-edge.io would support...
**Is your feature request related to a problem? Please describe.** A traditional industrial company doesn't allow outbound connections using 8883 or other ports. Only allow 443 ports. **Describe the solution...
flaky unittest: file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api
**Describe the bug** Flaky unit test. **Test name** `tedge-agent file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api` **Failures** ``` FAIL [ 0.019s] tedge-agent file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api --- STDOUT: tedge-agent file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api --- running 1 test test file_transfer_server::http_rest::tests::uploaded_file_can_be_downloaded_from_the_api ... FAILED failures:...