Bad block breaks geth

I've started running firehose and I just ran into the following log lines which seems to have broken geth - it's now reporting that a Disk Quota has been been exceeded:
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"WARNING","timestamp":"2022-10-31T15:23:24.478946191-04:00","logger":"reader.geth","message":"beacon chain gapped                      head=15,869,849 newHead=15,869,855","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:24.478990291-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:24.477] Failed to clean stale beacon headers     err=\"filled header below beacon header tail: 6158489 < 15869849\"","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:24.693057822-04:00","logger":"reader.geth","message":"unindexed transactions                   blocks=439 txs=55767 tail=6,158,362 elapsed=227.838ms","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"WARNING","timestamp":"2022-10-31T15:23:24.880649279-04:00","logger":"reader","message":"failed to upload file","error":"moving file \"0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default\" to storage: open file: open /data/firehose/reader/work/uploadable-oneblock/0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default.dbin.zst: disk quota exceeded","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:25.332971157-04:00","logger":"reader.geth","message":"syncing beacon headers                   downloaded=1540 left=6,158,488 eta=550h18m24.979s","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"WARNING","timestamp":"2022-10-31T15:23:25.382861547-04:00","logger":"reader","message":"failed to upload file","error":"moving file \"0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default\" to storage: open file: open /data/firehose/reader/work/uploadable-oneblock/0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default.dbin.zst: disk quota exceeded","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:25.518788928-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:25.518] Expired request does not exist           peer=e053914017a506772cce70913eac44cc9b0e4378adc138f6f11b7c943fe5acbf","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"WARNING","timestamp":"2022-10-31T15:23:25.884820224-04:00","logger":"reader","message":"failed to upload file","error":"moving file \"0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default\" to storage: open file: open /data/firehose/reader/work/uploadable-oneblock/0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default.dbin.zst: disk quota exceeded","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:25.955989251-04:00","logger":"reader.geth","message":"downloader queue stats                   receiptTasks=0 blockTasks=34168 itemSize=27.24KiB throttle=8192","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.036932293-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.036] Unhandled trie error: missing trie node 4cdf3958a41d42a048cb37085d0e2450f3a92074a99d446ab4dd7b48cfd190ab (path 03070b030e0c04) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.212740567-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.212] Unhandled trie error: missing trie node 164b4f0699da01839785857cce9e614559afc9a569c10b3e82254db1abb7d16b (path 09090b0f0d04) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.259208341-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.259] Unhandled trie error: missing trie node 164b4f0699da01839785857cce9e614559afc9a569c10b3e82254db1abb7d16b (path 09090b0f0d04) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.268408351-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.268] Unhandled trie error: missing trie node 7217e48235c2c5bed47a4bc25418e952db40c64433424ea1f99b44669000b375 (path 09090e00010900) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.28229091-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.282] Unhandled trie error: missing trie node 7217e48235c2c5bed47a4bc25418e952db40c64433424ea1f99b44669000b375 (path 09090e00010900) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.287387822-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.283] Unhandled trie error: missing trie node ca4cbcd5f6e09f53c448cc68a9b452ce669a25a9eed0f22a79a4e07d4a07bae3 (path 07010e090b0f08) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.287431338-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.284] Unhandled trie error: missing trie node ca4cbcd5f6e09f53c448cc68a9b452ce669a25a9eed0f22a79a4e07d4a07bae3 (path 07010e090b0f08) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.30427221-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.304] Unhandled trie error: missing trie node b60717f155b92939dc3387492394afd09912678a26923af5d2c4e5e315c913f2 (path<PHONE_NUMBER>0e03) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.30760353-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.306] Unhandled trie error: missing trie node b60717f155b92939dc3387492394afd09912678a26923af5d2c4e5e315c913f2 (path<PHONE_NUMBER>0e03) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.30780068-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.307] Unhandled trie error: missing trie node 0936e560feba21cfd5ca6686193ede797b4c4a1818436703888696343c38b086 (path 0c09040909020b) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.30991422-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.309] Unhandled trie error: missing trie node 0936e560feba21cfd5ca6686193ede797b4c4a1818436703888696343c38b086 (path 0c09040909020b) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.311182544-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.311] Unhandled trie error: missing trie node da95e202db5dadb272aba88d218c26038af5e437514fa80e3f116f60d50cc4f5 (path 0c0a00030108) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.312121839-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.312] Unhandled trie error: missing trie node da95e202db5dadb272aba88d218c26038af5e437514fa80e3f116f60d50cc4f5 (path 0c0a00030108) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"WARNING","timestamp":"2022-10-31T15:23:26.393611317-04:00","logger":"reader","message":"failed to upload file","error":"moving file \"0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default\" to storage: open file: open /data/firehose/reader/work/uploadable-oneblock/0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default.dbin.zst: disk quota exceeded","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.40731312-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.407] Unhandled trie error: missing trie node d460e787b2bfc6b3683c49698b51115ee39bc01ed3211d86d2e2972c0237d6ad (path 06040e090b050b00) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.408046113-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.407] Unhandled trie error: missing trie node d460e787b2bfc6b3683c49698b51115ee39bc01ed3211d86d2e2972c0237d6ad (path 06040e090b050b00) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.408799923-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.408] Unhandled trie error: missing trie node d460e787b2bfc6b3683c49698b51115ee39bc01ed3211d86d2e2972c0237d6ad (path 06040e090b050b00) <nil> ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose FAILED trx "a9cb5b1c828218ee6a334dc9d48ed2c9367f6f35fbb644a1d66c4178056b1927" at block 6158490 (hash unavailable, probably forked): insufficient funds for gas * price + value: address 0x80f2b4ff20c8Ff8835cb815094E91E5b0120CD0B have 0 want<PHONE_NUMBER>4347515 2472
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410209421-04:00","logger":"reader.geth","message":"skip duplicated bad block                number=6,158,490  hash=b6e729..3720d4","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.410320327-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.410] ","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410359297-04:00","logger":"reader.geth","message":"########## BAD BLOCK #########","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410375414-04:00","logger":"reader.geth","message":"chain config: Chain ID:  1 (mainnet)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410387081-04:00","logger":"reader.geth","message":"consensus: Beacon (proof-of-stake), merged from Ethash (proof-of-work)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410399144-04:00","logger":"reader.geth","message":"pre-Merge hard forks:","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.41041168-04:00","logger":"reader.geth","message":" - Homestead:                   1150000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/homestead.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410424045-04:00","logger":"reader.geth","message":" - DAO Fork:                    1920000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/dao-fork.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410451966-04:00","logger":"reader.geth","message":" - Tangerine Whistle (EIP 150): 2463000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/tangerine-whistle.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410467232-04:00","logger":"reader.geth","message":" - Spurious Dragon/1 (EIP 155): 2675000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/spurious-dragon.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.41047902-04:00","logger":"reader.geth","message":" - Spurious Dragon/2 (EIP 158): 2675000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/spurious-dragon.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410490538-04:00","logger":"reader.geth","message":" - Byzantium:                   4370000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/byzantium.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410502395-04:00","logger":"reader.geth","message":" - Constantinople:              7280000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/constantinople.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410515128-04:00","logger":"reader.geth","message":" - Petersburg:                  7280000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/petersburg.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410528678-04:00","logger":"reader.geth","message":" - Istanbul:                    9069000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/istanbul.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410545419-04:00","logger":"reader.geth","message":" - Muir Glacier:                9200000  (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/muir-glacier.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.41057709-04:00","logger":"reader.geth","message":" - Berlin:                      12244000 (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/berlin.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410593931-04:00","logger":"reader.geth","message":" - London:                      12965000 (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/london.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410607918-04:00","logger":"reader.geth","message":" - Arrow Glacier:               13773000 (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/arrow-glacier.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.4106357-04:00","logger":"reader.geth","message":" - Gray Glacier:                15050000 (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/gray-glacier.md)","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.41065043-04:00","logger":"reader.geth","message":"merge configured:","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410661111-04:00","logger":"reader.geth","message":" - Hard-fork specification:    https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/paris.md","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.41067195-04:00","logger":"reader.geth","message":" - Network known to be merged: true","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410682275-04:00","logger":"reader.geth","message":" - Total terminal difficulty:<PHONE_NUMBER>0000000000000","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410693105-04:00","logger":"reader.geth","message":" - Merge netsplit block:       <nil>","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410704011-04:00","logger":"reader.geth","message":"number: 6158490","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.41072913-04:00","logger":"reader.geth","message":"hash: 0xb6e729d033a32968a21450a3408c8b5ab4566e0c5e1bd112017519d21b3720d4","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410747068-04:00","logger":"reader.geth","message":"error: could not apply tx 113 [0xa9cb5b1c828218ee6a334dc9d48ed2c9367f6f35fbb644a1d66c4178056b1927]: insufficient funds for gas * price + value: address 0x80f2b4ff20c8Ff8835cb815094E91E5b0120CD0B have 0 want<PHONE_NUMBER>4347515","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410762094-04:00","logger":"reader.geth","message":"##############################","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.410772044-04:00","logger":"reader.geth","message":" ","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"ERROR","timestamp":"2022-10-31T15:23:26.410808153-04:00","logger":"reader.geth","message":"eRROR[10-31|15:23:26.410] Beacon backfilling failed                err=\"retrieved hash chain is invalid: could not apply tx 113 [0xa9cb5b1c828218ee6a334dc9d48ed2c9367f6f35fbb644a1d66c4178056b1927]: insufficient funds for gas * price + value: address 0x80f2b4ff20c8Ff8835cb815094E91E5b0120CD0B have 0 want<PHONE_NUMBER>4347515\"","logging.googleapis.com/labels":{},"serviceContext":{"service":"unknown"}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"INFO","timestamp":"2022-10-31T15:23:26.874415245-04:00","logger":"index-builder","message":"reading from blocks store: file does not (yet?) exist, retrying in","filename":"merged-blocks/0006158300.dbin.zst","base_filename":"0006158300","retry_delay":4,"logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"WARNING","timestamp":"2022-10-31T15:23:26.896155225-04:00","logger":"reader","message":"failed to upload file","error":"moving file \"0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default\" to storage: open file: open /data/firehose/reader/work/uploadable-oneblock/0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default.dbin.zst: disk quota exceeded","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"WARNING","timestamp":"2022-10-31T15:23:27.399447259-04:00","logger":"reader","message":"failed to upload file","error":"moving file \"0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default\" to storage: open file: open /data/firehose/reader/work/uploadable-oneblock/0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default.dbin.zst: disk quota exceeded","logging.googleapis.com/labels":{}}
firehose-mainnet-7457c6d7f7-5w7pk firehose {"severity":"WARNING","timestamp":"2022-10-31T15:23:27.901626774-04:00","logger":"reader","message":"failed to upload file","error":"moving file \"0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default\" to storage: open file: open /data/firehose/reader/work/uploadable-oneblock/0006158489-8057bdc930322e92-016b7dd2cfb0000c-6158289-default.dbin.zst: disk quota exceeded","logging.googleapis.com/labels":{}}

Is this a known issue? Could it be that my geth instance isn't syncing properly? Might the bad block be a red herring for the disk quota error?

Not sure why Geth is not happy, everything flagged "logger":"reader.geth" is coming from Geth directly. Bad block indicates something really bad. The insufficient space might have cause this indeed.
Fix the space issue, rewind head earlier and try again. Not really a firehose-ethereum issue directly.

weird, restarting firehose seems to have solved the issue, at least temporarily. Will keep an eye on this and see if it comes back.
I've tried geth attaching to the new instance, and it seems I'm now at block 6158574:
> root@firehose-mainnet-7457c6d7f7-t6m26:/# geth attach /data/firehose/reader/ipc
INFO [10-31|15:43:18.537] Initializing firehose
INFO [10-31|15:43:18.556] Firehose initialized                     enabled=false sync_instrumentation_enabled=true mining_enabled=false block_progress_enabled=false compaction_disabled=false archive_blocks_to_keep=0 genesis_provenance="Geth Default" firehose_version=2.0 geth_version=1.10.25-fh2 chain_variant=geth
Welcome to the Geth JavaScript console!

instance: Geth/v1.10.25-fh2-67d4fa90/linux-amd64/go1.18.5
at block: 6158571 (Thu Aug 16 2018 11:46:38 GMT-0400 (EDT))
 datadir: /data/firehose/reader/data
 modules: admin:1.0 debug:1.0 engine:1.0 eth:1.0 ethash:1.0 miner:1.0 net:1.0 personal:1.0 rpc:1.0 txpool:1.0 web3:1.0

To exit, press ctrl-d or type exit
> eth.syncing
{
  currentBlock: 6158574,
  healedBytecodeBytes: 0,
  healedBytecodes: 0,
  healedTrienodeBytes: 0,
  healedTrienodes: 0,
  healingBytecode: 0,
  healingTrienodes: 0,
  highestBlock: 15870156,
  startingBlock: 6158488,
  syncedAccountBytes: 0,
  syncedAccounts: 0,
  syncedBytecodeBytes: 0,
  syncedBytecodes: 0,
  syncedStorage: 0,
  syncedStorageBytes: 0
}

yeah, looks like the disk space was an issue and the bad block was a symptom of that. I had causality reversed.


HA - Error doing job: Task exception was never retrieved

First - Thank you for your work.  I am in the testing phases currently with Home Assistant (hass.io).  Things seem to be working but my home-assistant.log is filling up with this (about every 2 sec)...
2018-04-05 22:51:50 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/components/mqtt/__init__.py", line 594, in _async_perform_subscription
    _raise_on_error(result)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/mqtt/__init__.py", line 680, in _raise_on_error
    'Error talking to MQTT: {}'.format(mqtt.error_string(result_code)))
homeassistant.exceptions.HomeAssistantError: Error talking to MQTT: The client is not currently connected.

After about 5-10min then GarHAge functionally stops and I have to cycle the NodeMCU which starts the process all over again.  I switched to your 'fixed' branch to see if that fixed it and also added/removed the automations.yaml configuration but no go.  I am using 'cover' method.
Have you seen this?  Any ideas you have would be appropriated.
Thanks again!

I haven't seen this particular error but I am very sure that it has nothing to do with GarHAge. No MQTT client should care whether another MQTT client is connected: Home Assistant connects to the broker and reads the topics and messages that get delivered to it regardless whether GarHAge is also connected to the broker.
What this looks like instead is that your Home Assistant instance is losing its own connection to your MQTT broker: the error is "Error talking to MQTT: The client is not currently connected." The client that message is referring to is Home Assistant's MQTT client functionality. You'll need to troubleshoot what's going on with HA to cause this. Some things to consider to start:

What broker are you using? Is it HA's built-in broker, or a Hass.io add-on, or a separate server altogether?
If the broker is an add-on or separate server, what does your configuration.yaml mqtt: configuration look like?


REGARDING FOLDER CONECT

Type: Bug
Actually when it open and showing the option "start"
below start there are three sub option new file , open flle , open folder .
When I select the option "open folder " then my files opening and select my coding folder but it is not opening or connecting to app before this all thing is fine .
please solve my issue .
VS Code version: Code 1.76.2 (ee2b180d582a7f601fa6ecfdad8d9fd269ab1884, 2023-03-14T17:55:54.936Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
AMD Ryzen 5 5600H with Radeon Graphics          (12 x 3294)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
7.35GB (1.00GB free)

Process Argv
C:\Users\Deves\OneDrive\Desktop\coding\c\loop\while.c --crash-reporter-id 084714dc-e300-409f-93f9-846c57646d22

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

prettier-vscode
esb
9.10.4

code-runner
for
0.12.0

cmake-tools
ms-
1.13.45

cpptools
ms-
1.14.5

cpptools-extension-pack
ms-
1.3.0

cmake
twx
0.0.17

intellicode-api-usage-examples
Vis
0.2.7

vscode-java-debug
vsc
0.49.0

vscode-java-dependency
vsc
0.21.1

vscode-maven
vsc
0.40.4

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848:30662994
nodejswelcome1:30587005
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
vsctsb:30677850
defaultazurewalk:30687958
pythonms35cf:30686773

bug

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


安装报错。

安装报错:

root@VM-102-99-debian:~# pip install tickets
Downloading/unpacking tickets
Could not find any downloads that satisfy the requirement tickets
No distributions at all found for tickets
Storing complete log in /root/.pip/pip.log

查看log文件:

root@VM-102-99-debian:~# cat /root/.pip/pip.log

/usr/bin/pip run on Sat Jun 11 21:57:15 2016
Downloading/unpacking tickets

Getting page http://pypi.python.org/simple/tickets
URLs to search for versions for tickets:

http://pypi.python.org/simple/tickets/
Getting page http://pypi.python.org/simple/tickets/
Analyzing links from page https://pypi.python.org/simple/tickets/
Skipping link https://pypi.python.org/packages/79/bf/27ec9203a03d95e53d9ea530a1a3130c7e661a419c08fd98c16eca4e8797/tickets-0.1-py2-none-any.whl#md5=c75da25678bcbed13795eccff7eebd66 (from https://pypi.python.org/simple/tickets/); unknown archive format: .whl
Could not find any downloads that satisfy the requirement tickets

No distributions at all found for tickets

Exception information:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 104, in main
status = self.run(options, args)
File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 245, in run
requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, bundle=self.bundle)
File "/usr/lib/python2.7/dist-packages/pip/req.py", line 978, in prepare_files
url = finder.find_requirement(req_to_install, upgrade=self.upgrade)
File "/usr/lib/python2.7/dist-packages/pip/index.py", line 157, in find_requirement
raise DistributionNotFound('No distributions at all found for %s' % req)
DistributionNotFound: No distributions at all found for tickets

我的系统是debian 7 32位:

root@VM-102-99-debian:~# cat /etc/debian_version
7.10
python 版本是2.7

root@VM-102-99-debian:~# python --version
Python 2.7.3

好吧，手动安装了requests,docopt和 prettytable 后正常安装了。
pip install requests docopt prettytable

@xtheo 运行正常吗?

运行一切正常。谢谢你！


Make Map<> movable

Extracted from https://github.com/grpc/grpc/pull/19390.

Please grab the additional tests in map_test.cc from the other PR as well.  Thanks!

Oops, missed that part. Thanks!

I'm going to merge this so that I can sync the changes into #19390.
Known issues: #19614 #19422 #19755


Windows 10 compatibility

Hello 👋, is the plugin supposed to work under windows? This line seems to break the gradle build as uname is not a Windows command.
my project build.gradle.kts
plugins {
    id("com.automattic.android.measure-builds") version "3.0.0"
}

measureBuilds {
    enable = true
}

The error I got
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'XXXXX'.
> A problem occurred starting process 'command 'uname''

Thanks for the response

Ideally, we should have CI testing for Windows.
However, I think it's better to use a try-catch block at least, instead of allowing the program to crash.

hi there @PremyslTalich 👋 Thanks for the report - indeed, the plugin wasn't tested on Windows. We should support this OS as well.
@takahirom good point - I plan to add OS matrix on CI, and it'll be better to have try-catch for this 👍


KeyError in hfstol when searching for strings in quick succession

