Closed stsievert closed 7 years ago
my first thought would be that PyMongo's not properly establishing a connection for some reason.
i'll attempt to reproduce tonight using master/HEAD
, and then try using database_cleanup
to get more informative error messages.
This is likely related to the DNS being in
constants.py
. We didn't (and shouldn't have to) set any environment variables to avoid this bug.
since all the docker containers are linked, and constants.py
just points at localhost:27017
, what are you referring to?
i'll attempt to reproduce
We launched this machine via the next_ec2.py
script then restarted and encountered this bug while running test_api.py
. This test ran fine for a number of responses, then failed after a seemingly random number of responses (sometimes on the 3rd response, sometimes on the 80th response). I'd like to see a test that follows this same procedure.
@liamim I've run a test (launched via next_ec2.py
, restarted) and which failed (query pages wouldn't load, etc). Can you dig into using NEXT after restarting EC2 machines with launch from next_ec2.py
?
Closed with documentation on the wiki (which added a note to use next_ec2.py start
)
@ayonsn017 and I ran into an issue with the database today.
NoneType does not support indexing
(or similar), meaning thatquery
wasNone
. This error was coming frombutler.queries.get
on App.py#L193butler.queries.get
with the argument provided gets rounded todb.get_doc
on Butler.py#L166This is likely related to the DNS being in constants.py. We didn't (and shouldn't have to) set any environment variables to avoid this bug.
@liamim can you look into this?