On Thu, 25 Oct 2012, Curtis Walker wrote:
So - concordance IS completing all of its tasks and then redetecting
the remote properly. Given that congruity appears to be waiting /
hanging at the remote re-detection step it appears to be either
concordance either isn't passing onto or congruity isn't receiving the
remote re-detection after a successful flash (hence congruity isn't
passing info to the website, hence the update process appears to fail
(but doesn't actually).
I took a look at what concordance was doing and compared it with what
congruity was doing. The only difference I could see is that concordance
was calling deinit_concord() after resetting the remote. Can you please
try the attached patch which adds a call to deinit_concord in congruity?
Finally and leastly, could I suggest a quick correction of the grammar
of the error message to: "couldn't initialize libconcord: Error
connecting or finding the remote"
Yes, that has been annoying me for a while. :-)
Scott
diff --git a/congruity b/congruity
index 3c80206..f2b43a4 100755
--- a/congruity
+++ b/congruity
@@ -142,6 +142,9 @@ def worker_body_connect(
cb_context
)
try:
+ if resources.connected:
+ libconcord.deinit_concord()
+ resources.SetConnected(False)
libconcord.init_concord()
resources.SetConnected(True)
try:
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
