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
Glados should have an API endpoint and a simple web dashboard feature for getting a list of content keys that had failed recently. This is useful for both manual debugging and for feeding into a bridge node to intelligently plug holes in the dataset.
Previously I made a script for nick to do this for manually debugging:
ssh glados "psql postgres://postgres:password@localhost:5432/glados -c \"\\copy (SELECT DISTINCT c.content_key FROM content c JOIN content_audit ca ON c.id = ca.content_key WHERE ca.result = 0 AND ca.strategy_used = 5 AND ca.created_at >= CURRENT_TIMESTAMP - INTERVAL '24 hours') TO '/home/devops/failed_4444s.txt';\"" && scp glados:/home/devops/failed_4444s.txt ~/failed_4444s.txt
The text was updated successfully, but these errors were encountered:
Glados should have an API endpoint and a simple web dashboard feature for getting a list of content keys that had failed recently. This is useful for both manual debugging and for feeding into a bridge node to intelligently plug holes in the dataset.
Previously I made a script for nick to do this for manually debugging:
ssh glados "psql postgres://postgres:password@localhost:5432/glados -c \"\\copy (SELECT DISTINCT c.content_key FROM content c JOIN content_audit ca ON c.id = ca.content_key WHERE ca.result = 0 AND ca.strategy_used = 5 AND ca.created_at >= CURRENT_TIMESTAMP - INTERVAL '24 hours') TO '/home/devops/failed_4444s.txt';\"" && scp glados:/home/devops/failed_4444s.txt ~/failed_4444s.txt
The text was updated successfully, but these errors were encountered: