heroku/WAL-E — Issue #13: when using a wrong directory, stack trace explosion
Author: fdr
Created: 2011-10-27 14:29:51+00:00
State: open

This should be a readable error message instead

```
Traceback (most recent call last):
File "/usr/bin/wal-e", line 9, in
load_entry_point('WAL-E==0.5.8c4', 'console_scripts', 'wal-e')()
File "/usr/lib/pymodules/python2.6/wal_e/cmd.py", line 301, in main
pool_size=args.pool_size)
File "/usr/lib/pymodules/python2.6/wal_e/operator/s3_operator.py", line 317, in database_s3_backup
start_backup_info, version=version, *args, **kwargs)
File "/usr/lib/pymodules/python2.6/wal_e/operator/s3_operator.py", line 205, in _s3_upload_pg_cluster_dir
for tpart in partitions:
File "/usr/lib/pymodules/python2.6/wal_e/tar_partition.py", line 205, in tar_partitions_plan
raise TarBadPathError(root=root, offensive_path=file_path)
wal_e.tar_partition.TarBadPathError
```