Skip to content
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.

Is connection_timeout respected somehow in server.post_replicate? #144

Open
greenais opened this issue Apr 4, 2018 · 0 comments
Open

Is connection_timeout respected somehow in server.post_replicate? #144

greenais opened this issue Apr 4, 2018 · 0 comments
Labels

Comments

@greenais
Copy link

greenais commented Apr 4, 2018

Hi,
first of all let me thank team for upgrading lib to the most recent CBL version 1.4, improving linking (BTW, manifests still should be added manually) and sorting out some mess in docs and .help().
Really great job, guys.

The question:
is there way to make RNCBL respect connection_timeout prop in server.post_replicate body for one-time (not continuous/poll) replication?
I tried to set different values with no effect: RNCBL always timeouts replication call after ~70 sec (returning err in my .catch() routine), which in my case is a way too long.

My request code is:

cbl.server.post_replicate({body: {
      source: syncURL,
      target: localDB,
      connection_timeout: 5000,
      filter: 'sync_gateway/bychannel',
      query_params: {channels: channelsList},
      cancel: false,
      attachments: false,
      continuous: false
    }})
.catch((err)=> {
      console.log(' !!!!!!!!!!!!!!! syncChannels ERR: ', err.status)
})

Any ideas, perhaps?

@djpongh djpongh added the icebox label Jan 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants