06d473692425fe85d92aac2b87a114e04f3158b1
galt
  Tue Oct 28 09:40:08 2025 -0700
It would of course be better to actually check these than skip them, however that could take a long time to do, so just tweaking hubCheck to skip the complex settings like was already done tdbQuery. Users at least will not be nagged about new settings being reported as invalid. fixes #28113

diff --git src/hg/utils/tdbQuery/tdbQuery.c src/hg/utils/tdbQuery/tdbQuery.c
index 7187b6af42c..a88e6a1188a 100644
--- src/hg/utils/tdbQuery/tdbQuery.c
+++ src/hg/utils/tdbQuery/tdbQuery.c
@@ -876,31 +876,32 @@
 			 parent->key, parentFp->startLineIx);
 	    struct tdbRecord *closestParent =
 	                                    closestTdbAboveLevel(recordList, childFp, parentDepth);
 	    assert(closestParent != NULL);
 	    if (closestParent != parent)
 	        errAbort("%s comes between parent (%s) and child (%s) in %s\n"
 		         "Parent at line %d, child at line %d.",
 			 closestParent->key, parent->key, child->key, childFp->fileName,
 			 parentFp->startLineIx, childFp->startLineIx);
 	    }
 	}
     }
 }
 
 static boolean isComplex(char *name)
-/* Check to see if this is one of the filter variables that have arbitrary initial strings. */
+/* Check to see if this is one of the filter variables that have arbitrary initial strings. 
+ * This routine copied to hubCheck.  */
 {
 if (startsWith("yAxisLabel.", name))
     return TRUE;
 if (startsWith("filter.", name))
     return TRUE;
 if (startsWith("filterValues.", name))
     return TRUE;
 if (startsWith("filterValuesDefault.", name))
     return TRUE;
 if (startsWith("filterType.", name))
     return TRUE;
 if (startsWith("filterLimits.", name))
     return TRUE;
 if (startsWith("filterLabel.", name))
     return TRUE;