Errors on the 31st day
-
Here is what happened: we deployed a small fix to a notoriously bad web application this morning. The application accepts invoices from our partners. The fix worked fine but there were problems in the report pages: reports with wrong dates were listed all over the place and one of the report generated error consistently. I spent about two hours trying to figure out what happened. Finally, I found the problem. A web service we use which we did not change this time cannot handle the 31st day of any month. That is, the problme will appear only on 1/31, 3/31/ 5/31, 7/31, 8/31, 10/31, and 12/31. On these dates, the report links on our web page will be screwed up. What worse is, this subtle bug also exposes another subtle bug in one of the stored procedures developed by another team. It turns out the stored procedure also cannot handle the 31st day of any month correctly. That's why one of the reports generated error consistently. The web application has terrible user interface and generates a lot of other errors, but despite my repeated requests, the power that be does not want to do anything about it.
My .NET Business Application Framework My Home Page
modified on Friday, February 01, 2008 3:38:56 PM
-
Here is what happened: we deployed a small fix to a notoriously bad web application this morning. The application accepts invoices from our partners. The fix worked fine but there were problems in the report pages: reports with wrong dates were listed all over the place and one of the report generated error consistently. I spent about two hours trying to figure out what happened. Finally, I found the problem. A web service we use which we did not change this time cannot handle the 31st day of any month. That is, the problme will appear only on 1/31, 3/31/ 5/31, 7/31, 8/31, 10/31, and 12/31. On these dates, the report links on our web page will be screwed up. What worse is, this subtle bug also exposes another subtle bug in one of the stored procedures developed by another team. It turns out the stored procedure also cannot handle the 31st day of any month correctly. That's why one of the reports generated error consistently. The web application has terrible user interface and generates a lot of other errors, but despite my repeated requests, the power that be does not want to do anything about it.
My .NET Business Application Framework My Home Page
modified on Friday, February 01, 2008 3:38:56 PM
[Error: can't view comment] But seriously have you found why it can't handle it? Would love to see the code for that :P
-
[Error: can't view comment] But seriously have you found why it can't handle it? Would love to see the code for that :P
One also has to wonder where development was outsourced to..
-
[Error: can't view comment] But seriously have you found why it can't handle it? Would love to see the code for that :P
Steve Hansen wrote:
But seriously have you found why it can't handle it?
Yes, but it is company secret/property, imaging our competitors learned how to pull stuff like that. :)
-
One also has to wonder where development was outsourced to..
Unfortunately, it is an "inside" job. But they are untouchable now, they are either team players (process followers) or have moved to different team/company already.
-
Here is what happened: we deployed a small fix to a notoriously bad web application this morning. The application accepts invoices from our partners. The fix worked fine but there were problems in the report pages: reports with wrong dates were listed all over the place and one of the report generated error consistently. I spent about two hours trying to figure out what happened. Finally, I found the problem. A web service we use which we did not change this time cannot handle the 31st day of any month. That is, the problme will appear only on 1/31, 3/31/ 5/31, 7/31, 8/31, 10/31, and 12/31. On these dates, the report links on our web page will be screwed up. What worse is, this subtle bug also exposes another subtle bug in one of the stored procedures developed by another team. It turns out the stored procedure also cannot handle the 31st day of any month correctly. That's why one of the reports generated error consistently. The web application has terrible user interface and generates a lot of other errors, but despite my repeated requests, the power that be does not want to do anything about it.
My .NET Business Application Framework My Home Page
modified on Friday, February 01, 2008 3:38:56 PM
-
Here is what happened: we deployed a small fix to a notoriously bad web application this morning. The application accepts invoices from our partners. The fix worked fine but there were problems in the report pages: reports with wrong dates were listed all over the place and one of the report generated error consistently. I spent about two hours trying to figure out what happened. Finally, I found the problem. A web service we use which we did not change this time cannot handle the 31st day of any month. That is, the problme will appear only on 1/31, 3/31/ 5/31, 7/31, 8/31, 10/31, and 12/31. On these dates, the report links on our web page will be screwed up. What worse is, this subtle bug also exposes another subtle bug in one of the stored procedures developed by another team. It turns out the stored procedure also cannot handle the 31st day of any month correctly. That's why one of the reports generated error consistently. The web application has terrible user interface and generates a lot of other errors, but despite my repeated requests, the power that be does not want to do anything about it.
My .NET Business Application Framework My Home Page
modified on Friday, February 01, 2008 3:38:56 PM
I once had to test an application (for an extraordinarily heavily regulated industry) which generated reports of activity on a per month basis. The developer made a few assumptions, namely every month had 30 days, including February, and there was no October!
I have no blog...
-
I once had to test an application (for an extraordinarily heavily regulated industry) which generated reports of activity on a per month basis. The developer made a few assumptions, namely every month had 30 days, including February, and there was no October!
I have no blog...
-
I once had to test an application (for an extraordinarily heavily regulated industry) which generated reports of activity on a per month basis. The developer made a few assumptions, namely every month had 30 days, including February, and there was no October!
I have no blog...
-
The guy was a French Revolutionary [^]. :-D
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
[my articles]If so he would not mention february either, but name all months differently, as in Pluviose, Ventose, Germinal, ... :)
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.
-
If so he would not mention february either, but name all months differently, as in Pluviose, Ventose, Germinal, ... :)
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.
That kind of people was so fascinating indeed... :-D
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
[my articles] -
I once had to test an application (for an extraordinarily heavily regulated industry) which generated reports of activity on a per month basis. The developer made a few assumptions, namely every month had 30 days, including February, and there was no October!
I have no blog...
Liam O'Hagan wrote:
and there was no October!
I don't know if you were teasing me that I left out 10/31 in my original post. :-D
-
Steve Hansen wrote:
But seriously have you found why it can't handle it?
Yes, but it is company secret/property, imaging our competitors learned how to pull stuff like that. :)
Xiangyang Liu wrote:
but it is company secret/property
Holy Crap! They call that sh*t as intellectual property!!
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
Makes me wonder what will happen on February 29th :)
Faith is a fine invention For gentlemen who see; But microscopes are prudent In an emergency! -Emily Dickinson
General Protection Fault and a blue screen!
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
I once had to test an application (for an extraordinarily heavily regulated industry) which generated reports of activity on a per month basis. The developer made a few assumptions, namely every month had 30 days, including February, and there was no October!
I have no blog...
Liam O'Hagan wrote:
The developer made a few assumptions, namely every month had 30 days, including February
:eek: Every month has at least 28 days :laugh:
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
