Qualio’s Post

If you want to learn about 𝐥𝐨𝐚𝐝 𝐛𝐚𝐥𝐚𝐧𝐜𝐢𝐧𝐠 𝐚𝐥𝐠𝐨𝐫𝐢𝐭𝐡𝐦𝐬 𝐚𝐧𝐝 𝐡𝐨𝐰 𝐭𝐨 𝐢𝐦𝐩𝐥𝐞𝐦𝐞𝐧𝐭 𝐭𝐡𝐞𝐦 𝐢𝐧 𝐜𝐨𝐝𝐞, checkout my new article: https://lnkd.in/gQE4KE8W Subscribe for more such articles every week: https://lnkd.in/gmePGK_J

Check out this Elastic blog on how we made internal improvements in version 8.13, bringing big memory savings to Elastic Agent and Beats: https://lnkd.in/gtjddkkZ

Check out this Elastic blog on how we made internal improvements in version 8.13, bringing big memory savings to Elastic Agent and Beats: https://lnkd.in/e797yzxK

Check out this Elastic blog on how we made internal improvements in version 8.13, bringing big memory savings to Elastic Agent and Beats: https://lnkd.in/gWUn-TuK

Check out this Elastic blog on how we made internal improvements in version 8.13, bringing big memory savings to Elastic Agent and Beats: https://lnkd.in/gM3JUJYS

Check out this Elastic blog on how we made internal improvements in version 8.13, bringing big memory savings to Elastic Agent and Beats: https://lnkd.in/gCjmVhXY

Guess the output !!!! //------------------------------------------------ new Promise(function(resolve, reject) { setTimeout(() => { throw new Error("Whoops!"); }, 1000); }).catch(alert); //------------------------------------------------- ANSWER: Uncaught Error: Whoops! -> My Interpretation of what happened which led to this output In the above task, the promise will never get settled and hence the handler function (then/catch/finally) will not get transferred to the microtask queue, meanwhile, the timer ends and the code inside of it goes to the callback queue (callback queue and microtask queue make the entire queue, microtask having more priority). soon, the execution of the main thread finishes and the item in the callback is picked and executed. since this contains an explicitly thrown error, the engine just logs this out in the browser console. also, the code inside setTimeout does not reject the promise hence the entire promise is still pending due to which the catch handler is not getting a slot in the microtask queue. Hence, the catch is not triggered. let me know what do you think.

Just in! 🔔 We've launched new Kinsta API endpoints that give you access to in-depth application analytics. Now, you can programmatically retrieve data on bandwidth, build time, runtime, CPU usage, and so many more! 😎 Dive deeper here ↓ https://ow.ly/Xxl850RvcOW

Finding the root cause of data issues, and performing proper data validation, are key tasks for data engineers. Especially when you need to create a comprehensive pull request for others to review your work. It’s why we’re focusing so much on making that process seamless and enabling you to follow the logical steps towards validating your work and re-use those checks in PR validation. Our aim is to allow you to start from holistic checks, and narrow the scope of focus right down to the row level, if necessary. Check out the Top-K and Value Diff features in Recce to see what I mean: https://lnkd.in/gDxrjDSU

Here's something that stands out: Going fast slowly (https://lnkd.in/gMCBpE5T)