Local VCS Failing - 'very long file content'

Just encountered this for a ~1900 line file - content not versioned. I
know it's big, but it doesn't seem inordinately large.

Is there a reason for this measly limit? Can it be increased? I've never
seen it before in all my years using IDEA (with sometimes even bigger
files) so could it point to a problem here?

Feels a lot less secure without LVCS guaranteed to be behind me...

N.

14 comments
Comment actions Permalink

Indeed, Local History does not version content of files larger than 1Mb. This restriction is due to storage space considerations.

Unfortunately you can not manually change this limit now. You may create jira request for that.

0
Comment actions Permalink

But the file in question is only 90.2KB... so it looks like there is a
problem here. Please let me know if there is anything I can do to help
you resolve this?

Cheers,
N.

Anton Makeev wrote:

Indeed, Local History does not version content of files larger than 1Mb. This restriction is due to storage space considerations.

Unfortunately you can not manually change this limit now. You may create jira request for that.

0
Comment actions Permalink

How did you get this message?
I mean that did you do? Open local history dialog? On what?

0
Comment actions Permalink

I opened local history of this file (Local History|Show History...) to
try to revert to a very recent version. The message was shown in red
where the source/diff usually is, above the local history table.

In the time since getting this problem I have restarted my machine (and
thus IDEA) and now I don't have any previous local history for the file
- the table is empty :(

But now local history seems to be working for the file again.

N.

Anton Makeev wrote:

How did you get this message?
I mean that did you do? Open local history dialog? On what?

0
Comment actions Permalink

The problem is, most likely, that local history was corrupted. The possible reason is previous forced shutdown. Did something like that take place?

0
Comment actions Permalink

That's possible I suppose, although I don't specifically remember doing
it... maybe it was a windows crash or something. I assume you have got
VM shutdown hooks in place to ensure non-corruption due to OS shutting
down normally, or just user stupidity (Ctrl+C in the console)?

N.

Anton Makeev wrote:

The problem is, most likely, that local history was corrupted. The possible reason is previous forced shutdown. Did something like that take place?

0
Comment actions Permalink

The problem is known, and we are trying to fix it at the moment.
I think the fix will be available after 7.0.2,

Thanks

0
Comment actions Permalink

Ah.. ok, well thats good news. Do you have a JIRA I can watch?

Thanks for the help,
Nathan.

Anton Makeev wrote:

The problem is known, and we are trying to fix it at the moment.
I think the fix will be available after 7.0.2,

Thanks

0
Comment actions Permalink

Yup, none of the files I've changed using #7584 have working Local History, all show the 'very long file content' error...

0
Comment actions Permalink

Event after IDEA restart?

0
Comment actions Permalink

On closing down and restarting IDEA, all my local history was lost, but now it seems to be working.

Would be nice if local history persisted across IDEA sessions... ;)

0
Comment actions Permalink

I had the same :(

N.

Dave Lorde wrote:

On closing down and restarting IDEA, all my local history was lost, but now it seems to be working.

Would be nice if local history persisted across IDEA sessions... ;)

0
Comment actions Permalink

There was a problem with local history - if idea had been closed incorrectly (hanged on or forced to shutdown), it could be corrupted.

We have fixed the problem and the fix will be available in first 7.0.3 eap.
If problem recur after upgrade, please let me know.

0
Comment actions Permalink

There was no incorrect or forced shutdown - If I remember correctly, IDEA 7584 had been running continuously since being installed over the previous EAP. The system logs show no reboot or program errors or warnings since it was installed.

Perhaps installing over the previous build had the same effect as a forced shutdown (although previous EAP installs were trouble-free)...

0

Please sign in to leave a comment.