Avoid allocating memory in sig segv handlers. I worked at a company once that had written their own handlers that tried to print a stack trace. I was fortunate enough to find a machine in a test environment that segfaulted while allocating memory. The handler then caused a deadlock in a call to malloc (through new). I ended up rewriting the handler to fix two sources of memory allocation. First I preallocate enough space to do string manipulations in the handler. Second I made eager calls to a few libc functions used in the handler to avoid memory allocation from lazy binding from ld.so.
RD1 generates power 99% of the year and collects solar radiation by autonomously redirecting its reflectors toward a concentrator to focus sunlight throughout each day. RD2 uses flat panels, with solar cells facing away from Earth and microwave emitters facing toward the Earth. RD2 generates power 60% of the year due to its limited capability to reposition itself or redirect solar radiation toward its solar cells.
Every projection between a sphere, or even sphere section to a plane is going to have distortion. You can make tradeoffs between different distortion types, but you wont eliminate them.
They contained the impact. Root causing or “understanding” should come after impact mitigation. If needed find a safe way to reproduce the bug without customer impact.
We reverted the refactoring, deployed, un-banned the CEO, and set about analysis.
Graduate students provide enormous value for their cost in funding. I’d like to better understand how k-12 students contribute here. Those students make up 88.7k of the reduction. How much do these students contribute and at what cost?
I’m in no way against inspiring the next generation. My question is aimed at correctly interpreting this table. The NSF is a worthwhile expense, but let’s understand the data we have.
For a limited definition of “solved”, sure. I recommend looking at the article for the dates that commonly used systems have solved the problem. Most are very recent, and changes like this take a very long time to adopt.
She’s complaining about the phrase “giving time back”. It’s a phrase used in corporate settings that is often used for small amounts of time. The meaning isn’t really important, but I find it’s used by individuals as a way of “virtue signaling” that everyone in the meeting are busy with other priorities.
Hopefully it’s a phrase that will pass quickly like many other corporate phrases.
Looking into the sale by James he shared in his form 4 filing that his sale was to cover the transaction cost in exercising his non-qualified stock options (NSO). This sale results in closing part* of his NSO grant and acquisition of 477,011 shares. The net cash value of the sale comes out to $196k. This should result in ordinary income tax of roughly $42M.
* I’m not actually sure how NSOs work here. It’s unclear to me if there are still exercisable options in this grant or any other outstanding grants.
The shares were sold to cover the exercise price relating to the exercise of stock options to purchase 531,787 shares, which are scheduled to expire in 2025.
It’s one backed by a lot of data. One example is from the Android project.
The percent of vulnerabilities caused by memory safety issues continues to correlate closely with the development language that’s used for new code. Memory safety issues, which accounted for 76% of Android vulnerabilities in 2019, and are currently 24% in 2024, well below the 70% industry norm, and continuing to drop.
There’s an argument that critical infrastructure software vendors are already meeting standards for basic, non-memory related items. Yes, there are other categories, but memory safety is one that’s harder to verify. Moving to memory safe languages is an ensure a category of correctness. This excludes usage of unsafe escape hatches.
I’m going to whoosh the joke for a moment.
Avoid allocating memory in sig segv handlers. I worked at a company once that had written their own handlers that tried to print a stack trace. I was fortunate enough to find a machine in a test environment that segfaulted while allocating memory. The handler then caused a deadlock in a call to malloc (through new). I ended up rewriting the handler to fix two sources of memory allocation. First I preallocate enough space to do string manipulations in the handler. Second I made eager calls to a few libc functions used in the handler to avoid memory allocation from lazy binding from ld.so.
https://ntrs.nasa.gov/api/citations/20230017756/downloads/ASCEND%20SBSP%20Final%2005162024.pdf
Here’s the paper from NASA that this is based on.
https://ntrs.nasa.gov/api/citations/20230017756/downloads/ASCEND%20SBSP%20Final%2005162024.pdf
Footage is in the link OP provided.
Every projection between a sphere, or even sphere section to a plane is going to have distortion. You can make tradeoffs between different distortion types, but you wont eliminate them.
Gauss's Theorema Egregium
They contained the impact. Root causing or “understanding” should come after impact mitigation. If needed find a safe way to reproduce the bug without customer impact.
It looks like the challenge was a variation on multi-agent path finding. Neat.
https://en.m.wikipedia.org/wiki/Multi-agent_pathfinding
https://atcoder.jp/contests/awtf2025heuristic/tasks/awtf2025heuristic_a
I’m not disagreeing. The report isn’t clear. This is written by people asking Congress for a budget cut.
The actual impact to the pipeline may be far larger.
Graduate students provide enormous value for their cost in funding. I’d like to better understand how k-12 students contribute here. Those students make up 88.7k of the reduction. How much do these students contribute and at what cost?
I’m in no way against inspiring the next generation. My question is aimed at correctly interpreting this table. The NSF is a worthwhile expense, but let’s understand the data we have.
For a limited definition of “solved”, sure. I recommend looking at the article for the dates that commonly used systems have solved the problem. Most are very recent, and changes like this take a very long time to adopt.
She’s complaining about the phrase “giving time back”. It’s a phrase used in corporate settings that is often used for small amounts of time. The meaning isn’t really important, but I find it’s used by individuals as a way of “virtue signaling” that everyone in the meeting are busy with other priorities.
Hopefully it’s a phrase that will pass quickly like many other corporate phrases.
ClassPass
Trial cancellation terms (sorry anchor link doesn’t seem to be working)
Relevant XKCD
https://xkcd.com/1172/
2010 and 2014 California AG elections, 2016 California Senate election, and 2024 US presidential election.
The source is worth a quick read. It’s very tongue in cheek.
Merrick Garland is no longer attorney general. What do you expect him to do?
Looking into the sale by James he shared in his form 4 filing that his sale was to cover the transaction cost in exercising his non-qualified stock options (NSO). This sale results in closing part* of his NSO grant and acquisition of 477,011 shares. The net cash value of the sale comes out to $196k. This should result in ordinary income tax of roughly $42M.
* I’m not actually sure how NSOs work here. It’s unclear to me if there are still exercisable options in this grant or any other outstanding grants.
https://www.sec.gov/Archives/edgar/data/1318605/000177134025000004/xslF345X05/edgardoc.xml
Some of these are incorrect. Amazon didn’t acquire iRobot, and the planned acquisition was terminated in January 2024.
https://media.irobot.com/2024-01-29-Amazon-and-iRobot-agree-to-terminate-pending-acquisition
arXiv link - https://arxiv.org/abs/2411.19826
It’s one backed by a lot of data. One example is from the Android project.
https://security.googleblog.com/2024/09/eliminating-memory-safety-vulnerabilities-Android.html
There’s an argument that critical infrastructure software vendors are already meeting standards for basic, non-memory related items. Yes, there are other categories, but memory safety is one that’s harder to verify. Moving to memory safe languages is an ensure a category of correctness. This excludes usage of unsafe escape hatches.