ace issueshttps://gitlab.umiacs.umd.edu/adapt/ace/-/issues2017-12-06T11:42:16-05:00https://gitlab.umiacs.umd.edu/adapt/ace/-/issues/45Deploy to Obj from pipeline2017-12-06T11:42:16-05:00Ghost UserDeploy to Obj from pipelineWe can streamline our deploy process a bit more to include creating our release artifacts for us and pushing them to obj. Since this is all cli based, we should be able to update the .gitlab-ci.yml in order to accomplish this.
The files...We can streamline our deploy process a bit more to include creating our release artifacts for us and pushing them to obj. Since this is all cli based, we should be able to update the .gitlab-ci.yml in order to accomplish this.
The files needed to be uploaded are
* ace-$VERSION-src.tar.gz
* ace-dist-$VERSION-RELEASE-bin.tar.gz
* ace-dist-$VERSION-RELEASE-bin.ziphttps://gitlab.umiacs.umd.edu/adapt/ace/-/issues/34Paginated pull of content in Browse Servlet2018-01-23T08:32:46-05:00Ghost UserPaginated pull of content in Browse ServletIn the browse servlet, folders with a large number of items can cause the Audit Manager to choke while it fetches everything from the database. We should aim to pull only a subset of items at a time.In the browse servlet, folders with a large number of items can cause the Audit Manager to choke while it fetches everything from the database. We should aim to pull only a subset of items at a time.https://gitlab.umiacs.umd.edu/adapt/ace/-/issues/40Additional Collection States2018-01-23T08:32:47-05:00Ghost UserAdditional Collection StatesIn the event of an audit failure (interrupt, network, etc), we want this information to be easily available to the user. This should be able to be completed without the need for too many changes through the collection state.In the event of an audit failure (interrupt, network, etc), we want this information to be easily available to the user. This should be able to be completed without the need for too many changes through the collection state.1.12https://gitlab.umiacs.umd.edu/adapt/ace/-/issues/38Compare API2018-01-23T08:32:47-05:00Ghost UserCompare APIAdd a rest API mimicking the 'Collection Compare' servlet we have. It taken in something with a data structure like, List<Tuple>, where our Tuple is a (path, hash). The tuple will be a named class, but that can be determined later.
The ...Add a rest API mimicking the 'Collection Compare' servlet we have. It taken in something with a data structure like, List<Tuple>, where our Tuple is a (path, hash). The tuple will be a named class, but that can be determined later.
The response should be similar to the Compare servlet as well, showing items which are the same, different, or not found.1.12https://gitlab.umiacs.umd.edu/adapt/ace/-/issues/32REST access for corrupt collections + files2018-01-23T08:32:47-05:00Ghost UserREST access for corrupt collections + filesWe're going to want easy access to see what collections are corrupt, and from those what files are corrupt in a collection. This should be pretty straightforward:
* `/rest/collections` with some various query parameters
* `/rest/collect...We're going to want easy access to see what collections are corrupt, and from those what files are corrupt in a collection. This should be pretty straightforward:
* `/rest/collections` with some various query parameters
* `/rest/collections/{id}/corrupt` or something for viewing fileshttps://gitlab.umiacs.umd.edu/adapt/ace/-/issues/49Add Remove All to Report2018-05-22T15:03:05-04:00Ghost UserAdd Remove All to ReportAllow removal of all corrupt/missing/etc monitored_items from a ReportAllow removal of all corrupt/missing/etc monitored_items from a Reporthttps://gitlab.umiacs.umd.edu/adapt/ace/-/issues/51Single session when removing items2018-05-16T13:30:29-04:00Ghost UserSingle session when removing itemsWhen issuing a remove, a new session is used for each log event which is created. It would be nice to tie together batch removals in a single session so it can be queried easily from the event log.When issuing a remove, a new session is used for each log event which is created. It would be nice to tie together batch removals in a single session so it can be queried easily from the event log.https://gitlab.umiacs.umd.edu/adapt/ace/-/issues/60Servlet for Active Audits/Token Imports2019-04-04T14:23:38-04:00Ghost UserServlet for Active Audits/Token ImportsIn the ACE AMs for the Chronopolis Project, we've been ingesting large amounts of collections. We've noticed recently when trying to browse it is difficult to find out which collections are actively auditing, and it's almost impossible t...In the ACE AMs for the Chronopolis Project, we've been ingesting large amounts of collections. We've noticed recently when trying to browse it is difficult to find out which collections are actively auditing, and it's almost impossible to see what collections are ingesting tokens.
Given that these both use the same thread pool, as they are processes which modify collections, it would be nice to have a servlet which can show any active processes. We will probably want to show information from the audit/token ingest when browsing the collections in this servlet. Maybe retrieving information from the CollectionThreadPoolExecutor. As this is still in its conception, nothing is really set in stone yet.