text:
OAuthPrompt ending the current WaterfallDialog

Sample information

Sample type: 18.bot-authentication

Sample language: dotnetcore
Sample name: 18.bot-authentication

Describe the bug
The step DisplayTokenAsync, which ist the last step in the WaterfallDialog "authDialog", is not reached after returning from prompt "Would you like to view your token?" in LoginStepAsync.
To Reproduce
Steps to reproduce the behavior:

Clone repo
Configure oAuth Connection
Run sample
Say "hi"
Sign in
"Would you like to view your token?" ==> say "yes"
==> Loops LoginStepAsync Step

Expected behavior
Should reach DisplayTokenAsync and display the token

Solved with PR #1339 . It is confusing having this sample not working completely without state save, specially when you're working on OAuth flow which would let you think something is wrong with the flow while testing/learning.

This is fixed in the samples-work-in-progress branch.  We will be merging that branch into master within a week or so, but if you need the fix now, that's where you can get it

Thanks! Quickly checked the samples and they seem to follow a new design. Is there any information what exactly is now advised? Webapi/controllers or more the style of e.g. the enterprise bot template (which I like very much).
So, where can we follow the thoughts on refactoring the samples?

The samples-work-in-progress branch has the patterns introduced as part of the 4.3 release.  These are the patterns that we will be using in all our samples going forward and also these are the patterns we are recommending when using 4.3 or greater

Great. Is there a doc explaining what and why it was introduced with 4.3 and what the design considerations are? Or is this something the bot framework team came up with internally, promoting this through changing the samples?
What I found hard in learning v4 was the constant change and the various ways in doing things.
What will happen to the enterprise bot template? Is that still a recommended starting point for a good end to end architecture and concrete implementation? Will it be updated to match 4.3 patterns?
Thanks

docs to support 4.3 should be landing on or about March 25.  the design was driven by customer feedback around the desire to formalize the activity protocol more formally into the programming model.  these changes are additive, so if you look at them and you don't like them, you won't be forced to use them.  that said, it was our goal that they simply handling the core behavior of the activity protocol, surfacing the activity protocol patterns in an idiomatic way for C# and Node.js.  The enterprise bot template will evolve to pick up these patterns as they push out updated version.  if you've recently started a new project based on the enterprise template you are totally fine.  again, 4.3 was strictly additive and is not required.

authors: sebastianzolg sgellock

repo: Microsoft/BotBuilder-Samples


text:
fix assert from sign extension in IntConstOpnd::New

resolves #129

Hi @MikeHolman, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Michael Holman). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@LouisLaf

Looks good.

source: gharchive/pull-request

authors: LouisLaf MikeHolman msftclas

repo: Microsoft/ChakraCore

license: MIT

license_type: permissive

license_source: github-api


text:
Fix few more line/column issue.

Fixed this time by putting the start/end in the emitboolean expression.

@agarwal-sandeep please have a look at this.


text:
Spelling

I haven't updated the commits to include the list of fixed words (I can do that, they're available via https://github.com/jsoref/ChakraCore/tree/spelling-full ), and I'm not really in a position to run any tests.
The first commits are intended to be fairly easy to review -- changes to comments, internal variables, and a build assert.
Other commits will change APIs, Output, and Test Output.
This request is for people like @dilijev to hang comments.

Hi @jsoref, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@jsoref , could you please fix the build and push another commit? Most likely has to do with not updating all the instances of a wrong spelling.

@jsoref Yep I was just looking at the logs. Definitely looks like multiple instances of variable renaming not propagating all the way through.

Sorry about those. I thought that my tools were properly replacing globally, apparently they were doing first instance only (oops). I've fixed that tool for the future.
I just wrote a tool to identify removed words (based on a diff), and I think that has identified the last stragglers. So far, it looks like there was one actual test whose output I changed (the alphabet one was using the string a couple of times), and I've now updated it.

I have a bone to pick w/ @msftclas: I've already played this game with @dnfclas here:
https://github.com/OpenLiveWriter/OpenLiveWriter/pull/134#event-491385573
How many of these bots do I have to appease?

@rajatd operations pushed. Thanks for reviewing. I know such things aren't the most enjoyable reading.

(admittedly, they can be rather amusing...)

@jsoref Thanks for fixing the build breaks.

@jsoref Thanks for the changes. Some of them were pretty funny :)

@jsoref  Can you please sign cla?

@jsoref sorry about the bots, but according to this one you haven't signed the CLA that applies to our project. Would you mind indulging us (to make the legal folks happy so we can merge your change)?

@dilijev shouldn't CLA be picked up by all MSFT repos?

@tcare one would think, but this one is saying it's not signed? Maybe it changed recently so a new version is needed? I'm not even sure who to ask about this.
If @jsoref tries to sign the CLA at the link provided above, and it doesn't work, then there's a problem I'll try to track down. (It has worked for others.)

@tcare @bterlson since there's no new IP in this PR, I suppose we could manually bypass the CLA since it's not actually required, but since the number of lines changed is so high, I'd feel better if the bot confirmed the CLA was signed. What do you think?

@dilijev @jsoref needs to make the CLA say signed, even if that means signing again.

@tcare I think the problem is that the DotNET Foundation has a different CLA than Microsoft repos.

Which is to say there's not actually a problem and once @jsoref makes @msftclas bot happy, that should be all he needs to do for our repo.

Sounds good

@jsoref, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Thanks for signing, @jsoref!

Thank you @jsoref

Reviewed 93 of 122 files at r1, 27 of 32 files at r2, 147 of 148 files at r3, 4 of 4 files at r4.
Review status: all files reviewed at latest revision, 12 unresolved discussions.

lib/Backend/GlobOpt.cpp, line 9624 [r3] (raw file):
"if any one of the sources is an int"

lib/Backend/GlobOpt.cpp, line 9634 [r3] (raw file):
"if any one of the sources is a float"

lib/common/core/FaultInjection.cpp, line 373 [r3] (raw file):
In this case I think 'reproing' is better because we use the term 'repro' for 'reproducing an [error/bug/etc.]'

lib/common/core/FaultInjection.cpp, line 1021 [r3] (raw file):
Same comment about 'reproing' here

lib/common/Memory/Recycler.cpp, line 6128 [r3] (raw file):
@curtisman Was this supposed to be 'priority-boost--overridden' or 'priority boost overrode' or 'priority boost overrides' or something else? I'm not entirely sure this correction captures the meaning.

lib/Parser/parse.h, line 164 [r3] (raw file):
Change loss-less to lossless.

lib/Runtime/Library/InJavascript/Intl.js, line 364 [r3] (raw file):
Be more specific that you're talking about the "pronun" below.

lib/Runtime/Types/DynamicObject.cpp, line 674 [r3] (raw file):
I think you should change this to 're-enable' but since the meaning is clear, it's fine either way.

lib/Runtime/Types/TypeHandler.h, line 584 [r3] (raw file):
This should probably be inlineSlotIndexSlot.

test/Array/array_indexOf.js, line 79 [r3] (raw file):
These were actually fine the way they were (arr is an abbreviation for array), but this change is incorrect. If you want to change these, change to floatArray.

test/es5/Lex_u3.js, line 18 [r3] (raw file):
I'm guessing this comment was supposed to read <LS><PS>

Comments from the review on Reviewable.io

@jsoref I've reviewed this entire changeset. I've left some comments on reviewable (see my previous comment).
Before I merge this in, please address those comments, and if you could, reduce this change to a smaller set of commits, and please rebase your commits on top of the latest master to help history be more legible.
I'll merge it in shortly after your next iteration.
Thanks for your work on this, and looking forward to any future PRs you've got in the works to correct similar issues.

@dilijev: so, I could easily make this one commit, I don't really know what you want in terms of commits...

@jsoref One commit is fine, and is preferred as far as we're concerned. If you had good logical reasons to split your PR into multiple commits, that would be fine too, but we just ask that you only do that if there's a clear reason.
Thanks for doing that. I'll merge this in today.

I tend to split to help maintainers review/manage risk.
If you don't care, it's certainly easy enough for me not to bother.

Reviewed 73 of 79 files at r5.
Review status: all files reviewed at latest revision, 7 unresolved discussions.

lib/Backend/IRBuilder.cpp, line 6666 [r5] (raw file):
There's some grammar weirdness here. You can follow up in your next PR.

lib/common/Memory/SmallFinalizableHeapBlock.cpp, line 164 [r5] (raw file):
Somehow 3 spaces ended up in these comments. You can follow up later.

lib/Runtime/Library/JavascriptEnumeratorIterator.h, line 6 [r5] (raw file):
I think this meant for-in as in for (x in array)

lib/Runtime/Types/PathTypeHandler.cpp, line 981 [r5] (raw file):
Personal preference on this: ...have the IsPrototypeFlag set?

Comments from the review on Reviewable.io

Also previous unresolved discussions:

lib/Backend/GlobOpt.cpp, line 9624 [r3] (raw file):
"if any one of the sources is an int"

lib/Backend/GlobOpt.cpp, line 9634 [r3] (raw file):
"if any one of the sources is a float"

Yes to the for-in typo

@jsoref That's absolutely reasonable, and it can sometimes help in review to have commits split up into separate logical segments. In this particular case, my reasoning is that there are really only two kinds of changes in this PR:

Comment changes, which pose no risk.
Renaming variables in a mostly local scope, which poses only a small amount of risk, especially if the CI checks pass.

So there's only one set of "risky" changes to consider here, and any non-risky changes can be combined into it. But overall, every change in this PR is a spelling change, and so to me, it's logically a single commit.
During a code review, I personally sometimes find it helpful to have multiple smaller commits because it can act as sort of a guided tour of the review. For related logic changes in a large PR this can be very helpful, but when it comes time to merge it in, a single commit is often best, especially if you're already rebasing on top of master.
Still, it is author's discretion. If there's clear enough logical units that the author believes should be highlighted in the history, multiple commits are absolutely welcome.

Review status: all files reviewed at latest revision, 8 unresolved discussions.

lib/Backend/GlobOpt.cpp, line 9624 [r3] (raw file):
Oh, right, I was going to run through the repo and do a/an work. I've started it. It'd probably be helpful if that didn't block the rest of this. The an -> a side is fairly annoying/slow.

lib/Backend/IRBuilder.cpp, line 6666 [r5] (raw file):
s/pass/passing/ ?? It's weird, but, it's also hard to fix, because there's so little text, and the code is fairly opaque (necessitating a comment!)

test/Array/array_indexOf.js, line 79 [r3] (raw file):
Ok, the reason I was changing it was to have only a single spelling (both ary and arr were used), I'm aware that both are valid, but I find using a single abbreviation consistently is helpful.

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, 7 unresolved discussions.

lib/Backend/GlobOpt.cpp, line 9624 [r3] (raw file):
Yeah, I don't want to block on this. I assumed you may have been working on additional changes in your other branch and I assume there will be another nice big spelling PR coming in.
Still these were omissions rather than a/an conversions and since I noticed them I figured I'd point them out. Feel free to address them in your other branch and I'll finish up merging in this PR.

lib/Backend/IRBuilder.cpp, line 6666 [r5] (raw file):
Hmm, yeah. Maybe just leave this one alone for now. We can consider it in your future PR. Maybe @curtisman knows more about the context here?

test/Array/array_indexOf.js, line 79 [r3] (raw file):
Ah, I see. It's such a small difference for the abbreviation I think spelling it out is better. Thanks for the change you made.

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, 5 unresolved discussions.

lib/Runtime/Library/JavascriptEnumeratorIterator.h, line 6 [r5] (raw file):
This one should definitely be changed in this PR.

Comments from the review on Reviewable.io

Sure. From my perspective, if you're comfortable with it completely folded, I'm fine with it.
Comfort varies a lot by project and test coverage.
Some projects have API/ABI rules which means that changing a function name or commandline argument is more problematic than others. So I try to be cautious about how I deliver changes.
For TypeScript and another Microsoft project, I'm going to try tossing the series raw and see what they want instead of spending the time categorizing.
Note that I benefit from playing around w/ all of these segmentations, since I'm working on improving Mercurial (hg)'s UX, which means I'm forced to use more tools/paths and find bugs/improve edges as I go.

Review status: all files reviewed at latest revision, 5 unresolved discussions.

lib/Backend/GlobOpt.cpp, line 9624 [r3] (raw file):
https://github.com/jsoref/ChakraCore/commit/685932a28dd40270df0276493e4ede617c6a20c8 has the only changes I'm holding off.

lib/Backend/IRBuilder.cpp, line 6666 [r5] (raw file):
I can stash a passing change into my pending branch for once everything else goes in.

lib/common/Memory/Recycler.cpp, line 6128 [r3] (raw file):
Do we want me to keep an open thing for this?

Comments from the review on Reviewable.io

Cool. In the days before I was active on GitHub I used Mercurial a lot. Good to see there's an eye to continued improvement. (Of course that's totally off-topic =P)

Review status: all files reviewed at latest revision, 4 unresolved discussions.

lib/common/Memory/Recycler.cpp, line 6128 [r3] (raw file):
Considering the spelling changes are low-impact and there's no harm in making no change, I wouldn't worry about this unless it bothers you. I don't want to block on this.

Comments from the review on Reviewable.io

One thing to note about Git is that it handles tracking of file renames best if the rename does not include any other changes to the file in the same commit. If you wanted to split those out, there's a good case for that. Of course if you didn't make any other changes within those files, no need.

Grr. Yeah, I wondered about that. Since mercurial tracks renames as an action, that's less of a problem for me. I'm pretty sure there are changes in the renamed files.
I'm not quite sure how to deal with them, since the files reference themselves. Would you rather files renamed before or after tests or both?

all changes rename files
changes except file references rename files fix references to files
rename files all changes

Yep I confirmed that git-blame now lists you as the author of the whole file. Before you rebased, it had the right info. So somehow that worked out...
I think option 2 is the best one.
Luckily we don't need to worry about intermediate steps being broken due to the PR-and-merge process. There's a good case for it here.

Review status: 291 of 298 files reviewed at latest revision, 3 unresolved discussions.

lib/Backend/IRBuilder.cpp, line 6666 [r5] (raw file):
@curtisman I don't suppose it should be skipping instead?

Comments from the review on Reviewable.io

Alright, it'll take a minute or three, but no big deal. Again, I get to test tooling :)

Oh weird, actually the reason it's showing up as you is because after your rebase the rename wasn't preserved as a rename and you've simply added those files this time.
See:
ChakraCore (jsoref-spelling)
$ git ls-files | grep -i watson
lib/common/Memory/RecyclerWatsonTelemetry.h
lib/common/Memory/RecyclerWatsonTelemtry.h

I think git will use some heuristic on how much of a file changed in order to determine a rename. It doesn't need to match 100% but like 90%+ and you should be okay.

Yeah. I noticed that when I looked at one of my diff reviews, I was wondering if I lost the info... sigh, I'll need to see if my blackbox shows where it got lost...

Reviewed 7 of 7 files at r6.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

Once you get the file rename info re-integrated I'll sign off and merge this PR. Thanks for bearing with me through this :)

Some projects have API/ABI rules which means that changing a function name or commandline argument is more problematic than others. So I try to be cautious about how I deliver changes.

This is a good policy. ChakraCore will have some of these limitations too when it comes to any function names / APIs that are exported, and possibly in JIT code generation or bytecode names. In this case, I don't think anything like that applied.

+1,022 −1,021

That looks right.

The +1 is the pronun comment.

One change that did happen is some error messages changed. Sometimes people (as in the tests) look for very specific error strings.
That said, I'm not sure how much sympathy should be allocated to that... Especially since each js engine is generally free to have its own error strings, or to localize them, resulting in far ranging messages.

@dilijev : Do I need to work around the rename, or is git now happy w/ me?

Looks like git is happy. I'll merge your change.

For the curious, the reason our tests look for specific error messages is so that we have better certainty that we are getting the expected error in our test, and not some other error with the same constructor.

@jsoref Looking for specific messages may be the easiest way to check whether a particular error path has been hit which is specific to our engine and our code base anyway, so I don't see a problem there. As long as all the tests have been updated properly it looks like the right thing to do.

@ianwjhalliday , @dilijev : yeah, I'm not saying your tests were written wrong, it was definitely the right way to write them, just noting that someone could be incredibly skittish and refuse to change even error messages -- because it could break code written expecting those messages. I'm glad you guys aren't that conservative :)

@jsoref It remains to be seen what might happen with internal testing (which I've just started). If there are any breakages, I'm sure it will be as easy to fix them as changing some more test messages, but I doubt there will be problems.

@jsoref FYI on the merge commit
 rename lib/common/Memory/{RecyclerWatsonTelemtry.h => RecyclerWatsonTelemetry.h} (100%)
 rename test/InlineCaches/{inlnieLocalCacheWithoutProperty.baseline => inlineLocalCacheWithoutProperty.baseline} (100%)
 rename test/InlineCaches/{inlnieLocalCacheWithoutProperty.js => inlineLocalCacheWithoutProperty.js} (100%)
 rename test/Object/{propertyIsEnumarable.js => propertyIsEnumerable.js} (100%)
 rename test/es5/{SemiCollonAfterBlockEs5.baseline => SemicolonAfterBlockEs5.baseline} (100%)
 rename test/es5/{SemiCollonAfterBlockEs5.js => SemicolonAfterBlockEs5.js} (100%)

@jsoref could you change your initial comment on this pull request to include any additional information you'd like to end up in the git history log (like which words were corrected, and so on).
Also please don't make any other changes to the commits in this PR as I'm integrating the changes into the internal code, which references some things that changed, and that will just make things more difficult.

Something like:
Fix various spelling errors.

Fixes misspellings of:
* a..z (the English alphabet sequence a..z with one pair of letters transposed)
* actual
* algorithm
* amount
* although
* argument
* array
* as
* assignment
* auxiliary
* availability
* avoiding
* because
* beginning
* built
* canonicalization
* canonical
* catch
* causes
* collection
* committed
* compare
* comparison
* compilation
* completed
* concurrent
* conditions
* constructor
* contain
* context
* contiguous
* conversion
* convert
* corresponding
* counterparts
* coverage
* covered
* current
* declaration
* default
* deferred
* delimiters
* dependencies
* descriptions
* descriptor
* diagonal
* dictionary
* differently
* different
* disposed
* dynamically
* dynamic
* earlier
* emitting
* empty
* emulated
* encodable
* enough
* entrypoint
* enumerable
* environment
* evaluate
* everything
* exactly
* exception
* exercised
* existing
* expandos
* explicitly
* extension
* floatarray
* for-in
* foreign
* function
* generate
* generator
* granularity
* identical
* implemented
* implicit
* inclusive
* index
* indicate
* indicating
* infinity
* initializer
* initial
* injection
* inlinable
* inline
* insertion
* instance
* instantiate
* interior
* interpreter
* interpret
* invalidation
* invoke
* iterable
* iterator
* javascript
* label
* lambda
* lane
* language
* left
* length
* manager
* maximum
* member
* memory
* message
* metadata
* necessarily
* occurrence
* offset
* offsets
* of lit (two word sequence)
* ofobj
* ofreturn
* optimization
* original
* outer
* output
* overridable
* overridden
* owning
* parameter
* participate
* perlargest
* physical
* pollute
* polyfill
* polymorphic
* popping
* possibility
* preceded
* precise
* precision
* preferenced
* primitive
* processed
* profiled
* profile
* program
* progress
* propagate
* prop'd
* properties
* property
* prototype
* recycler
* re-enable
* referenceable
* reference
* registers
* removed
* required
* result
* semantics
* semicolon
* separately
* separator
* sequences
* should
* sibling
* signature
* similar
* simultaneously
* source
* sources
* spec'd
* specialization
* statement
* store
* straight
* subtags
* succeed
* successful
* sufficient
* summation
* supplied
* supported
* support
* surrogate
* telemetry
* ternary
* testing
* then
* the
* though
* threshold
* timing
* transferred
* traversal
* truncation
* typespec'd
* underflow
* uninitialized
* unknown
* unless
* unregister
* unroll
* unscopable
* using
* value
* variable
* verifies
* verify
* visitor
* without
* zero

brand:
* ForceES5Array

grammar:
* a/an
* any one of the ... is
* as an input/output
* because
* be replaced
* different thresholds
* have
* is
* is a
* it is
* lossless
* not to report
* operations
* required by
* the
* true
* a tortured sentence involving interleaving

Tagging an ambiguous token with a guess
* pronunciation

Whitespace

@jsoref sure, LGTM. You can edit the PR description or I'll copy-paste that up there.

I've edited the commit message (I'm not sure if that's what you wanted me to do).

If it isn't, please just do the magic. Github is somewhat befuddling.

@jsoref I meant to edit the description of the PR on GitHub itself. But editing the commit message as well does no harm.

@dilijev Is this ready to get merged?

@abchatra yes, but due to the recent issues with the internal build system I haven't been able to get a clean build yet. I'm trying every so often.

@jsoref Thanks for the spelling changes! If you have any other related changes, feel free to open a new PR when ready. :)

authors: abchatra dilijev ianwjhalliday jsoref msftclas rajatd tcare


text:
Update logic to hide/show actions conditionally

Updated the logic to use onDataLoaded event for hiding/showing actions conditionally based on rental state.

@anuragtokhi,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@anuragtokhi,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

authors: anuragtokhi msftclas


text:
Odd behavior in multithreading with python

Environment info
Operating System: Ubuntu kernel: 4.4.0-78-generic
CPU:
C++/Python/R version: GCC 4.4.7, python 3.5.2
Error Message:
When using the sklean API in python (in a notebook) and leaving nthreads to the default value, -1, the system doesn't use all the processors. If you define nthreads=20, it runs correctly, then in you define nthreads=-1 it runs correctly again. It looks there is a problem witht he initialization
Reproducible examples
https://github.com/Azure/fast_retraining/blob/new_parameters/experiments/02_BCI.ipynb

@miguelgfierro
When set num_thread=-1, actually, it is ignored. So it the num_thread is still 20 after the second time set it to -1.
And the default value of num_thread is set by openmp. So its values vary according to compiler and platform. But its expect value should be the max num_threads of current platform.

source: gharchive/issue

authors: guolinke miguelgfierro

repo: Microsoft/LightGBM


text:
Fix func is not defined in MSVS2013

Fixes ability to build with MSVS2013 by defining __func__ keyword.
Discussed in #817.

@i3v,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@i3v, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot


text:
Converting trained Object Detection PyTorch Darknet model to Tensorflow

Platform (like ubuntu 16.04/win10): centos7
Python version: 3.6
Source framework with version (like Tensorflow 1.4.1 with GPU): PyTorch 1.0
Destination framework with version (like CNTK 2.3 with GPU): Tensorflow GPU
Pre-trained model path (webpath or webdisk path): https://storage.googleapis.com/ultralytics/xview_best_lite.pt
Running scripts:
Editing conversion/pytorch/pytorch_parser.py and loading the model like so:
cfg = './xview-yolov3/cfg/c60_a30symmetric.cfg'
            model = Darknet(cfg, 32 * 51)
            checkpoint = torch.load('xview_best_lite.pt', map_location='cpu')
            model.load_state_dict(checkpoint['model'], strict = False)

Then running
mmconvert -sf pytorch -iw ./xview_best_lite.pt -df tensorflow -om ./xview.pb --inputShape 3,1632,1632
Yields
RuntimeError: /opt/conda/conda-bld/pytorch_1524584710464/work/torch/csrc/jit/tracer.h:120: getTracingState: Assertion `state` failed.

I'm basically trying to use the exported xview.pb to do inference like this:
        boxes, scores, classes = [], [], []

        def tensor(t):
            return session.graph.get_tensor_by_name('{}/{}:0'.format(model, t))

        image_tensor = tensor('image_tensor')
        box_t, score_t, cls_t, detections_t = tensor('detection_boxes'), tensor('detection_scores'), \
                                              tensor('detection_classes'), tensor('num_detections')

        image = np.expand_dims(image, axis = 0)

        (box, score, cls, detections) = session.run(
            [box_t, score_t, cls_t, detections_t],
            feed_dict = {image_tensor: image})

        return np.squeeze(box), np.squeeze(score), np.squeeze(cls)```

Hi, @buroa probably because of the issue of https://github.com/pytorch/pytorch/issues/8473. I do look far into the problem, and maybe you can check your version of pytorch.

Hi, @buroa probably because of the issue of pytorch/pytorch#8473. I do look far into the problem, and maybe you can check your version of pytorch.

I have switched between so many different versions to get this to work ... I would just like to know how I can convert that model to do Tensorflow object detection.

I mean if the error is about RuntimeError: /opt/conda/conda-bld/pytorch_1524584710464/work/torch/csrc/jit/tracer.h:120: getTracingState: Assertion state failed., this is about the error reported from torch.jit. Thus, I do not know what happened where the model is passed through mmdnn.

authors: JiahaoYao buroa

repo: Microsoft/MMdnn


text:
HTK sharing is not working b/w hololens and Immersive headsets!!.

Overview
trying to sharing bw hololens and immersive headset!!.
Expected Behavior
it supposed to be work like 2 hololenses.
Actual Behavior
Not connected.
Steps to reproduce
tried with HTK sharing scene , not connecting / sharing  bw hololens and immersive headsets.
Unity Editor Version
2017.2.1p1
Mixed Reality Toolkit Release Version
2017.2.1.0

Are either devices able to connect? The HoloLens or the immersive headset?

Immersive headset even didnt connect to HTK sharing services!!.

Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.

authors: ALARUNVIGNESH keveleigh wiwei

repo: Microsoft/MixedRealityToolkit-Unity


text:
Adding EventRouting for Camera events, added option to ClippingPrimitive

Overview
Adding a helper script to Utilities that enables components to subscribe to OnPreRender() without living on a Camera component. We can add more as needed.
Context
I ran into an issue with TextMeshPro objects dynamically creating a sub TMP object at OnWillRenderObject(). This means any check for new objects that may exist in Update() or LateUpdate() will have to wait a minimum of a frame to catch the newly created TMP object.
Changes
--- Updated ClippingPrimitive. Now has an option to subscribe to  OnPreRender().

It's frustrating that this workaround is necessary. Probably worth opening a bug against TMP.

I agree. There is literally no way to catch the object unless you have a script on the parent TMP object, or this solution. Absurd.

authors: Railboy radicalad


text:
has_key method needed for debugger to recognise an object as dict-like

I've implemented a class that inherits from collections.MutableMapping, and it acts like a dictionary. I was hoping that the debugger would show the keys and values in a DataTip, but it only shows the keys.  After some digging through visualstudio_py_debugger.py, it turns out I have to implement a has_key method too otherwise it's not recognised (line 1338). The has_key method isn't called, so I guess it's just used to prevent some false positives where it would mistakenly recognise anything that has an attribute items as a dict. However, wouldn't it be nicer for it to recognise methods like __getitem__ instead? Surely the bare minimum is for an object to implement a method to iterate over/list the keys (keys/iterkeys/__iter__), and a method to get the associated value (__getitem__)?
Obviously one could argue that collections.MutableMapping should implement has_key already...
import collections

class Test(collections.MutableMapping):
    def __init__(self):
        self.__internal_dict = {}

    def __getitem__(self, key):
        return self.__internal_dict[key]

    def __setitem__(self, key, val):
        self.__internal_dict[key] = val

    def __delitem__(self, key):
        del self.__internal_dict[key]

    def __iter__(self):
        return iter(self.__internal_dict)

    def __len__(self):
        return len(self.__internal_dict)

class Test2(Test):
    def has_key(self):
        raise Exception('Not needed?')

# Looks like an enumerable object
t = Test()
t['a'] = 1
t['b'] = 2

# Looks like a dict
t2 = Test2()
t2['a'] = 1
t2['b'] = 2

Agreed. We should use the same test as the mapping ABC.

authors: slishak zooba

repo: Microsoft/PTVS


text:
Snippets in completion list need to update when snippet list changes

Start VS
Use snippet manager to add or remove snippets
You can use the new snippets by typing the name and TAB, but you will not see them appear in completion list. This requires VS restart.
We should listen to events that let us know to update our internal list of snippets.

We're closing old issues with no recent activity. If this is still important, please open a new issue.


text:
Enter in a specific construct over-idents

if (TRUE)
install.packages("foo")
foo()

#1285

repo: Microsoft/RTVS


text:
[DO NOT MERGE][Java][Datetime] Fix broken test cases for DatePeriodParser

Some tests were broken due to changes in test cases.
Also, some tests were skipped due to error in other classes that were fixed afterwards.

Do not merge this PR since it braked C# unit tests. We'll review and update it.

repo: Microsoft/Recognizers-Text


text:
Constructor should support decorators/annotations

If you align the closing constructor curly bracket the highlight will break:

If you place the bracket behind the last parameter everything works fine:

Duplicate of #8.

authors: DanielRosenwasser Fank

repo: Microsoft/TypeScript-TmLanguage

license: mit

license_source: bigquery


text:
[js] syntax highlight goes to wrong by 'function' method

From @mysticatea on July 15, 2016 10:25

VSCode Version: 1.4.0-insider (and 1.3.1)
OS Version: Windows 7

Steps to Reproduce:

write a call of function method.

Copied from original issue: Microsoft/vscode#9327

Duplicate of #64

authors: aeschli sheetalkamat


text:
Auto-import named export from default exported

From @janhartmann on November 9, 2017 5:0

VSCode Version: 1.18.0-insider
OS Version: MacOS High Sierra

Steps to Reproduce:

Create a file with a default export
Create another file where the default exported is exported as a named export
Try to import it

Reproduces without extensions: Yes
Thank you for this auto-import feature in JavaScript! This is something I have been awaiting for a long time! I am not sure of the limitations of this, but I have trouble auto-importing default export's from an index.js file.
Take for example:
// File: ProfilePhoto.js
import React from "react";
import PropTypes from "prop-types";
import injectSheet from "react-jss";

const ProfilePhoto = ({ classes, picture }) => {
    return <img src={"data:image/jpeg;base64," + picture} className={classes.photo} />
};

const styles = () => ({
    photo: {
       // Styling
    }
});

export default injectSheet(styles)(ProfilePhoto); // injects the classes argument

// File: index.js
export { default as ProfilePhoto } from "./ProfilePhoto";

What I am doing here is that I am using an higher order component to wrap the function and use that as the default export. But this will never be picked up from the auto-import suggestions?
Is this a limitation or is something which can be integrated in VSCode?
Copied from original issue: Microsoft/vscode#37874

From @zfeher on November 9, 2017 8:40
Also want to thank you for the new auto import feature. It would be nice if you can make it work with default exports as well in the future. Here are some suggestions:
We have many default exports in the following forms
// some-func/index.js
const someFunc = () => { ... }
export default someFunc

// other-func/index.js
export default function() { ... }

// other-func-with-name.js
export default function otherFuncWithName () { ... }

So sometimes a default name for the exported default function can be aquired from the module (this could be an extra bonus feature).
However in general cases the module name (folder-name, folderName, FolderName) or the filename can be used (converted camelCase/PascalCase version if name is kebab-case) as a default name for auto import. So if I type someFunction, SomeFunction or some-function it could find the module to import. Plus it could show us an extra option like import as which could ask for a name.
Maybe the whole auto import could be improved later via using (fuzzy) search so we could narrow the results eg typing: utils/feature/some-func, u/f/sf, etc ... which eventually will be replaced with the found import if accepted.

Auto-import does work for default exports but only if there is an understandable symbol name currently. Example:
export default class Foo { }

export default function foo() { }

A basic example of @janhartmann's request would recognizing exports such as :
const id = x => x;

class Foo { }

export default id(Foo);

Should be fixed by https://github.com/Microsoft/TypeScript/pull/19875

authors: mhegazy mjbvz

repo: Microsoft/TypeScript


text:
Emitted __asyncValues declaration checks for __asyncIterator property

TypeScript Version:  2.7.0-dev.20171202
Code
declare const iterable: AsyncIterable<number>;
declare function doStuff(i: number): void;

async function foo() {
    for await (const i of iterable) {
        doStuff(i);
    }
}

tsconfig.json
{
    "compilerOptions": {
        "module": "none",
        "lib": [
            "es5",
            "esnext.asynciterable"
        ],
        "target": "es5",
        "downlevelIteration": true
    }
}

The above example emits a variable declaration for __asyncValues that checks for the existence of the __asyncIterator property of the global object.
var __asyncValues = (this && this.__asyncIterator) || function (o) {
    if (!Symbol.asyncIterator) throw new TypeError("Symbol.asyncIterator is not defined.");
    var m = o[Symbol.asyncIterator];
    return m ? m.call(o) : typeof __values === "function" ? __values(o) : o[Symbol.iterator]();
};

Expected behavior:
From looking at the other generated helper functions, the declaration should rather check for __asyncValues:
var __asyncValues = (this && this.__asyncValues) || function (o) {
    if (!Symbol.asyncIterator) throw new TypeError("Symbol.asyncIterator is not defined.");
    var m = o[Symbol.asyncIterator];
    return m ? m.call(o) : typeof __values === "function" ? __values(o) : o[Symbol.iterator]();
};

Full example:
asynciterable-test.zip

A PR would be appreciated.

Created a small PR (#20460) where I basically replaced every occurrence of this.__asyncIterator in the repository with this.__asyncValues.

authors: martinhiller mhegazy


text:
Should not give suggestions when typing spread operator ....

foo(./* expecting no suggestion */);
foo(../* expecting no suggestion */);
foo(.../* expecting suggestions */);

function foo(./* expecting no suggestion */) { }
function foo(../* expecting no suggestion */) { }
function foo(.../* expecting no suggestion */) { }

I think this is also related to a bug of Visual Studio Code:

Dupe of https://github.com/Microsoft/TypeScript/issues/3242

authors: danquirk vilic


text:
Proposal: simplify access to static members

When accessing static member of class you must write class name followed with dot before member name. But this is redundant when using that member inside the class itself.
Let's see an example (it's a little bit far-fetched but shows the case):
class SampleClassWithLongName {
    static SCALE = 5;
    private num:number;

    // ...

    getScaled():number {
        return SampleClassWithLongName.scaleNumber(this.num);
    }

    static scaleNumber(n:number):number {
        return n * SampleClassWithLongName.SCALE;
    }
}

My suggestion is to extend the functionality of static keyword (just to not introduce a new one) so it will help eliminate the need to continuously repeat class name.
With this feature our example became shorter and more readable:
class SampleClassWithLongName {
    static SCALE = 5;
    private num:number;

    // ...

    getScaled():number {
        return static.scaleNumber(this.num);
    }

    static scaleNumber(n:number):number {
        return n * static.SCALE;
    }
}

+1
or
this::staticValue

this.constructor.scaleNumber will work on methods but not on static functions.

+1

+1

The class name does not seem like that bad of an option, and does not justify the complexity of adding a new syntax to the language.

mhegazy, accessing static property via class is not the same as accesing via 'this'.
If you access
class Parent {
  static x: 0;
  public method(): number {
    return Parent.x;
  }
}

all child classes (Child extends Parent) will use x = 0 even if they redefined it.
So accessing by 'this' is very useful, please give a chance to 'this.x' syntax.

How hard would it  be to user super as a reference to the super class?

authors: FabianLauer OlegDokuka SaschaNaz dmiko leegee mhegazy moonpyk vadimzzz


text:
Performance: Config Option to Use Functions in place of defineProperty() Getter/Setters

I've found there are potential performance implications when it comes to Object.defineProperty getter/setters across various browsers:
http://jsperf.com/es5-getters-setters-versus-getter-setter-methods/10
I would like to suggest a configuration option to output get/set class properties as regular functions instead of their Object.defineProperty counterparts. For example:
public get myprop() {
  //do some stuff
  return this._myprop;
}
public set myprop(value) {
  //do some stuff
  this._myprop = value;
}

would be transpiled to something like the following, free of  Object.defineProperty:
MyClass.prototype.__getmyprop() {
  //do some stuff
  return this._myprop;
}
MyClass.prototype.__setmyprop(value) {
  //do some stuff
  this._myprop = value;
}

This would be extremely useful in the event that application performance is impacted by the use of get/set.
I should also note that in an AS3->JS transpiler I wrote awhile back it did essentially exactly this, so I do believe it is possible from a syntactical standpoint. I think this would be a great feature to have with hopefully not too much effort.

You can't do this because any consumer of your JavaScript now has to specifically know that they need to use a method call. If that's what you want, you can already achieve identical behavior anyway through overloads:
class C {
    public myProp(): string;
    public myProp(value: string): void;
    public myProp(value?: string) {
        if (!value) {
            return this._myProp;
        }
        this._myProp = value;
    }
}

@DanielRosenwasser I should have noted that the purpose of this feature wouldn't be for code that's going to be consumed by non-TS code. The sole purpose would be to allow for the sugar of get/set without the potential overhead of Object.defineProperty in some environments. (Maybe it could have been a decorator or something)
But anyway, the overloading solution isn't quite what I was looking for since I want to be able to toggle on Object.defineProperty in environments where it was already fast (or faster). In a graphically intensive application I'm profiling, in one specific environment I'm seeing these defineProperty functions taking significantly more time to execute in rapid succession than essentially any regular function in the app (they literally show up at the top of the profiler). And they are really only being used as proxies for the most part in some abstractions built into the app, no extra logic that should result in such slowdowns.I think there could be significant benefits from being able to easily switch on a feature like the one I'm suggesting.
If there is still no interest in adding this feature for technical reasons then I'll let it go, though I'd like to kindly ask you to reconsider.

The problem is you have no way of knowing when to switch out a property/element access with a call expression apart from the type of the left side of the dot. How exactly would we preserve the correct semantics if your value ended up getting typed as any and you still performed the property access?

If the value had become casted as any I'd expect to receive a runtime error that the property doesn't exist, which I think should be trivial to debug if the feature is opt-in. The main idea is that this would be a feature designed around maximizing performance in areas of the code that are fully invested in the TS typing paradigm, and not likely to fall into these situations

Unfortunately, I don't think imposing that sort of edge case is in the best interest of users. Defining a regular property or using the above overload workaround should be sufficient.

Alrighty, well it was worth a shot. I appreciate the feedback at least.


text:
Can't edit files in Visual Studio after installing 1.8.4 On Update 2 CTP

TypeScript Version:
1.8.4
Visual Studio Version:
Community 2015 CTP 14.0.25008.00
Everything was working fine using TypeScript 1.8.1 beta. After installing 1.8.4 last night, the editor no longer works. Typing does nothing. The onlys keys it responds to are enter, delete, backspace. The three drop-down lists at the top of the editor that let you jump to certain parts of your code are all blank.
I've tried all of the following with no luck.

Repair/uninstall Visual Studio and TypeScript
Disable extensions
Uninstall ReSharper
Clear MEF component cache
Update devenv.exe.config

I also can't seem to stop Visual Studio from updating to the CTP when I reinstall. I started getting a lot of JavaScript language service crashes after installing the CTP. Viewing a compiled TS file would cause JavaScript to stop working.

I have the same problem. My co worker does not and the only major difference is I have the vs2015.2 CTP and he just has vs2015.1 rtm. Hope that helps

I ran into the same problem as well.
I was playing using the newly added ability to add comments to the tsconfig.json file.  If I added a comment at the very top of the file, then this behavior occurred after a restart of VS.
To resolve, remove any comments at the top of the tsconfig.json file (only use inline comments to the json), and then restart VS.  To be safe, you might try removing any comments to the file and restarting VS and see if that fixes it.

Update 2 CTP does not support TS 1.8.4. We are looking into why the setup did not show the correct blocking message.
TS has dependency on internal APIs that changed in Update 2, trying to install TS 1.8.4 (targeting Update1) will cause the language service to be broken.
Update 2 CTP has TS 1.8.1-beta in box, the next public release of Update2 should have the TS 1.8.4. sorry for the inconvenience.

@mhegazy - thanks for the update.  Partly our fault for running a CTP :)  The perf improvements have been worth it though.
If you've got some hacky way of rolling back to the 1.8.1-beta that'd be splendid.

uninstall TS 1.8.4, repair Update 2 entry in Add/Remove programs should do the trick.

Despite having Update 2 CTP installed, my Add/remove programs just shows
Microsoft Visual Studio Enterprise 2015 with Update 1

But CTP for update 2 was definitely installed and indeed when I run VS 2015 it says it's CTP for update 2

I guess the incorrect info being reported in add/remove programs is the reason why installation of TypeScript 1.8.4 wasn't blocked.
So I've uninstalled TS 1.8.4 - it was really quick and repaired the only entry in add/remove programs so I no longer get those crashes in VS pointing me to the activity log but I also get a read-only TypeScript editing experience.
Sorry for so many words - I wanted to be specific and anticipate what you might suggest :)  My other thread has the things I've tried already with regards to uninstall, reinstall, repair, etc.

I went to my layout folder for the update 2 CTP and found the pair of Typescript *.msi files.  They wouldn't install as a newer version of the product was already present.  Removing TypeScript 1.7.x and 1.8.x from add/remove programs still didn't let the *.msi files executes.
So I then fired up Windows Installer Cleanup Utility.  It lists many packages for CTP update 2 - so that's good.  It also still listed the TypeScript packages.  I nuked them and then ran the ones from the update 2 ctp folder.
That got me back to VS 2015 throwing errors directing me to the activity log upon opening a TypeScript file.
I visited add/remove programs and removed TypeScript from there.  Opening VS 2015 got me back to the behaviour described in this thread where I get the read-only TypeScript experience (but no errors raised in the GUI). Strange that even after uninstalling TypeScript I still got syntax highlighting, etc.
I'm now running a full repair from the VS 2015 Update 2 CTP installer.  Fingers crossed.

:no_good:
Reboot after repair and it's still read-only.  I noticed however that I can cut & paste code to the editor.  Saving doesn't recompile the JS files though.
I'm heading home (GMT + 10 here) and will check this thread again in an hour or two.  I have some work to do tonight so am very happy to be a guinea pig for any suggested fixes you may have.

uninstall TS 1.8.4, repair Update 2 entry in Add/Remove programs should do the trick.

Unfortunately, this does not resolve the issue. Everything @IanYates has posted is the same for my machine. There is no Update 2 entry in Add/Remove programs, and Visual Studio is still showing 1.8.4 as being installed.
Testing out all these different repairs takes way too long. At this point, I'm beginning to think that doing a clean install is going to be the easiest fix for me.

I've uninstalled, reinstalled, uninstalled, gone crazy...  :fire:
I have run uninstallers for VS 2015 Update 1 from add/remove programs and then also ran the installer for Update2 CTP to ask it to remove itself.  Rebooting in between every change.
I tried just VS 2015 update 1, which claims to mostly work (some TFS component fails) but then I can't apply the servicing update for update 1 since it says it needs update 1 installed.  TypeScript files open but with no syntax highlighting or any other special behaviour.  Whilst VS doesn't talk about being a CTP in its splash screen it's help->about menu still mentioned CTP 2.
So I figured I might as well try to get on to Update 2 CTP.  It installs without complaint.  Reboot.
But now I'm back to square one - I can't edit any typescript files :(
How can I completely remove TypeScript from my system so that I can perhaps run the 2x TypeScript MSIs that ship with Update 2's CTP?  I assume there are registry keys and folders to remove.  I just don't want to remove too many and break things further.

Can you delete the component cache [0] and the activity log from your machine... and send me the activityog [1] when it's created again?
[0] %localappdata%\Microsoft\VisualStudio\14.0\ComponentModelCache
[1] %AppData%\Microsoft\VisualStudio\14.0

@paulvanbrenk -TypeScript language service version: 14.1840.40222.1
ActivityLog.txt

Can you nuke this folder C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TypeScript\ and re-run the update 2 installer from here https://www.visualstudio.com/en-us/downloads/update2-prereleases

@OSUblake just to make sure, did you open a TypeScript file before grabbing the activitylog? I don't see any errors in there, which is a unexpected.

I was wondering if that's what you wanted to happen, but I had to manually log that out.
After doing a repair and clearing the component cache, it stops creating errors when you launch VS, even though it's not working correctly.

@OSUblake did you try clearing the TypeScript folder and re-running the Update 2 installer.. not repair from 'Programs and Features'...
I'm setting up a machine to see if I can get it in the same state... but that's taking a little while.

I'm not near my computer right now, but I'll try again using the steps you provided.
I did try running the installer before, but it would always crash as soon as I pressed install. For some reason using the installer from the Visualstudio.com site would always cause it to crash, but the installer from the Microsoft.com downloads worked.

I've just gone through the nuking of folders and am about to try the typescript installer.

(Note that it says update 1 in the image but I fetched and ran the installer at https://www.visualstudio.com/en-us/downloads/update2-prereleases clicking the web installer link)
Setup log
dd_vs_enterprise_20160225070059.log.txt
After launching VS it's still broken I'm afraid.  No user visible errors. I can open a TS file and get syntax highlighting but I can't type.
Unfortunately there's now no activity log file.  Weird.  (I did delete the XSL stylesheet for it by accident - maybe that had an effect). I'll rerun with the -log parameter.

Version of typescript is now 1.8.0.  VS 2015 version is update 2 CTP 14.0.25008.00
The folder C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TypeScript\ is no longer on my PC so I can't check the language file version in that folder.
BUT, it is in the C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\VWDExpressExtensions\TypeScript folder now.
Version: 14.1840.40222.1
Activity log...
typescriptactivity.txt
Screenshot of help->About

A better activity log.  I realised that I renamed TypeScript folder to _TypeScript and could see in the previous log that VS enumerates all folders for extensions and found the _TypeScript folder.  It's now completely nuked.
So rerunning VS again gives me a TypeScript editor where I can type but
a) I do get an activitylog.xml file and a message telling me to go look at it
b) Saving the TS file does not recompile the JS file anymore
Activity log attached
ActivityLog.xml.txt

You probably saw this message:

Now I see TypeScript files as plain text files.. but no TypeScript features work.

Thanks @paulvanbrenk - I appreciate the help.

Great success!
Someone here suggested to do a system restore - my earliest one available happened to be from 24hrs ago when I installed TypeScript 1.8 :)
After coming back up the copy of Visual Studio was completely hosed :(  Every possible pane was showing an error referring me to the activity log.  Not pretty.
I ran the CTP 2 installer from the web which only took a couple of minutes but VS was still hosed but with fewer modal dialogs about errors.
I then ran the CTP installer from my previously downloaded "/layout" folder and was given a repair option.  That took a while (10-15 minutes?).  Reboot.
Open VS - one error about something inconsequential and I CAN EDIT TS FILES AGAIN!  Saving them makes a JS file too.
Happy! :dancer:

Had the same problem today after installing VS 2015 Update 2 CTP (typescript 1.8.4 was already installed) because my VS 2015 started acting up horribly while writing typescript code. Made a bad thing even worse for me as well, rather than VS 2015 freezing up at nearly every letter, it now simply ignored my input except for selecting/deleting/newlines. Running VS 2015 in safe mode(devenv /SafeMode) with all extensions disabled allowed me to edit *.ts files again, however without any typescript actually going on.
Found this github-issue, tried uninstalling typescript 1.8.4 and a series of uninstalling/reinstalling/repairing VS2015 Update2, with no success except new warnings and errors along the way. Eventually tried removing all leftover registry entries I could find from typescript 1.8.4 because the typescript installer from Update 2 CTP refused to install claiming 1.8.4 was still installed. Now the installer finally loaded but was immediatly gone just as well, figuring it hadnt worked I uninstalled VS2015 again. That uninstall failed on some visual studio update, so i tried that again but added /uninstall /force to the setup command line. Now, after reinstalling VS2015 and Update2 CTP once more, removing theC:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TypeScript\folder as mentioned here, and repaired Update 2 CTP ... I can actually edit and compile *.ts again.
The version of my Microsoft.VisualStudio.LanguageServices.TypeScript.dll is now 14.1800.40203.2. However, actually writing any typescript code in my project still behaves as before this Update 2 CTP story began: eating up my memory, frequently freezes for 30-60s periods, 'visual studio is busy notifications' and eventually it crashes. Got an error similar to what @paulvanbrenk posted as well, but it was quickly followed by many more components failing the same way (about 10 of 'em).
Tried a new project rather than my existing one, and no immediate typescript issues there. So I guess the issues I am currently still stuck with might be project-specfic rather than still relevant to this thread. Anyway, hope it helps,

Thanks for reporting back all... and we'll definitely make sure this won't happen in the future.

Maybe a workaround is to uninstall TS 1.8.4 and just install TS 1.8.1-beta again? (As that is what Update 2 CTP uses)
https://www.microsoft.com/en-us/download/details.aspx?id=48593 (click "Details")

@mwijnands we have bug which won't let you uninstall 1.8.4, if you have 1.7.x installed, which comes with Update 1.
So uninstalling 1.7.x first and then uninstalling 1.8.4 should work.

I see. And then install TS 1.8.1-beta or repair Update CTP 2 right.

@mwijnands repair.. the released version of 1.8.1-beta only works on Update 1.

@paulvanbrenk thanks!

How can I uninstall Update 2 ctp if it doesn't show in "Add or Remove Programs"?

Having the same problem with 1.8.x without CTP 2.  Just update 1.  Not sure what to try at this point.

@respectfulyellow what do you see after installing update 2? can you share your install logs (%temp%\dd_TypeScript*)? also can you share your activity log from VS and any error messages you see?

Does update 2 RC solve this issue?

Update 2 RC should have the correct version of TS (1.8.24.0). give it a try and let us know if you run into issues.

@mhegazy Running tsc -v from command line gives 1.8.0 -- is this expected?

Ok, I've restarted my machine and perhaps there were some env var issues, now I'm seeing 1.8.5 from tsc -v  (which is correct I think for VS plugin 1.8.6) -- right?

1.8.5 is correct.

Same issue here. I downloaded the latest ts.msi  (TypeScript_Dev14Full.exe) ran it, rebooted.
At cmd prompt i typed   tsc -v and it says Version 1.0.3.0 .
What I use to do is: FrontEnd stuff , run via gulp, but edited in Sublime Text 2. The backend WebApi was edited / compiled via  VS2015.
On 6th March 2106 I decided to bring all development under VS2015.
But I've now got these TS editing errors.
I reverting back to Sublime Text 2  / gulp runners for the front end.
This is another pathetic bug by MS, ever wonder why web devs just don't trust you, and never will !!!!
SORT IT OUT !

I noticed I had previous versions on TS for VS2015 installed.
So, via Control panel I uninstalled the older versions and the latest 1.8.6.0.
Rebooted my  I7 16G memory Win10 laptop.
I installed ver 1.8.6.0 again and rebooted.
Opened VS2015 and I CAN edit .ts files and compile etc via my gulp setup.
But when typing code the IDE seems slow to respond in general, I can out type what appears in the code window, I'm not that fast a typer either.
I now have a serious doubt w.r.t. VS2015 for the frontend.
I'm staying with my original development for frontend i.e. Sublime Text 2,, just a nagging doubt that's all.

The problem is back again !
I close VS2015, shut down my laptop.
3 hours later came back, started it up, .ts files will not edit ! Can only backspace.
Good job I'm using Sublime Text as mentioned above
So MS, when's the fix ?

@bikerboyroy Can you share the activitylog? Do you have Resharper installed?

Yes reshaper is installed and updated
Sent from my iPhone

On 8 Mar 2016, at 20:46, "Paul van Brenk" notifications@github.com wrote:
@bikerboyroy Can you share the activitylog? Do you have Resharper installed?
—
Reply to this email directly or view it on GitHub.

Can you disable Resharper for TypeScript files, and see if that works better.

I'll try give me a few moments
Sent from my iPhone

On 8 Mar 2016, at 20:49, "Paul van Brenk" notifications@github.com wrote:
Can you disable Resharper for TypeScript files, and see if that works better.
—
Reply to this email directly or view it on GitHub.

Hi
Disabled reshaper for ts and js. Still can't edit
Sent from my iPhone

On 8 Mar 2016, at 20:49, "Paul van Brenk" notifications@github.com wrote:
Can you disable Resharper for TypeScript files, and see if that works better.
—
Reply to this email directly or view it on GitHub.

Can you close VS, delete the activitylog [0], restart VS, and share the activity log if it re-opens.
Is this in any TS file, even ones not part of a project?
[0] %AppData%\Microsoft\VisualStudio\14.0\ActivityLog.xml

Hi
I'll do this in the morning, it's 21.17 in uk, I'm done :-)
Regards
Roy
Sent from my iPhone

On 8 Mar 2016, at 21:15, "Paul van Brenk" notifications@github.com wrote:
Can you close VS, delete the activitylog [0], restart VS, and share the activity log if it re-opens.
Is this in any TS file, even ones not part of a project?
[0] %AppData%\Microsoft\VisualStudio\14.0\ActivityLog.xml
—
Reply to this email directly or view it on GitHub.

@bikerboyroy do you happen to have a tsconfig.json in your project? does it have excludes anywhere? can you share the project, or a sample that reproduces the issue?

Hi
No I don't use a typescript config file, it's all run via gulp tasks. Can't share project due to legal reasons. What I can do is create a small test solution this morning and see if I get errors. The solution with the problem is using the latest mvc core dnx templates
Sent from my iPhone

On 9 Mar 2016, at 01:24, "Mohamed Hegazy" notifications@github.com wrote:
@bikerboyroy do you happen to have a tsconfig.json in your project? does it have excludes anywhere? can you share the project, or a sample that reproduces the issue?
—
Reply to this email directly or view it on GitHub.

Thanks to Paul & Mohamed for getting back to me.
Oped the test project this morning and it will still not edit .ts files. I have several small  ts files in the folder structure. I'm not sure if this locking is caused by me running gulp tasks.. anyway....
We've had a Skype meeting this morning to discuss.
What we're doing is keeping the C# WebApi part of the project in VS2013 , not porting to VS2015.
The frontend will still be developed via Sublime Text, we're upgrading to ver 3 of ST.
Thank you for your emails to me, hope you fix the problem

@bikerboyroy we would appreciate your help diagnosing this issue. We do not have other reports of this issue, so that leads me to believe it is something special about your project. we would be happy to sign any applicable NDAs to get access to your project, or a sample that reproduces the issue. feel free ot email me directly on mhegazy at Microsoft dot com

Hi Thank you but we're having to get on with the job at hand at the moment.Funny thing is: I shut down my laptop a few hours ago, an hour ago started it up and opened the test project in VS2015.It's working .ts files are editing ok. I've done nothing other then shutdown then start the machine again !RegardsRoy
Date: Wed, 9 Mar 2016 08:55:41 -0800
From: notifications@github.com
To: TypeScript@noreply.github.com
CC: roy_tynan@hotmail.com
Subject: Re: [TypeScript] Can't edit files in Visual Studio after installing 1.8.4 On Update 2 CTP (#7204)
@bikerboyroy we would appreciate your help diagnosing this issue. We do not have other reports of this issue, so that leads me to believe it is something special about your project. we would be happy to sign any applicable NDAs to get access to your project, or a sample that reproduces the issue. feel free ot email me directly on mhegazy at Microsoft dot com
—
Reply to this email directly or view it on GitHub.

same issue here. from one minute to another, i can't edit ts files. only backspace is possible.
in other projects it's currently possible, but i'm afraid that i get the same issue there!

Hi ALL.
It's happened again this morning. Start up etc , can't edit .ts file in my small test project.
I've not got the time to investigate any further.
The main project is staying VS2013 with ST3 for the frontend.
I have a meeting with the client to discuss the project on Monday. The dev team is 4 contractors including myself based around the UK, working remotely, with me as team leader.
We have ported the frontend to React via typescript in VS2013.
At the meeting on Monday I'm recommending a port of the backend C# Web Api to Node/Express rather than port to DNX via VS2015. The WebApi communicates to an external  Java WebService b.t.w
I really can't trust VS2015 for the frontend.
Sorry MS guys, but I can't spare any more time floundering about with VS2015.

My coworker and I are also having this problem. I uninstalled all versions of typescript and reinstalled the latest from the Extensions and Updates inside Visual Studio 2015.  We are still completely unable to type in any .TS files.  This is a serious problem and may be forced to ditch typescript for this project if it cannot be fixed soon.

I had the same problem. Like @mrunks I uninstalled all versions and then installed 1.8.1.0 Beta and it works. I'm not going for 1.8.4 or latest untill this is solved.

Stick with typescript. Use ST3 and build with gulp from command window. Just ditch VS2015 for frontend dev work.
Sent from my iPhone

On 11 Mar 2016, at 15:16, "Matt Unks" notifications@github.com wrote:
My coworker and I are also having this problem. I uninstalled all versions of typescript and reinstalled the latest from the Extensions and Updates inside Visual Studio 2015. We are still completely unable to type in any .TS files. This is a serious problem and may be forced to ditch typescript for this project if it cannot be fixed soon.
—
Reply to this email directly or view it on GitHub.

@mrunks can you provide some details on what version you had, and what you installed after that.
@cwojke any additional information is appreciated.

Stick with typescript. Use ST3 and build with gulp from command window. Just ditch VS2015 for frontend dev work.

@bikerboyroy we would appreciate the help solving this issue. we have not had a local reproduction of the issue you described. I would rather we solve the bug, rather than throwing the baby with the water; and for that we would need some more information.

We have visual studio 2015 with update 1.  Previously had 1.6 then installed the latest version from Visual studio Online gallery.  If is done use a config file for Typescript I can type but a project that uses the config file is where the problem seems to reside.

@mrunks this seems to be different from the OP. do you see this issue with a new project create from template? or just the project you are working on? what version of TS did you install from gallery?

Hi @mhegazy,here are additional information:
VS 2015 Community Edition with Update1. I have some other extensions installed like Web Essentials, Bundler & Minifier, Web compiler, WebPack task runner. No Resharper.
My solution consist of about 100 C# projects (Orchard CMS), 8 of them have Typescript and I couldn't edit .ts in any of them. In one project there is .tsconfig and some node modules (but not included in project), in other there is nothing but few .ts files.
The problem occured with TS 1.8.4 from downloaded installer. I could not type any characters in files with .ts and .tsx extension. Only wokring keys were Backspace (and maybe Delete, I'm not sure now).
Like I said before, after reverting back to 1.8.1. Beta I was able to edit these files again.

I suddenly got the same issue today (ts version 1.8.6). The only thing that helped was to add tsconfig.json to the project. After that I was able to edit ts files again. Maybe this helps someone else.

Same issue here. I was able to solve it by removing the comment on top of my tsconfig.json file.
Doesn't work:
/**
 * Comment
 **/
{
    "compilerOptions": {
        "module": "commonjs",
        "noImplicitAny": true,
        "allowUnreachableCode": false,
        "allowUnusedLabels": false,
        "forceConsistentCasingInFileNames": true,
        "noFallthroughCasesInSwitch": true,
        "noImplicitReturns": true,
        "removeComments": false,
        "preserveConstEnums": false,
        "sourceMap": false,
        "noEmitOnError": true,
        "emitBOM": false,
        "suppressImplicitAnyIndexErrors": false,
        "target": "es5",
        "declaration": true,
        "experimentalDecorators": true
    },
    "compileOnSave": false, // Gulp does this for us
    "exclude": [
        "node_modules"
    ]
}

Works:
{
    "compilerOptions": {
        "module": "commonjs",
        "noImplicitAny": true,
        "allowUnreachableCode": false,
        "allowUnusedLabels": false,
        "forceConsistentCasingInFileNames": true,
        "noFallthroughCasesInSwitch": true,
        "noImplicitReturns": true,
        "removeComments": false,
        "preserveConstEnums": false,
        "sourceMap": false,
        "noEmitOnError": true,
        "emitBOM": false,
        "suppressImplicitAnyIndexErrors": false,
        "target": "es5",
        "declaration": true,
        "experimentalDecorators": true
    },
    "compileOnSave": false, // Gulp does this for us
    "exclude": [
        "node_modules"
    ]
}

i got it working again by simply making a change in tsconfig.json, pressing save, revert it, save again - now i can edit files again

"birick:'s  comment's on Feb 23 worked for me.
He said "To resolve, remove any comments at the top of the tsconfig.json file (only use inline comments to the json), and then restart VS. To be safe, you might try removing any comments to the file and restarting VS and see if that fixes it."
I had comments above the open brace of my tsconfig.json file.  I simply moved them down inside the open brace.  Then I right clicked on the project, selected 'Unload Project', let it unload, then right clicked on the project again, (which now is labeled as '(unavailable)', and selected 'Reload Project'.  AFter the project loaded I could now edit the ts files normally.

I have updated to VS2015 update 2 RTM. My previous plugin version was 1.8.6 but after the update it has been downgraded to 1.8.29. Is there any risk in trying to install the latest plugin on update 2? or should I wait for a future release?

@malibuzios VS Update 2 installs a newer version of the plugin (29 > 6). And you will break VS if you manage to install 1.8.6.

@paulvanbrenk Thanks for the information, I assumed it was 1.8.2.9 as .29 seemed like a big jump :).

We fixed all the cases that we could find where parsing the tsconfig.file would break the editing experience and most of those fixes were shipped as part of Update. The remainder will ship in the next release of TypeScript.

Hello,
After installing TypeScript latest Next version (from https://www.microsoft.com/en-us/download/details.aspx?id=48593), I had the same issue (only backspace/delete key are active when editing any .ts file), Installing VS2015 Update 2 did not fix it either. What seems to fix it in my case is to remove the tsconfig.json file from the project (I use a fully independent gulp stack setup to compile my client-side typescript files, anyway). Home this can help someone.
As soon as I reintegrate the tsconfig.json file in the project, it breaks the .ts editor. And likewise, as soon as i remove it from the project, the editor starts working again.
For information: the file content I have is really simple:
{
"compilerOptions": {
"target": "es5",
"module": "commonjs",
"sourceMap": true,
"noResolve": true
}

@cboulva that's interesting... there are no comments anywhere in the tsconfig.json file?

Hello, no @paulvanbrenk , no comments at all.

@cboulva Missing parenthesis? In case you just din't copy&paste the last line...

it's happened, because of tsconfig.json file, actually I was trying to develop an Angular2 application in Visual Studio 2015 Update 2, once I added tsconfig.json file then .ts file get locked.
if I go to project property, say "one or more tsconfig.json files detected. project properties are disabled" and .ts file can't edit.
Please try to resolve ASAP
Thanks

@vikasjain6 Can you share the tsconfig.json file you were using.

below json setting was using
{
"compileOnSave": true,
"compilerOptions": {
"target": "es5",
"module": "system",
"moduleResolution": "node",
"sourceMap": true,
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"removeComments": false,
"noImplicitAny": false
},
"exclude": [
"node_modules",
"typings/main",
"typings/main.d.ts"
]
}

I had a similar problem: everything worked fine. But then, during typing in a typescript file, from one second to another, I no longer was able to edit anymore. Repairing Visual Studio took a lot of time, but did't change for the better.
Finally, I added a default tsconfig.json file, and - I was able to edit again. Afterwards I deleted the file again, but I am still able to edit.
Strange...

Had this same problem.  Renamed the tsconfig.json to tsconfig.json.bak.  I could now type again.  I restored the tsconfig.json and it still works.
Crazy bug.

I'm getting this issue using .tsx files only with the following setup:

For what it's worth, I am using MVC6, DNX, webpack and Reactjs.NET.
I have tried uninstalling all instances of typescript and then running a repair of visual studio and reinstalling typescript.
I have also tried removing/re-adding/renaming the tsconfig.json file. This did not help.
Finally, I created a new project using the default ASP.NET 5 MVC template. I added a .jsx file to that, and was also unable to edit.
This whole time, regular typescript (.ts) files are working fine. This is a super simple project based off of a super simple boilerplate at this point, so I'm honestly really at a loss to know what would be causing this issue.
Backspace, enter and delete seem to work, but that's it.

I added a .jsx file to that, and was also unable to edit.

.jsx or .tsx?

can you share your tsconfig.json

.tsx - typo there.
{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es6",
    "jsx": "preserve"
  }
}

There's absolutely nothing proprietary, it's just junk code, so I pushed the whole repo:
https://github.com/maggiepint/ReactTSBehavingWeird

I had to create a batch file to workaround this.
move tsconfig.json tsconfig.json.bak
REM start typing in the visual studio typescript file then un pause the this script to keep gulp happy
pause
move tsconfig.json.bak tsconfig.json

@CarlosOnline Can you elaborate on how exactly are you using your solution?
In my case after I rename the tsconfig file I regain editing ability, but when when the file is renamed back to its original name although I retain editing ability the project system is no longer using the tsconfig file and instead is looking at the project as if no tsconfig is present in the project.
Note: I'm using an ASP.Net 4.6 project not a ASP.Net Core one.

I make sure to restore tsconfig before typescript file is saved, otherwise gulp will fail.

After get latest with tfs I cant edit any typescrit files anymore. Turned source control plugin on and off, changed nothing in the tsconfig file, reboot and can still edit .js and .html files but no .ts files. unable to work

In my case I was able to overcome my problems by removing some content from my tsconfig.json file. More specifically I had a filesGlob element and a files element in my file, which weren't being used, my project builds with gulp and the source files are specified in another form. After removing these elements everything started working normally.
This leads me to believe that this problem might have something to do with some invalid content in tsconfig preventing the language service to operate properly.

@segersrobbert If you remove the tsconfig.json does editing work again... can you share your project?

I've upgraded visual studio and all works fine now. I'm sorry to say it's been a real struggle working with visual studio on front-end work besides this edit bug, configuring own compiling of typescript was a real hassle, its slow, it freezes and crashes quite often.

configuring own compiling of typescript was a real hassle, its slow, it freezes and crashes quite often.

@segersrobbert sorry to hear you are running into trouble there. We would love to get these issues fixed. Can you share more information about your set up, how can we reproduces the crashes, and freezes? can you share crash dumps, or at least stacks from relevant error events in your event viewer?

Setup: mac(10.11.4) running parallels with windows10, since updated to VS2015 update 2 crashes and freezes are no more. VS is still interfering with typescript compiling and adding its typescript compile tags to csproj whenever it feels like.

VS is still interfering with typescript compiling and adding its typescript compile tags to csproj whenever it feels like.

adding a new typescript file will always add it as TypeScriptCompile item.

VS is still interfering with typescript compiling

can you elaborate on this? what is the expectation and what is actually happening?

As soon as I reintegrate the tsconfig.json file in the project, it breaks the .ts editor. And likewise, as soon as i remove it from the project, the editor starts working again.

I ran into a similar issue to @cboulva, except my .ts files would only be editable when I added the tsconfig.json (default one from Add > New Item context menu) file back to my project.
I initially used VS to compile my .ts files, but then switched to using gulp for compiling them.  That's when I deleted the tsconfig.json file, restarted VS the following day, then ran into the non-editable .ts files.  Of course, adding it back made it work.
I also added the <TypeScriptCompileBlocked> line to my .csproj file to prevent msbuild from compiling the .ts files in my project.
    ....
    <TypeScriptToolsVersion>1.8</TypeScriptToolsVersion>
    <TypeScriptCompileBlocked>true</TypeScriptCompileBlocked>
</PropertyGroup>

@vanister can you share your project?

@paulvanbrenk sure, how do you want me to get it to you?

@vanister A repo on GitHub is probably easiest. Also, which version of VS and TypeScript are you using ( see Help - About).

@paulvanbrenk I'll create a repo for it and send you the details.  I'm using 2015 update 2 with TypeScript 1.8.31.  Whatever was installed the VS update 2 installer.  I am also using gulp-typescript and that typescript version is:
$ node_modules/gulp-typescript/node_modules/typescript/bin/tsc -v Version 1.8.10

@paulvanbrenk sent you and email

@vanister change the following in your project files:
-    <TypeScriptTarget>Unknown</TypeScriptTarget>
+    <TypeScriptTarget>ES6</TypeScriptTarget>

We don't gracefully deal with this will be fixed in the next release of TypeScript

Thanks @paulvanbrenk

I think I found the Issue!
I just ran across the same problem BUT I think I've tracked down the issue.
If I have a very simple project; which contains only a single ts file and a tsconfig.json file then I can edit the ts file. However, if I include the project's node_modules folder (which contains Angular2's QuickStart required modules - consists of 5,610 files) then I can't edit the ts file; well not for a few seconds that is.
On future investigation, I discovered that when I couldn't edit the ts file, the three drop-down list boxes were empty. But then after several seconds, I noticed that the first drop-down list box would finally show "TypeScript Virtual Projects" at which point, I could edit my ts file!!
By changing my tsconfig.json file to exclude the node_modules folder, I could edit my ts almost instantaneously.
My test tsconfig.json file:
{
    "compilerOptions": {
        "target": "es5",
        "module": "system",
        "moduleResolution": "Node",

        "declaration": false,
        "diagnostics": true,
        "removeComments": false,
        "sourceMap": true,
        "listFiles": true
    },

    "exclude": [
        "WebUtilities",
        "node_modules",
        "typings"
    ],

    "compileOnSave": true
}

Can anyone else verify that this fixed the issue?

@kabua that sounds very plausible.. I'll update the default tsconfig.json file to exclude node_modules and bower. Are there any other suggestions?

I am running into the same issue, and none of the fixes suggested here seem to be working. My .tsconfig has always excluded node_modules, so I can't add it pursuant to @kabua 's suggestion, so presumably that's not universally the cause of this issue. I tried adding and removing .bak on the .tsconfig and that also has made no difference. I'm compiling .ts into .js using VisualStudio, and not running gulp or any other such tool.
I have a question out on Stack Overflow here: http://stackoverflow.com/questions/37820711/visual-studio-2015-cannot-edit-typescript-files-get-exception-0x80020101 and I'm happy to share any other information that may be useful, though I can't upload the project itself without getting fired. :)

@natwebb Yeah, this looks like a different issue.. replied on the StackOverflow question.

At the suggestion of @paulvanbrenk I intalled Update 3 RC from here: https://www.visualstudio.com/downloads/visual-studio-prerelease-downloads and while the initial install failed, necessitating a restart and making VS unusable, running a Repair to get VS back up and running included a successful install of Update 3 RC and fixed the bug!

I started receiving this error after I updated to Update 3 (Final). I made a stackoverflow question about this issue: http://stackoverflow.com/questions/38184024/error-in-visual-studio-2015-update-3-when-opening-solution-typescript

I was able to edit Typescript files again when I installed Update 3 for VS.

Close VS2015.
In the root of your solution, go to .vs folder > folder named with solution name > v14 folder > delete the hidden vs file
Restart VS2015
Voila it works

authors: CarlosOnline IanYates IvanMisyats Lanayx MhausT OSUblake PeteCJohnson Ritzlgrmft ThomasSchoof bikerboyroy birick cboulva cwojke djarekg janb87 kabua maggiepint malibuzios mhegazy morsmodr mredl mrunks mwijnands natwebb oising paulvanbrenk pgorbas respectfulyellow segersrobbert teves-castro vanister vikasjain6


text:
Duplicate identifier error does not show up for method signatures

interface A {
    a();
    a();
    a();
}

Expected:
file.ts(2,5): error TSxxxx: Duplicate overload signature for 'a'.
file.ts(3,5): error TSxxxx: Duplicate overload signature for 'a'.
file.ts(4,5): error TSxxxx: Duplicate overload signature for 'a'.

Actual:

(no error)

Apparently the following also gives no error:
function f();
function f();
function f() {
}

Let me know if  PR #1572  needs more changes or is waiting on something

In my opinion this needs more concrete requirements/scope before it can even be attempted again.
Of the following, which (if any) are considered duplicate overloads:
type StringAlias = string;

declare function a(p1: string);          // Case 0

declare function a(p1: StringAlias);     // Case 1

declare function a(p1: any);             // Case 2

declare function a(p1: string | number); // Case 3

interface Parent {
    b();                                 // Case 4
}

interface Child extends Parent {
    b();                                 // Case 5
}

declare function a(p1: Parent);          // Case 6

declare function a(p1: Child);           // Case 7

?
Are there any more cases that need to be included (apart from those already mentioned here and in the comments above)?

authors: DanielRosenwasser begincalendar dekajp


text:
NodeJS Error: spawn EACCES (different variants of this error)

Hey all, I've been having this issue for a few weeks now with NodeJS with modules that specifically need to spawn child processes. The two main packages I've enconutered this with are create-react-app's "test" command and Zeit's Now CLI within WSL. Below is the information necessary for the issues I'm experiencing.
Please fill out the below information:

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.17134.619]

What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

Reproduce the Zeit Now CLI Error

npm i -g now
now login
Login with your now credentials
git clone https://github.com/tracy-codes/tracycodes-portfolio.git (project files used to push to now)
cd tracycodes-portfolio
now

Expected output is as follows:
$ now
now
> Deploying ~\dev\tracycodes\tracycodes-portfolio under tracycodes
> Using project my-portfolio
https://my-portfolio-cg6rbcv31.now.sh
┌ **        Ready               [414ms]
├── src/main.js
├── src/img/favicon.png
├── index.html
├── README.md
├── _redirects
├── src/style.css
├── about.html
└── coming-soon.html
> Success! Deployment ready [4s]

Actual output on WSL:
$ now
> Deploying /c/Users/tracy/dev/tracycodes/tracycodes-portfolio under tracycodes
> Using project my-portfolio
> Synced 5 files (8.87KB) [2s]
> https://my-portfolio-8zxgcamfp.now.sh [v2] [1s]
> Error! An unexpected error occurred!
  Error: spawn xsel EACCES
    at Process.ChildProcess._handle.onexit (internal/child_process.js:229:19)
    at onErrorNT (internal/child_process.js:406:16)
    at process._tickCallback (internal/process/next_tick.js:63:19) Error: spawn xsel EACCES
    at Process.ChildProcess._handle.onexit (internal/child_process.js:229:19)
    at onErrorNT (internal/child_process.js:406:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)

Reproduce create-react-app's test error

npm i -g create-react-app
create-react-app test
cd test
yarn run test

Expected output:
$ yarn run test
yarn run v1.13.0
$ react-scripts test
No tests found related to files changed since last commit.

Actual output in WSL:
$ yarn run test
yarn run v1.13.0
$ react-scripts test
Determining test suites to run...events.js:173
      throw er; // Unhandled 'error' event
      ^

Error: spawn hg EACCES
    at Process.ChildProcess._handle.onexit (internal/child_process.js:246:19)
    at onErrorNT (internal/child_process.js:421:16)
    at processTicksAndRejections (internal/process/next_tick.js:76:17)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:252:12)
    at onErrorNT (internal/child_process.js:421:16)
    at processTicksAndRejections (internal/process/next_tick.js:76:17)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

What's wrong / what should be happening instead:
I'm encountering multiple different "spawn EACCES" errors for Node modules that seem to require spawning child processes.

I've tested this with Jest with --watch, Create-React-App's "test" command, and the Now CLI from Zeit. For Create-React-App's "test" and Jest's --watch, they both output the "Error: spawn hg EACCES" with the above trace. I've tried the following to resolve the issue on my own:

Completely remove NPM, Node, and Yarn and reinstall from scratch
Install watchman (recommended by FB and seems to fix the issue on some Macs)
Set permissions to 777 for global node_modules and local modules in the projects' directories
Uninstalled/Deleted WSL and did a clean install, installed Node/NPM/Yarn first, then went through the reproduction steps above and still encountered the errors

Please let me know if there's anything else I can provide to add value to this issue report, and I hope someone can help me find a resolution for this!
I've reported this issue to Zeit's Now CLI team and they haven't ever encountered this error before:
#1902

Hi @tracy-codes !
Could you please run an strace on the failing commands? Instructions on how to do so are here.
It'll help us get a better picture of what's going on!

Hi @tracy-codes !
Could you please run an strace on the failing commands? Instructions on how to do so are here.
It'll help us get a better picture of what's going on!

Hi @mscraigloewen! Thank you so much for taking the time to investigate this issue. The following two gists are for the Now and the create-react-app test straces:

Now Strace Output
create-react-app test strace output files (this generated 198 strace files, these are the ones >1000kb):

https://gist.github.com/tracy-codes/cdec11a0410b264f55dacb8b0b649801
https://gist.github.com/tracy-codes/2952a3f58dda62a3c1ecc60bf6442596\
https://gist.github.com/tracy-codes/909062c6481d356f0f0a290863b7f6a7
https://gist.github.com/tracy-codes/f388c023607a53f663611f02532b7954
https://gist.github.com/tracy-codes/cca19eb84d6569eefdaeb740b71d3926

@mscraigloewen Sounds good! Thank you ❤

Well, the only EACCES in there is:
execve("/c/Users/Administrator/AppData/Local/Microsoft/WindowsApps/xsel", ["xsel", "--clipboard", "--input"], 0x4286910 /* 30 vars */) = -1 EACCES (Permission denied)

Which would strangely enough make this variation #3833 (https://github.com/Microsoft/WSL/issues/3833#issuecomment-462599467).
What does echo $PATH return for you right before you run now? Try:
$ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ # ... do node things

That might still fail for other reasons if now really requires xsel(1). It might not. (Wouldn't know. There is no repro and I've never really been a huge Tangerine Dream fan.)
If now really does require xsel(1) for reasons, then do sudo apt install xsel after rationalizing your $PATH.

@therealkenc Running that path cmd and doing my node things seems to have worked! I think this issue is solved by the export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin command. Thank you so much!

I'll close out this issue. Thank you for the fix @therealkenc , and thanks for filing the issue @tracy-codes !

Thank you for the fix @therealkenc

YW. Glad you're up and running.
But just for clarification, the underlying bug in both this issue and #3833 remains. I have no horse in that race mind you, and am never one to turn down a closed issue#.
If /c/Users/Administrator/AppData/Local/Microsoft/WindowsApps/xsel or /mnt/c/WINDOWS/system32/config/systemprofile/.dnx/bin/help can't be executed, then they shouldn't have been marked as executable. This is a diverge. I can't tell for sure if that counts as dupe #2779 or not (maybe not). But I can say the WSL ABI is coughing up dirents that claim they can be executed when they can't. Because, otherwise now wouldn't have tried to execve() the thing, only to die trying. Rationalizing the $PATH to something sane avoids the issue, but doesn't address the underlying problem. Just sayin'.

Ah I see! I'll re-open the issue so we can track that the underlying cause isn't fixed.

Alright I looked a little closer since I went and opened my mouth. I had said quoth "the WSL ABI is coughing up dirents that claim they can be executed when they can't". That isn't the case. zsh and presumably now (whatever now is) is blindly appending names to the $PATH components. This makes sense in Real Linux™ because putting a component in your $PATH that you don't have permission to access is just plain "user error".
In WSL (contrast the real thing) we have the added snag of paths where the underlying Windows user doesn't have permission. This is harmless in Windows because Windows software is written with the assumption that can happen. Having nonsensical components in one's Window's %PATH% is "normal". But Linux software isn't written with that assumption.
The repro over in #3833 is maybe better because .../Microsoft/WindowsApps/xsel here looks to be something third party that the OP installed. Over there, .../.dnx/bin is in WSL's $PATH if you've installed Visual Studio 2015. [I gather. Actually I wouldn't know a DNX from the hole in the ground either but I think it gets put in the Windows %PATH% along with the kitchen sink that is MSVS.] I guess I got "lucky" because if I didn't have MSVS 2015 I wouldn't have had the path component, I wouldn't have been able to reproduce #3833's problem either.
$ echo "$PATH" | tr ':' '\n' | grep WINDOWS/system32
/mnt/c/WINDOWS/system32
/mnt/c/WINDOWS/system32/config/systemprofile/.dnx/bin

But that path isn't accessible, because the Windows user (me) doesn't have permissions to that path. That's going to be the case for the OP's xsel too.
Fix is going to be to launder path components from being imported when the Windows user doesn't have permission to that component. Basically, interop is imposing a "user error" on WSL, because it is putting components in the $PATH that can't ever be accessed. The ABI strictly speaking is correct.

Running into this issue when trying to child_process.spawn() a java command but the user doesn't have Java installed.  So as I understand the above it's trying to check everything in the $PATH but then runs into permissions issues?
I also can't find a way to catch this error, I would be fine to workaround it because I know the meaning in this case but it seems to always throw for me.

Yes

some problem ...

Among all those converted paths in %PATH% appended to $PATH some contain subdirectories named like common executables, say help or md5.  (As an aside, perhaps they should preferably be prepended?)
For the moment, you can remove in ZSH an offending path that contains a subdirectory named like an executable, say /mnt/c/Program Files (x86)/Lua/5.1/clibs which contains a subfolder md5, from $PATH by
# See https://stackoverflow.com/questions/370047/what-is-the-most-elegant-way-to-remove-a-path-from-the-path-variable-in-bash/29159378#29159378
removeFromPath() {
   local p d
   p=":$1:"
   d=":$PATH:"
   d=${d//$p/:}
   d=${d/#:/}
   PATH=${d/%:/}
}
removeDirFromPath "/mnt/c/Program Files (x86)/Lua/5.1/clibs"

According to Bart Schaefer this is intentional. See this question for possibly further answers.

According to these comments the fix might be as simple as updating zsh to version 5.7.1.

My personal fix to avoid this problem was the realization that in WSL:
mv file.txt other.txt
fails miserably when there are file watchers, but
cp file.txt other.txt
rm file.txt
is totally OK
:pensive:
I am trying to survive with a temporal shell alias mv.wsl until WSL2 solves all the problems :sparkles:

authors: Konfekt fgarcia jottasystem mscraigloewen samtstern therealkenc tracy-codes

repo: Microsoft/WSL


text:
XamlListView throw exception

System.InvalidCastException: 'Unable to cast object of type 'System.Char' to type 'System.String'.'
at ListViewSample.SimpleGridViewSample.SimpleGridViewSample_obj10_Bindings.Update_Key(Object obj, Int32 phase)
at ListViewSample.SimpleGridViewSample.SimpleGridViewSample_obj10_Bindings.Update_(GroupInfoList obj, Int32 phase)
at ListViewSample.SimpleGridViewSample.SimpleGridViewSample_obj10_Bindings.Update()
at ListViewSample.SimpleGridViewSample.SimpleGridViewSample_obj10_Bindings.DataContextChangedHandler(FrameworkElement sender, DataContextChangedEventArgs args)

Quick fix is to make GetContactsGrouped in Contacts.cs (line 108) select a String key to group on instead of a Char. Also added ToUpper to eliminate a mixed case scenario.
var query = from item in GetContacts(numberOfContacts)
                        group item by item.LastName.Substring(0, 1).ToUpper() into g
                        orderby g.Key
                        select new { GroupName = g.Key, Items = g };

Fixed in v5.0.4

authors: egmkang jburman oldnewthing

repo: Microsoft/Windows-universal-samples


text:
JSON parse error when receiving error messages from test cloud upload endpoint

Errors are in some cases send as text and not JSON. The cli can look at the content type of the reply  to determine the format.
Steps to reproduce:
Upload ipa with architecture that is not compatible with the device selection.
Result:
Error "Unexpected token N in JSON at position 0" occurred in deserializing the responseBody - "No valid devices in selection (fb9a78d3: 1 devices)" for the default response.
Expected result:
Error output with the following content:
No valid devices in selection (fb9a78d3: 1 devices)

Is this issue resolved or not? I'm still getting same error while uploading iOS app to appcenter.
Error: Error "Unexpected token N in JSON at position 0" occurred in deserializin
g the responseBody - "No valid devices in selection (e1439c1a: 1 devices)" for t
he default response.

We talked about this a bit in the test cloud team. The issue is that the swagger file in appcenter does not tell the truth entirely. on HTTP code 200 we return JSON alright, but on != 200 we return plaintext. The swagger declares that it is always JSON.
IOW: the fix is to update the server side swagger, then regenerate the client libs in this project.
(@prashantchoubey16 the issue is not fixed yet - sorry)

I get the same error

This issue is now fixed on the server-side, which should now be returning proper JSON in all error cases. @prashantchoubey16 /cc @glennwester

Will close for now per @jacobe request. Thanks!

authors: curia-damiano glennwester jacobe john7doe kamstrup prashantchoubey16

repo: Microsoft/appcenter-cli


text:
Update to the overview document

We don't support partner logs. I updated with what we now support

#Sign_Off

#sign_off

#sign_off

#sign-off

#sign-off

#signoff

I'm not sure why we are not seeing validation and staging on this, if folks have signed off. I will try closing and reopening.

Hi @ndolker, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Namgyal Dolker). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@ndolker : Thanks for your contribution to the Azure documentation! The author, @TomShinder, has been notified to review your proposed change.

Only the author of the article can use the sign off comment to add the ready-to-merge label.

#sign-off

#sign-off

Only the author of the article can use the sign off comment to add the ready-to-merge label.

added ready-to-merge label manually due to metadata attribute updates in PRMerger

#sign-off

#sign_off

#signoff

@ja-dunn @KatieCumming - This PR has been stalled.  Can one of you merge it or let us know what is needed before it can be merged?  Author Tom Shinder has signed off.

@KatieCumming - Thank you!

authors: Ja-Dunn PRmerger TerryLanfear TomShinder daveba msftclas msmbaldwin ndolker

repo: Microsoft/azure-docs