radhika [Thu, 18 Feb 2016 17:55:25 +0000 (12:55 -0500)]
8441: Update project chooser modal to display favorites and top-level-my-projects and remove the now unused build_project_trees and shared_project_tree code.
radhika [Tue, 16 Feb 2016 17:00:09 +0000 (12:00 -0500)]
8286: also include link to Home in favorites section of the Projects dropdown, so that the user does not have to scroll through all of his favorites to seek in MyProjects section.
radhika [Mon, 15 Feb 2016 22:28:55 +0000 (17:28 -0500)]
8286: to facilitate in-place star icon refresh without the whole page refresh, it became necessary
to refresh the Projects menu after star/unstar action. Hence, moved the breadcrumbs code from
body.html into a partial.
Brett Smith [Fri, 12 Feb 2016 23:38:36 +0000 (18:38 -0500)]
8203: crunch-job tempfails after failing to install a Docker image.
* Use `bash -o pipefail` to run the image installer shell script, to
reliably detect more failures.
* Exit EX_RETRY_UNLOCKED after a failure to install the image.
Refs #8203, because I'm cautiously optimistic that this will reduce
the incidence of the "can't find UID" problem.
radhika [Fri, 12 Feb 2016 21:50:34 +0000 (16:50 -0500)]
8183: while displaying "my projects" tree, just show only the user's projects and omit shared projects
even when there are no more than 300 projects to avoid confusion.
Brett Smith [Wed, 10 Feb 2016 18:19:11 +0000 (13:19 -0500)]
Pin PySDK's gflags dependency to <3.0.
We've built and tested with 3.0 successfully, but its ChangeLog says:
* A lot of potentially backwards incompatible changes since 2.0.
* This version is NOT recommended to use in production. Some of the files and
documentation has been lost during export; this will be fixed in next
versions.
We found out about this after 3.0.2 broke our tests.
Take their advice for now. No issue #.
Brett Smith [Tue, 9 Feb 2016 22:10:08 +0000 (17:10 -0500)]
crunch-job detects more "io aborted" SLURM errors.
It's seemingly random whether SLURM reports "Aborting, io aborted and
missing step" or "Aborting, missing step and io aborted". Extend the
regexp to catch both. No issue #.
radhika [Fri, 5 Feb 2016 23:25:11 +0000 (18:25 -0500)]
8183: add test to check build of my projects tree with the new method; update the method implementation
to accommodate testing by make the page_size an argument.
radhika [Fri, 5 Feb 2016 17:00:58 +0000 (12:00 -0500)]
8183: When there are more than 200 readable projects, build the tree in steps;
fetch projects under home, then subprojects under those projects and so on
until we exceed the 200 limit. In that case, also display a message in Projects
dropdown informing the user that all projects are not retrieved.
The chooser version of the project tree is untouched (and hence not performing well)
until we have the favorite projects implementation is in place. This is because
there is no search capability in the chooser dialog and hence no way to choose a
shared project when the limit is exceeded in this new top-down approach.
Peter Amstutz [Fri, 5 Feb 2016 16:10:43 +0000 (11:10 -0500)]
7667: Combine polling logs into fewer lines for less noise. Adjust message
when last_ping_at is unexpectedly none to be less severe (can happen in
innocent circumstances). Report nodes in "booted" list as "booting" since they
are unpaired. Fix tests.
Brett Smith [Fri, 5 Feb 2016 09:52:43 +0000 (04:52 -0500)]
7868: Update API server's arvados-cli version.
Curoverse clusters are deployed by setting CRUNCH_JOB_BIN,
effectively excluding it from the bundle, but this is not true for
clusters deployed following the install guide. Out of the box,
they'll use the version of crunch-job that's actually in the
arvados-cli gem in the bundle.
crunch-dispatch has functionality in it that requires a newer
arvados-cli, so update accordingly. This is not exactly the version
produced by #7868, but it's pretty close.
I think there's a strong case that we should update this version
whenever we make a substantial change to crunch-job. But since I'm
pushing this without discussion or review, I'm doing the smallest
thing possible.
Tom Clegg [Mon, 1 Feb 2016 06:58:34 +0000 (01:58 -0500)]
8288: Add timeout option to close() method of event clients.
Previously in EventClient, close() didn't wait for anything. Now, if a
timeout is given, it waits for ws4py to call the closed() callback to
indicate the connection has closed.
Previously in PollClient, close() waited indefinitely for the polling
thread to terminate. This can take a very long time if, for example,
there are multiple subscriptions and the "get logs" API transaction is
slow.
The only apparent reason a caller would want to wait here at all is to
guarantee the simplifying assumption the on_event() callback is never
called after close(). Now, instead of letting the thread run until
all events are received and handled, PollClient achieves this the same
way EventClient does: ignore events that arrive after close().
projects / arvados.git / log