-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
NPE from scheduleFeedbackSessionPublishedEmail #10974
Comments
Let us know if this issue is not resolved with #10930 (comment) |
After setting the region in build.properties, I did not receive any errors. Unfortunately, it's because even the error reporting mechanism (which relies on the task queue) stopped working. Only realized the problem when a few users reported not being able to send reminders to students. I rolled back to the previous version after that. There are several errors in the log, but all mention permission issues.
|
For the record, app info:
|
Solved by giving 'Editor' permissions to the gserviceaccount Thanks @wkurniawan07 for the solution info |
The 'log compilation' cron job that runs every 5 minutes still seems to have some problem.
|
That is a known issue (googleapis/google-cloud-java#3693) and is not a cause of concern (at best, just some annoyance). It does not affect the logs being fetched. Can think of it as something like resource failed to be closed. |
I see. Well, this means I'm going to receive an error log email every 5 minutes. I can't simply ignore them either, as the email can contain other error messages. So, looks like we'll have to find a way around it? Perhaps we can update the log compilation task to ignore this specific error? googleapis/google-cloud-java#3693 says it is fixed and to be released but that was more than 1 year ago. |
teammates/src/main/java/teammates/ui/webapi/CompileLogsAction.java Lines 61 to 69 in 4e44320
@damithc can try adding this before the try {
logging.close();
} catch (Exception e) {
// ignore exception when closing resource
} |
That seems to have done the trick. Thanks @wkurniawan07 |
I'm guessing the task now is to have this in the main code base by the next release |
Yes, I think so. |
This error happened soon after both times I deployed v7.10.0 (I rolled back both times). First time I wasn't sure if the error is caused by a change in the new version. After the second time, seems too much of a coincidence.
v7.10.0
Caused by [POST] https://teammatesv4.appspot.com/webapi/session/publish
Let me know you need more info.
The text was updated successfully, but these errors were encountered: