WSS | Convert nested CSS into usable HTML | Style Language library

This is normal. I don't know why binance does not fix this, but as API doc say you should ignore it.

How to manage a local order book correctly

If the quantity is 0, remove the price level.

You have to deal with the namespaces in your xml. So try this instead:

I think there are a number of issues here, more specifically with the Generated Code for the XML.

In Visual Studio, I created a new Class and copied your XML content and used Edit -> Paste Special -> Paste XML as Classes.

Here's the generated code from that exercise:

The error might be due to the notorious assembly version mismatch problem on Tizen devices.

https://developer.samsung.com/tizen/blog/en-us/2020/02/17/assembly-loading-problem-in-tizen-net-applications

Explanation: Tizen 4.0 devices come with the pre-installed System.Threading.Tasks.Extensions.dll assembly of the version 4.1.1.0, but the latest Microsoft.AspNetCore.SignalR.Client nuget package depends on System.Threading.Tasks.Extensions.dll of 4.2.1.0. So the app will break because the runtime host always resolves the pre-installed assembly first. (The same app will run without problem on Tizen 5.5 devices because the pre-installed assembly version is 4.3.1.0.) However, I'm not sure why Microsoft.Extensions.DependencyInjection.Abstractions.dll couldn't be resolved since it's not part of the .NET Core runtime and not pre-installed with Tizen devices.

In short, you may add the following event handler your app's Main() and check if the problem persists.

I had a look at your pipeline grok patterns. Taking cue from that, I modified the IP section a bit.

it is normal thing developing manifest version 3 extensions. Chrome is becoming a browser that is everything but light and this is partly due to the dozens of extensions the user installs. Thus Google introduced service worker in extensions in order to free up some memory whenever possible. SW is activated when necessary and then goes to sleep until the moment it's awakened to perform a new job.

Said this,

1. "persistent": true in manifest is useless and could generate an error.
2. we have to realize that when SW becomes inactive all variables and objects defined in this script will be lost unless we plan to save them somehow in a persistent storage. Normally, the asynchronous chrome.storage API are used to save variables \ objects used in the SW.
3. If you cannot allow SW become inactive (for some important reason) you could use a "dirty" technique that bypasses this "restriction". This technique consists in opening a long-lasting communication channel and sending fictitious messages between SW and any browser tab. For more details on this technique read this thread: Persistent Service Worker in Chrome Extension

Update

You have created two daemon processes. They will terminate when all non-daemon processes have terminated, which in this case is the main process, which terminates immediately after creating the daemon processes. You are lucky that even one of the processes has a chance to produce output, but why take chances? Do not use dameon processes. Instead:

You are doing the correct thing to send the message: socket.next(...), however you need to ensure you are subscribing to your socket. From the rxjs docs:

Note that at least one consumer has to subscribe to the created subject - otherwise "nexted" values will be just buffered and not sent

It looks like you are re-implementing features already provided by RxJS WebSocket. You don't need a connect() method nor a close() method. This is because the socket connection is automatically made when there is a subscriber, and closed when there are no subscribers.

Also, you don't need to have a separate MessagesSubject, just define messages$ from your socket$.

Your service could be simplified to this:

This is a problem with the ssl certificate. For some reason, going from browser to node.js server using a self-signed ssl certificate is fine, but going from node.js server to node.js using a self-signed ssl certificate is not.

I created a brand new ssl certificate and then in the client server, instead of: