2,322 karma · joined June 26, 2011
Also, the great thing is you might not even have an explicit `receive` statement in your gen_server code. You might just be using a library that is using a `receive` somewhere that is unsafe with a large message queue and now you are burned. The BEAM also added some alternative message queue thing so you are able to use this instead of the main message queue of a process which should be a lot safer but I think a lot of libraries still do not use this. This alternative is 'alias' (https://www.erlang.org/doc/system/ref_man_processes.html#pro...) which does something slightly different from what I thought which is to protect the queue from 'lost' messages. Without aliases 'timeouts' can end up causing the process message queue to be polluted with messages that are no longer being waited on. This can lead to the same problems with large message queues causing throughput of a process to drop. However, usually long lived processes will have a loop that handles messages in the queue.
1) pages from the shared library are lazily loaded into memory so if you try and access a new page you are going to get it from the new binary which is likely to cause problems
2) pages from the shared library might be 'swapped' back to disk due to memory pressure. not sure whether the pager will just throw the page away and try to swap back in from disk from the new file contents or if it will notice the disk page is dirty and use the swap for write back to preserve the original page.
also, i remember it used to be possible to trigger some error if you tried to open a shared library for writing while it was in use but I can't seem to trigger that error anymore.
also, i think apple has a scheme similar to this for protecting the passcode from being brute forced when recovering from iCloud backup. however, if this scheme breaks it doesn't reveal the encryption key i believe it just allows the passcode that protects the encryption key to be brute forced which I guess may or may not result in the encryption key being revealed.
but the problem is the real game being played is different because the political process ends up diverging from maximising value in the economy. the free trade argument is this is because the political process is captured by concentrated interests who benefit from tariffs to reduce competition. the deadweight loss caused by tariffs to the rest of society is not properly accounted for in the political process because the cost is diffused over many people. other people who accept the text book comparative advantage argument but reject free trade will claim to have a different optimisation function that is not purely maximising value in the economy. for example maybe they think its important to have a strong manufacturing base in order to make it easier to re-arm to fight a conflict.
but if we accept this situation then its difficult to say what the optimal strategy is because you don't really know the payoff matrices for the players. even what they tell you could be a lie and might be difficult to derive what their values are based on their actions.
> Maxie Allen, 50, and Rosalind Levine, 46, were questioned on suspicion of harassment, malicious communications and causing a nuisance on school property. After a five-week investigation, the police concluded that there should be no further action.
> A police officer also said that elected officials could be treated as harassment suspects if they continued advocating for the couple.
> Andy Prophet, chief constable of Hertfordshire, defended the arrests, saying that the force had given warnings and they were lawful, although he conceded that “with the benefit of hindsight we could have achieved the same ends in a different way”.
the optional static type checking in python gives you a stronger typing than what golang does because you don't have to type everything as (None | Foo) and presumably its a type error to perform Foo operations on a (None | Foo) type.
The full text of the executive order is available here: https://www.whitehouse.gov/presidential-actions/2025/03/addr... and mentions removing access to a SCIF:
> The Office of Management and Budget shall identify all Government goods, property, material, and services, including Sensitive Compartmented Information Facilities, provided for the benefit of Perkins Coie. The heads of all agencies providing such material or services shall, to the extent permitted by law, expeditiously cease such provision.
It has also been publicly documented from court transcripts that contractors were making unauthorised queries but I don't believe it has ever been released who the contractors were or who they were targeting. Hopefully, if this is the reason for removing SCIF access the current government is able to make these documents public without redaction. Though, the whole thing could just be a conspiracy theory generated by people piecing together bits of random information.