| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
COUCHDB-2874
|
|
|
|
| |
Signed-off-by: Alexander Shorin <kxepal@apache.org>
|
| |
|
| |
|
|
|
|
| |
COUCHDB-708
|
| |
|
|
|
|
|
|
|
|
|
| |
Fixes the opacity on the favicon so it doesnt look awkward on non
white browser chrome
Original patch by Benjamin Anderson
Closes COUCHDB-1133
|
| |
|
|
|
|
| |
closes COUCHDB-2026
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
The value of source_seq is just what's been seen, not what's actually
been stored on the target. We expose through_seq now to show the actual
progress.
|
| |
| |
| |
| |
| | |
Further speedups to replication.js. Now runs in 32s on my machine vs.
the 1m45s it started at.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Attempting to compare the source and target update_seq values isn't
valid as any document modification on the source will permanently alter
the comparison. This changes things to just wait for the task's status
to update and reflect the source database's update sequence.
Locally this shortens the replication.js test by about 45s.
|
| |
| |
| |
| |
| |
| |
| | |
There was a race condition where we could end up grabbing repDoc1 before
the replicator manager got around to updating it. Local timespans had
this in the 19ms range. Rather than slap a timeout on it I've added a
call to a longpoll on the changes feed to wait for the update.
|
| |
| |
| |
| |
| |
| | |
Tweak hard coded assumptions about update_seq ordering for documents
posted to _bulk_updates. See the comment in replication.js for more
information.
|
| |
| |
| |
| |
| |
| |
| | |
The change to lager changed how w configure logging in CouchDB. We'll
need to figure out if we want to update things so that we can configure
lager from the INI files at which point we can either reenable this test
or remove it.
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The EventSource connection can get stuck (in TCP half-open state*) and there's no way
for the client to detect that. This commit changes the way heartbeat is sent, instead of
sending a newline character, it sends an empty event of type heartbeat:
event: heartbeat
data:
This event doesn't have an id: field, so the client will retain its latest Last-Event-ID state.
This doesn't change the expectations of clients that used EventSource till now, because they
subscribe to the 'message' event type. To get the 'heartbeat' events a client will need to
explicitly subscribe to it:
source.addEventListener('heartbeat', function () { /* cancel a timer that would otherwise reconnect the source */ });
* this can happen when you suspend your laptop, on flaky internet connection, ADSL reconnect,
bad wifi signals, bad routers etc. Pretty often in a typical internet usage nowadays.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes client-side password crypto from the JavaScript tests.
In some JavaScript tests, it has been assumed that SHA-1 is used for the
password hash in user docs. Those tests should, however, not rely on
implementation details of the user authentication hash function, as it
isn't the goal of those tests to check these. Furthermore, this causes
problems when a password scheme is changed, or a new one is introduced.
|
| |
| |
| |
| |
| |
| |
| |
| | |
We now upgrade user docs to the new PBKDF2 password scheme on successful
authentication if the password hash is still from the old days where we
only used plain SHA-1 for hashing salted passwords.
Closes COUCHDB-1780.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This test was incorrectly relying on a bug in the reduce behavior that
would return a reduce value without ever re-reducing it. The fix is to
just correct the test reduce function to behave properly.
COUCHDB-2001
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This uses an instance wide token set in the application environment to
detect when the server has restarted.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
https://github.com/davisp/couchdb/commit/35bc88b69486a96409d9f9709209a5dacffc9174
The fact that the old test worked was a fluke. If we want to validate
all doc updates (even these that are no-ops) we should think harder
about our validation scheme.
|
| |
| |
| |
| |
| | |
For the test suite this should minimize the "file exists" errors that we
see. Theoretically maybe.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Theoretically this should prevent all of those annoying test suite
failures when a test fails in with a temporary config set and fails to
undo its changes.
This works by storing the list of INI files in the config server and on
command will clear its ets table and re-read data from disk thus
clearing its cache of non-persisted values. Obviously this isn't
something that should be relied on in production settings.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
couchjs/js/SConscript
share/server/json2.js
share/server/render.js
share/server/util.js
|
| |
| |
| |
| | |
and better looping.
|
| |
| |
| |
| |
| | |
We should provide access to the full sequence in Futon somehow, as
it's useful for things like changes since "now".
|
| | |
|
| |
| |
| |
| |
| | |
fixed a formatting typo as reported by
Blake Gideon
|
| |
| |
| |
| |
| |
| | |
This closes #250
Signed-off-by: Alexander Shorin <kxepal@apache.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Like every web application, Fauxton is vulnerable against XSS and
CSP is a technology that tries to help against that.
The patch makes it possible to enable CSP for the /_utils path and
allows configuration of the sent header.
The default setting for the value of the header breaks the old
Futon, when CSP is enabled there. The old Futon has alot of
inline-JavaScript which is not allowed in the setting I have
chosen as default.
For development, the header is also sent from the Node server
which launches Fauxton in dev-mode.
People can enable the feature by setting enable = true in the
section [csp] of their configs
|