NetHack VS Polly

download NetHack sources (https://github.com/NetHack/NetHack -> Code -> Download ZIP, unpack them on your computer)

My configuration of Eglot is simple: (use-package eglot :hook (c-mode . eglot-ensure)). And it works for a single c file. But when I use this setup to read the code of NetHack, it doesn't work for linting and definition finding (M-.), even though eglot connection has no problem. I observed the same problems when reading the code of SQLite. Some specific problems I observed:

Since nethack 3.1.0, the source for nethack's "bestiary" has been dat/data.base, in plain text, processed into a file named "data" when building the program. The unprocessed file intended for the nethack's next version can be seen at https://github.com/NetHack/NetHack/blob/NetHack-3.7/dat/data.base (it's quite long).

I am not really 100% sure what you are looking for. Are you looking for the actual picture? It is built during compilation from this uuencoded file https://github.com/NetHack/NetHack/blob/NetHack-3.7/win/win32/splash.uu

xNetHack is based on NetHack 3.7.0, and there was a bug (now fixed) in NetHack 3.7.0 that caused stair destinations to be messed up after a game is recovered. I wonder that has happened here: perhaps you are playing a version of xNetHack that inherited the bug from NetHack 3.7.0, this is a recovered game.

They won't be afraid of music in 3.7.

This is a bug that was fixed in the upcoming 3.7, in this commit. Basically, if the random filler created a space that was made inaccessible by the fixed level design getting overlaid on top of the random filler, a door could be created to make that space accessible.

There is not a comprehensive list of changes in existence. This one comes close but doesn't contain everything https://github.com/NetHack/NetHack/blob/NetHack-3.7/doc/fixes3-7-0.txt

I have an open github issue requesting that intrinsic invisibility be made only temporary, not permanent. That would make the invisibility mechanic more interesting since you could decide multiple times per game whether you want it, and extrinsic invisibility items would become more useful.

In our applications, we should wrap all requests to remote services in code that implements a retry policy that follows one of the strategies I listed earlier. If you are a .NET developer like myself, you may be familiar with the Polly library. Golang has a library called Retry, and there are numerous third-party libraries for Python and Java.

Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?

D'Oh! Sorry, not PolySharp. I meant Polly. Too many similarly-named libraries!

Everywhere I've worked with AGs, we've worked with the application team to add retry logic to help make things a bit more seamless to end users. There are libraries out there that can make this pretty easy - Polly is one that I've used a few times, but there are others.

Fallacy 1: The network is reliable. If system 2 works perfectly well, but is not accessible for service 1 due to network issues, service 2 is still unavailable. This is why timeouts, service breakers and retry policies exist. A great tool for .NET to handle common network issues is Polly, but even when using a tool like this, the network is still not completely reliable.

I see. Then I don't have any better idea right now, but I do want to suggest that if your script is mostly API calls and you want to be able to deal with failures then take a look at the polly library: https://github.com/App-vNext/Polly

Runs in containers nicely, has good integration with Kafka, RabbitMQ, gRPC, etc. for Microservices communication. Implements resiliency patterns you'd want in Microservices via Polly. Has a decent Dependency Injection framework built in by default.

It's in no way hidden. But I use Polly all the time.

Depending if the sender or the reciever is down, you can also try Polly http://www.thepollyproject.org/