bootstrapped | A collection of minified bootstrap themes and extras | Theme library

What does this value represent?

It represents the amount of memory that TCMalloc has told the system that it does not need and that the system may use for other purposes.

Has my memory been freed or not?

No. The OS has decided that making it free just to have to make it used again when the program needs it is a waste of effort and has decided instead to switch it directly from one use to another use in a single step rather than going through twice the effort of making it free just to have to make it un-free to use it.

What can I do to prevent this consumption from growing?

Why would you want to? It just makes it easier if the program needs the memory later, minimizes contention on the system's free list, and has no harmful effects at all. TCMalloc has told the OS (via madvise(DONTNEED)) that the OS may recover the memory and the OS has made the decision that it's not a good idea to make it free just to have to make it used again when it's needed. Do you have some good reason to think the OS is wrong?

It's much easier to just directly transition memory from one us to another in a single step than go through the two steps of making it free just to have to make it used again. The free list can get contended under load and it's much simpler not to use it.

You can force the OS to free it by running some program that consumes a lot of memory and then terminates. That will force the OS to transition the memory to that process and then free it when that process terminates. But this would provide no benefit at all and would be a lot of effort just to eventually increase contention in the memory manager. There is no issue here.

Probably the problem is with your GraphQL query. To create an Item in Monday you need to provide the column_values. Unfortunately in Monday API documentation it's not clearly specified how it should be done. The answer how you need to provision column_values to create_item query can be found in Changing column values with JSON section of Monday API documentation

Please try the following code:

Try parallel = FALSE inside parboot().

Documentation: https://www.rdocumentation.org/packages/unmarked/versions/1.1.0/topics/parboot

Have you seem this example - https://github.com/spring-projects-experimental/spring-native/tree/main/samples/cloud-function-aws?

Also, there were issues with that new CustomRuntimeEventLoop that have already been addressed, so consider using the latest snapshot.

y_pred must be a single number, giving the probability of the positive class p1; currently your y_pred consists of both probabilities [p0, p1] (with p0+p1=1.0 by definition).

Assuming that your positive class is class 1 (i.e. the second element of each array in y_pred), what you should do is:

Your bootPearson() function does not do what you presumably want it to do. Right now, it calculates seven different correlations but only returns the last one - everything else gets calculated and discarded. In R, functions only return the last result created in the function body. You may want to read up on how R functions work.

The solution is simple: just change bootPearson() to create and return a single object - namely, a vector of length 7 that contains the seven correlations you calculate. Concatenate them into one vector using the c() command:

In order to meet this need this is what I cobbled together. Maybe it will help someone else. Criticism welcome.

/app/node_modules creates a directory inside the container and the Docker Engine automatically creates an anonymous volume for this (i.e. it should will probably be empty). This is from the docs about the compose file spec in the "Short Syntax" section.

./frontend/node_modules:/app/node_modules creates a bind mount. The ./frontend/node_modules directory from your host machine will be shared with the container.

In response to followups regarding why using /app/node_modules works but the other syntax does not:

Your yarn install command creates a node_modules folder inside the Docker image. This created folder conflicts with the existing frontend/node_modules folder you have locally when trying to run with ./frontend/node_modules:/app/node_modules. When you specify /app/node_modules, the container uses the directory created during the build step.

Closing the loop on this. In ionic v4.x, this isn't possible as it appears the overlay components are registered at runtime. While can be used with JIT-compiled templates to preload the scripts where needed, it will fail when used with AOT-compiled templates. So the solution for now is to programmatically present then dismiss a modal during the bootstrap process or as early as can be done after IonicModule is available.