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
env.getEnvironment return {} in standalone mode. #101
Conversation
|
We will going to prepare try2 with this revision points, thanks for your review =)!!! |
|
@dnarvaez, @rogemita Should we take some action due to this known issue? |
|
I tend to think adding a comment would be fine for now. I can't think of a way to avoid the race either, we might have to write a webkit extension and avoid the hack if it turns out we need to be multi thread safe. |
|
One possible approach to get rid of the race without having to write C code might be to fetch an activity://..../environment.json (dynamically generated on the python side). I sort of like that approach actually, it feels better of what we have now at least. |
|
(Breaking the contract with toolkit would be annoying for backward compatibility reason, but I'm not sure we should start worrying too much about that yet). |
so is ok at the moment, a message on getEnvironment function, like: ...
??? |
|
Maybe "// FIXME we assume this code runs on the same thread as the javascript executed from python" or something like that. |
|
summary for try2:
@dnarvaez, I'm going to fix those points and push directly (if you agree). |
|
Yup! |
|
pushed Thanks for reviewing! |
NOTE: env.getEnvironment single-thread only