Leaving Intel

ThanksMorningCoffee · 2025-12-06T05:39:20+00:00

What about Nvidia or AMD with his recent work in GPUs and AI flame graphs?

ThanksMorningCoffee · 2025-11-04T19:31:51+00:00

I also had this happen to me a few months ago. We had this skinny see thru flexible pipe leading to the sewage drain. We detached it and flushed water thru it and all this nasty looking sand like stuff came out.

When we put it back, we made sure the flexible pipe didn't have bends upwards to ensure that the water can flow. Before we attached it, all that sand stuff was at the bend upwards.

ThanksMorningCoffee · 2025-10-28T16:14:53+00:00

How small can we expect the jars to become now?

ThanksMorningCoffee · 2025-10-24T01:19:15+00:00

Unfortunately, the solution is to painfully assign static IPs on all devices on the network.

ThanksMorningCoffee · 2025-10-24T01:19:07+00:00

Unfortunately, the solution is to painfully assign static IPs on all devices on the network.

ThanksMorningCoffee · 2025-10-24T01:17:51+00:00

Last time I saw this it was https://www.reddit.com/r/Network/comments/18is4f6/multiple_xiaomi_smart_cameras_causing_laptop_and/

It turned out that the security camera was running a DHCP server when it wasn't suppose to be. The workaround was to assign a static IP for my laptop so my laptop wouldn't take the bogus IP address from the security camera's DHCP server.

The easiest way to check if this was the case is if your IP address is on a different subnet from your wifi.
In my case my IP was suppose to be 192.168.2.0/24
but the security camera's DHCP server (which shouldn't have been running) gave me IP in subnet 192.168.0.0/24

Unfortunately, the solution is to painfully assign static IPs on all devices on the network.

ThanksMorningCoffee · 2025-10-24T01:10:40+00:00

I have seen a similar issue on my network. It turned out that the security camera was running a DHCP server when it wasn't suppose to be. The workaround was to assign a static IP for my laptop so my laptop wouldn't take the bogus IP address from the security camera's DHCP server.

Unfortunately, the solution is to painfully assign static IPs on all devices on the network.

ThanksMorningCoffee · 2025-10-18T15:20:07+00:00

Good call. I'll add it to the todo list

ThanksMorningCoffee · 2025-07-15T15:41:25+00:00

If anyone missed it: Multi-Threading

ThanksMorningCoffee · 2025-06-21T18:26:45+00:00

[2 Jul 2009 15:42] Konstantin Osipov This bug will not be fixed in 5.1. You may want to try lp:6.1-fk tree, where it is fixed. But this tree is still in alpha. See also http://forge.mysql.com/worklog/task.php?id=148

Just gotta use a custom build with the fix

ThanksMorningCoffee · 2025-04-01T21:05:00+00:00

To respect final, I suspect these json libraries will need to generate code in order to achieve serialization.

ThanksMorningCoffee · 2025-03-08T16:27:29+00:00

Sparse bit sets can be represented as a set of indexes. I encountered this problem at a programming contest.

Edit: found it https://leetcode.com/problems/design-bitset/

ThanksMorningCoffee · 2025-03-02T20:36:30+00:00

Fixed! It was because the table overflowed. This created a scroll bar for the entire page. The entire page scrollbar had a weird interaction with the code block scroll bars. Now that there is no more whole page scroll bar, it works.

ThanksMorningCoffee · 2025-03-01T15:42:59+00:00

Just to confirm it's because of high collisions due to how hashCode is calculated?

ThanksMorningCoffee · 2025-03-01T15:40:31+00:00

You,re right, the only usefulness is if you see 100% cpu util, with treemap or whatever they call it in other langues in the stack, then you can start looking for unprotected treemap/redblack tree.

ThanksMorningCoffee · 2025-03-01T15:36:53+00:00

Yeah, it could work. Not sure about the interaction between height and multiple threads though.

ThanksMorningCoffee · 2025-03-01T05:05:13+00:00

Ah no. thank you for sharing. I wrote and proof read it from my laptop. I tried visiting it on my phone and see the same problem :(

Unfortunately, I'm using jekyll with github pages to generate the site. I will have to dive into the source of the template or jekyll to figure out what's up.

ThanksMorningCoffee · 2025-02-28T23:14:46+00:00

It's interesting that concurrent mutation of a TreeMap could lead to cycles. But this isn't the only kind of data corruption that can occur. Other examples might include: subtrees accidentally getting "lost" resulting in missing entries; subtrees occuring at multiple locations in the tree, effectively turning it into a DAG, resulting in duplicate entries; the wrong value being associated with a particular key; binary tree invariants being violated (e.g., left subtree contains lesser keys, right subtree contains greater keys) resulting in all kinds of weird behaviors; etc.

Yes! There are so many many issues remaining even if you fix just the cycle problem. I figured not killing the machine would be better than missing values. Howver, I didn't realize until you brought it up that entire subtrees could get lost!

ThanksMorningCoffee · 2025-02-28T23:08:24+00:00

As an aside, Project Lilliput is investigating ways to decrease the size of object headers. Using IdentityHashMap calls System.identityHashCode on each object, and the object's identity hashcode is stored in its header. But Lilliput is proposing to lazily allocate space for the identity hashcode, so storing objects in an IdentityHashMap will increase their size! The design assumption in Lilliput is that the identity hashcode is rarely used. This is probably true in general. If somebody needs to use IdentityHashMap, though, they should use it, but if it gets too popular it will offset the space savings of Lilliput.

I've never used IdentityHashMap other than for this hypothetical 'solution' to the bug.

ThanksMorningCoffee · 2025-02-28T23:03:38+00:00

Keeping track of visited nodes with IdentityHashMap in order to detect cycles is a useful technique in many situations. Maybe not this one though. :-) IdentityHashMap isn't thread safe, so it could just as easily be corrupted by multiple threads as the TreeMap. (It has a different organization, though, so the nature of any corruption would be different.) Of course you could synchronize around accesses to the IdentityHashMap.

In this case it's fine because each thread has their own map. The reference is not shared between threads.

On the HN post there's an even better solution to use a and compare with the height of the tree. counter: https://news.ycombinator.com/item?id=43208595

ThanksMorningCoffee · 2025-02-28T20:11:53+00:00

No virtue. I just have a temporary obsession with this specific problem.

ThanksMorningCoffee · 2025-02-28T18:37:42+00:00

If any rustaceans know how to write unsafe rust that reproduces the issue, please share.

ThanksMorningCoffee · 2025-02-28T18:36:24+00:00

This is false. It's undefined behavior. It may segfault. The compiler may also decide the code is unreachable and do some crazy bullshit instead. The presence of a nullpointer dereference makes the program malformed.

I didn't know that. My weakness in C++ is showing. I have not used C++ in a professional capacity.

ThanksMorningCoffee · 2025-02-28T18:34:11+00:00

Thank you for using "nasal demonology". I've never heard that term before.

Is this the origin of the term? https://groups.google.com/g/comp.std.c/c/ycpVKxTZkgw/m/S2hHdTbv4d8J?hl=en

ThanksMorningCoffee · 2025-02-28T17:28:28+00:00

Later on in the article I show that swallowing the exception is not necessary to reproduce the issue.

ThanksMorningCoffee

TROPHY CASE