Re: [Pharo-dev] Problem with zinc 2.9.2

On 22 Jul 2018, at 12:10, Norbert Hartl wrote: Thank you guys! It is really great to see that there are people like Max jumping onto problems like this and solving it. You're welcome! @sven I’m eager to test when the new configuration is available. Please drop us a note when you are done!

Re: [Pharo-dev] Problem with zinc 2.9.2

Good! > On 22 Jul 2018, at 13:53, Norbert Hartl wrote: > > Sven, > > thank you very much for quickly providing a new version. I changed the > dependencies of my project for 2.9.4 and everything is fine now. So I can > start using pharo7 on my laptop and keep 6.1 images for building the >

Re: [Pharo-dev] Problem with zinc 2.9.2

Sven, thank you very much for quickly providing a new version. I changed the dependencies of my project for 2.9.4 and everything is fine now. So I can start using pharo7 on my laptop and keep 6.1 images for building the deployment artefact. Great! thanks, Norberr > Am 22.07.2018 um 12:59

Re: [Pharo-dev] Problem with zinc 2.9.2

Done: === Name: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.117 Author: SvenVanCaekenberghe Time: 22 July 2018, 12:58:12.362 pm UUID: 949d5a24-f62d-0d00-a12c-ead9078b1897 Ancestors: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.116 stable v 2.9.4 === Please tell us if this

Re: [Pharo-dev] Problem with zinc 2.9.2

Thank you guys! It is really great to see that there are people like Max jumping onto problems like this and solving it. @sven I’m eager to test when the new configuration is available. Please drop us a note when you are done! thanks again, Norbert > Am 22.07.2018 um 11:06 schrieb Sven Van

Re: [Pharo-dev] Problem with zinc 2.9.2

Ah, that makes total sense. Great catch. Thank you. === Name: Zinc-FileSystem-SvenVanCaekenberghe.17 Author: SvenVanCaekenberghe Time: 22 July 2018, 11:04:40.148339 am UUID: e97a508e-f42d-0d00-a127-f016078b1897 Ancestors: Zinc-FileSystem-SvenVanCaekenberghe.16 Bugfix to ZnFileSystemUtils

Re: [Pharo-dev] Problem with zinc 2.9.2

Sven, you're right. What I found last time works as a side-effect. The real problem is in ZnFileSystemUtils class>>newBinaryFileNamed:do:. In Pharo 6.1 the logic there leads to the following evaluation: `block value: (self binaryFileStreamFor: fileName)` This is the only place where the

Re: [Pharo-dev] Problem with zinc 2.9.2

Just to be safe, I'll redo my experiment and get back to you. On 21 Jul 2018, at 16:59, Sven Van Caekenberghe wrote: I tried running Max's snippet (Pharo 6.1 on Ubuntu 16.04 LTS), ZnClient new url: 'https://github.com/zweidenker/Parasol/archive/master.zip'; downloadTo:

Re: [Pharo-dev] Problem with zinc 2.9.2

I tried running Max's snippet (Pharo 6.1 on Ubuntu 16.04 LTS), ZnClient new url: 'https://github.com/zweidenker/Parasol/archive/master.zip'; downloadTo: '/tmp/foobar.zip'. bytes := '/tmp/foobar.zip' asFileReference binaryReadStreamDo: [ :s | s contents ]. Transcript open; show: bytes

Re: [Pharo-dev] Problem with zinc 2.9.2

On 21 Jul 2018, at 12:07, Norbert Hartl wrote: Max, what do you think will be a proper fix for this? I cannot see if this is a vm problem or not. In my opinion it should be fixed in Zinc as there's no way for the user of Zinc to flush the stream. The alternative would be for Zinc to expose

Re: [Pharo-dev] Problem with zinc 2.9.2

Max, what do you think will be a proper fix for this? I cannot see if this is a vm problem or not. Norbert > Am 14.07.2018 um 08:25 schrieb Max Leske : > > Hi Nicolas, > > The PR you are referring [1] to concerns a missing fflush() when truncating a > file. I believe that is a different

Re: [Pharo-dev] Problem with zinc 2.9.2

Hi Nicolas, The PR you are referring [1] to concerns a missing fflush() when truncating a file. I believe that is a different case to this one, as a) the file is not truncated and b) in the case of truncation it is an explicit requirement that the file be empty before the first write

Re: [Pharo-dev] Problem with zinc 2.9.2

On 13 Jul 2018, at 13:37, Norbert Hartl wrote: Sven, for me the problem is only on linux Yes, exactly. The problem doesn't exist on macOS. I tested on Ubuntu 17.04 (32-bit). Norbert Am 13.07.2018 um 13:26 schrieb Sven Van Caekenberghe : On 12 Jul 2018, at 23:15, Max Leske wrote:

Re: [Pharo-dev] Problem with zinc 2.9.2

Sven, for me the problem is only on linux Norbert > Am 13.07.2018 um 13:26 schrieb Sven Van Caekenberghe : > > > >> On 12 Jul 2018, at 23:15, Max Leske wrote: >> >> Hi Norbert, >> >> I was able to reproduce the problem and then identify the culprit, although >> what I don't yet

Re: [Pharo-dev] Problem with zinc 2.9.2

> On 12 Jul 2018, at 23:15, Max Leske wrote: > > Hi Norbert, > > I was able to reproduce the problem and then identify the culprit, although > what I don't yet understand is how this is related to the changes in Zinc. > > Anyway, the problem is that the file stream isn't properly flushed

Re: [Pharo-dev] Problem with zinc 2.9.2

Gosh , I’m always impressed how you guys figure this stuff out. Many thanks to all of you for coming up with a test case and solution(s). It’s a great community. Tim Sent from my iPhone > On 13 Jul 2018, at 00:19, Nicolas Cellier > wrote: > > Isn't there a recent PR on opensmalltalk that

Re: [Pharo-dev] Problem with zinc 2.9.2

Isn't there a recent PR on opensmalltalk that address just this? Le jeu. 12 juil. 2018 à 23:16, Max Leske a écrit : > Hi Norbert, > > I was able to reproduce the problem and then identify the culprit, > although what I don't yet understand is how this is related to the changes > in Zinc. > >

Re: [Pharo-dev] Problem with zinc 2.9.2

