Reprojection example can overload WMS server

Describe the bug
Reprojecting the EPSG:4326 tile WMS source to EPSG:3857 is slow and may overload the server.
To Reproduce
Open https://openlayers.org/en/latest/examples/reprojection.html on a wide screen, select WMS EPSG:4326 as the base map, the equatorial and mid latitude reproj tiles appear quite quickly.  Pan north or south and the rendering gets very slow as the number of source tiles requested increases exponentially with latitude.  Eventually most of the tiles are rendered, but there may be some gaps and load errors on the console.
Expected behavior
The example should be reasonably fast and not request more tiles than the server can handle.  Possible solutions might be to restrict the maximum width of the map, to specify a tile grid to limit the zoom level of source tiles, or to use ImageWMS or an alternative cached XYZ source (e.g. https://github.com/openlayers/openlayers/issues/13782#issuecomment-1161720327) which is more able to handle the load - or better queue management.

Thanks for reporting this, @mike-000. I think configuring tileSize: 512 on the TiledWMS source should be enough to achieve an acceptable performance.

Or, even better, just change the service url to https://ahocevar.com/geoserver/gwc/service/wms and the WMS version to 1.1.1. Then cached versions of the tiles will be delivered.

Or, even better, just change the service url to https://ahocevar.com/geoserver/gwc/service/wms and the WMS version to 1.1.1. Then cached versions of the tiles will be delivered.

That is better but with a 1920px wide window it still overloads if panning to the high arctic or antarctic . Although the reproj tiles are handled in the main tile queue each requires many source tiles, which are loaded simultaneously without queueing - using an additional queue for source tiles needed for reprojection restricts the number of simultaneous requests on the server and prevents overload: https://codesandbox.io/s/reprojection-forked-r2421m?file=/main.js


Add repr to Token

Adds a __repr__ to token. Part of issue https://github.com/RasaHQ/rasa/issues/7250.
Haven't 100% decided what an ideal __repr__ of the other message features might be. So I'll do that later in another PR. Here's what it looks like locally;
from rasa.nlu.tokenizers.tokenizer import Token

Token("hello", start=10, end=15)
# <Token object value='hello' start=10 end=15 at 0x119b4ffd0>

It feels like a grand formality, do we really want to add docstrings to dunder-methods like __repr__?

It feels like a grand formality, do we really want to add docstrings to dunder-methods like __repr__?

@koaning The change looks good to me. Regarding your question on docstring, I'd ask @joejuzl or @wochinge on it. Any opinions folks?

I don't think all dunder methods (especially  __repr__) should require docstrings. However I think this would require a change to the docstring CI check.

I don't think all dunder methods (especially repr) should require docstrings. However I think this would require a change to the docstring CI check.

I was also annoyed by this. Will create a survey.

@koaning is this PR still on your radar?

It kind of is, but it's very much in the "nice to have"-category as opposed to the "must have"-category.
Was the docstring style thing resolved already? I assumed since there's no ping on the topic it's still ongoing.


Feature request: Indicators of connection towards Danfoss device

Would it be possible to configure 2 GPIO pins for LED indicators ?
E.g. if no connection to the Danfoss device, flash a LED on a configurable GPIO for 50 msec every 10 seconds
And when connection is established, light up a GPIO for 3 seconds - and then use the same pin to flash for 20msec e.g. every 60 seconds
This will give a visual indicator of whether the device has connection to the Danfoss device via BLE or not...

Hi @bipsendk,
This component does not keep the BLE connection open, it only checks on the device from time to time, so implementing the LED indication exactly as you've described doesn't seem possible.
You can try configuring https://esphome.io/components/status_led.html to get some indication of the current status. I haven't tried it myself, but at the moment component will set STATUS_LED_ERROR when incorrect PIN is provided for a PIN-protected device.
Let me know if that would work for you and I can extend the usage of status API, e.g. set warning status, when connection to the device failed and clear it on the next successful connection.

I tried to configure logging to debug and enable web interface on the ESP32 ...
For some reason,  the TCP connections is lost when the ESP tries to query via BLE ... And I sometime also see BLE connection error 133 (as far as I remember), which apparently could indicate something like "too many connections" ..
I will try to see if I can connect a host to the USB/Serial port and get the log that way around (instead of through the wireless interface) - to see if any usefull messages might pop up somewhere..


Tab within the textarea not working

Before report an issue, be sure to put these informations. Thanks :)
Informations
**Browser + version IE11:
OS: Windows 7
Resolution: 1080
How to reproduce the bug?
Initialize the library
Hey, great library! Just wondering, is there support for tab spacing in the textarea? I initialize the the editor with the following code (by the way the html setting doesn't work for me) :
$('#logbook').trumbowyg({
      btns: [
        ['formatting'],
        'btnGrp-semantic',
        ['link'],
        'btnGrp-justify',
        'btnGrp-lists',
        ['horizontalRule'],
        ['removeformat'],
        ['fullscreen']
      ]
    });

But when I click tab in the editor to indent the text it just leaves the editor (like normal tab behaviour).
Do I need to do something to change this behaviour?
Thanks

I did not support this kind of behaviour, but if you want to do that by yourself, you should add a listener on keydown, prevent default for the tab key and insert tab char.
Good luck :D

Thanks!


Consistency - shares not users

A share can have one or more members. Shares with more than one member are called group shares, see e.g. the selector for "sharing mode" on the app. They're still just one share, however. So when you view a group share in the browser, you're viewing one share with multiple members/participants.

I can add a group share to a group share?
I thought an entry is one individual share

You can't add two group shares together, but you can add a single user share to a group share. What actually happens when you do that, is that the owner of the single user share starts broadcasting to two shares instead of just one - his own personal share, and the group share in question. The group share will also show up as a separate share in the app for that person, as "Group share (member)". Hence, they will then have an active participation in multiple shares.
When you use the "Create new tracking link" button, that also creates a new share, but is still the same user.

I think we are lost in translation here, I know what's going on.
Not sure why those need to be "users" in this one string when they're called "shares" elsewhere?

I think that may be a case to rephrase the others away from "share" in that case. I may not have chosen the best phrasing for some of the strings. I'll push some commits here

Pushed a commit above. If I missed any, feel free to let me know


tikv panic when run jepsen case jepsen-bank-tbls

Bug Report

What version of TiKV are you using?
[2022/07/23 03:41:27.371 +00:00] [INFO] [lib.rs:84] ["Welcome to TiKV"] [2022/07/23 03:41:27.371 +00:00] [INFO] [lib.rs:89] ["Release Version:   6.2.0-alpha"] [2022/07/23 03:41:27.371 +00:00] [INFO] [lib.rs:89] ["Edition:           Community"] [2022/07/23 03:41:27.371 +00:00] [INFO] [lib.rs:89] ["Git Commit Hash:   dc7c48d1731e079ae0949694f88858554982136e"] [2022/07/23 03:41:27.371 +00:00] [INFO] [lib.rs:89] ["Git Commit Branch: heads/refs/tags/v6.2.0"] [2022/07/23 03:41:27.371 +00:00] [INFO] [lib.rs:89] ["UTC Build Time:    Unknown (env var does not exist when building)"] [2022/07/23 03:41:27.371 +00:00] [INFO] [lib.rs:89] ["Rust Version:      rustc 1.62.0-nightly (7c4b47696 2022-04-30)"] [2022/07/23 03:41:27.371 +00:00] [INFO] [lib.rs:89] ["Enable Features:   pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp cloud-azure"] [2022/07/23 03:41:27.371 +00:00] [INFO] [lib.rs:89] ["Profile:           dist_release"]
What operating system and CPU are you using?
do not care
Steps to reproduce
run jepsen case jepsen-bank-tbls with the following options：
{:auto-retry-limit :default,
 :ssh-private-key "jepsen.pem",
 :isolation :repeatable-read,
 :concurrency 15,
 :predicate-read false,
 :tarball-url
 "http://minio.pingcap.net:9000/tp-team/tests/jepsen/tidb-v6.2.0-pre-amd64.tar.gz",
 :txn-mode "optimistic",
 :force-reinstall true,
 :update-in-place false,
 :ssh
 {:username "root",
  :password "root",
  :strict-host-key-checking false,
  :private-key-path "jepsen.pem"},
 :nemesis-long-recovery false,
 :follower-read false,
 :nemesis
 {:interval 10,
  :schedules true,
  :kill true,
  :stop true,
  :partition-one true},
 :nodes
 ["node-0.node-peer.jepsen-tps-1021429-1-424"
  "node-1.node-peer.jepsen-tps-1021429-1-424"
  "node-2.node-peer.jepsen-tps-1021429-1-424"
  "node-3.node-peer.jepsen-tps-1021429-1-424"
  "node-4.node-peer.jepsen-tps-1021429-1-424"],
 :test-count 1,
 :read-lock nil,
 :use-index false,
 :os #object[tidb.core.Image 0x19fec3d6 "tidb.core.Image@19fec3d6"],
 :time-limit 600,
 :recovery-time 10,
 :version "master",
 :auto-retry :default,
 :workload :bank-multitable,
 :init-txn-sql nil,
 :init-sql
 ("set @@tidb_enable_mutation_checker=1, @@tidb_txn_assertion_level=strict")}

What did you expect?
tikv run normal
What did happened?
tikv panic：
[2022/07/23 03:40:52.837 +00:00] [ERROR] [util.rs:447] ["request failed, retry"] [err_code=KV:PD:gRPC] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: \"not leader\", details: [] }))"]
[2022/07/23 03:40:52.839 +00:00] [ERROR] [util.rs:447] ["request failed, retry"] [err_code=KV:PD:gRPC] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: \"not leader\", details: [] }))"]
[2022/07/23 03:40:52.839 +00:00] [ERROR] [util.rs:447] ["request failed, retry"] [err_code=KV:PD:gRPC] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: \"not leader\", details: [] }))"]
[2022/07/23 03:40:52.839 +00:00] [ERROR] [util.rs:447] ["request failed, retry"] [err_code=KV:PD:gRPC] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: \"not leader\", details: [] }))"]
[2022/07/23 03:40:52.839 +00:00] [ERROR] [util.rs:447] ["request failed, retry"] [err_code=KV:PD:gRPC] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: \"not leader\", details: [] }))"]
[2022/07/23 03:40:52.839 +00:00] [INFO] [util.rs:575] ["connecting to PD endpoint"] [endpoints=http://node-1.node-peer.jepsen-tps-1021429-1-424:2379]
[2022/07/23 03:40:52.840 +00:00] [ERROR] [util.rs:447] ["request failed, retry"] [err_code=KV:PD:gRPC] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: \"not leader\", details: [] }))"]
[2022/07/23 03:40:52.848 +00:00] [FATAL] [lib.rs:494] ["http://node-1.node-peer.jepsen-tps-1021429-1-424:2379 no longer belongs to cluster<PHONE_NUMBER>188645195, it is in 0"] [backtrace="   0: tikv_util::set_panic_hook::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tikv_util/src/lib.rs:493:18\n   1: std::panicking::rust_panic_with_hook\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:702:17\n   2: std::panicking::begin_panic_handler::{{closure}}\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:588:13\n   3: std::sys_common::backtrace::__rust_end_short_backtrace\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:138:18\n   4: rust_begin_unwind\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:584:5\n   5: core::panicking::panic_fmt\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:142:14\n   6: pd_client::util::PdConnector::load_members::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/pd_client/src/util.rs:618:29\n      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n      pd_client::util::PdConnector::reconnect_pd::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/pd_client/src/util.rs:648:52\n      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n   7: pd_client::util::Client::reconnect::{{closure}}::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/pd_client/src/util.rs:341:92\n      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n      pd_client::util::Client::reconnect::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/pd_client/src/util.rs:361:63\n      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n   8: pd_client::util::Request<Req,F>::reconnect_if_needed::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/pd_client/src/util.rs:418:42\n      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n      pd_client::util::Request<Req,F>::execute::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/pd_client/src/util.rs:467:43\n      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n   9: <core::pin::Pin<P> as core::future::future::Future>::poll\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/future.rs:124:9\n      futures_executor::local_pool::block_on::{{closure}}\n             at /rust/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.15/src/local_pool.rs:315:23\n      futures_executor::local_pool::run_executor::{{closure}}\n             at /rust/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.15/src/local_pool.rs:90:37\n      std::thread::local::LocalKey<T>::try_with\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:443:16\n      std::thread::local::LocalKey<T>::with\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:419:9\n      futures_executor::local_pool::run_executor\n             at /rust/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.15/src/local_pool.rs:86:5\n      futures_executor::local_pool::block_on\n             at /rust/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.15/src/local_pool.rs:315:5\n      <alloc::sync::Arc<T> as tikv::server::gc_worker::gc_worker::GcSafePointProvider>::get_safe_point\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/server/gc_worker/gc_worker.rs:81:9\n      tikv::server::gc_worker::gc_manager::GcManager<S,R,E>::try_update_safe_point\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/server/gc_worker/gc_manager.rs:355:32\n  10: tikv::server::gc_worker::gc_manager::GcManager<S,R,E>::wait_for_next_safe_point\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/server/gc_worker/gc_manager.rs:341:16\n      tikv::server::gc_worker::gc_manager::GcManager<S,R,E>::run_impl\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/server/gc_worker/gc_manager.rs:314:13\n      tikv::server::gc_worker::gc_manager::GcManager<S,R,E>::run\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/server/gc_worker/gc_manager.rs:299:9\n      tikv::server::gc_worker::gc_manager::GcManager<S,R,E>::start::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/server/gc_worker/gc_manager.rs:285:17\n      <std::thread::Builder as tikv_util::sys::thread::StdThreadBuildWrapper>::spawn_wrapper::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tikv_util/src/sys/thread.rs:414:23\n      std::sys_common::backtrace::__rust_begin_short_backtrace\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:122:18\n  11: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:500:17\n      <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:271:9\n      std::panicking::try::do_call\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:492:40\n      std::panicking::try\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:456:19\n      std::panic::catch_unwind\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:137:14\n      std::thread::Builder::spawn_unchecked_::{{closure}}\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:499:30\n      core::ops::function::FnOnce::call_once{{vtable.shim}}\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:248:5\n  12: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1866:9\n      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1866:9\n      std::sys::unix::thread::Thread::new::thread_start\n             at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/unix/thread.rs:108:17\n  13: start_thread\n  14: clone\n"] [location=components/pd_client/src/util.rs:618] [thread_name=gc-manager]

[2022/07/23 03:40:52.848 +00:00] [FATAL] [lib.rs:494] ["http://node-1.node-peer.jepsen-tps-1021429-1-424:2379 no longer belongs to cluster<PHONE_NUMBER>188645195, it is in 0"] [backtrace="   0: tikv_util::set_panic_hook::{{closure}}
at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tikv_util/src/lib.rs:493:18
1: std::panicking::rust_panic_with_hook
at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:702:17
2: std::panicking::begin_panic_handler::{{closure}}
at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:588:13
3: std::sys_common::backtrace::__rust_end_short_backtrace
at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:138:18
4: rust_begin_unwind
at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:584:5
5: core::panicking::panic_fmt
at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:142:14
6: pd_client::util::PdConnector::load_members::{{closure}}
at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/pd_client/src/util.rs:618:29
<core::future::from_generator::GenFuture as core::future::future::Future>::poll
at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19
pd_client::util::PdConnector::reconnect_pd::{{closure}}
at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/pd_client/src/util.rs:648:52
<core::future::from_generator::GenFuture as core::future::future::Future>::poll
at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19
7: pd_client::util::Client::reconnect::{{closure}}::{{closure}}
at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/pd_client/src/util.rs:341:92
<core::future::from_generator::GenFuture as core::future::future::Future>::poll
at /rust/toolchains/nightly-2022-05-01-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19
pd_client::util::Client::reconnect::{{closure}}
It looks like there are some environmental issues. @vivid392845427 Please help verify if the test environment is set correctly.

Here is the brief history. It seems pd starts to accept connection requests before it's fully initialized. I didn't see this before, and I also don't known whether there is any related change to pd recently. /cc @nolouch.
08:06:13.862 jepsen nemesis stop-pd @{node-0,node-1,node-2,node-4}
08:07:03,106 jepsen nemesis start-pd @all
08:07:03.290 pd@node-2 ["Welcome to Placement Driver (PD)"]
08:07:03.593 kv@node-4 try to connect to pd@node-2 but got resp.header.cluster_id == 0, then PANICKED
08:07:13.327 pd@node-2 ["init cluster id"] [cluster-id=7123104101284464385]
08:07:13.361 pd@node-2 ["server starts to synchronize with leader"] [server=pd3] [leader=pd4] [request-index=6800]
08:07:13.764 pd@node-2 ["server sync index not match the leader"] [server=pd3] [own=6800] [leader=6815] [records-length=0]
...

The full logs can be accessed here (you may need to right click and 'save link as...').

I check it and there are no new changes.  if PD is not initialized, it is normal as expect, but the initailized used 10 time seconds, it's main reason.

OK, maybe it's caused by the slow environment.

I think it's https://github.com/tikv/pd/pull/5310 that leads to the issue. We may need to let tikv handle the error properly (to avoid unwanted panics). @nolouch @Connor1996 PTAL

PTAL @JmPotato @HuSharp Some cases that are not logic errors should return grpc error to let TiKV retry other PD members. https://github.com/tikv/pd/pull/5310/files#diff-eb404b45d0a569b05f58f4e4bf2b42b32150be75ec2ed72f86330c4b5d739eabR108


Support multiple tables / star schema

Right now, only a single fact table is supported, and aggregations of dimensions will assume that all columns for a given dimension are perfectly denormalised. The application should support JOINs for a star schema instead.

@akariv first we need to understand if we need this. Assigning to you to investigate as part of general deep dive on babbage.

Might be useful to separate between being able to load from multiple resources and keeping multiple tables for dimensions internally. The two are almost certainly a "false friend" equality (i.e. looks like the same thing but in practice turns out not to be one).

@pudo totally agree. seems to me that single resources in FDP speak could (should?) load into multiple tables (star schema).
I definitely do not want babbage to change to reflect the various modelling strategies in an FDP mapping: rather, that the loader can work with the mapping to write to a consistent (normalised?) babbage model.

There was an interesting thought from @stiivi (also relevant to #4): he proposed loading the source data facts into a JSON column on the fact table (i.e. as-is) and then generating the actual columns and star schema as the model is defined through PostgreSQL commands (i.e. inside the DB).
Otherwise you end up in that spot where each time someone changes the label for an attribute, you have to re-load 900 MB of source CSV.

I'm going to backlog this now. We don't need this now, and while there are great ideas in here, let's focus on our core tasks first.

I am not sure if now is the time to pop this out of the backlog.
We are interested in using such a feature in openbudgets.eu. Other than the backend implementation, in which I can't offer any opinion yet, what is the suggested way to support this API-wise?
Would it be a call to the aggregates/facts etc endpoints without a cube path part?

I would say that from an API point of view, nothing needs to change.
The API should reflect to the user a denormalized data table, while using normalized tables in the backend.

Yes, but how do you imagine a call of this service? This call:
http://next.openspending.org/api/3/cubes/405f5e1681d4b6673fbfc0ceb196fe47:boost-armenia-2006-2014/aggregate?drilldown=activity.program&pagesize=30&cut=classification.econ_func%3A%22Economic%22&order=adjusted.sum%3Adesc
already contains the cube name in it. Will "cube-less" queries be supported somehow?

Just out of interest: what are the semantics of a cube-less call? I imagine it would be quite hard to properly aggregate budgetary data even with slightly different origins. If we're talking RDF here: Wouldn't it be less dangerous for a data integration tool to actually materialise merged cubes with well-defined semantics? (e.g. "here's the merged cube of all cohesion fund data sub-cubes")

Well a cube-less call is a fictional, ideal call, intended to force us explore alternative solutions.
We are indeed working with RDF at openbudgets.eu, but we do not desire to suggest any direction for openspending based on our expactations from RDF.
This means we don't even care if openspending's loader materialises the merged cubes. In rudolf, we have to tackle the same issues: determine which dimensions are similiar, determine which values of these dimensions are similar (in order to support common cuts) and find a way to get normalized values (mostly currency-related normalization).
Regarding the dimensions: we can either cross our fingers and rely on dimensions inheriting from common parents (also having values linked with some kind of similarity predicate) or go with CONSTRUCT queries which indeed materialize the datasets into a new cube. Both ways are implementable our side, I was just wondering if, API-wise, there would be some actual super-cube to query in the same way as with the ordinary cubes.


Responsiveness Update Site-wide - rebased on main

Originally:
@Cililocwee : I redid a slew of the bootstrap classes to make sure that we weren't overflowing (especially) on smaller devices.
There were conflicts with the main branch that were not trivial to fix, I tried my best to rebase your branch on top of:

the main branch
the format / lint branch

@danypellerin the only issues I'm seeing are several of the changes on the dashboard were reverted, so some things are overflowing. And there's an issue with the home page, the banner has a top margin. You want me to fix the issues and push to this branch?

@danypellerin @joebeernink I retouched the UI issues after the rebase and this should be ready to merge over!

##BEFORE

##AFTER

Did a QA looked good, I squashed everything otherwise it would`ve been impossible to rebase. Did an autofix and format. Comments will be addressed in a follow-up PR.


Continuing refactoring of the extraction objects

Following #685, I continued the refactoring of the extraction classes Image, ROI, Patch and Slice. I suggest to get rid of some complicated features while adding some useful ones:

For all: remove use_uncropped_image that should be put in Preprocessing.

Slice: in addition to discarded_slices that only enable slice filtering, I suggest to introduce two new arguments. slices  enables slice selection (e.g. Slice(slices=[128, 129, 130])); and borders enables slice filtering at the edge of the image. For example, Slice(discarded_slices=[42], borders=5) will filter out the slice with index 42, as well as the first five and the last five slices in each direction. borders can also be specified for each border (e.g. Slice(borders=((1, 1), (2, 3), (1, 1))).

Patch: I suggest to enable anisotropic sliding window by allowing the user to pass anisotropic values for patch_size and stride (e.g. Patch(patch_size=(18, 16, 17), stride=(1, 1, 2)).

ROI:  to replace roi_list, roi_mask_location, roi_crop_input, roi_crop_output, roi_template,  roi_mask_pattern, roi_custom_template and roi_custom_mask_pattern, I would suggest to have only two arguments. masks, where a list of masks can be passed via their file location (e.g. ROI(masks=["masks/leftHippocampus.nii.gz", "masks/rightHippocampus.nii.gz"])); and crop that enables to filter out regions that are always 0 for all masks, in order to reduce the size of the images.
In doing so, I purposely release some constraints on the masks that can be used, that I felt unnecessary.

Besides, I also made some minor changes:

Renaming BaseExtraction to Extraction, in order not to have Base... in our typings;
Gathering roi, patch, slice and image under the generic word sample. I changed the function names and dosctrings accordingly;
Uniformizing the docstring between the four child classes (there is still work the be done).

As of now, the classes are not tested. i'm waiting for your opinion first.

The classes are now tested with 100% coverage.

I just added some useful class methods to manipulate TorchIO's class Subject. This is crucial as our transforms will manipulate Subject objects. More precisely:

get_tio_image: puts the image and the label in a Subject, as well as other potential masks that will be used to compute the transforms.
extract_tio_sample: does the extraction like extract_sample, but works on Subject. All the images in the Subject object will undergo the extraction. For example, in the case of segmentation, extraction will be performed also on the  segmentation map.
format_output: takes a Subject and some metadata and returns a Sample, which is typically the output of the __getitem__ in our CapsDataset. Sample is similar to the old CapsDatasetSample, but it is different depending on the extraction method.

So, in the __getitem__ of our CapsDataset, I imagine it this way:
    participant, session, img_index, sample_index = self._get_meta_data(idx)
    image, image_path = self._get_image(img_index)
    label = self._get_label(img_index)

    tio_image = self.transforms.extraction.get_tio_image(image, label)

    tio_image = self.transforms.image_transforms(tio_image)

    if not self.eval_mode:
        tio_image = self.transforms.image_augmentation(tio_image)

    tio_sample = self.transforms.extraction.extract_tio_sample(tio_image, sample_index)

    tio_sample = self.transforms.sample_transforms(tio_sample)

    if not self.eval_mode:
        tio_sample = self.transforms.sample_augmentation(tio_sample)

    return self.transforms.extraction.format_output(
        tio_sample,
        participant_id=participant,
        session_id=session,
        image_path=image_path,
    )

In Slice, I removed the argument slice_mode, as duplicating channels can easily be done with a basic transform.

As discussed in developer meeting, I removed the ROI extraction as it can be done with common transforms (e.g. Mask, potentially followed by Crop).


Re-fix the problem with missing session

After more through investigation of Cro::HTTP::Session::Persistent it became clear that load method must not do autovivifaction of a session record if it's missing in the DB. Instead it must return a Failure. In this case Cro::HTTP::Session::Persistent will correctly create a new session.

I apologize for incorrect fix provided in #1. It came to me today that when a session gets auto-vivified it also might be a security risk.

Thank you very much


Added a reminder about Go to member

@phistuck Can you please fix the typo I found.

Err.... no. :) See my reply to the comment.
Note - I get e-mail notifications for the note you add, you can avoid asking me to take care of those in a comment as well. :)

Thought I was looking at the end of a sentence. Sorry.


Multi upload files

Bug:
I have 2 ngFileDrop and ngFileSelect in the same html page, when I drop or browser a file for a specified component they will call all handlers from all components.
Version: 2.0.0
This bug don't exist at version 1.6
example code that works in version 1.6
html:

                    Drag & drop
                    Your files here, or
                        <input id="uploadInvoiced" type="file" style="display:none" ngFileSelect [options]="optionsInvoiceFile" (onUpload)="handleUploadInvoiced($event)" />browse.

                    Drag & drop
                    Your files here, or
                        <input id="uploadResourceCosts" type="file" style="display:none" ngFileSelect [options]="optionsResourceCosts" (onUpload)="handleUploadResourceCosts($event)" />browse.

component.ts:
handleUploadResourceCosts(data): void {
    console.log("handleUploadResourceCosts: data do upload.. ");
    this.hasBaseDropZoneOverResourceCosts = false;
    if (data && data.status === 200) {
      this.snackBar.open("Resources file uploaded with success.", "Close");
    }else if(data && data.status === 400){
      this.snackBar.open("You tried upload a invalid resources file.", "Close");
    }

  }

handleUploadInvoiced(data): void {
    console.log("handleUploadInvoiced: data do upload2.. ");
    if (data && data.status === 200) {
      this.snackBar.open("Invoiced file uploaded with success.", "Close");
    }else if(data && data.status === 400){
      this.snackBar.open("You tried upload a invalid invoiced file.", "Close");
    }
    this.hasBaseDropZoneOverInvoiced = false;
  }

With version 1.6 if i upload Invoice file they will call handleUploadInvoiced handler, it's ok.
With version 2.0 if i upload Invoice file they will call both handlers.

hi @FilipeQ. thanks for your report, I'll check on this.


Add document about best practices for maintainers

PR Summary
Add document about best practices for maintainers.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@iSazonov I think it's much more clear and also look better now. Please take another look.


Issue with GFS time reference

I am currently translating some old ferret code into python. However, when downloading GFS operational data, there was an issue...
When downloaded from ferret, the GFS file has the following time reference (using ncdump -h):
double TIME(TIME) ;
        TIME:units = "days since 0001-01-01 00:00:00" ;
        TIME:long_name = "time" ;
        TIME:time_origin = "01-JAN-0001 00:00:00" ;
        TIME:axis = "T" ;
        TIME:standard_name = "time" ;

When using xarray to access the openDAP server and writing to disk using ds.to_netcdf(), the file has this time reference.
double time(time) ;
        string time:grads_dim = "t" ;
        string time:grads_mapping = "linear" ;
        string time:grads_size = "81" ;
        string time:grads_min = "00z15apr2016" ;
        string time:grads_step = "3hr" ;
        string time:long_name = "time" ;
        string time:minimum = "00z15apr2016" ;
        string time:maximum = "00z25apr2016" ;
        time:resolution = 0.125f ;
        string time:units = "days since 2001-01-01" ;
        time:calendar = "proleptic_gregorian" ;

This is not really an issue while using the data inside python because the dates are translated correct. However, in my work flux, I need this file to be read for other models such as  WW3. For instance, trying to read it from WW3, results in:
Processing data
 --------------------------------------------------
           Time : 0015/03/15 00:00:00 UTC
                  reading ....
                  interpolating ....
                  writing ....
           Time : 0015/03/15 03:00:00 UTC

Looking at the reference time, ferret gives TIME:time_origin = "01-JAN-0001 00:00:00" while xarray gives string time:units = "days since 2001-01-01". Well, there are 2000 years missing...
I tried to fix it using something like:
ds.coords['reference_time'] = pd.Timestamp('1-1-1')
But the reference time didn't really updated. Is there an easy way to fix the reference time to match what is in the NOAA's openDAP server ?

When you're writing the data back to disk with to_netcdf, use try writing something like: ds.to_netcdf('somefile.nc', encoding={'time': {'units': '01-JAN-0001 00:00:00'}}).
But I'm a little surprised this doesn't work by default. Xarray does use '2001-01-01' as a default reference time, but if you pulled the data from an existing dataset (rather than creating the time variable directly yourself such as with numpy or pandas), then it should save the original units in encoding attribute of the time variable, which should then be used to save the units that it writes to the file. If ds is the name of the dataset you open from OpenDAP or save to netcdf, what does the value of ds.time.encoding look like?

ds.time.encoding results in
{'dtype': dtype('float64'),
 'original_shape': (81,),
 'source': 'http://nomads.ncep.noaa.gov:9090/dods/gfs_0p25/gfs20160417/gfs_0p25_00z',
 'units': u'days since 1-1-1 00:00:0.0'}

I tried to use ds.to_netcdf('filename.nc', encoding={'time': {'units': u'days since 1-1-1 00:00:0.0'}}), but ncdump still shows "time" as having "days since 2001-01-01" as reference time:
double time(time) ;
		string time:grads_dim = "t" ;
		string time:grads_mapping = "linear" ;
		string time:grads_size = "81" ;
		string time:grads_min = "00z17apr2016" ;
		string time:grads_step = "3hr" ;
		string time:long_name = "time" ;
		string time:minimum = "00z17apr2016" ;
		string time:maximum = "00z27apr2016" ;
		time:resolution = 0.125f ;
		string time:units = "days since 2001-01-01" ;
		time:calendar = "proleptic_gregorian" ;

Ah, I finally figured out what's going on.
We use pandas to cleanup time units in an attempt to always write ISO-8601 compatible reference times. Unfortunately, pandas interprets dates like '1-1-1' or '01-JAN-0001' as January 1, 2001:
In [21]: pd.Timestamp('1-1-1 00:00:0.0')
Out[21]: Timestamp('2001-01-01 00:00:00')

In [25]: pd.Timestamp('01-JAN-0001 00:00:00')
Out[25]: Timestamp('2001-01-01 00:00:00')

One might argue this is a bug in pandas, but nonetheless that's what it does.
xarray can currently handle datetimes outside the range dates hangled by pandas (roughly 1700-2300), but only if pandas raises an OutOfBoundDatetime error.
Two fixes that we need for this:

use netCDF4's reference time decoding (if available) before trying to use pandas in decode_cf_datetime. Note that it is important to only decode only the one reference time if possible using netCDF4, because it's a lot faster to parse dates with vectorized operations with pandas/numpy.
stop using _cleanup_netcdf_time_units, since apparently it can go wrong.

cc @jhamman who has some experience with these issues

I would rather stick only with xarray, but iris solved the issue for now...
Another alternative is to use NCO  an do something like: ncatted -O -a units,time,o,c,'days since 0001-01-01 00:00:00'

Unfortunately, pandas interprets dates like '1-1-1' or '01-JAN-0001' as January 1, 2001

this is too bad.

use netCDF4's reference time decoding (if available) before trying to use pandas in decode_cf_datetime. Note that it is important to only decode only the one reference time if possible using netCDF4, because it's a lot faster to parse dates with vectorized operations with pandas/numpy.

This seems easy enough. It would be nice if we always had netcdftime available.
I can try to take a hack at this later this week (unless someone gets there first).

Also mentioned in #4422 and fixed in #4506


Crash on launch

Got a crash with the following traceback straight after launching the app:
java.lang.RuntimeException: Unable to destroy activity {com.btcontract.wallet/com.btcontract.wallet.HubActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'akka.actor.ActorRef immortan.LNParams$WalletExt.catcher()' on a null object reference
	at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:5176)
	at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:5205)
	at android.app.servertransaction.DestroyActivityItem.execute(DestroyActivityItem.java:44)
	at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2183)
	at android.os.Handler.dispatchMessage(Handler.java:107)
	at android.os.Looper.loop(Looper.java:241)
	at android.app.ActivityThread.main(ActivityThread.java:7604)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:941)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'akka.actor.ActorRef immortan.LNParams$WalletExt.catcher()' on a null object reference
	at com.btcontract.wallet.HubActivity.onDestroy(HubActivity.scala:733)
	at android.app.Activity.performDestroy(Activity.java:8068)
	at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1363)
	at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:5161)
	... 11 more

I remember swiping it off of the recent app list hours ago so that's probably related.

Most likely fixed in https://github.com/btcontract/wallet/commit/7ad94c13dd6f45077edf1c8c9a2a7515afe260e9.
Due to Android specifics an app may become half-destroyed so to say: some objects may be nullified while others remain in place.
So when launched an app may find itself in such a state, in which case it destroys itself completely and restarts. The issue most likely is that app was trying to access already nullified object properties in onDestroy method, which resulted in exception.
Now those parts are surrounded by try blocks which swallow exceptions allowing an app to restart cleanly.

Let's see if this happens again within some time after next update, if not then I'll close an issue.

Closing this for now, feel free to reopen if this happens again.


Custom package manager for libs,commands, progarmming languages

I suggest creating custom package manager like brew/apt/pacman.
And it works like this
pca install <package name> - add package
pca list - list of your installed packges
pca remove <package name> - remove package
pca remove -r <package name> - remove recursively package
pca repo add <link to repo> - add repository from which you source packages
pca repo remove <link to repo> - remove repository from which you source packages
pca repo list - list of repositories from which you source packages
This will solve many issues and create tool for community to better contribute to list of commands avalibale in terminal

While it's a great idea, iOS doesn't allow installing arbitrary commands outside the app bundle. Furthermore, most of the commands don't work on iOS without heavy modification.

but you can install commands throw pip
and also community can make modifications for this to work

but you can install commands throw pip
and also community can make modifications for this to work

Sure. So I'll leave this open :) I think it's possible if the commands are compiled as webassembly.

https://wapm.io/
there is a package manager for wasm and it has many packages.
you could try modificate it

https://wapm.io/
there is a package manager for wasm and it has many packages.
you could try to modificate it

Wow, thank you for sharing this! It looks promising.


upgrade: consider multiple hypervisors and secondary storages

This fixes an issue during upgrade in edge case.
Steps to reproduce the issue

deploy an env with ACS 4.18
the env has multiple hypervisors: KVM and VMware
the env has multiple secondary storages: sec1 and sec2
register the new 4.19.1 systemvm template for VMware (systemvm-vmware-4.19.1), but mistakely as a private template.
the systemvm template is downloaded to sec2 (not sec1). If it is downloaded to sec1, remove it and re-register the template.
backup the cloudstack databases by mysqldump -R cloud and mysqldump -R cloud_usage
install ACS <IP_ADDRESS> and start mgmt server

Without this PR, got an NPE during mgmt server start
2024-10-29 12:46:53,904 ERROR [c.c.u.SystemVmTemplateRegistration] (main:null) (logid:) Failed to register template for hypervisor: VMware
java.lang.NullPointerException
        at com.cloud.upgrade.SystemVmTemplateRegistration.updateTemplateDetails(SystemVmTemplateRegistration.java:519)
        at com.cloud.upgrade.SystemVmTemplateRegistration.performTemplateRegistrationOperations(SystemVmTemplateRegistration.java:640)
        at com.cloud.upgrade.SystemVmTemplateRegistration.registerTemplate(SystemVmTemplateRegistration.java:650)
        at com.cloud.upgrade.SystemVmTemplateRegistration$4.doInTransactionWithoutResult(SystemVmTemplateRegistration.java:789)
        at com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)

Description
This PR...

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11723

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11725


expose LED switch and outdoor temp to home assistant

Describe the solution you'd like
LED (AC display) could be exposed as a switch. Outdoor temp could be exposed as a sensor. The upstream library appears to support these.

I added a setter for the AC LED light on/off state and tested it: it works.
https://github.com/aa755/midea-ac-lib/commit/6aa0eb660edea4f08bce73ab31e51d6992dd7e87#diff-6ad3d8b7b3d88f8f4c5bb4a84db572f8R109

Perhaps you could expose this as a switch entity? Or add a custom service to toggle it? PRs welcome :)

If exposed as a separate switch entity, I am not sure how the switch and the AC entities would share the same midea.device object. Custom service seems simpler to implement. By any chance, do you know any developer-oriented tutorial for writing custom services in home assistant?

For home assistant to be able to log and draw graphs of outdoor temperature, I think custom service wont suffice and it would need to be exposed as a sensor.

Consider the method used by the Dyson component. They don't expose it as a switch, however they do provide a service and attribute.
I have used template switches to give me what I want.
- platform: template
  switches:
    template_service_midea.set_night_mode:
      friendly_name: Midea LED Night Mode
      value_template: "{{ is_state_attr('fan.midea_0123456789ABCDEF', 'night_mode', true) }}"
      turn_on:
        service: midea.set_night_mode
        data:
          entity_id: fan.midea_0123456789ABCDEF
          night_mode: true
      turn_off:
        service: midea.set_night_mode
        data:
          entity_id: fan.midea_0123456789ABCDEF
          night_mode: false

Dyson Cool Link Tower only expose fan… whereas Dyson Hot+Cool expose both climate and fan...

Well, it's summer again. And I've put my window rattler back in place. Bought a second one as well...
Anyone have any further interest in exposing the LED as a switch or as a service?

Perhaps the night_mode concepts from shenxn/ha-dyson would be helpful
https://github.com/shenxn/ha-dyson/blob/main/custom_components/dyson_local/switch.py


cohesin loading unloading ancestry

I now think the regulation descendants  should be a descendent of positive/and or negative regulation of DNA binding?
See also
@ukemi #12624
"cohesin DNA binding Wapl did not stimulate ATP hydrolysis (Figure S1A), suggesting that it facilitates DNA binding in a different way."
PMID:26687354

So should I make 'cohesin loading' a subclass of DNA binding rather than a subclass of 'protein localization to chromatin'. Or perhaps it should be both?
Based on the new definition, wouldn't 'cohesin unloading' itself be a negative regulation of DNA binding?

Both seems correct to me....

OK. I added DNA binding as an is_a parent of 'cohesin loading'. The regulation children should sort when the reasoner runs.
It seems that 'cohesin unloading' itself should be a negative regulation of DNA binding. Don't you think?

I made it that for now. It makes sense based on how the term is placed. Let me know if you think I should change it.

It seems that 'cohesin unloading' itself should be a negative regulation of DNA binding. Don't you think?

yep, I agree  see first comment

Oops. I can't make cohesin loading a child of DNA binding because DNA binding is a molecular function and cohesin loading is a biological process. I can make cohesin loading has_part DNA binding.

Its the process "GO:0051101 regulation of DNA binding" that we need "cohesin loading" to be related to

So cohesin loading is_a positive regulation of DNA binding. That makes sense to me.

yep and -ve for the unloading

Done


Swift 4.2 Support

Support for Swift 4.2

Thanks for the pull request @michaljach. The tests should pass after #28 is merged.

@michaljach Could you please rebase this branch against latest develop branch? I'll merge in and release a new version once CI passes.

@michaljach Could you please rebase this branch against latest develop branch? I'll merge in and release a new version once CI passes.


Persistent Notification - homeassistant.exceptions.InvalidEntityFormatError

Home Assistant release with the issue: <=0.77.3
Last working Home Assistant release (if known): Never worked (for me)
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Component/platform: notify.persistent_notification
Description of problem:
When attempting to create a persistent notification it fails to execute.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
#
  - id: new_device_detection
    alias: New Device Detection
    initial_state: 'on'
    trigger:
      platform: event
      event_type: device_tracker_new_device
    action:
      - service: notify.ha_hangouts_main
        data_template:
          message: >
            {{ trigger.event.data.host_name }}
            {{ trigger.event.data.entity_id }}
            {{ trigger.event.data.source_type }}
          title: "New Device"
      - service: persistent_notification.create
        data_template:
          title: "New Device"
          message: >
            {{ trigger.event.data.host_name }}
            {{ trigger.event.data.entity_id }}
            {{ trigger.event.data.source_type }}
          notification_id: '{{ trigger.event.data.title }}'
      - service: notify.automation_script_triggers
        data:
          message:
            '{{now().strftime("%Y-%m-%d %H:%M:%S")}} -- new_device_detection'

Traceback (if applicable):
2018-09-05 16:46:35 ERROR (MainThread) [homeassistant.core] Error executing service <ServiceCall persistent_notification.create (c:b4a59dec934348fc80e227a309a44a8d): title=<homeassistant.helpers.template.Template object at 0x7fccbc4f8898>, message=<homeassistant.helpers.template.Template object at 0x7fccbc4f8dd8>, notification_id=>
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/core.py", line 1114, in _event_to_service_call
    service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/persistent_notification/__init__.py", line 121, in create_service
    hass.states.async_set(entity_id, STATE, attr)
  File "/usr/src/app/homeassistant/core.py", line 853, in async_set
    context)
  File "/usr/src/app/homeassistant/core.py", line 618, in __init__
    "Format should be <domain>.<object_id>").format(entity_id))
homeassistant.exceptions.InvalidEntityFormatError: Invalid entity id encountered: persistent_notification.. Format should be <domain>.<object_id>

Additional information:
The hangouts notify works just fine that is in this same automation.  This could just be an issue where persistent_notification doesn't support certain parameters but I am unsure as I cannot find any documentation stating such info.  This error message to me indicates that there is something wrong with the entity_id.  But when the hangouts notify works and sends the notification, it comes in this same format.  "New Device" hostname device_tracker.mac_address.

{{ trigger.event.data.title }} is evaluating to an empty string resulting in an invalid persistent_notification entity_id. The device_tracker_new_device event doesn't have a title property in its data.


Vulkan lookups should use SDL_HashTable

We can rip out our internal hashtable jank now.

Resolved by #214


Updated headers to sentence case

Instead of title case :)
https://sendgrid.com/docs/ui/managing-contacts/building-your-contact-list/

Closes #

Hello @schmeiss,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Hello @schmeiss,Thanks again for the PR!                                         You have earned 5 out of the 5 points needed to receive glorious SendGrid Hacktoberfest swag.                                         Please take a moment to checkout this link to find more issues to get you past the required threshold or to simply continue the celebration.                                         Also, please be sure you have officially registered with us here by November 1, 2018 to qualify.                                         If you have any questions you can email us at<EMAIL_ADDRESS>                                        Thank you and Happy Hacktobering!                                         Team SendGrid


[API. Employee]  When the administrator creates a new employee position, response 200 is not reproduced

Environment:
Windows 10 Pro (22H2)/Google Chrome Версія 110.0.5481.180
Reproducible:
always,
Build found:
12/03/2023
Steps to reproduse:

Choose method POST
Set up https://greencity-ubs.testgreencity.ga/admin/ubs-employee/create-position ( Authorized by bearer token )
Set up name parameter 'any data'
Send request

Actual result
Response 201. Created
Expected result
Respone 200.OK
Test case link:
https://jira.softserve.academy/browse/GC-5635

temporary we deleted this endpoint from our project, so i'll close this task


Add (probably) forgotten type parameters ...

... to the pyobject_native_type_convert macro.
This is needed for rust-numpy to compile.

Nice, thanks!


Implement SA1130

Fixes #1451.
visual studio provides a (local) code fix (without fix all). We probably want to implement one ourself.

I'd like to see a test included for overloads like the following:
void Method(Action action) { }
void Method(Expression<Func<int>> expression) { }

@sharwell I added that test


Bump to Netty 4.1.27.Final

Netty 4.1.27.Final has just been released :-)
Changelogs since 4.1.25.Final:

http://netty.io/news/2018/07/10/4-1-26-Final.html
http://netty.io/news/2018/07/11/4-1-27-Final.html

Unit tests ran with success.

Thanks!


DNS Cache question

Under "Advanced settings" there is "DNS Cache" option.
Can you please explain, is this cache a separate DNS cache that is maintained by dnscrypt-proxy, or is this DNS cache belonging to Windows OS?
I ask this because I want to clear the cache, if it's cache by OS, then simply Clear-DNSClientCache in PowerShell will do, however if it's cache maintained by dnscrypt-proxy, then how do you clear it?

This is an abandoned issue list.
There is anybody other than 'you' the author who can answer your question.
Let me ask you what the relationship between SimpleDnsCrypt and dnscrypt-proxy because I don’t think you know exactly the behavior to clear cache using ordinary DNS software.
Most DNS software will restart itself when a user want to clear its only states set: the cache.
Unfortunately dnscrypt-proxy belongs to ordinary DNS software and SimpleDnsCrypt is just another modern UI for it which spends/maintains more LOCs (source lines of code) than its couple.

For anyone interested I found this issue which partially answers the question:
https://github.com/DNSCrypt/dnscrypt-proxy/issues/228


MUI TreeView is broken

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯

Expected behavior 🤔
A normal working tree
Steps to reproduce 🕹
Steps:

install material ui and go to your index file

import React from "react";
import ReactDOM from "react-dom/client";

import { TreeItem, TreeView } from "@mui/lab";

function Root() {
  return (
    <TreeView>
      <TreeItem nodeId="10" label="OSS" />
    </TreeView>
  );
}

const root = ReactDOM.createRoot(document.getElementById("root")!);

root.render(<React.StrictMode children={<Root />} />);

Context 🔦
Tried to make folder with treeview But couldn't even make a simple TreeView because of internal error
Your environment 🌎

npx @mui/envinfo
  System:
    OS: Windows 10 10.0.19044
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.1.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1266.0), Chromium (103.0.1264.44)
  npmPackages:
    @emotion/react: ^11.9.3 => 11.9.3
    @emotion/styled: ^11.9.3 => 11.9.3
    @mui/base:  5.0.0-alpha.88
    @mui/lab: ^5.0.0-alpha.89 => 5.0.0-alpha.89
    @mui/material: ^5.8.7 => 5.8.7
    @mui/private-theming:  5.8.6
    @mui/styled-engine:  5.8.7
    @mui/system:  5.8.7
    @mui/types:  7.1.4
    @mui/utils:  5.8.6
    @mui/x-date-pickers:  5.0.0-alpha.1
    @types/react:  17.0.47
    react:  17.0.2
    react-dom:  17.0.2

    Default Chrome browser

Please provide a CodeSandbox reproducing the issue. The issue template is a good starting point.


Ref docs landing page for mgmt plane packages are not using the readme

The ref docs for all our new data plane packages use the readme from the package to show for the "Overview" node. The new previews for mgmt plane packages should get the same treatment, but they are not. For example, see the Overview page for @azure/arm-eventhub

Sorry for the delay in response I needed to make sure we were treating these mgmt plane packages the same way we're treating our data plane packages. We are treating these packages in the same way.
In short: NO, this is not a problem... publishing automation handles this scenario.
In long:
When publishing a package we call Update-DocsMsMetadata.ps1 which ensures that the file goes into the right location (GA or preview) based on the package version. The sync_tocs.py script uses reference-unified.yml to generate an accurate ToC based on the list of packages that were onboarded and built by the docs CI build. If a package is not onboarded for a given moniker and documentation isn't generated for that package then entries in reference-unified.yml for that package are ignored.
When @azure/arm-eventhub releases to GA the readme.md file will be generated by the metadata release script and the package will be automatically onboarded to GA by our daily run of Update-DocsMSPackages.ps1.

Hi @ramya-rao-a , I think this issue should have been resolved, see from here  https://docs.microsoft.com/en-us/javascript/api/overview/azure/arm-eventhub-readme?view=azure-node-latest I will close this issue, feel free to let me know if you other comments.


bug: create mview stuck when creating hummock iterator

If we disable the no-shuffle exchange rule (in #5423), creating tpch-q21 mview (tpch_snapshot.slt) will likely be stuck.

Async stack trace:
# 14A -> upstream hash-join
# 14D -> middle-stream hash-join
# 154 -> downstream hash-join

>> Actor 134
[captured 747.071687ms ago]
Actor 134 [22.004078377s]
  Epoch<PHONE_NUMBER>636544 [!!! 21.868077877s]
    HashJoinExecutor<PHONE_NUMBER> (actor 134, executor 340) [!!! 21.868077877s]
      store_create_iter [!!! 21.864077862s]
      store_create_iter [!!! 21.864077862s]
[??? Detached]
  HashJoinExecutor 860000014A (actor 134, executor 330) [!!! 21.868077877s]
    hash_join_barrier_align [!!! 21.868077877s]
      MergeExecutor (actor 134, executor 323) [!!! 21.868077877s]
        LocalInput (actor 146) [!!! 21.868077877s]
        RemoteInput (actor 144) [!!! 21.868077877s]
        RemoteInput (actor 145) [!!! 21.868077877s]
      MergeExecutor (actor 134, executor 328) [!!! 21.868077877s]
        LocalInput (actor 140) [!!! 21.868077877s]
        RemoteInput (actor 138) [!!! 21.868077877s]
        RemoteInput (actor 139) [!!! 21.868077877s]
[??? Detached]
  LocalInput (actor 137) [!!! 21.868077877s]
[??? Detached]
  HashJoinExecutor 860000014D (actor 134, executor 333) [!!! 21.868077877s]
    store_create_iter [!!! 21.864077862s]
    store_create_iter [!!! 21.864077862s]

Related:

#2580

I've checked all await points in the iter_inner and find that all of those are calling the block/meta cache, where there should be no potential stuck problem after fixes in #3911, except for get_compaction_group_id. Further tracing shows that we indeed are stuck here.
>> Actor 2741
[captured 611.720751ms ago]
Actor 2741 [676.998006643s]
  Epoch<PHONE_NUMBER>825856 [!!!<PHONE_NUMBER>52s]
    HashJoinExecutor AB500000154 (actor 2741, executor 340) [!!!<PHONE_NUMBER>52s]
      store_create_iter [!!!<PHONE_NUMBER>73s]
        store_get_compaction_group_id [!!!<PHONE_NUMBER>73s]
      store_create_iter [!!!<PHONE_NUMBER>73s]
        store_get_compaction_group_id [!!!<PHONE_NUMBER>73s]
[??? Detached]
  RemoteInput (actor 2745) [!!!<PHONE_NUMBER>52s]
[??? Detached]
  HashJoinExecutor AB50000014D (actor 2741, executor 333) [!!!<PHONE_NUMBER>52s]
    store_create_iter [!!!<PHONE_NUMBER>46s]
      store_get_compaction_group_id [!!!<PHONE_NUMBER>46s]
    store_create_iter [!!!<PHONE_NUMBER>46s]
      store_get_compaction_group_id [!!!<PHONE_NUMBER>46s]
[??? Detached]
  HashJoinExecutor AB50000014A (actor 2741, executor 330) [!!!<PHONE_NUMBER>52s]
    hash_join_barrier_align [!!!<PHONE_NUMBER>52s]
      MergeExecutor (actor 2741, executor 323) [!!!<PHONE_NUMBER>52s]
        LocalInput (actor 2753) [!!!<PHONE_NUMBER>52s]
        RemoteInput (actor 2751) [!!!<PHONE_NUMBER>52s]
        RemoteInput (actor 2752) [!!!<PHONE_NUMBER>52s]
      MergeExecutor (actor 2741, executor 328) [!!!<PHONE_NUMBER>52s]
        LocalInput (actor 2750) [!!!<PHONE_NUMBER>52s]
        RemoteInput (actor 2748) [!!!<PHONE_NUMBER>52s]
        RemoteInput (actor 2749) [!!!<PHONE_NUMBER>52s]
[??? Detached]
  RemoteInput (actor 2742) [!!!<PHONE_NUMBER>52s]

Could you please help to take a look? @zwang28


Implement Infinite Zoom Exit Image

update gitignore for Visual Studio developers
specify seed for consistent images as needed

I am test the exit  image.
not bad, the exit image is being zoom in from "behind to front", but has a strong edge to the interpol image,

here is my proposal how we can blend the exit image (once fully drawn on screen) with the previous image:
(robot is exit image, female bunny previous image)

result

Algorithm:
When last prompt is being rendered,
begin at next frame (when it becomes smaller)
A:
* draw a soft mask (64 px? adjustable) around the previous image
*  inpaint over masked area, so the prv Image morph together with the exit img
* loop to A until last prompt is 1x1 pixel. then draw the complete exit image.

another example

can help on debugging
https://marketplace.visualstudio.com/items?itemName=elazarcoh.simply-view-image-for-python-debugging


Split bad examples into separate files.

Each file should only contain a single failing test case.
Closes #27

Thank you!


[T3A2][F09-A1] Yuan Wenyi

Ready for review

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.

Please rename your commit according to the changes in the files, after seeing this comment you can close this PR.


Anax version badge fixes ze

Added badges to ZE pages
Fixed Node version number

@JillieBeanSim I corrected the Node version number and added badges to all the ZE articles in Zowe Docs (only one article has badges currently). If you don't want badges on every ZE article, let me know and I can undo. Please review and if you have any advise on how to place both badges in one line, please let me know!


Add PowerDNS provider

What this PR does / why we need it:
This PR adds a PowerDNS provider for DNS01 challenges.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
fixes #282
Special notes for your reviewer:
Based on lego PowerDNS provider.
Release note:

Add PowerDNS DNS01 provider

Thank you for this PR. We're in the process of changing how we handle DNS01 providers that should make the process easier for users and us as maintainers. You can read more about how we plan to handle these here
Unfortunately, this means we will not be reviewing and accepting this PR for the moment. Once we have the webhook implementation up and running, we'll let you know how to set up and get this running.
You can follow along with our webhook implementation at PR #1443

First of all, thanks for this pull request and for your time working on it.
As mentioned in the above comment, we have added a DNS01 provider extension
mechanism to cert-manager that allows out-of-tree DNS01 providers to be
built, including an example repository
to act as a template for how to implement your own providers.
At this time, we don't have the bandwidth nor means to maintain and automatically
test this DNS01 provider, and so I'm going to close this PR and ask that you
port your changes over to the new webhook example format in order to allow
anyone to use your new provider without needing to have it accepted into
the cert-manager codebase.
If in future your plugin has a wide user base and sufficient testing, we
may consider accepting it into the cert-manager project. The exact process
for this is still to be worked out, and we'd like to work with the community
to determine how we should best publish plugins for users :smile:
Again, thank you for your time, and I look forward to hearing your feedback
on the new DNS provider plugin feature!

@zachomedia please consider it, I'd love to use your provider for pdns.

@towolf I will take a look at implementing the webhook for pdns.

@towolf I created https://github.com/zachomedia/cert-manager-webhook-pdns going and it currently seems to work as expected with the latest cert-manager.


Add factor_returns to plot_rolling_sharpe (2)

Addresses #561

Ah I'm sorry, I should've been more explicit. You can close and re-open the same PR. Once you've closed the PR, the button that used to be "Close Pull Request" turns into "Reopen Pull Request" (next to the green "Comment" button). Just so you know!
Supercedes #563

@twiecki ready to merge

Thanks!


Streaming pricing performance

I would strongly suggest changing chunk_size from 1 byte to a typical size of a Price packet. This will introduce a very little delay in packet processing but at the same time it will significantly decrease CPU usage.
The line that needs to be changed is init.py#L186
Subscribe to all instruments and you'll see how hard is the performance hit with iter_lines(1)

Good call, not exactly sure why it was set to 1 in the first place. The fix will show up in the next release.

Performance is quite an essential factor when processing streaming rates and Requests/httplib doesn't seem to handle it well.
There is no "correct" way to implement iter_lines() using blocking I/O, as you always have to bite the bullet and take a guess as to how much data you should read. I would strongly suggest implementing other means of streaming pricing. Protobuf would probably be the best option. Is this something you would be willing to consider?

The next version of the v20 library will leave the default intact and allow you to set the chunk size to whatever you desire through the API context.
As for a non-HTTP based streaming solution, that is really a decision for the product team that is based on the demand for the feature. From a technology perspective, protobuf would make a lot of sense (plus we use it extensively internally).

When do you expect to release next version? Could you please include release notes whenever you release a new build?
How can I express my demand for non-HTTP based streaming solution? Is there a formal procedure to do this?

I'll try to get a new release out tomorrow. There should already be release notes in the repo, found at:
https://github.com/oanda/v20-python/blob/master/src/ChangeLog
Let me get back to you on the product request.

There's Changelog in the repo, that's correct. What I was suggesting you is to include same information within the releases page. It is easier to access information this way.

Still waiting for feedback regarding product request.

I've been told that your best options are:

Post to the forum
Make a request though<EMAIL_ADDRESS>

OK. Thanks.


fix(config): disable Supervision and increase report timeout for Yale Smart Door Lock

@zwave-js-bot approve


Code that could get some coverage

Parts with some lower test coverage

[ ] TargetWithContext.cs - coverage
[x] NetworkSenders/ -  coverage

HttpNetworkSender -> replace WebRequest.Create with custom IWebRequestFactory?

[ ] LogReceiverService/ -  coverage
[ ] (lower prio) AsyncTaskTarget.cs - coverage
[x] (easy) MessageTemplateParameter PositionalIndex coverage
[ ] (easy) ValueFormatter  coverage

[ ] render null
[ ] handle cycle

[x] MessageTemplateParameters IsPositional+IsValidTemplate + TemplateParserException coverage
[x] (low priority, easy) TimeSource tostring
[ ] https://github.com/NLog/NLog/pull/3469 (TypeConverter)

The TypeConverter class, LogLevelTypeConverter, has 88% code coverage via the test LogLevelConvertTest in LogLevelTests. I don't see it in your coverage report so I'm wondering if it actually need more coverage added or if it could already be considered complete. I suppose it might benefit to move the test into its own dedicated test class to make the coverage more obvious.
Could you elaborate on what the these requested test cases mean:

[ ]  (easy) ValueFormatter  coverage

[ ]  render null
[ ]  handle cycle

The TypeConverter class, LogLevelTypeConverter, has 88% code coverage via the test LogLevelConvertTest in LogLevelTests. I don't see it in your coverage report so I'm wondering if it actually need more coverage added or if it could already be considered complete. I suppose it might benefit to move the test into its own dedicated test class to make the coverage more obvious.

I have to check that, maybe it's done already indeed.

Also, could you elaborate on what the these requested test cases mean:

[ ]   (easy) ValueFormatter  coverage

[ ]   render null
[ ]   handle cycle

null prints "NULL", and objects with recursion (cycles) will rendered correctly (and not infinite looping).

Took the two easy ones. I might come back and try some other classes later this week.


[BD-46] feat: move CLI design tokens commands to paragon CLI

Description
Include a description of your changes here, along with a link to any relevant Jira tickets and/or Github issues.
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @monteri!
When this pull request is ready, tag your edX technical lead.

I propose to add descriptions for newly added commands after the help command PR will be merged.
https://github.com/openedx/paragon/pull/2603

@monteri 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


Resizing GUI window

Resizing the GUI window does not appropriately resize the lattice. The cells can become distorted and ugly. Fix graph proportions.

Resolved in release 2.0. The cells now do not dynamically scale as you change window size, but upon resetting the system (using the "STOP" button) the lattice gets properly resized.


Reload Page Automatically

I am using this code to change the filters in the org roam server. But the change is not being reflected in the page right away. It needs to be explicitely reloaded. Is there a way to update the filter automatically in the page, or reload the page as soon as the update is made.
(setq org-roam-server-tags "")
(defun my-org-roam-server-tags()
  "Process org-roam-server-tags"
  (interactive)
  (let* (
         (tags (read-string "Tags: " org-roam-server-tags))
         (tags-temp (cdr (split-string tags "\ [\+]")))
         (plus (mapcar (lambda(a) (string-trim (car (split-string a "\ [\-]")))) tags-temp))
         (tags-temp (cdr (split-string tags "\ [\-]")))
         (minus (mapcar (lambda(a) (string-trim (car (split-string a "\ [\+]")))) tags-temp)))

    (setq org-roam-server-default-include-filters (json-encode (mapcar (lambda (tag) (list (cons 'id tag ) (cons 'parent "tags"))) plus)))
    (setq org-roam-server-default-exclude-filters (json-encode (mapcar (lambda (tag) (list (cons 'id tag ) (cons 'parent "tags"))) minus)))
    (setq org-roam-server-tags tags)
         ))

Unfortunately, the filters are only loaded at the beginning.
See https://github.com/org-roam/org-roam-server/blob/2122a61e9e9be205355c7e2c1e4b65986d6985a5/index.html#L309-L329

Hi @goktug97, i have written some code to make it work, but i am not able to go to a larger subset of notes from a smaller one.


Build error cannot find module providing package github.com/caddyserver/caddy/v2/caddyconfig/httpcaddyfile

I try to build my module https://github.com/git001/caddyv2-upload which was possible with 2.5.0 nowadays I get the following errors.
2022/05/19 12:52:14 [INFO] exec (timeout=0s): /usr/local/go/bin/go get -d -v github.com/caddyserver/caddy/v2
github.com/caddyserver/caddy/v2 imports
	github.com/caddyserver/caddy/v2/caddyconfig/caddyfile: cannot find module providing package github.com/caddyserver/caddy/v2/caddyconfig/caddyfile
github.com/caddyserver/caddy/v2 imports
	github.com/caddyserver/caddy/v2/caddyconfig/httpcaddyfile: cannot find module providing package github.com/caddyserver/caddy/v2/caddyconfig/httpcaddyfile
github.com/caddyserver/caddy/v2 imports
	github.com/caddyserver/caddy/v2/modules/caddyhttp: cannot find module providing package github.com/caddyserver/caddy/v2/modules/caddyhttp
2022/05/19 12:52:14 [FATAL] exit status 1

My golang version
go version
go version go1.18.2 linux/amd64

As this is my first caddy module I'm quite sure that I do something wrong, please can you help me to fix the issue.
Here is the full build output.
--with github.com/caddyserver/caddy/v2=.
2022/05/19 12:52:14 [INFO] Resolved relative replacement github.com/caddyserver/caddy/v2=. to /datadisk/git-repos/caddyv2-upload
2022/05/19 12:52:14 [INFO] Temporary folder: /tmp/buildenv_2022-05-19-1252.3116395694
2022/05/19 12:52:14 [INFO] Writing main module: /tmp/buildenv_2022-05-19-1252.3116395694/main.go
package main

import (
	caddycmd "github.com/caddyserver/caddy/v2/cmd"

	// plug in Caddy modules here
	_ "github.com/caddyserver/caddy/v2/modules/standard"
	_ "github.com/caddyserver/jsonc-adapter"
	_ "github.com/caddyserver/caddy/v2"
)

func main() {
	caddycmd.Main()
}
2022/05/19 12:52:14 [INFO] Initializing Go module
2022/05/19 12:52:14 [INFO] exec (timeout=10s): /usr/local/go/bin/go mod init caddy
go: creating new go.mod: module caddy
go: to add module requirements and sums:
	go mod tidy
2022/05/19 12:52:14 [INFO] Replace github.com/caddyserver/caddy/v2 => /datadisk/git-repos/caddyv2-upload
2022/05/19 12:52:14 [INFO] exec (timeout=10s): /usr/local/go/bin/go mod edit -replace github.com/caddyserver/caddy/v2=/datadisk/git-repos/caddyv2-upload
2022/05/19 12:52:14 [INFO] Pinning versions
2022/05/19 12:52:14 [INFO] exec (timeout=0s): /usr/local/go/bin/go get -d -v github.com/caddyserver/caddy/v2
github.com/caddyserver/caddy/v2 imports
	github.com/caddyserver/caddy/v2/caddyconfig/caddyfile: cannot find module providing package github.com/caddyserver/caddy/v2/caddyconfig/caddyfile
github.com/caddyserver/caddy/v2 imports
	github.com/caddyserver/caddy/v2/caddyconfig/httpcaddyfile: cannot find module providing package github.com/caddyserver/caddy/v2/caddyconfig/httpcaddyfile
github.com/caddyserver/caddy/v2 imports
	github.com/caddyserver/caddy/v2/modules/caddyhttp: cannot find module providing package github.com/caddyserver/caddy/v2/modules/caddyhttp
2022/05/19 12:52:14 [FATAL] exit status 1

Please post the actual command you're running. We can't confirm unless we see the xcaddy build command.

--with github.com/caddyserver/caddy/v2=.

This reads to me like you're trying to replace Caddy itself with your plugin. That doesn't make sense. I think you wanted to do --with github.com/git001/caddyv2-upload=.


Delete Study: Not redirecting after request is done, stays on study page.

Delete a study
Not getting redirected, stays on study details page even though study is successfully deleted
F5 causes "Not found" error message
Trying to delete again also causes "Not found" error message

Did you have a datasets/sandbox in the study?


Recoverymodel updates and tests

tests pass but do broke a few builds /cc @niphlod

aargh, I thought I fixed it. lemme prep a PR real fast.

thanks so much! 💞


chore: document version an emdpoint was introduced in ...

... via api_endpont macro argument.
Fix #4190

Seems like CI is failing due to this PR https://github.com/fedimint/fedimint/actions/runs/7820733924/job/21336093216?pr=4267


How can generate pagetables of 2-stage in EL2?

I want to generate pagetables of stage-1 and stage-2 in EL2.
But I do not know how to do.
Please give some examples. Thanks a lot!

Well it's quite easy to do! It's called RTFM (read the f-ing manual!)


Addressing https://github.com/hwchase17/langchain/issues/301

https://github.com/hwchase17/langchain/issues/301

We are addressing issues with too many mapping of parallel jobs next, to avoid errors such as this:
>InvalidRequestError: Too many parallel completions requested. You submitted 34 prompts, but you can currently request up to at most a total of 20). Please contact us through our help center at help.openai.com for further questions.

After https://github.com/hwchase17/langchain/pull/338/commits/35bf3e230afc118fac37eb5f08fb54f682f31fd1 I tested and now this works with > 20 sub-docs, too.


Your session has been disconnected

I am trying to execute python scripts via shell (powered by Datacamp) included at https://www.learnpython.org/
However, I am always getting Your session has been disconnected error.
Here is a screenshot of console error which I am getting on hitting the run button:

Hi. I am experiencing the same problem, and it seems we are not the first ones #397 .
I'm curious how @MichaelJCole has solved it there.
@bakera81  do you know if we need a DataCamp account to run these examples?

Hi all, you don't need a DataCamp account to be able to run the code chunks on sites like Learn Python. I unfortunately can't reproduce the issue here. The session disconnecting is likely an issue with DataCamp Light itself - if refreshing the page or trying a different browser doesn't do the trick, please file an issue on the DataCamp Light project here: https://github.com/datacamp/datacamp-light/issues

I had been experiencing the same problem using the Brave Browser for Windows, until I turned off's Brave's site-specific "shields" for the site. Once I did that, the problem went away.
The site-specific "shields" can be accessed by clicking the Brave lion icon to the right side of Brave's address bar panel. [See How do I configure global and site-specific Shields settings?]

While using the Python tutorial today, I looked into this some more, and isolated what was causing the problem for me, at least, in Brave.
Brave's shields have 3 options regarding cookies:

Block cross-site cookies
Block cookies
Allow all cookies

I think this originally had been set to

Block cross-site cookies

but the only option which seems to work for this is:

Allow all cookies

I wonder if blocked cookies might also be what's causing this problem for garvit1608  and cipri-tom.
When a session ends up being disconnected because of blocked cookies, maybe the message could be changed to let the user know that's the cause of the problem. baker81 - Should I file an issue on the DataCamp Light project? Thanks.


New package: LibAwsCommon v1.0.0

Registering package: LibAwsCommon
Repository: https://github.com/JuliaServices/LibAwsCommon.jl
Created by: @Octogonapus
Version: v1.0.0
Commit: 9a7f198422810b467298cb7d738ff5f0e6588417
Reviewed by: @Octogonapus
Reference: https://github.com/JuliaServices/LibAwsCommon.jl/commit/9a7f198422810b467298cb7d738ff5f0e6588417#commitcomment-141286847

[noblock]
This is the follow-up to https://github.com/JuliaRegistries/General/pull/101851 using the new design and naming scheme.


chore: github action

post-procedure for both pull request and commit

chore/github-action : 88bf8eb53ef97a5ce2d5da7b28724df42a94d914


feat: add text input component

Feature request
Add text input component.
Documentation: https://www.decathlon.design/726f8c765/p/31121d-text-input/b/18ceeb
Figma: https://www.figma.com/file/zDZIyayUlr1yTWrsi7cFoo/?node-id=150%3A3410
Checklist:

[x] CSS
[ ] Web Components
[ ] React @gabbloquet 🚧 (You can reach me out<EMAIL_ADDRESS>[x] Svelte
[ ] Vue

Hi, I work on the text input component for react in Vitamin right now, I asked myself a question : can we suggest some sizes for the component ?  If it's the case which ones ? I don't find this spec on figma.

Hi @MatthiasCartelDkt, for contributing guide on design part, you can follow this page: https://www.decathlon.design/726f8c765/p/24ef08-contributing/b/237af4

I'm working on React part 🚀


Add support for dynamically imported translation resources

Adds a proper localize-dynamic mixin to simplify individual component complexity. Docs have been updated with example usage.
Dependent upon:
~https://github.com/Brightspace/brightspace-integration/pull/3350~
~https://github.com/Brightspace/eslint-config-brightspace/pull/39~

I realized we don't actually need supportedLanguages at all, because rollup replaces the import with a switch. If the language isn't truely supported (a file exists!) there is no case and it falls through and loops to the next language. If someone is using this outside BSI and for whatever reason can't use a build system that does the same, they're no worse off. They can either be ok with 404s, handle them themselves in their importFunc, or simply use the Manual method instead.


Tutorials guides

GCP Python section has been updated and finished (for now)
Added a section for the NGI catalog and how to link aerials in QGIS and Geoserver for own use - data is freely available.
Minor list fixes to GIS resources.
GCP python sections

NGI catalog

@timlinux Finished the GCP section, had some sections outstanding for Python. This should be up-to-date with the guide I put together while learning and using GCP.
Added a section on how to add NGI aerials for SA - very nice 50cm aerials! Other data also available, but used the aerials as an example as it covers the whole of SA.
Let me know if there are mistakes I've missed.

Wow @vermeulendivan ! Great work  - I took a speed read through it. What do you think about getting one of the interns to run through it and provide any corrections / feedback?

@timlinux That will be great! I will also give it another read through now that its been merged, might (likely will) find issues myself. But having someone going through whom didn't put it together will likely notice issues I don't, or point out if something is vague.
Recently started a c++ course(s), so might start adding some info on c++, maybe just provide resources on where a person can learn the language.


Add support for external/remote signers

This allows for a value signer in values.yaml...
accounts:
  archive-baking-node-0:
    bootstrap_balance: '4000000000000'
    is_bootstrap_baker_account: true
    key: edpk......
    signer: http://<POD-NAME>.<SERVICE-NAME>.<NAMESPACE>:6732/
    type: secret

That allows for an external/remote signer, including a signer in a different namespace.  This is specifically related to our securing the hot wallet, and eventually the KMS wallet. We will restrict who can shell into the signer pod by separating it out into its own namespace.
Note - Magic numbers 0x01 will need to be parameterized for testnets (dailynet for example), as activation is blocked with the current functionality. @nicolasochem is currently working on a PR for this https://github.com/oxheadalpha/tezos-k8s/blob/master/charts/tezos/scripts/remote-signer.sh#L9
Tested both same namespace (deafult without url) and separate namespace signers functionality.

I addressed some review comments. The suggestion to remove the hash from the URL has been implemented. The suggestion to deprecate key types in values.yaml has been implemented in another PR which is now the target of this one.
We still don't have a solution for passing signer env vars. Aryeh has one in his branch which has not pushed yet. So, for the time being we need to carry an additional commit to allow the additional magic byte 0x01 for activation.


feat: add option to generate HSM keys

here is the reference https://github.com/GoogleCloudPlatform/python-docs-samples/blob/9531bf469545820624a2ef0fa1a2aaa965dc2c99/kms/snippets/create_key_hsm.py

added in #11


Enhancementadd datelikev2 type support for fold constant.

Proposed changes
Issue Number: close #xxx
Problem summary
add datelikev2 type support for fold constant.
date_add / years_add / mouths_add / days_add / hours_add / minutes_add / seconds_add and xxx_sub.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[x] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.34 seconds
stream load tsv:          449 seconds loaded<PHONE_NUMBER>9 Bytes, about 158 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          72 seconds loaded<PHONE_NUMBER> Bytes, about 14 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230331075112_clickbench_pr_123244.html


Current Location

This wants to be plugin and not enabled by default in the script for the default view.

The default view checks for a non truthy locator key value in the locale before adding the locator button to the button column.
This can also be added as a locator plugin for any other view as the locator key value in the locale would trigger this plugin.


Update Buildvana.Sdk for saner CI

Types of changes

[ ] Bugfix
[ ] Enhancement (new and/or improved behavior)
[ ] Refactoring (no functional changes)
[ ] Code style update (no functional changes)
[x] Dependencies added, updated, or removed
[ ] Build related changes
[x] CI related changes
[ ] Documentation update
[ ] Other (please describe below)

Proposed changes / fixed issues

Update Buildvana.Sdk 1.0.0-alpha.7 -> 1.0.0-alpha.9
Remove setup of an additional .NET Core version in CI workflow, as the build tools (namely ExportAnnotation) no longer need it.

Checklist

[x] My contribution is either my original work, or comes from projects with an MIT-compatible license, in which case I have updated the THIRD-PARTY-NOTICES file accordingly
[ ] I have added and/or updated related documentation (if applicable)
[ ] I have updated the "Unreleased changes" section in CHANGELOG.md according to the modifications I made

Other information

Codecov Report

Merging #14 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #14   +/-   ##
=======================================
  Coverage   66.66%   66.66%
=======================================
  Files           3        3
  Lines         105      105
  Branches       21       21
=======================================
  Hits           70       70
  Misses         25       25
  Partials       10       10

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7bc0b83...1924592. Read the comment docs.

Let's recap:

builds still fail with .NET 5.0-rc1, apparently [by no fault of our own[(https://github.com/tenacom/Cecil.XmlDocNames/pull/11#issuecomment-704071805)
the Buildvana.Sdk update made Ubuntu builds succeed at least with .NET Core 3.1
LGTM can build the solution at last! The problem was that by default LGTM does a nuget restore before building, then builds with MSBuild 15.0. Their versions of nuget and MSBuild don't support centrally-managed package versions, so they were using terribly old (and incompatible) versions of dependencies (thanks NuGet for defaulting to the oldest version of everything!)
actions/labeler fails. The error comes from the Minimatch constructor, that apparently is passed an object instead of an array of strings. Pulling actions/labeler from the main branch instead of the 2.2.0 tag would somewhat help in debugging the issue, as it now uses JSON.stringify instead of toString in the debug message that shows the globs being evaluated. Since after changing the labeler version in the workflow file GitHub seems to be still using 2.2.0, there's no choice but to merge this PR and open a new one to try the updated workflow.


Donation page HTTPS Certificate is out of date

I tried to donate via the website by clicking the donate website and my browser sent me a warning saying that the site is insecure and is not HTTPS.

@SolarDesalination thanks for telling!
You are right, https://donate.qgis.org/ has (accidently) the certificate of https://hangelog.qgis.org
ping @timlinux @dimasciput

Hi @rduivenvoorde @SolarDesalination ,
The page is now fixed.

Cool, thanks @dimasciput for the prompt actions!
Closing


GridFS support no longer exists. If you are using GridFS, you cannot upgrade.

Really?! I can not use Grid FS in 4.0.0?
I read about in on page http://mongoid.org/en/mongoid/docs/upgrading.html
Or this page is stale?

GridFS will be once again supported in Mongoid 5, as we are switching to the official Ruby driver at that point.


fix a bug with  search value is '0'

in php
empty('0') == true
so,when search a field value with '0',this function did not work;

good catch! thanks for the contribution...


version a file to capture the java version for the project

should this encourage a single approach to this for consistency, or would it be better to enable multiple options as choices?
Known Options

SDKman
jEnv

Considerations

compatibility with the setup-java action
ability to leverage renovate to prevent the version from growing stale

possibly also worth considering asdf, which renovate does support

sdkman is not supported natively by setup-java, but there is a community supported action

it looks like the intention of the setup-java action is to only ever support the .java-version file (used by jenv)

https://github.com/marketplace/actions/java-info-action supports jenv and asdf approaches


Refract files

I am calling everyone because I am doing major refraction to remove all addressbook instances in the project to ClinicIO. And so i will change the package naming if possible.

Pull Request Test Coverage Report for Build 299

5 of 5 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.2%) to 87.703%

Totals

Change from base Build 287:
1.2%

Covered Lines:
1890

Relevant Lines:
2155

💛  - Coveralls

Change all instances of addressbook to clinicio in the src project

Do not merge this. I need approve from all of u then can merge coz its major refracting.

Just to clarify the term you used, you mean refactoring right? (as opposed to refracting)

Oops its refractoring

refactor bro. Just wanna make sure the terms are consistent across all commits/PRs so in future those changes can be found easily (ctrl + f, etc)


EnumerateStereoisomers should remove non-abs enhanced stereo from results

Describe the bug
In [7]: m = Chem.MolFromSmiles('O[C@H](Br)[C@H](F)C |&1:1,3|')

In [8]: set(Chem.MolToCXSmiles(x) for x in EnumerateStereoisomers.EnumerateStereoisomers(m))
Out[8]: {'C[C@@H](F)[C@H](O)Br |&1:1,3|', 'C[C@H](F)[C@@H](O)Br |&1:1,3|'}

Given that one of the purposes of EnumerateStereoisomers() is to give all the individual stereoisomers which are described by a set of StereoGropus, I believe that the results should no longer have the enhanced stereo.
Configuration (please complete the following information):

RDKit version: release and master
OS: all

@ricrogz , @d-b-w : I think we've talked about this in the past, but I want to check that you agree with me here.

I don't remember if we talked about this, but it makes sense to me.

I think that this is probably the right thing to do - stereoisomer enumeration is generating all the real structures possible...
I think that there is some use case where people want to know what the source molecule was after a long workflow, but I think that there are probably better ways to do that.
Fixing this will break RegistrationHash's hacky canonicalization of enhanced stereochemistry... But I assume that you're raising this issue because you intend to remove the stereogroups in enumeration when canonicalization also canonicalizes stereo groups.