#random (2023-06)
Non-work banter and water cooler conversation
A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you’d prefer to keep out of more focused work-related channels.
Archive: https://archive.sweetops.com/random/
2023-06-05
Just wanted to share (related to Karpenter):
I’ve been highly anticipating the 0.28.0 release of Karpenter —the one which has a huge internal refactor on how to handle edge cases for nodes not registering properly. When to terminate unregistered nodes, etc. This release has been taking several months —evidently because of such a huge refactor— and the Karpenter maintainers have cut several release candidates for it. The last time they even had to cut release candidates was back in 0.14.0.
But I found out that v0.27.3 has seemingly backported from the 0.28.0 release candidates some very important fixes for handling node lifecycle. For example handling nodes that no longer exist in the cloud provider (i.e. EC2 instances that are already terminated) but the k8s API cannot delete the node object, e.g. pods stuck in terminating because of PDBs, do-not-evict annotations, etc.
So if you’re not already on the latest 0.27.x release, I highly recommend the upgrade.
@Jonathan Eunice
@Steven Miller
2023-06-06
2023-06-07
Anyone here use any automated PR review bots that catch common errors? Do you like it or hate it? I imagine this trend is on the rise and I’m interested to hear if folks have found anything they like and would recommend.
commenting to subscribe to this thread!
I think different behaviors based on PR type are important too. For example, if it’s a software patch, I’d love a CVE lookup for supply chain attack. Maybe even a compatibility review through static analysis if we want to get fancy!
For feature PRs, I’d love to see code smell checks, style and architecture consistency, test coverage, etc.
Yeah that’s exactly the type of thing I’m looking for.
Trivy can supply the CVE lookup stuff. I should work that into our standard CI…
Test coverage can be useful as a heuristic but I find it meaningless as a gate
Or actively damaging as a gate
When it comes to PRs, I think having machines blocking the merge button are inherently bad practice. We want the machines to inform the decision, not choose for the reviewer.
There is a special case where we might choose to have the machine automatically apply patches, but this is a case of machines approving machine generated pull requests, not human ones.
Every time I see a mandatory x% code coverage check, it always leads to a lot of “does not throw an unhandled exception” useless tests.
Also when you’re refactoring some component which results in a certain utility function etc not being utilised anymore, your coverage drops since that function/class isn’t being used by anything. So then you’ve got to take up the responsibility of writing a unit test for something you don’t even need.
If contributors aren’t incentivised to write meaningless tests, then the coverage reports have the potential to be used as reliable metrics to see the cause & effect of tests and refactors.
In unexpected news: HashiCorp laid off ~8% of their workforce today
The economy will be really bad
2023-06-08
2023-06-17
2023-06-18
2023-06-20
is that answer from bing?
That’s the Google result
Let’s see what the Bing result is
Perfect
lovely =))
In relation to Celery queues, do the terms/metrics: “low length” and “max length”, meany anything? They either aren’t a real thing or they aren’t in the docs that I can find. Queue Depth is what I would expect the terminology to be…
Hey Folks,
I’m thrilled to share our journey towards Continuous Security Audits at Dgraph Labs Inc. In our blog post, we delve into how we detect and remediate potential Security Issues within our offerings. Our new setup integrates a selection of toolsets and aids in “Improved Visibility” and “Faster Security Issue Resolution” for our organization (and our esteemed customers). Within a concise timeframe (~3 months), we’ve successfully addressed over 2k+ security issues with this, significantly bolstering our SOC2 compliance endeavors. Learn more about our Security Landscape, Layers, Tools in our blog post. https://www.sudhishkr.com/posts/20230609_how-we-fixed-2kplus-security-issues/
#DevSecOps #SecurityAudit #DgraphLabs #ContinuousSecurity #OpenSource #DevOps #CVEs #Linters #GitHubActions #SecureCoding
2023-06-21
2023-06-22
2023-06-28
2023-06-29
Does anyone have a favorite globally distributed database as a service?
I remember someone pointed out https://neon.tech/, but surely there are others someone loves.
its been a couple years since i used it but i was a fan of Cosmos DB… https://learn.microsoft.com/en-us/azure/cosmos-db/distribute-data-globally
oh, Azure is a thing. I never think to look at what they’ve got going on over there.
I was so put off by the sliding windows8 style panes in their web console when they launched, since then the only thing I’ve used them for was… a weather api? I think? An inherited service integration.
I have no .net workloads, so I’m happy to stay in AWS land. But I’ll checkout cosmos.
afaik neon.tech isn’t globally distributed, they are decoupling storage from compute (similar to Amazon Aurora)
Ahh, gotcha. I’ll do a bit more reading.
I’d look into CockroachDB, but it always depends on the specific use case / acceptable trade-offs
Ty
Ahhhhh. CockroachDB serverless… It’s a multi-tenant platform. Spinning up a “Serverless” offering is simply initiating a tenant provisioning function. https://www.youtube.com/watch?v=0fgva3Mzr9k
What an interesting approach for merging the concepts of slack and forums.