Internal Server Error: /_search_results/ac/
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner
    response = get_response(request)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/base.py", line 115, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/travis/build/UAlbertaALTLab/cree-intelligent-dictionary/CreeDictionary/CreeDictionary/views.py", line 26, in search_results
    lemmas = Inflection.fetch_lemmas_by_user_query(query_string)
  File "/home/travis/build/UAlbertaALTLab/cree-intelligent-dictionary/CreeDictionary/API/models.py", line 158, in fetch_lemmas_by_user_query
    fst_analyses: Set[str] = descriptive_analyzer.feed_in_bulk_fast([user_query])[
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/hfstol/main.py", line 130, in feed_in_bulk_fast
    return self._call_hfstol(list(strings), multi_process)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/hfstol/main.py", line 214, in _call_hfstol
    results[original_input].add(res)
KeyError: 'a'

the heck. I'm on it.

Here's another example of it:
https://travis-ci.org/UAlbertaALTLab/cree-intelligent-dictionary/jobs/597054345#L386-L402
Internal Server Error: /_search_results/acâhko/
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner
    response = get_response(request)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/base.py", line 115, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/travis/build/UAlbertaALTLab/cree-intelligent-dictionary/CreeDictionary/CreeDictionary/views.py", line 26, in search_results
    lemmas = Inflection.fetch_lemmas_by_user_query(query_string)
  File "/home/travis/build/UAlbertaALTLab/cree-intelligent-dictionary/CreeDictionary/API/models.py", line 158, in fetch_lemmas_by_user_query
    fst_analyses: Set[str] = descriptive_analyzer.feed_in_bulk_fast([user_query])[
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/hfstol/main.py", line 130, in feed_in_bulk_fast
    return self._call_hfstol(list(strings), multi_process)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/hfstol/main.py", line 214, in _call_hfstol
    results[original_input].add(res)
KeyError: 'acâhkos'

It's easily triggered by the integration tests.

https://www.youtube.com/watch?v=_asNhzXq72w

I think I have an idea for a reproducible test case.
Look-up a word with A LOT of possible analyses, e.g., "ôma":
$ pipenv run analyze
Loading .env environment variables…
!! Warning: file contains more than one transducer          !!
!! This is currently not handled - using only the first one !!
ôma
ôma	ôma+Ipc+Foc
ôma	ôma+Pron+Dem+Prox+IN+Sg
ôma	ôma+Pron+Def+Prox+IN+Sg

Then try to look up something else.

fully fixed
https://travis-ci.org/UAlbertaALTLab/cree-intelligent-dictionary/builds/600235228

@Madoshakalaka, I've got bad news for you:
Internal Server Error: /_search_results/acâhk/
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner
    response = get_response(request)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/base.py", line 115, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/travis/build/UAlbertaALTLab/cree-intelligent-dictionary/CreeDictionary/CreeDictionary/views.py", line 31, in search_results
    lemmas = Inflection.fetch_lemmas_by_user_query(query_string)
  File "/home/travis/build/UAlbertaALTLab/cree-intelligent-dictionary/CreeDictionary/API/models.py", line 155, in fetch_lemmas_by_user_query
    fst_analyses: Set[str] = descriptive_analyzer.feed_in_bulk_fast([user_query])[
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/hfstol/main.py", line 131, in feed_in_bulk_fast
    return self._call_hfstol(list(strings), multi_process)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/hfstol/main.py", line 220, in _call_hfstol
    results[original_input].add(res)
KeyError: 'acâhkos'
[22/Oct/2019 17:05:10] "GET /_search_results/ac%C3%A2hk/ HTTP/1.1" 500 115192
      1) should search for an exact lemma
[22/Oct/2019 17:05:14] "GET /search/amisk HTTP/1.1" 301 0
[22/Oct/2019 17:05:14] "GET /search/amisk/ HTTP/1.1" 200 7906
[22/Oct/2019 17:05:14] "GET /jsreverse/ HTTP/1.1" 200 4214
[22/Oct/2019 17:05:14] "GET /static/CreeDictionary/js/index.js HTTP/1.1" 304 0
Internal Server Error: /_search_results/acâhkos/
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner
    response = get_response(request)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/base.py", line 115, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/travis/build/UAlbertaALTLab/cree-intelligent-dictionary/CreeDictionary/CreeDictionary/views.py", line 31, in search_results
    lemmas = Inflection.fetch_lemmas_by_user_query(query_string)
  File "/home/travis/build/UAlbertaALTLab/cree-intelligent-dictionary/CreeDictionary/API/models.py", line 155, in fetch_lemmas_by_user_query
    fst_analyses: Set[str] = descriptive_analyzer.feed_in_bulk_fast([user_query])[
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/hfstol/main.py", line 131, in feed_in_bulk_fast
    return self._call_hfstol(list(strings), multi_process)
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/hfstol/main.py", line 220, in _call_hfstol
    results[original_input].add(res)
KeyError: 'amisk'

https://travis-ci.org/UAlbertaALTLab/cree-intelligent-dictionary/jobs/601387324#L379-L420

What is the underlying bug here? What actually is going wrong?

I disabled the HFSTOL descriptive analyzer so that we have less flakey builds as of 74a6fb0. Since this bug keeps popping back up, I think we should put it on the back-burner, since the slower implementation still works -- it's just slower 🤷♂ .
I've set this as a "future" task, since all the tests pass, and the site work without using hfstol.

very depressing. But sure

I'm marking this as wontfix. Eventually, we'll have to implement an hfstol evaluator that is stable, can be installed without external dependencies via pypi, and does not have weird concurrency bugs!


Not bug - feature request

First, apologies if this is the wrong place.
Please ignore or delete if out of order.
Just thinking... When you CAT or CATALOG a ProDOS disk, locked files have an asterisk to indicate locked status. Now, since DIR files are locked by default, could ProDOS be modified to show a "/" for DIR files where locked files have the asterix?
Like this:
*PRODOS
*BASIC.SYSTEM
START
/DIRECTORY
etc
Just a cosmetic thing that wandered across my mind...

This would actually be helpful visually.


chore(browser): bump modern-node-polyfills

This should fix the vite-ecosystem-ci fail.
https://discord.com/channels/804011606160703521/1098838358660239360/1098884420905226261

Thank you!


Remove use of dyn in multitest Router

for Storage, Api, Querier, we should stick with dyn, as that is what we pass into Deps and we have no real need for more details. For the other, it can be useful to get the original types when setting up test code.
I am talking about:
pub struct Router<ExecC, QueryC> {
    pub(crate) wasm: Box<dyn Wasm<ExecC, QueryC>>,
    pub(crate) bank: Box<dyn Bank>,
    pub(crate) custom: Box<dyn CustomHandler<ExecC, QueryC>>,
}

https://github.com/CosmWasm/cw-plus/blob/mt-msg-handling/packages/multi-test/src/app.rs#L254-L258
I would propose something like the follow:
pub struct Router<ExecC, QueryC, W: Wasm<ExecC, QueryC>, B: Bank, C: CustomHandler<ExecC, QueryC>> {
    pub(crate) wasm: Box<W>,
    pub(crate) bank: Box<B>,
    pub(crate) custom: Box<C>,
}

It would require some changes to the builder pattern (but we have a similar setup in ContractWrapper where we change types during the builder.

Basically I very much like this approach. Two things which I would already note:

If you don't have dyn Traits, you nevermore need boxing - just keep stuff by ownership. You need box to handle unsized types, but there is no need to accept unsized generics.
I really don't like trait bounds in types. They doesn't give anything, but propagates quickly (if I use the type anywhere, I immediately have to add bounds - even if I don't need to use impl of it). Basically I find it way better to add bounds only to impl block (where you have to add it anyway). There is an argumentation that maybe at some point in future implied bounds would be there, but it doesn't look like it would happen anytime soon if ever.

Does this also close https://github.com/CosmWasm/cw-plus/issues/362 in the refactor?
Or is that a separate issue still?


[BUG] Can't retrieve data stored on volume using directions in the documentation

Describe the bug
I want to offline retrieve the data stored in a longhorn volume, because the cluster doesn't exist any more.
I tried to use the directions in the documentation https://longhorn.io/docs/1.6.2/advanced-resources/data-recovery/export-from-replica/ but they don't seem to work.
To Reproduce

Copy replicas directory from offline cluster to local machine
Look at meta data of volume using:

❯ cat pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d/volume.meta
{"Size":8589934592,"Head":"volume-head-001.img","Dirty":true,"Rebuilding":false,"Error":"","Parent":"volume-snap-15d8c57a-eebd-4f53-922b-1e53d570303a.img","SectorSize":512,"BackingFilePath":""}

Run the docker command described in the documentation, to get a new device under /dev/longhorn.

docker run -v /dev:/host/dev -v /proc:/host/proc -v pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d:/volume --privileged longhornio/longhorn-engine:v1.6.2 launch-simple-longhorn pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d<PHONE_NUMBER>

Get the following output, indicating a missing executable called iscsiadm inside the container.

+ set -e
+ mount --rbind /host/dev /dev
+ volume=pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d
+ size=8589934592
+ frontend=
+ '[' -z pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d ']'
+ '[' -z<PHONE_NUMBER> ']'
+ '[' -z ']'
+ echo Use default frontend TGT block device
Use default frontend TGT block device
+ frontend=tgt-blockdev
+ exec longhorn-instance-manager daemon
+ start
+ set +e
+ true
+ /usr/local/bin/grpc_health_probe -addr localhost:8500
time="2024-07-05T15:09:26Z" level=info msg="Storing process logs at path: /var/log/instances"
[longhorn-instance-manager] time="2024-07-05T15:09:26Z" level=info msg="Instance Manager listening to localhost:8500"
status: SERVING
+ [[ 0 -eq 0 ]]
+ echo longhorn instance manager is ready
+ break
+ set -e
longhorn instance manager is ready
+ tgtd -f
+ longhorn-instance-manager process create --name pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-r --binary /usr/local/bin/longhorn --port-count 15 --port-args --listen,localhost: -- replica /volume/ --size<PHONE_NUMBER>
+ tee /var/log/tgtd.log
[longhorn-instance-manager] time="2024-07-05T15:09:26Z" level=info msg="Process Manager: prepare to create process pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-r"
[longhorn-instance-manager] time="2024-07-05T15:09:26Z" level=info msg="Process Manager: created process pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-r"
{
	"name": "pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-r",
	"binary": "/usr/local/bin/longhorn",
	"args": [
		"replica",
		"/volume/",
		"--size",
		"8589934592",
		"--listen",
		"localhost:10000"
	],
	"portCount": 15,
	"portArgs": [
		"--listen,localhost:"
	],
	"processStatus": {
		"state": "starting",
		"errorMsg": "",
		"portStart": 10000,
		"portEnd": 10014
	},
	"deleted": false
}
+ sleep 5
tgtd: iser_ib_init(3431) Failed to initialize RDMA; load kernel modules?
tgtd: work_timer_start(146) use timer_fd based scheduler
tgtd: bs_init(387) use signalfd notification
[pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-r] time="2024-07-05T15:09:26Z" level=info msg="Listening on data server localhost:10001"
[pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-r] time="2024-07-05T15:09:26Z" level=info msg="Listening on gRPC Replica server localhost:10000"
time="2024-07-05T15:09:26Z" level=info msg="Listening on sync agent server localhost:10002"
[pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-r] time="2024-07-05T15:09:26Z" level=info msg="Listening on sync localhost:10002"
[longhorn-instance-manager] time="2024-07-05T15:09:26Z" level=info msg="Process pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-r has started at localhost:10000"
+ longhorn-instance-manager process create --name pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e --binary /usr/local/bin/longhorn --port-count 1 --port-args --listen,localhost: -- controller pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d --frontend tgt-blockdev --replica tcp://localhost:10000
[longhorn-instance-manager] time="2024-07-05T15:09:31Z" level=info msg="Process Manager: prepare to create process pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e"
[longhorn-instance-manager] time="2024-07-05T15:09:31Z" level=info msg="Process Manager: created process pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e"
{
	"name": "pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e",
	"binary": "/usr/local/bin/longhorn",
	"args": [
		"controller",
		"pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d",
		"--frontend",
		"tgt-blockdev",
		"--replica",
		"tcp://localhost:10000",
		"--listen",
		"localhost:10015"
	],
	"portCount": 1,
	"portArgs": [
		"--listen,localhost:"
	],
	"processStatus": {
		"state": "starting",
		"errorMsg": "",
		"portStart": 10015,
		"portEnd": 10015
	},
	"deleted": false
}
[pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e] time="2024-07-05T15:09:31Z" level=info msg="Starting with replicas [\"tcp://localhost:10000\"]"
time="2024-07-05T15:09:31Z" level=info msg="Connecting to remote: localhost:10000"
[pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-r] time="2024-07-05T15:09:31Z" level=info msg="New connection from: <IP_ADDRESS>:59972"
time="2024-07-05T15:09:31Z" level=info msg="Opening volume /volume/, size<PHONE_NUMBER>/512"
[pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e] time="2024-07-05T15:09:31Z" level=info msg="Opening: localhost:10000"
[pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e] time="2024-07-05T15:09:31Z" level=info msg="Adding backend: tcp://localhost:10000"
time="2024-07-05T15:09:31Z" level=info msg="Start monitoring tcp://localhost:10000"
time="2024-07-05T15:09:31Z" level=info msg="Get backend tcp://localhost:10000 revision counter 0"
[pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e] time="2024-07-05T15:09:31Z" level=error msg="Failed to init frontend: device pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d: fail to stop SCSI device: Fail to logout target: Failed to execute: nsenter [--mount=/host/proc/1/ns/mnt --net=/host/proc/1/ns/net iscsiadm --version], output , stderr, nsenter: failed to execute iscsiadm: No such file or directory\n, error exit status 1"
[pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e] 2024/07/05 15:09:31 failed to init frontend: device pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d: fail to stop SCSI device: Fail to logout target: Failed to execute: nsenter [--mount=/host/proc/1/ns/mnt --net=/host/proc/1/ns/net iscsiadm --version], output , stderr, nsenter: failed to execute iscsiadm: No such file or directory
, error exit status 1
[longhorn-instance-manager] time="2024-07-05T15:09:31Z" level=info msg="Process Manager: process pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e error out, error msg: exit status 1"
[longhorn-instance-manager] time="2024-07-05T15:09:31Z" level=info msg="stop waiting for gRPC service of process pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d-e to start at localhost:10015"

Expected behavior
A mountable device should appear under /dev/longhorn/ from which I can retrieve the data stored on the volume.
Support bundle for troubleshooting
Sorry, the cluster doesn't exist any more, but it ran v1.6.0 if that helps.
Environment

Longhorn version: v1.6.0
Impacted volume (PV): pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d and two more
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): ArgoCD using this manifest https://raw.githubusercontent.com/longhorn/longhorn/v1.6.0/deploy/longhorn.yaml
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3s

Number of control plane nodes in the cluster: 3
Number of worker nodes in the cluster: 0

Node config

OS type and version: -
Kernel version: -
CPU per node: 2
Memory per node: 4GB
Disk type (e.g. SSD/NVMe/HDD): -
Network bandwidth between the nodes (Gbps): -

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): VMWare
Number of Longhorn volumes in the cluster: 3

Additional context
After the cluster entered a failing state, because it ran out of resources, we decided to start over instead of trying to fix it.
It was essentially a playground, to gain experience, but the content of this image would still be very useful to retrieve.

failed to execute iscsiadm: No such file or directory
Have you installed open-iscsi on your host?

Thank you for your help. I didn't realize that this program, which is installed to /usr/bin/iscsiadm (which is not mounted into the container), has to be installed on the host, but installing open-iscsi and starting its associated service with systemctl start iscsid.service on my Arch Linux host system, made the creation of the device succeed.
Unfortunately, I still can't access the content, because I can't mount it.
When I try to run mount -o ro /dev/longhorn/pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d /mnt I get the error:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/longhorn/pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.

and dmesg says
[31769.344872] FAT-fs (sdd): bogus number of reserved sectors
[31769.344880] FAT-fs (sdd): Can't find a valid FAT filesystem

Running a file system check with fsck /dev/longhorn/pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d returns:
fsck from util-linux 2.40.2
e2fsck 1.47.1 (20-May-2024)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/longhorn/pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Am I still doing something wrong?

Is it an ext4 filesystem or xfs?

I didn't change the default set in https://raw.githubusercontent.com/longhorn/longhorn/v1.6.0/deploy/longhorn.yaml so it should be an ext4 file system, but when I run a few of the these commands https://unix.stackexchange.com/questions/53542/how-to-determine-the-filesystem-of-an-unmounted-device , none of them are able to detect the file system that is actually used.
blkid ignores the device and parted only outputs this for the longhorn device.
Error: /dev/sdd: unrecognised disk label
Model: IET VIRTUAL-DISK (scsi)
Disk /dev/sdd: 1074MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Also, explicitly passing the file system to the mount command with -t ext4 also doesn't work:
mount -t ext4 -o ro /dev/longhorn/pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/longhorn/pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.

and the dmesg output is:
[76955.196452] EXT4-fs (sdd): VFS: Can't find ext4 filesystem

So it seems that the content of the disk image is completely broken or I am still doing something wrong.

So it seems that the content of the disk image is completely broken or I am still doing something wrong.

It seems yes. Do you have other replicas?

On my local machine I have 3 images of 3 different volumes, if I am doing everything correctly, it seems all of them are broken.
There should still be the replicas from the other nodes, which I could retrieve to try the same. I will try that and come back to you.
I am just wondering, what's the probability that 3 out of 3 volumes from one node are broken as opposed to me still messing something up.
Anyway, thank you for your help so far.

Ok, now I am sure I am doing something wrong. We were able to spin up the old cluster on another machine, with the same IP addresses, even rolled back to a working state. So I even have access to the longhorn dashboard. I checked the application relying on the volume, and it works, so I know the data is ok, although the dashboard tells me the volume is degraded, because the replica on one node seems to be broken.
So now I copied the volume directory to my local machine using scp from one of the good nodes. I even created a snapshot of the volume before doing that, to ensure I have a consistent state, because during the copying, the data could change, because I didn't shut down the pods.
And again, I get the exact same error.
Is it possible the filesystem of the volume got corrupted, because I didn't shut down the pod accessing it? If yes, is it possible to directly mount a snapshot of the volume instead of the current state of the volume to avoid that? When I look into the snapshots metadata information I don't get information about size, which is necessary for the docker command.
Now that the cluster is up again, maybe there is a way to circumvent longhorn altogether to rescue the data.

Ok, I finally got it.
I mounted the volume on one working node of the restored cluster with sudo mount /dev/longhorn/pvc-b7be9fee-a85a-4443-a938-232adf2cc3fa-6f3f286d /mnt and then I rsynced the data to the new cluster.
Unfortunately, I was never able to mount a downloaded volume on my local machine, given the manual in the documentation.
Thank you for your help anyway!


bug(material/stepper): ExpressionChangedAfterItHasBeenCheckedError. Previous value: 'stepControl: undefined'. Current value: 'stepControl: [object Object]'

Error:
I got below error on below action.
Action: while initializes the first step of stepper.
Error:
ERROR Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'stepControl: undefined'. Current value: 'stepControl: [object Object]'
This console error is not breaking the UI but need to remove this as this is not the good practice
Angular version.
"@angular/material": "^8.2.3"
"@angular/cli": "^8.3.9",
Code Snippet:
<mat-horizontal-stepper [linear]="true" #stepper labelPosition="bottom">
  <ng-template matStepperIcon="edit">
    <mat-icon>done</mat-icon>
  </ng-template>
  <mat-step [stepControl]="firstStepComponent.firstFormGroup">
    <ng-template matStepLabel class="mat-step-label">First Step</ng-template>

First Step

        <app-first-step [source]="test.source" (resetFunction)="restFunction()"
          (afterSelection)="save($event)" (goToNextStep)="nextStep()">
        </app-first-step>

  </mat-step>
  <mat-step [stepControl]="secondStep.secondGroupWrapper" [optional]="isOptional">
    <ng-template matStepLabel class="mat-step-label">Second Step</ng-template>

Second Step (Optional)

        <app-second-step [selectedFilters]="test.filter" [source]="test.source"
          (resetData)="resetData($event)"></app-second-step>

  </mat-step>

Can you post a Stackblitz that shows the issue? It's hard to tell what is going on purely from the markup.

I'm also having a similar issue. I'm trying to use 2 Forms inside a child component.
@crisbeto https://stackblitz.com/edit/angular-ivy-xvxwdq
I'm also getting an error  ERROR Error: Cannot read property '_syncPendingControls' of null when trying to submit the form.

This is still driving me crazy trying to figure out how to do this in an "atomic" way.
Passing the FormGroup seems to be bad practice. Moving the FormGroups to the Stepper parent would mean that the child components wouldn't "work" on their own without the FormGroup being passed to it (unnecessary bootstrapping).
Currently I'm using Outputs to pass an event to go .previous() or .next() on the stepper, but this loses the Stepper .reset() functionality which is really useful. And adding more Inputs and Outputs to reset every form in each steps seems like a lot more hassle.
Are there any more examples of how to use the stepper with child components?

Error:
I got below error on below action.
Action: while initializes the first step of stepper.
Error:
ERROR Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'stepControl: undefined'. Current value: 'stepControl: [object Object]'
This console error is not breaking the UI but need to remove this as this is not the good practice
Angular version.
"@angular/material": "^8.2.3"
"@angular/cli": "^8.3.9",
Code Snippet:
<mat-horizontal-stepper [linear]="true" #stepper labelPosition="bottom">
  <ng-template matStepperIcon="edit">
    <mat-icon>done</mat-icon>
  </ng-template>
  <mat-step [stepControl]="firstStepComponent.firstFormGroup">
    <ng-template matStepLabel class="mat-step-label">First Step</ng-template>

First Step

        <app-first-step [source]="test.source" (resetFunction)="restFunction()"
          (afterSelection)="save($event)" (goToNextStep)="nextStep()">
        </app-first-step>

  </mat-step>
  <mat-step [stepControl]="secondStep.secondGroupWrapper" [optional]="isOptional">
    <ng-template matStepLabel class="mat-step-label">Second Step</ng-template>

Second Step (Optional)

        <app-second-step [selectedFilters]="test.filter" [source]="test.source"
          (resetData)="resetData($event)"></app-second-step>

  </mat-step>

This issue can be solved simply by injecting into the constructor private cdRef: ChangeDetectorRef
And in the ngAfterViewInit cycle hook just call the method detectChanges()
ngAfterViewInit(): void { this.cdRef.detectChanges(); }


Adds a useful error message

Desciption:
if we make a typo in an app name we get an empty error message:
Validating arguments... done.
Creating new test run... failed.
Error:

This PR fixes that problem. We'll see the message
The app name was not found for the provided org name

Done - I made a slight change because the app might exist within a user account rather than an org. We could split this logic out so that the message is different if it's an org account but that seemed like overkill.
Owens-MBP:appcenter-cli owenniblock$ ts-node src/index.ts test run uitest --app "Niblock-Org/org-app" --devices 1100f5c0 --app-path /Users/owenniblock/Downloads/clear-text-run-files.tar/workspace/resigned_app.ipa  --test-series "master" --locale "en_US" --build-dir /Users/owenniblock/Downloads/UIAutomation/bin/Debug
Preparing tests... done.
Validating arguments... done.
Creating new test run... failed.
Error: The app named org-app does not exist in the organization or user: Niblock-Org

Further error details: For help, please send both the reported error above and the following environment information to us by going to https://appcenter.ms/apps and starting a new conversation (using the icon in the bottom right corner of the screen)

    Environment: darwin
    App Upload Id: Niblock-Org/org-app
    Timestamp:<PHONE_NUMBER>992
    Operation: RunUITestsCommand
    Exit Code: 3
    User Email<EMAIL_ADDRESS>    User Name: ownibloc
    User Id: 0e6e4a2a-c20d-48ab-9952-d5535b5fa000


fix/datadog-scaler-null-last-point

In issue 3906, we found out that the last data point of some specific query always returns null, this fix is to find out the last data point which is not null instead of validating the last data point only
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Changelog has been updated and is aligned with our changelog requirements

Fixes #3906

/run-e2e datadog*

@dogzzdogzz could you please fix the Static Check?

@dogzzdogzz you can probably add exception for this check here: https://github.com/kedacore/keda/blob/main/.golangci.yml#L63

/run-e2e datadog*

static check passed, thanks for the suggestion


org.postgresql.util.PSQLException: ERROR: relation "results.catalogue_results" does not exist

I get an error message when running Catalog export. This is the code:
cdmDatabaseSchema <- "cdm"
resultsDatabaseSchema <- "results"
vocabDatabaseSchema <- cdmDatabaseSchema
numThreads <- 1
cdmSourceName <- "Heliant"
cdmVersion <- "5.3.1"

library(CatalogueExport)

CatalogueExport::catalogueExport(connectionDetails, cdmDatabaseSchema = cdmDatabaseSchema, resultsDatabaseSchema = resultsDatabaseSchema, vocabDatabaseSchema = vocabDatabaseSchema, numThreads = numThreads, sourceName = cdmSourceName, cdmVersion = cdmVersion)

Here's the console output:
output.txt
And here's the final error report I get (all the intermediate ones do get overwritten for some reason):
errorReportSql.txt
The same thing happens if I add the "createTable = TRUE" parameter to the call.
I really don't have a catalogue_report table, as can be seen in this screenshot:

I reran this on our postgresql box and did not have these issues. The fact you do not have the catalogue_results table is because some queries did not execute so these temp tables are not there (these are created per query to allow for parallel execution). This means that the catalogue_results table cannot be created out of all the temp tables.
You seem to have issue with queries that use the concept_ancestor table.
Can you run this query in your database and report back the result:
-- 430	Number of descendant condition occurrence records,by condition_concept_id
--HINT DISTRIBUTE_ON_KEY(stratum_1)
WITH CTE_CONDITION AS (
SELECT ca.ANCESTOR_CONCEPT_ID AS CONCEPT_ID, COUNT(*)
AS DRC
FROM cdm.CONDITION_OCCURRENCE co
JOIN cdm.CONCEPT_ANCESTOR ca
ON ca.DESCENDANT_CONCEPT_ID = co.CONDITION_CONCEPT_ID
GROUP BY ca.ANCESTOR_CONCEPT_ID
)
SELECT  430 as analysis_id,
CAST(co.CONDITION_CONCEPT_ID AS VARCHAR(255)) AS stratum_1,
cast(null as varchar(255)) AS stratum_2,
cast(null as varchar(255)) as stratum_3,
cast(null as varchar(255)) as stratum_4,
cast(null as varchar(255)) as stratum_5,
floor((c.DRC+99)/100)*100 as count_value
FROM cdm.CONDITION_OCCURRENCE co
JOIN CTE_CONDITION c
ON c.CONCEPT_ID = co.CONDITION_CONCEPT_ID
GROUP BY co.CONDITION_CONCEPT_ID, c.DRC

That query returns empty resultset. The CTE_CONDITION subquery / statement scoped view also returns empty set.

that is very strange, do you have data in your concept_ancestor table?

Maybe it's a coincidence but @filipmaljkovic got a SQL:org.postgresql.util.PSQLException:ERROR:no schema has been selected to create_ error for queries:  430, 630, 730, 830, 1830, 2130 and we got a SQLSyntaxErrorException: ORA-00905: missing keyword for the exact same queries: https://github.com/EHDEN/CatalogueExport/issues/25

Yes I was thinking the same, but that would not explain why he does not get back the CTE in his own environment..
@scossin if you get it running till the end the I can create a new release with your fixes in there and we can test also on the Serbian dataset from @filipmaljkovic

that is very strange, do you have data in your concept_ancestor table?

Yes, 122833 rows.

Also, I didn't initially attach any of the intermediate errors that I got (because they get overwritten), but here's one. From different runs and different samples, they all look alike and have similar semantics -- insert statement is into something like s_tmpach_***, that doesn't specify a schema, which then fails.
errorReportSql-intermediate.txt

@filipmaljkovic
Yes, intermediate errors are overwritten, I will open an issue for that.
In your error file, I think the "into s_tmpach_830" line is causing the problem. By adding a ";" at the end of the template query 830 it would generate another SQL for postgresql that might work for you:
CREATE TABLE s_tmpach_830
AS
WITH CTE_procedure AS (
  SELECT ca.ancestor_concept_id AS concept_id, COUNT(*)
  AS DRC
  FROM cdm.observation co
  JOIN cdm.concept_ancestor ca
  ON ca.descendant_concept_id = co.observation_concept_id
  GROUP BY ca.ancestor_concept_id
)
SELECT  830 as analysis_id,
CAST(co.observation_concept_id AS VARCHAR(255)) AS stratum_1,
cast(null as varchar(255)) AS stratum_2,
cast(null as varchar(255)) as stratum_3,
cast(null as varchar(255)) as stratum_4,
cast(null as varchar(255)) as stratum_5,
floor((c.DRC+99)/100)*100 as count_value
FROM cdm.observation co
JOIN CTE_procedure c
ON c.concept_id = co.observation_concept_id
GROUP BY co.observation_concept_id, c.DRC
;

Is there a way to edit template queries? I figured that the upstream library/package should be fixed.
I tried running this query, but of course I had to specify the results schema up front. The table was empty.
However, as per output.txt, there were in total 6 errors of that kind, only one of which is 830. So any fix should include other occurrences, I suppose.

@filipmaljkovic
You can try to re-install the package from the dev branch (that contains a fix for these 6 errors) with this command:
devtools::install_github(repo = "EHDEN/CatalogueExport@dev")

Thanks, that did the trick! I confirm successful generation of the csv.


Fix sdk sample use coding components

Update ArcgisArcadeEditor component to use custom element syntax.
@qlqllu

Please update the readme file as well.


Doesn't render on IOS

The lib doesn't render on ios, I am not using full linking, any help?

Hey, thanks for using my library!
Have you tried reproducing your issue with the sample project included in the source code?

I am sorry, i missed this line 			ImageButtonRenderer.Init();


Type\not_null()

Is your feature request related to a problem? Please describe.
Quite often I find myself using Type\instance_of to assert values are not null, for example...
/** @var null|Foo $x */
$x = getSomeValueOrAccessAPropertyOrMethodEtc();

$x = Type\instance_of(Foo::class)->assert($x);

Here I'm essentially duplicating the expected type (Foo::class), because it's usually already declared on the property/method etc...  but is nullable.
Describe the solution you'd like
It would be more concise to be able to say...
$x = Type\not_null()->assert($x);

Which would assert that $x is Foo and not null|Foo.
Describe alternatives you've considered
I've presented my current solution for this above, I'm not aware of any other features of PSL which could be used here (apologies if I've missed something).

There is Psl\invariant:
invariant($x !== null, 'must not be null');

this won't be possible, as psalm doesn't have a type that includes everything but not null 🤔

The not_null type exists - yet there is no type narrowing possible in psalm (without a plugin).
Is that sufficient or should we keep this open @azjezz  ?

we could close this issue, and open a new one in the plugin repository to add support for type narrowing when Type\not_null() is used?
wdyt @veewee ?


overwrite QueryParams - only string is supported

Improve the Portman transformation to automatically set string values for numbers
Review the Portman schema validation to make sure Portman reports if non-string values are defined.

The Portman schema validation is properly triggered via the portman CLI, when non-string values are used.

When Portman is used as library, there is no schema validation, which took the number values instead of strings, which resulted in an invalid Postman collection


Add rocky-9-arm to build step

Tests are failing with error - Failed to create test workflow: googleapi: Error 404: The resource 'projects/gcp-guest/global/images/rocky-linux-9-arm64-guest-agent-stable-1729608283' was not found, notFound
Make sure rocky-9-arm image is built so its available at test step

/hold

/lgtm

/unhold


Update CA resource customSetDefaults method for RevocationConfiguration field

Description of changes:

Update the CA resource customSetDefaults method to set default values of the RevocationConfiguration field
Update e2e tests to test for different values of the RevocationConfiguration field

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/test-all

/retest

/retest

/retest

/lgtm


[GJ-75] Unify function names

This pr unified the function names according to the Substrait specifications in:
https://substrait.io/extensions/.
Based on: https://github.com/substrait-io/substrait/pull/147.
Closes https://github.com/oap-project/gazelle-jni/issues/75.

@marin-ma Hi Rong, please help to check if this PR works for you, thanks.

Verified with ClickHouse Lib, LGTM.


pdfminer unable to extract metadata - returns PDFObjRef

When trying to extract metadata from some pdf files, instead of getting a string value for the metadata information, I get a PDFObjRef.
I tried with PyPDF2 and I get the same problem.
I also tried dumping the whole pdf as xml, but the metadata tags are not there either.
The metadata information IS there, because regular pdf readers and pdfminer command line tool extract it correctly.
I also tried to see if there was a 'Metadata' key in the doc.catalog, but it isn't there.
EDIT: it's probably worth mentioning that the issue happens mostly with pdf file produced with mac os

The following was how I solved it:
from pdfminer.pdftypes import PDFObjRef, resolver1

if isinstance(value, PDFObjRef):
    value = resolve1(value)

Where "value" is something like PDFObjRef:5860.

It works, thanks!

I'm having this same problem where my doc.catalog has no Metadata key and don't quite understand the solution here. Would it be possible to post a super short example of reading a pdf and using the resolve1 trick to extract metadata?

You can see how I'm doing in this edited version of "dumppdf.py": https://github.com/sowdust/pdfxplr/blob/master/dumppdf.py built for the tool https://github.com/sowdust/pdfxplr

@os-gabe if you need more attention for your question you could also create a new issue. Make sure to include the code and pdf you are using.

Would something similar to "docs/source/tutorial/extract_pages.rst" be OK?
Also, I'll need some help: how do I add stuff there? Fork PDFMiner, add my file and when it's done do a pull request?
(no experience here)


Fix eq() comparison of DecorationSets

This function is currently always returning false for different objects, so the value equality comparison is not working. Seems like a typo to me, and I think this causes some unnecessary re-renders when applying the same decoration set.

Thanks for spotting that! It seemed the view desc reuse did prevent most DOM redrawing from taking place, but still this should definitely be an efficiency gain.


Create Kubernetes objects from the extension

I would like to be able to create Kubernetes objects from the extension. The experience would be as follows:

right click the type of object you want to create from the extension pane
click create
the editor opens YAML file, pre-populated with the template for the object type I want to create

Of course it would not work for all objects in the tree (such as Nodes), but for anything that can be created with a declarative file, it should work.
Thoughts?

What's the user story for this, as a developer? Can you write the scenario out? Radu might want that, or Ralph, but for prioritization I'd love to hear the "common developer workflow" story.

User story:

Radu is working on a simple application. Suddenly, he needs to add credentials for a database connection string, and he heard that secrets might be the way to go in Kubernetes. As he never created a secret before, or is unfamiliar / unwilling to write Kubernetes YAML by hand, from scratch, this would spare Radu the Google search for Kubernetes secret, then the copy-paste from the Kubernetes docs, a right-click -> create secret -> pre-populated YAML file might be the experience he needs.

Now replace  with any Kubernetes object. Does it make sense?
Thanks!

yes, more generally, I would start with specific objects and work up from there. Secrets/configmaps are good starts. :-)

Hey guys, would be also nice to edit ConfigMaps and Secrets from the extension. :)

Raised a new issue #579 for the specific case of ConfigMaps and Secrets because those are more specific, we have more concrete use cases and it's a bit more bounded.


warnings, errors, and usability of eaf2rttm.py

I'm trying to format some AAS .eaf files as .rttm to compare them against different SAD outputs and to feed them into the other tools. I ran into several issues>
No example call for the reformat script in the DiViMe docs
I followed the instructions at https://divime.readthedocs.io/en/latest/formats.html, but there's no actual example call. I ran it as vagrant ssh -c "eafAAS2rttm_folder.sh data/exampledir english", which seemed to work. Please add this to the formats instructions page.
The python script called by the .sh script throws some errors
The output I get for the command above is:
m14404737:DiViMe marcas$ vagrant ssh -c "eafAAS2rttm_folder.sh data/CogSciTutorial english"
/home/vagrant/utils/elan2rttm.py: line 12: $'\nwritten in python3.5\n\nscript for translating .eaf annotation files into .rttm format\n\nWARNING: this version results in a loss of information since .rttm\nonly keeps speaker ID regardless of the nature of the speech (whereas\n.eaf contains additional information such as speech nature e.g. MWU, VCM ...)\n\nThis information might be recovered in an advanced version of this script\n\n': command not found
/home/vagrant/utils/elan2rttm.py: line 15: import: command not found
/home/vagrant/utils/elan2rttm.py: line 16: import: command not found
/home/vagrant/utils/elan2rttm.py: line 17: import: command not found
/home/vagrant/utils/elan2rttm.py: line 20: syntax error near unexpected token `('
/home/vagrant/utils/elan2rttm.py: line 20: `def eaf2rttm(path_to_eaf, path_to_write_rttm):'
Directory found.
Converting data/CogSciTutorial//5271-0GS0.eaf files to data/CogSciTutorial//5271-0GS0.txt ...
Parsing unknown version of ELAN spec... This could result in errors...
Enriching data/CogSciTutorial//5271-0GS0.txt
Cleaning data/CogSciTutorial//5271-0GS0.txt
Pĥonemizing /vagrant/data/CogSciTutorial/clean_transcript.txt3.tmp ...
/usr/lib/python2.7/dist-packages/pkg_resources.py:1031: UserWarning: /home/vagrant/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
  warnings.warn(msg, UserWarning)
Done.
Converting data/CogSciTutorial//5959-0GS0.eaf files to data/CogSciTutorial//5959-0GS0.txt ...
Parsing unknown version of ELAN spec... This could result in errors...
Enriching data/CogSciTutorial//5959-0GS0.txt
Cleaning data/CogSciTutorial//5959-0GS0.txt
Pĥonemizing /vagrant/data/CogSciTutorial/clean_transcript.txt3.tmp ...
/usr/lib/python2.7/dist-packages/pkg_resources.py:1031: UserWarning: /home/vagrant/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
  warnings.warn(msg, UserWarning)
Done.
Connection to <IP_ADDRESS> closed.

The 'spanish' language flag gives some extra warnings:
Language set on spanish or tzeltal. But no vowels have been provided.
Setting this parameter to aeiouáéíóúü
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_CTYPE = "C",
	LANG = "spanish"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

Perhaps most importantly: The output doesn't look like an .rttm file formatted into the columns specified in the docs
With the 'english' language flag
5271-0GS0_enriched-EN.txt
5959-0GS0_enriched-EN.txt
With the 'spanish' language flag
5271-0GS0_enriched-SP.txt
5959-0GS0_enriched-SP.txt

I tried creating my own .rttm file manually in order to test the rest of the system out, but the diarization script doesn't seem to like my input file: 5959.rttm
m14404737:DiViMe marcas$ vagrant ssh -c "diartk.sh data/CogSciTutorial/ rttm"
wavs and transcriptions found !
Tests finished
treating 5959
cp: cannot stat '/vagrant/data/CogSciTutorial//5959.rttm': No such file or directory
sed: can't read /vagrant/data/CogSciTutorial//temp/diartk//5959.rttm: No such file or directory
Traceback (most recent call last):
  File "/home/vagrant/utils/rttm2scp.py", line 103, in <module>
    main()
  File "/home/vagrant/utils/rttm2scp.py", line 99, in main
    sad_tree, fname = read_rttm(args.rttm)
  File "/home/vagrant/utils/rttm2scp.py", line 69, in read_rttm
    raise IOError(errno.ENOENT, os.strerror(errno.ENOENT), input_path)
IOError: [Errno 2] No such file or directory: '/vagrant/data/CogSciTutorial//temp/diartk/5959.rttm'
Connection to <IP_ADDRESS> closed.

Files:
5959-eaf2rttm_manual_file_issue.zip

@marisacasillas about your very last point, RE your hand-made rttms, when I download the sample file you gave me, it's a csv. Meaning that it has a double extension, .rttm.csv. This may explain why the system doesn't see it. Can you check?
About the rest of your comments, nearly all I fixed BUT not completely. Strangely, my copy of vagrant  doesn't "see" the data folder at all.

Oof! That is a .csv! Not sure how/when that happened. I changed the extension but didn't update DiViMe yet. Changing the extension of the manual rttm worked though: I get output.
m14404737:DiViMe marcas$ vagrant ssh -c "diartk.sh data/CogSciTutorial/ rttm"
wavs and transcriptions found !
Tests finished
treating 5959
WARNING for /vagrant/data/CogSciTutorial//temp/diartk/5959.fea: replacing HCopy htconfig with SMILExtract MFCC12_E_D_A is untested
(MSG) [2] in SMILExtract : openSMILE starting!
(MSG) [2] in SMILExtract : config file is: /home/vagrant/repos/opensmile-2.3.0/config/MFCC12_E_D_A.conf
(MSG) [2] in cComponentManager : successfully registered 96 component types.
(MSG) [2] in instance 'lldcsvsink' : No filename given, disabling this sink component.
(MSG) [2] in instance 'lldarffsink' : No filename given, disabling this sink component.
(MSG) [2] in cComponentManager : successfully finished createInstances
                                 (16 component instances were finalised, 1 data memories were finalised)
(MSG) [2] in cComponentManager : starting single thread processing loop
(MSG) [2] in cComponentManager : Processing finished! System ran for 30019 ticks.
----------Initialize HMM
Connection to <IP_ADDRESS> closed.

Do you want me to update my local DiViMe and try your eaf2rttm script again? It's so nice to have it automated!

sure! give it a try. I think it may be an error in a script, though, in which case you'll get the same error I got.


winget isn't publishing

See https://github.com/pulumi/pulumi-winget/actions/runs/2871825166

Debugging, going with the hypothesis that this is the problem:
{"PackageIdentifier":"Pulumi.Pulumi","PackageVersion":"3.38.0","InstallerUrls":[],"ReleaseNotesUrl":"https://github.com/pulumi/pulumi-winget/releases/tag/v3.38.0","ReleaseDate":"2022-08-16","DeletePreviousVersion":false}'

Note InstallerUrls: []

    const instRegex = getInput('installers-regex');

    InstallerUrls: releaseInfo.assets
      .filter((asset) => {
        return new RegExp(instRegex, 'g').test(asset.name);
      })
      .map((asset) => {
        return asset.browser_download_url;
      }),

I can revert to using the previous manifest format which removes the dependency on the external github action

FWIW
const { context, getOctokit } = require('@actions/github');

const owner = 'pulumi';
const repo = 'pulumi-winget';
const token = process.env['GITHUB_TOKEN'];
const releaseTag = 'v3.38.0';
const instRegex = '.(exe|msi|msix|appx)(bundle){0,1}$';

async function foo() {
    const resp = await getOctokit(token).rest.repos.getReleaseByTag({
        owner: owner,
        repo: repo,
        tag: releaseTag,
    });
    const releaseInfo = resp.data;
    const installerUrls = releaseInfo.assets
      .filter((asset) => {
        return new RegExp(instRegex, 'g').test(asset.name);
      })
      .map((asset) => {
        return asset.browser_download_url;
      });
    return installerUrls;
}

foo()
    .then(text => {
        console.log(text);
    })
    .catch(err => {
        console.log(err);
        // Deal with the fact the chain failed
    });

[
  'https://github.com/pulumi/pulumi-winget/releases/download/v3.38.0/pulumi-3.38.0-windows-x64.msi'
]

So I couldn't repro the issue with the GitHub action step but Zaid has removed it entirely from the repo's dependencies so that's probably better, we don't need to continue debugging it.


Remove Default impl for SymbolInfo

It makes no sense whatsoever to implement Default for a type that does not have any logical default value, such as SymbolInfo. Remove it.

There is "all zero" symbol #0 in ELF (you can even see it in readelf output):
0:<PHONE_NUMBER>000000     0 NOTYPE  LOCAL  DEFAULT  UND

but if default is not helpful, sure, why not. We can always add it back, if necessary.

Yes, but it's not a valid entry, is it? The index is invalid/undefined. So, what would a user do with such an entry? Nothing, it's useless, it conveys zero information. As such, it should be filtered out and not be representable in the first place, instead of its creation be "encouraged" by making it the default.


empty is nil in unmarshal

empty nodes are nil in unmarshal. this makes sense to me, but has caused me inconvenience and i wondered if it made sense to put an empty interface there. when using unmarshal, kdl behaved differently than the others when looking at koanf

i believe there might be something in kdl specs that says the data model or something agrees with what you've done, i just, wanted to note this issue here and maybe i'm doing something wrong.
https://github.com/developing-today-forks/koanf/pull/1/files

so with this
key "value"
map "skipped"
map key="skipped" key="value"
nested_map {
map key="value" 17 {
	list "item1" "item2" "item3"
	mixup ""=1 2 3 4
	first "first"=1 2 3 4
	child ""=1 2 3 4 { "" 5 ; "" 6 ; }
}
}

i get unmarshal errors from map being there twice at start, i think because the type changes. but i think it should just replace the type and the last one should win? any other option gets complicated, but i dont think it should throw because its valid kdl and there is a set order so replacing makes sense.
although there is valid kdl i think should throw in certain marshalling scenarios. such as child ""=1 "0"=3 2 3 4 because "0"=3 overlaps "2" each map to "child.0" except properties have no order. maybe a rule properties are before arguments? but then that's all custom behavior on top so idk. panic or custom behavior or options to toggle flags? hard to say best course.
separate issue { "" 5 ; "" 6 ; } is valid kdl but seems to cause an issue. i think semicolon isn't correctly being handled.
{
"" 5
"" 6 }

seems to work better but i think that maybe empty node name is behaving strangely. perhaps identifiers have been given the rules for bare identifiers? for instance, i don't think i can make a "1" node, yet that is all valid kdl so long as double quotes are used
i'm also having issues with properly unmarshalling nested_map, it doesn't panic but it returns empty. this problem may be unrelated to kdl-go though, no sure yet. nobody likes empty string keys :)
i did try and read through https://github.com/sblinch/kdl-go/blob/main/docs/unmarshal.md but i didn't find anything that said these documents should unmarshal. i appreciate the detailed steps and everything you listed there. i had thought most toggles were to extend what is permissible. is there one that enables overwriting values or something i'm missing that would be causing these kdl doucments to error?

Please provide a complete test case including the Go code and the KDL you're unmarshaling. The struct tags you use will completely change how a KDL snippet is interpreted so I can't even begin to diagnose without that information.
Please also open a separate issue for each bug you're reporting as it becomes confusing tracking multiple issues in a single thread.

I'll make an isolated example when I get back to that machine, for now here is my marshal unmarshal commands
func (p *KDL) Unmarshal(b []byte) (map[string]interface{}, error) {
        var o map[string]interface{}
        err := kdl.Unmarshal(b, &o)
        return o, err
}
func (p *KDL) Marshal(o map[string]interface{}) ([]byte, error) {
        return kdl.Marshal(o)
}

Thank you!

Fixed in 3d5e45f.


Let TAPI clients discover forked processes more easily

The netbeans gradle plugin could benefit from a Gradle API that exposes the PID of the JVM process(es) that are spawned when running application, tests, etc.  This would allow for more convenient/automated connections to run profiler on those processes.  Currently the only option is to manually point the profiler to the processes, but it would be nicer if any tool calling Gradle could automate that.
This API would make most sense for cases where the gradle tasks being executed only result in a single application/test JVM being spawned.  In cases where multiple JVMs are spawned (for example when running tests in parallel), the API could return the whole list of PIDs, but the usefulness in that case is less clear.
Related issues:
https://github.com/kelemen/netbeans-gradle-project/issues/106
https://github.com/kelemen/netbeans-gradle-project/issues/394

There is no need for a list, if a task was capable to call back to the client of the Tooling API (if there is any) with a somewhat custom message (e.g., a map mapping strings to strings and boxed primitives).

I think this could be modelled as a progress event (similar to what we already have for tasks and tests in the Tooling API). This event could be fired whenever we fork a new process and provide that processes PID. We could fire another one when the process is killed.

Yes, I think that would be good, if the progress event is well defined. So that I can be confident that my code won't break in a subsequent Gradle version.


feat: select add keyboard prop

close #4340
Signed-off-by: Sepush<EMAIL_ADDRESS>

Codecov Report
Base: 62.50% // Head: 62.49% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (b508fe3) compared to base (2c2066c).
Patch coverage: 0.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4441      +/-   ##
==========================================
- Coverage   62.50%   62.49%   -0.01%
==========================================
  Files        1069     1069
  Lines       22420    22423       +3
  Branches     5882     5883       +1
==========================================
  Hits        14013    14013
- Misses       6879     6882       +3
  Partials     1528     1528

Impacted Files
Coverage Δ

src/select/src/Select.tsx
34.69% <0.00%> (-0.31%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


The module don't use custom venvs

it is using now https://github.com/sepal-contrib/alert_module/commit/6cc56ff63c56d8570ea1c1a54a9a804162949eef


RHEL-08-020024 is not using the rhel8stig_maxlogins variable

Describe the Issue
The task RHEL-08-020024 does not use the variable rhel8stig_maxlogins it is currently using a hard coded value of '10'.
Expected Behavior
The task to use the variable to define the value for max logins.
Actual Behavior
The task does not use the variable since the value is hard coded.
Control(s) Affected
https://www.stigviewer.com/stig/red_hat_enterprise_linux_8/2021-06-14/finding/V-230346
Environment (please complete the following information):

RHEL 8

Additional Notes
Possible Solution

Hi @rheak
Thank you for taking the time to highlight this bug, we are currently looking to update to the latest release and will be sure to add this fix into that release.
Regards
uk-bolly

hi @rheak
Thank you again for taking the time to raise this issue, this should now be resolved in the latest devel branch this also includes updates to the latest STIG release.
I will close this call over the next week unless you have any further feedback?
Many thanks again
uk-bolly


How to set today date selected ?

How to set today date selected in bootstrap-datepicker ?
im already use this code
$("#date").val($.datepicker.formatDate('dd-mm-yy', new Date()));
but the input value will disappear when i click bootstrap-datepicker and not selected/highlight in the bootstrap-datepicker.
sorry for newbie question,
thanks

sorry, just read the docs. just use html value


<MySnippet: such and such> is not JSON serializable - snippets in streamfield

Given the following Snippet:
class InfographicSnippet(models.Model):
    name = models.CharField(max_length=255, help_text="The name of this infographic, for identification within Wagtail")
    html = models.TextField()

    panels = [
        FieldPanel('name'),
        FieldPanel('html')
    ]

    def __str__(self):
        return self.name

    class Meta:
        verbose_name = "Infographic"
        ordering = ['name']

and the following streamfield block
from models import InfographicSnippet

class InfographicBlock(FieldBlock):
    field = SnippetChooserBlock(InfographicSnippet)

While it's possible to choose a snippet to appear in my streamfield, it's not possible to save the page. I get the error <InfographicSnippet: Myanmar oil and gas> is not JSON serializable

class InfographicBlock(FieldBlock):
    field = SnippetChooserBlock(InfographicSnippet)

This is invalid - a SnippetChooserBlock is not a field object. You should use infographic = SnippetChooserBlock(InfographicSnippet) directly in your streamfield definition instead.


Make an analysis schema

Our schema should be able to describe an analysis result.

@dyf We have run into a fundamental challenge with this. Let's discuss in person asap.


Adjustment to Table Component AutoHeight Parameter

Ticket Summary:
This ticket addresses an issue with the autoHeight parameter of the Table component which is not functioning as expected in Storybook.
Issue Description:

The autoHeight parameter of the Table component documented at Table Component in Storybook is not operating correctly. The expected behavior is that the table adjusts its height automatically based on content, but this does not occur.

Tasks:

Investigate and Identify Cause:

Determine why the autoHeight parameter is not working as documented.

Code Adjustment:

Adjust the implementation of the autoHeight parameter to ensure it functions correctly.
Conduct thorough testing to validate the fix.

Impact Analysis:

Analyze the potential impact of this change on existing frontends utilizing the Table component.
Document the changes and their expected behavior for developers.

Acceptance Criteria:

The autoHeight parameter must function as expected, allowing the Table component's height to automatically adjust based on its content.
The solution should not negatively impact the current functionalities and design of the Table component in other aspects.

Implementation Notes:

Ensure backward compatibility or provide a migration path for frontends currently using the autoHeight parameter.
Update the Storybook documentation to reflect the corrected behavior of the autoHeight parameter.

Technical Details:

Reference URL: Table Component Story

Communication Plan:

Notify all frontend teams of the change and its potential impact.
Clearly label the pull request with the "breaking" label to highlight the importance of the change.

@jjeroch Fundamental understanding of autoheight seems wrong here. autoheight is not meant to handle the auto height of a row. If a table is wrapped in container and the height has to be dynamic, then autoheight helps to do so.
ex:
<Box sx={{ height: 100, width: "100%" }}>
      <DataGrid
        autoHeight={false}
       rows=[
{
    id: 1,
    lastName: "Snow",
    firstName: "Jon",
    age: 14
  },
  { id: 2, lastName: "Lannister", firstName: "Cersei", age: 31 },
  { id: 3, lastName: "Lannister", firstName: "Jaime", age: 31 },
  { id: 4, lastName: "Stark", firstName: "Arya", age: 11 },
  { id: 5, lastName: "Targaryen", firstName: "Daenerys", age: null },
  { id: 6, lastName: "Melisandre", firstName: null, age: 150 },
  { id: 7, lastName: "Clifford", firstName: "Ferrara", age: 44 },
  { id: 8, lastName: "Frances", firstName: "Rossini", age: 36 },
  { id: 9, lastName: "Roxie", firstName: "Harvey", age: 65 }]
 />
</Box>

<Box sx={{ height: 100, width: "100%" }}>
      <DataGrid
        autoHeight={true}
       rows=[
{
    id: 1,
    lastName: "Snow",
    firstName: "Jon",
    age: 14
  },
  { id: 2, lastName: "Lannister", firstName: "Cersei", age: 31 },
  { id: 3, lastName: "Lannister", firstName: "Jaime", age: 31 },
  { id: 4, lastName: "Stark", firstName: "Arya", age: 11 },
  { id: 5, lastName: "Targaryen", firstName: "Daenerys", age: null },
  { id: 6, lastName: "Melisandre", firstName: null, age: 150 },
  { id: 7, lastName: "Clifford", firstName: "Ferrara", age: 44 },
  { id: 8, lastName: "Frances", firstName: "Rossini", age: 36 },
  { id: 9, lastName: "Roxie", firstName: "Harvey", age: 65 }]
 />
</Box>

In the above example when autoheight is false UI screwed as the height is set to 100px. But when it changed to true height adjusted for the whole container


BITMAKER-2142 estela-web: Implement "In Projects/Scheduled Jobs"

Description
estela-web: Implement "In Projects/Scheduled Jobs"
Issue
https://tasks.bitmaker.dev/issues/2142
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] My code follows the style guidelines of this project.
[x] I have made corresponding changes to the documentation.
[x] New and existing tests pass locally with my changes.
[x] If this change is a core feature, I have added thorough tests.
[x] If this change affects or depends on the behavior of other estela repositories, I have created pull requests with the relevant changes in the affected repositories. Please, refer to our official documentation.
[x] I understand that my pull request may be closed if it becomes obvious or I did not perform all of the steps above.

@Adriana618 This is ready to review

@Adriana618 I fixed the comment you did


[MRG] Fix update gui default dicts

Dictionaries that are nested within dictionaries are not updated with the update method. A recursive function was added to search for dictionary keys of nested dictionaries for updating. This is used for updating default values for GUI widgets.
Changes:

Added a recursive update function that will search nested dictionaries for keys to update
Updated default values for poisson widget

split from #808

@ntolley This one is rebased and ready to merge now.


Remore now irrelevant section from gotchas.md

React Boilerplate
In the now defunct config.js file inside internals/, we had a setting to exclude dependencies from the DLL. This is no longer relevant so we need to remove the section about this from gotchas.md.
Reported by @danobot in #2639.

Coverage remained the same at 99.669% when pulling 79c4312433572e4692022c03255439b9eef496aa on docs-update into fd58cd23c9186bd49d7e8f3aac7536f1f52a9e19 on dev.

Coverage remained the same at 99.669% when pulling 79c4312433572e4692022c03255439b9eef496aa on docs-update into fd58cd23c9186bd49d7e8f3aac7536f1f52a9e19 on dev.


Headers setting support when files match a regex

Sometimes it might be useful being able to assign to a file a specific header to be returned by RackSpace when serving the file to the clients.
E.g. it is useful for font files that sometimes need to include an Access-Control-Allow-Origin: * header in order to be accessible cross-domain.
This PR tries to add to posthaste a functionality similar to the one provide by Django-cumulus headers (http://django-cumulus.readthedocs.org/en/latest/#headers).

I received this traceback when attempting this PR:
posthaste -i rackspace -u user -p password -vv -r dfw -c testcontainer upload ~/Downloads/test

Traceback (most recent call last):
  File "/Users/paul/Projects/Python/virtualenvs/posthaste/bin/posthaste", line 9, in <module>
    load_entry_point('posthaste==0.2.3', 'console_scripts', 'posthaste')()
  File "/Users/paul/Projects/Python/posthaste/posthaste.py", line 646, in shell
    for regex, header_name, header_value in args.headers:
TypeError: 'NoneType' object is not iterable

I'll revert this PR.  Please re-pull working and re-submit.