While I think that making it a national holiday would be a good idea because it would maximize the number of eligible voters, it would still disenfranchise some people. There are jobs that have to be done 24/7/365 (mostly safety jobs), therefor there will be someone who is stuck at work that day. There are people who work at power companies on Christmas Day just to make sure the lights on Christmas trees light up.
I think the best approach is what Georgia has done. No-excuse mail-in for those who want that. And 3 weeks of early voting including Saturdays. And for those who just enjoy standing in lines, there is the official Election Day. If a redneck state can get it done without issues, then we all can do it.
I keep on having issues with my WD SN850 dropping offline and coming back R/O but it still fails to produce any reads and my system still crashes. I've applied all the pcie power management fixes on the kernel command line and still having problems. That sounds similar to what you describe. It starts off with vscode disappearing, then UI locks, and then it dumps me to a virtual console spitting kernel errors for a bit.
The nvme drive itself reports no media errors so I really do think it's a system side problem with the pcie controllers...
I'm lucky that I had no USBC issues with mine I guess. Unlike my ryzen desktop that hard locks when resuming from suspend sometimes when it goes to enumerate the USB devices. If I time a key press right I can get it to continue some times, but if I miss the window it just shuts down entirely.
AMD has had several USB based issues on their 500 series chipsets, x570 etc. so part of me wonders how much of these problems are on the vendor vs the integrator.
If you're on Linux you might be able to use a combination of modprobe + udev + systemd unit files to hardcode a solution.
Either you hardcode your keyboard and mouse absolutely into kernel parameters, or you make two systemd unit files: one that runs with before suspend and one that runs 'before' resume.
You make the before suspend unit file manually temporarily disable USB enumeration. And the before resume unit file enables it again.
This trick at least works with Gigabyte Aorus 5XX motherboards that have an infamous suspend bug, where any used PCIe SSD slot would prevent the system from properly suspending and you have to disable the slot temporarily.
Also, always check the NixOS repo for stuff like this. In some ways it has started to rival or even surpass the Arch wiki for finding workarounds for hardware quirks.
My support experience has been quite similar. Lots of required evidence, slow responses, and then just links to buy replacement parts in the store.
The kicker is that the things they were telling me to buy didn't even fix the problem. My fingerprint reader was very flakey, and after replacing it and all cabling connected to it, it still didn't work.
They then told me to buy a whole new input cover which was the wrong solution again. The issue was the touchpad, which routes the signal for the fingerprint sensor through its circuit board.
They also encouraged me heavily to update the BIOS and firmware of everything aggressively before really digging into any of the kernel messages I was seeing.
All that said, it's really hard to complain that for $50 and some waiting I was easily able to fix the problem.
Compared to replacing the battery on a MacBook pro which took me 5hrs and required complete disassembly of the chassis sans fans it was a dream.
Here's to hoping that framework does better, they do seem to take well to community feedback.
Dial up into an air gapped network defeats the purpose of being air gapped. I would think the bare minimum standard is that there is no way to change anything in the control systems without being physically present at the facility, past it's physical security boundary.
For example, traditionally still film cameras used 35mm film, but cinema cameras also used 35mm film. However the cinema cameras capture the image vertically instead of horizontally on the film, otherwise known as a Super 35. Literally the film runs through the camera vertically instead of horizontally.
In order to make an image work that is understandable to our brains you either need to do heavy cropping and waste tons of film, or you use an anamorphic lens to "squeeze" more light onto the film. You then have to reverse that when you go to project the film.
Those could just be individual commits on a branch. Why does it need to be a stacked PR? That concept really only exists within the interfaces of these kinds of tools.
They don't. But reviewing individual commits in the GitHub UI is hard.
A set of stacked PRs is exactly the same as a line of commits. The only difference is the UI, but the UI is the important bit here because lack of UI is what's stopping folk from doing that today.
Even when I've developed my changes as a stack of commits, I'll feed them to my team one commit (and one PR) at a time so they're easier to review — and I discovered that GitHub had turned on stacked commits UI because for one particular project I'd manually created a set of PRs in advance (with the right bases) and GitHub offered to create a stack out of them.
> They don't. But reviewing individual commits in the GitHub UI is hard.
So instead of solving that problem, GitHub developed tooling around a workaround for that problem (targeting a PR at another branch that also has a PR).
Expanding reviews to allow per-commit reviews avoids the need for managing additional branches and all the headache that comes with it.
Indeed. But lots of people have never even heard of Gerrit :P.
And the implementation feels very much like it sits in the UI layer, rather than further down the stack.
I'm not trying to claim stacking PRs in this way is the best way (it's not). But it does add an extra affordance for those who want it without burdening those who don't with the need to understand why someone would prefer it.
And there are also plenty of ways that people have been working around GitHub's (and to a lesser extent, git's) lack of tooling for working on changes in this way. I'm sure they have customers clamouring for the feature; whether they'll be happy with what they get remains to be seen.
(Very happy jujutsu user here, my tooling makes it really easy to create stacked commits with a stable identifier that maps really easily to branches and then onwards to running `gh stack`, but what GitHub have delivered is definitely still lacking)
I’m a pretty clean committee. About every graphite stack I’ve worked on for the past 2years has been single commit per PR. The tooling managing all the rebasing and PR bases is great.
The sad fact of life is that too many developers are used to pushing PRs with unprincipled commits, and relying on squash merges.
The approach that GitHub chose can show those people almost immediate benefits, which is surely the better path towards adoption than trying to reeducate everyone to adopt a development flow based on clean rebases.
And for those of us who do prefer clean rebases, the thing they built is still useful.
A bunch of details aside, the major conceptual thing that the email based flow has which is still missing in GitHub's data model is the ability to have a discussion on the stack as a whole.
> The sad fact of life is that too many developers are used to pushing PRs with unprincipled commits, and relying on squash merges.
We couldn't organise our commits once the PR review started because reviewers would complain they couldn't easily determine what had changed between rounds of reviews.
If we tried to organise them after review then approvals would be stripped so squash was the only way we could keep the main line history reasonably tidy as you can keep the approvals if GitHub does the squash via the UI.
They could but they don't belong together. A PR should be about one thing. Refactoring one module for another's sake should be done in another PR. If not for reviewing, for revertability, and future debuggability.
Yeah, I think it's largely a UI issue! I really want a UI that lets me review distinct changes that are dependent on each other, and handle comments/changes neatly within that structure. I've found GitHub quite lacking there historically.
Also, if you're the mchristen I know, then I think we've had this discussion before haha! Hope you're well :)
For the longest time I could not stream YouTube on my Google fiber connection without constant buffering unless I ran my browser through a socks proxy to a server outside of the ISP network.
Some time a few years ago they got it figured out and it's no longer been an issue. I could not explain to the CSR in terms they understood what the problem was.
I always assumed it was some kind of mis-configuration...
reply