Incompatibility with long chain upgrades

Issue description
[supervysor] failed to query height. - 10 retries and restart...
This functionality is not compatible with chain upgrades when it can take time to migrate/upgrade
Playing with Osmo v6.4.0 upgrade, and after restart migration continues from the same step but if it is not completed this will be an endless loop
Workaround:

manual restart without supervysor
wait for the chain upgrade
restart with supervysor

Logs
12:17AM INF indexed block height=2383299 module=txindex
12:17AM ERR UPGRADE "v5" NEEDED at height: 2383300: https://raw.githubusercontent.com/osmosis-labs/osmosis/v5.x/networks/osmosis-1/upgrades/v5/mainnet/v5.0.0-binaries.json
panic: UPGRADE "v5" NEEDED at height: 2383300: https://raw.githubusercontent.com/osmosis-labs/osmosis/v5.x/networks/osmosis-1/upgrades/v5/mainnet/v5.0.0-binaries.json
goroutine 77 [running]:
github.com/cosmos/cosmos-sdk/x/upgrade.BeginBlocker({{_, _}, _, {_, _}, {_, _}, _}, {{0x20796f8, 0xc000044060}, ...}, ...)
        github.com/cosmos/cosmos-sdk@v0.42.9/x/upgrade/abci.go:70 +0xf08
github.com/cosmos/cosmos-sdk/x/upgrade.AppModule.BeginBlock(...)
        github.com/cosmos/cosmos-sdk@v0.42.9/x/upgrade/module.go:127
github.com/cosmos/cosmos-sdk/types/module.(*Manager).BeginBlock(_, {{0x20796f8, 0xc000044060}, {0x20866c8, 0xc01ed2e800}, {{0xb, 0x1}, {0xc013760a44, 0x9}, 0x245dc4, ...}, ...}, ...)
        github.com/cosmos/cosmos-sdk@v0.42.9/types/module/module.go:341 +0x198
github.com/osmosis-labs/osmosis/app.(*OsmosisApp).BeginBlocker(_, {{0x20796f8, 0xc000044060}, {0x20866c8, 0xc01ed2e800}, {{0xb, 0x1}, {0xc013760a44, 0x9}, 0x245dc4, ...}, ...}, ...)
        github.com/osmosis-labs/osmosis/app/app.go:589 +0xdb
github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).BeginBlock(_, {{0xc023199720, 0x20, 0x20}, {{0xb, 0x1}, {0xc013760a44, 0x9}, 0x245dc4, {0x31a65e1c, ...}, ...}, ...})
        github.com/cosmos/cosmos-sdk@v0.42.9/baseapp/abci.go:191 +0x89b
github.com/tendermint/tendermint/abci/client.(*localClient).BeginBlockSync(_, {{0xc023199720, 0x20, 0x20}, {{0xb, 0x1}, {0xc013760a44, 0x9}, 0x245dc4, {0x31a65e1c, ...}, ...}, ...})
        github.com/tendermint/tendermint@v0.34.14/abci/client/local_client.go:280 +0x118
github.com/tendermint/tendermint/proxy.(*appConnConsensus).BeginBlockSync(_, {{0xc023199720, 0x20, 0x20}, {{0xb, 0x1}, {0xc013760a44, 0x9}, 0x245dc4, {0x31a65e1c, ...}, ...}, ...})
        github.com/tendermint/tendermint@v0.34.14/proxy/app_conn.go:81 +0x55
github.com/tendermint/tendermint/state.execBlockOnProxyApp({0x207a338?, 0xc007b4c480}, {0x2080410, 0xc000d58b90}, 0xc006573a40, {0x2086938, 0xc0059984c0}, 0x245dc3?)
        github.com/tendermint/tendermint@v0.34.14/state/execution.go:307 +0x51d
github.com/tendermint/tendermint/state.(*BlockExecutor).ApplyBlock(_, {{{0xb, 0x1}, {0xc0082b0ef0, 0x7}}, {0xc0082b0ef7, 0x9}, 0x1, 0x245dc3, {{0xc011b08920, ...}, ...}, ...}, ...)
        github.com/tendermint/tendermint@v0.34.14/state/execution.go:140 +0x171
github.com/tendermint/tendermint/blockchain/v0.(*BlockchainReactor).poolRoutine(0xc005b66a80, 0x0)
        github.com/tendermint/tendermint@v0.34.14/blockchain/v0/reactor.go:398 +0xb5a
created by github.com/tendermint/tendermint/blockchain/v0.(*BlockchainReactor).OnStart
        github.com/tendermint/tendermint@v0.34.14/blockchain/v0/reactor.go:110 +0x7a
12:17AM INF daemon shutting down in an attempt to restart module=cosmovisor
12:17AM INF pre-upgrade command does not exist. continuing the upgrade. module=cosmovisor
12:17AM INF upgrade detected, relaunching app=osmosisd module=cosmovisor
12:17AM INF running app args=["start","--p2p.seeds","400f3d9e30b69e78a7fb891f60d76fa3c73f0ecc@osmosis.rpc.kjnodes.com:12959,ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:12556","--home","/home/cosmos/.osmosisd","--x-crisis-skip-assert-invariants"] module=cosmovisor path=/home/cosmos/.osmosisd/cosmovisor/upgrades/v5/bin/osmosisd
12:17AM INF starting ABCI with Tendermint
12:17AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B3234302031303720373420313620313838203133372031372031373620343020323236203533203138362034203134322032303220313436203133352031333620323238203131362034342034302031303020313233203234392033322034302032203134312032303520313237203139325D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34b80, acc}" version=0
12:17AM ERR [supervysor] failed to query height. Try again in 20s ... (1/10)
12:17AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B5D3A307D is_lazy=false store_key="KVStoreKey{0xc000f34d80, authz}" version=2383300
12:17AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B31373920313134203336203230392037302031383420343520393420313035203132392039332034372034342033392031323220313039203131203137362031362032303720323336203231312031352032353520383320313237203230332032343820373520313834203731203136315D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34ba0, bank}" version=0
12:17AM ERR [supervysor] failed to query height. Try again in 20s ... (2/10)
12:18AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B5D3A307D is_lazy=false store_key="KVStoreKey{0xc000f34db0, bech32ibc}" version=2383300
12:18AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B3134372032313420313734203231392031372032313520313630203134342038312036332039362031313020323331203431203138312035382032303020333420313230203133312031363420313637203131382031323520323920323032203231362031343120393720323037203138203234315D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34ce0, capability}" version=0
12:18AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B3233312037332031353720313637203234372031383920313137203532203136302032362031383820353520393720363720323533203630203734203233392032313620313020323334203120323335203131203530203130203230372031373620392031322039362032395D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34d20, claim}" version=0
12:18AM ERR [supervysor] failed to query height. Try again in 20s ... (3/10)
12:18AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B313135203737203135342032333220333720313230203135352031373520323237203239203233352032343020363520313438203135302031323420313420313536203830203134302039322031393720313630203231312031333320393420313331203234382031353520323030203139312037305D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34be0, distribution}" version=0
12:18AM ERR [supervysor] failed to query height. Try again in 20s ... (4/10)
12:18AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B3231352031393720313420343720323236203130392039392031383620323433203620313432203233362031323820323434203230322031393120313537203020323038203834203231382032303620353320393920323039203237203134203231382031313820313533203231382034325D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34d50, epochs}" version=0
12:18AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B3232372031373620313936203636203135322032353220323820323020313534203235312032343420323030203135332031313120313835203336203339203137342036352032323820313030203135352031343720373620313634203134392031353320323720313230203832203138342038355D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34cb0, evidence}" version=0
12:18AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B38362032333520323720323438203230372032343120323535203133342031352035332034382031323020313037203836203234302036392033312034382031353920332031383920393020313835203137352031363220333220323337203635203233302032313720313531203131355D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34cf0, gamm}" version=0
12:18AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B31372031303120323439203920313633203233312031303520313533203130382034332031393720313333203631203339203234203332203137312032343620313732203230312032313220323133203132332032343420313938203839203139342032303920322032313820323339203130305D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34c40, gov}" version=0
12:18AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B31353720313332203930203634203134382033322031323820383520373620353720313120393120323430203139352032323320333720313436203234322032322033362036302031382032313320343320313236203135322038312034332039362034302033312034355D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc000f34c70, ibc}" version=0
12:18AM ERR [supervysor] failed to query height. Try again in 20s ... (5/10)
12:19AM ERR [supervysor] failed to query height. Try again in 20s ... (6/10)
12:19AM ERR [supervysor] failed to query height. Try again in 20s ... (7/10)
12:19AM ERR [supervysor] failed to query height. Try again in 20s ... (8/10)
12:20AM ERR [supervysor] failed to query height. Try again in 20s ... (9/10)
12:20AM ERR [supervysor] failed to query height. Try again in 20s ... (10/10)
12:20AM ERR [supervysor] could not get node height err="could not get node height, exiting ..."
12:20AM FTL terminated error="os: process already finished" bin=/home/cosmos/.osmosisd/cosmovisor/upgrades/v4/bin/osmosisd module=cosmovisor
Error: could not get node height, exiting ...
Usage:
  supervysor start [flags]
Flags:
  -h, --help   help for start
osmosisd.service: Main process exited, code=exited, status=1/FAILURE
osmosisd.service: Failed with result 'exit-code'.
osmosisd.service: Consumed 7h 10min 20.316s CPU time.
osmosisd.service: Scheduled restart job, restart counter is at 1.
Stopped osmosisd node service.
osmosisd.service: Consumed 7h 10min 20.316s CPU time.
Started osmosisd node service.
12:21AM INF [supervysor] starting initially
12:21AM INF [supervysor] initial process started pId=4120044
12:21AM ERR [supervysor] failed to query height. Try again in 20s ... (1/10)
12:21AM INF running app args=["start","--p2p.seeds","400f3d9e30b69e78a7fb891f60d76fa3c73f0ecc@osmosis.rpc.kjnodes.com:12959,ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:12556","--home","/home/cosmos/.osmosisd","--x-crisis-skip-assert-invariants"] module=cosmovisor path=/home/cosmos/.osmosisd/cosmovisor/upgrades/v5/bin/osmosisd
12:21AM INF starting ABCI with Tendermint
12:21AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B31353720313332203930203634203134382033322031323820383520373620353720313120393120323430203139352032323320333720313436203234322032322033362036302031382032313320343320313236203135322038312034332039362034302033312034355D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc00179c680, ibc}" version=0
12:21AM ERR [supervysor] failed to query height. Try again in 20s ... (2/10)
12:22AM ERR [supervysor] failed to query height. Try again in 20s ... (3/10)
12:22AM ERR [supervysor] failed to query height. Try again in 20s ... (4/10)
12:22AM ERR [supervysor] failed to query height. Try again in 20s ... (5/10)
12:23AM ERR [supervysor] failed to query height. Try again in 20s ... (6/10)
12:23AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B3432203436203639203133392036322031323920313037203335203131392036352033332039372031303720313620313930203530203231322032323420313036203232342033332033362031333620323620313937203132382031303620323233203137382031313720323134203134365D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc00179c700, incentives}" version=0
12:23AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B3232312032313420313230203331203232372031343120323336203137302033382031333020313633203537203236203230312032313420333020313020323134203231352031353720313039203235302035342032313920323131203131362032323820353020323238203220323335203137385D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc00179c6e0, lockup}" version=0
12:23AM ERR [supervysor] failed to query height. Try again in 20s ... (7/10)
12:23AM ERR [supervysor] failed to query height. Try again in 20s ... (8/10)
12:24AM ERR [supervysor] failed to query height. Try again in 20s ... (9/10)
12:24AM ERR [supervysor] failed to query height. Try again in 20s ... (10/10)
12:24AM ERR [supervysor] could not get node height err="could not get node height, exiting ..."
Error: signal: terminated
12:24AM ERR error="signal: terminated" module=cosmovisor
Error: could not get node height, exiting ...
Usage:
  supervysor start [flags]
Flags:
  -h, --help   help for start
osmosisd.service: Main process exited, code=exited, status=1/FAILURE
osmosisd.service: Failed with result 'exit-code'.
osmosisd.service: Consumed 5min 17.210s CPU time.
osmosisd.service: Scheduled restart job, restart counter is at 2.
Stopped osmosisd node service.
osmosisd.service: Consumed 5min 17.210s CPU time.
Started osmosisd node service.
12:25AM INF [supervysor] starting initially
12:25AM INF [supervysor] initial process started pId=4134856
12:25AM ERR [supervysor] failed to query height. Try again in 20s ... (1/10)
12:25AM INF running app args=["start","--p2p.seeds","400f3d9e30b69e78a7fb891f60d76fa3c73f0ecc@osmosis.rpc.kjnodes.com:12959,ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:12556","--home","/home/cosmos/.osmosisd","--x-crisis-skip-assert-invariants"] module=cosmovisor path=/home/cosmos/.osmosisd/cosmovisor/upgrades/v5/bin/osmosisd
12:25AM INF starting ABCI with Tendermint
12:25AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B3232312032313420313230203331203232372031343120323336203137302033382031333020313633203537203236203230312032313420333020313020323134203231352031353720313039203235302035342032313920323131203131362032323820353020323238203220323335203137385D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc001610420, lockup}" version=0
12:25AM ERR [supervysor] failed to query height. Try again in 20s ... (2/10)
12:25AM ERR [supervysor] failed to query height. Try again in 20s ... (3/10)
12:26AM ERR [supervysor] failed to query height. Try again in 20s ... (4/10)
12:26AM ERR [supervysor] failed to query height. Try again in 20s ... (5/10)
12:26AM ERR [supervysor] failed to query height. Try again in 20s ... (6/10)
12:27AM ERR [supervysor] failed to query height. Try again in 20s ... (7/10)
12:27AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B3136382031383220363720343620383520313934203134392033332031353620323033203534203135382032333120313535203232312032323320323030203232332038352032313720313032203139312031343720343620353220313530203135352038362032343020313532203932203135345D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc001610370, mint}" version=0
12:27AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B31303220323335203230332032333520362031323320333420313738203234362031373220313932203731203535203138392034312031343920313230203934203132392031373220383620323031203934203233332033392033342032333820333420323035203420313133203230355D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc0016103b0, params}" version=0
12:27AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B32303620313330203831203631203938203139362037342038322031333920373420333520323034203130312039322032323520313431203231322037352032343120333220393920313334203735203130302032313620313638203134372032333420313020313831203131392036325D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc001610460, poolincentives}" version=0
12:27AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B32343920313238203933203939203138312032343320313433203135203933203134362032333920343720323433203136362036382031323620313639203637203135302032303620313720353120323530203232352032322031343720323020313335203139302035203138302032315D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc001610390, slashing}" version=0
12:27AM ERR [supervysor] failed to query height. Try again in 20s ... (8/10)
12:27AM ERR [supervysor] failed to query height. Try again in 20s ... (9/10)
12:28AM ERR [supervysor] failed to query height. Try again in 20s ... (10/10)
12:28AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B32303420323036203531203230332037203137362032313220363420393120322031343820313334203339203135352038372031313120353320313037203130342032323220323237203635203137352031393820323238203137312032323920383920323333203234312033352033375D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc001610360, staking}" version=0
12:28AM ERR [supervysor] could not get node height err="could not get node height, exiting ..."
Error: signal: terminated
12:28AM ERR error="signal: terminated" module=cosmovisor
Error: could not get node height, exiting ...
Usage:
  supervysor start [flags]
Flags:
  -h, --help   help for start
osmosisd.service: Main process exited, code=exited, status=1/FAILURE
osmosisd.service: Failed with result 'exit-code'.
osmosisd.service: Consumed 5min 2.637s CPU time.
osmosisd.service: Scheduled restart job, restart counter is at 3.
Stopped osmosisd node service.
osmosisd.service: Consumed 5min 2.637s CPU time.
Started osmosisd node service.
12:29AM INF [supervysor] starting initially
12:29AM INF [supervysor] initial process started pId=4150398
12:29AM ERR [supervysor] failed to query height. Try again in 20s ... (1/10)
12:29AM INF running app args=["start","--p2p.seeds","400f3d9e30b69e78a7fb891f60d76fa3c73f0ecc@osmosis.rpc.kjnodes.com:12959,ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:12556","--home","/home/cosmos/.osmosisd","--x-crisis-skip-assert-invariants"] module=cosmovisor path=/home/cosmos/.osmosisd/cosmovisor/upgrades/v5/bin/osmosisd
12:29AM INF starting ABCI with Tendermint
12:29AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B32303420323036203531203230332037203137362032313220363420393120322031343820313334203339203135352038372031313120353320313037203130342032323220323237203635203137352031393820323238203137312032323920383920323333203234312033352033375D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc001434650, staking}" version=0
12:29AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B31353320363220313835203233342031393220393920373320313930203139302033372038362031383920323335203139312031383520313031203931203139302031353820313320313438203232392031323520343420313536203232203138342034203337203235322035372036385D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc0014346e0, transfer}" version=0
12:29AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B5D3A307D is_lazy=false store_key="KVStoreKey{0xc001434770, txfees}" version=2383300
12:29AM INF Upgrading IAVL storage for faster queries + execution on live state. This may take a while commit=436F6D6D697449447B5B323435203720313133203938203136302036392036312031343620323337203238203530203139392031363120313237203538203632203333203737203135332031393520313434203131203930203636203139322038382032323420363520313937203630203433203231395D3A3234354443337D is_lazy=false store_key="KVStoreKey{0xc0014346c0, upgrade}" version=0
12:29AM INF Starting multiAppConn service impl=multiAppConn module=proxy
12:29AM INF Starting localClient service connection=query impl=localClient module=abci-client
12:29AM INF Starting localClient service connection=snapshot impl=localClient module=abci-client
12:29AM INF Starting localClient service connection=mempool impl=localClient module=abci-client
12:29AM INF Starting localClient service connection=consensus impl=localClient module=abci-client
12:29AM INF Starting EventBus service impl=EventBus module=events
12:29AM INF Starting PubSub service impl=PubSub module=pubsub
12:29AM INF Starting IndexerService service impl=IndexerService module=txindex
12:29AM INF ABCI Handshake App Info hash="Z\x11M��4\x01�����\x14L���2�\a�O��\x1e���\n�ٟ" height=2383299 module=consensus protocol-version=0 software-version=6.4.0
12:29AM INF ABCI Replay Blocks appHeight=2383299 module=consensus stateHeight=2383299 storeHeight=2383300
12:29AM INF Replay last block using real app module=consensus
12:29AM INF applying upgrade "v5" at height: 2383300
12:29AM INF Start running migrations
12:29AM INF Running migration for module: authz, InitGenesis (on default genesis) toVersion 1
12:29AM INF Running migration for module: bank, fromVersion 1, toVersion 2
12:29AM ERR [supervysor] failed to query height. Try again in 20s ... (2/10)
12:29AM INF Running migration for module: bech32ibc, InitGenesis (on default genesis) toVersion 1
12:29AM INF Running migration for module: distribution, fromVersion 1, toVersion 2
12:29AM INF Running migration for module: gov, fromVersion 1, toVersion 2
12:29AM INF Running migration for module: ibc, fromVersion 1, toVersion 2
12:29AM ERR [supervysor] failed to query height. Try again in 20s ... (3/10)
12:30AM INF Running migration for module: slashing, fromVersion 1, toVersion 2
12:30AM ERR [supervysor] failed to query height. Try again in 20s ... (4/10)
12:30AM INF Running migration for module: staking, fromVersion 1, toVersion 2
12:30AM INF Setting txfees module genesis with actual v5 desired genesis
12:30AM INF Now running migrations just for auth, to get auth migration to be last. (CC https://github.com/cosmos/cosmos-sdk/issues/10591)
12:30AM INF Start running migrations
12:30AM INF Running migration for module: auth, fromVersion 1, toVersion 2
12:30AM INF executed block height=2383300 module=consensus num_invalid_txs=17 num_valid_txs=0
12:30AM ERR [supervysor] failed to query height. Try again in 20s ... (5/10)
12:30AM ERR [supervysor] failed to query height. Try again in 20s ... (6/10)
12:31AM ERR [supervysor] failed to query height. Try again in 20s ... (7/10)
12:31AM ERR [supervysor] failed to query height. Try again in 20s ... (8/10)
12:31AM ERR [supervysor] failed to query height. Try again in 20s ... (9/10)
12:32AM ERR [supervysor] failed to query height. Try again in 20s ... (10/10)
12:32AM ERR [supervysor] could not get node height err="could not get node height, exiting ..."
Error: signal: terminated
12:32AM ERR error="signal: terminated" module=cosmovisor
Error: could not get node height, exiting ...
Usage:
  supervysor start [flags]
Flags:
  -h, --help   help for start
osmosisd.service: Main process exited, code=exited, status=1/FAILURE
osmosisd.service: Failed with result 'exit-code'.
osmosisd.service: Consumed 5min 58.721s CPU time.
osmosisd.service: Scheduled restart job, restart counter is at 4.
Stopped osmosisd node service.
osmosisd.service: Consumed 5min 58.721s CPU time.
Started osmosisd node service.
12:32AM INF [supervysor] starting initially
12:32AM INF [supervysor] initial process started pId=4165552
12:32AM ERR [supervysor] failed to query height. Try again in 20s ... (1/10)
12:32AM INF running app args=["start","--p2p.seeds","400f3d9e30b69e78a7fb891f60d76fa3c73f0ecc@osmosis.rpc.kjnodes.com:12959,ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:12556","--home","/home/cosmos/.osmosisd","--x-crisis-skip-assert-invariants"] module=cosmovisor path=/home/cosmos/.osmosisd/cosmovisor/upgrades/v5/bin/osmosisd
12:32AM INF starting ABCI with Tendermint
12:32AM INF Starting multiAppConn service impl=multiAppConn module=proxy
12:32AM INF Starting localClient service connection=query impl=localClient module=abci-client
12:32AM INF Starting localClient service connection=snapshot impl=localClient module=abci-client
12:32AM INF Starting localClient service connection=mempool impl=localClient module=abci-client
12:32AM INF Starting localClient service connection=consensus impl=localClient module=abci-client
12:32AM INF Starting EventBus service impl=EventBus module=events
12:32AM INF Starting PubSub service impl=PubSub module=pubsub
12:32AM INF Starting IndexerService service impl=IndexerService module=txindex
12:32AM INF ABCI Handshake App Info hash="Z\x11M��4\x01�����\x14L���2�\a�O��\x1e���\n�ٟ" height=2383299 module=consensus protocol-version=0 software-version=6.4.0
12:32AM INF ABCI Replay Blocks appHeight=2383299 module=consensus stateHeight=2383299 storeHeight=2383300
12:32AM INF Replay last block using real app module=consensus
12:32AM INF applying upgrade "v5" at height: 2383300
12:32AM INF Start running migrations
12:32AM INF Running migration for module: authz, InitGenesis (on default genesis) toVersion 1
12:32AM INF Running migration for module: bank, fromVersion 1, toVersion 2
12:33AM INF Running migration for module: bech32ibc, InitGenesis (on default genesis) toVersion 1
12:33AM INF Running migration for module: distribution, fromVersion 1, toVersion 2
12:33AM INF Running migration for module: gov, fromVersion 1, toVersion 2
12:33AM INF Running migration for module: ibc, fromVersion 1, toVersion 2
12:33AM ERR [supervysor] failed to query height. Try again in 20s ... (2/10)
12:33AM ERR [supervysor] failed to query height. Try again in 20s ... (3/10)
12:33AM INF Running migration for module: slashing, fromVersion 1, toVersion 2
12:33AM INF Running migration for module: staking, fromVersion 1, toVersion 2
12:33AM INF Setting txfees module genesis with actual v5 desired genesis
12:33AM INF Now running migrations just for auth, to get auth migration to be last. (CC https://github.com/cosmos/cosmos-sdk/issues/10591)
12:33AM INF Start running migrations
12:33AM INF Running migration for module: auth, fromVersion 1, toVersion 2
12:33AM INF executed block height=2383300 module=consensus num_invalid_txs=17 num_valid_txs=0
12:33AM ERR [supervysor] failed to query height. Try again in 20s ... (4/10)
12:34AM ERR [supervysor] failed to query height. Try again in 20s ... (5/10)
12:34AM ERR [supervysor] failed to query height. Try again in 20s ... (6/10)
12:34AM ERR [supervysor] failed to query height. Try again in 20s ... (7/10)
12:35AM ERR [supervysor] failed to query height. Try again in 20s ... (8/10)
12:35AM ERR [supervysor] failed to query height. Try again in 20s ... (9/10)
12:35AM ERR [supervysor] failed to query height. Try again in 20s ... (10/10)
12:36AM ERR [supervysor] could not get node height err="could not get node height, exiting ..."
Error: signal: terminated
12:36AM ERR error="signal: terminated" module=cosmovisor
Error: could not get node height, exiting ...
Usage:
  supervysor start [flags]
Flags:
  -h, --help   help for start
osmosisd.service: Main process exited, code=exited, status=1/FAILURE
osmosisd.service: Failed with result 'exit-code'.
osmosisd.service: Consumed 6min 27.139s CPU time.
osmosisd.service: Scheduled restart job, restart counter is at 5.
Stopped osmosisd node service.
osmosisd.service: Consumed 6min 27.139s CPU time.
Started osmosisd node service.
12:36AM INF [supervysor] starting initially
12:36AM INF [supervysor] initial process started pId=4180880
12:36AM ERR [supervysor] failed to query height. Try again in 20s ... (1/10)
12:36AM INF running app args=["start","--p2p.seeds","400f3d9e30b69e78a7fb891f60d76fa3c73f0ecc@osmosis.rpc.kjnodes.com:12959,ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:12556","--home","/home/cosmos/.osmosisd","--x-crisis-skip-assert-invariants"] module=cosmovisor path=/home/cosmos/.osmosisd/cosmovisor/upgrades/v5/bin/osmosisd
12:36AM INF starting ABCI with Tendermint
12:36AM INF Starting multiAppConn service impl=multiAppConn module=proxy
12:36AM INF Starting localClient service connection=query impl=localClient module=abci-client
12:36AM INF Starting localClient service connection=snapshot impl=localClient module=abci-client
12:36AM INF Starting localClient service connection=mempool impl=localClient module=abci-client
12:36AM INF Starting localClient service connection=consensus impl=localClient module=abci-client
12:36AM INF Starting EventBus service impl=EventBus module=events
12:36AM INF Starting PubSub service impl=PubSub module=pubsub
12:36AM INF Starting IndexerService service impl=IndexerService module=txindex
12:36AM INF ABCI Handshake App Info hash="Z\x11M��4\x01�����\x14L���2�\a�O��\x1e���\n�ٟ" height=2383299 module=consensus protocol-version=0 software-version=6.4.0
12:36AM INF ABCI Replay Blocks appHeight=2383299 module=consensus stateHeight=2383299 storeHeight=2383300
12:36AM INF Replay last block using real app module=consensus
12:36AM INF applying upgrade "v5" at height: 2383300
12:36AM INF Start running migrations
12:36AM INF Running migration for module: authz, InitGenesis (on default genesis) toVersion 1
12:36AM INF Running migration for module: bank, fromVersion 1, toVersion 2
12:36AM INF Running migration for module: bech32ibc, InitGenesis (on default genesis) toVersion 1
12:36AM INF Running migration for module: distribution, fromVersion 1, toVersion 2
12:36AM INF Running migration for module: gov, fromVersion 1, toVersion 2
12:36AM INF Running migration for module: ibc, fromVersion 1, toVersion 2
12:37AM ERR [supervysor] failed to query height. Try again in 20s ... (2/10)
12:37AM INF Running migration for module: slashing, fromVersion 1, toVersion 2
12:37AM ERR [supervysor] failed to query height. Try again in 20s ... (3/10)
12:37AM INF Running migration for module: staking, fromVersion 1, toVersion 2
12:37AM INF Setting txfees module genesis with actual v5 desired genesis
12:37AM INF Now running migrations just for auth, to get auth migration to be last. (CC https://github.com/cosmos/cosmos-sdk/issues/10591)
12:37AM INF Start running migrations
12:37AM INF Running migration for module: auth, fromVersion 1, toVersion 2
12:37AM INF executed block height=2383300 module=consensus num_invalid_txs=17 num_valid_txs=0
12:37AM ERR [supervysor] failed to query height. Try again in 20s ... (4/10)
12:38AM ERR [supervysor] failed to query height. Try again in 20s ... (5/10)
12:38AM ERR [supervysor] failed to query height. Try again in 20s ... (6/10)

Thoughts about solution

gather data from the targeted chain with the list of upgrade blocks: even if not possible to parse then just create a manual config file with map of upgrades
update halt-height to "upgrade block - N" value
once halt height is reached turn off reboot functionality and wait until "upgrade block + N"
when "upgrade block + N" is reached turn reboot on again
update halt-height to the next value if exists

With #5, this will be resolved due to the exponential backoff. Due to the longer timeframe, nodes will have the chance to perform big upgrades when running with the Cosmovisor.
However, can you explain how you did end up in an endless loop?

After each 10 retires the node was restarted and once up it is trying to migrate again and again, and the time dedicated to 10 retries is not enough.
As I understand 12:37AM INF executed block height=2383300 module=consensus num_invalid_txs=17 num_valid_txs=0 such 1st block after the upgrade can take much more time to be processed

This behaviour should be prevented by a longer upgrade timeframe.
Due to the potential big timeframe, I will increase the BackoffMaxRetries to 15 so the node has more than 16 hours to upgrade successfully before the supervysor exits.


How to input multi files

I see the options says 'javascript files'. But when I enter the command 'nexe -i a.js b.js', it seems useless. So how can I input multi files, or its impossible?
-i, --input    The entry javascript files

Hi! This is a failure on my part of documentation. You'd want to just require('b.js') and it would be automatically bundled into your project. Thanks!


Auto select an input text search term when blur

Hi
I use select2 for tag user selection on Ajax
I am using a createSearchChoice for adding the search term for the selection list if there are no items.
But sometimes the server is slow for query, while ajax is calling the user tab to another textbox, and they want the select2 select this input text search term that they type before.
How can I do it.

This is effectively a duplicate of https://github.com/select2/select2/issues/2231, as they both point back to the same issue.


Streama Video Player

you can update the Streama video player project with file of this Streama Version Player? Because this version the player work correctly but on the project streama video player not work correctly

Perhaps the video player should be placed inside the main repo as a submodule?


pkg/controller/gitopsconfig: update Status based on informers (#217)

Description

This PR changes the mechanism for updating the Status field of
GitOpsConfig from cron (pull-based) to informers (push-based).
The implementation in this PR is unfortunately not ideal. I
encountered many challenges when developing it, and in the end took
compromises in some aspects. Specifically:

Status is now calculated based on single Job's data received from
Informer. As such, this makes Status calculations "edge-based",
instead of "level-based", with the latter being the recommended
approach for Kubernetes apps. In case Informer misses some changes
(for example, potentially in case of lost network connection), we may
miss recalculating some GitOpsConfig Status transition.
I tried changing this approach to "level-based". In OnUpdate, I tried
List-ing all Jobs belonging to GitOpsConfig, and calculating Status
based on the newest one among them. However, to my surprise, List was
giving me stale data from Kubernetes. I considered adding an extra
cron-like task, that would periodically recalculate Status for all
GitOpsConfig CRs; however, it's not yet clear to me how to implement
it in a stateless and robust way in eunomia.
In the end, I reverted back to the "edge-based" approach as shown in
this PR, finding it the simplest implementation for now, while
seemingly (to my surprise) giving robust results. I am considering a
theory, that maybe the Informers infrastructure is robust enough that
it takes some complexity from its users.

Setting GitOpsConfig Status can currently fail in case the CR was
modified between the Get() and Status().Update() calls. Current
implementation doesn't do any retries in such case, thus making it
possible for Status to become stale and incorrect.
However, it's not clear to me how to implement retries correctly.
I expect retries shouldn't block the OnUpdate function with
Sleep-like mechanism, as that would risk stalling that part of
eunomia. Also, I am not sure how to do it in a stateless way, such
that it would retry also in case eunomia is restarted in meantime.
Again, I would consider trying to use a cron-like mechanism here,
possibly as complementary to "fast" edge-based updates. However, I
see challenges in how to implement such cron well in a stateless and
scaling-safe way, so I decided to not do it yet, and bring it up to
discussion.

As a potential workaround, if nobody comes up with a better idea, I
would like to propose adding a background thread in eunomia, repeatedly
picking a random GitOpsConfig from the cluster, and recalculating its
Status. That could be a method to achieve eventual consistency, though
in a non-deterministic way.
Additionally, through the course of implementing this feature, I came to
believe it would be good to simplify tracking the relation between
GitOpsConfig, and Jobs it spawns, by marking the Jobs with a new label,
with GitOpsConfig name as its value. This would simplify the "owner
detection" code in numerous places in eunomia, currently done in
numerous different ways, and also make it simpler and more future-proof.
I wanted to make it part of the work done in this PR, but I decided
to postpone it for now, as implementing this feature as is was already
taking me too long.

Partially implements #217
Type of change

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] Unit tests and e2e tests updated
[ ] Documentation updated

@akavel I like this being stateless and some remediation task running in the background to "self-heal" anything that got out of whack.
Wouldn't we need that logic anyway if the pod get restarted? We need to expect Eunomia to go down at any point in time and then being able to pick up where it left off.
Worst case you could leverage configmaps to write out some kind of status to get a bit more stateful, but I'm not a huge fan of it. It might be better to have a shared filesystem between the pods to accomplish this.

Also if this doesn't get merged before the release, then I please need #242 merged in the interim.

Looks pretty good. I believe this much closer to the correct way for updating .status than what we had before.
But I see that go vet is failing. Can you please address these issues listed by go vet from the Travis CI run ...
https://travis-ci.com/KohlsTechnology/eunomia/builds/144404755#L771-L784


The small red part

Please consider submitting the following information (if relevant):

Library setup method: CocoaPods.
Version of the library. Example: 5.0.1.
Xcode version. Example: 9.4.1.
OS version. Example: iOS 11.4.

The small red part that appears to be cut off on the top right always pops up. What should I do in order to remove it?

Thank you!

Thanks for reporting @elibooklover. This is really weird, I've never seen such thing before. I don't know what is causing it. Do you think you can make a simple demo app that recreates this bug and attach it here? So I can have a look?

Thanks for your comments. I figured out why it happened. I added the badge by using both codes and the label. Since I removed the label, it disappeared. Thanks!

I'm glad you figured it out! 👍


missing viewBox methods...

What is the best way to patch viewBox attributes in SVGs to implement baseVal?
https://developer.mozilla.org/en-US/docs/Web/API/SVGMarkerElement/viewBox

@swamidass do something similar that has been done for class and className accessor in the svg element file.
Please remember to add tests or it won't pass without 100% code-coverage 👋


Unable to use plugin

Unable to use the plugin
After installing the theme and setting it as colour theme, it does not work, is there something wrong with my config ?
  plugins = {
    init = {
      {
        "folke/tokyonight.nvim",
        as = "tokioo",
      },
       },
    },

is it too dark and weird like mines ?

Can you be more specific on what's not working?
Also, I have no idea what that code means. Lunarvim or some other distro?
Are you sure the plugin is loaded?
What happens if you do colorscheme tokyonight?

I accidentally commited a change earlier today that only worked on Neovim 0.8, so that might also be the issue you had. Please update and check if it works now.

@folke could you by any chance know why the colorscheme is different in tmux and in regular ubuntu terminal ?

@kx0101 you need a terminal that supports native full colors. Also make sure termguicolors is set inside neovim.

I can't use the plugin neither after an update and here's the error I got:
                    Error detected while processing /home/yoeight/.local/share/nvim/site/pack/packer/start/tokyonight.nvim/colors
/tokyonight.lua:
W18: Invalid character in group name
W18: Invalid character in group name
Press ENTER or type command to continue

same

Turns out my issue got fixed by https://github.com/folke/tokyonight.nvim/issues/207 but I can no longer use the day style. I'm opening a different issue.

@folke yes I'm using Astro vim, when I set 'colorscheme = tokionight' nothing happens, it just defaults to the default color scheme 🫠

I'm am sure the plug-in is installed

@b1twe1ser no idea how astrovim loads modules. You'll have to check there to see what's wrong

Alright thank you for your assistance 🫡


Reused stateful widget constructor event listening can lead to EventEmitter leak

In a stateful widget, it might be necessary to listen to the destroy event. In most cases you register a destroy listener in the constructor.
For example:
init: function() {
    this.on('destroy', function(event) {
        // do something
    });
}

Every time the widget is re-rendered, this triggers the init function to be called for the same widget.
If widget is repeatedly re-rendered due to state change, this error will be triggered:
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.

This is a workaround but I'm not really happy with it:
init: function() {
    if (!this._initialized) {
        this._initialized = true;
        this.on('destroy', function() {
            // do something
        });
    }
}

Wanted to see if there's a cleaner way to write code that should be only ran the first time the widget is created.

What are your thoughts on adding support for an initOnce() method? The initOnce() method would only be called once while the init() method would be called every time a widget is updated.

personally, I would love to see a initOnce() method! I have a few things were I need the workaround @philidem mentioned.

I'm wondering if destroy event should fire when the widget is being re-rendered (even if it is reusing the old widget). I think we need to do a little work to make this less confusing. I personally find it strange that init for a single widget will be called multiple times.
If we're not going to emit destroy event when re-rendering then we might want to support:

init called during first construction
onUpdate called after each update due to re-rendering

So if you need to handle any DOM changes after re-rendering then maybe onUpdate would be the right place to do that (not in the one-time constructor init function).

@philidem good question... I am not even sure about when the destroy event fires... (never used it so far...) I would assume that it fires when the DOM behind the component will be removed... so re-rendering the widget should not fire the destroy event...
For your specific case couldn't you just use the onDestroy() method for widgets??? Although it does not seem to be documented, it is mentioned in our FAQ. (https://github.com/marko-js/marko-widgets/blob/master/docs/faq.md#which-component-functions-are-invoked-at-what-time---whats-the-order-of-invocation)

The reason that I think that destroy/onDestroy should happen during re-render based on current design is because it would mirror when init (the constructor-like function) is called. If the widget went through the destroy lifecycle event then the listener subscriptions would be removed (and that would have solved my original problem).
However, I still think that neither init or destroy should happen during re-render. I think if the end-user wants to handle DOM changes due to re-render then they should do that in onAfterUpdate.
So hopefully I can convince you all to change the design so that init is not called during re-render :) I know that might be breaking change but I think it would be worth it.

It looks like the main problem that I was seeing as far as destroy not being called was actually due to installing raptor-dom at the root of my project.
The hairy details:
raptor-dom and marko-widgets both need to use the same raptor-pubsub. When raptor-dom was installed as root module in my project, it didn't find raptor-pubsub because my project did not have raptor-pubsub installed and neither did raptor-dom. When you install marko-widgets it will also include raptor-pubsub as the dependency and this is the one that you want marko-widgets and raptor-dom to share.
Workaround:
use require('marko-widgets/dom') to access the raptor-dom module from your project and don't install raptor-dom into your project as a top-level dependency.
I'm going to close this issue for now and let's revisit the init/destroy flows in the future.

It seems reasonable to make init() only be called once for the entire life of the widget. I think it is definitely something we should consider for the next major version of marko-widgets.
Regarding raptor-pubsub, I am surprised you are seeing issues since raptor-pubsub creates a global variable for that very reason:
https://github.com/raptorjs/raptor-pubsub/blob/419231e0b88ee6201ae21d4519f76d256af42dae/lib/index.js#L3

Just chiming in a +1 for some implementation of initOnce(). I've run into usecases where I re-render part of a widget very often and would prefer some separation of the the actual initialization versus updating.

I'm trying to use the workaround in the first post but it seems like this._initialized reverts back to undefined during every init, so the condition is always satisfied.
Does this workaround still work in marko v5, or can initOnce() be used now?

Hey @hliang93, with the Marko v5 release we changed the behavior:

The init() constructor for a widget is only called once even if a widget is rerendered

Please see:
https://github.com/marko-js/marko-widgets/blob/master/CHANGELOG.md#breaking-changes
Therefore, the workaround to prevent the constructor being invoked multiple times should not be necessary. Are you seeing a widget constructor being invoked multiple times?

I see it being invoked twice.
I am currently trying to make D3 charts out of components in Marko. For my line chart, I have a component called data-series whose template looks like this:
<g w-bind>
    <line-path path="$data.path" />
</g>

In init(), the component creates a SVG path out of some fake data and then sets the state:
this.setState({
            'path': path,
...

The SVG path is then passed to the line-path widget through getTemplateData:
   getTemplateData: function(state) {
        return {
            path: state.path
        }
    },

The line-path widget takes the path prop and inserts it into the template to render a SVG path (this is the 'line' of the line chart):
getTemplateData: function(state, input) {
        console.log(input);
        return {
            path: input.path
        }
    },

  <path d=${data.path} class="line" />
However, the line does not show up when I use setState to set the path property, and init appears to run twice. The line shows up properly if I do the path-genertion inside getTemplateData instead of using setState.

Hey @hliang93, would you be able to setup a minimal project for reproducing the issue? It could be a bug, but we do have tests to make sure the init() function is only invoked once.

Sure! I'm also at eBay Orchard, so maybe I could ping you later. :-)

Here is the repo, I hope it is minimal enough: https://github.com/hliang93/marko-d3
I had used one of the Marko samples ("widget communication") as my initial seed.

Same Issue is happening with me also


Day455

Resolves #919.

Pull Request Test Coverage Report for Build 1709

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1707:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


pull request for e2e test at 01/09/2017 19:45:06

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


Fix version of regenerator-runtime

7.7.7 is version of @babel/runtime, not regenerator-runtime. Looks like the intended version was "0.11.0" as you can see in the yarn.lock:
<EMAIL_ADDRESS>  version "0.11.1"
  resolved "https://registry.yarnpkg.com/regenerator-runtime/-/re...
  integrity sha512-MguG95oij0fC3QV3URf4V2SDYGJhJnJGqvIIgdECeODCT9...

Reference:

https://github.com/swc-project/swc/commit/05be89c19

LGTM
bors r+

bors retry

bors r+


Add displaySuccess and displayError method

displayError just duplicate the display method for not deprecated the old one
displaySuccess is for display a success massage using class= 'alert alert-success'
if there is something to show after error it maybe better to have something to show after sucess!

the current display method can be used for both errors and success message and change the class used by passing the class to be used as a second param, what you've proposed it duplicating functionality.
For displaying a dedicated success message it would be better to use a session that way you can display the success message one time then it clears. That way you don't see the same message again unless the event happens again.
In the sessions helper class is a method called message:
/**
     * display message
      * @return string return the message inside div
     */
    public static function message($sessionName = 'success')
    {
        $msg = Session::pull($sessionName);
        if (!empty($msg)) {
            return "

                    <button type='button' class='close' data-dismiss='alert' aria-hidden='true'>×</button>

 ".$msg."

";
        }
    }

Thank you. sir :)


works with MSS110

Just wanted to let you know that I tested this with the MSS110 and it works out of the box. I was getting the info together to add support for it but found that the payload is already identical.
Figured I'd let you know in case you wanted to add it to the notes.
Cheers.

Thanks @ianwaldrop for this hint!


Refactor to use Async Methods

We should think about refactoring our endpoints to be Async. This can help us with speed, etc.

Removing discussion tag now that It is required for #10, and #10 is a security vulnerability so it's required.


Remove redundant jobs from Kubernetes agent GHA

Background
These were required because we had required checks on them but now they can be removed.
[sc-82969]

☝ No changeset required as we're just adjusting the GHAs

@kevjt Required checks come from repository configuration which is managed via https://github.com/OctopusDeploy/GithubBranchProtections
I adjusted the required checks here: https://github.com/OctopusDeploy/GithubBranchProtections/pull/752
and I added branch protections for release branches here: https://github.com/OctopusDeploy/GithubBranchProtections/pull/753


Add paging feature on AllPosts of Dashboard

10 items per page on Dashboard/AllPosts

Added by https://github.com/ymita/Lifelog/commit/8b8a4a7d9449e905aea60eb9a90b4174036c5348.


Ubuntu 22

I Face error during installation

This is a duplicate of https://github.com/rajannpatel/ubuntupbx/issues/3
The resolution was found, the install.sh script has been updated 3 weeks ago with commit b4e3f8012de92e7d266e83936e4e5c4a4390aefb. I am unable to reproduce this issue on a LXD container or on a public cloud virtual machine.
Please reopen issue #3 if you continue having issues.

https://github.com/rajannpatel/ubuntupbx/blob/main/jammy/install.sh


Conversion to and from static arrays

This is motivated mainly to allow a seamless interaction with piston libraries. Piston internally uses https://github.com/PistonDevelopers/vecmath, which are generic functions on static arrays ([T, ..n] or [[T, ..n], ..m]). Thus to interface with the libraries it is crucial to be able to convert vectors and matrices to and from static arrays seamlessly.
I don't know whether this warrants changing the internal representation to arrays. Transitioning from cgmath I find this a bit cumbersome to work around.

Maybe I'm missing something here, but isn't implementing From<[T; N]> and Into<[T; N]> for e.g. VecN<T> sufficient?

You're correct, implementing those two traits is the way to go! They did not exist (and neither did DSTs) when this issue was created.

Into and From are now implemented for matrices and vectors since v0.11.1. For other structures, the user can access their vector or matrix representations (and then use Into and From) if needed. Closing this.


OpenCL Header only Dynamically Opened ICD Loader Proposal

This is a (full fledged, functional) straw-man proposal of an implementation of one of @bashbaug ideas for easing OpenCL ICD loader issues. These headers allow an OpenCL application to be built normally or with the -DOPENCL_LOAD flag active. In this case, linking with the loader is not necessary anymore as it is opened dynamically.
The title is slightly misleading as ONE source file from the project must also include the CL/opencl_load_lib.h to have a single definitions of the global variables used. (on windows this could go away as on MSVC inline functions can declare non const static variables).
This allows:

Functions failing with an error code if the loader cannot be found
Functions failing with another error code if the loader does not export the required function
Using outdated loader while still using the loader for dispatch, layers are working
It should be able to load a non khr_icd driver

This does not allow an application to:

Use recent OpenCL functions on an outdated loader: function will return an error
Avoid segfaulting when carelessly calling newer functionalities from an outdated implementation

The last point could be fixed using indirect dispatch in the loader.
I will add CI tests for it.

Cool!  This looks like a mix between the previous Static Lib with Dynamic Loader and ICD Loader Header File proposals.  Having working code to play around with and demonstrate that it works is awesome.
Out of curiousity are you generating these files, or did you author them manually?  I think it should be possible to generate most of them.
I think we mostly need to figure out which solution (or solutions, this doesn't need to be one-size-fits-all) we want and then start adding them to the SDK / CI / etc.  There are clearly lots of different options, with different pros and cons.
Note that there are some aspects of this PR that we may want to adopt regardless, for example it looks like we both added some sort of a define to control linkage in the header file - see CLLD_INLINE in this PR and CL_API_LINKAGE in my proposal.

Cool! This looks like a mix between the previous Static Lib with Dynamic Loader and ICD Loader Header File proposals. Having working code to play around with and demonstrate that it works is awesome.

Thanks, I didn't knew about those (only about your presentation, I didn't find pointer to code in it), I will need to study them, they look great.

Out of curiousity are you generating these files, or did you author them manually? I think it should be possible to generate most of them.

I did not generate them yet because I wanted to do a full pass on the headers to be sure not to miss something. There are some strange inconsistencies:

Some APIS/extensions not behind version guards: if we generate the headers we may end up adding all the correct guards and maybe break some codes. Do we want to do this?
Windows extensions not having a function declaration but only function pointers, whereas all other loader extensions have function declarations. It broke my assumption that extensions functions present in the loader were declared in the headers (to be able to link with the loader), while other had function pointers types declarations. This led me to extract the function definitions from the cl_icd.h file to avoid forcing the inclusion of directx headers/extensions when compiling for windows, as I assumed without declaration nobody ever linked with those directly. It also led to my remark in https://github.com/KhronosGroup/OpenCL-Headers/pull/161#issuecomment-841745608.
We need to decide if we want to keep the deprecation prefixes/suffixes on function definitions, especially if they are inline. The function typdefs from https://github.com/KhronosGroup/OpenCL-Headers/pull/161#issuecomment-841745608 would help handling this more cleanly by I am unsure they will appeal to everyone.

I think we mostly need to figure out which solution (or solutions, this doesn't need to be one-size-fits-all) we want and then start adding them to the SDK / CI / etc. There are clearly lots of different options, with different pros and cons.

Yes, hopefully this one will help accomplish this goal. For this work there is some thread safety involved, so maybe using it to run the conformance test may be better (though I don't know how much parallel testing the conformance tests do). We also need some way to be able to install a working driver on windows image in GitHub actions. Ubuntu is easy, MacOS can work (with reservations), but for now I don't have a solution for windows...

Note that there are some aspects of this PR that we may want to adopt regardless, for example it looks like we both added some sort of a define to control linkage in the header file - see CLLD_INLINE in this PR and CL_API_LINKAGE in my proposal.

I agree with you completely. I started with a slighly more complex proposal initially that allowed even more flexibility, by having non static inline functions with extern declarations in the library. And you could switch between static inline/inline mode. This may be desirable and could allow to adapt the scheme to more exotic platforms.


Disable output shown in console

Is there any way to disable that the result of an command request is shown in console, too?
If not, pls add :)

Are you referring to requests to the /cmd endpoint?

Yes

Using ur commands.js from https://github.com/Valandur/Web-API/blob/master/docs/CONSUME.md

This will be in the next release! :+1:


[Candidate 1v1 Drallim Desert v1] Sphinx objects in map corners look strange as they extend way into the black border

Issue Description
Sphinx objects in map corners look strange as they extend way into the black border.
Expected behavior
Smaller object not extending map boundaries would look better.
Screenshots

Issue obsolete. Map moved to back log: https://github.com/xezon/GeneralsRankedMaps/commit/6bcc17399631e515e562ee6acec3a3d520a0ff07

Fixed with https://github.com/xezon/GeneralsRankedMaps/commit/19757aa402ad82087d312cf09502d15fecaba13f


Match text of error

Would it be possible to expose the error text for possible matching? Something along the lines of
interface Person {
  name: string;
  age: number;
}
type PersonWithAllPropertiesOptional = Partial<Person>;
const person1: PersonWithAllPropertiesOptional = {}; // OK

// OK
const person2: PersonWithAllPropertiesOptional = {
  name: 'Me',
};

// OK
const person3: PersonWithAllPropertiesOptional = {
  name: 'Me',
  age: 123,
};

const person4: PersonWithAllPropertiesOptional = {
  name: 'Me',
  age: 123,

  // $ExpectError: Type '{ name: string; age: number; foo: string; }' is not assignable to type 'Partial<Person>'.
  foo: 'foo',
};

const person5: PersonWithAllPropertiesOptional = {
  name: 'Me',
  age: 123,

  // $ExpectError: Type '{ name: string; age: number; foo: string; }' is not assignable to type 'Partial<Person>'.
  foo: 'foo',
}

I figure matching any part of any line of error text is the correct amount of matching. Happy to take a stab at it if it's something the library would be interested in incorporating.

+1
Alternatively, I would at least want to be able to write a comment explaining why an error is expected. But currently, sth like // $ExpectError (because it's the wrong data type) would be completely ignored, i.e. the assertionis not executed. Because allowing it now could in future break users who wrote something there, an intermediate syntax could be // $ExpectError // blabla, i.e. an extra comment after the first one.


view terminology

Hey guys, just checking out your library for the first time, so feel free to close this due to early ignorance, but I just wanted to discuss your concept of the "view" terminology.
Since views are a well established keyword/role in Rails, why do you override the term with the view method, instead of using something more unique? FactoryBot uses the term traits for this same purpose. Or you could use the "branding" of a blueprint from the construction industry and do something like "layer", "cross section", or "floor".
😃

No problem, glad to discuss!
You're right that view has an established usage in Rails, however I also think that the same meaning of view already in Rails can be used in the context of Blueprinter. Just like you would create HTML views that you expect ActionController to render, you also create JSON views for Blueprinter to render.
While using unique terminologies might be nice, if the terminologies are too unique, it might become harder for people to understand what the methods are actually used for. The README.md would be larger as we would have to explain all the new terminologies we are using.

Closing for now, feel free to reopen if you or anyone else thinks it warrants more discussion.


igdm

hello, I'm having an issue with igdm because I can't enter to a group chat, and sometimes I send a mesage to a person and another person recieves it instead. please fix this, it's the only way of comunication I have!! thank you

hello, I'm having an issue with igdm because I can't enter to a chat, and sometimes I send a mesage to a person and another person recieves it instead.


v8 Updates for First MVC series

Update First MVC 10 tutorial series for .NET 8 and fix additional open issues where I can.
Fixes #28669, #28960, #29004, #28591, #28379, #29007
Since VS for Mac Preview (nor Stable version) does not work yet for .NET 8 as of preview 3, the tabs for VS for Mac have text indicating to use the .NET 7 version of the doc, as we did for version 6 in the same situation.

Internal previews
Toggle expand/collapse

📄 File
🔗 Preview link

aspnetcore/tutorials/first-mvc-app/adding-controller.md
[Visual Studio for Mac](https://review.learn.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/adding-controller?branch=pr-en-us-29115)

aspnetcore/tutorials/first-mvc-app/adding-model.md
[Visual Studio Code / Visual Studio for Mac](https://review.learn.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/adding-model?branch=pr-en-us-29115)

aspnetcore/tutorials/first-mvc-app/adding-view.md
[Visual Studio for Mac](https://review.learn.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/adding-view?branch=pr-en-us-29115)

aspnetcore/tutorials/first-mvc-app/controller-methods-views.md
Part 6, controller methods and views in ASP.NET Core

aspnetcore/tutorials/first-mvc-app/details.md
Part 10, examine the Details and Delete methods of an ASP.NET Core app

aspnetcore/tutorials/first-mvc-app/new-field.md
[Visual Studio Code / Visual Studio for Mac](https://review.learn.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/new-field?branch=pr-en-us-29115)

aspnetcore/tutorials/first-mvc-app/search.md
Part 7, add search to an ASP.NET Core MVC app

aspnetcore/tutorials/first-mvc-app/start-mvc.md
[Visual Studio for Mac](https://review.learn.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/start-mvc?branch=pr-en-us-29115)

aspnetcore/tutorials/first-mvc-app/start-mvc/sample/ReadMe.md
aspnetcore/tutorials/first-mvc-app/start-mvc/sample/ReadMe

aspnetcore/tutorials/first-mvc-app/validation.md
Part 9, add validation to an ASP.NET Core MVC app

aspnetcore/tutorials/first-mvc-app/working-with-sql.md
[Visual Studio Code / Visual Studio for Mac](https://review.learn.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/working-with-sql?branch=pr-en-us-29115)

In draft until actually set for review.  Still updating the code samples/snippets at the moment...

In draft until actually set for review.  Still updating the code samples/snippets


community-operators [CI] 3scale-community-operator (0.7.0)

Add reviewers list to ci.yaml for 3scale-operator community

/test all

/test all

/merge possible


Merge composed bundle environment into Ruby object

Motivation
Closes #1767, closes #1785
Merge the composed bundle environment into the workspace's Ruby object. The language server sets up the composed bundle environment, returns it, and then we merge that into the Ruby object to ensure that any other parts of the extension are using the exact same environment.
This fixes a few issues people have been experiencing with the debug client.
Implementation
Started merging the composed environment into the Ruby object and then started relying on that for the debug client.
Automated Tests
Added some tests. I will follow up with another PR that creates an integration test for a scenario that currently fails.

Merge activity

Nov 20, 3:08 PM EST: A user merged this pull request with Graphite.


Disabling "Show Pay with Amazon Button on Cart" removes "Pay with Amazon" button from checkout page

When I disable "Show Pay with Amazon Button on Cart" the "Pay with Amazon" button disappears from the checkout page too. Without the button users are not able to log in during the checkout process anymore.

@MichaelThessel Can I get a screen shot of the before and after for this to understand?
We will take this for the next sprint to fix


Performance with User mapping file

Hi I've been reading and using the SPMT tool at a customer and I'm trying to understand if there is any performance improvement if I use a User Mapping file or the Auto Mapping Feature.
Can you propose any guidelines, Also there is no guidance on how to generate the User mapping file , perhaps we can give links to exporting users from SharePoint / File Server and exporting AAD  + Vlookup in excel etc.

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

ID: 30e1dc7e-46ae-1b74-a205-e6f75a1f4cdd
Version Independent ID: e1e8803a-0190-429e-fa3f-4a410bf580c0
Content: Improve SPMT or Migration Manager agent performance - Migrate to Microsoft 365
Content Source: migration/SPMT-performance-guidance.md
Service: sharepoint-online
Sub-service: sharepoint-migration
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

Hello @jasonwbaxter
About the first question, I am trying to find out if there is any performance improvement.
About the 2nd one, I guess you already visited https://learn.microsoft.com/en-us/sharepointmigration/create-a-user-mapping-file-for-data-content-migration
what else would you like to see there? how to get the SID of a user/group, for example?
Thanks for clarifying

Thanks Andres
I think we can add some guidance here to remove orphaned users from SharePoint. And then to script out the users from AAD / SP to help with the CSV file.
What I'm seeing is that there are many users that have left an organisation but they still reside in sharePoint , and during the migration it checks several times for a matching user, for a large org with thousands of users this severely slows down the migration.
If you need to have a meeting with me you can see my availability from My Online Schedule @.***/bookings/> and book the respective meeting.
Kind regards
Jason Baxter
he/him
Customer Engineer
Customer Success Unit - Modern Work
Office: +27113618866tel:+27113618866
Mobile: +27762490644tel:+27762490644
<EMAIL_ADDRESS>[Microsoft Logo]

From: Andres Mariano Gorzelany @.>
Sent: Wednesday, October 26, 2022 7:01 PM
To: MicrosoftDocs/OfficeDocs-SharePoint @.>
Cc: Jason Baxter @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SharePoint] Performance with User mapping file (Issue #3484)
Hello @jasonwbaxterhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjasonwbaxter&data=05|01|Jason.Baxter%40microsoft.com|7bb65cad729749a04e1c08dab773b771|72f988bf86f141af91ab2d7cd011db47|1|0|638024004907951343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=E5Jhbl%2Flb2e%2FZWk0o5Me2tHoFHVXg24VtKdJ5clAHSg%3D&reserved=0
About the first question, I am trying to find out if there is any performance improvement.
About the 2nd one, I guess you already visited https://learn.microsoft.com/en-us/sharepointmigration/create-a-user-mapping-file-for-data-content-migrationhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fsharepointmigration%2Fcreate-a-user-mapping-file-for-data-content-migration&data=05|01|Jason.Baxter%40microsoft.com|7bb65cad729749a04e1c08dab773b771|72f988bf86f141af91ab2d7cd011db47|1|0|638024004907951343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=oKu2zU0i2O1f%2F4APMt127G5RnS9diUhuMGVkEft1aBo%3D&reserved=0
what else would you like to see there? how to get the SID of a user/group, for example?
Thanks for clarifying
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SharePoint%2Fissues%2F3484%23issuecomment-1292341837&data=05|01|Jason.Baxter%40microsoft.com|7bb65cad729749a04e1c08dab773b771|72f988bf86f141af91ab2d7cd011db47|1|0|638024004907951343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Fu8%2BESTszCjVeOViCLnj8%2FEp4KatWt4bCK%2Bbw1qzJWU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQJV2PCCIPRDYEWGPMSEAPDWFFPWJANCNFSM6AAAAAARJAFMOI&data=05|01|Jason.Baxter%40microsoft.com|7bb65cad729749a04e1c08dab773b771|72f988bf86f141af91ab2d7cd011db47|1|0|638024004907951343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=gJz4VuBUnX6wQ1AWIyRio4Gb92PeYcDbALV5CCDIEYA%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@scanum


Add s390x platform support for z-systems

@chef/engineering-services

@chef/chef-server-maintainers

Looks OK to me.  Any particular reason to use === over == here?

@stevendanna I think that's a typo :D

@stevendanna fixed the "===" please review. Thanks

👍 mwr

👍

:+1:


Make sure to keep font meta info on view recycling

Otherwise, the font info will be lost if it's not system default font

Thanks!


(CheckNumberOfSamples "true") can cause the registration to crash

Hi,
I am registering a mouse brain to a template, on Windows, using the following command:
elastix -f template.tiff -m ds_sample_200320_142837_25_25_ch01.tif  -out ./reg/vanilla -p 01_ARA_affine.txt -p 02_ARA_bspline.txt
When CheckNumberOfSamples is set to "true" in the second parameter file, the associated registration step crashes after a few hundred iterations ('elastix stopped working'); when I set (CheckNumberOfSamples "false") the registration completes.
The same data was registered by someone else without issue with (CheckNumberOfSamples "true") (other parameters are identical), with the same elastix version (5.0), on a Mac.
That parameter is not in the manual: is it simply a check, as the name suggests, so without any impact on the result?
I attached the elastix logs for the 2 scenarios, in case you want to have a look.
Best regards,
Adrien
elastix_log_check_true.log
elastix_log_check_false.log

Meet the same issue, I registered the human brain to template with affine and bspline transform.

The default of this parameter is True. If you set it to True and meet a crash, it means that your moving image and fixed image do not have enough overlap. If you write the output image after each resolution, you can visually check their overlap. Two ways you can try, 1) reduce the number of samples (NumberOfSpatialSamples 10000) 2) choose a smaller fraction of overlap samples (RequiredRatioOfValidSamples 0.1).

What this parameter does is check if enough samples map in the moving image domain. So, setting it to true is a wise thing. elastix should not segfault however when this check is on. Are you able to debug it?


Drag and drop of columns in nayjest data grid

Hello ,
Is it possible to make drag and drop of columns in nayjest data grid ?
Thanks Maja

Hi!
Yes it's possible but it's not related to functionality of Grids package. Grids package is responsible for rendering HTML tables & filtering-sorting data. Drag & Drop functionality can be implemented using JavaScript & this doesn't requires a lot from Grids package (maybe just getting some HTML element id's).


Cannot POST /<IP_ADDRESS>:8000/api/v1/milvus/connect

Describe the bug:
When click Connect button, the dialog reports the message "Cannot POST /<IP_ADDRESS>:8000/api/v1/milvus/connect"

Then I go to dev mode, find that connect's Request URL is http://<IP_ADDRESS>:8000/<IP_ADDRESS>:8000/api/v1/milvus/connect . I guess it should be http://<IP_ADDRESS>:8000/api/v1/milvus/connect. But I try a post request as follow, it still failed.
post http://<IP_ADDRESS>:8000/api/v1/milvus/connect
body
{
  "address": "<IP_ADDRESS>:19530"
}

response
{
  "statusCode": 400,
  "message": "Error: Connect milvus failed, check your milvus address.",
  "error": "Bad Request"
}

However, I can run hello_milvus.py successfully.
Steps to reproduce:

deploy milvus using docker-compose follow by https://milvus.io/docs/install_standalone-docker.md
run command docker run -p 8000:3000 -e HOST_URL=<IP_ADDRESS>:8000 -e MILVUS_URL=<IP_ADDRESS>:19530 milvusdb/milvus-insight:latest
open <IP_ADDRESS>:8000 in the browser, click connect button

The information about docker ps
$docker ps -a
CONTAINER ID   IMAGE                            COMMAND                  CREATED          STATUS                    PORTS                                           NAMES
f828d6535006   milvusdb/milvus-insight:latest   "/bin/bash -c '/app/…"   47 minutes ago   Up 47 minutes             <IP_ADDRESS>:8000->3000/tcp, :::8000->3000/tcp       stoic_pascal
78b701884e49   8938d19d0313                     "/tini -- milvus run…"   53 minutes ago   Up 53 minutes             <IP_ADDRESS>:19530->19530/tcp, :::19530->19530/tcp   milvus-standalone
e2b1dcf9a7f6   61ad63875109                     "etcd -listen-peer-u…"   53 minutes ago   Up 53 minutes (healthy)   2379-2380/tcp                                   milvus-etcd
3a69db060801   b849e0c26c4c                     "/usr/bin/docker-ent…"   53 minutes ago   Up 53 minutes (healthy)   9000/tcp                                        milvus-minio
9a12aadf0c92   registry:2                       "/entrypoint.sh /etc…"   25 hours ago     Up 25 hours               <IP_ADDRESS>:5000->5000/tcp, :::5000->5000/tcp       kind-registry

Milvus-insight version:
latest
Milvus version:
latest

You can try to replace <IP_ADDRESS> with your computer ip.


Replace Pygments with Highlight.js for Code Styling

Replace the current Pygments syntax highlighter with highlight.js to simplify styling and support themes.

This issue could be closed. Greg implemented this in #1538

Closing this issue since https://github.com/boostorg/website-v2/pull/1538 fixed it.


RFC on strategy/design doc for Tisane R

Goal: Create an R version of Tisane
Considerations:

Keep user-facing API as R-idiomatic as possible
Reduce duplicate maintenance efforts. So that changes to Tisane in Python will improve/update Tisane R package.

Pipeline at 10,000 ft
R API (user input code) --> Python script --> JSON --> Tisane GUI --> R Code (output statistical modeling code)

Note: The new part is R API --> Python script. The rest is already how Tisane (Python implementation) works.
Put another way, the goal is to "transpile" R into Python.

How to compile/transpile R into Python?

Strategy 1: Build up internal graph IR in R, traverse graph to produce Python code
Strategy 2: Parse R script into AST, traverse AST, generate Python code from AST
Strategy 3: Build up internal graph IR in R, output graph IR in some format (maybe DOT or something like that), read in graph output, write Python code from graph

In all of these: Key thing is to control Python script execution through a bash script, which we can call from R.
Current/next steps
As of January 18, 2022: I opt for Strategy 1 first because (i) I suspect the syntax of Tisane is likely to change more than the graph IR and (ii) outputting the graph to read it back in might not be necessary.
TODOS related to Tisane R:

@emjun: write R API --> Python script
@audreyseo: revise code generation (Tisane GUI --> code)

@audreyseo @shreyashnigam Did this capture our discussion? Anything you would change/add?

RFC looks good. Nothing to add


install: Handle rancher-desktop CNI location

Automatically detect if being installed onto rancher-desktop by checking
if the kubeconfig context/cluster name matches 'rancher-desktop'

Will this always be the name of the cluster with ranger?

Unless the user changes the name of their cluster/context, it should not change unless rancher-desktop changes how they update the kubeconfig.

I'm assuming if the cluster name CAN change, context will not, yes?

Same as above.
In general it's similar to Minikube.

Let's wait until https://github.com/cilium/cilium-cli/pull/717 is merged

@sayboras  The changes are similar to what's required for Minikube, I'm not sure what else could be done besides the docs which we already merged?

The changes are similar to what's required for Minikube, I'm not sure what else could be done besides the docs which we already merged?

All good, the above comment might be added before I checked related PR in cilium repo.

Let's wait until #717 is merged

This PR needs a rebase now that #717 is merged.


Automated Tests for BPF LSM, Unorchestrated Workloads and ARM

          I was hoping we can automate the system tests for this. Can we create another issue and handle it there since it would require provisioning of the resources?

We can leverage equinix instances for this.
Originally posted by @nyrahul in https://github.com/kubearmor/KubeArmor/issues/1206#issuecomment-1548129222

Also see: #1129


Failed to install fundoc via cargo

nekitk@192 ~ % cargo install fundoc
    Updating crates.io index
  Installing fundoc v0.2.5
error: failed to compile `fundoc v0.2.5`, intermediate artifacts can be found at `/var/folders/gx/2tsmxvzx1pxgnm3pg8200t4r0000gn/T/cargo-installcGL3PO`
Caused by:
  failed to select a version for the requirement `zeroize = "^0.9.3"`
  candidate versions found which didn't match: 1.3.0, 1.2.0, 1.1.1, ...
  location searched: crates.io index
  required by package `dialoguer v0.7.1`
      ... which is depended on by `fundoc v0.2.5`

The same error appears when trying to install v0.2.1 though I had successfully installed it via cargo before.

Seems like the problem is caused by deletion of zeroize versions prior to 1.x:
https://crates.io/crates/zeroize/versions

Solved by running cargo install fundoc --locked


Identification of tonal headers and attributes in Tonals page - Phase 1

We'll be using a method (similar to the one described in #46) to identify Tonal headers and rows.
This is also based on the visual representation of the table, and involves metadata hardcoding.
We'll be explicitly checking for Source, Ratio/Freq, Harmonics, Remarks < td > column headers to be present in one row.
Here's the method:
* Identify the tonal header: first < tr > which contains < td > elements with innerHTML as string literals "Source", "Ratio/Freq",  "Harmonics", and "Remarks" in the same order.
* Identify the `Tonal-Type` header: first < tr > following tonal header will be the first `Tonal-Type` < tr >  which might have optional < td > indicating the tonal-type,  say `Power Related` or `Auxiliary Sources` or `Transient Sources`. It MAY also have < strong > attribute
* Identify `Tonal attributes` under this `Tonal-Type`: < tr > with exactly four < td > elements
* Keep collating the `Tonal attributes` under the previously identified `Tonal-Type` until reaching the next `Tonal-Type` header.

Assumptions:

There will be only one Tonal table per tonal page under PageLayer div.

@IanMayo, please make corrections as necessary.

I'm pretty sure the tonals are always preceded by their tonal-type category.  Let's assume that - but also test to verify.  So the table rows are:

6 cells of propulsion cell headers
6 cells of propulsion cell values
"commonly detected sources". [*]
tonal headers
first tonal type
tonals

[*] I don't think we need to worry about the presence of this row or not. We're actually looking for the 4-column tonal headers - they mark the start of the tonals

Yep, that's exactly how we've coded it now. Will be pushing it in sometime.

This can be closed as any new changes to tonal extraction can be tracked via new issue.


fix: event macro

Fixes #3655
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
Metrics with a significant change:

circuit_simulation_time_in_ms (base-rollup): 1,069 (-48%)
circuit_input_size_in_bytes (base-rollup): 123,254 (-50%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit e83dd2b3 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,948
868,340
3,448,364

l1_rollup_execution_gas
867,057 (+3%)
3,746,393 (+4%)
23,305,129 (+5%)

l2_block_processing_time_in_ms
1,323 (-1%)
5,059
20,882

note_successful_decrypting_time_in_ms
334 (-3%)
1,150 (-1%)
3,765 (-1%)

note_trial_decrypting_time_in_ms
43.4 (-18%)
36.0 (-8%)
142 (+3%)

l2_block_building_time_in_ms
14,099 (+3%)
56,059 (+4%)
225,742 (+4%)

l2_block_rollup_simulation_time_in_ms
10,519 (+4%)
41,943 (+6%)
169,783 (+5%)

l2_block_public_tx_process_time_in_ms
3,554 (+1%)
14,062 (+1%)
55,758

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,095 (-3%)
28,837 (-2%)

note_history_successful_decrypting_time_in_ms
2,595 (+5%)
5,082 (+5%)

note_history_trial_decrypting_time_in_ms
84.9 (+8%)
192

node_database_size_in_bytes
3,615,439 (-7%)
3,716,673 (-11%)

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
201 (+1%)
43,109
20,441

private-kernel-ordering
115
25,833
9,689

base-rollup
:warning: 1,069 (-48%)
:warning: 123,254 (-50%)
881

root-rollup
82.4 (-2%)
4,088
889

private-kernel-inner
262
64,516
20,441

public-kernel-private-input
172
25,203
20,441

public-kernel-non-first-iteration
171
25,245
20,441

merge-rollup
9.67 (-1%)
2,608
881

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
10,331
26,317


Uncaught (in promise) TypeError: Failed to execute 'compile' on 'WebAssembly': Incorrect response MIME type. Expected 'application/wasm'.

I cloned this package and ran the test server successfully.
Without changing anything, I ran the build script and the built files were available in dist/ folder. When I served the contents of the folder and opened it with Chrome, I got the following error in the console.
Uncaught (in promise) TypeError: Failed to execute 'compile' on 'WebAssembly': Incorrect response MIME type. Expected 'application/wasm'.
Is there anything that I am missing?

This is most likely because the server you're running doesn't know about .wasm files.

You can either modify your server to handle .wasm files
or simply just use a server that knows how to handle them. I ended up using https://crates.io/crates/https

@Lxrd-AJ is correct. The .wasm file is served with an incorrect mime type, due to HTTP server configuration.


Prepare for 0.1.6 release

Undo #40
Switch publish namespace from com.danieltrinh to org.scalariform
Create dummy project that points the com.danieltrinh stuff to org.scalariform, so users don't have to switch namespaces in their code (although they will still have to switch versions)
Update release notes, scala versions

:smile:

@fommil How important is it to actually create a dummy project with the com.danieltrinh namespace to org.scalariform? I spent a few minutes trying to figure out how to set this up via the sbt build and haven't figured out how to do it yet.

Pretty important. Should be simple, it's just an empty project wind one dependency. To avoid creating a multi module project, just do it on a fresh branch.

This has been published and should be out in maven central now for 2.11, 2.10, 2.9.3, and 2.9.2, under both org.scalariform and com.danieltrinh.
I didn't actually go with the dummy project route, and instead published the same project twice under both namespaces, but I imagine the effect should be the same.

AWESOME! :grinning:


Fix: Update botAvatar URL in Chatbot.jsx, closes #317

Issue Title:
resolve issue: #317
Type of change ☑
Changed url from local to remote which should fix the issue

[x] Bug fix (non-breaking change which fixes an issue)

Checklist: ☑

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

How Has This Been Tested? ⚙
By running locally
Screenshots
Before:

After:

Not assigned.


ThemeProvider theme passing not working

Version: 4.3.3
Environment: DOM
Type: Bug
React version: 15.4.2

Description
Hello, I've experienced issue with ThemeProvider.
It looks like it is passing empty theme to children.
I've setup an example at github.
This might not be a bug, maybe just a bad setup of Fela and React and I am the one to blame.
Thanks for help.

Steps to reproduce

git clone https://github.com/mrceperka/react-fela-theme-not-working
cd react-fela-theme-not-working
yarn install
yarn start
Visit localhost:3000 and see console

Expected Behavior
Non empty theme should be passed
Actual Behavior
Empty theme passed

Is fixed with the new release, got broken in 4.3.3

Thank you! :fireworks:

It looks like it still not working.
Previous code was like this:
const Root = props => (
  <FelaProvider renderer={getRenderer()} mountNode={getMountNode()}>
    <ThemeProvider theme={theme}>
      <App />
    </ThemeProvider>
  </FelaProvider>
);

Now I have to pass renderer to ThemeProvider to get rid of
Error: createComponent() can't render styles without the renderer in the context. Missing react-fela's <Provider /> at the app root?
So I've modified code to this (to silence the error :no_bell: )
const Root = props => (
  <FelaProvider renderer={getRenderer()} mountNode={getMountNode()}>
    <ThemeProvider theme={theme} renderer={getRenderer()}>
      <App />
    </ThemeProvider>
  </FelaProvider>
);

But theme is still empty. I've updated example repo. What am I doing wrong?
Thanks for help.

OMG, my bad. I accidently replaced  with  😅 next release is coming


Pages

Fixed the baseurl and update the gemfile

I don't think so but I'd like the site to be as portable as possible. Need to do some additional tests I guess.


plots: create experimental design plots

Plot results of ode integration together with best time and temperature points.
Define the newly written function such that the following options are possible:

use specific n_temps and n_times
plot the 1..m best results with respect to observable

The n(times) curves were plotted with a scatter plot showing chosen experimental design.


feat: ISY-2905: initial commit correction

Merge:
:thumbsup: without conflicts
:thumbsup: root project: compile & test
:thumbsup: module in question (ref-impl-basis): application can be started


Issue 5 sendemailasync

Implementation for SendEmailAsync for all transport types.  Refactored client / request / response logic into common private methods since it's shared between async and non-async implementations.  .NET 4.0 configuration no longer builds because async/await keywords require 4.5+.

@jturinetti the .net 4.0 support was removed. Can you rebase your branch, and fix conflicts?

Will do.

@lira92 There are still references to the Debug4.0 and Release 4.0 configurations in the SendEmailTest project, which is causing issues.  Do you want to remove those first or should I as part of my changes?

@jturinetti If you can include these changes in your PR, I'm grateful.

Not sure I did the rebase/squash right, let me know if it looks wrong.  The SendEmailTest project file still has old solution configurations in it, I didn't get to changing those.

@lira92 Fixed build configurations in project files to you have Debug and Release now.  They are both building successfully.  Fixed the configuration references in the .bat scripts too, but they were not working for me.  Let me know if this all looks good or if you want me to do anything else, happy to help.

@jturinetti ok, I expected that after rebase/squash your commits, only one commit remained listed, but i get 14. I you dont't have the upstream origin added, execute:
git remote add upstream https://github.com/Inside-Sistemas/mailer.net.git
After this in yout branch, execute:
git rebase -i upstream/master and change 'pick' to 's' in all commits except first. I believe this will work.

@lira92 Think I got it that time!  Take a look when you can, all squashed into one commit.

@jturinetti you forgot to add a async method on Email class, but I will do this. thank you for contributing.


Adds Sysdig Secure product

Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~5 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Deploy preview for landscape ready!
Built with commit 01987dbe8224138e89b3b8a957e8d4209290ead6
https://deploy-preview-1468--landscape.netlify.com

@dankohn
So can I grab some of your time in the coming weeks to talk about this? I want to echo that their are three separate entities here that have involvement from Sysdig (the company).
Sysdig
A FOSS CLI tool with an Apache 2 license that behaves like Wireshark, but for kernel event tracing
Sysdig Secure
A commercial offering with (confusingly) the same name
Falco
Sandbox project with the CNCF

We understand that the sysdig language is confusing, and we are working on rectifying this. Other projects such as docker also were subject to this same pain point so we ask that you understand that there are differences in these entities.

Sure. Let's try to sit down next week.

Could you please reopen when you've decided what you'd like to do here?


Dimension mismatch or high dimensional dot operation is not supported

Code :
NDManager manager = NDManager.newBaseManager();
NDArray X = manager.randomNormal(new Shape(1, 2));
NDArray trueW = manager.create(new float[]{2, -3.4f});
X.dot(trueW);
Exception
Dimension mismatch or high dimensional dot operation is not supported. Please use .matMul instead.
The engine is  pytorch-engine  and the environment is windows cpu
Thanks

@foolfish1
Can you use X.matMul(trueW)?
See: https://pytorch.org/docs/stable/generated/torch.dot.html

The issue can also be solved by specifying the Shape:
           NDArray trueW = manager.create(new float[]{2, -3.4f}, new Shape(2, 1));
But as instructed, .matMul is suggested.


Error Connection was reset when connect to expose port

I use node-alpine to build web app, I expose port 8080 and run my app on that port
When I try to connect it show connection was reset
I use node:8-alpine which use alpine:3.6
Docker version Docker version 17.06.1-ce, build 874a737
My dockerfile
FROM node:8-alpine

RUN apk add --no-cache yarn
RUN apk add --no-cache python
RUN apk add --no-cache make
RUN apk add --no-cache gcc
RUN apk add --no-cache g++
RUN npm install -g node-gyp
ENV NODE_ENV "development"
EXPOSE 8080
RUN mkdir /app
RUN chown -R node:node /app
WORKDIR /app
VOLUME /app
USER node
CMD ["/bin/sh"]

Command I run sudo docker run -it --rm -v ~/Project/Nodejs/ng2-admin/:/app -p 4200:8080 node-build-env yarn run start

This isn't really the right place for these kind of questions. It is better suited for something like https://stackoverflow.com/. It is also harder to debug without the steps you used to reproduce the error and example code so someone can build the image themselves.
If you create a question on Stack Overflow and ask for assistance in the Glider Labs Slack #help channel I'll be happy to take a look.


config: health checker timeout and interval should be greater than 0

Description:
This patch adds value validation for interval and timeout fields to accept values greater than 0.
Risk Level: Low
Testing: Manual testing by setting timeout or interval to 0s
Docs Changes: N/A
Release Notes: N/A
Fixes #3729
Signed-off-by: Dhi Aurrahman<EMAIL_ADDRESS>

@mattklein123 do you think I can just add config tests inside the health_checker_impl_test and redis' config_test? Or is it a good idea to introduce a new file containing config tests for the health check config?

@dio I would just add tests wherever is easiest. (Obviously just make sure the validator actually runs.) Thank you!

@junr03 please take a pass on this once tests are added. Thank you!

Test is added. PTAL. Thanks!


Knative Integration

Integrate app with Knative

Done here: https://github.com/bee-travels/config

Code pattern issue: https://github.ibm.com/IBMCode/IBMCodeContent/issues/2871


Filter out existimg members when add a new member #4364

Filter out existimg members when add a new member #4364

Coverage decreased (-0.006%) to 64.537% when pulling 285078c95e815fd920019a9a6aa231e720509098 on pengpengshui:leftNav into 6a7ba4609faa46380387bb12583a24829789a397 on vmware:master.

when typing in a name of a user already a member of a project, if you partially type in the name and select it from the dropdown you can add the same user over and over again. if you fully type in the name, you get the error  "Username already exists"


localStorage breaks Backbone.js

So I've just downloaded and setup localStorage along with Backbone.js and here's what happening with FireBug:
When using non-minified file:
model.collection is undefined
http://<IP_ADDRESS>/assets/js/backbone.localStorage.js
Line 87

Minified version:
d.collection is undefined
http://<IP_ADDRESS>/assets/js/backbone.localStorage-min.js
Line 8

Correction:
I've entered the tests folder of localStorage and ran the qUnit tests with the current backbone.js from the test folder (version Backbone.js 0.5.0-pre) and all tests passed.
When I replaced it with the newest backbone.js - that's Backbone.js 0.5.3, the following occurs:
2 tests of 10 passed, 8 failed.

I'll have to check this out.

Fixed from one of the latest pulls which tests against 0.5.3

Thanks a lot for your support!


Add bank payout method form not clear which address it wants

Is this screen asking for my organization's address, which is already filled out on the left but could potentially be different to the address associated with my bank account, or my bank's address? We should make this clear to the user.

(I already raised a separate issue about how the fields are greyed out).

@kewitz @alanna Can we consider that solved?

I think it was solved on another issue by adding a tooltip. If @kewitz has completed that with the help text I supplied, this can be closed.


Fix code style config and fix eslint: consistent-return

[x] tests and linter show no problems (npm t)
[ ] tests are added/updated for bug fixes and new features
[x] code is properly formatted (npm run fmt)

Landed in https://github.com/metarhia/metasync/commit/3afbc3be847af3df43bd2ec3ebb40bfa164d4fb1 and https://github.com/metarhia/metasync/commit/2f64120f2a2876b3460fde9a94fc8dd6c8aea09c


fix: chips having same dimension and different stages werent showing stage name when in different axes [DHIS2-16462]

Fixes https://dhis2.atlassian.net/browse/DHIS2-16462
In order to know if there is a duplicate it's necessary to check all the dimensions added to the layout, not just those in the same axis.
Also, instead of using suffix, or stageName, use the more generic nameModifier. This is in anticipation of the upcoming TEI multi-program implementation where the modifier could be a program name rather than a stage name.
Note that for the dimension modal, stageName is still used.
For the dragging chip, all the needed dimension info, including nameModifier is now provided in the dnd data object, so no need to find it in the metadata in DndContext.

This work is not currently prioritized. Keeping the branch for later.