![]() Due to the involvement of J# I cannot obtain the actual exception. So to summarize, sometimes I get a file length of '0' returned for a file that I know exists. The output stream points at a file which has newly been created with no sharing. The files that get passed into the 'pack' method have very recently been created, as in milliseconds ago, wall-clock time. The file sizes involved are typically under 100kb. ![]() There is no apparent pattern to when these errors occur. In the case where 'ERROR 2' occurs, there are always 0 bytes written. The exceptions labelled in the comments below as 'Error 1' and 'Error 2' have both been seen in the wild. Now the code below works perfectly in developement, but intermittently experiences errors in production. NET reflector over the J# code to generate the equivalent J# libraries. I've provided a rough version at the end of this question that gives a good indication of what the underlying J# does. I have a 'pack files' method, written in J# that takes a bunch of files and writes them all into a stream, along with some enough metadata that they can be reconstructed as individual files by a related 'unpack' method.
0 Comments
Leave a Reply. |