| const asyncOk = async () => { | |
| return new Promise(re => setTimeout(re, 0)) | |
| } | |
| const asyncFail = async () => { | |
| return new Promise((_, re) => setTimeout(() => re(Error()), 0)) | |
| } | |
| const run1 = async () => { | |
| try { | |
| const [a, b] = [asyncFail(), asyncOk()] |
%GetOptimizationStatus return a set of bitwise flags instead of a single value,
to access the value, you need to take the binary representation of the returned value.
Now, for example, if 65 is returned, the binary representation is the following:
(65).toString(2).padStart(12, '0');
// 000001000001Each binary digit acts as a boolean with the following meaning:
A security talk is often a hacker showing off what they can do and how you should defend.
I'm not a hacker. At least I never considered myself one in my adult life.
My team at Egnyte is running an ever-growing number of small integrations to make big apps work together.
I happened to be in the middle of a maintenance run across 30 repositories when a bunch of new vulnerabilities in popular npm packages were published. What follows is a story of good security practices at scale: 30 failed pipelines, lots of teeth grinding and finally - automation.
from tag: diag-agenda
from tag: diag-agenda
from tag: diag-agenda
from tag: diag-agenda
diag-agenda
# WG Meeting 6/2017
*diag-agenda*
## Agenda
* Integrate C++ AsyncHooks Embedder API with native abstraction [node#13254](https://github.com/nodejs/node/issues/13254)