eclipse-researchlabs / scava

Eclipse Public License 2.0
7 stars 1 forks source link

Projects, Tasks, Metrics and Reset #71

Open davidediruscio opened 4 years ago

davidediruscio commented 4 years ago

Hello,

Today exploring some issues that @mhow2 and in minor degree @valeriocos raised to me, I discovered an important bug that it is affecting indirectly all the creators of metric providers.

The issue is similar to https://github.com/crossminer/scava/issues/178 and quite probable to the implemented solution.

The core issue is the fact that metrics are sometimes not executed, whether a new task has been created or reset. Meaning that data in MongoDB and ElasticSearch are not being updated.

Both issues are are serious. In first place because all the metrics are affected historic and not historic, as well indexer. If metrics are not executed, yes we prevent duplicated data in historic metrics, but none of the data will be updated correctly in MongoDB and the ElasticSearch. In second place, User Partners will believe that metrics and tools created by R&D partners are wrong, not fixed, or not working.

Again, after seeing this issues, I think my proposal of creating collections based on project+task was the correct way to solve issue #178. As it allowed the platform dropping a collection if the task was reset or changed.

I will send an email to all the partners and recommend them rather than creating task to create projects. And rather than resetting tasks, to delete the project and recreate it. That's the current hotfix that I can propose.