ID 241876 - Read metadata input/filesize overflow

Problem summary
input/fileize metadata value is using an int type, which limits it to 2147483648 (equivalent to 2GB in bytes). If a file is larger, this value overflows and sets input/filesize to a negative number.

Customer reported version
nuke.10.0v4

Customer reported platform
n_a_linux

Steps to reproduce

1)
Open attached script write_large.nk
It writes a stereo exr 40960x31120 reformatted to 10x scale
and it has a separate Read followed by a ViewMetaData

set the Write node file knob path

2)
render a frame

3)
set the Read node file knob path and reload the frame

4)
open the ViewmMetaData node and look at the filesize value


Workaround
Unknown.

Reproduced by support
Nuke10.0v4
OS 10.10.5

Expected behaviour
filesize is a positive correct integer reflecting the fliesize

Actual behaviour
filesize is negative