talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

QA to be down for 30-40 minutes starting at 4:40 pm PST (7:40 pm EST)

AR
Aron Roberts
Fri, Dec 21, 2012 12:37 AM

Patrick has identified and fixed a significant Services layer bug, below.

At 4:40 pm PST (7:40 pm EST), I'm planning to rebuild and redeploy
the services layer on QA, then restart Tomcat to reflect this change.

This may disrupt testing for a minimum of 20 minutes (plan on 30-40
minutes to be conservative).

With apologies for those of us testing right now ... we need to get
this bugfix in ASAP, so any remaining testing can be done with it in.

Thanks,
Aron

--

On Thu, Dec 20, 2012 at 3:32 PM, Patrick Schmitz pschmitz@berkeley.edu wrote:

Turns out this was a much more fundamental bug that we caught with this
test. It also messed up the creation of indexes in the DBs, etc. In the few
places where we connect directly to the DB, we were always connecting to the
lifesci DB, and not the core one. Ack!  Fortunately this turned up the
problem, and we have a very focused fix that we have tested, and that I just
checked in.

Can someone kick a services build on QA?

Patrick has identified and fixed a significant Services layer bug, below. At 4:40 pm PST (7:40 pm EST), I'm planning to rebuild and redeploy the services layer on QA, then restart Tomcat to reflect this change. This may disrupt testing for a minimum of 20 minutes (plan on 30-40 minutes to be conservative). With apologies for those of us testing right now ... we need to get this bugfix in ASAP, so any remaining testing can be done with it in. Thanks, Aron -- On Thu, Dec 20, 2012 at 3:32 PM, Patrick Schmitz <pschmitz@berkeley.edu> wrote: > Turns out this was a much more fundamental bug that we caught with this > test. It also messed up the creation of indexes in the DBs, etc. In the few > places where we connect directly to the DB, we were always connecting to the > lifesci DB, and not the core one. Ack! Fortunately this turned up the > problem, and we have a very focused fix that we have tested, and that I just > checked in. > > Can someone kick a services build on QA? -- Patrick's fix: https://github.com/collectionspace/services/commit/2ff26066715d6cb0cc1149586c745bff52d9f212