Skip to content
This repository was archived by the owner on Nov 24, 2021. It is now read-only.

Lab doesn't work with Benthos v3.2.1 (seems like it's Go 1.13) #18

Closed
ilyaglow opened this issue Oct 2, 2019 · 6 comments · Fixed by #19
Closed

Lab doesn't work with Benthos v3.2.1 (seems like it's Go 1.13) #18

ilyaglow opened this issue Oct 2, 2019 · 6 comments · Fixed by #19
Assignees
Labels
bug Something isn't working

Comments

@ilyaglow
Copy link
Contributor

ilyaglow commented Oct 2, 2019

I tried to build a lab with the latest benthos version (3.2.1) that requires Go 1.13.

It builds successfully with a few Dockerfile changes, but the Attempting to initialise Benthos engine... message doesn't disappear when I visit UI.

In the browser's console I see the following error:

(index):1 Uncaught (in promise) LinkError: WebAssembly.instantiate(): Import #20 module="go" function="syscall/js.copyBytesToGo" error: function import requires a callable
Promise.then (async)
(anonymous) @ editor.js:400

I noticed that whatever version of benthos I try to build with Go 1.13 in the lab I get the same error.

@Jeffail Jeffail self-assigned this Oct 2, 2019
@Jeffail Jeffail added the bug Something isn't working label Oct 2, 2019
@Jeffail
Copy link
Member

Jeffail commented Oct 3, 2019

Looks like it's this: golang/go#29827 (comment)

Just need to remember that any time we upgrade the version of Go we also need to update the .js file that comes with it. I'll update later today and add comments on our docker images as a reminder for next time.

@Jeffail
Copy link
Member

Jeffail commented Oct 3, 2019

Looks like there's also a regression so we might not be able to upgrade to 1.13 until this is resolved golang/go#34395

@DpoBoceka
Copy link
Contributor

Looks like it's been patched up. Would love to have benthos lab up to date

@Jeffail
Copy link
Member

Jeffail commented Feb 4, 2020

Still getting LinkError: data segment does not fit in memory with Go 1.13.7.

@DpoBoceka
Copy link
Contributor

DpoBoceka commented Feb 4, 2020

Should we report the unexpected behaviour?

@Jeffail
Copy link
Member

Jeffail commented Feb 4, 2020

If we can dig into it more, I'm a little stretched right now so I'd rather not take this on right now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants