disposable | Decorators on top of your ORM layer

In my extension, I'd like to register an event listener when the user issues a command but unregisters the listener (or update the listener to something else) when the user issues another command.

For instance, at the end of command A, I register window.onDidChangeActiveTextEditor to be something (in my case I registered it to the command A handler). At the end of command B, I'd like to unregister this registration. I understand window.onDidChangeActiveTextEditor will return a Disposable, but I don't know how I would pass this disposable to command B.

My code structure is this:

How I can Create a timer component in Blazor and start it from outside of component or other page. My component code is as below:

I have a custom DocumentsProvider implementation that works flawlessly for a user to choose photos or videos for use by the app, as long as the Android API is 26 or greater. Using APIs 21-25 I get a security error similar to what is described in this SO post. However I am already doing everything mentioned in that post as a solution.

Manifest entry:

I am having trouble wiring up identity into Blazor server with ASP.NET Core identity. Specifically getting the correct logged in state in Blazor pages (while I am getting them from the Blazor pages).

I think it's related to some of the startup being initialized in another project - but not sure how to debug it or what the solution is to be able to get the logged in state correctly.

Reproduction steps and link to GH repo below as a POC.

Background

I'm porting over the clean-code project by JasonTaylor from Angular / ASP.NET Core to a Blazor server project with ASP.NET Core Identity.

Issue

The application runs up and I can browse the pages when I register I can see logged-in state in the identity-based default pages but in the Blazor pages that use the AuthorizeView (e.g. LoginDisplay.razor) it's not aware of being authorized.

Startup in the Blazor project:

I have entry fields in a Xamarin Forms page that I want to trigger a ReactiveUI command when the user is finished entering text into them. I am using ReactiveUI.Events.XamForms and am trying to trigger a command based off of the Unfocused event, but I am not sure how to set up the command to get that to work.

Here is my XAML:

I face the following problem with GEKKO: some parameters (.Param) are changing (others not) when solving a model and I cannot determine why.

Background: I am currently trying to translate code from EViews (see gennaro.zezza.it) to python. I use GEKKO to simulate a system consisting out of 11 equations (for now). I do want to use parameters (instead of constants which seem to work perfectly fine) as I need to ('exogenously') change their value over time (and thus need an array).

Example: In the following example, an 'economic system' reacts to new government expenditures. Here, I particularly face problems with "m.alpha1" and "m.alpha2" - if they are introduced as ".Param" their value will change to 1.0 (instead of 0.6 and 0.4) when solving the model. How can I stop GEKKO from doing this? (Again, I want to be able to change, e.g., alpha1 to 0.7 after time x. E.g., lower and upper bounds won't help here.)

Thanks for your help!!

Code:

I'm using the latest C# client and attempting to write data to InfluxDB using the lineprotocol.

This works:

I have two sequential API calls so I decided to use RxJava flatmap to accomplish it as below code,

I have a bunch of instances, each having a unique tempfile for its use (save data from memory to disk and retrieve them later).

I want to be sure that at the end of the day, all these files are removed. However, I want to leave a room for a fine-grained control of their deletion. That is, some files may be removed earlier, if needed (e.g. they are too big and not important any more).

What is the best / recommended way to achieve this?

May thoughts on that

• The try-finalize blocks or with statements are not an option, as we have many files, whose lifetime may overlap each other. Also, it hardly admits the option of finer control.

• From what I have read, __del__ is also not a feasible option, as it is not even guaranteed that it will eventually run (although, it is not entirely clear to me, what are the "risky" cases). Also (if it is still the case), the libraries may not be available when __del__ runs.

• tempfile library seems promising. However, the file is gone after just closing it, which is definitely a bummer, as I want them to be closed (when they perform no operation) to limit the number of open files.

  • The library promises that the file "will be destroyed as soon as it is closed (including an implicit close when the object is garbage collected)."

    How do they achieve the implicit close? E.g. in C# I would use a (reliable) finalizer, which __del__ is not.

• atexit library seems to be the best candidate, which can work as a reliable finalizer instead of __del__ to implement safe disposable pattern. The only problem, compared to object finalizers, is that it runs truly at-exit, which is rather inconvenient (what if the object eligible to be garbage-collected earlier?).

  • Here, the question still stands. How the library achieves that the methods always run? (Except in a really unexpected cases with which is hard to do anything)

In ideal case, it seems that a combination of __del__ and atexit library may perform best. That is, the clean-up is both at __del__ and the method registered in atexit, while repeated clean-up would be forbidden. If __del__ was called, the registered will be removed.

The only (yet crucial) problem is that __del__ won't run if a method is registered at atexit, because a reference to the object exists forever.

Thus, any suggestion, advice, useful link and so on is welcomed.