markmssd / bitbucket-server-nodejs Goto Github PK

The implementation of client.repos.getAll is not idempotent, and compounds responses from the second call onwards.
It seems to keep a global state of all repos read (for recursion purposes), requiring the creation of a new client to nullify state.

The culprit is at https://github.com/markmssd/bitbucket-server-nodejs/blob/master/lib/api/repos.js#L10

The following code demonstrates the issue:

const client = new Client(url, auth);

client.repos.getAll().then(repos => console.log(repos.length)); // prints N
client.repos.getAll().then(repos => console.log(repos.length)); // prints 2N

Can you please comment on this finding? I can submit a quick PR that will add an optional repos array as a second arg of getAll, allowing the recursion to carry its state internally.

Hello, I'm building a simple NodeJS based CLI with some bitbucket features.

I'm trying to connect using basic auth but I'm struggling with the apis url:

var auth = {
"type": "basic",
"username": "username",
"password": "password"
}

var client = await new bitbucket('https://api.bitbucket.orgs/2.0', auth)

client.settings.get('omarfouad')

I'm getting a 'Resource not found' error.
Ideas?