This repository has been archived by the owner on Dec 14, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 87
patch broken topics query to make topic timespan list API endpoint work #833
Labels
Comments
I agree. I can't see how it ever worked as-is. |
philbudne
added a commit
that referenced
this issue
May 18, 2022
Removed extra AND to try to fix #833 as suggested by Rahul.
Image built and containers redeployed using new image. |
Still getting the same exact error. If you're logged into our web tools with an admin account this test URL shows the error:
|
I get a 403 ( User lacks read permission for the requested topic ) for your URL. |
(and/or give me instructions I can try to follow for the test topic in Emily's account, OR give [email protected] access to the topic!) |
Works now! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems everyone is onboard to slowly disable Topic Mapper, but we do need to support people retrieving their data. It'd be nice to do this via the UI, but viewing topics via Topic Mapper is broken right now. The first issue seems to be this:
That error suggests the root is a SQL query syntax problem caused by having two
AND
s in a row. Reading the code quickly, it looks like this line in Timespans.pm is the problem. Each of the clauses on the lines of code just after has anAND
at the front, so the one on this line becomes a duplicate no matter what. I believe removing theAND
on line this could fix this initial problem. Do you read the same bug here?If so, is there an easy way to fix this and redeploy this
webapp-api
container? Of course there is the potential that we'd fix this and something else would be problematic... but I thought it prudent to ask once I saw this.Related: if we can't make topics browsable again, we'll go with plan B. I think that is probably writing a script to generate emails to users with links to the existing topic timespan data dump files (which hopefully exist for all successfully completed topics).
The text was updated successfully, but these errors were encountered: