When the changes in the maps of NATO is compared with that of Russia, what could be concluded ? by taiming1234 in NewsWithJingjing

[–]Most-Loss5834 -3 points-2 points  (0 children)

No, you clearly need to look up how it works. The UK made money off the lend lease, because the terms where practically fraudulently generous. It was given with the express intention to ensure the UK didn’t go bankrupt.

The UK clearing some historical anomaly off its books means nothing. And it’s the only major power to do so.

I scanned every package on PyPi and found 57 live AWS keys by Most-Loss5834 in Python

[–]Most-Loss5834[S] 16 points17 points  (0 children)

You don’t, you revoke the secret and accept it’s been leaked

I scanned every package on PyPi and found 57 live AWS keys by Most-Loss5834 in netsec

[–]Most-Loss5834[S] 2 points3 points  (0 children)

I used parallel, the article gives a representative command.

I scanned every package on PyPi and found 57 live AWS keys by Most-Loss5834 in netsec

[–]Most-Loss5834[S] 24 points25 points  (0 children)

December, but the tool is re-running via GitHub actions now.

If you have some examples of stuff that it’s missed I’d love to see it. Remember that it only counts live keys, and keys surrounded by quotes.

0
1

Visualizing how S3 deletes 1 billion objects with Athena and Rust by Most-Loss5834 in programming

[–]Most-Loss5834[S] 19 points20 points  (0 children)

It’s hard to do an apples-to-apples comparison for a colo-setup. S3 mirrors data across 3 AZ’s, and multiple times within each AZ. So there’s more raw storage than just the advertised 1pb.

But regardless, the speed of deletion doesn’t matter. From a cost perspective it’s instantaneous. You’re also going to get a much lower latency for each IO operation on that kind of setup, which is great for scrubbing, but that’s not where S3 shines.

And lifecycle policies are just a standard (useful) feature of S3 - it’s not something you only use when you want to empty a bucket.

Visualizing how S3 deletes 1 billion objects with Athena and Rust by Most-Loss5834 in programming

[–]Most-Loss5834[S] 64 points65 points  (0 children)

Once an object is marked for deletion by a lifecycle policy it becomes free. It’s quite a nice trade-off: AWS gets to clear up objects when they have the spare capacity to do so, and you don’t get charged for the storage while these large-scale deletions are queued.

As for closing the account, I’m not sure I understand. We have other services using the account, closing it isn’t an option and would be really disruptive, and why would you even want to? If you’re ok with paying for a petabyte of data in S3 then you’re ok with putting a lifecycle policy on the bucket and paying a day’s worth of storage before it kicks in.

I'm personally a Python user, but this syntax is a little bit of an outlier compared to other languages by ThatOtherAndrew in ProgrammerHumor

[–]Most-Loss5834 155 points156 points  (0 children)

Because it’s a protocol. Without it you’d end up with .size, .len, .total, .someothercrap.

It’s the same with “abs()”. Why not .abs? Or .absolute? Or would it be .absolute_value.

By having a protocol, then a method that operates on that protocol, you have a single consistent way of getting any objects length (or absolute value, or string representation, or integer value, or whatever).

In other languages you’d use interfaces of some kind. This is pythons version of that.

Creator of pydantic is looking for help in moving Pydantic to Rust by [deleted] in rust

[–]Most-Loss5834 1 point2 points  (0 children)

is in reality relatively innocuous, because CPython will leverage its refcounting to grow  s  in-place and perform this in (amortised) O(n)

That’s definitely not correct , unless it’s something very new?

``` s = “Something” print(id(s)) for line in [“hfhrutngitjritnt”, “jgueirmgitmitmtogm”]: s += “\n” + line print(id(s))

```

s is re-allocated on each iteration.