GETs remote file twice

Open

#264 opened on Aug 5, 2021 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue PRIORITY: High

Dominant language: JavaScript
Stars: 27
Forks: 16
PR merge metrics: No merged PRs in 30d

Description

visiting http://nwbexplorer.opensourcebrain.org/nwbfile=https://datasets-dev.datalad.org/dandi/dandisets/000027/sub-RAT123/sub-RAT123.nwb and looking at apache logs, shows
```
XXX - - [05/Aug/2021:17:05:10 -0400] "GET /dandi/dandisets/000027/sub-RAT123/sub-RAT123.nwb HTTP/1.1" 200 18792
XXX - - [05/Aug/2021:17:05:18 -0400] "GET /dandi/dandisets/000027/sub-RAT123/sub-RAT123.nwb HTTP/1.1" 200 18792

```
with I guess first one to display details, and then 2nd one appears shortly after a spinner in Python tab stops spinning so - for that Python session? ... For a more sizeable http://nwbexplorer.opensourcebrain.org/nwbfile=https://datasets-dev.datalad.org/dandi/dandisets/000005/sub-anm184389/sub-anm184389_ses-20130207_behavior+ecephys.nwb - the same effect of two full 286MB download requests.

```
XXX - - [05/Aug/2021:17:10:55 -0400] "GET /dandi/dandisets/000005/sub-anm184389/sub-anm184389_ses-20130207_behavior+ecephys.nwb HTTP/1.1" 200 299000608
XXX - - [05/Aug/2021:17:11:28 -0400] "GET /dandi/dandisets/000005/sub-anm184389/sub-anm184389_ses-20130207_behavior+ecephys.nwb HTTP/1.1" 200 299000608
```

It seems that ideally it should be avoided, and a singular GET should be sufficient.

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Reproduce the remote NWB file URLs and inspect browser requests alongside the Apache access logs, including the Python tab's loading behavior. Trace the two download requests through the application entry points; done means each remote file is fetched only once while the details and Python views still load.

Written by the indexing model from the issue text.

Assessment

Tech stack: javascript
Domain: backend, web-dev
Issue type: Bug
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 35/100