blog-example | example files in the blog include Kubernetes | Microservice library

Not sure if this will be an answer, but the errors I already see are:

• If your react app doesn't make use of PHP (and I suppose it doesn't) why are you use location ^~ /blog/ { ... } having a PHP handler below this block? This way no request for /blog/any/path/file.php ever reach that PHP handler. Use simple location /blog/ { ... } prefix location or move the PHP handler inside the location ^~ /blog/ { ... } making it nested location (preferred).
• If your directory where the WP is located is /var/www/example.org/blog and your URI pefix is /blog/ you'd better use root /var/www/example.org; instead of alias /var/www/example.org/blog;. It those string doesn't match, add the trailing slash at the end of the alias directive argument: alias /var/www/example.org/blog/;
• You are using try_files directive incorectly, the last argument supposed to be an URI, so to redirect all the requests to WP index file you should use try_files $uri $uri/ /blog/index.php?$args;
• Your PHP handler uses global /var/www/project/app/functions/build root instead of WordPress one (if you'd make the PHP handler nested location, this one would gone automatically).

Not sure that's all, but lets start from fixing these errors.

Update

The final working configuration was added by OP as the original question update.

As others have noted, ConfigureAwait(false) is less necessary with modern code (in particular, since ASP.NET Core has gone mainstream). Whether to use it in your library at this point is a judgement call; personally, I still do use it, but my main async library is very low-level.

especially given the fact the code after await Do1Async().ConfigureAwait(false) will continue on exactly the same conditions as the code after await ContextSwitcher.SwitchToThreadPool() ?

The conditions aren't exactly the same - there's a difference if Do1Async completes synchronously.

Why is the 1st option considered a good practice and this one isn't

As explained by Stephen Toub, the "switcher" approach does allow code like this:

You need to use pako.Inflate in your frontend.
Additionally you need to remove the 4 bytes size you added to the front of the gzBuffer in the frontend before decoding.

Something like this should work:

I encountered the same issue, and I think it was rectified by changing

.equals("x", Type.LONG,

to

.equals("x",PredicateLeaf.Type.LONG

On using this, the reader seems to return only the batch with the relevant rows, not only once which we asked for.

You are trying to generate entities that use relationships in a NoSQL project. Relations are not supported by JHipster for NoSQL projects. For more information on how JHipster handles relationships, see the docs on Managing Relationships:

Relationships only work when JPA is used. If you choose to use Cassandra or MongoDB, they won’t be available.

Removing the relationships allows the JDL to be imported. You can also try with a project using an SQL database option.

The JDL error message is more verbose in future versions of JHipster (v4.10.0+) so you won't need to use the --debug flag in the future.