(Logs) Logging for remaining parts

In this PR were added logging for remaining parts/RPC calls, which wasn't included in previous PRs with "(Logs)".
Sample output (initialization, state syncing, transaction submitting and batch/block building.
2024-01-31T08:58:22.107756Z  INFO store::setup: miden-store: store/src/db/mod.rs:50: Connecting to the database, config: { endpoint: "http://localhost:28943",  database_filepath: "miden-store.sqlite3", genesis_filepath: "genesis.dat" }
2024-01-31T08:58:22.107915Z  INFO store::setup: miden-store: store/src/db/mod.rs:84: Connected to the database, sqlite: "miden-store.sqlite3"
2024-01-31T08:58:22.136575Z  INFO store::setup:ensure_genesis_block: miden-store: store/src/db/mod.rs:256: new
2024-01-31T08:58:22.184967Z  INFO store::setup:ensure_genesis_block:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: new
2024-01-31T08:58:22.185749Z  INFO store::setup:ensure_genesis_block:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: close, time.busy: 189µs, time.idle: 594µs
2024-01-31T08:58:22.185903Z  INFO setup:ensure_genesis_block:writing genesis block to DB: miden-store: store/src/db/mod.rs:297: new
2024-01-31T08:58:22.186150Z  INFO setup:ensure_genesis_block:writing genesis block to DB: miden-store: store/src/db/mod.rs:297: close, time.busy: 218µs, time.idle: 32.3µs
2024-01-31T08:58:22.186207Z  INFO store::setup:ensure_genesis_block: miden-store: store/src/db/mod.rs:256: close, time.busy: 48.7ms, time.idle: 913µs
2024-01-31T08:58:22.186229Z  INFO store::setup: miden-store: store/src/db/mod.rs:48: close, time.busy: 49.5ms, time.idle: 29.1ms
2024-01-31T08:58:22.186455Z  INFO store: miden-store: store/src/server/mod.rs:15: new
2024-01-31T08:58:22.195009Z  INFO store: miden-store: store/src/server/mod.rs:20: Initializing server, config: { endpoint: "http://localhost:28943",  database_filepath: "miden-store.sqlite3", genesis_filepath: "genesis.dat" }
2024-01-31T08:58:22.195053Z  INFO store:load: miden-store: store/src/state.rs:178: new
2024-01-31T08:58:22.195070Z  INFO store:load:load_nullifier_tree: miden-store: store/src/state.rs:577: new
2024-01-31T08:58:22.195086Z  INFO store:load:load_nullifier_tree:select_nullifiers: miden-store: store/src/db/mod.rs:105: new
2024-01-31T08:58:22.195261Z  INFO store:load:load_nullifier_tree:select_nullifiers: miden-store: store/src/db/mod.rs:105: close, time.busy: 38.5µs, time.idle: 136µs
2024-01-31T08:58:22.195719Z  INFO store:load:load_nullifier_tree: miden_node_store::state: store/src/state.rs:589: Loaded nullifier tree, num_of_leaves: 0, tree_construction: 0, COMPONENT: "miden-store"
2024-01-31T08:58:22.195759Z  INFO store:load:load_nullifier_tree: miden-store: store/src/state.rs:577: close, time.busy: 561µs, time.idle: 127µs
2024-01-31T08:58:22.195785Z  INFO store:load:load_mmr: miden-store: store/src/state.rs:598: new
2024-01-31T08:58:22.195802Z  INFO store:load:load_mmr:select_block_headers: miden-store: store/src/db/mod.rs:158: new
2024-01-31T08:58:22.196713Z  INFO store:load:load_mmr:select_block_headers: miden-store: store/src/db/mod.rs:158: close, time.busy: 46.1µs, time.idle: 864µs
2024-01-31T08:58:22.197452Z  INFO store:load:load_mmr: miden-store: store/src/state.rs:598: close, time.busy: 1.48ms, time.idle: 191µs
2024-01-31T08:58:22.197474Z  INFO store:load:load_accounts: miden-store: store/src/state.rs:611: new
2024-01-31T08:58:22.197491Z  INFO store:load:load_accounts:select_account_hashes: miden-store: store/src/db/mod.rs:172: new
2024-01-31T08:58:22.197607Z  INFO store:load:load_accounts:select_account_hashes: miden-store: store/src/db/mod.rs:172: close, time.busy: 24.3µs, time.idle: 91.7µs
2024-01-31T08:58:22.212719Z  INFO store:load:load_accounts: miden-store: store/src/state.rs:611: close, time.busy: 15.2ms, time.idle: 87.4µs
2024-01-31T08:58:22.212748Z  INFO store:load: miden-store: store/src/state.rs:178: close, time.busy: 17.3ms, time.idle: 359µs
2024-01-31T08:58:22.212785Z  INFO store: miden-store: store/src/server/mod.rs:25: Server initialized
2024-01-31T08:58:23.189201Z  INFO block_producer: miden-block-producer: block-producer/src/server/mod.rs:26: new
2024-01-31T08:58:23.189460Z  INFO block_producer: miden-block-producer: block-producer/src/server/mod.rs:28: Initializing server, config: { endpoint: "http://localhost:48046", store_url: "http://localhost:28943" }
2024-01-31T08:58:23.222755Z  INFO block_producer:Parsing program: miden_assembly::ast::program: /Users/polydez/.cargo/git/checkouts/miden-vm-3db6be6805d1979c/bd10b8c/assembly/src/ast/program.rs:126: new
2024-01-31T08:58:23.223590Z  INFO block_producer:Parsing program: miden_assembly::ast::program: /Users/polydez/.cargo/git/checkouts/miden-vm-3db6be6805d1979c/bd10b8c/assembly/src/ast/program.rs:126: close, time.busy: 750µs, time.idle: 98.0µs
2024-01-31T08:58:23.223653Z  INFO block_producer:Compile AST: miden_assembly::assembler: /Users/polydez/.cargo/git/checkouts/miden-vm-3db6be6805d1979c/bd10b8c/assembly/src/assembler/mod.rs:144: new
2024-01-31T08:58:23.256645Z  INFO block_producer:Compile AST: miden_assembly::assembler: /Users/polydez/.cargo/git/checkouts/miden-vm-3db6be6805d1979c/bd10b8c/assembly/src/assembler/mod.rs:144: close, time.busy: 33.0ms, time.idle: 32.8µs
2024-01-31T08:58:23.257161Z  INFO block_producer:batch_builder: miden-block-producer: block-producer/src/server/mod.rs:59: new
2024-01-31T08:58:23.257187Z  INFO block_producer: miden-block-producer: block-producer/src/server/mod.rs:62: Server initialized
2024-01-31T08:58:23.257260Z  INFO block_producer: miden-block-producer: block-producer/src/txqueue/mod.rs:140: new
2024-01-31T08:58:23.257303Z  INFO block_producer: miden-block-producer: block-producer/src/txqueue/mod.rs:144: Transaction queue started, period_ms: 2000
2024-01-31T08:58:23.257742Z  INFO block_producer:batch_builder: miden-block-producer: block-producer/src/batch_builder/mod.rs:86: Batch builder started, period_ms: 10000
2024-01-31T08:58:23.258533Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: new
2024-01-31T08:58:23.275021Z  INFO block_producer:batch_builder:try_build_block: miden-block-producer: block-producer/src/batch_builder/mod.rs:99: new
2024-01-31T08:58:23.275022Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: close, time.busy: 14.2µs, time.idle: 16.5ms
2024-01-31T08:58:23.275060Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:72: new
2024-01-31T08:58:23.275636Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:77: num_batches: 0, batches: None
2024-01-31T08:58:23.276794Z  INFO store:get_block_inputs: miden-store: store/src/server/api.rs:179: new
2024-01-31T08:58:23.276833Z  INFO store:get_block_inputs:validate_nullifiers: miden-store: store/src/server/api.rs:315: new
2024-01-31T08:58:23.276862Z  INFO store:get_block_inputs:validate_nullifiers: miden-store: store/src/server/api.rs:315: close, time.busy: 14.8µs, time.idle: 14.1µs
2024-01-31T08:58:23.276887Z  INFO store:get_block_inputs:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: new
2024-01-31T08:58:23.277188Z  INFO store:get_block_inputs:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: close, time.busy: 62.8µs, time.idle: 234µs
2024-01-31T08:58:23.277236Z  INFO store:get_block_inputs: miden-store: store/src/server/api.rs:179: close, time.busy: 211µs, time.idle: 232µs
2024-01-31T08:58:23.282019Z  INFO block_producer:batch_builder:try_build_block:build_block:Executing program: miden_processor: /Users/polydez/.cargo/git/checkouts/miden-vm-3db6be6805d1979c/bd10b8c/processor/src/lib.rs:119: new
2024-01-31T08:58:23.296313Z  INFO block_producer:batch_builder:try_build_block:build_block:Executing program: miden_processor: /Users/polydez/.cargo/git/checkouts/miden-vm-3db6be6805d1979c/bd10b8c/processor/src/lib.rs:119: close, time.busy: 14.3ms, time.idle: 35.0µs
2024-01-31T08:58:23.297004Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:119: block is built, block_num: 1, block_hash: 0xee39466854d565cbde65ddd7d5eeb4d6e352b44bd2e205438b4ce1b7be4568d6
2024-01-31T08:58:23.297037Z  INFO block_producer:batch_builder:try_build_block:build_block:apply_block: miden-block-producer: block-producer/src/state_view/mod.rs:102: new
2024-01-31T08:58:23.297062Z  INFO block_producer:batch_builder:try_build_block:build_block:apply_block:apply_block: miden-block-producer: block-producer/src/store/mod.rs:92: new
2024-01-31T08:58:23.297677Z  INFO store:apply_block: miden-store: store/src/server/api.rs:131: new
2024-01-31T08:58:23.298315Z  INFO store:apply_block: miden-store: store/src/server/api.rs:151: Apply block, block_hash: 0xee39466854d565cbde65ddd7d5eeb4d6e352b44bd2e205438b4ce1b7be4568d6
2024-01-31T08:58:23.298344Z  INFO store:apply_block:validate_nullifiers: miden-store: store/src/server/api.rs:315: new
2024-01-31T08:58:23.298364Z  INFO store:apply_block:validate_nullifiers: miden-store: store/src/server/api.rs:315: close, time.busy: 5.17µs, time.idle: 14.5µs
2024-01-31T08:58:23.298401Z  INFO store:apply_block:db:apply_block: miden-store: store/src/state.rs:214: new
2024-01-31T08:58:23.299032Z  INFO store:apply_block:db:apply_block:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: new
2024-01-31T08:58:23.299258Z  INFO store:apply_block:db:apply_block:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: close, time.busy: 50.6µs, time.idle: 175µs
2024-01-31T08:58:23.299882Z  INFO store:apply_block:db:apply_block:updating in-memory data structures: miden-store: store/src/state.rs:246: new
2024-01-31T08:58:23.319048Z  INFO store:apply_block:db:apply_block:updating in-memory data structures:build_notes_tree: miden-store: store/src/state.rs:558: new
2024-01-31T08:58:23.319081Z  INFO store:apply_block:db:apply_block:updating in-memory data structures:build_notes_tree: miden-store: store/src/state.rs:558: close, time.busy: 7.83µs, time.idle: 29.2µs
2024-01-31T08:58:23.319105Z  INFO store:apply_block:db:apply_block:updating in-memory data structures: miden-store: store/src/state.rs:246: close, time.busy: 1.22ms, time.idle: 18.0ms
2024-01-31T08:58:23.319168Z  INFO store:db:apply_block: miden-store: store/src/db/mod.rs:216: new
2024-01-31T08:58:23.319276Z  INFO store:db:apply_block:Writing new block data to database: miden-store: store/src/db/mod.rs:231: new
2024-01-31T08:58:23.319409Z  INFO store:apply_block:db:apply_block: miden-store: store/src/state.rs:214: close, time.busy: 20.6ms, time.idle: 403µs
2024-01-31T08:58:23.319432Z  INFO store:apply_block: miden-store: store/src/server/api.rs:131: close, time.busy: 21.4ms, time.idle: 403µs
2024-01-31T08:58:23.319449Z  INFO store:db:apply_block:Writing new block data to database: miden-store: store/src/db/mod.rs:231: close, time.busy: 160µs, time.idle: 13.2µs
2024-01-31T08:58:23.319616Z  INFO store:db:apply_block: miden-store: store/src/db/mod.rs:216: close, time.busy: 42.7µs, time.idle: 406µs
2024-01-31T08:58:23.320058Z  INFO block_producer:batch_builder:try_build_block:build_block:apply_block:apply_block: miden-block-producer: block-producer/src/store/mod.rs:92: close, time.busy: 164µs, time.idle: 22.8ms
2024-01-31T08:58:23.320111Z  INFO block_producer:batch_builder:try_build_block:build_block:apply_block: miden-block-producer: block-producer/src/state_view/mod.rs:102: close, time.busy: 235µs, time.idle: 22.8ms
2024-01-31T08:58:23.338706Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:124: block is applied!, block_num: 1, block_hash: 0xee39466854d565cbde65ddd7d5eeb4d6e352b44bd2e205438b4ce1b7be4568d6
2024-01-31T08:58:23.338758Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:72: close, time.busy: 38.5ms, time.idle: 25.2ms
2024-01-31T08:58:23.338782Z  INFO block_producer:batch_builder:try_build_block: miden-block-producer: block-producer/src/batch_builder/mod.rs:99: close, time.busy: 39.1ms, time.idle: 24.7ms
2024-01-31T08:58:24.191393Z  INFO rpc: miden-rpc: rpc/src/server/mod.rs:14: new
2024-01-31T08:58:24.191616Z  INFO rpc: miden-rpc: rpc/src/server/mod.rs:16: Initializing server, config: { endpoint: "http://localhost:57291", store_url: "http://localhost:28943", block_producer_url: "http://localhost:48046" }
2024-01-31T08:58:24.194890Z  INFO rpc: miden-rpc: rpc/src/server/api.rs:35: Store client initialized, store_endpoint: "http://localhost:28943"
2024-01-31T08:58:24.197459Z  INFO rpc: miden-rpc: rpc/src/server/api.rs:39: Block producer client initialized, block_producer_endpoint: "http://localhost:48046"
2024-01-31T08:58:24.197562Z  INFO rpc: miden-rpc: rpc/src/server/mod.rs:21: Server initialized
2024-01-31T08:58:25.259067Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: new
2024-01-31T08:58:25.259322Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: close, time.busy: 57.6µs, time.idle: 237µs
2024-01-31T08:58:27.259264Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: new
2024-01-31T08:58:27.259586Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: close, time.busy: 72.5µs, time.idle: 290µs
2024-01-31T08:58:28.708203Z  INFO rpc:get_block_header_by_number: miden-rpc: rpc/src/server/api.rs:79: new
2024-01-31T08:58:28.708277Z  INFO rpc:get_block_header_by_number: miden-rpc: rpc/src/server/api.rs:90: request: GetBlockHeaderByNumberRequest { block_num: Some(0) }
2024-01-31T08:58:28.709315Z  INFO store:get_block_header_by_number: miden-store: store/src/server/api.rs:44: new
2024-01-31T08:58:28.709394Z  INFO store:get_block_header_by_number: miden-store: store/src/server/api.rs:55: request: Request { metadata: MetadataMap { headers: {"te": "trailers", "content-type": "application/grpc", "user-agent": "tonic/0.10.2"} }, message: GetBlockHeaderByNumberRequest { block_num: Some(0) }, extensions: Extensions }
2024-01-31T08:58:28.709491Z  INFO store:get_block_header_by_number:get_block_header: miden-store: store/src/state.rs:369: new
2024-01-31T08:58:28.709550Z  INFO store:get_block_header_by_number:get_block_header:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: new
2024-01-31T08:58:28.710219Z  INFO store:get_block_header_by_number:get_block_header:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: close, time.busy: 110µs, time.idle: 558µs
2024-01-31T08:58:28.710303Z  INFO store:get_block_header_by_number:get_block_header: miden-store: store/src/state.rs:369: close, time.busy: 279µs, time.idle: 534µs
2024-01-31T08:58:28.710368Z  INFO store:get_block_header_by_number: miden-store: store/src/server/api.rs:44: close, time.busy: 538µs, time.idle: 518µs
2024-01-31T08:58:28.711583Z  INFO rpc:get_block_header_by_number: miden-rpc: rpc/src/server/api.rs:79: close, time.busy: 308µs, time.idle: 3.08ms
2024-01-31T08:58:28.715267Z  INFO rpc:sync_state: miden-rpc: rpc/src/server/api.rs:96: new
2024-01-31T08:58:28.716303Z  INFO store:sync_state: miden-store: store/src/server/api.rs:95: new
2024-01-31T08:58:28.716387Z  INFO store:sync_state:sync_state: miden-store: store/src/state.rs:407: new
2024-01-31T08:58:28.716448Z  INFO store:sync_state:sync_state:get_state_sync: miden-store: store/src/db/mod.rs:183: new
2024-01-31T08:58:28.717781Z  INFO store:sync_state:sync_state:get_state_sync: miden-store: store/src/db/mod.rs:183: close, time.busy: 96.0µs, time.idle: 1.23ms
2024-01-31T08:58:28.717903Z  INFO store:sync_state:sync_state: miden-store: store/src/state.rs:407: close, time.busy: 308µs, time.idle: 1.21ms
2024-01-31T08:58:28.718001Z  INFO store:sync_state: miden-store: store/src/server/api.rs:95: close, time.busy: 530µs, time.idle: 1.17ms
2024-01-31T08:58:28.719495Z  INFO rpc:sync_state: miden-rpc: rpc/src/server/api.rs:96: close, time.busy: 270µs, time.idle: 3.96ms
2024-01-31T08:58:29.258989Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: new
2024-01-31T08:58:29.259182Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: close, time.busy: 38.8µs, time.idle: 168µs
2024-01-31T08:58:31.257645Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: new
2024-01-31T08:58:31.257756Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: close, time.busy: 25.6µs, time.idle: 96.5µs
2024-01-31T08:58:33.072481Z  INFO rpc:submit_proven_transaction: miden-rpc: rpc/src/server/api.rs:113: new
2024-01-31T08:58:33.075721Z  INFO block_producer:submit_proven_transaction: miden-block-producer: block-producer/src/server/api.rs:40: new
2024-01-31T08:58:33.080405Z  INFO block_producer:submit_proven_transaction: miden-block-producer: block-producer/src/server/api.rs:56: Deserialized transaction, tx_id: 0xebe903a7ea87df2eb623d794bb43b742ebf2dfbab72bd0e5ae71b814dcd0c8ca, account_id: 0x8a03f7789eb6df12, initial_account_hash: 0xcb66038507b40a94b53f49b0aeb0de3c4c2dcd8b320311a286b68063dfe171e1, final_account_hash: 0x2098c2d38d282f8811e63cc80bdf9c69bae5df7fd9d307c660248be7c0dd4173, input_notes: None, output_notes: [{ note_id: 0xa7ae0d40a24be19be2eb0e60976699c1280e6b1a463bec1879f8e8630175634f, note_metadata: {sender: 0x8a03f7789eb6df12, tag:<PHONE_NUMBER>604656842 }}], tx_script_root: 0x201f5f4313a4107490fb6ae5b755cbd84206190bb4886e78e556e5292d259260, block_ref: 0xee39466854d565cbde65ddd7d5eeb4d6e352b44bd2e205438b4ce1b7be4568d6
2024-01-31T08:58:33.080637Z  INFO block_producer:submit_proven_transaction:add_transaction: miden-block-producer: block-producer/src/txqueue/mod.rs:193: new
2024-01-31T08:58:33.080738Z  INFO block_producer:submit_proven_transaction:add_transaction: miden-block-producer: block-producer/src/txqueue/mod.rs:198: tx_id: 0xebe903a7ea87df2eb623d794bb43b742ebf2dfbab72bd0e5ae71b814dcd0c8ca, account_id: 0x8a03f7789eb6df12
2024-01-31T08:58:33.080838Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx: miden_node_block_producer::state_view: block-producer/src/state_view/mod.rs:50: new
2024-01-31T08:58:33.080955Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx:ensure_in_flight_constraints: miden-block-producer: block-producer/src/state_view/mod.rs:141: new
2024-01-31T08:58:33.083205Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx:ensure_in_flight_constraints: miden-block-producer: block-producer/src/state_view/mod.rs:141: close, time.busy: 14.0µs, time.idle: 2.24ms
2024-01-31T08:58:33.083313Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx:get_tx_inputs: miden-block-producer: block-producer/src/store/mod.rs:118: new
2024-01-31T08:58:33.083398Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx:get_tx_inputs: miden-block-producer: block-producer/src/store/mod.rs:132: tx_id: 0xebe903a7ea87df2eb623d794bb43b742ebf2dfbab72bd0e5ae71b814dcd0c8ca
2024-01-31T08:58:33.087096Z  INFO store:get_transaction_inputs: miden-store: store/src/server/api.rs:211: new
2024-01-31T08:58:33.087197Z  INFO store:get_transaction_inputs:validate_nullifiers: miden-store: store/src/server/api.rs:315: new
2024-01-31T08:58:33.087267Z  INFO store:get_transaction_inputs:validate_nullifiers: miden-store: store/src/server/api.rs:315: close, time.busy: 11.2µs, time.idle: 59.9µs
2024-01-31T08:58:33.087359Z  INFO store:get_transaction_inputs:get_transaction_inputs: miden-store: store/src/state.rs:493: new
2024-01-31T08:58:33.087420Z  INFO store:get_transaction_inputs:get_transaction_inputs: miden-store: store/src/state.rs:499: account_id: 0x8a03f7789eb6df12, nullifiers: None
2024-01-31T08:58:33.088963Z  INFO store:get_transaction_inputs:get_transaction_inputs: miden-store: store/src/state.rs:493: return: ({ account_id: 0x8a03f7789eb6df12, account_hash: 0xcb66038507b40a94b53f49b0aeb0de3c4c2dcd8b320311a286b68063dfe171e1 }, [])
2024-01-31T08:58:33.089064Z  INFO store:get_transaction_inputs:get_transaction_inputs: miden-store: store/src/state.rs:493: close, time.busy: 1.64ms, time.idle: 64.7µs
2024-01-31T08:58:33.089157Z  INFO store:get_transaction_inputs: miden-store: store/src/server/api.rs:211: close, time.busy: 1.98ms, time.idle: 90.7µs
2024-01-31T08:58:33.092364Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx:get_tx_inputs: miden-block-producer: block-producer/src/store/mod.rs:118: close, time.busy: 2.78ms, time.idle: 6.26ms
2024-01-31T08:58:33.092468Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx:ensure_tx_inputs_constraints: miden-block-producer: block-producer/src/state_view/mod.rs:175: new
2024-01-31T08:58:33.092537Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx:ensure_tx_inputs_constraints: miden-block-producer: block-producer/src/state_view/mod.rs:175: close, time.busy: 13.4µs, time.idle: 56.0µs
2024-01-31T08:58:33.093726Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx:ensure_in_flight_constraints: miden-block-producer: block-producer/src/state_view/mod.rs:141: new
2024-01-31T08:58:33.093788Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx:ensure_in_flight_constraints: miden-block-producer: block-producer/src/state_view/mod.rs:141: close, time.busy: 7.58µs, time.idle: 54.8µs
2024-01-31T08:58:33.093956Z  INFO block_producer:submit_proven_transaction:add_transaction:verify_tx: miden_node_block_producer::state_view: block-producer/src/state_view/mod.rs:50: close, time.busy: 6.83ms, time.idle: 6.29ms
2024-01-31T08:58:33.094020Z  INFO block_producer:submit_proven_transaction:add_transaction: miden-block-producer: block-producer/src/txqueue/mod.rs:211: Transaction added to tx queue, queue_len: 1
2024-01-31T08:58:33.095934Z  INFO block_producer:submit_proven_transaction:add_transaction: miden-block-producer: block-producer/src/txqueue/mod.rs:193: close, time.busy: 9.03ms, time.idle: 6.27ms
2024-01-31T08:58:33.096000Z  INFO block_producer:submit_proven_transaction: miden-block-producer: block-producer/src/server/api.rs:40: close, time.busy: 14.0ms, time.idle: 6.27ms
2024-01-31T08:58:33.097013Z  INFO rpc:submit_proven_transaction: miden-rpc: rpc/src/server/api.rs:113: close, time.busy: 283µs, time.idle: 24.3ms
2024-01-31T08:58:33.258346Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: new
2024-01-31T08:58:33.258395Z  INFO block_producer:try_build_batches:batch_builder: miden-block-producer: block-producer/src/txqueue/mod.rs:183: new
2024-01-31T08:58:33.258445Z  INFO block_producer:try_build_batches:batch_builder:build_batch: miden-block-producer: block-producer/src/batch_builder/mod.rs:128: new
2024-01-31T08:58:33.258462Z  INFO block_producer:try_build_batches:batch_builder:build_batch: miden-block-producer: block-producer/src/batch_builder/mod.rs:135: Building a transaction batch, num_txs: 1
2024-01-31T08:58:33.258481Z  INFO block_producer:try_build_batches:batch_builder:build_batch:new_batch: miden-block-producer: block-producer/src/batch_builder/batch.rs:41: new
2024-01-31T08:58:33.261720Z  INFO block_producer:try_build_batches:batch_builder:build_batch:new_batch: miden-block-producer: block-producer/src/batch_builder/batch.rs:41: close, time.busy: 3.22ms, time.idle: 15.8µs
2024-01-31T08:58:33.261748Z  INFO block_producer:try_build_batches:batch_builder:build_batch: miden-block-producer: block-producer/src/batch_builder/mod.rs:140: Transaction batch built
2024-01-31T08:58:33.261781Z  INFO block_producer:try_build_batches:batch_builder:build_batch: miden-block-producer: block-producer/src/batch_builder/mod.rs:149: Transaction batch added to the batch queue, num_batches: 1 batch_id: "0x48a0d3e2c925dacad5dc2a6824682b78acd5bbd545250a0a1c239e9ff8eeb999"
2024-01-31T08:58:33.261800Z  INFO block_producer:try_build_batches:batch_builder:build_batch: miden-block-producer: block-producer/src/batch_builder/mod.rs:128: close, time.busy: 3.34ms, time.idle: 17.6µs batch_id: "0x48a0d3e2c925dacad5dc2a6824682b78acd5bbd545250a0a1c239e9ff8eeb999"
2024-01-31T08:58:33.262034Z  INFO block_producer:try_build_batches:batch_builder: miden-block-producer: block-producer/src/txqueue/mod.rs:183: close, time.busy: 3.59ms, time.idle: 44.5µs
2024-01-31T08:58:33.262047Z  INFO block_producer:try_build_batches: miden-block-producer: block-producer/src/txqueue/mod.rs:153: close, time.busy: 47.7µs, time.idle: 3.66ms
2024-01-31T08:58:33.262105Z  INFO block_producer:batch_builder:try_build_block: miden-block-producer: block-producer/src/batch_builder/mod.rs:99: new
2024-01-31T08:58:33.262126Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:72: new
2024-01-31T08:58:33.262735Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:77: num_batches: 1, batches: [0x48a0d3e2c925dacad5dc2a6824682b78acd5bbd545250a0a1c239e9ff8eeb999]
2024-01-31T08:58:33.263309Z  INFO store:get_block_inputs: miden-store: store/src/server/api.rs:179: new
2024-01-31T08:58:33.263329Z  INFO store:get_block_inputs:validate_nullifiers: miden-store: store/src/server/api.rs:315: new
2024-01-31T08:58:33.263344Z  INFO store:get_block_inputs:validate_nullifiers: miden-store: store/src/server/api.rs:315: close, time.busy: 3.46µs, time.idle: 11.5µs
2024-01-31T08:58:33.263397Z  INFO store:get_block_inputs:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: new
2024-01-31T08:58:33.263573Z  INFO store:get_block_inputs:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: close, time.busy: 48.0µs, time.idle: 129µs
2024-01-31T08:58:33.263644Z  INFO store:get_block_inputs: miden-store: store/src/server/api.rs:179: close, time.busy: 210µs, time.idle: 125µs
2024-01-31T08:58:33.283966Z  INFO block_producer:batch_builder:try_build_block:build_block:Executing program: miden_processor: /Users/polydez/.cargo/git/checkouts/miden-vm-3db6be6805d1979c/bd10b8c/processor/src/lib.rs:119: new
2024-01-31T08:58:33.334548Z  INFO block_producer:batch_builder:try_build_block:build_block:Executing program: miden_processor: /Users/polydez/.cargo/git/checkouts/miden-vm-3db6be6805d1979c/bd10b8c/processor/src/lib.rs:119: close, time.busy: 50.5ms, time.idle: 57.0µs
2024-01-31T08:58:33.335236Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:119: block is built, block_num: 2, block_hash: 0x28f9d90291b954942d1d93e6f7e0fdecba075870df63aa26b8d3469f7e505a11
2024-01-31T08:58:33.335271Z  INFO block_producer:batch_builder:try_build_block:build_block:apply_block: miden-block-producer: block-producer/src/state_view/mod.rs:102: new
2024-01-31T08:58:33.335300Z  INFO block_producer:batch_builder:try_build_block:build_block:apply_block:apply_block: miden-block-producer: block-producer/src/store/mod.rs:92: new
2024-01-31T08:58:33.335904Z  INFO store:apply_block: miden-store: store/src/server/api.rs:131: new
2024-01-31T08:58:33.336509Z  INFO store:apply_block: miden-store: store/src/server/api.rs:151: Apply block, block_hash: 0x28f9d90291b954942d1d93e6f7e0fdecba075870df63aa26b8d3469f7e505a11
2024-01-31T08:58:33.336527Z  INFO store:apply_block:validate_nullifiers: miden-store: store/src/server/api.rs:315: new
2024-01-31T08:58:33.336543Z  INFO store:apply_block:validate_nullifiers: miden-store: store/src/server/api.rs:315: close, time.busy: 4.08µs, time.idle: 11.7µs
2024-01-31T08:58:33.336565Z  INFO store:apply_block:db:apply_block: miden-store: store/src/state.rs:214: new
2024-01-31T08:58:33.337166Z  INFO store:apply_block:db:apply_block:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: new
2024-01-31T08:58:33.337383Z  INFO store:apply_block:db:apply_block:select_block_header_by_block_num: miden-store: store/src/db/mod.rs:143: close, time.busy: 46.5µs, time.idle: 170µs
2024-01-31T08:58:33.338001Z  INFO store:apply_block:db:apply_block:updating in-memory data structures: miden-store: store/src/state.rs:246: new
2024-01-31T08:58:33.346496Z  INFO store:apply_block:db:apply_block:updating in-memory data structures:build_notes_tree: miden-store: store/src/state.rs:558: new
2024-01-31T08:58:33.351499Z  INFO store:apply_block:db:apply_block:updating in-memory data structures:build_notes_tree: miden-store: store/src/state.rs:558: close, time.busy: 4.98ms, time.idle: 27.2µs
2024-01-31T08:58:33.351527Z  INFO store:apply_block:db:apply_block:updating in-memory data structures: miden-store: store/src/state.rs:246: close, time.busy: 13.5ms, time.idle: 17.0µs
2024-01-31T08:58:33.351606Z  INFO store:db:apply_block: miden-store: store/src/db/mod.rs:216: new
2024-01-31T08:58:33.351714Z  INFO store:db:apply_block:Writing new block data to database: miden-store: store/src/db/mod.rs:231: new
2024-01-31T08:58:33.351879Z  INFO store:apply_block:db:apply_block: miden-store: store/src/state.rs:214: close, time.busy: 14.9ms, time.idle: 429µs
2024-01-31T08:58:33.351946Z  INFO store:db:apply_block:Writing new block data to database: miden-store: store/src/db/mod.rs:231: close, time.busy: 216µs, time.idle: 16.3µs
2024-01-31T08:58:33.362043Z  INFO store:apply_block: miden-store: store/src/server/api.rs:131: close, time.busy: 25.7ms, time.idle: 422µs
2024-01-31T08:58:33.362083Z  INFO store:db:apply_block: miden-store: store/src/db/mod.rs:216: close, time.busy: 44.4µs, time.idle: 10.4ms
2024-01-31T08:58:33.362502Z  INFO block_producer:batch_builder:try_build_block:build_block:apply_block:apply_block: miden-block-producer: block-producer/src/store/mod.rs:92: close, time.busy: 148µs, time.idle: 27.1ms
2024-01-31T08:58:33.362759Z  INFO block_producer:batch_builder:try_build_block:build_block:apply_block: miden-block-producer: block-producer/src/state_view/mod.rs:102: close, time.busy: 422µs, time.idle: 27.1ms
2024-01-31T08:58:33.362779Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:124: block is applied!, block_num: 2, block_hash: 0x28f9d90291b954942d1d93e6f7e0fdecba075870df63aa26b8d3469f7e505a11
2024-01-31T08:58:33.362808Z  INFO block_producer:batch_builder:try_build_block:build_block: miden-block-producer: block-producer/src/block_builder/mod.rs:72: close, time.busy: 72.0ms, time.idle: 28.6ms
2024-01-31T08:58:33.363421Z  INFO block_producer:batch_builder:try_build_block: miden-block-producer: block-producer/src/batch_builder/mod.rs:99: close, time.busy: 73.3ms, time.idle: 28.1ms

All changes were merged to #190


Portainer CE - unable to contact any other agent

Bug description
Portainer CE service frequently fails with this error
"The agent was unable to contact any other agent located on a manager node".
Portainer CE stack is deployed in a docker swarm cluster with 3 manager roles and 7 workers. Portainer service is pinned to one of the managers.
During the day, agent randomly fail with the message mentioned above. Other services deployed in the cluster are working without issues during this period. Only way to fix it, is to restart the agent service (deployed as a global service).
Expected behavior
Working Portainer CE stack.
Portainer Logs
2023-01-16T16:38:33.086908239Z portainer.1.tp9ci4ar8ypm@sha-swarm-node-02    |
time="2023-01-16T16:38:33Z" level=info msg="2023/01/16 16:38:33 http error: time=\"2023-01-16T16:38:32Z\"
level=warning msg=\"network default: network.external.name is deprecated in favor of network.name\""

2023-01-16T16:38:33.087113644Z portainer.1.tp9ci4ar8ypm@sha-swarm-node-02    |
time="2023-01-16T16:38:33Z" level=info msg="Error response from daemon:
The agent was unable to contact any other agent located on a manager node"

2023-01-16T23:50:41.869870394Z portainer_agent.0.o6ddo0ezwdcr@sha-swarm-node-03    |
2023/01/16 23:50:41 [INFO] memberlist: Suspect sha-swarm-node-06-5d7a50666e66 has failed, no acks received

Steps to reproduce the issue:
None, happens occasionally.
Technical details:

Portainer version: 2.15.1 CE
Docker version (managed by Portainer): 20.10.8
Platform (windows/linux): Ubuntu 20.01.3 LTS with HWE
Command used to start Portainer: compose file (stack)
Use Case (delete as appropriate): Using Portainer in a Commercial setup.
Have you reviewed our technical documentation and knowledge base? Yes

@jansumsky
This may be related in regards to the agent service update:  https://github.com/portainer/portainer/issues/8256
I am uncertain why your Manager and Worker nodes are having networking connectivity issues.  Have you investigated those further?  Does your overlay have an overlay of 1550?
Thanks!

Related:  https://github.com/portainer/portainer/issues/8256


Can't use with unstable_enablePackageExports metro option (expo)

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
When using @supabase/supabase-js in an expo react native project, if I use the unstable_enablePackageExports with the metro bundler, bundling fails with the following error:
To Reproduce

Generate a new expo app
Add @supabase/supabase-js as a dependency
Create a supabase client in the main _layout.tsx file
Run npx expo customize metro.config.js
Add config.resolver.unstable_enablePackageExports = true; to metro.config.js
Add ios.bundleIdentifier to app.json
Run npx expo run:ios

Repro repo: https://github.com/aldebout/supabase-expo-exports-issue
Expected behavior
No crash
Screenshots

System information

OS: macOS
Version of supabase-js: 2.45.1
Version of Node.js: 20.16.0

Additional information
Opening here because the error message I got in my actual project was
The package at<EMAIL_ADDRESS>attempted to import the Node standard library module "stream".
It failed because the native React runtime does not include the Node standard library.

Is there any update on this? I've run into the same issue

now that we have native ws support I do think that we can remove ws which seems to be the source of the issue.
https://github.com/supabase/realtime-js/pull/426 here's a branch for us to use for testing to see if we can fix it by removing ws from realtime-js dependencies.
but after removing it I keep getting the same issue and the only dependency that uses it's node_modules/@expo/cli 😞 . what could be the way to fix it?

@filipecabaco I'm not sure what the next step is, how can I help you?

@aldebout maybe. it seems that the main issue was the fact that we had the ws dependency which created issues with expo. the PR https://github.com/supabase/realtime-js/pull/426 removes said dependency.
could you try to checkout the repo, checkout the branch fix/remove-ws-lib and override the dependency to check if it's not something related to my environment?

I tried using the branch but I'm having issues because package.json references the build outputs (/dist/...) and they're not in the github source code :/
When you tested locally, did you use npm with overrides or a local link? I've had issues with npm overrides in the past, it might work better with yarn or pnpm.

I need to try it again but if I'm not mistaken I did use overrides... maybe I should just make an example with just realtime-js and expo to make it easier to test out without overrides and just importing the "fix branch"

Any update? Currently running into this issue as well

sorry not yet as we were tackling other issues. I need to do another fix in realtime-js and then I will pick this one up again
as mentioned above I'm going to create a new repo with realtime-js so we can test this in a more consistent way to find a fix 👀

FYI I've merged https://github.com/supabase/realtime-js/pull/444 so 2.11.4-next.1 will have this code.
I do need some help testing this change, if possible do override realtime-js in supabase-js with this version

Did a new change to have it as an optionalDependency and also to have a script to remove modules if Expo is present
https://github.com/supabase/realtime-js/pull/448


Add product version in /end endpoint to fix #267

The issue or feature being addressed

#267

Details on the issue fix or feature implementation

I just based my implementation on what was already done for assembly version

Confirm the following

[X ] I have ensured that I have merged the latest changes from the dev branch
[ X] I have successfully run a local build
[x] I have included unit tests for the issue/feature

I need help on that one

[ X] I have included the github issue number in my commits

Build looks fine. Not sure if you saw my previous comment Thinking we can make what's provided in the environment info extensible from client apps instead. Thoughts?

Hi,
Yes, making /env extensible would be nice

/env => a bunch of properties that don't change during the life of the program execution
/health => a bunch of properties that do change during the life of the program execution

In fact, in my current implementation, I have created a health check that collects all version numbers of all assemblies installed in my program path...
I was looking for a way to move it to /env but saw that there was no extension point.
I'm not sure it's worth the effort: I mean, I would understand if you wanted to keep /env as simple as it is, but the product version would be nice, in the meantime.
Maybe we could open an issue and see how many votes it gets before starting to dev?

As another consumer of this library I vote to make /env extensible so that if people want to add this they can. Not everyone needs or wants this information, but because of it they'll be required to have System.Diagnostics.FileVersionInfo as a dependency with this PR.

Then I agree, let's work on an extension point for /env
@alhardy & @bdrupieski do you have an idea on how to do it?/where to do it?

Closing this one, review in issue https://github.com/AppMetrics/AppMetrics/issues/267


Update assignment of critic/error smooth window

Resolve #132. Adjust smooth window setting.

Codecov Report

Merging #134 (9221dbd) into master (ea2d2f3) will not change coverage.
The diff coverage is 33.33%.

@@           Coverage Diff           @@
##           master     #134   +/-   ##
=======================================
  Coverage   35.78%   35.78%
=======================================
  Files          24       24
  Lines        1794     1794
=======================================
  Hits          642      642
  Misses       1152     1152

Impacted Files
Coverage Δ

orion/primitives/tadgan.py
19.17% <33.33%> (ø)

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 ea2d2f3...9221dbd. Read the comment docs.


Fix CliCommand compile error

CliCommand not import Sets class

It has been fixed in 13037

It has been fixed in 13037

Thanks for your reminder.


Using unions for a result

When an union of Error and/or Ok is provided to a function like R.isOk, it will not accept the input, even though the code will run.
This makes it a lot harder to return different errors within a pipe.
Accepting different Error and Ok types which then get narrowed down, would be a lot nicer.
Example:
// Simplified code example
import { R } from "@mobily/ts-belt"

function fn(a: number) {
	if (Number.isNaN(a)) return R.Error("Number is NaN")

	return a > 10
		? R.Ok("Is bigger than 10")
		: R.Error({ value: a, message: "Number too small" })
}

R.isOk(fn(10)) // => Errors

It looks like that there is no perfect solution - but changing the signature of R.isOk to
declare function isOk<A, unknown >(result: Result<A, unknown>): result is Ok<A>;

Makes it a lot more compatible. Same goes for R.isError

I think the fn type should define its result type. In your example, the fn's type signature is function fn(a: number): R.Error<string> | R.Ok<string> | R.Error<{     value: number;     message: string; }>, in which the Error type is separated. that's not even possible with rescript code.
let fn = x => {
  switch x {
  | x if Float.isNaN(x) => Error("Number is NaN")
  | x if x > 10. => Ok(x)
  | _ => Error({value: x, message: "Number too small"})
  // ^ where error occurs, because the type system inferences
  // fn's return type as result<float, string> from the first match clause.
  }
}

in rescript, we can fix by describing the custom error type, in this case, a variant represents two cases of the errors.
type myError = JustError(string) | ErrorWithMessage({value: float, message: string})

let fn = (x: float): result<float, myError> => {
  switch x {
  | x if Float.isNaN(x) => Error(JustError("Number is NaN"))
  | x if x > 10. => Ok(x)
  | _ => Error(ErrorWithMessage({value: x, message: "Number too small"}))
  }
}

Maybe some black magic of type-level programming in typescript would handle this, but I think It'll hurt the signatures of functions in the Result module's readability(yes, this change should be applied to all the functions in result module, not just isOk and isError, since the input value, in this case the return type of the fn function is not sanitized).
So I think, in this case you can just write your own error type, not changing signatures of the functions.
type MyError = string | {
	value:number,
	message:string
}

function fn(a: number):R.Result<number,MyError> {
	if (!G.isNumber(a)) return R.Error("Number is NaN")

	return a > 10
		? R.Ok(a)
		: R.Error({ value: a, message: "Number too small" })
}

const x = R.isOk(fn(10)) // => no more errors

I'll post a type that meets your request later here, let me know what you think!

@JUSTIVE Hey, thank you for the detailed response! :)
For errors this could work, however, within a pipe Ok types are often implicitly defined, and being able to pass to R.isOk a union of R.Ok<string> | R.Ok<something lese> | R.Error to filter out the errors, does seem like a good use case.
But, if this is a ReScript limitation, there also doesnt seem to be a good solution to this ,except manually changing the generated Typescript code, which is not optimal

rescript, which is the basis of ts-belt, does not work like this because it uses a stricter type system than typescript. Since typescript is much more flexible than rescript, there seems to be a way if you want to try it. I'm currently working on a trick using hotscript, and I'd like to share it with you as soon as it's completed.

Sounds cool, thank you :)

just finished making a simple proof-of-concept.
here's link

While it may enhance developer experience(at least at a type level), I think It's a hacky way to achieve with the current state of typescript's type system. I didn't consider compiler performance and readability of the implementation. It's a very impractical case I guess.

we can easily remove these nightmare types by adding a type to your function.

guess it's ok to close this issue?

Yep :)


GUIDE.md: footnotes formatting

@vbatts why? now we have to worry about ordering!

perhaps it'll work fine as words too. but the base revision didn't work. the links were broken.

@vbatts oh you're right, bad brackets - could you kindly change () to [] ? thanks!

updated

LGTM, thanks


Cannot find module 'react-sketch' or its corresponding type declarations

I am receiving the following error when attempting to npm start from showcase folder.
ERROR in ./src/components/Canvas/index.tsx 2:0-43
Module not found: Error: Can't resolve 'react-sketch' in 'D:\Computer Science\Capstone\React-Sketch\react-sketch\packages\showcase\src\components\Canvas'
@ ./src/components/index.ts 3:0-40 3:0-40
@ ./src/App.tsx 6:0-65 20:36-42 22:36-48 24:36-47
@ ./src/index.tsx 1:0-28 14:31-34
ERROR in [at-loader] ./src/stores/config.ts:1:23
TS2307: Cannot find module 'react-sketch' or its corresponding type declarations.
ERROR in [at-loader] ./src/components/Canvas/index.tsx:2:36
TS2307: Cannot find module 'react-sketch' or its corresponding type declarations.
1 error has detailed information that is not shown.
Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.
webpack 5.69.1 compiled with 3 errors in 2596 ms
i ｢wdm｣: Failed to compile.

if you want to run demo, cd to packages/showcase and yarn start

Were you able to resolve this? @peanutrhs


Quote version in authorized_packages

As unquoted versions do not work for version numbers with MAJOR.MINOR.PATCH format.

@ochedru Updated the branch now. Hope that works.


Add a LABEL cache check testcase

Thanks to @tiborvass's review of another PR it was noticed that
we didn't have a testcase to make sure the cache checking for LABEL
was being done.  This adds a test for it.
Signed-off-by: Doug Davis<EMAIL_ADDRESS>

the failure has nothing to do with these edits.
ping @jfrazelle @tiborvass  for review

LGTM

LGTM


validate users on import

See PR: Change presence/uniqueness constraint on email #109

So can we close this?

We want to not allow duplicates of name + email combos


Add spinning indicator at advanced search

Add a spinning indicator at the advanced search

reference: https://ant.design/components/spin#spin-demo-custom-indicator
source: https://github.com/adoptium/aqa-test-tools/blob/master/test-result-summary-client/src/AdvancedSearch/AdvancedSearch.jsx

Could you assign this to me?


[Bug] AP AR Enhanced Table - Numeric value '' Is Not Recognized

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
I've already opened a ticket with Fivetran Support, and they've asked me to report the bug here as well. So, I'm pasting the ticket text below. We've recently added a dbt transformation package for Sage Intacct in Fivetran, and all individual table transformations have worked, except for one. There is a "sage_intacct__ap_ar_enhanced" transformation that has failed with an error message: "Numeric value '' is not recognized". The error message makes me think that there is a varchar column that has an empty string entry ('') that the Fivetran transformation code is trying to convert to the numeric data type. However, the error message is very short and not insightful enough to realize what column causes this error.
Relevant error log or model output
Database Error in model sage_intacct__ap_ar_enhanced (models/sage_intacct__ap_ar_enhanced.sql)
100038 (22018): Numeric value '' is not recognized
compiled Code at target/run/sage_intacct/models/sage_intacct__ap_ar_enhanced.sql

Expected behavior
"SAGE__INTACCT_AP_AR_ENHANCED" table constructed and inserted into in our destination of Snowflake.
dbt Project configurations
config-version: 2
name: 'sage_intacct'
version: '0.2.2'
require-dbt-version: [">=1.3.0", "<2.0.0"]
models:
  sage_intacct:
    +materialized: table
    +schema: sage
    intermediate:
      +materialized: view
vars:
  sage_intacct_database: havenpark
  sage_intacct_schema: sage
  sage_account_pass_through_columns: []
  sage_gl_pass_through_columns: []
  sage_intacct:
    gl_detail: "{{ ref('stg_sage_intacct__gl_detail') }}"
    gl_account: "{{ ref('stg_sage_intacct__gl_account') }}"
    ap_bill_item: "{{ ref('stg_sage_intacct__ap_bill_item') }}"
    ap_bill: "{{ ref('stg_sage_intacct__ap_bill') }}"
    ar_invoice_item: "{{ ref('stg_sage_intacct__ar_invoice_item') }}"
    ar_invoice: "{{ ref('stg_sage_intacct__ar_invoice') }}"
    sage_gl_pass_through_columns: ['location_id', 'location_name']
    sage_account_pass_through_columns: []
    sage_intacct_category_asset: ('Inventory','Fixed Assets','Other Current Assets','Cash and Cash Equivalents','Intercompany Receivable','Accounts Receivable','Deposits and Prepayments','Goodwill','Intangible Assets','Short-Term Investments','Inventory','Accumulated Depreciation','Other Assets','Unrealized Currency Gain/Loss','Patents','Investment in Subsidiary','Escrows and Reserves','Long Term Investments')
    sage_intacct_category_equity: ('Partners Equity','Retained Earnings','Dividend Paid')
    sage_intacct_category_expense: ('Advertising and Promotion Expense','Other Operating Expense','Cost of Sales Revenue', 'Professional Services Expense','Cost of Services Revenue','Payroll Expense','Payroll Taxes','Travel Expense','Cost of Goods Sold','Other Expenses','Compensation Expense','Federal Tax','Depreciation Expense')
    sage_intacct_category_liability: ('Accounts Payable','Other Current Liabilities','Accrued Liabilities','Note Payable - Current','Deferred Taxes Liabilities - Long Term','Note Payable - Long Term','Other Liabilities','Deferred Revenue - Current')
    sage_intacct_category_revenue: ('Revenue','Revenue - Sales','Dividend Income','Revenue - Other','Other Income','Revenue - Services','Revenue - Products')
    sage_intacct__using_invoices: true
    sage_intacct__using_bills: true
analysis-paths: ["analysis"]

Package versions
packages:

package: fivetran/sage_intacct_source
version: [">=0.2.0", "<0.3.0"]

What database are you using dbt with?
snowflake
dbt Version
dbtVersion: 1.3.0
jobs:

name: daily
schedule: 0 8 * * *
steps:

name: run models
command: dbt run

Additional Context
No response
Are you willing to open a PR to help address this issue?

[ ] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Hi @matt-tkachev thanks for opening this issue. I wasn't able to reproduce this myself, but I am wondering how you are running the Sage Intacct package? It looks like the changes you have applied to the package are directly within the package's dbt_project.yml is this true?
You should be making any variable changes that you want the package to apply to be within your root dbt_project.yml. I have seen some instances where updating the package dbt_project.yml directly can result in some unexpected behavior, like what you may be seeing.
Additionally, can you inspect the target/run/sage_intacct/models/sage_intacct__ap_ar_enhanced.sql file of your project and share the compiled code? This should give some insight more directly into what is erroring out.
Let me know!

Hello @fivetran-joemarkiewicz we're running the Sage Intacct package as a Fivetran transformation where I've added my GitHub fork of the package repository. The only changes I've made to the dbt_project.yml file are related to the schema name since the package assumes the schema to be Sage Intacct while in our case it's just Sage; thus, I don't think that it should cause any functional difference.
Also, I believe it's important to mention that I've integrated the same package fork (without the schema name changes mentioned above since their schema is Sage Intacct as expected by the package) for a different client, and it's been working without any issues for all tables including AP AR Enhanced. So, I think that the issue may have appeared due to a difference in the Sage Intacct data that the code doesn't expect. Because again, the error message implies that there is a varchar column instead of a numeric one that the package code expects.
I'm attaching the target/run/sage_intacct/models/sage_intacct__ap_ar_enhanced.sql file contents below. As with regards to the compiled code, I'm not sure if I'm able to access it since it's run by Fivetran. Should I run it in another environment to get the compiled version?
{{ config(enabled=fivetran_utils.enabled_vars_one_true(vars=["sage_intacct__using_bills", "sage_intacct__using_invoices"])) }}

with

{% if var('sage_intacct__using_bills', True) %}
ap_bill as (
    select *
    from {{ ref('stg_sage_intacct__ap_bill') }}
),

ap_bill_item as (
    select *
    from {{ ref('stg_sage_intacct__ap_bill_item') }}
),
{% endif %}

{% if var('sage_intacct__using_invoices', True) %}
ar_invoice as (
    select *
    from {{ ref('stg_sage_intacct__ar_invoice') }}
),

ar_invoice_item as (
    select *
    from {{ ref('stg_sage_intacct__ar_invoice_item') }}
),
{% endif %}

{% if var('sage_intacct__using_bills', True) %}
ap_bill_enhanced as (
    select
        ap_bill_item.bill_id,
        ap_bill_item.bill_item_id,
        cast(null as {{ dbt.type_string() }}) as invoice_id,
        cast(null as {{ dbt.type_string() }}) as invoice_item_id,
        ap_bill_item.account_no,
        ap_bill_item.account_title,
        ap_bill_item.amount,
        ap_bill_item.class_id,
        ap_bill_item.class_name,
        ap_bill_item.currency,
        ap_bill_item.customer_id,
        ap_bill_item.customer_name,
        ap_bill_item.department_id,
        ap_bill_item.department_name,
        ap_bill_item.entry_date_at,
        ap_bill_item.entry_description,
        ap_bill_item.item_id,
        ap_bill_item.item_name,
        ap_bill_item.line_no,
        ap_bill_item.line_item,
        ap_bill_item.location_id,
        ap_bill_item.location_name,
        ap_bill_item.offset_gl_account_no,
        ap_bill_item.offset_gl_account_title,
        ap_bill_item.total_item_paid,
        ap_bill_item.vendor_id,
        ap_bill_item.vendor_name,
        ap_bill_item.created_at,
        ap_bill_item.modified_at,
        ap_bill.due_in_days,
        ap_bill.total_due,
        ap_bill.total_entered,
        ap_bill.total_paid,
        ap_bill.record_id,
        count(*) over (partition by ap_bill_item.bill_id) as number_of_items
    from ap_bill_item

    left join ap_bill
        on ap_bill_item.bill_id = ap_bill.bill_id
),
{% endif %}

{% if var('sage_intacct__using_invoices', True) %}
    ar_invoice_enhanced as (
    select
        cast(null as {{ dbt.type_string() }}) as bill_id,
        cast(null as {{ dbt.type_string() }}) as bill_item_id,
        ar_invoice_item.invoice_id,
        ar_invoice_item.invoice_item_id,
        ar_invoice_item.account_no,
        ar_invoice_item.account_title,
        ar_invoice_item.amount,
        ar_invoice_item.class_id,
        ar_invoice_item.class_name,
        ar_invoice_item.currency,
        ar_invoice_item.customer_id,
        ar_invoice_item.customer_name,
        ar_invoice_item.department_id,
        ar_invoice_item.department_name,
        ar_invoice_item.entry_date_at,
        ar_invoice_item.entry_description,
        ar_invoice_item.item_id,
        ar_invoice_item.item_name,
        ar_invoice_item.line_no,
        ar_invoice_item.line_item,
        ar_invoice_item.location_id,
        ar_invoice_item.location_name,
        ar_invoice_item.offset_gl_account_no,
        ar_invoice_item.offset_gl_account_title,
        ar_invoice_item.total_item_paid,
        ar_invoice_item.vendor_id,
        ar_invoice_item.vendor_name,
        ar_invoice_item.created_at,
        ar_invoice_item.modified_at,
        ar_invoice.due_in_days,
        ar_invoice.total_due,
        ar_invoice.total_entered,
        ar_invoice.total_paid,
        ar_invoice.record_id,
        count(*) over (partition by ar_invoice_item.invoice_id) as number_of_items

        from ar_invoice_item
        left join ar_invoice
            on ar_invoice_item.invoice_id = ar_invoice.invoice_id
    ),
{% endif %}

ap_ar_enhanced as (
    {% if var('sage_intacct__using_bills', True) %}
    select *
    from ap_bill_enhanced
    {% endif %}

    {% if fivetran_utils.enabled_vars(vars=["sage_intacct__using_bills", "sage_intacct__using_invoices"]) %}
    union all
    {% endif %}

    {% if var('sage_intacct__using_invoices', True) %}
    select *
    from ar_invoice_enhanced
    {% endif %}

),

final as (
    select
        coalesce(
                {% if var('sage_intacct__using_bills', True) %} bill_id {% endif %}

                {% if fivetran_utils.enabled_vars(vars=["sage_intacct__using_bills", "sage_intacct__using_invoices"]) %}
                ,
                {% endif %}

                {% if var('sage_intacct__using_invoices', True) %} invoice_id {% endif %}
        ,null) as document_id,
        coalesce(
                {% if var('sage_intacct__using_bills', True) %} bill_item_id {% endif %}

                {% if fivetran_utils.enabled_vars(vars=["sage_intacct__using_bills", "sage_intacct__using_invoices"]) %}
                ,
                {% endif %}

                {% if var('sage_intacct__using_invoices', True) %}  invoice_item_id {% endif %}
        ,null) as document_item_id,
        case
            {% if var('sage_intacct__using_bills', True) %} when bill_id is not null then 'bill' {% endif %}
            {% if var('sage_intacct__using_invoices', True) %} when invoice_id is not null then 'invoice' {% endif %}
        end as document_type,
        entry_date_at,
        entry_description,
        amount,
        currency,
        due_in_days,
        item_id,
        item_name,
        line_no,
        line_item,
        customer_id,
        customer_name,
        department_id,
        department_name,
        location_id,
        location_name,
        vendor_id,
        vendor_name,
        account_no,
        account_title,
        class_id,
        class_name,
        created_at,
        modified_at,
        total_due,
        total_entered,
        total_paid,
        number_of_items,
        total_item_paid,
        offset_gl_account_no,
        offset_gl_account_title,
        record_id
    from ap_ar_enhanced
)

select *
from final

Thanks for the context @matt-tkachev. While the intention of the packages is that you do not need to fork them, if you have been able to implement this properly elsewhere then I agree that there may be something we need to remedy in the package code.
It seems the code you shared is the dbt version of the code, would you be able to share the compiled version? This code should be in the target folder and will not have any of the dbt-jinja logic within it. It should be the code that is run in your warehouse. Upon inspecting that we should get a good sense of where the error may be happening.

My apologies @matt-tkachev, I just saw your comment about not being able to access the direct target compile code since it is being orchestrated by Fivetran.
Let me see if I can reproduce. In the meantime, do any of the staging models used in this AR and AP model look particularly "off" when you inspect them in your destination?

@matt-tkachev unfortunately I have not been able to reproduce this error 🤔. If you are unable to find anything that looks off in the underlying data, it may make the most sense to meet over a video call. If you would like, feel free to schedule some time during our office hours. We can then debug this live!

Hey @fivetran-joemarkiewicz, I am working with Matt on the Support Ticket for this.
I have checked into his latest point regarding the column type differences and confirmed the same in the DBT Docs for the Project.
The [stg_sage_intacct__ar_invoice_item] model (https://fivetran.github.io/dbt_sage_intacct_source/#!/model/model.sage_intacct_source.stg_sage_intacct__ar_invoice_item) defines class_id as an INT:

The stg_sage_intacct__ap_bill_item model defines it as a String:

@matt-tkachev @fivetran-rory thanks so much for sharing the additional information, this has been incredibly helpful!
Upon you raising the class_id as the problem, I believe I unintentionally caught this error last week when I was working on an unrelated update to this package (and the upstream dbt_sage_intacct_source) package. Here is my PR #14  for the source package which includes a safe cast of the class_id to be of type string for destinations. This will ensure the type of error you are seeing does not occur.
I am actually planning on releasing these updates either today or tomorrow, so this is great timing! Another reason it is usually best to install the package versus forking it is you will be able to easily update the package via your packages.yml once I roll these updates out. Otherwise you will need to manually ensure your fork is up to date with the origin. If you are interested in testing the updates in my PR before they go live, you can use the first option in your root packages.yml (or if you would like to still use the fork, you can just update the packages.yml in your fork to the second option).

packages:
  - git: https://github.com/fivetran/dbt_sage_intacct.git
    revision: feature/gl-batch-addition
    warn-unpinned: false

packages:
  - git: https://github.com/fivetran/dbt_sage_intacct_source.git
    revision: feature/gl-batch-addition
    warn-unpinned: false

I'll be sure to share updates here once the updates are live on the main branches. Thanks again!

Hello @fivetran-joemarkiewicz I've tested your PR, and it has solved the issue. The AP AR Enhanced table has been successfully constructed. Thanks for providing it!
As with regards to forking against using the original package, we have added some custom code to add the location columns to the target tables that didn't have them because our clients considered these columns to be essential for their reporting purposes. When we had initially contacted Fivetran Support about the dbt package not having the location columns in some tables, they'd said that they'd had it in their backlog but hadn't specified an ETA for the implementation and had advised us to make our own copy of the repository and develop any needed package additions there. That was the first reason which made us decide to fork the repository and add our custom code for including the location columns there.
Besides the location columns issue, as I've mentioned before, when I was adding the dbt package, there was an instruction in Fivetran Transformations asking to add a public access key for Fivetran to the repository so that Fivetran would have SSH access to the repository. I'm pretty sure that it's only possible to add a public access key to the repositories where you're an owner/admin; thus, I don't believe that it's possible to add a public access key provided by Fivetran to the original/main package repository since obviously I'm not an owner of it. So, that was the second reason behind the forking strategy.
However, since you've mentioned that most organizations add the original package repository to their orchestration platform, my understanding regarding the issues above might be wrong. Please let me know if I can troubleshoot the problems described above without using a custom fork. Thanks for your help once again!

Hi @matt-tkachev the reasoning for the forking of this repo makes sense to me with your need to include the location field. By the way, if you are interested in contributing that to the main version of the package, we would happily welcome reviewing a PR!
I also wanted to share that the latest update of the dbt_sage_intacct_source package should include the fix to this issue. As such, I will close out this ticket. Thanks again @matt-tkachev and @fivetran-rory for your collaboration efforts on understanding the issue and providing a fix!


Master clock

Initial PR for the master clock script. Includes adding the script to the main menu.
Also includes minor CV Recorder changes as these are not yet merged into the main upstream branch.

Note that in addition to changes mentioned in the comments above I implemented a change to allow pulse width percentages up to 80% of the total clock cycle of output 1 (fixed at /1).

Sorry it's been so long since I looked at this. Just tested again and found a few things:
In lcm() there is a chance of a divide by zero, I'm not sure exactly how it happens but it halted the code during my test. An easy fix would just be to add this max() calculation so it's never lower than 1 before dividing, but that is a bit of a bodge so there might be a better way to do it.
lcm = lcm*item//max(self.computeGcd(lcm, item), 1)
The other much more important thing, is that if you set any of the outputs to random (0) they break all the other outputs, I'm not sure why this is but tbh it could be worth just removing the random functionality and make 0 be 'off', and then add it in at a later date if it can be made to work as it's a great script without it.
The percentage:millisecond display is potentially a little confusing; even once I read what it was showing at a glance I'd forget which number was which. I think it might be more intuitive to just pick one (percentage would be clearer to most eurorack users I'd imagine) and just display that, and then maybe have a constant in the code if people really wanted to change it.

Suggested changes made and merge conflicts resolved - let's merge ASAP!

It looks like the Turing machine has been accidentally removed and master clock not imported from the contrib folder, I think that's the only thing failing now!

Awesome work everyone! I think this script is an awesome addition to the EuroPi ecosystem!


[PHPStanRules] Another patch version BC break

Well thank you for another patch version BC break. :man_facepalming:
https://github.com/symplify/symplify/commit/0f48a40c6dea3d68a3a4d25e6a2d092605ea6d97
Causes PHPStan to fail like this:
Note: Using configuration file /app/phpstan.neon.
These files are included multiple times:
- /app/vendor/symplify/phpstan-rules/config/services/services.neon
- /app/vendor/symplify/phpstan-rules/config/services/name-resolver-services.neon
- /app/vendor/symplify/phpstan-rules/packages/cognitive-complexity/config/cognitive-complexity-services.neon

It can lead to unexpected results. If you're using phpstan/extension-installer, make sure you have removed corresponding neon files from your project config file.

Of course it's easy to fix by removing the files from my own config - but it took a while to figure out what's causing the problem.
Once again great improvement for a minor version, terrible one for a patch version.

There is an easy way around this.

make sure you have removed corresponding neon files from your project config file.

This should help :+1:

Of course. I already wrote that I easily fixed it by removing them. My point is that previously it was required to have the files in the config and now it's required to not have them there which is BC break.


chore(blog): add june community summary blog

Community Summary Update for the month of June

/ptal

/rtm


Add a VolumeInstance CRD to internal.acorn.io

A VolumeInstance would allow things like acorn volume create.
It would also allow for a centralized place for looking at volume statuses instead of compiling the status from various objects every time they are needed.
Lastly, this would also allow for significant expansion of the Acorn volume API.

Moving this over with the rest of the volume issues...but do we really need this issue or can it be closed?


GitHub runner 2.302.0

Description of changes
New release: https://github.com/actions/runner/releases/tag/v2.302.0
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Welcome to the party @zimbatm 👋


Allow multi-line display on custom text fields and the About field

Is your feature request related to a problem? Please describe.
Currently, these text fields for the About section and custom text content accept multiline entry but when you look at your profile in the app, the text is displayed as one continuous chunk of text with no line breaks.
Describe the solution you'd like
It would be good if we could change this so that the text appears as it was entered.
Video of the Issue
https://user-images.githubusercontent.com/69275762/156786394-d039d558-cc33-4d47-9cec-44e9f323eed1.mov

Can i implement this using the maxLine property?

Hi, I am Palak Jain, a contributor to OpenForce 2022. I would like to work on this issue. I would be making a PR as soon as I am done with resolving the issue. Thank you.

I thought standard workflow is to claim an issue and the work on it :(

@jalanprakhar We are allowing multiple people to work on issues so that more of you have a chance to contribute :)

Hey @tinashe404  . I am Shubham Shah, a contributor to OpenForce 2022.
I would like to work on this issue so please can you assign this issue to me

Hi, I am Ninad, a contributor to OpenForce 2022. I would like to work on this issue. I would be making a PR as soon as I am done with resolving the issue. Thank you.


Is there a Bootstrap 4 implementation of this?

Just wondering if anyone has added Bootstrap 4 to the library or if there's any instructions anyone could give on this, before I try it.

Adding bootstrap is no different to adding any other CSS lib, though it feels wrong to bring in jQuery ;p
npm install bootstrap-4 popper.js jquery --save
Then add the following to src/renderer/main.js
/* eslint-disable no-unused-vars */
import $ from 'jquery'
import 'bootstrap/dist/css/bootstrap.min.css'
import 'bootstrap/dist/js/bootstrap.bundle.min.js'

Then add something to LandingPage.vue, for example, source from: https://getbootstrap.com/docs/4.0/examples/jumbotron/

Maybe that helps.

Thanks for the reply. I ended up using ElementUI.


In Debts / Credits Analysis Report when balance is zero , cant click on it and view credit history

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

It is not clear what is at stake, please provide more information


Fix flipped forcefeed log

About the PR

Target and actor are flipped... oopsies
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

keron gon murder u

User issue


[keepercore] - allow dynamic CLI aliases

From user feedback on Discord:
Queries like is(aws_alb) and ctime<"-7d" and backends==[] with(empty, <-- is(aws_alb_target_group) and target_type=="instance" and ctime<"-7d" with(empty, <-- is(aws_ec2_instance) and instance_status!="terminated")) <-[0:1]- is(aws_alb_target_group) or is(aws_alb) are powerful but also complex.
Chat protocol:
ViktorHarutyunyan:
I am not sure what's the target audience but I think this is an overkill, I think a simple query like:
> ck show unused lbs
then there should be like a man page explaining the criteria of selection.
then the user can choose to say -r region -a account etc..
or say --days=7
imo, this is much simpler
then if we talk about UI, then it is all clicks and nice small value edit windows.
ck show unused tgs ....
ck show unattached volumes ....

The CLI already has aliases. We should make those configurable so that users can download/exchange other users aliases. So the complex query above could turn into show unused loadbalancers.
Personally I'd also not want to have to type the complex query even if I know the syntax. A shorthand form would be useful.

2.0.0a9 ships with a query template engine. This allows defining complex queries and store them in the library under a given name. A query can now expand and execute this query.
> templates add old_load_balancer is(load_balancer) and reported.age > {{old}}
Template old_load_balancer added to the query library.
is(load_balancer) and reported.age > {{old}}
> query expand(old_load_balancer, old=3w)

It is not a dynamic CLI alias, but solves the original problem of managing complex queries.
I would opt to close this ticket.


fix(android): bottomnav and ripple - NativeClass decorations needed

closes https://github.com/Akylas/nativescript-material-components/issues/164

thanks!


Illegal Instruction Error on latest 2.8.1 image

Checklist
Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? yes
Are you sure you're not using someone else's docker image? yes
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? not relevant
Describe the bug
Have the following error in the docker container logs:
nginx line 18: 1631 Illegal instruction (core dumped) node --abort on uncaught exception --max_old_space_size=250 index.js
Image will now no longer start. Error started a few hours ago.
What version of Nginx Proxy Manager is reported on the login page?
Cannot get to login page

Same issue here after upgrading to 2.8.1. Is there a stable version I can safely downgrade to?

I have been on 2.8.1 since it was originally released (28 days ago according to Github) which was fine, but it seems that the 2.8.1 image was modified and pushed a few hours ago which is what seems to be causing this (for me anyway)

I have been on 2.8.1 since it was originally released (26 days ago according to Github) which was fine, but it seems that the 2.8.1 image was modified and pushed a few hours ago which is what seems to be causing this (for me anyway) - my Watchtower auto pulled it this morning.

My watchtower did too. I downgraded to 2.8.0 but receiving the following error:
`
[4/12/2021] [3:33:38 PM] [Migrate  ] › ℹ  info      Current database version:<PHONE_NUMBER>4703
[4/12/2021] [3:33:38 PM] [Global   ] › ✖  error     The migration directory is corrupt, the following files are missing:<PHONE_NUMBER>4702_redirection_scheme.js,<PHONE_NUMBER>4703_redirection_status_code.js`
Both versions are unusable for me at this point.

Edit: Replaced the missing files from the new version and downgraded to 2.8.0 and it seems to be working now. I can access the front end and the proxy appears functional for now.

Fortunately I had a full backup with I reverted to which got me working again. Made sure I stopped Watchtower for now though until resolved :-)

Lets document workaround:

vi docker-compose.yml
and change label to 'jc21/nginx-proxy-manager:2.8.0'

Pull new image
docker-compose pull

Create migration files
docker exec -it nginx_proxy_manager /bin/sh
cd /app/migrations
touch<PHONE_NUMBER>4702_redirection_scheme.js
touch<PHONE_NUMBER>4703_redirection_status_code.js
``

Restart docker container
docker-compose restart nginx_proxy_manager

Let's document workaround:
1. `vi docker-compose.yml`
   and change label to 'jc21/nginx-proxy-manager:2.8.0'

2. Pull new image
   `docker-compose pull`

3. Create migration files
   `docker exec -it nginx_proxy_manager /bin/sh`
   `cd /app/migrations`
   `touch<PHONE_NUMBER>4702_redirection_scheme.js`
   `touch<PHONE_NUMBER>4703_redirection_status_code.js`

4. Restart docker container
   `docker-compose restart nginx_proxy_manager`

Thank you. I actually had to copy the files entirely as the blank .js files didn't work to completely get me up and running..

Additional Logs:
pi@pi-proxy:~/docker $ docker logs nginx_proxy_manager
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01_s6-secret-init.sh: executing...
[cont-init.d] 01_s6-secret-init.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/production.conf
  ❯ /etc/nginx/conf.d/include/proxy.conf

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbed0219c
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /etc/nginx/conf.d/include/assets.conf
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
  ❯ /etc/nginx/conf.d/include/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
  ❯ /etc/nginx/conf.d/default.conf
./run: line 18:   223 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
❯ Enabling IPV6 in hosts: /data/nginx
  ❯ /data/nginx/proxy_host/18.conf
  ❯ /data/nginx/proxy_host/15.conf
  ❯ /data/nginx/proxy_host/11.conf
  ❯ /data/nginx/proxy_host/1.conf
  ❯ /data/nginx/proxy_host/14.conf
  ❯ /data/nginx/proxy_host/8.conf
  ❯ /data/nginx/proxy_host/22.conf
  ❯ /data/nginx/proxy_host/2.conf
  ❯ /data/nginx/proxy_host/13.conf
  ❯ /data/nginx/proxy_host/16.conf
  ❯ /data/nginx/proxy_host/3.conf
  ❯ /data/nginx/proxy_host/19.conf
  ❯ /data/nginx/proxy_host/5.conf
  ❯ /data/nginx/proxy_host/4.conf
  ❯ /data/nginx/proxy_host/12.conf
  ❯ /data/nginx/proxy_host/23.conf
  ❯ /data/nginx/proxy_host/9.conf
  ❯ /data/nginx/proxy_host/6.conf
  ❯ /data/nginx/proxy_host/7.conf
  ❯ /data/nginx/custom/http.conf
  ❯ /data/nginx/default_host/site.conf

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe83719c
./run: line 18:   288 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeab219c
./run: line 18:   295 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9d219c
./run: line 18:   302 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe8f319c
./run: line 18:   309 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe88819c
./run: line 18:   326 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe99519c
./run: line 18:   333 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeaed19c
./run: line 18:   340 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe96019c
./run: line 18:   347 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbeda119c
./run: line 18:   354 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbee3019c
./run: line 18:   366 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea2d19c
./run: line 18:   377 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9f719c
./run: line 18:   384 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe86519c
./run: line 18:   391 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

2.8.1 was rebuilt yesterday to address a vulnerability in openssl. This problem is likely due to the base nginx image: https://hub.docker.com/r/jc21/alpine-nginx-full.
To investigate if this image will run correctly on your architecture:
docker run --rm -ti jc21/alpine-nginx-full nginx -V

Should this NOT work for you, please mention the architecture you're running it on. Someone has already mentioned arm7 (thank you!)
I'll continue to investigate what's happened here, but ..
For now
To go back to a previous, but compatible build, use the github-develop docker tag.

Ok looks like it's nodejs then! I'll have it fixed hopefully today

Ok looks like it's nodejs then! I'll have it fixed hopefully today

Thank you for your prompt response to this. I switched to github-develop and so far so good.

Ok looks like it's nodejs then! I'll have it fixed hopefully today

Many thanks for looking into this so promptly for us.

Just wanted to pop by as i'm having the same error as well. Currently in process of downloading github-develop tag as well to see if it works for me. Much appreciated to the quick response time!

Thanks for the github-develop tag. Going to try that now. Armv7 arch (Pi4).

So the cause of the problem is this: nodejs packages in alpine have been updated since the last time the base image was built. Unfortunately they are broken for arm7, at least.
I can't seem to find a fixable workaround for it, so instead I've repushed the github-develop branch to latest, 2, 2.8.1. This problem unfortunately affects all future releases as well.
I'll close the issue as those images should be fine now.


⚠ GreatPosterWall has degraded performance

In a33ec48, GreatPosterWall ($GPW) experienced degraded performance:

HTTP code: 200
Response time: 2090 ms

Resolved: GreatPosterWall performance has improved in aec732d after 8 minutes.


Note field interoperable with Brays application

It would be great to have an optional note field for each individual item that could record information about copyright, pii, redaction, etc.; this info could be passed along to the dip to be read by Brays within the Brays application to aid in decision-making within the metadata unit.  Can discuss in future in-person meeting if this isn't clear.

You can add the field 'productionNotes' to accomplish that. Brays understands that field and will flag the object.
Would that work?

There is also 'uhlib.note'. @metaweidner would something like that work as well?

@seanlw   I'm unfamiliar with the specific functionalities of Brays or how that note might look within the carpenter's app, since there aren't really "fields" that we work with in Carpenters.  This sounds promising, though---let's discuss in standups in the new year?

For v1.0 it would be with the spreadsheet metadata. Would this be information that would benifate being listed in the finding aid as well?
We can pick this back up in the new year.

@seanlw  https://uhlibraries-digital.github.io/bcdams-map/#note is a display field for end-user descriptive data. We may need to differentiate between fields for display (public) and non-display (in-house).

@seanlw   Also, I think the thought was that it was just a comment that would be passed to the other app... it wouldn't necessarily have to be included in the formal metadata record... you would need to ask Anne about her thoughts on that.  This functionality would essentially be a way to streamline comments from SC to the metadata unit.

@seanlw    I was thinking in terms of v 2.0.  No need to integrate that into the old version.

@ajkrewer Ok, v2.0 would be different. We can discuss this during our first Sprint planing meeting for 2017.


New version: Piriform.CCleaner.ProTrial version 5.91

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

/azp run


Change language statistics to save size instead of percentage (#11681)

Backport #11681

More fixes are coming

Please integrate https://github.com/go-gitea/gitea/pull/11692

@CirnoT done

Make lgtm work


[dapsys] Exception when no continuous recording is contained in file

Function fails when no continuous recording is contained in file

fixed by #31


Add Cyber Start to Beginner/Intro education section

Added a section for beginner/introductory level resources, like Cyber Start, which is focused on simple, gamified challenges for High School (and maybe other education levels).

Approved


Peers not reachable for a 500 node GCE Kubernetes cluster

I tried to create a 500 node Kubernetes cluster but cluster validation failed during the kube-up process:
Attempt 1 to check Docker on node oneofmany-minion-496 ... [working]
Attempt 1 to check Docker on node oneofmany-minion-497 ... [working]
Attempt 1 to check Docker on node oneofmany-minion-498 ... [working]
Attempt 1 to check Docker on node oneofmany-minion-499 ... [working]
Attempt 1 to check Docker on node oneofmany-minion-500 ... [working]

Kubernetes cluster is running.  The master is running at:

  https://<IP_ADDRESS>

The user name and password to use is located in ~/.kubernetes_auth.

... calling validate-cluster
Project: kubernetes-scale
Zone: asia-east1-b
Running: cluster/../cluster/gce/../../cluster/../cluster/gce/../../cluster/../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl get minions -o template -t {{range.items}}{{.id}}
{{end}}
F0127 12:51:17.950796    2168 get.go:143] 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]

After waiting a bit I re-ran the cluster validation process which now finds 500 nodes but (very slowly) determines they are not working yet.
$ cluster/validate-cluster.sh
Project: kubernetes-scale
Zone: asia-east1-b
Found 500 nodes.
Attempt 1 at checking Kubelet installation on node oneofmany-minion-1 ... [not working yet]
Attempt 2 at checking Kubelet installation on node oneofmany-minion-1 ... [not working yet]
Attempt 3 at checking Kubelet installation on node oneofmany-minion-1 ... [not working yet]
Attempt 4 at checking Kubelet installation on node oneofmany-minion-1 ... [not working yet]
Attempt 5 at checking Kubelet installation on node oneofmany-minion-1 ... [not working yet]
Attempt 6 at checking Kubelet installation on node oneofmany-minion-1 ... [not working yet]
Attempt 7 at checking Kubelet installation on node oneofmany-minion-1 ...
Kubelet failed to install on node oneofmany-minion-1. Your cluster is unlikely to work correctly.
Please run ./cluster/kube-down.sh and re-create the cluster. (sorry!)

We should investigate what is going on here.

I took a quick look, and found that kubelet complaints net container cannot start. I checked docker log, and found error message: "no available ip addresses on network".

Is this related to how I compute IP addresses, as shown in PR #3849 ?

My fault. I incorrectly re-created the code to compute the IP addresses -- forgetting to add /24 for the CIDR address. One more reason for having this functionality checked in! Fixed.


⚠ ESPN has degraded performance

In d9e6ab5, ESPN (https://espn.com) experienced degraded performance:

HTTP code: 200
Response time: 710 ms

Resolved: ESPN performance has improved in 5b3e246.


Long waiting times when opening minified js file.

Hey there,
I am not sure this has been reported yet and it could very well be related to this #979 issue.
When I open a minified file (in my case a default jquery v1.11.2) I get the Keep Waiting or Close dialog.
I can reproduce that 100% every time. Now I opened the file in dev mode and recorded the timeline and get the below:

Hope this helps
Atom: 1.0.0
OS: Mac 10.10.3

Thanks for the report.

it could very well be related to this #979 issue.

It's very likely that it is, so I'm closing this in favor of that issue. Please follow along there :bow:


CLI interactive mode

Inspired by this tweet and this PR to create-react-native-app and obviously Jest.
I think it would be very nice if the dev registry when starting, would have some sort of interactive mode.
Perhaps a command to rebuild the components (only changed or all - jest style) and perhaps one to toggle the verbosity level

One of the very useful features (perhaps async without delaying startup time) would be to auto-detect new oc/compiler versions, and ask the user for an auto update :)


[bug]: Crash after window resize on invokeai-configure

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
8gb
What version did you experience this issue on?
main branch
What happened?
When attempting to call invokeai-configure with a terminal window that was too small, you receive the
Maximize the window and/or decrease the font size then press any key to continue. Type [Q] to give up..

prompt.
After resizing the window and hitting enter, I encountered this error:
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "D:\invokeai\.venv\Scripts\invokeai-configure.exe\__main__.py", line 7, in <module>
  File "D:\invokeai\invokeai\backend\install\invokeai_configure.py", line 927, in main
    init_options, models_to_download = run_console_ui(opt, new_init_file)
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\invokeai\invokeai\backend\install\invokeai_configure.py", line 746, in run_console_ui
    torch.multiprocessing.set_start_method("spawn")
  File "C:\Python311\Lib\multiprocessing\context.py", line 247, in set_start_method
    raise RuntimeError('context has already been set')
RuntimeError: context has already been set
NativeCommandExitException: Program "invokeai-configure.exe" ended with non-zero exit code: 1.

Everything worked as expected once invoke-configure was called a second time, with a correctly sized window.
Screenshots
No response
Additional context
Using Python 3.11.
Contact Details
No response

I had a very similar problem with Python 3.10 on Ubuntu Linux 23.10. I got the RuntimeError: context has already been set error upon running invokeai-configure --root . from the terminal, although I did not see any prompt about resizing the window. Running invokeai-configure --root . a second time worked as expected without resizing any terminal windows.

The configure script was removed in v4.


Strange type-error from the analyzer (2.1.0-dev.8.0)

Hi, with such code:
import 'dart:html';
import 'package:mockito/mockito.dart';

class WindowMock extends Mock implements Window {}

The analyzer shows the error in the 4th string:
The return type of getter 'Window.opener' is 'WindowBase' which isn't assignable to the type 'Window' of its setter 'Window.opener'.
For the stable Dart version, there are no errors.
dart --version: Dart VM version: 2.1.0-dev.8.0 (Wed Oct 24 21:47:12 2018 +0200) on "linux_x64"
I do not understand what should I do to fix the code, or it is just an issue of the new analyzer.
Can somebody help, please?

Giving an area so it shows as triaged.


how do i make a bot with a database?

Hello
I'm using bot for my thesis assignment
I want to ask how do I interact with the database?
then what should i do?
this is my script
public function execute()
    {
        $message = $this->getMessage();
        $chat_id = $message->getChat()->getId();
        $text    = trim($message->getText(true));

        if ($text === '') {
            $text = 'Masukkan mata kuliah: ' . $this->getUsage();
        }

        $query = DB::getPdo()->query("SELECT * from informasi_perkuliahan
		WHERE namamk = '$text'");

        while($row = $query->fetch()) {

        }

        $data = [
            'chat_id' => $chat_id,
            'text'    => $text,
        ];

        return Request::sendMessage($data);
    }

Hi @lorennatasya
Sorry for the very late reply to this!
Did you manage to get what you needed to work?


Stop using Cloudflare for the website -- or at least warn users that their data is shared

It is crazy that libretranslate uses Cloudflare, and allows a privacy-abusing tech giant to access all the sensitive translations that people may be using the service for -- without even warning the users.
First, there is no privacy policy.  There should be.
Second, if Cloudflare is going to be used, there should be a loud and clear notice to all users that Cloudflare Inc. has visibility of all their translations despite the HTTPS padlock.  And this should not be buried in the fine print of the privacy policy; it should be unavoidably loud.
Some of the Cloudflare risks and harms are documented here:
https://git.disroot.org/cyberMonk/liberethos_paradigm/src/branch/master/rap_sheets/cloudflare.md
Please consider renaming the service if Cloudflare usage continues.  There is nothing “libre” about Cloudflare’s exclusive walled garden.
Related issue:
https://github.com/argosopentech/argos-translate/issues/251

Thanks for your concern @bruceleerabbit :pray: (I currently manage libretranslate.com).
Cloudflare currently helps the website to stay online when it receives a lot of requests, as well as ban IPs/users that currently abuse the service. If you have an alternative service that is free and open source (and has the same features as cloudflare), send it our way.
We're not going to rename the service, but you can certainly host your own server if you have privacy concerns (which you should always do, if these are important to you).

Cloudflare currently helps the website to stay online when it receives a lot of requests, as well as ban IPs/users that currently abuse the service. If you have an alternative service that is free and open source (and has the same features as cloudflare), send it our way.

Trading confidentiality for performance is a bad trade.  It’s better to have a sluggish website than one that shares sensitive data with a bad actor.

We're not going to rename the service, but you can certainly host your own server if you have privacy concerns (which you should always do, if these are important to you).

This is not about me. For me the problem is solved by running locally inside a firejail --net=none.  I wrote this bug report for the public -- the unwitting masses.
This is about the people who discover Libretranslate; baited by “libre” and FOSS to grant excessive trust unwittingly. These people think they’ve dodged the surveillance capitalist behind Google Translate -- only to be led into the surveillance trap of another privacy abusing tech giant.  You have the guy in that linked thread who was entirely oblivious to Cloudflare thinking he could feed other people’s sensitive medical records into LibreTranslate.
Even if I were to host an instance that has no surveillance capitalists in the loop & has a privacy policy suitable for sensitive docs, it doesn’t solve the problem because some people will still find the LibreTranslate trap.
There should be a banner on that page that’s hard to miss.  It should say:
“all queries on this page are shared with Cloudflare, Inc., a separate entity not under our control. This service is not suitable for processing sensitive data.  Data submitted on this page is done so at your own risk.”
I see no case here for not informing people.


GH-40899: [CI][Java] Check dependency licenses

Rationale for this change
Check licenses of Java dependencies so that we don't accidentally pick up something that isn't fully acceptable to Apache (like the Eclipse Public License which is Category B).
What changes are included in this PR?
Run license-maven-plugin at build time. Since the plugin itself is LGPL, we don't depend on it directly, we just use it in the build scripts.
Are these changes tested?
This change itself a test.
It should fail until rebased on the fix for #40896.
Are there any user-facing changes?
No.

GitHub Issue: #40899

It's not exactly critical for 16.0.0. I wouldn't hold up the release. This is just to prevent future mistakes.

IMHO, it's good to have but definitely not a release blocker.


Deduce reference in boost::fusion::for_each

Description of the Change
Since Boost 1.68.0, boost::fusion::for_each started using T instead of const T& for function parameter, making it impossible to pass a non-copyable rvalue.
This change passes the function by reference by explicitly specifying template parameters.
Conditional macro based on Boost version is used to avoid "reference to reference" for versions prior to the introduced change in the interface.
Closes https://github.com/SOCI/soci/issues/679
Benefits
The project compiles with modern versions of Boost
Possible Drawbacks
None?

Excellent! Thank you very much!


The message "none is not an allowed value" suggests that "none" is not an acceptable option or setting within the configuration for Azure's ChatGPT.

ValidationError: 1 validation error for LLMChain
llm
none is not an allowed value (type=type_error.none.not_allowed)

Hi, I don't have currently access to Azure,
I opened a PR for a fix that should solve the issue.
The only change in the config should be in all llm fields, modifying to:
  type: 'Azure'
  name: <deployment_name>

Please let me know if it solved the issue


Resizing in Resizable Div

I'm unable to get the directives to resize when the parent div resizes. Have tried setting svg to auto, height and width to auto, and changing them to 100% etc.  Has anyone been able to get these things to resize with a div?

Hi . Having same pb here.
Could you tell me where you change the svg viewBox in the lib plz?
Thank