[ROCKETMQ-339] Specify consume thread pool for different topic

What is the purpose of the change
When a consumer group consumes many topics, it use only one consume thread pool to submit consume tasks.When one topic callback process cost much time,it may block other topic consume and cause message delay.
Brief changelog
add consumeThreadExecutor when subscribe a topic.
Verifying this change
This is a trivial change.
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ROCKETMQ-XXX] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.03%) to 39.993% when pulling 925a5867db5284431bbf8625c21255ddfb151f9e on lindzh:consume_thread_pool into cc0b3d091814a390107b8e733dd8a5427ff49296 on apache:develop.

No need to implement this feature, flow control on topic  https://issues.apache.org/jira/browse/ROCKETMQ-106  should solve the problem


Pvp left click options

It would be a nice addition to the client if the option to remove left click attack on friends and clan members was added. This would help pull some users away from the konduit launcher which is much more pvp based.

This is disallowed by Jagex's unofficial client statement:

Removes or deprioritises attack, cast (or similar) options from the minimenu in any scenario


Jodit type errors when running project with this package

Hey there! I found your project through an issue on jodit-react, but I'm running into a lot of TS errors when starting up my project with it. It doesn't happen using jodit-react, but after installing this one I'm getting TS errors inside of the jodit node_module file. Things like:
ERROR in /Users/scottmalmberg/Dev/jodit-react-ts/node_modules/jodit/src/modules/table.ts
741:31-36
[tsl] ERROR in /Users/scottmalmberg/Dev/jodit-react-ts/node_modules/jodit/src/modules/table.ts(741,32)
      TS6133: 'index' is declared but its value is never read.

ERROR in /Users/scottmalmberg/Dev/jodit-react-ts/node_modules/jodit/src/jodit.ts
684:39-43
[tsl] ERROR in /Users/scottmalmberg/Dev/jodit-react-ts/node_modules/jodit/src/jodit.ts(684,40)
      TS6133: 'type' is declared but its value is never read.

I've tried removing my yarn.lock file and updating my TypeScript (v4.2.2) and ts-loader (v8.0.14) versions to match Jodit's, but haven't had luck. Initially the install seemed successful when I installed while my webpack-dev-server (v3.11.2) was running, but the errors popped up after I restarted it.
Any idea what could be wrong? Thanks!

Hi @ScottMalmberg ! The errors come from Jodit itself. Their types aren't the best.
For typescript projects you should add https://www.typescriptlang.org/tsconfig/skipLibCheck.html to your tsconfig.json file.
This will skip checking types on any of your node_modules packages. Read more here
{
 skipLibCheck: true
}

If this doesn't work please let me know,
Cheers

Thanks for the response! Unfortunately, that flag is already set in my project. Strange that no errors come through when using jodit-react, too. I am able to run your example after cloning into this repo, but not when I try to add it to any of my existing projects.

Could you please share me your tsconfig.json? It would be super helpful for Jodit and I. What kind of framework are you using? Nextjs, gatsby? Create-react-app? Cheers,

I am having th e same issue while using,
"jodit-react": "^1.1.1",
"typescript": "^4.4.2"
and "skipLibCheck": true, option in my tsconfig.json.
I can not do gulp serve. Is it due to tslint ?

I am having th e same issue while using,
"jodit-react": "^1.1.1",
"typescript": "^4.4.2"
and "skipLibCheck": true, option in my tsconfig.json.
I can not do gulp serve. Is it due to tslint ?

Could you please make a sandbox with a basic set up so I can test it?
Regards

I am having th e same issue while using,
"jodit-react": "^1.1.1",
"typescript": "^4.4.2"
and "skipLibCheck": true, option in my tsconfig.json.
I can not do gulp serve. Is it due to tslint ?

Could you please make a sandbox with a basic set up so I can test it?
Regards

There is a compiling error;

I am having th e same issue while using,
"jodit-react": "^1.1.1",
"typescript": "^4.4.2"
and "skipLibCheck": true, option in my tsconfig.json.
I can not do gulp serve. Is it due to tslint ?

Could you please make a sandbox with a basic set up so I can test it?
Regards

There is a compiling error;

Were you able to resolve this error ?


Update source to match latest from .NET repo

See latest bug fix in https://github.com/dotnet/runtime/pull/64143
Sorry I don't have time to post a PR just now; maybe this weekend.

Thanks!!


Update DeveloperGuide.md

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (9789879) compared to base (98a5520).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #50   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


docs(README.md): Fix the url for the EmailPreviewPlug

This PR address a broken link to the EmailPreviewPlug

@tomciopp Thanks for the PR! The README is following master so some links are broken until the new version is shipped. 1.0rc1 is almost done, and once it is the link will work again. So we'll leave this for now since the best way to get docs for the latest published version is to go to hex.
I know it's not ideal, but it's the best we can do right now


typo on Proxies doc

🛑 IMPORTANT: You can get your feedback addressed faster if you use the comment section for the article in which you encountered a problem.
Link to article:
Tell us where exactly a problem occurs.
Problem:
What's wrong with the article?

@videlalvaro Please submit this feedback to the article itself. You can do this by using the feedback section at the bottom


Adding rock paper scissors game

I would like to add Rock paper scissors game.Please assign this issue to me under Gssoc2023

please assign me this issue

please assign me this issue

https://github.com/pranjay-poddar/Dev-Geeks/assets/124433525/457df1c8-b64c-4e07-8fd7-781052c5a36c


gherkin: Update gherkin-python for the Rule keyword

Summary
Bring gherkin-python up to date.
Details

Make gherkin-python up to date (primarily the Rule keyword was missing).
Add back gherkin-python to the gherkin Makefile.
Enable the use of GHERKIN_PYTHON_VERSION to select between python2 and python3 when running the acceptance tests (python3 is the default).

Does also fix #1447
Motivation and Context
How Has This Been Tested?
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

[ ] The change has been ported to Java.
[ ] The change has been ported to Ruby.
[ ] The change has been ported to JavaScript.
[ ] The change has been ported to Go.
[ ] The change has been ported to .NET.
[ ] I've added tests for my code.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have updated the CHANGELOG accordingly.

Excellent work as usual @brasmusson - thanks!!!!


Relax the upper bound on jupyter_client :arrow_up:

Motivation and Context

Closes #72
How has this been tested?

Checklist

[x] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Assigned myself to the PR
[ ] Added tests to cover my changes

FYI @datajoely

Oh you star! Thank you!

Oh, I just noticed this isn't running the CI checks. Please could you do whatever you did to fix your kedro forks CircleCI issue here also?

Looks like the astro-iris starter is unhappy, happy to approve once it's fixed. Also please remember to sign off every commit in order for the DCO plugin to pass (we can force it to pass but it's not sustainable in the long term). We know it's not an ideal workflow but it'a a requirements from Linux Foundation. You can have a look at https://github.com/kedro-org/kedro/blob/main/Makefile#L59-L63 for shortcut on how we enable it by default for kedro.

Closing this as it will be removed altogether in https://github.com/kedro-org/kedro-starters/pull/78


afterChange event no longer available in V2

Hey,
Im currently working on upgrading the version of Astronomer to V2 for one of our project but have come across an issue with the events.
In our application we require the ability to monitor individual property changes and we was doing this via the beforeChange and afterChange events but now they do not fire.
In V2 I cannot see any reference to events that are fired on individual property mutations.
Any advice would be appreciated.
Thanks

It was removed because of performance reason. Firing change events on every document mutation was overkill. Right now you have to handle that in the beforeUpdate and afterUpdate events. You can get modified fields const modified = e.target.getModified() or check if a given field was modified e.target.isModified('fieldName'). However if you want to monitor several fields  the first approach will be faster.


it works，use the release version

Or compile the injector using the x86 architecture and not the x64 architecture. A lot of people just run into errors when they are compiling the source. This is in relation to #2

Hi!
Release version is the same as source. Make sure you building with following configuration (visual studio on screen):

Have a nice day! :)


Tutorial workspace sizes incorrectly when holding a block

Moving blocks around in the workspace during a tutorial has a few side effects.

Blocks behind the hint can be seen when a block is held, but not when not
Scroll bars appear on the right and bottom of the screen. At least when testing at 1920x960 (using a 1920x1080 screen with tabs on top and widows taskbar)
A white box appears sometimes below the simulator using the same resolution as 2.

Looks to be fixed

This still repros. If blocks are behind the tutorial steps and a block is dragged to the bottom of the workspace.

A bit of an edge case. Not sure if it's worth fixing.

Fixed


feat: disable vertical swipe

Feature:
added ability to disable vertical swipe, when scale is equal  1
Description:
In some cases, you would like to disable this gesture (like in my case). I am using X button to close the gallery so I don't need this gesture.
How to test it:
just add disableVerticalSwipe prop and check, if you can't swipe vertically, when image is not zoomed

Please, compare with latest main

Please, compare with latest main

What do you mean ? to resolve conflicts ?

Please, compare with latest main

What do you mean ? to resolve conflicts ?

Yes

@pavelbabenko done :D


Python Tools server keeps crashing

Environment data

VS Code version: 1.25.1
Extension version (available under the Extensions sidebar): 2018.7.1
OS and version: Mac OS X 10.11.6 (El Capitan)

Actual behavior
Python language server is crashing.
Steps to reproduce:

Installed the new vscode plugin

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Starting Microsoft Python language server.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Info  - 12:04:07 PM] Connection to server got closed. Server will restart.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Info  - 12:04:07 PM] Connection to server got closed. Server will restart.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Info  - 12:04:07 PM] Connection to server got closed. Server will restart.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Info  - 12:04:07 PM] Connection to server got closed. Server will restart.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/alysivji/.vscode/extensions/ms-python.python-2018.7.1/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Error - 12:04:08 PM] Connection to server got closed. Server will not be restarted.

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
log.ts:159  INFO no standard startup: not a new window
extensionService.ts:894 Overwriting extension /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.node-debug2 with /Users/alysivji/.vscode/extensions/ms-vscode.node-debug2-1.26.6.
w._logMessageInConsole @ extensionService.ts:894
TMSyntax.ts:47 Overwriting grammar scope name to file mapping for scope source.js.jsx.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/javascript/syntaxes/JavaScriptReact.tmLanguage.json.
New grammar file: file:///Users/alysivji/.vscode/extensions/dzannotti.vscode-babel-coloring-0.0.4/syntaxes/Babel%20Language.json
e.register @ TMSyntax.ts:47
TMSyntax.ts:47 Overwriting grammar scope name to file mapping for scope source.js.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/javascript/syntaxes/JavaScript.tmLanguage.json.
New grammar file: file:///Users/alysivji/.vscode/extensions/joshpeng.sublime-babel-vscode-0.2.10/syntaxes/sublime-babel.json
e.register @ TMSyntax.ts:47
TMSyntax.ts:47 Overwriting grammar scope name to file mapping for scope source.python.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/python/syntaxes/MagicPython.tmLanguage.json.
New grammar file: file:///Users/alysivji/.vscode/extensions/magicstack.magicpython-1.0.12/grammars/MagicPython.tmLanguage
e.register @ TMSyntax.ts:47
notificationsAlerts.ts:42 The Python Tools server crashed 5 times in the last 3 minutes. The server will not be restarted.
e.onDidNotificationChange @ notificationsAlerts.ts:42
console.ts:136 [Extension Host] Failed to get interpreter information for '/Users/alysivji/.virtualenvs/sivtools_dev/bin/python' Error: spawn /Users/alysivji/.virtualenvs/sivtools_dev/bin/python ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)
t.log @ console.ts:136
console.ts:136 [Extension Host] Failed to get interpreter information for '/Users/alysivji/.virtualenvs/sivtools_dev/bin/python' Error: spawn /Users/alysivji/.virtualenvs/sivtools_dev/bin/python ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)
t.log @ console.ts:136
console.ts:136 [Extension Host] Failed to get interpreter information for '/Users/alysivji/.virtualenvs/sivtools_dev/bin/python' Error: spawn /Users/alysivji/.virtualenvs/sivtools_dev/bin/python ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)
t.log @ console.ts:136
console.ts:136 [Extension Host] Failed to get interpreter information for '/Users/alysivji/.virtualenvs/sivtools_dev/bin/python' Error: spawn /Users/alysivji/.virtualenvs/sivtools_dev/bin/python ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)
t.log @ console.ts:136
console.ts:136 [Extension Host] Failed to get interpreter information for '/Users/alysivji/.virtualenvs/sivtools_dev/bin/python' Error: spawn /Users/alysivji/.virtualenvs/sivtools_dev/bin/python ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)
t.log @ console.ts:136
console.ts:136 [Extension Host] Failed to get interpreter information for '/Users/alysivji/.virtualenvs/sivtools_dev/bin/python' Error: spawn /Users/alysivji/.virtualenvs/sivtools_dev/bin/python ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)
t.log @ console.ts:136
console.ts:136 [Extension Host] Failed to get interpreter information for '/Users/alysivji/.virtualenvs/sivtools_dev/bin/python' Error: spawn /Users/alysivji/.virtualenvs/sivtools_dev/bin/python ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)
t.log @ console.ts:136
console.ts:136 [Extension Host] Failed to get interpreter information for '/Users/alysivji/.virtualenvs/sivtools_dev/bin/python' Error: spawn /Users/alysivji/.virtualenvs/sivtools_dev/bin/python ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)
t.log @ console.ts:136

Closing as a duplicate of #2245
Minimum OS requirements not meet.


WIP: PersistentMemory PowerShell reference update

1871163
Previously undocumented module with 9 new cmdlets.

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

File
Status
Preview URL
Details

docset/winserver2022-ps/PersistentMemory/Get-PmemDedicatedMemory.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Get-PmemDisk.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Get-PmemPhysicalDevice.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Get-PmemUnusedRegion.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Initialize-PmemPhysicalDevice.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/New-PmemDedicatedMemory.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/New-PmemDisk.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/PersistentMemory.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Remove-PmemDedicatedMemory.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Remove-PmemDisk.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

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

Docs Build status updates of commit 6f675dd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/PersistentMemory/Get-PmemDedicatedMemory.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Get-PmemDisk.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Get-PmemPhysicalDevice.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Get-PmemUnusedRegion.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Initialize-PmemPhysicalDevice.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/New-PmemDedicatedMemory.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/New-PmemDisk.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/PersistentMemory.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Remove-PmemDedicatedMemory.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/PersistentMemory/Remove-PmemDisk.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

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

Replaced by MicrosoftDocs/windows-powershell-docs/pull/2650


Fix/745 remove fallback data columns; COUNTRY=cambodia

This commit removes the normalized fallback data from the charts CSV creation. It removes the column headers and the values of avg 100 of the anomaly columns.
@ericboucher this is a fix that solves our problem I think. Some additional notes are that the downloadCSV function that downloads the chart data into a CSV file has become quite unreadable. I think we need to address this in a backlog task on moving the function in a separate util file and splitting it in some smaller unit functions and test them properly. Added also individual test in order to have clear testable scenario.
Cc @wadhwamatic

thanks @HarryMytilinaios. This functions as we need.
From what I understand, we're deleting the column for anomaly_avg, which I think is fine. I don't anticipate anyone using that name for a chart variable but it's not entirely impossible. It would good make sure this is well documented. I don't think we have much info on the charts functionality in the readme yet. We should mention that it's a reserved name for exclusion.

@wadhwamatic could you test this latest version and let us know if this suits your needs?

@wadhwamatic could you test this latest version and let us know if this suits your needs?

@ericboucher and @HarryMytilinaios - looks good, thanks!


update key

Updated key and version for pip

Codecov Report

Merging #19 into master will decrease coverage by 6.95%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #19      +/-   ##
==========================================
- Coverage   90.37%   83.42%   -6.96%
==========================================
  Files           1        1
  Lines         187      187
  Branches       20       20
==========================================
- Hits          169      156      -13
- Misses         10       23      +13
  Partials        8        8

Impacted Files
Coverage Δ

src/jodel_api.py
83.42% <100%> (-6.96%)
:arrow_down:

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 eee644d...7e215c3. Read the comment docs.

Thanks!


fix type error

Type 'true | "shell"' is not assignable to type 'boolean | undefined'.

This is not correct though. According to https://pptr.dev/guides/headless-modes, it should be boolean | "shell"

I just pasted the error VS Code was showing me after copying your code.

I just pasted the error VS Code was showing me after copying your code, and how I resolved it.

@Sparticuz Just noticed you linked to Puppeteer docs, but the fix is about Playwright. 😅

Ah, hmm. I'll have to think about the best way to fix that. I've been thinking about how to better divorce the package from puppeteer. (some work of that is in #257)


Multi camera support

Hoi,
i spent a couple of hours the last days trying to understand the code in order to reimplement a few of the original OpenMV features in https://github.com/Oitzu/esp32-camera.
Now, i'm kinda questioning myself if it wouldn't be better to modify the esp32-cam-demo to support multiple cameras and the gone camera settings.
Question: Would you approve such pull requests?

I see this repository more as a simple demo, rather than a comprehensive solution for working with cameras on the ESP32. Well, maybe it's not simple enough, but still.
I think the best way of having multiple cameras supported would be to port OpenMV code to the ESP32. This may offer less instant gratification, but is surely better in the long term.
Initially we can start porting just the camera and image processing related parts of OpenMV. Micropython port is already available from Pycom, so we can reuse that. I think that other folks who frequent this repository would be interested in helping with OpenMV port as well. I don't have huge amount of free time, but I can lend hand with this as well.

Okay, that clarifies my question.

Well, maybe it's not simple enough, but still.

It's great that we have this, without this we would probably still searching the whole next year for the right registers. :D I appreciate your help pretty much.
You are totally right, that porting the OpenMV code would be the best option.
Currently i'm concentrating on implenting the image processing related parts with keeping as much as possible from the OpenMV camera settings and registers.
After this is done, i could maybe concentrate to reimplement more of the OpenMV functions, if more people are interested in this.
But i'm still waiting for my camera (OV7620) for testing to be delivered. :/
At the moment i only have the datasheets to look at, but no actual hardware to test and probe it.

Somehow we have drifted into actually supporting multiple (2) cameras in the same demo, although i think that porting OpenMV is still the way forward. Closing this for now.


Feature: Executables and installers output dir should be customizable

Currently, Tauri builds executables to src-tauri/target/release/. The output dir should be customizable. This will allow the vue cli plugin to output to dist_tauri along with the web code.

This is possible, we would have to add a feature flag and a output directory environment variable.  I could cover the Rust side of things.  Just need someone to add the simple JS/JSON stuff.

I hit this same problem since my target-path is different to default.
I have all the rust-targets at /rust/target/
Currently the tauri build fails for me with following info.
$ yarn tauri build
yarn run v1.22.4
$ /rust/tauri/node_modules/.bin/tauri build
[tauri]: running build
 app:spawn Running "cargo tauri-bundler --features embedded-server --release" +0ms

   Compiling app v0.1.0 (/rust/tauri/src-tauri)
   Compiling tauri v0.5.2
    Finished release [optimized] target(s) in 11.81s
    Bundling app_0.1.0_amd64.deb
error: Failed to build folders
  Caused by: Failed to copy binary file
  Caused by: "/rust/tauri/src-tauri/target/release/app" does not exist

 app:spawn Command "cargo" failed with exit code: 1 +0ms

 app:tauri (runner) ⚠  [FAIL] Cargo CLI has failed +0ms

 app:tauri Shutting down tauri process... +0ms
error Command failed with exit code 1.

There should be a way in the tauri-config to set another target-dir.

We should revisit this.

Looks like an issue with the bundler, probably not following all of the Cargo output folder alternatives (env vars, config etc).

@vhelke your use case will be supported on the next release, see https://github.com/tauri-apps/tauri/pull/895
Thank you for reporting it!


Updating Comments.

It should be True instead of true.
A user can write true by modifying the argument "False" in lines 17 and 23 in Python3 and lines 18 and 24 in Python2 files : "about_asserts.py". However that wont work , because the right keyword is "True". Hence the proposed change.

Thanks!

Welcome, happy to be of help . I am a noob at opensource contributing . I would be grateful if you could guide me towards some more small bugs or issues that i might be able to fix as a beginner .

Thanks for the interest, but Python Koans is really low maintenance these days. Occasionally people report things as Issues but they usually boil down to suggestions that arn't necessarily the way to go. Most of tye PRs these days are spelling corrections or minor tweaks like this one.
The most useful contribution honestly would be testing other peoples PRs as they come in and confirming if they work.

Ok , thanks. I will do that.
On Mon, Jan 25, 2016 at 10:15 PM, Greg Malcolm<EMAIL_ADDRESS>wrote:

Thanks for the interest, but Python Koans is really low maintenance these
days. Occasionally people report things as Issues but they usually boil
down to suggestions that arn't necessarily the way to go. Most of tye PRs
these days are spelling corrections or minor tweaks like this one.
The most useful contribution honestly would be testing other peoples PRs
as they come in and confirming if they work.
—
Reply to this email directly or view it on GitHub
https://github.com/gregmalcolm/python_koans/pull/124#issuecomment-174576671
.


Lint/LiteralInInterpolation does incorrect replacement for hashes

Running the autocorrect for Lint/LiteralInInterpolation does the right thing for strings and numbers, but it does an incorrect replacement for hashes. This is because unlike strings and numbers the string representation of a hash is different from how it is written in code.

Expected behavior
# original code
"#{ { foo: 'bar'} }" #=> "{:foo=>\"bar\"}"

# autocorrected code
"{:foo=>\"bar\"}"

Alternatively, and maybe more preferably, this cop could just not complain about hash literals since depending on the string representation of a hash is an unusual use case.
Actual behavior
# original code
"#{ { foo: 'bar'} }" #=> "{:foo=>\"bar\"}"

# autocorrected code
"{ foo: 'bar' }"

Steps to reproduce the problem

Create a Ruby file foo.rb with contents "#{ { foo: 'bar'} }"
run rubocop --autocorrect --only Lint/LiteralInInterpolation foo.rb

RuboCop version
$ [bundle exec] rubocop -V
1.36.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.21.0, running on ruby 2.7.5) +server [x86_64-darwin21]
  - rubocop-rails 2.15.2

I think @tristil said right.
Actual behavior is not better.
hash type is not defined. so, hash type is using else.
I'll try to fix it to create a when :hash.
https://github.com/rubocop/rubocop/blob/4b4c2a409b14908c4344995720e04a0c65dc55e4/lib/rubocop/cop/lint/literal_in_interpolation.rb#L62-L79

I agree to @KessaPassa, because linter's autocorrect should not break compatibility of the target code. On this case it is expected that rubocop corrects the code exactly same as the result Ruby evaluates.


Explain the filethumbs example a bit.

:+1: Clear improvement.
I will point out that constructing image files on the fly is a major use case (although not one we brought to production), but generally with a tool like numpy+pylab for scientific images as might be used in more technical XBlocks.
JSON on the file system is obviously just a very, very artificial test case.

:+1: Thanks for providing an explanation for the example. It provides a small bit of clarification to developers in how they should use the feature.


💡 [FEATURE] - Add About Page

Idea Contribution

[X] I have read all the feature request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Explain feature request
I will add an about us page for the website
Explain your solution
This will help the user to get an abstract view of the website
Any alternative approaches/features
No response
Additional Context
No response

duplicate issue


Do not reinstall moby in docker.sh, pull images only

docker.sh script re-installs moby. This is unnecessary as the moby is installed in the docker-moby.sh called just shortly before (on Ubuntu 16 and 18). Moreover, the moby-cli is misspelled to mobi-cli.
The script has been renamed to docker-images.sh as it only pull images now.
Fixes #474

Closing the PR in favor of #470


right sidebar: Adjust tooltip design to explain what faded users in the right sidebar mean

Zulip's fading of users in the right sidebar is very useful for seeing who will receive your message at a glance, but it's not intuitive to users and needs explanation.  At present, we don't have anything in-app to explain how this feature works.
We should do the following:

When hovering over a user in the right sidebar who is currently faded by the compose_fade.js code path, we should add an extra line to their tooltip saying "This user will not receive the message you are currently composing."
If that design change is a success, we may want to do something similar when hovering over a faded message in the main message area.

@zulipbot claim

After seeing this prototyped, this design direction isn't going to work, so closing this as an abandoned idea.


Does not work with self-signed HTTPS certificates

I'm not sure if I am doing anything wrong, but it seems es-dump is not working with our setup, where ES is reachable via HTTPS through a self-signed certificate.
From the console:
--- ~ » curl -XGET https://our-internal-server/_cat/indices | tail
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  5742  100  5742    0     0  10313      0 --:--:-- --:--:-- --:--:-- 10327
yellow logstash-2014.09.30 5 1    9645 0 337.2mb 337.2mb
yellow logstash-2014.12.14 5 1   51324 0  33.1mb  33.1mb
yellow logstash-2014.11.02 5 1   16900 0  56.6mb  56.6mb
yellow logstash-2015.01.06 5 1   47712 0  58.6mb  58.6mb
yellow logstash-2014.12.13 5 1   31839 0  35.8mb  35.8mb
yellow logstash-2014.11.14 5 1   34022 0    79mb    79mb
yellow logstash-2015.01.01 5 1   27092 0  32.8mb  32.8mb
yellow logstash-2014.10.20 5 1   13366 0  40.7mb  40.7mb
yellow logstash-2014.10.12 5 1   31878 0   1.3gb   1.3gb
yellow logstash-2014.11.04 5 1   13078 0  22.8mb  22.8mb

...which shows that the certificate works and indices are there. However:
--- ~ » .npm/elasticdump/0.7.7/package/bin/elasticdump --input='https://our-internal-server/kibana-int' --output=/tmp/my_index.json --type=data --debug
Wed, 07 Jan 2015 13:37:38 GMT | starting dump
Wed, 07 Jan 2015 13:37:38 GMT | SELF_SIGNED_CERT_IN_CHAIN
Wed, 07 Jan 2015 13:37:38 GMT | got 0 objects from source elasticsearch (offset: 0)
Wed, 07 Jan 2015 13:37:38 GMT | sent 0 objects to destination file, wrote 0
Wed, 07 Jan 2015 13:37:38 GMT | dump complete

I tried to explicitly specify the 443 port, to omit the --type and --debug parameters, to change the index, to specify --all, to set the output to stdout, and more...
...but to no avail.  If I am doing something wrong, I'm missing what that is...
[As visible from the command line, I am using v0.7.7, and I am running it on my local machine, a Fedora 21 64 bit installation].

Under the hood, we use the request package for making the HTTP requests.  To use self signed certs, it looks like a few steps are required:

supply the strictSSL option

If true, requires SSL certificates be valid. Note: to use your own certificate authority, you need to specify an agent that was created with that CA as an option.

provide a proxy certificate authority via the PEM file with the options:

agentOptions: {
        ca: fs.readFileSync('ca.cert.pem')
    }

It is possible to accept other certificates than those signed by generally allowed Certificate Authorities (CAs). This can be useful, for example, when using self-signed certificates. To allow a different certificate, you can specify the signing CA by adding the contents of the CA's certificate file to the agentOptions

The SELF_SIGNED_CERT_IN_CHAIN  error you are seeing is indicative of request having an SSL issue, so I believe that this is the cause of your problem.  We use this tool over HTTPS with a valid cert, and I confirm that it does work OK.
Please try out the options above (all of your changes should be within this file) and let us know if it works.  If it does, we can try and sort out how to handle the command-line arguments that would be required.

@evantahler - Thank you for the prompt, informative answer. :)
Unluckily I am not a JS developer and I wanted to use elasticsearch-dump for a one-off operation, so both the time and skills I can throw at this are limited, as I could find a workaround to my contingent problem.
I am willing to test stuff to help improving elasticsearch-dump though, but I'd need stricter directions, especially given that the source is undocumented. Where/how should I modify the file? Is the call on line 83 the one of concern (I got to that idea because despite the object being called searchRequest it looks like it's a search that will match all entries).
As I said, I'd be happy to test stuff for you, but I need guidance.

We'll leave this issue open until someone has the time to implement insecure HTTPS certificates.

Cool.  Just to be clear though: a self-signed certificate is not "insecure", it's just a certificate whose chain of trust does not relies on CA authorities.
In fact self-signed certificates is the most common way to secure back-end elasticsearch connections [at least according to the poll conducted by Elasticsearch itself during the webinair on Shield].
In my case I was able to get to a colleague with an account on the server and dump using http on localhost and bypassing Apache altogether, working around the problem.

If you want to use a self-signed cert in node in general, you can add an environment variable to trigger node to be OK with it (which, by default, it is not).
You can either add this as an early ling of code in your elasticsearch "binary" process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0"; or set this when you launch the application, IE:
NODE_TLS_REJECT_UNAUTHORIZED=0 elasticdump --input=http://production.es.com:9200/my_index --output=http://staging.es.com:9200/my_index --type=mapping

Is your example not a self-signed certificate???
http://production.es.com:9200/my_index

is not  self-signed certificate.
in correctly, is below right?
https://production.es.com:9200/my_index

On my machine,  self-signed certificate doesn't work yes....

I believe that the hack above (ENV VARS) only works on some operating systems.  The real answer is to change the code per https://github.com/taskrabbit/elasticsearch-dump/issues/59#issuecomment-69057549.
Pull requests welcome!

In case someone faces the issue and needs a quick workaround.
Here is the Dockerfile that builds a Docker image ignoring the errors caused by the self-signed certificate (based on the original image from Evan):
 FROM alpine:3.3 MAINTAINER<EMAIL_ADDRESS>RUN apk add --update nodejs ENV NODE_TLS_REJECT_UNAUTHORIZED 0 RUN npm install elasticdump -g ENTRYPOINT ["/usr/lib/node_modules/elasticdump/bin/elasticdump"]

You don't need to rebuild the docker file at all, you can pass environment variables in at runtime with  -e NODE_TLS_REJECT_UNAUTHORIZED=0

So glad you addressed this, or I couldn't use the tool!


application text box cutoff text when application name is long

how many characters do you think we should support for application name?

The overflow is wrong. When application name is long , it overflow out of the box and cutoff other application names. It should overflow and if it is long , it should use ellipsis and a tooltip you can hover over


docs: CI/CD Scan API Documentation

Summary
Added documentation for CI/CD Scan APIs. Note: This doc on confluence is outdated, we will need to update it as well

Please do a squash merge

Sure, that's what we do for other repos as well. Will create a ticket for Ben to update settings to only allow squash merge


Remove Locust from API repo

User Story - Business Need
Once the new performance testing system is complete, we want to remove the old system.

[ ] Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)
As a   VANotify
I want to remove API code that is no longer necessary
So that the codebase is clean and easy to maintain
Additional Info and Resources

remove directory load_testing
remove all GHA actions associated with Locust

Acceptance Criteria

There are no more traces of locust in our application repo

QA Considerations

[ ] double-check that all references to Locust no longer exists in this repo.

Potential Dependencies
Needs the new system to be working first.

Still needed.


The llm model is support infer use vllm  or use multi GPUs?

The llm module is support infer use vllm  or use multi GPUs?
If not, when will these features be implemented ?

I have no knowledge in vllm, our repo only provide python inference code by now

I have no knowledge in vllm, our repo only provide python inference code by now

The vllm is A high-throughput and memory-efficient inference and serving engine for LLMs
https://github.com/vllm-project/vllm .
Question 2, is support infer use multi GPUs, Is there a plan to support multi GPUs?

I have no knowledge in vllm, our repo only provide python inference code by now

The vllm is A high-throughput and memory-efficient inference and serving engine for LLMs
https://github.com/vllm-project/vllm .
Question 2, is support infer use multi GPUs, Is there a plan to support multi GPUs?

no, I don't think multi gpu for one service is a good idea. We will try to reduce rtf on a single GPU

I have no knowledge in vllm, our repo only provide python inference code by now

The vllm is A high-throughput and memory-efficient inference and serving engine for LLMs
https://github.com/vllm-project/vllm .
Question 2, is support infer use multi GPUs, Is there a plan to support multi GPUs?

no, I don't think multi gpu for one service is a good idea. We will try to reduce rtf on a single GPU

Thank you for your reply.


When Condition Filters should recognize LogLevel-Type

Support compare of LogLevel instead of just string-comparison. Ex. "Error" >= "Warn".
See also: https://stackoverflow.com/questions/64984152/set-logger-max-log-level-per-http-request-via-filter
And also: https://stackoverflow.com/questions/47475698/how-to-control-nlog-loglevel-using-environment-variables/47517826#47517826
Then one can do this:
<logger name="*"  writeTo="console">
          <filters>
              <when condition="level >= `${environment:LOG_LEVEL:cachedSeconds=5}'" action="Log"/>
          </filters>
 </logger>

Instead of this:
<logger name="*"  writeTo="console">
          <filters>
              <when condition="(level >= LogLevel.Fatal and equals('${environment:LOG_LEVEL:cachedSeconds=5}','LogLevel.Fatal)" action="Log"/>
              <when condition="(level >= LogLevel.Error and equals('${environment:LOG_LEVEL:cachedSeconds=5}','LogLevel.Error')" action="Log"/>
              <when condition="(level >= LogLevel.Info and equals('${environment:LOG_LEVEL:cachedSeconds=5}','LogLevel.Info')" action="Log"/>
              <when condition="(level >= LogLevel.Debug and equals('${environment:LOG_LEVEL:cachedSeconds=5}','LogLevel.Debug')" action="Log"/>
              <when condition="(level >= LogLevel.Trace and equals('${environment:LOG_LEVEL:cachedSeconds=5}','LogLevel.Trace')" action="Log"/>
          </filters>
 </logger>

I guess one could also put this in the master-branch for early release.

I guess one could also put this in the master-branch for early release.

Should also add support for doing this. By recognizing "exception" as keyword just like "logger" and "level".
<logger name="*"  writeTo="console">
          <filters>
              <when condition="exception != null" action="Log"/>
          </filters>
 </logger>

Updated wiki: https://github.com/NLog/NLog/wiki/When-Filter about exception-token


Make webhooks optional

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets

License
Apache 2.0

What's in this PR?

Why?
In constrained environments when Operator is running with least privileges creating the
ValidatingWebhookConfiguration CR may be an option from a RBAC perspective.
Allowing these webhooks to be disabled allows using the operator in these environments.
Default: true (enabled)
Checklist

[x] Implementation tested
[x] Error handling code meets the guideline
[x] Logging code meets the guideline
[x] User guide and development docs updated (if needed)

Hi guys - wanted to get your feedback on this patch. The reason for flag is to optionally lower the privs requirements.
Also - the topic admission webhook seems a bit too heavy as it involves talking with kafka. Wondering if we should push that check to controller and let the webhook do syntactic validations only (kafkaCluster name exists, etc)


Release v0.23.0

v0.23.0 Apr. 20, 2021
Enhancements

Refactored EngineBase and SequentialEngine api. Adding DaskEngine #1975.
Added optional engine argument to AutoMLSearch #1975
Added a warning about how time series support is still in beta when a user passes in a time series problem to AutoMLSearch #2118
Added NaturalLanguageNaNDataCheck data check #2122
Added ValueError to partial_dependence to prevent users from computing partial dependence on columns with all NaNs #2120
Added standard deviation of cv scores to rankings table #2154

Fixes

Fixed BalancedClassificationDataCVSplit, BalancedClassificationDataTVSplit, and BalancedClassificationSampler to use minority:majority ratio instead of majority:minority #2077
Fixed bug where two-way partial dependence plots with categorical variables were not working correctly #2117
Fixed bug where hyperparameters were not displaying properly for pipelines with a list component_graph and duplicate components #2133
Fixed bug where pipeline_parameters argument in AutoMLSearch was not applied to pipelines passed in as allowed_pipelines #2133
Fixed bug where AutoMLSearch was not applying custom hyperparameters to pipelines with a list component_graph and duplicate components #2133

Changes

Removed hyperparameter_ranges from Undersampler and renamed balanced_ratio to sampling_ratio for samplers #2113
Renamed TARGET_BINARY_NOT_TWO_EXAMPLES_PER_CLASS data check message code to TARGET_MULTICLASS_NOT_TWO_EXAMPLES_PER_CLASS #2126
Modified one-way partial dependence plots of categorical features to display data with a bar plot #2117
Renamed score column for automl.rankings as mean_cv_score #2135

Documentation Changes

Fixed conf.py file #2112
Added a sentence to the automl user guide stating that our support for time series problems is still in beta. #2118
Fixed documentation demos #2139
Update test badge in README to use GitHub Actions #2150

Testing Changes

Fixed test_describe_pipeline for pandas v1.2.4 #2129
Added a GitHub Action for building the conda package #1870 #2148
.. warning::

Breaking Changes

Renamed balanced_ratio to sampling_ratio for the BalancedClassificationDataCVSplit, BalancedClassificationDataTVSplit, BalancedClassficationSampler, and Undersampler #2113
Deleted the "errors" key from automl results #1975
Deleted the raise_and_save_error_callback and the log_and_save_error_callback #1975
Fixed BalancedClassificationDataCVSplit, BalancedClassificationDataTVSplit, and BalancedClassificationSampler to use minority:majority ratio instead of majority:minority #2077

@chukarsten one note: in the PR body (and in the text you'll put in the GH release) I see this leftover sphinx gunk:

.. warning::
That's because I haven't merged #2031 yet. My bad. Will do as soon as main reopens.


Singlecellnet introduces "rand" as new cells in the prediction output

Hello,
I have been reviewing some of the previous issues on the "rand" annotation category specifically in #20 and #28.
However, I also noticed that upon prediction for my query dataset using the RF model, singlecellnet introduced 50 new columns in the same location where my cells barcodes are held, each being labelled "rand#" i.e. rand1, rand2 etc.. This caused my prediction output data frame to contain more "cells" (6326) than actual cells in my Seurat object (6276), and required removal prior to merging.
Is this expected behaviour, and if so, could you explain why the package is introducing "new" cells into the prediction? I understand why an individual cell would be annotated as "rand" in certain circumstances, but I do not understand why, in the output prediction frame, new columns are introduced that resemble cells that are named "rand".

Hi, the "new" cells serve as a positive control to attest to the functionality of the "rand" category which prevents your query cells from being forcefully classified as the most similar label in your training. So if most if not all these "new" cells are classified as rand, it means your rand category is working properly. If you don't want to introduce any new "rand" cells, set the nrand parameter in scn_predict to 0.

Thank you for the information!


Collect events before ingesting

Instead of sending events one-by-one, collect them and send them in batches (every 1s or 1000 events would be a sane configuration).

@bahlo I believe this one has been implemented by @damaredayo. can we close the issue?

Can this be closed?

Yes, closed


Detect document body on load

Resolves issue https://github.com/Ciul/angular-facebook/issues/73

Does this is may partially resolved with #94 ?

@mrzmyr Probably, my version wraps everything in a $q promise, so it should theoretically avoid race conditions like that.
I have been using this pull request in production for some time now, so I haven't had issues like that


Picekl/geoclip

:memo: Changelog

[x] GeoCLIP Encoder was added as a pre-trained model.

:link: Links

Reference to the Original Implementation

:white_check_mark: Checklist

[x] Lint and tests pass locally with my changes
[x] I've added the necessary DocString documentation

The code provided looks fine to me. However before pushing it to dev, I feel like we should add an example of it in custom_train (no dataset, or just sample) or benchmarks (with dataset) first.
It will be necessary before pushing it to main anyway

@tlarcher I agree with the "baseline example". Besides, before the merge, I would like to first finish the SatClip model as well.


Addon Idea: Add an addon that makes @ mentions in bios clickable profile links

idea by @lolzthedev

@all-contributors please add @lolzthedev for ideas


Dockerfile does not build

$ docker build .
Sending build context to Docker daemon   6.07MB
Step 1/6 : FROM adoptopenjdk:11-jre-hotspot
 ---> 2c57fb3bc67b
Step 2/6 : WORKDIR /
 ---> Using cache
 ---> cfd8754b8c01
Step 3/6 : COPY [ "./target/docker/dgcg.jar", "/dgcg.jar" ]
COPY failed: file not found in build context or excluded by .dockerignore: stat target/docker/dgcg.jar: file does not exist

Is there a proper Dockerfile which builds from source?

The docker file is for a maven-based build, it should work if you follow the steps outlined in https://github.com/eu-digital-green-certificates/dgc-gateway#build

You have to setup your GitHub Authentication in Maven in order to be able to download dgc-lib dependency.
As an alternative you could build dgc-lib manually on your computer.


Cannot open Runbook locally (macOS )

When I click on the runbook it opens but in read-only mode. When I right click on the runbook and click on "Open local" it doesn't open. How can I edit a runbook locally or on azure within the vs code extension?
I'm working on a mac (macOS Monterey 12.6) with VS Code 1.72

This is fixed in new version (1.0.7). Thanks!
The issue was due to slight dependency on path structure. You can also change directory by using Command palette (ctrl+ shift+P) > 'Change directory' and update directory like "user/abc/..."

Thanks for the fix. Works like a charm now!


Web export ignores clicks under a focused LineEdit

Tested versions
Reproduces in:

v4.3.beta2.official [b75f0485b]
v4.3.beta1.official [a4f2ea91a]

Doesn't reproduce in v4.3.dev6.official [89850d553].
First affected commit is 99d6f32918b8d5b5ca842b5283948dd9c7759f0d.
System information
Arch Linux #1 SMP PREEMPT_DYNAMIC Fri, 28 Jun 2024 04:32:50 +0000 - Tty - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) - 12th Gen Intel(R) Core(TM) i5-1235U (12 Threads)
Issue description
If there's a focused LineEdit directly above a control, the control can't be clicked.
Steps to reproduce
Run MRP as a web export. Focus a LineEdit, then try to click the button below it.
Minimal reproduction project (MRP)
line_edit_web_focus.zip

I think IME is blocking the clicks. Happens in both Firefox and Chromium.

I'll try to fix this. It broke in a PR to fix to #91204, I can reproduce that issue with Windows Chrome and Godot 4.2.2 so I should be able to keep the earlier issue fixed.


Congratulations aram

You win iPhone 11

You win iPhone 11

Let me guess I just need to give you my credit card numbers?😂


Latest authorizationName" in log overwrites all "authorizationName" entries in nuki/lock/log

First, thanks for your effort. 8.34 is working great!
Since the last 8.34 update, the "authorizationName" seems to have been overwritten by the latest "authorizationName".
In 8.33, this feature worked well.
Topic message:
[
	{
		"index": 4289,
		"authorizationId": 926285825,
		"authorizationName": "Linus (Keypad)",
		"timeYear": 2024,
		"timeMonth": 5,
		"timeDay": 19,
		"timeHour": 8,
		"timeMinute": 26,
		"timeSecond": 9,
		"type": "KeypadAction",
		"action": "Unlatch",
		"completionStatus": "success"
	},
	{
		"index": 4288,
		"authorizationId": 902758402,
		"authorizationName": "Linus (Keypad)",
		"timeYear": 2024,
		"timeMonth": 5,
		"timeDay": 19,
		"timeHour": 6,
		"timeMinute": 52,
		"timeSecond": 39,
		"type": "LockAction",
		"action": "Unlock",
		"trigger": "system",
		"completionStatus": "success"
	},
	{
		"index": 4287,
		"authorizationId": 902758402,
		"authorizationName": "Linus (Keypad)",
		"timeYear": 2024,
		"timeMonth": 5,
		"timeDay": 18,
		"timeHour": 19,
		"timeMinute": 36,
		"timeSecond": 21,
		"type": "LockAction",
		"action": "Lock",
		"trigger": "system",
		"completionStatus": "success"
	},
	{
		"index": 4286,
		"authorizationId": 926285825,
		"authorizationName": "Linus (Keypad)",
		"timeYear": 2024,
		"timeMonth": 5,
		"timeDay": 18,
		"timeHour": 14,
		"timeMinute": 12,
		"timeSecond": 21,
		"type": "KeypadAction",
		"action": "Unlatch",
		"completionStatus": "success"
	},
	{
		"index": 4285,
		"authorizationId": 902758402,
		"authorizationName": "Linus (Keypad)",
		"timeYear": 2024,
		"timeMonth": 5,
		"timeDay": 18,
		"timeHour": 14,
		"timeMinute": 8,
		"timeSecond": 14,
		"type": "LockAction",
		"action": "Unlock",
		"trigger": "system",
		"completionStatus": "success"
	}
]

Nuki app log:

Confirmed.
Bug was introduced as part of the fixes for in #344 in #345.
Fixed by #368

@iranl is this fix available in 8.35 ? Thanks!

It is

Works, thanks a lot!


how can i assure that bot does not move forward unless the entity of the intent resolve

Could you share some code of what you have so far so we can help you?

``/*-----------------------------------------------------------------------------
This Bot demonstrates how to use an IntentDialog with a LuisRecognizer to add
natural language support to a bot. The example also shows how to use
UniversalBot.send() to push notifications to a user.
For a complete walkthrough of creating this bot see the article below.
http://docs.botframework.com/builder/node/guides/understanding-natural-language/

-----------------------------------------------------------------------------/
var request = require("request");
/ const fs = require('fs'); */
var restify = require('restify');
var builder = require('botbuilder');
var server = restify.createServer();
server.listen(process.env.port || process.env.PORT || 3978, function () {
console.log('%s listening to %s', server.name, server.url);
});
//=======================================================================
// Create chat bot
//=======================================================================
var connector = new builder.ChatConnector({
appId: '2dfb3dd',
appPassword: 's1v'
});
var builder = require('core');
// Create bot and bind to console
/* var connector = new builder.ConsoleConnector().listen(); */
var bot = new builder.UniversalBot(connector);
server.post('/api/messages', connector.listen());
// Add global LUIS recognizer to bot
var model = process.env.model || 'https://api.projectoxford.ai/luis/v2.0/apps/72556e01-956c-4784-a26d-b7fb3e00df7b?subscription-key=15f282c492514272a354088915b56321';
bot.recognizer(new builder.LuisRecognizer(model));
// Default dialog
bot.dialog('/', function (session) {
session.send("Hi... I'm the reservation bot . I can set reservation for you.");
});
// Set Alarm dialog
bot.dialog('/tsuggest', [
function (session, args, next) {
    // Resolve and store any entities passed from LUIS.
    var intent = args.intent;
    var number = builder.EntityRecognizer.findEntity(intent.entities, 'builtin.numer');
    var time = builder.EntityRecognizer.resolveTime(intent.entities);
    var alarm = session.dialogData.alarm = {
      number: number ? number.entity : null,
      timestamp: time ? time.getTime() : null
    };

    // Prompt for number
    if (!alarm.number) {
        builder.Prompts.text(session, 'how many people you are');
    } else {
        next();
    }
},
function (session, results, next) {
    var alarm = session.dialogData.alarm;
    if (results.response) {
        alarm.number = results.response;
    }

    // Prompt for time
    if (!alarm.timestamp) {
        builder.Prompts.time(session, 'What time would you like to set for tea');
    } else {
        next();
    }
},
function (session, results) {
    var alarm = session.dialogData.alarm;
    if (results.response) {
        var time = builder.EntityRecognizer.resolveTime([results.response]);
        alarm.timestamp = time ? time.getTime() : null;
    }

    // Save address of who to notify and write to scheduler.
    alarm.address = session.message.address;
    alarms[alarm.number] = alarm;

    // Send confirmation to user
    var date = new Date(alarm.timestamp);
    var isAM = date.getHours() < 12;
    session.endDialog('we will suggest you reservation  for "%s" people and time is as follows %d/%d/%d %d:%02d%s please wait',
        alarm.number,
        date.getMonth() + 1, date.getDate(), date.getFullYear(),
        isAM ? date.getHours() : date.getHours() - 12, date.getMinutes(), isAM ? 'am' : 'pm');
}

]).triggerAction({
matches: 'TSUGGEST',
onSelectAction: function (session, args, next) {
switchTasks(session, args, next, "You're already setting a reservation. You need to cancel the current reservation first.");
}
}).cancelAction('cancelSetAlarm', "Reservation canceled.", {
matches: /^(cancel|nevermind)/i,
confirmPrompt: "Are you sure?"
});
/***************************************************************************************************************/
// Delete Alarm dialog
bot.dialog('/TRESERVE', [
function (session, args, next) {
session.send("%s",args.intent);
// Resolve and store any entities passed from LUIS.
var intent = args.intent;
var number = builder.EntityRecognizer.findEntity(intent.entities, 'builtin.numer');
var location1 = builder.EntityRecognizer.findEntity(intent.entities, 'Location');
var time = builder.EntityRecognizer.resolveTime(intent.entities);
var alarm = session.dialogData.alarm = {
number: number ? number.entity : null,
timestamp: time ? time.getTime() : null,
location1: location1? location1.entity :null
};
    // Prompt for number
    if (!alarm.number) {
        builder.Prompts.text(session, 'how many people you are');
    } else {
        next();
    }
},
function (session, results, next) {
    var alarm = session.dialogData.alarm;

    if (results.response) {
        alarm.number = results.response;
    }

    // Prompt for time
    if (!alarm.location1) {
        builder.Prompts.text(session, 'What location would you like to reserve');
    } else {
        next();
    }
},
function (session, results,next) {
	var alarm = session.dialogData.alarm;
    if (results.response) {
       alarm.location1 = results.response;
	  session.send(results.response);
    }
     if (!alarm.timestamp) {
        builder.Prompts.time(session, 'What time would you like to set for tea');
    } else {
        next();
    }
},
function (session, results) {
   var alarm = session.dialogData.alarm;
    if (results.response) {
        var time = builder.EntityRecognizer.resolveTime([results.response]);
        alarm.timestamp = time ? time.getTime() : null;
    }

    // Save address of who to notify and write to scheduler.
    alarm.address = session.message.address;
    alarms[alarm.location1] = alarm;

    // Send confirmation to user
    var date = new Date(alarm.timestamp);
    var isAM = date.getHours() < 12;
    session.endDialog('we will confirm your  reservation  for "%s" people and time is as follows "%s"  %d/%d/%d %d:%02d%s please wait',
        alarm.number,
		alarm.location1,
        date.getMonth() + 1, date.getDate(), date.getFullYear(),
        isAM ? date.getHours() : date.getHours() - 12, date.getMinutes(), isAM ? 'am' : 'pm');
}

]).triggerAction({
matches: 'TRESERVE'
}).cancelAction('cancelDeleteAlarm', "Ok.", {
matches: /^(cancel|nevermind)/i
});
// Very simple alarm scheduler
var alarms = {};
setInterval(function () {
var now = new Date().getTime();
for (var key in alarms) {
var alarm = alarms[key];
if (now >= alarm.timestamp) {
var msg = new builder.Message()
.address(alarm.address)
.text("Here's your '%s' reservation.", alarm.location1);
bot.send(msg);
delete alarms[key];
}
}
}, 15000);
// Helpers
function alarmCount() {
var i = 0;
for (var name in alarms) {
i++;
}
return i;
}
function switchTasks(session, args, next, alreadyActiveMessage) {
// Check to see if we're already active.
// - We're assuming that we're being called from a triggerAction() some
//   args.action is the fully qualified dialog ID.
var stack = session.dialogStack();
if (builder.Session.findDialogStackEntry(stack, args.action) >= 0) {
session.send(alreadyActiveMessage);
} else {
// Clear stack and switch tasks
session.clearDialogStack();
next();
}
}

So the issue is that model isn't great at detecting things like the name of your alarm and since its using the built-in Cortana model you can't actually re-train it which is what you would normally do to fix this type of problem.  I noticed the same issue when I coded the sample and you can't really do anything about it but it is just meant to be a sample.
Hope that made sense...

thanks for your help from your reply i understand that we could only make
resolve check on builtin entities  Is I am right?
On Sat, Nov 26, 2016 at 10:48 AM, Steven Ickman<EMAIL_ADDRESS>wrote:

So the issue is that model isn't great at detecting things like the name
of your alarm and since its using the built-in Cortana model you can't
actually re-train it which is what you would normally do to fix this type
of problem. I noticed the same issue when I coded the sample and you can't
really do anything about it but it is just meant to be a sample.
Hope that made sense...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/1694#issuecomment-263045865,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASxjp2s-xARahTAVb6ypkpso3NCs128yks5rB8gggaJpZM4K2Wta
.

@stevenic or @maxpert could you comment?

Normally you can log into LUIS and train it to fix the unrecognized entities. You can't do that with the built in models so there's nothing you can fix. Fortunately it's pretty easy to build a custom model that des the same thing.

{
"query": "please suggest tee time for 6 people at the gardens at 9 pm on 20th dec",
"topScoringIntent": {
"intent": "TSUGGEST",
"score": 0.9413908,
"actions": [
{
"triggered": true,
"name": "TSUGGEST",
"parameters": [
{
"name": "Number",
"type": "Number",
"required": true,
"value": [
{
"entity": "6",
"type": "Number",
"resolution": {}
}
]
},
{
"name": "Date",
"type": "datetime",
"required": true,
"value": [
{
"entity": "9 pm",
"type": "builtin.datetime.time",
"resolution": {
"time": "T21"
}
},
{
"entity": "20th dec",
"type": "builtin.datetime.date",
"resolution": {
"date": "XXXX-12-20"
}
}
]
},
{
"name": "Location",
"type": "Location",
"required": true,
"value": [
{
"entity": "the gardens",
"type": "Location",
"resolution": {}
}
]
}
]
}
]
},
"entities": [
{
"entity": "the gardens",
"type": "Location",
"startIndex": 40,
"endIndex": 50,
"score": 0.736285031,
"resolution": {}
},
{
"entity": "6",
"type": "Number",
"startIndex": 28,
"endIndex": 28,
"score": 0.982263565,
"resolution": {}
},
{
"entity": "9 pm",
"type": "builtin.datetime.time",
"startIndex": 55,
"endIndex": 58,
"resolution": {
"time": "T21"
}
},
{
"entity": "20th dec",
"type": "builtin.datetime.date",
"startIndex": 63,
"endIndex": 70,
"resolution": {
"date": "XXXX-12-20"
}
}
],
"dialog": {
"contextId": "ef12a34a-77ab-427a-bce3-6e7a40f4f774",
"status": "Finished"
}
}

Hi @subhans3tech, training the model is beyond the scope of what we can do in this forum, but please let us know if you encounter a specific problem.
Closing this issue for now, please at-mention or file a new issue if you want to discuss further.

Fortunately it's pretty easy to build a custom model that does the same thing.

@Stevenic : How? how to reuse the existing one (import selective entities) from builtin-entities and modify further

@habibcs  can you please create a new issue and for your question?
also:
The Bot Framework support team prefers to answer questions like this on Stack Overflow.  If the issue gets closed here on GitHub, it will not be available and indexed for external search engines so others can easily find it.  We are happy to answer your question here, but would you please also post your question to Stack Overflow.  Thanks!


Fix incorrect quote placement in command

The quote was in an incorrect place here, which if copied would cause an error to be thrown.

Good catch! Thanks.