Monticello broken (was: [5.1] DataStream bug)

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

Monticello broken (was: [5.1] DataStream bug)

Bert Freudenberg
This happens for me on every MC operation, when it is trying to store a local copy in the package cache. The files get written but are 0 bytes (probably due to aborting the dialog). Later this results in a broken ZIP error (EOCD not found).

- Bert -

On Wed, Aug 24, 2016 at 12:43 PM, Bert Freudenberg <[hidden email]> wrote:
This appears to happen a lot in 5.1, e.g. the first time you compare a package in Monticello:

UndefinedObject(Object)>>doesNotUnderstand: #instSize
nil(Object)>>storeDataOn:
DataStream>>writeInstance:
DataStream>>nextPut:

Anybody else seeing it?

- Bert -



Reply | Threaded
Open this post in threaded view
|

Re: Monticello broken (was: [5.1] DataStream bug)

Levente Uzonyi
A few years ago there was a VM bug causing this. Which VM do you use?

Levente

On Wed, 24 Aug 2016, Bert Freudenberg wrote:

> This happens for me on every MC operation, when it is trying to store a local copy in the package cache. The files get written but are 0 bytes (probably due to aborting the dialog). Later this results in a
> broken ZIP error (EOCD not found).
> - Bert -
>
> On Wed, Aug 24, 2016 at 12:43 PM, Bert Freudenberg <[hidden email]> wrote:
>       This appears to happen a lot in 5.1, e.g. the first time you compare a package in Monticello:
> UndefinedObject(Object)>>doesNotUnderstand: #instSize
> nil(Object)>>storeDataOn:
> DataStream>>writeInstance:
> DataStream>>nextPut:
>
> Anybody else seeing it?
>
> - Bert -
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Monticello broken (was: [5.1] DataStream bug)

Bert Freudenberg
5 class
==> nil

That's the problem. WTF? Happens on multiple VMs I tried.

- Bert -

On Wed, Aug 24, 2016 at 1:06 PM, Levente Uzonyi <[hidden email]> wrote:
A few years ago there was a VM bug causing this. Which VM do you use?

Levente


On Wed, 24 Aug 2016, Bert Freudenberg wrote:

This happens for me on every MC operation, when it is trying to store a local copy in the package cache. The files get written but are 0 bytes (probably due to aborting the dialog). Later this results in a
broken ZIP error (EOCD not found).
- Bert -

On Wed, Aug 24, 2016 at 12:43 PM, Bert Freudenberg <[hidden email]> wrote:
      This appears to happen a lot in 5.1, e.g. the first time you compare a package in Monticello:
UndefinedObject(Object)>>doesNotUnderstand: #instSize
nil(Object)>>storeDataOn:
DataStream>>writeInstance:
DataStream>>nextPut:

Anybody else seeing it?

- Bert -








Reply | Threaded
Open this post in threaded view
|

Re: Monticello broken (was: [5.1] DataStream bug)

Levente Uzonyi
Doesn't happen here on cogspur64linuxht 5.0-201607150008.

Levente

On Wed, 24 Aug 2016, Bert Freudenberg wrote:

> 5 class
> ==> nil
>
> That's the problem. WTF? Happens on multiple VMs I tried.
>
> - Bert -
>
> On Wed, Aug 24, 2016 at 1:06 PM, Levente Uzonyi <[hidden email]> wrote:
>       A few years ago there was a VM bug causing this. Which VM do you use?
>
>       Levente
>
>       On Wed, 24 Aug 2016, Bert Freudenberg wrote:
>
>             This happens for me on every MC operation, when it is trying to store a local copy in the package cache. The files get written but are 0 bytes (probably due to aborting the dialog).
>             Later this results in a
>             broken ZIP error (EOCD not found).
>             - Bert -
>
>             On Wed, Aug 24, 2016 at 12:43 PM, Bert Freudenberg <[hidden email]> wrote:
>                   This appears to happen a lot in 5.1, e.g. the first time you compare a package in Monticello:
>             UndefinedObject(Object)>>doesNotUnderstand: #instSize
>             nil(Object)>>storeDataOn:
>             DataStream>>writeInstance:
>             DataStream>>nextPut:
>
>             Anybody else seeing it?
>
>             - Bert -
>
>
>
>
>
>
>
>