Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 
World Community Grid Forums
  Category: Support
  Forum: Website Support
  Thread: API Returning Conflicting Data

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 32
Posts: 32   Pages: 4   [ Previous Page | 1 2 3 4 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 3508 times and has 31 replies Next Thread
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2166
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
Sometimes the API returns an incorrect date in a date field:
       {
           "AppName": "scc1",
           "ClaimedCredit": 50.73148905626898,
           "CpuTime": 9.4197359085083,
           "ElapsedTime": 18.6638126373291,
           "ExitStatus": 0,
           "GrantedCredit": 50.73148905626898,
           "DeviceId": *******,
           "DeviceName": "android_********",
           "ModTime": 1491323617,
           "WorkunitId": 2028561759,
           "ResultId": 1360765959,
           "Name": "SCC1_0000239_Lin-ZNF-A_79778_0",
           "Outcome": 1,
           "ReceivedTime": "2017-04-12T17:47:18",  
           "ReportDeadline": "2017-04-12T02:49:05",
           "SentTime": "2017-04-02T02:49:05",
           "ServerState": 5,
           "ValidateState": 1,
           "FileDeleteState": 2
        },
No need to say, the ReceivedTime lies 8 days in the future!

Another example:
           "ModTime": 1491245554,
           "WorkunitId": 2030671392,
           "ResultId": 1363604923,
           "Name": "FAHV_1003659_3j3y-_D-P4_30488_0",
           "Outcome": 1,
           "ReceivedTime": "2017-04-03T18:52:23",
           "ReportDeadline": "2017-04-13T17:47:54",
           "SentTime": "2017-04-13T16:43:17",  
           "ServerState": 5,
           "ValidateState": 1,
           "FileDeleteState": 2
The SentTime lies 10 days in the future!
[Apr 4, 2017 5:53:57 PM]   Link   Report threatening or abusive post: please login first  Go to top 
SekeRob
Master Cruncher
Joined: Jan 7, 2013
Post Count: 2741
Status: Offline
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
Can't be bothered reading the underlying server code, but, looking at filedeletestate = 2, this means that the canonical result was already migrated to the master database ... the record has no further meaning, ready to be tossed, which is why my hunting tool [upon my instruction] entirely ignores them. The challenge for you is to find bogus dates on tasks that are not ready for deletion. biggrin
[Apr 4, 2017 6:35:53 PM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2166
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
Although dates/times to be ignored, they are there and wrong, Rob.

Regarding the first example that I gave with WU SCC1_0000239_Lin-ZNF-A_79778_0, you saw this:
           "ModTime": 1491323617,
           "WorkunitId": 2028561759,
           "ResultId": 1360765959,
           "Name": "SCC1_0000239_Lin-ZNF-A_79778_0",
           "Outcome": 1,
           "ReceivedTime": "2017-04-12T17:47:18",  
           "ReportDeadline": "2017-04-12T02:49:05",
           "SentTime": "2017-04-02T02:49:05",
           "ServerState": 5,
           "ValidateState": 1,
           "FileDeleteState": 2
Right?
Well, one hour later (through my crontab) the API returns the correct time for this same WU:
           "ModTime": 1491323617,
           "WorkunitId": 2028561759,
           "ResultId": 1360765959,
           "Name": "SCC1_0000239_Lin-ZNF-A_79778_0",
           "Outcome": 1,
           "ReceivedTime": "2017-04-04T16:33:23",  
           "ReportDeadline": "2017-04-12T02:49:05",
           "SentTime": "2017-04-02T02:49:05",
           "ServerState": 5,
           "ValidateState": 1,
           "FileDeleteState": 2
Although it's not a big deal, wrong is wrong.
[Apr 4, 2017 7:29:36 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
Again, what's the relevance... the fields could have been repurposed purely for internal housekeeping reasons, such as setting nonsense to prevent them from being counted again for one or the other statistic. Anyway, enjoy the riddle.
[Apr 4, 2017 7:48:34 PM]   Link   Report threatening or abusive post: please login first  Go to top 
armstrdj
Former World Community Grid Tech
Joined: Oct 21, 2004
Post Count: 695
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
We will look into this when we get a chance.

Thanks,
armstrdj
[Apr 7, 2017 3:03:36 PM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2166
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
Thanks in advance!
[Apr 7, 2017 4:50:27 PM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1673
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
Just for confirmation!
Could we consider that the combination "WorkunitId - ResultId" is absolutely unique on WCG?
Or is this combination only unique on project level (i.e. for each WCG project such a combination could maybe exist)?
Cheers,
Yves
----------------------------------------

Décrypthon team progress - KerSamson's contribution
[Apr 22, 2017 5:44:36 PM]   Link   Report threatening or abusive post: please login first  Go to top 
SekeRob
Master Cruncher
Joined: Jan 7, 2013
Post Count: 2741
Status: Offline
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
either is unique over-overall smile , so chose to only add resultid to the db. peace
----------------------------------------
[Edit 2 times, last edit by SekeRob* at Apr 22, 2017 6:52:12 PM]
[Apr 22, 2017 6:49:58 PM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1673
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
Thank you SekeRob for your clear and fast answer.
Just one more question: if ResultId is "absolutely" unique, what does WorkunitId mean? What is its purpose?
Yves
(still missing a comprehensive API and information description ...)
----------------------------------------

Décrypthon team progress - KerSamson's contribution
[Apr 22, 2017 10:17:21 PM]   Link   Report threatening or abusive post: please login first  Go to top 
SekeRob
Master Cruncher
Joined: Jan 7, 2013
Post Count: 2741
Status: Offline
Reply to this Post  Reply with Quote 
Re: API Returning Conflicting Data
A little hmmm, was I too quick ;?

a HST1 task has this as URL

https://www.worldcommunitygrid.org/ms/device/....do?workunitId=2067734334

the copies have

javascript:addHostPopup('/ms/device/viewResultErrorLog.do?resultId=1414097335','errPop',500,700);

javascript:addHostPopup('/ms/device/viewResultErrorLog.do?resultId=1414097336','errPop',500,700);

When I made my choice, I looked at the data link of the individual results. In case you happen to get both copies on different machines of the same user, there's a good chance that workunitid is not unique as 1414097335+6 are coupled to 2067734334, which I suspect to be the forever incrementing number at WCG (we're at 3.3 billion results, some have quorum 1, 2, 3, so 2 billion is about right in the educated guess department). The outside chance of you ever getting the same resultid, would series be reused is well 1 in a few billion, whereas a member with a 10 cruncher farm, stands a greater chance to grab both copies of the same unit, so wuid would become duplicated, at least occasionally we read about this, short for, the combo is unique. Anyway, the hunting tool with which I've captured millions against a large account, has never reported duplicate resultid... way outside chance for mortals to happen.
[Apr 22, 2017 10:44:09 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 32   Pages: 4   [ Previous Page | 1 2 3 4 | Next Page ]
[ Jump to Last Post ]
Post new Thread