piping to parse doesn't work if TFX_TRACE is on

[microsoft]

piping to parse doesn't work if TFX_TRACE is on

[bryanmacfarlane]

I thought of that - we don't care since trace is a troubleshooting mechanism for a single call. So you would troubleshoot a single call (with --json), figure it out and then turn it off.

[teddyward]

Ok that makes sense. I'll just add a trace statement to the parse exec method to remind users to turn off trace

[jessehouwing]

The same happens for warnings. Which is really annoying. Even with tracing turned off.

C:\Users\jhouw\Source\Repos\vsts-extension-tasks [master +1 ~4 -0 !]> tfx extension create --json --root . --no-prompt -
-manifest-globs extension-manifest.json 3> NULL | ConvertFrom-Json
ConvertFrom-Json : Invalid JSON primitive: Could.
At line:1 char:101
+ ... t --manifest-globs extension-manifest.json 3> NULL | ConvertFrom-Json
+                                                          ~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [ConvertFrom-Json], ArgumentException
    + FullyQualifiedErrorId : System.ArgumentException,Microsoft.PowerShell.Commands.ConvertFromJsonCommand

Result looks like:

Could not determine content type for extension .pssproj. Defaulting to application/octet-stream. To override this, add a contentType property to this file entry in the manifest.
Could not determine content type for extension .lastpatched. Defaulting to application/octet-stream. To override this, add a contentType property to this file entry in the manifest.
Could not determine content type for extension .psm1. Defaulting to application/octet-stream. To override this, add a contentType property to this file entry in the manifest.
{
    "path": "C:\\Users\\jhouw\\Source\\Repos\\vsts-extension-tasks\\jessehouwing.jessehouwing-vsts-extension-tasks-TEST-0.0.41.vsix",
    "extensionId": "jessehouwing-vsts-extension-tasks-TEST",
    "publisher": "jessehouwing"
}

[T-Hugs]

Good call, I'll fix this next week.

On Sat, Feb 27, 2016 at 5:18 PM, Jesse Houwing [email protected]
wrote:

The same happens for warnings. Which is really annoying. Even with tracing
turned off.

C:\Users\jhouw\Source\Repos\vsts-extension-tasks [master +1 ~4 -0 !]> tfx extension create --json --root . --no-prompt -
-manifest-globs extension-manifest.json 3> NULL | ConvertFrom-Json
ConvertFrom-Json : Invalid JSON primitive: Could.
At line:1 char:101

• ... t --manifest-globs extension-manifest.json 3> NULL | ConvertFrom-Json

•                                                      ~~~~~~~~~~~~~~~~
  

  • CategoryInfo : NotSpecified: (:) [ConvertFrom-Json], ArgumentException
  • FullyQualifiedErrorId : System.ArgumentException,Microsoft.PowerShell.Commands.ConvertFromJsonCommand

Result looks like:

Could not determine content type for extension .pssproj. Defaulting to application/octet-stream. To override this, add a contentType property to this file entry in the manifest.
Could not determine content type for extension .lastpatched. Defaulting to application/octet-stream. To override this, add a contentType property to this file entry in the manifest.
Could not determine content type for extension .psm1. Defaulting to application/octet-stream. To override this, add a contentType property to this file entry in the manifest.
{
"path": "C:\Users\jhouw\Source\Repos\vsts-extension-tasks\jessehouwing.jessehouwing-vsts-extension-tasks-TEST-0.0.41.vsix",
"extensionId": "jessehouwing-vsts-extension-tasks-TEST",
"publisher": "jessehouwing"
}

—
Reply to this email directly or view it on GitHub
#9 (comment).