q2view says a tutorial file is too large

Hi! I was going through the importing tutorial and noticed that the emp-paired-end-sequences.qza “output artifact” breaks q2view if you click on the “view” button next to it—

This issue can be reproduced by just following this URL to q2view that points to the problematic artifact: https://view.qiime2.org/?src=https%3A%2F%2Fdocs.qiime2.org%2F2019.7%2Fdata%2Ftutorials%2Fimporting%2Femp-paired-end-sequences.qza

This doesn’t seem like that big of a file (pretty sure I’ve thrown heavier stuff at q2view in the past :), so I’d be curious as to why this error is happening. But it’s not a large issue at all.

edit: looks like this problem impacts a few of the other artifacts listed on the page, including emp-single-end-sequences.qza, and demux-single-end.qza. (Interestingly, demux-paired-end.qza seems ok?)


Hey there @fedarko!

I just loaded the link up on FF68:

I wonder if for some reason the Accept-Ranges header wasn’t being set appropriately when you checked earlier (not sure off the top of my head if that is strictly server-supplied, or if the client has to somehow negotiate that header):

When I load that link right now the Accept-Ranges header is set (which means the size check branch is skipped).

1 Like

Hi @thermokarst! Oh man, I think this might be another funky browser issue.

The link works for me in Firefox (version 68.0.1) also—but I consistently get this error in Chrome, both in version 77.0.3865.90 (on a macOS laptop) and in version 77.0.3865.92 (on an Android phone).

I just checked and the error also occurs in Safari (version 12.1.2). The problem persists in incognito/private mode in Chrome/Safari, also. That this error persists across multiple devices and browsers leads me to think that this isn’t an intermittent issue.

In the Chrome browser console, I get pretty much the same error as is displayed on the page: Uncaught (in promise) Error: File is too large (32997106 bytes) and the server does accept the "Ranges" header at resolve.js:34.

Similarly, the Safari JS console gives me the error Unhandled Promise Rejection: Error: File is too large (32997106 bytes) and the server does accept the "Ranges" header. (The listed line here, though, is index.js:126.)

I’m not really sure what to do with this information… my guess is the non-Firefox browsers are maybe handling the Accept-Ranges header in a idiosyncratic way (or vice versa :)?

Thanks for your help with this!

1 Like

Sorry I lost track of this topic.

Worth mentioning, the ranges header is kind of a red-herring here, in that even if the server did support it, nothing useful would happen as the zip library we use doesn’t have a way to abstract over the IO so I can’t really proxy seek calls against a remote server via ranges.

That said, browsers should be agreeing on which branch to take in this code :expressionless: so something should probably change to make the requests similar in different browser’s networking stacks (I hope a plain old XMLHTTPRequest will just “fix” this).

We can also probably increase the cap from 15MiB which is kind of low nowadays.

I’m sorry if this original message came off as rude, it wasn’t my intention, but re-reading it can definitely be seen as a little dismissive, so again I apologize.

Looking at the code again, I don’t see a very compelling reason to have any of this branching (especially if browsers are interpreting it differently like @fedarko found) . I think originally the goal was to prevent the browser from giving an OOM exception as the JS heap is only around 4gb, but it seems like that isn’t worth worrying about at this point.

We should still figure out how to do actual range-requests someday, which would let us handle arbitrarily large visualizations (as long as those visualizations can stream data). But until then, I made a PR stripping the above logic:


@ebolyen I don’t think your original message sounded rude! I really appreciate you all taking the time to handle the weird issues like this that QIIME 2 users like me run into :slight_smile:

The main reason I reported this issue to you all was that it seemed like a general problem that’d impact people following the tutorials – so alleviating that problem (for now, at least) sounds great.

1 Like