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
In the demo system of OpenWISP, some users try to create a network topology object and insert a random URL.
This raises exceptions which are logged on the server side but not presented to the user.
We should find a way to present this information to the user, notify them, avoid logging the error on the server side.
We should also make sure that we do not bombard the user with many notifications if the error keeps on repeating.
I think we should probably modify the model to add some state which indicates whether the parsing is working fine or not.
The text was updated successfully, but these errors were encountered:
In the demo system of OpenWISP, some users try to create a network topology object and insert a random URL.
This raises exceptions which are logged on the server side but not presented to the user.
We should find a way to present this information to the user, notify them, avoid logging the error on the server side.
We should also make sure that we do not bombard the user with many notifications if the error keeps on repeating.
I think we should probably modify the model to add some state which indicates whether the parsing is working fine or not.
The text was updated successfully, but these errors were encountered: