Closed
Bug 1055737
Opened 11 years ago
Closed 11 years ago
Datazilla Repository Update
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jeads, Assigned: cturra)
References
Details
(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1073] )
A new datazilla repository is ready to push to stage. This release includes the following changes:
1.) Added messaging indicating when an http GET request fails.
| Assignee | ||
Comment 1•11 years ago
|
||
commit 658096d5d0a99cff9eb1c214fe508271e0a2c7e0 pushed to stage. please let me know when you've completed your testing and are happy with this change going into production.
Flags: needinfo?(jeads)
OS: Mac OS X → All
Hardware: x86 → All
| Reporter | ||
Comment 2•11 years ago
|
||
It looks like we're hitting a bug in jquery that prevents the error callback getting called when the data type is json and the http get times out. I added an explicit timeout for the failing queries.
Please push the repository to stage again and I will confirm that the change works.
Flags: needinfo?(jeads) → needinfo?(cturra)
| Reporter | ||
Comment 4•11 years ago
|
||
The timeout's set in the jquery ajax calls are not honored. It's a bug in jquery. Having error handling callbacks is better than not having them, might figure a quick fix in the future at some point and the dialogs will be displayed as expected.
Please go ahead and push to production.
Comment 5•11 years ago
|
||
Production is now on commit 714d3a6b39d889fbcd21363b329b3b2b1dc47a6f.
Can you please verify that the fix is working as intended in production?
Comment 6•11 years ago
|
||
If someone could define how it should behave, I can test.
What I tried just now:
- Visited https://datazilla.mozilla.org/
- Throbber spins for ~4 minutes already (and counting).
- No message is displayed and also it doesn't show data.
How long is the timeout duration?
Comment 7•11 years ago
|
||
(In reply to C. Liang [:cyliang] from comment #5)
> Production is now on commit 714d3a6b39d889fbcd21363b329b3b2b1dc47a6f.
>
> Can you please verify that the fix is working as intended in production?
jeads mentioned on IRC that the "fix" doesn't fix anything right now due to a jquery bug. See comment 4. This explains comment 6.
Comment 8•11 years ago
|
||
Marking the bug as R/F. If it turns out that this is incorrect, please re-open the bug.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 9•11 years ago
|
||
I modified the title to what this bug is about - according to comment 0, and as such, the issue is not resolved yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Datazilla Repository Update → DataZilla: show a timeout message instead of spinning the throbber indefinitely
| Assignee | ||
Comment 10•11 years ago
|
||
:avih - the latest git commit has been pushed, which was the request fulfilled by this bug (Datazilla Repository Update). as a result, i am going to remark this bug as r/fixed.
i understand there's still an issue with the with timeout loading data. to have this addressed, you'll need to file a bug with the datazilla dev team (we just assist in pushing code to stage/prod). for more details about how to do that, i would recommend chatting with :jeads.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Summary: DataZilla: show a timeout message instead of spinning the throbber indefinitely → Datazilla Repository Update
Updated•7 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•