dTP90pN
It's little very badly translated popup under "Available models" in Model Studio -> My subscriptions: https://imgtree.co/direct/s9x9ksdg.png
https://de.m.wikipedia.org/wiki/Anschlussstelle_(Autobahn)#D...
A supply chain attack serve as the basis for another supply chain attack.
Of course, you have to do this the "correct way", which in and of itself requires a bit of experimentation to learn.
If you're running the latest kernel, which automatically sets the chicken bit, you don't have to worry about this.
If you're running fixed microcode, which is only available for Rome, Castle Peak and Mendocino, you don't have to worry about this. Good microcode revisions are:
Rome / Castle Peak: 0x0830107a (published)
Xbox Series X: unknown
Renoir / Grey Hawk: 0x0860010b
Lucienne: 0x08608105
Matisse: 0x08701032
Van Gogh (Steam Deck): unknown
Mendocino: 0x08a00008 (published)
If you're running neither the latest kernel, nor fixed microcode, you should set the chicken bit yourself until you have updated those. wrmsr -a 0xc0011029 $(($(rdmsr -c 0xc0011029) | (1<<9)))`good_revs` as per the kernel: https://github.com/torvalds/linux/commit/522b1d69219d8f08317...
Currently published revs ("Patch") (git HEAD):
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/lin...
As of this writing, only two of the five `good_rev`s have been published.
I don't think that is correct. AMD has released a microcode update[0] for family 17h models 0x31 and 0xa0, which corresponds to Rome, Castle Peak and Mendocino as per WikiChip [1].
So far, there seems to be no microcode update for Renoir, Grey Hawk, Lucienne, Matisse and Van Gogh. Fortunately, the newly released kernels can and do simply set the chicken bit for those. [2]
[0] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/lin...
[1] https://en.wikichip.org/wiki/amd/cpuid#Family_23_.2817h.29
[2] https://github.com/torvalds/linux/commit/522b1d69219d8f08317...
[1] https://github.com/mitmproxy/mitmproxy/commit/8c6ec5cb56fbf4...
edit: I misread that ticket. It's about allowing school/company IT to disable the feature, not to allow them to use it.
There is consideration to allow enterprises to disable this feature though: https://bugzilla.mozilla.org/show_bug.cgi?id=1834985
edit: fixed 2nd link description.
Regarding libdbus-glib-1-2, you may want to open a bug. It looks like [1] it's mainly used by the ~12 year old UPowerClient, and more recently, for wake/sleep and timezone change notifications (nsAppShell).
[1] https://searchfox.org/mozilla-central/search?q=DBusG.*&path=...
https://github.com/christianselig/apollo-backend/blob/b992d2...
Reddit had many years to listen to 3p devs and to it's own internal developers to improve their API. They/Leadership decided not to do so.
/**
* @type {module:look/here~MyType}
*/
or TypeScript "JSDoc" imports like /**
* @type {typeof import("./look/here").MyType}
*/
or both?Looks like the negative DST has already caused problems in the past and applications that can't handle it (ICU & OpenJDK) have to build tzdata as per the rearguard section / ziguard.awk.