Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
| framework "CoreWLAN" | |
| iface = CWInterface.interface | |
| iface.disassociate | |
| wlans = iface.scanForNetworksWithParameters(nil, error: nil) | |
| wlan = wlans.find {|w| w.ssid == "WLAN_724A"} | |
| p [wlan.bssid, wlan.ssid, wlan.securityMode, wlan.wlanChannel.channelNumber] | |
| keys = File.read("./dictionary.txt").lines.to_a.reverse |
| # | |
| # read/write access to python's memory, using a custom bytearray. | |
| # some code taken from: http://tinyurl.com/q7duzxj | |
| # | |
| # tested on: | |
| # Python 2.7.10, ubuntu 32bit | |
| # Python 2.7.8, win32 | |
| # | |
| # example of correct output: | |
| # inspecting int=0x41424344, at 0x0228f898 |
| static NSData *PSPDFCalculateSHA256FromFileURL(NSURL *fileURL, CC_LONG dataLength, NSError **error) { | |
| NSCParameterAssert(fileURL); | |
| dispatch_queue_t shaQueue = dispatch_queue_create("com.pspdfkit.sha256-queue", DISPATCH_QUEUE_SERIAL); | |
| __block dispatch_io_t readChannel; | |
| void (^processIntError)(int intError) = ^(int intError) { | |
| if (intError != 0) { | |
| PSPDFLogWarning(@"Stream error: %d", intError); | |
| if (error) *error = [NSError errorWithDomain:@"SHA256Error" code:100 userInfo:@{NSLocalizedDescriptionKey: @"failed to open file for calculating SHA256."}]; |
| /* | |
| * This is an example provided by Facebook are for non-commercial testing and | |
| * evaluation purposes only. | |
| * | |
| * Facebook reserves all rights not expressly granted. | |
| * | |
| * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS | |
| * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | |
| * FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL | |
| * FACEBOOK BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN |
| // | |
| // ZUISwitch.h | |
| // zeebox | |
| // | |
| // Created by Will on 26/10/2012. | |
| // Copyright (c) 2012 Electric Labs. All rights reserved. | |
| // | |
| @interface ZUISwitch : UISwitch |
In this article, I'm going to explore a way that we can create views that implement custom Core Animation property animations in a natural way.
As we know, layers in iOS come in two flavours: Backing layers and hosted layers. The only difference between them is that the view acts as the layer delegate for its backing layer, but not for any hosted sublayers.
In order to implement the UIView transactional animation blocks, UIView disables all animations by default and then re-enables them individually as required. It does this using the actionForLayer:forKey: method.
Somewhat strangely, UIView doesn't enable animations for every property that CALayer does by default. A notable example is the layer.contents property, which is animatable by default for a hosted layer, but cannot be animated using a UIView animation block.
When Swift was first announced, I was gratified to see that one of the (few) philosophies that it shared with Objective-C was that exceptions should not be used for control flow, only for highlighting fatal programming errors at development time.
So it came as a surprise to me when Swift 2 brought (What appeared to be) traditional exception handling to the language.
Similarly surprised were the functional Swift programmers, who had put their faith in the Haskell-style approach to error handling, where every function returns an enum (or monad, if you like) containing either a valid result or an error. This seemed like a natural fit for Swift, so why did Apple instead opt for a solution originally designed for clumsy imperative languages?
I'm going to cover three things in this post:
| * { | |
| font-size: 12pt; | |
| font-family: monospace; | |
| font-weight: normal; | |
| font-style: normal; | |
| text-decoration: none; | |
| color: black; | |
| cursor: default; | |
| } |