-
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
running 'all tests' on CouchDBX 0.11 fails at 'oauth' and then requires admin password ? #13
Comments
Hi, thanks for the report! Can you send me your operating system specs and other info like if you have previous couchdb installs and/or macports installed? |
It's Leopard 10.5.8, I've never used macports but used to run an earlier version of couchdbx (CouchDBX-0.9.1-R13B-pl2). I'm able to delete databases etc. until i run the testsuite, then it all goes doolally. |
I have the exact same issue running CouchDBX-R13B2-0.10.0-Leopard. I'm actually on a 32-bit machine with Snow Leopard, but as has been pointed out in another issue, the Snow Leopard CouchDBX fails to boot. Leopard CouchDBX seems to run fine, until running the test suite and hitting the oauth test. No macports, no prior CouchDBX installs. Stopping and starting CouchDBX returns to a happy place, no more authorization requests. |
I have the same problem when running the tests. OS X 10.5.8, first time with CouchDBX. |
Seeing the issue here when using Futon (on CouchDB 0.10.1 on Snow Leopard) within the standalone app, but not when performing the tests through an actual web browser. For those having problems during and after the "oauth" test, try using the web interface (http://localhost:5984/) and run the automated tests from there. I'm still seeing a couple of other test failures, mostly with "erlang_views" and "rev_stemming," but the oauth issue seems to be isolated to the standalone Futon app. |
m104's assessment agrees with what I'm seeing on CouchDBX-0.10.1-R13B03-Leopard (on an actual Leopard machine this time, to boot). oauth tests pass with Safari. |
The tests run only(!) in a separate browser and that browser needs to be Firefox. This is a limitation of the test suite / webkit combination, nothing CouchDBX can do anything about. |
if I run the test suite, it starts to fail at the oauth test:
1> [info] [<0.1060.0>] 127.0.0.1 - - 'GET' /_session?foo=bar&oauth_signature_method=PLAINTEXT&oauth_consumer_key=nonexistent_key&oauth_token=bar&oauth_token_secret=%40%02%C2%A0%C2%92%C2%B9%C3%A9wx%C3%B8%C3%8D%C3%9A%02%0FJ%C3%90o%1E%C3%95%02D%2B%C3%8FF%C3%BEJ%C2%83%C3%AC%C2%80z%C2%A3%C3%94%2F%C3%BF%C3%B4%C2%B1%12%0C%C3%B2%C3%AA%08%C2%92%C3%80%C3%B8%C3%A1c%1A%C2%AF2%C3%95y%C2%99%13%13%C2%B65%C3%ADd%C3%895%C2%AE%C3%B7g%C2%83%C3%8C&oauth_version=1.0&oauth_signature=j%25C3%25B4%25C3%25AA%2526%25C2%258F%25C3%2589%252B%25C3%258B%2514E%2504%255C%25C2%259A%2522d%25C2%2596%253D%251B%25C3%25A2%2502%25065%25C3%25B2n%25C3%2583%253Br%2526%25C2%2591%25C3%2594%25C3%2580N%25C3%258A%25C3%25B9%25C3%25B6rnyA%257F%25C3%2589ny%25C2%25A8%252B%25C3%25B0%25C3%2596A%25C2%25B7%25C2%2584%251E%251C%250A4%25C2%2591~%25C3%25B7%2501%25C3%25A6%2522%25C3%258E%25C2%25B3%2514%25C3%25B6%26%2540%2502%25C2%25A0%25C2%2592%25C2%25B9%25C3%25A9wx%25C3%25B8%25C3%258D%25C3%259A%2502%250FJ%25C3%2590o%251E%25C3%2595%2502D%252B%25C3%258FF%25C3%25BEJ%25C2%2583%25C3%25AC%25C2%2580z%25C2%25A3%25C3%2594%252F%25C3%25BF%25C3%25B4%25C2%25B1%2512%250C%25C3%25B2%25C3%25AA%2508%25C2%2592%25C3%2580%25C3%25B8%25C3%25A1c%251A%25C2%25AF2%25C3%2595y%25C2%2599%2513%2513%25C2%25B65%25C3%25ADd%25C3%25895%25C2%25AE%25C3%25B7g%25C2%2583%25C3%258C 400
1> [info] [<0.1060.0>] 127.0.0.1 - - 'GET' /_oauth/request_token?oauth_signature_method=HMAC-SHA1&oauth_consumer_key=key&oauth_token=foo&oauth_token_secret=%5C%60%C2%B2%C2%8D%C3%B6q%C3%BDU%C2%91%3E%C2%92%C3%A2%C2%B38%C2%B1%C3%95%C2%98%C3%A7H%7C%C3%91%25%00Q%12%0D%5D%27%5B%C2%9A%C2%98%1C%C2%A2%C2%BD%C2%83%C3%A8%C3%B7V%C2%A0%C3%90%02%C2%89%3Dv%C3%BCcu%C2%87%3A%04%3AsB%C2%81%2An%C2%8C%C3%B0%00%14%C2%BB%C2%9F-%3B&oauth_version=1.0&oauth_signature=tnupVHiU2LKNPAF1%2FN88YAiARdE%3D 200
1> [error] [<0.1060.0>] Uncaught error in HTTP request: {exit,normal}
1> [error] [<0.1303.0>] Uncaught error in HTTP request: {exit,normal}
1> [info] [<0.1319.0>] 127.0.0.1 - - 'PUT' /_config/httpd/WWW-Authenticate 401
and then the rest of the tests all fail , and any operations like deleting databases ask me to log into the area 'administrator'.
The text was updated successfully, but these errors were encountered: