summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-09-09 04:23:40 +0000
committerGravatar admin <admin@branchable.com>2013-09-09 04:23:40 +0000
commit40033b5e02c2a9ef9b0eeed3b3c461a16f4231ec (patch)
treed25308d2bf395664d8ed3322efaf0606205df598
parent25dfa6e29630b4338846cf16ab6eadfd4eadf7fb (diff)
Added a comment
-rw-r--r--doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment
new file mode 100644
index 000000000..ece6ce0e3
--- /dev/null
+++ b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="4.153.255.110"
+ subject="comment 1"
+ date="2013-09-09T04:23:36Z"
+ content="""
+This occurs when the javascript long polling code fails 4 times in a row attempting to communicate with git-annex's web server. Normally this will mean that the assistant has been stopped. I have seen it once or twice happen while the web server is still running -- possibly due to the browser killing the connection? I have never seen it happen when navigating between pages in the webapp, which is designed to allow use of back button etc. If you can reproduce it reliably, using the chromium inspector to modify the javascript code (look for \"longpoll\") and perhaps add some debug prints might track down what is going on.
+"""]]