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-01T06:39:35.697843
| 2021-03-17T19:36:40
|
834113982
|
{
"authors": [
"yongyan-gh"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8415",
"repo": "microsoft/sarif-visualstudio-extension",
"url": "https://github.com/microsoft/sarif-visualstudio-extension/pull/381"
}
|
gharchive/pull-request
|
Add FileWatcher to load sarif logs from .sarif folder automatically
for #380
Automatically load all sarif log files from .sarif folder under solution directory to error lists when solution is loaded.
Close all sarif logs when solution is closed.
Monitor the folder and watch sarif log files created/deleted, load/unload results accordingly.
Updates error list when any sarif log file in the folder is updated.
Enabled/disable the behavior using option.
Abandon this PR since the functionality should be added to sarif viewer not sarifer.
Created another PR #382 instead.
|
2025-04-01T06:39:35.702727
| 2020-07-24T09:35:35
|
665047719
|
{
"authors": [
"JarLob",
"jeffersonking"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8416",
"repo": "microsoft/sarif-vscode-extension",
"url": "https://github.com/microsoft/sarif-vscode-extension/issues/307"
}
|
gharchive/issue
|
File location dialog
Tested with 3.2020.715004
When locating sources a FileOpen dialogs pops up, but there is no indication of the path I need to resolve.
In Visual Studio extension the location is in the title of the dialog, like Locate missing file: /folder/folder2/file.ext. This way it is convenient to navigate to the root of the sources and then use the information from the title to find the file.
Not sure if it is the limitation of integration into VS Code. Another option would be to prefill File name: editbox with the relative path of the missing file.
Thanks for the feedback.
A bit of a survey: Do you have a folder open in VS Code? And if so, are the SARIF file and "missing" file both in that same folder? Generally asking: what is the typical file structure relationship between your SARIF file and "missing" file? We are trying to understand the common cases better. Thanks!
Thanks for the feedback.
A bit of a survey: Do you have a folder open in VS Code?
Initially no, but then I tried both options. In both cases it doesn't find the find automatically until I locate it manually. Then when I click on other items it finds the corresponding file.
And if so, are the SARIF file and "missing" file both in that same folder? Generally asking: what is the typical file structure relationship between your SARIF file and "missing" file? We are trying to understand the common cases better. Thanks!
The sarif file is not in the same folder.
We have new logic that, in certain cases, is able to automatically associate SARIF uris with workspace uris. Would you be able to share the project structure and the set of uri's within the SARIF file to help reproduce the issue?
Note: The matching heuristic looks for distinct file names between the SARIF log and workspace. Thus it may not work if there are many files with the same name. However, we do have some more advanced strategies in our back pocket that we can employ depending on feedback/scenarios such as yours.
The file contains sensitive information. I can share it after some time when all issues are fixed.
@JarLob Still having the same issues in the most recent version? If so, let's take a look at your folder structure. Thanks!
|
2025-04-01T06:39:35.705283
| 2023-11-30T16:47:08
|
2019071939
|
{
"authors": [
"markwallace-microsoft"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8417",
"repo": "microsoft/semantic-kernel",
"url": "https://github.com/microsoft/semantic-kernel/issues/3786"
}
|
gharchive/issue
|
.Net: Example44_MultiChatCompletion needs to be rewritten
Describe the bug
The example has the following issues:
It is broken into multiple methods and so is not copy/paste friendly
It uses the IChatCompletion directly, which is not our preferred pattern
It doesn't use a prompt as the input for the example
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.
|
2025-04-01T06:39:35.707720
| 2020-03-27T21:23:43
|
589420314
|
{
"authors": [
"amanbha",
"andrewtyped"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8418",
"repo": "microsoft/service-fabric-client-dotnet",
"url": "https://github.com/microsoft/service-fabric-client-dotnet/issues/85"
}
|
gharchive/issue
|
How are PowerShell help files generated for this repository?
I see that Microsoft.ServiceFabric.Powershell.Http-Help.xml is stored in the repository, and the build depends on this file's presence. Are you able to share how this file is generated? As far as I can tell, the build isn't responsible for it, and no generation tools are referenced by the repository.
Thank you for making this module available!
@andrewtyped The rest api and powershell is generated usign a tool leveraging AutoRest from the swagger rest api specification for service fabric.
Thank you. Is this the tool you're referring to: https://github.com/Azure/autorest.powershell ? If so, would you accept a PR updating the docs to refer to this dependency?
No thats not we use exactly, the tool does use Autorest to generate the models from swagger, but then it generates customized code based on extensions specified in the swagger files, the entire client library in this repo has customized serialization/deserialization logic.
|
2025-04-01T06:39:35.709928
| 2020-12-09T04:28:17
|
759981328
|
{
"authors": [
"GitTorre",
"agolotin"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8419",
"repo": "microsoft/service-fabric-observer",
"url": "https://github.com/microsoft/service-fabric-observer/pull/98"
}
|
gharchive/pull-request
|
Fix a memory leaks with windows Process handling
Process implements IDisposable. Every object returned by Process.GetProcessById() will keep lingering in heap until a service instance restarts.
Thanks for catching these. I have made changes to the upcoming release. These will live in the plugin-refactoring branch, which houses 3.1.0 (which includes a refactored FO API .NET Standard 2.0 library). That branch will be merged into develop then master in the next few days. Appreciate the bugs!
I have merged plugin-refactoring branch into develop. Going to close this PR as it is not going to be merged. As I mentioned, I took your changes already. Thanks again.
Thanks Charles! Appreciate your review!
|
2025-04-01T06:39:35.717597
| 2022-11-12T11:28:33
|
1446409443
|
{
"authors": [
"AravindhKumarSivaramakrishnan",
"carlos-zamora",
"lhecker",
"zadjii-msft"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8420",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/issues/14377"
}
|
gharchive/issue
|
Terminal keeps disappearing when laptop sleeps
Windows Terminal version
1.15.2875.0
Windows build number
10.0.22000.1098
Other Software
No response
Steps to reproduce
Open terminal and let the computer to sleep off and once woken up, the terminal will vanish.
Same behavior with battery and charger connected.
Note: This issue has started with the recent windows update.
Expected Behavior
Terminal should persist the state and behavior and not get closed.
Actual Behavior
Terminal seems to be missing/vanished, process seems to be running sometime (few mins even when the Terminal is missing) in background but eventually stops in some time.
Does the terminal disappear every single time you sleep or only sometimes? Does your device need to sleep for a long time for the terminal to disappear?
Do you see any events in Event Viewer ala "The power manager has not requested the deletion of all entries" / "The power manager has requested the deletion of all entries"/?
See also #12513.
Can you try setting "closeOnExit": "never" in the settings? Maybe pwsh.exe is crashing, exiting, causing the Terminal to "crash".
It's also possible that the Store may have noticed that there was an update available for the Terminal, and chose to update it for you right as it was going to sleep / resuming from sleep. If this happens literally every sleep, then we can probably rule this out.
Does the terminal disappear every single time you sleep or only sometimes? Does your device need to sleep for a long time for the terminal to disappear?
It only happens when the sleep is longer then 4 to 5 mins, few mins in sleep does not kill the terminal
Do you see any events in Event Viewer ala "The power manager has not requested the deletion of all entries" / "The power manager has requested the deletion of all entries"/?
See also #12513.
Can you try setting "closeOnExit": "never" in the settings? Maybe pwsh.exe is crashing, exiting, causing the Terminal to "crash".
It's also possible that the Store may have noticed that there was an update available for the Terminal, and chose to update it for you right as it was going to sleep / resuming from sleep. If this happens literally every sleep, then we can probably rule this out.
Tried "closeOnExit": "never", there is no change in the behavior and also there is no update to Terminal available in store and the issue literally happens for every sleep but only when a process is running (let's say you run an angular app or any process that runs longer). When the terminal is open without any process running, it seems to remain alive.
Checked the Event Logs, nothing related to Terminal or power manager.
We'd love to get some additional information. Would you mind filing this in feedback hub?
/feedback
|
2025-04-01T06:39:35.728847
| 2023-02-19T06:10:57
|
1590578136
|
{
"authors": [
"HarukaMa",
"lhecker",
"zadjii-msft"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8421",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/issues/14877"
}
|
gharchive/issue
|
Rendering of some escape codes are broken on some fonts
Windows Terminal version
1.16.10261.0, also main branch
Windows build number
10.0.19044.2364
Other Software
Most TUI programs
Steps to reproduce
The screenshot below uses make menuconfig on Linux kernel source and tool aptitude, but many TUI applications show this behavior as well. Try using some with specific fonts and you will spot it.
Expected Behavior
Might be the most ambiguous issue title I've written in a while, but I'm not quite sure what's causing it. I'll explain below.
(Warning, lots of screenshots)
When using common monospaced fonts, the rendering is fine:
Consolas:
Lucida Console:
and a third-party one:
MxPlus IBM VGA font:
Actual Behavior
However, when using some fonts (didn't find out the specifics here), the rendering is borked. Notice that the checkboxes are not aligned anymore, some characters are missing, and the window borders are broken:
PC-98 font:
That's a third-party font, however some standard fonts are showing this as well:
SimHei:
MS Gothic:
Tried with AtlasEngine both on and off and nothing changed (it didn't need a restart right?).
Forgot about the aptitude example, but it's like this:
Tried with AtlasEngine both on and off and nothing changed (it didn't need a restart right?).
FWIW it absolutely does require a restart of that tab, unfortunately. One of the few settings that can't hot-reload. Double checking these results with it both enabled and disabled might help point at the right root cause.
I'm sure there's a dupe laying around that @lhecker can find. Probably one for each of the renderers 😅
Just tried and the rendering is broken on both situations:
AtlasEngine off:
AtlasEngine on:
Also it might be a good idea to add a description below to indicate that this specific setting needs a restart (or a new tab) to take effect:
I'm about to open a PR which improves the situation around such box drawing characters up to the point, where we draw to the best capabilities of the font you've chosen. If the font doesn't have proper box drawing characters, they'll look broken, because that's what the font tells us to do. This is for instance the case for MS Gothic, where the right border in make menuconfig will appear invisible, because that's what MS Gothic tells us to do:
For further improvements we'll have to wait for #5897.
|
2025-04-01T06:39:35.735191
| 2020-09-02T21:44:25
|
691446915
|
{
"authors": [
"DHowett",
"carlreinke"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8422",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/issues/7514"
}
|
gharchive/issue
|
"Disable Scroll-Forward" doesn't account for page-up/page-down keys
Environment
Windows build number: 10.0.19041.0
Steps to reproduce
Start PowerShell in conhost.
Enable "Disable Scroll-Forward".
Run a command that produces multiple screens of output.
Use the page-up key to scroll to the top of the output.
Use the page-down key to scroll past the output.
Expected behavior
Scrolling it limited to the output and the scrollbar lets you scroll the output.
Actual behavior
After running command, scrollbar is as expected:
After page-up key once, scrollbar is indeterminate:
After page-up key again, scrollbar indicates that you see all the output (but you don't):
After page-down key, you have scrolled past the end of the output:
So I've got some unfortunate news!
PowerShell (specifically PSReadline) has implemented its own handling for PgUp/PgDown:
In these handlers (code here), they're directly manipulating the console screen buffer.
Because they're setting the actual active viewport using these APIs, there's nothing we can really do but listen to them. If they want to scroll the viewport into the unpopulated region below the virtual bottom, they're fully allowed to do so.
Resolution on this one is, regrettable, "by design" -- we have to support these APIs forever, even if they coincide with our experimental features in an unfortunate way.
|
2025-04-01T06:39:35.742243
| 2021-05-14T21:49:27
|
892266116
|
{
"authors": [
"DHowett",
"miniksa"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8423",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/pull/10098"
}
|
gharchive/pull-request
|
Set keyword flags on all events so those sharing a provider with telemetry do not fire unless tracing is enabled
Set keyword flags on all events so those sharing a provider with
telemetry do not fire unless tracing is enabled
PR Checklist
[x] Closes #10093
[x] I work here
[ ] Tests added/passed
[x] Documentation added in til.h about how keywords work and at the
only other site of keywords we define in the Host project tracing
files.
Detailed Description of the Pull Request / Additional comments
I initially thought that we would need to split providers here to
accomplish this... but @DHowett helped me realize that might be a lot of
additional metadata and bloat binary size. So with help from a friend
from fundamentals, I realized that we could use Keywords to
differentiate here. We can no longer define 0 keywords as that
represents an any/all scenario. Every TraceLoggingWrite event now
needs a keyword. When our events have a keyword, they're not included in
any trace. Additionally, when we have an explicit keyword to check that
is different from the ones used for the telemetry pipeline, we can
ensure that we only do "hard work" to generate debug trace data when an
"ALL" type listener like TraceView or Windows Performance Recorder with
our profiles is listening to these providers for ALL keyworded events.
Validation Steps Performed
[x] - Built with full release build config to confirm performance is
worse than dev builds BECAUSE of the telemetry event collector camping
our provider and triggering full trace event generation on shared
providers.
[x] - Built with full release build config to enable statistics
collection and validated trace event collection is excluded and trace
event short-circuits work with this change.
[ ] - Checked that TraceView still sees both telemetry and tracing
events
[ ] - Checked that WPR with our .wprp profile sees both telemetry and
tracing events
Bonuses:
Added privacy tagging where I noticed it was missing (so we no longer have to confirm those tags on the back end)
Updated wprp file for Terminal providers that are missing but didn't rename the wprp file
nit: shorten PR title to ~72 chars so it doesn't get truncated
@msftbot wait 5 minutes before merging
|
2025-04-01T06:39:35.745030
| 2022-04-04T19:45:05
|
1192235421
|
{
"authors": [
"DHowett"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8424",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/pull/12820"
}
|
gharchive/pull-request
|
Autocomplete keyframe animations when occluded on Windows 11
On certain builds of Windows, when Terminal is set as the default it
will accumulate an unbounded amount of queued animations while the
screen is off and it is servicing window management for console
applications.
This results in Terminal hanging when left overnight, as it has millions
of animations to process.
The new call into TerminalThemeHelpers will tell our compositor to
automatically complete animations that are scheduled while the screen is
off.
Fixes MSFT-38506980
For servicing, this actually needs custom conflict resolution since this PR is built on the Common Nuget infrastructure.
@msftbot merge this in 3 minutes
|
2025-04-01T06:39:35.750193
| 2022-11-28T10:55:06
|
1466209654
|
{
"authors": [
"DHowett",
"jsoref"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8425",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/pull/14455"
}
|
gharchive/pull-request
|
Update to check-spelling v0.0.21
Upgrades check-spelling to v0.0.21
The command to apply changes should now work on Windows (it requires
Perl, but I believe that's more or less present most of the time, and it
should walk you through the rest of the required tools).
There are a bunch of new features, the most important here are probably
being able to update the metadata from Windows. (If it doesn't work,
please @ me).
Also, candidate.patterns will automatically suggest patterns. You can
see them in patterns.txt, e.g.:
# Automatically suggested patterns
# hit-count: 3831 file-count: 582
# IServiceProvider
\bI(?=(?:[A-Z][a-z]{2,})+\b)
The metadata bits (the hit count/file count) don't have to be retained
(I hope they'll be useful in deciding whether/or not to add a pattern,
i.e. "how applicable is it?"), the comment hinting at what the pattern
does is probably worth retaining.
We've been using more or less this version for a while internally
(including talk-to-bot, and, I do have a pattern that could be used to
let people use that in forks, but, I'm going to skip that for now).
This weekend, I did some cleanup for act (to run check-spelling
locally), and some minor polish.
You can see the runs I made in
https://github.com/check-spelling/terminal/actions
Thanks. You're going to want to reenable the workflow :)
indeed, i'm going to reflect the changes to all open branches first (:
thanks @floh96
Well, it turns out that we have 335 branches. Good lord. They've all been updated to<EMAIL_ADDRESS>Thanks again!
|
2025-04-01T06:39:35.756431
| 2024-05-16T23:57:11
|
2301565941
|
{
"authors": [
"DHowett",
"PankajBhojwani",
"erikzhang",
"zadjii-msft"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8426",
"repo": "microsoft/terminal",
"url": "https://github.com/microsoft/terminal/pull/17281"
}
|
gharchive/pull-request
|
Allow actions in the new tab dropdown
Summary of the Pull Request
Targets #17215
Allows the user to define entries in the new tab menu that execute actions, based on their action Id
Detailed Description of the Pull Request / Additional comments
For example, the newTabMenu in the json can now contain:
{
"type": "action",
"actionId": "mySendInputAction"
}
Validation Steps Performed
PR Checklist
[ ] Closes #xxx
[ ] Tests added/passed
[ ] Documentation updated
If checked, please file a pull request on our docs repo and link it here: #xxx
[ ] Schema updated (if necessary)
YAAAAAAAAAAAAAAASS
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
may want to add a "closes #3759"
may want to add a
closes #3759
closes #9362
Very explicitly, you need to put them on separate lines both of which start with "Closes".
Validation Steps Performed
Can I assign an icon to a command?
Can I assign an icon to a command?
Yep!
|
2025-04-01T06:39:35.762060
| 2022-03-17T08:10:54
|
1172058172
|
{
"authors": [
"Evangelink",
"nohwnd",
"stan-sz"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8427",
"repo": "microsoft/testfx",
"url": "https://github.com/microsoft/testfx/issues/1054"
}
|
gharchive/issue
|
Getting DataSource object right is very difficult
Description
I was trying to get the new UI in VS for data driven tests. And getting the object for the data source to correctly serialize is so painful.
My contains other objects and getting it to work took me a lot of time.
Is there any additional guidance on this? Or a method that can check if the type is eligible for the new UI?
From what I see:
Get Set properties need to be used, and default constructor must be present.
[Serialize] needs to be used for all the objects.
Abstract class must not be used.
When inheriting, the objects must be produced exactly using the type that is used in the data source object, but not as any child class.
Using records or readonly record struct does not make this easier.
I could not get it to work when there was a collection on the object, but I might be just confused by some other edge case that was preventing me from getting this to work at the same time.
e.g. This works:
[Serializable]
public class OtherInfo : OtherInfoBase {
}
[Serializable]
public class OtherInfoBase {
public string Name {get; set;}
}
[Serializable]
public class RunnerInfo {
public string Name {get; set;}
public OtherInfo {get; set;}
}
BUT making the RunnerInfo use the Base class, it only works when we assign the BaseClass itself, but not if we create OtherInfo and assign it:
[Serializable]
public class OtherInfo : OtherInfoBase {
}
[Serializable]
public class OtherInfoBase {
public string Name {get; set;}
}
[Serializable]
public class RunnerInfo {
public string Name {get; set;}
public OtherInfoBase {get; set;}
}
@nohwnd What kind of data source are you referring to? Could you provide a more complete example?
DataSource like the one here: https://github.com/microsoft/vstest/blob/3fac63690f8cd14e2681470639b15c527c3d09ff/test/Microsoft.TestPlatform.AcceptanceTests/ExecutionTests.cs#L21
Once your parameter is not a primitive type (RunnerInfo in the case above) it gets really difficult to make sure MSTest will expand it to multiple test cases using the new top level expansion. You need to balance all the things listed above.
@Evangelink - Is this something that can be checked with a MSTest analyzer?
After working for a while on the codebase I think this mostly boils down to the serializer that is used. It would be pretty difficult to enforce the rules by analyzer, and custom data sources are imho not that used to warrant that investment.
|
2025-04-01T06:39:35.764261
| 2024-09-11T09:45:57
|
2519213841
|
{
"authors": [
"Evangelink",
"Mertsch"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8428",
"repo": "microsoft/testfx",
"url": "https://github.com/microsoft/testfx/issues/3807"
}
|
gharchive/issue
|
Typo in MSTEST0016 description
Describe the bug
https://learn.microsoft.com/en-us/dotnet/core/testing/mstest-analyzers/mstest0016
Rule description
A test class should have at least one test method or be static and have methods that are attributed with [AssemblyInitialization] or [AssemblyCleanup].
States AssemblyInitialization, but it should be AssemblyInitialize.
Additional context
MSTest 3.6.0
We will be releasing a bug fix so I'll bakcport this fix into it.
|
2025-04-01T06:39:35.766010
| 2024-12-10T08:08:14
|
2729339879
|
{
"authors": [
"Evangelink",
"Youssef1313"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8429",
"repo": "microsoft/testfx",
"url": "https://github.com/microsoft/testfx/issues/4299"
}
|
gharchive/issue
|
MSTEST0017 (Assertion arguments should be passed in the correct order) shouldn't warn if both arguments are literals
Describe the bug
If both arguments are literals, e.g:
Assert.AreEqual(0, 1);
we currently issue a warning, but following the codefix will still keep the warning.
We shouldn't issue a diagnostic when "both" arguments look like they should be "expected".
Currently, the above snippet will already produce MSTEST0025 (Use 'Assert.Fail' instead of an always-failing 'Assert.AreEqual' assert).
I agree!
|
2025-04-01T06:39:35.769583
| 2020-07-20T20:34:28
|
662236640
|
{
"authors": [
"AyobamiBalogun",
"ccrowley96"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8430",
"repo": "microsoft/tsiclient",
"url": "https://github.com/microsoft/tsiclient/pull/256"
}
|
gharchive/pull-request
|
User/t ayb/geo process graphic2
Created the Geo Process Graphic Component
I'm trying to check out the geo process graphic (running locally on this PR branch) with this example https://insights-local.timeseries.azure.com/withplatform/geoProcessGraphic.html
When I hit that page I get a promise error from HistoryPlayback. @AyobamiBalogun, how can I view the geo graphic? Is that the correct example page?
I'm trying to check out the geo process graphic (running locally on this PR branch) with this example https://insights-local.timeseries.azure.com/withplatform/geoProcessGraphic.html
When I hit that page I get a promise error from HistoryPlayback. @AyobamiBalogun, how can I view the geo graphic? Is that the correct example page?
@darsney Do you know why I'm getting this error when I try to access the geoProcessGraphic? If it's just me, I don't think it's an issue for this PR, I'm just not able to test the graphic. It may be something to do with me not having access to the right env.
|
2025-04-01T06:39:35.772240
| 2022-03-02T11:19:51
|
1157054136
|
{
"authors": [
"donglixp",
"iiLaurens",
"sean-zhuh",
"shumingma"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8431",
"repo": "microsoft/unilm",
"url": "https://github.com/microsoft/unilm/issues/639"
}
|
gharchive/issue
|
When will DeepNorm release code ?
As the title asks.
The code will be updated at https://github.com/microsoft/unilm/tree/master/deepnet soon
Thanks.
Any updates here?
The code will be ready very soon. Please stay tuned!
@sean-zhuh @iiLaurens https://github.com/microsoft/torchscale
|
2025-04-01T06:39:35.773799
| 2022-10-27T22:46:15
|
1426350441
|
{
"authors": [
"BillyONeal"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8432",
"repo": "microsoft/vcpkg-tool",
"url": "https://github.com/microsoft/vcpkg-tool/pull/775"
}
|
gharchive/pull-request
|
Change the mismatched VCPKG_ROOT message to note which vcpkg.exe
… is emitting the message for clarity.
Thanks for the reviews folks!
|
2025-04-01T06:39:35.888011
| 2023-10-12T13:22:16
|
1939994960
|
{
"authors": [
"LilyWangLL",
"flmmkch",
"gennadij",
"trileyinvicro"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8433",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/34450"
}
|
gharchive/issue
|
[ICU] build failure
Operating system
Windows
Compiler
MSVC
Steps to reproduce the behavior
vcpkg install icu
Failure logs
C:\vcpkg>vcpkg install icu
warning: The vcpkg C:\vcpkg\vcpkg.exe is using detected vcpkg root C:\vcpkg and ignoring mismatched VCPKG_ROOT environment value C:\software\tools\vcpkg. To suppress this message, unset the environment variable or use the --vcpkg-root command line switch.
warning: In the September 2023 release, the default triplet for vcpkg libraries changed from x86-windows to the detected host triplet (x64-windows). For the old behavior, add --triplet x86-windows . To suppress this message, add --triplet x64-windows .
Computing installation plan...
The following packages will be built and installed:
icu[core,tools]:x64-windows -> 73.1
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\heimann\AppData\Local\vcpkg\archives in 287 us. Use --debug to see more details.
Installing 1/1 icu:x64-windows...
Building icu[core,tools]:x64-windows...
-- Using cached icu4c-73_1-src.tgz.
-- Cleaning sources at C:/vcpkg/buildtrees/icu/src/c-73_1-src-3575e21c7c.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/vcpkg/downloads/icu4c-73_1-src.tgz
-- Applying patch disable-escapestr-tool.patch
-- Applying patch remove-MD-from-configure.patch
-- Applying patch fix_parallel_build_on_windows.patch
-- Applying patch fix-extra.patch
-- Applying patch mingw-dll-install.patch
-- Applying patch disable-static-prefix.patch
-- Applying patch fix-win-build.patch
-- Using source at C:/vcpkg/buildtrees/icu/src/c-73_1-src-3575e21c7c.clean
-- Found external ninja('1.10.2').
-- Getting CMake variables for x64-windows
-- Using cached msys2-autoconf-wrapper-20221207-1-any.pkg.tar.zst.
-- Using cached msys2-automake-wrapper-20221207-1-any.pkg.tar.zst.
-- Using cached msys2-binutils-2.40-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libtool-2.4.7-3-x86_64.pkg.tar.zst.
-- Using cached msys2-make-4.4.1-1-x86_64.pkg.tar.zst.
-- Using cached msys2-pkgconf-1.9.4-1-x86_64.pkg.tar.zst.
-- Using cached msys2-which-2.21-4-x86_64.pkg.tar.zst.
-- Using cached msys2-autoconf-archive-2022.09.03-1-any.pkg.tar.zst.
-- Using cached msys2-bash-5.2.015-1-x86_64.pkg.tar.zst.
-- Using cached msys2-coreutils-8.32-5-x86_64.pkg.tar.zst.
-- Using cached msys2-file-5.44-5-x86_64.pkg.tar.zst.
-- Using cached msys2-gawk-5.2.1-2-x86_64.pkg.tar.zst.
-- Using cached msys2-grep-1~3.0-6-x86_64.pkg.tar.zst.
-- Using cached msys2-gzip-1.12-2-x86_64.pkg.tar.zst.
-- Using cached msys2-diffutils-3.9-1-x86_64.pkg.tar.zst.
-- Using cached msys2-sed-4.9-1-x86_64.pkg.tar.zst.
-- Using cached msys2-msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst.
-- Using cached msys2-autoconf2.71-2.71-1-any.pkg.tar.zst.
-- Using cached msys2-automake1.16-1.16.5-1-any.pkg.tar.zst.
-- Using cached msys2-libiconv-1.17-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libintl-0.21-2-x86_64.pkg.tar.zst.
-- Using cached msys2-zlib-1.2.13-1-x86_64.pkg.tar.zst.
-- Using cached msys2-tar-1.34-3-x86_64.pkg.tar.zst.
-- Using cached msys2-findutils-4.9.0-3-x86_64.pkg.tar.zst.
-- Using cached msys2-gmp-6.2.1-2-x86_64.pkg.tar.zst.
-- Using cached msys2-gcc-libs-11.3.0-3-x86_64.pkg.tar.zst.
-- Using cached msys2-libbz2-1.0.8-4-x86_64.pkg.tar.zst.
-- Using cached msys2-liblzma-5.4.1-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libzstd-1.5.4-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libreadline-8.2.001-3-x86_64.pkg.tar.zst.
-- Using cached msys2-mpfr-4.2.0-2-x86_64.pkg.tar.zst.
-- Using cached msys2-libpcre-8.45-3-x86_64.pkg.tar.zst.
-- Using cached msys2-m4-1.4.19-2-x86_64.pkg.tar.zst.
-- Using cached msys2-perl-5.36.0-1-x86_64.pkg.tar.zst.
-- Using cached msys2-ncurses-6.4-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libcrypt-2.1-4-x86_64.pkg.tar.zst.
-- Using msys root at C:/vcpkg/downloads/tools/msys2/87962f0d86055c95
CMake Warning at scripts/cmake/vcpkg_configure_make.cmake:269 (message):
Unable to find system dir in the PATH variable! Appending required msys
paths!
Call Stack (most recent call first):
ports/icu/portfile.cmake:54 (vcpkg_configure_make)
scripts/ports.cmake:168 (include)
-- Generating configure for x64-windows
-- Finished generating configure for x64-windows
-- Using cached mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst.
-- Using cached msys2-msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst.
-- Using msys root at C:/vcpkg/downloads/tools/msys2/6f3fa1a12ef85a6f
-- Configuring x64-windows-dbg
-- Configuring x64-windows-rel
-- Building x64-windows-dbg
-- Installing x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: C:/vcpkg/downloads/tools/msys2/87962f0d86055c95/usr/bin/make.exe -j 17 --trace -f Makefile install DESTDIR=/C/vcpkg/packages/icu_x64-windows
Working Directory: C:/vcpkg/buildtrees/icu/x64-windows-dbg/
See logs for more information:
C:\vcpkg\buildtrees\icu\install-x64-windows-dbg-out.log
C:\vcpkg\buildtrees\icu\install-x64-windows-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_make.cmake:168 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_make.cmake:2 (vcpkg_build_make)
ports/icu/portfile.cmake:144 (vcpkg_install_make)
scripts/ports.cmake:168 (include)
error: building icu:x64-windows failed with: BUILD_FAILED
Elapsed time to handle icu:x64-windows: 6.5 min
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+icu
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[icu]+Build+error&body=Copy+issue+body+from+C%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md
Additional context
This error has already been fixed in the https://github.com/microsoft/vcpkg/issues/32711
This error has already been fixed in the https://github.com/microsoft/vcpkg/issues/32711
Does PR https://github.com/microsoft/vcpkg/pull/32750 resolve your issue?
This error has already been fixed in the https://github.com/microsoft/vcpkg/issues/32711
Does PR #32750 resolve your issue?
I'm seeing this as well in 2023.08.09 which should have that PR unfortunately.
The last test of the installation of the ICU package this week led to the error again. I can't build my project because of this.
I have a tentative fix in my pull request. Hopefully it also works for you.
I tested that on myself. It works. Thanks on flmmkch
|
2025-04-01T06:39:35.894239
| 2023-11-02T11:38:31
|
1974062984
|
{
"authors": [
"amasciotta",
"jimwang118"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8434",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/34869"
}
|
gharchive/issue
|
[libressl] No .cmake files inside the share directory after vcpkg install
Describe the bug
find_package(LibreSSL) fails because the port has no .cmake file inside its share deployment folder.
Environment
OS: Windows
Compiler: MSVC 19.37.32825.0
To Reproduce
I'm using vcpkg in manifest mode.
Create a vcpkg.json with this content:
{
"$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
"dependencies": [
"libressl"
]
}
Create a CMakeLists.txt with this content:
project(MyProj CXX)
find_package(LibreSSL REQUIRED)
After generating the CMake cache, the output is:
1> CMake generation started for default configuration: 'x64-Debug'.
1> Found and using vcpkg toolchain file (C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake).
1> Command line: "C:\Windows\system32\cmd.exe" /c "%SYSTEMROOT%\System32\chcp.com 65001 >NUL && "C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe" -G "Ninja" -DCMAKE_BUILD_TYPE:STRING="Debug" -DCMAKE_INSTALL_PREFIX:PATH="D:\Dev\libresslcmaketest\out\install\x64-Debug" -DCMAKE_C_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe" -DCMAKE_CXX_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe" -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe" -DCMAKE_TOOLCHAIN_FILE="C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake" "D:\Dev\libresslcmaketest" 2>&1"
1> Working directory: D:\Dev\libresslcmaketest\out\build\x64-Debug
1> [CMake] CMake Warning (dev) at CMakeLists.txt:1 (project):
1> [CMake] cmake_minimum_required() should be called prior to this top-level project()
1> [CMake] call. Please see the cmake-commands(7) manual for usage documentation of
1> [CMake] both commands.
1> [CMake] This warning is for project developers. Use -Wno-dev to suppress it.
1> [CMake]
1> [CMake] -- Running vcpkg install
1> [CMake] Detecting compiler hash for triplet x64-windows...
1> [CMake] All requested packages are currently installed.
1> [CMake] Total install time: 300 ns
1> [CMake] -- Running vcpkg install - done
1> [CMake] CMake Error at C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package):
1> [CMake] By not providing "FindLibreSSL.cmake" in CMAKE_MODULE_PATH this project has
1> [CMake] asked CMake to find a package configuration file provided by "LibreSSL",
1> [CMake] but CMake did not find one.
1> [CMake]
1> [CMake] Could not find a package configuration file provided by "LibreSSL" with any
1> [CMake] of the following names:
1> [CMake]
1> [CMake] LibreSSLConfig.cmake
1> [CMake] libressl-config.cmake
1> [CMake]
1> [CMake] Add the installation prefix of "LibreSSL" to CMAKE_PREFIX_PATH or set
1> [CMake] "LibreSSL_DIR" to a directory containing one of the above files. If
1> [CMake] "LibreSSL" provides a separate development package or SDK, be sure it has
1> [CMake] been installed.
1> [CMake] Call Stack (most recent call first):
1> [CMake] CMakeLists.txt:3 (find_package)
1> [CMake] CMake Warning (dev) in D:\Dev\libresslcmaketest\CMakeLists.txt:
1> [CMake] No cmake_minimum_required command is present. A line of code such as
1> [CMake]
1> [CMake] cmake_minimum_required(VERSION 3.26)
1> [CMake]
1> [CMake] should be added at the top of the file. The version specified may be lower
1> [CMake] if you wish to support older CMake versions for this project. For more
1> [CMake] information run "cmake --help-policy CMP0000".
1> [CMake] This warning is for project developers. Use -Wno-dev to suppress it.
1> [CMake]
1> [CMake] -- Configuring incomplete, errors occurred!
1> 'C:\Windows\system32\cmd.exe' '/c "%SYSTEMROOT%\System32\chcp.com 65001 >NUL && "C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe" -G "Ninja" -DCMAKE_BUILD_TYPE:STRING="Debug" -DCMAKE_INSTALL_PREFIX:PATH="D:\Dev\libresslcmaketest\out\install\x64-Debug" -DCMAKE_C_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe" -DCMAKE_CXX_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe" -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe" -DCMAKE_TOOLCHAIN_FILE="C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake" "D:\Dev\libresslcmaketest" 2>&1"' execution failed with error: ''C:\Windows\system32\cmd.exe' '/c "%SYSTEMROOT%\System32\chcp.com 65001 >NUL && "C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe" -G "Ninja" -DCMAKE_BUILD_TYPE:STRING="Debug" -DCMAKE_INSTALL_PREFIX:PATH="D:\Dev\libresslcmaketest\out\install\x64-Debug" -DCMAKE_C_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe" -DCMAKE_CXX_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe" -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe" -DCMAKE_TOOLCHAIN_FILE="C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake" "D:\Dev\libresslcmaketest" 2>&1"' returned with exit code: 1'.
Moreover, if you check the share folder inside the libressl port, you'll see that there is no LibreSSLConfig.cmake file inside it. Actually, there is no .cmake file at all.
I'll try to add usage.
|
2025-04-01T06:39:35.905104
| 2024-11-12T21:03:23
|
2653324102
|
{
"authors": [
"FrankXie05",
"InfiniteLoopGameDev",
"dg0yt",
"smile-zyk"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8435",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/42128"
}
|
gharchive/issue
|
[vulkan-validationlayers] ErrorOutOfHostMemory when run
Description
When running a vulkan project that loads validation layers, I am unable to successfully create an instance due to an ErrorOutOfHostMemory exception
Environment
OS: Windows (MinGW)
IDE: CLion
Compiler: g++ 14.2 / clang++ 19.1.3 (Tried both)
To Reproduce
Steps to reproduce the behavior:
./vcpkg install vulkan-validationlayers
Set VK_ADD_LAYER_PATH=@layer_path@
Run program with vulkan validation layers
See error vk::createInstance: ErrorOutOfHostMemory
Expected behavior
The program successfully loads the validation layers
Additional context
Using system installed Vulkan SDK the error is not present on the same build (running the exe directly without setting VK_ADD_LAYER_PATH)
Set VK_ADD_LAYER_PATH=@layer_path@
What did you actually do in this step?
Set VK_ADD_LAYER_PATH=@layer_path@
What did you actually do in this step?
I set as VK_ADD_LAYER_PATH=vcpkg_installed\x64-mingw-dynamic\bin
I have also set it to the absolute path with the same result
@InfiniteLoopGameDev Could you please try x64-windows?
I am able to confirm that it is specifically vulkan-validationlayers; by replacing the DLL in vcpkg_installed\x64-mingw-dynamic\bin by the one that is provided by the vulkan SDK without actually installing the DLL.
I have also tried using the debug version by setting it to VK_ADD_LAYER_PATH=vcpkg_installed\x64-mingw-dynamic\debug\bin. That gave me the following output:
mimalloc-redirect: error: unable to find target module.
mimalloc-redirect: warning: standard malloc is _not_ redirected! -- using regular malloc/free. (v1.1c)
mimalloc: assertion failed: at "C:/Users/<username>/.vcpkg-clion/vcpkg/buildtrees/mimalloc/src/v2.1.7-7cda0129ba.clean/src/options.c":264, mi_add_stderr_output
assertion: "mi_out_default == NULL"
I'm having the same issue when i use mingw
I'm having the same issue when i use mingw
@smile-zyk Have you tried with Visual Studio / x64-windows? If, so does it give you the same issue?
After much trouble of trying to get WSL2 to work. I have successfully compiled and ran my code with WSL2. So the problem seems to come from Windows
I also tried x64-windows-static which also worked (the test on WSL was x64-linux-dynamic) but x64-mingw-static. I now don't know what is happening. It might be that vulkan-validationlayers might not be able to find its dependencies at runtime on Windows host
but x64-mingw-static. I now don't know what is happening.
Maybe https://github.com/microsoft/mimalloc/issues/542? There is "redirect: unable to find module".
BTW does x64-mingw-dynamic work?
BTW does x64-mingw-dynamic work?
Sadly, No
|
2025-04-01T06:39:35.908923
| 2019-08-14T08:22:33
|
480545676
|
{
"authors": [
"JackBoosY",
"lanyizi",
"mmhatami"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8436",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/7676"
}
|
gharchive/issue
|
[easyhook] support static build
Library name: easyhook
Library description:
Source repository URL: https://github.com/EasyHook/EasyHook
Project homepage (if different from the source repository):
Please Add static easyhook library
@JackBoosY thanks
please support static build of easyhook @JackBoosY
Blocked by #260 #138.
Besides static build, it's also desirable to have a dynamic version of EasyHook that is available when using static triplets.
Injected DLLs often needs to be self-contained (it should not reference any 3rd party DLLs) because the dependencies of injected DLL is usually not inside the target process's DLL search path. Linking to (the dynamic version of) EasyHook will be fine, because EasyHook will load itself into the target process beforehand.
This means we need to build our library with the static triplet, but currently EasyHook cannot be installed using static triplet..
Close this PR until upstream fixes this.
|
2025-04-01T06:39:35.917203
| 2019-11-07T15:04:15
|
519322574
|
{
"authors": [
"JackBoosY",
"SallySoul",
"timautry",
"xarthurx"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8437",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/8942"
}
|
gharchive/issue
|
[suitesparse[metis]] build failure
Host Environment
OS: Windows
Compiler: revision
To Reproduce
Steps to reproduce the behavior:
./vcpkg install suitesparse[metis] --recurse
Failure logs
The following packages will be built and installed:
* metis[core]:x64-windows
suitesparse[core,metis]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/2: metis:x64-windows
Building package metis[core]:x64-windows...
-- Note: metis only supports static library linkage. Building static library.
-- Downloading http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-5.1.0.tar.gz...
-- Downloading http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-5.1.0.tar.gz... Failed. Status: 6;"Couldn't resolve host name"
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:175 (message):
Failed to download file.
If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY environment
variables to "https://user:password@your-proxy-ip-address:port/".
Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues
Call Stack (most recent call first):
ports/metis/portfile.cmake:8 (vcpkg_download_distfile)
scripts/ports.cmake:94 (include)
Error: Building package metis:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: metis:x64-windows
Vcpkg version: 2019.09.12-nohash
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
related to: https://github.com/microsoft/vcpkg/issues/8336
@xarthurx Normally this error means either they are behind a proxy or the download site vcpkg is trying to download the file from is unavailable...
I just tried to contact the download site "http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-5.1.0.tar.gz" to see if it would download the file to my pc but I get an error:
This site can't be reached
glaros.dtc.umn.edu's server IP address could not be found.
ERR_NAME_NOT_RESOLVED
So the site may indeed be down or has been taken offline.
Seems it's site has problem. Please download this package and put it into VCPKG_PATH/downloads then rebuild suitesparse.
metis-5.1.0.tar.gz
Thanks.
@xarthurx Does this issue solved?
@JackBoosY Yes. I'll close it now. Thanks for the help.
I think we can still fix this issue long term though. (I just had this failure again since this site seems to be down again.)
METIS is now distributed via github:
https://github.com/KarypisLab/METIS
However, the previously included GKLib library is not a sub module, so that would also need to be added:
https://github.com/KarypisLab/GKlib
Some changes have been made so the patches we currently have will not apply anymore. I will try and get a PR together, but wanted to make sure this was in a comment somewhere.
|
2025-04-01T06:39:35.944938
| 2019-11-27T08:19:53
|
529187694
|
{
"authors": [
"AlvinZhangH",
"Cheney-W",
"MonicaLiu0311",
"PhoebeHui",
"dg0yt",
"toboRlivE"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8438",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/issues/9109"
}
|
gharchive/issue
|
[fmt] build failure while cygwin is installed and having a PATH variable to it
Host Environment
OS: Win 10
Compiler: Vcpkg version: 2019.09.12-nohash
To Reproduce
Steps to reproduce the behavior:
.\vcpkg.exe install fmt
Failure logs
PS C:\dev\tools\vcpkg> .\vcpkg.exe install fmt
The following packages will be built and installed:
fmt[core]:x86-windows
Starting package 1/1: fmt:x86-windows
Building package fmt[core]:x86-windows...
-- Downloading https://github.com/fmtlib/fmt/archive/6.0.0.tar.gz...
CMake Error at C:/dev/tools/vcpkg/scripts/cmake/vcpkg_download_distfile.cmake:185 (file):
file RENAME failed to rename
/cygdrive/c/dev/tools/vcpkg/C:/dev/tools/vcpkg/downloads/temp/fmtlib-fmt-6.0.0.tar.gz
to
/cygdrive/c/dev/tools/vcpkg/C:/dev/tools/vcpkg/downloads/fmtlib-fmt-6.0.0.tar.gz
because: No such file or directory
Call Stack (most recent call first):
C:/dev/tools/vcpkg/scripts/cmake/vcpkg_from_github.cmake:132 (vcpkg_download_distfile)
C:/dev/tools/vcpkg/ports/fmt/portfile.cmake:2 (vcpkg_from_github)
C:/dev/tools/vcpkg/scripts/ports.cmake:94 (include)
Error: Building package fmt:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: fmt:x86-windows
Vcpkg version: 2019.09.12-nohash
Additionally, attach any relevant sections from the log files above.
PS C:\dev\tools\vcpkg> .\vcpkg update
Using local portfile versions. To update the local portfiles, use git pull.
No packages need updating.
Additional context
PS was run as admin, 98GBs free on C:, I'll stand by for any requests for info.
x86-windows.vcpkg_abi_info.txt was created in a "C:\dev\tools\vcpkg\buildtrees\fmt" directory
Content of the file:
CONTROL 9cebf357c183e641caa402126ebc6d6688d1a771 portfile.cmake b2434022329236462cc9304b9e3c3a19ef69faa8 cmake 3.14.5 powershell ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0 vcpkg_fixup_cmake_targets 0ddb96472da00d45d10e0b0bf037bfb744164d0a triplet e8dc96fd479b53bb0e6748625827c8268017e35a features core
Looks like the cygdrive created a wierd directory for C:
`PS C:\dev\tools\vcpkg> ls
Directory: C:\dev\tools\vcpkg
Mode LastWriteTime Length Name
d----- 11/27/2019 3:01 AM .github
d----- 11/27/2019 3:06 AM buildtrees
d----- 11/27/2019 3:06 AM C
d----- 11/27/2019 3:01 AM docs
d----- 11/27/2019 3:06 AM downloads
d----- 11/27/2019 3:06 AM installed
d----- 11/27/2019 3:06 AM packages
d----- 11/27/2019 3:01 AM ports
d----- 11/27/2019 3:03 AM scripts
d----- 11/27/2019 3:03 AM toolsrc
d----- 11/27/2019 3:01 AM triplets
-a---- 11/27/2019 3:01 AM 8 .gitattributes
-a---- 11/27/2019 3:01 AM 5625 .gitignore
-a---- 11/27/2019 3:01 AM 0 .vcpkg-root
-a---- 11/27/2019 3:01 AM 100 bootstrap-vcpkg.bat
-a---- 11/27/2019 3:01 AM 109 bootstrap-vcpkg.sh
-a---- 11/27/2019 3:01 AM 368962 CHANGELOG.md
-a---- 11/27/2019 3:01 AM 2432 CONTRIBUTING.md
-a---- 11/27/2019 3:01 AM 1096 LICENSE.txt
-a---- 11/27/2019 3:01 AM 2334 NOTICE.txt
-a---- 11/27/2019 3:01 AM 4345 README.md
-a---- 11/27/2019 3:01 AM 3282 README_zh_CN.md
-a---- 11/27/2019 3:03 AM 1014272 vcpkg.exe`
The same thing just occurred for me while installing SDL2
OK, I already have an install of cygwin on my computer. I renamed the "c:\cygwin64" directory (which "C:\cygwin64\bin"i s in my PATH env) to "c:\cygwin64BAK" and all the packages install.
I don't know if it's because of cygwin being there, git, or the CMake in that install conflicting, but it looks like it has something to do with that. Should be enough for you guys to reproduce the issue.
Duplicated to #3205, #5856.
I don't know if you'd like me to edit the title of this issue, there is no problem installing fmt. My problem appears to be installing any package via vcpkg while cygwin is installed and having a PATH variable to it.
Also, I am not behind a proxy... Just FYI for setting up an environment to replicate.
Hi, @toboRlivE
You Can use Visual Studio 2019, not cygwin, link https://visualstudio.microsoft.com/zh-hans/vs/?rr=http%3A%2F%2Fwww.baidu.com%2Flink%3Furl%3DSVTex4JDby4HUtB3gxXDHqArrMBZVveLt-rW0hhxWp2B6Yr7zThG_Oyd8vLX72rg%26wd%3D%26eqid%3De1838db7000095d9000000065de47f03 Community 2019 is free.
Professionnal 2019 and Enterprise 2019 need to pay.
Thanks, I am using VS2019 already. I just have an install of cygwin on my computer previously, and when I installed and started using vcpkg, I came across that issue. I read through a few of the issues that seem to have the same symptoms, so I added as much detail as I could so you could replicate the problem.
I don't think this is a port bug, I'm pretty sure it has to do with vcpkg internals conflicting with cygwin being in my PATH env. Just wanted to leave a reminder that if I mangle the path to my cygwin install, or remove the PATH variable, vcpkg installs packages with no problem. I don't know how to change the tag on this issue.
Would you like me to change the Label or Title of the issue?
@toboRlivE, thanks for reporting this issue and providing us details about this issue! We will try to repro it.
Confirmed, this issue caused by using cmake under cygwin.
Repro steps:
git clone https://github.com/microsoft/vcpkg
./bootstrap-vcpkg.bat
Installed cygwin(select cmake)
Add C:\cygwin64\bin to PATH
./vcpkg install fmt
VCPKG try to find cmake that installed by system first, if it doesn't exist, it will download a new one. If it exist, then it will use that one. Using cmake under cygwin looks has some issues here.
This issue current disappears in the latest vcpkg(2021-08-03-1a6d67b8150e94b7f473c6ab1c0cfd), it's due to the camke version used in vcpkg(3.20.2) is large than the version of cygwin(3.20.0), If set the cmake version used by vcpkg to 3.20.0, this issue will appear again.
Oh, I should record this issue number, given the many duplicate issues.
The cygwin cmake needs to be recognized. IIRC one indicator is the list of generators. @Cheney-W can you share the output of cmake -G for cygwin's cmake?
C:\cygwin64\bin>cmake.exe -G
CMake Error: No generator specified for -G
Generators
* Unix Makefiles = Generates standard UNIX makefiles.
Ninja = Generates build.ninja files.
Ninja Multi-Config = Generates build-<Config>.ninja files.
CodeBlocks - Ninja = Generates CodeBlocks project files.
CodeBlocks - Unix Makefiles = Generates CodeBlocks project files.
CodeLite - Ninja = Generates CodeLite project files.
CodeLite - Unix Makefiles = Generates CodeLite project files.
Eclipse CDT4 - Ninja = Generates Eclipse CDT 4.0 project files.
Eclipse CDT4 - Unix Makefiles= Generates Eclipse CDT 4.0 project files.
Kate - Ninja = Generates Kate project files.
Kate - Unix Makefiles = Generates Kate project files.
Sublime Text 2 - Ninja = Generates Sublime Text 2 project files.
Sublime Text 2 - Unix Makefiles
= Generates Sublime Text 2 project files.
Thanks! This confirms that there are no Windows generators (not even MinGW). IIRC this identical with the cmake in the msys subsystem of MSYS2. I will verify this later, on a Windows machine.
The latest vcpkg currently uses CMake 3.30.1.
PS E:\vcpkg> ./vcpkg version
vcpkg package management program version 2024-11-12-eb492805e92a2c14a230f5c3deb3e89f6771c321
See LICENSE.txt for license information.
The latest cygwin version is 3.5.4, which includes three optional CMake versions: 3.28.3, 3.25.3, 3.23.2.
Whenever I intentionally make the CMake version in vcpkg the same as in cygwin, I get an error. Currently I have tried CMake 3.28.3 and CMake 3.25.3, both give the following error:
PS E:\vcpkg> ./vcpkg install fmt
Computing installation plan...
The following packages will be built and installed:
<EMAIL_ADDRESS>Detecting compiler hash for triplet x64-windows...
error: while detecting compiler information:
The log file content at "E:\vcpkg\buildtrees\detect_compiler\stdout-x64-windows.log" is:
CMake Error at E:/vcpkg/scripts/ports.cmake:143 (message):
Cannot find port:
Directory does not exist: E;/vcpkg/scripts/detect_compiler
error: vcpkg was unable to detect the active compiler's information. See above for the CMake failure output.
If the CMake versions are inconsistent, the installation is successful.
The Cygwin environment, as the derived MSYS2 environment, is a POSIX-like runtime, not a Windows-like runtime. That's why Cygwin CMake uses POSIX path separator (/), POSIX path list separators (:), and POSIX paths (/C/Windows). This is incompatible by purpose. It is meant for buildings programs which are completely unaware of Windows.
IIRC these versions of CMake also come without Visual Studio generators, so they are easy to detect with cmake -G. This was elaborated in a previous issue.
This is a frequent issue. The vcpkg team should really improve the diagnostics for this case. All information is readily available.
|
2025-04-01T06:39:35.949278
| 2021-05-28T07:52:30
|
904884451
|
{
"authors": [
"NancyLi1013",
"mcmtroffaes",
"strega-nil-ms"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8439",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/18169"
}
|
gharchive/pull-request
|
[libssh] disable gssapi
What does your PR fix?
The .pc file of libssh does not add the appropriate linking flags for gssapi when it is found as a system library on linux or osx. This patch disables the feature so libssh can still be linked against on those platforms. Potential fix for Fixes #18166.
Which triplets are supported/not supported? Have you updated the CI baseline?
No changes.
Does your PR follow the maintainer guide?
Yes, to the best of my knowledge.
Yes.
Thanks for your fixing @mcmtroffaes.
Thanks @mcmtroffaes !
|
2025-04-01T06:39:35.953524
| 2021-09-14T15:18:43
|
996143784
|
{
"authors": [
"BillyONeal",
"SamuelMarks"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8440",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/20156"
}
|
gharchive/pull-request
|
[Guilite] Add new port
Describe the pull request
The smallest header-only GUI library (4 KLOC) for all platforms.
https://github.com/idea4good/GuiLite
What does your PR fix?
New port
Which triplets are supported/not supported? Have you updated the CI baseline?
All
Does your PR follow the maintainer guide?
Yes
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/
Thanks for the new port!
|
2025-04-01T06:39:35.958271
| 2023-12-06T02:42:02
|
2027537739
|
{
"authors": [
"BillyONeal",
"Cheney-W"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8441",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/35520"
}
|
gharchive/pull-request
|
[rtaudio] update to 6.0.1
Fixes https://github.com/microsoft/vcpkg/issues/35504
Features passed with following triplets:
x86-windows
x64-windows
x64-windows-static
[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.
/azp run
Thanks for the update!
|
2025-04-01T06:39:35.961680
| 2024-09-17T03:16:16
|
2529890499
|
{
"authors": [
"BillyONeal",
"c8ef"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8442",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/41012"
}
|
gharchive/pull-request
|
[rocksdb] update to 9.6.1
[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] When updating the upstream version, the "port-version" is reset (removed from vcpkg.json).
[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.
Thanks for the update!
|
2025-04-01T06:39:35.983558
| 2019-08-16T23:39:29
|
481820716
|
{
"authors": [
"BillyONeal",
"JackBoosY",
"Neumann-A",
"PhoebeHui",
"ras0219-msft"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8443",
"repo": "microsoft/vcpkg",
"url": "https://github.com/microsoft/vcpkg/pull/7733"
}
|
gharchive/pull-request
|
QoL: Buildtype variables for looping over buildtypes
While working on the qt scripts I often defined those variables below to avoid unnecessary code duplication to loop over the different buildtypes
TODO:
[ ] Rename VCPKG_BUILD_TRIPLET_* to something different ?
[ ] Remove VCPKG_BUILDTREE_TRIPLET_DIR_ ?
Thanks for the PR!
This in principle seems like it could be a useful abstraction, but I'd like to see it demonstrated in multiple contexts before merging.
Specifically, if it turns out to only be useful in Qt5, then it should be private to Qt5. However, if it can be used to make code significantly cleaner and clearer in more contexts, I'd like to see this PR introduce at least two of those refactorings.
TODO (only 2 of N):
[ ] Refactor vcpkg_build_cmake
[ ] Refactor vcpkg_build_msbuild
[ ] Refactor vcpkg_build_qmake
[ ] Refactor vcpkg_configure_cmake
[ ] Refactor vcpkg_configure_meson
[ ] Refactor vcpkg_configure_qmake
[ ] Refactor vcpkg_fixup_cmake_targets
[ ] Refactor vcpkg_install_meson (a bit short for a refactor, but consistency is important)
[ ] Refactor vcpkg_install_msbuild
[ ] Refactor an unknown number of ports which might benift from the PR (purely optional; but at least qt if the update to 5.12.4 PR is merged.)
Please resolve these conflicts.
Thanks.
Pinging @Neumann-A for response. Is work still being done for this PR?
@JackBoosY: You put the PR back into Draft?!?! I consider it finished for the time unless there is something which needs to ne fixed which I don't know of or you want some changes to it. Maybe run a full rebuild of everything to check if everything is working as intended.
@Neumann-A Sorry, my fault.
/azp run
Could you select some ports to test these functions?
hmm most regressions are failed due to download failures. The rest seems to be port build issues and not related to these changes.
Test result:
sdl2:x64-uwp: failed on master branch.
Waiting for other pipeline results...
Hmm from the whole list only two ports seem to be relevant which are:
seal:x64-linux : needs further investigate
libfabric:x64-windows-static : needs further investigate
I was able to build both successfully using this branch.
@Neumann-A Yep, I also can't repro that in my machine.
OMG...more and more different regressions...
[ ] osg:x64-linux
[ ] signalrclient:x64-linux
[ ] opencc:x64-linux
[ ] seal:x64-linux
[ ] xmsh:x64-osx
[ ] rply:x64-osx
[ ] seal:x64-osx
[ ] signalrclient:x64-osx
[ ] gmp:x64-osx
[ ] rply:x64-uwp
[ ] solid3:x64-uwp
[ ] protobuf:x64-uwp
[ ] signalrclient:x64-windows
[ ] seal:x64-windows
[ ] libaiff:x64-windows
[ ] monkeys-audio:x64-windows
[ ] rply:x64-windows
[ ] pdal:x64-windows
[ ] gmp:x64-windows
[ ] dmlc:x64-windows
[ ] icu:x64-windows
[ ] signalrclient:x64-windows-static
[ ] seal:x64-windows-static
[ ] dcmtk:x64-windows-static
[ ] icu:x64-windows-static
[ ] rply:x64-windows-static
[ ] pdal:x64-windows-static
[ ] gmp:x64-windows-static
[ ] zxing-cpp:x64-windows-static
[ ] libfabric:x64-windows-static
[ ] signalrclient:x86-windows
[ ] seal:x86-windows
[ ] monkeys-audio:x86-windows
[ ] gsoap:x86-windows
[ ] rply:x86-windows
[ ] pdal:x86-windows
[ ] gmp:x86-windows
[ ] icu:x86-windows
/azp run
This PR always seems to be the first one that triggers msys losing it ¯\_(ツ)_/¯
/azp run
Either the msys servers relied upon by some ports are broken causing CI failure, or something in this change causes CI to hang consistently.
This change depends on msys being fixed as in https://github.com/microsoft/vcpkg/pull/11443 or https://github.com/microsoft/vcpkg/pull/11471
@JackBoosY: None of those regressions look like they are caused by this PR. I assume some hidden unresolved dependencies in the ports which generate the errors in a full rebuild. (also see #11502 for comparison)
pdal: -> find_package issue. PostgreSQL::PostgreSQL in wrapper used without check if it actually exists.
@Neumann-A That's correct, I only want to know which port failed on the baseline.
@JackBoosY: Ah okay was just wondering due to the requires:author-response tag
/azp run
@Neumann-A pipelines are fixed, could you resolve the file conflict?
Thanks.
@JackBoosY: done
Can you merge the latest changes into this branch?
/azp run
/azp run
@Neumann-A, ocilib:x86-windows and ocilib:x64-windows failed with debug mode, I noticed it only build release mode before, the solution doesn't configure debug mode, could you help have a look?
"D:\buildtrees\ocilib\x86-windows-dbg\v4.6.4-271d6c24cf\proj\dll\ocilib_dll_vs2019.sln" (Rebuild target) (1) ->
(ValidateSolutionConfiguration target) ->
D:\buildtrees\ocilib\x86-windows-dbg\v4.6.4-271d6c24cf\proj\dll\ocilib_dll_vs2019.sln.metaproj : error MSB4126: The specified solution configuration "Debug|x86" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. [D:\buildtrees\ocilib\x86-windows-dbg\v4.6.4-271d6c24cf\proj\dll\ocilib_dll_vs2019.sln]
monkeys-audio regression will be fixed in another PR.
Closing this PR since it seems that no progress is being made. Please reopen if work is still being done.
|
2025-04-01T06:39:35.989889
| 2023-04-10T02:25:54
|
1660131921
|
{
"authors": [
"myintn02",
"ruiminwang"
],
"license": "CC-BY-4.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8444",
"repo": "microsoft/vscode-asa",
"url": "https://github.com/microsoft/vscode-asa/issues/96"
}
|
gharchive/issue
|
[Survey] User feedback
VSCode Version: 1.77.1,
Extension Version: 1.4.8,
OS: OSX
1. Overall, how would you rate your experience with the Stream Analytics Visual Studio Code Extension? Please rate us from 1 (poor) to 10 (excellent).
2. What do you like or dislike about the Stream Analytics Visual Studio Code Extension?
3. What improvements do you suggest for Stream Analytics Visual Studio Code Extension?
7 Have issue with docker image
good I like it for being user friendly but can be more intuitive
more clear visual understanding with interactive learning pattern for the new user, problem solving help when issues arise
What issues are you having when using Azure Stream Analytics extension?
|
2025-04-01T06:39:35.991928
| 2019-12-06T15:02:24
|
534054647
|
{
"authors": [
"ereeneid",
"nturinski"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8445",
"repo": "microsoft/vscode-azureappservice",
"url": "https://github.com/microsoft/vscode-azureappservice/issues/1325"
}
|
gharchive/issue
|
Azure Remote Debugging is currently only supported for Node.js apps on Linux.
Action: appService.StartRemoteDebug
Error type: Error
Error Message: Azure Remote Debugging is currently only supported for Node.js apps on Linux.
Version: 0.16.2
OS: win32
OS Release: 10.0.17763
Product: Visual Studio Code
Product Version: 1.40.2
Language: en
@ereeneid Thanks for reporting. If you're trying to remote debug, it's currently only supported on Node.js. What are you trying to remote debug?
|
2025-04-01T06:39:35.998244
| 2020-09-23T08:13:13
|
707148198
|
{
"authors": [
"chimerashashi",
"nturinski"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8446",
"repo": "microsoft/vscode-azurefunctions",
"url": "https://github.com/microsoft/vscode-azurefunctions/issues/2406"
}
|
gharchive/issue
|
Region issues
Does this occur consistently?
Repro steps:
Action: azureFunctions.createFunctionApp
Error type: Unauthorized
Error Message: The scale operation is not allowed for this subscription in this region. Try selecting different region or scale option.
Version: 0.24.1
OS: linux
OS Release: 5.4.0-47-generic
Product: Visual Studio Code
Product Version: 1.48.2
Language: en
Call Stack
new RestError extension.bundle.js:48:94460
extension.bundle.js:48:1291123
processTicksAndRejections task_queues.js:85:5
Please try creating your function app in a different region. If this still doesn't work, please provide detailed repro steps.
|
2025-04-01T06:39:36.004250
| 2022-02-24T18:40:25
|
1149624162
|
{
"authors": [
"AzCode-Bot",
"RaphaelSilv",
"nturinski"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8447",
"repo": "microsoft/vscode-azurefunctions",
"url": "https://github.com/microsoft/vscode-azurefunctions/issues/3053"
}
|
gharchive/issue
|
Debugging Azure Function with vscode
I've been struggling to debug an HttpTrigger type azure function with vscode.
My assumption is that the issue might be related to the config files within .vscode/ or at worst, my own environment.
As of now, when I try to debug a recently created function (func init) I get the following error from vscode:
> Executing task: dotnet clean /property:GenerateFullPaths=true /consoleloggerparameters:NoSummary <
execvp(3) failed.: Permission denied
The terminal process "dotnet 'clean', '/property:GenerateFullPaths=true', '/consoleloggerparameters:NoSummary'" failed to launch (exit code: 1)
Inside .vscode/ there 4 files:
├── extensions.json
├── launch.json
├── settings.json
└── tasks.json
and inside task.json there are a few dotnet related commands that are causing the error above.
Despite these files being automatically generated by core tools (func) I removed the dotnet lines from task.json and hit Debug.
After a few seconds I get:
Failed to detect running Functions host within "60" seconds. You may want to adjust the "azureFunctions.pickProcessTimeout" setting.
Is there any command to automatically generate the debug configuration? e.g. ".NET generate assets for build and debug"
Have you faced anything similar to it?
My env settings:
OS: Ubuntu 20.04.4 LTS
Code:1.64.2 x64
Azure Functions Extension: v1.6.0
Core Tools Version: 3.0.3904
RaphaelSilv Thanks for reporting! It looks like the dotnet clean command isn't able to run in its current directory due to user permissions.
The tasks.json is necessary to debug because we are looking for that task to attach to the process, so deleting it will cause some issues.
Replace the type from process to shell inside tasks.json solved it.
FWIW:
omnisharp-vscode #4556
Thanks for bringing this issue to our attention. Seems like this might be an upstream issue that we can't do anything about. Changing it to shell seems like it has some negative performance impacts, but it's worth to use this workaround until it can get resolved.
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-01T06:39:36.009000
| 2023-01-05T08:46:55
|
1520339128
|
{
"authors": [
"MicroFish91",
"v-xinda"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8448",
"repo": "microsoft/vscode-azurestorage",
"url": "https://github.com/microsoft/vscode-azurestorage/issues/1192"
}
|
gharchive/issue
|
[Suggestion] It would be better to change the "Downloaded to 'Users/...'. Succeeded" to the "Download to 'Users/...'. Succeeded" in the Azure: Activity Log window
OS: Win10
Build Version: 20230104.1
Regression: Not a regression
Repro Steps:
Expand a storage account -> Expand a blob container-> Right click a file/folder -> Click "Download...".
Check the log message in the Azure: Activity Log window.
Actual:
Show the "Downloaded to 'Users/...'. Succeeded" in the Azure: Activity Log window.
Suggestion;
It would be better to change the "Downloaded to 'Users/...'. Succeeded" to the "Download to 'Users/...'. Succeeded" in the Azure: Activity Log window.
More Info:
This issue doesn't reproduce after uploading a file/folder.
We should remove the 'ed' from 'downloaded' and also remove the extra period as well.
|
2025-04-01T06:39:36.021791
| 2019-11-09T00:08:08
|
520291565
|
{
"authors": [
"CarloWood",
"bobbrow",
"thomthom"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8449",
"repo": "microsoft/vscode-cmake-tools",
"url": "https://github.com/microsoft/vscode-cmake-tools/issues/892"
}
|
gharchive/issue
|
message(DEBUG "...") doesn't display in VSCode output?
Brief Issue Summary
While working on my projects I added some message(DEBUG "...") statements. I also set "cmake.loggingLevel": "debug".
Expected:
What I expected to see was the message statements from DEBUG and above.
Apparent Behavior:
What I do see is that there is some extra info the the VSCode Output [driver] messages etc. But none of the message(DEBUG "...") statements.
If I use message(STATUS "...") then I do see the messages.
Have I misinterpreted the cmake.loggingLevel settings? Is that not controlling the log level of CMake when it runs?
CMake Tools Log
[driver] Start configure
[driver] Runnnig pre-configure checks and steps
[driver] Run _refreshExpansions
[cms-driver] Run doRefreshExpansions
[driver] Run _refreshExpansions cb
[cmake] Configuring done
[cmake] CMake Deprecation Warning:
[cmake] The 'cmake-server(7)' is deprecated. Please port clients to use the
[cmake] 'cmake-file-api(7)' instead.
[cmake]
[cmake]
[cmake] Generating done
[cache] Reading CMake cache file c:/Users/Thomas/SourceTree/traceup/cext/build/Release/CMakeCache.txt
[cache] Parsing CMake cache string
[extension] [1947] cmake.configure finished (returned 0)
[kit] OK running C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat amd64, env vars: undefined
Platform and Versions
Operating System: Windows 10
CMake Version: 3.15.4
VSCode Version: 1.40.0
CMake Tools Extension Version: 1.2.1
Compiler/Toolchain: Visual C++ 2019
Sorry, I meant to respond to this earlier, but lost track of it. YOu shouldn't need to set cmake.loggingLevel to Debug to make this work because it is controlled by a different mechanism.
This works for me in 3.14, but it didn't work for me in 3.15. It could be a CMake bug, but I haven't had the time to try a lot of different configurations.
CMakeLists.txt
project(foo)
add_executable(foo src/1.cpp)
message(DEBUG "debug message")
Output
[cmake] DEBUGdebug message
[cmake] Configuring done
[cmake] Generating done
Gotcha. I recently upgraded to CMake 3.15 because of some good new features/improvement in that version.
So is the message type being mapped to VSCode's Output types?
but it didn't work for me in 3.15. It could be a CMake bug, but I haven't had the time to try a lot of different configurations.
I didn't even try this with cmake directly from the terminal. After I set up CMake Tools I've exclusively done everything from VSCode. (Great extension btw!)
Add to CMakeLists.txt:
# Use cmake --log-level=debug to get debug output.
set( CMAKE_MESSAGE_LOG_LEVEL "STATUS" )
The latter is the default, which you can change on the command line.
Can I also use cmake.configureArgs for this?
I've tried with
"cmake.configureArgs": [
"--log-level=DEBUG"
],
And that didn't seem to yield any message(DEBUG ...) messages.
"cmake.buildArgs": [
"--log-level=DEBUG"
],
This will lead to an error [build] ninja: fatal: -l parameter not numeric: did you mean -l 0.0?
Is there any way to control the warning level for CMake via CMakeTools that doesn't require editing CMakeList.txt files?
Ah! After updating to CMake 3.16 the above worked as expected. Must be 3.15 being bugged.
Why are you CC-ing me?
On Mon, 23 Mar 2020 09:47:13 -0700
Thomas Thomassen<EMAIL_ADDRESS>wrote:
I've tried with
"cmake.configureArgs": [
"--log-level=DEBUG"
],
And that didn't seem to yield any message(DEBUG ...) messages.
"cmake.buildArgs": [
"--log-level=DEBUG"
],
This will lead to an error [build] ninja: fatal: -l parameter not numeric: did you mean -l 0.0?
Is there any way to control the warning level for CMake via
CMakeTools that doesn't require editing CMakeList.txt files?
--
Carlo Wood<EMAIL_ADDRESS>
I wasn't, I'm replying to the issue via GitHub. Must be the notification system from GitHub.
That's great! I'll close the issue.
|
2025-04-01T06:39:36.023914
| 2024-11-22T20:00:37
|
2684413571
|
{
"authors": [
"SWCurragh",
"TylerLeonhardt"
],
"license": "CC-BY-4.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8450",
"repo": "microsoft/vscode-copilot-release",
"url": "https://github.com/microsoft/vscode-copilot-release/issues/2788"
}
|
gharchive/issue
|
Owner
Copilot Chat Extension Version:
VS Code Version:
OS Version:
Logs:
Steps to Reproduce:
Please elaborate
|
2025-04-01T06:39:36.028580
| 2020-05-19T09:08:13
|
620810289
|
{
"authors": [
"EricJizbaMSFT",
"MANakib"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8451",
"repo": "microsoft/vscode-cosmosdb",
"url": "https://github.com/microsoft/vscode-cosmosdb/issues/1472"
}
|
gharchive/issue
|
Deployment issue on VSCode cosmosDB
Repro steps:
Action: cosmosDB.createAccount
Error type: ServiceUnavailable
Error Message: Long running operation failed with error: "Sorry, we are currently experiencing high demand in this region, and cannot fulfill your request at this time. We work continuously to bring more and more capacity online, and encourage you to try again shortly. Please do not hesitate to contact us via Azure support at any time or for any reason using this link http://aka.ms/azuresupport.
ActivityId: 38e053a4-0790-4844-b951-565cf5f5aaf8, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0,...
Version: 0.12.2
OS: win32
Product: Visual Studio Code
Product Version: 1.45.1
Language: en
Unfortunately our extension in VS Code can't do anything if there's no availability in Azure. This could be related to high demand during the build conference, but I'm purely speculating. I recommend trying a different region, trying again later, or contact Azure support as linked in the error message above.
|
2025-04-01T06:39:36.090919
| 2022-05-18T21:10:42
|
1240535118
|
{
"authors": [
"bamurtaugh",
"kforeverisback",
"worldofgeese"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8452",
"repo": "microsoft/vscode-dev-containers",
"url": "https://github.com/microsoft/vscode-dev-containers/pull/1456"
}
|
gharchive/pull-request
|
Add devcontainer definition for k3d kubernetes cluster (minikube alternative)
Description
Add a new devcontainer definition for k3d kubernetes cluster.
With this, user will be able to create a new devcontainer which will enable the creation of a local kubernetes cluster (automated or manual).
This PR is based off of kubernetes-helm-minikube dev container.
PR Checklist
[X] I have updated the documentation accordingly.
[X] Added README.md describing the container
[X] Added sample nginx deployment document in README.md
[X] I have added/updated tests to cover my changes.
[X] Changed test.sh under test-project directory
[X] All new and existing tests passed.
[X] My code follows the code style of this project.
[X] I have checked to ensure there aren't other open Pull Requests for the same update/change.
[ ] Lint checker not integrated but fixed most Markdown lint errors (followed existing container document format)
Does this introduce a breaking change?
[ ] Yes
[X] No
Testing
[X] Manually created Codespaces from .devcontainer
[X] Provisioned a k3d cluster from terminal
[X] Automatically provisioned k3d cluster in postStartCommand
[X] Manually created local devcontainer
[X] Provisioned a k3d cluster from terminal afterwards
[X] Automatically provisioned k3d cluster in postStartCommand
[X] Manually applied pods/deployments to verify k3d cluster
References
Reference: https://github.com/microsoft/vscode-dev-containers/issues/1455
@iamnicoj @sivamu @juzuluag
@bamurtaugh can you please clarify what this means in practice? As an end user I see a PR that's open and ready to merge. Are user-contributed devcontainer features frozen from being accepted into main? What should end users of these features do in the meantime? I would appreciate a functional alternative in the interim.
Thanks again for opening this PR!
As a heads up, our team has been actively focused on an updated plan for community contributions and this repo moving forward, which we've now outlined in this issue: https://github.com/microsoft/vscode-dev-containers/issues/1589. This includes moving to a couple new repos for images (https://github.com/devcontainers/images) and Features (https://github.com/devcontainers/features).
We anticipate to have a similar repo and distribution process for templates/definitions. We'll keep everyone updated (likely via another issue in this repo or comment on https://github.com/microsoft/vscode-dev-containers/issues/1589) when our new templates repo is available and the process is defined.
Please let me know if you have any questions, thank you!
|
2025-04-01T06:39:36.120296
| 2022-09-20T05:34:48
|
1378844149
|
{
"authors": [
"DonJayamanne"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8453",
"repo": "microsoft/vscode-jupyter",
"url": "https://github.com/microsoft/vscode-jupyter/issues/11408"
}
|
gharchive/issue
|
Broken test 'Import pandas and goto it:'
https://github.com/microsoft/vscode-jupyter/actions/runs/3086711973/jobs/4991343761
Error: Waiting for editor to switch
+ expected - actual
at Timeout.<anonymous> (src/test/common.ts:59:20)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
@IanMatthewHuff looks like this test is consistently failing, will be disabling this test.
No longer an issue.
|
2025-04-01T06:39:36.123244
| 2022-11-14T19:15:58
|
1448605394
|
{
"authors": [
"Tyriar"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8454",
"repo": "microsoft/vscode-jupyter",
"url": "https://github.com/microsoft/vscode-jupyter/issues/12023"
}
|
gharchive/issue
|
Why do we use msrCrypto?
It was added here: https://github.com/microsoft/vscode-jupyter/pull/11263
The library is huge at 343KB, src/notebooks is 490KB for comparison. It also says:
It is recommended that this library be used as a polyfill for the native Web Crypto API supported in modern browsers. It is strongly advised that you used the native browser crypto whenever available. It will be more thoroughly tested, more secure, and have significantly better performance.
...
var crypto = window.crypto /*native*/ || window.msCrypto /*IE11 native*/ || window.msrCrypto; /*polyfill*/
This advice isn't followed, we actually recommend the opposite here? (note that msrCrypto is used regardless of which call from crypto is used.
https://github.com/microsoft/vscode-jupyter/blob/2482391980596b07d958e5fe15b3b2afd684eaab/src/platform/common/crypto.ts#L10-L18
If we must use it, could we switch to fetching it via a CDN only when a polyfill is needed?
Some more information in PRs or a link to issues would have been useful here, the PR doesn't address why this was introduced
|
2025-04-01T06:39:36.127767
| 2021-04-28T15:32:59
|
870323244
|
{
"authors": [
"RMacfarlane",
"kieferrm",
"misolori"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8455",
"repo": "microsoft/vscode-pull-request-github",
"url": "https://github.com/microsoft/vscode-pull-request-github/issues/2695"
}
|
gharchive/issue
|
"Greyed out text" in the input box
Testing microsoft/vscode#122243
The text in the input box for the PR title looks like it's greyed out. This mislead me for example to assume that the pre-filled in title is a placeholder and not an actual string.
Interestingly, these inputs are already using var(--vscode-input-foreground) as the color which matches other inputs in VS Code. The vscode-dropdown-foreground color which the selects are using appears to be a bit different and higher contrast. @misolori do you think we should align these colors?
I think this just varies by theme, for example the GH Light theme shows both text as the same colors, though it looks like the placeholder text is not using any color token?
Updated the placeholder text color to use the vscode theme token for it
|
2025-04-01T06:39:36.130752
| 2022-05-12T01:53:21
|
1233348529
|
{
"authors": [
"alexr00",
"luqmana"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8456",
"repo": "microsoft/vscode-pull-request-github",
"url": "https://github.com/microsoft/vscode-pull-request-github/issues/3551"
}
|
gharchive/issue
|
Switching to a diff of a file with comments always open comments pane.
Extension version: 0.40.0
VSCode Version: 1.66.1 (8dfae7a5cd50421d10cd99cb873990460525a898)
OS: Darwin arm64 20.6.0
Steps to Reproduce:
Navigate to PR w/ file-comments.
Open one such file. 'Comments' tab opens up in the bottom pane.
Close 'Comments' pane and navigate to different tab.
Go back to file-with-comments. 'Comments' tab opens up again.
It'd be nice if the Comments pane wouldn't pop up everytime I go back to the diff view or at least have an option to disable that behaviour.
You can disable this with the setting comments.openView. With VS Code 1.67 this has already been changed to be less aggressive and only open on the first file with comments.
|
2025-04-01T06:39:36.133325
| 2018-09-12T20:53:22
|
359648481
|
{
"authors": [
"RMacfarlane",
"Skowt",
"cat-turner",
"glemaitre",
"hemlok",
"patocallaghan"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8457",
"repo": "microsoft/vscode-pull-request-github",
"url": "https://github.com/microsoft/vscode-pull-request-github/issues/457"
}
|
gharchive/issue
|
Add status checks to the pull request description
It would great to expose PR status checks in the description. For example in Github we see
+1 for this one
+1 - Definitely a make or break for this extension
+1 one of the key values of making a pr on GitHub's ui
+1 yass
With the change for https://github.com/microsoft/vscode-pull-request-github/issues/1105 now merged, all status checks should show up on the description page. This isn't released yet but will be available in the nightly version of the extension tomorrow.
|
2025-04-01T06:39:36.141063
| 2020-04-24T19:24:17
|
606531185
|
{
"authors": [
"Rcubes",
"karrtikr"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8458",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/11397"
}
|
gharchive/issue
|
Highlighting for Python Code
Issue Type: Bug
Theme highlighting not working when using Python extension.
Python extension some times crashes and return original theme highlighting.
Extension version: 2020.4.74986
VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T16:36:23.138Z)
OS version: Windows_NT x64 10.0.18362
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)
GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled
Load (avg)
undefined
Memory (System)
31.85GB (13.98GB free)
Process Argv
Screen Reader
no
VM
0%
Are you using the Python Language server, i.e check the value of python.jediEnabled in settings
As you can see I have disabled Jedi. This is in my user settings, not sure if a I understand the difference between user and workspace, in case this is can produce a issue as well.
My vscode use to crash very often, that is almost unusable, and according to other github issues this was supposed to be resolved.
Any help will be deeply appreciated.
|
2025-04-01T06:39:36.142620
| 2021-03-20T02:41:26
|
836610710
|
{
"authors": [
"karthiknadig"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8459",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/15737"
}
|
gharchive/issue
|
command 'python.analysis.restartLanguageServer' already exists
We need to move this command to a global location rather than inside individual language server proxy. Potentially this should be in activation service for the language server since that currently handles starting a new server.
Duplicate of #13441
|
2025-04-01T06:39:36.147975
| 2021-03-29T15:32:15
|
843490317
|
{
"authors": [
"amina197",
"brettcannon",
"karthiknadig"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8460",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/15803"
}
|
gharchive/issue
|
Jedi 2and3 builtin error
Hi,
Everytime I launch a file in VScode, 2 Syntaxes errors are reported from the pythonFiles\lib\jedilsp\jedi\third_party\typeshed\stdlib\2and3 builtins.pyi file :
SyntaxError: non-default argument follows default argument jedi [1307, 12]
(and same for line 1319)
Lines 1306 and 1307 are:
@overload
def max(__iterable: Iterable[_T], *, key: Callable[[_T], Any] = ..., default: _VT) -> Union[_T, _VT]: ...
Lines 1318 and 1319 are:
@overload
def min(__iterable: Iterable[_T], *, key: Callable[[_T], Any] = ..., default: _VT) -> Union[_T, _VT]: ...
I have never modified this file since I am a beginner and I don't know what am I supposed to do about it.
Since these errors appeared my debugger works poorly and report non-existent errors on my files.
Thank you for your help!
This should be filed on jedi, https://github.com/davidhalter/jedi
/cc @davidhalter
@amina197 your version of Python is too old for keyword-only arguments which is what that file is using. You can either upgrade your version of Python or turn off Jedi and use either Pylance or no IntelliSense.
If it is a parso bug then it will be fixed in the next release of the extension for Jedi LSP and wasn't an issue in "old" Jedi as that's pinned for Python 2.7 support.
|
2025-04-01T06:39:36.154358
| 2021-03-30T02:15:57
|
843994144
|
{
"authors": [
"karrtikr",
"yanke1311"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8461",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/15808"
}
|
gharchive/issue
|
vscode-insider with Extension activation failed
Environment data
VS Code version: 1.55.0-insider
Extension version (available under the Extensions sidebar): 2021.3.680753044
OS and version: windows 10 Enterprise 20H2 19042.867
Python version (& distribution if applicable, e.g. Anaconda): 3.9.2
[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
my extension can not work normally for a long time.
Actual behaviour
Opening a python file prints Extension activation failed, run the 'Developer: Toggle Developer Tools' command for more information.
toggle developer tools, and can see errors:
Conflict in settings file vscode-userdata:/c%3A/Users/yke/AppData/Roaming/Code%20-%20Insiders/User: Ignoring python.insidersChannel as python is "set PYTHONIOENCODING=utf8 && python -u"
| (anonymous) | @ | workbench.desktop.main.js:633
-- | -- | -- | --
| u | @ | workbench.desktop.main.js:633
| f | @ | workbench.desktop.main.js:633
| doParseRaw | @ | workbench.desktop.main.js:633
| parseRaw | @ | workbench.desktop.main.js:633
| parseContent | @ | workbench.desktop.main.js:633
| loadConfiguration | @ | workbench.desktop.main.js:1265
| async function (async) | |
| loadConfiguration | @ | workbench.desktop.main.js:1265
| reload | @ | workbench.desktop.main.js:1265
| reloadLocalUserConfiguration | @ | workbench.desktop.main.js:2060
| (anonymous) | @ | workbench.desktop.main.js:2060
| requestIdleCallback (async) | |
| e.runWhenIdle | @ | workbench.desktop.main.js:68
| (anonymous) | @ | workbench.desktop.main.js:2060
| Promise.then (async) | |
| updateWorkspaceAndInitializeConfiguration | @ | workbench.desktop.main.js:2060
| initialize | @ | workbench.desktop.main.js:2060
| async function (async) | |
| initialize | @ | workbench.desktop.main.js:2060
| createWorkspaceService | @ | workbench.desktop.main.js:2789
| initServices | @ | workbench.desktop.main.js:2789
| open | @ | workbench.desktop.main.js:2789
| f | @ | workbench.desktop.main.js:2798
| m.load.removeDeveloperKeybindingsAfterLoad | @ | workbench.js:32
| (anonymous) | @ | bootstrap-window.js:167
| async function (async) | |
| (anonymous) | @ | bootstrap-window.js:162
| r._invokeFactory | @ | loader.js:1133
| r.complete | @ | loader.js:1143
| r._onModuleComplete | @ | loader.js:1769
| r._onModuleComplete | @ | loader.js:1781
| r._resolve | @ | loader.js:1729
| r.defineModule | @ | loader.js:1372
| p | @ | loader.js:1819
| _ | @ | loader.js:860
| (anonymous) | @ | workbench.desktop.main.js:2799
| (anonymous) | @ | workbench.desktop.main.js:2799
| r._createAndEvalScript | @ | loader.js:863
| (anonymous) | @ | loader.js:845
| v | @ | loader.js:964
| (anonymous) | @ | loader.js:969
| readFileAfterClose | @ | internal/fs/read_file_context.js:63
Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority.
If you think your issue is more of a question or configuration problem rather than a bug, please ask on Stack Overflow with the visual-studio-code and python labels for help.
Thanks for your understanding and patience!
Can you try clearing out the user settings? Open the settings.json file /c%3A/Users/yke/AppData/Roaming/Code%20-%20Insiders/User is referring to and delete all the settings there.
in latest version, it solved.
|
2025-04-01T06:39:36.172872
| 2022-03-27T05:55:55
|
1182365490
|
{
"authors": [
"karthiknadig",
"zbs"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8462",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/18790"
}
|
gharchive/issue
|
Linter fails because of read-only conda environment
In a remote SSH VS Code environment, pylint fails to run on save. Looking at the Python output, I see this:
conda run -n team_conda2 --no-capture-output --live-stream python /physical/gpfs/colo-teamusers/colo_team_users02/data_files/team/home/team/zsilversmit
h/.vscode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/get_output_via_markers.py /physical/gpfs/colo-teamusers/colo_team_users02/dat
a_files/team/home/team/zsilversmith/.vscode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/linter.py -m pylint ./sparta/sparta/product
ion/conda/full_bootstrap.py
conda run -n team_conda2 --no-capture-output --live-stream python /physical/gpfs/colo-teamusers/colo_team_users02/data_files/team/home/team/zsilversmith/.v
scode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/get_output_via_markers.py /physical/gpfs/colo-teamusers/colo_team_users02/data_fi
les/team/home/team/zsilversmith/.vscode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/linter.py -m pylint ./sparta/sparta/production/conda/full_bootstrap.py
# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<< Traceback (most recent call last):
File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/exceptions.py", line 1079, in __call__ return func(*args, **kwargs)
File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/cli/main.py", line 84, in _main exit_code = do_call(args, p)
File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/cli/conda_argparse.py", line 83, in do_call
return getattr(module, func_name)(args, parser)
File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/cli/main_run.py", line 25, in execute
script_caller, command_args = wrap_subprocess_call(on_win, context.root_prefix, prefix,
File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/utils.py", line 403, in wrap_subprocess_call
with Utf8NamedTemporaryFile(mode='w', prefix=tmp_prefix, delete=False) as fh:
File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/_vendor/auxlib/compat.py", line 81, in Utf8NamedTemporaryFile
return NamedTemporaryFile(mode=mode, buffering=buffering, encoding=encoding,
File "/team/public/conda/miniconda3-team.2/lib/python3.8/tempfile.py", line 541, in NamedTemporaryFile
(fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
File "/team/public/conda/miniconda3-team.2/lib/python3.8/tempfile.py", line 250, in _mkstemp_inner
fd = _os.open(file, flags, 0o600)
OSError: [Errno 30] Read-only file system: '/team/public/conda/miniconda3-team.2/envs/team_conda2/.tmpxix163cl'
The way my team's software is structured, I need to use this particular read-only conda environment. Could a setting be added that specifies a writable output directory for conda run? Or could a different command be invoked that doesn't require writing into the conda environment?
Issue Type: Bug
Diagnostic data
Python version (& distribution if applicable, e.g. Anaconda): 2.7.18
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
Value of the python.languageServer setting: Pylance
User Settings
defaultLS: {"defaultLSType":"Pylance"}
downloadLanguageServer: true
envFile: "<placeholder>"
venvPath: "<placeholder>"
venvFolders: "<placeholder>"
condaPath: "<placeholder>"
pipenvPath: "<placeholder>"
poetryPath: "<placeholder>"
languageServer: "Pylance"
linting
• enabled: true
• cwd: "<placeholder>"
• Flake8Args: "<placeholder>"
• flake8Enabled: true
• flake8Path: "<placeholder>"
• lintOnSave: true
• banditArgs: "<placeholder>"
• banditEnabled: false
• banditPath: "<placeholder>"
• mypyArgs: "<placeholder>"
• mypyEnabled: false
• mypyPath: "<placeholder>"
• pycodestyleArgs: "<placeholder>"
• pycodestyleEnabled: false
• pycodestylePath: "<placeholder>"
• prospectorArgs: "<placeholder>"
• prospectorEnabled: false
• prospectorPath: "<placeholder>"
• pydocstyleArgs: "<placeholder>"
• pydocstyleEnabled: false
• pydocstylePath: "<placeholder>"
• pylamaArgs: "<placeholder>"
• pylamaEnabled: false
• pylamaPath: "<placeholder>"
• pylintArgs: "<placeholder>"
• pylintPath: "<placeholder>"
sortImports
• args: "<placeholder>"
• path: "<placeholder>"
formatting
• autopep8Args: "<placeholder>"
• autopep8Path: "<placeholder>"
• provider: "black"
• blackArgs: "<placeholder>"
• blackPath: "<placeholder>"
• yapfArgs: "<placeholder>"
• yapfPath: "<placeholder>"
testing
• cwd: "<placeholder>"
• debugPort: 3000
• nosetestArgs: "<placeholder>"
• nosetestsEnabled: undefined
• nosetestPath: "<placeholder>"
• promptToConfigure: true
• pytestArgs: "<placeholder>"
• pytestEnabled: false
• pytestPath: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: false
• autoTestDiscoverOnSaveEnabled: true
terminal
• activateEnvironment: false
• executeInFileDir: "<placeholder>"
• launchArgs: "<placeholder>"
experiments
• enabled: true
• optInto: []
• optOutFrom: []
insidersChannel: "off"
tensorBoard
• logDirectory: "<placeholder>"
Extension version: 2022.2.1924087327
VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Remote OS version: Linux x64 3.10.0-1062.9.1.el7.comp3.x86_64
Connection to 'SSH: colo-appsvr-team86' could not be established Canceled
Connection to 'SSH: colo-login0007' could not be established Canceled
Connection to 'SSH: team-grid-jitter' could not be established Canceled
Remote OS version: Linux x64 3.10.0-1062.9.1.el7.comp3.x86_64
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz (16 x 2304)
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)
31.75GB (14.17GB free)
Process Argv
--folder-uri vscode-remote://ssh-remote%2Bcolo-login0010/physical/gpfs/colo-teamusers/colo_team_users02/data_files/team/home/team/zsilversmith/dev/git/eis5 --crash-reporter-id 745587e8-1a3a-48d7-afc4-0a837a16dc7e
Screen Reader
no
VM
0%
Item
Value
Remote
SSH: colo-login0010
OS
Linux x64 3.10.0-1062.9.1.el7.comp3.x86_64
CPUs
Intel(R) Xeon(R) Gold 6150 CPU @ 2.70GHz (36 x 3399)
Memory (System)
754.19GB (170.09GB free)
VM
0%
Connection to 'SSH: colo-appsvr-team86' could not be established Canceled
Connection to 'SSH: colo-login0007' could not be established Canceled
Connection to 'SSH: team-grid-jitang' could not be established Canceled
Item
Value
Remote
SSH: colo-login0009
OS
Linux x64 3.10.0-1062.9.1.el7.comp3.x86_64
CPUs
Intel(R) Xeon(R) Gold 6150 CPU @ 2.70GHz (36 x 3399)
Memory (System)
754.19GB (69.96GB free)
VM
0%
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvsnew555:30457759
vscscmwlcmt:30438805
vscgsvid2:30447481
pynewfile477:30450038
Looks like this is caused by conda attempting to write temporary files in read-only filesystems (conda issue). Is there a way to run this by doing conda activate <selected_environment>; pylint or something along those lines to avoid calling conda run?
Please update to the latest version of conda, https://github.com/conda/conda/pull/11215 . It should have fixed in it.
|
2025-04-01T06:39:36.175631
| 2019-02-05T01:28:26
|
406593773
|
{
"authors": [
"eleanorjboyd",
"karrtikr"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8463",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/4270"
}
|
gharchive/issue
|
Test Discovery: Unittest framework only detects test in current directory
Unittest framework only detects test in current directory, does not recursively detect tests in subdirectories.
Hello! I have reviewed this issue and given the architectural changes of the testing rewrite, this issue should no longer exist on the rewrite. Therefore I am going to close this issue but please comment or open a new issue if you are still seeing a problem when you try this yourself!
To use the rewrite yourself just add ”python.experiments.optInto": ["pythonTestAdapter"] to your user settings. You can confirm you have the rewrite enabled by setting your log level to trace, via the Developer: Set Log Level command in the command palette. Then check to see if Experiment 'pythonTestAdapter' is active is in your python logs.
Thanks!
|
2025-04-01T06:39:36.178906
| 2019-05-27T13:43:29
|
448864935
|
{
"authors": [
"DindoW",
"DonJayamanne"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8464",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/issues/5797"
}
|
gharchive/issue
|
Debug console cannot line feed
Issue Type: Feature Request
When I debug a python program, I wish arrays are in alignment.
But the debug console dosen't line feed though there is a '\n' in the end of the array.
Generally, the output of the debug console should be on every 5 elements in a row, and now, they are crowded together.
see:
Extension version: 2019.4.12954
VS Code version: Code 1.34.0 (a622c65b2c713c890fcf4fbf07cf34049d5fe758, 2019-05-15T21:59:37.030Z)
OS version: Windows_NT x64 10.0.17134
Issue moved to microsoft/ptvsd #1471 via ZenHub
|
2025-04-01T06:39:36.192785
| 2020-05-11T23:08:10
|
616244946
|
{
"authors": [
"codecov-io",
"rchiodo"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8465",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/pull/11754"
}
|
gharchive/pull-request
|
Fix run by line to scroll to the current location when stepping
Fix install message to reference run by line
For #11662, #11661
Fix run by line to set the cursor inside the cell and focus the cell.
Also fixed up the install directions so that they don't reference debugging.
Codecov Report
:exclamation: No coverage uploaded for pull request base (master@aa60924). Click here to learn what that means.
The diff coverage is 100.00%.
@@ Coverage Diff @@
## master #11754 +/- ##
=========================================
Coverage ? 60.62%
=========================================
Files ? 628
Lines ? 33935
Branches ? 4780
=========================================
Hits ? 20572
Misses ? 12365
Partials ? 998
Impacted Files
Coverage Δ
src/client/common/utils/localize.ts
95.56% <100.00%> (ø)
src/client/common/application/terminalManager.ts
33.33% <0.00%> (ø)
src/client/activation/common/downloader.ts
67.32% <0.00%> (ø)
src/client/activation/node/languageServerProxy.ts
27.94% <0.00%> (ø)
src/client/formatters/types.ts
100.00% <0.00%> (ø)
src/client/common/utils/version.ts
77.77% <0.00%> (ø)
src/client/workspaceSymbols/main.ts
69.87% <0.00%> (ø)
src/client/testing/display/main.ts
85.60% <0.00%> (ø)
src/client/common/application/types.ts
100.00% <0.00%> (ø)
src/client/logging/logger.ts
75.67% <0.00%> (ø)
... and 619 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 aa60924...b7d2696. Read the comment docs.
|
2025-04-01T06:39:36.206151
| 2020-09-07T00:10:56
|
694582014
|
{
"authors": [
"codecov-commenter",
"karthiknadig"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8466",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/pull/13817"
}
|
gharchive/pull-request
|
Disable flaky file system tests
For #10294
Disabling this entire suite. If we are comparing time, we should probably use a fuzzy comparison. For now disabling this.
Codecov Report
Merging #13817 into main will decrease coverage by 0.02%.
The diff coverage is n/a.
@@ Coverage Diff @@
## main #13817 +/- ##
==========================================
- Coverage 59.93% 59.91% -0.03%
==========================================
Files 684 684
Lines 37962 37962
Branches 5466 5466
==========================================
- Hits 22753 22744 -9
+ Misses 14048 14040 -8
- Partials 1161 1178 +17
Impacted Files
Coverage Δ
src/client/datascience/crossProcessLock.ts
79.41% <0.00%> (-11.77%)
:arrow_down:
src/client/common/utils/platform.ts
56.00% <0.00%> (-8.00%)
:arrow_down:
src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:
src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:
src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:
src/client/logging/levels.ts
61.11% <0.00%> (ø)
src/client/logging/logger.ts
62.74% <0.00%> (ø)
src/client/logging/formatters.ts
53.57% <0.00%> (ø)
src/client/logging/transports.ts
65.11% <0.00%> (ø)
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 24d1bc1...eb104b5. Read the comment docs.
|
2025-04-01T06:39:36.210735
| 2020-10-07T18:48:50
|
716769925
|
{
"authors": [
"kimadeline"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8467",
"repo": "microsoft/vscode-python",
"url": "https://github.com/microsoft/vscode-python/pull/14304"
}
|
gharchive/pull-request
|
Update release workflow to run tests in extension folder with spaces in path
For #14168
[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] 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).
[ ] The wiki is updated with any design decisions/details.
something went wrong lol
|
2025-04-01T06:39:36.271996
| 2020-08-03T07:53:52
|
671879849
|
{
"authors": [
"JDWilson1980",
"lszomoru"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8468",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/103814"
}
|
gharchive/issue
|
Azure DevOps - test improvements
[ ] Adopt a multi-stage pipeline for better visibility into dependencies
[ ] Review all test suites and ensure that they emit XML test results
[ ] Add pipeline task to publish the test results
NSS.cybersec.microsoft.com
G
Hubspot.ncis.host
Info.subscriber.report.net
Workflows.sysAutorun.IT6.1
BuildCyberSecurity.bat
Norton365.axio.net
Link.observe.solutions.deploy/Global-Axiom
Omni.brand.cybercommand.ntr
oP.github.hubspot.net
Unity.project.net
Repo.tv.net
Globalsolution.cyber.us
|
2025-04-01T06:39:36.282842
| 2020-08-20T00:45:22
|
682269937
|
{
"authors": [
"AleksandrHovhannisyan",
"GreatRequest",
"aeschli",
"xuchenrui-z"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8469",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/105039"
}
|
gharchive/issue
|
Wierd CSS properties sugestions
Issue Type: Bug
Started working with css and found that VScode (insiders) gives me some wild suggestions for the properties, eg. need "font-size: ;", first sugestion is "font-size-adjust: ;", need "line-height: ;" first suggestion is "line-height-step: ;". Can you please fix this, thanks.
VS Code version: Code - Insiders 1.49.0-insider (bd08768fd310d34cdd4423a53e5f3ca77340fea5, 2020-08-14T05:56:40.601Z)
OS version: Windows_NT x64 10.0.20190
System Info
Item
Value
CPUs
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 x 3600)
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)
23.87GB (8.47GB free)
Process Argv
O:\OneDrive\USER PROFILE\Desktop\Projects\Xanda Cutups\winnerlot-competitions --crash-reporter-id 195724cf-b023-494f-bd5b-8d48f67ba7b9
Screen Reader
no
VM
0%
Extensions (7)
Extension
Author (truncated)
Version
php-intellisense
fel
2.3.14
html-slim-scss-css-class-completion
gen
1.7.5
phpcs
ika
1.0.5
sftp
lix
1.12.9
remote-wsl
ms-
0.44.4
vscode-scss-formatter
sib
2.0.1
code-spell-checker
str
1.9.0
我草
change: https://github.com/microsoft/vscode-css-languageservice/commit/5b588f21fbd69051b6a18e7e44997480721f9d9b
This still seems to be a problem. I see this was part of the August milestone. Will it be released sometime this month?
The August release has just been released (1.49). If you still see a problem, please file a new issue with a small code sample and a description of what you see and what you expect.
|
2025-04-01T06:39:36.292129
| 2020-09-15T00:05:47
|
701508797
|
{
"authors": [
"WilliamParks",
"alexdima",
"deepak1556",
"lramos15",
"roblourens"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8470",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/106699"
}
|
gharchive/issue
|
Moving mouse over long lines in Javascript files uses 100% CPU for several seconds, and freezes
Version: 1.50.0-insider
Commit: cca20eba8974b1d6b6a9b71bf4e60a29c8f26648
Date: 2020-09-12T00:58:03.476Z
Electron: 9.3.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-47-generic snap
(reproduces on a friend's Windows 10 version as well)
This started happening on the main version of vscode ~3 days ago.
Sample: Needs to be renamed to .js
foo.txt
Steps to Reproduce:
Open a file with one long line. The file needs to have the JS extension (sample attached, but needs to have its extension changed to .js, as Github doesn't allow .js to be attached).
Click one spot in the file, and try to highlight a section.
Does this issue occur when all extensions are disabled?: Yes
Very interestingly, I don't see slowness in tokenizing the line, but there is significant slowness caused by hit testing to discover the mouse position:
I cannot reproduce if I execute with --disable-features=LayoutNG.
fyi @deepak1556
Here is a repro page -- clicking and selecting the text in Firefox & Safari is fast, while it is slow in Chromium -- https://jsfiddle.net/eahj49d8/
I have created https://bugs.chromium.org/p/chromium/issues/detail?id=1128937
Awesome, thanks @alexdima
Upstream changes are available in latest insiders, closing for another round of verification.
@deepak1556 I'm not sure what level of performance we're looking for here. On my mac it is super sluggish selecting and clicking the mouse to different sections of the line still freezes the editor
I see this
Same stack, much faster than the original example but still slow. Is there anything else to be done or is that just as good as the browser can get?
Firefox can do it quicker (about 20ms):
Oh yeah, this is nowhere near what it was. I've downloaded VS Code 1.48 (one version before updating to Electron 9) and profiled moving the mouse:
@deepak1556 Do you have any suggestion with what to do here? The upstream issue got fixed, but the perf issue remains, the caretRangeFromPoint call is still 100x slower for the same underlying HTML.
|
2025-04-01T06:39:36.294465
| 2020-10-19T05:31:23
|
724275936
|
{
"authors": [
"connor4312",
"harshlavingia"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8471",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/108915"
}
|
gharchive/issue
|
Allow to run single C# file easily similar to Python as csc.exe test.cs
It is very difficult to debug a single C# file in VS Code (without a visual studio project or solution) similar to Python. This feature is very helpful for students and interview preparations to run a single CS file in the terminal under the VS Code.
Feature: Open a folder in the VS Code which containing many C# files each containing the Main() function and after I open one of the C# files and click the Run/Debug button it will execute the code and show me the result in the terminal. This feature will make the C# popular among students and professionals preparing for interviews. Currently, I worked on C# projects/solutions at work but during my interview preparation, I use python to make my preparation faster. or use online compiler on coderpad or leetcode to compile the C# code.
/extCsharp
|
2025-04-01T06:39:36.302882
| 2020-11-23T16:44:14
|
748959187
|
{
"authors": [
"bpasero",
"eamodio",
"lramos15"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8472",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/111187"
}
|
gharchive/issue
|
Reopen Editor with breaks --wait behavior
Because Reopen Editor with seems to close the current document, and re-open it again in with the new editor, this break the --wait behavior. IMO, switching editors, shouldn't cause the document to be closed/opened nor break --wait
FYI, this causes issues for the new GitLens rebase editor, as it relies on the --wait behavior.
/cc @bpasero For more weird --wait cases. This is because internally a replace is just an open -> close which triggers the wait
When we detect --wait we install a listener to observe editors closing, e.g. here:
https://github.com/microsoft/vscode/blob/a14600c325fe43a34d57a42695cf1bb6708d2892/src/vs/workbench/electron-sandbox/window.ts#L665-L665
To then delete a wait marker file which the calling side polls on for deletion before returning:
https://github.com/microsoft/vscode/blob/a14600c325fe43a34d57a42695cf1bb6708d2892/src/vs/workbench/electron-sandbox/window.ts#L668-L668
The code for observing editors closing probably needs to be made more clever around the fact that editors can reopen:
https://github.com/microsoft/vscode/blob/eebf8e876ab99688b167b98874ca2b3c17822e4f/src/vs/workbench/browser/editor.ts#L174-L174
Currently we just listen to onDidCloseEditor which will fire even for the reopen case.
Some ideas:
enrich the IEditorCloseEvent to carry a boolean that can be used to figure out if the editor was closed because it was reopened
instead of reacting to the close event directly, add some debouncing to give the reopen a chance to bring up the new editor
Not a big fan of the debouncing because that solution sounds fragile to me. A property would make more sense to me.
Note that we already have a replaced property on IEditorCloseEvent which maybe is a bit misleading: it does not tell whether the editor was replaced from a replaceEditors call, but rather indicates that the editor was in preview mode and got replaced because another editor was opened. Maybe the property could still be reused though.
Given my recent change in this area, if we were to enrich EditorCloseContext with another context for the reopen, we can easily fix this:
https://github.com/microsoft/vscode/blob/cc4ace196cf5482f801b2ac06128bace2906f874/src/vs/workbench/common/editor.ts#L736-L736
Given my recent change in this area, if we were to enrich EditorCloseContext with another context for the reopen, we can easily fix this:
https://github.com/microsoft/vscode/blob/cc4ace196cf5482f801b2ac06128bace2906f874/src/vs/workbench/common/editor.ts#L736-L736
This sounds like a good solution
Tested this and it seems the REPLACE closed context is passed in the wait works properly.
|
2025-04-01T06:39:36.308544
| 2021-02-26T17:34:53
|
817539161
|
{
"authors": [
"connor4312",
"rzhao271",
"sandy081"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8473",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/117779"
}
|
gharchive/issue
|
Bad debugger suggestions for pwa-node
I tried debugging the node sample app in Dev Containers without having js-debug activated and the following message showed up:
However, when I click on the leftmost button to install extensions, I get the following query (tag:debuggers @sort:installs) and suggestions, none of them having to do with js or node debugging:
Searching just 'pwa' helped me realize that I forgot to activate js-debug, and searching 'pwa-node' yielded no results.
This suggestion should not generally be relevant since js-debug is built-in, and built-in extensions do not show in results. @rzhao271 do you use the js-debug nightly?
I've seen this sometimes where js-debug is not installed in remotes, but I assumed this was because I use the nightly extension and have the built-in one disabled.
@connor4312 I don't remember the exact state I was in, but I had the nightly version installed by that point. It was likely that I had both the nightly and stable versions disabled by accident, though I still felt confused by the results under tag: debuggers sort:@installs. I'm wondering if there's any way to add an OR into that query so that it can also list relevant disabled installed extensions?
It will usually list installed extensions (e.g. it shows the Debugger for Chrome in your screenshot), but not built-in extensions.
Giving to Sandeep who owns this but not sure it's worth fixing just for people using js-debug nightly.
Query to market place shows all result extensions in Marketplace - we do not filter built in extensions if they are also available in Marketplace. For eg., searching for pwa shows both stable (which is builtin) and nightly js debugger extensions
It seems the query tag:debuggers @sort:installs is also showing both those extensions but they are not shown on the top but somewhere in the middle due to sorting criteria
@connor4312 Moving this back to you if you would like to change the filter to get expected results
Ideally we could have metadata for packages in the marketplace to show the run with the right debug type... but this is not currently possible.
|
2025-04-01T06:39:36.311626
| 2021-03-24T18:21:09
|
840025391
|
{
"authors": [
"20anas11",
"eamodio",
"justinemojal",
"trileminh94"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8474",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/119814"
}
|
gharchive/issue
|
Git
Issue Type: Feature Request
VS code ne trouve pas le dossier Git, car il est installé dans mon autre disque dur. Je ne sais pas comment sélectionner le dossier où chercher.
Merci
VS Code version: Code 1.54.3 (2b9aebd5354a3629c3aba0a5f5df49f43d6689f8, 2021-03-15T10:55:45.459Z)
OS version: Windows_NT x64 10.0.10240
Translate to english:
VS code can't find the Git folder because it's installed in my other hard drive. I don't know how to select the folder to search.
Thank you
Would setting the PATH ENV variable help?
You can either add git to your path or set the git.path setting to the location of the git executable
|
2025-04-01T06:39:36.322422
| 2021-04-01T22:35:08
|
848840208
|
{
"authors": [
"gjsjohnmurray",
"glenn2223",
"sandy081"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8475",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/120389"
}
|
gharchive/issue
|
Marketplace Extension Manifest - SemVer not actually supported
Sorry if this isn't the correct place to bring this issue up.
Site ref: https://code.visualstudio.com/api/references/extension-manifest#fields
Github doc: https://github.com/microsoft/vscode-docs/blob/a641ec03073b116b12b9f5fcee95c024a79c6899/api/references/extension-manifest.md
It states under version that it's SemVer compatible. However, if I suffix a version with -rc.1 - which SemVer document, and have even used themselves (figure 1) - I get an error (figure 2)
Table row copied from the page
Name
Required
Type
Details
version
Y
string
SemVer compatible version.
(figure 1 - SemVer's own version of release candidate)
(figure 2 - Error displayed saying that only #.#.#.# is allowed)
I think this is a constraint of Marketplace, so probably belongs at https://github.com/microsoft/vsmarketplace
Do I need to create it over there or can it be moved?
A new development, initially reported here
So, as well as this issue I have reported here - which I will report at the suggested link, there's also a new issue with VS Code
Issue with VS Code
My extension isn't installing or is being automatically uninstalled, there's no errors in the code as a drag & drop of a .vsix file works
Steps to replicate: (brief)
Package the extension with version 5.0.0 (preview)
Upload it
Make changes
Package with the same version
Upload it
No one can install the extension or it automatically get uninstalled
Steps: (full breakdown)
Package the extension with version 5.0.0-rc.1 (preview)
Create a release on GitHub and add the package to it
Try to upload & get this error - only #.#.# is allowed
Package again, this time with version 5.0.0 (preview)
Upload this to the marketplace (upload successful)
Make changes
Package the extension with version 5.0.0-rc.2 (preview)
Create a release on GitHub and add the package to it
Package again - as I know it won't work - again with version 5.0.0 (preview)
Upload this to the marketplace (upload successful)
No one can install the extension or it automatically get uninstalled
It has to be supported by Marketplace, so assigning to @mjbvz ( I could not simply transfer it )
|
2025-04-01T06:39:36.325845
| 2021-04-27T13:16:34
|
868838482
|
{
"authors": [
"jrieken",
"misolori",
"sandy081",
"sbatten"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8476",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/122335"
}
|
gharchive/issue
|
Polish UI for @trustRequired filter
Testing #122230
open the extensions viewlet and filter by @trustRequired
there are two groups but the headers are rather cryptic
I suggest to insert some kind of message atop of each group that explains what this means
/cc @misolori
/cc @sandy081 as well
I wonder if this should apply to all of our cases where we do this splitting (WSL, Codespaces, Containers, etc.) because they all can fall under that same rule as well:
I wonder if this should apply to all of our cases where we do this splitting
+💯 It is so hard to convey the meaning of these bucket through titles only
Totally agree to have more info for views - Have you thought about providing this info using our custom hovers?
|
2025-04-01T06:39:36.332995
| 2021-08-31T12:57:15
|
987156362
|
{
"authors": [
"greazer",
"rebornix",
"turbonate"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8477",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/132166"
}
|
gharchive/issue
|
Horizontal scroll bar only works at the end of the Jupyter feed
Environment data
VS Code version: 1.59.1
Jupyter Extension version (available under the Extensions sidebar): v2021.8.1236758218
Python Extension version (available under the Extensions sidebar): v2021.8.1236758218
OS (Windows | Mac | Linux distro) and version: Windows 10 Pro - 20H2
Python and/or Anaconda version: 3.9.5 64-bit
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Jupyter server running: Local
Expected behaviour
When I am viewing a large dataframe output, I expect the horizontal scroll bar to be visible and work when I scroll up to view the headers of the dataframe print. The horizontal scrollbar should be available anytime the feed is showing a table or output that is wider than the visible feed.
Actual behaviour
I have to scroll to the bottom of the -correction: dataframe - to make the horizontal scroll bar visible, move the bar, then scroll back up to see the column headers.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
df = Dataframe()
load df with 15 columns and 36 rows of data (with long enough column names that it goes off the screen to the right)
print(df)
Logs
Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)
XXX
This is related to the other issue we have about being able to control how much of a dataframe (HTML) is displayed at a time.
The horizontal scrollbar should now be always visible
|
2025-04-01T06:39:36.344717
| 2021-09-15T12:38:53
|
997255249
|
{
"authors": [
"DonJayamanne",
"hammer",
"mjbvz",
"rchiodo"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8478",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/133172"
}
|
gharchive/issue
|
Latex stdout is not converted to latex (was: Julia help text rendered poorly)
How are you mainly using the Jupyter extension?
[X] Notebooks (.ipynb)
[ ] Interactive Window and or Cell Scripts (ex. .py files with #%%)
[ ] Both
What happened?
I wrote ?rand (for example) in a Julia notebook cell and executed the cell. The output of the cell was very difficult to read, as it appears to be unrendered LaTeX with strange coloring:
\begin{verbatim}
rand([rng=GLOBAL_RNG], [S], [dims...])
\end{verbatim}
Pick a random element or array of random elements from the set of values specified by \texttt{S}; \texttt{S} can be
\begin{itemize}
\item an indexable collection (for example \texttt{1:9} or \texttt{('x', "y", :z)}),
What flavor of VS Code are you using?
Stable
Jupyter Extension Version
v2021.8.2041215044
Jupyter logs
\begin{verbatim}
rand([rng=GLOBAL_RNG], [S], [dims...])
\end{verbatim}
Pick a random element or array of random elements from the set of values specified by \texttt{S}; \texttt{S} can be
\begin{itemize}
\item an indexable collection (for example \texttt{1:9} or \texttt{('x', "y", :z)}),
\item an \texttt{AbstractDict} or \texttt{AbstractSet} object,
\item a string (considered as a collection of characters), or
\item a type: the set of values to pick from is then equivalent to \texttt{typemin(S):typemax(S)} for integers (this is not applicable to \href{@ref}{\texttt{BigInt}}), to $[0, 1)$ for floating point numbers and to $[0, 1)+i[0, 1)$ for complex floating point numbers;
\end{itemize}
\texttt{S} defaults to \href{@ref}{\texttt{Float64}}. When only one argument is passed besides the optional \texttt{rng} and is a \texttt{Tuple}, it is interpreted as a collection of values (\texttt{S}) and not as \texttt{dims}.
\begin{quote}
\textbf{compat}
Julia 1.1
Support for \texttt{S} as a tuple requires at least Julia 1.1.
\end{quote}
\section{Examples}
\begin{verbatim}
julia> rand(Int, 2)
2-element Array{Int64,1}:
<PHONE_NUMBER>598768192
<PHONE_NUMBER>733606317
julia> using Random
julia> rand(MersenneTwister(0), Dict(1=>2, 3=>4))
1=>2
julia> rand((2, 3))
3
julia> rand(Float64, (2, 3))
2×3 Array{Float64,2}:
0.999717 0.0143835 0.540787
0.696556 0.783855 0.938235
\end{verbatim}
\begin{quote}
\textbf{note}
Note
The complexity of \texttt{rand(rng, s::Union\{AbstractDict,AbstractSet\})} is linear in the length of \texttt{s}, unless an optimized method with constant complexity is available, which is the case for \texttt{Dict}, \texttt{Set} and \texttt{BitSet}. For more than a few calls, use \texttt{rand(rng, collect(s))} instead, or either \texttt{rand(rng, Dict(s))} or \texttt{rand(rng, Set(s))} as appropriate.
\end{quote}
\rule{\textwidth}{1pt}
\begin{verbatim}
rand([rng::AbstractRNG,] s::Sampleable)
\end{verbatim}
Generate one sample for \texttt{s}.
\begin{verbatim}
rand([rng::AbstractRNG,] s::Sampleable, n::Int)
\end{verbatim}
Generate \texttt{n} samples from \texttt{s}. The form of the returned object depends on the variate form of \texttt{s}:
\begin{itemize}
\item When \texttt{s} is univariate, it returns a vector of length \texttt{n}.
\item When \texttt{s} is multivariate, it returns a matrix with \texttt{n} columns.
\item When \texttt{s} is matrix-variate, it returns an array, where each element is a sample matrix.
rand([rng::AbstractRNG,] s::Sampleable, dim1::Int, dim2::Int...) rand([rng::AbstractRNG,] s::Sampleable, dims::Dims)
\end{itemize}
Generate an array of samples from \texttt{s} whose shape is determined by the given dimensions. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(rng::AbstractRNG, d::UnivariateDistribution)
\end{verbatim}
Generate a scalar sample from \texttt{d}. The general fallback is \texttt{quantile(d, rand())}. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(rng, d)
\end{verbatim}
Extract a sample from the p-Generalized Gaussian distribution 'd'. The sampling procedure is implemented from from [1]. [1] Gonzalez-Farias, G., Molina, J. A. D., \& Rodríguez-Dagnino, R. M. (2009). Efficiency of the approximated shape parameter estimator in the generalized Gaussian distribution. IEEE Transactions on Vehicular Technology, 58(8), 4214-4223. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(::AbstractRNG, ::Distributions.AbstractMvNormal)
\end{verbatim}
Sample a random vector from the provided multi-variate normal distribution. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(::AbstractRNG, ::Sampleable)
\end{verbatim}
Samples from the sampler and returns the result. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(d::Union{UnivariateMixture, MultivariateMixture})
\end{verbatim}
Draw a sample from the mixture model \texttt{d}.
\begin{verbatim}
rand(d::Union{UnivariateMixture, MultivariateMixture}, n)
\end{verbatim}
Draw \texttt{n} samples from \texttt{d}.
What coding language are you working with?
Julia
VS Code Version?
1.60.1
Python Extension Version
No response
Python Version
No response
Anaconda Version
No response
What OS are you running on?
Mac
Running Jupyter locally or remotely?
Local
Code of Conduct
[X] I agree to follow this project's Code of Conduct
@rchiodo this is actually a duplicate of https://github.com/microsoft/vscode-jupyter/issues/6802
We need to discuss whether we should support latex in regular outputs or not (ipywidgets, plain html output, stdout, etc)
We need to discuss whether we should support latex in regular outputs or not
In the case of Julia, the ability to look up documentation with ? is quite fundamental, so I'm a big +1 for LaTeX support. That said, the use of LaTeX in Julia's docs is primarily for document structure and formatting, so another solution upstream might be to convert their LaTeX to Markdown on the client...
@DonJayamanne Should we close this as an upstream issue?
Ah it appears https://github.com/microsoft/vscode-jupyter/issues/6529 is a precise duplicate of this issue as well.
This is something that Jupyter supports so it should be supported in VS code (otherwise people can't open notebooks generated with Jupyter).
I'm closing this as an upstream issue based on my understanding of it. Rendering of output is left up to output renderers; we don't parse the output looking for latex but a renderer could
@mjbvz shouldn't the core support text/latex as an output type though? We had discussing submitting a PR to core to make so that markdown-it could actually render these latex outputs. They can also be embedded in regular markdown, so it seems to make sense to support them in the core itself.
Latex output was #123144 (which should be reopened since it was since reverted)
If there's something else you think VS Code itself should handle, please open an issue that explains the problem independently of Jupyter directly
@mjbvz sorry I was incorrect. This issue here is about latex outputs in stdout or text/html. For example the julia kernel generates latex in their stdout.
|
2025-04-01T06:39:36.354243
| 2021-11-09T09:37:53
|
1048386618
|
{
"authors": [
"IllusionMH",
"kundan1908"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8479",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/136736"
}
|
gharchive/issue
|
Extension issue
Issue Type: Bug
Extension Name: html-language-features
Extension Version: 1.0.0
OS Version: Windows_NT x64 10.0.19042
VS Code version: 1.62.0
:warning: We have written the needed data into your clipboard. Please paste! :warning:
/needsMoreInfo
|
2025-04-01T06:39:36.355878
| 2022-02-16T19:03:52
|
1140441358
|
{
"authors": [
"IllusionMH",
"amrendra22"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8480",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/143231"
}
|
gharchive/issue
|
unable to load static files
We have written the needed data into your clipboard because it was too large to send. Please paste
.
/needsMoreInfo
Please specify how exactly this is related to VS Code editor itself?
If you are using some extension to provide live server - issue should be reported in extension's repo.
|
2025-04-01T06:39:36.403493
| 2022-03-03T10:12:55
|
1158217489
|
{
"authors": [
"VSCodeTriageBot",
"bpasero",
"originlondon"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8481",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/144311"
}
|
gharchive/issue
|
Allow double click on tab to return layout to original
Issue Type: Bug
If you have a split screen you can vary the width of the split.
One behaviour was that you could double click a tab and it would occupy most of the window and then double click again to return it to its previous size and layout.
The second double click now resets the layout of all splits to some sort of middle.
It used to be very useful if you had many files but only generally wanted to be able to see a little bit of them in reference (like the bootstrap css breakpoints) but then occasionally enlarge that file to look at other parts of it.
Or just flick between file tabs and keep them large. This is very useful on screens smaller than enormous.
I have removed all extensions and it appears to be the same without extensions.
VS Code version: Code 1.64.2 (Universal) (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:00:58.347Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz (8 x 2800)
GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled
Load (avg)
2, 2, 3
Memory (System)
16.00GB (0.08GB free)
Process Argv
--crash-reporter-id a910920d-1205-4d5b-bb90-06a303804f97
Screen Reader
no
VM
0%
/gifPlease
Ok thanks. Will sort that later today.
Best regards
Matt Holmes
Director
Origin London Ltd
@.***
UK:<PHONE_NUMBER>0
Int: +447500847210
Companies House Number: 7302875
VAT Registration Number: GB231798196
Registered Office: 52 Llanover Road, London. SE18 3SU
From: Benjamin Pasero @.***>
Sent: Thursday, 3 March 2022, 11:44
To: microsoft/vscode
Cc: originlondon; Author
Subject: Re: [microsoft/vscode] Double click on tab no longer returns layout to original (Issue #144311)
/gifPlease
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/144311#issuecomment-1057960727, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7Y25OQI25IIB4HEAARYOLU6CQY7ANCNFSM5P2AIEBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
Thanks
I was asked to explain further with a screencast.
I have uploaded an mp4 and tried to embed a gif as requested, but couldn't as the mp4 converted to a gif was too large. It seems to display inline with mp4 though anyway.
https://user-images.githubusercontent.com/33525109/157091189-ef01fec6-1e59-4e57-bf98-de38377631d7.mp4
@originlondon I see but you indicate this has changed recently? I do not think so. Can you clarify?
I believe it was working as described in October last year. I couls be mistaken, as I took a break from coding for a few months.
My larger screen broke so I had to use an older smaller one. I also remember discovering that feature when using just a left-right split. So I discovered the feature around July/August last year, perhaps.
But I am pretty sure that it used to work like that as I used to keep four or five core scss variable definition files at the bottom of my left panel, each with just a few key lines showing and then expand and contract them as necessary, if needed to see the rest of the file, rather than search through them via the dropdown, or flick along the tabs or choose them in the open tabs browser in the panel.
Apologies for any typos, I was finding this difficult to write as Microsoft Outlook on Android mobile was not doing 'cut' functionality, only copy, paste and delete - weird. Lol. (not going to report that just yet - could be an Android thing after an update last night and its indicating another one due, which could correct that).
Thanks.
Best regards
Matt Holmes
Director
Origin London Ltd
@.***
UK:<PHONE_NUMBER>0
Int: +447500847210
Companies House Number: 7302875
VAT Registration Number: GB231798196
Registered Office: 52 Llanover Road, London. SE18 3SU
From: Benjamin Pasero @.>
Sent: Tuesday, March 8, 2022 6:28:33 AM
To: microsoft/vscode @.>
Cc: originlondon @.>; Mention @.>
Subject: Re: [microsoft/vscode] Double click on tab no longer returns layout to original (Issue #144311)
@originlondonhttps://github.com/originlondon I see but you indicate this has changed recently? I do not think so. Can you clarify?
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/144311#issuecomment-1061453056, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7Y25IF4XMFT5SWPADNSLLU63XRDANCNFSM5P2AIEBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
I think this is working for a long time like that, but treating as feature request.
//cc @joaomoreno @sbatten since this is grid related.
Ok thank you!
Best regards
Matt Holmes
Director
Origin London Ltd
@.***
UK:<PHONE_NUMBER>0
Int: +447500847210
Companies House Number: 7302875
VAT Registration Number: GB231798196
Registered Office: 52 Llanover Road, London. SE18 3SU
From: VS Code Issue Triage Bot @.>
Sent: Tuesday, March 8, 2022 8:13:49 AM
To: microsoft/vscode @.>
Cc: originlondon @.>; Mention @.>
Subject: Re: [microsoft/vscode] Allow double click on tab to return layout to original (Issue #144311)
This feature request is now a candidate for our backlog. The community has 60 days to upvotehttps://github.com/microsoft/vscode/wiki/Issues-Triaging#up-voting-a-feature-request 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 documentationhttps://aka.ms/vscode-issue-lifecycle.
Happy Coding!
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/144311#issuecomment-1061515320, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7Y25O3OKQDCYCP4LNIC4DU64D33ANCNFSM5P2AIEBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
|
2025-04-01T06:39:36.410683
| 2022-04-01T17:02:43
|
1190060305
|
{
"authors": [
"DillPickle80",
"VSCodeTriageBot",
"rzhao271"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8482",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/146566"
}
|
gharchive/issue
|
Allow users to override an extension's Activation Event in settings.json
Pretty much all in the title. A lot of extensions don't seem to care about choosing the most optimal Activation Event, or some extensions are simply having a hard time not to lag while running on a remote server, while they work just fine locally... It would be great if users could easily override it in settings.json if they desire, without needing to fork the whole extension and edit it on their own. Would it be possible somehow?
I'm wondering what are some extensions that currently have this issue?
Hi again, sorry i had to take a job break for health reasons.
@rzhao271 It would rather be for test purposes. Most extension are super fast on a regular network, but for some reason on a job network with picky firewall some will get really slow. Being able to test different Activation Event on our own could allow developers to suggest improvement to some extensions that would not be a problem for most users; and in the case the number of users it would benefit would be too low to be worth adressing, the user could try dealing with the issue on their own without needing to fork extensions.
I'm not on my job network right now and might not be for some time. I would have been pleased to provide you examples of Extensions giving me problems (there aren't that many anyway), but i can't right now. Also after a lot of testing trying to figure out a solution, i noticed that some slow-to-start extensions aren't problematic on their own, but starts to be when combined with other Extensions, most notably Python. Considering similar issues i've read online, it seems to be a problem with C++ extension too; i guess it might have something to do with compilers/debuggers, but that's just a guess i couldn't really tell.
It seemed to me it wouldn't necessarily be very complicated to implement, and might be a good idea in this context. I could be wrong. I'm aware users could end up shooting their own foot by tweaking such setting. I would be pleased to get more info about the feasibility of such feature, the possibility it could lead to security issues, or any problem related to it. I guess there are some since there was a downvote on my issue, but no further information was given by the disliking dev.
Could you reopen the issue?
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!
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
|
2025-04-01T06:39:36.418250
| 2022-05-04T19:41:52
|
1225826829
|
{
"authors": [
"roblourens",
"weinand",
"xisui-MSFT"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8483",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/148735"
}
|
gharchive/issue
|
Synchronous launch compounds
Launch compounds in workspaces launch asynchronously. While this saves launch time, we found a couple of issues with this:
Following quick pick menu / input box will cancel the previous one. If two launch task both have such requirements, then one of them ends up to be cancelled.
One launch may depend on another.
Although launching them one at a time is a workaround, it requires a lot of mouse clicks, and is error-prone if there are a lot of launch configs in a project.
So a synchronous launch compounds feature might be a great addition. Feel free to provide other workarounds though.
The first issue is https://github.com/microsoft/vscode/issues/141514
The second, I'm not sure we can do anything about it. How can we know when one config is "done launching" so that a dependent config can be started? Is it ready when we have attached to the debuggee and initialized the session?
Can you give an example of when you have a launch config that depends on another.
The second issue is a suspicion since our project is still in its early state. A possible usage is one project starts a service, and the second, like a test or some user space app, uses this service.
Is returning from startDebugging(), which is in vs code api but there should be something equivalent internally, not enough to decide a launch action is completed?
not enough to decide a launch action is completed
Maybe - the second project depends on "something" from the first project, and there is no way to know generically when the first project is in the right state that the second needs.
But I think if we tried to address this we would want to change the launch.json format to let us declare dependencies for a launch config. Curious whether you ever considered this @isidorn @weinand
We have our own debug adapter, so we can work around this by adding a new launch config request type, which is only allowed in workspace, and in which force launch configs to start one by one. And the only criteria we are using to decide if the previous launch finishes is returning form await startDebugging():
for (const launchConfig of config.launchConfigurations) {
const folderIndex = launchConfig.folderIndex;
if (!isNumber(folderIndex) || folderIndex >= vscode.workspace.workspaceFolders.length || folderIndex < 0) {
// Print error
return;
}
await vscode.debug.startDebugging(vscode.workspace.workspaceFolders[folderIndex], launchConfig.launchConfigurationName);
}
And the reason I open this feature request is because, if VS Code has this built in, then I don't need to add a different request type for this.
@roblourens we do not want to duplicate shell functionality in launch configs. If more control over process execution is needed, we recommend to use a shell script.
@roblourens we do not want to duplicate shell functionality in launch configs. If more control over process execution is needed, we recommend to use a shell script.
Is it possible to start debugging in VS Code via shell script?
You approach is a good one @xisui-MSFT, it works for you but might not work in every situation, and I would not build it into vscode.
You can also start your app in a shell script in debug mode, and write an "attach" config. Or if this is javascript, you can run a shell script in a "javascript debug terminal".
|
2025-04-01T06:39:36.419437
| 2022-06-30T14:59:10
|
1290261981
|
{
"authors": [
"AreejElshrief",
"gjsjohnmurray"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8484",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/153830"
}
|
gharchive/issue
|
MODULE PROBLEM
I downloaded a module named pygame, but it said there is no module named pygame when I say 'import pygame'.
/question
|
2025-04-01T06:39:36.427163
| 2022-10-03T18:31:44
|
1395151620
|
{
"authors": [
"VSCodeTriageBot",
"connor4312",
"gentig"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8485",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/162602"
}
|
gharchive/issue
|
Node debugger not working in WSL
Node debugger in WSL is not working. Node is installed in WSL but the debugger does not stop when adding breakpoints. All I am doing is creating a simple nodejs (v14.18) application, created the launch.json file and run the debugger.
I have the following launch configuration.
{ "version": "0.2.0", "configurations": [ { "type": "node", "request": "launch", "name": "Launch Program", "skipFiles": [ "<node_internals>/**" ], "program": "${workspaceFolder}/src/app.js" } ] }
/jsDebugLogs
Please collect trace logs using the following instructions:
If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.
⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to<EMAIL_ADDRESS>
Sent the trace file via email.
Hmm, can you set "console":"internalTerminal" in your launch.json, and screenshot the resulting TERMINAL tab in VS Code?
Hi Connor,
I changed my node version from 14 to 16 and that solved the problem. I did
not get a chance to try your fix but I will keep that in mind. Thanks for
your help.
Best,
Genti
On Tue, Oct 4, 2022 at 12:14 AM Connor Peet @.***>
wrote:
Hmm, can you set "console":"internalTerminal" in your launch.json, and
screenshot the resulting TERMINAL tab in VS Code?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/162602#issuecomment-1266374468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWRAYRZDKWBQ5J5CXITZ7TWBOVLXANCNFSM6AAAAAAQ33DW3Y
.
You are receiving this because you authored the thread.Message ID:
@.***>
|
2025-04-01T06:39:36.430559
| 2022-10-12T03:33:52
|
1405502818
|
{
"authors": [
"VSCodeTriageBot",
"eamodio",
"roblourens"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8486",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/163390"
}
|
gharchive/issue
|
Extension behaves VERY slowly during initialization while debugging
In the latest insiders build, initialization timings for GitLens while debugging are VERY slow (like 10x slower than when running the exact same code in 1.72.1). I can't point to any one thing but most calls during GitLens startup are just taking WAY longer. It visibily takes many seconds for the GL icon to show up in the activity bar, but under 1.72.1 it happens very quickly.
Not sure if its related, but restarting and stopping debugging seem to take extra long as well.
Today's insiders build seems to have resolved the issue so far.
I spoke too soon, with today's insiders the running code doesn't seem too slow, but stepping is VERY slow and stopping debugging gets stuck often (where I can't even click on anything)
Can you tell me where in gitlens I could set a breakpoint to see this? I've been debugging vscode-jupyter with no issues
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-01T06:39:36.435484
| 2022-10-19T13:15:48
|
1414956261
|
{
"authors": [
"bpasero",
"litaohe"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8487",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/164026"
}
|
gharchive/issue
|
Soft link causes the same source file to be edited in two windows at the same time
Does this issue occur when all extensions are disabled?: Yes/No
VS Code Version: 1.72.2 (Universal)
commit: d045a5eda657f4d7b676dedbfa7aab8207f8a075
date: 2022-10-12T22:16:30.254Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 21.6.0
OS Version: macOS Monterey 12.5.1
After vscode opens the project in the soft link directory, jumps to the definition in the code file, a new file will be opened, and the path of the new file is displayed as the file in the original directory.
Modifying one of the open files and saving them will trigger another unmodified "same" file window to also save, resulting in a messy file.
Steps to Reproduce:
Create a directory O, and create a soft link directory S to O;
Create project proj under O, add project file main.cpp, and open S/proj in vscode;
Open the file main.cpp through the left resource manager of vscode, add functions foo and bar, and call foo in bar;
Hold down ctrl and click foo in the bar, the expectation is to jump to the definition of foo in the same file, but it actually opens a new tab, and the display path is O/proj/main.cpp;
This works "as designed", we do not resolve symbolic links when you open an editor for performance reasons so you can end up having 2 distinct editors opened pointing to the same file with different buffers.
|
2025-04-01T06:39:36.440119
| 2022-10-28T08:23:15
|
1426884358
|
{
"authors": [
"VSCodeTriageBot",
"fpichlou",
"gjsjohnmurray"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8488",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/164862"
}
|
gharchive/issue
|
I can not open a new terminal or split the terminal
Type: Bug
I can not open a new terminal or split the terminal!!
VS Code version: Code 1.72.1 (Universal) (129500ee4c8ab7263461ffe327268ba56b9f210d, 2022-10-10T17:25:13.482Z)
OS version: Darwin arm64 20.6.0
Modes:
Sandboxed: No
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.72.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!
/gifPlease
Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette).
Happy coding!
Fixed!
|
2025-04-01T06:39:36.442685
| 2022-11-14T15:37:02
|
1451566747
|
{
"authors": [
"VSCodeTriageBot",
"idoprz",
"joaomoreno"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8489",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/166456"
}
|
gharchive/issue
|
Selecting github enterprise for cloning a project
Hi,
In latest releases I can sign in to my github enterprise for the pull request. But, when I want to clone a project the git clone only show "github" even if I'm signed into github enterprise.
/duplicate #98349
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!
|
2025-04-01T06:39:36.449099
| 2022-12-13T16:11:37
|
1494597909
|
{
"authors": [
"VSCodeTriageBot",
"sean-mcmanus",
"smeriano",
"yongyouhe"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8490",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/169013"
}
|
gharchive/issue
|
command-line error: invalid option: --using_directory
Does this issue occur when all extensions are disabled?: No
VS Code Version: 1.74.0
OS Version: Linux x64 5.8.0-63-generic
Steps to Reproduce:
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!
In a selected Directory, I type in the cmd : "code ."
VSCode opens up but the include directories of header/cpp files are not being recognized. For instance , if I have the files
"directoryA/test.h" and "directoryB/test.cpp" , and do --> include "directoryA/test.h" in the test.cpp file, then VSCODE cannot link these two files together, meaning Defined variables of test.h are not showing up automatically. Compilation works fine.
The "command-line error: invalid option: --using_directory" line is showing in both .h and .cpp files.
It also does not matter if the .h and .cpp files are in the same directory.
I have the same problem now. How was this problem finally solved?
I have the same problem now. How was this problem finally solved?
It was not.... I will write an issue to the cpp extension experts! If you find a solution please let me know.
Thanks :)
I have the same problem now. How was this problem finally solved?
There is already a thread concerning this issue :
https://github.com/microsoft/vscode-cpptools/issues/10249
Fixed with https://github.com/microsoft/vscode-cpptools/releases/tag/v1.13.8
|
2025-04-01T06:39:36.453097
| 2023-01-01T08:12:13
|
1515384718
|
{
"authors": [
"VSCodeTriageBot",
"muhammadyusuf-kurbonov",
"sandy081"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8491",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/170351"
}
|
gharchive/issue
|
Install extension only for this workspace (enable it only for this workspace)
Hello. I'm using VSCode with several of my Projects. Each has a different tech stack and toolset (even languages). I need always disable many extensions when creating a new one. Can developers make an option or something like this for:
Enable new (installing) extensions only for selected workspace.
For other workspaces, it should be disabled by default.
And there can be a dialog if I want to install the extension globally.
Thank you for your attention
/duplicate
Use Profiles feature - https://github.com/microsoft/vscode/issues/116740
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!
Thanks for help
|
2025-04-01T06:39:36.460544
| 2023-02-03T10:26:51
|
1569614708
|
{
"authors": [
"F1r3Pr1nc3",
"VSCodeTriageBot",
"rebornix"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8492",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/173278"
}
|
gharchive/issue
|
Selection Replace jumps unwanted
Does this issue occur when all extensions are disabled?: Yes
VS Code Version: 1.70.3 (user setup)
Commit: a21a160d630530476218b85db95b0fd2a8cd1230
Date: 2022-08-31T08:04:00.223Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT ia32 6.1.7601
Steps to Reproduce:
If you want to replace something in a selection and then you want to change the selection you must put off the Selection Replace (which is in other editor not the case).
But for this reason now the cursor jumps pretty unwanted automatically to the next hit on the whole text, which is pretty annoying in large text.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.75.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!
OK then do whatever you want with this report.
@F1r3Pr1nc3 would you mind checking if it's still an issue with the very latest VS Code stable when time allows?
@F1r3Pr1nc3 would you mind checking if it's still an issue with the very latest VS Code stable when time allows?
Yes, it is the same in the actual version.
Version: 1.75.1 (user setup)
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:32:34.589Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042
Hey @rebornix, this issue might need further attention.
@F1r3Pr1nc3, you can help us out by closing this issue if the problem no longer exists, or adding more information.
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-01T06:39:36.484267
| 2023-05-09T13:47:10
|
1702077274
|
{
"authors": [
"EthanBarlow",
"HighLiuk",
"VSCodeTriageBot",
"bantunes22",
"bormat",
"p32929",
"peerdavid",
"roblourens",
"ymongo"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8493",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/181892"
}
|
gharchive/issue
|
Bottom State bar not turning orange in debug anymore
Type: Bug
Hi there!
As title says, bottom state bar of VSCode doesn't turn orange when launching debug. Can you bring it back? Or give option to do so?
Thanks for the good work!
What theme?
Can you try starting with --disable-extensions?
got same problem today the theme changed by itself apparently
Having the same problem, this hapenning after I accepted the change to the new "Dark Modern" theme.
The flag is enabled.
Even worse, step debuggers do not work this way.
In that theme, it should turn blue. Can other share their theme?
Does it work as expected if you change your theme back to Dark+?
Maybe someone can share a video to be sure that I understand correctly, I don't see an issue.
@roblourens Yes, it works as expected when changing the theme back to Dark+. I expected the "Dark Modern" theme to color the bar in the same way, but thanks for suggesting changing the theme back to Dark+.
Do you happen to have any workbench.colorCustomizations in your settings.json?
I have the tame problem (V1.78.2). For me, it happens only with the "Dark Modern" theme, all other themes are fine, the bar is orange. I don't have any customizations in the settings.json file.
For now I simply switched to "Dark (Visual Studio)".
Do you happen to have any workbench.colorCustomizations in your settings.json?
No, I do not have any workbench.colorCustomizations in my settings.json. If the color of the bar is not expected to be orange in the "Dark Modern" theme, then I think this issue should be closed.
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!
This is a great feature. I missed this feature after updating so I downgraded to 1.74.3
|
2025-04-01T06:39:36.529380
| 2023-06-22T15:06:42
|
1769891172
|
{
"authors": [
"aiday-mar",
"hediet"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8494",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/185884"
}
|
gharchive/issue
|
Performance Improvement Suggestion: Only Rerender Sticky Scroll When State Is Different
In stickyScrollWidget.ts there is setState, which seems to be called every time the scroll event of the editor fires.
That method seems to clear the dom node and reconstruct it unconditionally.
When smooth scrolling is turned on, the scroll event fires many times per second and the setState call seems to take some time:
I think if you would only rerender the sticky scroll widget when necessary (and generally try to minimize dom API accesses), we could improve the performance here easily.
I think StickyScrollWidgetState could have an equals method and setState would just do an early return if the new state equals the old state.
Thanks for this remark. It is a very good optimization point.
|
2025-04-01T06:39:36.531946
| 2023-08-03T04:19:13
|
1834242406
|
{
"authors": [
"Tim-Cao"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8495",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/189522"
}
|
gharchive/issue
|
code -rg cannot open file on fedora OS
Type: Bug
Steps to reproduce
Install the vscode 1.80.2 on Fedora 38 OS
Open the terminal
Type code -rg /path/to/file
Expected Results:
The file should be opened in vscode.
Actual Results:
The vscode is opened but not open that file.
I cannot reproduce this issue after reboot
|
2025-04-01T06:39:36.535474
| 2023-10-15T08:52:33
|
1943802758
|
{
"authors": [
"VSCodeTriageBot",
"dishaphatta"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8496",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/195650"
}
|
gharchive/issue
|
Intellisense Not Working in Visual Studio Code
During coding sessions in Visual Studio Code, the Intellisense feature, known for code completion and suggestions, is malfunctioning. It has become unresponsive, causing coding slowdowns and heightened error risks due to the absence of its usual assistance. This setback hampers development efficiency, undermines the coding experience, and necessitates immediate resolution to restore the tool's vital support.
Solution:
Update VS Code: Ensure you have the latest version by going to Help > Check for Updates.
Restart: Restart VS Code to resolve potential Intellisense problems.
Install Language Extension: Get the right language extension from the VS Code Marketplace.
Check Firewall: Ensure VS Code can access the internet for Intellisense resources.
Disable Interfering Extensions: Turn off extensions that might be causing conflicts in File > Preferences > Extensions.
Reset IntelliSense Database: Clear cached data by typing "C/C++: Reset IntelliSense Database" in the Command Palette (Ctrl+Shift+P).
Reinstall VS Code: If issues persist, consider reinstalling VS Code as a last resort.
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 for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!
|
2025-04-01T06:39:36.554775
| 2024-02-16T09:16:00
|
2138182093
|
{
"authors": [
"VSCodeTriageBot",
"dimateos"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8497",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/205345"
}
|
gharchive/issue
|
Tasks "dependsOn" should preserve default value
At the top of tasks.json you can write default settings shared by all tasks, these can then be overwritten per task.
This feature is great: quite useful and helps reducing the verbosity of the file, e.g. setting a common "presentation", "type"...
But not all settings preserve the specified default value (could not find documentation)?
This is the case for "dependsOn" (probably also "dependsOrder").
Arguably ALL settings should respect specified global values, but my current use case for "dependsOn":
I have many tasks are related to BUILD XXXX with alternative build types/arch/targets. Preferred over a bunch of inputs (pickString) to get terminal panels for each one with separate logs.
All depend on a task that essentially stops all debugging to prevent binaries being protected from write access.
I have to add this task manually to each because the globally set "dependsOn" is ignored. If I want to change the task, I have to search and replace everywhere instead of just the flexible global etc.
In general, there is a reason why not all settings are preserved?
Regards
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!
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
|
2025-04-01T06:39:36.591156
| 2024-03-21T05:00:56
|
2199123465
|
{
"authors": [
"DevinJohw",
"JakubStasiak00",
"LucasOe",
"VSCodeTriageBot",
"alexvoedi",
"angelhdzmultimedia",
"bobslee",
"dantgw",
"dennmtr",
"devinjohw",
"gjsjohnmurray",
"mrcaidev",
"musjj",
"plashenkov"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8498",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/208276"
}
|
gharchive/issue
|
[linked rename] Linked Editing does't work well
Does this issue occur when all extensions are disabled?: Yes
VS Code Version: 1.87.2
OS Version: macOS 14.3.1 (23D60)
Steps to Reproduce:
set up the linked editing option as true
crate an HTML tag with one or two attributes, like <div class="main"></div>
modify the name of the tag on the opening tag, you would find out that the closing tag is automatically deleted while not added automatically.
/needsMoreInfo
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!
/needsMoreInfo
Sorry, I just misclicked the post button.
The Ayu theme extension cause this issue.
/causedByExtension
/causedByExtension
Sorry for my misunderstood, It's indeed an issue. If there are some attributes in the opening tag, you can't delete the entire name, then change it to another one, like this.
If you delete part of the name, it wokrs.
If there is no attributes in the opening tags, it works perfectly whether deleting the entire name or part of the name.
@aeschli is this your area? If not, please redirect. It also needs two tags removing.
+1 Experiencing this (annoying) issue as well.
Sometimes if I type too fast, the tag on the other side couldn't catch up, and stops updating half-way.
Facing this exact same issue as well
Still happening on VSCode 1.92.2.
same here
On 1.93.0, this is no longer a problem as far as I can tell. Can anyone else confirm?
It also works pretty well with the vim plugin.
Sometimes if I type too fast, the tag on the other side couldn't catch up, and stops updating half-way.
The same problem. It appears that at this point the only way to ensure predictable behavior is to disable this setting.
This problem has nothing to do with extensions. I just did a bisect and even without any extensions enabled this bug still occures.
https://github.com/user-attachments/assets/24507368-a003-4343-810b-a12652278f3c
21-10-2024 issue persists. I have found a woraround, you have to select the tag name and then instead of clearing the name, start writing the new one..
Duplicate of #185279
|
2025-04-01T06:39:36.597453
| 2024-05-03T01:41:04
|
2276762110
|
{
"authors": [
"AP1400",
"OccasionalDebugger",
"VSCodeTriageBot",
"roblourens"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8499",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/211894"
}
|
gharchive/issue
|
Support full range of function breakpoint fields in plugin addBreakpoints
At the moment, it is possible to pass a FunctionBreakpoint instance with the full range of fields configured, but when the breakpoint is eventually inserted, only the name and mode are included.
It would increase the power of the API to pass the full set of fields.
Friendly ping! Looks like this issue requires some further steps to be verified. Please provide us with the steps necessary to verify this issue.
Why i should do this when i dont get 1 single dollar but any cheater get
so mouch money or when i say im how to start this they laughs at me and
since yesterday I keep getting stupid messages About giving access and
taking money from whom, those whom I myself brought to this stage
On Wed, May 29, 2024, 2:52 AM VSCode Triage Bot @.***>
wrote:
Friendly ping! Looks like this issue requires some further steps to be
verified. Please provide us with the steps necessary to verify this issue.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/211894#issuecomment-2137464955,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWBOC6BKJNNI3P6GED2NYO3ZEXMTJAVCNFSM6AAAAABHEW4OCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZXGQ3DIOJVGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>
Steps: from an extension, call debug.addBreakpoints(new FunctionBreakpoint(...)) and verify that the breakpoint shows up in the UI, and in the debug.breakpoints list, with all the correct fields that you passed in the FunctionBreakpoint constructor.
|
2025-04-01T06:39:36.613778
| 2024-05-07T12:19:12
|
2283120898
|
{
"authors": [
"bruno-ribeiro-mck",
"kelleyjbrady"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8500",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/212165"
}
|
gharchive/issue
|
Ocasionally Commit & Push fails with "Actual command not found"
Type: Bug
Ocasionally I face the following error
Have pending changes
Click Commit & Push
See error notification
Next attempt works without issues
Developer Tools
10:54:07.622 notificationsAlerts.ts:40 Error: Actual command not found, wanted to execute git.commit /30
at r.h (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:153:189812)
c @ notificationsAlerts.ts:40
GIT Output
2024-05-07 10:54:04.887 [info] > git config --get commit.template [94ms]
2024-05-07 10:54:04.956 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/feature/<REDACTED> refs/remotes/feature/<REDACTED> [130ms]
2024-05-07 10:54:05.090 [info] > git status -z -uall [118ms]
2024-05-07 10:54:05.236 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/feature/<REDACTED> [114ms]
2024-05-07 10:54:05.380 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/feature/<REDACTED> [119ms]
2024-05-07 10:54:05.531 [info] > git config --local branch.feature/<REDACTED>.vscode-merge-base [94ms]
2024-05-07 10:54:05.531 [warning] git config failed: Failed to execute git
2024-05-07 10:54:05.647 [info] > git reflog refs/heads/feature/<REDACTED> --grep-reflog=branch: Created from *. [95ms]
VS Code version: Code 1.89.0 (b58957e67ee1e712cebf466b995adf4c5307b2bd, 2024-05-01T02:09:22.859Z)
OS version: Windows_NT x64 10.0.22631
Modes:
System Info
Item
Value
CPUs
12th Gen Intel(R) Core(TM) i7-1270P (16 x 2496)
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_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled
Load (avg)
undefined
Memory (System)
31.67GB (11.14GB free)
Process Argv
--folder-uri file:///c%3A/sources/Repos/FLT --crash-reporter-id 0ed2dc76-86cb-4e82-89ae-a98b71ec0a3f
Screen Reader
no
VM
0%
Extensions (15)
Extension
Author (truncated)
Version
vscode-tailwindcss
bra
0.10.5
copilot
Git
1.187.0
copilot-chat
Git
0.15.0
vscode-github-actions
git
0.26.2
rainbow-csv
mec
3.11.0
vscode-docker
ms-
1.29.1
vscode-dotnet-runtime
ms-
2.0.3
vscode-edge-devtools
ms-
2.1.5
data-workspace-vscode
ms-
0.5.0
mssql
ms-
1.22.1
sql-bindings-vscode
ms-
0.4.0
sql-database-projects-vscode
ms-
1.4.1
live-server
ms-
0.4.13
powershell
ms-
2024.2.1
vscode-thunder-client
ran
2.22.1
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
showvideot:31016892
chatpanelc:31018788
dsvsc021:30996838
724cj586:31013169
pythoncenvpt:31022790
fchga941:31038042
dwnewjupytercf:31035177
I experienced this error today. I was unable to commit with VSCode, but when I opened the repository with another git manager (I used GitExternsions), I was able to commit the changes which were generating the Actual command not found error in VSCode described above, presumably the CLI or another app would have also worked. After the successful commit with GitExtensions, committing within VSCode once again worked as expected.
|
2025-04-01T06:39:36.617557
| 2024-06-25T09:23:25
|
2372161497
|
{
"authors": [
"aiday-mar",
"justschen"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8501",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/217869"
}
|
gharchive/issue
|
Override less specific code action with more specific code action
Testing #217611
I set "source.fixAll": "always",. Saving the TS file in the example adds a semi-colon at the end of the second import. I added "source.fixAll.eslint": "never" and "source.fixAll.ts": "never" into that object. Saving the TS file also added a semi-colon at the end of the second import.
I think I was expecting that the more specific line would override the less specific one.
https://github.com/microsoft/vscode/assets/61460952/56b9cd37-bee8-4025-b053-28140ec4dde7
yep this is a known issue with how code actions on save work atm.
right now, we always take the larger superset, so if you have source.fixAll: ____, any other source.fixAll type codeactions will be overridden. we do support language specific overrides though, but i'm not sure if the correct choice is to allow the user with this many options.
|
2025-04-01T06:39:36.620385
| 2024-08-02T22:36:06
|
2445843163
|
{
"authors": [
"Tyriar",
"meganrogge"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8502",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/224652"
}
|
gharchive/issue
|
Build failed: shell integration - integration test failure
1 failing
1) vscode API - Terminal.shellIntegration
executeCommand(commandLine):
AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected
{
confidence: 2,
isTrusted: true,
+ value: 'e'
- value: 'echo hello'
}
+ expected - actual
{
"confidence": 2
"isTrusted": true
- "value": "e"
+ "value": "echo hello"
}
at Context.<anonymous> (/Users/runner/work/1/s/extensions/vscode-api-tests/src/singlefolder-tests/terminal.shellIntegration.test.ts:211:18)
Build: https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_build/results?buildId=286378
Changes: https://github.com/Microsoft/vscode/compare/331b772...b786d31
Happened again here https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_build/results?buildId=286444
Seemed to be a temporal issue as it hasn't been reported since these 2 occurrences on the same day.
|
2025-04-01T06:39:36.623238
| 2024-12-21T15:43:30
|
2754165156
|
{
"authors": [
"TwoBrushes",
"lszomoru"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8503",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/236779"
}
|
gharchive/issue
|
filter out the changed files listed in the git source code management panel in vscode
For some projects, making certain file modifications may result in a large number of associated changes. However, these changes are typically not ones I need to be concerned about. Therefore, I hope there is a filter to sort out the listed files for easier focus on the changes that matter to me.
When the "Source Control" view is focused you can press F3 to bring up the list find widget. You can search for the items that you are interested in, then press the "Filter" toggle on the right-hand side of the input field to only show the items that are matching the filter.
When the "Source Control" view is focused you can press F3 to bring up the list find widget. You can search for the items that you are interested in, then press the "Filter" toggle on the right-hand side of the input field to only show the items that are matching the filter.
Thank you for your reply, I tried it out, it's very good, but there is an issue, I can't use wildcards (such as *) when searching.
|
2025-04-01T06:39:36.638502
| 2018-09-26T22:53:56
|
364243190
|
{
"authors": [
"alexr00",
"bpasero",
"sandy081",
"sbatten"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8504",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/59500"
}
|
gharchive/issue
|
Commands executed via menu/contextmenu do not report error as notification
The built-in "Node Debug (legacy)" extension depends on "Node Debug".
Try to disable "Node Debug" but nothing happens, presumably because it has a dependency
Try to disable "Node Debug (legacy)" and it works
Then, also disable "Node Debug" and now it works, presumably because the dependency is gone
Finally, try to enable "Node Debug (legacy)" and it works?! and also automatically enabled "Node Debug"
To be consistent, if it is possible to enable "Node Debug (legacy)" when "Node Debug" is disabled and automatically enable "Node Debug" then it should also be possible to disable "Node Debug" and have "Node Debug (legacy)" also be automatically disabled.
This is also confusing because there's no indication why nothing happened when I clicked on Disable on "Node Debug" while "Node Debug (legacy)" is enabled.
Try to disable "Node Debug" but nothing happens, presumably because it has a dependency
You see an error at the bottom right that there is an extension (Node Debug Legacy) depends on it
Try to disable "Node Debug (legacy)" and it works
👍
Then, also disable "Node Debug" and now it works, presumably because the dependency is gone
👍
Finally, try to enable "Node Debug (legacy)" and it works?! and also automatically enabled "Node Debug"
Yes, enabling/installing an extension also installs its dependency. If a user is trying to enable/install an extension, it is implied dependencies too.
To be consistent, if it is possible to enable "Node Debug (legacy)" when "Node Debug" is disabled and automatically enable "Node Debug" then it should also be possible to disable "Node Debug" and have "Node Debug (legacy)" also be automatically disabled.
Other way around is not good. Uninstalling / Disabling dependencies of an extension together might not be expected and users would have installed them independently. It was this behaviour (with prompt) but I should say it was not the best. Hence made disablement and uninstalling independent.
This is also confusing because there's no indication why nothing happened when I clicked on Disable on "Node Debug" while "Node Debug (legacy)" is enabled.
There is. As I said you see error prompt at the bottom right
I don't get the error prompt at all :(
Strange I see it. May be try with all extensions disabled?
I disabled all extensions then restarted VS Code. Still nothing ☹️ What other info can I collect for you?
Node Debug and Node Debug (legacy) don't appear to be installed when I run from dev (e0e2738819c0f) I'm looking for another pair to try with. Let me know if you know of one or if there's a good way to check extension dependency.
Tried with the GitHub Pull Requests extension and the built-in Git extension. Same results: when I try to disable the Git extension it does not disable (👍) but there is no notification(👎).
@alexr00 Can you please breakpoint at the following line and see if it is getting hit?
https://github.com/Microsoft/vscode/blob/a144e2fa9fc2fb91a8add05833943a00f3b86371/src/vs/workbench/parts/extensions/node/extensionsWorkbenchService.ts#L775
If it is, can you please check why the error is not being notified?
@sandy081, the error tries to fire, but in event.ts on line 132 this._listeners is undefined. this._deliveryQueue is also undefined at the start of the fire function.
@bpasero
For @alexr00 When an action is executed and returns an error, it is not notified.
https://github.com/Microsoft/vscode/blob/4b427941dc20b303e35c7687924a4a92f73c4c20/src/vs/workbench/parts/extensions/electron-browser/extensionsActions.ts#L729
Any insights?
Any insights?
Any steps?
Try to disable an extension which is a dependent of some other extension. You can try disabling Node Debug or install Pull Request Extension and disable Git. You should see an error notification.
@sbatten I can reproduce and it looks like neither our custom context menu nor our native context menu delegate failing actions to a notification service to show the error. I think we should probably hook that in. I think this is not a recent regression, this probably never worked properly (or at least for a while).
Maybe we should open a separate issue for the menu issue, up to you @sandy081
I think its fine to use this issue and update the summary or description if needed.
I don't know when or how this was fixed, but I can not reproduce any longer. @bpasero @alexr00 to verify?
I can still reproduce by trying to disable Node Debug.
Correct. I don't see that prompt. It looks as though nothing happens when I try to disable Node Debug.
@alexr00 do you see the error in the devtools console?
No, I don't see the error in the devtools console. I just get this when I right click:
dom.ts:213 [Violation] Added non-passive event listener to a scroll-blocking 'mousewheel' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
@alexr00 oh im stupid, I was using the gear menu, not the context menu to disable. I can repro
@alexr00 this seems to be resolved for the context menu now, tested disabling git Hopefully I did not misread again, but please try it out.
|
2025-04-01T06:39:36.641575
| 2019-05-18T18:33:04
|
445742389
|
{
"authors": [
"gregvanl",
"jamesralstin"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8505",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/73946"
}
|
gharchive/issue
|
Add link in "How-To-Contribute" to GitHub Fork Help Page
In the "How-To-Contribute" wiki page under the "Getting the sources" subsection, recommending a hyperlink to the "Fork A Repo" GitHub article for users/developers that might be new to the term "Fork", albeit familiar with the concept. Also maybe a link to "Clone" as well.
Hi @jamesralstin Thank you for your suggestion. I'm reluctant to add links, that we would have to maintain if they move. Forking and cloning are part of the basic vocabulary of open-source development and I'd rather users searched and found their own guidance, which matches their level (beginner, advanced, refresher).
|
2025-04-01T06:39:36.650520
| 2019-05-25T13:10:39
|
449648910
|
{
"authors": [
"awto",
"isidorn"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8506",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/74516"
}
|
gharchive/issue
|
Forcing setBreakpoints request on sources change
I now work on JavaScript debugger plugin based on code instrumentation, this should allow time traveling and hot reloading during a debugging session.
I reload modules using Hot Module Replacement keeping all the state from the former version. This works except if I add a new line into a source all breakpoints become unverified, which is obviously right since their position is changed. Toggling one them sends setBreakpoints for the whole module and they are back verified and functioning.
I can workaround this using 'breakpoint' event, however, the back-end doesn't know its new correct position, resetting it to the former line looks pretty random.
Is there is some way to force resending setBreakpoints for a changed module? Or can the client send it on, say, loadedSource event?
Currently we send the setBreakpoints request when the user has manually changed breakpoints in some way (by adding them, disabling/enabling them...).
When the initiazlied event arrives. When the file with breakpoints got deleted.
Currently the client does not send them for the loadedSource event and there is no way to force the cliend to send the setBreakpoints request programatically.
Thus leaving this open as a feature request.
@isidorn would you accept a PR if I do this?
@awto not at the moment. Since this feature is not requested and we did not plan to have it yet.
Maybe in the future we might reconsider. Thanks
@isidorn do you mean the code hot swapping feature isn't requested? Many debuggers has it and it is actually great. In fact this issue looks more like a bug to me not a feature, why do you need loadedSources event after all.
But ok, for now I'm going to hack this by toggling some breakpoint twice via debugger service, my adapter runs in the same process. If there is some other better way to convey the new breakpoint positions, I would be happy to know.
Thanks.
@awto there is currenly no feature reqeust for code how swapping as far as I know. Though feel free to open a new feature request.
Thanks
@isidorn I work now on a JS debugger which supports hot swapping among a few other nice things, and the hot swapping does already work there. Except all the breakpoints are deactivated, untill I toggle one of them (so "setBreakpoints" is sent again).
I'm not sure if such feature request really belongs here, as this is a feature of an adapter (and debuggee). From the vscode side every feature needed is already there, except this small issue - no way to update breakpoints position. Which I would guess should be a part of loadedSources response, so I wouldn't call this issue a feature at all.
I can workaround this (if my adapter runs in the same process), but the purposes of loadedSources event isn't clear though.
How do the breakpoint get deactivated? Do they say Unverified breakpoint. File is modified, please restart debug session on hover or something else?
I can, and I tried this, but since on adapter and debuggee sides I don't know the new breakpoint positions, if someone, say, adds a line into text. So I tried to resend the same positions I know from the last setBreakpoints, this sets their possition on a quite random looking line.
Do they say Unverified breakpoint. File is modified, please restart debug session on hover or something else?
yes, this message, and when I toggle one of them everything is back to normal, since the setBreakpoints request is resent.
@isidorn I've just checked the recent version and IDE does send now setBreakpoints on source file changed. This is not on loadedSource event though, but it is pretty enough for me. I don't know, maybe this didn't work the same on May, or it is just me. Thanks a lot!
Welcome. I have been doing some refactoring in that area and seems like I fixed it hooray.
|
2025-04-01T06:39:36.656308
| 2019-06-02T11:50:18
|
451183174
|
{
"authors": [
"FuriouZz",
"Tyriar"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8507",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/74748"
}
|
gharchive/issue
|
Integrated terminal seems to clear at startup
Environment
VSCode Version: 1.34.0
OS Version: Windows 10
Problem description
The integrated terminal seems to truncate output. At VSCode startup or Reload Windows, the terminal does not show anything. I got a big blank space. If I pressed "Enter", it outputs something.
The problem seems to be the same with tasks, I got a big blank space but I do not have the output of the task.
Instead of :
The result is same with powershell.exe and cmd.exe. I do not have the problem with wsl.exe, exception for the task that did not found cargo...different problem I suppose...
Steps to reproduce
Set your shell to powershell.exe
"terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
Restart VSCode/Reload VSCode windows and display the terminal
Does this issue occur when all extensions are disabled?: Yes
This is a bug in Windows 10 1809, unfortunately we have no way to work around the issue so you will need to wait until you get the next version of Windows 10 (1903).
/duplicate https://github.com/Microsoft/vscode/issues/57803
|
2025-04-01T06:39:36.658773
| 2019-06-03T14:48:37
|
451526537
|
{
"authors": [
"Pavelbure34",
"kieferrm"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8508",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/74793"
}
|
gharchive/issue
|
html failed to save due to unknown file system error. it has been consistent with every html file I created and edited with VSCode.
VSCode Version:1.34
OS Version:Windows 10 Pro
Steps to Reproduce:
1.write anything on index.html
2.save it then sometime soon eventually it cannot be saved.
Does this issue occur when all extensions are disabled?: Yes/No
@Pavelbure34 same happens when you start VS Code from the command line with code --disable-extensions?
/needsMoreInfo
|
2025-04-01T06:39:36.663992
| 2019-07-04T10:32:35
|
464192889
|
{
"authors": [
"Tyriar",
"bpasero",
"byyxx128",
"gudvinr"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8509",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/76590"
}
|
gharchive/issue
|
User data: migrate Backups, Workspaces, user state into %APPDATA%/User
Today we have a bit of a mix in our %APPDATA% folder: a lot of stuff is going into the %APPDATA%/User folder but a few things outside are not:
Backups
Workspaces
storage.json
I think we should do a migration step for a while to consolidate this data under the User folder.
@Tyriar also happy for your input given you are the author of https://github.com/Microsoft/vscode/issues/3884
I removed part of the description. Specifically we can leave the backup format as it is today where we have a folder per scheme, even though that is not really needed if we take the hash of the full resource.
Is this just cleanup or is there a bigger problem with the folders being there?
@Tyriar I think it would bring us closer to a model where all of our data goes into one folder "User" and the rest is a) chrome stuff and b) some caches that can be ignored.
E.g. we could then start to think about nuking anything which is not in "User" to ensure a cleaner startup (e.g. no traces of previous chrome stuff around).
:+1: sounds good
What about extensions? Why is the extensions directory located in ~/.vscode/ rather than %APPDATA%/User?
I think very much in the beginning we were worried that Windows would automatically roam the stuff that is inside %APPDATA% so we decided to not put extensions in there. I also find it a bit unfortunate that we require 2 folders on disk to store stuff.
As mentioned in #3884, the optimum location for extensions is %LOCALAPPDATA% rather than %APPDATA%.
I expect to see the transition during my lifetime. 😁
|
2025-04-01T06:39:36.666285
| 2019-07-09T13:19:20
|
465776440
|
{
"authors": [
"aeschli",
"dbaeumer"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8510",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/76983"
}
|
gharchive/issue
|
Smoke test failure in CSS for 1.36.1
Smoke test failure under Windows testing 1.36.1
** Timeout!
Error: Active element not found. Current active element is 'HTML > BODY.vs-dark.vscode-theme-defaults-themes-dark_plus-json.file-icons-enabled.windows'. Looking for .monaco-editor[data-uri$="settings.json"] textarea
at m.<anonymous> (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:2208:775)
at Generator.next (<anonymous>)
at file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:35:460
at new Promise (<anonymous>)
at n (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:35:237)
at m.isActiveElement (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:2208:467)
at call (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:1386:581)
at C.onPromise (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:316:346)
at C.onRawMessage (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:315:994)
at C.protocolListener.protocol.onMessage.e (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:315:531)
at d.fire (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:79:760)
at EventEmitter.n (file:///C:/apps/VSCode/1.36.1/resources/app/out/vs/workbench/workbench.main.js:77:206)
at EventEmitter.emit (events.js:182:13)
1) verifies that warning becomes an error once setting changed
I can successfully run the smoketest on 1.38on Windows
|
2025-04-01T06:39:36.699632
| 2019-11-27T14:20:57
|
529376702
|
{
"authors": [
"alexandrudima",
"yanniszark"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8511",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/85694"
}
|
gharchive/issue
|
Vertical Select with middle click is not working
Issue Type: Bug
In older versions of VSCode, I did vertical selection by clicking the middle button on the mouse and dragging.
It seems like this doesn't work anymore.
VS Code version: Code 1.40.1 (8795a9889db74563ddd43eb0a897a2384129a619, 2019-11-13T16:49:30.162Z)
OS version: Linux x64 5.0.0-36-generic snap
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 x 1960)
GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled
Load (avg)
4, 2, 1
Memory (System)
7.76GB (0.16GB free)
Process Argv
--force-user-env --no-sandbox --unity-launch --no-sandbox
Screen Reader
no
VM
0%
Extensions (4)
Extension
Author (truncated)
Version
plantuml
jeb
2.13.5
intellij-idea-keybindings
k--
0.2.37
python
ms-
2019.11.50794
vscode-yaml
red
0.6.1
@yanniszark In some Linux distributions, middle clicking is reserved for moving windows. Did you perhaps change window compositors, or have upgraded your distribution since it last worked? Does middle clicking work for you in other applications?
@alexandrudima thanks for the response!
I'm working on Ubuntu 18.04.
This is the output of lsb_release -a:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
In Jetbrains Goland, vertical selection with middle click works as expected.
Thanks for your quick reply.
VS Code is built with Electron, which is built with Chromium. Can you please try opening https://vscode-web-test-playground.azurewebsites.net (it might take a long time to load) in Chromium on the same machine? Does using the middle mouse button work there?
@alexandrudima I loaded the web page and the middle click vertical select still doesn't work.
When I try to select vertically, it just selects normally.
Also, middle click for paste works.
Also, middle click for paste works.
Aha! Thanks for the last extra detail to jog my memory. Indeed, the middle mouse button by default will paste the selection clipboard on Linux. You can disable that via "editor.selectionClipboard": false. Once the selection clipboard is disabled, the middle mouse button can be used for column selection.
@alexandrudima yes that was it!
Thanks a lot for the help!
I can now go back to my favorite editor :smile:
|
2025-04-01T06:39:36.704714
| 2020-04-01T00:57:12
|
591540920
|
{
"authors": [
"chrisdias",
"connor4312",
"isidorn",
"kieferrm"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8512",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/94094"
}
|
gharchive/issue
|
cannot reference $returnValue in logpoint
testing https://github.com/microsoft/vscode/issues/93807
Not sure if this should work or not, but what the heck I'll give it a try!
In the debug console, I get this:
this is the ReferenceError: $returnValue is not defined
at eval (logpoint-bce3f6f.cdp:3:5)
at eval (logpoint-bce3f6f.cdp:7:3)
at helloWorld (/Users/chris/src/test93807/index.js:6:16)
at Object.<anonymous> (/Users/chris/src/test93807/index.js:10:11)
at Module._compile (internal/modules/cjs/loader.js:956:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
at Module.load (internal/modules/cjs/loader.js:812:32)
at Function.Module._load (internal/modules/cjs/loader.js:724:14)
at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)
at internal/main/run_main_module.js:17:11
Living loco @chrisdias
Though forwarding to @connor4312 since he is the author of that test plan item
Thanks for the issue! Unfortunately this won't work because the $returnValue is only available after stepping over the return statement, but breakpoints can't be set there.
@connor4312 In the following code
function foo() {
const val = [];
for (let i = 0; i < 20; i++) {
val.push(bar(i));
}
return val;
}
function bar(i) {
return {
code: i,
message: `msg ${i}`
};
}
foo();
I can set a breakpoint on line 13. When this one is hit $returnValue is defined. However logpoints referencing $returnValue fail and conditional breakpoints referencing $returnValue are never hit. When are those conditions being evaluated? In this case I'd guess after the return value was evaluated.
Ah, okay. I'll check on this.
Fixed in the linked commit. Note that, as mentioned, you need to make sure the logpoint is set after the return statement, since before it's evaluated the call frame's return value is not set. If compiling to js, the sourcemaps might already be set up like this.
|
2025-04-01T06:39:36.706677
| 2020-04-23T17:15:16
|
605706628
|
{
"authors": [
"connor4312"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8513",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/95989"
}
|
gharchive/issue
|
Build initial renderer starter code sample/repo
Refs: #95908
Create a sample renderer repo with all the good defaults. To be converted to a yeoman generator later.
Created in https://github.com/microsoft/vscode-notebook-renderer-starter
|
2025-04-01T06:39:36.711674
| 2020-05-27T06:10:12
|
625407574
|
{
"authors": [
"egamma",
"zehongs"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:8514",
"repo": "microsoft/vscode",
"url": "https://github.com/microsoft/vscode/issues/98636"
}
|
gharchive/issue
|
Can't view images when doing ssh-remote, port other than 22 is used.
VSCode Version: 1.46.0-insider
OS Version: Catalina 10.15.4; Darwin x64 19.4.0
Why I can't view an image through ssh-remote mode?
My situation is port22 is disabled, and I login by ssh -p NUMBER name@ip -A, where the host listens to that port.
Steps to Reproduce:
Login to ssh-remote with -p specified. Simply can't view images in any window/tab.
Does this issue occur when all extensions are disabled?: Yes
/needsMoreInfo
Please provide more detailed steps for how to reproduce the problem.
Are you using a VS Code Remote extension? What other extensions are you using?
Hi, @egamma
I disabled all extensions except for remote-ssh.
This happens only for insider-version. Since I also have a 1.45.1 code-stable-version, I tested on that, and all things went on well.
I can't say how to reproduce the problem. Since I just can't open an image or load a jupyter notebook(the kernel is started but the view doesn't appear) .
Could you give me some suggestions where to look for? like logfiles, check some port settings ?
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.