primordic/IssueDupesLite huggingface dataset:
Repository: microsoft/language-server-protocol

Issue #7: Add support for lexical syntax coloring
Created: 2016-05-19T06:31:34Z
I know lexical coloring is something that should be done on the client. However as this information is fully declarative (TextMate language grammars) we could serve the initial configuration from a language server instead of putting it into the extension json.
The reason is that I would like to define and package one language server and use it in many different editors as is. I.e. without the need to do some editor specific plumbing for every editor. Today only VSCode understands this protocol, but we should try to make it more widely used in order to leverage its full potential. I.e. we are working on a client for Che and on a server side implementation with Xtext.
For servers that only target vscode It could be simply ignored and turned off through the server capabilities.

Duplicate issue #120: Token based Highlighting vs. Self Containing Extensions
Created: 2016-11-09T07:55:46Z
Since (as given by VSCode as example) textMate Grammars seem to be a defacto standard for doing token/grammar based highlighting we have a "thing" in lsp that prevents us from language servers beeing self contained. we always need a side channel to provide the text mate grammars as vscode does it through the configuration in package.json.
it would be nice to have a service in the protocol that allows the servers to deliver the grammars to the client or alternatively a service that does grammar based highlighting server side.

Closing comment (2016-11-21T21:54:49Z): Thanks @svenefftinge. It is a dup of #7. I think if we open up the protocol for sematic classification then we can also support syntax classification. However syntax classification has the pre-requisite that it has to be fast and accurate during typing. So this must be defined in a clever way.
Dups #7 and #18. Lets continue the discussion in #18.
Repository: microsoft/language-server-protocol

Issue #1853: Specify exactly what "the client will normalize line ending characters" means
Created: 2023-12-08T09:39:03Z
I recently hit a weird but where our formatter was changing \n in a document to \r\n. Because we have a step to minimize edits (because otherwise things like breakpoints could be lost), the edit was reduced to "insert \r before the \n".
However, in VS Code this resulted in \n\n in the document instead of \r\n which meant a new blank line appeared between every line of code:

  
    
    

    format.mp4
    
  

  

  


I filed microsoft/vscode#200157 but this is considered by design. IMO this is not obvious behaviour from the current spec, and for servers not to produce edits that mess up a users code, the rules need to be clear.
So, I think the comments on the WorkspaceEditClientCapabilities.normalizesLineEndings class field need to clearly describe the rules of normalisation so that clients and servers have the same expectations/behaviour.
@dbaeumer I'm happy to send a PR detailing VS Code's behaviour if you think it's reasonable to define this as the LSP behaviour.

Duplicate issue #1800: Clarify how a server can know which line ending sequence to use (LF or CRLF) when inserting text
Created: 2023-09-05T05:12:17Z
#1021 adds the normalizesLineEndings client capability to 3.16
When true, does this guarantee that the server is free to insert text with either '\n' or '\r\n' and the client guarantees to perform the appropriate conversion? Or should the server always use '\n'?
When false or null, is there a way to know which line ending mode the editor is in for a particular document? i.e. for a server to insert line endings that are consistent with what happens when the user presses the enter key in an empty document.
Or does the server have to manually detect the line ending mode of each document based on the document's text? (Obviously this will fail for empty documents, hence my questions above).

Closing comment (2023-12-11T14:35:55Z): Marking as dup of #1853
Repository: microsoft/language-server-protocol

Issue #18: Support semantic highlighting
Created: 2016-06-28T03:42:25Z
Like WebStorm and VS does: eg. Symbol is a type or parameter or namespace or unresolved ...
Textmate based grammars are hard to do this. Since we did support Diagnostics, why not support semantic highlighting?

Duplicate issue #1017: Delimitate regions eligible for spell checking.
Created: 2020-06-10T07:48:13Z
A discussion started at neovim about the benefits that LSP could bring to spell checking, but I'm not sure whether this has been discussed here yet.
The LSP server is very aware of the file structure and programming language specificities, which makes it a very good candidate for delimiting regions eligible to spellchecking (comments, docstrings, strings maybe, variable names maybe, etc.).
Could this spellcheck-regions-delimiting activity be part of the protocol? What would it imply in terms of coordination with existing spellcheckers/editors?
The most basic support would be to not delimitate anything and return the whole file as one big region, leaving the burden of ignoring keywords, etc. to the spellchecker itself. Such a trivial implementation is dummy, but it would still be useful in 2 cases I think:

For a not-a-programming-language-LSP server, dedicated to parse plain, free .txt-like files written in natural language.
For transient, basic support in other LSP servers, as a temporary solution so they comply to the protocol even though they have not implemented precise region-delimiting logic yet.

Closing comment (2020-06-10T12:57:59Z): I think this is partly related to #18 . Semantic Highlighting actually seems to involve file tokenization and the LS returning file tokens to the client for further styling.
The "natural language text" could then be just a token type.
Repository: microsoft/msquic

Issue #895: Centos build instructions
Created: 2020-10-08T22:27:15Z
Describe the feature you'd like supported
Currently there are build instructions for ubuntu releases but some clusters are running on centos so it's better to have instructions for that platform as well

Duplicate issue #894: Build instructions for Centos 7/8
Created: 2020-10-08T22:26:27Z
Describe the feature you'd like supported
Currently there are build instructions for ubuntu releases but some clusters are running on centos so it's better to have instructions for that platform as well

Closing comment (2020-10-08T22:36:29Z): Closing this one, since it's pretty much the same as #895.
Repository: microsoft/msquic

Issue #1553: Client UDP Stops Working
Created: 2021-05-06T18:45:01Z
Describe the bug
I was looking at a recent one-off test failure's logs and it seems that after some time, we just stop getting any UDP operations (send or receive) on the client side. This happened with the Windows user mode client, and I have no reason to believe it would affect any other platform specific data path. No errors were spit out, which seems to indicate that we're posting completions to the IOCP but they aren't happening somehow. Only seen this the one time so far...
quic.log

Duplicate issue #1840: Misc/WithCidUpdateArgs.CidUpdate/1 failed
Created: 2021-07-22T19:12:56Z
Describe the bug
https://dev.azure.com/ms/msquic/_build/results?buildId=202861&view=logs&j=447b0da9-5035-5469-48f6-77c6f2394c86&t=0d2508b2-4515-5db4-46f9-9caef08c861a
This failure was seen on a PR run of the BVTs:
[----------] 1 test from Misc/WithCidUpdateArgs
[ RUN      ] Misc/WithCidUpdateArgs.CidUpdate/1
D:\a\1\msquic\src\test\lib\HandshakeTest.cpp(2039): error: Server->GetLocalBidiStreamCount() not equal to (uint16_t)(101+i)
[  FAILED  ] Misc/WithCidUpdateArgs.CidUpdate/1, where GetParam() = v4/2 (225 ms)
[----------] 1 test from Misc/WithCidUpdateArgs (225 ms total)

Logs: cidupdate.log

Closing comment (2021-09-14T17:13:13Z): After looking into the logs, this seems to be a duplicate of #1553 where we just stop getting receive indications.
Repository: microsoft/msquic

Issue #1795: Document all Stream, Connection, and Listener Events
Created: 2021-07-03T01:21:43Z
It would be great to have a list of events and event descriptions that can occur for each msquic handle.

Duplicate issue #4700: Improve Documentation for Listener Callbacks
Created: 2024-12-10T13:42:13Z
Discussed in #4698

Originally posted by Streamlet December 10, 2024
The documents for quic functions is very detail, but there is few for callbacks.
Would you add more documents for each parameters of each kind of callbacks?

Closing comment (2025-02-25T12:35:09Z): Resolving as duplicate of #1795.
Repository: microsoft/msquic

Issue #1912: MsQuicConnection on Linux
Created: 2021-08-13T09:46:50Z
MsQuicConnection depends on InterlockedIncrement` which is a Windows API
Is there support for Linux/POSIX?

Duplicate issue #1920: Use of InterlockedIncrement in msquic.hpp
Created: 2021-08-15T08:50:56Z
I am using Ubuntu 20.04 and gcc 9.3.0.
When I include the header src/inc/msquic.hpp in a project I get an "‘InterlockedIncrement’ was not declared in this scope" error (used in line 1032) as it is a WIN API function call. I found no parallel for it in Linux.
Is this by design?
Am I missing a header possibly?
Thanks.

Closing comment (2021-08-15T15:51:32Z): Duplicate of #1912. Please see the discussion there.
Repository: microsoft/msquic

Issue #1727: Basic/WithFamilyArgs.PathValidationTimeout/1 failed
Created: 2021-06-16T17:58:09Z
Describe the bug
Latest main pipeline has the following test failure on Windows user mode BVT:
https://dev.azure.com/ms/msquic/_build/results?buildId=180914&view=logs&j=c40b63a5-7dbb-5cb5-fce9-4bc98709706d&t=db2c8b2a-4837-55b9-0021-0a534936d219&l=366
[ RUN      ] Basic/WithFamilyArgs.PathValidationTimeout/1
D:\a\1\msquic\src\test\lib\TestConnection.cpp(184): error: WaitForShutdownComplete timed out after 2000 ms.
[  FAILED  ] Basic/WithFamilyArgs.PathValidationTimeout/1, where GetParam() = v6 (2343 ms)

Logs: PathValidationTimeout.log

Duplicate issue #1776: Basic/WithFamilyArgs.PathValidationTimeout/0 failed
Created: 2021-06-27T16:01:40Z
Describe the bug
On a recent CI run, we encountered the following test failure:
https://dev.azure.com/ms/msquic/_build/results?buildId=185954&view=logs&j=17cf080e-109c-5845-c927-1dbcdd652708&t=0c281c51-0e35-595d-7225-a7811f0c4226&l=370
[ RUN      ] Basic/WithFamilyArgs.PathValidationTimeout/0
D:\a\1\msquic\src\test\lib\TestConnection.cpp(184): error: WaitForShutdownComplete timed out after 2000 ms.
[  FAILED  ] Basic/WithFamilyArgs.PathValidationTimeout/0, where GetParam() = v4 (2373 ms)

Logs: PathValidationTimeout.log
1815 [0]1544.1AE4::‎2021‎-‎06‎-‎27 01:33:27.573 [Microsoft-Quic][conn][0x1E146B757B0] LOSS_DETECTION timer expired 
1859 [0]1544.1AE4::‎2021‎-‎06‎-‎27 01:33:27.573 [Microsoft-Quic][conn][0x1E146B757B0] Cannot send any more because of amplification protection 
1871 [1]1544.0D34::‎2021‎-‎06‎-‎27 01:33:28.773 [Microsoft-Quic][test] FAILURE - D:\a\1\msquic\src\test\lib\TestConnection.cpp:184 - WaitForShutdownComplete timed out after 2000 ms.

Closing comment (2021-06-27T16:02:12Z): Might be a dup of #1727? @ThadHouse?
Repository: microsoft/msquic

Issue #1805: Basic/WithFamilyArgs.LocalPathChanges/0 Test Failure
Created: 2021-07-09T22:03:24Z
Describe the bug
https://dev.azure.com/ms/msquic/_build/results?buildId=193142&view=logs&j=117cea68-5cbd-59c3-b438-3dc3522134d8&t=66e7dc66-7e7c-5560-3fec-16812f94817e&l=337
[ RUN      ] Basic/WithFamilyArgs.LocalPathChanges/0
/home/vsts/work/1/s/src/test/lib/PathTest.cpp:105: Failure
Context.PeerAddrChangedEvent.WaitTimeout(1500) not true
[  FAILED  ] Basic/WithFamilyArgs.LocalPathChanges/0, where GetParam() = v4 (1507 ms)

Logs: LocalPathChanges.log

Duplicate issue #1993: Basic/WithFamilyArgs.LocalPathChanges/0 Failure
Created: 2021-09-15T18:19:10Z
Describe the bug
https://dev.azure.com/ms/msquic/_build/results?buildId=221837&view=logs&j=117cea68-5cbd-59c3-b438-3dc3522134d8&t=66e7dc66-7e7c-5560-3fec-16812f94817e&l=345
[ RUN      ] Basic/WithFamilyArgs.LocalPathChanges/0
/home/vsts/work/1/s/src/test/lib/PathTest.cpp:105: Failure
Context.PeerAddrChangedEvent.WaitTimeout(1500) not true
[  FAILED  ] Basic/WithFamilyArgs.LocalPathChanges/0, where GetParam() = v4 (1538 ms)
[----------] 1 test from Basic/WithFamilyArgs (1538 ms total)

LocalPathChanges.log

Closing comment (2022-08-09T14:39:57Z): Closing as duplicate of #1805.
Repository: microsoft/msquic

Issue #2975: published Linux packages do not state dependency on libcrypto.so.1.1 
Created: 2022-08-12T17:51:40Z
Describe the bug
This is related to dotnet/arcade#10253
libmsquic package was installed on .NET test queues but tests dir not run successfully.
After some investigation I found there are missing dependencies:
toweinfu@toweinfu-u22:~$ ldd /usr/lib/x86_64-linux-gnu/libmsquic.so.2.1.0
	linux-vdso.so.1 (0x00007ffd9b1fe000)
	libcrypto.so.1.1 => not found
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fd21fcd6000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fd21fcd1000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd21faa9000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fd21fe32000)

It is going to be confusing for users if the package installs but does not work. We should properly claim dependencies so

the package would fail to install on old distributions where openssl 1.1 is not available (with possible --no-dpes override)
dependencies are installed automatically where available

Affected OS

 All
 Windows Server 2022
 Windows 11, version 22H2
 Windows 11, version 21H2
 Windows Insider Preview (specify affected build below)
 Ubuntu
 Debian
 Other (specify below)

Additional OS information
No response
MsQuic version
main
Steps taken to reproduce bug
apt-get install libmsquic
Expected behavior
libmsquic is useable
Actual outcome
libmsquic may miss dependencies
Additional details
No response

Duplicate issue #3393: Update packages to prevent installation on Debian 12+ and Ubuntu 22.04+
Created: 2023-02-03T18:58:10Z
Describe the feature you'd like supported
The msquic packages don't work on platforms that exclusively offer OpenSSL 3. It shouldn't be possible to install the msquic .deb packages on those distros.
As you can see, I was able to and had a bad experience: #3375 (comment)
Proposed solution
Do one or more of:

Add an OpenSSL 1.x package dependency.
Remove msquic from feeds where it is known to not work.
Adopt a static linking model.

Additional context
No response

Closing comment (2023-02-03T19:35:23Z): #3390 is unrelated e.g. that is build problem. What you describing is essentially dup of  #2975.
Repository: microsoft/node-pty

Issue #72: data events can be fired after exit is fired
Created: 2017-04-03T18:55:08Z
Downstream issue/repro: microsoft/vscode#23051
Temporary fix: microsoft/vscode@9464b54
Relevant commit that tried to fix the problem: chjj/pty.js@4af6285

Duplicate issue #85: Doesn't Always Display the Whole Output 
Created: 2017-06-02T15:30:26Z
On Linux, running a command with node-pty sometimes truncates the end of the output. Steps to reproduce:

docker run -it node bash

Then inside docker:

npm install node-pty
curl https://gist.githubusercontent.com/vlad-shatskyi/d3820878733294d8e12571eab207885b/raw/e644351d9a8bc81ea97e8797e696a7cc5a757f24/output > output
node -e "require('node-pty').spawn('cat', ['output']).on('data', data => console.log(data))"

I obfuscated the output, but note that sometimes the lines with dashes aren't printed.
It seems that onread isn't called the last time. https://github.com/nodejs/node/blob/master/lib/net.js#L568
A possibly related issue: nodejs/node-v0.x-archive#6595
This issue is also present in pty.js.
If you run the command with NODE_DEBUG=NET, it shows that the last chunk of data has a negative nread value:
NET 435: _read
NET 435: onread -4095
NET 435: EOF

Closing comment (2022-12-27T12:03:23Z): duplicate of #72
Repository: microsoft/node-pty

Issue #73: proposal: gain granularity under UNIX by refactoring of the module
Created: 2017-04-08T16:17:57Z
@Tyriar Not sure how to name it - well I think at least the unix part of this module is kinda broken by design. I've done some own investigations by trying out a much simpler pty implementation under linux and came to the following conclusion:
The C part of the module does to much at once, esp. the Ptyfork is heavy weighted - it tries to deal with forkpty, termios settings, the exec* call and registering of the waitpid callback at once - my prosopal is to separate those things into single calls exported to JS and gain much more interactivity in JS land. Also it would make pty.open useful again. Atm pty.open  is a dead end since the needed symbols from C are missing.
Changes of my proposal:

export forkpty in C semantics
export exec* functions in C semantics
export fork (to be used with openpty)
export wait* functions
some more basic C functions regarding tty file descriptors

Note that those changes would degrade the module to basic C semantics. Therefore it would need to set up higher level stuff in UnixTerminal.

Duplicate issue #142: Why IEXTEN?
Created: 2017-09-13T00:34:04Z
Why does node-pty have the IEXTEN flag enabled? It has the effect of barring bytes 0x0f and 0x16 from reaching the child process.
It might be nice to have an option to disable this.

Closing comment (2021-10-21T18:59:09Z): duplicate of #73, https://github.com/jerch/node-termios is current workaround
Repository: microsoft/node-pty

Issue #73: proposal: gain granularity under UNIX by refactoring of the module
Created: 2017-04-08T16:17:57Z
@Tyriar Not sure how to name it - well I think at least the unix part of this module is kinda broken by design. I've done some own investigations by trying out a much simpler pty implementation under linux and came to the following conclusion:
The C part of the module does to much at once, esp. the Ptyfork is heavy weighted - it tries to deal with forkpty, termios settings, the exec* call and registering of the waitpid callback at once - my prosopal is to separate those things into single calls exported to JS and gain much more interactivity in JS land. Also it would make pty.open useful again. Atm pty.open  is a dead end since the needed symbols from C are missing.
Changes of my proposal:

export forkpty in C semantics
export exec* functions in C semantics
export fork (to be used with openpty)
export wait* functions
some more basic C functions regarding tty file descriptors

Note that those changes would degrade the module to basic C semantics. Therefore it would need to set up higher level stuff in UnixTerminal.

Duplicate issue #134: spawn vs open and buggy behaviour.
Created: 2017-08-11T03:38:01Z
I've been having an odd issue with PTY.open and ChildProcess.spawn.
In particular, with this combination, then running htop and feeding data between node-pty and xterm.js, I can cause Atom editor to completely lock up with no hope of recovery, and in addition to that, all developer tools eventually break as you try to debug the issue.
I've avoided the problem by moving to PTY.spawn.
I wish I could provide more details, but at the very least I can state the problems is present in the 2.1.2 release of script-runner: https://github.com/ioquatix/script-runner/tree/v2.1.2
To reproduce the issue:

Install Atom 1.19.0
Install Script Runner 2.1.2 by cloning the above repo into your ~/.atom/packages directory.
Run atom ~/.atom/packages/script-runner
In the examples directory, run htop.sh.
Using the scroll wheel or trackpad, scroll htop up and down rapidly. It should eventually crash.

I was developing this and reproducing this crash on Mac OS X, but I believe it also shows up on linux.
I don't know why it crashed, but the solution was to change from:
this.pty = PTY.open()
this.child = ChildProcess.spawn(args[0], args.slice(1), cwd: cwd, env: env, stdio: [this.pty.slave, this.pty.slave, this.pty.slave], detached: true)
to
this.pty = PTY.spawn(args[0], args.slice(1), {
	cols: this.view.terminal.cols,
	rows: this.view.terminal.rows,
	cwd: cwd,
	env: env,
	name: 'xterm-color',
});
As I've made this change, I no longer have the issue. However, the first approach should work and I think I prefer it since it's more explicit.
Perhaps you would see I'm doing something wrong or making the wrong assumption. If that's the case, please accept my apologies for being ignorant.

Closing comment (2021-10-21T18:57:47Z): /duplicate of #73
Repository: microsoft/node-pty

Issue #26: Add more test coverage 
Created: 2017-01-15T17:25:11Z
Currently there is very little in the way of tests.

Duplicate issue #63: Tests don't run in CI properly
Created: 2017-03-26T00:58:12Z

Closing comment (2017-03-26T00:59:32Z): Wait there just aren't any non-Windows tests yet, duplicate of #26
Repository: microsoft/node-pty

Issue #52: termios support
Created: 2017-03-15T23:30:30Z
Enhancement proposal - How about exporting the termios symbols? This would give some more control over the pty from the terminal side within javascript (master end of pty). See https://blog.nelhage.com/2009/12/a-brief-introduction-to-termios/ for a brief introduction.

Duplicate issue #96: Disable echo on pty ?
Created: 2017-06-27T17:14:23Z
Hi,
I would like to be able to disable the echo of the pty like stty -echo does so I can use node-pty with something that expects it not to echo.
Would it be possible to add that to open ? Or add a generic way to set options with tcsetattr from javascript ?
Thanks!

Closing comment (2017-06-27T17:35:29Z): Just found out this is a duplicate of #52
Closing
Repository: microsoft/node-pty

Issue #73: proposal: gain granularity under UNIX by refactoring of the module
Created: 2017-04-08T16:17:57Z
@Tyriar Not sure how to name it - well I think at least the unix part of this module is kinda broken by design. I've done some own investigations by trying out a much simpler pty implementation under linux and came to the following conclusion:
The C part of the module does to much at once, esp. the Ptyfork is heavy weighted - it tries to deal with forkpty, termios settings, the exec* call and registering of the waitpid callback at once - my prosopal is to separate those things into single calls exported to JS and gain much more interactivity in JS land. Also it would make pty.open useful again. Atm pty.open  is a dead end since the needed symbols from C are missing.
Changes of my proposal:

export forkpty in C semantics
export exec* functions in C semantics
export fork (to be used with openpty)
export wait* functions
some more basic C functions regarding tty file descriptors

Note that those changes would degrade the module to basic C semantics. Therefore it would need to set up higher level stuff in UnixTerminal.

Duplicate issue #264: Registering a listener on the `close` event of pseudo-terminals created using .open() fails (UnixTerminal).
Created: 2019-01-21T20:17:43Z
Environment details

OS: Ubuntu 16.04
node-pty version: 0.8.0

Issue description
> nodepty = require('node-pty')
> pts = nodepty.open()
> pts.on('close', () => undefined)
TypeError: Cannot read property 'on' of undefined
    at UnixTerminal.Terminal.on ([...]/node_modules/node-pty/lib/terminal.js:67:30)

Closing comment (2021-10-21T19:17:08Z): duplicate of #73
Repository: microsoft/powerapps-tools

Issue #764: [BUG]: Teams environment deletion throws 404 error but successfully deleted it
Created: 2021-02-10T11:35:11Z
Describe the bug
When an environment in deleted in Teams clean up flow, the delete environment step throw an 404 error even if the environment is successfully deleted.
As the flow fails, user isn't notify and admins don't received the list of environments to review.
Component:

Solution - Governance
Version - 1.30
Flow - Microsoft Teams Admin | Weekly Clean Up of Microsoft Teams environments

Screenshots

Additional context
I suppose that 'Delete Environment' uses the same logic that PowerShell cmdlet.
According to the documentation, the operation returns a 404 NotFound, the environment was successfully deleted.
I performed some tests. If we pass an wrong environment GUID, error isn't thrown and the 204 - No content code is returned.

With a real environment GUID, error is thrown and the 404-NotFound code is returned

Duplicate issue #850: [BUG]: issue title
Created: 2021-03-18T14:02:19Z
Description
"Microsoft Teams Admin | Weekly Clean Up of Microsoft Teams environments" flow is actually able to delete the Teams environment but throwing "statusCode":404,"message":"Resource not found" and failing.
Component:

Solution Center of Excellence - Governance Components
Version 1.28
Flow Microsoft Teams Admin | Weekly Clean Up of Microsoft Teams environments

Screenshots

Closing comment (2021-03-18T15:17:19Z): Hello,
this is a duplicate of #764 and was fixed in our latest release. You're on an old version of the Governance components, so will need to upgrade to get the latest version.
lease be sure to remove any unmanaged layers from flows before you update as described in installing updates or you will not see the changes.
Thanks for using the CoE
Manuela
Repository: microsoft/powerapps-tools

Issue #703: Connectors by flow and app catalog in SP list 
Created: 2021-01-18T13:36:44Z
BUG 1
I don't see the part for Connections by flow and I can not filter flow connections by flow or by maker in any dashboard connected with info about flow connectors

Component (please tell us which flow or app you are experiencing issues with):

Core solution, dashboard
Version  1.73
dashboard

BUG 2
App catalog canvas app in Nurture component doesn't have SharePoint connector, where do you store app templates? I followed the set up information form Microsoft and its not working:
https://docs.microsoft.com/en-us/power-platform/guidance/coe/modify-components#set-up-the-template-catalog-and-upload-components

Duplicate issue #705: Flow Connectors in CoE starterKit - not up to date as added after move from full inventory by default
Created: 2021-01-19T13:09:05Z
Describe the bug
In the Power Platform Admin view (model driven app) when I open a flow I don't see all of the connectors that are used in the flow, I can only see SharePoint but there is more connector used. Also in a solution in one environment there are 5 different flows, I can see 3 of them in this model driven app but I can not see parent and child flow. I had to put all the flows into a solution because of this parent and child flows. Why I can't see these flows?
Component (please tell us which flow or app you are experiencing issues with):

Solution: Core
Version 1.78]
App or Flow: PowerPlatform admin view

In Power BI report all dashboards with the information about flow connections are not correct. I can not filter makers by flow connector used (I can do this for app connectors) I can not pick a flow to see the connectors and I can  not pick a connector to see all flows using this connector.

Closing comment (2021-01-19T15:33:38Z): This second set of images (associated with makers) is tracked in #703. That report will likely be cut.
We will track just the first issue here as a result.
This works for me locally so can you please confirm:

do you see this issue generally or just with this flow / this teams connector?
if you wait for the sync flows to run again, does it still repro? (perhaps the connection was added after the sync flows ran)
if just teams, if you go to the Connectors view instead and see what apps/flows are associated with Teams?
Repository: microsoft/powerapps-tools

Issue #814: [BUG]: CLEANUP - Admin | Sync Template v3 (Connection Status) flow is failing
Created: 2021-03-08T08:45:57Z
Description
CLEANUP - Admin | Sync Template v3 (Connection Status) flow is failing in "Get App as Admin" step or "Parse JSON" step under "Clean App Connection Status" "Apply to each" loop. The instances of the loop for which it is failing, I can see two types of error:

"statusCode":404 "message":"The response is not in a JSON format.","innerError":"Cannot read server response." I searched for some of these apps using Get-AdminPowerApp cmdlet and it seems they really do not exist anymore.
In the second case "Get App as Admin" is successful. But "Parse JSON" step fails with error: 'Parse_Connection_Ref_JSON' inputs at line '1' and column '54070': 'Required property 'content' expects a value but got null. Path ''.'. I took ownership of one of those apps and it had only one connection (which is active). And in the output

Component:

Solution Core Component
Version 1.78
App or Flow CLEANUP - Admin | Sync Template v3 (Connection Status)

To Reproduce
Steps to reproduce the behavior:

Go to CLEANUP - Admin | Sync Template v3 (Connection Status) flow inside Core Solutions
Click on Run
Wait for 6-8 minutes
Flow will fail with the mentioned error

Screenshots
App Not Found error:

Parse Connection error:

Duplicate issue #892: [BUG]: CLEANUP - Admin | Sync Template v3 (Connection Status) is failing
Created: 2021-04-05T06:56:21Z
Description
CLEANUP - Admin | Sync Template v3 (Connection Status) is failing with sometimes "App not found" error (which might be because the app got deleted after the sync flow ran) for a few apps and for below error for others (InvalidTemplate. Unable to process template language expressions in action 'Parse_Connection_Ref_JSON' inputs at line '1' and column '54071': 'Required property 'content' expects a value but got null. Path ''.'.):

Component (please tell us which flow or app you are experiencing issues with):

Solution Core
Version 1.98
App or Flow CLEANUP - Admin | Sync Template v3 (Connection Status)

Closing comment (2021-04-05T13:23:53Z): Hello. Connecting this to the duplicate #814
Repository: microsoft/powerapps-tools

Issue #941: Product Bug: (Check Deleted)' which fails on step 'Get Apps as Admin fails with "Request too long"
Created: 2021-04-20T12:57:46Z
I am installing COE toolkit for Core Components and the flow ' CLEANUP - Admin | Sync Template v3 (Check Deleted)' which fails on step 'Get Apps as Admin' ( under 'Newly Deleted Canvas apps' module). I have tried running this flow twice and both time it failed.
However when running just this step in a new flow it works for the same parameters.
I have successfully installed the same version of toolkit on our pre prod and dev tenant and it just fails on the Production tenant which has over 1.8million users
COE failure_prod.docx

Duplicate issue #1000: Admin | Sync Template v3 (Flows): The response is not in a JSON format.
Created: 2021-05-04T19:29:48Z
Describe the bug
First runs of the Admin | Sync Template v3 (Flows) Flow results in error:
{
  "error": {
    "code": 404,
    "source": "unitedstates-002.azure-apim.net",
    "clientRequestId": "fbc0b4ac-8a2e-4f1f-9d93-b1acddb250f5",
    "message": "The response is not in a JSON format.",
    "innerError": "Cannot read server response."
  }
}

Component (please tell us which flow or app you are experiencing issues with):

Solution: Core
Version: 2.0.10
App or Flow: Flow

To Reproduce
Steps to reproduce the behavior:

Ensure the Sync Template flows are already turned on for the following object types:
Apps, Connectors, Custom Connectors, Flows, Model Driven Apps, PVA, RPA
Turn on Admin | Sync Template v3. When it completes, turn it back off.

Expected behavior
Flow would run as expected
Screenshots

Additional context
Add any other context about the problem here.

Closing comment (2021-05-04T21:15:29Z): Hello. This is a known product bug and the product team has half the fix rolled and is working on the other half.
Tracked by #941
Repository: microsoft/powerapps-tools

Issue #386: [BUG]: Admin | Sync Template v2 (Power Apps User Shared With)
Created: 2020-07-22T11:27:53Z
Describe the bug
When the flow 'Admin | Sync Template v2 (Power Apps User Shared With)' runs, of the 30 or so runs that happens, only around 5 are successful, with the remainder reporting the error:
The request failed with error: 'The environment '' could not be found in the tenant ''.'. The tracking Id is ''.
5 of them are successful but the others are not. When i then use the 'Power Platform Admin View' power app, when i select an app, it says there are users that the app is shared with but the panel to show you those users is blank (Screenshot attached).
Any ideas?

Duplicate issue #391: Admin | Sync Template v2 (Power Apps User Shared With)
Created: 2020-07-24T13:55:19Z
Describe the bug
Power Apps User Shared with Has been failing multiple times when it runs. None of the runs is getting successful. The Error message is pasted below.
{
"error": {
"code": "AzureResourceManagerRequestFailed",
"message": "The request failed with error: 'The environment '' could not be found in the tenant ''.'. The tracking Id is ''.",
"details": [
{
"code": "MultipleErrorsOccurred",
"message": "There were multiple errors from the API Hubs service. Please see the details for more information.",
"details": [
{
"code": "EnvironmentNotFound",
"message": "The environment '' could not be found in the tenant ''."
}
]
},
{
"code": "FullNonLocalizedError",
"message": "{"error":{"code":"EnvironmentNotFound","message":"The environment '' could not be found in the tenant ''."}}"
}
]
}
}
Component (please tell us which flow or app you are experiencing issues with):

Solution - Core
Version -1.53
App or Flow - Sync Template (v2) Power Apps User Shared With

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots


Additional context
Add any other context about the problem here.

Closing comment (2020-07-24T16:07:29Z): Duplicate of #386
Repository: microsoft/powerapps-tools

Issue #515: [BUG]: Attribute admin_rpamodifiedon is a String, but a DateTime type was specified upgrade from version 1.60
Created: 2020-10-12T21:00:00Z
Hi @JeneferM-MSFT!
I am experiencing the same issue. My current version is 1.60, I tried installing 1.70 and 1.70.2 with same error message.
Unfortunately I cannot install the version from #491 since it is an earleir version from the one I have.
Many thanks for your help !
Victor

Duplicate issue #759: [BUG]: issue title
Created: 2021-02-06T14:11:47Z
Describe the bug
Unable to update Core Components of Centre of Excellence, Error 80041A06.
Component (please tell us which flow or app you are experiencing issues with):

Solution: Centre of Excellence - Core Components
Version 1.89
Managed Solution

To Reproduce
Steps to reproduce the behavior:

Click on "Import Solution"
Choose CenterofExcellenceCoreComponents_1_89_managed.zip
Select Upgrade (leave "Enable Plugin steps and flows included in the solution" checked)
Click "Import".

Expected behavior
Expected that the core components for the Centre of Excellence would update.
Screenshots

Additional context
Exception message:  Attribute admin_rpamodifiedon is a String, but a DateTime type was specified.

Closing comment (2021-02-06T17:48:34Z): Hello, you will need to upgrade to the interim solution (1.62) shown in #515
And then try again to upgrade to 1.85.
Thanks for using CoE!
Duplicate of #515
Repository: microsoft/powerapps-tools

Issue #764: [BUG]: Teams environment deletion throws 404 error but successfully deleted it
Created: 2021-02-10T11:35:11Z
Describe the bug
When an environment in deleted in Teams clean up flow, the delete environment step throw an 404 error even if the environment is successfully deleted.
As the flow fails, user isn't notify and admins don't received the list of environments to review.
Component:

Solution - Governance
Version - 1.30
Flow - Microsoft Teams Admin | Weekly Clean Up of Microsoft Teams environments

Screenshots

Additional context
I suppose that 'Delete Environment' uses the same logic that PowerShell cmdlet.
According to the documentation, the operation returns a 404 NotFound, the environment was successfully deleted.
I performed some tests. If we pass an wrong environment GUID, error isn't thrown and the 204 - No content code is returned.

With a real environment GUID, error is thrown and the 404-NotFound code is returned

Duplicate issue #975: [BUG]: Flow returns 404 Error when deleting Teams environments
Created: 2021-04-28T16:20:58Z
Weekly cleanup of teams environment flow .
The flow is delete the teams environment based on the condition , but it fails with the below error
{​​​"statusCode":404,"headers":{​​​"Access-Control-Allow-Methods":"GET, PUT, PATCH, DELETE, POST","Access-Control-Allow-Origin":"","Access-Control-Max-Age":"3600","Access-Control-Expose-Headers":"","Date":"Wed, 28 Apr 2021 14:58:44 GMT","Content-Length":"54","Content-Type":"application/json"}​​​,"body":{​​​"statusCode":404,"message":"Resource not found"}​​​}​​​

Can you please check and let us know.

Closing comment (2021-04-30T14:31:31Z): Closing out as duplicate per comment above.
Duplicate of #764
Repository: microsoft/powerapps-tools

Issue #592: [BUG]:office 365 Management APIs has been added to Enterprise Applications Rather then App Registrations
Created: 2020-11-24T12:11:10Z
Describe the bug
Installed  version 1.71.5 on a  development tenancy with version 1,54 on the production Tenancy
Component (please tell us which flow or app you are experiencing issues with):

Solution - core
Version  - 1.75.1
App or Flow Child flow

To Reproduce
Steps to reproduce the behavior:
1,  Update solution on development tenancy  to 1.75.1
Expected behavior
I expect updated flows to work.
Screenshots
Additional context
The connector "Office 365 Management APIs" would have appeared to have moved from App Registrations to Enterprise apps in Azure on the development tenancy.  I cannot now log into the Office 365 Management APIs connector because the REdirect URL presented by the login is not the same as the one on the Enterprise Apps Office 365 Management APIs .
Where there is only one tenancy per enterprise, this works OK and Office 365 Management APIs is in the App registration part of the Azure Active Directory.

Duplicate issue #594: How Do I Untangle an audit log from being multi tenant to a single tenant?
Created: 2020-11-24T15:18:44Z
Describe the bug
Somehow my Audity Log has gone from a single tenant audit log to a multi tenant audit log.  How do I make my Audit Log a Single Tenant Audit Log again ?
Component (please tell us which flow or app you are experiencing issues with):

Solution Core
Version 1.75.1
App or Flow [e.g. Sync Template (v2)]

To Reproduce
Steps to reproduce the behavior:
Expected behavior
Audit Log SHould be Single Tenant
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
How to set up an audit log as a single tenant audit log ?

Closing comment (2020-11-24T15:50:58Z): Duplicate of #592
I put a recommendation in your original
Repository: microsoft/powerapps-tools

Issue #941: Product Bug: (Check Deleted)' which fails on step 'Get Apps as Admin fails with "Request too long"
Created: 2021-04-20T12:57:46Z
I am installing COE toolkit for Core Components and the flow ' CLEANUP - Admin | Sync Template v3 (Check Deleted)' which fails on step 'Get Apps as Admin' ( under 'Newly Deleted Canvas apps' module). I have tried running this flow twice and both time it failed.
However when running just this step in a new flow it works for the same parameters.
I have successfully installed the same version of toolkit on our pre prod and dev tenant and it just fails on the Production tenant which has over 1.8million users
COE failure_prod.docx

Duplicate issue #982: Action 'List_Flows_as_Admin' failed for the flow in COE  CLEANUP - Admin | Sync Template v3 (Check Deleted)
Created: 2021-04-29T20:19:45Z
Describe the bug
The below 2 actions are failing in the flow " CLEANUP - Admin | Sync Template v3 (Check Deleted)" under COE core component.

List Flows as Admin
Get Flows as Admin
This is failing for the default environment only while lopping in.

Error Details: The Response is not in JSON format.
when I look into the output of the action, it is showing the below error.



innerError
"\r\n<TITLE>Bad Request</TITLE>\r\n<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii">\r\nBad Request - Request Too Long\r\nHTTP Error 400. The size of the request headers is too long.\r\n\r\n"



To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
The flow should complete successfully.
Screenshots

Additional context
We upgraded the COE from version 1.45 to 2.01 and As per the instruction in below URL, tuned on the flow " CLEANUP - Admin | Sync Template v3 (Check Deleted)"
https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#activate-the-sync-template-flows

Closing comment (2021-04-30T14:14:20Z): Hello you have hit a product bug. Please see #941 there is a flow at the bottom you can run to see this repro outside of the context of the toolkit. Please post a support ticket for assistance.
Closing as Duplicate of #941
Repository: microsoft/powerapps-tools

Issue #491: [BUG]: Import of Solution 1.70.2 from 1.45 : Attribute admin_rpamodifiedon is a String, but a DateTime type was specified.
Created: 2020-09-30T12:35:58Z
Describe the bug
We try to upgrade the CoE Installation. But we are facing an issue with upgrading the solution from 1.45
Component (please tell us which flow or app you are experiencing issues with):

CenterOfExcellenceCoreComponents
Version 1.45 to upgrade with 1.70.2
Entity RPA
seems like the datatype of the field admin_rpamodifiedon changed from string to datetime
ErrorMessage in import-log: Attribute admin_rpamodifiedon is a String, but a DateTime type was specified.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
To change the datatype of a field we would need to delete the field first in the target and than recreate it. As it is managed, this is not possible without completely uninstalling the solution and the dependecies.
Screenshots
Screenshot is also in bug #483
Additional context
Is there a a solution before, that remove that field? So maybe we just need to update to an earlier version, before we can get to 1.70.2.

Duplicate issue #563: [BUG]: issue title
Created: 2020-11-11T09:57:56Z
Describe the bug
On Core Components update from 1.39 to 1.70.6 fails giving error code 80041A06
https://support.microsoft.com/en-us/help/4346891/the-import-of-solution-solution-name-failed-error-occurs-in-dynamics-3
and Exception message
'Attribute admin_rpamodifiedon is a String, but a DateTime type was specified'
On the existing entity the datatype of this field cannot be modified because it is a managed solution. Tried to add a field with same name and text data type, but importing the Core Components keeps failing.
How do I get this issue bypassed or how to get the import done?
Component (please tell us which flow or app you are experiencing issues with):

Solution Core Components
Version 1.70.6
CenterofExcellenceCoreComponents

Closing comment (2020-11-11T13:29:19Z): Hello. This is known, you can import an interim solution in #491 and then import the current version.
Thank you for using CoE, and enjoy the upgrade!
Duplicate of #491
Repository: microsoft/vscode-docs

Issue #2911: when clause info hard to find
Created: 2019-07-24T17:35:13Z
the when clause is pretty powerful in the API, but finding information on how to use it is pretty hard.  there are a lot of references to the when clause but i only found 1 link in the API docs to the key bindings section
for example, in the treeview documentation https://code.visualstudio.com/api/extension-guides/tree-view#tree-view it says "You can also control the visibility of the view by providing the when context value." but there is no link on when."
Searching for the term when in the docs uber search at the top of the page is futile :).
So, I manually went through each of the API doc pages and did a find looking for when and only found a link to clauses here https://code.visualstudio.com/api/references/contribution-points#contributes.commands, which then takes me out of the API docs to the keybindings page.
It would be ideal to have a top level topic in the API docs that explains how to use the when clause and wherever we reference when, link to it.

Duplicate issue #2912: Where is documentation for all the possible macros used in contribution 'when' clause? 
Created: 2019-07-24T22:02:02Z
Throughout https://code.visualstudio.com/api/references/contribution-points the "when" clause is used a lot in contribution declaration but not really explained.
Later I found more comprehensive list on https://code.visualstudio.com/docs/getstarted/keybindings#_when-clause-contexts but it does not talk about how an extension can use a configuration it defines.
Eventually I figured by searching first-party extension https://github.com/microsoft/vscode-pull-request-github/blob/master/package.json that you can use config. prefix to reference your configuration.
My ask: please consider consolidate the documentation on this

Closing comment (2019-07-25T15:41:31Z): Duplicate of #2911
Repository: microsoft/vscode-docs

Issue #124: Add keybinding when context enumeration
Created: 2016-01-22T18:43:29Z
An ask for documentation through doc feedback verbatim.
We should add an explanation for the enumeration to keybindings.md

Duplicate issue #249: Documentation for Keybinding Customisation should list `when' predicates
Created: 2016-03-28T19:58:07Z
From @stephenmartindale on March 27, 2016 17:5

VSCode Version: 0.10.11
OS Version: Microsoft Windows 10

Steps to Reproduce:

Visit the documentation at https://code.visualstudio.com/docs/customization/keybindings
Observe the truly excellent coverage of 'key' and 'command' and other concepts, particularly the "Accepted Keys" and "Keyboard layouts" subheadings.
Observe that there is no table of predicates that may be used for `when' attributes - there is not even a note about the use of logical operators.

Inside VS Code, when the default keyboard shortcut definitions are open, you can discover a few of the predicates by reading existing definitions. For example, without scrolling down, I can see that editorTextFocus, inReferenceSearchEditor and editorHasSelection all exist and that they can be combined with the && operator. The only one that is mentioned in the documentation is editorTextFocus.
Copied from original issue: microsoft/vscode#4697

Closing comment (2016-03-29T17:23:34Z): Closing as a duplicate of #124
Repository: microsoft/vscode-docs

Issue #400: Extension section needs to be updated
Created: 2016-07-04T12:37:49Z
Ref: https://code.visualstudio.com/Docs/editor/extension-gallery
This whole section needs to be updated as most of those actions have moved to the extensions viewlet.
p.s I have added the important label to this repository, hope that is ok.

Duplicate issue #405: Extensions Management: update for new extensions viewlet
Created: 2016-07-04T12:53:39Z
Refs: https://code.visualstudio.com/docs/editor/extension-gallery
We no longer have a quick open management for extensions, but rather a viewlet. As such the extensions management topic should be updated to accomodate for that.

Closing comment (2016-07-05T18:17:28Z): Duplicate of #400
Repository: microsoft/vscode-docs

Issue #6496: 404 in download page
Created: 2023-07-18T15:36:09Z
I was downloading vscode for macOS here: https://code.visualstudio.com/download
However sometimes it automatically redirects me to: https://code.visualstudio.com/sha/undefined
I am not sure what is going on or if has anything to do with this repo. I was unable to download vscode for a while.

Duplicate issue #6503: STOP CLOSING THREADS DOWNLOAD WONT WORK
Created: 2023-07-18T19:22:40Z

Closing comment (2023-07-18T19:32:03Z): There is already a vscode-docs issue tracking the download issue and it is being worked on by VS Code engineering.
Duplicate of #6496

Yeah but bro it won't work I'm not sure why you're marking them as duplicates and fixed