-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Why execute_batch_tasks function was called twice in sirmordred.py ? #435
Comments
Thank you @heming6666 ! I checked the history of that file, but it isn't clear why this call is duplicated. It was added here: 99e2b28. Can you run to execution of sirmordred (the first one with the two statements and second one with just one) and check if the results are consistent? In order to run mordred you have to execute the script at https://github.com/chaoss/grimoirelab-sirmordred/tree/master/bin with a setup.cfg as input: |
Ok! I will check that and update the result here. |
Thanks! |
It seems that everything is still working fine after I remove the duplicate call. Firstly, I run mordred with the two statements. And I got the correct dashboard and logs, as is shown below.
Secondly, I run it again with just only one statements. And everything was still working fine. The logs were silimar with the previous one.
|
Sorry for the late reply @heming6666, and thank you for taking the time to have a look at this issue. |
Yes. I even removed all the data of elasticSearch by the following cammand: rm -rf elasticsearch-6.1.4 Then I re-installed elasticsearch and restart it. Here's the logs of elasticsearch corresponding to second test:
|
Thank you @heming6666 ! can you submit a PR? |
Sure. I will send a PR to remove the duplicate call. |
Great, thanks @heming6666 |
As mentioned in this issue, I went through the code of sirmordred.py. And I found that the
execute_batch_tasks
function would be called with the same params two times , which means that all tasks would be executed two times when the attributeupdate
was set toFalse
. Is there any specific reason?The text was updated successfully, but these errors were encountered: