I am trying to implement some of the methods and properties in NSOrderedSet. The read-only property "reversedOrderedSet" has the @NSCopying attribute according to the NSOrderedSet class reference. So, I tried to do this: @NSCopying public var reversedOrderedSet: NSOrderedSet { return
Thanks for your great work on NSURLSession and friends, Daniel!I was wondering if we are only waiting for dispatch to be available on Linux here. In that case, could we have the failing tests (if any) excluded (only on Linux perhaps) and have this merged please? Some of us at IBM would like to
Hi Tony, Daniel, Thanks for your responses. Would it be acceptable if, for now, we check for the availability of Dispatch and conditionally compile calls to it into the current implementation of NSURLSession* (something like the _HAS_DISPATCH__ macro used in CoreFoundation)? This would make
Hello,While working with HTTPCookie I realised that the "description" property isn't currently overridden. This is true for many other Foundation classes subclassing NSObject. Is there any guidance around when this property should be overridden (and when not)? Or is it open for
Hi Tony, Thanks! A starting point will really help. I've filed a feature request on JIRA: https://bugs.swift.org/browse/SR-3697Pushkar N Kulkarni,
IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra
-anthony.par...@apple.com wrote: -To: Pushkar N Kulkarni
Hi Simon, I think that's a warning message from the dynamic linker related to symbol versioning. I'm no expert, but I think the fact that you have a higher libcurl version installed is causing this. In other words, the libcurl version against which libFoundation.so is built (the default on 16.04
Hi Tony, Will, others: Apologies for bringing this up after a long time!I hope we still agree on the use of the "XDG Base Directory Specification". I did a quick read of the spec document. I am happy to file a JIRA report for this.The scope, as I understand it is: CoreFoundation will implement the
Hi Tony/Philippe, There've been a few bug reports related to the coercion problems between Swift and Foundation types on Linux. For example this one: https://bugs.swift.org/browse/SR-2477 (Double/Int don't coerce with NSNumber on Linux). Is there any general approach you'd suggest to work around
Hi Philippe, Thanks for your response! I have one more question.>> In general it is because we don't have bridging on Linux.Will we have it in future? Pardon my ignorance. Pushkar N Kulkarni,
IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra
-phaus...@apple.com wrote:
Hi Tony, Philippe, other onlookers, Long note. Kindly bear with me. I've created SR-2631 to report a crash in a very basic usage of URLSession. I'm providing a general synopsis of the problem below and proposing two approaches to solve it.The test case attached to the report creates a URLSession
swift-corelibs-dev <swift-corelibs-dev@swift.org>Subject: Re: [swift-corelibs-dev] Calendar identifiersOn 4 Oct 2016, at 10:29, Pushkar N Kulkarni via swift-corelibs-dev <swift-corelibs-dev@swift.org> wrote:Hi there, I've hit an obstacle while working on a crash seen in initing
Hi Mike, The tests look great and exhaustive to me. I just wish to mention here that we've experienced hangs in CI tests while connecting to some external URLs in the past (you can see a few tests commented out in the current TestNSURLSession for that reason). It was then recommended, by Tony,
Hi there, I have spent some time working on a basic implementation of HTTPCookieStorage. In the process, I came across two crucial questions related to cookie persistence:1. How do you persist the cookies?2. Where do you persist them?In my current implementation
Thanks Will! "NSHomeDirectory() + "/.foundation/Cookies/shared" seems good to mePushkar N Kulkarni,
IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra
-Will Stanton wrote: -To: Pushkar N Kulkarni/India/IBM@IBMINFrom: Will Stanton
Hi Tony, PRs 911 and 913 reminded me of this conversation you started. The current unit testing infrastructure for URLSession may prove insufficient for future contributions. I've been looking at these tests written by Mike Ferenduros and they appear quite exhaustive! The only issue is that they
Hello there, We have been talking about a known memory leak in String.cString(using: encoding) and String.utf8String over a JIRA report and a closed PR where we considered the option of freeing up the memory allocated by NSString.cString() in String.cString() - this approach isn’t acceptable
Peter: I agree. A stable testing infrastructure is absolutely necessary. Tony: I am curious about where the sources for these tests (that use the external httpbin.org) will be placed? Will it makes sense to have them in TestFoundation and have a guard to exclude them during normal test
Thanks Tony. I revisited your first email in this regard and a standalone tool sounds like the better idea here, given we'd want to try all possible configurations of URLSession and also possibly subject it to some stress.Pushkar N Kulkarni,
IBM RuntimesSimplicity is prerequisite for reliability -
Over the past few months, we've seen random and intermittent failures in the URLSession tests in TestFoundation in the CI builds running on Ubuntu 16.04. Surprisingly, these failures never occur on PR builds. We've tried to reproduce them locally (on matching Ubuntu levels) and fixed locally
Hi Nathaniel, A good place to start is the open Foundation bugs. This query lists all the open Foundation issues. The other way to start is to go through the swift-corelibs-foundation project and search for unimplemented methods and properties (you can simply grep for "NSUnimplemented") and chose
20 matches
Mail list logo