The PullHandler should be called for any "PUT /pull" request. It expects the request body to be a JSON object encoding a list of block pull requests. Each request is an object that specifies the locator of the block to be pulled, and an ordered list of servers to pull from. Example pull list: <pre> [ { "locator":"e4d909c290d0fb1ca068ffaddf22cbd0+4985", "servers":["keep0.qr1hi.arvadosapi.com:25107","keep1.qr1hi.arvadosapi.com:25108"] }, { "locator":"55ae4d45d2db0793d53f03e805f656e5+658395", "servers":["10.0.1.5:25107","10.0.1.6:25107","10.0.1.7:25108"] }, ... } </pre> The pull list should be stored in memory. Any previously sent pull list is discarded and replaced with the new one.

Once #3354 branch is merged, the project description in the dashboard should display the formatted description rather than the entered text verbatim.

Depends on 3149-filter-any branch.

Previously when Workbench rendered a project tree menu, the root project was not selectable, and so it didn't get a highlight on hover. Now the root project is the Home project, which is selectable, so it should get the hover effect too.

Note: reported bugfix is actually in 3660.

Please compare against branch 3112-report-bug branch (in case you review it before I merge that branch into master). Thanks.

Please compare against branch 3112-report-bug (in case you review it before I merge that branch into master). Thanks.

should probably be implemented as a sort of colofon, maybe in the footer. "This is Arvados Workbench version 'git rev' running against Arvados API server version 'git rev'". Add a link to the arvados homepage. You can find the git revision for the running workbench code version under the 'git_revision' key in the configuration (application.yml). Make sure you can handle git_revision not being present in application.yml - in that case you can probably print something like "No version information available". The deployment procedure will fill in that value in application.yml.

Add source_version to application.default.yml and make it available as source_version in discovery doc.

And add functional tests.

and update tests to test the button.

Needs #3593 resolved.

(TC) This removes the requirement that clients predict the UUID of a collection before calling create(). Aside from simplifying clients, this makes it possible to start modifying clients to be compatible with #3036.

* PUT requests should update the modification time of a block on success. (The Volume interface should provide a volume.Touch method for this.) * DELETE requests should check the timestamp of a block before deleting it.

Branch ready for review.

just one line change

commit:c5f8a89d

* Add @user_profile_notification_address@ configuration setting in @application.default.yml@ for recipient address (default = false, meaning no notifications are sent) * Send a notification email when a user's @prefs['profile']@ changes from nil to a hash

Otherwise, after "login as" a different user, the profile page will be displayed. And, this needs to be filled in before any other page can be accessed. Hence, when an admin user is logging in as a different user, skip the profile check.

Add a "message" field to config. This field can be used by the site administrator to configure a message to be displayed at the top of the profile page. This came from Adam during the review feedback.

Tom proposed this on Friday and felt that this would be a much better user experience.

At commit:a69da9e