Lineage not showing deepest root

[connorhsm]

In the case of Eve Happy, members of generation 282 are currently dying. Eve is only showing as 250 deep, while prior lineages show this well.

It does not appear there is a generation missing in the chain after briefly clicking through generations.

I can also select Serena Happy of gen 251 and cause all gens to now appear as expected. Following up to 10 of her grandparents and all gens still show as expected.

[connorhsm]

Possibly related #18

[connorhsm]

Eve Happy is only showing up to Gen 251 because... their data has only been generated to be equal to 251.

What's stopping the reloading of their generation information to update?

1315489	displayID	playerID	Eve Happy	118.522	1	2024-07-07 06:01:38	251	play.twohoursonelife.com

[connorhsm]

Likely somewhere in these functions, at somepoint we must have failed to compute the generations correctly.

OneLifeWeb/web/public/lineageServer/server.php

Line 1413 in 0ab910a

function ls_setDeepestGenerationUp( $inID,

OneLifeWeb/web/public/lineageServer/server.php

Line 2614 in 0ab910a

function ls_computeDeepestGeneration( $inID ) {

[connorhsm]

CSV of all Happy Family lives HappyFamilyRedacted.csv This was not actually all, by mistake.

• eve_life_id = 0 is Eve. Their lineage_depth should be the largest, but is not. Shows 250, expected 300ish.

• Causes Eve Happy to report only as "All Time Deep Roots" 250, when in reality its 300ish. If you view Eve Happy, you can see only down to that generation, but clicking Serena Happy in gen 251, you see the last gen 301.

• Eve Happy

• Serena Happy

I'm wondering if there's a correlation in the data that can point to where it went wrong, even filtering out the lives that are not part of the direct lineage line or visualisations of the direct line would be helpful.

A few related locations in the web server, some already mentioned above.

OneLifeWeb/web/public/lineageServer/server.php

Line 1727 in 0ab910a

echo "<tr><td colspan=6><font size=5>All Time Deep Roots:".

OneLifeWeb/web/public/lineageServer/server.php

Line 1803 in 0ab910a

function ls_printFrontPageRows( $inForceIndexClause,

OneLifeWeb/web/public/lineageServer/server.php

Line 1441 in 0ab910a

$query = "UPDATE $tableNamePrefix"."lives ".

OneLifeWeb/web/public/lineageServer/server.php

Line 2661 in 0ab910a

$query = "UPDATE $tableNamePrefix"."lives ".

[TanyaPegasus]

May or may not be useful, but clicking through the family members, starting with Eve, also incrementally adds more generations. eg Reality Happy shows up to gen 253,. Her daughter, Violet Happy shows up to gen 254 etc

[connorhsm]

The earliest life in the tree that can see max gen 301

• Tacori Happy

[connorhsm]

My best guess here is that at some point, for some reason around Tacori Happy's life being logged, or a character of a nearby generation, the PHP process was exited or failed while recursing up the tree.

OneLifeWeb/web/public/lineageServer/server.php

Lines 1413 to 1463 in 0ab910a

	function ls_setDeepestGenerationUp( $inID,
	$in_deepest_descendant_generation,
	$in_deepest_descendant_life_id ) {
	global $tableNamePrefix;
	$query = "SELECT parent_id, deepest_descendant_generation, ".
	"deepest_descendant_life_id ".
	"FROM $tableNamePrefix"."lives WHERE id=$inID;";
	$result = ls_queryDatabase( $query );
	$numRows = mysqli_num_rows( $result );
	if( $numRows == 0 ) {
	return;
	}
	$deepest_descendant_generation =
	ls_mysqli_result( $result, 0, "deepest_descendant_generation" );
	$deepest_descendant_life_id =
	ls_mysqli_result( $result, 0, "deepest_descendant_life_id" );
	if( $in_deepest_descendant_generation > $deepest_descendant_generation ) {
	// even deeper than last known
	// set it
	$query = "UPDATE $tableNamePrefix"."lives ".
	"SET ".
	"deepest_descendant_generation = ".
	" $in_deepest_descendant_generation, ".
	"deepest_descendant_life_id = ".
	" $in_deepest_descendant_life_id, ".
	"lineage_depth = ".
	" $in_deepest_descendant_generation - generation ".
	"WHERE id = $inID;";
	ls_queryDatabase( $query );
	// propagate it up
	$parentLifeID = ls_getParentLifeID( $inID );
	if( $parentLifeID != -1 ) {
	ls_setDeepestGenerationUp( $parentLifeID,
	$in_deepest_descendant_generation,
	$in_deepest_descendant_life_id );
	}
	}
	}

[connorhsm]

We've now experienced this again regarding River family.