You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also noticing that table data don't get reset correctly when moving between a table and one is empty - try toggling between comments and threads, or thread_reactions and threads
The text was updated successfully, but these errors were encountered:
It looks like we get this error when requesting the threads from the API: {"error":"Error: internal error - invalid threads/topic value (expected float)"}. I'm going to try to reproduce this locally...
The /models/:model endpoint for threads is failing with {"error":"Error: internal error - invalid threads/topic value (expected float)"}. This is because the topic column in the threads table has type "number" which is being stored as a number, however in decodePrimitiveValue the code expects this to be stored as a string. Fix here: packages/modeldb-pg - fix returning float columns #431
Also noticing that table data don't get reset correctly when moving between a table and one is empty - try toggling between
comments
andthreads
, orthread_reactions
andthreads
The text was updated successfully, but these errors were encountered: