Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cherry picking fixes into release #8032

Closed
wants to merge 5 commits into from

Conversation

karthiknadig
Copy link
Member

No description provided.

@karthiknadig
Copy link
Member Author

@kimadeline @luabud Have i missed any other fixes?

@codecov-io
Copy link

codecov-io commented Oct 17, 2019

Codecov Report

Merging #8032 into release will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           release    #8032   +/-   ##
========================================
  Coverage    58.78%   58.78%           
========================================
  Files          496      496           
  Lines        22126    22126           
  Branches      3560     3560           
========================================
  Hits         13006    13006           
  Misses        8308     8308           
  Partials       812      812

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 48fe766...f505a8e. Read the comment docs.

@kimadeline
Copy link

@karthiknadig 73b5937 for #7607 was merged into master but hasn't been validated yet, so I don't know whether we want to include it or not despite it being a P0.

Do we need to cherry-pick DS commits too?

@karthiknadig
Copy link
Member Author

DS is currently testing their fixes. They will be cherry-picking it into release and let me know.

@karthiknadig
Copy link
Member Author

karthiknadig commented Oct 18, 2019

@rchiodo Are you guys done with fixes needed for the point release?

@karthiknadig
Copy link
Member Author

73b5937 for #7607 was merged into master but hasn't been validated yet, so I don't know whether we want to include it or not despite it being a P0.

@luabud What is your opinion on this. I think we should take it since the prompt is showing up on Windows. I tried this on a couple of my windows machines. I did not get a prompt. Then again I am not sure how clean they were since this fix requires a clean install.

* Don't prompt inheritEnv on windows
* Add verification for undefined workspace config
* Why did i commit that formatting change
@rchiodo
Copy link

rchiodo commented Oct 18, 2019

@rchiodo Are you guys done with fixes needed for the point release?

No sorry still have one more. We haven't moved our changes into release yet either.

@rchiodo
Copy link

rchiodo commented Oct 18, 2019

We wanted to bug bash some more.

@luabud
Copy link
Member

luabud commented Oct 21, 2019

@karthiknadig yes please let's take the prompt (it's been validated now, right?)

@karthiknadig
Copy link
Member Author

@luabud i will include the prompt fix. I am going to close this one. since one of the cherry pics had a conflict and looks like it was not merged correctly.

@karthiknadig karthiknadig deleted the release branch October 21, 2019 18:32
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
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.

6 participants