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
There are still an assortment of these -- very low probability contingencies, probably -- but they should go to the log, since generally no one is watching the screen except when debugging.
The text was updated successfully, but these errors were encountered:
There's also a lot of info getting printed out during coding that would be nice to have logged rather than printed, while you're at it. For example, I get output like this for every story:
Processing story 5770266d172ab87ec6dc98ef
5770266d172ab87ec6dc98ef_0
FINANCE MINISTER MOSHE KAHLON ON SUNDAY SAID THAT THE FINANCE MINISTRY HAD SET UP A 24-HOUR `` SITUATION ROOM '' TO KEEP TABS ON ECONOMIC REPERCUSSIONS FROM THE UNITED KINGDOM 'S THURSDAY VOTE TO BREAK FROM THE EUROPEAN UNION .
NPgm-rec-2: ~GOV
NPgm-rec-1: ISRGOVMED
NPgm-rec-1.1: (u'ISRGOVMED', [u'>090401'])
NPgm-rec-2: ~GOV
There are still an assortment of these -- very low probability contingencies, probably -- but they should go to the log, since generally no one is watching the screen except when debugging.
The text was updated successfully, but these errors were encountered: