Closed mbanck closed 8 years ago
It's not expected but still happens yes, I have yet to see about proper signal handling. It's just the default lisp compiler behavior here...
Here's what happens nowadays on C-c
, the error is handled properly (enough):
# ./build/bin/pgloader ./test/census-places.load
2016-03-27T01:14:09.028000+01:00 LOG Main logs in '/private/tmp/pgloader/pgloader.log'
2016-03-27T01:14:09.033000+01:00 LOG Data errors in '/private/tmp/pgloader/'
2016-03-27T01:14:09.033000+01:00 LOG Parsing commands from file #P"/Users/dim/dev/pgloader/test/census-places.load"
2016-03-27T01:14:09.238000+01:00 LOG Fetching 'http://www2.census.gov/geo/docs/maps-data/data/gazetteer/places2k.zip'
C-c C-c^CAn unhandled error condition has been signalled:
Interactive interrupt at #x7FFF89DED07A.
An unhandled error condition has been signalled:
Interactive interrupt at #x7FFF89DED07A.
I'm using the supplied CentOS .tar file of the development version, but when I ^C during a pgloader run, I get "Interactive interrupt at #x7FFFF71C83E7." and a hang, no clean shutdown, is that expected?