matthiasgeihs

Thank you for the reply and the clarification. Would it make sense to check whether precision was lost in translation and throw an error in that case? Also note that...

> I'm not particularly fluent in Go but maybe there are ways to control serialization that makes dealing with int64 simple? In my Java implementation I defined an int53 type...

Any news?

I think YAML in some contexts is the new JSON. I'm happy that JSON is part of the standard lib. YAML should be too.

Having the same issue (on MacOS). ```js const appProcess = spawn("npm", ["run", "serve"]); // runs "webpack serve" ... appProcess.kill(); // returns true, but "webpack" still running ``` @alexander-akait

@alexander-akait created https://github.com/webpack/webpack-dev-server/issues/5026

Having same issue. Any solution available?

ah, wasn't aware that it's not maintained anymore. thx for the workaround tip. i'm wondering: maybe the problem is not too hard to fix? any idea what might be causing...

`fn decrypt_result(result: &EncryptedResult) -> String` probably needs a decryption key as input? As the result is a `String`, I assume the output is expected to be a string representation of...

If there is multiple rows that match, should we support returning multiple rows? Or just return one of the matching rows?