SIGABRT _status < MTLCommandBufferStatusCommitted > -[IOGPUMetalCommandBuffer setCurrentCommandEncoder:] > device

Steps to Reproduce

Flutter 2.8.1
Xcode 13.1
Cannot reproduce, but has happen over 1000 times in production to 1000 different users.
Only on iOS 15 variants, seems to happen directly after app transitions into foreground from background.
App uses a camera plugin

Actual results: App crashs with unexpected error
SIGABRT: _status < MTLCommandBufferStatusCommitted > -[IOGPUMetalCommandBuffer setCurrentCommandEncoder:] > device

crash log
OS Version: iOS 15.1 (19B74)
Report Version: 104

Exception Type: EXC_CRASH (SIGABRT)
Crashed Thread: 0

Application Specific Information:
_status < MTLCommandBufferStatusCommitted > -[IOGPUMetalCommandBuffer setCurrentCommandEncoder:] > setStoreAction:

Thread 0 Crashed:
0   libsystem_kernel.dylib          0x36f359964         __pthread_kill
1   libsystem_pthread.dylib         0x3e1c19374         pthread_kill
2   libsystem_c.dylib               0x31732df4c         abort
3   Metal                           0x335d7e38c         MTLReleaseAssertionFailure
4   IOGPU                           0x393f27ba4         -[IOGPUMetalCommandBuffer setCurrentCommandEncoder:]
5   Metal                           0x335cd46ac         -[_MTLCommandEncoder initWithCommandBuffer:]
6   IOGPU                           0x393f29820         -[IOGPUMetalCommandEncoder initWithCommandBuffer:]
7   AGXMetalA12                     0x3e43f64ac         <redacted>
8   AGXMetalA12                     0x3e4346d5c         <redacted>
9   Flutter                         0x10607f428         <redacted>
10  Flutter                         0x106086518         <redacted>
11  Flutter                         0x106083038         <redacted>
12  Flutter                         0x10601bdd8         <redacted>
13  Flutter                         0x105f837bc         <redacted>
14  Flutter                         0x105f83ba8         <redacted>
15  Flutter                         0x105e5167c         <redacted>
16  Flutter                         0x1062f5274         <redacted>
17  Flutter                         0x10627a558         <redacted>
18  Flutter                         0x105e35c38         <redacted>
19  Flutter                         0x1061b06d8         <redacted>
20  Flutter                         0x1061b0c20         <redacted>
21  Flutter                         0x1060e8868         <redacted>
22  Flutter                         0x1061b0318         <redacted>
23  Flutter                         0x1061b1c50         <redacted>
24  Flutter                         0x1061b0ed4         <redacted>
25  Flutter                         0x1061b9314         <redacted>
26  Flutter                         0x1060e70d8         <redacted>
27  Flutter                         0x1060ea6a4         <redacted>
28  CoreFoundation                  0x30164e264         __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
29  CoreFoundation                  0x3015d2c3c         __CFRunLoopDoTimer
30  CoreFoundation                  0x3015cd438         __CFRunLoopDoTimers
31  CoreFoundation                  0x3015abc54         __CFRunLoopRun
32  CoreFoundation                  0x3015bf3b4         CFRunLoopRunSpecific
33  GraphicsServices                0x3388fd388         GSEventRunModal
34  UIKitCore                       0x3064056a4         -[UIApplication _run]
35  UIKitCore                       0x3061847f0         UIApplicationMain
36  Pinnacle                        0x204a94d48         <redacted>
37  <unknown>                       0x104e51a24         <redacted>

Thread 0 Crashed:
0   libsystem_kernel.dylib          0x36f359964         __pthread_kill
1   libsystem_pthread.dylib         0x3e1c19374         pthread_kill
2   libsystem_c.dylib               0x31732df4c         abort
3   Metal                           0x335d7e38c         MTLReleaseAssertionFailure
4   IOGPU                           0x393f27ba4         -[IOGPUMetalCommandBuffer setCurrentCommandEncoder:]
5   Metal                           0x335cd46ac         -[_MTLCommandEncoder initWithCommandBuffer:]
6   IOGPU                           0x393f29820         -[IOGPUMetalCommandEncoder initWithCommandBuffer:]
7   AGXMetalA12                     0x3e43f64ac         <redacted>
8   AGXMetalA12                     0x3e4346d5c         <redacted>
9   Flutter                         0x10607f428         <redacted>
10  Flutter                         0x106086518         <redacted>
11  Flutter                         0x106083038         <redacted>
12  Flutter                         0x10601bdd8         <redacted>
13  Flutter                         0x105f837bc         <redacted>
14  Flutter                         0x105f83ba8         <redacted>
15  Flutter                         0x105e5167c         <redacted>
16  Flutter                         0x1062f5274         <redacted>
17  Flutter                         0x10627a558         <redacted>
18  Flutter                         0x105e35c38         <redacted>
19  Flutter                         0x1061b06d8         <redacted>
20  Flutter                         0x1061b0c20         <redacted>
21  Flutter                         0x1060e8868         <redacted>
22  Flutter                         0x1061b0318         <redacted>
23  Flutter                         0x1061b1c50         <redacted>
24  Flutter                         0x1061b0ed4         <redacted>
25  Flutter                         0x1061b9314         <redacted>
26  Flutter                         0x1060e70d8         <redacted>
27  Flutter                         0x1060ea6a4         <redacted>
28  CoreFoundation                  0x30164e264         __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
29  CoreFoundation                  0x3015d2c3c         __CFRunLoopDoTimer
30  CoreFoundation                  0x3015cd438         __CFRunLoopDoTimers
31  CoreFoundation                  0x3015abc54         __CFRunLoopRun
32  CoreFoundation                  0x3015bf3b4         CFRunLoopRunSpecific
33  GraphicsServices                0x3388fd388         GSEventRunModal
34  UIKitCore                       0x3064056a4         -[UIApplication _run]
35  UIKitCore                       0x3061847f0         UIApplicationMain
36  Pinnacle                        0x204a94d48         <redacted>
37  <unknown>                       0x104e51a24         <redacted>

Thread 1 name: com.apple.uikit.eventfetch-thread
0   libsystem_kernel.dylib          0x36f353504         mach_msg_trap
1   libsystem_kernel.dylib          0x36f353b98         mach_msg
2   CoreFoundation                  0x3015a7684         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x3015ab978         __CFRunLoopRun
4   CoreFoundation                  0x3015bf3b4         CFRunLoopRunSpecific
5   Foundation                      0x3045fc350         -[NSRunLoop(NSRunLoop) runMode:beforeDate:]
6   Foundation                      0x30463dc24         -[NSRunLoop(NSRunLoop) runUntilDate:]
7   UIKitCore                       0x30637e8a0         -[UIEventFetcher threadMain]
8   Foundation                      0x30464c368         __NSThread__start__
9   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 2 name: io.flutter.1.ui
0   App                             0x10d4c2830         Precompiled_TypeTestingStub_dart_async___StreamImplEvents__X0_716
1   App                             0x10d4c2558         Precompiled__BufferingStreamSubscription_4048458__addPending_4048458_711
2   App                             0x10d9fb98c         Precompiled__BroadcastStreamController_4048458_add_18607
3   App                             0x10d58175c         Precompiled_EventChannel_receiveBroadcastStream__anonymous_closure___async_op__anonymous_closure___async_op_3864
4   App                             0x10d581614         Precompiled_EventChannel_receiveBroadcastStream__anonymous_closure___async_op__anonymous_closure__3863
5   App                             0x10d5705d4         Precompiled__DefaultBinaryMessenger_639240726_setMessageHandler__anonymous_closure___async_op_3574
6   App                             0x10d57043c         Precompiled__DefaultBinaryMessenger_639240726_setMessageHandler__anonymous_closure__3573
7   App                             0x10d545f74         Precompiled_____invoke2_16065589__anonymous_closure__2799
8   App                             0x10d4a99b0         Precompiled_____rootRun_4048458_218
9   App                             0x10d4a9aac         Precompiled_____rootRun_4048458__rootRun_4048458_219
10  App                             0x10da30590         Precompiled__CustomZone_4048458_run_19468
11  App                             0x10da32030         Precompiled__CustomZone_4048458_runGuarded_19506
12  App                             0x10d545f10         Precompiled_____invoke2_16065589_2798
13  App                             0x10d545dcc         Precompiled__ChannelCallbackRecord_16065589_invoke_2797
14  App                             0x10d54660c         Precompiled__Channel_16065589_push_2817
15  App                             0x10d545a14         Precompiled_ChannelBuffers_push_2789
16  App                             0x10d545910         Precompiled_PlatformDispatcher__dispatchPlatformMessage_16065589_2788
17  App                             0x10d54bb90         Precompiled_____dispatchPlatformMessage_16065589_2942
18  App                             0x10d54bbdc         Precompiled_____dispatchPlatformMessage_16065589__dispatchPlatformMessage_16065589_2943
19  App                             0x10d49e204         Precompiled_Stub_InvokeDartCode
20  Flutter                         0x10632e270         <redacted>
21  Flutter                         0x10632ee08         <redacted>
22  Flutter                         0x10642ac10         <redacted>
23  Flutter                         0x1062a7d94         <redacted>
24  Flutter                         0x1062e7a20         <redacted>
25  Flutter                         0x1061bbd48         <redacted>
26  Flutter                         0x1060e70d8         <redacted>
27  Flutter                         0x1060ea6a4         <redacted>
28  CoreFoundation                  0x30164e264         __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
29  CoreFoundation                  0x3015d2c3c         __CFRunLoopDoTimer
30  CoreFoundation                  0x3015cd438         __CFRunLoopDoTimers
31  CoreFoundation                  0x3015abc54         __CFRunLoopRun
32  CoreFoundation                  0x3015bf3b4         CFRunLoopRunSpecific
33  Flutter                         0x1060ea570         <redacted>
34  Flutter                         0x1060e9d30         <redacted>
35  libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 3 name: io.flutter.1.raster
0   libsystem_kernel.dylib          0x36f353504         mach_msg_trap
1   libsystem_kernel.dylib          0x36f353b98         mach_msg
2   CoreFoundation                  0x3015a7684         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x3015ab978         __CFRunLoopRun
4   CoreFoundation                  0x3015bf3b4         CFRunLoopRunSpecific
5   Flutter                         0x1060ea570         <redacted>
6   Flutter                         0x1060e9d30         <redacted>
7   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 4 name: io.flutter.1.io
0   libsystem_kernel.dylib          0x36f353504         mach_msg_trap
1   libsystem_kernel.dylib          0x36f353b98         mach_msg
2   CoreFoundation                  0x3015a7684         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x3015ab978         __CFRunLoopRun
4   CoreFoundation                  0x3015bf3b4         CFRunLoopRunSpecific
5   Flutter                         0x1060ea570         <redacted>
6   Flutter                         0x1060e9d30         <redacted>
7   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 5 name: io.worker.1
0   libsystem_kernel.dylib          0x36f353f90         __psynch_cvwait
1   libsystem_pthread.dylib         0x3e1c1a250         _pthread_cond_wait
2   libc++.1.dylib                  0x3324e5dd8         std::__1::condition_variable::wait
3   Flutter                         0x1060e4928         <redacted>
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 6 name: io.worker.2
0   libsystem_kernel.dylib          0x36f353f90         __psynch_cvwait
1   libsystem_pthread.dylib         0x3e1c1a250         _pthread_cond_wait
2   libc++.1.dylib                  0x3324e5dd8         std::__1::condition_variable::wait
3   Flutter                         0x1060e4928         <redacted>
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 7 name: io.worker.3
0   libsystem_kernel.dylib          0x36f353f90         __psynch_cvwait
1   libsystem_pthread.dylib         0x3e1c1a250         _pthread_cond_wait
2   libc++.1.dylib                  0x3324e5dd8         std::__1::condition_variable::wait
3   Flutter                         0x1060e4928         <redacted>
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 8 name: io.worker.4
0   libsystem_kernel.dylib          0x36f353f90         __psynch_cvwait
1   libsystem_pthread.dylib         0x3e1c1a250         _pthread_cond_wait
2   libc++.1.dylib                  0x3324e5dd8         std::__1::condition_variable::wait
3   Flutter                         0x1060e4928         <redacted>
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 9 name: io.worker.5
0   libsystem_kernel.dylib          0x36f353f90         __psynch_cvwait
1   libsystem_pthread.dylib         0x3e1c1a250         _pthread_cond_wait
2   libc++.1.dylib                  0x3324e5dd8         std::__1::condition_variable::wait
3   Flutter                         0x1060e4928         <redacted>
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 10 name: io.worker.6
0   libsystem_kernel.dylib          0x36f353f90         __psynch_cvwait
1   libsystem_pthread.dylib         0x3e1c1a250         _pthread_cond_wait
2   libc++.1.dylib                  0x3324e5dd8         std::__1::condition_variable::wait
3   Flutter                         0x1060e4928         <redacted>
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 11 name: dart:io EventHandler
0   libsystem_kernel.dylib          0x36f354e7c         kevent
1   Flutter                         0x1062ad4dc         <redacted>
2   Flutter                         0x1062dc4e8         <redacted>
3   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 12
0   libsystem_kernel.dylib          0x36f353ae4         __semwait_signal
1   libsystem_c.dylib               0x317312efc         nanosleep
2   libsystem_c.dylib               0x317326f38         sleep
3   Sentry                          0x10536e18c         monitorCachedData
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 13 name: SentryCrash Exception Handler (Secondary)
0   libsystem_kernel.dylib          0x36f353504         mach_msg_trap
1   libsystem_kernel.dylib          0x36f353b98         mach_msg
2   libsystem_kernel.dylib          0x36f35f22c         thread_suspend
3   Sentry                          0x10537b030         handleExceptions
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 14 name: SentryCrash Exception Handler (Primary)
0   libsystem_kernel.dylib          0x36f353504         mach_msg_trap
1   libsystem_kernel.dylib          0x36f353b98         mach_msg
2   Sentry                          0x10537b05c         handleExceptions
3   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 15 name: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib          0x36f353504         mach_msg_trap
1   libsystem_kernel.dylib          0x36f353b98         mach_msg
2   CoreFoundation                  0x3015a7684         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x3015ab978         __CFRunLoopRun
4   CoreFoundation                  0x3015bf3b4         CFRunLoopRunSpecific
5   CFNetwork                       0x30284c69c         _CFURLStorageSessionCopyIdentifier
6   Foundation                      0x30464c368         __NSThread__start__
7   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 16 name: JavaScriptCore bmalloc scavenger
0   libsystem_kernel.dylib          0x36f353f90         __psynch_cvwait
1   libsystem_pthread.dylib         0x3e1c1a250         _pthread_cond_wait
2   libc++.1.dylib                  0x3324e5dd8         std::__1::condition_variable::wait
3   JavaScriptCore                  0x31866e1d0         std::__1::condition_variable_any::wait<T>
4   JavaScriptCore                  0x3186729a0         bmalloc::Scavenger::threadRunLoop
5   JavaScriptCore                  0x318672540         bmalloc::Scavenger::threadEntryPoint
6   JavaScriptCore                  0x3186739fc         std::__1::__thread_proxy<T>
7   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 17 name: com.apple.CoreMotion.MotionThread
0   libsystem_kernel.dylib          0x36f353504         mach_msg_trap
1   libsystem_kernel.dylib          0x36f353b98         mach_msg
2   CoreFoundation                  0x3015a7684         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x3015ab978         __CFRunLoopRun
4   CoreFoundation                  0x3015bf3b4         CFRunLoopRunSpecific
5   CoreFoundation                  0x30163fa74         CFRunLoopRun
6   CoreMotion                      0x31b58b540         CLMotionActivity::isTypeInVehicle
7   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 18
0   libsystem_kernel.dylib          0x36f353b2c         __workq_kernreturn
1   libsystem_pthread.dylib         0x3e1c1313c         _pthread_wqthread

Thread 19
0   libsystem_kernel.dylib          0x36f353b2c         __workq_kernreturn
1   libsystem_pthread.dylib         0x3e1c1313c         _pthread_wqthread

Thread 20
0   libsystem_pthread.dylib         0x3e1c12e8c         start_wqthread

Thread 21
0   libsystem_kernel.dylib          0x36f353b2c         __workq_kernreturn
1   libsystem_pthread.dylib         0x3e1c1313c         _pthread_wqthread

Thread 22
0   libsystem_pthread.dylib         0x3e1c12e8c         start_wqthread

Thread 23
0   libsystem_kernel.dylib          0x36f353b2c         __workq_kernreturn
1   libsystem_pthread.dylib         0x3e1c1313c         _pthread_wqthread

Thread 24
0   libsystem_kernel.dylib          0x36f353b2c         __workq_kernreturn
1   libsystem_pthread.dylib         0x3e1c1313c         _pthread_wqthread

Thread 25
0   libsystem_kernel.dylib          0x36f353b2c         __workq_kernreturn
1   libsystem_pthread.dylib         0x3e1c1313c         _pthread_wqthread

Thread 26
0   libsystem_kernel.dylib          0x36f353b2c         __workq_kernreturn
1   libsystem_pthread.dylib         0x3e1c1313c         _pthread_wqthread

Thread 27
0   libsystem_kernel.dylib          0x36f353b2c         __workq_kernreturn
1   libsystem_pthread.dylib         0x3e1c1313c         _pthread_wqthread

Thread 28
0   libsystem_pthread.dylib         0x3e1c12e8c         start_wqthread

Thread 30
0   libsystem_kernel.dylib          0x36f353558         semaphore_timedwait_trap
1   libdispatch.dylib               0x300fb2c68         _dispatch_sema4_timedwait
2   libdispatch.dylib               0x300fb326c         _dispatch_semaphore_wait_slow
3   libdispatch.dylib               0x300fc3ba0         _dispatch_worker_thread
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 31
0   libsystem_kernel.dylib          0x36f353558         semaphore_timedwait_trap
1   libdispatch.dylib               0x300fb2c68         _dispatch_sema4_timedwait
2   libdispatch.dylib               0x300fb326c         _dispatch_semaphore_wait_slow
3   libdispatch.dylib               0x300fc3ba0         _dispatch_worker_thread
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 32
0   libsystem_kernel.dylib          0x36f353558         semaphore_timedwait_trap
1   libdispatch.dylib               0x300fb2c68         _dispatch_sema4_timedwait
2   libdispatch.dylib               0x300fb326c         _dispatch_semaphore_wait_slow
3   libdispatch.dylib               0x300fc3ba0         _dispatch_worker_thread
4   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 33
0   libsystem_kernel.dylib          0x36f353f90         __psynch_cvwait
1   libsystem_pthread.dylib         0x3e1c1a27c         _pthread_cond_wait
2   Flutter                         0x10639e21c         <redacted>
3   Flutter                         0x1063e4634         <redacted>
4   Flutter                         0x10639db44         <redacted>
5   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

Thread 34
0   libsystem_kernel.dylib          0x36f353f90         __psynch_cvwait
1   libsystem_pthread.dylib         0x3e1c1a27c         _pthread_cond_wait
2   Flutter                         0x10639e21c         <redacted>
3   Flutter                         0x1063e4634         <redacted>
4   Flutter                         0x10639db44         <redacted>
5   libsystem_pthread.dylib         0x3e1c139a0         _pthread_start

@flutter-symbolizer-bot ios arm64 https://github.com/flutter/flutter/issues/96500#issue-1099792204

Hi @declanwoods, Thanks for filing the issue. Please share the complete output of flutter doctor -v.
Thanks

Hi @maheshmnj,
I am not sure whether it is related, but in an instance where I saw the app crash, the camera glitched out directly beforehand.

CI pipeline for exact version - flutter info from upgrade
Flutter 2.8.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 77d935af4d (13 days ago) • 2021-12-16 08:37:33 -0800
Engine • revision 890a5fca2e
Tools • Dart 2.15.1

Development machine - flutter doctor -v
[✓] Flutter (Channel stable, 2.8.1, on macOS 11.5.2 20G95 darwin-x64, locale en-AU)
    • Flutter version 2.8.1 at /Users/declanwoods/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (4 weeks ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1
    • Pub download mirror http://<IP_ADDRESS>:4000

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/declanwoods/Library/Android/sdk
    • Platform android-31, build-tools 30.0.2
    • ANDROID_SDK_ROOT = /Users/declanwoods/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] IntelliJ IDEA Community Edition (version 2020.1.4)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 54.0.1
    • Dart plugin version 201.9335

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.32.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 11.5.2 20G95 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 97.0.4692.71

• No issues found!

@flutter-symbolizer-bot engine#890a5fca2e ios arm64 https://github.com/flutter/flutter/issues/96500#issue-1099792204

Thanks for the info leaving this issue open for further insights from the team.

cc: @chinmaygarde

Thanks @maheshmnj
I can see that the crash log isn't symbolizing, so I've attached another from a random device

crash log
OS Version: iOS 15.1 (19B74)
Report Version: 104

Exception Type: EXC_CRASH (SIGABRT)
Crashed Thread: 3

Application Specific Information:
_status < MTLCommandBufferStatusCommitted > -[IOGPUMetalCommandBuffer setCurrentCommandEncoder:] > setStoreAction: > setTexture:

Thread 3 Crashed:
0   libsystem_kernel.dylib          0x375b5a9e8         __pthread_kill
1   libsystem_pthread.dylib         0x3b662e820         pthread_kill
2   libsystem_c.dylib               0x316f530b0         abort
3   Metal                           0x3340f9464         MTLReleaseAssertionFailure
4   IOGPU                           0x397d46bdc         -[IOGPUMetalCommandBuffer setCurrentCommandEncoder:]
5   Metal                           0x334059dd8         -[_MTLCommandEncoder initWithCommandBuffer:]
6   IOGPU                           0x397d487bc         -[IOGPUMetalCommandEncoder initWithCommandBuffer:]
7   AGXMetalA10                     0x3b89e80b0         <redacted>
8   AGXMetalA10                     0x3b896d554         <redacted>
9   Flutter                         0x103aaf428         <redacted>
10  Flutter                         0x103ab6518         <redacted>
11  Flutter                         0x103ab3038         <redacted>
12  Flutter                         0x103a4bdd8         <redacted>
13  Flutter                         0x1039b37bc         <redacted>
14  Flutter                         0x1039b3ba8         <redacted>
15  Flutter                         0x10388167c         <redacted>
16  Flutter                         0x103d25274         <redacted>
17  Flutter                         0x103caa558         <redacted>
18  Flutter                         0x103be0704         <redacted>
19  Flutter                         0x103be0c20         <redacted>
20  Flutter                         0x103b18868         <redacted>
21  Flutter                         0x103be0318         <redacted>
22  Flutter                         0x103be1c50         <redacted>
23  Flutter                         0x103be0ed4         <redacted>
24  Flutter                         0x103be9314         <redacted>
25  Flutter                         0x103b170d8         <redacted>
26  Flutter                         0x103b1a6a4         <redacted>
27  CoreFoundation                  0x302601fc8         __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
28  CoreFoundation                  0x30258c334         __CFRunLoopDoTimer
29  CoreFoundation                  0x302586fc8         __CFRunLoopDoTimers
30  CoreFoundation                  0x302566ea0         __CFRunLoopRun
31  CoreFoundation                  0x302579d78         CFRunLoopRunSpecific
32  Flutter                         0x103b1a570         <redacted>
33  Flutter                         0x103b19d30         <redacted>
34  libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 0
0   libsystem_kernel.dylib          0x375b54b10         mach_msg_trap
1   libsystem_kernel.dylib          0x375b55130         mach_msg
2   CoreFoundation                  0x302562abc         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x302566ba4         __CFRunLoopRun
4   CoreFoundation                  0x302579d78         CFRunLoopRunSpecific
5   GraphicsServices                0x336a7f99c         GSEventRunModal
6   UIKitCore                       0x307110058         -[UIApplication _run]
7   UIKitCore                       0x306ea5cdc         UIApplicationMain
8   Pinnacle                        0x2024e0d44         main (AppDelegate.swift:6)
9   <unknown>                       0x102984190         <redacted>

Thread 1 name: com.apple.uikit.eventfetch-thread
0   libsystem_kernel.dylib          0x375b54b10         mach_msg_trap
1   libsystem_kernel.dylib          0x375b55130         mach_msg
2   CoreFoundation                  0x302562abc         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x302566ba4         __CFRunLoopRun
4   CoreFoundation                  0x302579d78         CFRunLoopRunSpecific
5   Foundation                      0x3053f0008         -[NSRunLoop(NSRunLoop) runMode:beforeDate:]
6   Foundation                      0x30542f188         -[NSRunLoop(NSRunLoop) runUntilDate:]
7   UIKitCore                       0x30708dd54         -[UIEventFetcher threadMain]
8   Foundation                      0x30543cef8         __NSThread__start__
9   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 2 name: io.flutter.1.ui
0   libsystem_kernel.dylib          0x375b554f0         __psynch_cvwait
1   libsystem_pthread.dylib         0x3b662abf8         _pthread_cond_wait$VARIANT$mp
2   Flutter                         0x103e20ce4         <redacted>
3   Flutter                         0x103e1fe4c         <redacted>
4   Flutter                         0x103e1b0e8         <redacted>
5   Flutter                         0x103e1bc80         <redacted>
6   Flutter                         0x103d17844         <redacted>
7   Flutter                         0x103be4f3c         <redacted>
8   Flutter                         0x103bda0b0         <redacted>
9   Flutter                         0x103b170d8         <redacted>
10  Flutter                         0x103b1a6a4         <redacted>
11  CoreFoundation                  0x302601fc8         __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
12  CoreFoundation                  0x30258c334         __CFRunLoopDoTimer
13  CoreFoundation                  0x302586fc8         __CFRunLoopDoTimers
14  CoreFoundation                  0x302566ea0         __CFRunLoopRun
15  CoreFoundation                  0x302579d78         CFRunLoopRunSpecific
16  Flutter                         0x103b1a570         <redacted>
17  Flutter                         0x103b19d30         <redacted>
18  libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 3 name: io.flutter.1.raster Crashed:
0   libsystem_kernel.dylib          0x375b5a9e8         __pthread_kill
1   libsystem_pthread.dylib         0x3b662e820         pthread_kill
2   libsystem_c.dylib               0x316f530b0         abort
3   Metal                           0x3340f9464         MTLReleaseAssertionFailure
4   IOGPU                           0x397d46bdc         -[IOGPUMetalCommandBuffer setCurrentCommandEncoder:]
5   Metal                           0x334059dd8         -[_MTLCommandEncoder initWithCommandBuffer:]
6   IOGPU                           0x397d487bc         -[IOGPUMetalCommandEncoder initWithCommandBuffer:]
7   AGXMetalA10                     0x3b89e80b0         <redacted>
8   AGXMetalA10                     0x3b896d554         <redacted>
9   Flutter                         0x103aaf428         <redacted>
10  Flutter                         0x103ab6518         <redacted>
11  Flutter                         0x103ab3038         <redacted>
12  Flutter                         0x103a4bdd8         <redacted>
13  Flutter                         0x1039b37bc         <redacted>
14  Flutter                         0x1039b3ba8         <redacted>
15  Flutter                         0x10388167c         <redacted>
16  Flutter                         0x103d25274         <redacted>
17  Flutter                         0x103caa558         <redacted>
18  Flutter                         0x103be0704         <redacted>
19  Flutter                         0x103be0c20         <redacted>
20  Flutter                         0x103b18868         <redacted>
21  Flutter                         0x103be0318         <redacted>
22  Flutter                         0x103be1c50         <redacted>
23  Flutter                         0x103be0ed4         <redacted>
24  Flutter                         0x103be9314         <redacted>
25  Flutter                         0x103b170d8         <redacted>
26  Flutter                         0x103b1a6a4         <redacted>
27  CoreFoundation                  0x302601fc8         __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
28  CoreFoundation                  0x30258c334         __CFRunLoopDoTimer
29  CoreFoundation                  0x302586fc8         __CFRunLoopDoTimers
30  CoreFoundation                  0x302566ea0         __CFRunLoopRun
31  CoreFoundation                  0x302579d78         CFRunLoopRunSpecific
32  Flutter                         0x103b1a570         <redacted>
33  Flutter                         0x103b19d30         <redacted>
34  libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 4 name: io.flutter.1.io
0   libsystem_kernel.dylib          0x375b54b10         mach_msg_trap
1   libsystem_kernel.dylib          0x375b55130         mach_msg
2   CoreFoundation                  0x302562abc         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x302566ba4         __CFRunLoopRun
4   CoreFoundation                  0x302579d78         CFRunLoopRunSpecific
5   Flutter                         0x103b1a570         <redacted>
6   Flutter                         0x103b19d30         <redacted>
7   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 5 name: io.worker.1
0   libsystem_kernel.dylib          0x375b554f0         __psynch_cvwait
1   libsystem_pthread.dylib         0x3b662abf8         _pthread_cond_wait$VARIANT$mp
2   libc++.1.dylib                  0x330b032b4         std::__1::condition_variable::wait
3   Flutter                         0x103b14928         <redacted>
4   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 6 name: io.worker.2
0   libsystem_kernel.dylib          0x375b554f0         __psynch_cvwait
1   libsystem_pthread.dylib         0x3b662abf8         _pthread_cond_wait$VARIANT$mp
2   libc++.1.dylib                  0x330b032b4         std::__1::condition_variable::wait
3   Flutter                         0x103b14928         <redacted>
4   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 7 name: dart:io EventHandler
0   libsystem_kernel.dylib          0x375b562f8         kevent
1   Flutter                         0x103cdd4dc         <redacted>
2   Flutter                         0x103d0c4e8         <redacted>
3   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 8
0   libsystem_kernel.dylib          0x375b55088         __semwait_signal
1   libsystem_c.dylib               0x316f388dc         nanosleep
2   libsystem_c.dylib               0x316f4c288         sleep
3   Sentry                          0x102d3e188         monitorCachedData (SentryCrashCachedData.c:139)
4   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 9 name: SentryCrash Exception Handler (Secondary)
0   libsystem_kernel.dylib          0x375b54b10         mach_msg_trap
1   libsystem_kernel.dylib          0x375b55130         mach_msg
2   libsystem_kernel.dylib          0x375b5fff8         thread_suspend
3   Sentry                          0x102d4b02c         handleExceptions (SentryCrashMonitor_MachException.c:258)
4   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 10 name: SentryCrash Exception Handler (Primary)
0   libsystem_kernel.dylib          0x375b54b10         mach_msg_trap
1   libsystem_kernel.dylib          0x375b55130         mach_msg
2   Sentry                          0x102d4b058         handleExceptions (SentryCrashMonitor_MachException.c:266)
3   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 11 name: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib          0x375b54b10         mach_msg_trap
1   libsystem_kernel.dylib          0x375b55130         mach_msg
2   CoreFoundation                  0x302562abc         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x302566ba4         __CFRunLoopRun
4   CoreFoundation                  0x302579d78         CFRunLoopRunSpecific
5   CFNetwork                       0x303753f34         _CFURLStorageSessionCopyIdentifier
6   Foundation                      0x30543cef8         __NSThread__start__
7   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 12 name: JavaScriptCore bmalloc scavenger
0   libsystem_kernel.dylib          0x375b554f0         __psynch_cvwait
1   libsystem_pthread.dylib         0x3b662abf8         _pthread_cond_wait$VARIANT$mp
2   libc++.1.dylib                  0x330b032b4         std::__1::condition_variable::wait
3   JavaScriptCore                  0x3180e8d0c         std::__1::condition_variable_any::wait<T>
4   JavaScriptCore                  0x3180ed7c8         bmalloc::Scavenger::threadRunLoop
5   JavaScriptCore                  0x3180ed17c         bmalloc::Scavenger::threadEntryPoint
6   JavaScriptCore                  0x3180ee81c         std::__1::__thread_proxy<T>
7   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 13
0   libsystem_kernel.dylib          0x375b550cc         __workq_kernreturn
1   libsystem_pthread.dylib         0x3b6622ecc         _pthread_wqthread

Thread 14
0   libsystem_kernel.dylib          0x375b550cc         __workq_kernreturn
1   libsystem_pthread.dylib         0x3b6622ecc         _pthread_wqthread

Thread 15
0   libsystem_pthread.dylib         0x3b66229e8         start_wqthread

Thread 16
0   libsystem_kernel.dylib          0x375b54b10         mach_msg_trap
1   libsystem_kernel.dylib          0x375b55130         mach_msg
2   CoreFoundation                  0x302562abc         __CFRunLoopServiceMachPort
3   CoreFoundation                  0x302566ba4         __CFRunLoopRun
4   CoreFoundation                  0x302579d78         CFRunLoopRunSpecific
5   CoreFoundation                  0x3025f425c         CFRunLoopRun
6   CoreMotion                      0x31ad38a28         CLMotionActivity::isTypeInVehicle
7   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 17
0   CoreFoundation                  0x30256d7f8         CFNumberGetValue
1   CoreFoundation                  0x30258c898         [inlined] -[__NSCFNumber longValue]
2   CoreFoundation                  0x30258c898         -[__NSCFNumber longValue]
3   FirebaseCoreDiagnostics         0x1028515d0         FIRPopulateProtoWithInfoFromUserInfoParams (FIRCoreDiagnostics.m:272)
4   FirebaseCoreDiagnostics         0x1028523a4         __42-[FIRCoreDiagnostics sendDiagnosticsData:]_block_invoke (FIRCoreDiagnostics.m:509)
5   libdispatch.dylib               0x301fb3190         _dispatch_call_block_and_release
6   libdispatch.dylib               0x301fb4194         _dispatch_client_callout
7   libdispatch.dylib               0x301f5a0d0         _dispatch_lane_serial_drain$VARIANT$mp
8   libdispatch.dylib               0x301f5ab80         _dispatch_lane_invoke$VARIANT$mp
9   libdispatch.dylib               0x301f6474c         _dispatch_workloop_worker_thread
10  libsystem_pthread.dylib         0x3b6622e80         _pthread_wqthread

Thread 18
0   libsystem_kernel.dylib          0x375b550cc         __workq_kernreturn
1   libsystem_pthread.dylib         0x3b6622ecc         _pthread_wqthread

Thread 19
0   libsystem_pthread.dylib         0x3b66229e8         start_wqthread

Thread 20
0   libsystem_kernel.dylib          0x375b554f0         __psynch_cvwait
1   libsystem_pthread.dylib         0x3b662ac24         _pthread_cond_wait$VARIANT$mp
2   Flutter                         0x103dce21c         <redacted>
3   Flutter                         0x103e14634         <redacted>
4   Flutter                         0x103dcdb44         <redacted>
5   libsystem_pthread.dylib         0x3b66243a0         _pthread_start

Thread 21
0   libsystem_pthread.dylib         0x3b66229f4         thread_start

EOF

@declanwoods , thanks for the log, it seems the bot only symbolizes the ios logs starting with incident Identifier

iOS crashes starting with Incident Identifier: ... line.

Anyways let wait for the team members' input.

This is a duplicate fix for https://github.com/flutter/flutter/issues/89171 which has a speculative fix.


Gamepad support in WSL2 (/dev/jsx)

Is your feature request related to a problem? Please describe.
It would be nice to have gamepads exposed to Linux guests for the convince of running and testing cross platform programs that can make use of gamepads solely on Windows using WSLg. You can already attach USB gamepads to the WSL2 instance using usbipd-win, however the system dsitro does not have gamepad support enabled since this use-case was not considered.
Describe the solution you'd like
The system distro to have USB gamepad support enabled by default.
Describe alternatives you've considered
It is possible to modify the system distro kernel to enable USB gamepad support, however this is a rather large maintenance burden for such a dinky little feature since you have to continuously keep the custom kernel up to date.

Actually I am pretty sure this is tied to the Linux HID subsystem so I am pretty sure there are more serious potential use cases by having this enabled. It would apply for any USB input device.

I have been facing the same.
I have switched my PC to Win 11 in order to install and Run some ROS GUI apps, which is not possible in Win 10 and some heat issues on Ubuntu.
But I need the USB to control the Robot and I could not make my Joypad work.

I have been facing the same. I have switched my PC to Win 11 in order to install and Run some ROS GUI apps, which is not possible in Win 10 and some heat issues on Ubuntu. But I need the USB to control the Robot and I could not make my Joypad work.

I got gamepad attached to wsl using usbipd but seems that wsl2 has no joydev module what seems to be needed for gamepads. Not sure if it is fixable problem...

I got gamepad attached to wsl2 using usbipd and it appears under /dev/bus/usb/00x/ devices but not under /dev/input/jsx device. Is it some driver issue or what?

Have the same problem.
Did you figure it out?

Hello, i solved this problem by rebuilding kernel:

clone your kernel version from this
replace Microsoft/config-wsl with config-wsl from archive
kernel-xpad.zip
make KCONFIG_CONFIG=Microsoft/config-wsl

if u don't want to build kernel yourself:

wsl --shutdown
add in your .wslconfig line kernel=C:\\Path\\To\\bzImage with path to bzImage from archive.
PROFIT

i using kernel <IP_ADDRESS> and add to config these lines:
CONFIG_LOCALVERSION="-kotc9"
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=y
CONFIG_JOYSTICK_XPAD=y
CONFIG_JOYSTICK_XPAD_FF=y

link that might help:
https://microhobby.com.br/blog/2019/09/21/compiling-your-own-linux-kernel-for-windows-wsl2/
hope this helps you too!

kernel-xpad.zip

Add kernel-parport please.
Thank you.

Hello, i temporarily solved missing xpad by rebuilding kernel:

clone your kernel version from this
replace Microsoft/config-wsl with config-wsl from archive
kernel-xpad.zip
make KCONFIG_CONFIG=Microsoft/config-wsl

if u don't want to build kernel yourself:

wsl --shutdown
add in your .wslconfig line kernel=C:\\Path\\To\\bzImage with path to bzImage from archive.
PROFIT

i using kernel <IP_ADDRESS> and add to config these lines:
CONFIG_LOCALVERSION="-kotc9"
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=y
CONFIG_JOYSTICK_XPAD=y
CONFIG_JOYSTICK_XPAD_FF=y

link that might help: https://microhobby.com.br/blog/2019/09/21/compiling-your-own-linux-kernel-for-windows-wsl2/
hope this helps you too!

kernel-xpad.zip

This solution worked great for me, thanks for the help!
Just to add on a little bit to the solution to get my xbox elite series 1 controller working:
Without the changes to the kernel, my xbox controller would not show up under /dev/input.
I then found the lsusb does not detect my device in WSL. to get the device passed from W11 -> Ubuntu (WSL) -> Docker, I enlisted the help of usbipd which is another tool I use to attach the usb bus into my WSL instance.
After that, I noticed I could run jstest and input is shown up, but for my application, it still wasn't detected. If that's the case for yours as well, run sudo chmod 777 event0 and sudo chmod 777 js0. Then everything starts talking beautifully. It was something to do with permissions after plugging in the device.

Hello, i temporarily solved missing xpad by rebuilding kernel:
1. clone your kernel version from [this](https://github.com/microsoft/WSL2-Linux-Kernel)

2. replace `Microsoft/config-wsl` with config-wsl from archive
   [kernel-xpad.zip](https://github.com/microsoft/WSL/files/10098030/kernel-xpad.zip)

3. make KCONFIG_CONFIG=Microsoft/config-wsl

if u don't want to build kernel yourself:
1. wsl --shutdown

2. add in your .wslconfig line `kernel=C:\\Path\\To\\bzImage` with path to bzImage from archive.

3. PROFIT

i using kernel <IP_ADDRESS> and add to config these lines:
CONFIG_LOCALVERSION="-kotc9"
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=y
CONFIG_JOYSTICK_XPAD=y
CONFIG_JOYSTICK_XPAD_FF=y

link that might help: https://microhobby.com.br/blog/2019/09/21/compiling-your-own-linux-kernel-for-windows-wsl2/
hope this helps you too!

kernel-xpad.zip

This doesn't seem to work anymore, also tried compiling kernel with those specific options, /dev/jsx still missing (/dev/input/jsx missing too).... (and also tried bunch of linux specific things but nothing worked)

I made the discussed edits to the most recent kernel in this repo. Feel free to expand upon the explanation I put in the README, or let me know how to improve the repo as a resource via PRs.

thx for this, is there a way to download a binary to put this version of wls on my pc? I really know nothing of  compiling kernels.

do you just run the two command in the wsl terminal?
second fails.
make KCONFIG_CONFIG=Microsoft/config-wsl
make: *** No targets specified and no makefile found.  Stop.

I made the discussed edits to the most recent kernel in this repo. Feel free to expand upon the explanation I put in the README, or let me know how to improve the repo as a resource via PRs.

@atticusrussell Thanks for the excellent instructions you added to your repo! I'm working on a similar ROS2 project and having the same issue you had last year enabling joystick support. It has been quite the headache.
Since your fork of the kernel is a little outdated, I forked a fresh copy and made what I think are the same changes you did to the config.wsl file (see commit here). I was able to compile the kernel, replace it in WSL2, bind/attach it with usbipd on Windows, and see the device on /dev/input/js0. I am SO close to getting this to work and for the first time, I can  see the device using jstest-gtk. But for the life of me I can't get the joystick events to work. Did you ever run into this issue? If not, do you have any thoughts as to what might be broken? I've had the same results from both a cheap USB gamepad and one from an XBOX One.
@skunx99 To answer your question, you first need to clone the repo. If you are using the one from @atticusrussell, log into your wsl terminal first and clone it with git clone https://github.com/atticusrussell/WSL2-Linux-Kernel. Then cd WSL2-Linux-Kernel into the directory and run through the rest of the build steps in his readme. You'll probably need to install the build tools first. I'm not sure all of these are needed, but I did that by running sudo apt-get install git fakeroot build-essential ncurses-dev xz-utils libssl-dev bc flex libelf-dev bison dwarves. I've never done this either and it was much easier than I thought.

My attempt

First make sure you are at home so you do not make a mess elsewhere
git clone https://github.com/atticusrussell/WSL2-Linux-Kernel
sudo apt-get install git fakeroot build-essential ncurses-dev xz-utils libssl-dev bc flex libelf-dev bison dwarves
cd WSL2-Linux-Kernel
make KCONFIG_CONFIG=Microsoft/config-wsl
Answer yes to everything I guess? Did see that talked about
cp vmlinux /mnt/c/Users//  <<<<----- make sure to put in your user name and not < and >  -- i.e  "cp vmlinux /mnt/c/Users/john"
vi /mnt/c/Users//.wslconfig make sure to replace name again.
add this to the file
[wsl2]
kernel=C:\Users\\vmlinux
save and exit
in  vi
:w
:q
wsl --shutdown Ubuntu  from power shell in windows
run wsl again
uname -r
<IP_ADDRESS>-microsoft-standard-WSL2

From the look of that I think it failed...

@skunx99 Make sure you change all the usernames where appropriate. Let's say your Windows' username is skunx99. Then you should be able to open the following file in Windows. C:\Users\skunx99\.wslconfig. The vmlinux file should be in that folder too. And the contents of the .wslconfig should look like this:
[wsl2]
kernel=C:\\Users\\skunx99\\vmlinux

If any of that is different, fit it and restart WSL. Then check the kernel version with uname -r in WSL.

this is all correct. On windows I always use Administrator

best info I can get is
PS C:\Windows\System32\WindowsPowerShell\v1.0>  wsl.exe -l -v
NAME            STATE           VERSION

Ubuntu          Stopped         2
Ubuntu-22.04    Stopped         2
PS C:\Windows\System32\WindowsPowerShell\v1.0>  wsl.exe -v
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25880.1000-230602-1350.main
Windows version: 10.0.22631.3593
PS C:\Windows\System32\WindowsPowerShell\v1.0>  wsl.exe
freezes here.

Not sure. The build in https://github.com/atticusrussell/WSL2-Linux-Kernel was forked from kernel <IP_ADDRESS> and is currently 8,708 commits behind current. You could try the build I just made, which I forked this morning from the latest copy (<IP_ADDRESS>). I tried to mirror all the changes from @atticusrussell's fork and can now see the joystick in WSL, but as I said I'm still having issues with the events. But it might be worthwhile. All the steps are the same, but you'd start with git clone https://github.com/timmhayes/WSL2-Linux-Kernel. I'd love to hear if it works for you. I feel like I'm still missing something.

I apologize for the redundant question. but why not just share the binary?

that one worked

@skunx99 Great, glad to hear it. I was just trying to figure out how to publish my binary as a release.
I get the same view using my joystick, but the UI doesn't update when I push the buttons. Are all the buttons mapping correctly for you? I can't get that part to work and I'm not sure how to fix it.

yeah all is good here, interestingly this is my wheelhouse. I maybe can help. Let me try my Xbox one.

I have an old GameSir G3 gamepad and an XBOX controller. Both work fine from https://hardwaretester.com/gamepad using the Gamepad API from my Windows machine. I've tried attaching both at different times through usbipd and they seem to work, creating a device at /dev/input/js0 and /dev/input/event0. And when I run jstest-gtk from Ubuntu, I see the following:

I had installed other XBOX drivers at some point, but I wiped those out when I updated my kernel this morning. So I guess the answer to that question is  no.
So everything seems to work, but I don't see anything update in jstest-gtk when I use the controls... so the events are not working.

maybe try jstest alone ?
also try with the event instead of js, I have seen that  with some xbox drivers. but you should get an error if its a normal driver.
you can get the raw data by doing
cat /dev/input/js0
and see if its at least sending from the driver.

maybe try jstest alone

jstest on /dev/input/js0 gets me this, with no updates

also try with the event instead of js, I have seen that with some xbox drivers. but you should get an error if its a normal driver.

jstest on /dev/input/event/0 gets me the error you are talking about:

you can get the raw data by doing cat /dev/input/js0 and see if its at least sending from the driver.

I tried that before. Running cat it shows a small amount of data when it loads, but doesn't stream any additional data as I use the gamepad.

Also do
evtest
then 0

That pumps out a list of supported events, but gets to Properties and hangs at Testing ... (interrupt to exit). So something is breaking there...

Ok that's the issue, the event processing is busted.  You can check dmesg and also wireshark to maybe see what is going on, but my guess is this is driver related.  Though I suppose it could also be how windows is handling the to translation. I did update my usbipd the old version was not working. Also There was something about a firewall and giving it permissions. A warning about not skipping that step.

Here is that warning.
https://github.com/dorssel/usbipd-win/issues/335

Thanks, those are good ideas. I don't think I'm having firewall issues, as I'm using the standard Windows firewall. I can see the usbipd firewall rule is correctly listed and I'm not getting any errors when I bind the gamepad. I also have the latest copy of usbipd.
I tried evemu and it behaves like the other tools, pumping out all the info about my control, but stopping at events.
Dmesg has some interesting errors about the speed not being set, but I need to do more research about what that means:

RIght now I'm going through this usbipd troubleshooting page running the server with debug messages:
https://github.com/dorssel/usbipd-win/wiki/Troubleshooting
There I'm seeing a message that says, "connection close: Unable to read beyond the end of the stream". I might try posting an issue on their repo, since it looks likely the issue is with that software.

@skunx99 I'm not sure what changed, but my GameSir controller is now working! The Xbox is still out, but I don't care which I use. Thanks again for the help.


Custom operators are obtuse and restrictive

Currently, a custom operator must match one of five weird regexes that have subtle differences and are each of dubious necessity. There are many legitimate character combinations that should be legal, but are not, including anything using advanced unicode (related: unicode identifiers bug).
What this really points to is that custom operators should just be defined as externals, where we can define the rules in scanner.c and make it look something like what the official grammar says it should be.

The biggest impact I'm aware of here is that the <*> operator from Commandant isn't legal, which causes a bunch of failures in Carthage.

So it should follow the "Grammar of operators" from https://docs.swift.org/swift-book/ReferenceManual/zzSummaryOfTheGrammar.html? If so, from what I see, regexes will suffice

It should end up more or less equivalent to that, but there’s some special casing required for cases like the ones in #41, where an operator ending in a < symbol conflicts with the start of a generic type argument.

Unfinished PR at https://github.com/alex-pinkus/tree-sitter-swift/pull/151

For posterity: the top-repo error here currently is at firefox-ios/shared/Functions.swift caused by:
infix operator •


Carthage support?

Any chance for Carthage support?

Ok; I'll give it a shot!

Any news on the pull requests https://github.com/dzenbot/DZNWebViewController/pull/64 or https://github.com/dzenbot/DZNWebViewController/pull/62 ?

Any chance one of the pull requests are going to be merged?


Implement validation of Scenarios

Software Inc. mods can define a Scenario, a starting point for a game.
Completion of this task involves implementing and testing validation of Scenarios. The module should accept input from an arbitrary source and validate it as a valid Scenario.
Description shamelessly copied (and credit given) to Core Dumping from the Software Inc wiki.
Scenarios can define the start conditions, goals and events in-game. A scenario type XML file should contain the following tags:
Tag name 	Description 	Example
Scenario 	This is the root tag, which all tags should be a child to.
Name 	The name of the scenario as shown in the game.
Money 	The available amounts of money at the game start.
100020000
Goals 	Goals define the "win" condition(s). There can be multiple goals, each defined its own Goal tag. Each goal can also have multiple conditions, separated by commas. Conditions are defined by their name followed by an argument. The only goals available at the moment are Money and Date.
Money 200000,Date 6-1980Money 2000000,Date 4-1988
Years 	The available start years at the start of a new game.
19761988
Events 	Events are defined separately in the "Events" Folder. You can leave the tag empty to ignore it.
TestTest2
Simulation 	Whether the competition should be simulated. Relevant if you want the competition to be entirely controlled by your own events.
TRUE
Trees(Optional) 	Whether to place trees in the world
TRUE
MinFloor(Optional) 	The lowest floor the player can build on, between -1 and 9
0
MaxFloor(Optional) 	The lowest floor the player can build on, between 0 and 10
4
CanExpand(Optional) 	Whether the player can buy more plot.
FALSE
ForceEnvironment(Optional) 	Whether the player should be forced to play in a specific environment. Between 0 and 3, for forest, city, tundra and desert.
0
StartingArea(Optional) 	What the players starting plot should be. Defined as x,y,width,height. Will be clamped to match game limits.
9,128,32,32
Example of a "scenario" file:

Test scenario

500
1000

Money 1337,Date 5-1995
Money 1000000,Date 5-2012

1980
1985
2023

Test

TRUE

Only thing left is validation Goals.
When Software Inc loads a mod, it can accept goals with negative money or months beyond 12. Not sure if these are defects in the game or not.

I've decided that validation beyond XSD schema checking will be out of scope for this milestone. I want to make sure that XML validation is solid before branching out into checking for oddities like negative money goals.


Add a component for prefetching images

Overview
Gameface haven't implemented the onLoad event for images. Therefore, it's difficult to make a smooth UI where images don't pop in randomly as they are being fetched.
In this PR I've added a component that can prefetch images and invoke a callback when that is done. At that point they should be cached by the browser, and it should be a lot easier to have a smooth effect in other parts of the application.

Smart solution to the lack of onLoad!
I am wondering if we should not expose this as a new component, but instead integrate the functionality into the Image component so we can leverage its existing functionality.

@hebbeh reached out to me regarding a concern on adding this new package under the @react-facet namespace. After some chat we've agreed that it is probably a good idea to have this under a @ore-ui namespace.
So the final suggestion to the PR is to rename the package to @ore-ui/gameface-image-preloader.
Any thoughts @xaviervia @creativecreature ?

@hebbeh  has sent a feature request to Coherent (to ask for the onLoad event). Therefore, we'll pause this PR until we have received a response from them. If it is on their roadmap, and will be implemented within a reasonable timeframe, we'll close this PR and use that event instead.


Please add CocoaPods support

Since this sat unanswered, I forked the repo and pushed the spec with the latest commit as v1.0.1. CocoaPod is called "SwiftSequence".


Allow nuxt build to read production env

What problem does this feature solve?
Developers don't have to load production env vars and execute nuxt build. Env vars can be directly read from production.
Right now, when i console.log(process.env) from my production (AWS Elastic Beanstalk), the env returned are all my dev environment.
I had to run nuxt build then upload the entire project to AWS EB.

This feature request is available on Nuxt community (#c7427)

Good idea, i use build(pm2) in the beta environment, but env === production.

i need to set env using pm2

you could use https://github.com/samtgarson/nuxt-env

@aldarund Thanks, but this is not what I need

@gotoin I'm.not sure what u need, but that module do exactly what was asked in initial issue


2653: add accesskey 'f' to the student column filter field

Delivers #2653.

I find this (alt +f) working in Microsoft Edge and Safari. But on Chrome and Firefox, it failed. Is there an other shortcut to test on Chrome and Firefox?


About redis cluster delete key operation issue suggestion

Hi all,
When I use redis cluster, I found an issue at node_modules/node-resque/lib/worker.js line 386.
I suggested use async to rewrite that delete key operation.
Because on cluster mode, ioredis library can not delete key on different slot at once.
That error message sow below:
"CROSSSLOT Keys in request don't hash to the same slot".
I rewrite some code to fix this issue.
async.each(
    [
        self.connection.key('worker', name, self.stringQueues()),
        self.connection.key('worker', name, self.stringQueues(), 'started'),
        self.connection.key('stat', 'failed', name),
        self.connection.key('stat', 'processed', name)
    ],
    function iteratee(item, callback){
          self.connection.redis.del( item, function(err){
                callback(err);
            });
    },
    function(error){
        if(error){ self.emit('error', null, null, error); }
        if(typeof callback === 'function'){ callback(error); }
    }
);

Great research!
This will be fixed by: https://github.com/taskrabbit/node-resque/pull/159

> npm publish
+<EMAIL_ADDRESS>


perf: benchmarking encodings (read time, write time)

Many things to add/change, but wanted to get a review on the initial structure. Some considerations -

Can add write benchmarking within the same functions, and populate results in the same csv file. In the future if we want to benchmark query performance we can add new functions to the same file.
Later we can extend this to compare with frameworks other than pyarrow. But for now I have just compared pyarrow and lance.
Can extend to other datasets and encodings

Codecov Report
Attention: Patch coverage is 58.13397% with 1400 lines in your changes missing coverage. Please review.

Project coverage is 79.43%. Comparing base (7d9dbda) to head (2ffd6d3).
Report is 167 commits behind head on main.

Files
Patch %
Lines

rust/lance-encoding-datafusion/src/zone.rs
0.00%
372 Missing :warning:

java/core/lance-jni/src/blocking_dataset.rs
0.00%
225 Missing :warning:

rust/lance-encoding-datafusion/src/lib.rs
0.00%
120 Missing :warning:

...t/lance-encoding/compression-algo/fsst/src/fsst.rs
85.86%
106 Missing and 11 partials :warning:

java/core/lance-jni/src/blocking_scanner.rs
0.00%
87 Missing :warning:

java/core/lance-jni/src/fragment.rs
0.00%
87 Missing :warning:

rust/lance-encoding/src/decoder.rs
81.79%
50 Missing and 23 partials :warning:

java/core/lance-jni/src/error.rs
0.00%
43 Missing :warning:

rust/lance-datafusion/src/expr.rs
2.38%
41 Missing :warning:

rust/lance-datagen/src/generator.rs
42.02%
40 Missing :warning:

... and 16 more

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2383      +/-   ##
==========================================
- Coverage   80.69%   79.43%   -1.27%
==========================================
  Files         192      214      +22
  Lines       56193    62816    +6623
  Branches    56193    62816    +6623
==========================================
+ Hits        45344    49895    +4551
- Misses       8221    10001    +1780
- Partials     2628     2920     +292

Flag
Coverage Δ

unittests
79.43% <58.13%> (-1.27%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Check for deprecated keys sooner in checkpoint loading

Proposed refactoring or deprecation
Fail faster if the model checkpoint contains deprecated keys

Motivation
We currently wait all the way until restore_callbacks to validate that a checkpoint dictionary doesn't contain deprecated keys. However, this happens after the initial checkpoint load, datamodule, and lightning module weights are resumed.
It'd be better to fail faster immediately after the checkpoint load if the checkpoint contains deprecated keys.

Pitch
Add a utility function in the checkpoint connector to handle loading & validation
def _load_and_validate(checkpoint_path: _PATH) -> Dict:
    checkpoint = self.trainer.training_type_plugin.load_checkpoint(checkpoint_path)
    if any(key in checkpoint for key in DEPRECATED_CHECKPOINT_KEYS):
            raise ValueError(
                "The checkpoint you're attempting to load follows an"
                " outdated schema. You can upgrade to the current schema by running"
                f" `python -m pytorch_lightning.utilities.upgrade_checkpoint --file {checkpoint_path}`"
            )

and remove this check from restore_callbacks

Additional context

If you enjoy Lightning, check out our other projects! ⚡

Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, finetuning and solving problems with deep learning

Bolts: Pretrained SOTA Deep Learning models, callbacks and more for research and production with PyTorch Lightning and PyTorch

Lightning Transformers: Flexible interface for high performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

I would like to propose #9396. Users should not need to upgrade a checkpoint manually IMO.


feat(anthropic): Add Claude 3 support

Overview
Anthropic has released the Claude-3 series of models. This PR adds support for that (#523).
The code is updated to use the latest anthropic SDK and the new messages API.
The legacy completions API is still supported and this PR does not introduce any breaking changes.

[x] All API parameters are covered
[x] System messages are supported
[x] The cost of all models is supported
[x] Caching is supported
[x] API key can be provided in the config or via the ANTHROPIC_API_KEY environment variable

References

Release notes: https://www.anthropic.com/news/claude-3-family
Pricing: https://www.anthropic.com/api#pricing

@typpo these changes should be good to go, they were tested locally.

Thank you as always, @streichsbaer!


Void argument routes should not require null

When calling an endpoint that does not accept any parameters (e.g. usersGetCurrentAccount()), null must be passed as an argument. This is somewhat confusing and the error message returned when you forget to pass null doesn't help either:
> dbx.usersGetCurrentAccount()
POST https://api.dropboxapi.com/2/users/get_current_account 400 (Bad Request)
Error in call to API function "users/get_current_account": request body: could not decode input as JSON
> dbx.usersGetCurrentAccount(null)
lib$es6$promise$promise$$Promise {xot8798dunmi: 2, _state: undefined, _result: undefined, _subscribers: Array[0]}

We should default to sending null when no argument is supplied.

The issue still remains, in the typescript definitions.

@bobmoff Apologies for the delay, and thanks for the note. We'll look into it.

@jvilk a seemingly simple fix here is to remove the arg: void from https://github.com/dropbox/dropbox-sdk-js/blob/master/generator/typescript/dropbox.d.ts#L1484 (and any other functions that don't have an input). Can you advice if that is the correct thing to do?

@pran1990 Yes, that is correct.
Note that that file is auto-generated from the stone specification, which specifies that that route takes an argument of type 'void'.
You would need to change the TypeScript stone generator to special-case the output of routes that take a void argument.
Here's an (untested) change to the generator that should work (forgive any syntax errors / things that aren't best practice; I don't often write Python code):
        arg_data_type = fmt_type(route.arg_data_type)
        if route.arg_data_type == "void":
                self.emit('public %s(): Promise<%s>;' %
                           (function_name, fmt_type(route.result_data_type)))
        else:
                self.emit('public %s(arg: %s): Promise<%s>;' %
                          (function_name, arg_data_type, fmt_type(route.result_data_type)))

Hope that helps!

It's already fixed issue, and that's should be closed

Apologies, the original issue was resolved, but we had this still open for the same issue in TypeScript.

Newest version should fix the issue.

This should be fixed for TypeScript as of the latest version, v7.0.0.


Tweak many sections of the document

I love having a general guide, but I have a lot of specific comments.
For example:
GitHub Security Advisory doesn't allow external vulnerability reports,
and thus projects must have another mechanism (typically email).
I don't think that was clear enough.
Email systems should try to use at least hop-by-hop encryption
(e.g., STARTTLS). That's easy to get & provides real benefitst
While Google has a 90-day embargo policy, that is
definitely not a universally-agreed-on number. In fact, it's
unusually long (even Google used to have 60 days as their window),
so claiming that "everyone agrees on it" is easily falsified.
I think it's better to note that there's a range, and it's more
important to have continued discussions with the vulnerability reporter
if the reporter is open to it. After all, if your project's policy is
to make it public in 90 days, but the reporter makes it public in 7,
it really doesn't matter what the project's policy is.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

This took longer than I expected it to & I ended up with a lot of tweaks.
I still hope you'll find it useful.

@SecurityCRob @jenniferfernick would either of you like to review and merge if lgtm?

I’m a bit of a git-klutz (never been formally shown or trained anything…so yay me).  I’m glad to hop on a call and walk through something together.
Cheers,
CRob
Director of Security Communications
Intel Product Assurance and Security
From: Annabelle @.>
Sent: Monday, August 9, 2021 5:26 PM
To: ossf/oss-vulnerability-guide @.>
Cc: Robinson, Christopher @.>; Mention @.>
Subject: Re: [ossf/oss-vulnerability-guide] Tweak many sections of the document (#13)
@SecurityCRobhttps://github.com/SecurityCRob @jenniferfernickhttps://github.com/jenniferfernick would either of you like to review and merge if lgtm?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/ossf/oss-vulnerability-guide/pull/13#issuecomment-895561168, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQRFDLF3ME5IX2IALTEGGFTT4BBWRANCNFSM5BWPG6ZQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

I fixed the "emargo" typo, and also removed trailing spaces on lines.
All good now?

LGTM from @SecurityCRob in meeting 8/19/21


Network driver returns 404s for Discover notifications

See https://github.com/docker/libnetwork/blob/master/docs/remote.md#discovernew-notification
I'm not sure it matters...

I'm planning on taking this on as part of libnetwork ramp-up.  Should get to it early next week.

Suggestion from @tomdee Maybe need discovery parm

Just tried this and I got this in the docker logs
DEBU[0129] discovery notification error : Plugin Error: NetworkDriver.DiscoverNew, {
  "Err": "404: Not Found"
}

I started docker with
sudo docker daemon -D --cluster-store etcd://<IP_ADDRESS>:2379 --cluster-advertise=<IP_ADDRESS>:9999

Fixed by #17


AC sync?

how can i turn the ac ON/OFF if i dont know the AC current state?
is there an option to get the data from the AC to sync with the RP/UNO?

@yairigal were you able to make this work?

@yairigal were you able to make this work?

No, I just kept the current state of the AC synced with my data, in case someone change the state with the remote i just have to manually overwrite it.

@yairigal I actually meant this entire project. I ran it in my Pi and nothing happened.

I also tried the codes and couldn't get them to work. I outlined my experience in more detail in #3.

@oriharel.
Yea, Its actually still running on my arduino (esp 8266).
I'm not sure what causes the problem, the codes you generate or the hardware IR stuff.
I don't remember what i did back then, but you can look at my repo for the code.
https://github.com/yairigal/Arduino_AControl

In case this is still relevant... I managed to get things working with my AEG AC (which is apparently compatible with Electra ACs) using ESPHome with the IRremoteESP8266 library and code inspired by Hagakurje/ESPHome_Gree_AC. You can see how I did it in my repository HWiese1980/electra_chillflex_esphome.


:bug: Add tooltips for Priority and Preemption columns

Resolves: https://issues.redhat.com/browse/MTA-3235


can u provide more event handlers?

such as onMoveStart , onMoveEnd ?

I would accept PRs for those, but don't have time to code and test it, as of now.


Add gen_platform config param

platform indicates WHAT platform DC/OS is deployed on, rather than HOW the install artifacts were generated (provider)

It looks like Velocity is stalled...

velocity was renamed jenkins with the switch from "product" to "solution". I updated the webhooks and resent the lost messages from the last few PRs.

FWIW, we will likely want to expose both platform and provider via some API endpoint in the future, which likely doesn't make sense to be in dcos-signal. It would seem to make sense to have it be some component that is the source of truth for the dcos configuration. That way people could retrieve the config they put in. This would be useful for tests, debugging, reproducing environments, recovering from lost install artifacts, etc.


problems with named volumes instead of --volumes-from

I'm not sure if its caused by that but I have problems getting SSL working. I followed the instructions apart from --volumes-from which I can't use in my environment (portainer). I used named volumes instead, created two for the vhosts.d folder and the html folder on the nginx-proxy and added them with the same folders to the companion. I set them up to be writable.
Containers both run without errors, the proxy creates the vhost config according to my container with the VHOST env var but the companion says default.conf is unchanged and does nothing.
Does anyone have experiences using named volumes instead of --volumes-from? I'm a bit new to docker and may have missed a detail but to my understanding this should work just as good.

Hi. Can you post your whole container configuration ?

from the companion?
    {
        "Id": "fb3a7a10b532606dff588a2dd83fe7a034c3e71aaba28832decc93b4e2beeddd",
        "Created": "2018-09-11T05:32:47.699375032Z",
        "Path": "/bin/bash",
        "Args": [
            "/app/entrypoint.sh",
            "/bin/bash",
            "/app/start.sh"
        ],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 14287,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2018-09-11T06:19:52.0457971Z",
            "FinishedAt": "2018-09-11T06:19:44.973327116Z"
        },
        "Image": "sha256:6bcbf0ae23e87c70e4bd9aa5d459370924d8ea297cb830eed0a558f20a51fb38",
        "ResolvConfPath": "/var/lib/docker/containers/fb3a7a10b532606dff588a2dd83fe7a034c3e71aaba28832decc93b4e2beeddd/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/fb3a7a10b532606dff588a2dd83fe7a034c3e71aaba28832decc93b4e2beeddd/hostname",
        "HostsPath": "/var/lib/docker/containers/fb3a7a10b532606dff588a2dd83fe7a034c3e71aaba28832decc93b4e2beeddd/hosts",
        "LogPath": "/var/lib/docker/containers/fb3a7a10b532606dff588a2dd83fe7a034c3e71aaba28832decc93b4e2beeddd/fb3a7a10b532606dff588a2dd83fe7a034c3e71aaba28832decc93b4e2beeddd-json.log",
        "Name": "/nginx-proxy-le-ssl",
        "RestartCount": 0,
        "Driver": "overlay2",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "docker-default",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/var/run/docker.sock:/var/run/docker.sock:ro",
                "nginx-vhost:/etc/nginx/vhost.d",
                "nginx-html:/usr/share/nginx/html",
                "/root/certs:/etc/nginx/certs"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {}
            },
            "NetworkMode": "bridge",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "no",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": null,
            "CapDrop": null,
            "Dns": null,
            "DnsOptions": null,
            "DnsSearch": null,
            "ExtraHosts": [],
            "GroupAdd": null,
            "IpcMode": "shareable",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 0,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": null,
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": [],
            "DeviceCgroupRules": null,
            "DiskQuota": 0,
            "KernelMemory": 0,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": null,
            "OomKillDisable": false,
            "PidsLimit": 0,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": [
                "/proc/acpi",
                "/proc/kcore",
                "/proc/keys",
                "/proc/latency_stats",
                "/proc/timer_list",
                "/proc/timer_stats",
                "/proc/sched_debug",
                "/proc/scsi",
                "/sys/firmware"
            ],
            "ReadonlyPaths": [
                "/proc/asound",
                "/proc/bus",
                "/proc/fs",
                "/proc/irq",
                "/proc/sys",
                "/proc/sysrq-trigger"
            ]
        },
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/dd842378adb9a0f5a6d8109d4188050c8cf581cb622f4043618e2fca0ddaf28d-init/diff:/var/lib/docker/overlay2/75ff8dec03928ad8c6f1c9337d9bf80529ad8c773990f8ff4e9fb2f2a8dab463/diff:/var/lib/docker/overlay2/023b88815c8eb0e574640a354decf1e51a1862cad11f1876108541f8530f5a8e/diff:/var/lib/docker/overlay2/dd4f2e9008e57756f894a2cea955ff03d4f30fe8ae5b4574abd19d63d786520f/diff:/var/lib/docker/overlay2/f5fe057e9f6acc33fae42ece5c6519902ba03d15f5ebad4d113cf6325f1b3189/diff:/var/lib/docker/overlay2/80efe31540c2ed4849f34fc257fd43c51da4022c41b5300bca3a63c99deb5159/diff:/var/lib/docker/overlay2/9ef0e2e069fb69e16f7715ecd662e20a7ac1194f8f35ed65357c96f67af7a520/diff",
                "MergedDir": "/var/lib/docker/overlay2/dd842378adb9a0f5a6d8109d4188050c8cf581cb622f4043618e2fca0ddaf28d/merged",
                "UpperDir": "/var/lib/docker/overlay2/dd842378adb9a0f5a6d8109d4188050c8cf581cb622f4043618e2fca0ddaf28d/diff",
                "WorkDir": "/var/lib/docker/overlay2/dd842378adb9a0f5a6d8109d4188050c8cf581cb622f4043618e2fca0ddaf28d/work"
            },
            "Name": "overlay2"
        },
        "Mounts": [
            {
                "Type": "bind",
                "Source": "/var/run/docker.sock",
                "Destination": "/var/run/docker.sock",
                "Mode": "ro",
                "RW": false,
                "Propagation": "rprivate"
            },
            {
                "Type": "volume",
                "Name": "nginx-vhost",
                "Source": "/var/lib/docker/volumes/nginx-vhost/_data",
                "Destination": "/etc/nginx/vhost.d",
                "Driver": "local",
                "Mode": "z",
                "RW": true,
                "Propagation": ""
            },
            {
                "Type": "volume",
                "Name": "nginx-html",
                "Source": "/var/lib/docker/volumes/nginx-html/_data",
                "Destination": "/usr/share/nginx/html",
                "Driver": "local",
                "Mode": "z",
                "RW": true,
                "Propagation": ""
            },
            {
                "Type": "bind",
                "Source": "/root/certs",
                "Destination": "/etc/nginx/certs",
                "Mode": "",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "63abaef21058",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "DEBUG=false",
                "DOCKER_HOST=unix:///var/run/docker.sock",
                "NGINX_PROXY_CONTAINER=nginx-proxy",
<EMAIL_ADDRESS>            ],
            "Cmd": [
                "/bin/bash",
                "/app/start.sh"
            ],
            "ArgsEscaped": true,
            "Image": "jrcs/letsencrypt-nginx-proxy-companion:latest",
            "Volumes": {
                "/etc/nginx/certs": {},
                "/etc/nginx/vhost.d": {},
                "/usr/share/nginx/html": {},
                "/var/run/docker.sock": {}
            },
            "WorkingDir": "/app",
            "Entrypoint": [
                "/bin/bash",
                "/app/entrypoint.sh"
            ],
            "OnBuild": null,
            "Labels": {
                "maintainer": "Yves Blusseau<EMAIL_ADDRESS>(@blusseau)"
            }
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "2bbaabcd5013cd5dff807299d0a48ad6053d3cd4208b53c51b39fd0754db5c8d",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "/var/run/docker/netns/2bbaabcd5013",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "4306daf18237214522193f20d189e6ee4a6e34172aa4781581dc1bdfcf18a8ed",
            "Gateway": "<IP_ADDRESS>",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "<IP_ADDRESS>",
            "IPPrefixLen": 16,
            "IPv6Gateway": "",
            "MacAddress": "02:42:ac:11:00:03",
            "Networks": {
                "bridge": {
                    "IPAMConfig": {},
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "d478d520fa2f253bf79eb211f275e4215f3ffd0c889ad32f931ed08dd8f302a0",
                    "EndpointID": "4306daf18237214522193f20d189e6ee4a6e34172aa4781581dc1bdfcf18a8ed",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:03",
                    "DriverOpts": null
                }
            }
        }
    }
]```

I managed to get it setup with --volumes-from and are still seing the problem of the cert not being created. So it may be a different issue. I'm going to change the title of this issue.

Thanks for the config, I had more in mind the command (or compose file if you use docker compose) you use to launch both the nginx proxy and companion container.
You can use docker logs to check why your certs fails to be created. If you are experiencing let's encrypt validation issues, please check the corresponding wiki page on this project.

it's not that they fail to create, I think the issue is more that the companion doesn't see the config file changing.
2018/09/11 07:38:56 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'```

