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

[backport] Fixing old backport for content-disposition in reporting #49249

Merged
merged 1 commit into from
Oct 25, 2019
Merged

[backport] Fixing old backport for content-disposition in reporting #49249

merged 1 commit into from
Oct 25, 2019

Conversation

joelgriffith
Copy link
Contributor

We had an older backport get merged, but then get orphaned in a file-system change. This PR fixes that, assuming we want this change and are going to do another 6-series release.

@tsullivan
Copy link
Member

Looks like this fixes a backport that did not work perfectly? Can we link to that backport PR here? That will give us a fuller picture

@joelgriffith
Copy link
Contributor Author

joelgriffith commented Oct 24, 2019

Original backport is here: #31713

EDIT: it does look like my backport ended up in the wrong spot since I don't see the old JS version being deleted. It's possible that my fix was based upon the new file-system changes, and the backporting tool didn't really "catch" it. I think from now on:

  • Bugfixes should have tests.
  • Backported branches should be smoke tested.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Member

@tsullivan tsullivan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@tsullivan tsullivan merged commit cce96d2 into elastic:6.8 Oct 25, 2019
@LeeDr LeeDr added the v6.8.5 label Nov 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants