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

Use single backslash for nested paths in YAML integration tests #66794

Merged
merged 1 commit into from
Dec 23, 2020

Conversation

sethmlarson
Copy link
Contributor

This integration test is causing failures in a few clients repositories due to the double backslash. It seems like a single backslash is what is used elsewhere. The change was introduced in #65641.

cc @elastic/clients-team

@sethmlarson sethmlarson changed the title Use single backslash for nested paths Use single backslash for nested paths in YAML integration tests Dec 23, 2020
Copy link
Contributor

@jtibshirani jtibshirani left a comment

Choose a reason for hiding this comment

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

Thanks @sethmlarson for fixing this! Good to know when writing future tests.

@jtibshirani jtibshirani added >test Issues or PRs that are addressing/adding tests Team:Clients Meta label for clients team labels Dec 23, 2020
@jtibshirani
Copy link
Contributor

Looking at the labels: maybe we should backport to 7.10 too since we're actively testing that branch.

@sethmlarson
Copy link
Contributor Author

@jtharpla Definitely, thanks for the review!

@sethmlarson sethmlarson merged commit 11153fc into master Dec 23, 2020
@sethmlarson sethmlarson deleted the nested-path-single-backslash branch December 23, 2020 17:57
sethmlarson added a commit to sethmlarson/elasticsearch that referenced this pull request Dec 23, 2020
sethmlarson added a commit to sethmlarson/elasticsearch that referenced this pull request Dec 23, 2020
sethmlarson added a commit to sethmlarson/elasticsearch that referenced this pull request Dec 23, 2020
Mpdreamz added a commit to elastic/elasticsearch-net that referenced this pull request Dec 28, 2020
Already fixed upstream but needs to find its way to the docker images.

Relates: elastic/elasticsearch#66794
Mpdreamz added a commit to elastic/elasticsearch-net that referenced this pull request Dec 28, 2020
Already fixed upstream but needs to find its way to the docker images.

Relates: elastic/elasticsearch#66794
github-actions bot pushed a commit to elastic/elasticsearch-net that referenced this pull request Dec 28, 2020
Already fixed upstream but needs to find its way to the docker images.

Relates: elastic/elasticsearch#66794
github-actions bot pushed a commit to elastic/elasticsearch-net that referenced this pull request Dec 28, 2020
Already fixed upstream but needs to find its way to the docker images.

Relates: elastic/elasticsearch#66794
Mpdreamz added a commit to elastic/elasticsearch-net that referenced this pull request Dec 28, 2020
… to land (#5218)

Already fixed upstream but needs to find its way to the docker images.

Relates: elastic/elasticsearch#66794

Co-authored-by: Martijn Laarman <[email protected]>
Mpdreamz added a commit to elastic/elasticsearch-net that referenced this pull request Dec 28, 2020
… to land (#5217)

Already fixed upstream but needs to find its way to the docker images.

Relates: elastic/elasticsearch#66794

Co-authored-by: Martijn Laarman <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Clients Meta label for clients team >test Issues or PRs that are addressing/adding tests v7.10.2 v7.11.1 v7.12.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants