From f0a7a846f7ae7a7786239254161d700716ce644f Mon Sep 17 00:00:00 2001 From: Carl Worth Date: Wed, 30 Dec 2020 13:21:55 -0700 Subject: [PATCH] Fix stale usage of "puzzle_table" We no longer haave a separate table for puzzles, but instead the single "turb.table" holds all of our data. This doesn't fully convert this code to the new single-table schema, but it should at least let things pass the flake8 test and deployment. --- turbot/events.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/turbot/events.py b/turbot/events.py index 86a3c83..64430e5 100644 --- a/turbot/events.py +++ b/turbot/events.py @@ -221,14 +221,14 @@ def puzzle_channel_created(turb, puzzle_channel_name, puzzle_channel_id): # string and cleanly return (eliminating all future retries). item['sheet_url'] = 'pending' item['channel_url'] = channel_url(puzzle_channel_id) - puzzle_table.put_item(Item=item) + turb.table.put_item(Item=item) # Create a sheet for the puzzle sheet = sheets_create_for_puzzle(turb, item) # Update the database with the URL of the sheet item['sheet_url'] = sheet['url'] - puzzle_table.put_item(Item=item) + turb.table.put_item(Item=item) # Get the new sheet_url into the channel description set_channel_description(turb, item) -- 2.45.2