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

opa project no longer runnable with 1.0.6 #84

Closed
exterm opened this issue Sep 10, 2012 · 3 comments
Closed

opa project no longer runnable with 1.0.6 #84

exterm opened this issue Sep 10, 2012 · 3 comments

Comments

@exterm
Copy link

exterm commented Sep 10, 2012

I just updated the arch opa package to 1.0.6 but now my project is no longer runnable.

Node version is 0.8.8.

It compiles just fine. When I run it, I get

/usr/lib/opa/static/opa-js-runtime-cps/main.js:23
global.ccont = function (k,f){return [f,k[1]];};
^
TypeError: Cannot read property '1' of undefined
at global.ccont (/usr/lib/opa/static/opa-js-runtime-cps/main.js:23:42)
at /usr/lib/opa/stdlib/stdlib.qmljs/stdlib.core.rpc.core.opx/a.js:2694:204
at /usr/lib/opa/stdlib/stdlib.qmljs/stdlib.core.rpc.core.opx/a.js:2758:180
at /home/philip/projects/opa/opaah/opaah_depends/node_modules/opaah.opx/a.js:62:139
at Object. (/home/philip/projects/opa/opaah/opaah_depends/node_modules/opaah.opx/a.js:62:155)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:362:17)

@BourgerieQuentin
Copy link
Contributor

Hi,

Are you sure your project built are well cleaned, and recompiled (rm -rf _build opaah_depends)?
Indeed I taken a look with your backtrace and the error is raised with the use of Network.cloud,
but all of our tests works well.

Else do you have a piece of code to reproduce?

@exterm
Copy link
Author

exterm commented Sep 11, 2012

I'm not entirely sure but it seems that a left over @async annotation with the Network.cloud provoked the error. The build was totally cleaned before.

If this annotation is no longer supported, shouldn't the compiler throw an error? Or is it still supported and I just used it in the wrong way?

@BourgerieQuentin
Copy link
Contributor

Thanks for information, I was able to write a minimal test case.

@async Network.network(string) n = Network.cloud("test")
Network.observe(jlog, n)
Network.broadcast("Hello world", n)

It's a regression and I fixed it.
The patch (sha f8928ae) should be released on the next nightly (>= 3380).

Else I don't think you really want to use the 'async' directive on the network?
Basically in this example the async directive means 'compute n as an asynchronous value',
i.e. 'detach' the computation of n, then the use of n wait the end of computation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants