config:python.pythonPath is not the active conda env when running tasks

Issue Type: Bug
Hi every one,
Don't know what happend that now when I run a task my python points to other environement. Any one knows why?
See image bellow:

Any clue? Thank you in advance!
Extension version: 2021.6.944021595
VS Code version: Code 1.58.2 (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:10:15.214Z)
OS version: Windows_NT x64 10.0.18363
Restricted Mode: No
Remote OS version: Linux x64 5.4.72-microsoft-standard-WSL2

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 x 3411)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.98GB (3.88GB free)

Process Argv
--crash-reporter-id 374583dc-5a50-46a8-a2bc-0e19ed58e733

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu-20.04

OS
Linux x64 5.4.72-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 x 3411)

Memory (System)
12.47GB (6.84GB free)

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30311712
vspre833:30321513
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30322572
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255:30335481
vscod805:30301674
pythonvspyt200:30331937
vscextlangct:30333562
binariesv615:30325510
vsccppwtct:30329789
bridge0708:30335490

Hi, ${config:python.pythonPath} is now deprecated as we plan to remove python.pythonPath setting. Try using ${command:python.interpreterPath} instead.
Although I think we added something to automatically migrate ${config:python.pythonPath} to ${command:python.interpreterPath}, so not sure why you still see that in your launch.json file.

I've copied this old variable ${config:python.pythonPath} from the (vscode web)

The new docs will go out very soon (I think today🙂) which should contain the updated details.

Is there any list to consult the env-variables related to python in order to easily code my custom tasks??

I think this should help you out, it states how you can initialize your environment variables which the extension can read from. Closing this.

Hi again @karrtikr, my task is broken again because when I run the task the default shell is not initialized with the conda environment selected in the project. I use this small task to check it:
{
            "label": " echo conda env",
            "type": "shell",
            "command": "echo $CONDA_DEFAULT_ENV",
        }

I can run my tests, I run them pointing directly to the ${command:python.interpreterPath} but some of them fail...
when there is no active environment or when the active environment is the project's one I achieve to pass all the tests correctly using the same command. I checked this directly running in a WSL terminal.
So, I think that I am missing something to activate a specific conda environment when I run the tasks or if this process should be automatic, something is wrong in my vs code... Can you please help me? I attached my entire tasks.json
{
    "version": "2.0.0",
    "tasks": [
        {
            "label": " echo conda env",
            "type": "shell",
            "command": "echo $CONDA_DEFAULT_ENV",
        },
        {
            "label": "run tests",
            "type": "shell",
            "command": "${command:python.interpreterPath}",
            "args": [
                "-m",
                "pytest",
                "--cov=./"
            ],
        },
        {
            "label": "run coverage",
            "type": "shell",
            "command": "$(dirname ${command:python.interpreterPath})/coverage-badge -o coverage.svg -f",
        },
        {
            "label": "run test and coverage",
            "type": "shell",
            "command": "echo",
            "args": [
                "TEST AND COVERAGE SUCCESSFULLY CREATED!"
            ],
            "dependsOrder": "sequence",
            "dependsOn": [
                "run tests",
                "run coverage"
            ]
        },
    ]
}

Thank you very much in advance!

This looks like a different issue and also doesn't seem to be related to the Python extension as VSCode itself is responsible for running tasks. I would recommend creating an issue in the vscode repo, or create a new issue in our repo filling the issue template. Thanks.


Switch 2.0.0 release to tags

Description
Switching the manifest over to tags
Note; I figured I would update all projects, when this passes CI it indicates that all repositories have cut release tags.
Issues Resolved
Completes finalize the release of https://github.com/opensearch-project/opensearch-build/issues/1624
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Close this as 2.0.0 is pointing to GA no need for tags.

@peterzhuamazon Did we need to create tags for rc1 then?

@peterzhuamazon Thanks for the heads up!


Change sizes of inputs

Incrise some pixels on Qtde.
Reduce some pixels on Price
Validate in differents sizes if will be fluid.

61110a39f7d337fe50b7e774ae773939dba18fba


Remove :feature:autodiscovery:srvrecords

Remove :feature:autodiscovery:srvrecords as it's not used anymore

This code was never used. But we want to support DNS SRV records eventually. See #4721.


feat: add storage gaps to contracts

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.08%) to 78.877%

Files with Coverage Reduction
New Missed Lines
%

contracts/root/CheckpointManager.sol
1
96.81%

Totals

Change from base Build<PHONE_NUMBER>:
-0.08%

Covered Lines:
1335

Relevant Lines:
1637

💛  - Coveralls


Ensure quick-add dialog does not obscure ghost node when shifted

The change in 3.0 to make the Quick Add dialog taller didn't get carried through to the code that repositions the menu if it goes off the bottom of the screen. As a result, it was covering the ghost node.
This PR adds the additional height into the calculations

Coverage increased (+0.03%) to 68.225% when pulling e120bad779017682d64bf071bc950946c48db93b on ts-pos into 1b94cc3ac027bfc38a300867a0b0fd635bf273b8 on master.


Improved CLI

~### If you have an issue with a specific extension or type~
~Locate the definition for your extension/type in the db.json file in the mime-db project.  Does it look right?~
~- [ ] No. File a mime-db issue.~
~- [ ] Yes: Go ahead and submit your issue/PR here and I'll look into it.~
This Pull Request is related to the CLI
I added in the version flag, the help flag, and the name flag with a few improvements to the CLI.

This looks good, thanks!  Merging, but I'm going to hold off on publishing this until I've had a chance to add tests for the CLI, to make sure this runs on the supported node versions.

This looks good, thanks!  Merging, but I'm going to hold off on publishing this until I've had a chance to add tests for the CLI, to make sure this runs on the supported node versions.

Published as<EMAIL_ADDRESS>

Published as<EMAIL_ADDRESS>


Specify only IPv4 or IPv6 Outbound

What is the handling of ipv4/ipv6 outbound from server? Is it possible to specify only ipv4 or ipv6 outbound hosts if server has both ipv4 and ipv6 address?

Please check the "Local bind ip" section in the README file


[fix][sec] Bump commons-text to 1.10.0 fix CVE-2022-42889

Motivation
Fixes CVE-2022-42889
Modifications
Bump apache commons-text version to 1.10.0.
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

you have to update the license files also

Ok, I already updated it.

Codecov Report

Merging #18053 (5f1532f) into master (6c65ca0) will increase coverage by 15.79%.
The diff coverage is 60.00%.

@@              Coverage Diff              @@
##             master   #18053       +/-   ##
=============================================
+ Coverage     34.91%   50.71%   +15.79%
- Complexity     5707     8686     +2979
=============================================
  Files           607      607
  Lines         53396    53400        +4
  Branches       5712     5712
=============================================
+ Hits          18644    27082     +8438
+ Misses        32119    23276     -8843
- Partials       2633     3042      +409

Flag
Coverage Δ

unittests
50.71% <60.00%> (+15.79%)
:arrow_up:

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

Impacted Files
Coverage Δ

.../service/SystemTopicBasedTopicPoliciesService.java
62.97% <0.00%> (+11.38%)
:arrow_up:

...g/apache/pulsar/compaction/CompactedTopicImpl.java
69.28% <0.00%> (+58.57%)
:arrow_up:

...broker/delayed/InMemoryDelayedDeliveryTracker.java
65.00% <75.00%> (+65.00%)
:arrow_up:

...pulsar/broker/admin/impl/PersistentTopicsBase.java
52.24% <100.00%> (+40.84%)
:arrow_up:

...rg/apache/pulsar/broker/service/BrokerService.java
57.76% <100.00%> (+9.76%)
:arrow_up:

...ar/broker/loadbalance/impl/BundleSplitterTask.java
60.00% <0.00%> (-17.78%)
:arrow_down:

...apache/pulsar/broker/service/TopicListService.java
42.62% <0.00%> (-12.30%)
:arrow_down:

...tent/NonPersistentDispatcherMultipleConsumers.java
40.74% <0.00%> (-7.41%)
:arrow_down:

...r/io/kafka/connect/AbstractKafkaConnectSource.java
57.02% <0.00%> (-1.66%)
:arrow_down:

...pache/pulsar/proxy/server/ProxyServiceStarter.java
60.66% <0.00%> (-1.34%)
:arrow_down:

... and 141 more


Remove linkcheck parser from docs pages

See https://trello.com/c/a1E2H77k/608-update-contributing-docs-to-reflect-latest-docs-build-changes - when Sphinx was upgraded, the jobs were reconfigured and no longer use the linkcheck parser so they now fail (red) when there are broken links and you need to look in the console output to find the issue.

Fixed @sbesson comment, merging and deploying


Support for other models

Whether to support LLM models other than LLaMA, Mistral and Mixtral families, such as Chameleon

Hi, @ChinChyi!
Thanks for the suggestion. At the moment, I don't think we have the capacity to work on this, but I'll keep this in mind. Maybe later, if we have time or find someone interested in working on it.


Create deployment-with-docker.rst

Just a little extra clarity on postgres and the .env file, inspired by #1188.

thanks @mekhami