preprocessing-service crashing

I installed opni on my EKS cluster. After few minutes preprocessing-service starts crashing. I can see it is receiving 400 from opendistro-es-client-service and not able to handle that.
2021-08-11 05:58:41,927 - INFO - POST https://opendistro-es-client-service.opni-demo.svc.cluster.local:9200/_bulk [status:200 request:0.180s]
2021-08-11 05:58:42,538 - WARNING - POST https://opendistro-es-client-service.opni-demo.svc.cluster.local:9200/_bulk [status:400 request:0.035s]
Traceback (most recent call last):
  File "./preprocess.py", line 183, in <module>
    loop.run_until_complete(
  File "/usr/local/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "./preprocess.py", line 158, in mask_logs
    async for ok, result in async_streaming_bulk(
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 177, in async_streaming_bulk
    async for data, (ok, info) in azip(
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 107, in azip
    yield tuple([await x.__anext__() for x in aiters])
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 107, in <listcomp>
    yield tuple([await x.__anext__() for x in aiters])
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 82, in _process_bulk_chunk
    for item in gen:
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/helpers/actions.py", line 193, in _process_bulk_chunk_error
    raise error
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 70, in _process_bulk_chunk
    resp = await client.bulk("\n".join(bulk_actions) + "\n", *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/client/__init__.py", line 457, in bulk
    return await self.transport.perform_request(
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/transport.py", line 329, in perform_request
    raise e
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/transport.py", line 296, in perform_request
    status, headers, data = await connection.perform_request(
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/http_aiohttp.py", line 329, in perform_request
    self._raise_error(response.status, raw_data)
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/connection/base.py", line 322, in _raise_error
    raise HTTP_EXCEPTIONS.get(status_code, TransportError)(
elasticsearch.exceptions.RequestError: RequestError(400, 'illegal_argument_exception', 'For input string: ""')

I checked opendistro-es-client-service pod but no relevant logs are available there.
ture major version, direct access to system indices will be prevented by default
[2021-08-11T05:59:37,214][DEPRECATION][o.e.d.c.m.IndexNameExpressionResolver] [opendistro-es-client-55d4c4489f-78f96] this request accesses system indices: [.kibana_1, .kibana_92668751_admin_1], but in a future major version, direct access to system indices will be prevented by default
[2021-08-11T05:59:38,046][DEPRECATION][o.e.d.c.m.IndexNameExpressionResolver] [opendistro-es-client-55d4c4489f-78f96] this request accesses system indices: [.kibana_1, .kibana_92668751_admin_1], but in a future major version, direct access to system indices will be prevented by default
[2021-08-11T05:59:38,046][DEPRECATION][o.e.d.c.m.IndexNameExpressionResolver] [opendistro-es-client-55d4c4489f-78f96] this request accesses system indices: [.kibana_1, .kibana_92668751_admin_1], but in a future major version, direct access to system indices will be prevented by default
[2021-08-11T05:59:38,785][DEPRECATION][o.e.d.c.m.IndexNameExpressionResolver] [opendistro-es-client-55d4c4489f-78f96] this request accesses system indices: [.kibana_1, .kibana_92668751_admin_1], but in a future major version, direct access to system indices will be prevented by default
[2021-08-11T05:59:38,786][DEPRECATION][o.e.d.c.m.IndexNameExpressionResolver] [opendistro-es-client-55d4c4489f-78f96] this request accesses system indices: [.kibana_1, .kibana_92668751_admin_1], but in a future major version, direct access to system indices will be prevented by default
[2021-08-11T06:00:33,158][DEPRECATION][o.e.d.c.m.IndexNameExpressionResolver] [opendistro-es-client-55d4c4489f-78f96] this request accesses system indices: [.kibana_1, .kibana_92668751_admin_1], but in a future major version, direct access to system indices will be prevented by default
[2021-08-11T06:01:33,185][DEPRECATION][o.e.d.c.m.IndexNameExpressionResolver] [opendistro-es-client-55d4c4489f-78f96] this request accesses system indices: [.kibana_1, .kibana_92668751_admin_1], but in a future major version, direct access to system indices will be prevented by default

what's the image name and ID of the preprocessing service you're using?

Image:          rancher/opni-preprocessing-service:v0.1.2
Image ID:       docker-pullable://rancher/opni-preprocessing-service@sha256:c02755a646bb22eb5c5fbb6e33531a88939026a5c13e43486b9c6f8814e860d9

logs.tar.gz
Attaching logs from nat and preprocessing-service
Yes this issue is persisting. Pod is crashing every couple of minutes. I have tried re-installing opni demo as well but same issue.

I think I've identified the issue. Can you edit the deployment: kubectl edit deployment preprocessing-service -n opni-demo
and change .spec.template.spec.containers[0].image to sanjayrancher/preprocessing-service:v0.1.2-dev-patch
Let me know if this patch works

Thanks for the patch. I tried it but it is still crashing withing few second of pod coming up
2021-08-12 07:18:53,388 - INFO - POST https://opendistro-es-client-service.opni-demo.svc.cluster.local:9200/_bulk [status:200 request:0.035s]
2021-08-12 07:18:54,343 - INFO - POST https://opendistro-es-client-service.opni-demo.svc.cluster.local:9200/_bulk [status:200 request:0.159s]
2021-08-12 07:18:54,767 - WARNING - POST https://opendistro-es-client-service.opni-demo.svc.cluster.local:9200/_bulk [status:400 request:0.019s]
Traceback (most recent call last):
  File "./preprocess.py", line 183, in <module>
    loop.run_until_complete(
  File "/usr/local/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "./preprocess.py", line 158, in mask_logs
    async for ok, result in async_streaming_bulk(
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 177, in async_streaming_bulk
    async for data, (ok, info) in azip(
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 107, in azip
    yield tuple([await x.__anext__() for x in aiters])
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 107, in <listcomp>
    yield tuple([await x.__anext__() for x in aiters])
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 82, in _process_bulk_chunk
    for item in gen:
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/helpers/actions.py", line 193, in _process_bulk_chunk_error
    raise error
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/helpers.py", line 70, in _process_bulk_chunk
    resp = await client.bulk("\n".join(bulk_actions) + "\n", *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/client/__init__.py", line 457, in bulk
    return await self.transport.perform_request(
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/transport.py", line 329, in perform_request
    raise e
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/transport.py", line 296, in perform_request
    status, headers, data = await connection.perform_request(
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/_async/http_aiohttp.py", line 329, in perform_request
    self._raise_error(response.status, raw_data)
  File "/usr/local/lib/python3.8/site-packages/elasticsearch/connection/base.py", line 322, in _raise_error
    raise HTTP_EXCEPTIONS.get(status_code, TransportError)(
elasticsearch.exceptions.RequestError: RequestError(400, 'action_request_validation_exception', 'Validation Failed: 1: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;2: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;3: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;4: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;5: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;6: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;7: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;8: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;9: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;10: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;11: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;12: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;13: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;14: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;15: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;16: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;17: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;18: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;19: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;20: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;21: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;22: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;23: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;24: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;25: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;26: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;27: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;28: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;29: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;30: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;31: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;32: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;33: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;34: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;35: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;36: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;37: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;38: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;39: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;40: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;41: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;42: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;43: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;44: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;45: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;46: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;47: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;48: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;49: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;50: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;51: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;52: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;53: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;54: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;55: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;56: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;57: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;58: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;59: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;60: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;61: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;62: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;63: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;64: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;65: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;66: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;67: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;68: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;69: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;70: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;71: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;72: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;73: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;74: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;75: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;76: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;77: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;78: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;79: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;80: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;81: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;82: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;83: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;84: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;85: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;86: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;87: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;88: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;89: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;90: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;91: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;92: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;93: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;94: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;95: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;96: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;97: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;98: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;99: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;100: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;101: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;102: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;103: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;104: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;105: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;106: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;107: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;108: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;109: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;110: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;111: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;112: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;113: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;114: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;115: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;116: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;117: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;118: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;119: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;120: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;121: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;122: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;123: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;124: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;125: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;126: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;127: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;128: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;129: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;130: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;131: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;132: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;133: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;134: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;135: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;136: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;137: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;138: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;139: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;140: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;141: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;142: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;143: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;144: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;145: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;146: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;147: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;148: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;149: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;150: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;151: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;152: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;153: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;154: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;155: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;156: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;157: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;158: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;159: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;160: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;161: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;162: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;163: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;164: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;165: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;166: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;167: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;168: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;169: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;170: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;171: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;172: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;173: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;174: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;175: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;176: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;177: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;178: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;179: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;180: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;181: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;182: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;183: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;184: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;185: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;186: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;187: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;188: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;189: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;190: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;191: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;192: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;193: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;194: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;195: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;196: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;197: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;198: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;199: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;200: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;201: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;202: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;203: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;204: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;205: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;206: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;207: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;208: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;209: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;210: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;211: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;212: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;213: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;214: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;215: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;216: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;217: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;218: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;219: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;220: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;221: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;222: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;223: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;224: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;225: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;226: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;227: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;228: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;229: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;230: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;231: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;232: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;233: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;234: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;235: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;236: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;237: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;238: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;239: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;240: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;241: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;242: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;243: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;244: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;245: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;246: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;247: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;248: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;249: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;250: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;251: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;252: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;253: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;254: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;255: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;256: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;257: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;258: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;259: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;260: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;261: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;262: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;263: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;264: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;265: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;266: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;267: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;268: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;269: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;270: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;271: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;272: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;273: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;274: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;275: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;276: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;277: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;278: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;279: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;280: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;281: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;282: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;283: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;284: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;285: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;286: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;287: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;288: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;289: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;290: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;291: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;292: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;293: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;294: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;295: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;296: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;297: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;298: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;299: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;300: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;301: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;302: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;303: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;304: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;305: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;306: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;307: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;308: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;309: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;310: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;311: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;312: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;313: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;314: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;315: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;316: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;317: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;318: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;319: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;320: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;321: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;322: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;323: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;324: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;325: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;326: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;327: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;328: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;329: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;330: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;331: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;332: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;333: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;334: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;335: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;336: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;337: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;338: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;339: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;340: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;341: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;342: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;343: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;344: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;345: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;346: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;347: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;348: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;349: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;350: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;351: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;352: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;353: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;354: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;355: internal versioning can not be used for optimistic concurrency control. Please use `if_seq_no` and `if_primary_term` instead;')

preprocessing-service-logs.tar.gz
Please find logs attached.

thanks for providing the logs - It helped identify the delta.
try sanjayrancher/preprocessing-service:v0.1.2-dev-patch-3

@sanjay920 Thanks for the patch. Looks like it has resolved the issue.


[RUSTSEC-2023-0052] webpki: CPU denial of service in certificate path building

It appears this applies likely because of webpki-roots = { version = "0.22", optional = true } at L#48 in Cargo.toml

Crate:     webpki
Version:   0.22.0
Title:     webpki: CPU denial of service in certificate path building
Date:      2023-08-22
ID:        RUSTSEC-2023-0052
URL:       https://rustsec.org/advisories/RUSTSEC-2023-0052
Severity:  7.5 (high)
Solution:  No fixed upgrade is available!

Output of `cargo audit` after a standard `cargo build`:
webpki 0.22.0
├── webpki-roots 0.22.6
│   ├── twitch-irc 5.0.0
│   ├── reqwest 0.11.14
│   │   └── twitch-irc 5.0.0
│   └── async-tungstenite 0.17.2
│       └── twitch-irc 5.0.0
├── tungstenite 0.17.3
│   └── async-tungstenite 0.17.2
├── tokio-rustls 0.23.4
│   ├── twitch-irc 5.0.0
│   ├── reqwest 0.11.14
│   ├── hyper-rustls 0.23.2
│   │   └── reqwest 0.11.14
│   └── async-tungstenite 0.17.2
└── rustls 0.20.8
    ├── tungstenite 0.17.3
    ├── tokio-rustls 0.23.4
    ├── reqwest 0.11.14
    └── hyper-rustls 0.23.2

This was fixed in denoland/deno#20285 by updating to name webpki-roots to 0.25.2 which removes the inherit dependency on webpki. They also had to bump their reqwest version to 0.11.20(which would likely get picked up with a simple cargo update)
It looks like an update would fix things. I don't know if that should/can get caught up in #189 or if that should land separately.

Addendum: it appears that async-tungstenite = { version = "0.17", features = ["tokio-runtime"], optional = true } #L30 in cargo.toml pins a version that can also be updated to 0.22 or 0.23 both of which fix their underlying pin of webpki-roots to a version that alleviates this issue as well.

Fix released to crates.io as version 5.0.1

Thank you for such a prompt response. I hope this wasn't to out of protocol. I hope your day/night goes well too.


Remove selenium ohio

PR removes selenium from use in Ohio Supreme and Ohio lower courts
Additionally it fixes the citation form to match Ohio's form and replaces
a few tests that were broken (ie empty).
This is equivalent to a previous PR but a merge with the neutral/paralell citation update
caused havoc.

LGTM.


More Bash Programs

Submission Title
:bangbang: Help Needed :bangbang:
Submission Type
Algorithm + Data Structure + STL + Maths_And_Stats + Resources
Submission Description
Implement all the existing programs in bash script
Submission Directory
Main_Folder => Sub_Folder => ... => ... => Filename.sh
Important

Don't wait to get assigned :no_entry_sign:
Just create the PR :heavy_check_mark:
If a PR for a specific algo/ds has already been opened, kindly opt a different program.There are plenty of them :grin:
Push the program in the appropriate directory
Please do not spam or create duplicate PR :warning:

thanks everyone :v:


story highlights

A horizontal list thumbnails/titles at the top of the 'photos' section for special events/timelines.
Tapping on the thumbnail should bring up the story.
The story is a slideshow that cycles through the list of photos.

should be able to steal code from older version

get details from the DB

Hey @ghorbani-m,  In which pattern we are categorizing the images on the slide shows?
Can you please elaborate and describe this features details?
I would like to work on this issue/feature.

@gitaaron , @ehsan6sha , @ghorbani-m
I have tried this feature on my phone but this feature was missing from mine.
But there's something like this on iPhone photos app that picks the images randomly and shows them as featured photos.
The thing is I have no idea how to pick specific pictures and categorize them. @ghorbani-m do you still have the old version of the app, if you do so please share that with me. I need to take look at that.
Any ideas on this would be appreciated ;)

Hey @ghorbani-m, In which pattern we are categorizing the images on the slide shows? Can you please elaborate and describe this features details? I would like to work on this issue/feature.

@emadbaqeri , Thanks for contributing, Google photos use some AI mechanism to collect some of the images as a highlight for the clients,
But for now, we can highlight the images based on the creation date, like these:

last week
last month
last 3 moth
last 6 month
last 12 month
...

Hey @ghorbani-m, In which pattern we are categorizing the images on the slide shows? Can you please elaborate and describe this features details? I would like to work on this issue/feature.

@emadbaqeri , Thanks for contributing, As I know Google photos use some AI mechanism to collect some of the images as a highlight for the clients, But for now, we can highlight the images based on the creation date, like these:

last week
last month
last 3 moth
last 6 month
last 12 month
...

Thanks for your response, will be working on this part

@emadbaqeri FYI: There is a function (categorizeAssets) in the asset-service file that categorized the images and prepare them for RecycleListLiew, This is where you can add your algorithm to create the stories.

@ghorbani-m ohh I was thinking 🤔 about how to categorize the images. Thanks for that

My two cents -
I don't think the algo matters that much right now.  Instead I'd focus on the interface trying to think about what might come in the future.  I'd also be concerned about running the categorization process while the main UI thread is in the foreground.  Even if it is running under its own thread (ie/ not blocking the UI) while the app is running in the foreground then I'd be careful that the app responsiveness is not degraded.  Ideally it could run as a batch process in the background (ie/ UI is not in foreground) while the phone is plugged in.
Perhaps splitting it like this?
https://www.figma.com/file/nL3pPlzYkysK5NJ4XpD8pN/Untitled?node-id=0%3A1
That way the batch process might come from the Box in the future.
For the categorization algo - I think you guys have it right in clustering based on time.  Perhaps you could also do proximity?

@gitaaron Thanks for the comment, you are right, for highlighting the images we need to have some AI algo that could be done on the BOX, for now, we are preparing the UI to show the highlights on the top of listview, so we need a simple algo to collect some images as a highlight. later we can feed UI's data with a smart highlight collection that has been prepared with AI.

sounds good @ghorbani-m I had a feeling you were already taking these considerations in mind


Cleanup further

A continuation of PR #61.
The changes reduce the number of times uv_*_t identifiers occur in uvw code further. This focuses on the Request hierarchy (the Handle hierarchy was covered in the previous PR).
Also, made the change agreed upon in this comment.

Coverage remained the same at 98.493% when pulling 5258c36d4dbae836bbda118209a111c33ebc40b2 on tusharpm:test into 5415899d41bf4ed13b04d1347382e1c21fcee983 on skypjack:master.

Coverage remained the same at 98.493% when pulling f17020c6340267c3f66aa03777f7c491ee1aea72 on tusharpm:test into 5415899d41bf4ed13b04d1347382e1c21fcee983 on skypjack:master.


Update to syn 1.0

Not sure if this crate is still begin updated but it would be great to see it ported to syn 1.0 (and also quote 1.0).

Not sure if this crate is still begin updated

Not too much unfortunately as I don't have that much time/motivation, but it's not completely dead :)


Config Issue, Very Weird

I try to open the config, but instead it opens Adobe After Affects. Very strange... lmao
Running this on fabric, macOS latest

looks like a "your system" issue

There isn't any way that it's a system issue, because there isn't any call for that in system logs n'shit

That is an issue with the configuration of your file associations. SmoothBoot should use the standard system APIs for opening stuff. Check file associations for unknown files, Adobe is known to mess stuff up.

Going to close issue, Adobe has a weird issue where it will take precedence over any other app as the default opening application if it supports it. This is kind of the case with many other applications, and I don't know if macOS just does that, but it's annoying, and I hope they fix it.


Relax rainbow dependecy requirements to allow 2.x and 3.x

closes #1

Coverage remained the same at 93.846% when pulling ac5345eccd98d6e8ebe334bd4803c4968a2d02e7 on brodock:1-rainbow-dependency into f9eb5a1237e0b3eb9c6414df9e2df272674a8afe on ioquatix:master.

Coverage remained the same at 93.846% when pulling ac5345eccd98d6e8ebe334bd4803c4968a2d02e7 on brodock:1-rainbow-dependency into f9eb5a1237e0b3eb9c6414df9e2df272674a8afe on ioquatix:master.

Coverage remained the same at 93.846% when pulling ac5345eccd98d6e8ebe334bd4803c4968a2d02e7 on brodock:1-rainbow-dependency into f9eb5a1237e0b3eb9c6414df9e2df272674a8afe on ioquatix:master.

@ioquatix could you please review/merge this PR?

Okay released. In the future try to avoid committing whitespace changes :)


Use appharbor.commit_id instead of DOCKED_AT_APPHARBOR

Since we inject a key called "appharbor.commit_id", you could use that instead of a custom variable to simplify it even further. Suggested by Troels Thomson.

Issue is fixed now including updated documentation. Thanks Troels!


New words to the list

Don't know if this repo is still being maintained, but any thoughts on including the following words?
Forkortelser
bl.a.
ca.
fx
f.eks.
pga.
Nye ord
derfra
hen

sorry for the very late response, can you provide more info why those words should be included. thanks!

Hi @genediazjr. I had completely forgotten this issue, so no worries on the late response.
I cannot remember why I suggested these specific words. I think it was because they kept popping up in a project I was working on back then.
In any case, I don't know if you have a certain definition of what constitutes a stop-word? If not,  then I would think that at least the abbreviations carry very little, if any, semantic relevance for any nlp-model.
The two last words, "derfra" og "hen", I actually don't think you should include in the as they are adverbials. That was a bad suggestion I think.

Yeah, I do not consider abbreviations as part of it as it can have one or more meaning.
Thank you anyway!


Error in ApiGuardAuth.php

Hi,
I recently had no issues up until I upgraded, and am now getting the following error.
ErrorException in ApiGuardAuth.php line 14:
Argument 1 passed to Chrisbjr\ApiGuard\ApiGuardAuth::__construct() must be an instance of Chrisbjr\ApiGuard\Contracts\Providers\Auth, null given, called in
…vendor\chrisbjr\api-guard\src\Providers\ApiGuardServiceProvider.php on line 49 and defined
I saw that it had been posted before, but adding the middleware did not seem to have any effect. I recently added the laravel auth scaffolding for my application, so I'm not sure if that may have been the cause of the error.
Any help or suggestions would be greatly appreciated!

You have to check your apiguard.php config file located in the config folder for missing entries.
Just make a diff with the config file located in the vendor folder.

Hi @jakeols
@Schnoop is right - there were quiet a bit of changes in the config file so you'll need to re-publish the config file or copy/paste the missing config variables


Update references to renamed jupyterhub-home-nfs chart

fixes #4889

Hey @sunu could you help me understand what's going wrong with the GHCR package here please?

@sgibson91 this is failing because the published packages in https://github.com/orgs/2i2c-org/packages?repo_name=jupyterhub-home-nfs are all private. Can we make them public?

Can we make them public?

Yes, please do!

Is there a way to make the workflow in that repo push them publicly by default?

Ah ok, I'm on it

Is there a way to make the workflow in that repo push them publicly by default?
Once the package visibility is set to public, any new package pushed by the workflow will be public as well. But I don't know how to make the package public by default from the beginning of the top of my head

I changed the setting at the org level

Cool, I changed all the packages to be public.

GHA seems to be struggling to re-run the failed jobs, so let's leave that for a bit.

Once the package visibility is set to public, any new package pushed by the workflow will be public as well.

This is fine. It's a one-time action per package, and I don't think we'll be adding more soon :)

Hmmmm, still can't pull the image :/

@sgibson91 I made a fix by creating a new release of the helm chart and using that here. The previous versions were only accessible under the old name.

Thanks for the assist @sunu!


discover segmentation fault after writing resource attributes

Hi there,
Using the sample server/client I am getting a segmentation fault by first writing attributes to the client such as: attr 0 /31024/10/1 10 20 and then attempting a discover: disc 0 /31024
The client crashes at discover.c:91
else if (objectParamP->toSet & LWM2M_ATTR_FLAG_MIN_PERIOD)
objectParamP is NULL
Best regards,
Phil

The segmentation fault I reported on August 17 is corrected by first testing objectParamP for a NULL assignment. This test is performed in two places in discover.c
91         else if (objectParamP != NULL)
92         {
93             if (objectParamP->toSet & LWM2M_ATTR_FLAG_MIN_PERIOD)
94             {
............................

@sbertin-telular, you should check if this "fix" is needed.

This issue does still exist on master.


Sound 22

Describe the bug
Sound works on big sur but not Monterey
To Reproduce
Steps to reproduce the behavior:

Boot macOS
Play audio

Expected behavior
I expected to have audio feedback
Screenshots
Nan
macOS Info:

OS: Monterey
Version 12
Laptop Model: t450

Try turning on Codeccommander.kexy inside config.plist

Going to try it now 👍

Worked like a charm thank you

Worked like a charm thank you

No problem. I'll turn it on too since it seems to still affect Monterey users


Add protected mocking ctors

And rename Storage.Management to it's correct name.

So, in Track 2, is everything that is management plan in Azure.Management?

So, in Track 2, is everything that is management plane in Azure.Management?

That's that current plan of action that might still change.

That seems a little confusing... take Azure.AI.ConitiveServices. So, a management plane namespace would be Azure.Managment.AI.CognitiveServices? It seems like it would be better as Azure.AI.CognitiveServices.Management. For Storage, if you want to both create a storage container and then put a blob into it, you need to access 2 different namespaces... :-/

Feel free to start a discussion on this topic in the channel. It's not being decided here.


[trel-dnssd] Integrate TREL DNS-SD with avahi and mdnssd

This commit implements TREL DNS-SD module:

Register local TREL service to mDNS publishers
Browse remote TREL services from mDNS Publishers and maintain TREL peers

Some hints on implementation:

TREL DNS-SD uses Extended Address as the TREL service instance name
TREL DNS-SD pauses until all three conditions are met:

TREL DNS-SD was enabled by TREL core
TREL network interface (e.g. WiFi interface) is ready
mDNS Publisher is ready

Depends on #1183

@wgtdkp further comments?


Suppress incorrect CA2257 warnings

This PR suppresses some incorrect CS2257 warnings that were polluting our build output. As per the docs:

"Since a type that implements IDynamicInterfaceCastable may not implement a dynamic interface in metadata, calls to an instance interface member that is not an explicit implementation defined on this type are likely to fail at run time. To avoid run-time errors, mark new interface members static."

This clearly doesn't apply to these cases, since these members were just nested types, and not something you can invoke.

Related to https://github.com/dotnet/roslyn-analyzers/issues/7106


Full length Log In/Register Page

How do I add a Full-length login page in sigma react? when I add the login route it still shows the topbar and sidebar.
I think the solution is to add a new layout but I do not know how to do that.

Could you please let us know if the problem still continues? For now, I'm closing this.


Device disconnected

Connected to a remote phone, but the connection failed
~: ssh -L 6289:<IP_ADDRESS>:5555<EMAIL_ADDRESS>~:  adb connect <IP_ADDRESS>:6289
~:  scrcpy -s <IP_ADDRESS>:6289

2019-12-10 16:50:59.540 scrcpy[8142:153834] INFO: scrcpy 1.11 <https://github.com/Genymobile/scrcpy>
/usr/local/Cellar/scrcpy/1.11/share/sc...shed. 0.3 MB/s (25454 bytes in 0.076s)
error: more than one device/emulator
2019-12-10 16:50:59.759 scrcpy[8142:153834] ERROR: "adb reverse" returned with value 1
2019-12-10 16:50:59.759 scrcpy[8142:153834] WARN: 'adb reverse' failed, fallback to 'adb forward'
2019-12-10 16:51:00.258 scrcpy[8142:153834] INFO: Initial texture: 1280x720
[server] ERROR: Exception on thread Thread[main,5,main]2019-12-10 16:51:00.380 scrcpy[8142:153834] WARN: Device disconnected

https://github.com/Genymobile/scrcpy#ssh-tunnel (also see #242)


SD Card, Download and Run, no Program tab or Run time update,

ioSender 2.0.42   I don't know if this should be reported in grblHAL or ioSender Issues. Please forgive if misplaced.
In SD Card panel, right click on valid GCode file,  select Download and Run
It switches back to Grbl panel, the program runs, 3D View updates correctly but Program stays on first block and Run time in lower right stays at 0:00:00
If you use Run (SD Card panel, right click, select Run), Program panel remains blank but Run time in lower right does update correctly.
Pico grblHAL,
[VER:1.1f.20230704:]
[OPT:VNMSL2,35,1024,3,0]
[AXS:3:XYZ]
[NEWOPT:ENUMS,RT+,ES,SED,RTC,WIFI,FTP,SD,YM]
[FIRMWARE:grblHAL]
[NVS STORAGE:*FLASH]
[DRIVER:RP2040]
[DRIVER VERSION:230525]
[DRIVER OPTIONS:SDK_1.5.0]
[BOARD:PicoCNC]
[AUX IO:1,8,0,0]
[WIFI MAC:28:cd:c1:06:dd:2a]
[IP:<IP_ADDRESS>]
[NETCON:Telnet]
[PLUGIN:SDCARD v1.09]
[PLUGIN:FS macro plugin v0.03]

update.  It seems that the previous value of Run Time is left over when you do a Download and run.

I'll fix the Run Time issue. However, keeping the program listing in sync is not easy to get working - it would likely require gcode with line numbers and line number reporting enabled. Or streaming the gcode from the sender instead of from the SD card...

OK.  Thanks for looking into it.

The latest edge version has a fix for the Run Time issue.


fix: Literal backtick inside inline code

resolve: #56

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
230

Relevant Lines:
230

💛  - Coveralls

Sorry for the late reply. The fix looks elegant and will be included in version 4.2.1.


Update Gradle to 8.9

Description
Update Gradle to 8.9
Issues Resolved
N/A
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@andrross @sarthakaggarwal97 mind please taking a look folks? thank you


How many face images used to train the face-ip-adaptor?

Hi, authors
The face-ip-adaptor works relatively well.

Thx

@fortunechen we use about 40w images containing people

Is the face encoder trained from scratch or from common encoder trained from 10M common images?

@fortunechen hi, in current version, we use openclip ViT-H as image encoder

is the resampler only trained on 40w images ? Maybe it can be resumed from previous ckpt trained on 10M common images(according to the paper), then trained on 40w images

@fortunechen no, we don't use the previous ckpt, but maybe we can try it.

@fortunechen we use about 40w images containing people

Does this mean 40,000 or 400,000?

400,000

Does this face dataset only include faces? Does it also include the upper body?

@lxd941213 For better generalization, we do not specially deal with the person image. In other words, the dataset contains a wide variety of person images. Maybe we only crop a part of body, we can achive more better results.

为了更好地概括，我们不专门处理人物形象。换句话说，数据集包含各种各样的人物图像。也许我们只裁剪身体的一部分，我们可以取得更好的效果。

How to deal with the caption corresponding to the image? The caption should also include content that has nothing to do with faces, right? For example, there will be descriptors such as environment.

@lxd941213 For better generalization, we do not specially deal with the person image. In other words, the dataset contains a wide variety of person images. Maybe we only crop a part of body, we can achive more better results.

How to deal with the caption corresponding to the image? The caption should also include content that has nothing to do with faces, right? For example, there will be descriptors such as environment.

@lxd941213 we just use the original caption. Because image condition tend to be stronger than text condition, so this is not a problem.

@xiaohu2015  thank you

40w images in LAION-2B and COYO-700M?

40w images in LAION-2B and COYO-700M?

yeah


feat(avs): Add property get and clear error functions

feat(avs): Add property get and clear error functions
Use these to improve error handling by allowing
one to provide additional error information on
property related operations.

Stack created with Sapling. Best reviewed with ReviewStack.

#298
#297
#296
#295
#294
#293
#292
#291
#290
#289
-> #288
#287
#286
#285

pretty self explanatory, looks good to me why does property_clear_error return a property*, is it just a passthrough?

Don't ask me. =)
The original implementations do that because reasons.

pretty self explanatory, looks good to me why does property_clear_error return a property*, is it just a passthrough?

Don't ask me. =) The original implementations do that because reasons.

Have to correct my statement, see https://github.com/djhackersdev/bemanitools/pull/299


Initialization with a filled field containing parenthesis fails

Line 332: the value is retrieved as-is. It may contains () such as : "Greece (Ελλαδα)". Theses parenthesis seems to be interpreted as special characters in the RegExp and this country name does never match with the existing entry.
Just replaced line 332 with : var value = this.countryInput.val().replace(/(?=[() ])/g, '\'); found here : http://stackoverflow.com/questions/22872974/javascript-regex-to-escape-parentheses-and-spaces
I'am not sure if the space escaping is really necessary, thought...

I'm pretty sure that needed to be:
.replace(/(?=[() ])/g, '\');
Note the double backslash in the replacement string, rather than a single. Otherwise it escapes the closing quote and causes all kinds of havoc.


Add proper logging

The code contains print statements that could be moved to (verbose) logging.
Let's see if we can add proper logging with some verbosity levels.

I will checkout if we can use this: https://docs.rs/log/latest/log/

in another project I am working with Koen, coincidentally he suggested to use log for library things and https://docs.rs/pretty_env_logger/0.4.0/pretty_env_logger/
for binary

in another project I am working with Koen, coincidentally he suggested to use log for library things and https://docs.rs/pretty_env_logger/0.4.0/pretty_env_logger/
for binary

@simisimis I will take a look, if you know (or you could find out) why he had that preference, please share, I am really curious to know.


retrieves the storage data in any way?

While I respect that long term location tracking/logging is out of scope for the project,

Hauk is intended as a short-term location sharing service, and long-term sharing is really not in scope of the project

I (and seemingly some other users too) personally would like to make the location data rather persistent.
I've so far tried the following ways to retrieve the data:
Memcached  way:
$ memcdump --servers=localhost
# => it shows only two keys (while I expected a dumped data of the historical location data)

API way:
curl 'https://hauk.mysite.com/api/fetch.php?id=ABCD-1234&since=1697813273.711'
# => it can get the locations, but at most 7 or so array of data (not the all historical data)

PHP way:
$file = fopen("location.txt", "a");
    fwrite($file, json_encode([$lat, $lon, $time, $provider, $accuracy, $speed]));
    fclose($file);
# => it seems this causes an error that leads to show "session expired" on the shared urls

For now, I'm using the chrome + mitmproxy way (it uses mitmproxy as a man in the middle proxy whereby it logs the /fetch.php api responses onto a file through a python script), but this method is 1. a little lengthy and complicated 2. solely sharing is not enough but accessing the shared url on the chrome instance is necessary, so any server-side way solution would be nicer for me. I also expect to know some apis or hooks for this kind of needs if there's any. But anyways a patching idea suffice my needs if modifying the source code is the only way. Thanks for your help.

Related: https://github.com/bilde2910/Hauk/issues/174
I didn't find a way to actually survive a server restart :(

Couldn't agree more that a more permanent solution would be preferable.
Until then, it's services I'd rather not provide my data too sadly.

@TheCataliasTNT2k

Use an external redis, make it permanent, boom, done.

And when you restart that one?


Set high ulimit in travis.yml.

Fixes #497

till TBR on 3 successful green re-runs of the pypy shard for CI relief

reviving and TBR'ing this - since I think it's an innocuous enough change and seems to at least help with the pypy open files problem.

I was able to fix this problem locally by passing -n instead

ah, good eye - that's precisely what I had meant to do here.


Fixed-wing control bug: Stuttering rudder even in manual mode

Describe the bug
For fixed-wing aircraft, even in manual control mode, the rudder is stuttering significantly as soon as a constant aileron input is given via a remote controller. This was tested on 3 different platforms with a PX4FMUv3 with the current master, but the bug has existed for quite some time. This is a low-level control bug that should be removed ASAP. It is linked to the FW_RLL_TO_YAW_FF parameter, i.e. if that parameter is zero you will not see the issue.
To Reproduce

Set FW_RLL_TO_YAW_FF > 0. In the screenshot below. we use FW_RLL_TO_YAW_FF=0.2 .
go to manual mode and give a constant aileron input
The rudder stutters (although you might not be able to see that due to the mechanical setup of your platform). The actuator_control_target0 group shows that even though control.0 (aileron) is constant, control.2 (rudder) is jumping.

Root cause
The issue is that this line increments the rudder output every time that it is called, however, the actual manual control input (i.e. the base value which is incremented) is only reset when the manual_control_setpoint topic is updated. So if the controller runs at say 100Hz, but the manual_control_setpoint topic is only updated at 50Hz, then the rudder output will be incremented ca. 2 times by FW_RLL_TO_YAW_FF before it is reset to the actual control input. This is what you see in the screenshot above. Now the actual check whether manual_control_setpoint was updated is done here, and depending on that the _actuators variable is assigned a new value or not here.
I tested that just assigning replacing line 270 by if (_vcontrol_mode.flag_control_manual_enabled), i.e. ALWAYS assigning the _actuators variables even if the respective manual control inputs were not updated, works. The final question is: Does anything speak against just always updating these variables? That would solve the problem.
I could submit a PR for that. I'd even consider that a hot-fix, because if the value of FW_RLL_TO_YAW_FF is large (say 1.0), then the rudder oscillations will be significant and can even lead to significant yaw-axis instability of the plane in flight.

Off the bat I’d say always updating is fine.

Fixed in ba2cf5fa9a20a1577f9a9153df4f793f9e49c8f6, closing.


Update jsonwebtoken dependency

According to the migration notes from jsonwebtoken v7 to v8, this update appears to be fine.
This should also fix #20

Would love to get this merged to quiet the github security alerts. @AshanFernando / others with write access mind taking a look


couldn't find DSO to load: libhermes-executor-debug.so after upgrading from RN 0.65.0 to 0.70.4

Description
After upgrading RN project from 0.65.0 to 0.70.4 I end up in a problem with crashing app on start. The error appears in both debug and release build but in release build error cause app to freeze on splash screen. I tried all available solutions online but nothing didn't help.
Build.gradle:
project.ext.react = [
        enableHermes: true,
        enableVmCleanup: false,
]

apply from: '../../node_modules/react-native/react.gradle'

def enableSeparateBuildPerCPUArchitecture = false
def enableProguardInReleaseBuilds = true
def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get('enableHermes', true)
def reactNativeArchitectures() {
    def value = project.getProperties().get("reactNativeArchitectures")
    return value ? value.split(",") : ["armeabi-v7a", "x86", "x86_64", "arm64-v8a"]
}

My dependencies:
dependencies {

    implementation platform('com.google.firebase:firebase-bom:28.4.0')

    implementation 'com.facebook.soloader:soloader:0.10.4+'

    implementation 'androidx.constraintlayout:constraintlayout:2.0.4'

    implementation 'androidx.work:work-runtime-ktx:2.7.0'

    implementation 'com.android.support:multidex:1.0.3'
    implementation fileTree(dir: 'libs', include: ['*.jar'])

    implementation 'com.facebook.react:react-native:' // From node_modules

    implementation 'androidx.appcompat:appcompat:1.2.0'
    implementation 'androidx.annotation:annotation:1.2.0'
    implementation 'androidx.swiperefreshlayout:swiperefreshlayout:1.1.0'

    implementation 'com.google.android.gms:play-services-base:17.6.0'

    implementation 'me.leolin:ShortcutBadger:1.1.22@aar'
    implementation project(':react-native-config')

    debugImplementation("com.facebook.flipper:flipper:${FLIPPER_VERSION}") {
        exclude group:'com.facebook.fbjni'
    }

    debugImplementation("com.facebook.flipper:flipper-network-plugin:${FLIPPER_VERSION}") {
        exclude group:'com.facebook.flipper'
        exclude group:'com.squareup.okhttp3', module:'okhttp'
    }

    debugImplementation("com.facebook.flipper:flipper-fresco-plugin:${FLIPPER_VERSION}") {
        exclude group:'com.facebook.flipper'
    }

    huaweiImplementation 'com.huawei.hms:hianalytics:<IP_ADDRESS>2'

    if (enableHermes) {
        //noinspection GradleDynamicVersion
        implementation("com.facebook.react:hermes-engine:+") { // From node_modules
            exclude group:'com.facebook.fbjni'
        }
    } else {
        implementation jscFlavor
    }
}

Version
0.70.4
Output of npx react-native info
System:
OS: macOS 12.6.1
CPU: (10) arm64 Apple M1 Pro
Memory: 101.31 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.14.2 - /usr/local/bin/node
Yarn: Not Found
npm: 7.21.1 - ~/projects/uc-chameleon-nova-portal-app/node_modules/.bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.3 - /Users/urosuzelac/.rvm/gems/ruby-2.7.5/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.0.1/14A400 - /usr/bin/xcodebuild
Languages:
Java: <IP_ADDRESS> - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.4 => 0.70.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
After starting the app there is just Splash Screen in freezed state. This happens only in release build. In debug build error is just shown in Logcat.
Snack, code example, screenshot, or link to a repository
 couldn't find DSO to load: libhermes-executor-debug.so                                                                                SoSource 0: com.facebook.soloader.a[root = /data/data/com.ucnewsportal/lib-main flags = 1]                                                                                SoSource 1: com.facebook.soloader.d[root = /data/app/com.ucnewsportal-sPK_xK9tZWkhxvAZOwVmJA==/lib/arm64 flags = 0]                                                                                SoSource 2: com.facebook.soloader.d[root = /system/lib64 flags = 2]                                                                                SoSource 3: com.facebook.soloader.d[root = /vendor/lib64 flags = 2]                                                                                Native lib dir: /data/app/com.ucnewsportal-sPK_xK9tZWkhxvAZOwVmJA==/lib/arm64                                                                                result: 0

i am having the same problem. :(

Me Too

Me Too..

The only thing that worked for me was disabling Hermes in app/build.gradle
project.ext.react = [
    enableHermes: false,  // clean and rebuild if changing
]

After long process of trial and error, we finally found out what was causing Android realise build to freeze at start up. It was babel-plugin-minify-dead-code-elimination that we were using in our project.
In our babel.config.js file there was this plugin enabled
env: {
   production: {
     plugins: [['minify-dead-code-elimination', { optimizeRawSize: true }]],
   },
}

after upgrading babel-plugin-minify-dead-code-elimination from 0.5.1 to 0.5.2 we finally managed to build our Android realise build successfully.
I hope that this will help someone upgrading from RN 0.65.0 to newer version and save a lot of hours of searching for
the solution.
About libhermes-executor-debug.so, this actually will not cause your app stop working. You can try realise build with new clean project and you will see the same error message. If your app is not working it is not up to libhermes-executor-debug.so it is something else.
Happy hacking!

--------- beginning of crash
11-19 16:48:33.038 10319 10319 E AndroidRuntime: FATAL EXCEPTION: main
11-19 16:48:33.038 10319 10319 E AndroidRuntime: Process: com.a07061, PID: 10319
11-19 16:48:33.038 10319 10319 E AndroidRuntime: com.facebook.react.uimanager.IllegalViewOperationException: No ViewManager found for class RCTText
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.uimanager.ViewManagerRegistry.get(ViewManagerRegistry.java:68)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.fabric.mounting.SurfaceMountingManager.createViewUnsafe(SurfaceMountingManager.java:857)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.fabric.mounting.SurfaceMountingManager.preallocateView(SurfaceMountingManager.java:1250)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.fabric.mounting.mountitems.PreAllocateViewMountItem.execute(PreAllocateViewMountItem.java:63)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.fabric.mounting.MountItemDispatcher.executeOrEnqueue(MountItemDispatcher.java:351)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.fabric.mounting.MountItemDispatcher.dispatchPreMountItems(MountItemDispatcher.java:330)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.fabric.FabricUIManager$DispatchUIFrameCallback.doFrameGuarded(FabricUIManager.java:1248)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.fabric.GuardedFrameCallback.doFrame(GuardedFrameCallback.java:31)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.modules.core.ReactChoreographer$ReactChoreographerDispatcher.doFrame(ReactChoreographer.java:175)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.facebook.react.modules.core.ChoreographerCompat$FrameCallback$1.doFrame(ChoreographerCompat.java:85)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at android.view.Choreographer$CallbackRecord.run(Choreographer.java:970)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at android.view.Choreographer.doCallbacks(Choreographer.java:796)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at android.view.Choreographer.doFrame(Choreographer.java:727)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:957)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:938)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:99)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:223)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:7656)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
11-19 16:48:33.038 10319 10319 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
11-19 16:48:33.039   511  1513 W ActivityTaskManager:   Force finishing activity com.a07061/.MainActivity
11-19 16:48:33.039   511 10349 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
11-19 16:48:33.043   313   369 D goldfish-address-space: claimShared: Ask to claim region [0x3f74fc000 0x3f7aff000]

The app keeps crashing like this on first boot.

The only thing that worked for me was disabling Hermes in app/build.gradle
project.ext.react = [
    enableHermes: false,  // clean and rebuild if changing
]

That worked for me! Thanks

How to fix it?


stop tracking the bcfishpass.splite changes in repo unless changes to underlying tables actually happens and eventually serve db from elsewhere

Everytime we touch our sqlite database it logs in git as a change. Not sure if it is because it is binary or because of metadata updates but regardless it will balloon our repo.
For now lets stop tracking the bcfishpass.sqlite changes in repo unless changes to underlying tables actually happen by running the script below
 git update-index --assume-unchanged data/bcfishpass.sqlite. When changes actually occur we use git update-index --no-assume-unchanged data/bcfishpass.sqlite to log a commit
@Mateo9569 please run the assume-unchanged command in your terminal.    Then can you please make a wee note here to confirm it worked?
Once/if we move the whole sqlite database to a remote spot we can all access we can close this issue.

I ran the git unchanged command and then ran the tables script. The script ran fine. But then I got these files showing up in my git window.

naturally.  Those are from fpr::fpr_import_hab_con() .  Thats how we back up our versions of the fish submission template in a format that is easy to track.  We will have a similiar system for the pscis imports in place soon too.
Unrelated to the sqlite.  If it doesn't show the sqlite in the git window after you accessed the database (like through the tables.R script  it worked!
Try the same thing with git update-index --assume-unchanged data/habitat_confirmations.xls .  then open the file and close it.  It shouldn't show in the git window even though git doesn't know it hasn't changed.  After the test  unignore it again with a git update-index --no-assume-unchanged data/habitat_confirmations.xls until we get a stable version that we are unlikely to need to change often.....

airvine at Allans-MacBook-Pro in ~/Projects/repo/fish_passage_skeena_2022_reporting on main [!?]
$ git update-index --no-assume-unchanged data/bcfishpass.sqlite
fatal: Unable to mark file data/bcfishpass.sqlite


Additional ktx-ashley extensions

From what I know it is a best practice in ashley to remove entities at the end of a frame or at the beginning, when using a PooledEngine because otherwise you sometimes get strange behaviors when removing and adding entities within the same frame.
Therefore, I use a RemoveComponent in most of my projects that is added to an entity to mark it as being removed. Some IteratingSystems then exclude entities with a RemoveComponent. A RemoveSystem is then added at the end or at the front of all engine systems which then removes such entities from the engine.
There is no kotlin extension for that, from what I have seen and that's why you have to write something like
entity.add(engine.createComponent(RemoveComponent::class.java))

Might be a good idea to have the existing with function from the creation DSL for such things?
entity.with<RemoveComponent>

or something similar?
Also, very rarely you need to access certain systems from the engine. Here, I also could not find a kotlin counterpart and the current code is like:
engine.getSystem(SomeSystem::class.java)

Would it be possible to have something like:
engine[RemoveSystem::class]
// or
engine<RemoveSystem>

I could try something out on the weekend and provide a PR. What would be the preferred solutions?

I'll have to review Ashley module to give you more insights. You're welcome to submit the PR, if you already have a prototype of these features.
@Jkly Thoughts?

@Quillraven
Entity has no access to engine after creation, so we would either have to return EngineEntity (which has the with extension for adding components) or add a utility method such as Entity.addComponent<Type>(engine).
inline fun <reified C: Component> Entity.addComponent(engine: Engine, configure: (@AshleyDsl C).() -> Unit): C {
  val component = engine.create(configure)
  add(component)
  return component
}

// Usage example:
class Transform(var x: Float = 0f, var y: Float = 0f) : Component
fun example(entity: Entity, engine: Engine) {
  entity.addComponent<Transform>(engine) {
    x = 10f
    y = 10f
  }
}

As for the system, we could add something like this:
inline fun <reified S: EntitySystem> Engine.getSystem() = getSystem(S::class.java)

// Usage:
engine.getSystem<MySystem>()

If you'd like to refine my examples and write the tests, you're welcome to submit a PR. Otherwise I'll look into it during the weekend.

I can do that tomorrow,no problem  :)


Fix reboot loop: Update comparison date method

The problem arose from the fact that the date of the next update was compared with the current date 01/01/2024 is less than 12/31/2023 (compared values) and therefore launches a full update.

Addition of a global variable to determine the format for saving variables in the INI file
Save in yyyy-MM-dd HH:mm:ss format to ensure functional comparison over time
Modification of the default value when receiving variables from the INI file


Support for v8.10.0

Hi Callum,
Is there any possibility you could please bring this up-to-date to support 8.10.0. I have tried adding the package and it just fails to boot.
Regards
Toby.

Callum,
We are also needing something like this. My system does not fail to boot but when adding the keys to Web.config it just has no impact. Examine.ExternalIndex.SupportProtectedContent remains set to false. I am using ver 8.10.1. Any help would be greatly appreciated.
Regards,
Robbie

8.11.1.- fails to boot after install.

I have a similar issue with v8.12.2 where the boot fails.
When I remove the Our.Umbraco.ExamineConfig.dll from bin folder the site is running again.


enhancement #555: improved endpoint for displaying teachers in a specific discipline

enhancement #555: improved endpoint for displaying teachers in a specific discipline

added disciplineType for getting teachers
added swagger documentation
fixed bug with rating
added responses

closes #555

Undocumented exception

Undocumented / Unhandled exception


Add storage root folder prefix to startAfter flag

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

Project coverage is 29.79%. Comparing base (f83837b) to head (37c5c05).

Files with missing lines
Patch %
Lines

pkg/service/storage/azure.go
0.00%
1 Missing :warning:

pkg/service/storage/gcp.go
0.00%
1 Missing :warning:

pkg/service/storage/operations.go
0.00%
1 Missing :warning:

pkg/service/storage/s3.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##               v2     #270   +/-   ##
=======================================
  Coverage   29.79%   29.79%
=======================================
  Files          41       41
  Lines        2346     2346
=======================================
  Hits          699      699
  Misses       1556     1556
  Partials       91       91

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests