limbo | lightweight framework for Gaussian processes | Analytics library

If you want to display the contents of a list with some kind of special formatting, do not try to "fix" the natural string representation of the list. Instead, write your own code to build the string, inserting data from the list in the appropriate places. You can use string formatting to make this easier.

I assume you have the following actual data structure:

When exactly does segmentation fault happen (=when is SIGSEGV sent)?

When you attempt to access memory you don’t have access to, such as accessing an array out of bounds or dereferencing an invalid pointer. The signal SIGSEGV is standardized but different OS might implement it differently. "Segmentation fault" is mainly a term used in *nix systems, Windows calls it "access violation".

Why is the process in undefined behavior state after that point?

Because one or several of the variables in the program didn’t behave as expected. Let’s say you have some array that is supposed to store a number of values, but you didn’t allocate enough room for all them. So only those you allocated room for get written correctly, and the rest written out of bounds of the array can hold any values. How exactly is the OS to know how critical those out of bounds values are for your application to function? It knows nothing of their purpose.

Furthermore, writing outside allowed memory can often corrupt other unrelated variables, which is obviously dangerous and can cause any random behavior. Such bugs are often hard to track down. Stack overflows for example are such segmentation faults prone to overwrite adjacent variables, unless the error was caught by protection mechanisms.

If we look at the behavior of "bare metal" microcontroller systems without any OS and no virtual memory features, just raw physical memory - they will just silently do exactly as told - for example, overwriting unrelated variables and keep on going. Which in turn could cause disastrous behavior in case the application is mission-critical.

Why is it not recoverable?

Because the OS doesn’t know what your program is supposed to be doing.

Though in the "bare metal" scenario above, the system might be smart enough to place itself in a safe mode and keep going. Critical applications such as automotive and med-tech aren’t allowed to just stop or reset, as that in itself might be dangerous. They will rather try to "limp home" with limited functionality.

Why does this solution avoid that unrecoverable state? Does it even?

That solution is just ignoring the error and keeps on going. It doesn’t fix the problem that caused it. It’s a very dirty patch and setjmp/longjmp in general are very dangerous functions that should be avoided for any purpose.

We have to realize that a segmentation fault is a symptom of a bug, not the cause.

Basically, I was trying to read broken JSON, as Felix mentioned JSON cannot contain literal line breaks.

Solution: use https://www.npmjs.com/package/jsonrepair module. It detected the bad lines and fixed them, this is likely what google does (some sort of JSON repair).

PS: I tried https://www.npmjs.com/package/json-fixer without success

You should always provide a minimal working example. Otherwise we can only guess.

I've converted your code into this working example. It may or may not reflect what you are really trying to do:

I have exactly your problem. The query takes so long to run, the controller cannot respond back to the browser. So, the browser times out.

I tried 3 different ways to fix this.

The easy way out: I am using Tomcat. So, I set the connection timeout value longer. The connectionTimeout variable is in the server.xml file.

The lazy way out: I don't know if Grails has any sort of Message Queue function or not. So, I rolled my own. When I click the submit button to run a very long update query, the action will INSERT INTO a sort of update command in a database table along with the state. I then use Quartz to schedule maybe every 10 seconds to read this table to check the state. If the state is NEW, I change the state to "IN PROGRESS". And then I let the trigger to run the update query in the background. After it finish, I change the state to FINISH.

So, the action is just adding a row to the database and then respond back the view that says something like... You have issued the request. The system will process your request in a few moment.

The hard way out: I went over all my SQL and functions in the actions to calculate the time it will take the SQL and codes to finish the query. I then rearrange/rewrite the functions and procedures. I am not good enough for this. If I can get to O(n), that will be enough for me.

If you need the handle the mono-gram case from Yake just pass the output through a filter that adds the n-grams to the result list only if there is a space in the first element of that tuple or if the str.split() of that element results in more than 1 sub-element. If you're using a function and applying it to the dataframe, include this step in that function.

I don't know Datagrip so I can't help.

However, see if this helps with

what the heck is the open ?

Looks like a refcursor business. The following code uses the same open you saw in your code. It fetches employees that work in department whose deptno is equal to the result local variable's value.

--How was this resolved?--

After doing some digging, I came across an answer in this article (I am forever grateful) and forged a solution using it.

Here's a sample of my XAML content page for context:

Your stackblitz doesnt allow ngFor so the setup must be wrong. Here is what I think is the problem:

Your app has a weird data flow, when you subscribe to your observable, you wont receive any data until something calls next on your subject. What you seems to be doing from what I've seen in your stackblitz is:

1. Call to update which is going to to give a value to your Subject
2. You subscribe and its already too late

You can't get the last value from a subject and since you subsribed too late, your console.log from the subscribe is never actually doing anything. You are seeing the console.log related to your update(the one from hello component)