docker-pharo-runtime, docker image for Pharo reached it's v11.0.0-2024-04-18 version.
What's Changed
Update VM to v10.1.0 by @gcotelli in https://github.com/ba-st/docker-pharo-runtime/pull/17
Full Changelog: https://github.com/ba-st/docker-pharo-runtime/compare/v11.0.0-2023-10-25…v11.0.0-2024-04-
docker-pharo-vm, docker image for Pharo VM reached it's v10.1.0-2024-04-18 version.
What's Changed
Update actions versions by @gcotelli in https://github.com/ba-st/docker-pharo-vm/pull/13
Update Pharo VM to v10.1.0 by @gcotelli in https://github.com/ba-st/docker-pharo-vm/pull/14
Upgrade Debian bas
Just as a comment on this - I tried using #sync as an experiment and I get a
primFailed on an Ubuntu docker image - so I think that comment in the image is
misleading (or its a bug, or unfinished work)
On Thu, 18 Apr 2024, at 11:15 AM, Tim Mackinnon wrote:
> Hi Stef - I was aware of that class
Hi Stef - I was aware of that class - but a good reminder to re-read it for any
extra info, but I don't see anything in particular mentioned about how data is
flushed - and I think this is one of those black arts from in the field.
It looks like stdio uses an Stdiostream - and I did note an inte
