syncing a node

Which environment are you setting a node for?
Mainnet
Does your machine match the technical requirements?
Yes
Have you completed the setup?
Yes
Which method are you using?
Snapshot
Did you build your binary from source or download it from the Releases page?
Downloaded from Releases page
Please, share the contents of config.toml
# This is a TOML config file.
# For more information, see https://github.com/toml-lang/toml

# NOTE: Any path below can be absolute (e.g. "/var/myawesomeapp/data") or
# relative to the home directory (e.g. "data"). The home directory is
# "$HOME/.cometbft" by default, but could be changed via $CMTHOME env variable
# or --home cmd flag.

#######################################################################
###                   Main Base Config Options                      ###
#######################################################################

# TCP or UNIX socket address of the ABCI application,
# or the name of an ABCI application compiled in with the CometBFT binary
proxy_app = "tcp://<IP_ADDRESS>:17610"

# A custom human readable name for this node
moniker = "Cosmostation"

# If this node is many blocks behind the tip of the chain, FastSync
# allows them to catchup quickly by downloading blocks in parallel
# and verifying their commits
fast_sync = true

# Database backend: goleveldb | cleveldb | boltdb | rocksdb | badgerdb
# * goleveldb (github.com/syndtr/goleveldb - most popular implementation)
#   - pure go
#   - stable
# * cleveldb (uses levigo wrapper)
#   - fast
#   - requires gcc
#   - use cleveldb build tag (go build -tags cleveldb)
# * boltdb (uses etcd's fork of bolt - github.com/etcd-io/bbolt)
#   - EXPERIMENTAL
#   - may be faster is some use-cases (random reads - indexer)
#   - use boltdb build tag (go build -tags boltdb)
# * rocksdb (uses github.com/tecbot/gorocksdb)
#   - EXPERIMENTAL
#   - requires gcc
#   - use rocksdb build tag (go build -tags rocksdb)
# * badgerdb (uses github.com/dgraph-io/badger)
#   - EXPERIMENTAL
#   - use badgerdb build tag (go build -tags badgerdb)
db_backend = "goleveldb"

# Database directory
db_dir = "data"

# Output level for logging, including package level options
log_level = "info"

# Output format: 'plain' (colored text) or 'json'
log_format = "plain"

##### additional base config options #####

# Path to the JSON file containing the initial validator set and other meta data
genesis_file = "config/genesis.json"

# Path to the JSON file containing the private key to use as a validator in the consensus protocol
priv_validator_key_file = "config/priv_validator_key.json"

# Path to the JSON file containing the last sign state of a validator
priv_validator_state_file = "data/priv_validator_state.json"

# TCP or UNIX socket address for CometBFT to listen on for
# connections from an external PrivValidator process
priv_validator_laddr = ""

# Path to the JSON file containing the private key to use for node authentication in the p2p protocol
node_key_file = "config/node_key.json"

# Mechanism to connect to the ABCI application: socket | grpc
abci = "socket"

# If true, query the ABCI app on connecting to a new peer
# so the app can decide if we should keep the connection or not
filter_peers = false

#######################################################################
###                 Advanced Configuration Options                  ###
#######################################################################

#######################################################
###       RPC Server Configuration Options          ###
#######################################################
[rpc]

# TCP or UNIX socket address for the RPC server to listen on
laddr = "tcp://<IP_ADDRESS>:17602"

# A list of origins a cross-domain request can be executed from
# Default value '[]' disables cors support
# Use '["*"]' to allow any origin
cors_allowed_origins = []

# A list of methods the client is allowed to use with cross-domain requests
cors_allowed_methods = ["HEAD", "GET", "POST", ]

# A list of non simple headers the client is allowed to use with cross-domain requests
cors_allowed_headers = ["Origin", "Accept", "Content-Type", "X-Requested-With", "X-Server-Time", ]

# TCP or UNIX socket address for the gRPC server to listen on
# NOTE: This server only supports /broadcast_tx_commit
grpc_laddr = ""

# Maximum number of simultaneous connections.
# Does not include RPC (HTTP&WebSocket) connections. See max_open_connections
# If you want to accept a larger number than the default, make sure
# you increase your OS limits.
# 0 - unlimited.
# Should be < {ulimit -Sn} - {MaxNumInboundPeers} - {MaxNumOutboundPeers} - {N of wal, db and other open files}
# 1024 - 40 - 10 - 50 = 924 = ~900
grpc_max_open_connections = 900

# Activate unsafe RPC commands like /dial_seeds and /unsafe_flush_mempool
unsafe = false

# Maximum number of simultaneous connections (including WebSocket).
# Does not include gRPC connections. See grpc_max_open_connections
# If you want to accept a larger number than the default, make sure
# you increase your OS limits.
# 0 - unlimited.
# Should be < {ulimit -Sn} - {MaxNumInboundPeers} - {MaxNumOutboundPeers} - {N of wal, db and other open files}
# 1024 - 40 - 10 - 50 = 924 = ~900
max_open_connections = 900

# Maximum number of unique clientIDs that can /subscribe
# If you're using /broadcast_tx_commit, set to the estimated maximum number
# of broadcast_tx_commit calls per block.
max_subscription_clients = 100

# Maximum number of unique queries a given client can /subscribe to
# If you're using GRPC (or Local RPC client) and /broadcast_tx_commit, set to
# the estimated # maximum number of broadcast_tx_commit calls per block.
max_subscriptions_per_client = 5

# Experimental parameter to specify the maximum number of events a node will
# buffer, per subscription, before returning an error and closing the
# subscription. Must be set to at least 100, but higher values will accommodate
# higher event throughput rates (and will use more memory).
experimental_subscription_buffer_size = 200

# Experimental parameter to specify the maximum number of RPC responses that
# can be buffered per WebSocket client. If clients cannot read from the
# WebSocket endpoint fast enough, they will be disconnected, so increasing this
# parameter may reduce the chances of them being disconnected (but will cause
# the node to use more memory).
#
# Must be at least the same as "experimental_subscription_buffer_size",
# otherwise connections could be dropped unnecessarily. This value should
# ideally be somewhat higher than "experimental_subscription_buffer_size" to
# accommodate non-subscription-related RPC responses.
experimental_websocket_write_buffer_size = 200

# If a WebSocket client cannot read fast enough, at present we may
# silently drop events instead of generating an error or disconnecting the
# client.
#
# Enabling this experimental parameter will cause the WebSocket connection to
# be closed instead if it cannot read fast enough, allowing for greater
# predictability in subscription behaviour.
experimental_close_on_slow_client = false

# How long to wait for a tx to be committed during /broadcast_tx_commit.
# WARNING: Using a value larger than 10s will result in increasing the
# global HTTP write timeout, which applies to all connections and endpoints.
# See https://github.com/tendermint/tendermint/issues/3435
timeout_broadcast_tx_commit = "10s"

# Maximum size of request body, in bytes
max_body_bytes = 1000000

# Maximum size of request header, in bytes
max_header_bytes = 1048576

# The path to a file containing certificate that is used to create the HTTPS server.
# Might be either absolute path or path related to CometBFT's config directory.
# If the certificate is signed by a certificate authority,
# the certFile should be the concatenation of the server's certificate, any intermediates,
# and the CA's certificate.
# NOTE: both tls_cert_file and tls_key_file must be present for CometBFT to create HTTPS server.
# Otherwise, HTTP server is run.
tls_cert_file = ""

# The path to a file containing matching private key that is used to create the HTTPS server.
# Might be either absolute path or path related to CometBFT's config directory.
# NOTE: both tls-cert-file and tls-key-file must be present for CometBFT to create HTTPS server.
# Otherwise, HTTP server is run.
tls_key_file = ""

# pprof listen address (https://golang.org/pkg/net/http/pprof)
pprof_laddr = "localhost:17611"

#######################################################
###           P2P Configuration Options             ###
#######################################################
[p2p]

# Address to listen for incoming connections
laddr = "tcp://<IP_ADDRESS>:17600"

# Address to advertise to peers for them to dial
# If empty, will use the same port as the laddr,
# and will introspect on the listener or use UPnP
# to figure out the address. ip and port are required
# example: <IP_ADDRESS>:26656
external_address = "<IP_ADDRESS>:17600"

# Comma separated list of seed nodes to connect to
seeds = "ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:22556,20e1000e88125698264454a884812746c2eb4807@seeds.lavenderfive.com:22556"

# Comma separated list of nodes to keep persistent connections to
persistent_peers = "149c2c4cc6a3585b74183cbd288ce7691cb1c92b@<IP_ADDRESS>:26656,c14b1ded8ada662f88f07dc48df344bf3b0f6dae@<IP_ADDRESS>:26656,e0b89511a7a31d7867c00cfba748b474f853ac49@<IP_ADDRESS>:26656,af204f59efdc08efd5c450cab46645e19a9caffe@<IP_ADDRESS>:26656,9859172af3fbd0769b449a9c766aebf651f74a2e@<IP_ADDRESS>:55786,269273e7065748ec4aefa595a40156c292861064@<IP_ADDRESS>:26656,f591dd0778a0659035255c8f7e44002faea2156f@<IP_ADDRESS>:26656,d32b3e22cfcb72e11050db30a59a59cd05646046@<IP_ADDRESS>:26656,034c1f179321a7cc7106b0f8b021881bb2276622@<IP_ADDRESS>:31850,e44ee7bc8eaf83025f3fb4b7a6a300d760b61c86@<IP_ADDRESS>:26656,a5d984f145ea828048a0741a1d349f9fa13a643b@<IP_ADDRESS>:26656,5b5d0c20d54ec9a37a7c249b30966b257fd45d83@<IP_ADDRESS>:26656,01de75368e56b38fc27a22c07236d50319ed129d@<IP_ADDRESS>:26656,c4c9e9fb6182ef115531000dbf7d4ebb19e5460c@<IP_ADDRESS>:31850,7069d3e30752526ab512b43cdd7aca1012d9a142@<IP_ADDRESS>:26656,4a7c6688342b87f5a8f7aa59c6f28642abbfef5b@<IP_ADDRESS>:26656,9dcdb2297ea7032de58948ee8d044641378f8fed@<IP_ADDRESS>:26656,0f1b077a1110f30e618dfc756a6195fd3d4206ed@<IP_ADDRESS>:26656,ac4cbf842e38402e70f8297bcde0821c4d93d233@<IP_ADDRESS>:26656,e04ee1d6b5cc1aa24f7c1ab55139d1cec9962e39@<IP_ADDRESS>:26656,d4c884bb26ada8138a1160dcbb739229feb5245f@<IP_ADDRESS>:26656,3a78a843dd91d0d21a429e7f47038a99a1d74b16@<IP_ADDRESS>:35656,90f0b8ae47c7ef1b943ede2dfaed4bf228941514@<IP_ADDRESS>:26656,91e8bfc81374c3cb9e507f491b16a7b316aeb9dd@<IP_ADDRESS>:26656,b015384cceb3d25492c96a882ba84ad644b45402@<IP_ADDRESS>:26656,12654d64b312688b5ab5682e13a6ff1b6021eac7@<IP_ADDRESS>:26656,6fdc0f47d80fa2e948744469b21232f5ae64f91e@<IP_ADDRESS>:26656,f75a16acfd914846c2eee65b03df6e8fd129e225@<IP_ADDRESS>:26663,055bdda1a2f92d4d36c57b2c5aef1e5f5b85ffb6@<IP_ADDRESS>:26656,4d7a52d68af698c296211dec34a26cddefeb0b06@<IP_ADDRESS>:26656,912d07ae1c869e7a573c09cb7397304874388b5b@<IP_ADDRESS>:26656,d56a65e856443cf97fab922580de21cb234de51f@<IP_ADDRESS>:26656,8316df0565d02fe07b7e930599fe4217dd2cb69b@<IP_ADDRESS>:26656,1a3c98ff37355422d6f128543700d75e9e91a660@<IP_ADDRESS>:26656,4f610429b23eea677fef49712b9f182772403879@<IP_ADDRESS>:26656,6a6ae6ccfa3e10e8cab52135880e17c0786b71bb@<IP_ADDRESS>:26656,b1d9d61babda397dd0afcace80a93e60f113f54c@<IP_ADDRESS>:26673,28bb1ddb796e78168e3a6db71781dc7894e4fe84@<IP_ADDRESS>:22556,6a529474d63c4f2463b2765be9cafef5deaead52@<IP_ADDRESS>:27656,c37f642698260707c0e25a8895f9d36735318ef3@<IP_ADDRESS>:26656,0edfd371e5bc03ee5096ad241a2a02e335177285@<IP_ADDRESS>:26656,1d888c5985a536b53e528ad276b20294edb93592@<IP_ADDRESS>:26656,2462fd9bfbb84f7a3945ce3e2380e70ad17da6f0@<IP_ADDRESS>:26656,598ea52e6a902ef96cc7dadf496bc9cb2c366d5f@<IP_ADDRESS>:26656,f55f191f5036289ce0b7c2aee5aea6a3421e4a1d@<IP_ADDRESS>:26656,d6da4409e915b4c64e25e8bdb8afad90f802181e@<IP_ADDRESS>:26656,a2e3b668edf5b12a84e3fe39dbf61219354bd27f@<IP_ADDRESS>:26656,3353ed61bd79f746a0c43c9d805f6e6e07e8af17@<IP_ADDRESS>:26656,20dfec771f33b142c211abba14b9fe438510768f@<IP_ADDRESS>:26656,bfdd895017abc5c9f0d16f077f4fb40afbd9b8e4@<IP_ADDRESS>:26656,67b2dff23378c7a7db9afc56f227efab565d01cf@<IP_ADDRESS>:26656,c74771d56a065c9f3c9f3077a5f8e845df26312f@<IP_ADDRESS>:39656,ef2b470f8151625e62a486776b1d57a8563a5730@<IP_ADDRESS>:22556,730c0abcca73f74034ab27d6e033121caf021f19@<IP_ADDRESS>:26656,9de0360c8e816cf3b8202e0403674b1c228c3f44@<IP_ADDRESS>:26656,6554807a10fd2d0e34b8daeed3fee38b8ca048b6@<IP_ADDRESS>:26656,d105bb46800c46d3c6094b623dbe45077150baca@<IP_ADDRESS>:26656,ef6d163c0f85cb50922203543d1587a111c24f7c@<IP_ADDRESS>:26656,6fc8c0229962a581cba920ce7fbb5dcfba82f444@<IP_ADDRESS>:26656,b6f9b4304ea941f1766f86418eb6bbe93d4258f9@<IP_ADDRESS>:10656,bdb30db8eda58257e2fb5e79e7d8f0b5bc5d1f10@<IP_ADDRESS>:26656,c088a771008ad9f253c26dd7a517698624a829a4@<IP_ADDRESS>:26656,29451598238188abf748a62bdb45a852ee0392e6@<IP_ADDRESS>:26656,637077d431f618181597706810a65c826524fd74@<IP_ADDRESS>:22556,361057c02769a7cf218caae1939cb3e38cf58cf0@<IP_ADDRESS>:26656,9a346b83bfa243a9c8466156952ed3c161a7813c@<IP_ADDRESS>:26656,0ddce6317a9153b138532efb5051be585b752b96@<IP_ADDRESS>:26656,a6feed5c5f68127c332e468f87d10fe842e72b33@<IP_ADDRESS>:26656,cda49d4af5da9a3c5b01be36663b2257d49cc309@<IP_ADDRESS>:26656,a132ebfd8995be14b723336723839b8abfee82d6@<IP_ADDRESS>:31850,2326ab7d77bfaa301872f88fa8e0c065d3f46218@<IP_ADDRESS>:26656,e35b6f3968ec9616b646b0aa25920e19f6f21727@<IP_ADDRESS>:26656,a8d3eddaf7f91994cec2d75e2bdcada3445b8368@<IP_ADDRESS>:26656,0ae725c03483a17aa5f9b4ebbaf394924e404927@<IP_ADDRESS>:26656,2319b4676036fefc0fc083c0dec0a4ea37d85094@<IP_ADDRESS>:26656,34cd73db43d6c2852b07a4aa4bd92d404750ec85@<IP_ADDRESS>:22556,199b4ab0f9c2bca20f2a4682ff0d625f4afc30d0@<IP_ADDRESS>:16056,ee3a1efa596915328ddeae0198306afd94e5e848@<IP_ADDRESS>:22556,a3eda7526ccd7a3c78d199e8f71dbf2f7b3eee0f@<IP_ADDRESS>:26656,cae2ff2304ed86aa1635b7ee5ca795fd42d161fc@<IP_ADDRESS>:26656,13e67f1345dfacc0b2c81a7a624ff730099754f4@<IP_ADDRESS>:56556,87fd46a7304473fc4aeb6af12d656d3ea06e235d@<IP_ADDRESS>:26656,6d8296e6222eb992ff4814d950ed30630f924253@<IP_ADDRESS>:26656,b855a804a4caf334bc74794b48608b39f05f58d5@<IP_ADDRESS>:26656,233ffd3d2c4c97bb170f5bc6dd5e69d0f4d446e1@<IP_ADDRESS>:26656,d8730c76daaf371900159ab8c6e00bc3950eff79@<IP_ADDRESS>:26656,c3107f90796e6503e437134a22431f2a9be7549f@<IP_ADDRESS>:26656,98eb8ce5f00639cb466297c5b9eaa49f4ba55031@<IP_ADDRESS>:26656,4e668be2d80d3475d2350e313bc75b8f0646884f@<IP_ADDRESS>:39656,4d42ce9badc678e98ab429c2df0c095bc1a5b9d9@<IP_ADDRESS>:28656,d72b6ed8c99ffae667363181c6547b9747423aeb@<IP_ADDRESS>:39656"

# UPNP port forwarding
upnp = false

# Path to address book
addr_book_file = "config/addrbook.json"

# Set true for strict address routability rules
# Set false for private or local networks
addr_book_strict = true

# Maximum number of inbound peers
max_num_inbound_peers = 40

# Maximum number of outbound peers to connect to, excluding persistent peers
max_num_outbound_peers = 10

# List of node IDs, to which a connection will be (re)established ignoring any existing limits
unconditional_peer_ids = "eea4892699aa8d0d54491fd2164720687d7ffc93,fb7222250e62c55cc69dec6bc8aa8807f859215c"

# Maximum pause when redialing a persistent peer (if zero, exponential backoff is used)
persistent_peers_max_dial_period = "0s"

# Time to wait before flushing messages out on the connection
flush_throttle_timeout = "100ms"

# Maximum size of a message packet payload, in bytes
max_packet_msg_payload_size = 1024

# Rate at which packets can be sent, in bytes/second
send_rate = 5120000

# Rate at which packets can be received, in bytes/second
recv_rate = 5120000

# Set true to enable the peer-exchange reactor
pex = true

# Seed mode, in which node constantly crawls the network and looks for
# peers. If another node asks it for addresses, it responds and disconnects.
#
# Does not work if the peer-exchange reactor is disabled.
seed_mode = false

# Comma separated list of peer IDs to keep private (will not be gossiped to other peers)
private_peer_ids = ""

# Toggle to disable guard against peers connecting from the same ip.
allow_duplicate_ip = false

# Peer connection configuration.
handshake_timeout = "20s"
dial_timeout = "3s"

#######################################################
###          Mempool Configuration Option          ###
#######################################################
[mempool]

# Mempool version to use:
#   1) "v0" - (default) FIFO mempool.
#   2) "v1" - prioritized mempool.
version = "v1"

# Recheck (default: true) defines whether CometBFT should recheck the
# validity for all remaining transaction in the mempool after a block.
# Since a block affects the application state, some transactions in the
# mempool may become invalid. If this does not apply to your application,
# you can disable rechecking.
recheck = true
broadcast = true
wal_dir = ""

# Maximum number of transactions in the mempool
size = 5000

# Limit the total size of all txs in the mempool.
# This only accounts for raw transactions (e.g. given 1MB transactions and
# max_txs_bytes=5MB, mempool will only accept 5 transactions).
max_txs_bytes =<PHONE_NUMBER>

# Size of the cache (used to filter transactions we saw earlier) in transactions
cache_size = 10000

# Do not remove invalid transactions from the cache (default: false)
# Set to true if it's not possible for any invalid transaction to become valid
# again in the future.
keep-invalid-txs-in-cache = false

# Maximum size of a single transaction.
# NOTE: the max size of a tx transmitted over the network is {max_tx_bytes}.
max_tx_bytes = 1048576

# Maximum size of a batch of transactions to send to a peer
# Including space needed by encoding (one varint per transaction).
# XXX: Unused due to https://github.com/tendermint/tendermint/issues/5796
max_batch_bytes = 0

# ttl-duration, if non-zero, defines the maximum amount of time a transaction
# can exist for in the mempool.
#
# Note, if ttl-num-blocks is also defined, a transaction will be removed if it
# has existed in the mempool at least ttl-num-blocks number of blocks or if it's
# insertion time into the mempool is beyond ttl-duration.
ttl-duration = "0s"

# ttl-num-blocks, if non-zero, defines the maximum number of blocks a transaction
# can exist for in the mempool.
#
# Note, if ttl-duration is also defined, a transaction will be removed if it
# has existed in the mempool at least ttl-num-blocks number of blocks or if
# it's insertion time into the mempool is beyond ttl-duration.
ttl-num-blocks = 0

#######################################################
###         State Sync Configuration Options        ###
#######################################################
[statesync]
# State sync rapidly bootstraps a new node by discovering, fetching, and restoring a state machine
# snapshot from peers instead of fetching and replaying historical blocks. Requires some peers in
# the network to take and serve state machine snapshots. State sync is not attempted if the node
# has any local state (LastBlockHeight > 0). The node will have a truncated block history,
# starting from the height of the snapshot.
enable = true

# RPC servers (comma-separated) for light client verification of the synced state machine and
# retrieval of state data for node bootstrapping. Also needs a trusted height and corresponding
# header hash obtained from a trusted source, and a period during which validators can be trusted.
#
# For Cosmos SDK-based chains, trust_period should usually be about 2/3 of the unbonding time (~2
# weeks) during which they can be financially punished (slashed) for misbehavior.
rpc_servers = "https://zetachain-rpc.polkachu.com:443,https://zetachain-rpc.polkachu.com:443"
trust_height = 3599505
trust_hash = "517748DF1F8101B7B30BF0B733ADC208319BBB015DF05B552E25AF7C0AA6FF7C"
trust_period = "168h0m0s"
# Time to spend discovering snapshots before initiating a restore.
discovery_time = "15s"

#BAC8BE462D24CD0740084D63D9BC447C6078F06740C4EDBBDDC66085074DB5D0
#3599505

# Temporary directory for state sync snapshot chunks, defaults to the OS tempdir (typically /tmp).
# Will create a new, randomly named directory within, and remove it when done.
temp_dir = ""

# The timeout duration before re-requesting a chunk, possibly from a different
# peer (default: 1 minute).
chunk_request_timeout = "10s"

# The number of concurrent chunk fetchers to run (default: 1).
chunk_fetchers = "4"

#######################################################
###       Fast Sync Configuration Connections       ###
#######################################################
[fastsync]

# Fast Sync version to use:
#   1) "v0" (default) - the legacy fast sync implementation
#   2) "v1" - refactor of v0 version for better testability
#   2) "v2" - complete redesign of v0, optimized for testability & readability
version = "v0"

#######################################################
###         Consensus Configuration Options         ###
#######################################################
[consensus]

wal_file = "data/cs.wal/wal"

# How long we wait for a proposal block before prevoting nil
timeout_propose = "3s"
# How much timeout_propose increases with each round
timeout_propose_delta = "500ms"
# How long we wait after receiving +2/3 prevotes for “anything” (ie. not a single block or nil)
timeout_prevote = "1s"
# How much the timeout_prevote increases with each round
timeout_prevote_delta = "500ms"
# How long we wait after receiving +2/3 precommits for “anything” (ie. not a single block or nil)
timeout_precommit = "1s"
# How much the timeout_precommit increases with each round
timeout_precommit_delta = "500ms"
# How long we wait after committing a block, before starting on the new
# height (this gives us a chance to receive some more precommits, even
# though we already have +2/3).
timeout_commit = "5s"

# How many blocks to look back to check existence of the node's consensus votes before joining consensus
# When non-zero, the node will panic upon restart
# if the same consensus key was used to sign {double_sign_check_height} last blocks.
# So, validators should stop the state machine, wait for some blocks, and then restart the state machine to avoid panic.
double_sign_check_height = 0

# Make progress as soon as we have all the precommits (as if TimeoutCommit = 0)
skip_timeout_commit = false

# EmptyBlocks mode and possible interval between empty blocks
create_empty_blocks = true
create_empty_blocks_interval = "0s"

# Reactor sleep duration parameters
peer_gossip_sleep_duration = "100ms"
peer_query_maj23_sleep_duration = "2s"

#######################################################
###         Storage Configuration Options           ###
#######################################################
[storage]

# Set to true to discard ABCI responses from the state store, which can save a
# considerable amount of disk space. Set to false to ensure ABCI responses are
# persisted. ABCI responses are required for /block_results RPC queries, and to
# reindex events in the command-line tool.
discard_abci_responses = false

#######################################################
###   Transaction Indexer Configuration Options     ###
#######################################################
[tx_index]

# What indexer to use for transactions
#
# The application will set which txs to index. In some cases a node operator will be able
# to decide which txs to index based on configuration set in the application.
#
# Options:
#   1) "null"
#   2) "kv" (default) - the simplest possible indexer, backed by key-value storage (defaults to levelDB; see DBBackend).
#               - When "kv" is chosen "tx.height" and "tx.hash" will always be indexed.
#   3) "psql" - the indexer services backed by PostgreSQL.
# When "kv" or "psql" is chosen "tx.height" and "tx.hash" will always be indexed.
indexer = "null"

# The PostgreSQL connection configuration, the connection format:
#   postgresql://<user>:<password>@<host>:<port>/<db>?<opts>
psql-conn = ""

#######################################################
###       Instrumentation Configuration Options     ###
#######################################################
[instrumentation]

# When true, Prometheus metrics are served under /metrics on
# PrometheusListenAddr.
# Check out the documentation for the list of available metrics.
prometheus = true

# Address to listen for Prometheus collector(s) connections
prometheus_listen_addr = ":17608"

# Maximum number of simultaneous connections.
# If you want to accept a larger number than the default, make sure
# you increase your OS limits.
# 0 - unlimited.
max_open_connections = 3

# Instrumentation namespace
namespace = "cometbft"

Please, share the contents of app.toml
# This is a TOML config file.
# For more information, see https://github.com/toml-lang/toml

###############################################################################
###                           Base Configuration                            ###
###############################################################################

# The minimum gas prices a validator is willing to accept for processing a
# transaction. A transaction's fees must meet the minimum of any denomination
# specified in this config (e.g. 0.25token1;0.0001token2).
minimum-gas-prices = "0azeta"

# default: the last 362880 states are kept, pruning at 10 block intervals
# nothing: all historic states will be saved, nothing will be deleted (i.e. archiving node)
# everything: 2 latest states will be kept; pruning at 10 block intervals.
# custom: allow pruning options to be manually specified through 'pruning-keep-recent', and 'pruning-interval'
pruning = "default"

# These are applied if and only if the pruning strategy is custom.
pruning-keep-recent = "0"
pruning-interval = "0"

# HaltHeight contains a non-zero block height at which a node will gracefully
# halt and shutdown that can be used to assist upgrades and testing.
#
# Note: Commitment of state will be attempted on the corresponding block.
halt-height = 0

# HaltTime contains a non-zero minimum block time (in Unix seconds) at which
# a node will gracefully halt and shutdown that can be used to assist upgrades
# and testing.
#
# Note: Commitment of state will be attempted on the corresponding block.
halt-time = 0

# MinRetainBlocks defines the minimum block height offset from the current
# block being committed, such that all blocks past this offset are pruned
# from Tendermint. It is used as part of the process of determining the
# ResponseCommit.RetainHeight value during ABCI Commit. A value of 0 indicates
# that no blocks should be pruned.
#
# This configuration value is only responsible for pruning Tendermint blocks.
# It has no bearing on application state pruning which is determined by the
# "pruning-*" configurations.
#
# Note: Tendermint block pruning is dependant on this parameter in conunction
# with the unbonding (safety threshold) period, state pruning and state sync
# snapshot parameters to determine the correct minimum value of
# ResponseCommit.RetainHeight.
min-retain-blocks = 0

# InterBlockCache enables inter-block caching.
inter-block-cache = true

# IndexEvents defines the set of events in the form {eventType}.{attributeKey},
# which informs Tendermint what to index. If empty, all events will be indexed.
#
# Example:
# ["message.sender", "message.recipient"]
index-events = []

# IavlCacheSize set the size of the iavl tree cache.
# Default cache size is 50mb.
iavl-cache-size = 781250

# IavlDisableFastNode enables or disables the fast node feature of IAVL.
# Default is false.
iavl-disable-fastnode = true

# EXPERIMENTAL: IAVLLazyLoading enable/disable the lazy loading of iavl store.
# Default is false.
iavl-lazy-loading = false

# AppDBBackend defines the database backend type to use for the application and snapshots DBs.
# An empty string indicates that a fallback will be used.
# First fallback is the deprecated compile-time types.DBBackend value.
# Second fallback (if the types.DBBackend also isn't set), is the db-backend value set in Tendermint's config.toml.
app-db-backend = ""

###############################################################################
###                         Telemetry Configuration                         ###
###############################################################################

[telemetry]

# Prefixed with keys to separate services.
service-name = ""

# Enabled enables the application telemetry functionality. When enabled,
# an in-memory sink is also enabled by default. Operators may also enabled
# other sinks such as Prometheus.
enabled = false

# Enable prefixing gauge values with hostname.
enable-hostname = false

# Enable adding hostname to labels.
enable-hostname-label = false

# Enable adding service to labels.
enable-service-label = false

# PrometheusRetentionTime, when positive, enables a Prometheus metrics sink.
prometheus-retention-time = 0

# GlobalLabels defines a global set of name/value label tuples applied to all
# metrics emitted using the wrapper functions defined in telemetry package.
#
# Example:
# [["chain_id", "cosmoshub-1"]]
global-labels = [
]

###############################################################################
###                           API Configuration                             ###
###############################################################################

[api]

# Enable defines if the API server should be enabled.
enable = true

# Swagger defines if swagger documentation should automatically be registered.
swagger = true

# Address defines the API server to listen on.
address = "tcp://<IP_ADDRESS>:17601"

# MaxOpenConnections defines the number of maximum open connections.
max-open-connections = 1000

# RPCReadTimeout defines the Tendermint RPC read timeout (in seconds).
rpc-read-timeout = 10

# RPCWriteTimeout defines the Tendermint RPC write timeout (in seconds).
rpc-write-timeout = 0

# RPCMaxBodyBytes defines the Tendermint maximum response body (in bytes).
rpc-max-body-bytes = 1000000

# EnableUnsafeCORS defines if CORS should be enabled (unsafe - use it at your own risk).
enabled-unsafe-cors = false

###############################################################################
###                           Rosetta Configuration                         ###
###############################################################################

[rosetta]

# Enable defines if the Rosetta API server should be enabled.
enable = false

# Address defines the Rosetta API server to listen on.
address = ":8080"

# Network defines the name of the blockchain that will be returned by Rosetta.
blockchain = "app"

# Network defines the name of the network that will be returned by Rosetta.
network = "network"

# Retries defines the number of retries when connecting to the node before failing.
retries = 3

# Offline defines if Rosetta server should run in offline mode.
offline = false

# EnableDefaultSuggestedFee defines if the server should suggest fee by default.
# If 'construction/medata' is called without gas limit and gas price,
# suggested fee based on gas-to-suggest and denom-to-suggest will be given.
enable-fee-suggestion = false

# GasToSuggest defines gas limit when calculating the fee
gas-to-suggest = 200000

# DenomToSuggest defines the defult denom for fee suggestion.
# Price must be in minimum-gas-prices.
denom-to-suggest = "uatom"

###############################################################################
###                           gRPC Configuration                            ###
###############################################################################

[grpc]

# Enable defines if the gRPC server should be enabled.
enable = true

# Address defines the gRPC server address to bind to.
address = "<IP_ADDRESS>:17603"

# MaxRecvMsgSize defines the max message size in bytes the server can receive.
# The default value is 10MB.
max-recv-msg-size = "10485760"

# MaxSendMsgSize defines the max message size in bytes the server can send.
# The default value is math.MaxInt32.
max-send-msg-size = "2147483647"

###############################################################################
###                        gRPC Web Configuration                           ###
###############################################################################

[grpc-web]

# GRPCWebEnable defines if the gRPC-web should be enabled.
# NOTE: gRPC must also be enabled, otherwise, this configuration is a no-op.
enable = false

# Address defines the gRPC-web server address to bind to.
address = "<IP_ADDRESS>:9091"

# EnableUnsafeCORS defines if CORS should be enabled (unsafe - use it at your own risk).
enable-unsafe-cors = false

###############################################################################
###                        State Sync Configuration                         ###
###############################################################################

# State sync snapshots allow other nodes to rapidly join the network without replaying historical
# blocks, instead downloading and applying a snapshot of the application state at a given height.
[state-sync]

# snapshot-interval specifies the block interval at which local state sync snapshots are
# taken (0 to disable).
snapshot-interval = 1500

# snapshot-keep-recent specifies the number of recent snapshots to keep and serve (0 to keep all).
snapshot-keep-recent = 2

###############################################################################
###                         Store / State Streaming                         ###
###############################################################################

[store]
streamers = []

[streamers]
[streamers.file]
keys = ["*", ]
write_dir = ""
prefix = ""

# output-metadata specifies if output the metadata file which includes the abci request/responses
# during processing the block.
output-metadata = "true"

# stop-node-on-error specifies if propagate the file streamer errors to consensus state machine.
stop-node-on-error = "true"

# fsync specifies if call fsync after writing the files.
fsync = "false"

###############################################################################
###                             EVM Configuration                           ###
###############################################################################

[evm]

# Tracer defines the 'vm.Tracer' type that the EVM will use when the node is run in
# debug mode. To enable tracing use the '--evm.tracer' flag when starting your node.
# Valid types are: json|struct|access_list|markdown
tracer = ""

# MaxTxGasWanted defines the gas wanted for each eth tx returned in ante handler in check tx mode.
max-tx-gas-wanted = 0

###############################################################################
###                           JSON RPC Configuration                        ###
###############################################################################

[json-rpc]

# Enable defines if the gRPC server should be enabled.
enable = true

# Address defines the EVM RPC HTTP server address to bind to.
address = "<IP_ADDRESS>:17605"

# Address defines the EVM WebSocket server address to bind to.
ws-address = "<IP_ADDRESS>:17606"

# API defines a list of JSON-RPC namespaces that should be enabled
# Example: "eth,txpool,personal,net,debug,web3"
api = "eth,net,web3"

# GasCap sets a cap on gas that can be used in eth_call/estimateGas (0=infinite). Default: 25,000,000.
gas-cap = 25000000

# EVMTimeout is the global timeout for eth_call. Default: 5s.
evm-timeout = "5s"

# TxFeeCap is the global tx-fee cap for send transaction. Default: 1eth.
txfee-cap = 1

# FilterCap sets the global cap for total number of filters that can be created
filter-cap = 200

# FeeHistoryCap sets the global cap for total number of blocks that can be fetched
feehistory-cap = 100

# LogsCap defines the max number of results can be returned from single 'eth_getLogs' query.
logs-cap = 10000

# BlockRangeCap defines the max block range allowed for 'eth_getLogs' query.
block-range-cap = 10000

# HTTPTimeout is the read/write timeout of http json-rpc server.
http-timeout = "30s"

# HTTPIdleTimeout is the idle timeout of http json-rpc server.
http-idle-timeout = "2m0s"

# AllowUnprotectedTxs restricts unprotected (non EIP155 signed) transactions to be submitted via
# the node's RPC when the global parameter is disabled.
allow-unprotected-txs = false

# MaxOpenConnections sets the maximum number of simultaneous connections
# for the server listener.
max-open-connections = 0

# EnableIndexer enables the custom transaction indexer for the EVM (ethereum transactions).
enable-indexer = false

# MetricsAddress defines the EVM Metrics server address to bind to. Pass --metrics in CLI to enable
# Prometheus metrics path: /debug/metrics/prometheus
metrics-address = "<IP_ADDRESS>:6065"

# Upgrade height for fix of revert gas refund logic when transaction reverted.
fix-revert-gas-refund-height = 0

###############################################################################
###                             TLS Configuration                           ###
###############################################################################

[tls]

# Certificate path defines the cert.pem file path for the TLS configuration.
certificate-path = ""

# Key path defines the key.pem file path for the TLS configuration.
key-path = ""

Additional details
statesync is broken.. When will statesync be fixed?
9:33AM INF error from light block request from primary, removing... error="post failed: Post \"http://<IP_ADDRESS>:17602\": context deadline exceeded" height=3876852 module=light primary={} server=node 9:33AM ERR error on light block request from witness, removing... error="post failed: Post \"http://<IP_ADDRESS>:17602\": context deadline exceeded" module=light primary={} server=node 9:33AM ERR failed to remove witnesses err="no witnesses connected. please reset light client" module=light server=node witnessesToRemove=[0] 9:33AM ERR Can't verify err="failed to obtain the header at height #3876852: post failed: Post \"http://<IP_ADDRESS>:17602\": context deadline exceeded" module=light server=node

hey @kimheeje12, when setting trust_height and trust_hash, are you doing it from latest block?

hey @kimheeje12, when setting trust_height and trust_hash, are you doing it from latest block?

trust_height = 3877080
trust_hash = "C01A7CDE0A1AAAB28840426206912A8E44B04BE9061DBB04E6E43E9D6C7D77C8"

could you please try setting trust_height = (latest_height - 40000) and fetching the trust_hash from that specific height?
trust_hash=$(curl -s "${STATE_SYNC_SERVER}/block?height=${TRUST_HEIGHT}")

that way you will ensure that the node always finds a snapshot

could you please try setting trust_height = (latest_height - 40000) and fetching the trust_hash from that specific height?
trust_hash=$(curl -s "${STATE_SYNC_SERVER}/block?height=${TRUST_HEIGHT}")

that way you will ensure that the node always finds a snapshot

Thank you julianrubino! but.. chunk data is so big ..

@kimheeje12 it shouldn't take more than 30/45 min to sync 40k blocks. are you using ssd or nvme disk?
if you prefer a more consistent way for syncing your node, you could use one of our non-archive snapshots.
https://snapshots.zetachain.com/latest-snapshot?network=mainnet
https://snapshots.zetachain.com/latest-snapshot?network=athens3


[#4646] show Discover map clusters in Firefox

Resolves #4646
Pull Request Checklist:

[x] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

Navigate to https://www.hydroshare.org/search/ using FIREFOX
Show the map
Notice that clusters now show with an icon

BEFORE

AFTER

METRIC
VALUE

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4647


Recommend a candidate when possible

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Motivation and Context / Related issue
For non-deterministic parametrization, this means we won't resample, and we will actually recommend the best past evaluated candidate

How Has This Been Tested (if it applies)

Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CLA).
[x] All tests passed, and additional code has been covered with new tests.

LGTM for the principle of returning a sampled candidate.
admittedly i just checked that the modification was the one I expected to see and did not try to understand much, sorry for low quality review.


nmea_hardware_interfaceにテストを

https://github.com/OUXT-Polaris/nmea_hardware_interface

I added test cases in this PR


Workaround for nonnull operator on indexed accesses

We now force the substitution of an indexed access with its base constraint when getting a type with facts, allowing the resulting type to be filtered. The correct approach would be to apply a lazy subtraction type to the indexed access type, and defer the evaluation until required; however @rbuckton is already working on something which can subsume that purpose.
Fixes #17005

I'm having trouble with an example of the case that this hack breaks. Can you explain more? (See below for details)

No so much breaks as does not fully fix, for example in:
interface A {
    params?: { name: string; }
}

class Test<T extends A> {
    attrs: Readonly<T>;

    m() {
        return this.attrs.params!;
    }
}

The return type of m should be NonNull<T["params"]> - right now it is T["params"] (no null/undefined removed), and with this change it is {name: string} (which is no longer associated with T). Previously if a subclass gave a more specific "params" member type, the m method would return that more specific type - but now not so much.

@sandersn Got your comments. The bulk of the TODO comment has been replaced with a reference to this PR and the associated test, and the associated test now has an example showing where the current behavior is undesirable.

@mmitche The dotnet CI builds on this PR seem to be using an outdated node modules cache (build is failing because it's being build against @types/node@4 instead of 8) - any idea why?

@weswigham No idea...I don't know much about node.


NoMethodError at /omniauth/facebook/callback - undefined method `[]' for nil:NilClass

Hi,
I've updated to:
devise_token_auth 0.1.30
ng-token-auth 0.0.24

and now after redirect to /auth/facebook/callback I get:
NoMethodError at /omniauth/facebook/callback undefined method []' for nil:NilClass`
in
omniauth_success devise_token_auth (0.1.30) app/controllers/devise_token_auth/omniauth_callbacks_controller.rb:24
def omniauth_success
      # find or create user by provider and provider uid
      @resource = resource_class.where({
        uid:      auth_hash['uid'],
        provider: auth_hash['provider']
      }).first_or_initialize

when trying to access auth_hash.
I've tried to clean all browser cache/cookies, removed user from DB in order to have clean installation.

@ignacykasperowicz how did you solve it? I'm stuck with the same problem.

@stefanahman Hmmm, I do not think I was looking at it after in more details, I decided to switch to Ember and used other library for authentication. The issue here was that in devise_token_auth the names of methods had changed I think and that is why I was getting NoMethodError. Sorry I cannot help you more with this.

Hi @kspe , I got the same error using the following request:
GET /api/v1/auth/google_oauth2/callback.json?code=4/hNZXTWia27agrvVUGcbS_LwCIFq00BV0jP6GQ1ViQNM&amz;resource_class=User&redirect_uri= HTTP / 1.1
Host: localhost: 8080
X-Requested-With: XMLHttpRequest
Cache-Control: no-cache
Postman-Token: 9b3760ff-996d-4454-8a77-220f98178ed6

The gem is mounted on the path /api/ v1/auth. Is there a parameter missing in the request?


Address performance bottleneck around VFS updates

@bot-gradle test QFL please

OK, I've already triggered QuickFeedbackLinux build for you.

@bot-gradle test QF please

OK, I've already triggered QuickFeedback build for you.

Superseded by https://github.com/gradle/gradle/pull/14157.


how to fast compare descriptor of certain face with one million other face descriptors

or how to use this library with huge base of face descritors?

https://milvus.io/


Multiple pixel id for difference URL path

I got a problem with the multiple PixelId situation.
for example, when route is at / will use default PixelId.
when route is at /a/* will use PixelId a.
when route is at /b/* will use PixelId b.
To handle these, if plugin has a path option for determine which PixelId match to the path
facebook: [
  {
    /* module option a */
    track: 'PageView',
    pixelId: 'FACEBOOK_PIXEL_ID_A',
    disabled: false,
    path: '/a/*', // will use this option when path is http://foo.bar/a
  },
  {
    /* module option b */
    track: 'PageView',
    pixelId: 'FACEBOOK_PIXEL_ID_B',
    disabled: false,
    path: '/b/*', // will use this option when path is http://foo.bar/b
  },
  {  // will use this option when path are others
    /* module option default */
    track: 'PageView',
    pixelId: 'FACEBOOK_PIXEL_ID_DEFAULT',
    disabled: false,
  },
],

Or can change pixel on the fly with $fb.init('pixelId') or $fb.pixelId('pixelId')
Anyway, I'm looking for the possible methods to handle this.
Thanks 😊

I would love a way to be able to use multiple pixels, but don't need the different path feature (although I see why that would be useful).

@puuga please share is this method work? I would like to put FB pixel dynamically on each page also.
Regards.

FYI - I got this to work inside of the nuxt life cycle hooks (for my example I did it in the created() {} with disabled = true in the nuxt.config.js) with the following:
this.$fb.query('init', 'your pixel code');
this.$fb.track('PageView');
this.$fb.enable();

+1 for multiple pixels support in this module!

Hello there,
Thank you for taking the time to make this issue.
I've added a pixels property to specify multiple pixels according to the route in the release v1.4.0.
See more at https://github.com/WilliamDASILVA/nuxt-facebook-pixel-module#multiple-pixel-codes-according-to-route
Let me know if you have any further issues with that.


[commonjs--resolver] [vike][Wrong Usage] Client-only file /app/components/LangaugeSelect.client.tsx (https://vike.dev/file-env) imported on the server-side by /app/components/Footer.tsx

Description
I don't know if it's a bug or I missunderstood how *.client.ts files work.
I wanted to move my remix app to vike, and in remix this works fine.
I am using this LangaugeSelect component inside of Footer, which is rendered inside DefaultLayout.tsx.
In remix I used little helper <ClientOnly><LanguageSelect/></ClientOnly> which returned nothing on the server and component on the client.
In vike I am unable to build the app with same setup. I also tried clientOnly(() => ...), and react lazy + suspense, but the error message is still here.
If it may be a bug then I can provide more informations.

Minimal reproduction welcome.
On Sun 8. Sep 2024 at 08:49, NotNullDev @.***> wrote:

Description
I don't know if it's a bug or I missunderstood how *.client.ts files work.
I wanted to move my remix app to vike, and in remix this works fine.
I am using this LangaugeSelect component inside of Footer, which is
rendered inside DefaultLayout.tsx.
In remix I used little helper which returned nothing on the server and
component on the client.
In vike I am unable to build the app with same setup. I also tried
clientOnly(() => ...), and react lazy + suspense, but the error message is
still here.
—
Reply to this email directly, view it on GitHub
https://github.com/vikejs/vike/issues/1861, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHVQRSMP545Z57GOZF7AOLZVPXNTAVCNFSM6AAAAABN2WWGCGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYTEMRSHE2DCOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

https://github.com/NotNullDev/vike-client-component/commit/a7027a3aa8fffabeae973bf9a1ca4ce255fae3fd

Can vike support importing client modules in the same way as remix does?
https://remix.run/docs/en/main/file-conventions/-client
https://github.com/remix-run/remix/blob/7dece0e4db691fc9e5dfce27ad6373c46b6ef56c/packages/remix-dev/vite/plugin.ts#L1570
Right now, as far as I understand, it's simply not possible to import .client in ssr mode
https://github.com/vikejs/vike/blob/d84dc798eac0fe5b52e642111650f3bab9f02137/vike/node/plugin/plugins/fileEnv.ts#L61C9-L61C14
https://github.com/vikejs/vike/blob/d84dc798eac0fe5b52e642111650f3bab9f02137/vike/node/plugin/plugins/fileEnv.ts#L109

I could reproduce indeed, let me me fix this. In the meantime you can use clientOnly() without the .client.js suffix.

let me me fix this

ETA next week. In the meantime, feel free to let me know if not using .client.js is an issue for you.

Fix pre-released as 0.4.195-commit-f7e91ba.


cmd/go: crash during loading in dirAndRoot (vendor-related)

@samthanawalla encountered this crash while using the web-based VS Code with a Google VM as the  backend.

The error indicates a crash propagated via gopls and go/packages up from the go command, specifically the dirAndRoot function:
// dirAndRoot returns the source directory and workspace root
// for the package p, guaranteeing that root is a path prefix of dir.
func dirAndRoot(path string, dir, root string) (string, string) {
	origDir, origRoot := dir, root
	dir = filepath.Clean(dir)
	root = filepath.Join(root, "src")
	if !str.HasFilePathPrefix(dir, root) || path != "command-line-arguments" && filepath.Join(root, path) != dir {
		// Look for symlinks before reporting error.
		dir = expandPath(dir)
		root = expandPath(root)
	}

	if !str.HasFilePathPrefix(dir, root) || len(dir) <= len(root) || dir[len(root)] != filepath.Separator || path != "command-line-arguments" && !build.IsLocalImport(path) && filepath.Join(root, path) != dir {
		debug.PrintStack()
		base.Fatalf("unexpected directory layout:\n"+
			"	import path: %s\n"+
			"	root: %s\n"+
			"	dir: %s\n"+
			"	expand root: %s\n"+
			"	expand dir: %s\n"+
			"	separator: %s",
			path,
			filepath.Join(origRoot, "src"),
			filepath.Clean(origDir),
			origRoot,
			origDir,
			string(filepath.Separator))
	}

	return dir, root
}

In addition the VS Code UI showed this truncated error:
Failed to run "go env env, -json, GOMOD": Command failed: /usr/lib/go...

Sorry there's not much to go on yet. I wonder whether the remote machine has as GOPACKAGESDRIVER env var (or $PATH executable).

@hyangah The "failed to run go env" part appears to be from logic in vscode-go bug (in goModules.ts).

We managed to get the complete stack and the actual values in the assertion failure:
Error loading workspace: packages.Load error: err: exit status 1: stderr:

goroutine 3373 [running]:
runtime/debug.Stack()
	runtime/debug/stack.go:24 +0x5e
runtime/debug.PrintStack()
	runtime/debug/stack.go:16 +0x13
cmd/go/internal/load.dirAndRoot({0xc00058ace1, 0x17}, {0xc000c31630, 0x4e}, {0xc000026187, 0x27})
	cmd/go/internal/load/pkg.go:1203 +0x4ad
cmd/go/internal/load.vendoredImportPath({0xc0005bb9c1, 0x4}, {0xc00058ace1, 0x17}, {0xc000c31630?, 0xc000224548?}, {0xc000026187?, 0x48?})
	cmd/go/internal/load/pkg.go:1231 +0x85
cmd/go/internal/load.resolveImportPath({0xc0005bb9c1, 0x4}, {0xc00058ace1, 0x17}, {0xc000c31630, 0x4e}, {0xc000026187, 0x27}, 0x9b?)
	cmd/go/internal/load/pkg.go:1183 +0x9e
cmd/go/internal/load.loadPackageData.func1()
	cmd/go/internal/load/pkg.go:905 +0x1ac
cmd/go/internal/par.(*Cache[...]).Do(0xbb0de0, {{0xc0005bb9c1, 0x4}, {0xc00058ace1, 0x17}, {0xc000c31630, 0x4e}, {0xc000026187, 0x27}, 0x0, ...}, ...)
	cmd/go/internal/par/work.go:160 +0x159
cmd/go/internal/load.loadPackageData({0xbab970, 0xf96260}, {0xc0005bb9c1, 0x4}, {0xc00058ace1, 0x17}, {0xc000c31630, 0x4e}, {0xc000026187, 0x27}, ...)
	cmd/go/internal/load/pkg.go:893 +0x38e
cmd/go/internal/load.(*preload).preloadImports.func1({0xc0005bb9c1?, 0x8?})
	cmd/go/internal/load/pkg.go:1115 +0x8b
created by cmd/go/internal/load.(*preload).preloadImports in goroutine 3883
	cmd/go/internal/load/pkg.go:1114 +0x265
unexpected directory layout:

import path: golang.org/x/mod/semver
root: /usr/local/google/home/samthanawalla/go/src
dir: /usr/local/google/home/samthanawalla/go/src/cmd/vendor/golang.org/x/mod/semver
expand root: /usr/local/google/home/samthanawalla/go
expand dir: /usr/local/google/home/samthanawalla/go/src/cmd/vendor/golang.org/x/mod/semver
separator: /

it seems like the immediate problem is the "root + path = dir" invariant is violated because of a missing "vendor" segment.

I'm surprised that vendoredImportPath is being called at all: that's specific to GOPATH mode, which shouldn't be in use. 🤔
https://cs.opensource.google/go/go/+/master:src/cmd/go/internal/load/pkg.go;l=1177-1183;drc=b32ec6c961182e5bca6ae8420d6aa1204d7d2821

Yeah I think we should figure out why vendoredImportPath is being called. Sam, would you have time to do some debugging of this?

  I had one default installation of Go and one that I built from the github Repo.
This is what fixed it for me:

mv $HOME/go $HOME/w/go/
Copy the output of echo $PATH
Add this line to $HOME/.bashrc: export PATH=$HOME/go/bin:$HOME/w/go/bin:<what you copied from echo $PATH>
unset GOROOT and unset GOPATH.
Reload vscode

This fixed this issue and allowed gopls to work perfectly.


Selection with NOT operator

It would be nice if it was possible to use the selection with an inversion operator allowing concise selection of all field except the one defined.
Something along the lines of:
df[['~col1', '~col2']]

or
df[~['col1', 'col2']]

Looks like you're asking for something like dplyr's -col syntax.  We can do this with strings as you've done in your example.  This could be part of either the getitem syntax or a separate select function.
Personally I rarely need this syntax.  Is this something that you often find yourself using / wanting?  If so I'd be curious what the use case is (just for my own personal curiosity)
This might also be something to think about in Pandas land cc @jreback

we use
df.drop(['col1','col2']) in pandas

@mrocklin
I have a something like a transactional database / transaction log: It contains 3 "natural index columns", 11 data column and a time-stamp column for the entry and a 'validUntil' column that indicates until when the entry is valid.
A common usage is to get the state of the database at an arbitrary point in time:
db = somebackend
d = blaze.Data(db)

# get state of database at a particular point in time (2015-01-26T20:15:46.339000)
# i.e. all entries entered before the timestamp, which are still valid at the time stamp
a = db[(d.validUntil >= '2015-01-26T20:15:46.339000') &
      (d.timeStamp <= '2015-01-26T20:15:46.339000')][['-validUntil', '-timestamp']

@ARF1 we don't have syntax for this right now, but you don't have to explicitly list all the columns you want, just the ones you don't:
cond = ((d.validUntil >= '2015-01-26T20:15:46.339000') &
        (d.timeStamp <= '2015-01-26T20:15:46.339000'))
d[cond][[field for field in d.fields if field not in ('validUntil', 'timeStamp')]]

@ARF1 I'm going to close this as I don't think we'll implement this. I'll offer another suggestion instead :)
You could define a function without that takes the Data instance as the first argument and the columns to ignore as the second argument:
def without(data, ignore):
    return data[[field for field in data.fields if field not in ignore]]

You could use it like this:
result = without(d[cond], ['validUntil', 'timeStamp'])


limitation of having one launchpad per subscription due to hardcoded tags.workspace=="level0"

Hello Folks,
we wanted to have more launchpads within one subscription as separation between environments (dev,test,...). We fast run into the problem when deloying second launchpad because the pipeline always find existing one because it is done by filter based on resource type = storage account with tags: tfstate=level0 & workspace=level0.
Here is reference to the code:
https://github.com/aztfmod/rover/blob/1e1c15cb3c78c79c83acdb2d7341f6258bad3476/scripts/functions.sh#L197
As easy fix it would be to make the tag "workspace" as parameter instead of expect value "level0" which is hardcoded - that's limitation for 1 launchpad per 1 subscription.

Hi @eissko launchpad is not designed to manage an environment but the remote tfstates. If you need multiple environments you can create multiple workspaces
launchpad workspace create
then when you run the rover you can use the -w  to target your environment.
you have an advanced example here https://github.com/aztfmod/level0/blob/master/.github/workflows/ci-branches.yml
So from now we are going to keep this design of 1 level0/workspace level0 per sub.

"to keep this design of 1 level0/workspace level0 per sub" - fair enough. thank you for clarification.


chore(deps): update transitive deps

Description
Updated all transitive deps to pull in potential bug fixes.
refs #18598

@sapphi-red @bluwy apologies for hijacking this PR, didn't want to comment on a closed issue - any chance that #18598 could be backported to v5? Whilst I'm fine with moving to v6.beta, I'm also using dependencies that would no doubt complain at the major version bump.

@mrginglymus I would cut a patch if you send a PR to the v5 branch.

https://github.com/vitejs/vite/pull/18617


Make individual python scripts executable from terminal

-So that we do not need to modify the file to run the script (use argparse).

each script should have an input file and output file argument (not data/default-file-output-file-name in each script) by default you could use standard input and output stream so that you could use pipes (first-script | second_script).. could we?

Finished.


[ layer ] Mixed precision forwarding / backwarding for bn layer @open sesame 03/07 10:42

According to recent papers in mixed precision, when it comes to computation of statistics in bn layer, we should use fp32 values
input(fp16) <-> BN_layer(fp16 weight, but compute with fp32 and re-cast to fp16) <-> output(fp16)
Although we need a bulky code block for this, I believe we can revisit here for cleaner code when TensorV2 becomes official

Self evaluation:

Build test:     [X]Passed [ ]Failed [ ]Skipped
Run test:     [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2462. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

This PR is no longer needed. Close.


NIFI-13119: When evaluating dependent Properties, the UI should identify when the Property value is a parameter reference and resolve the value accordingly

NIFI-13119:

When evaluating dependent Properties, the UI should identify when the Property value is a parameter reference and resolve the value accordingly.

reviewing


Allow zero to be swapped

Something like this maybe:

This was resolved in #47 and released as 3.0.4


OpenSSL autoconfiguration does not recognize 32-bit Raspian GNU/Linux 11 as 32 bit

OpenSSL fails to build on 32-bit Rasbian GNU/Linux 11 on pi 4b hardware. This architecture has a 64-bit kernel and a 32-bit userland. OpenSSL uses the kernel architecture to determine whether to use 64-bit or 32-bit assembly language opcodes. As the userland is 32-bits, the resulting assembly will not generate machine code successfully. As can be seen from the following output, the machine architecture is aarch64 while executables are 32-bit.
$ uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux
$ file $(which file)
/usr/bin/file: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=46998c6200b7bcc2d6b1539b82d4044903017bb4, for GNU/Linux 3.2.0, stripped

Running Configure produces the following configdata:
Command line (with current working directory = .):

    /usr/bin/perl ./Configure --prefix=/usr/local/ssl --openssldir=/usr/local/ssl -Wl,-rpath,$(LIBRPATH)

Perl information:

    /usr/bin/perl
    5.32.1 for arm-linux-gnueabihf-thread-multi-64int

Enabled features:

    afalgeng
    argon2
    aria
    asm
    async
    autoalginit
    autoerrinit
    autoload-config
    bf
    blake2
    bulk
    cached-fetch
    camellia
    capieng
    cast
    chacha
    cmac
    cmp
    cms
    comp
    ct
    default-thread-pool
    deprecated
    des
    dgram
    dh
    dsa
    dso
    dtls
    dynamic-engine
    ec
    ec2m
    ecdh
    ecdsa
    engine
    err
    filenames
    gost
    idea
    legacy
    loadereng
    makedepend
    md4
    mdc2
    module
    multiblock
    nextprotoneg
    ocb
    ocsp
    padlockeng
    pic
    pinshared
    poly1305
    posix-io
    psk
    rc2
    rc4
    rdrand
    rfc3779
    rmd160
    scrypt
    secure-memory
    seed
    shared
    siphash
    siv
    sm2
    sm3
    sm4
    sock
    srp
    srtp
    sse2
    ssl
    ssl-trace
    static-engine
    stdio
    tests
    thread-pool
    threads
    tls
    ts
    ui-console
    whirlpool
    tls1
    tls1-method
    tls1_1
    tls1_1-method
    tls1_2
    tls1_2-method
    tls1_3
    dtls1
    dtls1-method
    dtls1_2
    dtls1_2-method

Disabled features:

    acvp-tests          [cascade]        OPENSSL_NO_ACVP_TESTS
    asan                [default]        OPENSSL_NO_ASAN
    brotli              [default]        OPENSSL_NO_BROTLI
    brotli-dynamic      [default]        OPENSSL_NO_BROTLI_DYNAMIC
    buildtest-c++       [default]
    winstore            [not-windows]    OPENSSL_NO_WINSTORE
    crypto-mdebug       [default]        OPENSSL_NO_CRYPTO_MDEBUG
    devcryptoeng        [default]        OPENSSL_NO_DEVCRYPTOENG
    ec_nistp_64_gcc_128 [default]        OPENSSL_NO_EC_NISTP_64_GCC_128
    egd                 [default]        OPENSSL_NO_EGD
    external-tests      [default]        OPENSSL_NO_EXTERNAL_TESTS
    fips                [default]
    fips-securitychecks [cascade]        OPENSSL_NO_FIPS_SECURITYCHECKS
    fuzz-afl            [default]        OPENSSL_NO_FUZZ_AFL
    fuzz-libfuzzer      [default]        OPENSSL_NO_FUZZ_LIBFUZZER
    ktls                [default]        OPENSSL_NO_KTLS
    md2                 [default]        OPENSSL_NO_MD2 (skip crypto/md2)
    msan                [default]        OPENSSL_NO_MSAN
    quic                [default]        OPENSSL_NO_QUIC
    rc5                 [default]        OPENSSL_NO_RC5 (skip crypto/rc5)
    sctp                [default]        OPENSSL_NO_SCTP
    tfo                 [default]        OPENSSL_NO_TFO
    trace               [default]        OPENSSL_NO_TRACE
    ubsan               [default]        OPENSSL_NO_UBSAN
    unit-test           [default]        OPENSSL_NO_UNIT_TEST
    uplink              [no uplink_arch] OPENSSL_NO_UPLINK
    weak-ssl-ciphers    [default]        OPENSSL_NO_WEAK_SSL_CIPHERS
    zlib                [default]        OPENSSL_NO_ZLIB
    zlib-dynamic        [default]        OPENSSL_NO_ZLIB_DYNAMIC
    zstd                [default]        OPENSSL_NO_ZSTD
    zstd-dynamic        [default]        OPENSSL_NO_ZSTD_DYNAMIC
    ssl3                [default]        OPENSSL_NO_SSL3
    ssl3-method         [default]        OPENSSL_NO_SSL3_METHOD

Config target attributes:

    AR => "ar",
    ARFLAGS => "qc",
    CC => "gcc",
    CFLAGS => "-Wall -O3",
    CXX => "g++",
    CXXFLAGS => "-Wall -O3",
    HASHBANGPERL => "/usr/bin/env perl",
    RANLIB => "ranlib",
    RC => "windres",
    asm_arch => "aarch64",
    bn_ops => "SIXTY_FOUR_BIT_LONG RC4_CHAR",
    build_file => "Makefile",
    build_scheme => [ "unified", "unix" ],
    cflags => "-pthread",
    cppflags => "",
    cxxflags => "-std=c++11 -pthread",
    defines => [ "OPENSSL_BUILDING_OPENSSL" ],
    disable => [  ],
    dso_ldflags => "-Wl,-z,defs",
    dso_scheme => "dlfcn",
    enable => [ "afalgeng" ],
    ex_libs => "-ldl -pthread",
    includes => [  ],
    lflags => "",
    lib_cflags => "",
    lib_cppflags => "-DOPENSSL_USE_NODELETE",
    lib_defines => [  ],
    module_cflags => "-fPIC",
    module_cxxflags => undef,
    module_ldflags => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    perl_platform => "Unix",
    perlasm_scheme => "linux64",
    shared_cflag => "-fPIC",
    shared_defflag => "-Wl,--version-script=",
    shared_defines => [  ],
    shared_ldflag => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    shared_rcflag => "",
    shared_sonameflag => "-Wl,-soname=",
    shared_target => "linux-shared",
    thread_defines => [  ],
    thread_scheme => "pthreads",
    unistd => "<unistd.h>",

Recorded environment:

    AR =
    BUILDFILE =
    CC =
    CFLAGS =
    CPPFLAGS =
    CROSS_COMPILE =
    CXX =
    CXXFLAGS =
    HASHBANGPERL =
    LDFLAGS =
    LDLIBS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB =
    RC =
    RCFLAGS =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =

Makevars:

    AR              = ar
    ARFLAGS         = qc
    CC              = gcc
    CFLAGS          = -Wall -O3
    CPPDEFINES      =
    CPPFLAGS        =
    CPPINCLUDES     =
    CXX             = g++
    CXXFLAGS        = -Wall -O3
    HASHBANGPERL    = /usr/bin/env perl
    LDFLAGS         = -Wl,-rpath,$(LIBRPATH)
    LDLIBS          =
    PERL            = /usr/bin/perl
    RANLIB          = ranlib
    RC              = windres
    RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    Makefile

build file:

    Makefile

build file templates:

    Configurations/common0.tmpl
    Configurations/unix-Makefile.tmpl

And compiling gives the following errors:
crypto/aes/bsaes-armv8.S
crypto/aes/bsaes-armv8.S: Assembler messages:
crypto/aes/bsaes-armv8.S:46: Error: ARM register expected -- `ldr q8,[x9],#16'
crypto/aes/bsaes-armv8.S:47: Error: ARM register expected -- `adr x11,.LM0ISR'
crypto/aes/bsaes-armv8.S:48: Error: bad instruction `movi v9.16b,#0x55'
crypto/aes/bsaes-armv8.S:49: Error: ARM register expected -- `ldr q10,[x11],#16'
crypto/aes/bsaes-armv8.S:50: Error: bad instruction `movi v16.16b,#0x33'

... hundreds more errors ...

crypto/aes/bsaes-armv8.S:2337: Error: ARM register expected -- `ldr x23,[sp,#112]'
crypto/aes/bsaes-armv8.S:2338: Error: bad instruction `ldp d8,d9,[sp,#128]'
crypto/aes/bsaes-armv8.S:2339: Error: bad instruction `ldp d10,d11,[sp,#144]'
crypto/aes/bsaes-armv8.S:2340: Error: bad instruction `ldp d12,d13,[sp,#160]'
crypto/aes/bsaes-armv8.S:2341: Error: bad instruction `ldp d14,d15,[sp,#176]'
crypto/aes/bsaes-armv8.S:2342: Error: bad instruction `ldp x29,x30,[sp],#192'
crypto/aes/bsaes-armv8.S:2343: Error: bad instruction `ret'
make[1]: *** [Makefile:13895: crypto/aes/libcrypto-lib-bsaes-armv8.o] Error 1

Setting the build target manually to linux-armv4 results in selection of the correct 32-bit instruction set.

IMO it would require some extra hoops in the configure target autodetection to recognize such special 32 bit userland with 64 bit kernel targets.

As the configuration with explicit target works correctly I do not think this is a bug per se.

That being said, if there is a better way to detect the userland bitness (I'm not sure that I think that looking at the output of file file is a terribly good criterion), it shouldn't terribly hard to add such a check among the already existing $map_patterns:
https://github.com/openssl/openssl/blob/24a322544373f7acda05e19f64a6c3120d459d5b/util/perl/OpenSSL/config.pm#L466-L965


Can't Use It On Bracktes

Please port it for bracktes i want to use it on bracktes please port it for bracktes please.

Unfavorable it don't seems that easy. Brackets and Atom doesn't share the same code base. Brackets is an entirely different editor, both of them use web technology (JS, HTML, CSS) but have different APIs. So I don't see Docblockr being ported to Brackets, but I found this Brackets package which seems to be similar to Docblockr: brackets-FuncDocr.


Support server-side rendering

Short version

Adds ssr config option to support server-side rendering
Updates README.md to document how the ssr option works
Removes Canvas dev dependency, since it isn't used by anything (and was breaking my local install)
Updates the package description to match the package!

Long version
Thanks a bunch for making this hook!
SSR support
I recently tried to use it in a Next.js app, but I ran into some problems with fractional time and server-side rendering. I found that it was pretty common for the server-side render and the client-side hydration to be a hundredth of a beat off from each other, so React complained about mismatching text.
To fix this, I added an SSR flag to the config object, that prevents setting the default state of time when enabled, and instead immediately sets the current time at the start of the useEffect. Since useEffect isn't run during the server-side pass, the time will evaluate to an empty string in both places on initial render.
I've also updated the README to reflect this option.
Alternate solution
If this seems a bit too absurd (and it kinda does), we might consider always setting the initial state of time to an empty string and always setting the initial time at the start of the useEffect hook. This would make useInternetTime 100% server-side rendering safe at all times, and we could forego this config option.
I think this approach makes sense from a best-practices standpoint, because we're dealing with time. We're just lucky when the server-side pass matches the client-side pass. The only problem with this implementation is that users might see a flash of an empty string on initial render. It's likely that this would be imperceivable, though, since we would basically be moving the state initialization two lines down.
I didn't want to make the call for you, though. If you think the empty string initialization is acceptable, awesome, I'll update this PR to implement that! If not, then the SSR option is the best way to go, and developers can opt-in to the flash of empty text.
Other fixes
I updated the description of the package since it didn't reflect the actual package's offering.
I removed the Canvas dev dependency, because it was having strange issues with node-gyp on my machine, and it doesn't seem to be required by any of the other dev depencencies.
I updated the React peer dependency (by accident, I guess 😅) to 16.13.x, but I can revert that if you want.

Thanks for the review, I left some clarification 👍

Huh, that's a good trick to know. Thanks for finding that! I'll try it out, adjust the docs and code based on the results, and fix the peer dev version.


adapt to breaking chanes in matplotlib API version 3.5.0

Description
This PR addresses the API change in matplotlib version 3.5.0 that currently breaks our code/tests, as raised by Stefan in #183.
Fixes #183
Checklist:

[x] I have performed a self-review of my own code
[x] My code is PEP8 compliant (flake8 anesthetic tests)
[x] My code contains compliant docstrings (pydocstyle --convention=numpy anesthetic)
[x] New and existing unit tests pass locally with my changes (python -m pytest)
[x] I have added tests that prove my fix is effective or that my feature works

Incredible work @lukashergt. From my local tests I believe (although you should check too) that this works on both <3.5 and >3.5. If it does, feel free to squash and merge to get this working again!

Yes, should work for both <3.5 and >3.5.


ALB metrics not updating - using 0.31.0-alpha

I see there are few similar issues - SQS, cloudfront - maybe the same fix is needed also for ALB metrics

I think it's not only about specific resources but all resources metrics are exported only once.
※In my case, Elascticache metrcis are also exported only once.

I'm rolling back to the v0.29.0-alpha and the metrics of my apigateway got back on updating

Should be fixed with newest release

the new version (v0.32) worked for me
Tks @thomaspeitz

Awesome to hear <3


opt Calculate workload group weighted memory limit

when construct workload group, mem_limit is equal to (process_memory_limit * group_limit_percent),
here, it is assumed that the available memory of workload groups is equal to process_memory_limit.
but process_memory_usage is actually bigger than all_workload_groups_mem_usage,
because public_memory of page cache, allocator cache, segment cache etc. are included in process_memory_usage.
so actual available memory of the workload groups is equal to (process_memory_limit - public_memory)
we will exclude this public_memory when calculate workload group mem_limit.
so a ratio is calculated to multiply the workload group mem_limit from the previous construction.
if all_workload_groups_mem_usage is greater than process_memory_usage, it means that the memory statistics of the workload group are inaccurate.
the reason is that query/load/etc. tracked is virtual memory, and virtual memory is not used in time.
At this time, weighted_memory_limit_ratio is equal to 1, and workload group mem_limit is still equal to (process_memory_limit * group_limit_percent), this may cause query spill to occur earlier,
However, there is no good solution at present, but we cannot predict when these virtual memory will be used.

run buildall

run buildall


support fetching containerd from non public GCS buckets

add support to fetch and download containerd tarball from GCS buckets that require authentication.

GCS_BUCKET_TOKEN should have read access to the bucket from which artifacts are to be fetched. The token is expected to be present in the instance metadata of the VM, similar to other node environment variables
Signed-off-by: Akhil Mohan<EMAIL_ADDRESS>To use this in tests from kubernetes, a new node env can be added as follows here. <your_gcs_bucket_token> can be fetched from a secret or from an env.
-node-env=GCS_BUCKET_TOKEN=<your_gcs_bucket_token>

/cc @estesp @samuelkarp

/cc @kzys


chore(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
8.9.0 -> 8.9.1

terraform-ibm-modules/key-protect/ibm (source)
module
patch
v2.8.0 -> v2.8.1

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.9.1
Compare Source
Bug Fixes

deps: update terraform time to latest for the deployable architecture solution (#682) (86cc006)

terraform-ibm-modules/terraform-ibm-key-protect (terraform-ibm-modules/key-protect/ibm)
v2.8.1
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cbr/ibm to v1.23.1 (#601) (3ad610f)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This issue has been resolved in version 1.23.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Remove internal functions of named colors from the public API

The following static methods are internal and became available in the public API by accident (as I understand it):

find_named_color;
get_named_color_count;
get_named_color_name;
get_named_color.

I suggest to hide them and add the get_named_colors method or other (if needed).

As @mhilbrunner brought in RocketChat:

#64830, what makes you think the named colors APIs were exposed by accident?

This is probably a piece of information that got lost as months have passed.
In my personal opinion, these methods are essentially useless to the average user, and overall they clutter the documentation. If necessary, it would be better to expose the named colors by returning a Dictionary of key/values from a single function instead of resorting on these four methods.

these methods are essentially useless to the average user. They return integers, indexes, and essentially clutter the documentation

fetching Colors by name can be so much simpler than all that (see Color.from_string())

Yes, I agree with this. I've added a detailed explanation to OP.

If there's need to, for example, count how many named colors there are, it would be better to expose these as a Dictionary of key/values returned from a single function

In the original version of this PR, I did it in a separate commit, but after recent changes, it's not building, so I removed it.

In my personal opinion, these methods are essentially useless to the average user. They return integers, indexes, and essentially clutter the documentation. They should simply not be encouraged, at all, because fetching Colors by name can be so much simpler than all that (see Color.from_string()).

I think the use case is iterating the list of named colors from e.g. a Editor extension or tool?
I agree exposing them as a dictionary makes more sense (and the same goes for a lot of similar places in the current API, where it has these kinds of "access/list by integer ID" APIs).
Personally, I'd be fine with the change to a dictionary, I'm also fine to remove these if we judge the use case too rare to bother, or if we do have evidence these got exposed by accident. As is, its a bit hard to judge for me.

I'd gladly contribute to the Dictionary idea before that time, to go hand-to-hand with this PR. Even if it's a "compatibility break" between versions, it's so unlikely users have even made use of these functions just yet, especially for the reasons stated above.

or if we do have evidence these got exposed by accident

I have no strong evidence that these methods were exposed by accident. Just a guess. These methods were exposed in #46378, which introduced the ability to bind static methods of Variant types.
In any case, the main argument is not the accident of adding these methods to the public API, but their uselessness there (IMO).

Thanks!


Editor should maybe have its own repo

I feel having the editor in this repo could clutter it a bit, it would probably be wise to give it its own repo.

Oh! It didn't look that cluttered to me :laughing:.  I'll quickly explain the level editor though. It's going to be a console based Java app that'll write out binary files for the patterns. It won't be something huge, just a convenience in development (so I don't have to write a bunch of hex).
I'll keep this open in case I change my mind (or you change it for me).


Request finalize v3

This is not ready yet and needs more testing.
The point of this PR is for libhtp to handle requests/responses ending and beginning in the middle of network provided chunks.
That is the added test case 97-requests-cut.t and 98
So htp_connp_REQ_FINALIZE probes a whole request line to say if we handle it as body or a new request, unless the connection is closed, in which case we complete the request.
Several test cases result change :

adding a line return to 91-request-unexpected-body.t so that the probing can restart at the new request
EmptyLineBetweenRequests : we do not have any longer tx->request_ignored_lines == 1 as the ignored line is now part of the previous request body
LongResponseHeader as the test framework directly returns on error before closing the connection, we do not make it to tx->request_progress == HTP_REQUEST_COMPLETE. Should we rather change the test framework ?
cf https://github.com/OISF/libhtp/blob/0.5.x/test/test.c#L357 versus https://github.com/OISF/libhtp/blob/0.5.x/test/test.c#L417

See https://redmine.openinfosecfoundation.org/issues/2655 for the latest changes to htp_connp_REQ_FINALIZE
Follows #270 by fixing same bug for responses and using HTTP/1.1 for real test case with pipelining

Does this address https://github.com/OISF/libhtp/pull/270#issuecomment-554326682 as well?

LongResponseHeader as the test framework directly returns on error before closing the connection, we do not make it to tx->request_progress == HTP_REQUEST_COMPLETE. Should we rather change the test framework ?
cf https://github.com/OISF/libhtp/blob/0.5.x/test/test.c#L357 versus https://github.com/OISF/libhtp/blob/0.5.x/test/test.c#L417

Not sure. Can you create a pcap based test (SV test) to see how this affects logging/matching in Suricata?


Style Issues (General)

Add "Beta" label to sidebar as well

For the subsection headings, should the title be of the form Web App Plugins: Reference, or is that redundant?

Completely 0/5, just wondering if someone lands on the page, is it obvious what reference they're looking at (until they check the sidebar, which may be more crowded once we add the other sections to the site)

I think the titles probably would be better off saying something like "Web App Plugins: Reference". At the very least, the tabs really need to say something more than "Reference":

Working on this now


Suggestion: allow loading browser stats form npm module

I'd like to suggest that there should be a way to express browser usage stats from a module.
It may be useful in case one wants to have the browser statistics shared across many projects.
In such case storing the stats JSON in project will not be enough.
How about allowing stats option to be a name of node module? main of that module would have to resolve to valid stats object (it may be json or JS)

Just use stats: "node_module/some-name/stats.json"


Update Application Owner

Description:

Implementing admin UI to change the OAuth application Owner of  an application to another user within the same tenant domain.

The feature is implemented [1].
[1] https://docs.wso2.com/display/AM260/Changing+the+Owner+of+an+Application


Get release 5 ready - Swift 4 support

Get release 5 ready and support Swift 4 💥
Related to #513

@gkye thanks, have fixed the wording.

🙈


Add requirement for CF deployment

What? and Why?

What does this pull request change/fix? Why was it necessary? Amend requirements for deployment to CF

Checklist

[ ] CHANGELOG.md updated? (if required)

Codecov Report

Merging #61 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #61   +/-   ##
=======================================
  Coverage   81.94%   81.94%
=======================================
  Files          12       12
  Lines         565      565
=======================================
  Hits          463      463
  Misses        102      102

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 4826050...6e4952c. Read the comment docs.


DSC not working for external database

Bug description
I am trying to create an artifact from a mocked database that s running locally on my machine but when I try to download the data through the connector I receive the code 417 as shown in the image:

I also tried with a resource from DWD and it works ok and can retrieve the data, I don't know what could be happening nor what the error I am getting means. I have correctly created on the provider side a complete offer (with an offer, catalog, rule, contract, artifact, and representation all linked together) and it shows the catalog in the self-description as expected.
I would like to know what the problem is and how to solve it. Let me know if you need any more information regarding this problem.
Screenshots & Logs
This is the artifact body post call that is working ok when I download the data:

This is the artifact body post call that is giving the code 417 once I try to download it:

Desktop (please complete the following information):

OS: Ubuntu 20.4
Browser Postman
Version (DSC) 6.2

What do the logs say when trying to access the backend URL (in debug mode)? When it works with a DWD resource, I assume that maybe the connection to your backend has some issues.

Hello.
I attach the log that is outputted in the terminal of the components. I haven't seen any documentation regarding any other type of logging. If there is, let me know that way I could send a complete log file.
Let me know if you need any more information
These are the logs when connecting with the DWD database which is working.
First connector (provider)

Second connector (consumer)

And these are the logs when trying to connect to my localhost database which isn't working.
First connector (provider)

Second connector (consumer)

Question:

Is the database deployed as a Docker container?
If yes, the database container-name has to be used as part of the accessUrl instead of <IP_ADDRESS> (localhost).
If the database is running locally outside of Docker, I personally can't help, because that would require access from a Container inside the Docker environment to access the DB on the local machine outside of the Docker environment. The resource from DWD for example is an external URL, which can be accessed.

it isn't, is a java server that i created hosted in the 9090 port on my machine

solved issue by launching the database out of the local host.


Add more status informations for ManagedCluster.Status

What would you like to be added:
Example:
status:
  allocatable:
    cpu: "8"
    memory: 15753Mi
  capacity:
    cpu: "8"
    memory: 15753Mi
  clusterCidr: <IP_ADDRESS>/24
  serviceCidr: <IP_ADDRESS>/24

Why is this needed:

wish report node numbers and status，like 5 node (1 failed)


refactor: fix imported package names shadowed in assignments

Description
This a modfied extract of changes suggested in https://github.com/aquasecurity/trivy-operator/pull/320 that fixes the cases where imported package names are shadowed in assignments. Ref. https://go-critic.com/overview#importShadow-ref. Also adding this rule to the lint configuration to avoid this problem from returning. Kudos to @JAORMX for the great suggestion!
Checklist

[x] I've read the guidelines for contributing to this repository.
[x] I've added tests that prove my fix is effective or that my feature works.
[ ] I've updated the documentation with the relevant information (if needed).
[ ] I've added usage information (if the PR introduces new options)
[ ] I've included a "before" and "after" example to the description (if the PR is a user interface change).

LGTM! I want to wait with this PR merge after we merge the #324


Choose rightsHolder

Who are the rights holders of this checklist? INBO as we are going to publish it? Or BE as BE is the project coordinator and responsible of the content?

I'm assuming we are gathering all the information, so it can be INBO.


"Sizes do not match" - Consider renaming to "Shapes do not match"

https://github.com/mateogianolio/vectorious/blob/354fc866b9c3b453a8000a96988e06934907eb9b/src/NDArray.ts#L104
It compares the shapes of the tensors, as well as the sizes.

Fixed in #132


Review CCR behaviour

There may be some performance optimization possible in this context, as every "group" of CCRs is paired with the main registry when querying, resulting in n queries against the main registry for n groups(?)

No longer required as CCS remote support is no longer on the table.
See #44


Design Review: Component - Badge

Component Name: Badge
Issue 1:

Description: Add a badge with icon variant

Steps to Reproduce: Check the available badge variants in Figma

Expected Result: A badge with icon variant included in StoryBook

Actual Result: A badge with icon variant is excluded in StoryBook

Screenshot of Expected Result:

Figma Reference Link:
https://www.figma.com/file/zPvPwPgb4EsYFXKC2nhzSG/Infineon-DDS-|-Main?type=design&node-id=23904%3A14546&mode=design&t=3no3fMzu06vmnQ6I-1

THANKS!

For version 2.


added test for useFetchDscStatus file

Closes: https://issues.redhat.com/browse/RHOAIENG-1877
Description
unit test for frontend/src/concepts/areas/useFetchDscStatus.ts

How Has This Been Tested?
npm run test

Test Impact
test coverage

Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/lgtm
/approve


Set log code when closing half open connections.

Since we now disallow half open connections for HTTP1/TLS we need
to set the log code when we close these connections so that
the 'crc' code is ERR_CLIENT_ABORT rather than ERR_UNKNOWN.
(cherry picked from commit 63ef107f927f94e5ae6e9c71e4c90fc082ea40c2)

This is a back-port of #4267 to branch 7.1.x.


how to assign values to change underlying data?

WARNING, the second test fails. I'm afraid I dont understand the strategy for updating a primitive variable using meta without explicitly casting, which is a problem for strongly typed enums unless we know the enum type ahead of time. (can't cast to int).
I do at least see the strategy for updating a member enum value using the meta_data.set()

Here I am. I think I don't get exactly this:

// ok so how do we update the meta handle
// with enum value (without expliclity using enum type casting)

Is your goal to modify directly a variable using the values for options registered through the meta type?
In this case, probably you can do that by means of a couple setter/getter, but I must admit I've never had this requirement and I'll think if there exists a shorter way.

ah your new test clarifies it for me. Thank you.
i may try extending the setter / getter to accept meta value as well.

Yeah. It's a bit convoluted but the fact is that meta types are all defined as if they were classes. Therefore we need to set a fake data member to set/get the value of a plain variable.
If you come up with a good idea to simplify it, I'd be glad to discuss it. :+1:


Quick Switcher is not working correctly

Describe the bug
After opening the Quick Switcher with CTRL+K, you are unable to select any choice from it with the arrow keys
Your discord client: [ e.g. Powercord ]
Powercord
Screenshots
If applicable, add screenshots to help explain your problem.

In this gif I tried using arrow keys, but they do nothing
Additional context
Pressing enter causes you to go to random(?) entry in the switcher

welp looks like another discord class change I was unaware of. I'll try to fix this within 24 hours!

So I just pushed an update but im on a different computer so i cant test if it actually worked or not, so lemme know if it worked after you try it 😂

So I just pushed an update but im on a different computer so i cant test if it actually worked or not, so lemme know if it worked after you try it 😂

it does! thanks!


wsei.txt

University of Economics and Innovation in Lublin

@JakubWaga Pull request merged. Thank you!

Thank you!
śr., 29 sie 2018 o 12:49 Philip Torchinsky<EMAIL_ADDRESS>napisał(a):

@JakubWaga https://github.com/JakubWaga Pull request merged. Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/5182#issuecomment-416909890, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ATP8fLozIQXdfgWE_HNhDDgBpmOCpNEkks5uVnGggaJpZM4WP5Q2
.


Precompilation is commented out

Is there a specific reason?
https://github.com/openjournals/joss-reviews/issues/5700

Yes, the precompilation takes too long and breaks the CI tests.
We added precompilation in this PR:
https://github.com/TensorBFS/TensorInference.jl/pull/26
And removed it in the following PR:
https://github.com/TensorBFS/TensorInference.jl/pull/48
The reasons to remove precompilation are discussed in the above issues. We will add it back when the precompilation time is acceptable.

this is non blocking for the review


Planning: fix bug in Hybrid a star

for case when node already visited in open set and with lower trajectory cost

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.wildblue seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Create user experience of logged in user

Write and submit a review for an item that includes:

A written text review
A score/rating

Only one review should be allowed per item, per user

View a list of all reviews I have written.

Delete reviews I have written.

Edit reviews I have written.

Change the text review.
Modify the score/rating.

Write comments on reviews written by others.

View a list of all comments I have written.

Edit and delete my comments.


Automatic color scheme based on theme (dark/light)

I use an app to automatically change the OS setting to dark/light mode depending on the time of the day. Using this with tools like edge is extremely comfortable because it reacts and changes it theme. At day I have a light edge, at night a dark edge.
In Terminal one can only change the window theme, but not the color scheme of the console.

Description of the new feature/enhancement
The window theme can switch according to the current system theme (dark/light). But the color scheme will always be the same.

I wish I could optionally set a color scheme per theme.
Example:
Light theme: One Half Light
Dark theme: Campbell

When I change the OS dark/light mode setting I want the color scheme in the terminal to change.

Hi, thanks for the suggestion. This is being tracked at #4066 . I'll close redirect the discussions to that thread.

thanks


Why all oozie workflow stored in the desktop_document2 table ??

Is the issue already present in https://github.com/cloudera/hue/issues or discussed in the forum https://discourse.gethue.com?
Describe the bug:
I used the AWS EMR HUE to create oozie workflow , the HUE version is 4.7.1,I found all metadata was saved in the table desktop_document2, why not save in oozie_workflow.
Steps to reproduce it?
Hue version or source? (e.g. open source 4.5, CDH 5.16, CDP 1.0...). System info (e.g. OS, Browser...).

All the apps shared the save tables, it is generic this way and enable easy reuse and functionalities.
Could you detail more what is your worry?


Unbreak autopushing docs

https://github.com/mapping-commons/sssom/runs/4407903105?check_suite_focus=true
For some reason build.yml does not work anymore - @hrshdhgd do you mind looking at that for a moment?

Maybe while you are at it, combine with https://github.com/mapping-commons/sssom/issues/115?

The build.yml works as expected now and highlighted the issues along the way.

The Pipfile and the Pipfile.lock are currently present in the make-venv directory.

Because of this, pipenv cannot see these two files when running within GitHub actions (locally as well for me) and hence creating new files (with none of the necessary packages listed). Thus the test was failing at Module not found: linkml_runtime
Solution: I copied the two files to the home directory and moved past this error to the next one
Question: Should we just move the 2 files to the home directory as opposed to having them within 'make-venv' directory?

ImportError: cannot import name 'Person' from 'sssom.sssom' (/home/runner/work/sssom/sssom/sssom/sssom.py)

This error arises from this line. There is no definition of the Person class in the project. How do I proceed?

cc @matentzn , @cmungall

@hrshdhgd has fixed this.


Increment installers

Anaconda3-2023.0
Miniconda3-py310_23.11.0-2
Mambaforge-23.11.0

I had an issue where I was getting conflicting SSL/Curl from some of the packages I was using and updating the base to new installers fixed it.

Thanks! Unfortunately, we need to ensure that all the installers use Python 3.10. I don't think that's the case for the added Anaconda version (see table). Can you double check with the others?

I've never used Anaconda, but looking through the list, it seems we'll have to just leave that installer alone. What's currently listed is the last python=3.10.
I have been testing the mambaforge one with success. If anyone else is able, please test with
!pip install -U https://github.com/hobu/condacolab/archive/0.1.x.tar.gz

Thanks!

Released in 0.1.9


A* routing bug

Fixed bug related to large number of turns, and incorrect routing. Added avoid_layers and distance.

it looks great Skandan


Strange loss values while training

I'm trying to perform faster rcnn on a custom dataset based on pascal voc format. I have set the number of iterations to 50000 and started the training on a gpu with 4GB memory. Now I have two problems:

the loss values don't seem to get close to a particular number and they change randomly without any order:

I don't know how to see if the network is over-fitting and if 50000 iterations are enough, low or even too much. How can I make sure how many iterations are appropriate?

the loss value seems fine, different images have different numbers.
you should use a separate validation set to test the model. if the model does not perform better after some iterations, then you are done.