text:
Error while play back

Having these strange errors since I updated to v19 beta 2
2023-02-14T21:17:56.334Z [V4L2:EZCAP GAME LIN] Frame too small: 0 != 4147200
2023-02-14T21:17:57.198Z [MUXER0] Priority 240 is now active
and
2023-02-14T21:17:54.200Z [HYPERHDR0] No source left -> switch LED-Device off
and
2023-02-14T21:17:56.292Z [V4L2:EZCAP GAME LIN] LUT file is not found here: /home/wouter/.hyperhdr/lut_lin_tables.3d
2023-02-14T21:17:56.292Z [V4L2:EZCAP GAME LIN] (Grabber.cpp:445) LUT file found: /usr/share/hyperhdr/lut/lut_lin_tables.3d
is this related to power source?  Or where do I start looking? Getting very frustrated with this

Without full logs cant help unfortunately. You was asked about it when submitted the issue. Suggest discussion section.

Aah sorry about that didn’t see that on the phone
here is full log
2023-02-14T20:52:47.713Z [IMAGETOLED0] Total index number is: 57248 (memory: 57248). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:53:20.011Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T20:53:23.710Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:54:20.013Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T20:55:13.070Z [IMAGETOLED0] Total index number is: 43136 (memory: 43136). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:55:16.370Z [IMAGETOLED0] Total index number is: 42672 (memory: 42672). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:55:20.009Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 6ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T20:55:37.207Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:55:54.170Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:56:06.573Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:56:07.903Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:56:10.472Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:56:16.233Z [IMAGETOLED0] Total index number is: 34932 (memory: 34932). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:56:20.007Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 6ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T20:56:20.501Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:56:22.500Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:56:47.003Z [IMAGETOLED0] Total index number is: 42800 (memory: 42800). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:56:49.570Z [IMAGETOLED0] Total index number is: 43264 (memory: 43264). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:56:54.501Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:57:13.863Z [IMAGETOLED0] Total index number is: 43032 (memory: 43032). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:57:20.026Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 6ms, frames = 1801, invalid = 0], [INSTANCE0: FPS = 30.01, processed = 1800], [LED0: FPS = 142.86, send = 8571, processed = 11999, dropped = 0]
2023-02-14T20:57:30.065Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:57:34.231Z [IMAGETOLED0] Total index number is: 38876 (memory: 38876). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:57:39.766Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:57:42.398Z [IMAGETOLED0] Total index number is: 43264 (memory: 43264). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:57:44.166Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:57:49.664Z [IMAGETOLED0] Total index number is: 40452 (memory: 40452). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:57:56.731Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:58:20.022Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8572, processed = 12001, dropped = 0]
2023-02-14T20:58:58.260Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:59:01.489Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:59:19.754Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:59:20.021Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1801], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T20:59:22.325Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:59:33.691Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:59:39.253Z [IMAGETOLED0] Total index number is: 42834 (memory: 42834). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:59:41.423Z [IMAGETOLED0] Total index number is: 43156 (memory: 43156). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T20:59:54.856Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:00:20.022Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.86, send = 8571, processed = 11999, dropped = 0]
2023-02-14T21:00:32.687Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:00:33.883Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:00:40.520Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:01:20.017Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.86, send = 8572, processed = 12001, dropped = 0]
2023-02-14T21:02:20.016Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:02:42.845Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:02:52.645Z [IMAGETOLED0] Total index number is: 42800 (memory: 42800). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:03:01.378Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:03:05.049Z [IMAGETOLED0] Total index number is: 41712 (memory: 41712). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:03:09.344Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:03:17.211Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:03:18.848Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:03:20.015Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:03:49.380Z [IMAGETOLED0] Total index number is: 42800 (memory: 42800). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:04:01.810Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:04:20.011Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:05:15.114Z [IMAGETOLED0] Total index number is: 43136 (memory: 43136). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:05:18.646Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:05:20.013Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.84, send = 8570, processed = 11999, dropped = 0]
2023-02-14T21:05:35.608Z [IMAGETOLED0] Total index number is: 42788 (memory: 42788). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:05:39.678Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:05:49.374Z [IMAGETOLED0] Total index number is: 42800 (memory: 42800). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:05:57.914Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:06:02.114Z [IMAGETOLED0] Total index number is: 42800 (memory: 42800). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:06:03.948Z [IMAGETOLED0] Total index number is: 43264 (memory: 43264). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:06:05.979Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:06:10.278Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:06:20.007Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.86, send = 8572, processed = 12001, dropped = 0]
2023-02-14T21:07:20.005Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:08:09.603Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:08:18.210Z [IMAGETOLED0] Total index number is: 43032 (memory: 43032). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:08:20.003Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:08:49.501Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:09:02.972Z [IMAGETOLED0] Total index number is: 43264 (memory: 43264). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:09:05.901Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:09:20.008Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:09:20.738Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:09:27.300Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:09:28.533Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:09:37.066Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:10:20.003Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:10:39.069Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:10:42.097Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:11:08.467Z [IMAGETOLED0] Total index number is: 42788 (memory: 42788). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:11:14.266Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:11:20.026Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1801, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.86, send = 8571, processed = 11999, dropped = 0]
2023-02-14T21:12:20.030Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1801], [LED0: FPS = 142.86, send = 8572, processed = 12001, dropped = 0]
2023-02-14T21:12:26.863Z [IMAGETOLED0] Total index number is: 43136 (memory: 43136). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:12:40.261Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:12:45.591Z [IMAGETOLED0] Total index number is: 43264 (memory: 43264). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:12:58.024Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:13:20.027Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:13:30.489Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:13:48.125Z [IMAGETOLED0] Total index number is: 43136 (memory: 43136). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:13:50.758Z [IMAGETOLED0] Total index number is: 42788 (memory: 42788). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:14:13.858Z [IMAGETOLED0] Total index number is: 40460 (memory: 40460). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:14:18.724Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:14:20.020Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.84, send = 8570, processed = 11999, dropped = 0]
2023-02-14T21:14:30.325Z [IMAGETOLED0] Total index number is: 39368 (memory: 39368). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:14:34.491Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:14:43.692Z [V4L2:EZCAP GAME LIN] Frame too small: 0 != 4147200
2023-02-14T21:14:43.692Z [V4L2:EZCAP GAME LIN] Frame too small: 0 != 4147200
2023-02-14T21:14:43.692Z [V4L2:EZCAP GAME LIN] Frame too small: 0 != 4147200
2023-02-14T21:14:43.693Z [V4L2:EZCAP GAME LIN] Frame too small: 0 != 4147200
2023-02-14T21:14:43.693Z [V4L2:EZCAP GAME LIN] Frame too small: 0 != 4147200
2023-02-14T21:14:44.853Z [MUXER0] Priority 240 is now inactive
2023-02-14T21:14:44.853Z [MUXER0] Set visible priority to 255
2023-02-14T21:14:44.853Z [HYPERHDR0] New priority[255], previous [240]
2023-02-14T21:14:44.853Z [HYPERHDR0] No source left -> switch LED-Device off
2023-02-14T21:14:44.853Z [SMOOTHING0] Clearing queued colors before: disabling
2023-02-14T21:14:44.853Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:14:44.853Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:138) Disable device
2023-02-14T21:14:44.853Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:205) Stopping timer
2023-02-14T21:14:44.853Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:355) Switch off
2023-02-14T21:14:44.853Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:313) Set LED strip to black/power off
2023-02-14T21:14:44.857Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:123) Flush was successful
2023-02-14T21:14:44.857Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:136) Close UART: ttyACM0
2023-02-14T21:14:45.091Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [LED0: FPS = 142.84, send = 8570, processed = 11999, dropped = 0]
2023-02-14T21:14:45.091Z [COMPONENTREG0] LED device: disabled
2023-02-14T21:14:45.091Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0]
2023-02-14T21:14:48.053Z [V4L2:EZCAP GAME LIN] The video control requested for the grabber restart due to signal lost, but it's caused by signal detection. No restart.
2023-02-14T21:15:18.262Z [WEBSOCKET] (WebSocketClient.cpp:30) New connection from ::ffff:192.168.2.62
2023-02-14T21:15:18.262Z [WEBSOCKET] (JsonAPI.cpp:97) Client '::ffff:192.168.2.62' switch to HyperHDR instance 0
2023-02-14T21:15:18.404Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:192.168.2.62
2023-02-14T21:16:09.472Z [V4L2:EZCAP GAME LIN] Throws error nr: VIDIOC_DQBUF error. Video stream is probably broken. Refreshing list of the devices. error code 19, No such device
2023-02-14T21:16:09.473Z [V4L2:EZCAP GAME LIN] VIDIOC_STREAMOFF  error code  19, No such device
2023-02-14T21:16:09.475Z [V4L2:EZCAP GAME LIN] Stopped
2023-02-14T21:16:35.351Z [WEBSOCKET] (WebSocketClient.cpp:30) New connection from ::ffff:192.168.2.62
2023-02-14T21:16:35.351Z [WEBSOCKET] (JsonAPI.cpp:97) Client '::ffff:192.168.2.62' switch to HyperHDR instance 0
2023-02-14T21:16:35.481Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:192.168.2.62
2023-02-14T21:16:56.359Z [COMPONENTREG0] (ComponentRegister.cpp:57) Disable Hyperhdr, store current component states
2023-02-14T21:16:56.359Z [COMPONENTREG0] HyperHDR: disabled
2023-02-14T21:16:56.359Z [SMOOTHING0] Clearing queued colors before: disabling
2023-02-14T21:16:56.359Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:16:56.359Z [COMPONENTREG0] Smoothing: disabled
2023-02-14T21:16:56.359Z [COMPONENTREG0] Blackborder detector: disabled
2023-02-14T21:16:56.359Z [MUXER0] Removed source priority 240
2023-02-14T21:16:56.359Z [COMPONENTREG0] Video capture device: disabled
2023-02-14T21:16:56.366Z [WEBSOCKET] (JsonAPI.cpp:1259) log streaming deactivated for client  ::ffff:192.168.2.62
2023-02-14T21:17:03.852Z [COMPONENTREG0] (ComponentRegister.cpp:74) Enable Hyperhdr, recover previous component states
2023-02-14T21:17:03.852Z [COMPONENTREG0] HyperHDR: enabled
2023-02-14T21:17:03.852Z [SMOOTHING0] Clearing queued colors before: enabling
2023-02-14T21:17:03.852Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:17:03.852Z [COMPONENTREG0] Smoothing: enabled
2023-02-14T21:17:03.852Z [COMPONENTREG0] Blackborder detector: enabled
2023-02-14T21:17:03.852Z [MUXER0] Register new input 'System/VIDEOGRABBER' with priority 240 as inactive
2023-02-14T21:17:03.852Z [COMPONENTREG0] Video capture device: enabled
2023-02-14T21:17:03.853Z [V4L2:EZCAP GAME LIN] Multithreading for V4L2 is enabled. Available thread's count 6
2023-02-14T21:17:04.056Z [V4L2:EZCAP GAME LIN] Found capture device: /dev/video1
2023-02-14T21:17:04.057Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:402) Device has 'brightness' control => min: -100, max: 100, default: 0
2023-02-14T21:17:04.057Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:408) Device has 'contrast' control => min: 50, max: 200, default: 100
2023-02-14T21:17:04.057Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:414) Device has 'saturation' control => min: 0, max: 200, default: 100
2023-02-14T21:17:04.058Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:420) Device has 'hue' control => min: -90, max: 90, default: 0
2023-02-14T21:17:04.058Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:506) /dev/video1 1920 x 1080 @ 30 fps NO_CHANGE (unsupported)
2023-02-14T21:17:04.058Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:506) /dev/video1 1280 x 720 @ 60 fps NO_CHANGE (unsupported)
2023-02-14T21:17:04.058Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:212) Searching for ezcap Game Link RAW: ezcap Game (video1) 1920 x 1080 @ 60 fps, input: -1 (yuyv)
2023-02-14T21:17:04.058Z [V4L2:EZCAP GAME LIN] *************************************************************************************************
2023-02-14T21:17:04.058Z [V4L2:EZCAP GAME LIN] Starting V4L2 grabber. Selected: ezcap Game Link RAW: ezcap Game (video1) [/dev/video1] 1920 x 1080 @ 60 fps yuyv
2023-02-14T21:17:04.058Z [V4L2:EZCAP GAME LIN] *************************************************************************************************
2023-02-14T21:17:04.059Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:819) Hardware cropping is not supported: ignoring
2023-02-14T21:17:04.059Z [V4L2:EZCAP GAME LIN] Set device input to: Camera 1
2023-02-14T21:17:04.059Z [V4L2:EZCAP GAME LIN] Set resolution to: 1920 x 1080
2023-02-14T21:17:04.060Z [V4L2:EZCAP GAME LIN] Set framerate to 60 FPS
2023-02-14T21:17:04.060Z [V4L2:EZCAP GAME LIN] Brightness set to: 0 (default)
2023-02-14T21:17:04.060Z [V4L2:EZCAP GAME LIN] Contrast set to: 100 (default)
2023-02-14T21:17:04.061Z [V4L2:EZCAP GAME LIN] Saturation set to: 100 (default)
2023-02-14T21:17:04.061Z [V4L2:EZCAP GAME LIN] Hue set to: 0 (default)
2023-02-14T21:17:04.061Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:105) LUT folder location: '/usr/share/hyperhdr/lut'
2023-02-14T21:17:04.061Z [V4L2:EZCAP GAME LIN] LUT file is not found here: /home/wouter/.hyperhdr/lut_lin_tables.3d
2023-02-14T21:17:04.061Z [V4L2:EZCAP GAME LIN] (Grabber.cpp:445) LUT file found: /usr/share/hyperhdr/lut/lut_lin_tables.3d
2023-02-14T21:17:04.061Z [V4L2:EZCAP GAME LIN] (Grabber.cpp:460) Index 2 for YUV
2023-02-14T21:17:04.077Z [V4L2:EZCAP GAME LIN] Found and loaded LUT: '/usr/share/hyperhdr/lut/lut_lin_tables.3d'
2023-02-14T21:17:04.077Z [V4L2:EZCAP GAME LIN] Video pixel format is set to: YUYV
2023-02-14T21:17:04.082Z [V4L2:EZCAP GAME LIN] Started
2023-02-14T21:17:03.858Z [SMOOTHING0] Using linear smoothing procedure (0)
2023-02-14T21:17:04.947Z [MUXER0] Priority 240 is now active
2023-02-14T21:17:04.947Z [MUXER0] Set visible priority to 240
2023-02-14T21:17:04.947Z [HYPERHDR0] New priority[240], previous [255]
2023-02-14T21:17:04.947Z [HYPERHDR0] New source available -> switch LED-Device on
2023-02-14T21:17:04.947Z [SMOOTHING0] Clearing queued colors before: enabling
2023-02-14T21:17:04.948Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:17:04.948Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:102) Enable device
2023-02-14T21:17:04.948Z [LEDDEVICE_ADALIGHT] Opening UART: ttyACM0
2023-02-14T21:17:04.948Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:183) _rs232Port.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
2023-02-14T21:17:04.974Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:188) portName:          ttyACM0
2023-02-14T21:17:04.974Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:189) systemLocation:    /dev/ttyACM0
2023-02-14T21:17:04.974Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:190) description:       USB Single Serial
2023-02-14T21:17:04.974Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:191) manufacturer:      1a86
2023-02-14T21:17:04.974Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:192) productIdentifier: 0x55d4
2023-02-14T21:17:04.975Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:193) vendorIdentifier:  0x1a86
2023-02-14T21:17:04.975Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:194) serialNumber:      5299007073
2023-02-14T21:17:04.975Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:329) Switch on
2023-02-14T21:17:04.975Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:405) Power On
2023-02-14T21:17:04.975Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:191) Starting timer with interval = 7ms
2023-02-14T21:17:04.976Z [COMPONENTREG0] LED device: enabled
2023-02-14T21:17:04.976Z [SMOOTHING0] Using linear smoothing input (0)
2023-02-14T21:17:04.976Z [SMOOTHING0] Using linear smoothing procedure (0)
2023-02-14T21:17:06.557Z [WEBSOCKET] (WebSocketClient.cpp:201) send close: 1000
2023-02-14T21:17:06.741Z [WEBSOCKET] (WebSocketClient.cpp:30) New connection from ::ffff:192.168.2.62
2023-02-14T21:17:06.741Z [WEBSOCKET] (JsonAPI.cpp:97) Client '::ffff:192.168.2.62' switch to HyperHDR instance 0
2023-02-14T21:17:54.200Z [COMPONENTREG0] (ComponentRegister.cpp:57) Disable Hyperhdr, store current component states
2023-02-14T21:17:54.200Z [COMPONENTREG0] HyperHDR: disabled
2023-02-14T21:17:54.200Z [SMOOTHING0] Clearing queued colors before: disabling
2023-02-14T21:17:54.200Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:17:54.200Z [COMPONENTREG0] Smoothing: disabled
2023-02-14T21:17:54.200Z [COMPONENTREG0] Blackborder detector: disabled
2023-02-14T21:17:54.200Z [MUXER0] Removed source priority 240
2023-02-14T21:17:54.200Z [MUXER0] Set visible priority to 255
2023-02-14T21:17:54.200Z [HYPERHDR0] New priority[255], previous [240]
2023-02-14T21:17:54.200Z [HYPERHDR0] No source left -> switch LED-Device off
2023-02-14T21:17:54.201Z [SMOOTHING0] Clearing queued colors before: disabling
2023-02-14T21:17:54.201Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:17:54.201Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:138) Disable device
2023-02-14T21:17:54.201Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:205) Stopping timer
2023-02-14T21:17:54.201Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:355) Switch off
2023-02-14T21:17:54.201Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:313) Set LED strip to black/power off
2023-02-14T21:17:54.205Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:123) Flush was successful
2023-02-14T21:17:54.205Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:136) Close UART: ttyACM0
2023-02-14T21:17:54.406Z [COMPONENTREG0] Video capture device: disabled
2023-02-14T21:17:54.413Z [V4L2:EZCAP GAME LIN] Stopped
2023-02-14T21:17:54.407Z [SMOOTHING0] Clearing queued colors before: disabling
2023-02-14T21:17:54.407Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:17:54.407Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:138) Disable device
2023-02-14T21:17:54.407Z [COMPONENTREG0] LED device: disabled
2023-02-14T21:17:56.285Z [COMPONENTREG0] (ComponentRegister.cpp:74) Enable Hyperhdr, recover previous component states
2023-02-14T21:17:56.285Z [COMPONENTREG0] HyperHDR: enabled
2023-02-14T21:17:56.285Z [SMOOTHING0] Clearing queued colors before: enabling
2023-02-14T21:17:56.285Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:17:56.285Z [COMPONENTREG0] Smoothing: enabled
2023-02-14T21:17:56.285Z [COMPONENTREG0] Blackborder detector: enabled
2023-02-14T21:17:56.285Z [MUXER0] Register new input 'System/VIDEOGRABBER' with priority 240 as inactive
2023-02-14T21:17:56.285Z [COMPONENTREG0] Video capture device: enabled
2023-02-14T21:17:56.285Z [V4L2:EZCAP GAME LIN] Multithreading for V4L2 is enabled. Available thread's count 6
2023-02-14T21:17:56.286Z [V4L2:EZCAP GAME LIN] Found capture device: /dev/video1
2023-02-14T21:17:56.286Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:402) Device has 'brightness' control => min: -100, max: 100, default: 0
2023-02-14T21:17:56.286Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:408) Device has 'contrast' control => min: 50, max: 200, default: 100
2023-02-14T21:17:56.286Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:414) Device has 'saturation' control => min: 0, max: 200, default: 100
2023-02-14T21:17:56.286Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:420) Device has 'hue' control => min: -90, max: 90, default: 0
2023-02-14T21:17:56.287Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:506) /dev/video1 1920 x 1080 @ 30 fps NO_CHANGE (unsupported)
2023-02-14T21:17:56.287Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:506) /dev/video1 1280 x 720 @ 60 fps NO_CHANGE (unsupported)
2023-02-14T21:17:56.287Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:212) Searching for ezcap Game Link RAW: ezcap Game (video1) 1920 x 1080 @ 60 fps, input: -1 (yuyv)
2023-02-14T21:17:56.287Z [V4L2:EZCAP GAME LIN] *************************************************************************************************
2023-02-14T21:17:56.288Z [V4L2:EZCAP GAME LIN] Starting V4L2 grabber. Selected: ezcap Game Link RAW: ezcap Game (video1) [/dev/video1] 1920 x 1080 @ 60 fps yuyv
2023-02-14T21:17:56.288Z [V4L2:EZCAP GAME LIN] *************************************************************************************************
2023-02-14T21:17:56.288Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:819) Hardware cropping is not supported: ignoring
2023-02-14T21:17:56.288Z [V4L2:EZCAP GAME LIN] Set device input to: Camera 1
2023-02-14T21:17:56.289Z [V4L2:EZCAP GAME LIN] Set resolution to: 1920 x 1080
2023-02-14T21:17:56.290Z [V4L2:EZCAP GAME LIN] Set framerate to 60 FPS
2023-02-14T21:17:56.290Z [V4L2:EZCAP GAME LIN] Brightness set to: 0 (default)
2023-02-14T21:17:56.291Z [V4L2:EZCAP GAME LIN] Contrast set to: 100 (default)
2023-02-14T21:17:56.291Z [V4L2:EZCAP GAME LIN] Saturation set to: 100 (default)
2023-02-14T21:17:56.291Z [V4L2:EZCAP GAME LIN] Hue set to: 0 (default)
2023-02-14T21:17:56.292Z [V4L2:EZCAP GAME LIN] (V4L2Grabber.cpp:105) LUT folder location: '/usr/share/hyperhdr/lut'
2023-02-14T21:17:56.292Z [V4L2:EZCAP GAME LIN] LUT file is not found here: /home/wouter/.hyperhdr/lut_lin_tables.3d
2023-02-14T21:17:56.292Z [V4L2:EZCAP GAME LIN] (Grabber.cpp:445) LUT file found: /usr/share/hyperhdr/lut/lut_lin_tables.3d
2023-02-14T21:17:56.292Z [V4L2:EZCAP GAME LIN] (Grabber.cpp:460) Index 2 for YUV
2023-02-14T21:17:56.324Z [V4L2:EZCAP GAME LIN] Found and loaded LUT: '/usr/share/hyperhdr/lut/lut_lin_tables.3d'
2023-02-14T21:17:56.324Z [V4L2:EZCAP GAME LIN] Video pixel format is set to: YUYV
2023-02-14T21:17:56.333Z [V4L2:EZCAP GAME LIN] Started
2023-02-14T21:17:56.285Z [SMOOTHING0] Clearing queued colors before: enabling
2023-02-14T21:17:56.285Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:17:56.286Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:102) Enable device
2023-02-14T21:17:56.286Z [LEDDEVICE_ADALIGHT] Opening UART: ttyACM0
2023-02-14T21:17:56.286Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:183) _rs232Port.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
2023-02-14T21:17:56.312Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:188) portName:          ttyACM0
2023-02-14T21:17:56.312Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:189) systemLocation:    /dev/ttyACM0
2023-02-14T21:17:56.313Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:190) description:       USB Single Serial
2023-02-14T21:17:56.313Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:191) manufacturer:      1a86
2023-02-14T21:17:56.313Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:192) productIdentifier: 0x55d4
2023-02-14T21:17:56.313Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:193) vendorIdentifier:  0x1a86
2023-02-14T21:17:56.313Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:194) serialNumber:      5299007073
2023-02-14T21:17:56.313Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:329) Switch on
2023-02-14T21:17:56.313Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:405) Power On
2023-02-14T21:17:56.313Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:191) Starting timer with interval = 7ms
2023-02-14T21:17:56.314Z [COMPONENTREG0] LED device: enabled
2023-02-14T21:17:56.314Z [SMOOTHING0] Using linear smoothing input (0)
2023-02-14T21:17:56.314Z [SMOOTHING0] Using linear smoothing procedure (0)
2023-02-14T21:17:56.333Z [V4L2:EZCAP GAME LIN] Frame too small: 0 != 4147200
2023-02-14T21:17:56.334Z [V4L2:EZCAP GAME LIN] Frame too small: 0 != 4147200
2023-02-14T21:17:57.198Z [MUXER0] Priority 240 is now active
2023-02-14T21:17:57.198Z [MUXER0] Set visible priority to 240
2023-02-14T21:17:57.198Z [HYPERHDR0] New priority[240], previous [255]
2023-02-14T21:17:57.198Z [HYPERHDR0] New source available -> switch LED-Device on
2023-02-14T21:17:57.198Z [SMOOTHING0] Clearing queued colors before: enabling
2023-02-14T21:17:57.198Z [SMOOTHING0] Smoothing queue is cleared
2023-02-14T21:17:57.198Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:102) Enable device
2023-02-14T21:17:57.199Z [SMOOTHING0] Using linear smoothing input (0)
2023-02-14T21:17:57.203Z [SMOOTHING0] Using linear smoothing procedure (0)
2023-02-14T21:18:00.883Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:192.168.2.62
2023-02-14T21:18:19.497Z [IMAGETOLED0] Total index number is: 43264 (memory: 43264). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:18:30.863Z [IMAGETOLED0] Total index number is: 42800 (memory: 42800). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:18:32.464Z [IMAGETOLED0] Total index number is: 57248 (memory: 57248). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:19:06.531Z [IMAGETOLED0] Total index number is: 48930 (memory: 48930). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:19:09.000Z [IMAGETOLED0] Total index number is: 57248 (memory: 57248). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:19:20.024Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1801, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:20:20.021Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 6ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:20:37.890Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:20:45.556Z [IMAGETOLED0] Total index number is: 43032 (memory: 43032). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:20:51.890Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:20:57.956Z [IMAGETOLED0] Total index number is: 57248 (memory: 57248). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:21:20.031Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1801], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:22:20.021Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 8ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:23:20.021Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 7ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:24:20.011Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:24:34.411Z [IMAGETOLED0] Total index number is: 43032 (memory: 43032). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:24:41.878Z [IMAGETOLED0] Total index number is: 43496 (memory: 43496). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:24:57.479Z [IMAGETOLED0] Total index number is: 43496 (memory: 43496). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:25:00.423Z [IMAGETOLED0] Total index number is: 43612 (memory: 43612). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:25:02.475Z [IMAGETOLED0] Total index number is: 57248 (memory: 57248). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:25:20.009Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:26:20.012Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:26:42.244Z [WEBSOCKET] (WebSocketClient.cpp:30) New connection from ::ffff:192.168.2.62
2023-02-14T21:26:42.245Z [WEBSOCKET] (JsonAPI.cpp:97) Client '::ffff:192.168.2.62' switch to HyperHDR instance 0
2023-02-14T21:26:42.468Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:192.168.2.62
2023-02-14T21:26:49.807Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:26:57.003Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:27:20.007Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:27:22.538Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:27:26.301Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:27:27.572Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:27:30.101Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:27:32.872Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:27:34.973Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:27:51.838Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:27:54.405Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:28:19.998Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 6ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:28:57.296Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:28:59.429Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:29:20.025Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1801, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8572, processed = 12001, dropped = 0]
2023-02-14T21:30:20.021Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8570, processed = 11999, dropped = 0]
2023-02-14T21:30:54.759Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:30:58.126Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:31:08.955Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:31:14.359Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:31:17.891Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:31:19.259Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:31:20.026Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1801], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:31:47.354Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:31:49.925Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:01.556Z [IMAGETOLED0] Total index number is: 42788 (memory: 42788). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:03.286Z [IMAGETOLED0] Total index number is: 43136 (memory: 43136). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:04.389Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:07.722Z [IMAGETOLED0] Total index number is: 31888 (memory: 31888). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:14.056Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:20.019Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:32:29.120Z [IMAGETOLED0] Total index number is: 43264 (memory: 43264). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:33.154Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:35.983Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:42.338Z [WEBSOCKET] (WebSocketClient.cpp:30) New connection from ::ffff:192.168.2.62
2023-02-14T21:32:42.339Z [WEBSOCKET] (JsonAPI.cpp:97) Client '::ffff:192.168.2.62' switch to HyperHDR instance 0
2023-02-14T21:32:42.475Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:192.168.2.62
2023-02-14T21:32:42.621Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:55.715Z [IMAGETOLED0] Total index number is: 42916 (memory: 42916). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:32:57.486Z [IMAGETOLED0] Total index number is: 43264 (memory: 43264). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:33:12.286Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:33:20.015Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 5ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.87, send = 8572, processed = 12000, dropped = 0]
2023-02-14T21:33:32.317Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:33:35.317Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:33:45.079Z [IMAGETOLED0] Total index number is: 43252 (memory: 43252). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:34:20.015Z [PERFORMANCE] [USB capturing: FPS = 30.00, decoding = 4ms, frames = 1800, invalid = 0], [INSTANCE0: FPS = 30.00, processed = 1800], [LED0: FPS = 142.85, send = 8571, processed = 12000, dropped = 0]
2023-02-14T21:34:44.881Z [IMAGETOLED0] Total index number is: 41024 (memory: 41024). User sparse processing is: disabled, image size: 960 x 540, area number: 104
2023-02-14T21:34:49.909Z [IMAGETOLED0] Total index number is: 43380 (memory: 43380). User sparse processing is: disabled, image size: 960 x 540, area number: 104

they are completely unreadable so useless

post it on pastebin.com

https://pastebin.com/jgyTA0ZX

Still lines are broken. But to answer your question and finish this topic: the messages you posted are not HyperHDR errors but diagnostic messages and frame size of zero is send by the grabber not us (usually it happens during grabber initialization but later it should work fine)

Where is the manual to get a correct log?

Managed to dig something:

2023-02-14T21:16:09.472Z [V4L2:EZCAP GAME LIN] Throws error nr: VIDIOC_DQBUF error. Video stream is probably broken. Refreshing list of the devices. error code 19, No such device
2023-02-14T21:16:09.473Z [V4L2:EZCAP GAME LIN] VIDIOC_STREAMOFF error code 19, No such device

And that's the error you missed. Definitely not HyperHDR issue but your USB grabber hardware issue..maybe voltage problem or something else. I stop here.

repo: awawa-dev/HyperHDR


text:
Some more tests for CheckoutSelectionView. Test for OrderConfirmView, and a bit of cleanup.

I added a test case for the OrderConfirmView, which had no tests, and two addition test cases for the CheckoutSelectionView. One tests that the order info is saved on the session if there is no user. The other tests the save_extra_info_to_order method.
While I was there I renamed ShippingBillingViewTestCase to CheckoutSelectionViewTestCase - the name of the view being tested. Also got two typos in comments in shop/views/checkout.py
shop/tests/views_checkout.py still needs a bit of reorganization, which I would like to get around to later.

This looks great, but unfortunately, it is outdated because django-shop has changed heavily in the meantime. I am closing this. Thank you, @evandempsey.

source: gharchive/pull-request

authors: evandempsey rfleschenberg

repo: awesto/django-shop

license_type: permissive

license_source: bigquery


text:
Get Involved - Page

As a user,
I need access to a "Get Involved" page,
So that I can learn about ways to participate and contribute as a volunteer or supporter.
Acceptance Criteria
Given that I am a user interested in getting involved
When I navigate to the "Get Involved" page
Then I should see information about volunteering opportunities, support options, and ways to contribute

This issue has also been addressed in thar commit: 80fc530b9e1a6b6e0becbf52f21f7af958e40e22

source: gharchive/issue

repo: awishto-write/GCISL

license: MIT

license_source: github-api


text:
Allow configurable update interval and backoff

In #28 an issue was encountered with exceeding API rate limits. This was attended to with PR #29 where the update query interval was increased to 30s, and handling was added for rate exceeded error.
30s interval also has the effect of adding a 0-30s overhead to each action, depending on when the CodeBuild job happens to complete. For some use cases this overhead can be quite noticeable and unnecessary. E.g. for a singular/small group of short CodeBuild build(s), where we have little danger of hitting the rate-limiting. Some use-cases may also involve running CodeBuild builds in sequence, where this overhead is multiplied by the number of sequenced builds.
Offering a way to configure the update interval and backoff, rather than have them hard-coded as they are now, allows for a more fine-grained way to tune the API call rate to fit the use-case. This makes it possible to limit the unnecessary time overhead involved and enable a faster turn-around time. The current values could be kept as default.

Is there anymore news on this one if configurable interval and backoff is in the future?

Is there anymore news on this one if configurable interval and backoff is in the future?

The CI run for #76 was approved after I had already moved on from a client, so I didn't see what happened with the CI run and do not have access to that account anymore. Apparently there was some error in CI run but alas those logs are long lost now. The codebase has seen very few changes so I created #77 with the same changes on top of the current master-branch here 👍🏻  Hoping that it will chug along a bit more swimmingly 🤞🏻

This can be closed, as the implementation was merged in #116 and released with v1.0.8.

repo: aws-actions/aws-codebuild-run-build


text:
GraphQL Subscription throws error "Validation error of type UndefinedVariable: variable not found"

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
React
Amplify APIs
Authentication, GraphQL API
Amplify Categories
auth, api
Environment information

# Put output below this line

❯ npx envinfo --system --binaries --browsers --npmPackages --duplicates --npmGlobalPackages

  System:
    OS: macOS 11.6.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 259.09 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.16.0 - ~/.nvm/versions/node/v14.16.0/bin/node
    Yarn: 1.22.11 - ~/.nvm/versions/node/v14.16.0/bin/yarn
    npm: 7.19.1 - ~/.nvm/versions/node/v14.16.0/bin/npm
  Browsers:
    Chrome: 96.0.4664.93
    Firefox: 94.0.2
    Safari: 15.1
  npmPackages:
    @aws-amplify/ui-react: ^2.1.3 => 2.1.3
    @aws-amplify/ui-react-internal:  undefined ()
    @aws-amplify/ui-react-legacy:  undefined ()
    @craco/craco: ^6.4.2 => 6.4.2
    @testing-library/jest-dom: ^5.11.4 => 5.16.1
    @testing-library/react: ^11.1.0 => 11.2.7
    @testing-library/user-event: ^12.1.10 => 12.8.3
    @types/jest: ^26.0.15 => 26.0.24
    @types/lodash: ^4.14.178 => 4.14.178
    @types/node: ^12.0.0 => 12.20.37
    @types/react: ^17.0.0 => 17.0.37
    @types/react-dom: ^17.0.0 => 17.0.11
    aws-amplify: ^4.3.10 => 4.3.10
    lodash: ^4.17.21 => 4.17.21
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    react-scripts: 4.0.3 => 4.0.3
    typescript: ^4.1.2 => 4.5.2
    web-vitals: ^1.0.1 => 1.1.2
  npmGlobalPackages:
    @aws-amplify/cli: 7.6.2
    create-next-app: 11.1.2
    npm: 7.19.1
    typescript: 4.3.5
    yarn: 1.22.11

Describe the bug
When trying to retrieve data via GQL Subscription, I'm getting the following errors (which prevents the subscription from working):
"Connection failed: {"errors":[{"message":"Validation error of type UndefinedVariable: variable not found"}]}"

Expected behavior
Using GraphQL Subscription should run and retrieve data successfully without throwing this error
Reproduction steps

Run project locally via npm start
Attempt to retrieve data via GraphQL Subscription
Open Console Logs in browser
Notice that an error is thrown in AWSAppSyncRealTimeProvider.js with the error message: "Connection failed: {"errors":[{"message":"Validation error of type UndefinedVariable: variable not found"}]}"

Code Snippet
I've created a repo with Create React App and some basic scaffolding to log in, create blog/post/comment, and retrieve the data through subscription.
https://github.com/ngnathan/amplifytest
This issue happens running locally via npm start.
	useEffect(() => {
		const subscription = API.graphql(graphqlOperation(subscriptions.onCreateBlog))
			// @ts-ignore
			.subscribe({
				next: ({ provider, value }: any) => console.log({ provider, value }),
				error: (error: any) => console.warn(error)
			});
		return () => {
			subscription.unsubscribe();
		};
	}, []);

Log output

// Put your logs below this line
log.js:24 [HMR] Waiting for update signal from WDS...
App.tsx:155 user null
ConsoleLogger.ts:125 [DEBUG] 51:36.81 PubSub - subscribe options {provider: Symbol(INTERNAL_AWS_APPSYNC_REALTIME_PUBSUB_PROVIDER), appSyncGraphqlEndpoint: 'https://123.appsync-api.us-east-1.amazonaws.com/graphql', authenticationType: 'AMAZON_COGNITO_USER_POOLS', apiKey: undefined, query: 'subscription OnCreateBlog($owner: String) {\n  onCr…   }\n    createdAt\n    updatedAt\n    owner\n  }\n}\n', …}
ConsoleLogger.ts:115 [DEBUG] 51:36.83 AuthClass - Getting current session
ConsoleLogger.ts:115 [DEBUG] 51:36.85 AuthClass - getting current authenticated user
ConsoleLogger.ts:115 [DEBUG] 51:36.91 AuthClass - get current authenticated userpool user
ConsoleLogger.ts:115 [DEBUG] 51:36.98 AuthClass - get current authenticated userpool user
ConsoleLogger.ts:125 [DEBUG] 51:36.99 AuthClass - Getting the session from this user: CognitoUser {username: '123', pool: CognitoUserPool, Session: null, client: Client, signInUserSession: CognitoUserSession, …}
ConsoleLogger.ts:125 [DEBUG] 51:36.99 AuthClass - Succeed to get the user session CognitoUserSession {idToken: CognitoIdToken, refreshToken: CognitoRefreshToken, accessToken: CognitoAccessToken, clockDrift: 0}
ConsoleLogger.ts:115 [DEBUG] 51:36.106 AuthClass - Getting current session
ConsoleLogger.ts:125 [DEBUG] 51:36.107 AuthClass - Getting the session from this user: CognitoUser {username: '123', pool: CognitoUserPool, Session: null, client: Client, signInUserSession: CognitoUserSession, …}
ConsoleLogger.ts:125 [DEBUG] 51:36.107 AuthClass - Succeed to get the user session CognitoUserSession {idToken: CognitoIdToken, refreshToken: CognitoRefreshToken, accessToken: CognitoAccessToken, clockDrift: 0}
ConsoleLogger.ts:125 [DEBUG] 51:36.109 AuthClass - Getting the session from this user: CognitoUser {username: '123', pool: CognitoUserPool, Session: null, client: Client, signInUserSession: CognitoUserSession, …}
ConsoleLogger.ts:125 [DEBUG] 51:36.109 AuthClass - Succeed to get the user session CognitoUserSession {idToken: CognitoIdToken, refreshToken: CognitoRefreshToken, accessToken: CognitoAccessToken, clockDrift: 0}
ConsoleLogger.ts:115 [DEBUG] 51:36.111 AWSAppSyncRealTimeProvider - Initializaling retryable Handshake
ConsoleLogger.ts:115 [DEBUG] 51:36.111 Util - bound  attempt aws-amplify/amplify-js#1 with this vars: [{"awsRealTimeUrl":"wss://123.appsync-realtime-api.us-east-1.amazonaws.com/graphql?header=123&payload=e30="}]
ConsoleLogger.ts:115 [DEBUG] 51:36.112 AWSAppSyncRealTimeProvider - Initializing handshake wss://123.appsync-realtime-api.us-east-1.amazonaws.com/graphql?header=123&payload=e30=
webpackHotDevClient.js:138 src/App.tsx
  Line 35:16:  'setBlogs' is assigned a value but never used     @typescript-eslint/no-unused-vars
  Line 36:16:  'setPosts' is assigned a value but never used     @typescript-eslint/no-unused-vars
  Line 37:19:  'setComments' is assigned a value but never used  @typescript-eslint/no-unused-vars
printWarnings @ webpackHotDevClient.js:138
handleWarnings @ webpackHotDevClient.js:143
push../node_modules/react-dev-utils/webpackHotDevClient.js.connection.onmessage @ webpackHotDevClient.js:210
ConsoleLogger.ts:115 [DEBUG] 51:36.300 AuthClass - getting current credentials
ConsoleLogger.ts:115 [DEBUG] 51:36.300 Credentials - getting credentials
ConsoleLogger.ts:115 [DEBUG] 51:36.300 Credentials - picking up credentials
ConsoleLogger.ts:115 [DEBUG] 51:36.300 Credentials - getting new cred promise
ConsoleLogger.ts:115 [DEBUG] 51:36.301 Credentials - checking if credentials exists and not expired
ConsoleLogger.ts:115 [DEBUG] 51:36.301 Credentials - need to get a new credential or refresh the existing one
ConsoleLogger.ts:115 [DEBUG] 51:36.301 Credentials - no credentials for expiration check
ConsoleLogger.ts:115 [DEBUG] 51:36.301 AuthClass - Getting current user credentials
ConsoleLogger.ts:115 [DEBUG] 51:36.302 AuthClass - Getting current session
ConsoleLogger.ts:125 [DEBUG] 51:36.302 AuthClass - Getting the session from this user: CognitoUser {username: '123', pool: CognitoUserPool, Session: null, client: Client, signInUserSession: CognitoUserSession, …}
ConsoleLogger.ts:125 [DEBUG] 51:36.302 AuthClass - Succeed to get the user session CognitoUserSession {idToken: CognitoIdToken, refreshToken: CognitoRefreshToken, accessToken: CognitoAccessToken, clockDrift: 0}
ConsoleLogger.ts:125 [DEBUG] 51:36.303 AuthClass - getting session success CognitoUserSession {idToken: CognitoIdToken, refreshToken: CognitoRefreshToken, accessToken: CognitoAccessToken, clockDrift: 0}
ConsoleLogger.ts:115 [DEBUG] 51:36.303 Credentials - set credentials from session
ConsoleLogger.ts:115 [DEBUG] 51:36.407 AWSAppSyncRealTimeProvider - subscription message from AWS AppSyncRealTime: {"type":"connection_ack","payload":{"connectionTimeoutMs":300000}}
ConsoleLogger.ts:115 [DEBUG] 51:36.408 AWSAppSyncRealTimeProvider - Notifying connection successful
ConsoleLogger.ts:115 [DEBUG] 51:36.408 AWSAppSyncRealTimeProvider - subscription message from AWS AppSync RealTime: {"type":"ka"}
ConsoleLogger.ts:118 [DEBUG] 51:36.409 AWSAppSyncRealTimeProvider {id: '', observer: null, query: '', variables: {…}}id: ""observer: nullquery: ""variables: {}[[Prototype]]: Object[[Prototype]]: Object
ConsoleLogger.ts:115 [DEBUG] 51:36.501 AWSAppSyncRealTimeProvider - subscription message from AWS AppSync RealTime: {"id":"234","type":"error","payload":{"errors":[{"message":"Validation error of type UndefinedVariable: variable not found"}]}}
ConsoleLogger.ts:118 [DEBUG] 51:36.501 AWSAppSyncRealTimeProvider {id: '234', observer: SubscriptionObserver, query: 'subscription OnCreateBlog($owner: String) {\n  onCr…   }\n    createdAt\n    updatedAt\n    owner\n  }\n}\n', variables: {…}}
App.tsx:72 {provider: AWSAppSyncRealTimeProvider, error: {…}}error: errors: Array(1)0: {message: 'Connection failed: {"errors":[{"message":"Validati…of type UndefinedVariable: variable not found"}]}'}length: 1[[Prototype]]: Array(0)[[Prototype]]: Objectprovider: AWSAppSyncRealTimeProvider {_config: {…}, socketStatus: 0, keepAliveTimeout: 300000, subscriptionObserverMap: Map(0), promiseArray: Array(0), …}[[Prototype]]: Object
error @ App.tsx:72
notifySubscription @ Observable.js:140
onNotify @ Observable.js:179
error @ Observable.js:240
error @ PubSub.ts:186
notifySubscription @ Observable.js:140
onNotify @ Observable.js:179
error @ Observable.js:240
AWSAppSyncRealTimeProvider._handleIncomingSubscriptionMessage @ AWSAppSyncRealTimeProvider.ts:517
ConsoleLogger.ts:115 [DEBUG] 51:36.504 AWSAppSyncRealTimeProvider - Error while unsubscribing Error: Subscription never connected
ConsoleLogger.ts:125 [DEBUG] 51:36.573 Credentials - Load credentials successfully {accessKeyId: 'accessKeyId', secretAccessKey: 'secretAccessKey', sessionToken: 'sessionToken', expiration: Wed Dec 08 2021 23:51:36 GMT-0500 (Eastern Standard Time), identityId: 'us-east-1:123'}
AuthContext.tsx:157 user {id: '123', email: 'email@email.com', isVerified: true}
ConsoleLogger.ts:115 [DEBUG] 51:37.504 AWSAppSyncRealTimeProvider - closing WebSocket...

aws-exports.js
const awsmobile = {
"aws_project_region": "us-east-1",
"aws_appsync_graphqlEndpoint": "https://123.appsync-api.us-east-1.amazonaws.com/graphql",
"aws_appsync_region": "us-east-1",
"aws_appsync_authenticationType": "AMAZON_COGNITO_USER_POOLS",
"aws_cognito_identity_pool_id": "us-east-1:234",
"aws_cognito_region": "us-east-1",
"aws_user_pools_id": "us-east-1_abc",
"aws_user_pools_web_client_id": "def",
"oauth": {},
"aws_cognito_username_attributes": [
"EMAIL"
],
"aws_cognito_social_providers": [],
"aws_cognito_signup_attributes": [
"EMAIL"
],
"aws_cognito_mfa_configuration": "OFF",
"aws_cognito_mfa_types": [
"SMS"
],
"aws_cognito_password_protection_settings": {
"passwordPolicyMinLength": 8,
"passwordPolicyCharacters": []
},
"aws_cognito_verification_mechanisms": [
"EMAIL"
]
};
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
Chrome
Mobile Browser Version
96
Additional information and screenshots
I've created a repo with Create React App and some basic scaffolding to log in, create blog/post/comment, and retrieve the data through subscription.
https://github.com/ngnathan/amplifytest

Any updates on this?

Please fix :)

Also having exactly the same issue here, created both react and angular project following the documentation, and always get this error when trying to use subscription

+1

A workaround I have is to downgrade Amplify CLI from 9.2.1 to 9.1.0, change schema.graphql for the CLI to recognize the change, amplify push, then re-test.

Hey guys! I had the same problem, my solution was to change my subscription from this:

to this:

Basically remove the $filter: parameter
Also if you are using React try removing the subscription.unsubscribe();
for example:
React.useEffect(() => {
  const subscription = API.graphql(
    graphqlOperation(subscriptions.onCreateTodo)
  ).subscribe({
    next: ({ provider, value }) => console.log({ provider, value }),
    error: (error) => console.warn(error),
  });

  // by removing this line the error goes away, the downside is that we never unsubscribe :/
  // subscription.unsubscribe();
}, []);

I hope this can help someone 👍

This issue has been resolved. An update has been made in AppSync to allow optional subscription arguments into the top-level graphql query object.
I've just verified in a local project in us-west-2.

authors: CrystalCastles alharris-at betomoedano diegosarmentero37 hidrogenos ngnathan reneonguitar truuth-of-abhi

repo: aws-amplify/amplify-category-api


text:
Mutations break after aws-amplify/cli update: "input contains a field that is not defined"

How did you install the Amplify CLI?
npm install -g @aws-amplify/cli@12.10.1
If applicable, what version of Node.js are you using?
21.7.1
Amplify CLI Version
12.10.1
GraphQL transformer version: 2
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
After upgrading from @aws-amplify/cli@12.0.0 to @aws-amplify/cli@12.10.1 I am unable to do any mutations. All of them return the error: "The variables input contains a field that is not defined for input object type 'DirListInput' "
Expected behavior
Carry out the mutation successfully without throwing an error as it did in @aws-amplify/cli@12.0.0
Reproduction steps
I am running a react app with "aws-amplify": "5.3.17"

(simplified) schema.graphql:

type DbDirTable @model(timestamps: { createdAt: "createdAt", updatedAt: "modifiedAt" }) {
  id: ID!
  createdAt: AWSDateTime!
  modifiedAt: AWSDateTime!
  dirList: [DirList!]!
  copiedFromId: String
}

type DirList {
  id: ID!
  items: [DirListItem!]!
  title: String
  colour: String
}

type DirListItem {
  id: ID!
  note: String
  visited: Boolean
}

After running amplify push --y it changed:

src/API.ts
src/graphql/mutations.ts
src/graphql/queries.ts
src/graphql/schema.json
src/graphql/subscriptions.ts

The difference in those files was that it added __typename to every type, input, mutation and query

Then I call

await API.graphql<GraphQLQuery<UpdateDbDirTableMutation>>(graphqlOperation(updateDbDirTable, { input: inputData }));

where  inputData is:
{
  {
    "id": "3894a81b-4e93-4627-aae1-0a0617a8ed75",
    "dirList": [
        {
            "id": "a9cb6ec9-0254-4d37-ac96-e25e46f50a42",
            "items": [],
            "title": "One",
            "colour": null,
        },
        {
            "id": "09701984-fe07-4140-b36a-c9ecd8ca0549",
            "items": [
                {
                    "id": "6535fb67-f55d-475c-b32d-065f5b26f4ee",
                    "note": null,
                    "visited": null,
                }
            ],
            "title": "Two",
            "colour": null,
        }
    ]
}

But it throws the error
[
    {
        "path": null,
        "locations": null,
        "message": "The variables input contains a field that is not defined for input object type 'DirListInput' "
    }
]

updateDbDirTable is auto-generated in src/graphql/mutations. I am not using any custom resolvers or overrides

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
If I discard changes in the graphql the code in step 3 works ok
If I downgrade to 12.0.0 and re-generate the graphql files the code in step 3 works ok
Same issue on 12.4.0 because it adds the same changes as 12.10.1 to the auto-generated graphql and API
I noticed that if I keep all of the regenerated changes and only discard the src/graphql/queries.ts then the code works ok
The only new change in src/graphql/queries.ts is that it added __typename everywhere.
This is strange since all my queries, when called directly, work fine with the newly generated file and they fetch the data ok.

Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hi @ok-martin, the changeset from 12.0.0 to 12.10.1 includes this codegen change which might have caused this. I've tried to reproduce this and noticed the typeName additions as well. However I have some questions:

I noticed that if I keep all of the regenerated changes and only discard the src/graphql/queries.ts then the code works ok

I am confused by this part since the types defined here are independent of the mutation that is failing for you. Do you happen to have a diff of mutations.ts that is generated? I see that in my repro, there is an additional diff seen below:

Hi @phani-srikar I am confused by that too.
Here is the diff on the mutation file:

Hey @ok-martin, Are you still experiencing this issue?

Hey 👋 , This issue is being closed due to inactivity. If you are still experiencing the same problem and need further assistance, please feel free to leave a comment. This will enable us to reopen the issue and provide you with the necessary support.

I am still experiencing the issue.
It seems that it only fails to update on objects that are already in the database. If I insert a new row and then try to update it, then it all works ok.
However, when I try to update a row that was already there (from version 12.0.0) then the update fails.

I can confirm that the problem occurs when updating records that have sub-fields that are missing __typename.
Is there a way to auto populate those sub-fields with __typename?

authors: AnilMaktala ok-martin phani-srikar


text:
amplify delete errors when project has been deleted from the AWS Console

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
10.5.1
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Yes, removed the Amplify app on console
Amplify Categories
Not applicable
Amplify Commands
delete
Describe the bug
Previously when a running amplify delete on a application where the amplify app has been deleted on AWS console, the CLI would remove the amplify folder after checking for stacks and application.
In the newer version of Amplify CLI, the application does the following
-> amplify delete
? Are you sure you want to continue? This CANNOT be undone. (This will delete all the environments of the project from the cloud and wipe out all the local files created by Amplify CLI) Yes
⠋ Deleting resources from the cloud. This will take a few minutes.
Deleting env: abc.

Deleting env: dev.
⠸ Deleting resources from the cloud. This will take a few minutes.Stack has already been deleted or does not exist
⠦ Deleting resources from the cloud. This will take a few minutes.App dooggmmyc7koy not found.
⠧ Deleting resources from the cloud. This will take a few minutes.Stack has already been deleted or does not exist
⠸ Deleting resources from the cloud. This will take a few minutes.App dooggmmyc7koy not found.
✖ Project delete failed.
🛑 Project delete failed.
App <App ID> not found.

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: 8e866bc3-263b-4215-bbea-6b251721c48a
✔ An unexpected error has occurred, opt in to send an error report to AWS Amplify with non-sensitive project configuration files. Confirm  (y/N) · no

The application recognizes the deleted app but fails to clean up.
on CLI version 10.0.0
amplify delete
? Are you sure you want to continue? This CANNOT be undone. (This will delete all the environments of the project from the cloud and wipe out all the local files created by Amplify CLI) Yes
- Deleting resources from the cloud. This will take a few minutes.
Deleting env: dev.
| Deleting resources from the cloud. This will take a few minutes.Unable to remove env: dev because deployment bucket amplify-testfullamp-dev-92940-deployment does not exist or has been deleted.
- Deleting resources from the cloud. This will take a few minutes.Stack has already been deleted or does not exist
/ Deleting resources from the cloud. This will take a few minutes.App dooggmmyc7koy not found.
√ Project already deleted in the cloud.
Project deleted locally.

Expected behavior
Remove amplify folder if not present and not invoke diagnose when not needed.
Reproduction steps

amplify init
delete app on console
amplify delete

GraphQL schema(s)

# Put schemas below this line

Project Identifier
8e866bc3-263b-4215-bbea-6b251721c48a
Log output

# Put your logs below this line

Additional information
No response

As a workaround, you can delete the amplify directory in your local project.

authors: GuiuMateu ykethan

repo: aws-amplify/amplify-cli


text:
deleted appsync data still being returned by amplify api call

** Which Category is your question related to? **
amplify api
** What AWS Services are you utilizing? **
appsync one-to-many sample with 1 added type: User
** Provide additional details e.g. code snippets **
amplfy version I'm using = 1.1.28
I am developing an Expo (React Native) app.
Inside my main <App /> component, inside componentDidMount, I perform the following:
const foundUser = await appsyncClient.query({
  query: gql(queries.getUserByOwner)
  variables: { owner: user_id },
});
if (!foundUser.data.getUserByOwner.items.length) {
  console.log('appsync user does not exist');
} else {
  console.log(`appsync user exists, dynamodb user.id = ${foundUser.data.getUserByOwner.items[0].id}`);
}

So now I've updated my schema.graphql and did amplify remove api + amplify push (i did it this way since simply pushing the updated schema lead to some errors, this happens quite often).
So all dynamodb tables were deleted and recreated, and are now thus empty. Still, the above code will return me a very old response. I am puzzled as to how this can happen as that dynamodb table + data was deleted, when looking in dynamodb in aws console, I can see all tables are empty!
Also restarting Expo on my phone etc. didn't resolve the problem.
Is there something I need to do to "flush" old data? or maybe some option to amplify to disable caching?

@klaop57 Can you run amplify console api to check the data-sources connected to your API? I'm wondering if this is the the data returned from the on-device/browser cache? Did you try clearing your local cahce?

@kaustavghosh06 thanks for your suggestions.
on-device cache
I've emptied expo cache by doing expo r -c as described here, still the same issue though.
connected Data Source
So I've ran amplify console api, and I end up at the appsync page, if I check the Data Sources, click on the User Table, I get a user table which is empty (which is expected since I amplify remove api followed by amplify add api).
caching issue on AWS side?
Also I've not worked on this during the last 2+ days so if it was a caching issue on AWS side it should by now have been gone, which it isn't.
Conclusion
I still have the same problem, I get a User table "user" returned, even though the dynamodb table is empty..
so the code I exec is:
const user_id = (await Auth.currentAuthenticatedUser()).attributes.sub;

const foundUser = await appsyncClient.query({
  query: gql(queries.getUserByOwner),
  variables: { owner: user_id },
});

@klaop57 Are you still able to get the data from your API?

So I managed to solve it by:

save the schema.graphql file of the api
amplify remove api
then renaming the query (since it was a queryField query)
amplify add api, pasting in the original schema from step 1 as schema
amplify push

what exactly was causing it is still a mystery to me

@klaop57 This seems like a momentary service issue. Please let me know if you're still seeing this.

@klaop57 I have the same problem. Could you please let e know what should I do?

I am having the exact same problem.

@JECamachoR did you try Datastore.clear() ?


text:
Status of Hosting category is always 'Create' when using CI/CD.

Describe the bug
Hosting category always have 'Create' status when using CI/CD configuration, no matter how many times you execute amplify push.
Additionally, ./amplify/backend/hosting directory only contains an 'amplifyhosting' empty directory.
Weirdly, Amplify CLI uses that directory to determine if hosting has been configured from CLI (If you delete the 'hosting' directory and execute amplify hosting update it will tell you that hosting has not been configured from CLI but from the Amplify console).
Amplify CLI Version
4.24.0
To Reproduce
amplify init
amplify hosting add
> Hosting with Amplify Console (Managed hosting with custom domains, Continuous deployment)
amplify push (at least two times)
Expected behavior
Hosting category to have 'No Change' status on successive amplify status or amplify push executions.
Screenshots

Desktop (please complete the following information):

OS: macOS 10.15.5
Node Version: 14.4.0

Additional context
None.

Additional note: Executing amplify pull when there is no changes other than Hosting will make the process hang on Fetching updates to backend environment: dev from the cloud.

This issue persists in v4.25. It disappeared for some time, after deleting and re-initializing my Amplify App, but now it has appeared again after adding a secondo backend environment from CLI. I also disconnected a branch and connected it again from the Amplify console, but I'am not sure of exactly when the issue appeared again.

Hi,
same here. For me it appears all the time.

+1 same as above. After too much time trying to resolve this, it must be a bug.
For now, will just treat 'create' on category hosting as meaning there is nothing to do.

Looks like the issue is that lastPushTimeStamp doesn't get set for category "hosting" with option "Hosting with Amplify Console" (i.e. in amplify/backend/amplify-meta.json).
This is presumably because there is nothing to be pushed via the CLI as this hosting option is managed directly in the Amplify Console web interface. Since there is no lastPushTimeStamp it is always considered as having never been pushed, therefore needing to be 'created'.
Probably need some special handling surrounding resources which require no 'push' such as in this case. While the lastPushTimeStamp could simply be set, this is a bit misleading where no change has been pushed. Probably better to track the plugin has no configuration required and provide the status accordingly (i.e. 'Not Applicable' or simply 'No Change').
Interestingly though, amplify/#current-cloud-backend/amplify-meta.json does contain a lastPushTimeStamp for hosting, and so there is inconsistency between the local and cloud configuration due to this.

I'm also seeing this issue. The empty amplify/backend/hosting/amplifyhosting is particularly problematic because it doesn't get recreated on fresh git clones. My temporary fix is to make it a file, since the check is an fs.exists.
rm -rf amplify/backend/hosting/amplifyhosting
touch amplify/backend/hosting/amplifyhosting

+1 same situation for me.
sometimes I resolved to do like
$ amplify pull --appId {appId} --envName {envName}

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html

? Do you want to use an AWS profile? Yes
? Please choose the profile you want to use {awsprofile}
Amplify AppID found: {appId}. Amplify App name is:{AmplifyAppName}
Backend environment prod found in Amplify Console app: {AmplifyAppName}
? Choose your default editor: Visual Studio Code
? Choose the type of app that you're building javascript
Please tell us about your project
? What javascript framework are you using react
? Source Directory Path:  src
? Distribution Directory Path: build
? Build Command:  npm run-script build
? Start Command: npm run-script start

? Do you plan on modifying this backend? Yes  # <-- look at this carefully. choose "Yes"

Successfully pulled backend environment {envName} from the cloud.
Run 'amplify pull' to sync upstream changes.

$ amplify status

Current Environment: {envName}

| Category | Resource name                        | Operation | Provider plugin   |
| -------- | ------------------------------------ | --------- | ----------------- |
| Hosting  | amplifyhosting                       | Create    |                   |
| Auth     | kendrabuttonhosting___               | No Change | awscloudformation |
| Function | kendrabuttonhosting____PreSignup     | No Change | awscloudformation |

after doing this,
$ amplify pull

Pre-pull status:

Current Environment: prod

| Category | Resource name                        | Operation | Provider plugin   |
| -------- | ------------------------------------ | --------- | ----------------- |
| Hosting  | amplifyhosting                       | Create    |                   |
| Auth     | kendrabuttonhosting___               | No Change | awscloudformation |
| Function | kendrabuttonhosting____PreSignup     | No Change | awscloudformation |

Local changes detected.
Pulling changes from the cloud will override your local changes.
? Are you sure you would like to continue? Yes
✔ Successfully pulled backend environment prod from the cloud.

Post-pull status:

Current Environment: {envName}

| Category | Resource name                        | Operation | Provider plugin   |
| -------- | ------------------------------------ | --------- | ----------------- |
| Hosting  | amplifyhosting                       | No Change |                   |
| Auth     | kendrabuttonhosting___               | No Change | awscloudformation |
| Function | kendrabuttonhosting____PreSignup     | No Change | awscloudformation |

but sometimes no luck.
Which point can I check this is "Create" Operation state or not? I have no clue!

If you went through these steps:
amplify add hosting -> Amplify Console -> Continuous deployment (Git-based deployments)
The CLI will open up the Amplify Console webpage, and you will connect to your Github project there, once that's done, come back to your  local dev terminal, and hit enter.
I'm not able to reproduce the issue with the latest CLI version though. If you somehow get into this situation, you can run amplify pull --restore to get synchronized and consistent amplify status report in your local environment.

authors: UnleashedMind cameronrr ernestostifano geoseong martinbiard mbecker


text:
chore: manual pr build script

Description of changes
Ability to kick off PR run manually.
yarn cloud-pr

Issue #, if available

Description of how you validated changes
$ yarn cloud-pr
What is your PR number ? 13070
Did you submit PR from fork (y/n)? y
PIN for sobkamil:
Press the button on your U2F token...
Successfully authenticated using u2f, session cookie saved in /Users/sobkamil/.midway/cookie
Successfully signed SSH public key /Users/sobkamil/.ssh/id_ecdsa.pub. The SSH certificate was saved in /Users/sobkamil/.ssh/id_ecdsa-cert.pub
2023/08/03 13:26:54 This profile appears to be ada managed, so there is no need to explicitly update.
2023/08/03 13:26:54 Your credentials will be pulled automatically, so you may continue on with your workflow.
https://us-east-1.console.aws.amazon.com/codesuite/codebuild/671107461633/projects/AmplifyCLI-PR-Testing/batch/AmplifyCLI-PR-Testing:732a33ba-6411-4937-93f7-2e6c2540b1de?region=us-east-1

Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #13070 (052e988) into dev (ec9a2ba) will increase coverage by 48.56%.
Report is 291 commits behind head on dev.
The diff coverage is 59.37%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##              dev   #13070       +/-   ##
===========================================
+ Coverage    0.00%   48.56%   +48.56%
===========================================
  Files        1296      848      -448
  Lines      149743    38131   -111612
  Branches     1296     7797     +6501
===========================================
+ Hits            0    18519    +18519
+ Misses     148447    18022   -130425
- Partials     1296     1590      +294

Files Changed
Coverage Δ

...rmation/auth-stack-builder/auth-stack-transform.ts
91.30% <0.00%> (+91.30%)
:arrow_up:

...tack-builder/auth-user-pool-group-stack-builder.ts
51.72% <ø> (+51.72%)
:arrow_up:

...h-stack-builder/user-pool-group-stack-transform.ts
94.59% <0.00%> (+94.59%)
:arrow_up:

.../src/provider-utils/awscloudformation/constants.ts
100.00% <ø> (+100.00%)
:arrow_up:

...e-walkthrough-types/awsCognito-user-input-types.ts
100.00% <ø> (+100.00%)
:arrow_up:

...vice-walkthrough-types/cognito-user-input-types.ts
100.00% <ø> (+100.00%)
:arrow_up:

...y-category-function/src/commands/function/build.ts
0.00% <0.00%> (ø)

...ify-category-function/src/events/prePushHandler.ts
33.33% <0.00%> (+33.33%)
:arrow_up:

...ider-utils/awscloudformation/utils/layerHelpers.ts
21.80% <0.00%> (+21.80%)
:arrow_up:

...er-utils/awscloudformation/utils/storeResources.ts
30.38% <ø> (+30.38%)
:arrow_up:

... and 57 more

... and 1244 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter sobolk


text:
Update 1.bug_report.yaml

Description of changes

add custom and override commands to multi-select

Issue #, if available

Description of how you validated changes
Checklist

[x] PR description included

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #8923 (8dbe295) into master (31f8dc6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8923   +/-   ##
=======================================
  Coverage   55.56%   55.56%
=======================================
  Files         873      873
  Lines       48788    48788
  Branches     9704     9704
=======================================
  Hits        27108    27108
  Misses      20803    20803
  Partials      877      877

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 31f8dc6...8dbe295. Read the comment docs.

authors: codecov-commenter siegerts


text:
fix: remove invalid breakpoints (#661)

ref pr661 merged back into feature branch
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #681 (c77b049) into tagged-release/forms-and-views (2118487) will increase coverage by 0.18%.
The diff coverage is 100.00%.

@@                        Coverage Diff                         @@
##           tagged-release/forms-and-views     #681      +/-   ##
==================================================================
+ Coverage                           91.16%   91.34%   +0.18%
==================================================================
  Files                                 100      100
  Lines                                3824     3825       +1
  Branches                             1059     1060       +1
==================================================================
+ Hits                                 3486     3494       +8
+ Misses                                317      310       -7
  Partials                               21       21

Impacted Files
Coverage Δ

packages/codegen-ui/lib/utils/breakpoint-utils.ts
100.00% <100.00%> (+63.63%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2118487...c77b049. Read the comment docs.

authors: SwaySway codecov-commenter

repo: aws-amplify/amplify-codegen-ui


text:
Amplify seems to add a large amount of delay to reverse proxy requests

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

Describe the bug
When not using Amplify (using separate nginx hosted react front end, my backend responds in 18.2 seconds for a large set of data.  When using Amplify for the exact same data, to the exact same backend, the response exceeds 30 seconds and of course Amplify kills the request and returns a 502.  What is amplify doing to extend this 18 second response past the 30 second mark.
Expected behavior
i expect an 18 second response, not a 12+ second delay.  This started out as #1171 to control the reverse proxy timeout, but if Amplify is going to add 12 seconds to everything then amplify will not be usable as a product.
Reproduction steps
Open our NOT amplify version and load the page. 18 seconds from nothing to done
Open our amplify version of the same page (same JS, same backend as above) more than 30s (and then the connection is 502'd)
Exact same backend URL used in both cases.  One is handled via nginx reverse proxy, one is handled by amplify.
Build Settings
[
    {
        "source": "/api/v3/<*>",
        "target": "elements-api.humanyze.com/api/v3/<*>",
        "status": "200",
        "condition": null
    },
    {
        "source": "/<*>",
        "target": "/index.html",
        "status": "404-200",
        "condition": null
    },
    {
        "source": "</^[^.]+$|\\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|ttf|map|json)$)([^.]+$)/>",
        "target": "/index.html",
        "status": "200",
        "condition": null
    }
]

This is the Amplify version of the API access
https://user-images.githubusercontent.com/18578897/113328420-e0198d80-92e1-11eb-854f-b9cd657744a8.mp4
This is the NON-Amplify version of the same API Access
https://user-images.githubusercontent.com/18578897/113334013-c596e280-92e8-11eb-807d-8eb64383be88.mp4

4 days and not even an acknowledgement of this show stopper :-(. I guess I should just give up on being able to use Amplify.

Hi @boatcoder, apologies for the delay. Sorry that this has been a blocker.
Are you able to share any additional details of the API, as well as whether or not the NGINX based instance happens to be geographically isolated/separated from where you're making requests to the Amplify app. Wondering if a combination of the reverse proxy lookup roundtrip + the ~18-25 seconds of API processing is causing the timeout.
If you're not comfortable sharing it here you can send it to aws-amplify-customer@amazon.com - please include the this GitHub issue (https://github.com/aws-amplify/amplify-console/issues/1719) so we know it's you!
Also, linking your other feature-request(https://github.com/aws-amplify/amplify-console/issues/1697) here for future tracking.

My API is running in us-east-1c.  I'll send the rest of the details via email.

Hi boatcoder@  I looked into what is going on.  We actually set the origin read timeout to 15 seconds on reverse proxy requests and have a 30 second timeout on the distribution.  So what is happening is the first request times out, it starts a second request and then hits the 30 second distribution timeout.  If you look in your api logs, you should see 2 requests.  We can take increasing the timeout on origin requests as a feature request.

authors: behrooziAWS boatcoder siegerts

repo: aws-amplify/amplify-console


text:
Amplify Preview builds are creating duplicated DynamoDB tables and new Cognito Userpools

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
Next.js
Amplify APIs
Authentication, GraphQL API
Amplify Categories
auth, api, hosting
Environment information

# Put output below this line
System:
    OS: macOS 11.3
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 661.54 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.12.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.6.3 - /usr/local/bin/npm
  Browsers:
    Chrome: 90.0.4430.212
    Safari: 14.1
  npmPackages:
    @ampproject/toolbox-optimizer:  undefined ()
    @aws-amplify/ui-react: ^1.0.6 => 1.0.7
    @babel/core:  undefined ()
    @babel/plugin-transform-runtime: ^7.13.15 => 7.13.15
    @babel/preset-env: ^7.13.15 => 7.14.1
    @babel/preset-react: ^7.13.13 => 7.13.13
    @chakra-ui/react: ^1.5.0 => 1.6.0
    @emotion/react: ^11 => 11.1.5
    @emotion/styled: ^11 => 11.3.0
    @testing-library/dom: ^7.30.3 => 7.30.4
    @testing-library/jest-dom: ^5.11.10 => 5.12.0
    @testing-library/react: ^11.2.6 => 11.2.6
    @testing-library/user-event: ^13.1.2 => 13.1.8
    @types/jest: ^26.0.22 => 26.0.23
    amphtml-validator:  undefined ()
    arg:  undefined ()
    async-retry:  undefined ()
    async-sema:  undefined ()
    aws-amplify: ^3.3.26 => 3.3.27
    babel-jest: ^26.6.3 => 26.6.3
    bfj:  undefined ()
    cacache:  undefined ()
    cache-loader:  undefined ()
    ci-info:  undefined ()
    comment-json:  undefined ()
    compression:  undefined ()
    conf:  undefined ()
    content-type:  undefined ()
    cookie:  undefined ()
    css-loader:  undefined ()
    debug:  undefined ()
    devalue:  undefined ()
    escape-string-regexp:  undefined ()
    file-loader:  undefined ()
    find-cache-dir:  undefined ()
    find-up:  undefined ()
    framer-motion: ^4 => 4.1.11
    fresh:  undefined ()
    gzip-size:  undefined ()
    http-proxy:  undefined ()
    ignore-loader:  undefined ()
    is-animated:  undefined ()
    is-docker:  undefined ()
    is-wsl:  undefined ()
    jest: ^26.6.3 => 26.6.3
    json5:  undefined ()
    jsonwebtoken:  undefined ()
    loader-utils:  undefined ()
    lodash.curry:  undefined ()
    lru-cache:  undefined ()
    mobx: ^6.1.8 => 6.3.0
    mobx-react: ^7.1.0 => 7.1.0
    mobx-state-tree: ^5.0.1 => 5.0.1
    nanoid:  undefined ()
    neo-async:  undefined ()
    next: 10.1.3 => 10.1.3
    npm-run-all: ^4.1.5 => 4.1.5
    ora:  undefined ()
    postcss-flexbugs-fixes:  undefined ()
    postcss-loader:  undefined ()
    postcss-preset-env:  undefined ()
    postcss-scss:  undefined ()
    react: 17.0.2 => 17.0.2
    react-dom: 17.0.2 => 17.0.2
    react-icons: ^4.2.0 => 4.2.0
    recast:  undefined ()
    resolve-url-loader:  undefined ()
    sass: ^1.32.8 => 1.32.12
    sass-loader:  undefined ()
    schema-utils:  undefined ()
    semver:  undefined ()
    send:  undefined ()
    source-map:  undefined ()
    string-hash:  undefined ()
    strip-ansi:  undefined ()
    terser:  undefined ()
    text-table:  undefined ()
    thread-loader:  undefined ()
    unistore:  undefined ()
    web-vitals:  undefined ()
    webpack:  undefined ()
    webpack-sources:  undefined ()
  npmGlobalPackages:
    @aws-amplify/cli: 4.46.1
    n: 7.1.0
    npm: 7.6.3

Describe the bug
When triggering an Amplify build via previews on a newly opened PR in Github the build completes successfully and the link is provided, however, all of the DynamoDB tables are duplicated and a new Cognito userpool is created for each new pr.
Expected behavior
I would expect that:

the same Cognito pools would be used for the provided link
logins via auth would work in the preview url
the same tables that were already established would be used for graphql api queries/mutations

Reproduction steps
open a pr and the preview build settings take it from there
Code Snippet
Build settings:
version: 1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --environment main --simple
        // also tried with just - amplifyPush --simple
frontend:
  phases:
    preBuild:
      commands:
        - nvm install 15
        - yarn install
    build:
      commands:
        - yarn build
  artifacts:
    baseDirectory: out
    files:
      - '**/*'
  cache:
    paths:
      - 'node_modules/**/*'
      - '*/node_modules/**/*'
test:
  phases:
    test:
      commands:
        - yarn test
  artifacts:
    baseDirectory: /
    configFilePath: jest.config.js
    files:
      - '**/*'

Log output
na
aws-exports.js
/* eslint-disable */
// WARNING: DO NOT EDIT. This file is automatically generated by AWS Amplify. It will be overwritten.

const awsmobile = {
    "aws_project_region": "us-east-1",
    "aws_cognito_identity_pool_id": "us-east-1:redacted",
    "aws_cognito_region": "us-east-1",
    "aws_user_pools_id": "us-east-1_oyktjNd7a",
    "aws_user_pools_web_client_id": "redacted",
    "oauth": {},
    "aws_appsync_graphqlEndpoint": "redacted",
    "aws_appsync_region": "us-east-1",
    "aws_appsync_authenticationType": "AWS_IAM"
};

export default awsmobile;

Manual configuration
na
Additional configuration
na
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
![Screen Shot 2021-05-18 at 3 26 19 PM](https://user-images.githubusercontent.com/75633714/118718998-887da580-

Hi @joshlongbrake this is expected behavior
"For apps with backend environments provisioned using the Amplify CLI, every pull request (private Git repositories only) spins up an ephemeral backend that is deleted when the PR is closed."
https://docs.aws.amazon.com/amplify/latest/userguide/pr-previews.html
please re-open if you continue to have issues, thanks!