Question on ffq [DOIS]

Greetings ffq developers,
Could anyone help explain a bit why my first attempt to fetch the accession information from one paper (https://doi.org/10.1016/j.cell.2023.01.034) fails, while my second attempt for another paper (https://doi.org/10.1093/nar/gkac908) is successful? The commands and corresponding outputs for 2 studies are shared here. In either situation, ffq 0.3.0 and Python 3.11.1 are used.
In each attempt, the similar warning messages pop up in my terminal: "WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...". For the first study, there is no output file in json format. However, for the second study, even I meet this sort of warning message of SRX8785942, the output file nar.json contains the information of SRX8785942, as you see below.
[2023-08-19 16:10:13,676]    INFO Parsing Experiment SRX8785942
[2023-08-19 16:10:13,681] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:14,088] WARNING There are 0 runs for SRX8785942

"                        "experiments": {
"SRX8785942": {
"accession": "SRX8785942",
"title": "Illumina NovaSeq 6000 paired end sequencing; GSM4681765: Breast cancer cells - MCF7 CL; Homo sapiens; RNA-Seq",
"platform": "ILLUMINA",
"instrument": "Illumina NovaSeq 6000",
"runs": {}
}"

Look forward to learning from your insights. I really appreciate your help in advance.
ffq -o ./json_file/cell.json 10.1016/j.cell.2023.01.034 --verbose
Output:
[2023-08-19 15:40:47,871]   DEBUG Printing verbose output
[2023-08-19 15:40:47,871]   DEBUG Namespace(IDs=['10.1016/j.cell.2023.01.034'], o=None, t=None, l=None, ftp=False, aws=False, gcp=False, ncbi=False, split=False, verbose=True)
[2023-08-19 15:40:47,871] WARNING Searching by DOI may result in missing information.
[2023-08-19 15:40:47,871]    INFO Searching for DOI '10.1016/J.CELL.2023.01.034'
[2023-08-19 15:40:47,978]    INFO Searching for Study SRP with title 'Cell lineage-specific mitochondrial resilience during mammalian organogenesis'
[2023-08-19 15:40:48,510]    INFO Found 2 studies that match this title: SRP370066, SRP400925
[2023-08-19 15:40:48,511]    INFO Parsing Study SRP370066
[2023-08-19 15:40:48,936]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:48,937]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:48,939]    INFO Getting Sample for SRP370066
[2023-08-19 15:40:53,327] WARNING There are 5 samples for SRP370066
[2023-08-19 15:40:53,327]    INFO Parsing sample SRS12598636
[2023-08-19 15:40:53,741]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:53,742]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:53,745] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:40:54,462]    INFO Getting Experiment for SRS12598636
[2023-08-19 15:40:54,462]    INFO Parsing Experiment SRX14843696
[2023-08-19 15:40:54,882]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:54,883]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:54,886] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:40:55,573] WARNING There is 1 run for SRX14843696
[2023-08-19 15:40:55,574]    INFO Parsing run SRR18743675
[2023-08-19 15:40:55,999]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:55,999]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:57,846]    INFO Parsing sample SRS12598635
[2023-08-19 15:40:58,260]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:58,260]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:58,263] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:40:58,670]    INFO Getting Experiment for SRS12598635
[2023-08-19 15:40:58,670]    INFO Parsing Experiment SRX14843695
[2023-08-19 15:40:59,088]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:59,089]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:59,093] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:40:59,501] WARNING There is 1 run for SRX14843695
[2023-08-19 15:40:59,501]    INFO Parsing run SRR18743676
[2023-08-19 15:40:59,903]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:40:59,903]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:02,002]    INFO Parsing sample SRS12598634
[2023-08-19 15:41:02,413]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:02,413]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:02,416] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:02,952]    INFO Getting Experiment for SRS12598634
[2023-08-19 15:41:02,952]    INFO Parsing Experiment SRX14843694
[2023-08-19 15:41:03,361]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:03,362]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:03,365] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:03,780] WARNING There is 1 run for SRX14843694
[2023-08-19 15:41:03,780]    INFO Parsing run SRR18743677
[2023-08-19 15:41:04,187]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:04,187]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:07,105]    INFO Parsing sample SRS12598633
[2023-08-19 15:41:07,512]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:07,512]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:07,515] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:07,921]    INFO Getting Experiment for SRS12598633
[2023-08-19 15:41:07,921]    INFO Parsing Experiment SRX14843693
[2023-08-19 15:41:08,331]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:08,332]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:08,336] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:08,744] WARNING There is 1 run for SRX14843693
[2023-08-19 15:41:08,745]    INFO Parsing run SRR18743678
[2023-08-19 15:41:09,147]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:09,147]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:11,117]    INFO Parsing sample SRS12598637
[2023-08-19 15:41:11,532]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:11,532]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:11,535] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:12,129]    INFO Getting Experiment for SRS12598637
[2023-08-19 15:41:12,129]    INFO Parsing Experiment SRX14843697
[2023-08-19 15:41:12,544]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:12,545]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:12,548] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:12,956] WARNING There is 1 run for SRX14843697
[2023-08-19 15:41:12,956]    INFO Parsing run SRR18743674
[2023-08-19 15:41:13,365]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:13,366]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:15,265]    INFO Parsing Study SRP400925
[2023-08-19 15:41:15,683]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:15,684]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:15,685]    INFO Getting Sample for SRP400925
[2023-08-19 15:41:30,185] WARNING There are 20 samples for SRP400925
[2023-08-19 15:41:30,185]    INFO Parsing sample SRS15319024
[2023-08-19 15:41:30,626]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:30,626]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:30,631] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:31,051]    INFO Getting Experiment for SRS15319024
[2023-08-19 15:41:31,052]    INFO Parsing Experiment SRX17793201
[2023-08-19 15:41:31,487]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:31,487]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:31,492] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:32,709] WARNING There are 2 runs for SRX17793201
[2023-08-19 15:41:32,709]    INFO Parsing run SRR21799208
[2023-08-19 15:41:33,141]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:33,142]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:35,187]    INFO Parsing run SRR21799209
[2023-08-19 15:41:35,614]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:35,615]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:37,563]    INFO Parsing sample SRS15319023
[2023-08-19 15:41:37,991]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:37,992]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:37,997] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:38,414]    INFO Getting Experiment for SRS15319023
[2023-08-19 15:41:38,415]    INFO Parsing Experiment SRX17793200
[2023-08-19 15:41:38,839]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:38,840]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:38,847] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:39,272] WARNING There are 2 runs for SRX17793200
[2023-08-19 15:41:39,272]    INFO Parsing run SRR21799210
[2023-08-19 15:41:39,693]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:39,694]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:41,682]    INFO Parsing run SRR21799211
[2023-08-19 15:41:42,102]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:42,102]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:44,049]    INFO Parsing sample SRS15319023
[2023-08-19 15:41:44,055] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:44,055]    INFO Getting Experiment for SRS15319023
[2023-08-19 15:41:44,055]    INFO Parsing Experiment SRX17793200
[2023-08-19 15:41:44,059] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:44,060] WARNING There are 2 runs for SRX17793200
[2023-08-19 15:41:44,060]    INFO Parsing run SRR21799210
[2023-08-19 15:41:44,317]    INFO Parsing run SRR21799211
[2023-08-19 15:41:44,591]    INFO Parsing sample SRS15319020
[2023-08-19 15:41:45,020]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:45,021]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:45,025] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:45,438]    INFO Getting Experiment for SRS15319020
[2023-08-19 15:41:45,438]    INFO Parsing Experiment SRX17793197
[2023-08-19 15:41:45,871]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:45,871]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:45,878] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:46,292] WARNING There are 2 runs for SRX17793197
[2023-08-19 15:41:46,292]    INFO Parsing run SRR21799216
[2023-08-19 15:41:46,714]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:46,715]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:48,669]    INFO Parsing run SRR21799217
[2023-08-19 15:41:49,102]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:49,103]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:51,084]    INFO Parsing sample SRS15319017
[2023-08-19 15:41:51,514]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:51,515]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:51,521] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:51,944]    INFO Getting Experiment for SRS15319017
[2023-08-19 15:41:51,944]    INFO Parsing Experiment SRX17793194
[2023-08-19 15:41:52,365]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:52,366]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:52,371] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:52,791] WARNING There are 2 runs for SRX17793194
[2023-08-19 15:41:52,791]    INFO Parsing run SRR21799222
[2023-08-19 15:41:53,222]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:53,223]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:55,341]    INFO Parsing run SRR21799223
[2023-08-19 15:41:55,761]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:55,761]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:57,729]    INFO Parsing sample SRS15319017
[2023-08-19 15:41:57,735] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:57,735]    INFO Getting Experiment for SRS15319017
[2023-08-19 15:41:57,735]    INFO Parsing Experiment SRX17793194
[2023-08-19 15:41:57,740] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:57,740] WARNING There are 2 runs for SRX17793194
[2023-08-19 15:41:57,740]    INFO Parsing run SRR21799222
[2023-08-19 15:41:58,001]    INFO Parsing run SRR21799223
[2023-08-19 15:41:58,289]    INFO Parsing sample SRS15319016
[2023-08-19 15:41:58,714]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:58,715]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:58,725] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:59,142]    INFO Getting Experiment for SRS15319016
[2023-08-19 15:41:59,142]    INFO Parsing Experiment SRX17793193
[2023-08-19 15:41:59,570]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:59,570]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:41:59,581] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:41:59,996] WARNING There are 2 runs for SRX17793193
[2023-08-19 15:41:59,996]    INFO Parsing run SRR21799225
[2023-08-19 15:42:00,427]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:00,427]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:02,381]    INFO Parsing run SRR21799224
[2023-08-19 15:42:02,808]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:02,809]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:04,780]    INFO Parsing sample SRS15319022
[2023-08-19 15:42:05,203]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:05,203]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:05,208] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:05,746]    INFO Getting Experiment for SRS15319022
[2023-08-19 15:42:05,746]    INFO Parsing Experiment SRX17793199
[2023-08-19 15:42:06,180]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:06,181]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:06,188] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:06,610] WARNING There are 2 runs for SRX17793199
[2023-08-19 15:42:06,611]    INFO Parsing run SRR21799212
[2023-08-19 15:42:07,031]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:07,032]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:08,995]    INFO Parsing run SRR21799213
[2023-08-19 15:42:09,423]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:09,425]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:11,391]    INFO Parsing sample SRS15319021
[2023-08-19 15:42:11,822]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:11,823]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:11,828] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:12,243]    INFO Getting Experiment for SRS15319021
[2023-08-19 15:42:12,243]    INFO Parsing Experiment SRX17793198
[2023-08-19 15:42:12,667]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:12,669]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:12,674] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:13,114] WARNING There are 2 runs for SRX17793198
[2023-08-19 15:42:13,114]    INFO Parsing run SRR21799215
[2023-08-19 15:42:13,533]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:13,534]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:15,519]    INFO Parsing run SRR21799214
[2023-08-19 15:42:15,939]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:15,940]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:17,899]    INFO Parsing sample SRS15319020
[2023-08-19 15:42:17,906] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:17,906]    INFO Getting Experiment for SRS15319020
[2023-08-19 15:42:17,907]    INFO Parsing Experiment SRX17793197
[2023-08-19 15:42:17,912] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:17,912] WARNING There are 2 runs for SRX17793197
[2023-08-19 15:42:17,912]    INFO Parsing run SRR21799216
[2023-08-19 15:42:18,174]    INFO Parsing run SRR21799217
[2023-08-19 15:42:18,437]    INFO Parsing sample SRS15319018
[2023-08-19 15:42:18,847]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:18,848]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:18,852] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:19,265]    INFO Getting Experiment for SRS15319018
[2023-08-19 15:42:19,265]    INFO Parsing Experiment SRX17793195
[2023-08-19 15:42:19,688]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:19,688]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:19,692] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:20,100] WARNING There are 2 runs for SRX17793195
[2023-08-19 15:42:20,101]    INFO Parsing run SRR21799220
[2023-08-19 15:42:20,508]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:20,508]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:22,444]    INFO Parsing run SRR21799221
[2023-08-19 15:42:22,851]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:22,852]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:24,727]    INFO Parsing sample SRS15319015
[2023-08-19 15:42:25,138]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:25,138]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:25,141] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:25,554]    INFO Getting Experiment for SRS15319015
[2023-08-19 15:42:25,554]    INFO Parsing Experiment SRX17793192
[2023-08-19 15:42:25,965]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:25,965]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:25,969] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:26,376] WARNING There are 2 runs for SRX17793192
[2023-08-19 15:42:26,376]    INFO Parsing run SRR21799226
[2023-08-19 15:42:26,781]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:26,782]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:28,665]    INFO Parsing run SRR21799227
[2023-08-19 15:42:29,076]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:29,076]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 15:42:31,326]    INFO Parsing sample SRS15319015
[2023-08-19 15:42:31,327] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:31,327]    INFO Getting Experiment for SRS15319015
[2023-08-19 15:42:31,327]    INFO Parsing Experiment SRX17793192
[2023-08-19 15:42:31,329] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:31,329] WARNING There are 2 runs for SRX17793192
[2023-08-19 15:42:31,329]    INFO Parsing run SRR21799226
[2023-08-19 15:42:31,569]    INFO Parsing run SRR21799227
[2023-08-19 15:42:31,832]    INFO Parsing sample SRS15319024
[2023-08-19 15:42:31,835] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:31,835]    INFO Getting Experiment for SRS15319024
[2023-08-19 15:42:31,835]    INFO Parsing Experiment SRX17793201
[2023-08-19 15:42:31,837] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 15:42:31,837] WARNING There are 2 runs for SRX17793201
[2023-08-19 15:42:31,838]    INFO Parsing run SRR21799208
[2023-08-19 15:42:32,090]    INFO Parsing run SRR21799209
[2023-08-19 15:42:32,161]   ERROR 429 Client Error: Too Many Requests for url: https://eutils.ncbi.nlm.nih.gov/entrez/eutils/efetch.fcgi?db=sra&id=SRR21799209&retmode=xml
[2023-08-19 15:42:32,161]   ERROR Provided accession is invalid
usage: ffq [-h] [-o OUT] [-l LEVEL] [--ftp] [--aws] [--gcp] [--ncbi] [--split] [--verbose] [--version] IDs [IDs ...]
ffq: error: For possible failure modes, please see https://github.com/pachterlab/ffq#failure-modes
ffq -o ./json_file/nar.json 10.1093/nar/gkac908 --verbose
Output:
[2023-08-19 16:09:47,143]   DEBUG Printing verbose output
[2023-08-19 16:09:47,143]   DEBUG Namespace(IDs=['10.1093/nar/gkac908'], o='./json_file/nar.json', t=None, l=None, ftp=False, aws=False, gcp=False, ncbi=False, split=False, verbose=True)
[2023-08-19 16:09:47,143] WARNING Searching by DOI may result in missing information.
[2023-08-19 16:09:47,143]    INFO Searching for DOI '10.1093/NAR/GKAC908'
[2023-08-19 16:09:47,245]    INFO Searching for Study SRP with title 'Estrogen regulates divergent transcriptional and epigenetic cell states in breast cancer'
[2023-08-19 16:09:48,612] WARNING No studies found with the given title. Searching Pubmed for DOI '10.1093/NAR/GKAC908'
[2023-08-19 16:09:48,880]    INFO Searching for GEO record linked to Pubmed ID '36318267'
[2023-08-19 16:09:49,226]    INFO Found 1 GEO Accessions: GSE154873
[2023-08-19 16:09:50,232]    INFO Parsing GEO GSE154873
[2023-08-19 16:09:50,413]    INFO Finding supplementary files for GEO GSE154873
[2023-08-19 16:09:52,959] WARNING There are 14 samples for GSE154873
[2023-08-19 16:09:52,959]    INFO Parsing GSM GSM4681761
[2023-08-19 16:09:53,417]    INFO Finding supplementary files for GSM GSM4681761
[2023-08-19 16:09:55,289]    INFO Getting sample for GSM4681761
[2023-08-19 16:09:55,898]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:09:55,898]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:09:55,901]    INFO Parsing sample SRS7054554
[2023-08-19 16:09:56,315]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:09:56,316]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:09:56,319] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:09:56,723] WARNING No experiment found
[2023-08-19 16:09:56,723]    INFO Getting Experiment for SRS7054554
[2023-08-19 16:09:57,192]    INFO Parsing Experiment SRX8785938
[2023-08-19 16:09:57,196] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:09:57,601] WARNING There are 0 runs for SRX8785938
[2023-08-19 16:09:57,601]    INFO Parsing GSM GSM4681762
[2023-08-19 16:09:57,815]    INFO Finding supplementary files for GSM GSM4681762
[2023-08-19 16:09:59,995]    INFO Getting sample for GSM4681762
[2023-08-19 16:10:00,555]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:00,555]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:00,557]    INFO Parsing sample SRS7054555
[2023-08-19 16:10:00,973]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:00,973]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:00,976] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:01,381] WARNING No experiment found
[2023-08-19 16:10:01,382]    INFO Getting Experiment for SRS7054555
[2023-08-19 16:10:01,780]    INFO Parsing Experiment SRX8785939
[2023-08-19 16:10:01,784] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:02,190] WARNING There are 0 runs for SRX8785939
[2023-08-19 16:10:02,190]    INFO Parsing GSM GSM4681763
[2023-08-19 16:10:02,424]    INFO Finding supplementary files for GSM GSM4681763
[2023-08-19 16:10:03,940]    INFO Getting sample for GSM4681763
[2023-08-19 16:10:04,503]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:04,504]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:04,506]    INFO Parsing sample SRS7054556
[2023-08-19 16:10:04,930]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:04,930]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:04,933] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:05,344] WARNING No experiment found
[2023-08-19 16:10:05,344]    INFO Getting Experiment for SRS7054556
[2023-08-19 16:10:05,742]    INFO Parsing Experiment SRX8785940
[2023-08-19 16:10:05,746] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:06,154] WARNING There are 0 runs for SRX8785940
[2023-08-19 16:10:06,155]    INFO Parsing GSM GSM4681764
[2023-08-19 16:10:06,386]    INFO Finding supplementary files for GSM GSM4681764
[2023-08-19 16:10:07,928]    INFO Getting sample for GSM4681764
[2023-08-19 16:10:08,482]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:08,483]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:08,485]    INFO Parsing sample SRS7054557
[2023-08-19 16:10:08,898]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:08,898]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:08,900] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:09,303] WARNING No experiment found
[2023-08-19 16:10:09,303]    INFO Getting Experiment for SRS7054557
[2023-08-19 16:10:09,795]    INFO Parsing Experiment SRX8785941
[2023-08-19 16:10:09,799] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:10,211] WARNING There are 0 runs for SRX8785941
[2023-08-19 16:10:10,211]    INFO Parsing GSM GSM4681765
[2023-08-19 16:10:10,439]    INFO Finding supplementary files for GSM GSM4681765
[2023-08-19 16:10:11,943]    INFO Getting sample for GSM4681765
[2023-08-19 16:10:12,496]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:12,496]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:12,499]    INFO Parsing sample SRS7054558
[2023-08-19 16:10:12,907]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:12,908]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:12,911] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:13,314] WARNING No experiment found
[2023-08-19 16:10:13,314]    INFO Getting Experiment for SRS7054558
[2023-08-19 16:10:13,676]    INFO Parsing Experiment SRX8785942
[2023-08-19 16:10:13,681] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:14,088] WARNING There are 0 runs for SRX8785942
[2023-08-19 16:10:14,088]    INFO Parsing GSM GSM6418438
[2023-08-19 16:10:14,288]    INFO Finding supplementary files for GSM GSM6418438
[2023-08-19 16:10:15,626]    INFO No supplementary files found for GSM6418438
[2023-08-19 16:10:15,999]    INFO Getting sample for GSM6418438
[2023-08-19 16:10:16,633]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:16,634]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:16,636]    INFO Parsing sample SRS14360572
[2023-08-19 16:10:17,039]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:17,040]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:17,043] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:17,446]    INFO Getting Experiment for SRS14360572
[2023-08-19 16:10:17,446]    INFO Parsing Experiment SRX16732252
[2023-08-19 16:10:17,449] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:17,855] WARNING There are 2 runs for SRX16732252
[2023-08-19 16:10:17,855]    INFO Parsing run SRR20711356
[2023-08-19 16:10:18,260]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:18,260]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:20,138]    INFO Parsing run SRR20711355
[2023-08-19 16:10:20,544]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:20,545]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:22,428]    INFO Parsing GSM GSM6418439
[2023-08-19 16:10:23,090]    INFO Finding supplementary files for GSM GSM6418439
[2023-08-19 16:10:24,182]    INFO No supplementary files found for GSM6418439
[2023-08-19 16:10:24,692]    INFO Getting sample for GSM6418439
[2023-08-19 16:10:25,245]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:25,245]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:25,247]    INFO Parsing sample SRS14360573
[2023-08-19 16:10:25,652]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:25,653]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:25,656] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:26,062]    INFO Getting Experiment for SRS14360573
[2023-08-19 16:10:26,062]    INFO Parsing Experiment SRX16732253
[2023-08-19 16:10:26,066] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:26,491] WARNING There are 4 runs for SRX16732253
[2023-08-19 16:10:26,491]    INFO Parsing run SRR20711357
[2023-08-19 16:10:26,902]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:26,902]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:28,868]    INFO Parsing run SRR20711359
[2023-08-19 16:10:29,283]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:29,283]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:31,229]    INFO Parsing run SRR20711358
[2023-08-19 16:10:31,641]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:31,642]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:33,682]    INFO Parsing run SRR20711360
[2023-08-19 16:10:34,094]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:34,095]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:36,038]    INFO Parsing GSM GSM6418440
[2023-08-19 16:10:36,903]    INFO Finding supplementary files for GSM GSM6418440
[2023-08-19 16:10:38,072]    INFO No supplementary files found for GSM6418440
[2023-08-19 16:10:38,444]    INFO Getting sample for GSM6418440
[2023-08-19 16:10:39,518]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:39,519]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:39,520]    INFO Parsing sample SRS14360574
[2023-08-19 16:10:39,937]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:39,937]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:39,940] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:40,344]    INFO Getting Experiment for SRS14360574
[2023-08-19 16:10:40,344]    INFO Parsing Experiment SRX16732254
[2023-08-19 16:10:40,349] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:40,762] WARNING There is 1 run for SRX16732254
[2023-08-19 16:10:40,762]    INFO Parsing run SRR20711361
[2023-08-19 16:10:41,183]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:41,183]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:43,138]    INFO Parsing GSM GSM6418441
[2023-08-19 16:10:43,890]    INFO Finding supplementary files for GSM GSM6418441
[2023-08-19 16:10:44,994]    INFO No supplementary files found for GSM6418441
[2023-08-19 16:10:45,413]    INFO Getting sample for GSM6418441
[2023-08-19 16:10:46,000]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:46,001]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:46,003]    INFO Parsing sample SRS14360575
[2023-08-19 16:10:46,417]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:46,418]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:46,420] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:46,832]    INFO Getting Experiment for SRS14360575
[2023-08-19 16:10:46,832]    INFO Parsing Experiment SRX16732255
[2023-08-19 16:10:46,836] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:47,241] WARNING There is 1 run for SRX16732255
[2023-08-19 16:10:47,241]    INFO Parsing run SRR20711362
[2023-08-19 16:10:47,647]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:47,648]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:49,547]    INFO Parsing GSM GSM6418442
[2023-08-19 16:10:49,766]    INFO Finding supplementary files for GSM GSM6418442
[2023-08-19 16:10:50,855]    INFO No supplementary files found for GSM6418442
[2023-08-19 16:10:51,245]    INFO Getting sample for GSM6418442
[2023-08-19 16:10:51,819]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:51,819]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:51,821]    INFO Parsing sample SRS14360576
[2023-08-19 16:10:52,236]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:52,236]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:52,238] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:52,650]    INFO Getting Experiment for SRS14360576
[2023-08-19 16:10:52,650]    INFO Parsing Experiment SRX16732256
[2023-08-19 16:10:52,653] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:53,061] WARNING There is 1 run for SRX16732256
[2023-08-19 16:10:53,061]    INFO Parsing run SRR20711363
[2023-08-19 16:10:53,483]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:53,484]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:55,436]    INFO Parsing GSM GSM6418443
[2023-08-19 16:10:55,646]    INFO Finding supplementary files for GSM GSM6418443
[2023-08-19 16:10:56,767]    INFO No supplementary files found for GSM6418443
[2023-08-19 16:10:57,188]    INFO Getting sample for GSM6418443
[2023-08-19 16:10:58,203]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:58,204]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:58,206]    INFO Parsing sample SRS14360577
[2023-08-19 16:10:58,617]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:58,617]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:58,620] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:59,039]    INFO Getting Experiment for SRS14360577
[2023-08-19 16:10:59,039]    INFO Parsing Experiment SRX16732257
[2023-08-19 16:10:59,043] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:10:59,458] WARNING There are 2 runs for SRX16732257
[2023-08-19 16:10:59,458]    INFO Parsing run SRR20711365
[2023-08-19 16:10:59,883]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:10:59,883]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:01,814]    INFO Parsing run SRR20711364
[2023-08-19 16:11:02,232]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:02,233]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:04,124]    INFO Parsing GSM GSM6418444
[2023-08-19 16:11:04,337]    INFO Finding supplementary files for GSM GSM6418444
[2023-08-19 16:11:05,427]    INFO No supplementary files found for GSM6418444
[2023-08-19 16:11:06,217]    INFO Getting sample for GSM6418444
[2023-08-19 16:11:07,075]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:07,076]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:07,078]    INFO Parsing sample SRS14360578
[2023-08-19 16:11:07,485]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:07,486]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:07,488] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:11:07,891]    INFO Getting Experiment for SRS14360578
[2023-08-19 16:11:07,892]    INFO Parsing Experiment SRX16732258
[2023-08-19 16:11:07,897] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:11:08,300] WARNING There are 2 runs for SRX16732258
[2023-08-19 16:11:08,301]    INFO Parsing run SRR20711366
[2023-08-19 16:11:08,712]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:08,713]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:10,618]    INFO Parsing run SRR20711367
[2023-08-19 16:11:11,032]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:11,033]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:12,943]    INFO Parsing GSM GSM6418445
[2023-08-19 16:11:13,141]    INFO Finding supplementary files for GSM GSM6418445
[2023-08-19 16:11:14,232]    INFO No supplementary files found for GSM6418445
[2023-08-19 16:11:15,152]    INFO Getting sample for GSM6418445
[2023-08-19 16:11:15,699]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:15,700]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:15,702]    INFO Parsing sample SRS14360579
[2023-08-19 16:11:16,115]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:16,115]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:16,118] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:11:16,523]    INFO Getting Experiment for SRS14360579
[2023-08-19 16:11:16,524]    INFO Parsing Experiment SRX16732259
[2023-08-19 16:11:16,526] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:11:16,939] WARNING There are 8 runs for SRX16732259
[2023-08-19 16:11:16,940]    INFO Parsing run SRR20711374
[2023-08-19 16:11:17,359]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:17,359]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:19,432]    INFO Parsing run SRR20711375
[2023-08-19 16:11:19,848]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:19,849]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:21,902]    INFO Parsing run SRR20711368
[2023-08-19 16:11:22,312]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:22,312]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:24,435]    INFO Parsing run SRR20711370
[2023-08-19 16:11:24,849]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:24,849]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:26,932]    INFO Parsing run SRR20711371
[2023-08-19 16:11:27,358]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:27,359]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:29,574]    INFO Parsing run SRR20711373
[2023-08-19 16:11:30,001]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:30,002]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:32,149]    INFO Parsing run SRR20711369
[2023-08-19 16:11:32,581]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:32,581]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:34,850]    INFO Parsing run SRR20711372
[2023-08-19 16:11:35,281]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:35,282]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:37,507]    INFO Parsing GSM GSM6418446
[2023-08-19 16:11:37,730]    INFO Finding supplementary files for GSM GSM6418446
[2023-08-19 16:11:39,076]    INFO No supplementary files found for GSM6418446
[2023-08-19 16:11:39,536]    INFO Getting sample for GSM6418446
[2023-08-19 16:11:40,159]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:40,162]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:40,165]    INFO Parsing sample SRS14360580
[2023-08-19 16:11:40,597]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:40,597]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:40,601] WARNING Failed to parse sample information from ENA XML. Falling back to ENA search...
[2023-08-19 16:11:41,012]    INFO Getting Experiment for SRS14360580
[2023-08-19 16:11:41,012]    INFO Parsing Experiment SRX16732260
[2023-08-19 16:11:41,020] WARNING Failed to parse experiment information from ENA XML. Falling back to ENA search...
[2023-08-19 16:11:41,469] WARNING There are 8 runs for SRX16732260
[2023-08-19 16:11:41,469]    INFO Parsing run SRR20711376
[2023-08-19 16:11:41,896]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:41,897]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:44,034]    INFO Parsing run SRR20711377
[2023-08-19 16:11:44,457]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:44,458]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:46,581]    INFO Parsing run SRR20711379
[2023-08-19 16:11:47,008]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:47,009]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:49,133]    INFO Parsing run SRR20711380
[2023-08-19 16:11:49,559]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:49,560]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:51,665]    INFO Parsing run SRR20711381
[2023-08-19 16:11:52,098]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:52,099]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:54,265]    INFO Parsing run SRR20711382
[2023-08-19 16:11:54,701]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:54,702]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:56,834]    INFO Parsing run SRR20711378
[2023-08-19 16:11:57,260]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:57,260]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:59,410]    INFO Parsing run SRR20711383
[2023-08-19 16:11:59,832]   DEBUG Encoding detection: utf_8 is most likely the one.
[2023-08-19 16:11:59,833]   DEBUG Encoding detection: utf_8 is most likely the one.

up


Azure/functions-container-action@v1 - TypeError: Cannot read property 'getApplicationURL'

I have an azure function (python code) containerized in a Dockerfile. I want to run it from Github actions, so I am doing in my workflow the following:

    - name: 'Run Azure Functions Container Action'
      uses: Azure/functions-container-action@v1
      id: fa
      with:
        app-name: my-spec-prod-azure-function
        image: containerregistry.azurecr.io/my-azure-function:latest

    - name: Azure logout
      run: |
        az logout

The thing here is I am using Azure/functions-container-action@v1 github action to run the container but it does not work, I got the following message error in my pipeline:
Run Azure/functions-container-action@v1
  with:
    app-name: my-spec-prod-azure-function
    image: containerregistry.azurecr.io/my-azure-function:latest
  env:
    AZURE_HTTP_USER_AGENT:
    AZUREPS_HOST_ENVIRONMENT:
    DOCKER_CONFIG: /home/runner/work/_temp/docker_login_1613723968334
Error: Error: Resource my-spec-prod-azure-function doesn't exist.
(node:4655) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'getApplicationURL' of undefined
    at /home/runner/work/_actions/Azure/functions-container-action/v1/lib/main.js:68:68
    at Generator.throw (<anonymous>)
    at rejected (/home/runner/work/_actions/Azure/functions-container-action/v1/lib/main.js:6:65)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:4655) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:4655) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Checking the azure actions workflow samples, you also use the same action (Azure/functions-container-action@v1) to deploy an azure function, they emphasize that here.
Here someone got a similar error description but I am afraid it is not for azure functions container but for appservices actions that use containers. Despite that, I also tried the azure/webapps-container-deploy@v1 action but it does not work, and I think that is not a suited action.
I checked your official marketplace site and you say this is the latest version to use:
- name: Azure Functions Container Action
  uses<EMAIL_ADDRESS>
So I changed Azure/functions-container-action@v1 by<EMAIL_ADDRESS>without success, I got a very similar error but with some hints or clue about setting environment variables.
Error: Unable to process command '::set-env name=AZURE_HTTP_USER_AGENT,::GITHUBACTIONS_DeployFunctionAppContainerToAzure_b32b908e01efeb4da360da24648fd5091bc18dcc93090b9c05ee3b76efe9b57e' successfully.
Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands
Error: Error: Resource my-spec-prod-azure-function doesn't exist.
(node:4508) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'getApplicationURL' of undefined
    at /home/runner/work/_actions/Azure/functions-container-action/v1.0.1/lib/main.js:68:68
    at Generator.throw (<anonymous>)
    at rejected (/home/runner/work/_actions/Azure/functions-container-action/v1.0.1/lib/main.js:6:65)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:4508) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:4508) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Regarding the The set-env command is disabled new error message, checking the log changes, here is not clear for me how or why the env variables like  AZURE_HTTP_USER_AGENT and the other one should be set it up properly.

@Hazhzeng - Can you please look into this issue?

Thanks @N-Usha and @Hazhzeng
I wanted to come up with a kind of workaround I have been trying
UPDATE
Regarding  the The set-env command is disabled new error message, checking the changes announced, here, I can see:

Action authors who are using the toolkit should update the @actions/core package to v1.2.6 or greater to get the updated addPath and exportVariable functions

I am not an actions author, but I wanted to try to update/install the @actions/core package to v1.2.6 into the github hosted runner I am using in the pipeline, so my YAML file definition has now these steps:
- name: 'Setting node environment to get npm command'
      # uses: actions/checkout@v2
      uses<EMAIL_ADDRESS>      with:
        node-version: '12'

    - name: 'Installing @actions/core latest version'
      # uses: @actions/core
      # with:
        # version: 1.2.6
      run: |
        npm install @actions/core
        # SETTING UP AZURE_HTTP_USER_AGENT to GITHUB_ENV
        echo "name=${AZURE_HTTP_USER_AGENT}" >> $GITHUB_ENV

    - name: 'Run Azure Functions Container Action'
      uses<EMAIL_ADDRESS>      id: fa
      with:
        app-name: my-spec-prod-azure-function
        image: containerregistry.azurecr.io/my-azure-function:latest

    - name: Azure logout
      run: |
        az logout

In addition, I added to my repository the following files:

package.json

{
  "name": "my-project",
  "version": "1.0.0",
  "repository": {
    "type": "git",
    "url": "https://github.com/user-org/my-project.git"
  },
  "dependencies": {
    "@actions/core": "^1.2.6"
  }
}

package-lock.json

{
  "name": "my-project",
  "version": "1.0.0",
  "lockfileVersion": 1,
  "requires": true,
  "packages": {
    "": {
      "version": "1.0.0",
      "dependencies": {
        "@actions/core": "^1.2.6"
      }
    },
    "node_modules/@actions/core": {
      "version": "1.2.6",
      "resolved"<EMAIL_ADDRESS>      "integrity": "sha512-ZQYitnqiyBc3D+k7LsgSBmMDVkOVidaagDG7j3fOym77jNunWRuYx7VSHa9GNfFZh+zh61xsCjRj4JxMZlDqTA=="
    }
  },
  "dependencies": {
    "@actions/core": {
      "version": "1.2.6",
      "resolved"<EMAIL_ADDRESS>      "integrity": "sha512-ZQYitnqiyBc3D+k7LsgSBmMDVkOVidaagDG7j3fOym77jNunWRuYx7VSHa9GNfFZh+zh61xsCjRj4JxMZlDqTA=="
    }
  }
}

I can see @actions/core package is being added to my workflow here:

Setting node environment to get npm command step

Run<EMAIL_ADDRESS>  with:
    node-version: 12
    always-auth: false
    check-latest: false
    token: ***
  env:
    AZURE_HTTP_USER_AGENT:
    AZUREPS_HOST_ENVIRONMENT:
    DOCKER_CONFIG: /home/runner/work/_temp/docker_login_1613768385315
Found in cache @ /opt/hostedtoolcache/node/12.20.2/x64

Installing @actions/core latest version step

Run npm install @actions/core
  npm install @actions/core
  echo "name=$***AZURE_HTTP_USER_AGENT***" >> $GITHUB_ENV
  shell: /usr/bin/bash -e ***0***
  env:
    AZURE_HTTP_USER_AGENT:
    AZUREPS_HOST_ENVIRONMENT:
    DOCKER_CONFIG: /home/runner/work/_temp/docker_login_1613768385315
npm WARN<EMAIL_ADDRESS>No license field.

+<EMAIL_ADDRESS>added 1 package and audited 1 package in 0.524s
found 0 vulnerabilities

But at the step when deploying azure function I got the same error gotten before
Error: Unable to process command '::set-env name=AZURE_HTTP_USER_AGENT,::GITHUBACTIONS_DeployFunctionAppContainerToAzure_b32b908e01efeb4da360da24648fd5091bc18dcc93090b9c05ee3b76efe9b57e' successfully.
Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands

Reading on here (also because of the blog post link referenced above) I detailed, the thing is I have to find a different way to set up variables instead of use the deprecated “set-env”.
It seems behind of scenes<EMAIL_ADDRESS>try to use the the deprecated “set-env” command. Now is necessary to pass variables into $GITHUB_ENV
such as GitHub actions docs say it here
I am trying to do the same with AZURE_HTTP_USER_AGENT in this way as you could see above at the immediately previous step before using<EMAIL_ADDRESS>echo "name=${AZURE_HTTP_USER_AGENT}" >> $GITHUB_ENV
But I got the same error. It seems that is not the correct way to do it. Is not clear for me how or why the env variables like  AZURE_HTTP_USER_AGENT should be set it up properly with respect to GITHUB_ENV
But in more general thinking,  I am in doubt whether is this an issue from azure functions container action marketplace or is something I should handle it by attending the GitHub changes env variables discussed
I would love your thoughts about it.

We have already upgraded @actions/core version in our action. since you are pointing older version v1.0.1 its failing for you. latest version id v1.0.2 or just `v1. set-env error is coming because of this version only.
Now coming back to your first error.
Are you using azure/login action before function-container-action as mentioned here?

@AmrutaKawade, By the time I filed this issue I tried the v1 and v1.0.1 versions and I got the error described above. I also tried these versions right now, without succeed
I didn't know there were a new v1.0.2 version for this github action. At the marketplace website the latest referenced version is v1.0.1.
I pointed up to v1.0.2 version and I got the same error as well. This one:
Run<EMAIL_ADDRESS>  with:
    app-name: rhd-spec-prod-fem-downloader-function
    image: rhdhvcontainerregistry.azurecr.io/af-fem-downloader:latest
  env:
    AZURE_HTTP_USER_AGENT:
    AZUREPS_HOST_ENVIRONMENT:
    DOCKER_CONFIG: /home/runner/work/_temp/docker_login_1613984821988
Error: Error: Resource rhd-spec-prod-fem-downloader-function doesn't exist.
(node:1724) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'getApplicationURL' of undefined
    at /home/runner/work/_actions/Azure/functions-container-action/v1.0.2/lib/main.js:68:68
    at Generator.throw (<anonymous>)
    at rejected (/home/runner/work/_actions/Azure/functions-container-action/v1.0.2/lib/main.js:6:65)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:1724) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1724) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I am using azure/login@v1 as a first step before building the container when azure functions live and before deploying it. The azure login and docker steps are successful for me, but not when running the azure functions action container. Here my entire workflow actions:
name: Deploy_Workflow

on:
  push:
    branches:
    - main

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
    - name: 'Checkout GitHub Action'
      uses: actions/checkout@master

    - name: 'Login via Azure CLI'
      uses: azure/login@v1
      with:
        creds: ${{ secrets.AZURE_CREDENTIALS }}

    - name: 'Docker Login'
      uses: azure/docker-login@v1
      with:
        login-server: containerregistry.azurecr.io
        username: ${{ secrets.REGISTRY_USERNAME }}
        password: ${{ secrets.REGISTRY_PASSWORD }}

    - name: 'Compose Customized Docker Image'
      shell: bash
      run: |
        docker image build --build-arg AZ_DEVOPS_TOKEN="${{ secrets.AZ_DEVOPS_TOKEN }}"  . -t containerregistry.azurecr.io/my-azure-function:latest
        docker push containerregistry.azurecr.io/my-azure-function:latest

    - name: 'Run Azure Functions Container Action'
      uses<EMAIL_ADDRESS>      id: fa
      with:
        app-name: my-spec-prod-azure-function
        image: containerregistry.azurecr.io/my-azure-function:latest

    - name: Azure logout
      run: |
        az logout

Dear @AmrutaKawade I already using the latest version, but the error persists.
Since you point out you have already upgraded the @actions/core version in this<EMAIL_ADDRESS>or @v1 any ideas what could be going on?

Dear @AmrutaKawade, @Hazhzeng, and @N-Usha
Is there any chance to consider this issue? :)

@bgarcial underline issue is
Error: Resource my-spec-prod-azure-function doesn't exist.
check if resource exists.

Hi @bgarcial,
Sorry for the confusion. The v1 version is actually pointing to the latest v1.0.2 version bumping the GitHub Action SDK to 1.2.6. In this version, we already fix the issue introduced by set-env. This issue only exists in the older version v1.0.1. That's why you're seeing this.
However, as Amruta mentioned, the root cause of your issue is not related to set-env command. You're seeing this because your my-spec-prod-azure-function resource is not created. If you have any questions, please let me.

@Hazhzeng @AmrutaKawade
Thanks for your reply.
That's is the strange of the situation. Of course the azure function exist. I am able to call it and send parameters to it. The tenant data and service principal used in azure login action has permissions over that azure function.

@Hazhzeng @AmrutaKawade Indeed the AZURE_CREDENTIALS value was not pointing to the correct place where the azure function is hosted. So I want to apologize to you all guys and thanks for your support.


This Month in Rust OSDev: December 2022

This is a draft for the upcoming "This Month in Rust OSDev: December 2022" post. Please add your content to this draft by creating a pull request against the next branch. All projects related to OS development in Rust are valid here, they don't need to be associated with the rust-osdev organization.
The post will be published around January 6.

Happy new year to you all! It's time to prepare a new issue of our monthly newsletter. I plan to publish it on Friday or Saturday, so please submit your content until then. Thanks!
cc @rust-osdev/all @kevinaboos

Thanks @phil-opp, will definitely submit an update within the next two days.


chore(agnostification): eliminate common's dependent on isNode check.

related to #6125
by add a Config module which contains the node specific packages(ws, fs etc), let the common depend on it(dependeny injection), we can remove isNode check in common code, as well as dynamic imports.
every entry(node, web) needs initialize the Config before export the Puppeteer object.
this way, we may support some kind of support for filesystem in the browser(normal webpage or chrome extension).

Jack, PTAL

Jack, PTAL

Jack, could you PTAL and see if your changes were addressed? Thanks!

This is looking really good, thanks! I have one final though and then I think we can try to get this in.


bug: ToastController displaying an orange border box

Bug Report
Ionic version:

[x] 5.1.0
Current behavior:

An orange border box appears when I present a toast message. Disappears when I tap anywhere else but the toast and appears again when I tap it.
Expected behavior:

Not displaying anything like this when presenting a toast message or tap it.
Steps to reproduce:

The easiest way to reproduce is to copy the "presentToast()" function below and call it. When the toast appears you should see an orange border box around the app and when you tap anywhere else it should disappear. (Use a dark theme might help you notice it)
Related code:

import { Component } from '@angular/core';
import { ToastController } from '@ionic/angular';

@Component({
  selector: 'app-home',
  templateUrl: 'home.page.html',
  styleUrls: ['home.page.scss'],
})
export class HomePage {

  constructor(
    private toastCtrl: ToastController
  ) {
    this.presentToast('Hello World!');
  }

  async presentToast(msg: string, dur = 150000) {
    const toast = await this.toastCtrl.create({
      message: msg,
      duration: dur
    });
    await toast.present();
  }
}

Other information:

Ionic info:

Ionic:

   Ionic CLI                     : 6.7.0 (/usr/local/lib/node_modules/@ionic/cli)
   Ionic Framework               : @ionic/angular 5.1.0
   @angular-devkit/build-angular : 0.803.26
   @angular-devkit/schematics    : 8.3.26
   @angular/cli                  : 8.3.26
   @ionic/angular-toolkit        : 2.2.0

Capacitor:

   Capacitor CLI   : 2.0.1
   @capacitor/core : 2.0.1

Utility:

   cordova-res : not installed
   native-run  : not installed

System:

   NodeJS : v12.16.1 (/usr/local/bin/node)
   npm    : 6.13.4
   OS     : macOS Catalina

This also affects loading controller window.
As a temporary fix,
ion-modal, ion-loading {   outline: none }
in globals.scss file seems to help.

This also affects LoadingController window.
As a temporary workaround adding this to globals.scss seems to help:
ion-modal, ion-loading {
  outline: none;
}

This also affects AlertController window.

Thanks for the issue. Can you try the following dev build and let me know if it resolves the issue?
Ionic React
npm i<EMAIL_ADDRESS>Ionic Angular
npm i<EMAIL_ADDRESS>

Thanks for the issue. Can you try the following dev build and let me know if it resolves the issue?
Ionic React
npm i<EMAIL_ADDRESS>Ionic Angular
npm i<EMAIL_ADDRESS>
Yep, fixed it for all controllers.

Thanks for the issue. This has been resolved via https://github.com/ionic-team/ionic/pull/21226, and a fix will be available in an upcoming release of Ionic Framework.


Sample Dockerfile: put comment in a separate line

The provided sample is not be a valid Dockerfile

Docker treats lines that begin with # as a comment, unless the line is a valid parser directive. A # marker anywhere else in a line is treated as an argument.

Thx!


-Xms and -Xmx are stated twice after setting the cassandra-jvm-extra-opts

juju config contrail-analyticsdb cassandra-jvm-extra-opts="-Xms14336m -Xmx14336m"
We noticed that after setting the cassandra-jvm-extra-opts above, in the command used to start cassandra. they are passing -Xms and -Xmx two times,
once with the old default: -Xms8041M -Xmx8041M
and one with the new values, in this case: -Xms14336m -Xmx14336m
ubuntu@juju-073f4e-6-kvm-1:~$ ps aux | grep cass | grep Xmx
999      13400  835 52.9 131978132 17446024 ?  Ssl  07:55 123:09 java -Xloggc:/var/log/cassandra/gc.log -ea -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -XX:+HeapDumpOnOutOfMemoryError -Xss256k -XX:StringTableSize=1000003 -XX:+AlwaysPreTouch -XX:-UseBiasedLocking -XX:+UseTLAB -XX:+ResizeTLAB -XX:+UseNUMA -XX:+PerfDisableSharedMem -Djava.net.preferIPv4Stack=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSWaitDuration=10000 -XX:+CMSParallelInitialMarkEnabled -XX:+CMSEdenChunksRecordAlways -XX:+CMSClassUnloadingEnabled -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -XX:+PrintPromotionFailure -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=10M -Xms8041M -Xmx8041M -Xmn1200M -XX:CompileCommandFile=/etc/cassandra/hotspot_compiler -javaagent:/usr/share/cassandra/lib/jamm-0.3.0.jar -Dcassandra.jmx.local.port=7199 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.password.file=/etc/cassandra/jmxremote.password -Djava.library.path=/usr/share/cassandra/lib/sigar-bin -Xms14336m -Xmx14336m -Dcassandra.rpc_port=9160 -Dcassandra.native_transport_port=9042 -Dcassandra.ssl_storage_port=7011 -Dcassandra.storage_port=7010 -Dcassandra.jmx.local.port=7200 -Dcassandra.libjemalloc=/usr/lib/x86_64-linux-gnu/libjemalloc.so.1 -XX:OnOutOfMemoryError=kill -9 %p -Dlogback.configurationFile=logback.xml -Dcassandra.logdir=/var/log/cassandra -Dcassandra.storagedir=/var/lib/cassandra -Dcassandra-foreground=yes -cp /etc/cassandra:/usr/share/cassandra/lib/HdrHistogram-2.1.9.jar:/usr/share/cassandra/lib/ST4-4.0.8.jar:/usr/share/cassandra/lib/airline-0.6.jar:/usr/share/cassandra/lib/antlr-runtime-3.5.2.jar:/usr/share/cassandra/lib/asm-5.0.4.jar:/usr/share/cassandra/lib/caffeine-2.2.6.jar:/usr/share/cassandra/lib/cassandra-driver-core-3.0.1-shaded.jar:/usr/share/cassandra/lib/commons-cli-1.1.jar:/usr/share/cassandra/lib/commons-codec-1.9.jar:/usr/share/cassandra/lib/commons-lang3-3.1.jar:/usr/share/cassandra/lib/commons-math3-3.2.jar:/usr/share/cassandra/lib/compress-lzf-0.8.4.jar:/usr/share/cassandra/lib/concurrent-trees-2.4.0.jar:/usr/share/cassandra/lib/concurrentlinkedhashmap-lru-1.4.jar:/usr/share/cassandra/lib/disruptor-3.0.1.jar:/usr/share/cassandra/lib/ecj-4.4.2.jar:/usr/share/cassandra/lib/guava-18.0.jar:/usr/share/cassandra/lib/high-scale-lib-1.0.6.jar:/usr/share/cassandra/lib/hppc-0.5.4.jar:/usr/share/cassandra/lib/jackson-core-asl-1.9.13.jar:/usr/share/cassandra/lib/jackson-mapper-asl-1.9.13.jar:/usr/share/cassandra/lib/jamm-0.3.0.jar:/usr/share/cassandra/lib/javax.inject.jar:/usr/share/cassandra/lib/jbcrypt-0.3m.jar:/usr/share/cassandra/lib/jcl-over-slf4j-1.7.7.jar:/usr/share/cassandra/lib/jctools-core-1.2.1.jar:/usr/share/cassandra/lib/jflex-1.6.0.jar:/usr/share/cassandra/lib/jna-4.2.2.jar:/usr/share/cassandra/lib/joda-time-2.4.jar:/usr/share/cassandra/lib/json-simple-1.1.jar:/usr/share/cassandra/lib/jstackjunit-0.0.1.jar:/usr/share/cassandra/lib/libthrift-0.9.2.jar:/usr/share/cassandra/lib/log4j-over-slf4j-1.7.7.jar:/usr/share/cassandra/lib/logback-classic-1.1.3.jar:/usr/share/cassandra/lib/logback-core-1.1.3.jar:/usr/share/cassandra/lib/lz4-1.3.0.jar:/usr/share/cassandra/lib/metrics-core-3.1.0.jar:/usr/share/cassandra/lib/metrics-jvm-3.1.0.jar:/usr/share/cassandra/lib/metrics-logback-3.1.0.jar:/usr/share/cassandra/lib/netty-all-4.0.44.Final.jar:/usr/share/cassandra/lib/ohc-core-0.4.4.jar:/usr/share/cassandra/lib/ohc-core-j8-0.4.4.jar:/usr/share/cassandra/lib/reporter-config-base-3.0.3.jar:/usr/share/cassandra/lib/reporter-config3-3.0.3.jar:/usr/share/cassandra/lib/sigar-1.6.4.jar:/usr/share/cassandra/lib/slf4j-api-1.7.7.jar:/usr/share/cassandra/lib/snakeyaml-1.11.jar:/usr/share/cassandra/lib/snappy-java-<IP_ADDRESS>.jar:/usr/share/cassandra/lib/snowball-stemmer-<IP_ADDRESS>1.1.jar:/usr/share/cassandra/lib/stream-2.5.2.jar:/usr/share/cassandra/lib/thrift-server-0.3.7.jar:/usr/share/cassandra/apache-cassandra-3.11.2.jar:/usr/share/cassandra/apache-cassandra-thrift-3.11.2.jar:/usr/share/cassandra/apache-cassandra.jar:/usr/share/cassandra/stress.jar: org.apache.cassandra.service.CassandraDaemo

private bug filed https://contrail-jws.atlassian.net/browse/CEM-7290

In general this bug is for official cassandra container - https://github.com/docker-library/cassandra/tree/5b7eebbf4412cf8b1434cfe6430648c606cdd6de/3.11
Charms uses Juniper's cassandra container that is built on top of official. We just passes additional opts there but cassandra's container doesn't remove from start string own params.
Anyway as I see - java takes correct values and works as expected.

Hi Andrey,
But it looks java didn't work as expected after we adding the following extra options, it resulted in one unit being unable to complete the restart of the cassandra container. Sorry, I can't provider more info because this happened in a product env, our operators reverted the change to attepmpt to recover after that.
juju config contrail-analyticsdb cassandra-jvm-extra-opts='-Xms10240M -Xmx10240M -XX:SurvivorRatio=2 -XX:MaxTenuringThreshold=16'
So actually we can not apply jvm options to optimize the system. and I just reported the original issue here - https://github.com/Juniper/contrail-charms/issues/96

Hi, as I see both bugs are for contrail itself and not for charms, do you agree?
And btw - do you you contrail as opensource code or via professional services?

Given we use the charms to deploy Contrail, it's whichever code is deployed by the charm.
Regarding if the bug reports are for the charm, or for Contrail, it really depends - the charm option for cassandra-jvm-extra-opts does deliver something to the unit, but it doesn't have the desired effect, which I would usually classify as a charm bug.  If there's a bug in Contrail which this highlights then that would be a separate, additional, bug report.


[BUG] SMO ServerConnection to AzureSqlDatabase using Active Directory Default auth

To Reproduce
After starting a Cloud Shell session, I connect my account and try to establish a connection to an Azure SQL Database.
I use (Get-AzAccessToken).UserId to check my account is connected.
I am using the SqlServer PowerShell module (updated to the latest version 22.1.1, since the version installed on Cloud Shell is 2 months old and also I want to use the same version I am using locally. In fact I get the same problem regardless of whether I update the SqlServer module or not.
My connection is using the ServerConnection class (SMO) as explained here, and using Active Directory Default authentication.
The SMO library used by the v22.1.1 SqlServer PowerShell module is v17.13.0.
Connect-AzAccount -DeviceCode # connect my account
Update-Module SqlServer # Update the SqlServer module to the latest version, currently 22.1.1
Import-Module SqlServer -MinimumVersion "22.1.1" # Import the SqlServer module, latest version
$newcon = New-Object Microsoft.SqlServer.Management.Common.ServerConnection
$newcon.ConnectionString = "Data Source=myserver.database.windows.net;Initial Catalog=mydb;Encrypt=False;Trust Server Certificate=False;Authentication=ActiveDirectoryDefault"
$newcon.Connect()

Observed Behavior
After a short period I get an error message and the connection fails to connect.
MethodInvocationException: Exception calling "Connect" with "0" argument(s): "Failed to connect to server myserver.database.windows.net."

InnerException : Microsoft.Data.SqlClient.SqlException (0x80131904): The operation was canceled.
                  ---> System.Threading.Tasks.TaskCanceledException: The operation was canceled.
                    at Azure.Core.CancellationHelper.ThrowOperationCanceledException(Exception innerException, CancellationToken cancellationToken)
                    at Azure.Core.CancellationHelper.ThrowIfCancellationRequested(CancellationToken cancellationToken)
                    at Azure.Core.Pipeline.ResponseBodyPolicy.ThrowIfCancellationRequestedOrTimeout(CancellationToken originalToken, CancellationToken timeoutToken, Exception inner,
                 TimeSpan timeout)
                    at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
                    at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
                    at Azure.Core.Pipeline.RedirectPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
                    at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
                    at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
                    at Azure.Identity.ManagedIdentitySource.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
                    at Azure.Identity.ManagedIdentityClient.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
                    at Azure.Identity.ManagedIdentityCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
                    at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)
                    at Azure.Identity.ManagedIdentityCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
                    at Azure.Identity.ManagedIdentityCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)
                    at Azure.Identity.DefaultAzureCredential.GetTokenFromSourcesAsync(TokenCredential[] sources, TokenRequestContext requestContext, Boolean async, CancellationToken
                 cancellationToken)
                    at Azure.Identity.DefaultAzureCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
                    at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)
                    at Azure.Identity.DefaultAzureCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
                    at Azure.Identity.DefaultAzureCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)
                    at Microsoft.Data.SqlClient.ActiveDirectoryAuthenticationProvider.AcquireTokenAsync(SqlAuthenticationParameters parameters)
                    at Microsoft.Data.SqlClient.SqlInternalConnectionTds.<>c__DisplayClass147_1.<<GetFedAuthToken>b__1>d.MoveNext()
                 --- End of stack trace from previous location ---
                    at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)
                    at Microsoft.Data.ProviderBase.DbConnectionPool.CheckPoolBlockingPeriod(Exception e)
                    at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
                    at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
                    at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean
                 onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
                    at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions,
                 DbConnectionInternal& connection)
                    at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions,
                 DbConnectionInternal oldConnection, DbConnectionInternal& connection)
                    at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory,
                 TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
                    at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1
                 retry, DbConnectionOptions userOptions)
                    at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides)
                    at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)
                    at Microsoft.Data.SqlClient.SqlConnection.Open()
                    at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnectImpl()
                    at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect()
                    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
                 ClientConnectionId:e9e29fbe-158c-43c8-8f60-9441402b92fc
                 ClientConnectionId before routing:0789793d-0e0e-4581-a163-8298de0f2665
                 Routing Destination:e5fd1a19bb6e.tr7243.australiaeast1-a.worker.database.windows.net,11024
HelpLink       :
Source         : Microsoft.SqlServer.ConnectionInfo
HResult        : -2146233087
StackTrace     :    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
                    at CallSite.Target(Closure, CallSite, Object)

Expected behavior
I expect that no error will be returned, and that my connection will be successful.
Is this specific to Cloud Shell?
I'm using PowerShell v7.3.4 (same as Cloud Shell) on my Windows 10 desktop. I have the same version of the SqlServer PowerShell module installed, v22.1.1. When I run the same commands, the expected behaviour occurs. I use (Get-AzAccessToken).UserId to confirm my account is connected (same account with Cloud Shell).
Interface information
Via Windows Terminal on Windows 10.
Additional context
If I change the authentication method from "Active Directory Default" to "Active Directory Password" and modify the connection string to this, "Data Source=myserver.database.windows.net;Initial Catalog=mydb;User ID=user@mydomain.com;Password=mYp@sSw0Rd!;Connect Timeout=30;Encrypt=False;Trust Server Certificate=False;Authentication=ActiveDirectoryPassword", the connection is successful.
However naturally I do want to use passwordless authentication (Active Directory Default).
EDIT: I decided to try the Cloud Shell in the Azure Portal just now, since I had been subbornly sticking with the Terminal version all along. And I get the expected behaviour from there. Furthermore it works regardless of whether I connect my account or not, I did not realise this. So the issue seems to be isolated specifically to the Windows Terminal Cloud Shell?

Check network connectivity: Make sure that Azure Cloud Shell has access to the Internet and that there are no network restrictions that might be blocking the connection to your Azure SQL database.Update the SqlServer module: Although you mentioned that you have already updated the SqlServer module to the latest version, there might be some incompatibility or specific issue that has not been addressed yet. Try using an older version of the SqlServer module to see if that fixes the problem.Try different authentication methods: If the connection works with "Active Directory Password" but not with "Active Directory Default", there might be a problem with the way authentication is done. Try using different supported authentication methods to see if that resolves the issue.Check your account settings: Make sure your Azure account has the proper permissions to access the SQL database and perform theauthentication using the selected method.Contact Azure support: If you've tried the above solutions and still can't resolve the issue, I would recommend contacting Azure support. They will have access to the most up-to-date information and tools to help you resolve your specific Azure Cloud Shell issue.

Thanks for the suggestions. There seems to be a difference between the terminal-based Cloud Shell vs the Cloud Shell in the Azure portal, based on the edit I added to the Additional context in my original post. I don't see that is my specific issue.

Hi @theJasonHelmick ,
Azure Cloud Shell (Terminal)
I am logged on to my desktop (laptop) with<EMAIL_ADDRESS>(Azure AD account). I start a new Azure Cloud Shell session via Windows Terminal. It prompts me to visit https://microsoft.com/devicelogin and enter the provided code. I do this, select my account, and close the tab. Back at the Cloud Shell, and it prompts me to select my Tenant, which I do (in my case there are 2 tenants to choose from, so I naturally select the one associated with the Azure SQL Database I am interested in). After the authentication process completes I am left at the command prompt. I run the command (Get-AzAccessToken).UserId and it returns MSI@***** (where ***** is a 5 digit number).
Azure Cloud Shell (Azure Portal)
I log in to the portal using my Azure AD account<EMAIL_ADDRESS>This is the same user as I used above. I open the Azure Cloud Shell by clicking on "Cloud Shell" at the top. After it authenticates I am left at the command prompt. I run the command (Get-AzAccessToken).UserId and it returns MSI@***** (where ***** is a 5 digit number). This is the same number as above.
In both shells above, I run the following commands:
Import-Module SqlServer
$newcon = New-Object Microsoft.SqlServer.Management.Common.ServerConnection
$newcon.ConnectionString = "Data Source=mysqlserver.database.windows.net;Initial Catalog=mydb;Encrypt=False;Trust Server Certificate=False;Authentication=ActiveDirectoryDefault"
$newcon.Connect()

From the Terminal Cloud Shell, after a brief period, I get this error:

MethodInvocationException: Exception calling "Connect" with "0" argument(s): "Failed to connect to server mysqlserver.database.windows.net."

After getting the error, I ran Get-Error and saved the output, in case it is of use.
connect_error.txt
From the Portal Cloud Shell it connects right away (no error is given). I can then, for example, use the connection to create a new server object and get details back from the server.
While documenting this for my response, I noticed that after I get a successful connection from the Portal Cloud Shell, the connection then succeeds from the Terminal Cloud Shell. It's not just a timing issue. I had tried repeatedly from my Terminal, even with a 10 minute wait in between, and consistently got the error message mentioned. I then tried the Portal Cloud Shell, and after connecting successfully, I immediately retried my Terminal Cloud Shell, and it connected right away. I exited from both Cloud Shells, and reauthenticated with my Terminal Cloud Shell, and I could still successfully connect to my SQL db.
Here is the output from az account show. It is identical in both Cloud Shells, Terminal and Portal.
{
  "environmentName": "AzureCloud",
  "homeTenantId": "94fd9d0a-7823-48d8-be50-0c6559650cc9",
  "id": "16afc5ef-0971-4cf2-bcdc-25a5e8f4e189",
  "isDefault": true,
  "managedByTenants": [],
  "name": "mysub",
  "state": "Enabled",
  "tenantId": "94fd9d0a-7823-48d8-be50-0c6559650cc9",
  "user": {
    "cloudShellID": true,
    "name"<EMAIL_ADDRESS>    "type": "user"
  }
}


HTTP Error: Converting JSONSpan to domain Span failed: strconv.ParseFloat: parsing "1.797693135e+308": value out of range

Describe the bug
I found this error when query traces. Spans are stored in es. I didn't find float64 type when checked directly from ES. There are too many 560 spans so I'm not able to display all here.
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Version (please complete the following information):

OS: [e.g. Linux]
Jaeger version: [e.g. 1.8]
Deployment: [e.g. bare metal, Docker, Kubernetes, ...]

What troubleshooting steps did you try?
Try to follow https://www.jaegertracing.io/docs/latest/troubleshooting/ and describe how far you were able to progress and/or which steps did not work.
Additional context
Add any other context about the problem here.

You forgot to answer all the leading questions that would help us understand your problem, especially the "steps to reproduce"...

You forgot to answer all the leading questions that would help us understand your problem, especially the "steps to reproduce"...

Just search as normal. I think it is related to the data, but I didn't find float type from the data.

What you are saying would imply that this is happening with any spans, for all users. That's clearly not the case, as this is the first time we hear about this. Please, provide instructions on how to reproduce it, otherwise, we cannot figure out how to fix it...

What you are saying would imply that this is happening with any spans, for all users. That's clearly not the case, as this is the first time we hear about this. Please, provide instructions on how to reproduce it, otherwise, we cannot figure out how to fix it...

Now I'm not sure what caused this error. And I don't know how to help you reproduce it without my data. I tried to figure out the different of the data, but failed.

Sorry, there's not much we can do without a reproducer. I'll leave this open for a couple of days, in case any of the other maintainers have an idea on what might be going on.

Sorry, there's not much we can do without a reproducer. I'll leave this open for a couple of days, in case any of the other maintainers have an idea on what might be going on.

I found the cause may be that using java client to save the span with the tag value of Double.MAX_VALUE. Then I found the value in ES is 1.797693135e+308, but the float64 max is 1.7976931348623157e+308,  it is round up, so it out of range.

That's a great hint.

I think is caused by this line:
https://github.com/jaegertracing/jaeger/blob/0a889e8ea7ca887f30eaa814456d86ad97be3f8e/model/keyvalue.go#L145

I think this fixes it, but there's one other FormatFloat with 10 which should be looked at too:
cmd/opentelemetry/app/exporter/elasticsearchexporter/esmodeltranslator/modeltranslator.go:		tag.Value = strconv.FormatFloat(attr.DoubleVal(), 'g', 10, 64)

diff --git a/model/keyvalue.go b/model/keyvalue.go
index 44f3e1b..9ca28fd 100644
--- a/model/keyvalue.go
+++ b/model/keyvalue.go
@@ -142,7 +142,7 @@ func (kv *KeyValue) asString(truncate bool) string {
        case Int64Type:
                return strconv.FormatInt(kv.Int64(), 10)
        case Float64Type:
-               return strconv.FormatFloat(kv.Float64(), 'g', 10, 64)
+               return strconv.FormatFloat(kv.Float64(), 'g', -1, 64)
        case BinaryType:
                if truncate && len(kv.VBinary) > 256 {
                        return hex.EncodeToString(kv.VBinary[0:256]) + "..."
diff --git a/model/keyvalue_test.go b/model/keyvalue_test.go
index d7af48f..542562a 100644
--- a/model/keyvalue_test.go
+++ b/model/keyvalue_test.go
@@ -17,6 +17,7 @@ package model_test

 import (
        "bytes"
+       "strconv"
        "testing"

        "github.com/stretchr/testify/assert"
@@ -56,6 +57,14 @@ func TestKeyValueFloat64(t *testing.T) {
        assert.Equal(t, 123.345, kv.Float64())
 }

+func TestKeyValueFloat64RoundTrippable(t *testing.T) {
+       kv := model.Float64("x", 1.7976931348623157e+308)
+       str := kv.AsString()
+       _, err := strconv.ParseFloat(str, 64)
+
+       assert.Nil(t, err, "AsString should be parseable with ParseFloat")
+}
+
 func TestKeyValueBinary(t *testing.T) {
        kv := model.Binary("x", []byte{123, 45})
        assert.Equal(t, "x", kv.Key)
@@ -125,7 +134,7 @@ func TestKeyValueAsStringAndValue(t *testing.T) {
                {kv: model.Bool("x", true), str: "true", val: true},
                {kv: model.Int64("x", 3000), str: "3000", val: int64(3000)},
                {kv: model.Int64("x", -1947), str: "-1947", val: int64(-1947)},
-               {kv: model.Float64("x", 3.14159265359), str: "3.141592654", val: float64(3.14159265359)},
+               {kv: model.Float64("x", 3.14159265359), str: "3.14159265359", val: float64(3.14159265359)},
                {kv: model.Binary("x", []byte("Bender")), str: "42656e646572", val: []byte("Bender")},
                {kv: model.Binary("x", []byte(longString)), str: expectedBinaryStr, val: []byte(longString)},
                {kv: model.Binary("x", []byte(longString)), strLossy: expectedBinaryStrLossy, val: []byte(longString)},

Also, I'm not sure if there are any more compatibility issues to consider. What is the specification of this format?


Fixes issue with the data model not always correctly being updated

When for example using the change/edit link buttons in the toolbar of tinymce the data model did not always get updated. This solves this issue by using the 'change' event instead of the 'KeyUp' and 'SetContent' events.

After doing some investigation, listening for just the change event is not what we want, since saving executes a change event.
Check out my commit in order to see the granularity I added

Great, thanks a lot for further investigating this!


[VL] CI: fix boost download

What changes were proposed in this pull request?
fix boost download, the jfrog repo is invalid since last weekend
How was this patch tested?
pass GHA

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_4313_time.csv
log/native_master_01_07_2024_6518d7633_time.csv
difference
percentage

q1
35.11
31.72
-3.396
90.33%

q2
25.83
25.39
-0.448
98.26%

q3
38.94
38.29
-0.653
98.32%

q4
39.30
39.22
-0.087
99.78%

q5
70.97
71.41
0.447
100.63%

q6
6.66
7.14
0.482
107.23%

q7
86.90
86.73
-0.167
99.81%

q8
87.33
86.53
-0.794
99.09%

q9
125.97
123.34
-2.636
97.91%

q10
42.56
42.30
-0.266
99.37%

q11
19.42
19.35
-0.071
99.63%

q12
27.37
25.36
-2.006
92.67%

q13
46.30
46.61
0.309
100.67%

q14
16.10
17.18
1.078
106.70%

q15
27.79
29.40
1.614
105.81%

q16
15.15
15.21
0.056
100.37%

q17
157.09
155.97
-1.128
99.28%

q18
193.10
197.47
4.370
102.26%

q19
17.40
16.59
-0.808
95.36%

q20
28.32
26.56
-1.760
93.78%

q21
223.46
227.35
3.895
101.74%

q22
13.85
14.12
0.267
101.93%

total
1344.93
1343.22
-1.702
99.87%


Update datastream file fixtures

I'm expecting tests to fail here. @xprazak2 you wrote some of the failing validations - I wonder if you based the namespace requirement on the SCAP spec or just from an example datastream file? These three datastreams were downloaded from the ComplianceAsCode repo's latest release: https://github.com/ComplianceAsCode/content/releases/download/v0.1.46/scap-security-guide-0.1.46.zip
None of the three are 'valid' as written:
[1] pry(#<DsTest>)> create_parser('ssg-rhel7-ds.xml').valid?
=> false
[2] pry(#<DsTest>)> create_parser('ssg-rhel6-ds.xml').valid?
=> false
[3] pry(#<DsTest>)> create_parser('ssg-rhel8-ds.xml').valid?
=> false

Signed-off-by: Andrew Kofink<EMAIL_ADDRESS>

It does, but the validation looking for namespaces still fails. I need to figure this out.

@akofink, I just took it from the file. The check is failing because the new file contains completely different namespaces:

maybe because scap-version changed to 1.3?

Right, so my question is about the namespaces. Why did we add the validations there? Is it okay to remove the namespace validation now?

I think you can remove them if it helps you move forward. I wanted some basic check that the file is really what we expect so I added validations for namespaces, because I did not think they would change.

Finally updated. The list of profiles was missing one for xccdf_org.ssgproject.content_profile_pci-dss_centric which has the same title as xccdf_org.ssgproject.content_profile_pci-dss.

Rebased


[typescript]makeStyles hook + props = problems

I have problems using makeStyles with props in typescript.

[X] This is not a v0.x issue.
[X] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔
Sample:
import * as React from "react";
import { render } from "react-dom";
import { createMuiTheme } from "@material-ui/core/styles";
import { ThemeProvider } from "@material-ui/styles";
import Button from "@material-ui/core/Button";
import { makeStyles } from "@material-ui/styles";

type TProps = {
  color: string;
};

const useStyles = makeStyles({
  root: (mProp: TProps) => ({ background: mProp.color })
});

function Page(mProp: TProps) {
  const _classes = useStyles(mProp);
  return <Button className={_classes.root}>Ok</Button>;
}

const theme = createMuiTheme({ typography: { useNextVariants: true } });

render(
  <ThemeProvider theme={theme}>
    <Page color="red" />
  </ThemeProvider>,
  document.getElementById("root")
);

A red background button :)
Current Behavior 😯
Runtime error:
node_modules/jss-plugin-rule-value-function/dist/jss-plugin-rule-value-function.esm.js:10
   7 | return {
   8 |   onCreateRule: function onCreateRule(name, decl, options) {
   9 |     if (typeof decl !== 'function') return null;
> 10 |     var rule = createRule(name, {}, options);
  11 |     rule[fnRuleNs] = decl;
  12 |     return rule;
  13 |   },

I really think it's related to different JSS version between core and styles...
Steps to Reproduce 🕹

Link:

fresh create-react-app typescript
update react, react-node
install material-ui/core, material-ui/styles
index.tsx

Context 🔦

Your Environment 🌎

Tech
Version

Material-UI/core
v3.9.0

Material-UI/styles
v3.0.0-alpha.8

React
v16.8.0-alpha.0

React-dom
v16.8.0-alpha.0

TypeScript
v3.2.2

Another thing I don't understand is the same sample work in codesandbox (runtime transpiling ?)...

I am having this same issue, it is not resolved.  It is making it to where it is impossible to write an app using the props within the styling.

@Guardiannw The original issue was mainly at runtime and cause by a wrong node_modules/ layout. Have you tried switching to yarn as the original author did to resolve this issue?

Unfortunately, our project cannot easily switch to yarn.  Is material-ui only usable with yarn?

Unfortunately, our project cannot easily switch to yarn. Is material-ui only usable with yarn?

No but it looks like you encountered a bug with npm. This might happen regardless of material-ui usage.

Ok, posted the issue here: https://npm.community/t/npm-vs-yarn-folder-structure-problems/5203.  We will see what happens.


[AutoPR trafficmanager/resource-manager] Do not omit type and name while serializing the resource object.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4007

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2899


Not able to download files

When I try to download a folder which is above 10-15MB, it will start to download and after a few seconds download will fail saying Network Error. Not sure what is the issue, is there a cap on the size of zip file download?
PS. Jupyter notebooks are hosted on Kubernetes.

The issue was with the k8s ambassador, it was timing out and stopping the download. Resolved by disabling the timeout.