Skip to content
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

"should get a new ref before getting an old one (line 369)" error on attempt to grade #13

Closed
GoogleCodeExporter opened this issue Apr 4, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.  Install Flubaroo from script gallery
2.  Create at least two forms questions
3.  Get the error shown above.

Original issue reported on code.google.com by astill...@gmail.com on 21 Apr 2012 at 1:41

@GoogleCodeExporter
Copy link
Author

Perhaps related, when I go to examine the script properties in the editor, the 
GUI hangs and a message "We're sorry, a server error occurred. Please wait..." 
appears in the header.

Original comment by astill...@gmail.com on 21 Apr 2012 at 1:45

@GoogleCodeExporter
Copy link
Author

Interesting, this error occurs on my domain account but not my Gmail.  Wonder 
if I've exceeded a service quota on my domain.

Original comment by astill...@gmail.com on 21 Apr 2012 at 1:49

@GoogleCodeExporter
Copy link
Author

Please let me know if you continue to see this. I will look into it soon.

Original comment by dabouav@gmail.com on 22 Apr 2012 at 8:35

@GoogleCodeExporter
Copy link
Author

Interestingly, around the same time I got this error on Flubaroo, I started 
getting it for the first time on my autoCrat script, and it occurred on my 
Gmail account as well as my domain account.

I was not able to replicate on several more runs of Flubaroo, but haven't 
tested extensively...

Here's my theory...something may have changed in the Script Properties service 
since the last Apps Script release that causes it to be much more finicky about 
parallel accesses to script and user properties.   Some kind of lock is getting 
applied when multiple functions simultaneously call to (read/write?) the same 
property, shutting off access to all properties.

Trying to access script properties after the lock gets put on results in the 
spinner.  I've gone back to some of the spreadsheets where this was happening 
after multiple hours and found that ScriptProperties were released for access 
again.  The script ran again once, and then locked up again.

I was able to fix autoCrat by moving a ScriptProperties-dependent function call 
into it's own, time-separated event (it was originally inside another function 
that had read-write access to ScriptProperties)...which I think was causing 
parallel calls to the service, possibly on the same property.

Someone else reported this same error in the forum in the past several days.
http://productforums.google.com/forum/#!topic/apps-script/rbDm2gbvIm0

I also reported it as an issue at the GAS tracker...issue 1279
http://code.google.com/p/google-apps-script-issues/issues/detail?id=1279&q=label
%3AType-Defect&colspec=Stars%20Opened%20ID%20Type%20Status%20Summary%20Priority%
20Component%20Owner



Original comment by astill...@gmail.com on 22 Apr 2012 at 11:46

@GoogleCodeExporter
Copy link
Author

Original comment by d...@edcode.org on 23 Apr 2012 at 5:20

  • Added labels: Flubaroo

@GoogleCodeExporter
Copy link
Author

Issue 14 has been merged into this issue.

Original comment by d...@edcode.org on 23 Apr 2012 at 5:21

@GoogleCodeExporter
Copy link
Author

I've not seen this same error since it was reported "fixed" in the Apps Script 
issue queue.

Original comment by astill...@gmail.com on 30 Apr 2012 at 8:44

@GoogleCodeExporter
Copy link
Author

Original comment by d...@edcode.org on 1 May 2012 at 4:30

  • Changed state: Verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant