pitterpatter
Why was the service holding things up? Because it was waiting on acquiring a lock held by one of its other threads.
What was that other thread doing? It was deadlocked because it tried to recursively acquire an exclusive srwlock (exactly what the docs say will happen if you try).
Why was it even trying to reacquire said lock? Ultimately because of a buffer overrun that ended up overwriting some important structures.
Misappropriating trade secrets is already a crime in several states and federally.
>you are paid highly for the specific reason that you are long term investment for that company.
Sounds like the company then should make staying long term an attractive proposition. I mean I understand, but "investment" usually implies some amount of risk.
https://doc.rust-lang.org/reference/type-layout.html#the-c-r...
So you didn't read the article huh. The very first paragraph says:
>“Ah”, they say, “that’s what the scroll wheel is for”. My friend, not everyone can use a scroll wheel or a swipe up touch screen.
Or literally the next paragraph about difficulties small/hidden scrollbars cause with other input methods, e.g. eye trackers.
oh man, I had my Windows install get into a weird state where trying to open 'Updates & Security' would just crash the Settings app altogether. Eventually I submitted a feedback hub report for it with a dump and tttrace (though that was a journey in and of itself) and in the meanwhile I actually managed to get updates installed via the PSWindowsUpdate powershell module. Alas, that still didn't fix the crashing Settings app. I had a friend at MS promote my feedback hub item to a bug who relayed the reason being that my copy of MusUpdatehandlers.dll was corrupt somehow. Ok, I guess I can try using sfc and dism to hopefully repair that. A couple rounds of that and all I learnt was I actually had a few more update related DLLs that were also corrupted. The real kicker being the copy in the store was also corrupted??
2022-05-25 16:40:41, Info CSI 00000226 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\\updatepolicy.dll; source file in store is also corrupted
Anyways, I was too stubborn to just reinstall and got it fixed by grabbing an install.wim from an ISO that matched my install and telling dism to use that. The really dumb thing was i first tried to do the repair in offline mode pointing it at the install.wim for sources but turns out that's just not supported.
Instead you get some opaque failure message and it only mentions the fact that wasn't supported in a single line buried in the huge log file.Uh, from the article:
>We use many off-the-shelf development boards and even provide support for a number of these boards in Hubris. These are great for many use-cases, but less great when we are trying to model specific circuits or subsystems of our product designs. Second, we have numerous examples of custom boards that were built simply because we could find no useful OTS (off-the-shelf) alternative.
Why does that require multiple implementations? There's nothing stopping said party from adding support for their OS/arch to rustc directly today. There are multiple examples of this already: fuchsia, Sony PSP, Nintendo Switch, etc [1]. Now if you want support in rustc itself out-of-the-box this does require LLVM support your target as well. But even then, again nothing stopping you from adding LLVM support too. The avr-rust project for instance maintained an LLVM/rustc fork for a while before those patches were upstreamed.
[1] See the wide variety of targets with varying support today: https://doc.rust-lang.org/nightly/rustc/platform-support.htm...
Math departments also tend to be a lot more lax in my experience. Case in point: I got sign-off to take a 300-level pure math class without its 300-level prereq. As well as just replace one required course for another to graduate.
https://wiki.qemu.org/ChangeLog/6.2#Arm
>On macOS hosts with Apple Silicon CPUs we now support the 'hvf' accelerator for running AArch64 guests
I'm not sure I understand this point? For one, if anything there's a clear preference for cars as the default mode of transportation.
Pretty sure they backtracked on that. "As such, games built against the DirectStorage SDK will be compatible with Windows 10, version 1909 and up"
https://devblogs.microsoft.com/directx/directstorage-develop...