Staging merger to prtest

Version(s) of document impacted

[ ] Impacts 6.next document
[ ] Impacts 6 document
[ ] Impacts 5.1 document
[ ] Impacts 5.0 document
[ ] Impacts 4.0 document
[ ] Impacts 3.0 document

Reason(s) for not updating all version of documents

[ ] The documented feature was introduced in version (list version here) of PowerShell
[ ] This issue only shows up in version (list version(s) here) of the document
[ ] This PR partially fixes the issue, and issue # tracks the remaining work

Docs Build status updates of commit 0f98ba4:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 0f98ba4:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

reference/3.0/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Data_Sections.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_For.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Foreach.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Functions.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Switch.md
:warning:Warning
View (powershell-3.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Data_Sections.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_For.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Foreach.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Functions.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Switch.md
:warning:Warning
View (powershell-4.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Data_Sections.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_For.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Foreach.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Functions.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Switch.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.1/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md
:warning:Warning
View (powershell-5.1)
Details

reference/5.1/Microsoft.PowerShell.Core/About/about_Data_Sections.md
:warning:Warning
View (powershell-5.1)
Details

reference/5.1/Microsoft.PowerShell.Core/About/about_For.md
:warning:Warning
View (powershell-5.1)
Details

reference/5.1/Microsoft.PowerShell.Core/About/about_Foreach.md
:warning:Warning
View (powershell-5.1)
Details

reference/5.1/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md
:warning:Warning
View (powershell-5.1)
Details

reference/5.1/Microsoft.PowerShell.Core/About/about_Functions.md
:warning:Warning
View (powershell-5.1)
Details

reference/5.1/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md
:warning:Warning
View (powershell-5.1)
Details

reference/5.1/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md
:warning:Warning
View (powershell-5.1)
Details

reference/5.1/Microsoft.PowerShell.Core/About/about_Switch.md
:warning:Warning
View (powershell-5.1)
Details

reference/6/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md
:warning:Warning
View (powershell-6)
Details

reference/6/Microsoft.PowerShell.Core/About/about_Data_Sections.md
:warning:Warning
View (powershell-6)
Details

reference/6/Microsoft.PowerShell.Core/About/about_For.md
:warning:Warning
View (powershell-6)
Details

reference/6/Microsoft.PowerShell.Core/About/about_Foreach.md
:warning:Warning
View (powershell-6)
Details

reference/6/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md
:warning:Warning
View (powershell-6)
Details

reference/6/Microsoft.PowerShell.Core/About/about_Functions.md
:warning:Warning
View (powershell-6)
Details

reference/6/Microsoft.PowerShell.Core/About/about_Preference_Variables.md
:warning:Warning
View (powershell-6)
Details

reference/6/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md
:warning:Warning
View (powershell-6)
Details

reference/6/Microsoft.PowerShell.Core/About/about_Switch.md
:warning:Warning
View (powershell-6)
Details

reference/6/PSDesiredStateConfiguration/About/about_Classes_and_DSC.md
:warning:Warning
View (powershell-6)
Details

.github/TestingPullRequest.md
:white_check_mark:Succeeded

.openpublishing.publish.config.json
:white_check_mark:Succeeded

ci.yml
:white_check_mark:Succeeded

daily.yml
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.

reference/3.0/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Data_Sections.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_For.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Foreach.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Functions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Switch.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Data_Sections.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_For.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Foreach.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Functions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Switch.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Data_Sections.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_For.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Foreach.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Functions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Switch.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.1/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.1/Microsoft.PowerShell.Core/About/about_Data_Sections.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.1/Microsoft.PowerShell.Core/About/about_For.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.1/Microsoft.PowerShell.Core/About/about_Foreach.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.1/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.1/Microsoft.PowerShell.Core/About/about_Functions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.1/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.1/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.1/Microsoft.PowerShell.Core/About/about_Switch.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/Microsoft.PowerShell.Core/About/about_Data_Sections.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/Microsoft.PowerShell.Core/About/about_For.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/Microsoft.PowerShell.Core/About/about_Foreach.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/Microsoft.PowerShell.Core/About/about_Functions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/Microsoft.PowerShell.Core/About/about_Preference_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/Microsoft.PowerShell.Core/About/about_Switch.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/6/PSDesiredStateConfiguration/About/about_Classes_and_DSC.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Refactoring probe-rs/src/debug/mod.rs into smaller files.

This is a WIP, to break apart the rather large probe-rs/src/debug/mod.rs

@Tiwalun and @Yatekii
As a sample, I've extracted two files (variable_cache.rs and stack_frame.rs) in probe-rs/src/debug.
Before I go through the work of extracting the rest of that mod, can you please have a quick look and comment on my approach? Is there anything you'd like me to do differently?


Make RepeatButton not Focusable by default

Should be fixed by https://github.com/AvaloniaUI/Avalonia/pull/2062


TypeError: core.setWarn is not a function

I am receiving an error while trying to test the action:
(node:1584) UnhandledPromiseRejectionWarning: TypeError: core.setWarn is not a function
    at main (/home/runner/work/_actions/Requarks/changelog-action/v1.3.1/dist/index.js:26894:17)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:1584) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:[15](https://github.com/area28technologies/gh-actions-test/runs/6321575423?check_suite_focus=true#step:3:15)84) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Fixed in 1.3.2

That was quick @NGPixel, thanks!


Multiline select with color view box wrong cursor position

VSCode Version: 1.33.1
OS Version: Windows 10

Steps to Reproduce:

In a CSS file where multiple RGBA square box can appear on the left of a rgba(1,1,1,1) or even a hex color like #ffffff.
Make a multicursor selection by pressing mouse left click + Shift + Alt
Have multiple color square box in the same line. (more make it easier to spot)
just try to move the cursor and farther they are in the line with color box, the cursor are following less the mouse.
Gif to represent it :

I was taking fun to edit vscode css to get my own personalize editor theme as I discover the Custom CSS and JS loader extension. So I slowly edit the CSS file and I try to make animation through linear-gradient. Bad Idea as there is no transition between each animation, but when I try to make multicursor edit, I found out that the cursor wasn't spawing where I was clicking but a bit on the right of where I click so I test it out and found out those box break where my selection should end and my mouse is.

Does this issue occur when all extensions are disabled?: Yes

So I though it would be easier to reproduce the setup by trying CSS that have a lot of RGB in so here is the animation I use in the gif
@keyframes scrollbar-horizontal {
  0%   {background:linear-gradient(to right, rgba(252,40,168,0.2) 0%,rgba(252,40,168,0.6) 20%, rgba(239,247,86,0.6) 40%,rgba(239,247,86,0.6) 60%, rgba(3,237,249,0.6) 80%, rgba(3,237,249,0.2) 100%);}
  16%  {background:linear-gradient(to right, rgba(3,237,249,0.2) 0%,rgba(252,40,168,0.6) 20%, rgba(252,40,168,0.6) 40%,rgba(239,247,86,0.6) 60%, rgba(239,247,86,0.6) 80%, rgba(3,237,249,0.2) 100%);}
  33%  {background:linear-gradient(to right, rgba(3,237,249,0.2) 0%,rgba(3,237,249,0.6) 20%, rgba(252,40,168,0.6) 40%,rgba(252,40,168,0.6) 60%, rgba(239,247,86,0.6) 80%, rgba(239,247,86,0.2) 100%);}
  50%  {background:linear-gradient(to right, rgba(239,247,86,0.2) 0%,rgba(3,237,249,0.6) 20%, rgba(3,237,249,0.6) 40%,rgba(252,40,168,0.6) 60%, rgba(252,40,168,0.6) 80%, rgba(239,247,86,0.2) 100%);}
  66%  {background:linear-gradient(to right, rgba(239,247,86,0.2) 0%,rgba(239,247,86,0.6) 20%, rgba(3,237,249,0.6) 40%,rgba(3,237,249,0.6) 60%, rgba(252,40,168,0.6) 80%, rgba(252,40,168,0.2) 100%);}
  83%  {background:linear-gradient(to right, rgba(252,40,168,0.2) 0%,rgba(239,247,86,0.6) 20%, rgba(239,247,86,0.6) 40%,rgba(3,237,249,0.6) 60%, rgba(3,237,249,0.6) 80%, rgba(252,40,168,0.2) 100%);}
  100% {background:linear-gradient(to right, rgba(252,40,168,0.2) 0%,rgba(252,40,168,0.6) 20%, rgba(239,247,86,0.6) 40%,rgba(239,247,86,0.6) 60%, rgba(3,237,249,0.6) 80%, rgba(3,237,249,0.2) 100%);}
}


Forklift site from / to /marketplace

Here's the yak shave of fixes:

Several broken tests with hardcoded paths
Removal of flask_wtf after the combination of non-root cookie paths, flask_login session handling and CSRF protection failed (now just using wtforms directly)
Reimplementation of CSRF protection

The new CSRF protection doesn't use sessions.  It uses Origin/Referer checks and a time-limited secret token based on the user agent and remote IP.  The old protection didn't do Origin/Referer checks or time limiting, and although it stored secret tokens in sessions, the user agent and remote IP were used to manage sessions in flask_login anyway.

This is for issue #16.

Copying the comment from the last commit for visibility:
The problem is that the third-party session/login library is buggy when
SESSION_COOKIE_PATH is not the root path.
The CSRF protection was rewritten as a workaround, but since then more
bugs have appeared:

sessions keep resetting in Firefox (but not Chrome)
logging out is broken on Chrome

I've reverted the workaround and set the cookie path to /.  I'll have to
debug the problem in the third-party library before we can set it to
/marketplace


pep8 / cleanups?

Nice project, looks like what I was looking for (for mp on esp32 in my case) - thanks for writing it!
What I noticed when looking through the source is that indentation is not 4 spaces as usual and also other spacing / formatting is not pep8 compliant.
Would you accept a PR that fixes this?

Thanks for Your contribution :) merged

@ThomasWaldmann you are collaborator of this project if you accept. 👍 i like your codes

Thanks. I'ld always submit a PR though, so someone (you) can have a second look at the code.


Upgrade 8.5RC1 to 8.5RC2 - Exception brakes site

After upgrade from 8.5RC1 to 8.5RC2 the following unexpected error is thrown:
An exception occurred while executing 'DROP INDEX UNIQ_60D69F3F6973EC66 ON OAuth2AccessToken': SQLSTATE[HY000]: General error: 1553 Cannot drop index 'UNIQ_60D69F3F6973EC66': needed in a foreign key constraint
Site including dashboard is completely unaccessible.

#7612 should fix this issue


[COMPILE ERROR] is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3

Dear Team,
Can you, please, assist?
I did everything in order to integrate with Android - according to README
However i get this:
Launching lib/main.dart on sdk gphone x86 in debug mode...
Running Gradle task 'assembleDebug'...
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/CheckoutApiService.kt: (36, 72): 'run(T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/CheckoutApiService.kt: (38, 22): 'forEach((T) -> Unit): Unit' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (96, 21): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (190, 21): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (198, 25): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (204, 25): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (213, 17): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (220, 13): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (240, 21): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (248, 21): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (254, 21): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (262, 17): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3
e: /Users/mikhailbarsukou/work/apps/flutter/.pub-cache/hosted/pub.dartlang.org/adyen_dropin-0.7.1/android/src/main/kotlin/app/adyen/flutter_adyen/FlutterAdyenPlugin.kt: (269, 13): 'with(T, T.() -> R): R' is only available since Kotlin 1.3.50 and cannot be used in Kotlin 1.3

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':adyen_dropin:compileDebugKotlin'.
> Compilation error. See log for more details

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s
Exception: Gradle task assembleDebug failed with exit code 1

Please, help me with this.
My flutter doctor -v is
[✓] Flutter (Channel stable, 2.2.1, on Mac OS X 10.15.7 19H15 darwin-x64, locale en-ES)
    • Flutter version 2.2.1 at
    • Framework revision 02c026b03c (4 weeks ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Ultimate Edition (version 2021.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 55.1.5
    • Dart plugin version 211.6693.108

[✓] VS Code (version 1.41.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • sdk gphone x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • macOS (desktop)         • macos         • darwin-x64     • Mac OS X 10.15.7 19H15 darwin-x64
    • Chrome (web)            • chrome        • web-javascript • Google Chrome 91.0.4472.114

• No issues found!

Kotlin was updated now. Please try again


Handle looping for Android

Hello, I needed looping on Android to works the same way as for iOS. I changed current onCompletionListener with custom one, that handles loops. Api is the same for iOS and Android. I'm not java master so any suggestion will be appreciated.
Sorry for formatting :/

@pawlowskim Thanks for this. Could you try to apply your changes again without all the formatting updates? It's difficult to keep track of changes if the whole file is reformatted

@benvium Second commit should keep old formatting.

Hi! Thank you for this! If you'd like to rebase this work onto latest master I'd be happy to get it merged! 😀

@paulmelnikow This PR is too old. I have created new one: https://github.com/zmxv/react-native-sound/pull/586
I will close this.


Publish process

[x]  Auto release (#850 )
[ ]  Remove <platform> folder
[ ]  All in One
[ ]  Publish to VSCode by workflow
[ ]  Publish to VSCode according to the platform

@numToStr Could you please help me to implement Remove <platform> folder and All in One ?

@numToStr Could you please help me to implement Remove <platform> folder and All in One ?

Sure. I'll update the workflow to build an all-in-one package until we'll be able release platform-specific vsix.
Meanwhile you can remove the platform folder as it won't effect the current workflow.

We do not need All in One, I could just publish according to the platform, it is not difficault.

Indeed, that'll be great. We could also setup action to publish platform-specific vsix. It'll cover all the points you've mentioned in the op.

Oh no, I forgot open-vsx.org , it seems not supports platform-specific vsix .

See https://github.com/eclipse/openvsx/issues/336 .
We still need the All in One, or we just not release to the market until it supports platform-specific vsix.

We still need the All in One, or we just not release to the market until it supports platform-specific vsix.

An all-in-one asset is still possible even If you've removed the platform folder. As the workflow already has linux, darwin, and windows marker.
We can remove the all-in-one asset once open-vsx starts supporting platform-specific extensions.

@sumneko is linux-64 build for arm64 or x86_64?

I request off-site support

@numToStr  linux-x64 means x86_64.

Done


Unable to assign role to App Registration

Unclear how to assign Azure Digital Twins Data Owner role to App Registration.
Hey Microsoft, I think it is unclear in the current docs how to assign roles to an App Registration, and there are pictures that try to show how it should look like but the important part is cut out.
From the docs under heading Create role assignment:
"In this section, you'll create a role assignment for the App Registration on the Azure Digital Twins instance."
It then suggests the Azure Digital Twins Data Owner role.
However, when following the steps in the next to images, there is no option to actually assign this role to the App Registration. It only shows users and managed identities under the member tab, and there is no managed identity option in the App Registration resource itself (like how it works with other resources).
Under Verify role assignments there is another screenshot that just shows the tab Role assigment, but it does not show how that App Registration has been selected.
I am building a React app with MSAL and ADT and getting Unauthorized errors, I think this might be the issue I can nowhere find how to add App Registrations as roles from within other resources than the App Registration itself.
I think this page could be improved by giving some more information about this issue and not cropping the screenshots.
EDIT: Assigning the role through CLI works even though the same action is not possible through UI. Unfortunately I am still getting the same 401 Unauthorized error.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: cb6b93de-0cab-202d-98b2-6526fd65b8cb
Version Independent ID: 779f81b0-5ef1-a05b-5c47-0ecbe798dd93
Content: Create an app registration with Azure Digital Twins access - Azure Digital Twins
Content Source: articles/digital-twins/how-to-create-app-registration.md
Service: digital-twins
GitHub Login: @baanders
Microsoft Alias: baanders

@Fuchio
Thanks for your feedback! We will investigate and update as appropriate.

#assign:baanders

Hi @Fuchio, thank you for your feedback! I will add some more information, here and in the document.
Here are the steps:

On the Role tab, select the role of Azure Digital Twins Data Owner. (This is the page that has a screenshot in the document currently)

On the "Members" tab, assign access to User, group, or service principal. Then, use + Select members to open the pane on the right, where you can search for the app registration by its name or Client ID, and select it to add the role. (I will add this screenshot to the document)

On the Review + assign tab, select the Review + assign button to finish the role assignment.

I am adding to the document in this pull request (PR): https://github.com/MicrosoftDocs/azure-docs-pr/pull/223660
Since the PR addresses the issue, I'll have Git automatically close this issue when the PR is merged.
However, feel free to continue the conversation here and we can reopen if needed.
Thank you!

@Fuchio: Also, if you continue to see authorization errors after adding the role and would like some help digging into your solution, I'd like to suggest the Microsoft Q&A forum for Azure Digital Twins. This is Azure’s preferred destination for community support, and is attended by Microsoft Engineers, Azure Most Valuable Professionals (MVPs), and our expert community. It’s a good place to post questions that might be solution-specific.

Thanks a lot. This was the solution. However, i had to search on registered app name, not id.

Thanks for the reply and additional information! I've confirmed that it appears to work better using the app name, so I'll update the instructions to recommend searching by name.
That work is being done in this PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/280353


Update README.md with new default branch

This prevents the slightly confusing "branch not found" message when loading from https://citation.js.org/api/0.5/

Thank you!


allow Xcelium, Modelsim, Questa as experimental simulators

Xcelium has been added to Jenkins sim matrix, Questa and Modelsim are lacking licenses, but are supported for partners with licenses

@ThomasFuchs your review has been incorporated


unexpected keyword argument 'collapse_to_SBS96'

Hi,
I am trying to run the sigprofilerextractor() function as following:
sigprofilerextractor("vcf",
output,
inputdata,
"GRCh37"
#exome = TRUE #when WES turn TRUE
#minimum_signatures= 1,
#maximum_signatures= 25,
#nmf_replicates= 100,
#min_nmf_iterations = 10000,
#max_nmf_iterations =1000000,
#nmf_test_conv = 10000,
#nmf_tolerance = 0.00000001,
)
The type of inputdata file is vcf format.
I am having the following error when trying to run:
Error in py_call_impl(callable, dots$args, dots$keywords) :
TypeError: sigProfilerExtractor() got an unexpected keyword argument 'collapse_to_SBS96'

Dear @togasaki1220,
I have just transferred your issue to the appropriate repo, as you are asking about the sigprofilerextractor function.
Could you please check that you have the latest versions of both the SigProfilerExtractorR R wrapper (v1.1.16) and the associated SigProfilerExtractor python package (v1.1.20)?

Please let us know and reopen the ticket if you are still having this issue after updating the versions of SigProfilerExtractorR and SigProfilerExtractor. Thanks for your interest!


fix: fix ios RCTBridgeModule type not found error

ios build is failing due to boost dependency management failing. Tested iOS build locally and works fine.
More info at https://github.com/facebook/react-native/issues/42180


Styling search input

Hi, I am looking for any option to style search input on map.
I know that there is almost no way to move it outside map container, but solution for that is better (for my purpose) searchbar styling.
I mean something like fixed searchbar on top of map.
There is any way to achive that?

see https://github.com/Esri/esri-leaflet-geocoder/issues/32#issuecomment-248769662

Hi @adrianratajczak. I'd like to close this since it has been awhile, but feel free to continue discussing/reopening if you wish.


Respect GA topology label first

Please provide a description of this PR:
node topology label has been GA and beta has been deprecated since k8s 1.17, we can safely do this.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
1b451f12a6d5026435bdfb88ddec55d91a37d15d
link
true
/test integ-cni_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-cni_istio

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
1b451f12a6d5026435bdfb88ddec55d91a37d15d
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster_istio

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
1b451f12a6d5026435bdfb88ddec55d91a37d15d
link
unknown
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
1b451f12a6d5026435bdfb88ddec55d91a37d15d
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster_istio

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
1b451f12a6d5026435bdfb88ddec55d91a37d15d
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster_istio

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
1b451f12a6d5026435bdfb88ddec55d91a37d15d
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster_istio

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
1b451f12a6d5026435bdfb88ddec55d91a37d15d
link
true
/test integ-security-multicluster_istio

integ-pilot-multicluster_istio
1b451f12a6d5026435bdfb88ddec55d91a37d15d
link
unknown
/test integ-pilot-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
1b451f12a6d5026435bdfb88ddec55d91a37d15d
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


How to specify OPENAI_API_BASE

Now in override I can only customize the key, but it is more difficult to use the OpenAI service directly in my country, I hope it is possible to specify OPENAI_API_BASE. if it is possible please let me know the temporary solution to specify OPENAI_API_BASE, I really need it now. Thank you 🙏🙏🙏

OPENAI_API_BASE can be made configurable.
See this example where we are setting the base url to a different value
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/examples/together/stt.py#L8
To configure it the following places in code need to be changed similar to above.
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/app/transcribe/gpt_responder.py#L141
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/app/transcribe/gpt_responder.py#L231
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/app/transcribe/gpt_responder.py#L251
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/sdk/transcriber_models.py#L194
Please submit a PR with the change and I can help with making all the changes.

OPENAI_API_BASE can be made configurable.OPENAI_API_BASE 可以进行配置。
See this example where we are setting the base url to a different value请参阅此示例，我们将基础 url 设置为不同的值
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/examples/together/stt.py#L8
To configure it the following places in code need to be changed similar to above.要对其进行配置，需要对代码中的以下位置进行类似修改。
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/app/transcribe/gpt_responder.py#L141
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/app/transcribe/gpt_responder.py#L231
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/app/transcribe/gpt_responder.py#L251
https://github.com/vivekuppal/transcribe/blob/e30827845e74ae7c5cdb51787fdd4265310ab9c8/sdk/transcriber_models.py#L194
Please submit a PR with the change and I can help with making all the changes.请提交一份修改 PR，我可以帮助您完成所有修改。

I have submitted some of the changes, thank you for your help! 🙏

Resolved in #152.
When using OpenAI based services but need to use a different base_url than 'https://api.openai.com/v1'
In override.yaml add the following
OpenAI:
  api_key: 'API_KEY'
  base_url: 'BASE_URL_FOR_API'

Let us know if this resolves the issue for you.

Resolved in #152.
When using OpenAI based services but need to use a different base_url than 'https://api.openai.com/v1' In override.yaml add the following
OpenAI:
  api_key: 'API_KEY'
  base_url: 'BASE_URL_FOR_API'

Let us know if this resolves the issue for you.

I have tried several times but have not succeeded in compiling the program, there are always numerous problems that lead to compilation errors. Can I ask you again to generate an installation file of the latest version for me? I'm really sorry to bother you again.

Resolved in #152. 已在 #152 中解决。
When using OpenAI based services but need to use a different base_url than 'https://api.openai.com/v1'当使用基于 OpenAI 的服务，但需要使用不同于 ' https://api.openai.com/v1' 的 base_url 时 In override.yaml add the following在 override.yaml 中添加以下内容
OpenAI:
  api_key: 'API_KEY'
  base_url: 'BASE_URL_FOR_API'

Let us know if this resolves the issue for you.如果问题得到解决，请告诉我们。

My friend told me that I can follow another part of the command in the readme to run the program directly instead of running it through the compiled exe program, but after my attempts, I had problems twice while installing the environment according to the tutorials, and once again I ask for your help in updating the compiled program, and that one I should be able to run perfectly.If I could solve the problem myself, I really wouldn't bother you again.

Resolved in #152. 已在 #152 中解决。
When using OpenAI based services but need to use a different base_url than 'https://api.openai.com/v1'当使用基于 OpenAI 的服务，但需要使用不同于 ' https://api.openai.com/v1' 的 base_url 时 In override.yaml add the following在 override.yaml 中添加以下内容
OpenAI:
  api_key: 'API_KEY'
  base_url: 'BASE_URL_FOR_API'

Let us know if this resolves the issue for you.如果问题得到解决，请告诉我们。

After many attempts, I managed to run the program, but it doesn't work. I have confirmed that the tts service provided by the api_base site that I have filled out works without issue. Talking to the webmaster of the api_base site I filled in, I learned that he thinks it is an ssl issue.

Share the api_base site and we can attempt to validate
or
We can debug it in a live session, provide a video conference link
or
Share an email and we will invite you to join the community chat where we can discuss further

@lem0ke eggi and em ok ?
tts -> Text To Speech -> Transcribe doesn't use it from OpenAI. No relevance ???
what the ssl error you getting what the api_base site url?

He told me later that he was drunk that day and misread it, not an ssl issue. But mine still doesn't work.

Share the api_base site and we can attempt to validate or We can debug it in a live session, provide a video conference link or Share an email and we will invite you to join the community chat where we can discuss further

My e-mail is<EMAIL_ADDRESS>

Invite sent to above email.
We are improving the code base to handle this case better in #157 so diagnosing the problem is easier.
The underlying problem seems to be with the provider.
You are using the --api option.
Speech to text is being done using the OpenAI provider service. The API call is timing out. I believe the default timeout is 30 seconds.
One thing you can try is to use the following
python main.py
instead of
python main.py --api
Expected behavior in this case is Speech to text will work ok.
Let us know how it goes.

Let us know if this resolved the issue
and
if you still require to generate binaries. It will take a couple of days at least to generate the binaries.


[Question] the Text property and searching

I used vb's Regex to find matches in the text and Since I wanted it to search all the text, I passed the "Text" property (byRef), thinking it would be faster than passing a whole copy of the text but it didn't work like I expected:
a) Even tho the Text property is actually a copy of the whole text (according to the wiki), I guessed the Text property is only updated if the text has changed since the last time the property was accessed, is it ? Or is it copied each time ?
b) Passing the Text property byRef seems to make it think it was modified. I tried making an empty sub with a byRef string as the only parameter and passing Text to it triggers the BeforeDelete event with the whole text, so I guess it probably deletes the whole text and re-write it every time which means I should probably pass it byVal but then it will make a copy each time and if im wrong about a), this means it is copied twice each time..
c) Avoiding using Text is most probably the anwser to my Regex searching problem, I since noticed that the Scintilla object has regex searching in it so that should keep the whole text from being copied. And for other times where I need get the whole text and pass it byRef, I can use getTextRange(0,TextLength-1) to make sure it doesnt think modifications have been made, but doesnt that mean beign able to get the whole text from Text possibly slower than from getTextRange, and if im wrong about a), doesnt it make using Text to get the whole text something that should always be avoided ?
I don't mean to ask for changes on how the Text property behaves, but I thought about updating the wiki with some clarifications about the stuff I noticed and don't want to go inserting false infos in there and as I am not familiar with C#, I didn't trust the answers I would find from reading the source code.

a). Scintilla will allocate a new String each time you get the Text property. There is no internal mechanism for change detection, but you could easily implement your own wrapper which monitors the change events and invalidates the cache.
b). I'm not an expert in VB.NET at all.. but I don't think passing Text ByVal will create a new copy of the string -- it will create a copy of the string pointer (the information which says where the string is located in memory) but not the string contents.
c). If you can use the regex features built into Scintilla that is ideal because it will avoid making a copy of the Text property, however, they are admittedly very limited. I could check the source code, but I believe internally the Text property is roughly equivalent to GetTextRange(0, TextLength).
In summary, you might be overthinking this a bit. Performance testing will tell you everything you need to know. Avoid "premature optimization". Chances are an occasional regex over the Text property is not going to adversely affect your application performance at all.
What are you doing with your regex and how often will you be doing it?

b) you are right, vb's strings are actually pointers, passing byVal only copies the pointer, I remember seeing an increase in performance by passing them byRef but I probably made other changes and thought the byRef was what made it faster and used byRef with strings ever since
im making a super nintendo ROM disassembly editor, I use regex to find text matching certain patterns to apply visual styles and keep track of stuff. The disassemblies are split in about 1MB .txt files, contain assembly code, comments, raw bytes for tables and gfx etc.. the goal is to use the existing txt files and use regex to cope with the fact that many people edited the files and didn't always use the same syntax, which makes some of the regex very complicated and slow. I managed to keep my app running fast by only using the slower ones when opening files, otherwise even by only using the text that requires styling, typing text was slow. I will save the files in a custom format and make everything coherent so that I dont have to use such complicated regex, make file opening faster and hopefull apply styling to everything dynamically.

I love your project idea! I actually tried to create my own NES emulator in C# (called it SweetNES which I thought was pretty clever) but never finished it. I got it to the point where it could run the 6502 processor code, but lost interest trying to emulate the graphics and sound.
Have you read the guide yet on Custom Syntax Highlighting? Also there have been a few good discussions in the forums about syntax highlighting and regex that you might find helpful such as #226, #76, #49, etc.... just search the forums.
If you are interested I would be happy to review any of your code and make suggestions if you want to PM it to me.
jslusser [dot] mobile [at] gmail [dot] com


[WIP] Add 'Load more' button to Extension Manager

At this point in time, this is just a quick POC of how this pagination could work.
Quite surprisingly, it seems to work well.
It speeds up the initial Extension Manager loading and tab switching quite a bit.
What's missing, though:

Quite some testing
Unit tests
Translation for "Load more"
Styling for the button
JSDoc

I'd like to get some early feedback from you folks.

In the model.change handler, when would it be the case that we add or remove an extension?
I see how the state of an extension can change (install, mark to uninstall, ...), but I don't see how one can appear/disappear...

@MarcelGerber If I recall correctly, model.change handler gets invoked when you drag/select an extension zip using the bottom left area controls of the extension manager dialog. This is the only workflow using which the extension model changes after you launched extension manager view.

Cool stuff @MarcelGerber!
One small question though: should we go with a virtualized list like https://bvaughn.github.io/react-virtualized/#/components/List instead? That way we could take the cake and eat it too: no need for pagination, but super good performance.


Create Wordle-Clone

🛠 Fixes Issue
Closes #239

👨💻 Changes proposed
Add wordle clone

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

@Akshata-Gunapache push your changes again bcoz only 1 line of code changed


Automated cherry pick of #4520: baremetal: fix megaraid check jbod always disabled

Cherry pick of #4520 on release/2.10.0.
#4520: baremetal: fix megaraid check jbod always disabled

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@5344189). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release/2.10.0   #4526   +/-   ##
================================================
  Coverage                  ?   7.46%
================================================
  Files                     ?     418
  Lines                     ?   66721
  Branches                  ?       0
================================================
  Hits                      ?    4984
  Misses                    ?   61311
  Partials                  ?     426

Flag
Coverage Δ

#aFlag
7.46% <ø> (?)

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 5344189...58cdf2a. Read the comment docs.


Windows - Could not find a required file "index.html" under "public" folder

Describe the bug
I am trying to the template app on windows but I get a "Could not find a required file." error.
To Reproduce
Steps to reproduce the behavior:

npx rnv new
select the "@rnv/template-starter" template when asked
npx rnv run -p windows

Expected behavior
Run the template app as an electron app on windows 10
Screenshots or copy&paste
Could not find a required file.
  Name: index.html
  Searched in: D:\Aymen\Projects\_tests\rnv\new\platformBuilds\app_windows\public

Desktop (please complete the following information):

OS: windows 10
Node Version: v16.14.0
RNV Version: 0.36.1

@aymensmurf thanks for reporting this issue.
I've tested on
OS: Windows 10 Pro
Node Version: v16.13.1
RNV Version: 0.37.1
and this error occurs:
│  RNV  BUNDLER STARTED | 31/07/2023, 08:35:58                                 │
│  $ rnv run -p windows                                                        │
├──────────────────────────────────────────────────────────────────────────────┤
│  ReNative Version: 0.37.1                                                    │
│  Project Name ($package.name): win                                           │
│  Project Version ($package.version): 0.1.0                                   │
│  Workspace ($.workspaceID): rnv                                              │
│  Platform (-p): windows                                                      │
│  Engine ($.platforms.windows.engine): engine-rn-electron                     │
│  Template<EMAIL_ADDRESS>                                    │
│  App Config (-c): app                                                        │
│  Build Scheme (-s): debug                                                    │
│  Supported Platforms: windows                                                │
│  Env Info: win32 | x64 | node v16.13.1                                       │
│  Executed Time: 0h:4m:48s:10ms                                               │
│                                                                              │
│ [ success ] [install] \next\dist\lib\find-pages-dir.js requires override by<EMAIL_ADDRESS>FIXING...DONE
│ [ warn ] [configure] Your app is missing assets at C:\Users\dev\Desktop\qa\win\appConfigs\base,C:\Users\dev\Desktop\qa\win\appConfigs\app.
│                                                                              │
│  Project location:                                                           │
│  C:\Users\dev\Desktop\qa\win\platformBuilds\app_windows                      │
└──────────────────────────────────────────────────────────────────────────────┘
[ task ] [run] _runWebDevServer[1]
[ task ] [run] parsePlugins[2]
(node:2436) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:2436) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: 'onBeforeSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
Starting the development server...

One of your dependencies, babel-preset-react-app, is importing the
"@babel/plugin-proposal-private-property-in-object" package without
declaring it in its dependencies. This is currently working because
"@babel/plugin-proposal-private-property-in-object" is already in your
node_modules folder for unrelated reasons, but it may break at any time.

babel-preset-react-app is part of the create-react-app project, which
is not maintianed anymore. It is thus unlikely that this bug will
ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
your devDependencies to work around this error. This will make this message
go away.

Compiled successfully!

You can now view win in the browser.

  http://localhost:8092

Note that the development build is not optimized.
To create a production build, use yarn build.

assets by path static/ 2.8 MiB
  asset static/js/bundle.js 2.49 MiB [emitted] (name: main) 1 related asset
  asset static/media/Inter-Light.58a136ec3193fa8a63e5.ttf 303 KiB [emitted] [immutable] [from: appConfigs/base/fonts/Inter-Light.ttf] (auxiliary name: main)
  asset static/media/logo.63d54a55b067ffc3e842.png 12.1 KiB [emitted] [immutable] [from: platformAssets/runtime/logo.png] (auxiliary name: main)
asset index.html 1.7 KiB [emitted]
asset asset-manifest.json 356 bytes [emitted]
363 modules
webpack 5.88.2 compiled successfully in 30732 ms
[ task ] [run] _runElectronSimulator:windows[1]
ERROR in src/app/index.tsx:25:10
TS2786: 'View' cannot be used as a JSX component.
  Its instance type 'View' is not a valid JSX element.
    The types returned by 'render()' are incompatible between these types.
      Type 'import("C:/Users/dev/Desktop/qa/win/node_modules/@types/react-native/node_modules/@types/react/index").ReactNode' is not assignable to type 'React.ReactNode'.
        Type '{}' is not assignable to type 'ReactNode'.
    23 |
    24 |     return (
  > 25 |         <View style={theme.styles.container}>
       |          ^^^^
    26 |             <Image
    27 |                 style={theme.styles.image}
    28 |                 source={ICON_LOGO}

ERROR in src/app/index.tsx:26:14
TS2786: 'Image' cannot be used as a JSX component.
  Its instance type 'Image' is not a valid JSX element.
    The types returned by 'render()' are incompatible between these types.
      Type 'import("C:/Users/dev/Desktop/qa/win/node_modules/@types/react-native/node_modules/@types/react/index").ReactNode' is not assignable to type 'React.ReactNode'.
    24 |     return (
    25 |         <View style={theme.styles.container}>
  > 26 |             <Image
       |              ^^^^^
    27 |                 style={theme.styles.image}
    28 |                 source={ICON_LOGO}
    29 |                 {...testProps('template-starter-home-screen-renative-image')}

ERROR in src/app/index.tsx:31:14
TS2786: 'Text' cannot be used as a JSX component.
  Its instance type 'Text' is not a valid JSX element.
    The types returned by 'render()' are incompatible between these types.
      Type 'import("C:/Users/dev/Desktop/qa/win/node_modules/@types/react-native/node_modules/@types/react/index").ReactNode' is not assignable to type 'React.ReactNode'.
    29 |                 {...testProps('template-starter-home-screen-renative-image')}
    30 |             />
  > 31 |             <Text style={theme.styles.textH2} {...testProps('template-starter-home-screen-welcome-message-text')}>
       |              ^^^^
    32 |                 {CONFIG.welcomeMessage}
    33 |             </Text>
    34 |             <Text style={theme.styles.textH2} {...testProps('template-starter-home-screen-version-number-text')}>

ERROR in src/app/index.tsx:34:14
TS2786: 'Text' cannot be used as a JSX component.
  Its instance type 'Text' is not a valid JSX element.
    32 |                 {CONFIG.welcomeMessage}
    33 |             </Text>
  > 34 |             <Text style={theme.styles.textH2} {...testProps('template-starter-home-screen-version-number-text')}>
       |              ^^^^
    35 |                 v {packageJson.version}
    36 |             </Text>
    37 |             <Text style={theme.styles.textH3}>

ERROR in src/app/index.tsx:37:14
TS2786: 'Text' cannot be used as a JSX component.
  Its instance type 'Text' is not a valid JSX element.
    35 |                 v {packageJson.version}
    36 |             </Text>
  > 37 |             <Text style={theme.styles.textH3}>
       |              ^^^^
    38 |                 {`platform: ${Api.platform}, factor: ${Api.formFactor}, engine: ${Api.engine}`}
    39 |             </Text>
    40 |             <Text style={theme.styles.textH3}>

ERROR in src/app/index.tsx:40:14
TS2786: 'Text' cannot be used as a JSX component.
  Its instance type 'Text' is not a valid JSX element.
    38 |                 {`platform: ${Api.platform}, factor: ${Api.formFactor}, engine: ${Api.engine}`}
    39 |             </Text>
  > 40 |             <Text style={theme.styles.textH3}>
       |              ^^^^
    41 |                 {
    42 |                     //@ts-ignore
    43 |                     `hermes: ${global.HermesInternal === undefined ? 'no' : 'yes'}`

ERROR in src/app/index.tsx:46:14
TS2786: 'Text' cannot be used as a JSX component.
  Its instance type 'Text' is not a valid JSX element.
    44 |                 }
    45 |             </Text>
  > 46 |             <Text style={theme.styles.textH3}>{`pixelRatio: ${pixelRatio}, ${fontScale}`}</Text>
       |              ^^^^
    47 |             <TouchableOpacity
    48 |                 onPress={toggle}
    49 |                 style={theme.styles.button}

ERROR in src/app/index.tsx:47:14
TS2786: 'TouchableOpacity' cannot be used as a JSX component.
  Its instance type 'TouchableOpacity' is not a valid JSX element.
    The types returned by 'render()' are incompatible between these types.
      Type 'import("C:/Users/dev/Desktop/qa/win/node_modules/@types/react-native/node_modules/@types/react/index").ReactNode' is not assignable to type 'React.ReactNode'.
    45 |             </Text>
    46 |             <Text style={theme.styles.textH3}>{`pixelRatio: ${pixelRatio}, ${fontScale}`}</Text>
  > 47 |             <TouchableOpacity
       |              ^^^^^^^^^^^^^^^^
    48 |                 onPress={toggle}
    49 |                 style={theme.styles.button}
    50 |                 {...testProps('template-starter-home-screen-try-my-button')}

ERROR in src/app/index.tsx:52:18
TS2786: 'Text' cannot be used as a JSX component.
  Its instance type 'Text' is not a valid JSX element.
    50 |                 {...testProps('template-starter-home-screen-try-my-button')}
    51 |             >
  > 52 |                 <Text style={theme.styles.buttonText}>Try me!</Text>
       |                  ^^^^
    53 |             </TouchableOpacity>
    54 |         </View>
    55 |     );

ERROR in src/config.tsx:6:23
TS2307: Cannot find module '../platformAssets/runtime/logo.png' or its corresponding type declarations.
    4 | import CONFIG from '../platformAssets/renative.runtime.json';
    5 | import '../platformAssets/runtime/fontManager';
  > 6 | import ICON_LOGO from '../platformAssets/runtime/logo.png';
      |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    7 |
    8 | export function testProps(testId: string | undefined) {
    9 |     if (!testId) {

ERROR in src/entry/index.lng.ts:1:24
TS2307: Cannot find module '@lightningjs/sdk' or its corresponding type declarations.
  > 1 | import { Launch } from '@lightningjs/sdk';
      |                        ^^^^^^^^^^^^^^^^^^
    2 | import App from '../app';
    3 |
    4 | const Main = (...args) => Launch(App, ...args);

ERROR in src/pages/404.tsx:7:10
TS2786: 'View' cannot be used as a JSX component.
  Its instance type 'View' is not a valid JSX element.
     5 | export default function Page() {
     6 |     return (
  >  7 |         <View style={themeStyles.container}>
       |          ^^^^
     8 |             <Text style={themeStyles.textH2}>This is custom 404!</Text>
     9 |         </View>
    10 |     );

ERROR in src/pages/404.tsx:8:14
TS2786: 'Text' cannot be used as a JSX component.
  Its instance type 'Text' is not a valid JSX element.
     6 |     return (
     7 |         <View style={themeStyles.container}>
  >  8 |             <Text style={themeStyles.textH2}>This is custom 404!</Text>
       |              ^^^^
     9 |         </View>
    10 |     );
    11 | }

@aymensmurf I can't reproduce it on rnv 1.0.0-rc.10; node v18.19.0. Could you try it on this version?

Closing as issue was resolved, feel free to reopen if needed


Trev8939/SurfacePlacement

Add sample which demonstrates the three types of Surface Placement (Draped, Relative, Absolute)

https://devtopia.esri.com/runtime/java-android-sdk/issues/1326

@TADraeseke Looks good to merge!


git_utils: fix push_refspecs result check

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.04% :tada:

Comparison is base (b2fa9dd) 85.47% compared to head (11ba7fa) 85.52%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #381      +/-   ##
==========================================
+ Coverage   85.47%   85.52%   +0.04%
==========================================
  Files          18       18
  Lines        2121     2121
==========================================
+ Hits         1813     1814       +1
+ Misses        308      307       -1

Files Changed
Coverage Δ

gto/git_utils.py
76.23% <100.00%> (+0.99%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


like condition get empty field when there is a column is empty

sqlite3 version："^5.0.2"
As you can see in table Note，there are three rows。And the row which id is 1 has a empty column contentNote, the row which id is 3 has a empty column tite

id
title
contentNote

1
test title

3

test content

https://i.stack.imgur.com/24Flf.png
I can get my expected results in DB Browser(SQLite) with sql:
SELECT Note.guid, Note.deleted, Note.stickTop, Note.title, Note.updateTime, Note.contentNote as content, Tag.name as tagName
FROM Note LEFT JOIN Tag ON Tag.noteGuid =  Note.guid
WHERE ((title is not NULL AND title !="" AND title LIKE '%test%') OR (content is not NULL AND content !="" AND content LIKE '%test%'))

[search result in DB Browser(SQLite)][2]
However, I get a empty column title in my node code with node-sqlite3
const dbPath = ''
const sqlite3 = require('sqlite3').verbose()
const db = new sqlite3.Database(dbPath)
function all(sql: string) {
        return new Promise((resolve, reject) => {
            db.all(sql, (err: Error, data: any) => {
                if (err) {
                    reject(err)
                } else {
                    resolve(data)
                }
            })
        })
    }
const sql = `SELECT title, contentNote as content
FROM Note
WHERE ((title is not NULL AND title LIKE '%test%') OR (content is not NULL AND content !="" AND content LIKE '%test%'))
`
all(sql).then(res => console.log(res))

I get the result as follow
[{
  title: "",
  content: ""
}, {
  title: "",
  content: "test content"
}]

What I expect to get is
[{
  title: "test title",
  content: ""
}, {
  title: "",
  content: "test content"
}]

Hi @zhengtulymGh any progress on this issue? I tried to replicate the same, but its working fine in my case. It will be helpful if you provide some additional details(for ex - node version etc). By the way are there any leading or trailing spaces in that column name ?

Closing as the issue is stale but please post a reproduction case and I can reopen it 🙂


[WIP] Misc fixes and improvements

Fix reminders going into infinite loop
Improve thread safety
Let users choose whether to normalize their audio
Accept 'full' YouTube URLs, reformatting for user

Look through pylint.


[zh] Sync /storage/volumes.md

Sync with one of en #42415
content/zh-cn/docs/concepts/storage/volumes.md

See preview.

/assign


Bug: Can only move 1 item BW/FW

Using MAS 0.9, I can only move one item forward or 1 item backward when using the app switcher. Subsequent TAB presses don't do anything 😢

Hey! Sorry to hear this. I can't repro but I reworked a lot of the internal logic, for the better I hope, please test the latest release.

I have a slightly different issue on 0.10: Now the problem is that the previous app immediately jumps to the second position. So every time I press TAB, I end up on the second to last app I came from.
Essentially I'm stuck between two apps.

Right, you're using tab for both switch keys, but with different hold keys. I can repro, will fix :)

Please retry 0.10, I updated the .exe 🙂

Works like a charm, thanks <3


performance issue with slicing and hdf5

Hi,
when using dask.arrays on hdf5 files, I noticed a quite drastic drop in performance when doing different kinds of slices (continuous vs leaps):
import dask.array as da
import numpy as np
import h5py

# create some big HDF5 files
with h5py.File('d1.h5') as f:
    f.create_dataset('data',data=np.random.rand(10000, 100,100), chunks=(200,100,100))

X = da.from_array(h5py.File('d1.h5')['/data'], chunks=(200,100,100))

ixFast = np.arange(100)   # contiguous indexing
ixSlow = np.arange(0,200,2)  # skipping every second one

% timeit X[ixFast].compute()
# Output:
# 100 loops, best of 3: 16.6 ms per loop

% timeit X[ixSlow].compute()
# Output:
# 10 loops, best of 3: 157 ms per loop

So, slicing out every second element is 10x slower than just getting a contiguous part of the array.
Note that both slices stay within the first chunk of the data (which goes up to element 200), so its not that for the second slice dask has to work on more chunks.
Also, this only seems to happen in conjunction with hdf5. If the array resides in memory, no performance difference occurs :
X = da.from_array(np.random.rand(10000, 100,100), chunks=(200,100,100))
% timeit X[ixFast].compute()
# Output:
# 100 loops, best of 3: 13.4 ms per loop

% timeit X[ixSlow].compute()
# 100 loops, best of 3: 13.3 ms per loop

Any ideas where this comes from?
For me it's quite an issue, since I have huge hdf5-datafiles on disk, whose elements I want to feed into a machine learning algorithm, but not necessarily in the order that they are stored on disk (this skipping every second thing above is just the most simple example I could come up with).

Thanks for the reproducible example.  That is odd.  I'll take a look.
On Tue, Jun 14, 2016 at 8:26 AM, redst4r<EMAIL_ADDRESS>wrote:

Hi,
when using dask.arrays on hdf5 files, I noticed a quite drastic drop in
performance when doing different kinds of slices (continuous vs leaps):
import dask.array as daimport numpy as npimport h5py
create some big HDF5 fileswith h5py.File('d1.h5') as f:
f.create_dataset('data',data=np.random.rand(10000, 100,100), chunks=(200,100,100))

X = da.from_array(h5py.File('d1.h5')['/data'], chunks=(200,100,100))
ixFast = np.arange(100)   # contiguous indexing
ixSlow = np.arange(0,200,2)  # skipping every second one
% timeit X[ixFast].compute()# Output: # 100 loops, best of 3: 16.6 ms per loop
% timeit X[ixSlow].compute()# Output: # 10 loops, best of 3: 157 ms per loop
So, slicing out every second element is 10x slower than just getting a
contiguous part of the array.
Note that both slices stay within the first chunk of the data (which goes
up to element 200), so its not that for the second slice dask has to work
on more chunks.
Also, this only seems to happen in conjunction with hdf5. If the array
resides in memory, no performance difference occurs :
X = da.from_array(np.random.rand(10000, 100,100), chunks=(200,100,100))% timeit X[ixFast].compute()# Output:# 100 loops, best of 3: 13.4 ms per loop
% timeit X[ixSlow].compute()# 100 loops, best of 3: 13.3 ms per loop
Any ideas where this comes from?
For me it's quite an issue, since I have huge hdf5-datafiles on disk,
whose elements I want to feed into a machine learning algorithm, but not
necessarily in the order that they are stored on disk (this skipping every
second thing above is just the most simple example I could come up with).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/1289, or mute the thread
https://github.com/notifications/unsubscribe/AASszKC_E6FuMgvod6zoyitrEot3o-oWks5qLsgWgaJpZM4I1cod
.

So, this might just be an HDF5 or H5Py thing.  Here is the same slowdown occuring without involving dask.array.
In [1]: import dask.array as da

In [2]: import numpy as np

In [3]: import h5py

In [4]: f = h5py.File('d1.h5')

In [5]: ixFast = np.arange(100)   # contiguous indexing

In [6]: ixSlow = np.arange(0,200,2)  # skipping every second one

In [7]: %time _ = f['data'][ixFast, :, :]
CPU times: user 0 ns, sys: 4 ms, total: 4 ms
Wall time: 5.21 ms

In [8]: %time _ = f['data'][ixSlow, :, :]
CPU times: user 184 ms, sys: 4 ms, total: 188 ms
Wall time: 188 ms

I can confirm that this is an HDF5 issue, maybe similar to this H5Py issue.
A simple workaround is to fetch the entire chunk (or multiple if the indices cover many chunks) from HDF5 and slice into them individually.
the_chunk = f['data'][:200]
the_chunk[ixSlow]
#100 loops, best of 3: 3.76 ms per loop

However, in general you pay the price of fetching much more elements than you need.
btw, thanks for this great project, dask made my life alot simpler :)

@redst4r is there anything dask should be doing differently here or should we close this issue?

I don't think it's dask responsibility to handle this; that's really a problem of h5py or even hdf5 itself.
Maybe we can put a hint into the documentation that slicing into those hdf5 arrays might decrease performance.

Hrm, where in the documentation would you suggest?  Corner cases like these are tricky.  It's important to alert people to their presence but hard to introduce them without derailing the general common-case conversation.

Closing for now.  Please reopen if further discussion is warranted


Change metrics name or allow to configure prefix

Is your feature request related to a problem? Please describe.
Hey, guys.
We encountered the following problem while configuring metrics for self hosted cluster. Metrics are not labeled with a special prefix, so there is no grouping for hundreds of metrics. This in turn makes it confusing, because it is not clear whose metrics they are exactly
The example on the screen from google cloud monitoring.

Describe the solution you'd like
It would be cool if all metrics could be grouped under a common label, like Temporal, TemporalWorker, TemporalPoll, etc, so as not to pollute the overall scope.
Describe alternatives you've considered
On the other hand, it's a pretty breakable change. It may be possible to specify a prefix through env variables, which will be empty by default (for backward compatibility), which anyone can specify and thus change the name of metrics in monitoring systems if desired

Thank you for reporting this issue. This issue is likely due to the lack of a common label for Temporal metrics. As you noted, this can be confusing as there are no inherent groupings for metrics when viewing them in your monitoring system.
This issue is a feature request, so we don't have an immediate fix available. However, your suggested solution of using environment variables is an interesting and valid way to work around this issue.
You can use a script to scrape the metrics from your Temporal Service and then prefix them with your desired label. This approach can be tailored to work with various monitoring systems.
This approach isn't ideal, but it does offer a way to work around the current lack of a native solution. We are committed to building a better solution for grouping and labeling Temporal metrics. We welcome your feedback, so that we can make it a priority in a future release.

Thank you for reporting this issue.
Based on the documentation you provided, the metrics are labeled with the Temporal namespace.
Let me know if you have any questions.


Add empty file to functions dir

Current dependencies on/for this PR:

develop

PR #17   👈

This comment was auto-generated by Graphite.


Cannot add BIN games to Naomi folder, even with edited regex

Hi,
just as the title says, even if I edit the regex string I cannot add .bin games to the frontend inside the Naomi category (flycast does support BIN files).
If I apply the same regex string to the same folder inside the Atomiswave section, these games are recognized.

Your using an outdated romset if your using bin files for naomi or atomiswave. Those need to be loaded with a .lst file. Highly would recommend to switching to a MAME romset.
If you want add bin: Highlight Platform > 🖊 > Select the player bubble below player settings > Edit > Save

Understood, thank you


Add a marker to filer by ansible host pattern

Hi,
is there a possibility to filter ansible hosts by host pattern? I know the way to filter by name via --hosts=web*, but this doesn't work for groups in ansible, only for hostnames. For example I can run a ad hoc command like ansible -m ping -i inventory groupname to just contact hosts in the group. This is a pretty cool feature of ansible.
Something like this would be great:  https://github.com/jlaska/pytest-ansible#parameterizing-with-pytestmarkansible. A marker to limit a test to a specific host pattern. So you can have a big test suite, but apply a test for mysql stuff on database hosts only.
What do you think, is this possible? Maybe even now and I don't get it?

Hi,
You can use --hosts=groupname, this will target all host in the group groupname. To target hosts on a per test basis an issue is already opened #48 (workaround available).


Light2D affects alpha-channel unexpectedly

Godot version:
3.3.2 stable
OS/device including version:
Windows 10, Nvidia GTX-960
Issue description:
Light2D affects alpha-channel and produces visible aliasing when lighting is strong enough. All affected non-zero alpha values are seemingly increased, until the resulting image looks as if it had 1-bit alpha.
This is especially apparent when textures have soft alpha-gradients or large areas that are partially transparent.
Proposal behavior for Light2D additive blend mode:
source.RGB = source.RGB + (light.RGB * light.A)
This issue is present in both GLES2 and GLES3
Steps to reproduce:
Add a Sprite with partially transparent areas.
Add a strong Light2D or multiple lights that affect the sprite.
Minimal reproduction project:
light2d_alpha_channel.zip

Related to https://github.com/godotengine/godot/issues/31824 and https://github.com/godotengine/godot/issues/8685. Can you check if either of those issues are duplicates?

Related to #31824 and #8685. Can you check if either of those issues are duplicates?

I don't think they are duplicates, because they seem to affect rendering based on bounding boxes of the lights. Based on those issues I'd guess masking somehow needs to disable any other lights that would affect the same pixels, but I'm only guessing.
This issue affects single pixels, not whole nodes.

This has existed since at least Godot 3.1.2. I suspect (without spending much time on this) it may be a consequence of the multi pass approach used for lighting in Godot 3 - if you try and lighten something up that doesn't have many bits, it will end up looking posterized.

Definitely not a feature, this is very unwanted behaviour. Alpha should be conserved.


STORM-944: storm-hive pom.xml has a dependency conflict with calcite (backport to 0.10.x)

For future maintaining 0.10.x-branch.

CHANGELOG.md should be modified to both branch - master and 0.10.x-branch.

+1


Results view structure

This PR does the following:

Sets up the basic results page structure including sidebar and accordions for new search and filter
Makes sidebar collapsible
Makes logo link back to search page
Fixes styles for search form fields that are required but have no input
Pre-populates search form inputs into new form on results view

TODO:

Build out filters
Build out results view

Great suggestions, @jtquach1! I have addressed your concerns and also fixed a few other very minor issues (see latest commit).


Does report-generation work well for you?

Not sure if it's something I did that was wrong, or it's actually defective, but I tried the examples in serenity-js project  neither running "npm run report" nor using "the failsafe" produces the correct report, which means the report get generated but will be marking the test as "Untested" and missing all the details no matter the tests ran previously were passed or failed. And I followed the instructions from the tutorial project (serenity-js-getting-started) with the same behavior. I wonder if I did something wrong or it's my computer with the latest Java and Node and NPM and browsers (it did run with my current chrome browser though).

Hey @zhtaoang - it's hard to tell without seeing the code. If you're seeing the issue with the serenity-js-getting-started, perhaps you could push your code to github so that I could have a look?

Hi @jan-molak - I checked out your 2-reports branch, and it worked beautifully ... so I guess that was me all along, must have missed something along the way ... anyway, thank you very much for replying to me back so quickly, and sorry that it was a false alarm ... please close the issue or delete it, I would have done that had I found a way to delete it myself. Thanks again!

No problem at all, always happy to help! Have fun with Serenity/JS and please let me know should you find any problems :-)