We have it as a data analyst that’s been trained via exemplar queries and MD about the underlying databases.
It also does ad creatives analysis and overall paid marketing spend analysis, including delivering briefs and conversing with stakeholders about things such as cross-ad-platform deduplicated cost of customer acquisition.
In general it is used to lower the technical bar required for cross-domain collab.
In this case the CPU wasn’t really saturated with work but with contention on global locks. The contention is lessened by removing the amount of concurrent mounts that are being done.
I wonder if simply setting a maximum number of concurrent mounts in the code or by letting containerd think there are only half the amount of cores, would have solved the contention to the same amount.
Even in a product as technically wonderful as Temporal, we can have relatively simple oversights like this that lead to cross tenant leakage.
If anyone is more familiar with Temporal, is there a way clients could have had internal defense in depth that guards against tenant leakage at the provider (Temporal) level?
As someone who doesn't keep track of the influencer scene at the moment because I am way addicted to building...
You should totally give Claude Code a try. The biggest problem is that it is glaze-optimized, so have to work at getting it to not treat you like the biggest genius of all time. But when you manage to get in a good flow with it, and your project is very predictably searchable, results start to be quite helpful, even if just to unstuck yourself when you're in a rut.
This. Claude Code was the only one to be able to grok my 20 year old C++ codebase so that I could update things deep in it's bowels to make it compile because I neglected it on a thumb drive for 15 years. I had no mental model of what was going on. Claude built one in a few minutes.
I will try it. I did use Cursor agents beforehand (using Sonnet/Opus 4), and my problems were that it was slower than I was (meaning me prompting AI), and was not good enough to leave it unattended.
This isn't the first time their plugin has led to RCE...