Using the admin interface to proceed to the next topic in the meeting causes the database to respond with the following error message:
db | ERROR: relation "agenda_item" does not exist at character 29
db | QUERY: SELECT EXISTS(SELECT 1 FROM agenda_item WHERE agenda_item.id=set_current_agenda_item.id)
db | CONTEXT: PL/pgSQL function api.set_current_agenda_item(integer) line 5 at IF
db | STATEMENT:
db | WITH pg_source AS (select "api"."set_current_agenda_item"("id":='2'::unknown))
db | SELECT
db | null::bigint AS total_result_set,
db | 1 AS page_total,
db | (row_to_json(_postgrest_t)->'set_current_agenda_item')::character varying AS body,
db | coalesce(nullif(current_setting('response.headers', true), ''), '[]') AS response_headers
db | FROM (SELECT "pg_source".* FROM "pg_source" ) _postgrest_t;
Setup: Docker setup
How to reproduce
Run docker-build.sh
Load attached mote.txt (really mote.tex, but Github don't like that extension)
with lemmingtools-exe
What
Using the admin interface to proceed to the next topic in the meeting causes the database to respond with the following error message:
Setup: Docker setup
How to reproduce
Then you'll be greeted with something that looks like this: