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
I presume that the intention is to create 2 lecture slots (which they did, but this bug remained), since it doesn't make sense for a timetable entry to occur in both week 1 and week 1 at the same time.
While we now hide these mistakes in the frontend through #3677, we should have the scraper produce a warning for when duplicated weeks appear in the weeks attribute of a timetable entry, so we can let the relevant departments know (especially if it's a systematic issue)
The text was updated successfully, but these errors were encountered:
In #3648, we notice that this year's data for ST2334 has individual lecture lesson slots (timetable entries) with duplicated weeks.
"weeks": [1, 1, 2, 2, 3, 3, 4, 4, 5, 5, 6, 6, 7, 7, 8, 8, 9, 9, 10, 10, 11, 11, 12, 12, 13, 13],
I presume that the intention is to create 2 lecture slots (which they did, but this bug remained), since it doesn't make sense for a timetable entry to occur in both week 1 and week 1 at the same time.
While we now hide these mistakes in the frontend through #3677, we should have the scraper produce a warning for when duplicated weeks appear in the
weeks
attribute of a timetable entry, so we can let the relevant departments know (especially if it's a systematic issue)The text was updated successfully, but these errors were encountered: