-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v1.3.1 #550
Merged
Release v1.3.1 #550
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Still debating between using a unix socket in a docker volume (not a bind mount) or using http requests between containers to make this work. Right now, i'm using http requests to test. Unix sockets should be faster or not depending on how docker volumes update each other.
…entire project. (#476) * Modified: Black-ed all the code. Too many developers did not keep the same coding style, all pages are divided in two or three different styles, python black will take care of the minutiae of the formatting. * Added: More detailed documentation in settings.py. * Modified: Reorganized admin, debug and test runner in settings.py * Added: Django-environ. * Added: Staticfiles for gunicorn. * Fixed: typos in settings.py * [WIP] dateutil. * Removed: Tornado is not being used anymore in this project. * Updated: Django to 1.8.19 * Updated: PyYaml * Updated gunicorn. * Alphabetized [Temporary, sort them by usage later.] * Updated: pillow to 5.2.0. * [WIP] Removed paramiko and flower, see description. They are not used and not setup. Flower would be helpful in the future, let's make the app work before adding other elements. * Updated: Django rest framework to 3.3.0. * Fixed: Removed django 1.7 (python < 2.7) compatibility with REST. * [WIP] - Allow all cors in django.
It is better to have them added to the Rodan docker process, instead of having them here.
Force install redis outside of virtual env for travis.
…ogether for django.
* Ensure temporary file is deleted * Catch failure on OOM and wait 10 s. Retry 3 times. This seems to work in most cases when testing locally and doesn't result in the same kind of slow down as with decreasing the concurrency parameter of the celery worker(s).
Typically inputs that belong to that workflow run prevent a resource from appearing as a run result but add an exception for Labeler
* Add support for getting resources in zipfile * Singular "resource_uuid" as GET parameter * Add archive endpoint to routes * Tweaks to make the client happy * Add queue "celery" * Add format=format * Don't return empty zip file * Let FileResponse close StringIO itself According to https://code.djangoproject.com/ticket/29278 this kind of response will close the file-like object itself. * Add test for archive * Make linter happy * Handle files with conflicting names * Use six to get StringIO * Use six.moves.range * Make linter happy since six only in doctests * Restore settings.py. Oops. * Modified: six import * whitespace * replace StringIO with six Co-authored-by: Alex Daigle <alex.daigle2@gmail.com>
Sorry, thought this was removed in the last PR.
This is to allow us to not need to comment in/out these lines to perform migrations.
Description field has no size limit and can contain a list of information for the entire workflow run. Depending on the job, it may contain a large amount of info as it will serialize the settings object with can contain any information needed to be preserved in phases of an interactive job. Since this can be so big and massively increase the response object size and is also not very helpful for finding a workflowrun, remove it.
Already installed due to calvo, but must be explicitly loaded as Resize job uses py3 queue.
Rename existing Classifier job to Non-Interactive Classifier as part of DDMAL/gamera_rodan#8. This should be merged into Rodan for the *same build* as the updated gamera_rodan job. Otherwise default behavior will delete the Classifier job from the database rather than rename it.
* Added: Stub * Created: Work-In-Progress Data Migration * Fixed: Tests * Flake8 * Version update
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.