diff options
author | 2014-05-29 15:23:05 -0400 | |
---|---|---|
committer | 2014-05-29 15:23:05 -0400 | |
commit | 1f6cfecc972b121fa42ea80383183bbaccc2195a (patch) | |
tree | 0a450c4226f5e05c2a3597a9f520376de281fffe /doc/bugs/No_progress_bars_with_S3.mdwn | |
parent | a95fb731cd117f35a6e0fce90d9eb35d0941e26e (diff) |
remove old closed bugs and todo items to speed up wiki updates and reduce size
Remove closed bugs and todos that were least edited before 2014.
Command line used:
for f in $(grep -l '\[\[done\]\]' *.mdwn); do if [ -z $(git log --since=2014 --pretty=oneline "$f") ]; then git rm $f; git rm -rf $(echo "$f" | sed 's/.mdwn$//'); fi; done
Diffstat (limited to 'doc/bugs/No_progress_bars_with_S3.mdwn')
-rw-r--r-- | doc/bugs/No_progress_bars_with_S3.mdwn | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/doc/bugs/No_progress_bars_with_S3.mdwn b/doc/bugs/No_progress_bars_with_S3.mdwn deleted file mode 100644 index afa7ba5ee..000000000 --- a/doc/bugs/No_progress_bars_with_S3.mdwn +++ /dev/null @@ -1,26 +0,0 @@ -## What steps will reproduce the problem? - -Add new data to a repository with an S3 special remote. Monitor the repository with the web app. - - -## What is the expected output? What do you see instead? - -I expect a changing status bar and percentage. Instead I see no changes when an upload becomes active. - - -## What version of git-annex are you using? On what operating system? - -3.20130102 on Arch 64-bit. - - -## Please provide any additional information below. - - -When uploading local data to an S3 remote, I see no progress bars. The progress bar area on active uploads stays the same grey as the bar on queued uploads. The status does not change from "0% of...". The uploads are completing, but this makes it very difficult to judge their activity. - -The only remotes I currently have setup are S3 special remotes, so I cannot say whether progress bars are working for uploads to other remote types. - -> [[done]], this turned out to be a confusion in the progress code; -> parts were expecting a full number of bytes since the start, while -> other parts were sending the number of bytes in a chunk. Result was -> progress bars stuck at 0% often. --[[Joey]] |