agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths

Scenario: Puppet Agent is bucketing file to Puppetserver

Following scenario (but in agent-server) configuration should show the error:
puppet apply -e 'file

'

puppet apply -e 'file

'

1. file1 already exists, so it is bucketed before rewritten by contents of 'bash'

puppet apply -e 'file

'

puppet apply -e 'file

'

1. file2 already exists, so it is bucketed before rewritten by contents of 'bash'. It is bucketed to same directory on server because md5 hash of file2 is same as md5 hash of bucketed file1. And bucketing fails.

In theory this should work. And for local bucketing it works.
There are 2 artefacts on server for each bucketed file - contents and paths. Paths contains all paths where contents was stored on origin system.

When file is bucketed there are multiple checks - size, md5 hash and file to be bucketed is byte-to-byte compared with already bucketed file.

In case that given file is bucketed (file with md5sum hash exists on server) and path on origin system is different to path stored in 'paths' than there are 2 checks - size of bucketed file and checksum. Size is compared between data of file received over network from agent and existing 'contents' on server.

The problem is, that this comparison usually fails because encoding of data received over network are 'UTF-8' encoded and contents is "like" plain bytes. So size doesn't match and it is considered error and processing of file resource fails.

For puppet-agent-1.10.4-1.el7.x86_64 rpm:
Comparison is in: method Puppet::FileBucketFile::File.verify_identical_file()
bucket_file is: Puppet::FileBucket::File::StringContents

Solution should be to ensure size of data received over network to be converted to something like "ASCII-8BIT" encoding even for 'size' operation.