added
stringdate 2025-04-01 04:05:38
2025-04-01 07:14:06
| created
timestamp[us]date 2001-10-09 16:19:16
2025-01-01 03:51:31
| id
stringlengths 4
10
| metadata
dict | source
stringclasses 2
values | text
stringlengths 0
1.61M
|
|---|---|---|---|---|---|
2025-04-01T04:34:43.083743
| 2023-01-09T10:57:36
|
1525350202
|
{
"authors": [
"UnChallenged",
"jhm-ciberman"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8526",
"repo": "microsoft/mssql-docker",
"url": "https://github.com/microsoft/mssql-docker/issues/800"
}
|
gharchive/issue
|
Support MSSQL_DB, MSSQL_USER and MSSQL_PASSWORD env variables (Bump #2)
This issue is just to bump #2. Currently using SQL Server for local environment or CI is a nightmare.
DB Engine
Has init DB variables?
DB2
:white_check_mark:
InfluxDB
:white_check_mark:
MariaDB
:white_check_mark:
MongoDB
:white_check_mark:
MS SQL Server
:x:
MySQL
:white_check_mark:
Neo4j
:white_check_mark:
PostgreSQL
:white_check_mark:
https://github.com/microsoft/mssql-docker/issues/2
any date regarding adding support for MS SQL Server?
|
2025-04-01T04:34:43.095072
| 2020-08-11T15:07:22
|
676955032
|
{
"authors": [
"freddydk",
"mhenricus"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8527",
"repo": "microsoft/navcontainerhelper",
"url": "https://github.com/microsoft/navcontainerhelper/issues/1214"
}
|
gharchive/issue
|
New-BcContainter -multitenant switch seems no working
Describe the issue
Some findings and questions about the -multitenant switch for New-BcContainer.
The Get-Help says:
-multitenant [<SwitchParameter>]
Setup container for multitenancy by adding this switch
Required? false
Position? named
Default value False
Accept pipeline input? false
Accept wildcard characters? false
I remember having read that for New-NavContainer the default option was 'false', for New-BcContainer the default option seems to be 'True'.
Using -multitenant $false, or -multitenant false or -multitenant no do not work. What should it be?
There seems to be no CRONUS demo data in the multitenant W1. Is this correct?
Question
what is the purpose of database 'tenant' that is created in sql server?
Scripts used to create container and cause the issue
$sasToken = "..."
$artifactURL = Get-BCArtifactUrl -storageAccount "bcinsider" -type "sandbox" -country "w1" -select "latest" -sasToken $sasToken
$licenseFile = "C:\Temp\DEV.flf"
$credential = New-Object PSCredential 'admin', (ConvertTo-SecureString -String '...' -AsPlainText -Force)
New-BCContainer -accept_eula `
-accept_outdated `
-containerName $containerName `
-artifactURL $artifactURL `
-auth UserPassword `
-Credential $credential `
-licenseFile $licenseFile `
-updateHosts `
-assignPremiumPlan `
-includeAL `
-isolation process `
-dns <IP_ADDRESS> `
-doNotCheckHealth `
-memoryLimit 6G `
-alwaysPull `
**-multitenant false ` / -multitenant $false / -multitenant no** > I have tried all 3
-shortCuts Desktop
Full output of scripts
BcContainerHelper is version 1.0.2
BcContainerHelper is running as administrator
Host is Microsoft Windows 10 Pro - 2004
Docker Client Version is 19.03.12
Docker Server Version is 19.03.12
ArtifactUrl and ImageName specified
Fetching all docker images
Image no:sandbox-17.0.15441.0-w1-mt doesn't exist
Building multitenant image no:sandbox-17.0.15441.0-w1-mt based on https://bcinsider.azureedge.net/sandbox/17.0.15441.0/w1
Building image no:sandbox-17.0.15441.0-w1-mt based on mcr.microsoft.com/dynamicsnav:10.0.19041.388-generic
no:sandbox-17.0.15441.0-w1-mt
Pulling latest image mcr.microsoft.com/dynamicsnav:10.0.19041.388-generic
10.0.19041.388-generic: Pulling from dynamicsnav
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.19041.388 (2004)
Host OS Version: 10.0.19041.388 (2004)
Using process isolation
Files in c:\bcartifacts.cache\tmp637327610323425213\my:
Copying Platform Artifacts
Copying Database
Copying Licensefile
Copying Extensions
c:\bcartifacts.cache\tmp637327610323425213
Sending build context to Docker daemon 1.528GB
Step 1/6 : FROM mcr.microsoft.com/dynamicsnav:10.0.19041.388-generic
---> a2c32f8f325c
Step 2/6 : ENV DatabaseServer=localhost DatabaseInstance=SQLEXPRESS DatabaseName=CRONUS IsBcSandbox=Y artifactUrl=...
---> Using cache
---> b50ed9b46ace
Step 3/6 : COPY my /run/
---> Using cache
---> b21c086b5414
Step 4/6 : COPY NAVDVD /NAVDVD/
---> 53176d282c52
Step 5/6 : RUN \Run\start.ps1 -installOnly -multitenant
---> Running in 167cab96a95d
Using installer from C:\Run\150-new
Installing Business Central
Installing from DVD
Starting Local SQL Server
Starting Internet Information Server
Copying Service Tier Files
Copying PowerShell Scripts
Copying dependencies
Copying ReportBuilder
Importing PowerShell Modules
Determining Database Collation
Restoring CRONUS Demo Database
Exporting Application to CRONUS
Removing Application from tenant
Modifying Business Central Service Tier Config File for Docker
Creating Business Central Service Tier
Installing SIP crypto provider: 'C:\Windows\System32\NavSip.dll'
Starting Business Central Service Tier
Importing CRONUS license file
Copying Database on localhost\SQLEXPRESS from tenant to default
Taking database tenant offline
Copying database files
Attaching files as new Database default
Putting database tenant back online
Mounting tenant database
Mounting Database for default on server localhost\SQLEXPRESS
Sync'ing Tenant
Tenant is Operational
Stopping Business Central Service Tier
Copying Web Client Files
Copying Client Files
Copying ModernDev Files
Copying additional files
Copying ConfigurationPackages
Copying Test Assemblies
Copying Extensions
Copying Applications
Installation took 293 seconds
Installation complete
Removing intermediate container 167cab96a95d
---> f1d8b72aa7fc
Step 6/6 : LABEL legal="http://go.microsoft.com/fwlink/?LinkId=837447" created="202008111444" nav="" cu="" multitenant="Y" country="W1" version="17.0.15441.0" platform="17.0.15352.0"
---> Running in 142a0c98a23c
Removing intermediate container 142a0c98a23c
---> adbdca4c9699
Successfully built adbdca4c9699
Successfully tagged no:sandbox-17.0.15441.0-w1-mt
Building image took 508 seconds
Using image no:sandbox-17.0.15441.0-w1-mt
Disabling Health Check (always report healthy)
Creating Container bci-w1-7
Version: 17.0.15441.0-W1
Style: sandbox
Multitenant: Yes
Platform: 17.0.15352.0
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.19041.388 (2004)
Host OS Version: 10.0.19041.388 (2004)
Using process isolation
Using locale en-US
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file C:\Temp\IGO DEV ISV 7241751 200714.flf
Files in C:\ProgramData\BcContainerHelper\Extensions\bci-w1-7\my:
- AdditionalOutput.ps1
- license.flf
- MainLoop.ps1
- SetupNavUsers.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container bci-w1-7 from image no:sandbox-17.0.15441.0-w1-mt
dcf54ec3fb97c465033f25743a200fda6609d93897d93a71c611c57509eec427
Waiting for container bci-w1-7 to be ready
Initializing...
Setting host.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to <IP_ADDRESS> in container hosts file
Starting Container
Hostname is bci-w1-7
PublicDnsName is bci-w1-7
Using NavUserPassword Authentication
Starting Local SQL Server
Starting Internet Information Server
Creating Self Signed Certificate
Self Signed Certificate Thumbprint 748687A7B3B60ECE84FF9760B54AB0D3DD0FE8B7
Modifying Service Tier Config File with Instance Specific Settings
Starting Service Tier
Registering event sources
Creating DotNetCore Web Server Instance
Enabling Financials User Experience
Using license file 'c:\run\my\license.flf'
Import License
Tenant is Mounted
Creating http download site
Setting SA Password and enabling SA
Creating admin as SQL User and add to sysadmin
WARNING: This license is not compatible with this version of Business Central.
Creating SUPER user
WARNING: This license is not compatible with this version of Business Central.
WARNING: This license is not compatible with this version of Business Central.
WARNING: This license is not compatible with this version of Business Central.
Assign Premium plan for ADMIN
Container IP Address: <IP_ADDRESS>
Container Hostname : bci-w1-7
Container Dns Name : bci-w1-7
Web Client : http://bci-w1-7/BC/?tenant=default
Dev. Server : http://bci-w1-7
Dev. ServerInstance : BC
Dev. Server Tenant : default
Setting bci-w1-7 to <IP_ADDRESS> in host hosts file
Files:
http://bci-w1-7:8080/ALLanguage.vsix
Initialization took 69 seconds
Ready for connections!
Reading CustomSettings.config from bci-w1-7
Creating Desktop Shortcuts for bci-w1-7
Extracting C:\Applications\BaseApp\Source\Base Application.Source.zip
Creating .net Assembly Reference Folder for VS Code
Copying DLLs from C:\Windows\assembly to assemblyProbingPath
Copying DLLs from C:\Program Files\Microsoft Dynamics NAV\170\Service to assemblyProbingPath
Copying DLLs from C:\Program Files (x86)\Microsoft Dynamics NAV\170\RoleTailored Client to assemblyProbingPath
Copying DLLs from C:\Test Assemblies\Mock Assemblies to assemblyProbingPath
Copying DLLs from C:\Program Files (x86)\Open XML SDK to assemblyProbingPath
Container bci-w1-7 successfully created
Screenshots
na
Additional context
does it happen all the time? yes
did it use to work? I think to remember it worked with New-NavContainer
https://freddysblog.com/2019/08/04/powershell-for-non-experts/ - search Switch vs. Boolean
-multitenant:$false
is the syntax (which my blog post from today also states)
New-BcContainer and New-NavContainer is the same - one is an alias for the other.
Sandbox containers are default multitenant in BcContainerHelper 1.0.1 and later.
All described here: https://freddysblog.com/2020/08/11/bccontainerhelper/
Freddy, thanks for the quick reply and answering questions I could have known. Sorry for wasting your time.
Can you give me quick reply on the other 2 questions I have (which I probably could have found elsewhere as well).
What is the purpose of database 'tenant' that is created in sql server? Can you explain about the 3 databases created when using the multitenant switch?
There seems to be no CRONUS demo data in the W1 database anymore, multitenant or not. I am pretty sure that there used to be. Is this correct?
The tenant database is the template database for new tenants.
The default database is the database for the default tenant.
New-BcContainerTenant creates a new tenant by copying the tenant database and mounting it.
There are no demo data in w1 sandbox databases and hasn't been for a very long time.
base (instead of w1) contains onprem demo data.
onprem has demo data,
Thanks. Then I mixed up Sandbox and OnPrem W1.
|
2025-04-01T04:34:43.097655
| 2020-11-12T05:46:42
|
741299521
|
{
"authors": [
"AlisaChen98"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8528",
"repo": "microsoft/nnfusion",
"url": "https://github.com/microsoft/nnfusion/issues/123"
}
|
gharchive/issue
|
parallel training support
ETA
test-owner @xiayuqing0622 1 day
parallel training support (via SuperScaler)
[ ] v0.1 intergation
[ ] document
@xiayuqing0622 Please check whether the code on the superscaler dev branch can be used for testing
|
2025-04-01T04:34:43.099243
| 2021-12-27T05:26:22
|
1088976805
|
{
"authors": [
"J-shang"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8529",
"repo": "microsoft/nni",
"url": "https://github.com/microsoft/nni/pull/4428"
}
|
gharchive/pull-request
|
[Bugbash] fix pre-masks inherit
Description
Split from pr #4423
e.g., if we set fine-grained pre-masks to a channel-wise pruner, then the generated masks will be channel-wise masks and may not inherit the fine-grained pre-masks. This pr is for inheriting the pre-maks.
for the second point, it might be better to also print warning message
Hi @QuanluZhang , this is the pr split from #4423 point 2nd.
What warning message should we add for users?
|
2025-04-01T04:34:43.102874
| 2024-12-03T05:34:49
|
2714044621
|
{
"authors": [
"elephantpanda"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8530",
"repo": "microsoft/onnxruntime-genai",
"url": "https://github.com/microsoft/onnxruntime-genai/issues/1112"
}
|
gharchive/issue
|
Bug DMLFusedNode_0_0 on second token in 0.5.2 (DML) (Wrong tensor shape)
I updated to 0.5.2 DirectML mode. Quadro P5000 GPU. Windows. C# DirectML 1.15.4. Model: microsoft/Phi-3-mini-4k-instruct-onnx
I get the following bug. (Bug only comes up in DML mode not CPU mode. It worked in version 0.4.0).
For any prompt e.g.
"<|user|>Hello <|end|><|assistant|>"
(tokens:)
1,32010,15043,29871,32007,32001
It outputs one token but then when trying to output the second token it errors out with:
OnnxRuntimeGenAIException: Non-zero status code returned while running DmlFusedNode_0_0 node. Name:'DmlFusedNode_0_0' Status Message: D:\a\_work\1\s\onnxruntime\core\framework\execution_frame.cc:173 onnxruntime::IExecutionFrame::GetOrCreateNodeOutputMLValue shape && tensor.Shape() == *shape was false. OrtValue shape verification failed. Current shape:{1,32,7,96} Requested shape:{1,32,2048,96}
Microsoft.ML.OnnxRuntimeGenAI.Result.VerifySuccess (System.IntPtr nativeResult) (at D:/a/_work/1/onnxruntime-genai/src/csharp/Result.cs:25)
Microsoft.ML.OnnxRuntimeGenAI.Generator.ComputeLogits () (at D:/a/_work/1/onnxruntime-genai/src/csharp/Generator.cs:25)
Main.Generate () (at Assets/Main.cs:202)
The relevant part seems to be: Current shape:{1,32,7,96} Requested shape:{1,32,2048,96}
I have "solved" this bug by commenting out this line in my code:
generatorParams.SetSearchOption("past_present_share_buffer", false);
I don't know if that is important or not.
|
2025-04-01T04:34:43.135555
| 2023-09-19T16:32:29
|
1903351208
|
{
"authors": [
"brianrob",
"mahamr"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8531",
"repo": "microsoft/perfview",
"url": "https://github.com/microsoft/perfview/issues/1913"
}
|
gharchive/issue
|
Using /dumpheap with /nogui or /logfile results in hang
We had a customer run into this issue (using the latest, though based on what I see in code it probably will happen with any version) - you can repro it by running the below command:
PerfView.exe "/DataFile:PerfViewData.etl" /BufferSizeMB:256 /StackCompression /DumpHeap /nogui collect
The command works fine if removing /DumpHeap, or if leaving that but allowing it to pop the GUI instead of not. I believe I have the correct analysis below of the behavior.
The command above results in the below output, and hangs here indefinitely:
VERBOSE LOG IN: PerfViewData.log.txt
EXECUTING: PerfView /DataFile:PerfViewData.etl /BufferSizeMB:256 /StackCompression /DumpHeap /nogui collect
Pre V4.0 .NET Rundown disabled, Type 'E' to enable symbols for V3.5 processes.
Do NOT close this console window. It will leave collection on!
Type S to stop collection, 'A' will abort. (Also consider /MaxCollectSec:N)
Kernel Log: C:\Windows\System32\PerfViewData.kernel.etl
User mode Log: C:\Windows\System32\PerfViewData.etl
Starting collection at 9/19/2023 10:46:04 AM
Manually Stopped (NoGui)
I captured a dump and this is the main thread's stack:
09 mscorlib_ni!System.Threading.WaitHandle.WaitOne
0a PerfView!PerfView.CommandProcessor.GuiHeapSnapshot
0b PerfView!PerfView.CommandProcessor.Stop
0c PerfView!PerfView.CommandProcessor.Collect
0d PerfView!PerfView.CommandProcessor.ExecuteCommand
0e PerfView!PerfView.App.DoMain
0f PerfView!PerfView.App.Main
This looks to be the code here:
https://github.com/microsoft/perfview/blob/v3.1.5/src/PerfView/CommandProcessor.cs#L1901
public void GuiHeapSnapshot(CommandLineArgs parsedArgs, bool waitForCompletion)
{
#if !PERFVIEW_COLLECT
// We'll wait on this handle until the heap snapshot completes.
ManualResetEvent waitHandle = new ManualResetEvent(false);
if (GuiApp.MainWindow != null)
{
GuiApp.MainWindow.Dispatcher.BeginInvoke((Action)delegate ()
{
GuiApp.MainWindow.TakeHeapShapshot((Action)delegate ()
{
// Set the wait handle once the memory heap snapshot has been completed.
// This action will run in the memory dialog continuation.
waitHandle.Set();
});
});
}
if (waitForCompletion)
{
**waitHandle.WaitOne();**
}
#endif
}
When running the app via command line, with /NoGui or /LogFile, it appears this GuiApp.MainWindow property is not set:
0:000> !DumpClass /d 00007ffb9937ec68
Class Name: PerfView.GuiApp
...
MT Field Offset Type VT Attr Value Name
00007ffb99399b58 40003de 258 PerfView.MainWindow 0 static<PHONE_NUMBER>000000 MainWindow
Thus, it appears the ManualResetEvent is instantiated and waited on, but will never be Set() since the setting code is inside a block that will not execute if the MainWindow is null.
@mahamr thank you very much for reporting this, and for the analysis. It looks like the heap snapshot functionality in place here doesn't support capture via GUI. I'm planning to emit a warning in this case and proceed to stop collection.
|
2025-04-01T04:34:43.142777
| 2021-06-23T18:24:21
|
928528640
|
{
"authors": [
"hlaueriksson",
"kblok",
"pavelfeldman"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8532",
"repo": "microsoft/playwright-dotnet",
"url": "https://github.com/microsoft/playwright-dotnet/issues/1595"
}
|
gharchive/issue
|
[Question] What <PackageId> and namespace to use when publishing third party NuGet packages
I would like to publish NuGet packages that will use and offer extensions to Microsoft.Playwright.
(In a similar fashion as I have done with PuppeteerSharp)
What <PackageId> and namespace should I use?
The code is in this repo:
https://github.com/hlaueriksson/playwright-dotnet-contrib
My suggested PackageIds:
Playwright.Contrib.Extensions
Playwright.Contrib.FluentAssertions
Playwright.Contrib.PageObjects
My suggested namespaces:
Microsoft.Playwright.Contrib.Extensions
Microsoft.Playwright.Contrib.FluentAssertions
Microsoft.Playwright.Contrib.PageObjects
Is it OK to prefix the namespace with Microsoft.?
The reason behind this is to make it straightforward to use the static Playwright class:
using Microsoft.Playwright;
using Microsoft.Playwright.Contrib.Extensions;
var playwright = await Playwright.CreateAsync();
If I use the namespace Playwright.Contrib.Extensions then it will not be as easy to refer to the class Playwright.
I created this repo https://github.com/hardkoded/playwright-sharp-contrib/projects/1, but I only created the issues 🙈
I like your package ids and namespaces ideas. I think there is no issue using the Microsoft. namespace. You won't be able to create packages with those names tho.
I would only use Microsoft.* for something coming from Microsoft! Looks like we are on the same page already.
I ended up with both PackageId and namespace like this:
PlaywrightContrib.Extensions
PlaywrightContrib.FluentAssertions
PlaywrightContrib.PageObjects
Now available on NuGet: https://www.nuget.org/packages?q=PlaywrightContrib
|
2025-04-01T04:34:43.145964
| 2023-02-06T18:16:50
|
1573056874
|
{
"authors": [
"chasestarr",
"mxschmitt"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8533",
"repo": "microsoft/playwright-vscode",
"url": "https://github.com/microsoft/playwright-vscode/pull/301"
}
|
gharchive/pull-request
|
Pass playwright.env config to node calls
This will support pnp package managers (yarn 2, pnpm) by allowing NODE_OPTIONS to be configured within playwright.env and passed to node calls. For example, when using yarn 2 I can edit my .vscode/settings.json file to below and register the pnp.cjs file.
{
"playwright": {
"env": {
"NODE_OPTIONS": "-r ./.pnp.cjs"
}
}
}
@microsoft-github-policy-service agree company="Uber"
Hi, checking in again. Is this something the team is interested in reviewing?
Thanks for your PR, after the requested changes we're happy to add it.
Resolved the change requests. Thanks!
|
2025-04-01T04:34:43.228874
| 2020-04-07T08:55:14
|
595705738
|
{
"authors": [
"dhpollack",
"eladiw",
"msftclas",
"omri374"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8534",
"repo": "microsoft/presidio",
"url": "https://github.com/microsoft/presidio/pull/299"
}
|
gharchive/pull-request
|
organize protobuf files
Issue #297
To make the protobufs use relative imports, I did the following. If you
regenerate the protobuf files then you will have to run the last command
to get the relative imports to work correctly.
cd presidio-analyzer/presidio_analyzer
mkdir -p protobuf_models
mv *_pb2*.py protobuf_models/
cd protobuf_models
sed -i -E 's/^import.*_pb2/from . \0/' *.py
Signed-off-by: David Pollack<EMAIL_ADDRESS>
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: dhpollack sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.
thanks @dhpollack we will review this PR soon.
Thanks for your contribution!
The manual step is not ideal but it's a long standing issue with Google and how they generate the files. You can see the link in the issue that's attached to this PR. Instead of adding this functionality they insist that it's not need despite the hundreds of messages in the issue.
/azp run
@dhpollack If this fix: https://github.com/protocolbuffers/protobuf/issues/1491#issuecomment-542398041 would work, it's easier to maintain and doesn't require some post processing. WDYT?
@dhpollack If this fix: protocolbuffers/protobuf#1491 (comment) would work, it's easier to maintain and doesn't require some post processing. WDYT?
The comment after that one looks more fool-proof. I'll give that a try.
/azp run
It looks like the build is failing due to failure downloading the spacy models, even though all the tests are passing. It would be nice if you used the small spacy model as a default, so one can test presidio without having to download and build 800MB large model. Also, the English spacy models aren't actually "requirements" if someone were to use this library on non-English data.
We have an issue with the build agent which is currently being fixed (see https://github.com/microsoft/presidio/pull/300)
The reason we're using the big spaCy model is because it has NER capabilities which the small one doesn't, and some of our tests validate the output of the spaCy model. The current deployment is coupled with the English version and supporting deployments of other models requires some changes to the deployment pipeline.
/azp run
Hi @dhpollack,
We have fixed the build issue. can you fix the merge conflicts and we will merge this
@eladiw I rebased on master and then fixed the imports in the test. I think it should work now.
/azp run
|
2025-04-01T04:34:43.230718
| 2022-03-08T21:35:58
|
1163163499
|
{
"authors": [
"Jaqster",
"abchatra"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8535",
"repo": "microsoft/pxt-arcade",
"url": "https://github.com/microsoft/pxt-arcade/issues/4694"
}
|
gharchive/issue
|
Sim support for Makey Makey extension
Request from Makey Makey for simulator support of a Makey Makey extension.
Idea would be that a student could use their Makey Makey board as a game controller for playing Arcade games on the computer.
This is duplicate of https://github.com/microsoft/pxt-arcade/issues/4738
|
2025-04-01T04:34:43.232606
| 2023-10-06T14:52:32
|
1930348688
|
{
"authors": [
"AidanTilanus",
"Vegz78"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8536",
"repo": "microsoft/pxt-arcade",
"url": "https://github.com/microsoft/pxt-arcade/issues/6106"
}
|
gharchive/issue
|
Pause until doesn’t work in python
If i use a puase until block in my game (block editor) and switch to python i get a error on the pause until
OS: Windows
Browser chrome
As eleborated on here:
https://forum.makecode.com/t/pause-until-doesnt-work-in-python/22944
|
2025-04-01T04:34:43.249735
| 2022-05-16T15:48:47
|
1237357467
|
{
"authors": [
"RuceShao1994",
"erictraut"
],
"license": "CC-BY-4.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8537",
"repo": "microsoft/pylance-release",
"url": "https://github.com/microsoft/pylance-release/issues/2818"
}
|
gharchive/issue
|
Showing "Code is unreachable" but code actually works
Used Version 2022.5.1 and shows "Code is unreachable" after the line of using grad function from Autograd.
Change to Version 2022.4.3 and highlighting works normally.
Could you please provide a self-contained minimal code sample that demonstrates the problem? Diagnosing problems based on partial-code screen shots is difficult at best. Your sample should include import statements for any non-builtin symbols. It would also be useful to understand the versions of the library (or libraries) that you are importing.
OK, I think I've figured out the information I requested above.
Here's a self-contained minimal code sample:
from autograd import grad
def d(g):
grad(g)
print(g) # Unreachable
This is using the autograd library version 1.4 (installed via pip install autograd --upgrade).
Autograd is an untyped library, so pyright (the static type analyzer that underlies pylance) attempts to infer type information from the available source code.
The grad function calls a function _make_vjp. This in turn calls a class method VJPNode.new_root which calls an instance method Node.initialize_root. This instance method is implemented as assert False which will always raise an error. The method is not marked as an abstract method, and it doesn't raise a NotImplementedError, so pyright assumes that the method is not designed to be overridden.
I don't think there's much we can do in pyright or pylance to address this. Potential fixes include the following:
The maintainers of autograd could add type information to the next release of the library. Increasingly, library maintainers are doing this to improve the experience for developers who consume their library.
As a more surgical fix, the maintainers of autograd could update the Node.initialize_root method in tracer.py to be marked as @abstractmethod or raise a NotImplementedError rather than simply assert False.
You could find and install type stubs for this library. This provides type information such that pylance doesn't need to infer type information from the library's source code.
|
2025-04-01T04:34:43.271434
| 2022-09-07T18:13:44
|
1365343942
|
{
"authors": [
"MaiMeng1204",
"bogurd",
"cpoptic",
"heejaechang"
],
"license": "CC-BY-4.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8538",
"repo": "microsoft/pylance-release",
"url": "https://github.com/microsoft/pylance-release/issues/3300"
}
|
gharchive/issue
|
Intellisense autocomplete hangs at Loading... on Remote-SSH
Possibly related to Remote-SSH Python intellisense stuck at loading... microsoft/vscode-python#9045
Behaviour
Expected vs. Actual
Expected: Intellisense should show suggested code completions when pressing "control"+"space" and should Tab complete.
Actual: Intellisense does not show suggestion code completions when pressing "control"+"space". And Tab completion does not work either.
Steps to reproduce:
Use VS Code to connect remotely via SSH extension.
Open a .py or .ipynb file
Type import numpy as np
Start typing np. and after the dot, attempt to activate Intellisense via "Ctrl"+"space" to get autocomplete suggestions.
VS Code only shows "Loading..." and hangs indefinitely. No autocompletion is performed, and no function signature information is shown.
VS IntelliCode output shows:
Language server is set to Pylance.
Acquiring model
Acquiring model 'intellisense-members-lstm-pylance' for python
Querying IntelliCode service for available models.
vs-intellicode-python was passed a model: {}.
Cached model is up to date.
Activating Python extension
Diagnostic data
Python version (& distribution if applicable, e.g. Anaconda): 3.8.13
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
Value of the python.languageServer setting: Pylance
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
does this only happen on remote (SSH extension)? or happen when doing locally as well?
Just on remote SSH. It works fine locally
On Thu, Sep 8, 2022, 1:53 PM Heejae Chang @.***> wrote:
does this only happen on remote (SSH extension)? or happen when doing
locally as well?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/pylance-release/issues/3300#issuecomment-1241044709,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABXGFVIUCKYNCYNYVN7IVULV5IRZJANCNFSM6AAAAAAQHHR2RQ
.
You are receiving this because you authored the thread.Message ID:
@.***>
I have the same issue. Bisect cannot find a problem with extensions, and instead says it might be a VSCode problem. Have you managed to fix it @cpoptic?
related to https://github.com/microsoft/pylance-release/issues/3188
I can't repro this now. is this still an issue?
I just performed a clean install of the SSH server and updated to the latest (insiders) version. I didn't install any extensions in the server other than the recommended python extensions (VSCode prompt).
The issue still persists for me in this setup.
On Tuesday, Nov 29, 2022 at 11:10 PM, Heejae Chang @.*** @.***)> wrote:
I can't repro this now. is this still an issue?
—
Reply to this email directly, view it on GitHub (https://github.com/microsoft/pylance-release/issues/3300#issuecomment-1331385189), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AA64JJWTMMW34PJSUJVOSG3WKZ5M5ANCNFSM6AAAAAAQHHR2RQ).
You are receiving this because you commented.Message ID: @.***>
Can you provide us some logs as described in the troubleshooting guide?
...
I used ubuntu + OpenSSH server 3.0.2 (on ubuntu) + vscode insider (1.74.0-insider) windows + OpenSSH 3.0.2 client on windows
and everything seems working as expected.
Sorry for the large delay in response. Allowing for a trace level in the errors I saw that the error was very large enumeration of files, suggesting it could not parse the home directory anymore. When navigating to a directory with fewer files, the extension works as intended, nothing wrong with SSH at all.
Would it be wise to add a more descriptive message to the loading bar or a toast in the bottom right warning users of a potentially large directory which can halt the language server?
I believe we already have warning for such case. we would need more detail to know why it didn't work in your case. the log I mentioned above would help us to find out why it didn't work as well.
It's been a while since I had to use remote SSH, and I now notice that the intellisense gets activated after a few minutes. When I had first commented on the issue, the intellisense wouldn't start working for hours. Here's the logs both before and after intellisense started working.
Logs prior to intellisense
prior.txt
Logs after intellisense
after.txt
from you log, I see this
[Error - 11:59:45 AM] (167185) Enumeration of workspace source files is taking longer than 10 seconds.
This may be because:
* You have opened your home directory or entire hard drive as a workspace
* Your workspace contains a very large number of directories and files
* Your workspace contains a symlink to a directory with many files
* Your workspace is remote, and file enumeration is slow
To reduce this time, open a workspace directory with fewer files or add a pyrightconfig.json configuration file with an "exclude" section to exclude subdirectories from your workspace. For more details, refer to https://github.com/microsoft/pyright/blob/main/docs/configuration.md.
[Info - 12:02:24 PM] (167185) Found 241 source files
which means your workspace root (' /home/ipausers/katsikas/Projects') is pointing to a folder that has a lot more than py files you need (assuming since it only discovered 241 py files)
you should either try changing the root to more specific folder or use exclude to let us know which folder we should ignore.
I also see indexing is taking about 14 seconds to index your installed packages. take a look at packageIndexDepth option to control indexing. you can give it depth 0 to skip indexing a package if you don't use them directly.
see https://github.com/microsoft/pylance-release/blob/main/README.md#settings-and-customization for all options we provide.
closed issue since we confirmed it is due to file system walking. our walking perf is leaner to the size of files/folders given to us and os's file walking perf. if user gives us 1 million files to walk, then we will take time to walk 1 million files.
Thanks for the recommendations, this is indeed the conclusion I reached in my earlier comment.
Sorry for the large delay in response. Allowing for a trace level in the errors I saw that the error was very large enumeration of files, suggesting it could not parse the home directory anymore. When navigating to a directory with fewer files, the extension works as intended, nothing wrong with SSH at all.
Would it be wise to add a more descriptive message to the loading bar or a toast in the bottom right warning users of a potentially large directory which can halt the language server?
However, I never received a popup notification that this was happening and had to enable trace logs and look in the output of the extension. I thought the meaning of these logs were to investigate why this notification was never started, as you mention here.
we would need more detail to know why it didn't work in your case. the log I mentioned above would help us to find out why it didn't work as well.
ah, I didn't mean it will show notification. I meant it will show up in the log which it did. currently, we don't have any notification on perf issues. instead, those issue usually show up in the log.
Sorry for the large delay in response. Allowing for a trace level in the errors I saw that the error was very large enumeration of files, suggesting it could not parse the home directory anymore. When navigating to a directory with fewer files, the extension works as intended, nothing wrong with SSH at all.
Would it be wise to add a more descriptive message to the loading bar or a toast in the bottom right warning users of a potentially large directory which can halt the language server?
really helpful！
|
2025-04-01T04:34:43.276892
| 2022-10-07T01:51:22
|
1400515341
|
{
"authors": [
"heejaechang",
"roxizhauk"
],
"license": "CC-BY-4.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8539",
"repo": "microsoft/pylance-release",
"url": "https://github.com/microsoft/pylance-release/issues/3441"
}
|
gharchive/issue
|
How to disable Auto-excluding venv workspace
Environment data
Language Server version: v2022.10.10
OS and version: macOS 12.6
Python version (& distribution if applicable, e.g. Anaconda): 3.10.2, venv
Repro Steps
go to WORKSPACE and activate the virtual env.
open Vscode.
Expected behavior
Include all source files under "WORKSPACE" directory.
Actual behavior
Excluded all source files. I assume it's because Pylance automatically excludes any virtual environment directories.
Logs
[Info - 10:41:27 AM] (76774) No configuration file found.
[Info - 10:41:27 AM] (76774) No pyproject.toml file found.
[Info - 10:41:27 AM] (76774) Setting pythonPath for service "WORKSPACE": "/Users/USERNAME/.dev/python/WORKSPACE/bin/python"
[Warn - 10:41:27 AM] (76774) stubPath /Users/USERNAME/.dev/python/WORKSPACE/typings is not a valid directory.
[Info - 10:41:27 AM] (76774) Assuming Python version 3.10
[Info - 10:41:27 AM] (76774) Assuming Python platform Darwin
[Info - 10:41:27 AM] (76774) Searching for source files
[Info - 10:41:27 AM] (76774) Auto-excluding /Users/USERNAME/.dev/python/WORKSPACE
[Info - 10:41:27 AM] (76774) No source files found.
there is no exposed option. but you can workaround by creating pyrightconfig.json file (https://github.com/microsoft/pyright/blob/main/docs/configuration.md) and then put dummy exclude option to hit this - https://github.com/microsoft/pyright/blob/main/packages/pyright-internal/src/common/configOptions.ts#L671
Ok, I understand. Sorry for the late response and thanks for the suggestion!
|
2025-04-01T04:34:43.283994
| 2023-02-07T09:59:30
|
1574026136
|
{
"authors": [
"LunarLanding",
"bschnurr",
"erictraut"
],
"license": "CC-BY-4.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8540",
"repo": "microsoft/pylance-release",
"url": "https://github.com/microsoft/pylance-release/issues/3916"
}
|
gharchive/issue
|
Emtpy kw only dataclass has incorrect type hint for init signature
Environment data
Language Server version: 2023.2.10
OS and version: OSX 13.1
Python version (& distribution if applicable, e.g. Anaconda): miniconda python 3.10.8
Code Snippet
from dataclasses import dataclass
@dataclass(kw_only=True)
class A:
pass
A() # shows (*args:Any,**kwargs:Any)
Screenshot
Repro Steps
Enter code above and show the type hint
Expected behavior
Typehint shows no args or kwargs, empty signature.
Actual behavior
Type hint shows any args or kwargs accepted.
Logs
Collected in empty vscode instance, by turning on trace, clearing, restarting, pasting code into unnamed file, and hovering over last line.
[Info - 10:56:22] (13001) Pylance language server 2023.2.10 (pyright 01758105) starting
[Info - 10:56:22] (13001) Server root directory: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist
[Info - 10:56:22] (13001) Starting service instance "<default>"
[Info - 10:56:22] (13001) No pyproject.toml file found.
[Info - 10:56:22] (13001) Setting pythonPath for service "<default>": "$CONDA_PREFIX/bin/python"
[Warn - 10:56:22] (13001) stubPath typings is not a valid directory.
[Info - 10:56:22] (13001) Assuming Python version 3.10
[Info - 10:56:22] (13001) Assuming Python platform Darwin
[Info - 10:56:22] (13001) Search paths for <default>
[Info - 10:56:22] (13001) $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib
[Info - 10:56:22] (13001) .
[Info - 10:56:22] (13001) typings
[Info - 10:56:22] (13001) $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stubs/...
[Info - 10:56:22] (13001) $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/bundled/stubs
[Info - 10:56:22] (13001) $CONDA_PREFIX/lib/python3.10
[Info - 10:56:22] (13001) $CONDA_PREFIX/lib/python3.10/lib-dynload
[Info - 10:56:22] (13001) $HOME/.local/lib/python3.10/site-packages
[Info - 10:56:22] (13001) $CONDA_PREFIX/lib/python3.10/site-packages
[Info - 10:56:22] (13001) Searching for source files
[Info - 10:56:22] (13001) No source files found.
(13001) [IDX(FG)] index libraries (index) ...
(13001) [IDX(FG)] read stdlib indices (16ms)
(13001) [IDX(FG)] index libraries (index) [succeed] (17ms)
[Info - 10:56:22] (13001) No pyproject.toml file found.
[Info - 10:56:22] (13001) Setting pythonPath for service "<default>": "$CONDA_PREFIX/bin/python"
[Warn - 10:56:22] (13001) stubPath typings is not a valid directory.
[Info - 10:56:22] (13001) Assuming Python version 3.10
[Info - 10:56:22] (13001) Assuming Python platform Darwin
[Info - 10:56:22] (13001) Search paths for <default>
[Info - 10:56:22] (13001) $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib
[Info - 10:56:22] (13001) .
[Info - 10:56:22] (13001) typings
[Info - 10:56:22] (13001) $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stubs/...
[Info - 10:56:22] (13001) $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/bundled/stubs
[Info - 10:56:22] (13001) $CONDA_PREFIX/lib/python3.10
[Info - 10:56:22] (13001) $CONDA_PREFIX/lib/python3.10/lib-dynload
[Info - 10:56:22] (13001) $HOME/.local/lib/python3.10/site-packages
[Info - 10:56:22] (13001) $CONDA_PREFIX/lib/python3.10/site-packages
[Info - 10:56:22] (13001) Searching for source files
[Info - 10:56:22] (13001) No source files found.
(13001) [IDX(FG)] index libraries (index) ...
(13001) [IDX(FG)] read stdlib indices (0ms)
(13001) [IDX(FG)] index libraries (index) [succeed] (1ms)
[Info - 10:56:22] (13001) Background analysis(1) root directory: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist
[Info - 10:56:22] (13001) Background analysis(1) started
(13001) Background analysis message: setConfigOptions
(13001) Background analysis message: setImportResolver
(13001) Background analysis message: ensurePartialStubPackages
(13001) [FG] parsing: Untitled-1 (16ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (83ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/builtins.pyi (15ms)
(13001) [FG] binding: Untitled-1 (0ms)
(13001) Background analysis message: setTrackedFiles
(13001) Background analysis message: markAllFilesDirty
(13001) Background analysis message: setFileOpened
(13001) Background analysis message: setConfigOptions
(13001) Background analysis message: setImportResolver
(13001) Background analysis message: ensurePartialStubPackages
(13001) Background analysis message: setTrackedFiles
(13001) Background analysis message: markAllFilesDirty
(13001) Background analysis message: getSemanticTokens full
(13001) [BG(1)] getSemanticTokens full at Untitled-1 ...
(13001) [BG(1)] parsing: Untitled-1 (17ms)
(13001) [BG(1)] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (84ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/builtins.pyi (17ms)
(13001) [BG(1)] binding: Untitled-1 (0ms)
(13001) [BG(1)] getSemanticTokens full at Untitled-1 (120ms)
(13001) Background analysis message: analyze
(13001) [BG(1)] analyzing: Untitled-1 ...
(13001) [BG(1)] checking: Untitled-1 (3ms)
(13001) [BG(1)] analyzing: Untitled-1 (3ms)
(13001) Background analysis message: resumeAnalysis
(13001) Background analysis message: setFileOpened
(13001) Background analysis message: markFilesDirty
(13001) [FG] parsing: Untitled-1 (10ms)
(13001) [FG] binding: Untitled-1 (0ms)
(13001) Background analysis message: analyze
(13001) [BG(1)] analyzing: Untitled-1 ...
(13001) [BG(1)] parsing: Untitled-1 (9ms)
(13001) [BG(1)] binding: Untitled-1 (0ms)
(13001) [BG(1)] checking: Untitled-1 ...
(13001) [BG(1)] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing.pyi [fs read 2ms] (39ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing.pyi (3ms)
(13001) [BG(1)] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (3ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing_extensions.pyi (1ms)
(13001) [BG(1)] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (24ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
(13001) [BG(1)] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/types.pyi [fs read 1ms] (10ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/types.pyi (1ms)
(13001) [BG(1)] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/abc.pyi [fs read 1ms] (1ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/abc.pyi (1ms)
(13001) [BG(1)] parsing: $CONDA_PREFIX/lib/python3.10/dataclasses.py [fs read 1ms] (34ms)
(13001) [BG(1)] binding: $CONDA_PREFIX/lib/python3.10/dataclasses.py (4ms)
(13001) [BG(1)] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/dataclasses.pyi [fs read 0ms] (6ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/dataclasses.pyi (1ms)
(13001) [BG(1)] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi [fs read 0ms] (0ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi ...
(13001) [BG(1)] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_collections_abc.pyi [fs read 0ms] (1ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_collections_abc.pyi (0ms)
(13001) [BG(1)] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi (1ms)
(13001) [BG(1)] checking: Untitled-1 (160ms)
(13001) [BG(1)] analyzing: Untitled-1 (169ms)
(13001) Background analysis message: getDiagnosticsForRange
(13001) Background analysis message: getSemanticTokens delta
(13001) [BG(1)] getSemanticTokens delta previousResultId:1675763782447 at Untitled-1 (1ms)
(13001) Background analysis message: resumeAnalysis
(13001) Background analysis message: getDiagnosticsForRange
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing.pyi [fs read 1ms] (43ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing.pyi (3ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 1ms] (3ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing_extensions.pyi (2ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (25ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/types.pyi [fs read 0ms] (8ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/types.pyi (2ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/abc.pyi [fs read 1ms] (1ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/abc.pyi (0ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/dataclasses.pyi [fs read 0ms] (5ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/dataclasses.pyi (1ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi [fs read 0ms] (0ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi ...
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_collections_abc.pyi [fs read 0ms] (0ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_collections_abc.pyi (0ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi (1ms)
Thanks for the bug report. This will be fixed in an upcoming version.
This issue has been fixed in prerelease version 2023.2.21, which we've just released. You can find the changelog here: CHANGELOG.md
|
2025-04-01T04:34:43.294833
| 2020-05-18T21:55:41
|
620529837
|
{
"authors": [
"swernli"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8541",
"repo": "microsoft/qsharp-runtime",
"url": "https://github.com/microsoft/qsharp-runtime/issues/206"
}
|
gharchive/issue
|
Simulator should allow release of measured Qubits
** Please describe what you would like the feature to accomplish.**
The current simulator implementation requires that all qubits be reset to the |0> state before release, and treats it as a runtime error if this is not the case. The reset can be accomplished via an actual call to Microsoft.Quantum.Intrinsic.Reset or via other appropriate operations that put the qubit into the |0> state. The intent is to make sure no quantum state is "leaked" by releasing a qubit that may still be carrying information via superposition or entanglement. However, this goal can also be met by allowing release of a qubit that has been measured with regard to any single basis and then had no further operations performed on it.
** Describe the solution you'd like **
The simulator check for qubits on release should be updated to allow release of a qubit if it is |0> or if it has been measured with regard to any basis.
** Describe alternatives you've considered **
An alternative could be removing the simulator check for qubit state on release entirely. However, that would be undesirable given the benefit for algorithm validation that this check affords. Without any check, it would be too easy to write algorithms in Q# that did not correctly account for cleaning up qubits that might contain relevant program state.
** Additional context **
The following sample code demonstrates the behavior:
namespace Test {
open Microsoft.Quantum.Intrinsic;
@EntryPoint()
operation Execute() : Result {
using (q = Qubit()) {
H(q);
return M(q);
}
}
}
Because the M will result in collapsing the state to Zero about half the time, this code will execute successfully half of the time but fail with the following error the rest of the time:
Unhandled exception. Microsoft.Quantum.Simulation.Simulators.Exceptions.ReleasedQubitsAreNotInZeroState: Released qubits are not in zero state.
---> Test.Execute on C:\Users\swern\Programming\experimental\Wgate\Program.qs:line 8
Unhandled exception: Microsoft.Quantum.Simulation.Simulators.Exceptions.ReleasedQubitsAreNotInZeroState: Released qubits are not in zero state.
at Microsoft.Quantum.Simulation.Simulators.QuantumSimulator.QSimQubitManager.ReleaseOneQubit(Qubit qubit, Boolean usedOnlyForBorrowing)
at Microsoft.Quantum.Simulation.Common.QubitManager.Release(Qubit qubit)
at Microsoft.Quantum.Simulation.Common.SimulatorBase.Release.Apply(Qubit q)
at Test.Execute.<get_Body>b__24_0(QVoid __in__) in C:\Users\swern\Programming\experimental\Wgate\Program.qs:line 8
at Microsoft.Quantum.Simulation.Core.Operation`2.Apply(I a)
at Microsoft.Quantum.Simulation.Core.Operation`2.Apply[GenO](Object args)
at Microsoft.Quantum.Simulation.Common.SimulatorBase.Execute[T,I,O](I args)
at Microsoft.Quantum.Simulation.Common.SimulatorBase.<>c__DisplayClass43_0`3.<Run>b__0()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__274_0(Object
obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception
was thrown ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location where exception
was thrown ---
at Test.__QsEntryPoint__.EntryPoint.Run(IOperationFactory __factory__) in C:\Users\swern\Programming\experimental\Wgate\obj\qsharp\src\Program.EntryPoint.g.cs:line 29
at Test.__QsEntryPoint__.Driver.DisplayEntryPointResult(EntryPoint entryPoint, Func`1 createSimulator) in C:\Users\swern\Programming\experimental\Wgate\obj\qsharp\src\Program.EntryPoint.g.cs:line 153
at Test.__QsEntryPoint__.Driver.Simulate(EntryPoint entryPoint, String simulator) in C:\Users\swern\Programming\experimental\Wgate\obj\qsharp\src\Program.EntryPoint.g.cs:line 136
at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context)
at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location where exception
was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseParseErrorReporting>b__20_0>d.MoveNext()
--- End of stack trace from previous location where exception
was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass15_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location where exception
was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass24_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location where exception
was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location where exception
was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__21_0>d.MoveNext()
--- End of stack trace from previous location where exception
was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseParseDirective>b__19_0>d.MoveNext()
--- End of stack trace from previous location where exception
was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseDebugDirective>b__11_0>d.MoveNext()
--- End of stack trace from previous location where exception
was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__10_0>d.MoveNext()
--- End of stack trace from previous location where exception
was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass13_0.<<UseExceptionHandler>b__0>d.MoveNext()
Note that replacing the H with an X will result in hitting this failure consistently, as expected. With the suggested change, both the H version and the X version would succeed consistently.
@aniketdalvi This is the issue I mentioned I'd file. Perhaps we can carve out some time later this week to discuss it and how you could use this as a place to get started with the simulator codebase :)
|
2025-04-01T04:34:43.304006
| 2018-12-17T15:16:41
|
391757784
|
{
"authors": [
"WessZumino",
"atimesastudios",
"yueguoguo"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8542",
"repo": "microsoft/recommenders",
"url": "https://github.com/microsoft/recommenders/issues/375"
}
|
gharchive/issue
|
User-friendly guidance on data preparation
It takes time in real-world problems that user feel frustrated about preparing data for recommender algorithms. It would be good to have notebooks to detail that.
Totally agree! In the RBM deepdive I have used some space to explain the logic behind the data splitting and preparation for movielens. However, this is quite a simple scenario as the data are already given in the correct format. It would be good to find a real case scenario in which more work is needed for data preparation
May we please also have guidance for FFM dataset preparation to feed xDeepFM, especially with integrating customer and item features into the input dataset along with implicit/explicit feedback.
@atimesastudios yea we do have some preparation functions for this
The negative_feedback_sampler (see here) is the one that samples negative feedback when data is about implicit feedback.
The LibffmConverter (see here) is the one that performs libffm format conversion from feature data set.
|
2025-04-01T04:34:43.306028
| 2020-12-19T01:39:30
|
771273677
|
{
"authors": [
"HyemiSong",
"imatiach-msft"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8543",
"repo": "microsoft/responsible-ai-widgets",
"url": "https://github.com/microsoft/responsible-ai-widgets/issues/227"
}
|
gharchive/issue
|
[Error Analysis] Size and zoom consistency (normal vs full screen mode)
[Obj size on the Top info area]
When I open the full screen, the overall objects on the top information area became bigger. Regardless of the screen status, all objects should have the same size. I am unsure of how this happens.
[Zoom]
When I load the dashboard and I open the full screen, the treemap should be centering and its zoom should be 100%. It seems to be above 100% zoom in the full screen.
closing this issue as zoom has been removed based on latest UI designer guidelines so the issue is no longer relevant
|
2025-04-01T04:34:43.311162
| 2023-04-22T08:38:35
|
1679419740
|
{
"authors": [
"YoChen",
"karelz",
"pinkfloydx33"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8544",
"repo": "microsoft/reverse-proxy",
"url": "https://github.com/microsoft/reverse-proxy/issues/2109"
}
|
gharchive/issue
|
How to config yarp.json to add or remove part of route?
eg:
from http://abc.com/a/b/{everything}
to http://cba.com/b/{everything}
or
from http://abc.com/a/b/{everything}
to http://cba.com/c/{everything}
or
from http://abc.com/a/b/{everything}
to http://abc.com/c/a/b/{everything}
can you help me ,if yarp.json can archive. very thanks.
Generally speaking, you could use two transforms: one to strip/remove the existing path prefix and a second transform to add a new prefix. That said, only your second case would require both; the first example only needs prefix removal while the third only needs to add a prefix.
Example Configuration
// *snip*
"ReverseProxy": {
"routes": {
"route1": {
"ClusterId": "cluster1",
"Match": {
"Path": "/a/b/{**catchall}"
},
"Transforms": [
{
"PathRemovePrefix": "/a"
}
]
},
"route2": {
"ClusterId": "cluster1",
"Match": {
"Path": "/a/b/{**catchall}"
},
"Transforms": [
{
"PathRemovePrefix": "/a/b"
},
{
"PathPrefix": "/c"
}
]
},
"route3": {
"ClusterId": "cluster2",
"Match": {
"Path": "/a/b/{**catchall}"
},
"Transforms": [
{
"PathPrefix": "/c"
}
]
}
},
"Clusters": {
"cluster1": {
"Destinations": {
"clustser1/backend": {
"Address": "http://www.cba.com/"
}
}
},
"cluster2": {
"Destinations": {
"clustser2/backend": {
"Address": "http://www.abc.com/"
}
}
}
}
}
Triage: Seems to be answered by @pinkfloydx33 (thank you!)
Closing.
|
2025-04-01T04:34:43.325524
| 2023-05-25T09:13:00
|
1725413384
|
{
"authors": [
"AsakusaRinne",
"KSemenenko",
"craigomatic",
"dluc",
"drasticactions",
"evchaki",
"markwallace-microsoft",
"matthewbolanos",
"xbotter"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8545",
"repo": "microsoft/semantic-kernel",
"url": "https://github.com/microsoft/semantic-kernel/issues/1215"
}
|
gharchive/issue
|
Integrate LLamaSharp to enable LLaMa model inference
Hi all, great work so far! As the open-source LLM models become more and more hot, will semantic-kernel consider supporting some of them such as LLaMa? I'm the main author of LLamaSharp, which is the .NET binding of llama.cpp. I wonder if it's possible to integrate LLamaSharp into semantic-kernel to add support for some open-source LLM models (as you can see, llama.cpp support 10 kinds of models). I'd like to work for this integration if it's taken into account to the future version of semantic-kernel. Thank you for your consideration.
Thanks for posting, this does sound interesting and I wonder if it would be possible to provide a LLamaSharp implementation along the lines of this sample: https://github.com/microsoft/semantic-kernel/blob/main/samples/dotnet/kernel-syntax-examples/Example16_CustomLLM.cs
@dluc make have opinions here also
@AsakusaRinne , let us know if you want to do a PR for this based on the other examples of how other models work.
Hi, thanks to the efforts of community, there's an example here to use LLamaSharp with sk. The example uses the latest pre-release of sk and is easy to deploy. Please have a look and I'll improve it with your advice.
@evchaki @craigomatic Please let me know if I can provide any further information to help move this forward. Thank you for your time and attention.
We have a basic implementation of this in LLamaSharp itself now: https://github.com/SciSharp/LLamaSharp/tree/master/LLama.SemanticKernel
I'm not sure how stable the Abstractions library is though, I've had to bump it due to a recent change in IChatCompletion. I'm not sure bringing this implementation into this repo makes sense, but maybe there could be more said for changes like these?
I'm definitely going to take this in somehow :-)
I can do this =)
@drasticactions, now that the abstractions have settled down, would you be interested in bringing in LlamaSharp into the main Semantic Kernel repo?
I am currently working on the maintenance of LLamaSharp.SemanticKernel. If possible, I would be willing to do it.
All .Net issues prior to 1-Dec-2023 are being closed. Please re-open, if this issue is still relevant to the .Net Semantic Kernel 1.x release. In the future all issues that are inactive for more than 90 days will be labelled as 'stale' and closed 14 days later.
It seems that this issue is still under-working. Please reopen it. :)
|
2025-04-01T04:34:43.354560
| 2024-10-11T16:18:47
|
2581747363
|
{
"authors": [
"diaburesphi",
"mckenkenedy"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8546",
"repo": "microsoft/semantic-kernel",
"url": "https://github.com/microsoft/semantic-kernel/issues/9214"
}
|
gharchive/issue
|
.Net: ![ＬＩＶＥ＠ＳＴＲＥＡＭsTv !] Mr Olympia 2024 Ｌｉｖｅ Ｓｔｒｅａｍｓ Ｆｒｅｅ Ｃｏｖｅｒａｇｅ ＯＮ 11 October 2024
The bodybuilding competition of the year is here. That's right — Mr. Olympia is back for its 60th anniversary and returning to Las Vegas.
Ms. Olympia pre-judging will take place on Friday morning with finals in the evening, and the Mr. Olympia main event is scheduled to start on Saturday night. Bodybuilders from all over the world will be competing for the coveted title this weekend.
🅻🅸🆅🅴🔴▶️ CLICK HERE TO WATCH LIVE ONLINE
🆆🅰🆃🅲🅷🔴▶️ CLICK HERE TO LIVE STREAM
MR. OLYMPIA RESULTS: Updated list of winners in 2024
American bodybuilder Derek Lunsford took home the title in 2023, making him the first winner of the competition in two separate divisions (2023 Mr. Olympia and 2021 212 Mr. Olympia). Lunsford swapped places with defending champion Hadi Choopan, who had beaten him out for first place in 2022.
Both Lunsford and Choopan have qualified for the 2024 competition, as well as 2019 champion Brandon Curry. Andrea Shaw will be looking for an incredible five-peat in the Ms. Olympia competition.
Here is everything you need to know about the 2024 competition, including a full schedule and list of participants.
When is Mr. Olympia in 2024?
Dates: Friday, Oct. 11-Saturday, Oct. 12
This year, Mr. Olympia will be held at Resorts World Las Vegas. The finals for Ms. Olympia and Mr. Olympia will take place on Friday and Saturday, respectively.
Mr. Olympia schedule 2024
Date Time (ET) Event
Oct. 11 12:30 p.m. Ms. Olympia pre-judging
9 p.m. Ms. Olympia finals/Mr. Olympia pre-judging
Oct. 12 10 p.m. Mr. Olympia finals
Mr. Olympia live stream 2024
Live stream: Olympia pay-per-view
Mr. Olympia will not be available to watch on a national TV channel. Viewers can live stream the event on OlympiaTV, which provides a pay-per-view package for $74.99.
Who is competing in Mr. and Ms. Olympia?
In order to qualify for events, competitors must meet the requirements set by the IFBB Professional League. Nineteen men qualified for Mr. Olympia, while 15 women qualified for Ms. Olympia.
Lunsford is the defending Mr. Olympia champion and will be looking for his second title this year. Choopan won in 2022 and will be hungry for a championship after placing second last year.
Shaw is competing for a fifth straight Ms. Olympia title.
Mr. Olympia qualifiers 2024
Name Country
Derek Lunsford USA
Hadi Choopan Iran
Samson Dauda UK
Theo Leguerrier France
Rafael Brandao Brazil
Martin Fitzwater USA
Nicholas Walker USA
Tonio Burton USA
Akim Williams USA
Brandon Curry USA
William Bonac Netherlands
Behrooz Tabani Iran
Nathan De Asha UK
John Jewett USA
Mohamed Foda Egypt
Jonathan Delarosa USA
Chinedu Andrew Obiekea UAE
Hunter Labrada USA
Bruno Santos Brazil
Ms. Olympia qualifiers 2024
Name Country
Andrea Shaw USA
Angela Yeo USA
Alcione Santos Barreto Brazil
Leyvina Rodrigues Barros Brazil
Theresa Ivancik USA
Julia Whitesel USA
Ashley Lynette Jones USA
Ava Melillo USA
Nadia Capotosto Italy
Helle Trevino USA
Anastasia Leonova Russia
Michaela Aycock USA
Sherry Priami USA
Kristina Mendoza USA
Alida Opre Hungary
What are the other events held during Mr. Olympia weekend?
There are a few other events beyond the typical Mr. and Ms. Olympia contests.
The other events for men are 212 Olympia, Men's Physique Olympia, Classic Physique Olympia and Wheelchair Olympia.
The other events for women are Figure Olympia, Fitness Olympia, Bikini Olympia, Women's Physique Olympia, Wellness Olympia and Wheelchair Olympia.
Mr. Olympia prize money 2024
The total purse has not yet been announced, but it is expected to break last year's record of $1.6 million.
The money will be split between the top finishers. In 2023, Lunsford took home $400,000, while the second- and third-place finishers earned $150,000 and $100,000, respectively.
The bodybuilding competition of the year is here. That's right — Mr. Olympia is back for its 60th anniversary and returning to Las Vegas.
Ms. Olympia pre-judging will take place on Friday morning with finals in the evening, and the Mr. Olympia main event is scheduled to start on Saturday night. Bodybuilders from all over the world will be competing for the coveted title this weekend.
🅻🅸🆅🅴🔴▶️ CLICK HERE TO WATCH LIVE ONLINE
🆆🅰🆃🅲🅷🔴▶️ CLICK HERE TO LIVE STREAM
MR. OLYMPIA RESULTS: Updated list of winners in 2024
American bodybuilder Derek Lunsford took home the title in 2023, making him the first winner of the competition in two separate divisions (2023 Mr. Olympia and 2021 212 Mr. Olympia). Lunsford swapped places with defending champion Hadi Choopan, who had beaten him out for first place in 2022.
Both Lunsford and Choopan have qualified for the 2024 competition, as well as 2019 champion Brandon Curry. Andrea Shaw will be looking for an incredible five-peat in the Ms. Olympia competition.
Here is everything you need to know about the 2024 competition, including a full schedule and list of participants.
When is Mr. Olympia in 2024?
Dates: Friday, Oct. 11-Saturday, Oct. 12
This year, Mr. Olympia will be held at Resorts World Las Vegas. The finals for Ms. Olympia and Mr. Olympia will take place on Friday and Saturday, respectively.
Mr. Olympia schedule 2024
Date Time (ET) Event
Oct. 11 12:30 p.m. Ms. Olympia pre-judging
9 p.m. Ms. Olympia finals/Mr. Olympia pre-judging
Oct. 12 10 p.m. Mr. Olympia finals
Mr. Olympia live stream 2024
Live stream: Olympia pay-per-view
Mr. Olympia will not be available to watch on a national TV channel. Viewers can live stream the event on OlympiaTV, which provides a pay-per-view package for $74.99.
Who is competing in Mr. and Ms. Olympia?
In order to qualify for events, competitors must meet the requirements set by the IFBB Professional League. Nineteen men qualified for Mr. Olympia, while 15 women qualified for Ms. Olympia.
Lunsford is the defending Mr. Olympia champion and will be looking for his second title this year. Choopan won in 2022 and will be hungry for a championship after placing second last year.
Shaw is competing for a fifth straight Ms. Olympia title.
Mr. Olympia qualifiers 2024
Name Country
Derek Lunsford USA
Hadi Choopan Iran
Samson Dauda UK
Theo Leguerrier France
Rafael Brandao Brazil
Martin Fitzwater USA
Nicholas Walker USA
Tonio Burton USA
Akim Williams USA
Brandon Curry USA
William Bonac Netherlands
Behrooz Tabani Iran
Nathan De Asha UK
John Jewett USA
Mohamed Foda Egypt
Jonathan Delarosa USA
Chinedu Andrew Obiekea UAE
Hunter Labrada USA
Bruno Santos Brazil
Ms. Olympia qualifiers 2024
Name Country
Andrea Shaw USA
Angela Yeo USA
Alcione Santos Barreto Brazil
Leyvina Rodrigues Barros Brazil
Theresa Ivancik USA
Julia Whitesel USA
Ashley Lynette Jones USA
Ava Melillo USA
Nadia Capotosto Italy
Helle Trevino USA
Anastasia Leonova Russia
Michaela Aycock USA
Sherry Priami USA
Kristina Mendoza USA
Alida Opre Hungary
What are the other events held during Mr. Olympia weekend?
There are a few other events beyond the typical Mr. and Ms. Olympia contests.
The other events for men are 212 Olympia, Men's Physique Olympia, Classic Physique Olympia and Wheelchair Olympia.
The other events for women are Figure Olympia, Fitness Olympia, Bikini Olympia, Women's Physique Olympia, Wellness Olympia and Wheelchair Olympia.
Mr. Olympia prize money 2024
The total purse has not yet been announced, but it is expected to break last year's record of $1.6 million.
The money will be split between the top finishers. In 2023, Lunsford took home $400,000, while the second- and third-place finishers earned $150,000 and $100,000, respectively.
The bodybuilding competition of the year is here. That's right — Mr. Olympia is back for its 60th anniversary and returning to Las Vegas.
Ms. Olympia pre-judging will take place on Friday morning with finals in the evening, and the Mr. Olympia main event is scheduled to start on Saturday night. Bodybuilders from all over the world will be competing for the coveted title this weekend.
🅻🅸🆅🅴🔴▶️ CLICK HERE TO WATCH LIVE ONLINE
🆆🅰🆃🅲🅷🔴▶️ CLICK HERE TO LIVE STREAM
MR. OLYMPIA RESULTS: Updated list of winners in 2024
American bodybuilder Derek Lunsford took home the title in 2023, making him the first winner of the competition in two separate divisions (2023 Mr. Olympia and 2021 212 Mr. Olympia). Lunsford swapped places with defending champion Hadi Choopan, who had beaten him out for first place in 2022.
Both Lunsford and Choopan have qualified for the 2024 competition, as well as 2019 champion Brandon Curry. Andrea Shaw will be looking for an incredible five-peat in the Ms. Olympia competition.
Here is everything you need to know about the 2024 competition, including a full schedule and list of participants.
When is Mr. Olympia in 2024?
Dates: Friday, Oct. 11-Saturday, Oct. 12
This year, Mr. Olympia will be held at Resorts World Las Vegas. The finals for Ms. Olympia and Mr. Olympia will take place on Friday and Saturday, respectively.
Mr. Olympia schedule 2024
Date Time (ET) Event
Oct. 11 12:30 p.m. Ms. Olympia pre-judging
9 p.m. Ms. Olympia finals/Mr. Olympia pre-judging
Oct. 12 10 p.m. Mr. Olympia finals
Mr. Olympia live stream 2024
Live stream: Olympia pay-per-view
Mr. Olympia will not be available to watch on a national TV channel. Viewers can live stream the event on OlympiaTV, which provides a pay-per-view package for $74.99.
Who is competing in Mr. and Ms. Olympia?
In order to qualify for events, competitors must meet the requirements set by the IFBB Professional League. Nineteen men qualified for Mr. Olympia, while 15 women qualified for Ms. Olympia.
Lunsford is the defending Mr. Olympia champion and will be looking for his second title this year. Choopan won in 2022 and will be hungry for a championship after placing second last year.
Shaw is competing for a fifth straight Ms. Olympia title.
Mr. Olympia qualifiers 2024
Name Country
Derek Lunsford USA
Hadi Choopan Iran
Samson Dauda UK
Theo Leguerrier France
Rafael Brandao Brazil
Martin Fitzwater USA
Nicholas Walker USA
Tonio Burton USA
Akim Williams USA
Brandon Curry USA
William Bonac Netherlands
Behrooz Tabani Iran
Nathan De Asha UK
John Jewett USA
Mohamed Foda Egypt
Jonathan Delarosa USA
Chinedu Andrew Obiekea UAE
Hunter Labrada USA
Bruno Santos Brazil
Ms. Olympia qualifiers 2024
Name Country
Andrea Shaw USA
Angela Yeo USA
Alcione Santos Barreto Brazil
Leyvina Rodrigues Barros Brazil
Theresa Ivancik USA
Julia Whitesel USA
Ashley Lynette Jones USA
Ava Melillo USA
Nadia Capotosto Italy
Helle Trevino USA
Anastasia Leonova Russia
Michaela Aycock USA
Sherry Priami USA
Kristina Mendoza USA
Alida Opre Hungary
What are the other events held during Mr. Olympia weekend?
There are a few other events beyond the typical Mr. and Ms. Olympia contests.
The other events for men are 212 Olympia, Men's Physique Olympia, Classic Physique Olympia and Wheelchair Olympia.
The other events for women are Figure Olympia, Fitness Olympia, Bikini Olympia, Women's Physique Olympia, Wellness Olympia and Wheelchair Olympia.
Mr. Olympia prize money 2024
The total purse has not yet been announced, but it is expected to break last year's record of $1.6 million.
The money will be split between the top finishers. In 2023, Lunsford took home $400,000, while the second- and third-place finishers earned $150,000 and $100,000, respectively.
xcvxcv
|
2025-04-01T04:34:43.357612
| 2023-07-11T14:37:20
|
1799088759
|
{
"authors": [
"HadwaAbdelhalem",
"hattan"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8547",
"repo": "microsoft/symphony",
"url": "https://github.com/microsoft/symphony/pull/215"
}
|
gharchive/pull-request
|
Update README.md
This change fixes a small grammatical error on the root repo README.
While this is a real change, another purpose of this PR is to test the PR checker workflow with external forks.
@hattan so we still need this PR?
No longer needed. Closing PR.
|
2025-04-01T04:34:43.362272
| 2023-05-23T20:19:24
|
1722728006
|
{
"authors": [
"j4james",
"lhecker"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8548",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/issues/15409"
}
|
gharchive/issue
|
Using a soft font causes the Atlas engine to crash
Windows Terminal version
1.18.1421.0
Windows build number
10.0.19045.2913
Other Software
No response
Steps to reproduce
Make sure the Atlas engine is activated in the Advanced profile settings.
Open a bash shell.
Execute printf "\eP0;1;1;4;2;1{B~~~~~~~~/~~~~~~~~\e\\"
Expected Behavior
Most characters output at this point should be reverse question marks, except for ! which should map to a solid block.
Actual Behavior
The terminal crashes. This is caused by a null pointer reference when accessing the fontFaceEntry.fontFace field in BackendD3D::_initializeFontFaceEntry.
https://github.com/microsoft/terminal/blob/c589784b54d46187289651fa6c04c49fe05826aa/src/renderer/atlas/BackendD3D.cpp#L1158
Just based on a brief scan of the code, I got the impression that it's expected for the fontFace to be null when you have a soft font, so it may just be that this method hasn't allowed for that case. This appears to be a regression introduced in PR #15343.
Ah dang I didn't test it again after the PR. 😟 Sorry for breaking it, and thank you so much for noticing it!
FYI the link I distributed in some other comments (click) is a build that also contains the PR that fixes this. If you're eager to test it out, you could consider installing that build. 🙂
I've patched my local build with the changes in your PR and it's working great now. Thanks!
|
2025-04-01T04:34:43.364030
| 2023-10-23T03:29:10
|
1956281435
|
{
"authors": [
"CCCAUCHY",
"lhecker"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8549",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/issues/16213"
}
|
gharchive/issue
|
Historysize is not big enough
Description of the new feature/enhancement
Historysize is not big enough. I need unlimit historysize.
Proposed technical implementation details (optional)
In that case, please subscribe to #1410 and give it a thumbs up. 🙂
/dup #16213
|
2025-04-01T04:34:43.368737
| 2024-09-10T11:12:07
|
2516142407
|
{
"authors": [
"SaurabhNew",
"lhecker"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8550",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/issues/17891"
}
|
gharchive/issue
|
[Windows Terminal - Command Palette]: Clear buffer button is not functional via mouse and keyboard.
Windows Terminal version
1.22.2362.0
Windows build number
27695.1000
Other Software
Test Environment:
OS: Windows 11 Version Dev (OS Build 27695.1000)
App: Windows Terminal Preview
Steps to reproduce
Repro steps :
1.Open Windows Terminal.
2.Open the 'Command Palette' using 'Ctrl + Shift + P' keys.
3.Navigate to the clear buffer control and activate it via mouse and keyboard.
4.Observe the issue.
User Experience
Users are unable to perform the "Clear Buffer" action using either mouse or keyboard, which can hinder their workflow.
Attachments:
Clear buffer button is not functional via mouse and keyboard..zip
Expected Behavior
Clear buffer button should be functional via both mouse and keyboard and on activating clear buffer button, it should clear all the buffer from the editing window.
Actual Behavior
Clear buffer button is not functional via mouse and keyboard.
Clear buffer button is not functional with the shortcut key as well, which is added from actions.
Hey! This was previously reported in #17867. I'll close your issue as a duplicate then. 🙂 /dup #17867
The good news is that a PR to fix it has been opened and should go out soon: #17884
|
2025-04-01T04:34:43.424258
| 2020-01-14T19:52:11
|
549782173
|
{
"authors": [
"0byt3",
"Clifra-Jones",
"DHowett",
"DHowett-MSFT",
"DoCode",
"KirkMunro",
"PeterRoots",
"Sarafian",
"TBBle",
"Wittionary",
"bitcrazed",
"cking22001",
"conioh",
"dadpolice",
"joshuatee",
"mcwidg3t",
"oising",
"pilgi3",
"skadog"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8551",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/issues/4217"
}
|
gharchive/issue
|
Explore whether Terminal could be 'runas' a different user identity
Related to #2485, #1053, #3534
This issue is a fork from a conversation started in #146 (specifically this comment onwards) discussing if/whether Terminal can/could support being runas a different user identity than the currently logged-in user.
Note: This is not sudo or run elevated - that's a different concept since elevation runs a process with the current user's identity, but with additional (admin) rights.
The primary ask here is that users, particularly those in enterprise scenarios, often need to run commands/scripts/etc. under a different user account with different permissions/rights than their normal/general user account.
Alas, UWP apps do not currently support the ability to run under a different identity than the currently logged-in user.
Thus, there are a couple of questions:
Can the UWP app platform provide a way to run UWP apps under a different/specific user identity?
If not, can Terminal be built/delivered allowing users to run under a different identity?
We'll go do some homework and respond to this thread with what we find.
Thanks all on the original thread for sharing their feedback :)
I'm not an enterprise user so I apologize if I don't fully understand the requirements here, but does the terminal GUI really need to run as another user? Or is it enough to spawn shells with runas and/or a potential sudo utility? I was able to get an admin tab with my wsudo POC, and I'd imagine running a shell as another user would work similarly.
That is a whole other thread with its own security concerns. https://github.com/microsoft/terminal/issues/632
The primary ask here is that users, particularly those in enterprise scenarios, often need to run commands/scripts/etc. under a different user account with different permissions/rights than their normal/general user account.
Isn't the primary issue here security? In my book no user, enterprise or not, should be running an admin account hoping UAC is doing it's job properly
Bypass User Account Control
https://attack.mitre.org/techniques/T1088/
to me this is a HUGE issue and it seems it is being swept under the rug
Isn't the primary issue here security? In my book no user, enterprise or not, should be running an admin account hoping UAC is doing its job properly
It's the same issue.
An example of this is that a domain admin should have two AD accounts; a standard user account and a domain admin account. They should be logged into their desktop under their standard user account.
This is preferable to switching to their domain admin user. It's more convenient and much quicker.
Yes, this is all about security.
Consider the scenario where a domain admin's standard environment is compromised with some form of pernicious malware.
If/when they launch an app from their compromised desktop running as their domain admin account, the malware now has considerable opportunity to key-log/screen-scrape/intercept/divert/whatever on the .
This is why many enterprises and most online services air-gap users from production systems, requiring users to login via RD to a strictly-managed, heavily-restricted hosted VM environment which is severely locked down, regularly re-paved, etc.
Such environments used to be the domain of the rich and famous, but this can now be built very cost effectively with commodity services and tools.
Is this more inconvenient than just runas /user:domainadmin1 "resetpasswords.bat /all"? Yes, but it's designed to be so.
One of the interesting artifacts of such changes is that scripts, automation, and systems get built to replace the user's need to run admin tasks ad-hoc, increasing reliability and repeatability, decreasing errors, and decreasing various other risks.
YMMV.
Being redirected from GH-5723 and I understand the security concerns but I think we are missing something from the user experience.
I actually work with a restricted user and when I do "Run as Admin", I elevate with a local admin user for which I need to enter the password. This works with everything, including powershell and cmd prompt. I understand the possible WUP limitations but the 2-user pattern is a much more secure pattern, I think, than a all the time admin with UAC on demand.
If the WUP won't allow for this, shouldn't there be an alternative like a global installation even outside the Windows Store, like PowerShell and every other application. At the end of the day, this looks like a limitation of the WUP because what would happen on systems that only run WUP apps? A Terminal is almost by design an extension to system configuration, so something needs to be considered when re-envisioning a Windows Terminal that can't do admin things.
I also request for this issue to be re-opened or lets create another one. Let me know please.
On systems that only run universal “modern” applications, there is no local administration scenario. Sorry.
This issue tracks the work we need from the application deployment team to make launching a modern packaged application with any identity that isn’t your local logged-in user identity work. This bug will be sufficient for tracking your request.
In the meantime, if you register the application package for your admin user you should be able to run Terminal as that user.
Hey Alex. I think your scenario is similar to those above so no need for a new one.
We do understand the scenario well. But as discussed above:
The UWP app model does not (currently) support running modern apps under the identity other than the currently logged-in user
The venerable Windows Console (the UI you traditionally see when you run Cmd/PowerShell directly) is a standard Win32 app and can be run under a different user's identity
Running under a different user identity does offer some security risk mitigation, but does not protect one from malware (e.g. keyloggers) running in the current user session.
Before we continue, let's remember ...
UAC is not a security barrier!
Elevating a process via UAC does help protect against several forms of attack, but UAC is NOT a security barrier. Nor is running tools under the identity of an arbitrary user account. They can help mitigate some risks, but they're not a security mechanism
Consider UAC:
When UAC is enabled:
Apps normally run without the admin bit set on the user's security token (even if the user is in the admin group), and the app is not permitted to do things that require admin rights
When an app is launched "elevated", after the UAC prompt, the launched process receives the identity and user token of the specified user - whether it's the current user or a different identity, but with the admin bit set. The elevated process is seen by the OS as running with elevated admin rights, and is granted permissions to do things that may affect machine-wide state and/or bypass certain standard protections. This is why it's unwise to run tools elevated by default, or elevated for extended periods of time - when elevated, such apps can "do things to things" that might not be appreciated!
However, once again, UAC/elevation is not a security barrier. UAC does not protect you from locally running malware, it does not protect you from keyloggers, it does not protect you from ransomware, etc. No single security feature will!
The best approach to protect one's self and/or one's systems from malware attack is multiple layers of defense.
UAC helps. As does correctly ACLing sensitive resources. As does running an OS & app platform that provides several layers of defense throughout. As does remoting (via something like Remote Desktop that itself implements several layers of protection) into a desktop session running on a carefully managed and highly restricted remote/virtual environment that requires biometric/2FA authentication, etc., in which only specifically permitted apps and tools can run.
Of course, this degree of security may be too costly, time-consuming, annoying, etc. for your needs/scenarios, but it does achieve the goals that many here aim to achieve. Up to where on this spectrum one is willing to invest time and resources is entirely up to you.
Get to the point Rich 😜
Sorry for the lengthy exposition, but I want to be sure we're all on the same page re. the true efficacy (from a security perspective) of launching a Terminal "as a different user" whether with or without admin rights. With this understanding (I hope) it's clear why the modern/future Windows app platform chose NOT to support running apps as a different user - the security benefits of doing so are not as valuable or effective as some might assume.
What does this mean for Terminal?
We build Windows Terminal as a modern Windows app. We chose to do so for many reasons, but in doing so, we did recognize that there would need to trade-off vs. certain capabilities/features. If Terminal doesn't meet some specific needs, we encourage you to continue to use Console or whatever 3rd party Terminal app does meet your needs. After all, no one tool can do it all for everyone!
However, do know that we remain in close contact with the app plat and security teams and continue to investigate and explore several approaches & features that will help provide layers of defense around Terminal scenarios.
Bear with us!
We build Windows Terminal as a modern Windows app. We chose to do so for many reasons, but in doing so, we did recognize that there would need to trade-off vs. certain capabilities/features. If Terminal doesn't meet some specific needs, we encourage you to continue to use Console or whatever 3rd party Terminal app does meet your needs. After all, no one tool can do it all for everyone!
@bitcrazed Is it possible to (very briefly) explain some of the functionality in modern apps that led you to that decision?
Hey @dadpolice - sure.
We wanted to be able to take advantage of:
Modern UX & WinUI controls (inc. Tab controls) with greater consistency with other Windows apps and tools
Acrylic backgrounds
Independent & clean per-user install & uninstall*
Always Up To Date via the Store
Push the app plat into new territory**
* Interestingly, this need, provided for inherently by the modern app platform (all users get their own independent mutable app state) is what makes supporting runas difficult, because if you don't login to said desktop and install Terminal, you wouldn't be able to runas since wouldn't have the app installed!
** We also wanted to push the app plat into new territory, and ensure that it was able to support scenarios which the app plat was originally designed to prevent (e.g. launching & communicating with arbitrary external processes, e.g. Cmd, PowerShell, WSL, ping/ipconfig/etc.).
@DHowett-MSFT and @bitcrazed I really appreciate you sharing your insight and I learned somethings as well.
We build Windows Terminal as a modern Windows app. We chose to do so for many reasons, but in doing so, we did recognize that there would need to trade-off vs. certain capabilities/features. If Terminal doesn't meet some specific needs, we encourage you to continue to use Console or whatever 3rd party Terminal app does meet your needs. After all, no one tool can do it all for everyone!
@bitcrazed Is it possible to (very briefly) explain some of the functionality in modern apps that led you to that decision?
To extend the @dadpolice question, I've already proposed a different release format if possible because I do understand the limitations of WUP.
If the WUP won't allow for this, shouldn't there be an alternative like a global installation even outside the Windows Store, like PowerShell and every other application.
I don't know if that is possible though. Not sure if an app built for WUP can be packaged and run outside of WUP. If not then given the "limitations" of the WUP then this won't work. Maybe, a recompilation of the same code for non WUP could be an option. As long as it is not a big hassle to implement, then adding a another release format is not a technical problem and more of a choice. It might be that there are some reasons to stay only on WUP. Looking forward to your insight on these topics as well.
In the meantime, if you register the application package for your admin user you should be able to run Terminal as that user.
I actually never thought about this.
Thank you all guys.
@Sarafian So, this is one of those cool things that we get sorta "for free". Terminal is actually built as a classic Win32 application and then packaged later.
The end result of this is that you can, if you're so motivated, extract the msixbundle like a zip file, then extract the msix for your architecture inside it. You'll get a folder of DLLs and EXEs. If you then double-click WindowsTerminal.exe or put it on your path or what-have-you it'll work just fine, and it'll work for any user who can access that folder.
There's a minor issue you'll run into with the dropdown icons doing it that way, but it is functional. :smile:
@DHowett-MSFT cool. Have you guys considered what I proposed? Creating another form of deliverable additional to WUP? A traditional installer that could be even leveraged by chocolatey for fast updates?
That's the subject of a very lively discussion in #1386.
So we should and can add a common msi package and distribute in the same way as other tools, like VS, Msbuild, etc.
Nice!
That's the subject of a very lively discussion in #1386.
Ok thanks. Continuing there.
Isn't the primary issue here security? In my book no user, enterprise or not, should be running an admin account hoping UAC is doing its job properly
It's the same issue.
An example of this is that a domain admin should have two AD accounts; a standard user account and a domain admin account. They should be logged into their desktop under their standard user account.
This is preferable to switching to their domain admin user. It's more convenient and much quicker.
This is my exact situation. We have a regular AD user account for our workstation and an AD administrator account to do our work. As it stands now I see no real point in using WT over my standard powershell or command terminal.
As a workaround, can you not Enter-PSSession with your alternate identity credentials? (obviously this is only a powershell solution)
This does not work if you are trying to do things like Active Directory management. A simple test is to try to access the c$ admin share on a DC using set-location, it will fail. While opening a Powershell windows "As a different user" works.
Interesting all the points above on security of elevation vs no elevation when running commands in a terminal (cmd, powershell or whatever). A big selling point of windows terminal is the tabs and split panes - great for running stuff remotely when enter-pssession is ideal. There are time though when I need/want to run something locally, at which point I need to ditch terminal and open a powershell window as admin to do it. Sort of defeats the point of having a nice neat all in one place for terminal windows
In the meantime, if you register the application package for your admin user you should be able to run Terminal as that user.
I recently found myself in the position of wanting to register Store-installed Windows Terminal with a second (high-privilege) account to try and work-around this issue, due to local corporate policies.
By my research, the command should be:
Add-AppxPackage -Register 'C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe\AppxManifest.xml' -DisableDevelopmentMode
when running PowerShell as the target user (either privileged or unprivileged), but it fails
Add-AppxPackage : Deployment failed with HRESULT: 0x80073D19, An error occurred because a user was logged off.
error 0x80070002: While processing the request, the system failed to register the windows.sharedFonts extension due to the following error: The system cannot find the file specified.
The Get-AppPackageLog -ActivityID 10f4110e-a0eb-0003-45f6-6b11eba0d601 output:
PS C:\WINDOWS\system32> Get-AppPackageLog -ActivityID 10f4110e-a0eb-0003-45f6-6b11eba0d601
Time ID Message
---- -- -------
10/20/2020 1:12:12 PM 603 Started deployment Register operation on a package with main parameter AppxManifest.xml and Options 0 and 0. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
10/20/2020 1:12:12 PM 819 The following packages will be installed: 1527c705-839a-4832-9118-54d4Bd6a0c89_10.0.18362.449_neutral_neutral_cw5n1h2txyewy c5e2524a-ea46-4f67-841f-6a9465d9d515_10.0.18362.449_neutral_neutral_cw5n1h2txyewy E2A4F912-2574-4A75-9BB0-0D023378592B_10.0.18362.449_neutral_neutral_cw5n1h2txyewy
F46D4000-FD22-4DB4-AC8E-4E1DDDE828FE_10.0.18362.449_neutral_neutral_cw5n1h2txyewy InputApp_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.AAD.BrokerPlugin_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.AccountsControl_10.0.18362.449_neutral_neutral_cw5n1h2txyewy
Microsoft.AsyncTextService_10.0.18362.449_neutral_neutral_8wekyb3d8bbwe Microsoft.BioEnrollment_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.CredDialogHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.ECApp_10.0.18362.449_neutral_neutral_8wekyb3d8bbwe
Microsoft.LockApp_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.MicrosoftEdgeDevToolsClient_10.0.18362.449_neutral__8wekyb3d8bbwe Microsoft.MicrosoftEdge_44.18362.449.0_neutral__8wekyb3d8bbwe Microsoft.PPIProjection_10.0.18362.449_neutral_neutral_cw5n1h2txyewy
Microsoft.Win32WebViewHost_10.0.18362.997_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.AppRep.ChxApp_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.AssignedAccessLockApp_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.CallingShellApp_10.0.18362.449_neutral_neutral_cw5n1h2txyewy
Microsoft.Windows.CapturePicker_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.CloudExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.ContentDeliveryManager_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.Cortana_10.0.18362.449_neutral_neutral_cw5n1h2txyewy
Microsoft.Windows.NarratorQuickStart_10.0.18362.449_neutral_neutral_8wekyb3d8bbwe Microsoft.Windows.OOBENetworkCaptivePortal_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.OOBENetworkConnectionFlow_10.0.18362.449_neutral_neutral_cw5n1h2txyewy
Microsoft.Windows.ParentalControls_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.PeopleExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.PinningConfirmationDialog_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.SecHealthUI_10.0.18362.449_neutral__cw5n1h2txyewy
Microsoft.Windows.SecureAssessmentBrowser_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.Windows.StartMenuExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy
Microsoft.Windows.XGpuEjectDialog_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Microsoft.XboxGameCallableUI_10.0.18362.449_neutral_neutral_cw5n1h2txyewy Windows.CBSPreview_10.0.18362.449_neutral_neutral_cw5n1h2txyewy windows.immersivecontrolpanel_<IP_ADDRESS>0_neutral_neutral_cw5n1h2txyewy
Windows.PrintDialog_<IP_ADDRESS>_neutral_neutral_cw5n1h2txyewy . The following packages will be removed: NULL
10/20/2020 1:12:12 PM 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com/developer/appx/2015/build is inapplicable, it will be ignored during manifest processing.
10/20/2020 1:12:12 PM 10002 Creating Resiliency File C:\ProgramData\Microsoft\Windows\AppRepository\b7bcf689-76ca-4023-87b5-164ce6fddd37_S-1-5-21-125588297-3509485221-1345772379-124099_2.rslc for Register Operation on Package Microsoft.WindowsTerminal_2020.921.2317.0_neutral_~_8wekyb3d8bbwe.
10/20/2020 1:12:12 PM 607 Deployment Register operation on package Microsoft.WindowsTerminal_2020.921.2317.0_neutral_~_8wekyb3d8bbwe has been de-queued and is running for user SID S-1-5-21-125588297-3509485221-1345772379-124099.
10/20/2020 1:12:12 PM 614 Bundle Uri C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_2020.921.2317.0_neutral_~_8wekyb3d8bbwe\AppxMetadata\AppxBundleManifest.xml contains packages: "CascadiaPackage_1.3.2651.0_x86.msix": Microsoft.WindowsTerminal_1.3.2651.0_x86__8wekyb3d8bbwe "CascadiaPackage_1.3.2651.0_ARM64.msix":
Microsoft.WindowsTerminal_1.3.2651.0_arm64__8wekyb3d8bbwe "CascadiaPackage_1.3.2651.0_x64.msix": Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe.
10/20/2020 1:12:12 PM 854 Successfully added the following uri(s) to be processed: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_2020.921.2317.0_neutral_~_8wekyb3d8bbwe\AppxMetadata\AppxBundleManifest.xml C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe\AppxManifest.xml.
10/20/2020 1:12:12 PM 855 Finished resolving action lists. DeploymentRequest action lists: addPackageList: Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe Microsoft.WindowsTerminal_2020.921.2317.0_neutral_~_8wekyb3d8bbwe.
10/20/2020 1:12:12 PM 573 Setting Sync Enabled status, package family name Microsoft.WindowsTerminal_8wekyb3d8bbwe, enabled false.
10/20/2020 1:12:13 PM 10000 About to service package Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe. Setting the package state to disabled returned with 0x0.
10/20/2020 1:12:13 PM 8100 Starting validation and setting the Trust Label on package Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe with flags 0x9.
10/20/2020 1:12:13 PM 8106 Package Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe has Trust Label already. Flags: 0x9
10/20/2020 1:12:13 PM 8101 Finished validation and setting the Trust Label on package Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe with flags 0x9.
10/20/2020 1:12:13 PM 306 error 0x80070002: While processing the request, the system failed to register the windows.sharedFonts extension due to the following error: The system cannot find the file specified.
.
10/20/2020 1:12:13 PM 316 error 0x80070002: Cannot register the request because the following error was encountered during the registration of the windows.sharedFonts extension: The system cannot find the file specified.
.
10/20/2020 1:12:13 PM 5507 Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe\microsoft.system.package.metadata\S-1-5-21-125588297-3509485221-1345772379-124099-MergedResources-*.pri : No user-specific merged files found
10/20/2020 1:12:13 PM 5507 Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe\microsoft.system.package.metadata\Resources.????????.pri : No shared merged files found
10/20/2020 1:12:13 PM 5507 Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe\microsoft.system.package.metadata\S-1-5-21-125588297-3509485221-1345772379-124099-MergedResources-*.pri : No user-specific merged files found
10/20/2020 1:12:13 PM 5507 Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe\microsoft.system.package.metadata\Resources.????????.pri : No shared merged files found
10/20/2020 1:12:13 PM 300 error 0x80073CF6: Cannot register the Microsoft.WindowsTerminal_8wekyb3d8bbwe package due to the following error: Package could not be registered.
.
10/20/2020 1:12:13 PM 605 The last successful state reached was SingletonRegisterAdd. Failure occurred before reaching the next state RegistrationChanged. hr: 0x80073CF6
10/20/2020 1:12:13 PM 330 error 0x80070002: While removing the request, the system failed to de-register the windows.MRT extension due to the following error: The system cannot find the file specified.
.
10/20/2020 1:12:13 PM 7750 warning 0x80070005: The following error occurred while performing Indexed DB cleanup when removing the package: AppxManifest.xml (Access is denied.
).
10/20/2020 1:12:13 PM 330 error 0x80070005: While removing the request, the system failed to de-register the windows.indexedDB extension due to the following error: Access is denied.
.
10/20/2020 1:12:13 PM 10001 Finished servicing package Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe. Setting the package state to enabled returned with 0x0.
10/20/2020 1:12:13 PM 10001 Finished servicing package Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe. Setting the package state to enabled returned with 0x0.
10/20/2020 1:12:14 PM 401 Deployment Register operation with target volume C: on Package Microsoft.WindowsTerminal_2020.921.2317.0_neutral_~_8wekyb3d8bbwe from: (AppxBundleManifest.xml) failed with error 0x80073D19. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
10/20/2020 1:12:14 PM 404 AppX Deployment operation failed for package Microsoft.WindowsTerminal_2020.921.2317.0_neutral_~_8wekyb3d8bbwe with error 0x80073D19. The specific error text for this failure is: error 0x80070002: While processing the request, the system failed to register the windows.sharedFonts extension due to the following error: The
system cannot find the file specified.
.
This appears to be a repro-case for #3194, but happens without Chocolately or an elevated session.
@TBBle Running that from an elevated Powershell 5.1 prompt allowed me to run WT as admin. Thanks!
I wonder how many of these complaints could be solved with the use of /netonly semantics. It's perfectly possible to run a terminal window as userA and employ runas /netonly to ensure outgoing authenticated connections are made as AdminB. You'd have to create profile that specifically launches cmd or pwsh with runas.
@Wittionary How did you install Windows Terminal? I had assumed #3194 would affect everyone who installed it from the Windows Store or Chocolatey, but if you did one of those, then perhaps it's something system-specific that triggers it.
@TBBle I believe I initially installed it which Chocolate because the Windows Store was previously blocked at my place of employment. And according to choco list -li I've got "microsoft-windows-terminal 1.0.1811.0" although contradicts what "About" is telling me in Terminal (v1.3.2651.0). However, somewhere along the way, the Store was unblocked and I re-installed from there (to see if it would resolve the multiple admin prompts -> File not found issue).
All that to say - the initial install was via choco although the Store may be managing the updates to it now.
In our company we have a second account for doing admin things.
So I open a windows powershell as admin with the admin user.
Then I installed the downloaded msixbundle.
Now I am able to open the terminal als admin. If the application get updated for my admin account i don't know.
@TBBle Running that from an elevated Powershell 5.1 prompt allowed me to run WT as admin. Thanks!
If I do & "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe" then I still get an
Program 'WindowsTerminal.exe' failed to run: Access is deniedAt line:1 char:1
Both from PowerShell 7 and 5, while in Admin privileged sessions
Yes, this is all about security.
Consider the scenario where a domain admin's standard environment is compromised with some form of pernicious malware.
If/when they launch an app from their compromised desktop running as their domain admin account, the malware now has considerable opportunity to key-log/screen-scrape/intercept/divert/delete/block/corrupt/encrypt all kinds of data and systems as domain admin.
Ever wonder how Ransomware takes an entire company offline?
This is why many enterprises and most online services air-gap users from production systems, requiring users to login via RD to a strictly-managed, heavily-restricted hosted VM environment which is severely locked down, regularly re-paved, etc.
Such environments used to be the domain of the rich and famous, but this can now be built very cost effectively with commodity services and tools.
Is this more inconvenient than just runas /user:domainadmin1 "resetpasswords.bat /all"? Yes, but it's designed to be so.
One of the interesting artifacts of such changes is that scripts, automation, and systems get built to replace the user's need to run admin tasks ad-hoc, increasing reliability and repeatability, decreasing errors, and decreasing various other risks. This is where CI/CD came from, and where many enterprises are going.
YMMV.
Correct me if I am wrong, but keyloggers and such will still catch everything you type even if you're RDP'd into a VM from where you do domain admin work. The info will be caught before it is sent through RDP, or caught when providing credentials to initiate your RDP connection.
I've run into this issue as well when working with a laptop from a new corporation that I'm working with. The workarounds suggested haven't resolved my issues with Microsoft Terminal, but they did allow me to get winget working (see referenced issue).
One idea came to mind related to this: if modern apps are all about installation/management for the current, logged in user, and more applications that users may want to run as admin like winget, the Microsoft Terminal, etc. are being built as modern apps to be installed this way, maybe the solution is to reimagine the non-admin login user pairing with an admin elevation user account (cannot log on locally) scenario. The end goal is simply to prevent running day-to-day as admin, while allowing for some content to be run as admin but only as needed, and behind explicit authentication, right? In which case being able to enter elevation credentials (different from your normal password, independently linkable to MFA/modern auth) so that you could execute applications on your system as admin in a more secure manner without dealing with two accounts could solve this problem while supporting the logged on user requirement of modern apps that are installed from the store or sideloaded.
I've run into this issue as well when working with a laptop from a new corporation that I'm working with. The workarounds suggested haven't resolved my issues with Microsoft Terminal, but they did allow me to get winget working (see referenced issue).
One idea came to mind related to this: if modern apps are all about installation/management for the current, logged in user, and more applications that users may want to run as admin like winget, the Microsoft Terminal, etc. are being built as modern apps to be installed this way, maybe the solution is to reimagine the non-admin login user pairing with an admin elevation user account (cannot log on locally) scenario. The end goal is simply to prevent running day-to-day as admin, while allowing for some content to be run as admin but only as needed, and behind explicit authentication, right? In which case being able to enter elevation credentials (different from your normal password, independently linkable to MFA/modern auth) so that you could execute applications on your system as admin in a more secure manner without dealing with two accounts could solve this problem while supporting the logged on user requirement of modern apps that are installed from the store or sideloaded.
Regarding this workaround mentioned above, I was able to get winget registered using that workaround, but as the poster of that linked comment indicated, I receive the same error he did, where the app could not be registered because the Cascadia fonts extension could not be found.
Is there some way to manually register/configure Cascadia fonts for the elevated admin account that cannot log on locally independently of the sideloading workaround for Microsoft Terminal? If the extension is the blocker here, I'm now looking for a workaround to unblock the extension so that I can then just register the Terminal app for my elevated admin account manually.
Regarding this workaround mentioned above, I was able to get winget registered using that workaround, but as the poster of that linked comment indicated, I receive the same error he did, where the app could not be registered because the Cascadia fonts extension could not be found.
Is there some way to manually register/configure Cascadia fonts for the elevated admin account that cannot log on locally independently of the sideloading workaround for Microsoft Terminal? If the extension is the blocker here, I'm now looking for a workaround to unblock the extension so that I can then just register the Terminal app for my elevated admin account manually.
We do understand the scenario well. But as discussed above:
The UWP app model does not (currently) support running modern apps under the identity other than the currently logged-in user
@bitcrazed, what you're saying is interesting but I have evidence to the contrary.
On most of my machines I have at least two user accounts, Me and MeAdmin, the first one being a "standard use" (i.e. member of BUILTIN\Users but not of BUILTIN\Administrators, etc.).
I do most of my work from the standard user, and only specific actions (e.g. upgrade Visual Studio, reconfigure network) through the admin. Usually I do it by "elevating" the required programs (e.g. vs_installer.exe), that is "running them as admin" and only sometimes I log on into another Terminal Services session as the admin user.
When I say "elevate" here I mean what used to be called when UAC just came out "OTS elevation" (Over-The-Shoulder, supposedly when the admin, who's another person, comes and enters the password over my shoulder) rather then "AAM" (Admin Approval Mode; just clicking Yes without entering a password).
Sometimes I get the OTS prompt because the application manifest requires elevation (as does the VS installer prior to 16.9), and sometimes I right click the program and choose Run as administrator (to run cmd.exe or pwsh.exe), but let me be clear here:
In all cases the currently logged on user (to whom the Terminal Services session belongs) is not an administrator. The programs are being run as a different user.
And while logged in as Me, the standard user, I am able to run Windows Terminal as a completely different user, MeAdmin, as long as the following conditions are met:
Windows Terminal is installed for both users, and is of the same version. (If I update it for Me but not for MeAdmin it sometimes fails.)
I'm running Windows Terminal as the other user elevated, through one of the following methods:
Holding Ctrl+Shift and clicking on the Windows Terminal icons pinned to my taskbar.
Right-clicking the Windows Terminal icon pinned to my taskbar, right-clicking again on Windows terminal in the jumplist, and selecting Run as administrator.
Finding Windows Terminal or wt.exe in the Start menu, holding Ctrl+Shift and hitting Enter.
Locating wt.exe in Windows Explorer, either at C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.6.10571.0_x64__8wekyb3d8bbwe\wt.exe or at C:\Users\Me\AppData\Local\Microsoft\WindowsApps\wt.exe or at C:\Users\Me\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe\wt.exe, right-clicking it and selecting Run as administrator.
but not
Running wt.exe from an elevated (running as the other user, MeAdmin) cmd.exe/pwsh.exe/etc.
Locating wt.exe as in item (iv) above, right-clicking while holding Shift, and selecting Run as different user.
TLDR: Contrary to what you wrote, it is possible to run UWP "modern apps under the identity other than the currently logged-in user" AT LEAST WHEN all the following is true: (a) The app is a Centennial/Desktop Bridge/fulltrust/whatever-you-call-it-today app; (b) It is installed for both users; (c) the other user is an administrator, and (d) It is being run as the other user "elevated", with the full token rather than with the UAC-filtered token.
Are (c) and (d) really requirements? I don't know. Maybe there are other ways to run as a different user, but your sweeping declaration is wrong.
Since it is OBVIOUSLY possible to run Windows Terminal as a different user (come one, reproducing what I just wrote will take you less time that it took me to write it...), it's worth checking inside your employer's other departments whether this can be done without elevation, and if so how.
I understand this is somewhat harder than announcing wrong sweeping declarations, but I must ask you try nonetheless.
Since it is OBVIOUSLY possible to run Windows Terminal as a different user (come one, reproducing what I just wrote will take you less time that it took me to write it...), it's worth checking inside your employer's other departments whether this can be done without elevation, and if so how.
I understand this is somewhat harder than announcing wrong sweeping declarations, but I must ask you try nonetheless.
I am certain that there would have been ways to frame this that were less incendiary, but you did not choose to use them.
It looks like the discussion on this thread has run its course. Anybody who has something constructive to add is free to e-mail me their comments.
|
2025-04-01T04:34:43.429208
| 2020-03-04T14:10:20
|
575431351
|
{
"authors": [
"DHowett-MSFT",
"SR-Lut3t1um"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8552",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/issues/4801"
}
|
gharchive/issue
|
Add support for fcntl and ioctl
Description of the new feature/enhancement
As Linux terminals support those features I think it would add a lot to the terminal, if these features would be implemented
Sorry, because ioctl and fcntl are API multiplexing APIs (that take action codes and do things with them) what you’re asking for pretty much amounts to “add some APIs for terminals.” We’ve already got a whole bunch of APIs.
If you’d be willing to describe the specific things you’re looking for, I’d be happy to listen.
|
2025-04-01T04:34:43.435143
| 2021-05-24T16:43:57
|
899829930
|
{
"authors": [
"DHowett",
"kovdu"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8553",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/pull/10164"
}
|
gharchive/pull-request
|
Clear all state tracking nested commands when switching command mode
Went for option 2 proposed here:
https://github.com/microsoft/terminal/issues/10140#issuecomment-845193132.
Disabling back space in the nested entry didn't felt as the nicest
solution. Instead now all state that keeps track of nested commands is
cleared when switching beteen modes.
Validation Steps Performed
Validated the specified issue is fixed by this change:. now after
entering a sub command and hitting backspace the palette no longer
shows the sub command item (here < Select color scheme... ).
Validated that switching between all modes (command line, actions, tab
search & tab switch) still work as expected.
Validated as well that all modes still work as expected.
Didn't add unit tests, but happy to try that out if this would be
required.
Closes #10140
@msftbot merge this in 2 minutes
|
2025-04-01T04:34:43.441289
| 2021-06-09T00:26:41
|
915661956
|
{
"authors": [
"DHowett",
"carlos-zamora"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8554",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/pull/10373"
}
|
gharchive/pull-request
|
Bugfix: serialize iterable commands
Summary of the Pull Request
Fixes a bug where top-level iterable commands were not serialized.
PR Checklist
[X] Closes #10365
[X] Tests added/passed
Detailed Description of the Pull Request / Additional comments
Command::ToJson:
iterable commands deserve the same treatment as nested commands
ActionMap:
Similar to how we store nested commands, iterable commands need to be handled separately from standard commands. Then, when generating the name map, we make sure we export the iterable commands at the same time we export the nested commands.
While working on this bugfix, I realized that another bug exists:
{
"name": "${profile.name}",
"command": { "action": "newTab", "profile": "${profile.name}" },
"iterateOn": "profiles"
},
{
"name": "${profile.name}",
"commands": [ { "command": "newTab" } ]
}
Here, the settings model exports these commands to the command palette as one entry in the name map (the iterable command). This is wrong though, because really the user is explicitly asking for a command named "${profile.name}".
However, this bug already exists in v1.8, but in a different manifestation.
Here's the encountered behaviors:
this PR: iterable command wins
v1.8 & main: whichever command is added second wins (in the case above, nested command)
expected: no conflict
This bugfix brings us closer to a world where this new bug is fixed. We would need to mess with how we expand commands. But (a) that's too risky for a hotfix and (b) this is a really obscure bug.
@DHowett Thoughts?
@DHowett Thoughts?
I'd say just.. file it and we can move on. :smile:
|
2025-04-01T04:34:43.446429
| 2023-08-02T12:46:29
|
1833119503
|
{
"authors": [
"donglixp",
"sunyt32",
"wangmengzhi"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8555",
"repo": "microsoft/torchscale",
"url": "https://github.com/microsoft/torchscale/issues/47"
}
|
gharchive/issue
|
There is a bug in the recurrent_forward function of the multiscale_retention module
kv = prev_kv * (1 - 1 / scale).view(self.num_heads, 1, 1) + kv / scale.view(self.num_heads, 1, 1) line 108 in the multiscale_retention.py
should be
kv = prev_kv * (prev_scale.sqrt() * decay / scale.sqrt()).view(self.num_heads, 1, 1) + kv / scale.sqrt().view(self.num_heads, 1, 1)
because line 65 of retnet.py has the sqrt function
mask = mask / mask.sum(dim=-1, keepdim=True).sqrt()
The division here is to control numerical stability and invariant to LayerNorm. I believe your modification also works.
@wangmengzhi The normalization doesn't affect the final results, because GN is scale-invariant. But it helps to rescale the numerical values. Both should work fine in practice.
I wrote a piece of code to check consistency:
from multiscale_retention import MultiScaleRetention
from retnet import RetNetRelPos
import argparse
import torch
parser = argparse.ArgumentParser()
parser.add_argument('--layernorm_eps', type=float, default=1e-5)
parser.add_argument('--decoder_embed_dim', type=int, default=512)
parser.add_argument('--decoder_retention_heads', type=int, default=2)
parser.add_argument('--recurrent_chunk_size', type=int, default=0)
args = parser.parse_args()
torch.manual_seed(0)
B,T,D=32,100,512
pos=RetNetRelPos(args)
pos_para=pos(T)
ret=MultiScaleRetention(args, args.decoder_embed_dim, args.decoder_retention_heads)
ret.eval()
x=torch.rand(B,T,D)
y1=ret(x,pos_para)
y2=[]
state={}
for t in range(T):
pos_rec=pos(t+1, activate_recurrent=True)
y=ret(x[:,t:t+1], pos_rec, incremental_state=state)
y2.append(y.squeeze(1))
y2=torch.stack(y2).permute(1,0,2)
print((y1-y2).abs().sum().item())
The output is 22011.2265625. If layernorm_eps set to 1e-10, output is<PHONE_NUMBER>9589844
But if I use
kv = prev_kv * (prev_scale.sqrt() * decay / scale.sqrt()).view(self.num_heads, 1, 1) + kv / scale.sqrt().view(self.num_heads, 1, 1)
The output is 0.021843837574124336. The difference is much smaller. I don't think GN is enough.
You are right! .sqrt() here can avoid numerical underflow thus improving consistency and performance. We are looking forward to your pull request.
@wangmengzhi Awesome! Thanks for your insightful suggestion. The improvement looks terrific. We will also do more local tests to compare them.
@wangmengzhi Awesome! Thanks for your insightful suggestion. The improvement looks terrific. We will also do more local tests to compare them.
I'm glad to be of help, and thank you all for proposing such a great Retnet model.
|
2025-04-01T04:34:43.495598
| 2019-09-14T15:46:24
|
493636607
|
{
"authors": [
"JKillian",
"Jessidhia",
"alexanderjarvis",
"arcanis",
"isaacs",
"jwalton",
"orta",
"sandersn",
"weswigham"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8556",
"repo": "microsoft/types-publisher",
"url": "https://github.com/microsoft/types-publisher/pull/655"
}
|
gharchive/pull-request
|
Allow using dev dependencies in a package json
The problem: Styled Components (and other node + RN projects) wants to augment types which come from React Native. The thing is you can't have @types/node and @types/react-native in the same repo because they have conflicting types.
What this has meant is that everyone using styled-components with web uses an old version of @types/styled-components, and the react native folks can use the latest.
A possible solution: Letting a library set a dev dependencies in the package.json for their section of DT. Then, during parsing that dependency is removed from "dependencies" in the npm version of the types and set in "devDependencies".
Using this technique would reduce the dependencies for styled-components from "react", "react-native" and "csstypes" to "react", "csstypes". Allowing people to have those features if they want, but not break builds.
I tested locally that it still works when @types/react-native is removed:
mkdir sc-test
cd sc-test
yarn init --yes; yarn add typescript @types/node @types/styled-components
yarn tsc --init
yarn tsc --noEmit # Found 19 errors.
rm -rf node_modules/@types/react-native
yarn tsc --noEmit # Success
There's a few whitespace and tslint import warnings I fixed on my way through the codebase too
Of the set of "xDependencies" in a package.json - peer dependencies are the only ones which aren't installed by default. This tends to mean that people use it as a weak link (which is why it's example is usually the plugin system where you don't want two copies in the tree for no reason)
So, it's not a "real" dependency in the way that it actually downloads and installs them. In Artsy we used them to indicate the versions which downstream consumers could care about, but have their own choice in the exact version. ( In this package you might not need any of these deps, depending on what parts of the lib you were using )
Do note that it is in npm's roadmap to install peerDependencies by default again, see https://github.com/npm/cli/wiki/Roadmap#proper-peerdependencies-support and the RFC at https://github.com/npm/rfcs/pull/43.
But yes, for nearly everything in DefinitelyTyped, peerDependencies is actually the correct dependency type, and IIUC it only isn't used because of the convenience cost of forcing the user to install them manually.
install peerDependencies by default again
Ergh, that's a shame.
OK, I think this will just have to be a way for a DT package to declare a blacklist for inferred dependencies in the @types/package version. No point in shipping this way and then having to revert in the future when it breaks.
In all fairness, the ultimate culprit is typescript eagerly loading every single @types package installed unless you specify a compilerOptions.types. I was already a user of this whitelisting approach which is how I never noticed the react-native issues for a while...
Of the set of "xDependencies" in a package.json - peer dependencies are the only ones which aren't installed by default.
What about making these devDependencies instead? They're not installed by default.
Aye, that's fair - but automatic type acquisition for JS projects end up needing the config-less option to be solid
but automatic type acquisition for JS projects end up needing the config-less option to be solid
Not sure I followed that. The only real difference between peer dependencies and dev dependencies is that you can constrain what version of the react native types are installed with peer dependencies (well... sort of, you'll get a warning. But you'll get the warning anyways if the peer dependencies are not installed at all).
Thanks for taking up this issue @orta! 😄
OK, I think this will just have to be a way for a DT package to declare a blocklist for inferred dependencies in the @types/package version. No point in shipping this way and then having to revert in the future when it breaks.
I think that seems reasonable. Would also be nice if info could then be added to the package's README: 'If you want to use @types/styled-components with react native, please also install<EMAIL_ADDRESS>or something like that.
It's not perfect: RN users might also have to add some config (compilerOptions.types, .yarnclean) to make sure @types/node aren't messing up their typings, but at the least it lets us support the most popular usecase (web) and still make RN use possible.
peer deps were useful because you could get a message. Ideally, messaging-wise optional dependencies feels the best.
If you're not a react-native developer though, you're also going to get a message every install complaining about missing peer dependencies. :P
I've updated to docs, and I'll poke Ron in chat
Let's talk about this in the design meeting. We have 3-4 possible solutions to this and I think having the whole team's input would be useful.
A couple more ideas Ron and I came up with:
Maybe we need a third dependency kind, "typeDependencies". But this would require a lot of change from npm and the ecosystem.
On the flip side, all the instances I'm aware of this problem are with node, and almost all of them are for Buffer. it would be a lot easier to create a @types/node-buffer module that both @types/node and anybody else could depend on.
Orta gave a good description of the problem above. Here's a summary of the solutions we've come up with so far. I'll update the list as more come in.
Allow devDependencies in DT's package.json. This is the solution I understand the least. You can explicitly install the node dependency but it won't show up otherwise?
a. Allow peerDependencies in DT's package.json. This doesn't install the node dependency (it may in the future), but you may have it from elsewhere if your project already uses node.
Allow a third dependency kind in DT's package.json, "typeDependencies". Actually, I'm not sure how this solves the problem here -- it is great for packages written in Typescript avoid putting type-only dependencies in "dependencies", but doesn't help react-native coexist with node in a compilation.
This only really happens for node types, and almost all the instances are for Buffer. If DT had a @types/node-buffer package, both node and react-native could depend on that.
Forward declarations. react-native could forward declare Buffer without specifying its contents and only types named Buffer would be assignable to it. The declaration might be scoped in some way too.
Allow devDependencies in DT's package.json. This is the solution I understand the least. You can explicitly install the node dependency but it won't show up otherwise?
The idea here is, inside @types/styled-components, we want to modify some types from @types/react-native. So, @types/react-native can't be in "dependencies" of @types/styled-components, because dependencies get installed automatically when you npm install in the package that references @types/styled-components. (Let's call this package that depends on @types/styled-components "referrer", just to give it a name.)
So what we need is a "dependency" that doesn't have this property. "peerDependencies" seems like a good fit here, because the module won't automatically be installed when you npm install in "referrer", except that a) you'll get a warning that there's an unmet peer dependency, and b) in npm 7 it's very likely that the module will, in fact, be installed automatically.
"optionalDependencies" has a nice ring to it, but it behaves like "dependencies" - the only difference is that if a package fails to build, then the package won't be installed. Since there's no build script for @types/react-native, it'll always be installed. (Could we add a build script to @types/react-native that tries to detect if @types/node is installed? Would that work reliably or would it depend on the order things are installed in? Probably not a wonderful idea.)
"devDependencies" is the only kind of dependency left, and that sounds a little weird at first, but it has the behavior we want; if @types/react-native is in "devDependencies" for @types/styled-components, it will not be installed when we do an npm install in "referrer" (just like babel, mocha, etc... are not installed when you install a library that depends on them). If you're in a react-native project, and you want to use @types/styled-components, you very likely already have @types/react-native installed, and if you don't you can certainly explicitly add it, so it works there too.
It's a little bit weird, but then this whole problem is a little bit weird, because @types/react-native isn't really a dependency of @types/styled-components. styled-components doesn't "need" react-native at all, it wants to add things to react-native but only if it's already there. It doesn't depend on it, so much as it "augments" it. (Maybe instead of adding a typeDependencies: to package.json, if we want to go down that road, we should add an augments: to package.json - a list of packages this package modifies if they are present?)
Related: https://github.com/react-native-community/react-native-template-typescript/issues/94
Comment related to this: https://github.com/npm/rfcs/pull/43#issuecomment-546440927
Using peerDependencies as an "optional dep not installed by default" is definitely a kludge that no one should be relying on. Turning off default peer dep installation was a mistake, and was never intended to be permanent. DefinitelyTyped should certainly not rely on that behavior being portable, since @arcanis has indicated that yarn will not match npm's behavior on this.
I would not be opposed to a dep type or flag to indicate that package's optional deps (and optional peerDeps) should not be installed by default. (Sort of like npm's --no-optional flag, but targeted to a single package's deps.)
It'd be good to be able to clarify exactly what DT needs in a dependency type, and then evaluate what gets the closest today, and how we could improve that in the future. Relying on peerDeps not being installed is a bad idea.
Ok, (sorry for the rapid-fire replies here) I think the answer is a lot simpler.
styled-components doesn't "need" react-native at all, it wants to add things to react-native but only if it's already there.
Here's what I'd do. Put it in devDependencies so that you can have a test that verifies the behavior. Don't put it anywhere else. At run-time, load it in a try block, and do the right thing if it's found. Basically, treat it as an unlisted dep (albeit, one that's loaded responsibly with the expectation that it might not be found).
It'd be good to be able to clarify exactly what DT needs in a dependency type, and then evaluate what gets the closest today, and how we could improve that in the future. Relying on peerDeps not being installed is a bad idea.
peerDependencies are the closest thing to what is needed today. Here's what's needed:
Not installed by default. (like peerDependencies today)
No errors if not installed. (like peerDependencies almost is today - it warns non-critically, and it would be nice if the warning were removable)
Validates version match if they are installed as a peer (like peerDependencies today)
If today's peerDependencies was simply renamed to and understood to be optionalPeerDependencies we'd be much better off for it.
At run-time, load it in a try block, and do the right thing if it's found. Basically, treat it as an unlisted dep (albeit, one that's loaded responsibly with the expectation that it might not be found).
try block
try
Excuse me, this isn't about including code. This is about type definitions and the presence thereof - there's nothing to try - either the file is there or it isn't. What we'd like to say is that it's up to the consumer to determine if some other package needs to be present and, if it is, that its version is compatible. There's no code involved.
The challenge for us, testing-wise, is if we go with.. well... any of @sandersn and @orta's solutions, is determining a reasonable test matrix for a project that utilizes them. styled-components is a great example - we probably need to test alongside both @types/node and @types/react-native, but not both simultaneously. It's a very specific and odd constraint that can't quite be captured in a versioning or peering requirement. It's a kind of oneof thing that doesn't exist really anywhere - I think we'd need to setup some special manifest fields and test infrastructure to handle this well.
And TBH, I think a much better fix, @isaacs, than installing peer deps would just be removing the warning on today's peerDependencies entirely and adding a requiredPeerDependencies that behaves like you suggest peerDependencies should in npm/rfcs#43 - this'd minimize breakage and confusion in the ecosysem
As discussed in npm/rfcs#43, the problem with adding a new kind of peerDeps that are installed by default is that most packages using peerDependencies today don't work at all if their peer deps are not found, and work improperly if their peer deps get installed in as a direct dep.
Adding a new thing that behaves as most users are currently using the existing thing isn't as good as making the existing thing behave like people are using it. Making the warnings go away without making the thing the warnings are warning about go away is worse than our current state.
Also, a new kind of peerDeps that are installed by default will be completely ignored by npm v6 and earlier, which presents another problem (albeit one that might only last 2-5 years or so). (While we could theoretically implement that as a non-breaking change, doing so with the current installer codebase would be prohibitively difficult.)
Excuse me, but this isn't about including code. This is about type definitions and the presence thereof - there's nothing to try - either the file is there or it isn't. What we'd like to say is that it's up to the consumer to determine if some other package needs to be present and, if it is, that its version is compatible. There's no code involved, other than npm or another package manager validating and installing.
Gotcha. It sounds like "unlisted dep that you investigate (or don't) at run time" is the way to go then?
For testing, if it's just about verifying that things work in the presence of different files, why not just bundle it as a test fixture?
It's a very specific and odd constraint that can't quite be captured in a versioning or peering requirement.
Not everything has to be delivered via a package manager ;)
Adding a new thing that behaves as most users are currently using the existing thing isn't as good as making the existing thing behave like people are using it. Making the warnings go away without making the thing the warnings are warning about go away is worse than our current state.
Remove peerDependencies entirely then, and replace it with two new dependency kinds (one optional, one not), whose behavior you don't change. Reverting to what is essentially npm 3 behavior isn't going to make the stackoverflow confusion go away, it's going to be magnified, as now you'll have some packages expecting pre-npm-3 behavior, and some packages expecting npm 4-7 behavior. There is no "winner" here, there is no "better" or "intended" behavior. It's definitely churn to silence a few loud voices that'll definitely come back with more equally loud voices who were broken by it. npm's peerDependencies have behaved as they do today for 4 years. 4 years. If you can admit that the core of the issue was the change over in npm 3, swapping back at this point is absolutely not going to solve the problem, since now there's 4 years of packages written with other behavior in mind.
Gotcha. It sounds like "unlisted dep that you investigate (or don't) at run time" is the way to go then?
Then there's nothing validating version range compatibility, which is remarkably important to ensuring things are deduped correctly, which impacts checking (as dupes are nominally separate!). We need something that behaves like peerDependencies does today. Ideally with less warnings.
And let's not forget that https://github.com/npm/npm/issues/3066 was closed and locked in 2015 with the explaination that
Given that peerDependencies at most warn in npm@3, and given that npm no longer causes peerDependencies to be installed, in effect all peerDependencies are optional. I'm not exactly declaring victory and going home here, but with the current behavior, I think there's nothing actionable remaining to this issue, so I'm closing it.
and is the top google search result for "optional peer dependencies", I think you are severely underestimating how breaking https://github.com/npm/rfcs/pull/43 might be. Relying on the current behavior has been the implicit guidance of npm for 4 years.
I think you are severely underestimating how breaking npm/rfcs#43 might be.
I am not going to rehash npm/rfcs#43 all over again here. As stated in that issue, I'm open to reopening it if there are new concerns to consider. Otherwise, there's no need to speculate about "how breaking" it'll be. npm v7 will go through a lengthy beta period, likely including programmatically installing everything in the npm registry, and that process will shake out empirically how much of a good or bad idea it is, along with other changes in that version.
When we have more data, we'll obviously consider it. It could be that peerDeps are made actually optional and ignored by default (by removing the confusing warning, and perhaps adding a new kind of peerDeps that install by default), or that we reserve the spot for them but otherwise do nothing unless the user opts in with a flag, or warn that they will become installed by default in v8. All those changes are easy, but without having the capability of creating a correct tree with peer deps, we are stuck in the current unfortunate state.
Best data available to me today indicates that people who are intimately familiar with package/module system internals are split on installing peer deps by default, and most others are in favor of it. I am not swayed by the intensity of your emotion about it nearly as much as I am by data about which programs and use cases will benefit, and I care much more about people running npm install than the people implementing it. I'm confident that we will want the option to install peer deps for the user easily and correctly, even if it's not done by default, so we're building the capability in v7, which also will allow us to collect better data. Until then, I recommend getting upset about other things instead. But I would advise that you not rely too strongly on peerDeps not being installed by default.
Well, as I said, there is no other dep kind that fills this use, and the npm issue requesting a dependency kind that works like this was closed four years ago, stating that peerDependencies could be used in this way. I should hope you'll at least reopen that issue and reconsider it, then. Even disregarding the break, changing the behavior like the rfc proposes removes a useful dependency kind that we still have use for (perhaps obviously, since we're using it).
Otherwise, there's no need to speculate about "how breaking" it'll be
That's exactly what an RFC is for. We're in this thread because the mere existence of your RFC makes at least one project (and probably more) confused how they should use a feature, where everything was agreed upon before - maybe not in your head, but certainly in everyone else's mind.
Overall, what irks me is that there's already a way to annotate mandatory peer dependencies. Now that we've implemented peerDependenciesMeta everywhere, we have a standard way to add metadata to existing peer dependencies. You could suggest a new field. You could even suggest to extend the already-existing "optional": true flag¹ to also support false as well. You could suggest to deprecate peer dependencies with no explicit optional field at publish time, and let the ecosystem self-correct. You could find a migration plan that would get our support.
Instead, the only option you seem willing to consider is an all-or-nothing plan. Your RFC offers little credible alternatives² and contains very little risk analysis - not even basics like "how many packages in the top 1000 use peer dependencies as optional tags?". It also doesn't describe obvious interactions, such as when two dependencies have similar peer dependencies that cannot overlap. And of course, it doesn't address the portability concern - if npm is the odd duck, won't that just increase confusion amongst your users instead of easing it?
You can tell us you're as data-driven as you want, but so far the only data you provided is a handful of results from a StackOverflow search on "peer dependencies". That's simply not enough to warrant breaking our users' expectations, and that makes me wonder what's the actual motivation.
¹ btw @orta @weswigham, this is what you're looking for. This field is supported by all package managers and will silence any warning when the dependency isn't there (while still printing one in case of mismatched versions).
² "Drop Support for Peer Dependencies Entirely" isn't even remotely possible, "Treat Like Regular Dependencies" isn't an option since the semantic is entirely different, "Treat Like Optional Dependencies" is irrelevant since optional dependencies impact the build, not the resolution.
this is what you're looking for. This field is supported by all package managers and will silence any warning when the dependency isn't there
I couldn't find anything indicating npm supported it? (Though yes, yarn and pnpm do, so we should consider setting it to silence warnings there, anyway, but npm still needs equivalent, especially if it's doing https://github.com/npm/rfcs/pull/43)
I implemented it in npm in https://github.com/npm/cli/pull/224, and it got shipped along with the 6.11. There was a small server-side bug remaining, but as of today it should be fixed for future releases.
@arcanis
You can tell us you're as data-driven as you want, but so far the only data you provided is a handful of results from a StackOverflow search on "peer dependencies". That's simply not enough to warrant breaking our users' expectations, and that makes me wonder what's the actual motivation.
I provided more data in the RFC, and explained further there. The more compelling data points are people reaching out via npm support email, on npm.community, conversations I've had with users directly, and my observations of experienced node.js users asking on Twitter why this doesn't work as they expect.
Please stop misrepresenting my position in this way. I understand that you disagree, but characterizing thousands of person-hours of user research and support work (not to mention hundreds of other SO threads) as a "handful of results on StackOverflow" is disingenuous and offensive. I provided 8 links to stack overflow (and suggested you could search yourself to easily find many more) when you said that it "addresses no particular pain point you had seen reported". Having seen the reports, you dismiss them. So...? Idk?
Instead, the only option you seem willing to consider is an all-or-nothing plan.
All I can do is redirect you to https://github.com/microsoft/types-publisher/pull/655#issuecomment-547212708
What part of that reads as "all or nothing" to you? The RFC hasn't yet been ratified, largely because of the issues you raised, and the v7 beta process will give us a chance to evaluate these concerns empirically. I'm kind of at a loss as to what you actually want or expect from me here.
I am going to stop following this thread, because it's getting repetitive and I cannot be confident that you are participating in good faith.
My email address is<EMAIL_ADDRESS>if anyone wants to continue the discussion productively.
|
2025-04-01T04:34:43.499640
| 2024-07-16T23:47:39
|
2412233216
|
{
"authors": [
"MaryGao",
"lmazuel",
"timotheeguerin"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8557",
"repo": "microsoft/typespec",
"url": "https://github.com/microsoft/typespec/issues/3856"
}
|
gharchive/issue
|
Encode int as string TSP Author doc
Document this encode scenario:
model Foo {
@encode("string")
x: int
}
Would also be good to decide if string is the right key.
Similar issue with https://github.com/microsoft/typespec/issues/2762
|
2025-04-01T04:34:43.500534
| 2023-02-14T18:54:18
|
1584668044
|
{
"authors": [
"tjprescott"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8558",
"repo": "microsoft/typespec",
"url": "https://github.com/microsoft/typespec/pull/1647"
}
|
gharchive/pull-request
|
Allow version enums to live outside the versioned namespace
Fixes #1520.
@markcowl I've revised the logic in this PR if you want to take a second look.
|
2025-04-01T04:34:43.502313
| 2024-02-01T20:59:03
|
2113470190
|
{
"authors": [
"azure-sdk",
"mario-guerra"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8559",
"repo": "microsoft/typespec",
"url": "https://github.com/microsoft/typespec/pull/2876"
}
|
gharchive/pull-request
|
Update homepage.tsx
change 'Typespec' to 'TypeSpec'
You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/2876/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/prs/2876/
|
2025-04-01T04:34:43.528884
| 2021-12-27T03:13:57
|
1088928314
|
{
"authors": [
"Cheney-W",
"JackBoosY",
"dg0yt",
"sfhacker",
"zhuwei07"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8560",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/22217"
}
|
gharchive/issue
|
[windows] vcpkg.exe install packages failed
.\vcpkg.exe install yaml-cpp:x86-windows
Computing installation plan...
The following packages will be built and installed:
vcpkg-cmake[core]:x64-windows -> 2021-12-05
vcpkg-cmake-config[core]:x64-windows -> 2021-12-01
yaml-cpp[core]:x86-windows -> 0.7.0#1
Additional packages (*) will be modified to complete this operation.
Error: in triplet x64-windows: Unable to find a valid Visual Studio instance
Could not locate a complete Visual Studio instance
The following paths were examined for Visual Studio instances:
D:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary/Build\vcvarsall.bat
I have installed the vc2019
Do I have to install vs in dir of C:\ ?
See https://github.com/microsoft/vcpkg/pull/22214
I can't solve the problem by installed the packages you list
vcpkg.exe install yaml-cpp --debug
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'manifests' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Using vcpkg-root: C:\dev\vcpkg
[DEBUG] Failed to open: C:\dev\vcpkg\vcpkg-bundle.json
[DEBUG] Bundle config: readonly=0, usegitregistry=0, embeddedsha=nullopt
[DEBUG] Using scripts-root: C:\dev\vcpkg\scripts
[DEBUG] Using downloads-root: C:\dev\vcpkg\downloads
[DEBUG] Using scripts-root: C:\dev\vcpkg\scripts
[DEBUG] Using builtin-ports: C:\dev\vcpkg\ports
[DEBUG] Using builtin-registry: C:\dev\vcpkg\versions
[DEBUG] Using installed-root: C:\dev\vcpkg\installed
[DEBUG] Using packages-root: C:\dev\vcpkg\packages
[DEBUG] Using buildtrees-root: C:\dev\vcpkg\buildtrees
[DEBUG] Default binary cache path is: C:\Users\Alden\AppData\Local\vcpkg\archives
Computing installation plan...
[DEBUG] Found path: C:\Users\Alden\scoop\shims\cmake.exe
[DEBUG] CreateProcessW("C:\Users\Alden\scoop\shims\cmake.exe" --version)
[DEBUG] cmd_execute_and_stream_data() returned 0 after 78434 us
[DEBUG] CreateProcessW("C:\Users\Alden\scoop\shims\cmake.exe" -DVCPKG_ROOT_DIR=C:/dev/vcpkg -DPACKAGES_DIR=C:/dev/vcpkg/packages -DBUILDTREES_DIR=C:/dev/vcpkg/buildtrees -D_VCPKG_INSTALLED_DIR=C:/dev/vcpkg/installed -DDOWNLOADS=C:/dev/vcpkg/downloads -DVCPKG_MANIFEST_INSTALL=OFF -P "C:\dev\vcpkg\buildtrees\0.vcpkg_tags.cmake")
[DEBUG] cmd_execute_and_stream_data() returned 0 after 68443 us
The following packages will be built and installed:
vcpkg-cmake[core]:x64-windows -> 2021-12-05
vcpkg-cmake-config[core]:x64-windows -> 2021-12-01
yaml-cpp[core]:x86-windows -> 0.7.0#1
Additional packages (*) will be modified to complete this operation.
[DEBUG] CreateProcessW("C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -all -prerelease -legacy -products * -format xml)
[DEBUG] cmd_execute_and_stream_data() returned 0 after 25352 us
Error: in triplet x64-windows: Unable to find a valid Visual Studio instance
Could not locate a complete Visual Studio instance
The following paths were examined for Visual Studio instances:
D:\Program Files (x86)\Microsoft Visual Studio\2022\Professional\VC\Auxiliary/Build\vcvarsall.bat
[DEBUG] D:\a_work\1\s\src\vcpkg\vcpkgpaths.cpp(1347)
[DEBUG] Time in subprocesses: 172229 us
[DEBUG] Time in parsing JSON: 41 us
[DEBUG] Time in JSON reader: 63 us
[DEBUG] Time in filesystem: 2218 us
[DEBUG] Time in loading ports: 502 us
[DEBUG] Exiting after 195.8 ms (185601 us)
@JackBoosY this problem has bothered me for a long time
below is the result of vswhere.exe
bd204dce
2021-12-28T15:14:02Z
VisualStudio/17.0.4+32014.148
D:\Program Files (x86)\Microsoft Visual Studio\2022\Professional
17.0.32014.148
Microsoft.VisualStudio.Product.Professional
D:\Program Files (x86)\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
4294967295
1
1
0
0
Visual Studio Professional 2022
为小型团队量身定制的专业 IDE
VisualStudio.17.Release
https://aka.ms/vs/17/release/channel
C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service
https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes-v17.0#17.0.4
https://go.microsoft.com/fwlink/?LinkId=661288
2021-12-28T15:14:02.6141847Z
d17.0
17.0.32014.148
VisualStudio/17.0.4+32014.148
build-lab
VisualStudio
installer
17.0.4
Dev17
2022
RTW
False
Visual Studio
4
1.0
17.0.4+32014.148
3.0.4496.34889
1
VisualStudio.17.Release/17.0.4+32014.148
C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe
Please check the following Visual Studio components in Visual Studio Installer:
Please ensure you've installed the following Visual Studio Components using
Visual Studio Installer:
- Windows Universal C Runtime
- C++ Build Tools core features
- Visual Studio Build tools:
* VC++ 2017 version ... latest v141 tools (for Visual Studio 2017)
* MSVC v142 - VS 2019 C++ x64/x86 build tools (for Visual Studio 2019)
* MSVC v143 - VS 2022 C++ x64/x86 build tools (for Visual Studio 2022)
- MSBuild
- Windows SDK
- English language Pack
For ARM / ARM64 or UWP triplet, please also installed:
- Visual Studio Build tools for ARM:
* VC++ 2017 version ... Libs for Spectre (ARM) (for Visual Studio 2017)
* MSVC v142 - VS 2019 C++ ARM build tools (for Visual Studio 2019)
* MSVC v143 - VS 2022 C++ ARM build tools (for Visual Studio 2022)
- Visual Studio Build tools for ARM64:
* VC++ 2017 version ... Libs for Spectre (ARM64) (for Visual Studio 2017)
* MSVC v142 - VS 2019 C++ ARM64 build tools (for Visual Studio 2019)
* MSVC v143 - VS 2022 C++ ARM64 build tools (for Visual Studio 2022)
- Visual Studio Build tools for UWP:
* Visual C++ runtime for UWP (for Visual Studio 2017)
* C++ Universal Windows Platform support for v142 build tools (for Visual Studio 2019)
* C++ Universal Windows Platform support for v143 build tools (for Visual Studio 2022)
I'm sure I have installed:
Visual Studio Build tools:
MSVC v143 - VS 2022 C++ x64/x86 build tools (for Visual Studio 2022)
MSBuild
Windows SDK
English language Pack
But, how to check fellows:
- Windows Universal C Runtime
- C++ Build Tools core features
I have installed it
Please note that vcpkg will choose the newer Visual Studio.
Can you make sure whether this path is exist: D:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary/Build\vcvarsall.bat
I have installed the newest vs2022
And
D:\Program Files (x86)\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build has vcvarsall.bat
I think your Visual Studio is broken, please repair it using Visual Studio Installer.
It still doesn't work after repairing
@zhuwei07 What's the version of your VCPKG? If you are not using the latest vcpkg, I suggest trying it.
And please double confirm you've installed the English language pack.
Please git pull vcpkg and rerun bootstrap script then try agian.
@zhuwei07 What's the version of your VCPKG? If you are not using the latest vcpkg, I suggest trying it.
I have got the latest vcpkg.
when I update the vcpkg, the problem happened.
Can you please use powershell instead?
cc @BillyONeal do you know why?
I installed to the default path, it works!!!
I installed to the default path, it works!!!
Of couse it works, but the problem is the non-default path doesn't work.
Found path: C:\Users\Alden\scoop\shims\cmake.exe
scoop is a possible source of problems in vcpkg:
https://github.com/microsoft/vcpkg/issues/25528#issuecomment-1174217103
This is from 2021! Thanks.
|
2025-04-01T04:34:43.540430
| 2022-02-16T07:58:36
|
1139660292
|
{
"authors": [
"JackBoosY",
"TomErnst"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8561",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/23127"
}
|
gharchive/issue
|
[icu] Build error
Host Environment
OS: Windows Server 2019 Standard
To Reproduce
execute <MumbleDir>\scripts\vcpkg\get_mumble_dependencies.ps1 in Windows Powershell ISE
Failure logs
-- Configuring x64-windows-static-md-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:128 (message):
Command failed: C:/Users/Administrator/vcpkg/downloads/tools/msys2/803521c5733336c9/usr/bin/bash.exe --noprofile --norc -
-debug -c "V=1 CPP='compile cl.exe -E' CC='compile cl.exe' CC_FOR_BUILD='compile cl.exe' CXX='compile cl.exe' RC='windres-rc
rc.exe' WINDRES='windres-rc rc.exe' AR='ar-lib lib.exe' LD='link.exe -verbose' RANLIB=':' STRIP=':' NM='dumpbin.exe -symbols
-headers' DLLTOOL='link.exe -verbose -dll' CCAS=':' AS=':' ./../src/c-69_1-src-b48be0c7ce.clean/source/configure --build=x86_
64-pc-mingw32 "--enable-icu-build-win" "--disable-samples" "--disable-tests" "--disable-layoutex" "--with-cross-buil
d=/C/Users/Administrator/vcpkg/installed/x64-windows/tools/icu" "ac_cv_prog_ac_ct_STRIP=:" "gl_cv_double_slash_root=yes"
"ac_cv_func_memmove=yes" "--disable-silent-rules" "--verbose" "--disable-shared" "--enable-static" "--enable-debu
g" "--disable-release" "--prefix=/C/Users/Administrator/vcpkg/installed/x64-windows-static-md/debug" "--bindir=\${pref
ix}/../tools/icu/debug/bin" "--sbindir=\${prefix}/../tools/icu/debug/sbin" "--libdir=\${prefix}/lib" "--includedir=\
${prefix}/../include" "--datarootdir=\${prefix}/share/icu""
Working Directory: C:/Users/Administrator/vcpkg/buildtrees/icu/x64-windows-static-md-dbg
Error code: 1
See logs for more information:
C:\Users\Administrator\vcpkg\buildtrees\icu\config-x64-windows-static-md-dbg-out.log
C:\Users\Administrator\vcpkg\buildtrees\icu\config-x64-windows-static-md-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_make.cmake:811 (vcpkg_execute_required_process)
ports/icu/portfile.cmake:51 (vcpkg_configure_make)
scripts/ports.cmake:145 (include)
Error: Building package icu:x64-windows-static-md failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with git pull and .\vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+icu
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[icu]+Build+error
including:
package: icu[core]:x64-windows-static-md -> 69.1#18
vcpkg-tool version: 2022-02-11-dac008bf9b55ef48e10bcc81e273b97a82bbf72d
vcpkg-scripts version: 9341313ad 2022-02-15 (8 hours ago)
Contents of C:\Users\Administrator\vcpkg\buildtrees\icu\config-x64-windows-static-md-dbg-err.log:
configure: WARNING: unrecognized options: --disable-silent-rules
configure: error: Namespace support is required to build ICU.
Meanwhile I have posted a second issue, because I ran into the same mess again, although I followed the given instructions (build documentation) slavishly.
I described the whole context better and emphasized the importance and urgency of this issue, please look at [https://github.com/mumble-voip/mumble/issues/5581].
C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/Llvm/bin/clang-cl.exe
|
2025-04-01T04:34:43.546416
| 2022-02-24T00:13:51
|
1148715200
|
{
"authors": [
"FrankXie05",
"JackBoosY",
"davidmatson",
"kennykerr",
"walbourn"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8562",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/23249"
}
|
gharchive/issue
|
[cppwinrt] update to 2.0.220131.2
Library name:
cppwinrt
New version number:
2.0.220131.2
Other information that may be useful (release notes, etc...)
The current port is a no-op, saying to get the code from the Windows SDK. But the Windows SDK version is an old version - the latest is on GitHub as a source and NuGet package release:
https://github.com/microsoft/cppwinrt/releases/tag/2.0.220131.2
I'm not sure what it would take to get the actual cppwinrt tool working properly with vcpkg, and no longer pointing to the old version in the Windows SDK instead.
@davidmatson Thanks for posting this issue, Since the PR https://github.com/microsoft/vcpkg/pull/14092, this port has been changed to be empty. I'm closing this issue, as it doesn't need updating.
@FrankXie05 - what's the right way to track requesting a non-empty port?
Thanks,
David
This port depends on the Windows SDK, so if you have a newer Windows SDK installed and remove-reinstall this port.
It will be updated to the latest.
I believe C++/WinRT recommends not using the Windows SDK version because it's older and recommend using what's available from NuGet releases instead.
@davidmatson Can you provide some links to prove it please?
https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/intro-to-using-cpp-with-winrt#sdk-support-for-cwinrt
Although it is now present only for compatibility reasons, as of version 10.0.17134.0 (Windows 10, version 1803), the Windows SDK contains a header-file-based standard C++ library for consuming first-party Windows APIs (Windows Runtime APIs in Windows namespaces). Those headers are inside the folder %WindowsSdkDir%Include<WindowsTargetPlatformVersion>\cppwinrt\winrt. As of the Windows SDK version 10.0.17763.0 (Windows 10, version 1809), these headers are generated for you inside your project's $(GeneratedFilesDir) folder.
Again for compatibility, the Windows SDK also comes with the cppwinrt.exe tool. However, we recommend that you instead install and use the most recent version of cppwinrt.exe, which is included with the Microsoft.Windows.CppWinRT NuGet package. That package, and cppwinrt.exe, are described in the sections above.
See also https://github.com/microsoft/vcpkg/pull/14092#issuecomment-1050332234
https://github.com/microsoft/vcpkg/pull/24967
|
2025-04-01T04:34:43.551312
| 2022-05-16T15:31:18
|
1237335486
|
{
"authors": [
"I-love-study",
"JackBoosY",
"MonicaLiu0311"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8563",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/24733"
}
|
gharchive/issue
|
[sqlpp11] "The following variables are not used in CMakeLists.txt: ENABLE_TESTS" while install
Host Environment
OS: Windows 11 21H2
Compiler: Visual Studio 2022 17.2.0
package: sqlpp11[core]:x64-windows -> 0.60#1
vcpkg-tool version: 2022-03-30-692785ac944e81417840c6de244fb3e18a4b35eb
vcpkg-scripts version: 5e7cbdcea 2022-05-15 (11 hours ago)
To Reproduce
Steps to reproduce the behavior:
./vcpkg install sqlpp11:x64-windows
Failure logs
❯ ./vcpkg install sqlpp11:x64-windows
Computing installation plan...
The following packages will be built and installed:
sqlpp11[core]:x64-windows -> 0.60#1
Detecting compiler hash for triplet x64-windows...
Restored 0 packages from C:\Users\I_Love_Study\AppData\Local\vcpkg\archives in 136.6 us. Use --debug to see more details.
Starting package 1/1: sqlpp11:x64-windows
Building package sqlpp11[core]:x64-windows...
-- Using cached rbock-sqlpp11-085713d4d301aeb58e7d14f44cfac6ce35fe2e77.tar.gz.
-- Cleaning sources at E:/Code/vcpkg/buildtrees/sqlpp11/src/ce35fe2e77-e49beaacfc.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source E:/Code/vcpkg/downloads/rbock-sqlpp11-085713d4d301aeb58e7d14f44cfac6ce35fe2e77.tar.gz
-- Applying patch ddl2cpp_path.patch
-- Applying patch fix-dependency.patch
-- Using source at E:/Code/vcpkg/buildtrees/sqlpp11/src/ce35fe2e77-e49beaacfc.clean
-- Found external ninja('1.10.2').
-- Configuring x64-windows
CMake Warning at scripts/cmake/vcpkg_configure_cmake.cmake:448 (message):
The following variables are not used in CMakeLists.txt:
ENABLE_TESTS
Please recheck them and remove the unnecessary options from the
`vcpkg_configure_cmake` call.
If these options should still be passed for whatever reason, please use the
`MAYBE_UNUSED_VARIABLES` argument.
Call Stack (most recent call first):
ports/sqlpp11/portfile.cmake:13 (vcpkg_configure_cmake)
scripts/ports.cmake:146 (include)
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:158 (message):
Command failed: D:/CMake/bin/cmake.exe --build . --config Debug --target install -- -v -j17
Working Directory: E:/Code/vcpkg/buildtrees/sqlpp11/x64-windows-dbg
See logs for more information:
E:\Code\vcpkg\buildtrees\sqlpp11\install-x64-windows-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:113 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:44 (vcpkg_build_cmake)
ports/sqlpp11/portfile.cmake:20 (vcpkg_install_cmake)
scripts/ports.cmake:146 (include)
error: building sqlpp11:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `git pull` and `.\vcpkg update`.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+sqlpp11
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[sqlpp11]+Build+error
including:
package: sqlpp11[core]:x64-windows -> 0.60#1
vcpkg-tool version: 2022-03-30-692785ac944e81417840c6de244fb3e18a4b35eb
vcpkg-scripts version: 5e7cbdcea 2022-05-15 (11 hours ago)
Additionally, attach any relevant sections from the log files above.
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
I confirm this option was removed, and it will be fixed by updating this port to the next release to reduce the modification.
Fixed by https://github.com/microsoft/vcpkg/pull/25458.
|
2025-04-01T04:34:43.561449
| 2022-05-18T21:37:38
|
1240556190
|
{
"authors": [
"Adela0814",
"terrylyons"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8564",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/24788"
}
|
gharchive/issue
|
[gmp] build failure
Host Environment
OS: [Linux]
Compiler: g++ (Ubuntu 9.3.0-10ubuntu2) 9.3.0
~/vcpkg$ cmake --version
cmake version 3.23.1
To Reproduce
Clean virtual ubuntu machine
with git, cmake, autoconf and all the tools needed for cross compilation in C++ with visual studio
Clean clone of vcpgk ; git pull and vcpkg update both say up to date.
then:
./vcpkg install gmp
Failure logs
terry@terry-vm3:~/vcpkg$ ./vcpkg install gmp
Computing installation plan...
The following packages will be built and installed:
gmp[core]:x64-linux -> 6.2.1#9
Detecting compiler hash for triplet x64-linux...
Restored 0 packages from /home/terry/.cache/vcpkg/archives in 3.9 us. Use --debug to see more details.
Installing 1/1 gmp:x64-linux...
Building gmp[core]:x64-linux...
-- Using cached gmp-6.2.1.tar.xz.
-- Cleaning sources at /home/terry/vcpkg/buildtrees/gmp/src/gmp-6.2.1-f412680bba.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/terry/vcpkg/downloads/gmp-6.2.1.tar.xz
-- Applying patch tools.patch
-- Using source at /home/terry/vcpkg/buildtrees/gmp/src/gmp-6.2.1-f412680bba.clean
-- Getting CMake variables for x64-linux-dbg
-- Getting CMake variables for x64-linux-rel
-- Generating configure for x64-linux
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:128 (message):
Command failed: /usr/bin/autoreconf -vfi
Working Directory: /home/terry/vcpkg/buildtrees/gmp/src/gmp-6.2.1-f412680bba.clean/
Error code: 1
See logs for more information:
/home/terry/vcpkg/buildtrees/gmp/autoconf-x64-linux-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_make.cmake:629 (vcpkg_execute_required_process)
ports/gmp/portfile.cmake:46 (vcpkg_configure_make)
scripts/ports.cmake:146 (include)
error: building gmp:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+gmp
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[gmp]+Build+error
Include '[gmp] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2022-05-05-67e17c1782801cf481be9ac0b3765dff3e4bdeb8
vcpkg-scripts version: 261ca0dd4 2022-05-18 (12 hours ago)
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
@terrylyons please install autoreconf first,
These can be installed on Ubuntu systems via
sudo apt-get update -y
sudo apt-get install -y autoconf-archive
if the issue still exists, please provide the failure log:
/home/terry/vcpkg/buildtrees/gmp/autoconf-x64-linux-err.log
@terrylyons Has your problem been solved?
We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.
|
2025-04-01T04:34:43.580600
| 2023-08-08T07:15:09
|
1840709730
|
{
"authors": [
"FrankXie05",
"WangHHY19931001"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8565",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/33028"
}
|
gharchive/issue
|
[libsndfile] build failure
Operating system
windows
Compiler
No response
Steps to reproduce the behavior
vcpkg install libsndfile:arm64-android
Failure logs
-- Downloading https://github.com/libsndfile/libsndfile/archive/1.2.0.tar.gz -> libsndfile-libsndfile-1.2.0.tar.gz...
-- Extracting source C:/vcpkg/downloads/libsndfile-libsndfile-1.2.0.tar.gz
-- Using source at C:/vcpkg/buildtrees/libsndfile/src/1.2.0-fe224c8d1f.clean
-- Configuring arm64-android
-- Building arm64-android-dbg
-- Building arm64-android-rel
CMake Error at installed/x64-windows/share/vcpkg-cmake-config/vcpkg_cmake_config_fixup.cmake:36 (message):
'C:/vcpkg/packages/libsndfile_arm64-android/debug/cmake' does not exist.
Call Stack (most recent call first):
ports/libsndfile/portfile.cmake:48 (vcpkg_cmake_config_fixup)
scripts/ports.cmake:147 (include)
Additional context
No response
This directory debug/cmake should not exist.
https://github.com/microsoft/vcpkg/blob/ad46340bfce415333d6a2139592c22a499fb0df0/ports/libsndfile/portfile.cmake#L42
|
2025-04-01T04:34:43.604528
| 2024-12-25T18:08:48
|
2759045134
|
{
"authors": [
"jimwang118",
"marc2k3",
"pascal754"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8566",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/42927"
}
|
gharchive/issue
|
[fmt] Update to 11.1.0
Library name
fmt
New version number
11.1.0
Other information that may be useful (release notes, etc...)
https://github.com/fmtlib/fmt/releases/tag/11.1.0
I naively thought updating this would be easy and opened my first ever pull for it #42928 but fixing the dependency failures is totally beyond me. I shall have to defer to someone with more expertise. Sorry for the noise.
Thanks for your contribution, I will fix this issue.
fmt v11.1.1 was released.
https://github.com/fmtlib/fmt/releases/tag/11.1.1
|
2025-04-01T04:34:43.613134
| 2019-09-27T22:44:48
|
499680573
|
{
"authors": [
"PhoebeHui",
"am2222",
"cbezault",
"dg0yt",
"lakinwecker",
"vicroms"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8567",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/8377"
}
|
gharchive/issue
|
Gdal builds, but no instructions for how to link it are given
GDAL builds, but no instructions on how to link are provided
When you build gdal on linux (or windows) you are not given any further instructions on how to use it or link with it. Considering that gdal links with quite a few different libraries, it's difficult to know which ones to link with and how. Some of them are static libraries inside of the vcpkg installed directory.
Considering that I need to build this and link against this library on both windows and linux in the upcoming weeks, I'd be happy to work on this. I'm not really sure where to start though. gdal isn't CMake based, but it does seem to provide some amount of pkg-config information. What is the usual process for ports that are not cmake based?
Environment
OS: Linux
Compiler: g++/clang
To Reproduce
Steps to reproduce the behavior:
./vcpkg install gdal
See lack of build instructions
Expected behavior
A clear and concise description of how to link with gdal.
Failure logs
➜ ./vcpkg install gdal
Warning: Different source is available for vcpkg (2019.8.27 -> 2019.6.26). Use .\bootstrap-vcpkg.bat to update.
The following packages will be built and installed:
gdal[core]:x64-linux
* sqlite3[core]:x64-linux
Additional packages (*) will be modified to complete this operation.
Starting package 1/2: sqlite3:x64-linux
Building package sqlite3[core]:x64-linux...
-- Downloading https://sqlite.org/2019/sqlite-amalgamation-3280000.zip...
-- Extracting source /home/lakin/software/vcpkg/downloads/sqlite-amalgamation-3280000.zip
-- Using source at /home/lakin/software/vcpkg/buildtrees/sqlite3/src/3280000-19670be87f
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Building x64-linux-rel
-- Performing post-build validation
-- Performing post-build validation done
Building package sqlite3[core]:x64-linux... done
Installing package sqlite3[core]:x64-linux...
Installing package sqlite3[core]:x64-linux... done
Elapsed time for package sqlite3:x64-linux: 40.37 s
Starting package 2/2: gdal:x64-linux
Building package gdal[core]:x64-linux...
Warning: abi keys are missing values:
libwebp
libxml2
-- Using cached /home/lakin/software/vcpkg/downloads/gdal241.zip
-- Extracting source /home/lakin/software/vcpkg/downloads/gdal241.zip
-- Applying patch /home/lakin/software/vcpkg/ports/gdal/0001-Fix-debug-crt-flags.patch
-- Applying patch /home/lakin/software/vcpkg/ports/gdal/0002-Fix-static-build.patch
-- Applying patch /home/lakin/software/vcpkg/ports/gdal/0003-Fix-std-fabs.patch
-- Extracting source /home/lakin/software/vcpkg/downloads/gdal241.zip
-- Applying patch /home/lakin/software/vcpkg/ports/gdal/0001-Fix-debug-crt-flags.patch
-- Applying patch /home/lakin/software/vcpkg/ports/gdal/0002-Fix-static-build.patch
-- Applying patch /home/lakin/software/vcpkg/ports/gdal/0003-Fix-std-fabs.patch
-- Configuring x64-linux-rel
-- Building x64-linux-rel
-- Installing x64-linux-rel
-- Installing x64-linux-rel done
-- Configuring x64-linux-dbg
-- Building x64-linux-dbg
-- Installing x64-linux-dbg
-- Installing x64-linux-dbg done
-- Performing post-build validation
-- Performing post-build validation done
Building package gdal[core]:x64-linux... done
Installing package gdal[core]:x64-linux...
Installing package gdal[core]:x64-linux... done
Elapsed time for package gdal:x64-linux: 1.111 h
Total elapsed time: 1.122 h
Additional context
None.
Hi @lakinwecker
There's a FindGDAL module shipped with CMake, which will define target GDAL::GDAL.
find_package(GDAL REQUIRED)
target_link_libraries(mytarget PRIVATE GDAL::GDAL)
Thanks for that. Should this package print that out at the end of the installation process?
I'm still running in to some linking issues after including the above, but I will file those as a separate issue once I have confirmed it's not something wrong with my environment.
In addition, in order to get this to link, I have to add:
find_package(OpenSSL REQUIRED)
set(LIBRARIES ${LIBRARIES} OpenSSL::SSL OpenSSL::Crypto)
Without this, I get:
/usr/bin/ld: /home/lakin/software/vcpkg/installed/x64-linux/lib/libcurl.a(openssl.c.o): undefined reference to symbol 'SSL_write@@OPENSSL_1_1_0'
/usr/bin/ld: /usr/lib/libssl.so.1.1: error adding symbols: DSO missing from command line
```
Because it tries to link to my local crypto library.
Are you using the most recent version of our curl port? I could have sworn I fixed that issue...
AFAIK, I am. I pulled from master today and updated everything. Is there some output I can provide to prove it?
No I believe you. It just means I missed something.
Well, I'm happy to test stuff. Feel free to ping me if you want me to test out any PRs, etc.
@lakinwecker How I can find GDAL_INCLUDE_DIRS and GDAL_LIBRARIES variables without using FindGDAL module in CMAKE? I want to manually link this library to my build command line
Currently the usage file was provided for gdal, you can use it as following.
The package GDAL provides CMake targets:
find_package(GDAL REQUIRED)
target_include_directories(main PRIVATE ${GDAL_INCLUDE_DIRS})
target_link_libraries(main PRIVATE ${GDAL_LIBRARIES})
For Linux, gdal is completely broken, #9068. I'm working on it, but there is no point in relying on pkgconfig or cmake files as long as there is no control about dependencies from the system used when building port gdal.
|
2025-04-01T04:34:43.620518
| 2020-06-13T16:28:25
|
638190825
|
{
"authors": [
"RT222",
"vicroms"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8568",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/11919"
}
|
gharchive/pull-request
|
[imgui] Add Freetype feature
-Add Freetype feature, which use Freetype instead of stb_truetype to build the font atlases (https://github.com/ocornut/imgui/tree/master/misc/freetype).
-Add imgui_internal.h to public includes, because it is required to use the experimental API and improve debug capabilities. It's also required to build Implot (#11920).
-Add imgui_stdlib files to allow std::string usage with Imgui text functions (https://github.com/ocornut/imgui/issues/2035).
-Fix bindings feature requiring SDL1 dependency instead of SDL2 (Imgui SDL binding is using the latter).
I'd also like to suggest to remove or at least split the bindings feature. Imgui bindings are not really part of the library, and including them all in the same feature require many dependencies to be fetched, which is probably overkill in most cases. Also copying cpp files to the include folder should be avoided.
Thanks for the PR!
I'm not familiar with imgui, are the bindings just example code? Or what is their purpose?
I think having them as a non-default feature is good enough, some ports already have "examples" features that do the same.
These bindings are very well maintained, feature complete and the author recommend to use them by default except if a custom implementation is really needed : https://github.com/ocornut/imgui#integration
I think it's a good thing they are available as features for this port. What I dislike is the inability to pick only the required ones, it's all or nothing. Because of this, you are forced to acquire a lot of dependencies you will probably never need. It's also ugly because it isn't compiled to libs but rely instead on the manual inclusion of cpp files in your project, because some of them depends on platform specific APIs that can't be compiled everywhere.
Splitting these bindings to different features would solve these problems. The only drawback is that we would have a very long list of features :
Allegro5
Dx9
Dx10
Dx11
Dx12
Glfw
Glut
Marmalade
Metal
Opengl2
Opengl3
Osx
Sdl
Vulkan
Win32
I don't know if it's acceptable for ports to have such a long feature list, but if it is, it would be a better solution than the current one.
|
2025-04-01T04:34:43.622284
| 2021-01-12T02:49:37
|
783862425
|
{
"authors": [
"NancyLi1013",
"adam-bloom"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8569",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/15585"
}
|
gharchive/pull-request
|
[speexdsp] Configure and install speexdsp.pc
Describe the pull request
What does your PR fix?
The speexdsp port did not previously configure and support pkgconfig.
LGTM now, thanks for your PR @adam-bloom.
LGTM now, thanks for your PR @adam-bloom.
|
2025-04-01T04:34:43.626697
| 2021-12-01T08:51:40
|
1068128895
|
{
"authors": [
"BillyONeal",
"JackBoosY"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8570",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/21788"
}
|
gharchive/pull-request
|
[pcl] Add feature apps, visualization, simulation, examples and add usage
Add the following features:
apps
visualization
examples
simulation
Add usage file since the usage provided by vcpkg is incorrect.
Fixes #15130.
Already test all features on x86-windows.
We can make this feature depend on pcl[core,visualization] right?
@BillyONeal I think the name of this feature cannot completely replace the corresponding function.
Many features in pcl rely on vtk, but vtk does not necessarily refer to these features.
Since this involves modification history, we can only keep this feature, but maybe it is more appropriate to set it as an alias for visualization?
We can make this feature depend on pcl[core,visualization] right?
@BillyONeal I think the name of this feature cannot completely replace the corresponding function. Many features in pcl rely on vtk, but vtk does not necessarily refer to these features.
Since this involves modification history, we can only keep this feature, but maybe it is more appropriate to set it as an alias for visualization?
@here-mikelley @raahilsha-z @UnaNancyOwen @claudiofantacci @fran6co What do you think about this?
If there is no objection, I will convert vtk to alias tomorrow.
Thanks for the feature fixes!
|
2025-04-01T04:34:43.630366
| 2023-02-14T21:49:13
|
1584876960
|
{
"authors": [
"LilyWangLL",
"RT222",
"Tabizzz"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8571",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/29659"
}
|
gharchive/pull-request
|
[imgui] Update to 1.89.3
Update imgui from 1.89.2 to 1.89.3 : https://github.com/ocornut/imgui/releases/tag/v1.89.3
[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.
👀
All features passed with following triplets:
x86-windows
x64-windows
x64-windows-static
|
2025-04-01T04:34:43.639221
| 2024-05-02T14:47:16
|
2275735091
|
{
"authors": [
"Neumann-A",
"bansan85"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8572",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/38530"
}
|
gharchive/pull-request
|
[vtk] Fix build of vtkHDF5Helper (#38529)
Fixes #38529
[X] Changes comply with the maintainer guide.
[X] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] Any fixed CI baseline entries are removed from that file.
[X] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.
Are you building for x86? Normally hid_t should be 64bit
Are you building for x86? Normally hid_t should be 64bit
No. It's x64. You're right, I don't know why it doesn't compile. And I hit the problem under Windows and Linux. This is why I said I have an old HDF5 library. It's probably related to the old version. But since it's a new bug in vtk and the patch is simple, I sent it. I also sent the patch to the mainstream repository.
And I hit the problem under Windows and Linux. This is why I said I have an old HDF5 library. It's probably related to the old version.
Yeah its the old version. There was an ABI break in HDF. They switch from int32 to int64. Are you interfacing with old MATLAB versions? MATLAB took quite a while to adopt a newer HDF5.
https://docs.hdfgroup.org/hdf5/rfc/64bit_hid_t-v1.docx.pdf
😁 Exactly, but even with Matlab 2022, it uses v1.8 :/
That is strange since they switched with 2021b to 1.10.7 if I trust the release notes.
That is strange since they switched with 2021b to 1.10.7 if I trust the release notes.
Under Linux, when I run export HDF5_DISABLE_VERSION_CHECK=1 && /opt/matlab/R2022b/bin/matlab -batch runTestsCi:
Warning! ***HDF5 library version mismatched error***
...
Headers are 1.8.23, library is 1.8.12
So Matlab have hdf5 1.8.12.
Again strange because https://www.scivision.dev/matlab-hdf5-version/ also says matlab has a higher version but ok.
It is strange that you had no problems on windows since i had problems on windows when mixing newer hdf5 with the older version from matlab.
Under Linux R2022b, [major,minor,rel] = H5.get_libversion() gave me 1.10.8.
But HDF5 v1.8 comes from /opt/matlab/R2022b/bin/glnxa64/libhdf5-1.8.so.8.0.1
My MATLAB shared library is built with all dependencies built as static library. I only have one big shared library with hdf5 library embedded. Maybe this avoided me some troubles under Windows ?
@FrankXie05 I sent a MR to Kitware about this problem. It should be merge.
|
2025-04-01T04:34:43.645892
| 2019-05-16T08:40:21
|
444826358
|
{
"authors": [
"JackBoosY",
"cenit"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8573",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/6474"
}
|
gharchive/pull-request
|
[armadillo]Fix usage error.
Add dependent port openblas.
Add vcpkg_configure_cmake options.
Fix share path error in linux.
Add dependent port clapack.
Relate: #5804.
BTW: Why is the macro VCPKG_CMAKE_SYSTEM_NAME is empty when running portfile.cmake?
BTW: Why is the macro VCPKG_CMAKE_SYSTEM_NAME is empty when running portfile.cmake?
mmm... this is really strange, since it is the correct way to understand the system on which you are running... (as I was saying in the review)
@cenit Yeah, I prefer to use VCPKG_CMAKE_SYSTEM_NAME to distinguish between different platforms.
Sometimes it works, sometimes it's empty.
when it's empty you are on Windows desktop. It just depends on your triplet :)
@cenit Clapack did not generate config.cmake file. So if I modify CMakeLists.txt and add find_package(clapack CONFIG REQUIRED) then port clapack will not be imported correctly.
And I found... we can just add clapack dependencies to solve this problem.
@cenit Clapack did not generate config.cmake file. So if I modify CMakeLists.txt and add find_package(clapack CONFIG REQUIRED) then port clapack will not be imported correctly.
And I found... we can just add clapack dependencies to solve this problem.
that's a problem I am trying to solve in #6371
@cenit In fact, if there is no port-config.cmake file, we can use find_library to solve the problem of finding the debug/release library path and use target_link_libraries to use the dependency library.
That’s exactly what I did in that PR :)
This issue has been fixed in #6371.
|
2025-04-01T04:34:43.652028
| 2020-01-16T16:21:56
|
550914107
|
{
"authors": [
"NancyLi1013",
"et-nik",
"strega-nil"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8574",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/9717"
}
|
gharchive/pull-request
|
[restclient-cpp] Fix portfile and update version.
This PR to update restclient library and fix portfile. Previously, the portfile had a command to delete the all compiled files (restclient-cpp.lib, restclient-cppd.lib), it is mistake.
I update library version from 0.5.1 tag to last commit. CMakeLists patches are no longer required in the new library version.
Library is updated and bugfixes, but the developer did not add new tags. Some people want tag updating (https://github.com/mrtazz/restclient-cpp/issues/145).
@et-nik
Could you please address the review suggestion?
Hello. I'll update this PR today.
It seems that the fix is not correct. Please refer to this doc to try it again.
Done
Bumped version to last tag 0.5.2
Removed old patches
Fixed descriptions
@NancyLi1013 Done
Hm. I see that all checks are succeeded https://dev.azure.com/vcpkg/public/_build/results?buildId=36451&view=results
But here check statuses are still "Waiting for..."
Cool, looks good to me! Thanks @et-nik :)
|
2025-04-01T04:34:43.654370
| 2020-09-10T19:10:48
|
698382385
|
{
"authors": [
"montgomp"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8575",
"repo": "microsoft/vscode-azure-iot-tools",
"url": "https://github.com/microsoft/vscode-azure-iot-tools/pull/32"
}
|
gharchive/pull-request
|
Address security vulnerabilities and addition to .gitignore
Address security vulnerabilities and addition to .gitignore
Changes included in PR #37
Changes included in PR #37
|
2025-04-01T04:34:43.657758
| 2022-12-21T13:01:39
|
1506264550
|
{
"authors": [
"nturinski",
"v-ruizh"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8576",
"repo": "microsoft/vscode-azurefunctions",
"url": "https://github.com/microsoft/vscode-azurefunctions/issues/3487"
}
|
gharchive/issue
|
[GitHub Codespaces] Fail to create a C# project
Environment: Local Codespaces
Azure Function Core Tools: v4
Build Version: 20221220.13
Repro Steps:
Create a .NET 7 C# project.
Check whether succeeds to create a C# project.
Expect:
Succeed to create a C# project.
Actual:
Fail to create a C# project with an error.
More Info:
This issue does not reproduce in the non-codespaces environment.
Does this work for .NET 6 projects?
|
2025-04-01T04:34:43.658755
| 2022-08-25T17:45:41
|
1351246540
|
{
"authors": [
"motm32"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8577",
"repo": "microsoft/vscode-azurestorage",
"url": "https://github.com/microsoft/vscode-azurestorage/pull/1130"
}
|
gharchive/pull-request
|
Added error message when creating queue/tables with existing name
Fixes #1015
Ignore the directoryUtils and uploadUtils. Accidently added previous commit to this branch will update that in next commit .
|
2025-04-01T04:34:43.667240
| 2021-05-03T07:55:53
|
874330566
|
{
"authors": [
"WardenGnaw",
"andreeis",
"seppeon"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8578",
"repo": "microsoft/vscode-cmake-tools",
"url": "https://github.com/microsoft/vscode-cmake-tools/issues/1827"
}
|
gharchive/issue
|
launch.json selects the incorrect debugger executable.
Brief Issue Summary
On my computer I have many different GCC installations, I have many LLVM installations etc...
When using the launch.json example here, the incorrect dbgExe is selected.
Expected:
Expected behaviour, Cmake Tools select the correct debugger, the same one used if launched using the CMake Tools dedicated debug button.
Apparent Behavior:
The resulting error is this:
However the compiler is this:
[cmake] -- Detecting C compiler ABI info
[cmake] -- Detecting C compiler ABI info - done
[cmake] -- Check for working C compiler: C:/utils/bin/mingw64/bin/clang.exe - skipped
[cmake] -- Detecting C compile features
[cmake] -- Detecting C compile features - done
[cmake] -- Detecting CXX compiler ABI info
[cmake] -- Detecting CXX compiler ABI info - done
[cmake] -- Check for working CXX compiler: C:/utils/bin/mingw64/bin/clang++.exe - skipped
Platform and Versions
Operating System: Windows
CMake Version: cmake version 3.19.0-rc3
VSCode Version: 1.55.2
CMake Tools Extension Version: 1.7.7
Compiler/Toolchain: Clang 11.1.0
Other Notes/Information
I use clang from winlibs:
http://www.winlibs.com/
My exact configuration in launch.json:
{
"name": "Launch",
"type": "cppdbg",
"request": "launch",
"program": "${command:cmake.launchTargetPath}",
"args": [],
"stopAtEntry": true,
"cwd": "${workspaceFolder}",
"environment": [
{
"name": "PATH",
"value": "$PATH:${command:cmake.getLaunchTargetDirectory}"
}
],
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
}
Thank you for opening this report. If you run debug from the CMake Tools debug button, you're saying that the debugging works (no error), but does it pick the same executable as I see in the error screenshot? Do you have any setting under "cmake.debugConfig"?
Also, the path syntax you are using in your launch.json environment block is wrong for windows. Use ${env.PATH} (and also see if the error occurs still).
Nope, it does the same thing with:
Nothing in settings.json, cmake.debugConfig (I had "externalConsole":false)
The path "environment" section of the launch file removed entirely.
@WardenGnaw, do you have any ideas what could happen here?
MIEngine determines which debugger to choose based off of the PATH environment variable if miDebuggerPath is not specified.
If you open a cmd prompt and run echo %PATH%, is C:/utils/bin/mingw32/bin/ before C:\Strawberry\c\bin\?
The cmake debug button is different from the regular launch and may be adding C:/utils/bin/mingw32/bin/ for the compilers.
But if you have a specific debugger to use, please specify miDebuggerPath in the launch.json.
|
2025-04-01T04:34:43.670239
| 2023-05-17T20:43:33
|
1714628953
|
{
"authors": [
"REDl3east",
"benmcmorran"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8579",
"repo": "microsoft/vscode-cmake-tools",
"url": "https://github.com/microsoft/vscode-cmake-tools/issues/3182"
}
|
gharchive/issue
|
Add language selection support to Quick Start.
Brief Issue Summary
I love using this tool for C++ and I always use the Quick Start command to quickly create a new project. I also enjoy writing programs in C, which becomes a problem with the Quick Start command. Whenever I start a new C project I will run the Quick Start as normal and then go in and change the filenames to .c files and update the files to represent the C language, e.q. use printf instead of cout. I would love for there to be an option to select either C or C++ language, similarly as selecting Executable or Library.
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response
Thanks for the feedback! I'm marking this as a feature request and will take a look at the PR you've opened.
Shipped in 1.15.31.
|
2025-04-01T04:34:43.690091
| 2022-05-14T15:31:18
|
1236030913
|
{
"authors": [
"Zingam",
"bobbrow",
"chausner",
"mpusz",
"prince-chrismc"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8580",
"repo": "microsoft/vscode-cmake-tools",
"url": "https://github.com/microsoft/vscode-cmake-tools/pull/2544"
}
|
gharchive/pull-request
|
Implement support for v4 presets files
This change addresses items #2492 and #2469
The primary addition is support for version 4 presets files.
The following changes are proposed:
A JSON schema for version 4 is added.
I noticed that the official schema that Kitware publishes is in a somewhat different format than what is included in this extension. The official one makes more use of $refs while the one in the extension only uses $refs sparingly and also includes additional schema information for vendor-specific attributes.
In order to update the schema to v4, I started with the v3 one in the extension and diffed it with the official v4 one.
Support for the ${fileDir} macro which is new in v4 is added.
Logic is added to support includes in preset files.
The implementation approach I've chosen is to recursively parse any included presets files and merge them into a single instance of preset.PresetsFile. It seemed the easiest way that requires little changes in other places but I would be happy to hear if there is a better way.
Correct implementation of ${fileDir} and include requires that preset.Preset tracks the file where the preset was originally defined ($fileDir should resolve to the directory of the include where that macro is used, not the root preset file. It is different, however, if a preset inherits from a preset in an included file: in this case, $fileDir should resolve to the directory of the presets file that inherits). For this purpose, I added some helper fields preset.PresetsFile.__path and preset.Preset.__file.
The file watcher logic is extended to also watch for any changes to included presets files.
A fix for #2469. The fix makes use of the helper field preset.Preset.__file which allows to query the version of the presets file where a preset is defined.
@bobbrow I would like to do more testing before declaring this PR ready to be reviewed but maybe you or somebody else would like to have an early look and let me know if the approach looks fine to you so far.
#2492 mentions resolvePackageReferences which is new in v4. I don't think anything needs to be added in the extension for this (apart from the schema addition). Can somebody confirm?
There is a V5 now.
There is a V5 now.
Yes, we know that's coming in 3.24. We're trying to release 1.11 and had some delays with the cpptools v6 integration PR. We'll work on getting this v4 PR in shortly after for 1.12 pre-release. Then we can do v5 after that. v5 doesn't look like it has too much in it so far (a test truncation property and path separator variable)
And it would be great if you could add some tests for the new includes feature somewhere.
I had a brief look into the tests folder but only found tests for some parsing functions but none for the overall preset functionality: test/unit-tests/presets.test.ts.
I had a brief look into the tests folder but only found tests for some parsing functions but none for the overall preset functionality: test/unit-tests/presets.test.ts.
I believe we have more coverage in the test/extension-tests/single-root-UI folder for presets, but I forget how good it is. If it's easy enough to add some basic coverage for the includes, we would appreciate it. Otherwise, we can investigate adding some more afterward.
I believe we have more coverage in the test/extension-tests/single-root-UI folder for presets, but I forget how good it is. If it's easy enough to add some basic coverage for the includes, we would appreciate it. Otherwise, we can investigate adding some more afterward.
Thanks. I added a basic test for now in 8586780cb65d9da56bfa550543b7f2065e6221d6. I haven't been able to test it locally, though, because running npm run extensionTestsSingleRoot shows all tests failing and there are warnings:
[vscode-cpptools-api] C/C++ extension is not installed
Do I need to run anything else before? I do have the C/C++ extension installed.
I tried running the test multiple times and am unable to reproduce the error on linux locally. If you rename include-presets.test.ts to include-presets.ts that should disable the test and we can open a new issue to ensure we add tests for it (though I think the existing tests will actually get some coverage of it since the CMakeUserPresets.json was changed.
I'm trying one last idea to exclude that generated file from the test build. If that doesn't work, let's disable the test for now.
Thank you so much for your help with this!
I was having issues and eventually I discovered this PR... I download Version: 1.12.0-1ca9c49 (from main's action results) and the v4 presets information I need instantly started working 💟
Thanks for all you hard work!
@prince-chrismc Every morning we publish a build to the VS Code Marketplace if anything was submitted to main the day before. From the extensions panel, you can right click on the CMake Tools item and select "Switch to Pre-Release Version". This feature is available starting in version 1.12.3.
Thanks for the tip!
I just tested the new feature. It mostly works great!
The only problem I noticed is that the Build Presets are not refreshed when the included file is changed/appended with new configurations.
For example:
I generated a Release configuration with Conan
Loaded CMakeUserPresets.json in VSCode
Realized that the Debug is missing so I generated it with Conan which added a proper configuration to the previously included CMakePresets.json file
I needed to restart the CMake Tools extension state to see the update of presets.
In theory, it should detect the file change and I think I tested the scenario with Conan but let me check again and see if I can reproduce it.
From: Mateusz Pusz @.>
Sent: Friday, June 24, 2022 8:47:15 AM
To: microsoft/vscode-cmake-tools @.>
Cc: chausner @.>; Author @.>
Subject: Re: [microsoft/vscode-cmake-tools] Implement support for v4 presets files (PR #2544)
I just tested the new feature. It mostly works great!
The only problem I noticed is that the Build Presets are not refreshed when the included file is changed/appended with new configurations.
For example:
I generated a Release configuration with Conan
Loaded CMakeUserPresets.json in VSCode
Realized that the Debug is missing so I generated it with Conan which added a proper configuration to the previously included CMakePresets.json file
I needed to restart the CMake Tools extension state to see the update of presets.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode-cmake-tools/pull/2544#issuecomment-1165257516, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADT2GDPGO7ZYDAPWQ7GRM2TVQVKXHANCNFSM5V5W2IEA.
You are receiving this because you authored the thread.Message ID: @.***>
@mpusz I was able to reproduce the issue and found the problem. I submitted a fix here: https://github.com/microsoft/vscode-cmake-tools/pull/2619.
Thanks again for reporting the problem.
|
2025-04-01T04:34:43.694367
| 2023-06-30T15:28:25
|
1782729476
|
{
"authors": [
"bobbrow",
"gcampbell-msft"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8581",
"repo": "microsoft/vscode-cmake-tools",
"url": "https://github.com/microsoft/vscode-cmake-tools/pull/3225"
}
|
gharchive/pull-request
|
attempt specific permissions
This change addresses item #[[put issue number here to generate a link]]
This changes [[visible behavior/performance/documentation/etc.]]
The following changes are proposed:
The purpose of this change
Other Notes/Information
I ran the Action/bot manually with this branch and it still failed. https://github.com/microsoft/vscode-cmake-tools/actions/runs/5447019987/jobs/9908535054
I ran the Action/bot manually with this branch and it still failed. https://github.com/microsoft/vscode-cmake-tools/actions/runs/5447019987/jobs/9908535054
I also tried this and failed. I got another response on the ticket and they suggested trying to update from node12 to node16, but I'm still noticing a failure. I'm wondering if we need to update our dependencies on the @actions npm packages?
|
2025-04-01T04:34:43.710961
| 2024-01-29T03:55:07
|
2104588855
|
{
"authors": [
"aiday-mar",
"akrherz",
"lramos15",
"sailxjx"
],
"license": "CC-BY-4.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8582",
"repo": "microsoft/vscode-copilot-release",
"url": "https://github.com/microsoft/vscode-copilot-release/issues/802"
}
|
gharchive/issue
|
Chat no longer quotes my code.
VS Code Version: Version: 1.86.0-insider
OS Version: MacOS
Logs:
[INFO] [streamChoices] [2024-01-29T03:50:03.399Z] solution 0 returned. finish reason: [stop]
[INFO] [streamChoices] [2024-01-29T03:50:03.400Z] request done: headerRequestId: [ab059369-1273-4b17-ac84-2f895df5649d] model deployment ID: [x878ecfd0739c]
[INFO] [ghostText] [2024-01-29T03:50:05.768Z] Cancelled during debounce
[INFO] [default] [2024-01-29T03:50:05.884Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex
[INFO] [default] [2024-01-29T03:50:06.307Z] request.response: [https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex/completions] took 422 ms
[INFO] [streamChoices] [2024-01-29T03:50:06.308Z] solution 0 returned. finish reason: [stop]
[INFO] [streamChoices] [2024-01-29T03:50:06.309Z] request done: headerRequestId: [b5e562d8-f9d0-4229-b0b1-08b099a2fb5b] model deployment ID: [x878ecfd0739c]
Steps to Reproduce:
Open copilot chat -> chat
As you see, copilot chat will reference my current editing code as the context, but after recent upgrades in these days, it will never do it, and became useless.
Hi @sailxjx thank you for filing the issue. In order to better assist you, it would help us if you could include a bigger screenshot or copy paste of the conversation you had with copilot. It would also help us if you include a longer copy paste of the log you see in the output view under the window copilot chat. As it stands, it is a bit difficult to pin point where the error occurs.
I think this is generally the issue that I am now seeing. I have been using copilot for many moons without this issue... Copilot has become about worthless as it no longer sees the code I am currently editing. I have to go back and forth with it attempting to figure what code I am referencing. I highlight things in the editor, still doesn't see it. I try again, it maybe sees it. I ask a question about the entire file I am editing, this is the now common interaction
@sailxjx We're experimenting with a more explicit selection based model. Does it reference it when you select the code?
I have switched from insider to stable verison of vscode, and the problem seems gone.
This problem occurs in stable version, the stable version is now unavailable as well.
版本: 1.86.1 (Universal)
提交: 31c37ee8f63491495ac49e43b8544550fbae4533
日期: 2024-02-07T09:09:01.236Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.1.0
how to set #editor as the default context as the previous setting versions?
|
2025-04-01T04:34:43.715255
| 2022-05-17T03:00:49
|
1237990343
|
{
"authors": [
"alexweininger",
"nturinski",
"v-xinda"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8583",
"repo": "microsoft/vscode-cosmosdb",
"url": "https://github.com/microsoft/vscode-cosmosdb/issues/2012"
}
|
gharchive/issue
|
An error occurs after expanding the resource group contains a database server
OS: Win10
Azure Database Build Version: 20220516.20
Resource Goup Build Version: 20220516.8
Repro Steps:
Create a database server.
Expand the resource group contains this database server.
Check whether no error occurs.
Expect:
No error occurs.
Actual:
An error occurs.
More Info:
This issue also reproduces when clicking "Click to view resource" in "ACTIVITYLOG" to focus the database server.
@nturinski was #2010 trying to fix this? The build they found this bug on was before that PR was merged.
@nturinski was #2010 trying to fix this? The build they found this bug on was before that PR was merged. I can't reproduce this myself on the latest builds.
Sorry for the late reply. Yeah, it was intended to fix this (and the create not working, I believe)
|
2025-04-01T04:34:43.780326
| 2020-08-05T13:24:27
|
673537316
|
{
"authors": [
"meganbradley",
"therealjohn"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8584",
"repo": "microsoft/vscode-docs-authoring",
"url": "https://github.com/microsoft/vscode-docs-authoring/issues/708"
}
|
gharchive/issue
|
Docs preview does not render zones
It's difficult to author docs that use zones because the preview feature does not show the UI as it would appear once published.
For example, consider this:
:::zone pivot="windows"
// some VS content
:::zone-end
:::zone pivot="win-vs2017"
// some 2017 content
:::zone-end
:::zone pivot="macos"
// some macOS content
:::zone-end
I'd expect the preview to render this at the top and it behave similarly to what shows up when published
AB#280461
This will be included in build-based local preview. ETA FY21 H2.
|
2025-04-01T04:34:43.801207
| 2023-03-14T19:35:18
|
1624171462
|
{
"authors": [
"captainbrosset",
"tjsplace2023"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8585",
"repo": "microsoft/vscode-edge-devtools",
"url": "https://github.com/microsoft/vscode-edge-devtools/issues/1406"
}
|
gharchive/issue
|
READ.ME
Is your feature request related to a problem? Please describe.
Describe the solution you'd like:
Describe alternatives you've considered:
Additional context:
Closing as incomplete.
Thank you
|
2025-04-01T04:34:43.825290
| 2020-12-10T20:21:48
|
761583246
|
{
"authors": [
"DavidKutu",
"joyceerhl"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8586",
"repo": "microsoft/vscode-jupyter",
"url": "https://github.com/microsoft/vscode-jupyter/issues/4206"
}
|
gharchive/issue
|
Gather: External buttons not appearing when using 'Create New Blank Jupyter Notebook' command
Steps:
Open a folder in VS code (don't open files, the python, jupyter and gather extensions should not activate)
Use the 'Create New Blank Jupyter Notebook' command
(If you open a python file, the button appears)
Actual Result:
The external buttons don't appear
Expected Result:
External buttons appear
This doesn't happen if the extensions were already activated.
Validated
Validated
|
2025-04-01T04:34:43.830523
| 2021-05-24T21:19:45
|
900022845
|
{
"authors": [
"IanMatthewHuff"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8587",
"repo": "microsoft/vscode-jupyter",
"url": "https://github.com/microsoft/vscode-jupyter/pull/5972"
}
|
gharchive/pull-request
|
Put ipywidget renderer back into build
For #5952
[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] Has a news entry file (remember to thank yourself!).
[x] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
Basically this review that I pushed over the weekend is required reading here.
https://github.com/microsoft/vscode-jupyter/pull/5964/files
I did a hack to build the renderer in its own project and download it to make sure that we wouldn't be broken. This change here adds the side renderer project back into jupyter extension, and deletes then download hack. Then that PR also has the matching extension side changes for handling the new API with outputId and cellInfo.
Basic widgets working:
Funny, looks like the windows smoke test failed on npm ci. Going to close and re-run.
|
2025-04-01T04:34:43.839942
| 2022-04-07T02:15:15
|
1195423219
|
{
"authors": [
"DonJayamanne",
"codecov-commenter",
"rchiodo"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8588",
"repo": "microsoft/vscode-jupyter",
"url": "https://github.com/microsoft/vscode-jupyter/pull/9616"
}
|
gharchive/pull-request
|
Ensure disposeAllDisposables is non-node specific
Wanted to add some telemetry for https://github.com/microsoft/vscode-jupyter/issues/9615 to figure out how many are using the Kernel filter, and came across the fact that KernelFilter was node specifci & found this to be one of the reasons
Codecov Report
Merging #9616 (ab9135d) into main (cae0758) will increase coverage by 0%.
The diff coverage is 100%.
@@ Coverage Diff @@
## main #9616 +/- ##
====================================
Coverage 72% 72%
====================================
Files 193 194 +1
Lines 8451 8451
Branches 1238 1238
====================================
+ Hits 6136 6138 +2
+ Misses 1844 1843 -1
+ Partials 471 470 -1
Impacted Files
Coverage Δ
src/platform/common/helpers.node.ts
60% <ø> (-15%)
:arrow_down:
src/platform/api/kernelApi.node.ts
71% <100%> (ø)
...rc/platform/common/extensionRecommendation.node.ts
81% <100%> (ø)
src/platform/common/helpers.ts
100% <100%> (ø)
...c/platform/progress/kernelProgressReporter.node.ts
79% <100%> (ø)
src/platform/errors/errorHandler.node.ts
65% <0%> (+1%)
:arrow_up:
Merging this too, less merge conflicts later
|
2025-04-01T04:34:43.853974
| 2023-08-25T16:11:30
|
1867326677
|
{
"authors": [
"beccamc",
"dbaeumer"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8589",
"repo": "microsoft/vscode-languageserver-node",
"url": "https://github.com/microsoft/vscode-languageserver-node/issues/1305"
}
|
gharchive/issue
|
Content-Length property not parsed correctly
For some projects, we are seeing a fatal server shutdown.
This is because we have some responses from the server not being parsed correctly. Although Content-Length is present, the results have been parsed with "jsonrpc" as the key. Somewhere our results are getting corrupted and are not parsing correctly.
I've debugged and logged from the server. The content we are sending looks correct. Here are three calls that were incorrectly parsed on the client.
{"jsonrpc"" => ""2.0","id":277,"method":"workspace/inlayHint/refresh","params":[]}Content-Length: 76"}
{"jsonrpc"" => ""2.0","id":278,"method":"workspace/codeLens/refresh","params":[]}Content-Length: 78"}
{"jsonrpc"" => ""2.0","id":279,"method":"workspace/diagnostic/refresh","params":[]}Content-Length: 82"}
If you look at the MonitorStream.log, the information being passed from the Roslyn server look correct and are not corrupted.
{"jsonrpc":"2.0","method":"window/logMessage","params":{"type":4,"message":"[LanguageServerHost][07:24:25.094][Start]codeLens/resolve"}}Content-Length: 77
{"jsonrpc":"2.0","id":277,"method":"workspace/inlayHint/refresh","params":[]}Content-Length: 76
{"jsonrpc":"2.0","id":278,"method":"workspace/codeLens/refresh","params":[]}Content-Length: 78
{"jsonrpc":"2.0","id":279,"method":"workspace/diagnostic/refresh","params":[]}Content-Length: 82
Given that the results being sent from the server are parse-able and correct, it seems like something is getting corrupted on the client side? Here is the project that this repros consistently with: ReproNetCode.zip
I've found the problem, but I don't know what it means. In the middle of the buffer we have this logging inserted..
[Info]Begin Processing assembly Assembly-CSharp candidates
[Info]End Processing assembly Assembly-CSharp candidates
[Info]Timing:
Total: 719.7607 msec
OnVisitSyntaxNode: 0.6842 msec (150) [0.1479]
HasGhostComponentAttribute: 0.2518 msec (4) [0.001]
This is definitely what is messing up the parsing. I took a look at the messageBuffer tryReadHeaders parsing. Everything is going normally, and the method is producing Content-Length : x until it hits this:
Looking at the log of what is sent from the server, this addition isn't coming from the server. There are three calls in a row that match what the client is trying to parse. Length 1064, 139 and then 196.
{"jsonrpc":"2.0","method":"window/logMessage","params":{"type":4,"message":"[LanguageServerHost][04:14:36.761][Start]textDocument/semanticTokens/range"}}Content-Length: 1064
{"jsonrpc":"2.0","id":13,"result":[{"range":{"start":{"line":6,"character":17},"end":{"line":6,"character":22}},"data":{"SyntaxVersion":"2023-08-28T16:14:36.3575048Z-10020-0","ListIndex":0,"TextDocument":{"uri":"file:///c:/Users/beccam/Downloads/ReproNetCode/ReproNetCode/Assets/Truc.cs"}}},{"range":{"start":{"line":12,"character":13},"end":{"line":12,"character":17}},"data":{"SyntaxVersion":"2023-08-28T16:14:36.3575048Z-10020-0","ListIndex":1,"TextDocument":{"uri":"file:///c:/Users/beccam/Downloads/ReproNetCode/ReproNetCode/Assets/Truc.cs"}}},{"range":{"start":{"line":15,"character":9},"end":{"line":15,"character":14}},"data":{"SyntaxVersion":"2023-08-28T16:14:36.3575048Z-10020-0","ListIndex":2,"TextDocument":{"uri":"file:///c:/Users/beccam/Downloads/ReproNetCode/ReproNetCode/Assets/Truc.cs"}}},{"range":{"start":{"line":21,"character":9},"end":{"line":21,"character":15}},"data":{"SyntaxVersion":"2023-08-28T16:14:36.3575048Z-10020-0","ListIndex":3,"TextDocument":{"uri":"file:///c:/Users/beccam/Downloads/ReproNetCode/ReproNetCode/Assets/Truc.cs"}}}]}Content-Length: 139
{"jsonrpc":"2.0","method":"window/logMessage","params":{"type":4,"message":"[LanguageServerHost][04:14:36.766][End]textDocument/codeLens"}}Content-Length: 196
This bug was originally reported with Unity projects. Poking around online it does look like this logging may be related?
Here is what I guess is happening:
the extension uses stdio to talk to the server
inside the server process there is a library or some other code that write to stdio which then messes up the whole communication.
You have two choices:
somehow redirect stdio to the connection inside the server process if this is possible inside C#.
or the better solution is to use pipes / file sockets to communicate with the server then you have your own dedicated communication channel. The VS Code LSP client support this with the --pipe options https://github.com/microsoft/vscode-languageserver-node/blob/a2954d24a550ea567df3d60d1c8eb86d39707149/client/src/node/main.ts#L347
I've resolved this issue by creating the dedicated communication channel. Closing - thanks!
|
2025-04-01T04:34:43.860897
| 2021-04-29T16:41:44
|
871230882
|
{
"authors": [
"DonJayamanne",
"joyceerhl"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8590",
"repo": "microsoft/vscode-notebook-renderers",
"url": "https://github.com/microsoft/vscode-notebook-renderers/issues/40"
}
|
gharchive/issue
|
Update vega transforms and support vegalite4
Port https://github.com/microsoft/vscode-jupyter/pull/5312/files
Already Done
|
2025-04-01T04:34:43.862672
| 2024-07-21T22:55:42
|
2421635069
|
{
"authors": [
"TylerLeonhardt",
"alexr00",
"chenqiongqiong"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8591",
"repo": "microsoft/vscode-pull-request-github",
"url": "https://github.com/microsoft/vscode-pull-request-github/issues/6099"
}
|
gharchive/issue
|
translation in zh-cn is wrong
'斗士' should be '都是'
I cannot find the source code of i18n
@TylerLeonhardt, how can I report a possibly incorrect translation?
We are now tracking this internally and will work with our Localization team to address this
Looks like the internal issue has been resolved.
|
2025-04-01T04:34:43.869078
| 2020-02-21T00:02:55
|
568655145
|
{
"authors": [
"DonJayamanne",
"damienrj"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8592",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/10238"
}
|
gharchive/issue
|
Can't use http proxy with interactive window
VS Code version: Code 1.42.1 (c47d83b293181d9be64f27ff093689e8e7aed054, 2020-02-11T14:44:27.652Z)
OS version: Darwin x64 19.3.0
Steps to Reproduce:
Attach to container
Install Python Extension
Try to connect to service behind proxy (sent as environment variable)
I understand that
Local proxy settings are not reused inside the container, which can prevent extensions from working unless the appropriate proxy information is configured (for example global HTTP_PROXY or HTTPS_PROXY environment variables with the appropriate proxy information)
So I set the proxies in /etc/profile.d in the containers, and this works for ipython but not the interactive python. Is there a way to configure the proxy for interactive python in a container?
Thanks for reporting this issue.
Is not supported in containers, is there a way to configure the proxy
To my knowledge this is the first time we've come across this issue.
Try to connect to service behind proxy (sent as environment variable)
Does this work with regular python, when run from the terminal?
Please could you create a file in your workspace with the name .env and add the necessary environment variables into that. Reload VS Code and try again.
Sure, I will try that. (I also added more info to the original post).
I tried adding an .env file in the container I am working in with (with the attach visual studio code option)
http_proxy=http...
HTTPS_PROXY=...
and triggered a reload.
From a notebook
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 159, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw)
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 80, in create_connection
raise err
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 70, in create_connection
sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out
The same command works from python and ipython in the integrated terminal running in the container.
Inside the notebook
import os
os.environ
doesn't show the proxies set, while they are set in ipython and python.
Setting the environment variables in the notebook seem to work, but ideally would like to do set it every time.
os.environ['http_proxy']=...
Any updates on this?
|
2025-04-01T04:34:43.941132
| 2020-04-13T15:11:02
|
598945012
|
{
"authors": [
"DavidKutu",
"DonJayamanne",
"rchiodo",
"u8sand"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8593",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/11124"
}
|
gharchive/issue
|
python.datascience.execSelectionInteractive is very slow compared to python.datascience.runcurrentcell
Bug: python.datascience.execSelectionInteractive is very slow compared to python.datascience.runcurrentcell
Steps to cause the bug to occur
Assign python.datascience.execSelectionInteractive to unique keybinding without when expression to rule out keybinding slowness
Assign python.datascience.runcurrentcell to keybinding
Compare the response time of two different actions on single line
Actual behavior
python.datascience.execSelectionInteractive is observably quite slow, especially compared to python.datascience.runcurrentcell which is instant.
Expected behavior
python.datascience.execSelectionInteractive should take the same amount of time as python.datascience.runcurrentcell
^ In this screenshot I pressed
python.datascience.execSelectionInteractive
python.datascience.runcurrentcell
python.datascience.execSelectionInteractive
python.datascience.runcurrentcell
Much more logs are displayed when pressing python.datascience.execSelectionInteractive
Your Jupyter and/or Python environment
Jupyter server running: Local
Extension version: 2020.3.71659
VS Code version: 1.43.2
Setting python.jediEnabled: false
Python and/or Anaconda version: 3.8.2
OS: Archlinux
Virtual environment: venv
Developer Tools Console Output
Full output:
console.log
My guess
It seems like python.datascience.execSelectionInteractive is trying to find interpreters every time it runs while python.datascience.runcurrentcell does not. It also seems like finding interpreters is slow, this would explain why starting up my notebook can be pretty slow; but I don't mind that as long as it runs well..
I prefer python.datascience.execSelectionInteractive so it'd be nice if it wasn't slow :(
Thank you for the awesome extension regardless.
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer
Hi @u8sand. Thank you for your feedback, it is very well researched.
execSelectionInteractive does indeed end up looking for all the interpreters. We'll discuss this issue in our next triage.
t seems like python.datascience.execSelectionInteractive is trying to find interpreters every time it runs while python.datascience.runcurrentcell does no
The interpreters listed here are cached, hence there is no searching taking place here.
I tried to isolate the parts of the logging for each by labeling them in the console prior to activating each command:
'python.datascience.execSelectionInteractive'
"python.datascience.execSelectionInteractive"
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:27: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:27: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: []
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:27: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/home/u8sand/Programs/cognition/ml/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/cognition/ml/conda-env","fileHash":"2741a377c5c304a13ed3c8b0f4ac7b310b49b02a6d1a9ad1066e59bd17e0ae9ac4b4e100fd3642f2c630b835a243a7bf11bceaa4d9c11ca97f52a2a6228d0bd1","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/cognition/ml/conda-env","envName":"conda-env"},{"architecture":3,"path":"/home/u8sand/Programs/gene-tfidf/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/gene-tfidf/conda-env","fileHash":"7e215e8d0271e03ad45dfaa9b3ba777cccf53b34e5ab72f9cba54d94ac71cc94657427d087de7d326f235aba5ff322e65f1874e413c93ba64f8fc80b563fe8fc","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/gene-tfidf/conda-env","envName":"conda-env"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:27: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: []
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:27: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: []
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:27: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: []
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:27: Get Interpreters in CacheableLocatorService, Class name = m, completed in 2ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/usr/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:27: Get Interpreters in CacheableLocatorService, Class name = m, completed in 3ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/usr/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:27: Get Interpreters, Class name = m, completed in 4ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/home/u8sand/Programs/cognition/ml/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/cognition/ml/conda-env","fileHash":"2741a377c5c304a13ed3c8b0f4ac7b310b49b02a6d1a9ad1066e59bd17e0ae9ac4b4e100fd3642f2c630b835a243a7bf11bceaa4d9c11ca97f52a2a6228d0bd1","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/cognition/ml/conda-env","envName":"conda-env"},{"architecture":3,"path":"/home/u8sand/Programs/gene-tfidf/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/gene-tfidf/conda-env","fileHash":"7e215e8d0271e03ad45dfaa9b3ba777cccf53b34e5ab72f9cba54d94ac71cc94657427d087de7d326f235aba5ff322e65f1874e413c93ba64f8fc80b563fe8fc","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/gene-tfidf/conda-env","envName":"conda-env"},{"architecture":3,"path":"/usr/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: > ~/Programs/jsonld-alchemy/venv/bin/python3 ~/.vscode/extensions/ms-python.python-2020.3.71659/pythonFiles/normalizeForInterpreter.py 'python.datascience.execSelectionInteractive'
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Loading web panel. Panel is set
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Wait for sys info for 2b497c39-db1d-4a7f-b5a1-3db45fb4febe 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Submitting code for 2b497c39-db1d-4a7f-b5a1-3db45fb4febe
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Loading web panel. Panel is set
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Wait for sys info for 2b497c39-db1d-4a7f-b5a1-3db45fb4febe 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Wait for sys info for 2b497c39-db1d-4a7f-b5a1-3db45fb4febe 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Adding hash for 4 = f19d40e9a903 with 1 lines
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:28: Finished execution for cfe4b718-8faf-4ae2-afcb-9ed07dbc5549
webviewElement.ts:261 [Embedded Page] Posting message send_info to extension.
webviewElement.ts:261 [Embedded Page] Posting message update_model to extension.
'python.datascience.runcurrentcell'
"python.datascience.runcurrentcell"
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Loading web panel. Panel is set
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Wait for sys info for 2b497c39-db1d-4a7f-b5a1-3db45fb4febe 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Submitting code for 2b497c39-db1d-4a7f-b5a1-3db45fb4febe
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Loading web panel. Panel is set
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Wait for sys info for 2b497c39-db1d-4a7f-b5a1-3db45fb4febe 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Wait for sys info for 2b497c39-db1d-4a7f-b5a1-3db45fb4febe 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Adding hash for 5 = ff938437a86e with 1 lines
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 16:36:36: Finished execution for e97f745c-9d12-42be-9d26-685701e88cfc
webviewElement.ts:261 [Embedded Page] Posting message send_info to extension.
webviewElement.ts:261 [Embedded Page] Posting message update_model to extension.
the timestamps suggest that the 'cache' may in fact be occurring more slowly than it is being reported.
Not sure what you mean here. It is returned immediatley.
Looking at the time stamps there's a delay of 8 seconds in loading the notebook.
You might want to try this after running the first cell.
@DonJayamanne Sorry for the confusion -- this is actually just 8 seconds between the two things I ran. I did in-fact wait for things to settle down -- the first command just does more things.
[Extension Host] Info Python Extension: 2020-04-16 18:19:06: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:19:06: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:19:06: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:19:06: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:19:06: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:19:06: Adding hash for 1 = 9b7a970b3e22 with 1 lines
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:19:06: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:19:06: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:19:06: Finished execution for 113c74b3-2d0a-4100-acf5-c38927b1d0d7
webviewElement.ts:261 [Embedded Page] Posting message send_info to extension.
webviewElement.ts:261 [Embedded Page] Posting message update_model to extension.
console.ts:137 [Extension Host] Kernel: connected (0753552a-de4f-4472-87ee-d6c8cc9e59c0)
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:19:06: Finished waiting for idle on (kernel): 0753552a-de4f-4472-87ee-d6c8cc9e59c0 -> idle
'init'
"init"
Here I type in console and then i trigger the execSelectionInteractive
'python.datascience.execSelectionInteractive'
"python.datascience.execSelectionInteractive"
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:01: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:01: Get Interpreters in CacheableLocatorService, Class name = m, completed in 0ms, has a truthy return value, Arg 1: undefined, Return Value: []
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:01: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/home/u8sand/Programs/cognition/ml/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/cognition/ml/conda-env","fileHash":"2741a377c5c304a13ed3c8b0f4ac7b310b49b02a6d1a9ad1066e59bd17e0ae9ac4b4e100fd3642f2c630b835a243a7bf11bceaa4d9c11ca97f52a2a6228d0bd1","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/cognition/ml/conda-env","envName":"conda-env"},{"architecture":3,"path":"/home/u8sand/Programs/gene-tfidf/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/gene-tfidf/conda-env","fileHash":"7e215e8d0271e03ad45dfaa9b3ba777cccf53b34e5ab72f9cba54d94ac71cc94657427d087de7d326f235aba5ff322e65f1874e413c93ba64f8fc80b563fe8fc","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/gene-tfidf/conda-env","envName":"conda-env"}]
3console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:01: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: []
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:01: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/usr/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:01: Get Interpreters in CacheableLocatorService, Class name = m, completed in 2ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/usr/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:01: Get Interpreters, Class name = m, completed in 2ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/home/u8sand/Programs/cognition/ml/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/cognition/ml/conda-env","fileHash":"2741a377c5c304a13ed3c8b0f4ac7b310b49b02a6d1a9ad1066e59bd17e0ae9ac4b4e100fd3642f2c630b835a243a7bf11bceaa4d9c11ca97f52a2a6228d0bd1","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/cognition/ml/conda-env","envName":"conda-env"},{"architecture":3,"path":"/home/u8sand/Programs/gene-tfidf/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/gene-tfidf/conda-env","fileHash":"7e215e8d0271e03ad45dfaa9b3ba777cccf53b34e5ab72f9cba54d94ac71cc94657427d087de7d326f235aba5ff322e65f1874e413c93ba64f8fc80b563fe8fc","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/gene-tfidf/conda-env","envName":"conda-env"},{"architecture":3,"path":"/usr/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: > ~/Programs/jsonld-alchemy/venv/bin/python3 ~/.vscode/extensions/ms-python.python-2020.3.71659/pythonFiles/normalizeForInterpreter.py 1+1
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Loading web panel. Panel is set
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Wait for sys info for 26acbf7a-dcd3-49e5-a3f6-65f39963da3b 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Submitting code for 26acbf7a-dcd3-49e5-a3f6-65f39963da3b
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Loading web panel. Panel is set
2console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Wait for sys info for 26acbf7a-dcd3-49e5-a3f6-65f39963da3b 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Adding hash for 2 = 9b7a970b3e22 with 1 lines
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:21:02: Finished execution for 1575d0f1-fc14-4894-8e3e-8f35e68d9e36
webviewElement.ts:261 [Embedded Page] Posting message send_info to extension.
webviewElement.ts:261 [Embedded Page] Posting message update_model to extension.
Now I type the other name in the console and execute it
'python.datascience.runcurrentcell'
"python.datascience.runcurrentcell"
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Loading web panel. Panel is set
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Wait for sys info for 26acbf7a-dcd3-49e5-a3f6-65f39963da3b 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Submitting code for 26acbf7a-dcd3-49e5-a3f6-65f39963da3b
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Loading web panel. Panel is set
2console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Wait for sys info for 26acbf7a-dcd3-49e5-a3f6-65f39963da3b 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Adding hash for 3 = 9b7a970b3e22 with 1 lines
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:23:16: Finished execution for d2956706-d4fc-4ce4-bc1f-bcb7762c46d5
webviewElement.ts:261 [Embedded Page] Posting message send_info to extension.
webviewElement.ts:261 [Embedded Page] Posting message update_model to extension.
There is substantially less info in run current cell....
Here i can run the prior one again after and you get the same logs
'python.datascience.execSelectionInteractive'
"python.datascience.execSelectionInteractive"
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:34: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:34: Get Interpreters in CacheableLocatorService, Class name = m, completed in 0ms, has a truthy return value, Arg 1: undefined, Return Value: []
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:34: Get Interpreters in CacheableLocatorService, Class name = m, completed in 0ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/home/u8sand/Programs/cognition/ml/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/cognition/ml/conda-env","fileHash":"2741a377c5c304a13ed3c8b0f4ac7b310b49b02a6d1a9ad1066e59bd17e0ae9ac4b4e100fd3642f2c630b835a243a7bf11bceaa4d9c11ca97f52a2a6228d0bd1","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/cognition/ml/conda-env","envName":"conda-env"},{"architecture":3,"path":"/home/u8sand/Programs/gene-tfidf/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/gene-tfidf/conda-env","fileHash":"7e215e8d0271e03ad45dfaa9b3ba777cccf53b34e5ab72f9cba54d94ac71cc94657427d087de7d326f235aba5ff322e65f1874e413c93ba64f8fc80b563fe8fc","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/gene-tfidf/conda-env","envName":"conda-env"}]
3console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:34: Get Interpreters in CacheableLocatorService, Class name = m, completed in 0ms, has a truthy return value, Arg 1: undefined, Return Value: []
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:34: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/usr/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:34: Get Interpreters in CacheableLocatorService, Class name = m, completed in 1ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/usr/sbin/python3","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python2","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:34: Get Interpreters, Class name = m, completed in 3ms, has a truthy return value, Arg 1: undefined, Return Value: [{"architecture":3,"path":"/home/u8sand/Programs/cognition/ml/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/cognition/ml/conda-env","fileHash":"2741a377c5c304a13ed3c8b0f4ac7b310b49b02a6d1a9ad1066e59bd17e0ae9ac4b4e100fd3642f2c630b835a243a7bf11bceaa4d9c11ca97f52a2a6228d0bd1","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/cognition/ml/conda-env","envName":"conda-env"},{"architecture":3,"path":"/home/u8sand/Programs/gene-tfidf/conda-env/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.7.6-final","major":3,"minor":7,"patch":6,"prerelease":["final"],"build":[],"version":"3.7.6-final"},"sysPrefix":"/home/u8sand/Programs/gene-tfidf/conda-env","fileHash":"7e215e8d0271e03ad45dfaa9b3ba777cccf53b34e5ab72f9cba54d94ac71cc94657427d087de7d326f235aba5ff322e65f1874e413c93ba64f8fc80b563fe8fc","companyDisplayName":"Anaconda, Inc.","type":"Conda","envPath":"/home/u8sand/Programs/gene-tfidf/conda-env","envName":"conda-env"},{"architecture":3,"path":"/usr/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/sbin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/sbin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python2.7","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"2.7.17-final","major":2,"minor":7,"patch":17,"prerelease":["final"],"build":[],"version":"2.7.17-final"},"sysPrefix":"/usr","fileHash":"35052569e442b1a3d07e8e8d507ec159686974bdeb9c0fd4f1529e56c80cfa368896b3a95f456ba6380fb4d760f793c6f921c022031ff9c5482a95917627dd8c","type":"Unknown"},{"architecture":3,"path":"/usr/bin/python3.8","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.2-final","major":3,"minor":8,"patch":2,"prerelease":["final"],"build":[],"version":"3.8.2-final"},"sysPrefix":"/usr","fileHash":"7938061237b4703f75514dbb7b4b6db9472beafbbb409d3914e0d3d96ac6f8d64994bd1ba5f23ba3b654c942cad74c97e5a3e41f9e303cdda4fcc9f0d891aeb8","type":"Unknown"}]
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Cached data exists getEnvironmentVariables, <No Resource>
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: > ~/Programs/jsonld-alchemy/venv/bin/python3 ~/.vscode/extensions/ms-python.python-2020.3.71659/pythonFiles/normalizeForInterpreter.py 1+1
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Loading web panel. Panel is set
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Wait for sys info for 26acbf7a-dcd3-49e5-a3f6-65f39963da3b 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Submitting code for 26acbf7a-dcd3-49e5-a3f6-65f39963da3b
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Loading web panel. Panel is set
2console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Wait for sys info for 26acbf7a-dcd3-49e5-a3f6-65f39963da3b 0
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Kernel switching to busy
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Adding hash for 5 = 9b7a970b3e22 with 1 lines
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Kernel switching to busy
webviewElement.ts:261 [Embedded Page] Posting message send_info to extension.
webviewElement.ts:261 [Embedded Page] Posting message update_model to extension.
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:35: Kernel switching to idle
console.ts:137 [Extension Host] Info Python Extension: 2020-04-16 18:24:36: Finished execution for 376eb283-beb2-44b0-b4d1-2932f0fb41d9
Closing this as it doesn't seem to happen anymore. (Although not positive it happened for me before either).
Binding exec selection to CTRL+i and run current cell to CTRL+l and executing the same code over and over shows no difference in execution time (logged with %%time or by looking at the console log)
Execution time of the cell didn't change, UI responsiveness changed (see screenshot).
Checking now it was in-fact fixed--thanks! :+1:
|
2025-04-01T04:34:43.948989
| 2023-08-01T06:05:31
|
1830528128
|
{
"authors": [
"DonJayamanne",
"karrtikr"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8594",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/21721"
}
|
gharchive/issue
|
Version information is empty in Python Enviornments (API) upon clearing cache and reloading
Steps to repro
Install Jupyter extension
Open a notebook
Select a kernel => Select Another Kernel => Python Environments
Note how the version information for Python envs are displayed
Now clear the cache and reload VS Code using the Python command
After reloading repeat the previous steps and note how the version information is missing
This is missing because the Python extension API is not returning this version information.
If you were to reload VS Code then it appears.
Version information is gradually populated via the change events, is Jupyter now handling it that way as hinted here: https://github.com/microsoft/vscode-python/issues/21271#issuecomment-1570653995?
s Jupyter now handling it that way as hinted here
Yes we are.
If you create a 3rd party extension and try this \you will see that the version object is always undefined, until and unless you re-load VS Code the second time.
I.e. i have verieid the bug is in the new API.
I'm unable to reproduce this on Windows, here's what my simplistic extension does:
import * as vscode from 'vscode';
import { PythonExtension } from '@vscode/python-extension';
export async function activate(context: vscode.ExtensionContext) {
console.log('Congratulations, your extension "helloworld-sample" is now active!');
const pythonApi = await PythonExtension.api();
pythonApi.environments.onDidChangeEnvironments(e => {
const envVersions = pythonApi.environments.known.map(e => e.version);
console.log(e.env.id, JSON.stringify(envVersions), JSON.stringify(e.env.version));
});
}
I run Python: Clear cache and reload window command, none of the versions logged to console are empty. Can you give me a minimal sample which repros this?
The steps I provided is super simple
Damn, I too cannot repro this anymore.
It was very easy thats why I provided the simple steps earlier.
Closing this as I can no longer repro this.
If I run into this again, I'll let you know.
|
2025-04-01T04:34:43.961877
| 2021-03-22T19:08:11
|
838026470
|
{
"authors": [
"bschnurr",
"karthiknadig"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8595",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/pull/15747"
}
|
gharchive/pull-request
|
fix for first time rename and goToDef returning 'no result'
For https://github.com/microsoft/vscode-python/issues/15727
@bschnurr can you add a news item for this, under news\2 Fixes? Use 15727.md as the file name.
updated with call out to user who submitted a fix
|
2025-04-01T04:34:43.975577
| 2019-11-08T01:20:25
|
519603945
|
{
"authors": [
"DonJayamanne",
"codecov-io"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8596",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/pull/8457"
}
|
gharchive/pull-request
|
Skip checking dependencies in PRs to speed up PR CI
For #8840
Codecov Report
Merging #8457 into master will decrease coverage by 0.38%.
The diff coverage is n/a.
@@ Coverage Diff @@
## master #8457 +/- ##
==========================================
- Coverage 59.46% 59.08% -0.39%
==========================================
Files 509 509
Lines 23390 23390
Branches 3779 3774 -5
==========================================
- Hits 13909 13820 -89
- Misses 8575 8655 +80
- Partials 906 915 +9
Impacted Files
Coverage Δ
src/client/testing/serviceRegistry.ts
48.64% <0%> (-46.85%)
:arrow_down:
src/client/testing/codeLenses/main.ts
44.44% <0%> (-33.34%)
:arrow_down:
...t/datascience/jupyter/jupyterDataRateLimitError.ts
66.66% <0%> (-33.34%)
:arrow_down:
src/client/formatters/serviceRegistry.ts
75% <0%> (-25%)
:arrow_down:
...ience/jupyter/jupyterDebuggerRemoteNotSupported.ts
75% <0%> (-25%)
:arrow_down:
src/client/common/utils/platform.ts
64.7% <0%> (-23.53%)
:arrow_down:
...cience/jupyter/jupyterDebuggerNotInstalledError.ts
60% <0%> (-20%)
:arrow_down:
src/client/common/utils/icons.ts
83.33% <0%> (-16.67%)
:arrow_down:
src/client/api.ts
78.57% <0%> (-14.29%)
:arrow_down:
src/client/datascience/cellFactory.ts
57.69% <0%> (-12.83%)
:arrow_down:
... and 10 more
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 764106b...e64ed5f. Read the comment docs.
|
2025-04-01T04:34:44.013059
| 2024-04-12T16:22:17
|
2240486027
|
{
"authors": [
"connor4312",
"mattnotmitt"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8597",
"repo": "microsoft/vscode-test-cli",
"url": "https://github.com/microsoft/vscode-test-cli/issues/37"
}
|
gharchive/issue
|
Expose c8 excludeAfterRemap argument to coverage config
We have a project which runs tests using the CLI against a webpacked extension and the node_modules aren't correctly excluded from coverage stats even if it's done explicitly. Manually bodging vscode-test-cli to add excludeAfterRemap: true to the Report in coverage.mts allows it to be successfully excluded. Could we get this exposed as an option or set to true by default?
Thanks, we should have exclude logic that takes into account sourcemaps. However, I don't want to expose c8 internals directly since that's a bit of an implementation detail (and I might write a v8-to-vscode helper at some point that bypasses istanbul.)
|
2025-04-01T04:34:44.030308
| 2020-10-13T21:48:42
|
720884497
|
{
"authors": [
"TylerGubala",
"alexr00"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8598",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/108625"
}
|
gharchive/issue
|
Recursive vscode task.json inputs
TL;DR: Desire a documented way for commands intended to be run to generate inputs to themselves depend on inputs
As part of a separate discussion, the seemingly intentional exclusion of task inputs that can be generated by a shell command is very strange to me.
For instance, I cannot use workbench.terminal.run as the command parameter of an input with the type of command.
I am coping with this by installing Task Shell Input, a command by Augusto César Dias (thank you!)
What this allows me to do, is prompt for user input for example, when I want to control or filter which subversion tags are displayed in a user pick list.
When the user selects my SVN - Checkout Blender Precompiled Libs Trunk on Windows, I have to ask them which windows library they want, since Blender Foundation has split up the precompiled libraries based on Visual Studio version.
What isn't working is when the user wants to first select the tag to checkout, and then I want to prompt them with a list of available Windows versions.
Here is the relevant parts of my `task.json` file (click to expand)
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "SVN - Checkout Blender Precompiled Libs Tag",
"type": "process",
"command": "svn",
"linux": {
"args": [
"checkout",
"https://svn.blender.org/svnroot/bf-blender/tags/${input:BfSvnTag}/lib/linux_centos7_x86_64/"
]
},
"osx": {
"args": [
"checkout",
"https://svn.blender.org/svnroot/bf-blender/tags/${input:BfSvnTag}/lib/darwin/"
]
},
"windows": {
"args": [
"checkout",
"https://svn.blender.org/svnroot/bf-blender/tags/${input:BfSvnTag}/lib/${input:BfSvnTagNTPlatform}"
]
},
"options": {
"cwd": "${workspaceFolder}/Blender/lib"
},
"problemMatcher": []
}
],
"inputs": [
{
"id": "BfSvnTag",
"type": "command",
"command": "shellCommand.execute",
"args": {
"command": "svn ls https://svn.blender.org/svnroot/bf-blender/tags/"
}
},
{
"id": "BfSvnTagNTPlatform",
"type": "command",
"command": "shellCommand.execute",
"args": {
"command": "svn ls https://svn.blender.org/svnroot/bf-blender/tags/${input:BfSvnTag}/lib/ | findstr \"^win\""
}
}
]
}
Here is my complete `tasks.json`
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "Python - Publish to PyPI",
"type": "process",
"command": "${config:python.pythonPath}",
"args": [
"-m",
"twine",
"upload",
"${workspaceFolder}/dist/*"
],
"problemMatcher": []
},
{
"label": "Python - Publish to PyPI [TEST]",
"type": "process",
"command": "${config:python.pythonPath}",
"args": [
"-m",
"twine",
"upload",
"--repository",
"pypitest",
"${workspaceFolder}/dist/*"
],
"problemMatcher": []
},
{
"label": "Python - Upgrade pip",
"type": "process",
"command": "${config:python.pythonPath}",
"args": [
"-m",
"pip",
"install",
"-U",
"pip"
],
"problemMatcher": []
},
{
"label": "Python - Install Dependencies",
"type": "process",
"command": "${config:python.pythonPath}",
"args": [
"-m",
"pip",
"install",
"-r",
"${workspaceFolder}/requirements.txt"
],
"dependsOn": [
"Python - Upgrade pip"
],
"problemMatcher": []
},
{
"label": "Make Blender Source & Libs Folder",
"type": "shell",
"linux": {
"command": "mkdir -p ${workspaceFolder}/Blender/lib"
},
"osx": {
"command": "mkdir -p ${workspaceFolder}/Blender/lib"
},
"windows": {
"command": "mkdir -p ${workspaceFolder}/Blender/lib"
},
"problemMatcher": []
},
{
"label": "Make Build Folder",
"type": "shell",
"linux": {
"command": "mkdir -p ${workspaceFolder}/build/linux"
},
"osx": {
"command": "mkdir -p ${workspaceFolder}/build/osx"
},
"windows": {
"command": "mkdir -p ${workspaceFolder}/build/windows"
},
"problemMatcher": []
},
{
"label": "Make OptiX Folder",
"type": "shell",
"linux": {
"command": "mkdir -p ${workspaceFolder}/OptiX"
},
"osx": {
"command": "mkdir -p ${workspaceFolder}/OptiX"
},
"windows": {
"command": "mkdir -p ${workspaceFolder}/OptiX"
},
"problemMatcher": []
},
{
"label": "Browser - Get OptiX [Requires Registration]",
"type": "shell",
"linux": {
"command": "open https://developer.nvidia.com/designworks/optix/download"
},
"osx": {
"command": "open https://developer.nvidia.com/designworks/optix/download"
},
"windows": {
"command": "start https://developer.nvidia.com/designworks/optix/download"
},
"dependsOn": [
"Make OptiX Folder"
],
"problemMatcher": []
},
{
"label": "Git - Clone Blender Sources",
"type": "process",
"command": "git",
"args": [
"clone",
"git://git.blender.org/blender.git"
],
"options": {
"cwd": "${workspaceFolder}/Blender"
},
"dependsOn": [
"Make Blender Source & Libs Folder"
],
"problemMatcher": []
},
{
"label": "Git - Fetch Blender Commits",
"type": "process",
"command": "git",
"args": [
"fetch"
],
"options": {
"cwd": "${workspaceFolder}/Blender/blender"
},
"problemMatcher": []
},
{
"label": "Git - Pull Blender Commits",
"type": "process",
"command": "git",
"args": [
"pull"
],
"options": {
"cwd": "${workspaceFolder}/Blender/blender"
},
"problemMatcher": []
},
{
"label": "Git - Checkout Blender Tag",
"type": "process",
"command": "git",
"args": [
"checkout",
"tags/${input:BfGitTag}",
"-b",
"origin/master"
],
"options": {
"cwd": "${workspaceFolder}/Blender/blender"
},
"dependsOn": [
"Git - Fetch Blender Commits"
],
"problemMatcher": []
},
{
"label": "Git - Checkout Blender Master",
"type": "process",
"command": "git",
"args": [
"checkout",
"master"
],
"options": {
"cwd": "${workspaceFolder}/Blender/blender"
},
"dependsOn": [
"Git - Fetch Blender Commits"
],
"problemMatcher": []
},
{
"label": "Git - Switch To Blender Master [Checkout & Pull]",
"dependsOn": [
"Git - Checkout Blender Master",
"Git - Pull Blender Commits"
],
"dependsOrder": "sequence",
"problemMatcher": []
},
{
"label": "Update Blender Sources [Checks out master branch]",
"type": "shell",
"command": "./make update",
"options": {
"cwd": "${workspaceFolder}/Blender/blender"
},
"dependsOn": [
"Git - Checkout Blender Master"
],
"problemMatcher": []
},
{
"label": "SVN - Checkout Blender Precompiled Libs Trunk",
"type": "process",
"command": "svn",
"linux": {
"args": [
"checkout",
"https://svn.blender.org/svnroot/bf-blender/trunk/lib/linux_centos7_x86_64/"
]
},
"osx": {
"args": [
"checkout",
"https://svn.blender.org/svnroot/bf-blender/trunk/lib/darwin/"
]
},
"windows": {
"args": [
"checkout",
"https://svn.blender.org/svnroot/bf-blender/trunk/lib/${input:BfSvnTrunkNTPlatform}"
]
},
"options": {
"cwd": "${workspaceFolder}/Blender/lib"
},
"problemMatcher": []
},
{
"label": "SVN - Checkout Blender Precompiled Libs Tag",
"type": "process",
"command": "svn",
"linux": {
"args": [
"checkout",
"https://svn.blender.org/svnroot/bf-blender/tags/${input:BfSvnTag}/lib/linux_centos7_x86_64/"
]
},
"osx": {
"args": [
"checkout",
"https://svn.blender.org/svnroot/bf-blender/tags/${input:BfSvnTag}/lib/darwin/"
]
},
"windows": {
"args": [
"checkout",
"https://svn.blender.org/svnroot/bf-blender/tags/${input:BfSvnTag}/lib/${input:BfSvnTagNTPlatform}"
]
},
"options": {
"cwd": "${workspaceFolder}/Blender/lib"
},
"problemMatcher": []
},
{
"label": "Configure",
"type": "shell",
"linux": {
"command": "cmake ${workspaceFolder}/Blender/blender -DWITH_PYTHON_INSTALL=OFF -DWITH_PYTHON_MODULE=ON -DWITH_CYCLES_CUDA_BINARIES=ON -DWITH_CYCLES_DEVICE_OPTIX=ON -DOPTIX_ROOT_DIR=/NVIDIA-OptiX-SDK-7.1.0-linux64-x86_64",
"options": {
"cwd": "${workspaceFolder}/build/linux"
}
},
"osx": {
"command": "cmake ${workspaceFolder}/Blender/blender -DWITH_PYTHON_INSTALL=OFF -DWITH_PYTHON_MODULE=ON",
"options": {
"cwd": "${workspaceFolder}/build/osx"
}
},
"windows": {
"command": "cmake ${workspaceFolder}/Blender/blender -DWITH_PYTHON_INSTALL=OFF -DWITH_PYTHON_MODULE=ON -DWITH_CYCLES_CUDA_BINARIES=ON -DWITH_CYCLES_DEVICE_OPTIX=ON -DOPTIX_ROOT_DIR=/NVIDIA-OptiX-SDK-7.1.0-linux64-x86_64",
"options": {
"cwd": "${workspaceFolder}/build/windows"
}
},
"problemMatcher": []
},
{
"label": "Build",
"type": "shell",
"linux": {
"command": "./make install",
"options": {
"cwd": "${workspaceFolder}/build/linux"
}
},
"osx": {
"command": "./make install",
"options": {
"cwd": "${workspaceFolder}/build/osx"
}
},
"windows": {
"command": "./make install",
"options": {
"cwd": "${workspaceFolder}/build/windows"
}
},
"problemMatcher": [],
"group": {
"kind": "build",
"isDefault": true
}
},
{
"label": "Docker - Full Clean",
"type": "process",
"command": "docker",
"args": [
"system",
"prune",
"--all",
"--force",
"--volumes"
],
"problemMatcher": []
},
{
"label": "Docker - Create Manylinux Wheel Build Environment",
"type": "process",
"command": "docker",
"args": [
"build",
"--target",
"blenderpy-manylinux-wheel-builder",
"-t",
"blenderpy/manylinux-wheel-builder",
"-f",
"${workspaceFolder}/.containers/Dockerfile",
"."
],
"problemMatcher": []
},
{
"label": "Docker - Create Windows Wheel Build Environment",
"type": "process",
"command": "docker",
"args": [
"build",
"--target",
"blenderpy-windows-wheel-builder",
"-t",
"blenderpy/windows-wheel-builder",
"-f",
"${workspaceFolder}/.containers/Dockerfile",
"."
],
"problemMatcher": []
},
{
"label": "Docker - Delete All Containers & Volumes",
"type": "shell",
"command": "docker rm -vf $(docker ps -a -q)",
"problemMatcher": []
},
{
"label": "Docker - Delete All Images",
"type": "shell",
"command": "docker rmi -f $(docker images -a -q)",
"problemMatcher": []
},
{
"label": "Docker - Delete EVERYTHING",
"type": "shell",
"dependsOn": [
"Docker - Delete All Containers & Volumes",
"Docker - Delete All Images"
],
"dependsOrder": "sequence",
"problemMatcher": []
}
],
"inputs": [
{
"id": "BfGitTag",
"type": "command",
"command": "shellCommand.execute",
"args": {
"command": "cd Blender/blender && git tag"
}
},
{
"id": "BfSvnTag",
"type": "command",
"command": "shellCommand.execute",
"args": {
"command": "svn ls https://svn.blender.org/svnroot/bf-blender/tags/"
}
},
{
"id": "BfSvnTrunkNTPlatform",
"type": "command",
"command": "shellCommand.execute",
"args": {
"command": "svn ls https://svn.blender.org/svnroot/bf-blender/trunk/lib/ | findstr \"^win\""
}
},
{
"id": "BfSvnTagNTPlatform",
"type": "command",
"command": "shellCommand.execute",
"args": {
"command": "svn ls https://svn.blender.org/svnroot/bf-blender/tags/${input:BfSvnTag}/lib/ | findstr \"^win\""
}
}
]
}
What Happens:
What I Would Like (opinion)
I would like to be able to have a task input that would accept a type of shell or process (like task). The user would supply a shell command or process (optionally breaking it down by OS variant [like task]). The output of the shell or process would produce text that would be split by newline in VS Code natively. Each split would be a list item for the input.
What Could Work
If there was some documented way for commands run by inputs to gather inputs themselves, then this would work today.
See Also
https://github.com/augustocdias/vscode-shell-command/issues/10
If you need to collect many inputs, the current recommendation is that you write an extension that has a command that prompts for input. We do not want to make task inputs recursive, since that gets us into the territory of writing a new programming language.
|
2025-04-01T04:34:44.040784
| 2020-10-30T20:33:23
|
733499757
|
{
"authors": [
"Github2256",
"IllusionMH"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8599",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/109759"
}
|
gharchive/issue
|
EDITING PROBLEM. :(
Issue Type: Bug
HELLO :( am unable to delete a single letter from my code i don't know why but please if you see this,
would you mind fixing this problem.
:(((
VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T15:06:15.712Z)
OS version: Windows_NT x64 10.0.19041
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz (4 x 2694)
GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled
Load (avg)
undefined
Memory (System)
7.95GB (3.25GB free)
Process Argv
--crash-reporter-id df82bdea-5997-4cbf-afe5-4bb5b07b5774
Screen Reader
no
VM
0%
Extensions (4)
Extension
Author (truncated)
Version
githistory
don
0.6.12
python
ms-
2020.10.332292344
debugger-for-chrome
msj
4.12.11
vim
vsc
1.17.1
/needsMoreInfo
Is it reproducible with all extensions disabled?
You can try this with F1 and >Developer: Reload Window With Extensions Disabled
Especially without vim.
Also do you see any read-only modifiers on files? Do you have any custom keybindings that involve delete key?
actually it is fixed now.
am just wondering, since am new at coding in Github can it allow me to see what i coded in vscode like see the game am making or do i need something else.
any help is appreciated :)
|
2025-04-01T04:34:44.046596
| 2021-01-01T09:12:30
|
777248924
|
{
"authors": [
"isidorn",
"sickdyd"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8600",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/113653"
}
|
gharchive/issue
|
Undo should be related only to the area on focus (file edit or file list)
VSCode version: November 2020 (version 1.52)
Steps
Write some code in a new file, rename the file, change the code and keep hitting command + z to undo.
Problem
While pressing command + z to revert changes, even if you cursor is in the text file, it will ask if you want to undo the file renaming.
Expected
Just undo edits in the code when the focus is on the text file where I write code.
Rant
I just want to undo edits to the code, not undo the renaming. The feature was supposed to undo only actions related to where the focus is set but it's not working, it just automatically goes from one stack to another.
From your release notes
Undo file operations in Explorer#
The File Explorer now supports Undo and Redo for all file operations: delete, rename, copy, move, new file, and new folder. Make sure the focus is in the File Explorer and trigger the Undo or Redo commands and your last file operation will be undone or redone respectively. Keep in mind that we have separate undo stacks for the editor and the File Explorer, and we choose which one to undo based on focus.
Also: after I got this message, I was stuck, unable to redo or undo
Could not undo 'Rename index.ts to index.js' across all files. The following files have been closed and modified on disk: /Users/robertoreale/Desktop/webdev.nosync/playaround/api/src/index.ts.
CPUs | Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2600)
-- | --
GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled webgl: enabled webgl2: enabled
Load (avg) | 2, 2, 2
Memory (System) | 32.00GB (1.87GB free)
Process Argv | --crash-reporter-id dc592e5f-dbee-4845-a19e-244f84d0ad99
Screen Reader | no
VM | 0%
Extensions
Extension | Author (truncated) | Version
-- | -- | --
copy-relative-path | ale | 0.0.2
simple-react-snippets | bur | 1.2.3
gitlens | eam | 11.1.0
prettier-vscode | esb | 5.8.0
vue-inline-template | fai | 1.0.1
html-slim-scss-css-class-completion | gen | 1.7.8
gc-excelviewer | Gra | 3.0.40
vscode-graphql | Gra | 0.3.13
ruby | gro | 0.1.0
vscode-edit-csv | jan | 0.5.3
vue | jcb | 0.1.5
vscode-styled-components | jpo | 1.4.1
haml | kar | 1.3.1
vscode-docker | ms- | 1.9.0
mssql | ms- | 1.10.0
remote-containers | ms- | 0.154.1
color-highlight | nau | 2.3.0
env-cmd-file-syntax | Nix | 0.2.2
vetur | oct | 0.31.3
ruby | reb | 0.27.0
rust | rus | 0.7.8
trailing-spaces | sha | 0.3.1
vscode-todo-highlight | way | 1.0.4
vscode-ruby | win | 0.27.0
material-theme | zhu | 3.9.12
Dup of https://github.com/microsoft/vscode/issues/111659
Dup of https://github.com/microsoft/vscode/issues/111659
|
2025-04-01T04:34:44.062589
| 2021-01-20T14:55:11
|
790052685
|
{
"authors": [
"aktoriukas",
"joaomoreno",
"jrieken",
"miketromba",
"misolori"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8601",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/114636"
}
|
gharchive/issue
|
Improve UX For Resizing Editor Suggestions Box
Hello, thank you for your great contributions to VS Code!
Recently in the /r/vscode subreddit, a post was made by a user who was only getting a single editor suggestion while typing. The problem was that the the user must have inadvertently minimized the box in the past, and now had no idea how to restore it to its original size. This happened to me too a while ago, and I went a while without having a good solution to the problem.
Image from reddit post:
Judging by the amount of upvotes on the post (50+ at the time of writing this) I imagine that this is an issue that many VS Code users experience and are confused about at some point. Its also easy for the user to assume that there is just a single suggestion, and decide to disable the box altogether since it's not as useful as it once was.
Is there some simple way to improve the UX without too much trouble? Maybe something like the drag handle UI that shows in the bottom right corner of HTML text areas?
Thanks for reaching out. Yeah, somehow folks run into the "resized to single line" case and I do agree that this is a problem. What I very very keen on knowing is how folks get into this state. Is there a bug in my persist/resize logic or do people unknowingly resize stuff?
Tho, for the next release I have pushed a poor mans fix which is so that sizes below a minimum height aren't persisted anymore. I have used 4.3 - a fraction on purpose so that you can see a little bit of the next item.
What also helps, is to make the resize-sash visible on hover. Our theme don't have a color defined so that are "invisible" but this is what I use and how it looks (mouse not captured, but resizing the width)
"workbench.colorCustomizations": {
"sash.hoverBorder": "#5a505042"
}
Adding @misolori for the proposed drag handle UX. I actually like it and I think it makes sense to have something like that. Too many user have been confused
Thanks for reaching out. Yeah, somehow folks run into the "resized to single line" case and I do agree that this is a problem. What I very very keen on knowing is how folks get into this state. Is there a bug in my persist/resize logic or do people unknowingly resize stuff?
Tho, for the next release I have pushed a poor mans fix which is so that sizes below a minimum height aren't persisted anymore. I have used 4.3 - a fraction on purpose so that you can see a little bit of the next item.
What also helps, is to make the resize-sash visible on hover. Our theme don't have a color defined so that are "invisible" but this is what I use and how it looks (mouse not captured, but resizing the width)
"workbench.colorCustomizations": {
"sash.hoverBorder": "#5a505042"
}
Adding @misolori for the proposed drag handle UX. I actually like it and I think it makes sense to have something like that. Too many user have been confused
Hi,
<-- that's actually me who created a post on Reddit.
I believe that happened ( at least in my case) with one of the extensions, it's difficult to say, which one as I was ok with a single line of example for a long time. And even though that it's an extension 'feature'. Never the less, resizing with a mouse never even came to my mind. As mentioned above some indication for the option to do it would be an improvement.
Hi,
<-- that's actually me who created a post on Reddit.
I believe that happened ( at least in my case) with one of the extensions, it's difficult to say, which one as I was ok with a single line of example for a long time. And even though that it's an extension 'feature'. Never the less, resizing with a mouse never even came to my mind. As mentioned above some indication for the option to do it would be an improvement.
The drag handle is typically used for text inputs, not sure if that would work well here. I'd be in favor of adding a sash hover color for our default themes but I think @joaomoreno wasn't a fan of this. I'd say we need to make sure that the resizing indicators match the rest (sidebar, panels, editors, etc.) and the sash color is one that spans all of those.
The drag handle is typically used for text inputs, not sure if that would work well here. I'd be in favor of adding a sash hover color for our default themes but I think @joaomoreno wasn't a fan of this. I'd say we need to make sure that the resizing indicators match the rest (sidebar, panels, editors, etc.) and the sash color is one that spans all of those.
I'd be in favor of adding a sash hover color for our default themes but I think @joaomoreno wasn't a fan of this.
Might just be me! Let's experiment!
I'd be in favor of adding a sash hover color for our default themes but I think @joaomoreno wasn't a fan of this.
Might just be me! Let's experiment!
Another thing that we could try to experiment with is to highlight all sash when they are connected. E.g in the suggest widget when hovering over the horizontal sash also highlight the veritical sash and vice versa
Another thing that we could try to experiment with is to highlight all sash when they are connected. E.g in the suggest widget when hovering over the horizontal sash also highlight the veritical sash and vice versa
So here's one thing we can try, I played around with setting the sash hover color using an existing color and focusBorder seemed to be the best color that other themes also included. Here's what that looks like:
And then how it applies for the rest of the workbench:
https://user-images.githubusercontent.com/35271042/105428063-6b501600-5c03-11eb-9528-322cddbb8f0f.mov
Since we're at the end of the iteration I think we should wait until the next milestone to try this out.
So here's one thing we can try, I played around with setting the sash hover color using an existing color and focusBorder seemed to be the best color that other themes also included. Here's what that looks like:
And then how it applies for the rest of the workbench:
https://user-images.githubusercontent.com/35271042/105428063-6b501600-5c03-11eb-9528-322cddbb8f0f.mov
Since we're at the end of the iteration I think we should wait until the next milestone to try this out.
Looks good and consistent.
Looks good and consistent.
Alright, I just enabled this for all themes. Let's try it out and see how it feels.
This happened with @joaomoreno's changes. Thanks
|
2025-04-01T04:34:44.095937
| 2021-02-14T13:21:13
|
807959911
|
{
"authors": [
"joe733",
"manishrnl"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8602",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/116641"
}
|
gharchive/issue
|
taking toooooooooo much time to compile a 20 line code
We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug
i had written a 20 line code in visual studio code and it takes much time to compile.i had waited for half an hour but i didnt get any output.I dont know when will this run succesfully .I get this compiling duration delay on nearly every programme i run on it. If the problem persist then i'll had to switch to my earlier software i.e.., CODE BLOCK
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19042
System Info
Item
Value
CPUs
Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz (4 x 3191)
GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onprotected_video_decode: enabledrasterization: unavailable_offskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: unavailable_off
Load (avg)
undefined
Memory (System)
7.93GB (5.16GB free)
Process Argv
--crash-reporter-id 0a0147a5-1d1a-4d17-aea2-bb7d51deb5ab
Screen Reader
no
VM
0%
Extensions (11)
Extension
Author (truncated)
Version
code-runner
for
0.11.2
csharp
ms-
1.23.9
cpptools
ms-
1.2.0
java
red
0.75.0
swdc-vscode
sof
2.4.9
vscodeintellicode
Vis
1.2.11
vscode-java-debug
vsc
0.31.0
vscode-java-dependency
vsc
0.18.0
vscode-java-pack
vsc
0.12.1
vscode-java-test
vsc
0.28.0
vscode-maven
vsc
0.27.1
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry914:30256638
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30251590
Hi, is it possible to post the source code, build tools/logs, please. It'll help others debug the issue.
Could you Please tell me which extension should i install so that system
doesn't take much time to compile even a larger file.
On Mon, Feb 15, 2021, 3:20 AM VS Code Issue Triage Bot <
<EMAIL_ADDRESS>wrote:
Closed #116641 https://github.com/microsoft/vscode/issues/116641.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/116641#event-4329164825, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3CV3SAXDWTG2FC7IO2B2LS7BARDANCNFSM4XTHHRHA
.
I didnt get what you said.
Explain me properly and please name the extension i ought to download
On Mon, Feb 15, 2021, 3:20 AM VS Code Issue Triage Bot <
<EMAIL_ADDRESS>wrote:
This issue is caused by an extension, please file it with the repository
(or contact) the extension has linked in its overview in VS Code or the
marketplace https://aka.ms/vscodemarketplace for VS Code. See also our issue
reporting https://aka.ms/vscodeissuereporting guidelines.
Happy Coding!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/116641#issuecomment-778847355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3CV3X3Y7QV74ZJH5BRWQ3S7BARBANCNFSM4XTHHRHA
.
Hi
I just found that scanf() is not working .
Whenever i use scanf() function then compiler didnt finished compiling not
even hours later. Could you now describe why this error occurs or any
extension i should download.
On Mon, Feb 15, 2021, 4:49 PM MANISH KUMAR<EMAIL_ADDRESS>wrote:
I didnt get what you said.
Explain me properly and please name the extension i ought to download
On Mon, Feb 15, 2021, 3:20 AM VS Code Issue Triage Bot <
<EMAIL_ADDRESS>wrote:
This issue is caused by an extension, please file it with the repository
(or contact) the extension has linked in its overview in VS Code or the
marketplace https://aka.ms/vscodemarketplace for VS Code. See also our issue
reporting https://aka.ms/vscodeissuereporting guidelines.
Happy Coding!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/116641#issuecomment-778847355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3CV3X3Y7QV74ZJH5BRWQ3S7BARBANCNFSM4XTHHRHA
.
Hi @manishrnl, your issue seems to be with your code not vscode nor any extension. Please try to compile the program from terminal.
|
2025-04-01T04:34:44.101383
| 2021-05-25T03:24:53
|
900220706
|
{
"authors": [
"connor4312",
"jdneo"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8603",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/124544"
}
|
gharchive/issue
|
Cannot toggle the test hide status
Does this issue occur when all extensions are disabled?: Yes/No
Version: 1.57.0-insider (user setup)
Commit:<PHONE_NUMBER>f77a050b49c10162939bfe60970c29
Date: 2021-05-24T05:14:19.500Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19043
@connor4312 Please correct me if I missed anything. Currently, if a test is set to hide, I didn't find a way to toggle that status, is this by design?
There are two ways to unhide the test:
With the "Unhide all Tests" command, available in the command palette and the filter button
If "Show Hidden Tests" is toggled on, via the "Unhide Tests" context menu action
I cannot see the "Unhide Tests" context menu action
https://user-images.githubusercontent.com/6193897/119440990-e5caa700-bd57-11eb-9f4c-d10955a33b96.mp4
Oop, that's a bug, good catch
|
2025-04-01T04:34:44.106447
| 2021-08-01T13:37:32
|
958506052
|
{
"authors": [
"dbuezas",
"roblourens"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8604",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/130000"
}
|
gharchive/issue
|
[typescript kernel tslab] VSCode's intellisense misses variables from blocks that contain "import" statements
Environment data
VS Code version: Version: 1.58.2 (Universal)
Jupyter Extension version: v2021.8.1054968649
Python Extension version: Not installed
OS: Mac 11.5.1 (20G80)
Python and/or Anaconda version: conda 4.10.3
Type of virtual environment used: N/A
Jupyter server running: Local
Expected behaviour
Imports from previous blocks are visible in following ones
Variables declared in previous blocks are visible in following ones (also if there is an import statement in the previous block)
Actual behaviour
Steps to reproduce:
Install this Jupyter extension
Install Jupyter Lab, tslab, add it as a kernel
Create a new notebook
in block 1: import something in block 1 and declare a variable
in block 2: refer to either the declared variable or imported module
Logs
Not applicable
@mjbvz has there been any discussion about js/ts language support in notebooks or is this out-of-scope for the time being?
|
2025-04-01T04:34:44.114038
| 2021-08-23T21:49:08
|
977508122
|
{
"authors": [
"TylerLeonhardt",
"connor4312",
"eamodio",
"sbatten"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8605",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/131445"
}
|
gharchive/issue
|
Test: Windows 11 Store Installer
Refs: #130410
[x] windows: @TylerLeonhardt (x64)
[ ] windows: @connor4312 (x86)
[x] windows: @eamodio (arm64)
Complexity: 2
Create Issue
Test machine must be running Windows 11
For x86 only, there is no Windows 11 option which means this test is for a theoretical future. Please just try using the installer directly on Windows 10 (which is not signed so you will get additional prompts)
https://github.com/microsoft/vscode-winsta11er/releases/tag/v0.0.3
This milestone, we created a simple executable installer for VS Code that can be deployed to the new Windows 11 Store. Currently, the first version of this installer has been deployed to the store and is available for those using Windows 11 Preview builds.
The installer will always install the latest stable release of VS Code and is completely silent.
To verify this installer:
Uninstall VS Code stable from the target machine.
Open the Microsoft Store on the target machine and search Visual Studio Code
Click Install
Perform general sanity testing on the newly installed VS Code
The store has no uninstall or update process, this is all managed just like it is with the normal user VS Code install on Windows.
Some additional fun testing:
Try the install process with a pre-existing install
Try the install process with the system install pre-installed
Try cutting the network just after the store finishes downloading the installer but while its still installing (this should break the executable and bubble up an error to the store)
Uninstalled with store opened? -> have to restart store to see install button
network cut out? -> have to restart store to see install button (retry button doesn't work)
I feel like these are not vscode bugs... but are Store bugs.
on the VS Code side everything seems to be working.
I'm blocked on https://github.com/microsoft/vscode/issues/131549
I saw the same as @connor4312, but the install did succeed for me (was able to launch VS Code from the start menu). The other issues I saw, I don't know how much control over the experience we have:
There was no launch button in the Store for VS Code, just a disabled "Installed" button
VS Code doesn't show up in the library in the Store
Works now!
|
2025-04-01T04:34:44.120616
| 2021-11-03T08:52:18
|
1043226776
|
{
"authors": [
"alexdima",
"weinand"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8606",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/136342"
}
|
gharchive/issue
|
Support structured "browser" property in package.json
Today VS Code supports a browser property of type string in the package.json to specify an extension's entry point for web worker based extensions.
When using esbuild for bundling the extension, the browser property of the package.json can be used to substitute some node-only built-in packages for a browser-friendly alternative by listing (see https://esbuild.github.io/getting-started/#bundling-for-the-browser).
When this esbuild feature is used, VS Code runs into an issue and shows this alert:
I suggest that VS Code accepts a structured browser property and looks for a main sub-property in this case.
/cc @jrieken @alexdima @sandy081
@weinand I'm sorry, this is very unfortunate. Is that the only way in which esbuild can be configured? It is unfortunate that they chose the same property name. It looks like this only happened 2 months ago -- https://github.com/defunctzombie/package-browser-field-spec . I wonder if they would be willing to add alternative configuration methods to esbuild besides the "browser" field in package.json ?
@alexdima the structured browser property was already supported in package.json more than a year ago when I started to provide a "browser" version of the debugadapter npm module. At that time esbuild was not even on my radar but webpack supported that property already for the same purpose (on the receiving side).
So even if we do use the structured browser propertyfor bundling extensions, a structuredbrowser` property might occur out there...
@weinand As a workaround to get unstuck, would one of the following work:
have a fake esbuild/package.json that defines the "browser" field to esbuild's liking and launch esbuild from that folder as a cwd
have a prepublishOnly script that edits the package.json to delete "browser" or turn it into a string again.
|
2025-04-01T04:34:44.130539
| 2022-01-17T13:48:16
|
1105879240
|
{
"authors": [
"stellarpower",
"weinand"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8607",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/140859"
}
|
gharchive/issue
|
launch.json - add option for logging stdout/stderr to file
My application dumps useful information to stdout / stderr when I run it. When debugging, I'd like to be able to copy this to a file automatically, rather than need to use some wort of wrapper script that calls tee, copy-paste from the output console, or run separately to capture this. There may well be an existing workaround, but as this is quite a simple and I imagine commonly useful feature request, I think it would be nice to add support for it on its own.
I'd propose adding an option similar ot this to launch.json, most likely keeping it simple as it's a pretty trivial addition:
// ...
configurations: [{
"name": "Foo",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/main",
// ...
"log": {
"stdout": "/path/to/file.out"
"stderr": "/path/to/file.err"
"stdin": "/path/to/file.in" // Optional - capture anything typed into the run console.
}
// ...
},
// ...
@stellarpower in theory this feature request sounds simple to implement but in reality it is difficult.
The problem is that VS Code knows nothing about "stdout/stdin/stderr" of the debuggee because only the debug extension controls the debuggee and "knows" if it supports "stdout/stdin/stderr" and whether it is possible to redirect "stdout/stdin/stderr" to/from a file.
Thanks for the fast response!
Afraid I'm not sure I understand, what do you mean by if the debuggee supports stdout/stdin/stderr? Every process forked ought to have at least these file descriptors opened I believe.
Presumably for any extenson being used to debug, if it outputs something to the integrated console as part of this it'd need to get access to the console in the same way as a different extension, wouldn't it?
@stellarpower VS Code does not know anything about "forked processes". It is the debug extension that might fork things. But when debugging Javascript running in a browser, or when attaching a debugger to an already running process, there is no need to "fork a process" and as a consequence there is nothing like "stdout/stdin/stderr".
If a debug extension starts a debuggee in the integrated terminal (or external terminal), then debuggee's "stdout/stdin/stderr" are managed directly by the integrated terminal's shell. In this case not even the debug extension sees the input/output "stdout/stdin/stderr". Only if the debuggee is launched in the debug console, has the debug extension a chance to see the stdout/stderr (but not even stdin).
So, in that case, would it be possible to wrap the shell that is running in the integrated or external terminal? Ultimately for text to appear in the terminal for the debugging process, it must have access to a stream at this point. I think dumping that would be sufficient to achieve this goal, although granted there may be many steps inbetween that make it ugly to perform in code itself.
17 Jan 2022 16:27:42 Andre Weinand @.***>:
@stellarpower[https://github.com/stellarpower] VS Code does not know anything about "forked processes". It is the debug extension that might fork things. But when debugging Javascript running in a browser, or when attaching a debugger to an already running process, there is no need to "fork a process" and as a consequence there is nothing like "stdout/stdin/stderr".
If a debug extension starts a debuggee in the integrated terminal (or external terminal), then debuggee's "stdout/stdin/stderr" are managed directly by the integrated terminal's shell. In this case not even the debug extension sees the input/output "stdout/stdin/stderr". Only if the debuggee is launched in the debug console, has the debug extension a chance to see the stdout/stderr (but not even stdin).
—
Reply to this email directly, view it on GitHub[https://github.com/microsoft/vscode/issues/140859#issuecomment-1014713770], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ABGF2APHAGPMWCUWVWMILMDUWQ7P3ANCNFSM5MEXVAMQ].
You are receiving this because you were mentioned.
[data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEgAAABICAYAAABV7bNHAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAArSURBVHic7cEBDQAAAMKg909tDjegAAAAAAAAAAAAAAAAAAAAAAAAAAA+DFFIAAEctgHwAAAAAElFTkSuQmCC###24x24:true###][Tracking image][https://github.com/notifications/beacon/ABGF2AJWHPR4UUAUVUDJNQTUWQ7P3A5CNFSM5MEXVAM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHR5U3KQ.gif]
Yes, the command that is used to run the debuggee in the shell could redirect "stdout/stdin/stderr". But this command is an implementation detail of the debug extension and not controlled by VS Code, so VS Code can not support this generically. So only the debug extension could implement this.
What makes things complex on that front is the fact that for many debuggers the debuggee is not directly launched in the shell but indirectly from within a command line debugger like "gdb". Redirecting "stdout/stdin/stderr" of the "gdb" does not help redirecting "stdout/stdin/stderr" of the debuggee.
|
2025-04-01T04:34:44.139757
| 2022-01-21T21:44:13
|
1110971697
|
{
"authors": [
"dreammixgames",
"mjbvz"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8608",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/141186"
}
|
gharchive/issue
|
Omnisharp crashes, giving "Null Reference Exception"
I'm not sure how to reproduce as I don't know what the issue is. Intellisense just stopped working yesterday and I've been stalled in my work as it's also telling me that places without errors are having errors as well. Please help
This is the bug that I'm getting:
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 x 4200)
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.91GB (8.25GB free)
Process Argv
C:\Users\nicep\Documents\Game Projects\Legend-Maker\Legend Maker -g C:\Users\nicep\Documents\Game Projects\Legend-Maker\Legend Maker\Assets\Resources\Prefabs\Gameplay\2. Enemies\Bosses\Froggaus\Scripts\Froggaus.cs:1:0 --crash-reporter-id 7964e3fe-e626-42da-b1d7-548172f7d2f3
Screen Reader
no
VM
0%
Extensions (6)
Extension
Author (truncated)
Version
comment-anchors
Exo
1.9.6
auto-using
Fud
0.7.15
auto-comment-blocks
kev
1.0.1
unity-code-snippets
kle
1.3.0
csharp
ms-
1.24.0
unity-debug
Uni
3.0.2
/extC#
|
2025-04-01T04:34:44.150111
| 2022-01-21T22:35:14
|
1111005497
|
{
"authors": [
"bpasero",
"jeffb-sfdc"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8609",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/141190"
}
|
gharchive/issue
|
editor.document.uri return stale URI after file rename
Does this issue occur when all extensions are disabled?: Yes
VS Code Version: 1.63.2
OS Version: OSX 11.6.2
Steps to Reproduce:
create a file
Using either the Finder, or within VS Code itself, rename the file and change the case, but don't add or remove any extra characters. For example, rename "testfile.js" to "testFile.js"
-> In the Explorer view, the file appears correctly
Restart VS Code and open the same project (just to make sure the change is picked up)
With the file open and in the active editor, run an extension and call editor.document.uri
Result: The original filename is returned (eg "testfile.js")
Expected: "testFile.js"
We publish an extension and we have some code which is failing because of this.
Yeah, this works "as designed", even though maybe unexpected: once an editor is opened it defines the casing of the document URI it shows. If you rename the file case, the document URI does not change, only the "associated resource" so that the label can update. When we close and reopen VSCode, the editor is still there as it was originally opened with the casing from the beginning.
On top of that we cache normalized URIs per session, so even when you now close and reopen the editor, the old URI form will preserve. The only way out is to close the editor and restart.
This is hassle, but imho a lot less hassle compared to all the issues we were able to fix with this approach ("canonical URIs").
https://github.com/microsoft/vscode/issues/137256 is related where an API is discussed that could provide extensions with the "associated URI".
Question: how do you use the editor.document.uri that it would be relevant how the casing is?
Hi @bpasero , thanks for the reply.
Yeah, this works "as designed", even though maybe unexpected
Not knowing your codebase, or historical issues, from my view it looks like a bug. If I start out with foobarbaz.js, and then rename it (either via VS Code or via the finder) to fooBarBaz.js and then restart VS Code, the files system (ls), the Finder, and VS Code displays each display fooBarBaz.js, yet editor.document.uri returns foobarbaz.js.
While I know of the issue and the work around, I suspect our customers won't, and so when our code fails due to the file paths not matching, they won't know to rename the file to something with different characters, and then rename back.
how do you use the editor.document.uri that it would be relevant how the casing is?
It's a little involved. Without going into all the details, we're using a library which gives us a list of files of a certain type. The filenames in the list match what's in the file system (so /{path-to-file}/fileName.ext). In our code, we're creating a Map<string, string> of the files, with the key being the path to the file. Later we do something along the lines of:
public findMatch(uri: vscode.Uri): string {
return this.files.get(uri.toString());
}
uri is coming from editor.document.uri, and since foobarbaz.js doesn't match fooBarBaz.js, the function isn't returning a match.
If this is "as designed" I'll understand, but this seems like a bug, and is causing bugs in our extension and impacting our users.
@jeffb-sfdc we obviously face the same challenge in VSCode internally because of the way how we handle file paths and have utilities that explicitly ignore casing on platforms that are case insensitive (Windows, macOS), e.g. ResourceMap:
https://github.com/microsoft/vscode/blob/a1541e92a2ee4f86e2aea1fcd0079b6b8ab5f821/src/vs/base/common/map.ts#L757
This is not just limited to file renames, a user may choose to open a folder from the command line with "wrong" casing, e.g. code <path to folder in upper case> and we preserve the case in the session. As such, every code we have that tries to compare paths is ignoring casing on Windows and Linux.
https://github.com/microsoft/vscode/issues/137256#issuecomment-984483333 is relevant where maybe an API is needed for extensions to use these utilities as well.
|
2025-04-01T04:34:44.155403
| 2022-01-24T22:11:16
|
1113194574
|
{
"authors": [
"elibroftw",
"lszomoru"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8610",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/141332"
}
|
gharchive/issue
|
Ctrl + Shift + G does not focus on Message
Does this issue occur when all extensions are disabled?: Yes
(follow the steps twice and you will get the following)
VS Code Version: Latest
OS Version: Windows 10
Steps to Reproduce:
Press Ctrl + Shift + G
Type my message
Expected:
@elibroftw, apologies for not getting back to you on this until now. I am unable to reproduce this issue with the latest Insiders build. I will go ahead and close this issue but please feel free to reopen in case you are still able to reproduce it. Thank you very much!
|
2025-04-01T04:34:44.159069
| 2022-05-31T16:24:26
|
1254108645
|
{
"authors": [
"Tyriar",
"meganrogge"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8611",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/150877"
}
|
gharchive/issue
|
bash debug trap doesn't work with shell integration for multi-word functions
add trap "echo Hello" debug to your .bash_profile with shell integration disabled -> Hello is echoed
enable shell integration and create a bash terminal
🐛 Hello is not echoed
this is because cut' ' -f3 uses ' ' as the delimiter and -f3 gives only the 3rd field that results from that
@meganrogge I'm not sure this case is particularly important since traps are typically always set to functions?
I don't think we should hope that is the case. They can be strings that are quite complicated
Spent several hours trying to get this to work to no avail.
this still doesn't work
|
2025-04-01T04:34:44.160896
| 2022-08-08T17:08:38
|
1332153626
|
{
"authors": [
"PurplePanther",
"VSCodeTriageBot",
"joaomoreno"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8612",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/157537"
}
|
gharchive/issue
|
Can't delete Code.exe
I needed to uninstall Visual Studio Code because I accidentally made Code.exe stop working and it couldn't update because of a "Can't rename" error. I want to reinstall it but I can't delete the Microsoft VS Code folder, and I can't do that because to delete Code.exe I need permission from the administrator. Thing is, I'm the administrator. How can I delete Code.exe?
@PurplePanther Could you remove it already?
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
|
2025-04-01T04:34:44.162806
| 2022-08-20T04:13:30
|
1345049513
|
{
"authors": [
"VSCodeTriageBot",
"alexr00",
"harshkash018"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8613",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/158645"
}
|
gharchive/issue
|
Mouse curser behave abnormal it keeps on jumping
Hello Team
Mouse curser behave abnormal it keeps on jumping to other task and keeps on opening it, making it difficult to work on vs code. it freezes jumps and open all other contents.
This happens only with the vs code editor while I am working with other application it does not happen like that .
Does this issue still occur if you disable all extensions?
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
|
2025-04-01T04:34:44.185209
| 2022-09-12T08:41:57
|
1369498749
|
{
"authors": [
"VanshSh",
"lszomoru"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8614",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/160685"
}
|
gharchive/issue
|
Source Control (Intialize Repository)
Type: Bug
I tried to initalize the repository but there is no response. It is not working.
VS Code version: Code 1.71.0 (784b0177c56c607789f9638da7b6bf3230d47a8c, 2022-09-01T07:36:10.600Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No
System Info
Item
Value
CPUs
11th Gen Intel(R) Core(TM) i5-11320H @ 3.20GHz (8 x 3187)
GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off
Load (avg)
undefined
Memory (System)
7.79GB (2.45GB free)
Process Argv
--crash-reporter-id 774bf0cf-629d-4665-99d1-6effa74bcf17
Screen Reader
no
VM
0%
Extensions (29)
Extension
Author (truncated)
Version
emojisense
bie
0.9.1
markdown-preview-github-styles
bie
1.0.1
vscode-tailwindcss
bra
0.8.6
path-intellisense
chr
2.8.1
es7-react-js-snippets
dsz
4.4.3
gitlens
eam
12.2.2
react-native-react-redux
EQu
2.0.6
prettier-vscode
esb
9.8.0
auto-rename-tag
for
0.1.10
codespaces
Git
1.10.4
copilot
Git
1.44.6735
remotehub
Git
0.42.0
vscode-pull-request-github
Git
0.50.0
vscode-colorize
kam
0.11.1
git-graph
mhu
1.30.0
js-debug-nightly
ms-
2022.9.717
live-server
ms-
0.4.0
remote-repositories
ms-
0.20.0
vsliveshare
ms-
1.0.5711
vsliveshare-pack
ms-
0.4.0
vscode-react-native
msj
1.9.3
nextjs-snippets
Pul
0.0.5
vscode-thunder-client
ran
1.18.7
LiveServer
rit
5.7.9
highlight-matching-tag
vin
0.10.1
vscodeintellicode
Vis
1.2.25
vscode-conventional-commits
viv
1.24.2
vscode-icons
vsc
11.17.0
JavaScriptSnippets
xab
1.8.0
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411cf:30557515
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
pylanb8912:30545647
vsclangdf:30486550
c4g48928:30535728
hb751961:30553087
dsvsc012cf:30540253
azure-dev_surveyone:30548225
2144e591:30553903
@VanshSh, could you please use the steps from this wiki page to enable trace logging. After you have done that, please restart VS Code, open the folder/workspace and click on the "initialize repository" button, and share the contents of the git output window. Thank you.
I followed the above step and I got the following Git Output:
[2022-09-12T12:33:35.445Z] Log level: Trace
[2022-09-12T12:33:35.451Z] [info] Validating found git in: C:\Program Files\Git\cmd\git.exe
[2022-09-12T12:33:35.505Z] [info] Using git 2.37.2.windows.2 from C:\Program Files\Git\cmd\git.exe
[2022-09-12T12:33:35.505Z] [trace] [swf] Scan workspace folders: [c:\Users\vansh\Documents\Developer\foodie]
[2022-09-12T12:33:35.505Z] [trace] [svte] Scan visible text editors. autoRepositoryDetection=true
[2022-09-12T12:33:35.506Z] [trace] [swsf] Scan workspace sub folders. autoRepositoryDetection=true
[2022-09-12T12:33:35.506Z] [trace] [swsf] Workspace folder: c:\Users\vansh\Documents\Developer\foodie
[2022-09-12T12:33:35.507Z] [trace] Opening repository: c:\Users\vansh\Documents\Developer\foodie
[2022-09-12T12:33:35.534Z] [trace] [swsf] Workspace scan settings: repositoryScanMaxDepth=1; repositoryScanIgnoredFolders=[node_modules]; scanRepositories=[]
[2022-09-12T12:33:35.534Z] [trace] [swsf] Workspace scan sub folders: [c:\Users\vansh\Documents\Developer\foodie\.expo, c:\Users\vansh\Documents\Developer\foodie\.expo-shared, c:\Users\vansh\Documents\Developer\foodie\.vscode, c:\Users\vansh\Documents\Developer\foodie\assets, c:\Users\vansh\Documents\Developer\foodie\screens]
[2022-09-12T12:33:35.537Z] [trace] [svte] Scan visible text editors. autoRepositoryDetection=true
[2022-09-12T12:33:35.578Z] [trace] [svte] Scan visible text editors. autoRepositoryDetection=true
[2022-09-12T12:33:35.598Z] > git rev-parse --show-toplevel [86ms]
[2022-09-12T12:33:35.598Z] fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'
To add an exception for this directory, call:
git config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie
Set the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run
again for more information.
[2022-09-12T12:33:35.599Z] [trace] Opening repository for path='c:\Users\vansh\Documents\Developer\foodie' failed; ex=Failed to execute git {
"exitCode": 128,
"gitCommand": "rev-parse",
"stdout": "",
"stderr": "fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'\nTo add an exception for this directory, call:\n\n\tgit config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie\n\nSet the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run\nagain for more information.\n"
}
[2022-09-12T12:33:35.599Z] [trace] Opening repository: c:\Users\vansh\Documents\Developer\foodie\.expo
[2022-09-12T12:33:35.656Z] > git rev-parse --show-toplevel [54ms]
[2022-09-12T12:33:35.656Z] fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'
To add an exception for this directory, call:
git config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie
Set the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run
again for more information.
[2022-09-12T12:33:35.657Z] [trace] Opening repository for path='c:\Users\vansh\Documents\Developer\foodie\.expo' failed; ex=Failed to execute git {
"exitCode": 128,
"gitCommand": "rev-parse",
"stdout": "",
"stderr": "fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'\nTo add an exception for this directory, call:\n\n\tgit config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie\n\nSet the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run\nagain for more information.\n"
}
[2022-09-12T12:33:35.657Z] [trace] Opening repository: c:\Users\vansh\Documents\Developer\foodie\.expo-shared
[2022-09-12T12:33:36.723Z] > git rev-parse --show-toplevel [1062ms]
[2022-09-12T12:33:36.723Z] fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'
To add an exception for this directory, call:
git config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie
Set the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run
again for more information.
[2022-09-12T12:33:36.724Z] [trace] Opening repository for path='c:\Users\vansh\Documents\Developer\foodie\.expo-shared' failed; ex=Failed to execute git {
"exitCode": 128,
"gitCommand": "rev-parse",
"stdout": "",
"stderr": "fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'\nTo add an exception for this directory, call:\n\n\tgit config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie\n\nSet the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run\nagain for more information.\n"
}
[2022-09-12T12:33:36.724Z] [trace] Opening repository: c:\Users\vansh\Documents\Developer\foodie\.vscode
[2022-09-12T12:33:36.841Z] > git rev-parse --show-toplevel [112ms]
[2022-09-12T12:33:36.841Z] fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'
To add an exception for this directory, call:
git config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie
Set the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run
again for more information.
[2022-09-12T12:33:36.842Z] [trace] Opening repository for path='c:\Users\vansh\Documents\Developer\foodie\.vscode' failed; ex=Failed to execute git {
"exitCode": 128,
"gitCommand": "rev-parse",
"stdout": "",
"stderr": "fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'\nTo add an exception for this directory, call:\n\n\tgit config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie\n\nSet the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run\nagain for more information.\n"
}
[2022-09-12T12:33:36.842Z] [trace] Opening repository: c:\Users\vansh\Documents\Developer\foodie\assets
[2022-09-12T12:33:36.970Z] > git rev-parse --show-toplevel [126ms]
[2022-09-12T12:33:36.970Z] fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'
To add an exception for this directory, call:
git config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie
Set the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run
again for more information.
[2022-09-12T12:33:36.970Z] [trace] Opening repository for path='c:\Users\vansh\Documents\Developer\foodie\assets' failed; ex=Failed to execute git {
"exitCode": 128,
"gitCommand": "rev-parse",
"stdout": "",
"stderr": "fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'\nTo add an exception for this directory, call:\n\n\tgit config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie\n\nSet the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run\nagain for more information.\n"
}
[2022-09-12T12:33:36.970Z] [trace] Opening repository: c:\Users\vansh\Documents\Developer\foodie\screens
[2022-09-12T12:33:37.035Z] > git rev-parse --show-toplevel [61ms]
[2022-09-12T12:33:37.035Z] fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'
To add an exception for this directory, call:
git config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie
Set the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run
again for more information.
[2022-09-12T12:33:37.036Z] [trace] Opening repository for path='c:\Users\vansh\Documents\Developer\foodie\screens' failed; ex=Failed to execute git {
"exitCode": 128,
"gitCommand": "rev-parse",
"stdout": "",
"stderr": "fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'\nTo add an exception for this directory, call:\n\n\tgit config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie\n\nSet the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run\nagain for more information.\n"
}
[2022-09-12T12:33:39.306Z] [trace] [svte] Scan visible text editors. autoRepositoryDetection=true
[2022-09-12T12:33:44.808Z] > git init [33ms]
[2022-09-12T12:33:45.368Z] [trace] Opening repository: c:\Users\vansh\Documents\Developer\foodie\
[2022-09-12T12:33:45.399Z] > git rev-parse --show-toplevel [29ms]
[2022-09-12T12:33:45.399Z] fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'
To add an exception for this directory, call:
git config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie
Set the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run
again for more information.
[2022-09-12T12:33:45.399Z] [trace] Opening repository for path='c:\Users\vansh\Documents\Developer\foodie\' failed; ex=Failed to execute git {
"exitCode": 128,
"gitCommand": "rev-parse",
"stdout": "",
"stderr": "fatal: detected dubious ownership in repository at 'C:/Users/vansh/Documents/Developer/foodie'\nTo add an exception for this directory, call:\n\n\tgit config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie\n\nSet the environment variable GIT_TEST_DEBUG_UNSAFE_DIRECTORIES=true and run\nagain for more information.\n"
}
[2022-09-12T12:33:49.867Z] [trace] [svte] Scan visible text editors. autoRepositoryDetection=true
Please help 🆘
@VanshSh, thank you! You are hitting a behaviour change in git that is documented in this blog post. We are looking at improving the messaging when sure a repository is detected but for the time being the only solution to this is to run the following command:
git config --global --add safe.directory C:/Users/vansh/Documents/Developer/foodie
|
2025-04-01T04:34:44.238162
| 2022-11-08T12:28:15
|
1440104828
|
{
"authors": [
"VSCodeTriageBot",
"rebornix",
"timforby"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8615",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/165809"
}
|
gharchive/issue
|
Notebook cut/copy stack overwrites editor clipboard
Type: Bug
Sorry if this is for the jupyter extension, but it seems like notebook is internal to vscode.
When trying to cut and paste I am used to the jupyter browser style of managing two different clipboards, one for cells and one for cell contents. It appears that the VSCode editor respects the notebook clipboard but the notebook clipboard will overwrite the contents of the editor.
Here are the steps to reproduce and after I show the steps that show how the editor clipboard works as intended.
Create new jupyter notebook.
create new cell, write "foo" in cell, select "foo" and copy (ctrl+c), exit cell (escape) [or copy text from anywhere else]
create new cell, write "bar" in cell, exit cell (escape)
copy/cut cell (x/c)
paste cell (v)
edit cell (enter), paste (ctrl+v)
expect to paste: "foo"
what happens: "bar"
The editor clipboard does not overwrite which I think makes more sense. Example:
Create new jupyter notebook.
create new cell, write "bar" in cell, exit cell (escape)
copy/cut cell (x/c)
create new cell, write "foo" in cell, select "foo" and copy (ctrl+c), exit cell (escape) [or copy text from anywhere else]
paste cell (v)
edit cell (enter), paste (ctrl+v)
expect to paste: "foo"
what happens: "foo"
VS Code version: Code 1.73.0 (Universal) (8fa188b2b301d36553cbc9ce1b0a146ccb93351f, 2022-11-01T15:38:50.881Z)
OS version: Darwin arm64 21.6.0
Modes:
Sandboxed: No
System Info
Item
Value
CPUs
Apple M1 Pro (10 x 24)
GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off
Load (avg)
2, 2, 3
Memory (System)
32.00GB (1.72GB free)
Process Argv
/Volumes/workplace/erevia/erevia.code-workspace
Screen Reader
no
VM
0%
Extensions (20)
Extension
Author (truncated)
Version
vscode-sql-formatter
adp
1.4.4
TabOut
alb
0.2.2
gitlens
eam
13.0.4
shell-format
fox
7.2.2
applescript
idl
0.21.2
vsc-python-indent
Kev
1.18.0
isort
ms-
2022.4.0
python
ms-
2022.18.1
vscode-pylance
ms-
2022.11.10
jupyter
ms-
2022.11.1003141027
jupyter-keymap
ms-
1.0.0
jupyter-renderers
ms-
1.0.12
vscode-jupyter-cell-tags
ms-
0.1.6
vscode-jupyter-slideshow
ms-
0.1.5
autodocstring
njp
0.6.1
vscode-sort-json
ric
1.20.0
vscode-open
san
0.1.0
intellicode-api-usage-examples
Vis
0.2.6
vscodeintellicode
Vis
1.2.29
(2 theme extensions excluded)
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
looks like this is the same issue in https://github.com/microsoft/vscode/issues/162204 ?
@timforby you are right, it's duplicate and let's track it there.
|
2025-04-01T04:34:44.240419
| 2023-01-18T18:09:26
|
1538441535
|
{
"authors": [
"meganrogge"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8616",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/171652"
}
|
gharchive/issue
|
when a file is not wrapped in quotes, link line/col detection don't work
miss a semicolon somewhere in your changes
git add . && git commit
try to click on the link to go to the line with a problem
https://user-images.githubusercontent.com/29464607/213260508-eef0d6cc-7f18-4173-9bdd-84473bfae807.mov
So nice that it works 🎉
|
2025-04-01T04:34:44.289163
| 2023-04-05T03:33:50
|
1654873900
|
{
"authors": [
"GitMensch",
"R3EBL",
"VSCodeTriageBot",
"sandy081"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8617",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/179223"
}
|
gharchive/issue
|
EXTENSON NOT INSTALLING
Type: Bug
extenson is not downloading it takes entire day to install a extenson
VS Code version: Code 1.77.0 (7f329fe6c66b0f86ae1574c2911b681ad5a45d63, 2023-03-29T10:02:16.981Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No
THIS IS NOT REPRODUCIBLE.
EXTENSIONS DO INSTALL FINE FOR ME.
AND: WHY ARE WE SCREAMING CAPSLOCKED?
Can you please follow these steps
Enable log level to trace F1 > Developer: Set Log Level... > Trace
Install an extension
Share following logs
F1 > Open View... > Shared
F1 > Open View... > Network
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
|
2025-04-01T04:34:44.312461
| 2023-05-06T08:16:43
|
1698531229
|
{
"authors": [
"akihikodaki",
"andreamah"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8618",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/181693"
}
|
gharchive/issue
|
Global file search does not work.
Type: Bug
Run: git clone https://gitlab.com/qemu-project/qemu.git -b v8.0.0
Run: code qemu
Press Ctrl-P
Type: cpu.c
This should list cpu.c, but it won't.
Oh, I see you're running Asahi Linux. If you do the following, what logs do you get when you perform a search?
run Developer: Set Log Level in the command palette and set Trace
do a search
In the bottom panel, check logs in the Extension Host channel in the Outputs tab
I think this might be a duplicate of https://github.com/microsoft/vscode/issues/179907
Here are the logs:
2023-05-11 22:22:32.575 [info] Extension host with pid 21876 started
2023-05-11 22:22:32.575 [info] Skipping acquiring lock for /home/alarm/.config/Code/User/workspaceStorage/d1e536861f51614c264f81c24f8760d3.
2023-05-11 22:22:32.645 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2023-05-11 22:22:32.650 [info] ExtensionService#_doActivateExtension ms-vscode.cpptools, startup: true, activationEvent: 'workspaceContains:/.vscode/c_cpp_properties.json'
2023-05-11 22:22:32.830 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2023-05-11 22:22:32.839 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2023-05-11 22:22:32.935 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
2023-05-11 22:22:32.993 [info] Eager extensions activated
2023-05-11 22:22:32.993 [info] ExtensionService#_doActivateExtension vscode.extension-editing, startup: false, activationEvent: 'onLanguage:json'
2023-05-11 22:22:32.996 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:json'
2023-05-11 22:22:33.004 [info] ExtensionService#_doActivateExtension vscode.npm, startup: false, activationEvent: 'onLanguage:json'
2023-05-11 22:22:33.008 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2023-05-11 22:22:33.024 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2023-05-11 22:22:33.025 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2023-05-11 22:22:33.032 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-containers, startup: false, activationEvent: 'onStartupFinished'
2023-05-11 22:22:33.048 [info] ExtensionService#_doActivateExtension streetsidesoftware.code-spell-checker, startup: false, activationEvent: 'onStartupFinished'
2023-05-11 22:22:33.138 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2023-05-11 22:22:33.264 [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication, startup: false, activationEvent: 'onAuthenticationRequest:microsoft'
2023-05-11 22:22:40.130 [info] Extension host terminating: renderer closed the MessagePort
2023-05-11 22:22:40.138 [error] Canceled: Canceled
at new l (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:104563)
at a.O (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:110:11657)
at H.<computed>.V.charCodeAt.H.<computed> (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:110:8947)
at e.ExtHostCommands.g (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:124729)
at e.ExtHostCommands.executeCommand (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:124105)
at C.registerCommand.description (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:123398)
at e.ExtHostCommands.h (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:125315)
at e.ExtHostCommands.g (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:124205)
at e.ExtHostCommands.executeCommand (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:124105)
at Object.executeCommand (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:116:24043)
at D (/opt/visual-studio-code/resources/app/extensions/git/dist/main.js:2:1259661)
at v.invoke (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at h.deliver (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at i.fire (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at Object.m [as dispose] (/opt/visual-studio-code/resources/app/extensions/git/dist/main.js:2:1274494)
at /opt/visual-studio-code/resources/app/extensions/git/dist/main.js:2:1278940
at Array.forEach (<anonymous>)
at g.dispose (/opt/visual-studio-code/resources/app/extensions/git/dist/main.js:2:1278926)
at t.<anonymous> (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:12369)
at t.dispose (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:12504)
at t.<anonymous> (/opt/visual-studio-code/resources/app/extensions/git/dist/main.js:2:1261791)
at t.dispose (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:12504)
at T (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:10:12080)
at v.Y (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:11173)
at /opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:9157
at Array.map (<anonymous>)
at v.R (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:9144)
at v.terminate (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:9415)
at d.terminate (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:116:1544)
at g (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:126:34439)
at MessagePortMain.<anonymous> (/opt/visual-studio-code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:126:30578)
at MessagePortMain.emit (node:events:513:28)
at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367) setContext undefined
2023-05-11 22:22:40.144 [info] Extension host with pid 21876 exiting with code 0
2023-05-11 22:22:40.707 [info] Extension host with pid 22066 started
2023-05-11 22:22:40.707 [info] Skipping acquiring lock for /home/alarm/.config/Code/User/workspaceStorage/0f8b5389439ea956357cfabe3cd9213d.
2023-05-11 22:22:40.730 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2023-05-11 22:22:40.732 [info] ExtensionService#_doActivateExtension ms-vscode.cpptools, startup: true, activationEvent: 'workspaceContains:/.vscode/c_cpp_properties.json'
2023-05-11 22:22:40.773 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2023-05-11 22:22:40.782 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2023-05-11 22:22:40.785 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2023-05-11 22:22:40.994 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
2023-05-11 22:22:41.008 [info] Eager extensions activated
2023-05-11 22:22:41.088 [info] ExtensionService#_doActivateExtension vscode.extension-editing, startup: false, activationEvent: 'onLanguage:json'
2023-05-11 22:22:41.092 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:json'
2023-05-11 22:22:41.123 [info] ExtensionService#_doActivateExtension vscode.npm, startup: false, activationEvent: 'onLanguage:json'
2023-05-11 22:22:41.133 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2023-05-11 22:22:41.134 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2023-05-11 22:22:41.136 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-containers, startup: false, activationEvent: 'onStartupFinished'
2023-05-11 22:22:41.155 [info] ExtensionService#_doActivateExtension streetsidesoftware.code-spell-checker, startup: false, activationEvent: 'onStartupFinished'
2023-05-11 22:22:41.174 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2023-05-11 22:22:41.235 [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication, startup: false, activationEvent: 'onAuthenticationRequest:microsoft'
2023-05-11 22:23:13.786 [debug] ExtHostSearch /opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/ripgrep/bin/rg --files --hidden --case-sensitive -g '!**/.git' -g '!**/.svn' -g '!**/.hg' -g '!**/CVS' -g '!**/.DS_Store' -g '!**/Thumbs.db' -g '!**/.ruby-lsp' -g '!**/node_modules' -g '!**/bower_components' -g '!**/*.code-search' --no-ignore-parent --follow --no-config --no-ignore-global
- cwd: /home/alarm/q/var/qemu
- Sibling clauses: {}
I'm quite sure that the issue you pointed out is affecting my system, but somehow the log does not say Unsupported system page size.
I think you might have cut it off before it returned its results. Did you wait a while after performing your search to collect the logs?
Yes, but there is no output. I have just tried while a terminal emulator running watch sh -c 'ps -aux | grep rg' and it showed nothing so I guess rg terminates really quickly.
If you invoke rg directly (I think the path is in the logs), what do you see?
$ /opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/ripgrep/bin/rg --files --hidden --case-sensitive -g '!**/.git' -g '!**/.svn' -g '!**/.hg' -g '!**/CVS' -g '!**/.DS_Store' -g '!**/Thumbs.db' -g '!**/.ruby-lsp' -g '!**/node_modules' -g '!**/bower_components' -g '!**/*.code-search' --no-ignore-parent --follow --no-config --no-ignore-global
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
memory allocation of 5 bytes failed
Aborted (core dumped)
It says "Unsupported system page size".
Ah ok, that should be a duplicate of https://github.com/microsoft/vscode/issues/179907 then. Thanks for the info!
|
2025-04-01T04:34:44.328994
| 2023-08-20T23:52:43
|
1858312774
|
{
"authors": [
"Tyriar"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8619",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/190843"
}
|
gharchive/issue
|
Cursor is not having re-rendered after terminal is focused
Repro:
Open terminal
Focus editor
Focus terminal, 🐛 the cursor is an outline
I can't reproduce anymore
|
2025-04-01T04:34:44.331643
| 2023-09-06T18:15:47
|
1884521667
|
{
"authors": [
"VSCodeTriageBot",
"xgizam77"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8620",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/192320"
}
|
gharchive/issue
|
Infinity 12
Does this issue occur when all extensions are disabled?: Yes/No
VS Code Version:
OS Version:
Steps to Reproduce:
### Tasks
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
|
2025-04-01T04:34:44.337082
| 2023-09-19T03:23:05
|
1902138262
|
{
"authors": [
"VSCodeTriageBot",
"xinyanmsft"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8621",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/193422"
}
|
gharchive/issue
|
Avoid unnecessary repaint in minimap during typing
VS Code Version: 1.80.0
OS Version: Windows 11 22H2 (22621.2134)
Steps to Reproduce:
Open a text file in VSCode editor. Make sure minimap is enabled. Turn on Developer tools \ Rendering \ Paint flashing
Type a few characters without changing line.
Observe the screen refresh areas. With each character typing, the whole minimap area is updated.
I created a recording https://microsoft-my.sharepoint.com/:v:/p/xinyan/Eaf7AGdZNfxGueabgRwFQfwBJHdiJfBXzlOmS5jlSysF7w?e=cdzbmb&xsdata=MDV8MDF8eGlueWFuQG1pY3Jvc29mdC5jb218Njc4NzIyYjY3YjUwNGU5ZjYzZWUwOGRiYjg0Y2NhM2F8NzJmOTg4YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDd8MXwwfDYzODMwNjQxMjE5OTkzNjA5N3xVbmtub3dufFRXRnBiR1pzYjNkOGV5SldJam9pTUM0d0xqQXdNREFpTENKUUlqb2lWMmx1TXpJaUxDSkJUaUk2SWsxaGFXd2lMQ0pYVkNJNk1uMD18MzAwMHx8fA%3D%3D&sdata=YkNVZGVORmpFOThsQm9xVUkvbmFSalZYNWtCYVJzOUZaQWplcE1TbTJNbz0%3D
Expected: only modified region of minimap is refreshed.
Impact: I think this behavior leads to https://github.com/microsoft/vscode/issues/164503, which causes underlying Chromium to combine and refresh the entire whole editor screen. This kind of behavior is not optimized for Remote Desktop experience such as Dev Box.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.82.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!
From Alex: The minimap is rendered with two layers, one for the text, and one for the decorations on top and both use . The code that renders the text is written with a “delta” approach in mind: it tries to touch only the surface which needs to be touched using the putImageData canvas API (where we can basically give an area of pixels).
The code that renders the decorations is written without such an approach. It always clears the entire and redraws the decorations using canvas APIs such as clearRect, fillRect, etc. To get an improvement here, the decorations rendering code needs to be basically reimplemented with a similar “delta” approach in order to minimize the surface of the canvas it touches. This means either moving that to also use putImageData or to continue using clearRect, fillRect, etc, but do so in a more minimal manner, taking into account the rectangles rendered in the last frame.
|
2025-04-01T04:34:44.357107
| 2023-10-18T00:36:50
|
1948518611
|
{
"authors": [
"rebornix",
"rzhao271"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8622",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/195851"
}
|
gharchive/issue
|
Blank setting editor view
Type: Bug
ERR Cannot read properties of undefined (reading '0'): TypeError: Cannot read properties of undefined (reading '0')
at vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1669:910
at Array.forEach (<anonymous>)
at m.o (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1669:871)
at m.n (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1669:33)
at m.k (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1668:1964)
at m.pushGroup (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1668:1572)
at c.J (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1667:2174)
at c.t (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1666:6138)
at c.getSettingsGroups (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1666:6095)
at get settingsGroups [as settingsGroups] (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1666:2950)
at be.Tc (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2342:70919)
at be.setInput (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2342:57798)
at async c.S (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2346:22582)
at async c.L (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2346:21142)
at async c.openEditor (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2346:20120)
at async vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2476:21530
at async B.L (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2362:3043)
VS Code version: Code - Insiders 1.84.0-insider (Universal) (f1c3b1dcf85e3b6ddb24b7dce0e4b122e8ce6233, 2023-10-17T05:38:23.658Z)
OS version: Darwin x64 23.0.0
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|9, 17, 11|
|Memory (System)|32.00GB (0.08GB free)|
|Process Argv|--enable-proposed-api ms-vscode.vscode-notebook-history --enable-proposed-api vscode.notebook-editing --enable-proposed-api vscode.vscode-test-resolver --enable-proposed-api donjayamanne.kusto --enable-proposed-api donjayamanne.jupyterpowertools --enable-proposed-api rebornix.better-jupyter-errors --enable-proposed-api rchiodo.jupyter-tools --crash-reporter-id 1a907bbd-fa02-4595-81e0-63e1648afb31|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Duplicate of #194008
|
2025-04-01T04:34:44.358847
| 2023-10-23T19:03:27
|
1957839902
|
{
"authors": [
"claudiaregio",
"mjbvz"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8623",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/196312"
}
|
gharchive/issue
|
Code action lightbulb covering code & hard to see
The lightbulb appears to be in the wrong spot (usually it's off to the left between the code and line numbers, yes?) and covering code and hard to see. It is also showing up on the wrong line number? See picture below : If my cursor is on line 5 it shows up on line 4
VS Code: 1.83.1
It's a best effort. We try to position it in blank space but if that can't be found, then it will overlap with the code
|
2025-04-01T04:34:44.368722
| 2023-11-02T12:32:02
|
1974152544
|
{
"authors": [
"AnrDaemon",
"benibenj"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8624",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/197227"
}
|
gharchive/issue
|
workbench.action.maximizeEditor command is missing
Type: Bug
I've had a keybind bound to the workbench.action.maximizeEditor command I've been using repeatedly. Now it is gone.
The new workbench.action.maximizeEditorHideSidebar is a no replacement for it, as it hides all other editor groups. Not what I wanted from it. I still need other group's tabs clearly visible, as they are opened project files I use as references. Sometimes opening them side by side, sometimes collapsing to only the headers. But never I want them hidden.
VS Code version: Code 1.84.0 (d037ac076cee195194f93ce6fe2bdfe2969cc82d, 2023-11-01T11:29:04.398Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
Item
Value
CPUs
Intel(R) Core(TM) i3-8145U CPU @ 2.10GHz (4 x 2304)
GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled
Load (avg)
undefined
Memory (System)
7.86GB (1.15GB free)
Process Argv
--folder-uri file:///d%3A/Profiles/anrdaemon/Documents/hk/invapi-php
Screen Reader
no
VM
0%
An alternate solution for me would be to allow the so-called "web panels" - side bar panels containing open project files, read-only with a button to reopen them for editing.
You can use the command workbench.action.toggleMaximizeEditorGroup to maximize/unmaximize the active editor group. If you want to have different shortcuts depending on the maximized state, you can use context keys with your shortcuts (When state).
With maximizedEditorGroup you make your shortcut only run if it is maximized (or not).
multipleEditorGroup (true if more then 1 editor group) could also be helpful depending on the shortcuts you are creating.
We renamed the old maximize feature to expand. You can use the Expand Editor Group (workbench.action.minimizeOtherEditors) command.
The workbench.action.minimizeOtherEditorsHideSidebar command would be a good addition to the mix.
You are right, I will add it back. Until it's available, you can use the workbench.action.closeSidebar command together with workbench.action.minimizeOtherEditors.
Sorry, I don't quite get it. How would I call two commands with a single keybind?
You can run multiple commands with a single shortcut in the following way:
{ "key": "ctrl+k", "command": "runCommands", "args": { "commands": [ "workbench.action.closeSidebar", "workbench.action.minimizeOtherEditors" ] } }
|
2025-04-01T04:34:44.371218
| 2023-11-30T10:10:59
|
2018303719
|
{
"authors": [
"aeschli",
"alexr00"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0004.json.gz:8625",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/199645"
}
|
gharchive/issue
|
scss syntax highlighting: support @layer
Issue of the SCSS grammar
(We're still on the archived https://github.com/atom/language-sass)
@layer in
@layer bootstrap;
@import url('bootstrap/scss/bootstrap.scss') layer(bootstrap);
not being highlighted is SCSS
Marking as a duplicate of the issue tracking finding a new scss grammar: https://github.com/microsoft/vscode/issues/81038
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.