Home » Modeling » Papyrus » Notation file blank after failed search
Notation file blank after failed search [message #1178078] |
Sat, 09 November 2013 11:16 |
Tomas Sandkvist Messages: 149 Registered: October 2013 |
Senior Member |
|
|
I managed to make a search over the entire workbench, which failed so badly that now is my Notation file apparently blank.
What to do, other than load a backup?
[EDIT:] I got the crazed idea of just putting back the notation file from the backup when I realized that the notation file seems to contain all diagrams. Stupid or not, at least I now only have to recreate the diagram I've create this morning.
But am I doing something that would potentially fail later on?
Regards,
Tomas Sandkvist
[Updated on: Sat, 09 November 2013 11:31] Report message to a moderator
|
|
|
Re: Notation file blank after failed search [message #1178462 is a reply to message #1178078] |
Sat, 09 November 2013 17:25 |
|
Hi, Tomas,
Search shouldn't modify any files, unless you did a search-and-replace.
Does simply closing and re-opening the model not help? Or do you mean
that the contents of the *.notation file were actually wiped out?
Do you see exceptions in the log?
This is probably a bug. I'd suggest creating a bugzilla with a model
attached in which the problem is reproducible, with steps to reproduce
it and any exceptions that were logged during the search.
Cheers,
Christian
On 2013-11-09 11:16:09 +0000, Tomas Sandkvist said:
> I managed to make a search over the entire workbench, which failed so
> badly that now is my Notation file apparently blank.
>
> What to do, other than load a backup?
>
> Regards,
> Tomas Sandkvist
|
|
|
Re: Notation file blank after failed search [message #1179428 is a reply to message #1178462] |
Sun, 10 November 2013 09:05 |
Tomas Sandkvist Messages: 149 Registered: October 2013 |
Senior Member |
|
|
I don't really know what to look for here. Where are the log files stored? My workspace consists of a lot of tests, failures, broken models and so on, and also confidential stuff (the proper models) that I cannot show because of confidentiality agreements.
But at least the logs could perhaps be of use. This was one of these "O MY GOD WHAT IS HAPPENING I DON*T KNOW WHAT TO DO AND I HAVE LOST ALL OF TODAY'S WORK AND IT IS EVEN SATURDAY" moments that made me do stuff hastily.
I opened the notation file with notepad++, it was in fact empty.
I can add something in Bugzilla just as a reminder, but I will probably not have enough facts to back it up. My best guess is that is has to do with saving, I noticed the asterisk on the model tab. I probably had some diagram open in the editor, and I did get a lot of messages that to me looked like Java was out of memory, but I'm no programmer. There where messages about internal failures and one dialog at the end recommended to close the workspace. If any of these gives any pointers on where to look, I can write it into Bugzilla.
What do you recommend in such a case?
Regards,
Tomas
|
|
|
Re: Notation file blank after failed search [message #1180016 is a reply to message #1179428] |
Sun, 10 November 2013 18:23 |
|
Hi, Tomas,
Wow. I'm sorry, this doesn't look like a good situation.
The workspace log file is the one I referred to: in the .metadata/
sub-folder of your workspace folder you'll find a file named simply
".log". (there will likely be a bunch of numbered roll-over log files,
too) This should have stack traces that can help diagnose problems.
There may also be names of confidential model elements or other
sensitive information in there; take care before posting any of it!
One of the features that I continually bless Eclipse for is the
Workspace History. By default, every save of a file in the workspace
keeps a delta from the previous. By default, seven days of such
history are maintained. This doesn't require any version control
system; it is always present and it just works.
You should be able to find some recent version of the notation file
that could restore at least most of its content. Perhaps other files
are similarly affected? In the Project Explorer, right-click on a file
and select the "Replace With -> Local History..." menu action to browse
recent versions and see what you can restore.
Obviously I wouldn't recommend trying to reproduce this kind of
disaster on your own data just to raise a bugzilla. If you are
motivated to look through the log and see whether any exceptions in
there seem related to the search operation and your data loss, then you
might post some excerpts from the log.
However, I do know (having worked on extending the search function into
CDO repositories in the Luna release) that the Kepler release appears
to have some significant memory leaks. Your mention of internal error
dialogs recommending to close the workspace supports this:
out-of-memory errors typically trigger that dialog. I suppose you
performed several searches, right? I suspect that your VM ran out of
memory while trying to save a file (EMF buffers the entire text in
memory before writing it out) and so the result was truncation to zero
bytes. But, this is just speculation on my part. Your log could
provide more insight.
HTH,
Christian
On 2013-11-10 09:05:33 +0000, Tomas Sandkvist said:
> I don't really know what to look for here. Where are the log files
> stored? My workspace consists of a lot of tests, failures, broken
> models and so on, and also confidential stuff (the proper models) that
> I cannot show because of confidentiality agreements.
>
> But at least the logs could perhaps be of use. This was one of these "O
> MY GOD WHAT IS HAPPENING I DON*T KNOW WHAT TO DO AND I HAVE LOST ALL OF
> TODAY'S WORK AND IT IS EVEN SATURDAY" moments that made me do stuff
> hastily.
>
> I opened the notation file with notepad++, it was in fact empty.
> I can add something in Bugzilla just as a reminder, but I will probably
> not have enough facts to back it up. My best guess is that is has to do
> with saving, I noticed the asterisk on the model tab. I probably had
> some diagram open in the editor, and I did get a lot of messages that
> to me looked like Java was out of memory, but I'm no programmer. There
> where messages about internal failures and one dialog at the end
> recommended to close the workspace. If any of these gives any pointers
> on where to look, I can write it into Bugzilla.
>
> What do you recommend in such a case?
>
> Regards,
> Tomas
|
|
| | | | | | |
Goto Forum:
Current Time: Wed Sep 25 16:21:39 GMT 2024
Powered by FUDForum. Page generated in 0.02950 seconds
|