You’ve probably heard a lot about how awesome Git is from all the _cool_ people who are already using it. If you want to be part of the trendy crowd but feel tied down by your old Subversion repositories have no fear; Migrating all of those SVN repos to Git could not be easier **and** you get to keep the entire commit history of your project.
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.
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.
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.
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;
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:
Cloud, Overlay, dependencies, instances, service discovery
Source of truth and consensus what this truth is and who the source is
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:
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):
The underlying issue has to do with switches interpreting too much information of (un)encrypted traffic and dropping them because they wrongly think it’s plain ethernet traffic they need to handle.
MAC addresses starting with a 4 or 6 have have a common bit pattern (likekly that fails with 12 and 14 as well) that cause failure in certain network equipment that’s hard to trace as there is limited.
Quick look at commands that can be used to gather hardware information such as cpu, disks, memory, partition, peripherals etc on Linux OS based systems
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters