[BUG]

Context

ElasticDump version - Latest
Elasticsearch version-  Latest
Node.js version (note that nodejs v10+ is required for this tool) Latest
Full command you are having issue with (with inputs and outputs)
A data-set you can share publicly which reproduces the problem
(py2env) [jmk7972@i4-csx-esm03 ~]$ elasticdump \

--input=http://localhost:9200/test_new_pdfmef_index
--output=/mnt/gstorage03/machinebackup-temp/es-snapshots/test_new_pdfmef_index.json
--type=data
--limit=10000
--fsCompress
My index has 36gb data,
Wed, 24 Apr 2024 02:24:43 GMT | starting dump
Wed, 24 Apr 2024 02:24:50 GMT | got 10000 objects from source elasticsearch (offset: 0)
Wed, 24 Apr 2024 02:24:54 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:25:04 GMT | got 10000 objects from source elasticsearch (offset: 10000)
Wed, 24 Apr 2024 02:25:08 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:25:18 GMT | got 10000 objects from source elasticsearch (offset: 20000)
Wed, 24 Apr 2024 02:25:21 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:25:31 GMT | got 10000 objects from source elasticsearch (offset: 30000)
Wed, 24 Apr 2024 02:25:35 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:25:44 GMT | got 10000 objects from source elasticsearch (offset: 40000)
Wed, 24 Apr 2024 02:25:47 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:25:56 GMT | got 10000 objects from source elasticsearch (offset: 50000)
Wed, 24 Apr 2024 02:25:59 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:26:09 GMT | got 10000 objects from source elasticsearch (offset: 60000)
Wed, 24 Apr 2024 02:26:12 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:26:22 GMT | got 10000 objects from source elasticsearch (offset: 70000)
Wed, 24 Apr 2024 02:26:25 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:26:36 GMT | got 10000 objects from source elasticsearch (offset: 80000)
Wed, 24 Apr 2024 02:26:40 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:26:50 GMT | got 10000 objects from source elasticsearch (offset: 90000)
Wed, 24 Apr 2024 02:26:53 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:27:03 GMT | got 10000 objects from source elasticsearch (offset: 100000)
Wed, 24 Apr 2024 02:27:06 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:27:16 GMT | got 10000 objects from source elasticsearch (offset: 110000)
Wed, 24 Apr 2024 02:27:19 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:27:30 GMT | got 10000 objects from source elasticsearch (offset: 120000)
Wed, 24 Apr 2024 02:27:34 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:27:44 GMT | got 10000 objects from source elasticsearch (offset: 130000)
Wed, 24 Apr 2024 02:27:48 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:27:59 GMT | got 10000 objects from source elasticsearch (offset: 140000)
Wed, 24 Apr 2024 02:28:03 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:28:15 GMT | got 10000 objects from source elasticsearch (offset: 150000)
Wed, 24 Apr 2024 02:28:19 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:28:33 GMT | got 10000 objects from source elasticsearch (offset: 160000)
Wed, 24 Apr 2024 02:28:36 GMT | sent 10000 objects to destination file, wrote 10000
Wed, 24 Apr 2024 02:28:56 GMT | Error Emitted => connect ECONNREFUSED <IP_ADDRESS>:9200
Wed, 24 Apr 2024 02:28:56 GMT | Error Emitted => connect ECONNREFUSED <IP_ADDRESS>:9200
Wed, 24 Apr 2024 02:28:56 GMT | Total Writes: 0
Wed, 24 Apr 2024 02:28:56 GMT | dump ended with error (get phase) => Error: connect ECONNREFUSED <IP_ADDRESS>:9200

Describe the bug
Suddenly it stopped and crashed the Elastic search service running in that node.
So should i decrease batch size to 1000? What might be the problem?

Further help
I have 900gb index to dump to a file, Please recommend me something to dump the index?
** Ran again with batch 1000 **
(py2env) [jmk7972@i4-csx-esm03 ~]$ elasticdump   --input=http://localhost:9200/test_new_pdfmef_index   --output=/mnt/gstorage03/machinebackup-temp/es-snapshots/test_new_pdfmef_index.json   --type=data   --limit=1000   --fsCompress
Wed, 24 Apr 2024 17:51:28 GMT | starting dump
Wed, 24 Apr 2024 17:51:29 GMT | got 1000 objects from source elasticsearch (offset: 0)
Wed, 24 Apr 2024 17:51:29 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:30 GMT | got 1000 objects from source elasticsearch (offset: 1000)
Wed, 24 Apr 2024 17:51:31 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:32 GMT | got 1000 objects from source elasticsearch (offset: 2000)
Wed, 24 Apr 2024 17:51:32 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:34 GMT | got 1000 objects from source elasticsearch (offset: 3000)
Wed, 24 Apr 2024 17:51:34 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:35 GMT | got 1000 objects from source elasticsearch (offset: 4000)
Wed, 24 Apr 2024 17:51:36 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:37 GMT | got 1000 objects from source elasticsearch (offset: 5000)
Wed, 24 Apr 2024 17:51:37 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:39 GMT | got 1000 objects from source elasticsearch (offset: 6000)
Wed, 24 Apr 2024 17:51:39 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:40 GMT | got 1000 objects from source elasticsearch (offset: 7000)
Wed, 24 Apr 2024 17:51:41 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:42 GMT | got 1000 objects from source elasticsearch (offset: 8000)
Wed, 24 Apr 2024 17:51:42 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:44 GMT | got 1000 objects from source elasticsearch (offset: 9000)
Wed, 24 Apr 2024 17:51:44 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:45 GMT | got 1000 objects from source elasticsearch (offset: 10000)
Wed, 24 Apr 2024 17:51:46 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:47 GMT | got 1000 objects from source elasticsearch (offset: 11000)
Wed, 24 Apr 2024 17:51:47 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:48 GMT | got 1000 objects from source elasticsearch (offset: 12000)
Wed, 24 Apr 2024 17:51:48 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:49 GMT | got 1000 objects from source elasticsearch (offset: 13000)
Wed, 24 Apr 2024 17:51:50 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:51 GMT | got 1000 objects from source elasticsearch (offset: 14000)
Wed, 24 Apr 2024 17:51:51 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:53 GMT | got 1000 objects from source elasticsearch (offset: 15000)
Wed, 24 Apr 2024 17:51:53 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:54 GMT | got 1000 objects from source elasticsearch (offset: 16000)
Wed, 24 Apr 2024 17:51:54 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:55 GMT | got 1000 objects from source elasticsearch (offset: 17000)
Wed, 24 Apr 2024 17:51:56 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:57 GMT | got 1000 objects from source elasticsearch (offset: 18000)
Wed, 24 Apr 2024 17:51:57 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:51:58 GMT | got 1000 objects from source elasticsearch (offset: 19000)
Wed, 24 Apr 2024 17:51:59 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:00 GMT | got 1000 objects from source elasticsearch (offset: 20000)
Wed, 24 Apr 2024 17:52:00 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:02 GMT | got 1000 objects from source elasticsearch (offset: 21000)
Wed, 24 Apr 2024 17:52:02 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:03 GMT | got 1000 objects from source elasticsearch (offset: 22000)
Wed, 24 Apr 2024 17:52:04 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:05 GMT | got 1000 objects from source elasticsearch (offset: 23000)
Wed, 24 Apr 2024 17:52:05 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:06 GMT | got 1000 objects from source elasticsearch (offset: 24000)
Wed, 24 Apr 2024 17:52:07 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:08 GMT | got 1000 objects from source elasticsearch (offset: 25000)
Wed, 24 Apr 2024 17:52:08 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:09 GMT | got 1000 objects from source elasticsearch (offset: 26000)
Wed, 24 Apr 2024 17:52:09 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:10 GMT | got 1000 objects from source elasticsearch (offset: 27000)
Wed, 24 Apr 2024 17:52:10 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:11 GMT | got 1000 objects from source elasticsearch (offset: 28000)
Wed, 24 Apr 2024 17:52:11 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:12 GMT | got 1000 objects from source elasticsearch (offset: 29000)
Wed, 24 Apr 2024 17:52:13 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:14 GMT | got 1000 objects from source elasticsearch (offset: 30000)
Wed, 24 Apr 2024 17:52:14 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:15 GMT | got 1000 objects from source elasticsearch (offset: 31000)
Wed, 24 Apr 2024 17:52:16 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:17 GMT | got 1000 objects from source elasticsearch (offset: 32000)
Wed, 24 Apr 2024 17:52:17 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:18 GMT | got 1000 objects from source elasticsearch (offset: 33000)
Wed, 24 Apr 2024 17:52:19 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:20 GMT | got 1000 objects from source elasticsearch (offset: 34000)
Wed, 24 Apr 2024 17:52:20 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:21 GMT | got 1000 objects from source elasticsearch (offset: 35000)
Wed, 24 Apr 2024 17:52:22 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:23 GMT | got 1000 objects from source elasticsearch (offset: 36000)
Wed, 24 Apr 2024 17:52:23 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:24 GMT | got 1000 objects from source elasticsearch (offset: 37000)
Wed, 24 Apr 2024 17:52:25 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:26 GMT | got 1000 objects from source elasticsearch (offset: 38000)
Wed, 24 Apr 2024 17:52:26 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:27 GMT | got 1000 objects from source elasticsearch (offset: 39000)
Wed, 24 Apr 2024 17:52:27 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:28 GMT | got 1000 objects from source elasticsearch (offset: 40000)
Wed, 24 Apr 2024 17:52:29 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:30 GMT | got 1000 objects from source elasticsearch (offset: 41000)
Wed, 24 Apr 2024 17:52:30 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:31 GMT | got 1000 objects from source elasticsearch (offset: 42000)
Wed, 24 Apr 2024 17:52:31 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:32 GMT | got 1000 objects from source elasticsearch (offset: 43000)
Wed, 24 Apr 2024 17:52:32 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:33 GMT | got 1000 objects from source elasticsearch (offset: 44000)
Wed, 24 Apr 2024 17:52:33 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:34 GMT | got 1000 objects from source elasticsearch (offset: 45000)
Wed, 24 Apr 2024 17:52:35 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:35 GMT | got 1000 objects from source elasticsearch (offset: 46000)
Wed, 24 Apr 2024 17:52:36 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:37 GMT | got 1000 objects from source elasticsearch (offset: 47000)
Wed, 24 Apr 2024 17:52:37 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:38 GMT | got 1000 objects from source elasticsearch (offset: 48000)
Wed, 24 Apr 2024 17:52:39 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:40 GMT | got 1000 objects from source elasticsearch (offset: 49000)
Wed, 24 Apr 2024 17:52:40 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:41 GMT | got 1000 objects from source elasticsearch (offset: 50000)
Wed, 24 Apr 2024 17:52:42 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:43 GMT | got 1000 objects from source elasticsearch (offset: 51000)
Wed, 24 Apr 2024 17:52:43 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:44 GMT | got 1000 objects from source elasticsearch (offset: 52000)
Wed, 24 Apr 2024 17:52:45 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:46 GMT | got 1000 objects from source elasticsearch (offset: 53000)
Wed, 24 Apr 2024 17:52:46 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:47 GMT | got 1000 objects from source elasticsearch (offset: 54000)
Wed, 24 Apr 2024 17:52:47 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:48 GMT | got 1000 objects from source elasticsearch (offset: 55000)
Wed, 24 Apr 2024 17:52:48 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:49 GMT | got 1000 objects from source elasticsearch (offset: 56000)
Wed, 24 Apr 2024 17:52:50 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:51 GMT | got 1000 objects from source elasticsearch (offset: 57000)
Wed, 24 Apr 2024 17:52:51 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:52 GMT | got 1000 objects from source elasticsearch (offset: 58000)
Wed, 24 Apr 2024 17:52:52 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:53 GMT | got 1000 objects from source elasticsearch (offset: 59000)
Wed, 24 Apr 2024 17:52:53 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:54 GMT | got 1000 objects from source elasticsearch (offset: 60000)
Wed, 24 Apr 2024 17:52:54 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:55 GMT | got 1000 objects from source elasticsearch (offset: 61000)
Wed, 24 Apr 2024 17:52:56 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:57 GMT | got 1000 objects from source elasticsearch (offset: 62000)
Wed, 24 Apr 2024 17:52:57 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:58 GMT | got 1000 objects from source elasticsearch (offset: 63000)
Wed, 24 Apr 2024 17:52:58 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:52:59 GMT | got 1000 objects from source elasticsearch (offset: 64000)
Wed, 24 Apr 2024 17:53:00 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:01 GMT | got 1000 objects from source elasticsearch (offset: 65000)
Wed, 24 Apr 2024 17:53:01 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:02 GMT | got 1000 objects from source elasticsearch (offset: 66000)
Wed, 24 Apr 2024 17:53:02 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:03 GMT | got 1000 objects from source elasticsearch (offset: 67000)
Wed, 24 Apr 2024 17:53:04 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:05 GMT | got 1000 objects from source elasticsearch (offset: 68000)
Wed, 24 Apr 2024 17:53:06 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:07 GMT | got 1000 objects from source elasticsearch (offset: 69000)
Wed, 24 Apr 2024 17:53:07 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:08 GMT | got 1000 objects from source elasticsearch (offset: 70000)
Wed, 24 Apr 2024 17:53:09 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:10 GMT | got 1000 objects from source elasticsearch (offset: 71000)
Wed, 24 Apr 2024 17:53:10 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:11 GMT | got 1000 objects from source elasticsearch (offset: 72000)
Wed, 24 Apr 2024 17:53:12 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:13 GMT | got 1000 objects from source elasticsearch (offset: 73000)
Wed, 24 Apr 2024 17:53:13 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:14 GMT | got 1000 objects from source elasticsearch (offset: 74000)
Wed, 24 Apr 2024 17:53:14 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:15 GMT | got 1000 objects from source elasticsearch (offset: 75000)
Wed, 24 Apr 2024 17:53:15 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:17 GMT | got 1000 objects from source elasticsearch (offset: 76000)
Wed, 24 Apr 2024 17:53:17 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:18 GMT | got 1000 objects from source elasticsearch (offset: 77000)
Wed, 24 Apr 2024 17:53:18 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:20 GMT | got 1000 objects from source elasticsearch (offset: 78000)
Wed, 24 Apr 2024 17:53:20 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:21 GMT | got 1000 objects from source elasticsearch (offset: 79000)
Wed, 24 Apr 2024 17:53:21 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:22 GMT | got 1000 objects from source elasticsearch (offset: 80000)
Wed, 24 Apr 2024 17:53:22 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:23 GMT | got 1000 objects from source elasticsearch (offset: 81000)
Wed, 24 Apr 2024 17:53:24 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:25 GMT | got 1000 objects from source elasticsearch (offset: 82000)
Wed, 24 Apr 2024 17:53:25 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:27 GMT | got 1000 objects from source elasticsearch (offset: 83000)
Wed, 24 Apr 2024 17:53:27 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:29 GMT | got 1000 objects from source elasticsearch (offset: 84000)
Wed, 24 Apr 2024 17:53:29 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:30 GMT | got 1000 objects from source elasticsearch (offset: 85000)
Wed, 24 Apr 2024 17:53:31 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:32 GMT | got 1000 objects from source elasticsearch (offset: 86000)
Wed, 24 Apr 2024 17:53:32 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:33 GMT | got 1000 objects from source elasticsearch (offset: 87000)
Wed, 24 Apr 2024 17:53:33 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:35 GMT | got 1000 objects from source elasticsearch (offset: 88000)
Wed, 24 Apr 2024 17:53:35 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:36 GMT | got 1000 objects from source elasticsearch (offset: 89000)
Wed, 24 Apr 2024 17:53:37 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:38 GMT | got 1000 objects from source elasticsearch (offset: 90000)
Wed, 24 Apr 2024 17:53:38 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:40 GMT | got 1000 objects from source elasticsearch (offset: 91000)
Wed, 24 Apr 2024 17:53:40 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:41 GMT | got 1000 objects from source elasticsearch (offset: 92000)
Wed, 24 Apr 2024 17:53:41 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:43 GMT | got 1000 objects from source elasticsearch (offset: 93000)
Wed, 24 Apr 2024 17:53:43 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:44 GMT | got 1000 objects from source elasticsearch (offset: 94000)
Wed, 24 Apr 2024 17:53:44 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:45 GMT | got 1000 objects from source elasticsearch (offset: 95000)
Wed, 24 Apr 2024 17:53:45 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:46 GMT | got 1000 objects from source elasticsearch (offset: 96000)
Wed, 24 Apr 2024 17:53:47 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:48 GMT | got 1000 objects from source elasticsearch (offset: 97000)
Wed, 24 Apr 2024 17:53:48 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:49 GMT | got 1000 objects from source elasticsearch (offset: 98000)
Wed, 24 Apr 2024 17:53:49 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:50 GMT | got 1000 objects from source elasticsearch (offset: 99000)
Wed, 24 Apr 2024 17:53:50 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:51 GMT | got 1000 objects from source elasticsearch (offset: 100000)
Wed, 24 Apr 2024 17:53:52 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:53 GMT | got 1000 objects from source elasticsearch (offset: 101000)
Wed, 24 Apr 2024 17:53:53 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:54 GMT | got 1000 objects from source elasticsearch (offset: 102000)
Wed, 24 Apr 2024 17:53:54 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:55 GMT | got 1000 objects from source elasticsearch (offset: 103000)
Wed, 24 Apr 2024 17:53:56 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:57 GMT | got 1000 objects from source elasticsearch (offset: 104000)
Wed, 24 Apr 2024 17:53:57 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:58 GMT | got 1000 objects from source elasticsearch (offset: 105000)
Wed, 24 Apr 2024 17:53:58 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:53:59 GMT | got 1000 objects from source elasticsearch (offset: 106000)
Wed, 24 Apr 2024 17:54:00 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:01 GMT | got 1000 objects from source elasticsearch (offset: 107000)
Wed, 24 Apr 2024 17:54:01 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:02 GMT | got 1000 objects from source elasticsearch (offset: 108000)
Wed, 24 Apr 2024 17:54:02 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:03 GMT | got 1000 objects from source elasticsearch (offset: 109000)
Wed, 24 Apr 2024 17:54:04 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:05 GMT | got 1000 objects from source elasticsearch (offset: 110000)
Wed, 24 Apr 2024 17:54:05 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:06 GMT | got 1000 objects from source elasticsearch (offset: 111000)
Wed, 24 Apr 2024 17:54:06 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:07 GMT | got 1000 objects from source elasticsearch (offset: 112000)
Wed, 24 Apr 2024 17:54:07 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:08 GMT | got 1000 objects from source elasticsearch (offset: 113000)
Wed, 24 Apr 2024 17:54:08 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:09 GMT | got 1000 objects from source elasticsearch (offset: 114000)
Wed, 24 Apr 2024 17:54:09 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:10 GMT | got 1000 objects from source elasticsearch (offset: 115000)
Wed, 24 Apr 2024 17:54:11 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:12 GMT | got 1000 objects from source elasticsearch (offset: 116000)
Wed, 24 Apr 2024 17:54:12 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:13 GMT | got 1000 objects from source elasticsearch (offset: 117000)
Wed, 24 Apr 2024 17:54:14 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:15 GMT | got 1000 objects from source elasticsearch (offset: 118000)
Wed, 24 Apr 2024 17:54:15 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:17 GMT | got 1000 objects from source elasticsearch (offset: 119000)
Wed, 24 Apr 2024 17:54:17 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:18 GMT | got 1000 objects from source elasticsearch (offset: 120000)
Wed, 24 Apr 2024 17:54:18 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:19 GMT | got 1000 objects from source elasticsearch (offset: 121000)
Wed, 24 Apr 2024 17:54:20 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:21 GMT | got 1000 objects from source elasticsearch (offset: 122000)
Wed, 24 Apr 2024 17:54:21 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:23 GMT | got 1000 objects from source elasticsearch (offset: 123000)
Wed, 24 Apr 2024 17:54:23 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:25 GMT | got 1000 objects from source elasticsearch (offset: 124000)
Wed, 24 Apr 2024 17:54:25 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:26 GMT | got 1000 objects from source elasticsearch (offset: 125000)
Wed, 24 Apr 2024 17:54:26 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:28 GMT | got 1000 objects from source elasticsearch (offset: 126000)
Wed, 24 Apr 2024 17:54:28 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:29 GMT | got 1000 objects from source elasticsearch (offset: 127000)
Wed, 24 Apr 2024 17:54:29 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:30 GMT | got 1000 objects from source elasticsearch (offset: 128000)
Wed, 24 Apr 2024 17:54:31 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:32 GMT | got 1000 objects from source elasticsearch (offset: 129000)
Wed, 24 Apr 2024 17:54:32 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:33 GMT | got 1000 objects from source elasticsearch (offset: 130000)
Wed, 24 Apr 2024 17:54:34 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:35 GMT | got 1000 objects from source elasticsearch (offset: 131000)
Wed, 24 Apr 2024 17:54:35 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:36 GMT | got 1000 objects from source elasticsearch (offset: 132000)
Wed, 24 Apr 2024 17:54:37 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:38 GMT | got 1000 objects from source elasticsearch (offset: 133000)
Wed, 24 Apr 2024 17:54:38 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:39 GMT | got 1000 objects from source elasticsearch (offset: 134000)
Wed, 24 Apr 2024 17:54:39 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:40 GMT | got 1000 objects from source elasticsearch (offset: 135000)
Wed, 24 Apr 2024 17:54:41 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:42 GMT | got 1000 objects from source elasticsearch (offset: 136000)
Wed, 24 Apr 2024 17:54:42 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:43 GMT | got 1000 objects from source elasticsearch (offset: 137000)
Wed, 24 Apr 2024 17:54:43 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:44 GMT | got 1000 objects from source elasticsearch (offset: 138000)
Wed, 24 Apr 2024 17:54:45 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:46 GMT | got 1000 objects from source elasticsearch (offset: 139000)
Wed, 24 Apr 2024 17:54:46 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:47 GMT | got 1000 objects from source elasticsearch (offset: 140000)
Wed, 24 Apr 2024 17:54:48 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:49 GMT | got 1000 objects from source elasticsearch (offset: 141000)
Wed, 24 Apr 2024 17:54:49 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:51 GMT | got 1000 objects from source elasticsearch (offset: 142000)
Wed, 24 Apr 2024 17:54:51 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:52 GMT | got 1000 objects from source elasticsearch (offset: 143000)
Wed, 24 Apr 2024 17:54:53 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:54 GMT | got 1000 objects from source elasticsearch (offset: 144000)
Wed, 24 Apr 2024 17:54:54 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:55 GMT | got 1000 objects from source elasticsearch (offset: 145000)
Wed, 24 Apr 2024 17:54:56 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:57 GMT | got 1000 objects from source elasticsearch (offset: 146000)
Wed, 24 Apr 2024 17:54:57 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:54:59 GMT | got 1000 objects from source elasticsearch (offset: 147000)
Wed, 24 Apr 2024 17:54:59 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:00 GMT | got 1000 objects from source elasticsearch (offset: 148000)
Wed, 24 Apr 2024 17:55:00 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:02 GMT | got 1000 objects from source elasticsearch (offset: 149000)
Wed, 24 Apr 2024 17:55:02 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:03 GMT | got 1000 objects from source elasticsearch (offset: 150000)
Wed, 24 Apr 2024 17:55:03 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:05 GMT | got 1000 objects from source elasticsearch (offset: 151000)
Wed, 24 Apr 2024 17:55:05 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:06 GMT | got 1000 objects from source elasticsearch (offset: 152000)
Wed, 24 Apr 2024 17:55:07 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:08 GMT | got 1000 objects from source elasticsearch (offset: 153000)
Wed, 24 Apr 2024 17:55:08 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:09 GMT | got 1000 objects from source elasticsearch (offset: 154000)
Wed, 24 Apr 2024 17:55:10 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:11 GMT | got 1000 objects from source elasticsearch (offset: 155000)
Wed, 24 Apr 2024 17:55:11 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:13 GMT | got 1000 objects from source elasticsearch (offset: 156000)
Wed, 24 Apr 2024 17:55:13 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:14 GMT | got 1000 objects from source elasticsearch (offset: 157000)
Wed, 24 Apr 2024 17:55:15 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:16 GMT | got 1000 objects from source elasticsearch (offset: 158000)
Wed, 24 Apr 2024 17:55:16 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:17 GMT | got 1000 objects from source elasticsearch (offset: 159000)
Wed, 24 Apr 2024 17:55:18 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:19 GMT | got 1000 objects from source elasticsearch (offset: 160000)
Wed, 24 Apr 2024 17:55:19 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:20 GMT | got 1000 objects from source elasticsearch (offset: 161000)
Wed, 24 Apr 2024 17:55:21 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:22 GMT | got 1000 objects from source elasticsearch (offset: 162000)
Wed, 24 Apr 2024 17:55:22 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:23 GMT | got 1000 objects from source elasticsearch (offset: 163000)
Wed, 24 Apr 2024 17:55:24 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:25 GMT | got 1000 objects from source elasticsearch (offset: 164000)
Wed, 24 Apr 2024 17:55:25 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:26 GMT | got 1000 objects from source elasticsearch (offset: 165000)
Wed, 24 Apr 2024 17:55:26 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:28 GMT | got 1000 objects from source elasticsearch (offset: 166000)
Wed, 24 Apr 2024 17:55:28 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:29 GMT | got 1000 objects from source elasticsearch (offset: 167000)
Wed, 24 Apr 2024 17:55:30 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:31 GMT | got 1000 objects from source elasticsearch (offset: 168000)
Wed, 24 Apr 2024 17:55:31 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:32 GMT | got 1000 objects from source elasticsearch (offset: 169000)
Wed, 24 Apr 2024 17:55:33 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:34 GMT | got 1000 objects from source elasticsearch (offset: 170000)
Wed, 24 Apr 2024 17:55:34 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:36 GMT | got 1000 objects from source elasticsearch (offset: 171000)
Wed, 24 Apr 2024 17:55:36 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:37 GMT | got 1000 objects from source elasticsearch (offset: 172000)
Wed, 24 Apr 2024 17:55:37 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:39 GMT | got 1000 objects from source elasticsearch (offset: 173000)
Wed, 24 Apr 2024 17:55:39 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:40 GMT | got 1000 objects from source elasticsearch (offset: 174000)
Wed, 24 Apr 2024 17:55:40 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:41 GMT | got 1000 objects from source elasticsearch (offset: 175000)
Wed, 24 Apr 2024 17:55:42 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:43 GMT | got 1000 objects from source elasticsearch (offset: 176000)
Wed, 24 Apr 2024 17:55:43 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:44 GMT | got 1000 objects from source elasticsearch (offset: 177000)
Wed, 24 Apr 2024 17:55:45 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:46 GMT | got 1000 objects from source elasticsearch (offset: 178000)
Wed, 24 Apr 2024 17:55:46 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:47 GMT | got 1000 objects from source elasticsearch (offset: 179000)
Wed, 24 Apr 2024 17:55:48 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:49 GMT | got 1000 objects from source elasticsearch (offset: 180000)
Wed, 24 Apr 2024 17:55:49 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:50 GMT | got 1000 objects from source elasticsearch (offset: 181000)
Wed, 24 Apr 2024 17:55:51 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:52 GMT | got 1000 objects from source elasticsearch (offset: 182000)
Wed, 24 Apr 2024 17:55:52 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:53 GMT | got 1000 objects from source elasticsearch (offset: 183000)
Wed, 24 Apr 2024 17:55:54 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:55 GMT | got 1000 objects from source elasticsearch (offset: 184000)
Wed, 24 Apr 2024 17:55:56 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:57 GMT | got 1000 objects from source elasticsearch (offset: 185000)
Wed, 24 Apr 2024 17:55:57 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:55:58 GMT | got 1000 objects from source elasticsearch (offset: 186000)
Wed, 24 Apr 2024 17:55:59 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:00 GMT | got 1000 objects from source elasticsearch (offset: 187000)
Wed, 24 Apr 2024 17:56:01 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:03 GMT | got 1000 objects from source elasticsearch (offset: 188000)
Wed, 24 Apr 2024 17:56:03 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:05 GMT | got 1000 objects from source elasticsearch (offset: 189000)
Wed, 24 Apr 2024 17:56:05 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:07 GMT | got 1000 objects from source elasticsearch (offset: 190000)
Wed, 24 Apr 2024 17:56:07 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:11 GMT | got 1000 objects from source elasticsearch (offset: 191000)
Wed, 24 Apr 2024 17:56:12 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:13 GMT | got 1000 objects from source elasticsearch (offset: 192000)
Wed, 24 Apr 2024 17:56:14 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:16 GMT | got 1000 objects from source elasticsearch (offset: 193000)
Wed, 24 Apr 2024 17:56:16 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:19 GMT | got 1000 objects from source elasticsearch (offset: 194000)
Wed, 24 Apr 2024 17:56:20 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:22 GMT | got 1000 objects from source elasticsearch (offset: 195000)
Wed, 24 Apr 2024 17:56:23 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:25 GMT | got 1000 objects from source elasticsearch (offset: 196000)
Wed, 24 Apr 2024 17:56:26 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:27 GMT | got 1000 objects from source elasticsearch (offset: 197000)
Wed, 24 Apr 2024 17:56:28 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:29 GMT | got 1000 objects from source elasticsearch (offset: 198000)
Wed, 24 Apr 2024 17:56:30 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:31 GMT | got 1000 objects from source elasticsearch (offset: 199000)
Wed, 24 Apr 2024 17:56:32 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:34 GMT | got 1000 objects from source elasticsearch (offset: 200000)
Wed, 24 Apr 2024 17:56:34 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:36 GMT | got 1000 objects from source elasticsearch (offset: 201000)
Wed, 24 Apr 2024 17:56:36 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:38 GMT | got 1000 objects from source elasticsearch (offset: 202000)
Wed, 24 Apr 2024 17:56:38 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:39 GMT | got 1000 objects from source elasticsearch (offset: 203000)
Wed, 24 Apr 2024 17:56:39 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:41 GMT | got 1000 objects from source elasticsearch (offset: 204000)
Wed, 24 Apr 2024 17:56:41 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:42 GMT | got 1000 objects from source elasticsearch (offset: 205000)
Wed, 24 Apr 2024 17:56:42 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:44 GMT | got 1000 objects from source elasticsearch (offset: 206000)
Wed, 24 Apr 2024 17:56:44 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:45 GMT | got 1000 objects from source elasticsearch (offset: 207000)
Wed, 24 Apr 2024 17:56:46 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:47 GMT | got 1000 objects from source elasticsearch (offset: 208000)
Wed, 24 Apr 2024 17:56:47 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:48 GMT | got 1000 objects from source elasticsearch (offset: 209000)
Wed, 24 Apr 2024 17:56:49 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:50 GMT | got 1000 objects from source elasticsearch (offset: 210000)
Wed, 24 Apr 2024 17:56:50 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:52 GMT | got 1000 objects from source elasticsearch (offset: 211000)
Wed, 24 Apr 2024 17:56:52 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:53 GMT | got 1000 objects from source elasticsearch (offset: 212000)
Wed, 24 Apr 2024 17:56:54 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:55 GMT | got 1000 objects from source elasticsearch (offset: 213000)
Wed, 24 Apr 2024 17:56:56 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:57 GMT | got 1000 objects from source elasticsearch (offset: 214000)
Wed, 24 Apr 2024 17:56:57 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:56:58 GMT | got 1000 objects from source elasticsearch (offset: 215000)
Wed, 24 Apr 2024 17:56:58 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:57:00 GMT | got 1000 objects from source elasticsearch (offset: 216000)
Wed, 24 Apr 2024 17:57:00 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:57:01 GMT | got 1000 objects from source elasticsearch (offset: 217000)
Wed, 24 Apr 2024 17:57:02 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:57:03 GMT | got 1000 objects from source elasticsearch (offset: 218000)
Wed, 24 Apr 2024 17:57:03 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:57:04 GMT | got 1000 objects from source elasticsearch (offset: 219000)
Wed, 24 Apr 2024 17:57:05 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:57:06 GMT | got 1000 objects from source elasticsearch (offset: 220000)
Wed, 24 Apr 2024 17:57:06 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:57:08 GMT | got 1000 objects from source elasticsearch (offset: 221000)
Wed, 24 Apr 2024 17:57:09 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:57:18 GMT | got 1000 objects from source elasticsearch (offset: 222000)
Wed, 24 Apr 2024 17:57:19 GMT | sent 1000 objects to destination file, wrote 1000
Wed, 24 Apr 2024 17:57:39 GMT | Error Emitted => connect ECONNREFUSED <IP_ADDRESS>:9200
Wed, 24 Apr 2024 17:57:39 GMT | Error Emitted => connect ECONNREFUSED <IP_ADDRESS>:9200
Wed, 24 Apr 2024 17:57:39 GMT | Total Writes: 0
Wed, 24 Apr 2024 17:57:39 GMT | dump ended with error (get phase) => Error: connect ECONNREFUSED <IP_ADDRESS>:9200
Same error why??? Please help us :(

1000 records shouldn't crash any es system. Check if you have sufficient memory and disk. also need more ES logs. I don't see any useful information here as to why the crash occured.

I have lot of disk space of 5TB, even reducing batch size crashing the es node :(.
I guess i will use the snapshot endpoint then

Something is crashing especially, but without the logs I can't advise you as to what the issue is


Broken images on the website?

I am seeing the first image being entirely black on https://beta.flathub.org/en-GB/apps/io.github.jacalz.rymdport but the other image seems fine. On https://flathub.org/apps/details/io.github.jacalz.rymdport the same thing happens but both image previews are black as well.

The images worked fine when I added them in January (see https://github.com/Jacalz/rymdport/blob/main/internal/assets/screenshot1.png and https://github.com/Jacalz/rymdport/blob/main/internal/assets/screenshot2.png) and the links in https://github.com/Jacalz/rymdport/blob/main/internal/assets/unix/io.github.jacalz.rymdport.appdata.xml have not changed since then. Everything looks fine on my end so I don't entirely get why they appear broken on your site.
The only thing I can think of is that the images are compressed with https://tinypng.com/ but they worked a month ago so I don't quite know if that is the reason.
I had something similar (but I think the images were white instead) a while back and opened https://github.com/Jacalz/rymdport/issues/61 but now it seems to be on desktop as well and not only on mobile.

There are similar corruptions here: https://flathub.org/apps/xyz.mx_moment.moment

Indeed. They seem even worse. I checked the network inspector in Firefox and it seems like it doesn't actually fetch the images from the links that are in the appdata but instead to some local copy on the flathub website. My guess is that something is wrong with how the images are copied to the flathub storage.

Afaik something happened and images needed to be recopied recently, I suspect, that this was introduced by that.

Rymdport seems fine on my end now but the moment app linked above still seems broken for me.

https://beta.flathub.org/apps/com.github.yucefsourani.albasheer-electronic-quran-browser might also suffer from this?

Rymdport still seems broken on mobile. Was definitely work on desktop a few days ago but it might just have been a temporary thing

I checked, when you wrote this and wasn't able to confirm, that it was fixed

This app screenshots are 404 on the CDN
https://beta.flathub.org/apps/com.gitlab.coringao.cavestory-nx

All listed here seem to be fixed now


Potential crash when opening window from bottom sheet

The app can crash when opening a window from the bottom sheet. This is always reproducible when using the Don't keep Activities developer setting on Android. Example:
import TiBottomSheet from 'ti.bottomsheet';

const window = Ti.UI.createWindow({
    backgroundColor: '#fff'
});

const btn = Ti.UI.createButton({ title: 'Show bottom sheet' });
btn.addEventListener('click', () => {
    const contentView = Ti.UI.createView({ height: 200 });
    const innerBtn = Ti.UI.createButton({ title: 'Open Sub Window' });
    innerBtn.addEventListener('click', openSubWindow);

    contentView.add(innerBtn);

    const sheet = TiBottomSheet.createDialog({
        view: contentView,
        cancelable: true,
        sheetState: TiBottomSheet.SHEET_STATE_EXPANDED,
        backgroundColor: 'red',
        canceledOnTouchOutside: true
    });
    sheet.show();
});

window.add(btn);
window.open();

function openSubWindow() {
    const window = Ti.UI.createWindow({ title: 'Sub Window' });
    window.open();
}

The error is:
[ERROR] WindowManager: android.view.WindowLeaked: Activity org.appcelerator.titanium.TiActivity has leaked window DecorView@9a4bac5[TiActivity] that was originally added here
[ERROR] WindowManager: 	at android.view.ViewRootImpl.<init>(ViewRootImpl.java:900)
[ERROR] WindowManager: 	at android.view.ViewRootImpl.<init>(ViewRootImpl.java:884)
[ERROR] WindowManager: 	at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:386)
[ERROR] WindowManager: 	at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:148)
[ERROR] WindowManager: 	at android.app.Dialog.show(Dialog.java:352) <----
[ERROR] WindowManager: 	at ti.bottomsheet.DialogProxy.show(DialogProxy.kt:99)
[ERROR] WindowManager: 	at org.appcelerator.kroll.runtime.v8.V8Object.nativeFireEvent(Native Method)
[ERROR] WindowManager: 	at org.appcelerator.kroll.runtime.v8.V8Object.fireEvent(V8Object.java:63)
[ERROR] WindowManager: 	at org.appcelerator.kroll.KrollProxy.doFireEvent(KrollProxy.java:985)
[ERROR] WindowManager: 	at org.appcelerator.kroll.KrollProxy.handleMessage(KrollProxy.java:1219)
[ERROR] WindowManager: 	at org.appcelerator.titanium.proxy.TiViewProxy.handleMessage(TiViewProxy.java:261)
[ERROR] WindowManager: 	at android.os.Handler.dispatchMessage(Handler.java:102)
[ERROR] WindowManager: 	at android.os.Looper.loopOnce(Looper.java:201)
[ERROR] WindowManager: 	at android.os.Looper.loop(Looper.java:288)
[ERROR] WindowManager: 	at android.app.ActivityThread.main(ActivityThread.java:7898)
[ERROR] WindowManager: 	at java.lang.reflect.Method.invoke(Native Method)
[ERROR] WindowManager: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
[ERROR] WindowManager: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

cc @prashantsaini1 @m1ga as we talked about it

I was checking this issue and found that since the activity, on which BSD is attached, will be destroyed by OS because of that Developer Setting, is not able to be GC.
I also tried setting a WeakReference but that didn't work too since the activity is not having any strong references at first place.
I couldn't find a way to programmatically detach the activity reference from this BSD before its activity is actually destroyed.
So as a temporary fix, I tried hiding the BSD and opened a new Ti Window in its close event and it worked properly.
import TiBottomSheet from 'ti.bottomsheet';
let sheet;

(function () {
    $.index.open();
}());

function openSubWindow() {
    const window = Ti.UI.createWindow({ title: 'Sub Window' });
    window.addEventListener('click', () => window.close() );
    window.open();
}

function createCustomView() {
    const contentView = Ti.UI.createView();
    const innerBtn = Ti.UI.createButton({ title: 'Open Sub Window', height: 200 });
    innerBtn.addEventListener('click', () => sheet.hide());
    contentView.add(innerBtn);
    return contentView;
}

function showSheet(e) {
    sheet = TiBottomSheet.createDialog({
        view: createCustomView(),
        cancelable: true,
        sheetState: TiBottomSheet.SHEET_STATE_EXPANDED,
        backgroundColor: 'red',
        canceledOnTouchOutside: true
    });

    sheet.addEventListener('close', () => {
        openSubWindow();    // it works fine since this Dialog will release its references to the activity internally
    });

    sheet.show();
}

As a permanent fix, I have been reviewing the TiUIAlertDialog code and it's also using some sort of wrapper class to manage the activity references. I will post the permanent solution once it's ready.

Unfortunately this will not be a feasible solution, as we need to retain the sheet state and want to prevent additional transitions up/down every time a new window is opened.

It's strange. Not seeing a crash on my test devices: Pixel 7 (Android 13) and Samsung A20 (Android 11). But only did a quick test run. Sounds like @prashantsaini1 already did some more debugging here and can produce it :+1: Hopefully the TiUIAlertDialog way does the trick!
Even if I attach leakCanary I only see a notification that 5 elements are still there but it goes away after a short time because they are garbage collected.
And I couldn't compile the module because of an error in https://github.com/hansemannn/titanium-bottom-sheet/blob/master/android/src/ti/bottomsheet/DialogProxy.kt#L83 :thinking: had to change it to titaniumView?.outerView?.let { nestedScrollView!!.addView(it) }

Maybe a newer Kotlin version? Thats possible!

@m1ga @hansemannn The compile error was because of null safe check on outerview, so that's absolutely fine at your end.
I also found that the app was not crashing, but I was only getting the Window leakage error on console.
I'm still doing some more tests on TiUIAlertDialog as it seems to be working fine, only that it doesn't show up when the new window is opened because of its actual parent window is destroyed under this setting and all the attached dialogs are destroyed too.
@m1ga if you get some time today, can you check whether it's leaking window even after passing the App Root Activity or Application Context, rather than current activity context in BottomSheetDialog() here?
I'll try the same tomorrow before moving to AlertDialog way.

not even seeing it in the logs:
https://user-images.githubusercontent.com/4334997/207930110-f22d1680-d54f-4d9a-a358-31e0b63bfe9c.mp4

Module 1.0.0 (that one from the sample folder) and just tested 1.1.0 (from release)
Ti 11.1.1, 12.0.0.RC
Pixel 7
Android 13
Background limit: none

Do you have Don't keep Activities enabled?

my bad! I've changed the setting below that :man_facepalming:
Will test it tomorrow again

Now I see it too :smile:
@prashantsaini1 the Alertdialog part is interesting. There are even some notes about memory leaks:
https://github.com/tidev/titanium_mobile/blob/f80e1dc35b7e1d8795fd096db2b350fddc94e88c/android/modules/ui/src/java/ti/modules/titanium/ui/widget/TiUIDialog.java#L354-L369
just added two buttons to test both ways:
import TiBottomSheet from 'ti.bottomsheet';

const window = Ti.UI.createWindow();

const btn = Ti.UI.createButton({title: 'Show dialog'});
btn.addEventListener('click', () => {
	const contentView = Ti.UI.createView({ height: 200 });
	const innerBtn = Ti.UI.createButton({ title: 'Open Sub Window' });
	innerBtn.addEventListener('click', openSubWindow);

	contentView.add(innerBtn);

	var dialog = Ti.UI.createAlertDialog({
		androidView: contentView
	});
	dialog.show();
});

const btn2 = Ti.UI.createButton({ bottom: 10, title: 'Show bottom sheet'});
btn2.addEventListener('click', () => {
  const contentView = Ti.UI.createView({ height: 200 });
    const innerBtn = Ti.UI.createButton({ title: 'Open Sub Window' });
    innerBtn.addEventListener('click', openSubWindow);

    contentView.add(innerBtn);

    const sheet = TiBottomSheet.createDialog({
        view: contentView,
        cancelable: true,
        sheetState: TiBottomSheet.SHEET_STATE_EXPANDED,
        backgroundColor: 'red',
        canceledOnTouchOutside: true
    });
    sheet.show();
});

window.add([btn, btn2]);
window.open();

function openSubWindow() {
	const window = Ti.UI.createWindow({title: 'Sub Window'});
	window.open();
}

can you check whether it's leaking window even after passing the App Root Activity or Application Context, rather than current activity context in BottomSheetDialog() here

I've tried:
TiApplication.getAppCurrentActivity()
TiApplication.getAppRootOrCurrentActivity()
TiApplication.getInstance().currentActivity

but no difference.
https://stackoverflow.com/a/65593461/5193915 same in native land.
Tried to override onDestroy and clean up some parts in there but its not called .

@m1ga I tried the application context as well but same leakage.
Looks like the AlertDialog is the only way, though I've made the changes in the new AlertDialog based class for BSD, but it'll take upto next week as I'm off on this weekend.
@hansemannn fyi

To be clear here: I am not concerned about the minor leak, it's more that the dialog cannot retain it's state and closes itself / crashes sometimes.

@hansemannn not sure if state can be maintained internally as it's not even happening with the AlertDialog.

It is retained when "Don't keep activities" is disabled (normal use case). We're doing that in dozens of cases with success. It's just not able to create the state in this module. In our other bottom sheet module that's used for the waypoints map, it's working great. Maybe we should fix this internally @janvennemann


Split port config for PPTP and IKEv2

Steps for configuring the Maximum Ports for WAN Miniport (PPTP) and WAN Miniport (IKEv2) look like they got combined by mistake.  Split these into separate steps and sub-steps.

Thanks! @shortpatti - can you take a look at the proposed split out? Thanks!

@NeighborGeek, thank you for catching!


Add max-height to modal to enable scrolling elements

PR Type
enhancement

Description

Enhanced the modal component by adding a maxHeight of 75% to allow for scrolling within the modal when content exceeds this height.
Added overflow: "hidden" to prevent content overflow issues.
Improved the layout handling by setting flex: 1 on the children view to ensure it expands properly within the modal.

Changes walkthrough 📝
Relevant filesEnhancement

Modal.tsxEnhance modal with max-height and improved layout

packages/ui/src/Modal.tsx
Added overflow: "hidden" and maxHeight: "75%" to the modal style.  Modified the children view to have flex: 1 for better layout handling.

+3/-1

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

Closing since this change is not needed.


Not working properly inside ScrollView

Hi I am using ExpandableTextView inside ScrollView. It is not behaving as it should. Please take a look

Manabu, first of all: Thank you for writing this code ^_^
I was experiencing the same issue (in a ScrollView also) but then I tried to put the code in a simple activity with a LinearLayout and the same happens.
Then I checked the compile version and mine is 19 with buildTools 19, meanwhile this library is compiled against 21 (and you need JDK 7 for that task) so I guess the problem is around there ;)

Ritesh,
I tried  to update the code and nothing
Fiinally I discovered I was setting the TextView with setText("blablabla").
Instead, the ExpandableTextView should be the one set.

@ritesh24 Thank you for using my library. Is this issue still not resolved? Based on DrDuke's comment, I am wondering I should still look into this one. If the issue is still occurring, please share the entire layout xml file you are using for ExapandableTextView.

I keep running into this issue, where I inadvertently set text to the inner textview instead of the overall expand_text_view. The README.md should include this caveat. :)

The README.md should include this caveat. :)
-> Thank you for your feedback. I just updated the README to point that out.


[IO-414] don't write a BOM on every (or any) line

Per JDK docs, "When decoding, the UTF-16 charset interprets the byte-order mark at the beginning of the input stream to indicate the byte-order of the stream but defaults to big-endian if there is no byte-order mark; when encoding, it uses big-endian byte order and writes a big-endian byte-order mark."

Codecov Report

Merging #492 (adb2f49) into master (877b9e3) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #492      +/-   ##
============================================
- Coverage     84.97%   84.96%   -0.01%
  Complexity     3372     3372
============================================
  Files           227      227
  Lines          8080     8082       +2
  Branches        953      954       +1
============================================
+ Hits           6866     6867       +1
  Misses          960      960
- Partials        254      255       +1

Files
Coverage Δ

src/main/java/org/apache/commons/io/IOUtils.java
86.81% <100.00%> (+0.04%)
:arrow_up:

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


Update complementary projects to support v4

Initial list only includes projects which we depend on in our docs. Might be a good idea to include other high-profile projects.
projects

[x] material-ui-popup-state #15691
Seems like no changes are necessary
[x] @material-ui/pickers
Some minor improvements to reduce number of transitive dependencies are possible (react-transition-group)
[x] material-table Tracking in mbrn/material-table#255, PR
[x] notistack  iamhosseindhv/notistack#119 PR
Some minor improvements to reduce number of transitive dependencies are possible (clsx)

Closed with #16124


Investigate full project build time

These times will vary depending on a users internet connection:
My current setup consists of 500/100 down/up connection.
This is using just make install
Time to full build with full download of node dependencies is ~3m 41s.
Subsequent incremental builds without download of node dependencies is ~2m 17s.
I think the build times have gotten down to a reasonable length.


Feedback for Documentation/Guide

Coming from CAD, I am used to being able to "instance" an object, then modify the source and have all of the instances update.  In plasticity, it appears that I can duplicate an object, but then to modify the original and all of the duplicates, I have to manually select them all each time.
This can be very tedious if, for example, I have hundreds of duplicates of a given object.
Perhaps the intention is for me to use a group for this?
Anyhoo, I would love to see a page in the documentation about how to do common operations like this - perhaps something under the "CAD Essentials" section that talks about "How Plasticity is different" or "Achieving CAD-like results in Plasticity".
I searched YouTube and read the existing documentation, but I couldn't find anything explaining this difference.  Right now, this is a major hurdle for me in adopting Plasticity, and i imagine it's an issue for others as well.

Thank you for your feedback regarding object instancing and documentation in Plasticity. We acknowledge the convenience of the "instance" feature in CAD and understand the challenge with the current workflow in Plasticity.
We are exploring ways to improve this, and your suggestion regarding enhanced documentation is noted. In the meantime, we invite you to join our Discord community for further discussion and support. If you are a trial user, you can access the Discord community via the following link: https://discord.gg/jeDd2hVK  If you are an Indie or Studio license user, the link to the Discord community has been provided in the email sent to you upon purchase.
Thank you for bringing this to our attention.


Show travis env for debugging

Whoops. This was intended as a test for #979, though I had meant to open it on my fork.


guide to implement a Sql implementation for InstacneStore

I'm interested into implementing a SqlInstanceStore and pull it here if this repo is right place for it.
just before going into code i wanted to know if there is any guide to help me.
What i want to do is to implement something like PurchaseProcess example of the WF which is implemented the instance store using XML serialization,  then i will save the XML to  a sql table.
Is this a proper implementation?

We are not interested at this time.

At this time we have no plans for an instance store.

@yekanchi I'm sure there are other people interested in having a database instance store provider. Instance store implementations should be in their own repos since there's a well-known interface. I'd suggest following these instructions on how to create a custom instance store.
Regarding XML serialization, I would suggest not going this route. The serializer for WF in the .NET Framework is the NetDataContractSerializer. NDCS writes type information so that when it's deserialized, the correct assemblies and types can be loaded. DataContractSerializer and XmlSerializer don't do this and NDCS was not ported to .NET Core/Standard. We use the JsonSerializer in our JsonFileInstanceStore example because it has an option to write type info.
A couple other suggestions:

Use Entity Framework so you're not limited to just SQL Server. Also it can automatically create and migrate the database without explicitly running a SQL file, like was done with the .NET Framework.
Create a shim for CoreWF to call into the original SqlWorkflowInstanceStore. Since the serialization will have to be different and people are likely to have already persisted instances in a database, the only way to migrate is to load the instances into memory with the original InstanceStore and then persist again with the new one.


Added String Tensor support to the Strings Module

Added support for tensors of strings to the strings module. It only includes two basic ops (print and to_string) however this should be sufficient for testing the internal data format, accessors, and constructors.

Can you add some tests to the curriculum that stimulate this before adding it? It's really hard to evaluate this without seeing what is driving it.


Refactor fromMem.

Fixes #479.

I don't think anyone is going to care about this, so just landing it.

I don't think anyone is going to care about this, so just landing it.

Was it intentional to drop support for Node.js 18, since from-mem requires Node.js 20?

No.  See #495


Cannot update dataset when using Service Principal

I am attempting to use DevOps to deploy report updates and then set the dataset to a different server (and database). We are using service principals since this is a Power BI embedded scenario.
The steps I have set up are:

Publish
Take Ownership
Update datasource (for entire workspace)

The first two tasks succeed, and I am able to confirm that the service principal has ownership of the dataset by looking at the dataset on the powerbi website. Unfortunately, the change dataset fails with the message, "This operation is only supported for the dataset owner".
Not sure where to go next or how to resolve this.
Thanks.
(I just re-ran the test with Update Dataset for only the specific data set I am testing and got the same error.)

Could you add the system.debug variable with the value true and run the flow again and send the log files?

Agent job.zip
There are several reports in the release; I am only testing with the first report, "340B Performance Report" (if that works, I will add the others in).
Let me know if you need any additional information.
Thanks.

@RobertAltman-CPS: Thing I see in the logs is that you are targetting different workspaces. Please check the configuration of your tasts

That resolved my first stumbling block; now I am back to my original problem when trying to update the datasource. The error I am getting is "Dataset doesn't contain a datasource that matches selector #1" and I am guessing that it has to do with the server or database parameters, but they appear correct and I am not sure how else to validate that. I am attaching a log from my latest test run.
ReleaseLogs_539.zip

@RobertAltman-CPS: The script tries to find a existing configuration with that setting. Occording to the error it is not able to find that parameter with the old server.
What you could try is getting the value via the PowerBI Api to be absolutly sure you have the correct values.


Examples of how to use

Hey,
Is there anyway you can provide a simple working sample of this? I am struggling to piece together all the parts.
Thanks

I'm struggling with this as well.  I understand that the client contacts the authorization server (running laravel and your package).  Some magic happens there, and it send back the Authorization Grant to the client, which then uses that to request an access token for further requests to protected resources.
I've added the routes and I've added the authorization-form view.  I think what I have to do is set things up so that the client makes a call to http://myurl.com/oauth/authorize with client id, client secret and redirect url as query params.  If they are not currently authorized with my application, they should get redirected to the login form.  After they authorize, I should then redirect back to oauth/authorize with the params and the magic then happens if they authorize it.
Do I have that right?


Minimum utxo value should not influence inputs

Context

We have #1916 dealing with outputs in the context of minimum value utxo. Also in #1894 we make dust determined by it.
The min value rule in the ledger is simple: new outputs must be bigger than the minimum.
The min value can be changed, and this can lead to existing UTxOs being below the current minimum for new outputs. Those existing UTxOs are still spendable.
Decision

Revert the dependence of input dusting on minmium UTxO value
Acceptance Criteria

Development

QA

Do I understand correctly that this change will be discarded? @paweljakubas, @KtorZ

This issue is to be discarded indeed. The dust threshold has no influence on the inputs but operate on the change outputs.

Closing.


cargo test --all crashes macOS High Sierra

This occurred at commit 8bbbb4322e on macOS 10.13.4 with rust 1.24.0.
Also happens with rust 1.25.0.
This is reminiscent of https://github.com/cloudfoundry/jvmkill/issues/11.

I experimented with setrlimit(RLIMIT_NPROC, n) for various values of n. I couldn't find a value which made the tests pass but prevented macOS from crashing.

The macOS CI is running Sierra, so this behaviour seems to have been introduced by High Sierra.

Later versions of rust on High Sierra seem to have solved this.


.NET Core 3.1 end-of-life

I'm not super familiar with all the features of the Functions extension, but with .NET Core 3.1's end-of-life being yesterday, we should remove any facilities for creating new projects like this (which #3472 does some of), and we can also remove any code that is in place specifically to support 3.1 and/or below. In addition, branding changes should be made since, after .NET Core 3.1, all versions are just called ".NET".
There may or may not be changes to still make after #3472, someone more familiar with the extension will have to look :smile:

ASP.NET is still called "ASP.NET Core".


Search function does not explain that no results were found.

Steps to recreate:

Search for something that returns no results, e.g. supercalifragilisticexpialidocious

Expected results:
I see some text to the effect that no results were found for the search term.
Actual results:
No information is displayed about the search results.

I'm pretty sure the search function used to say something like "no results found". When I searched earlier for a name to check if a bench was submitted already and got what's shown in the image above I initially thought the search was broken.

Good spot! Thanks.


Create package Scheduling

This package is to be created in Utils. It will contain all the stuff related to platforms schedulers. A first implementation will be provided for Windows.

Completed, tested.


Ranked - choice system

In a ranked-choice system, voters can vote for more than one candidate. Instead of just voting for their top choice, they can rank the candidates in order of preference.
Use : ./runoff   ...
Command - line argument

Put these two files in a folder and then make a PR again


CacheSynchronisation error

Running microsoft/bcsandbox:nl in Docker gives me this warning/error. Tried deleting all containers/images and redownload them already. Same happend with :latest version. I'm using Windows 10. Any ideas what causes this and how to solve?

Just ignore it - it is just stating that it initializes the cache (which of course shouldnt give an error)


ACL operations in fs.c

Hi,
I want to add ACL operations (set and get) into fs.c.
There is interest with the neovim project for these functions, so I'm wondering if there is interest here as well before I start working on them.

Can you sketch up an API proposal?

I just drafted this up; this is my first API proposal, so I'd be happy to clarify anything I'm missing.
Overview:
This API would allow for thread safe ACL file operations.
Implementation:
I would include these functions in fs.c.  I'd  work with the fs API (uv_fs_t, INIT, PATH,  POST, etc.) as I believe they would be useful for implementing the ACL functions.  I'd first implement the acl_get_* and acl_set_* functions before attempting the rest of them as I believe they would be the most useful.
Use-cases:
These functions would be useful for anyone wanting to use thread safe ACL functions.  I haven't been able to find any implementations yet.
Comments:
I'm open to any comments/suggestions as I am new to libuv and have just been messing around with the code for the past few days.

I think this is the related to or the same as https://github.com/libuv/libuv/issues/234?

Oh, looks like it indeed. @Adam-K-P mind dropping by #234?

Yes, I will start looking at it today, thanks for finding that.

Closing in favor of @234 then.


[docs]: Suggestions for skipLast documentation improvements

Documentation Related To Component:
The skipLast operator:
skipLast.ts
Please check those that apply

[ ] typo
[X] documentation doesn't exist
[ ] documentation needs clarification
[ ] error(s)/adoption/updates in example
[ ] needs example

Description Of The Issue
The detailed description is missing. Also, the see also links are missing.
We might want to improve this to serve a better more detailed description for the community.
Description
The detailed description can be improved. Here we should include that:

it will always complete if the source completes
it errors if source raises an error

See Also
We miss the see also section completely.
A suggested list for related operators could look like this:
 * @see {@link last}
 * @see {@link skip}
 * @see {@link skipWhile}
 * @see {@link skipUntil}

In case we also want to reference take operators (which is partially the case here) we also might want to include the following operators:
 * @see {@link first}
 * @see {@link take}
 * @see {@link takeWhile}
 * @see {@link takeUntil}
 * @see {@link takeLast}

Sry, overlooked #4631 and #4696

@BioPhoton, I think documentation is already updated for this one 🤔 https://rxjs.dev/api/operators/skipLast


Marvel API

🎯 Title and Issue Number
Closes #340
I have added project using marvel api
There are cards thattake name of character from user as input and fetch the data from the api and display information of that character along with image

🗒 Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x]  I have gone through rules of when PR will get merged.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have followed proper file structure.
[x] I have gone through CONTRIBUTING GUIDELINES.md.

Thank you for contributing!❤
Don't forget to show some love by ⭐ the repository!

Hey @komal-agarwal5, Thank you for creating PR! We will review it super soon. 😇❣
As we continue to evolve and innovate, we encourage you to share your ideas, feedback, and code to help us push the boundaries of what's possible in the world of APIs🚀.
We hope you have followed CONTRIBUTING GUIDELINES.
Thank you for being an essential part of our community. Together, we'll keep building amazing things!
Don’t forget to ⭐ our repository!
Happy Coding!✨
Will See you soon❣


About NMS

I found that when training, use torchvision.ops.batched_nms. But when demo, use torchvision.ops.nms.
The former is NMS for each category, The latter is to do NMS with all detection frames.
Shouldn't each detection box be NMS separately?

Using batchnms or nms is only related to arg named class_agnostic. Batched nms is used to provide higher recall value while nms could make your demo looks well.


Batch encoding with negative controls

in the encoder mode, current implementation assumes input tensor has the same dimension as the batch covariate, whereas one can think of cases where batch encodings have to be learned from all samples/cells e.g. when data contains negative controls

testing completed


gltfpack: Implement support for KHR_texture_basisu inputs

When the input file has KHR_texture_basisu extension, we now will
preserve the images along with the extension in the output file instead
of discarding it.
When -tc is specified, images like this will not be recompressed; accordingly,
some flags like -tl and -tp will not work with pre-compressed inputs.
When the input textures specify both uncompressed and compressed image,
the behavior is likely to be suboptimal...
Fixes #537.

TBD:

[ ] Automatically fix assets like AnisotropyBarnLamp: https://github.com/KhronosGroup/glTF-Sample-Assets/issues/117
[ ] Better behavior when -tc isn't used and the input file has both uncompressed and compressed textures (when -tc is used we can't really do anything meaningful...)


temporary hotfix for PlatformException

PlatformException thrown when isValidPhoneNumber is passed a 0 or 1 character phoneNumber parameter.
I don't know enough about the platform system to trace this issue further than here. This temporary fix stops PlatformException from being thrown for now.

@natintosh any idea until when this fix will be live?

It's already live with 0.7.0+2


Support for darwin_arm64

Hello, the currently published provider version 0.1.7 has no darwin_arm64 package.
I get this error message:
│ Error: Incompatible provider version
│
│ Provider registry.terraform.io/namecheap-ecosystem/namecheap v0.1.7 does not have a package available for your current
│ platform, darwin_arm64.
│
│ Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other
│ versions of this provider may have different platforms supported.

This is the provider to use https://registry.terraform.io/providers/namecheap/namecheap/


Provide a way to run service code out of I/O event loops

When service devs are not very familiar with asynchronous programming, it is very easy to drive Armeria's core event loops into havoc by blocking them.
Framework devs may want to make sure Armeria at least handle I/O and function normally for a certain set of core services, such as PrometheusExpositionService or HealthCheckService, by isolating other non-core services from the I/O event loops.
To achieve this, I'd like to propose adding the per-service/virtual host/server serviceWorkerGroup property that makes a service use a different EventLoopGroup than ServerBuilder.workerGroup, e.g.
Server
  .builder()
  .workerGroup(ioEventLoopGroup, /* shutdownOnStop */ true)
  .serviceWorkerGroup(isolatedEventLoopGroup, /* shutdownOnStop */ true)
  .route()
    .path("/core-services/metrics")
    .serviceWorkerGroup(ioEventLoopGroup, /* shutdownOnStop */ true) // Use the core event loops.
    .build(new PrometheusExpositionService())
  .route()
    .path("/non-core-services/foo")
    .build(new FooService()) // Will use `isolatedEventLoopGroup`
  .build()

Action items:

Add the serviceWorkerGroup() builder methods to ServerBuilder and AbstractServiceBindingBuilder so a user can specify the service worker groups as shown in the above example.

Check this commit to get an idea on what this change will look like.

Change how Armeria assigns an event loop to a ServiceRequestContext.

Currently, it always uses the same event loop with the current connection.
Modify the constructor of DefaultServiceRequestContext so it accepts an EventLoop.
Modify HttpServerHandler.handleRequest(), so it specifies an event loop from the serviceWorkerGroup:ServiceConfig serviceCfg = ...;
EventLoop eventLoop = serviceCfg.serviceWorkerGroup().next()
reqCtx = new DefaultServiceRequestContext(..., eventLoop, ...);

Let me try this 😉

We had some discussion about this issue and decided the following:

We allow specifying a ScheduledExecutorService and/or some type we'll define in the future (which can wrap an existing ScheduledExecutorService for sure), instead of letting a user specify an event loop group for a service.
We deprecate RequestContext.eventLoop() in favor of a new method RequestContext.executor().
We may want to deprecate BlockingTaskExecutor in favor of the service-level executor, but we'll still looking for ways to streamline this.

/cc @vkostyukov @yzfeng2020 ^


[SUPPORT] DFS Schema Provider not working with S3EventsHoodieIncrSource

Describe the problem you faced
I am running a delta streamer job to ingest JSON files from S3 using the S3EventsHoodieIncrSource. In this use case, I need to enforce the schema in the source files because there may or may not be some fields depending on certain occasions. According to the docs, I can do this using the hoodie.deltastreamer.schemaprovider.source.schema.file parameter, but it doesn't seem to be working.
Although the documentation states that "For sources that return Dataset, the schema is obtained implicitly. However, this CLI option allows overriding the schema provider returned by Source", this does not seem to apply to the specific source being referred to. Upon examining this piece of code, it appears that the informed schema is not being explicitly set.
    String fileFormat = props.getString(SOURCE_FILE_FORMAT, DEFAULT_SOURCE_FILE_FORMAT);
    Option<Dataset<Row>> dataset = Option.empty();
    if (!cloudFiles.isEmpty()) {
      dataset = Option.of(sparkSession.read().format(fileFormat).load(cloudFiles.toArray(new String[0])));
    }
    return Pair.of(dataset, instantEndpts.getRight());

If I inform a source schema using the parameter hoodie.deltastreamer.schemaprovider.source.schema.file, I expect that the schema will be enforced over all the files read in the job. Is it appropriate to consider this a bug? Should I fill a bug ticket on Jira?
P.S: If my assumptions and analysis are right, I'd have interest in submitting a fix for this, since this issue is affecting my workloads 😄
Environment Description
This is happening in all hudi versions that I tested >= 0.9, I have jobs running with 0.9 and 0.11 on EMR.

The incremental source infers schema by simply loading the dataset from the source table. What you're proposing is a good enhancement. Would you like to take it up? HUDI-5997

@codope yes, I would, but I would need some guidance tough. Do you think that's possible?

Makes sense. Have updated the ticket.


Google Cloud Storage requests during query execution being performed in series

Describe the bug
I'm experimenting with datafusion 38 (using as a library, not the cli) to query against parquet files in Google Cloud Storage. For now I'm doing a basic test, just select distinct(some_column) from my_table.
I wrapped the ObjectStore and TableProvider traits to add tracing to their execution, and this is what I see:

I'd like to improve the query performance to be much faster than my current 30s, and I think one dial in my control is to resize the parquet files so that there are fewer requests.
Another observation is that the requests to Google Cloud Storage during query execution appear to be done in series. The table scan, on the other hand, is being successfully done in parallel so takes a lot less time even though the total requests are a similar scale and duration per request.
This serial pattern on the requests seems like a performance bug to me.
To Reproduce
select distinct(some_column) from my_table, where the table provider is parquet in Google Cloud Storage.
Expected behavior
I would hope we can parallelise the requests to Google Cloud Storage! Best case is I'm told it's user error and there's a simple fix, otherwise if it's work needed in datafusion perhaps I can contribute a fix.
Additional context
No response

Thanks @davidhewitt, one extra note - if it would help anyone looking into this to see the Logfire live view of the trace, as well as the screenshot, happy to send some data to temporary project and share it with them.

Ok great, so this is happily user error!
After digging around with the query plans and understanding that each file group is loaded sequentially by design, I found ListingOptions::with_target_partitions, and after setting that suitably, problem solved! 🚀


Add platform helpers

For pretty much the reason that OBS gives itself ("These functions/structures/types are used to perform actions that typically don’t have shared functions across different operating systems and platforms.") it would be good to have the platform helper functions available, for example os_gettime_ns() to be able to create the same timestamps that OBS is using itself.
This should be the right header file.

Added the APIs, but found that some of them are not really compatible with how .NET does cross-platform. Some APIs write information (or return) to struct pointers that have different layouts in different platforms.
In C, this is handled by #define - it works since it is compiled to each platform separately.
So I recommend to use .NET APIs whenever possible (and added a notice to do that to ObsPlatform class).
The new APIs are in <IP_ADDRESS>-alpha

Ah, you're right, good find, still thanks a lot for implementing it!


export BinarySpacePartition type

Description
I've exported the BinarySpacePartition type as it's really hard to write type signatures without it!
I haven't updated the CHANGES.md file as it's non-obvious where to put changes for unreleased code. But I'm happy to amend them if needed.
Checklist

[x] I've read CONTRIBUTING.md

[ ] I tested my changes with xmonad-testing

[ ] I updated the CHANGES.md file

This seems good to me :+1

Makes sense, thanks!


Allow usage of config file

Hi folks,
I really like your project.
Unfortunately I cannot use it in production because I use a config file on my host before using docker-compose up.
It looks like this.
  environment:
    HTML_ROOT: ${HTML_ROOT}

    SITE_TITLE: ${SITE_TITLE}
    ADMIN_USER: ${ADMIN_USER}
    ADMIN_PW: ${ADMIN_PW}
    ADMIN_EMAIL: ${ADMIN_EMAIL}

My Startup Script looks like this
source config.cf
docker-compose up

The advantage is, that I only have to use one config file for everything instead of hardcoding the environment variables inside the docker-compose.yml.
Also my 2. Question. Is it possible to use a custom docker-compose.yml? So I could make a docker-production.yml and so on.
Best Regards
Michael

Hi

I'm not sure if it can help you, but I've been using the extends keyword to do that, e.g.

conf.yml

env:
  environment:
  - FOO=quux

docker-compose.yml
hello:
  extends:
    file: conf.yml
    service: env
  build: app
  command : #do something with $FOO

it's not (yet) possible since the application is relying on the docker compose SUPPORTED_FILENAMES

thank you
Francesco

Hi Francesco,
Thank you so much for your answer!
The trick with extends did it! (y)
Am 28.02.16 um 22:04 schrieb Francesco Uliana:

Hi

I'm not sure if it can help you, but I've been using the extends
https://docs.docker.com/compose/extends/#extending-services
keyword to do that, e.g.

conf.yml
env:
environment:

FOO=quux

docker-compose.yml
hello:
extends:
file: conf.yml
service: env
build: app
command : #do something with $FOO

it's not (yet) possible since the application is relying on the
docker compose SUPPORTED_FILENAMES
https://github.com/docker/compose/blob/42f4d814d7dd6ad4799ad71ddc738ada954143f6/compose/config/config.py#L103

thank you
Francesco
—
Reply to this email directly or view it on GitHub
https://github.com/francescou/docker-compose-ui/issues/19#issuecomment-189946140.


New package: AHS.TsurumakiMakiJPN version 1.1.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Exception during executable launch operation System.AggregateException: One or more errors occurred. (An error occurred trying to start process 'C:\Windows\Installer{1818DCB9-0371-4E7D-9F71-35121608027A}_853F67D554F05449430E7E.exe' with working directory 'D:\TOOLS'. The specified executable is not a valid application for this OS platform.)  ---> System.ComponentModel.Win32Exception (216): An error occurred trying to start process 'C:\Windows\Installer{1818DCB9-0371-4E7D-9F71-35121608027A}_853F67D554F05449430E7E.exe' with working directory 'D:\TOOLS'. The specified executable is not a valid application for this OS platform.    --- End of inner exception stack trace ---    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)

@wingetbot waivers Add Validation-Executable-Error


[Event Request] Codeunit 6224 - OnBeforeNewChild

The functionality of the SII for Spain is not fully developed for all communities. Adjustments to 'Fixed texts' are necessary for nodes that cannot be adapted in any other way. With the proposed event it could be adapted for all cases.
CODEUNIT 6224 XML DOM Management
AddElementWithPrefix()
 OnBeforeNewChild(var NodeName);
NewChildNode := XMLNode.OwnerDocument.CreateElement(Prefix,NodeName,NameSpace);

Sorry I closed without wanting the request. PLEASE TREAT AS OPEN.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


'No match for group package' shows up in the logs when building a new image

Fedora 32 host, newly installed osbuild-composer, the journal output contains these errors. They don't cause the build to fail though:
May 22 13:28:42 localhost.localdomain osbuild-composer[13339]: No match for group package "lsvpd"
May 22 13:28:42 localhost.localdomain osbuild-composer[13339]: No match for group package "powerpc-utils"
May 22 13:28:42 localhost.localdomain osbuild-composer[13339]: No match for group package "plymouth"
May 22 13:28:42 localhost.localdomain osbuild-composer[13339]: No match for group package "dracut-config-rescue"
May 22 13:28:42 localhost.localdomain osbuild-composer[13339]: No match for group package "firewalld"

@teg thinks these are coming from dnf-json

osbuild-composer installs the @core comps group, which mentions packages that do not exist, likelsvpd and powerpc-utils.
plymouth, dracut-config-rescue, and firewalld do exist, at least in the x86_64 repos. I don't know why we're seeing warnings there. Which image type are you trying to build, on which architecture?

Warnings like this can be seen on all architectures. Only the missing groups are different, e.g. on PowerPC powerpc-utils are present, whereas on x86_64 they are not. I don't think this is a problem for us to solve. If we wanted to do something about it, I'd suggest to look at the definition or @core or the way dnf handles these groups and if it is possible to have them conditional based on architecture.


Subflows and integrate them into other flows

Would be nice to have "subflows" wich can be written without an appId or launchApp command and they can be called from other flows.
Our use case: When we want to test our checkout flow the user needs to enter the billing details (name, phone number etc.) after this the user can select a payment method. Of course, we want to test the checkout flow with different payment methods but currently, we need to do a lot of copy and paste because of the billing details screen which is error-prone and annoying ;)

This is currently supported via a concept of initFlow (docs).

Can an initFlow call an flow which also has an initFlow inside?

After looking into it a bit more, perhaps initFlow is not exactly what you have in mind here. We will think on how to add some sort of an import command

This is now solved by runFlow command released as part of 1.8.0


Clear Package Folder Before Generation

Fix: https://github.com/Azure/azure-sdk-tools/issues/8057
Test pipeline: https://github.com/test-repo-billy/azure-rest-api-specs/pull/3473

Left small comments!
Regarding the customization code I remember Ray has mentioned we could improve our automation to have message like The SDK has customized SDK code and might not be compatible with the new specs, the service team may need to update the customized code or the new specs. Not sure this is feasible and we have plan for this.

The current customized code is mixed in generated code, we don't know if customer has customized code. I think it's better to seperate generated code and customized code in the future.