Skip to content

Conversation

@yjbanov
Copy link
Contributor

@yjbanov yjbanov commented Jun 23, 2017

The upstream fix was: dart-archive/usage@021664e

Absence of clientId caused crash reporting to not function in the rare situation when $HOME/.flutter has not been initialized yet.

@jason-simmons
Copy link
Member

LGTM

@yjbanov yjbanov merged commit 0426fb6 into flutter:master Jun 23, 2017
@Hixie
Copy link
Contributor

Hixie commented Jun 23, 2017

BTW, this was checked in when the tree was red. Please avoid checking anything in when the tree is red except for attempts to fix the tree. Thanks!

@yjbanov
Copy link
Contributor Author

yjbanov commented Jun 23, 2017

Sorry, thought it was safe enough because everything else is green. Can rollback if this change is risky.

@Hixie
Copy link
Contributor

Hixie commented Jun 23, 2017

It's probably fine. The problem is just that we don't really know since not all the tests are actually running, so if this or anything else checked in on red did actually regress anything, we might not discover until later, at which point this would be just one checkin among many for us to try to search through when trying to find the problem.

gspencergoog pushed a commit to gspencergoog/flutter that referenced this pull request Jul 1, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants