Is there a metric available in the DC CloudWatch dashboard that gives an indication of the wall-clock latency between a database being advanced to a basis-t on the transactor and that same database being on other nodes either in the PCG or a QG?
IOW, what is the scale of "eventually" in "eventually consistent"?
Per the https://docs.datomic.com/transactions/acid.html#implications : > Datomic provides strong consistency of the entire database I know what you're asking for, and no, there are no metrics for propagation delay of consistent database values.
Thanks, Joe. I was not sure how to interpret some of the metrics on the built-in dashboard and was hoping maybe there was something in there to give me a rough feel. But it was a long shot since most of the interesting candidates were only visible on the PCG and the metric I'm looking for would be on all nodes.
Hey folks, using datomic cloud ions, I am having this on a security scanner:
Package / Version to update
org.clojure:clojure / 1.12.0-alpha9 or latest
An issue in Clojure versions 1.20 to 1.12.0-alpha5 allows an attacker to cause a denial of service (DoS) via the clojure.core$partial$fn__5920 function.==================================================Lambda:
service--CreateCodeDeployDeployme-LcspR0Jg6Ab1
service-com-UpdateLambdaFromArray-BnmZ2Yx4OGQV
service-compu-GetDeploymentStatus-6GCDxubQ6kk6Vulnerability: CWE-117 - Log injection
Severity: High
Location: index.jsthe CVE in question relates to using Java serialization to deserialize object graphs from untrusted sources (where a maliciously crafted object graph could be deserialized). If you don't do that, you are unaffected.
ok yeah makes sense
I'm assuming this is https://nvd.nist.gov/vuln/detail/CVE-2024-22871 which was closed in Clojure 1.11.3 and 1.12.0
datomic cloud can be updated to clojure 1.11.3 or 1.12.1?
Datomic Cloud is already running 1.11.4 IIRC
should I be worried about it?