pgBackRest 2.11 commit log

commit   : 68d20edea6cbfc7b8b6db69633e08ac473821547    
  
author   : David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 18:56:00 +0200    
  
committer: David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 18:56:00 +0200    

Bug Fixes:  
  
* Fix possible truncated WAL segments when an error occurs mid-write. (Reported by blogh.)  
* Fix info command missing WAL min/max when stanza specified. (Fixed by Stefan Fercot.)  
* Fix non-compliant JSON for options passed from C to Perl. (Reported by Leo Khomenko.)  
  
Improvements:  
  
* The archive-get command is implemented entirely in C.  
* Enable socket keep-alive on older Perl versions. (Contributed by Marc Cousin.)  
* Error when parameters are passed to a command that does not accept parameters. (Suggested by Jason O'Donnell.)  
* Add hints when unable to find a WAL segment in the archive. (Suggested by Hans-Jürgen Schönig.)  
* Improve error when hostname cannot be found in a certificate. (Suggested by James Badger.)  
* Add additional options to backup.manifest for debugging purposes. (Contributed by blogh.)  

commit   : 2ef5ad70a29b36db570f8f50a2ba821fc4ee02ff    
  
author   : David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 13:27:30 +0200    
  
committer: David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 13:27:30 +0200    

It makes sense for the crypto code to be in common since it is not pgBackRest-specific.  
  
Also combine the crypto tests into a single module.  

commit   : 95597be81e7450fdbb88a6c17b549e9eb750d5dd    
  
author   : David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 13:11:20 +0200    
  
committer: David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 13:11:20 +0200    

It makes sense for the compression code to be in common since it is not pgBackRest-specific.  

commit   : 2f63babe9dfa6f49d5fbc9a6e039e1a1dfa5054d    
  
author   : David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 11:55:01 +0200    
  
committer: David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 11:55:01 +0200    

commit   : e4e2606fce1ef28e82f359581e1a90be6d10414c    
  
author   : blogh <[email protected]>    
date     : Sun, 10 Mar 2019 11:03:52 +0200    
  
committer: David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 11:03:52 +0200    

Add the buffer-size, compress-level, compress-level-network, and process-max options to the backup:option section in backup.manifest to aid in debugging.  
  
It may also make sense to propagate these options up to backup.info so they can be displayed in the info command, but for now this is deemed sufficient.  
  
Contributed by blogh.  

commit   : 21f56f64ebe0af34b61793efad1730707a8e9f39    
  
author   : David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 10:38:12 +0200    
  
committer: David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 10:38:12 +0200    

When this error happens in the context of a backup it can be a bit mystifying as to why the backup is failing.  Add some hints to get the user started.  
  
These hints will appear any time a WAL segment can't be found, which makes the hint about the check command redundant when the user is actually running the check command, but it doesn't seem worth trying to exclude the hint in that case.  
  
Suggested by Hans-Jürgen Schönig.  

commit   : bc9fb0f59ae4d9cc843fa8ac2d9d434cf850910d    
  
author   : David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 09:16:25 +0200    
  
committer: David Steele <[email protected]>    
date     : Sun, 10 Mar 2019 09:16:25 +0200    

Suggested by ucando, jungle-boogie, Luca Ferrari.  

commit   : 786e77a9feb0ec3133d7f1ab7efe0037816a1382    
  
author   : Douglas J Hunley <[email protected]>    
date     : Sat, 9 Mar 2019 11:40:55 +0200    
  
committer: David Steele <[email protected]>    
date     : Sat, 9 Mar 2019 11:40:55 +0200    

DESTDIR always had /usr/bin appended which was a problem systems that don't use /usr/bin as the install location for binaries.  
  
Instead, use the value of DESTDIR exactly and update the Debian packages accordingly.  
  
Contributed by Douglas J Hunley.  

commit   : 60fe5b7365c9eaaa03e954cac7dec14777aa2461    
  
author   : David Steele <[email protected]>    
date     : Sat, 9 Mar 2019 11:03:47 +0200    
  
committer: David Steele <[email protected]>    
date     : Sat, 9 Mar 2019 11:03:47 +0200    

This behavior allowed a command like this to run without error:  
  
pgbackrest backup --stanza=db full  
  
Even though it actually performed an incremental backup in most circumstances because the `full` parameter was ignored.  
  
Instead, output an error and exit.  
  
Suggested by Jason O'Donnell.  

commit   : cad6fedb7ba2877f7ea1b2e23415c42b6bda3483    
  
author   : David Steele <[email protected]>    
date     : Thu, 7 Mar 2019 15:54:59 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 7 Mar 2019 15:54:59 +0200    

This warning was being output when getting help if retention was not set:  
  
WARN: option repo1-retention-full is not set, the repository may run out of space  
  
Suppress this when getting help since the warning will display by default on a system that is not completely configured.  

commit   : 3d7edc4ca4db2f75a33d43ffc5131a6a20086507    
  
author   : Luca Ferrari <[email protected]>    
date     : Thu, 7 Mar 2019 14:08:35 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 7 Mar 2019 14:08:35 +0200    

Contributed by Luca Ferrari.  

commit   : d441061168ec56d22082a6ff54e5f1fb02cc8eae    
  
author   : David Steele <[email protected]>    
date     : Sat, 2 Mar 2019 15:01:02 +0200    
  
committer: David Steele <[email protected]>    
date     : Sat, 2 Mar 2019 15:01:02 +0200    

The same test configurations are run on all four test VMs, which seems a real waste of resources.  
  
Vary the tests per VM to increase coverage while reducing the total number of tests. Be sure to include each major feature (remote, s3, encryption) in each VM at least once.  

commit   : f7d1d4400f1edcdd3216dfa5c9d1e306946c36a2    
  
author   : David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 19:04:26 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 19:04:26 +0200    

The same test configurations are run on all four test VMs, which seems a real waste of resources.  
  
Vary the tests per VM to increase coverage while reducing the total number of tests.  

commit   : 91622942c2e465cb46571343d0e40f8b7cef8742    
  
author   : David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 17:12:41 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 17:12:41 +0200    

The same test configurations are run on all four test VMs, which seems a real waste of resources.  
  
Vary the tests per VM to increase coverage while reducing the total number of tests. Be sure to include each major feature (remote, s3, encryption) in each VM at least once.  

commit   : c307d9fdf9439661d2a94f215bbc7b1ef714e34f    
  
author   : David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 15:58:52 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 15:58:52 +0200    

This is very inefficient in terms of memory and time and dynamic context names were never utilized.  
  
Just require that context names be valid for the life of the context.  
  
In practice they are all static strings.  

commit   : 90709dfd213b1eb1dab3daff0101768f61be4b5f    
  
author   : David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 14:57:01 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 14:57:01 +0200    

Allocations required a sequential scan through the allocation list for both contexts and memory.  This was very inefficient since for the most part individual memory allocations are seldom freed directly, rather they are freed when their context is freed.  
  
For both types of allocations track an index for the lowest free position.  After an allocation of the free position, a sequential search will be required for the next allocation but this is still far better than doing a scan for every allocation.  
  
With a moderately-sized dataset (500 history entries in backup.info), there is a 237X performance improvement when combined with the f74e88bb refactor.  
  
Before:  
  
  %   cumulative   self  
 time   seconds   seconds name  
 65.11    331.37   331.37 memContextAlloc  
 16.19    413.78    82.40 memContextCurrent  
 14.74    488.81    75.03 memContextTop  
  2.65    502.29    13.48 memContextNewIndex  
  1.18    508.31     6.02 memFind  
  
After:  
  
  %   cumulative   self  
 time   seconds   seconds name  
 94.69      2.14     2.14 memFind  
  
Finding memory allocations in order to free or resize them is the next bottleneck, but this does not seem to be a major issue presently.  

commit   : f74e88bba9c7a7912f0b1fc322823f1b527042f8    
  
author   : David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 13:33:58 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 13:33:58 +0200    

Using the functions internally is great for abstraction but not so great for performance on non-optimized builds.  
  
Also, the functions end up prominent in any profiled build.  

commit   : 6ce3310f8a2900d1af717da8d4c3345a9016933b    
  
author   : David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 09:10:14 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 09:10:14 +0200    

Also update CentOS 6 and 7 versions to PostgreSQL 9.5 and 9.6 respectively.  

commit   : 409360924151a561dd5dc122dbcd9173a4e6c950    
  
author   : David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 09:00:51 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 1 Mar 2019 09:00:51 +0200    

More than likely 9.2-11 will work as well, but this has not been tested.  
  
However, 11 needs work on the group permissions introduced in that version.  

commit   : cb3b4fa24bbe271a517b50a3522bc5075d8fe6c7    
  
author   : Marc Cousin <[email protected]>    
date     : Thu, 28 Feb 2019 14:33:29 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 28 Feb 2019 14:33:29 +0200    

The prior method depended on IO:Socket:SSL to push the keep-alive options down to the socket but it only worked for recent versions of the module.  
  
Instead, create the socket directly using IO::Socket::IP if available or IO:Socket:INET as a fallback.  The keep-alive option is set directly on the socket before it is passed to IO:Socket:SSL.  
  
Contributed by Marc Cousin.  

commit   : 0913523096cf9178ffa46595171dc16ab815148b    
  
author   : David Steele <[email protected]>    
date     : Thu, 28 Feb 2019 09:51:19 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 28 Feb 2019 09:51:19 +0200    

The command option was not being set correctly when a remote was started from a local.  It was being set as 'local' rather than the command that the local was running as.  
  
Also automatically select the remote protocol id based on whether it is started from a local (use the local protocol id) or from the main process (use 0).  
  
These were not live issues but could cause strange behaviors as new features are added that might be hard to diagnose.  

commit   : db4b447be89878496f0a50905b2f51c1306b9de5    
  
author   : David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 23:03:02 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 23:03:02 +0200    

This new implementation should behave exactly like the old Perl code with the exception of a few updated log messages.  
  
Remove as much of the Perl code as possible without breaking other commands.  

commit   : 9367cc461cda63698caa04ddb262405eef05890d    
  
author   : David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 22:34:21 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 22:34:21 +0200    

The C local is only used for C commands in the main process.  
  
Some tweaking of the existing protocolGet() command was required. Originally the idea was to share the function for local and remote requests but the differences (as in Perl) were too great to make that practical.  

commit   : 35abd4cd9517c4acf02d98bf386e1ef2ed2e8485    
  
author   : David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 21:10:52 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 21:10:52 +0200    

Allows commands to be easily parallelized if the jobs are broken up into discrete, non-overlapping chunks.  

commit   : 35acfae7c2328a70f978973aa1c7ed91af750d88    
  
author   : David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 19:48:30 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 19:48:30 +0200    

This formalizes the creation of protocol commands, which was previously done by creating KeyValue objects manually.  

commit   : dee90d3e606262fe99dcc099867a96039540a1c2    
  
author   : David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 18:11:09 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 18:11:09 +0200    

Some IO objects have file descriptors which can be useful for monitoring with select().  
  
It might also be useful to expose handles for write objects but there is currently no use case.  

commit   : b1957b07f351a93fa64658f8c898420b4bbe68f5    
  
author   : David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 18:10:18 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 18:10:18 +0200    

commit   : ea2aef1d0ceff366b75f663281df511b8169eadd    
  
author   : David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 18:09:21 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 18:09:21 +0200    

Because it is sometimes useful to remove items from a list.  

commit   : 4be271ea2a1a7bed4e5165f10a8e62a19b4e7dc9    
  
author   : David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 18:07:16 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 18:07:16 +0200    

There was a lot of extra boilerplate involved in setting up pipes so that is now automated.  
  
In some cases testing with multiple children is useful so allow that as well.  

commit   : 18b62a4220acabc4ba0018ed884e20f695304aed    
  
author   : David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 17:09:19 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 27 Feb 2019 17:09:19 +0200    

This amends 70c30dfb which disabled test tracing in general.  
  
Instead, only enable test tracing by default for modules that are being unit tested. This saves lots of time but still ensures that test tracing is working and helps with debugging in unit tests.  
  
Also rename the option to --debug-test-trace for a clarity.  

commit   : 3a05359087560248dc0bc7d1ce35516c6a5d622f    
  
author   : David Steele <[email protected]>    
date     : Sun, 24 Feb 2019 07:42:41 +0200    
  
committer: David Steele <[email protected]>    
date     : Sun, 24 Feb 2019 07:42:41 +0200    

The same test configurations are run on all four test VMs, which seems a real waste of resources.  
  
Vary the tests per VM to increase coverage while reducing the total number of tests. Be sure to include each major feature (remote, s3, encryption) in each VM at least once.  

commit   : 6d3e18b181d08f4e1ed64c097346a3532e6005af    
  
author   : David Steele <[email protected]>    
date     : Sun, 24 Feb 2019 06:55:59 +0200    
  
committer: David Steele <[email protected]>    
date     : Sun, 24 Feb 2019 06:55:59 +0200    

The expect tests were originally a rough-and-ready type of unit test so monitoring changes in the expect log helped us detect changes in behavior.  
  
Now the stanza code is heavily unit-tested so the detailed logs mainly cause churn and don't have any measurable benefit.  
  
Reduce the log level to DETAIL to make the logs less verbose and volatile, yet still check user-facing log messages.  

commit   : 2f081f3ec7a0c9bb664eb5a426ec21859bb48722    
  
author   : David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 18:51:52 +0200    
  
committer: David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 18:51:52 +0200    

The conventions for command and info tests have shifted in the C modules, though not even all the C modules got the message.  

commit   : d489eb87f7f7da58dd02812e5088f507e1cab491    
  
author   : David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 15:59:39 +0200    
  
committer: David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 15:59:39 +0200    

The same test configurations are run on all four test VMs, which seems a real waste of resources.  
  
Vary the tests per VM to increase coverage while reducing the total number of tests.  Be sure to include each major feature (remote, s3, encryption) in each VM at least once.  

commit   : 4a7588e604d3b39858f09e8c879e973bd4432ded    
  
author   : David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 15:13:23 +0200    
  
committer: David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 15:13:23 +0200    

This will allow for smarter allocation of tests in the next commit.  

commit   : 59d7958914d2965d0690ebd579541c21a40ad201    
  
author   : David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 15:05:06 +0200    
  
committer: David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 15:05:06 +0200    

The expect tests were originally a rough-and-ready type of unit test so monitoring changes in the expect log helped us detect changes in behavior.  
  
Now the archive code is heavily unit-tested so the detailed logs mainly cause churn and don't have any measurable benefit.  
  
Reduce the log level to DETAIL to make the logs less verbose and volatile, yet still check user-facing log messages.  

commit   : a9cbf23f4cacb18d85e7a6f02cff198790a9e21f    
  
author   : David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 07:28:27 +0200    
  
committer: David Steele <[email protected]>    
date     : Sat, 23 Feb 2019 07:28:27 +0200    

Update error message with the hostname and more detail about what went wrong.  Hopefully this will help in diagnosing certificate/hostname issues.  
  
Suggested by James Badger.  

commit   : 1f66bda02ec9ae92403af2feeaf61505b3482932    
  
author   : David Steele <[email protected]>    
date     : Fri, 22 Feb 2019 12:02:26 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 22 Feb 2019 12:02:26 +0200    

We have been using a hacked-up JSON generator to pass options from C to Perl since the C binary was introduced.  This generator was not very compliant which led to issues with \n, ", etc. inside strings.  
  
We have a fully-compliant JSON generator now so use that instead.  
  
Reported by Leo Khomenko.  

commit   : 70c30dfb619a3ec2ea7d465d5b8e2014518b723d    
  
author   : David Steele <[email protected]>    
date     : Fri, 22 Feb 2019 11:40:30 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 22 Feb 2019 11:40:30 +0200    

Detailed stack traces for low-level functions (e.g. strCat, bufMove) can be very useful for debugging but leaving them on for all tests has become quite burdensome in terms of time.  Complex operations like generating JSON on a large KevValue can lead to timeouts even with generous values.  
  
Add a new param, --debug-trace, to enable test-level stack trace, but leave it off by default.  

commit   : ae86e6d5b2f6f86bc3ec1a4b1378d9b49e89799e    
  
author   : David Steele <[email protected]>    
date     : Fri, 22 Feb 2019 11:31:37 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 22 Feb 2019 11:31:37 +0200    

Missing coverage is exposed in the next commit which disables test tracing by default.  

commit   : a7c8906581e8fc875c3cac99153aacb323de034f    
  
author   : David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 18:49:02 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 18:49:02 +0200    

commit   : e14c0eeb65a998a419e5a2e6c0ce833e8d7d03dc    
  
author   : David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 16:20:46 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 16:20:46 +0200    

The remote protocol was calling into the Storage object but this required some translation which will get more awkward as time goes by.  
  
Instead, call directly into the local driver so the communication is directly driver to driver.  This still requires resolving the path and may eventually have more duplication with the Storage object methods but it seems the right thing to do.  

commit   : b1eb8af7d5093a26a2e221a428540e5e7b356eed    
  
author   : David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 15:40:21 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 15:40:21 +0200    

Expressions such as <REPO:ARCHIVE> require a stanza name in order to be resolved correctly.  However, if the stanza name is passed to the remote then that remote will only work correctly for that one stanza.  
  
Instead, resolved the expressions locally but still pass a relative path to the remote.  That way, a storage path that is only configured on the remote does not need to be known locally.  

commit   : b4d4680f8c3126d1c2016d30aa2a1b77aac085c0    
  
author   : David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 14:40:35 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 14:40:35 +0200    

It is useful to be able to exclude an option even if it is shared by both commands.  

commit   : be6a3f131e746304c6a30c39fcab4fe4b44dcb7f    
  
author   : David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 14:26:06 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 14:26:06 +0200    

NULL was returning {"(null)"} which was comprehensible but not very pretty.  Instead return null on NULL.  

commit   : 1fd89f05afd8d8614d7b38a006eda4418f6324ce    
  
author   : David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 14:16:17 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 14:16:17 +0200    

Check if a key exists even if the value is NULL, which is the same result for a missing key.  

commit   : 80df1114bdc97a930421f491bb7f41d9aeab6069    
  
author   : Stefan Fercot <[email protected]>    
date     : Thu, 21 Feb 2019 12:09:12 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 12:09:12 +0200    

This issue was a result of STORAGE_REPO_PATH prepending an extra stanza when the stanza was specified on the command line.  
  
The tests missed this because by some strange coincidence the WAL dirs were empty for each test that specified a stanza.  Add new tests to prevent a regression.  
  
Fixed by Stefan Fercot.  

commit   : 1519f5b04540d5a431044f83a45b604ad8757397    
  
author   : David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 11:40:30 +0200    
  
committer: David Steele <[email protected]>    
date     : Thu, 21 Feb 2019 11:40:30 +0200    

Free all cached objects in the storage helper, especially the stanza name.  
  
This clears the storage environment for tests that switch stanza names or go from a stanza name to no stanza name or vice versa. This is only useful for testing right now, but may be used in the future for commands than act on multiple stanzas.  

commit   : b0b5989acae29b962b9101719459234968a8e6c1    
  
author   : David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 22:57:18 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 22:57:18 +0200    

All required protocol commands are implemented so this is mostly a matter of enabling the feature and updating expect logs.  

commit   : 6866ff031a6a48d6cd966f5df78bcbc2c84a3890    
  
author   : David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 22:43:02 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 22:43:02 +0200    

commit   : 71bc5697b1a35c8460af7885b888b1d43bd994b1    
  
author   : David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 22:23:19 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 22:23:19 +0200    

This was previously 256, which was too small to log protocol parameters.  Not only did this truncate important debug information but varying path lengths caused spurious differences in the expect logs.  

commit   : 73be64ce49aaff9d94f70c47590476c404365ce4    
  
author   : David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 15:52:07 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 15:52:07 +0200    

This command was previously forked off from the archive-get command which required a bit of artificial option and log manipulation.  
  
A separate command is easier to test and will work on platforms that don't have fork(), e.g. Windows.  

commit   : e48b406cdc3c73056137d6767a7f70e08bee9806    
  
author   : David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 15:48:14 +0200    
  
committer: David Steele <[email protected]>    
date     : Wed, 20 Feb 2019 15:48:14 +0200    

These are intended to be temporary until a fully automated report is developed.  
  
Since we don't know when that will happen, at least make it easier to generate the current report.  

commit   : da628be8a8045e73b621fb229ac149b545008327    
  
author   : David Steele <[email protected]>    
date     : Tue, 19 Feb 2019 20:57:38 +0200    
  
committer: David Steele <[email protected]>    
date     : Tue, 19 Feb 2019 20:57:38 +0200    

Prior to this the Perl remote was used to satisfy C requests. This worked fine but since the remote needed to be migrated to C anyway there was no reason to wait.  
  
Add the ProtocolServer object and tweak ProtocolClient to work with it. It was also necessary to add a mechanism to get option values from the remote so that encryption settings could be read and used in the storage object.  
  
Update the remote storage objects to comply with the protocol changes and add the storage protocol handler.  
  
Ideally this commit would have been broken up into smaller chunks but there are cross-dependencies in the protocol layer and it didn't seem worth the extra effort.  

commit   : d211c2b8b51ae5b796bbb581d21a4a406e3ed972    
  
author   : David Steele <[email protected]>    
date     : Fri, 15 Feb 2019 11:52:39 +0200    
  
committer: David Steele <[email protected]>    
date     : Fri, 15 Feb 2019 11:52:39 +0200    

The file write object destructors called close() and finalized the file even if it was not completely written.  This was an issue in both the C and Perl code.  
  
Rewrite the destructors to simply free resources (like file handles) rather than calling the close() method.  This leaves the temp file in place for filesystems that use temp files.  
  
Add unit tests to prevent regression.  
  
Reported by blogh.  

commit   : 2cd204f38037f1465c84bb4e6b55893204ee8f93    
  
author   : Stephen Frost <[email protected]>    
date     : Tue, 12 Feb 2019 14:59:51 +0200    
  
committer: David Steele <[email protected]>    
date     : Tue, 12 Feb 2019 14:59:51 +0200    

execRead() should be returning a size_t, not a void. Thankfully, this isn't actually used and therefore shouldn't be an issue, but we should fix it anyway.  
  
Contributed by Stephen Frost.  

commit   : a5f6f801d7651606363715471dcb958e3339414c    
  
author   : David Steele <[email protected]>    
date     : Tue, 12 Feb 2019 14:11:16 +0200    
  
committer: David Steele <[email protected]>    
date     : Tue, 12 Feb 2019 14:11:16 +0200