Dlog | Host log detection based on deep learning | Machine Learning library

This appears to be caused by messages with no text content (embed/image upload, etc)

When a message is sent with no text content, msg.content will be set to "".

As a result, the field's value is then an empty string and throws the error.

To fix this, add a check for the content:

The way you've found in tutorial does not restart the whole JVM process, it closes the application context and re-creates it. This means that all the beans get loaded again which is logically equivalent to restart as far as all the objects are managed by Spring or course.

There as also a way of making such a restart without writing custom code - use Spring Boot's actuator that has a restart endpoint. You can invoke the endpoint and the application will be restarted in the same sense as you've described. See this tutorial for example there are many others.

In both of the ways, there will be the same JVM process (jvm does not restart), so both classpath and JVM parameters will remain just the same (do not change).

So if you want to restart the JVM you can wrap the long command into some sort of script (like bash if you're working on linux, or *.bat file for windows for example).

Other than that spring boot can't help much - from this perspective its a regular java application.

No, the logs won't be stripped in Release. The OSLogType just describes the type of message to filter in Console.app, debug type messages will still be logged in production.

The correct way to disable OS logging in a scheme is to edit the Release scheme itself:

Set the OS_ACTIVITY_MODE environment variable to disable in your scheme, then you will not see any logs for your app in the console.

This won't work for Archived apps though, but you should never really disable logging in production anyway. If you really want to, it’s possible to use preprocessor directives in this case.

When upgraded to 1.16, you can convert your resources.

As written in the blog you can use kubectl convert. The migration recommend convert. See kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16

you should open port on run docker :

Add this rule with your css:

So you map the port of 80 on your container to 5001 on the host right? If you then want to connect to the nginx-container over the same network, you should try to connect to port 80 (that' presumably the only "exposed" port that container has).

So this should work from your risk-analysis-XXXX1 container:

http://ngnix-server:80

You want the NLog Config Variables to behave in two ways:

1. When editing the NLog.config file, then it should discard the existing NLog Config Variables and take those when reloading the updated NLog.config.

   • This requires that you have configured KeepVariablesOnReload=false (default)

     • It would be easier if you had included NLog.config in your question. Instead of having to guess.

2. After the reload of the NLog.config then there is one NLog Config Variable (${var:regionName}) that you would like to keep.

   • Because you have configured KeepVariablesOnReload=false (default) then I guess you have hooked into LogManager.ConfigurationReloaded-event and re-assigning it manually.

     • It would be easier if you had included the logic for dynamic assigment of NLog config variable in your question. Instead of having to guess.

The LogManager.ConfigurationReloaded-event is called after the reloaded NLog Config has been assigned and initialized. So any logging happening until having dynamically re-assigned the ${var:regionName} will get empty value. See also https://github.com/NLog/NLog/pull/3954 and https://github.com/NLog/NLog/pull/3952

The current work-around is stop using LogManager.ConfigurationReloaded-event and instead just use NLog Global Diagnostic Context (GDC) for the single NLog Config Variable that needs to be restored on every reload. So it becomes ${gdc:regionName} and you assign it like this (once at startup):

So, it seems I was wrong to close the connection. I assumed that, when getting a connection from a pool if I "close" the connection it returned it to the pool. Seems it closed it but kept it in the pool (maybe left borrowed, maybe just unusable, didn't investigate that far). It seems I need instead to return it to the pool, and to keep a reference to the pool for that.

I had a function (actually an injected service) that handles the pool and returns a connection. What I was trying to do was: