formatter | Phug Formatter contains a baseclass for Formatters

Use the date-time API.
(The code should be self-explanatory.)

Although they 'don't exist', can Format.ps1xml files be created/used in versions of PowerShell greater than 5.1?

• Yes; in fact any third-party code must use them to define custom formatting.

  • That *.ps1xml files are invariably needed for such definitions is unfortunate; GitHub issue #7845 asks for an in-memory, API-based alternative (which for type data already exists, via the Update-TypeData cmdlet).

• It is only the formatting data that ships with PowerShell that is now hardcoded into the PowerShell (Core) executable, presumably for performance reasons.

is there some better practice for suggesting to PowerShell how a certain function should format returned data?

The lack of an API-based way to define formatting data requires the following approach:

• Determine the full name of the .NET type(s) to which the formatting should apply.

  • If it is [pscustomobject] instances that the formatting should apply to, you need to (a) choose a unique (virtual) type name and (b) assign it to the [pscustomobject] instances via PowerShell's ETS (Extended Type System); e.g.:

    • For [pscustomobject] instances created by the Select-Object cmdlet:

React hooks are only valid in React functional components, not in any callbacks, loops, conditional blocks. If you need the location data in the callback it needs to be passed in.

From what I can tell it seems you need to move the columns.js code into the main component so the location values can be closed over in scope.

Ok so turns out I'm an idiot.

The problem was this: "prettier.resolveGlobalModules": true

This has to be set to false, i cannot stress this enough, do not set it to true.

Correct: "prettier.resolveGlobalModules": false

Wrong: "prettier.resolveGlobalModules": true

I came to this conclusion after resetting every setting and trying it until i found out the reason it didn't work before.

To tomstone a message after compacted, current time - compacted time should be grater than delete.retention.ms. It is defaulted by broker config log.cleaner.delete.retention.ms. So in your case it is zero. But this is applied for compacted logs.

But to compact kafka messages in logs, not compacted / compacted + not compacted ratio it is called dirty ratio should be greater than config min.cleanable.dirty.ratio, defaul = is 0.5. Active segment is not considered for this calculations.

So in your scenario, they are not still compacted. That is why they are remaining in the topic.

For more info about compaction and tombstone refer this

There is something wrong either with the String you are providing to the parse() method. It seems there is a zero-width null character bug in your String. That is your string has a Unicode u+FEFF Byte order mark character at the beginning and end of the string, which is known as a “Zero-width null character”. It's not whitespace, so trim() will not remove it. For validation just print the length of your String and observing that it would be 2 longer than expected.

How to resolve: Trim these characters. You can write a function to trim before parse it, something like below:

Opened a pr https://github.com/Shelkovenkov/defichain-income/pull/5

The problem is that you're bootstrapping your application twice.
I'm sure you want to have only one version of this code in src/main.ts and remove it from src/app/app.module.ts.

it seems I need a way to turn self-owned reference to 'static lifetime.

That's what Rc is for. Define the struct as EmailTemplateMessageBuilder(Rc), and define translator as self.0.clone(). The clone() only clones the pointer and increases the reference count, so it's cheap. Finally, make the closure move, so it owns all captured data.

The error message already gives you some hint here:

System.NotSupportedException: The collection type 'Newtonsoft.Json.Linq.JObject' is not supported. at System.Text.Json.JsonPropertyInfoNotNullable`4.GetDictionaryKeyAndValueFromGenericDictionary(WriteStackFrame& writeStackFrame, String& key, Object& value)

As you can see, there is some Newtonsoft.Json.Linq namespace, and a System.Text.Json namespace.

Starting with ASP.NET Core 3.0, the default serializer for JSON was changed from Newtonsoft.Json to the new serializer that is built into .NET Core: System.Text.Json. There is very detailed documentation on the differences between these two serializers and how to migrate your code to System.Text.Json. But the summary here is that System.Text.Json is—by design—more limited than Newtonsoft.Json and it will not be able to serialize directly from or to those JObject or JArray objects.

Fortunately, for applications that rely on the behavior of Newtonsoft.Json or otherwise require some of its flexibility, there is a way to reconfigure the ASP.NET Core application to continue using Newtonsoft.Json for JSON serialization.

To do that, you can follow the migration guide for ASP.NET Core 3.0. Essentially you will have to reference the NuGet package Microsoft.AspNetCore.Mvc.NewtonsoftJson and then call AddNewtonsoftJson() on the MVC builder in your ConfigureServices method. For example: