could not link rtph264depay0 to videoconvert0

I have problems when run this command on same cameras:
gst-launch-1.0 rtspsrc location="rtsp://route-of-camera" short-header=TRUE ! rtph264depay ! h264parse ! video/x-h264, format=avc,alignment=au ! kvssink stream-name="NAME" storage-size=64 access-key="ACCESSKEY" secret-key="SECRETKEY" fragment-duration="10000" aws-region="us-east-1" framerate="15"
When the terminal showed me the message error MAX_FRAGMENT_DURATION_REACHED I tried the solution from #147 and add his recomendation. But whe I run the new command the terminal show me WARNING: erroneous pipeline: could not link rtph264depay0 to videoconvert0:
gst-launch-1.0 rtspsrc location="rtsp://route-of-camera" short-header=TRUE ! rtph264depay! videoconvert ! x264enc bframes=0 key-int-max=10 ! h264parse ! video/x-h264, format=avc,alignment=au ! kvssink stream-name="NAME" storage-size=64 access-key="ACCESSKEY" secret-key="SECRETKEY" fragment-duration="10000" aws-region="us-east-1" framerate="15"
Have I possibly made a mistake while adding the parameters?

@jorrego ,
Can you modify the first command to set key-int-max to 10 and remove using fragment-duration?
 erroneous pipeline: could not link rtph264depay0 to videoconvert0: This means linking rtph264depay to videoconvert is not accepted by gstreamer libraries.

@jorrego ,
Can you modify the first command to set key-int-max to 10 and remove using fragment-duration?
 erroneous pipeline: could not link rtph264depay0 to videoconvert0: This means linking rtph264depay to videoconvert is not accepted by gstreamer libraries.

@disa6302 , i did it but it didn't work. It show me WARNING: erroneous pipeline: no property "key-int-max" in element "kvssink0".I ran this command:
gst-launch-1.0 rtspsrc location="rtsp://route-of-camera" short-header=TRUE ! rtph264depay ! h264parse ! video/x-h264, format=avc,alignment=au ! kvssink stream-name="NAME" storage-size=64 access-key="ACCESSKEY" secret-key="SECRETKEY" aws-region="us-east-1" framerate="15" key-int-max=10

Key-int-max is a x264enc property. It is not a kvssink property.

Which parameters should I use or remove? Based on what you mentioned, I modified my command adding the x264enc, looking like this:
gst-launch-1.0 rtspsrc location="rtsp://route-of-camera" short-header=TRUE ! videoconvert ! x264enc bframes=0 key-int-max=10 ! kvssink stream-name="NAME" storage-size=64 access-key="ACCESSKEY" secret-key="SECRETKEY" aws-region="us-east-1" framerate="15"
The console responded to me as follows:
Setting pipeline to PAUSED ...
log4cplus:ERROR could not open file ../kvs_log_configuration
INFO - createKinesisVideoClient(): Creating Kinesis Video Client
2023-01-11 10:32:39 [140024012063808] INFO - heapInitialize(): Initializing native heap with limit size 67108864, spill ratio 0% and flags 0x00000001
2023-01-11 10:32:39 [140024012063808] INFO - heapInitialize(): Creating AIV heap.
2023-01-11 10:32:39 [140024012063808] INFO - heapInitialize(): Heap is initialized OK
2023-01-11 10:32:39 [140024012063808] DEBUG - getSecurityTokenHandler invoked
2023-01-11 10:32:39 [140024012063808] DEBUG - Refreshing credentials. Force refreshing: 0 Now time is:<PHONE_NUMBER>786557800 Expiration: 0
2023-01-11 10:32:39 [140024012063808] INFO - createDeviceResultEvent(): Create device result event.
2023-01-11 10:32:39 [140024012063808] DEBUG - clientReadyHandler invoked
2023-01-11 10:32:39 [140024012063808] INFO - try creating stream
2023-01-11 10:32:39 [140024012063808] INFO - Creating Kinesis Video Stream NAME
2023-01-11 10:32:39 [140024012063808] INFO - createKinesisVideoStream(): Creating Kinesis Video Stream.
2023-01-11 10:32:39 [140024012063808] INFO - logStreamInfo(): SDK version: 70f74f14cf27b09f71dc1889f36eb6e04cdd90a8
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Kinesis Video Stream Info
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Stream name: NAME
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Streaming type: STREAMING_TYPE_REALTIME
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Content type: video/h264
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Max latency (100ns): 600000000
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Fragment duration (100ns): 20000000
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Key frame fragmentation: Yes
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Use frame timecode: Yes
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Absolute frame timecode: Yes
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Nal adaptation flags: 0
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Average bandwith (bps): 4194304
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Framerate: 15
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Buffer duration (100ns):<PHONE_NUMBER>
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Replay duration (100ns): 400000000
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Connection Staleness duration (100ns): 600000000
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Store Pressure Policy: 1
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): View Overflow Policy: 1
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Segment UUID: NULL
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Frame ordering mode: 0
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Track list
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Track id: 1
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Track name: kinesis_video
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Codec id: V_MPEG4/ISO/AVC
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Track type: TRACK_INFO_TYPE_VIDEO
2023-01-11 10:32:39 [140024012063808] DEBUG - logStreamInfo(): Track cpd: NULL
2023-01-11 10:32:39 [140024012063808] INFO - writeHeaderCallback(): RequestId: cfd450b0-0ac2-41fd-954d-ed984ff5aa66
2023-01-11 10:32:40 [140023917553408] DEBUG - describeStreamCurlHandler(): DescribeStream API response: {"StreamInfo":{"CreationTime":1.66632840935E9,"DataRetentionInHours":2,"DeviceName":"Kinesis_Video_Device","IngestionConfiguration":null,"KmsKeyId":"arn:aws:kms:us-east-1:000000000000:alias/aws/kinesisvideo","MediaType":"video/h264","Status":"ACTIVE","StreamARN":"arn:aws:kinesisvideo:us-east-1:000000000000:stream/NAME/1666328409350","StreamName":"NAME","Version":"b4nyaGcv8imiUxOK7ySh"}}
2023-01-11 10:32:40 [140023917553408] INFO - describeStreamResultEvent(): Describe stream result event.
2023-01-11 10:32:40 [140023917553408] INFO - writeHeaderCallback(): RequestId: 8a3d7383-a7c0-4c8e-908c-290b7fb6aa06
2023-01-11 10:32:40 [140023909160704] DEBUG - getStreamingEndpointCurlHandler(): GetStreamingEndpoint API response: {"DataEndpoint":"https://s-d8eb3b21.kinesisvideo.us-east-1.amazonaws.com"}
2023-01-11 10:32:40 [140023909160704] INFO - getStreamingEndpointResultEvent(): Get streaming endpoint result event.
2023-01-11 10:32:40 [140023909160704] DEBUG - getStreamingTokenHandler invoked
2023-01-11 10:32:40 [140023909160704] DEBUG - Refreshing credentials. Force refreshing: 1 Now time is:<PHONE_NUMBER>715493400 Expiration:<PHONE_NUMBER>3709551615
2023-01-11 10:32:40 [140023909160704] INFO - getStreamingTokenResultEvent(): Get streaming token result event.
2023-01-11 10:32:40 [140023909160704] DEBUG - streamReadyHandler invoked
2023-01-11 10:32:40 [140023909160704] Stream is ready
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://route-of-camera
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
Progress: (open) Opened Stream
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Progress: (request) Sending PLAY request
Progress: (request) Sending PLAY request
Progress: (request) Sent PLAY request
WARNING: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not read from resource.
Additional debug info:
gstrtspsrc.c(5769): gst_rtspsrc_reconnect (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
Could not receive any UDP packets for 5.0000 seconds, maybe your firewall is blocking it. Retrying using a tcp connection.
WARNING: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Delayed linking failed.
Additional debug info:
./grammar.y(506): gst_parse_no_more_pads (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
failed delayed linking some pad of GstRTSPSrc named rtspsrc0 to some pad of GstVideoConvert named videoconvert0
ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Internal data stream error.
Additional debug info:
gstrtspsrc.c(6057): gst_rtspsrc_loop (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
streaming stopped, reason not-linked (-1)
Execution ended after 0:00:06.661939200
Setting pipeline to NULL ...
Freeing pipeline ...
INFO - Freeing Kinesis Video Stream NAME
2023-01-11 10:32:48 [140024012063808] INFO - freeKinesisVideoStream(): Freeing Kinesis Video stream.
2023-01-11 10:32:48 [140024012063808] DEBUG - curlApiCallbacksShutdownActiveRequests(): pActiveRequests hashtable is empty
2023-01-11 10:32:48 [140024012063808] INFO - freeKinesisVideoClient(): Freeing Kinesis Video Client
2023-01-11 10:32:48 [140024012063808] DEBUG - curlApiCallbacksShutdownActiveRequests(): pActiveRequests hashtable is empty
2023-01-11 10:32:48 [140024012063808] DEBUG - freeKinesisVideoClientInternal(): Total allocated memory 0
2023-01-11 10:32:49 [140024012063808] WARN - curlApiCallbacksShutdown(): curlApiCallbacksShutdown called when already in progress of shutting down
2023-01-11 10:32:49 [140024012063808] #

The indicated error is: ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Internal data stream error.

@jorrego ,
Please follow our sample pipelines which are available here:
https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-cpp/tree/v3.3.1/docs
Not sure which platform you are using, but we instructions in both linux and MacOS.
Also please attach complete verbose logs when you try the sample pipeline. You can get the VERBOSE logs by modifying this line to set to TRACE.
https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-cpp/blob/70f74f14cf27b09f71dc1889f36eb6e04cdd90a8/kvs_log_configuration#L1

The compilation is in TRACE and run on Ubuntu container with an Intelbras brand camera using a public IP.

Start with the pipeline samples. As such we wouldnt know the specifics of the IP cameras being used and it is likely there are some additional attributes that might be required.
One thing you can do to understand if your pipeline is correct is to generate a pipeline using fakesink instead of KVS sink. Ensure you get the source of the pipeline correct before trying with kvssink. Based on the logs you attached, I do not see a MAX_FRAGMENT_DURATION error. It looks like there is a problem reading from the RTSP source itself.

I will test with the samples that you indicate. I have seen that the issue #183 mentions an error with the same brand of camera (Intelbras) with kvssink.

It's not a camera compatibility issue, it's a gstreamer pipeline issue. If the pipeline is failing to construct then kvssink hasn't even been deployed in the application yet.
Additionally the issue with #183 was they were missing h264parse in their pipeline.
In your earlier pipeline you were including h264parse before kvssink, please add it back and try again.

I have run the connect to RTSP camera command on two cameras of the same make and model, one that is the one I have the problem with and the other one where the stream is successful.
Command:
gst-launch-1.0 rtspsrc location="rtsp://CAMERA" short-header=TRUE ! rtph264depay ! h264parse ! video/x-h264, format=avc,alignment=au ! kvssink stream-name="NAME" storage-size=64 access-key="AKEY" secret-key="SKEY" fragment-duration="10000" aws-region="us-east-1" framerate="15"
The results of each camera are in each file that I attach.
camera CONNECTION ERROR.txt
camera CONNECTION OK.txt
Using VLC player I can see the RTSP stream from both cameras without any problems.

Thank you for sharing that @jorrego, there appear to be two issues:

I see lots of these in your log:

2023-01-23 19:42:14 [140670672467712] DEBUG - Dropping frame with flag %u1024

I see this log:

2023-01-23 19:42:18 [140670672467712] DEBUG - postWriteCallback(): Curl post body write function for stream with handle: jojo and upload handle: 0 returned: {"EventType":"ERROR","FragmentTimecode":1674502918659,"FragmentNumber":"91343852333181442296202376934447363596220606745","ErrorCode":"MAX_FRAGMENT_DURATION_REACHED","ErrorId":4002}

For (1) it looks like you have frames which the source has marked as HEADER, see here for details: https://gstreamer.freedesktop.org/documentation/gstreamer/gstbuffer.html?gi-language=c#GstBufferFlags
But in short we have logic in our kvssink that if it's a header flag and the timestamps (PTS/DTS) are INVALID then we drop the frame.
(GST_BUFFER_FLAG_IS_SET(buf, GST_BUFFER_FLAG_HEADER) && (!GST_BUFFER_PTS_IS_VALID(buf) || !GST_BUFFER_DTS_IS_VALID(buf)));

In any case dropping this could be benign but it could also be a problem if this information is necessary to decode. In which case the issue is with the timestamps on your source.  I would recommend you first try to fix the issue with (2) and see if this is actually a problem.  If it is then please report back and we can debug what is wrong with your timestamps.
For (2), so we enforce a maximum fragment size for 10s (time between key frames), meaning with the default option where we create a new fragment at key frame, your rtsp source is not adhering to that requirement.  Can you check the camera vendor and see if there is a way you can force a keyframe for example every 2s?  Just any number less than 10s should work OK then you will not see this issue.
For example on Axis cameras they allow you to pass in a parameter like videokeyframeinterval in the rtsp url to set the key frame interval, though by default it is fixed and would not cause this issue.  You have to find out from your source how to adjust this.  https://www.axis.com/vapix-library/subjects/t10175981/section/t10051110/display?section=t10051110-t10003638

@jorrego Any updates here?  Were you able to try my suggestions?

We have another problem with another brand of camera. The error that shows us is the following:
`gst-launch-1.0 rtspsrc location="rtsp://camera" short-header=TRUE ! rtph264depay ! h264parse ! video/x-h264, format=avc,alignment=au ! kvssink stream-name="jojo" storage-size=64 access-key="ACCESSKEY" secret-key="SECRETKEY" fragment-duration="10000" aws-region="us-east-1" framerate="15"
Setting pipeline to PAUSED ...
log4cplus:ERROR could not open file ./kvs_log_configuration
INFO - createKinesisVideoClient(): Creating Kinesis Video Client
2023-02-01 21:49:24 [139648666998592] INFO - heapInitialize(): Initializing native heap with limit size 67108864, spill ratio 0% and flags 0x00000001
2023-02-01 21:49:24 [139648666998592] INFO - heapInitialize(): Creating AIV heap.
2023-02-01 21:49:24 [139648666998592] INFO - heapInitialize(): Heap is initialized OK
2023-02-01 21:49:24 [139648666998592] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000001, Next state: 0x0000000000000002
2023-02-01 21:49:24 [139648666998592] DEBUG - getSecurityTokenHandler invoked
2023-02-01 21:49:24 [139648666998592] DEBUG - Refreshing credentials. Force refreshing: 0 Now time is:<PHONE_NUMBER>744378718 Expiration: 0
2023-02-01 21:49:24 [139648666998592] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000002, Next state: 0x0000000000000010
2023-02-01 21:49:24 [139648666998592] INFO - createDeviceResultEvent(): Create device result event.
2023-02-01 21:49:24 [139648666998592] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000010, Next state: 0x0000000000000040
2023-02-01 21:49:24 [139648666998592] DEBUG - clientReadyHandler invoked
2023-02-01 21:49:24 [139648666998592] INFO - try creating stream
2023-02-01 21:49:24 [139648666998592] INFO - Creating Kinesis Video Stream jojo
2023-02-01 21:49:24 [139648666998592] INFO - createKinesisVideoStream(): Creating Kinesis Video Stream.
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo(): Kinesis Video Stream Info
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Stream name: jojo
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Streaming type: STREAMING_TYPE_REALTIME
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Content type: video/h264
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Max latency (100ns): 600000000
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Fragment duration (100ns): 100000000
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Key frame fragmentation: Yes
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Use frame timecode: Yes
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Absolute frame timecode: Yes
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Nal adaptation flags: 0
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Average bandwith (bps): 4194304
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Framerate: 15
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Buffer duration (100ns):<PHONE_NUMBER>
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Replay duration (100ns): 400000000
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Connection Staleness duration (100ns): 600000000
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Store Pressure Policy: 1
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  View Overflow Policy: 1
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Segment UUID: NULL
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Frame ordering mode: 0
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo(): Track list
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Track id: 1
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Track name: kinesis_video
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Codec id: V_MPEG4/ISO/AVC
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Track type: TRACK_INFO_TYPE_VIDEO
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Track cpd: NULL
2023-02-01 21:49:24 [139648666998592] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000001, Next state: 0x0000000000000002
2023-02-01 21:49:24 [139648666998592] INFO - writeHeaderCallback(): RequestId: c7142f5a-dcdd-49d3-8000-3e616329f620
2023-02-01 21:49:24 [139648486536960] DEBUG - describeStreamCurlHandler(): DescribeStream API response: {"StreamInfo":{"CreationTime":1.674165442087E9,"DataRetentionInHours":2,"DeviceName":"Kinesis_Video_Device","IngestionConfiguration":null,"KmsKeyId":"arn:aws:kms:us-east-1:750035152062:alias/aws/kinesisvideo","MediaType":"video/h264","Status":"ACTIVE","StreamARN":"arn:aws:kinesisvideo:us-east-1:750035152062:stream/jojo/1674165442087","StreamName":"jojo","Version":"lWs45pLZtgnGV59WWcJ9"}}
2023-02-01 21:49:24 [139648486536960] INFO - describeStreamResultEvent(): Describe stream result event.
2023-02-01 21:49:24 [139648486536960] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000002, Next state: 0x0000000000000020
2023-02-01 21:49:24 [139648486536960] INFO - writeHeaderCallback(): RequestId: d08a7d62-c56b-4b41-81fc-7063d69abda1
2023-02-01 21:49:24 [139648476047104] DEBUG - getStreamingEndpointCurlHandler(): GetStreamingEndpoint API response: {"DataEndpoint":"https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com"}
2023-02-01 21:49:24 [139648476047104] INFO - getStreamingEndpointResultEvent(): Get streaming endpoint result event.
2023-02-01 21:49:24 [139648476047104] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000020, Next state: 0x0000000000000010
2023-02-01 21:49:24 [139648476047104] DEBUG - getStreamingTokenHandler invoked
2023-02-01 21:49:24 [139648476047104] DEBUG - Refreshing credentials. Force refreshing: 1 Now time is:<PHONE_NUMBER>866238840 Expiration:<PHONE_NUMBER>3709551615
2023-02-01 21:49:24 [139648476047104] INFO - getStreamingTokenResultEvent(): Get streaming token result event.
2023-02-01 21:49:24 [139648476047104] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000010, Next state: 0x0000000000000040
2023-02-01 21:49:24 [139648476047104] DEBUG - streamReadyHandler invoked
2023-02-01 21:49:24 [139648476047104] Stream is ready
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://camera
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
Progress: (open) Opened Stream
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Progress: (request) Sending PLAY request
Progress: (request) Sending PLAY request
Progress: (request) Sent PLAY request
WARNING: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not read from resource.
Additional debug info:
gstrtspsrc.c(4904): gst_rtspsrc_reconnect (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
Could not receive any UDP packets for 5.0000 seconds, maybe your firewall is blocking it. Retrying using a tcp connection.
INFO - kinesisVideoStreamFormatChanged(): Stream format changed.
2023-02-01 21:49:32 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:49:32 [139648191325952] INFO - putStreamResultEvent(): Put stream result event. New upload handle 0
2023-02-01 21:49:32 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:49:32 [139648191325952] DEBUG - Kinesis Video client and stream metrics
>> Overall storage byte size: 67108864
>> Available storage byte size: 67085540
>> Allocated storage byte size: 23324
>> Total view allocation byte size: 86480
>> Total streams frame rate (fps): 15
>> Total streams transfer rate (bps): 33554432 (32768 Kbps)
>> Current view duration (ms): 0
>> Overall view duration (ms): 0
>> Current view byte size: 23276
>> Overall view byte size: 23276
>> Current frame rate (fps): 15
>> Current transfer rate (bps): 33554432 (32768 Kbps)
2023-02-01 21:49:32 [139648191325952] DEBUG - postReadCallback(): Wrote 23276 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:32 [139648201815808] INFO - writeHeaderCallback(): RequestId: de1c8b0d-bdbd-eed3-8248-6ba12e0076e3
2023-02-01 21:49:32 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:32 [139648201815808] DEBUG - postWriteCallback(): Curl post body write function for stream with handle: jojo and upload handle: 0 returned: {"EventType":"BUFFERING","FragmentTimecode":1675288172244,"FragmentNumber":"91343852333181476958523476925305850672026308238"}
2023-02-01 21:49:32 [139648201815808] DEBUG - fragmentAckReceivedHandler invoked
2023-02-01 21:49:32 [139648201815808] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:49:32 [139648191325952] DEBUG - postReadCallback(): Wrote 1515 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:32 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:32 [139648201815808] DEBUG - postReadCallback(): Wrote 6699 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:33 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:33 [139648201815808] DEBUG - postReadCallback(): Wrote 19765 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:34 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:34 [139648201815808] DEBUG - postReadCallback(): Wrote 15567 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:35 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:35 [139648201815808] DEBUG - postReadCallback(): Wrote 21665 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:36 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:36 [139648201815808] DEBUG - postReadCallback(): Wrote 12995 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:37 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:37 [139648201815808] DEBUG - postReadCallback(): Wrote 23725 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:38 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:38 [139648201815808] DEBUG - postReadCallback(): Wrote 18876 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:39 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:39 [139648201815808] DEBUG - postReadCallback(): Wrote 20056 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:40 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:40 [139648201815808] DEBUG - postReadCallback(): Wrote 22737 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:41 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:41 [139648201815808] DEBUG - postReadCallback(): Wrote 16718 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:42 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:42 [139648201815808] DEBUG - postReadCallback(): Wrote 7629 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:43 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:43 [139648201815808] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:49:43 [139648191325952] DEBUG - postReadCallback(): Wrote 4185 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:44 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:44 [139648201815808] DEBUG - postReadCallback(): Wrote 3925 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:45 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:45 [139648201815808] DEBUG - postReadCallback(): Wrote 5468 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:46 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:46 [139648201815808] DEBUG - postReadCallback(): Wrote 3387 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:47 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:47 [139648201815808] DEBUG - postReadCallback(): Wrote 6221 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:48 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:48 [139648201815808] DEBUG - postReadCallback(): Wrote 3138 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:49 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:49 [139648201815808] DEBUG - postReadCallback(): Wrote 7499 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:50 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:50 [139648201815808] DEBUG - postReadCallback(): Wrote 62886 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:51 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:51 [139648201815808] DEBUG - postReadCallback(): Wrote 65524 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - postReadCallback(): Wrote 10091 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - postWriteCallback(): Curl post body write function for stream with handle: jojo and upload handle: 0 returned: {"EventType":"ERROR","FragmentTimecode":1675288172244,"FragmentNumber":"91343852333181476958523476925305850672026308238","ErrorCode":"MAX_FRAGMENT_DURATION_REACHED","ErrorId":4002}
2023-02-01 21:49:52 [139648201815808] DEBUG - streamErrorHandler invoked
2023-02-01 21:49:52 [139648201815808] ERROR - Reported stream error. Errored timecode: 64080000 Status: 0x5200005e
2023-02-01 21:49:52 [139648201815808] WARN - continuousRetryStreamErrorReportHandler(): Reporting stream error. Errored timecode: 64080000 Status: 0x5200005e
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000001
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000001, Next state: 0x0000000000000002
2023-02-01 21:49:52 [139648201815808] INFO - describeStreamResultEvent(): Describe stream result event.
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000002, Next state: 0x0000000000000020
2023-02-01 21:49:52 [139648201815808] INFO - getStreamingEndpointResultEvent(): Get streaming endpoint result event.
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000020, Next state: 0x0000000000000010
2023-02-01 21:49:52 [139648201815808] DEBUG - getStreamingTokenHandler invoked
2023-02-01 21:49:52 [139648201815808] DEBUG - Refreshing credentials. Force refreshing: 1 Now time is:<PHONE_NUMBER>315079145 Expiration:<PHONE_NUMBER>3709551615
2023-02-01 21:49:52 [139648201815808] INFO - getStreamingTokenResultEvent(): Get streaming token result event.
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000010, Next state: 0x0000000000000040
2023-02-01 21:49:52 [139648201815808] DEBUG - streamReadyHandler invoked
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:49:52 [139648201815808] INFO - putStreamResultEvent(): Put stream result event. New upload handle 1
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:49:52 [139648201815808] DEBUG - fragmentAckReceivedHandler invoked
2023-02-01 21:49:52 [139648201815808] WARN - getStreamData(): Indicating an end-of-stream for a terminated stream upload handle 0
2023-02-01 21:49:52 [139648201815808] INFO - postReadCallback(): Reported end-of-stream for stream jojo. Upload handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - postReadCallback(): Wrote 0 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - putStreamCurlHandler(): Network thread for Kinesis Video stream: jojo with upload handle: 0 exited. http status: 200
2023-02-01 21:49:52 [139648201815808] INFO - writeHeaderCallback(): RequestId: c9cd07e8-cc10-54a1-9599-e728309225e3
2023-02-01 21:49:52 [139648212305664] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 1
2023-02-01 21:49:52 [139648212305664] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:49:52 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:02 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:09 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:17 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:22 [139648191325952] WARN - curlCompleteSync(): curl perform failed for url https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia with result Timeout was reached: Operation too slow. Less than 30 bytes/sec transferred the last 30 seconds
2023-02-01 21:50:22 [139648212305664] WARN - curlCompleteSync(): HTTP Error 0 : Response: (null)
Request URL: https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia
Request Headers:
Authorization: AWS4-HMAC-SHA256 Credential=ACCESSKEY/20230201/us-east-1/kinesisvideo/aws4_request, SignedHeaders=connection;host;transfer-encoding;user-agent;x-amz-date;x-amzn-fragment-acknowledgment-required;x-amzn-fragment-timecode-type;x-amzn-producer-start-timestamp;x-amzn-stream-name, Signature=0f009bbf1686640579367ed578a27cb8db228c0018aff6a
2023-02-01 21:50:22 [139648212305664] DEBUG - putStreamCurlHandler(): Network thread for Kinesis Video stream: jojo with upload handle: 1 exited. http status: 0
2023-02-01 21:50:22 [139648212305664] WARN - putStreamCurlHandler(): Stream with streamHandle 39109624 has exited without triggering end-of-stream. Service call result: 599
2023-02-01 21:50:22 [139648212305664] INFO - kinesisVideoStreamTerminated(): Stream 0x254c3f8 terminated upload handle 1 with service call result 599.
2023-02-01 21:50:22 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
2023-02-01 21:50:22 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
2023-02-01 21:50:22 [139648191325952] DEBUG - streamReadyHandler invoked
2023-02-01 21:50:22 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:50:22 [139648191325952] INFO - putStreamResultEvent(): Put stream result event. New upload handle 2
2023-02-01 21:50:22 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:50:22 [139648191325952] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 2
2023-02-01 21:50:22 [139648212305664] INFO - writeHeaderCallback(): RequestId: cf5eb206-772f-67a1-930a-52d8ef9eb8c6
2023-02-01 21:50:22 [139648212305664] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:29 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:39 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:46 [139648191325952] WARN - curlCompleteSync(): curl perform failed for url https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia with result Timeout was reached: Operation too slow. Less than 30 bytes/sec transferred the last 30 seconds
2023-02-01 21:50:52 [139648212305664] WARN - curlCompleteSync(): HTTP Error 0 : Response: (null)
Request URL: https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia
Request Headers:
Authorization: AWS4-HMAC-SHA256 Credential=ACCESSKEY/20230201/us-east-1/kinesisvideo/aws4_request, SignedHeaders=connection;host;transfer-encoding;user-agent;x-amz-date;x-amzn-fragment-acknowledgment-required;x-amzn-fragment-timecode-type;x-amzn-producer-start-timestamp;x-amzn-stream-name, Signature=1e13e9b9e5417e741a7085b8a8299b2930dcb6dd946ad61
2023-02-01 21:50:52 [139648212305664] DEBUG - putStreamCurlHandler(): Network thread for Kinesis Video stream: jojo with upload handle: 2 exited. http status: 0
2023-02-01 21:50:52 [139648212305664] WARN - putStreamCurlHandler(): Stream with streamHandle 39109624 has exited without triggering end-of-stream. Service call result: 599
2023-02-01 21:50:52 [139648212305664] INFO - kinesisVideoStreamTerminated(): Stream 0x254c3f8 terminated upload handle 2 with service call result 599.
2023-02-01 21:50:52 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
2023-02-01 21:50:52 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
2023-02-01 21:50:52 [139648191325952] DEBUG - streamReadyHandler invoked
2023-02-01 21:50:52 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:50:52 [139648191325952] INFO - putStreamResultEvent(): Put stream result event. New upload handle 3
2023-02-01 21:50:52 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:50:52 [139648191325952] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 3
2023-02-01 21:50:52 [139648212305664] INFO - writeHeaderCallback(): RequestId: c576e5e1-f313-d8bd-9922-051d6d372aaf
2023-02-01 21:50:52 [139648212305664] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:56 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:51:06 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:51:17 [139648191325952] WARN - curlCompleteSync(): curl perform failed for url https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia with result Timeout was reached: Operation too slow. Less than 30 bytes/sec transferred the last 30 seconds
2023-02-01 21:51:22 [139648212305664] WARN - curlCompleteSync(): HTTP Error 0 : Response: (null)
Request URL: https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia
Request Headers:
Authorization: AWS4-HMAC-SHA256 Credential=ACCESSKEY/20230201/us-east-1/kinesisvideo/aws4_request, SignedHeaders=connection;host;transfer-encoding;user-agent;x-amz-date;x-amzn-fragment-acknowledgment-required;x-amzn-fragment-timecode-type;x-amzn-producer-start-timestamp;x-amzn-stream-name, Signature=4049b15ec30491b7e212a0ffa384cea11d8a232d0020f42
2023-02-01 21:51:22 [139648212305664] DEBUG - putStreamCurlHandler(): Network thread for Kinesis Video stream: jojo with upload handle: 3 exited. http status: 0
2023-02-01 21:51:22 [139648212305664] WARN - putStreamCurlHandler(): Stream with streamHandle 39109624 has exited without triggering end-of-stream. Service call result: 599
2023-02-01 21:51:22 [139648212305664] INFO - kinesisVideoStreamTerminated(): Stream 0x254c3f8 terminated upload handle 3 with service call result 599.
2023-02-01 21:51:22 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
2023-02-01 21:51:22 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
2023-02-01 21:51:22 [139648191325952] DEBUG - streamReadyHandler invoked
2023-02-01 21:51:22 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:51:22 [139648191325952] INFO - putStreamResultEvent(): Put stream result event. New upload handle 4
2023-02-01 21:51:22 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:51:22 [139648191325952] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 4
2023-02-01 21:51:22 [139648212305664] INFO - writeHeaderCallback(): RequestId: e72c4c39-a542-5246-bb78-ad2335791dcc
2023-02-01 21:51:22 [139648212305664] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:51:23 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:51:28 [139648191325952] DEBUG - Dropping frame with flag %u1024`

We have another problem with another brand of camera. The error that shows us is the following:
gst-launch-1.0 rtspsrc location="rtsp://camera" short-header=TRUE ! rtph264depay ! h264parse ! video/x-h264, format=avc,alignment=au ! kvssink stream-name="jojo" storage-size=64 access-key="ACCESSKEY" secret-key="SECRETKEY" fragment-duration="10000" aws-region="us-east-1" framerate="15"
Setting pipeline to PAUSED ...
log4cplus:ERROR could not open file ./kvs_log_configuration
INFO - createKinesisVideoClient(): Creating Kinesis Video Client
2023-02-01 21:49:24 [139648666998592] INFO - heapInitialize(): Initializing native heap with limit size 67108864, spill ratio 0% and flags 0x00000001
2023-02-01 21:49:24 [139648666998592] INFO - heapInitialize(): Creating AIV heap.
2023-02-01 21:49:24 [139648666998592] INFO - heapInitialize(): Heap is initialized OK
2023-02-01 21:49:24 [139648666998592] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000001, Next state: 0x0000000000000002
2023-02-01 21:49:24 [139648666998592] DEBUG - getSecurityTokenHandler invoked
2023-02-01 21:49:24 [139648666998592] DEBUG - Refreshing credentials. Force refreshing: 0 Now time is:<PHONE_NUMBER>744378718 Expiration: 0
2023-02-01 21:49:24 [139648666998592] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000002, Next state: 0x0000000000000010
2023-02-01 21:49:24 [139648666998592] INFO - createDeviceResultEvent(): Create device result event.
2023-02-01 21:49:24 [139648666998592] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000010, Next state: 0x0000000000000040
2023-02-01 21:49:24 [139648666998592] DEBUG - clientReadyHandler invoked
2023-02-01 21:49:24 [139648666998592] INFO - try creating stream
2023-02-01 21:49:24 [139648666998592] INFO - Creating Kinesis Video Stream jojo
2023-02-01 21:49:24 [139648666998592] INFO - createKinesisVideoStream(): Creating Kinesis Video Stream.
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo(): Kinesis Video Stream Info
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Stream name: jojo
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Streaming type: STREAMING_TYPE_REALTIME
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Content type: video/h264
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Max latency (100ns): 600000000
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Fragment duration (100ns): 100000000
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Key frame fragmentation: Yes
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Use frame timecode: Yes
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Absolute frame timecode: Yes
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Nal adaptation flags: 0
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Average bandwith (bps): 4194304
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Framerate: 15
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Buffer duration (100ns):<PHONE_NUMBER>
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Replay duration (100ns): 400000000
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Connection Staleness duration (100ns): 600000000
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Store Pressure Policy: 1
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  View Overflow Policy: 1
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Segment UUID: NULL
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Frame ordering mode: 0
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo(): Track list
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Track id: 1
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Track name: kinesis_video
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Codec id: V_MPEG4/ISO/AVC
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Track type: TRACK_INFO_TYPE_VIDEO
2023-02-01 21:49:24 [139648666998592] DEBUG - logStreamInfo():  Track cpd: NULL
2023-02-01 21:49:24 [139648666998592] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000001, Next state: 0x0000000000000002
2023-02-01 21:49:24 [139648666998592] INFO - writeHeaderCallback(): RequestId: c7142f5a-dcdd-49d3-8000-3e616329f620
2023-02-01 21:49:24 [139648486536960] DEBUG - describeStreamCurlHandler(): DescribeStream API response: {"StreamInfo":{"CreationTime":1.674165442087E9,"DataRetentionInHours":2,"DeviceName":"Kinesis_Video_Device","IngestionConfiguration":null,"KmsKeyId":"arn:aws:kms:us-east-1:750035152062:alias/aws/kinesisvideo","MediaType":"video/h264","Status":"ACTIVE","StreamARN":"arn:aws:kinesisvideo:us-east-1:750035152062:stream/jojo/1674165442087","StreamName":"jojo","Version":"lWs45pLZtgnGV59WWcJ9"}}
2023-02-01 21:49:24 [139648486536960] INFO - describeStreamResultEvent(): Describe stream result event.
2023-02-01 21:49:24 [139648486536960] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000002, Next state: 0x0000000000000020
2023-02-01 21:49:24 [139648486536960] INFO - writeHeaderCallback(): RequestId: d08a7d62-c56b-4b41-81fc-7063d69abda1
2023-02-01 21:49:24 [139648476047104] DEBUG - getStreamingEndpointCurlHandler(): GetStreamingEndpoint API response: {"DataEndpoint":"https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com"}
2023-02-01 21:49:24 [139648476047104] INFO - getStreamingEndpointResultEvent(): Get streaming endpoint result event.
2023-02-01 21:49:24 [139648476047104] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000020, Next state: 0x0000000000000010
2023-02-01 21:49:24 [139648476047104] DEBUG - getStreamingTokenHandler invoked
2023-02-01 21:49:24 [139648476047104] DEBUG - Refreshing credentials. Force refreshing: 1 Now time is:<PHONE_NUMBER>866238840 Expiration:<PHONE_NUMBER>3709551615
2023-02-01 21:49:24 [139648476047104] INFO - getStreamingTokenResultEvent(): Get streaming token result event.
2023-02-01 21:49:24 [139648476047104] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000010, Next state: 0x0000000000000040
2023-02-01 21:49:24 [139648476047104] DEBUG - streamReadyHandler invoked
2023-02-01 21:49:24 [139648476047104] Stream is ready
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://camera
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
Progress: (open) Opened Stream
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Progress: (request) Sending PLAY request
Progress: (request) Sending PLAY request
Progress: (request) Sent PLAY request
WARNING: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not read from resource.
Additional debug info:
gstrtspsrc.c(4904): gst_rtspsrc_reconnect (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
Could not receive any UDP packets for 5.0000 seconds, maybe your firewall is blocking it. Retrying using a tcp connection.
INFO - kinesisVideoStreamFormatChanged(): Stream format changed.
2023-02-01 21:49:32 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:49:32 [139648191325952] INFO - putStreamResultEvent(): Put stream result event. New upload handle 0
2023-02-01 21:49:32 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:49:32 [139648191325952] DEBUG - Kinesis Video client and stream metrics
        >> Overall storage byte size: 67108864
        >> Available storage byte size: 67085540
        >> Allocated storage byte size: 23324
        >> Total view allocation byte size: 86480
        >> Total streams frame rate (fps): 15
        >> Total streams transfer rate (bps): 33554432 (32768 Kbps)
        >> Current view duration (ms): 0
        >> Overall view duration (ms): 0
        >> Current view byte size: 23276
        >> Overall view byte size: 23276
        >> Current frame rate (fps): 15
        >> Current transfer rate (bps): 33554432 (32768 Kbps)
2023-02-01 21:49:32 [139648191325952] DEBUG - postReadCallback(): Wrote 23276 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:32 [139648201815808] INFO - writeHeaderCallback(): RequestId: de1c8b0d-bdbd-eed3-8248-6ba12e0076e3
2023-02-01 21:49:32 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:32 [139648201815808] DEBUG - postWriteCallback(): Curl post body write function for stream with handle: jojo and upload handle: 0 returned: {"EventType":"BUFFERING","FragmentTimecode":1675288172244,"FragmentNumber":"91343852333181476958523476925305850672026308238"}

2023-02-01 21:49:32 [139648201815808] DEBUG - fragmentAckReceivedHandler invoked
2023-02-01 21:49:32 [139648201815808] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:49:32 [139648191325952] DEBUG - postReadCallback(): Wrote 1515 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:32 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:32 [139648201815808] DEBUG - postReadCallback(): Wrote 6699 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:33 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:33 [139648201815808] DEBUG - postReadCallback(): Wrote 19765 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:34 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:34 [139648201815808] DEBUG - postReadCallback(): Wrote 15567 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:35 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:35 [139648201815808] DEBUG - postReadCallback(): Wrote 21665 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:36 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:36 [139648201815808] DEBUG - postReadCallback(): Wrote 12995 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:37 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:37 [139648201815808] DEBUG - postReadCallback(): Wrote 23725 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:38 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:38 [139648201815808] DEBUG - postReadCallback(): Wrote 18876 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:39 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:39 [139648201815808] DEBUG - postReadCallback(): Wrote 20056 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:40 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:40 [139648201815808] DEBUG - postReadCallback(): Wrote 22737 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:41 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:41 [139648201815808] DEBUG - postReadCallback(): Wrote 16718 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:42 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:42 [139648201815808] DEBUG - postReadCallback(): Wrote 7629 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:43 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:43 [139648201815808] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:49:43 [139648191325952] DEBUG - postReadCallback(): Wrote 4185 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:44 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:44 [139648201815808] DEBUG - postReadCallback(): Wrote 3925 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:45 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:45 [139648201815808] DEBUG - postReadCallback(): Wrote 5468 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:46 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:46 [139648201815808] DEBUG - postReadCallback(): Wrote 3387 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:47 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:47 [139648201815808] DEBUG - postReadCallback(): Wrote 6221 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:48 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:48 [139648201815808] DEBUG - postReadCallback(): Wrote 3138 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:49 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:49 [139648201815808] DEBUG - postReadCallback(): Wrote 7499 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:50 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:50 [139648201815808] DEBUG - postReadCallback(): Wrote 62886 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:51 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:51 [139648201815808] DEBUG - postReadCallback(): Wrote 65524 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - postReadCallback(): Wrote 10091 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - postWriteCallback(): Curl post body write function for stream with handle: jojo and upload handle: 0 returned: {"EventType":"ERROR","FragmentTimecode":1675288172244,"FragmentNumber":"91343852333181476958523476925305850672026308238","ErrorCode":"MAX_FRAGMENT_DURATION_REACHED","ErrorId":4002}

2023-02-01 21:49:52 [139648201815808] DEBUG - streamErrorHandler invoked
2023-02-01 21:49:52 [139648201815808] ERROR - Reported stream error. Errored timecode: 64080000 Status: 0x5200005e
2023-02-01 21:49:52 [139648201815808] WARN - continuousRetryStreamErrorReportHandler(): Reporting stream error. Errored timecode: 64080000 Status: 0x5200005e
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000001
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000001, Next state: 0x0000000000000002
2023-02-01 21:49:52 [139648201815808] INFO - describeStreamResultEvent(): Describe stream result event.
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000002, Next state: 0x0000000000000020
2023-02-01 21:49:52 [139648201815808] INFO - getStreamingEndpointResultEvent(): Get streaming endpoint result event.
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000020, Next state: 0x0000000000000010
2023-02-01 21:49:52 [139648201815808] DEBUG - getStreamingTokenHandler invoked
2023-02-01 21:49:52 [139648201815808] DEBUG - Refreshing credentials. Force refreshing: 1 Now time is:<PHONE_NUMBER>315079145 Expiration:<PHONE_NUMBER>3709551615
2023-02-01 21:49:52 [139648201815808] INFO - getStreamingTokenResultEvent(): Get streaming token result event.
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000010, Next state: 0x0000000000000040
2023-02-01 21:49:52 [139648201815808] DEBUG - streamReadyHandler invoked
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:49:52 [139648201815808] INFO - putStreamResultEvent(): Put stream result event. New upload handle 1
2023-02-01 21:49:52 [139648201815808] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:49:52 [139648201815808] DEBUG - fragmentAckReceivedHandler invoked
2023-02-01 21:49:52 [139648201815808] WARN - getStreamData(): Indicating an end-of-stream for a terminated stream upload handle 0
2023-02-01 21:49:52 [139648201815808] INFO - postReadCallback(): Reported end-of-stream for stream jojo. Upload handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - postReadCallback(): Wrote 0 bytes to Kinesis Video. Upload stream handle: 0
2023-02-01 21:49:52 [139648201815808] DEBUG - putStreamCurlHandler(): Network thread for Kinesis Video stream: jojo with upload handle: 0 exited. http status: 200
2023-02-01 21:49:52 [139648201815808] INFO - writeHeaderCallback(): RequestId: c9cd07e8-cc10-54a1-9599-e728309225e3
2023-02-01 21:49:52 [139648212305664] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 1
2023-02-01 21:49:52 [139648212305664] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:49:52 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:02 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:09 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:17 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:22 [139648191325952] WARN - curlCompleteSync(): curl perform failed for url https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia with result Timeout was reached: Operation too slow. Less than 30 bytes/sec transferred the last 30 seconds
2023-02-01 21:50:22 [139648212305664] WARN - curlCompleteSync(): HTTP Error 0 : Response: (null)
Request URL: https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia
Request Headers:
    Authorization: AWS4-HMAC-SHA256 Credential=ACCESSKEY/20230201/us-east-1/kinesisvideo/aws4_request, SignedHeaders=connection;host;transfer-encoding;user-agent;x-amz-date;x-amzn-fragment-acknowledgment-required;x-amzn-fragment-timecode-type;x-amzn-producer-start-timestamp;x-amzn-stream-name, Signature=0f009bbf1686640579367ed578a27cb8db228c0018aff6a
2023-02-01 21:50:22 [139648212305664] DEBUG - putStreamCurlHandler(): Network thread for Kinesis Video stream: jojo with upload handle: 1 exited. http status: 0
2023-02-01 21:50:22 [139648212305664] WARN - putStreamCurlHandler(): Stream with streamHandle 39109624 has exited without triggering end-of-stream. Service call result: 599
2023-02-01 21:50:22 [139648212305664] INFO - kinesisVideoStreamTerminated(): Stream 0x254c3f8 terminated upload handle 1 with service call result 599.
2023-02-01 21:50:22 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
2023-02-01 21:50:22 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
2023-02-01 21:50:22 [139648191325952] DEBUG - streamReadyHandler invoked
2023-02-01 21:50:22 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:50:22 [139648191325952] INFO - putStreamResultEvent(): Put stream result event. New upload handle 2
2023-02-01 21:50:22 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:50:22 [139648191325952] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 2
2023-02-01 21:50:22 [139648212305664] INFO - writeHeaderCallback(): RequestId: cf5eb206-772f-67a1-930a-52d8ef9eb8c6
2023-02-01 21:50:22 [139648212305664] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:29 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:39 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:46 [139648191325952] WARN - curlCompleteSync(): curl perform failed for url https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia with result Timeout was reached: Operation too slow. Less than 30 bytes/sec transferred the last 30 seconds
2023-02-01 21:50:52 [139648212305664] WARN - curlCompleteSync(): HTTP Error 0 : Response: (null)
Request URL: https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia
Request Headers:
    Authorization: AWS4-HMAC-SHA256 Credential=ACCESSKEY/20230201/us-east-1/kinesisvideo/aws4_request, SignedHeaders=connection;host;transfer-encoding;user-agent;x-amz-date;x-amzn-fragment-acknowledgment-required;x-amzn-fragment-timecode-type;x-amzn-producer-start-timestamp;x-amzn-stream-name, Signature=1e13e9b9e5417e741a7085b8a8299b2930dcb6dd946ad61
2023-02-01 21:50:52 [139648212305664] DEBUG - putStreamCurlHandler(): Network thread for Kinesis Video stream: jojo with upload handle: 2 exited. http status: 0
2023-02-01 21:50:52 [139648212305664] WARN - putStreamCurlHandler(): Stream with streamHandle 39109624 has exited without triggering end-of-stream. Service call result: 599
2023-02-01 21:50:52 [139648212305664] INFO - kinesisVideoStreamTerminated(): Stream 0x254c3f8 terminated upload handle 2 with service call result 599.
2023-02-01 21:50:52 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
2023-02-01 21:50:52 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
2023-02-01 21:50:52 [139648191325952] DEBUG - streamReadyHandler invoked
2023-02-01 21:50:52 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:50:52 [139648191325952] INFO - putStreamResultEvent(): Put stream result event. New upload handle 3
2023-02-01 21:50:52 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:50:52 [139648191325952] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 3
2023-02-01 21:50:52 [139648212305664] INFO - writeHeaderCallback(): RequestId: c576e5e1-f313-d8bd-9922-051d6d372aaf
2023-02-01 21:50:52 [139648212305664] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:50:56 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:51:06 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:51:17 [139648191325952] WARN - curlCompleteSync(): curl perform failed for url https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia with result Timeout was reached: Operation too slow. Less than 30 bytes/sec transferred the last 30 seconds
2023-02-01 21:51:22 [139648212305664] WARN - curlCompleteSync(): HTTP Error 0 : Response: (null)
Request URL: https://s-808fdb44.kinesisvideo.us-east-1.amazonaws.com/putMedia
Request Headers:
    Authorization: AWS4-HMAC-SHA256 Credential=ACCESSKEY/20230201/us-east-1/kinesisvideo/aws4_request, SignedHeaders=connection;host;transfer-encoding;user-agent;x-amz-date;x-amzn-fragment-acknowledgment-required;x-amzn-fragment-timecode-type;x-amzn-producer-start-timestamp;x-amzn-stream-name, Signature=4049b15ec30491b7e212a0ffa384cea11d8a232d0020f42
2023-02-01 21:51:22 [139648212305664] DEBUG - putStreamCurlHandler(): Network thread for Kinesis Video stream: jojo with upload handle: 3 exited. http status: 0
2023-02-01 21:51:22 [139648212305664] WARN - putStreamCurlHandler(): Stream with streamHandle 39109624 has exited without triggering end-of-stream. Service call result: 599
2023-02-01 21:51:22 [139648212305664] INFO - kinesisVideoStreamTerminated(): Stream 0x254c3f8 terminated upload handle 3 with service call result 599.
2023-02-01 21:51:22 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
2023-02-01 21:51:22 [139648212305664] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
2023-02-01 21:51:22 [139648191325952] DEBUG - streamReadyHandler invoked
2023-02-01 21:51:22 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2023-02-01 21:51:22 [139648191325952] INFO - putStreamResultEvent(): Put stream result event. New upload handle 4
2023-02-01 21:51:22 [139648191325952] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2023-02-01 21:51:22 [139648191325952] DEBUG - postReadCallback(): Pausing CURL read for upload handle: 4
2023-02-01 21:51:22 [139648212305664] INFO - writeHeaderCallback(): RequestId: e72c4c39-a542-5246-bb78-ad2335791dcc
2023-02-01 21:51:22 [139648212305664] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:51:23 [139648191325952] DEBUG - Dropping frame with flag %u1024
2023-02-01 21:51:28 [139648191325952] DEBUG - Dropping frame with flag %u1024

@jorrego Any updates here? Were you able to try my suggestions?

We cannot find where to manipulate the keyframe in these cameras, so we are looking at resetting them since not all of the Intelbras brand has this problem. As soon as we can prove it, I'll let you know what happened.

Hey @jorrego your latest logs here have the same items pointed out by @hassanctech in this earlier comment.
Keyframe interval is the same thing as I-Frame interval. There should be an option to change it. Could you try @hassanctech's suggestion to try lowering the interval? Since you appear to be using a framerate of 15, a keyframe interval of 30 would fit the 2-second interval suggestion.

Closing due to no response. @jorrego , if you have more details or have any more questions, feel free to reopen or create a new issue.


Add how to test your simple shell

Added a testing process in the testing.md file
Linked the testing.md in the README.md of the simple-shell directory.

I added some guidelines for testing a simple shell...
Now, I have one concern about the structure in the table of the README.md
| File/folder    | Description    | External resource |
What is that External resource supposed to mean?
Because it is useless to always have to link to alx. What did you intend for that column?

I added some guidelines for testing a simple shell... Now, I have one concern about the structure in the table of the README.md
| File/folder | Description | External resource |
What is that External resource supposed to mean? Because it is useless to always have to link to alx. What did you intend for that column?

The external resource is for a breve explanation or overview, we can't link to alx (intranet concept) 'cause if we do that we are in violation of the alx's code of conduct. So what we do is link a good resource of overview referring to the specific topic of resource we are adding (note that it's optional)

Thanks!

I added some guidelines for testing a simple shell... Now, I have one concern about the structure in the table of the README.md
| File/folder | Description | External resource |
What is that External resource supposed to mean? Because it is useless to always have to link to alx. What did you intend for that column?

The external resource is for a breve explanation or overview, we can't link to alx (intranet concept) 'cause if we do that we are in violation of the alx's code of conduct. So what we do is link a good resource of overview referring to the specific topic of resource we are adding (note that it's optional)

Clear now. Thanks!


Simplify bash PROMPT_COMMAND handling

This change attempts to evaluate PROMPT_COMMAND in the same way that
bash would, adding support or many more cases and removing the check
that disables unsupported PROMPT_COMMANDS.
Fixes #155221
Fixes #146197

Tested true/false exit codes with:

Simple PS1
PROMPT_COMMAND echo
PROMPT_COMMAND function
PROMPT_COMMAND ;
PROMPT COMMAND &&
Starship
oh-my-posh
git-bash-prompt
preexec integration

It's possible PROMPT_COMMAND of the form ("first" "second") aren't working correctly, but I didn't totally understand how it's meant to be handled as no shell integration only seems to evaluate "first" in that case which we do.
FYI @meganrogge

Yep I was aware that other terminals with shell integration also don't support that kind of valid syntax. This looks much simpler, so probably not worth the added complexity to support it


close-on-select does not work with group-select

Reproduction Link
https://jsfiddle.net/wbeuyqv8/
Steps to reproduce
Create a multiselect with both group-select and close-on-select set to true. When a normal option is selected, the control closes itself. However, when the group options are selected, the control does not close itself.
Expected behaviour
When a group option is selected, the control should close itself.
Actual behaviour
When a group option is selected, the control does not close itself.

Is there any workaround on this?
Like listen on @input and calling something on the component by ref or something?

@shentao is my thought in previous comment achievable to do?
I can't find any documentation on how to call something on component to close select or something, but I guess that if it exists it would be ok for now, until a boolean property for close-on-group-select is created, or close-on-select can take values such as true/false/ìtem/group/all/ group-and-item` (just brainstorming).

@shentao I did a PULL request, with proposed solution.
https://github.com/shentao/vue-multiselect/pull/1206
I guess that would be the best solution, it's quick and respects the closeOnSelect-property and if you feel you can make fine-grained properties later on, but that's probably bigger effort. ;)

It still happens, is any solution for this?

Same here. Select is not closed after group was selected.

Well, my pull-request is accepted, should work, but NPM package isn’t updated. Maybe @shentao can do that when he finds time for it!? 😉

@Aterr and @001123 — since the npm-package isn’t updated, it doesn’t matter my pull-request is accepted and is in the code base… So we have to rely on @shentao doing a npm-release…

…or maybe change reference to shentao/vue-multiselect#master, if I understand it will use this github repo directly instead of latest released npm-package.
I haven’t tried that one though…

Hi, for those among you awaiting a new release, I have found a quick fix : add a ref property on the multiselect and call the deactivate() function when the @select event is fired :
<multiselect ref="mySelect" @select="selected" />
<script> export default {     methods: {         selected() {             this.$refs.mySelect.deactivate();         }     } } </script>


Feature/cavity reset cal

calibration routine for 2-step CLEAR pulse (McClure et al., 2016)
Protocol:

measure photon population after measurement using a Ramsey seq. (see above)
apply ideal CLEAR pulse (from theory)
sweep step amplitudes around the ideal values

Using:

CLEAR pulse shape (= measPulse followed by 2 steps)

TODO:

update pulse shape at the end of calibration (make the step amplitudes pulse parameters?)
metafile info supporting multiple msm't on same physical channel, but different logical channels

LGTM. Do you want to merge this now or after you add pulse shape update at the end?

I think you can merge now. I'm not sure if those parameters (CLEAR step amplitudes and length) are generic enough to become MEAS pulse parameters.


Goto-definition combined with .d.ts.map file produces location past the end of the file

TypeScript Version:  master
Code
See the test "tsserverProjectSystem project references" "goToDefinition" added in #24867.
CC @weswigham

That's the sourcemap that tsc generated when I tried it out. Would be nice if there were a way to programatically generate a.d.ts and a.d.ts.map inside the test instead of hardcoding.

There is! Some of the declaration map tests make use of it.

I'm going to hazard a guess that #24886 fixed this.

Since we're using the feature now, you can reproduce the error by clicking on any skipTrivia in textChanges.ts.

I'm going to hazard a guess that #24886 fixed this.

And we haven't done an lkg but only use light to build, so the change can't be seen in our own project yet.

Hi @weswigham, could you provide the location of the test helper that will generate a map?

This fourslash test does it

@weswigham Updated #24867 but it looks like the declaration emit hasn't changed in the master branch. Also, while working on that I've noticed that goto-definition doesn't always go to the right file either -- for example, in tsserverProjectSystem.ts, clicking on ProjectService in server.ProjectService takes me to scriptVersionCache.ts instead of editorServices.ts.

@andy-ms So it's worth noting that while we "fixed" your test, it's still entirely possible for us to return a position outside the bounds of a file for the end of a span we return (though probably much less likely now, since every identifier is actually sourcemapped). Do we need to guard against that anywhere?

We do call scriptInfo.positionToLineOffset on the result, but I don't see any asserts in there -- so we'll just return an out-of-bounds location to the editor, which should be able to handle it without crashing.


Add a student

User Story
As a teacher, I want to be able to add a student
AC
WHEN I click the add student button
THEN I should have a form to create a new student
AND When I submit the new student
THEN I should be brought back to the main management page with the new student on my list of students
Dev Notes

Use bootstrap forms
Make API post to create new student
Reload student management page upon completion


Fix meta variable misuse

Hi @ia0, are you able to give a quick summary of what this PR is all about and whether it's likely to break anything?

Hi @KodrAus,
This PR is about fixing #![deny(meta_variable_misuse)] lints (from https://github.com/rust-lang/rust/pull/62008). It should not break anything that was not already broken, but one of the change can probably be done differently. I'll add a comment on the given change.


Rename project to "Python-GraphBLAS" and package to graphblas

🤞

I pip-installed a beta release from PyPI, and everything works for me!

Merging 🚀 🎉


Error in build App

Hello,
I'm trying to build the App, but I'm getting the following errors in VS 2015 (MainPage.xaml.cs):
Error	CS1061	'MainPage' does not contain a definition for 'ChangingLocationMessage' and no extension method 'ChangingLocationMessage' accepting a first argument of type 'MainPage' could be found (are you missing a using directive or an assembly reference?)
Error	CS1061	'MainPage' does not contain a definition for 'HideLocationsButton' and no extension method 'HideLocationsButton' accepting a first argument of type 'MainPage' could be found (are you missing a using directive or an assembly reference?)
Error	CS1061	'MainPage' does not contain a definition for 'ChangingLocationMessage' and no extension method 'ChangingLocationMessage' accepting a first argument of type 'MainPage' could be found (are you missing a using directive or an assembly reference?)
Error	CS1061	'MainPage' does not contain a definition for 'HideLocationsButton' and no extension method 'HideLocationsButton' accepting a first argument of type 'MainPage' could be found (are you missing a using directive or an assembly reference?)

Solved after downloading again the Project.


Fix cache memory leaks

@cache is stored in the Class, not in the Object. So when multiple Safe objects were created, and get_contract() was called, cache only increased (also if the same Safe was created multiple times)
Use now @cached_property, which is binded to the object, so when the object is destroyed, so is the cached value
Closes #322
Related to #325
All the credit to @moisses89 who was the one realising of this behaviour

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

17 of 19 (89.47%)  changed or added relevant lines in 1 file are covered.
14 unchanged lines in 7 files lost coverage.
Overall coverage decreased (-0.08%) to 89.722%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

gnosis/safe/safe.py
17
19
89.47%

Files with Coverage Reduction
New Missed Lines
%

gnosis/safe/safe.py
1
87.5%

gnosis/eth/oracles/oracles.py
2
89.27%

gnosis/eth/typing.py
2
83.33%

gnosis/protocol/gnosis_protocol_api.py
2
89.25%

gnosis/safe/api/relay_service_api.py
2
52.27%

gnosis/safe/safe_tx.py
2
90.53%

gnosis/eth/ethereum_client.py
3
86.91%

Totals

Change from base Build<PHONE_NUMBER>:
-0.08%

Covered Lines:
3361

Relevant Lines:
3746

💛  - Coveralls

I would like to test something like this https://github.com/safe-global/safe-eth-py/pull/325/files#diff-dbf8b4d43e58fe9c2345cff856302940182d80b34590cfd26648a7076277d8c5R819 and also check that everything is ok with the memory from tx-service.

Should we continue reviewing the @cache decorator? For example this could generate other memory leak AFAIK.
    @cache
    def get_chain_id(self) -> int:
        """
        :return: ChainId returned by the RPC `eth_chainId` method. It should never change, so it's cached.
        """
        return int(self.w3.eth.chain_id)

Usually EthereumClient is created as a Singleton, so this is not an issue, but we should definitely review other places


plaintiffs and defendants should show up as .gather() in the interview order block

Right now the interview order block generates a trigger that doesn't actually work.

See #108 which I think states this more clearly

See #108 which I think states this more clearly


QueryExecutionException details field is coming null even after setting it

Basic information

Axon Framework version: 4.6.0
JDK version:  17
Complete executable reproducer if available (e.g. GitHub Repo): https://github.com/github4sanjay/spring-cqrs-axon-poc

Steps to reproduce
@Getter
public class ApplicationQueryExecutionException extends QueryExecutionException {

  public ApplicationQueryExecutionException(IException e) {
    super(e.getEx().code, e.getEx(), e);
  }
}

@SpringBootApplication
public class ProductApplication {

  public static void main(String[] args) {
    SpringApplication.run(ProductApplication.class, args);
  }

  @Autowired
  public void configure(
      ReactorQueryGateway reactorQueryGateway, ReactorCommandGateway reactorCommandGateway) {
    reactorCommandGateway.registerResultHandlerInterceptor(
        (command, result) ->
            result.onErrorMap(
                throwable -> {
                  var e = (CommandExecutionException) throwable;
                  var iException =
                      (IException) e.getDetails().orElse(CoreExceptions.INTERNAL_SERVER_ERROR);
                  throw iException.getEx();
                }));

    reactorQueryGateway.registerResultHandlerInterceptor(
        (query, result) ->
            result.onErrorMap(
                throwable -> {
                  var e = (QueryExecutionException) throwable;
                  var iException =
                      (IException) e.getDetails().orElse(CoreExceptions.INTERNAL_SERVER_ERROR);
                  throw iException.getEx();
                }));
  }
}

@QueryHandler
  public Product getProductById(GetProductByIdQuery getProductByIdQuery) {
    return productRepository
        .findById(getProductByIdQuery.getId().toString())
        .orElseThrow(() -> new ApplicationQueryExecutionException(PRODUCT_NOT_FOUND));
  }

Expected behaviour
In registerResultHandlerInterceptor, details field should come whatever was set during throwing an exception wherever ApplicationQueryExecutionException is defined.
Actual behaviour
If i keep ApplicationQueryExecutionException in same repo then I am able to receive the details in registerResultHandlerInterceptor but when I try to keep ApplicationQueryExecutionException in shareable module/java library then details field start coming null not sure why its happening.
Working with https://github.com/github4sanjay/spring-cqrs-axon-poc/blob/master/product/src/main/java/com/example/product/exception/ApplicationQueryExecutionException.java#L8
but not working with https://github.com/github4sanjay/spring-cqrs-axon-poc/blob/master/spring-axon-reactor/src/main/java/com/example/spring/axon/reactor/ApplicationQueryExecutionException.java#L8
even though both are same exact class but in different package.

after removing devtools it works, really dont know the reason

I'd be guessing here, but I'd wager that has to do with how Spring Boot DevTools works.
When we introduced the Spring Boot DevTools support to the framework, we had to mark the *.jar files users would depend on so that they're included in a DevTools-initiated restart.
Perhaps you have to define your other module in such a spring-devtools.properties file (under META-INF) for it to work.


Distributed: problems on rollback with async replication in case of conflict

This has been reproduced by concurrent change to graph in transactions with async replication.

Fixed in 2.1.2-SNAPSHOT and 2.2.0-SNAPSHOT.


Match args using specs/constraints rather than just equality

Most of the time expectations specify literal parameter values that are compared for equality against the actual parameters of invoked methods. For example:
allow(calculator).add(2, 2).and_return(5)
Sometimes, however, you will need to define looser constraints over parameter values to clearly express the intent of the test or to ignore parameters (or parts of parameters) that are not relevant to the behaviour being tested. For example:
allow(calculator).sqrt(less_than(0)).and_raise(ValueError)
allow(log).append(equal_to(Log.ERROR), contains_string("sqrt"))

Loose parameter constraints can be defined by specifying matchers for each parameter. Matchers are created by factory functions, such as less_than, equal_to and contains_string in the example above, to ensure that the expectation is easy to read.
See http://www.jmock.org/matchers.html for motivation and details.

It would also be interesting to be able to define, in the case of multiple args, that some of the args can have any value.

thanks! Merry Christmas


Wfcore 5406 illegal access deny

Experiment to further validate #4591

Core - Full Integration Build 10586 outcome was UNKNOWN using a merge of d53876e5566167b2f462c4a2283fcd100898565c
Summary: Canceled (Exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 00:03:46

Core - Full Integration Build 10663 outcome was UNKNOWN using a merge of 9da9880bea412bb45bb22055f61fa14ac2f144b0
Summary: Canceled (Tests passed: 2475, ignored: 50; exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 00:23:23

Core - Full Integration Build 10589 outcome was UNKNOWN using a merge of 9da9880bea412bb45bb22055f61fa14ac2f144b0
Summary: Canceled (Tests passed: 583, ignored: 8; exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 00:26:42

Closing; I got the data I wanted from the CI runs and https://ci.wildfly.org/viewLog.html?buildId=257314&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperimentsJdk11


Handle harvester loading in a route guard to better handle the unauthenticated method.

Summary
This is done by providing a 404l page which is authenticated.
Fixes #11350
Technical notes summary
We will still need the fix from https://github.com/rancher/dashboard/pull/11359/commits/be1e27b0630d32d2309c5d3969643f5fa84df014 for prod.
Areas or cases that should be tested
404 routing.
Harvester routing.
Screenshot/Video
Regular 404:
https://github.com/rancher/dashboard/assets/55104481/5d3d2fc8-0cbd-4d20-99e0-59dda8a0d8e3
Harvester 404:
https://github.com/rancher/dashboard/assets/55104481/310f10e4-6881-402f-8952-a55f9b846d82
I noticed a flicker of the resource page on this one. I can only reproduce this on the harvester cluster  but it's in master and unrelated to both this PR and harvester itself. If anyone else can reproduce this I'll resolve it as a separate issue.
Checklist

[x] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
[x] The PR has a Milestone
[x] The PR template has been filled out
[x] The PR has been self reviewed
[x] The PR has a reviewer assigned
[x] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
[x] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

I'll open for review once tests pass again. Looks like we may have had a node version change. This change was passing all unit and e2e tests on friday.

I think we need to be really clear what the issue is because the way that you've described it and the commit you added makes me think there's a misunderstanding of how navigation guards work.

Just as a tidy up I added async/await to the beforeEach hooks (though i don't think vue router awaits them).

You're right, vue-router isn't awaiting them. It's waiting for the the hook passed to beforeEach to call next(). This change doesn't actually safeguard against anything.

When testing I saw all nav guards start in order, but finish out of order.

The call to next() is what will call the next navigation guard in the list. You will not see the caller finish until the callee finishes because it's going in stack order.
function b() {
   console.log('b');
}

function a() {
   console.log('a')
   b()
   console.log('c')
}

a();

We will see abc printed which indicates a() finished executing after b() finished. This is the exact behavior we should see with the beforeEach navigation guards. If you're seeing out of stack order then we do have a problem and we should address that. But that's not what I noticed while working on this.

I'll go ahead and merge once master has all tests pass or we decide to skip.


Option to show only country code in phone country

Can you give more detail about what you want?

I think it would be good to have the option to show only the country code in the select field when selected, the option popover is good with both name of country and code but when selected it is also showing both country name and code which is not necessary in most cases, would he better to have option to only show country code when selected


refactor(RadialMenu): Change visibility of menuButtons to private

There were the following issues with your Pull Request

Commit: a870d6a26998183fe79becf8275b14eecaf16eb7
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

There were the following issues with your Pull Request

Commit: f46c4bb135e620f4c08e21c3b5590ee72bbce9ad
Commits must be in the following format: %{type}(%{scope}): %{description}
Your subject line is longer than 72 characters

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

this shouldn't be private, should be protected so it can be changed in inherited scripts.

I dont think this should be set to private or protected, if people are trying to add menu buttons at runtime and then disable/reenable the script to generate the new buttons then they'll need access to this parameter.


vtable read faild

can;t read vtable win7 sp1 Chinese language
https://puu.sh/CIGSV/d5f83f26e3.png

this is bug still not be fixed.....on WIN10 1809
https://puu.sh/HHVvZ/3b882cbdbe.png

Try pressing the little camera icon

thank.  after pressing the little camera icon, it  work. but why we should do this??xD


Fixes to Serialization

Additional serializaiton tests
Support for set() and frozenset()
Refactorings

@braxtonmckee this is ready for another look from you. I added a number of serialization tests that are failing (which I marked with @unittest.skip) so that we have an idea of some of the things that pickle does that we're not, but not have to implement them right-away.

@braxtonmckee this is the second PR. I've rebased it on top of #16


Mobile Navbar not Opening

Navbar briefly opens with no background:

This has been fixed for a while, but wasn’t tagged in a PR


[FR] Provide conditional to test if document is tagged

I'd like to suggest the provision of a conditional to test whether "the document is supposed to be tagged and the tagging infrastructure (currently provided by tagpdf) is expected to be available". Let's say \tag_if_enabled:TF.
I'm aware, of course, of \tag_if_active:TF, but it falls short for a couple of reasons:

The kernel does provide a dummy definition for it, but only at begindocument, so a package cannot count on its existence in the preamble.
\tag_if_active:TF tests if tagging is "currently active", depending on \l__tag_active_struct_bool and \l__tag_active_mc_bool which may be toggled by \tag_stop:/\tag_start: and friends. Which is different from "the document is supposed to be tagged".

As use case for motivation, my attempts to add tagging support to postnotes included a number of tasks which must be globally performed as long as the document is intended to be tagged, regardless of current state of "activation" of tagging (of  \l__tag_active_struct_bool and \l__tag_active_mc_bool, that is). These are basically a number of cross-references and passing information around from the mark to the note (and back). But these must be available at all times. Suppose someone stops tagging at the place the mark is placed but then turns it on again when the note is supposed to be printed. If the cross-reference is not there, there's no hope the latter will work. (True, in this case, things will likely go wrong for other reasons, but I hope you get what I mean). However, there's also no reason to set these things if the document is not supposed to be tagged at all.
I'm currently testing for:
\bool_lazy_and:nnT
  { \cs_if_exist_p:N \tag_if_active_p: }
  { \tag_if_active_p: }

And expecting no one has any reason to call \tag_stop: in the preamble. But it feels weird...

I just met another use case which may help motivate this (beyond "infrastructure cross-refs"). If a pair of sockets surrounding some content needs to suspend tagging for the length of said content, we cannot use \tag_socket_use:n, but need to rely on \socket_use:n. Hence, the workings of these sockets would depend on the plugs assigned to them, and the plugs with tagging content should be assigned under some condition. And, in my view, the right condition is "if the document is supposed to be tagged". The same general reasoning would apply if we were working with a couple of dedicated functions instead of sockets.
Practical case in hand, latex-lab-footmisc defines \multfootsep to include the tagging code (for reasons, which I'm not questioning). So anyone else trying to add support for such feature meets the situation where the structure of the tagging code depends on whether footmisc is loaded or not. A reasonable thing to do is suspend/resume tagging around \multfootsep, which leads to the situation above. Of course, nothing unique there, \tag_suspend:n and \tag_resume:n exist because they are needed and the tagpdf documentation acknowledges that.

If you need to suspend tagging you should normally do something like
\UseTaggingSocket{...}\SuspendTagging{\endnote} ... \ResumeTagging{\endnote}\UseTaggingSocket . (One could hide the suspend command inside the socket, but it looks more symmetric like this.)
But it sounds wrong to go through some suspend/resume hoops to get around an awkward definition of \multfootsep. I think one should look at what the various packages/classes are doing here and try to find a saner solution.


Jupyter Server Initialization Failed

Jupyter Server Initialization Failed
Jupyter Server, which is a prerequisite for JupyterLab Desktop, did not initialize properly.
This might be because of an issue with the selected environment. You can change environment to try a different server using buttons below.
If this does not seem right, please report this issue in the JupyterLab Desktop repository, providing the error details presented below:
Error: spawn cmd.exe ENOENT
That is the message I get when I try to open Jupyter Lab Desktop.
If I follow with the "Change Environment" button then it pops this dialog window with two options:
**Set Python Environment
Select the Python executable in the conda or virtualenv environment you would like to use for JupyterLab Desktop. Python packages in the environment selected need to meet the following requirements: jupyterlab >=3.1.0. Prebuilt extensions installed in the selected environment will also be available in JupyterLab Desktop.
[ ]Use the bundled Python environment
[ ]Use a custom Python environment
C:\Users<user>\AppData\Roaming\jupyterlab-desktop\jlab_server\python.exe
Select Python path
Apply and restart
Cancel**
For either option I choose I land on the same message with "Error: spawn cmd.exe ENOENT"

I seem to have the same issue on Mac. I'm running a fresh install.
Error: Jupyter Server process terminated before the initialization completed
➜  ~ jlab --version
3.4.6-1

➜  ~ sw_vers
ProductName:		macOS
ProductVersion:		13.0
BuildVersion:		22A380

main.log

I had a similar symptom on a Windows 10 PC and investigated the cause and found that the environment variable PATH was set to the wrong value and cmd.exe could not start.
I found a way by searching the web for keywords like "reset environment variables in Windows 10" and was able to get it installed.
However, this solution is (or at least, seems) not guaranteed by any authorities and, of course, might have a negative impact on already installed applications, so it is better to use it as a last resort.

@tos-kamiya did you run into issues when launching from command prompt or UI or both?
can you describe what was wrong with the PATH? we include the desktop app process' environment variables when launching the server.
by the way, have you tried the latest version 3.6.1-1?

On one Windows 10 PC, I attempted to install JupyterLab Destkop 3.6.1-1.

ran JupyterLab-Setup-Windows.exe and finished JupyterLab setup.
When I tried to run JupyterLab (GUI app), I got a message "Python envrionment not found. Install using the bundled installer or Change the default Python environment. Install using the bundled installer or Change the default Python environment.
When I clicked on "Install using the bundled installer," I got the error message "Error: spawn cmd.exe ENOENT. If it had executed successfully, the dialog "Welcome to JupyterLabDesktopAppServer 3.6.1-1(64-bit) Setup" would have appeared. (Actually, this is what was displayed after troubleshooting was complete.)
After some investigation, I found that the environment variables on that PC were strange: the directory where cmd.exe is located (C:\Windows\System32) was not stored in the path variable.
By resetting the Windows PC environment variables, I successfully proceeded to install JupyterLabDektopAppServer.

I hope this information is helpful.

Closing this issue as some users have a workaround. Please try again with the latest version and create new issue if persists. Latest version provides more detailed logs.


mismatched url from cache once '&' is included

When compiling the application user is trying to push to cloud foundry, at this time the cache may be very helpful for offline platforms. Unluckily once the cached resource includes '&' as the file name, it can be hit due to the mismatched cache encoding name. e.g.:
http://www14.software.ibm.com/cgi-bin/weblap/lap.pl?la_formnum=&li_formnum=L-SMKR-AVSEUH&title=IBM�+SDK%2C+Java�+Technology+Edition%2C+Version+8.0&l=en
The solutions would look like below:

+++ b/resources/download_buildpack_cache.rb
@@ -152,7 +152,7 @@ class BuildpackCache
   #
   # @param [String] uri location of the remote resource
   def filename(uri)
-    "#{URI.escape(uri, ':/')}.cached"
+    "#{URI.escape(uri, ':/&')}.cached"
   end

could you help to review? or you want me to submit the code and send out a pull request?

@pivotal-bin-ju That looks ok. Can you please submit a pull request with this change?

Fixed in #408

thanks a lot, Jarek!
On Thu, Nov 15, 2018 at 2:31 AM Jarek Gawor<EMAIL_ADDRESS>wrote:

Fixed in #408
https://github.com/cloudfoundry/ibm-websphere-liberty-buildpack/pull/408
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/ibm-websphere-liberty-buildpack/issues/407#issuecomment-438768765,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASo6M7cQniRY6ZrCtm8g1ft_lNn-H_nwks5uvGGLgaJpZM4Yc53B
.

--
鞠国滨       Bin Ju
+86<PHONE_NUMBER>7


Update rm2fb to start before launcher.service

Thanks for the PR! It looks good, although I’m not sure whether remux should be marked as conflicting with other launchers since it doesn’t show anything on screen unless triggered (thoughts @raisjn?).

Remux does conflict with oxide as they both control applications with drastically different mechanisms. So having Oxide and remux run at the same time will have bad side-effects.

Yes you’re right, but remux doesn’t conflict with Xochitl, for example. Should we just leave the Conflicts list for the remux unit?

Good point. Although I believe remux assumes that xochitl isn't started before it? Not sure though.

If I understand remux correctly, it does not (but @ raisjn can correct me). It will detect that Xochitl (or any other app) is already running by scanning the process list.

I reverted the changes for the remux unit then.