LOGGER datasource does not work with T1, T2, Node and data rate specified

[kjhazelwood]

Describe the bug
If datalogger request is made where all the optional arguments are specified for LOGGER, including data rate, NODE, T1 and T2, nothing is returned. Data can be retrieved if NODE and data rate is omitted.

Expected behavior
If the user explicitly lists all the arguments to retrieve data from a particular dataloger list, it should return data from that list, no other list, not archive, and not some assumption of what the user may have wanted. Also, explicit use of the Backup and Archive lists don't seem to work. Requests of data that have rolled off a list may return data but whether it's 5m or 1s data seems to be dependent on date range.

[kjhazelwood]

Code from Feb 2024 worked as expected, this bug occurred sometime after

[rneswold]

@kjhazelwood, can you give a set of parameters that didn't work for you? We'll try to recreate it in the GraphQL environment. If it happens there, then it's a DPM issue. If it doesn't happen, then it's in the Python code.