Is it possible to use RGB image as input, without hair color map?

Hello!
Is it possible to use RGB image as input, without hair color map?
Thanks!

It support such behavior after the latest commit.
When you place 256x256 images into predict_from, output with a random hair color.
Thanks.

Thanks for quick answer!
Would you please clearify:
3-channel full-colour image (not a semantic map, but just an anime-type image) used as input, already contains hair colour, as well as face colour and etc.
vanilla pix 2 pix/spade will understand this and generate output image resembling the input colours
why then output of your work will be with totally random hair color?
Yes I understand that if it would be trained on semantic map, the colour is undefined and would be random; but when we train on full-colour - we already "telling" the net how we expect colours to be preserved?
What I am looking for is the modern-age clever paired image to image GAN, and I can't understand why everything nowdays is "semantic map to image" instead.

Oh, I'm sorry. You want to use the RGB image of the anime-type as the style. Semantic labels are also RGB, so I was mistaken.
I don't follow state-of-the-art GANs, so I don't know much about recent pix2pix. However, the pix2pix with SPADE in this repository does not use the style control by KL divergence shown in the original paper. Ideally, as you say, full-color anime images should be used by encoders to compute noise and learn latent representation. However, since I do not have enough computational resources, I could not generate a synthetic anime image using both a semantic map and a style image as the target with encoders.
Therefore, in this repository, instead of learning styles, only hair is learned in a small network, so no anime-type images are used as input for the generator as a target style.
I think the recent trend of generating images from semantic maps is probably to reproduce the pen that generates hair, eyes, etc. in drawing software. It seems to me that this is probably a more interesting application than regenerating the same images.
I'm sorry if I'm missing the point as I don't fully understand your question.

Sorry for the late reply.
I have often heard of things like AnimeGAN2 which converts images to anime style.
SPADE is a method to restrict the loss of semantic information when generating images from Semantic maps. So I am not sure if the same effect can be theoretically performed for an image obtained from a camera. Even if the accuracy is improved, the fact may be due to an increase in the number of parameters.
Thanks for all the discussion. If you have any other questions, please let me know.
The answer to this question of whether my model will produce the desired results with the input image from the camera is NO.
Thanks.


RecursionError when inferring recursive protobuf definitions.

Hello,
Thanks for developing the pbspark library. This seems quite useful for converting protobuf on the wire to dataframes.
I have some recursive proto definitions of the form (a simplified example):
message RecMessage {
	string         id        = 1;
	RecMessage     rec_msg   = 2;
}

A minimal code example that shows the issue:
from example.example_pb2 import RecMessage
r = RecMessage(id="recmsg1")
data = [{"value": r.SerializeToString()}]
df = spark.createDataFrame(data)
mc = MessageConverter()
mc_pb = mc.from_protobuf(df.value, RecMessage)
df_decoded = df.select(mc_pb).alias("value")
df_flattened = df_decoded.select("value.*")
df_flattened.show()

The above code barfs with a RecursionError at from_protobuf  while trying to infer the Spark schema from the recursive protobuf schema:
----> 7 mc_pb = mc.from_protobuf(df.value, RecMessage)
/usr/local/lib/python3.7/dist-packages/pbspark/_proto.py in get_spark_schema(self, descriptor, options)
    202                     )
    203                 else:
--> 204                     spark_type = self.get_spark_schema(field.message_type)
    205             else:
    206                 spark_type = _CPPTYPE_TO_SPARK_TYPE_MAP[field.cpp_type]()

... last 1 frames repeated, from the frame below ...

/usr/local/lib/python3.7/dist-packages/pbspark/_proto.py in get_spark_schema(self, descriptor, options)
    202                     )
    203                 else:
--> 204                     spark_type = self.get_spark_schema(field.message_type)
    205             else:
    206                 spark_type = _CPPTYPE_TO_SPARK_TYPE_MAP[field.cpp_type]()

RecursionError: maximum recursion depth exceeded while calling a Python object

Wondering how to get around this @crflynn?  Thanks!

My initial thought is that self-referencing definitions just won't work here. If the protobuf definition allows for arbitrary depth, but spark schemas don't, I don't see how could we reasonably infer a schema by the definition alone.

@crflynn, yes, that was my initial thought as well. Would it be reasonable for pbspark to terminate the recursive schema inference at a configurable depth (and default to a reasonable depth, say 2 or 3)? Alternatively, provide an option to skip the recursive protobuf bits altogether (this may seem like a hack, but would work for my use case at least because the protobuf data is guaranteed to not be recursive)?

It's been a while but I think a custom serializer for that message type would do the trick. You'd have to specify a parsing function and the return type schema for that message in particular. There is an example in the readme.

I took another look at this problem and added an example+test. You can take a look at it here:
https://github.com/crflynn/pbspark/blob/fd75e9d46706bc9b48e2bc0e058ad0e32d95604f/tests/fixtures.py#L14
https://github.com/crflynn/pbspark/blob/fd75e9d46706bc9b48e2bc0e058ad0e32d95604f/tests/test_proto.py#L221

Were you able to resolve this?
I am closing and labeling this wontfix for now.


Show detailed diagnostic messages for callables with an unsupported required capability

Adds secondary diagnostics for unsupported capabilities that give the reasons why a callable from a library isn't supported. For example:
namespace Library {
    function MyResultAsBool(result : Result) : Bool {
        return result == One ? true | false;
    }
}

namespace App {
    open Library;

    operation Foo() : Bool {
        return MyResultAsBool(Zero);
    }
}

gives the diagnostics when compiled for Honeywell:

Error QS5027:
File: C:\Users\samarsha\Desktop\QSharpSandbox\App\App.qs
Position: [ln 5, cn 16]
The callable MyResultAsBool requires the FullComputation runtime capability, which is not supported by the target HoneywellProcessor.

Warning QS5024:
File: C:\Users\samarsha\Desktop\QSharpSandbox\App\App.qs
Position: [ln 5, cn 16]
MyResultAsBool: Measurement results cannot be compared here. The target HoneywellProcessor only supports comparing measurement results as part of the condition of an if- or elif-statement in an operation. [C:\Users\samarsha\Desktop\QSharpSandbox\Library\Library.qs:3:16]

Resolves #736.

@bettinaheim Could you take another look at your remaining open comments?

@bettinaheim Could you take another look at your remaining open comments?


[BEAM-2802] Support multi-byte custom separator in TextIO

Follow this checklist to help us incorporate your contribution quickly and easily:

[X] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[X] Each commit in the pull request should have a meaningful subject line and body.
[X] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[X] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[X] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @jkff

Coverage decreased (-0.02%) to 69.937% when pulling 16dda224f7ec54a61fdb402c0b978d6cf7e27d62 on echauchot:TextIO-Record-Separator into e33cc24a577d049416451266f398e6b22f5c7058 on apache:master.

Coverage decreased (-0.01%) to 69.947% when pulling 16dda224f7ec54a61fdb402c0b978d6cf7e27d62 on echauchot:TextIO-Record-Separator into e33cc24a577d049416451266f398e6b22f5c7058 on apache:master.

Coverage decreased (-0.03%) to 69.928% when pulling 16dda224f7ec54a61fdb402c0b978d6cf7e27d62 on echauchot:TextIO-Record-Separator into e33cc24a577d049416451266f398e6b22f5c7058 on apache:master.

Thanks for your review once again Eugene!

Coverage decreased (-0.002%) to 69.957% when pulling ce699356f8448ac4f879a25fce551cfe3b54d333 on echauchot:TextIO-Record-Separator into e33cc24a577d049416451266f398e6b22f5c7058 on apache:master.

rebased on master

Coverage decreased (-0.02%) to 69.722% when pulling 43e9faa45edfdbfa4f548e489c3cf3c71d7c4dcd on echauchot:TextIO-Record-Separator into c9653f27056d9d4dd85f7951f4edbd9da524b894 on apache:master.

I did the check that provided separator does not self-overlaps. PTAL

retest this please

Coverage decreased (-0.004%) to 69.734% when pulling a01a231c8fe6624c11c16c661fbe10e4371c0e1e on echauchot:TextIO-Record-Separator into c9653f27056d9d4dd85f7951f4edbd9da524b894 on apache:master.

Merged with changes:

Renamed separator to delimiter for consistency with previous terminology
More compact code for detecting self-overlap
More extensive exhaustive splitting test (code still passed the test without changes!)

Thanks @jkff !


sara no stam method for tbow

I have a suggestion that I don't see posted yet. Saradomin gwd no-stam method for tbow (5tick) and bowfa (4tick) . 2 different methods. I believe they were developed by GEChallengeM and you can find them on YouTube.

Adding bowfa as well

finished


false reportGeneralTypeIssues when doing arithmethic with pint package

Environment data

Language Server version: v2022.8.10
OS and version: Windows 10 Pro (Build: 19044.1889)
Python version: 3.10.5

Code Snippet

import numpy as np
import uncertainties as uc
from pint import UnitRegistry
from uncertainties import unumpy as unp

ureg = UnitRegistry()  # Initialize units registry
ureg.default_format = "~P"  # Pretty print by default

R2 = uc.ufloat(98, 0.1, "R2") * ureg.ohm
R1 = uc.ufloat(98.2, 0.1, "R1") * ureg.ohm

print(R2 / (R1 + R2))

print(1 * ureg.ohm + 2 * ureg.ohm)

print(np.array([1, 2, 3]) * ureg.meter + np.array([1.1, 4, 3.4]) * ureg.meter)
print(unp.uarray([1, 2, 3], [0.1, 0.2, 0.3]) * ureg.meter + unp.uarray([1.1, 4, 3.4], [0.01, 0.04, 0.07]) * ureg.meter)

Expected behavior
No linting errors for the provided code. it runs just fine, and has no issues at all as seen here:

Actual behavior
pylance reports I can't add quantities with units from pint even though I can. Both regular numbers with units and quantities with uncertainties created by the uncertainties library with pint units fail to type check. However, notice that numpy arrays as well as uncertainties arrays (which are basically numpy arrays) type check just fine.
Also, note that pylance thinks these expressions are of type Unit (which really can't be added. can't do ureg.meter + ureg.meter), but in reality, these expressions are of type Quantity because of the multiplication by numerical values. Quantity objects can be added.
Logs

[Info  - 1:21:16 PM] (8820) Pylance language server 2022.8.10 (pyright 6fa755c0) starting
[Info  - 1:21:16 PM] (8820) Server root directory: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist
[Info  - 1:21:16 PM] (8820) Starting service instance "dc"
[Info  - 1:21:16 PM] (8820) Notebook support: LSP
[Info  - 1:21:16 PM] (8820) Interactive window support: LSP
[Info  - 1:21:16 PM] (8820) No configuration file found.
[Info  - 1:21:16 PM] (8820) No pyproject.toml file found.
[Info  - 1:21:16 PM] (8820) Setting pythonPath for service "dc": "D:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\python.exe"
[Warn  - 1:21:16 PM] (8820) stubPath d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings is not a valid directory.
[Info  - 1:21:16 PM] (8820) Assuming Python version 3.10
[Info  - 1:21:16 PM] (8820) Assuming Python platform Windows
[Info  - 1:21:17 PM] (8820) Search paths for d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc
[Info  - 1:21:17 PM] (8820)   c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib
[Info  - 1:21:17 PM] (8820)   d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc
[Info  - 1:21:17 PM] (8820)   d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings
[Info  - 1:21:17 PM] (8820)   c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stubs\...
[Info  - 1:21:17 PM] (8820)   c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs
[Info  - 1:21:17 PM] (8820)   d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs
[Info  - 1:21:17 PM] (8820)   d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib
[Info  - 1:21:17 PM] (8820)   d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5
[Info  - 1:21:17 PM] (8820)   d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages
[Info  - 1:21:17 PM] (8820)   d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32
[Info  - 1:21:17 PM] (8820)   d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib
[Info  - 1:21:17 PM] (8820)   d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin
[Info  - 1:21:17 PM] (8820) Adding fs watcher for library directories:
 D:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs
D:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\lib
D:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5
D:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\lib\site-packages
D:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\lib\site-packages\win32
D:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\lib\site-packages\win32\lib
D:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\lib\site-packages\Pythonwin
[Info  - 1:21:18 PM] (8820) Adding fs watcher for directories:
 d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc
[Info  - 1:21:18 PM] (8820) Searching for source files
[Info  - 1:21:18 PM] (8820) Found 1 source file
(8820) [IDX(FG)] index libraries d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc (index) ...
(8820) [IDX(FG)]   read stdlib indices (27ms)
(8820) [IDX(FG)] index libraries d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc (index) [succeed] (27ms)
(8820) [FG] parsing: d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\dc2.py (52ms)
(8820) [FG] parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 2ms] (77ms)
(8820) [FG] binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\builtins.pyi (28ms)
(8820) [FG] binding: d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\dc2.py (1ms)
[Info  - 1:21:18 PM] (8820) Background analysis(1) root directory: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist
[Info  - 1:21:18 PM] (8820) Background analysis(1) started
(8820) Background analysis message: setConfigOptions
(8820) Background analysis message: setImportResolver
(8820) Background analysis message: ensurePartialStubPackages
(8820) Background analysis message: setTrackedFiles
(8820) Background analysis message: markAllFilesDirty
(8820) Background analysis message: setFileOpened
(8820) Background analysis message: getDiagnosticsForRange
(8820) Background analysis message: analyze
(8820) [BG(1)] analyzing: d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\dc2.py ...
(8820) [BG(1)]   parsing: d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\dc2.py (52ms)
(8820) [BG(1)]   parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 3ms] (82ms)
(8820) [BG(1)]   binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\builtins.pyi (29ms)
(8820) [BG(1)]   binding: d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\dc2.py (2ms)
(8820) [BG(1)]   checking: d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\dc2.py ...
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\typing_extensions.pyi [fs read 1ms] (6ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\typing_extensions.pyi (2ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\typing.pyi [fs read 0ms] (12ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\typing.pyi (7ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi [fs read 1ms] (13ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\types.pyi [fs read 0ms] (11ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\types.pyi (3ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\abc.pyi [fs read 0ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\abc.pyi (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\pyplot.pyi [fs read 0ms] (61ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\pyplot.pyi (3ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\__init__.py [fs read 0ms] (24ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\__init__.py ...
(8820) [BG(1)]       parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_stats_py.py [fs read 1ms] (94ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_stats_py.py (20ms)
(8820) [BG(1)]       parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\distributions.py [fs read 0ms] (5ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\distributions.py ...
(8820) [BG(1)]         parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_continuous_distns.py [fs read 1ms] (104ms)
(8820) [BG(1)]         binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_continuous_distns.py (49ms)
(8820) [BG(1)]         parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_discrete_distns.py [fs read 1ms] (16ms)
(8820) [BG(1)]         binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_discrete_distns.py (8ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\distributions.py (180ms)
(8820) [BG(1)]       parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_morestats.py [fs read 1ms] (31ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_morestats.py (8ms)
(8820) [BG(1)]       parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_binned_statistic.py [fs read 1ms] (5ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_binned_statistic.py (3ms)
(8820) [BG(1)]       parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_multivariate.py [fs read 1ms] (51ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_multivariate.py (17ms)
(8820) [BG(1)]       parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_entropy.py [fs read 1ms] (13ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_entropy.py (2ms)
(8820) [BG(1)]       parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_hypotests.py [fs read 1ms] (26ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_hypotests.py (4ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\__init__.py (465ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_stats_mstats_common.py [fs read 1ms] (12ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\stats\_stats_mstats_common.py (2ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\__init__.pyi [fs read 1ms] (161ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\__init__.pyi (17ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\__init__.py [fs read 0ms] (3ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\__init__.py ...
(8820) [BG(1)]       parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\core.py [fs read 1ms] (24ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\core.py (6ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\__init__.py (32ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\__init__.py [fs read 1ms] (4ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\__init__.py (0ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\registry.py [fs read 1ms] (25ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\registry.py (6ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\unumpy\__init__.py [fs read 0ms] (1ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\unumpy\__init__.py ...
(8820) [BG(1)]       parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\unumpy\core.py [fs read 0ms] (3ms)
(8820) [BG(1)]       binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\unumpy\core.py (2ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\uncertainties\unumpy\__init__.py (5ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\collections\abc.pyi [fs read 0ms] (0ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\collections\abc.pyi ...
(8820) [BG(1)]       parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\_collections_abc.pyi [fs read 1ms] (1ms)
(8820) [BG(1)]       binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\_collections_abc.pyi (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\collections\abc.pyi (2ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\math.pyi [fs read 0ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\math.pyi (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\array.pyi [fs read 0ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\array.pyi (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\mmap.pyi [fs read 0ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\mmap.pyi (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\ctypes\__init__.pyi [fs read 1ms] (3ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\ctypes\__init__.pyi (2ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\pickle.pyi [fs read 1ms] (3ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\pickle.pyi (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\warnings.pyi [fs read 1ms] (3ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\warnings.pyi (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\_warnings.pyi [fs read 0ms] (0ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\_warnings.pyi (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\re.pyi [fs read 1ms] (3ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\re.pyi (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\enum.pyi [fs read 0ms] (2ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\enum.pyi (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\sre_compile.pyi [fs read 0ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\sre_compile.pyi ...
(8820) [BG(1)]       parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\sre_constants.pyi [fs read 1ms] (1ms)
(8820) [BG(1)]       binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\sre_constants.pyi (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\sre_compile.pyi (2ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\util.py [fs read 1ms] (9ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\util.py (4ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\unit.py [fs read 1ms] (4ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\unit.py (1ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\_typing.py [fs read 0ms] (0ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\_typing.py (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\logging\__init__.pyi [fs read 0ms] (13ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\logging\__init__.pyi (2ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\importlib\metadata\__init__.pyi [fs read 1ms] (5ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\importlib\metadata\__init__.pyi (1ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\quantity.py [fs read 1ms] (17ms)
[Info  - 1:21:18 PM] (8820) Could not import 'dask.base' in file 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\quantity.py'
[Info  - 1:21:18 PM] (8820)   Looking in stubPath 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Looking in root directory of execution environment 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Looking in bundled stubs path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib'
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
[Info  - 1:21:18 PM] (8820)   Looking for typeshed third-party path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stubs path
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\quantity.py (9ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\compat.py [fs read 1ms] (12ms)
[Info  - 1:21:18 PM] (8820) Could not import 'pint_pandas' in file 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\compat.py'
[Info  - 1:21:18 PM] (8820)   Looking in stubPath 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Looking in root directory of execution environment 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Looking in bundled stubs path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib'
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
[Info  - 1:21:18 PM] (8820)   Looking for typeshed third-party path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stubs path
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
[Info  - 1:21:18 PM] (8820) Could not import 'xarray' in file 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\compat.py'
[Info  - 1:21:18 PM] (8820)   Looking in stubPath 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Looking in root directory of execution environment 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Looking in bundled stubs path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib'
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
[Info  - 1:21:18 PM] (8820)   Looking for typeshed third-party path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stubs path
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
[Info  - 1:21:18 PM] (8820) Could not import 'dask' in file 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\compat.py'
[Info  - 1:21:18 PM] (8820)   Looking in stubPath 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Looking in root directory of execution environment 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Looking in bundled stubs path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib'
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
[Info  - 1:21:18 PM] (8820)   Looking for typeshed third-party path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stubs path
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
[Info  - 1:21:18 PM] (8820) Could not import 'dask.base' in file 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\compat.py'
[Info  - 1:21:18 PM] (8820)   Looking in stubPath 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\typings'
[Info  - 1:21:18 PM] (8820)   Looking in root directory of execution environment 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\DLLs'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\win32\lib'
[Info  - 1:21:18 PM] (8820)   Looking in python search path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'd:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pythonwin'
[Info  - 1:21:18 PM] (8820)   Looking in bundled stubs path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve stub package using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs'
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stdlib path
[Info  - 1:21:18 PM] (8820)   Attempting to resolve using root path 'c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib'
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
[Info  - 1:21:18 PM] (8820)   Looking for typeshed third-party path
[Info  - 1:21:18 PM] (8820)   Looking for typeshed stubs path
[Info  - 1:21:18 PM] (8820)   Typeshed path not found
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\pint\compat.py (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\numbers.pyi [fs read 0ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\numbers.pyi (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\operator.pyi [fs read 0ms] (2ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\operator.pyi ...
(8820) [BG(1)]       parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\_operator.pyi [fs read 0ms] (3ms)
(8820) [BG(1)]       binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\_operator.pyi (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\operator.pyi (4ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\datetime.pyi [fs read 0ms] (2ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\datetime.pyi (1ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\core\multiarray.pyi [fs read 1ms] (4ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\core\multiarray.pyi (2ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\__init__.py [fs read 1ms] (3ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\__init__.py (1ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_dtype_like.py [fs read 0ms] (1ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_dtype_like.py (1ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_generic_alias.py [fs read 1ms] (3ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_generic_alias.py (2ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_shape.py [fs read 1ms] (1ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_shape.py (0ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_array_like.py [fs read 1ms] (2ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_array_like.py (0ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_nested_sequence.py [fs read 1ms] (2ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_nested_sequence.py (0ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\core\overrides.py [fs read 1ms] (5ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\core\overrides.py (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\inspect.pyi [fs read 1ms] (5ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\inspect.pyi (1ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\linalg\__init__.pyi [fs read 0ms] (3ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\linalg\__init__.pyi (0ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\linalg\linalg.pyi [fs read 1ms] (7ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\linalg\linalg.pyi (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\colors.pyi [fs read 0ms] (6ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\colors.pyi (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\figure.pyi [fs read 1ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\figure.pyi (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\artist.pyi [fs read 0ms] (0ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\artist.pyi (0ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\_lib\_bunch.py [fs read 0ms] (2ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\scipy\_lib\_bunch.py (1ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\sys.pyi [fs read 1ms] (2ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\typeshed-fallback\stdlib\sys.pyi (2ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\lib\function_base.pyi [fs read 0ms] (4ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\lib\function_base.pyi (1ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\core\fromnumeric.pyi [fs read 1ms] (7ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\core\fromnumeric.pyi (2ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_scalars.py [fs read 1ms] (1ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\_typing\_scalars.py (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\_typing.pyi [fs read 0ms] (3ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\_typing.pyi (0ms)
(8820) [BG(1)]     parsing: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\typing\__init__.py [fs read 1ms] (5ms)
(8820) [BG(1)]     binding: d:\Portable_Programs\.pyenv\pyenv-win\versions\3.10.5\Lib\site-packages\numpy\typing\__init__.py (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\container.pyi [fs read 1ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\container.pyi (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\collections.pyi [fs read 1ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\collections.pyi (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\cm.pyi [fs read 1ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\cm.pyi (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\lines.pyi [fs read 1ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\lines.pyi (0ms)
(8820) [BG(1)]     parsing: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\legend.pyi [fs read 0ms] (1ms)
(8820) [BG(1)]     binding: c:\Users\shai\.vscode\extensions\ms-python.vscode-pylance-2022.8.10\dist\bundled\stubs\matplotlib\legend.pyi (0ms)
(8820) [BG(1)]   checking: d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\dc2.py (1395ms)
(8820) [BG(1)] analyzing: d:\OneDrive - Technion\פיזיקה\מעבדה 2מ\dc\dc2.py (1564ms)
(8820) Background analysis message: getDiagnosticsForRange
(8820) Background analysis message: resumeAnalysis
(8820) Background analysis message: getDiagnosticsForRange
(8820) Background analysis message: getDiagnosticsForRange
(8820) Background analysis message: getDiagnosticsForRange
(8820) Background analysis message: getDiagnosticsForRange

It looks like you've set "python.analysis.typeCheckingMode" to "basic", which enables static type checking diagnostics.
pint is an untyped library, and I assume that you have no type stubs for it. That means pyright (the type checker upon which pylance is built) falls back on type inference techniques to attempt to infer the types based on the available sources.
In this particular case, the inferred return type of pint.Unit.__mul__ is Unit | Quantity because the method's implementation returns instances of both Unit and Quantitiy on different code paths. However, Unit doesn't support an __add__ or __radd__ operator overload, so when you attempt to use the + operator, it is a static type violation.
If you want to use static type checking, we recommend using typed libraries or find/create type stubs for the untyped libraries you use. Pylance bundles a set of type stubs for popular libraries, but pint is not included in that set. You might want to contact the maintainers of pint and ask them if they plan to add inlined type annotations. Many library authors are now doing this. We provide this guidance for library authors.
You have a few options for working around the lack of type information in the pint library:

Set python.analysis.useLibraryCodeForTypes to "false". This will disable pyright's type inference for libraries that don't have inlined type information. This will eliminate the false positive type violation errors, but it will also eliminate any completion suggestions for that library because completion suggestions are based on the inferred type information.
Manually create a minimal type stub for pint, at least for the parts of the library that you use. Here is some documentation if you want to attempt this.


[Recipe Request]: Google Groups (groups.google.com)

Preflight Checklist

[X] I have read the Contributing Guidelines for this project.
[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Name of the service
Google Groups
URL of the service
https://groups.google.com
GitHub URL to a recipe that has already been created by someone else or you
No response
Features you want implemented
Hello everyone,
I'd like Ferdium to support Google Groups. You can use Google Groups like a multi-user or functional mailbox and "light" issue tracker. No recipe seems to exist for Ferdium or Franz.
Implementing it in Rambox was rather easy with a custom script but Ferdium recipes look a lot more complicated.
Is anyone interested in tackling this? Together with someone experienced in making Ferdium recipes we should be able to dish out something pretty fast I think.

You can folllow this guide to create a new recipe

Hi @vraravam can I take this up?.

Close as per https://github.com/ferdium/ferdium-recipes/pull/207

Thank you very much for adding the service. Is it possible to automatically stay in the group you chose within the service on reload/reopening of Ferdium?
Currently I'd like to be in two different groups at once, so I created two services. But every time I reload or restart Ferdium I need to go into the service and open up the group I want again. I'd like to "stay" in the group that I opened up this way even after reloading/restarting.
Is it possible to achieve this by editing the service?

@Braintelligence - this is theoretically possible IFF the address bar url changes when you switch the chosen service. If this is the behavior, you can capture that and edit the service's package.json file, and set the value of the serviceUrl to what was shown in the address bar for that service. This process will need to be done each time there's an update to the service from a new version of Ferdium.


Fresh install of VSCode crash loops TS server

Issue Type: Bug

Fresh install VSCode
Open a JavaScript project
Typescript crash loops

VS Code version: Code 1.41.0 (9579eda04fdb3a9bba2750f15193e5fafe16b959, 2019-12-11T17:58:38.338Z)
OS version: Darwin x64 18.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
4, 4, 4

Memory (System)
16.00GB (0.72GB free)

Process Argv
-psn_0_24696716

Screen Reader
no

VM
0%

Extensions: none

Please check the TS Server log to see what the first occurrence of the crash is:

Set "typescript.tsserver.log": "verbose",
Restart VS Code and reproduce the problem
Back in VS Code, go to the TypeScript section of output panel
At the very top of this output, there should be a line that prints the path to the main server log. It should look like this (note the <semantic> part) :

[Info  - 4:06:59 PM] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20191111T144045/exthost1/vscode.typescript-language-features/tsserver-log-F2rDlk/tsserver.log

Please look through that log file for errors or stack traces (they should be near the end). If you can share the log, I can also take a look to see if anything stands out

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this


Spark Java - strange behavior when uploading files

In my project I want to try to upload files, here is the part of the code responsible for this:
        MultipartConfigElement multipartConfigElement =
                new MultipartConfigElement(
                        "/tmp_files",
                        avatarSize,
                        avatarSize,
                        1024
                );

        request.raw().setAttribute(
                "org.eclipse.jetty.multipartConfig",
                multipartConfigElement
        );

        Part uploadedFile = request.raw().getPart("file");

And a request to upload a file using Idea's http client:
POST http://localhost:8080/users/me/avatar
Content-Type: multipart/form-data; boundary=abcd
Authorization: Bearer {{authToken}}

--abcd
Content-Disposition: form-data; name="file"; filename="test.png"

< /Users/user1/resources/test.png
--abcd--

where test.png is a regular picture.
But when I try to load in this code place:
Part uploadedFile = request.raw().getPart("file");

I get an error:
java.nio.file.NoSuchFileException: /tmp_files/MultiPart11851484240893602177
	at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
	at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:218)
	at java.base/java.nio.file.Files.newByteChannel(Files.java:375)
	at java.base/java.nio.file.Files.createFile(Files.java:652)

It can be assumed that this error is due to the fact that there are no write permissions to the root of the file system (I'm testing on mac os, under the user).
But if i try to upload another file - which is just a zip file then everything works.
POST http://{{host}}/users/me/avatar
Content-Type: multipart/form-data; boundary=abcd
Authorization: Bearer {{authToken}}

--abcd
Content-Disposition: form-data; name="file"; filename="file123.zip"

< /Users/18493151/develop/icandev/api-gateway/src/main/resources/file123.zip
--abcd--

and no exception in this line:
Part uploadedFile = request.raw().getPart("file");

Why is this happening? Why does the result depend on the file type?
sparkjava version 2.9.4

I don't know.


[FilledInput][material-next] Add FilledInput component

Part of https://github.com/mui/material-ui/issues/39052

Most of the PR focuses on converting everything (including FormControl.tests and InputBase.tests) to TS, and adopting useSlotProps
Design-wise, existing v5 tokens are replaced but Material You styles/tokens are not fully implemented yet and will be done in a separate PR, since the changes could be quite extensive (as a reference material-web uses 80+ tokens!). It could also be easier to implement the design together with the related Label/HelperText components.
There are now only 2 remaining sets of skipped tests across FilledInput, FormControl, and InputBase: one depends on Select, the other depends on TextField
Experiments page added under /experiments/md3/inputs

[x] I have followed (at least) the PR section of the contributing guide.

Preview: https://deploy-preview-39307--material-ui.netlify.app/experiments/md3/inputs/

can we do some runtime warning if the users does not provide multiline, but they provide some of the props that makes sense only if the component rendered is textarea?

Good idea ~ added in https://github.com/mui/material-ui/pull/39307/commits/2f6bc51f1cb6c406c1146663950123ad75e2f431


Installing via paq bring this error message

When i run :FnlCompile with code below:
(paq {
	"savq/paq-nvim"
	"udayvir-singh/tangerine.nvim"
	"kyazdani42/nvim-tree.lua"
	"nvim-treesitter/nvim-treesitter"
	"windwp/nvim-autopairs"
})

I got this error:
:: COMPILE ERROR
  xxx nvim/init.fnl
      Parse error in nvim/init.fnl:9
        expected even number of values in table literal

      * Try removing a key.
      * Try adding a value.

It compiled well when i use brackets instead of braces like this:
(paq [
	"savq/paq-nvim"
	"udayvir-singh/tangerine.nvim"
	"kyazdani42/nvim-tree.lua"
	"nvim-treesitter/nvim-treesitter"
	"windwp/nvim-autopairs"
])

@krapjost Thanks for pointing out the typo in documentation.
The error was caused because fennel interpreters curly braces {} as key-value table, for example:
{
  :key "value"
}

Which compiles to:
{
  key="value"
}

While square brackets are interpreted as lists or arrays:
[:foo :baz :bar]

Which compiles to:
{
  "foo",
  "baz",
  "bar"
}

Therefore the correct code was:
(paq [
	"savq/paq-nvim"
	"udayvir-singh/tangerine.nvim"
	"kyazdani42/nvim-tree.lua"
	"nvim-treesitter/nvim-treesitter"
	"windwp/nvim-autopairs"
])

Thank you for explanation! It worked but i didn't know why 😀


Python Module Seems to Leak Memory if it Experiences an Unhandled Exception

We had a cluster fail in production.  Turns out a value in our key value store was wrong and our python code was frequently exiting with an unhandled exception.   This apparently caused a fast memory leak and all the unbound servers in the cluster started dying due to OOM killer.
I reproduced the problem in our test environment and under valgrind I could clearly see Python leaking.   We've had similar high rates of unhandled exceptions during previous events under previous versions of unbound, but never had OOM killer get involved.  I wonder if it's related to a change in the unbound codebase (We just recently upgraded to a 1.13.2 from a very old version)?  But it seems like a python bug to me.
Below is the valgrind stack trace of the biggest leak.    We tried adding gc.collect() (Manually run a garbage collection run) to our codebase but there seemed to be no impact.
==4241== 52,405,144 bytes in 595,513 blocks are possibly lost in loss record 3,991 of 3,996
==4241==    at 0x4C28BE3: malloc (vg_replace_malloc.c:299)
==4241==    by 0x512E593: PyObject_Malloc (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x51B8D58: _PyObject_GC_Malloc (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x51B8E95: _PyObject_GC_NewVar (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x514012E: PyTuple_New (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x518521F: PyEval_EvalFrameEx (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x518B1FC: PyEval_EvalCodeEx (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x5187609: PyEval_EvalFrameEx (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x518B1FC: PyEval_EvalCodeEx (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x511571F: ??? (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x50F0FE2: PyObject_Call (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x50F10C4: ??? (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x50F119D: PyObject_CallFunction (in /usr/lib64/libpython2.7.so.1.0)
==4241==    by 0x4B1D00: pythonmod_operate (pythonmod.c:530)
==4241==    by 0x4655DF: mesh_run (mesh.c:1704)
==4241==    by 0x42946B: worker_handle_request (worker.c:1573)
==4241==    by 0x4AEB70: comm_point_udp_callback (netevent.c:769)
==4241==    by 0x4E7C36: handle_select (mini_event.c:220)
==4241==    by 0x4E7DEB: minievent_base_dispatch (mini_event.c:242)
==4241==    by 0x4AED1B: comm_base_dispatch (netevent.c:246)

The 'recent' change was the addition of a log routine that logs the python stack trace to syslog. This is for debugging convenience.
It turns out that this log routine does not Py_XDECREF the three arguments from PyErr_Fetch. That is likely the memory leak, by keeping extra references to the exception data. In the commit I have added Py_XDECREFs for the exception data and stack trace. That hopefully removes the memory leak that you have discovered.
Thanks for the detailed report. I hope the fix fixes your problem, please let me know if it does not; although I have no clue what it would otherwise be, except more reference leaks in pythonmod/pythonmod.c:122 log_py_err().

I tried your code today and I can confirm it fixes the issue.   Do you know when it will see a production ready release?


 See documentation.

:robot: Created releases:

v1.0.0
:sunflower:


Bugfix/webview version upgrade

#9

Notes:
Unfortunatelly I wasn't able to verify the fix, npm completely ignore peerDependency check for local modules (so I wasn't able to reproduce the issue locally)
@e271828- if you know how we can 'force' this check for local modules please let me know I will update CI

npm completely ignore peerDependency check for local modules

https://www.npmjs.com/package/check-peer-dependencies perhaps?

npm completely ignore peerDependency check for local modules

https://www.npmjs.com/package/check-peer-dependencies perhaps?

Looks exactly what we need, I will update PR later

@e271828- done


Refactor to remove "guzzle specific" logic

Follow up from #175
FYI @GrahamCampbell and @dbu

indeed, this is more compact
i don't think we need a new release for this, as its functionally doing the same. agreed?


LoadBalancer

Issue on page:        https://github.com/opentelekomcloud-docs/cloud-container-engine/blob/main/umn/source/networking/services/loadbalancer.rst
Please check the format of the menu on this page.

I'm not able to reproduce this view. What browser/OS do you use please?

also other browsers

Chrome on MacOs...
FireFox on MacOS

Please check one last thing, when I reach the old path, I see the same wrong view, but when I reach the new one, it's ok, please check if it's not the same case for you.
https://docs.otc.t-systems.com/cloud-container-engine/umn/networking/services/loadbalancer.html
https://docs.otc.t-systems.com/cloud-container-engine/umn/network/service/loadbalancer/creating_a_loadbalancer_service.html


Create a new businesses by name demo page

No map, just an autocompleting business name text box.

Can we retire the address finder widget now?

We are maybe waiting on a new geocoding address autocomplete example code gallery type of page before we retire it?


fix: Dynamic name in list

Checklist

[ ] Tests have been written/updated (if necessary)

[ ] All tests are passing

[ ] Docs have been updated (if necessary)
[ ] Updated Linear issue to In Review

Description
When checking this PR you have to add this line to the .env file:
MANUAL_URL="https://manuals.tst.energietransitiewindesheim.nl/devices/"
Linked Issues

Looks good to me aswell


Plenary Sessions (under Schedule)

Number of volunteers: 1

[x] Edit the sitedata_acl2020/speakers.csv.

Get the keynote schedule here.
Ask @dreasysnail or @raosudha89 for more information.

[x] Change "Example Day" to "Keynotes", and remove "Highlighted Papers" section in templates/schedule.html.

Suggestion from PCs

[ ] Make this a plenary session instead and include Keynotes, Test of Time Award, Lifetime achievement award and other livestream

Suggestion from PCs

[ ]  Make this a plenary session instead and include Keynotes, Test of Time Award, Lifetime achievement award and other livestream

Not sure how to do this. Any hints?

@georgepar Let's do this.
Create a sub-page for each day during July 6 -- 8, like ICLR2020 did (https://iclr.cc/virtual_2020/calendar.html#tab-Monday). See the screenshot below.

Each sub-page contains the plenary sessions on that day.  Here is our schedule.
July 6

July 7

July 8

Let us know if you have any thoughts about this.

@hao-fang
Hi Hao,
Can you share the plenary schedule so I can include them and close this?
Basically we need something that is close to the fields of this YAML

@georgepar See https://github.com/acl-org/acl-2020-virtual-conference-sitedata/pull/33 and https://github.com/acl-org/acl-2020-virtual-conference/pull/145
The rough schedule is here

We will need to improve it.

[ ] Rename the "Speakers" to "Plenary Sessions" in the page title
[ ] Order the sessions by time (I didn't do the PST / GMT conversion)
[ ] Gather the necessary information to be displayed. Can you make a list? I'll send an email to our program chairs and cc you to get those information.

Also, I'm thinking instead of opening a new page for each plenary session, can we make those as a collapse cards? (https://getbootstrap.com/docs/4.3/components/collapse/) In this way, the audience will stay on the same page for the whole plenary sessions on this day. (Just like a physical room experience).
But let's first get the basic version working and come back to this when we have time, unless you already know an easy way to do it.
Feel free to create another ticket if you feel you need some additional volunteers to work on this together.

@OguzCennet Are you actively working on this ticket? I feel there may be a way to split the ticket into separate sub-tasks.

In the schedule tab, under each of the days (Monday, Tuesday, Wednesday), I think it is more useful to show the events in the form of a calendar so that people can understand what time is the event in their own timezone. Just listing it out might be less useful.
We can have an "Overall Calendar" that shows the events for all days. And then additionally show each day separately again in form of a calendar.
Since we have many events in parallel, it is getting a little crowded in the overall calendar. So having a calendar for each day may make it more cleaner.

@raosudha89 We may test whether the calendar view can show enough context information about the event. The title itself may not be informative enough. The current "card" view have more opportunity to show the start-end time, speaker, and some description about the meeting.
But if you or some volunteer can implement a calendar view, then we can see how it works. Because of the current time constraint, we can probably only get a basic version working.

@hao-fang  Sounds good. I will wait for the workshop multiple calendar view issue https://github.com/acl-org/acl-2020-virtual-conference/pull/153 to be fixed and then I will create a demo for this and share it here.

All plenary sessions have been added to the schedule (https://github.com/acl-org/acl-2020-virtual-conference-sitedata/pull/49)
Closing this issue and creating a new one to add content of plenary session https://github.com/acl-org/acl-2020-virtual-conference/issues/205


Hyperlayout simply printing out config

Hyper version: 1.0.0
OS: Linux (elementary OS Loki)
I have the following in my ./.hyperlayout (a bit verbose, but I intend to add more to it in the future):
{
  "p2lab": [
    {
      "entry": "tab",
      "layout": [
        "gitsub-dir && cd experimental/p2lab",
        {
          "entry": "vertical",
          "layout": [ "gitsub-dir && cd experimental/p2lab && yarn run watch", "gitsub-dir && cd experimental/p2lab && yarn run serve-dev" ]
        }
      ]
    }
  ],
}

When I run hyperlayout p2lab, it simply prints out:
[hyperlayout config]:{"config":{"entry":"tab","layout":[{"entry":"tab","layout":["gitsub-dir && cd experimental/p2lab",{"entry":"vertical","layout":["gitsub-dir && cd experimental/p2lab && yarn run watch","gitsub-dir && cd experimental/p2lab && yarn run serve-dev"]}]}]},"cwd":"/home"}

... and does not effect the defined layout. Am I doing something wrong?

I'm not entirely sure why it prints out the config. Are you sure you have hyperlayout inside ~/.hyper.js? It still seems weird since it should detect the missing plugin (never tested it on Linux, though).
If that issue is fixed it still fails since the config is not correct. It should look like this:
{
  "p2lab": [
    "gitsub-dir && cd experimental/p2lab",
    [[
      "gitsub-dir && cd experimental/p2lab && yarn run watch",
      "gitsub-dir && cd experimental/p2lab && yarn run serve-dev"
    ]]
  ]
}

Since you set the entry point to tab you can leave it out, since this it's the default anyway. entry only works on root level, so it's necessary to create a nested array for a split view.

Ok I understand the syntax now. I also had a trailing comma which should have blown it up.
I'm using what you have posted there and it manipulates the tabs, but not so well. I've simplified the config so that we can see what is going on, and included screenshots of the result below. Note that I am using oh-my-zsh, could that perhaps introduce issues?
{
  "layout-test": [
    "echo one",
    [["echo two", "echo three"]]
  ]
}

First tab appears to do what is required.

Second tab does not do anything.

Weird. Can't really tell why this happens – I need to test this myself on a linux machine. oh-my-zsh shouldn't cause any troubles (I'm using it myself, and it works fine).
Does a single tab config work for you? It looks like pane-splitting is causing some issues.
[[
  "echo 1",
  "echo 2"
]]

$ hyperlayout

Splits, but does not execute the second command.

Okay, thanks for your help! I will try to reproduce this bug, once I get my hands on a linux machine.

This is happening to me currently after a fresh install of Hyper on MacOS Sierra.

@kevingelion The thing with the config-printing or commands not executing?

The config is just printed and nothing happens. Here's my config:
{
  "devbox": [
    [[
      ["dashboard", "cd ~/Documents/Repositories/dashboard; git status;"],
      ["coreapi", "worker"]
    ]]
  ]
}

@kevingelion Is this still an issue, or has this been resolved in #9?

@timolins unfortunately still an issue

Are you using Hyper.app? I could imagine that this happens with Hyperterm.

Okay, I think I got the same issue since Hyper 1.0, so I was able to look into it & fix it. 🎉  At least it works for me again. Can someone confirm this?

@kevingelion @WoodyWoodsta

Works for me! Thanks! 🎉

So I actually noticed now that, even with your example .hyperlayout from the README with printing Hello and World, that only the first command will get run. So I'll type hyperlayout in bash, and the first pane will echo Hello, then the second pane will open but nothing will happen. I can continue adding panes and it still gets to the second and stops. Should I open another issue?

Updated hyperlayout and hyper and tried the simple test as below:
[[
  "echo 1",
  "echo 2"
]]

It's still splitting the window correctly, but both commands are being run in the first pane.

Great! 👍 Does anyone of you  remeber why the original Issue (Printing out the raw config) happend? Still seems to be a problem according to #12

Unfortunately I did not get to the bottom of that. If I had the time, I would dig into the module and try and find out :frowning_face:

I have a fix which I could test on my Windows 10 machine. I'll submit a PR and then someone else can test it on a Mac/Linux :)

I accidentally added a broken linked to the PR but fixed it now.

I've had the same issue (printing the config) and restarting Hyper fixed the issue

I have currently the issue (printing the config).
Windows 7 SP1
Hyper 1.3.1
zsh (with babun http://babun.github.io/)
~/.hyperlayout
[[   "echo 1",   "echo 2" ]]
❯ hyperlayout
[hyperlayout config]:{"config":{"entry":"tab","layout":[["echo 1","echo 2"]]},"cwd":"C:\Users\cyril.moreau"}

I can replicate the "printing out config" issue, by typing hyperlayout right after installing the plugin. After restarting hyper though it's gone.
I still have trouble getting hyperlayout to work though... after typing hyperlayout the window just freezes, and dev tools throws a syntax error about unexpected token in JSON.

Also fixed by implementing this #16 by hand solved. Would be nice to get that merged.

Still happening on Windows 7 x64 with Hyper 2.0.0 - the same .hyperlayout file works fine on linux and macos (hyperlayout 0.2.1)

I have the same issue, Windows 10 Hyper 2.0.0. When I run hyperlayout all I get is hyperlayout config]:{"config":{"entry":"tab","layout":[["echo 'Hello'","echo 'World'"]]},"cwd":"C:\\Users\\ScriptPup"}
My .hyperlayout file is very simple
[
  [
    "echo 'Hello'",
    "echo 'World'"
  ]
]
[
  [
    "echo 'Hello'",
    "echo 'World'"
  ]
]

Same Issue with Hyper v3

https://github.com/timolins/hyperlayout/commit/07e0a978cdb5a14aec539dd9e44f01936f13a4f9#diff-1818e7e7bdb050f4deb1fe38c76041a2L77


dbeaver/pro#2925 Add schema and catalog to qm

Added schema and catalog to view of the record in qm

Please provide a screenshot

Verified


Validation issue with +380721036177

Country/region affected (e.g., "SI"): UA
Example number(s) affected ("+1<PHONE_NUMBER>"): +380721036081
The phone number range(s) to which the issue applies ("+1 555 555-XXXX"): +38072XXXXXXX
The type of the number(s) ("fixed-line", "mobile", "short code", etc.): mobile
The cost, if applicable ("toll-free", "premium rate", "shared cost"): shared cost
Supporting evidence (for example, national numbering plan, announcement from mobile carrier, news article): announcement from mobile carrier
IMPORTANT - anything posted here is made public. Read the guidelines first!
Link
http://lugacom.su/
Contacts
+38 (072) 103-61-77
+38 (072) 103-60-88
+38 (0642) 33-11-10
Link to Hofer Telekom contact page, where the demo phone was taken from
http://lugacom.su/dlya-biznesa/kontaktnaya-informatsiya_biz/
http://libphonenumber.appspot.com/phonenumberparser?number=%2B38072106081

@lugacom2015,
Thanks for providing all the details we need! We've accepted this issue and will fix this in an upcoming release. For your next metadata issue, we invite you to file issues in Google's new Issue Tracker, which we're currently testing.
Please note that you have submitted this information with the knowledge that we may use, modify, reproduce, publicly display, and distribute the information in accordance with our open source policies. Please let us know if you did not intend to submit the information for such use.

Fixed in release 8.6.0


Please update podspec to 0.2.0

Podspec points to 0.1.5 but latest release is 0.2.0.

Ah! Nice catch. Sorry about that @jingx23. Thanks@intelliot!


Difference version of this app already installed in OnPrem (SP 2019)

I have created a SPFx extension and deployed it to the app catalog in On-Prem (SP 2019). For some of the time, when I install the app to site it throws an error "Difference version of this app already installed", but I did not install the app to that erroring site. When i installing the same app to different site collection it was installing. I have checked the Recycle bin (Admin, Secondary recycle bin) also. There is no reference to my app in the site. Can anyone please help!!!!

I have created a SPFx extension and deployed it to the app catalog in On-Prem (SP 2019). For some of the time, when I install the app to site it throws an error "Difference version of this app already installed", but I did not install the app to that erroring site. When i installing the same app to different site collection it was installing. I have checked the Recycle bin (Admin, Secondary recycle bin) also. There is no reference to my app in the site. Can anyone please help!!!!

Is there any update on this!!!!

Steps to Reproduce:

Create site with 3 Level subsites ex. Site A -> Subsite A-1 -> Subsite A-1-1
Create SPFx app and deploy to farm (App catalog) and add to site (Site A and Subsite A-1)
Change SPFx some code  or files (don't change the version)
Redeploy App to App catalog
Add app to the Subsite A-1-1 (Throws error "Difference version of this app already installed"), If it is success change the code(don't change the version) redeploy.

SPFx Libraries Version : ~1.4.1

@shahulcode  - The issue you are seeing is because what you are doing is not supported.  This will happen in SharePoint online as well.  When you modify your package you MUST update the version number.  When you install a package it creates a hash of the package and saves it as a fingerprint.  If this fingerprint changes but the version has not, and you have previously installed the solution already on that site collection (why this only happens using multiple webs), you will receive this error.  This can be easily fixed by just modifying the version number when updating a package.

if i doing so, should i need to update the app version all sites?


InvalidArgumentException in WritableStream.php line 105: MongoDB\BSON\UTCDateTime::__construct() expects exactly 1 parameter, 0 given

https://github.com/mongodb/mongo-php-library/blob/master/src/GridFS/WritableStream.php#L105
http://php.net/manual/en/mongodb-bson-utcdatetime.construct.php

Removing mongodb/mongodb (1.1.0)
Installing mongodb/mongodb (1.1.1)

The 1.1.x series of the PHP library requires ext-mongodb 1.2.0+. Since extension version 1.2.0, the UTCDateTime constructor defaults to the current time if no arguments are provided (see: PHPC-536). If you are installing the library with Composer, it should have caught this when checking the platform requirements. If you're installing manually, you'll need to ensure your extension is current when upgrading the PHP library.
Regardless, the UTCDateTime::__construct() documentation needs to be updated for 1.2.0. I'll take care of that shortly.

PHP.net documentation updated here. Changes should be live in a few days.


feat: Make DLQ buffer size configurable

If commit isn't being called regularly, it may grow too large, let users configure the buffer size.

what is our plan if we want to dlq a message outside of the buffer? crashloop the consumer and hope we have more luck next time?

Yeah, that's pretty much it. But I figure this is a more rare case where the consumer is misconfigured AND there's an invalid message.


question about the code

https://github.com/gengshan-y/VCN/blob/00c4befdbdf4e42050867996a6f686f52086e01a/dataloader/flow_transforms.py#L186-L189
Hi, could you please explain what this exit condition means? thx!

It checks whether the 4 corners of the warped image lie within the original image, and break (with success) if they are in.


Add checksum-md5 command

This adds a checksum-md5 command to espflash.
e.g.
❯ espflash checksum-md5 --address 0x10000 --length 0x1000 --no-stub
[2023-12-27T11:39:27Z INFO ] Serial port: 'COM22'
[2023-12-27T11:39:27Z INFO ] Connecting...
[2023-12-27T11:39:27Z WARN ] Setting baud rate higher than 115,200 can cause issues
0x95d0df6456de4ac114251a67a5f85

While this is not too exciting on its own, it's the ground work for #259 and #479
It's very unfortunate that the Rust flasher-stub currently doesn't implement the required command while the ROM code and the C based flasher stub does. (Verified by temporarily reverting the stubs locally). Maybe we should revert the change to use the Rust flasher-stub (but use it based on a feature at build time) until it's supported there
I checked the result with reading a flash region with esptool and running md5sum on it.

It's very unfortunate that the Rust flasher-stub currently doesn't implement the required command while the ROM code and the C based flasher stub does. (Verified by temporarily reverting the stubs locally). Maybe we should revert the change to use the Rust flasher-stub (but use it based on a feature at build time) until it's supported there:

The initial idea of the Rust stub, was to put them behind a feature, but we decided not to do that because nobody will use the feature. That being said, we now have an argument to do so or to go back to the C stubs or just force to use --no-stub for this subcommand until esp-rs/esp-flasher-stub#43 is implemented

BTW I also currently cannot flash the H2 with the current stub - we really need to be very confident that the stub works for us (including MD5) before we force every user to use it (while I agree that no average user will use such a feature we could agree to use it in our team - it's kind of a chicken and egg problem)

Current main of esp-flasher-stub should be able to flash all targets, we should probably cut a release and update them in espflash. But I agree, current state of espflash is not good as you can't flash many targets, I'm happy to add the Rust stubs behind a feature.

In any case, that behind the scope of this PR, I'll do some testing tomorrow morning and update with the results!

I locally updated the flasher stubs ( commit 2b0b0f0de5020e6d5e2bf39e8950d49737fd5edb ) and it works for all chips - also flashing H2 works now for me
I'm still not sure if we should add a feature to choose the old vs the new stub. e.g. the new stub doesn't support 26 MHz xtals - maybe having at least a feature to force using the old stubs might be helpful for those users (but certainly not scope of this PR)

I'm still not sure if we should add a feature to choose the old vs the new stub. e.g. the new stub doesn't support 26 MHz xtals - maybe having at least a feature to force using the old stubs might be helpful for those users (but certainly not scope of this PR)

Is the 26 MHz a stub issue? I don't have any 26 MHz board so I cant test it. We have https://github.com/esp-rs/espflash/issues/526, but that's a bootloader issue. This definitely needs some investigation, so I'll try to get some 26 MHz devkit

I'm still not sure if we should add a feature to choose the old vs the new stub. e.g. the new stub doesn't support 26 MHz xtals - maybe having at least a feature to force using the old stubs might be helpful for those users (but certainly not scope of this PR)

Is the 26 MHz a stub issue? I don't have any 26 MHz board so I cant test it. We have #526, but that's a bootloader issue. This definitely needs some investigation, so I'll try to get some 26 MHz devkit

Yes it works with --no-stub ... so probably we don't need that feature ... I forgot there is --no-stub 😆