MagmaCompressor reports not assigned id, but so far ok!

[Chris Muller]

> I got the following error:
> MaSoftwareError: MagmaSet has not id assigned

SoftwareErrors should never happen, you've found a bug (and I've
reproduced it here).  Compression of a repository checks all the
MagmaCollection back-end files (.hdx's) so it knows to copy them over
to the new compressed location if they are still referenced.  You got
this error occurs when you don't have any MagmaSets in your repository,
which is totally fine.  The Magma test-cases test with everything and
the kitchen sink, so they were too robust for their own good.  I will
fix this and post a new release of Magma soon, thanks for reporting
this!

> it be should read 1.4MB and not 140MB

You consider 1.4MB to be "crazy size"?

Its true that Magma appends all *new* objects to the end of the objects
file, but updated objects which have not grown in length (which can
only happen on Sets, Dictionary's or redefined classes with new
instance variables) get replaced in the objects file without growing
it.

But yes, compressing is essential, and a future version of Magma will
be able to do this on the fly (i.e., the server remaining up) with no
interruption of service.

Regards,
  Chris