Failed to complete read of log file

APL-related discussions - a stream of APL consciousness.
Not sure where to start a discussion ? Here's the place to be
Forum rules
This forum is for discussing APL-related issues. If you think that the subject is off-topic, then the Chat forum is probably a better place for your thoughts !
Post Reply
User avatar
ray
Posts: 238
Joined: Wed Feb 24, 2010 12:24 am
Location: Blackwater, Camberley. UK

Failed to complete read of log file

Post by ray »

Hi,

While playing with a compression algorithm, I have managed to corrupt my Session LOG file.

So each time I start up "Dyalog APL/W-64 Version 19.0.48959" I get the error:
Failed to complete read of log file "C:\Users\ray_c\Documents\Dyalog APL-64 19.0 Unicode Files\default_000.dlfx".
I have tried using the Log menu to "Clear" and then "Save". I then ")OFF".
But when I start up APL again I get the same error.

I think I have got round this by using the Log menu options "Clear" and then "Save as",
supplying the name "C:\Users\ray_c\Documents\Dyalog APL-64 19.0 Unicode Files\default_000.dlfx" and then saying "Yes" to the pop-up message box requiring conformation to overwriting the (corrupt) file.

My query is :
Could any data of ⎕DR type 320, when displayed in the session, be the cause of the corruption of the log file?

(My compression algorithms was converting a "sparse" Boolean matrix with many all-zero rows. A Boolean vector used to compress out the all-zero row was converted into a 32 bit character, and the non-all-zero rows were then converted into 32 bit characters.

I had no difficulty in viewing these 320 bit characters in the session with "]Box on -s=max".

However, it is at that point that the "Read" of the log file failed at the next Dyalog start-up.

I have since rewritten the compression to use data types of 80 for the compression vector and 160 for the non-zero rows, resulting in a 70% reduction in size, but fear displaying the these characters in the session my again corrupt the log.)
Ray Cannon
Please excuse any smelling pisstakes.
User avatar
AndyS|Dyalog
Posts: 263
Joined: Tue May 12, 2009 6:06 pm

Re: Failed to complete read of log file

Post by AndyS|Dyalog »

Hi Ray

I think we'll need either a "corrupted" log file or the code you use to generate the characters before we can say very much - drop support@ an email with a logfile or the code.

Deleting the log file has no other effect other than you lose all your history, so using Windows Explorer to delete it is often the quickest solution. Having said that, if the log file is still in use, then you'd need to terminate the APL process so that there is no lock on the logfile preventing the deletion.
Vince|Dyalog
Posts: 439
Joined: Wed Oct 01, 2008 9:39 am

Re: Failed to complete read of log file

Post by Vince|Dyalog »

Hi Everyone,

I have received Ray's log file, but I am able to start Dyalog with it.

In general, if you get a "Failed to complete read of log file" message, please do the following:

1) Copy your log files to a safe place in a different directory.
2) In Options→Configure→Session, please increase your Session Log Size to a larger value. By default, it's 800K. I would suggest trying 2M.
3) )off and start Dyalog again.
4) If you still have a problem, please write to us at Dyalog Support.

Regards,

Vince
Vince|Dyalog
Posts: 439
Joined: Wed Oct 01, 2008 9:39 am

Re: Failed to complete read of log file

Post by Vince|Dyalog »

Hi Everyone,

I have received Ray's workspace and have his barbits variable.

With it, I can reproduce his session log problem and have logged an issue for this, 21439.

Ray does this:
320⎕DR {⍵≢¨0,¯1↓⍵} ↓ 320 ⎕DR 128 128↑barbits

Regards,

Vince
User avatar
ray
Posts: 238
Joined: Wed Feb 24, 2010 12:24 am
Location: Blackwater, Camberley. UK

Re: Failed to complete read of log file

Post by ray »

Many thanks Vince
Ray Cannon
Please excuse any smelling pisstakes.
Post Reply