On 9/16/15 8:05 PM, dewey wrote:
Hey Mike,
I've found and fixed (with help) my problem, but I thought I'd
describe it here to support anyone else who hits this...
Was not a threading issue..it was a combination of:
* data-edge case
* bug in our code
* bug in how SA was reporting a
check out this case, this is one way to reproduce that:
https://bitbucket.org/zzzeek/sqlalchemy/issues/3532/detect-property-being-assigned-to-more
On 9/15/15 3:56 PM, dewey wrote:
I'll see if I can reproduce this in a simple example.it's
currently in a job being run every night from a
Hey Mike,
I've found and fixed (with help) my problem, but I thought I'd describe it
here to support anyone else who hits this...
Was not a threading issue..it was a combination of:
- data-edge case
- bug in our code
- bug in how SA was reporting a failure...
I was adding a
On 9/15/15 2:05 PM, dewey wrote:
The contents of the full traceback was:
Traceback (most recent call last):
File
"/opt/paysys/python/lib/python2.7/site-packages/celery/app/trace.py",
line 240, in trace_task
R = retval = fun(*args, **kwargs)
File
I've got a SA session, and i'm running the following:
cot = sess.query(MyTable).get( int(someIntAsString) )
I'm seeing the error:
AttributeError: 'NoneType' object has no attribute 'accepts_scalar_loader'
I'm guessing that means the record was not found..any suggestions what
else I should
On 9/15/15 1:02 PM, dewey wrote:
I've got a SA session, and i'm running the following:
cot = sess.query(MyTable).get( int(someIntAsString) )
I'm seeing the error:
AttributeError: 'NoneType' object has no attribute 'accepts_scalar_loader'
I'm guessing that means the record was not
The contents of the full traceback was:
Traceback (most recent call last):
File "/opt/paysys/python/lib/python2.7/site-packages/celery/app/trace.py",
line 240, in trace_task
R = retval = fun(*args, **kwargs)
File "/opt/paysys/python/lib/python2.7/site-packages/celery/app/trace.py",
I'll see if I can reproduce this in a simple example.it's currently in
a job being run every night from a Celery-Beat scheduler..
Interestingly, just changing the data in the DB made this problem go away
temporarily...we were seeing this error thrown every night on staging
for 5
