- !308 [docs] added validation prodedure for web interface Bug 485 to the admin documentation: This merge request adds information given in beat/beat.web#485 about validation procedure for web interface for web admin documentation.
- !309 Fix all the beat dependencies used for CI testing to match the versions used by buildout: Since beat.core is fixed at 1.8.0, the others must also be pinned to their corresponding versions. See release.cfg
- !310 removing Biometrics Evaluation from BEAT definition as the platform has become more generic than that.
- !311 Don't make the test database in memory for beat.cmdline tests. This allows for re-use during the tests rather than recreate everthing from scratch every time.
- !312 Postpone date of users validation and clean up user profiles.
- !313 Patch the cleaning of invalid users: This patch avoids the crash of the cronjob during the cleanup of invalid profiles, depends on !312
- !314 Cleanup model representation: This patch updates the models to show proper string representation with Python 3. This is useful for getting information on Django's admin pages
- !315 Remove google analytics: Fixes #543
- !316 Remove the beta channel from the list in dev.yml: dev.yml is used to test against the latest stable version of the beat packages. The CI build system now uses the new strict channel policy of conda which means that it does not search further after a package is found in a channel. Thus if the specified version is not found, it ends up with an error. See !315 for details
- !317 Improve database map command output: The scripts now lists by default only the users with an active account. There's an option that will print all users with their activate state. The user email has been added to the output.
- !318 Remove .conda and .condarc from docker image when doing deployment: The current conda-concourse-ci image includes wrong configuration
- !319 Add usage time to database: This merge request implements accessibility time handling for database objects. Without dates the database behaviour is the same as now. If dates are added they become only accessible within the range of dates. Experiment configured with these databases won't be re-run after access expiration. Part of beat/beat.web#541
- !320 Add accessibility edition to admin page: Add the missing fields for editing the accessibility date and time in the admin page. Part of beat/beat.web#541
- !321 Fix new experiment save: When pushing a completely new experiment on the platform, an error occurs when calling update_blocks on the cache content check. If the object does not exists, then an exception is rightfully raised. This patch changes that by using get_or_create like of the outputs handling.
- !322 Fix Sign-up/Sign-in form and documentation pointers: This MR fixes sign-up and sign-in forms and improves documentation pointers Fixes #544, #545
- !323 Improve experiment failure/success notification email: This MR targets the notification of experiments success/failure by having a login direction followed by a re-direction to the experiments page. Fixes #546
- !324 Return compatibility information for algorithms and libraries: This merge request implements the retrieval for execution environment used for an algorithm. It cleans the current implementation providing that information to the views and makes it also available on demand through the API. Fixes #548
- !325 Improve new version handling: This merge request refactors the new version handling API wise. It now does not guess what the new version should be. The version value shall be send along the rest of the data so the content of the platform can properly be checked. After this update people shall update to beat/beat.cmdline> version 1.7.1 Related to beat.cmdline#67 Fixes #547
- !326 Fix object existence check in common serialiser: The check worked with SQLite but not with PostgreSQL. In any case, since we have a user object here, there's no reason to not use it directly. Part of #547
- !327 Refactor update creation api: This merge request does the following: - Raise DRF errors rather than returning response to take advantage of the DRF exception handling mechanism - Create serialisers for PUT request to simplify the code - Improve validation checks in several places - Fixes several issues in DRF infrastructure uses - Fixes JSON fields handling - Remove routes that do no fully qualify objects - Implement a custom DRF exception handler that will allow to log errors - Improve testing - Improve permission management
- !328 Improve automatic emails with temporary urls: This MR targets the improvement for automatic emails concerning validation of new users by supervisors/re-validation of users. Fixes #542 Fixes #550
- !329 Fix supervision lists expand: This MR targets expansion of supervision lists and tables Fixes #549
!330 Fix parallel testing on ci: This merge request fixes parallel CI builds in the most simple way. For Linux host,
/dev/shmis used to store the test database and prefix to speedup tests execution. However, on the Gitlab CI, the same machine may run several builds in parallel which means that one run might overwrite data from another one. In order to avoid that two solutions are possible: - Use the database and prefix "in place" (i.e. in the same folder as the code) - Use the various Gitlab provided environment variables to build a path in
/dev/shmto ensure each build has its data in its own directory The first solution was chosen has it is the easiest to put in place.
- !332 Update beat.backend.python version