HydroShare on Jupyter 0.1.3
Issue when downloading an entire resource from backend. Previously, resources were unzipped to data_path / resource_id. They are now, correctly, unzipped to data_path / resource_id / resource_id. Issue with resource files being shown as only local, when they are in-sync. This was likely because when a file was downloaded from hydroshare and moved to the correct file-system location, the remote fs resource map had not completed its update causing all files to appear as local.
Changes
- Fixes unpacking location of entire resource upon download.
- Fixes remote fs resource map race condition, where files might have appeared to only be on the local system.
- websocket handler no longer subscribes to resource downloaded and resource entity downloaded events. Given that the current event system dispatches callbacks sequentially in the order of subscription (works like queue), if the websocket were to have subscribed to these events before the aggregate filesystem (the aggregate filesystem updates itself based off of these events), it was possible to have a false state.