VW7.7 - Bug in Store leads to a loss of a class definition

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

VW7.7 - Bug in Store leads to a loss of a class definition

Ladislav Lenart
Hi all,

I would like to report kind of a serious bug in the Store
code handling. Minimal test case to reproduce it in the
vanilla:
   1. Create package Foo.
   2. Create class Foo in it.
   3. Pubish it.
   4. Rename class Foo to Bar.
   5. Zero or more publishes in between.
   6. Create new class Foo.
   7. Publish it.

The last version no longer contains one of the definions,
i.e. it either lacks the definition of new Foo or the
definition of Bar (former Foo). The choice of the banned
name seems completely arbitrary to me (the same sequence
of the steps has varying behavior).

Republish does not help, the one name is banned forever
in this package.

My questions:
   1. Is it generally known?
   2. Is there a patch for it?
   2. Is there at least a workaround to mitigate it (e.g.
      a Glorp script that will fix the corrupted DB)?


Thank you,

Ladislav Lenart

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: VW7.7 - Bug in Store leads to a loss of a class definition

Alan Knight-2
I'm pretty sure this is known and fixed in later versions, but I'm not finding the AR number easily, and the people who would know are out for the American holiday.



[hidden email]
24 November, 2011 9:08 AM


Hi all,

I would like to report kind of a serious bug in the Store
code handling. Minimal test case to reproduce it in the
vanilla:
1. Create package Foo.
2. Create class Foo in it.
3. Pubish it.
4. Rename class Foo to Bar.
5. Zero or more publishes in between.
6. Create new class Foo.
7. Publish it.

The last version no longer contains one of the definions,
i.e. it either lacks the definition of new Foo or the
definition of Bar (former Foo). The choice of the banned
name seems completely arbitrary to me (the same sequence
of the steps has varying behavior).

Republish does not help, the one name is banned forever
in this package.

My questions:
1. Is it generally known?
2. Is there a patch for it?
2. Is there at least a workaround to mitigate it (e.g.
a Glorp script that will fix the corrupted DB)?


Thank you,

Ladislav Lenart

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc