Sagar Gubbi

Thanks @kenjitoyama. Updating pexpect to 4.8.0 seems to have fixed it even in Python 3.6.

I'm having the same problem on Postgres 9.5.3. My `recovery.conf` is ``` restore_command = '/usr/bin/envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-fetch "%f" "%p"' ``` Postgres fails to start. Here's the log: ``` 2016-07-19...

Never mind. I'd put `recovery.conf` in `/etc/postgresql/9.5/main/` instead of `/var/lib/postgresql/9.5/main/`.

And have an option for the user to not receive @ notifications

Can you create a table for banned IPs (like in the wiki) and read banned IPs from that? This will also get you to setup postgres.

I haven't been able to reproduce this on my machine. Which OS did this problem occur on? Was this with sqlite3 or Postgres?

Is that with sqlite or postgres?

Throwing darts here. - Could be related to this: https://github.com/mattn/go-sqlite3/issues/274 Can you try removing the `github.com/mattn/go-sqlite3` package and installing the gcc version with `go install github.com/mattn/go-sqlite3`? - Does it happen...

Can you try adding `db.SetMaxOpenConns(1)` to `db.go` when using sqlite? ``` if driverName == "sqlite3" { db.SetMaxOpenConns(1) db.Exec("PRAGMA journal_mode = WAL;") db.Exec("PRAGMA synchronous = FULL;") db.Exec("PRAGMA foreign_keys = ON;") }...

Can you identify which handler is hanging? Does `TopicCreateHandler` return? Or is it `GroupIndexHandler` that's hanging? Also, does setting `journal_mode` for sqlite in `db.go` to `DELETE` or `OFF` help? (Without...