This issue has been reported internally within MolePro team by @codewarrior2000 where we have issues where the metadata info reported by UI does not match the same query:
The first PK reported within the UI URL is about this query:
While the second PK (from ARS) is about this query:
It happens that I was running those 2 queries in (almost in parallel, I believe potassium happened first) when submitting the tickets so I wonder whether the mixing could happen from there?
perhaps not a priority, but it could become an issue if we move forward with the automated parsing of the issues and come up with conflicting queries...
@sandrine-muller-research we are unable to reproduce this issue. If this is still happening can you give exact reproduction steps? We are going to close the ticket for now.
This issue has been reported internally within MolePro team by @codewarrior2000 where we have issues where the metadata info reported by UI does not match the same query:
The first PK reported within the UI URL is about this query:
While the second PK (from ARS) is about this query:
It happens that I was running those 2 queries in (almost in parallel, I believe potassium happened first) when submitting the tickets so I wonder whether the mixing could happen from there?
perhaps not a priority, but it could become an issue if we move forward with the automated parsing of the issues and come up with conflicting queries...