summaryrefslogtreecommitdiff
path: root/Assistant/Alert.hs
Commit message (Collapse)AuthorAge
* hlintGravatar Joey Hess2012-09-13
|
* fixed all pairing alert issuesGravatar Joey Hess2012-09-11
|
* fix combining of pairing alertsGravatar Joey Hess2012-09-11
|
* pairing works!!Gravatar Joey Hess2012-09-11
| | | | | | | | | Finally. Last bug fixes here: Send PairResp with same UUID in the PairReq. Fix off-by-one in code that filters out our own pairing messages. Also reworked the pairing alerts, which are still slightly buggy.
* responding to pair requests *almost* worksGravatar Joey Hess2012-09-10
|
* add an alert while a locally initiated pairing request is in progressGravatar Joey Hess2012-09-09
| | | | Has a button to cancel the request.
* pair request alert tweaksGravatar Joey Hess2012-09-09
|
* unify bootstrap icon names in a data typeGravatar Joey Hess2012-09-09
|
* update pair request alert when button is pressedGravatar Joey Hess2012-09-09
|
* first pass at alert buttonsGravatar Joey Hess2012-09-08
| | | | | | | | | They work fine. But I had to go to a lot of trouble to get Yesod to render routes in a pure function. It may instead make more sense to have each alert have an assocated IO action, and a single route that runs the IO action of a given alert id. I just wish I'd realized that before the past several hours of struggling with something Yesod really doesn't want to allow.
* added pair listener threadGravatar Joey Hess2012-09-08
|
* display alert for inotify/kqueue errorsGravatar Joey Hess2012-09-06
|
* improve display of failed transfer alertGravatar Joey Hess2012-08-27
|
* scan multiple remotes in one passGravatar Joey Hess2012-08-26
| | | | | | | | | | | | | | | | | | | | | | | | | The expensive transfer scan now scans a whole set of remotes in one pass. So at startup, or when network comes up, it will run only once. Note that this can result in transfers from/to higher cost remotes being queued before other transfers of other content from/to lower cost remotes. Before, low cost remotes were scanned first and all their transfers came first. When multiple transfers are queued for a key, the lower cost ones are still queued first. However, this could result in transfers from slow remotes running for a long time while transfers of other data from faster remotes waits. I expect to make the transfer queue smarter about ordering and/or make it allow multiple transfers at a time, which should eliminate this annoyance. (Also, it was already possible to get into that situation, for example if the network was up, lots of transfers from slow remotes might be queued, and then a disk is mounted and its faster transfers have to wait.) Also note that this means I don't need to improve the code in Assistant.Sync that currently checks if any of the reconnected remotes have diverged, and if so, queues scans of all of them. That had been very innefficient, but now doesn't matter.
* remove slightly misleading extended messageGravatar Joey Hess2012-08-23
|
* fix display of icon in block alert headingGravatar Joey Hess2012-08-06
|
* added an alert after a file transferGravatar Joey Hess2012-08-06
|
* better alert message generationGravatar Joey Hess2012-08-06
|
* make alerts change tense when they finishGravatar Joey Hess2012-08-06
|
* add alert when committingGravatar Joey Hess2012-08-02
|
* refactorGravatar Joey Hess2012-08-02
|
* add some strictness annotationsGravatar Joey Hess2012-08-02
| | | | on general principles
* trim long filenames (have to fit on the sidebar)Gravatar Joey Hess2012-08-02
| | | | | | | | 30 characters would mostly work, but 20 is safer due to some wider letters like 'w'. Of course this is very heuristic based on filesize anyway. (Bootstrap does a surprisingly bad job at dealing with overlong words in the sidebar.)
* awesome alert combiningGravatar Joey Hess2012-08-02
| | | | | | | | | Now an alert tracks files that have recently been added. As a large file is added, it will have its own alert, that then combines with the tracker when dones. Also used for combining sanity checker alerts, as it could possibly want to display a lot.
* add iconsGravatar Joey Hess2012-07-31
|
* remove the "running" alertGravatar Joey Hess2012-07-30
|
* remove old filler that is effectively the same as new fillerGravatar Joey Hess2012-07-30
|
* implement server-side alert closingGravatar Joey Hess2012-07-30
| | | | | Rather than using bootstrap's client-side closing. Now closed alerts stay closed.
* make filler closeableGravatar Joey Hess2012-07-30
|
* prune old filler alertsGravatar Joey Hess2012-07-30
|
* make old activiy alerts stay visibleGravatar Joey Hess2012-07-30
| | | | | | They're updated to show whether the activity succeeded or failed. This adds several TODOs to the code to fix later.
* avoid first personGravatar Joey Hess2012-07-29
|
* tweak Alert closability and constructionGravatar Joey Hess2012-07-29
|
* better ordering of alertsGravatar Joey Hess2012-07-29
|
* moved all alert messages into one fileGravatar Joey Hess2012-07-29
| | | | Makes it easier to edit for consistent voice etc.
* show alerts in the sidebarGravatar Joey Hess2012-07-29
| | | | | This has a bug -- it seems long polling can only wait on one page at a time. Need to re-unify the notifiers.
* add alerts to DaemonStatusGravatar Joey Hess2012-07-29