I was returning a promise in a (reject, resolve) -Function. :)
Hi, I seem to be getting a big performance regression when upgrading node from 6.11.3 to 8.5.0. The bottleneck seems to be around long stack traces, so not really critical in production. Did anyone else witness this problem? I'm using bluebird@3.5.0.
'use strict';
const bluebird = require('bluebird');
const repeat = 100000;
const array = [];
for (let i = 0; i < repeat; i++) {
array.push(0);
}
console.time('promiseSeries');
bluebird.mapSeries(array, () => {
return bluebird.resolve();
})
.then(() => {
console.timeEnd('promiseSeries');
});
Hi everyone,
In my application i am using bluebird and rxjs. I am trying to return bluebird promise as observable but i get a warning
(node:34520) Warning: a promise was created in a handler at Users/gaspergracner/Projects/node_modules/rxjs/observable/PromiseObservable.js:66:36 but was not returned from it, see http://goo.gl/rRqMUw
at Function.Promise.attempt.Promise.try (/Users/gaspergracner/Projects/node_modules/bluebird/js/release/method.js:29:9)
this is what causes a problem:
public getUserByUsername(username: string): Observable<any> {
let $obs = Observable.fromPromise(User.findOne({
where: {
username: username
}
}));
return $obs;
}Maybe you know how to avoid this warning?
I find it a bit more clearer to use that pattern, although the second one obviously works, too.
Using the second one will give you problems when you're using Bluebird in Typescript, because the return type doesn't match.
Given a
.then(params => {});, I want to add a property to params, where the value is a promise that processes another property of params as argument. I'm having a hard time wrapping my head around this. For example, assume params is passed in as { prop1: [{},{},{}] } initially. I want to return a promise that eventually resolves to { prop1: [{},{},{}], prop2: ["","",""] }, where prop2 was evaluated from a promise that depended on prop1. How could I do this?
i am getting a problem with an event emitter giving me this error
Unhandled rejection TimeoutError: operation timed out
at afterTimeout (/home/ubuntu/workspace/node_modules/bluebird/js/release/timers.js:46:19)
at Timeout.timeoutTimeout [as _onTimeout] (/home/ubuntu/workspace/node_modules/bluebird/js/release/timers.js:76:13)
at ontimeout (timers.js:386:14)
at tryOnTimeout (timers.js:250:5)
at Timer.listOnTimeout (timers.js:214:5)
i have strange work of Promise.all. I want to insert in base 10k notes, but fetch only 10. node 7.10.1 bluebird 3.5.1
let fetchbase = [];
for (var i = 0; i < res.length; ++i) {
fetchbase.push(insertDB('INSERT INTO city SET ?', res[i]));
};
return Promise.all(fetchbase);
let insertDB = (sql,arr) => {
return new Promise(function(resolve, reject) {
Db.getPool().then(function(connection){
connection.query(sql,arr,function(err,result) {
if (err) {
throw err;
console.log(err);
};
console.log(result.insertId);
resolve(result.insertId);
});
});
});
}
item: Promise { [] }
well, adding
.then(fp.mapValues(fp.toArray)) works...
@fratting Appears to be a variety of problems, one of which is the tryCatcher function executing a function called 'bound error'. the target var is the source of the illegal character. Another instance is the console.warn at like 1546 of the unminified bluebird.js file. console is considered an illegal character. Odd and only with firefox
Also, "Promise.config is not a function", and "Promise is not a constructor"
What is the license for the code snippets in the Bluebird's Wiki, more specifically the Optimization killers?
Thank you
Thank you
Basically was hoping Promise.map().then() would run after all the mapped promises, however the then is running immediately.
https://gist.github.com/bag-man/4b5db93b3c9c5e38876946d36c89331f#file-import-js-L32-L45
So I would hope for the indexes to be built after the save operations, but it's happening immediately.
Beautiful, that was it, thank you so much! The pain that has saved me :D
here's my "not" working example:
resultSet.map( item => {
Promise.coroutine( function* (user) {
let opt = {
TableName: 'tableName',
KeyConditions: {
username: {
AttributeValueList: [user],
ComparisonOperator: 'EQ'
}
},
ProjectionExpression: 'firstname, lastname',
}
let userFriends = yield dynamodb.queryAsync(opt)
/* random code here to assign first name and last name to item */
})(item);
return item
});
@danyextreame_twitter Are you sure? I don't see any notice in the docs and seems to work fine with a quick test in https://npm.runkit.com/bluebird
