Terry T. Student

On Windows, cURL may fail with an error like this:

curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_INVALID_TOKEN (0x80090308) - The token supplied to the function is invalid

Among other causes, this may happen if you treat a HTTP server as HTTPS, e.g. running commands like curl https://cohost.org:80.

Note that "HTTPS" proxy servers commonly respond in clear-text HTTP only; this includes the proxy server implemented by Fiddler Classic, and a command like curl --proxy https://127.0.0.1:8888 https://cohost.org will fail in the same way.

the thing about evangelizing firefox is that there's a lot of talk about making sure the web isn't just chrome and keeping the web open, which is good and important, but also we lose sight of telling people about functionality that chrome doesn't have like:

• did you know that firefox lets you hold shift while right-clicking to prevent websites from hijacking the context menu

Opens a page information window. In the Media tab, there's a list of all images in the page.

Sometimes, a GitHub PR will report that "this branch has conflicts that must be resolved", when plain git would merge the branch with no issues.

When this happens, GitHub may be so stubborn that nothing short of merging the entire base branch into the head branch of the PR will satisfy it and make the PR mergeable. You may not want to do this, but fortunately, there's another way.

If repository permissions allow you to, you can merge the head branch into the base branch locally, and push the base branch manually. GitHub will notice the merge, and automatically close all PRs that would have performed the merge. Remember to pass --no-ff to the git merge command, so that the merge always creates a separate merge commit, like merging the PR from GitHub would.

Example of a full error message:

C:\Program Files (x86)\Windows Kits\8.1\build\WindowsDriver.Win32.props(38,24): A numeric comparison was attempted on "$(_NT_TARGET_VERSION)" that evaluates to "" instead of a number, in condition "'$(IsKernelModeToolset)'=='true' and '$(_NT_TARGET_VERSION)' < '$(_NT_TARGET_VERSION_WIN8)'".

You are missing one of the versions of the Windows Driver Kit (WDK) that match your Visual Studio version. Yes, even if the error refers to an older WDK version. Yes, WDKs specifically match Visual Studio versions, not toolset versions.

Refer to documentation pages Download the Windows Driver Kit (WDK) and Other WDK downloads for the full list of requirements.