text:
客户端订阅服务后报错"missing field serviceInfo"

nacos服务版本: 2.2.2
nacos-sdk-rust版本: 0.2.5
注: 注册的服务不在public组, nacos已开启鉴权, 客户端不订阅服务的时候, 可以跑通. 在订阅服务后, 也可以跑通, 但是只接收到一次服务变更的订阅消息, 后续的服务变更消息就无法收到了.
日志信息:
2023-04-27T06:28:03.061654Z  INFO request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update: nacos_sdk::naming::updater: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\updater\mod.rs:185: 992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:test-group:tonic-grpc::ServiceInfoUpdateTask refreshing
2023-04-27T06:28:03.063710Z ERROR request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update:unary_call_async{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" conn_id="1682576873792_127.0.0.1_50263"}:unary_call_async{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2"}: nacos_sdk::common::remote::grpc::message: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\message\mod.rs:88: payload {"resultCode":500,"errorCode":403,"message":"user not found!","success":false} can not convert to QueryServiceResponse occur an error:Serialization(Error("missing field `serviceInfo`", line: 1, column: 78))
2023-04-27T06:28:03.064569Z ERROR request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update: nacos_sdk::naming::updater: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\updater\mod.rs:219: 992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:test-group:tonic-grpc::ServiceInfoUpdateTask occur an error: Serialization(Error("missing field `serviceInfo`", line: 1, column: 78))
2023-04-27T06:28:03.722855Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:04.611174Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:05.067064Z  INFO request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update: nacos_sdk::naming::updater: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\updater\mod.rs:185: 992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:test-group:tonic-grpc::ServiceInfoUpdateTask refreshing
2023-04-27T06:28:05.068995Z ERROR request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update:unary_call_async{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" conn_id="1682576873792_127.0.0.1_50263"}:unary_call_async{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2"}: nacos_sdk::common::remote::grpc::message: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\message\mod.rs:88: payload {"resultCode":500,"errorCode":403,"message":"user not found!","success":false} can not convert to QueryServiceResponse occur an error:Serialization(Error("missing field `serviceInfo`", line: 1, column: 78))
2023-04-27T06:28:05.069787Z ERROR request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update: nacos_sdk::naming::updater: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\updater\mod.rs:219: 992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:test-group:tonic-grpc::ServiceInfoUpdateTask occur an error: Serialization(Error("missing field `serviceInfo`", line: 1, column: 78))
2023-04-27T06:28:05.921950Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:06.811825Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:08.725451Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:09.071860Z  INFO request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update: nacos_sdk::naming::updater: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\updater\mod.rs:185: 992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:test-group:tonic-grpc::ServiceInfoUpdateTask refreshing
2023-04-27T06:28:09.073517Z ERROR request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update:unary_call_async{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" conn_id="1682576873792_127.0.0.1_50263"}:unary_call_async{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2"}: nacos_sdk::common::remote::grpc::message: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\message\mod.rs:88: payload {"resultCode":500,"errorCode":403,"message":"user not found!","success":false} can not convert to QueryServiceResponse occur an error:Serialization(Error("missing field `serviceInfo`", line: 1, column: 78))
2023-04-27T06:28:09.074254Z ERROR request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update: nacos_sdk::naming::updater: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\updater\mod.rs:219: 992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:test-group:tonic-grpc::ServiceInfoUpdateTask occur an error: Serialization(Error("missing field `serviceInfo`", line: 1, column: 78))
2023-04-27T06:28:09.614127Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:10.924793Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:11.815126Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:13.729705Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:14.616659Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:15.927770Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:16.817808Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:17.077091Z  INFO request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update: nacos_sdk::naming::updater: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\updater\mod.rs:185: 992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:test-group:tonic-grpc::ServiceInfoUpdateTask refreshing
2023-04-27T06:28:17.078860Z ERROR request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update:unary_call_async{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" conn_id="1682576873792_127.0.0.1_50263"}:unary_call_async{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2"}: nacos_sdk::common::remote::grpc::message: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\message\mod.rs:88: payload {"resultCode":500,"errorCode":403,"message":"user not found!","success":false} can not convert to QueryServiceResponse occur an error:Serialization(Error("missing field `serviceInfo`", line: 1, column: 78))
2023-04-27T06:28:17.079575Z ERROR request{request_id="d9267191-0952-4939-a9b5-8c4fa7fb9734"}:subscribe{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2" group="test-group" service_name="tonic-grpc"}:schedule_update: nacos_sdk::naming::updater: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\updater\mod.rs:219: 992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:test-group:tonic-grpc::ServiceInfoUpdateTask occur an error: Serialization(Error("missing field `serviceInfo`", line: 1, column: 78))
2023-04-27T06:28:18.732611Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:19.620278Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:20.930710Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:20.989505Z DEBUG config_init{client_id="config:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:1"}:config_auth_task: nacos_sdk::api::plugin::auth::auth_by_http: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\api\plugin\auth\auth_by_http.rs:44: Http login return because now_instant lte next_login_refresh.
2023-04-27T06:28:20.989968Z DEBUG config_init{client_id="config:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:1"}:config_auth_task: nacos_sdk::config::worker: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\config\worker.rs:97: auth_plugin schedule at fixed delay
2023-04-27T06:28:21.821075Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:21.875127Z DEBUG naming_init{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:1"}:naming_auth_task: nacos_sdk::api::plugin::auth::auth_by_http: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\api\plugin\auth\auth_by_http.rs:44: Http login return because now_instant lte next_login_refresh.
2023-04-27T06:28:21.875746Z DEBUG naming_init{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:1"}:naming_auth_task: nacos_sdk::naming: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\mod.rs:129: auth_plugin schedule at fixed delay
2023-04-27T06:28:23.736651Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:23.791379Z DEBUG config_init{client_id="config:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2"}:config_auth_task: nacos_sdk::api::plugin::auth::auth_by_http: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\api\plugin\auth\auth_by_http.rs:44: Http login return because now_instant lte next_login_refresh.
2023-04-27T06:28:23.791770Z DEBUG config_init{client_id="config:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2"}:config_auth_task: nacos_sdk::config::worker: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\config\worker.rs:97: auth_plugin schedule at fixed delay
2023-04-27T06:28:24.623739Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:24.677771Z DEBUG naming_init{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2"}:naming_auth_task: nacos_sdk::api::plugin::auth::auth_by_http: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\api\plugin\auth\auth_by_http.rs:44: Http login return because now_instant lte next_login_refresh.
2023-04-27T06:28:24.678394Z DEBUG naming_init{client_id="naming:127.0.0.1:8848:992eb8e9-c1c9-40f1-9f80-ca669ed59e7e:2"}:naming_auth_task: nacos_sdk::naming: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\naming\mod.rs:129: auth_plugin schedule at fixed delay
2023-04-27T06:28:25.934455Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }
2023-04-27T06:28:26.823072Z DEBUG nacos_sdk::common::remote::grpc: E:\Library_Store\Cargo\registry\src\github.com-1ecc6299db9ec823\nacos-sdk-0.2.5\src\common\remote\grpc\mod.rs:131: health check. HealthCheckResponse { result_code: 200, error_code: 0, message: None, request_id: None }

看起来 403 呀 {"resultCode":500,"errorCode":403,"message":"user not found!","success":false}

估计你自己本地加一下日志看看 login 返回的 token 是否有效，是否后续被服务端验证不通过了

问题也比较奇怪, 客户端获取可用的服务是成功的, 也能获取到可用的服务列表, 但就是订阅功能不行

有可能是nacos服务端的BUG, 跟token有关系.

找到原因了, 是ServiceInfoUpdateTask的start方法里, 发送请求的时候把token相关的header丢掉了

@gy0801151351 大佬,有空的话多来 0.3.x 分支看看, 有些设计重新弄了一下,望大佬多多提意见

@gy0801151351 大佬,有空的话多来 0.3.x 分支看看, 有些设计重新弄了一下,望大佬多多提意见

好的

authors: CherishCai gy0801151351 onewe

repo: nacos-group/nacos-sdk-rust


text:
When an advert is playing

When an advert is playing this fails..
res.track.length
Do you know what the res object looks like when an advert is playing, sorry to ask but it will save me some time not waiting for an advert...

Not sure how it looks, but why not just check if the res.track/ res.track.length object is defined and skip if it's not?

Cheers dude, This is what I did... it also fixes another issue when a track is not available in the users country.
It will be in my V2 release coming this week.

source: gharchive/issue

authors: Fasani nadavbar

repo: nadavbar/node-spotify-webhelper

license: mit

license_type: permissive

license_source: bigquery


text:
SignIn 페이지 UI 구현

해당 사항 (중복 선택)

FEAT : 새로운 기능 추가 및 개선
CHORE : 패키지 매니저 설정, 코드 수정 없이 설정 변경(eslint) 등 기타 사항

설명
로그인 페이지 UI 제작했습니다. ("/signin")
이슈 번호

cloes #84

footer를 나중에 아래에 고정시키고, height을 100%로 해야할듯!

지금 27인치 화면에서 하단부가 좀 비게 되는데, 이거 어떻게 처리하면 좋지? 그냥 이대로 놔 두어도 되려나?

일단 castle height를 100%로 변경해서 좀 길어지긴 했을텐데, 계속 비면 나중에 한번 처리해봐야 할듯..!?

source: gharchive/pull-request

authors: shyjnnn wooleejaan

repo: najasin/na-jasin-fe

license: MIT

license_source: github-api


text:
Track loading state per item page

Currently a new item just starts loading and replaces the previous one without notification once all necessary requests are done. This is not ideal as it makes it hard to know what is happening on the page currently after clicking on a new item if the request takes too long.
This can be solved by tracking all request on a page in a joint "loading" value and display a spinner during the loading process.

Closed in #59

repo: nam-pi/frontend


text:
Automatic anonymity-enforcing coin control

Once https://github.com/namecoin/electrum-nmc/issues/158 is implemented, we could make the commands that issue name transactions exclude coins that are already grouped with another name (unless the user approves it).  This would have the high-level effect of enforcing anonymity (at least against blockchain analysis) for name registrations, as long as the coins were obtained anonymously (e.g. by buying them with Monero).

Implementation-wise, seems like we could add a few lines to get_spendable_coins.  In particular, accepting an extra optional parameter only_linkable_names, and using that with the output of listaddressgroupings to filter self.frozen_addresses before we pass it to self.get_utxos seems like a pretty good approach.
I am hesitant to make this mode turned on by default, at least at first.  Maybe we could investigate making this the default behavior in the future, but for now I think it's okay to make this behavior opt-in.  braces for the angry horde of Monero community members telling me that opt-in privacy isn't privacy  We can discuss making it the default in a subsequent issue.

Anyone who wants to implement this, please contact me to coordinate.  :)

repo: namecoin/electrum-nmc


text:
security: Add ed25519 signer

Fix: #91

Validator is already there
https://github.com/named-data/ndnd/blob/be1788d1a2d201b668c53fab13213ed049b2a1d2/std/security/known-key-validator.go#L72-L80
Don't have a unit test for now (WIP), but it should work.

repo: named-data/ndnd


text:
groupRenderer does not work correctly

Describe the bug
I try to give some style to my group elements with a custom component (name, picture, etc), however, it does not seem to work correctly.

I create a template for the group:

function GroupItem ({person}) {
  return (

        {person.title}

  )
}

Then I put the groups in place:

<Timeline
              groups={employees}
              groupRenderer={() => <GroupItem person={employees} />)}

In the scenario above, nothing is shown, the data is not fetched correctly because person is an array instead of an object. So I try to loop through it in the scenario below:

I try this way, where I loop through the group, but it only repeats the first item in the array:

groupRenderer={() => employees.map(i => <GroupItem item={i} />)}

What is the solution? Do I do something wrong?
Expected behavior
The entire group should be shown on the timeline left side bar.
Library Version
"react-calendar-timeline": "^0.28.0"
Desktop (please complete the following information):

OS: [macOS Ventura]
Browser [Chrome]
Version [Version 108.0.5359.124 (Official Build) (arm64)]

Additional context
I use NextJS:
"next": "13.1.6",
"react": "18.2.0",

I solved this issue, if anyone wants to see how, this is the code:
Custom renderer component (this works whether you want to render a custom item component or a group component)
const CustomGroupRenderer = ({group}) => {
    return (

{group.title}

    );
  }

  export default CustomGroupRenderer;

Then just use it like this:
                            <Timeline
                              groups={filtered_employees}
                              groupRenderer={CustomGroupRenderer}
                              items={new_orders}
                              itemRenderer={CustomItemRenderer}
                              />

repo: namespace-ee/react-calendar-timeline


text:
Single server adapter renamed/moved

The adapter has been renamed to Ubuntu server adapter and moved to https://github.com/torfs-ict/nanobox-adapter-ubuntu. Could you update the links?
Thanks!

How's that?

Thanks @danhunsaker!

authors: danhunsaker kristoftorfs


text:
Add http keep alive for RPC callback. Fixes #1125

Assuming this is what https://github.com/nanocurrency/raiblocks/issues/1125 is referring to?
Not sure on the actual timeout value itself, should I make it configurable?

Not quite, the keepalive needed is at the HTTP level, not the TCP level as this PR sets.

2nd part is the http keep alive or am I in the wrong place altogether?
req->insert (boost::beast::http::field::connection, "keep-alive");
req->insert (boost::beast::http::field::keep_alive, "timeout=120");

The callback isn't a persistent connection, it makes a new connection on every observed block.

That tells the server that we support HTTP keepalive, except we don't, which would cause problems with servers that actually support HTTP keepalive.

Ahhh I get you, was looking for a quick issue from the list to get my feet wet, I guess this is not one :smiley:

authors: CathalT PlasmaPower cryptocode

repo: nanocurrency/raiblocks


text:
Repo reorganization

Moved library source files to its own folder
Add Nuproj projects to main solution
Add msbuild property to allow building Nuproj projects locally when GitVersion is not available
Add NuGet.config
Remove deprecated .nuget folder from solution
Drop solution specific for NuGets
Update CI scripts accordingly

Signed-off-by: nfbot nanoframework@outlook.com

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

authors: CLAassistant josesimoes


text:
pb_decode can't decode a tag with large numbers

Input value: 88d4c394a303862edd239fd0ec1c

cat test.proto
syntax = "proto2";
message Test {
optional uint32 f = 106044737;
optional fixed32 g = 571;
}

echo 88d4c394a303862edd239fd0ec1c | xxd -r -p | protoc --decode Test test.proto
g: 485281951
f: 5894

Decoding fails with nanopb because the varint32 decoder thinks there's been an overflow.

To me, this seems more like an invalid protobuf message which protoc just doesn't detect.
The number encoded in 88 d4 c3 94 a3 03 is 0x1a3290ea08 which gives a tag number of 14064688449, which is more than 536,870,911, which is the maximum in the specification. Google's implementation silently truncates this to 32 bits, while nanopb issues an error. Either behaviour seems fine to me, as protobuf is not really designed to reliably detect corrupted messages - one would use e.g. checksum for that purpose.
Also, if possible, please try to slow down your issue reporting pace. I'm pretty short on time that I can spend on nanopb nowadays, but I do not like to build a big queue of unanswered issue reports either.

My bad.  Thanks for the quick reply.

authors: PetteriAimonen vlovich

repo: nanopb/nanopb

license: Zlib


text:
Use subscribe API in React 18

https://github.com/reactwg/react-18/discussions/86
https://twitter.com/acemarke/status/1444736773142241285

Hi. Sounds like a really cool idea! I am selecting store for my work and it is a beautiful wrapper for asynchronous data loading - the only thing I would like in nanostores.
If it was +- compatible with how Recoil does it, it would be great. More about Facebook way: https://recoiljs.org/docs/guides/asynchronous-data-queries

The react wrapper of https://github.com/pmndrs/valtio (another state management library - somewhat similar to nanostores) also uses React Suspense to transparently allow async values in stores - as in suspends until the promise resolves.

Was used already https://github.com/nanostores/react/blob/main/index.js#L3

authors: IgnusG ai nikolay-govorov

repo: nanostores/nanostores


text:
feat(interactive-mode): Added option to enable support of inquirer plugins

Main changes

Added option to enable support of inquirer plugins, which defaults to false when not provided. As the result, this PR preserves  backward-compatibility.

Pinging @nanovazquez just in case, as it seems I cannot request a review :)

I was just about to create a PR with something like this in it.  Our use case is that we use various Inquirer plugins such as inquirer-fuzzy-path, etc. -- and because the existing code calls createPromptModule, any questions processed by Inquirer that were defined using yargs-interactive cannot use any modules that we have registered with Inquirer, even if we register them at the very top of the first file we load.
As far as backwards compatibility -- there's actually not even any real reason to use createPromptModule() at all in yargs-interactive, because yargs-interactive doesn't even call registerModule().  Even if it did. you only really need to use createPromptModule() if you are about to register other modules against inquirer and you don't want any other consumers of inquirer to be effected by your registerModule() call.  In practice, this only matters if you are about to override an existing inquirer prompt with something that has a different API than the original did.  If all you're doing is adding new modules, that would not be a breaking change anyway.
So IMO it would be perfectly safe to just remove L9 entirely (const prompt = inquirer.createPromptModule();) and just call inquirer.promp() directly.
@nanovazquez Is this project maintained anymore?

authors: MaximusHaximus TheOptimisticFactory

repo: nanovazquez/yargs-interactive


text:
Pin napalm-base driver

See details in the parent issue napalm-automation/napalm-base#107

Closing via https://github.com/napalm-automation/napalm-junos/pull/55

authors: dbarrosop mirceaulinic

repo: napalm-automation/napalm-junos


text:
Focus/jump to object selected of the currently selected label

Hi,
🚀 Feature
Option to focus/jump to the object of the currently selected label. The camera should center on the object and zoom in on it so that the object makes up X% of the view.
Motivation
Sometimes images have lots of labels that need to be corrected, but it is difficult to keep track on the progress. Being able to automatically jump to the next object in an instance segmentation, correct it and then jump to the next one, would make this task a lot easier.
Best,
Karol

Could You check if the Search Label widget from the PartSeg plugin does this job?
You could see a video with a presentation on napari hub https://www.napari-hub.org/plugins/PartSeg
(this plugin will not work with dask arrays)

Hi Czaki,
yes this is what I wanted. However, it would be nice if this could still be implemented in native napari.
I also noticed some issues with the Search Label widget sometimes not working, but I will open a separate issue there on the PartSeg repo.
Best,
Karol

As your description is a little laconic then having a working code is a good starting point.
Let's wait on one of the core dev team responses.
The biggest problem with moving my implementation into napari is that it uses C++ code for performance and napari itself is planned to be a pure python. So there needs to be made a decision if create a new package or add such code to one of a  package in the napari ecosystem.

The feature is certainly nice.  How much code did it take @Czaki?  Can you link to the implementation?

I ran into the same question and write this very short function which can be used in the napari console
in my version I had to jump only to the x and y coordinate and then to the first time point where the label appears but it should be very easy to adjust

import numpy as np

def center(label_number, viewer=viewer, label_layer=viewer.layers["your_label_layer"]):
    """Center the view on the given label number."""
    coordinates = np.argwhere(label_layer.data == label_number)
    if len(coordinates) == 0:
        print(f"Label {label_number} not found.")
        return

    # Find the minimum coordinates and the center
    min_coords = np.min(coordinates, axis=0) #for timepoint
    center_coords = np.mean(coordinates, axis=0) #for center coordinates

    # Set the camera center (x, y)
    viewer.camera.center = (center_coords[1], center_coords[2])  # (x, y) order

    # Set the first timepoint (z)
    viewer.dims.current_step = (int(min_coords[0]),) + viewer.dims.current_step[1:]

    # Set the selected label
    label_layer.selected_label = label_number
    print(f"Centered on label {label_number} at {center_coords}")

Usage:
    center(102)

Cool! Thanks for sharing!

authors: Czaki Karol-G XylotrupesGideon psobolewskiPhD tlambert03

repo: napari/napari


text:
Fix/add some typing to napari.layers.tracks

Adds/fixes some typing in napari.layers.tracks.

I am getting local test failures on Ubuntu, as well as the CI failures.

authors: GenevieveBuckley dstansby


text:
Would you please show me how to use single node multi-gpu mode?

Hi,
Thanks for your helpful tutorial, I am working on one machine with 2gpus, and I am also playing around torch.distributed. After studying carefully your code, I have tried to write one on myself. Here is a simplified version of my code:
import torch
import torch.nn as nn
import torch.nn.functional as F
import time

import argparse

def parse_args():
    parse = argparse.ArgumentParser()
    parse.add_argument(
            '--local_rank',
            dest = 'local_rank',
            type = int,
            default = -1,
            )
    return parse.parse_args()

class Net(nn.Module):
    def __init__(self):
        super(Net, self).__init__()
        self.conv1 = nn.Conv2d(3,
            64,
            kernel_size = 3,
            stride = 2,
            padding = 1,)
        self.conv2 = nn.Conv2d(64,
            256,
            kernel_size = 3,
            stride = 2,
            padding = 1,)
        self.conv3 = nn.Conv2d(256,
            19,
            kernel_size = 3,
            stride = 2,
            padding = 1,)
        self.linear = nn.Linear(512, 10)

    def forward(self, x):
        H, W = x.size()[2:]
        x = self.conv1(x)
        x = self.conv2(x)
        logits = self.conv3(x)
        logits = F.interpolate(logits, (H, W), mode='bilinear')
        return logits

def train():
    args = parse_args()

    torch.cuda.set_device(args.local_rank)
    torch.distributed.init_process_group(
                backend='nccl',
                init_method='env://',
                )
    net = Net()
    net.train()
    net.cuda()
    #  net = nn.DataParallel(net)
    net = nn.parallel.DistributedDataParallel(net,
            device_ids = [args.local_rank, ],
            output_device = args.local_rank
            )

    optim = torch.optim.SGD(
            net.parameters(),
            lr = 1e-3,
            momentum = 0.9,
            weight_decay = 5e-4)
    criteria = nn.CrossEntropyLoss()

    for i in range(10000):
        img = torch.randn(2, 3, 768, 768).cuda()
        lb = torch.randint(0, 18, [2,768,768]).cuda()
        optim.zero_grad()
        out = net(img)
        #  out = out.permute(0,2,3,1).contiguous().view(-1, 19)
        #  lb = lb.view(-1, )
        #  print(out.size())
        #  print(lb.size())
        loss = criteria(out, lb)
        loss.backward()
        optim.step()

if __name__ == "__main__":
    train()

by running: python -m torch.distributed.launch --nproc_per_node=2 main.py. I got weird error. Would you please show what mistake I have made?

@CoinCheung , Hi, I'm try to do the same thing, have you solve the problem?

@yzl96 Yes, please refer to this codebase.

repo: narumiruna/pytorch-distributed-example


text:
CCSDS header file macro CCSDS_INC_SEQ generates a compiler warning when referenced (GSFC DCR 22932)

The macro CCSDS_INC_SEQ defined in ccsds.h generates a compile time warning because it calls the macro CCSDS_WR_SEQ with 2 arguments.  The first argument is "phdr" which is ok, but the second argument is "CCSDS_RD_SEQ(phdr) + 1" which is not ok.  The problem is that the second argument results in code that looks like (x + 1 >> 8), which is unclear.
Putting "CCSDS_RD_SEQ(phdr) + 1" inside parens results in code that looks like ((x + 1) >> 8) which is ok.
Change macro CCSDS_INC_SEQ

from:
{{{
#define CCSDS_INC_SEQ(phdr) CCSDS_WR_SEQ(phdr, CCSDS_RD_SEQ(phdr)+1)
}}}
to:
{{{
#define CCSDS_INC_SEQ(phdr) CCSDS_WR_SEQ(phdr, (CCSDS_RD_SEQ(phdr)+1))
}}}

Imported from trac issue 106.  Created by sstrege on 2015-08-28T15:24:14, last modified: 2019-03-05T14:57:55

Trac comment by glimes on 2015-09-02 12:39:11:
More correct is to fix CCSDS_WR_SEQ to put parens around value
where it is used. Please note that all over this file we have
many cases of (phdr). recognizing that parameters might be
expressions; this is acually a '''very common coding rule'''.
We should go into ccsds.h and fix all of the value >> n
and value << n expressions to put value in parementheses.

Trac comment by sstrege on 2016-03-06 16:11:39:
Pushed commit [changeset:e30f97a] for CCB review

Trac comment by jhageman on 2019-03-05 14:57:55:
Milestone renamed

Trac comment by glimes on 2016-03-09 15:15:38:
This change is being accepted via the ic-2016-03-08 merge.
Review of this ticket spawned additional discussion about a better
approach which unfrotunately requires more time. Ticket #172 will track
this effort separately going forward.

repo: nasa/cFE


text:
No Success Test and Boundaries for CFE_TBL_ReleaseAddresses

Is your feature request related to a problem? Please describe.
From #548. No Success Test for CFE_TBL_ReleaseAddresses. No test on boundary conditions for NumTables.
Describe the solution you'd like
Add a success test for CFE_TBL_ReleaseAddresses in cFE/modules/tbl/ut-coverage/tbl_UT.c. Test boundary conditions for NumTables.
Requester Info
Ariel Adams, ASRC Federal

I'll work on this.

authors: ArielSAdamsNASA nmullane


text:
Table decompression

Is your feature request related to a problem? Please describe.
Compressed tables could save space in NV-RAMs.
Describe the solution you'd like
The decompression feature (implemented already for apps) can be extended to tables.
Describe alternatives you've considered
None.
Additional context
N/A
Requester Info
Onur TURHAN

table_decompression.diff.txt

This will require some community discussion - this decompress for apps is being considered for removal as it has been identified as a (possibly) un-required feature.
The problem is that the decompress happens to a RAMDISK so you simply trade a slight NVRAM savings for significant increase in RAM use, as the table is now effectively loaded into RAM twice.  In many flight systems the RAM is just as constrained, if not more so, than the NVRAM storage.
Can you identify a specific use case for this (i.e. a flight computer where the NVRAM is constrained such that this would be a requirement)?

Note that the decompression functionality is transitioning out of cFE to a library (likely called FS_lib), so the FM app will retain it's capability to decompress (and actually untar is also getting added).  The dependency of cFE on decompress is being removed, so "automatic" decompression as part of load isn't supported.
The plan is to continue to support decompress with FM, then you can load the app/lib/table.  It just won't be automatically done within cFE.  The use case for us is to handle transferring many large tables to a cFS based system as tar.gz, then decompressing and untaring on board.
A major motivation of moving decompress (and untar) into a library is to make it easier for users to replace with whatever decompression algorithm they'd like.

There could be two requirements actually,

flight computer where the NVRAM is constrained.
Yes, actually I encountered two times NVRAM/RAM size rate as 1/4, so at least projects that I work have such a situation.

size reduction important for also uplink. There are requirements for LEO satellites like updating all applications in one pass, so this requires more uplink rate if there is no compression.

As an example 270KB CF(CFDP App) (rtems/sparc,stripped) task could be zipped to 70KB (26% compression rate). This is usually better for tables due to repetitive parts like Space Packet Header (ex;sch_def_msgtbl). In projects, I have encountered an average ~1/10 compression rate for tables. Also, ATS and RTS tables loaded daily to some spacecraft, so 1/10 compression is very good for effective operational time usage.
On the other hand, implementing this feature with FM will cause at least three constraints or situations in order to load compressed lib, app and tables.

FM app and its tables (or FS_lib) should not be compressed.

FM app (or FS_lib) should be loaded with any other compressed tasks (with related tables).

ES app should send a command to FM app before loading apps, or TBL app should send a command to FM app before loading the tables. Or maybe ES & TBL will use FS_lib functions after loading FS_lib.
So circular dependency between CFE-CORE apps and FM app or FS_lib.

IMHO, FM app should have compression and decompression features. Especially, file compression will be very useful for DS app output files. However, compression & decompression functions can be implemented in OSAL(FS), since some operating systems have these features inherently (posix,rtems). There could be some flag to disable this feature for unsupported RTOS. ES and TBL apps could use these functions to load zipped app, libs, tables, if RTOS supports. FM can use OSAL functions or any other loaded comp-decomp library like FS_lib with hooks or options.

FM app and its tables (or FS_lib) should not be compressed.

True (along with the core).

FM app (or FS_lib) should be loaded before any other compressed tasks (with related tables).

True.

ES app should send a command to FM app before loading apps, or TBL app should send a command to FM app before loading the tables. Or maybe ES & TBL will use FS_lib functions after loading FS_lib. (Assumption: cfe_es_startup.scr is used to load all apps.)
So circular dependency between CFE-CORE apps and FM app or FS_lib.

Plan is FM would need to decompress before the load command to ES.  ES would not have any linkage to decompress or FM.  Could be a scripted set of startup commands.  Compressed file system is also a valid approach for operating systems that support it(below the cFS level).

IMHO, FM app should have compression and decompression features. Especially, file compression will be very useful for DS app output files.

Decompress is being maintained in FM app.  Compression (as a library addition) could certainly be considered, and I encourage open source contribution of a cFS/Flight friendly implementation.

However, compression & decompression functions can be implemented in OSAL(FS), since some operating systems have these features inherently (posix,rtems).

Note that built in support is frequently not flight software friendly (recursive, unbounded timing, dynamic memory use, non-portable, etc).  There is the shell command from ES already if you want to evoke built in tools on a supporting OS.

There could be some flag to disable this feature for unsupported RTOS. ES and TBL apps could use these functions to load zipped app, libs, tables, if RTOS supports. FM can use OSAL functions or any other loaded comp-decomp library like FS_lib with hooks or options.

Planned approach is to abstract via FS_lib, and maintain a common set of API's and allow projects to easily swap out for other implementations.

authors: jphickey onurturhan skliper


text:
Fix #1685, Add table registration functional tests

Describe the contribution
A clear and concise description of what the contribution is.

Fixes #1685
Adds functional unit tests for

CFE_TBL_Register
CFE_TBL_Share
CFE_TBL_Unregister

Testing performed
Steps taken to test the contribution:

Build CFE and run all functional tests

Expected behavior changes
A clear and concise description of how this contribution will change behavior and level of impact.

no impact to behavior

System(s) tested on

Hardware: PC
OS: Ubuntu 20.04

Contributor Info - All information REQUIRED for consideration of pull request
Niall Mullane - GSFC 582 Intern

Combining this PR with additional table api functional tests into #1734


text:
Integrate R2 SAS Final Point Releases

Ticket to track integration of the latest point releases for the R2 SAS.
Completion of this ticket should culminate with a new R2 PGE release that bundles the updates for both SAS.

Addressed by #422

repo: nasa/opera-sds-pge


text:
[Processing Request]: OPERA RTC-S1 for Dist-S1 R&D

Venue
PST
Product
RTC-S1
SAS Version
No response
SDS Version
No response
Input Data
This is a specific request for generating time-series of a given bursts that overlaps 300 sites around the globe.
The relevant table is here: https://github.com/OPERA-Cal-Val/dist-s1-research/blob/dev/marshak/3_dist_sites/slcs_for_processing.csv.zip
In terms of processing, the relevant information in the table is: (s1_slc_id, burst_id) --> (uniquely) JPL burst RTC-S1 product
This amounts to approximately 2 TBs of data assuming there is about ~30 MBs files per burst product generate (though is an overestimate I believe).
Share Results

[ ] Google Earth Engine (GEE)
[ ] NASA Distributed Active Archive Centers (DAAC) User Acceptance Testing (UAT)

Additional Notes
If you do not have the capability to limit to specified burst, we will need to talk as this generates orders of magnitude more data.

Would like to process a few bursts in the list and see them delivered to UAT before proceeding to the entire list.

@niarenaw and @LucaCinquini - we have updated the request.
The SLCs span a subset of sites and only go from 2020-10-01 to 2022-12-01 (a little over 2 years).
There should be 8,703 SLCs in https://github.com/OPERA-Cal-Val/dist-s1-research/blob/dev/marshak/3_dist_sites/slcs_for_processing.csv.zip. The request will cost ~$3,050 based on Nick's estimate of $0.35 / SLC.
Let me know if there are any questions.

All SLCs processed except the following:
S1A_IW_SLC__1SDV_20221117T060948_20221117T061015_045930_057EE2_89A5 S1A_IW_SLC__1SDV_20221117T153336_20221117T153403_045936_057F16_AD44 S1A_IW_SLC__1SDV_20221117T153516_20221117T153543_045936_057F16_AB2D S1A_IW_SLC__1SDV_20221117T171630_20221117T171657_045937_057F23_824A
Further investigation needed on why these can't be downloaded from ASF.

Has to be a transient error.
I was able to download the first one through the search GUI in the browser:
https://search.asf.alaska.edu/#/?searchType=List Search&searchList=S1A_IW_SLC__1SDV_20221117T060948_20221117T061015_045930_057EE2_89A5&resultsLoaded=true&granule=S1A_IW_SLC__1SDV_20221117T060948_20221117T061015_045930_057EE2_89A5-SLC

Products should be complete now.

Thanks, Nick!

authors: cmarshak niarenaw

repo: nasa/opera-sds


text:
Github link provided is for auto annotater.

Github link provided to convert Yolo label txt files to JSON is auto annotater. I didn't find way to convert into JSON. Correct me If I am wrong.

Hi @suku47 ,
https://github.com/naseemap47/autoAnnoter/tree/master/tools#10-yolo_to_jsonpy
this will convert Yolo label txt files to JSON.
If any issues, please let me know


text:
No way to pass free arguments to a specific place

With shell scripts, it's possible to do something like: python -m robot --pythonpath . -d ./outptut "$@" tests, so that when you call a script, the passed arguments are forwarded to the command in a specific location.
However with poe a task like:
[tool.poe.tasks.test]
help = "Run all tests"
cmd = "python -m robot --pythonpath . -d ./output ./tests"

Any passed arguments will simply be appended to the end of the command. This isn't ideal, as some CLI tools only support usage like: robot [options] paths, which means any positional arguments left after the options are interpreted as paths. This means that running for example: robot --pythonpath . ./tests -d ./output wouldn't work, and I'd get an error that it couldn't find -d as a path.
I'd love to see a feature that would allow for me to pass arguments to a specific place in my command.

Hi @ItsDrike,
I agree this is an issue, but I've not managed to find a good solution yet. One difficulty is that I haven't found a robust way to pass arguments to a shell child process (to populate $@ within the shell) where the script content is being passed via stdin (which is how shell tasks work). Rethinking shell tasks as discussed in #64 might help, but that's a way off on the roadmap.
Thinking allowed here, maybe just having a way to capture extra arguments (either when there are no args defined, or when provided after the -- on the command line) and being able to specifically inject them at a certain point in a command rather than append them to the end is all that's needed? Need to think this through a bit...
I'm open to ideas.
That said, one imperfect solution that might just work for you is to define a positional arg on your task that accepts multiple values. For example given a task like:
[tool.poe.tasks.show-args]
cmd = """
python -c "import sys; print(sys.argv[1:])" being $all_args end
"""
args = [{ name = "all_args", positional = true, multiple = true }]

And a command like:
poe show-args middle "multiple words" -- and then some

The result will be:
Poe => python -c import sys; print(sys.argv[1:]) being middle multiple words end and then some
['being', 'middle', 'multiple', 'words', 'end', 'and', 'then', 'some']

A couple of points to pay attention to:

you can also accept multiple values for cli options, but args multiple must come first in the command. Accepting multiple values for multiple args gets complicated quickly
the multiple values are essentially just passed as a whitespace delimited string which is then lexed into multiple words inside the task. If you don't want this then put quotes around the "${variable}" just like in a normal POSIX shell.

I was hoping to migrate from Makefile to a better tool and found this library.
I found a similar limitation with regards to running command inside a docker container. For example when running Django commands, I have to do docker-compose run --rm server bash -c "python manage.py makemigrations" but most of the commands need extra arguments to be passed. This is not possible with the tool because we need to put the command inside quotes/double quotes.
I also used go-tasks for a while and I think I am looking for something similar to {{.CLI_ARGS}} (https://taskfile.dev/usage/#forwarding-cli-arguments-to-commands)

I agree that poe should have a way to do this.
You can put arguments in an environment variable and use it wherever the arguments are going to be passed:
[tool.poe.tasks.test]
sequence = [
    { cmd = 'pytest $TEST_ARGS' },
    { cmd = 'some other command' }
]

TEST_ARGS="-n auto" poe test
Which isn't very elegant but at least it works.

authors: ItsDrike merlinz01 nat-n roniemartinez

repo: nat-n/poethepoet


text:
reCaptcha Website Help

So I went into the reCaptcha v2 Website and I followed all of you instructions but at the end it asked me for the public-key? But the website gave me a site key and a secret key. I was confused at that point what I should do. And it said if you are using a domain put it in the config.json but the website forces you to use a domain or else it wont create so please help me fix some errors. number 1 error - the public key and private key, number 2 - Should me domain be like name.com or something and my bot gives me a invalid site so please help!

If you are hosting on your local computer set the domain to 127.0.0.1, if not use your domain. When I said public key, I meant site key.

So Nate for the domain should it be like localhost:127.0.0.0? and for the config.json "domain": "localhost:127.0.0.1" should it be this?

And Im Hosting The Bot on repl.it. So what do i do?

It should be, "domain": "127.0.0.1", but if you are using repl.it, they will give you a domain to use (google: how to find repl.it project domain)

im confused now can you dm me on discord? Discord is - Spike I AM TOY#1699

@nates

Mr Nates can you please help! I have a issue

MR NATEEEEE REEEEEEEEEEEEEE. So Basically WTF DO I DO???. So I go to reCaptcha Website what should I put as my domain???

IM CONFUSED BY YOUR TUTORIAL BRUH

Put the domain as the repl.it domain

so it needs to connect right?

I got the repl.it domain. But it said enter your domain so I entered 127.0.0.1

is that right?

Do you know your repl.it domain?

yes I just got it

but I get an error

Use that on recaptcha and the config

when I open the website

nates can you dm me on discord

I am quite unclear

nates???

my guy left me lmao

I sent you a friend request

authors: ProHyphonzDaCoder nates

repo: nates/ward


text:
Correct phone numbers are considered invalid

All Moroccan numbers that start with something other than 6 after +212 are considered invalid meanwhile they are valid
await PhoneNumberUtil.isValidPhoneNumber("600000000", "MA"); // true

await PhoneNumberUtil.isValidPhoneNumber("500000000", "MA"); // false
await PhoneNumberUtil.isValidPhoneNumber("700000000", "MA"); // false
await PhoneNumberUtil.isValidPhoneNumber("+212700000000", "MA"); // false
await PhoneNumberUtil.isValidPhoneNumber("0700000000", "MA"); // false

I confirm to have the same issue

authors: anassrakibi rabraghib


text:
Can you create example for Angular? I get error -  TypeError: Cannot read properties of undefined (reading 'nativeElement')

this is my page
  <StackLayout orientation="horizontal">
            <canvasView #canvas width="300" height="300" style="border-width: 1; border-style: solid; border-color: red;" (draw)="draw($event)" (tap)="canvasTap()" />
  </StackLayout>

this is code
   export class ItemDetailComponent implements OnInit {

     @ViewChild("canvas", { static: false }) canvasElementRef: ElementRef<CanvasView>;
     canvas:CanvasView;

     ngOnInit(): void {
       registerElement('CanvasView', () => CanvasView);
       this.canvas=this.canvasElementRef.nativeElement
     }

     canvasTap(){
         this.canvas.backgroundColor = "green"
     }
   }

line "this.canvas=this.canvasElementRef.nativeElement" produced error: TypeError: Cannot read properties of undefined (reading 'nativeElement'). Without this line there is nothing reference to nativeElement and nothing showing on page.
Where is mistake?

@AAlex-11 there is an example in the doc https://github.com/nativescript-community/ui-canvas?tab=readme-ov-file#nativescript--angular
as for  this.canvas=this.canvasElementRef.nativeElement it is an angular issue not related to this plugin.

thank for answer, @farfromrefug I use a couple of your modules, it working fine, for example gesture module,
but I still don't understand how to use this Canvas

Hm... canvasElementRef.nativeElement - working fine with any other native Android component
and I don't see in this CanvasView any meaningful Android methods https://developer.android.com/reference/android/graphics/Canvas, for example drawARGB

@AAlex-11 if you go in the draw event then it is working. now i dont know what event.Proxy is supposed to be but it does not come from that plugin
Here is a vue example of how it works https://github.com/nativescript-community/ui-canvas/blob/master/demo-snippets/vue/Simple.vue#L24. CanvasView does not expose Canvas methods. Those methods are on the Canvas object you get from the event

Thank you. Your example code is working with Angular.

@AAlex-11 you need to pass the bitmap/imageSource on Canvas creation as you would on Android (native). In the case of canvasview you cant as it is not a normal Canvas (RecordingCanvas). You need to search on the web on how to get image from view "screenshot"

repo: nativescript-community/ui-canvas


text:
Formally review "new" feature request template

Proposed Changes
It still says July 2021. Let's just commit to it.

Justification
We have two "feature request" items in our new issue templates. It's a little confusing, especially since it's November!

[ ] It should have a "Overview" section at the top for a brief description?
[ ] Get rid of the July 202/beta stuff.
[ ] Drop old feature request template

repo: nautobot/nautobot


text:
Support for EOS enable_password

Environment

Python version: Python 3.8.10
Nautobot version: 1.2.3

Steps to Reproduce

Try to connect with NAPALM to an ARISTA (arista_eos) equipment with eos driver, with "secret" argument (text or environment variable) in GUI.
"secret" argument is not working, we need to use "enable_password" argument, but it seems not possible in GUI. Only with a napalm shell command.

Here the result with "secret" argument (we have the same issue on GUI, with TEXT or Environment variable):
root@xxxx:/opt/nautobot# napalm --vendor eos --user admin --password xxx --optional_args "secret='pas
sword'" xx.xx.xx.xx --debug
2022-01-21 09:46:45,649 - napalm - DEBUG - Starting napalm's debugging tool
2022-01-21 09:46:45,649 - napalm - DEBUG - Gathering napalm packages
2022-01-21 09:46:45,649 - napalm - DEBUG - napalm==3.3.1
2022-01-21 09:46:45,649 - napalm - DEBUG - get_network_driver - Calling with args: ('eos',), {}
2022-01-21 09:46:45,649 - napalm - DEBUG - get_network_driver - Successful
2022-01-21 09:46:45,650 - napalm - DEBUG - init - Calling with args: (<class 'napalm.eos.eos.EOSDriver'>, 'xx.xx.xx.xx', 'admin'), {'password': '*******', 'timeout': 60, 'optional_args': {'secret': 'xxx'}}
2022-01-21 09:46:45,650 - napalm - DEBUG - init - Successful
2022-01-21 09:46:45,650 - napalm - DEBUG - pre_connection_tests - Calling with args: (<napalm.eos.eos.EOSDriver object at 0x7f5274ccd100>,), {}
2022-01-21 09:46:45,650 - napalm - DEBUG - open - Calling with args: (<napalm.eos.eos.EOSDriver object at 0x7f5274ccd100>,), {}
2022-01-21 09:46:45,776 - napalm - ERROR - open - Failed: 'errors'
================= Traceback =================
Traceback (most recent call last):
File "/usr/local/bin/napalm", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.8/dist-packages/napalm/base/clitools/cl_napalm.py", line 308, in main
run_tests(args)
File "/usr/local/lib/python3.8/dist-packages/napalm/base/clitools/cl_napalm.py", line 283, in run_tests
call_open_device(device)
File "/usr/local/lib/python3.8/dist-packages/napalm/base/clitools/cl_napalm.py", line 27, in wrapper
r = func(*args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/napalm/base/clitools/cl_napalm.py", line 207, in call_open_device
return device.open()
File "/usr/local/lib/python3.8/dist-packages/napalm/eos/eos.py", line 167, in open
sh_ver = self.device.run_commands(["show version"])
File "/usr/local/lib/python3.8/dist-packages/napalm/eos/pyeapi_syntax_wrapper.py", line 42, in run_commands
return super(Node, self).run_commands(commands, *args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/pyeapi/client.py", line 771, in run_commands
response = self._connection.execute(commands, encoding, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/pyeapi/eapilib.py", line 554, in execute
response = self.send(request)
File "/usr/local/lib/python3.8/dist-packages/pyeapi/eapilib.py", line 465, in send
(code, msg, err, out) = self._parse_error_message(decoded)
File "/usr/local/lib/python3.8/dist-packages/pyeapi/eapilib.py", line 516, in _parse_error_message
err = ' '.join(message['error']['data'][-1]['errors'])
KeyError: 'errors'

Expected Behavior
We expected the same result as we have in command line :
root@xxx:/opt/nautobot/device_passwords/xxx# napalm --vendor eos --user admin --password xxx --optional_args "enable_password='xxx'" xx.xx.xx.xx --debug
2022-01-20 17:34:48,878 - napalm - DEBUG - Starting napalm's debugging tool
2022-01-20 17:34:48,878 - napalm - DEBUG - Gathering napalm packages
2022-01-20 17:34:48,878 - napalm - DEBUG - napalm==3.3.1
2022-01-20 17:34:48,878 - napalm - DEBUG - get_network_driver - Calling with args: ('eos',), {}
2022-01-20 17:34:48,878 - napalm - DEBUG - get_network_driver - Successful
2022-01-20 17:34:48,878 - napalm - DEBUG - init - Calling with args: (<class 'napalm.eos.eos.EOSDriver'>, 'xx.xx.xx.xx', 'admin'), {'password': '*******', 'timeout': 60, 'optional_args': {'enable_password': 'xxx'}}
2022-01-20 17:34:48,878 - napalm - DEBUG - init - Successful
2022-01-20 17:34:48,878 - napalm - DEBUG - pre_connection_tests - Calling with args: (<napalm.eos.eos.EOSDriver object at 0x7f60e5bd3f70>,), {}
2022-01-20 17:34:48,878 - napalm - DEBUG - open - Calling with args: (<napalm.eos.eos.EOSDriver object at 0x7f60e5bd3f70>,), {}
2022-01-20 17:34:48,957 - napalm - DEBUG - open - Successful
2022-01-20 17:34:48,957 - napalm - DEBUG - connection_tests - Calling with args: (<napalm.eos.eos.EOSDriver object at 0x7f60e5bd3f70>,), {}
2022-01-20 17:34:48,957 - napalm - DEBUG - get_facts - Calling with args: (<napalm.eos.eos.EOSDriver object at 0x7f60e5bd3f70>,), {}
2022-01-20 17:34:49,027 - napalm - DEBUG - Gathered facts:
{
"hostname": "xxx",
"fqdn": "xxx",
"vendor": "Arista",
"model": "vEOS-lab",
"serial_number": "27A0AF893A21170CF9CB2D451D365435",
"os_version": "4.26.3M-24689762.4263M",
"uptime": 190279,
"interface_list": [
"Ethernet1",
"Ethernet2",
"Ethernet3",
"Loopback1",
"Management1",
"Vlan10"
]
}
{
"hostname": "xxx",
"fqdn": "xxx",
"vendor": "Arista",
"model": "vEOS-lab",
"serial_number": "27A0AF893A21170CF9CB2D451D365435",
"os_version": "4.26.3M-24689762.4263M",
"uptime": 190279,
"interface_list": [
"Ethernet1",
"Ethernet2",
"Ethernet3",
"Loopback1",
"Management1",
"Vlan10"
]
}
2022-01-20 17:34:49,027 - napalm - DEBUG - get_facts - Successful
2022-01-20 17:34:49,027 - napalm - DEBUG - close - Calling with args: (<napalm.eos.eos.EOSDriver object at 0x7f60e5bd3f70>,), {}
2022-01-20 17:34:49,028 - napalm - DEBUG - close - Successful
2022-01-20 17:34:49,028 - napalm - DEBUG - post_connection_tests - Calling with args: (<napalm.eos.eos.EOSDriver object at 0x7f60e5bd3f70>,), {}

Observed Behavior
We get an error, whether we use a text file or by an environment variable  :
{"detail":"Error connecting to the device at xx.xx.xx.xx: 'errors'"}
As discuted with your dev team on Slack, "enable_password" argument is not implemented on the GUI, only "secrets" argument, but it's not working for eos_arista equipments.

Resolved (temporary)
We modified this file : /opt/nautobot/lib/python3.8/site-packages/nautobot/dcim/api/views.py
It's well working now with Junos and EOS.
        # Get NAPALM enable-secret from the device if present
        # EOS driver exception
        enable_password_name = ""
        if device.platform.napalm_driver == "eos":
            enable_password_name = "enable_password"
        else:
            enable_password_name = "secret"
        print(enable_password_name)
        if device.secrets_group:
            try:
                optional_args[enable_password_name] = device.secrets_group.get_secret_value(
                    SecretsGroupAccessTypeChoices.TYPE_GENERIC,
                    SecretsGroupSecretTypeChoices.TYPE_SECRET,
                    obj=device,
                )
            except ObjectDoesNotExist:
                # No defined secret, this is OK
                pass
            except SecretError as exc:
                raise ServiceUnavailable("Unable to retrieve device credentials: {exc.message}") from exc

Thanks for the submission @pierre-marie-esposito! Looks like we could fix this pretty close to how you implemented your patch locally, however we will see if we can address this upstream as that seems to be a miss on NAPALM.

authors: bryanculver pierre-marie-esposito


text:
🛑 Harmony Bot Website is down

In 102f83a, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 33f824c.


text:
🛑 Harmony Backup Bot is down

In 8b8d0b5, Harmony Backup Bot ($HARMONY_BACKUP) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Backup Bot is back up in c35a581.


text:
🛑 Harmony Bot Website is down

In a8aa66c, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in ab0aaf5.


text:
🛑 Harmony Bot Website is down

In 380b117, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 168d735.


text:
🛑 Harmony Bot Website is down

In 7e16f53, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 72e4d65.


text:
🛑 Harmony Bot Website is down

In 3fa765c, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in ca15c95.


text:
🛑 Harmony Bot Website is down

In 32ac3ca, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 3bc05d0.


text:
🛑 Harmony Backup Bot is down

In 1b7f309, Harmony Backup Bot ($HARMONY_BACKUP) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Backup Bot is back up in 5042eaa.


text:
TEST: Add a distributed packet test about long key in UDP

UDP 프로토콜 테스트에서 long key에 대한 response 메시지 구성 시
패킷이 분배되어 UDP 헤더 인덱스가 1 이상으로 증가하는 경우에 대한 테스트를 추가합니다.
UDP 프로토콜 사용시 UDP_MAX_PAYLOAD(1400 Byte)를 초과하는
Response 메시지를 구성할 경우 UDP_MAX_PAYLOAD 크기로 나눈 다음
UDP 헤더를 구성하여 송신합니다.
현재 존재하는 udp 테스트에서는 UDP_MAX_PAYLOAD를 초과하여 Response 메시지를 구성하는 경우에 대한 테스트가 존재하지 않으므로,
이후 이루어질 udp 헤더에 대한 좀더 정학한 테스트를 위해 추가했습니다.
참조
테스트 개수가 9개가 증가한 이유

"abcd" x 1024 에 대한 Response 메시지(대략 4096 Byte)를 구성하므로 UDP_MAX_PAYLOAD(1400 Byte) 기준으로 3개의 Packet으로 나누어져 전송하게 되며, 각각의 패킷에 대하여 총 3번의 valid 검사를 수행합니다.
udp 테스트는 ASCII, Binary 프로토콜에 대해 각각 수행하므로 3x2번 총 6번의 Packet valid 테스트가 수행됩니다.
get 테스트의 경우 ASCII에서는 1번의 테스트, Binary에서는 status 검사 및 Value에 대한 테스트 총 2번의 테스트가 수행됩니다.
3 x 2 + (2 + 1) = 9번의 테스트가 수행됩니다.

변경에 대한 설명을 더 추가해 주면 좋겠습니다.

@namsic
수정되었습니다.

authors: ing-eoking namsic

repo: naver/arcus-memcached


text:
chore(demo): add syncronize demo

Issue
Ref #263
Details
add syncronize demo

Coverage remained the same at 93.729% when pulling 4c83ee37bdf6acffe563ecbd2cfbc27736b3b3fa on jongmoon:3.2.0-rc into cee43e12f3a66da93d2864cf0ff04f09074ae5a2 on naver:3.2.0-rc.

authors: coveralls jongmoon


text:
Delete bar items

Adds the ability to delete bar items

Hi @Topvennie
Thanks for the PR, can u sign your commits and fix the golangci failure.
Regards

Hi @Topvennie
Thanks for the PR, CI test is showing two failure. can you please:

Sign your commits
Fix golang-ci lint issue

Regards

@navidys
I've fixed the linting issue and signed my commit by using `git commit -S -m "..."

Hi @Topvennie
Still the DCO check is failing, did u sign all three commits ?
Maybe u can squash all the commits and only have one signed commit.
Regards

authors: Topvennie navidys

repo: navidys/tvxwidgets


text:
Legg til metadata for å skille på bruk av menyer

Vi kategoriserer alle lenkeklikk idag med "navigere".
Vi trenger å kunne skille på bruk av ulike menyer på sidene som

Header
Footer
Side-meny på produktsider, f.eks Utvidet barnetrygd
Paneler og grupper med paneler for livssituasjoner som på forsiden

Vi bruker både kategori og komponent idag som attributt, og vi bruker de til det samme, så vi bør holde oss til kun én av disse. Jeg foreslår å fjerne kategori.
Forslag
Trykk på lenke i header-meny
event-navn: navigere
komponent: header
lenketekst: Ditt NAV
destinasjon: https://www.nav.no/person/dittnav/
Trykk på lenke i footer-meny
event-navn: navigere
komponent: footer
lenketekst: Kontakt oss
destinasjon: https://www.nav.no/person/kontakt-oss/nb
Trykk på sidemeny på produktside
event-navn: navigere
komponent: sidemeny
lenketekst: Kort om utvidet barnetrygd
destinasjon: #kort

Tenker vi kan legge til innholdsmenyen på situasjonssiden (tilsvarende innholdsmenyen på produktsiden)

authors: TuvaSverdstad tobiasmcvey

repo: navikt/nav-enonicxp-frontend


text:
Fix documentation & initializer typos

Pauseable isn't an option. Pausable is the available one.

[X] Fix the option in the documentation
[X] Fix pausable? option in the initializer
[X] Fix initializer type? options' color

Thank you very much ♥

repo: nawafscript/toaststrap


text:
Provide the access to processTouch

Will allow for the user to set their own touch listener with its own behaviour, while also maintaining the original functionality and not just overriding the original touch listener

Bump


text:
Bug in detrending of epoched data

There seems to be a bug in the detrending function. When i use it on two raw (two dimensional) data, the result is as expected but when I use it on epoched data, the result is very strange - probably there is an issue with reshaping the matrix, see my example below:
import numpy
from matplotlib import pyplot as plt
from meegkit.detrend import detrend

time = numpy.arange(0, 10, 0.01)

# on raw data the detrending works as expected:
X = numpy.zeros([len(time), 3])
X[:, 0], X[:, 1], X[:, 2] = numpy.sin(time)+5, numpy.sin(time), numpy.sin(time)-5

X += numpy.random.randn(X.shape[0], X.shape[1])

fix, ax = plt.subplots(2)
for x in X.T:
    ax[0].plot(time, x)
X, _, _ = detrend(X, 1)
for x in X.T:
    ax[1].plot(time, x)

# but on epoched data the result looks strange:
X = numpy.zeros([len(time), 3, 100])
X[:, 0] = numpy.repeat(numpy.sin(time)[:, numpy.newaxis], 100, axis=1)+5
X[:, 1] = numpy.repeat(numpy.sin(time)[:, numpy.newaxis], 100, axis=1)
X[:, 2] = numpy.repeat(numpy.sin(time)[:, numpy.newaxis], 100, axis=1)-5
X += numpy.random.randn(X.shape[0], X.shape[1], X.shape[2])

fix, ax = plt.subplots(2)
for x in X.mean(axis=2).T:
    ax[0].plot(time, x)
X, _, _ = detrend(X, 1)
for x in X.mean(axis=2).T:
    ax[1].plot(time, x)

@OleBialas Hi, thanks for letting me know ! I've never really used the technique on epoched data. I will look into it in the next days.

I've been thinking about this issue, and I wonder what the correct behaviour should be for epoched data.
I don't think the detrending function should handle 3D data, unless the epochs are assumed to be consecutive (which the current code already handles well I think)
The most straightforward solution in your case is to handle each epoch separately, but that's equivalent to calling detrend on each epoch in a loop.
What I should do is add a warning to the docstring such as Warning: if 3D data are provided, epochs are assumed to be consecutive

I think you are right, I came to the conclusion that, in my case, there is not much of a point in using detrend on the epochs anyways so I just went with using it on the raw data.

authors: OleBialas nbara

repo: nbara/python-meegkit


text:
🛑 NBB is down

In b18038b, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 593 ms

Resolved: NBB is back up in f3a8958.

repo: nbbrd/sdmx-upptime


text:
🛑 ESTAT is down

In 0ad4e87, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in d31f6e6 after 6 minutes.


text:
🛑 ESTAT is down

In 1af55bf, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in e22feea after 8 minutes.


text:
🛑 ISTAT is down

In 895ae71, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 1ee4453 after 5 minutes.


text:
🛑 NBB is down

In f40cefc, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 567 ms

Resolved: NBB is back up in 81268ae after 2 hours, 9 minutes.


text:
🛑 ISTAT is down

In 79f8b67, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 36a8639 after 5 minutes.


text:
🛑 ISTAT is down

In bf41fb2, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in bce24ba after 4 minutes.


text:
🛑 ESTAT is down

In 1b33baa, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in cf92851 after 17 minutes.


text:
🛑 ISTAT is down

In 8274f82, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 5bfd215 after 6 minutes.


text:
🛑 NBB is down

In f279aa2, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 476 ms

Resolved: NBB is back up in c2bffb9 after 7 minutes.


text:
🛑 ISTAT is down

In 1739f1c, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 84ef600 after 34 minutes.


text:
🛑 ESTAT is down

In 1a05271, ESTAT (http://ec.europa.eu/eurostat/SDMX/diss-web/rest/dataflow/ESTAT/all/latest/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in e74eb8a.


text:
🛑 NBB is down

In 04ea52b, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 784 ms

Resolved: NBB is back up in c1031c2.


text:
🛑 ESTAT is down

In b30e3ed, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in d6926d8.


text:
🛑 ESTAT is down

In 3fc0943, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 265e90b.


text:
🛑 ESTAT is down

In 048e10c, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in c4a18dd.


text:
Create Posts “followgraph-un-outil-pour-découvrir-des-comptes-à-suivre-sur-mastodon”

Automatically generated by Netlify CMS

👷 Deploy Preview for shiny-babka-998c7e processing.

Name
Link

🔨 Latest commit
f2d91fdc85ae194e7af0b84881516977dd1e3bb5

🔍 Latest deploy log
https://app.netlify.com/sites/shiny-babka-998c7e/deploys/642bcfe61708390008df02b0


text:
Add security rule: open port 6066 from client

This PR makes the following changes:

open port 6066 from client, to allow '--deploy-mode cluster' when submitting jobs

I tested this PR by submitting a spark job from a remote client (a host that does not belong to the spark cluster) : spark-submit --deploy-mode cluster --master spark://host:6066

Thanks for the PR @dm-tran.
How does this relate to #103? I thought port 7077 was the Spark master port.

I couldn't find mention of port 6066 anywhere in the docs, but I did find this line which seems to suggest the port is for a REST server.
Is that required for spark-submit --deploy-mode cluster to work from a remote client?

Port 7077 is used with '--deploy-mode client' (which is the default deploy-mode).
Port 6066 is used with '--deploy-mode cluster' and Spark's REST API (http://arturmkrtchyan.com/apache-spark-hidden-rest-api).
The main page of Spark UI (http://master-host:8080/) lists both ports :
URL: spark://host:7077
REST URL: spark://host:6066 (cluster mode)

Interesting. Thanks for the link!

authors: dm-tran nchammas

repo: nchammas/flintrock


text:
Is it possible to change the legend of the Graph in runtime?

Hello,
Initially
property var names: ['Current1','Current2','Previous Current 1','Previous Current2']
addGraph(names[0], true, colors[0], 1, 'solid');
during runtime I would like to change names[0] to "Voltage1"
I see that you have writen set graph name function
// set graph name
function setGraphName( n,name,replot_ ){ plot.setGraphName(n,name); if (replot_) replot(); }
Can you Please tell me with an example, what are the parameters n & replot_ i need to pass ?
Thanks a lot.

Got it!!!
plot1.setGraphName(0,"anotherName",true)
works perfect!!!


text:
🛑 Secrets Manager is down

In 57a81aa, Secrets Manager ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secrets Manager is back up in ab0a9fc.

repo: ndaringer/upptime


text:
🛑 Secrets Manager is down

In 3217438, Secrets Manager ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secrets Manager is back up in f76bbb7.


text:
UX for creating a new FastAuth Account

Design for creating a new FastAuth Account. This Design supports account creation for both passkey supporting browsers and unsupported browsers.
Figma Design Link
Passkey Supported

No Passkey Support

Added design and Figma link.

repo: near/fast-auth-signer


text:
Disable 2FA script question

Observing https://github.com/near/near-wallet/pull/2487/files#diff-af1599f511c250583625e7629817717180c2b3693cb7d8727d2c9250e612fd6cR22 - which contact is been deployed?
Also why is contract been deployed for disabling 2FA?
My expectation that next sequence of actions are done:

remove functional access key and replace them back with full access keys except for the one by NEAR Wallet
deploy state cleaning contract
call it to clean state after 2FA contract
deploy empty contract (to get to 0x0 hash)

Also if account had a contract before, a special circumstances are applied and probably should be done manually:

lookup old contract before by finding a offending transaction and it's block
fetch the old contract code via next command http post http://rpc.mainnet.near.org/ method=query params:=‘{“account_id”: “pool.near”, “request_type”: “view_code”, “block_id”: [59131110](tel:59131110) }’ jsonrpc=2.0 id=123 (need to replace block_id to before deployment and account id to the specific account)
deserialize the resulting base64 encoded file into .wasm file
deploy that contract by using the key from the seed phrase (near deploy <account id> decoded.wasm --seedPhrase='...')
replace functional access keys with full access keys except for one by NEAR Wallet (near keys <account id>, near add-key <account id> <key> --seedPhrase='...')

@ilblackdragon #2487 is meant to solve a specific case where some users have a seedphrase but they have a bricked 2fa. When they import account via seedphrase, the wallet detects that they have a multisig deployed and adds a LAK leaving them in the same state as before (unable to sign transactions due to bricked multisig). The idea was to provide this script to disable 2fa the same way the wallet does and then the next time they import via seedphrase the wallet would add a FAK since it identifies this as the empty contract the wallet currently uses and assumes the user has disabled 2fa. There is the option of providing documentation for them to run via near-cli instead of a script as well.
There is an upcoming PR that will address the issues in #2261. The flow we are considering for disabling 2fa is as you described though the wallet will still use the same contract wasm it currently uses (it's an arg in near-api-js). We will also add some gating based on whether the contract has existing state and if it's serializable as multisig before deploying the multisig when enabling 2fa.

@ilblackdragon https://github.com/near/near-wallet/pull/2487 is meant to solve a specific case where some users have a seedphrase but they have a bricked 2fa. When they import account via seedphrase, the wallet detects that they have a multisig deployed and adds a LAK leaving them in the same state as before (unable to sign transactions due to bricked multisig). The idea was to provide this script to disable 2fa the same way the wallet does and then the next time they import via seedphrase the wallet would add a FAK since it identifies this as the empty contract the wallet currently uses and assumes the user has disabled 2fa. There is the option of providing documentation for them to run via near-cli instead of a script as well. Not sure if we should update the script to fetch the old contract code but that may be the best approach here since the script will be useful to whoever is providing support so they don't have to execute the steps manually and can just provide block_id, accountId and seedPhrase. cc @MaximusHaximus
There is an upcoming PR that will address the issues in https://github.com/near/near-wallet/issues/2261. The flow being implemented for disabling 2fa is as you described though the wallet will still use the same contract wasm it currently uses (it's an arg in near-api-js). We will also add some gating based on whether the contract has existing state and if it's serializable as multisig before deploying the multisig when enabling 2fa.

authors: esaminu ilblackdragon

repo: near/near-wallet


text:
Update UI for implicit account creation

The goal of this UI update is to more clearly convey that the temporary funding address is indeed temporary and that the user should use their Account ID for any future NEAR operations.
Follow up TODO's (separate PR's):

Add progress bar to create account flow
Update design of recovery options on /set-recovery.

@vgrichina, once the account is created, the modal closes and there's a couple of seconds delay before the router redirects to the success page. I've tried to add different state flags etc to keep the modal open until redirect happens, but doesn't seem to help.
I set this flag creatingAccount to true before, and never set it to false, expecting it to stay true until the router redirects to the next page.
I'm trying to avoid adding on the formLoader flag for showing the modal in case there's a pending action in progress once the user lands on /fund-create-account, which would trigger the 'account funded modal' right away.
Any idea what might be the issue?

@ihaid, can you please do a round of testing on this updated account creation flow? Thank you

@ihaid, can you please do a round of testing on this updated account creation flow? Thank you

@corwinharrell I excluded the 'progress bar' because depending on the route the user takes at the recovery setup step, the current and total number of steps can change. Probably not a good idea to change the step/total mid flow.
I do think that a progress bar improves the UX in general, but I'm not sure how we can solve for the step/total issue.

@corwinharrell I excluded the 'progress bar' because depending on the route the user takes at the recovery setup step, the current and total number of steps can change. Probably not a good idea to change the step/total mid flow.
I do think that a progress bar improves the UX in general, but I'm not sure how we can solve for the step/total issue.


text:
Finality param, use new endpoint

Is your feature request related to a problem? Please describe.
We should expose some finality parameter to users in the client, with a default to wait for full finality. Use the newer send_tx
https://docs.near.org/api/rpc/transactions#send-tx
https://docs.near.org/api/rpc/transactions#tx-status-result
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe.
We should expose some finality parameter to users in the client, with a default to wait for full finality. Use the newer send_tx
https://docs.near.org/api/rpc/transactions#send-tx https://docs.near.org/api/rpc/transactions#tx-status-result
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.

Sent to: cd9b9351fd8ec40c8e82df9803e911c30064c6a07d4e156df2880b2a5290e58c

authors: Momendwiri dndll

repo: near/rollup-data-availability


text:
Implemented proper error handling for WAMP RPC handler registrations

@robin-thomas FYI, this and #45 PRs should improve the reliability of the backend.

Your PR Server URL is https://near-explorer-frontend-pr-47.onrender.com.
Follow its progress at https://dashboard.render.com/web/srv-bktll1ufgkcntf8refog.
Cheers,
The Render Team

authors: frol vgrichina

repo: nearprotocol/near-explorer


text:
Raw errors should not be returned to client

Right now, some errors get sent to the client, which include details that may not be desirable to reveal publicly.  Need a way to capture errors and handle them outside of this library.

+1 We probably could do this by checking whether the error implements certain interface and use it instead of the string representation.

For returned errors I see this as a simple solution:
if err := [...] ; err != nil {
    myErrorHandler(err)
    return nil, errors.New("something went wrong, but I won't tell you what")
}

For panics I think that in the future they will not include the panic's message any more, but simply say "an internal error occurred". However, I can only do that after finishing all the necessary error reporting for bad queries.

Is there something preventing errors from being returned as part of Schema.Exec?  Then they could be dealt with as part of the normal flow inside a request.
What you suggest I think would work, but at a glance doesn't appear to be the ideal solution.

Returning the errors like this is according to the spec, see https://facebook.github.io/graphql/#sec-Errors. If you really want to hide all errors from the client, couldn't you just not send the Errors field to the client after calling Schema.Exec, for example by setting it to nil?

Good points, and I think these are a product of me not understanding the spec well yet, as well as not knowing the details of your library.  I see now I can access those errors via the returned response.
The original concern I had was that an error message was being sent to the client that included information about the source code that I don't think should be sent.  I don't recall whether this was an error with the marshal part, or from the schema.Exec, so I'll need to keep an eye open for if I run across it again.
I'd like errors to be sent to the client as per the spec, but not containing details about source code.  What do you think?  I realise this will be much more helpful if I can provide you with an example.

Yes, please provide an example. Maybe it was related to a panic. I'm closing this issue until we can specify it further.

authors: bsr203 neelance saward

repo: neelance/graphql-go


text:
Create 1905-count-sub-islands.java

This java translation follows the python solution as closely as possible. There are 2 changes which have been made to make the python solution work in java. The first change is that the class RecursiveBiFunction is defined. This class exists so that the dfs lambda expression may refer to itself. The second change is that the visit set contains flattened integer coordinates instead of tuples. This change is made because tuples do not exist in java, and using an int array would not provide the correct behavior as int arrays compare themselves by not by value, but by reference.

File(s) Modified: 1905-count-sub-islands.java
Language(s) Used: java
Submission URL: _https://leetcode.com/submissions/detail/867724587/_

Thanks, @AP-Repositories!

repo: neetcode-gh/leetcode


text:
CSP Assessment Photos

Today each person in our group re-created a clone of the GitHub repositories and added our own label into it. Here are the screenshots, for each person's student_2025, name-here_2025, and portfolio_2025.
My Screenshots (Neil)
neil_2025

portfolio_2025

student_2025

Yash's Screenshots
yash_2025

portfolio_2025

Rohan's Screenshots
student_2025

portfolio_2025

rohan_2025

Nikhil's Screenshots
student_2025

portfolio_2025

nikhil_2025

Group Photo

Great job!  Try to look like an individual.


text:
Reproduce of training

Hi,
I am trying to train dlpacker from scratch. How did the learning rate been adjusted? In the paper, you mentioned a decrease when the loss is not improving, I am not sure there is a more strict definition.

I think Figure 1 in the paper illustrates this pretty well. Not sure what I can add here to answer your question!

authors: JinyuanSun nekitmm

repo: nekitmm/DLPacker


text:
Imposible to search account with excluded character

Required functionality to exclude characters from target account for vanity search
ex.:
nem --chain=testnet account vanity --exclude A, 2, 3

Duplicates #113.

repo: nem-toolchain/nem-toolchain


text:
Priority - Delegated harvesting to persist linked Keys

At the moment Delegated harvesting registration won't save up the linked keys. It is proposed that:
Delegated harvesting improvement

Separate key link transactions and persistent harvesting transaction's creation & announcement
Step 1 (currently the start button): Generate Remote, VRF key pairs, create and announce 3 (Remote, VRF, Node) key link transactions in an aggregate complete. Encrypt the Private key for Remote and  VRF keys, save the encrypted keys into the storage.
Step 2 (current the activate):  Load the vrf private key from local storage, create and announce the persistent harvesting transaction.
All other main delegated harvesting function stays the same.

Disaply linked keys

Add a new section in account info to show Linked Public keys. (accountInfo store)
Link any saved Remote and VRF private keys to the above public keys.
Ability to display the private key (password needed), for those who need them to setup their own nodes.

Will this remove the need for the two-step process to enable Delegated Harvesting?

Will this remove the need for the two-step process to enable Delegated Harvesting?

repo: nemgrouplimited/symbol-desktop-wallet


text:
Neue Action GetSepaDirectDebitLeadTime inkl. benötigter Parametersegmente

@Philipp91

Hast du dir das so vorgestellt Informationen aus den BDP abzufragen?
Sollten die Actions evtl. noch in thematische Unterordner platziert werden?
Hast du eine bessere Idee die Nicht-FinTs-Daten aus z.B. $minimaleVorlaufzeitCodiert d.h. (MinimaleVorlaufzeitSEPALastschrift) unterzubringen?

Außerdem frage ich mich ob es sinnvoll ist, immer die neueste Version eines Geschäftsvorfalls zu verwenden und wie man die Wahl dem Nutzer der Action überlässt.

Hast du dir das so vorgestellt Informationen aus den BDP abzufragen?

Ja. Hier fehlt noch ein Aufruf an die Action (z.B. eine neue BaseAction::markAvailable()) um $isAvailable zu setzen. Dann kann die Anwendung $action->isSuccess() aufrufen und glücklich sein, und der Getter in der Action kann wie üblich ensureSuccess() aufrufen.

Sollten die Actions evtl. noch in thematische Unterordner platziert werden?

Hätten wir dann nicht genau eine Klasse pro Unterordner?
Vermutlich sind es auch auf Dauer nicht soo viele Klassen, oder?

Hast du eine bessere Idee die Nicht-FinTs-Daten aus z.B. $minimaleVorlaufzeitCodiert d.h. (MinimaleVorlaufzeitSEPALastschrift) unterzubringen?

Das ist gut so. Sieht unelegant aus, aber die Spezifikation ist eben genauso unelegant und es spiegelt sich nur in der Bibliothek wider. Jedenfalls wüsste ich keine bessere Lösung. Eine eigene Parser-Klasse nur für explode(';', ...) wird sich vermutlich nie lohnen, selbst wenn noch mehr solcher Fälle dazukommen.

Außerdem frage ich mich ob es sinnvoll ist, immer die neueste Version eines Geschäftsvorfalls zu verwenden und wie man die Wahl dem Nutzer der Action überlässt.

Die Spezifikation geht davon aus, dass immer die neueste Version verwendet wird von denen, die sowohl Bank als auch Kundenprodukt (also phpFinTS) unterstützen.

Hätten wir dann nicht genau eine Klasse pro Unterordner?
Vermutlich sind es auch auf Dauer nicht soo viele Klassen, oder?

Im Falle von Lastschriften hätten wir dann zumindest schonmal zwei: GetSepaDirectDebitLeadTime und SendSepaDirectDebit
und es gibt bestimmt noch mehr Informationen aus den Parametern die Interessant sind abzufragen.

es gibt bestimmt noch mehr Informationen aus den Parametern die Interessant sind abzufragen

Naja wenn es irgendwann N Felder werden, die man vor einer Überweisung (beispielsweise) in Erfahrung bringen möchte, dann sollten wir dafür nicht N verschiedene Klassen haben, sondern eine GetÜberweisungsParameterAction, die einmal alles aus den BPD/UPD extrahiert und über mehrere Getter zur Verfügung stellt.
Ich finde es allgemein schwierig, vorab eine gute Ordnerstruktur festzulegen. Für dieses konkrete Projekt habe ich mir jetzt keine Gedanken gemacht, aber in der Praxis (bei anderen Projekten) hat man am Ende dann oft Ordner wo ewig nur eine Klasse drin ist, und irgendwann Klassen, die man nicht eindeutig zuordnen kann, usw. Also würde ich einfach dann anfangen umzusortieren, wenn es ungemütlich wird.
Man kann ja (stattdessen oder zusätzlich) in der Dokumentation und den Codebeispielen die zusammengehörigen zusammenfassen.

Seit diesem PR schlägt der HIUPDTest fehl.
@nemiah Können wir es wieder so einrichten, dass GitHub den Travis-Erfolg prüft, bevor es einen Merge zulässt?
@ampaze Die Konstruktoren von Segment/DEG-Klassen müssen ohne irgendwelche Argumente aufgerufen werden können. Btg::__construct() sollte am besten Btg::create() sein, dann kann es immer noch PHP Type-Hints verwenden.

Das weiß der Parser/Serializer.
ampaze notifications@github.com schrieb am Do., 19. Dez. 2019, 08:58:

@ampaze commented on this pull request.
In lib/Fhp/Segment/Common/Btg.php
https://github.com/nemiah/phpFinTS/pull/190#discussion_r359726969:

@@ -9,8 +9,14 @@
*/
class Btg extends BaseDeg
{

/** @var float */

/** @var string */

Weil ein Float einen Punkt als Dezimaltrenner hat, es muss aber ein Komma
sein.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nemiah/phpFinTS/pull/190?email_source=notifications&email_token=AATCUWZ3GKKJXRS2QWWHK4TQZMSTRA5CNFSM4J3NEPI2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCPXW5LA#discussion_r359726969,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATCUW34OSVFGZPFJVEYQODQZMSTRANCNFSM4J3NEPIQ
.

repo: nemiah/phpFinTS


text:
{"unsealed":true,"error":"The role requested does not exist."}

I am trying to solve this but not able to get any help.
i have the policy in place as per the documentation.
btw not able to proceed futher because of this.
curl -X POST -d"{"task_id":"n.9bc5088a-9e0f-11e9-a6d9-024258bea194"}" 'http://localhost:9201/token'
{"unsealed":true,"error":"The role requested does not exist."}

I'm getting this too but can't remember if I had a workaround that fixed it or not a few months back when I tested things out, or perhaps it's environmental.... idk.
Hopefully someone bumps this and if I figure out in the meantime will do so.

If you are getting ErrNoSuchRole, that means the AppRole you are trying to use doesn't exist. Let's say in your vault config you have { roles: ["test"] } - you should have created an approle of the same name:
vault write auth/approle/role/test \
    secret_id_ttl=10m \
    secret_id_num_uses=1 \
    policies=default \
    token_ttl=60m \
    period=60m

Gatekeeper leverages approles, so the ACLs you need should be tied the AppRole. You should take a look at the Getting Started guide if you are having trouble.

Thanks for the response! I'll have some time later today to jump back on this and will post what I find.

authors: ericxnelson nemosupremo shashankimanage

repo: nemosupremo/vault-gatekeeper


text:
Task/g56 expose serialization methods

Issue #56
Added:

Utility/TransactionMapping

createFromDTO(dataJson: object): Transaction
createFromPayload(dataBytes: string): Transaction

Transaction - new methods

Transaction.toJSON(): string - create JSON object from Transaction class.
Transaction.serialize(): string - serialize Transaction (unsigned payload)

@evias  I managed to fixed the bug in RegisterNamespaceTransaction now.
All done!

Pull Request Test Coverage Report for Build 261

237 of 253 (93.68%)  changed or added relevant lines in 13 files are covered.
72 unchanged lines in 1 file lost coverage.
Overall coverage increased (+3.3%) to 75.11%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/core/utils/TransactionMapping.ts
4
5
80.0%

src/model/account/PublicAccount.ts
0
1
0.0%

src/model/transaction/AggregateTransactionCosignature.ts
0
1
0.0%

src/model/transaction/SignedTransaction.ts
0
1
0.0%

src/model/transaction/Transaction.ts
7
8
87.5%

src/infrastructure/transaction/SerializeTransactionToJSON.ts
31
33
93.94%

src/infrastructure/transaction/CreateTransactionFromPayload.ts
189
198
95.45%

Files with Coverage Reduction
New Missed Lines
%

src/infrastructure/Listener.ts
72
28.34%

Totals

Change from base Build 245:
3.3%

Covered Lines:
1298

Relevant Lines:
1581

💛  - Coveralls


text:
fixes #162: Conversion error in case of nested field of array records

Fixes #162
Fixes the bug
Proposed Changes (Mandatory)
A brief list of proposed changes in order to fix the issue:

fixed the bug into ValueConverter class
added log in case of Neo4j error code listOf("Neo.ClientError.Statement.PropertyNotFound", "Neo.ClientError.Statement.SemanticError", "Neo.ClientError.Statement.ParameterMissing") because throwing an exception in that case stops the connect plugin. We also need to investigate if there are some other errors that we want they don't cause a plugin stop.

Thanks a lot Andrea, would you mind adding tests for that array case?

@jexp I updated the PR with the required changes:
Now we have a unit test for the converter ValueConverterTest where we create a tree structure like this:
       body
      /    \
 [p, ...]   [ul, ...]
                |
          [li[class, ...], ...]

thanks a lot for the feedback!