Adding bullet-kafka code.

Coverage increased (+98.5%) to 98.54% when pulling 5bc4ccb04e0a70ceced808a475b54e15797cc67b on ShriramKumar:bullet-kafka into ddb952612c886f14143d69ccd3756ef3c2167fe9 on yahoo:master.


prisma2 lift up appears to work without prisma lift save then fails spectacularly

$ ./node_modules/.bin/prisma2 introspect --pg-host localhost --pg-password "" --pg-user m --pg-schema public --pg-db prisma-blog
$ mv datamodel* schema.prisma
$ ./node_modules/.bin/prisma2 lift up

 ERROR  Oops, an unexpected error occured!
Error in migration engine: thread 'tokio-runtime-worker-0' panicked at 'Deserializing the database migration failed.:
Error("missing field `original_steps`", line: 0, column: 0)', src/libcore/result.rs:999:5
stack backtrace:
   0: std::panicking::default_hook::{{closure}}
 ERROR  Oops, an unexpected error occured!
Error in migration engine: thread 'tokio-runtime-worker-0' panicked at 'Deserializing the database migration failed.:
Error("missing field `original_steps`", line: 0, column: 0)', src/libcore/result.rs:999:5
stack backtrace:
   0: std::panicking::default_hook::{{closure}}
   1: std::panicking::default_hook
   2: migration_engine::main::{{closure}}
   3: std::panicking::rust_panic_with_hook
   4: std::panicking::continue_panic_fmt
   5: rust_begin_unwind
   6: core::panicking::panic_fmt
   7: core::result::unwrap_failed
   8: <sql_migration_connector::SqlMigrationConnector as migration_connector::MigrationConnector>::deserialize_databas
e_migration
   9: <migration_engine::commands::list_migrations::ListMigrationStepsCommand as migration_engine::commands::command::
MigrationCommand>::execute
  10: <migration_engine::api::MigrationApi<C,D> as migration_engine::api::GenericApi>::list_migrations
  11: migration_engine::api::rpc::RpcApi::create_sync_handler
  12: tokio_executor::enter::exit
  13: tokio_threadpool::blocking::blocking
  14: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
  15: futures::future::chain::Chain<A,B,C>::poll
  16: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll
  17: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
  18: futures::future::chain::Chain<A,B,C>::poll
  19: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll
  20: <futures::future::map::Map<A,F> as futures::future::Future>::poll
  21: <futures::future::either::Either<A,B> as futures::future::Future>::poll
  22: <futures::future::map::Map<A,F> as futures::future::Future>::poll
  23: <futures::future::map_err::MapErr<A,F> as futures::future::Future>::poll
  24: <futures::stream::and_then::AndThen<S,F,U> as futures::stream::Stream>::poll
  25: <futures::stream::forward::Forward<T,U> as futures::future::Future>::poll
  26: <futures::future::map::Map<A,F> as futures::future::Future>::poll
  27: <futures::future::map_err::MapErr<A,F> as futures::future::Future>::poll
  28: futures::task_impl::std::set
  29: std::panicking::try::do_call
  30: __rust_maybe_catch_panic
  31: tokio_threadpool::task::Task::run
  32: tokio_threadpool::worker::Worker::run_task
  33: tokio_threadpool::worker::Worker::run
  34: std::thread::local::LocalKey<T>::with
  35: std::thread::local::LocalKey<T>::with
  36: tokio_reactor::with_default
  37: tokio::runtime::threadpool::builder::Builder::build::{{closure}}
  38: std::thread::local::LocalKey<T>::with
  39: std::thread::local::LocalKey<T>::with
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Please help us improve Prisma 2 by submitting an error report.
Error reports never contain personal or other sensitive information.
Learn more: https://pris.ly/d/telemetry

I guess  prisma2 lift save also doesn't work:
$ ./node_modules/.bin/prisma2 lift save

 ERROR  Oops, an unexpected error occured!
Error in migration engine: thread 'tokio-runtime-worker-0' panicked at 'Deserializing the database migration failed.:
Error("missing field `original_steps`", line: 0, column: 0)', src/libcore/result.rs:999:5
stack backtrace:
   0: std::panicking::default_hook::{{closure}}
 ERROR  Oops, an unexpected error occured!
Error in migration engine: thread 'tokio-runtime-worker-0' panicked at 'Deserializing the database migration failed.:
Error("missing field `original_steps`", line: 0, column: 0)', src/libcore/result.rs:999:5
stack backtrace:
   0: std::panicking::default_hook::{{closure}}
   1: std::panicking::default_hook
   2: migration_engine::main::{{closure}}
   3: std::panicking::rust_panic_with_hook
   4: std::panicking::continue_panic_fmt
   5: rust_begin_unwind
   6: core::panicking::panic_fmt
   7: core::result::unwrap_failed
   8: <sql_migration_connector::SqlMigrationConnector as migration_connector::MigrationConnector>::deserialize_databas
e_migration
   9: <migration_engine::commands::list_migrations::ListMigrationStepsCommand as migration_engine::commands::command::
MigrationCommand>::execute
  10: <migration_engine::api::MigrationApi<C,D> as migration_engine::api::GenericApi>::list_migrations
  11: migration_engine::api::rpc::RpcApi::create_sync_handler
  12: tokio_executor::enter::exit
  13: tokio_threadpool::blocking::blocking
  14: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
  15: futures::future::chain::Chain<A,B,C>::poll
  16: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll
  17: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
  18: futures::future::chain::Chain<A,B,C>::poll
  19: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll
  20: <futures::future::map::Map<A,F> as futures::future::Future>::poll
  21: <futures::future::either::Either<A,B> as futures::future::Future>::poll
  22: <futures::future::map::Map<A,F> as futures::future::Future>::poll
  23: <futures::future::map_err::MapErr<A,F> as futures::future::Future>::poll
  24: <futures::stream::and_then::AndThen<S,F,U> as futures::stream::Stream>::poll
  25: <futures::stream::forward::Forward<T,U> as futures::future::Future>::poll
  26: <futures::future::map::Map<A,F> as futures::future::Future>::poll
  27: <futures::future::map_err::MapErr<A,F> as futures::future::Future>::poll
  28: futures::task_impl::std::set
  29: std::panicking::try::do_call
  30: __rust_maybe_catch_panic
  31: tokio_threadpool::task::Task::run
  32: tokio_threadpool::worker::Worker::run_task
  33: tokio_threadpool::worker::Worker::run
  34: std::thread::local::LocalKey<T>::with
  35: std::thread::local::LocalKey<T>::with
  36: tokio_reactor::with_default
  37: tokio::runtime::threadpool::builder::Builder::build::{{closure}}
  38: std::thread::local::LocalKey<T>::with
  39: std::thread::local::LocalKey<T>::with
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Please help us improve Prisma 2 by submitting an error report.
Error reports never contain personal or other sensitive information.
Learn more: https://pris.ly/d/telemetry


chore: use latest version of monero-dashboard

Hi @cachho, thank you for the PR!
I already went ahead and did this almost at the exact same time as you opened your PR.
621e202


Image scale preserving aspect ratio with Spannable logic

Hello, thanks for the library. I have a question about image size.
According to default ImageSizeResolverDef implementation for Spannable case, my image is cut off. I want my image to be scaled preserving aspect ratio. Is it possible to implement?
This is cut image:

This is full image:

Hello @CraggyHaggy ,
It definitely should be as you mention, image should be scaled to fit width of a TextView (whilst keeping the ratio). Unfortunately this piece of logic was mistakenly excluded from previous releases. But the good thing is I have identified and fixed it in SNAPSHOT version. Can you please check with it? 2.0.0-SNAPSHOT (information of how to add it to your project is in the README)
Also, I want to notice, that you can use HTML <img> tag and specify width attribute (it accepts percent units):
<img src="my-image.JPEG" width="100%" />

But in current stable release it also might not work as expected (see #52 for reference). But, again, it is fixed in SNAPSHOT version, which will be released soon (at least I hope so).
There is also an option of implementing own ImageSizeResolver which can handle all logic that you might have (see documentation for more info)

I will try this logic in SNAPSHOT version. Thandk for the advice.

np 👍


Updated fork to use v0.3.11 & made points public

this commit has our changes

I think I found a way to make the msm api work against the regular blst fork:
@ToufeeqP  poly-multiproof references upstream blst now:
https://github.com/Aphoh/poly-multiproof/blob/7beaeb68d6fc866d464e724851d469998ff0c2e3/Cargo.toml#L20
See the logic put together in the MSMEngine wrapper I built around both blst and arkworks:
https://github.com/Aphoh/poly-multiproof/blob/7beaeb68d6fc866d464e724851d469998ff0c2e3/src/msm.rs#L220
Not sure where else you're using this, but it might be helpful to pull in that file (or just use the MSMEngine api from poly-multiproof).

I think I found a way to make the msm api work against the regular blst fork:
@ToufeeqP poly-multiproof references upstream blst now: https://github.com/Aphoh/poly-multiproof/blob/7beaeb68d6fc866d464e724851d469998ff0c2e3/Cargo.toml#L20
See the logic put together in the MSMEngine wrapper I built around both blst and arkworks:
https://github.com/Aphoh/poly-multiproof/blob/7beaeb68d6fc866d464e724851d469998ff0c2e3/src/msm.rs#L220
Not sure where else you're using this, but it might be helpful to pull in that file (or just use the MSMEngine api from poly-multiproof).

Hey @Aphoh, thanks for looking into it! I believe this is also being used in avail-core, but we specifically needed blst version 0.3.11 due to deps in the bridge pallet. However, we’ve decided not to use that library directly in the pallet for now, so I’ll go ahead and close this PR. If we need it in the future, I can reopen it


Carla on WSL2 with GUI rendering

Hi I'm just filling this for the records if someone want to use Carla on WSL2 with GUI rendering.
This guide was very helpful to me for the audio setting:
https://carette.xyz/posts/setup_sound_video_wsl2/
For the video you need a custom lavapipe:
https://github.com/gnsmrky/wsl-vulkan-mesa
The readme guide says to set the DISPLAY setting at 1. That doesn't worked for me. I suggest instead:

leave the setting in VcXsrv at -1
tick "disable access control" in VcXsrv
in WSL export DISPLAY=$(ip route | awk '/^default/{print $3}'):0
(as explained here https://github.com/gnsmrky/wsl-vulkan-mesa/issues/3)

(The prerequisite is a correct driver setup for your GPU in  windows to comunicate with WSL.)
I tested the behaviour just launching ./CarlaUE4.sh
(if you don't want the renderings just add -RenderOffscreen and you are done)

Troubleshooting

if you are seeing the black screen that opens and closes immediately with a segmentation fault like

Malloc Size=65538 LargeMemoryPoolOffset=65554
CommonUnixCrashHandler: Signal=11

check the DISPLAY env variable being setted in accordance with VcXsrv

if you have a message of permission denied it's probably fauult of the Nvidia driver, as people suggest on internet. Someone says that strange resolutions on windows or not in accordance with the native one of the screen cause that, others solved by updating the drivers. In my case was having two screen. I disabled the secondary screen and all works fine.

CARLA version: 0.9.13
Platform/OS:  Windows 11, 22H2, Build: 22623.730
WSL2: Debian GNU/Linux 11 (bullseye)
I hope this saves someone else some time.

Can you render CARLA using all of your GPU capabilities? I followed the links and I can get a render of CARLA from wsl, but it doesn't seem to be able to access the GPU in my system and is running very slow. I have the proper Nvidia drivers installed as well.

No, actually the last time I tried I had the same problem and I rollback to the Windows version 😓

For anyone trying to use carla in wsl2, I suggest running the carla server in windows and running client in WSL. This works perfect for me.

For anyone trying to use carla in wsl2, I suggest running the carla server in windows and running client in WSL. This works perfect for me.

Could you please describe the steps to do it?

Download the Carla server of Win version and start the Win server instead of Linux server.
In your client script, change the "localhost" to the ip of your Win.
Run your script in wsl and the client will connect to the Win server.

Download the Carla server of Win version and start the Win server instead of Linux server.
In your client script, change the "localhost" to the ip of your Win.
Run your script in wsl and the client will connect to the Win server.

connecting to Carla server...
WARNING: Version mismatch detected: You are trying to connect to a simulator that might be incompatible with this API
WARNING: Client API version     = 0.9.6
WARNING: Simulator API version  = baf43b07
I've run into this problem. I was wondering if you have done anything else to fix this? Because Win doesn't have carla 9.6

Download the Carla server of Win version and start the Win server instead of Linux server.
In your client script, change the "localhost" to the ip of your Win.
Run your script in wsl and the client will connect to the Win server.

connecting to Carla server... WARNING: Version mismatch detected: You are trying to connect to a simulator that might be incompatible with this API WARNING: Client API version = 0.9.6 WARNING: Simulator API version = baf43b0
I've run into this problem. I was wondering if you have done anything else to fix this? Because Win doesn't have carla 9.6

Hey last time I had a similar error it was because i needed to use Python 3.8, try running the client in a virtual env with conda

Do we still need a VcXsrv on Windows to use Carla on WSL2 when WSL2 now actually support GUI application?


⚠ Turnos 24x7 has degraded performance

In 53155ea, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1248 ms

Resolved: Turnos 24x7 performance has improved in 982007a.


Add line break to end of file

Missing line break causing build to fail

Merging this to fix the build.


add MongoDB chart

@k8s-bot ok to test

ICYMI we already have a chart in incubator for mongo with replicasets. We should rename that chart to mongo-replicaset and set the chart description properly before merging this.

@viglesiasce agreed, we should rename it adding a -petset, -statefulset or -clustered postfix in this PR. Any particular preference to which it should be? -clustered is more general, could there be a usecase for someone wanting a clustered using multiple deployments vs. StatefulSet?

The feature in mongo that it is using is literally called replicaset so we should use that as the suffix.

@viglesiasce Oh right, yeah. I'm a little hesitant that this will confuse other like it confused me though, but I guess an end-user will be thinking more about MongoDB than Kubernetes resource types.

PR has been updated to rename the existing mongodb chart to mongodb-replicaset

@sameersbn can you fix the conflict?

have rebased the PR to resolve the conflicts and also updated the docker image version used in the chart.

ping!

I tested this and found that the new mongodb chart works well but the old one is failing to install due to the following:
installing config scripts into /work-dir
installing mongod.conf into /config
chown: invalid user: 'mongodb:mongodb'

I'll get an issue open and assign to @foxish.

@k8s-bot e2e test this

@prydonius @lachie83 LGTM


make natdnshostresolver1 and natdnsproxy1 easily configurable via environment variables

would it be possible to expose natdnshostresolver1 and natdnsproxy1 through environment variables?
we have a large user base and having all of them run the required virtualbox commands to enable these options is unwieldy.
it'd be nice to tell our users to set environment variables so boot2docker will work out of the box for users on vpn.
thanks
References:
https://github.com/boot2docker/boot2docker-cli/pull/316
https://github.com/boot2docker/boot2docker-cli/pull/320

:+1:  In our testing, in "NAT DNS Proxy" mode the DNS performance is good enough, and not having to explain why people's containers are broken whenever they switch networks would be a huge benefit.

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).


Always show scrollbars (DynamicScrollbars)

[x] I have signed the Contributor License Agreement.
[ ] This pull request is related to an issue.

/azp run

/azp run

/azp run

/azp run

/azp run


Refactor to try to simplify the config and build chain

Closing this due to inactivity. If we want to do this, we can go through the changes and reimplement on latest master.


Miscellaneous notes on notes.md

https://github.com/brson/wasm-opt-rs/blob/aad563327f248190a17ad48de8e0a3f667b76597/notes.md#L732-L735
It doesn't necessitate it, you can write them as self: Pin<&mut ModuleReader> instead of self: Pin<&mut Self> if you want, even with multiple extern types in the block. Using a block per type is a good idiom though.

https://github.com/brson/wasm-opt-rs/blob/aad563327f248190a17ad48de8e0a3f667b76597/notes.md#L754-L764
This sounds like after going high enough in the API, far enough removed from the original incorrectly-nonconst method, things happened to work out. It's great that it worked out but I suspect you got somewhat lucky here regarding the specific structure of this API.
Generally you would want to fix an incorrectly-nonconst situation at as low a level as possible, as close as possible to the original incorrect-nonconst C++ code. A more general purpose idiom for binding incorrectly-nonconst functions safely using cxx is to pass &UniquePtr<T> from Rust to C++, receive it as std::unique_ptr<T> const& in C++, then use T* operator->() const (https://en.cppreference.com/w/cpp/memory/unique_ptr/operator*) which turns a const unique_ptr into a non-const T.
// lib.rs

extern "C++" {
    type Thing;

    fn incorrectly_nonconst(thing: &UniquePtr<Thing>, arg: bool) -> i32;
}

// lib.cpp

int32_t incorrectly_nonconst(std::unique_ptr<Thing> const&, bool arg) {
    return thing->incorrectlyNonconst(arg);
}

https://github.com/brson/wasm-opt-rs/blob/aad563327f248190a17ad48de8e0a3f667b76597/notes.md#L906-L911
Yep, and the way to avoid a copy is by passing Pin<&mut CxxString> from Rust to C++, receiving it as std::string&, and calling std::move. let_cxx_string! (which you are already using) produces a local binding of type Pin<&mut CxxString>, so the deref from that to &CxxString in your Rust code is what forces a copy to be done afterward in C++.

https://github.com/brson/wasm-opt-rs/blob/aad563327f248190a17ad48de8e0a3f667b76597/notes.md#L912-L915
You can plug in your own catching logic to make C++ catch any kind of type on all signatures in the binding. See the very bottom of https://cxx.rs/binding/result.html. You'd stick the following somewhere in your shims.h or any other header include!ed in the FFI extern block:
namespace rust::behavior {
  template <typename Try, typename Fail>
  static void trycatch(Try &&func, Fail &&fail) noexcept try {
    func();
  } catch (const std::exception &e) {
    fail(e.what());
  } catch (const wasm::ParseException &e) {
    fail(???);
  } catch (const wasm::MapParseException &e) {
    fail(???);
  }
}

This sounds like after going high enough in the API, far enough removed from the original incorrectly-nonconst method, things happened to work out. It's great that it worked out but I suspect you got somewhat lucky here regarding the specific structure of this API.

This is true. We do all our work in one big blast, in a run method. The underlying const correctness doesn't matter because it never escapes this function. I'll try to add some nuance to the text.

Generally you would want to fix an incorrectly-nonconst situation at as low a level as possible, as close as possible to the original incorrect-nonconst C++ code. A more general purpose idiom for binding incorrectly-nonconst functions safely using cxx is to pass &UniquePtr<T> from Rust to C++, receive it as std::unique_ptr<T> const& in C++, then use T* operator->() const (https://en.cppreference.com/w/cpp/memory/unique_ptr/operator*) which turns a const unique_ptr into a non-const T.

I filed https://github.com/brson/wasm-opt-rs/issues/104 to try this in a future release. I think I can explain it in the blog post.

Generally you would want to fix an incorrectly-nonconst situation at as low a level as possible, as close as possible to the original incorrect-nonconst C++ code. A more general purpose idiom for binding incorrectly-nonconst functions safely using cxx is to pass &UniquePtr<T> from Rust to C++, receive it as std::unique_ptr<T> const& in C++, then use T* operator->() const (https://en.cppreference.com/w/cpp/memory/unique_ptr/operator*) which turns a const unique_ptr into a non-const T.

Can this pattern be adapted to work for non-const methods, or does this require operating only on free functions ?

You'd need the wrapper to be a free function because C++ member functions don't have anything similar to Rust self: &Box<Self> methods receivers. But the underlying API called by the wrapper function can be a member function.

I've also filed an issue https://github.com/brson/wasm-opt-rs/issues/107 to avoid string copies in shims.

Ok, I believe I have addressed all issues here. Everything is reflected in the blog post, even if some I have punted to a future milestone to actually resolve in the code.
Thank you very much for your help.


Theme disregarded when Panel:True

Home Assistant release with the issue:

HA 0.97.0
HassOS 2.12
Supervisor 172
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.):

Hassio
Component/platform:

Lovelace/Themes
Description of problem:
When a view in Lovelace has "panel" set to "true", the view will disregard the theme configured in favor of the default theme
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
  - title: flowers
    id: 5
    theme: BlueNight
    panel: true
    cards:

Traceback (if applicable):

Additional information:
By setting "panel" to "false", saving, and refreshing, the theme is applied. I edit lovelace in YAML mode.

This is fixed in 98


Ensure that tags work on the gateway

User story

Story

As a user of a Swarm gateway, I want to know the status of my upload, such that I know whether my upload succeeded
Acceptance criteria

Tags enabled in gateway mode
Old tags are intelligently flushed

Background

Tags are disabled in the gateway mode since old tags are not flushed and hence there might eventually be too many tags, rendering the gateway unusable. The completion of this issue is to solve this underlying issue, such that tags can be exposed in the gateway mode.
Tasks

Task
Assignee
Done (1), or 0

Related: #1530

if we enable tags on gateway mode, they might conflict and someone would have to periodically flush and clean them. also, with postage stamps in place i'm not sure how relevant is this anymore

I just now discovered that with every upload you automatically creates a tag and return it in the response header. Is this behaviour also present in Gateway mode? (I did not manage to test it) If so, maybe we don't need to have the ability to create tags, but only to query their status in the Gateway mode...

The bug that @AuHau mentioned is already fixed. The tags could be accessed through the gateway with the restricted APIs. Closing :+1:


add Scrollbars to CommentFooter

Fixes #1036
In my last PR it seem that breaking comment actions in two line take alot of space , so in this one i suggest this changement by adding antd scrollbars to comment actions .
As the issue is in the mobile view , we can use this feature temporarily untill we have a better solution .

Changes on ; busy/src/client/components/CommentFooter/CommentFooter.js

Adding scrollbars module & implent it.

Changes on ; busy/src/client/components/CommentFooter/CommentFooter.lss

force full width to commentFooter

Closing this PR we will fix that issue in another way.


settings: logging: Add log_strdup to error messages

In case of corrupted key in settings, error message is shown. However,
the key name is lost by logger if it is not explicitly copied.
Signed-off-by: Filip Kubicz<EMAIL_ADDRESS>

@nvlsianpu I missed it during review, but now in logs I see following:
<err> settings: set-value failure. key: �� error(-22)

PR fixes this.

Codecov Report

Merging #14700 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #14700   +/-   ##
=======================================
  Coverage   51.97%   51.97%
=======================================
  Files         309      309
  Lines       45582    45582
  Branches    10555    10555
=======================================
  Hits        23691    23691
  Misses      17082    17082
  Partials     4809     4809

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 d1f4206...054babf. Read the comment docs.


Hugo 15 support Markdown per GitHub; Removing seds

All the links reverted to GitHub Style.
Signed-off-by: Mary Anthony<EMAIL_ADDRESS>

LGTM

LGTM

Cool. Ty


Machine Learning Algorithms

Please see the guide if the algorithm you wish to explain is already present. Include in guides/data_science/machine_learning


Handle nested classes in queries

It looks like Juggle has problems with nested classes.
$ juggle -i java.net 'PasswordAuthentication (Authenticator,String,InetAddress,int,String,String,String,URL,Authenticator.RequestorType)'
*** Couldn't find type: Authenticator.RequestorType; using class java.lang.Object instead
$

Specifying the full type with package also didn't help.

Is the problem that Class.forName(String) requires the "binary name" of the class, i.e. Authenticator$RequestorType? Could the solution be as simple as s/\./$/g on the class name before looking it up?


Broken Edge - Compatibility

The following game can be added to the compatibility list:
Game: Broken Edge
Distribution: Steam
OpenXR Runtime in VD: VDXR
Runtime in overlay: VDXR

The game natively supports openXR so no additional commands were used. Hand positioning and buttons worked good 👍

Thank you for the reports!


Process List: Sorting, Columns, One-Click Link

[ ] Default Sortig mode: ???
[ ] Sorting on all Columns should be possible, execept from "Description"

[ ] Sorting: should Folder always be on top or not?
[ ] E2E-Tests

[x] Columns adding and deselecting Bug: should work again

[ ] E2E-Tests

[ ] Process-List: 'Name' column should not be de-selectable
[x] Selecting of processes only on the checkbox column => had to remove shift-selection, as some browsers dont emit events, when shift+clicking inputs of type checkbox, as soon as one checkbox is checked => #278

[ ] E2E-Tests => remove?

[ ] Drag and Drop of processes into folders: not on the whole anymore

[ ] if a process is selected, then show an icon in the action bar (on top of the table) for moving the process into a folder
[ ] Drag and Drop Symbol (Six-Point-Symbol) an the right row side of a Process and Folder: https://react-icons.github.io/react-icons/search/#q=drag
[ ] E2E-Tests

[x] Column Size should be adaptable (width) => #278
[x] Make the column blocks clickable with left click (also good for opening a process in a browser tab): ~all but Select Column and Star Column~  => Name and Description are clickable links, as soon as drag is changed, text selectable => #278

[ ] Text should be selectable (now it is not)
[ ] E2E-Tests

[ ] Right Click Context Menu: Open, Open in New Tab, Copy Process Link, Make a Copy
[ ] Button for Creating a new Folder

[ ] E2E-Tests

[x] store every User setting of the process list in the localstorage
[ ] make the process list component abstract and reusable for usage in other views

@iaktern I think adding a drag and drop symbol would make the process list too cluttered, what do you think?

@iaktern I think  the selection of Elements in the list via the checkbox should not be tested, as it is part of the antdesign table.

@iaktern I think the selection of Elements in the list via the checkbox should not be tested, as it is part of the antdesign table.

yes, you're right: we should only test logic coming from our code. But in your case, isn't the selection logic coming from us? e.g., if someone clicks an icon within the row.

@iaktern I think the selection of Elements in the list via the checkbox should not be tested, as it is part of the antdesign table.

yes, you're right: we should only test logic coming from our code. But in your case, isn't the selection logic coming from us? e.g., if someone clicks an icon within the row.

While the selection logic can be set from outside, I still think, it should not be tested as part of the selection of elements within the list.
The selection of an element in the list is given through AntDesign, we just pass it some callback for further functionality - which, currently, is just saving the selection in a state, as well as saving the last clicked element..
I think further added functionality should definitely be tested, however, this should come from the user's perspective, i.e. not checking state changes but rather gui changes associated with it. These test should then test the further functionality that follows / results from the selection. However, they should not test the selection itself, as it is given.
Functionality inside some nested elements such as buttons / icons can and should be tested - I agree - but they are not part of the selection either, but rather doing something else, such as copying or exporting.
As of for the way it is implemented currently, the only way to select an element, is via the 'Select all' shortcut, which has some tests on this branch (WIP), via the checkbox click (handled by AntDesign), or if starting some custom logic that then sets the selection from outside (e.g. exporting a process). The latter - I think - should then be tested in tests for the respective functionality rather than a way of selection; otherwise the tests are overlapping.

@MaxiLein We don't need to test implementation details of AntDesign, but we need to test that we use them correctly (e..g the correct props).
For example, we don't need to test the DatePicker component, that it displays the days of a month in the correct order - that is up to AntDesign. But we need to test that it is configured correctly (for example a max range of dates, show only months, also show day time, etc.). If, for example, we accidentally delete a prop or the name or type of a prop changes in AntDesign and we don't update it, it would be an error on our side that the E2E tests should catch.
For this selection case, AntDesign handles the drawing of the checkboxes, but only if we set the props correctly and store the selection. If we ever have a bug, that overrides the selection state, that needs to be caught by E2E tests. We don't need to test the checkboxes themselves, but we need to test that the selection as a whole works.
But as you said, since we should test user stories in Playwright, it should be enough to test the derived functionality of the modals etc. working with the selected processes, so that should be enough. Because that inherently also covers the selection of processes - it's just important that they are included in the tests somehow.

Value in the "Created on" column should include the time (not just the date)
@iaktern  I don't know if this is such a good idea, with dates that are really old, people don't usually care about the exact time, maybe the full date could be in a tooltip?

Your right with old dates. But if they are new, the exact time is often quite interesting.
The important point is, it must be consistent with "Last Edited".
Lets make is similar to MS Teams (implement logic in frontend):

if Date is smaller than 1 day, show the time, e.g. 13:37
if Date is smaller than 7 days, show the number of dates, e.g. "5 days ago"
if Date is more than 7 days away, show the date without time, e.g. "13.12.2024"

The hovering tooltip should always contain the full date and time.


raylib 3.0 roadmap

Actually raylib 3.0 is just an extension to raylib 2.6 but with some big expected changes to the ABI that require lots of redesigns. Check #911 for reference.
Three big changes for this new release:

[x] Move all global variables to a global context defined by nested structs. For the moment, context will be defined by module to be self-contained and portable.
[ ] Complete review and rewrite of logging system. #1065
[ ] Support custom memory allocators for raylib and all dependencies. #1074

Also considering:

[ ] rnet module review and addition. #753

I'll update this issue with further info as required.

If big changes are coming to the ABI, this would be the perfect opportunity to switch from pass by value to pass by reference. Syntax wouldn't change much, and it's more efficient to pass pointers around instead of filling the stack up with big structures.

I agree with @brankoku especially for models, meshes etc...

@brankoku sorry, no plans for that. I already did a big refactor to reduce all structures size, usually under 64 bytes and unify all structures to be used as pass-by-value (Music was a pointer reference before), I think it's easier for students and overload shouldn't be dramatic.

Implemented global context state in commit https://github.com/raysan5/raylib/commit/40b73a8a91afb26becfcb39560dae73447ce15af.

release publish checklist: #1084

Just a thought, is it worth making the "context" structures non-static so more advanced users can make use of them ?

any plan for iOS support?

@pixelblender no plans for the moment but you can check rayfork, it supports iOS.

raylib 3.0 is complete.


id migration: testworld

fixed testworld tests for identity branch

@manuelpolzhofer I think you didn't get what I meant by my comment. Lets discuss tomorrow.


Data Science with python: Support vector machines

Description
Providing brief description to explain the topic with help of code snippets and example.
Domain
Datascience with Python
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

It's already done I guess. @shreyarai05

It's already done I guess and also inform when issue is created from your end. @shreyarai05

mam how would i inform you?

Thanks for informing in thread. Issue assigned to @shreyarai05 for documentation

No, it's an algorithm. It needs .ipynb file with sample code and implementation along with README.md file with good elaboration. @shreyarai05

Sorry to say, but this issue is already done. It can't be worked on. If you would like to work on this issue, there is already an open issue with same title, you can check over there if audio / video contribution available. @shreyarai05


native fetcher test flake in Reverse proxy a pagespeed URL.

When I run tests with the native fetcher I'll sometimes get a test flake in http://mpd.example.com/gstatic_images/*1.gif.pagespeed*expecting one year cache.  This is actually because a recursive download in the previous test failed, getting a 404 for the gif, which means when we look in the filesystem to figure out the url (which we do because we want the correct hash to send) the file isn't found and the *s stay literal.
To reproduce:
while true; do
  touch ngx_pagespeed/test/tmp/file-cache/cache.flush
  curl -s -D- -o/dev/null \
      localhost:8050/gstatic_images/1.gif.pagespeed.ce.JiBnMqyl6S.gif | grep ^HTTP
  sleep 0.1
done

observe that after a while you start getting 404s:
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 404 Not Found
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK

@jeffkaufman I haven't seen this in a while, have you?

I haven't seen it either, but only because this flake was annoying enough that we stopped running the native fetcher tests on every change.  I don't know if it's still a problem.

I suspect that running dnsmasq and configuring the resolver that the native fetcher uses to point to that would fix this.


DisableIdleTimeout is not work as expected

The session still freezing when you run pgweb with --disable-idle-timeout. Maybe I do not correctly understand the meaning of that flag?

No activity - closing.


add support for website collections to the WYSIWYG editor

Once we can edit and save website collections we want to be able to insert these lists into page content.
We'll do this by supporting inserting a collection into Markdown via a hugo shortcode.
Acceptance Criteria:

[ ] add custom 'Website Collection' node type, including Markdown shortcode ({{ websiteCollection $UUID }} ?)
[ ] add a rich preview to the WYSIWYG editor to show the editor what the rendered content will look like (roughly)
[ ] add support for rendering these shortcodes to relevant hugo themes (possibly using a public collections API on Studio to fetch data for them)

if anyone else takes this on, the documentation I wrote here will hopefully be helpful!
https://github.com/mitodl/ocw-studio/blob/master/docs/ckeditor/plugin.md


fix(cloud_functions): ci failures

Description
Fix for CI failures highlighted in #2499.

Added missing gradle.properties AndroidX properties to cloud_functions example repository
Updated environment SDK version range to fix Packages with an SDK constraint on a pre-release of the Dart SDK should themselves be published as a pre-release version. If this package needs Dart version 2.0.0-dev.28.0, consider publishing the package as a pre-release instead. CI publishable issue.

Before

After

Related Issues

#2499  - "CI is red"

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Just saw this PR. We should probably increase the dark sdk lower bound instead of decreasing it. Any particular language feature we need in the plugin in 2.0.0?

Just saw this PR. We should probably increase the dark sdk lower bound instead of decreasing it. Any particular language feature we need in the plugin in 2.0.0?

Isn't changing 2.0.0-dev.28.0 to 2.0.0 increasing the lower bound SDK version already?

2.0.0-dev.28.0 (OLDER) was released 17th Feb 2018 - https://github.com/dart-lang/sdk/releases/tag/2.0.0-dev.28.0
2.0.0 (NEWER) was released 6th Aug 2018 - https://github.com/dart-lang/sdk/releases/tag/2.0.0

The change was just remove its from referencing pre-release versions of the Dart SDK - changing to 2.0.0 was the initial safest bet I thought with the least upgrade friction.


WARNING: unable to extract duration

while downloading from streamcloud.eu

Read the bug reporting instructions and post the required information.

sorry, was fixed in last version

Glad to see that your problem is solved. Feel free to open new issues if you've encountered other problems.


Parsing simple constraints

Addressing #2.

Thanks @tohrnii looks like a great start! I'll review in more depth soon. In the meantime, can you add some comments & a brief README?

One more thing - it woule

Thank you @grjte for the review. Made suggested changes.


(MODULES-8232) fixes for snmp notification receiver to support unsetting

The existing code allowed you to unset a value through -1/unset and was missed during the conversion.
Changes still need to happen to netdev_stdlib to support this.
The deletion of the existing snmp receiver was missed during conversion and meant that multiple receivers with same host/name would be created causing problems.

Closing as it is not ready.


[PE-D] Information window still shows the information of the contact after running the clear command

How to reproduce:

Run the CMM.jar program
Enter the 'clear' command
The information window still contains the information of the previously shown contact (see screenshot 3.1)

Screenshot 3.1:

Labels: type.FunctionalityBug severity.Low
original: WangGLJoseph/ped#3

FIX THIS @loose-bus-change


How to use R to visualize the result?

I've install the R environment, but how can I visualize the result file, it there any tutorials yet?

From here:
https://github.com/PaulTaykalo/xcode-time-tracker/tree/master/visualization/r
Rscript Timecheck.R

I had to install the R packages readr, ``anytime, and ggplot2` before I could run the script.


Get CI green

Coverage increased (+0.01%) to 98.221% when pulling e495fed71f8ee302e2973b2ce3a9a274ac190d4c on bugfix/ci into 2cf78dc3b416fa4eebd759427143ccb3181c7f33 on develop.

Coverage increased (+0.01%) to 98.221% when pulling 704d9ab73404d31ced3aee7947dfbdbe9a3686c5 on bugfix/ci into 2cf78dc3b416fa4eebd759427143ccb3181c7f33 on develop.

Coverage increased (+0.01%) to 98.221% when pulling 704d9ab73404d31ced3aee7947dfbdbe9a3686c5 on bugfix/ci into 2cf78dc3b416fa4eebd759427143ccb3181c7f33 on develop.


Roll engine into flutter to pick up revert in engine/third_party/dart which broke flutter tests

The revert in dart-lang/sdk@d38c08d fixes broken flutter tests.

Guess this needs to wait a little bit until the engine buildbot archived the build under that revision.

The macos artifacts.zip is still not available (guess the buildbot is still running) :-/
But feel free to review it.

LGTM!

Thanks for the review!
(Now I know one has to wait for the client.flutter buildbot to finish, since it needs to archive the engine tarballs first before the flutter travis bots can use it.)


docs: write reminders for the steps involved in wiki page updates

i broke tom so ci might fail - unmounted the /nix/store smh

tom is back welcome back tom 🧿 ✨


Add German translations

Overview:
(mostly) completed:

[x] Lesson 1
[x] Lesson 2
[x] Lesson 3
[x] Lesson 4
[x] Lesson 5
[x] Lesson 6
[x] Lesson 7
[x] Lesson 8
[x] Lesson 9
[x] Lesson 10
[x] Lesson 11
[x] Lesson 12
[x] Lesson 13
[x] Lesson 14
[x] Lesson 15
[x] Lesson 16
[x] Lesson 17
[x] Lesson 18
[x] Lesson 19
[x] Lesson 20
[x] * application (= Lesson 28)
[x] * classref (= Lesson 28)
[x] * error_database (= Lesson 28)

machine translated only:

[ ] Lesson 21
[ ] Lesson 22
[ ] Lesson 23
[ ] Lesson 24
[ ] Lesson 25
[ ] Lesson 26
[ ] Lesson 27
[ ] Lesson 28
[ ] * glossary_database

not done/started:
** Needs updates for new lessons when they arrive, see comment in parenthesis for current status

Lesson 1-20 completely translated now

Added Lesson 21 - 28 machine translation
Added glossary_database machine translating
Updated and translated classref_database

@SpeCter may I merge this PR so that the translated lessons appear in Weblate? Contributors can now collaborate on translations on the same platform Godot uses.

Sure, go ahead

@SpeCter may I merge this PR so that the translated lessons appear in Weblate? Contributors can now collaborate on translations on the same platform Godot uses.

If the German translation was synched with Weblate, is the warning there (copied into here below) counterproductive and causes translators to refrain from continuously translating?

The German translation in particular is almost complete, so if you contribute to German on Weblate, your work will be lost.


Re-enable leak checking in address sanitizer builds

Currently the leak sanitizer (part of address sanitizer) is reporting a number of leaks. They look spurious to me and probably because libc++ needs to be instrumented as well. So the next actions here are to:

[ ] Instrument libc++
[ ] Build node against instrumented libc++
[ ] Re-enable the leak checking that was disabled in https://github.com/mapnik/node-mapnik/commit/cd5f6b419ca447840b67cf26c10e050de260b91b
[ ] Evaluate if any of the remaining leaks are serious and need fixing

For reference, here are the errors coming from the leak sanitizer (from a branch that I re-enabled it on): https://travis-ci.org/mapnik/node-mapnik/jobs/219065861


Creating a line from distance and bearing - angle warning - ArcMap

When adding the angle, if the angle exceeds 360 degrees, it still renders a line. In it's defense, 2700 degrees really is 180 degrees, but I think it should at least show a warning.

This is something that should be added to the validation based on the selection of mils or degrees. Good Catch

I have a fix for this locally, will make a pull request when possible.

PR: https://github.com/Esri/distance-direction-addin-dotnet/pull/305

Assigning to @joebayles  who originally submitted the issue and the MT PEs to verify.

This is still an issue.
We should have the same interaction that happens in the Visibility Add in when an angle is put in that is higher than 360

This should be done when using degrees for one and for mils it would be 6400 mil. From my research that is that amount of mils in a circle. If I am wrong the tool should turn red when the number exceeds the equivalent of 360 degrees

Saw that this covered ArcMap and I found the following error with the verification:

ArcGIS Pro does not conduct any validation. I think this issue should cover ArcMap and ArcGIS Pro.
@pHill5136 FYI; thought you would care based on the pull request that you merged.

Assigning Devs - @csmoore and @kgonzago and adding backlog label

I wasn't exactly able to reproduce this issue, but I did notice some badness when distance=0 (as show in the screenshot), so added a check for that - can you retest in the next daily?  Reassigning for re-test.
I also noticed several other issues with the feedback graphic while testing this recorded in new issue #364

@csmoore I don't know, is this the output you were expecting?

verified.  values between 340-360 work.  values greater than 360 do not.

This issue still isnt fixed.  The graphic still draws past 360.  It actually draws the last valid angle that was dynamically drawn.

I have a change for this that resets the the feedback angle to zero (its initial state) - hopefully this will work to clear up the confusion above:

This is ready for re-retest in the next build (with/note the behavior mentioned in the last comment)

i got this one.

Verified.  Any angle over 360 throws an invalid input

This looks like it is fixed. If you start entering a value, say .... 4 then 0 it will draw a preview at 40 degrees. if you continue on to enter 5 (thus trying to create an angle of 405) you get the red X warning and it won't draw when you press enter. Closing this issue, however i am opening a new one, as it seems like mils is not working correctly, from my understanding 405 would be a valid angle when working with mils, but when i switch to mils, i still can not enter a value over 360.


cardinality bug?

https://dl.dropboxusercontent.com/u/209/zxcvbn/test/index.html
temppass22 cardinality is 69
should not it be 36 (lower case + digits = 26+10)?

This bug was fixed long ago and I forgot to close this issue, apologies and thanks for reporting.


Inconsistent plan for kafka connector

I tested presto kafka connector and find a problem:
I can see the kafka topics in presto, but sometimes query on the table returns nothing, for example
Here are the results of the same query:
presto:s1> select count(*) from t2;
_col0
5503
(1 row)
presto:s1> select count(*) from t2;
_col0
 0

(1 row)
I was quite confused about this, and I tried to explain this query
Why they have two different plan? Where is the Filter[false] come from?
presto:s1> explain select count(*) from t2;
Query Plan

Output[_col0] => [count:bigint]
_col0 := count

Aggregate(FINAL) => [count:bigint]
count := "count"("count_3")

Exchange[GATHER] => count_3:bigint

Aggregate(PARTIAL) => [count_3:bigint]
count_3 := "count"(*)

TableScan[kafka:KafkaTableHandle{connectorId=kafka, schemaName=s1, tableName=t2, topicName=s1.t2, keyDataFormat=dummy, messageDataFormat=dummy}, original constraint=true] => []

(1 row)
presto:s1> explain select count(*) from t2;
Query Plan

Output[_col0] => [count:bigint]
_col0 := count

Aggregate(FINAL) => [count:bigint]
count := "count"("count_3")

Exchange[GATHER] => count_3:bigint

Aggregate(PARTIAL) => [count_3:bigint]
count_3 := "count"(*)

Filter[false] => []

TableScan[kafka:KafkaTableHandle{connectorId=kafka, schemaName=s1, tableName=t2, topicName=s1.t2, keyDataFormat=dummy, messageDataFormat=dummy}, original constraint=true] => []

I have encountered the same problem,anyone could explain why?

My guess is the Kafka broker is reporting that there are no partitions, so the Kafka connector is telling presto there is no data.  When Presto see there is no data it adds a "false" filter, and when the plan is optimized the whole thing folds to a no data node.  The code that is looking for the partitions is here:
https://github.com/facebook/presto/blob/master/presto-kafka/src/main/java/com/facebook/presto/kafka/KafkaSplitManager.java#L90

Oh, it appears that the topic has some weird problem, not a problem anymore.


Implement warp in cairo-protostar

It should have signature
extern fn warp(blk_timestamp: felt, target_contract_address: Option<felt>) -> Result<(),felt> nopanic

@Radinyn is this one finished?


Boundry annotation wrongly created: The description only described an if-case for the boundry, not a requirement.

URL Hash
#/sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__/min_df
Actual Annotation Type
@boundary
Actual Annotation Inputs
{
    "target": "sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__/min_df",
    "authors": [
        "$autogen$"
    ],
    "interval": {
        "isDiscrete": false,
        "lowerIntervalLimit": 0,
        "lowerLimitType": 0,
        "upperIntervalLimit": 1,
        "upperLimitType": 0
    }
}

Expected Annotation Type
No annotation
Expected Annotation Inputs

Minimal API Data (optional)

Minimal API Data for `sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__/min_df`
{
    "schemaVersion": 1,
    "distribution": "scikit-learn",
    "package": "sklearn",
    "version": "1.1.1",
    "modules": [
        {
            "id": "sklearn/sklearn.feature_extraction.text",
            "name": "sklearn.feature_extraction.text",
            "imports": [
                {
                    "module": "array",
                    "alias": null
                },
                {
                    "module": "numbers",
                    "alias": null
                },
                {
                    "module": "numpy",
                    "alias": "np"
                },
                {
                    "module": "re",
                    "alias": null
                },
                {
                    "module": "scipy.sparse",
                    "alias": "sp"
                },
                {
                    "module": "unicodedata",
                    "alias": null
                },
                {
                    "module": "warnings",
                    "alias": null
                }
            ],
            "from_imports": [
                {
                    "module": "collections",
                    "declaration": "defaultdict",
                    "alias": null
                },
                {
                    "module": "collections.abc",
                    "declaration": "Mapping",
                    "alias": null
                },
                {
                    "module": "functools",
                    "declaration": "partial",
                    "alias": null
                },
                {
                    "module": "operator",
                    "declaration": "itemgetter",
                    "alias": null
                },
                {
                    "module": "sklearn.base",
                    "declaration": "_OneToOneFeatureMixin",
                    "alias": null
                },
                {
                    "module": "sklearn.base",
                    "declaration": "BaseEstimator",
                    "alias": null
                },
                {
                    "module": "sklearn.base",
                    "declaration": "TransformerMixin",
                    "alias": null
                },
                {
                    "module": "sklearn.exceptions",
                    "declaration": "NotFittedError",
                    "alias": null
                },
                {
                    "module": "sklearn.feature_extraction._hash",
                    "declaration": "FeatureHasher",
                    "alias": null
                },
                {
                    "module": "sklearn.feature_extraction._stop_words",
                    "declaration": "ENGLISH_STOP_WORDS",
                    "alias": null
                },
                {
                    "module": "sklearn.preprocessing",
                    "declaration": "normalize",
                    "alias": null
                },
                {
                    "module": "sklearn.utils",
                    "declaration": "_IS_32BIT",
                    "alias": null
                },
                {
                    "module": "sklearn.utils.deprecation",
                    "declaration": "deprecated",
                    "alias": null
                },
                {
                    "module": "sklearn.utils.validation",
                    "declaration": "check_array",
                    "alias": null
                },
                {
                    "module": "sklearn.utils.validation",
                    "declaration": "check_is_fitted",
                    "alias": null
                },
                {
                    "module": "sklearn.utils.validation",
                    "declaration": "check_scalar",
                    "alias": null
                },
                {
                    "module": "sklearn.utils.validation",
                    "declaration": "FLOAT_DTYPES",
                    "alias": null
                }
            ],
            "classes": [
                "sklearn/sklearn.feature_extraction.text/TfidfVectorizer"
            ],
            "functions": []
        }
    ],
    "classes": [
        {
            "id": "sklearn/sklearn.feature_extraction.text/TfidfVectorizer",
            "name": "TfidfVectorizer",
            "qname": "sklearn.feature_extraction.text.TfidfVectorizer",
            "decorators": [],
            "superclasses": [
                "CountVectorizer"
            ],
            "methods": [
                "sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__"
            ],
            "is_public": true,
            "reexported_by": [],
            "description": "Convert a collection of raw documents to a matrix of TF-IDF features.\n\nEquivalent to :class:`CountVectorizer` followed by\n:class:`TfidfTransformer`.\n\nRead more in the :ref:`User Guide <text_feature_extraction>`.",
            "docstring": "Convert a collection of raw documents to a matrix of TF-IDF features.\n\nEquivalent to :class:`CountVectorizer` followed by\n:class:`TfidfTransformer`.\n\nRead more in the :ref:`User Guide <text_feature_extraction>`.\n\nParameters\n----------\ninput : {'filename', 'file', 'content'}, default='content'\n    - If `'filename'`, the sequence passed as an argument to fit is\n      expected to be a list of filenames that need reading to fetch\n      the raw content to analyze.\n\n    - If `'file'`, the sequence items must have a 'read' method (file-like\n      object) that is called to fetch the bytes in memory.\n\n    - If `'content'`, the input is expected to be a sequence of items that\n      can be of type string or byte.\n\nencoding : str, default='utf-8'\n    If bytes or files are given to analyze, this encoding is used to\n    decode.\n\ndecode_error : {'strict', 'ignore', 'replace'}, default='strict'\n    Instruction on what to do if a byte sequence is given to analyze that\n    contains characters not of the given `encoding`. By default, it is\n    'strict', meaning that a UnicodeDecodeError will be raised. Other\n    values are 'ignore' and 'replace'.\n\nstrip_accents : {'ascii', 'unicode'}, default=None\n    Remove accents and perform other character normalization\n    during the preprocessing step.\n    'ascii' is a fast method that only works on characters that have\n    an direct ASCII mapping.\n    'unicode' is a slightly slower method that works on any characters.\n    None (default) does nothing.\n\n    Both 'ascii' and 'unicode' use NFKD normalization from\n    :func:`unicodedata.normalize`.\n\nlowercase : bool, default=True\n    Convert all characters to lowercase before tokenizing.\n\npreprocessor : callable, default=None\n    Override the preprocessing (string transformation) stage while\n    preserving the tokenizing and n-grams generation steps.\n    Only applies if ``analyzer`` is not callable.\n\ntokenizer : callable, default=None\n    Override the string tokenization step while preserving the\n    preprocessing and n-grams generation steps.\n    Only applies if ``analyzer == 'word'``.\n\nanalyzer : {'word', 'char', 'char_wb'} or callable, default='word'\n    Whether the feature should be made of word or character n-grams.\n    Option 'char_wb' creates character n-grams only from text inside\n    word boundaries; n-grams at the edges of words are padded with space.\n\n    If a callable is passed it is used to extract the sequence of features\n    out of the raw, unprocessed input.\n\n    .. versionchanged:: 0.21\n        Since v0.21, if ``input`` is ``'filename'`` or ``'file'``, the data\n        is first read from the file and then passed to the given callable\n        analyzer.\n\nstop_words : {'english'}, list, default=None\n    If a string, it is passed to _check_stop_list and the appropriate stop\n    list is returned. 'english' is currently the only supported string\n    value.\n    There are several known issues with 'english' and you should\n    consider an alternative (see :ref:`stop_words`).\n\n    If a list, that list is assumed to contain stop words, all of which\n    will be removed from the resulting tokens.\n    Only applies if ``analyzer == 'word'``.\n\n    If None, no stop words will be used. max_df can be set to a value\n    in the range [0.7, 1.0) to automatically detect and filter stop\n    words based on intra corpus document frequency of terms.\n\ntoken_pattern : str, default=r\"(?u)\\\\b\\\\w\\\\w+\\\\b\"\n    Regular expression denoting what constitutes a \"token\", only used\n    if ``analyzer == 'word'``. The default regexp selects tokens of 2\n    or more alphanumeric characters (punctuation is completely ignored\n    and always treated as a token separator).\n\n    If there is a capturing group in token_pattern then the\n    captured group content, not the entire match, becomes the token.\n    At most one capturing group is permitted.\n\nngram_range : tuple (min_n, max_n), default=(1, 1)\n    The lower and upper boundary of the range of n-values for different\n    n-grams to be extracted. All values of n such that min_n <= n <= max_n\n    will be used. For example an ``ngram_range`` of ``(1, 1)`` means only\n    unigrams, ``(1, 2)`` means unigrams and bigrams, and ``(2, 2)`` means\n    only bigrams.\n    Only applies if ``analyzer`` is not callable.\n\nmax_df : float or int, default=1.0\n    When building the vocabulary ignore terms that have a document\n    frequency strictly higher than the given threshold (corpus-specific\n    stop words).\n    If float in range [0.0, 1.0], the parameter represents a proportion of\n    documents, integer absolute counts.\n    This parameter is ignored if vocabulary is not None.\n\nmin_df : float or int, default=1\n    When building the vocabulary ignore terms that have a document\n    frequency strictly lower than the given threshold. This value is also\n    called cut-off in the literature.\n    If float in range of [0.0, 1.0], the parameter represents a proportion\n    of documents, integer absolute counts.\n    This parameter is ignored if vocabulary is not None.\n\nmax_features : int, default=None\n    If not None, build a vocabulary that only consider the top\n    max_features ordered by term frequency across the corpus.\n\n    This parameter is ignored if vocabulary is not None.\n\nvocabulary : Mapping or iterable, default=None\n    Either a Mapping (e.g., a dict) where keys are terms and values are\n    indices in the feature matrix, or an iterable over terms. If not\n    given, a vocabulary is determined from the input documents.\n\nbinary : bool, default=False\n    If True, all non-zero term counts are set to 1. This does not mean\n    outputs will have only 0/1 values, only that the tf term in tf-idf\n    is binary. (Set idf and normalization to False to get 0/1 outputs).\n\ndtype : dtype, default=float64\n    Type of the matrix returned by fit_transform() or transform().\n\nnorm : {'l1', 'l2'}, default='l2'\n    Each output row will have unit norm, either:\n\n    - 'l2': Sum of squares of vector elements is 1. The cosine\n      similarity between two vectors is their dot product when l2 norm has\n      been applied.\n    - 'l1': Sum of absolute values of vector elements is 1.\n      See :func:`preprocessing.normalize`.\n\nuse_idf : bool, default=True\n    Enable inverse-document-frequency reweighting. If False, idf(t) = 1.\n\nsmooth_idf : bool, default=True\n    Smooth idf weights by adding one to document frequencies, as if an\n    extra document was seen containing every term in the collection\n    exactly once. Prevents zero divisions.\n\nsublinear_tf : bool, default=False\n    Apply sublinear tf scaling, i.e. replace tf with 1 + log(tf).\n\nAttributes\n----------\nvocabulary_ : dict\n    A mapping of terms to feature indices.\n\nfixed_vocabulary_ : bool\n    True if a fixed vocabulary of term to indices mapping\n    is provided by the user.\n\nidf_ : array of shape (n_features,)\n    The inverse document frequency (IDF) vector; only defined\n    if ``use_idf`` is True.\n\nstop_words_ : set\n    Terms that were ignored because they either:\n\n      - occurred in too many documents (`max_df`)\n      - occurred in too few documents (`min_df`)\n      - were cut off by feature selection (`max_features`).\n\n    This is only available if no vocabulary was given.\n\nSee Also\n--------\nCountVectorizer : Transforms text into a sparse matrix of n-gram counts.\n\nTfidfTransformer : Performs the TF-IDF transformation from a provided\n    matrix of counts.\n\nNotes\n-----\nThe ``stop_words_`` attribute can get large and increase the model size\nwhen pickling. This attribute is provided only for introspection and can\nbe safely removed using delattr or set to None before pickling.\n\nExamples\n--------\n>>> from sklearn.feature_extraction.text import TfidfVectorizer\n>>> corpus = [\n...     'This is the first document.',\n...     'This document is the second document.',\n...     'And this is the third one.',\n...     'Is this the first document?',\n... ]\n>>> vectorizer = TfidfVectorizer()\n>>> X = vectorizer.fit_transform(corpus)\n>>> vectorizer.get_feature_names_out()\narray(['and', 'document', 'first', 'is', 'one', 'second', 'the', 'third',\n       'this'], ...)\n>>> print(X.shape)\n(4, 9)"
        }
    ],
    "functions": [
        {
            "id": "sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__",
            "name": "__init__",
            "qname": "sklearn.feature_extraction.text.TfidfVectorizer.__init__",
            "decorators": [],
            "parameters": [
                {
                    "id": "sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__/min_df",
                    "name": "min_df",
                    "qname": "sklearn.feature_extraction.text.TfidfVectorizer.__init__.min_df",
                    "default_value": "1",
                    "assigned_by": "NAME_ONLY",
                    "is_public": true,
                    "docstring": {
                        "type": "float or int",
                        "description": "When building the vocabulary ignore terms that have a document\nfrequency strictly lower than the given threshold. This value is also\ncalled cut-off in the literature.\nIf float in range of [0.0, 1.0], the parameter represents a proportion\nof documents, integer absolute counts.\nThis parameter is ignored if vocabulary is not None."
                    },
                    "type": {}
                }
            ],
            "results": [],
            "is_public": true,
            "reexported_by": [],
            "description": "Convert a collection of raw documents to a matrix of TF-IDF features.\n\nEquivalent to :class:`CountVectorizer` followed by\n:class:`TfidfTransformer`.\n\nRead more in the :ref:`User Guide <text_feature_extraction>`.",
            "docstring": ""
        }
    ]
}

Minimal Usage Store (optional)

Minimal Usage Store for `sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__/min_df`
{
    "schemaVersion": 1,
    "module_counts": {
        "sklearn/sklearn.feature_extraction.text": 18626
    },
    "class_counts": {
        "sklearn/sklearn.feature_extraction.text/TfidfVectorizer": 8587
    },
    "function_counts": {
        "sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__": 3212
    },
    "parameter_counts": {
        "sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__/min_df": 1028
    },
    "value_counts": {
        "sklearn/sklearn.feature_extraction.text/TfidfVectorizer/__init__/min_df": {
            "0": 41,
            "1": 2242,
            "2": 172,
            "3": 323,
            "4": 7,
            "5": 214,
            "6": 1,
            "7": 2,
            "9": 1,
            "10": 77,
            "15": 4,
            "20": 9,
            "23": 1,
            "25": 1,
            "30": 3,
            "50": 6,
            "100": 12,
            "150": 9,
            "200": 6,
            "0.0": 13,
            "0.01": 12,
            "9e-05": 10,
            "min_df": 10,
            "0.001": 6,
            "0.2": 4,
            "self.min_df": 3,
            "np.int(min_df * texts.shape[0])": 2,
            "0.005": 2,
            "0.1": 2,
            "0.05": 2,
            "MIN_DOCUMENT_FREQUENCY": 2,
            "1e-07": 1,
            "0.009": 1,
            "noOfocurance": 1,
            "0.15": 1,
            "model_question.vocabulary.min_count": 1,
            "0.0005": 1,
            "0.0001": 1,
            "MIN_DF_TF": 1,
            "NAME_MIN_DF": 1,
            "0.0025": 1,
            "min_df_opt": 1,
            "self.tfidf_min_df": 1,
            "mindf": 1
        }
    }
}

Suggested Solution (optional)
No response
Additional Context (optional)

The descriptions only says "If float... " which isn't a requirement. The boundry annotation is therefore wrongly added.

Similiar problem with #/sklearn/sklearn.manifold._t_sne/TSNE/init/learning_rate

The given range is not a requirement.


FineTuning HiFi with GLowTTS npy

Hello!
I'm trying to FineTuning HiFi with GlowTTS npy
i generate npy with this code:
def TTS(tst_stn, path):
    if getattr(hps.data, "add_blank", False):
        text_norm = text_to_sequence(tst_stn.strip(), ['english_cleaners'], cmu_dict)
        text_norm = commons.intersperse(text_norm, len(symbols))
    else:
        tst_stn = " " + tst_stn.strip() + " "
        text_norm = text_to_sequence(tst_stn.strip(), ['english_cleaners'], cmu_dict)
    sequence = np.array(text_norm)[None, :]
    x_tst = torch.autograd.Variable(torch.from_numpy(sequence)).cuda().long()
    x_tst_lengths = torch.tensor([x_tst.shape[1]]).cuda()

   with torch.no_grad():
        noise_scale = 0.667
        length_scale = 1.0
        (y_gen_tst, *_), *_, (attn_gen, *_) = model(x_tst, x_tst_lengths, gen=True, noise_scale=noise_scale, length_scale=length_scale)

    np.save("hf/ft_dataset/" + path.split('/')[1]  + '.npy', y_gen_tst.cpu().detach().numpy())

Next, I make a metafile:
wavs/x.wav | ft_dataset/x.npy
And I get the following error:
RuntimeError: stack expects each tensor to be equal size, but got [8192] at entry 0 and [6623] at entry 6
Hi-Fi generates wav using these npy in inference mode with GlowTTS

I do not think you need/should fine-tune HiFi-GAN when using Glow-TTS. Glow-TTS doesn't have an oversmoothing problem that fine-tuning could resolve.
Do you have any audio samples before fine-tuning? I'm pretty sure if there is an audio quality issue then it'd stem from Glow-TTS or your speaker being out of the training set that HiFi-GAN was trained on.

I do not think you need/should fine-tune HiFi-GAN when using Glow-TTS. Glow-TTS doesn't have an oversmoothing problem that fine-tuning could resolve.
Do you have any audio samples before fine-tuning? I'm pretty sure if there is an audio quality issue then it'd stem from Glow-TTS or your speaker being out of the training set that HiFi-GAN was trained on.

I used the training data on which I taught GlowTTS and generate npy out of them
i will attach train wav file and npy
wavs.zip

@4nton-P
Hello.
To get mel-spectrograms for fine tuning, you need to make some changes to the code. If you set the 'gen' argument to True, the length of the generated mel-spectrogram may not match the length of the ground truth audio.
In the branch where 'gen' of the forward operation is False, there is a part that generates mean and variance using the output of the encoder and the output of the decoder.
If you use these to sample z from Gaussian and feed it to the decoder with 'reverse=True', you will get the desired result. See lines 313 and 299.
And 'noise_scale' can affect the quality. You will get good results with the default settings, but experimenting with various 'noise_scale' would be a good try.

@jik876
Thanks, I will try to do this.
"noise_scale" has already experimented with tuning
If everything works out, I will close the discussion.

RuntimeError: stack expects each tensor to be equal size, but got [8192] at entry 0 and [3037] at entry 1

@4nton-P
Hello.
To get mel-spectrograms for fine tuning, you need to make some changes to the code. If you set the 'gen' argument to True, the length of the generated mel-spectrogram may not match the length of the ground truth audio.
In the branch where 'gen' of the forward operation is False, there is a part that generates mean and variance using the output of the encoder and the output of the decoder.
If you use these to sample z from Gaussian and feed it to the decoder with 'reverse=True', you will get the desired result. See lines 313 and 299 in models.py.
And 'noise_scale' can affect the quality. You will get good results with the default settings, but experimenting with various 'noise_scale' would be a good try.

Hello!
I took the code from this issue for generate .npy and am also trying to fine-tune HifiGan with GlowTTS. So, I set the parameter 'reverse = True' in models.py, generated .npy and got the same error. What could have gone wrong?

@romadomaa
Please understand that we are a bit busy with other work.
The above explanation is to match the length with the ground truth using MAS.
Posting your modified code will be helpful to find a solution.

@jik876
Thanks, I will try to do this.
"noise_scale" has already experimented with tuning
If everything works out, I will close the discussion.

@4nton-P @jik876
Can you share the code changes to fine tune hifigan w.r.t. GlowTTS predicted Mel?

I am taking mels from fastspeech2 and trying to input it to hifigan to generate audio but I am getting noise in the audio file . I made it shape compatible but there are problems internally . please share your idea that I can try.


[UPDATE] v1.0.0 alpha3

Description
Updates to v1.0.0-alpha3.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update
[x] Update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new errors or linter warnings
[x] My changes generate no problems with other code
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing tests passed locally with my changes

@mergifyio update


chore: Property pane control to generate query for a widget

Description
This PR adds a property pane control through which we can browse the datsource, tables and columns. This will be used later in the one click feature.
Fixes #21504
Type of change

Chore (housekeeping or task changes that don't impact user perception

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=b8dea3b

/ok-to-test sha=351447d

/ok-to-test sha=e0b687b

/ok-to-test sha=e0b687b


Add support for \hspace

Are there any plans to add support for \hspace{2px} ?
I need this to format numbers, meaning I have things like:
12\hspace{2px}345

Closing in favour of https://github.com/Khan/KaTeX/issues/164.


Crash when disposing in 2.1.0-rc1-final

Our unit tests crashed with the following error.
Note that our code has no way to actually capture this error and handle it.
Unhandled Exception: System.AggregateException: One or more errors occurred. (An existing connection was forcibly closed by the remote host) ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
   at System.Net.Sockets.Socket.Shutdown(SocketShutdown how)
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.Internal.SocketConnection.Shutdown()
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.Internal.SocketConnection.Abort()
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1OutputProducer.Abort(Exception error)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.Abort(Exception error)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.HttpConnection.Abort(Exception ex)
   at System.IO.Pipelines.PipeCompletionCallbacks.Execute()
   --- End of inner exception stack trace ---
   at System.IO.Pipelines.PipeCompletionCallbacks.Execute()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Fixed in the rtm https://github.com/aspnet/KestrelHttpServer/issues/2554

Thanks for the report.


Show XML tree view as a new icon on the activity bar

Since the April 2018 update, extensions can now add a new icon to the activity bar. I suggest moving the XML tree view from the Explorer pane to a new pane.
Better even, add an option to choose between having the XML tree view on the Explorer pane or on a separate pane. But to provide such option, we would have to wait for https://github.com/Microsoft/vscode/issues/48704.

I like this idea. I'm going to backlog it for now and circle back around when I have a clearer picture in terms of how to make this optional while allowing reuse of the existing data provider. The parts all seem to be there, it will just take a little thought.
Thanks!


[LOW] [Perfromance] Unnecessary calls of triggerUnreadUpdate method

Coming from Slack.
There were a couple of places where there was a noticeable delay in the response of the UI. I will log this as CRITICAL because it works so randomly that I think this is not only performance issue but UX reliability.
unfortunately, in the video, you cannot see when I press the buttons to see the delay

Click + in the compose - 11second
DELAY 1 Opening the bottom drawer modal
47 second after adding the amount and currency there is a delay populating it in the transaction thread
BUG: 57 second - Added a merchant and the Amount got cleared up :rage:
DELAY 2 - 1:04 When I have opened the amount page again, the page was not responsive for good 4 seconds, you can see the currency opened at 1:10 and then the numbers I pressed before were in the amount.
There is no API call on that page I think, what was the UI hang up on? Even if there is a READ call, it should not cause the UI slowdown
BUG 2 - 1:18 saving the amount cleared the merchant again :rage:
Logs and video in the Slack thread

Issue OwnerCurrent Issue Owner: @OlimpiaZurek

Hi. I'm Olimpia from Callstack.  I would like to work on this issue.

@OlimpiaZurek Any update for this one? What would be your next steps and ETA?
Lets try to make many small improvements iteratively so we do not wait for one bigger PR

Not much progress here. Today I was investigating a reassure performance issue in PR related to Onyx bump.

let us know if you have any updates

Today I started looking into potential improvements to this method

Daily update:  I’ve been investigating how we can improve the triggerUnreadUpdate() method. By adding debouncing and some memoization, we can reduce the number of calls to this function. I’m working on the draft PR.

PR merged 🚀
@OlimpiaZurek Do you expect more changes to reduce the number of calls even further

I'm planning to check if there is more room for improvement here.

It appears that after applying the changes, the function is only called when the navigation state changes, which is the expected behavior.  I didn't detect any unnecessary calls, so I think we can close this issue as resolved

@DylanDylann sent you an offer here: https://www.upwork.com/nx/wm/offer/102918311
Ping me on this issue when you've accepted.

@puneetlath I accepted, thanks 🚀

Paid. Thanks everyone!


Switch project form from tabs to collapsible panels; fixes #630

Lets get rid of tabs and go to collapsible panes. We also now show all fields when javascript is disabled.
This additionally closes #595, #475, and #218.
Signed-off-by: Jason Dossett<EMAIL_ADDRESS>

Codecov Report

Merging #662 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #662   +/-   ##
=======================================
  Coverage   99.65%   99.65%
=======================================
  Files          42       42
  Lines        1150     1150
=======================================
  Hits         1146     1146
  Misses          4        4

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 f57c64c...d841776. Read the comment docs.

On initial look this looks pretty good. However, clearly the panel to open will differ depending on what information has already been provided. This patch always closes the later panels. How about doing a quick check on the 1st question in each panel, and close all the panels by default except the first panel where the first question the is unknown? That way, when people save comma they will by default see the panel that is most likely to be useful.

So I just pushed up a number of changes.

The url is now updated whenever you open a panel.
If you give a panel id in the url (an anchor) the correct panel will open when loading the page.
Submit buttons are now at the bottom of each panel.  They also submit the anchor for the section in which they reside. When you save and continue, The panel where you saved will be opened on reload.
Added an expand/collapse all panels button.

Let me know what you think.

Awesome. Lots of pieces here. Let us NOT squash the merge. Then it'll be easier to revert pieces instead of only the whole thing, if we need to do that

A few comments:

In the panel headings the caret is too close to the heading text.  The CSS should probably be tweaked to add a little margin.
The buttons and headings are easily confused.  The "Submit" and "Save" buttons currently have the same color as the headings - they should be different.  That should be a quick CSS tweak.  While we're at it, the buttons at the top should also have colors, to make them more obvious (maybe the as save & submit, since they're also buttons?)

Here are some specifics.  Perhaps the buttons at top, like "Expand all panels" and "Show detailed text", should be Bootstrap class "btn-info" instead of "btn-default" (or change the color for btn-default).  That would make it more obvious that they exist.
The CSS classes .btn-primary and .panel-title seem have the same colors, which leads to visual confusion.  We should change the CSS colors, or change a class of one of them.

I worry that because "save and continue" doesn't open the next panel, people may not progress.  That's especially true because "save and continue" jumps them up to the top of the panel.  I suggest that "save and continue" open the next panel (with wrap around), so that we keep people moving.  They can always uncollapse the previous panel, if they want to.

My latest change addresses the button styles.  I think we should discuss more whether save and continue jumps to the next pane.  I can see a scenario where people will save when still working on that pane, but indeed it may be better to go to the next pane.

This doesn't quite scroll to the right places in some cases, but we didn't even have that functionality earlier.
There are some minor test failures and formatting issues, which I presume you'll fix soon.  Once you fix them, I plan to merge this (not as a squash merge, but as individual commits so we can cherry-pick rollbacks if needed).  That way, the results will be easily visible on the master tier.  We can then fix from there (I think it'd be better to make that a new branch).
Thanks!

Yes, I am working on the test failures now.  It is a bit more complicated than I though, but I should have it done by tonight.

I reverted the last commit for now.  I am working on an alternative, cleaner approach.

Okay.  I won't merge until you say you're ready.

Finally fixed all the little quirks:
Last push does the following:

Panel's anchor tag opens that panel on load
Child element's anchor tag opens parent panel on load
and scrolls to childs anchor
Save (and continue) opens next panel on reload.
css to resolve anchor issues with fixed header

There is a problem after the merge from master with the new css.  Somehow clickable areas of the panel headings have resized strangely.

Issues fixed, not perfect without js (anchors are slightly off on page load) but with javascript it works perfect.
Ready to pull.

That's fine. Thanks for working this out!


feat: navigation dropdown refactoring

I have one more question about navigation dropdown with highlight

Let's check it with design


ignore files depending on git status, .gitignore and exclude

ignore files depending on git exclusion
ignore files depending on git ignore (non recursive)
depends on
https://github.com/albfan/nerdtree/commit/e9b690723b942db378d3a53b455f37db442b09b0
once filter ignore files is active you can toggle exclude, ignore or status filter.
For me it changes the shell workflow so now I prefer to navigate NERDTree  than Ctrl-Z and git status. A total inflection point

Nice work!
But It's not enough.
~/.config/git/ignore
~/.gitignore
${WORK_DIR}/.gitignore
# ...
../../.gitignore
../.gitignore
.gitignore

All these gitignore files should be checkd.

Yeah, I say it clear on commit. It is not recursive.
I have extract consequently
function NERDTreeGitIgnoreFilterByFile(params, fname)

So recursion is only a commit away.
I dislike too the magical map for toggle custom ignore filters, so I've planned to provide a function to create new mappings.
As last step I will create a byzanz screencast to show it's usage
Let me know any improvements/refactors you detect.
We could integrate this without "toggle custom ignore filter shorcuts" to avoid https://github.com/scrooloose/nerdtree/issues/447 pull request need.

Hey @albfan, I am currently on holiday till Tuesday - am typing this on my phone (it hurts). I will properly review this when I am home, but my first thought is that we should not need a facility to add custom filter mappings. We already have NERDTreeAddMapping().
One route we could take is to change the default 'f' mapping to 'ff' (for 'for filters'). This way any plugin can add filter mappings (via NERDTreeAddMap()) starting with 'f' - as your gitignore code does.
Thoughts?


nodeSelector to run dockerbuilder pod

Deploy an app consumes high CPU, in order to don't affect the deployed apps, I would like to run the dockerbuilder container in an isolate node.
In the following method the builder component creates the dockerbuilder pod:
https://github.com/deis/builder/blob/96292153e5a52f8ea7643349665f8b3d75a5c1c8/pkg/gitreceive/k8s_util.go#L55
I could add 'nodeselector' parameter in the pod creation, but it means that I'll have a custom Deis component...
There is an esasier way to run this pod in an isolate node?

i don't think there is another way than the one you suggested.If you want to make a PR against the builder instead of maintaining you own component, i am happy to help you. You can just add it to the struct https://github.com/deis/builder/blob/master/pkg/gitreceive/config.go#L15 and need to use it if specified while creating the pod.Any one who wan't to use can edit the deis-builder deployment object to add the extra environment variable.

this can used to track as an enhancement request


Envelope Encryption / Vault system tests should use specific Vault Helm Chart version (test repeatability)

Describe the bug
Currently, the system tests use the latest Vault Helm Chart.  That means the tests aren't repeatable over time and we don't have certainty about what has actually been tested.
We need the integration test framework to use a specific version of the chart.
Expected behavior
I think we we should pin to https://github.com/hashicorp/vault-helm/releases/tag/v0.27.0.
That will give use Vault 1.15, which in in synch with the Docker image used by io.kroxylicious.kms.provider.hashicorp.vault.TestVault#HASHICORP_VAULT
We should make sure that the version is overridable by a environment variable, in case we need to override it.

@franvila would you have capacity to do this soon?


PV Shading and Layout input page warning message with backtracking enabled

When backtracking is enabled, Shading and Layout page shows message about number of rows even though that input is not used with backtracking and inputs are disabled:

To get to this state:

On System Design page, choose 1-axis tracking with no backtracking.
On Shading and Layout page, choose standard or non-linear self shading, and choose numbers of modules along side and bottom of row that result in a single row or non-integer number of rows so that a red UI message appears.
On System Design page, enable backtracking.


support download transcript

Description
Please tell us the changes you've made
Issues to fix
Please link issues this PR will fix:
#[issue number]
if no relevant issue, but this will fix something important for reference
, please free to open an issue.
Reminding
Something you can do before PR to reduce time to merge

run "make build" to build the code
run "make format" to reformat the code
run "make lint" if you are using unix system
run "make test-integration" to pass all tests

Do you wanna bring the transcript feature upstream?


fix list_aggregates to work for public FI file records

Fixes #103

The failure is that the session with id self.EID_EPHYS does not seem to exist on the test database. I am not sure what could cause this, these tests passed a few hours ago. It now fails on my local machine too.
The test I added passes (and would fail on the main branch) so once the above has been solved this could be merged


No radio in the car

Hello, that's all working fine with your script only I have a problem, I can't use the radio in a vehicle even to speak or open it, once I get out of the vehicle I can, how can I solve this? Thank You.

Police car?


experiment with hatdocs / txtar

For voice discussion. Lots of important caveats and explaining required.
interesting fixtures:

packages/cursorless-vscode-e2e/src/suite/fixtures/recorded//everyRange/clearEveryFunkNameFinePastBlueDrum.yml
packages/cursorless-vscode-e2e/src/suite/fixtures/recorded/languages/scss/moveFirstWordZipBeforeFineTakeFine.yml
packages/cursorless-vscode-e2e/src/suite/fixtures/recorded/actions/giveEqualsPastColon.yml

type RangeDoc struct {
	Content string
	Ranges  []NamedRangeSet // "hats", "selections", "that", etc.
}

type NamedRangeSet struct {
	Name   string
	Ranges []AnnotatedRange // ranges along with annotations
}

type AnnotatedRange struct {
	Annotation    string
	AnnotationEnd int // how many chars into the range should the annotatin end (e.g. for hats); zero means "don't care", which we will interpret for now as "center"
	Range         Range
	Direction     Direction
}

type Range struct {
	Start Position `yaml:"start,flow"`
	End   Position `yaml:"end,flow"`
}

type Direction int

const (
	DirectionNone Direction = iota
	DirectionStart
	DirectionEnd
)

range
!
#
[]
[-]
[--]

directed range
!
>
<
[>
<]
[->
<-]

--- raw notes ---
- Q: primary cursor: how? range? use a hat ref? can't quite cram that last single bool in there :/
- Q: visible vs invisible contents using > vs <?
- Q: how to sync with scope tests, subtle differences due to different needs
- Q: unicode? tabs?

txtar: way to combine hatdoc + metadata for other purposes
- hat tests: hats, tokens (set of ranges), split editors, multi-stage assignment (either file naming conventinos or config at top)
- test fixtures: extract initial/final docs and some ranges (maybe now can run some of these editor-free?!)
- txtar makes it easier to update just part, do diffs, do multi-step things, do multi-editor things, etc.

# problems

currently losing some thatMark (etc) metadata: reversed, explicit, etc.
ranges need lots more metadata (isReversed, explicit, etc) / annotations :(

# stats test

given doc + other metadata:

number of 0, 1, 2 penalty hats
nubmer of hats on first letter of word
percent of tokens with no hat
distance to nearest token with no hat

https://github.com/cursorless-dev/cursorless/pull/1768/commits/1ac8931cf0c6274873c61f2f97a73a8a1c4ecd86

Fwiw if you mark a PR as draft, as you've done, we won't merge it, and will assume it's WIP, so you don't need the big all-caps caveat in the title 😄. We also have a to discuss tag you can put on it which indicates it should be discussed in a meet-up

Also, I'm guessing you've seen https://github.com/cursorless-dev/cursorless/issues/1524, but figured I'd mention it just in case

I'm guessing you've seen https://github.com/cursorless-dev/cursorless/issues/1524

This was very much inspired by #1524. Unfortunately due to different needs, they diverged in minor ways, and continue to do so. I was designing for hat tests and then got distracted by attempting to re-use for other fixtures. https://github.com/cursorless-dev/cursorless/issues/1767 is an added wrinkle I'm still pondering.

this is actually ready to discuss a bit now. will need voice intro, though, for sure.

outcome from meetup: as anticipated, the advantages of having a single uniform data format are outweighed by the disadvantages of it not being a perfect fit for any particular use case.
plan is that @pokey (and maybe @AndreasArvidsson?) are going to look through a few of the interesting fixtures in case there are any ideas they want to steal, and we will put this on ice. :)


Bump to 2.38.0 and make Linux only

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


DepthFunc per material

This change adds the material property 'depthFunc' that can be set to
any of the following values in order to control what comparison function
is used for the depth test during rendering:
FUNC_NEVER: don't draw
FUNC_LESS: draw if new depth < depth buffer
FUNC_EQUAL: draw if new depth == depth buffer
FUNC_LESSEQUAL: draw if new depth <= depth buffer
FUNC_GREATER: draw if new depth > depth buffer
FUNC_NOTEQUAL: draw if new depth != depth buffer
FUNC_GREATEREQUAL: draw if new depth >= depth buffer
FUNC_ALWAYS: always draw
previously depthFunc was always set to FUNC_LESSEQUAL, which is thus the
new default value for this property.
Fixes #4093
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

Personally, I would name it something more specific, as by reading it out of context e.g. "func less" - does not speak enough for itself.
DEPTHFUNC_LESS - would work better to give an idea of a constant out of context.

DEPTHFUNC_LESS ...

I agree with you, but these constant names are existing constants in the engine. The PR only allows them to be set on material, but does not create any additional constant names.


[Bug]: RedisVectorStore delete_ref_doc doesn't delete all nodes

Bug Description
index.delete_ref_doc(ref_doc_id=doc_id)
Won't delete all of the nodes of a document if there are more than 10.
Because the code in delete does a search for nodes then deletes what it finds node by node.  However the query default is to limit to 10 items returned.  Documents created using SentenceSplitter often have more than 10 nodes.
I believe setting setting the limit explicitly in query_params passed to the search in that code, and putting that code in a loop that repeats until the number of nodes returned < limit would do it, but I don't know a lot about redis so there is probably a better way.
Version
0.9.13
Steps to Reproduce

Index a doc with more than 10 nodes.
Delete the doc using index.delete_ref_doc(doc_id)
Verify nodes are still in the redis data store from that document.

Relevant Logs/Tracbacks
No response

In RedisVectorStore.delete, maybe we should create a redis.commands.search.query.Query object, and modify its attributes (for example, Query._num) using values from the delete_kwargs parameter, and pass this Query object to self._redis_client.ft(self._index_name).search.
In this way, we can directly control the query behavior from the delete_kwargs parameter in index.delete_ref_doc.
However, I'm not sure what number should be set to Query._num.


FY2023Q1 Refresh

Update screen capture in slide deck 1
Update Ex 3 project files
Update link to M365 Developer Program page in project README files

thanks... manually merged


layout schema check

Coverage remained the same at 33.933% when pulling dff3c8731e2d8627ec363abaf8203847c396d32c on suiguoxin:layout-schema into 86c73e32f8f2c8b2b651bd71a2855ff116c27c83 on microsoft:master.


[SPARK-49540][PS] Unify the usage of distributed_sequence_id

What changes were proposed in this pull request?
in PySpark Classic, it was used via a dataframe method withSequenceColumn, while in PySpark Connect, it was used as an internal function
This PR unifies the usage of distributed_sequence_id
Why are the changes needed?
code refactoring
Does this PR introduce any user-facing change?
No
How was this patch tested?
updated tests
Was this patch authored or co-authored using generative AI tooling?
No

Nice cleanup

thanks, merged to master


Can't enable camera again - macOS BigSur

Installed the isight disabler in 2016 I can't enable the camera now again. In the meantime Apple has changed to macOS BigSur. What can I do? I'm not a professionel, so I do unfortunately have no coding skills. Thanks in advance!

macOS has changed a lot over the years with regards to iSight/FaceTime camera, drivers and just macOS in general - so the situation is potentially complex with regards to when you originally disabled it, what version of macOS it was, what version you're running now, etc.
The most straight-forward solution reported by others is re-installation of macOS. See issue #9 for some tips on other options (and confirmation of a successful re-install) but the most reliable and simple answer is probably to re-install macOS.