ZLib VS virtualagc

A fix has been checked into the upstream git repo: https://github.com/madler/zlib/pull/843 but a release has not yet been made including it.

So the real issue here is that the lack of tree validation before the tree construction, I believe. I'm surprised that this check was not yet implemented (I actually checked libwebp to make sure that I was missing one). Given this blind spot, an automated test based on the domain knowledge is likely useless to catch this bug.

[1] https://github.com/madler/zlib/blob/master/examples/enough.c

In the source code of the Node.js opensource project, lib folder contains JavaScript code, mostly wrappers over C++ and function definitions. On the contrary, src folder contains C++ implementations of the functions, which pulls dependencies from the V8 project, the libuv project, the zlib project, the llhttp project, and many more - which are all placed at the deps folder.

Seeing the text in red got me thinking for a moment, "wow, didn't realize pirates had such love for an open-source compression library"

cd "${srcdir}/zlib-$pkgver/contrib/minizip" make install DESTDIR="${pkgdir}" install -D -m644 "${srcdir}/zlib-$pkgver/LICENSE" "${pkgdir}/usr/share/licenses/minizip/LICENSE" # https://github.com/madler/zlib/pull/229 rm "${pkgdir}/usr/include/minizip/crypt.h"

I don't think that's a great example.

For instance, I can step through and even modify that code using tooling like AGC emulators like this one http://www.ibiblio.org/apollo/#gsc.tab=0

What makes it open source is access to the same level of source access that the original developers worked in.

That's what's missing here. Mistral's engineers do not simply open this binary in their editor to do their job.

Glad you're enjoying the videos! I'm Mike from them. :) The Apollo 14 code I linked above was reconstructed in the same way as Luminary 69/2, but the process was far, far too involved for a video. Like I said above, I probably won't be much help with math, but I'd be more than happy to assist with finding documentation or navigating AGC code whenever you want!

The fact that all the information about the computer and software is public and you can verify it yourself like thousands of people have. https://www.ibiblio.org/apollo/

If you’re curious about the the technical specs of the AGC check out Ron Burkey’s website, it’s even got the source code for you to see for yourself: https://www.ibiblio.org/apollo/

Of course you should be able to tell us because all the hardware architecture and software can be found here. So you must have fully reviewed it and located the issues. Right? Than please point out where the error is.

It had manually encoded ROM in the form of "core rope memory", which is pretty wacky, but it was a digital computer. In fact, it was the first IC computer.

You can learn way too much about it and even operate (a simulation of) one here: http://www.ibiblio.org/apollo/