goss | Quick and Easy server testing/validation | Continuous Deployment library

Probably your request is wrong and you don't get the expected response because of it... Look at the status that's returned (hReq.status and hReq.statusText), I bet it's 400 Bad Request or 500 Internal Error and not 200 Ok. (You could also use an inspecting proxy like Fiddler to look at what exactly you send and receive here.)

I can already see your request body is invalid JSON as it has unquoted strings in it... It's not the exact same as you showed in Postman! That's like the issue (or one of the issues). You have e.g. "methodType": extract, but it has to be "methodType": "extract" (in VBA ""methodType"": ""extract"") - you did it correctly in Postman but wrong in your code.

There is a little hack with the scratch image:

Ok, here is one way to obtain what you want in about 2min. Some tickers are bad, that's why it crashes.

Here's the code. I use joblib for threading or multiprocess since it doesn't work in my env. But, that's the spirit.

If i see correctly, in the vuetify example v-dialog component in

This seems to be an open source Go application, so it's preferable to use Nixpkgs' Go support instead, which may be more straightforward than patching a binary.

That said, installPhase is responsible creating the $out path; typically mkdir -p $out/bin followed by cp, make install or similar commands.

So that's not actually installing it into the system; after all Nix derivations are not supposed to have side effects. "Installing" it into the system is the responsibility of NixOS's derivations, as configured by you.

You could say that 'installation' is the combination of modifying the NixOS configuration + switching to the new NixOS. I tend to think about the modification to the configuration only; the build and switch feel like implementation details, even though nixos-rebuild is usually a manual operation.

I would point out that that min_data_in_leaf parameter in all the options seems very high and I suspect that the model is not learning anything and just sending the average value of the response variable with only root node.

++Update++

--memory is indeed not yet implemented in molecule docker provisioner.

If anybody is interested, here is the relevant change to the source code:

pass the hyperparam dictionary to the model constructor, adding ** to the dict to pass each dict item like a kwarg param as lgbm expects it per https://lightgbm.readthedocs.io/en/latest/pythonapi/lightgbm.LGBMClassifier.html#lightgbm.LGBMClassifier: