idevice | bluebox security open source : Ruby FFI bindings

Why didn't any one tell me! ... ;-) (ok, the links provided in the comments above eventually lead me to this)

Summary

Use Func<> instead of delegates and .Factorys. This was my big misunderstanding.

Refactored code

The program start remains the same:

The GraphServiceClient is being instantiated for each call. This in turns instantiates one OkHttpClient per GraphServiceClient, which in turns creates a connection pool. Because of the way connections are managed by OSes (they are kept open for a period because closing and opening a connection is a costly operation), this will lead to a port exhaustion on the machine.
The next requests that come in after no more ports are available, block waiting for a port to free and for a connection to be available, and eventually timeout with the exception you are seeing.

To fix that issue:

• Make sure your GraphClient class is instantiated once throughout the lifecycle of your application
• Implement some lazy loading for the getGraphServiceClient method, so it "caches" a client in a field and returns that if the value is not null instead of creating a new one for each call.

Injecting an IEnumerable of dependencies is a pretty common thing with DI, so that seems perfectly reasonable to me.

For example Microsoft uses the same pattern to inject retrieve all the IHostedService's to call StartAsync/StopAsync. Only difference is they directly retrieve the dependency from the IServiceProvider instead of injecting it into a constructor.

Only thing I'd change is to use a foreach loop instead of a for loop with the IEnumerable:

According to the C# specification, if there is no static constructor, there is no guarantee when a static field is exactly initialized, only that this happens before first use.

15.5.6.2 Static field initialization

The static field variable initializers of a class correspond to a sequence of assignments that are executed in the textual order in which they appear in the class declaration (§15.5.6.1). Within a partial class, the meaning of "textual order" is specified by §15.5.6.1. If a static constructor (§15.12) exists in the class, execution of the static field initializers occurs immediately prior to executing that static constructor. Otherwise, the static field initializers are executed at an implementation-dependent time prior to the first use of a static field of that class.

If there is however a static constructor, it is guaranteed that all static fields are initialized before it runs, which is in turn guaranteed to happen if you instantiate an object of the class or access a static member for the first time.

So to force the initialization of your field, you can add a static constructor:

State shouldn't be modified directly, which is what you're currently doing now in your .map() method by updating the objects. TS is trying to tell you not to do this by making your objects read-only.

Instead, you can create a new object with all the properties from item (done using the spread syntax ...), along with a new overwritting property selected, which will use the negated version of the item's currently selected item if the id matches the event's data item id, or it'll keep the original selected value:

All you need is python default csv and json.

A simple example for json

The main big problem is that you want to throw from the dtor. https://www.kolpackov.net/projects/c++/eh/dtor-1.xhtml has a nice explanation of why this does not play nicely with the language and its idioms.

In general, if you expect that a device can fail at shutting down, then you should probably handle this part explicity, because it not something that happens "exceptionally".

For example, you could have the destructor try to gracefully shut off the device, and in case of errors (or exceptions), apply a force shut off. then, if the user of your system wants to handle the case of a device that can't shut off, he can still call shutoff directly.

Finally, modeling from real world objects is just a first draft of your class design. don't worry to notstick to what the real world object do, if it helps to get a more practical design and a better UX.

From the exception stack traces I can see that RoboVM detected your device before compilation (as it got your UDID), compiled project and failed during deployment while trying to get device by UDID.

This happens if you device is not connected anymore or connected not over USB. E.g. over wifi.

Probably you should uncheck Connect via network for your device (accessable by Xcode->Windows->Device and Simulator menu) and connect it using USB.