You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're seeing results come back like this:
"node_bindings": {
"on": [
{
"id": "NCBIGene:154",
"query_id": null,
"attributes": null
}
],
"sn": [
{
"id": "PUBCHEM.COMPOUND:5311065",
"query_id": null,
"attributes": null
}
],
"intermediate_gene_96062": [
{
"id": "NCBIGene:348",
"query_id": null,
"attributes": null
}
]
with the extra "intermediate_gene" node. Is this intentional? At the moment, it throws off the ARS merge behavior because we determine whether two results are the same by looking for the set of nodes in the node bindings to match. So, this one doesn't match with the results returned by other ARAs that are the same, except for lacking the intermediary node.
This is in CI with PK = 21791a56-966b-477b-9f6e-7fb3450387cf
The text was updated successfully, but these errors were encountered:
From Mark:
This is in CI with PK = 21791a56-966b-477b-9f6e-7fb3450387cf
The text was updated successfully, but these errors were encountered: