Marten Veldthuis
Marten Veldthuis
``` $ ~/rgoc/chef git:(2409m|littlechef✗) fix node:10.210.100.23 deploy_chef Are you sure you want to install Chef 0.10 on node 10.210.100.23, using "sudo: unable to resolve host stag-test1.roqua.nl lucid" packages? [Y/n] y...
If you add Bogus, you lose RSpec's `double`, and the syntax for `stub` changes. Is there any way of incrementally adding Bogus to an existing codebase? We're on RSpec 2.14...
These can be removed after some time has passed: * `organization_contents` table * `project_contents` table * `workflow_contents` table * `versions` table
AFAIK we're now running everything through Caesar when it comes to aggregations. Perhaps we can think about removing aggregations altogether from Panoptes. Clears a bit of memory from the DB...
So, @mrniaboc has this presentation where he does the following things: - create a new project - upload a bg image - upload 3 subjects - create a new workflow...
What happens currently is that people just unlive their project, make edits, and relive. All it really does is prevent accidental edits to the workflow. But since liveness and publicness...
We want to be able to query the projects listing such that we only get back projects that are known to work correctly in the mobile app. For this, adding...
I can reproduce this. It might be due to the congestion configuration being set to `cancel`.
This new field should be the timestamp that gets touched on each classification, instead of the `updated_at`. We're touching `updated_at` for each classification so that the front-page can sort UPPs...
We're missing a FK between projects and workflows, so: ``` sql SELECT * FROM workflows LEFT OUTER JOIN projects on workflows.project_id = projects.id WHERE projects.id IS NULL; ``` returns 22...