Skip to content

[6.5] Ref/canvas interpreter2 oss take5 (#26068)#26108

Closed
ppisljar wants to merge 1 commit intoelastic:6.5from
ppisljar:backport/6.5/pr-26068
Closed

[6.5] Ref/canvas interpreter2 oss take5 (#26068)#26108
ppisljar wants to merge 1 commit intoelastic:6.5from
ppisljar:backport/6.5/pr-26068

Conversation

@ppisljar
Copy link
Copy Markdown
Contributor

Backports the following commits to 6.5:

# Conflicts:
#	package.json
#	src/setup_node_env/babel_register/register.js
#	x-pack/package.json
#	x-pack/plugins/canvas/__tests__/fixtures/function_specs.js
#	x-pack/plugins/canvas/common/lib/index.js
#	x-pack/plugins/canvas/init.js
#	x-pack/plugins/canvas/server/routes/plugins.js
#	x-pack/plugins/canvas/server/routes/translate.js
#	x-pack/plugins/canvas/tasks/helpers/webpack.plugins.js
#	yarn.lock
@ppisljar ppisljar added the backport This PR is a backport of another PR label Nov 23, 2018
@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@ppisljar
Copy link
Copy Markdown
Contributor Author

ppisljar commented Nov 23, 2018

@LeeDr @spalger do we even want to backport this to 6.5 ?
pros: it will be easier to backport canvas bug fixes
cons: its a huge PR, not a bug fix

@spalger
Copy link
Copy Markdown
Contributor

spalger commented Nov 23, 2018

I'm going to try and submit this backport

@spalger spalger closed this Nov 23, 2018
@spalger
Copy link
Copy Markdown
Contributor

spalger commented Nov 23, 2018

There are already a lot of conflicts that seem to indicate that 6.5 isn't getting a lot backported to it from the canvas team, so I'm good with skipping 6.5 here. @rashidkpc @w33ble do you guys agree? Would you be able to help with some of the conflicts? This pr is a lot bigger than it should be, so we should probably start a fresh backport to make sure it's accurate if we're going to do it.

@rashidkpc
Copy link
Copy Markdown
Contributor

I don't think there's any reason to back port this to 6.5 at all. Nothing going into 6.5 depends on it and I'd rather not risk introducing regressions in a patch release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants