Astares

Same for 

@Ducasse / @jecisc / @MarcusDenker Yes - build seems broken. Maybe I'm to blame: Because 4 days ago my PR for WelcomeBrowser was merged: https://github.com/pharo-spec/NewTools-WelcomeBrowser/commit/8046cf7fc6da91544554f4374fadf38ce192c824 which typically should be in...

My PR in the WelcomeBrowser repo included a change in **"BaselineOfWelcomeBrowser >> repositoryLocation"** (see https://github.com/pharo-spec/NewTools-WelcomeBrowser/commit/8046cf7fc6da91544554f4374fadf38ce192c824) which was not working - so I fixed it. Maybe this one has trouble when...

As even in Pharo 13 it is still possible to publish workspace/playground content to the @svenvc cloud  we should give it some love and repair it

Also it is now **StPlaygroundPresenter** We cloud implement a StPlaygroundPresenter(class)>>#openUrl like: ```Smalltalk StPlaygroundPresenter openContents: (ZnEasy get: 'http://ws.stfx.eu/6M3DIN9WNU2O') contents ```

A small step is done in https://github.com/pharo-spec/NewTools-WelcomeBrowser/pull/25 fixing https://github.com/pharo-spec/NewTools-WelcomeBrowser/issues/24

Yes - much better now. Thanks! Screens for reference:   We can close the issue.

According to docu: https://github.com/libgit2/libgit2/blob/main/docs/changelog.md ``` A new error code GIT_EEOF indicates an early EOF from the server. This typically indicates an error with the URL or configuration of the server,...

It worked before around a week since when Pharo 12 release came out. Now with a fresh image I get this issue since last week. I think this is a...

I updated (with Pharo launcher to latest Pharo 12 VM) - but that did not solve the problem  Image is Pharo12.0.0SNAPSHOT Build information: Pharo-12.0.0+SNAPSHOT.build.1513.sha.ee8b9dea9b3bbc42dbcc5efca62ee8de39633f9e (64 Bit) VM is 120-x64\Pharo.exe...