node.js - Async await not working in forEach -


i have following code:

async function goodusers(users) {   const filteredusers = [];    users.foreach(async (userinstance) => {     console.log('test1');      const fromusercontacts = await db.usercontactinvite.findall({       where: {         fromuserid: userinstance.id,       },     });     console.log('test2');     await fromusercontacts.foreach((fromusercontact) => {       console.log('test3');       const userjson = fromusercontact.tojson();       userjson.contactstate = 'invitation_sent';       filteredusers.push(userjson);     });      console.log('test4');   });    console.log('filtered', filteredusers);   return filteredusers; }

when call goodusers following output: test1 filtered test2 test3 test4

filtered should last (obviously).

i tried various options seem not understanding here. guys notice what's going on?

this's correct behavior, async/await affect function used. need replace foreach calls callback each element, for operator:

async function goodusers(users) {    const filteredusers = [];      for(user in users) {      console.log('test1');      const fromusercontacts = await new promise(resolve => settimeout(() => resolve(['c1', 'c2']), 500));        console.log('test2');      fromusercontacts.foreach(fromusercontact => {        console.log('test3');        filteredusers.push('json');      });        console.log('test4');    }      console.log('filtered', filteredusers);    return filteredusers;  }    goodusers(['u1', 'u2']);


Comments

Post a Comment

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

i'm using class based views in django , never specify url in ajax calls , omit action parameter in form because know these requests go through post method of class based view. notice view - profile page make many requests depending on user updating on page - post method become convoluted , if/else mess example: def post(self, request, *args, **kwargs): # handle user changing available date if request.post.get('availabledate') != none: self.updateavailabledate(request) return jsonresponse({'result':'success'}) if request.post.get('newprojectname') != none: creative_user = creativeuserprofile.objects.get(id = request.user.id) project = project.create_project(creative_user, request.post['newprojectname']) project.save() return jsonresponse({'projectid': project.id }) if request.post.get('projectimage') != none , request.files['file']: proj
Read more

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

i'm doing micro-optimization on performance critical part of code , came across sequence of instructions (in at&t syntax): add %rax, %rbx mov %rdx, %rax mov %rbx, %rdx i thought had use case xchg allow me shave instruction , write: add %rbx, %rax xchg %rax, %rdx however, dimay found agner fog's instruction tables , xchg 3 micro-op instruction 2 cycle latency on sandy bridge, ivy bridge, broadwell, haswell , skylake. 3 whole micro-ops , 2 cycles of latency! 3 micro-ops throws off 4-1-1-1 cadence , 2 cycle latency makes worse original in best case since last 2 instructions in original might execute in parallel. now... cpu might breaking instruction micro-ops equivalent to: mov %rax, %tmp mov %rdx, %rax mov %tmp, %rdx where tmp anonymous internal register , suppose last 2 micro-ops run in parallel latency 2 cycles. given register renaming occurs on these micro-architectures, though, doesn't make sense me done way. why wouldn't register renamer
Read more

jquery - Responsive Navbar with Sub Navbar -

good day, forgive me nav vocabulary not best. if question confusing apologize. i'm working on navigation bar needs centered on page @ 768px , above. items in nav open (or perhaps toggle) subnav lives directly below. these nav should appear centered on page. i have been able work through responsive portion of nav bar, having main items align vertically , sub nav menu of each item roll out below, , gave them indent separation. working well. however, issue not responsive side, behavior @ width greater 768px. happens toggling menu's sub navigation pushes other main items down page below sub nav. here's code: $(document).ready(function () { //stick in fixed 100% height behind navbar don't wrap $('#slide-nav.navbar-inverse').after($('<div class="inverse" id="navbar-height-col"></div>')); $('#slide-nav.navbar-default').after($('<div id="navbar-height-col"></d
Read more