Closed yongrenjie closed 1 year ago
Ok, this is because of invalid YAML metadata, so active projects are being removed entirely from the programme. Specifically, the project tracker contains 34 issues in the AGNG, FP, AS, and Active columns (as of the time of writing), of which:
That leaves 9 issues that have readable and complete YAML (1185, 1234, 1066, 1132, 1077, 1095 1079, 1096, 482). Only assignments belonging to these issues are retained, so only fetching 15 assignments makes sense.
I guess we should save the warnings until the end instead of simply deleting the issues at such at early stage. Even if a project is missing a code we'd probably still like to track allocations and FTEs, while also bugging people to edit in a project code.
The finance code is optional now, I think. (see e.g. 1214) However, other errors in the metadata still lead to projects being deleted (see e.g. 1216). This is a bit annoying, and not difficult to fix, but will probably be tedious (I think).
Fixed the above. Now whatwhat reports that it got:
44 people (correct as of the time of writing); 31 projects (correct as of the time of writing); and 118 assignments (I didn't go to Forecast to count, but this seems like a sensible number).
Working on the dev branch:
Schedule.get_the_schedule
only returns 15 assignments, which seems slightly low (note thatForecast.get_the_schedule
fetches around 500+ assignments, so it's likely something going on with merging the two sources of data)sub d1 d2
actually meansd1 - d2
, notd2 - d1
:https://github.com/alan-turing-institute/whatwhat/blob/82113da23cf0936f6bc40d9d7b10bacc3b64e418/lib/forecast.ml#L164