A quick note on mounting windows filesystems on linux.
Your platform will require cifs-utils.
sudo apt install cifs-utilsFrom here, you can connect and mount a remote file system.
sudo mount -t cifs //ip.address.of.windows/location/to/mount /mnt -o user=john,password=mypassword,domain=mydomainDone. You can now access the remote filesystem.
In today’s article, we’ll talk a bit about the HDF5 format. From the HDF5 website:
An HDF5 file is a container for two kinds of objects: datasets, which are array-like collections of data, and groups, which are folder-like containers that hold datasets and other groups.
Useful links:
GNU Grep is an amazingly powerful tool that will allow you to search input files containing specified patterns.
The following command performs a recursive search for a string, inside a directory of files:
grep -rnw '/path/to/search' -e 'pattern-to-find'Breaking this command down:
-r makes the execution recursive-n will give you the line number-w matches the whole wordYou can use the --exclude switch to remove file patterns from the set of files included in your search. Removing js and html files from your search might look like this:
--exclude *.{js,html}The opposite of this will be the --include switch.
For further details on this really useful tool, check out the man page.
Sometimes you might find yourself in the situation where you require a little more power out of your node.js application. You may need to squeeze some extra performance out of a piece of code that you simply can’t achieve using javascript alone. Node.js provides a very rich sdk to allow application developers to create their own addons to use, that allow you to write in C++.
These binary compiled modules then become directly accessible from your node.js applications.
In today’s article, I’d like to walk through the basic setup of an addon project. We’ll also add a function to the addon, and demonstrate the call from javascript to C++.
Before you can get developing, you’ll need to make sure you have some dependencies installed. Create a directory, and start a new node application.
mkdir my-addon
cd my-addon
npm initYou’ll need to let the package manager know that your application has a gyp file present by switching gypfile to true.
// package.json
{
"name": "my-addon",
"version": "1.0.0",
"description": "",
"main": "index.js",
"gypfile": true,
"scripts": {
"build": "node-gyp rebuild",
"clean": "node-gyp clean"
},
"author": "",
"license": "ISC",
"devDependencies": {
"node-gyp": "^3.8.0"
},
"dependencies": {
"node-addon-api": "^1.6.3"
}
}The project is going to require a gyp file called binding.gyp. It’s the responsibility of this file to generate the build environment that will compile our addon.
// binding.gyp
{
"targets": [{
"target_name": "myaddon",
"cflags!": ["-fno-exceptions"],
"cflags-cc!": ["-fno-exceptions"],
"sources": [
"src/main.cpp"
],
"include_dirs": [
"<!@(node -p \"require('node-addon-api').include\")"
],
"libraries": [],
"dependencies": [
"<!(node -p \"require('node-addon-api').gyp\")"
],
"defines": [ "NAPI_DISABLE_CPP_EXCEPTIONS" ]
}]
}With these in place, you can install your dependencies.
npm installThe gyp file notes that the source of our addon sits at src/main.cpp. Create this file now, and we can fill it out with the following.
// src/hello.cpp
#include <napi.h>
Napi::Object InitAll(Napi::Env env, Napi::Object exports) {
return exports;
}
NODE_API_MODULE(myaddon, InitAll)The keen reader would see that our module does nothing. That’s ok to start with. This will be an exercise in checking that the build environment is setup correctly.
Import and use your addon just like you would any other module from within the node environment.
// index.js
const myAddon = require("./build/Release/myaddon.node");
module.exports = myAddon;We’re ready to run.
npm run build
node index.jsOk, great. As expected, that did nothing.
Let’s create a function that will return a string. We can then take that string, and print it out to the console once we’re in the node environment.
We’ll add a header file that will define any functions. We also need to tell our build environment that we’ve got another file to compile.
// binding.gyp
{
"targets": [{
"target_name": "myaddon",
"cflags!": ["-fno-exceptions"],
"cflags-cc!": ["-fno-exceptions"],
"sources": [
"src/funcs.h",
"src/main.cpp"
],
"include_dirs": [
"<!@(node -p \"require('node-addon-api').include\")"
],
"libraries": [],
"dependencies": [
"<!(node -p \"require('node-addon-api').gyp\")"
],
"defines": [ "NAPI_DISABLE_CPP_EXCEPTIONS" ]
}]We define the functions for the addon.
// src/funcs.h
#include <napi.h>
namespace myaddon {
Napi::String getGreeting(const Napi::CallbackInfo &info);
}Now for the definition of the function, as well as its registration into the module.
#include "funcs.h"
Napi::String myaddon::getGreeting(const Napi::CallbackInfo &info) {
Napi::Env env = info.Env();
return Napi::String::New(env, "Good morning!");
}
Napi::Object InitAll(Napi::Env env, Napi::Object exports) {
exports.Set("getGreeting", Napi::Function::New(env, myaddon::getGreeting));
return exports;
}
NODE_API_MODULE(myaddon, InitAll)The getGreeting function is actually doing the work here. It’s simply returning a greeting. The InitAll function now changes to add a Set call on the exports object. This is just registering the function to be available to us.
So, now we can actually use the greeting. We can just console.log it out.
const myAddon = require("./build/Release/myaddon.node");
console.log(myAddon.getGreeting());
module.exports = myAddon;We can now run our code.
➜ my-addon node index.js
Good morning!Generating ranges in PostgreSQL can be a very useful tool for the creation of virtual tables to join to. Should your report require you to generate an entire range; left joining only to the values that need to be filled out.
The following code snippet will allow you to generate such a range:
WITH RECURSIVE cte_dates AS (
SELECT '2018-01-01T00:00:00.000'::timestamp AS cd
UNION ALL
SELECT cd + interval '1 month'
FROM cte_dates
WHERE cd + interval '1 month' <= '2019-01-01T00:00:00.000'::timestamp
)This snippet will create a table of dates, 1st of each month for the year 2018.
The initial line of the CTE allows you to set the start of the range:
SELECT '2018-01-01T00:00:00.000'::timestamp AS cdThe frequency at which the range is sampled is then set with this line:
SELECT cd + interval '1 month'Finally, the end of the range is set with the following line:
WHERE cd + interval '1 month' <= '2019-01-01T00:00:00.000'::timestamp