An extra white space in the -log_folder parameter makes the program exit with a FailedRecognitionError

The below command doesn't work as there is an additional space before "/my_nfs/logs" for the -log_folder parameter.
docker run --rm -ti -v /home/ml/my_nfs:/my_nfs docker.io/batchkit/speech-batch-kit:latest -config /my_nfs/config.yaml -input_folder /my_nfs/audio_files -output_folder /my_nfs/transcriptions -log_folder   /my_nfs/logs -file_log_level DEBUG -nbest 1 -m ONESHOT -diarization None -profanity Raw -language en-US -console_log_level DEBUG
The output we get is only console based as the logs also doesn't get saved in this scenario.
Please find the logs below:
2020-10-27 19:30:43.472:INFO:LoggingListenerProcess:Log folder \udcc2\udca0/my_nfs/logs created successfully
2020-10-27 19:30:43.477:INFO:MainProcess:Starting a watch on file: /my_nfs/config.yaml
2020-10-27 19:30:43.477:INFO:MainProcess:Orchestrator created by process: 1
2020-10-27 19:30:43.477:INFO:MainProcess:client.py: run(): Running:  OneShotClient  with settings: Settings(input_folder='/my_nfs/audio_files', input_list=None, output_folder='/my_nfs/transcriptions', apiserver_port=5000, scratch_folder='/my_nfs/transcriptions/.scratch', log_folder='\udcc2\udca0/my_nfs/logs', store_combined_json=False, config_file='/my_nfs/config.yaml', strict_configuration_validation=False),  and speech config: SpeechSDKBatchConfig({'combine_results': False, 'language': 'en-US', 'nbest': 1, 'diarization': 'None', 'profanity': 'Raw', 'sentiment': False, 'allow_resume': False})
2020-10-27 19:30:43.869:DEBUG:MainProcess:BatchRequest subtypes on sys.path identified: [<class 'batchkit_examples.speech_sdk.batch_request.SpeechSDKBatchRequest'>]
2020-10-27 19:30:43.900:DEBUG:MainProcess:BatchRequest subtypes on sys.path identified: [<class 'batchkit_examples.speech_sdk.batch_request.SpeechSDKBatchRequest'>]
2020-10-27 19:30:43.900:INFO:MainProcess:OneShotClient:  Submitting SpeechSDKBatchRequest with 2 files.
2020-10-27 19:30:43.901:INFO:MainProcess:ApiServer: submit() request:  {"py/object": "batchkit_examples.speech_sdk.batch_request.SpeechSDKBatchRequest", "batch_id":<PHONE_NUMBER>88503786707517342978000830611, "files": ["/my_nfs/audio_files/jurrasic1_16k_mono.wav", "/my_nfs/audio_files/sotl1.wav"], "combine_results": false, "language": "en-US", "diarization": "None", "nbest": 1, "profanity": "Raw", "allow_resume": false, "enable_sentiment": false}
2020-10-27 19:30:43.902:INFO:MainProcess:OneShotClient:  Waiting on batch id:<PHONE_NUMBER>88503786707517342978000830611, in status: BatchStatusEnum.waiting
2020-10-27 19:30:43.902:INFO:MainProcess:ApiServer: watch() request:  batch_id:<PHONE_NUMBER>88503786707517342978000830611, target_state: BatchStatusEnum.done, timeout: 30
2020-10-27 19:30:43.921:DEBUG:MainProcess:Original configuration:
2020-10-27 19:30:43.921:DEBUG:MainProcess:MyContainer: {
  "concurrency": 2,
  "host": "<IP_ADDRESS>",
  "port": 5000
}
2020-10-27 19:30:43.921:DEBUG:MainProcess:Normalized configuration:
2020-10-27 19:30:43.921:DEBUG:MainProcess:MyContainer: {
  "concurrency": 2,
  "host": "<IP_ADDRESS>",
  "isCloudService": false,
  "isSecure": false,
  "language": "en-US",
  "port": 5000,
  "rtf": 3.0,
  "startConcurrency": 2
}
2020-10-27 19:30:43.928:INFO:MainProcess:Set new EndpointManagers after hot-swap: {'MyContainer': {'concurrency': 2, 'host': '<IP_ADDRESS>', 'port': 5000, 'rtf': 3.0, 'language': 'en-US', 'isCloudService': False, 'isSecure': False, 'startConcurrency': 2}}
2020-10-27 19:30:43.929:INFO:MainProcess:Orchestrator: Starting batch<PHONE_NUMBER>88503786707517342978000830611
2020-10-27 19:30:43.933:DEBUG:MainProcess:Updating singleton run_summary: /my_nfs/transcriptions/run_summary.json
2020-10-27 19:30:43.934:INFO:MainProcess:write_json_file_atomic():  Atomically wrote file /my_nfs/transcriptions/run_summary.json
2020-10-27 19:30:43.936:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  will try to steal work
2020-10-27 19:30:43.936:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  stole work and will delegate to a worker.
2020-10-27 19:30:43.936:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  will try to steal work
2020-10-27 19:30:43.936:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  stole work and will delegate to a worker.
2020-10-27 19:30:43.937:INFO:HotswapGen0_MyContainer_PoolWorker-2:Processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-2
2020-10-27 19:30:43.937:INFO:HotswapGen0_MyContainer_PoolWorker-3:Processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-3
2020-10-27 19:30:43.940:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProc
2020-10-27 19:30:43.940:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProc
2020-10-27 19:30:44.130:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProc
2020-10-27 19:30:44.130:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-3

2020-10-27 19:30:44.130:WARNING:HotswapGen0_MyContainer_PoolWorker-3:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-3
2020-10-27 19:30:44.130:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProc
2020-10-27 19:30:44.131:INFO:HotswapGen0_MyContainer_PoolWorker-3:Processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-3
2020-10-27 19:30:44.131:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-2

2020-10-27 19:30:44.131:WARNING:HotswapGen0_MyContainer_PoolWorker-2:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-2
2020-10-27 19:30:44.131:INFO:HotswapGen0_MyContainer_PoolWorker-2:Processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-2
2020-10-27 19:30:44.132:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProc
2020-10-27 19:30:44.133:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProc
2020-10-27 19:30:44.211:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProc
2020-10-27 19:30:44.211:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProc
2020-10-27 19:30:44.211:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-2

2020-10-27 19:30:44.211:WARNING:HotswapGen0_MyContainer_PoolWorker-2:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-2
2020-10-27 19:30:44.211:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-3

2020-10-27 19:30:44.211:WARNING:HotswapGen0_MyContainer_PoolWorker-3:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-3
2020-10-27 19:30:44.212:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  will try to steal work
2020-10-27 19:30:44.212:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  stole work and will delegate to a worker.
2020-10-27 19:30:44.212:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  will try to steal work
2020-10-27 19:30:44.212:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  stole work and will delegate to a worker.
2020-10-27 19:30:44.213:INFO:HotswapGen0_MyContainer_PoolWorker-4:Processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-4
2020-10-27 19:30:44.213:INFO:HotswapGen0_MyContainer_PoolWorker-5:Processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-5
2020-10-27 19:30:44.216:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProc
2020-10-27 19:30:44.216:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProc
2020-10-27 19:30:44.296:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProc
2020-10-27 19:30:44.296:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProc
2020-10-27 19:30:44.296:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-4

2020-10-27 19:30:44.296:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-5

2020-10-27 19:30:44.297:WARNING:HotswapGen0_MyContainer_PoolWorker-4:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-4
2020-10-27 19:30:44.297:WARNING:HotswapGen0_MyContainer_PoolWorker-5:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-5
2020-10-27 19:30:44.297:INFO:HotswapGen0_MyContainer_PoolWorker-4:Processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-4
2020-10-27 19:30:44.297:INFO:HotswapGen0_MyContainer_PoolWorker-5:Processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-5
2020-10-27 19:30:44.299:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProc
2020-10-27 19:30:44.299:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProc
2020-10-27 19:30:44.378:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProc
2020-10-27 19:30:44.378:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProc
2020-10-27 19:30:44.379:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-5

2020-10-27 19:30:44.379:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-4

2020-10-27 19:30:44.379:WARNING:HotswapGen0_MyContainer_PoolWorker-5:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-5
2020-10-27 19:30:44.379:WARNING:HotswapGen0_MyContainer_PoolWorker-4:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-4
2020-10-27 19:30:44.379:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  will try to steal work
2020-10-27 19:30:44.379:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  stole work and will delegate to a worker.
2020-10-27 19:30:44.379:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  will try to steal work
2020-10-27 19:30:44.379:CRITICAL:MainProcess:Endpoint manager HotswapGen0_MyContainer has failed 4 consecutive recognitions on endpoint <IP_ADDRESS>:5000
2020-10-27 19:30:44.379:INFO:HotswapGen0_MyContainer_PoolWorker-2:Processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-2
2020-10-27 19:30:44.380:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  stole work and will delegate to a worker.
2020-10-27 19:30:44.380:INFO:HotswapGen0_MyContainer_PoolWorker-3:Processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-3
2020-10-27 19:30:44.381:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProc
2020-10-27 19:30:44.382:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProc
2020-10-27 19:30:44.461:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProc
2020-10-27 19:30:44.461:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProc
2020-10-27 19:30:44.461:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-3

2020-10-27 19:30:44.461:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-2

2020-10-27 19:30:44.461:WARNING:HotswapGen0_MyContainer_PoolWorker-3:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-3
2020-10-27 19:30:44.461:WARNING:HotswapGen0_MyContainer_PoolWorker-2:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-2
2020-10-27 19:30:44.461:INFO:HotswapGen0_MyContainer_PoolWorker-3:Processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-3
2020-10-27 19:30:44.461:INFO:HotswapGen0_MyContainer_PoolWorker-2:Processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-2
2020-10-27 19:30:44.463:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProc
2020-10-27 19:30:44.463:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProc
2020-10-27 19:30:44.543:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProc
2020-10-27 19:30:44.543:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProc
2020-10-27 19:30:44.543:DEBUG:HotswapGen0_MyContainer_PoolWorker-3:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-3

2020-10-27 19:30:44.543:DEBUG:HotswapGen0_MyContainer_PoolWorker-2:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-2

2020-10-27 19:30:44.543:WARNING:HotswapGen0_MyContainer_PoolWorker-3:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-3__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-3
2020-10-27 19:30:44.543:WARNING:HotswapGen0_MyContainer_PoolWorker-2:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-2__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-2
2020-10-27 19:30:44.543:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  will try to steal work
2020-10-27 19:30:44.543:CRITICAL:MainProcess:Endpoint manager HotswapGen0_MyContainer has failed 5 consecutive recognitions on endpoint <IP_ADDRESS>:5000
2020-10-27 19:30:44.544:CRITICAL:MainProcess:Endpoint manager HotswapGen0_MyContainer has failed 6 consecutive recognitions on endpoint <IP_ADDRESS>:5000
2020-10-27 19:30:44.544:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  stole work and will delegate to a worker.
2020-10-27 19:30:44.544:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  will try to steal work
2020-10-27 19:30:44.544:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  stole work and will delegate to a worker.
2020-10-27 19:30:44.544:INFO:HotswapGen0_MyContainer_PoolWorker-4:Processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-4
2020-10-27 19:30:44.544:INFO:HotswapGen0_MyContainer_PoolWorker-5:Processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-5
2020-10-27 19:30:44.546:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProc
2020-10-27 19:30:44.546:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProc
2020-10-27 19:30:44.625:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProc
2020-10-27 19:30:44.625:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProc
2020-10-27 19:30:44.625:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-4

2020-10-27 19:30:44.625:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-5

2020-10-27 19:30:44.625:WARNING:HotswapGen0_MyContainer_PoolWorker-5:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-5
2020-10-27 19:30:44.625:WARNING:HotswapGen0_MyContainer_PoolWorker-4:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-4
2020-10-27 19:30:44.626:INFO:HotswapGen0_MyContainer_PoolWorker-5:Processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-5
2020-10-27 19:30:44.626:INFO:HotswapGen0_MyContainer_PoolWorker-4:Processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, with process: HotswapGen0_MyContainer_PoolWorker-4
2020-10-27 19:30:44.627:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProc
2020-10-27 19:30:44.627:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Starting FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProc
2020-10-27 19:30:44.705:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProc
2020-10-27 19:30:44.705:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Finished FileRecognizer.__recognize() in subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProc
2020-10-27 19:30:44.706:DEBUG:HotswapGen0_MyContainer_PoolWorker-5:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-5

2020-10-27 19:30:44.706:DEBUG:HotswapGen0_MyContainer_PoolWorker-4:Exception details: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 143, in recognize
    audio_duration = self.__recognize_in_subproc(self._filepath, json_data, cancellation_token)
  File "/usr/local/lib/python3.6/dist-packages/batchkit_examples/speech_sdk/recognize.py", line 231, in __recognize_in_subproc
    raise FailedRecognitionError(err_msg)
batchkit.utils.FailedRecognitionError: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-4

2020-10-27 19:30:44.706:WARNING:HotswapGen0_MyContainer_PoolWorker-5:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-5
2020-10-27 19:30:44.706:WARNING:HotswapGen0_MyContainer_PoolWorker-4:FailedRecognitionError happened, must terminate the recognition.Details: Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-4
2020-10-27 19:30:44.706:DEBUG:MainProcess:EndpointManager name: HotswapGen0_MyContainer  will try to steal work
2020-10-27 19:30:44.706:CRITICAL:MainProcess:Endpoint manager HotswapGen0_MyContainer has failed 7 consecutive recognitions on endpoint <IP_ADDRESS>:5000
2020-10-27 19:30:44.706:INFO:MainProcess:Orchestrator: Completed batch<PHONE_NUMBER>88503786707517342978000830611
2020-10-27 19:30:44.706:CRITICAL:MainProcess:Endpoint manager HotswapGen0_MyContainer has failed 8 consecutive recognitions on endpoint <IP_ADDRESS>:5000
2020-10-27 19:30:46.938:DEBUG:MainProcess:Updating singleton run_summary: /my_nfs/transcriptions/run_summary.json
2020-10-27 19:30:46.939:INFO:MainProcess:write_json_file_atomic():  Atomically wrote file /my_nfs/transcriptions/run_summary.json
2020-10-27 19:30:49.944:INFO:MainProcess:Orchestrator: Updated batch status to Done:<PHONE_NUMBER>88503786707517342978000830611
2020-10-27 19:30:49.946:INFO:MainProcess:OneShotClient:  Moving files (intermediate): /my_nfs/transcriptions/.scratch/batch_331792578788503786707517342978000830611 -> /my_nfs/transcriptions
2020-10-27 19:30:49.947:INFO:MainProcess:OneShotClient:  Moving files (final): /my_nfs/transcriptions/.scratch/batch_331792578788503786707517342978000830611 -> /my_nfs/transcriptions
2020-10-27 19:30:49.947:INFO:MainProcess:OneShotClient: Batch id:<PHONE_NUMBER>88503786707517342978000830611 is finished.
2020-10-27 19:30:49.947:INFO:MainProcess:OneShotClient:  Cleaning up scratch directory for single batch:<PHONE_NUMBER>88503786707517342978000830611
2020-10-27 19:30:49.947:INFO:MainProcess:BatchStatusProvider: rm_batch(): Removing batch_id:<PHONE_NUMBER>88503786707517342978000830611
2020-10-27 19:30:49.948:INFO:MainProcess:OneShotClient:  Requesting Orchestrator to stop.
2020-10-27 19:30:49.950:INFO:MainProcess:EndpointManager name: HotswapGen0_MyContainer  was requested to stop while stealing work.
2020-10-27 19:30:49.959:DEBUG:MainProcess:Original configuration:
2020-10-27 19:30:49.959:DEBUG:MainProcess:MyContainer: {
  "concurrency": 2,
  "host": "<IP_ADDRESS>",
  "port": 5000
}
2020-10-27 19:30:49.959:DEBUG:MainProcess:Normalized configuration:
2020-10-27 19:30:49.959:DEBUG:MainProcess:MyContainer: {
  "concurrency": 2,
  "host": "<IP_ADDRESS>",
  "isCloudService": false,
  "isSecure": false,
  "language": "en-US",
  "port": 5000,
  "rtf": 3.0,
  "startConcurrency": 2
}
2020-10-27 19:30:49.960:INFO:MainProcess:Output list:
2020-10-27 19:30:49.960:INFO:MainProcess:Result for: /my_nfs/audio_files/jurrasic1_16k_mono.wav: {
  "audio_duration": null,
  "cached": false,
  "can_retry": true,
  "endpoint": "ws://<IP_ADDRESS>:5000",
  "error_type": "FailedRecognitionError",
  "failed_reason": "Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-4__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/jurrasic1_16k_mono.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-4",
  "filepath": "/my_nfs/audio_files/jurrasic1_16k_mono.wav",
  "latency": 0.08022069931030273,
  "passed": false,
  "retries": 11,
  "thread": "HotswapGen0_MyContainer_PoolWorker-4"
}
2020-10-27 19:30:49.960:INFO:MainProcess:Result for: /my_nfs/audio_files/sotl1.wav: {
  "audio_duration": null,
  "cached": false,
  "can_retry": true,
  "endpoint": "ws://<IP_ADDRESS>:5000",
  "error_type": "FailedRecognitionError",
  "failed_reason": "Terminating signum: 11 was received in sdk subproc: HotswapGen0_MyContainer_PoolWorker-5__SDKRequestChildProcwhile processing file: /my_nfs/audio_files/sotl1.wav on endpoint: ws://<IP_ADDRESS>:5000, caught by supervisor: HotswapGen0_MyContainer_PoolWorker-5",
  "filepath": "/my_nfs/audio_files/sotl1.wav",
  "latency": 0.0802311897277832,
  "passed": false,
  "retries": 11,
  "thread": "HotswapGen0_MyContainer_PoolWorker-5"
}
2020-10-27 19:30:49.960:INFO:MainProcess:Decoded 0.00 seconds in 6.48 seconds on 1 decoders for a ratio of 0.00
2020-10-27 19:30:49.960:INFO:MainProcess:Processed 2/2 files, 0 passed, 0 fetched from cache and 2 failed.
2020-10-27 19:30:49.960:INFO:MainProcess:Total retries: 22
2020-10-27 19:30:49.960:INFO:MainProcess:
Failed recognitions (2):

