Question: How to print the start image of an embeded video

Thank you again for your great, essential plugin which I often use. ;-)
When I want to print the start image an embeded video, there is no output.
The side looks rendered as so:

Printed:

Markdown:
---
aliases: eins
---

Python: Film 7: type-casting in Python (14:07).

<iframe width="560" height="315" src="https://www.youtube.com/embed/u_ECGvn1Z2c?si=GaML67idFSvWc4tG" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

Do you have an idea?

There is no easy way to solve this problem, you can currently add an image/text link to the video, set the CSS style, and only display it when printing, to alleviate the problem.


Added a function to TM1py Utils, which enables to sync a 2-dimensiona…

…l cube. Can be used to sync a security cube, }Clients cube, }DimensionAttribute cube.

Closed: Subject to Future Re-evaluation


Implement a project manager tool

Adds an implementation of a project manager tool that can add assets (also parented to each other) and can assign each of them tasks.
To give a test run on a project you can try it with:
import os

from mindbender.tools import lib as tool_lib
import mindbender.tools.projectmanager as tool
import mindbender.io as io

# Initialize project environment
os.environ["MINDBENDER_PROJECTS"] = "D:/Projects"
os.environ["MINDBENDER_PROJECT"] = "testproject"

# The project must have "silos" and "tasks" in its
# configuration in the database.

io.install()
io.activate_project(os.environ["MINDBENDER_PROJECT"])

with tool_lib.application() as application:
    tool.show()

Got a double Awesome font in here, let's look at merging those.
Here and here.

Could we isolate the resources used by projectmanager/ into the directory itself, and not put things into the global widget/? I'd rather we work out way outwards from one tool.
I know you have other things that likely depend on those global ones, but I want to make it more clear what is being made global, and explicitly record why.

This is almost at feature parity with our .inventory.toml interface, apart from:

Creating a new project
Adding metadata to assets

The metadata so far are int and str with a str for name.
[[assets]]
name = "Bruce"
label = "Bruce Wayne"  # (Optional) Nicer name
group = "Character"  # (Optional) Visual grouping
icon = "gear"  # (Optional) Icon from FontAwesome

Also the project needs metadata.
label = "The Hulk"
fps = 24
resolution_width = 1920
resolution_height = 1080

How about this for creating and visualising other projects?

How about this for creating and visualising other projects?

That could work; we originally had this:

The "manager" (project manager) and "explorer" (browse a project's work areas) had this top project bar to switch between project and depict the current project you're in. It could also house the "edit project metadata" functionality.

Got a double Awesome font in here, let's look at merging those.

Currently I'm also using these as icons (e.g. in a menu). How would I do it with your awesome.py? Not sure how the features from one to the other transfer.

Currently I'm also using these as icons (e.g. in a menu).

There's an example here.
QtWidgets.QPushButton(awesome["refresh"])

Ah I see what you mean now, qtawesome.py implements some sort of wrapper of a letter of Awesome to be rendered as a QIcon.
Mine doesn't do that, and unless QIcon can take a plain character and render it on its own I think we should use yours.

Ok, here's what's changed.

awesome.py was merged with qtawesome
All global modules, in mindbender/widgets was merged with projectmanager, I expect these to reach out into global space where (absolutely) necessary
PEP8 fixed and Napoleon docstrings implemented
The command-line interface is the one below.

$ python -m mindbender --projectmanager "spiderman"

Oh, and Maya crashes on tests. :D Not sure why yet, looking into it.

Had accidentally added the script I used to show the project manager.

Ready to merge!


Force close stuck, TX disappeared

Some time ago a channel was closed. It's been sitting in pending_forced for very long so now I checked the TXID and it isn't in the blockchain, isn't in the mempool.
How can I get LND to give me the raw transaction so I can attempt to re-broadcast it? I'm worried about opening any more channels if I can lose the money because of failed closing transactions. I'd prefer to know what happened here and also be able to resolve it.
lnd version 0.4.1-beta commit=13945de8060ad42e077988c1cf69e205dc11e528 on a Debian with Bitcoind (0.16) as backend.

"pending_force_closing_channels": [
{
"channel": {
"remote_node_pub": "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432",
"channel_point": "7cbc012a8c8c1472d560b77a5dbe9759288647d671aa550925bc0d59c4ada2e9:1",
"capacity": "5000000",
"local_balance": "4999276",
"remote_balance": "0"
},
"closing_txid": "14f0121bfc785806a224b60a3a8f009babfba06e1ede38a756816199810e886f",
"limbo_balance": "4999276",
"maturity_height": 0,
"blocks_til_maturity": 0,
"recovered_balance": "0",
"pending_htlcs": [
]

I noticed your issue and wanted to point to my issue with appears similar.
https://github.com/lightningnetwork/lnd/issues/1071

How can I get LND to give me the raw transaction so I can attempt to re-broadcast it?

lnd will automatically rebroadcast transactions on start up. On restart, do you see your bitcoind reject the transaction?

Looking at the chain, we see: https://www.smartbit.com.au/tx/7cbc012a8c8c1472d560b77a5dbe9759288647d671aa550925bc0d59c4ada2e9
Which has both outputs spent, which means that all funds have been fully swept by lnd. So it would appear that this is related #1071, which will be fixed by #1017.

I'm worried about opening any more channels if I can lose the money because of failed closing transactions.

No money was lost, if you follow the link above, you'll see that all the funds were properly swept.

In response to your request for logs:

2018-04-13 12:36:12.584 [ERR] UTXN: Notification chan closed, can't advance output 14f0121bfc785806a224b60a3a8f009babfba06e1ede38a756816199810e886f:0
2018-04-13 12:36:14.702 [INF] UTXN: Commitment outpoint 14f0121bfc785806a224b60a3a8f009babfba06e1ede38a756816199810e886f:0 registered for confirmation notification.

Thanks for the clarification. That puts me at ease (hopefully it fixes not just the issue but will also remove this phantom / stuck tx). Feel free to close this ticket. Thanks again.

same as me;
Where is the 59K Satoshi?
Initial Balance;
lncli walletbalance
{
"total_balance": "1006634",
"confirmed_balance": "0",
"unconfirmed_balance": "1006634"
}
Payments stuck for a few days now afer closeallchannels forced.
lncli pendingchannels
{
"total_limbo_balance": "467280",
"pending_open_channels": [
],
"pending_closing_channels": [
{
"channel": {
"remote_node_pub": "035f804103054d1d24aa4b1cbe29a90c06af2695c93adb6e7501dc143cffbc09bd",
"channel_point": "870c55d150833a518e201765cae3d8827cca95b687094a76cc77551d8b3c0f06:1",
"capacity": "81034",
"local_balance": "80853",
"remote_balance": "0"
},
"closing_txid": "96eb50eaec2d71c5ba4ea2b16a7b90751a47a9aa041d51037a5911834de988c6"
},
{
"channel": {
"remote_node_pub": "025e77156e4c5e1ed62f9ad113ac2115a981ee99fa05d95be9e43add7f785a9b4d",
"channel_point": "b7bc21da6fb89c6ac3b61469bb5ee6e7103f93e5811caad0a5d250155329f008:1",
"capacity": "153978",
"local_balance": "153797",
"remote_balance": "0"
},
"closing_txid": "b5b3e9f501a1f216e611062e63ecf30e58ee55f43f59a89fdb2f42a475d22ddd"
},
{
"channel": {
"remote_node_pub": "02ad6fb8d693dc1e4569bcedefadf5f72a931ae027dc0f0c544b34c1c6f3b9a02b",
"channel_point": "a061c52fef9a578f73204cfbf1f27310aa37543cf1018abc318a7754930f3ec6:1",
"capacity": "110024",
"local_balance": "109736",
"remote_balance": "0"
},
"closing_txid": "1e80c3e1fdcf85c8df3da61d98192b25447d473c1b888906044bb04d76934836"
},
{
"channel": {
"remote_node_pub": "033c3a18d7ffe9e1eec718b45616b202cd98a8054b47e424fb56a0f2ea6877a13f",
"channel_point": "69a03a186f7a6d1d3b3142ade35f8ce7d614f4a26c985b96c3e847d657546fd3:1",
"capacity": "29577",
"local_balance": "29396",
"remote_balance": "0"
},
"closing_txid": "48d19746465c854084f90bef7674d2cad2c4ae89e5d6ab9e038be4224e4bf29a"
},
{
"channel": {
"remote_node_pub": "0350a241aca91b8f6a694f1643a93b2f5022c226ae7025868ddaf9c87e5d4e4e09",
"channel_point": "315a6286fc8577aa0e29848222a5b91f549ca693487340ad8544669f646285ff:0",
"capacity": "93679",
"local_balance": "93498",
"remote_balance": "0"
},
"closing_txid": "f7e8843655586b5a130ee085b25d3b42f30b6680ff20ba7c4de35781c272343a"
}
],
"pending_force_closing_channels": [
{
"channel": {
"remote_node_pub": "0355157b4260b70c7f407a720c527a84e9522cd948e7a8ad92ae00773be52488e3",
"channel_point": "e284f54f4cbc4cc6c8a95773650b9623bc0f0a68442b63b1705f3a1e3aa1ac8b:0",
"capacity": "266885",
"local_balance": "266704",
"remote_balance": "0"
},
"closing_txid": "27e8bc7ac798e537be359e272936dae153a3e048ab3177c9750aefc28f60685e",
"limbo_balance": "0",
"maturity_height": 0,
"blocks_til_maturity": 0,
"recovered_balance": "0",
"pending_htlcs": [
]
},
{
"channel": {
"remote_node_pub": "0350a241aca91b8f6a694f1643a93b2f5022c226ae7025868ddaf9c87e5d4e4e09",
"channel_point": "5e3a31d773e1e251a3eef87694e764cd8f0cb7aa185275568fc9c3e3c27d66ad:1",
"capacity": "32113",
"local_balance": "31932",
"remote_balance": "0"
},
"closing_txid": "36e32efb0a7356b01664b389bcad57773740158ad075c37a1458ca27c13bb4fd",
"limbo_balance": "0",
"maturity_height": 0,
"blocks_til_maturity": 0,
"recovered_balance": "0",
"pending_htlcs": [
]
}
]
}
Current Balance;
{
"total_balance": "947180",
"confirmed_balance": "947180",
"unconfirmed_balance": "0"
}
net in;1006634
Net out;947180
Loss;-59454
Never made a payment, paid additional fee's on-chain.
Where did it go?

@8KSS for those last two channels, everything has been fully resolved on-chain, meaning all funds have been swept. It's possible that the sum of your fees across all those channels went up to 59k satoshis, as there were multiple instances a transaction fee is paid: when opening a channel, when closing a channel, when sweeping time-locked funds from a channel.

Also if you do listchaintxns, which transactions are included?

It's also the case that if you have any channels which at closing time had a "dusty" output, then those aren't able to be claimed, and will instead go to miner's fees.

{
"transactions": [
{
"tx_hash": "9c974ced47bc0b75d5ea34ee0158a6906932d3c49977b5691130377fd91b6d2d",
"amount": "1106810",
"num_confirmations": 1095,
"block_hash": "0000000000000000003d1c0fa13f9373f5471d4ab46722b4f8b37dddb06fbcce",
"block_height": 517241,
"time_stamp": "1523202090",
"total_fees": "0",
"dest_addresses": [
"37KrUw2WE9wJcyP7nv9n1GEuhxW4CFdmGR",
"13uXq2N3LpP3P1AtSbV1TWQ6TBbszomshe"
]
},
{
"tx_hash": "74fe74027f10c59ba2c575571775d695ad7a67b7cad84cd5d78d41fb5b92a379",
"amount": "-100176",
"num_confirmations": 1091,
"block_hash": "0000000000000000004b1ef0def18c0549541e090dcb9199721e6cad8f18ccdf",
"block_height": 517245,
"time_stamp": "1523204067",
"total_fees": "176",
"dest_addresses": [
"bc1qlykhj7gkurptx4zdlsql4gv4fpnh5drk3yahcjlhwch3jz9hpfrquxmw27",
"bc1qa45w3vh6zl9rh0v4k62yr7znx849sxxf58zywf"
]
},
{
"tx_hash": "faac42fe33dfd3d457456fde310aff9e9c6b4f0a8d5fec84a7bc043679701aa8",
"amount": "-100153",
"num_confirmations": 1089,
"block_hash": "0000000000000000004e4e712b8d6dd77f61681f061727922fc7267817bd7baf",
"block_height": 517247,
"time_stamp": "1523204788",
"total_fees": "153",
"dest_addresses": [
"bc1quajc4wd0a8pzgcl8c9a4yj8p74eku34k2aq6y7rx30swfwclmw8scg6r8a",
"bc1q2utu0dy0577vswz2k7gm23lzlxuxmj0j23ztsm"
]
},
{
"tx_hash": "70bbbec912d53394434937b4c7f6d4a2ec4a0dbdf64daa943567e24c085d0da6",
"amount": "-100153",
"num_confirmations": 1086,
"block_hash": "000000000000000000429f5fec52afdc16540ef5eda2d5a711a988db8041da46",
"block_height": 517250,
"time_stamp": "1523207188",
"total_fees": "153",
"dest_addresses": [
"bc1qyfml8qcj6rqfj4he0ft60vqfw726zcwjz36exn94sn5z9vd2drsqprk02p",
"bc1qnzmfzw5wag0446aap8u476ppuj5tuzcqd4g9tc"
]
},
{
"tx_hash": "9cf94667f4932c7a5de3945fe1dcd38792ed668e3019f391f9221d4689c8f5b1",
"amount": "-242584",
"num_confirmations": 1081,
"block_hash": "00000000000000000004b9e238f822a7bdf4104ffcc8ef44c22bef468a47facd",
"block_height": 517255,
"time_stamp": "1523209562",
"total_fees": "306",
"dest_addresses": [
"bc1qttkh9e0gnllupvmye8j5khwc8gy9ku07588xrdpk7kn8v63yz9ysu09c7e",
"bc1qfcyn75cqzmnw9l92mafgwtnuf2w6dzq86k63qw"
]
},
{
"tx_hash": "e284f54f4cbc4cc6c8a95773650b9623bc0f0a68442b63b1705f3a1e3aa1ac8b",
"amount": "-267191",
"num_confirmations": 1079,
"block_hash": "000000000000000000428a173468966d068f08f63f11c2d8db47d95ab861a32a",
"block_height": 517257,
"time_stamp": "1523210752",
"total_fees": "306",
"dest_addresses": [
"bc1q6c8pha924qag9xwxqyxsk532h60wvggyxvy23j6qp9mpslwsgzasezqayu",
"bc1q77tutdrdmpdqh7q7y6tprvdgsseql3j23dzap4"
]
},
{
"tx_hash": "15c7ae08a0c2b361b0949a8ab8cf303014703d76c6c4ed83d0b96e43d048d60b",
"amount": "49448",
"num_confirmations": 1077,
"block_hash": "0000000000000000001e00ceb49c819ce4b7d2ff4097345c83146bc81a5466c7",
"block_height": 517259,
"time_stamp": "1523212151",
"total_fees": "0",
"dest_addresses": [
"bc1qqs6ydfeeacj9x857ctwdde97uzg7a5p6ar9m2y"
]
},
{
"tx_hash": "cc9bcf84953174c14473a510a1e7a32f6dc556677379c4f5a41549d4963b1a74",
"amount": "49819",
"num_confirmations": 1066,
"block_hash": "000000000000000000173855d066a30d10598bb537df6e9f1c5c7260c3587ff6",
"block_height": 517270,
"time_stamp": "1523218909",
"total_fees": "0",
"dest_addresses": [
"bc1qmg97xsfzapplwqtj23weyptd6sh3e3zx08nwpr",
"bc1qzm7rzvrt8gmlxp6hlrnazw3c8eammkdmmr7m92"
]
},
{
"tx_hash": "a5cdf35837516aab6b2a29cfd82b391df820888a6f37c911ac3ef6be5b7acc4f",
"amount": "-24951",
"num_confirmations": 1063,
"block_hash": "0000000000000000000765e613d057c8c8e2b9aa6f869cbc7bb9c60a4fbc1a1a",
"block_height": 517273,
"time_stamp": "1523221187",
"total_fees": "612",
"dest_addresses": [
"bc1q098yc3prl42ly6xgtjdlllvzeuucht69y423d20rsaur7w49lh4s2m6tuk",
"bc1q03dsr6r3xjkred35yp6qnjupz0l7s54jtjrxfz"
]
},
{
"tx_hash": "308eba2e4e405b9ff3b6fcbaf0229253d3ce3f0c907eecc26eb50966fb6a1def",
"amount": "-24868",
"num_confirmations": 1062,
"block_hash": "0000000000000000001d0572268c17bf1105f548730d3f595400621f0c1e33d5",
"block_height": 517274,
"time_stamp": "1523221313",
"total_fees": "777",
"dest_addresses": [
"bc1qedegkw9zsxutmjnqtfxjcvupmcrj5yfl0ysvejwq655lzc2x9uwqluw4m9"
]
},
{
"tx_hash": "07c539253aae202f9e2565b336090254725a8c1a99ca5f6bdf5a95f9eff7f97e",
"amount": "23425",
"num_confirmations": 1056,
"block_hash": "000000000000000000171e0180e529175b64abdccf07fb5d8939c5df402770aa",
"block_height": 517280,
"time_stamp": "1523222852",
"total_fees": "0",
"dest_addresses": [
"bc1qcpeg4z27x3980mf36etuwdvk8n4zkkgc8vukht"
]
},
{
"tx_hash": "f56105760ffecb543e7c258df90923d6ec8e6dc5061aa80c44ac706f005c8c86",
"amount": "23539",
"num_confirmations": 1055,
"block_hash": "00000000000000000007a0598c0dfa22a62e695f8499c6e54fae5a6f13ceb3c2",
"block_height": 517281,
"time_stamp": "1523224213",
"total_fees": "0",
"dest_addresses": [
"bc1q8m4caucwc5xf0g3ycvytacx0vejdvsn8udm65f"
]
},
{
"tx_hash": "5e3a31d773e1e251a3eef87694e764cd8f0cb7aa185275568fc9c3e3c27d66ad",
"amount": "-32334",
"num_confirmations": 1029,
"block_hash": "000000000000000000009d4941e841717bc0659dee2cf36a24e15766400fcd14",
"block_height": 517307,
"time_stamp": "1523235565",
"total_fees": "221",
"dest_addresses": [
"bc1qep8nygcc04859rk9faegcca9pthdc6sd28t3up",
"bc1qvxk0r76kj4uhggpmxclxesna6lpeh5nuyucqn9zwasz22kg392dsvk49lz"
]
},
{
"tx_hash": "83933bc9f6ef890b4ad829b4daf3a9d40c7b984b695727e71db45062b61ee33e",
"amount": "49515",
"num_confirmations": 914,
"block_hash": "0000000000000000001901ed133f6243d0e09996cc2cba0c02ac0995cb9ac5fa",
"block_height": 517422,
"time_stamp": "1523299592",
"total_fees": "0",
"dest_addresses": [
"bc1qxxqsjgsyu7jac30yv9wndv2zczw32ajjfan8gs"
]
},
{
"tx_hash": "69a03a186f7a6d1d3b3142ade35f8ce7d614f4a26c985b96c3e847d657546fd3",
"amount": "-31107",
"num_confirmations": 913,
"block_hash": "0000000000000000000fe118346644678212ec2258b450e78e6f4e97257d4f68",
"block_height": 517423,
"time_stamp": "1523300465",
"total_fees": "1530",
"dest_addresses": [
"bc1qhza8qu93wu56jqu8h7fgmn9uezqznt4j76z6k5",
"bc1qrccs7f597q6a2pewckfwmalzam7yulpy7elw3wvnjcvhkpfsxmesgsl0n2"
]
},
{
"tx_hash": "cde8b0b50eac0371bf53fc5cb826104704d2c2c0f9cfd000ffac11f0a0357378",
"amount": "242097",
"num_confirmations": 698,
"block_hash": "00000000000000000034fa3f2a40160414b8383b79fde2cad794c076f40107e0",
"block_height": 517638,
"time_stamp": "1523416750",
"total_fees": "0",
"dest_addresses": [
"bc1qzzrfwzk2j7pwt2uw8rxe4tpad76qmrz9yhxety"
]
},
{
"tx_hash": "48d19746465c854084f90bef7674d2cad2c4ae89e5d6ab9e038be4224e4bf29a",
"amount": "29396",
"num_confirmations": 698,
"block_hash": "00000000000000000034fa3f2a40160414b8383b79fde2cad794c076f40107e0",
"block_height": 517638,
"time_stamp": "1523416750",
"total_fees": "0",
"dest_addresses": [
"bc1qfaudg3c79qt6ka24j5vaakh2a692va24qn28uh"
]
},
{
"tx_hash": "b7bc21da6fb89c6ac3b61469bb5ee6e7103f93e5811caad0a5d250155329f008",
"amount": "-154131",
"num_confirmations": 697,
"block_hash": "00000000000000000024bb10868e4e0705f476def339971ea478cef6ede4d615",
"block_height": 517639,
"time_stamp": "1523417604",
"total_fees": "153",
"dest_addresses": [
"bc1qwl9nkxw7npkgv48sxkstv23e9smfl9vywzekl8",
"bc1q7q86lxgarst74qse6e664g2g3p35g94ganfl6vjqnn8cvh4xk4lqn8f7fq"
]
},
{
"tx_hash": "a061c52fef9a578f73204cfbf1f27310aa37543cf1018abc318a7754930f3ec6",
"amount": "-110245",
"num_confirmations": 694,
"block_hash": "0000000000000000001ede02615aa1d20085340fd575343606ad99145c4bbba3",
"block_height": 517642,
"time_stamp": "1523418467",
"total_fees": "221",
"dest_addresses": [
"bc1q5auvgydauj8tkl5dx35dtc57p4ywx6tsj7szct",
"bc1q2v5tzvuzqh006xtflpraf9gqqscqyhuukl3m3ewy6j2q6lh8n8ds7rqvmp"
]
},
{
"tx_hash": "870c55d150833a518e201765cae3d8827cca95b687094a76cc77551d8b3c0f06",
"amount": "-81392",
"num_confirmations": 685,
"block_hash": "0000000000000000002d20adf0060cf304355a851b2451564a52b682d7d51ed8",
"block_height": 517651,
"time_stamp": "1523422212",
"total_fees": "358",
"dest_addresses": [
"bc1q3yscranux5jjasnr8gl73nt065r8d86dapzh8d",
"bc1qge5xr7a555ymvweaut83hyfvc4hucap05n6py0gjrvusqevvyp3syav0jy"
]
},
{
"tx_hash": "315a6286fc8577aa0e29848222a5b91f549ca693487340ad8544669f646285ff",
"amount": "-93900",
"num_confirmations": 682,
"block_hash": "0000000000000000002f3d97213e775e21ec33fee04381fd8e193a4dd61c9d17",
"block_height": 517654,
"time_stamp": "1523423028",
"total_fees": "221",
"dest_addresses": [
"bc1qj43uk8xhhyz50ve229xal0n73nqj3xfm0crfg2tmd894psnntfrqha29vd",
"bc1qa2q47myrv0ykyhngmxfsqf6nlscv8q42k3yjm0"
]
},
{
"tx_hash": "1e80c3e1fdcf85c8df3da61d98192b25447d473c1b888906044bb04d76934836",
"amount": "109736",
"num_confirmations": 623,
"block_hash": "0000000000000000003376431f1927bec9cc690d44636f230ea22a6db5bbe6a5",
"block_height": 517713,
"time_stamp": "1523457794",
"total_fees": "0",
"dest_addresses": [
"bc1qaj0aeup5m9gj3tk86gvafcajqxnl2dygud5wg3"
]
},
{
"tx_hash": "b5b3e9f501a1f216e611062e63ecf30e58ee55f43f59a89fdb2f42a475d22ddd",
"amount": "153797",
"num_confirmations": 622,
"block_hash": "0000000000000000000e28622c0fd7d8bdd8f0029b99800b9790e5f15b5f5320",
"block_height": 517714,
"time_stamp": "1523457812",
"total_fees": "0",
"dest_addresses": [
"bc1qd0f8353jsmn8d7mjgap0geququzcw3w7ngv9td"
]
},
{
"tx_hash": "f7e8843655586b5a130ee085b25d3b42f30b6680ff20ba7c4de35781c272343a",
"amount": "93498",
"num_confirmations": 622,
"block_hash": "0000000000000000000e28622c0fd7d8bdd8f0029b99800b9790e5f15b5f5320",
"block_height": 517714,
"time_stamp": "1523457812",
"total_fees": "0",
"dest_addresses": [
"bc1q3yrn9nmnedug70ehrzvlvknzk4jgsnfz4srnee"
]
},
{
"tx_hash": "96eb50eaec2d71c5ba4ea2b16a7b90751a47a9aa041d51037a5911834de988c6",
},
{
"tx_hash": "f7e8843655586b5a130ee085b25d3b42f30b6680ff20ba7c4de35781c272343a",
"amount": "93498",
"num_confirmations": 622,
"block_hash": "0000000000000000000e28622c0fd7d8bdd8f0029b99800b9790e5f15b5f5320",
"block_height": 517714,
"time_stamp": "1523457812",
"total_fees": "0",
"dest_addresses": [
"bc1q3yrn9nmnedug70ehrzvlvknzk4jgsnfz4srnee"
]
},
{
"tx_hash": "96eb50eaec2d71c5ba4ea2b16a7b90751a47a9aa041d51037a5911834de988c6",
"amount": "80853",
"num_confirmations": 622,
"block_hash": "0000000000000000000e28622c0fd7d8bdd8f0029b99800b9790e5f15b5f5320",
"block_height": 517714,
"time_stamp": "1523457812",
"total_fees": "0",
"dest_addresses": [
"bc1q38hkhrdc8sp9n2ttvgyvq508vmk2zjfwm69vk2"
]
},
{
"tx_hash": "6c19483e7c04d9ba1dd50e05fbb62b78f44701568721669aa53630d537eb6f0c",
"amount": "298432",
"num_confirmations": 537,
"block_hash": "0000000000000000002e9d97ba959422043f3b9ec6301909f39946acd243b741",
"block_height": 517799,
"time_stamp": "1523503391",
"total_fees": "0",
"dest_addresses": [
"bc1qpsm0hn432wztf6m5nrmdjpzvwq6lajqnnnaaq3"
]
},
{
"tx_hash": "b5316f61f5acbd8ca94d9cf0a6c60017cf972dc682ea6f454a43510b9efc1cf2",
"amount": "-947180",
"num_confirmations": 385,
"block_hash": "00000000000000000036cfc2d0abdbf286603db9e8f53f9c76b12df9c8135760",
"block_height": 517951,
"time_stamp": "1523587508",
"total_fees": "6000",
"dest_addresses": [
"16kKXtA9AN9LLgMS4pikTqUJuuJRPwFR5f"
]
}
]
}

so total fees, 11187.  6000 was to get back to on-chain
Never spent a satoshi for anything, just opened/closed a few channels.

@8KSS upon updating to the latest master, do the pending close transactions still persist? Also note that intermediate sweeping transaction won't show up in listchaintxns. By these I mean those transactions that are created when we spend HTLC transactions on our commitment, or when commitments are broadcast.

Nope didn’t spend anything.

@8KSS upon updating to the latest master, do the pending close transactions still persist?

For what it's worth, mine's still there.

"pending_force_closing_channels": [
    {
        "channel": {
            "remote_node_pub": "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432",
            "channel_point": "7cbc012a8c8c1472d560b77a5dbe9759288647d671aa550925bc0d59c4ada2e9:1",
            "capacity": "5000000",
            "local_balance": "4999276",
            "remote_balance": "0"
        },
        "closing_txid": "14f0121bfc785806a224b60a3a8f009babfba06e1ede38a756816199810e886f",
        "limbo_balance": "4999276",
        "maturity_height": 0,
        "blocks_til_maturity": 0,
        "recovered_balance": "0",
        "pending_htlcs": [
        ]
    }
]

}

lncli version 0.4.1 commit=b0709b45f7af9314481d06e617b1cee088fd708e

We recently fixed another bug related to sending out notification of spends that are already confirmed in the chain. Note that this only affected the btcd chain backend.

Is this something that should be cleared up in the latest version?
lnd version 0.4.1-beta commit=86fd9e361e04716b6a0d2e7146d6c19c0b4f05b5
Still seeing this stuck TX :(

Yes, as in we'll always only act on the ultimately confirmed commitment transaction. In your case, both outputs have been fully spent on the transaction, meaning that if you had any funds, they've been swept into the wallet.

That'll have to work, thanks.
In the long run it'd be preferable if channels couldn't get stuck this way in the first place to have to 'clean up' after them. I don't know how easily this is doable. I'm sure there are challenges. But still.
Many ghost channels piling up over time does not sound like a good thing to live with and it's suspcious that the solution could be automated. Anyway, I'm sure there are priorities, so for now a manual cleanup method is OK. Thanks in advance.

In the long run it'd be preferable if channels couldn't get stuck this way in the first place to have to 'clean up' after them.

Totally, that PR that just landed clears up all instances of weird situations like this we're aware of.

Many ghost channels piling up over time does not sound like a good thing to live with

Defiantly, they shouldn't pile up at all. What you're seeing is lingering behavior of the recently fixed bug. When we fixed the bug, we could have remove the faulty channels in an automated fashion. But then with that, there's a risk that we'd accidentally remove a non-faulty channel. As a result, it's safer to give users tools to pin point these faulty channels and remove them manually.


Icon request: Warehouse / Storage

Describe the requested icon
Should show a warehouse. More a hall than a factory, but not a normal house as well. Will be used to illustrate some area where stuff is stored.

Added warehouse, garage in v2.0.0

Thanks!


Add new French translations for Stretchly redesign

Add new French translations for Stretchly redesign.
Issue:  #584
Requirements

[x]  issue was opened to discuss proposed changes before starting implementation.
[x]  during development, node version specified in package.json was used (ie using nvm).
[x]  package versions and package-lock.json were not changed (npm install --no-save).
[x]  app version number was not changed.
[x]  all new code has tests to ensure against regressions.
[x] npm run lint reports no offenses.
[x] npm run test is error-free.
[x]  README and CHANGELOG were updated accordingly.

Description of the Change
New French translations for the app redesign.
Verification Process
Not verified yet.
Other information

@whiver I can merge this, then?

Sure, you can! Thanks :)


10.0.18362.1533  not supported

termsrv.zip

termsrv.zip

https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini

Reopened. Not included in official INI.


bug: Infinite scroll only works if it's a direct child of ion-content

I found another issue reporting this bug already, but it was closed. I'd like to know if there is any work around for this problem and if the there are any updates.
Bug Report
Ionic version:
[x] 5.x
Current behavior:
Infinite scroll only works if it's a direct child (and the list) of the ion-content element
Expected behavior:
It should work inside any element
Steps to reproduce:
someView.html:
<ion-content>
<ion-grid>
  <ion-row>
    <ion-col>
      <ion-card class="fixed-height">
       <ion-card-header></ion-card-header>
       <ion-card-content>
         <ion-list> ... </ion-list>
         <ion-infinite-scroll threshold="100px" (ionInfinite)="loadData($event)">
           <ion-infinite-scroll-content loadingText="Loading..."> </ion-infinite-scroll-content>
         </ion-infinite-scroll>
      </ion-card-content>
    </ion-card>
    </ion-col>
  </ion-row>
 </ion-grid>
</ion-content>

someView.component.ts
loadData(event) {
    console.log('loading more');
    event.target.complete();
  }

Ionic info:
Ionic:

   Ionic CLI                     : 5.2.7 (/usr/local/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 5.1.0
   @angular-devkit/build-angular : 0.803.26
   @angular-devkit/schematics    : 8.3.26
   @angular/cli                  : 8.3.26
   @ionic/angular-toolkit        : 2.2.0

Utility:

   cordova-res : not installed
   native-run  : 0.2.8 (update available: 1.0.0)

System:

   NodeJS : v12.16.3 (/Users/Garh/.nvm/versions/node/v12.16.3/bin/node)
   npm    : 6.14.4
   OS     : macOS Catalina

what is the issue?
if you are having two css tabs (not ion-tabs) that has one ion-content you can place infinitescroll as child element of ion-content. based on tap on css tab you can reset infinitescroll and call appropriate apis.  Infinitescroll designed that way you will have to put as an child element of ion-content

The issue is that you cannot use infinite scroll inside any element that isn't ion content

Infinitescroll designed that way you will have to put as an child element of ion-content

This isn't bug you can request for feature.

Infinitescroll designed that way you will have to put as an child element of ion-content

This isn't bug you can request for feature.

And how am I supposed to use it in the example I provided? According to Ionic docs, I can only have one ion content per page...

if you are having two css tabs (not ion-tabs) that has one ion-content you can place infinitescroll as child element of ion-content. based on tap on css tab you can reset infinitescroll and call appropriate apis. Infinitescroll designed that way you will have to put as an child element of ion-content

if you are having two css tabs (not ion-tabs) that has one ion-content you can place infinitescroll as a child element of ion-content. based on tap on CSS tab you can reset infinitescroll and call appropriate apis. Infinitescroll designed that way you will have to put as a child element of ion-content

Would you mind to share the code? I'm not sure I fully understand what you mean.

We ran into the one ion-content in a single view limitation with ion-virtual-scroll because we wanted to have a virtual scroll that wasn't a direct child to the Page's singular ion-content. We began using the Angular CDK's virtual scroll control in those instances (https://material.angular.io/cdk/scrolling/overview).
I remember watching an Ionic video chat from around a year or so ago where they talked about some issues with their homegrown virtual scroll and that they were planning to recommend framework-specific implementations from the respective ecosystems (such as the CDK virtual scroll in the case of Angular). Not sure what the position is today.
Using the Angular CDK's virtual scroll might not be the best solution for you, but thought I'd pass along the info in case it's helpful. 🙂

if you are having two css tabs (not ion-tabs) that has one ion-content you can place infinitescroll as a child element of ion-content. based on tap on CSS tab you can reset infinitescroll and call appropriate apis. Infinitescroll designed that way you will have to put as a child element of ion-content

Would you mind to share the code? I'm not sure I fully understand what you mean.

Could you provide reproduction i would be happy to apply some conditional logic there

Try to put it inside  tag.
Will it work?

Thanks for the issue! This issue is being closed due to the lack of a code reproduction. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.
Thank you for using Ionic!


No mesh in rviz showing

Description:
Install kimera in ubuntu18 without errors. Run the basic commands for running euroc data in the README. The whole bag can run till the end without any errors but no mesh is showing.
Command:
roslaunch kimera_vio_ros kimera_vio_ros_euroc.launch
rviz -d $(rospack find kimera_vio_ros)/rviz/kimera_vio_euroc.rviz
rosbag play --clock MH_01_easy.bag

Console output:
I0519 14:51:33.387197   379 RegularVioBackEnd.cpp:114] Using Regular VIO backend.
I0519 14:51:33.387293   379 PipelineModule.h:450] MISO Pipeline Module: Display has no output queue registered.
I0519 14:51:33.387828   379 RosOnlineDataProvider.cpp:45] Waiting for ROS time to be valid...
(Sim Time is enabled; run rosbag with --clock argument)
process[kimera_vio_ros/posegraph_viewer-2]: started with pid [380]
[ INFO] [1589921493.726398268]: Initializing pose graph visualizer
I0519 14:53:37.476522   379 RosOnlineDataProvider.cpp:56] Requested initialization from ground-truth. Initializing ground-truth odometry one-shot subscriber.
W0519 14:53:37.478446   379 RosOnlineDataProvider.cpp:65] Waiting for ground-truth pose to initialize VIO on ros topic: /kimera_vio_ros/gt_odom
E0519 14:53:40.550179   379 RosOnlineDataProvider.cpp:82] Missing ground-truth pose while trying for 3.00386 seconds.
Enabling autoInitialize and continuing without ground-truth pose.
I0519 14:53:40.562574   379 KimeraVioRos.cpp:114] Statistics
-----------                                  #	Log Hz	{avg     +- std    }	[min,max]
Display [ms]                            	    0
backend_input_queue Size [#]            	    0
data_provider_left_frame_queue Size [#] 	    0
data_provider_right_frame_queue Size [#]	    0
display_input_queue Size [#]            	    0
mesher_backend Size [#]                 	    0
mesher_frontend Size [#]                	    0
stereo_frontend_input_queue Size [#]    	    0
visualizer_backend_queue Size [#]       	    0
visualizer_frontend_queue Size [#]      	    0
visualizer_mesher_queue Size [#]        	    0
I0519 14:53:40.562610   483 Pipeline.h:184] Spinning Kimera-VIO.
I0519 14:53:40.818538   483 Pipeline.cpp:785] Frontend launched (parallel_run set to 1).
I0519 14:53:40.818589   483 Pipeline.cpp:600] ------------------- Initialize Pipeline with frame k = 1--------------------
W0519 14:53:40.818609   483 InitializationFromImu.cpp:26] InitializationFromImu: assumes that the vehicle is stationary and upright along some axis,and gravity vector is along a single axis!
I0519 14:53:40.871023   483 Pipeline.cpp:309] Before launching threads.
I0519 14:53:40.871157   483 Pipeline.cpp:814] Backend, mesher and visualizer launched (parallel_run set to 1).
I0519 14:53:40.871165   483 Pipeline.cpp:311]  launching threads.
W0519 14:53:41.066159   486 Mesher.cpp:1377] Missing landmark information to build 3D Mesh.
I0519 14:53:41.067255   379 KimeraVioRos.cpp:114] Statistics
-----------                                  #	Log Hz	{avg     +- std    }	[min,max]
Data Provider [ms]                      	    0
Display [ms]                            	    0
Mesher [ms]                             	    1	5.10853	{0.00000 +- 0.00000}	[0,0]
VioBackEnd [ms]                         	    1	5.12833	{0.00000 +- 0.00000}	[0,0]
VioFrontEnd Frame Rate [ms]             	    3	25.4317	{8.33333 +- 5.77350}	[5,15]
VioFrontEnd Keyframe Rate [ms]          	    1	5.20294	{43.0000 +- 0.00000}	[43,43]
VioFrontEnd [ms]                        	    4	16.2115	{17.0000 +- 17.9629}	[5,43]
Visualizer [ms]                         	    1	5.10477	{0.00000 +- 0.00000}	[0,0]
backend_input_queue Size [#]            	    1	0.00783201	{1.00000 +- 0.00000}	[1,1]
data_provider_left_frame_queue Size [#] 	    7	0.0548275	{1.00000 +- 0.00000}	[1,1]
data_provider_right_frame_queue Size [#]	    7	0.0548274	{1.00000 +- 0.00000}	[1,1]
display_input_queue Size [#]            	    2	0.0156638	{1.00000 +- 0.00000}	[1,1]
mesher_backend Size [#]                 	    1	0.00783215	{1.00000 +- 0.00000}	[1,1]
mesher_frontend Size [#]                	    4	0.0313288	{2.50000 +- 1.29099}	[1,4]
stereo_frontend_input_queue Size [#]    	    5	0.0391610	{1.00000 +- 0.00000}	[1,1]
visualizer_backend_queue Size [#]       	    1	0.00783215	{1.00000 +- 0.00000}	[1,1]
visualizer_frontend_queue Size [#]      	    4	0.0313288	{2.50000 +- 1.29099}	[1,4]
visualizer_mesher_queue Size [#]        	    1	0.00783210	{1.00000 +- 0.00000}	[1,1]
W0519 14:53:41.248561   484 Tracker.cpp:578] 1-point RANSAC (voting) could not find a solution.
W0519 14:53:41.280649   486 Mesher.cpp:1377] Missing landmark information to build 3D Mesh.
W0519 14:53:41.477052   486 Mesher.cpp:1377] Missing landmark information to build 3D Mesh.
I0519 14:53:41.563220   379 KimeraVioRos.cpp:114] Statistics
-----------                                  #	Log Hz	{avg     +- std    }	[min,max]
Data Provider [ms]                      	    0
Display [ms]                            	    6	6.55172	{4.00000 +- 9.79796}	[0,24]
Mesher [ms]                             	    3	4.94113	{0.666667 +- 0.577350}	[0,1]
VioBackEnd [ms]                         	    3	4.95144	{0.00000 +- 0.00000}	[0,0]
VioFrontEnd Frame Rate [ms]             	   11	17.1288	{6.36364 +- 4.98543}	[3,15]
VioFrontEnd Keyframe Rate [ms]          	    3	4.97439	{54.0000 +- 9.64365}	[43,61]
VioFrontEnd [ms]                        	   14	20.0818	{16.6429 +- 21.0443}	[3,61]
Visualizer [ms]                         	    3	4.94079	{0.00000 +- 0.00000}	[0,0]
backend_input_queue Size [#]            	    3	0.0234207	{1.00000 +- 0.00000}	[1,1]
data_provider_left_frame_queue Size [#] 	   17	0.132633	{1.00000 +- 0.00000}	[1,1]
data_provider_right_frame_queue Size [#]	   17	0.132633	{1.00000 +- 0.00000}	[1,1]
display_input_queue Size [#]            	    6	0.0468406	{1.00000 +- 0.00000}	[1,1]
mesher_backend Size [#]                 	    3	0.0234211	{1.00000 +- 0.00000}	[1,1]
mesher_frontend Size [#]                	   14	0.109265	{2.35714 +- 1.15073}	[1,4]
stereo_frontend_input_queue Size [#]    	   14	0.109266	{1.00000 +- 0.00000}	[1,1]
visualizer_backend_queue Size [#]       	    3	0.0234211	{1.00000 +- 0.00000}	[1,1]
visualizer_frontend_queue Size [#]      	   14	0.109265	{2.35714 +- 1.15073}	[1,4]
visualizer_mesher_queue Size [#]        	    3	0.0234208	{1.00000 +- 0.00000}	[1,1]
W0519 14:53:41.709491   483 DataProviderModule.cpp:103] Waiting for IMU data...
I0519 14:53:42.067512   379 KimeraVioRos.cpp:114] Statistics
-----------                                  #	Log Hz	{avg     +- std    }	[min,max]
Data Provider [ms]                      	    0
Display [ms]                            	   10	7.59147	{2.40000 +- 7.58947}	[0,24]
Mesher [ms]                             	    5	4.95752	{0.800000 +- 0.447214}	[0,1]
VioBackEnd [ms]                         	    5	4.96579	{0.400000 +- 0.547723}	[0,1]
VioFrontEnd Frame Rate [ms]             	   18	16.2319	{5.61111 +- 4.27219}	[2,15]
VioFrontEnd Keyframe Rate [ms]          	    5	4.98267	{56.6000 +- 7.89303}	[43,63]
VioFrontEnd [ms]                        	   23	19.7679	{16.7391 +- 22.0603}	[2,63]
Visualizer [ms]                         	    5	4.95717	{0.00000 +- 0.00000}	[0,0]
backend_input_queue Size [#]            	    5	0.0389128	{1.00000 +- 0.00000}	[1,1]
data_provider_left_frame_queue Size [#] 	   27	0.209827	{1.00000 +- 0.00000}	[1,1]
data_provider_right_frame_queue Size [#]	   27	0.209827	{1.00000 +- 0.00000}	[1,1]
display_input_queue Size [#]            	   10	0.0778237	{1.00000 +- 0.00000}	[1,1]
mesher_backend Size [#]                 	    5	0.0389133	{1.00000 +- 0.00000}	[1,1]
mesher_frontend Size [#]                	   23	0.178856	{2.43478 +- 1.12112}	[1,4]
stereo_frontend_input_queue Size [#]    	   25	0.194277	{1.00000 +- 0.00000}	[1,1]
visualizer_backend_queue Size [#]       	    5	0.0389133	{1.00000 +- 0.00000}	[1,1]
visualizer_frontend_queue Size [#]      	   23	0.178856	{2.43478 +- 1.12112}	[1,4]
visualizer_mesher_queue Size [#]        	    5	0.0389128	{1.00000 +- 0.00000}	[1,1]

The pose seems being updated. I checked if there is mesh topic by
rostopic echo /kimera_vio_ros/mesh

I got
WARNING: no messages received and simulated time is active.
Is /clock being published?

Then I checked /clock
rostopic echo /clock

I got
...
clock:
  secs:<PHONE_NUMBER>
  nsecs: 287217368
---
clock:
  secs:<PHONE_NUMBER>
  nsecs: 297334446
---
clock:
  secs:<PHONE_NUMBER>
  nsecs: 307413524
---
clock:
  secs:<PHONE_NUMBER>
  nsecs: 317497013
---
clock:
  secs:<PHONE_NUMBER>
  nsecs: 327580458
---
...

Seems /clock is being published correctly.
Additional files:
Please attach all the files needed to reproduce the error.

Please give also the following information:

SparkVio branch, tag or commit used:
GTSAM version used: develop
OpenGV version used: master
OpenCV version used: 3.4
Operating system and version (e.g. Ubuntu 16.04 or Windows 10): ubuntu18 in docker
Did you change the source code? (yes / no): no

Hi @zhaozhongch, can you check the params/Euroc/flags/stereoVIOEuroc.flags file, there should be this param:
**# Type of 3D Visualization:
# 0: mesh 3d
# 1: pointcloud
# 2: none
--viz_type=1**

Set --viz_type=0

I modified that number to 0 but it seems it doesn't work. Still no mesh.
I downgrade to ubunu16, reinstall everything, and got the same result. Still no mesh. Pretty confusing because the system can run.
I might have made some silly operations during the installation but I double-checked the mesh_rviz_markers package is installed with no errors...

Seems like I can see it either in the current master, thank you for raising the issue! I'll try to look at it tomorrow, in the meantime, please use a commit previous to the last merge.

I'm experiencing the same issue. I have done the flag change and switched Kimera-VIO-ROS to that mentioned commit. As well as switch Kimera-VIO to 79174b191496653380dc185c85356c5b9ace2e50.

@ToniRV  I am experiencing the same issue. When I just checked the code, I found that it's not the problem with publishing mesh and mesh rviz plugin, There is no mesh creation happening. If there is any mesh and if there is any subscriber, then the only mesh will publish.

Thanks for the feedback! I'm on a tight schedule right now, but will give it a try tomorrow :+1:

I'm experiencing the same issue. I have done the flag change and switched Kimera-VIO-ROS to that mentioned commit. As well as switch Kimera-VIO to 79174b191496653380dc185c85356c5b9ace2e50. Nothing gets published on /kimera_vio_ros/mesh

I did the same you`ve described but nothing helped. Did you solve this issue with no mesh created somehow  ?

Was experiencing the same issue and switching Kimera-VIO-ROS to the mentioned commit did not help. Also, I have tried the commit from Apr 15 (considering the commits from the Dockerfile from goseek-challenge), mesh visualization was also not working there. But these commits worked for me:
Kimera-VIO-ROS: c535109a5e8490be9fd5226a02faee509e878eb9 from Mar 13 (https://github.com/MIT-SPARK/Kimera-VIO-ROS/commit/c535109a5e8490be9fd5226a02faee509e878eb9)
Kimera-VIO: a5109c7157482bb1203918512ef6593e226507f7 from Mar 11 (https://github.com/MIT-SPARK/Kimera-VIO/commit/a5109c7157482bb1203918512ef6593e226507f7)
Gtsam: master branch

I managed to get a visible mesh in RVIZ with the EUROC dataset, although without textures. Here's how I did it:

In Kimera-VIO set return_mesh_2d=true in params/Euroc/flags/Mesher.flags. Mesh data should now be published on the /kimera_vio_ros/mesh topic.
In RVIZ, after opening the kimera_vio_euroc.rviz file, go to the 3D Mesh Textured settings. Remove the value for the Texture topic (it is set to /kimera_vio_ros/debug_mesh_img/image_raw which has no publishers, removing this value enables drawing without texture). Set the Polygon Mode to WIREFRAME or SOLID and set the Shader Program to something else than TEXTURE.
Lastly, I had a problem on one machine with the wireframe being drawn in white on a white background. I changed the background color of RVIZ to see the mesh. On a different machine it was fine though.

I hope this issue gets a fix of some sorts, as it seems the texture topic was removed with no replacement.

@pherbers thanks for the information, I managed to display the meshes as well and I need to changed to background color as well (the meshes are displayed in white)
Fabrice

How to visualize multi-frame mesh in the rviz-windows? I try to modify the file Mesher.flags ----reduce_mesh_to_time_horizon=false, but it dosen't change.

@tftangming I haven't added the time-horizon visualization to ROS (Rviz), but you can visualize it if you run the OpenCV visualizer without ROS.

With https://github.com/MIT-SPARK/Kimera-VIO/pull/113 and https://github.com/MIT-SPARK/Kimera-VIO-ROS/pull/109
The mesh viz in Rviz and OpenCV visualizer should be all visible by default, at least on the Euroc Dataset.


RM Pro v1 Device not found "2797"

Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code: "2797". The device is connected to your network with the IP address "<IP_ADDRESS>".

Broadlink RM PRO:
Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code:                                                                      "4ead".
BroadLink-Outlet:
Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code:                                                                      "947a".

Sorry, "4ead" isn't RM Pro, but Thermostat.

@galfaroth I've added support for the RM Pro you mentioned.
@S474N the plugin should now ignore those two you provided, thanks!


Assist Microphone Addon: ALSA lib underrun occurred (inside a VM)

Hi, today I was playing with Assist Microphone Add-on for HA. Unfortunately I get only to the point where i get this error in Assist Microphone Logs.
Edit: It's worth to mention, that a standard rhasspy Add-on is working perfectly fine with the same setup.
My system

Proxmox VM with HA OS (pass through sound card & Anker PowerConf S330)
Home Assistant 2023.10.2
Supervisor 2023.10.0
Operating System 10.5
UI 20231005.0 - latest

Connected Speakers/Mics/Sound Cards

Anker PowerConf S330 (USB) - chosen in Assist Microphone Add-on configuration
External SoundCard used by Mopidy Add-on (later I removed it without any impact on issue)
Intel HDA sound card pass through to VM

Assist Microphone Logs
...
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
...

ha audio info
[core-ssh ~]$ ha audio info
audio:
  application:
  - addon: 47701997_assist_microphone
    index: 193
    mute: false
    name: ALSA plug-in [python3.11]
    stream_index: 0
    stream_type: output
    volume: 1
  - addon: 47701997_assist_microphone
    index: 1
    mute: false
    name: ALSA plug-in [python3.11]
    stream_index: 1
    stream_type: input
    volume: 1
  card:
  - driver: module-alsa-card.c
    index: 0
    name: alsa_card.usb-ANKER_Anker_PowerConf_S330_ACCUDP1C49600164-00
    profiles:
    - active: false
      description: Analog Stereo Input
      name: input:analog-stereo
    - active: false
      description: Digital Stereo (IEC958) Input
      name: input:iec958-stereo
    - active: false
      description: Analog Stereo Output
      name: output:analog-stereo
    - active: true
      description: Analog Stereo Duplex
      name: output:analog-stereo+input:analog-stereo
    - active: false
      description: Analog Stereo Output + Digital Stereo (IEC958) Input
      name: output:analog-stereo+input:iec958-stereo
    - active: false
      description: Digital Stereo (IEC958) Output
      name: output:iec958-stereo
    - active: false
      description: Digital Stereo (IEC958) Output + Analog Stereo Input
      name: output:iec958-stereo+input:analog-stereo
    - active: false
      description: Digital Stereo Duplex (IEC958)
      name: output:iec958-stereo+input:iec958-stereo
    - active: false
      description: "Off"
      name: "off"
  - driver: module-alsa-card.c
    index: 1
    name: alsa_card.pci-0000_08_0c.0
    profiles:
    - active: false
      description: Analog Stereo Input
      name: input:analog-stereo
    - active: false
      description: Analog Stereo Output
      name: output:analog-stereo
    - active: true
      description: Analog Stereo Duplex
      name: output:analog-stereo+input:analog-stereo
    - active: false
      description: "Off"
      name: "off"
  input:
  - applications:
    - addon: 47701997_assist_microphone
      index: 1
      mute: false
      name: ALSA plug-in [python3.11]
      stream_index: 1
      stream_type: input
      volume: 1
    card: 0
    default: true
    description: Anker PowerConf S330 Analog Stereo
    index: 1
    mute: false
    name: alsa_input.usb-ANKER_Anker_PowerConf_S330_ACCUDP1C49600164-00.analog-stereo
    volume: 1
  - applications: []
    card: 1
    default: false
    description: HDA Intel Analog Stereo
    index: 3
    mute: true
    name: alsa_input.pci-0000_08_0c.0.analog-stereo
    volume: 0.058441162109375
  output:
  - applications:
    - addon: 47701997_assist_microphone
      index: 193
      mute: false
      name: ALSA plug-in [python3.11]
      stream_index: 0
      stream_type: output
      volume: 1
    card: 0
    default: true
    description: Anker PowerConf S330 Analog Stereo
    index: 0
    mute: false
    name: alsa_output.usb-ANKER_Anker_PowerConf_S330_ACCUDP1C49600164-00.analog-stereo
    volume: 1
  - applications: []
    card: 1
    default: false
    description: HDA Intel Analog Stereo
    index: 1
    mute: false
    name: alsa_output.pci-0000_08_0c.0.analog-stereo
    volume: 1
host: <IP_ADDRESS>
update_available: false
version: 2023.06.0
version_latest: 2023.06.0

ha audio log
[core-ssh ~]$ ha audio log
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/alsa-mixer.sh
[17:38:34] INFO: Adjust ALSA mixer settings for /dev/snd/controlC0
[17:38:35] INFO: Adjust ALSA mixer settings for /dev/snd/controlC1
[17:38:35] INFO: Adjust ALSA mixer settings for /dev/snd/controlC2
cont-init: info: /etc/cont-init.d/alsa-mixer.sh exited 0
cont-init: info: running /etc/cont-init.d/filesystem.sh
cont-init: info: /etc/cont-init.d/filesystem.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun alsa (no readiness notification)
services-up: info: copying legacy longrun pulseaudio (no readiness notification)
s6-rc: info: service legacy-services successfully started
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
W: [pulseaudio] main.c: Home directory of user 'root' is not '/var/run/pulse', ignoring.
W: [pulseaudio] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support.
W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card0: No such file or directory
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-0000_00_1b.0" card_name="alsa_card.pci-0000_00_1b.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card2: No such file or directory
N: [pulseaudio] alsa-util.c: Disabling timer-based scheduling because running inside a VM.
N: [pulseaudio] alsa-util.c: Disabling timer-based scheduling because running inside a VM.
W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card1: No such file or directory
N: [pulseaudio] alsa-util.c: Disabling timer-based scheduling because running inside a VM.
N: [pulseaudio] alsa-util.c: Disabling timer-based scheduling because running inside a VM.
E: [pulseaudio] module-rescue-streams.c: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
E: [alsa-sink-USB Audio] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
E: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
E: [alsa-sink-USB Audio] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
E: [alsa-source-USB Audio] alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read.
E: [alsa-source-USB Audio] alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
E: [alsa-source-USB Audio] alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

+1
Using Anker PowerConf S330 Analog Stereo (latest firmware)
Home Assistant Yellow
No external sound card.
Home Assistant 2023.10.2
Supervisor 2023.10.0
Operating System 10.5

Resolved in 4731121de02bff300f2be5e3c532afa2e86e22a5


Add support for landing zones

Add example for different landing zone examples

HUB/PRD/QA/DEV
HUB/PRD/QA/HOM/DEV
HUB/PRD/QA/DEV/HOM/SBX

issue being dealt in branch feature/landing_zones

Landing zone examples are completed. Waiting for main reference for LPG config PR under https://github.com/oracle-devrel/terraform-oci-cloudbricks-lpg-config/pull/4 to be approved and merged to main to continue working on this.

Resolved on https://github.com/oracle-devrel/terraform-oci-cloudbricks-examples/pull/5


script.Add accepts a CallableFunc value

fixes #77
I've the conversion in scripts.Add instead of objects.FromInterface as it is not clear that objects.FromInterface will never be called for builtins.

I think it's safe to assume that builtin functions will be defined explicitly, not through objects.FromInterface. We can move it inside objects.FromInterface.

Btw, not sure if you know this or not, but, you can auto-close related issue by using 'fixes' or 'resolves': https://help.github.com/en/articles/closing-issues-using-keywords

Done

Thanks @earncef !


Add None marker

Purpose:

fixes #3057

This is a great solution @Gray-lab, thanks so much for this PR! I'm merging it in now 🚀


[MWPW-142899] Add additional IMS scopes for Universal Navigation integration

The Universal Navigation uses additional IMS scopes to render user data (avatar and firefly credits balance). Adding the additional scope will ensure that the Profile Menu is rendered correctly when the Universal Navigation is enabled.
Note: all known IMS client IDs from the list - https://wiki.corp.adobe.com/pages/viewpage.action?spaceKey=adobedotcom&title=Adobe.com+IMS+Client+IDs -  have been previously granted access for these additional IMS scopes.
Resolves: MWPW-142899
Test URLs:

Before: https://main--milo--adobecom.hlx.page/drafts/narcis/default?martech=off
After: https://gnav--milo--adobecom.hlx.page/drafts/narcis/default?martech=off

Should we change the description to something more actionable, since each consumer will need to add those scopes to their scripts/ims configs too?

@mokimo - I checked existing Milo projects and they inherit the scope configuration from Milo. However, the integration wiki will account for this step, all consumers are required to add the additional scope - https://wiki.corp.adobe.com/display/adobedotcom/Universal+Navigation+integration+guide

a small addition to ensure that the same default scope is set if not able to retrieve from config

That was going to be my next suggestion, great that it's already in!

Since not including those scopes leads to users not being able to sign in
One more note on this: not including the scopes in the configuration will not break the sign in functionality. The functionality is broken when the scopes are included in the config, but they are not approved in IMSS. I have manually checked all IMS client IDs and all have been granted the scopes.


Connect to On-Demand instance using SQL Authentication

Hi,
can you confirm that the SQL Authentication is working on on-demand instances?
I am always getting a 18456 error.
Thanks,
JP

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

ID: 16e95996-8204-c098-1063-041296e5482d
Version Independent ID: 43de2764-111b-38c4-dda1-b5c68fca6d15
Content: Connect with VSTS - Azure Synapse Analytics
Content Source: articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-query-visual-studio.md
Service: synapse-analytics
Sub-service: sql-dw
GitHub Login: @kevinvngo
Microsoft Alias: kevin

@gpitzalis
Thank you for reaching out. At this time we are reviewing the ask and will provide an update as appropriate

Hello @gpitzalis and thank you for your patience.  I can confirm SQL authentication is working (from SSMS).  Here is how I tested:

I created a new Synapse workspace and associated storage
Launched the workspace and created a new login as per doc CREATE LOGIN Mary WITH PASSWORD = 'XXXXXXXXX';
Created new database (as users must be created inside a database other than master) CREATE DATABASE first;
Reload the workspace page so I can select the new database
Select the new database and then create new user CREATE USER Mary FROM LOGIN Mary;
Open SSMS, and enter the on-demand endpoint, login name and login password.
Connect and able to see only the new database.

Can you tell me if you did something differently?  I am a little confused; This issue was opened against the doc using Visual Studio.  Visual Studio and On-Demand SQL are not mentioned together.

@gpitzalis
We will now proceed to close this thread as we have not heard back from you. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.


Add android build workflow & Add CODEOWNERS

Features

Add a workflow that runs ./gradlew build on each push or PR on dev branch.
example:

Add CODOWNERS file.

Improvements

For android workflow you can add also ./gradlew spotlessCheck for code lint and ./gradlew apiCheck.
Update repository settings for taking full advantage from CODOWNERS.

Thank @driouecheMed for the contribution, next time please separate the updates you've done on different branches.


Public EN

Proposed changes
Added link to public EN
gitbook link: https://app.gitbook.com/o/-LZ3M2TduHoL5IluFRpr/s/gwneSXOk0UYiVPoEYAO7/dapp/json-rpc/public-en
Types of changes
Please put an x in the boxes related to your change.

[ ] Minor Issues and Typos
[x] Major Content Contribution
[ ] Others

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to reach out. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING GUIDELINES
[x] I have signed the CLA
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Related issues

Please leave the issue numbers or links related to this PR here.

Further comments
If this is a relatively large content contribution, kick off the discussion by explaining why you would suggest the content contribution, etc...

@dcground @kjhman21  @neoofklaytn Please review when you can :)


D3D12CreateDevice failed after update to Win10 Anniversary Edition

Hi,
I am having issue to as discussed in #234. All the samples were working before the Win10 upgrade, but now on v1607 with debug layer enabled (the Graphics Tools is installed) the D3D12CreateDevice failed with E_INVALIDARG. However, if debug layer is not enabled or Release mode is used the device is created and the samples run fine.
Some info about my PC:
WIndows 10 Enterprise
Version: 1607
Windows Build: 14393.693.amd64fre.rs1_release.161220-1747
GPU Info
Adapter 0: NVIDIA GeForce GTX 970
D3D Support = D3D12 (FL_12_1)
Hardware ID = 10DE:13C2
UMD Version = <IP_ADDRESS>66
ETW Markers = 9(Yes) 10+(Yes)
Adapter 1: Microsoft Basic Render Driver
D3D Support = D3D12 (FL_12_1)
Hardware ID = 1414:008C
UMD Version = 10.0.14393.576
ETW Markers = 9(No) 10+(No)
Executing DXCap version
Path: C:\Windows\system32\DXCap.exe
DxCap.exe                       : 10.0.14393.0 (07/15/16 19:13) 1,171 KB
System32 Info
DxCap.exe                       : 10.0.14393.0 (07/15/16 19:13) 1,171 KB
DxCaptureReplay.dll             : 10.0.14393.0 (07/15/16 19:23) 14,051 KB
DxToolsMonitor.dll              : 10.0.14393.0 (07/15/16 19:12) 194 KB
DxToolsOfflineAnalysis.dll      : 10.0.14393.0 (07/15/16 19:13) 1,959 KB
DxToolsReportGenerator.dll      : 10.0.14393.0 (07/15/16 19:58) 93 KB
DxToolsReporting.dll            : 10.0.14393.0 (07/15/16 19:11) 179 KB
perf_gputiming.dll              : 10.0.14393.0 (07/15/16 19:22) 348 KB
VsGraphicsCapture.dll           : 10.0.14393.0 (07/15/16 19:13) 172 KB
VsGraphicsDesktopEngine.exe     : 10.0.14393.0 (07/15/16 19:16) 5,714 KB
VsGraphicsExperiment.dll        : 10.0.14393.0 (07/15/16 19:12) 291 KB
VsGraphicsProxyStub.dll         : 10.0.14393.0 (07/15/16 19:28) 89 KB
VsGraphicsRemoteEngine.exe      : 10.0.14393.0 (07/15/16 19:16) 4,853 KB
d3d11_3sdklayers.dll            : 10.0.14393.0 (07/15/16 19:19) 1,293 KB
d3d12SDKLayers.dll              : 10.0.14393.0 (07/15/16 19:14) 2,428 KB
d3d12warp.dll                   : 10.0.14393.0 (07/15/16 19:15) 6,429 KB
d2d1debug3.dll                  : 10.0.14393.0 (07/15/16 19:22) 419 KB
dxgidebug.dll                   : 10.0.14393.0 (07/15/16 19:25) 330 KB
SysWow64 Info
DxCap.exe                       : 10.0.14393.0 (07/15/16 18:29) 931 KB
DxCaptureReplay.dll             : 10.0.14393.0 (07/15/16 18:39) 11,397 KB
DxToolsMonitor.dll              : 10.0.14393.0 (07/15/16 18:28) 152 KB
DxToolsOfflineAnalysis.dll      : 10.0.14393.0 (07/15/16 18:28) 1,475 KB
DxToolsReportGenerator.dll      : 10.0.14393.0 (07/15/16 18:58) 93 KB
DxToolsReporting.dll            : 10.0.14393.0 (07/15/16 18:28) 125 KB
perf_gputiming.dll              : 10.0.14393.0 (07/15/16 18:35) 268 KB
VsGraphicsCapture.dll           : 10.0.14393.0 (07/15/16 18:29) 131 KB
VsGraphicsDesktopEngine.exe     : 10.0.14393.0 (07/15/16 18:32) 4,489 KB
VsGraphicsExperiment.dll        : 10.0.14393.0 (07/15/16 18:29) 226 KB
VsGraphicsProxyStub.dll         : 10.0.14393.0 (07/15/16 18:44) 41 KB
VsGraphicsRemoteEngine.exe      : 10.0.14393.0 (07/15/16 18:32) 3,615 KB
d3d11_3sdklayers.dll            : 10.0.14393.0 (07/15/16 18:37) 1,049 KB
d3d12SDKLayers.dll              : 10.0.14393.0 (07/15/16 18:37) 1,890 KB
d3d12warp.dll                   : 10.0.14393.0 (07/15/16 18:31) 4,861 KB
d2d1debug3.dll                  : 10.0.14393.0 (07/15/16 18:38) 363 KB
dxgidebug.dll                   : 10.0.14393.0 (07/15/16 18:41) 234 KB
VS2015 VsGraphics
DxDebugEngine.dll               : 14.0.25420.1 (06/20/16 13:45) 22 KB
DxDebugEngineWorker.dll         : 14.0.25420.1 (06/20/16 13:45) 22 KB
DxDebuggerApi.dll               : 14.0.25420.1 (06/20/16 13:45) 22 KB
DxTex.dll                       : 14.0.23107.0 (07/06/15 23:51) 403 KB
VsGraphics.exe                  : 14.0.25420.1 (06/20/16 13:45) 2,182 KB
VsGraphicsCore.dll              : 14.0.23107.0 (07/06/15 23:51) 929 KB
VsGraphicsDebuggerPkg.dll       : 14.0.25420.1 (06/20/16 13:45) 22 KB
VsGraphicsDesktopEngine.exe     : 14.0.25420.1 (06/20/16 13:45) 23 KB
VsGraphicsNativeUtils.dll       : 14.0.25420.1 (06/20/16 13:45) 22 KB
VsGraphicsProxyStub.dll         : 14.0.25420.1 (06/20/16 13:45) 22 KB
DiagnosticsHub.js               : (06/20/16 13:45) 12 KB
Plugin.js                       : (06/20/16 13:45) 12 KB
VS2015 VsGraphics\amd64
GpuProfilingCollectionAgent.dll : 14.0.25420.1 (06/20/16 13:45) 22 KB
VS2015 VsGraphics\x86
GpuProfilingCollectionAgent.dll : 14.0.25420.1 (06/20/16 13:45) 22 KB
VS2015 x86 Remote Debugger
VsGraphicsCaptureEngine.dll     : 14.0.25420.1 (06/20/16 13:45) 151 KB
VsGraphicsHelper.dll            : 14.0.25420.1 (06/20/16 13:45) 1,784 KB
VsGraphicsRemoteEngine.exe      : 14.0.25420.1 (06/20/16 13:45) 2,503 KB
VS2015 amd64 Remote Debugger
VsGraphicsCaptureEngine.dll     : 14.0.25420.1 (06/20/16 12:51) 195 KB
VsGraphicsHelper.dll            : 14.0.25420.1 (06/20/16 12:51) 3,114 KB
VsGraphicsRemoteEngine.exe      : 14.0.25420.1 (06/20/16 12:51) 3,490 KB
Windows Phone Binaries
Dxcap.exe                       : File not found
DxCaptureReplay.dll             : File not found
DxToolsMonitor.dll              : File not found
DxToolsOfflineAnalysis.dll      : File not found
DxToolsReporting.dll            : File not found
VsGraphicsCapture.dll           : File not found
VsGraphicsCaptureEngine.dll     : 14.0.25420.1 (06/20/16 12:27) 97 KB
VsGraphicsExperiment.dll        : File not found
VsGraphicsRemoteEngine.exe      : File not found
Windows Phone Emulator Binaries
Dxcap.exe                       : File not found
DxCaptureReplay.dll             : File not found
DxToolsMonitor.dll              : File not found
DxToolsOfflineAnalysis.dll      : File not found
DxToolsReporting.dll            : File not found
VsGraphicsCapture.dll           : File not found
VsGraphicsCaptureEngine.dll     : 14.0.25420.1 (06/20/16 13:45) 92 KB
VsGraphicsExperiment.dll        : File not found
VsGraphicsRemoteEngine.exe      : File not found
GPU Usage Data
Feature Support       : Yes
D3D9 Driver Support   : Pass
D3D10+ Driver Support : Pass
OS Version Check      : Pass
Driver Version Check  : Pass

Thinking it might be conflicting with previous version, I have tried this on a clean install of windows 10 Anniversary Edition with SDK. But that also results in same issue. It seems I am missing something, but not sure what as same steps had previously worked with the older Win 10/SDK.
Any support on this would be very helpful.
Thanks,
Raj

The problem looks like mismatched sdk layers binaries:
Windows Build: 14393.693.amd64fre.rs1_release.161220-1747
d3d12SDKLayers.dll : 10.0.14393.0 (07/15/16 19:14) 2,428 KB
You can try reinstalling the Graphics Tools optional feature, or rescanning for Windows Updates.  Either (or both) of those will usually resolve the issue.

Thanks bobbrow for the reply..
I have tried uninstalling/installing the graphics tools multiple times, but unfortunately it has not worked. I am assuming getting latest windows update should also load in the latest graphics tools in the feature list which seems to be not happening in our case. Also we are updated to quite a latest windows update. Would it be possible to point out anything  we might be missing that we can't update to latest tools. Also is there a package of latest graphics tools that we could use for a manual install rather as Add a feature.
Thanks,
Rajeev

Also just to mention..we do have internal IT department WSUS server...so usually we have HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer set to 1. So have to manually set it 0 and reboot to fill the optional feature list. Is there any other registry value that might be effecting getting latest updates for optional features and should be changed?

Unfortunately, I don't know very much about that.  If your IT department is blocking the update I think you'll need to talk with them about letting the Feature on Demand updates go through.


Fix kes period start interval in kes-period-info command

Resolves: #3689

bors r+

bors r+

Subsumed by #3718


Card outline when hovering/clicking in Safari is off.

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
Steps:

Open https://mui.com/material-ui/react-card/#primary-action on Safari and click/hover on the Card.
Make sure you zoom in and check the corners of the card
You will see that the corners doesn't get the rounded borders

I think this is related to the following issue and the issues linked to this which was fixed by @mj12albert :
https://github.com/mui/material-ui/pull/36213
Current behavior 😯
The current behaviour of the Card component with outline styling is off on Safari, this doesn't only affect the docs but also the component. There seems to be a working solution for this used in the linked PR above?

Expected behavior 🤔
I would've expected the styles to be the same on Safari as on Chrome for instance.
Context 🔦
No response
Your environment 🌎
No response

@ozgurbaserdem I think this is a different issue and looks like it's from Safari because the Card already applies overflow: 'hidden'.

@ozgurbaserdem I think this is a different issue and looks like it's from Safari because the Card already applies overflow: 'hidden'.

Yeah I think you might be right. I think it could be related to what is described here regarding outline/border-radius described here: https://medium.com/@jeandesravines/use-border-radius-and-outline-simultaneously-on-safari-14ce92889e1f
I think it's the button element that gets rendered in CardActionArea that affects this?

@ozgurbaserdem Thanks for reporting this, it's hard to see, especially in the light theme.
It seems that CardActionArea (the button) not inheriting border-radius from the parent Card

Assuming that CardActionArea is intended to be used as a direct child of Card (is that correct @siriwatknp ?), I think this should fix it:
diff --git a/packages/mui-material/src/CardActionArea/CardActionArea.js b/packages/mui-material/src/CardActionArea/CardActionArea.js
index 93d24c5fae..38d14697e9 100644
--- a/packages/mui-material/src/CardActionArea/CardActionArea.js
+++ b/packages/mui-material/src/CardActionArea/CardActionArea.js
@@ -25,6 +25,7 @@ const CardActionAreaRoot = styled(ButtonBase, {
 })(({ theme }) => ({
   display: 'block',
   textAlign: 'inherit',
+  borderRadius: 'inherit',
   width: '100%',
   [`&:hover .${cardActionAreaClasses.focusHighlight}`]: {
     opacity: (theme.vars || theme).palette.action.hoverOpacity,


Forest chain muxer error

Issue summary

I got hit by this several times already. In short, sometimes, in case of an error (e.g., state mismatch) and after throwing a ctrl-c (I am not sure it's 100% needed, though) Forest will start spamming the terminal with:
2023-03-15T12:00:49.755785Z ERROR forest_chain_sync::chain_muxer: Evaluating the network head failed, retrying. Error = P2PEventStreamReceive("receiving on a closed channel")
2023-03-15T12:00:49.755788Z  INFO forest_chain_sync::chain_muxer: Evaluating network head...
2023-03-15T12:00:49.755789Z ERROR forest_chain_sync::chain_muxer: Evaluating the network head failed, retrying. Error = P2PEventStreamReceive("receiving on a closed channel")
2023-03-15T12:00:49.755792Z  INFO forest_chain_sync::chain_muxer: Evaluating network head...
2023-03-15T12:00:49.755793Z ERROR forest_chain_sync::chain_muxer: Evaluating the network head failed, retrying. Error = P2PEventStreamReceive("receiving on a closed channel")
2023-03-15T12:00:49.755796Z  INFO forest_chain_sync::chain_muxer: Evaluating network head...
2023-03-15T12:00:49.755798Z ERROR forest_chain_sync::chain_muxer: Evaluating the network head failed, retrying. Error = P2PEventStreamReceive("receiving on a closed channel")
2023-03-15T12:00:49.755802Z  INFO forest_chain_sync::chain_muxer: Evaluating network head...
2023-03-15T12:00:49.755804Z ERROR forest_chain_sync::chain_muxer: Evaluating the network head failed, retrying. Error = P2PEventStreamReceive("receiving on a closed channel")
2023-03-15T12:00:49.755806Z  INFO forest_chain_sync::chain_muxer: Evaluating network head...
2023-03-15T12:00:49.755808Z ERROR forest_chain_sync::chain_muxer: Evaluating the network head failed, retrying. Error = P2PEventStreamReceive("receiving on a closed channel")
2023-03-15T12:00:49.755810Z  INFO forest_chain_sync::chain_muxer: Evaluating network head...
2023-03-15T12:00:49.755812Z ERROR forest_chain_sync::chain_muxer: Evaluating the network head failed, retrying. Error = P2PEventStreamReceive("receiving on a closed channel")
2023-03-15T12:00:49.755815Z  INFO forest_chain_sync::chain_muxer: Evaluating network head...
2023-03-15T12:00:49.755817Z ERROR forest_chain_sync::chain_muxer: Evaluating the network head failed, retrying. Error = P2PEventStreamReceive("receiving on a closed channel")
2023-03-15T12:00:49.755819Z  INFO forest_chain_sync::chain_muxer: Evaluating network head...
2023-03-15T12:00:49.755821Z ERROR forest_chain_sync::chain_muxer: Evaluating the network head failed, retrying. Error = P2PEventStreamReceive("receiving on a closed channel")

It is impossible to kill it with a regular ctrl-c; one has to open another tab and pkill -9 forest. To make it even worse, this uses a significant amount of CPU (probably coming from endless logs flooding the terminal without sleep). It's hard to reproduce, but it happened quite a few times when I sent SIGINT at the wrong moment.
We need to handle it better, but I have no clear solution. The simple idea is to shut down Forest after some amount of errors in a given interval.
Other information and links

Could you give more details on how to reproduce this error (at which moment do you hit ctrl-c)?
Maybe the ChainMuxer future needs special case when shutting down the Tokio runtime.

Not really. As I mentioned, it's difficult to reproduce. To no surprise, it happens during sync. I often encountered it when analysing state mismatches while pressing ctrl-c just after the state mismatch error.

@LesnyRumcajs But can it be reproduced on calibnet?

Yeah, it was happening on calibnet on my machine. The logs I posted are from mainnet from the sync-check.


Does not exit

Hi, i would like to be able to use this scanner in a batch procedure.
But if one of the libraries is edited, then the scanner does not exit and does not create a log file, but seems to hang at the end.
This is what i use
%MDP_PATCH_ROOT%\log4j2-scan.exe --force-fix --report-csv --report-path "%LOGF1%" %1

What's the meaning of edit..? Need more details. Try run in cmd with --trace option.


Add 'oled' package to support OLED display module device

Enable users to plug an OLED display module like this to quickly check stats like IP address.
https://a.co/d/7iCWAA5

run.py is modified to add I2C devices accessible from the container
the container image is based on ubuntu:22.04 (to shrink the resulting image down to 405MB, not 9GB)

@tokk-nv for the github token, instead of modifying many functionss, can you instead check for $GITHUB_TOKEN environment variable inside github_latest_commit()?   os.environ.get('GITHUB_TOKEN')

Filed this based on jp6 (https://github.com/dusty-nv/jetson-containers/pull/340), so closing this old PR.


Avoid a useless animation when the spinner is invisible

In looking at a profile, I noticed in Marker chart that there's an animation for loading-icon.gif even if this icon isn't visible. This patch doesn't completely remove it but just slightly postpones it.

/botio-linux preview

@calixteman Possibly a pointless idea, but something that I've been wondering recently:
Would performance improve if we replaced this (very old) GIF loading-icon with a SVG one instead? To test that theory, using the existing images/loading.svg might work.

@calixteman Possibly a pointless idea, but something that I've been wondering recently: Would performance improve if we replaced this (very old) GIF loading-icon with a SVG one instead? To test that theory, using the existing images/loading.svg might work.

Interesting I was wondering exactly the same question but for a pure css spinner, for example: https://loading.io/css/, the second on the first line looks pretty simple (few others are using several divs). Anyway I'll have a look to see if it improves something (tbh I was a little disappointed to see that the animation is running even if the spinner is not visible but maybe it's inherent to gif format).


Not so early exit

Why.

@tetraptych I am also happy to only change this temporarily. But now that we are exposing closest provider and that the app is static, it makes sense to optimize for results instead of speed. Happy to consider other options

Then should we have early exit at all? IIRC this can be replaced with None (or possibly 0, or possible -1.0...)


Runtime error occurred in Image Ids: CUDA error: device-side assert triggered

There is Runtime error when I am testing the models with batch-size other than 1.
You can see the repetitive error below -
Runtime error occurred in Image Ids: 451,456,461,467,473,477,478,479
CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Runtime error occurred in Image Ids: 458,459,460,462,463,464,465,466
CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
  2%|____                                                                                | 59/3306 [00:08<04:41, 11.53it/s]Runtime error occurred in Image Ids: 468,469,470,471,472,474,475,476
CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Runtime error occurred in Image Ids: 480,482,487,489,490,491,492,494
CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

Is there a fix for this?

I had the same issue and I solved it by adding CUDA_VISIBLE_DEVICE=0,1,2,3 at the beginning of the command line (or in Pycharm in the environment variables).

@DavidHuji following your solution, I tried to test the model; the error still persists. Is there any modifications to be done to the code.

Hi I found the solution. You set the test batch size to 1 the problem is gone. But I am investigating the code logic to see why this should be like this. There are a lot of errors of this code as I found.

Hi I found the solution. You set the test batch size to 1 the problem is gone. But I am investigating the code logic to see why this should be like this. There are a lot of errors of this code as I found.

Have you find the reason?

I solved the problem long time ago with the same solution. But there are still many errors so I finally gave up reproducing their results. Now I am using other code base.

在 2022年8月20日，上午1:23，zhuyibing @.***> 写道：

Hi I found the solution. You set the test batch size to 1 the problem is gone. But I am investigating the code logic to see why this should be like this. There are a lot of errors of this code as I found.
Have you find the reason?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

I solved the problem long time ago with the same solution. But there are still many errors so I finally gave up reproducing their results. Now I am using other code base.
…
在 2022年8月20日，上午1:23，zhuyibing @.***> 写道：  Hi I found the solution. You set the test batch size to 1 the problem is gone. But I am investigating the code logic to see why this should be like this. There are a lot of errors of this code as I found. Have you find the reason? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

what code base ?can you give me a link

https://github.com/KaihuaTang/Scene-Graph-Benchmark.pytorch

在 2022年8月22日，下午8:08，zhuyibing @.***> 写道：

I solved the problem long time ago with the same solution. But there are still many errors so I finally gave up reproducing their results. Now I am using other code base.
…
在 2022年8月20日，上午1:23，zhuyibing @.***> 写道：  Hi I found the solution. You set the test batch size to 1 the problem is gone. But I am investigating the code logic to see why this should be like this. There are a lot of errors of this code as I found. Have you find the reason? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
what code base ?can you give me a link
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.


How to set default date/time

Hi,
Is is possible to set default date / time while show the picker ?

Hi @ppyoosuf why did you close this? I don't find how to set the default value too...!
Someone has an idea?

You can set the staartingDate field of the picker
eg .pickDate({
title: "Select Date",
theme: "light",
startingDate: defaultDate, //new Date()
maxDate: new Date()
})


Update chocolatey things

Updated the README with the following changes:

The cinst command is being deprecated in the next version of Chocolatey CLI. Replaced it with the correct command.
Added a link to the carnac package page on the Chocolatey Community Repository.

@shiftkey I came here to make the same suggestion that is included in this PR.  I know that there hasn't been any releases to Carnac for a while, but just yesterday we had folks asking about it on our Chocolatey Discord Server, so it is still being used.
With the cinst command being deprecated, I think getting this updated on the README is an important change.  Thanks!


Logo/Icon Proposal

Hi good day! Im Jibbie Eguna, a graphics designer, I would like to ask for your permission to propose a new designs of logo in your application/project. I would like to help projects in open-source .I would just like to propose new designs if you are needing it. Hoping for your positive response Thank You!

Do you have a portfolio of work that you can show? Previous icon designs you have done?

For what it's worth, I'm a big fan of the current icon scheme.

Thank you very much for for your generous offer but I think I'll stick with the current application/document icon scheme for now.

I came straight back here after seeing the new icon.
What happened!?

Yeah... whoa. I stand by my previous enthusiasm for the “classic” icon.

I see in changes.txt

For 5.3

First facelift in a decade: New application icons created by Drífa Líftóra

Well, she has great personal style, but I'm not sure she's going to give Susan Kare a run for her money

Echoing the above, the issue became obvious to me when it took quite a few seconds for me to figure out what the new icon was - a platypus. And this is knowing the application is called Platypus.

Well it does look a bit like a spermazoidal banana. But you know, design is hard work, and someone did put their hard work into it. You can't please everybody all the time.. or in my case, really just about anyone, for more than a few weeks.
Maybe just a few tweaks to make them read better?

The banner headline here should be that 5.3 is out.. early, a very welcome development. THANK YOU Sveinbjorn!

Hey guys, I'm flattered that you take such a keen interest in the new icon for this old piece of software!
The decision to change the icons and stop using Jon Hooper's Hexley (the Darwin mascot) was not made lightly. The icons looked increasingly dated after the aesthetic changes in recent versions of macOS, where skeumorphism, depth and strong shadows are out of place. A young designer I know personally offered to make a new one for me, more in keeping with the direction Mac applications are going. I'm quite happy with the outcome and I'm sorry to hear not everyone feels the same.
For my part, I think they look considerably better than the old ones at smaller sizes and in Mojave's Dark Mode (see attached screenshots). I also think Hexley never looked like much of a platypus in the first place -- more like Donald Duck. Never the less, I'll send your comments to the designer and hear what she thinks.
That being said, people can use any icon they want for their Platypus-generated apps. I may even add a "Default Icon" option to the Preferences for the next versions. I even contemplated keeping the old default icon as an option.

Hi Sveinbjorn, thanks for the summary. I think we totally understand the direction, and actually i agree that it was overdue. However, the issue for me is the execution. I look forward to hearing what the designer says about this feedback.


repeat issue in calendar heatmap

https://github.com/apache/superset/issues/22408#issue-1494151128

Closing in favor of https://github.com/apache/superset/issues/23018 which is still open.


Don't request empty groups from the server

They aren't shown in the joinGroup dialog anyways, so why request them?

Current coverage is 98.51% (diff: 100%)

Merging #196 into master will not change coverage

@@             master       #196   diff @@
==========================================
  Files           100        100
  Lines          1479       1479
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1457       1457
  Misses           22         22
  Partials          0          0

Powered by Codecov. Last update bdcf458...08d4ceb


Question about sync when sensor API is used

Required Info

Camera Model
D400

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10

Kernel Version (Linux Only)

Platform
PC

SDK Version
2.50.10

Language

Segment

Hi, I have a question about sync.cpp. I've been looking into it a bit, and I've noticed something strange when using sensor API instead of pipeline API. So, when using sensor API, when the first frame arrives, the following is done:

In line 197, we use "dev->create_matcher(frame)" to create all matchers we need (which in the end goes to the composite_matcher constructor. What I'm interested in is the callback that's set to the matcher. From what I can gather, this callback is called when the matchers previously created with "create_matcher()" manage to sync frames. So, when frames are synced, the callback set here should be called, and it's currently set so that it, again, calls sync with the fameset that was already synced.
What I believe the callback should be is following:

This has been taken from "syncer-processing-block.cpp" and this is the callback that's set when pipeline API is used. It basically moves the composite frame into queue which is then used for whatever is next (in the end being outputed when "wait_for_frames()" is called.
The only reason this is currently working is because when sync is used the frame is outputed if there are no missing streams which will happen sooner or later. Can I please get some information if this is deliberate, and if so, what the reasoning behind it was.
Thank you

Hi @Marenix  I will discuss your question with my Intel RealSense colleagues.  Thanks very much for your patience!

Hi @Marenix  My colleagues researched your question and determined that the behavior is by design, as described by a RealSense team member at https://github.com/IntelRealSense/librealsense/issues/5675#issuecomment-576018859
The syncer will only output a frameset only when the matched frames are found.  The pipeline will output a frameset when one of the streams is not available.

Hi @MartyG-RealSense, thank you for the answer. In the next few days I'll do a few tests based on your answer and then get back to you to close the issue if everything works as expected.

You are very welcome.  I look forward to your next update.  Good luck with your tests!

Hi @Marenix  Do you have an update about this case that you can provide, please?  Thanks!

That's no problem at all.  Good luck with your work and thanks again for the update!

Hi @MartyG-RealSense, sorry it took me so long to get back to this. I've ran some tests with both the original callback and with the changed one (both which I mentioned in the first post). I haven't noticed any change when I changed the callback.
Just for clarification, while using syncer, I should never receive 2 framesets which have one of the frames identical in both framesets, right? Well, I encountered that case (where I have 2 framesets in which I have the same depth or color frame while the other is different) while using both the original callback and the one I suggested. If this shouldn't happen, is there any simple example with which I could check if there might be some problem in my application?
Thank you

A RealSense team member advises at https://github.com/IntelRealSense/librealsense/issues/5107#issuecomment-546870736 that use of poll_for_frames() avoids duplicate frames.

Hi @MartyG-RealSense, after some additional tests, I found an issue in my example. I have since fixed the issue and now I do not see duplicated frames with wait_for_frames() (haven't tried poll_for_frames() after fixing the problem).
Going back to my original post, I now tried the example with both version of the callback I mentioned there, and I do not see any difference in my example. Neither version gives a duplicate of the previous frame if the new one is missing. So, looking back to your original answer, I cannot see the syncer giving unmatched frames with either callback. Could there be some other reason for choosing one callback over the other?

My honest answer to your question of whether there could be some other reason for choosing one callback over the other is that I do not know.  I do apologize.

Hi @Marenix  Bearing in mind the comment above, do you require further assistance with this case please?  Thanks!

Hi @MartyG-RealSense Thanks for the clarifications you have given me. Since there is nothing further that can be said on the topic, I think it can be closed

You are very welcome.  As you suggest, I will close the issue.  Thanks again!


cleaned up init data script and setup sites

Changes

Updated initial data script to match current environment
merged setup_sites script

Testing

drop database and run ./create-mysql-db.sh && ./cfgov/manage.py migrate && ./cfgov/manage.py runscript initial_data

run setup script and verify sites host name is whatever you have entered in the args e.g:

./cfgov/manage.py runscript setup_sites --script-args='test'

Review

@kurtw
@richaagarwal
@rosskarchner

:+1:


调试开发,很麻烦, 有没有好的测试方法,每次都要扫码登录,烦琐的工作!

记得puppeteer有一个接口,puppeteer.connect(options), 可以连接到现有的puppeteer上,
wechaty有暴露出puppeteer.connect(options)接口吗,   这样我们就可以开一个puppeteer服务,
wechaty测试开发时连接 puppeteer服务,更好的调试逻辑代码,避免每次都要扫码登录,烦琐调试工作!
小白一个知识面小, 如有其它好调试的方法, 希望能告知一二,谢谢

You can save your profile when creating the Wechaty instance so that you can save your session between restarts.

you can implement a mock puppeteer just like wechaty-puppet-mock ,  sending mock qr code, contacts profiles, group profiles after puppeteer started, and then make appropriate reponses to the wechaty command.

@iyjian That's correct.
I'll treat this is an advance unit testing method for your project, and if anyone is interested in using a  wechaty-puppet-mock to do unit testing, please let me know!

You can save your profile when creating the Wechaty instance so that you can save your session between restarts.

如何保存一个实例, 在文档中没有找到对应的api

@tangjoin You can specify the name options in the WechatyOptions


ENH: Support k!=0 for sparse.diagonal()

My editor also removed a lot of trailing white space, so the relevant diff is much smaller than the stats for csr.h and csc.h tell.
It still needs tests for the new functionality, but I need to figure out the sparse testing framework beforing tackling that.
I'd appreciate a review of the code in its current state, and any pointers on what to test and where to put those tests.

TravisCI is not yet happy. One style issue:
$ pep8 scipy benchmarks/benchmarks
scipy/sparse/compressed.py:524:40: E225 missing whitespace around operator
1       E225 missing whitespace around operator

and just restarted the job that timed out

any pointers on what to test and where to put those tests.

I think adding to _TestCommon.test_diagonal in test_base.py.
Testing valid and invalid values of ints (int32 and int64 maybe), for various shapes matrices, plus invalid inputs (floats, sequences, etc.) would seem reasonable to me.

This turned into much more work than I was expecting, but arbitrary diagonals now work for all formats, including COO, DIA and BSR. Especially BSR was much more thinking than I was hoping to do on a Sunday afternoon...
Not sure how self explanatory the BSR code is, am willing to comment it in detail if needed. But not only does it handle arbitrary k, it is also more efficient for the general case. So much so that I have removed the special path that used to be there for the case R == C.
There are also a lot of formatting changes that happened when my editor converted all tabs to spaces in bsr.h, have gone ahead and fixed the indentation throughout as well.
Anyway, I think this is mostly ready now.

Have added some comments to the BSR code and removed the extra docstrings.

Docstring added before heading to bed, more tomorrow.
Not sure about how to specify a 'See also' entry referring to numpy, comments welcome.
Also, is this worthy of including in the release notes?

Also, is this worthy of including in the release notes?

Borderline, but I'd say yes. And easier to put all enhancements into the release notes with the PRs and later edit down than having to hunt for things to put in the release notes at the last moment.

Not sure about how to specify a 'See also' entry referring to numpy, comments welcome.

This will do it:
See Also
--------
numpy.funcname

The magic of intersphinx:)

Have added a mention in in the release notes.
I think this is ready for a final review.

Merged. The TravisCI failure was a timeout during coverage analysis, after having passed the test suite.
Thanks @jaimefrio !


README improvements - minimal success path

Opening as a follow-up issue for #9, I want to close out #9 quicker, but I think this item would take more time, so creating a 2nd issue to track it.

Validate that there's a minimum clear and base success path

Looking at the New/Existing instructions in AWS and Azure, I'd like to be able to launch something minimally.   The instructions says:

cd ibm-spectrum-scale-cloud-install/aws_scale_templates/aws_new_vpc_scale/
Create aws_new_vpc_scale_inputs.auto.tfvars.json
terraform init/apply...

So that means the customer is sitting in this repo and HAS to create some custom files.. How does terraform pick it, does it just pick up the various json files in the path?
If we take that example aws_new_vpc_scale_inputs.auto.tfvars.json in the README, as is, could a user launch something into AWS, or would it fail... invalid operator_email?
If it works, couldn't we ship that example, so if the user wanted to change nothing but had all their credentials already configured, they could just do something like:
git clone <repo>
cd <some path>
terraform init
terraform apply --auto-approve

Thanks README has been improved.