Natty | New Answers to Old Questions tool | Chat library

You are not supposed to alter your changesets. You're supposed to only add new changesets. Altering the changesets is an anti-pattern.

Is you need to add changes to your database schema, you should keep the existing changesets and write new ones.

If you don't want to make your changeLog file too massive, then create a parent changeLog file and some multiple child changeLog files (see include or includeAll tags). You can create a new child changeLog file like every month, or every week, or by some other logic.

And if you really want to trim your changeLog, I suggest you read "Trimming Changelogs" article first.

there was an error on documentation, the developer of the libs suggest me to change:

curl 'http://127.0.0.1:8000/api/test1' --data-binary '{"jsonrpc":"2.0","method":"pharmacies@ping","params":["innings": "out"],"id" : 1}'

to

curl 'http://127.0.0.1:8000/api/test1' --data-binary '{"jsonrpc":"2.0","method":"pharmacies@ping","params":{"innings": "out"},"id" : 1}'

so changing [] to {} in "params" make it works!

consider changing host entry 127.0.0.1 to localhost or even the IP address of the server.

First of all, there's an issue with your question's first statement.

Unity is single-threaded

Unity is not single-threaded; in fact, Unity is a multi-threaded environment. Why? Just go to the official Unity web page and read there:

High-performance multithreaded system: Fully utilize the multicore processors available today (and tomorrow), without heavy programming. Our new foundation for enabling high-performance is made up of three sub-systems: the C# Job System, which gives you a safe and easy sandbox for writing parallel code; the Entity Component System (ECS), a model for writing high-performance code by default, and the Burst Compiler, which produces highly-optimized native code.

The Unity 3D engine uses a .NET Runtime called "Mono" which is multi-threaded by its nature. For some platforms, the managed code will be transformed into native code, so there will be no .NET Runtime. But the code itself will be multi-threaded anyway.

So please, don't state misleading and technically incorrect facts.

What you're arguing with, is simply a statement that there is a main thread in Unity which processes the core workload in a frame-based way. This is true. But it isn't something new and unique! E.g. a WPF application running on .NET Framework (or .NET Core starting with 3.0) has a main thread too (often called the UI thread), and the workload is processed on that thread in a frame-based way using the WPF Dispatcher (dispatcher queue, operations, frames etc.) But all this doesn't make the environment single-threaded! It's just a way to handle the application's logic.

Please note: my answer only applies to such Unity instances that run a .NET Runtime environment (Mono). For those instances that convert the managed C# code into native C++ code and build/run native binaries, my answer is most probably at least inaccurate.

You write:

When you do something on another thread, you often use async/wait since, uh, all the good C# programmers say that's the easy way to do that!

The async and await keywords in C# are just a way to use the TAP (Task-Asynchronous Pattern).

The TAP is used for arbitrary asynchronous operations. Generally speaking, there is no thread. I strongly recommend to read this Stephen Cleary's article called "There is no thread". (Stephen Cleary is a renowned asynchronous programming guru if you don't know.)

The primary cause for using the async/await feature is an asynchronous operation. You use async/await not because "you do something on another thread", but because you have an asynchronous operation you have to wait for. Whether there is a background thread this operation will run or or not - this does not matter for you (well, almost; see below). The TAP is an abstraction level that hides these details.

In fact, does the code above literally launch another thread, or does c#/.Net use some other approach to achieve tasks when you use the natty async/wait pattern?

The correct answer is: it depends.

• if ClientWebSocket.ConnectAsync throws an argument validation exception right away (e.g. an ArgumentNullException when uri is null), no new thread will be started
• if the code in that method completes very quickly, the result of the method will be available synchronously, no new thread will be started
• if the implementation of the ClientWebSocket.ConnectAsync method is a pure asynchronous operation with no threads involved, your calling method will be "suspended" (due to await) - so no new thread will be started
• if the method implementation involves threads and the current TaskScheduler is able to schedule this work item on a running thread pool thread, no new thread will be started; instead, the work item will be queued on an already running thread pool thread
• if all thread pool threads are already busy, the runtime might spawn new threads depending on its configuration and current system state, so yes - a new thread might be started and the work item will be queued on that new thread

You see, this is pretty much complex. But that's exactly the reason why the TAP pattern and the async/await keyword pair were introduced into C#. These are usually the things a developer doesn't want to bother with, so let's hide this stuff in the runtime/framework.

@agfc states a not quite correct thing:

"This won't run the method on a background thread"

NioEventLoopGroup uses worker threads to utilize multiple CPU cores. As per the no-argument constructor javadoc:

NioEventLoopGroup()

Create a new instance using the default number of threads, the default ThreadFactory and the SelectorProvider which is returned by SelectorProvider.provider().

The deafult thread count as per MultithreadEventLoopGroup will be twice the number of available processors:

My guess would be that the storm.log.dir variable isn't being correctly set for the worker JVM. Remember that the JVM you start when running storm jar isn't the same JVM that will run your topology.

In order to set VM options for your workers, you can use the worker.childopts variable in storm.yaml to set options globally (you might want to make sure to copy over the defaults from https://github.com/apache/storm/blob/v1.1.1/conf/defaults.yaml#L171 if you do this), or topology.worker.childopts in your topology config to set them per topology.

For example, I get logs printed to E:\testLogs with the following config:

storm.yaml

As @AlexisKing notes, the nAdd in the type signature for foo is just treated as another type variable (like m or n) and Haskell doesn't tie it back to the definition of the function nAdd.

In Haskell, you can't apply term-level functions (like nAdd) to types. Instead, you need to use type families. If you define a type-level "function" NAdd as a type family:

This is happening because of cookie(document.cookie = e;). cookie is maintaining the user data as and when user requests for the same resource second time the data already presents in cookie and the same is being sent to the server and hence the server is sending the HTTP 500 Error.