5,779 karma · joined February 19, 2013
Bugreports:
* Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1889892
* Ubuntu: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1899800
I only purchased RAM with heatsinks since then, and I didn't have such problems anymore (also my latest case has much better airflow)
Wish the 'Recursive' font had a 'Slab-Serif' slider too, would've been interesting to compare.
Having separate repos only makes sense if they are maintained by separate teams with a well defined API in-between that doesn't change often. If the same team maintains all repos then it is just overhead, especially if you end up with a 100 repos and you have significantly less than 100 engineers in your team.
There are also potential build time savings when having a monorepo since you can do parallel builds across different subdirs without serialising at package boundaries.
When you have a higher level language with more accurately defined semantics, running it all through C would risk introducing undefined behaviour.
With an IR you can control and define the semantics more closely to what your language needs.
--- a/fs/dlm/lowcomms.c
+++ b/fs/dlm/lowcomms.c
@@ -1209,7 +1209,7 @@ static struct socket *tcp_create_listen_sock(struct connection *con,
log_print("Set keepalive failed: %d", result);
}
- result = sock->ops->listen(sock, 5);
+ result = sock->ops->listen(sock, 128);
This is mostly a theoretical issue, because upstream RHEL used to support only up to 16 hosts in a cluster.Another alternative is to treat the 25m as a minimum time in Pomodoro: if you are tired or have reached a natural break point for your task then stop. If you're in the flow continue.
You may want to enforce a maximum amount of time for health reasons (e.g. to get up from your chain every now and then).
FWIW this doesn't apply to Fedora currently, because it has a patch that re-enables SHA-1 in security level 2 in non-FIPS mode: https://src.fedoraproject.org/rpms/openssl/blob/master/f/ope...
See here for more details: https://access.redhat.com/documentation/en-us/red_hat_enterp...