LND v0.5-beta Not Started | Not Ready Yet

I had successfully setup a RaspiBlitz and populated with some BTC.  All was fine until a recent reboot.
After the reboot, I am able to unlock the LND wallet but when I proceed to the INFO screen

I have reformatted the SD card several times but continue with the same result.
Any ideas to help?  I would love to continue to learn about LND and support the network.

Can you go to the terminal and run this command to get some debug logs from the LND?
sudo journalctl -u lnd -b --no-pager -n20

-- Logs begin at Thu 2016-11-03 17:16:43 UTC, end at Tue 2018-12-11 22:40:52 UTC                                                                                . --
Dec 11 19:00:07 MiloBigCheese lnd[11704]: 2018-12-11 19:00:07.130 [INF] LNWL: Op                                                                                ened wallet
Dec 11 19:00:07 MiloBigCheese lnd[11704]: 2018-12-11 19:00:07.575 [INF] LTND: Pr                                                                                imary chain is set to: bitcoin
Dec 11 19:00:07 MiloBigCheese lnd[11704]: unable to create chain control: unable                                                                                to connect to bitcoind: status code: 401, response: ""
Dec 11 19:00:07 MiloBigCheese systemd[1]: lnd.service: Main process exited, code                                                                                =exited, status=1/FAILURE
Dec 11 19:00:07 MiloBigCheese systemd[1]: lnd.service: Unit entered failed state                                                                                .
Dec 11 19:00:07 MiloBigCheese systemd[1]: lnd.service: Failed with result 'exit-                                                                                code'.
Dec 11 19:01:07 MiloBigCheese systemd[1]: lnd.service: Service hold-off time ove                                                                                r, scheduling restart.
Dec 11 19:01:07 MiloBigCheese systemd[1]: Stopped LND Lightning Daemon.
Dec 11 19:01:07 MiloBigCheese systemd[1]: Started LND Lightning Daemon.
Dec 11 19:01:08 MiloBigCheese lnd[19044]: 2018-12-11 19:01:08.204 [INF] LTND: Ve                                                                                rsion: 0.5.0-beta commit=v0.5-beta-101-g61e867741926bcb318432a6344b80161fabd1455                                                                                , build=production, logging=default
Dec 11 19:01:08 MiloBigCheese lnd[19044]: 2018-12-11 19:01:08.204 [INF] LTND: Ac                                                                                tive chain: Bitcoin (network=mainnet)
Dec 11 19:01:08 MiloBigCheese lnd[19044]: 2018-12-11 19:01:08.205 [INF] CHDB: Ch                                                                                ecking for schema update: latest_version=6, db_version=6
Dec 11 19:01:08 MiloBigCheese lnd[19044]: 2018-12-11 19:01:08.210 [INF] RPCS: pa                                                                                ssword gRPC proxy started at <IP_ADDRESS>:8080
Dec 11 19:01:08 MiloBigCheese lnd[19044]: 2018-12-11 19:01:08.210 [INF] RPCS: pa                                                                                ssword RPC server listening on [::]:10009
Dec 11 19:01:08 MiloBigCheese lnd[19044]: 2018-12-11 19:01:08.213 [INF] LTND: Wa                                                                                iting for wallet encryption password. Use lncli create to create a wallet, ln                                                                                cli unlock to unlock an existing wallet, or lncli changepassword to change th                                                                                e password of an existing wallet and unlock it.
Dec 11 22:40:39 MiloBigCheese lnd[19044]: 2018-12-11 22:40:39.803 [INF] LNWL: Op                                                                                ened wallet
Dec 11 22:40:40 MiloBigCheese lnd[19044]: 2018-12-11 22:40:40.272 [INF] LTND: Pr                                                                                imary chain is set to: bitcoin
Dec 11 22:40:40 MiloBigCheese systemd[1]: lnd.service: Main process exited, code                                                                                =exited, status=1/FAILURE
Dec 11 22:40:40 MiloBigCheese systemd[1]: lnd.service: Unit entered failed state                                                                                .
Dec 11 22:40:40 MiloBigCheese systemd[1]: lnd.service: Failed with result 'exit-                                                                                code'.

there is some hint that "unable to create chain control: unable to connect to bitcoind" .. lets look into the debugs of the bitcoind - to see if it has some internal problems:
sudo tail -n 50 /mnt/hdd/bitcoin/debug.log
Just to check: did you use some special characters in your passwords?

In my Master password yes - there is a $.  Here are the bitcoind logs
2018-12-11T20:32:48Z socket recv error Connection reset by peer (104)
2018-12-11T20:38:29Z socket recv error Connection reset by peer (104)
2018-12-11T20:40:16Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 7898 seconds ago)
2018-12-11T20:43:56Z socket recv error Connection reset by peer (104)
2018-12-11T20:46:29Z socket recv error Connection reset by peer (104)
2018-12-11T20:48:30Z socket recv error Connection reset by peer (104)
2018-12-11T20:50:46Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 8528 seconds ago)
2018-12-11T20:53:30Z socket send error Connection reset by peer (104)
2018-12-11T20:54:03Z socket recv error Connection reset by peer (104)
2018-12-11T20:58:31Z socket send error Connection reset by peer (104)
2018-12-11T21:01:16Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 9158 seconds ago)
2018-12-11T21:01:43Z socket recv error Connection reset by peer (104)
2018-12-11T21:11:46Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 9788 seconds ago)
2018-12-11T21:15:59Z socket recv error Connection reset by peer (104)
2018-12-11T21:22:16Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 10418 seconds ago)
2018-12-11T21:23:32Z socket recv error Connection reset by peer (104)
2018-12-11T21:23:32Z socket send error Broken pipe (32)
2018-12-11T21:32:46Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 11048 seconds ago)
2018-12-11T21:32:56Z socket recv error Connection reset by peer (104)
2018-12-11T21:43:16Z socket recv error Connection reset by peer (104)
2018-12-11T21:43:16Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 11678 seconds ago)
2018-12-11T21:45:27Z socket recv error Connection reset by peer (104)
2018-12-11T21:46:09Z socket recv error Connection reset by peer (104)
2018-12-11T21:46:20Z socket recv error Connection reset by peer (104)
2018-12-11T21:46:51Z socket recv error Connection reset by peer (104)
2018-12-11T21:47:06Z socket recv error Connection reset by peer (104)
2018-12-11T21:48:34Z socket recv error Connection reset by peer (104)
2018-12-11T21:53:34Z socket send error Connection reset by peer (104)
2018-12-11T21:53:46Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 12308 seconds ago)
2018-12-11T21:56:36Z socket recv error Connection reset by peer (104)
2018-12-11T21:58:35Z socket send error Connection reset by peer (104)
2018-12-11T22:04:16Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 12938 seconds ago)
2018-12-11T22:08:35Z socket recv error Connection reset by peer (104)
2018-12-11T22:10:15Z socket recv error Connection reset by peer (104)
2018-12-11T22:13:36Z socket send error Connection reset by peer (104)
2018-12-11T22:14:46Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 13568 seconds ago)
2018-12-11T22:18:36Z socket recv error Connection reset by peer (104)
2018-12-11T22:25:16Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 14198 seconds ago)
2018-12-11T22:28:37Z socket send error Connection reset by peer (104)
2018-12-11T22:33:37Z socket recv error Connection reset by peer (104)
2018-12-11T22:35:13Z socket recv error Connection reset by peer (104)
2018-12-11T22:35:46Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 14828 seconds ago)
2018-12-11T22:38:41Z socket recv error Connection reset by peer (104)
2018-12-11T22:40:40Z ThreadRPCServer incorrect password attempt from <IP_ADDRESS>:5                                                                                8336
2018-12-11T22:46:16Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 15458 seconds ago)
2018-12-11T22:48:59Z socket recv error Connection reset by peer (104)
2018-12-11T22:53:38Z socket send error Connection reset by peer (104)
2018-12-11T22:53:51Z socket recv error Connection reset by peer (104)
2018-12-11T22:56:46Z Potential stale tip detected, will try using extra outbound                                                                                peer (last tip update: 16088 seconds ago)
2018-12-11T22:58:39Z socket send error Connection reset by peer (104)

i am currently having a similar issue as well. Also i have a ! in my password
debug logs from the LND
-- Logs begin at Wed 2018-12-12 03:53:31 UTC, end at Wed 2018-12-12 11:06:50 UTC                                                        . --
Dec 12 10:59:25 Node1 lnd[31528]: 2018-12-12 10:59:25.554 [INF] LTND: Primary ch                                                        ain is set to: bitcoin
Dec 12 10:59:25 Node1 lnd[31528]: unable to create chain control: unable to conn                                                        ect to bitcoind: Post http://<IP_ADDRESS>:8332: dial tcp <IP_ADDRESS>:8332: connect: c                                                        onnection refused
Dec 12 10:59:25 Node1 lnd[31528]: 2018-12-12 10:59:25.789 [INF] LTND: Shutdown c                                                        omplete
Dec 12 10:59:25 Node1 systemd[1]: lnd.service: Main process exited, code=exited,                                                         status=1/FAILURE
Dec 12 10:59:25 Node1 systemd[1]: lnd.service: Unit entered failed state.
Dec 12 10:59:25 Node1 systemd[1]: lnd.service: Failed with result 'exit-code'.
Dec 12 11:00:26 Node1 systemd[1]: lnd.service: Service hold-off time over, sched                                                        uling restart.
Dec 12 11:00:26 Node1 systemd[1]: Stopped LND Lightning Daemon.
Dec 12 11:00:26 Node1 systemd[1]: Started LND Lightning Daemon.
Dec 12 11:00:26 Node1 lnd[32512]: 2018-12-12 11:00:26.514 [INF] LTND: Version: 0                                                        .5.0-beta commit=v0.5-beta-101-g61e867741926bcb318432a6344b80161fabd1455, build=                                                        production, logging=default
Dec 12 11:00:26 Node1 lnd[32512]: 2018-12-12 11:00:26.515 [INF] LTND: Active cha                                                        in: Bitcoin (network=mainnet)
Dec 12 11:00:26 Node1 lnd[32512]: 2018-12-12 11:00:26.515 [INF] CHDB: Checking f                                                        or schema update: latest_version=6, db_version=6
Dec 12 11:00:26 Node1 lnd[32512]: 2018-12-12 11:00:26.526 [INF] RPCS: password R                                                        PC server listening on [::]:10009
Dec 12 11:00:26 Node1 lnd[32512]: 2018-12-12 11:00:26.526 [INF] RPCS: password g                                                        RPC proxy started at <IP_ADDRESS>:8080
Dec 12 11:00:26 Node1 lnd[32512]: 2018-12-12 11:00:26.527 [INF] LTND: Waiting fo                                                        r wallet encryption password. Use lncli create to create a wallet, lncli unlo                                                        ck to unlock an existing wallet, or lncli changepassword to change the passwo                                                        rd of an existing wallet and unlock it.
Dec 12 11:06:35 Node1 lnd[32512]: 2018-12-12 11:06:35.797 [INF] LNWL: Opened wal                                                        let
Dec 12 11:06:36 Node1 lnd[32512]: 2018-12-12 11:06:36.315 [INF] LTND: Primary ch                                                        ain is set to: bitcoin
Dec 12 11:06:36 Node1 systemd[1]: lnd.service: Main process exited, code=exited,                                                         status=1/FAILURE
Dec 12 11:06:36 Node1 systemd[1]: lnd.service: Unit entered failed state.
Dec 12 11:06:36 Node1 systemd[1]: lnd.service: Failed with result 'exit-code'.
debug of the bitcoind
2018-12-12T04:14:38Z UpdateTip: new best=0000000000000000002fa928a8c2ecf79f1d8f962745c49a8ba4f98e32de3f05 height=553482 version=0x20000000 log2_work=90.117743 tx=363838797 date='2018-12-12T04:14:27Z' progress=1.000000 cache=56.1MiB(492197txo) warning='33 of last 100 blocks have unexpected version'
2018-12-12T04:15:42Z UpdateTip: new best=000000000000000000189ffff78b77d6c408a36b99098c41fb4be2d4ff6ffceb height=553483 version=0x20000000 log2_work=90.117769 tx=363839216 date='2018-12-12T04:15:40Z' progress=1.000000 cache=56.1MiB(492341txo) warning='33 of last 100 blocks have unexpected version'
2018-12-12T04:46:49Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1867 seconds ago)
2018-12-12T04:47:02Z New outbound peer connected: version: 70015, blocks=553483, peer=108
2018-12-12T04:52:53Z Pre-allocating up to position 0xb00000 in rev01459.dat
2018-12-12T04:52:54Z UpdateTip: new best=0000000000000000001cf0ebf56562a16461f1fea099950fcec09e1f2686b8a7 height=553484 version=0x20000000 log2_work=90.117795 tx=363842195 date='2018-12-12T04:51:50Z' progress=1.000000 cache=57.0MiB(500865txo) warning='33 of last 100 blocks have unexpected version'
2018-12-12T05:02:43Z UpdateTip: new best=00000000000000000001396826d49b72e9e1061665039553ac783a26a75e6dfc height=553485 version=0x20000000 log2_work=90.117821 tx=363844765 date='2018-12-12T05:02:33Z' progress=1.000000 cache=57.2MiB(502640txo) warning='32 of last 100 blocks have unexpected version'
2018-12-12T05:18:31Z UpdateTip: new best=0000000000000000001b8496b762072161e06bda6507937bba91f09cba143ea8 height=553486 version=0x20000000 log2_work=90.117848 tx=363847213 date='2018-12-12T05:18:00Z' progress=1.000000 cache=58.0MiB(510269txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T05:19:29Z UpdateTip: new best=0000000000000000001589bf541d78bc3f70f26baf9a1feb39bc05a56f404a1a height=553487 version=0x20000000 log2_work=90.117874 tx=363848016 date='2018-12-12T05:19:01Z' progress=1.000000 cache=58.2MiB(511491txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T05:36:49Z Pre-allocating up to position 0x6000000 in blk01459.dat
2018-12-12T05:36:50Z UpdateTip: new best=00000000000000000030024f11e9afa1d81d89fec96b2a7c396efee5069f729b height=553488 version=0x20000000 log2_work=90.1179 tx=363850488 date='2018-12-12T05:37:23Z' progress=1.000000 cache=58.5MiB(515124txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T05:38:45Z UpdateTip: new best=0000000000000000000fbfbe0191f010ea922e0463aefc8328a1962376306e76 height=553489 version=0x3fffe000 log2_work=90.117926 tx=363851662 date='2018-12-12T05:38:46Z' progress=1.000000 cache=58.7MiB(516160txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T05:46:31Z UpdateTip: new best=0000000000000000000f166ce406b17ae37926ab26a2e46d0a0f578cff586d3a height=553490 version=0x20800000 log2_work=90.117952 tx=363853148 date='2018-12-12T05:46:19Z' progress=1.000000 cache=59.0MiB(518910txo) warning='32 of last 100 blocks have unexpected version'
2018-12-12T05:50:17Z UpdateTip: new best=00000000000000000005cd0f9470c095e8ea2ca462f99a7e1d531defb559bbd7 height=553491 version=0x20400000 log2_work=90.117978 tx=363853917 date='2018-12-12T05:49:58Z' progress=1.000000 cache=59.1MiB(519827txo) warning='32 of last 100 blocks have unexpected version'
2018-12-12T05:59:16Z Pre-allocating up to position 0xc00000 in rev01459.dat
2018-12-12T05:59:16Z UpdateTip: new best=00000000000000000018ed0cb4e200842cc30f9aa42b838a2a494d380ff4f6e9 height=553492 version=0x20000000 log2_work=90.118004 tx=363854769 date='2018-12-12T05:58:35Z' progress=1.000000 cache=59.3MiB(522048txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T06:15:36Z UpdateTip: new best=000000000000000000314503d988f870a07670db6311ecac5f4b1672881558e9 height=553493 version=0x20000000 log2_work=90.11803 tx=363856759 date='2018-12-12T06:15:09Z' progress=1.000000 cache=59.6MiB(524999txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T06:31:01Z UpdateTip: new best=0000000000000000001c7c13326c8d58fc0c4e5cc293200e38732a6f32f065ce height=553494 version=0x20000000 log2_work=90.118056 tx=363859561 date='2018-12-12T06:30:54Z' progress=1.000000 cache=60.0MiB(528988txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T06:34:18Z UpdateTip: new best=00000000000000000012672a428a18ca8f8ffe81126ba33f247e69e0f6f88e98 height=553495 version=0x20000000 log2_work=90.118082 tx=363861334 date='2018-12-12T06:33:30Z' progress=1.000000 cache=60.2MiB(530106txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T06:43:17Z UpdateTip: new best=00000000000000000008b8c5cb58818b5c84ae733077ff5c84122764af0840e4 height=553496 version=0x20000000 log2_work=90.118108 tx=363862245 date='2018-12-12T06:43:26Z' progress=1.000000 cache=60.4MiB(532411txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T06:49:40Z UpdateTip: new best=0000000000000000001cb150b7c4b651aa0807cb378a6fa46bce68d090028940 height=553497 version=0x20000000 log2_work=90.118134 tx=363864458 date='2018-12-12T06:49:32Z' progress=1.000000 cache=60.6MiB(534136txo) warning='31 of last 100 blocks have unexpected version'
2018-12-12T06:58:44Z UpdateTip: new best=00000000000000000030940e6d623c77a05db93124b0378b5e585adf110370c4 height=553498 version=0x20400000 log2_work=90.11816 tx=363865854 date='2018-12-12T06:57:58Z' progress=1.000000 cache=60.9MiB(536733txo) warning='32 of last 100 blocks have unexpected version'
2018-12-12T07:23:31Z UpdateTip: new best=000000000000000000190ff09e61119625694f3e67dacd76b979943aa29429d5 height=553499 version=0x20c00000 log2_work=90.118186 tx=363868700 date='2018-12-12T07:23:22Z' progress=1.000000 cache=61.7MiB(544516txo) warning='33 of last 100 blocks have unexpected version'
2018-12-12T07:26:42Z Pre-allocating up to position 0xd00000 in rev01459.dat
2018-12-12T07:26:42Z UpdateTip: new best=0000000000000000000f2766bc975b337f8e2391fe9ea9741f906a0dec21af41 height=553500 version=0x20000000 log2_work=90.118212 tx=363870667 date='2018-12-12T07:26:15Z' progress=1.000000 cache=61.8MiB(545749txo) warning='33 of last 100 blocks have unexpected version'
2018-12-12T07:40:48Z UpdateTip: new best=0000000000000000000230bef450892af770803da0e5ef4c1554e70993876a0b height=553501 version=0x20400000 log2_work=90.118238 tx=363873155 date='2018-12-12T07:40:18Z' progress=1.000000 cache=62.4MiB(550972txo) warning='34 of last 100 blocks have unexpected version'
2018-12-12T07:41:11Z UpdateTip: new best=00000000000000000017b0522cdc4587ae71a39edc525302c1d0bf8cbe7b1f2b height=553502 version=0x20000000 log2_work=90.118264 tx=363873608 date='2018-12-12T07:40:48Z' progress=1.000000 cache=62.3MiB(549831txo) warning='34 of last 100 blocks have unexpected version'
2018-12-12T08:10:34Z UpdateTip: new best=0000000000000000000e555452592f95145ae55c83a500ed3ec91ddcfe3ded39 height=553503 version=0x20800000 log2_work=90.11829 tx=363875971 date='2018-12-12T08:10:19Z' progress=1.000000 cache=63.3MiB(559362txo) warning='34 of last 100 blocks have unexpected version'
2018-12-12T08:12:36Z UpdateTip: new best=000000000000000000298870bbe38b8fe2b043c2bd25ce6e48f7784836e5e4b3 height=553504 version=0x20400000 log2_work=90.118316 tx=363878354 date='2018-12-12T08:12:15Z' progress=1.000000 cache=63.7MiB(562908txo) warning='35 of last 100 blocks have unexpected version'
2018-12-12T08:14:20Z Pre-allocating up to position 0x7000000 in blk01459.dat
2018-12-12T08:14:21Z UpdateTip: new best=00000000000000000005a71cdd2ab943dd9f686131cff6781f8cca3e92091cf9 height=553505 version=0x20800000 log2_work=90.118342 tx=363879334 date='2018-12-12T08:14:08Z' progress=1.000000 cache=63.6MiB(562724txo) warning='36 of last 100 blocks have unexpected version'
2018-12-12T08:22:18Z Pre-allocating up to position 0xe00000 in rev01459.dat
2018-12-12T08:22:18Z UpdateTip: new best=0000000000000000001ef62296a0933bb10b55a0c049978b019873e47f20a7e4 height=553506 version=0x20c00000 log2_work=90.118368 tx=363881018 date='2018-12-12T08:21:51Z' progress=1.000000 cache=63.8MiB(564653txo) warning='36 of last 100 blocks have unexpected version'
2018-12-12T08:37:34Z UpdateTip: new best=000000000000000000207abbe3072dc2cffb81f1085eafcb753f84e11326ba8d height=553507 version=0x20000000 log2_work=90.118394 tx=363883656 date='2018-12-12T08:37:13Z' progress=1.000000 cache=64.3MiB(569253txo) warning='35 of last 100 blocks have unexpected version'
2018-12-12T08:50:13Z UpdateTip: new best=00000000000000000002886ca20ef72395c5da5a95a27311b810376f5b83835d height=553508 version=0x20800000 log2_work=90.11842 tx=363886281 date='2018-12-12T08:49:55Z' progress=1.000000 cache=4.4MiB(9367txo) warning='35 of last 100 blocks have unexpected version'
2018-12-12T08:54:58Z UpdateTip: new best=0000000000000000000e51d9f59467a55512de3ffcb17790fae6dddf23108434 height=553509 version=0x20000000 log2_work=90.118446 tx=363887578 date='2018-12-12T08:54:56Z' progress=1.000000 cache=4.9MiB(13499txo) warning='34 of last 100 blocks have unexpected version'
2018-12-12T09:08:08Z UpdateTip: new best=0000000000000000000402058e6f0c73a35755b15b4ad1ccb9831649ccece6f9 height=553510 version=0x20c00000 log2_work=90.118472 tx=363889669 date='2018-12-12T09:07:53Z' progress=1.000000 cache=5.9MiB(23316txo) warning='35 of last 100 blocks have unexpected version'
2018-12-12T09:09:09Z UpdateTip: new best=0000000000000000002d5140cd3a13534dc530456fcdf355b31039d68b4b9e3d height=553511 version=0x20800000 log2_work=90.118499 tx=363890470 date='2018-12-12T09:08:51Z' progress=1.000000 cache=6.2MiB(25535txo) warning='36 of last 100 blocks have unexpected version'
2018-12-12T09:15:17Z New outbound peer connected: version: 70015, blocks=553511, peer=109
2018-12-12T09:35:15Z UpdateTip: new best=000000000000000000125a9a4bcf30485f7fac0fbb699e57c7c8b6c1090bc5b2 height=553512 version=0x20000000 log2_work=90.118525 tx=363892831 date='2018-12-12T09:34:59Z' progress=1.000000 cache=7.7MiB(39611txo) warning='36 of last 100 blocks have unexpected version'
2018-12-12T09:49:54Z Pre-allocating up to position 0xf00000 in rev01459.dat
2018-12-12T09:49:54Z UpdateTip: new best=00000000000000000003621901dc710f8e74d7865c24d0a4fda75c531bf77d63 height=553513 version=0x20c00000 log2_work=90.118551 tx=363895370 date='2018-12-12T09:49:18Z' progress=1.000000 cache=8.5MiB(47542txo) warning='37 of last 100 blocks have unexpected version'
2018-12-12T10:23:10Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1996 seconds ago)
2018-12-12T10:23:11Z New outbound peer connected: version: 70015, blocks=553513, peer=110
2018-12-12T10:28:22Z UpdateTip: new best=00000000000000000018a242f541c0dbab143fa5c35f458b114dfbfe56e98171 height=553514 version=0x20000000 log2_work=90.118577 tx=363897882 date='2018-12-12T10:28:24Z' progress=1.000000 cache=10.0MiB(61663txo) warning='36 of last 100 blocks have unexpected version'
2018-12-12T10:31:12Z UpdateTip: new best=0000000000000000002ecb172d571ac3a16516461cc80778b8fe8d311bab81bb height=553515 version=0x20400000 log2_work=90.118603 tx=363900583 date='2018-12-12T10:30:51Z' progress=1.000000 cache=10.6MiB(66509txo) warning='37 of last 100 blocks have unexpected version'
2018-12-12T11:05:12Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2040 seconds ago)
2018-12-12T11:05:13Z New outbound peer connected: version: 70015, blocks=553515, peer=111
2018-12-12T11:05:16Z New outbound peer connected: version: 70015, blocks=553515, peer=112
2018-12-12T11:05:36Z UpdateTip: new best=0000000000000000001d7053b6cc53765bb4316d4c6f82e977778137d10321da height=553516 version=0x20000000 log2_work=90.118629 tx=363903205 date='2018-12-12T11:05:23Z' progress=1.000000 cache=12.1MiB(81063txo) warning='36 of last 100 blocks have unexpected version'

hardwire1010 - did you find any solution?
rootzoll - I posted the bitcoind logs you requested above.  Is there a problem having a special character in any password?

@RyanSepio  No not yet, i wonder if it could be as simple as having special charters. over the next few days i might test it with a different password and see if it works.

@rootzoll When I start lnd I get the following and lnd is shutdown.  Any ideas what is happening here?
lnd
2018-12-13 17:24:48.945 [INF] LTND: Version: 0.5.0-beta commit=v0.5-beta-101-g61e867741926bcb318432a6344b80161fabd1455, build=production, logging=default
2018-12-13 17:24:48.945 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2018-12-13 17:27:27.476 [INF] CHDB: Checking for schema update: latest_version=6, db_version=6
2018-12-13 17:27:27.482 [INF] RPCS: password RPC server listening on [::]:10009
2018-12-13 17:27:27.482 [INF] RPCS: password gRPC proxy started at <IP_ADDRESS>:8080
2018-12-13 17:27:27.483 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
2018-12-13 17:28:28.867 [INF] LNWL: Opened wallet
2018-12-13 17:28:29.288 [INF] LTND: Primary chain is set to: bitcoin
2018-12-13 17:28:29.326 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on tcp://:28332
2018-12-13 17:28:29.326 [INF] LTND: Initializing bitcoind backed fee estimator
2018-12-13 17:28:29.327 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on tcp://:28333
2018-12-13 17:28:29.330 [DBG] LNWL: Using minimum fee rate of 253 sat/kw
2018-12-13 17:28:35.359 [INF] LNWL: The wallet has been unlocked without a time limit
2018-12-13 17:28:35.360 [INF] LTND: LightningWallet opened
2018-12-13 17:28:35.414 [INF] LNWL: Started rescan from block<PHONE_NUMBER>000000002363b3563bd9823068b7c5eb787d409d62d3c3bdef17d9 (height 552930) for 29 addresses
2018-12-13 17:28:35.416 [INF] LNWL: Starting rescan from block<PHONE_NUMBER>000000002363b3563bd9823068b7c5eb787d409d62d3c3bdef17d9
2018-12-13 17:28:35.899 [INF] HSWC: Restoring in-memory circuit state from disk
2018-12-13 17:28:35.932 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
2018-12-13 17:28:35.959 [INF] HSWC: Trimming open circuits for chan_id=552704:1191:1, start_htlc_id=0
2018-12-13 17:28:35.959 [INF] HSWC: Trimming open circuits for chan_id=552704:1190:1, start_htlc_id=0
2018-12-13 17:28:35.959 [INF] HSWC: Trimming open circuits for chan_id=552703:2668:1, start_htlc_id=0
2018-12-13 17:28:35.988 [INF] SRVR: Scanning local network for a UPnP enabled device
2018-12-13 17:28:36.096 [DBG] LNWL: Filtering block 552931<PHONE_NUMBER>000000001e9f559a4794ba476b81df52baf014eeb1387730872705) with 1371 transactions
2018-12-13 17:28:37.684 [DBG] LNWL: Filtering block 552932<PHONE_NUMBER>000000000c6e0c753347fd4d71f1fd6cd55f461bbfccd6886f36a3) with 2976 transactions
2018-12-13 17:28:39.203 [DBG] LNWL: Filtering block 552933<PHONE_NUMBER>000000000b47d8eff9fd6eb358732adaadde0052bbfd74623308b7) with 2263 transactions
2018-12-13 17:28:40.607 [DBG] LNWL: Filtering block 552934<PHONE_NUMBER>00000000238503c7257da249e93361adc24c81c784b0bd14c83c5d) with 1735 transactions
2018-12-13 17:28:41.996 [DBG] LNWL: Filtering block 552935<PHONE_NUMBER>00000000133db99e5f95db01b597bf59bcd6c3f4340c6101156a19) with 2851 transactions
2018-12-13 17:28:44.354 [DBG] LNWL: Filtering block 552936<PHONE_NUMBER>0000000026cdb6403ccf715cc23113e2327f7da2ea744e143331c7) with 2618 transactions
2018-12-13 17:28:44.355 [DBG] LNWL: Unable to parse output script in 5a5ba72039745007899c8328a230541e7c333dc5fe76bed2886b50b8d2ad2548:2: opcode OP_DATA_75 requires 76 bytes, but script only has 39 remaining
2018-12-13 17:28:45.988 [ERR] SRVR: Unable to discover a UPnP enabled device on the local network: context canceled
2018-12-13 17:28:45.988 [INF] SRVR: Scanning local network for a NAT-PMP enabled device
2018-12-13 17:28:46.017 [ERR] SRVR: Unable to discover a NAT-PMP enabled device on the local network: fork/exec /usr/bin/ip: no such file or directory
2018-12-13 17:28:46.018 [ERR] SRVR: unable to create server: Unable to discover a NAT-PMP enabled device on the local network: fork/exec /usr/bin/ip: no such file or directory
2018-12-13 17:28:46.018 [INF] LTND: Shutdown complete
Unable to discover a NAT-PMP enabled device on the local network: fork/exec /usr/bin/ip: no such file or directory

I finally solved the issue.
The issue was the nat=true setting.
2018-12-13 17:28:46.018 [ERR] SRVR: unable to create server: Unable to discover a NAT-PMP enabled device on the local network: fork/exec /usr/bin/ip: no such file or directory
I had set the inbound port forwarding manually on my firewall and did not need the automatic upnp or nat-pmp configuration coming from the RaspiPI.  This was causing LND not to start.  Once I removed that setting from lnd.conf all started fine.
I now have a running node on a public IP.


Allow string option transformations for native elements

This PR fixes a remaining bug for optional parameters, from https://github.com/ml-in-barcelona/jsoo-react/issues/81#issuecomment-1002261158
Was introduced by https://github.com/ml-in-barcelona/jsoo-react/pull/84.

Just want to chime in and say thanks for this @davesnx ❤! I bumped up against this when trying to create components that used input, i.e. wanting to only set value if a value for it is passed in above. Will be nice to have this in 🎉


Combine Rd Salt Data and scale to PRMS level

From the list of annual Rd salt dfs, create a single aggregated df with all years and a additional column per catchment that calculates: sum of salt accumulation for every year in catchment / salt accumulation across DRB

@msleckman I thought the road salt PR addressed this, but maybe not fully? If there's more to address, can you add a comment to this issue with the remaining tasks?

Yes it did.  Final target p2_rdsalt_per_catchment_allyrs


Raycast extension for Outline

Is there an existing issue that is already proposing this?

[X] I have searched the existing issues

Application
Outline Client
What are you trying to do? What is your use case?
To turn the Outline server on and off, you have to do it through the app all the time.
Is your feature request related to a problem? Please describe it.
My request isn't really related to the problem, it's just that using Outline on macOS would be much more comfortable this way.
Describe the solution you'd like.
Raycast extension to connect and disconnect from the Outline server
Need 2 thing by commands:

Turn on VPN, without visit the app.
Turn off VPN, without visit the app

Describe alternatives you've considered
I also familiarised myself with the request for IOS Shortcuts, that would be handy too.

Hi @khlebobul , thanks for contacting us. We'd like to know more information about the user scenario here and what we need to implement for the Raycast.

Hi @jyyi1, I don't really understand your question. You can make an extension for Raycast using TypeScript. I made this request because I saw extensions for using VPN with similar functionality.
https://www.raycast.com/search?q=vpn

Hi @khlebobul , Sorry for the confusion. Let me explain more.
Apple has built-in VPN settings, which we currently don't support very well. But we have a plan to add Outline VPN configuration to it, so the user can directly turn on/off Outline VPN connections using the system Settings UI without launching the Outline app.
My question is, if we add this support, will Raycast automatically recognize it? If so, we wouldn't need to create a Raycast extension.

I think this way will work for both the extension and the request for IOS Shortcuts. At the moment, as I understand it, this method does not work due to lack of support


add wireguard-install tool

I've been using wireguard-install for a while to run/manage my little home VPN with wireguard (and before that I used the openvpn-install script from the same author).

@bobafetthotmail Hi. wireguard-install is already there and can be found under terminal/cli section. Thank you for sharing. I'm closing this PR.


Various changes including:

Subnet operations/caching
Adding openstack specific Namespace in Keys ... Core doesn't support SUBNETS
Refactored instances to use jackson for serialization/deserilzation of openstack domain model
Formatting
Added some static imports to DRY up some classes/specs

lgtm

Addressed comments ... Closing and PR'ing against spinnaker.


Remove TraversableOnce, CanBuildFrom to support Scala 2.13

With the collections redesign, some things are deprecated or removed. We should find a way to support 2.13 and older versions.

IterableOnce is only in 2.13
So Iterable as it is present in both 2.12.x and 2.13.M4+?

Iterable may be a good replacement, but we're gonna need a new way to BuildFrom as well, since CanBuildFrom won't be an option availlable anymore.
Maybe something à la Data.Buildable?

We don't need to build it we just need to fold it.
As sad as it sounds I think the best option is to implement a fold function in terms of Iterator, it has been around since ever so it's the only common interface shared among all collections across all scala versions.
So users will have to call toIterator on whatever collection type they have in hand, which I guess is a zero-cost operation.

Hi @ktonga ,
I completely get your point about the need of a fold function in terms of Iterator.
But think I'm missing something then.
E.g. how we can implement traverse without notion of build? Specifically, how we can build an F[B]?
final def traverse[E, A, B, F[_]: Iterator](
  in: F[A]
)(fn: A => IO[E, B]): IO[E, F[B]]

In the current implementation this is solved by CanBuildFrom.
  final def traverse[E, A, B, M[X] <: TraversableOnce[X]](
    in: M[A]
  )(fn: A => IO[E, B])(implicit cbf: CanBuildFrom[M[A], B, M[B]]): IO[E, M[B]]

@AL333Z please disdain my first comment, I amended my mistake in my last comment. We do need to build collections too.

There's BuildFrom, which is available from both 2.12 and 2.13

We are already cross compiling for 2.11 too

I'm afraid BuildFrom is not available for 2.11, only 2.12+

But I don't think there's any diff in collections between 2.11 and 2.12 tho

the BuildFrom comes from the 2.12 -> 2.13 compatibility library I mentioned above

Ok. It seems it's not my day for making guesses

I checked as well, and I got to the conclusion that there's nothing we can use from scala std lib (2.11 -> 2.13) which we can leverage for this duty.
So I was thinking about building our own, even if this decision is not gonna be easy..
E.g. where to put this? scalaz-zio? or even, scalaz (and then, how can we import that in scalaz-zio, since the dependency is reversed)?

I'm afraid we will need to setup the project to provide per scala version implementations

core has to remain zero-deps, this needs to be solved for people using zio from vanilla scala. This is already solved by the interop module for scalaz users

It seems API for 2.13 collections is not yet definitive, so I would propose to start working on this in a separate long-term branch and don't merge any of this to master until 2.13 is released.
I can create the branch if you agree @jdegoes. WDYT?

@ktonga Yes, that seems good, although no need to create the branch now unless someone is willing to work on this ticket right away.
Also I feel very strongly that ZIO core must have zero dependencies.
In the worst case we can just hard-code to List.

unless someone is willing to work on this ticket right away

I think @AL333Z is. Although there is no need for a new branch if we go the List way :slightly_smiling_face:

Also I feel very strongly that ZIO core must have zero dependencies.

I already expressed my agreement on that too

In the worst case we can just hard-code to List.

I'm down for that!

I think we can just stick to List, avoiding the dep from scala-collection-compat.
For users which plan to use scalaz-zio without scalaz this may be enough.
scalaz may then bring in a more general solution, which may be addressed separately (a proper replacement for CanBuildFrom?).

Closed by #147


Make sure the isSimulating flag for hands is reset when losing window…

Overview
Reset the "isSimulating" flags for simulated hands when the application loses focus, so that hands are not moving with the mouse when focusing back on the window.
Changes

Fixes: #5375

Verification

Go into play mode
Hold shift and/or space to bring up simulated hands
While holding shift/space, alt+tab out of the window.
Simulated hands are released and disappear (or stop moving with the mouse if in persistent mode).

/azp run


end of article recirc

@mparent61 @MichaelButkovic @kand
This is currently a work in progress, but I'm pushing it up to get it to @shawncook so she can work on it. Let me know if you don't like this implementation or me as a person.

Seems fine to me so far.

Ingredients

1 lb. 90% lean ground beef
1 cup dried bread crumbs
1/2 cup diced yellow onion
1/2 cup milk
1 large egg beaten
2 tbsp. ketchup
1 tbsp. Worcestershire sauce
1 tsp. dried parsley leaves
3/4 tsp. salt
1/2 tsp. garlic powder
1/4 tsp. ground black pepper
For the Topping:
1/4 cup ketchup
2 tbsp. packed light brown sugar
1 tbsp. red wine vinegar

Instructions

Preheat oven to 350 degrees Fahrenheit.
In a large bowl, add the beef, bread crumbs, onion, milk, egg, 2 tablespoons ketchup, worcestershire sauce, parsley, salt, garlic powder, and pepper. Use your hands to mush and mix these ingredients together until well combined.*
Add the meat mixture to a loaf pan. Pat the meat down into an even layer.
In a small bowl, add 1/4 cup ketchup, the brown sugar, and vinegar. Stir to combine. Pour the sauce on top of the meatloaf and spread it into an even layer.
Bake uncovered for 55 minutes.
Let the meatloaf rest for 8-10 minutes before serving (or it may fall apart).**

Nice. This can be an old onion forum.

@spra85 please approve

👋

🐄 I love meatloaf, I'm gonna have to try out that recipe 🐄

Has anyone seen this? Pretty funny
https://www.youtube.com/watch?v=A3oL7v7PLac

@shawncook, Travis checks failed.  Can you make sure the meatloaf isn't over-cooked?

 They just fired me because they think I'm moonlighting. Help, my family is starving.

👋 I don't like meatloaf @shawncook got anything else?

See here for the top business reputation management currently in stock on the market and reasonably priced..

G̴̭͖̃̅̌̉͆̒Ő̶͔̆̌̃̑͗̏̕O̸͈͉͖̞͕̠̲̹͝G̸̻̠͙̞͕͎͒̈́̽̊̅͘L̴͚͕̪̥͋͜E̵̡͓̰̱̝͊̅͋̽̌̅̍ ̷̨͙͈͖̦͓͙̉͌͌̽̊̃̌͘M̵̧̫̞̫̙̝̥̈́̉̉̄̐̄͋̚͝Ą̶̛̛͇̺̝̦̰̊͒̎͐̎̀͛P̵̗̦̌̑̃͂͋̇̕S̸̨̛̥̼̳̭̬̞̅

https://www.youtube.com/watch?v=T6qDIov_eU4

Dang is that @jmelvnsn ?!

may I contribute kos holding a small Hawaiian shirt wearing dog like a burrito

@csinchok

@kelly-bishop

Don't tell Brietbart 2 much blackmail in here!


Update date for v3 release

This PR updates the date for the release of V3 from June to July 2019 to reflect our current estimate.

You can preview this change here:
Built with commit 089bcc55bbbdec12950c12edc17724dc1ada3b08
https://deploy-preview-917--govuk-design-system-preview.netlify.com


Events/Interviews: Spread out article metadata

From @akeshiiv:

You might want to consider increasing horizontal margins between the article components so that it will not look so concentrated towards the centre + increasing the padding to make the title+body+industry look less cramped.

Possible design inspiration: https://experience.dropbox.com/events-webinars

Whoops, original feedback was actually on post cards, but I think this part still needs to be spread out more.


[microNPU] Match requantize in min/max with activation pattern

Optimizes a corner case where min/max + clip also produces a re-quantize operation. Previously the re-quantize was lowered separately as an identity operation which is unnecessary. Now the quantization parameters from re-quantize will be used by the lowered min/max operation.
cc @ekalda @NicolaLancellotti @manupa-arm

friendly ping @manupa-arm, when you get some time would you be able to take a look at this?

Thanks @lhutton1 @NicolaLancellotti @ekalda !


Export todo

QUnit has support for todo tests (https://api.qunitjs.com/QUnit.todo/). I find them useful for when I have an acceptance test that will take several commits to get green.

I ❤ QUnit.todo!!!


Option to configure UPTIME_KUMA_LOG_FORMAT: json or text

📑 I have found these related issues/pull requests

[x] Checked and didn't find similar issue

🏷 Feature Request Type
Settings
🔖 Feature description
It would be very helpful for us to have an ENV_VAR to configure the logging format directly.
To be clear, a general option to switch between the current "text" logs and logs in "json" would already be a great benefit.
✔ Solution
Extend Logger implementation with a e.g. UPTIME_KUMA_LOG_FORMAT variable that can be set to "text" or "json" with "text" being the default, similar to the implementation of UPTIME_KUMA_HIDE_LOG.
Instead of logging to console as
console.error(timePart, modulePart, levelPart, msgPart);

with the value set to "json" the logging could log like this:
console.error(
  JSON.stringify(
    "timestamp": timePart,
    "module": modulePart,
    "level": levelPart,
    "message": msgPart
  )
);

❓ Alternatives
We have considered that this functionality would be possible by a log management solution, but a direct choice and configuration of the logFormat seems to us like a quick and valuable option to avoid further transformations in upstream solutions for the logs produced by kuma.
📝 Additional Context
n/a

Shure, reasonable.
Doing this needs the following PRs to work fully:

https://github.com/louislam/uptime-kuma/pull/4392
https://github.com/louislam/uptime-kuma/pull/4391

If you want to provide a PR to have json as an alternative log output, our contribution guide is here: https://github.com/louislam/uptime-kuma/blob/dd75890364fe9cbdfbef6119da6c126234fa6044/CONTRIBUTING.md

@CommanderStorm is there something else, that can be done here to support or is there a chance to get https://github.com/louislam/uptime-kuma/pull/5118 reviewed, merged and release in the next days? 😉

Released is a bit of a taller task.
The concrete reasons are listed in #4500.
Currently, the 2.0.0-beta.0 release is blocked by:

adding a database migration for existing data and retention https://github.com/louislam/uptime-kuma/pull/5075
writing a changelog that highlights what has changed and highlights why some of the more interesting changes were made (performance, db, email-templating).
https://github.com/louislam/uptime-kuma/issues/5096

If you want to help, going through the PRs and writing a changelog would be appreciated, but that is a lot of work.


No way to delete a route from HTTPRouter

There currently is no way to delete a route from a HTTPRouter instance. Shouldn't such a feature be implemented? It could be useful for modular applications that load dynamic libraries and unload them again.

Will make this part of a FAQ section.


Multiplexed messages in monitor output

Currently, when using multiplexed messages, they get decoded under the same message like so:
Received: 104, Discarded: 49, Errors: 0
   TIMESTAMP  MESSAGE
       2.750  BatteryVoltageTemperature(
                  BatteryIndex_mux: 28,
                  Voltage_28: 39294,
                  Temperature_28: 23122
              )

When you have multiplexed messages that come at high frequency, this is somewhat hard to parse, as it updates too quickly.
I think it would be useful to either:

Display all the muxed values under separate messages
Display all the muxed values under the same message

(1) would look something like:
Received: 104, Discarded: 49, Errors: 0
   TIMESTAMP  MESSAGE
       2.750  BatteryVoltageTemperature(
                  BatteryIndex_mux: 28,
                  Voltage_28: 39294,
                  Temperature_28: 23122
              )

       2.754  BatteryVoltageTemperature(
                  BatteryIndex_mux: 29,
                  Voltage_29: 39477,
                  Temperature_29: 23022
              )

And (2) would look something like:
Received: 104, Discarded: 49, Errors: 0
   TIMESTAMP  MESSAGE
       2.754  BatteryVoltageTemperature(
                  BatteryIndex_mux: 29,
                  Voltage_28: 39294,
                  Voltage_29: 39477,
                  Temperature_28: 23122
                  Temperature_29: 23022
              )

The multiplexer value would denote the last MUX'd value received (or it could optionally be hidden).
I guess this would also be applicable to the decode subparser as well.
What are your thoughts?

Closing as the PR was merged and available as of 32.14.0


Upgrade the Issue Template to use GitHub Issue forms 📜

Introduction
GitHub has recently rolled out a public beta for their issue forms feature. This would allow us to create interactive issue templates and validate them.
Stepzen-SpaceX-Graphql currently uses the older issue template format. The task is to create GitHub issue forms for this repository.
Tasks summary:

[ ] Fork & clone this repository
[ ] Prepare bug report issue form in .github/ISSUE_TEMPLATE/bug.yaml
[ ] Prepare documentation issue form in .github/ISSUE_TEMPLATE/documentation.yaml
[ ] Prepare feature request issue form in .github/ISSUE_TEMPLATE/feature.yaml
[ ] Push changes to master and test issue forms on your fork
[ ] Submit pull request

hey, I'm going to check this tomorrow morning (MST) to see if a PR was made, but I won't be reachable afterwards just FYI

@Cerchie The PR is ready just in time for you to review and approve. Please have a look and suggest changes, if any. Thanks


read the calc_xc routine in lsda calculations

In PR #305, builtin subroutine is directly read for lsda calculations. By this PR, calc_xc subroutine is read in the calculations. In addition, src/xc/exc_cor.f90, which is currently no longer used, is removed. @tt-ims san, could you check this PR?

OK, I will check it later.

Thank you for merging, @tt-ims san.


Multiple filters

HELP! Does someone have experience where you can filter an appsync query and combine different filters.
For example:
type Product
@model
{
name
color
price
theme
category
size
....
}
I want to filter on these fields and also on all possible  combinations. With secondary indexes I have reached the limit of 20 indexes, so that is not the solution :disappointed:
It need goes over 6000 product items

For complex query patterns, take a look at the @searchable directive: https://docs.amplify.aws/cli/graphql-transformer/searchable

Ok so it is only possible with an additional service?


Was this code reviewed?

Was this code reviewed?
Is the author familiar with Python? (class names do not follow Python's convention, misuse of **kwargs)
Is the author familiar with programming? (assignment to a variable followed by assignment to the same variable on the next line, without using the value)
How Amazon lets this happen?

Multiple code quality issues in this project are hurting my eyes. Similar to other project by this author - https://github.com/aws-samples/resource-auto-tagger/issues?q=is%3Aissue+author%3Ailyash-b

Duplicated code all over.

This is insane

Hi ilyash-b,
Thank you for your feedback.  We are reviewing your comments.


feat: ✨ new Rating Component

✨ New Rating Component

Disclaimer: I am aware of other PRs such as #2818 and #2350, but I reviewed both and came to the conclusion that I wanted to sort of combine them. #2818 allows a user to select a new rating but a new rating is set when hovering, which I'm not a fan of. #2350 does not allow for setting a rating, instead just displays the rating that was passed as a prop.

This implementation is based on @radix-ui/react-radio-group, which makes it more accessible, since it is also navigable with a keyboard.
https://github.com/shadcn-ui/ui/assets/61006057/e125da2c-8c7c-43bb-953e-eef5fb97fba6

Custom icon
A custom icon can be passed as an Icon prop. Depending on the style, you should pass a Lucide Icon or a Radix Icon. The Rating components handles all states.

count
A custom amount of ratings can be passed to adjust the granularity of the rating using the ratingSteps prop.

custom label
By default the label will be (${currentValue}/${totalSteps}). This can be overridden by simply passing a customLabel prop as a string.

disabled
To show the user the rating component is disabled, the opacity of the icons is lowered.

readonly
In contrary to the disabled state, the readonly is supposed to be used in cases where the component merely displays the current rating and never expects any input to be entered.
In this case the component looks the same but cursor events as well as keyboard events are turned off.

LGTM! 🚀

Hey, Is it possible to rate, or display decimal values such as 3.5 , 4.5?


[YD-2681] Enable camera option for Supplementary document flow in the Web View App

B&T

[ ] Supplementary Document flow

Start a SupDoc session
Tap BROWSE, a chooser is shown
Tap Camera or Files
The preview is shown after taking a pic by camera

B&T: OK


Photoresistor Documentation Support

Documentation requirements:

[x] link to the documentation
[x] Overview
[x] Components
[x] Assembly Instructions
[x] Circuit Diagram
[x] Functionality
[x] Testing
[x] Troubleshooting
[x] YAML
[x] Constructor and Methods
[x] Example Controller

This issue was resolved


Crashes when I want to go to settings

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
When I go to the settings and then to the profile information, the game crashes
Uploading Prufs.zip…

Acknowledgement of preliminary instructions

[x]  I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
When I go to the settings and then to the profile information, the game crashes


Feature: implement EngineIO V3

Here's some initial progress on the V3 implementation. Please provide detailed feedback if you can, I don't consider myself proficient in Rust yet.
A major difference in the v3 protocol is that packets are separatated by counting the characters instead of a record separator  like in V4 (\x1e). See https://github.com/socketio/engine.io-protocol/tree/v3#payload for more details.
Overview of changes:

Determine protocol version based on the request URI (EIO).
Moved packet parsing logic to a separate function that takes the protocol version into account.
Added unit test

I ran the socket.io test suites as well and all tests still succeed. However, I should note that the socketio test suites only cover V4. The V3 branch doesn't contain V3-specific test suites for me to test, unfortunately.

Marked this as draft because I still need to implement the rest for the protocol to work properly. I'm moving on with the reverse ping/pong mechanism. Feel free to check the code in the meantime though.

Thanks for starting all of this !
I have just one suggestion, I think it is much better to have feature flags for versions (with v4,v3) and that you do all your version conditions on those feature flags. It would allow to remove useless code at compile time and also to have the information everywhere in the codebase without having a ProtocolVersion enum.
Also, don't forget to rebase from main regularly

I think end to end test-suites are very important, therefore if I have the time I'll try to make one for the v3 version (by copying v4) and modifing things with the feature. It could be tested with the official engine.io v3 to be sure it is ok.
This would allow that this implementation is correct

Agreed, feature flags make more sense for this project. I'll make adjustments.

Currently ts version has option allowEI3 and it works with both versions.
So I would suggest to have ProtocolVersion as param in case of V3 flag is enabled.

I agree but it should be a separate feature for when eio3 is already supported.

I think end to end test-suites are very important, therefore if I have the time I'll try to make one for the v3 version (by copying v4) and modifing things according to changes between v3 & v4. It could be tested with the official engine.io v3 to be sure it is ok.
We would then be sure that this implementation is correct

Just got started on this as well, feel free to suggest adjustments: https://github.com/socketio/engine.io-protocol/pull/45

Sure ! I totally agree with you

Currently ts version has option allowEI3 and it works with both versions. So I would suggest to have ProtocolVersion as param in case of V3 flag is enabled.

I agree but it should be a separate feature for when eio3 is already supported.

I agree with both of you but I think if we want to support a allowEI3 equivalent then the Rust features need to be implemented a bit differently.
Personally, I think we need give consumers of the library the choice to either enable a specific EngineIO protocol or multiple. In case multiple protocol versions are specified, the version to use is decided at runtime by the EIO parameter.
My current solution
Please see the following commit: https://github.com/sleeyax/socketioxide/commit/a88a0b0a37f64d666a47dd8e19671effd5f54d50.
V4 is enabled by default and other protocol versions can be added alongside of it by adding features. When default features are disabled and only one version is specified, that version is used instead and big chunks of specific code from other versions (like hearthbeat and packet parsing) are eliminated at compile time.
At the time of writing, there's still some smaller lines of code from other protocol versions that are not eliminated at compile time yet. I'm still considering the right approach to remove this code too (with as little code duplication as possible).
Examples
Default (v4 only):
[dependencies]
engineioxide = { version = "0.3.0"}

Default (v4) and v3. This is essentially the same as the allowEIO3 option in the official ts server implementation:
[dependencies]
engineioxide = { version = "0.3.0", features = ["v3"] }

Only v3. Large parts of v4-specific code are eliminated at compile time:
[dependencies]
engineioxide = { version = "0.3.0", features = ["v3"] , default-features = false}

Caveats

The ProtocolVersion enum has to stay and be passed around for multi-protocol support at runtime.  I don't think it's that big of an issue, because it's a very small enum and it's also used for validation of the EIO query parameter.

I like this solution ! I'll try to review this today

I like this solution ! I'll try to review this today

Awesome, I'm happy you like it! :) No rush, there's a few more things I need to fine tune. I'll be done in an hour or so.

Support non-base64-encoded binary payload

Not sure if I want to continue implementing this last part of the v3 protocol myself. It seems like Node clients and modern browsers favor base64 strings over binary blobs so I think most people won't require this feature anyways. If the need arises we can still add it, but for now I'd rather get a thorough review on this PR and move on to the SocketIO V3 protocol implementation.

Thank you for the review, I'll further check it out and make changes tomorrow :)

I've addressed everything now :)

I can't comment on unchanged lines but I think you should rename this part to heartbeat_rx and heartbeat_tx in socket.rs because in v3 it would be ping_rx and ping_tx so it is better to have an agnostic name (and also change comments accordingly) :

    /// Internal channel to receive Pong [`Packets`](Packet) in the heartbeat job
    /// which is running in a separate task
    pong_rx: Mutex<mpsc::Receiver<()>>,
    /// Channel to send Ping [`Packets`](Packet) from the connexion to the heartbeat job
    /// which is running in a separate task
    pub(crate) pong_tx: mpsc::Sender<()>,

Round 2 of the PR review : :heavy_check_mark:
Please let me know if more changes are required. I'd be happy to see this merged soon :)

@Totodore oops
https://github.com/Totodore/socketioxide/blob/3b802d9f9deb5baf2a3cdde01b837473e816d116/engineioxide/src/payload.rs#L29
there is a security issue:
if there is no separator and a client send a lot of data it will increase buffer until memory is running out.
in case of getting the length it mustn't exceed 8 bytes.
in case of reading until separator(v4) it should exceed configured size.

Right, let's fix that in another PR


rickshaw-run: bug fixes in dump_params

The output from multiplex.go produces 'value' and not 'val'.

Detect whether a parameter has a value or not and act accordingly.

@atheurer
I'm not sure whether you want to move to 'value' or stay with 'val' -- either way something needs to be fixed.
The other changes fix the spewing of messages that I was seeing.

This will probably throw off a lot of existing bench-params.json files out there, but I suppose that is not a big deal if you think 'value' is more clear.


Switching from Travis to Github Actions

Hi - I noticed that the Travis CI link is broken. I had several of those myself since when Travis switched to a premium-only CI.
If that is okay for you, I will make a pull request changing the travis setup for a GitHub actions setup.
Best,
Luca

Once issue #30 is dealt with this should be complete. Thanks, Luca, for getting the ball rolling on it.


WSL2 Crashing With Docker

Windows Version
Microsoft Windows [Version 10.0.22635.4580]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[x] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-1
Distro Version
Ubuntu
Other Software
Docker Desktop with WSL integration Version 4.37.0
Immich self-hosted container image
Repro Steps
Launch anything on wsl related to docker, such as a container, docker --help, etc.
Expected Behavior
Continuing with the process.
Actual Behavior
WSL crashes with docker showing the error
Docker Desktop WSL Integration Terminated Abruptly.
WSL Error:
[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

Diagnostic Logs
Attaching WSL logs.
WslLogs-2024-12-13_22-50-55.zip

Thank you for reporting this @Hashah2311. Looking at the logs, I can see that the issue is that the VM exits with triple fault:
Microsoft.Windows.Lxss.Manager	AbnormalVmExit	12-13-2024 09:24:30.687	"	"	"Details:
{
	""""Status"""": 	-1070137082
	""""ExitType"""": 	""""UnexpectedExit""""
	""""Attribution"""": 	[{""""SystemExit"""":{""""Detail"""":""""UnexpectedExit"""",""""Initiator"""":""""GuestOS""""}}
	{""""WorkerExit"""":
	{
		""""Type"""": 	""""StoppedOnReset""""
		""""Detail"""": 	""""TripleFault""""
		""""Initiator"""": 	""""GuestOS""""
	}
	{""""TripleFault"""": 	{""""ErrorType"""":18446744071562068001}}]
}
wslVersion: 	<IP_ADDRESS>"				4832	17912	5		00000000-0000-0000-0000-000000000000

Unfortunately those are usually caused by hardware issues so they're pretty difficult to root cause. Can you run a memory check and see if anything comes out ?

I ran memory diagnostics (assuming you meant checking up my RAM) and it shows no errors.

@OneBlue Can you help me?

Interesting. Could you share which CPU model your machine is running on ?

My machine configuration:
CPU: Intel Core i5-10300H
Ram: 8GB
GPU: NVIDIA GeForce GTX 1650 4GB
OS: Windows 11 Home Insider Preview (Beta)


Scope provisioning to specific users and groups - Can or cannot use OU's

The Scope provisioning to specific users and groups section states that you can change scopes for cloud sync for OU's but then the next statement says it cannot.
"You can scope the agent to synchronize specific users and groups by using on-premises Active Directory groups or organizational units."
vs
"You can't configure groups and organizational units within a configuration."
https://learn.microsoft.com/en-us/azure/active-directory/hybrid/cloud-sync/how-to-configure#scope-provisioning-to-specific-users-and-groups

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

ID: 5909c1d7-157a-d3f2-2b88-3023c132e901
Version Independent ID: be9ab177-6a7d-e744-4600-01e0fc44cb1d
Content: Azure AD Connect cloud sync new agent configuration - Microsoft Entra
Content Source: articles/active-directory/hybrid/cloud-sync/how-to-configure.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

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

Yes, this is a typo and should be can.  I have fixed this and submitted the change.  It should be live later today.  Thanks and good catch!
#please-close


Preflight doesn't check if the GitLab projects already exist

Which version of kubefirst are you using?
v2.4.10
Which cloud provider?
k3d (local)
Which DNS?
None specific
Which installation type?
CLI
Which distributed Git provider?
GitLab
Did you use a fork of gitops-template?
No
Which Operating System?
None specific
What is the issue?
Preflight doesn't check if the GitLab projects already exist, so it start the process, and failed on the "Applying gitlab Terraform" step.
I tried only with k3d, but I assume it's the same with all the clouds.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

So @jokestax may have been right, it may have been after a first try that failed, as I can't reproduce on a clean new environment, so I'm closing this one for now.


Crash when async yielding is enabled

Test Case
I created a small repo that reproduces the issue. Tried to make it as minimal as possible but as I'm not sure what exactly the reason is, I stayed with a realistic example that is similar to how we use wasmtime.
The repo is here: https://github.com/vigoo/wasmtime-crash-repro
component contains a project to be compiled with cargo component build - it's basically just a sleep
host initializes wasmtime and contains a fake wasi implementation using async bindings which only does an async sleep in the poll_oneoff implementation. Then it spawns 100 instances and runs them in parallel.
If either epoch based async yielding, or fuel based async yielding is enabled, I get a random crash from traphandlers.rs:
thread '   4:        0x105e81b04 - core::fmttokio-runtime-worker::' panicked at 'writeassertion failed: std::ptr::eq(head, self)::', h34766cf8fff7af1e/Users/vigoo/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmtime-runtime-9.0.3/src/traphandlers.rs

Steps to Reproduce
cargo component build in the component directory
cargo run in the host directory
Expected Results
All the 100 instances run, sleep for 2 seconds and finish.
By commenting out the epoch related lines in main.rs it finishes successfully.
Actual Results
Panic in traphandlers.rs
Versions and Environment
Tried it with both the stable release and an (almost) latest master and it happens in both.
Operating system: OSX Ventura
Architecture: arm64
Extra Info

Thanks for the report! I'm digging into this and trying to figure out what's going on. It's proving elusive so it may take me a moment to figure out the best fix for this.

Ok I've isolated this to a failing unit test. I wrote a fix for that and was about to make a PR until I realized that the fix wasn't complete. I've written a second test to trigger that failure and I'll work more tomorrow on a complete fix for this.

I'll also note that as a heads up this is a memory unsoundness issue. We won't be issuing a CVE due to our policy right now as the component model support is "tier 3" which doesn't get CVEs allocated. If that impacts your usage though you may wish to be aware.

Thanks for the updates!

Ok I believe that https://github.com/bytecodealliance/wasmtime/pull/6509 should address this issue for now


Update vivaldi to 1.7.735.46

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

@neutric I have removed the thunderbird.rb file from your PR.

Darn, something is messed up. Thanks!


Error: Building package boost-build:x64-windows failed with: BUILD_FAILED

bootstrap-x64-windows-err.log
bootstrap-x64-windows-out.log
-- Testing integrity of cached file... OK
-- Bootstrapping...
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:44 (message):
Command failed: C:/vcpkg/packages/boost-build_x64-windows/tools/boost-build/bootstrap.bat;msvc
Working Directory: C:/vcpkg/packages/boost-build_x64-windows/tools/boost-build
See logs for more information:
C:\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-out.log
C:\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-err.log
Call Stack (most recent call first):
ports/boost-build/portfile.cmake:47 (vcpkg_execute_required_process)
scripts/ports.cmake:72 (include)
Error: Building package boost-build:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: boost-build:x64-windows
Vcpkg version: 0.0.100-2017-12-19-6cb6a61aaf5ef2c143f974e9f731778bcd3f5cbe
Additionally, attach any relevant sections from the log files above.
==========
I am running 64bit win10 Education version.
What to do? :(
Thank You!

Thanks for posting this issue!
Could you attach the contents of:

C:/vcpkg/packages/boost-build_x64-windows/tools/boost-build/bootstrap.log

Hi, thanks for replying.
File is attached below:
bootstrap.log
Thank You!

I... am not really sure what the issue is. Does your username have Unicode characters in it? I tried a user account with spaces, but boost-build still works for me.
If that isn't the issue then I think the best thing to do will be to try running bootstrap.bat yourself (it's located at C:/vcpkg/packages/boost-build_x64-windows/tools/boost-build/bootstrap.bat), outside vcpkg -- if that fails, then you can go to #boost on the cpplang slack to get help.
Really sorry I can't be of more help 😢!

All ASCII characters, english letters only 1 space. #boost on cpplang.slack sent me here xD I already tried all the methods they suggested

Hi @Vehemos , thanks for reporting this issue!
I tested installing boost-build:x64-windows in a path with spaces, but found no problems.
Please open a new issue if this is still a problem for you.
Thx.


Documentation: Guide for mocking ES6 modules (different from ES6 classes)

🚀 Feature Proposal
A guide on using ES6 modules with Jest. The guide would probably go above "ES6 Class Mocks" on the sidebar.
It would explain the __esModule: true property when using jest.mock and provide examples for using it and not using it.
It would also explain that ES6 modules are non-writable unlike CommonJS. To create a different mock in a specific test you have to:

Reset modules with jest.resetModules().
Create the new mock with jest.doMock inside the specific test.
Dynamically re-import the module with import().

Motivation
I haven't found any information on the Jest website about using the __esModules: true property. Without that information users would not be able to properly use ES6 module mocks in their tests without using manual mocks.
I also haven't found information on the Jest website mentioning how having a different mock for an ES6 module requires re-importing the module dynamically.
As a result I've gotten very stuck in the past on how to properly mock ES6 modules. I think this information would help a lot of users.
Please let me know your thoughts. If interested I can make a PR.

Hey @sargalias, thanks for your interest in improving the documentation :)
doMock, resetModules and dynamic imports just to make mocking work are things that I'd like the documentation not to encourage to avoid fragile/complicated test setups - usually there are better ways of solving these cases, maybe the docs need to get better at offering alternatives to doMock etc. instead?

Hey @jeysal, it's a pleasure. Ah that's fair enough. To be honest I think manual mocks are sufficient for most cases. I was thinking more from a point of view of having that information available.
I understand the sentiment. In that case please feel free to close the issue :).

Super happy about improvements to etc. the doMock API docs, just for guides I think we should avoid these things / show people how to avoid them :)


Fix up relationship-association API test issue

Closes: #DNE
What's Changed
Just a bit of code cleanup to address an issue in the RelationshipAssociation REST API test that I had worked around while implementing tests for #2092. I'd thought at the time that it was a potential bug in the REST API (requiring PATCH requests on /api/dcim/site/ to always include status as a field) but it turned out to be much simpler - another case where we were creating objects via the ORM in the test case setup and not actually specifying all object attributes that should be required. (tagging #1034 here). Ensuring that the Site objects we create during setup actually have a status value at creation time makes it so that we don't need to specify a status on subsequent PATCH requests.

Curious if there are other places we are running into issues like this (outside of #1034)


_nuxt folder is missing

Nuxt compiles his file into .nuxt directory in the root and builds it to .nuxt/dist, so _nuxt folder inside public doesn't created, that's why this error appeared:
ErrorException (E_WARNING)
file_get_contents(D:\OSPanel\domains\ln.ll\public\_nuxt/index.html): failed to open stream: No such file or directory:
Route::get('{path}', function () {
    return file_get_contents(public_path('_nuxt/index.html')); // <----
})->where('path', '(.*)');

Did you try to make clean installation step by step following readme? Or maybe there's some missing content for settings?

If you don't use SSR make sure to follow the guide https://github.com/cretueusebiu/laravel-nuxt#production-without-ssr and set the app env to production.

I'm in SSR mode.

Set GITHUB_CLIENT_ID
run yarn run build
run yarn run start
visit http://localhost:3000/login
press 'Login with github' and got this error.

You have 2 options to run this:

with SSR (default) where you would access it via http://localhost:3000
without SSR where you have to follow the guide, set the app env to production, run npm run build then visit http://yourapp.test without running npm run start (like a normal Laravel app).


NullReferenceException

CSC : warning AD0001: Analyzer 'BepInEx.Analyzers.HarmonyPropertyPatchAnalyzer' threw an exception of type 'System.NullReferenceException' with message 'Object reference not set to an instance of an object.'.
Tried installing on Visual Studio 2019 and the analyzer throws this

Should be fixed in 1.0.6


⚠ Bofrost.de has degraded performance

In 8ae95f9, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 890 ms

Resolved: Bofrost.de performance has improved in 384e248.


IP blocklists

Hi,
First, thanks for your pico, very powerfull & tiny torrent app, do the job, remember me the good old days with μT.
I love the gui integration w/ windows 10.
And, I wanted to know if you could add the ipfilter feature.
Like in Deluge, or just take into account the ipfiler file (dat etc..) like in μT, qB.. .
That's a small feature,  that can be very useful.
I use that for family pc's  to give an easy and simple minimum protection againt hadopi (fr), and it works so.
Thanks, best regards,
from a guy lost in France :)
ps: sorry for my english if i could some mistakes ^.-

Similar to #796


CREATE -> TRANSFER -> TRANSFER throws 400

To reproduce this issue, perform below operations

CREATE
TRANSFER of (1)
TRANSFER of (2)

When performing operation (3), metadata object is serialized with value {} which is not valid schema for transaction on BigchainDB server, and hence server throws HTTP 400 Invalid schema {}

It seems like it was issue with the passing of metadata values. It works and doesn't need to be fixed.


Display used resource quota for namespaces in a project with associated resource quota

For a project with resource quota, we need to display the resource quota usage for the namespaces in a user friendly manner.
Currently the only way to find the resource quota used for a namespace is by using the API.

@vincent99 @westlywright
As there is no project/namespace detail page, we can only view the resource quota for a project/namespace in edit project/namespace page now.
Where should we display the resource quota of namespace and project?

How about adding a View action in action menu for project and namespace?

ping @vincent99 @westlywright ^ answer?

@loganhz @cjellick Vince and I have come up with a solution. We wont be adding a view action or a detail page (i think there are actual reasons we don't have these details pages). On the namespace creation page we we will show a progress bar with the project limit total/used/remaining. This is what we briefly discussed in our meeting earlier @cjellick

"Reserved" color shouldn't stand out... bg-info
"This namespace" number should be the same as the input on the right (=5), not (reserved+this=11)
The math is wrong somehow, if you put in a 0 quota there's still a yellow bar, sometimes @tfiduccia gets NaNs for all the numbers, etc
You shouldn't be able to type in a number higher than is available, or negative numbers in the first place.. set min/max on the input
Use colons instead of hyphens, and newlines, and drop the field name ("Pods") from the tooltip
Show units on the numbers when appropriate (500 MiB)
Trying again on the labels with @tfiduccia (below)
And +1 internet points if it could be an actual HTML table so they line up nicely (ignore the first row, GitHub markdown...):

Other Namespaces:1500 MiB
This Namespace:600 MiB
Available:400 MiB
-- border-top line --
Total:2000 MiB

Version - 2.1 master 9/21
Verified fixed


Suggestion: Put "dnd5e" in the title of this module

I'm not certain that this is only for dnd5e, but I assume so, and that's actually kind of my point.
It's not immediately apparent that this is only for dnd5e on the package list (or readme), and doing this would help GMs who don't use dnd5e immensely.

The intention of this is to be able to use it for any system, but I haven't had the time to check/test yet. But I can add some details saying as such.


Cannot read property "xpath" or "get" of undefined on element

I have an element that asserts true when tested with .isPresent()). But when I try to chain methods like .by.xpath or .get(0), they throw an error that the element is undefined.
What information do I need to provide to help debug this?

Saw a stack overflow issue and also tried throwing together a promise chain real quick, which didn't work:
    var text = element.all(by.css('ul[data-field-name="form.mayonnaise"]')).then(function (elm){       return elm[0].by.xpath('preceding-sibling').then(function(elm){         return elm[0].get(0).then(function(elm){           return elm[0].getText();         })       })     });
This again told me that the element at elm[0].by.xpath is undefined.

Can you provide your protractor config and a more simplified example (ideally with markup as well as your test code?)

Here's a sample:
element(by.css('tag-manager[tags="mayonnaise.found_withs"]')).get(0).get(1).get(0);
The structure of the dom is such that this tag-manager element has underneath it a div, which has four children, the first of which is a span, the last three divs. The first div has an input which I need to send text too, while the second one has a button I need to click.
Here's my protractor conf:
var s = require('selenium-server-standalone-jar'); var c = require('chromedriver'); exports.config = {   seleniumServerJar: s.path,   seleniumPort: 4444,   chromeDriver: c.path,   specs: [     '../test/spec-e2e/**/*.{js,coffee}'   ],   capabilities: {     'browserName': 'chrome'   },   baseUrl: 'http://<IP_ADDRESS>:9009',   rootElement: 'body',   jasmineNodeOpts: {     onComplete: null,     isVerbose: true,     showColors: true,     includeStackTrace: true,     defaultTimeoutInterval: 20000   } };

I made a bad assumption and now realize that the get method does not go through the children but rather all results from given query.
Instead what I needed what element(by.css('css')).element(by.css('css')).


I won a lot of coins, it's a real random

I won a lot of coins, it's a real random

only with 53 plots?

Well done I've been farming for almost a day

Well done I've been farming for almost a day

Check if plots are passing filter... I moved over to the Windows client this morning and plots seem to just stop passing filter after a while. Restarted the client and it happened again after half an hour.
Just went back to the Linux CLI instead which has won 10 blocks for me since the reset with a lot less plots than you!

i farmed 12spare with 1770plots from restart yesterday

seem to pass filter

I've had probably over 100 proofs found going through the logs an I have a total of 16 spare

seem to pass filter

check pass filter time with your system time if its longer than 15 secounds you won't win

Well done I've been farming for almost a day

Check if plots are passing filter... I moved over to the Windows client this morning and plots seem to just stop passing filter after a while. Restarted the client and it happened again after half an hour.
Just went back to the Linux CLI instead which has won 10 blocks for me since the reset with a lot less plots than you!

did you got allready some coins?

Pray for the coin to get listed in an exchange. Otherwise you'll just rely on community to buy/sell the coin. Unlisted coin is useless if you can't exchange or trade.


Feature/1132 rails assets migration

New Build Process

acquire dependencies bundle install
setup db rake db:create rake db:setup rake sample:demo
set your environment RAILS_ENV= (production, development, test)
precompile assets for the environment rake assets:precompile
start the server rails s

Description
Swaps npm for rails, gulp for rails asset bridge and refactors structural layout of the frontend.
Minimal touch was applied to frontend, likely bugs that existed before still exist.
Updates a number of in place gems for compatibility.
Related Issue
closes #1132
Motivation and Context

How Has This Been Tested?
existing tests pass, rspec
Screenshots (if appropriate):
unmagled compiled code using env production and app working

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Adds database migrations (Requires all environments to run rake db:migrate to work)
[x] Adds new Gemfile dependencies (Requires all environments to run bundle install to work)
[ ] Adds new ENV variables (description of ENV and purpose is required in the above description)

Checklist:

[x] My code follows the code style of this project.
[x] My code has been cleaned of commented, logging, and inline test code.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Getting errors about missing assets.

The template cache is not working. Requests are made for each template.

Missing assets. These were found by mousing over the sidebar.

yep a few lingering ones, addressed.

@stackus @AllenBW ready to go with this one?

I CAN'T WAIT FOR THOSE THUMBS!!! yeah all good on my end.


openshift: add instructions to integrate with OLM

Description
Once our operator is certified and published in the RedHat catalog, we'll want users to be able to manage the operator via the Operator Lifecycle Manager (OLM).
This PR adds extra instructions at the end of the OpenShift install page to do so, with a warning about upgrading. It also instructs users to install the latest stable v4.3.

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit bc576cda05e6432691a57691031071550120c17b
https://deploy-preview-3378--calico.netlify.com

replaced by https://github.com/projectcalico/calico/pull/3826


Detail Solid GitHub permissions associated to roles

Solution associated to conversation on https://github.com/solid/information/issues/48

@Mitzi-Laszlo Went through and applied updates as requested. You can see the differences in this commit. A few details on the rationale behind some of the changes:

Panels: Added a rule that repos created for panels have to be suffixed with "-panel". The reason for this is that it would otherwise be confusing for someone coming to the solid github organization, looking for definitive guidance on a topic, and mistaking a panel repository for that definitive guidance. These repos will have tons of content that hasn't gone through editorial review and acceptance. Since anyone can create a panel, and panels can request to have a repo made, i believe this rule is important to impose.
Editors: Editors need the ability to do more than triage. I touched on this here, but to add another reason - merging isn't always just a button click. Often there are cases where conflicts need to be resolved, and unless someone is well-informed on the substance of the material (editor or author), they're aren't in a position to resolve conflicts correctly. IMO - this isn't the place of an administrator, it's part of editorial responsibility.
There was a section in "Becoming an Administrator" that didn't have anything to do with becoming an administrator. It essentially said if you don't have a role that's already been named, you have regular public access. It seemed superfluous so I removed it.

This pull request has been succeeded by #95. This branch and its associated version history was merged into that branch and then modified further. Closing this pull request.


New option --crunchyroll-session-id which allows the user to specify a specific API session ID

Reference:
Option to set crunchyroll session ID
Support providing a custom Crunchyroll session ID
Link to 32-digit session ID for crunchyroll.com:
https://cr.onestay.moe/getId
https://github.com/Onestay/CR-Unblocker/blob/master/extension/background_script.js
https://chrome.google.com/webstore/detail/cr-unblocker/agapeeilkibacbfeijlidlgppmjaaijn
Link to crunchyroll.py with "session_id" implemented successfully:
https://github.com/streamlink/streamlink/blob/master/src/streamlink/plugins/crunchyroll.py
Since they already got that working and both of you are writing codes in Python, it should be a piece of cake to add an option --crunchyroll-session-id for crunchyroll.py and thanks a lot!

youtube-dl does not use crunchyroll APIs.

Sorry for necrobumping but wouldn't it be possible to implement this feature using cookies instead of the API?
Onestay's CR-Unblocker plugin does it this way.


Use react-scripts build instead of npm run build

To make the build flow more consistent

Codecov Report

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

@@          Coverage Diff          @@
##           master    #65   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines          56     56
  Branches       10     10
=====================================
  Hits           56     56

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 f5a131b...01042b7. Read the comment docs.


Allow users to set their own handlers for hyperlinks

Is your feature request related to a problem? Please describe.
I want to be able to handle link opening myself, such that I can use different code for different protocols, and other stuff like being able to open the link in a seperate tab on web, rather than the current tab.

Describe the solution you'd like
This could easily be implemented via just passing a closure to the hyperlink widget.

Describe alternatives you've considered
None?

Additional context
Nothing.

I think this could be implemented in another way:
If we add a new widget LinkButton that just takes a label (no URL) and does nothing on click, then you could do it yourself:
if ui.add(LinKButton::new("Documentation")).clicked() {
    …
}

It would look the same as HyperLink but have no click response, no url, and now hover text. Hyperlink could use LinkButton internally.

I think this could be implemented in another way:
If we add a new widget LinkButton that just takes a label (no URL) and does nothing on click, then you could do it yourself:
if ui.add(LinKButton::new("Documentation")).clicked() {
    …
}

It would look the same as HyperLink but have no click response, no url, and now hover text. Hyperlink could use LinkButton internally.

Yeah that would work better, more composition :sweat_smile:


No xml produced

I added {:junit_formatter, "~>0.1.2"} as a dependency, added :junit_formatter to the applications list and added ExUnit.configure formatters: [JUnitFormatter, ExUnit.CLIFormatter] before ExUnit.start but no xml file is produced.
I'm using elixir 1.2.2.
Did I miss something? What could I look to know what's going on?

eh my bad... I was looking in the wrong _build directory...

No problem! If anything shows up just open a new Issue

I was looking in an app's _build folder that was a leftover from when umbrella apps did not share it.


Dose ConsulServiceDiscoveryProvider request the services' register info by consul http api for each http request?

    public async Task<List<Service>> Get()
    {
        var queryResult = await _consul.Health.Service(_consulConfig.KeyOfServiceInConsul, string.Empty, true);

        var services = new List<Service>();

        foreach (var serviceEntry in queryResult.Response)
        {
            if (IsValid(serviceEntry))
            {
                services.Add(BuildService(serviceEntry));
            }
            else
            {
                _logger.LogError($"Unable to use service Address: {serviceEntry.Service.Address} and Port: {serviceEntry.Service.Port} as it is invalid. Address must contain host only e.g. localhost and port must be greater than 0");
            }
        }

        return services.ToList();
    }

I think this solution costs more network traffic. Correct me if I'm wrong?

And the second issue: Consul down cause Ocelot down? May we need a reroute configuration cache.

@zlzforever thanks for your interest in the project!  Consul should run as a sidecar so there is no network traffic. I'm not sure what the cost of calling localhost (quick google didnt find much) is but i think its minimal as this is how Consul is designed.
There is another Ocelot feature that stores the configuration in Consul and that uses a poller and has a cache so it doesnt matter if Consul goes down, the same technique could be applied to the problem above.
However if the consul sidecar goes down you probably have bigger problems on your host or something. I would say the chances of just the Consul sidecar going down are very slim when running next to Ocelot.
If you are not running Consul next to Ocelot (e.g. sidecar style or at least on same host) then you are going to be calling across the network but this is not a supported configuration.
I don't think we need to worry too much about this.

Closing as no activity, feel free to reopen


#idea 🧠  Can we have an option to export or import the in-app notifications

Is there a way possible to export the in-app notification configuration in JSON format and import it back for re-using.
As I was using the in-app notification builder, every time I close the XTB and reopen again - i have to start from scratch to build the notification. Having this feature could the tool usage.
I am willing to contribute my time but I am relatively have less experience in developing WPF or XTB plugins. Having said that, I am completely willing to learn and do and help increase the tool usage for community

Thanks for the feedback, that's definetly a good idea. There is a settings feature in XTB that can handle things like that. I will try to implement that it loads the last notification created for each organization at least.

Yes thanks. That will be great for starting with
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Ivan Ficko @.***>
Sent: Monday, February 7, 2022, 2:40 PM
To: DynamicsNinja/InAppNotificationBuilder
Cc: Dinesh Siva; Author
Subject: Re: [DynamicsNinja/InAppNotificationBuilder] #idea 🧠 Can we have an option to export or import the in-app notifications (Issue #2)
Thanks for the feedback, that's definetly a good idea. There is a settings feature in XTB that can handle things like that. I will try to implement that it loads the last notification created for each organization at least.
—
Reply to this email directly, view it on GitHubhttps://github.com/DynamicsNinja/InAppNotificationBuilder/issues/2#issuecomment-1031231122, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOAJS6ADQGVKDEJLYTYWGJTUZ6D6RANCNFSM5NRZ5EDA.
You are receiving this because you authored the thread.Message ID: @.***>


Exported UI classes have protected members that get renamed

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
master, v3.0.x
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app?
Custom
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
ChromeOS stable 86
What are the manifest and license server URIs?
N/A
What did you do?
Register a custom UI plugin based on shaka.ui.RangeElement or shaka.ui.SettingsMenu
What did you expect to happen?
The protected members in those base classes should be available to app plugins
What actually happened?
The protected members of the base class get renamed
This has been solved for shaka.ui.Element through shaka.extern.IUIElement, so we should apply the same fixes to these other helpful base classes.

Also, shaka.util.FakeEvent would be useful to export for apps to use in custom UI elements.  They can dispatch events, but without this export, it's harder.


Custom domain, SNI and self signed cert

Please provide us with the following information:

This issue is a: (mark with an x)

[ ] bug report -> please search issues before submitting
[x] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
I'm trying to the custom domain feature of ACA. To do so I am required to provide a TLS cert with SNI. So I am using openssl command line to generate a self signed one.
After configuring it all in ACA, when I access the app via the custom domain, I get "connect reset by peer" error
Questions:

Is there anywhere I can see errors relating to the cert? I looked in the LA logs and saw nothing
I notice that "Solution" is always blank in the portal, I don't know if that is related
Is it possible to use self-signed certs with ACA? If so could the steps be documented?

Steps to reproduce

Create a self signed cert using openSSL. This is the command I've been using
Configure ACA as per the docs, e.g. setup & upload the cert, add DNS records, add custom domain to ingress in ACA
Try to hit the site with curl http://foo.mydomain.com

Expected behaviour [What you expected to happen.]
I am able to access the site, even if I get a browser warning about the self signed cert
Actual behaviour [What actually happened.]
Connect reset by peer error is returned
Additional context
I've configured ACA with the cert and domain using the portal and using Bicep. It makes no difference.

Did you also ran openssl pkcs12 -inkey cert.key -in cert.pem -export -out test.dev.export.pem and used the output cert?
Also, note that your app will still have self sign cert and you will have to tweak your browser.
For curl, you can add --insecure

Just including here, what I covered in our chat
The error I was seeing was connection reset, I got this error when using the PEM formatted cert, when I tried pkcs12 format, then it works, with the warnings (which is what I expected with a self signed cert)
It seems like the cert must be in PKCS12 format to work with ACA, however it lets you upload and try with PEM, and doesn't tell you that it's not going to work. I still feel like there might be a bug or issue here, perhaps disallow PEM format certs?

Thanks @benc-uk we will discuss the best way to handle this within the platform and make sure it is documented as well.

:clap: Thanks @benc-uk. I had the exact same problem - and this issue saved me a huge amount of time.
Agreed that the platform should handle this better.


Thread Accessibility Messaging

This adds messaging for new user join about accessibility and Slack threads. It also adds a @gopher trigger for the same message.

Not sure who generally reviews these so I looked at a couple and it seems @freeformz does these things sometimes. I was also talking to @theckman about this previously on Slack. This is why I have two reviewers.

Would you mind re-raising this against https://github.com/gobridge/gopherbot for consideration? I'm going to be archiving this repo.


Where I can download the app? I forgot

Describe your suggested feature
Could you just give the exact site to download the latest version and different site for the reviews of changes I Don't Know Where Exactly to download the app
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.13.
[X] I will fill out all of the requested information in this form.

There's no site, all the releases and their changelogs are in the release section.


Adding of NAT rules is not idempotent

Hello! I am currently using cp_mgmt_add_nat_rule to add new NAT policies into my CP Firewall. However, when I run the same playbook twice, I expect idempotency but instead, the NAT rules were added twice.
Is there a way to add NAT rules only when it is not currently not in the policy list? I want to prevent duplicated NAT rules in my policy list.
Thank you!

Issue closed as I managed to find a workaround. I query the existing rulebase using cp_mgmt_nat_rule_facts before conditionally running cp_mgmt_add_nat_rule


Encode form seems buggy

Was playing with the encode form. Doesn't seem to always work.
Was mostly changing the custom name

Pretty sure the error is the path needs "" around the string to make it absolute


Bottom bar reappears whenever I click (not swipe) the screen

Description
I use SystemNavigationBar.navigationHide(); to hide the bottom bar. The bar does get hidden, though whenever I click the screen again the bar reappears. (I'm on Android 11 emulator, don't have access to a physical Android device)
react-native-system-navigation-bar version
2.6.3
React Native version
0.72.4
Snack, code example, screenshot, or link to a repository
No response

Hi @canpoyrazoglu, can a sample screen recording be shared?

Hi @kadiraydinli when preparing to record I've noticed a few observations. Because of NDA I can't directly share my app screen, though when I commented out parts of my app (e.g. navigation controller) the problem stopped, so I suspect it's due to something in the navigation stack.
In addition, the problem is occuring on Nexus 5 Android 11 emulator, but not occuring on Pixel 7 Pro API 34. Will add more details when I can pinpoint what is causing it.


Fix readthedocs documentation generation

readthedocs makes the assumption that the binary sphinx-build
will be located in the venv binary directory.
readthedocs logs demonstrate that this binary is actually installed
in /lib/launch_ros_sandbox.
While the reason for this behavior is unclear, this changes work
around this issue creating a symbolic link to sphinx-build in the
bin directory to ensure that sphinx-build will find the binary
as expected.
To do so, a fake Python package is introduced in
doc/sphinx_build_symbolink. This fake package is added to
.readthedocs.yml so that its setup.py is executed before
documentation generation. Using a fake package ensures that no
production code is touched by this workaround.
This commit also fixes the .readthedoc.yml file by:

fixing the path to conf.py which was incorrect
removing commented out configuration options

Fix #22
Signed-off-by: Thomas Moulard<EMAIL_ADDRESS>By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@emersonknapp yes it does
https://launch-ros-sandbox.readthedocs.io/en/tmoulard-fix-readthedocs/

Yes! I'll check it's the case.


top bar default color should be gray instead of black

#6D6D6D
applies to

back buttons
action text (done, cancel, next, etc.)
magnifying glass icon
feed and profile names (and the carrot icons associated with them)
navigation text
'add' menu text/icons

You mean the text color?

text, icon, anything up there besides channel privacy and the orange notification color


Add "exists" operation

Just a simple wrapper for std::fs::exists using blocking. Strange that it wasn't implemented considering tokio's fs feature has it as try_exists.

I would accept a PR that adds this.