-
Notifications
You must be signed in to change notification settings - Fork 495
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
As someone playing with demo.dataverse.org, I want to be able to see my notifications without the whole application blowing up #5687
Comments
It has been like that for a while... Sorry for not reporting it! |
😞 |
Here's the line that's throwing the NullPointerException That is to say that
|
Related to:
Some of these could probably be closed and consolidated into one issue to refactor notifications, if not as a whole, then at the very least for the request access feature, which is will be a more prominent feature with the upcoming DataTags integration. |
|
I can easily reproduce the 500 error with the following steps:
I just created pull request #6008 to fix this. The idea is to show the generic "The dataverse, dataset, or file for this notification has been deleted" error we use elsewhere instead, like in the screenshot below: The pull request has additional screenshots. |
New info: I don't think that a missing file is the only cause of this. I just debugged an issue in production where and old request from 2016 was causing this to happen. The object_id of that notification leads to a dataset. SO, I think the issue could be because we switched from tracking the dataset here to the file? If so, the dataset object id will not be found by the file Service bean. I think it's worth at least looking at the change history and verifying if this is the case. If so, then just saying it's been deleted may not be the best solution. Or it may be, since I don't recall at this moment when we made the change. |
After some investigation, it turns out the access request notiication was always tracking a file, that was incorrect on my part. However there is an issue in that a subset of notifications pre mid 2017 got corrupted and are incorrect. So @sekmiller is adding to the release notes associated with this issue to delete all pre 2018 notifications. |
for deleting invalidated notifications
generic REQUESTFILEACCESS notification when dataset destroyed #5687
I mentioned this problem at standup this morning and was told to go ahead and create and issue. At the moment https://demo.dataverse.org is running 3721306 (4.11)
Here's the stacktrace (kudos to @kcondon ):
My username on demo is "philip_durbin":
The text was updated successfully, but these errors were encountered: