[Pharo-users] Re: [ANN] New Pharo VM released (v8.6.1)

[Christophe Demarey]

Hi Tom,

Pharo Launcher downloads VMs as a zip archive (HTTP GET) and then extract it to 
the desired path.
Probably Kaspersky puts a flag on files downloaded from the web until you 
explicitly give your approbation that it is not a malicious software.
Maybe you can configure Kaspersky to whitelist Pharo Launcher downloads?
Check https://support.kaspersky.com/KAV/2020/en-us/68499.htm , sections On all 
websites except those specified /  <>Manage exclusions <>

Regards,
Christophe.

> Le 3 nov. 2020 à 22:45, Tom Wern  a écrit :
> 
> Kapersky did not like updating Pharo Launcher  ... specifically 
> vms\90-x64\PharoConsole.exe which it quarantined and promptly deleted  
> (Object name: VHO:Exploit.Win32.Agent.gen)
> 
> Any idea what's going on?
> 
> Tom Wern
> 
> 
> 
> On Mon, Nov 2, 2020 at 10:49 AM teso...@gmail.com  
> mailto:teso...@gmail.com>> wrote:
> Hi,
>  this is an announcement of a new release of the Pharo VM. This
> new version is available to be downloaded through get-pharo scripts
> and through the Pharo Launcher. From the Pharo Launcher, remember to
> update the VM from the VM manager window.
> 
> This version includes a series of improvements:
> 
> - Unification of code base with the headless VM
> - Preparation for supporting HDPI displays.
> - Improvements in the speed of Threaded FFI (40x times faster in
> SameThread runner and 2x in Threaded worker).
> - Better handling of semaphores
> - Improvements in the loading of large images (better buffering)
> - Better support for headless execution on non-main thread
> 
> Please let me know if you find any issues.
> 
> Cheers, Pablo
> 
> -- 
> Pablo Tesone.
> teso...@gmail.com 

[Pharo-users] Re: [ANN] New Pharo VM released (v8.6.1)

[Tom Wern]

Kapersky did not like updating Pharo Launcher  ...
specifically vms\90-x64\PharoConsole.exe which it quarantined and promptly
deleted  (Object name: VHO:Exploit.Win32.Agent.gen)

Any idea what's going on?

Tom Wern



On Mon, Nov 2, 2020 at 10:49 AM teso...@gmail.com  wrote:

> Hi,
>  this is an announcement of a new release of the Pharo VM. This
> new version is available to be downloaded through get-pharo scripts
> and through the Pharo Launcher. From the Pharo Launcher, remember to
> update the VM from the VM manager window.
>
> This version includes a series of improvements:
>
> - Unification of code base with the headless VM
> - Preparation for supporting HDPI displays.
> - Improvements in the speed of Threaded FFI (40x times faster in
> SameThread runner and 2x in Threaded worker).
> - Better handling of semaphores
> - Improvements in the loading of large images (better buffering)
> - Better support for headless execution on non-main thread
>
> Please let me know if you find any issues.
>
> Cheers, Pablo
>
> --
> Pablo Tesone.
> teso...@gmail.com
>

[Pharo-users] Re: [Pharo-dev] [ANN] New Pharo VM released (v8.6.1)

[Tudor Girba]

Great work!

Thanks,
Tudor

> On Nov 2, 2020, at 4:48 PM, teso...@gmail.com wrote:
> 
> Hi,
> this is an announcement of a new release of the Pharo VM. This
> new version is available to be downloaded through get-pharo scripts
> and through the Pharo Launcher. From the Pharo Launcher, remember to
> update the VM from the VM manager window.
> 
> This version includes a series of improvements:
> 
> - Unification of code base with the headless VM
> - Preparation for supporting HDPI displays.
> - Improvements in the speed of Threaded FFI (40x times faster in
> SameThread runner and 2x in Threaded worker).
> - Better handling of semaphores
> - Improvements in the loading of large images (better buffering)
> - Better support for headless execution on non-main thread
> 
> Please let me know if you find any issues.
> 
> Cheers, Pablo
> 
> -- 
> Pablo Tesone.
> teso...@gmail.com

--
feenk.com

“Software has no shape. Actually, it has no one shape. It has many."

[Pharo-users] Re: [Pharo-dev] [ANN] New Pharo VM released (v8.6.1)

