Notebooks on readthedocs

We want notebooks that automatically run through on readthedocs: https://nbsphinx.readthedocs.io/en/0.3.5. So that the basic tutorial (https://nbviewer.jupyter.org/github/theislab/scanpy_usage/blob/master/170505_seurat/seurat.ipynb) can be integrated into the scanpy repository in docs/tutorials as a notebook with all output cleared (no images etc.). It is run on the readthedocs server and will produce exactly the same output, as is guaranteed by this test: https://github.com/theislab/scanpy/blob/master/scanpy/tests/notebooks/pbmc3k.py

you could also consider jupytext + sphinx-gallery for this.

Why not using https://nbsphinx.readthedocs.io? It works completely fine for me. So, I would simply moved forward with it as soon as there is some bandwidth.

Sure, there's nothing wrong with nbsphinx!
Actually, the only advantage of jupytext is that it provides an elegant way to only keep the input cells of notebooks under version control.

You mean it uses/relies on nbstripout?

Pro
Con

Tests the Notebooks by running them
Docs need a long time to build

Only Text under version control

The idea is the same, but it works differently.
Jupytext allows to save jupyter notebooks as various text formats (e.g. Rmd or plain python with comments). One of the supported formats is sphinx-gallery, that can be directly rendered by readthedocs if I'm not mistaken.
Using a text-representation of notebooks is great when having them under version control.
But of course the pros/cons apply as you pointed out.

There are different ways of stripping output from jupyter notebooks, several of them can be combined with the git commit workflow. I've played around a bit with them. The only thing I need to make sure is if there is a way that people cannot commit notebooks with output in them to the scanpy repo. The latter is an absolute no go. @grst, committing things in sphinx-gallery format could be a new way. I'll check whether this offers some convenience. In general I'd rather prefer to have the stripped .ipynb files in the repo, as it's done in tensorflow.
@flying-sheep: I'm not worrying about the build time of the docs, that's decently fast in all my tests so far.
@flying-sheep: After a bit of research I've done some time ago, I also don't consider tests based on notebooks a possibility. I made versions of two notebooks running on subsampled data producing ugly looking low-resolution figures, which ensures small test times and prevents the repo from blowing up. For the tutorials, I want extremely high resolution figures and no subsampled data.
I think I should be almost there. Hopefully we'll have the first two notebooks in the Scanpy repo this or next week...

The only thing I need to make sure is if there is a way that people cannot commit notebooks with output in them to the scanpy repo. The latter is an absolute no go.

Should be easy to have that checked by travis

committing things in sphinx-gallery format could be a new way. I'll check whether this offers some convenience.

If you have any questions/issues regarding this approach, don't hesitate to open an issue in the jupytext repo. The maintainer is extremely responsive and willing to help.

@flying-sheep and anyone interested: I started putting the notebooks on scanpy-tutorials: https://github.com/theislab/scanpy-tutorials and https://scanpy.readthedocs.io/en/latest/tutorials.html now links to the docs generated from scanpy-tutorials.
I'm doing it like this for now as it's quite a bit less work than getting everything to run on readthedocs, there might indeed be problems with the runtime for building the docs and I think this updated solution isn't so bad after all...
Opinions are welcome!


hello world in Marathi

Jai Hind !!

Oh, sorry about that.... Also, I'll close this pull request as someone else with the same native language as mine already got his request merged. Thanks for the chance though :)

It's not a problem if someone else speaks the same language, everybody is welcomed! If you want to participate again, just send me a new PR following the convention and I'll accept with joy!


Add a configuration hook to run after protobuf compilation

This is intended as a simpler alternative to PRs like #494 and #549. Instead of adding additional ways to filter types, we can just expose the file descriptor set to the user and give them the power to do the filtering.
By allowing the user to inspect the file descriptor set themselves, its possible to do stuff like adding attributes to messages but not enums and oneofs
For example, with prost-reflect it can be used to annotate the messages with the message name to add reflection support
config
    .post_compile_hook(|config, file_set| {
        for file in &file_set.file {
            for message in &file.message_type {
                config.type_attribute(
                    &format!(".{}.{}", file.package(), message.name()),
                    &format!("#[derive(::prost_reflect::ReflectMessage)] #[prost_reflect(file_descriptor = \"TEST_FILE_DESCRIPTOR\", message_name = \"test.{}\")]", message.name()),
                );
            }
        }
    })

Why does this need to be a hook on config and not a free fn that you can call then allow you to call the methods on config?

I'm not sure what you mean by a free fn, could you give an example of the api you had in mind?

let file_set = prost_build::get_file_descriptor(...path config);

for file in &file_set.file {
            for message in &file.message_type {
                config.type_attribute(
                    &format!(".{}.{}", file.package(), message.name()),
                    &format!("#[derive(::prost_reflect::ReflectMessage)] #[prost_reflect(file_descriptor = \"TEST_FILE_DESCRIPTOR\", message_name = \"test.{}\")]", message.name()),
                );
            }
        }

Something like this maybe? and we can avoid the hook config

I think that works too, though there are a couple slight annoyances:

The user has to provide the protos/include paths twice
Unless the user calls skip_protoc_run on the config, we'd be running protoc twice

The main reason for the hook-based approach was so that as a library author, I can just provide an extension method like
add_reflect_message_impls(config: prost_build::Config) without the user needing to make any other changes to how they use prost_build

Yeah, I am just hesitant to adding these sort of "hooks" when I don't think they are 100% needed. I would imagine maybe going a non extension trait way might be better in this case and provide a custom config that kinda handles this. I would really to reduce the verbosity of the config struct as I think its gotten a bit out of hand and am hesitant to adding more to it. I don't think running protoc twice is that bad and as you said its still possible to disable it.


feat: Add support to parse a SecretStore as a struct using the config crate

Description of change
The config crate is pretty standard nowadays on the Rust community to parse configuration files to a Rust type.
I didn't want to fetch one by one the secrets from the SecretStore manually since the config crate does that automatically and I figured out a way to pass the contents of the SecretStore as an Environment source to the ConfigBuilder as explained here.
How has this been tested? (if applicable)
I use this implementation locally on my production software.

I wanted to implement the From crate for any T that implement DeserializeOwned but Rust doesn't allow to implement a foreign trait to a foreign type so I guess I should create some sort of wrapper around T

Probably a proper thing to do could be to implement Deserialize on the SecretsStore to a NewType SecretsConfig that contains T

Thanks for the suggestion! We will consider adding support for more opinionated ways of secrets/env loading like this one in a future update. In that case it can probably be built in without a feature flag. Will leave this PR open to keep the idea alive. More discussions can be found in #1571.


⚠ Jenkins Plugins Artifactory has degraded performance

In 6c9b44b, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1313 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 688e6a5 after 12 minutes.


refactor(frontend): computed hours for open creations

🍰 Pullrequest

Issues

None

Todo

[X] None

Good fix. Works as expected.
Tests cover 100% of the code.


FFI: Handle exceptions

Exception handling is now supported. Here is an example:
do
  propValue <- try ((systemClass <.> "getProperty(?java/lang/String)") Nothing) [
    ([catch IllegalArgumentExceptionClass, catch NullPointerExceptionClass], \t =>
        do
          printLn "property name is null or empty"
          pure Nothing
    ),
    ([catchNonFatal], \t =>
      do
        printLn "unable to get property value"
        pure Nothing
    )
  ]


Add tests

Closes #2

I see that your test failed due to the 1.7 requirement (which you've fixed in #23). I've merged that so I'll be able to merge this PR as soon as you rebase from master!

Sure, I'll rebase it right away.

As for checking out the exit calls, do you mean for when a hook check returns a non-zero exit code? Have you tried catch_exit/1? Quick glance seems like that could work.

I tried really quickly with it, doesn't seem to work, but I may missed something. Maybe we should revisit it later and try again.

@edisonywh branch rebased.

I've went ahead and merged this PR, thanks so much for your contributino @thiamsantos!
💯💯💯💯💯


feat(AlgebraicGeometry/Restrict): more API for Scheme.Opens.

You caught a merge conflict

Thanks!
maintainer-merge

Thanks!
bors merge


TopBar .contain-to-grid not available in Foundation 6 anymore?

Is there a special reason why the .contain-to-grid class doesn't exist in foundation 6 anymore? Or is there a new way to fit the top-bar into the grid?

In the Foundation 6 docs, you can can give a full-width column a container class column row which will give the same behaviour as contain-to-grid.

    ...

@ScottyZA That's the solution, thanks :)

Thanks @ScottyZA :)

I did it a little bid differently, so I could keep the full width nav color.

    ...

thanks @zacksmash

Actually, this is working with the normal grid, but using flex doesn't work anymore. You have to set width : 100% in the div containing top-bar.

Will be great that the example have to nav instead div, and the Top bar should works with navbars.

Am also facing the same problem, It doesn't work with "Flex Grid", I wish they had "contain-to-grid" in F6 also. so many features from F5 is lost.. :(
Top-Bar-Left takes the full width, forcing Tob-Bar-Right to go Below.. which is bad when using Flex-Box Grid. Whereas, in Normal grid - its fine.
Hope they fix such issues in F6
@zacksmash : Have you tried Responsive toggle in Flex-Box ??

@madhanan Yes,  you are right.


Add support of LLM to prepare variables in SequentialPlanner

Motivation and Context

See issue/feature request #1138
Description

Add support of LLM to prepare variables in SequentialPlanner
Contribution Checklist

[X] The code builds clean without any errors or warnings
[X] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[X] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[X] All unit tests pass, and I have added new tests where possible
[X] I didn't break anyone :smile:

Closing this for now while the issue continues to be discussed.


New package: GeneticBitArrays v0.2.0

Registering package: GeneticBitArrays
Repository: https://github.com/jangevaare/GeneticBitArrays.jl
Created by: @jangevaare
Version: v0.2.0
Commit: 16e6cde02d847a4a230e2f91ce0c1a48973c21e8
Reviewed by: @jangevaare
Reference: https://github.com/jangevaare/GeneticBitArrays.jl/commit/16e6cde02d847a4a230e2f91ce0c1a48973c21e8#commitcomment-35074013

Note that a PR for v0.1.0 is found here: https://github.com/JuliaRegistries/General/pull/3466

Needs a rebase.


Fix/some error

@Alex20180512. Thanks a lot for your contribution. This error was fixed in PR #231 and the solution is available in editorjs-toggle-block v0.3.15. Please let us know if the solution is helpful for you. Cheers!


Python packages required by the plugin could not be loaded due to the following error:

thanks a lot for the development of the plugin! I am looking forward to testing it out!
When trying to install the plugin either through the Plug -In manager or through the .zip file I am running into the following error:
`Attempting to install required packages...
Running command:
$ /Applications/QGIS.app/Contents/MacOS/bin/python3 -m pip install -U --target=/Users/heljo/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/deepness/python3.9opencv-python-headless>=<IP_ADDRESS>,=1.12.1,
Collecting opencv-python-headless=<IP_ADDRESS>
Using cached opencv_python_headless-<IP_ADDRESS>-cp37-abi3-macosx_10_16_x86_64.whl (55.7 MB)
Collecting onnxruntime=1.12.1
Using cached onnxruntime-1.17.0-cp39-cp39-macosx_11_0_universal2.whl (14.8 MB)
Collecting numpy>=1.17.0
Using cached numpy-1.26.4-cp39-cp39-macosx_10_9_x86_64.whl (20.6 MB)
Collecting sympy
Using cached sympy-1.12-py3-none-any.whl (5.7 MB)
Collecting protobuf
Using cached protobuf-5.26.1-cp37-abi3-macosx_10_9_universal2.whl (404 kB)
Collecting packaging
Using cached packaging-24.0-py3-none-any.whl (53 kB)
Collecting coloredlogs
Using cached coloredlogs-15.0.1-py2.py3-none-any.whl (46 kB)
Collecting flatbuffers
Using cached flatbuffers-24.3.25-py2.py3-none-any.whl (26 kB)
Collecting humanfriendly>=9.1
Using cached humanfriendly-10.0-py2.py3-none-any.whl (86 kB)
Collecting mpmath>=0.19
Using cached mpmath-1.3.0-py3-none-any.whl (536 kB)
Installing collected packages: mpmath, humanfriendly, sympy, protobuf, packaging, numpy, flatbuffers, coloredlogs, opencv-python-headless, onnxruntime
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
splot 1.1.3 requires descartes, which is not installed.
sphinx 2.4.3 requires alabaster=0.7, which is not installed.
sphinx 2.4.3 requires babel!=2.0,>=1.3, which is not installed.
sphinx 2.4.3 requires docutils>=0.12, which is not installed.
sphinx 2.4.3 requires imagesize, which is not installed.
sphinx 2.4.3 requires snowballstemmer>=1.1, which is not installed.
sphinx 2.4.3 requires sphinxcontrib-applehelp, which is not installed.
sphinx 2.4.3 requires sphinxcontrib-devhelp, which is not installed.
sphinx 2.4.3 requires sphinxcontrib-htmlhelp, which is not installed.
sphinx 2.4.3 requires sphinxcontrib-jsmath, which is not installed.
sphinx 2.4.3 requires sphinxcontrib-qthelp, which is not installed.
sphinx 2.4.3 requires sphinxcontrib-serializinghtml, which is not installed.
pysal 2.5.0 requires spopt>=0.1.2, which is not installed.
pysal 2.5.0 requires access>=1.1.3, but you have access 1.1.1 which is incompatible.
pysal 2.5.0 requires esda>=2.4.1, but you have esda 2.3.1 which is incompatible.
pysal 2.5.0 requires mapclassify>=2.4.3, but you have mapclassify 2.3.0 which is incompatible.
pysal 2.5.0 requires mgwr>=2.1.2, but you have mgwr 2.1.1 which is incompatible.
pysal 2.5.0 requires segregation>=2.0.0, but you have segregation 1.3.0 which is incompatible.
pysal 2.5.0 requires spaghetti>=1.6.2, but you have spaghetti 1.5.0 which is incompatible.
pysal 2.5.0 requires spglm>=1.0.8, but you have spglm 1.0.7 which is incompatible.
pysal 2.5.0 requires spint>=1.0.7, but you have spint 1.0.6 which is incompatible.
pysal 2.5.0 requires splot>=1.1.4, but you have splot 1.1.3 which is incompatible.
pysal 2.5.0 requires spreg>=1.2.4, but you have spreg 1.1.2.post1 which is incompatible.
pysal 2.5.0 requires tobler>=0.8.2, but you have tobler 0.3.1 which is incompatible.
pysal 2.5.0 requires urllib3>=1.26, but you have urllib3 1.24.3 which is incompatible.
Successfully installed coloredlogs-15.0.1 flatbuffers-24.3.25 humanfriendly-10.0 mpmath-1.3.0 numpy-1.26.4 onnxruntime-1.17.0 opencv-python-headless-<IP_ADDRESS> packaging-24.0 protobuf-5.26.1 sympy-1.12
Packages installed correctly!
Installation of required packages finished. Validating installation...
Python packages required by the plugin could not be loaded due to the following error:
Traceback (most recent call last):
File "/Users/heljo/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/deepness/dialogs/packages_installer/packages_installer_dialog.py", line 300, in _check_packages_installation_and_log
import_packages()
File "/Users/heljo/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/deepness/dialogs/packages_installer/packages_installer_dialog.py", line 325, in import_packages
import_package(package)
File "/Users/heljo/Library/Application Support/QGIS/QGIS3/profiles/default/python/plugins/deepness/dialogs/packages_installer/packages_installer_dialog.py", line 320, in import_package
importlib.import_module(package.import_name)
File "/Applications/QGIS.app/Contents/MacOS/../Resources/python/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 855, in exec_module
File "", line 228, in _call_with_frames_removed
File "/Applications/QGIS.app/Contents/MacOS/lib/python3.9/site-packages/opencv_contrib_python-<IP_ADDRESS>-py3.9-macosx-10.13.0-x86_64.egg/cv2/init.py", line 5, in
from .cv2 import *
File "/Applications/QGIS.app/Contents/MacOS/../Resources/python/qgis/utils.py", line 923, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
ImportError: dlopen(/Applications/QGIS.app/Contents/MacOS/lib/python3.9/site-packages/opencv_contrib_python-<IP_ADDRESS>-py3.9-macosx-10.13.0-x86_64.egg/cv2/cv2.cpython-39-darwin.so, 0x0002): Library not loaded: @rpath/libprotobuf.22.dylib
Referenced from: /Applications/QGIS.app/Contents/Resources/python/site-packages/opencv_contrib_python-<IP_ADDRESS>-py3.9-macosx-10.13.0-x86_64.egg/cv2/cv2.cpython-39-darwin.so
Reason: tried: '/opt/Qt/5.15.2/clang_64/lib/libprotobuf.22.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/Qt/5.15.2/clang_64/lib/libprotobuf.22.dylib' (no such file), '/opt/Qt/5.15.2/clang_64/lib/libprotobuf.22.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/Qt/5.15.2/clang_64/lib/libprotobuf.22.dylib' (no such file), '/Applications/QGIS.app/Contents/Frameworks/libprotobuf.22.dylib' (no such file), '/Applications/QGIS.app/Contents/MacOS/lib/libprotobuf.22.dylib' (no such file), '/Applications/QGIS.app/Contents/Resources/grass78/lib/libprotobuf.22.dylib' (no such file), '/usr/local/lib/libprotobuf.22.dylib' (no such file), '/usr/lib/libprotobuf.22.dylib' (no such file, not in dyld cache)
Please try installing the packages again.`

Hi,
looks like the installation of the packages succeded, but their verification afterwards failed. Please try to install the Python packages manually from the QGIS Python console.
Cheers
Przemek


remove note

confirmed with PM and in lab that at least one of the parameters (EnablePrivacyMode) has effect in Teams
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/9104

Docs Build status updates of commit e78d7e8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsPrivacyConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@get-itips

Docs Build status updates of commit d1bab26:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsPrivacyConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@get-itips

Does anything else in this cmdlet work for Teams?
If not, maybe we should change the note to "Only EnablePrivacyMode for federated users works for Teams".

waiting on some confirmations for now i would just remove the note

@tiburd Please merge this PR. Thanks


bool type generate Inferno Error: Expected function or string for element tag type

version 0.7.12
I did a small example of a todo and I have a field that contains a 'bool' type with true, false
Not working -> Inferno Error: Expected function or string for element tag type
const Todo = ({ todo }) =>
  (
 {todo.id}	 {todo.desc}	 {todo.done}
 );

Working with toString()
const Todo = ({ todo }) =>
  (
 {todo.id}	 {todo.desc}	 {todo.done.toString()}
 );

Is it normal to have this error, because it was not obvious? The integer type is working, but not the boolean type. The integer type is not a string or a function !
Thanks

Hi @vinej, thanks for making this issue. It's not normal to throw an error, but in either case of outputting a boolean, nothing should appear on screen unless you explicitly do to.String(). Numbers are different as they always convert to string, as they do in React and other libraries – but booleans can be used to infer that something is not to render (for example, false behaves like null and undefined within a render). Would you expect for the boolean to output as true or false too?

I understand better why it's like that. I was expecting that the toString() would be apply to any expression. As I also doing some React development, I only expect that Inferno has the same behavior than React.
Thanks

@vinej the latest dev branch of Inferno now treats true booleans like React (ignores them). I'll release an update later today. :)

https://github.com/trueadm/inferno/releases/tag/0.7.13


Modus Icon: Event Name is iconClick, not onClick as shown in Storybook and clicking causes error

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have read the contributing guidelines

Describe the issue
Component creates iconClick event
  @Event() iconClick?: EventEmitter;

But Storybook shows it has having an onClick event that is emitted

And when the icon is clicked it produces an error
Uncaught TypeError: Cannot read properties of undefined (reading 'emit')
    at Object.onClick (25.cf0f1bcf.iframe.bundle.js:1:2565)
    at IconSun.Object.onClick (0.fb127b46.iframe.bundle.js:1:421530)

This is caused by the icons onClick being set as
<IconMap ... onClick={this.onClick} ... />

when it should be this at minimum to maintain the this context.
<IconMap ... onClick={() => this.onClick()} ... />

Otherwise the context will be the icon from the icon map, not the modus-icon.
I am creating this ticket so I can work on it later.
Reduced test cases
In Storybook for MWC, navigate to the Icon component and click on the icon. Observer the javascript error in the dev console.
What operating system(s) are you seeing the problem on?
No response
What browser(s) are you seeing the problem on?
No response
What is the issue regarding ?
@trimble-oss/modus-web-components
What version of npm package are you using ?
v0.13.0
Priority
Medium
What product/project are you using Modus Components for ?
Modus
What is your team/division name ?
Modus
Are you willing to contribute ?
Maybe
Are you using Modus Web Components in production ?
No response

Closing this issue as it is fixed in #2201


WaterproofTransformer: Battery has input port.

The Waterproof Battery has an automation input port instead of an output port.
From WaterproofBatteryConfig.cs, line 44:
buildingDef.LogicInputPorts = LogicOperationalController.CreateSingleInputPortList(new CellOffset(0, 0));

Resolved


A11y_SQL Azure Data Studio_Extensions -uninstall_Screen reader: After invoking "uninstall" button Screen Reader is not announcing "Uninstallation" status whether it is uninstallation is completed or not.

GitHub Tags:
#A11ySev2; #A11yTCS; #DesktopApp; #BM_SQL Azure Data Studio_Win32_Aug2023; #SQL Azure Data Studio; #WCAG4.1.3; #ScreenReader; #Win32; #A11yWCAG2.1; #FTP; #STP; #Status Messages; #NVDA; #Narrator;
Environment Details:
Application Name: Sql Azure Data studio
Version: 1.45.1
OS: Win11
Screen Reader: NVDA Version 2023.1(2<IP_ADDRESS>913)
Repro Steps:

Launch Azure Data Studio.
From the left menu, Tab till the 'Extensions' icon and press enter to open the Extension Manager.
Choose any extension from the library.
Now Turn on NVDA/Narrator.
Tab till 'uninstall' button to uninstall and press enter.
Now verify that NVDA/Narrator is not announcing uninstallation is completed or not.

Actual Results:
After invoking "uninstallation" button Screen Reader is not announcing "uninstallation" status whether it is uninstallation is completed or not.
Note:
1.Similar issue observed with NVDA
Expected Results:
After invoking "uninstallation" button Screen Reader should announce "uninstallation" status whether it is installation is completed or not.
User Impact:
Screen reader user will not be able to know uninstallation status whether it is uninstallation is completed or not. If NVDA/Narrator not announcing.
Attachment:
Uninstalled not fixed Narrator.webm
Uninstalled not fixed NVDA.webm

@PadminiGariki
After the uninstallation is started, the screenreader says "Please reload Azure Data Studio to complete the uninstallation of the extension" - is this not acceptable as announcing that ADS needs to be restarted to complete the uninstallation?

verified the bug in this environment Latest insiders build.
As per above comment  we check this bug. "Please reload Azure Data Studio to complete the uninstallation of the extension". This message also acceptable. Because screen reader know about the uninstallation is completed or not.
Here Issue is fixed.
Hence that Bug is Closed.
Attachments is added for reference.
#Closed; #Regressed:10-31-23;
Issue is fixed with Narrator.webm
Issue is fixed with NVDA.webm

closing issue after the confirmation above.


proof instability / flakiness

I'm running into lots of cases where touching something somewhere in a file causes a failure in an unrelated fn. Informally, it seems like this happens a lot in verus, where it was very rare in Dafny.
Here's a particularly egregious case. Add this completely standalone function commute_transitivity to the file, and a proof a hundred lines prior suddenly stops verifying.
Such flakiness is very disheartening; it changes the user experience from "a long slog" to "am I even making forward progress?"
Repro:
git clone git@github.com:vmware-labs/verified-betrfs.git
git checkout c4e28489b98851127ae017bfc7c51a97bfc298ef
cd verified-betrfs/Splinter
$verus --time --expand-errors --multiple-errors 5 src/bundle.rs --verify-module journal::LinkedJournal_v::LinkedJournal --verify-module journal::LinkedJournal_v

...passes, but uncomment commute_transitivity and unrelated build_tight_is_awesome fails.

which version of verus are you using @jonhnet ?

ce715d977f801747d12b35079b4ed073f48b9e43 from yesterday

Just hit another spooky-flake-at-a-distance:
git clone git@github.com:vmware-labs/verified-betrfs.git
git checkout f1135cd2f93f5bef694f590284e422d612ecc27d
cd verified-betrfs/Splinter
$verus --time --expand-errors --multiple-errors 5 src/bundle.rs --verify-module journal::LinkedJournal_v::LinkedJournal --verify-module journal::LinkedJournal_v

@yizhou7 note that I made a copy-paste mistake in my repro instructions in the first comment above; it wasn't --verify-moduleing the module with the actual change in it. Corrected above.

I ran mariposa on the repo state before the change that would trigger instability, for the above two cases respectively. FWIW, the two failing functions were labeled as unstable at that point already.
The comment on the query:
;; Function-Def bundle::journal::LinkedJournal_v::DiskView::build_tight_is_awesome
query: gen/journal__LinkedJournalRefinement_v.smt2_/split.10.smt2
| mutation   | status   | success      | mean(second)   | std(second)   |
|------------|----------|--------------|----------------|---------------|
| overall    | unstable | x            | x              | x             |
| shuffle    | unstable | 36/61 59.0%  | 0.05           | 0.01          |
| rename     | stable   | 61/61 100.0% | 0.05           | 0.01          |
| reseed     | stable   | 61/61 100.0% | 0.05           | 0.0           |
| quake      | unstable | 51/61 83.6%  | 0.03           | 0.0           |

The comment on the query:
;; Function-Def bundle::journal::LinkedJournal_v::DiskView::tight_empty_disk
query: gen/journal__LinkedJournal_v.smt2_/split.17.smt2
| mutation   | status   | success      | mean(second)   | std(second)   |
|------------|----------|--------------|----------------|---------------|
| overall    | unstable | x            | x              | x             |
| shuffle    | stable   | 61/61 100.0% | 0.02           | 0.0           |
| rename     | stable   | 61/61 100.0% | 0.02           | 0.0           |
| reseed     | stable   | 61/61 100.0% | 0.02           | 0.0           |
| quake      | unstable | 37/61 60.7%  | 0.01           | 0.0           |

Moved to https://github.com/verus-lang/verus/discussions/147.


Enable rf sec motion sensors devices + Previous commit

This is the second of my two commits.  It includes the first commit.
Looking forward to your changes/comments.
Again, this is my first time, so please be gentle.

@jimcghee my HA system has been humming along so I hadn't looked at this in a while.  Thanks for the contributions.


[FR] Move to PyPA org on PyPI?

What's the problem this feature will solve?
PyPA projects consolidation and continued access to publishing to PyPI?
Describe the solution you'd like
With the orgs feature on PyPI, there's a PyPA org that exists already — https://pypi.org/org/pypa/. Why not make use of it?
Alternative Solutions
No response
Additional context
No response
Code of Conduct

[X] I agree to follow the PSF Code of Conduct

See https://github.com/pypa/pip/issues/12250#issuecomment-1698025213 -- let's hold off on this.


Move apps to data file

Easier to update the list now.
Also fixed the app descriptions, so you can read what the app is w/o having to click the link.

If this is merged then #157, #231, #233 and #234 might want to rebase and update their PRs too.

Would you mind making this a JSON or YAML file? CSV is quite unwieldy and difficult to maintain.

This was done as part of the Electron 10 relaunch that just happened and was merged in #238
There is now an apps.yml file that powers http://electron.atom.io/apps/
Thanks for opening this but I think we are all set now and I'm going to close this out. Apologies for the delayed response and thanks for contributing :shipit:

Will you accept a PR that adds the description into the title attribute? IMO while it's nice one can see the name of the app, this new design still suffers from the same problem... I have to click on the link to find out what the app does.

Will you accept a PR that adds the description into the title attribute?

Yup, that would be great, thanks.


RecordVideo not recording any videos anymore in 0.26.x

Describe the bug
Hello,
since the change in 0.26.0 of the render_mode flag, the gym.wrappers.RecordVideo does not work anymore.
When recording the video we are getting the following log message:
.../lib/python3.8/site-packages/gym/wrappers/monitoring/video_recorder.py:59: UserWarning: WARN: Disabling video recorder because environment <OrderEnforcing<PassiveEnvChecker<AtariEnv<ALE/Pong-v5>>>> was not initialized with any compatible video mode between rgb_array and rgb_array_list

We are setting the render_mode when creating the environment, as showed in the blog for the 0.26.0 release, but the render_mode flag no longer gets set, leading to the warning and videos not being recorded.
Here is a code sample that can help with the issue replication:
Code example
import gym

env = gym.make("ALE/Pong-v5", render_mode="rgb_array")

env = gym.wrappers.RecordVideo(
  env,
  video_folder='video',
  step_trigger=lambda x: x % 100 == 0
)

env.reset()
for t in range(100):
  action = env.action_space.sample()
  observation, reward, terminated, truncated, info = env.step(action)

env.close()

System info
Gym 0.26.2, Python 3.8.10.
Additional context
No response
Checklist

[X] I have checked that there is no similar issue in the repo

After further investigation, this seems to be an issue with the ALE, where in the AtariEnv, the self.render_mode is set to None, as the class uses another variable self._render_mode instead. Should this be addressed in the ALE repo?

Yes, I think ALE store the render_mode in self._render_mode as atari made the change before gym.
Could you make an issue on the ALE-py repo
In the meantime, I would set the render_mode after, env.render_mode = "rgb_array"

Thanks @pseudo-rnd-thoughts ! Reported the issue there.
Unfortunately the workaround you suggested does not work, as render_mode is a read-only property for the gym  wrappers, which are used to wrap the AtariEnv object.

Ahh, what about env.unwrapped.render_mode = "rgb_array"?

Thanks @pseudo-rnd-thoughts, that indeed worked! Closing this issue!


Create nostr profile

Allows you to create a nostr profile. Added a sync_nostr function that'll sync up their profile with primal, that way we can fetch changes made outside the app

needs rebase

Can you rebase to master plz

Can you manually cut a release without merging here? Should be able to from the command line, might as well make it 0.6.0-rc1


get the pure periodic components in matlab

Hi!
I'm using MATLAB R2023a and Python 3.9.
I've successfully obtained the FOOOF results using the fooof_mat wrapper.
My colleague mentioned that they can extract the pure periodic components without the aperiodic components using Python. I'm curious if there are any methods to achieve the same in MATLAB, as I'm not very proficient in Python.
Thank you for your time in advance.

Hey @thisistianjing - the matlab wrapper here does support getting the model fit - you can get the full model fit and aperiodic fit in the fooof_get_model function. I'm not sure why I didn't add the periodic fit there (ooops), but you should be able to recalculate it by subtracting the aperiodic fit from the periodic fit.
More generally, this wrapper is a fairly minimal wrapper to fit the model and get the model parameters, so not everything in the python toolbox is available. In general, it should be fairly straight-forward to extend it to get other features, if you want to try and do that.


remove mention to sort in Window example

Removes the mention of sorting in the Window example.
see discussion here: https://github.com/pola-rs/polars/issues/8958

deleting, I will do another PR.
this no longer works with the 0.18 updates


Update Project Reunion nuspec to require .NET 5 or greater

Describe the bug
This is stated in the docs already as a requirement, but it would be good to have an check in the product.
Steps to reproduce the bug
Currently you get a non-obvious error if you try to build an app that uses MRTCore in Project Reunion with a version of .NET lower than 5.
Expected behavior
It would be helpful to have a clear error at the outset of trying to use Project Reunion.
Version Info
This is true for version 0.5 of Project Reunion.

UWP apps using .NET Native can't use Project Reunion features if you did this until you provide .NET 5 for UWP apps. Even Win32 apps using frameworks like WinForms and WPF can, why can't apps using the state of the art app model use .NET 5?

Hey @Jaiganeshkumaran, with nuspec TFMs, we're actually able to target both UWP and .NET 5 apps from one package.
For example, the Windows Community Toolkit Notifications library supports both UWP (non-.NET 5 apps) and Desktop Windows .NET 5 apps (WPF/WinForms/console/etc).
We similarly can update the nuspec to have two TFMs...

net5.0-windows10.0.17763 (this targets .NET 5 WPF/WinForms/etc apps)
uap10.0.17763 (this targets UWP apps)


fix: fix containerruntime display in cluster detail

Signed-off-by: moweiwei<EMAIL_ADDRESS>
What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for reviewers:

Does this PR introduced a user-facing change?

Additional documentation, usage docs, etc.:

/lgtm
/approve

/cherrypick release-1.3


cran release todos

please omit the redundant "Utility Functions for" from the title.
Please remove the sinlge quotes around "phasing", single quotes should
only be used around package/software names.
If there are references describing the methods in your package, please
add these in the description field of your DESCRIPTION file in the form
authors (year) doi:...
authors (year, ISBN:...)
or if those are not available: https:...
with no space after 'doi:', 'https:' and angle brackets for
auto-linking. (If you want to add a title as well please put it in
quotes: "Title")
For more details:
https://contributor.r-project.org/cran-cookbook/description_issues.html#references
Please add \value to .Rd files regarding exported methods and explain
the functions results in the documentation. Please write about the
structure of the output (class) and also what the output means. (If a
function does not return a value, please document that too, e.g.
\value{No return value, called for side effects} or similar) -> Missing
Rd-tags:
haplotypePainter.Rd: \value
plotAltVsRef.Rd: \value
plotObsExpWSAF.Rd: \value
plotProportions.Rd: \value
plotWSAFvsPLAF.Rd: \value
For more details:
https://contributor.r-project.org/cran-cookbook/docs_issues.html#missing-value-tags-in-.rd-files
Some code lines in examples are commented out. Please never do that.
Ideally find toy examples that can be regularly executed and checked.
Lengthy examples (> 5 sec), can be wrapped in \donttest{}. -> Examples
in comments in:
plotProportions.Rd
You write information messages to the console that cannot be easily
suppressed.
It is more R like to generate objects that can be used to extract the
information a user is interested in, and then print() that object.
Instead of print()/cat() rather use message()/warning() or
if(verbose)cat(..) (or maybe stop()) if you really have to write text to
the console. (except for print, summary, interactive functions) ->
R/errorAnalysis.r; R/interface.R; R/plotting.R
For more details:
https://contributor.r-project.org/cran-cookbook/code_issues.html#using-printcat
Please ensure that your functions do not write by default or in your
examples/vignettes/tests in the user's home filespace (including the
package directory and getwd()). This is not allowed by CRAN policies.
Please omit any default path in writing functions. In your
examples/vignettes/tests you can write to tempdir(). -> R/plotting.R
For more details:
https://contributor.r-project.org/cran-cookbook/code_issues.html#writing-files-and-directories-to-the-home-filespace
Please make sure that you do not change the user's options, par or
working directory. If you really have to do so within functions, please
ensure with an immediate call of on.exit() that the settings are reset
when the function is exited.
e.g.:
...
oldpar <- par(no.readonly = TRUE) # code line i
on.exit(par(oldpar)) # code line i + 1
...
par(mfrow=c(2,2)) # somewhere after
...
-> R/errorAnalysis.r; R/plotting.R
If you're not familiar with the function, please check ?on.exit. This
function makes it possible to restore options before exiting a function
even if the function breaks. Therefore it needs to be called immediately
after the option change within a function.
For more details:
https://contributor.r-project.org/cran-cookbook/code_issues.html#change-of-options-graphical-parameters-and-working-directory
Please do not modify the user's global environment or the user's home
filespace in your examples or vignettes by deleting objects rm(list =
ls()) -> inst/scripts/dataExplore.r, inst/scripts/interpretDEploid.r
Please always add all authors, contributors and copyright holders in the
Authors@R field with the appropriate roles.
From CRAN policies you agreed to:
"The ownership of copyright and intellectual property rights of all
components of the package must be clear and unambiguous (including from
the authors specification in the DESCRIPTION file). Where code is copied
(or derived) from the work of others (including from R itself), care
must be taken that any copyright/license statements are preserved and
authorship is not misrepresented.
Preferably, an ‘Authors@R’ would be used with ‘ctb’ roles for the
authors of such code. Alternatively, the ‘Author’ field should list
these authors as contributors. Where copyrights are held by an entity
other than the package authors, this should preferably be indicated via
‘cph’ roles in the ‘Authors@R’ field, or using a ‘Copyright’ field (if
necessary referring to an inst/COPYRIGHTS file)." e.g.: Deepak
Bandyopadhyay, Lutz Kettner in gzstream.cpp
Please explain in the submission comments what you did about this issue.
For more details:
https://contributor.r-project.org/cran-cookbook/description_issues.html#using-authorsr

cran released
https://cran.r-project.org/web/packages/DEploid.utils/index.html


[Snyk] Upgrade mongodb from 6.5.0 to 6.10.0

Snyk has created this PR to upgrade mongodb from 6.5.0 to 6.10.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 86 versions ahead of your current version.

The recommended version was released on a month ago.

Release notes

Package name: mongodb

6.10.0 - 2024-10-216.10.0 (2024-10-21)
The MongoDB Node.js team is pleased to announce version 6.10.0 of the mongodb package!
Release Notes
WarningServer versions 3.6 and lower will get a compatibility error on connection and support for MONGODB-CR authentication is now also removed.

Support for new client bulkWrite API (8.0+)
A new bulk write API on the MongoClient is now supported for users on server versions 8.0 and higher.
This API is meant to replace the existing bulk write API on the Collection as it supports a bulk
write across multiple databases and collections in a single call.
Usage
Users of this API call MongoClient#bulkWrite and provide a list of bulk write models and options.
The models have a structure as follows:
Insert One
Note that when no _id field is provided in the document, the driver will generate a BSON ObjectId
automatically.
{
  namespace: '<db>.<collection>',
  name: 'insertOne',
  document: Document
}
Update One
{
  namespace: '<db>.<collection>',
  name: 'updateOne',
  filter: Document,
  update: Document | Document[],
  arrayFilters?: Document[],
  hint?: Document | string,
  collation?: Document,
  upsert: boolean
}
Update Many
Note that write errors occuring with an update many model present are not retryable.
{
  namespace: '<db>.<collection>',
  name: 'updateMany',
  filter: Document,
  update: Document | Document[],
  arrayFilters?: Document[],
  hint?: Document | string,
  collation?: Document,
  upsert: boolean
}
Replace One
{
  namespace: '<db>.<collection>',
  name: 'replaceOne',
  filter: Document,
  replacement: Document,
  hint?: Document | string,
  collation?: Document
}
Delete One
{
  namespace: '<db>.<collection>',
  name: 'deleteOne',
  filter: Document,
  hint?: Document | string,
  collation?: Document
}
Delete Many
Note that write errors occuring with a delete many model present are not retryable.*
{
  namespace: '<db>.<collection>',
  name: 'deleteMany',
  filter: Document,
  hint?: Document | string,
  collation?: Document
}
Example
Below is a mixed model example of using the new API:
const client = new MongoClient(process.env.MONGODB_URI);
const models = [
  {
    name: 'insertOne',
    namespace: 'db.authors',
    document: { name: 'King' }
  },
  {
    name: 'insertOne',
    namespace: 'db.books',
    document: { name: 'It' }
  },
  {
    name: 'updateOne',
    namespace: 'db.books',
    filter: { name: 'it' },
    update: { $set: { year: 1986 } }
  }
];
const result = await client.bulkWrite(models);
The bulk write specific options that can be provided to the API are as follows:

ordered: Optional boolean that indicates the bulk write as ordered. Defaults to true.
verboseResults: Optional boolean to indicate to provide verbose results. Defaults to false.
bypassDocumentValidation: Optional boolean to bypass document validation rules. Defaults to false.
let: Optional document of parameter names and values that can be accessed using $$var. No default.

The object returned by the bulk write API is:
interface ClientBulkWriteResult {
  // Whether the bulk write was acknowledged.
  readonly acknowledged: boolean;
  // The total number of documents inserted across all insert operations.
  readonly insertedCount: number;
  // The total number of documents upserted across all update operations.
  readonly upsertedCount: number;
  // The total number of documents matched across all update operations.
  readonly matchedCount: number;
  // The total number of documents modified across all update operations.
  readonly modifiedCount: number;
  // The total number of documents deleted across all delete operations.
  readonly deletedCount: number;
  // The results of each individual insert operation that was successfully performed.
  // Note the keys in the map are the associated index in the models array.
  readonly insertResults?: ReadonlyMap<number, ClientInsertOneResult>;
  // The results of each individual update operation that was successfully performed.
  // Note the keys in the map are the associated index in the models array.
  readonly updateResults?: ReadonlyMap<number, ClientUpdateResult>;
  // The results of each individual delete operation that was successfully performed.
  // Note the keys in the map are the associated index in the models array.
  readonly deleteResults?: ReadonlyMap<number, ClientDeleteResult>;
}
Error Handling
Server side errors encountered during a bulk write will throw a MongoClientBulkWriteError. This error
has the following properties:

writeConcernErrors: Ann array of documents for each write concern error that occurred.
writeErrors: A map of index pointing at the models provided and the individual write error.
partialResult: The client bulk write result at the point where the error was thrown.

Schema assertion support
interface Book {
name: string;
authorName: string;
}
interface Author {
name: string;
}
type MongoDBSchemas = {
'db.books': Book;
'db.authors': Author;
}
const model: ClientBulkWriteModel<MongoDBSchemas> = {
namespace: 'db.books'
name: 'insertOne',
document: { title: 'Practical MongoDB Aggregations', authorName: 3 }
// error authorName cannot be number
};
Notice how authorName is type checked against the Book type because namespace is set to "db.books".
Allow SRV hostnames with fewer than three . separated parts
In an effort to make internal networking solutions easier to use like deployments using kubernetes, the client now accepts SRV hostname strings with one or two . separated parts.
await new MongoClient('mongodb+srv://mongodb.local').connect();
For security reasons, the returned addresses of SRV strings with less than three parts must end with the entire SRV hostname and contain at least one additional domain level. This is because this added validation ensures that the returned address(es) are from a known host. In future releases, we plan on extending this validation to SRV strings with three or more parts, as well.
mySite.com'
// Example 3: Validation passes since the returned address ends with the entire SRV hostname and contains an additional domain level
'mongodb+srv://mySite.com' => 'cluster_1.mySite.com' ">// Example 1: Validation fails since the returned address doesn't end with the entire SRV hostname
'mongodb+srv://mySite.com' => 'myEvilSite.com'
// Example 2: Validation fails since the returned address is identical to the SRV hostname
'mongodb+srv://mySite.com' => 'mySite.com'
// Example 3: Validation passes since the returned address ends with the entire SRV hostname and contains an additional domain level
'mongodb+srv://mySite.com' => 'cluster_1.mySite.com'
Explain now supports maxTimeMS
Driver CRUD commands can be explained by providing the explain option:
collection.find({}).explain('queryPlanner'); // using the fluent cursor API
collection.deleteMany({}, { explain: 'queryPlanner' }); // as an option
However, if maxTimeMS was provided, the maxTimeMS value was applied to the command to explain, and consequently the server could take more than maxTimeMS to respond.
Now, maxTimeMS can be specified as a new option for explain commands:
collection.find({}).explain({ verbosity: 'queryPlanner', maxTimeMS: 2000 }); // using the fluent cursor API
collection.deleteMany({}, {
	explain: {
		verbosity: 'queryPlanner',
		maxTimeMS: 2000
	}
); // as an option
If a top-level maxTimeMS option is provided in addition to the explain maxTimeMS, the explain-specific maxTimeMS is applied to the explain command, and the top-level maxTimeMS is applied to the explained command:
collection.deleteMany({}, {
maxTimeMS: 1000,
explain: {
verbosity: 'queryPlanner',
maxTimeMS: 2000
}
);
// the actual command that gets sent to the server looks like:
{
explain: { delete: <collection name>, ..., maxTimeMS: 1000 },
verbosity: 'queryPlanner',
maxTimeMS: 2000
}
Find and Aggregate Explain in Options is Deprecated
NoteSpecifying explain for cursors in the operation's options is deprecated in favor of the .explain() methods on cursors:

collection.find({}, { explain: true })
// -> collection.find({}).explain()
collection.aggregate([], { explain: true })
// -> collection.aggregate([]).explain()
db.find([], { explain: true })
// -> db.find([]).explain()
Fixed writeConcern.w set to 0 unacknowledged write protocol trigger
The driver now correctly handles w=0 writes as 'fire-and-forget' messages, where the server does not reply and the driver does not wait for a response. This change eliminates the possibility of encountering certain rare protocol format, BSON type, or network errors that could previously arise during server replies. As a result, w=0 operations now involve less I/O, specifically no socket read.
In addition, when command monitoring is enabled, the reply field of a CommandSucceededEvent of an unacknowledged write will always be { ok: 1 }.
Fixed indefinite hang bug for high write load scenarios
When performing large and many write operations, the driver will likely encounter buffering at the socket layer. The logic that waited until buffered writes were complete would mistakenly drop 'data' (reading from the socket), causing the driver to hang indefinitely or until a socket timeout. Using pausing and resuming mechanisms exposed by Node streams we have eliminated the possibility for data events to go unhandled.
Shout out to @ hunkydoryrepair for debugging and finding this issue!
Fixed change stream infinite resume
Before this fix, when change streams would fail to establish a cursor on the server, the driver would infinitely attempt to resume the change stream. Now, when the aggregate to establish the change stream fails, the driver will throw an error and clos the change stream.
ClientSession.commitTransaction() no longer unconditionally overrides write concern
Prior to this change, ClientSession.commitTransaction() would always override any previously configured writeConcern on the initial attempt. This overriding behaviour now only applies to internal and user-initiated retries of ClientSession.commitTransaction() for a given transaction.
Features

NODE-5838: remove support for server 3.6 (#4182) (7b71e1f)
NODE-6289: allow valid srv hostnames with less than 3 parts (#4197) (3d5bd51)
NODE-6329: client bulk write happy path (#4206) (3d3da40)
NODE-6337: implement client bulk write batching (#4248) (d56e235)
NODE-6338: implement client bulk write error handling (#4262) (8def42d)
NODE-6342: support maxTimeMS for explain commands (#4207) (20396e1)
NODE-6350: add typescript support to client bulkWrite API (#4257) (30c61f2)
NODE-6409: new errors for unacknowledged bulk writes (#4276) (7fde8dd)
NODE-6419: deprecate explain options API for find and aggregate (#4271) (a473de9)

Bug Fixes

NODE-6060: set fire-and-forget protocol when writeConcern is w: 0 (#4219) (643a875)
NODE-6394: data events missed while awaiting drain (#4249) (3f9d243)
NODE-6418: change stream resumes infinitely after failed aggregates (#4267) (6ecf198)
NODE-6436: only force majority write concern on commitTransaction retry (#4284) (a7d1d43)

Documentation

Reference
API
Changelog

We invite you to try the mongodb library immediately, and report any issues to the NODE project.

6.10.0-dev.20241116.sha.aa986f8e - 2024-11-16

6.10.0-dev.20241115.sha.1320ad87 - 2024-11-15

6.10.0-dev.20241113.sha.20564f7a - 2024-11-13

6.10.0-dev.20241112.sha.48ed47ec - 2024-11-12

6.10.0-dev.20241109.sha.ed25d561 - 2024-11-09

6.10.0-dev.20241108.sha.fd7acde6 - 2024-11-08

6.10.0-dev.20241107.sha.e5582ed7 - 2024-11-07

6.10.0-dev.20241106.sha.dc3fe957 - 2024-11-06

6.10.0-dev.20241102.sha.2f3fb466 - 2024-11-02

6.10.0-dev.20241101.sha.5e6638a2 - 2024-11-01

6.10.0-dev.20241031.sha.f62c45d2 - 2024-10-31

6.10.0-dev.20241024.sha.5c4355ad - 2024-10-24

6.10.0-dev.20241022.sha.678e9322 - 2024-10-22

6.9.0 - 2024-09-126.9.0 (2024-09-06)
The MongoDB Node.js team is pleased to announce version 6.9.0 of the mongodb package!
Release Notes
Driver support of upcoming MongoDB server release
Increased the driver's max supported Wire Protocol version and server version in preparation for the upcoming release of MongoDB 8.0.
MongoDB 3.6 server support deprecated
WarningSupport for 3.6 servers is deprecated and will be removed in a future version.

Support for explicit resource management
The driver now natively supports explicit resource management for MongoClient, ClientSession, ChangeStreams and cursors.  Additionally, on compatible Node.js versions, explicit resource management can be used with cursor.stream() and the GridFSDownloadStream, since these classes inherit resource management from Node.js' readable streams.
This feature is experimental and subject to changes at any time.  This feature will remain experimental until the proposal has reached stage 4 and Node.js declares its implementation of async disposable resources as stable.
To use explicit resource management with the Node driver, you must:

Use Typescript 5.2 or greater (or another bundler that supports resource management)
Enable tslib polyfills for your application
Either use a compatible Node.js version or polyfill Symbol.asyncDispose (see the TS 5.2 release announcement for more information).

Explicit resource management is a feature that ensures that resources' disposal methods are always called when the resources' scope is exited.  For driver resources, explicit resource management guarantees that the resources' corresponding close method is called when the resource goes out of scope.
// before:
{
try {
const client = MongoClient.connect('<uri>');
try {
const session = client.startSession();
const cursor = client.db('my-db').collection("my-collection").find({}, { session });
try {
const doc = await cursor.next();
} finally {
await cursor.close();
}
} finally {
await session.endSession();
}
} finally {
await client.close();
}
}
// with explicit resource management:
{
await using client = MongoClient.connect('<uri>');
await using session = client.startSession();
await using cursor = client.db('my-db').collection('my-collection').find({}, { session });
const doc = await cursor.next();
}
// outside of scope, the cursor, session and mongo client will be cleaned up automatically.
The full explicit resource management proposal can be found here.
Driver now supports auto selecting between IPv4 and IPv6 connections
For users on Node versions that support the autoSelectFamily and autoSelectFamilyAttemptTimeout options (Node 18.13+), they can now be provided to the MongoClient and will be passed through to socket creation. autoSelectFamily will default to true with autoSelectFamilyAttemptTimeout by default not defined. Example:
const client = new MongoClient(process.env.MONGODB_URI, { autoSelectFamilyAttemptTimeout: 100 });
Allow passing through allowPartialTrustChain Node.js TLS option
This option is now exposed through the MongoClient constructor's options parameter and controls the X509_V_FLAG_PARTIAL_CHAIN OpenSSL flag.
Fixed enableUtf8Validation option
Starting in v6.8.0 we inadvertently removed the ability to disable UTF-8 validation when deserializing BSON. Validation is normally a good thing, but it was always meant to be configurable and the recent Node.js runtime issues (v22.7.0) make this option indispensable for avoiding errors from mistakenly generated invalid UTF-8 bytes.
Add duration indicating time elapsed between connection creation and when the connection is ready
ConnectionReadyEvent now has a durationMS property that represents the time between the connection creation event and when the connection ready event is fired.
Add duration indicating time elapsed between the beginning and end of a connection checkout operation
ConnectionCheckedOutEvent/ConnectionCheckFailedEvent now have a durationMS property that represents the time between checkout start and success/failure.
Create native cryptoCallbacks 🔐
Node.js bundles OpenSSL, which means we can access the crypto APIs from C++ directly, avoiding the need to define them in JavaScript and call back into the JS engine to perform encryption. Now, when running the bindings in a version of Node.js that bundles OpenSSL 3 (should correspond to Node.js 18+), the cryptoCallbacks option will be ignored and C++ defined callbacks will be used instead. This improves the performance of encryption dramatically, as much as 5x faster. 🚀
This improvement was made to<EMAIL_ADDRESS>which is available now!
Only permit mongocryptd spawn path and arguments to be own properties
We have added some defensive programming to the options that specify spawn path and spawn arguments for mongocryptd due to the sensitivity of the system resource they control, namely, launching a process. Now, mongocryptdSpawnPath and mongocryptdSpawnArgs must be own properties of autoEncryption.extraOptions. This makes it more difficult for a global prototype pollution bug related to these options to occur.
Support for range v2: Queryable Encryption supports range queries
Queryable encryption range queries are now officially supported.  To use this feature, you must:

use a version of mongodb-client-encryption > 6.1.0
use a Node driver version > 6.9.0
use an 8.0+ MongoDB enterprise server

ImportantCollections and documents encrypted with range queryable fields with a 7.0 server are not compatible with range queries on 8.0 servers.

Documentation for queryable encryption can be found in the MongoDB server manual.
insertMany and bulkWrite accept ReadonlyArray inputs
This improves the typescript developer experience, developers tend to use ReadonlyArray because it can help understand where mutations are made and when enabling noUncheckedIndexedAccess leads to a better type narrowing experience.
Please note, that the array is read only but not the documents, the driver adds _id fields to your documents unless you request that the server generate the _id with forceServerObjectId
Fix retryability criteria for write concern errors on pre-4.4 sharded clusters
Previously, the driver would erroneously retry writes on pre-4.4 sharded clusters based on a nested code in the server response (error.result.writeConcernError.code). Per the common drivers specification, retryability should be based on the top-level code (error.code). With this fix, the driver avoids unnecessary retries.
The LocalKMSProviderConfiguration's key property accepts Binary for auto encryption
In #4160 we fixed a type issue where a local KMS provider at runtime accepted a BSON Binary instance but the Typescript inaccurately only permitted Buffer and string. The same change has now been applied to AutoEncryptionOptions.
BulkOperationBase (superclass of UnorderedBulkOperation and OrderedBulkOperation) now reports length property in Typescript
The length getter for these classes was defined manually using Object.defineProperty which hid it from typescript. Thanks to @ sis0k0 we now have the getter defined on the class, which is functionally the same, but a greatly improved DX when working with types. 🎉
MongoWriteConcernError.code is overwritten by nested code within MongoWriteConcernError.result.writeConcernError.code
MongoWriteConcernError is now correctly formed such that the original top-level code is preserved

If no top-level code exists, MongoWriteConcernError.code should be set to MongoWriteConcernError.result.writeConcernError.code
If a top-level code is passed into the constructor, it shouldn't be changed or overwritten by the nested writeConcernError.code

Optimized cursor.toArray()
Prior to this change, toArray() simply used the cursor's async iterator API, which parses BSON documents lazily (see more here). toArray(), however, eagerly fetches the entire set of results, pushing each document into the returned array.  As such, toArray does not have the same benefits from lazy parsing as other parts of the cursor API.
With this change, when toArray() accumulates documents, it empties the current batch of documents into the array before calling the async iterator again, which means each iteration will fetch the next batch rather than wrap each document in a promise. This allows the cursor.toArray() to avoid the required delays associated with async/await execution, and allows for a performance improvement of up to 5% on average! 🎉
Note: This performance optimization does not apply if a transform has been provided to cursor.map() before toArray is called.
Fixed mixed use of cursor.next() and cursor[Symbol.asyncIterator]
In 6.8.0, we inadvertently prevented the use of cursor.next() along with using for await syntax to iterate cursors. If your code made use of the following pattern and the call to cursor.next retrieved all your documents in the first batch, then the for-await loop would never be entered. This issue is now fixed.
const firstDoc = await cursor.next();
for await (const doc of cursor) {
// process doc
// ...
}
Features

NODE-5459: add durations to connection pool events (#4166) (7295695)
NODE-5614: add support for explicit resource management (#4177) (b3f3987)
NODE-5754: allow auto select family options (#4185) (54efb7d)
NODE-5908: support range v2 (<a href="https://redirect.github.com/mongodb/node-mongodb-native/issues/4141" data-hovercard-type="pull_request" data-hovercard-url="/mongodb/node-mongodb-native/pull/4141/...

@hashgraph/developer-advocates-guardian please review and merge this bump if appropriate


App Spatial: show Map of Datasets

Maybe with an ST_Envelope() function as an optional tab with possibility of subsetting by tags.

ST_Envelope with ST_Simplify to produce quick footprints of each dataset for display
Show Location (eg red polygon) on top of the datasets (eg blue polygons), optionally filtered by Tags
Defaults to Table view, but can then show Map view too

Source: app Spatial with Map tab - Google Drawings

See also datasets app:
https://shiny.marineenergy.app/datasets


Update repositories.txt

Added URL to a new library that we will use for an Arduino-based high-altitude weather balloon.

@ArduinoBot

@ArduinoBot


fix: make env vars fallback to empty strings

This PR replaces import.meta.env statements with empty strings that were not replaced.
This fix an issue where if you don't define an environment it will not replace the statement and fail at runtime

oh yeah ... it should not use renderChunk ... i'll fix

not sure why tests are failing now...

yeah tests are a little bit flaky. I can make it all pass on my machine (sometimes after a few retries)

Not worry.It doesn't matter.

I don't think it needs to be that complicated - let me know if this fixes it for you: 7994d35

well yeah haha most likely ! thanks


M-League fantasy league

I can't believe my permissions to push directly got removed

it's fine eigamma took his meds now


flannel: use the correct network interface

/cc @eyakubovich
Is it ok to add the flannel/interface parameter even if flannel is not installed?

LGTM. It should be harmless to have flannel parameters if it's not running. This was a much needed PR.


Property 'arrayElement' does not exist on type 'Random'.

What are the steps to reproduce this issue?

Run Orval with a schema with Array or Enum Elements in an Array. days?: Array<DaysEnum>;

What happens?
Orval generates mocks with faker.random.arrayElement(). But arrayElement does not exist on random, it is now on helpers.
What were you expecting to happen?
Orval should generate mocks with faker.helpers.arrayElement().
Any other comments?
Probably just a breaking change with FakerJS?
What versions are you using?
Operating System: macOS Monterey 12.4
Package Version: 6.8.1
Browser Version: Chrome 103.0.5060.114

@AO19 I would like to work on this issue, Could you assign this to me?

I can not assign you to this issue, I think @anymaniax has to do it.

Hello, it's because of the new version of faker. It's already done and will be in the next release

Alright, thank you for your response.


Feature m instruction set

Length Assertion in JALR instruction was faulty.
Implements MULHSU and MULHU.
Fixes overflow bug in MULH

Hey! Thanks for these fixes! Do you mind adding a filecheck test that passes now but failed previously? I feel that this would help greatly in improving confidence in the emulation accuracy!
Something like this should do:
// RUN: riscemu -o libc %s | filecheck %s

.text
.globl main
main:
    li a0, 0xabcdefgh...
    mulh a1, a0, a0
    print a1
// CHECK: register a1 contains value ...
    mulhu a1, a0, a0
    print a1
// CHECK-NEXT: register a1 contains value ...

Hey  @Joshy1970, if you need help with this or have any questions, feel free to let me know!

Hey, I got sick but will be working on it in one or two days. Seems straightforward, so I think I don't need help, but thanks for offering, and sorry for being absent for so long

Heya, sorry for the lack of response, we had a busy few weeks and this fell under the table. It looks like you tried to rebase these changes in a weird way, can you try to make the diff a bit smaller?

If you're okay with it I'd give rebasing and cleaning up the conflicts a go myself. Sorry again for letting this slip!


SAML responses with a InResponseTo attribute not rejected when requestId not passed to validate

The InResponseTo validation done here: https://github.com/onelogin/python-saml/blob/master/src/onelogin/saml2/response.py#L138-L143 does not fail if in_response_to is not None and request_id is None.
Can an option be added for stricter checking, similar to how this issue was resolved? https://github.com/onelogin/java-saml/issues/62
Specifically the functionality added in this commit https://github.com/miszobi/java-saml/commit/61904ad4f62e021f5ee79d8d8489c38e77acf5cb should be replicated in this library ("reject Responses with a InResponseTo if null was provided as an argument to validate (enabled by Saml2Settings.rejectUnsolicitedResponsesWithInResponseTo").

I think we can apply similar solution here at python-saml
to accelerate the process, are you able to provide a PR?

Here is: https://github.com/onelogin/python-saml/commit/4081893698abc46c41e2a5c4b91bcdd37d401a19


Reference the AWS CDK root stack created from GraphQLTransform

Is this feature request related to a new or existing Amplify category?
api
Is this related to another service?
No response
Describe the feature you'd like to request
I am currently using AWS CDK to manage the infrastructure and only make use of the GraphQL transformers provided by AWS Amplify by directly building and invoking the GraphQLTransform class. With the new version of the transformers I noticed that under the hood it uses AWS CDK so, instead of first writing the deployment resources as Cloudformation templates and then having to import that, I would like to reference the stack created by GraphQLTransform#transform function. It seems to be possible, as the result of this function has the type DeploymentResources which includes a rootStack field. The only issue I see is that the root stack's scope is a new CDK App, which is created here:
https://github.com/aws-amplify/amplify-cli/blob/master/packages/amplify-graphql-transformer-core/src/transformation/transform.ts#L144
  public transform(schema: string): DeploymentResources {
    this.seenTransformations = {};
    const parsedDocument = parse(schema);
    this.app = new App();
    const context = new TransformerContext(
      this.app,
      ...

Instead of a new app being created during the transformation process I would like to have the option to pass my own scope so that the Stack will be part of the AWS CDK app my project manages.
Describe the solution you'd like
My suggestion would be to extend the GraphQLTransformOptions type to receive an optional scope field such as this:
export interface GraphQLTransformOptions {
  ...
  scope?: cdk.Construct
}

Note: I would also consider changing the type from cdk.App to cdk.Construct in order to be able to include the stack within another stack's scope or the top level app.
If the scope param was not provided, then it will work the same way as now and new instance of cdk.App will be assigned to it.
Let me know please if you think this approach looks right to you and I will be available to perform these changes myself. Thanks for your help!
Describe alternatives you've considered
Another option is to pass the scope as an additional parameter to the method GraphQLTransform#transform method, but I think it makes more sense to be passed to the constructor, unless there are some implications I am not aware of when calling multiple time the transform function.
Additional context
No response
Is this something that you'd be interested in working on?

[X] 👋 I may be able to implement this feature request
[ ] ⚠ This feature might incur a breaking change

Closing this as done, as you're able to create a new Amplify API purely via CDK now. See "AWS CDK" tab under https://docs.amplify.aws/react/build-a-backend/graphqlapi/set-up-graphql-api/


Add option to load a local file in explorer method

Very similar to this functionality in CAT

same as #235


ERROR: dependency ‘cBioPortalData’ is not available for package ‘imogene’

Hi,
I received this error during installation
ERROR: dependency ‘cBioPortalData’ is not available for package ‘imogene’
Please let me know.
Thanks,
Praveen

Closing since I think we now depend on curatedTCGAData


Bug with default entities selection when variable not calculated for certain entity

Update 20190521
Possible fix in SumVariables(): added 5 lines that, when no entities selected, get entities for which all given variables exists. Seems to work.
This fix needs to be applied to other methods as well that have the same problem! Similar can be used for others if we construct a separate loop for variables at start. This entity selection needs to be wrapped as separate static method and apply it to all.
Init post
Default entity selection
if entities == None:
entities = list(np.unique(self.df.columns.get_level_values(1).values))
is not working (at least) for following methods:
SumVariables()
DetrendVariables()
MRADecomposition()
SumVariables()
ReduceVariableDimension()
Example case: MRADecomposition() is performed on entity DEU:
variables = ['Credit_def_ld1','ResidentialPrices_ld1','StockPrices_def_ld1']
do.MRADecomposition(variables,entities=['DEU'],levels = 6,expanding=False)
Later we try to perform SumVariables() on default entities:
variables = {'L45':['StockPrices_def_ld1_wl4','StockPrices_def_ld1_wl5','Credit_def_ld1_wl4','Credit_def_ld1_wl5','ResidentialPrices_ld1_wl4','ResidentialPrices_ld1_wl5']}
do.SumVariables(variables)
For entities that were not included in MRADecomposition, SumVariables() results in variable with values 0 throughtout, although it should throw an error.

Along #4 and ver 0.1.1 this is done.


Proposal: Introduce versioning and version alignment

We know that the relation interface is at the moment lacking capabilities in terms of:

TLS
Authentication

The capabilities above are virtually certain to require either side of the relation to perform significant different logic than they do now, so current providers and requesters, even if they do not fail outright when confronted with, say, and endpoint requiring TLS, they will not be able to set up their workloads to interoperate with that endpoint.
IMO, we should add an optional property, called version to the root objects for provider and consumer, to represent the version of the relation interface. If not set, the version is assumed to be 0, and should correspond in terms of capabilities with the LIBAPI version 0 of the prometheus_remote_write charm library.
Future versions of the relation schema will have different structures depending on the version. Provider and requester should always post to the relation interface the highest version they are capable off, and when receiving from the other side a version that they also support, "downgrade" the relation data they expose accordingly.
If one role in the relation receives relation data with a version it does not understand, it must do nothing in response. That charm may decide to go into BlockedState, to signal the incompatibility with to the Juju admin. (WaitingState seems not semantically correct because there is no guarantee that a common version will be agreed upon.) If the other side downgrades its relation data to a common version, the charm will then recover from the BlockedState.

We did implement simple versioning for the specs themselves, however not at runtime. Closing this as we're not likely to get further for the time being. This could very well be a future enhancement, so I'll label it accordingly.


docs(chips): make separatorKeysCodes readonly

Make separatorKeysCodes readonly because it isn't changed after component is intialized.

@jhuang314 Could you please rebase? Thanks!


A thank you (and have you considered using JSDB?)

Hey Ben, just stumbled on this today and I wanted to both say thank-you for working on a Small Web-style single-person implementation and also to ask if you’ve heard of JSDB (JavaScript Database):
https://codeberg.org/small-tech/jsdb
If not, take a look (it might help with the persistence bits. (Although it is also in-memory and I’d be interested in seeing what sort of sharding you come up for that.)
Best of luck with this. Looking forward to seeing how it evolves :)

Awesome, thanks for the pointer. I’ll take a look. and thanks for the kind words!
Part of the important part for me is that the data on disk is easy to look at and manage - like I can delete old posts by just deleting folders. Does this package write files in a similar way?

Part of the important part for me is that the data on disk is easy to look at and manage - like I can delete old posts by just deleting folders.

I’m a big fan of this too :)
JSDB writes to append-only JavaScript logs so it’s not as great for the design properties you mentioned.
Interestingly, with Heartbeat (about ~24m in at https://www.youtube.com/watch?v=kbfvEBfHO-M; source: https://source.small-tech.org/project/heartbeat-node, https://source.small-tech.org/project/heartbeat-cocoa), I was writing everything to the file system for the same reasons as you and basically using Syncthing to replicate changes to all peers (and using a LevelDB database if I remember correctly to weave all that into timelines). There are lots of advantages to using the file system. (It might be interesting to see whether peer-to-peer sync might be an interesting extension for Shuttlecraft.)

Thanks for all the pointers. I appreciate it.
My personal instance now has 11,000 posts in the index and ... so far is doing ok performance wise. But in a few months it will easily hit 100,000 posts.
In particular I think a JSDB that is quick to query would be very useful for the index itself, which just needs to know metadata and not full content of the posts.

Scenarios are things like:

get most recent posts
get most recent posts by a user
traverse a thread

Take a look at https://codeberg.org/small-tech/jsdb#javascript-query-language-jsql
Basically, it’s all in-memory so it should be more than fast enough. And hopefully the interface is fluent (and if you do try it out and run into any issues, please do let me know) :)

Ah, looks great!


Pure static classes to namespaces

Commit Message: Envoy prefers namespaces to static classes.
Additional Description: This is a followup from comments in https://github.com/envoyproxy/envoy/pull/17728
Risk Level: Very Low
Testing: Existing

/retest

"Envoy prefers namespaces to static classes." --> citation needed :)
I can't find any reference to that in https://github.com/envoyproxy/envoy/blob/main/STYLE.md -- and I thought it was plenty common to use statics in a class in Envoy.

"Envoy prefers namespaces to static classes." --> citation needed :)

Oh... well I got a comment on the last PR that I should use a namespace instead. I don't personally have a preference.
https://github.com/envoyproxy/envoy/pull/17728#discussion_r689894346

Heh -- I personally prefer static class methods for various reasons, but don't feel that strongly. I'll defer to @dmitri-d :)

Haha, I don't actually feel strongly about this either, I thought that was the preferred way for grouping of static functions in Envoy. Lgtm.

I'm OK merging this but IMO this is not at all preferred by Envoy style, for the record. I think Envoy is OK with either one and there are a ton of existing uses of classes with static members, and there are some benefits to that approach.


chore(tile-group): migrate tile-group to scss

Summary
Moves TileGroup component from styled-components to scss
Acceptance Test (how to verify the PR)
Navigate to TileCatalog and verify that the styling is still correct.

:tada: This PR is included in version 2.59.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implemented isReadOnly prop for RangeSlider component

This PR implements isReadOnly prop to the RangeSlider.
-This prop ensures that the RangeSlider cannot be used to change the value in readOnly mode.
This feature can be really useful when implementing the RangeSlider and ensuring that only certain users can edit the value on the RangeSlider.

:tada: This PR is included in version 1.26.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add automated tests for Windows

Fixes #49

https://app.travis-ci.com/github/IBM/javacore-analyser/jobs/628483031:
The language 'python' is currently unsupported on the Windows Build Environment.
We are unable to test on Windows with Travis right now.


[SIP] Step/Funnel Step Visualization (American Express)

SIP: Add Step Visualization (American Express)
SIP issue #7574
Choose one

[x] Enhancement (new features, refinement)
[x] Refactor
[x] Add tests
[x] Build / Development Environment
[x] Documentation

SUMMARY
Adding Step Visualization to Apache Superset
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

STEPS
Using the 'dist_bar' Viz_type the user will be able to add many steps. Each step has is simply a bar graph step with a specific query. Relationships are made between each step by printing the delta for story telling effect.

ABSOLUTE FILTER
Absolute Filter can be added on a slice as a whole for repetitive filters. For example if you are only interested in telling a story on domestic sales. You can apply the domestic_sales filter once in absolute filter instead of on every step.

TEST PLAN
Run additional tests on the issue
ADDITIONAL INFORMATION

[x] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[x] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

Can anyone comment on what would need to be added to successfully pass these build tests?


Dialog forms don't work properly and trigger a page reload in shadow DOM

In Firefox and Safari, inside a shadow DOM, submitting (via a submit button) a form with method set to "dialog" (inside a dialog element) triggers a page reload instead of closing the dialog with the proper returnValue.

This seems to happen because the submit event is handled globally at document level. It works well in regular DOM, as the event bubbles up. In shadow DOM, the event still bubbles up, but it doesn't propagate across the shadow DOM boundary because the composed property of the submit event is false.

Thanks for the report. I'll solve this by setting composed and handling it
globally.
On Tue, 21 Apr 2020 at 21:17, Adrian Nita<EMAIL_ADDRESS>wrote:

This seems to happen because the submit event is handled globally at
document level. It works well in regular DOM, as the event bubbles up. In
shadow DOM, the event still bubbles up, but it doesn't propagate across the
shadow DOM boundary because the composed property of the submit event is
false.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/dialog-polyfill/issues/195#issuecomment-617115077,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5DEDYOYE5FNZHGDCDP7LRNV6C3ANCNFSM4MNGX3AA
.

But can you override the composed flag of the native submit event?

I've fixed this in 0.5.4.


wg-components April 2021 Office Hours

Meeting date/time (UTC)
04/20/2021 - 6PM UTC, 11AM PST
Instructions for joining the meeting
Join https://meet.google.com/spd-oowj-ndo, and you will be let in
Agenda
GitHub Projects
Project updates

Thank you for the call. We will recap the list/template issue with live code and link to this issue.

@micajuine-ho Rather than opening another issue, i'll include two working examples from previously posted issues.
v4-40 illustrates a single hierarchical JSON list, a single template and CSS to maintain inline paragraph control:
https://afdsi.com/samouri-amp/v4-40/
v6-40 illustrates two lists, two templates and CSS that fails to maintain inline paragraph control:
https://afdsi.com/samouri-amp/v6-40/
either list or template injects a line break that prohibits the ability to have atomic lists (i.e. definition of a single word in multiple natural languages) and use more than one atomic list in a paragraph.
said another way: we cannot implement a tooltip from a library of words - each coded in a list - in a paragraph.
our request is to replace the list/template block level control with inline control.

/cc @alanorozco

@jaygray0919 The templates in the <amp-list>s shown  are very large, could you please:

isolate a single paragraph with a single tooltip, so I can read the code
show a screenshot pointing at the linebreak you don't want
show an example/screenshot of what you want


SampleApiConsumers About

How exactly is the logic here processed? Could you tell us a little bit about it?

Hello, I guess nobody is involved here, my question is, do you have an example to post data from outside please can we help you

Hello, I guess nobody is involved here, my question is, do you have an example to post data from outside please can we help you @thiennn

Hi @thiennn Please add us an example of how data is posted and put.

@fetullahyldz I think you can use Swagger to try post data.
Then you can use HttpClient to RequestClientCredentialsTokenAsync to get token and then use token to PostAsync with FormUrlEncodedContent.


New NamingStrategy for Querydsl SQL

A new NamingStrategy based on the default naming strategy with improved FK name generation.
The naming on db level would be fk__
e.g.
tables user and company
user has fk_company_users foreign key to referencing company via company_id

generated fk names in meta model are
class User { company: Fk }
class Company { users: InvFK }

other examples
Order / Row : fk_order_rows
Category / Events : fk_category_events

The risk of name clashes is bigger with this kind of namingstrategy, but the constraint names are intuitive and the resulting fk / invFk names in the model as well.

Released in 2.3.0


restore function doesn't work in REPL

Code to reproduce the issue:
const foo = createEvent()
const bar = restore(foo, null)

Expected behavior:
No errors
Actual behavior:
Try Effector crashes
Versions of packages used: master
https://effector.now.sh/try/
To reset saved code remove it from localStorage

IssueHunt Summary

 laiff has been rewarded.
Backers (Total: $40.00)

 issuehunt ($40.00)

Submitted pull Requests

#151 #149 Fix crash in try environment while use restore

Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

IssueHunt has been backed by the following sponsors. Become a sponsor

solved in https://github.com/zerobias/effector/pull/151


Openbox and Tint2 and Qt5 themes are not consistent, or dynamically linked

Due to the nature of how SYN-OS has been put together it allows a robust fully interoperable system build from the ground up in zsh and bash.
However the very fact there is no desktop environment or display manager, it means we get a limited range of ways to connect these different tools so changing a simple detail like a theme requires three custom themes to be applied manually each.

~/.config/tint2
This contains our themes and settings for the panel.
~/.config/openbox
This contains the Openbox configuration.
It would be fine if we simply had to change both parts of theme manually, but then qt5ctl and the CSS is an additional layer of colours which further justifies the need for a desktop environment.
For the pursuit, we will find a way of dynamically linking this technology thereby effectively making our own desktop environment from these tools.

Not going to happen. We are going to switch up the desktop environment.


Faraday::SSLError: SSL_connect SYSCALL returned=5 ... on MacOS

Hi, I'm using the zendesk API to bring all the tickets from my domain, and in the middle of the script, it breaks and return this Faraday error: Faraday::SSLError: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A (if you guys need, i can send the full stack error). I read something on faraday gem page, and, according with the zendesk gem wiki, i set some params on my client config
      config.client_options = {
        :ssl => false,
        :request => {
          :timeout => 10000000,
          :open_timeout => 2000000
        }
      }

but that didn't solve my problem... I'm trying to get all the tickets from my zendesk and save all the comments and users. Can i set the timeout or ssl verification in some other way? Anyone had the same issue? Can you guys help me? PLS!

@maxforasteiro try
config.client_options = {:ssl => {:verify => false}}


Import of module causes buildlog file to be generated

Bug Report

General Troubleshooting steps

[x] Verified running latest release of dbatools?
[x] Verified errors are not related to permissions?
[x] Can duplicate in new/fresh PowerShell.exe session on new server?

Version Information

Operating System (Name|Version): Window Server 2012 R2
PowerShell Version: ```Name                           Value

PSVersion                      4.0
WSManStackVersion              3.0
SerializationVersion           <IP_ADDRESS>
CLRVersion                     4.0.30319.42000
BuildVersion                   6.3.9600.17400
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion      2.2```

SQL Server (Edition|Version): N/A

Steps to Reproduce

[ ] Attach any screenshots (if possible/allowed)
[ ] Attach logs generated by dbatools (Get-DbatoolsLog)
[ ] Attach output from PowerShell console (if possible/allowed)
Download module via httsp://dbatools.io/zip and then import and it will sit for a few seconds. I know this should be the portion that is building the DLL file, and as soon as it is done I can check the root folder where I expanded the zip file. An msbuild.log file is generated.

I can't provide the full file because it is two large for me to pull from client environments. I'll have to get a new server built in my lab and can provide the full output if required.
Problem to solve

Main one is why the log is generated as it seems to indicate errors.

@wsmelton : with all the changes done to our "build system" I feel we can close this now, I can't repro


Warm runtime

R: @jeffposnick @addyosmani
This delightful little wonder introduces caching of un-revisioned caching. To make use of a big chunk of the code from the "revisioned" caching I had to move quite a few things around but the core logic is the same.
@jeffposnick I tried to move to the RequestWrapper, but due to caching being done async from the function being completed it's cause issues with my tests.

This delightful little wonder introduces caching of un-revisioned caching

Caching of unrevisioned assets? :)

Happy to chat off-thread about what you're running into that prevents the use of RequestWrapper here.

@jeffposnick @addyosmani All of the raised issues have been fixed, could you take another look.

LGTM. I don't know if @addyosmani has any more feedback, but otherwise, feel free to merge.
We should still chat about what changes could be made to RequestWrapper to get it usable here, but that doesn't need to block this PR.


Guard death test by conditional compile.

Current sample program does death tests always. So, the test will fail on the release build because assert() doesn't work.
https://github.com/suikan4github/template_application/blob/d3639b5b67a4ff6feeb7dde634e8a9e21f8de29f/test/test_calc_death.cpp#L9-L10
To avoid it, add conditional compile guard to the death test.
#ifndef NDEBUG
    // We test only when assert() works.
    ASSERT_DEATH(...);
#endif

Merged to develop. Ready to release.


Error during cordova platform install android 8.1.0

Hello,
after installing the latest versione of this NFC plugin, if I launch:
cordova platform add<EMAIL_ADDRESS>the installation process is completed and everything works ok. Instead if I launch:
cordova platform add<EMAIL_ADDRESS>or android@latest
I have this error (C:\L\intelliclima-app\ is my Cordova app):
Failed to install 'phonegap-nfc': Error: Unable to graft xml at selector "/manifest/uses-sdk" from "C:\L\intelliclima-app\platforms\android\app\src\main\AndroidManifest.xml" during config install
at ConfigFile_graft_child [as graft_child] (C:\L\intelliclima-app\node_modules\cordova-common\src\ConfigChanges\ConfigFile.js:122:19)
at PlatformMunger_apply_file_munge [as apply_file_munge] (C:\L\intelliclima-app\node_modules\cordova-common\src\ConfigChanges\ConfigChanges.js:81:34)
at munge_helper (C:\L\intelliclima-app\node_modules\cordova-common\src\ConfigChanges\ConfigChanges.js:252:14)
at PlatformMunger.add_plugin_changes (C:\L\intelliclima-app\node_modules\cordova-common\src\ConfigChanges\ConfigChanges.js:159:12)
at C:\L\intelliclima-app\node_modules\cordova-common\src\PluginManager.js:123:29
at _fulfilled (C:\L\intelliclima-app\node_modules\q\q.js:854:54)
at C:\L\intelliclima-app\node_modules\q\q.js:883:30
at Promise.promise.promiseDispatch (C:\L\intelliclima-app\node_modules\q\q.js:816:13)
at C:\L\intelliclima-app\node_modules\q\q.js:877:14
at runSingle (C:\L\intelliclima-app\node_modules\q\q.js:137:13)
Unable to graft xml at selector "/manifest/uses-sdk" from "C:\L\intelliclima-app\platforms\android\app\src\main\AndroidManifest.xml" during config install
Any idea?

I have the same problem. Did you find a solution?

Same here! Need to build twice for it to go away

I think this is fixed now by some other updates. I've been building with<EMAIL_ADDRESS>with Cordova CLI 9.0.0 on macOS all week without problems. Re-open this issue or create a new one if it's still a problem.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.15 to before v5.15.8",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8d5f7954b7c8de54902a8beda141064a7e2e6ee0",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=973a0373e88cc19129bd6ef0ec193040535397d9"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "8d5f7954b7c8de54902a8beda141064a7e2e6ee0",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "973a0373e88cc19129bd6ef0ec193040535397d9",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net: dsa: felix: Fix memory leak in felix_setup_mmio_filtering\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.8 by commit 973a0373e88cc19129bd6ef0ec193040535397d9, it was introduced in version v5.15 by commit 8d5f7954b7c8de54902a8beda141064a7e2e6ee0. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002593


Add "sealed" key word to mark some public/protected methods not be overriden

From https://github.com/Microsoft/TypeScript/issues/1524, I see that the default method are all "virtual", but sometimes I don't wanna some public method to be overidden. Would you invent a mechasim to force the users that they cannot override a public method (with the key word, something like "sealed")?
Thanks!

Please add a final or sealed accessibility modifier. To be to public as private is to protected.

Overridable
Non-overridable

Internal
protected
private

All
public
final

Has this fallen into oblivion?
This is an essential features for the sugars design of an public extensible API!


net/wol weird port behaviour

Description
Non exclusively tested reconstruction. WOL doesn't work.
When I use the GUI to wake a single host, I get an OK from the GUI.
But when I listen in via Wireshark it shows:
67583	3756.024125	<IP_ADDRESS>	<IP_ADDRESS>	? KNXnet/IP	144	? Unknown Service Family

It turns out that this happens if the default port 40000 is used, but not if for example 41000 or 40001 is used.
If I change
https://github.com/opnsense/plugins/blob/master/net/wol/src/opnsense/service/conf/actions.d/actions_wol.conf
to...
[wake]
command:/usr/local/bin/wol -p 40001 -i
parameters: %s %s
type:script

(just the -p part)
...then Wireshark tells me that this is a sane WOL packet:
67950	3785.004252	<IP_ADDRESS>	<IP_ADDRESS>	WOL	144	MagicPacket for Giga-Byt_ad:7c:35 (e0:d5:5e:ad:7c:35)

Environment

10G "INTEL X520-SR1" Adapter
sent to a ethernet/broadcast device target of type VLAN
using Ubiquity Switches to produce untagged LAN using that VLANID
listened on that untagged LAN

and

OPNsense 19.7.7-amd64
FreeBSD 11.2-RELEASE-p16-HBSD
os-wol 2.2

I don't understand the basics of WOL, but I'm willing to test more if you advise me how to.

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


What is this for

What is this for
Originally posted by @ghost in https://github.com/octocat/Spoon-Knife/issues/31284#issuecomment-1799946029

Sorry, I'm not sure what this is for but it doesn't seem to be an issue with WinUI, so I'm going to close it.


Enforce lowercase variable naming convention.

This PR enforces the lowercase variable naming convention: all variables or properties start with a lowercase letter.

Is there anything blocking for this PR @CoolGoose?

I need some time to rebase thus @CoolGoose

Conflicts are fixed @CoolGoose

Ready to be merged @CoolGoose
As other PR merges would potentially create new conflicts.


bug: file-selector popup with telescope provider doesn't list any files in projects that don't use git

Describe the bug
This happens when I

open the Avante chat
focus the files pane
press @ to open the "(Avante) Add a file>" popup
no files are listed in the popup

To reproduce
Install avante.nvim and open neovim in any project that isn't a git repository.
Expected behavior
Project files are displayed in the popup.
Installation method
Use lazy.nvim:
{
  "yetone/avante.nvim",
  event = "VeryLazy",
  lazy = false,
  version = false, -- set this if you want to always pull the latest change
  opts = {
      file_selector = {
          provider = "telescope",
      },
  },
  -- if you want to build from source then do `make BUILD_FROM_SOURCE=true`
  build = "make",
  -- build = "powershell -ExecutionPolicy Bypass -File Build.ps1 -BuildFromSource false" -- for windows
  dependencies = {
    "nvim-treesitter/nvim-treesitter",
    "stevearc/dressing.nvim",
    "nvim-lua/plenary.nvim",
    "MunifTanjim/nui.nvim",
  },
}

Environment
NVIM v0.10.2
MacOS 14.7.2
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    -- add any other plugins here
  },
})

i think it will be fixed by #954


Fix: Documentation

Fix conflict

Codecov Report

Merging #246 (298b63a) into master (80ed5e0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #246   +/-   ##
=========================================
  Coverage     38.44%   38.44%
  Complexity      556      556
=========================================
  Files           178      178
  Lines          3283     3283
  Branches        389      389
=========================================
  Hits           1262     1262
  Misses         1883     1883
  Partials        138      138

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 80ed5e0...298b63a. Read the comment docs.

I have fixed all the bugs that Elton found. Do tell if there are more to be modified.


fix(date): dates should be dates

:tada: This PR is included in version 1.7.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: