girder_worker icon indicating copy to clipboard operation
girder_worker copied to clipboard

Distributed task execution engine with Girder integration, developed by Kitware

Results 75 girder_worker issues
Sort by recently updated
recently updated
newest added

Provide a set of volumes that can be mounted in all docker containers. This could be in the config file, for instance. Specifically, this could be used to allow docker...

enhancement

This was introduced as an issue in PR #96. This happens both with implicit pulls and explicit pulls, including running BusyBox. Specifically, there is no equivalent of *not* specifying `--all-tags`...

This isn't related to the celery refactor necessarily, but would be good to be done after all of that churn settles down. Additionally, making it so that pip installing girder-worker...

legacy

If a task times out (via Celery), the task failure hook should be able to tell that the exception that caused the task to fail was a time limit exception....

enhancement

Currently item_tasks can pull Docker containers from public DockerHub, but it would be desired by customers in the context of Algorithm-as-a-Service that they keep their code in private repos. >For...

enhancement

### Deliverables + Demonstrate syntax like the following from girder REST endpoint: ```python grp = celery.group([task.delay(item_id) for item_id in items]) grp.delay() ``` ### Technical Notes + Note that celery.group is...

enhancement
canvas

Currently it's very difficult to determine what went wrong with a task running in Girder worker. Our logging functionality should be defined, which should include details such as: - The...

enhancement

How should restarting Girder worker during deployment function? Sometimes the service may need to be restarted but have running tasks, can a soft restart be accomplished with a specific kill...

devops

Our Dockerfiles make use of [wait-for-it](https://github.com/vishnubob/wait-for-it) but execute the entrypoint scripts regardless of whether or not the service is up. The examples for wait-for-it show that the --strict flag is...

devops