| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Website Support
Thread: API Returning Different ReportDeadline Dates |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
foxfire
Advanced Cruncher United States Joined: Sep 1, 2007 Post Count: 121 Status: Offline Project Badges: 
|
The API is returning ReportDeadline dates that are different from the first and last time pulled. The status of the following changed from In-Progress and Pending Verification to Valid between pulls and the ReportDeadline changed. This is not occurring for all WUs that change status to valid between pulls (654 status changed, 12 ReportDeadline different).
----------------------------------------WorkunitId ResultId First ReportDeadline Last ReportDeadline  |
||
|
|
TonyEllis
Senior Cruncher Australia Joined: Jul 9, 2008 Post Count: 286 Status: Offline Project Badges: 
|
Exactly two days... Possibly as a resullt of this?
----------------------------------------knreed wrote in the thread "World Community Grid Moves to IBM Cloud" One of our first steps in our cut-over plan is to "Extend report deadline for all in progress results by 2 days". This will address any issues with results that might become overdue while clients are unable to access the website.
Run Time Stats https://grassmere-productions.no-ip.biz/
|
||
|
|
foxfire
Advanced Cruncher United States Joined: Sep 1, 2007 Post Count: 121 Status: Offline Project Badges:
|
The two days seems to be luck of the draw for the pull I referenced. I have seen times when the ReportDeadline is less the SentTime and others when the difference is hours, or more or less than the 2 days.
---------------------------------------- |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Think you had a reply [someone recently] had a reply from armstrdj on the matter of seeming random changes of sent times, some turning [temporarily] to be later than the received time and some such [without any consequence as it would return to correct later on... suspecting some array that is not cleared before next read-in pass.
|
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
I have seen times when the ReportDeadline is less the SentTime. Have you seen this in the past couple of days (i.e. since the migration) or is this comment based on previous experience before the migration? I'd like to get a list of oddities (we have captured some of the reported issues, but I want to make sure we have the all) in the API because we should be able to dive into looking at this in the next few weeks now that the migration is done. However, I'd like to make sure that we are only discussing things observed since the migration and not before since there are a lot of changes there were part of the migration. |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Recently Active Project Badges: 
|
I did a quick search and found 7 peculiarities since the migration in my API results:
ResultId WorkunitId ModTime Exit Outc SentTime ReceivedTime Name |
||
|
|
foxfire
Advanced Cruncher United States Joined: Sep 1, 2007 Post Count: 121 Status: Offline Project Badges:
|
As an add to adriverhoef post, yes, I've seen ReportDeadline change to less than SentTime since the migration and have also seen changes to SentTime as well (both types in app oet1).
----------------------------------------When I first encountered it I thought the problem was in my pull program and it took me a couple of days to determine it was in the API data. Because of that I will have to compile the doc going forward. I'll post what I see to this thread. Thank you for the response |
||
|
|
foxfire
Advanced Cruncher United States Joined: Sep 1, 2007 Post Count: 121 Status: Offline Project Badges:
|
I have seen times when the ReportDeadline is less the SentTime. Have you seen this in the past couple of days (i.e. since the migration) or is this comment based on previous experience before the migration? I'd like to get a list of oddities (we have captured some of the reported issues, but I want to make sure we have the all) in the API because we should be able to dive into looking at this in the next few weeks now that the migration is done. However, I'd like to make sure that we are only discussing things observed since the migration and not before since there are a lot of changes there were part of the migration. The night of 05/25/2017 140 records were returned with different SentTime, ReportDeadline and/or ReceivedTime values. For the next 5 nights there were no differences. Tonight 90 records were returned with different values. In addition, 6 WUs were returned with ReportDeadline empty. WU's mossing Report Deadline: OET1_0004730_x4O6HchD_rig_93136_1 OET1_0004729_x4O6HchD_rig_31611_0 OET1_0004729_x4O6HchD_rig_28421_0 OET1_0004730_x4O6HchD_rig_82901_0 OET1_0004730_x4O6HchD_rig_84875_0 Examples of different SentTime, ReportDeadline and/or ReceivedTime values: WorkunitId ResultId DiffList fSent fDue fRtn sSent sDue sRtn Hope this helps! |
||
|
|
ErikaT
Former World Community Grid Admin USA Joined: Apr 27, 2009 Post Count: 912 Status: Offline Project Badges: 
|
The night of 05/25/2017 140 records were returned with different SentTime, ReportDeadline and/or ReceivedTime values. For the next 5 nights there were no differences. Tonight 90 records were returned with different values. In addition, 6 WUs were returned with ReportDeadline empty. We are aware of this issue, and the work to fix it is on our backlog at this time. Thank you for your support, ErikaT |
||
|
|
|