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
{{ message }}
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
Hey,
last week a student was shown the wrong time and location for an exam in the app. The event was updated in december, but the app still showed the old data. Turns out the app hadn't refreshed the calendar for more than a month, despite regular use by the student.
Short analysis of the api access logs in TUMonline shows that more than 50% of the users may be affected. Out of all the clients with UA TCA Client 579 that interacted with the API within the last hour, less than 50% called the kalender endpoint within the last 7 days.
Please have a look at the update/caching policy for the calendar as this may indicate a general issue. I cannot provide steps to reproduce though.
The wrong location in question was shown as upcoming event on the main screen of the app. Maybe that's part of the issue?
The text was updated successfully, but these errors were encountered:
Hey,
last week a student was shown the wrong time and location for an exam in the app. The event was updated in december, but the app still showed the old data. Turns out the app hadn't refreshed the calendar for more than a month, despite regular use by the student.
Short analysis of the api access logs in TUMonline shows that more than 50% of the users may be affected. Out of all the clients with UA
TCA Client 579
that interacted with the API within the last hour, less than 50% called thekalender
endpoint within the last 7 days.Please have a look at the update/caching policy for the calendar as this may indicate a general issue. I cannot provide steps to reproduce though.
The wrong location in question was shown as upcoming event on the main screen of the app. Maybe that's part of the issue?
The text was updated successfully, but these errors were encountered: