| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Website Support
Thread: How to format the API query URL on Modtime? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 16
|
|
| Author |
|
|
ErikaT
Former World Community Grid Admin USA Joined: Apr 27, 2009 Post Count: 912 Status: Offline Project Badges: 
|
We have a deployed a change that should resolve this issue. If you could test with your apps and let us know that would be great! Did the update break some filters? I usually query with ValidateState=1 and now it just returns 500. Removing ValidateState=1 works fine. We have also identified other 'ValidateState' parameter filtering issues that are in the process being fixed Thank you for your patience & support! ErikaT |
||
|
|
ErikaT
Former World Community Grid Admin USA Joined: Apr 27, 2009 Post Count: 912 Status: Offline Project Badges:
|
Adding (small) validationstate= or proper ValidationState= seems ineffective with any of the VS codes, 0, 1, 2, 4 or kicks out an error, noting that if modtime (small) is used it does not work but if ModTime (Proper) is used, it works i.e. the call seems to be case sensitive (superficial testing). Sek,The parameters are case sensitive, and must be used exactly as you see here. Thanks, ErikaT |
||
|
|
ErikaT
Former World Community Grid Admin USA Joined: Apr 27, 2009 Post Count: 912 Status: Offline Project Badges:
|
BTW, may have asked about this before but an inverse filter would also be great e.g. ValidationState<>0 or Outcome<>7 (who's interested in pulling aborted tasks with zero runtime, which brings me to just pulling ServerState=5 and CPUTime>0, as an additional filter tag, or CPUTime=1 meaning has runtime ;?) I have added this as something to discuss with the team, to possibly be implemented in the future.From the creative commons department, and only if you have the hour spare to be creative. ;P) Thanks, ErikaT |
||
|
|
wujj123456
Cruncher Joined: Jun 9, 2010 Post Count: 40 Status: Offline Project Badges: 
|
We have a deployed a change that should resolve this issue. If you could test with your apps and let us know that would be great! Did the update break some filters? I usually query with ValidateState=1 and now it just returns 500. Removing ValidateState=1 works fine. We have also identified other 'ValidateState' parameter filtering issues that are in the process being fixed Thank you for your patience & support! ErikaT Thanks! Good to know it's being fixed. For now I just removed the ValidateState=1 and filter on my own. Will revert back once the ValidateState query works again. I think I haven't really thanked you guys, but I am very grateful that WCG web team provided an API at first place. This is really a huge feature for me compared against other BOINC projects. I love tracking my history in more details and for longer than project owners do. Only through WCG API I was able to do this. It's also good tools for monitoring multiple hosts without using the clunky BOINC remote feature. Thank you for all the support. That's some really great work. Merry Christmas! |
||
|
|
ErikaT
Former World Community Grid Admin USA Joined: Apr 27, 2009 Post Count: 912 Status: Offline Project Badges:
|
I think I haven't really thanked you guys, but I am very grateful that WCG web team provided an API at first place. This is really a huge feature for me compared against other BOINC projects. I love tracking my history in more details and for longer than project owners do. Only through WCG API I was able to do this. It's also good tools for monitoring multiple hosts without using the clunky BOINC remote feature. Thank you for all the support. That's some really great work. Merry Christmas! Thank you for the kind words  ErikaT |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
We have a deployed a change that should resolve this issue. If you could test with your apps and let us know that would be great! Did the update break some filters? I usually query with ValidateState=1 and now it just returns 500. Removing ValidateState=1 works fine. We've deployed the fix for the issue with the ValidateState parameter. |
||
|
|
|