Stuck in a loop even after restore

Describe the bug
My node hardware (RasPi4) failed.
I saw something in the logs like a specific file failed checksum, so I mistakenly thought that it would help if I deleted the file.  Once I rm'ed the file, bitcoin's debug.log showed it kept looping, complaining about that specific file missing.
Replaced node with a new RasPi4.
Flashed new SDHC with latest raspiblitz.
Booted up and it saw the files on the SSD, asked me if I wanted to restore, I agreed.  Great, I thought.  Nope...
It's now looping again on the same place it was before I swapped out the hardware and flashed a new SDHC.
To Reproduce
On a node you don't care about, do this;
sudo ls -la /mnt/hdd/bitcoin/indexes/txindex/
Choose one of the files, then delete it like this;
sudo rm /mnt/hdd/bitcoin/indexes/txindex/053716.ldb
then reboot the node and see the looping failure on that missing file with no obvious solution.
Debug file
loopy.txt | https://termbin.com/101t | https://archive.ph/rGxEc
Please add something to the code to help idiots like me figure out how to get out of this stuck-in-loop situation, or add comment(s) on suggestions for what I can try here.  I love the raspiblitz software and commend you on producing the best bitcoin lightning node software I have ever seen.

Decided to try harder at fixing this myself.
I have another raspiblitz node on my LAN that is working just fine.
I will use that node's non-corrupted blockchain data to copy over to my stuck-in-loop node.
<IP_ADDRESS> is the IP address of my stuck-in-loop node;
admin@<IP_ADDRESS>:~ ₿ sudo systemctl stop lnd
admin@<IP_ADDRESS>:~ ₿ sudo systemctl stop bitcoind
admin@<IP_ADDRESS>:~ ₿ sudo rm -rf /mnt/hdd/bitcoin/blocks
admin@<IP_ADDRESS>:~ ₿ sudo rm -rf /mnt/hdd/bitcoin/chainstate
admin@<IP_ADDRESS>:~ ₿

I then went to my good raspiblitz node: MENU > REPAIR > COPY-SOURCE.
It's now in the process of copying the data, 1% completed.  ETA = ~4 hours.

26% done...

Looks like it's done.
Now seeing this:

Did a ^C to get out of that screen, followed by:
sudo reboot
Gave it a few minutes, ssh'ed back in.  Now seeing the same problem still;

The same stuck-in-loop problem still exists;
admin@<IP_ADDRESS>:~ ₿ sudo tail -f /mnt/hdd/bitcoin/debug.log
2023-10-27T07:58:02Z * Using 2230.2 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2023-10-27T07:58:02Z init message: Loading block index…
2023-10-27T07:58:02Z Assuming ancestors of block<PHONE_NUMBER>00000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
2023-10-27T07:58:02Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
2023-10-27T07:58:02Z Opening LevelDB in /mnt/hdd/bitcoin/blocks/index
2023-10-27T07:58:02Z Opened LevelDB successfully
2023-10-27T07:58:02Z Using obfuscation key for /mnt/hdd/bitcoin/blocks/index:<PHONE_NUMBER>000000
2023-10-27T07:58:14Z LoadBlockIndexDB: last block file = 3904
2023-10-27T07:58:14Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=3, size=4641724, heights=813976...813978, time=2023-10-26...2023-10-26)
2023-10-27T07:58:14Z Checking all blk files are present...
2023-10-27T07:58:18Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2023-10-27T07:58:18Z Opening LevelDB in /mnt/hdd/bitcoin/chainstate
2023-10-27T07:58:18Z Opened LevelDB successfully
2023-10-27T07:58:18Z Using obfuscation key for /mnt/hdd/bitcoin/chainstate: 7424f602662de5fb
2023-10-27T07:58:19Z Loaded best chain: hashBestChain=0000000000000000000104dae34a02d245d6e18316e1ad8035e504fc8dc006d6 height=813978 date=2023-10-26T22:03:08Z progress=0.999856
2023-10-27T07:58:19Z [snapshot] allocating all cache to the IBD chainstate
2023-10-27T07:58:19Z Opening LevelDB in /mnt/hdd/bitcoin/chainstate
2023-10-27T07:58:19Z Opened LevelDB successfully
2023-10-27T07:58:19Z Using obfuscation key for /mnt/hdd/bitcoin/chainstate: 7424f602662de5fb
2023-10-27T07:58:19Z [Chainstate [ibd] @ height 813978<PHONE_NUMBER>000000000104dae34a02d245d6e18316e1ad8035e504fc8dc006d6)] resized coinsdb cache to 8.0 MiB
2023-10-27T07:58:19Z [Chainstate [ibd] @ height 813978<PHONE_NUMBER>000000000104dae34a02d245d6e18316e1ad8035e504fc8dc006d6)] resized coinstip cache to 2230.2 MiB
2023-10-27T07:58:19Z init message: Verifying blocks…
2023-10-27T07:58:19Z Verifying last 6 blocks at level 3
2023-10-27T07:58:19Z Verification progress: 0%
2023-10-27T07:58:20Z Verification progress: 16%
2023-10-27T07:58:21Z Verification progress: 33%
2023-10-27T07:58:22Z Verification progress: 50%
2023-10-27T07:58:23Z Verification progress: 66%
2023-10-27T07:58:24Z Verification progress: 83%
2023-10-27T07:58:25Z Verification progress: 99%
2023-10-27T07:58:25Z Verification: No coin database inconsistencies in last 6 blocks (16152 transactions)
2023-10-27T07:58:25Z  block index           23787ms
2023-10-27T07:58:25Z Opening LevelDB in /mnt/hdd/bitcoin/indexes/txindex
2023-10-27T07:58:25Z Fatal LevelDB error: Corruption: 1 missing files; e.g.: /mnt/hdd/bitcoin/indexes/txindex/053716.ldb
2023-10-27T07:58:25Z You can use -debug=leveldb to get more complete diagnostic messages
2023-10-27T07:58:25Z

EXCEPTION: 15dbwrapper_error
Fatal LevelDB error: Corruption: 1 missing files; e.g.: /mnt/hdd/bitcoin/indexes/txindex/053716.ldb
bitcoin in AppInit()
2023-10-27T07:58:25Z Shutdown: In progress...
2023-10-27T07:58:25Z scheduler thread exit
2023-10-27T07:58:26Z Shutdown: done
2023-10-27T07:58:27Z Bitcoin Core version v25.0.0 (release build)
2023-10-27T07:58:27Z InitParameterInteraction: parameter interaction: -bind set -> setting -listen=1
2023-10-27T07:58:27Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2023-10-27T07:58:27Z InitParameterInteraction: parameter interaction: -proxy set -> setting -natpmp=0
2023-10-27T07:58:27Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2023-10-27T07:58:27Z Using the 'standard' SHA256 implementation
2023-10-27T07:58:27Z Default data directory /home/bitcoin/.bitcoin
2023-10-27T07:58:27Z Using data directory /mnt/hdd/bitcoin
2023-10-27T07:58:27Z Config file: /mnt/hdd/bitcoin/bitcoin.conf
2023-10-27T07:58:27Z Config file arg: daemon="1"
2023-10-27T07:58:27Z Config file arg: datadir="/mnt/hdd/bitcoin"
2023-10-27T07:58:27Z Config file arg: dbcache="2560"
2023-10-27T07:58:27Z Config file arg: deprecatedrpc="addresses"
2023-10-27T07:58:27Z Config file arg: disablewallet="1"
2023-10-27T07:58:27Z Config file arg: dns="0"
2023-10-27T07:58:27Z Config file arg: dnsseed="0"
2023-10-27T07:58:27Z Config file arg: maxconnections="40"
2023-10-27T07:58:27Z Config file arg: maxmempool="300"
2023-10-27T07:58:27Z Config file arg: maxorphantx="10"
2023-10-27T07:58:27Z Config file arg: maxuploadtarget="5000"
2023-10-27T07:58:27Z Config file arg: onlynet="onion"
2023-10-27T07:58:27Z Config file arg: peerbloomfilters="1"
2023-10-27T07:58:27Z Config file arg: proxy="<IP_ADDRESS>:9050"
2023-10-27T07:58:27Z Config file arg: rpcallowip="<IP_ADDRESS>"
2023-10-27T07:58:27Z Config file arg: rpcpassword=****
2023-10-27T07:58:27Z Config file arg: rpcuser=****
2023-10-27T07:58:27Z Config file arg: server="1"
2023-10-27T07:58:27Z Config file arg: testnet="0"
2023-10-27T07:58:27Z Config file arg: txindex="1"
2023-10-27T07:58:27Z Config file arg: [main] bind="<IP_ADDRESS>"
2023-10-27T07:58:27Z Config file arg: [main] debuglogfile="/mnt/hdd/bitcoin/debug.log"
2023-10-27T07:58:27Z Config file arg: [main] rpcbind="<IP_ADDRESS>:8332"
2023-10-27T07:58:27Z Config file arg: [main] rpcport="8332"
2023-10-27T07:58:27Z Config file arg: [main] zmqpubrawblock="tcp://<IP_ADDRESS>:28332"
2023-10-27T07:58:27Z Config file arg: [main] zmqpubrawtx="tcp://<IP_ADDRESS>:28333"
2023-10-27T07:58:27Z Config file arg: [signet] debuglogfile="/mnt/hdd/bitcoin/signet/debug.log"
2023-10-27T07:58:27Z Config file arg: [test] bind="<IP_ADDRESS>"
2023-10-27T07:58:27Z Config file arg: [test] debuglogfile="/mnt/hdd/bitcoin/testnet3/debug.log"
2023-10-27T07:58:27Z Config file arg: [test] rpcbind="<IP_ADDRESS>:18332"
2023-10-27T07:58:27Z Config file arg: [test] rpcport="18332"
2023-10-27T07:58:27Z Command-line arg: conf="/mnt/hdd/bitcoin/bitcoin.conf"
2023-10-27T07:58:27Z Command-line arg: daemonwait=""
2023-10-27T07:58:27Z Command-line arg: datadir="/mnt/hdd/bitcoin"
2023-10-27T07:58:27Z Using at most 40 automatic connections (1024 file descriptors available)
2023-10-27T07:58:27Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2023-10-27T07:58:27Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2023-10-27T07:58:27Z Script verification uses 3 additional threads
2023-10-27T07:58:27Z Wallet disabled!
2023-10-27T07:58:27Z scheduler thread start
2023-10-27T07:58:27Z Binding RPC on address <IP_ADDRESS> port 8332
2023-10-27T07:58:27Z [http] creating work queue of depth 16
2023-10-27T07:58:27Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2023-10-27T07:58:27Z [http] starting 4 worker threads
2023-10-27T07:58:27Z Using /16 prefix for IP bucketing
2023-10-27T07:58:27Z init message: Loading P2P addresses…
2023-10-27T07:58:27Z Loaded 10541 addresses from peers.dat  163ms
2023-10-27T07:58:27Z init message: Loading banlist…
2023-10-27T07:58:27Z SetNetworkActive: true
2023-10-27T07:58:27Z Cache configuration:
2023-10-27T07:58:27Z * Using 2.0 MiB for block index database
2023-10-27T07:58:27Z * Using 319.8 MiB for transaction index database
2023-10-27T07:58:27Z * Using 8.0 MiB for chain state database
2023-10-27T07:58:27Z * Using 2230.2 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2023-10-27T07:58:27Z init message: Loading block index…
2023-10-27T07:58:27Z Assuming ancestors of block<PHONE_NUMBER>00000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
2023-10-27T07:58:27Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
2023-10-27T07:58:27Z Opening LevelDB in /mnt/hdd/bitcoin/blocks/index
2023-10-27T07:58:27Z Opened LevelDB successfully
2023-10-27T07:58:27Z Using obfuscation key for /mnt/hdd/bitcoin/blocks/index:<PHONE_NUMBER>000000
2023-10-27T07:58:40Z LoadBlockIndexDB: last block file = 3904
2023-10-27T07:58:40Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=3, size=4641724, heights=813976...813978, time=2023-10-26...2023-10-26)
2023-10-27T07:58:40Z Checking all blk files are present...
2023-10-27T07:58:43Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2023-10-27T07:58:43Z Opening LevelDB in /mnt/hdd/bitcoin/chainstate
2023-10-27T07:58:44Z Opened LevelDB successfully
2023-10-27T07:58:44Z Using obfuscation key for /mnt/hdd/bitcoin/chainstate: 7424f602662de5fb
2023-10-27T07:58:44Z Loaded best chain: hashBestChain=0000000000000000000104dae34a02d245d6e18316e1ad8035e504fc8dc006d6 height=813978 date=2023-10-26T22:03:08Z progress=0.999856
2023-10-27T07:58:44Z [snapshot] allocating all cache to the IBD chainstate
2023-10-27T07:58:44Z Opening LevelDB in /mnt/hdd/bitcoin/chainstate
2023-10-27T07:58:44Z Opened LevelDB successfully
2023-10-27T07:58:44Z Using obfuscation key for /mnt/hdd/bitcoin/chainstate: 7424f602662de5fb
2023-10-27T07:58:44Z [Chainstate [ibd] @ height 813978<PHONE_NUMBER>000000000104dae34a02d245d6e18316e1ad8035e504fc8dc006d6)] resized coinsdb cache to 8.0 MiB
2023-10-27T07:58:44Z [Chainstate [ibd] @ height 813978<PHONE_NUMBER>000000000104dae34a02d245d6e18316e1ad8035e504fc8dc006d6)] resized coinstip cache to 2230.2 MiB
2023-10-27T07:58:44Z init message: Verifying blocks…
2023-10-27T07:58:44Z Verifying last 6 blocks at level 3
2023-10-27T07:58:44Z Verification progress: 0%
2023-10-27T07:58:45Z Verification progress: 16%
2023-10-27T07:58:46Z Verification progress: 33%
2023-10-27T07:58:48Z Verification progress: 50%
2023-10-27T07:58:49Z Verification progress: 66%
2023-10-27T07:58:50Z Verification progress: 83%
2023-10-27T07:58:51Z Verification progress: 99%
2023-10-27T07:58:51Z Verification: No coin database inconsistencies in last 6 blocks (16152 transactions)
2023-10-27T07:58:51Z  block index           23765ms
2023-10-27T07:58:51Z Opening LevelDB in /mnt/hdd/bitcoin/indexes/txindex
2023-10-27T07:58:51Z Fatal LevelDB error: Corruption: 1 missing files; e.g.: /mnt/hdd/bitcoin/indexes/txindex/053716.ldb
2023-10-27T07:58:51Z You can use -debug=leveldb to get more complete diagnostic messages
2023-10-27T07:58:51Z

EXCEPTION: 15dbwrapper_error
Fatal LevelDB error: Corruption: 1 missing files; e.g.: /mnt/hdd/bitcoin/indexes/txindex/053716.ldb
bitcoin in AppInit()
2023-10-27T07:58:51Z Shutdown: In progress...
2023-10-27T07:58:51Z scheduler thread exit
2023-10-27T07:58:52Z Shutdown: done
2023-10-27T07:58:52Z Bitcoin Core version v25.0.0 (release build)
2023-10-27T07:58:52Z InitParameterInteraction: parameter interaction: -bind set -> setting -listen=1
2023-10-27T07:58:52Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2023-10-27T07:58:52Z InitParameterInteraction: parameter interaction: -proxy set -> setting -natpmp=0
2023-10-27T07:58:52Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2023-10-27T07:58:52Z Using the 'standard' SHA256 implementation
2023-10-27T07:58:52Z Default data directory /home/bitcoin/.bitcoin
2023-10-27T07:58:52Z Using data directory /mnt/hdd/bitcoin
2023-10-27T07:58:52Z Config file: /mnt/hdd/bitcoin/bitcoin.conf
2023-10-27T07:58:52Z Config file arg: daemon="1"
2023-10-27T07:58:52Z Config file arg: datadir="/mnt/hdd/bitcoin"
2023-10-27T07:58:52Z Config file arg: dbcache="2560"
2023-10-27T07:58:52Z Config file arg: deprecatedrpc="addresses"
2023-10-27T07:58:52Z Config file arg: disablewallet="1"
2023-10-27T07:58:52Z Config file arg: dns="0"
2023-10-27T07:58:52Z Config file arg: dnsseed="0"
2023-10-27T07:58:52Z Config file arg: maxconnections="40"
2023-10-27T07:58:52Z Config file arg: maxmempool="300"
2023-10-27T07:58:52Z Config file arg: maxorphantx="10"
2023-10-27T07:58:52Z Config file arg: maxuploadtarget="5000"
2023-10-27T07:58:52Z Config file arg: onlynet="onion"
2023-10-27T07:58:52Z Config file arg: peerbloomfilters="1"
2023-10-27T07:58:52Z Config file arg: proxy="<IP_ADDRESS>:9050"
2023-10-27T07:58:52Z Config file arg: rpcallowip="<IP_ADDRESS>"
2023-10-27T07:58:52Z Config file arg: rpcpassword=****
2023-10-27T07:58:52Z Config file arg: rpcuser=****
2023-10-27T07:58:52Z Config file arg: server="1"
2023-10-27T07:58:52Z Config file arg: testnet="0"
2023-10-27T07:58:52Z Config file arg: txindex="1"
2023-10-27T07:58:52Z Config file arg: [main] bind="<IP_ADDRESS>"
2023-10-27T07:58:52Z Config file arg: [main] debuglogfile="/mnt/hdd/bitcoin/debug.log"
2023-10-27T07:58:52Z Config file arg: [main] rpcbind="<IP_ADDRESS>:8332"
2023-10-27T07:58:52Z Config file arg: [main] rpcport="8332"
2023-10-27T07:58:52Z Config file arg: [main] zmqpubrawblock="tcp://<IP_ADDRESS>:28332"
2023-10-27T07:58:52Z Config file arg: [main] zmqpubrawtx="tcp://<IP_ADDRESS>:28333"
2023-10-27T07:58:52Z Config file arg: [signet] debuglogfile="/mnt/hdd/bitcoin/signet/debug.log"
2023-10-27T07:58:52Z Config file arg: [test] bind="<IP_ADDRESS>"
2023-10-27T07:58:52Z Config file arg: [test] debuglogfile="/mnt/hdd/bitcoin/testnet3/debug.log"
2023-10-27T07:58:52Z Config file arg: [test] rpcbind="<IP_ADDRESS>:18332"
2023-10-27T07:58:52Z Config file arg: [test] rpcport="18332"
2023-10-27T07:58:52Z Command-line arg: conf="/mnt/hdd/bitcoin/bitcoin.conf"
2023-10-27T07:58:52Z Command-line arg: daemonwait=""
2023-10-27T07:58:52Z Command-line arg: datadir="/mnt/hdd/bitcoin"
2023-10-27T07:58:52Z Using at most 40 automatic connections (1024 file descriptors available)
2023-10-27T07:58:52Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2023-10-27T07:58:52Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2023-10-27T07:58:52Z Script verification uses 3 additional threads
2023-10-27T07:58:52Z Wallet disabled!
2023-10-27T07:58:52Z scheduler thread start
2023-10-27T07:58:52Z Binding RPC on address <IP_ADDRESS> port 8332
2023-10-27T07:58:52Z [http] creating work queue of depth 16
2023-10-27T07:58:52Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2023-10-27T07:58:52Z [http] starting 4 worker threads
2023-10-27T07:58:52Z Using /16 prefix for IP bucketing
2023-10-27T07:58:52Z init message: Loading P2P addresses…
2023-10-27T07:58:52Z Loaded 10541 addresses from peers.dat  177ms
2023-10-27T07:58:52Z init message: Loading banlist…
2023-10-27T07:58:52Z SetNetworkActive: true
2023-10-27T07:58:52Z Cache configuration:
2023-10-27T07:58:52Z * Using 2.0 MiB for block index database
2023-10-27T07:58:52Z * Using 319.8 MiB for transaction index database
2023-10-27T07:58:52Z * Using 8.0 MiB for chain state database
2023-10-27T07:58:52Z * Using 2230.2 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2023-10-27T07:58:52Z init message: Loading block index…
2023-10-27T07:58:52Z Assuming ancestors of block<PHONE_NUMBER>00000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
2023-10-27T07:58:52Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
2023-10-27T07:58:52Z Opening LevelDB in /mnt/hdd/bitcoin/blocks/index
2023-10-27T07:58:52Z Opened LevelDB successfully
2023-10-27T07:58:52Z Using obfuscation key for /mnt/hdd/bitcoin/blocks/index:<PHONE_NUMBER>000000
^C
admin@<IP_ADDRESS>:~ ₿

Trying this;
admin@<IP_ADDRESS>:~ ₿ sudo -u bitcoin /usr/local/bin/bitcoind -reindex
Bitcoin Core starting
admin@<IP_ADDRESS>:~ ₿

There are 1905 files that need to be reindexed.
admin@<IP_ADDRESS>:~ ₿ sudo ls -la /mnt/hdd/bitcoin/blocks/ | grep blk0 | wc -l
3905
admin@<IP_ADDRESS>:~ ₿

Watching the action here;
admin@<IP_ADDRESS>:~ ₿ sudo tail -n 1000 -f /mnt/hdd/bitcoin/debug.log
Looks like this is going to take a few hours...

There are 3905 files that need to be reindexed.
admin@<IP_ADDRESS>:~ ₿ sudo ls -la /mnt/hdd/bitcoin/blocks/ | grep blk0 | wc -l
3905
admin@<IP_ADDRESS>:~ ₿
Watching the action here;
admin@<IP_ADDRESS>:~ ₿ sudo tail -n 1000 -f /mnt/hdd/bitcoin/debug.log
Looks like this is going to take a long time...

There are 3905 files that need to be reindexed.
admin@<IP_ADDRESS>:~ ₿ sudo ls -la /mnt/hdd/bitcoin/blocks/ | grep blk0 | wc -l
3905
admin@<IP_ADDRESS>:~ ₿

Watching the action here;
admin@<IP_ADDRESS>:~ ₿ sudo tail -n 1000 -f /mnt/hdd/bitcoin/debug.log
Looks like this is going to take a long time...

Progress update: 3266 blk0*.dat files reindexed out of 3905 total.  So 3266 * 3950 = 0.836363636 * 100 = 83.6363636% completed

Progress update: 3266 blk0*.dat files reindexed out of 3905 total.  So 3266 / 3950 = 0.836363636 * 100 = 83.6363636% completed

Progress update: it looks like all 3,266 of the blk0*.dat files were processed.
The reindex has moved on to the next phase.  This part is going super slow.  Looks like it will be a couple days yet...
This is what I see when doing sudo tail -n 1000 -f /mnt/hdd/bitcoin/debug.log:
2023-10-28T21:00:26Z UpdateTip: new best=000000000000000000b6f29a8a88b5418c3cc5abf17a15d43d8e1a06a1cef703 height=426013 version=0x20000000 log2_work=85.155665 tx=150547940 date='2016-08-20T08:49:49Z' progress=0.169829 cache=895.3MiB(5794686txo)
2023-10-28T21:00:27Z UpdateTip: new best=000000000000000004508f3efeb9b814dd5c9a6984bf695ed22ab86af7b24d26 height=426014 version=0x20000000 log2_work=85.155696 tx=150550075 date='2016-08-20T09:04:11Z' progress=0.169831 cache=895.4MiB(5795794txo)
2023-10-28T21:00:28Z UpdateTip: new best=000000000000000003124a980ca59758bb4d952229986a34057536651291aac3 height=426015 version=0x20000000 log2_work=85.155727 tx=150551887 date='2016-08-20T09:16:38Z' progress=0.169833 cache=895.5MiB(5795960txo)
2023-10-28T21:00:28Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2023-10-28T21:00:28Z UpdateTip: new best=0000000000000000039f100b08d8821dae5767b198966f7cbfe0c0ddc7be05d5 height=426016 version=0x20000000 log2_work=85.155758 tx=150552648 date='2016-08-20T09:20:38Z' progress=0.169834 cache=895.5MiB(5796173txo)
2023-10-28T21:00:33Z UpdateTip: new best=00000000000000000249d9ff629bf9a864871d081130bf4a12cf9eef8473129d height=426017 version=0x20000000 log2_work=85.155790 tx=150553342 date='2016-08-20T09:23:35Z' progress=0.169835 cache=895.8MiB(5799033txo)
2023-10-28T21:00:34Z UpdateTip: new best=00000000000000000250e79f84879993549008345e2e24f72c4212c7cd0a6202 height=426018 version=0x20000000 log2_work=85.155821 tx=150555894 date='2016-08-20T09:44:35Z' progress=0.169838 cache=896.0MiB(5800113txo)
2023-10-28T21:00:38Z UpdateTip: new best=00000000000000000270bb32f7d42ae03742bbc9124d349e10774d8cd7a57856 height=426019 version=0x20000000 log2_work=85.155852 tx=150556621 date='2016-08-20T09:45:39Z' progress=0.169839 cache=896.2MiB(5801650txo)
2023-10-28T21:00:38Z UpdateTip: new best=000000000000000000733817ff6a52cdea1ab4273bc68cfd55c223405818551c height=426020 version=0x20000000 log2_work=85.155883 tx=150557802 date='2016-08-20T09:54:20Z' progress=0.169840 cache=896.3MiB(5802549txo)
2023-10-28T21:00:39Z UpdateTip: new best=0000000000000000010a6212570a433c98b5b1f298a953f785a45ae9d1cb4c73 height=426021 version=0x20000000 log2_work=85.155915 tx=150559010 date='2016-08-20T10:02:35Z' progress=0.169841 cache=896.5MiB(5804306txo)
2023-10-28T21:00:39Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2023-10-28T21:00:41Z UpdateTip: new best=0000000000000000014392b28167efe78bb182d28b19a06b36f623833e1fd077 height=426022 version=0x20000000 log2_work=85.155946 tx=150560187 date='2016-08-20T10:09:26Z' progress=0.169843 cache=897.2MiB(5809760txo)
2023-10-28T21:00:42Z UpdateTip: new best=000000000000000001e7f96119eb022bfb5c82490a463022678bfd91a9471cb1 height=426023 version=0x20000000 log2_work=85.155977 tx=150563077 date='2016-08-20T10:38:34Z' progress=0.169846 cache=897.4MiB(5811763txo)
2023-10-28T21:00:43Z UpdateTip: new best=000000000000000003cf30612f29d23e7e5cf98390ec4ef5faab18a2cd68a57b height=426024 version=0x20000000 log2_work=85.156008 tx=150565544 date='2016-08-20T10:52:03Z' progress=0.169849 cache=897.6MiB(5813747txo)
2023-10-28T21:00:44Z UpdateTip: new best=0000000000000000007da31c882a318810f4f66812ed692d4e166fd7cd25f5d3 height=426025 version=0x20000000 log2_work=85.156040 tx=150567624 date='2016-08-20T11:09:12Z' progress=0.169851 cache=897.6MiB(5813781txo)
2023-10-28T21:00:45Z UpdateTip: new best=000000000000000003037d050fa86cdd17b8e0c670550e4f81c9b5cf5f5debb4 height=426026 version=0x20000000 log2_work=85.156071 tx=150569961 date='2016-08-20T11:37:47Z' progress=0.169854 cache=897.8MiB(5814663txo)
2023-10-28T21:00:46Z UpdateTip: new best=0000000000000000042feb02dc744796cdd3d04f011f1ebf841707b7f5d5b86a height=426027 version=0x20000000 log2_work=85.156102 tx=150572707 date='2016-08-20T11:50:34Z' progress=0.169857 cache=897.9MiB(5816120txo)
2023-10-28T21:00:46Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2023-10-28T21:00:46Z UpdateTip: new best=000000000000000000e90fa028a2fe7bffdc1fd43039ea32be9c476488e34841 height=426028 version=0x20000000 log2_work=85.156133 tx=150574048 date='2016-08-20T11:55:48Z' progress=0.169858 cache=897.7MiB(5813995txo)
2023-10-28T21:00:47Z UpdateTip: new best=000000000000000001d4a8dc1ec8b2562a0242d03b878ee293e8b3c9391b8abf height=426029 version=0x20000000 log2_work=85.156165 tx=150575905 date='2016-08-20T12:04:14Z' progress=0.169860 cache=897.7MiB(5814118txo)
2023-10-28T21:00:48Z UpdateTip: new best=0000000000000000040cc385a1ba9f582d66186a5415a1e666b2478e1b281782 height=426030 version=0x20000000 log2_work=85.156196 tx=150577504 date='2016-08-20T12:13:48Z' progress=0.169862 cache=898.7MiB(5822579txo)
2023-10-28T21:00:48Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications

I am going to Close this issue since it's quite obvious to me now that the corruption issue that I encountered was not a problem with Raspiblitz.
The only thing that I can think of that could possibly done would be for raspiblitz to give an informative error message about what the problem is if it sees a file missing like what happened with me after I deleted that file.
The error message that raspiblitz could look for would match this regex when parsing bitcoin's debug.log:
/^Fatal LevelDB error: Corruption: (\d+) missing files; e.g.: /mnt/hdd/bitcoin/indexes/txindex/(\d+).ldb$/
If such a match was found, the recommended action would be to say that a critical file was missing and that a reindex may be necessary to correct it.

I am going to Close this issue since it's quite obvious to me now that the corruption issue that I encountered was not a problem with Raspiblitz.
The only thing that I can think of that could possibly be done would be for raspiblitz to give an informative error message about what the problem is if it sees a file missing like what happened with me after I deleted that file.
The error message that raspiblitz could look for would match this regex when parsing bitcoin's debug.log:
/^Fatal LevelDB error: Corruption: (\d+) missing files; e.g.: /mnt/hdd/bitcoin/indexes/txindex/(\d+).ldb$/
If such a match was found, the recommended action would be to say that a critical file was missing and that a reindex may be necessary to correct it.

My node is still crunching it's way through the reindex.  Currently 28% complete.
Details on it will be tracked in https://lightningnetwork.plus/posts/468


[Enhancement] Print stack trace if cannot acquire lock for a long time

Print stack trace if cannot acquire lock for a long time. Used to
locate production environment deadlock issues.
Obtain stack trace through SQL:
> admin execute on 10006 '
for (s in ExecEnv.list_stack_trace_of_long_wait_mutex()) {
    System.print(s)
}
';

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

Ok, I'll update this later.

cache the trace to a global var, and make it available through a function like get_long_wait_mutex_info, bind it to the script engine

Updated, PTAL

@imay @wyb PTAL

How about adding some UT

How about adding some UT

OK

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0


 Es gibt keine Fehlermeldung.

(Windows 11, Firefox, Chrome, jeweils die neueste Version)

@phylor Did we have a device upgrade that maybe screwed this up?

There seems to be a problem with the cookies. When the login succeeds, the following is returned in the set-cookie header:
	["remember_user_token=...; path=/; expires=Sat, 08 Jun 2024 13:40:14 GMT; httponly; SameSite=Lax", "_wortschule_session=...; path=/; httponly; SameSite=Lax"]

This should be two cookies, but it seems both are wrapped in an array (starting with [" and ending with "]) and returned as one.
Unfortunately, I can't reproduce the issue locally.

See https://github.com/rails/rails/issues/48195
We probably need to downgrade.

@wintermeyer Could we use puma in production as well? Or do you want to stick with unicorn?

I don’t care. Puma is fine too.

Thank you both, for fixing this quickly and also all the other stuff! I am really happy this is getting better and better.


Manual output cache busting?

Is there any way to clear/flush/remove OutputCache?
I have html fragments in a partial view that uses the output cache like so
 <cache<EMAIL_ADDRESS>expires-after="@TimeSpan.FromHours(1)">

some content

 </cache>

In the event that I need the content to be updated before the expiration of the cache, how do I go about busting the cache for that particular fragment (or the entire cache, if necessary) ?

This issue was moved to aspnet/Mvc#4117


Float -> Decimal | PauseMode Variable

Change précision  Float to Decimal to avoid of strange round/precision representation
Add variable in config.example for pausemod

pleae make workable with latest code

I update with all last code !


execute go test as part of prow/presubmit.

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

none

@guptasu: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.
Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
42ff81071888c75bfa95bc0941e40901a056fea3
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
9745e68841656b98ec56d4d11e13bdbe9a4e9bc6
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
689b2829c70914740892623d82904b927475ef5a
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
c5511f76443efd6346bd02a45e471d8df88dd51c
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
55d825a56f8485f12a71bc50ebb7a98b39085805
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
270945e8075df801cb9952abbddbb45bd8f4cf5a
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
5208ca60999cd909627f3438eb716422abd20e3d
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
3b4a49c29ed45c317416d508ab6c7df6134b222a
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ba9255f8de8a11e067c80c6ce1afac813fba5779
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
2733d028ccaa07b0fad0f8d9e342c57df71f5d96
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
c37ce6ab9265c3020b8f94480127b26a5043b05c
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
c59b8950afd42e83ee0507cebb48db33942e912a
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
43db0a32f69a8867fa46d09fda9baf7f681f3f76
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
09c7620de84ab7901830cc276144de02b24ef360
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
d73835173fc2d5984541fab2dd95b1cf2872c34e
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
d73835173fc2d5984541fab2dd95b1cf2872c34e
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
5a23a9617a0498683a66f04d4601c31558089e0e
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
a65ef486fdaeddd43d1c7dfadb725c3d5f4bfc52
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
7499dad340ca5cd28a5adb1c5f4e6beb4968e3d3
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ed6503317f8dbd8cc97e8955c4ed96ae35f91995
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Handle manually invoked completion

The LSP spec allows users to invoke completion manually without typing anything.
This scenario is very different from what we currently handle because there's no target node. We simply need to show all possible completion items for the current receiver.
We will need to think about how addons can be invoked for this case and how they should enhance the base response. We may need to allow for a nil target intentionally and then define a special event for it.

Can that be triggered in VS Code?

It should be possible, although I'm not sure what's the right hotkey.

Ah, Ctrl-Space.


rails generate/g subcommands not completing

rails generate itself autocompletes, but past that, it just falls back to file completion... weird cause eg rails plugin  actually autocompletes to install remove (even though its really slow) so some subcommands are working...

I'm quite busy this weekend, but I'll see if I can have a look at that over the next one.

Really appreciate it! Let me know if you need any other debugging info
Also, my rails executable maps to ./bin/rails and is springified

Sorry for ignoring this for so long. Should be fixed now!


🌹 Add blog URL to settings page

~Fixes #437~
Edit: Doesn't actually solve #437

Lovely!
Sent with GitHawk

Oh ha, meant "add a url to the app on blog.githawk.com", but this is also nice! 😀

Dang, sorry bug I'm actually going to back out of this. The more I thought about it, it might end up just bloating the settings. I want to keep them as light as possible for now. Will revive if the need comes up!

Think at some point we should improve there. Think it can be better even at this point. Maybe declutter by having eg. the switches in a new vc, like accounts?
Sent with GitHawk


/ not working after update

Hello, thanks for the plug-in
I've encountered behavior that I don't believe is intended—after updating the plug-in, when using / to search for a keyword, the cursor is not moved to the search box, so the mouse must be used to get it there. Also, once a search term is entered, no highlight is presented—I don't think it is working.
Thank you, @vipzhicheng

Sorry for the issue, the update depends on a declaration to the market which was merged https://github.com/logseq/marketplace/pull/229, but I am not sure when it can take effect. So please try this feature later, I guess it may take effect after a new plugin was added to the market.


Compileing

I have 64bit g++ and I get errors when compiling
e:/saves/code/c++/Mapart/include/nbt.hpp: In member function ‘auto nbt::tags::compound_tag::put(std::string&&, T&&)’: e:/saves/code/c++/Mapart/include/nbt.hpp:838:17: error: ‘nbt::tags::compound_tag::value_type’ {aka ‘class std::map<std::basic_string<char>, std::unique_ptr<nbt::tags::tag> >’} has no member  named ‘insert_or_assign’   838 |    return value.insert_or_assign(std::move(name), std::make_unique<tag_of<T>>(std::move(item)));       |                 ^~~~~~~~~~~~~~~~ e:/saves/code/c++/Mapart/include/nbt.hpp: In member function ‘auto nbt::tags::compound_tag::put(const string&, T&&)’: e:/saves/code/c++/Mapart/include/nbt.hpp:843:17: error: ‘nbt::tags::compound_tag::value_type’ {aka ‘class std::map<std::basic_string<char>, std::unique_ptr<nbt::tags::tag> >’} has no member  named ‘insert_or_assign’   843 |    return value.insert_or_assign(name, std::make_unique<tag_of<T>>(item));       |                 ^~~~~~~~~~~~~~~~
What does this mean / how do I fix it?

Can you provide your system environment details and steps to reproduce this error? I need OS name, GCC version, Meson and Ninja version numbers that was used to build it to examine it.
As I understand, the software was build using g++ directly without Meson or Ninja. In that case. It's possible, that you missed flag -std=c++17.

Okay sorry about that. I am on win 10 64, gcc 10.2.0 through Cygwin 64.
Your fix worked but now I get more problems.
/usr/lib/gcc/x86_64-pc-cygwin/10/../../../../x86_64-pc-cygwin/bin/ld: CMakeFiles/Mapart.dir/Mapart.cpp.o:Mapart.cpp:(.data$_ZN3nbt4tags3endE[_ZN3nbt4tags3endE]+0x0): undefined reference to vtable for nbt::tags::end_tag'
/usr/lib/gcc/x86_64-pc-cygwin/10/../../../../x86_64-pc-cygwin/bin/ld: CMakeFiles/Mapart.dir/Mapart.cpp.o:Mapart.cpp:(.data$_ZN3nbt4tags8end_listE[_ZN3nbt4tags8end_listE]+0x0): undefined reference to vtable for nbt::tags::end_list_tag' /usr/lib/gcc/x86_64-pc-cygwin/10/../../../../x86_64-pc-cygwin/bin/ld: CMakeFiles/Mapart.dir/Mapart.cpp.o:Mapart.cpp:(.rdata$.refptr._ZTVN3nbt4tags12end_list_tagE[.refptr._ZTVN3nbt4tags12end_list_tagE]+0x0): undefined reference to vtable for nbt::tags::end_list_tag'
/usr/lib/gcc/x86_64-pc-cygwin/10/../../../../x86_64-pc-cygwin/bin/ld: CMakeFiles/Mapart.dir/Mapart.cpp.o:Mapart.cpp:(.rdata$.refptr._ZTVN3nbt4tags7end_tagE[.refptr._ZTVN3nbt4tags7end_tagE]+0x0): undefined reference to vtable for nbt::tags::end_tag' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/Mapart.dir/build.make:104: Mapart.exe] Error 1 make[1]: *** [CMakeFiles/Makefile2:96: CMakeFiles/Mapart.dir/all] Error 2 make: *** [Makefile:104: all] Error 2
You can see the code here: https://github.com/Polarbub/Mapart-Program/tree/master
Also thank you for your help :)

There are source file src/nbt.cpp that should be compiled independently and linked with your code. It uses src/nbt_internal.hpp header, that also should be added to your project. I didn't found them in your repository, so I assume this is the reason.


typo: excercises

https://lifecycle.keptn.sh/docs/getting-started/ contains the typo above.

Hey, @agardnerIT just wanted to know, are you planning to open a PR for this?

Please assign it to me, I want to work on it

@Saurav-Pant thanks for volunteering, we assigned you to the issue 🚀

Thanks @RealAnna  , I will work on it


[QUERY] Is it possible to delete a Blob through a BlobItem?

Query/Question
I'm converting a logic from an old library to a new one. In here, I'm getting all blobs from a container, filtering it by the LastModified property, and then deleting it. With the old library, I could do this in a very straight foward manner:
        var storageConnectionString = ConfigurationManager.ConnectionStrings["AzureWebJobsStorage"].ConnectionString;
        CloudStorageAccount storageAccount = CloudStorageAccount.Parse(storageConnectionString);
	CloudBlobClient blobClient = storageAccount.CreateCloudBlobClient();

	var containerHostArchive = blobClient.GetContainerReference("azure-jobs-host-archive");
	if (containerHostArchive.Exists())
	{
		var blobsHostArchive = containerHostArchive
			.ListBlobs()
			.OfType<CloudBlob>()
			.Where(b => b.Properties.LastModified < new DateTimeOffset(DateTime.Now.AddDays(-RETENTION_DAYS_JOBS_LOGS)))
			.ToList();

		foreach (var item in blobsHostArchive)
		{
			item.DeleteIfExists();
		}
	}

In the new library, I'm not finding a easy way to do this. I have to make two access to the storage, first one to find the BlobItems from a container, the second to get a reference to the BlobClient so I can delete it (see bellow):}
                var blobContainerClient = storageWrapper.GetContainerReference(_connectionString, containerName); //Returns a BlobContainerClient
                var dateLastWeek = DateTime.Now.AddDays(-7);

                var desiredBlobs = blobContainerClient
                    .GetBlobs()
                    .ToList()
                    .Where(x => x.Properties.LastModified < dateLastWeek)
                    .ToList();

                var blobsToDelete = desiredBlobs
                    .Select(blob => storageWrapper.GetBlobReferenceNew(_connectionString, containerName, blob.Name)) //GetReferenceNew returns a BlobClient
                    .ToList();

                blobsToDelete.ForEach(blob => blob.DeleteIfExists());

Is there a way to do this without accessing the storage twice?
Environment:

.Net Version: Full Framework 4.8
Original version: Microsoft.WindowsAzure.Storage.Blob <IP_ADDRESS>
New version: Azure.Storage.Blobs v12.8.0
IDE and version : Visual Studio 16.8.5

This functionality is not supported by the SDK.  BlobItem is a model, BlobClient is a client.  This is a well established pattern in the new SDKs across Azure.

I have to make two access to the storage, first one to find the BlobItems from a container, the second to get a reference to the BlobClient so I can delete it

Getting a refence to a BlobClient doesn't actually make a REST call into the service, it just creates a new BlobClient locally.  Same for newing up a BlobContainerClient
No matter what the SDK APIs look like, there is going to be a call into the storage service to list the blobs in a container, and another call for each blob you would like to delete.
-Sean


IP is leaked

I have set this up and deployed on lightsail. My client phone connects successfully via wireguard. However , my original IP is still being leaked rather than using the lightsail’s IP. I can’t figure out what’s wrong and why the IP leaking is happening?
I have not changed anything on the instance since cloudblock after deployed.

hey @rxng - What value did you set for vpn_traffic here? This setting configures the wireguard clients that are generated.
If you deployed with the value set to dns - only your DNS traffic is routed via wireguard VPN.
If you want to change the behavior to all traffic, open wireguard on your phone and edit the imported VPN profile. Set the allowed IPs field to <IP_ADDRESS>/0.

Thanks for the reply @chadgeary , I managed to fix it by changing the allowed IPs.
I may change the vpn_traffic and redeploy rather than manually changing the allowed ips each time!
also wondered why create extra s3 resource if we can use the lightsail instance itself to host the files? As it would be an extra cost.

Glad it’s resolved ☀
For S3 it’s a matter of low cost backup and convenience.
Along with the client configs, the pihole and wireguard data directories are stored here in the event the instance needs to be rebuilt or exported.


TS 5.1.3 Regression: TSC Compiler throws FATAL ERROR: Reached heap limit Allocation failed

Bug Report
🔎 Search Terms
tsc, compiler, heap limit, crash, memory
🕗 Version & Regression Information

This is a crash
This changed between versions 5.0.4 and 5.1.3

⏯ Repository Link
https://github.com/virtuallyunknown/tsc-error
💻 Code
To reproduce the error, clone the repository and run the build script or just npx tsc.
git clone https://github.com/virtuallyunknown/tsc-error.git && cd tsc-error
npm install
npx tsc

🙁 Actual behavior
Running the typescript compiler (tsc) from project root causes the build to fail and produce this error:
<--- Last few GCs --->

[43355:0x6bd0ae0]     9563 ms: Scavenge 4038.1 (4116.6) -> 4037.2 (4117.8) MB, 4.5 / 0.0 ms  (average mu = 0.538, current mu = 0.113) allocation failure;
[43355:0x6bd0ae0]     9572 ms: Scavenge 4039.0 (4117.8) -> 4038.2 (4138.6) MB, 8.4 / 0.0 ms  (average mu = 0.538, current mu = 0.113) allocation failure;
[43355:0x6bd0ae0]    10371 ms: Mark-Compact 4052.2 (4138.6) -> 4048.8 (4152.1) MB, 794.9 / 0.0 ms  (average mu = 0.390, current mu = 0.040) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0xbf9890 node::Abort() [node]
 2: 0xaf6859  [node]
 3: 0xddaf80 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0xddb336 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 5: 0xfd9db5  [node]
 6: 0xfed4e5 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 7: 0xfc924f v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 8: 0xfca297 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 9: 0xfa99fa v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
10: 0x13bd76f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
11: 0x18443f9  [node]
Aborted (core dumped)

I also tried typescript@next, but that doesn't fix it. I also tried this command:
NODE_OPTIONS=--max-old-space-size=28000 npx tsc --noEmit  --diagnostics --extendedDiagnostics --incremental false
but it crashes with a different error after a while.
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)

🙂 Expected behavior
Running the typescript compiler (tsc) command compiles the build successfully after 1-2 seconds, just like it did in 5.0.4.

Can confirm. Not only does it crash, but it also cause the transpile time to increase by ~x6 before the crash happens.

bisected to https://github.com/microsoft/TypeScript/pull/53672 , cc @ahejlsberg

The problem originates in @sapphire/shapeshift and its ArrayValidator. A reduced test case is this:
type UnshiftTuple<T extends [...any[]]> = T extends [T[0], ...infer Tail] ? Tail : never;
type ExpandSmallerTuples<T extends [...any[]]> = T extends [T[0], ...infer Tail] ? T | ExpandSmallerTuples<Tail> : [];
type Shift<A extends Array<any>> = ((...args: A) => void) extends (...args: [A[0], ...infer R]) => void ? R : never;
type GrowExpRev<A extends Array<any>, N extends number, P extends Array<Array<any>>> = A['length'] extends N ? A : GrowExpRev<[...A, ...P[0]][N] extends undefined ? [...A, ...P[0]] : A, N, Shift<P>>;
type GrowExp<A extends Array<any>, N extends number, P extends Array<Array<any>>> = [...A, ...A][N] extends undefined ? GrowExp<[...A, ...A], N, [A, ...P]> : GrowExpRev<A, N, P>;
type Tuple<T, N extends number> = number extends N ? Array<T> : N extends 0 ? [] : N extends 1 ? [T] : GrowExp<[T], N, [[]]>;

declare class ArrayValidator<T extends unknown[], I = T[number]> {
    lengthRange<S extends number, E extends number>(start: S, endBefore: E): ArrayValidator<Exclude<ExpandSmallerTuples<UnshiftTuple<[...Tuple<I, E>]>>, ExpandSmallerTuples<UnshiftTuple<[...Tuple<I, S>]>>>>;
}

You can use this TS playground to verify this. Just wait for a moment - you will see that the browser tab crashes.
I reduced this to the lengthRange method but in the regression test you might also want to include other methods from this class from the same length* "family". They all do complex things with arrays/tuples.

Might be related to https://github.com/microsoft/TypeScript/issues/54348 as well ?

The issue appears to be runaway type instantiation as the compiler is attempting to compute variance information. That logic relies on our various depth limiters to catch infinite recursion, but apparently that doesn't happen fast enough here.
A quick workaround for now is to change the declaration of the Tuple type to
type Tuple<T, N extends number> = N extends number ? number extends N ? Array<T> : N extends 0 ? [] : N extends 1 ? [T] : GrowExp<[T], N, [[]]> : never;

That is, introduce a sanity check that N is actually a number and resolve to never if not. This would seem unnecessary since N is constrained to number, but variance computation introduces special marker types that (by design) aren't related to anything else.

Just wait for a moment - you will see that the browser tab crashes.

Isolated tabs are a wonderful thing.  I still remember the days when this kind of thing would have taken out the entire browser.
Still a bit alarming that any JS code is able to outright crash a process (and thereby cause a DoS), though.

Many thanks for the fix that we can apply @ahejlsberg! We'll release an update for @sapphire/shapeshift ASAP so I think this issue can be closed.

You guys are legends for fixing this so quickly, thanks to everyone involved!
If my understanding is correct, we now wait for the next TS release where this is backported, or just use the nightly version?

I also encountered this issue in my node discord.js project after upgrading from TypeScript 5.0.4 to 5.1.3. Enabling the skipLibCheck option has resolved it for now. Looking forward to the fix!

I also encountered this issue in my node discord.js project after upgrading from TypeScript 5.0.4 to 5.1.3. Enabling the skipLibCheck option has resolved it for now. Looking forward to the fix!

As @sapphire/shapeshift update has been rolled out you can update the transient dependency with your package manager:
npm
I cannot find anything for npm to do a transitive dependency update so you'll have to provide overrides until @discordjs/builders releases an update (and subsequently discord.js). If someone knows a way to update transitive dependencies with npm please do correct me.
In your package.json:
{
  "overrides": {
    "@sapphire/shapeshift": "3.9.2"
  }
}

Then run npm install. You can verify the change by checking your package-lock.json
Yarn v1
Yarn v1 (deprecated, recommend updating to v3) does not have a way to update transitive dependencies so a similar strategy is required as npm:
In your package.json:
{
  "resolutions": {
    "@sapphire/shapeshift": "3.9.2"
  }
}

Then run yarn install. You can verify the change by checking your yarn.lock
Yarn v3
Yarn v3 can update transitive dependencies so run the command:
yarn up -R @sapphire/shapeshift

pnpm
pnpm can also update transitive dependencies so run the command:
pnpm --recursive update<EMAIL_ADDRESS>


Update contributing doc with copyright message info

@nicolasnoble

Test failures are infrastructural or existing:
Bazel RBE MSAN C/C++: https://github.com/grpc/grpc/issues/20814
Interop cloud-to-cloud tests: https://github.com/grpc/grpc/issues/19437
Interop Cloud-to-prod tests: https://github.com/grpc/grpc/issues/20793


Wordpress chart on bare metal

Hello,
I'm trying to install stable/wordpress chart in a bare metal installation of kubernetes and I'm getting this message:
19s        5s        3    {kubelet minion1}   Warning        FailedSync    Error syncing pod, skipping: failed to "StartContainer" for "exasperated-quokka-wordp" with RunContainerError: GenerateRunContainerOptions: secrets \"exasperated-quokka-maria\" not found"
I configure persistence as false and service type as Node port.
Those are the available secrets:
default-token-ecxnm        kubernetes.io/service-account-token   3         14d
exasperated-quokka-wordp   Opaque                                2         18h
jittery-fly-secret         Opaque                                2         14d
masked-shrimp-secret       Opaque                                2         14d
mewing-narwhal-secret      Opaque                                2         14d

There is no mariadb secrets because there is no mariadb charts installed. I thought charts dependencies should be included, doesn't it?
Am I missing something?
I followed the kubernetes start guide with ubuntu xenial and kubeadm with flannel network overlay. It is a quite standard installation of Kubernetes.

Hey @nordri, if you're installing from a local directory, you need to run helm dep update ./wordpress to fetch the MariaDB dependency. You should then be able to run helm upgrade exasperated-quokka ./wordpress or delete and re-deploy to fix your issue.


Default logger needs to mark itself as helper to avoid the line numbers

Right now, the default logger does not call the helper function, so it ends up logging an extraneous line number logger.go:66:.

Hmm this didn't have the expected effect so will close.


Allow Symfony 7

@alexander-schranz any chance you have time to review this one? Would love to upgrade to Symfony 7 myself 🙂

@ker0x Thx for the pull request can you rebase it to the latest changes of 0.2?
@ToshY I will try to find some time this week to test this.

Hello @alexander-schranz , it's done 👍

@ker0x Thank you!


hit_test_text_position bug?

Hello!
I'm working on some text features for piet and ran into an issue.
I'm trying to use hit_test_text_position, and the trailing bool appears to give me the opposite edge than what I expect. I'm wondering if the bool -> int conversion at https://github.com/Connicpu/directwrite-rs/blob/master/src/text_layout/mod.rs#L488 is backwards.
Thanks!

Oops you're totally right, that's backwards! I don't know why I didn't just use as i32 heh, I'll have it fixed soon.

Thanks! It would also be great if you could release a 0.1.5, since piet is not yet on 0.3.0.


Compatibility with standard async

Can this be used as a general executor for futures? Or maybe to make rayon work on different workers?
I have been trying to find a way to make my program work on wasm, but since it has heavy computations, it take a very long time to process without multi-threading (There are some encryption decryption on very large files). So I made my program using the asynchronous paradigm of rust to pipeline my process, and a little bit of parallel processing with rayon (both of which work very well when compiled on windows). But when I compile it for Wasm, I rayon isn't able to launch its executor threads. So I was wondering if there was a way to make this executor work with rayon, or if I would have to re implement the functionality I need from rayon myself using this.

Can this be used as a general executor for futures?

Yes, based on wasm_mt::Thread, you can implement a wide variety of custom executors for Rust futures (such as the toy executors in README and more practical wasm-mt-pool) in a fairly general manner.  But, please note that,  for any Rust futures involved here, their actual entity is a JavaScript Promise whose conversion is facilitated by wasm-bindgen.
After seeing this example in wasm-bindgen, I guess it's also possible to adapt wasm-mt-pool to being used with rayon.

So I was wondering if there was a way to make this executor work with rayon, or if I would have to re implement the functionality I need from rayon myself using this.

I would suggest, maybe, you put aside the (possibly laborious) rayon adaptation for the moment.  Instead, just try executing your parallel tasks with wasm-mt-pool to see if it works as you expect.


Documentation for manifest release output example

TL;DR
When using a manifest the action outputs track the release information per package, but there is no documentation on how that is presented to the user.
Detailed design
It appears that output after creating releases should be outputting the package specific release information. But what does that look like in the final output?
For example:
- name: Deploy package-a docs to prod
  # Code shows it uses the path for the release.
  # if: ${{ steps.release.outputs.${path}--release_created }}
  # But if the package is in a sub directory do you use a slash?
  # if: ${{ steps.release.outputs.packages/package-a--release_created }}
  # Or does it transform the directory and output differently?
  # if: ${{ steps.release.outputs.packages.package-a--release_created }}
  run: echo "Deploy package-a docs to prod... ${{ steps.release.outputs.packages.package-a--tag_name }}"

See #297


ci: update to CIclops 1.2.0

among other improvements, CIclops 1.2.0 monitors for systematic
failures, and if there are any, sends them via Slack (see grab below).
Note a run with forced systematic failures: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/4860511703
And the automated slack message triggered:

/test

/ok-to-merge


Information for trouble-shooting page.

This is from my notes over the last few days, and I wanted to store them, to be put in a troubleshooting page or FAQ.

"serial.serialutil.SerialException: write failed: [Errno 5] Input/output error"

One cause for this is if your LED lights aren't powered (in my case, the power supply had become unplugged).  You might see the lights work until many of them are lit up - and then crash when the processor can no longer output enough power.
We might also catch this specific error and annotate it with a suggestion when we print it (we do quite a lot of that).

SyntaxError: invalid syntax during installation of BP..

This is a normal part of the Jinja installation and can be ignored.  (I knew this, both others might not.)

I'll add more here as these show up and we can eventually move this to publicly-visible documentation.

Regarding #1: What's actually happening there is you are USB powering and
when you start, it draws more than 500mA and the poly fuse on the AllPixel
trips. Fortunately it's a poly fuse, so it resets after removing power. But
I wanted to be specific about the reason.
On Wed, Dec 20, 2017 at 5:21 AM, Tom Swirly<EMAIL_ADDRESS>wrote:

This is from my notes over the last few days, and I wanted to store them,
to be put in a troubleshooting page or FAQ.

"serial.serialutil.SerialException: write failed: [Errno 5]
Input/output error"

One cause for this is if your LED lights aren't powered (in my case, the
power supply had become unplugged). You might see the lights work until
many of them are lit up - and then fail to work.
We might also catch this specific error and annotate it with a suggestion.

SyntaxError: invalid syntax during installation of BP..

This is a normal part of the Jinja installation and can be ignored. (I
knew this, both others might not.)
I'll add more here as these show up and we can eventually move this to
publicly-visible documentation.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/546, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AA6a6kGW7ifDvVElCFrCGlVT70dm87amks5tCN--gaJpZM4RILmx
.

Note that someone seemed to have just that trouble a few minutes after I
posted this!  :-D
On Wed, Dec 20, 2017 at 2:20 PM, Adam Haile<EMAIL_ADDRESS>wrote:

Regarding #1: What's actually happening there is you are USB powering and
when you start, it draws more than 500mA and the poly fuse on the AllPixel
trips. Fortunately it's a poly fuse, so it resets after removing power. But
I wanted to be specific about the reason.
On Wed, Dec 20, 2017 at 5:21 AM, Tom Swirly<EMAIL_ADDRESS>wrote:

This is from my notes over the last few days, and I wanted to store them,
to be put in a troubleshooting page or FAQ.

"serial.serialutil.SerialException: write failed: [Errno 5]
Input/output error"

One cause for this is if your LED lights aren't powered (in my case, the
power supply had become unplugged). You might see the lights work until
many of them are lit up - and then fail to work.
We might also catch this specific error and annotate it with a
suggestion.

SyntaxError: invalid syntax during installation of BP..

This is a normal part of the Jinja installation and can be ignored. (I
knew this, both others might not.)
I'll add more here as these show up and we can eventually move this to
publicly-visible documentation.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/546, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/
AA6a6kGW7ifDvVElCFrCGlVT70dm87amks5tCN--gaJpZM4RILmx>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/546#issuecomment-353061221,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdskgBVpqqMnn5sRQrxoAUMC07eyKxks5tCQmfgaJpZM4RILmx
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com


Redesign: Keyboard shortcuts dialog

Feature Description
Update keyboard shortcut dialog based on Figma.

[x] Update dialog content as per design
[x] Update dialog placement and background as per design
[x] Make sure dialog scrolls correctly on a smaller viewport

Current design
New large viewport
New small viewport

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Some cutoff along right edge. Seeing this on PC only (looked fine in Mac/Chrome)

Some cutoff along right edge. Seeing this on PC only (looked fine in Mac/Chrome)

Thank you for this - hadn't considered that. Have brought it up with UX!

Awaiting UX decision by @samitron7 in this thread.

@barklund If we reduce the white spacing inside the button, I think it'll fit. Let me know if this works Figma

@barklund If we reduce the white spacing inside the button, I think it'll fit. Let me know if this works Figma

This has now been implemented - back to you, @csossi!

Mac
Windows

Verified in QA


snap is no longer free for private repo

https://snap-ci.com/my_plans/
private repos for as little as $30/mo

AFAIU public repos are still for free but with limitations, so nothing to fix.

Snap is Going Away
https://blog.snap-ci.com/blog/2017/02/06/2017-02-06-snap-announcement/

It was removed.

It was removed.


added support for $ne operator

Describe your changes
Added support for $ne comparison operator in query/filter, to test not-equal
How best to test these changes
Added tests to query/filter/comparison_test.go
Issue ticket number and link
/claim #873 for algora bounty

Overall, it is the right direction. But change it like this,

$ne will implement LikeMatcher interface
Then this matcher will be used by LikeFilter, which you'll add in the second case in filter.go at line 359.
The reason for doing it this way is that we don't want to implement keys from this filter and mainly only want to use it for filtering.

Once this is done, please add a test in test/v1/server/document_test.go where we have other Read API integration tests.

Overall, it is the right direction. But change it like this,
* `$ne` will implement `LikeMatcher` interface

* Then this matcher will be used by `LikeFilter,` which you'll add in the second case in `filter.go` at line 359.
  The reason for doing it this way is that we don't want to implement keys from this filter and mainly only want to use it for filtering.

Once this is done, please add a test in test/v1/server/document_test.go where we have other Read API integration tests.

If I'm understanding correctly, do you mean that $ne should only implement LikeMatcher, or should it also implement ValueMatcher? Also, is the purpose of $ne to do exact string comparison, as opposed to $not which is more like 'does not contain'?

Overall, it is the right direction. But change it like this,

* `$ne` will implement `LikeMatcher` interface

* Then this matcher will be used by `LikeFilter,` which you'll add in the second case in `filter.go` at line 359.

  The reason for doing it this way is that we don't want to implement keys from this filter and mainly only want to use it for filtering.

Once this is done, please add a test in test/v1/server/document_test.go where we have other Read API integration tests.

If I'm understanding correctly, do you mean that $ne should only implement LikeMatcher, or should it also implement ValueMatcher? Also, is the purpose of $ne to do exact string comparison, as opposed to $not which is more like 'does not contain'?

That's right only LikeMatcher. Correct $ne is for exact not equality comparison.

Looks good, can you rebase it, and I'll merge it.


Revert "Re-save the .rbxmx file to prevent Rojo issues"

Reverts Epix-Incorporated/Adonis#1173
@Sceleratis I think I re-saved the bugged ones.
I'll re-submit them with a fixed version. Idk what reverting does, if it doesn't remove it from the commits, for anyone that wants to pull from this repository, then it's pointless to merge this.

@Expertcoderz could you please do this to prevent potential catastrophes

took you long enough expertcoderz...


polish

First couple of intents in pl-pl including:

play
like song
stop
next
resume
read
prev
global stop
pause
open
feature
play faves
media stop

hello! thanks for the contribution
these files are not meant to be edited directly, but rather they are managed from https://gitlocalize.com/users/OpenVoiceOS
please resubmit the translations via the translations portal, as they might get overwritten otherwise

just noticed polish was missing in our webportal, i will add it!


Added descriptive text to the Talk Media section of the talk form

Closes #860

Looks like the only thing blocking this is an approval, which should be quick given the small diff. @heiglandreas @iansltx


Silent failure with missing artifact during publish to DependencyTrack

I have added the publish to DependencyTrack to my pipeline however during testing I noticed that if it could not find the artifact the build would fail in the console output it would not really state that it was a hard failure.  Looking at the pipeline steps every stage would show success making harder to determine the cause of the failure.
From the logs

........
[Pipeline] dependencyTrackPublisher
[DependencyTrack] Publishing artifact to Dependency-Track
[DependencyTrack] The specified artifact does not exist
........
Finished: FAILURE

This ticket should probably be opened on the dependency-track project: https://github.com/DependencyTrack/dependency-track
--Jeremy

Do they manage the dependency-check upload to dependency-track portion if the Jenkins plugin because the issue is somewhere in that process.  I am unsure who owns that portion of code being that the dependencyTrackPublisher step in my Jenkinsfile comes from the dependency-check plugin.

The Dependency-Track publisher is part https://github.com/jenkinsci/dependency-check-plugin
However, I don't think there's a whole lot that can be done to improve this issue. Plugins have the ability to set the build status to:

SUCCESS
UNSTABLE
FAILURE
NOT_BUILT
ABORTED

If the dependency-check report specified in the job config doesn't exist when it attempts to upload it to Dependency-Track, the plugin will log The specified artifact does not exist to the console and set the build to FAILURE. The issue you're describing seems to be more of a Jenkins usability issue. There should be a better way to find out which step in the pipeline had an issue, and I agree.
If there are other things that can be done in the plugin to improve visibility into which step caused the issue, please open a PR and submit an issue to https://issues.jenkins-ci.org.

Is there a way to fail the step vs the build so you can see where the failure is?  I was using the verbiage described in another plugin that users were reporting similar results.  Probably the best known is in archiveArtifacts on https://issues.jenkins-ci.org/browse/JENKINS-38005
There is two PR with different ways of failing the step and/or better log messages.  Not very good at Java but I will try to see what I can do to help.
https://github.com/jenkinsci/jenkins/pull/2823
https://github.com/jenkinsci/workflow-basic-steps-plugin/compare/86af7fdf73cd...05bf1fb6446d


i18n(zh-CN): Update translations in v3.mdx, images.mdx and typescript.mdx

What kind of changes does this PR include?

Translated content

Description
Translate content added in #4446, #4447, #4495 and #4498.

建议同个文件合并到一个PR进行提交，一旦 PR被合并之后，该页面的翻译状态就会被标记成完成

@Genteure 我在英文原文有一个新提交：https://github.com/withastro/docs/pull/4464

I have updated this PR accordingly.

I have rebased the changes onto current main and added changes made in those two PRs.


[#122200041] Merge integrations conf from 3rd party jobs

https://www.pivotaltracker.com/story/show/122200041
NOTE: dependencies and next steps.
This is a copy of the upstream PR https://github.com/onemedical/datadog-agent-boshrelease/pull/7, so we can use it meanwhile it is not merged upstream.
This PR includes a commit to change the bucket for blobs, as it adds a new blob for spruce. The bucket is configured in https://github.com/alphagov/paas-bootstrap/pull/2
This PR include commits from #4, which should be merged first and this PR reviewed.
Next steps
After this PR has been merge, we must create a binary "development release" and upload it to github as a binary release. We do it so as a temporary solution meanwhile we do not implement a process to build our own releases with a CI server. We require a binary dev release instead of build it every time because this release is also used by concourse and bosh with bosh-init.
bosh create release --with-tarball --name datadog-agent --version custom_007

Update the PR https://github.com/alphagov/paas-cf/pull/521 once is done.
We uploaded a temporary release: https://github.com/alphagov/paas-datadog-agent-boshrelease/releases/tag/wip.122200041.1, it can be deleted later.
What?
Datadog bundles several additional checks[1] that can run on the host from the collector. These checks usually require some configuration in the ${DD_AGENT_DIR}/conf.d/[2].
This configuration is in form of YAML files.
Currently we generate these files in the collector ctl script from the manifest properties, but third party releases might also want to  extend datadog to monitor local services using these additional integrations.
To solve that, this commit adds logic to merge all files from jobs which follow this pattern:
${JOB_PATH}/config/datadog-integrations/${checkname}.yaml

For example:
/var/vcap/jobs/datadog-router/config/datadog-integrations/process.yaml

The script will use spruce[3] to merge all the configurations in one unique file per check, as datadog agent expects.
We also extract the logic to generate the integrations config from the manifest to a external helper file, and make it generate the files using the pattern described above.
[1] http://docs.datadoghq.com/integrations/
[2] https://github.com/DataDog/dd-agent/tree/master/conf.d
[3] https://github.com/geofffranks/spruce
How to test this?
You can test this configuration together with the https://github.com/alphagov/paas-datadog-for-cloudfoundry-boshrelease/pull/1 which implements an example of this logic.
Follow the instructions in https://github.com/alphagov/paas-datadog-for-cloudfoundry-boshrelease/pull/1, with bosh-lite, but using a manifest like this. Change the api_key of datadog if you want to test if the metrics get there. The metrics will be in the form of system.process.*, tagged with the name of the machine.
---
name: learn-bosh
director_uuid: fb70f16a-4d6f-41f8-bc2e-0181a03dff18

releases:
- name: datadog-agent
  version: latest
- name: datadog-for-cloudfoundry
  version: latest
- name: routing
  version: "0.138.0"
  url: https://bosh.io/d/github.com/cloudfoundry-incubator/cf-routing-release?v=0.138.0
  sha1: 10a4bc79b8a32e4120760291975810f3855119a8
- name: nats
  version: "13"
  url: https://bosh.io/d/github.com/cloudfoundry/nats-release?v=13
  sha1: bc405a67de529a9aad41ca0cf618a522d9d2b310

networks:
- name: default
  subnets:
  - range: <IP_ADDRESS>/28
    reserved: [<IP_ADDRESS>]
    static: [<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>]
    cloud_properties:
      name: random

resource_pools:
- name: default
  stemcell:
    name: bosh-warden-boshlite-ubuntu-trusty-go_agent
    version: "3262.2"
  network: default
  cloud_properties: {}

compilation:
  workers: 2
  network: default
  cloud_properties: {}

update:
  canaries: 1
  canary_watch_time: 60000
  update_watch_time: 10000-300000
  max_in_flight: 2

jobs:
- name: nats
  templates:
  - name: nats
    release: nats
  instances: 1
  resource_pool: default
  networks:
  - name: default
    static_ips:
    - <IP_ADDRESS>

- name: app
  templates:
  - name: datadog-agent
    release: datadog-agent
  - name: datadog-router
    release: datadog-for-cloudfoundry
  - name: gorouter
    release: routing

  instances: 1
  resource_pool: default
  networks:
  - name: default
    static_ips:
    - <IP_ADDRESS>
properties:
  api_key: ....
  hostname: hehe
  tags:
    env: bosh-lite
  router:
    enable_ssl: false
    requested_route_registration_interval_in_seconds:
    ssl_skip_validation:
    status:
      port:
      user: router_user
      password: password
    secure_cookies:
    route_services_secret:
    route_services_secret_decrypt_only:
    route_services_timeout:
    logrotate:
    extra_headers_to_log:
    debug_address:
    enable_routing_api:
    drain_wait: 15
  nats:
    port: 4222
    machines:
    - <IP_ADDRESS>
    debug: false
    trace: false
    monitor_port: 0
    prof_port: 0
    user: nats_user
    password: aaa
  uaa:
    clients:
      gorouter:
        secret: 1234
    ssl:
      port: 123

Who?
Anyone but @richardc or @keymon

I am happy this does the job. What I need clarification on is where we test our configuration. Do we or can we set up alerts when certain metrics are not being received by Datadog? If so, we can assert the configuration is correct from that end. If not, how do we know configuration changes don't break anything or cause regressions?

Good point.
I don't have an answer about that, but the issue will be the same for any kind of strategy used to configure the agent.

I have removed the temporary commit, merged this pull request, and created the dev release: https://github.com/alphagov/paas-datadog-agent-boshrelease/releases/tag/custom_007


Sending Arrays in Redis Multi Commands

While chaining multiple commands to client.multi(), the commands only accepted comma separated arguments directly. I made a small change in the index file that allows params to be passed in arrays. The command was earlier being sent to the queue as a multi dimensional array which made the command fail.
Therefore earlier, only client.multi().zadd('foobar', 1, 'foo', 2, 'bar' ) was getting accepted.
With the new change, the command can be sent as
client.multi().zadd(['foobar', 1, 'foo', 2, 'bar']) or
client.multi().zadd('foobar',[ 1, 'foo', 2, 'bar'])
and it would work correctly. It would be a very useful fields for commands where multiple arguments need to be passed. I personally thought it was possible until the code returned with nothing.
Hope we can consider this change. I have also written a test MULTI_9 which passed.

:+1:

Needs a rebase. Otherwise LGTM

Seems like a reasonable patch to get out in version 2.0 to me too.

Closing this in favor of #838


Consider how to migrate applications using Windows auth

Summary
There should be some way to handle Windows auth, or at least documentation to direct users how to migrate.
Motivation and goals
The remote app setup allows for sharing some remote authentication schemes. However, Windows auth does not currently work in this set up. We should identify how to direct users in situations like this.

This is related to #109 (we can likely solve them both at the same time).

interested to see how and when can make directional progress...

Any progress on this?


Enable explainers to work with ModelMesh

What this PR does / why we need it:
Currently explainers don't work when the inference service deploymentMode is ModelMesh. This PR enables KServe explainers to work with ModelMesh.
Which issue(s) this PR fixes:
Fixes #2388
Type of changes

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Feature/Issue validation/testing:
The alibi cifar10 explainer example is updated with ModelMesh annotation and used to validate the changes.
Special notes for your reviewer:

The controllers are changed to wait for predictor status and provide predictor protocol for explainers to adjust payloads and innovation
Ingress reconciler is updated to bypass predictor route when deploymentMode is ModelMesh
Alibi explainer is enhanced with logic to handle additional predictor protocols, REST v2 and gRPC
AIX, AIF, ART are unchanged since these don't use framework based servingtimes for predictors, not suitable for ModelMesh
The default triton server in ModelMesh is not configured to support batch size > 1. Manual configuration (max-batch-size>=100) is needed to make the alibi cifar10 explainer to work.

Release note:
KServe explainers are now enabled to work with ModelMesh. Please note the Triton server in ModelMesh has to be configured with max-batch-size=100 or more for the Alibi cifar10 explainer to work.

@yuzisun Wondering if you can take a look?

@yuzisun Wondering if you can take a look?

Sorry I will be back from vacation tomorrow, will get this done this week.

@yuzisun Thanks for the review. Sorry, being tied with other things. Will get back to your comments shortly.

HI all, is this issue still relevant?

Is this issue still valid?


VSCodeHook to communicate with vscode, sending start-end events and http logs.

RuntimeHook to comunicate with vscode, sending start-end events and http logs in real time.

Relevant Issues : #1389
Relevant PRs : (optional)
Type of change :

[x] New feature
[ ] Bug fix for existing feature
[ ] Code quality improvement
[ ] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

@ivangsa seems to be a custom requirement, does not need to be in core IMO

@ptrthomas yes is a custom requirement but it would help adoption if provided by karate and users don't need to add it
it will not affect other users as is a separte hook
would you consider adding this?

@ivangsa I don't think this will make it into 1.0 for sure. it also is an area that needs time to think through and validate if this needs to be more generic, and to be honest I still haven't understood exactly what this is trying to solve.
I would also like feedback from @kirksl

@ptrthomas ok, I undestand if this needs time to think through and validate
it is going to be a different extension from original karate-runner from @kirksl, they are two very different code styles that don't mix well
I will proceed with the vscode extension, I hope you will consider this for a future karate version

while we're at it can we proceed with releasing a 2nd version of Peter's Karate project too? 🙂
i think ivan has some great suggestions and additions here, but agree we need to properly vet everything.
@ivangsa happy to work with you and be "very" accommodating with your asks in an effort to fuse our solutions together into the existing Karate Runner extension.  also in agreement that there are quite a number of differences between our implementations, but that shouldn't serve as reason to publish an entirely new extension nor go against working together.
consider the implications.  each of us will probably hate each other over time, double the work, wasted time competing, the extensions will be diluted/weakened as a whole with 2 releases, users will likely be confused and/or unhappy generaly, especially if each version of the extension offers something the other doesn't that they really want.  which one will the choose?
please reconsider as i'm ecstatic to join forces.

hi @kirksl, it's nice to talk you again
first I agree that ideas may need to thought throught, and properly vet everything..
and I think I understant the implications of having two different extensions in terms of

fragmentation vs diversity
double work vs coordination
handling all issues vs shared support
users confusion

I took all this into consideration back in december... when approached you..
I know that saying, that "going along can move faster but going together can get farther"...
But I first expressed my concerns here (remember?):
https://github.com/kirksl/karate-runner/pull/74#issuecomment-750825052

code style was very different and hard to merge and keep compatible overtime
but more important your project has been very irresponsive... we got two PRs waiting for 20 days without any comment or answer (and yes one was very experimental, but the other one as small usefull and self-contained)

After our conversation we almost agree in:

we are going to develop some functionality we needed and in a couple of weeks we will back to you to see to merge them to your project
we were going to re-format code using prettier, which is somehow an standard for js/ts code formatting, to avoid incompatibilities in code

Remember? https://github.com/ivangsa/karate-ide/issues/1#issuecomment-751352725
Well, what happend after two weeks when we got back to you was:

you refactored our contributions to your project to a different style and we have refactored all your project using prettier (as 'agreed' before) => this means code don't merge anymore
but also and more important we asked your for a code review, if we are going to merge this... "I think if we can agree on this refactoring all the rest would be just simple evolution..."
https://github.com/ivangsa/karate-ide/issues/1#issuecomment-757285899

and we didn't really get any code review (and it was later I found out about the code refactoring that made merging hard if not imposible...)
I don't expected this to work...  I already show you our appreciation for your work, without it we wouldn't even start this..
The main reason we did this fork is because we need this functionality for every day work... I'm work for a team of ~10 people dedicated to write api testing as main task, and for apis they are not developers nor users (so they don't really know tha api and need tools to explore)...
We created the extension we need for ourselves, some may like it and some may not, but we do... And I need to publish it to the marketplace because I can not keep sending zip files all the time..
I'm not sure, but I would keep the original karate-runner for compatibility with previous karate version
And if you want to keep developing the extension you can join forces in our project, you will be more than welcome...
I'm not sure about how this would work, but I still mean it... (any way prettier formating will be required)
And I would say this once again, I thank you for all the effort you put into this because is an important part of our daily work. So thanks for that!
Now please take your time, because there is no rush...
What I have in mind for the future is:

explore generating tests and mocks from openapi definitions (some may like it, some may not, but we do have use for them)
explore (as tentative) this "Record and Replay UI tests" https://github.com/intuit/karate/projects/3#card-36516057
but it will be also be great to have this "Language server protocol" https://github.com/intuit/karate/projects/3#card-22529505 (low priority for me but nice to have)

I leave it like this, and sorry for this excedingly long post...

I've just introduced methods to intercept (and even modify if needed) the http request and response as part of the runtime-hook (which has been simplified so that you only need to over-ride the methods you need to)
https://github.com/intuit/karate/commit/38990771f368d8ff833f8b0da6761343046f6535
have not tested this - but hopefully is a generic way for users to introduce custom http logging, capture etc. for e.g. one of the possibilities would be to document all HTTP calls made by a test-suite


Save downloaded torrents to your Downloads dir instead of home dir

I believe it should work cross platform but please give it a try on Windows (if you use it) before merging.
Works fine on Ubuntu

It puts the downloaded torrents in the CURRENT directory, not the home directory, which is a much better solution than forcing them into a folder that might not even exist. if you want the files in your documents folder just run it there.

Tried on windows, doesn't work:
https://www.dropbox.com/s/ef9ilp8iivv5vz1/2023-05-01_18-09-19.mkv?dl=1


Install dependencies failed

I am using Github actions on my project, and I cannot  install dependencies  as it keeps failing,

I have seen a similar issue here and this post on stack overflow but they did not help with my problem.

Here is the full Github actions log:
Because ghinbli_app depends on integration_test any from sdk which doesn't exist (could not find package integration_test in the Flutter SDK), version solving failed.

---- Log transcript ----

FINE: Pub 2.10.4

MSG : Resolving dependencies...

SLVR: fact: ghinbli_app is 1.0.0+1

SLVR: derived: ghinbli_app
SLVR: fact: ghinbli_app depends on flutter any from sdk

SLVR: fact: ghinbli_app depends on http ^0.12.2

SLVR: fact: ghinbli_app depends on lint ^1.3.1
SLVR: fact: ghinbli_app depends on cupertino_icons ^1.0.1
SLVR: fact: ghinbli_app depends on flutter_test any from sdk
SLVR: fact: ghinbli_app depends on integration_test any from sdk
SLVR:   selecting ghinbli_app
SLVR:   derived: integration_test any from sdk
SLVR:   derived: flutter_test any from sdk
SLVR:   derived: cupertino_icons ^1.0.1
SLVR:   derived: lint ^1.3.1
SLVR:   derived: http ^0.12.2
SLVR:   derived: flutter any from sdk
SLVR:   fact: no versions of integration_test from sdk match 0.9.2+2
SLVR:   derived: not integration_test 0.9.2+2 from sdk
SLVR:   fact: integration_test from sdk doesn't exist (could not find package integration_test in the Flutter SDK)
SLVR:   conflict: integration_test from sdk doesn't exist (could not find package integration_test in the Flutter SDK)
SLVR:   ! integration_test any from sdk is satisfied by integration_test any from sdk
SLVR:   ! which is caused by "ghinbli_app depends on integration_test any from sdk"
SLVR:   ! thus: version solving failed
SLVR: Version solving took 0:00:00.062657 seconds.
    | Tried 1 solutions.
FINE: Resolving dependencies finished (0.1s).
ERR : Because ghinbli_app depends on integration_test any from sdk which doesn't exist (could not find package integration_test in the Flutter SDK), version solving failed.
FINE: Exception type: SolveFailure
FINE: package:pub/src/solver/version_solver.dart 312:5   VersionSolver._resolveConflict
    | package:pub/src/solver/version_solver.dart 133:27  VersionSolver._propagate
    | package:pub/src/solver/version_solver.dart 97:11   VersionSolver.solve.<fn>
    | ===== asynchronous gap ===========================
    | dart:async                                         Future.catchError
    | package:pub/src/utils.dart 113:52                  captureErrors.wrappedCallback
    | package:stack_trace                                Chain.capture
    | package:pub/src/utils.dart 126:11                  captureErrors
    | package:pub/src/command_runner.dart 182:13         PubCommandRunner.runCommand
---- End log transcript ----

Any idea on what Could be wrong here?

@Tamir198
can you provide your flutter doctor -v
what's the output when you run flutter pub get -v locally ?

@Tamir198
can you provide your flutter doctor -v
what's the output when you run flutter pub get -v locally ?

When running flutter doctor(locally):
G:\flutter_sdk\flutter\bin\flutter.bat doctor --verbose
[√] Flutter (Channel beta, 1.25.0-8.1.pre, on Microsoft Windows [Version 10.0.18363.1256], locale he-IL)
    • Flutter version 1.25.0-8.1.pre at G:\flutter_sdk\flutter
    • Framework revision 8f89f6505b (3 weeks ago), 2020-12-15 15:07:52 -0800
    • Engine revision 92ae191c17
    • Dart version 2.12.0 (build 2.12.0-133.2.beta)

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\The Vegan\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[√] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] IntelliJ IDEA Community Edition (version 2019.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2019.1.3
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.
Process finished with exit code 0

When running flutter pub get:
Running "flutter pub get" in Ghibli-fun...                         672ms
Process finished with exit code 0

When running flutter doctor(locally):
G:\flutter_sdk\flutter\bin\flutter.bat doctor --verbose
[√] Flutter (Channel beta, 1.25.0-8.1.pre, on Microsoft Windows [Version 10.0.18363.1256], locale he-IL)
    • Flutter version 1.25.0-8.1.pre at G:\flutter_sdk\flutter
    • Framework revision 8f89f6505b (3 weeks ago), 2020-12-15 15:07:52 -0800
    • Engine revision 92ae191c17
    • Dart version 2.12.0 (build 2.12.0-133.2.beta)

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\The Vegan\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[√] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] IntelliJ IDEA Community Edition (version 2019.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2019.1.3
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.
Process finished with exit code 0

When running flutter pub get:
Running "flutter pub get" in Ghibli-fun...                         672ms
Process finished with exit code 0

@Tamir198
G:\flutter_sdk\flutter\bin\flutter.bat doctor --verbose
this suggests me that your installation might be incomplete
please make sure you add flutter to your path
After that please run flutter doctor --android-licenses
and provide your updated flutter doctor -v
and the output of flutter pub get -v (running it from you app folder)

@Tamir198
G:\flutter_sdk\flutter\bin\flutter.bat doctor --verbose
this suggests me that your installation might be incomplete
please make sure you add flutter to your path
After that please run flutter doctor --android-licenses
and provide your updated flutter doctor -v
and the output of flutter pub get -v (running it from you app folder)

Hi @Tamir198
Please see Conflict resolution section to see how to solve this version conflict.
Closing as this is not an issue with flutter itself. If you disagree please comment and I will reopen it.
Thank you

Hi @Tamir198
Please see Conflict resolution section to see how to solve this version conflict.
Closing as this is not an issue with flutter itself. If you disagree please comment and I will reopen it.
Thank you

Hi,
I'm new to Flutter,
How to fix version solving failed. I tried Conflict resolution but I cannot make it work.
Please help
Thank you

@putheng
if you need assistance with your code please follow the link I want help writing my application in the new issue menu


XSS issue on Welcome page

Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if any
[ ] I have reproduced the issue with at least the latest released version of superset
[ ] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
I am using old Caravel 0.10.0
Expected results
I have created one dashboard with this name "test" .
When opening the welcome page, expected output is to be able to view the dashboard name.
Actual results
But instead of only viewing it, the alert() is getting triggered.
Steps to reproduce
Created a dashboard with "test" .
Go back to Welcome page.

Notice: this issue has been closed because it has been inactive for 456 days. Feel free to comment and request for this issue to be reopened.


Suggestion about take_pic.py

Hi, TreB1eN!
When I run take_pic.py to crop face, I find two little problems:

The script isn't sensitive enough to my press (especially when I press q for quitting).
The text in crop area will be saved.

I think the code could be better like:
while cap.isOpened():
    isSuccess, frame = cap.read()

    press_key = cv2.waitKey(1) & 0xFF
    if press_key == ord('t'):
        ...
    elif press_key == ord('q'):
        break

    if isSuccess:
        frame_text = cv2.putText(...)
        ...

cap.release()

Hmm... please push a PR, I/m quite busy recently