It very much does happen. I’m one 11. It seems like every time it updates I get the “let’s finish setting up your computer” screen that asks me to setup one drive.
You shouldn’t be denied for smoking weed in college and disclosing it. I had no issues with that. The other thing is you can appeal a denial of your clearance if you can demonstrate the issue is not an issue. If you truly did only smoke weed in college and get denied due to that, you could appeal and make your case that your weed use is not ongoing, ended in college, and not an issue in your personal life. It’s not guaranteed to be a successful appeal, of course, but the process does exist.
The bigger problem is when people fib about their usage. Saying you only used it in college when you’ve used it more recently is something people do fairly often, and seemingly are encouraged to fib about.
In this particular case I think it has more to do with the times than anything else. Discovering the records of that investigation from when he was 12 in the 40’s would have likely been a massive undertaking if not impossible. The investigator likely recognized this and just had him remove it.
These days I don’t think that happens with digital records. Omitting that incident would almost certainly cause more issues than not now as I’m sure they’d turn up in the investigation. If not included on your sf86 you’d likely be grilled about it.
Investigators are usually reasonable in my experience. If you omitted it because you earnestly forgot because it happened when you were 12, they’d likely understand if you were forthcoming about it during your interview. Investigators are human though so it depends on how they feel.
What they really care about is stuff to try to purposely hide.
Afaik, you can choose to not sign into icloud when creating an account on your mac. It's not a hard requirement like it is on Windows, though they do obviously strongly nudge you to login to icloud.
Yeah I mean if you’re deleting namespaces after each run then sure, that may solve it. They have a pruner now that you can enable too to set up retention periods for pipeline runs.
There’s also some issues with large Results, though I think you have to manually enable that. From their site
> CAUTION: the larger you make the size, more likely will the CRD reach its max limit enforced by the etcd server leading to bad user experience.
And then if you use Chains you’re opening up a whole other can of worms.
I contracted with a large institution that was moving all of their cicd to Tekton and they hit scaling issues with etcd pretty early in the process and had to get Red Hat to address some of them. If they couldn’t get them addressed by RH they were going to scrap the whole project.
An example where they’re creating a new mutex every time they call a function and then surprised when multiple goroutines that called that function and got entirely different mutexes somehow couldn’t coordinate the locks together.
That isn’t a core misunderstanding of Go, that’s a core misunderstanding of programming.
Yeah this whole section of the article threw me all the way off. What even is this code? There’s so many things wrong with it, it blows my mind.
About the only code example I saw in here and thought “yeah it sucks when that happens” is the accidental closure example. Accidentally shadowing something you’re trying to assign to in a branch because you need to handle an error or accidentally reassigning something can be subtle. But it’s pretty 101 go.
This is why I’ve always thought Tekton was a strange project. It feels inevitable that if you buy into Tekton CI/CD you will hit issues with etcd scaling due to the sheer number of resources you can wind up with.
Way back in the day when I primarily wrote c# I used to use a tool called SemanticMerge. It was pretty cool, it actually parsed the code and could pick up refactors like moving a method to a different class and what not. This kinda reminds me of that a bit.
Same. I interact with too many machines, many of which are ephemeral and will have been reprovisioned the next time I have to interact with it.
I value out of the box stuff that works most everywhere. I have a fairly lightweight zsh config I use locally but it’s mostly just stuff like a status like that suits me, better history settings, etc. Stuff I won’t miss if it’s not there.
Very obvious writing style but also the bullet points that restate the same thing in slightly different ways as well as the weirdly worded “full server privileges” and “full nodejs privileges”.
Like… yes running a process is going to have whatever privileges your user has by default. But I’ve never once heard someone say “full server privileges” or “full nodejs privileges”…. It’s just random that is not necessarily wrong but not really right either.
No one used the word must until you right now. The OP comment was posting a valid thing that Windows has that Linux does not. It’s fine if Linux doesn’t have it but I don’t understand where you’re coming from as presenting this as though someone said Linux must have this.