larntz

He didn't get the job. :(

I think a few games are only on NFL Network (not always included in the base cable subscription) also. And you'll need Peacock if you don't have cable/antenna.

This is ridiculous logic. When a person makes a premeditated decision it was their choice, and only their choice. There is no one else responsible.

Is he required to permanently fire anyone because of a government shutdown? If the answer is no, then he made a choice to do so (if firings happen).

> Your secrets are not safe from someone if someone needs them to run your code.

This is true. I don't disagree with that or you're assessment of repo secrets.

My comment was in the context of the grandparent committing secrets to a private repo which is a bad practice (regardless of visibility). You could do that for tests, sure (I would suggestion creating random secrets for each test when you can), but then you're creating a bad habit. If you can't use random secrets for tests repo secrets would be acceptable, but I wouldn't use them beyond that.

For CI and deploys I would opt for some kind of secret manager. CI can be run on your own infrastructure, secret managers can be run on your own infrastructure, etc...

But somewhere in the stack secret(s) will be exposed to _someone_.

I wouldn't rely on anything other than rotating leaked credentials.

Does that entire model fit in gpu memory? How's it run?

I tried running a model larger than ram size and it loads some layers into the gpu but offloads to the cpu also. It's faster than cpu alone for me, but not by a lot.

This is what I'm using on a old-ish Dell Latitude. Everything works except the fingerprint reader, but I knew that going in and I'm ok with it.

Which makes me wonder, would docker have gained traction if they didn't offer free registry services?

Are you referring to the Panama Papers? I searched for Princeton Papers but didn't find anything similar to you comment.