[Bug] There's nothing displayed on the UI

What did I do
I used it without any issues for the past two days, but yesterday I found that after opening MQTTX (ver: 1.9.3) software, nothing was displayed.
Environment

OS: OS version, e.g. Microsoft Windows 11 Chinese Edition 64bit 10.0.22621
BuildNumber Caption OSArchitecture Version 22621
MQTTX version, 1.9.3

More detail
no logs

Duplicate of #968
Hi, thanks for your feedback. There could be many reasons you're experiencing this issue, and it could be related to the software itself, its compatibility with your OS, or other factors. Here's what you can try to solve the problem:

Always Run MQTTX as an Administrator: Right-click the MQTTX icon, select Properties, then in the Compatibility tab, check "Run this program as an administrator". Click OK to save the settings.
Check File Permissions for MQTTX: Check the permissions of relevant files in the installation directory of MQTTX. Ensure your user account has sufficient permissions to access and modify these files.
Review your Security Software: Sometimes, antivirus software or firewalls might block certain applications from correctly accessing files or networks. Check your security settings to ensure MQTTX is not being blocked.
Delete and Recreate MQTTX Database File: Delete the %USERPROFILE%\AppData\Roaming\MQTTX\MQTTX.db file and restart MQTTX. This will force MQTTX to recreate the .db file which might resolve the issue.
Reinstall MQTTX: A simple reinstall might fix potential corruption or file missing issues. Uninstall the application completely, and then download the latest version from the official website. Install it again to see if the problem persists.


3 red stripes after opening the app/browser

Describe the bug
When I open my browser or app for the first time (every time), it shows the cards I've setup with the Garbage-Collection as 3 red stripes.
After when i'm opening the menu and switch between boards or when I open and close the configure-UI, the pictures will appear.
I'm using the custom card-templater
Configuration
YAML or Config Flow (GUI):
This is my configuration: https://pastebin.com/XCV5tQjn

Error log/debug information
I can't find any logging

To enable debug logging, add custom_components.garbage_collection: debug to your config under logger/logs.
Screenshots
Here u can see the screenshots: https://imgur.com/a/4EJ9Nos
Version
I'm running Home Assistant 0.108.3

Is this a bug in the garbage collection integration? Can you try simple entity card? Will that be red as well?
Or is this an issue with Lovelace config? In that case, it is hard to troubleshoot from here. What I'd do is, I'd start simple - take 1 card, no card-templater. See if that works. And then start adding the complexity back, until you figure out what is causing it.


⚠ Nebulance has degraded performance

In 49d3b4a, Nebulance ($NBL) experienced degraded performance:

HTTP code: 200
Response time: 1420 ms

Resolved: Nebulance performance has improved in 8442c22.


Fix race condition on OffsetManager shutdown

If updateCommitted ran between the Unlock call and the read from clean
then we might miss the transition message and hang. Instead, use a condition
value from the sync package which does the right thing.
@wvanbergen @hasnickl fixes #656
Supersedes #657

lgtm


Bump all rust deps

Looks like there has been some API changes in generated code etc from flatbuffers 0.6 to 0.8.2 that requires more work to upgrade.

Looks like there has been some API changes in generated code etc from flatbuffers 0.6 to 0.8.2 that requires more work to upgrade.

 Made a therefore a separate PR #105.
flatc 1.12 has no substancial improvements and the corresponding Rust flatbuffers 0.6.2 is obviously unpublished.

 Made a therefore a separate PR #105.
flatc 1.12 has no substancial improvements and the corresponding Rust flatbuffers 0.6.2 is obviously unpublished.

Apache Arrow updated to Rust flatbuffers 0.8.1 yesterday: https://github.com/apache/arrow/commit/7ee016652b

Apache Arrow updated to Rust flatbuffers 0.8.1 yesterday: https://github.com/apache/arrow/commit/7ee016652b


Consider reporting total run time with turbiniactl status

I imagine each task can report their own run time and the command could display the sum of all of those. This could be interesting even if that sum is different than the time it took to process everything because we're running multiple workers

Have you looked at turbiniactl status --statistics?  I'm not sure if it has exactly what you're looking for, but it would be fairly easy to adapt if not.   You can use the normal flags for the status command  (e.g. -r <request id>, -d <days>, -u <user>, and -t <task>) to filter on just the jobs/tasks you're interested in.

@rgayon :  I'm going to close this for now as I think that the --statistics flag can be used here, but feel free to re-open if your use-case doesn't match.


"Greeter recerived : RPC failed" in cpp example

When i try to run cpp hello world example, a error have been happenning.
"Greeter received: RPC failed"  What can i do to resolve this problem?
$ ./greeter_server
D0610 13:46:17.375313774   31124 env_linux.c:77]             Warning: insecure environment read function 'getenv' used
D0610 13:46:17.375486286   31124 env_linux.c:77]             Warning: insecure environment read function 'getenv' used
D0610 13:46:17.375512302   31124 ev_posix.c:101]             Using polling engine: poll
D0610 13:46:17.375542479   31124 env_linux.c:77]             Warning: insecure environment read function 'getenv' used
Server listening on <IP_ADDRESS>:50051
E0610 13:46:27.531291219   31128 compression.c:157]          Unknown compression level 32759.
$./greeter_client
D0610 13:46:27.529877420   31136 env_linux.c:77]             Warning: insecure environment read function 'getenv' used
D0610 13:46:27.530095493   31136 env_linux.c:77]             Warning: insecure environment read function 'getenv' used
D0610 13:46:27.530131618   31136 ev_posix.c:101]             Using polling engine: poll
D0610 13:46:27.530186037   31136 env_linux.c:77]             Warning: insecure environment read function 'getenv' used
Greeter received: RPC failed

You can enable grpc tracing with
export GRPC_TRACE=all && ./greeter_server and same thing for the client.

I'm seeing the same "unknown compression level" error with our Haskell gRPC library (which uses the C core), on OS X with 0.15.0, when running a simple unary request/response test. Note this happens regardless of whether I set a compression level explicitly when starting the server. This didn't happen with 0.14.0, and is blocking us from upgrading to 0.15.0.
Server trace:
0728 13:21:11.355667000<PHONE_NUMBER>24640 ev_posix.c:101] Using polling engine: poll
I0728 13:21:11.357069000<PHONE_NUMBER>24640 init.c:188] grpc_init(void)
I0728 13:21:11.357762000<PHONE_NUMBER>24640 server.c:984] grpc_server_create(0x7fb575000310, 0x0)
I0728 13:21:11.358661000<PHONE_NUMBER>24640 server_chttp2.c:92] grpc_server_add_insecure_http2_port(server=0x7fb573c05a90, addr=localhost:50051)
I0728 13:21:11.359685000<PHONE_NUMBER>24640 completion_queue.c:129] grpc_completion_queue_create(reserved=0x0)
I0728 13:21:11.359698000<PHONE_NUMBER>24640 server.c:968] grpc_server_register_completion_queue(server=0x7fb573c05a90, cq=0x7fb575101420, reserved=0x0)
I0728 13:21:11.359704000<PHONE_NUMBER>24640 server.c:1064] grpc_server_start(server=0x7fb573c05a90)
I0728 13:21:11.359857000<PHONE_NUMBER>24640 completion_queue.c:129] grpc_completion_queue_create(reserved=0x0)
I0728 13:21:11.360085000<PHONE_NUMBER>24640 metadata_array.c:42] grpc_metadata_array_init(array=0x7fb573c06210)
I0728 13:21:11.360102000<PHONE_NUMBER>24640 call_details.c:42] grpc_call_details_init(cd=0x7fb573c05780)
I0728 13:21:11.360113000<PHONE_NUMBER>24640 server.c:1371] grpc_server_request_call(server=0x7fb573c05a90, call=0x7fb575100dd0, details=0x7fb573c05780, initial_metadata=0x7fb573c06210, cq_bound_to_call=0x7fb5751015b0, cq_for_notification=0x7fb575101420, tag=0x8000000000000000)
I0728 13:21:11.360275000<PHONE_NUMBER>24640 completion_queue.c:434] grpc_completion_queue_pluck(cc=0x7fb575101420, tag=0x8000000000000000, deadline=gpr_timespec { tv_sec:<PHONE_NUMBER>854775807, tv_nsec: 0, clock_type: 0 }, reserved=0x0)
D0728 13:21:30.539424000<PHONE_NUMBER>24640 tcp_server_posix.c:367] SERVER_CONNECT: incoming connection: ipv6:[::1]:50868
D0728 13:21:30.539774000<PHONE_NUMBER>24640 connectivity_state.c:109] CONWATCH: 0x7fb5740b4d48 server_transport: from IDLE [cur=READY] notify=0x7fb573c06aa8
D0728 13:21:30.539799000<PHONE_NUMBER>24640 connectivity_state.c:109] CONWATCH: 0x7fb5740b4d48 server_transport: from READY [cur=READY] notify=0x7fb573c06aa8
D0728 13:21:30.539821000<PHONE_NUMBER>24640 parsing.c:168] FLOW parsed: server transport CREDIT       global.announce_incoming_window(0) by                   announce_bytes(983041) giving 983041
D0728 13:21:30.539830000<PHONE_NUMBER>24640 parsing.c:170] FLOW parsed: server transport CREDIT           parsing.incoming_window(65535) by                   announce_bytes(983041) giving 1048576
D0728 13:21:30.539840000<PHONE_NUMBER>24640 writing.c:163] FLOW write: server transport DEBIT   global.announce_incoming_window(983041) by                        announced(983041) giving 0
D0728 13:21:30.539877000<PHONE_NUMBER>24640 frame_settings.c:250] CHTTP2:SVR: got setting 2 = 0
D0728 13:21:30.539883000<PHONE_NUMBER>24640 frame_settings.c:250] CHTTP2:SVR: got setting 3 = 0
D0728 13:21:30.539886000<PHONE_NUMBER>24640 frame_settings.c:250] CHTTP2:SVR: got setting 4 = 65535
D0728 13:21:30.539889000<PHONE_NUMBER>24640 frame_settings.c:250] CHTTP2:SVR: got setting 6 = 16384
D0728 13:21:30.539894000<PHONE_NUMBER>24640 frame_window_update.c:122] FLOW parse: server transport CREDIT               parsing.outgoing_window(0) by                  received_update(983041) giving 983041
I0728 13:21:30.539908000<PHONE_NUMBER>24640 call.c:1353] ops[0]: RECV_INITIAL_METADATA ptr=0x7fb5740b76f0
I0728 13:21:30.539915000<PHONE_NUMBER>24640 server.c:780] OP[server:0x7fb5740b7608]: RECV_INITIAL_METADATA
I0728 13:21:30.539919000<PHONE_NUMBER>24640 http_server_filter.c:219] OP[http-server:0x7fb5740b7620]: RECV_INITIAL_METADATA
I0728 13:21:30.539923000<PHONE_NUMBER>24640 connected_channel.c:70] OP[connected:0x7fb5740b7650]: RECV_INITIAL_METADATA
I0728 13:21:30.539931000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: :scheme: http
I0728 13:21:30.539938000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: :method: POST
I0728 13:21:30.539946000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: :path: /echo.Echo/DoEcho
I0728 13:21:30.539953000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: :authority: localhost:50051
I0728 13:21:30.539959000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: grpc-encoding: identity
I0728 13:21:30.539966000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: grpc-accept-encoding: identity,deflate,gzip
I0728 13:21:30.539977000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: te: trailers
I0728 13:21:30.539981000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: content-type: application/grpc
I0728 13:21:30.539987000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: user-agent: grpc-c/0.15.0 (osx; chttp2)
I0728 13:21:30.539995000<PHONE_NUMBER>24640 parsing.c:655] HTTP:1:HDR:SVR: grpc-timeout: 5S
D0728 13:21:30.540008000<PHONE_NUMBER>24640 parsing.c:592] FLOW parse: server transport DEBIT          parsing.incoming_window(1048576) by                   incoming_frame_size(9) giving 1048567
D0728 13:21:30.540015000<PHONE_NUMBER>24640 parsing.c:594] FLOW parse: server stream[1] DEBIT            parsing.incoming_window(65535) by                   incoming_frame_size(9) giving 65526
I0728 13:21:30.540029000<PHONE_NUMBER>24640 call.c:1353] ops[0]: RECV_INITIAL_METADATA ptr=0x7fb5740b86f0
I0728 13:21:30.540033000<PHONE_NUMBER>24640 server.c:780] OP[server:0x7fb5740b8608]: RECV_INITIAL_METADATA
I0728 13:21:30.540037000<PHONE_NUMBER>24640 http_server_filter.c:219] OP[http-server:0x7fb5740b8620]: RECV_INITIAL_METADATA
I0728 13:21:30.540040000<PHONE_NUMBER>24640 connected_channel.c:70] OP[connected:0x7fb5740b8650]: RECV_INITIAL_METADATA
I0728 13:21:30.540046000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: :scheme: http
I0728 13:21:30.540049000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: :method: POST
I0728 13:21:30.540052000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: :path: /echo.Echo/DoEcho
I0728 13:21:30.540055000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: :authority: localhost:50051
I0728 13:21:30.540058000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: grpc-encoding: identity
I0728 13:21:30.540061000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: grpc-accept-encoding: identity,deflate,gzip
I0728 13:21:30.540064000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: te: trailers
I0728 13:21:30.540067000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: content-type: application/grpc
I0728 13:21:30.540070000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: user-agent: grpc-c/0.15.0 (osx; chttp2)
I0728 13:21:30.540074000<PHONE_NUMBER>24640 parsing.c:655] HTTP:3:HDR:SVR: grpc-timeout: 5S
D0728 13:21:30.540079000<PHONE_NUMBER>24640 parsing.c:592] FLOW parse: server transport DEBIT          parsing.incoming_window(1048567) by                   incoming_frame_size(9) giving 1048558
D0728 13:21:30.540084000<PHONE_NUMBER>24640 parsing.c:594] FLOW parse: server stream[3] DEBIT            parsing.incoming_window(65535) by                   incoming_frame_size(9) giving 65526
I0728 13:21:30.540095000<PHONE_NUMBER>24640 call.c:1353] ops[0]: RECV_INITIAL_METADATA ptr=0x7fb5740b96f0
I0728 13:21:30.540099000<PHONE_NUMBER>24640 server.c:780] OP[server:0x7fb5740b9608]: RECV_INITIAL_METADATA
I0728 13:21:30.540102000<PHONE_NUMBER>24640 http_server_filter.c:219] OP[http-server:0x7fb5740b9620]: RECV_INITIAL_METADATA
I0728 13:21:30.540106000<PHONE_NUMBER>24640 connected_channel.c:70] OP[connected:0x7fb5740b9650]: RECV_INITIAL_METADATA
I0728 13:21:30.540111000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: :scheme: http
I0728 13:21:30.540114000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: :method: POST
I0728 13:21:30.540117000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: :path: /echo.Echo/DoEcho
I0728 13:21:30.540120000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: :authority: localhost:50051
I0728 13:21:30.540123000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: grpc-encoding: identity
I0728 13:21:30.540126000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: grpc-accept-encoding: identity,deflate,gzip
I0728 13:21:30.540129000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: te: trailers
I0728 13:21:30.540132000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: content-type: application/grpc
I0728 13:21:30.540135000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: user-agent: grpc-c/0.15.0 (osx; chttp2)
I0728 13:21:30.540138000<PHONE_NUMBER>24640 parsing.c:655] HTTP:5:HDR:SVR: grpc-timeout: 5S
D0728 13:21:30.540143000<PHONE_NUMBER>24640 parsing.c:592] FLOW parse: server transport DEBIT          parsing.incoming_window(1048558) by                   incoming_frame_size(9) giving 1048549
D0728 13:21:30.540152000<PHONE_NUMBER>24640 parsing.c:594] FLOW parse: server stream[5] DEBIT            parsing.incoming_window(65535) by                   incoming_frame_size(9) giving 65526
I0728 13:21:30.540164000<PHONE_NUMBER>24640 call.c:1353] ops[0]: RECV_INITIAL_METADATA ptr=0x7fb5740ba6f0
I0728 13:21:30.540168000<PHONE_NUMBER>24640 server.c:780] OP[server:0x7fb5740ba608]: RECV_INITIAL_METADATA
I0728 13:21:30.540171000<PHONE_NUMBER>24640 http_server_filter.c:219] OP[http-server:0x7fb5740ba620]: RECV_INITIAL_METADATA
I0728 13:21:30.540174000<PHONE_NUMBER>24640 connected_channel.c:70] OP[connected:0x7fb5740ba650]: RECV_INITIAL_METADATA
I0728 13:21:30.540179000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: :scheme: http
I0728 13:21:30.540183000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: :method: POST
I0728 13:21:30.540186000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: :path: /echo.Echo/DoEcho
I0728 13:21:30.540189000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: :authority: localhost:50051
I0728 13:21:30.540192000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: grpc-encoding: identity
I0728 13:21:30.540195000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: grpc-accept-encoding: identity,deflate,gzip
I0728 13:21:30.540198000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: te: trailers
I0728 13:21:30.540201000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: content-type: application/grpc
I0728 13:21:30.540204000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: user-agent: grpc-c/0.15.0 (osx; chttp2)
I0728 13:21:30.540207000<PHONE_NUMBER>24640 parsing.c:655] HTTP:7:HDR:SVR: grpc-timeout: 5S
D0728 13:21:30.540211000<PHONE_NUMBER>24640 parsing.c:592] FLOW parse: server transport DEBIT          parsing.incoming_window(1048549) by                   incoming_frame_size(9) giving 1048540
D0728 13:21:30.540216000<PHONE_NUMBER>24640 parsing.c:594] FLOW parse: server stream[7] DEBIT            parsing.incoming_window(65535) by                   incoming_frame_size(9) giving 65526
D0728 13:21:30.540225000<PHONE_NUMBER>24640 parsing.c:154] FLOW parsed: server transport MOVE                  global.outgoing_window(0) <-          parsing.outgoing_window(983041) giving 983041
D0728 13:21:30.540241000<PHONE_NUMBER>24640 writing.c:77] FLOW write: server transport MOVE             writing.outgoing_window(65535) <-           global.outgoing_window(983041) giving 1048576
D0728 13:21:30.540272000<PHONE_NUMBER>24640 frame_window_update.c:116] FLOW parse: server stream[5] CREDIT               parsing.outgoing_window(0) by                   received_update(65535) giving 65535
D0728 13:21:30.540280000<PHONE_NUMBER>24640 frame_window_update.c:116] FLOW parse: server stream[3] CREDIT               parsing.outgoing_window(0) by                   received_update(65535) giving 65535
D0728 13:21:30.540285000<PHONE_NUMBER>24640 frame_window_update.c:116] FLOW parse: server stream[7] CREDIT               parsing.outgoing_window(0) by                   received_update(65535) giving 65535
D0728 13:21:30.540290000<PHONE_NUMBER>24640 frame_window_update.c:116] FLOW parse: server stream[1] CREDIT               parsing.outgoing_window(0) by                   received_update(65535) giving 65535
D0728 13:21:30.540298000<PHONE_NUMBER>24640 parsing.c:190] FLOW parsed: server stream[5] MOVE              global.outgoing_window(65535) <-           parsing.outgoing_window(65535) giving 131070
D0728 13:21:30.540304000<PHONE_NUMBER>24640 parsing.c:190] FLOW parsed: server stream[3] MOVE              global.outgoing_window(65535) <-           parsing.outgoing_window(65535) giving 131070
D0728 13:21:30.540309000<PHONE_NUMBER>24640 parsing.c:190] FLOW parsed: server stream[7] MOVE              global.outgoing_window(65535) <-           parsing.outgoing_window(65535) giving 131070
D0728 13:21:30.540315000<PHONE_NUMBER>24640 parsing.c:190] FLOW parsed: server stream[1] MOVE              global.outgoing_window(65535) <-           parsing.outgoing_window(65535) giving 131070
I0728 13:21:30.540330000<PHONE_NUMBER>24640 completion_queue.c:242] grpc_cq_end_op(exec_ctx=0x7fff53f3c480, cc=0x7fb575101420, tag=0x8000000000000000, error=null, done=0x10c63df23, done_arg=0x10d43ff98, storage=0x10d43ffc0)
E0728 13:21:30.540334000<PHONE_NUMBER>24640 completion_queue.c:244] Operation failed: tag=0x8000000000000000, error=null
I0728 13:21:30.540341000<PHONE_NUMBER>24640 completion_queue.c:513] RETURN_EVENT[0x7fb575101420]: OP_COMPLETE: tag:0x8000000000000000 OK
I0728 13:21:30.540701000<PHONE_NUMBER>24640 call_details.c:47] grpc_call_details_destroy(cd=0x7fb573c05780)
I0728 13:21:30.540710000<PHONE_NUMBER>24640 metadata_array.c:47] grpc_metadata_array_destroy(array=0x7fb573c06210)
I0728 13:21:30.540827000<PHONE_NUMBER>24640 call.c:1677] grpc_call_start_batch(call=0x7fb5740b7000, ops=0x7fb573c06fa0, nops=2, tag=0x8000000000000000, reserved=0x0)
I0728 13:21:30.540834000<PHONE_NUMBER>24640 call.c:1353] ops[0]: SEND_INITIAL_METADATA
I0728 13:21:30.540838000<PHONE_NUMBER>24640 call.c:1353] ops[1]: RECV_MESSAGE ptr=0x7fb573c06280
I0728 13:21:30.540842000<PHONE_NUMBER>24640 compression.c:155] grpc_compression_algorithm_for_level(level=1413827664)
E0728 13:21:30.540845000<PHONE_NUMBER>24640 compression.c:157] Unknown compression level<PHONE_NUMBER>.

Client trace:
D0728 13:21:30.534631000<PHONE_NUMBER>24640 ev_posix.c:101] Using polling engine: poll
E0728 13:21:31.123614000<PHONE_NUMBER>31904 chttp2_transport.c:1810] close_transport: {"created":"@1469737291.123526000","description":"Failed parsing HTTP/2","file":"src/core/ext/transport/chttp2/transport/chttp2_transport.c","file_line":1726,"referenced_errors":[{"created":"@1469737291.123515000","description":"EOF","file":"src/core/lib/iomgr/tcp_posix.c","file_line":233}]}

The error on the client side makes it look like this might be the same underlying issue as https://github.com/grpc/grpc/issues/7278.

@crclark , thanks. I'm having a look today. I seem to recall that this has been fixed on the pre-1.0.0. Would you mind testing against the "v1.0.x" branch?

Sure, I'll try to test against that branch and get back to you.

@dgquintas This still happens on branch v1.0.x. For some reason, though, GRPC_TRACE isn't working for me on that branch. Also, the client fails differently. I get an unavailable status code and the status details are:
{"created":"@1469740136.839567000","description":"EOF","file":"src/core/lib/iomgr/tcp_posix.c","file_line":235,"grpc_status":14}

@crclark yes, and I know why: at https://github.com/grpc/grpc/blob/master/src/core/lib/surface/call.c#L1412 , effective_compression_level is not initialized, and the following logic is such that it can remain so when there's no specification of the compression level from the channel or the call.
The fix is simply initializing effective_compression_level to GRPC_COMPRESS_LEVEL_NONE. I'm improving the tests to actually catch this error, on top of creating a PR with the fix in a matter of minutes. But just in case you wanted to quickly fix it.
Thanks for the report. This is "one of those things" and it would have been unfortunate if it'd made it into the 1.0 release :)

OTOH, GRPC_TRACE should be working as usual... I'll get back to you on that one.

@dgquintas Thanks for the quick reply. Unfortunately, I just rebuilt the library (v1.0.x) with the fix you suggested, and I'm still getting the same "unknown compression level" error. Let me know if you want me to try anything else.

@crclark make install as well? Perhaps the binary is picking up the old library file.

@dgquintas I added a printf under the changed line to make sure it's using my changed version. However, I just discovered that if I run the executable with valgrind, I don't get the error, so something strange might be going on. I'll keep digging.

BTW, a new environment variable GRPC_VERBOSITY was added in https://github.com/grpc/grpc/pull/7494 in order to control the amount of logging output. In order to get the former tracing behavior, one would have to do GRPC_VERBOSITY=DEBUG GRPC_TRACE=all ...

Some updates:

My previous comment still stands. The variable should be initialized. However, the problem wasn't there (its usage was always protected by level_set). The problem is actually here. There needs to be a maybe_compression_level_.is_set = false in that default constructor. The reasons are somewhat involved, but they add up to there being a new way to set compression options via initial metadata as opposed to C++ cheating and (over)reaching into the C core.
There has been a pending PR with this and other changes (that fix the aforementioned C++ cheating). That's why all this seemed familiar. I'm merging it to master and backporting it to the v1.0.x branch today. I'd recommend picking up those changes, as it fixes everything The Right Way.

@dgquintas Would the fixes in https://github.com/grpc/grpc/pull/7502 help our library, which is only using the C library? I find it puzzling that this error occurs regardless of whether we set compression level in the grpc_channel_args.

@crclark hmm no, all I've been saying assumed C++. It's very surprising It happens when using only the C layer. Is there any way for me to repro? We run tests under msan for C, which should catch issues like this (which clearly look like an uninitialized variable issue).

@crclark hold on... here's where the issue may be. If you are dealing with the core directly, I assume you are assembling grpc_ops yourself, something like what happens here. If so, you have to always memset your ops to zero. Otherwise, in this particular case, op->data.send_initial_metadata.maybe_compression_level.is_set can have a non-zero value, which would then cause op->data.send_initial_metadata.maybe_compression_level.level to be taken into account while it also contains uninitialized garbage`.

@yookyoung89 could you pull from master (now that #7502 has been merged) and try again? Thanks!

@dgquintas Aha! We had initially modeled our code off those tests, but I hadn't thought to look for changes to the tests in 0.15 when tracking down the problem. That fixed it for me. Sorry if I led you astray!

@crclark no worries! In fact we found the bad form of the initialized variable and it reminded me to merge and backport to v1.0.x the critical C++ fix mentioned (which I'm sure does explain the rest of the similar bug reports).

Marking as fixed.

philips@z420:~/software/grpc/examples/cpp/helloworld$ ./greeter_server
I0328 14:11:34.874821922     458 server_builder.cc:247]      Synchronous server. Num CQs: 1, Min pollers: 1, Max Pollers:<PHONE_NUMBER>, CQ timeout (msec): 1000
Server listening on <IP_ADDRESS>:50051
philips@z420:~/software/grpc/examples/cpp/helloworld$ ./greeter_client
14: Connect Failed
Greeter received: RPC failed
The following is my installation script:
git clone -b $(curl -L http://grpc.io/release) https://github.com/grpc/grpc
git clone https://github.com/grpc/grpc
cd grpc
git submodule update --init
make -j$(nproc)
sudo make -j$(nproc) install

@chakpongchung
metoo, please Team help me !!!
Thank!

Please specify:

what version of gRPC you have installed
what OS you are running on

Also please run with GRPC_VERBOSITY=DEBUG and GRPC_TRACE=all and paste the output

V1.4.3    && ubuntu 14.04

https://github.com/grpc/grpc/issues/9989
unset http_proxy

Yes you can use:
unset http_proxy
unset https_proxy
unset ftp_proxy
unset socks_proxy
But now it seem just work for me in the first several times , then when I use client to call server, it stuck. Not thing is showed and no "ask me failed"
When I use :
ps aux | grep path/to/server or path/toclient
I saw that although I ctrl + z server or client already but They are not dead.
So I have to use :
kill -9
It work. But it is hard working.And I don't know how to get better way.


Add AIT Protocol to Taiko's ecosystem

Title of your project
AIT Protocol
Short (1-2 sentence) description of your project
AIT Protocol is the first’s Web3 data infrastructure focusing on AI data annotations, leverages blockchain technology to deliver a trustless and cross-border labor market being strategically incentivized by crypto economics and having instant cross-nation payment settlements.
Link to your project
https://ait.tech/
Live on Testnet
Yes (default)
If your project is live on one of Taiko's testnets, please provide evidence of that here (eg. links, screenshots).
https://explorer.jolnir.taiko.xyz/address/0x802e73F54D092D2F3f237bC5Dba74fFF7cF89BE5
Upload a quality logo to your project
https://drive.google.com/file/d/1qWzB_BO6b7t3_KGcKWl2ORDqMocu2bjO/view

Good going

On
https://testnet.ait.tech/
I don't see Taiko listed

Also the contract at
https://explorer.jolnir.taiko.xyz/address/0x802e73F54D092D2F3f237bC5Dba74fFF7cF89BE5
is not verified. GitHub link to the deployed contract? Are you able to verify the contract on the explorer?

Hi. This is the internal testnet for OG user on discord. We limited to 200 users only. There is a new public testnet coming out in October that will open the omnichain feature, supporting 5 chains: BNB, OKTC, Zksync, BASE, Taiko and Tomochain.

On 09/25/2023 6:46 PM WIB Marcus Wentz @.***> wrote:
On
https://testnet.ait.tech/
I don't see Taiko listed
[ait] https://user-images.githubusercontent.com/52706599/270330342-8e82a366-d9b0-4295-9780-16bdfc1e0388.png
Also the contract at
https://explorer.jolnir.taiko.xyz/address/0x802e73F54D092D2F3f237bC5Dba74fFF7cF89BE5
is not verified. GitHub link to the deployed contract? Are you able to verify the contract on the explorer?
—
Reply to this email directly, view it on GitHub https://github.com/taikoxyz/taiko-mono/issues/14794#issuecomment-1733504284, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7BNO22EKGG5WDHASG55BWLX4FVIDANCNFSM6AAAAAA5FAMY64.
You are receiving this because you authored the thread.Message ID: @.***>

Hi. We have successfully verified the contract.
https://explorer.jolnir.taiko.xyz/address/0x802e73F54D092D2F3f237bC5Dba74fFF7cF89BE5?tab=contract

Let us know when the public testnet comes out in October.

Hi. This is the internal testnet for OG user on discord. We limited to 200 users only. There is a new public testnet coming out in October that will open the omnichain feature, supporting 5 chains: BNB, OKTC, Zksync, BASE, Taiko and Tomochain.

Let us know when the public testnet comes out in October.

Hi. We have successfully verified the contract. https://explorer.jolnir.taiko.xyz/address/0x802e73F54D092D2F3f237bC5Dba74fFF7cF89BE5?tab=contract

Thank you.

Sure. We will be inviting our partners to co-host a panel on Twitter Space. For the announcement on Taiko's discord, is there anything else needed?
We have announced on our end: https://x.com/AITProtocol/status/1706543806114578446?s=20

On 09/26/2023 9:09 PM WIB Marcus Wentz @.***> wrote:

Hi. This is the internal testnet for OG user on discord. We limited to 200 users only. There is a new public testnet coming out in October that will open the omnichain feature, supporting 5 chains: BNB, OKTC, Zksync, BASE, Taiko and Tomochain.

Let us know when the public testnet comes out in October.

Hi. We have successfully verified the contract. https://explorer.jolnir.taiko.xyz/address/0x802e73F54D092D2F3f237bC5Dba74fFF7cF89BE5?tab=contract

Thank you.
—
Reply to this email directly, view it on GitHub https://github.com/taikoxyz/taiko-mono/issues/14794#issuecomment-1735621098, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7BNO2ZZGT7P3TWP237JOZLX4LO2JANCNFSM6AAAAAA5FAMY64.
You are receiving this because you authored the thread.Message ID: @.***>

Sure. We will be inviting our partners to co-host a panel on Twitter Space. For the announcement on Taiko's discord, is there anything else needed?
We have announced on our end: https://x.com/AITProtocol/status/1706543806114578446?s=20

Hi, can you approve us to list on https://taiko.xyz/ecosystem? https://taiko.xyz/ecosystem Ben @.***) from the Taiko team is waiting for that to draft the announcement. Thank you.

On 09/26/2023 9:09 PM WIB Marcus Wentz @.***> wrote:

Hi. This is the internal testnet for OG user on discord. We limited to 200 users only. There is a new public testnet coming out in October that will open the omnichain feature, supporting 5 chains: BNB, OKTC, Zksync, BASE, Taiko and Tomochain.

Let us know when the public testnet comes out in October.

Hi. We have successfully verified the contract. https://explorer.jolnir.taiko.xyz/address/0x802e73F54D092D2F3f237bC5Dba74fFF7cF89BE5?tab=contract

Thank you.
—
Reply to this email directly, view it on GitHub https://github.com/taikoxyz/taiko-mono/issues/14794#issuecomment-1735621098, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7BNO2ZZGT7P3TWP237JOZLX4LO2JANCNFSM6AAAAAA5FAMY64.
You are receiving this because you authored the thread.Message ID: @.***>

Can you verify these contracts as well and integrate them with your frontend?
AIT Token: 0x802e73F54D092D2F3f237bC5Dba74fFF7cF89BE5
Pool Reward: 0x469828686D8F24ba71093c0696a0C1f58034F439
AITONFT: 0xd686194da724b82E33fCD30152a7A6201dA2aBF9
Claim: 0x3233003f9B241e1CD0f8A922BdF69A1160643EAf
It would be best if there were actual successful integration before announcing anything so as to not confuse the users.


Console

How do I run a command from the console?
For eg. I created a /dailyreward command and then the console will give the player the rewards
I already did it but the console didn't give it, the player who executed the command did
There's no option on the form about the console

There will be an "Execute a command from console" action in the command category.

If not, please run /mineflow permission <your name> 1 from the console

Thank you very much!
Also, can u include it in the description, it'll be helpful so players don't ask anymore tho. Anyways thanku sm

I have a question.
I added a command /hello which has a /sendmessage {player} hi (command from console) and console says player not found? Idk what to do


Resizable / Hide-able Console Palette

I understand the point of TypeScript is to be strict on warnings, but on an 11" MacBook Air the warning palette takes up too much vertical space. There doesn't seem to be a way to collapse, hide, or detach it. I think it would be really nice to be able to detach it to another tab.

That is not our panel. Its linters https://github.com/steelbrain/linter :rose:


emacs-nox for msys2

emacs without x tool kit version for MSYS2

I think naming it emacs instead of emacs-nox would be better.
Also check CI error:
configure: error: You seem to be running X, but no X development libraries
were found.  You should install the relevant development files for X
and for the toolkit you want, such as Gtk+ or Motif.  Also make
sure you have development files for image handling, i.e.
tiff, gif, jpeg, png and xpm.
If you are sure you want Emacs compiled without X window support, pass
  --without-x
to configure.

This package is for MSYS2 environment like vim.

msys2 do not include x tool kit, if we use it with GUI, we must use WIN32 native GUI solution. But we have full emacs for win32 version in mingw.

makepkg --skippgpcheck   in your MSYS

@RickLeaf, the mingw version is named mingw-w64-i686-emacs or mingw-w64-x86_64-emacs in pacman.

@elieux yes, I knew. I have used it for a long time.

Then why not use the name emacs for msys2 emacs?
Anyway, that's just a nitpick. More important is to solve the CI error. I think you just need to add --without-x to the ./configure line.

Ok , I rename it


FRAIHM-1008 Made changes to the api yaml files

The mitigation api yaml file and the changelist have been updated to handle the new /state endpoint

The mitigation api version needs to be bumped by a revision number for this to be accepted. Also the changelist should be modified as well.


Support PDF uploads

imgproxy allows for conversion of PDFs to images, so add support for PDF uploads.

PDF only? What about epubs?

-- https://stacker.news/items/429663
Since I don't see EPUB specifically mentioned in the improxy docs^1, I think if we want to support epubs, we need to convert them to PDF first.


Powertoys crashing when trying to open

Microsoft PowerToys version
0.70.1
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
Settings
Steps to reproduce
Powertoys appears to have some functionality as keyboard shortcuts still work and I can see it running in my system tray, if I try and open the app it will bring up the settings window and immediately crash.  I have tried removing and installing again and attached a bug report zip
PowerToysReport_2023-06-30-16-32-13.zip
✔ Expected Behavior
Powertoys to run without crashing
❌ Actual Behavior
It crashed

Other Software
Nothing else opening or running at time of software crashing

Hi @papalazerous,
Was this a one-time occurrence or it happens often? /needinfo

It has never worked properly on version 0.70.1 and always crashes when I try and open the settings window. although keyboard shortcuts otherwise work indicating that it is running in the background. I have rolled back to V0.43.0 and have it fully functioning as expected in the meantime.

Would you be willing to try the following steps in order to help us figure out what's wrong with Settings app?

If you have VC redistributable installed on your machine, uninstall it and install it again.
Then uninstall PowerToys, make sure that PowerToys in Program Files is completely removed (if it's installed in Program Files)
Install PowerToys again
Check if Settings app works

Thanks in advance /needinfo

also crashing
happened after I toggled the legacy  mouse without boarders optiom on > off

also crashing seems to be a config corruption issue
happened after I toggled the legacy mouse without boarders option on > off uninstall / reinstall does not resolve the issue. deleting the entire config folder resolves the issue

https://github.com/microsoft/PowerToys/issues/27126#issuecomment-1689487485 looks like another problem. Can you open an issue attaching a bug report?

I tried generating a bug report but its not generating any logs / the bug report tool doesn't find them

@UrbanPotato Hi, can you please describe what issue you are having and why do you suspect it to be caused by mouse without borders?

the crashing started as soon as I enabled the use Legacy Mouse Without boarders button checkbox
works fine on my laptop not on my desktop
at this stage I am not sure what the problem is seems like its ok on first run but then buggs out on the next
https://streamable.com/f5b9r8

@UrbanPotato thanks for the video. I've noticed that on 1:11 you've removed your config, then restarted PowerToys without opening settings ("Welcome to PowerToys" window is a different window), and then the config folder appeared, then you've started PowerToys yet again and got a crash without enabling MWB. 🤔
Anyway, please try again creating a bug report - it actually zips your config folder, so if you've removed it earlier that might be the issue. If you want to make sure that the Settings logs are there, they should be located in PowerToys\Settings\Logs.

yea I had no problems untill I enabled the Legacy Option for MWB. now it will run ONCE after a config clear and then crash on subequent attempts Ill try the bug report option but the issue is clicking on ANY part of the tray UI causes the crash 🪦 including the bug report button lol

You can launch PowerToys\Tools\PowerToys.BugReportTool.exe directly, it should generate a bug report on your desktop.

PowerToysReport_2023-08-23-17-51-41.zip
PowerToysReport_2023-08-24-05-11-44.zip
PowerToysReport_2023-08-24-11-35-33.zip
PowerToysReport_2023-08-24-11-42-34.zip
PowerToysReport_2023-08-23-17-50-39.zip
lol I had run  that tool before but al lI got with a con window complaining about missing logs.
but I also don't enable desktop icons lol

Thanks. Your reports indeed do not contain any crash-related info, i.e. all EventViewer-* are empty. Settings logs are also weird. It might be that the application is getting closed instead.
One thing I've noticed is that MWB reports an invalid service path. Please try to remove it manually using services.msc. If that doesn't help, please create a new issue so we can track it.

moved #28140


fix: remove decimals in holders section on treasury page

This PR addresses this jira ticket

Already fixed on https://github.com/RootstockCollective/dao-frontend/pull/308


Failed to delete form submission

Key path element must not be incomplete: [FormStatisticsShard: ]

solutions/common/bizz/forms/__init__.py", line 189, in _delete_submission
shard = FormStatisticsShard.create_key(submission.statistics_shard_id).get()

this is due to a migration that we didn't run

actually nevermind, it still isn't merged yet: https://github.com/our-city-app/oca-backend/pull/1276


Fix Demo Mode and Docker Build

Overview
Karthik QA Automation Test Branch (Not for merging)

Looking forward to hear if this works @karthikmsqa 🤞


Removed White Background Around Email Field

Fixes: #746

YES

Is this issue still open ?
If yes please assign this to me.


infra: Get compute engine slaves to have apport disabled and core_pattern set correctly for our slaves

To allow us to do core dump archiving, we need a pid-specific core pattern and need to prevent apport from taking control over it.
Disabling apport in /etc/default/apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0

We should also get /proc/sys/kernel/core_pattern set to:
$ echo 'core.%p' >  /proc/sys/kernel/core_pattern

I think both of these things can be handled via puppet so it doesn't necessarily need to be in the image.
@whesse Could you follow up with CIT about this?
/cc @mraleph

Filed https://bugs.chromium.org/p/chromium/issues/detail?id=686652

Was fixed.


src: return an object of metadata from oc calls

This change adds a new command line option, --metadata.out which can have three possible values stdout, false or <filename>. When specified as stdout or <filename> the returned JSON from the oc REST calls is written to the specified output location.
Fixes: https://github.com/bucharest-gold/nodeshift/issues/76
connects to #76

Coverage remained the same at 97.91% when pulling b70030d3b4bf34bcd17a4a094a3a5e307890321e on 76-object-of-stuff into d970d5af479dbea0eb74a5a8af527bac22c95627 on master.

connects to #76

Coverage decreased (-0.02%) to 97.892% when pulling e72c5e4bb426f8cad0f1a448935319bf127a2369 on 76-object-of-stuff into d970d5af479dbea0eb74a5a8af527bac22c95627 on master.

@lance i hope you don't mind,  i fixed the build error with e72c5e4

Coverage decreased (-0.02%) to 97.888% when pulling 710913ad14d3718401ae0c9962ae775f8ae1e460 on 76-object-of-stuff into d970d5af479dbea0eb74a5a8af527bac22c95627 on master.


Running on AWS in ECS or Fargate?

Has anyone successfully run this on ECS or Fargate? I'm wondering how I'd go about approaching this with wasabi. Any help is appreciated.
Thank you!

@jgillick I am working on this right now. Did you have any progress?

I managed to get a dedicated docker image working and ready to be deployed.  We use Codeship Pro to do our CI and have yet to get it in there to actually build and push to AWS ECR. So far this is what I have done and got it working:

Built a docker image whose sole responsibility is to bootstrap and build via an  entrypoint script.
entrypoint script would copy all relative build directories over to a docker volume mount including the Dockerfile in the wasabi repo.
Created a docker-compose.yml for the image to be built
Created a bash script to launch the compose file, build the wasabi-main Dockerfile, build cqlsh.docker, build migration.docker

Essentially all I really needed for an ECS deployment is the wasabi-main docker image.

@rwadstein Would you mind to share your docker and docker-compose file?
@jgillick I was thinking of creating a docker file where I install the debian rpms. For mysql I will probably use RDS and a cassandra cluster.

It would be great if you can share it @rwadstein


IsVisible Timeout not adhered

I Open my page with an ad authentication and Made my login playwright is redirected back to the application.
I wanna then verify if the login was successful.
For that I use:
page.waitForSelector("my selector").isVisible();
But that fails.
When i put a thread.sleep(5000) before it is working.
Seems that the timeout for wait for selector or isVisible Not working.

Could you share sample page and exact code snippet that fails to wait for visibility? page.waitForSelector("my selector") wait by default for the element to be visible The fact that thread.sleep(500) means that elements visibility state likely changes a few times before it gets stable, i.e. waitForSelector returns when the element is visible but when isVisible() is called the element is already hidden again.

The snippet is the following:
page.waitForSelector("btn_New_Product").IsVisible();
That gives me every time false back.
Ok is it possible to wait for a stable visible State?
For the page direct I have to communicate with our devs.

Ok is it possible to wait for a stable visible State?

This would be page-specific so there is no generic way, page.waitForSelector will return immediately once all the conditions are met but there is no guarantee that the state won't change right after. The easiest way would likely be to check some condition in the page that would tell you if it's still updating. Just curious, is it a React page?

It is a react page.
What is with the load State?
waitForLoadState(LoadState.DOMCONTENTLOADED) or waitForLoadState(LoadState.NETWORKIDLE)
PS: I wanna say that I love playwright and the idea. I find it better than cypress and really love that. Thank you.

It is a react page.

Yeah, most likely there is race with reconciliation/hydration in React and adding thread.sleep(5000) just ensures that the DOM tree is fully updated by React. There is no generic way to detect it in Playwright at the moment.

What is with the load State?
waitForLoadState(LoadState.DOMCONTENTLOADED) or waitForLoadState(LoadState.NETWORKIDLE)

See this page for a brief overview of the navigation lifecycle, I doubt it will help you in this case since you already wait for the selected element to become visible.

PS: I wanna say that I love playwright and the idea. I find it better than cypress and really love that. Thank you.

:heart:

Ok, I found a "solution / workaround":
Response response = page.waitForResponse("MyAppURL", () -> {});
page.waitForSelector("#btn_New_Product").isVisible()

Closing this issue for now as you have a solution. Please reopen if you need further help. In the future we may provide something generic for React problems like this one.


Adding the moorres voting algorithm in the arrays folder

Related Issue

moore's voting algorithm #47

Proposed Changes

Added the Algorithm

Additional Info

Any additional information or context

Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the documentation.
[ ] 🎀 I have updated the documentation accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

A mentor will review this pull request shortly , please have patience.

Hey @satyam4484  , make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.
For contribution and more guidelines i would recommend you to go through this
tutorial video of the project here, thanks.

could you tell me what to do in readme file of particular folder

also what to do in last three check boxes

could you tell me what to do in readme file of particular folder

Please have a look a contribution guidelines in the main Repository of the project , there it is mentioned .

also what to do in last three check boxes

just ignore them

Please have a look a contribution guidelines in the main Repository of the project , there it is mentioned .
there is nothing about readme files could you tell me where it is

@satyam4484 , here
If you can write properly, then only take up the task of writing readme.

yes i can do that

could help me in that part

No response from the contributor ??

sorry, Lakhan currently I am in hospital due to some health issues, that's why unable to work as per the requirement. I will get discharged next Sunday, till then I will not be able to make a contribution.
Could you wait for the next Sunday else you can assign it someone else will make a new contribution if someone will do these
Thank You

Don't worry , get well soon and this PR won't be assigned to anyone else , you can take your time and do it , I'll be glad to merge it at last , do the required changes when you are free .

@satyam4484
Wishing you a speedy recovery.
We understand that you are in the hospital, but if there is a delay in the future, make sure to let the mentors or admin know before they have to ask you.

i have done the changes suggested by you , but how should I show them to here can you suggest me

LGTM.

Do you want to write the Readme for this algorithm as well?

Actually, i don't know much about writing the readme content.

You need to follow particular guidelines for your README , please follow
these guidelines click here
also you can see how your README should look like see here
for more please go through these here

Practice on this https://dillinger.io/

@Lakhankumawat he has not written readme. Please look into it regarding what needs to be done.

closed


⚠ Cioos National CKAN has degraded performance

In 6d69062, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 23933 ms

Resolved: Cioos National CKAN performance has improved in 9b1b59e after 8 minutes.


[ssh-manager] Support remote command in ssh config

Description
Adding an SSH connection with a remote command does not currently work when saving ssh connections in the ssh config file. This PR fixes that
Screencast
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@scoop could you check this?
@gdebrauwer thanks for your contribution 🔥 Could you also add a CHANGELOG entry?

@pernielsentikaer very close on the mention but not quite my extension 😅

Sorry about that 🙂 You're allowed to check it too 🔥
@scopsy could you check this?


Run without debugging issue

Issue Type: Bug
When I press the run without debugging button the program doesn't show any output on the debug console apart from the location of my file. It calls a stack for a debugging session and the navigation bar for the debuger which has the stop and restart options as well as all the others does not disappear. As far as I am concerned, I believe that the program basically debuggs even though I press "run without debugging", however I cannot understand why and how I can fix this.

Are you expecting output but there is none?
"Run without debugging" is basically debugging without hitting breakpoints. So the debug toolbar is expected (because you can still use the Stop button).


support for HM-Sec- Key

Hi Daniel,
thanks for your work to integrate Homegear.
I've got a HM-Sec-Key device, which is recognized in home-assistant but switch functions produces an error:
16-11-23 17:43:17 homeassistant.core: Error doing job: Task exception was never retrieved Traceback (most recent call last):   File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step     result = coro.throw(exc)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 1050, in _event_to_service_call     yield from service_handler.func(service_call)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/switch/__init__.py", line 92, in async_handle_switch_service     yield from switch.async_turn_off()   File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity.py", line 356, in async_turn_off     None, ft.partial(self.turn_off, **kwargs))   File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup     value = future.result()   File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result     raise self._exception   File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run     result = self.fn(*self.args, **self.kwargs)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/switch/homematic.py", line 59, in turn_off     self._hmdevice.off(self._channel) AttributeError: 'KeyMatic' object has no attribute 'off'
There is no On or Off state for the HM-Sec-Key.
VALUES of channel 1 are the following:
{ "DIRECTION": 3,   "ERROR": 0,   "INHIBIT": false,   "STATE": true,   "STATE_UNCERTAIN": true }
This are the possible values:
{   "DIRECTION": {     "DEFAULT": 0,     "FLAGS": 3,     "ID": "DIRECTION",     "MAX": 3,     "MIN": 0,     "OPERATIONS": 5,     "TAB_ORDER": 0,     "TYPE": "ENUM",     "UNIT": "",     "VALUE_LIST": [       "NONE",       "UP",       "DOWN",       "UNDEFINED"     ]   },   "ERROR": {     "CONTROL": "NONE",     "DEFAULT": 0,     "FLAGS": 9,     "ID": "ERROR",     "MAX": 2,     "MIN": 0,     "OPERATIONS": 5,     "TAB_ORDER": 1,     "TYPE": "ENUM",     "UNIT": "",     "VALUE_LIST": [       "NO_ERROR",       "CLUTCH_FAILURE",       "MOTOR_ABORTED"     ]   },   "INHIBIT": {     "CONTROL": "NONE",     "FLAGS": 1,     "ID": "INHIBIT",     "MAX": true,     "MIN": false,     "OPERATIONS": 7,     "TAB_ORDER": 2,     "TYPE": "BOOL",     "UNIT": ""   },   "INSTALL_TEST": {     "FLAGS": 3,     "ID": "INSTALL_TEST",     "MAX": true,     "MIN": false,     "OPERATIONS": 2,     "TAB_ORDER": 3,     "TYPE": "ACTION",     "UNIT": ""   },   "OPEN": {     "CONTROL": "LOCK.OPEN",     "FLAGS": 1,     "ID": "OPEN",     "MAX": true,     "MIN": false,     "OPERATIONS": 2,     "TAB_ORDER": 4,     "TYPE": "ACTION",     "UNIT": ""   },   "RELOCK_DELAY": {     "CONTROL": "NONE",     "DEFAULT": 111600,     "FLAGS": 1,     "ID": "RELOCK_DELAY",     "MAX": 65535,     "MIN": 0,     "OPERATIONS": 2,     "SPECIAL": [       {         "ID": "NOT_USED",         "VALUE": 111600       }     ],     "TAB_ORDER": 5,     "TYPE": "FLOAT",     "UNIT": "s"   },   "STATE": {     "CONTROL": "LOCK.STATE",     "FLAGS": 1,     "ID": "STATE",     "MAX": true,     "MIN": false,     "OPERATIONS": 7,     "TAB_ORDER": 6,     "TYPE": "BOOL",     "UNIT": ""   },   "STATE_UNCERTAIN": {     "CONTROL": "LOCK.UNCERTAIN",     "DEFAULT": true,     "FLAGS": 1,     "ID": "STATE_UNCERTAIN",     "MAX": true,     "MIN": false,     "OPERATIONS": 5,     "TAB_ORDER": 7,     "TYPE": "BOOL",     "UNIT": ""   } }
Is it possible to implement this device?
Best regards
Horst

Hi,
yes somehow it will be possible. But without a device to test it it's not that easy. We've done the implementation by looking at the documentation in hm_devices_Endkunden.pdf. There it's saying, that the device should be able to behave like a switch-actor. Although I saw just now, that the KeyMatic-object is not inheriting from the Switch-class.
Anyhow, the KeyMatic-object provides an Action-Node, which has to be called with open. So instead of having a switch in the HASS UI, the device should be controlled with a service-call. So something like this:
action:
  service: homematic.virtualkey
  data:
    address: MEQ1324657
    channel: 1
    param: OPEN

Since we couldn't test that we don't know what that actually does. I would assume this would unlock the device, which closes after some amount of time. At least that's what I thought the device works like.
Indeed it would also make sense to make this device work like a regular switch since it should be capable of doing that.
So, could you please clarify what the device can to, and how that relates to the paramters the documentation above mentions?

I can imagine that it is not easy to implement without having the device, but thanks for trying...
In principle the Key-Sec has to switching flags

state - setting false locks the door 'verriegelt'
setting true - unlocks the door 'entriegelt'

open - setting true opens the door 'wirkliches öffnen, wie Türklinke drücken'

Then there is a thrird flag which is interesting, STATE_UNCERTAIN
means - the device is not sure if the door was opened from outside by a key
If there is anything more you need to know please let me know...

@pvizeli has pushed a commit, which should enable the usage of the device as a switch. That will be included in the next HASS release, which will reference the new pyhomematic version.
If you want you can try it out and confirm that it's working by manually applying the changes from commit ab7ffd3747f81e3b462b0a1226e1afeca7992587 to the pyhomematic your HASS is using. How that's done depends on how you're running hass.
Have you tried my suggestion regarding the OPEN-action through usage of the homematic.virtualkey service? You can also do that through the HASS UI on the services-site (your-hass-url/dev-service).
The payload then should look something like:
{
  "address": "LEQ1234657",
  "channel": 1,
  "param": "OPEN"
}

This should already be working.
Regarding the STATE_UNCERTAIN it probably would make sense to generate an additional sensor-entity in HASS, which could then be tracked using automations. Do you agree on that being a useful way of using the data?

tried via the service console - but unfortunately not working
16-11-26 12:40:35 homeassistant.components.homematic: 1 is not a channel in hm device KEQ0856675
tried also with the state flag
16-11-26 12:42:11 homeassistant.components.homematic: STATE not datapoint in hm device KEQ0856675
Is there any options where i can see which data home assistant knows abot my HM devices?

I have added another fix to the actors.py file (added the ELEMENT-property). Could you please try again? That could actually make the entity work as a switch and open the lock with the service.
The data HASS knows about your device can be seen on the entities-page in the HASS-UI. It should be one of the switch-devices.

patched the actor.py - if i click now the device in hass gui i get following error in the log:
16-11-27 15:56:11 homeassistant.core: Error doing job: Task exception was never retrieved Traceback (most recent call last):   File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step     result = coro.throw(exc)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 1050, in _event_to_service_call     yield from service_handler.func(service_call)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/switch/__init__.py", line 92, in async_handle_switch_service     yield from switch.async_turn_off()   File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity.py", line 356, in async_turn_off     None, ft.partial(self.turn_off, **kwargs))   File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup     value = future.result()   File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result     raise self._exception   File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run     result = self.fn(*self.args, **self.kwargs)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/switch/homematic.py", line 59, in turn_off     self._hmdevice.off(self._channel) AttributeError: 'KeyMatic' object has no attribute 'off'
tried also the patch in homematic.py - by sending the action as virtual key i get
16-11-27 15:59:23 pyhomematic.devicetypes.generic: HMGeneric.setValue: Exception: <Fault -5: 'Parameter of type action cannot be set to "false".'>
If i look to the entities page in HASS it seems there is no channel definition of the device available:
{
"ID": "KEQ0856675",
"RSSI": -74,
"friendly_name": "EG_FLR_Motorschloss"
}

How did you patch the actors.py? My change with the ELEMENT-property wasn't relevant. But making the KeyMatic class inherit from GenericSwitch (class KeyMatic(GenericSwitch)) should have done the trick for locking and unlocking the device through the UI.

How did the payload look like?

The channels aren't listed in the entity-data, since there can be multiple channels, and they usually is no need to show them.

And one more thing that comes to my mind:
try changing 1 to True in https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/homematic.py
Maybe that get's the OPEN-action to work.

i patched it in the installed file on my raspberry
vi /usr/local/lib/python3.4/dist-packages/homeassistant/components/homematic.py
and restarted the home-assistant-service
16-11-27 16:33:44 pyhomematic.devicetypes.generic: HMGeneric.setValue: key = 'OPEN' value = '1'
16-11-27 16:33:44 pyhomematic.devicetypes.generic: HMGeneric.setValue: Exception: <Fault -5: 'Parameter of type action cannot be set to "false".'>
that is all i get within the log file while pyhomematic is on debug
Is there any way to get more information and debug with python?

The patch I meant was meant for pyhomematic itself. So the actors.py on your system has to be in sync with actors.py

try changing 1 to True in https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/homematic.py

That made the virtual key working! great
Should i reroll the patch on actors.py?

Great!
Yes. I suggest to replace the whole file to make sure everything in there is up to date.

ok, downloaded the whole file from git - but still the problem that pushing the button in HASS Gui is not working
Traceback (most recent call last):   File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step     result = coro.throw(exc)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 1050, in _event_to_service_call     yield from service_handler.func(service_call)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/switch/__init__.py", line 92, in async_handle_switch_service     yield from switch.async_turn_off()   File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity.py", line 356, in async_turn_off     None, ft.partial(self.turn_off, **kwargs))   File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup     value = future.result()   File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result     raise self._exception   File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run     result = self.fn(*self.args, **self.kwargs)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/switch/homematic.py", line 59, in turn_off     self._hmdevice.off(self._channel) AttributeError: 'KeyMatic' object has no attribute 'off'

Hhmm, doesn't make sense to me. Other switches are working. You can change the loglevel like this:
logger:
  default: warning
  logs:
    homeassistant.core: warning
    homeassistant.components.homematic: debug
    pyhomematic: debug

Maybe that will provide some useful information.

you are right, all my other stuff is working. please don't get me wrong, i appreciate your support and didn't want to blame...
added the missing line homeassistant.components.homematic to the logger but still the same output...
16-11-27 17:10:21 homeassistant.core: Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step
result = coro.throw(exc)
File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 1050, in _event_to_service_call
yield from service_handler.func(service_call)
File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/switch/init.py", line 92, in async_handle_switch_service
yield from switch.async_turn_off()
File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity.py", line 356, in async_turn_off
None, ft.partial(self.turn_off, **kwargs))
File "/usr/lib/python3.4/asyncio/futures.py", line 388, in iter
yield self  # This tells Task to wait for completion.
File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
value = future.result()
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/switch/homematic.py", line 59, in turn_off
self._hmdevice.off(self._channel)
AttributeError: 'KeyMatic' object has no attribute 'off'
within the entities i see one difference from a normal switch device to the keymatic
switch.dg_msd_reserve	off	ID: KEQ1109986
RSSI: -60
Working: No
friendly_name: DG_MSD_Reserve
switch.eg_flr_motorschloss	on	ID: KEQ0856675
RSSI: -61
friendly_name: EG_FLR_Motorschloss
There is no Working flag listed

That's because the KeyMatic does not have that parameter.
Since I'm running out of ideas, could you please try to use pyhomematic manually as seen in example.py?
Within the shell you should be able to do the following operations:
pyhomematic.devices["KEQ0856675"].is_on()
pyhomematic.devices["KEQ0856675"].is_off()
pyhomematic.devices["KEQ0856675"].on()
pyhomematic.devices["KEQ0856675"].off()

# and do this so we can see what the object actually looks like
dir(pyhomematic.devices["KEQ0856675"])

dir(pyhomematic.devices["KEQ0856675"])
['ACTIONNODE', 'ADDRESS', 'ATTRIBUTENODE', 'BINARYNODE', 'CHANNELS', 'ELEMENT', 'EVENTNODE', 'NAME', 'PARAMSETS', 'SENSORNODE', 'TYPE', 'UNREACH', 'WRITENODE', '_ACTIONNODE', '_ADDRESS', '_ATTRIBUTENODE', '_AVAILABLE_FIRMWARE', '_BINARYNODE', '_CHANNELS', '_CHILDREN', '_EVENTNODE', '_FAMILY', '_FIRMWARE', '_FLAGS', '_ID', '_INTERFACE', '_PARAMSETS', '_PARAMSET_DESCRIPTIONS', '_PARENT_TYPE', '_PHYSICAL_ADDRESS', '_RF_ADDRESS', '_ROAMING', '_RX_MODE', '_SENSORNODE', '_TYPE', '_UPDATABLE', '_VERSION', '_WRITENODE', 'class', 'delattr', 'dict', 'dir', 'doc', 'eq', 'format', 'ge', 'getattribute', 'gt', 'hash', 'init', 'le', 'lt', 'module', 'ne', 'new', 'reduce', 'reduce_ex', 'repr', 'setattr', 'sizeof', 'str', 'subclasshook', 'weakref', '_eventcallbacks', '_getNodeData', '_hmchannels', '_name', '_paramsets', '_proxy', '_setNodeData', '_unreach', 'actionNodeData', 'event', 'getAttributeData', 'getBinaryData', 'getParamsetDescription', 'getSensorData', 'getValue', 'getWriteData', 'get_rssi', 'get_state', 'is_off', 'is_on', 'off', 'on', 'putParamset', 'setEventCallback', 'setValue', 'set_state', 'updateParamset', 'updateParamsets', 'writeNodeData']
Cool :-)
Played in the past with PERL and FHEM arround, but now i like python definately more
I can drive the HM-KEY-SEC with
pyhomematic.devices["KEQ0856675"].on()
pyhomematic.devices["KEQ0856675"].off()

Yes, Python is quite nice. That's why I left FHEM behind and started with this library. ;-)
Ok, so now we know, that the object pyhomematic is generating generally is capable of doing everything like it should. For some reason though HASS doesn't see the on/off methods.
@pvizeli any idea why that happens?

How flexible is your library? I am asking while i am developing an HM framework for Arduino. Target is to generate own devices. Additional i am creating xml device files for the ccu or homegear to let them know about the functionallity of the specific device. Currently i have the switch modul working, dimmer misses some configuration variables, next to come is a remote and sensor module.
As explained, the devices will have their own xml file while could be a mix of a switch with a remote and some sensor channels. The sensor channels can transmit values as degree celcius, or % humidity or watt or whatever.
Within FHEM their was no easy way of introducing new devices, while everything was hardcoded in some modules. Homegear is flexible enough to handle new devices on base of the xml file, is home-assistant, or your module flexible enough?

We don't parse any XML. Device support has to be manually introduced, like you can see with the switches in actors.py. But you can mix different types quite easily and create new classes. So for example the class for the power-meter-switch inherits it's capabilities from the generic HMDevice class, but also some from one of the Switch classes, and somehow also of sensors.
So basically we're trying to rebuild what the XML-files are telling us with Python-Objects inheriting from one another.
The problem I see in your case is, that EQ3 probably will never add the XML files for the devices you build to the CCU. So they will only work with Homegear.
Personally I think it would make more sense to let them use the MQTT protocol. I'm pretty sure there are already quite a lot Arduino-projects doing just that. And with MQTT those devices work with HASS out of the box, and also pretty much any other application capable of speaking MQTT. As far as I know there's even somehow the possibility to talk MQTT with the CCU (Google hm2mqtt). Even Homegear supports MQTT.
So instead of limiting yourself to follow the specification of a vendor that's mostly active in the german speaking area, why not go global with a protocol that's spoken internationally?

Regarding KeyMatic:
Turns out the switching may be fixed by some other change that's already up to be merged for the next HASS release. The Pull Request where all this happens is here: 4568

i like the idea of peering devices :-)
mqtt is a server based protocol, but with homematic you can communicate between certain devices.
Imagine, your server is down but your blind is out and it starts raining :-)

Since I have never done device peering I can't say much about that. But I would stick to my opinion, that such a device should still be, additionally to enything else, capable of talking MQTT.
Event though pyhomematic would be capable of supporting your devices, the classes for self-made devices shouldn't be in pyhomematic by default. Some sort of plug-in mechanism would be ok. But letting custom devices enter our code could lead other developers to also wanting to do that, and then we would have to decide which classes make it into the final release, and nobody except the owner could actually verify everything is working correctly.
So, yeah, I guess some sort of Plug-In functionality may make sense in that case.

Closing this issue since the bug should be fixed now. It might be reasonable to convert the current type from a switch to a lock-type, which exposes open/close methods instead of on/off. But that's just cosmetic and should be part of another issue.

Seems as if this issue wasn't fixed with the update: https://community.home-assistant.io/t/keymatic-with-homegear/16469

As I mentioned in https://community.home-assistant.io/t/keymatic-with-homegear/16469/21 the script is not working for me:
#!/usr/bin/python3
import time
import sys
import logging
from pyhomematic import HMConnection

logging.basicConfig(level=logging.INFO)

def systemcallback(src, *args):
    print(src)
    for arg in args:
        print(arg)

try:
    pyhomematic = HMConnection(interface_id="myserver",
                               autostart=True,
                               systemcallback=systemcallback,
                               remotes={"rf":{
                                   "ip":"<IP_ADDRESS>",
                                   "port": 2001}})
except Exception:
    sys.exit(1)

sleepcounter = 0

def eventcallback(address, interface_id, key, value):
    print("CALLBACK: %s, %s, %s, %s" % (address, interface_id, key, value))

while not pyhomematic.devices and sleepcounter < 20:
    print("Waiting for devices")
    sleepcounter += 1
    time.sleep(1)
print(pyhomematic.devices)

pyhomematic.devices["FEQ00XXXXX"].setEventCallback(eventcallback)
time.sleep(10)

print(pyhomematic.devices["FEQ00XXXXX"].on())
print(pyhomematic.devices["FEQ00XXXXX"].is_on())

time.sleep(10)
print(pyhomematic.devices["FEQ00XXXXX"].off())
print(pyhomematic.devices["FEQ00XXXXX"].is_off())

pyhomematic.stop()

sys.exit(0)

I also tried feq00XXXXX

Can you teach how can I get a list of device ids from pyhomematic?

That's actually what the line with print(pyhomematic.devices) should already do. One of the first things you would see would be a large block with all the devices that were detected.

That's my output:
INFO:pyhomematic._hm:Creating proxy rf. Connecting to http://<IP_ADDRESS>:2001
createDeviceObjects
INFO:pyhomematic._hm:Starting server at http://<IP_ADDRESS>:34635
INFO:pyhomematic._hm:Proxy initialized
{'rf': {}}
Traceback (most recent call last):
  File "example.py", line 35, in <module>
    pyhomematic.devices["FEQ00XXXXX"].setEventCallback(eventcallback)
KeyError: 'FEQ00XXXXX'
listDevices
myserver-rf

After that I got all the homegear debug messages.

I think it will work better if you do it manually on the Python shell. Open the Python shell by entering python3 on the commandline. From there, enter the following commands one after another:
import logging
from pyhomematic import HMConnection
logging.basicConfig(level=logging.INFO)
pyhomematic = HMConnection(interface_id="myserver", autostart=True, remotes={"rf":{"ip":"<IP_ADDRESS>", "port": 2001}})
# Now wait a few seconds. You should see some output
print(pyhomematic.devices)
# Now you should see all the devices you have

I've made another minor modification for KeyMatic in actors.py. If you replace the actors.py from HASS with this one AND perform the modification mentioned below, you should get two more sensors: ERROR (a numeric value) and STATE_UNCERTAIN (True if the lock doesn't know the actual state).
Needed chage in homematic.py from HASS:
Add 'KeyMatic' to the DISCOVER_SENSORS and DISCOVER_BINARY_SENSORS lists.

After applied your modification I restarted HASS and I was able to see the new sensors. Values were 0 for sensor.feq00xxxxx_error and off. for binary_sensor.feq00xxxxx_state_uncertain. After I reproduced the error sensor.feq00xxxxx_error changed to value 2. The attribute sabotage also changed to value 2. binary_sensor.feq00xxxxx_state_uncertain is still off.

import logging
from pyhomematic import HMConnection
logging.basicConfig(level=logging.INFO)
pyhomematic = HMConnection(interface_id="myserver", autostart=True, remotes={"rf":{"ip":"<IP_ADDRESS>", "port": 2001}})
# Now wait a few seconds. You should see some output
print(pyhomematic.devices)
# Now you should see all the devices you have
pyhomematic.stop()

is working via python shell and I get following output:
'FEQ00XXXXXX': <pyhomematic.devicetypes.actors.KeyMatic object at 0x759a7090>
If I try to execute pyhomematic.devices['FEQ00XXXXX'].setEventCallback(eventcallback) I get the known error: KeyError: 'FEQ00XXXXX'
I also tried these syntax without any success:
pyhomematic.devices[FEQ00XXXXX].setEventCallback(eventcallback)`` pyhomematic.devices["FEQ00XXXXX"].setEventCallback(eventcallback)``

The error-value of 2 you get could be a problem. The value 2 stands for MOTOR_ABORTED. I don't think that should ever happen in normal operation.
You can leave away the lines with setEventCallback. When you use the lines I told you to enter manually, the callback isn't defined, so you can't set it. What you should try instead is the following:
print(pyhomematic.devices["FEQ00XXXXX"].on())
print(pyhomematic.devices["FEQ00XXXXX"].is_on())
print(pyhomematic.devices["FEQ00XXXXX"].off())
print(pyhomematic.devices["FEQ00XXXXX"].is_off())

With those lines you should be able to lock and unlock the device and print out the current state.

That explains the whole behaviour I guess. As far as I know it's the standard that the switch is not switched if it runs into an error. Let me try to fix it.

I fixed the error, but unfortunately the switch issue is not fixed. I adjusted the ANGLE_MAX value and it's now working without setting sensor.feq00xxxxx_error to value 2. Behaviour in HASS is the same like before.
Tested the script again, but KeyError: 'FEQ00XXXXX'
import logging
from pyhomematic import HMConnection
logging.basicConfig(level=logging.INFO)
pyhomematic = HMConnection(interface_id="myserver", autostart=True, remotes={"rf":{"ip":"<IP_ADDRESS>", "port": 2001}})
print(pyhomematic.devices)
print(pyhomematic.devices["FEQ00XXXXX"].on())

Just to verify it's not an operational error: do you have any other switch-devices with which you could verify those few lines of code work? If so, please do that to confirm devices other than the KeyMatic work when switching them manually.

Just tested it with one of my light switches - Same behaviour.

The KeyMatic now works correctly in the HASS UI?
In that case there was something you did wrong when accessing the switch / keymatic. Since you've always - for good reason - redacted the device-ID I can't see where the error was. But using the same code works for me. But that doesn't matter anymore if the KeyMatic is now working as it should. :)

Exactly! Thanks a lot for your support 👍 Like described in this thread locked-state is shown as off and unlocked-state is shown as on, but there a lot of methods to work around in HASS.
Yes - I think we don't need to invest more time in my Python problem.


Move to native Deno http

I've been trying to move from legacy std/http but didn't manage to do it, so anyone else is welcome

@talentlessguy if you still need help I would be up for it

@rekram1-node yes it'd be very appreciated!

@rekram1-node if you want I can assign the issue to you

@talentlessguy sure

@rekram1-node how's the work going?

work is going well on this branch #9


Fix installer.0 bug.

Insure that mon node is used for rbd_pools.
Signed-off-by: Warren Usui<EMAIL_ADDRESS>

This fixes installer.0 when rbd_pool is created and installer.0 has no monitors on the same node.

tests http://pulpito.ceph.com/teuthology-2017-12-22_14:55:03-ceph-ansible-master-distro-basic-vps/


Running Error: loaded state dict contains a parameter group that doesn't match the size of optimizer's group

When I tried to use pretrained model: sceneflow_pretrained_model.pth.tar, it reported error below:
Traceback (most recent call last):
File "/media/data1/dh/CODE/stereo-transformer/main.py", line 258, in
main(args_)
File "/media/data1/dh/CODE/stereo-transformer/main.py", line 189, in main
optimizer.load_state_dict(checkpoint['optimizer'])
File "/media/data1/dh/anaconda3/lib/python3.7/site-packages/torch/optim/optimizer.py", line 123, in load_state_dict
raise ValueError("loaded state dict contains a parameter group "
ValueError: loaded state dict contains a parameter group that doesn't match the size of optimizer's group

@Comet2dh
Good catch here. This is a corner case I didn't think about. You tried to resuming a training with the old model, which contains BN stats in the optimizer. In the latest version, the BN stats are removed. Thus you have this exception.
I fixed this in the latest PR #59 . Instead of throwing the ValueError, I raised an exception that reminds people this is not possible unfortuntely because optimizer params are not "named".
If you intend to run inference or finetune, you probably have fogotten some args.


Modify spawn to overworld biome causes freeze

I've recently found in the most recent update, that with an origin's modify spawn set to an overworld biome that isn't currently rendered in causes the server to freeze and in single player to be unable to respawn without first relogging. The modify spawn into a specific biome in the end and in the nether still works fine with a little lag, but not with an unloaded in overworld biome. When I tested with a biome next to spawn or a biome another player is already in, it did work though.

same problem

Having the same problem but it acts worse. Creating a new world spawns me in the right biome just fine, but dying makes the respawn button do nothing unless I had used a bed, even when I haven't moved from the initial spawn point, and relogging just puts me back on the same "You Died!" screen so I can't get back into the world. Trying the respawn button spits out this error in the log (btw this is origins 1.7.1 on Minecraft 1.19.2)
Failed to handle packet net.minecraft.class_2799@75682bee, suppressing error
java.lang.NullPointerException: Cannot invoke "net.minecraft.class_2338.method_10263()" because "pos" is null
at net.minecraft.class_1937.method_8320(class_1937.java:7070)
at net.minecraft.class_3222.handler$hcn000$onSetSpawnPoint(class_3222.java:20783)
at net.minecraft.class_3222.method_26284(class_3222.java)
at io.github.apace100.apoli.power.ModifyPlayerSpawnPower.onRemoved(ModifyPlayerSpawnPower.java:74)
at java.base/java.lang.Iterable.forEach(Iterable.java:75)
at net.minecraft.class_3324.handler$clf000$invokePowerRemovedCallback(class_3324.java:1085)
at net.minecraft.class_3324.method_14556(class_3324.java)
at net.minecraft.class_3244.method_12068(class_3244.java:1720)
at net.minecraft.class_2799.method_12120(class_2799.java:24)
at net.minecraft.class_2799.method_11054(class_2799.java:6)
at net.minecraft.class_2600.method_11072(class_2600.java:22)
at net.minecraft.class_3738.run(class_3738.java:18)
at net.minecraft.class_1255.method_18859(class_1255.java:157)
at net.minecraft.class_4093.method_18859(class_4093.java:23)
at net.minecraft.server.MinecraftServer.method_24306(MinecraftServer.java:776)
at net.minecraft.server.MinecraftServer.method_18859(MinecraftServer.java:159)
at net.minecraft.class_1255.method_16075(class_1255.java:131)
at net.minecraft.server.MinecraftServer.method_20415(MinecraftServer.java:758)
at net.minecraft.server.MinecraftServer.method_16075(MinecraftServer.java:752)
at net.minecraft.class_1255.method_5383(class_1255.java:116)
at net.minecraft.server.MinecraftServer.method_16208(MinecraftServer.java:736)
at net.minecraft.server.MinecraftServer.method_29741(MinecraftServer.java:669)
at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer.java:257)
at java.base/java.lang.Thread.run(Thread.java:833)
I can recover the world by removing the modify spawn power from the origin's files and restarting my game, at least.


Node module on NPM please

Proposed feature
Right now, installing this module is a pain - developers have to generate a GH_TOKEN. I tried setting up a scoped token, and got permision denied errors? Is there any good reason for this instead of NPM ?
Please create a release for NPM so that I can just run
npm i @input-output-hk/atala-prism-wallet-sdk

Feature description
=
Anything else?
=

Totally agree and we're planning to solve this problem and friction point as soon as possible. We'll get the package published in npm repo.
Meanwhile and as I wrote you here we can and are more than happy to assist you while the package is not published so you can have access to the data.
Installing the package from github directly is a very bad idea.

Note to others - use the classic tokens from github.

In combination with #112 , I decided it was easier to publish this myself.
I chose a name not associated with this project so as not to name-squat, or advertise it's existence:
https://www.npmjs.com/package/ahau-vc-sdk

Hello @mixmix , we forgot to apply the update in the readme instructions but the package has just been released in the new Atala organisation on NPM.
You can safely destroy that package and use https://www.npmjs.com/package/@atala/prism-wallet-sdk instead.
Thank you!


Example: Local Package Import - Support Windows

Coverage remained the same at 100.0% when pulling e03cf0461b5de77a7b517b7e4eae7eb2c8708aa0 on 53 into ef4dd98e18e0b31432aed397845f79c1f1216160 on master.


[Request] Missing doc for testing api using 'api' auth scheme

As documentation said about authenticate user while testing, I expect loginVia method treating any token-based authentication the same way and in this case I'm using personal api scheme as default. Which mean I could test my end-point this way
test('Get Some Data', async ({ client }) => {
  const user = await User.first()
  const response = await client.get('/end-point')
    .accept('json')
    .loginVia(user)
    .end()

  response.assertStatus(200)
  response.assertJSONSubset(expectedData)
})

But when I take a look at src/Schemes/Api it request a string instead of User Instance.
https://github.com/adonisjs/adonis-auth/blob/5e3e59bf761950651df6c6859794e287292fa50d/src/Schemes/Api.js#L199-L201
While the src/Schemes/Jwt we could simply pass the instance of User
https://github.com/adonisjs/adonis-auth/blob/5e3e59bf761950651df6c6859794e287292fa50d/src/Schemes/Jwt.js#L441-L444
The question is

Why both should be treated differently?
Why both couldn't accept 2 types of params, which is string of token or User instance? also
Why doc doesn't mention about api scheme?

Thanks & cheers 🥂

Yes, they should not be. Fixing it here https://forum.adonisjs.com/t/authenticating-rest-api-tests/972/2

Awesome! thanks so much @thetutlage.


Fixed #25938 -- Factored out common base class for GEOSBase and GDALBase.

https://code.djangoproject.com/ticket/25938

@timgraham, all your suggestions are applied.

I would say we prefer assertRaisesMessage and only resort to assertRaisesRegex when needed.

Please send a new PR when this is ready to review.


adapt fc_mpi test for MS Windows by utilizing ms-mpi package

2 msmpi files are modified according to the tutorial

Rado, please restart the build https://travis-ci.org/scisoft/autocmake/builds/79170217 due to problems described in https://github.com/scisoft/autocmake/issues/119 .

Let's fix this problem in #117.

Thanks! I integrated it anyway.


tag releases for semantic versioning

this is very important for people vendoring your code, see this excellent article for more information

Thank you for bringing this to my attention. This is clearly an oversight.
I will release a proper semantically versioned tag of this package once I'm home tonight, as I am at my day job where it would be legally and morally inappropriate and reprehensible to work on a personal project such as this, even one for which I am extremely passionate about.
I implore you to be patient with me, and I promise you can begin using the semantically proper version of the package in no time!

I would like to officially let you know that I have corrected my oversight.
The official v1.0.0 tag is up, and you can begin using it immediately!
Thanks again


python.envFile need to restart/reload vscode to take effect

Environment data

VS Code version: 1.46.0
Extension version (available under the Extensions sidebar): v2020.6.88468
OS and version: Windows_NT x64 10.0.18363
Python version (& distribution if applicable, e.g. Anaconda): 3.6
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): both

Expected behavior
I set PYTHONPATH in the python.envFile for autocomplete. I hoped the PYTHONPATH can take effect immediately when I changed the PYTHONPATH.
Actual behavior
I need to restart or reload vscode for autocomplete to take effect after modifying the PYTHONPATH.

This will be an enhancement. We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

Thanks for the suggestion! We talked about it with the team and we have unfortunately decided we will not be moving forward with this idea. We think there isn't an enough widespread need for this to warrant the maintenance cost for the feature. However, we will consider this scenario when addressing #6544.


Scaffold-GS

hi, whether or not we support the Scaffold-GS in this project in the future?
Thanks.

We are open for contribution on Scaffold-GS!


Error when running segmeth   Value error: invalid contig

Hi Adam,
Sorry to keep bothering you. I ran into this error when running methylartist segmeth. I have included below the error traceback. This seems similar to an issue I was having when running tldr, which also kicked up an error when I ran it that to me looked similar as it also had to do with the chromosome CM025008.1. If you get a chance to look at this, if you could also let me know if it is related to the issue in tldr that would be fantastic (I have an open issue for this on tldr's page as well). Let me know if you can figure this out as I'd really love to run this tldr on this run as well. And let me know if any further information would be helpful. Thanks again for this great software, I have some high hopes for the information it could deliver on this organism.
nohup: ignoring input and appending output to 'nohup.out'

data=/project/bbenayou_34/malone/nanopore/methylartist/scripts/data.txt
inputFile=/project/bbenayou_34/malone/nanopore/methylartist/0610FishTEDBGTFtutorial.bed
methylartist segmeth -d /project/bbenayou_34/malone/nanopore/methylartist/scripts/data.txt -i /project/bbenayou_34/malone/nanopore/methylartist/0610FishTEDBGTFtutorial.bed -p 32 --excl_ambig
2022-01-13 10:57:19,614 starting methylartist with command: /home1/malonema/.local/bin/methylartist segmeth -d /project/bbenayou_34/malone/nanopore/methylartist/scripts/data.txt -i /project/bbenayou_34/malone/nanopore/methylartist/0610FishTEDBGTFtutorial.bed -p 32 --excl_ambig
2022-01-13 10:57:19,623 found mod names: m
2022-01-13 10:57:19,623 segmeth output filename: 0610FishTEDBGTFtutorial.data.excl_ambig.segmeth.tsv
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/spack/apps/linux-centos7-x86_64/gcc-8.3.0/python-3.9.2-uvcroioc4witkp6qf7mbebof5ix4wlb6/lib/python3.9/multiprocessing/pool.py", line 125, in worker
result = (True, func(*args, **kwds))
File "/home1/malonema/.local/bin/methylartist", line 512, in get_segmeth_calls
reads = exclude_ambiguous_reads(bam_fn, chrom, seg_start, seg_end, min_mapq=int(args.min_mapq), spanning_only=args.spanning_only)
File "/home1/malonema/.local/bin/methylartist", line 368, in exclude_ambiguous_reads
for read in bam.fetch(chrom, start, end):
File "pysam/libcalignmentfile.pyx", line 1091, in pysam.libcalignmentfile.AlignmentFile.fetch
File "pysam/libchtslib.pyx", line 685, in pysam.libchtslib.HTSFile.parse_region
ValueError: invalid contig "CM025008.1"
"""

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home1/malonema/.local/bin/methylartist", line 3770, in
main(args)
File "/home1/malonema/.local/bin/methylartist", line 3547, in main
args.func(args)
File "/home1/malonema/.local/bin/methylartist", line 1609, in segmeth
meth_result, seg = res.get()
File "/spack/apps/linux-centos7-x86_64/gcc-8.3.0/python-3.9.2-uvcroioc4witkp6qf7mbebof5ix4wlb6/lib/python3.9/multiprocessing/pool.py", line 771, in get
raise self._value
ValueError: invalid contig "CM025008.1"

If you're referencing issue 23 on tldr, I don't think that's related. This one just looks like the bed file you're using might contain contigs not present in at least one of the .bam files. What happens if you try samtools view your.bam CM025008.1 | head?


New doc: how to prepare BIG-IP for LBaaS

OpenStack Release
Liberty +
Description
From the documentation we have for LBaaS, it would be helpful to have a section talk about what the expectation there is for the BIG-IP to be “ready” for the LBaaS deployment.  I’m thinking about what selfip’s need to be created, VTEP’s when using VXLAN, what needs to be done for GRE, what vlans need to be created?

This is pretty much the same as #146. Documentation for each feature needs to list the pre-reqs, including what has to be pre-configured on the BIG-IP(s).


Strange artifact displayed after INPUT

Hello, first of all I'd like to thank you for creating this powerful tool. I think it's way more versatile, fast and powerful than the plain Basic V.2.0 a newbie like me would be stuck to. So, thanks again. A lot.
I'm encountering a strange bug: a weird character is shown on screen after the program gets user's INPUT. I don't know if I'm doing something wrong. I attach a screenshot of this problem, the character is underlined in red. Here is the code behind the screenshot (I'm trying to code a text adventure, so INPUT is the core of the experience! :-) ).
I'm using the latest XC=Basic version, i.e. 2.3.09
Thanks.
Dom (Italy)
dim ibuffer![41]
i$ = @ibuffer!
print "{CLR}"
print ""
print "write something here:" ;
input i$, 41
print "" : print ""
print "you wrote:", i$

Hi Dom
Thanks for giving XC=BASIC a try!
Well, yes, this is a known bug. I'll try to fix it and let you know when it's done.

Hi Dom
Thanks for giving XC=BASIC a try!
Well, yes, this is a known bug. I'll try to fix it and let you know when it's done.

Had some time after lunch so I fixed it: https://github.com/neilsf/XC-BASIC/releases/tag/v2.3.10
BTW, there is a possible mistake in your code. The buffer should be one byte longer than the maximum string length. This is because one byte must be preserved for the end character, which is a zero byte (0x00). So if buffer is 41 bytes long, the input should be maximum 40 chars.

Had some time after lunch so I fixed it: https://github.com/neilsf/XC-BASIC/releases/tag/v2.3.10
BTW, there is a possible mistake in your code. The buffer should be one byte longer than the maximum string length. This is because one byte must be preserved for the end character, which is a zero byte (0x00). So if buffer is 41 bytes long, the input should be maximum 40 chars.

Had some time after lunch so I fixed it: https://github.com/neilsf/XC-BASIC/releases/tag/v2.3.10
BTW, there is a possible mistake in your code. The buffer should be one byte longer than the maximum string length. This is because one byte must be preserved for the end character, which is a zero byte (0x00). So if buffer is 41 bytes long, the input should be maximum 40 chars.

Thank you so much, the mischievous character has disappeared! :-D
I also fixed the buffer mistake. ;-)

Had some time after lunch so I fixed it: https://github.com/neilsf/XC-BASIC/releases/tag/v2.3.10
BTW, there is a possible mistake in your code. The buffer should be one byte longer than the maximum string length. This is because one byte must be preserved for the end character, which is a zero byte (0x00). So if buffer is 41 bytes long, the input should be maximum 40 chars.

Thank you so much, the mischievous character has disappeared! :-D
I also fixed the buffer mistake. ;-)


"genmove" with no color results in crash

expected behavior not a crash

is the crash in gtp.py?

In may have been on this line https://github.com/jtauber/gtp/blob/master/gtp.py#L69 but minigo is complicated to setup so I can't verify

I'll take this, I'm looking at that code anyway

The problem is that gtp.py always assumes that the color is specified: https://github.com/jtauber/gtp/blob/1e55c3e0f146baf511264b8fa6294786c402dfff/gtp.py#L220
I'll just work around it for now because I'm going to refactor all that code soon and I'm not sure that gtp.Engine is actually giving us much benefit these days.