Watchers are not paused/destroyed when keepalive is set to true

Environment

Operating System: Darwin
Node Version:     v18.15.0
Nuxt Version:     3.8.0
CLI Version:      3.9.1
Nitro Version:    2.7.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      ssr, runtimeConfig, site, modules, imports, experimental, sourcemap, devtools, app, vite, typescript, css, postcss, nitro, piniaPersistedstate, http, auth, colorMode, plausible, sitemap
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-watch-teardown-bug
Describe the bug
When keepalive is set to true in nuxt.config.ts, watchers are not properly destroyed. This means if you have dynamic pages with a watcher and navigate through a few pages and then an action or mutation triggers a watcher, it fires once for each page, see reproduction with magic keys.
Additional context
No response
Logs
No response

Potentially related to https://github.com/nuxt/nuxt/issues/18871

This is upstream behaviour. You can consider using onActivated and onDeactivated when using keepalive.
https://vuejs.org/guide/built-ins/keep-alive.html#lifecycle-of-cached-instance
Vue 3 only reproduction: https://stackblitz.com/edit/github-q7kqa2?file=src/App.vue,src/pages/About.vue,src/pages/Home.vue,src/pages/Another.vue.

Oh crazy! Gonna roll without keepalive then. Thanks for clarifying 🙏🏽


memory leak postgresql close connection

related: #126

closing the database connection is no longer an existing problem, I will close this issue and better understand the actual problem


Data Science with Python : Facial Keypoints Detection

Description
Welcome to the 'DSWP' Team, good to see you here.
With this issue, the readers will know on how to predict keypoints on face images. You analyze faces in images and videos along with expressions.
Here is the dataset to follow : https://www.kaggle.com/c/facial-keypoints-detection/data
To get assigned to this issue, add your serial numbers mentioned in the spreadsheet of "Data Science with Python", the approach one would follow and the choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
If you had referred any resources, add them up in "DS Resources". Similarly, if you had used datasets, include them in "DS Datasets".
Domain: Kaggle Competitions
Mentors Assigned : Pushpit Jain | Aishani Singh
Points to Note :
The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title" should be the same. Include issue number along with it.
Changes should be made inside the Datascience_With_Python/ directory & Datascience_With_Python branch.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'GWOC' contributors of 'DSWP' domain.
All the best. Enjoy your journey ahead. 😎
Domain
Data Science with Python
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

./assign Documentation

Just choose one issue you like to. @rahilmehta-24

/assign Documentation

Don't self assign yourself without providing details. @eliziaeve7


can't  reproduce the step-by-step in the wiki page

Running $ python3 -i tptp_experiments.py (note the typo in the wiki _ not -).
$ python3 -i tptp_experiments.py
Traceback (most recent call last):
  File "tptp_experiments.py", line 245, in <module>
    problems_dir = sys.argv[1]
IndexError: list index out of range
>>>

sorry, ignore.


\prefacesection removes the indent from the first paragraph of the acknowledgment

Why do \prefacesection  remove the indent from the first paragraph? Is this done on purpose?
I tried \indent but I believe that the command   \prefacesection  makes the former command useless.

That's really a matter of style. Some style guides prefer first paragraph of each without indentation.


KAFKA-12170: Fix for Connect Cast SMT to correctly transform a Byte array into a string

Cast SMT transformation for bytes -> string.
Without this fix, the conversion becomes
ByteBuffer.toString(), which always gives one of these useless results:
"java.nio.HeapByteBuffer[pos=0 lim=4 cap=4]"
"[B@5ec0a365" (for byte array)
With this change, the byte array is converted into a hex string of the
byte buffer content, for example
"FEDCBA9876543210"

Completed with test case and successfully tried out in a
real database conversion.
Committer Checklist (excluded from commit message)

[X ] Verify design and implementation
[ X] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@sknop  hello , It seems like there are some style error .
You can use ./gradlew checkstyleMain checkstyleTest to cehck .

@sknop  hello , It seems like there are some style error .
You can use ./gradlew checkstyleMain checkstyleTest to cehck .

@sknop hello , It seems like there are some style error .
You can use ./gradlew checkstyleMain checkstyleTest to cehck .

Thank you for your feedback. I have adjusted the code and it now passes the style check.

@sknop hello , It seems like there are some style error .
You can use ./gradlew checkstyleMain checkstyleTest to cehck .

Thank you for your feedback. I have adjusted the code and it now passes the style check.

Hi Mickael
Thank you so much for your code review. I have adjusted the code according to your suggestions, they all make sense to me.
Cheers
Sven Erik
<EMAIL_ADDRESS>On 18 Feb 2021, 16:40 +0000, apache/kafka<EMAIL_ADDRESS>wrote:

@mimaison

Before this fix, the changes made in #4820 (KAFKA-6684) resulted in toString() being called on byte[] and ByteBuffer. As highlighted in this PR and issue that ByteBuffer.toString() is not useful, but the toString() on byte[] still works. This PR seems to change that behavior, which would not be backward compatible.
The discussion on PR #4820 also talked about making this compatible with Values.convertToString(...), which for byte[] and ByteBuffer results in a base 64 encoded string (with ISO-8859-1 encoding). See the Values code for details.
Because of this, it seems much more sensible to also use base64 here for ByteBuffer so it matches the existing behavior with byte[].
I agree that it maybe doesn't suffice in all user situations, so if we also want to support other encodings we'd need other config changes that will require using the KIP mechanism to propose such enhancements.

What about documentation?
Where is the documentation stored and what is the process to change it? It might be useful to point out that the Cast SMT will create base64 strings for byte arrays.

The documentation is auto-generated from the code, via TransformationDoc.

Thank you @rhauch. Just to make sure I understand this correctly - the types mentioned in the cast string are the target casts, not the source tasks. The current code does not allow casting to a byte array, only casting from a byte array.
As I understand it, therefore no documentation changes are required (except maybe for release notes)?

If we don't clarify the documentation, then I think users will be very confused. Can you take a stab at improving/expanding the documentation a bit to clarify the input and output types?

Yes of course, totally agree.

Test failures are not related:
JDK 8 / org.apache.kafka.connect.mirror.integration.MirrorConnectorsIntegrationSSLTest.testOneWayReplicationWithAutoOffsetSync()
JDK 11 / org.apache.kafka.connect.integration.RebalanceSourceConnectorsIntegrationTest.testMultipleWorkersRejoining

Merging to trunk


Makefile no longer installs mutatingwebhook.yaml

What happened:
After running make cluster-up the install does not include the mutating webhook.
kubectl get mutatingwebhookconfigurations.admissionregistration.k8s.io pod-identity-webhook
Error from server (NotFound): mutatingwebhookconfigurations.admissionregistration.k8s.io "pod-identity-webhook" not found

What you expected to happen:
kubectl get mutatingwebhookconfigurations.admissionregistration.k8s.io pod-identity-webhook
NAME                   WEBHOOKS   AGE
pod-identity-webhook   1          9h

How to reproduce it (as minimally and precisely as possible):
make cluster-up
Anything else we need to know?:
It looks like the mutatingwebhook.yaml inclusion was unintentionally removed as part of the csr removal.
https://github.com/aws/amazon-eks-pod-identity-webhook/commit/131e8e1dc768d2005d4aa5b80c4d85652b8f1839#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52L75

I'll work on a simple PR here.


Train F2-NeRF on your custom data

Generate cameras file:
When I run the command of :python scripts/colmap2poses.py --data_dir ./data//
The issues  as follows：
Traceback (most recent call last):
File "/home/xxx/anaconda3/envs/F2-NERF/lib/python3.9/site-packages/click/core.py", line 1055, in main
rv = self.invoke(ctx)
File "/home/xxx/anaconda3/envs/F2-NERF/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/xxx/anaconda3/envs/F2-NERF/lib/python3.9/site-packages/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "/home/xxx/f2-nerf/scripts/colmap2poses.py", line 218, in main
dataset = Dataset(data_dir)
File "/home/xxx/f2-nerf/scripts/colmap2poses.py", line 137, in init
image_id_to_image_idx[name_to_ids[image_name]] = sorted_image_names.index(image_name)
IndexError: index 372 is out of bounds for axis 0 with size 29
python-BaseException

Hello, it seems to be a common issue when some images fail to be registered in COLMAP SfM. I would try to address it in the processing when I have time. At this stage you may check you input images and make sure that the images are with rich and sharp visual textures for a successful structure-from-motion.

@Totoro97
How can I use the pose data to generate the training data?

Thank you for your reply

Hello @Totoro97, do you have any plan to fix it? COLMAP SfM is always failed on my dataset.
Or can you integrate hloc into your code as an alternate option for using COLMAP?

Generate cameras file:
When I run the command of :python scripts/colmap2poses.py --data_dir ./data// The issues as follows： Traceback (most recent call last): File "/home/xxx/anaconda3/envs/F2-NERF/lib/python3.9/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/home/xxx/anaconda3/envs/F2-NERF/lib/python3.9/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/home/xxx/anaconda3/envs/F2-NERF/lib/python3.9/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/home/xxx/f2-nerf/scripts/colmap2poses.py", line 218, in main dataset = Dataset(data_dir) File "/home/xxx/f2-nerf/scripts/colmap2poses.py", line 137, in init image_id_to_image_idx[name_to_ids[image_name]] = sorted_image_names.index(image_name) IndexError: index 372 is out of bounds for axis 0 with size 29 python-BaseException

I solved it by change https://github.com/Totoro97/f2-nerf/blob/683b7b8326b35b70c8d2a2850a1f794a8ffca010/scripts/colmap2poses.py#LL135C25-L135C25 to
image_id_to_image_idx = np.zeros(len(os.listdir(pjoin(data_dir, "images"))) + 10, dtype=np.int32)


tedge-agent can leave an operation in a non-final state if the service is restarted

Describe the bug

An operation can be left in a non final state (e.g. anything other than successful or failed) if the tedge-agent is shutdown whilst processing a workflow state. For cloud operations this generally means that the operation will be left in the EXECUTING state (as the mapper relies on these status updates to publish the operation status to the cloud).
If the tedge-agent is processing a workflow state, and then receives a SIGTERM, then the agent saves the next state as "failed", but the local MQTT message is not published (as the agent is still shutting down). If the "next" state is "failed", then the tedge-agent will not try to republish the command's MQTT message as "failed" is a final state (and waiting the operation to be cleared via an empty retain message).
Looking at the tedge-agent logs, it shows that the status update failed to send:
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.972204101Z  INFO tedge_api::workflow::log::command_log: => moving to example @ failed
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.973304352Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/example/local-1727906852" }, payload: "{"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","reason":"sleep killed by signal 15","status":"failed"}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.973503103Z ERROR Runtime: Actor WorkflowActor-10 has finished unsuccessfully: ChannelError(SendError(SendError { kind: Disconnected }))
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.973518978Z  INFO Runtime: All actors have finished

Below shows an exert from the custom workflow (firmware_update) which shows the commit state's script being killed via SIGTERM (15), where the SIGTERM sent to the state script is due to the tedge-agent actor being shutdown (also via a SIGTERM).
==================================================================
Triggered example workflow
==================================================================

topic:     te/device/child02///cmd/example/local-1727906852
operation: example
cmd_id:    local-1727906852
time:      2024-10-02T22:07:32.931748348Z

==================================================================

----------------------[ example @ init | time=2024-10-02T22:07:32.933776768Z ]----------------------

State:    {"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","status":"init"}

Action:   move to executing state

=> moving to example @ executing

----------------------[ example @ executing | time=2024-10-02T22:07:32.939933069Z ]----------------------

State:    {"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","status":"executing"}

Action:   sleep 1000000

Killed by signal: 15

stderr (EMPTY)

stdout (EMPTY)
=> moving to example @ failed

----------------------[ example @ failed | time=2024-10-02T22:07:43.011961995Z ]----------------------

State:    {"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","reason":"sleep killed by signal 15","resumed_at":"1727906862.0","status":"failed"}

Action:   wait for the requester to finalize the command

To Reproduce

This behaviour was first experienced when creating a dummy firmware_update operation, however the following minimal workflow/procedure can be used to reproduce the issue:

Create the following workflow on a thin-edge.io device
cat <<EOT > /etc/tedge/operations/example.toml
operation = "example"

[init]
action = "proceed"
on_success = "executing"

[executing]
script = "sleep 120"
on_success = "successful"

[successful]
action = "cleanup"

[failed]
action = "cleanup"
EOT

Restart tedge-agent (so it will reload the new workflow)
systemctl restart tedge-agent

Trigger the workflow and restart it (to simulate interrupting the tedge-agent service with a SIGTERM)
TOPIC="$(tedge config get mqtt.topic_root)/$(tedge config get mqtt.device_topic_id)/cmd/example/local-$(date +%s)"
tedge mqtt pub -r -q 1 "$TOPIC" '{"status":"init"}'

sleep 10
systemctl restart tedge-agent
echo "Check if the operation"
tedge mqtt sub "$TOPIC"

The error condition is that the operation message published to the local MQTT broker will remain in the state and is not updated by the agent to set it to failed.

Cleanup the operation. This step is to remove the message from the MQTT broker
tedge mqtt pub -r "$TOPIC" ''

Expected behavior

The tedge-agent should leave a local operation in a non-final state (e.g. successful or failed). Ideally the tedge-agent should remember if it was successful publishing the operation status update or not, and retry it until it is successful.
Screenshots

Environment (please complete the following information):

OS [incl. version]: Debian 12
Hardware [incl. revision]: Container
System-Architecture [e.g. result of "uname -a"]: aarch64 / arm64
thin-edge.io version [e.g. 0.1.0]: 1.3.0

Additional context

tedge-agent logs (debug level)
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.91599274Z DEBUG MQTT recv: [te/device/child02///cmd/example/local-1727906852 qos=1] {"status":"init"}
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.919216412Z DEBUG Mqtt-Request-Converter: recv Some(MqttMessage(MqttMessage { topic: Topic { name: "te/device/child02///cmd/example/local-1727906852" }, payload: "{"status":"init"}", qos: AtLeastOnce, retain: false }))
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.935506645Z  INFO tedge_agent::operation_workflows::actor: Moving example operation to state: executing
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.938747234Z  INFO tedge_api::workflow::log::command_log: => moving to example @ executing
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.939789944Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/example/local-1727906852" }, payload: "{"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","status":"executing"}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.939841277Z DEBUG Mqtt-Request-Converter: recv Some(InternalCommandState(InternalCommandState(GenericCommandState { topic: Topic { name: "te/device/child02///cmd/example/local-1727906852" }, status: "executing", payload: Object {"logPath": String("/var/log/tedge/agent/workflow-example-local-1727906852.log"), "status": String("executing")}, invoking_command_topic: None })))
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.939960069Z DEBUG MQTT pub: [te/device/child02///cmd/example/local-1727906852 qos=1 retained] {"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","status":"executing"}
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.940031402Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/example/local-1727906852, Pkid = 19, Payload Size = 93
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.941241488Z  INFO tedge_agent::operation_workflows::actor: Processing example operation executing step with script: sleep 1000000
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.941296113Z DEBUG Script: recv Some(Execute { command: "sleep", args: ["1000000"], timeouts: None })
Oct 02 22:07:32 child02 tedge-agent[1200]: 2024-10-02T22:07:32.957338763Z DEBUG MQTT recv: [te/device/child02///cmd/example/local-1727906852 qos=1] {"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","status":"executing"}
Oct 02 22:07:42 child02 systemd[1]: Stopping tedge-agent.service - tedge-agent is a thin-edge.io component to support operations....
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949221649Z DEBUG Signal-Handler: send Shutdown
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949259149Z  INFO Runtime: Shutting down
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949287774Z DEBUG Runtime: Successfully sent shutdown request to Uploader-4
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949304524Z DEBUG Runtime: Successfully sent shutdown request to MQTT-1
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949320607Z DEBUG Runtime: Successfully sent shutdown request to Signal-Handler-0
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949347024Z DEBUG Runtime: Successfully sent shutdown request to HealthMonitorActor-11
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949358482Z DEBUG Runtime: Successfully sent shutdown request to WorkflowActor-10
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949362566Z DEBUG Runtime: Successfully sent shutdown request to LogManager-6
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949379232Z DEBUG Runtime: Successfully sent shutdown request to FsWatcher-2
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949391732Z DEBUG Runtime: Successfully sent shutdown request to Script-9
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949395191Z DEBUG Runtime: Successfully sent shutdown request to SoftwareManagerActor-8
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949399524Z DEBUG Runtime: Successfully sent shutdown request to RestartManagerActor-7
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949454107Z DEBUG device/child02/service/tedge-agent: recv None
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.949638149Z DEBUG Uploader: recv None
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.950455942Z DEBUG Signal-Handler: recv None
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.950611151Z DEBUG rumqttc::state: Publish. Topic = te/device/child02/service/tedge-agent/status/health, Pkid = 20, Payload Size = 28
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.950749609Z DEBUG rumqttc::state: Disconnect
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.950774943Z  INFO mqtt_channel::connection: MQTT connection closed
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.95207582Z DEBUG Log Manager: recv None
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952172695Z DEBUG SoftwareManager: recv None
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952191653Z DEBUG Script: recv None
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.95220857Z DEBUG RestartManager: recv None
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952112737Z DEBUG Runtime: Successfully sent shutdown request to ConfigManager-5
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952254695Z DEBUG Runtime: Successfully sent shutdown request to Downloader-3
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952307445Z  INFO Runtime: Actor has finished: HealthMonitorActor-11
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952379279Z  INFO Runtime: Actor has finished: Uploader-4
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952397404Z  INFO Runtime: Actor has finished: MQTT-1
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952459737Z  INFO Runtime: Actor has finished: Signal-Handler-0
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952467029Z  INFO Runtime: Actor has finished: FsWatcher-2
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952471112Z  INFO Runtime: Actor has finished: LogManager-6
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.95247457Z  INFO Runtime: Actor has finished: Script-9
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952478154Z  INFO Runtime: Actor has finished: RestartManagerActor-7
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952481737Z  INFO Runtime: Actor has finished: SoftwareManagerActor-8
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952515654Z DEBUG Downloader: recv None
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952552737Z DEBUG Tedge-Config-Manager: recv None
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952623737Z  INFO Runtime: Actor has finished: Downloader-3
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.952638696Z  INFO Runtime: Actor has finished: ConfigManager-5
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.972204101Z  INFO tedge_api::workflow::log::command_log: => moving to example @ failed
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.973304352Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/example/local-1727906852" }, payload: "{"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","reason":"sleep killed by signal 15","status":"failed"}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.973503103Z ERROR Runtime: Actor WorkflowActor-10 has finished unsuccessfully: ChannelError(SendError(SendError { kind: Disconnected }))
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.973518978Z  INFO Runtime: All actors have finished
Oct 02 22:07:42 child02 tedge-agent[1200]: 2024-10-02T22:07:42.97366577Z DEBUG sm-agent: flockfile::unix: Lockfile deleted ""/run/lock/tedge-agent.lock""
Oct 02 22:07:42 child02 systemd[1]: tedge-agent.service: Deactivated successfully.
Oct 02 22:07:42 child02 systemd[1]: Stopped tedge-agent.service - tedge-agent is a thin-edge.io component to support operations..
Oct 02 22:07:42 child02 systemd[1]: tedge-agent.service: Consumed 2.333s CPU time.
Oct 02 22:07:42 child02 systemd[1]: Starting tedge-agent.service - tedge-agent is a thin-edge.io component to support operations....
Oct 02 22:07:42 child02 systemd[1]: Started tedge-agent.service - tedge-agent is a thin-edge.io component to support operations..
Oct 02 22:07:42 child02 tedge-agent[1490]: 2024-10-02T22:07:42.988011542Z DEBUG tedge_config::tedge_config_cli::tedge_config_location: Loading configuration from "/etc/tedge/tedge.toml"
Oct 02 22:07:42 child02 tedge-agent[1490]: 2024-10-02T22:07:42.988046958Z DEBUG mqtt_channel::config: Using CA directory: /etc/ssl/certs
Oct 02 22:07:42 child02 tedge-agent[1490]: 2024-10-02T22:07:42.992810841Z DEBUG mqtt_channel::config: Using client certificate: /etc/tedge/device-certs/tedge-agent.crt
Oct 02 22:07:42 child02 tedge-agent[1490]: 2024-10-02T22:07:42.992838966Z DEBUG mqtt_channel::config: Using client private key: /etc/tedge/device-certs/tedge-agent.key
Oct 02 22:07:42 child02 tedge-agent[1490]: 2024-10-02T22:07:42.993170591Z DEBUG tedge_config::tedge_config_cli::tedge_config_location: Loading configuration from "/etc/tedge/tedge.toml"
Oct 02 22:07:42 child02 tedge-agent[1490]: 2024-10-02T22:07:42.9933948Z DEBUG tedge_config::tedge_config_cli::tedge_config_location: Loading configuration from "/etc/tedge/tedge.toml"
Oct 02 22:07:42 child02 tedge-agent[1490]: 2024-10-02T22:07:42.993656258Z DEBUG tedge_config::tedge_config_cli::tedge_config_location: Loading configuration from "/etc/tedge/tedge.toml"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007508405Z DEBUG flockfile::unix: Lockfile created "/run/lock/tedge-agent.lock"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007529446Z  INFO tedge_agent::agent: tedge-agent starting
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007556363Z  INFO sm-agent: tedge_agent::agent: Starting tedge-agent v1.3.1~42+ga50bdcf
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007574405Z DEBUG sm-agent:sm-agent: tedge_utils::file: Creating the directory "/etc/tedge/.agent"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007579196Z DEBUG sm-agent:sm-agent: tedge_utils::file: Applying desired user and group for already existing dir: "/etc/tedge/.agent"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00758653Z DEBUG sm-agent:sm-agent: tedge_utils::file: Creating the directory "/var/log/tedge/agent"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007595155Z DEBUG sm-agent:sm-agent: tedge_utils::file: Applying desired user and group for already existing dir: "/var/log/tedge/agent"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007604072Z DEBUG sm-agent:sm-agent: tedge_utils::file: Creating the directory "/var/tedge"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007606905Z DEBUG sm-agent:sm-agent: tedge_utils::file: Applying desired user and group for already existing dir: "/var/tedge"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007612655Z DEBUG sm-agent:sm-agent: tedge_utils::file: Creating the directory "/var/tedge/file-transfer"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00762028Z DEBUG sm-agent:sm-agent: tedge_utils::file: Applying desired user and group for already existing dir: "/var/tedge/file-transfer"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00762453Z DEBUG sm-agent:sm-agent: tedge_utils::file: Creating the directory "/var/tedge/cache"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007627447Z DEBUG sm-agent:sm-agent: tedge_utils::file: Applying desired user and group for already existing dir: "/var/tedge/cache"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.007630738Z DEBUG sm-agent:sm-agent: tedge_utils::file: Creating the directory "/etc/tedge/operations"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00763378Z DEBUG sm-agent:sm-agent: tedge_utils::file: Applying desired user and group for already existing dir: "/etc/tedge/operations"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00768528Z  INFO Runtime: Started
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008066739Z  INFO sm-agent: tedge_agent::operation_workflows: Using operation workflow definition from "/etc/tedge/operations/device_profile.toml" for 'device_profile' operation
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008253697Z  INFO sm-agent: tedge_agent::operation_workflows: Using operation workflow definition from "/etc/tedge/operations/firmware_update.toml" for 'firmware_update' operation
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008369114Z  INFO sm-agent: tedge_agent::operation_workflows: Using operation workflow definition from "/etc/tedge/operations/example.toml" for 'example' operation
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008706407Z  INFO sm-agent: tedge_config_manager::config: Using the configuration from /etc/tedge/plugins/tedge-configuration-plugin.toml
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008847032Z  INFO sm-agent: log_manager::config: Using the configuration from /etc/tedge/plugins/tedge-log-plugin.toml
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008919657Z  INFO sm-agent: tedge_agent::agent: Running as a child device, tedge_to_te_converter and File Transfer Service disabled
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008930574Z DEBUG sm-agent: Runtime: schedule Spawn(Signal-Handler)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008949324Z  INFO sm-agent: MQTT sub: te/device/child02///cmd/+/+
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008952449Z  INFO sm-agent: MQTT sub: te/device/child02/service/tedge-agent/cmd/health/check
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008954699Z  WARN sm-agent: MQTT sub: ignoring overlapping subscription to te/device/child02///cmd/health/check
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00895724Z DEBUG sm-agent: Runtime: schedule Spawn(MQTT)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008960365Z DEBUG sm-agent: Runtime: schedule Spawn(FsWatcher)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008963949Z DEBUG sm-agent: Runtime: schedule Spawn(Downloader)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00896674Z DEBUG sm-agent: Runtime: schedule Spawn(Uploader)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00896999Z DEBUG sm-agent: Runtime: schedule Spawn(ConfigManager)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008968532Z  INFO Runtime: Running Signal-Handler-0
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00897349Z DEBUG sm-agent: Runtime: schedule Spawn(LogManager)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008987157Z  INFO Runtime: Running MQTT-1
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.008996532Z  WARN sm-agent: tedge_agent::state_repository::state: Cannot use "/data/tedge/agent" to store tedge-agent state: No such file or directory (os error 2)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009002657Z  INFO sm-agent: tedge_agent::state_repository::state: Use "/etc/tedge/.agent/restart-current-operation" to store tedge-agent restart-current-operation state
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00900524Z DEBUG sm-agent: Runtime: schedule Spawn(RestartManagerActor)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009010032Z  WARN sm-agent: tedge_agent::state_repository::state: Cannot use "/data/tedge/agent" to store tedge-agent state: No such file or directory (os error 2)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.00901974Z  INFO sm-agent: tedge_agent::state_repository::state: Use "/etc/tedge/.agent/software-current-operation" to store tedge-agent software-current-operation state
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009023615Z DEBUG sm-agent: Runtime: schedule Spawn(SoftwareManagerActor)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009027699Z DEBUG sm-agent: Runtime: schedule Spawn(Script)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009068574Z  INFO Runtime: Running FsWatcher-2
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009077324Z  INFO Runtime: Running Downloader-3
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009101282Z  INFO Runtime: Running Uploader-4
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009128366Z  INFO Runtime: Running ConfigManager-5
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009200366Z  INFO Runtime: Running LogManager-6
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009209282Z  INFO Runtime: Running RestartManagerActor-7
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009203032Z  WARN sm-agent: tedge_agent::state_repository::state: Cannot use "/data/tedge/agent" to store tedge-agent state: No such file or directory (os error 2)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009266324Z  INFO tedge_config_manager::config: Using the configuration from /etc/tedge/plugins/tedge-configuration-plugin.toml
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009310866Z  INFO sm-agent: tedge_agent::state_repository::state: Use "/etc/tedge/.agent/workflows" to store tedge-agent workflows state
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009325032Z DEBUG sm-agent: Runtime: schedule Spawn(WorkflowActor)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009346574Z DEBUG sm-agent: Runtime: schedule Spawn(HealthMonitorActor)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009217574Z  INFO Runtime: Running SoftwareManagerActor-8
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009392324Z  INFO Runtime: Running Script-9
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009401491Z  INFO Runtime: Running WorkflowActor-10
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009417283Z  INFO Runtime: Running HealthMonitorActor-11
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009430908Z DEBUG device/child02/service/tedge-agent: send MqttMessage { topic: Topic { name: "te/device/child02/service/tedge-agent" }, payload: "{"@parent":"device/child02//","@type":"service","type":"service"}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009596325Z DEBUG device/child02/service/tedge-agent: send MqttMessage { topic: Topic { name: "te/device/child02/service/tedge-agent/status/health" }, payload: "{"pid":1490,"status":"up","time":1727906863.0095108}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009673408Z  INFO tedge_log_manager::actor: Reloading supported log types
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009685991Z  INFO log_manager::config: Using the configuration from /etc/tedge/plugins/tedge-log-plugin.toml
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009831783Z DEBUG Tedge-Config-Manager: send Metadata { topic: Topic { name: "te/device/child02///cmd/config_snapshot" }, types: ["modem", "system.toml", "tedge-configuration-plugin", "tedge.toml"] }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.0098862Z  INFO mqtt_channel::connection: MQTT connecting to broker: host=tedge:8883, session_name=Some("tedge-agent#te/device/child02//")
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.009898033Z DEBUG Tedge-Config-Manager: send Metadata { topic: Topic { name: "te/device/child02///cmd/config_update" }, types: ["modem", "system.toml", "tedge-configuration-plugin", "tedge.toml"] }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.010575368Z DEBUG tedge_config::tedge_config_cli::tedge_config_location: Loading configuration from "/etc/tedge/tedge.toml"
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.010725785Z DEBUG rustls::client::hs: No cached session for DnsName("tedge")
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.010784451Z DEBUG rustls::client::hs: Not resuming any session
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.010791326Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/device_profile" }, payload: "{}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.010819826Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/example" }, payload: "{}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.01082891Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/firmware_update" }, payload: "{}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.010832576Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/restart" }, payload: "{}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.011554036Z DEBUG Log Manager: send LogUploadCmdMetadata(LogUploadCmdMetadata { types: ["all-workflows", "firmware_update", "restart", "shell", "software-management"] })
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.01189062Z DEBUG rustls::client::hs: Using ciphersuite TLS13_AES_256_GCM_SHA384
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.011905703Z DEBUG rustls::client::tls13: Not resuming
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.011997703Z DEBUG rustls::client::tls13: TLS1.3 encrypted extensions: []
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.01201012Z DEBUG rustls::client::hs: ALPN protocol is None
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.012019828Z DEBUG rustls::client::tls13: Got CertificateRequest CertificateRequestPayloadTLS13 { context: , extensions: [SignatureAlgorithms([ECDSA_NISTP256_SHA256, ECDSA_NISTP384_SHA384, ECDSA_NISTP521_SHA512, ED25519, ED448, Unknown(2057), Unknown(2058), Unknown(2059), RSA_PSS_SHA256, RSA_PSS_SHA384, RSA_PSS_SHA512, RSA_PKCS1_SHA256, RSA_PKCS1_SHA384, RSA_PKCS1_SHA512, Unknown(771), Unknown(769)])] }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.01202662Z DEBUG rustls::client::common: Attempting client auth
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.01406679Z  INFO tedge_agent::operation_workflows::actor: Waiting failed example operation to be cleared
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.01408804Z DEBUG Mqtt-Request-Converter: recv Some(GenericCommandData(Metadata(GenericCommandMetadata { operation: "config_snapshot", payload: Object {"types": Array [String("modem"), String("system.toml"), String("tedge-configuration-plugin"), String("tedge.toml")]} })))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.01411029Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/config_snapshot" }, payload: "{"types":["modem","system.toml","tedge-configuration-plugin","tedge.toml"]}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.014122706Z DEBUG Mqtt-Request-Converter: recv Some(GenericCommandData(Metadata(GenericCommandMetadata { operation: "config_update", payload: Object {"types": Array [String("modem"), String("system.toml"), String("tedge-configuration-plugin"), String("tedge.toml")]} })))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.014133415Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/config_update" }, payload: "{"types":["modem","system.toml","tedge-configuration-plugin","tedge.toml"]}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.01413729Z DEBUG Mqtt-Request-Converter: recv Some(GenericCommandData(Metadata(GenericCommandMetadata { operation: "log_upload", payload: Object {"types": Array [String("all-workflows"), String("firmware_update"), String("restart"), String("shell"), String("software-management")]} })))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.014141915Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/log_upload" }, payload: "{"types":["all-workflows","firmware_update","restart","shell","software-management"]}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 sudo[1498]:    tedge : PWD=/ ; USER=root ; COMMAND=/etc/tedge/sm-plugins/container list
Oct 02 22:07:43 child02 sudo[1498]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=997)
Oct 02 22:07:43 child02 sudo[1498]: pam_unix(sudo:session): session closed for user root
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.037974451Z ERROR plugin_sm::plugin_manager: File /etc/tedge/sm-plugins/container in plugin directory does not support list operation and may not be a valid plugin, skipping.
Oct 02 22:07:43 child02 sudo[1512]:    tedge : PWD=/ ; USER=root ; COMMAND=/etc/tedge/sm-plugins/container-group list
Oct 02 22:07:43 child02 sudo[1512]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=997)
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.055639062Z  INFO mqtt_channel::connection: MQTT connection established
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.055669853Z DEBUG rumqttc::state: Subscribe. Topics = [Filter = te/device/child02///cmd/+/+, Qos = AtLeastOnce, Filter = te/device/child02/service/tedge-agent/cmd/health/check, Qos = AtLeastOnce], Pkid = 1
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056107146Z DEBUG MQTT pub: [te/device/child02/service/tedge-agent qos=1 retained] {"@parent":"device/child02//","@type":"service","type":"service"}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056195021Z DEBUG MQTT pub: [te/device/child02/service/tedge-agent/status/health qos=1 retained] {"pid":1490,"status":"up","time":1727906863.0095108}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056201646Z DEBUG MQTT pub: [te/device/child02///cmd/device_profile qos=1 retained] {}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056204563Z DEBUG MQTT pub: [te/device/child02///cmd/example qos=1 retained] {}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056206396Z DEBUG MQTT pub: [te/device/child02///cmd/firmware_update qos=1 retained] {}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056210729Z DEBUG MQTT pub: [te/device/child02///cmd/restart qos=1 retained] {}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056216604Z DEBUG MQTT pub: [te/device/child02///cmd/config_snapshot qos=1 retained] {"types":["modem","system.toml","tedge-configuration-plugin","tedge.toml"]}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056219063Z DEBUG MQTT pub: [te/device/child02///cmd/config_update qos=1 retained] {"types":["modem","system.toml","tedge-configuration-plugin","tedge.toml"]}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056220688Z DEBUG MQTT pub: [te/device/child02///cmd/log_upload qos=1 retained] {"types":["all-workflows","firmware_update","restart","shell","software-management"]}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056342188Z DEBUG rumqttc::state: Publish. Topic = te/device/child02/service/tedge-agent, Pkid = 2, Payload Size = 65
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056373396Z DEBUG rumqttc::state: Publish. Topic = te/device/child02/service/tedge-agent/status/health, Pkid = 3, Payload Size = 52
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056480438Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/device_profile, Pkid = 4, Payload Size = 2
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056496188Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/example, Pkid = 5, Payload Size = 2
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056506146Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/firmware_update, Pkid = 6, Payload Size = 2
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056520563Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/restart, Pkid = 7, Payload Size = 2
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056526188Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/config_snapshot, Pkid = 8, Payload Size = 75
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056531521Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/config_update, Pkid = 9, Payload Size = 75
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056536688Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/log_upload, Pkid = 10, Payload Size = 85
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.05657598Z DEBUG MQTT recv: [te/device/child02///cmd/example/local-1727906852 qos=1 retained] {"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","status":"executing"}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.056593438Z DEBUG Mqtt-Request-Converter: recv Some(MqttMessage(MqttMessage { topic: Topic { name: "te/device/child02///cmd/example/local-1727906852" }, payload: "{"logPath":"/var/log/tedge/agent/workflow-example-local-1727906852.log","status":"executing"}", qos: AtLeastOnce, retain: true }))
Oct 02 22:07:43 child02 sudo[1512]: pam_unix(sudo:session): session closed for user root
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.153181794Z ERROR plugin_sm::plugin_manager: File /etc/tedge/sm-plugins/container-group in plugin directory does not support list operation and may not be a valid plugin, skipping.
Oct 02 22:07:43 child02 sudo[1588]:    tedge : PWD=/ ; USER=root ; COMMAND=/etc/tedge/sm-plugins/apt list
Oct 02 22:07:43 child02 sudo[1588]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=997)
Oct 02 22:07:43 child02 sudo[1588]: pam_unix(sudo:session): session closed for user root
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.158951053Z  INFO plugin_sm::plugin_manager: Plugin activated: /etc/tedge/sm-plugins/apt
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.159024928Z  INFO plugin_sm::plugin_manager: Default plugin type: apt
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.161669266Z DEBUG SoftwareManager: send SoftwareCommandMetadata(SoftwareCommandMetadata { types: ["apt"] })
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.161714099Z DEBUG Mqtt-Request-Converter: recv Some(GenericCommandData(Metadata(GenericCommandMetadata { operation: "software_list", payload: Object {"types": Array [String("apt")]} })))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.161726557Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/software_list" }, payload: "{"types":["apt"]}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.161734724Z DEBUG Mqtt-Request-Converter: recv Some(GenericCommandData(Metadata(GenericCommandMetadata { operation: "software_update", payload: Object {"types": Array [String("apt")]} })))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.161738599Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/software_update" }, payload: "{"types":["apt"]}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.161744266Z DEBUG MQTT pub: [te/device/child02///cmd/software_list qos=1 retained] {"types":["apt"]}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.161746932Z DEBUG MQTT pub: [te/device/child02///cmd/software_update qos=1 retained] {"types":["apt"]}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.161762599Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/software_list, Pkid = 11, Payload Size = 17
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.161811599Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/software_update, Pkid = 12, Payload Size = 17
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.204384789Z DEBUG MQTT recv: [te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z qos=1] {"status":"init"}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.204428581Z DEBUG Mqtt-Request-Converter: recv Some(MqttMessage(MqttMessage { topic: Topic { name: "te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z" }, payload: "{"status":"init"}", qos: AtLeastOnce, retain: false }))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.208723463Z  INFO tedge_agent::operation_workflows::actor: Moving software_list operation to state: scheduled
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.211200675Z  INFO tedge_api::workflow::log::command_log: => moving to software_list @ scheduled
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.212069176Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z" }, payload: "{"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"scheduled"}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.212088384Z DEBUG Mqtt-Request-Converter: recv Some(InternalCommandState(InternalCommandState(GenericCommandState { topic: Topic { name: "te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z" }, status: "scheduled", payload: Object {"logPath": String("/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log"), "status": String("scheduled")}, invoking_command_topic: None })))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.212115884Z DEBUG MQTT pub: [te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z qos=1 retained] {"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"scheduled"}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.212135134Z DEBUG rumqttc::state: Publish. Topic = te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z, Pkid = 13, Payload Size = 124
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.212666635Z  INFO tedge_agent::operation_workflows::actor: Executing builtin:software_list operation scheduled step
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.213876345Z  INFO tedge_api::workflow::log::command_log: => moving to software_list @ executing
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.214488638Z DEBUG MqttPublisher: send MqttMessage { topic: Topic { name: "te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z" }, payload: "{"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"executing"}", qos: AtLeastOnce, retain: true }
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.214539513Z DEBUG Mqtt-Request-Converter: recv Some(InternalCommandState(InternalCommandState(GenericCommandState { topic: Topic { name: "te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z" }, status: "executing", payload: Object {"logPath": String("/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log"), "status": String("executing")}, invoking_command_topic: None })))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.214553846Z DEBUG MQTT pub: [te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z qos=1 retained] {"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"executing"}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.214562055Z DEBUG SoftwareManager: recv Some(SoftwareListCommand(Command { target: EntityTopicId("device/child02//"), cmd_id: "c8y-mapper-2024-10-02T22:07:43.162204766Z", payload: SoftwareListCommandPayload { status: Scheduled, current_software_list: [], log_path: Some("/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log") } }))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.214567971Z DEBUG rumqttc::state: Publish.  Topic = te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z, Pkid = 15, Payload Size = 3958
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.225113613Z  INFO tedge_agent::software_manager::actor: Installed binary version: 1.3.1~42+ga50bdcf
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.225318905Z DEBUG MQTT recv: [te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z qos=1] {"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"scheduled"}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.22547578Z DEBUG MQTT recv: [te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z qos=1] {"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"executing"}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.225487822Z DEBUG MQTT recv: [te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z qos=1] {"currentSoftwareList":[{"modules":[{"name":"adduser","version":"3.134"},{"name":"apt","version":"2.6.1"},{"name":"apt-transport-https","version":"2.6.1"},{"name":"base-files","version":"12.4+deb12u7"},{"name":"base-passwd","version":"3.6.1"},{"name":"bash","version":"5.2.15-2+b7"},{"name":"bsdutils","version":"1:2.38.1-5+deb12u1"},{"name":"c8y-command-plugin","version":"0.0.2"},{"name":"ca-certificates","version":"20230311"},{"name":"coreutils","version":"9.1-1"},{"name":"curl","version":"7.88.1-10+deb12u7"},{"name":"dash","version":"0.5.12-2"},{"name":"debconf","version":"1.5.82"},{"name":"debian-archive-keyring","version":"2023.3+deb12u1"},{"name":"debianutils","version":"5.7-0.5~deb12u1"},{"name":"diffutils","version":"1:3.8-4"},{"name":"dirmngr","version":"2.2.40-1.1"},{"name":"dmsetup","version":"2:1.02.185-2"},{"name":"docker-ce-cli","version":"5:27.3.1-1~debian.12~bookworm"},{"name":"docker-compose-plugin","version":"2.29.7-1~debian.12~bookworm"},{"name":"dpkg","version":"1.21.22"},{"name":"e2fsprogs","version":"1.47.0-2"},{"name":"findutils","version":"4.9.0-4"},{"name":"gcc-12-base","version":"12.2.0-14"},{"name":"gnupg","version":"2.2.40-1.1"},{"name":"gnupg-l10n","version":"2.2.40-1.1"},{"name":"gnupg-utils","version":"2.2.40-1.1"},{"name":"gnupg2","version":"2.2.40-1.1"},{"name":"gpg","version":"2.2.40-1.1"},{"name":"gpg-agent","version":"2.2.40-1.1"},{"name":"gpg-wks-client","version":"2.2.40-1.1"},{"name":"gpg-wks-server","version":"2.2.40-1.1"},{"name":"gpgconf","version":"2.2.40-1.1"},{"name":"gpgsm","version":"2.2.40-1.1"},{"name":"gpgv","version":"2.2.40-1.1"},{"name":"grep","version":"3.8-5"},{"name":"gzip","version":"1.12-1"},{"name":"hostname","version":"3.23+nmu1"},{"name":"init-system-helpers","version":"1.65.2"},{"name":"login","version":"1:4.13+dfsg1-1+b1"},{"name":"logsave","version":"1.47.0-2"},{"name":"mawk","version":"<IP_ADDRESS>00120-3.1"},{"name":"mosquitto","version":"2.0.11-1.2+deb12u1"},{"name":"mount","version":"2.38.1-5+deb12u1"},{"name":"ncurses-base","version":"6.4-4"},{"name":"ncurses-bin","version":"6.4-4"},{"name":"openssh-client","version":"1:9.2p1-2+deb12u3"},{"name":"openssh-server","version":"1:9.2p1-2+deb12u3"},{"name":"openssh-sftp-server","version":"1:9.2p1-2+deb12u3"},{"name":"openssl","version":"3.0.14-1~deb12u2"},{"name":"passwd","version":"1:4.13+dfsg1-1+b1"},{"name":"perl-base","version":"5.36.0-7+deb12u1"},{"name":"pinentry-curses","version":"1.2.1-1"},{"name":"procps","version":"2:4.0.2-3"},{"name":"readline-common","version":"8.2-1.3"},{"name":"runit-helper","version":"2.15.2"},{"name":"sed","version":"4.9-1"},{"name":"sensible-utils","version":"0.0.17+nmu1"},{"name":"ssh","version":"1:9.2p1-2+deb12u3"},{"name":"step-ca","version":"0.27.4"},{"name":"step-cli","version":"0.27.4-1"},{"name":"sudo","version":"1.9.13p3-1+deb12u1"},{"name":"systemd","version":"252.30-1~deb12u2"},{"name":"systemd-sysv","version":"252.30-1~deb12u2"},{"name":"sysvinit-utils","version":"3.06-4"},{"name":"tar","version":"1.34+dfsg-1.2+deb12u1"},{"name":"tedge","version":"1.3.1~42+ga50bdcf"},{"name":"tedge-agent","version":"1.3.1~42+ga50bdcf"},{"name":"tedge-apt-plugin","version":"1.3.1~42+ga50bdcf"},{"name":"tedge-container-plugin","version":"1.3.1"},{"name":"tedge-inventory-plugin","version":"0.0.3"},{"name":"tedge-pki-smallstep-ca","version":"0.0.22"},{"name":"tedge-pki-smallstep-client","version":"0.0.22"},{"name":"tzdata","version":"2024a-0+deb12u1"},{"name":"ucf","version":"3.0043+nmu1"},{"name":"usr-is-merged","version":"37~deb12u1"},{"name":"util-linux","version":"2.38.1-5+deb12u1"},{"name":"util-linux-extra","version":"2.38.1-5+deb12u1"},{"name":"vim-common","version":"2:9.0.1378-2"},{"name":"vim-tiny","version":"2:9.0.1378-2"},{"name":"wget","version":"1.21.3-1+b1"},{"name":"zlib1g","version":"1:1.2.13.dfsg-1"}],"type":"apt"}],"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"successful"}
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.226088239Z  INFO tedge_agent::operation_workflows::actor: Waiting successful software_list operation to be cleared
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.226125739Z DEBUG Mqtt-Request-Converter: recv Some(MqttMessage(MqttMessage { topic: Topic { name: "te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z" }, payload: "{"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"scheduled"}", qos: AtLeastOnce, retain: false }))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.226139948Z DEBUG Mqtt-Request-Converter: recv Some(MqttMessage(MqttMessage { topic: Topic { name: "te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z" }, payload: "{"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"executing"}", qos: AtLeastOnce, retain: false }))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.226147448Z DEBUG Mqtt-Request-Converter: recv Some(MqttMessage(MqttMessage { topic: Topic { name: "te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z" }, payload: "{"currentSoftwareList":[{"modules":[{"name":"adduser","version":"3.134"},{"name":"apt","version":"2.6.1"},{"name":"apt-transport-https","version":"2.6.1"},{"name":"base-files","version":"12.4+deb12u7"},{"name":"base-passwd","version":"3.6.1"},{"name":"bash","version":"5.2.15-2+b7"},{"name":"bsdutils","version":"1:2.38.1-5+deb12u1"},{"name":"c8y-command-plugin","version":"0.0.2"},{"name":"ca-certificates","version":"20230311"},{"name":"coreutils","version":"9.1-1"},{"name":"curl","version":"7.88.1-10+deb12u7"},{"name":"dash","version":"0.5.12-2"},{"name":"debconf","version":"1.5.82"},{"name":"debian-archive-keyring","version":"2023.3+deb12u1"},{"name":"debianutils","version":"5.7-0.5~deb12u1"},{"name":"diffutils","version":"1:3.8-4"},{"name":"dirmngr","version":"2.2.40-1.1"},{"name":"dmsetup","version":"2:1.02.185-2"},{"name":"docker-ce-cli","version":"5:27.3.1-1~debian.12~bookworm"},{"name":"docker-compose-plugin","version":"2.29.7-1~debian.12~bookworm"},{"name":"dpkg","version":"1.21.22"},{"name":"e2fsprogs","version":"1.47.0-2"},{"name":"findutils","version":"4.9.0-4"},{"name":"gcc-12-base","version":"12.2.0-14"},{"name":"gnupg","version":"2.2.40-1.1"},{"name":"gnupg-l10n","version":"2.2.40-1.1"},{"name":"gnupg-utils","version":"2.2.40-1.1"},{"name":"gnupg2","version":"2.2.40-1.1"},{"name":"gpg","version":"2.2.40-1.1"},{"name":"gpg-agent","version":"2.2.40-1.1"},{"name":"gpg-wks-client","version":"2.2.40-1.1"},{"name":"gpg-wks-server","version":"2.2.40-1.1"},{"name":"gpgconf","version":"2.2.40-1.1"},{"name":"gpgsm","version":"2.2.40-1.1"},{"name":"gpgv","version":"2.2.40-1.1"},{"name":"grep","version":"3.8-5"},{"name":"gzip","version":"1.12-1"},{"name":"hostname","version":"3.23+nmu1"},{"name":"init-system-helpers","version":"1.65.2"},{"name":"login","version":"1:4.13+dfsg1-1+b1"},{"name":"logsave","version":"1.47.0-2"},{"name":"mawk","version":"<IP_ADDRESS>00120-3.1"},{"name":"mosquitto","version":"2.0.11-1.2+deb12u1"},{"name":"mount","version":"2.38.1-5+deb12u1"},{"name":"ncurses-base","version":"6.4-4"},{"name":"ncurses-bin","version":"6.4-4"},{"name":"openssh-client","version":"1:9.2p1-2+deb12u3"},{"name":"openssh-server","version":"1:9.2p1-2+deb12u3"},{"name":"openssh-sftp-server","version":"1:9.2p1-2+deb12u3"},{"name":"openssl","version":"3.0.14-1~deb12u2"},{"name":"passwd","version":"1:4.13+dfsg1-1+b1"},{"name":"perl-base","version":"5.36.0-7+deb12u1"},{"name":"pinentry-curses","version":"1.2.1-1"},{"name":"procps","version":"2:4.0.2-3"},{"name":"readline-common","version":"8.2-1.3"},{"name":"runit-helper","version":"2.15.2"},{"name":"sed","version":"4.9-1"},{"name":"sensible-utils","version":"0.0.17+nmu1"},{"name":"ssh","version":"1:9.2p1-2+deb12u3"},{"name":"step-ca","version":"0.27.4"},{"name":"step-cli","version":"0.27.4-1"},{"name":"sudo","version":"1.9.13p3-1+deb12u1"},{"name":"systemd","version":"252.30-1~deb12u2"},{"name":"systemd-sysv","version":"252.30-1~deb12u2"},{"name":"sysvinit-utils","version":"3.06-4"},{"name":"tar","version":"1.34+dfsg-1.2+deb12u1"},{"name":"tedge","version":"1.3.1~42+ga50bdcf"},{"name":"tedge-agent","version":"1.3.1~42+ga50bdcf"},{"name":"tedge-apt-plugin","version":"1.3.1~42+ga50bdcf"},{"name":"tedge-container-plugin","version":"1.3.1"},{"name":"tedge-inventory-plugin","version":"0.0.3"},{"name":"tedge-pki-smallstep-ca","version":"0.0.22"},{"name":"tedge-pki-smallstep-client","version":"0.0.22"},{"name":"tzdata","version":"2024a-0+deb12u1"},{"name":"ucf","version":"3.0043+nmu1"},{"name":"usr-is-merged","version":"37~deb12u1"},{"name":"util-linux","version":"2.38.1-5+deb12u1"},{"name":"util-linux-extra","version":"2.38.1-5+deb12u1"},{"name":"vim-common","version":"2:9.0.1378-2"},{"name":"vim-tiny","version":"2:9.0.1378-2"},{"name":"wget","version":"1.21.3-1+b1"},{"name":"zlib1g","version":"1:1.2.13.dfsg-1"}],"type":"apt"}],"logPath":"/var/log/tedge/agent/workflow-software_list-c8y-mapper-2024-10-02T22:07:43.162204766Z.log","status":"successful"}", qos: AtLeastOnce, retain: false }))
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.350662055Z DEBUG MQTT recv: [te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z qos=1]
Oct 02 22:07:43 child02 tedge-agent[1490]: 2024-10-02T22:07:43.350703846Z DEBUG Mqtt-Request-Converter: recv Some(MqttMessage(MqttMessage { topic: Topic { name: "te/device/child02///cmd/software_list/c8y-mapper-2024-10-02T22:07:43.162204766Z" }, payload: "", qos: AtLeastOnce, retain: false }))

Resolved. The operation is now set to failed. Below shows an example of the command's topic and the status is set to failed.
[te/device/main///cmd/example/local-1733383389] {"@version":"b130cc7ebd8e74920774818a4dcfb9a0a954f6cac54733892d7d3e499337ff47","logPath":"/var/log/tedge/agent/workflow-example-local-1733383389.log","reason":"sleep killed by signal 15","resumed_at":"1733383399.0","status":"failed"}


Add API support to mouse events in editor

Hi, I've started to write an extension to provide support for W3C XLink Specification to the xml language the xlink specification provides attributes to document links from an XML fragment o another XML fragment.
At the time I find an xlink:href attribute on an XML node I'm able to create a customized decoration on the attribute value but I'm unable to find the way to properly implement a mechanism to detect when the user has clicked on the decoration. I've actually implemented a DefinitionProvider that is able to open the document but the user must press F12 or right click on the text and select "Go to Definition" but a link is not a Definition but just the link end point.
Cheers,
Ignacio

@alexandrudima ping

@jrieken How do you think we should better handle this?
Should we expose ILinkSupport in the api and accumulate & dedup the links from all parties? Or should DefinitionProvider be expanded in scope to capture any link?

@IgnacioHR Are the documents those links point to usually inside the workspace or something like a http-url that you want to be opened in a browser?

Links points anywhere. They are just links. The URI is resolved using xml:base standard resolution and the target file might be local or external. When local, I open it on a side editor and I find the target element so it is highlighted.

Thanks. I think the best will be expose the ILinkSupport in some form. VS Code (as today) will come with a decent default implementation but for special cases (like above) you can mark for regions of a document as hyperlink.

Sounds good to me. Thanks

[ ] add registerDocumentLinkProvider API
[ ] add corresponding command
[ ] update sample


Binary difference? How should I build?

Hi there Jauderho,
First I'd like to say I appreciate your efforts in keeping the Dive image up to date with dependencies
I have no experience with Go, so please tell me if I my process is wrong.
I am using an Intel MacBook Pro (AMD64)
go build -o jauderho
docker create --name jauderho jauderho/dive
docker cp jauderho:/usr/local/bin/dive jauderho-dh
cmp -l jauderho jauderho-dh

The binary comparison found many differences, and so I wonder if something in my build process is not agnostic, and how to achieve a binary identical to the one you compiled
Thank you :)

If you are looking for a docker image, these are already built out of my dockerfiles repo. The Dockerfile in this repo is from upstream and I do not actively update it.
Here's what I personally use: https://github.com/jauderho/dockerfiles/pkgs/container/dive

Not necessarily, I already am using your image
I made a small workaround to one of the errors Dive is currently experiencing, failing to locate blobs when using the containers image registry instead of the regular one
My image is based on docker:latest and copies the Dive binary into it
This allows you to run Dive using the normal image store without compromising the abilities using the containerd image store provides
deanayalon/dive-dind:jauderho features your binary:
COPY --from=jauderho/dive /usr/local/bin/dive /usr/local/bin/

For the sake of security, with how you never know what's in binaries, I tried compiling the code in your repository into a binary, which I then compared with the binary within your docker image
They do not match, and so, is something in my build process not agnostic, how do you build the binary from your source code?

these are already built out of my dockerfiles repo

Ohh, sorry, should've taken a better look at the dockerfile you linked, it actually has the build process within it, awesome :)

Another question, unrelated but undeserving of its own issue
Forking Dive, one of my branches was tracking your main.
I accidentally pushed it, and the commits within ended up referencing a few of wagoodman's open issues, which got a tad spammy (DeanAyalon mentioned this issue in commit xxxxxx)
I was wondering how you made those commits without them appearing within wagoodman's repository


bug: ESM named export identifier conflict

This kind of code:
var publicAPI = {
   something
};

module.exports.something = publicAPI.something;

function something() {}

...is transpiled to ESM format as:
var publicAPI = {
   something
};

export let {
   something   // <---- conflict
} = publicAPI;

function something() {}   // <---- conflict

The alternative named export form would have been:
let _exp1234 = publicAPI.something;
export { _exp1234 as something };

Need to check for this name conflict and use this alternate form if necessary.

References:

https://github.com/getify/moduloze/blob/0ceb03a54223207c8d2a0611cb6caedb59e322f8/src/esm.js#L424-L477

https://github.com/getify/moduloze/blob/master/src/analysis.js#L643-L665

So, if I understand it correctly, the esm.js already can handle both types of conversions.
But the analysis.js file is only using the "destructured-declaration-export".
A possible solution would be to add some code for checking the conflict and using the "named-declaration-export" bit ?

@vipulbhj I believe that's the case, yes. I hope that's all it is.

Will try to look into it. Thanks 😁


running elegant sim in radtrack with embedded file links does not work

When running elegant in Radtrack, the file links (e.g. WAKE) that are hard coded in the LTE file cause a fatal error.
This happens because the file links are referenced using a subdirectory (i.e. "directory/filename.sdds") but radtrack collapses the file tree structure and can not find these files.

This issue should be fixed. Please test.


No output file after attempted conversions

(Based on prior email discussion, migrated to this issue)
I am looking to convert a 研究社 Yomichan dictionary for potential use with my Kobo. However, I've run into some difficulties.

cargo run kobo_jp_dict -y 研究社　新和英大辞典　第５版.zip dicthtml-ja-en.zip

On running this command in Cygwin, I am met with the following error:

cargo run kobo_jp_dict -y 研究社　新和英大辞典　第５版.zip

On running this command, I am met with:

Unlike with the first command, which I based on the example in the readme, this one seems to work(?) in that the program appears to spend roughly 3 minutes doing something—however, at the end of the process, there doesn't seem to be an output file anywhere.
By sorting files by Date Modified in Everything, I'm able to see files such as MARISA-BUILD.EXE-908E7366.pf and KOBO_JP_DICT.EXE-CF27C84A.pf appearing/being accessed while the command is running, which implies to me that the program itself and Marisa are functioning throughout. Whether or not as intended, I'm not sure.
Attempts at troubleshooting so far:

Putting quote marks around 研究社　新和英大辞典　第５版.zip — Yields the same result, that is, no output file
Trying the process with jmdict_english.zip instead — Same result, no output file

For reference, here are what my file paths look like, in case that might help:

(Sorry for the image wall, not sure what will and won't be useful.)
Any and all guidance would be appreciated. Thank you for your time.

Thanks so much for reporting this!  As I mentioned over email, I'm rather busy right now.  But I'll get to this as soon as I reasonably can (which might be a bit).


Create camel-gps-bu353 component

I'd like to have Camel component to read GPS coordinates from by BU353 [1] USB device.
[1] http://blog.retep.org/2012/06/18/getting-gps-to-work-on-a-raspberry-pi/

Done.


Plotly renderer config support

Describe the bug
I want to set plotly defaults. In Jupyter I normally use scrollZoom and editable plots by default.
But in Marimo it seems that plotly plots neither have scrollZoom nor are they editable. Are either possible? Do I need to choose a different 'renderer'? Wrapping in a mo.ui.plotly doesn't change the behavior.
Environment
{
"marimo": "0.2.5",
"OS": "Linux",
"OS Version": "6.2.0-1019-gcp",
"Processor": "x86_64",
"Python Version": "3.10.12",
"Binaries": {
"Chrome": "--",
"Node": "--"
},
"Requirements": {
"black": "21.7b0",
"click": "8.0.2",
"jedi": "0.19.0",
"pymdown-extensions": "9.11",
"starlette": "0.37.1",
"tomlkit": "0.12.1",
"typing_extensions": "4.5.0",
"uvicorn": "0.27.1"
}
}
Code to reproduce
import marimo as mo
import numpy as np
import plotly.express as px
import plotly.io as pio

pio.renderers.default = "notebook"
pio.renderers["notebook"].config["scrollZoom"] = True
pio.renderers["notebook"].config["editable"] = True
fig = px.scatter(np.random.rand(5))
# mo.ui.plotly(fig)  # this didn't help
fig

@jamieray , thanks for opening this issue. We haven't really looked into default Plotly rendering options. How important is it to you that we support this?

I'll still have some use for Marimo without editable, but I use scrollZoom on almost every plot because I don't know what axis limits will be useful a priori. So I would end up using Jupyter for much of my plotting if it's not available in marimo. I can look into other plotting options but thought I would check if I was doing something wrong here.

So I would end up using Jupyter for much of my plotting if it's not available in marimo. I can look into other plotting options but thought I would check if I was doing something wrong here.

Thanks for letting us know. In that case, we can look into supporting this

Not sure if it's related but plotly usually default to the tool being zoom (drag a rectangle to zoom) but in Marimo it is default to select. (drag a rectangle and select some points, useful for a callback or getting the data, less helpful for data exploration.)

@jamieray , @astrowonk  This will be fixed in the next release (https://github.com/marimo-team/marimo/pull/1170)
You can pass config or a renderer name to the plugin. We still have the default tool being "selection", just we want people to use the marimo reactivity, but happy to change it if people feel strongly.

I would prefer zoom be the default, but as long as there's a way to change the default I am ok with whatever you want to do. I can see how it makes sense for reactivity demonstration purposes for selection to be default.


Adds acts_as_taggable_on

Switches from the array column based acts_as_taggable_array_on gem to the join-table based acts_as_taggable_on.
When we discussed this some days ago, we'd floated the idea of configuring the gem to point at our categories table. I got that to work now that i better understand how the library works, i'm leaning towards sticking with their default tags and taggings tables.
We'd still keep the categories table. That would be the authoritative source of 'available' tags, configurable by system admins. The tag tables would be used exclusively by the gem to track which categories get tagged.
I think that sets us up to support user-provided tags that don't pollute the admin-managed categories table, and avoids any potential collisions between our own migrations and the gem's.
LMK your thoughts on that @maebeale .
I tried to refactor anything that looked to be using tags but i'm not confident that i knew what to test 🙈 .

YAYYYY!!!!! Yup, this was my original imagined structure, so all green lights from me! :)

No worries on testing! Yeah, some of it I've just hard-coded until we had a solid strategy for storing and accessing them.


Use a config file for loading files and commands

I'm not 100% sure this is what we want, but it's looking a little funky the way we have it now. After #27, we'll be initializing File objects, and then later setting their Source parameter. I'd be nicer if we were generating those File objects from a stored list elsewhere, either as a go list of strings in the same file or an external list grabbed from a config file.

Implemented in #29


gccemacs update - solving "emacs-version-changed"

On my Arch Linux machine, I use an "emacs native compilation branch" package (from the archlinuxcn repository), and I recently switched to straight.el for package management ("develop" branch). Every time my emacs package gets updated, straight.el bails out with 'emacs-version-changed'. This, I found out to be caused by natively compiled files left over from the before-the-update emacs binary, in the "~/.emacs.d/eln-cache" folder (see 'comp-eln-load-path' variable doc). So, I fixed it using a slightly changed version of the bootstrap sequence recommended on straight.el homepage, as follows, to delete that folder (the bottom part):

(setq load-prefer-newer t)
(setq straight-repository-branch "develop"
      straight-vc-git-default-clone-depth 1)

;;; package manager bootstrap
(defvar bootstrap-version)
(let ((bootstrap-file
       (expand-file-name "straight/repos/straight.el/bootstrap.el" user-emacs-directory))
      (bootstrap-version 5))
  (unless (file-exists-p bootstrap-file)
    (with-current-buffer
        (url-retrieve-synchronously
         "https://raw.githubusercontent.com/raxod502/straight.el/develop/install.el"
         'silent 'inhibit-cookies)
      (goto-char (point-max))
      (eval-print-last-sexp)))
  ;; catch emacs updates that have native compiled leftovers
  (unless (catch 'emacs-version-changed
	    (load bootstrap-file nil 'nomessage))
    (when (boundp 'comp-eln-load-path)
      ;; remove leftovers, with confirmation just to be safe
      (when (yes-or-no-p (format "Delete '%s'?" (car comp-eln-load-path)))
	(delete-directory (expand-file-name (car comp-eln-load-path)) t))
      ;; and try again
      (load bootstrap-file nil 'nomessage))))

Now (finally!) the question: is that the solution? In other words, who's responsible for dealing with that error: a) should straight.el not check for that mismatch, b) is it ok if I do it there, or c) should the package installer remove that folder for me (but, since it's customizable from my init.el, how could it know what folder to delete, in this case)?
I know 'straight.el' is actually checking for compiled files mismatch, but the native compilation is adding an extra layer of 'compiled' in the mix.

I'm not suggesting the above code is the solution, since I believe straight.el is checking for any type of compiled file leftovers (not only the native ones). Maybe there is a way to check specifically for native compiled files leftovers (and in that case delete the eln-cache)?

Thank you for bringing this to our attention.
I'm not currently using the native-comp branch, but what you're running into makes sense.
If the eln file is preferred over the elc, then it could become stale after upgrading Emacs.
@flatwhatson: Have you run into any similar scenarios? Does this solution look reasonable to you?
As far as prompting whether or not to remove the eln files, I think that's safe to skip.
If the Emacs version has changed, you generally want to re-compile all elc/eln files, as the upgrade may have introduced incompatibilities.

If I'm understanding the issue here, the correct solution is most likely to adjust the code in bootstrap.el that does some manual management of the file straight.elc, so that it also takes into account the possible existence of straight.eln.

Removing waiting on response because it seems there definitely is a problem that needs to be solved.

Sorry, I haven't encountered this error because I use straight via Doom Emacs which bypasses that check in bootstrap.el.
I think that extending the existing bootstrap logic for stale elc to also handle rebuilding the eln makes sense.
I'm not sure whether straight should enforce or even encourage deletion of the eln cache directory, even though this is currently common practice.  The native-compilation feature has its own logic for managing outdated eln files which should also handle version upgrades, it's just that each new commit on the feature/native-comp branch doesn't constitute a "version upgrade".

Same here.
I am using feature/native-comp branch. and after git fetch and compiling. I get No catch for tag: emacs-version-changed, nil.
Instead of modifying bootstrap.el, I rush to delete eln-cache directory. Solved.

It seems to me like updating to a new commit on feature/native-comp should result in the compiled files being rebuilt. What if there was a bug in the previous version of feature/native-comp that has been fixed, for example? If feature/native-comp has its own logic for managing outdated compiled files, as @flatwhatson mentions, but straight.el wants to be more granular about when the cache is cleared, it seems reasonable to take care of that on the straight.el side.
I think, in bootstrap.el, all we would have to do is update the (when emacs-version-changed ...) clause to also delete anything related to .eln files.

Updated https://github.com/raxod502/straight.el/issues/697 which can be merged into this, I think

#729 should fix this.


Connection overflow in central scheduler history

Hi,
We use luigi central scheduler with history on PostgreSQL.
When we running task after a few minutes the  central scheduler fall because connection overflow.
sqlalchemy.exc.TimeoutError: QueuePool limit of size 5 overflow 10 reached, connection time out. timeout 30
We are using luigi 2.7.1
Do you have any suggestion how to overcome those problems ?
Thanks,
Ron.

See http://docs.sqlalchemy.org/en/latest/errors.html#error-3o7r. There would need to be a way to specify additional parameters into the create_engine call at https://github.com/spotify/luigi/blob/1b2f0fd800b3b02a230d3613273f796fbc469c11/luigi/db_task_history.py#L82.


Remove version property from the localization google docs and update the script accordingly

Localization files: https://drive.google.com/drive/folders/1QDCwxmTWZ8-9nLUg_b0M47UYaHXFR3n0

Done. Also, updated the scripts to show missing properties at the top, though the way it does it is a bit opaque, but necessary to avoid having to parse the document completely. Someday we may write up an attempt at a clear description...


Added new known limitation

see:
https://github.com/cockroachdb/cockroach/issues/39117
https://cockroachdb.zendesk.com/agent/tickets/3517
Users can encounter this any time they have a large # of ranges (>500GiB per node), and cold start. I think it's worth documenting given that it can make an entire cluster unavailable until these steps are taken.
@bdarnell please ensure I didn't say anything inaccurate and @jseldess let me know if you think there's a better place for these :)

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/75259965ea2613456ba661e234d2ca0d6c8ddbb1/
Edited pages:

v19.1/known-limitations.md
v2.1/known-limitations.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3b3be5e1c59409d241590c76a4b51d1a37a61fe4/
Edited pages:

v19.1/known-limitations.md
v2.1/known-limitations.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/95a639314e2a160165a6be35f9e54b9bdfa2b084/
Edited pages:

v19.1/known-limitations.md
v19.2/known-limitations.md
v2.1/known-limitations.md