The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My work

  • My badges

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming

    20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now

    20140424-Windows-7-free-disk-space

    More Photos
  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,680 other followers

Version 1.8.1 History – builds 121-185 – Continua CI

Posted by jpluimers on 2016/12/07

I’ve been very busy with broken hardware and operating systems lately so today was the first chance to post about recent Version 1.8.1 History of  Continua CI. During October and November the below builds got released.

For almost all of them, you will need to update your agents after installing the build.

v1.8.1.185, November 23rd, 2016

Changes

  • Update: Added preliminary support for Visual Studio 2017 RC to MSBuild, VSTest, MSTest and Visual Studio actions
  • Fix: Issue where ExecuteRepositoryServerSideScripts app setting was not being read preventing running of Git post commit scripts.

v1.8.1.178, November 22nd, 2016

Changes

  • Fix: “changeset.style” file was missing from installer causing error when getting new changesets for new Mercurial repositories.
  • Fix: Issue where Shared Resource Locks at the configuration level would be released before the end of the build, if Shared Resource Locks existed at the stage level and were released.
  • Fix: Build version is now truncated to fit into the maximum field length of 128 characters.
  • Update: Email publisher now supports wider range of secure sockets options. This also fixes an issue where you it would always try to use TLS if it was supported by the server.

v1.8.1.167, November 15th, 2016

Changes

  • Fix: Issue where enabling a configuration would cause all time triggers in other configurations to stop working.
  • Update: Any updates to loggers in the Continua CI Server service configuration file, such as enabling debug logging, are no longer reset when running the installer.

v1.8.1.165, November 14th, 2016

Changes

  • Fix: Repository error status was being reset to “Ready” status when getting new changesets.
  • Fix: Associated triggers are now updated to point to the new repository when repository edit requires it to be recreated.
  • Fix: Concurrency issue with build event handlers causing incorrect build data to be used.
  • Update: Bundled Mercurial used for repository cache has been upgraded to version 3.9.2
  • Update: Improvements to speed when exporting files from agent repository cache to agent workspace.
  • Update: Agent installer has been updated to allow it to be run silently and take additional command line parameters. The relevant parameters are:
    • /usage (optional) – shows usage information.
    • /silent (optional) – runs the setup in silent mode. Note that progress bars will still be displayed.
    • /verysilent (optional) – runs the setup in completely silent mode. No UI is displayed.
    • /log=”filename” (optional) – creates a log file with the specified filename.
    • /dir=”x:\dirname” (optional) – overrides the default installation directory name.
    • /serviceUser (required in silent modes) – the domain and user name of the service user e.g. domain\username.
    • /servicePassword (required in silent modes) – the password of the service user.
    • /serverHostName (optional) – the host name of the ContinuaCI service. Defaults to “localhost” if not provided.
    • /serverPort (optional) – the port of the ContinuaCI service. Defaults to 9000 if not provided.
    • /agentPort (optional) – a port for the agent being installed. Defaults to 9002 if not provided.
    • /workspacePath (optional) – the local path to the agent workspace folder. Defaults to “C:\CI_AWS” if not provided.
  • Update: Now showing the finished time for the last finished build rather than Never for the last queued/running build on List View dashboard.
  • Update: JUnit parser now includes test case times.
  • Update: Diagnostics report is now generated in the background to prevent timeouts.
  • Update: Further improvements to build queue performance.

v1.8.1.121, October 11th, 2016

Changes

  • Fix: Regression bug in v1.8.1.118 where Path Exists property collector plugin would always return false.

–jeroen

Posted in Continua CI, Continuous Integration, Development, Power User, Software Development | Leave a Comment »

Why does the Windows calculator generate tiny errors when calculating the square root of a perfect square? – The Old New Thing

Posted by jpluimers on 2016/12/07

In the continued “floating point code is hard for most software developers” series:

Why does the Windows calculator generate tiny errors when calculating the square root of a perfect square?

Because it doesn’t know that it’s a perfect square.

–jeroen

Posted in Algorithms, Development, Floating point handling, Software Development | Leave a Comment »

Indy: getting response despite exceptions or 4xx HTTP status codes

Posted by jpluimers on 2016/12/07

