I think your problem is probably that the "garbo" database user doesn't have the necessary permissions on that table. You can fix this in `database/schema/security.cfg`: the `[garbo]` section will need something like `public.signedcodeofconduct = SELECT, UPDATE`.
security.cfg changes are applied automatically on rollouts to our various instances, but in a development setup you'll need to run `for db in launchpad_empty launchpad_dev_template launchpad_dev launchpad_ftest_template launchpad_ftest_playground; do database/schema/security.py -d $db; done` (or `make schema`, but that wipes and replaces your local database rather than changing its permissions in place). -- https://code.launchpad.net/~jugmac00/launchpad/+git/launchpad/+merge/410227 Your team Launchpad code reviewers is requested to review the proposed merge of ~jugmac00/launchpad:populate-signedcodeofconduct.affirmed into launchpad:master. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-reviewers Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-reviewers More help : https://help.launchpad.net/ListHelp
