Peter Amstutz [Thu, 25 Sep 2014 19:01:44 +0000 (15:01 -0400)]
3899: Shorten count of ended/succeed/failed in a-r-p-i with some clever Ruby.
Improve reporting to test for state == Cancelled instead of looking at
cancelled_at, and distinguish between cancelled the state being unexpectedly
changed to success/failed. pipeline_instances_helper uses state attribute.
Peter Amstutz [Wed, 24 Sep 2014 17:28:58 +0000 (13:28 -0400)]
3988: Update crunch-job, arv-run-pipeline-instance and workbench to read/write
"state" field of jobs instead of using running/success (+
cancelled_at/started_at/finished_at) to figure out what state the job is in.
3038: if there is a unique constraint violation when a collection is removed from a project,
which happens if there is already a collection with that same name in the Home project,
rename the collection to ensure the removal process can complete.
Peter Amstutz [Tue, 23 Sep 2014 15:20:16 +0000 (11:20 -0400)]
3605: Rename "default_show" to "title_and_buttons". Revert capitalization
change to "curl". Eliminate excess top margin on page title. Restored
RunningOnClient to running list.
3038: Recommended default port number related update. Now the defaults are as follows:
API server (dev mode): 3030
API server (test mode): 3000
Workbench (dev mode): 3031
Workbench (test mode): 3001
Peter Amstutz [Tue, 23 Sep 2014 14:38:07 +0000 (10:38 -0400)]
3605: Filter out nodes that have a last ping time of more than 1 hour. Add
queue to compute status panel. Refactor utc-date spans to
render_localized_date().
Peter Amstutz [Mon, 22 Sep 2014 18:56:22 +0000 (14:56 -0400)]
3605: Change runtime() to render_runtime(). Improve rendering when started_at
and finished_at are missing from pipelines and tasks. Include count of days
when rendering run times. Add comments.
Tom Clegg [Mon, 22 Sep 2014 14:23:16 +0000 (10:23 -0400)]
3894: Use git log --first-parent to get nearest commit/merge on
current branch to label package version, rather than nearest
commit. This ensures the package version number increases when an
older commit is merged after a newer commit.
Tom Clegg [Fri, 19 Sep 2014 15:27:41 +0000 (11:27 -0400)]
3894: gem version numbers reflect latest commit in the subdirectory
where the gem content comes from.
Even if there are more recent commits elsewhere in the source tree,
those changes won't be reflected in the package so there's no need to
increment the package version.
In addition to avoiding the proliferation of packages with no changes
other than the version number, this makes it possible to change an
SDK, predict the gem version that the CI server will build, refer to
that version in a Gemfile elsewhere in the source tree, and push both
changes at once -- without time travel.
Brett Smith [Thu, 18 Sep 2014 21:24:35 +0000 (17:24 -0400)]
3147: FUSE requires a built Python SDK.
Unlike our Ruby Gems, Python package versioning is sensitive to
commits that actually affect the package, rather than the entire
arvados repository. On the plus side, this makes it a little easier
to reliably name a package version that meets our requirements. This
commit does that. Refs #3147.
Brett Smith [Thu, 18 Sep 2014 20:37:18 +0000 (16:37 -0400)]
3147: Rebuild the Python SDK to satisfy FUSE version requirement.
When I wrote the FUSE driver's version dependency, I did my math
wrong, and it's newer than any version of the SDK. This commit will
cause a new SDK to be built with a new version number that satisfies
the dependency. Refs #3147.
Brett Smith [Tue, 16 Sep 2014 21:27:51 +0000 (17:27 -0400)]
3147: Add retry support to PySDK Collection objects.
This required updating the FUSE driver's SafeApi object to better
imitate a real API object, now that CollectionReader will pass it down
to the underlying KeepClient.
Brett Smith [Fri, 12 Sep 2014 12:49:21 +0000 (08:49 -0400)]
3147: Add retry_method to the Python SDK.
This gives us a way to make retry support flexible and consistent
across SDK classes. Any class that has retryable operations should
take a num_retries argument at initialization. Then, the specific
methods that implement those operations should also take a num_retries
argument, which will fall back to the instance's setting by default.
This lets SDK users express their retry preferences wherever it's most
convenient for them.