Fore query "cannot persist Microsoft authentication token cache securely!" (with quotes) Google returns single result, written in Chinese. Luckily I opened that Chinese result and spotted link to that issue.
duck.com does find the issue at hand.
I mean GitHub is no small site, but somehow I expected that Google will find my ANY public string on the internet.
Not that it doesn't find issues at all - but I stumbled upon this one that got left out.
Sometimes I can't find anything non-commercial. For instance, I wanted to find out where the phrase "milk and honey" comes from. Googling it only yields a book for sale. But a Wikipedia search for it, which is one click away in Firefox, gives me this page [0] which is exactly what I wanted to know.
Looks like Google no longer acts on the mission to organize the world's information, but focuses on making money.
My tip is to try to avoid searching. Ask yourself where the information may be located. Then try to find that location if you do not already know it.
GitHub is absurdly large in terms of the number of documents since there's ostensibly a "document" per file and commit, it's likely the crawling budget Google affords GitHub simply runs out before they've crawled it all unless they implement special logic to prioritize issues and about-pages.
Is it the case tough? Does Google index everything? I don't think it's the case.
I'm not even sure I can blame them. Creating the search index is a huge investment on Google's side, both in terms of time (can't crawl too fast or else they knock the target offline) and in terms of bandwidth, CPU power, and storage space. But Google needs to operate their search profitably, on average, or else they will go bust. In the long term, I predict that this leads to ever more SEO spam and ever more ads as the internet grows and more and more NLP and AI processing is needed to separate the good results from the bad ones. Filtering gets more expensive => more false positives + need more ads to pay for it.
I've been trying hard (maybe a bit too hard?) to stir up a discussion about people actually paying for the search index, because that would allow them to get the results that they want - private and ad-free - no matter if those results are monetizable with ads or not.
In my opinion, that would make for a nice open source project. In case you're curious:
There's not a lot one can glean about the operation of a search engine from one anecdote; any number of things (including the backing store on which the one copy of this data is indexed being temporarily unavailable) can explain a failure-to-find like this.
But this story does point to both an advantage a meta-search like DDG has and a best practice: different search engines will give different answers. Keep several in your back pocket; don't assume Google is omniscient.
A solution is to move most of the documentation to self-hosted website, leaving only references in the code itself.