HPCC-7929 Configmr - Tooltips too long and multiples

- Tool tips will be truncated to at 100 characters
- Navigator tooltips will not appear outside of table

Signed-off-by: Gleb Aronsky <gleb.aronsky@lexisnexis.com>
Merge pull request #3692 from garonsky/issue-7929_Tooltip_issues

HPCC-7929 Configmr - Tooltips too long and multiples

Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
HPCC-8279 Merge removeEntry and removePhysical

Merge removeEntry and removePhysical and let it decide which
path based on the type of the file and not user's choice.

Signed-off-by: Renato Golin <rengolin@hpccsystems.com>
HPCC-2351 Add a new sequential flag for a graph

Occasionally (e.g., for APPLY) the actions in a graph should be
executed SEQUENTIALly, rather than in PARALLEL.  This code adds
an attribute onto the graph to indicate if this is true.
applyaction.ecl is an example that requires it.

Will also require changes in roxie/thor.  See issue #2351.

Signed-off-by: Gavin Halliday <gavin.halliday@lexisnexis.com>
HPCC-2351 Use new sequential flag for roxie graphs

If codegen indicates that a graph should be executed sequentially, do so.
Re-enable the applyaction.ecl test that was (sometimes) failing without
this fix.

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
HPCC-2351 Ensure APPLY actions are in separate subgraphs

This is required so that roxie/thor can execute the apply actions sequentially,
since they generally execute all sinks in a subgraph in parallel.

Signed-off-by: Gavin Halliday <gavin.halliday@lexisnexis.com>
Merge remote-tracking branch 'origin/candidate-3.10.x'

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
HPCC-8303 Allow resizeRow to indicate how much data should be copied.

If thor uses resizeRow to resize the auxiliary array used for stable sorting
it doesn't need to copy any of the contents of the old array.  The oldsize
parameter is now changed to a copysize parameter to allow no data to be copied.

Signed-off-by: Gavin Halliday <gavin.halliday@lexisnexis.com>
Merge pull request #3717 from ghalliday/issue8303

HPCC-8303 Allow resizeRow to indicate how much data should be copied.
Merge remote-tracking branch 'origin/candidate-3.10.x'

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
HPCC-3309 Ensure child graphs are executed sequentially

Thor already executed child graphs in parent graph sequentially,
but they were store in a hash table, and were no longer retrieved
in the order added.

Ensure that they remain ordered.

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
HPCC-8278 Cache memory allocators

Thor or generated code will ask for allocators during the
lifetime of a query. On the whole these are all requested up
front, e.g. in activity initialization or onCreate() methods.
Some might be requested repeatedly e.g. in transform() methods
Ensure that previously request meta/actid allocators are reused
by introducing a cache.

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
HPCC-8310 Verify KeyedJoin,local matches index

Check that the index supplied to a keyedjoin,LOCAL is also
local. Fire an error if not.

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
Merge pull request #3696 from rengolin/dfs-remove

HPCC-8279 Merge removeEntry and removePhysical

Reviewed-By: Jake Smith <jake.smith@lexisnexis.com>
Reviewed-By: Gavin Halliday <gavin.halliday@lexisnexis.com>
Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
HPCC-7983 Avoid circular link leak for null inputs

Null activities that were created whilst tying up the graph, e.g.
when it was detected that a projectfilter had no matches, caused
a leak due to a circular leak

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
HPCC-8059 Memory leaks

Various leaks fixed, none large in terms of memory:

1) IndexWrite outRowAllocator leak
2) local join (left already sorted) input leak
3) lookahead reader, writer leak
4) piperead activity leak unless transformer used
5) minor graph results leak

the most significant is 2) - which as a side-effect caused all
acitivies above the left hand side input of the join to be
leaked also.

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
Merge pull request #3729 from jakesmith/memleaks

HPCC-8059 Memory leaks

Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
HPCC-7991 Avoid uninitialized valgrind warning

A raw (unpacked) struct that was serialized to between slave
and master, caused valgrind warnings regarding uninitialized
data, because of the uninitialized padding between fields
Avoid warning, by memsetting to empty.

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
Merge pull request #3732 from jakesmith/uninit

HPCC-7991 Avoid uninitialized valgrind warning

Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
Merge pull request #3725 from jakesmith/keyjoin-local-check

HPCC-8310 Verify KeyedJoin,local matches index

Reviewed-by: Gavin Halliday <ghalliday@hpccsystems.com>