-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some items populate with duplicate dates #196
Comments
This is the main open issue I think that we still have to work on - anyone around at CSV tomorrow nite? I'll be there, happy to help figure it out. |
Yeah, I can look into it tomorrow night with you. |
@cezary4: I can't really duplicate this error. when I look at the suspicious tables after they've been parsed, they look like this: This makes me think that the problem isn't the fixies but perhaps date parsing? Let's keep this open for now, but I'm not sure how to approach the solution right now. |
I just replicated it - run this query in the API: http://api.treasury.io/cc7znvq/47d80ae900e04f2/sql/?q=SELECT "table", 8/30 appears twice when you output through API; so the underlying CSV Cezary On Fri, Dec 20, 2013 at 1:47 PM, Brian Abelson [email protected]:
Cezary Podkul | @cezary |
Weird, the problem seems to be that the parser is pulling in multiple files, check the urls in these "duplicate" records:
One is from |
OHHHH I GET IT. At one point our parser downloaded |
That explains it. Though I thought we had put in a line in the parser to On Fri, Dec 20, 2013 at 2:22 PM, Brian Abelson [email protected]:
Cezary Podkul | @cezary |
fixed. |
Thanks for taking a look at this -- I checked to see if there were any 2013-07-29 Here is a query that flags them:
Treasury.io picked up two fixies for each of those dates, which is why
It looks like FMS uploaded a second one with an 01 at the end, which Can we tell it to just pick up the latest one on days where there are This is the last major item on the issues list; thanks everyone for Happy holidays, Cezary |
It looks like the issue is that the function that requests the fixies DOES NOT download the most recent file, instead it actually downloads ALL THE AVAILABLE FILES. It seems that it was written with the built in assumption that there would only ever be one version of the file on the server. In the case of the dates in question, this must not have been the case. At least for a brief period of time. See this function: I'll work on patching this so that it more intelligently requests the fixies. |
Actually, nevermind, the |
Honestly, I can't figure out why a file would be duplicated. It seems like everything in our software should handle this. The best I can do is write a test to check for duplicated dates. See this issue: #198 |
Hey guys, I noticed that sometimes the withdrawals table populates with two entries for the same item. This appears to be rare, but we should get to the bottom of why it happens. Here are the three dates for which it happened for the 'Federal Salaries' line item. I checked and Treasury did not reissue corrected statements that day, which could have been one possible explanation for the dupe. @bdewilde @abelsonlive any ideas why this would happen?
Here is the query to pick up the duplicate days:
And here are the duplicate dates picked out by query:
The text was updated successfully, but these errors were encountered: