rrd | package implements Go bindings for the rrdtool C

This is because lastupdate() and fetch() do different things.

When you add data to an RRD, there is a multi-stage process going on in the background. First, the data are turned to Rates; then Normalised; then Consolodated.

1. Data submitted update()

2. Data are converted to a Rate. If your DS is of type gauge then this is a noop, but other types will be converted based on the time of the previous update.

3. Now we get the value returned by lastupdate(), which is this DP (datapoint)

4. Data are Normalised. This means that we assume a linear progression from the last known datapoint, and calculate the average over the last step Interval (300s in your example above). This gives a new PDP (primary datapoint) on a time window boundary (IE with the PDP time being a multiple of the Interval)

5. The PDP are now Consolodated. When sufficient have been collected,a new CDP (Consolodated Datapoint) is written to the RRA, depending on the CF and XFF. If your RRA has 1cdp=1pdp (as in your case) then the CDP should be the same as the PDP.

6. Now we get the CDP in the RRA, which is what fetch() returns.

From this, you can see that the value you store is not the same as the lastupdate() (due to Normalisation and Rate); and this is not the same as the fetch() (due to Consolodation).

In addition, you won't see the value appearing in the lastupdate() until the time window has completed; and you wont see it appearing in fetch() until the RRA CDP is completed.

Since your fetch() is not asking for more data than in your 1cdp=1pdp RRA, you'll avoid changes due to consolodation, but you're likely hitting Normalisation.

If you want the shown values to be the same, then you need to ensure all 3 operations are no-ops.

1. Use type gauge to stop Rate conversion

2. Ensure all updates are done exactly on a time boundary to avoid Normalisation. Don't use 'N' (now) in the update, fix it to a timestamp that is a multiple of the Interval (300s).

3. Have a 1cdp=1pdp RRA of sufficient size to avoid Consolodation.

For more detail on this, see Alex's famous page here: http://rrdtool.vandenbogaerdt.nl/process.php

How can I segregate these nested routes ("/wordmaster/anything_here/anything_here_again") into their component folders?

You can move these routes into the component you want to render them. They would be rendered again into a Routes component.

Example:

App - renders the base/root routes, wildcard * appended to route paths so sub-routes can be matched.

Use array_filter to remove NaN with is_nan function.

As I know, every algo works on numerics, or converts text to numerics, and then does it's job. Maybe you can try this.

The answer is strictly due to make's rules and has nothing to do with any of the other tags here (I'll remove all the others). The makefile that doesn't work says:

• to build gitbranch-foo, we must build git-spawn-branch
• to build gitbranch-bar, we must build git-spawn-branch

(plus of course the code for building git-spawn-branch itself and the other associated stuff, but let's stop here).

You then run make, telling it to build both gitbranch-foo and gitbranch-bar.

Make picks one of these to build—gitbranch-foo, in this case—and begins building. Oh hey, says make to itself, this needs git-spawn-branch to be built, and we have not done that yet. Off goes make, which builds git-spawn-branch according to the rules. Now it's built! Make can go back to building gitbranch-foo. This executes the remaining recipe, which is empty.

If parallel builds are allowed, make can also now begin building gitbranch-bar while gitbranch-foo builds. If not, we wait for gitbranch-foo to be fully built at this point. Either way we very quickly get around to buildling gitbranch-bar. Hm, says make to itself, this needs git-spawn-branch to be built ... but fortunately, I have done that already! Onward! Let's make the rest of gitbranch-bar now! That requires executing the empty recipe, which goes very quickly.

Make is now done. It has built everything required.

(The makefile that works uses $call sensibly, directly from each rule, so that the commands that $call expands to are required to be run for each target, rather than hidden away in a third target that can be built just once and never needs to be run any further.)

(Note that the gmake documentation mentions that a .PHONY rule is run every time. This means once per invocation of make, not once per invocation of the rule.)

You should create separate component for header

header.js

Try drop_duplicates + sort_values

I fixed this by removing fibers (that is responsible for this error) from the dependencies. This might affect the build performance a little bit but everything works for me now.