I don't see any hints in the log that there are attempts to create a cert. That's what is confusing me. I've not set it up exactly to the directions in the readme including adding the env var for NGINX_PROXY_CONTAINER which isn't in there and all seems to run just fine and with not visible errors in the log. It's just that the cert doesn't get created.

Again, can you post the whole commands (redacting personal info like mails or domains if needed) you use to launch your nginx proxy, companion and proxyed container ?

sure, sorry for the lack of information from my side:
  --name nginx-proxy \
  -v /root/certs:/etc/nginx/certs:ro \
  -v /etc/nginx/vhost.d \
  -v /usr/share/nginx/html \
  -v /var/run/docker.sock:/tmp/docker.sock:ro \
  --name nginx-proxy \
  --label com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy \
  jwilder/nginx-proxy```

```docker run -d -v /root/certs:/etc/nginx/certs:rw -v /var/run/docker.sock:/var/run/docker.sock:ro -e NGINX_PROXY_CONTAINER=nginx-proxy --volumes-from nginx-proxy --name nginx-proxy-le-ssl jrcs/letsencrypt-nginx-proxy-companion```

```docker run -d -p 9000:9000 -e "VIRTUAL_HOST=my.domain.com" -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer```

That should be it.

Okay. You have to add specific environment variables on the proxyed containers for the whole thing to work. I'd recommend you review both nginx proxy readme and the companion doc (in the project's wiki).

got it - thanks for pointing that out. Should have dug deeper in the docs and not only use the quick readme.

@Helmi Can I close the issue ?

Yeah. sorry for not doing that proactively.


Problem with  component from MUI

See: https://github.com/garronej/tss-react/issues/103#issuecomment-1266999107
Will be fixed when this pr gets merged.

Hello @garronej !
Thank you for your involvement in these issues! Appreciate your time!
Best regards, Ivan

You are very welcome,
You are helping me address critical issues that many peoples are experiencing but only a handful of people like you actually reports.
Best regards,


command-${string}-formatted --success condition fails with dashes

This should use the exit code from the first command (exit 1), but doesn't because the successCondition splits on -:
concurrently \
  --names 'this-one,that-one' \
  --success command-this-one \
  'exit 1' \
  'exit 0'

This version does work:
concurrently \
  --names 'this,that' \
  --success command-that \
  'exit 1' \
  'exit 0'

Thanks for spotting this 🤦

Related, passing a command name that doesn't exist just silently ignores it. Maybe also true with indexes?

Related, passing a command name that doesn't exist just silently ignores it. Maybe also true with indexes?

Thanks for your input! We've discussed this in https://github.com/open-cli-tools/concurrently/pull/318#issuecomment-1125982525.

Fix out in v7.2.1.