[
https://issues.apache.org/jira/browse/COUCHDB-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121871#comment-13121871
]
Riyad Kalla commented on COUCHDB-1302:
--------------------------------------
Now is the perfect opportunity to make this change, once 1.2/2.0 goes out the
door it likely couldn't be safely addressed again until 3.0 and the uptake in
CouchDB (from what I see at least) seems to be on the rapid rise.
Making this change in 1.2/2.0 becomes an education issue, so maybe some
questions around how to be *really* helpful explaining the situation to the
user, e.g. errors in the server log when the problem is encountered and exactly
how to work around it pointing at a Wiki page with clarification explaining
why; maybe warnings during startup when the server does a quick scan for the
issue (that can be disabled if the user knows they have a good setup);
Sure it will be painful, but trying to monkey-patch this until 3.0 (or beyond)
will be much more painful and have a lot more negative impact by that time.
I like Jason's suggestion of some quick-patch tool that might ship with the
install that attempts the fix automatically or at least gives the users enough
tools and help/information so as to get them from Point A to B as quickly as
possible.
> Fix couchjs
> -----------
>
> Key: COUCHDB-1302
> URL: https://issues.apache.org/jira/browse/COUCHDB-1302
> Project: CouchDB
> Issue Type: Improvement
> Components: JavaScript View Server
> Affects Versions: 1.1.1, 1.2, 1.3
> Reporter: Paul Joseph Davis
> Priority: Blocker
>
> Figure out why some spidermonkeys have an error when doing:
> eval("function(){}")
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
