The frontline support team will be unavailable to answer questions on April 15th and 17th 2019. We will be back soon after. Thank you for your patience and we apologize for any inconvenience!
Release Notes can be found here.
Release notes: June 2017
June 29, 2017
- When creating or editing methods or method namespaces, you will be restricted to using only letters (
a-z), numbers (
0-9), underscores (
_), dashes (
-), and periods (
.). For more information on why we are doing this, as well as the effect this may have on you going forward, please read here.
- Fixed a bug where right-clicking to download workspace files could fail with an authorization error.
June 22, 2017
- As the owner of a method or method configuration, you now are able to edit the synopsis, description, and WDL to create a new snapshot of your method or method configuration from the Method Repository. The access control list for this method will be imported to the new snapshot.
- In "Method Configurations" when you click the "Import Configuration..." button, you will now have the option to copy a method configuration from another workspace. Previously you could only copy a method configuration from the Methods Repository. This allows you to share Method Configurations without publishing them to the Method Repository.
- For our API users, you can now
deleteworkspace tags through the API endpoint.
- Again using the API, you can now retrieve Library metadata and Library discoverable-groups values on individual workspaces.
- When viewing the details of a list entity, the single-entity viewer will now render the list properly.
- In Chrome, certain error messages were not displaying properly. These missing or incomplete messages are now fixed when you try to view a non-existent workspace, or when you attempt to edit a namespace to which you are a reader.
- Workspace and submissions icons now correctly reflect the status of the workflows. Previously they would show green if some workflows failed but other subsequently succeeded. Now they show red if any workflow in the submission failed. The most recently completed submission determines the status of the workspace icon.
- We fixed an error when malformed column default attributes were loaded into the workspace which would not allow you to navigate between data tabs. The error no longer occurs and you can navigate as you wish.
June 19, 2017
- FireCloud is now upgraded to Cromwell version 27. For notes on the new version of Cromwell, read here
- In the Launch Analysis page, you can now click anywhere in the table row to select an entity, regardless of what columns are visible.
- When you try to set an invalid namespace on a config output, you will receive an error message now instead of a blank modal.
- When a new user receives an email invitation to a workspace, they can now click the "Sign up" link, register, and be taken directly to the workspace that the invitation was sent for.
June 12, 2017
- FireCloud's email system is back and functional. It will now properly send workspace sharing emails to both existing users and new users.
June 8, 2017
The TCGA controlled access Authorization Domain has been renamed from dbGapAuthorizedUsers to TCGA-dbGaP-Authorized.
This change will allow us to support multiple distinct dbGaP-mediated datasets in the future.
If you navigated to the second (or later) page of the workspaces list and applied a text filter that did not return very many items, you could end up with no results displayed. Now, we jump back to the first page to avoid confusion.
- We have improved the messaging shown when you link your NIH account to FireCloud but do not have authorization to see any protected NIH datasets. Previously, we would display the error "Failed to link NIH account". This was incorrect. In the event that you don't have access to a protected dataset, we will display instructions for checking your credentials with the NIH.
- Previously you would need to refresh the page in order to see new workspace attributes you just imported. Now you will see these display with their new values after importing
- When you cancel editing a method configuration, the information on the page will revert to its original state before you made any edits. Previously there were some fields that would keep the edited info until you refreshed the page.
- If you remove all data from an entity column, the column will now no longer display. Previously it would display the header for the column with no data filled in.
- Clicking outside of dropdown menus now causes them to be dismissed.
June 1, 2017
In the Methods Repository, you can now create a new snapshot of an existing method if you have OWNER permission on at least one previous snapshot.
If you are creating a brand-new method (e.g. no previous snapshot exists), the previous behavior applies: you need OWNER permission on the target namespace.
A workspace is shared with you, and it uses a group you are not a part of as its Authorization Domain. You are now able to request access to the group from the workspaces list. This will send an email to the admins of the group letting them know you would like to be added as a member of their group.
- In the Monitor tab when looking at a run's details, there is an ID associated with the call which contains JES level metadata. Previously you would have to look up the ID on gcloud, but now you can simply click the link ID and be shown the JES-level metadata.
- On the Methods Repository detail page (i.e. inside a method or config), the "Permissions" and "Redact" buttons are now disabled if you do not have permissions to use them.
- FireCloud now uses a single Cromwell instance. Previously we used two Cromwell instances, and if your first call was run on Cromwell #1 and the second call was run on Cromwell #2, the cached call would not be recognized and the job would run again.
- Fixed a bug where users with no billing projects were unable to share workspaces.
- Fixed a bug where importing an empty TSV gave you an error. Now it doesn't!
- Due to a bug, links to other entities within an entity's metadata were not displayed in the data table. This has been fixed.