Formy snippet archive (thanks Walter Prins for answering and Oliver Funcke for asking and elaborating on the answer):

in the case of error, you can get what would’ve normally been in the contentstream from the ExceptionObj.ErrorMessage property.  So you can use something like the following if you want to get the content response regardless of http response code (untested):

var 
  FResponseStream: TStringStream;
  FRequestURL, Content : String;
begin
  //.... etc etc
  try
    FIdHTTP.Get(FRequestURL, FResponseStream);
    Content := FResponseStream.DataString;
  except
    on E:EIdHTTPProtocolException do
      Content := E.ErrorMessage; 
  end;
  // At this point, "Content" contains the response body, both for 
  // successful (200) as well as other response codes.
  
  //.... etc etc
end;

….

You can even do it simpler:

Response := IdHTTP.Get('http://host/path', [404]);

Source: delphi – Indy and REST – Can I prevent exceptions? – Stack Overflow

–jeroen

via:

Posted in Delphi, Delphi 10 Seattle, Delphi 2007, Delphi 2009, Delphi 2010, Delphi XE, Delphi XE2, Delphi XE3, Delphi XE4, Delphi XE5, Delphi XE6, Delphi XE7, Delphi XE8, Development, Software Development | 1 Comment »

Consensus systems (Zookepper, etcd, consul) – what are they?

Posted by jpluimers on 2016/12/06

A while ago,  wrote these very nice G+ posts

The English text is about a year older, but the German text Google Translates pretty well.

The most important points in ot for me were these:

  • Consensus systems are distribute systems, so take at least the P (partitioned) from the CAP theorem.
  • In addidtion, Consensus systems also chose the C (consistent) from the CAP theorem.
  • Since in CAP you can only pick 2 out of 3, the A (available) isn’t guaranteed on Consensus systems.
  • Only three systems get this right: Zookeeper, etcd, Consul. All others shred data eventually.
  • Leader election algorithms Paxos and Raft.
  • Cluster a.k.a. Ensemble provide a consistent view of the data no matter to what member of the Cluster/Ensemble you talk to
  • The (set of) connection(s) from a client to the Cluster/Ensemble is called session
  • Cluster/Ensemble operations are on a tree with nodes that can have atomic operations on them
  • Nodes can be persistent or ephemeral (temporal)
  • All nodes can have data (keep it small enough ~4kilobyte max)
  • Directories in the tree are usually persistent; leaf nodes often ephemeral
  • Useful operations: load balancing, queueing, data availability
  • There are transactions so you can make atomic operations larger. Don’t make them too long.
  • Consistency takes time; expect at max ~1000s of write operations per second
  • Not being available is a feature (it means it still is P and C, just not reachable right now)
  • Clients must cope with the Cluster/Ensemble being temporarily being read-only or unavailable
  • Applications should always re-create any persistent nodes they create (just in case – during non availability – from one consistent phase to another consistent phase) a persistent node is no more.

Some more keywords and links from the article:

–jeroen

Posted in Development, Distributed Computing, Software Development | Leave a Comment »

How do I embed multiple sizes in an .ico file? – Super User

Posted by jpluimers on 2016/12/06

Scripts are soooo coool.

I remember doing similar things in Windows, but couldn’t find the batch files any more. There is an example (thanks Rob W for answering, thanks Suchipi for asking) that works in Mac/Linux:

ImageMagick (Windows/Mac/Linux) contains a command-line tool called convert that can be used for many things, including packing multiple images in one icon:

convert 16.png 32.png 48.png 128.png 256.png -colors 256 icon.ico

The previous command takes 5 PNG images, and combines them into a single .ico file.

Unlike the other answers, this method can easily be used in batch scripts to automatically generate several icon files. In one of my projects, I have a single vector image (SVG), and use Inkscape to generate png’s of various sizes, followed by convert to create a icon container. This is a reduced example (in a bash script):

#!/bin/bash
for size in 16 32 48 128 256; do
    inkscape -z -e $size.png -w $size -h $size icon.svg >/dev/null 2>/dev/null
done
convert 16.png 32.png 48.png 128.png 256.png -colors 256 icon.ico

–jeroen

via:

Posted in bash, Development, Scripting, Software Development | Leave a Comment »

 
%d bloggers like this: