Proposal: make ament test return non-zero on test failure

Following discussions on other issues (e.g., #139 and ros-infrastructure/ros_buildfarm#367), I'd like to propose a change in the behavior of ament: Make ament test return non-zero if:

there was a failure in the build step (the test step first runs the build step); or
there was a failure to invoke a test; or
there was a failure reported by a test that was successfully invoked.

At present, ament test returns non-zero only for the first two conditions, but not the third.
Rationale: ament test is a step that aggregates underlying steps and as such it should follow the common pattern of ORing together the return codes of those underlying steps to produce its own return code.
Pro:

It's easy to check whether anything went wrong with the test step without having to subsequently run ament test_results (this command does return non-zero if any of the results include test failures).

Con:

The caller can no longer distinguish based on the return code between failure to invoke a test and a test that reports a failure.

(Note that you can still distinguish build failure from test failure by run ament build and ament test separately.)
My opinion is that the benefits of the pro outweigh the costs of the con. Thoughts?
p.s. I'm proposing this change only for ament, which is a new tool that we can fairly freely modify. The same change could in principle be made to catkin, but there seems to be risk of disruption in doing that.

For any kind of automation it is crucial to distinguish failures to run something vs. some tests returning non-zero return codes. In my opinion this it is a strict requirement for our tools to satisfy this requirement. With the proposal it is not possible anymore to identify if the invocation of test failed for any reason. Nor is there any other way to achieve that (e.g. by invoking more commands). That prevents those use cases to operate correctly (e.g. sending a notification email in case tests fail, but not when something in the infrastructure / invocation failed) which I consider an unacceptable "cost" which can't be outweigh by any benefit.
On the other hand with the current state your use case is easily possible by invoking two two commands.
There is an alternative which continues meeting the requirement stated above as well as your desire to get a non-zero return code for any kind of failure. The ament test command could offer an argument to choose the desired return code behavior.

There is an alternative which continues meeting the requirement stated above as well as your desire to get a non-zero return code for any kind of failure. The ament test command could offer an argument to choose the desired return code behavior.

Ah, that sounds like the perfect compromise! How about this change instead: change the default behavior of ament test according to my earlier proposal, but simultaneously offer an option to produce the current behavior? Automated systems would supply the option to get the current behavior, but regular users who don't supply that option would get the new behavior.

I am not sure if this is relevant here, but I do remember that we decided to ignore the return code in the first place because all our successful builds with test failures were marked as failed on the buildfarm (e.g. ). So https://github.com/ament/ament_tools/pull/110/files has been made so that we could make the difference between a failing job and a job with failing tests.

:+1: I don't mind what the default behavior is as long as the mandatory use cases are still possible.

Fixed by #141.


getting Graphql errors when running docs server locally

Problem
when starting docs server locally, keep seeing the error below:

Steps to Reproduce

go to docs
npm start

Acceptance Criteria

either fix the error, or perhaps deprecate that file if it's no longer used
(optional) is there a way we can capture the breaking changes earlier and reject commits before they are committed

Mac has addressed this. closing


Need test run command in Getting Started

https://mochajs.org/#getting-started
Problem: getting started has you install mocha locally, make a test dir, and write a test, but doesn't show you how to run it nor how to set up npm test.
Suggestion: instruct users to add a test script to package.json such as:
If mocha is installed locally:
"scripts": {     "test": "./node_modules/mocha/bin/mocha"   },
If mocha is installed globally:
"scripts": {     "test": "mocha"   },
And then run it with $ npm test
Expected: some instruction on how to run tests after installing mocha.
Current:

See also https://github.com/mochajs/mocha/issues/2282#issuecomment-253162837


GitVersioning may interfere with Markup Compilation for WPF applications and cause assembly load exception at runtime

This may not be a common scenario, and it has a simple workaround, so may not need a fix. I am logging it here in case other people encounter it.
Symptom: System.IO.FileLoadException thrown when wpf is trying to load resources in InitializeComponent
Background:

GitVersioning sets the AssemblyVersion property to something like "14.1"
MarkupCompilePass1 WPF target picks up the AssemblyVersion property and inserts it into the generated .g.cs based on the XAML:

        public void InitializeComponent() {
            // ...
            System.Uri resourceLocater = new System.Uri("/foo;V14.1;component/bar.xaml", System.UriKind.Relative);
            // ...
        }

At runtime, when this method gets called, it first tries to match the assembly against loaded assemblies; however that fails in this case as it tries to match against the full version (<IP_ADDRESS>)
Because it couldn't find the assembly (even it if was already in memory), it tries to load it. Most of the times that will succeed, but in some cases (e.g. the assembly is located somewhere else, not under the probing path) you will encounter this problem

Workaround: Insert the following snippet in the affected projects
  <Target Name="ClearAssemblyVersionBeforeMarkupCompilePass1" BeforeTargets="MarkupCompilePass1">
    <PropertyGroup>
      <AssemblyVersion />
    </PropertyGroup>
  </Target>

This will clear up the AssemblyVersion right before the MarkupCompilePass1 target gets executed. This will cause the version not to be specified in the generated file, and it will successfully match the assembly against the version already loaded in memory

Thanks for reporting this, @adrianvmsft. We only just started setting the AssemblyVersion MSBuild property, and we could use a property by a different name if that avoids this problem. I'd like to understand it a bit better though. What makes specifying the assembly version problematic? If it is indeed the assembly version of the compiled assembly, shouldn't WPF still be able to find it?

It doesn't find the assembly in memory (it is already loaded) because it ends up comparing "14.1" against "<IP_ADDRESS>". I know, perhaps the comparison should succeed but it doesn't.
So it tries to load it using Assembly.Load. Usually that works, but in some cases it may fail (e.g. if the assembly is located somewhere else on the disk).
In that case you end up in a situation where the assembly is already loaded, but it tries to load it anyways and if that fails it throws exception.
I think it is a corner case - I encountered it with a VS extension that has WPF UI.

I see. I suspect that .NET considers versions to always have 4 components, but this project initializes the MSBuild property with only 2. If we force it to always be 4 components long, in effect like this:
<AssemblyVersion><IP_ADDRESS></AssemblyVersion>

Then that should resolve it. Do you agree?

I have confirmed that the CLR always considers that an AssemblyVersion has 4 integer components to it, regardless of how it is formatted in the AssemblyVersionAttribute constructor. So I'm preparing a fix so that the AssemblyVersion property in MSBuild always have four integer components in it as well.


The file reference for "OpenInSafariOperationTests.swift" is a member of multiple groups

Compiling a branch "swift/2.2" with Carthage I received following warnings:

*** Building scheme "iOS Operations" in Operations.xcodeproj
2016-08-29 06:44:56.802 xcodebuild[4079:113369] warning:  The file reference for "OpenInSafariOperationTests.swift" is a member of multiple groups ("Features" and "Features"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
2016-08-29 06:46:18.184 xcodebuild[4287:121264] warning:  The file reference for "OpenInSafariOperationTests.swift" is a member of multiple groups ("Features" and "Features"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.

Yeah, I've seen this too - I don't think it's a huge issue, but will have a look into it.


Create stresemanngymnasium.txt

@Furno221 I am sorry, I have to close the request without merging. The file path is incorrect, I can not guess which domain do you mean. Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with correct information. Thank you for the understanding!


installation: sphinx version fix

Signed-off-by: Lars Holm Nielsen<EMAIL_ADDRESS>

Deprecated by #103


Video Player plugin - support file of the application folder

Recently the plugin updated and new VideoPlayerController.asset(path) have been added, is it possible also to add new VideoPlayerController.file(path) to access the application's folder of saved videos ?
For example, my application is downloading videos from network and saves it in the application folder. I want to be able to load that video again via the Video Player.

cc @szakarias

cc @sigurdm

The video can already be played by using a file URL with the new VideoPlayerController.network('file://$path').
I agree we should probably rename .network => .uri or somesuch.

On further consideration, for alignment with Image we should probably have a .file() constructor...

@sigurdm You right, totally my fault of how I used the API .. thanks.

Hi!
Do you have any idea if we upload a video from assets ,does it play in ios!
for me its working fine on android but not on ios!

It should work...
If it does not could you open a new issue at https://github.com/flutter/flutter/issues/new , and describe more detailed what you do and what goes wrong.


test suite for all event sources

I think it would be good to write a suite of tests for all event sources and then just apply it to all of them.
Should remove some duplication and maybe motivate event source authors to actually write tests...
I don't know if there is a technique for this ... so could somebody nudge me in the right direction? I'd like to learn how to do this ..

I think you can do this with parameterized tests, like we do with things like the GeometryConverter.  You can define a test with a special decorator that contains all the classes you want to test on for example, and it will run that test with each class.  See https://docs.pytest.org/en/latest/parametrize.html  (and also the test code for GeometryConverter)

You can also separate the part that tests the resulting output into a function (not called test_x), that can then be called by each camera test.

Thanks .. I'll dig a bit into that docu ... always nice to improve my pytest-foo :+1:

Several event sources got removed from ctapipe and the remaining ones are tested against each other.


Updates to preprocessing script

Change the name of the script to be clean_n_split.py
Output  of the script is now csv rather than pickle
Took out hard coded path name that was accidentally left in
Changed function name from seasons to get_seasons
Removed the pickle processed data and replaced it with csv files

@voremargot there is a merge conflict on the data file, can you look into it? I couldn't merge it. Also, we don't fire or rain_cat anymore. Thanks!

I am merging it now for my work. @gauthampughaz  please review if you want.

@hatefr I am fine with the changes.


Changelog says jquery was removed but it's still there

Changelog says
    - jquery.js has been **removed** from widget.media, this means that you are
      now responsible for ensuring that jquery is loaded in your page prior to
      displaying the form (form.media).

But jquery is still loaded automatically:
https://github.com/yourlabs/django-autocomplete-light/blob/bc83aecdde2328e683b278149ff7cdce3ebf4065/src/dal_select2/widgets.py#L87

Hi, is there any chance you could make a release with this change in? Cheers!

Released in 3.5.1

Brilliant thanks!

Keep up the great work yall!
Le mar. 4 févr. 2020 à 12:01, Alex Nathanail<EMAIL_ADDRESS>a
écrit :

Brilliant thanks!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/yourlabs/django-autocomplete-light/issues/1130?email_source=notifications&email_token=AAAXDLGXFIVDITK5P7BVI5DRBFDHBA5CNFSM4J36PMM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKXGLGQ#issuecomment-581854618,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAXDLHQDYGXAWVIAIMM6ADRBFDHBANCNFSM4J36PMMQ
.


ability to use string data type for all parquet columns

would be great to have option to write all columns as STRING data type in the final parquet, instead of int..etc

yes I will consider adding this as it will make things faster as there will be no need for type detection for this case.


Kemintiri (G2 ADV)

text: Closed Session precisions
link: https://www.vekn.net/forum/rules-questions/79988-keminitiri-closed-session#106540

Done


Can not resolve packages under customized python package path

Language Server version: PyLance v2020.9.6
OS and version: Ubuntu 16.04
Python version (& distribution if applicable, e.g. Anaconda): python3.5

Expected behaviour
should be able to resolve python pacakge/module under my customized path /home/ziqi.liu/.extra_pkg/lib/python3.5/site-packages, given the config in .vscode/settings.json
    "python.autoComplete.extraPaths": [
        "/home/ziqi.liu/.extra_pkg/lib/python3.5/site-packages",
        "/home/ziqi.liu/.extra_pkg/lib/python3.5/dist-packages"
    ],
    "python.analysis.extraPaths": [
        "/home/ziqi.liu/.extra_pkg/lib/python3.5/site-packages",
        "/home/ziqi.liu/.extra_pkg/lib/python3.5/dist-packages"
    ],

Actual behaviour
could not resolve any package under /home/ziqi.liu/.extra_pkg/lib/python3.5/site-packages
Note
Given the above config in .vscode/settings.json, both Jedi and Microsoft options in python language server are able to resolve my customized packages

Does rolling back to Pylance 2020.9.5 fix the problem, or has this problem always occurred?

You can right click the extension in the extension's menu to install another version (if you hadn't done so before).

@jakebailey  the problem still exists when rolling back to 2020.9.5
BTW, I'm running macOS 10.15.6, connecting to remote Ubuntu 16.04, both sides have installed 2020.9.5, I'm not sure if it makes a difference,  but I think this only depends on remote environment.

Thanks for confirming. Can you provide some logs of the analysis? https://github.com/microsoft/pylance-release/blob/master/TROUBLESHOOTING.md#filing-an-issue
Also note that when working with a remote machine, the settings syncing can get a bit weird. Are you certain these settings are making it to the remote machine and aren't just being applied to your local machine? I'm guessing they are making it if MPLS/Jedi were working (as they read the python.autoComplete.extraPaths setting which should be declared in the same way to VS Code for syncing).
And just to confirm, those paths are on the remote machine, correct? Not your local machine? With a remote setup, Pylance (and most of VS Code) runs on the remote system.

here are the logs by enabling "python.analysis.logLevel": "Trace"
User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'LocalZMQKernel - experiment'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
User belongs to experiment group 'EnableIPyWidgets - experiment'
User belongs to experiment group 'DeprecatePythonPath - experiment'
User belongs to experiment group 'RunByLine - experiment'
User belongs to experiment group 'CustomEditorSupport - control'
User belongs to experiment group 'pythonaa'
Error 2020-09-24 12:19:42: Exception while attempting zmq : [Error: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /home/ziqi.liu/.vscode-server/extensions/ms-python.python-2020.9.111407/out/client/node_modules/zeromq/prebuilds/linux-x64/node.napi.glibc.node)
	at Object.Module._extensions..node (internal/modules/cjs/loader.js:1021:18)
	at Module.load (internal/modules/cjs/loader.js:811:32)
	at Function.Module._load (internal/modules/cjs/loader.js:723:14)
	at Function.t._load (/home/ziqi.liu/.vscode-server/bin/58bb7b2331731bf72587010e943852e13e6fd3cf/out/vs/server/remoteExtensionHostProcess.js:1070:268)
	at Function.i._load (/home/ziqi.liu/.vscode-server/bin/58bb7b2331731bf72587010e943852e13e6fd3cf/out/vs/server/remoteExtensionHostProcess.js:1039:981)
	at Function.n._load (/home/ziqi.liu/.vscode-server/bin/58bb7b2331731bf72587010e943852e13e6fd3cf/out/vs/server/remoteExtensionHostProcess.js:1036:303)
	at Module.require (internal/modules/cjs/loader.js:848:19)
	at require (internal/modules/cjs/helpers.js:74:18)
	at load (/home/ziqi.liu/.vscode-server/extensions/ms-python.python-2020.9.111407/out/client/node_modules/node-gyp-build/index.js:21:10)
	at Object.<anonymous> (/home/ziqi.liu/.vscode-server/extensions/ms-python.python-2020.9.111407/out/client/node_modules/zeromq/lib/native.js:6:43)
	at Module._compile (internal/modules/cjs/loader.js:955:30)
	at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
	at Module.load (internal/modules/cjs/loader.js:811:32)
	at Function.Module._load (internal/modules/cjs/loader.js:723:14)
	at Function.t._load (/home/ziqi.liu/.vscode-server/bin/58bb7b2331731bf72587010e943852e13e6fd3cf/out/vs/server/remoteExtensionHostProcess.js:1070:268)
	at Function.i._load (/home/ziqi.liu/.vscode-server/bin/58bb7b2331731bf72587010e943852e13e6fd3cf/out/vs/server/remoteExtensionHostProcess.js:1039:981)
	at Function.n._load (/home/ziqi.liu/.vscode-server/bin/58bb7b2331731bf72587010e943852e13e6fd3cf/out/vs/server/remoteExtensionHostProcess.js:1036:303)
	at Module.require (internal/modules/cjs/loader.js:848:19)
	at require (internal/modules/cjs/helpers.js:74:18)
	at Object.<anonymous> (/home/ziqi.liu/.vscode-server/extensions/ms-python.python-2020.9.111407/out/client/node_modules/zeromq/lib/index.js:3:16)
	at Module._compile (internal/modules/cjs/loader.js:955:30)
	at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
	at Module.load (internal/modules/cjs/loader.js:811:32)
	at Function.Module._load (internal/modules/cjs/loader.js:723:14)
	at Function.t._load (/home/ziqi.liu/.vscode-server/bin/58bb7b2331731bf72587010e943852e13e6fd3cf/out/vs/server/remoteExtensionHostProcess.js:1070:268)
	at Function.i._load (/home/ziqi.liu/.vscode-server/bin/58bb7b2331731bf72587010e943852e13e6fd3cf/out/vs/server/remoteExtensionHostProcess.js:1039:981)
	at Function.n._load (/home/ziqi.liu/.vscode-server/bin/58bb7b2331731bf72587010e943852e13e6fd3cf/out/vs/server/remoteExtensionHostProcess.js:1036:303)
	at Module.require (internal/modules/cjs/loader.js:848:19)
	at require (internal/modules/cjs/helpers.js:74:18)
	at Object.<anonymous> (/home/ziqi.liu/.vscode-server/extensions/ms-python.python-2020.9.111407/out/client/extension.js:24:302770)
	at n (/home/ziqi.liu/.vscode-server/extensions/ms-python.python-2020.9.111407/out/client/extension.js:1:124)
	at /home/ziqi.liu/.vscode-server/extensions/ms-python.python-2020.9.111407/out/client/extension.js:56:730603
	at processTicksAndRejections (internal/process/task_queues.js:94:5)
	at async d.zmqSupportedImpl (/home/ziqi.liu/.vscode-server/extensions/ms-python.python-2020.9.111407/out/client/extension.js:56:730570)]
> conda --version
> pyenv root
> python3 ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3.6 ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3.7 ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> ~/.extra_pkg/lib ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python2 ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> conda info --json
> /usr/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import jupyter"
> /usr/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import jupyter"
> /usr/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import notebook"
> /usr/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import notebook"
> /usr/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py jupyter kernelspec --version
> /usr/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py jupyter kernelspec --version
Python interpreter path: /usr/bin/python3
Starting Pylance language server.
> conda --version

I think the settings are sync correctly....I've tried to make some changes on remote .vscode/settings.json, and it did apply on VSCode immediately. (I'll try to run it on Ubuntu machine locally if I got a chance to get back to my office)
And those paths are on my remote machine for sure. All settings are configured with remote environment.

Those are the Python extension's logs. Can you post Pylance's logs? They are in the "Python Language Server" output window, not the "Python" output window.

oh sorry for that, here are the pylance log:
[Info  - 12:19:44 PM] Pylance language server 2020.9.5 (pyright a6a34d5b) starting
[Info  - 12:19:44 PM] Server root directory: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist
[Info  - 12:19:44 PM] No configuration file found.
[Info  - 12:19:44 PM] Setting pythonPath for service "infra-dataset-map": "/usr/bin/python3"
[Error - 12:19:44 PM] stubPath typings is not a valid directory.
[Info  - 12:19:44 PM] Assuming Python version 3.5
[Info  - 12:19:44 PM] Assuming Python platform Linux
[Info  - 12:19:44 PM] Searching for source files
[Info  - 12:19:44 PM] Found 117 source files
[Info  - 12:19:44 PM] Background analysis(1) root directory: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist
[Info  - 12:19:44 PM] Background analysis(1) started
Background analysis message: setConfigOptions
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: setFileOpened
Background analysis message: getSemanticTokens
[BG(1)] parsing: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (27ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/2and3/builtins.pyi (81ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/2and3/builtins.pyi (27ms)
[BG(1)] binding: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (2ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/typing.pyi (24ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/typing.pyi (9ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/collections/__init__.pyi (8ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/collections/__init__.pyi (5ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/abc.pyi (1ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/abc.pyi (0ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/2and3/_typeshed/__init__.pyi (8ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/2and3/_typeshed/__init__.pyi (1ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/third_party/2and3/typing_extensions.pyi (1ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/third_party/2and3/typing_extensions.pyi (1ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/io.pyi (7ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/io.pyi (2ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/types.pyi (5ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/3/types.pyi (3ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/2and3/math.pyi (2ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.5/dist/typeshed-fallback/stdlib/2and3/math.pyi (2ms)
Background analysis message: analyze
[BG(1)] analyzing: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py ...
[BG(1)]   checking: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (5ms)
[BG(1)] analyzing: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (5ms)
Background analysis message: getSemanticTokens
Background analysis message: resumeAnalysis
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange

I think you're still rolled back, can you go back up to the latest release?
It does seem like it's not doing anything in those folders. If you attempt to hover on something from the other files (say an imported value), can you show what the log says? Mainly checking to see if it's going there or not.

with latest build (2020.9.6), it seems it still do nothing with those folders.
I've added a lib installed from pip and can definitely be recognized by pylance, say, from aiohttp import request, and I can see pylance is analyzing them correctly
below are the logs when I just reload the window and open a python file:
[Info  - 12:49:39 PM] Pylance language server 2020.9.6 (pyright c52b78aa) starting
[Info  - 12:49:39 PM] Server root directory: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist
[Info  - 12:49:39 PM] No configuration file found.
[Info  - 12:49:39 PM] Setting pythonPath for service "infra-dataset-map": "/usr/bin/python3"
[Error - 12:49:39 PM] stubPath /home/ziqi.liu/code/infra-dataset-map/typings is not a valid directory.
[Info  - 12:49:39 PM] Assuming Python version 3.5
[Info  - 12:49:39 PM] Assuming Python platform Linux
[Info  - 12:49:39 PM] Searching for source files
[Info  - 12:49:39 PM] Found 117 source files
[Info  - 12:49:39 PM] Background analysis(1) root directory: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist
[Info  - 12:49:39 PM] Background analysis(1) started
Background analysis message: setConfigOptions
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: setFileOpened
Background analysis message: getSemanticTokens
[BG(1)] parsing: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (69ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/builtins.pyi (73ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/builtins.pyi (30ms)
[BG(1)] binding: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (2ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/collections/__init__.pyi (16ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/collections/__init__.pyi (5ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/_typeshed/__init__.pyi (8ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/_typeshed/__init__.pyi (1ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/third_party/2and3/typing_extensions.pyi (2ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/third_party/2and3/typing_extensions.pyi (0ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/typing.pyi (15ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/typing.pyi (7ms)
[BG(1)] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/math.pyi (1ms)
[BG(1)] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/math.pyi (1ms)
[BG(1)] parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/__init__.py (1ms)
[BG(1)] binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/__init__.py ...
[BG(1)]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client.py (50ms)
[BG(1)]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client.py ...

[BG(1)]   checking: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py ...
[BG(1)]     parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/io.pyi (3ms)
[BG(1)]     binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/io.pyi (2ms)
[BG(1)]     parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/types.pyi (4ms)
[BG(1)]     binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/types.pyi (1ms)
[BG(1)]   checking: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (45ms)
[BG(1)] analyzing: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (45ms)
Background analysis message: getSemanticTokens
Background analysis message: resumeAnalysis
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange

when I hover over a resolved symbal, say, request in from aiohttp import request, I can see pylance print out lots of things
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] parsing: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (30ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/builtins.pyi (78ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/builtins.pyi (25ms)
[FG] binding: /home/ziqi.liu/code/infra-dataset-map/tmp/compute_map_overlap.py (3ms)
[FG] parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/__init__.py (5ms)
[FG] binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/__init__.py ...
[FG]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client.py (30ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client.py ...
[FG]     parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client_exceptions.py (3ms)
[FG]     binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client_exceptions.py (2ms)
[FG]     parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client_reqrep.py (23ms)
[FG]     binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client_reqrep.py (6ms)
[FG]     parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/connector.py (18ms)
[FG]     binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/connector.py (6ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client.py (64ms)
[FG]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/formdata.py (4ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/formdata.py (1ms)
[FG]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/helpers.py (25ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/helpers.py (6ms)
[FG]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/streams.py (8ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/streams.py (6ms)
[FG]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/multipart.py (17ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/multipart.py (9ms)
[FG]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/cookiejar.py (6ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/cookiejar.py (2ms)
[FG]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/payload.py (5ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/payload.py (1ms)
[FG]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/payload_streamer.py (1ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/payload_streamer.py (0ms)
[FG]   parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/resolver.py (5ms)
[FG]   binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/resolver.py (0ms)
[FG] binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/__init__.py (196ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/_typeshed/__init__.pyi (5ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/_typeshed/__init__.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/third_party/2and3/typing_extensions.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/third_party/2and3/typing_extensions.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/typing.pyi (12ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/typing.pyi (8ms)
[FG] parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/http.py (2ms)
[FG] binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/http.py (1ms)
[FG] parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/http_writer.py (5ms)
[FG] binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/http_writer.py (1ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/collections/__init__.pyi (3ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/collections/__init__.pyi (3ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/collections/abc.pyi (1ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/collections/abc.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/json/__init__.pyi (1ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/json/__init__.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/json/encoder.pyi (1ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/json/encoder.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client_ws.py (3ms)
[FG] binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/client_ws.py (2ms)
[FG] parsing: /usr/local/lib/python3.5/dist-packages/multidict/__init__.pyi (1ms)
[FG] binding: /usr/local/lib/python3.5/dist-packages/multidict/__init__.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/abc.py (0ms)
[FG] binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/abc.py (2ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/abc.pyi (0ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/abc.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/warnings.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/warnings.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/traceback.pyi (1ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/traceback.pyi (2ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/types.pyi (3ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/types.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/sys.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/sys.pyi (3ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/__init__.pyi (1ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/__init__.pyi (4ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/coroutines.pyi (0ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/coroutines.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/log.py (2ms)
[FG] binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/log.py (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/logging/__init__.pyi (8ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/logging/__init__.pyi (2ms)
[FG] parsing: /usr/local/lib/python3.5/dist-packages/async_timeout/__init__.py (1ms)
[FG] binding: /usr/local/lib/python3.5/dist-packages/async_timeout/__init__.py (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/re.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/re.pyi (2ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/os/__init__.pyi (7ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/os/__init__.pyi (3ms)
[FG] parsing: /usr/local/lib/python3.5/dist-packages/yarl/__init__.pyi (3ms)
[FG] binding: /usr/local/lib/python3.5/dist-packages/yarl/__init__.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/urllib/request.pyi (8ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/urllib/request.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/events.pyi (14ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/events.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/futures.pyi (3ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/futures.pyi (2ms)
[FG] parsing: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/hdrs.py (1ms)
[FG] binding: /home/ziqi.liu/.local/lib/python3.5/site-packages/aiohttp/hdrs.py (1ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/math.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/math.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/http/cookies.pyi (1ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/http/cookies.pyi (0ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange

when I hover over some unresolved symbols from the package in my customized path, pylance output is weird, seems it's searching under std lib
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/_importlib_modulespec.pyi (3ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/_importlib_modulespec.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/base_events.pyi (18ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/base_events.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/locks.pyi (3ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/locks.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/protocols.pyi (1ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/protocols.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/queues.pyi (1ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/queues.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/streams.pyi (4ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/streams.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/subprocess.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/subprocess.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/tasks.pyi (4ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/tasks.pyi (1ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/transports.pyi (3ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/transports.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/concurrent/futures/__init__.pyi (1ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/concurrent/futures/__init__.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/concurrent/futures/_base.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/concurrent/futures/_base.pyi (2ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/unix_events.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/asyncio/unix_events.pyi (2ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/json/decoder.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/json/decoder.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/posix.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/3/posix.pyi (0ms)
[FG] parsing: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/_warnings.pyi (2ms)
[FG] binding: /home/ziqi.liu/.vscode-server/extensions/ms-python.vscode-pylance-2020.9.6/dist/typeshed-fallback/stdlib/2and3/_warnings.pyi (0ms)

my whole .vscode/settings.json is :
{
    "git.ignoreLimitWarning": true,
    "python.pythonPath": "/home/ziqi.liu/.extra_pkg/lib",
    "python.autoComplete.extraPaths": [
        "${cwd}/backend",
        "/home/ziqi.liu/.extra_pkg/lib/python3.5/site-packages",
        "/home/ziqi.liu/.extra_pkg/lib/python3.5/dist-packages"
    ],
    "editor.fontSize": 18,
    "python.analysis.extraPaths": [
        "${cwd}/backend",
        "/home/ziqi.liu/.extra_pkg/lib/python3.5/site-packages",
        "/home/ziqi.liu/.extra_pkg/lib/python3.5/dist-packages"
    ],
    "python.analysis.logLevel": "Trace"
}

my project root is /home/ziqi.liu/code/infra-dataset-map,
, and I have a .env under my proejct root dir, with
PYTHONPATH=/home/ziqi.liu/code/infra-dataset-map/backend

this is to make it resolve all sub modules under ${my_project_root}/backend/

Note that we don't support the ${cwd} specifier (nor does MPLS). Is that the code that isn't resolving? Or is it anything from .extra_pkg as well?
For backend, try specifying it relatively, i.e. write ./backend, as per our troubleshooting section on unresolved imports: https://github.com/microsoft/pylance-release/blob/master/TROUBLESHOOTING.md#unresolved-import-warnings

thanks for the tips regarding bakcend.   But some of the unresolved symbols also comes from .extra_pkg

I have a similar problem with PyLance v2020.9.6 (downgrading to 2020.9.5 solves the problem though). For me pylance ignores my actual conda environment.

@ocraft If you aren't using extraPaths, we'd appreciate a new issue as a setup with nothing configured at all should work out of the box and would differ. The changes made to fix extraPaths in 2020.9.6 should not have effected any path we pull from the interpreter (e.g., within the conda environment).

I was able to reproduce the issue on both v2020.9.6 and v2020.10.0. I believe this issue is that  that pylance does not support PEP 420, which became standard in Python 3.3.
It appears that when resolving imports pylance uses the first directory it finds that matches the module name. If it can not find an import in that directory it reports an error instead of looking for additional directories in extraPath that might contain parts of the module. Consider a python file:
from production import foo
from production import generated

Files production/foo.py and production/bazel-bin/production/generated.py exist.
If "python.analysis.extraPaths": [] then pylance can not locate the second import (as expected)
If "python.analysis.extraPaths": [ "bazel-bin"] then pylance can not locate the first import
If "python.analysis.extraPaths": [ ".", "bazel-bin"] then pylance can not locate the second import
If "python.analysis.extraPaths": [ "bazel-bin", "."] then pylance can not locate the first import
If "python.analysis.extraPaths": [ "bad" ] then pylance can not locate either the first or second import, this may be a seperate bug.

@onet-git It's not clear to me that it's related to the original issue; would you mind opening a new issue with a reproducer? Our import resolver is based on PEP 420, so these sorts of imports should work. Maybe the issue is in the nesting. You should never have to add "." as an extraPath, as the workspace root is implicitly added by default.

@liuzqt are there any symbolic links in your python.analysis.extraPaths? You may be having the same problem as me. Look: #131

@liuzqt Is this still not working in a recent release 9e.g. 2021.2.3)? Do these paths contain symlinks?

@savannahostrowski  sorry currently I don't have time to try it out, I'll update later once I test it.
A quick answer regarding symlinks: yes, it contains many symlinks.

Ah no worries! It's likely that the symlinks are the issue. We're currently tracking this on #131 so I'll close this as a duplicate issue.


Api rework

This is work in progress. Pull request is created just for the purpose of discussion on this approach.
Things to be revised:

Implementation of BufferDataSource, how to handle propagation of time components?
Make abstract Rate Generator for periodic functions to ease implementation of new
Is approach with prev and current time instant ok ?
Few sample implementations are provided in LoadGeneratorTest for 'look & feel'

Adding JavaDoc could help twofold:

If you cannot clearly describe meaning/purpose and usage of a certain field/method/class, it's probably unfinished or unnecessary.
Once clearly described, others can understand it easier.

More unit tests should be created.

Fix code comments and lets merge. I'll add improvements as issues

I'm merging. Let work on this code base.


ThemeConfig: Navbar items href validation error

🐛 Bug Report
I upgrade from 2.0.0-alpha.54 to 2.0.0-alpha.61, and get a validation error for the following config (which used to work before)
themeConfig: {
      items: [
        {
          href: '/foobar',
          label: 'Foobar',
          position: 'left',
          target: '_blank'
        },
      ],
    },
  }

Error: ValidationError: "navbar.items[0].href" must be a valid uri
My webserver is hosting 2 sites, and I need to jump out from docusaurus to another static html side on path /foobar. The path has a dynamic base url, because the site gets hosted and different environment stages. It would be great if you support this again.
Thanks

Hi,
Can you give more details please?
What are the fully qualified URL(s) this link should lead to?
Have you tried to: /foobar instead of href?
Honestly this part of the code is a bit messy and it's hard to change anything without introducing a breaking change.
At some point we should be able to tell the router if we should do a regular HTML navigation, or history.push(), and the current API surface does not help us to make this explicit, but using to + target=_blank should do the job

Hi, thanks for your feedback, using to: /foobar with target solves the problem. A more explicit api surface would be definitely nice to have.


Read data from csv

Add the ability to read data from a csv and process it as salesforce data
Should be able to specify the file, then unmarshal response into a struct
This would allow users to transform data before updating, inserting, etc

Marking this as not planned. I don't think this is within scope of the project as of now.


refactor openstack-envs for v7k

update v7k openstack-envs, the new structure is as the following:
v7k:
  enabled: True
  management_ip: <IP_ADDRESS>
  ssh_port: 22
  users:
    cinder:
      name: bbcadmin
      password:
      ssh_pvt_key:
      ssh_pub_key:
    monitoring:
      name: bbcmonitor
      password:
      ssh_pvt_key:
      ssh_pub_key:
  storage_pools:
    - v7k_pool1

we need to define following variables in cinder-common/defaults/main.yml
v7k:
  enabled: False
  ssh_port: 22

In addition, we need to add v7k.yml to https://github.com/blueboxgroup/ursula/blob/master/roles/preflight-checks/tasks/check_items.yml that will assert required variables are defined if v7k.enable is true


Multi GPU

I see few issues in running the code with multi gpu's. Is it supporting?

Currently, we do not support multi-GPU since only one training video is used.


Default system tags

Quarks should add default tags to topology elements.  The console should use known Quarks tags to show useful information.
TBD

What sort of information would default tags convey?  The graph JSON representation already provides type info via the className attribute...
e.g. would tags attached to a Filter propagate to the downstream reachable TStreams?

Issue moved to https://issues.apache.org/jira/browse/QUARKS-70


Burn mode

Implemented a burn mode that allows us to delete tree elements.
Also did some major refactoring to the UI/logic separation.

You can not delete leaves with the burn mode enabled

Got it! Working on it.

You can not delete leaves with the burn mode enabled

Got it! Working on it.

You better be


🐛 [BUG]: Deleting a node that has a connected edge that has deletable: false will always trigger an orphaned edge error

Is there an existing issue for this?

[X] I have searched the existing issues and this is a new bug.

Current Behavior
See title. When deleting a node that has any connected edges that are deletable: false, an orphaned edge error is always logged. In my environment, the edge is not removed from the state and every future modification to the graph re-triggers an error on the same edge (although I was not able to create a repro for this).
Expected Behavior
No orphaned edge error is logged, as the edge is not rendered and effectively does not exist/was deleted anyway.
Steps To Reproduce

Hook onError to console.error
Make any edge in the Basic example deletable: false
Delete the associated edge
An orphaned edge error is logged

Relevant log output
No response
Anything else?
The fact that nodes/edges which are deletable: false aren't deletable when calling deleteX() manually has tripped me up before, but I never logged a bug/issue for it because it seemed intentional and was consistent, even though my natural instinct is that the flag would only control whether or not the user is able to delete the node via the deleteKeyCode. However, the fact that the library itself tries to respect this flag when performing its own internal cleanup seems broken to me and in at least this case, it produces an invalid internal state. (Similar behavior also exists if a node has a parentNode and is deletable: false - the child node is not deleted and left orphaned when the parent node is deleted. But, no error is logged, so I never opened a bug for that either.)

Mh… I’ll take a look and see what can be done about this. Thanks for another in-depth report :)

Thanks! I figure this will be kinda tricky to solve because everything is using the same utilities, and I imagine there's some concerns around breaking changes as well. I'm in no hurry for this though, I found a workaround in my application for the time being.

Should be fixed with 1.19.3


Gives the possibility to parametrize the  $tmp_config_path

Gives the possibility to parametrize the  $tmp_config_path and avoid tmp config file creation

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

Will open something new as this one is in conflict and module evolved, need to rethink that


(getting started example): Material "disappears" after ~10 seconds

Not sure whether this is relevant to three or react-three-renderer though this issue is particularly boggling to me.
When running the getting started example the material "disappears" after a few seconds. Small changes to the scene affect how long it takes until the change:

default ~5 seconds
swap meshBasicMaterial for meshPhongMaterial ~8 seconds
add second cube ~6 seconds
swap boxGeometry for sphereGeometry ~10 seconds

Code
```js
// using redux instead of this.setState
// is equivalent - error still occurs when using this.setState
const Scene = connect(
  state => ({cubeRotation: new THREE.Euler(..._.range(3).map(() => state.meta.age * 0.01))})
)(
class Scene extends React.Component {
  constructor(props, context) {
    super(props, context)
this.cameraPosition = new THREE.Vector3(0, 0, 5)
this.firstCubePosition = new THREE.Vector3(0, 0, 0)
this.secondCubePosition = new THREE.Vector3(2, 0, 2)

}
render() {
const width = window.innerWidth
const height = window.innerHeight
const box = i => (
  <mesh
    position={this[i ? 'secondCubePosition' : 'firstCubePosition']}
    rotation={this.props.cubeRotation}
  >
    <boxGeometry
      dynamic={false}
      width={1}
      height={1}
      depth={1}
    />
    <meshPhongMaterial
      color={0x00ff00}
    />
  </mesh>
)

return (
  <React3
    mainCamera="camera"
    width={width}
    height={height}
    onAnimate={() => store.dispatch('TICK')}
  >
    <scene>
      <perspectiveCamera
        name="camera"
        fov={75}
        aspect={width / height}
        near={0.1}
        far={1000}
        position={this.cameraPosition}
      />
      <pointLight
        color={0xffffff}
        position={this.cameraPosition}
      />
      <ambientLight
        color={0x111111}
        position={this.cameraPosition}
      />
      {box(0)}
      {box(1)}
    </scene>
  </React3>
)

}
})
</details>

There's nothing (except the visual change) to indicate a problem occurred.

That's very strange. Which browser and which version of react-three-renderer / threejs / react ?

Wow, tested in chrome and I get similar problems, but funnily on firefox it's all fine. WTF??

Also confirming that it works fine in Edge and Internet Explorer.

OK. It looks like on Chrome it's spending an awfully long time on getting stack traces for prop type validation errors... and somehow that's making it miss some frames for some very strange reason. On other browsers this does not happen, also if you serve with e.g.
new webpack.DefinePlugin({
    'process.env': {
      NODE_ENV: '"production"',
    },
  }),

Then prop types will not be checked and it's all fine. I'm wondering if I should try to somehow use a stackless error at least for the react-three-renderer internal prop type checking...

@toxicFork, I just tried out the Simple example and React 15.1.0 with react-three-renderer 2.0.1 and it gave me the following warnings.

I looked at the code and it checked if it is in the production environment:
function checkDebugID(debugID) {
  process.env.NODE_ENV !== 'production' ? warning(debugID, 'ReactDebugTool: debugID may not be empty.') : void 0;
}

I turned it on and my error was gone, might it be related to this issue?

I couldn't reproduce the debug id error but it could be a clue! I will have more time this evening UK time to take a look.

@toxicFork Using react 15.0.2, react-three-renderer 2.0.1 & chrome 50.0.2661.102.
Also noticed the problem goes away in production mode & other browsers.
@imjasonmiller Tempted to say no, I tried setting NODE_ENV to "development" explicitly though the problem still occurred.
Here's another example with 3 pointLights (0x666666, 0x333333, 0x333333) and 1 ambientLight (0xaaaaaa). When the problem occurs the effect is equivalent to deleting the ambientLight.
I don't think this is exactly what's happening in the previous example though. The point light is brightest in that example. In this one you can also see the Earth retains a blue tint when the lights go out instead of the color being stripped.

This sounds like this chrome issue: mrdoob/three.js#8666

It looks like "debugId may not be empty" came from a newer version of React 3 renderer. I'm using an older version of r3r in another project and have no issues.

And a newer version of React :) I think 15.1.

OK, I fixed the _debugId issues on #77 , will keep an eye on the weird chrome lighting issue still

Still seeing the issue in production mode using the latest React 15.1.0 and R3R 2.1.3. I also see a secondary error that says "invariant requires an error message argument."
The problem goes away in development mode.

Hmm... Okay I will fix this asap, looks like I forgot to wrap a call in dev
flag checks, sorry about that
On Wed, 15 Jun 2016, 15:46 Robinnnnn<EMAIL_ADDRESS>wrote:

Still seeing the issue in production mode using the latest React 15.1.0
and R3R 2.1.3. I also see a secondary error that says "invariant requires
an error message argument."
The problem goes away in development mode.
[image: screen shot 2016-06-15 at 10 42 17 am]
https://cloud.githubusercontent.com/assets/12162433/16084324/620d8046-32e6-11e6-8309-ae08920cdd8e.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/toxicFork/react-three-renderer/issues/74#issuecomment-226210139,
or mute the thread
https://github.com/notifications/unsubscribe/AA0iLWbSFOWoK554NhQhe76d4gj3vqrOks5qMBA_gaJpZM4IkGvC
.

@Robinnnnn can you please provide a link to a repro build? I could not reproduce this on my end

I also have not seen this issue with latest versions, including dev build.

Apologies with the delayed update.
The issue was my fault. While I was minifying my code, I never set NODE_ENV to production (was using testing instead for a temporary testing server), and was being thrown the following error:

This then caused the ReactDebugTool error when trying to launch a 3D scene. Everything was fixed after switching to modes to production.
TL;DR Ran into an edge case using minified code without NODE_ENV=production

@ashtonwar do you still see this issue?

@toxicFork I'll test sometime later this week


Drag and drop doesn't work on Chrome

Version 85.0.4168.2 (Official Build) dev (64-bit)

Related to https://github.com/react-dnd/react-dnd/issues/2253

Same as https://github.com/react-dnd/react-dnd/issues/2554
And it happens only on specific Chrome versions.

The issue is fixed on Chrome Version 85.0.4173.0 (Official Build) dev (64-bit). It seems to tie to a specific Chrome version.

Seems a weird bug on Chrome dev


Public instance hyperlink returns 404

The hyperlink in README.md file api.recor.dev redirects to https://rekor.dev/api/v1/log/ but it returns 404 status code.

Thanks - this should be fixed now!


Align cpu/io thread count with partition count

We increased the partition count to three, but left the cpu/io thread count untouched. This means they are still on 2. We could either raise it to 3 or bump it to 1 since the resources are so low.

My suggestion here is to set the default cpuThreadCount to 3 (=partitioncCount). But keep the i/o threadcount at 2. i/o threads are only used by exporters. So we don't need so many i/o threads. But cpuThreads are used by several actors with in a single partition itself. So it helps to have more cpuThreads to distribute the work.
@Zelldon wdyt?

I often try to have similar values, for simplicity. But, I guess this is fine since we anyway have fewer resources and the web apps are currently not able to keep up with Zeebe, so I guess less pressure via exporting would be fine. If the user wants more performance he can set it, we can also increase the number later if we see issues with it.
Do you think it makes sense to set such a value in SaaS then as well? I think we currently haven't adjusted them for a while.

Do you think it makes sense to set such a value in SaaS then as well? I think we currently haven't adjusted them for a while.

I think it makes sense to adjust if we see any problems. May be once Roman is done with the performance targets we can revisit them and adjust if needed.
Are we trying to keep the configs of helm charts and SaaS in sync?

Are we trying to keep the configs of helm charts and SaaS in sync?

Yes we try that our defaults are similar the the S plan

Are we trying to keep the configs of helm charts and SaaS in sync?

Yes we try that our defaults are similar the the S plan

In that case, I would use the current configs from S plan. We can discuss later if the config of S plan should be adjusted or not.


Update AboutUs.adoc

Changes the description and links. Still need to update the profile pictures

@melpulomas for some reason your continuous integration for appveyor branch did not work as shown in the details section: The error seemed to be systemtests.DeleteCommandSystemTest > delete FAILED     guitests.GuiRobot$EventTimeoutException at DeleteCommandSystemTest.java:82 can you check from your IDE does that particular test work

Rerun the test seem to work now must be some mistake on the remote server of AppVeyor


Change default console to novnc

This commit does the following:

Add nova_console_type: novnc into the osa default variable file
Make the necessary changes in maas for the console check to support
both novnc and spice
Change the rpc_support role to conditionally include the spice-specific
bit

Connects https://github.com/rcbops/u-suk-dev/issues/131

recheck_all

recheck_all

I tested this with MaaS in my own AIO, but I've also fired up some maas jobs to make sure this check is implemented correctly:
http://jenkins.propter.net/job/JJB-RPC-AIO_master-swift-periodic/91/
http://jenkins.propter.net/job/JJB-RPC-AIO_master-xenial-periodic/


smartCars METAR

Can we just dump the METARs rather than link to them? This is on the actual exercise details page.

eb5baa5fa5bf78d680d9aab3f369cfd50c653a18


added exit on passphrase retrieval in command line by revendoring the…

… term package from docker/docker
Signed-off-by: Avi Vaid<EMAIL_ADDRESS>

Can one of the admins verify this patch?

jenkins, test this please

jenkins, test this please.

jenkins, ok to test

Awesome, CTRL-C now cancels out of password prompt.  Thank you for fixing this @avaid96!  LGTM pending CI.

thanks for updating this, just gave this a spin and LGTM!

awesome! opening new terminals every time was really frustrating me, happy to have this!


Automated cherry pick of #2306: [Windows]Check HostNamespace value when removing HcnEndpoint

Cherry pick of #2306 on release-1.0.
#2306: [Windows]Check HostNamespace value when removing HcnEndpoint
For details on the cherry pick process, see the cherry pick requests page.

/test-all

Codecov Report

Merging #2327 (be3eb62) into release-1.0 (e8bf52d) will decrease coverage by 19.74%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           release-1.0    #2327       +/-   ##
================================================
- Coverage        61.07%   41.32%   -19.75%
================================================
  Files              272      131      -141
  Lines            20404    16452     -3952
================================================
- Hits             12462     6799     -5663
- Misses            6645     9070     +2425
+ Partials          1297      583      -714

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
41.32% <ø> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.


Custom Resource failed to stabilize in expected time

Trying to deploy it with CDK and after it hangs for an hour trying to deploy the Custom Resource, it gives this error: "Custom Resource failed to stabilize in expected time."

Hi, trying to replicate issue at our end. Will get back to you when we have findings.  Thanks!

What seems to be happening is that when you deploy via CDK, the library dependencies are not being packaged up with the Lambda functions automatically. The installation of the custom resources fails to find expected modules.
You will need to run npm install both in the source/custom-resource and the source/job-submit directories. Then run deploy. We'll update our documentation in the next release. Hope this gets you unblocked.

Thanks a lot for fast reply!!!  That solution worked.
I wonder if there is anyway to adjust the timeout, so in case of errors doesn't take 2 hrs.

Added in the v1.1.0 release.


unit test failed buffer_set_write_buffer_switch_release

failures:

---- page_store::version::tests::buffer_set_write_buffer_switch_release stdout ----
thread 'page_store::version::tests::buffer_set_write_buffer_switch_release' panicked at 'assertion failed: `(left == right)`
  left: `3`,
 right: `1`', src/page_store/version.rs:590:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Seems it fails occasionally.

Seems to be affected by other tests.


Unhandled user callback exception on dynamic library interaction

Describe the bug
When use dynamic library to render, clicking the exit button the application stop for seconds and exit with error.
To Reproduce
Steps to reproduce the behavior:
main.rs:
use eframe::egui::{self, Context};
use eframe::{App, Frame};
use libloading::{Library, Symbol};
use std::fs;

pub struct Program {
    libs: Vec<Library>,
}

impl Default for Program {
    fn default() -> Program {
        let plugins = fs::read_dir("libs/").expect("no plugins folder!");
        let mut libs = vec![];
        for plugin in plugins {
            unsafe {
                let path = plugin.unwrap().path();
                let lib = Library::new(path).expect("couldn't find dll");
                libs.push(lib);
            }
        }
        Self { libs }
    }
}

impl App for Program {
    fn update(&mut self, ctx: &Context, _frame: &mut Frame) {
        for lib in &self.libs {
            unsafe {
                let func: Symbol<unsafe extern "C" fn(&Context)> = lib.get(b"render").unwrap();
                func(ctx);
            }
        }
        egui::SidePanel::right("main").show(ctx, |ui| {
            ui.heading("My egui Application Main");
        });
    }
}

fn main() {
    let options = eframe::NativeOptions {
        viewport: egui::ViewportBuilder::default().with_inner_size([320.0, 240.0]),
        ..Default::default()
    };
    eframe::run_native(
        "My egui App",
        options,
        Box::new(|_cc| Ok(Box::<Program>::default())),
    )
    .unwrap();
}

lib.rs:
use eframe::egui;
use eframe::egui::Context;

#[no_mangle]
pub fn render(ctx: &Context) {
    egui::SidePanel::left("dll").show(ctx, |ui| {
        ui.heading("My egui Application dll");
    });
}

Expected behavior
Exit normally.
Screenshots

Desktop (please complete the following information):

OS: Windows11

Additional context
Error appears on both Glow and wgpu backend.
Both panic before dropping painter.
Eframe version: 0.28.1
Error 0xc000041d exists when exception isn't handled in windows' user callback.

The render function in lib.rs is not defined as extern "C" but it is imported as one, which might result in the calling convention mismatching.

The render function in lib.rs is not defined as extern "C" but it is imported as one, which might result in the calling convention mismatching.

It made no difference in my test. And I have something more from debugger(sorry for the pic reading but I don't know how to dump it in vscode) :

And it seem like a deallocation problem here, may be it is caused by using Arc in dll(wait for more test)?

In 0.29.1, After using mimalloc and applying -Zbuild-std=core,std, allocation issue is toward to LayoutJob's text's dropping, and it seems like a double-free problem?


FFI doesn't open DLLs installed per pacman

FFI::DynamicLibrary.open("libusb-1.0.dll",0) # => LoadError: Could not open library 'libusb-1.0.dll': Falscher Parameter.

FFI makes use of LoadLibraryEx() with LOAD_WITH_ALTERED_SEARCH_PATH since it's very first commit . However this requires an absolute dll path. A relative path like "libusb-1.0.dll" should locate the DLL in c:\msys64\mingw32\bin\libusb-1.0.dll , but it doesn't, because LOAD_WITH_ALTERED_SEARCH_PATH doesn't allow relative paths.
In contrary Fiddle.dlopen('libusb-1.0.dll') works as expected and loads the dll. It uses the basic LoadLibrary() call.
IMHO this is a FFI bug and should be filed there.

I have opened upstream PRs on https://github.com/ffi/ffi/pull/553 and https://github.com/jnr/jffi/pull/45 .

The patch was merged to master on ffi: https://github.com/ffi/ffi/commit/cb65f1ac33e8d6db452a88d73fef1f63eef9ad7a
Waiting for the next release...


Update github-actions workflow steps

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.81%. Comparing base (dd8125f) to head (07e6773).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #109   +/-   ##
=======================================
  Coverage   92.81%   92.81%
=======================================
  Files           4        4
  Lines         362      362
  Branches       54       54
=======================================
  Hits          336      336
  Misses         18       18
  Partials        8        8

Flag
Coverage Δ

unittests
92.81% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Add "pytoml" to install_requires

Thanks, I should probably add something to read this from Pipfile instead.