Duplicated menu items

MBP, El Capitan, v. 1.3.1
When I wake computer from sleep multiple instances are shown in menubar.

Same  here:

What version are you running?

On 5 Jan 2016, at 14:53, John Gibb<EMAIL_ADDRESS>wrote:
Same here:
https://cloud.githubusercontent.com/assets/619602/12118000/1e99fc00-b392-11e5-890e-ea9e5faa2a69.png
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-169021901.

+1

v1.3.1 @matryer

Do you have Xcode? Could you run the master code to test this? I think it was fixed after 1.3.1...

On 5 Jan 2016, at 14:59, John Gibb<EMAIL_ADDRESS>wrote:
v1.3.1 @matryer https://github.com/matryer
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-169025223.

I wanted to test it with master but there are some problem with LaunchAtLoginController as you mentioned here https://github.com/matryer/bitbar/issues/27.
The problem is also non-consistent. Sometimes it duplicates, sometimes it doesn't.

I just built master, and slept then awoke, and didn't see any duplication. As alesf said though, it didn't seem to happen every time—I'll keep you posted if I see it again.

I think it's fixed in the latest - I plan to release v1.4 this weekend.

Happened again with master, don't think it's fixed:

What version is that?

On 6 Jan 2016, at 15:02, John Gibb<EMAIL_ADDRESS>wrote:
Happened again with master, don't think it's fixed:
https://cloud.githubusercontent.com/assets/619602/12145507/928ae582-b45c-11e5-9687-323e6a2c8475.png
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-169346332.

Sorry, meant to paste in the SHA
6dbeb0b636901f737dc94cab88e346b6a8ddaf99

Can you please provide the steps to reproduce this?

Is it many BitBar instances running? Or is it one instance with many plugins?
What does Activity Monitor show when you search for BitBar?

I don't have any reason to believe that there would have been multiple instances running, all I did was hit run from xcode yesterday afternoon. I slept the computer and awoke it a few times, and it was fine. Then, after the computer had slept overnight, when I awoke it this morning I saw what's in the above screenshot.
I unfortunately have already killed and restarted it, so I can't tell you what activity monitor says; if it happens again, I'll capture that information for you.

Thanks - I am wondering if it’s an Xcode thing or if running the app directly also does it.
Perhaps you can try with the latest release candidate?

On 6 Jan 2016, at 15:17, John Gibb<EMAIL_ADDRESS>wrote:
I don't have any reason to believe that there would have been multiple instances running, all I did was hit run from xcode yesterday afternoon. I slept the computer and awoke it a few times, and it was fine. Then, after the computer had slept overnight, when I awoke it this morning I saw what's in the above screenshot.
I unfortunately have already killed and restarted it, so I can't tell you what activity monitor says; if it happens again, I'll capture that information for you.
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-169352198.

Sure, I'll give that a shot. FWIW it originally happened when I used the 1.3 release that was available when the hacker news post went up, so it's happened when I wasn't running via xcode as well. I only used xcode to try a more recent version than what was available as an official release.

It’s possible 1.3 is still on your system somewhere… you can see the version number if you look in the “Preferences” menu for each item. Perhaps you have different versions running?

On 6 Jan 2016, at 15:29, John Gibb<EMAIL_ADDRESS>wrote:
Sure, I'll give that a shot. FWIW it originally happened when I used the 1.3 release that was available when the hacker news post went up, so it's happened when I wasn't running via xcode as well. I only used xcode to try a more recent version than what was available as an official release.
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-169357900.

I was sure to kill 1.3 before running via xcode, so don't think that's it. but I've killed them all and started 1.4beta already so I can't provide evidence :)
Only one running now:
$ ps aux | grep -i bitbar
johngibb         19101   0.0  0.0  2434836    764 s000  S+   10:34AM   0:00.00 grep -i bitbar
johngibb         18964   0.0  0.1  2549904  19224   ??  S    10:30AM   0:00.84 /Applications/BitBar.app/Contents/MacOS/BitBar -psn_0_4940982

$ cat /Applications/BitBar.app/Contents/Info.plist | grep -A1 CFBundleShortVersionString
<key>CFBundleShortVersionString</key>
<string>1.4beta</string>

if it happens again, I'll provide the same output, let me know if there's anything else you want me to capture as well.

That’s a great start - thanks for helping

On 6 Jan 2016, at 15:37, John Gibb<EMAIL_ADDRESS>wrote:
I was sure to kill 1.3 before running via xcode, so don't think that's it. but I've killed them all and started 1.4beta already so I can't provide evidence :)
Only one running now:
$ ps aux | grep -i bitbar
johngibb         19101   0.0  0.0  2434836    764 s000  S+   10:34AM   0:00.00 grep -i bitbar
johngibb         18964   0.0  0.1  2549904  19224   ??  S    10:30AM   0:00.84 /Applications/BitBar.app/Contents/MacOS/BitBar -psn_0_4940982
$ cat /Applications/BitBar.app/Contents/Info.plist | grep -A1 CFBundleShortVersionString
CFBundleShortVersionString
1.4beta
if it happens again, I'll provide the same output, let me know if there's anything else you want me to capture as well.
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-169361238.

Same on version 1.3.1. Only one instance running with duplicates in menubar.
39151   ??  S     16:13.70 /Applications/BitBar.app/Contents/MacOS/BitBar
55384 s001  S+     0:00.00 grep BitBar```

Happened again, 1.4beta and only one instance:

$ ps aux | grep -i bitbar
johngibb         18964   0.1  0.4  2719668  60176   ??  S    10:30AM   2:52.87 /Applications/BitBar.app/Contents/MacOS/BitBar -psn_0_4940982
johngibb         97975   0.0  0.0  2444052    780 s000  S+    9:15PM   0:00.00 grep -i bitbar

$ cat /Applications/BitBar.app/Contents/Info.plist | grep -A1 CFBundleShortVersionString
<key>CFBundleShortVersionString</key>
<string>1.4beta</string>

I'm now also on 1.4beta with only one instance running directly from XCode with some additional weirdness.
When I closed the lid yesterday there was only one instance.
Upon waking from sleep in the morning I saw this.

Then after a minute or so it changed to this.

And also a minute or so later to this.

There was additional BitBar menu item at first that said no plugins are installed and one menu item with a different value (-5°C). All items were marked as "Updated just now". Later on BitBar menu item disappeared and menu item with different value got updated.
Also, when I refresh any item from its dropdown menu only leftmost item shows three dots indicating refreshing.

I wonder whether this is an Xcode oddity - or a bug in the app.

On 7 Jan 2016, at 07:08, Aleš Farčnik<EMAIL_ADDRESS>wrote:
I'm now also on 1.4beta with only one instance running directly from XCode with some additional weirdness.
When I closed the lid yesterday there was only one instance.
Upon waking from sleep in the morning I saw this.
https://cloud.githubusercontent.com/assets/1148574/12164344/1b356b92-b515-11e5-9abc-1186b6e4fe4b.png
Then after a minute or so it changed to this.
https://cloud.githubusercontent.com/assets/1148574/12164349/27c071b8-b515-11e5-9a3e-dea521af3cf4.png
And also a minute or so later to this.
https://cloud.githubusercontent.com/assets/1148574/12164357/360d2536-b515-11e5-9c8e-e953b66d5437.png
There was additional BitBar menu item at first that said no plugins are installed and one menu item with a different value (-5°C). All items were marked as "Updated just now". Later on BitBar menu item disappeared and menu item with different value got updated.
Also, when I refresh any item from its dropdown menu only leftmost item shows three dots indicating refreshing.
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-169577490.

I am not sure if sleeping/waking is the sole trigger for this bug. I have written my first plugin (in Python) today, and I have had it happen multiple times (but without being able to reproduce it reliably) that, during editing and testing, an execution path containing a static print statement like print("BOO!"); sys.exit() will cause BOO! BOO! BOO! to appear in the menu bar. Using the BitBar reset option doesn't help, but quitting and restarting BitBar always does. I do have XCode on my system, but am simply running v1.3.1 as app installed with brew.

I have a theory that new builds of BitBar automatically set the “Open at login” feature. And they’re all hanging around in Derived Data somewhere. What’s in Preferences > Users & Groups > Login Items for you?

On 8 Jan 2016, at 21:07, Leo Breebaart<EMAIL_ADDRESS>wrote:
I am not sure if sleeping/waking is the sole trigger for this bug. I have written my first plugin (in Python) today, and I have had it happen multiple times (but without being able to reproduce it reliably) that, during editing and testing, an execution path containing a static print statement like print("BOO!"); sys.exit() will cause BOO! BOO! BOO! to appear in the menu bar. Using the BitBar reset option doesn't help, but quitting and restarting BitBar always does. I do have XCode on my system, but am simply running v1.3.1 as app installed with brew.
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-170123808.

Mine shows just a single BitBar at the moment, but I will keep an eye out and check what it looks like if the multiplication happens again.

This happens for me as well after sleeping, single bash script containing "curl -s someurl"

It could be that it has nothing to do with sleep.
I have two plugins. One bash plugin that calls curl function, the other simple python script for fuzzy clock.
The python fuzzy clock never duplicates, the bash plugin was fine for some time, but is now showing two instances.
And the computer has been put to sleep many times.
I'm on 1.4 beta2.

I have the newest v1.5 beta, and I'm seeing this too. I've had "Open at login" enabled, but I've disabled it now to see if it helps.

I've been using 1.4-beta.2 a while now and for most of the time the problem seems to be gone. It sometimes still duplicates one plugin, but it resolves by itself (before I had to relaunch BitBar for it to work).

My 1.5 beta is still producing duplicate items in the toolbar. Now it's got 4 items. "Open at login" has been disabled.

Can you look in Activity Monitor to see how many instances of BitBar are running?

It's just 1 process. Currently I have 4 duplicates in totalt in my toolbar.
Here is a screenshot with stats. The thread count varies from 6 to 11.

I quit bitbar. To see if the threads would change. It's now running with 5-11 threads.

@alesf @mattseh I also use curl in my script. Maybe curl it giving some funky output every once in a while, eg if there isn't any network, and this cause Bitbar to show multiple items in the menu bar. I use curl with grep and awk, so it's fairly unlikely. But it might spit out something on stderr.

This could be the case.
I now have all local scripts and come to think of it the problem hasn’t occurred since.

On 9. feb. 2016, at 14:17, hmottestad<EMAIL_ADDRESS>wrote:
@alesf https://github.com/alesf @mattseh https://github.com/mattseh I also use curl in my script. Maybe curl it giving some funky output every once in a while, eg if there isn't any network, and this cause Bitbar to show multiple items in the menu bar. I use curl with grep and awk, so it's fairly unlikely. But it might spit out something on stderr.
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-181859376.

I had the same issue and I also use curl. The issue is when you wake up your computer there is no internet connection yet so curl is retuning empty response. Somehow when script returns no output BitBar start multiple instances of the script. I fixed it with curl http://example.com || echo "..."

I think no response from a script should cause the menu item to be hidden, not duplicate them. Right?

On 9 Feb 2016, at 13:23, Krzysztof Jablonski<EMAIL_ADDRESS>wrote:
I had the same issue and I also use curl. The issue is when you wake up your computer there is no internet connection yet so curl is retuning empty response. Somehow when script returns no output BitBar start multiple instances of the script. I fixed it with curl http://example.com || echo "..."
—
Reply to this email directly or view it on GitHub https://github.com/matryer/bitbar/issues/21#issuecomment-181862302.

What about the timeout. I set my script to run every 10 seconds, what if curl takes more than 10 seconds to timeout, then you might get multiple replies when curl times out.

I'm currently trying: curl -s -m 10  http://.... 2>/dev/null
In a script that runs every 20 seconds. This should make curl timeout before the script is rerun, and any messages on stderr will go to /dev/null

Nope. Doesn't help. I still got two bitbars in my menu bar.

i am seeing this also with latest beta, only 2 local scripts:
memory meter and cpu meter  (both using spark).
the number of cpu meters slowly increases during the day.

+1

+1 still happening for me 1.5.2beta

Sorry about this one, it's a tough one to reproduce. Will give it some attention this week.

Anybody who is having one instance of the app with many plugins, can you please try if https://github.com/iosdeveloper/bitbar/tree/duplicated-status-items fixes it for you? @matryer and I are having a hard time reproducing this bug.

Hi. I just updated to the newly released 1.5 version (non beta) and I'm now seeing this exact issue, which I'm 100% certain wasn't happening before on 1.5 Beta 2. If I choose "Refresh" from the Preferences submenu, my installed plug-ins duplicate in the menubar. It seems related to this discussion.
This only happens on a manual refresh as far as I can tell, not when the plug-ins refresh on their defined cycle. Here's a screenshot showing only one instance of BitBar running as per Activity Monitor, but multiple menu items showing in the menubar after choosing Refresh.

What's unclear to me is why I would be seeing this now under 1.5 and not with the previous 1.5 beta 2 version. I know others were seeing this under the Beta 2 version, but I never did. Very strange. What could have changed between the versions that would cause this now?

We're trying a few things and it's somewhat tricky. We'll figure it out. Thanks for your patience while we address this.

On 16 Feb 2016, at 19:28, Mike M<EMAIL_ADDRESS>wrote:
Hi. I just updated to the newly released 1.5 version (non beta) and I'm now seeing this exact issue, which I'm 100% certain wasn't happening before on 1.5 Beta 2. If I choose "Refresh" from the Preferences submenu, my installed plug-ins duplicate in the menubar. It seems related to this discussion.
This only happens on a manual refresh as far as I can tell, not when the plug-ins refresh on their defined cycle. Here's a screenshot showing only one instance of BitBar running as per Activity Monitor, but multiple menu items showing in the menubar after choosing Refresh.
What's unclear to me is why I would be seeing this now under 1.5 and not with the previous 1.5 beta 2 version. I know others were seeing this under the Beta 2 version, but I never did. Very strange. What could have changed between the versions that would cause this now?
—
Reply to this email directly or view it on GitHub.

Thanks @matryer. I know you guys are working on it. Just wanted to comment on it since it was new for me. Other than that issue, the 1.5 release looks good to me. I especially like the fix for #219 since that one was bugging me from a UI standpoint.
Also, I confirmed that reverting to 1.5 Beta 2 I'm not seeing the duplicated menubar items, so for me at least, I'm only seeing it show up in the final 1.5 release, for whatever that's worth.

Happy to say that the just released 1.5.1 seems to fix the issue for me. No more dupes! At least not when manually refreshing. I'll do some testing with sleep/wake later to confirm.
But I'm only one person. Will be interesting to see if it addresses it for others. Here's hoping!
Thanks for continuing to make improvements and fixes to BitBar!  👍

Thanks for your patience and support. Also, check out the new Add to BitBar button on getbitbar.com and the new Option Key feature :)

On 16 Feb 2016, at 22:22, Mike M<EMAIL_ADDRESS>wrote:
Happy to say that the just released 1.5.1 seems to fix the issue for me. No more dupes! At least not when manually refreshing. I'll do some testing with sleep/wake later to confirm.
But I'm only one person. Will be interesting to see if it addresses it for others. Here's hoping!
Thanks for continuing to make improvements and fixes to BitBar! 👍
—
Reply to this email directly or view it on GitHub.

OK we think the duplicated menu items might have been addressed - can everyone please test with the latest v1.5.1 release and let us know :) @iosdeveloper is doing a great job chasing this issue down.

Sorry guys, but I've installed version 1.5.1 today and I'm still seeing duplicate menu items :-(
So far, 5 of them.
Only a single BitBar instance in Activity Monitor process list.
Process stats say it has 5 children....

Ok please tell us everything you can :)
This is proving to be a pain (a pretty rare one)

On 17 Feb 2016, at 17:30, Romain Criton<EMAIL_ADDRESS>wrote:
Sorry guys, but I've installed version 1.5.1 today and I'm still seeing duplicate menu items :-(
So far, 5 of them.
Only a single BitBar instance in Activity Monitor process list.
Process stats say it has 5 children....
—
Reply to this email directly or view it on GitHub.

I had really strange behaviors this afternoon:
After having my macbook Pro sleeping for a couple hours, I opened it to find 5 instances of BitBar running, with the leftmost not showing my IP address (I only run the script that displays the IP address), but saying "BitBar" instead.
Then after only a couple minutes, 2 instances did disappear.
As i reconnected to the network, my IP address changed and I ended up with the inconsistent display shown in the screenshot below: 3 instances of BitBar showing different information, with the leftmost even saying that I don't have any plugin installed

After some time (maybe 10 or 15 minutes), the stale instances did refresh and started showing the right IP address, and at the same time 2 more instances appeared, then a 3rd one after yet another minute.
This happened as I was using my computer as usual, and without any switch to sleep mode

Let me know if you need any specific information

Its fixed for me, after updating to El Captain

Didn't mention it, but I'm running El Capitan as well, but I still get the issue (as reported earlier).
I'm running 10.11.3 on a mid-2014 Retina 15" MBP

Installed 1.6 today. Problem still here.

Installed 1.6 today. Problem still here.

The problem persists on my machine as well: El Capitan 10.11.3 , 1.5beta

Same here with a curl -s '..' | awk '...' command running every 3 seconds

I also have the issue, El Capitan and 1.6

This should be fixed as well by bfb47b3 and c352e7e.

with 1.8 now there are no duplicate items, but also no items at all.
i have to restart bitbar every day when resuming my notebook,
becuase it is gone from the menubar.

@naddeoa @tresni Any ideas?

@squfrans Was BitBar still running or did it crash (you can check in Activity Monitor.app)?
@naddeoa @tresni Any ideas?

yes, it was running when i closed the lid.
how can i check if it crashed?

If it was still running on wake. ;)

i thought you meant a core dump or similar. no, wasn't running.

Might relate to #288 (pinging @vogonistic) then. Maybe look under ~/Library/Logs/DiagnosticReports or use Console.app.

FWIW,  I'm on 1.8 and I'm not seeing this issue at all with waking from sleep. BitBar stays running perfectly for me.
@squfrans you didn't mention what OS version this is happening on. That might be relevant.

Also which plugins and refresh intervals.

el capitan, plugin: real-cpu-usage-chart.1s.sh and a custom plugin based on it (spark stuff)
ha, the Logs is bingo, attaching crash dump from yesterday:
Process:               BitBar [11669]
Path:                  /Applications/BitBar.app/Contents/MacOS/BitBar
Identifier:            BitBar
Version:               1.8 (1.8.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           BitBar [11669]
User ID:               501

Date/Time:             2016-03-17 09:31:07.924 +0100
OS Version:            Mac OS X 10.11.3 (15D21)
Report Version:        11
Anonymous UUID:        D9096163-10FD-6223-1F28-BEBBBDE37B87

Sleep/Wake UUID:       C4FA9728-13EF-4357-8A1E-9721D84083E0

Time Awake Since Boot: 320000 seconds
Time Since Wake:       65 seconds

System Integrity Protection: disabled

Crashed Thread:        4  Dispatch queue: com.apple.root.default-qos

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0x18:
-->
    __TEXT<PHONE_NUMBER>000000-0000000100034000 [  208K] r-x/rwx SM=COW  /Applications/BitBar.app/Contents/MacOS/BitBar

Application Specific Information:
objc_msgSend() selector name: setContent:

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff930a6386 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff930a57c7 mach_msg + 55
2   com.apple.CoreFoundation      	0x00007fff96e22624 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      	0x00007fff96e21aec __CFRunLoopRun + 1356
4   com.apple.CoreFoundation      	0x00007fff96e21338 CFRunLoopRunSpecific + 296
5   com.apple.HIToolbox           	0x00007fff8d965935 RunCurrentEventLoopInMode + 235
6   com.apple.HIToolbox           	0x00007fff8d96576f ReceiveNextEventCommon + 432
7   com.apple.HIToolbox           	0x00007fff8d9655af _BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit              	0x00007fff87b0a0ee _DPSNextEvent + 1067
9   com.apple.AppKit              	0x00007fff87ed6943 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
10  com.apple.AppKit              	0x00007fff87afffc8 -[NSApplication run] + 682
11  com.apple.AppKit              	0x00007fff87a82520 NSApplicationMain + 1176
12  com.matryer.BitBar            	0x00000001000016c4 start + 52

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        	0x00007fff930acff6 kevent_qos + 10
1   libdispatch.dylib             	0x00007fff8406d099 _dispatch_mgr_invoke + 216
2   libdispatch.dylib             	0x00007fff8406cd01 _dispatch_mgr_thread + 52

Thread 2:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff930a6386 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff930a57c7 mach_msg + 55
2   com.apple.CoreFoundation      	0x00007fff96e22624 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      	0x00007fff96e21aec __CFRunLoopRun + 1356
4   com.apple.CoreFoundation      	0x00007fff96e21338 CFRunLoopRunSpecific + 296
5   com.apple.AppKit              	0x00007fff87bc9065 _NSEventThread + 149
6   libsystem_pthread.dylib       	0x00007fff85093c13 _pthread_body + 131
7   libsystem_pthread.dylib       	0x00007fff85093b90 _pthread_start + 168
8   libsystem_pthread.dylib       	0x00007fff85091375 thread_start + 13

Thread 3:
0   libsystem_kernel.dylib        	0x00007fff930ac6de __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff85093729 _pthread_wqthread + 1283
2   libsystem_pthread.dylib       	0x00007fff85091365 start_wqthread + 13

Thread 4 Crashed:: Dispatch queue: com.apple.root.default-qos
0   libobjc.A.dylib               	0x00007fff8e03b4dd objc_msgSend + 29
1   com.matryer.BitBar            	0x000000010000b760 __27-[ExecutablePlugin refresh]_block_invoke + 29
2   libdispatch.dylib             	0x00007fff84072871 _dispatch_call_block_and_release + 12
3   libdispatch.dylib             	0x00007fff8406733f _dispatch_client_callout + 8
4   libdispatch.dylib             	0x00007fff8406b1cf _dispatch_root_queue_drain + 1890
5   libdispatch.dylib             	0x00007fff8406aa34 _dispatch_worker_thread3 + 91
6   libsystem_pthread.dylib       	0x00007fff8509368f _pthread_wqthread + 1129
7   libsystem_pthread.dylib       	0x00007fff85091365 start_wqthread + 13

Thread 5:: Dispatch queue: com.apple.root.default-qos
0   libsystem_kernel.dylib        	0x00007fff930ad45e read + 10
1   com.apple.Foundation          	0x00007fff858b326b _NSReadFromFileDescriptorWithProgress + 240
2   com.apple.Foundation          	0x00007fff85975a9d -[NSConcreteFileHandle readDataOfLength:] + 481
3   com.matryer.BitBar            	0x000000010000b341 -[ExecutablePlugin refreshContentByExecutingCommand] + 430
4   com.matryer.BitBar            	0x000000010000b760 __27-[ExecutablePlugin refresh]_block_invoke + 29
5   libdispatch.dylib             	0x00007fff84072871 _dispatch_call_block_and_release + 12
6   libdispatch.dylib             	0x00007fff8406733f _dispatch_client_callout + 8
7   libdispatch.dylib             	0x00007fff8406b1cf _dispatch_root_queue_drain + 1890
8   libdispatch.dylib             	0x00007fff8406aa34 _dispatch_worker_thread3 + 91
9   libsystem_pthread.dylib       	0x00007fff8509368f _pthread_wqthread + 1129
10  libsystem_pthread.dylib       	0x00007fff85091365 start_wqthread + 13

Thread 6:
0   libsystem_kernel.dylib        	0x00007fff930ac6de __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff85093729 _pthread_wqthread + 1283
2   libsystem_pthread.dylib       	0x00007fff85091365 start_wqthread + 13

Thread 7:
0   libsystem_kernel.dylib        	0x00007fff930ac6de __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff85093729 _pthread_wqthread + 1283
2   libsystem_pthread.dylib       	0x00007fff85091365 start_wqthread + 13

Thread 8:

Thread 4 crashed with X86 Thread State (64-bit):
  rax: 0x0000000100295ee0  rbx: 0x0000000100295ee0  rcx: 0x0000000100295ee0  rdx: 0x0000000100295ee0
  rdi: 0x0000000100125d40  rsi: 0x00007fff9051ae89  rbp: 0x000070000029fe00  rsp: 0x000070000029fda8
   r8: 0x00007fff76209440   r9: 0x0000000000000100  r10: 0x00007fff9051ae89  r11: 0x0000000000000000
  r12: 0x000000010015c370  r13: 0x00007fff8e03b4c0  r14: 0x0000000100125d40  r15: 0x000000010028dbe0
  rip: 0x00007fff8e03b4dd  rfl: 0x0000000000010246  cr2: 0x0000000000000000

Logical CPU:     0
Error Code:      0x00000000
Trap Number:     0

Binary Images:
       0x100000000 -        0x100033fff +com.matryer.BitBar (1.8 - 1.8.0) <7EAD4E7E-E8BE-3B99-8960-6522105346F2> /Applications/BitBar.app/Contents/MacOS/BitBar
       0x100659000 -        0x10066eff3  libCGInterfaces.dylib (317.9) <473434E1-5269-3077-A047-D05E024AE631> /System/Library/Frameworks/Accelerate.framework/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
       0x1007fa000 -        0x1007faff7 +cl_kernels (???) <25E56EB9-2509-4D4F-BEE5-AEC83C96B409> cl_kernels
    0x7fff6d357000 -     0x7fff6d38e007  dyld (360.19) <9D05FDF4-65CE-3B53-86D4-ABE1A5BF35F3> /usr/lib/dyld
    0x7fff8292f000 -     0x7fff8298cfff  com.apple.CoreServices.OSServices (728.6 - 728.6) <CA616ACB-A872-386C-B16D-193A7E495C4D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff8298d000 -     0x7fff8298fff7  com.apple.xpc.ServiceManagement (1.0 - 1) <3777FD15-B6F3-32A2-A8E3-3E8CE3B8D5E7> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff82990000 -     0x7fff82ab5ff7  com.apple.LaunchServices (728.6 - 728.6) <204CD7A1-D99C-3655-82D7-E8E89F9C666B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff82d48000 -     0x7fff82d4cfff  libcache.dylib (75) <6B245C0A-F3EA-383B-A542-5B0D0456A41B> /usr/lib/system/libcache.dylib
    0x7fff82d4d000 -     0x7fff82df1fff  com.apple.Bluetooth (4.4.3 - 4.4.3f4) <B5F46DA5-EAE8-3F79-864D-1423C61C0A69> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x7fff8329e000 -     0x7fff83326fff  com.apple.CoreSymbolication (3.1 - 58048.1) <6436E5E0-B05C-36D6-942A-47026DD2D874> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
    0x7fff83327000 -     0x7fff835adff7  com.apple.CFNetwork (760.2.6 - 760.2.6) <653B1552-C1EC-36A5-85D0-9FC3ED3CCF72> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff835ae000 -     0x7fff83667ff7  libvMisc.dylib (563.4) <3114F9E9-2B0D-3371-93A1-04BB55CE8DBD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff83668000 -     0x7fff83a6afff  libLAPACK.dylib (1159) <A333AA38-9C2C-329C-AB92-94774C8264C5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff83a6b000 -     0x7fff83a6bfff  libmetal_timestamp.dylib (6<IP_ADDRESS>) <4BA5B935-F932-3863-9B31-EF0A7DEAF15C> /System/Library/PrivateFrameworks/GPUCompiler.framework/libmetal_timestamp.dylib
    0x7fff84058000 -     0x7fff84064fff  com.apple.HelpData (2.1.4 - 90) <3A533F58-9C3B-3341-A8F8-084C96BDB70D> /System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
    0x7fff84065000 -     0x7fff84092fff  libdispatch.dylib (501.20.1) <324C9189-2AF3-3356-847F-6F4CE1C6E901> /usr/lib/system/libdispatch.dylib
    0x7fff8409a000 -     0x7fff84127dd7  com.apple.AppleJPEG (1.0 - 1) <9F0E8564-FCC4-33BE-9C6A-2BA926A33F6F> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
    0x7fff84128000 -     0x7fff84133fff  libGL.dylib (<IP_ADDRESS>) <2A13E40A-BFA1-34FD-925A-C7023FEF254C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff841d7000 -     0x7fff84223ff3  com.apple.HIServices (1.22 - 549) <14FB5BB6-8456-39F9-A694-8A1C12426880> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff84224000 -     0x7fff84237fff  com.apple.CoreBluetooth (1.0 - 1) <BF5F87E3-6AAA-3B1F-9979-7A03D77937C8> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
    0x7fff8423b000 -     0x7fff84275fff  com.apple.QD (3.12 - 302) <3F36A108-C557-353A-A3F7-80DDCB82BB37> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff84290000 -     0x7fff84307fe7  libcorecrypto.dylib (335.20.1) <C6BD205F-4ECE-37EE-BCAB-A76F39CDCFFA> /usr/lib/system/libcorecrypto.dylib
    0x7fff8436a000 -     0x7fff8436afff  com.apple.CoreServices (728.6 - 728.6) <1FC9300C-6D3D-330C-829C-C8F094BC38C6> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff8436b000 -     0x7fff84374ff7  com.apple.CommonAuth (4.0 - 2.0) <B2CEE6B5-9464-35F2-9339-9F52001C8A27> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff843e9000 -     0x7fff846ceff3  com.apple.CoreServices.CarbonCore (1136 - 1136) <FFBDE3BF-0BB3-37A2-8A44-6E25284CC348> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff84c9f000 -     0x7fff84ca5fff  com.apple.IOAccelerator (205.1 - 205.1) <9B56A248-FA12-3DB9-AD97-51EB4700E8A8> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
    0x7fff84ca6000 -     0x7fff84ca8fff  libsystem_coreservices.dylib (19.2) <1B3F5AFC-FFCD-3ECB-8B9A-5538366FB20D> /usr/lib/system/libsystem_coreservices.dylib
    0x7fff84ca9000 -     0x7fff84d9bff7  libJP2.dylib (1442) <3B374049-CCA4-3B4D-9517-583F2BF6B77D> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff84f2a000 -     0x7fff84f91fff  com.apple.framework.CoreWiFi (11.0 - 1101.20) <BEC7B27E-8CE8-3DAB-BFDF-6C240C6A4B12> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi
    0x7fff84fc2000 -     0x7fff84fd0fff  libxar.1.dylib (302) <03207F66-2C4A-3DBD-8D81-70F4C85903C4> /usr/lib/libxar.1.dylib
    0x7fff84fd1000 -     0x7fff84fd4ff7  com.apple.help (1.3.3 - 46) <62056D9B-A87C-3E4D-B4E2-7E1CDB74CE68> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff85090000 -     0x7fff85099ff7  libsystem_pthread.dylib (138.10.4) <327CECD0-B881-3153-8FCC-4FD4818B7F16> /usr/lib/system/libsystem_pthread.dylib
    0x7fff8509a000 -     0x7fff850f5ff7  libTIFF.dylib (1442) <FC2ADE78-3710-31E7-9CE7-44CD61F4B8DC> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff850f6000 -     0x7fff85146ff7  com.apple.Symbolication (1.4 - 58044) <2EC9F04A-4370-39C8-8549-FC6411D87463> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
    0x7fff85163000 -     0x7fff8516dfff  com.apple.NetAuth (6.0 - 6.0) <19E44307-6F9F-3DEC-8C1A-4685BC252A35> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
    0x7fff8516e000 -     0x7fff85170fff  libCGXType.A.dylib (948) <C3D473CF-7261-3E0D-A161-E9B642B75D6A> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
    0x7fff8519a000 -     0x7fff852e4fc7  com.apple.coreui (2.1 - 365.2) <727C55D3-503A-3EC4-8A23-C984E320F65F> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x7fff85313000 -     0x7fff85491fff  com.apple.UIFoundation (1.0 - 436.1) <8C254BB0-1DED-36A2-AAAF-786EB19CCE39> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
    0x7fff8553b000 -     0x7fff8554dfff  libsasl2.2.dylib (209) <02BF4226-23E9-34EC-A727-CF0E205395F8> /usr/lib/libsasl2.2.dylib
    0x7fff8554e000 -     0x7fff85556fff  libGFXShared.dylib (<IP_ADDRESS>) <7E84C8A9-40DA-302A-A3DE-9AE3C61A3465> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff85557000 -     0x7fff8557efff  com.apple.ChunkingLibrary (167 - 167) <508861C9-F5E6-343B-8DD0-D71DFE49ECFD> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
    0x7fff8557f000 -     0x7fff8578cffb  libicucore.A.dylib (551.41) <CFFD7342-A7D6-323A-AC14-B9EECF6EFFED> /usr/lib/libicucore.A.dylib
    0x7fff8578d000 -     0x7fff8587cfff  libxml2.2.dylib (29.2) <F70308DF-313F-334F-8F0E-82E79821583D> /usr/lib/libxml2.2.dylib
    0x7fff8587e000 -     0x7fff8587efff  com.apple.Carbon (154 - 157) <34263101-328D-3FE4-B212-14BD3CFF6965> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff85893000 -     0x7fff85896ffb  libdyld.dylib (360.19) <AA629043-C6F6-32FE-8007-E3478E99ACA7> /usr/lib/system/libdyld.dylib
    0x7fff85897000 -     0x7fff85bebff7  com.apple.Foundation (6.9 - 1256.1) <66106CC9-9D97-3846-88D8-4BF6BB508296> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff85c0a000 -     0x7fff85c15ff7  libChineseTokenizer.dylib (16) <998637AB-DC37-3A7C-A85C-F10FD98CAAD7> /usr/lib/libChineseTokenizer.dylib
    0x7fff85c16000 -     0x7fff85c18ff7  libquarantine.dylib (80) <163CF63A-7455-3D1F-AE57-8C4475A9204C> /usr/lib/system/libquarantine.dylib
    0x7fff85c19000 -     0x7fff85c47ff7  com.apple.DictionaryServices (1.2 - 250) <D9AB6B92-CAF5-3EC2-8D07-639B42DA1CB9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff85c48000 -     0x7fff85c4afff  com.apple.loginsupport (1.0 - 1) <9B2F5F9B-ED38-313F-B798-D2B667BCD6B5> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
    0x7fff85d8d000 -     0x7fff85d91fff  com.apple.CommonPanels (1.2.6 - 96) <61E9D84F-435A-3C7B-A065-047B80775777> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff85d92000 -     0x7fff85e4cfff  com.apple.DiscRecording (9.0.1 - 9010.4.3) <C4EC1EA7-E2AA-30F7-83CC-79171CDD50AA> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
    0x7fff85fd4000 -     0x7fff85fdcfff  com.apple.CoreServices.FSEvents (1223.10.1 - 1223.10.1) <7F5B7A23-BC1D-3FA9-A9B8-D534F1E1979A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff85fdd000 -     0x7fff85fddfff  com.apple.audio.units.AudioUnit (1.13 - 1.13) <D2E8EA94-3828-3D7C-87E2-97E4CD00269D> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x7fff85fde000 -     0x7fff85ff7fff  com.apple.openscripting (1.7.1 - 169.1) <F6532253-9EC5-3FF3-AA16-8AE58531B1D1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff85ff8000 -     0x7fff86021ff7  libxslt.1.dylib (14.1) <AE86E275-499F-3D4F-8433-142186D383CB> /usr/lib/libxslt.1.dylib
    0x7fff86055000 -     0x7fff8605dffb  libsystem_dnssd.dylib (625.20.4) <945B5FB1-DA91-3D45-A961-A8FAD53C1E7E> /usr/lib/system/libsystem_dnssd.dylib
    0x7fff86747000 -     0x7fff86772ffb  libarchive.2.dylib (33.20.2) <6C370A21-63FD-3A68-B4B3-5333F24B770B> /usr/lib/libarchive.2.dylib
    0x7fff86777000 -     0x7fff8679bff7  libJPEG.dylib (1442) <0F9069AB-D830-37DD-8813-B635D1ECB3E4> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff8693a000 -     0x7fff8693fff7  libmacho.dylib (875.1) <CB745E1F-4885-3F96-B38B-2093DF488FD5> /usr/lib/system/libmacho.dylib
    0x7fff8695d000 -     0x7fff86979ff7  libextension.dylib (78) <589FA312-F17C-3A8D-986F-FD995D0065D5> /usr/lib/libextension.dylib
    0x7fff8697a000 -     0x7fff86a0ffff  com.apple.ink.framework (10.9 - 214) <6B573126-A6E9-357F-B36A-AA5BDC0BEAF8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff86c5e000 -     0x7fff86c92ff7  com.apple.CoreVideo (1.8 - 191.2) <88D903C8-E608-320E-8ACD-11E5B3003C18> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff86c93000 -     0x7fff86c99ff7  com.apple.speech.recognition.framework (5.1.1 - 5.1.1) <FA5CB89A-2BFE-38CC-B1A3-E48792CD898C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff86c9a000 -     0x7fff86d23ff7  com.apple.PerformanceAnalysis (1.0 - 1) <FB33FACE-5A99-34E0-83CC-CEDCCFAC74C3> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
    0x7fff86d24000 -     0x7fff86d24fff  com.apple.Cocoa (6.11 - 22) <0A634D46-B468-3CBC-B2A0-16C381C11BF2> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff87137000 -     0x7fff87195fff  com.apple.SystemConfiguration (1.14 - 1.14) <5A70115B-E346-3EBD-A617-9A11C61EEF2E> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff87208000 -     0x7fff872e8ff7  unorm8_rgba.dylib (<IP_ADDRESS>) <6970FC46-0D13-3614-929D-9504AB54C740> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_rgba.dylib
    0x7fff87316000 -     0x7fff879bcffb  com.apple.JavaScriptCore (11601 - 11601.4.2) <33235884-914C-3A2B-AD91-142E5AB8899F> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
    0x7fff879bd000 -     0x7fff879befff  libDiagnosticMessagesClient.dylib (100) <4243B6B4-21E9-355B-9C5A-95A216233B96> /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff879bf000 -     0x7fff87a01ff7  com.apple.Metal (55.2.8 - 55.2.8) <D4D7AC6F-7B31-3D94-B4B1-587EC2856CDB> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff87a1f000 -     0x7fff87a74ff7  com.apple.AE (701 - 701) <FB22BE84-9CB8-36BF-8061-F93D716C0A84> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff87a7d000 -     0x7fff87a7fff7  libsystem_configuration.dylib (802.20.7) <5FD79070-36CC-3D02-BEA7-BB5D2AE97D5D> /usr/lib/system/libsystem_configuration.dylib
    0x7fff87a80000 -     0x7fff886a3ff7  com.apple.AppKit (6.9 - 1404.34) <467468E2-C551-3408-B351-414B21F57DEB> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff886a4000 -     0x7fff886deff7  com.apple.DebugSymbols (132 - 132) <BDF57386-2881-35BD-9310-36904C764E93> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
    0x7fff886df000 -     0x7fff8876cfff  libsystem_c.dylib (1082.20.4) <EAB38A6C-8671-3B13-B500-90EC1B912063> /usr/lib/system/libsystem_c.dylib
    0x7fff8876d000 -     0x7fff88814fff  com.apple.LanguageModeling (1.0 - 1) <E1E4091D-6CAB-36E0-A206-AAADE69791DC> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
    0x7fff888e9000 -     0x7fff888f4fff  com.apple.CrashReporterSupport (10.11 - 717) <474544AD-1199-3ECC-90E5-071847BA72C6> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
    0x7fff88911000 -     0x7fff8892dfff  com.apple.GenerationalStorage (2.0 - 239) <EE667C63-3ADF-34D3-A8A7-316B66C7E290> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
    0x7fff8892e000 -     0x7fff88974ff7  libauto.dylib (186) <999E610F-41FC-32A3-ADCA-5EC049B65DFB> /usr/lib/libauto.dylib
    0x7fff88c03000 -     0x7fff88c03ff7  libkeymgr.dylib (28) <09397E01-6066-3179-A50C-2CE666FDA929> /usr/lib/system/libkeymgr.dylib
    0x7fff88dbf000 -     0x7fff88e6ffff  com.apple.backup.framework (1.7.2 - 1.7.2) <F6A2F892-0728-3DD6-883C-2CDE789BF26F> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x7fff88f12000 -     0x7fff88f37ff7  libPng.dylib (1442) <E8391CE4-9B83-3895-A406-D987FC826D4A> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff88f43000 -     0x7fff88fb7fff  com.apple.framework.IOKit (2.0.2 - 1179.20.6) <D92E537D-F96D-39E1-B9AC-9A18943AFCC7> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff89012000 -     0x7fff89019ff7  libcompiler_rt.dylib (62) <D3C4AB40-23B4-3BC6-8C38-5B8758D14E80> /usr/lib/system/libcompiler_rt.dylib
    0x7fff898aa000 -     0x7fff898abfff  com.apple.TrustEvaluationAgent (2.0 - 25) <0239494E-FEFE-39BC-9FC7-E251BA5128F1> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent
    0x7fff898ac000 -     0x7fff898aefff  libCVMSPluginSupport.dylib (<IP_ADDRESS>) <C88875DF-9888-37A6-AE69-3CABFACDAF45> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff898af000 -     0x7fff8993eff7  libCoreStorage.dylib (517.20.1) <EC540EAA-089C-36D9-BBAA-0684EDE098AB> /usr/lib/libCoreStorage.dylib
    0x7fff89a40000 -     0x7fff89a48fff  com.apple.AppleSRP (5.0 - 1) <25775E90-1DBB-3BFA-B4B4-F8F262B9EC1F> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP
    0x7fff89b45000 -     0x7fff89b45ff7  liblaunch.dylib (756.20.4) <EDF719D6-D2BB-38DD-8C94-4272BEFDA2CD> /usr/lib/system/liblaunch.dylib
    0x7fff89bd4000 -     0x7fff89bd4fff  com.apple.Accelerate.vecLib (3.10 - vecLib 3.10) <E0D5C411-052F-3B71-9562-C1098FB2F86D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff89c26000 -     0x7fff89c2efe7  libsystem_platform.dylib (74.10.3) <D3A27E10-7F08-3603-ACC8-7A92B2C04BAB> /usr/lib/system/libsystem_platform.dylib
    0x7fff89c32000 -     0x7fff89c56fff  com.apple.MultitouchSupport.framework (304.10 - 304.10) <1E0206D9-34AD-3810-8ED0-29DC450D1485> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
    0x7fff89c98000 -     0x7fff89e58feb  libBLAS.dylib (1159) <943445A4-F6CA-3923-882C-154D7D4AEFE0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff8a787000 -     0x7fff8a827ff7  com.apple.Metadata (10.7.0 - 972.16) <3E42A570-BE32-396D-96E1-01B4A778D991> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff8a95c000 -     0x7fff8a976fff  com.apple.Kerberos (3.0 - 1) <836358DE-2731-3ACD-98E3-E5FA48917728> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff8a9b8000 -     0x7fff8a9bbff7  libsystem_sandbox.dylib (460.30.1) <3E0036AF-FC64-3352-8DA4-6B550C2C2562> /usr/lib/system/libsystem_sandbox.dylib
    0x7fff8aa34000 -     0x7fff8aa65fff  com.apple.GSS (4.0 - 2.0) <25DECD44-0905-3E53-9480-DE7BEB84DB83> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff8aa66000 -     0x7fff8aa68ffb  libutil.dylib (43) <4C9BFE8B-563B-3EEA-A323-8F4F14E0A46C> /usr/lib/libutil.dylib
    0x7fff8aa69000 -     0x7fff8aa88ff7  com.apple.framework.Apple80211 (11.0 - 1110.33) <EC583C00-9073-39C3-B613-96D5BA0FDD32> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
    0x7fff8ab87000 -     0x7fff8ab88fff  libsystem_secinit.dylib (20) <FD6ECF2C-1489-32CA-981B-9045B5EB1FAA> /usr/lib/system/libsystem_secinit.dylib
    0x7fff8bb12000 -     0x7fff8bb16fff  libGIF.dylib (1442) <2F7DA684-3510-38C2-B48F-9D33194860A1> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff8bb73000 -     0x7fff8bb81ff7  libbz2.1.0.dylib (38) <28E54258-C0FE-38D4-AB76-1734CACCB344> /usr/lib/libbz2.1.0.dylib
    0x7fff8bb82000 -     0x7fff8bb82fff  com.apple.Accelerate (1.10 - Accelerate 1.10) <97B71D88-9C93-3943-B09E-642183B4E1AC> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff8bb83000 -     0x7fff8bb86fff  libCoreVMClient.dylib (119.5) <CD7DE25C-D7AD-3ECD-BEEC-F57992A4A08E> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff8bb87000 -     0x7fff8bb89fff  com.apple.EFILogin (2.0 - 2) <38150198-DD7F-3C73-BCAA-C74BB376393A> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin
    0x7fff8bb8a000 -     0x7fff8bb8bffb  libremovefile.dylib (41) <B8D1A5FC-CFD5-3AAB-8A10-14DDC129710A> /usr/lib/system/libremovefile.dylib
    0x7fff8c1c6000 -     0x7fff8c1dcff7  libsystem_coretls.dylib (83.20.8) <75C97D88-0A63-3093-AE83-DE33EB7405CE> /usr/lib/system/libsystem_coretls.dylib
    0x7fff8c1e9000 -     0x7fff8c237fff  libcurl.4.dylib (90) <FF42FAA6-E71B-3D0D-B5C9-B05BD2460C9A> /usr/lib/libcurl.4.dylib
    0x7fff8c2b6000 -     0x7fff8c45cff7  com.apple.audio.toolbox.AudioToolbox (1.13 - 1.13) <F912765D-88ED-3324-B512-3778A8CE878B> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff8c84b000 -     0x7fff8c95dfef  libvDSP.dylib (563.4) <C069B6A3-D7CD-3B72-918C-15514066A2F3> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff8c95e000 -     0x7fff8c96fff7  libz.1.dylib (61.20.1) <B3EBB42F-48E3-3287-9F0D-308E04D407AC> /usr/lib/libz.1.dylib
    0x7fff8cb9c000 -     0x7fff8cbaafff  com.apple.opengl (12.0.40 - 12.0.40) <D37D88AE-0731-3105-99AB-984DA9B9BCE6> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff8cbd5000 -     0x7fff8cc44fff  com.apple.datadetectorscore (7.0 - 460) <CDBB7D7D-B189-37B0-AA4B-DC79090D0D71> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
    0x7fff8cc45000 -     0x7fff8cc98ff7  libc++.1.dylib (120.1) <8FC3D139-8055-3498-9AC5-6467CB7F4D14> /usr/lib/libc++.1.dylib
    0x7fff8d242000 -     0x7fff8d24bfff  com.apple.icloud.FindMyDevice (1.0 - 1) <BB049D2D-9789-39E8-A09D-D300E7AA94D2> /System/Library/PrivateFrameworks/FindMyDevice.framework/Versions/A/FindMyDevice
    0x7fff8d47a000 -     0x7fff8d47aff7  libunc.dylib (29) <1D0F8265-F026-3CBD-93D3-F8DF14FFCE68> /usr/lib/system/libunc.dylib
    0x7fff8d47f000 -     0x7fff8d4d0ff7  com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <BB7C0F61-E39B-382C-AF03-1650C054BFE1> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff8d4d1000 -     0x7fff8d4fafff  libc++abi.dylib (125) <DCCC8177-3D09-35BC-9784-2A04FEC4C71B> /usr/lib/libc++abi.dylib
    0x7fff8d556000 -     0x7fff8d561fff  libkxld.dylib (3248.30.4) <BAA3DDEC-AD81-3C29-AECC-59E4AD114D3C> /usr/lib/system/libkxld.dylib
    0x7fff8d586000 -     0x7fff8d6e1ffb  com.apple.WebKitLegacy (11601 - 11601.4.4) <5CC2787B-FDD4-3025-BD63-4021F97787A8> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebKitLegacy.framework/Versions/A/WebKitLegacy
    0x7fff8d7cd000 -     0x7fff8d819fff  com.apple.print.framework.PrintCore (11.2 - 472.2) <449D8AB5-7891-32D0-9DC5-C90FE10DC0BF> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff8d81a000 -     0x7fff8d889fff  com.apple.SearchKit (1.4.0 - 1.4.0) <CA50106F-F45A-36AC-AD2B-C3B19F5DD52F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff8d88a000 -     0x7fff8d89bff7  libsystem_trace.dylib (201.10.3) <B485369F-E3A1-319E-998C-89AAF606079E> /usr/lib/system/libsystem_trace.dylib
    0x7fff8d89c000 -     0x7fff8d8a1ff7  libheimdal-asn1.dylib (453.20.2) <EE3DD8E9-E543-3849-ADC9-EDBF2379C97C> /usr/lib/libheimdal-asn1.dylib
    0x7fff8d935000 -     0x7fff8dc2afff  com.apple.HIToolbox (2.1.1 - 807.2) <D9338BEF-CA84-3085-B6CB-4E93B3B9A2E1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff8dfa3000 -     0x7fff8e039fff  com.apple.ColorSync (4.9.0 - 4.9.0) <8BB8DF19-C24F-39F8-8B90-AD186D74587C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff8e03a000 -     0x7fff8e3a5657  libobjc.A.dylib (680) <58CB8CFC-7DBD-3A53-BD72-A42FF799B21E> /usr/lib/libobjc.A.dylib
    0x7fff8e55b000 -     0x7fff8e5aaff7  com.apple.opencl (2.6.9 - 2.6.9) <27643341-DC6F-3C2F-8B8B-637061979BF3> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff8e5ab000 -     0x7fff8e9d9fff  com.apple.vision.FaceCore (3.3.1 - 3.3.1) <B8482831-77BD-3FBC-A0B1-12502353AA57> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
    0x7fff8e9da000 -     0x7fff8e9dffff  com.apple.DiskArbitration (2.7 - 2.7) <B7FAE647-156A-30C8-BA8B-69D188D02602> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff8ea22000 -     0x7fff8ea23fff  liblangid.dylib (122) <9CC4F0D1-5C51-3B69-BC8F-EE3A51FD0822> /usr/lib/liblangid.dylib
    0x7fff8eafb000 -     0x7fff8eb69ff7  com.apple.ApplicationServices.ATS (377 - 394.3) <0DDD3503-3D74-3CCA-BD25-7F19B03C2579> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff8ed11000 -     0x7fff8ed3afff  libsystem_info.dylib (477.20.1) <6513635B-4ADE-3B45-BF63-ED7AC565B0C9> /usr/lib/system/libsystem_info.dylib
    0x7fff8ed3b000 -     0x7fff8ed3effb  libScreenReader.dylib (425.102) <BDC46586-4925-38F2-85D3-BD23DB6E6D43> /usr/lib/libScreenReader.dylib
    0x7fff8ef2b000 -     0x7fff8f1d1ff7  com.apple.CoreData (120 - 641.3) <65509AA2-A0E6-3EE3-BDFE-B9B120F744ED> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff8f20b000 -     0x7fff8f3d9ffb  com.apple.QuartzCore (1.11 - 410.14) <CB19502B-D25F-379C-B50F-08A98FF73B68> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff8f816000 -     0x7fff8f880ff7  com.apple.framework.CoreWLAN (11.0 - 1101.20) <6A535459-6A8A-3D60-986B-EE7ED833A9C3> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
    0x7fff8f8a6000 -     0x7fff8f8a6fff  libOpenScriptingUtil.dylib (169.1) <03BEF6F0-07CD-3EDC-9D11-32202C1857B6> /usr/lib/libOpenScriptingUtil.dylib
    0x7fff8f8b0000 -     0x7fff8f8e1ff7  libtidy.A.dylib (15.17) <03EF1071-8B43-3B41-9879-118FA27F89C5> /usr/lib/libtidy.A.dylib
    0x7fff8f8e2000 -     0x7fff8f932fff  libcups.2.dylib (435) <28A05475-9DBF-35EA-B218-3432B69EA18B> /usr/lib/libcups.2.dylib
    0x7fff8f93b000 -     0x7fff8f96eff7  com.apple.MediaKit (16 - 809) <BF8032FE-6645-37F6-A622-BC7EEE3EAABF> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
    0x7fff8f9c2000 -     0x7fff8faa9ff7  libcrypto.0.9.8.dylib (59) <ED1C2A26-8FFC-30FF-8726-FF952EF94ADF> /usr/lib/libcrypto.0.9.8.dylib
    0x7fff8fab4000 -     0x7fff8fadbfff  com.apple.shortcut (2.16 - 93) <D9DD2F6A-4AC7-38BD-A3B6-A9682EFCCE2E> /System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
    0x7fff8fadc000 -     0x7fff8fae7fff  libcsfde.dylib (517.20.1) <42376761-F1B3-3086-AFBC-231507582BBE> /usr/lib/libcsfde.dylib
    0x7fff8fbaf000 -     0x7fff8fcabff7  libFontParser.dylib (158.4) <BF7F82EB-7820-364A-865E-442F42BFDFA4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x7fff8fd33000 -     0x7fff8ffc9fff  libmecabra.dylib (696.4) <0A1574F0-3222-3856-A1C6-D8BE20DC4C48> /usr/lib/libmecabra.dylib
    0x7fff90522000 -     0x7fff90551ffb  libsystem_m.dylib (3105) <26655445-CA97-321E-B221-801CB378D1AA> /usr/lib/system/libsystem_m.dylib
    0x7fff90552000 -     0x7fff9056eff7  libsystem_malloc.dylib (67) <9EECAB18-F025-34C4-8E32-7EFFA6720EFC> /usr/lib/system/libsystem_malloc.dylib
    0x7fff9056f000 -     0x7fff90577fff  libcopyfile.dylib (127) <F5133269-0B22-388C-A57C-079667B6291E> /usr/lib/system/libcopyfile.dylib
    0x7fff90588000 -     0x7fff9059ffff  libmarisa.dylib (4) <E4919B03-D9BD-3AF8-B436-C415C98E3F0A> /usr/lib/libmarisa.dylib
    0x7fff905de000 -     0x7fff905f7fff  com.apple.CFOpenDirectory (10.11 - 194) <C21F33AA-CD06-3163-A1F3-1D116F788A11> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff90673000 -     0x7fff90690ff7  com.apple.AppleVPAFramework (2.1.2 - 2.1.2) <2B459E1F-0563-30B2-A04D-CF1793426B66> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA
    0x7fff90691000 -     0x7fff90691fff  libenergytrace.dylib (10) <A4AE7CBD-CF0A-3A74-8098-B642CE496611> /usr/lib/libenergytrace.dylib
    0x7fff90a24000 -     0x7fff90a3dfef  libcompression.dylib (25) <C8546222-B022-39EA-9896-0387BA1D5C51> /usr/lib/libcompression.dylib
    0x7fff90a3e000 -     0x7fff90a3fffb  libSystem.B.dylib (1226.10.1) <5A4257EF-3145-3BB3-87A4-0D2404A9462D> /usr/lib/libSystem.B.dylib
    0x7fff90abb000 -     0x7fff90abcfff  libsystem_blocks.dylib (65) <49D42329-7DE9-3413-92C3-A473A7E9CF35> /usr/lib/system/libsystem_blocks.dylib
    0x7fff90b99000 -     0x7fff90ba1fff  com.apple.frameworks.CoreDaemon (1.3 - 1.3) <D44F75E7-C679-3C21-AD76-8FA8A2B898F1> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon
    0x7fff90be2000 -     0x7fff90beeff7  com.apple.OpenDirectory (10.11 - 194) <5409AC27-3B83-3F35-8EB5-51228B4604AE> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff90bef000 -     0x7fff90dfcff7  com.apple.CoreImage (11.2.0 - 366.2.7) <344F1067-5F52-3626-8F6C-2B678DEB80A1> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff90ed9000 -     0x7fff90efbfff  com.apple.IconServices (68.1 - 68.1) <3ECAA762-1193-3D76-A25F-7680DB3A957E> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
    0x7fff90efc000 -     0x7fff90f04ff7  libcldcpuengine.dylib (<IP_ADDRESS>) <5FFEDBEF-2EFE-3F91-BABC-1E73B28487A2> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib
    0x7fff90f05000 -     0x7fff90f0eff3  libsystem_notify.dylib (150.20.3) <243FADE1-255A-3B78-8033-F336CD64B817> /usr/lib/system/libsystem_notify.dylib
    0x7fff9120e000 -     0x7fff9121aff7  com.apple.speech.synthesis.framework (5.4.12 - 5.4.12) <E507D438-517D-32AE-8609-02ACD2F0D692> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff9125f000 -     0x7fff91296ff7  com.apple.LDAPFramework (2.4.28 - 194.5) <79D981F2-F70C-3E47-B124-DC0C90D45563> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x7fff91d19000 -     0x7fff91d2afff  libcmph.dylib (6) <BA4BF2C6-7F4E-33B8-9DD7-619C9EB83ECF> /usr/lib/libcmph.dylib
    0x7fff91d2b000 -     0x7fff91d3bfff  libSparseBLAS.dylib (1159) <81330B45-9CA3-34AC-891C-6E770C3DFC24> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff91d3f000 -     0x7fff91d42fff  com.apple.IOSurface (108.0.1 - 108.0.1) <7B05B27A-5CC4-30D4-8A10-ED444A2807A2> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff91d43000 -     0x7fff92e02ff7  com.apple.WebCore (11601 - 11601.4.4) <815CFF7F-3839-3FDE-9B82-79253BFB3624> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore
    0x7fff92e80000 -     0x7fff92e9aff3  liblzma.5.dylib (10) <CC03591B-FA57-3CA5-AC81-0D76033AC0CE> /usr/lib/liblzma.5.dylib
    0x7fff92e9b000 -     0x7fff92ea0ff3  libunwind.dylib (35.3) <124E0F05-2350-3774-A32C-7F5BF38EDE73> /usr/lib/system/libunwind.dylib
    0x7fff9305f000 -     0x7fff9305ffff  com.apple.ApplicationServices (48 - 48) <DD9C4070-C0FC-3984-BCED-72E6E99838FC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff93060000 -     0x7fff93062ff7  libRadiance.dylib (1442) <9E9084DC-C0DF-30DF-BD6B-7AED3799A129> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff93095000 -     0x7fff930b3fff  libsystem_kernel.dylib (3248.30.4) <9CEB6C3B-1CAF-3C32-A9FD-93BC72CBCEA1> /usr/lib/system/libsystem_kernel.dylib
    0x7fff93260000 -     0x7fff9338cff7  com.apple.CoreText (352.0 - 494.10) <9FD834B1-FF8E-3EB0-BB11-6E9120969086> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff9338e000 -     0x7fff933d3ff7  com.apple.coreservices.SharedFileList (24.4 - 24.5) <72156BE7-0804-3F90-9AF9-14C4739430C2> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff933d4000 -     0x7fff933dcfff  com.apple.NetFS (6.0 - 4.0) <BDD59EC5-D399-31EA-9B2A-60E3A859FC42> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff933dd000 -     0x7fff94648ffb  com.apple.CoreGraphics (1.600.0 - 948) <A5BCCC6D-D931-360D-BF45-02F5ED4E1773> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff946c4000 -     0x7fff946dbff7  libsystem_asl.dylib (322.30.1) <9B500E4E-E462-321E-828E-5524DC984C1B> /usr/lib/system/libsystem_asl.dylib
    0x7fff947e3000 -     0x7fff9480cffb  libRIP.A.dylib (948) <96E8F983-A8BA-3B0F-9035-E09642A63F6E> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
    0x7fff94ca2000 -     0x7fff94d88fef  unorm8_bgra.dylib (<IP_ADDRESS>) <F2A325FF-D55F-3091-88E2-5EBF3648274A> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_bgra.dylib
    0x7fff94d89000 -     0x7fff94d9fff7  libLinearAlgebra.dylib (1159) <FA316609-9851-3C5C-AF46-685A25768D45> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff94da0000 -     0x7fff94e92ff7  libiconv.2.dylib (44) <F05A0A5A-92A9-3668-8F20-F27CBDA26BE9> /usr/lib/libiconv.2.dylib
    0x7fff94e93000 -     0x7fff94ed1ff7  libGLImage.dylib (<IP_ADDRESS>) <ACC6C7B0-A805-344C-AAC3-BA50780227E1> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff94eda000 -     0x7fff94f4efff  com.apple.Heimdal (4.0 - 2.0) <009F223D-B89B-376B-94F5-6D982CBEF771> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
    0x7fff94f52000 -     0x7fff94f5afff  libsystem_networkextension.dylib (385.20.6) <DC8A102A-BF02-31A4-8914-65C34DF6B592> /usr/lib/system/libsystem_networkextension.dylib
    0x7fff94f5b000 -     0x7fff94f67ff7  com.apple.SpeechRecognitionCore (2.2.7 - 2.2.7) <8B6C0DB6-8744-3AEB-BD00-9FA6967E7125> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore
    0x7fff95114000 -     0x7fff9511fff7  libcommonCrypto.dylib (60075.20.1) <766BC3F5-41F3-3315-BABC-72718A98EA92> /usr/lib/system/libcommonCrypto.dylib
    0x7fff956c9000 -     0x7fff956eafff  com.apple.Sharing (442.9.1 - 442.9.1) <672DE6DF-98E0-30A4-BA25-44BDE188D0BE> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
    0x7fff95873000 -     0x7fff95875ff7  com.apple.securityhi (9.0 - 55006) <B97C1C77-AA51-33ED-941D-F766BC94CD9E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff95a3f000 -     0x7fff95a4effb  com.apple.LangAnalysis (1.7.0 - 1.7.0) <0D1BCC13-76B9-3C19-85AA-D8DD8299F007> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff95b1e000 -     0x7fff95c2cff3  com.apple.desktopservices (1.10 - 1.10) <0BAED9FA-EFA5-3DA0-8715-043FD2400B77> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
    0x7fff95c3a000 -     0x7fff95c56ff3  libresolv.9.dylib (60) <A650B5C8-1950-36A0-86D1-0B2465318BFA> /usr/lib/libresolv.9.dylib
    0x7fff95c60000 -     0x7fff95cc1ff7  libsystem_network.dylib (583.20.10) <865FE79A-A22D-3733-A14F-FC7B37F3AECD> /usr/lib/system/libsystem_network.dylib
    0x7fff95d0a000 -     0x7fff95d33fff  libxpc.dylib (756.20.4) <61AB4610-9304-354C-9E9B-D57198AE9866> /usr/lib/system/libxpc.dylib
    0x7fff95d3b000 -     0x7fff95fbbff3  com.apple.security (7.0 - 57337.20.44) <290E0078-464E-30EE-8288-8B29A875FFE3> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff95fbc000 -     0x7fff95ffdff7  libGLU.dylib (<IP_ADDRESS>) <1C9899B5-4741-340F-A2D7-F9AF03B42A47> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff95ffe000 -     0x7fff9633bff3  com.apple.WebKit (11601 - 11601.4.4) <F35B60CF-8F10-3FC3-9E01-F7C887070EA2> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
    0x7fff9646c000 -     0x7fff9646dff3  com.apple.print.framework.Print (10.0 - 266) <BF573614-5666-3D16-9D45-4690911F030A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff964e9000 -     0x7fff96517ff7  com.apple.CoreServicesInternal (248.2 - 248.2) <7D0D2C65-C4C4-3FBD-89A7-12302EA444AA> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
    0x7fff9651d000 -     0x7fff96562ff3  libFontRegistry.dylib (155.1) <593CC743-3785-3CC5-A229-D3846C51E054> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff96563000 -     0x7fff96680fff  libsqlite3.dylib (216.4) <DC3D59E7-91A3-374F-957C-6699729CD82B> /usr/lib/libsqlite3.dylib
    0x7fff96888000 -     0x7fff9688dfff  com.apple.TCC (1.0 - 1) <C53628CA-0C75-34B6-AE6E-8BCF8A3ED099> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
    0x7fff9697c000 -     0x7fff9698cfff  libbsm.0.dylib (34) <7E14504C-A8B0-3574-B6EB-5D5FABC72926> /usr/lib/libbsm.0.dylib
    0x7fff9699d000 -     0x7fff969a0ff7  libCoreFSCache.dylib (119.5) <C7008E64-0AFB-3446-929E-BC3F76DEF049> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff969a1000 -     0x7fff969a6fff  com.apple.ImageCapture (9.0 - 9.0) <33F7822F-1124-3D73-AF66-515EA32A4A47> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff96b86000 -     0x7fff96bbefff  com.apple.RemoteViewServices (2.0 - 99) <596153FD-3CB9-3FED-9D63-1B73B01AC6DB> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
    0x7fff96bbf000 -     0x7fff96c95ff7  com.apple.DiskImagesFramework (10.11.3 - 417.2) <25BBE20C-E92B-360F-A326-093B61CC7B5E> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages
    0x7fff96db2000 -     0x7fff97228fff  com.apple.CoreFoundation (6.9 - 1256.14) <768A7FB7-9143-3148-8591-7C6ED3162D35> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff97d38000 -     0x7fff981f6fcf  com.apple.vImage (8.0 - 8.0) <85FB412E-EB30-3433-A79B-B3970FC83580> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff981f7000 -     0x7fff98402fff  libFosl_dynamic.dylib (16.24) <363B7CEE-B662-32F3-9D7B-245E64927C35> /usr/lib/libFosl_dynamic.dylib
    0x7fff98403000 -     0x7fff9842afff  com.apple.ProtectedCloudStorage (1.0 - 1) <F9E1BDE2-16AF-34B5-B7FE-127D511BDC9E> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage
    0x7fff984cd000 -     0x7fff98696ff7  com.apple.ImageIO.framework (3.3.0 - 1442) <2C8AF87E-080E-3FD8-824D-332B43DF4B61> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff98919000 -     0x7fff9898dff3  com.apple.securityfoundation (6.0 - 55126) <11644DA4-F1CF-3FB1-86A0-0DA8E8C27148> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff989c2000 -     0x7fff989c6fff  libpam.2.dylib (20) <CFCD19BD-87BC-3F2B-BB1C-4C23E8E55F1A> /usr/lib/libpam.2.dylib
    0x7fff98a9e000 -     0x7fff98ab9ff7  libCRFSuite.dylib (34) <078B4CD8-6A8C-3067-B2BA-0C2A0BAB8AC3> /usr/lib/libCRFSuite.dylib

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 46
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 1623212
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=246.3M resident=0K(0%) swapped_out_or_unallocated=246.3M(100%)
Writable regions: Total=55.1M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=55.1M(100%)

                                VIRTUAL   REGION
REGION TYPE                        SIZE    COUNT (non-coalesced)
===========                     =======  =======
Accelerate.framework               256K        3
Activity Tracing                  2048K        2
CG backing stores                   16K        5
CG image                            28K        7
CG shared images                   272K        8
CoreAnimation                       16K        3
CoreUI image data                  188K        3
CoreUI image file                  192K        4
Dispatch continuations            4096K        2
Kernel Alloc Once                    8K        3
MALLOC                            19.1M       18
MALLOC guard page                   32K        7
Memory Tag 242                      12K        2
OpenCL                               8K        2
Process Corpse Info               2048K        2
STACK GUARD                       56.0M        9
Stack                             11.1M        9
VM_ALLOCATE                         48K        8
__DATA                            19.8M      208
__IMAGE                            528K        2
__LINKEDIT                        91.3M        6
__TEXT                           155.0M      217
__UNICODE                          552K        2
mapped file                      117.4M       15
shared memory                     16.3M        9
===========                     =======  =======
TOTAL                            496.2M      531

That crash is the same as #282

I'm seeing duplicates in menu consistently after sleep. Sierra, 1.9.2, running one custom plugin (a shell script managing two VPNs).


Avoid CoW when appending inbound frame bytes.

Motivation:
This is basically a similar issue to #104: we have a CoW data structure (ByteBuffer) in some of
these states, and when calling append on them they force an unnecessary CoW. We can reproduce the
fix from that patch, which is to define an empty state and swap into it before we run the append.
We also define a helper that ensures that we don't screw this up.
Modifications:

Added new appending state to HTTP2FrameDecoder
Added helpers for avoiding a CoW
Avoided CoW in HTTP2FrameDecoder.

Result:
Fewer unnecessary copies

This is another roughly 1% perf gain on the h2load benchmark.


Autocomplete use the InputBase component.

According to @olivundassinari "Autocomplete and Select use the InputBase component, the approach should work identically."
I am using the following code to change the appearance of the autocomplete when it is disabled. Managing to put the TextField in read mode, but the ability to select is still enabled. I only manage to disable the ability to select using the disabled property, provided by autocomplete, showing the same appearance that I want to avoid.
I ask the Material-UI team, especially @olivundassinari, to check the question before closing.
<Autocomplete            //disabled={isDisabled}           renderInput={(params) => (           <TextField             {...params}              InputProps={{               ...params.InputProps,                readOnly: Boolean(true),                disabled: Boolean(true),                                      }}                     helperText={helperText ? helperText : ""}           />         )}       />

Duplicate of #24023

Duplicate of #24023

That's what I say!!  What's wrong with: https://codesandbox.io/s/xenodochial-shtern-7icn9?file=/src/playground.js
And why do they look so different.

That's what I say!!  What's wrong with: https://codesandbox.io/s/xenodochial-shtern-7icn9?file=/src/playground.js
And why do they look so different.


Generalize view service notes request to get notes satisfying a set of constraints

In support of planning fully general intents, the view service needs to be able to return notes based on more complex constraints. Specifically, we should be able to specify in a single request:

How much value is requested from each of a list of exact address indices?
How much value is requested from each of a list of accounts (exclusive of the amounts required by 1)?
How much value is requested from any source (exclusive of the amounts required by 1 and 2)?

The set of notes returned should satisfy all the constraints, which is to say:

there are no duplicate notes returned,
the sum of all the notes for each exact address index is equal to or greater than the sum specified in (1) for that address index,
the sum of all the notes for each account is equal to or greater than the sum specified in the subset of address indices in (1) which belong to that account, added to the sum specified in (2) for that account, and
the sum of all the notes returned in aggregate is equal to or greater than the sum specified in (1), (2), and (3) combined.

We can also add a field to specify constraints on the height the note was created or spent, which allows us to fold the voting notes requests into this kind of request. The Lifetime represents two intervals [not_created_before, created_before) and (spent_after, not_spent_after] which bound the creation height and spend height of the note. Any of the fields can be unset, which means that the interval is unbounded on that side. For this interval calculation, an unspent note is considered to be spent at height infinity, which means that specifying not_spent_after = u64::MAX excludes unspent notes, and specifying spent_after = u64::MAX excludes spent notes.
The proposed new request looks like:
message NotesRequest {
  // Specify value to be drawn from a specific address index
  message FromAddress {
    core.crypto.v1alpha1.AddressIndex address = 1;
    optional core.crypto.v1alpha1.AssetId asset_id = 2;
    optional core.chain.v1alpha1.Amount amount = 3; // if unset, demand all; must be set if `asset_id` is
  }

  // Specify value to be drawn from a specific account
  message FromAccount {
    uint32 account = 1;
    optional core.crypto.v1alpha1.AssetId asset_id = 2;
    optional core.chain.v1alpha1.Amount amount = 3; // if unset, demand all; must be set if `asset_id` is
  }

  // Specify value to be drawn from any source whatsoever
  message FromAnywhere {
    optional core.crypto.v1alpha1.AssetId asset_id = 2;
    optional core.chain.v1alpha1.Amount amount = 3; // if unset, demand all; must be set if `asset_id` is
  }

  // All the constraints on specific addresses
  repeated FromAddress from_addresses = 2;

  // All the constraints on specific accounts
  repeated FromAccount from_accounts = 3;

  // All the constraints on the entire set of notes
  repeated FromAnywhere from_anywhere = 4;

  // Constraint on the lifetime of all notes returned
  message Lifetime {
    optional uint64 not_created_before = 1;
    optional uint64 created_before = 2;
    optional uint64 spent_after = 3;
    optional uint64 not_spent_after = 4;
  }

  // Bounds the "lifetime" for all returned notes by this request. If unset, the default
  // is the lifetime constraint of [0, infinity) -> (u64::MAX, infinity], which restricts
  // to all unspent notes, created at any height. (This default is useful because in the
  // case of a spend, you just care about the fact that notes are unspent.)
  Lifetime lifetime = 5;

  // Identifies the FVK for the notes to query.
  optional core.crypto.v1alpha1.AccountID account_id = 14;

  // Authorizes the request.
  optional ViewAuthToken token = 15;
}

Internally, the procedure for fulfilling this request in the view service should be to iterate through the constraints, finding notes that satisfy each. After each constraint is satisfied, attempt to satisfy or partially satisfy all remaining constraints with the excess value beyond that which was used to satisfy all satisfied constraints. Modify all the constraints which were able to be (partially) satisfied by this procedure to reduce their demand, then continue the iteration, making sure to skip note records in the database which already were accumulated. An important note is that constraints with "infinite" demand (i.e. unset amount fields) must be dealt with last or else they will greedily eat up value. So we should solve all the finite constraints first, then fulfill all the remaining ones afterwards.
Note that each voting note request must be made separately for each proposal, because each NotesRequest below only accommodates a single Lifetime constraint. This is intentional, because while it's tractable to solve the constraints when each only demands a typed amount, adding arbitrary interval constraints to each demand makes the problem NP-hard, I'm pretty sure (reduces to knapsack). But also, multiple NotesRequests for multiple proposal votes is precisely what you want: because the design of the NotesRequest is to return non-overlapping sets of note records, it wouldn't actually tell you, for each proposal, which notes you can use; you'd have to do that logic again, in the client. Instead, you should (as presently) make a separate request for each proposal you want to vote on.

I'm not sure I understand why we need this, rather than the (much simpler) request we already have, which allows filtering at account-level granularity.  What's the concrete use case here?

Implementing this API will be a lot of work, and it's not clear what benefit it gives over the existing API, or who the intended consumer is.  I don't think that this will be a good use of resources prior to mainnet, rather than working out the more basic problems we already have with the Plan/View system.  Since none of this is consensus-critical, we can always improve it after we ship and have actual users running into problems with the system we built initially.


minor typo: columne => column

Please make all pull requests on the dev branch.
Don't commit build files
Try to get all tests to pass.

thank you!


phpcbf returns exit code 0 when errors that can't be automatically fixed are found

While configuring CI with GitHub Actions, we observed that duster fix --using="phpcs" always returns an exit code 0 even in case of failures, causing checks to pass incorrectly.
The root of this behavior lies in the fix method where phpcbf's return code is used, which also appears to be always 0. This creates confusion... for instance, checks pass when env() helpers are used in place of config().
We propose introducing a configuration option to govern the exit code or, alternatively, adjusting the default behavior to align with the linting response when used as a GitHub Action. This enhancement would provide a more intuitive and accurate CI behavior. Thoughts appreciated!

I didn't know the best way to implement this. PHPCS uses separate tools for fixing/linting. When you run fix not all the rules are tried because it allows rules that cannot be fixed automatically.  My thinking was that if you run fix you want it to only fix and report success/failure on if it was able to fix.
I might agree with you here though.  It might be better to run fix and lint and fail if either of them fail.  Rules that cannot be fixed automatically or you do not want to fix can be added to the config to be excluded.
Is this what you were thinking?
Thanks for reporting, I'll think about it for a bit.

I might agree with you here though. It might be better to run fix and lint and fail if either of them fail. Rules that cannot be fixed automatically or you do not want to fix can be added to the config to be excluded.
Is this what you were thinking?

That's exactly what we were thinking!
I know PHP-CS-Fixer has had a long debate on GitHub about what constitutes a 0 exit code in regard to fixing. Perhaps the debate around this means it would be better as an option, but I also know that too many options aren't a good thing.
It does seem to me that anyone using Duster for its intended purpose would likely want to know when the fix command returned unfixable errors, though. Particularly when it comes to major issues like the one above.


Vim mode: #number Arrow not working whereas #number j/k/l/i is

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
in vim mode enabled, type 10 +down arrow and it will ignore the 10.
Environment

If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

@haikyuu Thanks for the report! This should be fixed in recent versions of Zed, but please let me know if not.


Accessing nth element of array

The feature is present in other language implementations of mustache like JS, but it does not seem in this one.
Ideally, we can get something like
>>> chevron.render('Hello, {{ mustache.0 }}!', {'mustache': ['World']})
'Hello, World!'

Dan managed to implement this  before I even saw it :stuck_out_tongue:
This seems useful, kinda weird it's not part of the spec. It's already on master, I'll push a new PyPi version this weekend.

Any chance @noahmorrison  this could get pushed to a release? pypi version doesn't have this feature and it would be handy!


Allow users to use their own content and style images

A number of ways to make this happen. I could, at this point, already consider putting everything into a gradio interface. Or I could keep it at the command line level with a path to the style and content images.

Let's do the command line way first, and break that down into a number of steps.
First, I need to find the correct way to send images over to the remote. That should work in reverse to the way we're grabbing it, i.e., via byte streams (rather than more complicated objects that we then have to worry about pickling/unpickling with just the right version...).
Now, if we're dealing with these bytestreams, the image processing functions on the remote need to be adjusted, and that just seems like the easiest thing to do first. I.e., a refactor to make the subsequent change easier.

Just switching to thumbnail instead of resize so we don't mess up aspect ratios is fine.
Note: We run out of memory quite quickly when we process "properly" sized images, like 4000x3000. So for full-size images we might want to downsample and then do superresolution stuff.


Point jsonrpsee to forked version to support error metrics by error code

Description
Corresponding change in the forked repo: https://github.com/wlmyng/jsonrpsee/pull/1
Test Plan
How did you test the new or updated feature?

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

You need to run hakari generate

Is this a temporary walkaround? Do we plan to upstream this change?

Is this a temporary walkaround? Do we plan to upstream this change?

Yes, and yes. I've opened an issue with the repo owners https://github.com/paritytech/jsonrpsee/issues/1129
It is complicated by the fact that we're two major versions behind, and I think this implementation is not as straightforward in the latest version.


adding ChanUpgradeCancel implementation

Description
Adding the implementation for ChanUpgradeCancel
closes: #1623

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

Codecov Report

Merging #3387 (3ce6c62) into cian/issue#1619-implement-channelupgradetry-functionality-for-04-channel (7f7c399) will decrease coverage by 0.34%.
The diff coverage is 0.00%.

Additional details and impacted files

@@                                             Coverage Diff                                              @@
##           cian/issue#1619-implement-channelupgradetry-functionality-for-04-channel    #3387      +/-   ##
============================================================================================================
- Coverage                                                                     78.02%   77.69%   -0.34%
============================================================================================================
  Files                                                                           186      186
  Lines                                                                         13326    13383      +57
============================================================================================================
  Hits                                                                          10398    10398
- Misses                                                                         2481     2538      +57
  Partials                                                                        447      447

Impacted Files
Coverage Δ

modules/core/04-channel/keeper/upgrade.go
69.43% <0.00%> (-13.39%)
:arrow_down:

modules/core/keeper/msg_server.go
43.36% <0.00%> (-1.46%)
:arrow_down:

This just needs some additional test cases for crossing hellos and to add events. I can pick this up when I am back.


Desired properties changes not persist

Content: Deploy code in IoT Edge
Steps followed:

Created filter module using Set Module
Updated the desired properties to
{
"properties.desired":{
"TemperatureThreshold":25
}
}
Click Save
Click Next
Click Submit
Received message module saved successfully
When I reopen the module, the desired properties changes were not saved.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 181d5562-f8d7-9c59-85ea-09efbe397f3e
Version Independent ID: dbedd952-a050-286e-c951-4529ec8e87b8
Content: Azure IoT Edge C# module
Content Source: articles/iot-edge/tutorial-csharp-module.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@smharishbabu Thanks for your feedback! We will investigate and update as appropriate.

Hello @smharishbabu , thank you for your feedback. That is a normal behavior. For desired properties to persist on any new deployment, you will need to leverage Deployments.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Packages upgraded. .net 4.6.1

FluentAssertions, Ninject and .Net Framework updated

Hi @pjlorenzo thanks for your contribution.
Apart from the Fluent Assertions changes from the likes of act.ShouldNotThrow() to act.Should().NotThrow() are there any other breaking changes in consuming libs that are driving this update?
I usually like to keep the nuget dependencies as low as possible to avoid forcing consumers to have to upgrade and to maximise.  Bearing that in mind, a couple of questions:

Is net461 the lowest TFM we can target?  I'd like to be as low as possible to maximise compatablity for consumers.
Is there anything driving the Ninject update which prevents a binding redirect for consumers?
Likewise, can we downgrade Fluent Assertions to 5.0.0?

Closing as it's been superseded by #10.


FileSystemProvider: watch() returned Disposable is never called

Version: 1.32.0-insider
Commit: 804373ac4d5c84e96c8086cee5b9be132df88837
Date: 2019-03-01T18:18:10.354Z
Electron: 3.1.3
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Darwin x64 18.2.0
Steps to Reproduce:

Create a custom FileSystemProvider.
Open an editor against a file from the custom provider, the file should be outside the workspace, in case that matters.
Note watch is called as expected for the single file, with options={"recursive":false,"excludes":[], return a Disposable to track cleanup.
Close the editor tab.
Note the Disposable.dispose callback is not called at this point. 🤔
Open the file again.
Note watch is called again with same args.  Now we have two watchers, dispose is never called on either of them.

Would have either expected the initial watch to be disposed when the editor tab was closed, or at least the second watch not to be sent.
Thanks!

Verified watch dispose is now called when an editor becomes non-current, or closes.  Thanks!
Do you have suggestions on what to use as a proxy indicator for versions < 1.33 ?
Version: 1.33.0-insider
Commit: 9b849d9de7168eb4f685823bf9b9e27a0a8dae74
Date: 2019-03-08T06:57:39.083Z
Electron: 3.1.3
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Darwin x64 18.2.0

Do you have suggestions on what to use as a proxy indicator for versions < 1.33 ?

No sure what you means? Would the vscode.env.version work or do you want to prevent your extension from running with older versions of vscode?

The dispose call is a great indicator for cleaning up additional resources / polling started for the associated watch, but it's not reliable in 1.32.  I can at least de-duplicate watch calls when the same spec comes in, but It would be nice to have a similar cleanup signal somewhere in the api that works in current stable and earlier.
I suppose keeping track of activeTextEditor might be a good approximation, at least for watches initiated by editor focus.  Under what other scenarios is watch called on a custom fs provider?

Yeah, active editor could work but it's hard without the correct dispose call...


Add conjunction analysis example using nilearn

Summary

A question in today's OHBM NiMARE tutorial came up about conjunction analyses in NiMARE. These analyses should be possible with nilearn.image.threshold_img and nilearn.image.math_img, but it would be useful for NiMARE users if we had an example of how to do that in our documentation.
Additional details

Next steps

We performed conjunction analyses like this for our recent CBMA, trying to mirror the behavior of GingerALE (which also computes a conjunction image as the minimum ALE values [across groups] for all voxels that were significant in both individual group maps).
I'd be happy to try and contribute an example for the documentation but I feel like it would make sense to combine this with an example for a subtraction analysis (which, as far as I can see, isn't covered either at the moment). Of course, this would require either (a) a sensible second example data set that is complementary to the pain studies or (b) two completely new data sets that make for a meaningful subtraction/conjunction example. We could contribute our "semantic cognition in children" data (the Sleuth files are shared here anyways). Or would you prefer this to be based on an IBMA (in which case we could create new complementary data sets from Neurosynth)?

That code snippet looks great, and it would be awesome if you could contribute an example!

I'd be happy to try and contribute an example for the documentation but I feel like it would make sense to combine this with an example for a subtraction analysis (which, as far as I can see, isn't covered either at the moment).

I agree, a new example with both conjunction and subtraction analyses would be perfect.

Of course, this would require either (a) a sensible second example data set that is complementary to the pain studies or (b) two completely new data sets that make for a meaningful subtraction/conjunction example. We could contribute our "semantic cognition in children" data (the Sleuth files are shared here anyways). Or would you prefer this to be based on an IBMA (in which case we could create new complementary data sets from Neurosynth)?

I like the idea of using your semantic cognition in children samples, if you're willing to store copies in NiMARE's example data. Plus, you can reference your preprint in the example!

We're glad to have the relevant data shipped with NiMARE. I'll try to prepare a subtraction/conjunction example and will open a PR once it's ready.


eosio-blocklog trim-blocklog enhancement

Change Description

This PR enhances "eosio-blocklog trim-blocklog --last". Before trimming, sanity check is performed. If block file is corrupt, last good block is searched and everything after the good block is discarded. Then block file and index file are checked if they agree with each other. If index file has more entries, extra entries are discarded; if index file has less entries, missing entries are generated from the block file and added to the index file. Finally trimming is performed.
Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

Lin created a different PR for this.


woodcutter: Infinite saplings in creative mode

If I start a single player game and give a woodcutter a sapling, it will continue to plant saplings forever.
Expected behavior
Creative mode is really handy for testing working_villagers. I expected the villager to have one less sapling after planting one.
Screenshots

Log
Nothing useful in the log
Desktop
Minetest 5.6.1 (Linux)
As a side note, it is oddly biased to -X.
Fixed by #35

This happens only when the "global" creative mode is active. If creative mode is enabled per player (/grantme creative), it looks fine.

Merged. Should be part of release v1.5.3.

Maybe we could add a setting for people who intend to have villagers take part in creative mode.


[vscode] Configure vscode-apollo

This is the proper setup

Fails

:no_entry_sign:
No CHANGELOG added.

  Generated by :no_entry_sign: dangerJS


Add one more scam site - LOTS OF COMMENTS

LINK (DO NOT GO HERE)
mores.baby

2 comments with this link inculded, there are like 15 by different bots.


Add Heroku metadata to every page

Makes debugging things on Heroku a little easier

Coverage decreased (-5.7%) to 71.014% when pulling c5b1476571ba3792ed177c72c673ef6c0898c651 on heroku-metadata into 77bf0822c36c0b0fd88e7c06cbd04c77baf3437c on master.

Coverage increased (+3.04%) to 79.71% when pulling 4191da3f6845450677b3cc585b5a4159cb20c8ca on heroku-metadata into 77bf0822c36c0b0fd88e7c06cbd04c77baf3437c on master.


Add random pride flag printer

resolves #11
You can test it by adding pride.PrintRandomPrideFlag() to main.js
I attempted to use crypto/rand to avoid manually seeding, but a lot of extra code had to be added to coerce ints to int64s to big.Ints, so I just stuck with math/rand. Lmk if that will be a problem!

Looks good to me! Thank you for contributing 🙂