2020-10-27 19:30:49.960:INFO:MainProcess: END POINT                     AUDIO FILE
2020-10-27 19:30:49.960:INFO:MainProcess: ws://<IP_ADDRESS>:5000       /my_nfs/audio_files/jurrasic1_16k_mono.wav
2020-10-27 19:30:49.961:INFO:MainProcess: ws://<IP_ADDRESS>:5000       /my_nfs/audio_files/sotl1.wav
2020-10-27 19:30:49.961:WARNING:MainProcess:Overall # files failed: 2
2020-10-27 19:30:49.961:INFO:MainProcess:client.py: run(): Finished!
Killed:  18
Killed:  19
Killed:  20
Killed:  21

Hi @Navaneethsen, thanks for reporting. Would you please say which terminal you are using and what platform you are running on? Is it native Linux, WSL2 on Windows, etc? And were you able to get everything working fine when you remove the extra space? We will look through our documentation and try to remove that extra space. Thanks.

Hi @andrew, I am using the container in an Ubuntu machine.
Yes, I am able to get it working fine after I remove the extra space. I
have already raised a bug against  the documentation as well.
On Thu, 29 Oct 2020 at 04:12, Andrew Wald<EMAIL_ADDRESS>wrote:

Hi @Navaneethsen https://github.com/Navaneethsen, thanks for reporting.
Would you please say which terminal you are using and what platform you are
running on? Is it native Linux, WSL2 on Windows, etc? And were you able to
get everything working fine when you remove the extra space? We will look
through our documentation and try to remove that extra space. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/batch-processing-kit/issues/11#issuecomment-718314084,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHC5K2ASYWDQ5A5YKIZBIDSNDFPDANCNFSM4TBJHKPQ
.


Daniil: Watch +91<PHONE_NUMBER>

Daniil requests the watch of the watch_number +91<PHONE_NUMBER>. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by ArtOfCode in Charcoal HQ


Is it necessary to remove road points when pre-training?

Hi, thank you for your excellent work.
I am trying to reimplement your code and my codebase does not support removing points. I am wondering if it is necessary to remove the road points when pre-training. Will not removing hurt the performance?
Thank you.

Hi, thanks for your attention.
Does the 'removing points' refers to the ground points?
If so, actually, we donot remove the ground points, but we just record the
indices of the ground points, so as to reduce the sampling on the massive
ground.
This process assures the class balance of proposals, and improves the
performance by ~0.5mAP.
Hope this helps.
Best,
Junbo
Hiusam @.***> 于2022年10月19日周三 20:37写道：

Hi, thank you for your excellent work.
I am trying to reimplement your code and my codebase does not support
removing points. I am wondering if it is necessary to remove the road
points when pre-training. Will not removing hurt the performance?
Thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/yinjunbo/ProposalContrast/issues/7, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHCPIYOTUB2DNUPFBJCKT7TWD7TQDANCNFSM6AAAAAARJCQA5M
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Update user balance on reject vacation request

Closed as fixed, please if you notice that the issue still exists open it again.


Motif Breaking

We need to adress to what extent a bQTL's alternate allele is breaking a motif. Encode might not be comprehensive enough. Need to speak to Breeshey to retrieve those. Then see how the disturbed binding is concordant with the effect of the bQTL (ATE or CATE).

File was sent over by Breeshey and seems concordant with Encode


🐛 Auth - Cannot login, CORS erros

Describe the issue that you're seeing. Any Loom videos or screenshots usually help a lot!
Some users are experienceing login issues.
There are some CORS errors in the console, not sure if these are related.

FIgure: cannot login, console errors
Usually clearing the cache will resolve the issue.
Reproduction
https://github.com/sswconsulting/ssw.website
Steps to reproduce

Try Sign in
popup window opens
Never signs

System Info
System:
    OS: macOS 14.0
    CPU: (12) arm64 Apple M2 Max
    Memory: 38.55 GB / 96.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.2.0 - ~/.nvm/versions/node/v20.2.0/bin/node
    Yarn: 3.6.4 - ~/Developer/SSW/SSW.Website/node_modules/.bin/yarn
    npm: 9.6.6 - ~/.nvm/versions/node/v20.2.0/bin/npm
  Browsers:
    Chrome: 118.0.5993.96
    Edge: 117.0.2045.55
    Safari: 17.0
  npmPackages:
    @tinacms/cli: ^1.5.29 => 1.5.29
    tinacms: ^1.5.21 => 1.5.20

Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug.

How many users is this affecting? Were they able to login previously? (The CORS errors are a red herring)
If you can have one or more of the affected users record what they are seeing using https://jam.dev/ and DM me on discord it would be really helpful.

Hey @bradystroud. Closing this for now until we can get some more information: https://github.com/tinacms/tinacms/issues/4281#issuecomment-1777523626


Make Refile::File wrapper for uploadable

Instead of extracting filename and content_type through the Refile constant, it feels much better to take an object oriented approach. Refile::File now wraps the uploadable from the outside world, and doesn't know anything about backends or IDs.
What I originally intended with this is that we can now, instead of handling content types and extensions in Refile::Attacher, just let users register their validators (and pass them though :type parameter), which would yield a Refile::File and then users can write their own validation (the same way that they register processors). Of course, Refile would still provide an :image validator. This way Refile::File would abstract the "uploadable".
I realized only before opening this PR that I broke the #copy_to in the S3 backend. Do you think this approach has potential to justify trying to fix the S3 in another way? And also justify Refile::Backend#upload now returning an ID instead of a Refile::File? Probably not :P

This is interesting. It's a very large change, so difficult to review properly.
This helps a lot in solving the currently biggest design problem in Refile which is the Attachor. The code in it is pretty bad, and it's gotten even worse since we're juggling with metadata and validations. Improving the Attachor is high on my list.
That being said, I specifically chose not to wrap uploadables in a class. I did this in CarrierWave and the result is incomprehensible and bad. There's a lot of juggling in CarrierWave when files are wrapped in layers and layers of wrappers. It's pretty hard to understand what's going on. My idea was to go for a more functional approach of data flowing through, rather than OO, but this turns out a little weird in Ruby.
IMO, As implemented this PR makes the Backend API too low level and finicky. One of my design goals with Refile was that backends should be useful and nice to work with in of themselves. Having real File objects, instead of passing around ids feels much cleaner and Ruby-esque to me.
However, the idea of having Refile::File play this dual role is a bit dangerous too. This ends up in the same kind of hell that SanitzedFile is in. Should the metadata form of files also be Refile::File? It becomes a wrapper for everything. Also it doesn't make any sense, since for example an uploadable file can be asked for its content_type, whereas a file stored in a Refile backend explicitly does not know what its content type is, by design.
Should we add two different wrappers then, maybe Refile::File and Refile::Uploadable or something? Maybe. This seems like the least bad option to me, but it brings us dangerously close to the kind of confusion that's inherent in CarrierWave.
Also, consider this: an ActionDispatch::UploadedFile already exactly conforms to the interface we want. We can ask it for content_type, size, filename, read from it, copy_stream it, close it. That's all we need, really. Remember also that ActionDispatch::UploadedFile already is a wrapper around the raw Rack file upload data. In the most common case of what we're receiving, we wrap a wrapper in another wrapper which is identical to the original wrapper. Blurgh.
So the current code isn't super nice, but is wrapping it in OO better? Maybe. But we should consider it carefully before we run down that route. Just because there is less code doesn't necessarily mean it's a better design.
So this isn't really a definite yes or no to this PR. It's a maybe, I guess.

Thank you, I really appreciate the detailed review.
I agree, the dual role could bring back the CarrierWave::SantizedFile hell, so it's definitely a no-go.
However, I really like the idea of a separate Refile::Uploadable class. And I can argue that it wouldn't be anything like CarrierWave::SanitizedFile. The main reason is that you narrowed the uploadable interface upfront to specified 4 methods, which means the implementation of Refile::Uploadable won't be able to grow after the initial version.
I also see as a great benefit that Refile::Uploadable would force the interface to the specificed 4 methods, so then backends will always throw errors if something is wrong, and currently they may throw or not throw errors depending on which file they get (they might accidentally be using methods which they shouldn't).
I remade the PR with Refile::Uploadable. The code changed a bit since 2 weeks ago, and I don't think it will help with simplifying Refile::Attacher (which I would really like), but it feels more OO.

As a counter-point to this, we could have simply changed the various extract_ methods into one extract_metadata which returns a Hash, and then assign this hash to metadata. The code would have been even cleaner in Attacher and we wouldn't even need the Uploadable wrapper.

Well, I don't think extract_metadata would make things better, because you would still have to split it into multiple private methods, which in my opinion shouldn't be on the Refile module.
That being said, since this you're probably thinking in the context of refactoring the Attacher, which I don't have knowledge of, I'm assuming I'm not seeing the bigger picture, so you can close this if you have a different plan.

I've thought about this some more. What do you think about adding a class called Refile::Metadata whose sole purpose is extracting the metadata from an uploadable object.
It would be an internal class (@api private), and it would look pretty similar to your Uploadable class, but it would not wrap the IO methods, and it would not be passed to the backends, only used in the attacher to extract metadata from the uploadable object.
It would have a to_h method which would return the full metadata hash (minus id).
This way we don't end up with tons of wrapping, and we have a nice place to isolate all the metadata extraction. The validation is gone from the Refile singleton class now anyway. What do you think?

I got a bit out of sync with Refile the past few months. Since it's a small change anyway, I think it's best if I leave it to you :)


Work around rust-lang/rust#61440

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit b64db390c41462ffd58663be801a52658b63a468 has been approved by alexcrichton

:hourglass: Testing commit b64db390c41462ffd58663be801a52658b63a468 with merge 2b9b7e95a7cadac531d43711627881f7ac80294f...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: alexcrichton
Pushing 2b9b7e95a7cadac531d43711627881f7ac80294f to master...


inference with depth gt

Thank you so much for your hard work on great research.
We want to find out the difference in performance by inference with depth gt or not.
May I know how you used it? I want to know if it was Gaussian, one-hot, or something else.
thanks.

Hi, thanks for your attention. you can refer to exps here https://github.com/Megvii-BaseDetection/BEVDepth/tree/main/bevdepth/exps/nuscenes/fusion


Request body size did not match Content-Length

man im having alot of issue today

it also gives me a warning saying bundles not implemented yet don't know its thats a bad thing or not

fixed it by updating to devloper edition but now im getting alot more errors than i think im supposed to be getting and i can't even play

Game version ?
What branch of the server repo are you running ?


Kestrel limits are not loaded from appsettings.config

Description
At the beginning of the article there is a statement that

By default, Kestrel configuration is loaded from the Kestrel section using a preconfigured set of configuration providers.

and a sample is given
{
  "Kestrel": {
    "Limits": {
      "MaxConcurrentConnections": 100,
      "MaxConcurrentUpgradedConnections": 100
    },
    "DisableStringReuse": true
  }
}

However, neither of these settings seems to be loaded from the config, from my observation.
I also peeked at the KestrelConfigurationLoader and found no sign of these properties being loaded there.
I also found a sample where Kestrel options for some reason are loaded manually from the config during startup:

options
.Configure(context.Configuration.GetSection("Kestrel"), reloadOnChange: true)

So either the documentation page contains wrong information, or this is a bug in the code. Or I'm missing something :)
Page URL
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel/options?view=aspnetcore-7.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/servers/kestrel/options.md
Document ID
5a5a34c5-1c75-ff17-b3d6-762194391319
Article author
tdykstra

Associated WorkItem - 203246

@Tratcher, in the introduction section to the Kestrel Options doc, should we remove the quoted text and sample config:

By default, Kestrel configuration is loaded from the Kestrel section using a preconfigured set of configuration providers.

{
  "Kestrel": {
    "Limits": {
      "MaxConcurrentConnections": 100,
      "MaxConcurrentUpgradedConnections": 100
    },
    "DisableStringReuse": true
  }
}

The config example illustrates the statement "Kestrel options can also be set using a configuration provider" -- should that read "Some Kestrel options ..." and can you suggest a better example to illustrate the statement?

@amcasey

That seems to be correct based on the comments, but there's also the sample that suggests appsettings.json might not be read by default:

"I also found a sample where Kestrel options for some reason are loaded manually from the config during startup:"

"By default" is a little fuzzy here.  If you're using the default builder, I believe that is hooked up automatically, but there are certainly code paths where it isn't (e.g. with the HostBuilder, as in that sample).  In any case, the text does indicate that "the File Configuration Provider can load Kestrel configuration from an appsettings.json or appsettings.{Environment}.json file" [emphasis added].  It's a bit subtle, but that doesn't seem to be the core of the complaint.

Empirically, those settings do end up in the configuration provider, but they do not end up reflected in KestrelServerLimits.  Unfortunately, adding that functionality isn't a priority, at the moment (though I agree that it's uncomfortably inconsistent), but we absolutely shouldn't have a sample in the document that doesn't actually work.  The short-term mitigation is probably to pick kestrel configurations that are picked up.  I'll see what I can find.


Error when checking out repository when building

Hi
I have just updated my version (git pull origin) and when the build runs and checks out from Github, I now get the following error:
Error trying to execute: export GIT_SSH="/Sites/phpci/PHPCI/build/project1-build124.sh" && git clone  -b phpci-test git@github.com:XXXXXXXXX/XXXXXXX.git "/Sites/phpci/PHPCI/build/project1-build124/"

This then seems to have adverse effects on plugins that are run after, such as php_unit:
EXCEPTION: TapParser only supports TAP version 13

I'm re-opening this as this is still an issue.
I'm running an older version of Codeception (1.8.7). This uses PHPUnit as a dependency.
In my unit tests, I am extending PHPUnit:
class ContractTest extends PHPUnit_Extensions_Database_TestCase
When I define the codeception config in my configuration
codeception:
  config: "codeception.yml"

This gives me the exact same error:
`Exception: TapParser only supports TAP version 13 {"exception":"[object] (Exception(code: 0): TapParser only supports TAP version 13 at /Sites/phpci/PHPCI/Plugin/Util/TapParser.php:50)","buildID":"34"} []
This refers to:
if ($versionLine != 'TAP version 13') {
    throw new \Exception(Lang::get('tap_version'));
}

Since I'm using Codeception, I have no phpunit.xml file
Any ideas?

has anybody gotten around this issue yet?


bug in gen_obs_grid?

Hello,
It seems to me that the sub-grid observed by the agent is somtimes wrong depending on what is the agent direction.
For example, assuming that we have a AGENT_VIEW_SIZE or 3. We will have a grid 3x3 around the agent and 9 elements in the observation array.
Here are the indexes of the elements in the grid visible by the agent that is facing up and is positioned in the center-bottom of the grid.
8      7      6
5      4      3
2      A      0
In this example shouldn't the index 8 of the observation array always be the element that the agent percieves at its top-left corner and the element of idex 0 always be the one at bottom-right (and so on..)?
It seems that in the current implementation of gen_obs_grid the positions of the elements in the observation view of the agent are not consistent with their position in the actual sub-grid generated as observation when it rotates.
`
    topX, topY, botX, botY = self.get_view_exts()

    grid = self.grid.slice(topX, topY, AGENT_VIEW_SIZE, AGENT_VIEW_SIZE)

    for i in range(self.agent_dir + 1):
        grid = grid.rotate_left()

`
I tried with a very naive and not optimized implementation to fix this issue:
`
    topX, topY, botX, botY = self.get_view_exts()

    grid = self.grid.slice(topX, topY, AGENT_VIEW_SIZE, AGENT_VIEW_SIZE)
    grid_rotate_left_1 = grid
    grid_rotate_left_2 = grid
    grid_rotate_left_3 = grid

    grid_rotate_left_1 = grid_rotate_left_1.rotate_left()

    for i in range (2):
        grid_rotate_left_2 = grid_rotate_left_2.rotate_left()

    for i in range (3):
        grid_rotate_left_3 = grid_rotate_left_3.rotate_left()

    # agent facing right
    if self.agent_dir == 0:
        grid = grid_rotate_left_3
    # agent facing left
    elif self.agent_dir == 2:
        grid = grid_rotate_left_1
    # agent facing up
    elif self.agent_dir == 3:
        grid = grid_rotate_left_2

`
What do you think about this?
Thank you for your collaboration!
Pier

I'm not sure I fully understand what the issue is here. It's normal that the agent view is rotated. It's made so that the agent sees what is in front of it from an egocentric reference frame. Can you describe the problem in more details? Does it happen with the default 7x7 observation size?

Yes the view has to rotate, but it didn't.
It's my bad actually, I have just pulled again from your latest master and it works great with all view sizes.
Thank you!


Always use go tar libraries on windows

On the latest versions of Window Server 2016 (1803) and Windows Server 2019, there is a tar executable that is shipped in the OS image. This tar executable behaves more or less the same way as the BSD tar that has been shipped with the current version of Windows stemcells, but this behavior does not function properly when Houdini streams in resources into Windows workers. We fixed the problem in concourse-windows-release by removing the system tar from the PATH: https://github.com/pivotal-cf-experimental/concourse-windows-worker-release/pull/5. We think one possible fix would be to always use the standard go library for tar operations.

@ankeesler Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@ankeesler Thank you for signing the Contributor License Agreement!

@vito @jama-pivotal Is there anything we should change with this PR in order to merge it upstream? This would be helpful when we deploy concourse to Windows Server 2016 (1803) and 2019.

Thanks! We were in need of this too.
https://github.com/concourse/concourse/blob/master/jobs/baggageclaim-windows/templates/start.ps1#L5
Sorry for the delay.


4/11/2019 Publish

Docs Build status updates of commit 52ff975:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Build website with Jekyll

This depends on #433 getting merged first.

Removes unused image, JS, and CSS assets
Replaces Slick (the image carousel) with an updated version on a CDN (mainly for https support)
Optimizes image assets to reduce bandwidth
Adds Jekyll with templated release notes, homepage, and appcast (for app updates)
Integrates with automated Travis builds

@radiant-player/radiant-player-mac this is ready for review

If you'd like to test this, try running ./scripts/build-website.sh then cd website/_site and check out the results.

Just a thought - as this is triggered by Travis, does this mean it'll automatically deploy after any commit to master?

Yes, that is correct and is by design.  For the website, any commit to master will sync gh-pages with the website.  It is limited to the master branch, so other branches won't go to gh-pages.  I think this is the behavior we want for the website.
For automatically building the app itself, that will have some different logic (based on tags, so that when we tag 1.2.3 it will build and deploy 1.2.3, but only on that specific commit).

Seems to be a merge conflict in index.html.  Let me know when that's sorted and I'll check it out.
And don't forget to port over the PR from last night as I think it's included in the "old" section ;-)

Okay, merge conflicts are resolved and this should be good to go

Yo - haven't forgotten. Just getting a ./scripts/build-website.sh: line 5: bundle: command not found error, which I'm guessing is something to do with not having the right gems installed, maybe.
Trying to work it out now. If it is specific ruby gems that need installing, will these need specifying in the travis config?

Bundler is assumed to exist already (it's commonly installed with ruby) and is preinstalled on Travis.  On your local machine, you can gem install bundler to grab a copy.

Oh, and once you have bundler installed, you run bundle install to install the other dependencies.  Anyways, again this is something Travis does automatically.

Spent the past 2 minutes trying to work out what that notification sound was - turns out it was GitHub telling me you'd replied. This is what happens when I don't have music playing :anguished:
OK, will try that and report back shortly!

Oh and I went through the changelog - nice one logging the ticket. I'll push that up too when I'm done with this.

I just rebased this - you may need to re-pull

Will do :+1:

I have a favicon.ico file to contribute once this PR is merged. :)

Only issue with the build process was @options[:href_ignore] will be renamed in a future 3.x.x release: http://git.io/vGHHy` -- not sure if that's a Jekyll thing though
Aside from that, seems to be looking good. Though I'm making a mental note to rewrite that carousel to be pure CSS - the performance of that slick slider is awful.
:shipit:

That's the html test tool - we can fix later I think...
Merging!
@andrewnorell, ready for the favicon!


[AutoRelease] t2-networkcloud-2023-07-26-04603(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4359
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=6093

issue link:https://github.com/Azure/sdk-release-request/issues/4359


Add documentation for azure importer model

Add quick start guide for Azure importer model to documentation website.

Closed by Addressed by https://github.com/Green-Software-Foundation/if-docs/pull/2


updates tp using doc

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1481/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1484/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1485/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1486/
Test PASSed.


Add config to set your own path for the Chromedriver.exe

I always have my chromedriver.exe in a single location on my server for multiple applications to use the same executable. It would be helpful to add an extra config to allow us to specify a path to it instead of forcing to place it in the same dir as the script. 👍

You can now specify driver path in the v0.3.4

You can now specify driver path in the version 0.3.4. 4da611d9e856cf07bb49a0ee42fb9e67b0364fd1

Awesome! Thanks @EKOzkan 🤝


Swap in conda env and more container-based CI/CD workflows

Fixes issues with failing CI/CD. Uses conda for virtual environment. CI/CD now works on Docker container, aside from code quality checks.
Close #11

I can live with this. Let's merge and see if this can push to the registry.
Merging.

I can live with this. Let's merge and see if this can push to the registry.
Merging.


Update our fork with latest changes on grist-core

Since CI is constantly failing I hope this might fix our workflows

@dnsos When you are back. Can you review this PR. I'm not sure where your changes are located but we need to update the ci pipeline I think

@ff6347, I'll continue this in #3 where the merge conflicts were fixed and a recommended way for keeping the fork in sync is added.


select view require select privilege instead of create view privilege

In ViewAccessControl when check select privilege, using delegate.checkCanSelectFromColumns method instead of checkCanCreateViewWithSelectFromColumns method.

@JackyWoo this was intentional. See Travis results.

hi findepi, thanks for figuring out my mis-understanding.


hello_world doesn't build in linux with reccomended setup

G'day all,
For reference I'm on latest ubuntu. Tried to run the hello_world example - first by copying it into a blank project with required dependencies (Speedy2D 1.12.0 and log/simple_logger. Error message:
  --> src/main.rs:37:40
   |
37 |      window.run_loop(MyWindowHandler { text })
   |                                        ^^^^ expected `FormattedTextBlock`, found `Rc<FormattedTextBlock>`
   |
   = note: expected struct `FormattedTextBlock`
              found struct `Rc<FormattedTextBlock>`

error[E0308]: mismatched types
   --> src/main.rs:53:58
    |
53  |          graphics.draw_text((290.0, 90.0), Color::BLACK, &self.text);
    |                   ---------                              ^^^^^^^^^^ expected `&Rc<FormattedTextBlock>`, found `&FormattedTextBlock`
    |                   |
    |                   arguments to this method are incorrect
    |
    = note: expected reference `&Rc<FormattedTextBlock>`
               found reference `&FormattedTextBlock`
note: method defined here
   --> ~./.cargo/registry/src/index.crates.io-6f17d22bba15001f/speedy2d-1.12.0/src/lib.rs:796:12
    |
796 |     pub fn draw_text<V: Into<Vec2>>(
    |            ^^^^^^^^^

For more information about this error, try `rustc --explain E0308`.

I tried cloning this repo and running it with cargo run --example hello_world and it worked, to my surprise.
So I tried copying dep versions from Speedy2D cargo.toml to my blank project but the error persists.
For the life of me, I can't figure out the difference: Any suggestions?

Thanks for the report! This is because the current examples in master are designed to work with v2.0.0, which hasn't been released yet.
I'm hoping to release v2.0.0 soon. In the meantime, please use the examples from the previous release:
https://github.com/QuantumBadger/Speedy2D/tree/a00cd814ae6081cd09cb1e591ee06ec5d0b28261/examples

Welcome!
Cloned locally and and confirm problem solved. I'll keep using bleeding edge :)
I'm testing a couple libraries for a combined web / desktop rendering. This and bevy seem to fill the niche well, although bevy's raw graphics API leaves a lot to be desired, plus builds can be large.

Version 2.0.0 now released :)


chore: examples and dark forms

adds a pregenerated image to image docs until lib util fix is resolved
ensure example forms have enough contrast on dark mode
make form elements of examples small enough to fit frames on xs screens

:tada: This PR is included in version 1.9.10 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Fix carousel styling

see https://github.com/picocms/Pico/pull/349#issuecomment-220652384

Side note: GitHub presented me a 500 Internal Server Error on my first try to open this PR :scream:

Huh, that's odd. (The 500 error)
A Pull Request on a Fork... that's pending a PR... that's a weird idea.

Is this all ready to merge or did you have more work to do?

Without being able to view it first, is everything working okay with the dynamic sizing?  I guess that still falls under question 1... :unamused:

Yes, you can merge this, dynamic sizing works just fine now. Whether we use it or not is another question :wink: :smile:


Should ESP32_GENERIC-SPIRAM work on AI Thinker?

I get the following:
ets Jul 29 2019 12:21:46

rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4892
ho 0 tail 12 room 4
load:0x40078000,len:14896
load:0x40080400,len:4
load:0x40080404,len:3372
entry 0x400805b0
W (62) boot.esp32: PRO CPU has been reset by WDT.
W (62) boot.esp32: WDT reset info: PRO CPU PC=0x400862fb
W (63) boot.esp32: WDT reset info: APP CPU PC=0x40081a81

OK, I see your example must be for a different camera as cam_config.py in the distro at:
https://github.com/shariltumin/esp32-cam-micropython-2022/tree/main/X23/esp32-aiThinker
is quite different.
I would struggle to work out the pin re-assignment as it looks like you have used different names.  Any chance of an example  for AIThinker?

In general it should work, it did by the guy from #2 on a esp32 board. Could you provide more information about this error?
Is it while booting or during some specific code?
It seems to be a watchdog error.

I had read those issues.
I updated the first post.
The code I am running:
import machine
import time
import gc

gc.collect()

if machine.reset_cause() == machine.SOFT_RESET:
    print('doing a machine.reset()')
    time.sleep_ms(5)
    machine.reset()

print('wait 2 seconds to allow a CTRL-C')
time.sleep(2)

from camera import Camera, GrabMode, PixelFormat, FrameSize, GainCeiling

# Camera construction and initialization
camera = Camera(
    data_pins=[1,2,3,4,5,6,7,8],
    vsync_pin=9,
    href_pin=10,
    sda_pin=11,
    scl_pin=12,
    pclk_pin=13,
    xclk_pin=14,
    xclk_freq=20000000,
    powerdown_pin=-1,
    reset_pin=-1,
    pixel_format=PixelFormat.RGB565,
    frame_size=FrameSize.QVGA,
    jpeg_quality=15,
    fb_count=1,
    grab_mode=GrabMode.WHEN_EMPTY
)

img = camera.capture()
print('picture taken')

Has camera.init' been left out of the example as I have seen camera.deinit` in your other examples?

BTW, I want to run this on a ESP32-CAM

Hi,
You have to specify the right ins from your board. Take a look [here] for the right pins.(https://github.com/adafruit/circuitpython/blob/main/ports/espressif/boards/ai-thinker-esp32-cam/pins.c)
The camera initialization is done during construction. You have the deinit only for the purpose of freeing resources, if you need them.

Thank you very much.  I have read comments about doing a camera.deinit before WiFi so I have the habit of doing init/deinit/init.

You can just connect to wifi and then construct the camera. The implementation from shariltumin used micropython 1.20, i think, so this might not be needed any more. With the right pin assignment it should work =).

Originally, I was running cameras on a 2Watt PV panel so only used the WiFi when the camera was triggered (snapshots).  I had a look at the link to CircuitPython and it is beyond my skill level.  I will wait to see how this project develops.


feat: Remove rison from expectedNpmVersionFailures.txt

Upon successful merge of DT PR #70883, rison can be removed from expectedNpmVersionFailures.txt.

Hi @jakebailey, I see some run failure here, so I just try repushed the PR to see if it can make things right.

I have no idea why this is failing; maybe a bug in the diffing hacks I put in CI to not require the changesets for these kinds of PRs


TestSearchController tests fail if run twice on the same DB

I see that not all entities are cleaned up in DB by the tests which most likely causes these failures:
--- FAIL: TestSearchController (2.81s)
    --- FAIL: TestSearchController/TestSearchQueryScenarioDriven (0.43s)
        --- FAIL: TestSearchController/TestSearchQueryScenarioDriven/space!=ID_AND_(state!=open_AND_iteration!=fake-iterationID) (0.03s)
        	assertions.go:247:

	Error Trace:	search_blackbox_test.go:853

	Error:      	Should be empty, but was [0xc420b8e3c0 0xc42077fc20 0xc42077fda0 0xc42077ff20 0xc420d2c120 0xc420ad9e00 0xc420b8e0c0 0xc420ad9f80 0xc420b8e540 0xc420d2c5a0 0xc420ad9c80 0xc420d2c2a0 0xc420d2c420 0xc420b8e240 0xc420ad9b00 0xc420b8e6c0 0xc420d2c720 0xc42077faa0]

	Test:       	TestSearchController/TestSearchQueryScenarioDriven/space!=ID_AND_(state!=open_AND_iteration!=fake-iterationID)
        --- FAIL: TestSearchController/TestSearchQueryScenarioDriven/assignee=null_before_WI_creation (0.02s)
        	assertions.go:247:

	Error Trace:	search_blackbox_test.go:1051

	Error:      	"..." should have 1 item(s), but has 19

	Test:       	TestSearchController/TestSearchQueryScenarioDriven/assignee=null_before_WI_creation
        --- FAIL: TestSearchController/TestSearchQueryScenarioDriven/assignee=null_after_WI_creation_(top-level) (0.02s)
        	assertions.go:247:

	Error Trace:	search_blackbox_test.go:1060

	Error:      	"..." should have 1 item(s), but has 19

cc: @xcoulon @kwk

@kwk, can I take this up? I know which test isn't cleaning up the spaces/workitems.


cmd/compile: precalculate constant square roots

Low priority, but probably also an easy ssa rule.
package x

import "math"

func root2() float64 {
	return math.Sqrt(2)
}

yields (amd64):
"".root2 t=1 size=32 args=0x8 locals=0x0
	0x0000 00000 (/Volumes/Data/src/go.tip/src/sqrt.go:5)	TEXT	"".root2(SB), $0-8
	0x0000 00000 (/Volumes/Data/src/go.tip/src/sqrt.go:5)	NOP
	0x0000 00000 (/Volumes/Data/src/go.tip/src/sqrt.go:5)	NOP
	0x0000 00000 (/Volumes/Data/src/go.tip/src/sqrt.go:5)	FUNCDATA	$0, gclocals·5184031d3a32a42d85027f073f873668(SB)
	0x0000 00000 (/Volumes/Data/src/go.tip/src/sqrt.go:5)	FUNCDATA	$1, gclocals·33cdeccccebe80329f1fdbee7f5874cb(SB)
	0x0000 00000 (/Volumes/Data/src/go.tip/src/sqrt.go:6)	MOVSD	$f64.4000000000000000(SB), X0
	0x0008 00008 (/Volumes/Data/src/go.tip/src/sqrt.go:6)	SQRTSD	X0, X0
	0x000c 00012 (/Volumes/Data/src/go.tip/src/sqrt.go:6)	MOVSD	X0, "".~r0+8(FP)
	0x0012 00018 (/Volumes/Data/src/go.tip/src/sqrt.go:6)	RET

But sqrt(2) is a constant.
cc @randall77 @brtzsnr

const root2 = 1.41421356237309504880168872420969807856967187537694807317667973799

That's why it's low priority.

What's more interesting and generally useful is perhaps compile time
constant folding of pure (inlinable?) functions, esp. those in the math
package.

Another small, straightforward sqrt-related compiler learning bug. Paging the crew from #16804:  @odeke-em @kevinburke @martisch

I'm interested in both but likely won't have time until Monday
On Friday, August 19, 2016, Josh Bleecher Snyder<EMAIL_ADDRESS>wrote:

Another small, straightforward sqrt-related compiler learning bug. Paging
the crew from #16804 https://github.com/golang/go/issues/16804:
@odeke-em https://github.com/odeke-em @kevinburke
https://github.com/kevinburke @martisch https://github.com/martisch
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/15543#issuecomment-241170923, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAOSI6tL6oyHmaZ1gghIryRS0u0e03FNks5qhlyTgaJpZM4IXe8K
.

--
--
Kevin Burke
925.271.7005 | kev.inburke.com

Is this in walk.go the right place for it or is this too early?
		if n.Left.Op == ONAME && n.Left.Sym.Name == "Sqrt" && n.Left.Sym.Pkg.Path == "math" {
			if Thearch.LinkArch.InFamily(sys.AMD64, sys.ARM, sys.ARM64, sys.PPC64, sys.S390X) {
				n.Op = OSQRT
				n.Left = n.List.First()
				n.List.Set(nil)
				break opswitch
			}
		}

I think it'd be better in generic.rules (and the code that gets generated from it, see cmd/compile/internal/ssa/gen).

To be pedantic, math.Sqrt is not a pure function -- it depends on the rounding mode the FPU is in. But as Go does not provide any way to change that, it's probably not a real problem.

Does setting the FPU rounding mode to non-round-to-nearest
pass the builtin tests for math.Sqrt?

On 22 August 2016 at 13:06, Minux Ma<EMAIL_ADDRESS>wrote:

Does setting the FPU rounding mode to non-round-to-nearest
pass the builtin tests for math.Sqrt?

Probably not. The tests compare the result of the Go sqrt code with the
Sqrt code and the Go sqrt (according to the comments) omits checking of
rounding mode.
Cheers,
mwh

It seems that Go plays pretty fast and loose with how floating-point ops are rounded (not just sqrt).  The spec is silent on the topic.  I'm not sure if/how we should support e.g. C code changing the rounding mode.

Possibly apropos:
https://github.com/golang/go/commit/4a8cb4a49c8bda0759dd3bc0c9fc6bdf5f6aa6b7
There Russ said:

In general, if a Go program changes the floating point math modes to something other than what Go expects, the math library is not going to work exactly as intended, so we might be justified in not fixing this at all.

Perhaps the spec should just specify the rounding mode?
The only time specific rounding mode is mentioned is converting
ideal floating point values to float32/float64 uses rounds to nearest
even.

But what does Go expect?  Ideally we should set the rounding mode on process (or OS thread) start and at the start of each C->Go transition.  I don't see anything in our code for startup (except plan9), but maybe the default is OK.  For returns from cgo calls I think we can rely on the calling convention which states that fp rounding mode is callee-save.  But for callbacks from C->Go I don't see where we do anything, and I think we should save+set and restore the fp mode (on x86 at least).

The expected rounding mode is To Nearest Even - that's the only default that makes sense. I'm pretty sure a lot of things would break if that changed. For instance, some of the math/big.Float tests assume that float32/64 are rounded that way (and it's tested against big.Floats with that rounding mode).
I don't know that C or C++ say much about float rounding but I'd be surprised if things wouldn't break if the mode is changed. Probably the same for Java.
I have a vague memory that we talked about that in the long past and the conclusion was that all bets are off if a piece of code (Go or anywhere else) changes the rounding mode. Or in other words: if some code changes it locally, it better changes it back.

So the question is: should we specify the rounding mode
in the language spec?

@minux I may not recall this correctly, but I believe we deliberately didn't specify it.
I suspect this is mostly for historical reasons (in the distant past, not every architecture had IEEE floating-point support, say the Cray machines) - and languages wouldn't want to exclude themselves from being "correctly" implementable. Now any relevant hardware supports IEEE floats, so perhaps it's ok to request it (we already refer to the standard in the spec. But I doubt it makes a difference in practice, so why risk it?
Related, Java took a big floating-point performance hit in the 90's because it specified floating-point details such as rounding in very much detail: on x87 hardware, intermediate results not stored to memory where held in 80bit registers which lead to different results because rounding was not done to 64bits. As a result, a -strict interpretation of Java floating-point operations required that each intermediate result be stored to memory to achieve correct rounding. Intel was not happy about that (it made their chips look slower than others) - hence it was a JVM option.

Java's strictfp is very picky about arithmetic, and specifies not just rounding mode, but mantissa sizes, exponent ranges, use of denormalized numbers, particular NaN encodings, and a limit of only one rounding per mathematical operation.  I'm not sure we want all that for Go, but I think specified rounding would be helpful.  Changing rounding would change (for example) our random-number stream.  In our currently generated code, we're not especially careful about exponent ranges and mantissa sizes, which means that there are cases where differences could be seen if people knew what to look for (examples: x87 might use 80-bit FP, which can result in double-rounding even with storeback; PPC FP registers are double-precision only, and so "float32" calculations may have extra precision in their intermediate results; any architecture with a so-called "fused multiply-add" will perform the addition in a*b+c in a double-width mantissa before rounding).
One thing to possibly consider that might placate the small-but-nonempty set of numerically oriented people who actually do care about rounding modes and understand how to write code that depends on them, is something along the lines of runInRoundingMode(mode Mode, f func()) where a (presumably small) piece of Go code could be run in a non-standard rounding mode.  The compiler would be responsible for saving/restoring current rounding mode correctly in those places where it tinkers with it for code generation purposes.

IBM 360 was a notable non-standard FP architecture: https://en.wikipedia.org/wiki/IBM_Floating_Point_Architecture

I guess I should apologize a bit for opening this can of worms :-)
On 23 August 2016 at 03:34, Robert Griesemer<EMAIL_ADDRESS>wrote:

@minux https://github.com/minux I may not recall this correctly, but I
believe we deliberately didn't specify it.
I suspect this is mostly for historical reasons (in the distant past, not
every architecture had IEEE floating-point support, say the Cray machines)

and languages wouldn't want to exclude themselves from being "correctly"
implementable. Now any relevant hardware supports IEEE floats, so perhaps
it's ok to request it (we already refer to the standard in the spec. But I
doubt it makes a difference in practice, so why risk it?

Making it clear one way or another if changing the rounding mode is
supported would make it clear whether or not the compiler can constant fold
fp math. Mandating that the fp environment is a constant thing is a bit
different from mandating exactly what that fp environment is.

On 23 August 2016 at 09:47, Michael Hudson-Doyle<EMAIL_ADDRESS>wrote:

Making it clear one way or another if changing the rounding mode is
supported would make it clear whether or not the compiler can constant fold
fp math.

Although it's been decided elsewhere that floating point constants are
not IEEE floats, so I'm probably making a fuss over nothing!

@dr2chase "Starting with the S/390 G5 in 1998,[5] IBM mainframes have also included IEEE binary floating-point units which conform to the IEEE 754 Standard for Floating-Point Arithmetic."
@mwhudson This is not about Go constants, this is about the compiler optimizing float32/64 variables that it recognizes as constants.
The spec requires IEEE floats (definition of float32, float64). I'd be ok with stating that the rounding mode used should be round-to-nearest even. I'm pretty sure we can't guarantee anything if it's changed. And we'd have to carefully rewrite a lot of code if we'd support changing the rounding mode underneath.
The other rounding modes are useful to implement things such as interval arithmetic, but it would be rather tedious to do this in Go for float32/64's.
That all said, it's nowhere written that math.Sqrt(2) cannot return the exact rounded result, internally stored as a constant (and that instead it must return the possibly incorrect, computed value).


Added New Libraries, Script File, and Calibration Code

=======================================================
Added the do_cal.py to /misc. Added the CabrilloCalibrator sketch to the /Swarmathon-Arduino folder. Added /ros_lib amd /lsm303-arduino to /Swarmathon-Arduino/libraries. The purpose of these changes are to combine new calibration code into our repo with the proper dependencies.

Will do, thank you for letting me know!
On Feb 26, 2018 10:19 PM, "darrenchurchill"<EMAIL_ADDRESS>wrote:
Hi, can you grab the most recent version of CabrilloCalibrator.ino from our
repository? The version you have in here had a few issues. Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BCLab-UNM/SwarmBaseCode-ROS/pull/179#issuecomment-368750839,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALR7sxI3q4x_ztsWt2cEiXv4EQ0qvm2Xks5tY5BogaJpZM4SUM_d
.

Great, also, that version of the Arduino sketch no longer outputs a register value used for debugging, so you need to change line 46 of do_cal.py to reflect that:
https://github.com/BCLab-UNM/SwarmBaseCode-ROS/blob/calibration-file-arrangements/misc/do_cal.py#L46
Should be:
logfile.write('{}, {}, {}, {}, {}, {}, {}, {}\n'.format(*data.data))
Only eight values, instead of nine.

Understood, I'll push that change right now. Thank you again!
On Mon, Feb 26, 2018 at 10:43 PM, darrenchurchill<EMAIL_ADDRESS>wrote:

Great, also, that version of the Arduino sketch no longer outputs a
register value used for debugging, so you need to change line 46 of
do_cal.py to reflect that:
https://github.com/BCLab-UNM/SwarmBaseCode-ROS/blob/
calibration-file-arrangements/misc/do_cal.py#L46
Should be:
logfile.write('{}, {}, {}, {}, {}, {}, {}, {}\n'.format(*data.data))
Only eight values, instead of nine.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BCLab-UNM/SwarmBaseCode-ROS/pull/179#issuecomment-368754556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALR7s91PTMdKDDQmjkhP_O0NJ7DXbQc9ks5tY5YPgaJpZM4SUM_d
.

Awesome thanks!

No problem!
On Mon, Feb 26, 2018 at 10:51 PM, darrenchurchill<EMAIL_ADDRESS>wrote:

Awesome thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BCLab-UNM/SwarmBaseCode-ROS/pull/179#issuecomment-368755813,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALR7s3plc7-R50IxRqcziOhXIl9eR6Qkks5tY5fzgaJpZM4SUM_d
.

Don't forget to rename do_cal.py to calibrate.py.

Why do we need ros_serial when we can read the USB directly? I am worried about adding 42k lines just to read USB. We don't need the ROS integration to write the extended calibration file.

The calibration has been tested and works just as expected. There are no issues with running the rovers either.


UV issues with trees

Describe the bug
Some trees have UV issues that are not present in RuneLite's GPU plugin, when looked at from certain angles. Possibly introduced by the mirror shield UV changes.
Screenshots

Fixed by https://github.com/117HD/RLHD/commit/b63d7358bff1bae5d3f39d7065177e218a7b5558.


Add no changes recommended list

Signed-off-by: Celeste Horgan<EMAIL_ADDRESS>

Hi, is this holding for any reason other than a lack of reviews?
I'll give a full check and copyedit of the content, and will do a review if it helps/is needed.

@quaid - this is a holding because of lack of reviews!

@quaid - this is a holding because of lack of reviews!

Thanks, that helps because we had a whole round of verbal approvals in a meeting the other day, but I was the only one who came here and did a thing. So I will go and poke people to come and do a thing, and then we'll have enough reviews!


Discrepancy in dist_traveled and max_dist_home units between hourly and daily summaries

Commit hash (the first line of output from git show):
6c14f8d1f74866d54d2e890fc9b1fa8db0fd25fb
Describe the bug
The units in dist_traveled and max_dist_home vales returned from jasmine are inconsistent between daily and hourly summaries.
Expected behavior
Either dist_traveled values should be reported in kilometers for hourly summaries, or we should update the documentation to reflect that the units are different at different levels of resolution.
Additional context
I'm happy to make a PR for this, but wanted to get others' feedback before doing so.

Thank you for noticing this @clementzach. I will create a PR to update the values in kilometers and add you to review it.


Feature: Create compatibility styles between browsers

Motivation
Browsers process styles in different ways, and like StyledComponents or Emotion already do, apply styles for the browser to process the style as expected.
Details
Currently the style
css({
boxShadow: '10px 44px 5px 0px rgba(0,0,0,0.75)'
})

is transformed into the class
._yf6uil._yf6uil {
    box-shadow: 10px 44px 5px 0px rgba(0,0,0,0.75);
}

and it could add browser compatibility
._yf6uil._yf6uil {
    -webkit-box-shadow: 10px 44px 5px 0px rgba(0,0,0,0.75);
    -moz-box-shadow: 10px 44px 5px 0px rgba(0,0,0,0.75);
    box-shadow: 10px 44px 5px 0px rgba(0,0,0,0.75);
}

Are there any plans to add this feature in the future?

Thank you for the question!
Styled Components and Emotion both rely upon Stylis for auto-prefixing CSS properties. As otion has a strict constraint on bundle size, tiny-css-prefixer is used by default. In my experience, it does a great job to retain compatibility with IE 11 and up.
However, if you would like to use the prefixing mechanism of more popular CSS-in-JS libraries, please see how Stylis can be used for prefixing in the Gatsby plugin docs.


GitHub Copilot not operational within MacVim

Steps to reproduce

Install GitHub Copilot for Vim (https://github.com/github/copilot.vim)
Enable it within MacVim :Copilot enable
Check status: :Copilot status, which should report enabled and online, instead it reports back the ghost text required neovim v.0.6, which is not exactly accurate. The same instance of underlying nvim (@0.7.2) in terminal window works with copilot as desired.

Expected behaviour
Functional GitHub Copilot within MacVim. Currently when typing the Copilot instead of displaying proposed code, instead reports function: syntax error
Version of Vim and architecture
VIM - Vi IMproved 8.2; NVIM v0.7.2
Environment
OS: MacOS
Shell: zsh
$TERM: xterm-256color
Terminal: iTerm
How MacVim was installed
Binary download
Logs and stack traces
No response
Vim configuration where issue is reproducable
No response
Issue has been tested with given configuration

[X] by running MacVim.app from GUI macOS interface
[ ] by running vim/gvim/etc installed by MacVim
[X] by running other versions of vim (e.g. /usr/bin/vim)

Issue has been tested with no configuration

[ ] by running mvim --clean (or gvim, supplied by MacVim distribution)
[ ] by running vim --clean (in terminal, supplied by MacVim distribution)
[ ] by running vim --clean (in terminal, other suppliers, e.g. /usr/bin/vim)

Other conditions

[X] The both Homebrew packages "vim" and "macvim" are installed

Does this plugin works with regular Vim installed from another source?

The copilot plugin is only compatible with Neovim.

from https://github.com/github/copilot.vim
"Copilot.vim is a Vim plugin for GitHub Copilot. For now, it requires Neovim 0.6 (for virtual lines support) and a Node.js installation."
Agree, Not an macvim issue from what I see.

Yeah MacVim is a fork of Vim, not Neovim. You would need to use a Neovim GUI instead, e.g. Neovide, VimR, etc (I haven't used each much so can't really comment on their qualities).
Looking through the plugin, seems like they are saying they need Neovim for the virtual text support. I would imagine they could have supported regular Vim via popup windows (released in 8.2) if they wanted to, but may not have decided to spend the time. Looking through their code seems like they essentially only call nvim_buf_set_extmark and nvim_buf_del_extmark, and can easily replace those calls with Vim popup's. However, I don't have a subscription and will not be willing to pay for it to try it out so that's the extent of my digging (they say it is free for popular open-source software maintainers but MacVim is not considered as popular enough).
I would suggest just submitting a pull request to their plugin to add popup support (it actually seems quite manageable given the small amount of Neovim dependency they use) or just file a feedback.

Appreciate the insight. Much helpful. When I have time I will look into it more as well. Thanks!

The latest patch(+patch 9.0.0162) of vim9 already support the virtual text feature, and Copilot.vim has also supported it in v1.5.0.

Well to be fair Vim's support for virtual text is not considered to ready for prime time yet as far as I understand.


Update dependencies for node 12 support

Motivation
We need to build things which are written with node 12. This breaking change will add node 12 support to this module.
Notes
I've updated all dependencies to the very latest versions (explicitly where not already handled by the package.json versioning). Tests are green but it you feel test coverage isn't sufficient to feel comfortable releasing this - let me know and we can discuss adding further tests.

Coverage decreased (-0.3%) to 93.93% when pulling b96e6dbbda466f2cf35f2a5b0daef6f7c4777470 on owenniblock:fix/update-for-node12 into 1f6e032e290ac4b0ce47666f9be661a0336b7505 on npm-wharf:master.

Build broken on node 6 - I'm going to remove support for node 6 (let me know if you disagree with this decision and we can discuss what to do here) :)

having no context, i just might request that coverage go to 100% here to have an added assurance

If getting the test coverage up to 100% is prohibitive, I think at the very least what we should do is audit the lines that the coverage report say are missing and make sure we don't have another instance like with mkdirp where the function signature changed.


Remove the output of params used for oc login

oc login is sending the parameters used for oc login to std out.

@rthallisey Looks like this won't build due to the unused strings import.

Thanks @eriknelson. The new makefile run had me thinking I tested it.

ACK! (pending travis)

 Security cleanup of asb code


Fixed missing simple-report sender transform to set display when missing

This PR adds a missing transform needed to map an Observation's text description to OBX-3-2.
If you are suggesting a fix for a currently exploitable issue, please disclose the issue to the prime-reportstream team directly outside of GitHub instead of filing a PR, so we may immediately patch the affected systems before a disclosure. See SECURITY.md/Reporting a Vulnerability for more information.
Test Steps:

Check out and build the branch
run ./prime multiple-settings set -e local -i settings/staging/0155-NY-up-onboarding.yml
Send a test report using the attached Postman collection
NY.postman_collection.txt
Verify that the request was accepted
Open the generated HL7 file in the local sftp folder.
Verify that OBX-3-2 is being mapped correctly.

Changes

Updated Simple Report sender transforms
Updated integration tests

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[x] Added tests?

Linked Issues

#11231

LGTM


Amplitude should report installed add-ons

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
Currently we have no visibility into what add-ons are in use in the wild. It would be super appropriate to report them. As of v1.22+ this information is easy to get.
Describe your solution
Add them to the project info.
Describe alternatives
No response
Additional context
No response

Great idea!


Null values not allowed for StateMachine ResultPath

cfn-lint version: (cfn-lint --version)
0.35.1
Description of issue.
I have an AWS::Serverless::StateMachine resource with a state like this:
          MarkRunCompleted:
            Type: Task
            Resource: !GetAtt UpdateRunStatus.Arn
            Parameters:
              run_id.$: $.run.id
              status: RUN_COMPLETED
            ResultPath: null  # Don't pass output
            Next: NextStep

When I run poetry run cfn-lint template.yaml, it fails with
E0000 Null value at line 594 column 25
template.yaml:594:25

I am confused because in the CloudFormation docs, it says that ResultPath can be set to null to pass the original input as the output.
Is this a bug?
Even if I do poetry run cfn-lint template.yaml -i E0000, it still fails with the same error.

Even if I do poetry run cfn-lint template.yaml -i E0000, it still fails with the same error.

This part is being tracked here

Duplicate to #1657


Verify no elements have same mass

If any elements have the same mass, the output of the element_from_mass function may have ill-defined output.

Some of the elements do have the same mass. These come from the high atomic number cases where the mass is defined as the mass number of the most stable isotope. We need to consider how we want to handle these situations. This is an edge case, most elements that will be used do not suffer from this problem.
@umesh-timalsina any ideas?

Couple of ideas,

Return all the matching elements preferably as a tuple/list depending on the use case.
Raise an error DuplicateElementError or MultiMatchError. Can have a flag like silent=True for suppressing this error.

I prefer 2; it will only be a problem with element_from_mass; in these few (5, I think) cases there is not a unique choice. We also need to ensure the exact=False behavior is correct. We can use a return_duplicates=True flag if the user wishes to return duplicates; it should return a tuple of elements in that case.

I agree default to raising error when there is no unique match when searching with mass is the better option. And if the user choose to ignore the error, beside the option of returning a tuple of matched element, I think we also have the option of just return None along with a warning message indicating the index of the Atom (so they can select it later) and the matched list. That way, the user can go back add the missing ones manually.

I agree default to raising error when there is no unique match when searching with mass is the better option. And if the user choose to ignore the error, beside the option of returning a tuple of matched element, I think we also have the option of just return None along with a warning message.

This is OK with me, instead of return_duplicates=bool we can use an enum with options duplicates="error", duplicates="all", or duplicates="none".

indicating the index of the Atom (so they can select it later) and the matched list.

I think this is behavior that would be in the external package gmso, mbuild, foyer, etc, rather than here. ele has no knowledge of atom or atom indicies.


Script Page: Missing Artermis image

https://apps.atlasacademy.io/db/NA/script/0300060110

Added VERTICAL_IMAGE_SET on commit 757d1dd