The script stopped working

Hello. I ran the script as mentioned in readme, and the following is the output of the shell
cannot open 'tank': dataset does not exist
+ DEVICES=($(lsblk --fs --json | jq -r '.blockdevices[] | select(.children == null and .fstype == null) | .name'))
++ lsblk --fs --json
++ jq -r '.blockdevices[] | select(.children == null and .fstype == null) | .name'
+ DEVICES_FULLNAME=()
+ zpool create -o ashift=12 tank
missing vdev specification
usage:
        create [-fnd] [-o property=value] ...
            [-O file-system-property=value] ...
            [-m mountpoint] [-R root] <pool> <vdev> ...
ubuntu@ip-172-31-7-63:~/bsc-archive-snapshot$ sudo ./build_archive_node.sh
+ [[ 0 -ne 0 ]]
+ cat
+ install_prereq
+ set -euxo pipefail
+ apt update
Hit:1 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
25 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ DEBIAN_FRONTEND=noninteractive
+ apt install -y zfsutils-linux unzip pv clang-12 make jq python3-boto3 super
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
jq is already the newest version (1.6-2.1ubuntu3).
make is already the newest version (4.3-4.1build1).
pv is already the newest version (1.6.6-1build2).
clang-12 is already the newest version (1:12.0.1-19ubuntu3).
python3-boto3 is already the newest version (1.20.34+dfsg-1).
super is already the newest version (3.30.3-2).
unzip is already the newest version (6.0-26ubuntu3.1).
zfsutils-linux is already the newest version (2.1.4-0ubuntu0.1).
0 upgraded, 0 newly installed, 0 to remove and 25 not upgraded.
++ which clang-12
+ ln -s /usr/bin/clang-12 /usr/bin/cc
ln: failed to create symbolic link '/usr/bin/cc': File exists
+ true
+ snap install --classic go
snap "go" is already installed, see 'snap help refresh'
+ cargo --version
./build_archive_node.sh: line 101: cargo: command not found
+ curl --proto =https --tlsv1.2 -sSf https://sh.rustup.rs
+ bash /dev/stdin -y
info: downloading installer
info: profile set to 'default'
info: default host triple is x86_64-unknown-linux-gnu
warning: Updating existing toolchain, profile choice will be ignored
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: default toolchain set to 'stable-x86_64-unknown-linux-gnu'

  stable-x86_64-unknown-linux-gnu unchanged - rustc 1.66.0 (69f9c33d7 2022-12-12)

Rust is installed now. Great!

To get started you may need to restart your current shell.
This would reload your PATH environment variable to include
Cargo's bin directory ($HOME/.cargo/bin).

To configure your current shell, run:
source "$HOME/.cargo/env"
+ source /root/.cargo/env
++ case ":${PATH}:" in
++ export PATH=/root/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
++ PATH=/root/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
+ install_zstd
+ set -euxo pipefail
+ pzstd --help
+ install_aws_cli
+ set -euxo pipefail
+ aws --version
+ install_s3pcp
+ set -euxo pipefail
+ s3pcp --help
+ install_putils
+ safe_wait
+ set -euxo pipefail
+ BACKGROUND_PIDS=($(jobs -p))
+ psplit --help
+ install_erigon
+ set -euxo pipefail
+ erigon --help
++ jobs -p
+ for PID in "${BACKGROUND_PIDS[@]}"
+ wait -f 16635
Usage:
  pzstd [args] [FILE(s)]
Parallel ZSTD options:
  -p, --processes   #    : number of threads to use for (de)compression (default:<numcpus>)
ZSTD options:
  -#                     : # compression level (1-19, default:<numcpus>)
  -d, --decompress       : decompression
  -o                file : result stored into `file` (only if 1 input file)
  -f, --force            : overwrite output without prompting, (de)compress links
      --rm               : remove source file(s) after successful (de)compression
  -k, --keep             : preserve source file(s) (default)
  -h, --help             : display help and exit
  -V, --version          : display version number and exit
  -v, --verbose          : verbose mode; specify multiple times to increase log level (default:2)
  -q, --quiet            : suppress warnings; specify twice to suppress errors too
  -c, --stdout           : force write to standard output, even if it is the console
  -r                     : operate recursively on directories
      --ultra            : enable levels beyond 19, up to 22 (requires more memory)
psplit 0.1.0
Takes a file or stdin and splits it by -b bytes and sends them to the
OUTPUT_COMMAND in parallel limited by -p concurrent jobs.

Example:

$ printf '012345678901234567890123' | psplit -b 10 sh -c 'cat > /tmp/psplit_$SEQ; echo >>
/tmp/psplit_$SEQ'

Will result in 3 files:
/tmp/psplit_0 = "0123456789
"
/tmp/psplit_1 = "0123456789
"
/tmp/psplit_2 = "0123
"

USAGE:
    psplit [OPTIONS] <OUTPUT_COMMAND>

ARGS:
    <OUTPUT_COMMAND>    Command to run on each output. An environmental variable "SEQ" will be
                        set containing the sequence number of the slice. Data will be sent to
                        stdin of command

OPTIONS:
    -b, --bytes <BYTES>
            Number of bytes per output file [default:<PHONE_NUMBER>]

    -h, --help
            Print help information

    -i, --input-file <INPUT_FILE>
            Input file to split. If not set, uses stdin

    -p, --parallel-count <PARALLEL_COUNT>
            Number of commands allowed to run in parallel [default: 16]

    -V, --version
            Print version information
  -C, --check            : integrity check (default)
      --no-check         : no integrity check
  -t, --test             : test compressed file integrity
  --                     : all arguments after "--" are treated as files
+ pjoin --help
+ return
+ for PID in "${BACKGROUND_PIDS[@]}"
+ wait -f 16636
pjoin 0.1.0
Takes stdin commands split by new lines and executes them in parallel and
prints stdout in order based on the order they are in stdin.

Example:

$ pjoin <<'EOT'
sh -c 'printf foo; sleep 1'
printf bar
EOT

Will result in:
'foobar' (without quotes)

USAGE:
    pjoin [OPTIONS] [OUTPUT_FILE]

ARGS:
    <OUTPUT_FILE>    Path to write file. Prints to stdout if not set. Using a file can be faster
                     than stdout

OPTIONS:
    -b, --buffer-size <BUFFER_SIZE>
            Size in bytes of the stdout buffer for reach command [default:<PHONE_NUMBER>]

    -h, --help
            Print help information

    -p, --parallel-count <PARALLEL_COUNT>
            Number of commands to run in parallel [default: 16]

    -V, --version
            Print version information
Downloads data from s3 and sends it to stdout very fast and on a pinned version.
Many concurrent connections to s3 are opened and different chunks of the file
are downloaded in parallel and stiched together using the `pjoin` utility.

USAGE:
    s3pcp [OPTIONS] [S3_PATH]

ARGS:
    S3_PATH    A path to an s3 object. Format: 's3://{bucket}/{key}'

OPTIONS:
    --requester-pays
        If the account downloading is requesting to be the payer for
        the request.

    --region <REGION>
        The region the request should be sent to.

    -p, --parallel-count <PARALLEL_COUNT>
        Number of commands to run in parallel [default: based on computer resources]

    -h, --help
        Print help information
+ return
+ return
NAME:
   erigon - erigon experimental cli

USAGE:
   erigon [global options] command [command options] [arguments...]

VERSION:
   2.31.0-stable-a53e8a3e

COMMANDS:
   snapshots
   help, h    Shows a list of commands or help for one command
   BLOCKCHAIN COMMANDS:
     init    Bootstrap and initialize a new genesis block
     import  Import a blockchain file

GLOBAL OPTIONS:
   --datadir value                                Data directory for the databases (default: /root/.local/share/erigon)
   --ethash.dagdir value                          Directory to store the ethash mining DAGs (default: /root/.local/share/erigon-ethash)
   --snapshots                                    Default: use snapshots "true" for BSC, Mainnet and Goerli. use snapshots "false" in all other cases (default: true)
   --externalcl                                   enables external consensus (default: false)
   --txpool.disable                               experimental external pool and block producer, see ./cmd/txpool/readme.md for more info. Disabling internal txpool and block producer. (default: false)
   --txpool.locals value                          Comma separated accounts to treat as locals (no flush, priority inclusion)
   --txpool.nolocals                              Disables price exemptions for locally submitted transactions (default: false)
   --txpool.pricelimit value                      Minimum gas price (fee cap) limit to enforce for acceptance into the pool (default: 1)
   --txpool.pricebump value                       Price bump percentage to replace an already existing transaction (default: 10)
   --txpool.accountslots value                    Minimum number of executable transaction slots guaranteed per account (default: 16)
   --txpool.globalslots value                     Maximum number of executable transaction slots for all accounts (default: 10000)
   --txpool.globalbasefeeslots value              Maximum number of non-executable transactions where only not enough baseFee (default: 30000)
   --txpool.accountqueue value                    Maximum number of non-executable transaction slots permitted per account (default: 64)
   --txpool.globalqueue value                     Maximum number of non-executable transaction slots for all accounts (default: 30000)
   --txpool.lifetime value                        Maximum amount of time non-executable transaction are queued (default: 3h0m0s)
   --txpool.trace.senders value                   Comma separared list of addresses, whoes transactions will traced in transaction pool with debug printing
   --prune value                                  Choose which ancient data delete from DB:
                                                  h - prune history (ChangeSets, HistoryIndices - used by historical state access, like eth_getStorageAt, eth_getBalanceAt, debug_traceTransaction, trace_block, trace_transaction, etc.)
                                                  r - prune receipts (Receipts, Logs, LogTopicIndex, LogAddressIndex - used by eth_getLogs and similar RPC methods)
                                                  t - prune transaction by it's hash index
                                                  c - prune call traces (used by trace_filter method)
                                                  Does delete data older than 90K blocks, --prune=h is shortcut for: --prune.h.older=90000.
                                                  Similarly, --prune=t is shortcut for: --prune.t.older=90000 and --prune=c is shortcut for: --prune.c.older=90000.
                                                  However, --prune=r means to prune receipts before the Beacon Chain genesis (Consensus Layer might need receipts after that).
                                                  If an item is NOT on the list - means NO pruning for this data.
                                                  Example: --prune=htc (default: "disabled")
   --prune.h.older value                          Prune data older than this number of blocks from the tip of the chain (if --prune flag has 'h', then default is 90K) (default: 0)
   --prune.r.older value                          Prune data older than this number of blocks from the tip of the chain (default: 0)
   --prune.t.older value                          Prune data older than this number of blocks from the tip of the chain (if --prune flag has 't', then default is 90K) (default: 0)
   --prune.c.older value                          Prune data older than this number of blocks from the tip of the chain (if --prune flag has 'c', then default is 90K) (default: 0)
   --prune.h.before value                         Prune data before this block (default: 0)
   --prune.r.before value                         Prune data before this block (default: 0)
   --prune.t.before value                         Prune data before this block (default: 0)
   --prune.c.before value                         Prune data before this block (default: 0)
   --batchSize value                              Batch size for the execution stage (default: "256M")
   --blockDownloaderWindow value                  Outstanding limit of block bodies being downloaded (default: 32768)
   --database.verbosity value                     Enabling internal db logs. Very high verbosity levels may require recompile db. Default: 2, means warning. (default: 2)
   --private.api.addr value                       private api network address, for example: <IP_ADDRESS>:9090, empty string means not to start the listener. do not expose to public network. serves remote database interface (default: "<IP_ADDRESS>:9090")
   --private.api.ratelimit value                  Amount of requests server handle simultaneously - requests over this limit will wait. Increase it - if clients see 'request timeout' while server load is low - it means your 'hot data' is small or have much RAM.  (default: 31872)
   --etl.bufferSize value                         Buffer size for ETL operations. (default: "256MB")
   --tls                                          Enable TLS handshake (default: false)
   --tls.cert value                               Specify certificate
   --tls.key value                                Specify key file
   --tls.cacert value                             Specify certificate authority
   --state.stream.disable                         Disable streaming of state changes from core to RPC daemon (default: false)
   --sync.loop.throttle value                     Sets the minimum time between sync loop starts (e.g. 1h30m, default is none)
   --bad.block value                              Marks block with given hex string as bad and forces initial reorg before normal staged sync
   --http                                         HTTP-RPC server (enabled by default). Use --http=false to disable it (default: true)
   --http.addr value                              HTTP-RPC server listening interface (default: "localhost")
   --http.port value                              HTTP-RPC server listening port (default: 8545)
   --authrpc.addr value                           HTTP-RPC server listening interface for the Engine API (default: "localhost")
   --authrpc.port value                           HTTP-RPC server listening port for the Engine API (default: 8551)
   --authrpc.jwtsecret value                      Path to the token that ensures safe connection between CL and EL
   --http.compression                             Enable compression over HTTP-RPC (default: false)
   --http.corsdomain value                        Comma separated list of domains from which to accept cross origin requests (browser enforced)
   --http.vhosts value                            Comma separated list of virtual hostnames from which to accept requests (server enforced). Accepts '*' wildcard. (default: "localhost")
   --authrpc.vhosts value                         Comma separated list of virtual hostnames from which to accept Engine API requests (server enforced). Accepts '*' wildcard. (default: "localhost")
   --http.api value                               API's offered over the HTTP-RPC interface (default: "eth,erigon,engine")
   --ws                                           Enable the WS-RPC server (default: false)
   --ws.compression                               Enable compression over WebSocket (default: false)
   --http.trace                                   Trace HTTP requests with INFO level (default: false)
   --state.cache value                            Amount of data to store in StateCache (enabled if no --datadir set). Set 0 to disable StateCache. Defaults to 0MB (default: "0MB")
   --rpc.batch.concurrency value                  Does limit amount of goroutines to process 1 batch request. Means 1 bach request can't overload server. 1 batch still can have unlimited amount of request (default: 2)
   --rpc.streaming.disable                        Erigon has enalbed json streaming for some heavy endpoints (like trace_*). It's treadoff: greatly reduce amount of RAM (in some cases from 30GB to 30mb), but it produce invalid json format if error happened in the middle of streaming (because json is not streaming-friendly format) (default: false)
   --db.read.concurrency value                    Does limit amount of parallel db reads. Default: equal to GOMAXPROCS (or number of CPU) (default: 64)
   --rpc.accessList value                         Specify granular (method-by-method) API allowlist
   --trace.compat                                 Bug for bug compatibility with OE for trace_ routines (default: false)
   --rpc.gascap value                             Sets a cap on gas that can be used in eth_call/estimateGas (default: 50000000)
   --txpool.api.addr value                        txpool api network address, for example: <IP_ADDRESS>:9090 (default: use value of --private.api.addr)
   --trace.maxtraces value                        Sets a limit on traces that can be returned in trace_filter (default: 200)
   --http.timeouts.read value                     Maximum duration for reading the entire request, including the body. (default: 30s)
   --http.timeouts.write value                    Maximum duration before timing out writes of the response. It is reset whenever a new request's header is read. (default: 30m0s)
   --http.timeouts.idle value                     Maximum amount of time to wait for the next request when keep-alives are enabled. If http.timeouts.idle is zero, the value of http.timeouts.read is used. (default: 2m0s)
   --authrpc.timeouts.read value                  Maximum duration for reading the entire request, including the body. (default: 30s)
   --authrpc.timeouts.write value                 Maximum duration before timing out writes of the response. It is reset whenever a new request's header is read. (default: 30m0s)
   --authrpc.timeouts.idle value                  Maximum amount of time to wait for the next request when keep-alives are enabled. If authrpc.timeouts.idle is zero, the value of authrpc.timeouts.read is used. (default: 2m0s)
   --rpc.evmtimeout value                         Maximum amount of time to wait for the answer from EVM call. (default: 5m0s)
   --snap.keepblocks                              Keep ancient blocks in db (useful for debug) (default: false)
   --snap.stop                                    Workaround to stop producing new snapshots, if you meet some snapshots-related critical bug (default: false)
   --db.pagesize value                            set mdbx pagesize on db creation: must be power of 2 and '256b <= pagesize <= 64kb'. default: equal to OperationSystem's pageSize (default: "4KB")
   --torrent.port value                           port to listen and serve BitTorrent protocol (default: 42069)
   --torrent.maxpeers value                       unused parameter (reserved for future use) (default: 100)
   --torrent.conns.perfile value                  connections per file (default: 10)
   --torrent.download.slots value                 amount of files to download in parallel. If network has enough seeders 1-3 slot enough, if network has lack of seeders increase to 5-7 (too big value will slow down everything). (default: 3)
   --torrent.upload.rate value                    bytes per second, example: 32mb (default: "4mb")
   --torrent.download.rate value                  bytes per second, example: 32mb (default: "16mb")
   --torrent.verbosity value                      0=silent, 1=error, 2=warn, 3=info, 4=debug, 5=detail (must set --verbosity to equal or higher level and has defeault: 3) (default: 2)
   --port value                                   Network listening port (default: 30303)
   --p2p.protocol value [ --p2p.protocol value ]  Version of eth p2p protocol (default: 66, 67)
   --nat value                                    NAT port mapping mechanism (any|none|upnp|pmp|stun|extip:<IP>)
                                                       "" or "none"         default - do not nat
                                                       "extip:<IP_ADDRESS>"   will assume the local machine is reachable on the given IP
                                                       "any"                uses the first auto-detected mechanism
                                                       "upnp"               uses the Universal Plug and Play protocol
                                                       "pmp"                uses NAT-PMP with an auto-detected gateway address
                                                       "pmp:<IP_ADDRESS>"    uses NAT-PMP with the given gateway address
                                                       "stun"               uses STUN to detect an external IP using a default server
                                                       "stun:<server>"      uses STUN to detect an external IP using the given server (host:port)
   --nodiscover                                   Disables the peer discovery mechanism (manual peer addition) (default: false)
   --v5disc                                       Enables the experimental RLPx V5 (Topic Discovery) mechanism (default: false)
   --netrestrict value                            Restricts network communication to the given IP networks (CIDR masks)
   --nodekey value                                P2P node key file
   --nodekeyhex value                             P2P node key as hex (for testing)
   --discovery.dns value                          Sets DNS discovery entry points (use "" to disable DNS)
   --bootnodes value                              Comma separated enode URLs for P2P discovery bootstrap
   --staticpeers value                            Comma separated enode URLs to connect to
   --trustedpeers value                           Comma separated enode URLs which are always allowed to connect, even above the peer limit
   --maxpeers value                               Maximum number of network peers (network disabled if set to 0) (default: 100)
   --chain value                                  Name of the testnet to join (default: "mainnet")
   --dev.period value                             Block period to use in developer mode (0 = mine only if transaction pending) (default: 0)
   --vmdebug                                      Record information useful for VM and contract debugging (default: false)
   --networkid value                              Explicitly set network id (integer)(For testnets: use --chain <testnet_name> instead) (default: 1)
   --fakepow                                      Disables proof-of-work verification (default: false)
   --gpo.blocks value                             Number of recent blocks to check for gas prices (default: 20)
   --gpo.percentile value                         Suggested gas price is the given percentile of a set of recent transaction gas prices (default: 60)
   --allow-insecure-unlock                        Allow insecure account unlocking when account-related RPCs are exposed by http (default: false)
   --metrics                                      Enable metrics collection and reporting (default: false)
   --metrics.addr value                           Enable stand-alone metrics HTTP server listening interface (default: "<IP_ADDRESS>")
   --metrics.port value                           Metrics HTTP server listening port (default: 6060)
   --experimental.history.v3                      (also known as Erigon3) Not recommended yet: Can't change this flag after node creation. New DB and Snapshots format of history allows: parallel blocks execution, get state as of given transaction without executing whole block. (default: false)
   --identity value                               Custom node name
   --clique.checkpoint value                      number of blocks after which to save the vote snapshot to the database (default: 10)
   --clique.snapshots value                       number of recent vote snapshots to keep in memory (default: 1024)
   --clique.signatures value                      number of recent block signatures to keep in memory (default: 16384)
   --clique.datadir value                         a path to clique db folder
   --watch-the-burn                               Enable WatchTheBurn stage to keep track of ETH issuance (default: false)
   --mine                                         Enable mining (default: false)
   --proposer.disable                             Disables PoS proposer (default: false)
   --miner.notify value                           Comma separated HTTP URL list to notify of new work packages
   --miner.gaslimit value                         Target gas limit for mined blocks (default: 30000000)
   --miner.etherbase value                        Public address for block mining rewards (default: "0")
   --miner.extradata value                        Block extra data set by the miner (default = client version)
   --miner.noverify                               Disable remote sealing verification (default: false)
   --miner.sigfile value                          Private key to sign blocks with
   --sentry.api.addr value                        comma separated sentry addresses '<host>:<port>,<host>:<port>'
   --sentry.log-peer-info                         Log detailed peer info when a peer connects or disconnects. Enable to integrate with observer. (default: false)
   --downloader.api.addr value                    downloader address '<host>:<port>'
   --no-downloader                                to disable downloader component (default: false)
   --downloader.verify                            verify snapshots on startup. it will not report founded problems but just re-download broken pieces (default: false)
   --healthcheck                                  Enable grpc health check (default: false)
   --bor.heimdall value                           URL of Heimdall service (default: "http://localhost:1317")
   --bor.withoutheimdall                          Run without Heimdall service (for testing purpose) (default: false)
   --ethstats value                               Reporting URL of a ethstats service (nodename:secret@host:port)
   --override.terminaltotaldifficulty value       Manually specify TerminalTotalDifficulty, overriding the bundled setting (default: 0)
   --override.mergeNetsplitBlock value            Manually specify FORK_NEXT_VALUE (see EIP-3675), overriding the bundled setting (default: 0)
   --config value                                 Sets erigon flags from YAML/TOML file
   --log.console.verbosity value                  Set the log level for console logs (default: "info")
   --log.dir.verbosity value                      Set the log verbosity for logs stored to disk (default: "dbug")
   --log.dir.path value                           Path to store user and error logs to disk
   --log.console.json                             Format console logs with JSON (default: false)
   --log.json                                     Format console logs with JSON (default: false)
   --log.dir.json                                 Format file logs with JSON (default: false)
   --lightclient.discovery.addr value             Address for lightclient DISCV5 protocol (default: "<IP_ADDRESS>")
   --lightclient.discovery.port value             Port for lightclient DISCV5 protocol (default: 4000)
   --lightclient.discovery.tcpport value          TCP Port for lightclient DISCV5 protocol (default: 4001)
   --sentinel.addr value                          Address for sentinel (default: "localhost")
   --sentinel.port value                          Port for sentinel (default: 7777)
   --pprof                                        Enable the pprof HTTP server (default: false)
   --pprof.addr value                             pprof HTTP server listening interface (default: "<IP_ADDRESS>")
   --pprof.port value                             pprof HTTP server listening port (default: 6060)
   --pprof.cpuprofile value                       Write CPU profile to the given file
   --trace value                                  Write execution trace to the given file
   --help, -h                                     show help (default: false)
   --version, -v                                  print the version (default: false)
+ return
aws-cli/2.9.8 Python/3.9.11 Linux/5.15.0-1026-aws exe/x86_64.ubuntu.22 prompt/off
+ return
+ for PID in "${BACKGROUND_PIDS[@]}"
+ wait -f 16637
+ for PID in "${BACKGROUND_PIDS[@]}"
+ wait -f 16639
+ for PID in "${BACKGROUND_PIDS[@]}"
+ wait -f 16641
+ [[ '' == \1 ]]
+ setup_drives
+ set -euxo pipefail
+ zfs list tank
cannot open 'tank': dataset does not exist
+ DEVICES=($(lsblk --fs --json | jq -r '.blockdevices[] | select(.children == null and .fstype == null) | .name'))
++ lsblk --fs --json
++ jq -r '.blockdevices[] | select(.children == null and .fstype == null) | .name'
+ DEVICES_FULLNAME=()
+ zpool create -o ashift=12 tank
missing vdev specification
usage:
        create [-fnd] [-o property=value] ...
            [-O file-system-property=value] ...
            [-m mountpoint] [-R root] <pool> <vdev> ...
            ```

It looks like it failed because there are no unused block devices. It will only work if there are block devices that have no partitions.

Ohh I see. So I need to create a new partition and mount it as a DIR?

You probably added credentials to non sudo user.


fix: Small padding in country/language selection in settings

What

fix: Small padding in country/language selection in settings #2683

Screenshot

Fixes bug(s)

Part of

#2683

Codecov Report

Merging #2685 (4dd1b57) into develop (2ea0da3) will decrease coverage by 1.60%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           develop   #2685      +/-   ##
==========================================
- Coverage     8.86%   7.25%   -1.61%
==========================================
  Files          161     219      +58
  Lines         6623   10530    +3907
==========================================
+ Hits           587     764     +177
- Misses        6036    9766    +3730

Impacted Files
Coverage Δ

...kages/smooth_app/lib/widgets/attribute_button.dart
0.00% <0.00%> (-92.00%)
:arrow_down:

...s/smooth_app/lib/data_models/user_preferences.dart
8.73% <0.00%> (-23.57%)
:arrow_down:

packages/smooth_app/lib/themes/smooth_theme.dart
60.00% <0.00%> (-22.98%)
:arrow_down:

...p/lib/generic_lib/dialogs/smooth_alert_dialog.dart
15.11% <0.00%> (-19.10%)
:arrow_down:

...mooth_app/lib/data_models/product_preferences.dart
21.68% <0.00%> (-9.75%)
:arrow_down:

packages/smooth_app/lib/main.dart
14.65% <0.00%> (-3.24%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/welcome_page.dart
0.00% <0.00%> (-3.13%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/scan_example.dart
0.00% <0.00%> (-2.28%)
:arrow_down:

...p/lib/pages/onboarding/consent_analytics_page.dart
0.00% <0.00%> (-1.57%)
:arrow_down:

...ackages/smooth_app/lib/pages/scan/scan_header.dart
3.33% <0.00%> (-1.43%)
:arrow_down:

... and 236 more

Help us with your feedback. Take ten seconds to tell us how you rate us.

The point was to make the paddings even throughout the list, still the screenshot seems like there's inconsistencies. Perhaps you could have a look.

Like up and down padding

Yeah,exactly bottom and top padding


Doc header: change Documentation to Docs to conform with PR to crates.io

crates.io pull request: https://github.com/rust-lang/crates.io/pull/276

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @steveklabnik (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+<PHONE_NUMBER>18215f950816c5dd96b260c791ccad

:hourglass: Testing commit 7618750 with merge bb0f4ae...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


Pipeline publishCatalog step using SSH to push with Git does not work

Steps to reproduce :

Edit pipeline configuration, add a step

Step type selection "publish catalog app"

Edit step, select the protocol "Push to Git with SSH"

Select DEPLOY_KEY  (I can be sure it is correct)

Run the pipeline

Result:
Output error log:

The deploy key is in an invalid format so it is an expected failure.
But we should improve error handling so that it exists and terminates earlier without printing last few lines.


Put Comments to Structures (to remove redundancy)

Hey Folks,
i've put the comments to the structures and dumping it via these component, to remove the code redundancy
Feel free to merge: 5885ded
Why in  there is a try for opening a existing comments file? Is these for continuing a (broken) session?
Cheers

Issues are not for discussing code changes. If you want to contribute, please create a pull request.


Multiple deploys with vmware_workstation provider

Hi
Firstly, thanks for the plugin!
I recently switched to the vmware_workstation provider for vagrant and I am having an issue with the plugin. The r10k deploys multiple times for up and destroy commands. It also runs for the ssh command. I haven't yet tested resume or suspend.
There is some output below and I posted a gist with the debug flag set during an up command.
This is probably a niche issue but if you can spot anything useful from the output please let me know.
$ vagrant up master
Bringing machine 'master' up with 'vmware_workstation' provider...
==> master: vagrant-r10k: Beginning r10k deploy of puppet modules into ~/code/puppet-dev/modules using ~/code/puppet-dev/puppet/Puppetfile
==> master: vagrant-r10k: Deploy finished
==> master: Verifying vmnet devices are healthy...
==> master: vagrant-r10k: Beginning r10k deploy of puppet modules into ~/code/puppet-dev/modules using ~/code/puppet-dev/puppet/Puppetfile
==> master: vagrant-r10k: Deploy finished
==> master: vagrant-r10k: Beginning r10k deploy of puppet modules into ~/code/puppet-dev/modules using ~/code/puppet-dev/puppet/Puppetfile
==> master: vagrant-r10k: Deploy finished
==> master: Preparing network adapters...
==> master: Starting the VMware VM...
==> master: Waiting for machine to boot. This may take a few minutes...

$ vagrant destroy master
==> master: vagrant-r10k: Beginning r10k deploy of puppet modules into ~/code/puppet-dev/modules using ~/code/puppet-dev/puppet/Puppetfile
==> master: vagrant-r10k: Deploy finished
    master: Are you sure you want to destroy the 'master' VM? [y/N] y
==> master: vagrant-r10k: Beginning r10k deploy of puppet modules into ~/code/puppet-dev/modules using ~/code/puppet-dev/puppet/Puppetfile
==> master: vagrant-r10k: Deploy finished
==> master: Stopping the VMware VM...
==> master: Deleting the VM...
==> master: Running cleanup tasks for 'shell' provisioner...
==> master: Running cleanup tasks for 'puppet' provisioner...
==> master: Running triggers after destroy...
==> master: Updating /etc/hosts file on active guest machines...
==> master: Updating /etc/hosts file on host machine (password may be required)...

$ vagrant ssh master
==> master: vagrant-r10k: Beginning r10k deploy of puppet modules into /home/scott/code/puppet-dev/modules using /home/scott/code/puppet-dev/puppet/Puppetfile
==> master: vagrant-r10k: Deploy finished
[vagrant@master ~]$

@wyrie Hmmm...I think I have a vague idea of what's going on here.
I believe this is really two issues.

The plugin runs at both provision and config validation times (see the hooks), so the duplicate run on up is known. Though it's only supposed to run twice, not three times, so there definitely is something wrong here. I'm embarrassed to say that I don't remember the reason for running twice, but I believe it was the only method I could find to have the plugin both fail properly during config validation, and run before puppet in the provisioning phase. I could dig deeper into this, but I'd probably handle this more as a feature request than a bug. If you'd like, I'll open a separate issue for this part.
The plugin running at ssh time is new to me; I've never seen this before, and I can't seem to reproduce it. Though I also haven't used the VMWare provider. Do you think that you could please post a debug log of that (either with VAGRANT_LOG=debug or just by running vagrant ssh --debug)? My guess is that the vmware_workstation provider is running an action hook that VirtualBox doesn't, during the ssh phase. The action hooks part of Vagrant is pretty much undocumented, so a lot of this was based on examination of debug output...

Just for clarity, could you please confirm the version of Vagrant that you're running, along with your OS and ruby version (and if you're running ruby via rvm or rbenv, etc.)?

@jantman Thanks for checking it out.

I commented plugin.rb line 22, which probably breaks the check for plugin settings in the vagrant file, but it is running like it should i.e. once on up, resume and not on ssh, destroy etc.

So I have a workaround for now. If you want to move this to a feature request and need help testing in the future I'm happy with any of it.

Here is a gist for the ssh command.

Ubuntu 14.04 64bit
Vagrant version: 1.7.2
Ruby version: 2.0.0 (via apt)

Ok, thanks so much. It might take me a few days to get to it, but I'm going to try and dig through the code and see if there's a cleaner/safer way of hooking in for the config validation and then actual r10k run separately.
After doing a little more research, it appears that each of the providers handle hooks slightly differently. This isn't really well documented, so I based my code on how the virtualbox one works. I'll go through that debug ssh output and see if I can find something more concrete.

@wyrie I assume that you posted that gist after commenting out the hook.before Vagrant::Action::Builtin::ConfigValidate on line 22 in plugin.rb, as it only shows one deploy?
Assuming so, I'm going to close this in favor of #9.
If your offer of testing still holds, yeah, I might need some assistance with that, as it seems like I can't test with the vmware-workstation provider without actually buying both it and VMWare Workstation.

Yes that's right. Tested it again and there is definitely multiple deploys on the ssh command.
Just let me know when you have a commit you want to test and I'll send you the debug output.

I am seeing the multiple r10k deploy issue in my vagrant/Virtual_box env as well.

TL;DR: Yeah, you're right. It should be quick, I'll try my best to work on it this weekend, but my attention has been pulled to other things lately.
Yes, I can confirm this is still happening. I guess I should be really embarrassed by the amount of time it's taken me to address this, but I've gotten sidetracked on other things, and also had serious problems trying to get working acceptance tests for this project (apparently that's still a... very new... area for Vagrant plugins).
I believe the fix for this should be relatively simple, and I'll do my best to get back up to speed on this and try something this weekend, but I'll need some help testing it.
Hashicorp was nice enough to grant me a limited license to the VMWare Workstation provider (to be used exclusively for testing this plugin), and I already have Workstation, but it appears that the automated acceptance tests for this are going to have to be completely rewritten for each provider, AND I've been having trouble getting the VMWare provider working inside a bundle/rspec install...

Like #8, this should be fixed by #9 / #23 which are now merged to master but not yet released. I'll ping back once I have a release cut; I'm having issues with VMWare and the Vagrant plugin (can't get automated tests to work for them), but I'll try to do a manual confirmation.


Parallelize decorator

Description
Implements #934
Draft for now, may need to test more + add docs
Added a parallelized argument to resource. For me that seems like a good interface.
Under the hood it's basically the same decorator from the test implementation (maybe it makes sense to use it directly in some cases?) or we could integrate this more deeply in resource.
There was a lot of overhead coming from all the polling in PipeIterator when constantly yielding None, so I tried to implement more intelligent waiting for futures. Basically just block until some future completes when the pool is full instead of blindly polling and looping over the resources and that seems to make a big difference.
+ pretty big refactor of PipeIterator -> the futures worker pool is a separate class
Benchmark before and after optimizing: https://gist.github.com/steinitzu/671b47cdb7cbf61b2fab46cf1faefd86
The original iterator had a lot of overhead, especially when number of resources is <= number of workers.

one more comment to refactor: please split Pipe from PipeIterator. Also I think you can move items.py to typing.py but that's up to you

I did not review the PR, but want to point out that returning None from a resource to skip to the next in round robin mode should still work for backwards compatibility at least alex is using this.

I did not review the PR, but want to point out that returning None from a resource to skip to the next in round robin mode should still work for backwards compatibility at least alex is using this.

💯  we have a  test that makes sure that round robin really works test_rotation_on_none and all other tests must pass

@steinitzu one more ask - when this is implemented could you check if our sql_database can be executed in parallel? looks like engine is thread safe and we open connection when already (possibly) in a thread

@steinitzu one more ask - when this is implemented could you check if our sql_database can be executed in parallel? looks like engine is thread safe and we open connection when already (possibly) in a thread

Good call, wonder if that will work with streaming results. The conn pool is thread safe, but we're streaming chunks on one connection to load a table.

@rudolfix  Few more adjustements and tests.
The duplicate "submit futures" block in _get_source_item is gone. I was getting huge overhead (2x runtime in some cases) without it originally, but now after all the changes I see no real difference so there's no need for it.

Updated the docs. Couple of concerns:

I left one instance of @defer in the pokemon example since it's a different use case. We're not planning on removing it, right?
The "parallel pipelines asyncio" example I'm not sure if it works. For me it hangs sometimes and the generators don't look like they're even executing (print debugging) though the test passes https://github.com/dlt-hub/dlt/blob/sthor%2Fdestination-docs/docs/website/docs/reference/performance_snippets/performance-snippets.py#L123 . It's the same on the devel branch, was this working at some point?

Updated the docs. Couple of concerns:

I left one instance of @defer in the pokemon example since it's a different use case. We're not planning on removing it, right?

No, it still works well when you want parallelize a loop.

The "parallel pipelines asyncio" example I'm not sure if it works. For me it hangs sometimes and the generators don't look like they're even executing (print debugging) though the test passes https://github.com/dlt-hub/dlt/blob/sthor%2Fdestination-docs/docs/website/docs/reference/performance_snippets/performance-snippets.py#L123 . It's the same on the devel branch, was this working at some point?

It runs. But console output gets disabled when two pipelines are gathered at the same time. Something evil must happen there... It does not matter if we run the pools in extract step or if we run extract step at all. if I serialize all the calls by locking in _run_pipeline then the problem is gone. any ideas what could be happening?
also it indeed locks from time to time. probably connected to the above


docs: update okta provider doc

Hey, I just made a Pull Request!
Update Okta auth provider documentation to clarify the provided example is for local development only.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks for the contribution @phclark! 🚀
@Rugvip @camilaibs can you give this a quick look, just a small Docs update

Thanks again @phclark and @benjdlambert for the merge 🚀


Allow configuration of Gitea's storageclass

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When I'm running zarf init I can use --storage-class to set the registry's storageclass but I'm not able to set Gitea's storageclass
Describe the solution you'd like

Given a state
When an action is taken
Then something happens

Given I have a k8s cluster ready for zarf init
When I run zarf init --storage-class foo --components git-server
Then Gitea uses the "foo" storageclass for its PVC
Describe alternatives you've considered
(optional) A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Nevermind, using --storage-class foo does do it for EFS too. This issue can be converted to just a docs issue, since zarf init --help only mentions that --storage-class affects the registry.


Add 404 / failed install statistics

Hi!
It might be interesting to be able to query through failed installation data, if such a thing is possible.
I.e. -- to view pip install foo by volume, for foo a non-existing package, or existing package with no uploaded files.

This would probably also provide some interesting data on potential typosquats.

I think it would be possible to do this, using the simple API stats and download stats, to determine names that were hit on the simple index but not downloaded?
That’s assuming PyPI is sending in a note to linehaul even when it sends a 404. Not sure if that’s the case though.


Switch to new repository golib/auth/userinfo.

While this would work, the interface you need for ldap groups in general needs also a group filter see: https://github.com/Cloud-Foundations/keymaster/blob/d003619c9bde950e5935ce8f74bcdc2b4b327a45/lib/authutil/authutil.go#L294. To prevent future changes to the api for the ldap userinfo can you also add those to the library so that when we fix the library we dont need to backport much?

Which API are you suggesting to change? I think the generic interface should not change.
Are you suggesting adding parameters to userinfo/ldap.New? That's OK in principle.
I note that the Keymaster code seems more complicated. Why is the Cloud-Gate group lookup code simpler?
If we're considering changing the API, how about removing the pointer for the groupPrefix parameter to the GetUserGroups method? Also, I'd prefer to remove that parameter entirely and just have a tiny support function that performs this operation. It feels like the wrong layer the way it is now.

We need a way to filter groups at the server side.. a group filter (generic) would be OK for the ldap backend. But I agree that the removal of the groupprefix would be the right thing to do. The correct implementation actually the one one from keymaster.


Add individual members in a github team/org

Hi @trstringer
I'm not sure whether this is possible or not without a PAT but I want to add individual members under a particular org.

not complete org
not a team
but only a single member -> I'm not sure whether the action also works on members without considering them as a part of org/team

      - name: Manual Approval
        uses: trstringer/manual-approval@v1
        with:
          secret: ${{ secrets.GITHUB_TOKEN }}
          approvers: user1,user2,user3
          minimum-approvals: 1

I'm getting the following error:
Attempting to expand user <org-name>/<user1> as a group (may not succeed)
GET https://api.github.com/orgs/<org-name>/teams/<user1>/members: 404 Not Found []

Let me know if I'm missing something.
Any help is appreciated.

@trstringer I was able to solve the issue but later got into the problem, it created multiple similar issues.


firewall: Only accept messages from trusted peer ids

We can add new functionality to the firewall to only accept messages that initiated from a list of trusted peer ids.
User can update this list inside firewall config. If the list is empty, node accepts all incoming messages.

@b00f Should we work on this issue or close it?
Old issue....


Binding TextBox Text property to DynamicResource does not display value

Repro:
<TextBox Text="{DynamicResource FontSizeSmall}" IsReadOnly="True"/>

FontSizeSmall is defined in BaseLight.xaml
<sys:Double x:Key="FontSizeSmall">10</sys:Double>

Just tried this and it doesn't work on WPF either:


Need description about callRateLimit

[Enter feedback here]
The document about "Increase rate limit" should explain callRateLimit on Azure Portal's Resouce JSON
Some user after requesting increasing rate limit does not understand whether the request is approved and reflected the services.
At the situation, the customer can see the Resource JSON as the following picture but there are no explanation about callRateLimit.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: ae5c928f-d510-8974-e582-1d0cbf0b3097
Version Independent ID: 6fc84ab4-bbfd-ae00-a0df-0cd220acc902
Content: Auto-scale AI services limits - Azure AI services
Content Source: articles/ai-services/autoscale.md
Service: azure-ai-services
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

@verb55nta
Thanks for your feedback! We will investigate and update as appropriate.

@verb55nta
I've delegated this to @PatrickFarley, a content author, to review and share their valuable insights.

I will ask PM how to check a resource's current rate limit

@verb55nta Once you're approved, you'll receive an email showing how much quota was approved

Feel free to reopen if you have any follow-up questions
#please-close


Preview is inconsistent with post

Steps to reproduce
Click on "Create Post"
Fill in title with "HTML <ruby> tag"
Expected behavior
Within the preview div
I should see the the preview's title as "HTML <ruby> tag"
Actual behavior
Instead I see the preview title as "HTML tag"
When I click "Submit"
Then I see the Post's title as "HTML <ruby> tag"

I think this line: https://github.com/hashrocket/tilex/blob/master/assets/js/post_form.js#L107
should use the .text function, not the .html function


Thermis IO sensor - HA shows Unknown when temperature is exactly = 0

[x] I have read the Readme, including the Advanced section regarding debugging.

Describe the bug
I have two Somfy Thermis WireFree II io. Everything is OK, but when the sensor parameter Core:TemperatureState = 0, then state of sensor is Unknown. It should be exactly = 0. On screeenshot with graph you can see that value is not on graph when it is exactly 0.
To Reproduce

When the outside temperature is 0 you will see it in Home Assistant GUI

Expected behavior
Sensor state shoudl be 0.
Screenshots

Environment (please complete the following information):

ha-tahoma version: 2.4.2

Home Assistant version: Home Assistant 2021.1.5

Platform: sensor
Device: Thermis io

Model: TemperatureSensor

Type: Firmware: io:TemperatureIOSystemSensor

Additional context

Thanks for reporting @LubikR, good catch. It seems like 0 is returned as None.
This is due to if 0 expression will result in false.
https://github.com/iMicknl/ha-tahoma/blob/c170fb01ee9e00487c19f288a57c8cd10eb6d9e8/custom_components/tahoma/sensor.py#L137
We need to fix this in an upcoming version.

Thanks for reporting @LubikR, good catch. It seems like 0 is returned as None.
This is due to if 0 expression will result in false.
https://github.com/iMicknl/ha-tahoma/blob/c170fb01ee9e00487c19f288a57c8cd10eb6d9e8/custom_components/tahoma/sensor.py#L137
We need to fix this in an upcoming version.


Package import dependencies

@ddunbar - Apologies, I somehow missed your review comment. I responded and some of the feedback has been corrected in the latest version of this PR. Please take a look and let me know what you think!


Ignore newline differences in compiler tests

Currently, apollo-compiler's tests fail on Windows because checkTestFixture directly compares file contents, but Windows writes newlines differently from Unix.

This fixes that by stripping carriage return (\r) characters from the compared strings.

Thanks for catching this. 2 comments:

I opened an issue to see if it's easy to run Travis on Windows (https://github.com/apollographql/apollo-android/issues/1696). That might help maintain windows in the long run.
I'm not sure where the \r come from. There shouldn't be any \r in the commited test fixtures. Are they added by File.readText() ? That would seem weird to me.

That might help maintain windows in the long run.

That'd be good of course, but realistically I think I'm in the minority when it comes to dev environments. If it adds too much complexity/annoyance to maintain, I totally understand leaving it out.

I'm not sure where the \r come from

Checking it out..

I believe the \rs are added by Git during checkout, respecting the core.autocrlf setting.

TIL git changes my data :scream:...
What about a .gitattributes file ?
# apollo generates code without carriage return. Make sure git does not add them when checking out the test fixtures
apollo-compiler/src/test/graphql/com/example/* text eof=lf

Granted there's very little change but if for some reason, codegen starts generating \r, I would still like the tests to fail.

That might make sense. Will leave it for a repo owner to decide. (cc @sav007)

I think it makes totally sense to add .gitattributes file for test fixtures. @DSteve595 could you pls add it?

Will do once I'm back on my Windows machine.

Very sorry for the silence, I completely forgot about this. Thanks to @martinbonnin for reminding me about it.
I just pushed a directory-scoped gitattributes file defining LF line endings for .kt and .java files in the test dir.


Save button in AddNewExpense doesn't become to enable

After end of Exercise 3, Save button can't click just after filled all form items.
Repro step:

Input Type, Description, Amount, Location, City, and select date on CalendarView.

If setting focus any textbox control, then the Save button become to enable.

Thanks Kazuki. It seems that the problem is that the XAML Islands control doesn't trigger the focus changed event. With the starting WPF DatePicker control, when you press TAB and you move from the City field to the Date one the "CanExecute" in the ViewModel is revaluated. But it doesn't happen when you move from the City field ot the UWP Calendar control.
I'll investigate if there's an easy way to fix this. Feel free to take a look as well if you bandwidth!

I think that the workaround of this issue is add UpdateSourceTrigger argument with PropertyChanged value to Binding of all TextBox controls in AddNewExpense.xaml.
How do you think about this workaround?

Fixed in b7a7721


Don't panic in pump_write when a client is dropped and there are more calls to poll.

This can happen in cases where a response is being read and the client isn't around.
Fixes #220

@d1vyank let me know if this fixes it for you.

@d1vyank let me know if this fixes it for you.

It does, thanks!
PS: the CI fails because futures-preview does not compile with the current nightly: https://github.com/rust-lang-nursery/futures-rs/issues/1518


Demo is broken

Traceback (most recent call last):
  File "C:/Users/micha/dev/warpath-bot/adb_demo.py", line 4, in <module>
    from adb import sign_cryptography
ImportError: cannot import name 'sign_cryptography' from 'adb' (D:\ProgramData\Anaconda3\lib\site-packages\adb\__init__.py)

Check the old version of the README:
https://github.com/google/python-adb/blob/c610a56fb65c46b6438ac7d6a05faf07b44d5485/README.md#using-as-a-python-library
This was changed since version 1.3.0.


iOS: View logs doesn't work properly

The issue is that, when the logs are long, they don't appear properly in the TextView. It would be preferable if we could open the logs in a 3rd-party application.

The bug has been fixed, and the fix will be available in the next (major) app release: v1.6.0


Error when running sample 'AuthenticationManager' Class

Hello,
CSOM Version: 16.1.20211.12000
When attempting to add the sample 'AuthenticationManager' class to a project the following error is encountered:
'ClientContext' does not contain a definition for 'FormDigestHandlingEnabled'
When using the previous (non-standard) version the project compiles correctly.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 80e62a9d-06d0-ebc3-2c99-ce459388182a
Version Independent ID: 07d8b090-b18c-842d-ba1e-0f2b2a127ad3
Content: Using CSOM for .Net Standard instead of CSOM for .Net Framework
Content Source: docs/sp-add-ins/using-csom-for-dotnet-standard.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

@jansenbe did mention in his demo that the FormDigestHandlingEnabled property is redundant so my guess is this was removed from the published version but it still exists in the docs.

Yeah, it seems to work just commenting it out.

As noted by @vman, this was by design related on the authentication changes with the package. All other areas are working in parity between different versions.


Unknown support for obj files.

Godot version
4.x
System information
Android13
Issue description
I'm trying to import the obj model file on Android but there seems to be some compatibility issues? You can do two tests on both the computer and the mobile side to make sure what I'm saying is true.

Steps to reproduce
Create an obj file and import it into the Godot engine on Android.
Minimal reproduction project
test.zip

Under no circumstances should a cube look like this

Under no circumstances should a cube look like this

I need to declare that this is a "door" resource that I found from itch resources, but it appears in such a state in the engine.

Are you 100% sure the models look proper in Blender, that the materials aren't set as two-sided

This is the obj file from my last photo, you can try opening it on blender
door

For files exported by blender this is completely invisible in the editor

You can see the object only in the preview

Watch this video

I can confirm that that the cube's bottom triangle is missing on Gdoot Engine steam stable.

Maybe the 4.1.1 version fixed the problem.

@clayjohn @m4gr3d @BastiaanOlij Any ideas how to test on Android? The broken obj import seems to be a specific bug.

4.1.1 did not fix the export problem, in fact, when I repeatedly tried to import obj files, I found that their shapes would become strange

I confirm the bug with 4.1.1 on Android (Xiaomi Poco F1). Both the mobile and GL renderer seem to have the same issue.
I tried switching the MRP's obj to import as scene, which didn't solve it, but after switching back to import as mesh I managed to get a good import (3 default cubes). Then hitting reimport again made the cubes disappear.

sure

Please, fixing this bug is important to me

Please, fixing this bug is important to me

Issues are resolved by contributors on a best-effort basis. We can't provide an ETA on when this will be fixed.

hi guys, I have an idea why this might be happening. I have 2 devices: realme c21 with android 11 and Xiaomi pad 5 with android 13. I've been programming on both of them using C++. I have created a graphical application using SDL2. As you know, SDL2 uses double buffering, and if everything was fine on Realme, then on Xiaomi pad 5 the second buffer was constantly changing, various incomprehensible pieces appeared there, and sometimes it was completely cleaned. I solved the problem by manually creating a buffer.
As I said, the problem was only on the Xiaomi pad 5. I decided to check if the problem is related to the device. I asked a friend for a Poco 3 pro and after launching the program, I realized that the problem was related to either MIUI or android 13.
In the end, I decided to download Godot 4 on Realme c21 and the result only confirmed my theory: the problem is related to either MIUI or android 13. As far as I understand, something affects dynamic memory when no one uses it and in order to solve the problem, it is necessary to save data in dynamic memory, until then, while this data will not be needed.  Also, the erase command sometimes breaks data in the container, I didn't look at the code, but if the erase command is used, then you should be more careful with it.
I hope this information helps a little.
Realme c21:

Xiaomi pad 5:
https://github.com/godotengine/godot/assets/143567019/1634c184-6a9b-4e8f-8773-445a3f0c2105


Hls/duys

https://tls.mbed.org/

Content deleted and issue closed as it looked like a malicious link


Configure development of services utils and models

development service and models articles

this is module for service and models


On installation showing error Could not resolve io.github.lizhangqu:coreprogress:1.0.2.

My react-native - 0.70.6
and used react-native-compressor - 1.6.1
after installing using command  npm i react-native-compressor  when i run the project  it will threw an error
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':react-native-compressor:compileDebugAidl'.

Could not resolve all task dependencies for configuration ':react-native-compressor:debugCompileClasspath'.
Could not resolve io.github.lizhangqu:coreprogress:1.0.2.
Required by:
project :react-native-compressor
Skipped due to earlier error
Skipped due to earlier error
Please help to fix the issue ...

@mlecoq  @alariej  @numandev1  @closetothe  Please help to overcome the issue

@iasreact1  I don’t reproduce this issue, do you have an example to reproduce it

🙏 sorry for a long ago I was not maintaining due to the huge office workload, hopefully, I am going to start fixing bugs on a weekend basis,
I will fix at least 2 issues on the weekend, for priority bugs you can join the discord channel https://discord.gg/dtYzk8sp where we can discuss which bug is most important

@iasreact1 is this issue reproducing again?

removed io.github.lizhangqu:coreprogress implementation completely


There is no timeline/ among requests

As said, there is no "timeline/" request made by Instagram :(

Thank you @pronode and @alessiomonzillo, feel free to add this feature ;)


Highlight coinbase repartition problem

Hi !
What about display a color when a verified blockchain as a coin repartition problem ?
For instance, if Anders initially receive only 10 coin, the second block (and therefore the next ones) should be marked as suspect (with a yellow/orange color ?), because Anders gives money he doesn't have.
Even if this is out of scope of the blockchain implementation, it could be an easy way to teach about exchange verification using blockchains.
Maybe another tab, in order to keep things simple ?

Yeah, not a bad idea. I think there are many questions that come up that could benefit from visual explanations like this but I won't have time to do them all. Please feel free to fork the project and add stuff like this!


[docs] Add stray Joy UI documentation improvements

[x] I have followed (at least) the PR section of the contributing guide.

This PR tweaks almost every currently available Joy UI page. They're all simple changes, though, and mostly on the Markdown files. Generally, I'm just going for tiny style fixes, light copywriting updates, and overall formatting refinement. Some of the trends I've identified that got me thinking and interested in opening this PR:

I think we use way too many callouts, there's a lot of them on some pages.
There are a few cases where we introduce sections⎯with a callout⎯that are just a couple of lines away.
Some components had the "learn how to extend the variants" callout but others don't. I removed some of them, for now. It's valuable information we should probably append consistently in the "Variants" section.
Placement of the extra info chips below the introduction demo. I moved them all to be above it so that, once we introduce tabs in the Joy docs as well, it's a smoother transition.

@siriwatknp mind taking a look here?


Update Signing SDK path in Cartfile

Updates the path to the Hyperledger repo
Signed-off-by: Darian Plumb<EMAIL_ADDRESS>

Can you update the README as well? The section that explains how to import the SDK should point to this repo.


Improper name convertion for "ProjectVRAction"

Given this type:
type ProjectVRAction {
  name: String!
}

The generated code is:
export type ProjectVrAction = {
  __typename?: 'ProjectVRAction';
  name: Scalars['String'];
};

Notice the small 'r' in 'Vr'. Is there anyway I can keep it the same as the GraphQL entity?

Solved by adding the option config: { namingConvention: "keep" }


Annotate the word "generally" in useEffect()

This is challenging

How to create the command
How to locate the word by the command
How to modify the DOM
How to make it idempotent

sth like this, let's first try to add just add a link to it.
![Screenshot 2024-04-12 at 22 25 51](https://github.com/JSerZANP/deeper-dive/assets/69352453/ecb32980-89f3-4741-
b596-2f725079598e)


Feature/Help request: Mouse decouple

Hello! I really like the function execution ability of the radial menu, I have looked through the AHK files and cannot find how to decouple the mouse from the menu entirely. A setting that I would like to request is:
"menu does not react to and does not influence mouse movement".  Counter-intuitive for a radial menu but hyper efficient in certain applications. Particularly those who like to operate or must operate without a mouse. This would be a game-changing feature.
The effect would be this:

hotkey is pressed while "menu on center of screen" and "mouse decouple" are enabled
menu appears in the center of the screen and pie slices do not respond to and do not influence mouse input
function key executes pie slice and menu exits -OR- esc is pressed and menu exits

If this is something commented out in the AHK files somewhere or if I can be pointed to where I could test this, then I would be happy to.
Edit:
I have the menu opening in a static position regardless of mouse movement, this is close, I just need to figure out how to make that position at the center.

Got it, you want to use a pie menu by using the slice hotkeys only and a "Mouse decouple" checkbox.  I'll be able to get this in the next version, but that won't be ready until Tuesday.  If you want to test this out, take a look at line 1177 and make this change (duplicate and comment out original lines):
	; returnObj["midDistance"] := midDist
	returnObj["midDistance"] := 0
	; returnObj["distance"] := dist
	returnObj["distance"] := 0

This will make the menu think the mouse is always in the center of the menu.  Then to prevent AHP from moving your mouse to the center, comment out line 1879:
; MouseMove, p2_dimensions[1]+((p2_dimensions[2]-p2_dimensions[1])/2), p2_dimensions[3]+((p2_dimensions[4]-p2_dimensions[3])/2), 0
Also for AHP to use the AHK files instead of the EXE you just have to check this option:

Let me know what launch mode you're using this through.

Thanks a lot! I will absolutely try it.  Indeed, I have been using that feature. Much appreciated! I will tinker with that alteration.

Hell yea!  This should be easy to implement, should be able to get to this over the weekend but I'm happy it worked!

This has been added in v1.0.20

This has been added in v1.0.20

Fantastic. You literally made a menu for almost any game, congratulations and thank you for adding this.


Use the banned modules plugin in the bundle size tests

We had huge bundle size savings by removing the assert dependency. Let's make sure it doesn't come back!

For assert, trying to add it back would also show a sizable bundle size increase, but this adds an extra level of enforcement. So I'm curious how proactive you think we should be with banning packages.  I can see the common node polyfills immediately making their way onto this list after this, but for other packages that someone tries to add and are flagged by the size detector, I wouldn't think we need to add them to shortcut this in the future?
Also it looks like base-host is here to stay so the same packages should probably be banned from both

For assert, trying to add it back would also show a sizable bundle size increase, but this adds an extra level of enforcement. So I'm curious how proactive you think we should be with banning packages. I can see the common node polyfills immediately making their way onto this list after this, but for other packages that someone tries to add and are flagged by the size detector, I wouldn't think we need to add them to shortcut this in the future?
Also it looks like base-host is here to stay so the same packages should probably be banned from both

The concern I have (which I've seen in many repos) is that folks don't notice or investigate the bundle size increases. Given how bit the assert one is, I'd like to have it be one of the things we use to block.


GH-2799 avoid OOM through HashMap resizing by setting initial size

GitHub issue resolved: #2799
Briefly describe the changes proposed in this PR:

initialize the LinkedHashModel with a fixed size equal to the threshold we use for overflow to disk - this should avoid unexpected resizing before overflow is triggered
note that LinkedHashModel itself internally already uses size * 2 for the statement set to compensate for the load factor, so using the exact block size should be fine for our purposes

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[ ] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[x] I've squashed my commits down to one or a few meaningful commits
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change
[x] every commit has been signed off

There's a bit of a false assumption in this change I just realized, due to poor variable/constant naming: although the LARGE_BLOCK constant plays a roll in the overflow trigger, it is not as simple as "overflow when we have more statements than this fixed constant".
Alternative is that we move the "10% of the heap is still free" requirement up a bit, to, say, 15%?

I think we should start with a test, or a benchmark if that's easier. Essentially limit the memory available and load in a big file. I'm also curious if this scales as it should, eg. does loading in a bigger file while giving more memory trigger the overflow as consistently as loading a smaller file with less memory available?

Not at my desk right now, but I believe there's an existing compliance test for the overflow that we could extend if necessary.

I'm not aware of a simple way to control the available heap space for a single junit test - so we may want to "abuse" a jmh benchmark for this purpose. I'm currently out of spare time, so won't continue on this immediately. @hmottestad if you have an idea and time/will to set up such a test feel free to add it on to this branch.

After I commented here I set out to google if maybe junit 5 could fork the JVM for a test to configure the amount of memory. Could not find anything. I guess abusing JMH might be the only way unfortunately.

To be fair even with benchmarking in place there's only so much we can do to make  this work better: at the end of the day we are relying on an estimate of available heap space and predicted usage to trigger disk overflow. In real life situations that estimate could be way off because of circumstances beyond our control (e.g. some different Java object suddenly consuming a lot of memory or something as basic as the data currently being uploaded suddenly containing a few massive literal values). We make a best effort, but we can't guarantee the process won't run out of memory.

Btw a reason disk syncing on memory overflow is giving us such a performance hit was given by Arjohn Kampman on the mailinglist:

The reason that syncing the data to disk when the overflow is triggered takes so long is also related to a call to dataset(). When overflowToDisk() calls disk.addAll(memory), this triggers a call to SailSourceModel.add(s,p,o,c...) for each statement. This method then calls both contain(s,p,o,c...) and sink().approve(s,p,o.c) for for each statement. The latter call starts a new transaction and updates the txn-status file, but the contains() call then commits the transaction for the previous statement via a call to dataset(), again updating the txn-status file. So for every cached statement, rdf4j does two I/O calls. On a spinning disk with a an average write time of 10 ms, this limits the overflow process to at most 50 statements per second.

That is not directly related to this fix, but if we can address some of that, we can have more confidence that setting a lower overflow threshold won't cause a massive performance penalty.

Do you mind @jeenbroekstra if I force push this branch? I would like to add a commit with a benchmark as the first commit in this branch so that we can easily test before and after.

Go for it

ok, I've just force pushed, but will need to force push at least one more time before I'm done.

I've added two benchmarks, one synthetic and one with a real world file.
The synthetic one I've got failing with very low memory. The real world file I've got failing with higher memory. Both are failing at different places. And to make things even more complicated the real world file is failing only within a certain memory range (500-700 MB), outside of that range it either overflows correctly or doesn't need to overflow.

The synthetic benchmark only fails on java 8 for me.

Related: #2998

Not going to dig any further now. I've spent like 3 hours on this because IntelliJ was acting up and running the benchmarks takes a long time.

I'm becoming more and more convinced that we should invest in replacing the current MemoryOverflowModel with a completely different implementation, something that just relies on standard Java Object Serialization or some simple abstraction like MapDB for disk syncing. I will try and spike something, see what we get.

Maybe for the time being just try to adjust the point where the model overflows to disk. Perhaps you can add some logging to show what it currently thinks is going on memory wise so you can see what numbers it's comparing. Also maybe try without Xms in the benchmark.
The real world benchmark is best to start with I think.

I did some logging and found out that sometimes the algorithm would decide that the max block size was something like 10 MB. This is when it would overflow. So I've just added a hard limit of 32MB of required available memory. This works fine for both my tests (benchmarks) and I feel it's a reasonable tradeoff. How many users give their NativeStore 64MB or 128MB and then load large files?

I did some logging and found out that sometimes the algorithm would decide that the max block size was something like 10 MB. This is when it would overflow. So I've just added a hard limit of 32MB of required available memory. This works fine for both my tests (benchmarks) and I feel it's a reasonable tradeoff. How many users give their NativeStore 64MB or 128MB and then load large files?

This seems reasonable to me as well, nice workaround.


OS#18260893 avoid assertion for re-start/stop in debugger mode

@duongnhn was this bug found through oss-fuzz? If so, we should credit them- @akroshg does the credit need to be provided in the commit message?

yes, will do

In reply to: 411627408 [](ancestors = 411627408)


an idea about the performance improvement

Combine with the work practice,in my own opinion,the mq need append a function to invoke some slave mq broker to remember store the specified time span(or may be the offset) messages,which can improve the performance when some receiver need to use the message in special time or after some lag problem of the receiver.The nameserver may be use to schedule the  concrete details which is config by the user flexibly or changable or  when the laged-message receiver append to the mq.In the k8s situation ,also can combine the pods expand peculiarity when use metric tool to add new broker to pass the lagged message to the later receiver.Or can flexible change the connect after the receiver catch with latest message and shut down the redundant broker.If some problems in the design,welcome to communicate me in private.
Ulteriorly,we can separate the brokens use to receive and send the message,when the broker memory if full,the sender can change the destination broker,and the previous broker also handle the request from the receiver,when most/all of the receiver handle the messages,the broker can clear the memory and reday to receive the message in next round,when the receiver handled the message in this broker,the new connection with the newer message broker can be estiblished to consume the newer message.

@zhangyixin1222 I thought you had some very good suggestions, and It would be nice if you can write a more detailed design and send it to the dev mailing list for the discussion.


foreman refresh: use object refs instead of ids

Save inventory converts a hash to a collection of active record objects.
Sometimes one of these collections links to another.
pseudo code for linking records:
  save_inventory_multi(code_lookup_hash, :find_id => [:ems_ref])
  store_ids_for_new_records(code_lookup_hash, :find_id => [:ems_ref])
  target_hash.each {|tgt| tgt[:code_id] = code_lookup_hash.detect {|c| c.ems_ref == tgt[:code_ref]}[:id]}
  save_inventory_multi(target_hash, :ignore => :code_ref)

If it is a self reference:
  save_inventory_multi(obj, :hosts, target_hash, :find_id => [:ems_ref], :ignore => :parent)
  store_ids_for_new_records(obj.hosts, target_hash, :find_id => [:ems_ref])
  obj.hosts.each do |o|
    o.update_attributes(:parent_id => target_hash[o.id][:parent][:id])
  end

New suggested code is to just store the active record reference in the hash instead of the id:

no need to saving the record first
no need to store_ids_for_new_records which loops through all active record objects for lookup.
use the active record association rather than using the id.
only 1 line change in core code.
No need to change any existing code, but it would make sense to leverage it.

Gave example how this affects foreman. We have another PR #2440 that leverages this
/cc @gmcculloug @brandondunne @Fryguy

Can you show an example of the database queries (you can get them running through console).  I think this is ok (after GregM explained to me), but I'm concerned about thrashing.  Or perhaps, just run it twice in console and verify you don't have thrashing on records.

@Fryguy  good call gist
Yes, confirmed, no thrashing.
Not happy with all the duplicate lookups.
Really looks like we are calling association(true) too many times in our code. but the refresh is littered with that.

@blomquisg had concern with storing ar_object in the hash.
I think this is just a logical progression from storing :id in the hash.
In the future, it would be nice if save_inventory_multi returned something like [[hash, ar_object],[hash, ar_object]] - but that is probably for another day

@blomquisg @Fryguy Does this meet your concerns? If not, just say so.
(this PR is blocking 2440 that is blocking 1 or 2 others)

Loading the locations and organizations over and over again is a form of thrashing.  It should not be necessary if the save_inventory chain is done correctly.  However those are not affected by the changes in this PR and so were there already.
What might be affected by this PR is that configuration_script loading over and over again...that should not be happening.  Did that happen when you were use ids?  Was there a specific reason you didn't use ids like we do elsewhere?

Thrashing is not from this PR.
This thrashing is due to a record having a second habtm layer.
When we were loading these in a single manager, it was easy. no need to lookup all of these in the database, just once at the REST layer and sync each relationship to the database. (the id lookup happened automatically as part of the sync)
Since this is loading at a second level habtm, each of the children loads the relationships. I'll look into include and see if removing the relation(reload=true) helps this.

See how we already handle habtm and just do the same thing.   Essentially
we save one thing first completely to the database,  then when the second
thing comes along we just link back to the existing records.   This there
is no need for double lookups or the  N+1.
If you have N+1 at the rest layer that should not translate down to the
save inventory.
On Apr 1, 2015 12:02 PM, "Keenan Brock"<EMAIL_ADDRESS>wrote:

Thrashing is not from this PR.
This thrashing is due to a record having a second habtm layer.
When we were loading these in a single manager, it was easy. no need to
lookup all of these in the database, just once at the REST layer and sync
each relationship to the database. (the id lookup happened automatically as
part of the sync)
Since this is loading at a second level habtm, each of the children loads
the relationships. I'll look into include and see if removing the
relation(reload=true) helps this.
—
Reply to this email directly or view it on GitHub
https://github.com/ManageIQ/manageiq/pull/2473#issuecomment-88533776.

Is this problem related to this PR?
I am looking into it, but wondering if that should be blocking this PR

Going to return objects from save_inventory
This will allow us to go many directions from there


runHearth CardUniverse parameter

runHearth should take a Set Card argument for its known card universe. This is relevant for effects like UnstablePortal, Webspinner, etc. Note that it is safe to have a universe contain RazorfenHunter but not contain Boar. This is because Boar is built into RazorfenHunter (it is summed by card, not by name).

Note: This completely sidesteps the need for a registerCard function.

Need to vet that the card names for all the supplied cards are unique.
Need:
ExternalSetName :: Namespace -> String -> SetName
ExternalCardName :: SetName -> String -> CardName
Namespace :: Url -> Namespace


Stop only if module folder removed

Closes: https://github.com/metarhia/impress/issues/1321

[x] tests and linter show no problems (npm t)
[x] code is properly formatted (npm run fmt)
[x] description of changes is added in CHANGELOG.md

Landed in https://github.com/metarhia/impress/commit/6f1d45145c86870f3c8e10344963eb2cd542ec9f


Update es_dump_restore tool

This will pick up David's change here https://github.com/patientslikeme/es_dump_restore/pull/22
which should stop our env sync job from failing as much.
Trello: https://trello.com/c/8FAmik4j/311-data-sync-for-elasticsearch-its-been-failing-a-lot

Bumped the version again as a fix for https://github.com/alphagov/env-sync-and-backup/pull/35 has been merged.


Unable to send statistics under proxy

With current wakatime-cli implementation there is no possibility to send statistics under proxy
Under proxy warning messages appear in wakatime.log file:
"level": "WARNING",
"message": {
	"traceback": "Traceback (most recent call last):
  File \"/home/zee/.config/sublime-text-3/Packages/WakaTime/packages/wakatime/wakatime/__init__.py\", line 306, in send_heartbeat
    response = urlopen(request)
  File \"/usr/lib/python2.7/urllib2.py\", line 127, in urlopen
    return _opener.open(url, data, timeout)
  File \"/usr/lib/python2.7/urllib2.py\", line 404, in open
    response = self._open(req, data)
  File \"/usr/lib/python2.7/urllib2.py\", line 422, in _open
    '_open', req)
  File \"/usr/lib/python2.7/urllib2.py\", line 382, in _call_chain
    result = func(*args)
  File \"/usr/lib/python2.7/urllib2.py\", line 1222, in https_open
    return self.do_open(httplib.HTTPSConnection, req)
  File \"/usr/lib/python2.7/urllib2.py\", line 1184, in do_open
    raise URLError(err)
URLError: <urlopen error [Errno 111] Connection refused>
", "URLError": "<urlopen error [Errno 111] Connection refused>"
}

I think there should be some properties that enables statistics collection under proxy.
P.S. I really enjoy wakatime statistics with its plugins variety. Nice work!

Implemented with 5986a5634dddadeb03bfdc9d75ff1a1e3c49b420


Javascript backticks messing up syntax.

I'm getting javascript backticks (ES7 compliant JS), messing up the entire syntax of the file:
I think the js library needs to be updated.

same issue here

Is this still an issue? If so, please reopen.


Revert "Deprecate nix-shell use (#663)"

This reverts commit f83e8bb9e36bdb23c2d21acf9439867480ebdfc4.
Removing nix.shell broke support in VS Code

@Isaac-DeFrain I don't agree that we support VSCode.

We don't now. Should we remove ./.vscode then and modify .gitignore?

Closing to pursue direnv support

Yup, thanks for helping give direction to all these efforts, Isaac. I think it's all settled now - we don't "support" VSCode in this repo, but direnv is supported, and there is a VSCode plugin for direnv which enables Nix support.


added search header

DCWC-639
Description
Added a search bar header section to the search results page.
List of proposed changes:

Added search header and related component
Added tests for search header

What to test for/How to test
Additional Notes

Done in #63


Downloaded videos in wrong folder if using local time for file naming

I've enabled "UseLocalTime=true" in the Blink.ini file.  When files are automatically downloaded, they are placed in the Month\Day folder based on UTC, rather than being placed into folders appropriately based on local time.  I noticed this while looking for a particular clip that was approximately 8pm local time (I'm UTC+6).  This file ended up being in the folder for a day "later" than I'd have expected based on local time, but was correct for UTC.

I'm aware of this issue, should be easy to solve. I will solve it for next release thanks.


Don't Merge! Regression PR perf testing with metadata validation

Docs Build status updates of commit d17a828:
:clock10: Pending: waiting for processors (32 builds ahead of you)
:warning: Docs Build is busy, currently there are 32 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit d17a828:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

api/overview/azure/automation.md
:white_check_mark:Succeeded
View

[Warning] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.
[Warning] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit d17a828:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

api/overview/azure/automation.md
:white_check_mark:Succeeded
View

[Warning] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.
[Warning] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


“Bot Framework Emulator” can’t be opened because Apple cannot check it for malicious software.

Version
4.8.1
Description
“Bot Framework Emulator” can’t be opened because Apple cannot check it for malicious software.
macOs (10.15.3) is showing this error dialog while opening the Emulator
Screenshots

Useful Link
https://stackoverflow.com/questions/59149730/heroku-pkg-can-t-be-opened-because-apple-cannot-check-it-for-malicious-softwar

Hi @jithinputhiyattu ,
Thanks for the report!
It seems like since Mac OSX Catalina (10.15.x), applications must now be notarized by Apple as well in order to be completely whitelisted by Apple and not show this dialog. (Source)
We are currently working on adding this notarization step into our release pipeline so that Mac Users no longer see this system dialog when launching the Emulator.
We will leave this issue open until this task is completed, and will update the issue accordingly.

This has been added to our R9 milestone, planned to ship in mid May.

Is this issue resolved already ?

Hi @gourav1995 ,
No, this issue has not been resolved yet.

So it mean I can not work with Bot Emulator on Mac?

@gustavoalv We can work with Bot Emulator on Mac. It just has to be tagged as safe to open in the "Security and Privacy" section like this. The first time you open Emulator it would have queued up this warning in the Privacy section. Once marked safe you can continue using and you wont be prompted in the future.


477

touchui-composite-multifield doesn't load values for several field types e.g. checkbox, dropdown selection #477
@justinedelson @davidjgonzalez

@schoudry thanks!

@schoudry Is there an event that is triggered when the data is loaded?
The values for the multifield are set after the foundation-contentloaded event is triggered, so the content is not yet available then

Selection box is working but still checkbox values are not persisting in the dialog when used under multifield


How come it work with two different models?

To perform a knowledge distillation, the teacher and the student model must have the same tokenizer. But you have used two different teacher models, that is Llama and GPT2, and these both have different tokenizers, thus their probabilities cannot be compared. So my doubt is, how come it works?

We use one and the same tokenizer trained on the BabyLM training dataset for all models. Llama and GPT2 refer to the architectures in HF Transformers, not the original pretrained models.

So you have trained a custom Llama and GPT2 models with your custom tokenizer. And then you have used the same custom tokenizer to train the BabyLlama as well. Am I right?

Oh thank you. It's mentioned in the paper, and I just read it. So you have trained it on an RTX 3090 right? What is the peak memory usage?

Yes. If I remember correctly, it was  below 20 GB with the default hyper parameters (still ~100% utilization). You can always reduce it by decreasing the batch size and increasing gradient_accumulation_steps.

Thanks for the info. I'm planning on running it on a 3060 with 12GB VRAM, I think I have to drastically reduce the batch size and increase gradient_accumulation_steps by a bit

Well, if you don't want to change the lr,  proportionally increase gradient_accumulation_steps  so that the logical_bsz =  gradient_accumulation_steps * bsz stays the same.

logical batch size? Sorry I did not get you

Ah, I mean that with the gradient accumulation you have effective (or logical) batch size which is equal to bsz * gradient_accumulation_steps
You want to keep this effective batch size constant.

So I need to try to match my logical bsz to your actual bsz by increasing the gradient accumulation

Yep
batch_size -> batch_size / factor
gradient_accumulation_steps ->  gradient_accumulation_steps * factor
I would start with factor = 2, and increase till it fits.

Once again, thanks a lot for the clarification. Closing this issue by the way


Branch resolve duplicate recent dates

This commit resolves https://github.com/AY2122S2-CS2103T-T17-3/tp/issues/117.
Now, users are not allowed to input a duplicated contacted date.

Codecov Report

Merging #119 (1dea9b7) into master (da01ae4) will increase coverage by 0.14%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #119      +/-   ##
============================================
+ Coverage     71.48%   71.62%   +0.14%
- Complexity      649      653       +4
============================================
  Files           110      110
  Lines          2104     2111       +7
  Branches        216      219       +3
============================================
+ Hits           1504     1512       +8
+ Misses          542      541       -1
  Partials         58       58

Impacted Files
Coverage Δ

...ddress/logic/parser/AddContactedCommandParser.java
93.33% <ø> (ø)

...main/java/seedu/address/model/date/RecentDate.java
100.00% <ø> (+5.55%)
:arrow_up:

...ddress/logic/commands/AddContactedInfoCommand.java
88.88% <100.00%> (+0.65%)
:arrow_up:

...a/seedu/address/model/description/Description.java
90.90% <100.00%> (ø)

...c/main/java/seedu/address/model/person/Person.java
96.20% <100.00%> (+0.31%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update da01ae4...1dea9b7. Read the comment docs.


Update Tekton Chains to 0.14.0

https://issues.redhat.com/browse/HACBS-1529
Signed-off-by: Luiz Carvalho<EMAIL_ADDRESS>

/lgtm


How to train with GPU?

How to train with GPU because it takes too long to train with CPU.

The training script is written to support training on single and multiple gpus, it uses all the available gpus by default. If you are facing any issues with gpu utilization please check if cuda and cudnn are installed correctly.


Add missing dependency in dev.txt.

@johngian quick r? This is needed for fake-factory.

Coverage remained the same at 92.534% when pulling 8c2bb19df7611f8e5c0324fd20b2c50da6e87d03 on akatsoulas:update-requirements into 5db27d78c5db43e86a1bd895ab83289d8d430545 on mozilla:master.

r+


Please review improvements

customizable via config object/file, better docs, more granular design
added args to some of the fakers and added a few extras such as: geo coordinate near
allow custom faker sections and split into separate faker function section files
allow passing custom faker object via config

PS: Not yet tested

I'd suggest you just go through it one commit at a time to follow the changes and my thinking.
Consult the updated Changelog.md for an overview of the main changes. I will test it shortly on my end.
Happy for now. Fully customisable!

I'd suggest you just go through it one commit at a time to follow the changes and my thinking.

@kristianmandrup Sorry, but every big change should be submitted and discussed as a separate PR. If you want your changes to be merged please break them into separate PRs.

Sure, but not until my work has stabilised and has been tested. I'll close this PR for now then.

@kristianmandrup Great 👍
Sure, take as much time as you need.
Looking forward to your PRs.

Sure. I will add a jest test suite as well to document it works as expected and make it clear how to use and extend the new functionality.


Geocode returns [0.0, 0.0]

Hi, I have the following setup for my Prospect model:
class Prospect < ApplicationRecord
  geocoded_by :ip_address do |obj, results|
       geo = results.first.try(:data)

       if obj.ip_address.present? && geo.present?
           obj.update_columns(latitude: geo['latitude'], longitude: geo['longitude'])
       end
   end
end

In config/initializers/geocoder.rb I have:
Geocoder.configure(
    language: :en,
    timeout: 3,
    use_https: true,
    lookup: :google,
    ip_lookup: :ipstack,
    ipstack: {
        use_https: false,
        api_key: ENV['IPSTACK_API_KEY']
    },
    google: {
        api_key: ENV['GOOGLE_API_KEY']
    }
)

If I try to geocode an instance of Prospect like so, I get invalid coordinates for a valid ip address.
prospect.ip_address
=> "<IP_ADDRESS>" # This is a Los Angeles IP address
prospect.geocode
=> [0.0, 0.0] # ???

I can't figure out why this is not working. It was working previously with freegeoip until recently. I've been over the documentation on using multiple providers several times and it's very confusing to say the least. For example, it's not at all clear how the gem determines which provider to use for lookup vs ip_lookup or if I need to specify which service to use for which function.

The gem will detect whether you're trying to geocode an IP address or a physical address and use the appropriate lookup. Can you run Geocoder.search("<IP_ADDRESS>") to help determine whether the problem is in getting the data or in assigning it to the object?

Ok, thanks for that clarification on how it works.Here is the output of that command:
Geocoder.search("<IP_ADDRESS>")
=> [#<Geocoder::Result::Ipstack:0x000055bbc048d740 @data={"ip"=>"<IP_ADDRESS>", "type"=>"ipv4", "continent_code"=>nil, "continent_name"=>nil, "country_code"=>nil, "country_name"=>nil, "region_code"=>nil, "region_name"=>nil, "city"=>nil, "zip"=>nil, "latitude"=>nil, "longitude"=>nil, "location"=>{"geoname_id"=>nil, "capital"=>nil, "languages"=>nil, "country_flag"=>nil, "country_flag_emoji"=>nil, "country_flag_emoji_unicode"=>nil, "calling_code"=>nil, "is_eu"=>false}}, @cache_hit=nil>]

I'm not getting results for that address from freegeoip or ipinfo.io either. Looks like a hole in the database.
Closing, because I think this is an API issue, not a gem issue.

I have tons of others that fail too. I've also tried them with ipinfo.io and they still fail. Do you have any recommendations on better API providers or is there a way to configure the gem to try multiple providers until it either finds the address or fails?

I'd recommend checking out any of the non-free solutions, but know that IP address is just not possible in 100% of cases, or even close to it. Eg: https://www.maxmind.com/en/geoip2-city-accuracy-comparison