SerialOSC crashes in Mark Eates Sequencer
barksten opened this issue · comments
I'm not sure if it's the app or lib thats the problem. This is a cross post from
lines forum
The crash reports:
Process: serialosc-device [28116]
Path: /Library/Application Support/Monome/serialosc.bundle/Contents/MacOS/serialosc-device
Identifier: serialosc-device
Version: ???
Code Type: X86-64 (Native)
Parent Process: serialoscd [26191]
Responsible: serialosc-device [28116]
User ID: 501
Date/Time: 2016-04-21 21:30:54.686 +0200
OS Version: Mac OS X 10.11.4 (15E65)
Report Version: 11
Anonymous UUID: B4EB77D2-35ED-B898-9214-BE1B40005A37
Sleep/Wake UUID: ED44798F-6F05-4EE2-BFCB-9DEE60607BC0
Time Awake Since Boot: 860000 seconds
Time Since Wake: 3500 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000006fc5fa2e8
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0x6fc5fa2e8:
Process Corpse Info 0000000101b00000-0000000101d00000 [ 2048K] rw-/rwx SM=COW
-->
STACK GUARD 00007fff5bc00000-00007fff5f400000 [ 56.0M] ---/rwx SM=NUL stack guard for thread 0
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libmonome.dylib 0x000000010002f793 monome_event_handle_next + 83
1 serialosc-device 0x0000000100000e14 sosc_event_loop + 772
2 serialosc-device 0x0000000100004257 sosc_server_run + 983
3 serialosc-device 0x0000000100004f8a main + 234
4 serialosc-device 0x0000000100000924 start + 52
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x000000005fbff9f0 rbx: 0x0000000000000000 rcx: 0x00000006fc5fa2e8 rdx: 0x00000006fc5fa2e8
rdi: 0x0000000000000004 rsi: 0x00007fff5fbff810 rbp: 0x00007fff5fbff9f0 rsp: 0x00007fff5fbff9b0
r8: 0x00007fff5fbff890 r9: 0x0000000000000080 r10: 0x00007fff5fbff790 r11: 0x0000000000000282
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x000000010002f793 rfl: 0x0000000000010206 cr2: 0x00000006fc5fa2e8
Logical CPU: 2
Error Code: 0x00000004
Trap Number: 14
Binary Images:
0x100000000 - 0x100012fff +serialosc-device (???) <DA546AE9-F786-3AEF-843E-E58419015C4C> /Library/Application Support/Monome/serialosc.bundle/Contents/MacOS/serialosc-device
0x100018000 - 0x100028fff +liblo.7.dylib (10) <3C0E103E-EEBC-3A6E-9874-9240CFDA16DC> /Library/Application Support/Monome/serialosc.bundle/Contents/Frameworks/liblo.7.dylib
0x10002d000 - 0x100030ff7 +libmonome.dylib (1) <4FACC6CC-0C41-3500-A846-AE7E2BCFCCF6> /Library/Application Support/Monome/serialosc.bundle/Contents/Frameworks/libmonome.dylib
0x100066000 - 0x100067ff7 +protocol_series.dylib (1) <56A8B7B6-E396-3A3E-8146-4A9BBC3007E0> /Library/Application Support/Monome/serialosc.bundle/Contents/Frameworks/monome/protocol_series.dylib
0x7fff6dad7000 - 0x7fff6db0e0d7 dyld (360.21) <D9B236BC-4AC1-325F-B3EF-3F06DBDA7119> /usr/lib/dyld
0x7fff869ea000 - 0x7fff869ebfff libsystem_secinit.dylib (20) <32B1A8C6-DC84-3F4F-B8CE-9A52B47C3E6B> /usr/lib/system/libsystem_secinit.dylib
0x7fff875bc000 - 0x7fff875bdfff libDiagnosticMessagesClient.dylib (100) <4243B6B4-21E9-355B-9C5A-95A216233B96> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff87cba000 - 0x7fff87cbefff libcache.dylib (75) <9548AAE9-2AB7-3525-9ECE-A2A7C4688447> /usr/lib/system/libcache.dylib
0x7fff897d9000 - 0x7fff897e1fff libcopyfile.dylib (127) <A48637BC-F3F2-34F2-BB68-4C65FD012832> /usr/lib/system/libcopyfile.dylib
0x7fff8c2d0000 - 0x7fff8c2f9ff7 libxpc.dylib (765.40.36) <2CC7CF36-66D4-301B-A6D8-EBAE7405B008> /usr/lib/system/libxpc.dylib
0x7fff8cb28000 - 0x7fff8cb2aff7 libsystem_configuration.dylib (802.40.13) <3DEB7DF9-6804-37E1-BC83-0166882FF0FF> /usr/lib/system/libsystem_configuration.dylib
0x7fff8cb2b000 - 0x7fff8cb49ff7 libsystem_kernel.dylib (3248.40.184) <88C17B7F-1CD8-3979-A1A9-F7BDB4FCE789> /usr/lib/system/libsystem_kernel.dylib
0x7fff8cd7d000 - 0x7fff8cd82ff7 libmacho.dylib (875.1) <318264FA-58F1-39D8-8285-1F6254EE410E> /usr/lib/system/libmacho.dylib
0x7fff8d4e3000 - 0x7fff8d536ff7 libc++.1.dylib (120.1) <8FC3D139-8055-3498-9AC5-6467CB7F4D14> /usr/lib/libc++.1.dylib
0x7fff8d845000 - 0x7fff8d84eff7 libsystem_pthread.dylib (138.10.4) <3DD1EF4C-1D1B-3ABF-8CC6-B3B1CEEE9559> /usr/lib/system/libsystem_pthread.dylib
0x7fff8f0b4000 - 0x7fff8f0bcfff libsystem_networkextension.dylib (385.40.36) <66095DC7-6539-38F2-95EE-458F15F6D014> /usr/lib/system/libsystem_networkextension.dylib
0x7fff8f767000 - 0x7fff8f769fff libsystem_coreservices.dylib (19.2) <1B3F5AFC-FFCD-3ECB-8B9A-5538366FB20D> /usr/lib/system/libsystem_coreservices.dylib
0x7fff8fdad000 - 0x7fff8fdb0ffb libdyld.dylib (360.21) <8390E026-F7DE-3C32-9486-3DFF6BD131B0> /usr/lib/system/libdyld.dylib
0x7fff90faa000 - 0x7fff90fc6ff7 libsystem_malloc.dylib (67.40.1) <5748E8B2-F81C-34C6-8B13-456213127678> /usr/lib/system/libsystem_malloc.dylib
0x7fff91a66000 - 0x7fff91a6fff3 libsystem_notify.dylib (150.40.1) <D48BDE34-0F7E-34CA-A0FF-C578E39987CC> /usr/lib/system/libsystem_notify.dylib
0x7fff922fb000 - 0x7fff92312ff7 libsystem_asl.dylib (323.40.3) <007F9094-317A-33EA-AF62-BAEAAB48C0F7> /usr/lib/system/libsystem_asl.dylib
0x7fff931d6000 - 0x7fff931d7fff libsystem_blocks.dylib (65) <1244D9D5-F6AA-35BB-B307-86851C24B8E5> /usr/lib/system/libsystem_blocks.dylib
0x7fff931d8000 - 0x7fff9321eff7 libauto.dylib (186) <999E610F-41FC-32A3-ADCA-5EC049B65DFB> /usr/lib/libauto.dylib
0x7fff932d3000 - 0x7fff932d4ffb libremovefile.dylib (41) <552EF39E-14D7-363E-9059-4565AC2F894E> /usr/lib/system/libremovefile.dylib
0x7fff932d5000 - 0x7fff932d5ff7 libunc.dylib (29) <DDB1E947-C775-33B8-B461-63E5EB698F0E> /usr/lib/system/libunc.dylib
0x7fff933c9000 - 0x7fff933f2fff libc++abi.dylib (125) <DCCC8177-3D09-35BC-9784-2A04FEC4C71B> /usr/lib/libc++abi.dylib
0x7fff9361e000 - 0x7fff9361fffb libSystem.B.dylib (1226.10.1) <CD307E99-FC5C-3575-BCCE-0C861AA63124> /usr/lib/libSystem.B.dylib
0x7fff93652000 - 0x7fff936dffff libsystem_c.dylib (1082.20.4) <CDEBF2BB-A578-30F5-846F-96274951C3C5> /usr/lib/system/libsystem_c.dylib
0x7fff93d14000 - 0x7fff93d1cffb libsystem_dnssd.dylib (625.40.20) <86A05653-DCA0-3345-B29F-F320029AA05E> /usr/lib/system/libsystem_dnssd.dylib
0x7fff93f22000 - 0x7fff93f2dff7 libcommonCrypto.dylib (60075.40.2) <B9D08EB8-FB35-3F7B-8A1C-6FCE3F07B7E7> /usr/lib/system/libcommonCrypto.dylib
0x7fff95afb000 - 0x7fff95b24fff libsystem_info.dylib (477.40.5) <6B01C09E-A3E5-3C71-B370-D0CABD11A436> /usr/lib/system/libsystem_info.dylib
0x7fff95b2e000 - 0x7fff95b2eff7 libkeymgr.dylib (28) <8371CE54-5FDD-3CE9-B3DF-E98C761B6FE0> /usr/lib/system/libkeymgr.dylib
0x7fff96074000 - 0x7fff9608bff7 libsystem_coretls.dylib (83.40.5) <C90DAE38-4082-381C-A185-2A6A8B677628> /usr/lib/system/libsystem_coretls.dylib
0x7fff9608c000 - 0x7fff960f2ff7 libsystem_network.dylib (583.40.20) <269E5ADD-6922-31E2-8D55-7B777263AC0D> /usr/lib/system/libsystem_network.dylib
0x7fff96a53000 - 0x7fff96dbe657 libobjc.A.dylib (680) <D55D5807-1FBE-32A5-9105-44D7AFE68C27> /usr/lib/libobjc.A.dylib
0x7fff97198000 - 0x7fff9720ffeb libcorecrypto.dylib (335.40.8) <9D300121-CAF8-3894-8774-DF38FA65F238> /usr/lib/system/libcorecrypto.dylib
0x7fff9722e000 - 0x7fff97230ff7 libquarantine.dylib (80) <0F4169F0-0C84-3A25-B3AE-E47B3586D908> /usr/lib/system/libquarantine.dylib
0x7fff979a1000 - 0x7fff979a6ff3 libunwind.dylib (35.3) <F6EB48E5-4D12-359A-AB54-C937FBBE9043> /usr/lib/system/libunwind.dylib
0x7fff97c9d000 - 0x7fff97ca5fef libsystem_platform.dylib (74.40.2) <29A905EF-6777-3C33-82B0-6C3A88C4BA15> /usr/lib/system/libsystem_platform.dylib
0x7fff97cfb000 - 0x7fff97d28fff libdispatch.dylib (501.40.12) <C7499857-61A5-3D7D-A5EA-65DCC8C3DF92> /usr/lib/system/libdispatch.dylib
0x7fff98659000 - 0x7fff98659ff7 liblaunch.dylib (765.40.36) <1CD7619D-AF2E-34D1-8EC6-8021CF473D9B> /usr/lib/system/liblaunch.dylib
0x7fff98c6e000 - 0x7fff98c7fff7 libsystem_trace.dylib (201.10.3) <25104542-5251-3E8D-B14A-9E37207218BC> /usr/lib/system/libsystem_trace.dylib
0x7fff997af000 - 0x7fff997b2fff libsystem_sandbox.dylib (460.40.33) <30671DCC-265F-325A-B33D-11CD336B3DA3> /usr/lib/system/libsystem_sandbox.dylib
0x7fff9c33a000 - 0x7fff9c369ffb libsystem_m.dylib (3105) <08E1A4B2-6448-3DFE-A58C-ACC7335BE7E4> /usr/lib/system/libsystem_m.dylib
0x7fff9c621000 - 0x7fff9c628ff7 libcompiler_rt.dylib (62) <A13ECF69-F59F-38AE-8609-7B731450FBCD> /usr/lib/system/libcompiler_rt.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
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: 408013
thread_create: 0
thread_set_state: 725
VM Region Summary:
ReadOnly portion of Libraries: Total=99.2M resident=0K(0%) swapped_out_or_unallocated=99.2M(100%)
Writable regions: Total=36.4M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=36.4M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Activity Tracing 2048K 2
Kernel Alloc Once 4K 2
MALLOC 24.2M 10
MALLOC guard page 16K 4
Process Corpse Info 2048K 2
STACK GUARD 56.0M 2
Stack 8192K 2
VM_ALLOCATE 4K 2
__DATA 1460K 45
__LINKEDIT 91.5M 7
__TEXT 7852K 46
shared memory 12K 4
=========== ======= =======
TOTAL 192.8M 116
whoa, that's nasty.
which monome (size and generation) do you have, and could you describe what causes this crash, in the event it's reproducible?
it seems like we're crashing while reading from the device, which could be tricky indeed.
It's a GS 64. serial nr 1035. It happens randomly. Right now when I connected it to read the serial it locked on the mark eats sequencer "OK" "screen".
monomer sum or smallbatch have never locked the device. Not when I have been playing around with Processing either. It's just when I use Mark Eats Sequencer.
Same problem for me!!
please provide some details about your OS, grid edition, etc
Hi! Still Cant get it to work, also a little slow in my head after a meningits…
Really do need help to work around this, but Dont really understand coding etc these days.
Is it possible?
Monome64 with Mark Eats Sequencer/Ableton Live, MacBook Pro 2010, OSX 10.13.6
If so, is there a way to get around the problem in Mark Eats Sequencer that makes the Monome64 freeze?
I know the problem is in Mark Eats Sequencer, tried all installations with control 1.1 etc, all the right settings in live etc etc.
The Monome64 work perfectly with all other apps.
when does the crash happen? did this work at any point in the past? how recently did you install serialosc?
Hi Brian!
Thanks for your reply.
Monome64 with Mark Eats Sequencer/Ableton Live, MacBook Pro 2010, OSX
10.13.6
If so, is there a way to get around the problem in Mark Eats Sequencer that
makes the Monome64 freeze?
I know the problem is in Mark Eats Sequencer, tried all installations with
control 1.1 etc, all the right settings in live etc etc.
The Monome64 work perfectly with all other apps.
Dont really wanna give up the sequencer since it fits my needs perfect.
Also, im a little bit slower in my head due to a meningitis a few years
back.
lör 20 nov. 2021 kl. 19:19 skrev brian crabtree ***@***.***>:
… when does the crash happen? did this work at any point in the past? how
recently did you install serialosc?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATDYZLSN3CSVAOMOZR5X34TUM7RCLANCNFSM4CBUBOJQ>
.
Does it freeze immediately on startup similar to the other report? Have you
ever had this working?
…On Sun, Nov 21, 2021 at 5:24 AM JohanElmros ***@***.***> wrote:
Hi Brian!
Thanks for your reply.
Monome64 with Mark Eats Sequencer/Ableton Live, MacBook Pro 2010, OSX
10.13.6
If so, is there a way to get around the problem in Mark Eats Sequencer that
makes the Monome64 freeze?
I know the problem is in Mark Eats Sequencer, tried all installations with
control 1.1 etc, all the right settings in live etc etc.
The Monome64 work perfectly with all other apps.
Dont really wanna give up the sequencer since it fits my needs perfect.
Also, im a little bit slower in my head due to a meningitis a few years
back.
lör 20 nov. 2021 kl. 19:19 skrev brian crabtree ***@***.***>:
> when does the crash happen? did this work at any point in the past? how
> recently did you install serialosc?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#21 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ATDYZLSN3CSVAOMOZR5X34TUM7RCLANCNFSM4CBUBOJQ
>
> .
>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB4I4AZQH5OHUJEFNXMFPTUNDCEFANCNFSM4CBUBOJQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
Thanks for your reply.
It works for a bit, sometimes a few min, then freezes up.
Sometimes if you tilt or tap the buttons like crazy the Monome64 sometimes
starts to run again.
Tried different tilt settings in sequencer, but still the same problem.
sön 21 nov. 2021 kl. 17:12 skrev brian crabtree ***@***.***>:
… Does it freeze immediately on startup similar to the other report? Have you
ever had this working?
On Sun, Nov 21, 2021 at 5:24 AM JohanElmros ***@***.***>
wrote:
> Hi Brian!
> Thanks for your reply.
> Monome64 with Mark Eats Sequencer/Ableton Live, MacBook Pro 2010, OSX
> 10.13.6
> If so, is there a way to get around the problem in Mark Eats Sequencer
that
> makes the Monome64 freeze?
> I know the problem is in Mark Eats Sequencer, tried all installations
with
> control 1.1 etc, all the right settings in live etc etc.
> The Monome64 work perfectly with all other apps.
> Dont really wanna give up the sequencer since it fits my needs perfect.
> Also, im a little bit slower in my head due to a meningitis a few years
> back.
>
>
> lör 20 nov. 2021 kl. 19:19 skrev brian crabtree ***@***.***>:
>
> > when does the crash happen? did this work at any point in the past? how
> > recently did you install serialosc?
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <#21 (comment)
>,
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/ATDYZLSN3CSVAOMOZR5X34TUM7RCLANCNFSM4CBUBOJQ
> >
> > .
> >
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#21 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAB4I4AZQH5OHUJEFNXMFPTUNDCEFANCNFSM4CBUBOJQ
>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
>
> or Android
> <
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
>.
>
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATDYZLVICDNEFLHQNRICPJTUNEK7LANCNFSM4CBUBOJQ>
.
Do you understand What i mean?
:)
sön 21 nov. 2021 kl. 19:26 skrev Johan Afterglow ***@***.***>:
… Thanks for your reply.
It works for a bit, sometimes a few min, then freezes up.
Sometimes if you tilt or tap the buttons like crazy the Monome64 sometimes
starts to run again.
Tried different tilt settings in sequencer, but still the same problem.
sön 21 nov. 2021 kl. 17:12 skrev brian crabtree ***@***.***
>:
> Does it freeze immediately on startup similar to the other report? Have
> you
> ever had this working?
>
> On Sun, Nov 21, 2021 at 5:24 AM JohanElmros ***@***.***>
> wrote:
>
> > Hi Brian!
> > Thanks for your reply.
> > Monome64 with Mark Eats Sequencer/Ableton Live, MacBook Pro 2010, OSX
> > 10.13.6
> > If so, is there a way to get around the problem in Mark Eats Sequencer
> that
> > makes the Monome64 freeze?
> > I know the problem is in Mark Eats Sequencer, tried all installations
> with
> > control 1.1 etc, all the right settings in live etc etc.
> > The Monome64 work perfectly with all other apps.
> > Dont really wanna give up the sequencer since it fits my needs perfect.
> > Also, im a little bit slower in my head due to a meningitis a few years
> > back.
> >
> >
> > lör 20 nov. 2021 kl. 19:19 skrev brian crabtree ***@***.***>:
> >
> > > when does the crash happen? did this work at any point in the past?
> how
> > > recently did you install serialosc?
> > >
> > > —
> > > You are receiving this because you commented.
> > > Reply to this email directly, view it on GitHub
> > > <#21 (comment)
> >,
> > > or unsubscribe
> > > <
> >
> https://github.com/notifications/unsubscribe-auth/ATDYZLSN3CSVAOMOZR5X34TUM7RCLANCNFSM4CBUBOJQ
> > >
> > > .
> > >
> >
> > —
> > You are receiving this because you modified the open/close state.
> > Reply to this email directly, view it on GitHub
> > <#21 (comment)>,
> > or unsubscribe
> > <
> https://github.com/notifications/unsubscribe-auth/AAB4I4AZQH5OHUJEFNXMFPTUNDCEFANCNFSM4CBUBOJQ
> >
> > .
> > Triage notifications on the go with GitHub Mobile for iOS
> > <
> https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
> >
> > or Android
> > <
> https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
> >.
> >
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#21 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ATDYZLVICDNEFLHQNRICPJTUNEK7LANCNFSM4CBUBOJQ>
> .
>
apologies for the delay. can you confirm which version of serialosc you're
using? which installer you used.
On Sun, Nov 21, 2021 at 1:26 PM JohanElmros ***@***.***>
wrote:
… Thanks for your reply.
It works for a bit, sometimes a few min, then freezes up.
Sometimes if you tilt or tap the buttons like crazy the Monome64 sometimes
starts to run again.
Tried different tilt settings in sequencer, but still the same problem.
sön 21 nov. 2021 kl. 17:12 skrev brian crabtree ***@***.***>:
> Does it freeze immediately on startup similar to the other report? Have
you
> ever had this working?
>
> On Sun, Nov 21, 2021 at 5:24 AM JohanElmros ***@***.***>
> wrote:
>
> > Hi Brian!
> > Thanks for your reply.
> > Monome64 with Mark Eats Sequencer/Ableton Live, MacBook Pro 2010, OSX
> > 10.13.6
> > If so, is there a way to get around the problem in Mark Eats Sequencer
> that
> > makes the Monome64 freeze?
> > I know the problem is in Mark Eats Sequencer, tried all installations
> with
> > control 1.1 etc, all the right settings in live etc etc.
> > The Monome64 work perfectly with all other apps.
> > Dont really wanna give up the sequencer since it fits my needs perfect.
> > Also, im a little bit slower in my head due to a meningitis a few years
> > back.
> >
> >
> > lör 20 nov. 2021 kl. 19:19 skrev brian crabtree ***@***.***>:
> >
> > > when does the crash happen? did this work at any point in the past?
how
> > > recently did you install serialosc?
> > >
> > > —
> > > You are receiving this because you commented.
> > > Reply to this email directly, view it on GitHub
> > > <
#21 (comment)
> >,
> > > or unsubscribe
> > > <
> >
>
https://github.com/notifications/unsubscribe-auth/ATDYZLSN3CSVAOMOZR5X34TUM7RCLANCNFSM4CBUBOJQ
> > >
> > > .
> > >
> >
> > —
> > You are receiving this because you modified the open/close state.
> > Reply to this email directly, view it on GitHub
> > <#21 (comment)
>,
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AAB4I4AZQH5OHUJEFNXMFPTUNDCEFANCNFSM4CBUBOJQ
> >
> > .
> > Triage notifications on the go with GitHub Mobile for iOS
> > <
>
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
> >
> > or Android
> > <
>
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
> >.
> >
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#21 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ATDYZLVICDNEFLHQNRICPJTUNEK7LANCNFSM4CBUBOJQ
>
> .
>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB4I4FKAVT7Y5G2F6A7KA3UNE2WXANCNFSM4CBUBOJQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.