Skip to content
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

Check if remove_alert is present in toplevel #582

Closed
wants to merge 1 commit into from

Conversation

i5o
Copy link
Contributor

@i5o i5o commented Oct 9, 2015

Sometimes the toplevel is changed to DocumentButton,
and there is no remove_alert on DocumentButton.

The idea is to check if there is remove_alert on toplevel,
to prevent a false function call

I made this patch because of this error in logs after duplicate activity (appears -I think- 10 seconds after the duplication process)

Traceback (most recent call last): File "/home/broot/sugar-build/build/out/install/lib/python2.7/site-packages/jarabe/view/viewsource.py", line 470, in __alert_response_cb self.get_toplevel().remove_alert(alert) AttributeError: 'DocumentButton' object has no attribute 'remove_alert'

Sometimes the toplevel is changed to DocumentButton,
and there is no remove_alert on DocumentButton.

The idea is to check if there is remove_alert on toplevel,
to prevent a false function call
@samdroid-apps
Copy link
Contributor

Does the alert get removed automatically?

@i5o
Copy link
Contributor Author

i5o commented Oct 9, 2015

Nop,

if I don't call remove_alert it's not automatic

2015-10-09 19:14 GMT-02:00, Sam notifications@github.com:

Does the alert get removed automatically?


Reply to this email directly or view it on GitHub:
#582 (comment)

Ignacio Rodríguez
SugarLabs at Facebook
https://www.facebook.com/pages/SugarLabs/187845102582

@samdroid-apps samdroid-apps added this to the 0.108 Features milestone Oct 9, 2015
@samdroid-apps
Copy link
Contributor

I've made a ticket for this bug: https://bugs.sugarlabs.org/ticket/4898

@samdroid-apps
Copy link
Contributor

I think we should wait until we understand what this bug is before we patch it. Them maybe we can make an even better patch!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants