root-ro | Read-only Root-FS for Raspian

Generally when people use output, if the template is being used multiple times within the same parent stack they will prefix the export with a variable (such as the stack name) to make it unique.

This can be done using the sub intrinsic function such as in the example below

You are right, TTreeView should have this, but it doesn't, and I don't see a good reason. However, here are some thoughts to take into account:

The data structure used in the TTreeView doesn't directly support counting direct children or accessing them by index, because it is a linked list where each node links to its parent, its next and previous sibling, and its first child.

For your convenience, the TTreeNode object is able to give you what you want, but for that it has to loop through the chain and count.

That also means, accessing all children in a for-loop is anyway not a good idea, like in the recursive function you mentioned - it would unnecessarily be a loop in a loop.

Instead, directly go through the chain using TreeView.Items.GetFirstNode (or MyParentNode.getFirstChild) and then a while loop with Node:= Node.getNextSibling (that also works very well for a recursive function).

Suggestion: look at the implementation in Vcl.ComCtrls. From there, you could also adapt the two most elegant functions you ask for, in case you still need it :)

That's because /tasks has a leading /.

The navigation system pushes everything that's there, let me explain.

If you had there routes:

• /
• /tasks
• /tasks/new

navigating to /tasks/new will push all of three.

If you want to keep "single" routes, you should use top level qualifiers. In your case that would be removing the / from /tasks.

This mechanism is useful to push a path and avoid strange pops if, for example, you navigate to /tasks/new from a shortcut (not from /tasks) and then pop back. Would it be good to pop to the starting point? Would it be better if popping from a new task will lead to the tasks page?

That's a brief explanation of what the navigator tries to do, I guess.

This usually happens for me when the requested resource returns 404 and instead of requested JS file you receive your index.html which has tags hence '<' token. Could it somehow be the case? Say you have versioning on your scripts and rebuild invalidates old URLs or something like that.

In Angular you can compose URL with respect of any path; [routerLink] provide the facility to provide string token or variables to make final path

[routerLink]="['/', var, 'str']" = /var/str

I was able to match using another .use for the route using the extension.

There is an upper limit to the number of unique values for attributes per node - please refer to https://docs.vespa.ai/documentation/performance/attribute-memory-usage.html#data

The only remedy is to add more content nodes to the Vespa application - this is auto-redistribute documents over more nodes and hence reduce number of unique values in the attribute

It's a list, use index of wanted field:

hostvars[inventory_hostname]['ansible_devices']['sda']['partitions']['sda2']['holders'][2]

or hostvars.inventory_hostname.ansible_devices.sda.partitions.sda2.holders[2]

My suggestion to try jq command:

There is a lot of research on this topic and your approach will inevitably lead to a lot of self joins which is slow. It is very close to this solution. I recommend you to use some native XQuery database such as BaseX, or Saxon which are inherently optimized to process the XQueries without the need to rewrite them into the SQL.

However, if you really want to rewrite XQueries into SQL then read for example XPath accelerator proposed by Torsten Grust. Ideas behind his work are implemented in MonetDB XQuery engine. He is using slightly different labeling scheme than you, but I guess the ideas can be implemented in your approach as well.