-
Notifications
You must be signed in to change notification settings - Fork 12
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
problem sending messages #3
Comments
Here is the trace from the couchdb log:
|
oops, closed by mistake, sorry. reopening. |
@JasonSmith : Any reason why you wouldn't take this pull request? It would be very useful for us :) |
Sorry @jhs :) |
@jhs Thanks for the feedback! |
Are you running the unit test suite? I would like to see exactly which test fails to help identify the problem. I updated the documentation (and I made a mistake and had to Can you run the tests with your couch? Does it give any clues? If you have an Iris Couch account, does it behave any differently there? Thanks! |
P.S. I believe the browser versions of the test have some errors, I will fix them before releasing another version but for now, the |
Final note, I suppose the most likely thing is still regular expressions. Perhaps changing them to a string method instead?
However I will wait for your feedback before changing the code again. |
Iriscouch works, but on my install fails. Strange, because it's a fresh homebrew install. Anyway, don't bother, I'll first try changing the ddoc as suggested. |
Ok, good idea. The only thing to check is that sometimes I needed the regex match results to extract substrings. That is why I like Good luck with the change, let me know if you have problems (I am also JasonSmith in #couchdb on Freenode), during daytime, US central. |
Hey, I am Jason Smith too. Not sure why I am on this list. Can someone Thanks On Fri, Sep 16, 2011 at 9:07 AM, Jason Smith <
|
@pgte I think you are the first user of CQS on a non-Jason CouchDB build (i.e. not Iris Couch or build-couchdb). I am sorry that you encountered frustrating bugs. I was too careless writing with modern Javascript features that are not yet universal on the server-side. Anyway, if I push a branch or two with some portability ports, are you able to test them? If so, I have some ideas to fix the bugs (mostly regular expression and possibly some Object.keys() calls and similar things. Thanks very much for your help and your patience! |
Hi Jason, thanks for the feedback! Meanwhile I have been distracted by other things, but I intend to revisit this, since it would be great to start using couchdb for everything, including message queueing. |
CouchBase will install cleanly and easy. Get the community edition |
Replaced log4js with debug, pass `require` to defaultable
I create a queue and all looks good. Here is the design doc source: https://gist.github.com/1211432
When sending a message I get a 500 response status from couchdb.
In introduced some debugging at the request level and found that the error was {"error":"case_clause","reason":"{[{<<\"message\">>,<<\"/^CQS\\//.test is not a function\">>}
which comes from the validate_doc_update on the design doc, line 17:
...
if(! /^CQS//.test(newDoc._id)) // A simple test, hopefully future-proof
...
BTW, I'm using cqs 0.3.0, node 0.4.10 and couchdn 1.1.0.
Thanks.
The text was updated successfully, but these errors were encountered: