hpack | HPACK Compression library for Go | Compression library

After several hours of trial and error, I finally figured out what the problem was, it like many other bugs it turned out to be a stupid one. The order of the tags in the proto file's message has been changed (a new field was added at the top and all of the other fields were pushed downward). The server was using the new definition, while the client was using the old one. When the client tried to call an endpoint, the tags did not match.

All I had to do is re-generate the files for the client stub.

I assume, given when you posted this question, you are using LTS 18.17. Looking at that LTS, it uses mintty 0.1.3. Looking in mintty 0.1.3's cabal file shows a special flag that is enabled by default that means that System.Console.MinTTY.Win32 is not included. The comments in that cabal file say that that flag should be used when using Win32 2.13.1.0 or newer.

However, when I look at LTS 18's configuration in Stackage, I can see that it is using Win32 2.6.2.1, so that flag ought to be set to false for this package to work.

So let's check that in the Stackage build constraints. I see that another flag is being set, and it seems to be an old flag that is no longer used (looks like it was used in an older 0.1.2 version). This must be the problem.

The solution: manually set the flag in your stack.yaml:

I asked around on GitHub and IRC. The solution was to download and use rakudo-pkg to get a newer version of zef. The one that can be installed via apt is too old.

Stack itself is written in Haskell and therefore it accepts the +RTS -p parameter too. To pass the +RTS -p to your prof-exe you should use the -- separator:

Parse log files with a custom parser based on logdissect module.
Assuming a log format as
%(asctime)s - %(levelname)s - %(message)s

The regex to parse it could be
^(\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2},\d{3}) - (INFO|ERROR|WARNING|CRITICAL) - (.*)$

The code to parse

This has happened to me once when I downloaded numpy using pip, but I used a computer with windows, and the solution was to move a file from one folder to another. The solution might be different on a Linux pc. Maybe this post can help you: Python pip install module is not found. How to link python to pip location?

The error is not about the version, that is just a warning. The real error is about a missing "regex.h" header for the underlying C library. That header is almost always present on posix platforms (like linux), but not on Windows. See https://github.com/haskell-hvr/regex-posix/issues/4

Particularly this comment by Paul Johnson:

Correction to the above: you don't need mingw64. You just need to install with the _regex-posix-clib flag enabled (note the underscore).

With plain cabal: cabal install regex-posix -f _regex-posix-clib

In Stack, add the following to your stack.yaml:

It turns out I was on the right track, except I also need to include the so-called internal package DB in the list of package DBs. Distribution.Simple.Build exports a function called createInternalPackageDB, which, unfortunately, we can't use wholesale (since it deletes and re-initializes the internal package DB, in effect deleting the build outputs of previous components); but we can duplicate its behaviour:

Specifying the module under an always false conditional will make hpack's auto-discovery skip it: