Manuel Jasso

Update: it looks like the name of the local branch doesn't matter, I changed my `foo` branch to track `github/master` and then `yarn start` worked fine! 🤷🏻‍♂️ This is my...

I tried a fresh checkout of best repo and the condition is that the current branch has to be tracking something that is **not** `[origin/master]`, this is my fresh setup...

But given the conditions, this is a low priority issue because there is a workaround.

Mh, no, even one branch causes the error, I just pulled new master from best and these are the simplest repro steps I was able to come up with: Do...

Thanks, I know tracking a local branch makes no sense, this was just my simplest repro steps, I saw this error without tracking a local branch but I don't remember...

Sure @caridy let's talk about details, maybe an adaptation of the diagram we have or split it, etc.

Hi @AllanOricil, thanks for the report, @nolanlawson kindly mentioned it in our internal channels and the @salesforce/ui-security team is aware. We'll probably need some details in order to reproduce it,...

Hello @AllanOricil, thanks for the details. Again we need to analyze this in detail to be sure, but it looks like LWS is doing what it is supposed to do:...

@seksenov @caridy Tracking on W-7429747

Hi @AllanOricil, I am from Locker team, I would like to reproduce this issue, is there an environment you can point me to and steps to reproduce? Ideally, I would...