text:
Mix floating point values into runtime signature

Note: mixing the value for Instr::F32Le has been disabled, see here

To compare signatures across machines:
curl https://mainnet-api.tig.foundation/get-wasm-blob?algorithm_id=c003_a032 -L -o c003_a032.wasm; \
curl https://mainnet-api.tig.foundation/get-wasm-blob?algorithm_id=c004_a042 -L -o c004_a042.wasm; \
curl https://mainnet-api.tig.foundation/get-wasm-blob?algorithm_id=c001_a041 -L -o c001_a041.wasm; \
curl https://mainnet-api.tig.foundation/get-wasm-blob?algorithm_id=c003_a051 -L -o c003_a051.wasm; \
curl https://mainnet-api.tig.foundation/get-wasm-blob?algorithm_id=c003_a001 -L -o c003_a001.wasm;

target/release/tig-worker compute_solution '{"block_id": "4a360ec2480fc933d43efa5f9e15a6a0", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' d5826baf8951ebfbd6a57c6f5d32afb1 2509 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "a92773649e4a33f9fe944ab5ea2f8f80", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 82f6d6e4c396ac9fd484a645a0acad91 686 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "fec975cda05101d73e18d3a0af877ef3", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1187, 390], "algorithm_id": "c003_a051", "challenge_id": "c003"}' af3f2ce7b93ea018ea7e4efd0cf1b7aa 1412 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "c1575cd770c4e8444a2d639471cad587", "player_id": "0x5078b1e4032fccbc2a6e1b9d1baf0e8ad979b9cb", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 26e01002c3c9911372efb504a7c98d13 7 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "d9827858a8957583896777ea78c3fc9d", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 3d11feb97b4cd58f528d10aea4094c41 57 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "b2879c7d7aac1f0bdcdab9c952002c33", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1078, 402], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 01bb15478580c34336fdd6ddd31d60ff 123370 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "5f71a45fcad62e808d6e5fc324c8f9f2", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' b35bbc09f4f0a51ed38641ad445b8486 2395 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "782a437b391dbbcb1b5c98091af863ac", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1208, 387], "algorithm_id": "c003_a032", "challenge_id": "c003"}' efa0c9ce9b1702ff931dba7fed3e4532 309563 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "a3a8d8a014b39124a92185ae32088523", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1078, 402], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 0e8025d9939961017017c699afe87111 300452 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "0842ae6ddcdd155342b2a2622bca2f1e", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1270, 378], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 5d12d14c58d6e3cf281fe43acad717ab 39921 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "62277b64f8128746dd4e98f68b6e92ca", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1271, 377], "algorithm_id": "c003_a032", "challenge_id": "c003"}' ead2e1afd0d6cb2530ad3c5f9a117bf9 150488 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "d5826baf8951ebfbd6a57c6f5d32afb1", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' c881561e29c502edc218e4286256842a 555 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "087cf39f3947cd90913f952a813f5880", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1191, 388], "algorithm_id": "c003_a051", "challenge_id": "c003"}' a92773649e4a33f9fe944ab5ea2f8f80 12144 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "0e0a9793d97000395e7fe31ee55ed6a0", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1271, 377], "algorithm_id": "c003_a032", "challenge_id": "c003"}' b5e4f96d63b6cd0305d0f1f870fe7803 28705 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "5154e00248acb1b333446d1915c285cf", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1266, 379], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 781460d5b7af9ab7277dc89e82faf846 2004 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "5b04fb1577b40edef87923803dc4df66", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1270, 378], "algorithm_id": "c003_a032", "challenge_id": "c003"}' e050316337fa39de724ee27088718c85 106763 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "82f6d6e4c396ac9fd484a645a0acad91", "player_id": "0x9a1be92e41700394f2f2b1fbe2cc011979b3e992", "difficulty": [1356, 372], "algorithm_id": "c003_a051", "challenge_id": "c003"}' a7d8a64dbd17b0974507f1e0e0dea210 9901 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "5b04fb1577b40edef87923803dc4df66", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1270, 378], "algorithm_id": "c003_a032", "challenge_id": "c003"}' e050316337fa39de724ee27088718c85 106763 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "82f6d6e4c396ac9fd484a645a0acad91", "player_id": "0x9a1be92e41700394f2f2b1fbe2cc011979b3e992", "difficulty": [1356, 372], "algorithm_id": "c003_a051", "challenge_id": "c003"}' a7d8a64dbd17b0974507f1e0e0dea210 9901 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "4a360ec2480fc933d43efa5f9e15a6a0", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' d5826baf8951ebfbd6a57c6f5d32afb1 2509 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "b35bbc09f4f0a51ed38641ad445b8486", "player_id": "0xaacda4022e347e96236ab77cac0d32aea45f81f9", "difficulty": [1355, 373], "algorithm_id": "c003_a051", "challenge_id": "c003"}' cb174432f5d69c640fe4509c4b58426e 2419 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "9b9f903e3116414e3efafdd5fcc3913d", "player_id": "0x712f3a6e8050d507a7ef6dd096233ac18c60537f", "difficulty": [1094, 407], "algorithm_id": "c003_a001", "challenge_id": "c003"}' d42784c1ee1b3f164f1e06130b843915 283 c003_a001.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "1c14650a3d43dd8822f1136619a0c616", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' abb0fdfb11598ddf16ffc4c2f66b83bb 617 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "3d5126bdd94ad1678780f2002383120f", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 3451df57b28ef8d1808738a7b80de7cd 2004 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "3362a7e58095303c929283eaf85bc50b", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' cccbd2dff6fc5b70eb4883fac291744b 13 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "a1756b76d644c5a140ac3983c43766ac", "player_id": "0xc38ac76a7a4608959f8e10e7fe4fbe0db90029fa", "difficulty": [1140, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' a35ca651777d57aa12b402c3444489bc 8795 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "62277b64f8128746dd4e98f68b6e92ca", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1599, 351], "algorithm_id": "c003_a051", "challenge_id": "c003"}' ead2e1afd0d6cb2530ad3c5f9a117bf9 1954 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "e4588aee3b2de400319b924ba7db3e37", "player_id": "0x7c89f216d066192a30d0e9b978f84b098b1e88e1", "difficulty": [1043, 414], "algorithm_id": "c003_a001", "challenge_id": "c003"}' fd7e1ae76df927434f477eec89576435 464 c003_a001.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "304c5840795a3d5bb9791a4078820274", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' fec975cda05101d73e18d3a0af877ef3 5987 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "96be2afa478644b980f9980562779db6", "player_id": "0x712f3a6e8050d507a7ef6dd096233ac18c60537f", "difficulty": [1007, 439], "algorithm_id": "c003_a001", "challenge_id": "c003"}' bf9768809c1f15aabc032e82fb396510 126 c003_a001.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "1c14650a3d43dd8822f1136619a0c616", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1187, 390], "algorithm_id": "c003_a051", "challenge_id": "c003"}' abb0fdfb11598ddf16ffc4c2f66b83bb 1601 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "12adb7f0ea45b5b300425b6b606cb5df", "player_id": "0x9a1be92e41700394f2f2b1fbe2cc011979b3e992", "difficulty": [1005, 431], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 4976a52d349e960977ffe6a87d7d02e2 9731 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "304c5840795a3d5bb9791a4078820274", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' fec975cda05101d73e18d3a0af877ef3 963 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "62277b64f8128746dd4e98f68b6e92ca", "player_id": "0x0410c65554ff46fa9ff26d14ed0308e3c54228a9", "difficulty": [1133, 396], "algorithm_id": "c003_a051", "challenge_id": "c003"}' ead2e1afd0d6cb2530ad3c5f9a117bf9 54992 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "3b449c2225e1b72051afefcc38a4d989", "player_id": "0x9c6fd552f184fcd5c177347ccd2a1dac26280115", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 93cbbdaef4d8d9c40fb6f37e3e4bdf20 117 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "3d5126bdd94ad1678780f2002383120f", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1086, 401], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 3451df57b28ef8d1808738a7b80de7cd 744 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "3362a7e58095303c929283eaf85bc50b", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' cccbd2dff6fc5b70eb4883fac291744b 245 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "1c14650a3d43dd8822f1136619a0c616", "player_id": "0x4dc6d3acbfc3112bc42273b81873acdb0c3eff3d", "difficulty": [229, 526], "algorithm_id": "c004_a042", "challenge_id": "c004"}' abb0fdfb11598ddf16ffc4c2f66b83bb 417 c004_a042.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "e712837a9379d6d7ce5b1cca2ca72ff7", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1210, 386], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 5bc1f19b4e1fd067b674527f607154f9 5444 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "0e8025d9939961017017c699afe87111", "player_id": "0x5078b1e4032fccbc2a6e1b9d1baf0e8ad979b9cb", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' c013560a17708f498da72b71b92856a4 1187 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "c1575cd770c4e8444a2d639471cad587", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1271, 377], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 26e01002c3c9911372efb504a7c98d13 55929 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "3451df57b28ef8d1808738a7b80de7cd", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1187, 390], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 4cfc79b6a87cd58d1c6cfdc16d960dcc 1167 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "026461e45e6ab5a3dbef54f20496a91a", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1270, 378], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 1c14650a3d43dd8822f1136619a0c616 320024 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "b35bbc09f4f0a51ed38641ad445b8486", "player_id": "0xdbf7de04b9236d0cc5cec0aebfc9ddd2c73fbcaa", "difficulty": [1094, 400], "algorithm_id": "c003_a051", "challenge_id": "c003"}' cb174432f5d69c640fe4509c4b58426e 599 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "4976a52d349e960977ffe6a87d7d02e2", "player_id": "0xc38ac76a7a4608959f8e10e7fe4fbe0db90029fa", "difficulty": [1221, 392], "algorithm_id": "c003_a051", "challenge_id": "c003"}' f8af2dfd785fcc0734ca2d6d548cff8c 7482 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "781460d5b7af9ab7277dc89e82faf846", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1110, 398], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 0e0a9793d97000395e7fe31ee55ed6a0 163841 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "577457ae4eea54bbbdc80f28cfdfbfc8", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1271, 377], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 796f93a9585d575404d73471274e1f79 180736 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "a3a8d8a014b39124a92185ae32088523", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1271, 377], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 0e8025d9939961017017c699afe87111 79947 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "1c14650a3d43dd8822f1136619a0c616", "player_id": "0x9c6fd552f184fcd5c177347ccd2a1dac26280115", "difficulty": [1048, 408], "algorithm_id": "c003_a051", "challenge_id": "c003"}' abb0fdfb11598ddf16ffc4c2f66b83bb 116 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "c881561e29c502edc218e4286256842a", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' a0c8066c3dd1ef4e44792578f384f7bb 2033 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "796f93a9585d575404d73471274e1f79", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' d1ea11db6bb4fda4ac688eba742ebc2c 537 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "51757b6bafc37bda2ab48b5d185f5358", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1191, 388], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 60ab7e1d540f862093fe8bfb25be1d9d 1528 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "8f2dc01e939cffc67066d108bc66f7e2", "player_id": "0xc38ac76a7a4608959f8e10e7fe4fbe0db90029fa", "difficulty": [1493, 365], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 62277b64f8128746dd4e98f68b6e92ca 5623 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "424fba2f137f2a347a76bb8bc6d6a1a7", "player_id": "0x9a1be92e41700394f2f2b1fbe2cc011979b3e992", "difficulty": [1512, 357], "algorithm_id": "c003_a051", "challenge_id": "c003"}' e75431b50dfae28f5869c8d70dc06bd2 2990 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "f8af2dfd785fcc0734ca2d6d548cff8c", "player_id": "0x5078b1e4032fccbc2a6e1b9d1baf0e8ad979b9cb", "difficulty": [1078, 402], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 5154e00248acb1b333446d1915c285cf 1161 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "b3d4db28487f7580b5f23dad2bd22434", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1086, 401], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 8d12f6e2612a0118db9ebfa8301c1c04 955 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "5f71a45fcad62e808d6e5fc324c8f9f2", "player_id": "0x6c4e774ca36fb7bc0a26d19bf6a3a852f01ecc80", "difficulty": [9677, 422], "algorithm_id": "c001_a041", "challenge_id": "c001"}' b35bbc09f4f0a51ed38641ad445b8486 477 c001_a041.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "a1756b76d644c5a140ac3983c43766ac", "player_id": "0x7c89f216d066192a30d0e9b978f84b098b1e88e1", "difficulty": [1262, 386], "algorithm_id": "c003_a001", "challenge_id": "c003"}' a35ca651777d57aa12b402c3444489bc 807 c003_a001.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "cccbd2dff6fc5b70eb4883fac291744b", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1086, 401], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 3b449c2225e1b72051afefcc38a4d989 1495 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "d5826baf8951ebfbd6a57c6f5d32afb1", "player_id": "0x6c4e774ca36fb7bc0a26d19bf6a3a852f01ecc80", "difficulty": [9814, 422], "algorithm_id": "c001_a041", "challenge_id": "c001"}' c881561e29c502edc218e4286256842a 986 c001_a041.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "1102c953f4592804f03a699382ffb6d1", "player_id": "0x9c6fd552f184fcd5c177347ccd2a1dac26280115", "difficulty": [1063, 407], "algorithm_id": "c003_a051", "challenge_id": "c003"}' e5498f1922a40c6a59693491c4bcb1d1 431 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "2db888a29bcbf54a8f5eed8be185e7d6", "player_id": "0x9c6fd552f184fcd5c177347ccd2a1dac26280115", "difficulty": [130, 551], "algorithm_id": "c004_a042", "challenge_id": "c004"}' 2888110ce31de4ee233a7b6924f90331 549 c004_a042.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "abb0fdfb11598ddf16ffc4c2f66b83bb", "player_id": "0x9c6fd552f184fcd5c177347ccd2a1dac26280115", "difficulty": [1063, 407], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 3362a7e58095303c929283eaf85bc50b 154 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "5d12d14c58d6e3cf281fe43acad717ab", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' c4bf74bbc5494b461f24ad9ba1d48119 435 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "d823505f6b04059dab45704c5708260a", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1271, 377], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 96be2afa478644b980f9980562779db6 2014 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "2db888a29bcbf54a8f5eed8be185e7d6", "player_id": "0x9c6fd552f184fcd5c177347ccd2a1dac26280115", "difficulty": [109, 567], "algorithm_id": "c004_a042", "challenge_id": "c004"}' 2888110ce31de4ee233a7b6924f90331 616 c004_a042.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "f70396b9de0227672e17de3bedfa9909", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1271, 377], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 755e805a912f78a3c704be93819a4492 105192 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "47ada2671ae1a13c54423ceade6fb4a1", "player_id": "0xbbbffd989e9c06cd0808ba1be8cbc2ca1b160f8b", "difficulty": [1599, 351], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 8f2dc01e939cffc67066d108bc66f7e2 3473 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "4b19788b33c83d2bac5838b47d6f0a8f", "player_id": "0x122f614ee8bc744f930ed46bedace3f97ebd6871", "difficulty": [1515, 356], "algorithm_id": "c003_a051", "challenge_id": "c003"}' c1575cd770c4e8444a2d639471cad587 19379 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "93cbbdaef4d8d9c40fb6f37e3e4bdf20", "player_id": "0x9c6fd552f184fcd5c177347ccd2a1dac26280115", "difficulty": [1063, 407], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 1102c953f4592804f03a699382ffb6d1 23 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "182ff56b2c68be75ec2b377d7f9a7942", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' e0a1fdac133980d8d7c0862b849217b0 1120 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "d1ea11db6bb4fda4ac688eba742ebc2c", "player_id": "0xb4bb66cd93b02cbed344d68f91bd33e479d947f3", "difficulty": [1210, 386], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 087cf39f3947cd90913f952a813f5880 602 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "3d5126bdd94ad1678780f2002383120f", "player_id": "0xb28b25c93b6264a11b9031327f2bd41f04c10624", "difficulty": [1210, 386], "algorithm_id": "c003_a032", "challenge_id": "c003"}' 3451df57b28ef8d1808738a7b80de7cd 175568 c003_a032.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "026461e45e6ab5a3dbef54f20496a91a", "player_id": "0xe5a153002622c4a2ff88a4289157a92b5d3915ec", "difficulty": [1208, 387], "algorithm_id": "c003_a051", "challenge_id": "c003"}' 1c14650a3d43dd8822f1136619a0c616 1763 c003_a051.wasm >> out.txt; \
target/release/tig-worker compute_solution '{"block_id": "2db888a29bcbf54a8f5eed8be185e7d6", "player_id": "0x6c4e774ca36fb7bc0a26d19bf6a3a852f01ecc80", "difficulty": [3169, 432], "algorithm_id": "c001_a041", "challenge_id": "c001"}' 424fba2f137f2a347a76bb8bc6d6a1a7 893 c001_a041.wasm >> out.txt;

sha256sum out.txt
expected output at current HEAD:
824ef5c360ec0c8cfeb65a378c8a9bd70f3de188542fc12eeb4a7c0122d509e8  out.txt

awesome work. I'll run your test scripts to confirm, and then merge afterwards

expected output @ latest commit:
b9c8b523cc387472d5b505e47d3f92d8ee62d9151e8754e15afe1fb995aae739  out.txt

repo: tig-foundation/wasmi


text:
DOCS-1427: Fix yaml errors in the bash code block

Product Version(s):

Issue:
https://tigera.atlassian.net/browse/DOCS-1428
https://tigera.atlassian.net/browse/DOCS-1429
Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

@girishshankaran please recheck all the noValidation tags in here - i'd like to understand each one. I don't want to apply noValidation without it really being necessary. In some cases, it may be hiding actual yaml problems and in other cases, I think it could hide other errors that need to be fixed - like leftover liquid syntax from jekyll!

@girishshankaran please recheck all the noValidation tags in here - i'd like to understand each one. I don't want to apply noValidation without it really being necessary. In some cases, it may be hiding actual yaml problems and in other cases, I think it could hide other errors that need to be fixed - like leftover liquid syntax from jekyll!

Sure Doug. The noValidation tag is a temporary one. I may or may not keep it.

source: gharchive/pull-request

authors: doucol girishshankaran

repo: tigera/docs

license_type: permissive

license_source: github-api


text:
Google Analytics 4 is replacing Universal Analytics

Deadline: July 1, 2023
Universal Analytics will be replaced with Google Analytics 4. More information can be found here.

Universal Analytics in env ANALYTICS_VIEW_ID=
Google Analytics 4 in env ???

Hi,
I think this package coud interest you : https://github.com/MyOutDeskLLC/Laravel-Analytics-V4
It could be used in a laravel nova package ;)

Cloud it be as easy as cloning this repo and updating it's composer to include Spatie's updated package?

source: gharchive/issue

authors: Jesus-Rojas RibesAlexandre eugenefvdm krievley

repo: tighten/nova-google-analytics

license: MIT


text:
Add a grafana dashboard

Big thanks for this prometheus exporter. Are you willing to share a grafana dashboard for these metrics?

Hey, I just added what we are using to the dashboards folder, check it out. We only started using grafana recently, and as you can see, my dashboard building skills could be improved. If you make it better looking, feel free to issue a pull request.

Thank you! We also created a Grafana dashboard in the meantime, i will have a look at your solution and see if we can contribute to this repo.

Sounds great, pull requests are welcome. Happy to include your dashboard as well, we can also combine forces. Sorry for the late responses, I pay more attention to the issues of this project. I am super happy that it was useful to someone else as well.

authors: MatthiasVervaet pboros

repo: tigrisdata/fdb-exporter


text:
Email should submit on "enter" on login page

When you click enter/done on the email form for login, the email should automatically submit. Users do not need to then additionally click the continue button. This will improve flow, particularly if the button is covered by the keyboard.

Let's talk about this.
While it might look that it decreases the effort by saving 1 step, my worry is that this will increase the number of wrong emails entered, and then the user will have to keep going back.
For example, I almost always type my personal email on mobile as anna@annastoiova.com instead of anna@annastoilova.com and similar combinations, as my email is long.

okay, will not implement for now. closing

authors: annastoilova mike-audi

repo: tiki/app


text:
Merge branch develop into master

Development Task
Merge develop into master part by part.
Development Progress
The pull requests merged at develop branch are as follows, I would try to apply them into master.

vlog

[ ] https://github.com/tikv/agatedb/pull/84
[ ] https://github.com/tikv/agatedb/pull/88
[ ] https://github.com/tikv/agatedb/pull/98

memtable

[ ] https://github.com/tikv/agatedb/pull/45
[ ] https://github.com/tikv/agatedb/pull/46

levels

[ ] https://github.com/tikv/agatedb/pull/47
[ ] https://github.com/tikv/agatedb/pull/50
[ ] https://github.com/tikv/agatedb/pull/52
[ ] https://github.com/tikv/agatedb/pull/54
[ ] https://github.com/tikv/agatedb/pull/75
[ ] https://github.com/tikv/agatedb/pull/73
[ ] https://github.com/tikv/agatedb/pull/75
[ ] https://github.com/tikv/agatedb/pull/77
[ ] https://github.com/tikv/agatedb/pull/78
[ ] https://github.com/tikv/agatedb/pull/101

txn

[ ] https://github.com/tikv/agatedb/pull/57
[ ] https://github.com/tikv/agatedb/pull/67
[ ] https://github.com/tikv/agatedb/pull/72

agate

[ ] https://github.com/tikv/agatedb/pull/58
[ ] https://github.com/tikv/agatedb/pull/62
[ ] https://github.com/tikv/agatedb/pull/60
[ ] https://github.com/tikv/agatedb/pull/87
[ ] https://github.com/tikv/agatedb/pull/91

bench

[ ] https://github.com/tikv/agatedb/pull/86
[ ] https://github.com/tikv/agatedb/pull/90
[ ] https://github.com/tikv/agatedb/pull/93
[ ] https://github.com/tikv/agatedb/pull/94
[ ] https://github.com/tikv/agatedb/pull/96
[ ] https://github.com/tikv/agatedb/pull/99
[ ] https://github.com/tikv/agatedb/pull/102

ci

[ ] https://github.com/tikv/agatedb/pull/56

@skyzh PTAL, thx.

That's cool! I think it's also okay to port module by module. But sometimes, reviewers might not be knowing what some code is doing without looking ahead for future PRs. I'd be okay with any solution.

authors: GanZiheng skyzh

repo: tikv/agatedb


text:
How to use SDK to access RawKV from outside the k8s cluster?

We have deployed a TiKV cluster on k8s, which can only be accessed from within the k8s cluster. In order to enable access to the TiKV cluster from outside the k8s cluster, we need to configure CoreDNS resolution on each client machine, but this is not elegant. Is there a way to specify the DNS for accessing the k8s internal cluster through the application layer?
Can we implement DNS resolution within the SDK without modifying the system's DNS settings? Would this be a good approach?
This issue is moved by https://github.com/pingcap/tidb-operator/issues/5051

I am not familiar with k8s, but I think maybe you can bind a domain name for each tikv node and PD node so that they can be accessed from outside the k8s cluster. However, exposing internal addresses may raise security concerns. A safer approach may be to start a rawkv proxy service within the k8s cluster to forward rawkv requests.

Currently, we are using proxy forwarding, but it is not suitable for scenarios with high-performance requirements and limited resources.
In the current Tikv on k8s solution, each Tikv has its own domain name, but this domain name can only be resolved through a dedicated DNS server. So I am thinking about adding a configuration DNS server function for the client so that there is no need to change the system configuration to resolve the domain name.

This idea sounds interesting to me. I did some research and found that grpc provides the ability to customize name resolver functions (https://github.com/grpc/grpc-go/blob/master/examples/features/name_resolving/README.md) If possible, I think we can add an option to the client to support a custom name resolver.

If your TiKV is accessbile from a K8 cluster: https://mirrord.dev/

authors: Smityz caniko disksing

repo: tikv/client-go


text:
[Dynamic Regions] v2 60% QPS drop compare with v1 with ~5x delete_skipped-index

Bug Report

What version of TiKV are you using?

master
What operating system and CPU are you using?

x86
Steps to reproduce

run a workload with 2 select, 1 insert and 1 commit
What did you expect?
no performance degradation.
What did happened?

/severity critical

/assign @bufferflies

Changing the memtable of lockcf to 2MB greatly mitigate this problem. Downgrade it to major.

This delete skip happened in lock cf. In dynamic regions, every region store the cf data and compact it, so the frequence of compaction is less than v1. User can downsize the lockcf write-buffer-size to speed up the frequence of the flush and compaction. Here is the test result of modify the write-buffer-size:

We're doing the benchmark on different workloads on the reduced lock-cf size.  If there's a sweet spot size, then this issue can be closed.

It should be greatly mitigated by the new 4MB lock-cf size. Changing it as moderate.

ref #https://github.com/tikv/tikv/pull/15453

close #15132

authors: bufferflies dbsid tonyxuqqi

repo: tikv/tikv


text:
support raftstore prewrite commit cmd

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Proposal: xxx
What's Changed:
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note

TBD

/bench

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Got little improvement, close it.


text:
Existing metadata is not copied to new job

When Connect creates a new job @:
https://github.com/tilialabs/tilia-phoenix-connect/blob/6f4ec26000dfa6c7b58f8a102a11045cbb134497/source.js#L795
it is not copying the existing metadata from the input job. This metadata includes private data and datasets.

Hi Dwight,
Thanks for submitting this issue.  We understand what you're suggesting, but would like to learn more about the use case and urgency if possible.  Also, is this causing problems for any of your customers?
For CSV Import mode there is only a single input file so metadata copying might make more sense.  In direct mode, the input artwork file that triggers work to be done can be fairly random, so copying existing metadata might be less intuitive and/or useful.

yes, we have a couple of customers that are complaining about missing metadata after processing jobs thru Tilia Phoenix element. Both private data and datasets.

@dwightkelly Sorry for the delay on this! After just checking, we do pass through both private data and datasets.
If you're having any issues with this, please reach out to us at support.tilialabs.com.

authors: dwightkelly tiliadavid tilialabs

repo: tilialabs/tilia-phoenix-connect


text:
Gear state and flaps state not changing

Im Try on PMDG 737-800 and default msfs airbus a310.
Gear handle position went up but not the gear. It could be a MSFS issue.
i gave u record on yt with simvar watcher:
https://www.youtube.com/watch?v=SfEjIg99_Tw
my plugins:
-toolbar pushback
-nameplates
i use only Speedlink BLACK WIDOW XE Flightstick as a joystick.

Hello,
Thanks for reporting! Yes, this is a known issue specifically with (3rd party) aircraft that use their own simulation logic, e.g. for hydraulics: they do not react to "simulation variables", as sent via SimConnect.
The good news: I have already started investigating other means to send those "state changes" (keyword: SimConnect "events"), and I have had quite some success already with the PDMG Boeing 737-800 (that I happen to own as well ;)).
Parts of it has just been merged into the "main" branch yesterday, but this is still "work in progress" and systematic testing with other aircraft such as the A310 remains to be done once all changes have fully been implemented.
Also refer to the corresponding announcement e.g. here, toward the end of this posting:
https://forums.flightsimulator.com/t/sky-dolly-v0-13-free-flight-recorder-replay-location-management/405367/58

This is expected to be improved in the upcoming v0.14 release.

im waiting for 0.14 release , thank u for responding :)


text:
Unknown attribute doorLockStatus

Describe the bug
Getting the following attribute error.
Logs
/vehicles/XXXX/domains/access/accessStatus: Unknown attribute doorLockStatus with value locked

Additional context
Using 45.1

Please update to 0.48.1

authors: ColinRobbins tillsteinbach

repo: tillsteinbach/WeConnect-python


text:
Changes in 1.9.4 break WooCommerce My Account Page

Changes in #1813 break the WooCommerce My Account Orders Page by setting defaults on the Query that WooCommerce is not expecting - specifically 'no_found_rows' => true.
When no_found_rows is true the query object's found_posts will ALWAYS be 0 unless we hook in and alter it.
When using the [woocommerce_my_account] shortcode to display the WooCommerce account section they check found_posts
See this template file and this data store function for the relevant lines of WooCommerce code.
Expected behavior
I would expect that the order section displays.
Actual behavior
The orders section displayed no orders, even if there are customer orders in the DB.
Steps to reproduce behavior
Install the latest timber + WooCommerce.
Visit the account section, usually http://mysite.com/my-account/
Visit the orders tab, no orders will be displayed..
Overall, I feel like setting defaults on EVERY WordPress query, as this PR has done, is very dangerous. Anecdotally, we've had to downgrade Timber on other sites recently due to misc issues and weird behaviour, I'd suspect that these issues too were cause by these changes.
Fine to set those defaults for all Timber Queries, but the current method sets it for ALL queries.
What version of WordPress, PHP and Timber are you using?
WordPress 5.1.x, Timber 1.9.4, WooCommerce 3.6.2+
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
Composer

Overall, I feel like setting defaults on EVERY WordPress query, as this PR has done, is very dangerous. Anecdotally, we've had to downgrade Timber on other sites recently due to misc issues and weird behaviour, I'd suspect that these issues too were cause by these changes.

I agree. Timber sets it for queries that come after you use Timber::get_posts(). It shouldn’t be the case when you use new Timber\PostQuery(). For now, can you try to use new Timber\PostQuery() for the page that displays your WooCommerce account page?
Adding a filter that affects global queries can have very strange effects in different environments. So it can very well be that your other issues are caused by this as well.
@jarednova What do you think, should we reverse this breaking change? There have been other issues, like #1961. Or can we find another solution?
Related: #1957

@gchtr It all comes down to one thing - are we using Timber::get_posts as get_posts clone or not. If we are than we should keep it and inform people better. If not - than maybe we should reverse it as it's causing problems.
The last solution would be adding a filter/flag so to user could go back to original Timber::get_posts untill he rewrites his code. And after few version we would deprecated it.

@palmiak But it doesn’t help developers when we introduce a change that on the one hand mimicks WordPress’s behaviour, but on the other hand introduces a breaking change. Simply informing people is not a good solution if it means that everybody would have to check every Timber query on every site to see whether it still does what it should. Yes, it fixes a deviation we had. But for me, this is a breaking change that should probably not have been introduced in a patch version. This is major change.

The last solution would be adding a filter/flag so to user could go back to original Timber::get_posts untill he rewrites his code. And after few version we would deprecated it.

I’d actually prefer to have it the other way round: use a filter that allows you to opt into that behaviour. And then make that behaviour the default in a major version.
What is strange here is also that it seems to affect WooCommerce queries, even though the pre_get_posts filter is removed after it was used once.

Also just in case some people land here via google etc...
Regardless of the outcome of this ticket we were able to fix this via the following code..
<?php

// In your functions.php or similar

function my_namespace_order_query_args( $args ){

    $args['no_found_rows'] = true;

    return $args;

}

add_filter( 'woocommerce_my_account_my_orders_query', 'my_namespace_order_query_args' );

Hey all, I'm just back from vacation and really want to figure out a way to solve this and #1961. It would seem that the best strategy is to "undo" this release is to at once ...

Remove 1.9.4
Re-release 1.9.4 as 1.10.0
Release the current master as 1.10.1

This way, the prior behavior is captured for anyone using WPML/WooCommerce (and other similar plugins) with 1.9.x — we can then investigate the proper final resolution to these issues in 1.10 or 1.11 (and of course, 2.x).
I didn't seen any info in the Semantic Versioning docs about pulling a release. Does anyone know of proper procedure here (esp. for packagist) or even what this is called (Pulling? Undoing? Yanking?)

@jarednova I guess you could remove the 1.9.4 tag manually in Packagist. There’s a delete button next to each tag listed in the right column:

And you can delete releases in GitHub.
But what does speak against releasing a version 1.9.5 as a «hotfix» that reverts the change introduced in 1.9.4? We can still release a version 1.10.0 once we figure out the best way to handle this.

FYI, I'm working on this today with the 1.9.5 hotfix path suggested by @gchtr

Alright, version 1.9.5 is ready as a pre-release:
https://github.com/timber/timber/releases/tag/1.9.5
Here's my plan from here:

Release to WP.org
Publish as an official release
Pull the 1.9.4 release from packagist (I think it makes sense to leave as a record on GitHub)

Timber 2.0 removes the distinction anyway by depreciating Timber::get_posts — so I think the behavior or 1.9.5 should stand for future versions

... just wanted to note the big reminder/lesson. When in doubt, make things a "bigger" release. I thought because this was correcting a bug, to make it just a "patch" version — but in reality, changes in behavior (even to the way they "should" be) is still a change in behavior

@jarednova I think that plan works.
I added the example for the filter in the release notes (https://github.com/timber/timber/releases/tag/1.9.5), because the name of the filter is not the same as the opening description of the pull request.

Alright, version 1.9.5 is ready as a pre-release

It’s now already a released version. Is this intended?

Timber 2.0 removes the distinction anyway by depreciating Timber::get_posts — so I think the behavior or 1.9.5 should stand for future versions

@jarednova I don’t know if understand you correctly when you say «should stand for future versions». If we deprecate Timber::get_posts() in 2.0 (#1957), we would have to deprecate the newly introduced timber/get_posts/mirror_wp_get_posts again, right?

@gchtr composer didn't seem to recognize it as a pre-release, so I went ahead and made it "real" on GitHub too.
In regards to your second question, my point was since we're deprecating Timber::get_posts (at least, right now) — changing the underlying behavior of get_posts seems unnecessary. If someone needed to get get_posts behavior, the preferred method should be to set those arguments as-such. We should also deprecate the newly-introduced filter

authors: aj-adl gchtr jarednova palmiak

repo: timber/timber


text:
2.x: Update escaping docs

Almost identical to https://github.com/timber/timber/pull/1841, so please look there for details.
Differences:

This PR doesn't add a fallback if autoescape is set to true.
This PR adds a note about the change in the Upgrade Guide.

@danielpost Cool, thank you for your help! 👍 I added some improvements to be more explicit in the changes.
When the fallback is merged into master, we’ll have it in 2.x as well.

authors: danielpost gchtr


text:
feat: db provisioner retries connect

refactor tests to localize stubbing
feat: db provisioner retries connect

Marking draft pending integration testing.

Perfection!
2023-03-29T12:10:58.176-07:00 | 2023-03-29T19:10:58.175Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Connecting to database "postgres"
-- | --
  | 2023-03-29T12:10:58.255-07:00 | 2023-03-29T19:10:58.254Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Failed to connect (attempt 1/60): Error: connect ECONNREFUSED 10.18.27.197:5432, sleeping 10000ms
  | 2023-03-29T12:11:08.274-07:00 | 2023-03-29T19:11:08.274Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Failed to connect (attempt 2/60): Error: connect ECONNREFUSED 10.18.27.197:5432, sleeping 10000ms
  | 2023-03-29T12:11:18.285-07:00 | 2023-03-29T19:11:18.285Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Failed to connect (attempt 3/60): Error: connect ECONNREFUSED 10.18.27.197:5432, sleeping 10000ms
  | 2023-03-29T12:11:28.298-07:00 | 2023-03-29T19:11:28.298Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Failed to connect (attempt 4/60): Error: connect ECONNREFUSED 10.18.27.197:5432, sleeping 10000ms
  | 2023-03-29T12:11:38.305-07:00 | 2023-03-29T19:11:38.305Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Failed to connect (attempt 5/60): Error: connect ECONNREFUSED 10.18.27.197:5432, sleeping 10000ms
  | 2023-03-29T12:11:48.314-07:00 | 2023-03-29T19:11:48.314Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Failed to connect (attempt 6/60): Error: connect ECONNREFUSED 10.18.27.197:5432, sleeping 10000ms
  | 2023-03-29T12:11:58.323-07:00 | 2023-03-29T19:11:58.322Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Failed to connect (attempt 7/60): Error: connect ECONNREFUSED 10.18.27.197:5432, sleeping 10000ms
  | 2023-03-29T12:12:08.337-07:00 | 2023-03-29T19:12:08.337Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Connected, validating
  | 2023-03-29T12:12:08.414-07:00 | 2023-03-29T19:12:08.414Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Running: CREATE DATABASE infratest
  | 2023-03-29T12:12:09.605-07:00 | 2023-03-29T19:12:09.604Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Running: CREATE ROLE r_reader
  | 2023-03-29T12:12:09.614-07:00 | 2023-03-29T19:12:09.614Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Running: CREATE ROLE r_writer
  | 2023-03-29T12:12:09.617-07:00 | 2023-03-29T19:12:09.617Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Running: ALTER ROLE r_reader NOBYPASSRLS NOCREATEDB NOCREATEROLE NOLOGIN INHERIT
  | 2023-03-29T12:12:09.634-07:00 | 2023-03-29T19:12:09.634Z 68f43b3d-a23d-4cb5-a60d-3400f848c751 INFO Running: ALTER ROLE r_writer NOBYPASSRLS NOCREATEDB NOCREATEROLE NOLOGIN INHERIT

repo: time-loop/cdk-aurora


text:
use layoutmanager to determine first visible item.  ViewGroup.getChildAt...

...(0) cannot reliably be used to determine this
This fixes a bug where if you notifyItemChanged on an item in the list it will temporarily show a new header since it is initially childAt(0)

Thanks! Looks good to me, can you please adjust the style to match the rest of the code? Specifically, no spaces between parenthesis, and 4 space continuation indent?

I didn't see that you added more commits- sorry! Why did you close?

No worries.  There were some new conflicts with master..I'll fix and resubmit when I have the time.

From: Jacob Tabak notifications@github.com
Sent: Thursday, May 14, 2015 11:17 AM
To: timehop/sticky-headers-recyclerview
Cc: Edward Yee
Subject: Re: [sticky-headers-recyclerview] use layoutmanager to determine first visible item. ViewGroup.getChildAt... (#45)
I didn't see that you added more commits- sorry! Why did you close?

Reply to this email directly or view it on GitHubhttps://github.com/timehop/sticky-headers-recyclerview/pull/45#issuecomment-102069116.

authors: edwardyee jacobtabak

repo: timehop/sticky-headers-recyclerview

license_source: bigquery


text:
Outputting SVG for print

The ability to output charts to SVG for print use

number of columns needs to be specified
height needs to be specified
more details to be collected from Jenny Holly (ST) and Matt Swift (TT)

I'm going to close this because these are mostly taken care of. I've added Jeremy's styles as a new config in 11a41caae9ffe8be678f5ed2a32d323a74a41025, only thing remaining is to fix #42 (dependent upon masayuki0812/c3#895).

Reopening because of recent work to make this better for The Times, notably adding presets and better title options.

authors: aendrew nickpetrie

repo: times/axisJS

license: mit


text:
Update package on pub.dev

Can you update the package on pub.dev soon?

@magginichi ok  i will pub the latest version these days.

For anyone waiting... while waiting:
  webdav: #^1.0.9
    git:
      url: https://github.com/timestee/dart-webdav.git
      ref: 1a70d3f7236484ed170f688980020b344d729d39

authors: avioli magginichi timestee

repo: timestee/dart-webdav

license: Unlicense


text:
Trained your network locally, but my eval. result is not as good as yours

Hi,
Thanks for sharing your wonderful works.
I followed your readme file, and it seems that everything goes well until when I see different evaluation result compared with yours (Ours(K) in table 1 of your paper) when I do evaluate based on locally trained weight. During training, I used the same parameters as suggested on this webpage.
The followings metrics which I got:
abs_rel,     sq_rel,        rms,    log_rms,     d1_all,         a1,         a2,         a3
0.2621,     3.6171,     8.2036,     0.3806,     0.0000,     0.6577,     0.8520,     0.9258
I checked and reviewed procedure, but I cannot find any hint for the above different evaluation result.
Let me know what do you think about it.
Regards,
CJ

How long did you train it for?

Hi,
I ran 20 epochs, and tried training locally twice, but got almost same results.
-- Training messages
Epoch: [20] [ 8522/10062] time: 1.0036/it loss: 0.767
Epoch: [20] [ 8622/10062] time: 0.9790/it loss: 0.807
Epoch: [20] [ 8722/10062] time: 0.9521/it loss: 0.773
When I ran inference with your weight or your ".npy", I got almost the same results as your paper.
CJ

This is consistent with my observation too. The system could start overfitting on KITTI if trained for too long. You could use the validation set to decide the stopping point.

I have the same problem. According to the paper (section4), I chose the check point in 150930 steps to test the result (eigen test split). But the performance is really bad, almost double the errors.
Do you just resize the image to 128x416 first, then feed it to the network? Or you perform some pre-processing?

The best model I had was trained on Cityscapes for ~100K steps and then fine-tuned on KITTI for ~50K steps. This should have been made more clear in the paper.

I faced similar problem too. And there are a more serious problem is about the explainability mask.
The model trained without mask have a result,
abs_rel,     sq_rel,        rms,    log_rms,     d1_all,         a1,         a2,         a3
0.2333,     3.4107,     7.4939,     0.3107,     0.0000,     0.6883,     0.8785,     0.9449
while the model trained with mask (weight is 0.2 from the paper) have a result,
abs_rel,     sq_rel,        rms,    log_rms,     d1_all,         a1,         a2,         a3
0.2474,     4.0113,     7.7726,     0.3197,     0.0000,     0.6722,     0.8746,     0.9430
The both two model are selected around the 200k steps, model_191178.
So this is not consistent with the paper, the result is bad after applying mask.
Could you explain it for me?

I have gotten reports that if you use a Tensorflow version later than 1.0, the results could get somewhat worse (not sure why). Also, I have done some tweaks to the code that improve the results for the non-mask model (see Notes section in README), which might have made the explainability weight non-optimal any more.

authors: Huang-Jin Yuliang-Zou jeongc tinghuiz

repo: tinghuiz/SfMLearner


text:
fix .item() for single item

Before
In [2]: Tensor(10).item()
AttributeError: 'NoneType' object has no attribute 'toCPU'
In [3]: (Tensor(10)+1).item()
Out[3]: 11

Now
In [2]: Tensor(10).item()
Out[2]: 10
In [3]: (Tensor(10)+1).item()
Out[3]: 11

I'm not sure if this is the right fix though....

The new lazy fixed this 🚀

repo: tinygrad/tinygrad


text:
Vue 3 Support

basically, this solves #1123  . After linting the vue docs and migration guide, the only part that actually effects us is that we have Instance-based components instead of global components and the fact that there is  a different place to inject extras instead of manipulating the Vue prototype. This is the initial implementation, and i've made sure nothing is broken from it. However, need to add more testing before pushing out.
@tipsy  a quick review before i continue work would be nice.

Looks good! I'm thinking 3 should be the default from now on. I'm wondering if it should be an int though, vueVersion = 3?

Looks good! I'm thinking 3 should be the default from now on. I'm wondering if it should be an int though, vueVersion = 3?

Well since vue releases come out once ever few years, I don't think it's that worth it - by the time vue4 comes out, vue2 would be deprecated, plus it adds a chance for error.
If we have to do it, maybe I can use an enum ?

We don't have too, I just thought it would read cleaner. "Not vue 3" is theoretically vue 1, 2 and >3 (although I agree it's most likely 2)

@tipsy  I made it an enum at the end, because i felt like that made the most sense(having it as an int is functionally the same, but more error prone on the user's end). Ive also made the vueAppName safer to use with Vue2, so that even if you do change it without changing the Vue Version, the behavior of the dependency resolver stays the same.

So i've added a test to make sure that the dependency resolver actually detects the custom regex based on appName, and it seems to work ok now. @tipsy  do we need more tests or is that enough to cover the difference?

Looks great, I don't think more tests are required. It would be nice if you could update the JavalinVue tutorial with instructions on how to use it with Vue3 :)

@tipsy  Sure! just point me to the tutorial i need to update :D

@TareqK thanks, it's /tutorials/simple-frontends-with-javalin-and-vue (source) - You don't have to change any of the code, just add a small comment for what has to be done to use it with Vue 3.
I also made a small change to get rid of the getter: https://github.com/tipsy/javalin/commit/bd593207036bbc97c46cd926cf63840476c74cc7, let me know if you have any concerns.

The getter code looks fine - makes more sense that doing the If statement each time(tho i was like 99% sure the JIT compiler would just get rid of it on its own haha). Ill update the tutorials hopefully tonight

Ill update the tutorials hopefully tonight

Great, thank you !

authors: TareqK tipsy

repo: tipsy/javalin


text:
🛑 Portfolio is down

In 4ce6748, Portfolio (https://titouan-joseph.cicorella.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portfolio is back up in c35cf84.

repo: titouan-joseph/upptime


text:
Adding missing dependencies

The README additions are based on steps that I needed in order to get it running locally. Let me know if you'd rather expand on them or chuck them entirely.

We should break the README additions out into two separate lists, one for just installing it (which shouldn't require any build steps) and one for developing it (which starts with a git clone and includes npm install and npm start).
RE: Missing dependencies ugh, sorry :( Thanks for catching that.

Something like this? (Having not installed it from npm I'm not 100% sure what you're expecting to see in there)
Installation

npm install anthracite
Rename index-example.html to index.html, changing the <base> tag if necessary
Rename config-example.js to config.js and set your firebase endpoint
npm start
Open http://localhost:9966 in a browser

Development

Create a fork of https://github.com/tivac/anthracite
git clone https://github.com/<username>/anthracite.git
cd anthracite
npm install
Rename index-example.html to index.html, changing the <base> tag if necessary
Rename config-example.js to config.js and set your firebase endpoint
npm run build
npm start
Open http://localhost:9966 in a browser

Installation section shouldn't actually require npm start, that's only if you need bundling. Should just be able to open index.html in a web browser.
Otherwise :+1:

authors: tivac voodoochild

repo: tivac/anthracite


text:
create issue template for new posts

set this up so i can hit new issue and get a post with all the front matter configured already

Fixed!

repo: tjheffner/heffdotdev


text:
🛑 media.tjo.space is down

In 89c25ce, media.tjo.space (https://media.tjo.space) was down:

HTTP code: 0
Response time: 0 ms

Resolved: media.tjo.space is back up in 59d633f after 6 minutes.

repo: tjo-space/status


text:
🛑 media.tjo.space is down

In 0daa581, media.tjo.space (https://media.tjo.space) was down:

HTTP code: 0
Response time: 0 ms

Resolved: media.tjo.space is back up in 81216a1.


text:
How to get a story for random images

How do I test your project on a set of random images using the pretrained models? Say, I have a folder that has 5 images and I need to generate text for them, is that possible?

Of course. However, some code modification is required.
First, follow the instructions in the README.
After that you need to modify the inference.ipynb file so that it can read the images you want.
Please note that we plan to upload additional code for this in the near future.

We tried changing the directory from which it is taking the images as the input but the story which it is generating is not at all relevant to the images

We have tried to run the inference.ipynb file using google colab. Here's a link to the notebook: https://colab.research.google.com/drive/1P9QICcVD15aTXgOQOsa1xktH2C_ddigq?usp=sharing
I have mounted my google drive to the notebook, and a folder named "sample_test" in the drive contains the images that I want to use for testing. Each time I run the code, the output text seems to change but the images remain blacked out. All the necessary files - encoder, decoder, vocab pickle files and the json files are present in the drive.
In the screenshot below you can see the paths set for image_dir and other variables:

The Output:

The images in the sample_test folder are:

I added the 'test.ipynb' file for your case.
But I couldn't test it because I don't have your photo files.
Try generating text using the 'test.ipynb' file.
Please refer to the changed code below.
image_files = ['929665.jpg', '929669.jpg', '929673.jpg', '929678.jpg', '929689.jpg']
for i in range(5):
image = Image.open('sample_test/' + image_files[i]).convert('RGB')
images.append(image)
image = transform_image(image, transform)
image_tensor.append(image)

We implemented test.ipynb and we could generate stories from random images. Thank you so much for helping us out.

Can you please share the number of epochs that you trained the model for, and what were the values of the other parameters to obtain the pretrained model that you have currently provided?

authors: KhushiGala tkim-snu

repo: tkim-snu/GLACNet


text:
Take pair_selector as arguments

Summary
Take pair_selector as arguments.
You can customize it. (e.g. by giving lambda functions.)
ref #38, #88

Codecov Report

Merging #91 (a9ffa09) into develop (90a4afd) will increase coverage by 0.75%.
The diff coverage is 97.57%.

@@             Coverage Diff             @@
##           develop      #91      +/-   ##
===========================================
+ Coverage    92.37%   93.12%   +0.75%
===========================================
  Files           18       18
  Lines         1953     2166     +213
===========================================
+ Hits          1804     2017     +213
  Misses         149      149

Impacted Files
Coverage Δ

ssspy/bss/ilrma.py
95.70% <97.28%> (+1.63%)
:arrow_up:

ssspy/bss/__init__.py
100.00% <100.00%> (ø)

ssspy/bss/fdica.py
91.71% <100.00%> (+0.06%)
:arrow_up:

ssspy/bss/iva.py
94.49% <100.00%> (+0.02%)
:arrow_up:

ssspy/utils/dataset/__init__.py
100.00% <100.00%> (ø)

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 c125fa7...a9ffa09. Read the comment docs.


text:
add z_stack options

add to the MDA GUI the possibility to select different z_stack mode from useq MDASequence ( "TopBottom", "RangeAround" and "AboveBelow").

@tlambert03 fixed


text:
React Storybook

https://github.com/kadirahq/react-storybook
Just an idea. Could be good for creating examples.

Hi @HriBB, yes, I also believe it could be great, especially for the demos/examples. But I wonder how easy it is to customize the generated website to make it look the way you want.

Not sure. It's just an idea. I've been playing around with it and it's really cool because you can easily create different scenarios of the same component.
I see they have storybook-ui. Maybe it's possible to create a custom UI like react-mdl-storybook-ui
Will do some research when I find some time.

I've been playing around with it and it's really cool because you can easily create different scenarios of the same component.

I agree, I've also been playing with it for another UI library and it works very well. I'm really interested in using something like this (or like carte-blanche) for react-mdl if we can customize the generated website.

authors: HriBB tleunen

repo: tleunen/react-mdl


text:
Error when running on an Apple Virtual Machine

I am trying to run this on a macOS Virtual Machine to monitor usage; the base machine is a mac mini with an M1 chip. I am getting the error below.
min@admins-Mac ~ % sudo asitop
Password:

ASITOP - Performance monitoring CLI tool for Apple Silicon
You can update ASITOP by running `pip install asitop --upgrade`
Get help at `https://github.com/tlkh/asitop`
P.S. You are recommended to run ASITOP with `sudo asitop`

[1/3] Loading ASITOP

[2/3] Starting powermetrics process

[3/3] Waiting for first reading...

ERROR: cannot find the IO registry entry for IODeviceTree:/arm-io/pmgr
ERROR: cannot find the IO registry entry for IODeviceTree:/arm-io/pmgr
Traceback (most recent call last):
  File "/opt/homebrew/lib/python3.9/site-packages/asitop/utils.py", line 18, in parse_powermetrics
    cpu_metrics_dict = parse_cpu_metrics(powermetrics_parse)
  File "/opt/homebrew/lib/python3.9/site-packages/asitop/parsers.py", line 79, in parse_cpu_metrics
    cpu_metrics = powermetrics_parse["processor"]
KeyError: 'processor'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/homebrew/bin/asitop", line 8, in <module>
    sys.exit(main())
  File "/opt/homebrew/lib/python3.9/site-packages/asitop/asitop.py", line 121, in main
    ready = get_reading()
  File "/opt/homebrew/lib/python3.9/site-packages/asitop/asitop.py", line 118, in get_reading
    ready = parse_powermetrics(timecode=timecode)
  File "/opt/homebrew/lib/python3.9/site-packages/asitop/utils.py", line 28, in parse_powermetrics
    cpu_metrics_dict = parse_cpu_metrics(powermetrics_parse)
  File "/opt/homebrew/lib/python3.9/site-packages/asitop/parsers.py", line 79, in parse_cpu_metrics
    cpu_metrics = powermetrics_parse["processor"]
KeyError: 'processor'
admin@admins-Mac ~ %

It will not work in a VM. The VM doesn’t expose such information from the
base system.
On Tue, 19 Apr 2022 at 10:32 AM, Anahit Sarao @.***>
wrote:

I am trying to run this on a macOS Virtual Machine to monitor usage; the
base machine is a mac mini with an M1 chip. I am getting the error below.
@.*** ~ % sudo asitop
Password:
ASITOP - Performance monitoring CLI tool for Apple Silicon
You can update ASITOP by running pip install asitop --upgrade
Get help at https://github.com/tlkh/asitop https://github.com/tlkh/asitop
P.S. You are recommended to run ASITOP with sudo asitop
[1/3] Loading ASITOP
[2/3] Starting powermetrics process
[3/3] Waiting for first reading...
ERROR: cannot find the IO registry entry for IODeviceTree:/arm-io/pmgr
ERROR: cannot find the IO registry entry for IODeviceTree:/arm-io/pmgr
Traceback (most recent call last):
File "/opt/homebrew/lib/python3.9/site-packages/asitop/utils.py", line 18, in parse_powermetrics
cpu_metrics_dict = parse_cpu_metrics(powermetrics_parse)
File "/opt/homebrew/lib/python3.9/site-packages/asitop/parsers.py", line 79, in parse_cpu_metrics
cpu_metrics = powermetrics_parse["processor"]
KeyError: 'processor'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/homebrew/bin/asitop", line 8, in
sys.exit(main())
File "/opt/homebrew/lib/python3.9/site-packages/asitop/asitop.py", line 121, in main
ready = get_reading()
File "/opt/homebrew/lib/python3.9/site-packages/asitop/asitop.py", line 118, in get_reading
ready = parse_powermetrics(timecode=timecode)
File "/opt/homebrew/lib/python3.9/site-packages/asitop/utils.py", line 28, in parse_powermetrics
cpu_metrics_dict = parse_cpu_metrics(powermetrics_parse)
File "/opt/homebrew/lib/python3.9/site-packages/asitop/parsers.py", line 79, in parse_cpu_metrics
cpu_metrics = powermetrics_parse["processor"]
KeyError: 'processor'
@.*** ~ %
—
Reply to this email directly, view it on GitHub
https://github.com/tlkh/asitop/issues/28, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJIWUKLG5J6QKQW3TNUT43VFYLMXANCNFSM5TXMUEIA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

repo: tlkh/asitop


text:
groups: editing channel options permanently displays options button

Describe the bug, optionally with screenshots
The button to edit channel options only appears on a channel when you hover over it. However, if you click the button and edit the channel options, once you exit, the button is now permanently displayed. This can affect multiple channels at one time.
Screenshot
To Reproduce
Steps to reproduce the behavior:

Go to any group that you admin
Go to the "member & group info" page
Go to channels
Hover over a channel to bring up the options on the right-hand side
Click the options
Click "edit channel"
Click cancel in the new pop-up
See error

Expected behavior
No options buttons should be displayed on the right-hand side, since after clicking cancel the mouse cursor is not covering any channels.
Additional context:

Ship type = planet
Instance type = self-hosted
Chormium-based browser on Pop!_OS 20.10

We're renovating the channel admin screen shortly anyway, keeping this around so we're aware in the redesign.

Still a think @ashelkovnykov ?

@jamesacklin Currently traveling, will let you know shortly

@jamesacklin No, the interface has changed to make this no longer relevant

authors: ashelkovnykov jamesacklin

repo: tloncorp/landscape-apps


text:
Add scheduled task "cron" support

Allow the config to automatically execute the Lambda. The event passed to the Lambda is very specific, so it needs to be re-created for the scheduled invocation. Or maybe a special event gets passed that the aegis Lambda handler can look for and process separately.
It would be nice to keep the same semantics for handling these invocations. Something like:
router.Handle("CRON", handlerFn)
Or:
cron.Handle(handleFn)
There may be several cron tasks to perform so there may even be a name in the event that helps handle each one. The Go code won't necessarily be configuring and setting up the actual schedule (that's best left to the YML config) but it can handle the tasks in a conventional manner while co-existing with the rest of the app.
Or...maybe the Go application code does do the scheduling and defines everything. Then when calling up and with a single config parameter of cron: true the Lambda will be invoked in a special manner to then execute all of the cron configurations and set them up.
There's many ways to do it, I'm not sure yet how to handle it just yet...But it's a very nice feature. It would be nice to build into configuration to avoid additional commands on the CLI.

Create a tasks folder within app (where aegis command runs alongside source code). Add JSON files with the following contents:
{
    "schedule": "rate(1 hour)",
    "input": {
        "_taskName": "test",
        "foo": "bar"
    }
}

Enjoy. Schedule updates on each deploy as it gets changed. _taskName is conventional and allows Tasker handlers to handle specific tasks by name. Tasker like Router also has a "fall through" handler that catches everything. At that point, the catch all handler function could look at the input map and do whatever it needs to do. So tasks by name are completely optional.
Task handlers will get a map[string]interface{} that is this input key value from each of the JSON files within the tasks directory.

repo: tmaiaroto/aegis


text:
implementation of iterative forward pass

In order to make a forward pass, in the current mainstream version, you need the whole sequence at once. I have implemented a function that takes a single SequenceElem (aka a Mat), performs the forward pass and stores the input/output for a possibly subsequent call to backward().
the function also takes a bool parameter "reset" which, if it is set to True, resets the state of the network and clears all vectors.

I'm not sure yet that this is the right way of supporting very long sequences. I'll have to think about it some more.

This iterative version is not meant to solve the issues concerning very long sequences. It is mainly meant to handle the case when you do not have the whole input, e.g., when you would like to feed the network with its own output or when the input at time t+1 depends directly or undirectly on the output at time t. I also agree with you that there is probably a most efficient (memory-wide) way to handle this expecially if, as you mentioned, you have to deal with streaming data. In that case, it would be probably better to further differentiate between the learning and "prediction" phases and just store the current state of clstm cells. In this PR i have just taken the most conservative path and tried to change as little as possible the internal architecture and to provide a function that can be used along with the standard backward pass.

I've merged the Tensor branch into "master"; have another look. CLSTM really isn't set up for changing the way recurrece works; for OCR that's not needed, but it means it's not a good framework for doing some of the new sequence models people have been experimenting with (for example for language modeling).

authors: apbard tmbdev

repo: tmbdev/clstm


text:
Is there any way to combine language models?

HI i Have set saving frequency of 200 i got 10's of models, is there any way to combine the models,
If the last file saved in last iteration should be taken as final?
Also I'm getting error "index 60 is out of bounds for axis with size 60" when I try to load existing model and train.
Kindly guide me as ocropus linegen generation png images like

but actual text is చౌపాఈ....

Also I'm getting error "index 60 is out of bounds for axis with size 60" when I try to load existing model and train.

Any one kindly guide me i am using Telugu uni code Its showing fine in ground truth text file but showing the image as above..

Please provide more information: explain step-by-step and in details such that it is reproducible for anyone else. Don't ignore all points from the issue template, cf. https://github.com/tmbdev/ocropy/issues/168.
Moreover, it looks for me that you have two questions about training and one question about line generation, which may be independent of each other.
Please copy the exact commands you use here and copy the exact error message with all intermediate messages here. Maybe someone can help you then.

@zuphilip Thanks for your response.

I am trying to train Ocropus in telugu (unicode language) while training I have a text file containing Telugu text Im trying to generate ground truth and bin.png images using ocropus-linegen using command
ocropus-linegen -t tests/sri.txt -f tests/mallanna.ttf
The images generated is showing consonant seperately and Vowel Seperate in Telugu this both together will give correct charecter,In gt its giving exact word as desired .plz find the above image and text for ref.

2.I have trained Telugu with images and gt txt and I set a saving frequency of 200 iterations so i have about 15-16 models of telugu .Will i have to take last iteration saved model or is there any way to combine all the models?
3.When i try to train on the top of telugu language model i previously generated using --load option
Its throwing error "index 60 is out of bounds for axis with size 60"
I am using the command "ocropus-rtrain --load tel.pyrnn.gz -o tel-plus *.bin.png -c *.gt.txt -f 200 -S200"

The problem point 3 is due to addition of more training data than previously trained data

2.) Normally, it is expected that the last model you obtain is the best one, because it is trained the most. However, you should evaluate your models on some evaluation data. Then you will have for each model an error rate and you can stop if the error is not changing or you are happy with the current error rate. You can for example look at https://github.com/jze/ocropus-model_oesterreich-ungarn for a similar example.
It seems for me that 15*200 = 3000 iterations might be not enough to train a model, especially if it is a completely new language with (a lot of?) different characters.

3.) Shouldn't you provide also the character set with -c as discussed in the other issue? If the error still exists, then please show all lines of the error message as well as your command you used.

repo: tmbdev/ocropy


text:
Is it possible to train ocropy for any other language?

Basically ta  ocropy is for recognition of english characters but is it possible to use it for any other language?

Yes, that is possible and besides English there is also the (official) Fraktur model which is trained to another script. Some more models are listed in the wiki: https://github.com/tmbdev/ocropy/wiki/Models

Maybe just note: Ocropus does not have any language modeling at the moment, the models are for scripts e.g. the letters of a language.

Thank you very much for quick reply.

authors: codeheadshopon zuphilip


text:
AttributesTable: remove from results

Hey @tmcgee!
Is there a nice way to remove a record from results? Let's say that I did spatial Search and then I want to remove one or some of the resulted records, maybe through a custom column or context menu in hovered line of table. I know how to "inject" custom columns there, my problem is to interact with the table data.
Thanks!

Maybe with populateGrid topic publication? Or there is a more polished way?

I digged into AttributesTable stuff and now I'm working to include this option:

The idea is to remove graphics from results (highlights and all) and the record from table.
Valid?

@carrbrpoa Using a menu option is what I would do though not sure that a Remove option belongs in the Clear menu. Perhaps create a new separate button? @roemhildtg started a discussion about adding custom buttons is in issue #69.

Actually I intend to contribute this feature to AttributeTable, others could benefit from it.
The goal is to clear selected lines of results grid and purple/highlighted/whatever circles around the found features. I could put it in another menu, no problem, just seemed ok to me in Clear.

authors: carrbrpoa tmcgee

repo: tmcgee/cmv-widgets


text:
Update textarea to support sidecar screen reader support

Added a visually hidden container that is updated dynamically after a slight pause
Hide visible container from screen readers
Updated AC and text content in the page
Adjusted JS to accommodate the new approach

@silverli Thank you for the review and great ideas - I've addressed them :) take a peek!


text:
Send ips only on change

Отправлять ips, только когда он меняется

Fixed in scope of other issue...

repo: tmptrash/jevo


text:
Suggestion: Web Interface

To make this more friendly to non-developers a web interface is probably the best way to go in my opinion. Maybe flask or django?

I agree. I think Flask would be best.

My initial thought is to completely decouple this code from any future UI. Maybe even have the UI in its own repo?
This repo could serve as a restful-like API that could be consumed by any UI.
I'm open to thoughts on this though.

I've played with Django Rest Framework in the past and it has served me well.

Here's an example of how you might combine Django with a UI component: https://github.com/geezhawk/drf-react

authors: AidanHanda huangsam tmthyjames

repo: tmthyjames/Achoo


text:
TDCAction / Parcelable fix

Update the TDCAction's constructor and writeToParcel methods so the behavior description gets set when created from a parcel

:+1:

authors: Revenaunt bradmontgomery

repo: tndatacommons/android-app


text:
Add readOnly option

This is such a neat project!
I found myself needing to open a database as read-only, so I added the option here.

Thanks for the PR. I added the option with tests and docs in #39. I will release it soon.


text:
DrRacket without debugging

Is DrRacket fast enough without debugging info? What things need to be disabled?
Can Forge disable debugging etc. automatically?

Closing issue since we switched mainly to VSCode

authors: bennn tnelson

repo: tnelson/Forge


text:
fix(Generator): Bug empty release version

Bug empty release version
see #25
close #25

Coverage increased (+0.02%) to 99.006% when pulling f01bf52c7a40eea8659414dcb838806fa18fcc2c on fix/Generator/Bug-empty-release-version into cbb0efb7d6cb58075f91224fee429f91a94a52d5 on master.

authors: coveralls toancong

repo: toancong/clgt


text:
Channels stuck in a 'pending' state

I'm occasionally seeing messages "Connection not established. Add message to queue.", which is based off the channel still being in a 'pending' state, meaning the code never received a 'subscribed' message from the server.
BUT I am seeing the ActionCable server did send that subscribed message! I'm not sure why py-actioncable isn't receiving this subscribed message, and therefore pulling the channel out of 'pending'.
I see this issue locally and when talking to a dockerized server. I'd love to provide sample code, but it's a little hard to reproduce. This dance works flawlessly the first time, and generally happens when there is an unhealthy connection ping, and py-actioncable attempts to reconnect.
Do you get this issue as well sometimes?

No, I don't have this problem. Do you have upgraded to the most recent version?

Hi! Iḿ having a similar problem, i get connected to my localhost server but my subscription is stuck at pennding state, so i do not recieve any messages nor can send them.
`from actioncable.connection import Connection
from actioncable.subscription import Subscription
connection = Connection(url='ws://localhost:3000/cable', origin='http://localhost:3000')
connection.connect()
sleep(3)
print(connection.connected) #this is True
subscription = Subscription(connection, identifier={'channel': 'RaspiCommChannel'})
subscription.create()`
If I check subscription state is 'pending' allways.
I try it from python console, using Python 3.7.2.
Can you help me please? Thanks!

authors: eterrones nicw tobiasfeistmantl


text:
Generating graphics

The most annoying thing about your distribution = which is otherwise wonderful - is the need to have to wait for it to graciously generate the graphics. This is a pain... reboot the machine?? Wait wait wait... Temperature detector decides to give up?? Wait wait wait. Still not sure why the detector decides to give up but it seems to, I then fiddle with the 'hat' and it springs into life again.
Surely it's possible to allow the standard 'UNIX' thing that SIGHUP is used to make daemons do things that are useful. In this case SIGHUP generates the images and there's a flag to the binary that  just sends the signal to the running daemon.
This is a really missing 'standard' feature (i.e it's a bad bug not a feature). Assuming, of course that your development environment can handle UNIX signals and process them then it should not be a big change. Failing that can we have  a standalone tool to make these things??

honestly, the graphs leave much to be desired, if you have probes with a wide temperature differential the graphs distort the X,Y, really bad, it compresses the time because its a static image.  Toby, I recommend looking at brewPI , and see how they do there graphs, its open source and they are really nice and you can zoom in and out dynamically C. and F.  looks great on moble and in a brouser, You can name probes and export logging ,  please do look and see if there is some code that could make the TM better,   here is an example of the graphs https://pbs.twimg.com/media/BZGPxQzCYAAtfBP.jpg

In the dynamic chart, you can switch off specific probe lines by clicking on the legend which may help with the disparate temps. The static charts are a by product of using RRD as the data store. I have plans to replace this and the charts but have limited time to work on it.
But hey, if you don’t like the software, you have other options - you could find an alternative or write something yourself. Even better you could build a new charting component (I think BrewPi uses Dynchart) and contribute directly to this project.

Hi There!
My Temp-machine isn1T generate chart's...
Here's my log:

Mon 20-Apr-202014:54:37.103[sun.management.jmxremote]CONFIGJMX Connector ready at: service:jmx:rmi:///jndi/rmi://raspberrypi:34037/jmxrmi
Mon 20-Apr-202014:54:44.189[main]INFOStarting temperature-machine (server mode)...
Mon 20-Apr-202014:54:44.245[main]INFOStarting Discovery Server, listening for 'raspberrypi'...
Mon 20-Apr-202014:54:44.294[main]INFOWriting to the RRD every 30 seconds (sample times may be off by +/- 30 seconds, maybe a little more)
Mon 20-Apr-202014:54:44.297[temperature-machine-discovery-server-1]INFOListening for broadcast messages...
Mon 20-Apr-202014:54:46.282[main]INFOMonitoring sensor file(s) on 'raspberrypi'
/sys/bus/w1/devices/28-011913b9b6b1/w1_slave
Mon 20-Apr-202014:54:46.373[temperature-graphing-thread-2]DEBUGGenerating RRD chart for last 7 days
Mon 20-Apr-202014:54:46.378[temperature-graphing-thread-3]DEBUGGenerating RRD chart for last 30 days

What should be the problem? It's measure the the temperature good, beacuse these part is works.
Thansk!

authors: DemBones78 pcollinson tobyweston ukjoci

repo: tobyweston/temperature-machine


text:
ERROR in ./node_modules/vuejs-smart-table/src/main.js

I Follow the installation guide.
When I run my project I get the following error :
`ERROR in ./node_modules/vuejs-smart-table/src/main.js
Module not found: Error: Can't resolve './SmartPagination' in '/Users/my/dev/projects/floxx/FloxxFrontApp/node_modules/vuejs-smart-table/src'
@ ./node_modules/vuejs-smart-table/src/main.js 4:0-47 6:0-11:1 18:38-53
@ ./src/app/index.js
ERROR in ./node_modules/vuejs-smart-table/src/main.js
Module not found: Error: Can't resolve './VTable' in '/Users/my/dev/projects/floxx/FloxxFrontApp/node_modules/vuejs-smart-table/src'
@ ./node_modules/vuejs-smart-table/src/main.js 1:0-29 6:0-11:1 15:29-35
@ ./src/app/index.js
ERROR in ./node_modules/vuejs-smart-table/src/main.js
Module not found: Error: Can't resolve './VTh' in '/Users/my/dev/projects/floxx/FloxxFrontApp/node_modules/vuejs-smart-table/src'
@ ./node_modules/vuejs-smart-table/src/main.js 2:0-23 6:0-11:1 16:26-29
@ ./src/app/index.js
ERROR in ./node_modules/vuejs-smart-table/src/main.js
Module not found: Error: Can't resolve './VTr' in '/Users/my/dev/projects/floxx/FloxxFrontApp/node_modules/vuejs-smart-table/src'
@ ./node_modules/vuejs-smart-table/src/main.js 3:0-23 6:0-11:1 17:26-29
@ ./src/app/index.js`
Any idea ?
Many thanks

same here.
Adding the file extension .vue in all those errornous import statements inside ./node_modules/vuejs-smart-table/src/main.js the errors disappear. Maybe this should be considered as the fix.

as this maybe related to webpack which I am using: adding the extensions to be resolved automatically in the webpack config like this:
resolve: {
    extensions: ['.vue']
},

also resolves the issue. However the clean approach is to add those extensions in main.js IMHO.

Thank you for your help @derMart, I will add those extensions to the main.js to avoid this problem in the future

authors: Fabszn derMart tochoromero

repo: tochoromero/vuejs-smart-table


text:
Dynamic Bridge crashes with services

When I run the ros1 dynamic bridge and then run a ros1 node that has a service, the bridge crashes.
Steps to reproduce:
Terminal 1 -
source /opt/ros/kinetic/setup.bash
roscore
Terminal 2 -
source /opt/ros/kinetic/setup.bash
source ros2 bouncy
ros2 run ros1_bridge dynamic_bridge -- --bridge-all-2to1-topics
Terminal 3 -
source /opt/ros/kinetic/setup.bash
rosrun turtlesim turtlesim_node
Another option for terminal 3, which is the ros1 node that has a service, is to run rviz (this is how this bug was originally discovered.
The failure mode is for the terminal running the dynamic_bridge to output something as follows:
ros2 run ros1_bridge dynamic_bridge -- --bridge-all-2to1-topicsCreated 2 to 1 bridge for service /clear
Created 2 to 1 bridge for service /reset
Created 1 to 2 bridge for service /clea
Created 1 to 2 bridge for service /rese
Created 1 to 2 bridge for service /cle
Created 1 to 2 bridge for service /res
Created 1 to 2 bridge for service /cl
Created 1 to 2 bridge for service /re
Created 1 to 2 bridge for service /c
Created 1 to 2 bridge for service /r
terminate called after throwing an instance of 'rclcpp::exceptions::InvalidServiceNameError'
what():  Invalid service name: topic name must not end with a forward slash:
'/'
^
This is high priority, as we require the dynamic bridge for key functionality. Our only workaround currently is to not use coredx.

any update on this?


text:
Wrong file identifier

Have an odd issue.
Searcharr has been running fine, however i noticed a group chat where there was no response. so i went looking for where the issue is. The whoile setup has not changed at all so not sure where the issue lies.
I have tested several /movie and /tv commands and most are fine.
however 2 examples i have for now "/movie vortex" and "/movie the last detail" both give the following error in the logs
Caught error: Wrong file identifier/http url specified
Cant work out why however

I can reproduce the error, but I don't immediately see the cause. I will have to research further.

I tried to capture some logs of the issue for deeper analysis, but I can no longer reproduce the error. Please try again and let me know if you are still seeing the problem.

A user in the Telegram group reported this issue when searching /movie groundhogs and /movie flux gourmet, which are both currently causing the error for me. I hope to research deeper with these examples.

It looks like Telegram is reporting a different error message than before when it doesn't like a movie/series poster image. I am updating Searcharr to use a default poster image when this new error message is encountered. The fix will be in v2.1.4 probably later today, and it's being built in the beta branch right now.

fixed in v2.1.4

Yep fixed, thanks

Happening again:
2023-05-19 05:21:37,794 -    DEBUG - searcharr(140093794192184):1405 - Stripped entities from message [/movie Clerks 3]: [Clerks 3]
2023-05-19 05:21:37,794 -    DEBUG - searcharr.radarr(140093794192184):146 - Submitting GET request: [http://localhost:7878/api/v3/movie/lookup?apikey=redacted&term=Clerks%203]
2023-05-19 05:21:38,016 -    DEBUG - searcharr(140093794192184):1691 - Database connection established [/app/data/searcharr.db].
2023-05-19 05:21:38,018 -    DEBUG - searcharr(140093794192184):1691 - Database connection established [/app/data/searcharr.db].
2023-05-19 05:21:38,019 -    DEBUG - searcharr(140093794192184):1442 - Executing query: [INSERT OR REPLACE INTO conversations (id, username, type, results) VALUES (?, ?, ?, ?)] with args: [('ce3d39b9', 'savagecore', 'movie', '[{"title": "The Clerks 3 Documentary", "overview": "Documentary on the making of Clerks 3", "status": "announced", "inCinemas": null, "remotePoster": "https://image.tmdb.org/t/p/original/v1J7hfij55BN5ptwSvCpXRtEBcY.jpg", "year": 2022, "tmdbId": 1058229, "imdbId": "tt23117900", "runtime": 96, "id": null, "titleSlug": "1058229", "images": [{"coverType": "poster", "url": "/radarr/MediaCoverProxy/a6876410c516433a4af04755a751827f4c36945f21bdcb45698db22c28a58987/v1J7hfij55BN5ptwSvCpXRtEBcY.jpg", "remoteUrl": "https://image.tmdb.org/t/p/original/v1J7hfij55BN5ptwSvCpXRtEBcY.jpg"}]}, {"title": "We\'re Not Even Supposed To Be Here Today: 3 Decades of Clerks Documentary", "overview": "A documentary covering 3 decades of Clerks films", "status": "released", "inCinemas": null, "remotePoster": "https://image.tmdb.org/t/p/original/thJxfcv6pCUamVxCAsHloClijmw.jpg", "year": 2022, "tmdbId": 1063682, "imdbId": null, "runtime": 75, "id": null, "titleSlug": "1063682", "images": [{"coverType": "poster", "url": "/radarr/MediaCoverProxy/42c9073a12742c752bf132ce723844147d5ac9ac5260de8f43f2aaa5a3c550f7/thJxfcv6pCUamVxCAsHloClijmw.jpg", "remoteUrl": "https://image.tmdb.org/t/p/original/thJxfcv6pCUamVxCAsHloClijmw.jpg"}]}, {"title": "Clerks III", "overview": "After narrowly surviving a massive heart attack, Randal enlists his old friend Dante to help him make a movie immortalizing their youthful days at the little convenience store that started it all.", "status": "released", "inCinemas": "2022-09-16T00:00:00Z", "remotePoster": "https://image.tmdb.org/t/p/original/apzIqZIQLc8fNx5nbbcSSfPFtax.jpg", "year": 2022, "tmdbId": 635891, "imdbId": "tt11128440", "runtime": 100, "id": 74, "titleSlug": "635891", "images": [{"coverType": "poster", "url": "/radarr/MediaCover/74/poster.jpg?lastWrite=638092677181546378", "remoteUrl": "https://image.tmdb.org/t/p/original/apzIqZIQLc8fNx5nbbcSSfPFtax.jpg"}, {"coverType": "fanart", "url": "/radarr/MediaCover/74/fanart.jpg?lastWrite=638039944807429529", "remoteUrl": "https://image.tmdb.org/t/p/original/5tqWi8wEV88meo6OAC6N1hTdNrj.jpg"}]}]')]
2023-05-19 05:21:38,071 -    ERROR - searcharr(140093794192184):1339 - Caught error: Wrong file identifier/http url specified

Happening again:
2023-05-19 05:21:37,794 -    DEBUG - searcharr(140093794192184):1405 - Stripped entities from message [/movie Clerks 3]: [Clerks 3]
2023-05-19 05:21:37,794 -    DEBUG - searcharr.radarr(140093794192184):146 - Submitting GET request: [http://localhost:7878/api/v3/movie/lookup?apikey=redacted&term=Clerks%203]
2023-05-19 05:21:38,016 -    DEBUG - searcharr(140093794192184):1691 - Database connection established [/app/data/searcharr.db].
2023-05-19 05:21:38,018 -    DEBUG - searcharr(140093794192184):1691 - Database connection established [/app/data/searcharr.db].
2023-05-19 05:21:38,019 -    DEBUG - searcharr(140093794192184):1442 - Executing query: [INSERT OR REPLACE INTO conversations (id, username, type, results) VALUES (?, ?, ?, ?)] with args: [('ce3d39b9', 'savagecore', 'movie', '[{"title": "The Clerks 3 Documentary", "overview": "Documentary on the making of Clerks 3", "status": "announced", "inCinemas": null, "remotePoster": "https://image.tmdb.org/t/p/original/v1J7hfij55BN5ptwSvCpXRtEBcY.jpg", "year": 2022, "tmdbId": 1058229, "imdbId": "tt23117900", "runtime": 96, "id": null, "titleSlug": "1058229", "images": [{"coverType": "poster", "url": "/radarr/MediaCoverProxy/a6876410c516433a4af04755a751827f4c36945f21bdcb45698db22c28a58987/v1J7hfij55BN5ptwSvCpXRtEBcY.jpg", "remoteUrl": "https://image.tmdb.org/t/p/original/v1J7hfij55BN5ptwSvCpXRtEBcY.jpg"}]}, {"title": "We\'re Not Even Supposed To Be Here Today: 3 Decades of Clerks Documentary", "overview": "A documentary covering 3 decades of Clerks films", "status": "released", "inCinemas": null, "remotePoster": "https://image.tmdb.org/t/p/original/thJxfcv6pCUamVxCAsHloClijmw.jpg", "year": 2022, "tmdbId": 1063682, "imdbId": null, "runtime": 75, "id": null, "titleSlug": "1063682", "images": [{"coverType": "poster", "url": "/radarr/MediaCoverProxy/42c9073a12742c752bf132ce723844147d5ac9ac5260de8f43f2aaa5a3c550f7/thJxfcv6pCUamVxCAsHloClijmw.jpg", "remoteUrl": "https://image.tmdb.org/t/p/original/thJxfcv6pCUamVxCAsHloClijmw.jpg"}]}, {"title": "Clerks III", "overview": "After narrowly surviving a massive heart attack, Randal enlists his old friend Dante to help him make a movie immortalizing their youthful days at the little convenience store that started it all.", "status": "released", "inCinemas": "2022-09-16T00:00:00Z", "remotePoster": "https://image.tmdb.org/t/p/original/apzIqZIQLc8fNx5nbbcSSfPFtax.jpg", "year": 2022, "tmdbId": 635891, "imdbId": "tt11128440", "runtime": 100, "id": 74, "titleSlug": "635891", "images": [{"coverType": "poster", "url": "/radarr/MediaCover/74/poster.jpg?lastWrite=638092677181546378", "remoteUrl": "https://image.tmdb.org/t/p/original/apzIqZIQLc8fNx5nbbcSSfPFtax.jpg"}, {"coverType": "fanart", "url": "/radarr/MediaCover/74/fanart.jpg?lastWrite=638039944807429529", "remoteUrl": "https://image.tmdb.org/t/p/original/5tqWi8wEV88meo6OAC6N1hTdNrj.jpg"}]}]')]
2023-05-19 05:21:38,071 -    ERROR - searcharr(140093794192184):1339 - Caught error: Wrong file identifier/http url specified

The error message in your log is exactly the one that I added. Please ensure you are running Searcharr v2.1.4+ @SavageCore


text:
Improve performance  by matchaddpos()

This patch improves performance by using matchaddpos() function, which is available Vim 7.4.330 or later, if available.
http://vim-jp.org/vimmagazine/2014/06/30/vimmagazine.html
matchaddpos() is significantly faster than matchadd().
https://github.com/vim/vim/blob/master/runtime/doc/eval.txt#L4442
Vim is particularly faster when moving the cursor.
benchmark
function! Test()
  call cursor(1, 1)
  let t = reltime()
  for i in range(1, line('$'))
    call cursor(i, 1)
    redraw
  endfor
  echom reltimestr(reltime(t))
endfunction

function! SetBuf()
  for _ in range(1, 100)
    call append('$', 'a, b, c, d, e, f, g, h, i, j, k, l = nil')
  endfor

  let g:ruby_hl_lvar_hl_group = 'Error'

  set rtp+=~/.vim/bundle/ruby_hl_lvar.vim/

  filetype plugin indent on
  syntax enable
endfunction

call SetBuf()

Save the above as test.vim, and run the following command.
vim -u test.vim -N -c 'set ft=ruby' -c 'call Test()'

Before patch(ef2b4a2486d1f84e5e056ac302551afa66c2f5d6)
1.492471 sec
After patch
0.095837 sec

Seems OK :+1:

authors: pocke todesking


text:
Rename dispatch to send for consistency with TCA

Summary
As discussed in #23, using send instead of dispatch would be beneficial for individuals and teams that have previous experience with TCA (The Composable Architecture). This PR changes the name to send, deprecating the dispatch methods.
Relationships
Closes #23
Technical considerations

Tests
Existing tests have been updated. No new tests have been added since this is just a rename that doesn't introduce any new behavior.
Review pointers
As suggested by @semanticer, @Deprecated annotations were added, I hope I did them correctly.

Hi @semanticer! Are you expecting feedback from @toggl/androids or can I go ahead and do the changes you propose?

Hi @semanticer! Are you expecting feedback from @toggl/androids or can I go ahead and do the changes you propose?

Go for it, and thanks again!

Sorry that it's taking so long @jonekdahl

It's mostly in the docs, comments or tests but we should also probably rename those
dispatchFn: (List) -> Unit
as well right?

Yeah, it'd be good to have these changed as well to avoid confusion.

@semanticer Oh, go ahead!

Here is the continuation #30

authors: jonekdahl pdrj semanticer

repo: toggl/komposable-architecture


text:
www.meistertask.com not working with Toggl Button

Hi guys,
I'm trying to use the Toggl button in Chrome with Meistertask, but it's not working. The button doesn't appear in Meistertask.
Environment details

Operation system: Ubuntu 16.04 / Google Chrome
Extension version: 1.10.7

Expected behavior
Toggl button appears in Meistertask
Actual behavior
Toggl button doesn't appear in Meistertask
Steps to reproduce the behavior

Install Toggl button in Google Chrome
Setup Toggl button to allow all or at least www.meistertask.com
Open Meistertask task

Additional details
I get the following error in the Google Chrome console:
meistertask.js:10 Uncaught TypeError: Cannot read property 'textContent' of null     at meistertask.js:10     at Object.renderTo (common.js:146)     at MutationObserver.<anonymous> (common.js:128)
The code doesn't work here:

I tested a little bit and in this file is the issue:  https://github.com/toggl/toggl-button/blob/master/src/scripts/content/meistertask.js
In line 10 the project variable can not be set, because it doesn't find the title element. I removed this line and the button working, but without project.

Fixed the project name and created the following pull request: #1075

repo: toggl/toggl-button


text:
Incorrect width after restart desktop app

Hi.
Starting from the last update my Toggle desktop application starts like that. I mean without bordering to "start menu".
Ok, actually I always put application like that. I throw it to the right side of the screen and it resizing to some standard for Windows width, but after restart width become like it was before throwing (wider), upper left corner standstill so it looks like in first screenshot.
Notify me if you need steps to reproduce.

Thanks for reporting the problem!
It seems that it does not take the position/size of the taskbar into account properly.
We'll see what we can do!

Actually... taking a second look, I think it might be an issue related to dpi scaling (you seem to be using a rather high resolution monitor).
Which version are you using? (you can check in the app's about window)

App version 7.3.27
Monitor resolution: 1920*1080
BEST Regards.
Ukraine. Vinnytsia
skype: windreaver2622
mobile:  +380636076872
+380995225406
On Mon, Oct 26, 2015 at 10:58 AM, Paul Scharf notifications@github.com
wrote:

Actually... taking a second look, I think it might be an issue related to
dpi scaling (you seem to be using a rather high resolution monitor).
Which version are you using? (you can check in the app's about window)
—
Reply to this email directly or view it on GitHub
https://github.com/toggl/toggldesktop/issues/1615#issuecomment-151066551
.

I had the same issue at beta channel until I've updated to dev. Don't see this issue now.

So far I have not been able to reproduce the problem. I tried a couple of things with different DPI settings, window positions and taskbar configurations.
Could you guys send us a bug report through the app's send feedback window? That will include more information, including log files for us to take a look at. Please include that the info is for Paul (that's me).
It would be great if you could replicate the bug, and send the feedback right after the app starts with the wrong position. That will make the relevant information much easier to find.
Thanks for your help and patience!

hmm, maybe I was wrong with describing an issue, here's what I found today:

if we moved window somewhere and after that quit app through tray (I mean quit app, but not close window through 'X') - then window current position is stored and after restart it appears in the same position.
but if we moved window, then close it through 'X' and then quit app, then position isn't stored and after restart window appears in the previous place (where it was before moving).

Maybe in my situation window somehow was moved out off screen and stored this position, and each next time I've moved it to the right position, and at the end of day, just closed the window and turned off computer which is equals to the second behavior that I described.

Ah! Thanks for the clarification. I understand the problem now, and I already found the cause. Should be fixed soon. :)

authors: amulware egoroof iatsyk

repo: toggl/toggldesktop