Skip to content
This repository has been archived by the owner on May 25, 2021. It is now read-only.

notifications infinite loading without useful feedback to the user #258

Closed
michielbdejong opened this issue Nov 1, 2019 · 5 comments
Closed
Labels
Triaged Issue has been triaged and prioritized by the development team.

Comments

@michielbdejong
Copy link
Contributor

https://www.dropbox.com/s/2uqjs1o5pnz6zvr/generator-infinite-loading-notifications.mp4?dl=0

@james-martin-jd
Copy link
Contributor

james-martin-jd commented Nov 1, 2019

This was actually fixed in a recent push to develop branch. The core issue was a mixup in the components library when creating new notifications, it was causing the prefix for the "current document" prefix look something like @prefix :: <https://example.com/whatever> and the double-colon was causing parsing issues.

I should also note that if you were using develop during the time period that the bug existed, you will need to manually edit or delete the malformed notifications. We cannot properly catch the errors loading the files due to an ldflex feature coming soon, it is not properly bubbling errors up so we cannot catch the error.

@michielbdejong
Copy link
Contributor Author

Ah great, then I will wait for the release and retry! :)

Regarding catching errors loading the files, that sounds serious. What is the issue number for that? And what is the LDFlex issue number it's blocked on?

@james-martin-jd
Copy link
Contributor

The fix is on develop now for notifications if you want to try again (and I can close this issue if it's working).

We don't have a specific issue here yet, but it's something we're tracking internally. The ldflex issue(s) are: LDflex/Query-Solid#30 and LDflex/Query-Solid#23

Essentially what this means is even if the code is in a try/catch block, if there's an error in an ldflex query, it just halts the javascript, instead of getting caught. That's why there's an infinite loop, the fetch failed and can't be properly caught.

@brownhoward brownhoward added the Triaged Issue has been triaged and prioritized by the development team. label Nov 6, 2019
@james-martin-jd
Copy link
Contributor

On develop, we just pushed a change that will use ShEx validation on incoming notifications, and ignore any notification that does not successfully validate with the core notification shape found here: https://shexshapes.inrupt.net/public/notifications/core-notification.shex

This should further help to prevent bad or invalid notifications from corrupting the page or notification load, but also means older, nonconformant notifications will not show in the UI.

@james-martin-jd
Copy link
Contributor

This is on develop now, and never made it to master, so I am closing the issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Triaged Issue has been triaged and prioritized by the development team.
Projects
None yet
Development

No branches or pull requests

3 participants