Include with JoinType.LeftOuter issues

The only test for this functionality returns a single Item:
https://github.com/JasperFx/marten/blob/master/src/Marten.Testing/Services/Includes/end_to_end_query_with_include_Tests.cs#L153
I'm having issues getting Include with JoinType.LeftOuter to work with an Include the returns a List or Dictionary of results. The primary document is not returned.

@jeremydmiller we did some investigation using a logging interceptor and the generated SQL still says INNER JOIN when you try to Include with the JoinType.LeftOuter for a List or Dictionary. Hopefully that helps make this a quick fix.

I've got a failing test that confirms the issue. First test passes, second test fails.
https://github.com/jeffdoolittle/Marten/commit/3c5caa93cae5ec27f9271ad4fe256d5e3c491676

fixed: https://github.com/JasperFx/marten/pull/507


The app crashed after delete my account

Expected Behavior
Sign-up / Sign-in window should appears to continue using the app
Actual Behavior
Right after start an app the following error pops-up:
Application Error
Failed to render. Please report to [our Github Issues](https://github.com/Kong/insomnia/issues)

Network connectivity issue: Failed to load Organizations. Cannot read properties of undefined (reading 'find')
Try to reload the app
Error: Network connectivity issue: Failed to load Organizations.
Cannot read properties of undefined (reading 'find') at Module.Il1 [as indexLoader]
(file:///C:/Users/Katana/AppData/Local/insomnia/app-8.0.0/resources/app.asar/index-334620de.js:1255:3095) at async d8
(file:///C:/Users/Katana/AppData/Local/insomnia/app-8.0.0/resources/app.asar/index-334620de.js:31:3691) at async Promise.all (index 2) at async ce
(file:///C:/Users/Katana/AppData/Local/insomnia/app-8.0.0/resources/app.asar/index-334620de.js:30:21935) at async qe
(file:///C:/Users/Katana/AppData/Local/insomnia/app-8.0.0/resources/app.asar/index-334620de.js:30:16866) at async we
(file:///C:/Users/Katana/AppData/Local/insomnia/app-8.0.0/resources/app.asar/index-334620de.js:30:15042)

Reproduction Steps

Download last 8.0 installer Insomnia.Core-8.0.0.exe
Install / run the app
Successfully sign-up / sign-in using Google account (set passphrase etc.)
Go to account settings page
Hit Delete my account button and confirm
Return to the app - an above error appears

From this point the app crashed and doesen't work at all.
There is no way to log-in using another account or somehow force the app to work.
The following steps was sttempted to try solve the problem - nothing helped me:

Hitting Try to reload the app button below the error message
End task through Windows Task Manager and run the app again
Uninstall the app / install again 8.0

I am only managed to solve this by downgrading to another version, in my case Insomnia 2022.6.0
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
8.0.0
What operating system are you using?
Windows
Operating System Version
Windows 11 Pro Version 22H2 OS build 22621.2283
Installation method
Download from insomnia.rest
Last Known Working Insomnia version
No response

This issue will be fixed in 8.1 today or tomorrow the latest.

Fixed as 8.1 is now out.


Add some info about vcenter and norm params

I added two plots showing how vcenter and norm params (added in https://github.com/theislab/scanpy/pull/1551) are used. There are also a few small fixes like replace louvain with clusters and fix cluster cell type mapping which was designed for 12 clusters although we have 9 now.

What do you think about having a separate document all about how colors are handled in the plotting API? This could start with just the examples you have here for continuous colors. It would also have categorical, and null value handling added, but that would be separate. I'm thinking of something a bit more topical, kind of like this: https://seaborn.pydata.org/tutorial/color_palettes.html

@ivirshup Sounds good, I wanna merge the bugfixes in the plotting tutorial but I moved 4 new plots about vcenter/norm to a new tutorial. Do you mind adding the other coloring tricks you have in mind to the new tutorial and merge it @ivirshup ?

I'm happy to merge the bug fixes, but what do you think about putting the docs for coloring as part of the main documentation?
That way the plots will stay up to date and will be easier to modify/ add to (since we don't have to recommit the entire notebook with embedded plots for any change).

Also sounds good. Shall I make a new PR to keep the git tree a little cleaner then? Or just remove the new notebook with a commit?

I don't have permission to merge, so feel free to merge it whenever.


[bug] The window size is incorrect under multiple monitors

Describe the bug
I now have two monitors, the primary screen is 1920x1080 with a dpi of 1.25 and the secondary screen is 1024x768 with a dpi of 1. Windows multi-window mode is set to extended.
I registered a global shortcut in my application to create a window at the mouse location, and set a fixed window size value using .inner_size when creating the window, which, if I understand correctly, this should be the logical size, so no matter which screen I create the window on, they should look the same size, but this is not the case:
When I create a window on the secondary screen, the size of the window is larger, but when I create a window on the primary screen and drag it to the secondary screen, the window size is correct, even when I create a window on the secondary screen, Drag it to the main screen and drag it back, the size of the window will become correct.
Reproduction
No response
Expected behavior
No response
Platform and versions
Environment
  › OS: Windows 10.0.22621 X64
  › Webview2: 112.0.1722.64
  › MSVC:
  › Node.js: 19.5.0
  › npm: 9.3.1
  › pnpm: 8.4.0
  › yarn: Not installed!
  › rustup: 1.25.2
  › rustc: 1.67.0
  › cargo: 1.67.0
  › Rust toolchain: stable-x86_64-pc-windows-gnu

Packages
  › @tauri-apps/cli [NPM]: 1.2.3

Stack trace
No response
Additional context
https://user-images.githubusercontent.com/59004461/235893229-a5af8661-f46a-47e9-b1de-b0be0576d96d.mp4

Could you please provide a minimal reproduction example I can use to debug this?

I can give you a reproduction process:

Prepare two monitors with different dpi connected in extended mode.
Create an application using create-tauri-app.
Create a new window in the rust code, and make it appear on the second monitor by setting the position of the window (setting a value larger than the size of the main monitor).
You will find that the window created this way is the wrong size on the second monitor, but if you create the window on the main monitor and then drag it to the second monitor, the window will be the correct size.

This issue might be similar to mine. I've found that when creating a main window on a screen with a 3840x2160 resolution and 1.5 scaling, and dragging this window into another window with the same resolution but 2.0 scaling, the physical resolution is altered twice. Similarly, this also happens when dragging it back to the original window.
Window resized to PhysicalSize { width: 1801, height: 1140 }
Scale factor changed to 2x and new inner size PhysicalSize { width: 2401, height: 1520 }
Window resized to PhysicalSize { width: 2401, height: 1520 }
Window resized to PhysicalSize { width: 1794, height: 1122 }
Scale factor changed to 1.5x and new inner size PhysicalSize { width: 1346, height: 842 }
Window resized to PhysicalSize { width: 1346, height: 842 }
Window resized to PhysicalSize { width: 1802, height: 1141 }
Scale factor changed to 2x and new inner size PhysicalSize { width: 2403, height: 1521 }
Window resized to PhysicalSize { width: 2403, height: 1521 }

When the window is first dragged into the 2.0 scaling screen, the initial resize should be to the correct size, but after the resize is completed, a ScaleFactorChanged event is triggered again, followed by another resize, which results in the window being too large.
Is there a temporary workaround for this issue?

I found that the condition for this issue to reoccur is that it only happens after turning off the "Show window contents while dragging" option in the performance settings of the Windows system.

I also encountered this problem and I couldn't accurately use setPosition on different dip screens to specify the display position on different screens.


Add tests opendp polars

Coverage report
 Click to see where and how coverage changed
FileStatementsMissingCoverageCoverage(new stmts)Lines missing

  server/lomas_server/tests
  test_api.py

  test_api_diffprivlib.py

  test_api_opendp_polars.py

  test_api_root.py
79
  test_mongodb_admin.py

  server/lomas_server/utils
  example_inputs.py

Project Total

This report was generated by python-coverage-comment-action


Update README.md

On Tue, Dec 20, 2022 at 9:04 AM Vladislav Kovalev @.***>
wrote:

Closed #27 https://github.com/BEPb/BEPb/pull/27.
—
Reply to this email directly, view it on GitHub
https://github.com/BEPb/BEPb/pull/27#event-8078735516, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3ELPCQCZYMSCQJ4WQI3JTDWOG4FHANCNFSM6AAAAAATERHAOM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Ok


Pulsar Search - QFT + Grover

Can we use QFT + Grover (amplitude amplification) to get a binary classifier for the pulsar search ?

probably no and QML approaches for pulsar detection have already been published


Deep linking search filters with URL

@lukehollis Can you provide more details regarding the issue ?

We will need to make search filters affect some kind of parameters in the URL that may be parsed if present on page load.  These parameters will update the filters selected in the search tools, kind of like the way this link https://devart.withgoogle.com/#/?q=javascript selects "Javascript" as a search filter in the search tools on that website.
In order to build this, we will need to first build the search tools.

If I'm not wrong this issue is directly related to the design of the API rather than frontend itself. Right ?

This is an issue related to the way the frontend application will build a query to be put in place of this one (which returns all works--only "{}"--the search filters need to be added here by our search tools) on the WorksList view: https://github.com/cltk/cltk_frontend/blob/master/client/views/works/WorksList.jsx#L11
This does not access the cltk_api Flask application, but rather leverages Meteor's internal websockets connection.

Closed with https://github.com/cltk/cltk_frontend/commit/5b7e9da0b866675d39f60d572504fe91eaf88b1f


wafv2.py Missing Valid Transformation Types in VALID_TRANSFORMATION_TYPES List

The wafv2.py module is missing new TextTransformation values announced here (https://aws.amazon.com/about-aws/whats-new/2021/06/aws-waf-adds-15-new-text-transformations/) and documented as supported by CloudFormation here (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-wafv2-webacl-texttransformation.html).
Transformations currently allowed:  CMD_LINE | COMPRESS_WHITE_SPACE | HTML_ENTITY_DECODE | LOWERCASE | NONE | URL_DECODE
Full set of transformations that are allowed by CloudFormation:  BASE64_DECODE | BASE64_DECODE_EXT | CMD_LINE | COMPRESS_WHITE_SPACE | CSS_DECODE | ESCAPE_SEQ_DECODE | HEX_DECODE | HTML_ENTITY_DECODE | JS_DECODE | LOWERCASE | MD5 | NONE | NORMALIZE_PATH | NORMALIZE_PATH_WIN | REMOVE_NULLS | REPLACE_COMMENTS | REPLACE_NULLS | SQL_HEX_DECODE | URL_DECODE | URL_DECODE_UNI | UTF8_TO_UNICODE

Thanks for this issue. I'll include these changes in an upcoming update I have pending for WAFv2. I'm going to be pulling out the validators into a separate file to allow for better auto-generation of the core files.

Please review PR #1996 which includes these changes.

These were included in the Release 3.2.0.