[Santiago Bragagnolo]

These are great newsss!!! thanks a lot for your hardwork.
None of the other things we like to do would be possible without this.




El lun., 2 nov. 2020 a las 16:48, teso...@gmail.com ()
escribió:

> Hi,
>  this is an announcement of a new release of the Pharo VM. This
> new version is available to be downloaded through get-pharo scripts
> and through the Pharo Launcher. From the Pharo Launcher, remember to
> update the VM from the VM manager window.
>
> This version includes a series of improvements:
>
> - Unification of code base with the headless VM
> - Preparation for supporting HDPI displays.
> - Improvements in the speed of Threaded FFI (40x times faster in
> SameThread runner and 2x in Threaded worker).
> - Better handling of semaphores
> - Improvements in the loading of large images (better buffering)
> - Better support for headless execution on non-main thread
>
> Please let me know if you find any issues.
>
> Cheers, Pablo
>
> --
> Pablo Tesone.
> teso...@gmail.com
>

[Pharo-users] [ANN] Stargate v6.0.0 [v6.0.0] released!

[Buenos Aires Smalltalk]

Stargate, a library supporting the creation of HTTP based RESTful APIs.  reached it's v6.0.0 version.
Breaking changes

Revamped CORS support (see the updated docs)

Migration Guide
Migration of APIs using CORS will be performed automatically via rewrite rule. To achieve this, manually load the package Stargate-Deprecated-V6 before loading your code.
Non breaking changes

HTTPMetrics can now be configured to only breakdown on certain categories  (see the updated docs)
Use again the official smalltalkCI
Update the version of the CodeCov action in use
Export coverage in LCOV format

Regards,
The Buenos Aires Smalltalk team

[Pharo-users] [ANN] Superluminal v1.1.0 [v1.1.0] released!

[Buenos Aires Smalltalk]

Superluminal, building blocks for creating HTTP requests and API clients reached it's v1.1.0 version.
Changelog

Core
Refactor some internals of the request builder
HttpRequest now include methods to easily support DELETE, PATCH and PUT
HttpRequest instances can now be applied several times to the same HTTP Client
The header builder now supports setBearerTokenTo: , setIfMatchTo: and setIfNoneMatchTo:
API Client
RESTfulAPIClient provides a building block to create more specific RESTful API clients by providing http clients pooling, automatic handling of ETag related headers, and by now in-memory caching
ExpiringCache provides an in-memory cache for incoming request responses adhering to the received caching directives
Service Discovery
ConsulAgentHttpAPIBasedDiscoveryClient provides service discovery abilities using the Consul Health HTTP API as backend
FixedServiceDiscoveryClient provides basic service discovery abilities using a fixed list of services
All the service discovery clients can be used in a chained fashion
Add integration tests for the service discovery client using docker-compose
Tooling
Use GitHub actions and CodeCov to run the build
Automatically send release announcements to the mailing list

Next steps

Add usage documentation
Provide some kind of caching policy so we can use different strategies according to the situation

Regards,
The Buenos Aires Smalltalk team

[Pharo-users] [ANN] Hyperspace v2.2.0 [v2.2.0] released!

[Buenos Aires Smalltalk]

Hyperspace, a couple of facilities on top of Zinc HTTP Components reached it's v2.2.0 version.
Non breaking changes

Add HTTPClientError>>-
Add HTTPServerError exception
Add extensions to ZnClient
setLogLevelAtLeastTo:
logLevel
setIfNoneMatchTo:
resetRequest
Add extensions to ZnSingleThreadedServer
setLogLevelAtLeastTo:
logLevel
Add Retry, one of the resilience operations that repeat failed executions a number of times.
 Configuration Options
#upTo: retryCount : The maximum number of retries. Defaults to 2.
#every: duration : Wait a time duration between retry attempts. By default don't wait.
#when: condition : Evaluate the condition with the current execution result, if met retry the execution.
#on: exceptionSelector : Retry the execution if an exception handled by exceptionSelector is raised.
#ignore: exceptionSelector : Scope the previous method ignoring the exceptions that can be handled by exceptionSelector.
 Usage 

Retry 
value: [ ""operation to execute"" ]
configuredBy: [:retry | ""configuration options"" ]


Regards,
The Buenos Aires Smalltalk team