Opened 11 years ago

Closed 11 years ago

Last modified 10 years ago

#4648 closed bug (notabug)

Download Builder fails often

Reported by: DarwinSurvivor Owned by:
Priority: major Milestone: 1.8
Component: [meta] ui.downloadbuilder Version: 1.7.2
Keywords: fail refresh Cc:
Blocked by: Blocking:

Description

There are certain configurations that cause the Download Builder to fail. By fail, I mean the page pauses for 5 seconds (appearing to load), the refreshes with no download prompt.

To recreate, select: UI Core - All Interaction - All (except Selectable) Widgets - All Effects - None (note this will work) Now disable Interaction -> Droppable (now it will NOT work)

I love the work you guys are doing and would hate for people to lose out because they simply can't download it properly :(

Change History (3)

comment:1 Changed 11 years ago by Jörn Zaefferer

Milestone: TBD1.8

comment:2 Changed 11 years ago by d3r1v3d

I'm having a bit of trouble replicating this error. Here's the steps I'm using to test:

  1. Browse to (http://jqueryui.com/download/).
  2. Uncheck selectable interaction.
  3. Hit deselect all for effects.
  4. Attempt to download distribution and verify that it works.
  5. Uncheck droppable interaction.
  6. Attempt to download again.

The first time I got to the last step, it paused for about three seconds and then allowed me to download a valid distribution. I think this combination hadn't been cached before and so it was attempting to build the distribution and cache it before allowing me to download it. Now, whenever I run this test procedure, it returns me the cached distribution immediately.

Not sure why the download builder would fail to cache this combination every time DarwinSurvivor tried to download it. It's possible that the user tried to cache under a peak load, although I'm not convinced it would fail repeatedly like it seemed to.

Was anyone else able to replicate this?

comment:3 Changed 11 years ago by Jörn Zaefferer

Resolution: invalid
Status: newclosed

Can't replicate it either. I tried a few other variations, until finding one that wasn't cached - took a few seconds, but worked fine otherwise.

Please reopen with a new description to reproduce.

Note: See TracTickets for help on using tickets.