nbb | .Net Building Blocks | Microservice library

What about this ?

For each step, I group on column1, then set column4 as index and work on the transpose matrix with your criteria. Note that I've extrapoled a bit on your criteria to match your attended results (I hope it is correct but you will have to check that).

Note also that I have kept each step separate to make it easier to read. But it would be more efficient to make the grouping/indexing/transposing in one shot and work on your algorithm from there.

The 2-character sequence '\'+'n' is not treated as an escape sequence in Delphi (only in C/C++, and only in compile-time literals, not in runtime data). You will have to replace the sequence manually, such as with StringReplace(), eg:

What that machines is expecting is wrong. In JSON any newline data inside a value must be escaped, and \n in the string is the correct way to do it. This is the fault of the receiver's expectations.

A "real" newline would result in an invalid JSON document and most parsers will flat-out reject it.

On the receiving end JSON deserializer can deal with \n encoded strings. If your receiver requires newlines it's broken and needs repairing. If you can't repair it then you're committed to sending busted up, malformed JSON-ish data that's not actually JSON and your broker is fully justified in trashing it.

I guess strictly speaking this answer doesn't really answer your question, since I'm not trying to figure out where your error is. But I'm convinced that if you change your coding style you won't encounter such difficult to debug errors any more.

As mentioned in my comments, your code will become must clearer and easier to debug if you split the signal up properly. I.e. don't create one giant signal for everything.

VHDL has arrays and records, use them, they won't make your circuit any larger, but the code will be much easier to reason about.

It's been a while since I actually wrote VHDL, so the syntax below might contain typo's, but hopefully the idea behind the code is clear:

Your problem is the \s* at the end of the non-capturing group; this is being greedy and absorbing the vertical white-space at the end of the line containing bb = 22 and preventing the group matching again on the line with cc = 33 in it. Changing that to [\t\v\f ] (or even \s*?) makes the regex match the entire string as desired. See demo on regex101. The reason it works when you add the {2} quantifier is that the desire to match makes the engine backtrack when processing the \s* to a point where it can then match the non-capturing group again.

You have used \t instead of \\s+. We should use \\s+ to match a whitespace character: [ \t\n\x0B\f\r]. Check this to learn more about patterns.

Side notes:

1. Follow Java naming conventions e.g. ID should be named as id and CM should be named as cm.
2. Do not mix reading with writing i.e. read the source file and close it and then write to the target file and close it.
3. Replace e.getMessage(); with e.printStackTrace(); or at least System.out.println(e.getMessage());.

That is maybe you are using == instead of ===. i might suggest using strcasecmp if you do not want the case to be considered or use strcmp if you want case to be considered.

strcasecmp()

strcmp()

pay attention to the comparison of the result of these to functions to 0 with === so that you be sure they are equal for example: if (strcmp('Hello, 'Hello') === 0) ...

Be aware when using == and ===

(1 == '1') //Equal -- not taking into consideration the type but just the value

(1 === '1') //Not equal -- taking into consideration the type and the value

Just for your information for not you use != or !==

I'm not sure if it's always possible to do what you're trying to do. The docs at https://docs.python.org/3/library/subprocess.html say

Warning: Use communicate() rather than .stdin.write, .stdout.read or .stderr.read to avoid deadlocks due to any of the other OS pipe buffers filling up and blocking the child process.

So you're supposed to use communicate, but that means waiting for the process to terminate:

Popen.communicate(input=None, timeout=None) Interact with process: Send data to stdin. Read data from stdout and stderr, until end-of-file is reached. Wait for process to terminate.

That means you would be able to use communicate only once, which is not what you want.

However, I think using a line-buffered text mode should be safe to avoid a dead-lock:

If I understand you right, simple itertools.groupby is what you need: