Using inline lambda functions causes errors on line 1 to be reported

Environment data

VS Code version: 1.36.1
Extension version (available under the Extensions sidebar): 2019.6.24221 (9 July 2019)
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): Anaconda Python 3.7.3
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Relevant/affected Python packages and their versions: pandas 0.24.2
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): False

Expected behaviour
No error message
Actual behaviour
Get message  (repeated twice) in "Problems" that says "Function already defined at line 1.Python(function-redefined)"
Line 1 is highlighted indicating there is an error on the import statement.
Steps to reproduce:
Enter this code, and wait a while until the Python analysis completes:
import pandas as pd

def foo():

    somedf = pd.DataFrame({'x': [1, 2], 'y': [3, 4]})

    newdf = (
        somedf
        .assign(
            Abc=lambda df: df.x + df.y,
            Xyz=lambda df: df.x * df.y
        )
    )

    return True

After pasting the above into the editor, and letting the analysis complete, it may be necessary to add another lambda function to make the next analysis show the error message.  In other words, change
            Abc=lambda df: df.x + df.y,
            Xyz=lambda df: df.x * df.y

to
            Abc=lambda df: df.x + df.y,
            Xyz=lambda df: df.x * df.y,
            Hij=lambda df: df.x / df.y

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
User belongs to experiment group 'AlwaysDisplayTestExplorer - experiment'
Starting Microsoft Python language server.
##########Linting Output - pep8##########
[Info  - 8:46:01 PM] Analysis cache path: C:\Users\irv.PCI\AppData\Local\Microsoft\Python Language Server
[Info  - 8:46:02 PM] GetCurrentSearchPaths C:\Anaconda3\python.exe
[Info  - 8:46:02 PM] Interpreter search paths:
[Info  - 8:46:02 PM]     c:\anaconda3\dlls
[Info  - 8:46:02 PM]     c:\anaconda3\lib
[Info  - 8:46:02 PM]     c:\anaconda3
[Info  - 8:46:02 PM]     c:\anaconda3\lib\site-packages
[Info  - 8:46:02 PM]     c:\anaconda3\lib\site-packages\win32
[Info  - 8:46:02 PM]     c:\anaconda3\lib\site-packages\win32\lib
[Info  - 8:46:02 PM]     c:\anaconda3\lib\site-packages\pythonwin
[Info  - 8:46:02 PM] User search paths:
##########Linting Output - pep8##########
[Info  - 8:47:20 PM] Microsoft Python Language Server version <IP_ADDRESS>
[Info  - 8:47:20 PM] Initializing for C:\Anaconda3\python.exe
##########Linting Output - pep8##########

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
abstractTextMateService.ts:52 Overwriting grammar scope name to file mapping for scope source.yaml.
Old grammar file: file:///c%3A/Program%20Files/Microsoft%20VS%20Code/resources/app/extensions/yaml/syntaxes/yaml.tmLanguage.json.
New grammar file: file:///c%3A/Users/irv.PCI/.vscode/extensions/redhat.vscode-yaml-0.4.1/syntaxes/yaml.tmLanguage.json
register @ abstractTextMateService.ts:52
log.ts:173   ERR Error: [File Watcher (node.js)] Error: ENOENT: no such file or directory, stat 'c:\Code\Misc\VSCodeTst\.vscode'
log.ts:173   ERR [File Watcher (node.js)] Error: ENOENT: no such file or directory, stat 'c:\Code\Misc\VSCodeTst\.vscode'
extensionHost.ts:293 [Extension Host] debugger listening on port 42627
extensionHost.ts:201 Extension Host
extensionHost.ts:202 Debugger listening on ws://<IP_ADDRESS>:42627/45070a6c-2d5c-47f2-b7a3-194ed19ce0fd
For help, see: https://nodejs.org/en/docs/inspector
console.ts:134 [Extension Host] (node:38300) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
t.log @ console.ts:134
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 3ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 4ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 5ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 1ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 2ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Create file systemwatcher with pattern *\python.exe
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Create file systemwatcher with pattern *\*\python.exe
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 1ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Register Intepreter Watcher, Class name = p, completed in 15ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst\src\simple.py>, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Build the workspace interpreter watcher, Class name = h, completed in 20ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst\src\simple.py>, Return Value: <Return value cannot be serialized for logging>
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Rule = settings, result = exit
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: autoSelectInterpreter, Class name = f, completed in 6ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst>, Arg 2: <argument cannot be serialized for logging>, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Notify locators are locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detected refreshing of Interpreters, Class name = p, completed in 0ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Rule = settings, result = exit
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Build the workspace interpreter watcher, Class name = h, completed in 2ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst\src\simple.py>, Return Value: <Return value cannot be serialized for logging>
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: autoSelectInterpreter, Class name = f, completed in 7ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst>, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detection of Python Interpreter for Command python3.7 and args  failed
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detection of Python Interpreter for Command python3.6 and args  failed
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detection of Python Interpreter for Command python3 and args  failed
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detection of Python Interpreter for Command python2 and args  failed
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detection of Python Interpreter for Command py and args -3.7 failed
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:51: Detection of Python Interpreter for Command py and args -3.6 failed
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Detection of Python Interpreter for Command py and args -3 failed
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Detection of Python Interpreter for Command py and args -2 failed
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Selected Interpreter from windowsRegistry, {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown","cachedEntry":true}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Selected Interpreter from currentPath, {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","type":"Unknown","cachedEntry":true}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Current value for rule system is {"architecture":3,"path":"C:\\Anaconda3\\envs\\pandas-dev\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3\\envs\\pandas-dev","fileHash":"aad3647123fc6fc53d0a0d423ee7fb6e9d87fb1a6b43846356f00617a0a5be8880772b1e013941261fda2cf493b7b6ae7a83e4495b02ef6e1f6972878a8b9fe5","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"C:\\Anaconda3\\envs\\pandas-dev","envName":"pandas-dev","displayName":"Python 3.7.3 64-bit ('pandas-dev': conda)"}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Current value for rule currentPath is {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","type":"Unknown","cachedEntry":true}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Current value for rule windowsRegistry is {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown","cachedEntry":true}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Selected Interpreter from cachedInterpreters, {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown","cachedEntry":true}
console.ts:134 [Extension Host] Error Python Extension: 2019-07-22 20:45:52: Failed to check if file needs to be fixed { [Error: ENOENT: no such file or directory, open 'c:\Code\Misc\VSCodeTst\.vscode\settings.json']  errno: -4058,  code: 'ENOENT',  syscall: 'open',  path: 'c:\\Code\\Misc\\VSCodeTst\\.vscode\\settings.json' }
t.log @ console.ts:134
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Get language server folder name, Class name = f, completed in 530ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst\src\simple.py>, Return Value: "languageServer.0.3.38"
2console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Interpreters returned by PipEnvService are of count 0
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: setGlobalInterpreter, Class name = f, completed in 397ms, Arg 1: {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown","cachedEntry":true}, Arg 2: undefined, Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: setGlobalInterpreter, Class name = f, completed in 396ms, Arg 1: {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","type":"Unknown","cachedEntry":true}, Arg 2: undefined, Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: setGlobalInterpreter, Class name = f, completed in 393ms, Arg 1: {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown","cachedEntry":true}, Arg 2: undefined, Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Rule = windowsRegistry, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Executing next rule from windowsRegistry
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Rule = currentPath, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Executing next rule from currentPath
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Rule = cachedInterpreters, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Executing next rule from cachedInterpreters
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: autoSelectInterpreter, Class name = f, completed in 684ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst>, Return Value: undefined
2console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: autoSelectInterpreter, Class name = f, completed in 685ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst>, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Get language server folder name, Class name = f, completed in 150ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst\src\simple.py>, Return Value: "languageServer.0.3.38"
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Cached data exists getEnvironmentVariables, c:\Code\Misc\VSCodeTst\src\simple.py
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Selected Interpreter from system, {"architecture":3,"path":"C:\\Anaconda3\\envs\\pandas-dev\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3\\envs\\pandas-dev","fileHash":"aad3647123fc6fc53d0a0d423ee7fb6e9d87fb1a6b43846356f00617a0a5be8880772b1e013941261fda2cf493b7b6ae7a83e4495b02ef6e1f6972878a8b9fe5","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"C:\\Anaconda3\\envs\\pandas-dev","envName":"pandas-dev","cachedEntry":true,"displayName":"Python 3.7.3 64-bit ('pandas-dev': conda)"}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Interpreters returned by VirtualEnvService are of count 0
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Interpreters returned by KnownPathsService are of count 1
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Cached data exists getEnvironmentVariables, c:\Code\Misc\VSCodeTst\src\simple.py
2console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Interpreters returned by WorkspaceVirtualEnvService are of count 0
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: setGlobalInterpreter, Class name = f, completed in 107ms, Arg 1: {"architecture":3,"path":"C:\\Anaconda3\\envs\\pandas-dev\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3\\envs\\pandas-dev","fileHash":"aad3647123fc6fc53d0a0d423ee7fb6e9d87fb1a6b43846356f00617a0a5be8880772b1e013941261fda2cf493b7b6ae7a83e4495b02ef6e1f6972878a8b9fe5","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"C:\\Anaconda3\\envs\\pandas-dev","envName":"pandas-dev","cachedEntry":true,"displayName":"Python 3.7.3 64-bit ('pandas-dev': conda)"}, Arg 2: undefined, Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Rule = system, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Executing next rule from system
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Selected Interpreter from workspaceEnvs, Nothing Selected
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: autoSelectInterpreter, Class name = f, completed in 848ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst>, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Rule = workspaceEnvs, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Executing next rule from workspaceEnvs
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: autoSelectInterpreter, Class name = f, completed in 849ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst>, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Cached data exists getEnvironmentVariables, c:\Code\Misc\VSCodeTst\src\simple.py
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Interpreters returned by CurrentPathService are of count 2
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Interpreters returned by WindowsRegistryService are of count 2
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:52: Checking whether locactors have completed locating, Class name = p, completed in 1ms, , Return Value: false
3console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:53: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:56: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:56: Activation Commands received C:/Anaconda3/Scripts/activate,conda activate base for shell cmd
2console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:56: Cached data exists getEnvironmentVariables, c:\Code\Misc\VSCodeTst\src\simple.py
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:56: Has Custom Env Vars
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:56: Activating Environment to capture Environment variables, C:/Anaconda3/Scripts/activate && conda activate base && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python C:/Users/irv.PCI/.vscode/extensions/ms-python.python-2019.6.24221/pythonFiles/printEnvVariables.py
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:58: parseEnvironmentOutput, Class name = b, completed in 0ms
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:58: getActivatedEnvironmentVariables, Class name = b, completed in 6339ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst\src\simple.py>
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:45:58: Get language server folder name, Class name = f, completed in 5ms, Arg 1: <Uri:c:\Code\Misc\VSCodeTst\src\simple.py>, Return Value: "languageServer.0.3.38"
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:46:00: Interpreters returned by CondaEnvFileService are of count 3
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:46:02: Interpreters returned by CondaEnvService are of count 4
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:46:02: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: true
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:46:02: Hide locator refreshing progress, Class name = p, completed in 1ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:46:02: All locators have completed locating, Class name = p, completed in 1ms, , Return Value: undefined
console.ts:134 [Extension Host] Error Python Extension: 2019-07-22 20:46:14: Failed to initialize experiments, Class name = b, completed in 23286ms, , Return Value: undefined { [Error: read ECONNRESET	at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)] errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
t.log @ console.ts:134
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:46:35: Cached data exists getEnvironmentVariables, c:\Code\Misc\VSCodeTst\src\simple.py
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:20: Starting Language Server, Class name = d, completed in 88445ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:20: Cached data exists getEnvironmentVariables, c:\Code\Misc\VSCodeTst\src\simple.py
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:20: Rule = settings, result = exit
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:20: autoSelectInterpreter, Class name = f, completed in 0ms, Arg 1: undefined, Arg 2: <argument cannot be serialized for logging>, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Display locator refreshing progress, Class name = p, completed in 1ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Notify locators are locating, Class name = p, completed in 2ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Detected refreshing of Interpreters, Class name = p, completed in 2ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Notify locators are locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Rule = settings, result = exit
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: autoSelectInterpreter, Class name = f, completed in 6ms, Arg 1: undefined, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Shell path from user settings 'null'
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Shell path 'C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe'
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Shell path identified as shell 'powershell'
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Shell path from user env 'C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe'
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Shell identified as 'powershell'
3console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Selected Interpreter from windowsRegistry, {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown"}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Selected Interpreter from currentPath, {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","type":"Unknown"}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Current value for rule system is {"architecture":3,"path":"C:\\Anaconda3\\envs\\pandas-dev\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3\\envs\\pandas-dev","fileHash":"aad3647123fc6fc53d0a0d423ee7fb6e9d87fb1a6b43846356f00617a0a5be8880772b1e013941261fda2cf493b7b6ae7a83e4495b02ef6e1f6972878a8b9fe5","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"C:\\Anaconda3\\envs\\pandas-dev","envName":"pandas-dev","cachedEntry":true,"displayName":"Python 3.7.3 64-bit ('pandas-dev': conda)"}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Current value for rule currentPath is {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","type":"Unknown"}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Current value for rule windowsRegistry is {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown"}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Selected Interpreter from cachedInterpreters, {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown"}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Notify locators are locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Create file systemwatcher with pattern *\python.exe
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Create file systemwatcher with pattern *\*\python.exe
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Display locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Notify locators are locating, Class name = p, completed in 1ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Detected refreshing of Interpreters, Class name = p, completed in 1ms, Arg 1: {}, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Register Intepreter Watcher, Class name = p, completed in 3ms, Arg 1: undefined, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Build the workspace interpreter watcher, Class name = h, completed in 4ms, Arg 1: undefined, Return Value: <Return value cannot be serialized for logging>
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Selected Interpreter from system, {"architecture":3,"path":"C:\\Anaconda3\\envs\\pandas-dev\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3\\envs\\pandas-dev","fileHash":"aad3647123fc6fc53d0a0d423ee7fb6e9d87fb1a6b43846356f00617a0a5be8880772b1e013941261fda2cf493b7b6ae7a83e4495b02ef6e1f6972878a8b9fe5","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"C:\\Anaconda3\\envs\\pandas-dev","envName":"pandas-dev","displayName":"Python 3.7.3 64-bit ('pandas-dev': conda)"}
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Interpreters returned by PipEnvService are of count 0
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: setGlobalInterpreter, Class name = f, completed in 57ms, Arg 1: {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown"}, Arg 2: undefined, Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: setGlobalInterpreter, Class name = f, completed in 56ms, Arg 1: {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","type":"Unknown"}, Arg 2: undefined, Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: setGlobalInterpreter, Class name = f, completed in 54ms, Arg 1: {"architecture":3,"path":"C:\\Anaconda3\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3","fileHash":"717e7367a991a271e3fa6a2586fa165c9a7f5a7d25685d0679f62ad999b31d58b53cd26cfd66ba1e979b261d9509588dcac41d2038e1fdeb3b5f631ff9903011","companyDisplayName":"Anaconda, Inc.","type":"Unknown"}, Arg 2: undefined, Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Rule = windowsRegistry, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Executing next rule from windowsRegistry
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Rule = currentPath, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Executing next rule from currentPath
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Rule = cachedInterpreters, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Executing next rule from cachedInterpreters
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: false
3console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: autoSelectInterpreter, Class name = f, completed in 145ms, Arg 1: undefined, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Interpreters returned by PipEnvService are of count 0
2console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Interpreters returned by WorkspaceVirtualEnvService are of count 0
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: setGlobalInterpreter, Class name = f, completed in 61ms, Arg 1: {"architecture":3,"path":"C:\\Anaconda3\\envs\\pandas-dev\\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\\Anaconda3\\envs\\pandas-dev","fileHash":"aad3647123fc6fc53d0a0d423ee7fb6e9d87fb1a6b43846356f00617a0a5be8880772b1e013941261fda2cf493b7b6ae7a83e4495b02ef6e1f6972878a8b9fe5","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"C:\\Anaconda3\\envs\\pandas-dev","envName":"pandas-dev","displayName":"Python 3.7.3 64-bit ('pandas-dev': conda)"}, Arg 2: undefined, Return Value: false
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Rule = system, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Executing next rule from system
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Checking whether locactors have completed locating, Class name = p, completed in 0ms, , Return Value: true
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Hide locator refreshing progress, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: All locators have completed locating, Class name = p, completed in 0ms, , Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Selected Interpreter from workspaceEnvs, Nothing Selected
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: autoSelectInterpreter, Class name = f, completed in 186ms, Arg 1: undefined, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Rule = workspaceEnvs, result = runNextRule
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: Executing next rule from workspaceEnvs
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:21: autoSelectInterpreter, Class name = f, completed in 186ms, Arg 1: undefined, Return Value: undefined
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:22: Current value for rule workspaceEnvs is nothing
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:47:31: Cached data exists getEnvironmentVariables, c:\Code\Misc\VSCodeTst\src\simple.py
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:52:26: Cached data exists getEnvironmentVariables, c:\Code\Misc\VSCodeTst
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:53:21: Cached data exists getEnvironmentVariables, c:\Code\Misc\VSCodeTst
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:56:08: Cached data exists getEnvironmentVariables, tasks
console.ts:134 [Extension Host] Info Python Extension: 2019-07-22 20:56:12: Cached data exists getEnvironmentVariables, extension-output-#3

This warning has been removed in the latest version, 0.3.39. You should be able to restart VS Code to trigger and update to the latest language server version. If you don't get it automatically, you can force an update via: https://github.com/microsoft/vscode-python/issues/3977


httpx 0.27.0 support

Can you please support httpx 0.27.0? Seems like there aren't any breaking changes.
Thank you :)

@hxtomer FYI https://github.com/frontegg/python-sdk/pull/132


Work around xtensa deadlock

Fixes (works around) #1449
This PR is intended as a temporary workaround until a proper solution can be found. This is unnecessary and wasteful on single-core MCUs, and also probably wasteful on dual-core ones. As dirbaio explained, esp-hal should probably provide a specialized executor implementation for dual-core Xtensa CPUs that maybe only disables interrupts without a complete cross-core lock.
Hacky and probably shouldn't be merged.

How does this fix it? Even if you re-disable interrupts, the interrupt can fire during the waiti, right?

The whole point of this patch is to prevent a race condition in the critical section implementation. Disabling the interrupts after wakeup means it's no longer possible for an interrupt handler to trigger while the core is in the process of exiting the critical section. It is no longer possible to try to lock the cross-core lock at the same point as the exiting critical section tries to release it.

Interestingly, this doesn't work. It reduces the likelihood of the deadlock, and in fact there is no more deadlock I can see, but the CPU locks up at the rsil (in take 1) or the waiti (in take 2).


Cleanup and add more log options to user pages

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable
[ ] Documentation in docs/ or install-docs/ was updated, if applicable

@pajlada DB/login lookups are a little beyond my knowledge at the moment. I can revert the Twitch Logs option and work on it at a later date - as I currently don't have time. This was meant to just be a small pr in order to fix the horrible spacing on the current user page:

It's fine if you don't do the twitch logs part, but if you want some other logs to show up, the preferred method is still the one I posted in the previous comment

@pajlada I'm still a slight bit confused on how you wish for this to be implemented. How do you want the variables logs_link_template and logs_link_name to be implemented? Something similar to the contributors section?

Well now that overrustle is being shutdown, I'm going to close this and try and figure something else out. Might result in just removing the logs option or something similar


Schema: add diagnostic node and tagged edge kinds [phab:D1618]

Created by schroederc at 2017-05-04 19:33:07:

fromberger commented inline (context lost during migration) at 2017-05-04 19:40:35:
Perhaps include "human-readable".
Do we want to require these be UTF-8?
Any other constraints worth mentioning? (One line only, for example?)

fromberger wrote at 2017-05-04 19:40:35:
A few suggestions, but otherwise looks good.

fromberger accepted this revision at 2017-05-04 19:40:35

schroederc wrote at 2017-05-04 20:05:00:
More constraints

schroederc commented inline (context lost during migration) at 2017-05-04 20:05:01:
✓

schroederc closed via commit 0b0284d2d6b5190a74b819ec8e9fe6a109884836 at 2017-05-04 21:56:53


Can no longer update from repo

Hey, I recently tried to update (Packer Sync), and the packer update failed repeatedly.
After some digging, it seems like there was maybe a rebase of the main branch, which packer did not like. So, I went to the repo directory in packer, and tried to do `git pull --allow-unrelated-histories, so I could update from the main branch.
However, the auto merge failes
Auto-merging lua/copilot_cmp/init.lua
CONFLICT (add/add): Merge conflict in lua/copilot_cmp/init.lua
Auto-merging lua/copilot_cmp/source.lua
CONFLICT (add/add): Merge conflict in lua/copilot_cmp/source.lua
Automatic merge failed; fix conflicts and then commit the result.

Do I just need to uninstall and reinstall this plugin?

That's interesting, as I haven't run into any problems like that.
Just rm -rf the copilot-cmp directory wherever packer installs it, then packersync again. It should be this by default:
~/.local/share/nvim/pack/packer/{start or opt}/copilot-cmp

That fixed it, thanks.


Adding Nexcom supplied binary blobs for B116 and generating proper DTB

This finalizes support for Nexcom B116 (complete with a blinking light). We are adding Nexcom supplied binary blobs for u-boot and trust and starting to generate a proper DTB. In fact we're generating two DTBs -- one is what Nexcom provides and the other one (on top of the first) simply adds LED definitions.
This time -- I'm trying something new for LEDs on ARM (lets see if y'all like it ;-)) I'm actually calling the LED we need to use eve. That way -- we may even have a generic part in ledmanager that will blink whatever LED is called eve. This will cut down on configuration guessing -- and since we're the ones managing the DTB for those LEDs -- we may as well call them what we want.

Hey @eriknordmark -- can you please take a quick look so this can be tested/pushed?

@eriknordmark -- both eve-cloud as a name and making it always present (but a no-op where that's the case) are great ideas -- would love to implement them as a follow up and thus clean the ledmanager code up somewhat. I'll also move uno and RPi4 LEDs to the same naming convention.
Let me file a tracker story so I don't forget -- and then we can get this merged (once the tests pass) and I can work on the followup in the next sprint.
Sounds good?


fix(registry): use empty strings and not nil in config

In #1858, the LRU cache was activated for registry. This exposed
an issue with how config settings are handled by docker-registry -
specifically, it doesn't appear to handle the YAML nil (~) value
properly. In the config parser logic in docker-registry
(see: https://github.com/deis/docker-registry/blob/2d50c1c6f396ac68858135be05dbfe41fe1898e2/docker_registry/lib/config.py#L61),
values are expected to be strings, dicts, or non-existent. The default value
when an option exists but is unset is an empty string.
This commit changes the cache config settings in
registry to use an empty string instead of ~.
Additionally, this commit also ensures that deisctl starts cache
before registry to ensure the registry is using the LRU cache.
closes #2833

Code LGTM. I've provisioned a boatload of clusters since #1858 and I haven't seen this actual issue, but I do see how it could happen. Thanks for fixing this.

manually built deisctl and brought up platform, stopped cache and restarted the registry. The registry works fine either way (with or without cache), and explicitly starting the cache before the registry will ensure that users will end up with a cache-enabled registry.
Code LTGM

Thanks for testing. I'm going to make the change @gabrtv suggested and then merge.

Code LGTM, though I haven't tested the empty string change.

though I haven't tested the empty string change.

I think with @bacongobbler's manual test, we are good once Jenkins passes again.


How to choose model

Hi, is there a way to choose the model is used? currently I only know how to change the models by changing the max ram but inside of config.py there are references to other models (am particulary interested on phi-1_5).  Thanks for your work!

Found it. lm.config['instruct_model'] = 'phi-1_5' does it


TODO: 2015/06/24

1 . implement solid pddl parser to parse all domains.
2 . debug pdb

use typing information when instantiating actions.
there are too many instantiation available with pure strips without typing.

pdb has a bug in regression search.
need to read some of abstraction search or regression search to find a good way of building pdb.

parser is working fine!
let's go on to pdb. maybe building new domain is smarter way as regression search is completely different story.

running all domains parallel is working.
so, let's work for outputting into a single file.

done: output on single file.
todo: put them into a latex to output table in pdf.


Updating to version 1.19.4

Explain the feature
Cloth Config API

Ideal solution or implementation
I don't know.
[Optional] Alternative solutions or implementations
No response
[Optional] Other context
No response

i really hope, really hope this mod can continue update bcz this mod are very useful.

Can you take a look at the mod "e4mc"? It's pretty similar and might be what you're looking for.

Oh! My mod is only for fabric too, sorry for any confusion.


Support for partitioned cookies

As part of their third-party cookie crackdown, Chrome will start requiring partitioned cookies for content in an iframe at some point in the future. So far only Chrome and derived browsers support this, but according to my testing other browsers accept and ignore the Partitioned attribute, so it should be safe to add.
My current goal is to future-proof a library that serves Dash apps in iframes and requires session cookies, and without built-in support the simplest solution I can find is to monkey-patch werkzeug.sansio.response.dump_cookie 🙈
This functionality is effectively an extension of (and only relevant when) SameSite=None so I could imagine it being implemented as samesite = "None; Partitioned" (in the session cookie context, app.config["SESSION_COOKIE_SAMESITE"] = "None; Partitioned") if you feel a separate attribute (partitioned = True and app.config["SESSION_COOKIE_PARTITIONED"] = True) would be excessive.

True, doesn't seem to have a spec, though it's pretty simple. Most of the complexity comes in how it interacts with the other attributes, which I suppose Flask could choose to either restrict or just leave up to users.
It's enabled by default since Chrome 116 after a long trial period so seems unlikely to change, but I don't see that they've stated any particular date to start enforcing it.

The simplicity isn't the issue here, it's the lack of a spec.


Allow custom styles

Sets up a simple pass-through (no sanitation) of custom styles to the form-builder instance.

FYI @drewwills  @ChristianMurphy


NextJs Caching Issue

https://github.com/vercel/next.js/tree/canary/examples/ssr-caching
Seems not to work on the current Next JS Version
Getting this error on Home Page
(node:20872) UnhandledPromiseRejectionWarning: TypeError: argument entity is required
at etag (C:\xampp\htdocs\next-app\node_modules\etag\index.js:72:11)
at C:\xampp\htdocs\next-app\node_modules\cacheable-response\index.js:93:32
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:20872) 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:20872) [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.

Sorry for that, but I can't help since I'm not using Next.js on my use case and also never was the library intention.
BTW, take a look at https://github.com/vercel/next.js/tree/canary/examples/ssr-caching

The link which you have shared is the same.
which is not working.

ops, https://github.com/rjyo/next-boost is the link I wanted to share 🙂


Update lint configs / code style

Just pick a eslint configuration we will be confortable with...
What would be nice is to have a common code style for any IDE.

I suggest we use prettier with linted-stage and husky.
Option 1. listed here
.lint.staged.json
{
  "*.{js,json,css,md}": [
    "prettier --arrow-parens always --trailing-comma all --single-quote --print-width 100 --write",
    "git add"
  ]
}


Clean up intro to d0796r1

I cleaned up the definitions of affinity, binding, and the affinity problem.
I also fixed some syntax issues with inline code, right before the first code example.

Thanks for this improved text!

Looks good to me, thanks.

Thanks @AerialMantis !


fixing bug with respecting sentBuffer max size

Service clients have two configurable buffer sizes:

sentBufferSize - how many sent requests can be currently waiting for a response
pendingBufferSize - how many requests can be waiting to be sent.

The expected behavior is that when the sent buffer maxes out, subsequent calls to send don't send the requests but instead add them to the pending buffer.  Once responses for the currently sent requests start coming in, the client dequeues requests from the pending buffer and sends them until the sent buffer fills up again.
However a bug caused the client to totally ignore the max sent buffer size when dequeuing from the pending buffer, so the entire pending buffer is then sent.
this PR fixes that bug and ensures that the sent buffer max size is respected even when draining the pending buffer.

+1


 gets stuck on stale value after user input

Qwik Version
0.14.0
Operating System (or Browser)
Ubuntu/Firefox
Node Version (if applicable)
N/A
Which component is affected?
Qwik Runtime
Expected Behaviour
In this playground demo, we expect that each textarea stays in sync with each other and the <input> element, and is cleared when clicking "Reset"
Actual Behaviour
Using value={store.text} has a different issue where the initial state isn't reflected on the first render, but otherwise it seems like  a mix of both value and "content" are required, otherwise if only "content" is provided, it will no longer update after being typed in, when a different textarea/input/reset button triggers a change to the store. This doesn't seem intentional.
Additional Information
Related: https://github.com/BuilderIO/qwik/issues/2000

Working on a fix! i think the solution will be to make the value property to work during SSR! and discourage using the children


Event window.onpopstate is never fired

Version
3.0.1
Reproduction link
https://jsfiddle.net/bjb8ukb8/
Steps to reproduce
Set listener for window.onpopstate and navigate through VUE app using VUE router. Event is never fired. Demo: https://jsfiddle.net/bjb8ukb8/ Event popstate works correctly without VUE. Demo: https://jsfiddle.net/bzo67L32/2/
What is expected?
Event popstate must be fired.
What is actually happening?
Event popstate is not fired.

So when this event is not working there is no possible way to detect that user used back or forward button in browser. And I think VUE and VUE router do not offer any API to check it.
var lastHistoryLength = window.history.length;
window.onpopstate = function() {
  if (window.history.length == lastHistoryLength)
      console.log("User used back button");
  lastHistoryLength = window.history.length;
};

This code works well in clean javascript website - you can put it into console at e.g. http://example.com/ and then put location.hash="foo" and press back button or use location.history.back() and in console you will see "User used back button". But this code does not work in website using vue+vue router.

This is normal, as router links trigger js navigation and not regular browser navigation. That's why it does appear when clicking the back and forward button (https://developer.mozilla.org/en-US/docs/Web/API/WindowEventHandlers/onpopstate)


Upgrade to fashion page:add different section to the page

Added different section to
changes page video
changes photo

https://github.com/user-attachments/assets/e5ee4b7d-5b4d-464f-98e1-6724341e11ed
earlier befire changes

### 1. Fashion Trends

Section Title: Fashion Trends
Image:

Explanation: This section discusses the current fashion trends, highlighting the resurgence of vintage styles, eco-conscious fabrics, and bold colors. The image visually represents the dynamic nature of fashion.

2. Iconic Designers

Section Title: Iconic Designers
Image:

Explanation: This section celebrates designers who have significantly impacted the fashion industry, such as Coco Chanel and Alexander McQueen. The image symbolizes the creativity and innovation these designers bring to fashion.

3. Sustainable Fashion

Section Title: Sustainable Fashion
Image:
![Sustainable Fashion Image](https://images.unsplash.com/photo-1600585154360-0d7cb3

Raise new pr and do relevant changes

closing due to lack of response


Revert part of #5339

Motivation
Reverts part of #5339
Changes
PutUvarint from standard library and github.com/multiformats/go-varint do not behave exactly the same. With Go 1.20 to the stdlib implementation was fixed to detect short reads, but in contrast to github.com/multiformats/go-varint it will still not return an error when decoding non-minimal encodings of integers.
Test Plan
n/a
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed
[x] Update changelog as needed

bors merge


Missing info, error, ... in TS declaration file

Hi,
thanks for the great component! Since the last update I get the following error:
ERROR in /app/src/modules/validation/ScanList.vue
147:17 Property 'info' does not exist on type '(message: string, options?: VuetifyToastObject | undefined) => void'.
146 |

147 |     this.$toast.info('Files were uploaded... please wait until processing has finished');

I looks like the declaration for the info, errror,... functions is missing in the added TS file.
Thanks!

@Jnig Hi,
Thanks for submitting the issue. I can see the problem here, as these are dynamically created. Though it might be possible to write interface for default methods, I'm not sure about the best approach to write an interface for everything. If you have any ideas how to make TS happy, you're welcome to comment or create a pull request.
The only solution that comes to mind is to write:
declare module 'vue/types/vue' {
  interface Vue {
    $toast: any
  }
}

Can you please try to modify index.d.ts in the package directory and check if this approach will solve your problem?

thanks for the fix!! 👍

app.js:142552 [Vue warn]: Unknown custom element:  - did you register the component correctly? For recursive components, make sure to provide the "name" option.
(found in )


Stop listening to the legacy topics

This PR was successfully deployed to production by CircleCI build 221 at 2017-05-22 16:56 BST.


[camera]rename dispatchQueue to captureSessionQueue

Rename the queue to be aligned with the proposal.
I am keeping this PR small and only scoped to renaming.
Since it's just renaming, I think it's exempt from version bump and unit test
Issue:
https://github.com/flutter/flutter/issues/96429
No version change: Because it's only renaming
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.*
[x] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.*
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

I think it's exempt from unit test

You're right, but you should still get a test exemption from @Hixie in Discord.

If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

@stuartmorgan we usually still do a CHANGELOG NEXT when the version isn't bumped?  Or do you not bother on little changes?

@stuartmorgan we usually still do a CHANGELOG NEXT when the version isn't bumped? Or do you not bother on little changes?

I moved us to a policy of generally requiring a CHANGELOG change for everything—see the last sentence of https://github.com/flutter/flutter/wiki/Contributing-to-Plugins-and-Packages#changelog for my rationale—which is why publishable is strict about it. But it's kind of a trial; if it turns out to be annoying in practice we can easily relax the policy and change the tooling to only require it when the version changes.

In this case I would lean toward:
## NEXT

* Minor internal code cleanup.

or something like that. Mostly because if there were some subtle bug introduced by the rename that we didn't notice until the next camera release, it would make it easier for us to realize that there would be two PRs to go look at, rather than potentially being misled by the CHANGELOG and looking at only the last change.

test-exempt: code refactor with no semantic change

@stuartmorgan updated the changelog. ptal thanks


Add ipBlock support for ingress rules in weave-npc

Implement https://github.com/weaveworks/weave/issues/3168
A new iptables rule will be generated for each NetworkPolicy with IPBlock peer just like others.  All rules will share the same ipset if NetworkPolicies except same CIDRs/IPs from IPBlocks.
Since external traffic is masqueraded by rules written by kube-proxy, ipblock based network policies can't be implemented by adding single rules in WEAVE-NPC-INGRESS chain like other policies.
IPblock based policies have to be applied before forwarding and destination nodes need to trust packets which src IP is one of weave bridges'. Rules below are added to Filter table.
-N WEAVE-NPC-INGRESS-IPBLOCK
-A WEAVE-NPC-INGRESS -m set --match-set weave-bridges src -m comment --comment "packets forwarded from weave bridges are safe" -j ACCEPT
-A WEAVE-NPC-INGRESS -j WEAVE-NPC-INGRESS-IPBLOCK

And, a new rule will be added to chain WEAVE-NPC-INGRESS-IPBLOCK when a new policy is created. Such as,
-A WEAVE-NPC-INGRESS-IPBLOCK -s <IP_ADDRESS>/32 -m set --match-set weave-LxTLCYBhd(0L*JS+fQ1Yt/IV7 dst -m comment --comment "cidr: <IP_ADDRESS>/32 -> pods: namespace: ffca51bb048a34684bfb905120f663c1f, selector: " -j ACCEPT

All IPs exposed on weave bridges are saved in ipset weave-bridges . It is important to keep weave-bridges up to date when nodes added or deleted, even when IP changed. I think the best way is to watch router changes, and get peer bridge IPs from ipam or router, then modify the ipset. But, this is too difficult to me because it causes too many changes in weave core modules. I choose a simpler way to achieve this, that is to save IPs in configmap weave-net after they are exposed by kube-peers. weave-npc will watch all pods created by DaemonSet weave-net and update the ipset using bridge IPs saved in configmap weave-net.
However,  packets send from nodes to pods will bypass all policies. The following rules have to be added to Filter table to prevent these packets(<IP_ADDRESS>/17 is the pod CIDR).
-N WEAVE-NPC-LOCAL-INGRESS
-A WEAVE-NPC-LOCAL-INGRESS -j WEAVE-NPC-DEFAULT
-A WEAVE-NPC-LOCAL-INGRESS -j WEAVE-NPC-INGRESS-IPBLOCK
-A WEAVE-NPC-LOCAL-INGRESS -j NFLOG --nflog-group 86
-A WEAVE-NPC-LOCAL-INGRESS -j DROP
-A OUTPUT -d <IP_ADDRESS>/17 -m state --state NEW -j WEAVE-NPC-LOCAL-INGRESS

If packets explicitly permitted by NetworkPolicy are only accepted, LivenessProbes and ReadinessProbes with type HTTPGet or TCPSocket will not work. We can filter and accept packets sent from kubelet by matching --pid-owner. It also needs to watch pid of kubelet to keep the rule up to date when kubelet restarted. I'm not very sure whether it is a right way since it is complicated and not very safe. Instead of adding a pid based rule and watching kubelet, an option trust-weave-bridges is provided for weave-npc . Chain WEAVE-NPC-LOCAL-INGRESS will keep empty if trust-weave-bridges is set to true. To keep all probes working, this option should be true.

I tested it between 2 k8s clusters. All traffic is not masqueraded because I exposed IPs in  <IP_ADDRESS>/16 for each weave bridge and assign IPs in <IP_ADDRESS>/17 and <IP_ADDRESS>/17 for pods in different clusters.  It is my scenario. I'm so sorry that I didn't test in the scenario you mentioned.

I'm trying to fix my code.

@brb I found that is difficult to apply IP block policies to external traffic. The way what I found is to apply all policies with IP block before forwarding for both external traffic and traffic from hosts in the cluster. So, packets received with any weave bridge IP as src is safe and we can trust weave bridges in FORWARD chain. What do you think about this solution?

packets received with any weave bridge IP as src is safe and we can trust weave bridges in FORWARD chain

Unfortunately, that would allow us to access protected services from any node.
However, we are currently considering to remove the MASQ rule for external traffic, so the original src IP would be kept. Would it help for your implementation?

-A OUTPUT -d IP_RANGE -m state --state NEW -j WEAVE-NPC-LOCAL-INGRESS
-A WEAVE-NPC-LOCAL-INGRESS -j WEAVE-NPC-DEFAULT
-A WEAVE-NPC-LOCAL-INGRESS -j WEAVE-NPC-INGRESS-IPBLOCK
-A WEAVE-NPC-LOCAL-INGRESS -j NFLOG --nflog-group 86
-A WEAVE-NPC-LOCAL-INGRESS -j DROP

Thanks for the reply.
I think above rules can keep traffic from nodes safe.

However, we are currently considering to remove the MASQ rule for external traffic, so the original src IP would be kept. Would it help for your implementation?

When accessing a service IP, external traffic is masqueraded by rules owned by kube-proxy. It is not enough to just change weave.

Sorry for taking some time to review. I'm currently trying to better understand all implications of the ipBlock implementation to weave-npc. Shortly, I will review your PR.
Meanwhile, have you tried to implement some tests (ideally - integration ones) for the feature?

Sorry for the late reply since Chinese new year holiday. I will write a brief to explain how I implement this feature as well as tests in scenarios below.

kube-proxy masquerade all traffic
within/without excepted CIDRs
internal/external traffic
within/without protocol
Pod on same/different hosts
NodePort
port proxy
for legacy k8s
ipalloc-range is not defined
for Probes

You can prevent the kube-proxy snat if you add spec":{"externalTrafficPolicy":"Local"} to a nodePort service definition
You can prevent (as a test for now) the weave snat using my script, see https://gist.github.com/mrdima/e0098308f2351e90132c7cf0e4fa460c

@kitt1987 Could you squash your commits, so that npc/ipblock.go would be in a separate commit? I'd like to cherry-pick it for egress policies. Thanks.

@brb I've squashed them.

@kitt1987 Thanks again for your contribution. I've applied some changes from your patch - https://github.com/weaveworks/weave/commit/9769c8d5b905808e0363f42506c4af19c275708e.
However, the tracking of bridge IP addrs and the proposed chains introduce a big complexity, which for the majority of use cases is unnecessary. Also, the "packets forwarded from weave bridges are safe" constraint is not compliant with the k8s netpol spec.
Therefore, I'm closing this PR in favor of https://github.com/weaveworks/weave/pull/3367 which treats ipBlock as any other selector.


Does not pack information to alpha channel properly

Trying to use this tool to generate mask maps for HDRP but the alpha packing completely fails

Any chance of getting this fixed?

This is the only feature I downloaded this asset for xD

Same here lol. Struggled for almost an hour until I figured out it's not packing the alpha channel correctly :/


Widgets for simultaneous dual metrics analysis

Feature Description
Plotly scatterplot widgets with functionality to select metrics for axes and hue from model parameters
Why this feature?
Great way to find pareto-optimum decisions in case of metrics trade-off
Additional context
No response

Creat PR for this issue: https://github.com/MobileTeleSystems/RecTools/pull/140


Prepare new patch release 1.1.4

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.422%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
963

Relevant Lines:
1278

💛  - Coveralls


Split create-package out of libpak

Describe the Enhancement
We need to split create-package out into its own repo and have it take a dependency on libpak, instead of being included with libpak. This will make it more flexible. It should also enable us to have actual releases of create-package, so it can be installed w/out requiring a Go SDK. It should also more easily facilitate some documentation on the tool.
Motivation
See above.

What is the relationship of create-package and https://github.com/paketo-buildpacks/jam, they looks has the same functionalities?

You are correct in that there is overlap between the two tools, and there are primarily just historical reasons for why we have both. There are some minor differences between them so it wouldn't be a drop-in replacement to move from one to the other. Down the road, we'd like to only have one of these tools but we haven't scoped out how much work it would be to switch.

Just to chime in, if this is done the create-package tool should work without an internet connection (ie not try to install libpak at runtime). Right now the jam utility will run go install packit as part of its build process.

@braunsonm FYI, I've started this work see https://github.com/paketo-buildpacks/libpak-tools?tab=readme-ov-file#libpak-tools-package-create
Right now, it will function exactly as it does presently. So if you're able to use create-package in an offline environment then it will keep working that way. I'm not sure off hand as we only run it on Github actions which is online. If it does not work in an offline env, feel free to open an issue over on the libpak-tools repo and request it. Right now, we're focused on moving existing functionality into that repo, but when we catch up we'll look at adding new features too.

Thanks @dmikusa I'll give it a try.
We are using the current create-package offline so as long as it maintains that functionality we should be good and I support moving it out and making it easier to actually acquire (without a go install)

Awesome. Yes, when we hit a release point. I'll start cutting and publishing releases of the tool on Github. For now, go install is the way to do it.

Unfortunately I'm not seeing these tools as a direct replacement. Unless I'm missing something (the docs are wrong) the equivalent command is libpak-tools package bundle which fails on the same buildpack that create-package works with (references buildpack which is not present).
Additionally it does not support output destination directories like create-package does.
I could raise issues on libpak-tools if you want.

This is done.


test,hack: Refactor the e2e package to use the deploy metering package.

Overview:
This would refactor the e2e package to handle both deploying metering and run the reporting tests. This PR adds a deploy framework that's in charge of ensuring all of the metering resources are ready to proceed to run the reporting tests and teardown after the testing phase has completed.
It's important to note that the teardown method for the deploy framework calls a bash script, so now the default behavior for when tests complete is to store logs first, then output the test results.
TODO:

[x] Update hack/ scripts to handle make e2e-local. These values can be hardcoded for now as there's only one MeteringConfig that's being tested
[x] Log test output (junit reports)
[x] Pass an overall testing directory to the deploy framework
[x] Log resource and containers logs to a tmpdir/specified path + random prefix
[x] Update testInstall to respect the defer closure call
[ ] Make sure that the teardown method doesn't error so deploy.Uninstall() is run

Follow-up PRs:

Pass clientsets to reportingframework.New instead of that method creating the clientsets explicitly
Support a partial install of metering
Support running tests on an existing namespace
Support validating storage spec without installing metering.

I think I covered the main functionality of the existing e2e process. The only thing that I think needs major work is the testhelpers.NewMeteringConfig(...) function as most of those values are hardcoded (storage, resource limits, images).
Not sure what the best approach is for that function, as we'll have a better idea of what it's going to look like once we add more MeteringConfig test cases.

/retest

Not sure what the best approach is for that function, as we'll have a better idea of what it's going to look like once we add more MeteringConfig test cases.

probably not using a function but just defining struct literals is best honestly.

@chancez I agree, I'll update to use a literal - I was mainly worried about the length of the test table and the general readability of the TestMultipleInstalls function.

@timflannagan1 We can also define the variables separately from the test tables and then just use them as variables.

/lgtm
/approve


Fix bug: Changed 'VALUE' to 'value' for consistency

Proposed changes
Summarize your changes here to communicate with the maintainers and make sure to put the link of that issue
Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[x] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the commit for DCO to be passed.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Dependency

Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:
This fixs #4176 .
Please review the changes carefully and confirm that the adjustment from 'VALUE' to 'value' is consistent and doesn't introduce any unintended side effects. Thank you for your review!

Can you do a full search and replace for this? It seems like almost all our experiments files in the mkdocs/docs/ have this, would be good to fix them all in one PR.

I search in the mkdocs/docs and there is only one more this
I've update the branch PTAL.

@RipulHandoo there's surely a lot more

@RipulHandoo there's surely a lot more

I'll make changes right away.

@gdsoumya
I replaced all the occurrences of "VALUE" to "value".
But there are some other changes as well.
PTAL. if they are alright or not.

LGTM

@gdsoumya
I am signing off the commits.
But still DCO is failing.
Any suggestions

@RipulHandoo try following the steps here https://github.com/litmuschaos/litmus/pull/4253/checks?check_run_id=18290456286

@RipulHandoo try following the steps here https://github.com/litmuschaos/litmus/pull/4253/checks?check_run_id=18290456286

I tried everything on my end.
Should i close this request and create a new PR for this issue?

I tried everything on my end. Should i close this request and create a new PR for this issue?

No need, have manually set it to pass.


Protobuf minimum unsigned integer (u32) vs UResource & UEntity id size (u16)

Hi there :wave:
I noticed when serializing the UURI to micro form, we do some bit shifts and casting to get the desired 16 bits written for the UResource and UEntity ids.
I suppose it's possible based on what I see here and here that we could form ids which are larger than the allotted 16 bits when serializing.
Perhaps we should explicitly check to make sure we can fit the ids within the allotted bits, e.g.
const UENTITY_ID_LENGTH: usize = 16;
const UENTITY_ID_VALID_BITMASK: u32 = 0xffff << UENTITY_ID_LENGTH;
const URESOURCE_ID_LENGTH: usize = 16;
const URESOURCE_ID_VALID_BITMASK: u32 = 0xffff << URESOURCE_ID_LENGTH;
// ...
        // URESOURCE_ID
        if let Some(id) = uri.resource.as_ref().and_then(|resource| resource.id) {
            // this is new -- start
            if id & URESOURCE_ID_VALID_BITMASK != 0 {
                return Err(SerializationError::new(format!("UResource id larger than allotted 16 bits: 0x{:x}", id)));
            }
            // this is new -- end
            cursor.write_all(&[(id >> 8) as u8]).unwrap();
            cursor.write_all(&[id as u8]).unwrap();
        }

        // UENTITY_ID
        if let Some(id) = uri.entity.as_ref().and_then(|entity| entity.id) {
            // this is new -- start
            if id & UENTITY_ID_VALID_BITMASK != 0 {
                return Err(SerializationError::new(format!("UEntity id larger than allotted 16 bits: 0x{:x}", id)));
            }
            // this is new -- end
            cursor.write_all(&[(id >> 8) as u8]).unwrap();
            cursor.write_all(&[id as u8]).unwrap();
        }

And these are the accompanying tests which pass with the code changes above:
    #[test]
    fn test_uentity_id_greater_than_16_bits() {
        let uri = UUri {
            entity: Some(UEntity {
                id: Some(1 << UENTITY_ID_LENGTH),
                version_major: Some(254),
                ..Default::default()
            }),
            resource: Some(UResource {
                id: Some(19999),
                ..Default::default()
            }),
            ..Default::default()
        };

        let uprotocol_uri = MicroUriSerializer::serialize(&uri);
        assert!(uprotocol_uri.is_err());
        assert_eq!(
            uprotocol_uri.unwrap_err().to_string(),
            "UEntity id larger than allotted 16 bits: 0x10000"
        );
    }

    #[test]
    fn test_uresource_id_greater_than_16_bits() {
        let uri = UUri {
            entity: Some(UEntity {
                id: Some(29999),
                version_major: Some(254),
                ..Default::default()
            }),
            resource: Some(UResource {
                id: Some(1 << URESOURCE_ID_LENGTH),
                ..Default::default()
            }),
            ..Default::default()
        };

        let uprotocol_uri = MicroUriSerializer::serialize(&uri);
        assert!(uprotocol_uri.is_err());
        assert_eq!(
            uprotocol_uri.unwrap_err().to_string(),
            "UResource id larger than allotted 16 bits: 0x10000"
        );
    }

Perhaps a more thorough solution is to create some sort of internal-to-the-Rust-library version of the UURI that can ensure that this does not occur in the first place? But I'm not familiar enough yet to have found other instances like this.

After reading a bit more through the spec for URIs and uSubscription, I am kinda considering some way to "front load" some of the verification and safety with some sort of builder for URIs.
I'm still thinking about how that might look. Might post some skeleton here later.

Okay, I'm looking at this again and reading the spec specifically this part:

All fields of micro UUri MUST be populated

Does that mean if the UEntity id or UResource id are empty we should fail to serialize? i.e. return a SerializationError?
Tagging in @stevenhartley, @sophokles73 for some guidance.

Does that mean if the UEntity id or UResource id are empty or overflow 16 bits we should fail to serialize? i.e. return a SerializationError?

That is my understanding.

Not sure what you mean by "empty", Entity Id of 0 is the uSubscription service and resource id of 0 is the fixed rpc.response topic

Yup, you're right. My bad.


chore: add stale config

What ?
I would like to introduce stale bot to this repositorry (and later the others of the visjs family). This means issues that are open for 60 days or longer get a stale warning and than get closed after 14 days.
Bugs and security problems will not be closed automatically.
Why?
In my experience the number of issues are always growing. The main problem here are the feature-requests that never get implemented and questions that nobody whats or can answer. This issues pile up and glutter the maintenance process. A project becomes almost unmaintainable if there are more than 30 open issues.
What do you folks think?

@Thomaash @yotamberk and every one else here: Could you please review this, I would like to introduce this to the other repositories in the visjs-family as well...If you like it..

Seems like a good idea to me.

Well, I understand what you're saying but sometimes I like to have feature request issues. I don't always have the time to get to implement them (okay okay... I seldom get the time to implement any features at all...) but I do like having a bank of good feature request ideas that are desired by the community. Is there a way maybe to ignore this bot rule for issues with a tag of feature request or something like priority feature?

Or maybe generic never-stale?

Yeah, seems legit too

Is there a way maybe to ignore this bot rule for issues with a tag of feature request or something like priority feature?

I fully understand! My idea was that people still can add :+1: :-1: to closed feature requests. If a feature request gets closed and a lot of people show interest we just can reopen it!?
I'm also not sure what the best way of dealing with feature-requests is. But we must be carefull not to glutter the issues with requests that will propably never get implemented...(we had this problem with vis)

We can have the rule on feature requests but once interest is high on an issue, a label of never-stale should be added by us to that feature to stop the bot from closing it again

@yotamberk I've added a never-stale label. It was a good idea! Please review!

I just enabled the stale bot for this repository: https://github.com/organizations/visjs/settings/installations/1340297


Add Robotron Bildungszentrum

The Robotron Bildungszentrum (Learning Center) offers training and retraining for IHK (Chamber of Industry and Commerce) certified IT specialists for software development and for system integration.
We would be grateful if Jetbrains could provide educational licenses for our trainees.
https://www.robotron-online.de/

@aramiscd Regrettably, I have to close the request without merging, because this organization is a training center, not a college, nor a university. Please ensure that you are familiar with this repository rules located at the bottom of this page.
Please apply for an appropriate licensing option (which may also be free) at https://www.jetbrains.com/community/education/#courses.
Thank you for your understanding!


Added new Asterisk Events to AMI Manager.

Here we go. Third time is the charm as they say.
Event handlers for AttendedTransfer, BlindTransfer, BridgeEnter, BridgeLeave, BridgeCreate and BridgeDestroy, and added a gitignore-file.

Looks good!

Just as a side not for future improvement. Comments for events need to be made a standard for all new contributions.


Use JSON.stringify instead of template strings for formatting

Hi @brandonaaron. Thank you for taking action on this issue. I just tried your changes locally and it looks good. Unfortunately it is necessary right now to re-map the errors, but no matter the implementation, now it's possible to do TDD with WTR and QUnit, which is awesome.
I just changed the actual/expected casting using JSON.stringify as we often compare structures and this makes the diffs way more readable.
It would be very nice to have a release with the improvements soon, so i can finally start migrating away from karma.
Thanks

#5 ended up being the preferred approach and includes the JSON serialization of actual and expected props.


⚠ Bofrost.at has degraded performance

In 0b909a2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 964 ms

Resolved: Bofrost.at performance has improved in a4b9bf1.


Hybrid adapter. Added docs for In-Image format

Added docs for In-Image format

part of 4.12 going out now


Use unified version names from pubspec.yaml

version name is currently used for android builds, but not for iOS

Fixed with #2


Implement a large modelbinding/validation benchmark

We need a larger benchmark using more complex/large validation and model binding.

@rynowak Shouldn't this be in the Benchmark or perf repo?

Did this already here: https://github.com/rynowak/mvc-sandbox/tree/master/workloads/BigModelBinding
As discussed will be moving all of these benchmarks to aspnet/Performance


All text changed to 'cmdlet deprecated'

Per email request

Docs Build status updates of commit 92c6d68:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Import-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Remove-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-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 a6f6af7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Import-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Remove-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-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


Create Project Setup Area

With easy to click ON/OFF modules like Randomizations, Adverse Events, etc. Clicking these will allow editors to then go edit the schemes.

Related to #485.

Note from @mrueschman, provide a bit more information on what the modules do. One line explanation, then with link to docs for more reading.