through the swift programming guide, when you know that the variable will never be nil when it has been initiated, maybe treat it as a normal variable is a better way, after all, you can see its type in the quick help window

Am I missing something?

I wrote some code in viewDidLoad() of a VC to block the main thread for seconds (just a long loop), and the watchdog won't fire (not printing anything). Am I missing something?

In the v1.x, the duration logs in the console was the duration of how long the main thread has been blocked. Starting with the 2.0, the duration is always displaying the threshold duration.

That's a sad regression, it was a really interesting feature. Do you think to bring it back?

This is useful if an app wants to do something other than log with NSLog or call assertionFailure()

Other than that I made some nit-picky changes for correctness, like changing some vars for lets and using final.

Watchdog is so cool, it works well, when watchdog find on the main thread is blocking, and I want to know who block the main thread. but I do not know how to print the callstack?

This looks like a port of existing Objective-C code that's floated around for a while. You should probably give credit to the original

https://gist.github.com/jspahrsummers/419266f5231832602bec

There may be other implementations out there to but that's what I found with a quick search.

I realised that the watchdog (of course) times out when the execution stops at a breakpoint. Does this really mean that I have to disable the initialisation of the watchdog normally during development, and enable it only when the app is running "freely"?

Watchdog is very useful, thanks a lot, but I have a problem: During normal execution of my app, I can set a rather small timeout time, say 0.5 sec. This works fine. However, I have a number of unit stress tests that use unrealistic large data, just to identify potential bottlenecks. To setup these tests, the main thread is busy more than the timeout time of 0.5 sec. I could of course increase it, but then I would not catch certain problems. So, what I would like to do is either to disable Watchdog only during the execution of my test setup, or change its timeout time. Is this possible?

When It's switched to main thread, and execute

self.pingTaskIsRunning = false
self.semaphore.signal()

Is it will consume main thread resources too much, if I set threshold a little number(just like 50 ms)?

('Was Created/Downloaded: ', '/Users/username/Downloads/LoadConf (1).pdf.crdownload')

` import sys import os import time from watchdog.observers import Observer from watchdog.events import FileSystemEventHandler

class Event(FileSystemEventHandler): def on_created(self, event): print('Was Created/Downloaded: ', event.src_path)

if name == 'main': path = sys.argv[1] if len(sys.argv) > 1 else '.' event_handler = Event() observer = Observer() observer.schedule(event_handler, path, recursive=True) observer.start() try: while True: time.sleep(5) print('Waiting for a change...') except KeyboardInterrupt: observer.stop() observer.join() `

This pull request contains the following update:

• Fixing @objc inference that changed in Swift 4
• Migrating to Xcode 9.3
• Updating project to use Swift 4.1

I originally created my branch to fix the @objc issues. With Swift 4 and above, rather than put @objc at the top of the class, they now must be put before (or above) each method to expose the method in Objective-C. Without this update, a user who consumes Watchdog will not be able to use it with Objective-C.

I've updated the project and migrated to Swift 4.1 while I was at it at well.