Hi Norbert, I was able to reproduce the problem and then identify the culprit, although what I don't yet understand is how this is related to the changes in Zinc. Anyway, the problem is that the file stream isn't properly flushed in ZnUtils class>>streamFrom:to:size:. Adding `outputStream

Re: [Pharo-dev] Problem with zinc 2.9.2

> Am 12.07.2018 um 08:05 schrieb Max Leske : > >> On 11 Jul 2018, at 22:44, Norbert Hartl wrote: >> >> Hi Max, >> >> I constructed a case that fails exactly like I experience it. Could you try? >> Just unpack the attachment on a linux, set PHARO_VM env to your executable >> and execute

Re: [Pharo-dev] Problem with zinc 2.9.2

On 11 Jul 2018, at 22:44, Norbert Hartl wrote: Hi Max, I constructed a case that fails exactly like I experience it. Could you try? Just unpack the attachment on a linux, set PHARO_VM env to your executable and execute build.sh I will. Might take a couple of days though. Max Norbert

Re: [Pharo-dev] Problem with zinc 2.9.2

Hi Max,I constructed a case that fails exactly like I experience it. Could you try? Just unpack the attachment on a linux, set PHARO_VM env to your executable and execute build.shNorbert<> Am 10.07.2018 um 09:17 schrieb Max Leske :On 10 Jul 2018, at 8:48, Norbert Hartl

Re: [Pharo-dev] Problem with zinc 2.9.2

> Am 11.07.2018 um 20:19 schrieb Sven Van Caekenberghe : > > > >> On 11 Jul 2018, at 19:50, Norbert Hartl wrote: >> >> Thank you Sven. That fixed my first problem. Sadly the other problem is more >> persitent than this. > > I would guess that the other problem (the ZipArchive usage)

Re: [Pharo-dev] Problem with zinc 2.9.2

> On 11 Jul 2018, at 19:50, Norbert Hartl wrote: > > Thank you Sven. That fixed my first problem. Sadly the other problem is more > persitent than this. I would guess that the other problem (the ZipArchive usage) might be related to the recent file/stream changes in Pharo 7 and not

Re: [Pharo-dev] Problem with zinc 2.9.2

Thank you Sven. That fixed my first problem. Sadly the other problem is more persitent than this. Norbert > Am 11.07.2018 um 16:46 schrieb Sven Van Caekenberghe : > > FWIW, I created a new #stable version 2.9.3 that includes a newer > Zinc-FileSystem-SvenVanCaekenberghe.16 - maybe this

Re: [Pharo-dev] Problem with zinc 2.9.2

FWIW, I created a new #stable version 2.9.3 that includes a newer Zinc-FileSystem-SvenVanCaekenberghe.16 - maybe this helps. === Name: Zinc-FileSystem-SvenVanCaekenberghe.16 Author: SvenVanCaekenberghe Time: 11 July 2018, 4:30:36.923152 pm UUID: 830fbcd3-1b2d-0d00-bd45-164704867404 Ancestors:

Re: [Pharo-dev] Problem with zinc 2.9.2

On 10 Jul 2018, at 8:48, Norbert Hartl wrote: Max, thanks for taking the effort. No worries. Am 10.07.2018 um 08:37 schrieb Max Leske : I did my best to reproduce the issue but didn't have any luck. I really need access to a Linux VM to debug this. So I'm praying that Apple fixes the

Re: [Pharo-dev] Problem with zinc 2.9.2

Max, thanks for taking the effort. > Am 10.07.2018 um 08:37 schrieb Max Leske : > > I did my best to reproduce the issue but didn't have any luck. I really need > access to a Linux VM to debug this. So I'm praying that Apple fixes the > access restrictions to kernel extensions in their next

Re: [Pharo-dev] Problem with zinc 2.9.2

I did my best to reproduce the issue but didn't have any luck. I really need access to a Linux VM to debug this. So I'm praying that Apple fixes the access restrictions to kernel extensions in their next beta... BTW, Metacello uses ZnClient, which uses ZnFileSystemUtils, so there is indeed a

Re: [Pharo-dev] Problem with zinc 2.9.2

> Am 09.07.2018 um 19:10 schrieb Max Leske : > > I checked the Parasol Archive and it does not appear to be in Zip64 format > (Metacello uses ZipArchive which can't cope with Zip64 but ZipArchive can > read the Parasol zip). So my next guess is that there's either a problem with > Metacello

Re: [Pharo-dev] Problem with zinc 2.9.2

I checked the Parasol Archive and it does not appear to be in Zip64 format (Metacello uses ZipArchive which can't cope with Zip64 but ZipArchive can read the Parasol zip). So my next guess is that there's either a problem with Metacello or Pharo in the way that ZipArchive is used (e.g.

Re: [Pharo-dev] Problem with zinc 2.9.2

Hi Max, > Am 09.07.2018 um 18:18 schrieb Max Leske : > > Hi Norbert, > > This is a bit of a guess, but it's possible that the archive that is > downloaded from github is in Zip64 format and that the libraries for > extracting Zip64 are missing on your Linux. That would of course contradict

Re: [Pharo-dev] Problem with zinc 2.9.2

Hi Norbert, This is a bit of a guess, but it's possible that the archive that is downloaded from github is in Zip64 format and that the libraries for extracting Zip64 are missing on your Linux. That would of course contradict the experience that the same operation appears to work in 6.1.

Re: [Pharo-dev] Problem with zinc 2.9.2

With the help of Esteban I got one step further. If I do MCWorkingCopy managersForClass: ZnFileSystemUtils do: [ :each | each ancestry initialize ] before loading my project it updates Zinc-FileSystem as well. Sadly it still does not work for me because I get Loading baseline

Re: [Pharo-dev] Problem with zinc 2.9.2

Really? I thought the same but then I didn’t believe it works like that. Anyway this would be very easy to solve. We just need to ask Sven if he is fine with doing an empty .16 version for Zinc-FileSystem and does an in-place version reset of 2.9.2 or a new 2.9.3. I’m not fully convinced that

Re: [Pharo-dev] Problem with zinc 2.9.2

> Need to investigate more. There are two .15 versions but there is 1 year > in between (if you didn’t notice TheIntegratior.15 is from 2017). Just want > to have more context information because I can only see that this is > strange but lacking insight. > > I’m trying to figure out why it does

Re: [Pharo-dev] Problem with zinc 2.9.2

> Am 07.07.2018 um 12:53 schrieb Sven Van Caekenberghe : > > Obviously something went wrong somewhere, but I cannot see what exactly. It > is a while ago, and integration processes have been in flux. > > Zinc is being developed in its own repo(s), but sometimes changes are made in > the

Re: [Pharo-dev] Problem with zinc 2.9.2

Obviously something went wrong somewhere, but I cannot see what exactly. It is a while ago, and integration processes have been in flux. Zinc is being developed in its own repo(s), but sometimes changes are made in the main Pharo repo that get copied back upstream. From time to time, Zinc

Re: [Pharo-dev] Problem with zinc 2.9.2

Can anyone explain how zinc is managed? The package Zinc-FileSystem in pharo 6.1 is Name: Zinc-FileSystem-TheIntegrator.15 Author: TheIntegrator Time: 15 March 2017, 1:16:56.199425 pm UUID: b9684fa8-2507-0d00-a4da-a21207d152a4 Ancestors: Zinc-FileSystem-HenrikNergaard.14 19838

Re: [Pharo-dev] Problem with zinc 2.9.2

Sven,I use Metacello and that seems to be different in behaviour. I prepared the case for you. What I did- save the attachment of this mail into a clean directory and open a terminal there$> unzip baseline-of-zincproblem.zip$> curl get.pharo.org/64/61 | bash$> 

Re: [Pharo-dev] Problem with zinc 2.9.2

Norbert, I did (on macOS): $ mkdir pharo61 $ cd pharo61/ $ curl get.pharo.org/61+vm | bash % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 3036 100 30360 0 24386 0

Re: [Pharo-dev] Problem with zinc 2.9.2

Bump. I wonder nobody sees the problem. Or do I misunderstand there is something wrong in pharo? Norbert > Am 05.07.2018 um 09:09 schrieb Norbert Hartl : > > Ok, > > I think I’ve found something. If you look at the screenshot (that is my image > from jenkins, 6.1 with my code loaded and that

Re: [Pharo-dev] Problem with zinc 2.9.2

On 4 Jul 2018, at 23:00, Norbert Hartl wrote: Am 04.07.2018 um 17:52 schrieb Max Leske : Hi Norbert, Where can I get my hands on that image that you say has no sender of #newBinaryFileNamed:do: in it? I cannot give away the image, sorry. I can try to reproduce it somehow. Do you expect

Re: [Pharo-dev] Problem with zinc 2.9.2

> Am 04.07.2018 um 19:34 schrieb Sven Van Caekenberghe : > > How exactly did you load ? > > On macOS > Pharo-7.0+alpha.build.1099.sha.bcfa81fa7b35214eede30962d35d1d547c199989 (64 > Bit) I went to the Catalog and loaded the default stable version. > > Fetched ->

Re: [Pharo-dev] Problem with zinc 2.9.2

> Am 04.07.2018 um 17:52 schrieb Max Leske : > > Hi Norbert, > > Where can I get my hands on that image that you say has no sender of > #newBinaryFileNamed:do: in it? > I cannot give away the image, sorry. I can try to reproduce it somehow. Do you expect the method to be there? Norbert >

Re: [Pharo-dev] Problem with zinc 2.9.2

How exactly did you load ? On macOS Pharo-7.0+alpha.build.1099.sha.bcfa81fa7b35214eede30962d35d1d547c199989 (64 Bit) I went to the Catalog and loaded the default stable version. Fetched -> ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.115 ---

Re: [Pharo-dev] Problem with zinc 2.9.2

Hi Norbert, Where can I get my hands on that image that you say has no sender of #newBinaryFileNamed:do: in it? Max On 4 Jul 2018, at 17:30, Norbert Hartl wrote: I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of