Please, in the name of #idempotence
On a particular #rockylinux machine (others seem fine), #saltstack has trouble enabling a service:
"The named service systemd-timesyncd is not available"
Trouble is: after I typed "systemctl enable systemd-timesyncd", the salt state (service.enabled) works forever (re-enabling ok). If I mask the service, the error is different.
Could it be an implicit "daemon-reload" when typing or something fishy like this?
#idempotence #RockyLinux #saltstack #linux #question
Please, in the name of #idempotence
On a particular #rockylinux machine (others seem fine), #saltstack has trouble enabling a service:
"The named service systemd-timesyncd is not available"
Trouble is: after I typed "systemctl enable systemd-timesyncd", the salt state (service.enabled) works forever (re-enabling ok). If I mask the service, the error is different.
Could it be an implicit "daemon-reload" when typing or something fishy like this?
#idempotence #RockyLinux #saltstack #linux #question
#Mastodon needs an #idempotence marker for toots.
Just had a Publish timeout, so I naturally retried.
Et voila: duplicate toots.
I'm kinda disappointed a network-failure-aware system doesn't already have this. Or maybe it does and the mastodon app doesn't use it?
(This one just timed out too. Will I get a dupe?)
x 3
Can there not be some kind of async callback after a timeout to check if the operation succeeded after all?
#Mastodon needs an #idempotence marker for toots.
Just had a Publish timeout, so I naturally retried.
Et voila: duplicate toots.
I'm kinda disappointed a network-failure-aware system doesn't already have this. Or maybe it does and the mastodon app doesn't use it?
(This one just timed out too. Will I get a dupe?)
#Mastodon needs an #idempotence marker for toots.
Just had a Publish timeout, so I naturally retried.
Et voila: duplicate toots.
I'm kinda disappointed a network-failure-aware system doesn't already have this. Or maybe it does and the mastodon app doesn't use it?