SDK JS Samples (30. stateMachineDialog) doesn't start

Here is the error when running npm start
const dialogs = new botbuilder_dialogs_adaptive_1.StateMachineDialog('main', 'offHook');
^
TypeError: botbuilder_dialogs_adaptive_1.StateMachineDialog is not a constructor
at Object. (/Users/sshehata/workspace/botbuilder-js-4.future/samples/30. stateMachineDialog/lib/index.js:33:17)
at Module._compile (internal/modules/cjs/loader.js:738:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:749:10)
at Module.load (internal/modules/cjs/loader.js:630:32)
at tryModuleLoad (internal/modules/cjs/loader.js:570:12)
at Function.Module._load (internal/modules/cjs/loader.js:562:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:801:12)
at internal/main/run_main_module.js:21:11
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node ./lib/index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/sshehata/.npm/_logs/2019-11-05T21_10_21_299Z-debug.log

@sshehata-zz Can you link me to that sample? As far as I can tell, it no longer exists. I know it was experimental to begin with and if it's been removed, we don't really provide support for it.
That being said, I'm happy to help--I just can't debug or repro it without any code to work off of.

@sshehata-zz  Never mind. I found it and will attempt to fix this. Again, though, those samples are definitely not ready for public use yet.

@mdrichardson - Thanks for your response. Here is the link:
https://github.com/microsoft/botbuilder-js/tree/4.future

@sshehata-zz How are you installing the packages? I'm not seeing botbuilder-dialogs-adaptive in any of our MyGet packages. Maybe I'm looking at the wrong ones. It's been awhile since I tried any of these samples..

@mdrichardson - First you will need to install the packages (npm install) then will need to build them (npm run build)

@sshehata-zz Figured. Doing that now. Guess I'm just surprised you're using a sample that is so clearly not ready for public consumption.

@mdrichardson - Thanks for your help. I understand your point. I'm looking for adaptive dialogs in Nodejs and it seems that this is the only repo I found with 4.6.* preview with samples. Happy to learn if there are other repos for Adaptive Dialogs in Nodejs that I'm missing. Is there an ETA for 4.6.* release (with adaptive dialogs) on Nodejs?

@sshehata-zz No problem. Adaptive Dialogs are pretty exciting, they're just VERY much in Preview, especially on the Node.js side, which is very far behind the C# side (with adaptive dialogs, only).

...and unfortunately, these do seem to be the only samples at the moment.

@sshehata-zz I can't seem to get this sample to build without throwing 70+ errors. I believe this is because this sample hasn't been substantially updated since April, but the adaptive libraries are updated constantly.
If you really would like to play with this sample, I can probably get it working. However, based on how long ago since it's been updated, I don't believe it's much of a priority for the dev team to fix. Also, no ETA on when Node Adaptive will be ready.
Personally, I recommend playing with the C# samples, if anything--if you know TypeScript, C# is fairly easy to pick up.
Let me know if you'd like help getting this sample running or will switch to the C# ones.

@mdrichardson - thanks for the suggestions! Actually, it is a bigger decision to change the language as it is tied to other components in the system and we need to use Nodejs and hopefully we can still use Microsoft bot framework given that we are Microsoft partner. So, I would like help getting this sample running. Based on the error I'm getting, it seems that StateMachineDialog is missing from botbuilder-dialogs-adaptive and this seems to be the main reason. Appreciate your help!

@sshehata-zz There's two ways we can try getting this to work:

Use the JS repo from an April commit. I'm currently trying this. This is probably the easier route (although I'm struggling with it), but a big downside is that it will be woefully out of date with current Adaptive changes

Get the sample to work with the current JS repo. This is likely a lot of work. I have a feeling that StateMachineDialog was removed because State Machines are sooo different from the rest of the SDK. How set are you on using this particular sample? It might be easier to get one of the others working.

@sshehata-zz Well, now I feel dumb. To get that sample working with the April repo:
git clone https://github.com/microsoft/botbuilder-js.git
cd botbuilder-js
git checkout 4.future
git reset --hard db56b4cac07dae20be7e6922e34a68d2ba07e31c
npm i
npm run build
cd "samples/30. stateMachineDialog"
npm start

I didn't realize npm i from the repo's root also does npm i within the sample. Still, this is out of date with current Adaptive changes.
Does this accomplish what you're looking for, or are you wanting something else?

If you want a sample closer to where Adaptive Dialogs are at today, To Do Bot is the most recent, although still not updated since June.

@mdrichardson - This is what I did as stated earlier. However, when I start it, I receive the following error of this created issue.
const dialogs = new botbuilder_dialogs_adaptive_1.StateMachineDialog('main', 'offHook');
^
TypeError: botbuilder_dialogs_adaptive_1.StateMachineDialog is not a constructor .......

@sshehata-zz Did you do this part:
git reset --hard db56b4cac07dae20be7e6922e34a68d2ba07e31c

@mdrichardson - By following the provided steps, I receive many errors on the npm i
Shadys-MacBook:botbuilder-js sshehata$ npm i

botbuilder-packages@ postinstall /Users/sshehata/workspace/botbuilder-js
lerna bootstrap --hoist

lerna notice cli v3.13.1
lerna info versioning independent
lerna info Bootstrapping 25 packages
lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "transcript-tests" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-connector" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna info Installing external dependencies
lerna info hoist Installing hoisted dependencies into root
lerna info hoist Pruning hoisted dependencies
lerna info hoist Finished pruning hoisted dependencies
lerna ERR! npm install exited 1 in 'botbuilder-packages'
lerna ERR! npm install stderr:
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-0aJ5UIjs6dKZYdovnlnoIb7+wBId3cubQzwC0tH6S//JhayqrKqMcD8vPPgwZHhBhBx8ZFNmKD3MJtCvZZ1GYA==) seems to be corrupted. Trying one more time.
npm ERR! code EINTEGRITY
npm ERR! sha512-58664aLhN1WQwAxMBK7LZQhFh8DHwenvpgz6ADFgeZLZS28NACfX+Uta8k2+WF6RK3g+VKoGOhV/yI71c5ccVg== integrity checksum failed when using sha512: wanted sha512-58664aLhN1WQwAxMBK7LZQhFh8DHwenvpgz6ADFgeZLZS28NACfX+Uta8k2+WF6RK3g+VKoGOhV/yI71c5ccVg== but got sha512-dNWR3SVQ8FxK8JEqj7l1nxbGT7zzWXpyKpPttiSZb4vBpGhxlTHEx1+UsDzRhlYX9GPxw5D6vnKgTZXns1s4ZQ==. (34771 bytes)
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-gej7KR0iFIK38M4eIkGFOn+Tk7sMpzGTJgMVy/ctz21m6vQDGfqFLjJzDk4GRG9oLaZfq5bqUw5sLtepLAZcUg==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-QHD9WigzC7rOJT0hb9Xzs/yHs1g/MOabJey8qxlZPdnnQqK5X8KJaZEEDnRqcUmLj/ydbxnxqImLEsMD5zlGag==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-U8n+eY9Cjce0GkMyyE0mv4HBjCjtyuczz6usl9XF2N7nY61jYDah4W5e4zqYdLdlqnBwfxG8ptS9pdnmVsC2ww==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-O2RmSG4AFyNc7h9zD2a7kdIBw8jF3Thpl8Pwfs/BpKGhRrCIJAMasV0+UbIV2Iwi2NEl7WzdpXjUsnpmB57XgQ==) seems to be corrupted. Trying one more time.
npm ERR! code EINTEGRITY
npm ERR! sha512-0aJ5UIjs6dKZYdovnlnoIb7+wBId3cubQzwC0tH6S//JhayqrKqMcD8vPPgwZHhBhBx8ZFNmKD3MJtCvZZ1GYA== integrity checksum failed when using sha512: wanted sha512-0aJ5UIjs6dKZYdovnlnoIb7+wBId3cubQzwC0tH6S//JhayqrKqMcD8vPPgwZHhBhBx8ZFNmKD3MJtCvZZ1GYA== but got sha512-AtRZO9K8khguxEw50yg3aDireNJbqlefpjkWCILxMplaCAIMSgUptEhcsbAL5LARYA8cAMKxmxwlCJ6zL8hz9w==. (24237 bytes)
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-gej7KR0iFIK38M4eIkGFOn+Tk7sMpzGTJgMVy/ctz21m6vQDGfqFLjJzDk4GRG9oLaZfq5bqUw5sLtepLAZcUg==) seems to be corrupted. Trying one more time.
npm WARN tar ENOENT: no such file or directory, open<EMAIL_ADDRESS>npm WARN tar ENOENT: no such file or directory, open<EMAIL_ADDRESS>npm WARN tar ENOENT: no such file or directory, open<EMAIL_ADDRESS>npm WARN tar ENOENT: no such file or directory, open<EMAIL_ADDRESS>npm WARN tar ENOENT: no such file or directory, open<EMAIL_ADDRESS>npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/workspace/botbuilder-js/node_modules/.staging/JSONSelect-81cc9138/src/test/js/jquery-1.6.1.min.js'
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-O2RmSG4AFyNc7h9zD2a7kdIBw8jF3Thpl8Pwfs/BpKGhRrCIJAMasV0+UbIV2Iwi2NEl7WzdpXjUsnpmB57XgQ==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-U8n+eY9Cjce0GkMyyE0mv4HBjCjtyuczz6usl9XF2N7nY61jYDah4W5e4zqYdLdlqnBwfxG8ptS9pdnmVsC2ww==) seems to be corrupted. Trying one more time.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Users/sshehata/workspace/botbuilder-js/node_modules/.staging/fsevents-5c495eb7/node_modules/abbrev' -> '/Users/sshehata/workspace/botbuilder-js/node_modules/.staging/abbrev-7be2c184'
npm ERR! code EINTEGRITY
npm ERR! Verification failed while extracting<EMAIL_ADDRESS>npm ERR! Verification failed while extracting<EMAIL_ADDRESS>npm ERR! sha512-gej7KR0iFIK38M4eIkGFOn+Tk7sMpzGTJgMVy/ctz21m6vQDGfqFLjJzDk4GRG9oLaZfq5bqUw5sLtepLAZcUg== integrity checksum failed when using sha512: wanted sha512-gej7KR0iFIK38M4eIkGFOn+Tk7sMpzGTJgMVy/ctz21m6vQDGfqFLjJzDk4GRG9oLaZfq5bqUw5sLtepLAZcUg== but got sha512-RDovFqtZFy9TGqcsX49SP8rjxSArsvmcWJA4ECTrg8haBTBq1wiiR6cFxKYfI8qonJo6y0+zzvU2LXuZNBI77w==. (40829 bytes)
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/workspace/botbuilder-js/node_modules/.staging/ms-rest-js-d922cbd2/dist/msRest.browser.min.js'
npm ERR!      /Users/sshehata/.npm/_logs/2019-11-06T21_15_31_561Z-debug.log
lerna ERR! npm install exited 1 in 'botbuilder-packages'
lerna WARN complete Waiting for 1 child process to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! botbuilder-packages@ postinstall: lerna bootstrap --hoist
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the botbuilder-packages@ postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/sshehata/.npm/_logs/2019-11-06T21_15_36_420Z-debug.log

@sshehata-zz Did you execute all of those commands, including a fresh git clone? I just did and it worked:

v-micric@MININT-9QM2D7A MINGW64 ~/Documents/Code/Bots - Testing/stateMachine/New folder                                                                                $ git clone https://github.com/microsoft/botbuilder-js.git                                                                                Cloning into 'botbuilder-js'...                                                                                remote: Enumerating objects: 277, done.                                                                                remote: Counting objects: 100% (277/277), done.                                                                                remote: Compressing objects: 100% (210/210), done.                                                                                remote: Total 42230 (delta 104), reused 126 (delta 61), pack-reused 41953                                                                                Receiving objects: 100% (42230/42230), 25.55 MiB \| 11.55 MiB/s, done.                                                                                Resolving deltas: 100% (30363/30363), done.                                                                                v-micric@MININT-9QM2D7A MINGW64 ~/Documents/Code/Bots - Testing/stateMachine/New folder                                                                                $ cd botbuilder-js                                                                                v-micric@MININT-9QM2D7A MINGW64 ~/Documents/Code/Bots - Testing/stateMachine/New folder/botbuilder-js (master)                                                            $ git checkout 4.future                                                                                Switched to a new branch '4.future'                                                                                Branch '4.future' set up to track remote branch '4.future' from 'origin'.                                                                                v-micric@MININT-9QM2D7A MINGW64 ~/Documents/Code/Bots - Testing/stateMachine/New folder/botbuilder-js (4.future)                                                          $ git reset --hard db56b4cac07dae20be7e6922e34a68d2ba07e31c                                                                                HEAD is now at db56b4ca LG: Fix more bugs                                                                                v-micric@MININT-9QM2D7A MINGW64 ~/Documents/Code/Bots - Testing/stateMachine/New folder/botbuilder-js (4.future)                                                          $ npm i                                                                                > botbuilder-packages@ postinstall C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js                                                  > lerna bootstrap --hoist                                                                                lerna notice cli v3.13.1                                                                                lerna info versioning independent                                                                                lerna info Bootstrapping 25 packages                                                                                lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>                                          lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                                   lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                            lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                                           lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>       lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>        lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted tslint-microsoft-contrib@ ^5.2.1.                                                                                lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>        lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>                                   lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                                    lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                       lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                               lerna WARN EHOIST_PKG_VERSION "transcript-tests" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                                             lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                                        lerna WARN EHOIST_PKG_VERSION "botframework-connector" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>                           lerna info Installing external dependencies                                                                                lerna info hoist Installing hoisted dependencies into root                                                                                lerna info hoist Pruning hoisted dependencies                                                                                lerna info hoist Finished pruning hoisted dependencies                                                                                lerna info hoist Finished bootstrapping root                                                                                lerna info Symlinking packages and binaries                                                                                lerna success Bootstrapped 25 packages                                                                                added 813 packages from 1580 contributors and audited 42222 packages in 97.577s                                                                                found 383 vulnerabilities (1 low, 8 moderate, 370 high, 4 critical)                                                                                run `npm audit fix` to fix them, or `npm audit` for details                                                                                v-micric@MININT-9QM2D7A MINGW64 ~/Documents/Code/Bots - Testing/stateMachine/New folder/botbuilder-js (4.future)                                                          $ npm run build                                                                                > botbuilder-packages@ build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js                                                        > lerna run build                                                                                lerna notice cli v3.13.1                                                                                lerna info versioning independent                                                                                lerna info Executing command in 15 packages: "npm run build"                                                                                lerna info run Ran npm script 'build' in 'botframework-schema' in 5.3s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botframework-schema                     > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-expression' in 5.8s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-expression                 > tsc                                                                                lerna info run Ran npm script 'build' in 'botframework-config' in 6.3s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botframework-config                     > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-expression-parser' in 6.4s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-expression-parser   > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-core' in 6.9s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-core                             > tsc                                                                                lerna info run Ran npm script 'build' in 'botframework-connector' in 7.1s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botframework-connector               > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-applicationinsights' in 7.5s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-applicationinsigh ts                                                                                > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder' in 8.1s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder                                       > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-ai' in 8.1s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-ai                                 > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-lg' in 9.7s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-lg                                 > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-dialogs' in 10.2s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-dialogs                       > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-dialogs-declarative' in 4.9s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-dialogs-declarati ve                                                                                > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-azure' in 6.6s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-azure                           > tsc                                                                                lerna info run Ran npm script 'build' in 'botbuilder-dialogs-adaptive' in 8.4s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\libraries\botbuilder-dialogs-adaptive     > tsc                                                                                lerna info run Ran npm script 'build' in 'sidecar-debugging-sample' in 4.5s:                                                                                ><EMAIL_ADDRESS>build C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\samples\10. sidecarDebugging                 > tsc                                                                                lerna success run Ran npm script 'build' in 15 packages in 36.8s:                                                                                lerna success - botbuilder                                                                                lerna success - botbuilder-ai                                                                                lerna success - botbuilder-applicationinsights                                                                                lerna success - botbuilder-azure                                                                                lerna success - botbuilder-core                                                                                lerna success - botbuilder-dialogs                                                                                lerna success - botbuilder-dialogs-adaptive                                                                                lerna success - botbuilder-dialogs-declarative                                                                                lerna success - botbuilder-expression                                                                                lerna success - botbuilder-expression-parser                                                                                lerna success - botbuilder-lg                                                                                lerna success - botframework-config                                                                                lerna success - botframework-connector                                                                                lerna success - botframework-schema                                                                                lerna success - sidecar-debugging-sample                                                                                v-micric@MININT-9QM2D7A MINGW64 ~/Documents/Code/Bots - Testing/stateMachine/New folder/botbuilder-js (4.future)                                                          $ cd "samples/30. stateMachineDialog"                                                                                v-micric@MININT-9QM2D7A MINGW64 ~/Documents/Code/Bots - Testing/stateMachine/New folder/botbuilder-js/samples/30. stateMachineDialog (4.future)                           $ npm start                                                                                ><EMAIL_ADDRESS>start C:\Users\v-micric\Documents\Code\Bots - Testing\stateMachine\New folder\botbuilder-js\samples\30. stateMachineDialog              > node ./lib/index.js                                                                                line 1:0 token recognition error at: '$'                                                                                line 1:0 token recognition error at: '$'                                                                                restify listening to http://[::]:3978                                                                                Get Bot Framework Emulator: https://aka.ms/botframework-emulator                                                                                To talk to your bot, open echobot.bot file in the Emulator.
--

@mdrichardson - I followed the same steps and I received the errors mentioned before. What is your NodeJs version?

That might be it. I'm on v11.15.0

Same issues.
Shadys-MacBook:~ sshehata$ node --version
v11.15.0
Shadys-MacBook:~ sshehata$ mkdir future
Shadys-MacBook:~ sshehata$ cd future
Shadys-MacBook:future sshehata$ git clone https://github.com/microsoft/botbuilder-js.git
Cloning into 'botbuilder-js'...
remote: Enumerating objects: 285, done.
remote: Counting objects: 100% (285/285), done.
remote: Compressing objects: 100% (218/218), done.
remote: Total 42239 (delta 110), reused 126 (delta 61), pack-reused 41954
Receiving objects: 100% (42239/42239), 25.55 MiB | 4.75 MiB/s, done.
Resolving deltas: 100% (30369/30369), done.
Shadys-MacBook:future sshehata$ cd botbuilder-js
Shadys-MacBook:botbuilder-js sshehata$ git checkout 4.future
Branch '4.future' set up to track remote branch '4.future' from 'origin'.
Switched to a new branch '4.future'
Shadys-MacBook:botbuilder-js sshehata$ git reset --hard db56b4cac07dae20be7e6922e34a68d2ba07e31c
HEAD is now at db56b4ca LG: Fix more bugs
Shadys-MacBook:botbuilder-js sshehata$ npm i

botbuilder-packages@ postinstall /Users/sshehata/future/botbuilder-js
lerna bootstrap --hoist

lerna notice cli v3.13.1
lerna info versioning independent
lerna info Bootstrapping 25 packages
lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "transcript-tests" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-connector" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna info Installing external dependencies
lerna info hoist Installing hoisted dependencies into root
lerna info hoist Pruning hoisted dependencies
lerna info hoist Finished pruning hoisted dependencies
lerna ERR! npm install exited 1 in 'botbuilder-packages'
lerna ERR! npm install stderr:
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-0aJ5UIjs6dKZYdovnlnoIb7+wBId3cubQzwC0tH6S//JhayqrKqMcD8vPPgwZHhBhBx8ZFNmKD3MJtCvZZ1GYA==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-gej7KR0iFIK38M4eIkGFOn+Tk7sMpzGTJgMVy/ctz21m6vQDGfqFLjJzDk4GRG9oLaZfq5bqUw5sLtepLAZcUg==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-U8n+eY9Cjce0GkMyyE0mv4HBjCjtyuczz6usl9XF2N7nY61jYDah4W5e4zqYdLdlqnBwfxG8ptS9pdnmVsC2ww==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-O2RmSG4AFyNc7h9zD2a7kdIBw8jF3Thpl8Pwfs/BpKGhRrCIJAMasV0+UbIV2Iwi2NEl7WzdpXjUsnpmB57XgQ==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-58664aLhN1WQwAxMBK7LZQhFh8DHwenvpgz6ADFgeZLZS28NACfX+Uta8k2+WF6RK3g+VKoGOhV/yI71c5ccVg==) seems to be corrupted. Trying one more time.
npm ERR! code EINTEGRITY
npm ERR! sha512-0aJ5UIjs6dKZYdovnlnoIb7+wBId3cubQzwC0tH6S//JhayqrKqMcD8vPPgwZHhBhBx8ZFNmKD3MJtCvZZ1GYA== integrity checksum failed when using sha512: wanted sha512-0aJ5UIjs6dKZYdovnlnoIb7+wBId3cubQzwC0tH6S//JhayqrKqMcD8vPPgwZHhBhBx8ZFNmKD3MJtCvZZ1GYA== but got sha512-AtRZO9K8khguxEw50yg3aDireNJbqlefpjkWCILxMplaCAIMSgUptEhcsbAL5LARYA8cAMKxmxwlCJ6zL8hz9w==. (24237 bytes)
npm ERR! code EINTEGRITY
npm ERR! sha512-gej7KR0iFIK38M4eIkGFOn+Tk7sMpzGTJgMVy/ctz21m6vQDGfqFLjJzDk4GRG9oLaZfq5bqUw5sLtepLAZcUg== integrity checksum failed when using sha512: wanted sha512-gej7KR0iFIK38M4eIkGFOn+Tk7sMpzGTJgMVy/ctz21m6vQDGfqFLjJzDk4GRG9oLaZfq5bqUw5sLtepLAZcUg== but got sha512-RDovFqtZFy9TGqcsX49SP8rjxSArsvmcWJA4ECTrg8haBTBq1wiiR6cFxKYfI8qonJo6y0+zzvU2LXuZNBI77w==. (40829 bytes)
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-QHD9WigzC7rOJT0hb9Xzs/yHs1g/MOabJey8qxlZPdnnQqK5X8KJaZEEDnRqcUmLj/ydbxnxqImLEsMD5zlGag==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-58664aLhN1WQwAxMBK7LZQhFh8DHwenvpgz6ADFgeZLZS28NACfX+Uta8k2+WF6RK3g+VKoGOhV/yI71c5ccVg==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-O2RmSG4AFyNc7h9zD2a7kdIBw8jF3Thpl8Pwfs/BpKGhRrCIJAMasV0+UbIV2Iwi2NEl7WzdpXjUsnpmB57XgQ==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-U8n+eY9Cjce0GkMyyE0mv4HBjCjtyuczz6usl9XF2N7nY61jYDah4W5e4zqYdLdlqnBwfxG8ptS9pdnmVsC2ww==) seems to be corrupted. Trying one more time.
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/botbuilder-core-1db2efef/src/turnContext.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/botbuilder-core-1db2efef/src/userState.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/credentials/apiKeyCredentials.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/credentials/basicAuthenticationCredentials.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/credentials/credentials.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/credentials/serviceClientCredentials.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/credentials/tokenCredentials.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/credentials/topicCredentials.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/deserializationPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/exponentialRetryPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/generateClientRequestIdPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/logPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/msRestUserAgentPolicy.browser.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/msRestUserAgentPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/redirectPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/requestPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/rpRegistrationPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/signingPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/systemErrorRetryPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/policies/userAgentPolicy.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/util/base64.browser.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/util/base64.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/util/constants.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/util/utils.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/util/xml.browser.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/lib/util/xml.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/apiKeyCredentials.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/apiKeyCredentials.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/apiKeyCredentials.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/apiKeyCredentials.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/basicAuthenticationCredentials.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/basicAuthenticationCredentials.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/basicAuthenticationCredentials.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/basicAuthenticationCredentials.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/credentials.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/credentials.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/credentials.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/credentials.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/serviceClientCredentials.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/serviceClientCredentials.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/serviceClientCredentials.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/serviceClientCredentials.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/tokenCredentials.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/tokenCredentials.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/tokenCredentials.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/tokenCredentials.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/topicCredentials.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/topicCredentials.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/topicCredentials.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/credentials/topicCredentials.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/deserializationPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/deserializationPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/deserializationPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/deserializationPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/exponentialRetryPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/exponentialRetryPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/exponentialRetryPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/exponentialRetryPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/generateClientRequestIdPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/generateClientRequestIdPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/generateClientRequestIdPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/generateClientRequestIdPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/logPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/logPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/logPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/logPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/msRestUserAgentPolicy.browser.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/msRestUserAgentPolicy.browser.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/msRestUserAgentPolicy.browser.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/msRestUserAgentPolicy.browser.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/msRestUserAgentPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/msRestUserAgentPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/msRestUserAgentPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/msRestUserAgentPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/redirectPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/redirectPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/redirectPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/redirectPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/requestPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/requestPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/requestPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/requestPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/rpRegistrationPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/rpRegistrationPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/rpRegistrationPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/rpRegistrationPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/signingPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/signingPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/signingPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/signingPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/systemErrorRetryPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/systemErrorRetryPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/systemErrorRetryPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/systemErrorRetryPolicy.js.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/userAgentPolicy.d.ts'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/userAgentPolicy.d.ts.map'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/userAgentPolicy.js'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/future/botbuilder-js/node_modules/.staging/ms-rest-js-3d332aca/es/lib/policies/userAgentPolicy.js.map'
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-QHD9WigzC7rOJT0hb9Xzs/yHs1g/MOabJey8qxlZPdnnQqK5X8KJaZEEDnRqcUmLj/ydbxnxqImLEsMD5zlGag==) seems to be corrupted. Trying one more time.
npm ERR! code EINTEGRITY
npm ERR! Verification failed while extracting<EMAIL_ADDRESS>npm ERR! Verification failed while extracting<EMAIL_ADDRESS>npm ERR! sha512-58664aLhN1WQwAxMBK7LZQhFh8DHwenvpgz6ADFgeZLZS28NACfX+Uta8k2+WF6RK3g+VKoGOhV/yI71c5ccVg== integrity checksum failed when using sha512: wanted sha512-58664aLhN1WQwAxMBK7LZQhFh8DHwenvpgz6ADFgeZLZS28NACfX+Uta8k2+WF6RK3g+VKoGOhV/yI71c5ccVg== but got sha512-dNWR3SVQ8FxK8JEqj7l1nxbGT7zzWXpyKpPttiSZb4vBpGhxlTHEx1+UsDzRhlYX9GPxw5D6vnKgTZXns1s4ZQ==. (34771 bytes)
npm ERR!      /Users/sshehata/.npm/_logs/2019-11-06T22_12_01_928Z-debug.log
lerna ERR! npm install exited 1 in 'botbuilder-packages'
lerna WARN complete Waiting for 1 child process to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! botbuilder-packages@ postinstall: lerna bootstrap --hoist
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the botbuilder-packages@ postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/sshehata/.npm/_logs/2019-11-06T22_12_05_386Z-debug.log

Hmm...yours seems to suggest tarball corruption. Can you try:
npm uninstall -g typescript
npm cache clean --force
npm i -g typescript

...and then try running those commands again, but replace npm with yarn (npm install -g yarn)
I also see that some people run into this issue if they're behind a proxy or VPN.

Same issues.
Shadys-MacBook:workspace sshehata$ npm uninstall -g typescript
up to date in 0.033s
Shadys-MacBook:workspace sshehata$ npm uninstall -g typescript
up to date in 0.031s
Shadys-MacBook:workspace sshehata$ npm cache clean --force
npm WARN using --force I sure hope you know what you are doing.
npm ERR! path /Users/sshehata/.npm/_cacache/index-v5/00/90/33b874b1d668a0e687b5f218fec46393b2308acf2a67d3e107ced86fa4ad
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall unlink
npm ERR! Error: EACCES: permission denied, unlink '/Users/sshehata/.npm/_cacache/index-v5/00/90/33b874b1d668a0e687b5f218fec46393b2308acf2a67d3e107ced86fa4ad'
npm ERR!  { [OperationalError: EACCES: permission denied, unlink '/Users/sshehata/.npm/_cacache/index-v5/00/90/33b874b1d668a0e687b5f218fec46393b2308acf2a67d3e107ced86fa4ad']
npm ERR!   cause:
npm ERR!    { [Error: EACCES: permission denied, unlink '/Users/sshehata/.npm/_cacache/index-v5/00/90/33b874b1d668a0e687b5f218fec46393b2308acf2a67d3e107ced86fa4ad']
npm ERR!      errno: -13,
npm ERR!      code: 'EACCES',
npm ERR!      syscall: 'unlink',
npm ERR!      path:
npm ERR!       '/Users/sshehata/.npm/_cacache/index-v5/00/90/33b874b1d668a0e687b5f218fec46393b2308acf2a67d3e107ced86fa4ad' },
npm ERR!   isOperational: true,
npm ERR!   stack:
npm ERR!    "Error: EACCES: permission denied, unlink '/Users/sshehata/.npm/_cacache/index-v5/00/90/33b874b1d668a0e687b5f218fec46393b2308acf2a67d3e107ced86fa4ad'",
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'unlink',
npm ERR!   path:
npm ERR!    '/Users/sshehata/.npm/_cacache/index-v5/00/90/33b874b1d668a0e687b5f218fec46393b2308acf2a67d3e107ced86fa4ad' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).
npm ERR!      /Users/sshehata/.npm/_logs/2019-11-06T22_34_51_432Z-debug.log
Shadys-MacBook:workspace sshehata$ sudo npm cache clean --force
Password:
npm WARN using --force I sure hope you know what you are doing.
Shadys-MacBook:workspace sshehata$ sudo npm cache clean --force
npm WARN using --force I sure hope you know what you are doing.
Shadys-MacBook:workspace sshehata$ npm i -g typescript
/Users/sshehata/.nvm/versions/node/v11.15.0/bin/tsserver -> /Users/sshehata/.nvm/versions/node/v11.15.0/lib/node_modules/typescript/bin/tsserver
/Users/sshehata/.nvm/versions/node/v11.15.0/bin/tsc -> /Users/sshehata/.nvm/versions/node/v11.15.0/lib/node_modules/typescript/bin/tsc

<EMAIL_ADDRESS>added 1 package from 1 contributor in 13.463s
Shadys-MacBook:workspace sshehata$ npm install -g yarn
/Users/sshehata/.nvm/versions/node/v11.15.0/bin/yarn -> /Users/sshehata/.nvm/versions/node/v11.15.0/lib/node_modules/yarn/bin/yarn.js
/Users/sshehata/.nvm/versions/node/v11.15.0/bin/yarnpkg -> /Users/sshehata/.nvm/versions/node/v11.15.0/lib/node_modules/yarn/bin/yarn.js
<EMAIL_ADDRESS>added 1 package in 3.003s
Shadys-MacBook:workspace sshehata$ git clone https://github.com/microsoft/botbuilder-js.git
Cloning into 'botbuilder-js'...
remote: Enumerating objects: 285, done.
remote: Counting objects: 100% (285/285), done.
remote: Compressing objects: 100% (218/218), done.
remote: Total 42239 (delta 110), reused 126 (delta 61), pack-reused 41954
Receiving objects: 100% (42239/42239), 25.55 MiB | 4.97 MiB/s, done.
Resolving deltas: 100% (30369/30369), done.
Shadys-MacBook:workspace sshehata$ cd botbuilder-js
Shadys-MacBook:botbuilder-js sshehata$  git checkout 4.future
Branch '4.future' set up to track remote branch '4.future' from 'origin'.
Switched to a new branch '4.future'
Shadys-MacBook:botbuilder-js sshehata$ git reset --hard db56b4cac07dae20be7e6922e34a68d2ba07e31c
HEAD is now at db56b4ca LG: Fix more bugs
Shadys-MacBook:botbuilder-js sshehata$  npm i

botbuilder-packages@ postinstall /Users/sshehata/workspace/botbuilder-js
lerna bootstrap --hoist

lerna notice cli v3.13.1
lerna info versioning independent
lerna info Bootstrapping 25 packages
lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-expression-parser" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "transcript-tests" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-connector" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna info Installing external dependencies
lerna info hoist Installing hoisted dependencies into root
lerna info hoist Pruning hoisted dependencies
lerna info hoist Finished pruning hoisted dependencies
lerna ERR! npm install exited 1 in 'botbuilder-packages'
lerna ERR! npm install stderr:
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-0aJ5UIjs6dKZYdovnlnoIb7+wBId3cubQzwC0tH6S//JhayqrKqMcD8vPPgwZHhBhBx8ZFNmKD3MJtCvZZ1GYA==) seems to be corrupted. Trying one more time.
npm ERR! code EINTEGRITY
npm ERR! sha512-gej7KR0iFIK38M4eIkGFOn+Tk7sMpzGTJgMVy/ctz21m6vQDGfqFLjJzDk4GRG9oLaZfq5bqUw5sLtepLAZcUg== integrity checksum failed when using sha512: wanted sha512-gej7KR0iFIK38M4eIkGFOn+Tk7sMpzGTJgMVy/ctz21m6vQDGfqFLjJzDk4GRG9oLaZfq5bqUw5sLtepLAZcUg== but got sha512-RDovFqtZFy9TGqcsX49SP8rjxSArsvmcWJA4ECTrg8haBTBq1wiiR6cFxKYfI8qonJo6y0+zzvU2LXuZNBI77w==. (40829 bytes)
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-QHD9WigzC7rOJT0hb9Xzs/yHs1g/MOabJey8qxlZPdnnQqK5X8KJaZEEDnRqcUmLj/ydbxnxqImLEsMD5zlGag==) seems to be corrupted. Trying one more time.
npm ERR! code EINTEGRITY
npm ERR! sha512-0aJ5UIjs6dKZYdovnlnoIb7+wBId3cubQzwC0tH6S//JhayqrKqMcD8vPPgwZHhBhBx8ZFNmKD3MJtCvZZ1GYA== integrity checksum failed when using sha512: wanted sha512-0aJ5UIjs6dKZYdovnlnoIb7+wBId3cubQzwC0tH6S//JhayqrKqMcD8vPPgwZHhBhBx8ZFNmKD3MJtCvZZ1GYA== but got sha512-AtRZO9K8khguxEw50yg3aDireNJbqlefpjkWCILxMplaCAIMSgUptEhcsbAL5LARYA8cAMKxmxwlCJ6zL8hz9w==. (24237 bytes)
npm ERR! code EINTEGRITY
npm ERR! sha512-58664aLhN1WQwAxMBK7LZQhFh8DHwenvpgz6ADFgeZLZS28NACfX+Uta8k2+WF6RK3g+VKoGOhV/yI71c5ccVg== integrity checksum failed when using sha512: wanted sha512-58664aLhN1WQwAxMBK7LZQhFh8DHwenvpgz6ADFgeZLZS28NACfX+Uta8k2+WF6RK3g+VKoGOhV/yI71c5ccVg== but got sha512-dNWR3SVQ8FxK8JEqj7l1nxbGT7zzWXpyKpPttiSZb4vBpGhxlTHEx1+UsDzRhlYX9GPxw5D6vnKgTZXns1s4ZQ==. (34771 bytes)
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-U8n+eY9Cjce0GkMyyE0mv4HBjCjtyuczz6usl9XF2N7nY61jYDah4W5e4zqYdLdlqnBwfxG8ptS9pdnmVsC2ww==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-O2RmSG4AFyNc7h9zD2a7kdIBw8jF3Thpl8Pwfs/BpKGhRrCIJAMasV0+UbIV2Iwi2NEl7WzdpXjUsnpmB57XgQ==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-QHD9WigzC7rOJT0hb9Xzs/yHs1g/MOabJey8qxlZPdnnQqK5X8KJaZEEDnRqcUmLj/ydbxnxqImLEsMD5zlGag==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-U8n+eY9Cjce0GkMyyE0mv4HBjCjtyuczz6usl9XF2N7nY61jYDah4W5e4zqYdLdlqnBwfxG8ptS9pdnmVsC2ww==) seems to be corrupted. Trying one more time.
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/workspace/botbuilder-js/node_modules/.staging/chai-d602b467/CODE_OF_CONDUCT.md'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/workspace/botbuilder-js/node_modules/.staging/chai-d602b467/CODEOWNERS'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/workspace/botbuilder-js/node_modules/.staging/chai-d602b467/CONTRIBUTING.md'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/workspace/botbuilder-js/node_modules/.staging/bunyan-74874922/docs/index.html'
npm WARN tar ENOENT: no such file or directory, open '/Users/sshehata/workspace/botbuilder-js/node_modules/.staging/ms-rest-js-d922cbd2/dist/msRest.browser.min.js'
npm WARN tar ENOENT: no such file or directory, open<EMAIL_ADDRESS>npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-O2RmSG4AFyNc7h9zD2a7kdIBw8jF3Thpl8Pwfs/BpKGhRrCIJAMasV0+UbIV2Iwi2NEl7WzdpXjUsnpmB57XgQ==) seems to be corrupted. Trying one more time.
npm ERR! code EINTEGRITY
npm ERR! Verification failed while extracting<EMAIL_ADDRESS>npm ERR! Verification failed while extracting<EMAIL_ADDRESS>npm ERR! sha512-QHD9WigzC7rOJT0hb9Xzs/yHs1g/MOabJey8qxlZPdnnQqK5X8KJaZEEDnRqcUmLj/ydbxnxqImLEsMD5zlGag== integrity checksum failed when using sha512: wanted sha512-QHD9WigzC7rOJT0hb9Xzs/yHs1g/MOabJey8qxlZPdnnQqK5X8KJaZEEDnRqcUmLj/ydbxnxqImLEsMD5zlGag== but got sha512-luYhV9zMXfHHSl5xNPmBTVlxX2yj/+AzRUnB7gxQJ0L1OpNrFk/uf+xfuNwO94pu3jMtDbKA9axVhQtY2QSlyQ==. (91529 bytes)
npm ERR!      /Users/sshehata/.npm/_logs/2019-11-06T22_37_53_131Z-debug.log
lerna ERR! npm install exited 1 in 'botbuilder-packages'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! botbuilder-packages@ postinstall: lerna bootstrap --hoist
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the botbuilder-packages@ postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/sshehata/.npm/_logs/2019-11-06T22_38_06_331Z-debug.log

@mdrichardson - If I didn't git reset --hard db56b4cac07dae20be7e6922e34a68d2ba07e31c
It went through but provide the issue about StateMachineDialog is not a constructor
Shadys-MacBook:workspace sshehata$ git clone https://github.com/microsoft/botbuilder-js.git
Cloning into 'botbuilder-js'...
remote: Enumerating objects: 285, done.
remote: Counting objects: 100% (285/285), done.
remote: Compressing objects: 100% (218/218), done.
remote: Total 42239 (delta 110), reused 126 (delta 61), pack-reused 41954
Receiving objects: 100% (42239/42239), 25.55 MiB | 5.63 MiB/s, done.
Resolving deltas: 100% (30369/30369), done.
Shadys-MacBook:workspace sshehata$ cd botbuilder-js
Shadys-MacBook:botbuilder-js sshehata$ git checkout 4.future
Branch '4.future' set up to track remote branch '4.future' from 'origin'.
Switched to a new branch '4.future'
Shadys-MacBook:botbuilder-js sshehata$ npm install

botbuilder-packages@ postinstall /Users/sshehata/workspace/botbuilder-js
lerna bootstrap --hoist

lerna notice cli v3.13.1
lerna info versioning independent
lerna info Bootstrapping 26 packages
lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-dialogs-adaptive" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-dialogs-declarative" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-connector" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-connector" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-applicationinsights" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-azure" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-core" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-dialogs" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-dialogs-adaptive" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-dialogs-declarative" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-testing" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-config" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-connector" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "testbot" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "transcript-tests" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-expressions" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-connector" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "transcript-tests" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-config" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-ai" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botframework-connector" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "botbuilder-lg" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "testbot" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna info Installing external dependencies
lerna info hoist Installing hoisted dependencies into root
lerna info hoist Pruning hoisted dependencies
lerna info hoist Finished pruning hoisted dependencies
lerna info hoist Finished bootstrapping root
lerna info Symlinking packages and binaries
lerna success Bootstrapped 26 packages
added 859 packages from 1560 contributors in 79.603s
Shadys-MacBook:botbuilder-js sshehata$ npm run build

botbuilder-packages@ build /Users/sshehata/workspace/botbuilder-js
lerna run build

lerna notice cli v3.13.1
lerna info versioning independent
lerna info Executing command in 14 packages: "npm run build"
lerna info run Ran npm script 'build' in 'botframework-schema' in 3.0s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botframework-schema
tsc

lerna info run Ran npm script 'build' in 'botframework-config' in 3.2s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botframework-config
tsc

lerna info run Ran npm script 'build' in 'botframework-expressions' in 5.3s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botframework-expressions
tsc

lerna info run Ran npm script 'build' in 'botframework-connector' in 3.8s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botframework-connector
tsc

lerna info run Ran npm script 'build' in 'botbuilder-core' in 4.0s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder-core
tsc

lerna info run Ran npm script 'build' in 'botbuilder-lg' in 5.1s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder-lg
tsc

lerna info run Ran npm script 'build' in 'botbuilder-applicationinsights' in 4.2s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder-applicationinsights
tsc

lerna info run Ran npm script 'build' in 'botbuilder' in 4.7s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder
tsc

lerna info run Ran npm script 'build' in 'botbuilder-ai' in 4.9s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder-ai
tsc

lerna info run Ran npm script 'build' in 'botbuilder-dialogs' in 5.3s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder-dialogs
tsc

lerna info run Ran npm script 'build' in 'botbuilder-testing' in 3.7s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder-testing
tsc

lerna info run Ran npm script 'build' in 'botbuilder-azure' in 4.4s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder-azure
tsc

lerna info run Ran npm script 'build' in 'botbuilder-dialogs-adaptive' in 4.9s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder-dialogs-adaptive
tsc

lerna info run Ran npm script 'build' in 'botbuilder-dialogs-declarative' in 2.7s:

<EMAIL_ADDRESS>build /Users/sshehata/workspace/botbuilder-js/libraries/botbuilder-dialogs-declarative
tsc

lerna success run Ran npm script 'build' in 14 packages in 23.4s:
lerna success - botbuilder
lerna success - botbuilder-ai
lerna success - botbuilder-applicationinsights
lerna success - botbuilder-azure
lerna success - botbuilder-core
lerna success - botbuilder-dialogs
lerna success - botbuilder-dialogs-adaptive
lerna success - botbuilder-dialogs-declarative
lerna success - botbuilder-lg
lerna success - botbuilder-testing
lerna success - botframework-config
lerna success - botframework-connector
lerna success - botframework-expressions
lerna success - botframework-schema
Shadys-MacBook:botbuilder-js sshehata$ cd samples/30.\ stateMachineDialog/
Shadys-MacBook:30. stateMachineDialog sshehata$ npm start

<EMAIL_ADDRESS>start /Users/sshehata/workspace/botbuilder-js/samples/30. stateMachineDialog
node ./lib/index.js

/Users/sshehata/workspace/botbuilder-js/samples/30. stateMachineDialog/lib/index.js:33
const dialogs = new botbuilder_dialogs_adaptive_1.StateMachineDialog('main', 'offHook');
^
TypeError: botbuilder_dialogs_adaptive_1.StateMachineDialog is not a constructor
at Object. (/Users/sshehata/workspace/botbuilder-js/samples/30. stateMachineDialog/lib/index.js:33:17)
at Module._compile (internal/modules/cjs/loader.js:956:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
at Module.load (internal/modules/cjs/loader.js:812:32)
at Function.Module._load (internal/modules/cjs/loader.js:724:14)
at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)
at internal/main/run_main_module.js:17:11
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node ./lib/index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/sshehata/.npm/_logs/2019-11-06T22_45_32_605Z-debug.log
Shadys-MacBook:30. stateMachineDialog sshehata$

The git reset forces it to use the SDK from April, which has the StateMachineDialog (it doesn't currently)
Hm...hopefully it isn't a Mac thing.
I'm assuming if you run npm config get registry, it gives "http://registry.npmjs.org/"?
If not, try npm config set registry http://registry.npmjs.org/
Do you need to run the commands with sudo? ...not familiar with MacOS
This isn't ideal, but I fixed a similar issue to this a couple of weeks ago for myself by uninstalling npm, deleting the entire npm cache and install directories, and re-installing npm.
I really don't know what else to try beyond this, other than installing a VM with a different OS or something (also not ideal).

You might be able to copy the necessary classes over from here into your local install with the current state of the repo, then build. I'd test it, but I have trouble getting the current 4.future to build.

...actually, I've been trying that for the last hour and it is requiring a ridiculous number of changes. I honestly don't know what to recommend at this point. Probably:

Try to get the April state of the SDK to work, or
Play with the C# samples to get a feel for things until Node samples are ready. The SDK just isn't in a state where Adaptive Dialogs are ready for anything on the Node side.

I think we've exhausted this issue and I lean towards closing it, but let me know if you'd like to try something else. Normally, I'd leave this open as a feature request, but this particular sample may go away entirely and the dev team is aware that Adaptive Dialogs needs samples for Node

@mdrichardson - Thanks for your help. I'm fine to close the issue.

@sshehata-zz You're welcome. Sorry we couldn't get it to work! It's just a little too early for Adaptive Dialogs in Node.


[reggen,dv] Remove some unused type: ignore comments

These had no effect but cause errors if you run mypy with
make -C hw/ip/otbn/dv/otbnsim lint
I think I fixed the original problems with 6e37279.

Hmm. That doesn't work at all! I think the problem is that we don't set up a path correctly when we run this in CI, which means that the mypy check for OTBN can't see the reggen code. The lines that I was removing here are telling the test not to worry about it.
I suspect we can sort out the paths properly without much work, but the first step in tidying this up is definitely not this PR.


There is a significant performance issue on mobile devices

Check that this is really a bug

[X] I confirm

Reproduction link
https://studio.swiperjs.com/play
Bug description
We installed SwiperJs version 11.1 in our project and it looks great. However, when I open the site on real device, iPhone 15 pro, I saw a significant performance issue in other elements of the page.
On mobile view, we show 5 checkbox above the fold and render SliderJs below the fold. On mobile device, there is a delay when clicking on those checkboxes. If I remove SwiperJs the delay is gone.
We tried to downgrade to version 10.3.1 and the problem was gone. Therefore, I believe there is a significant performance issue on version 11+ on real mobile devices.
To confirm the bug, I opened your playground site - https://studio.swiperjs.com/play and clicked on the toggles very fast. I saw the same performance issue that we had on our website.
We also tried to use the web component version, which has the same problems. Therefore, we think it is a core issue.
Expected Behavior
The screen should be interactive without and delays.
Actual Behavior
No response
Swiper version
11+
Platform/Target and Browser Versions
Chrome
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

I was able to reproduce it on your official demo page - https://studio.swiperjs.com/play.
I think this is your repo - https://github.com/nolimits4web/swiper/tree/master/playground/react


Obsidian default checkbox is - [x] but dataview uses upper case like - [X]

Can it set to Obsidian default one?

Or just ignore case?

Dataview does ignore case for existing tasks; is there a particular reason you want lowercase 'x', or just for consistency?

In my case: to catch all [x] or [X] that might have been used in Markdown files. (Although my Obsidian 0.12.3 shows a task completed regardless of the x is lower- or uppercase. Maybe not all plugins do.)

Fixed in 0.3.10.


Add Maintainer's github link.

Fixes #248
Checklist

[x ] I have read the Contribution & Best practices Guide and my PR follows them.
[ x] My branch is up-to-date with the Upstream master branch.
[ ] I have added necessary documentation (if appropriate)

Changes proposed in this pull request:

Add Maintainer's github link so as to avoid 404 error.

@vaibhavsingh97  Thanks :).
@bhaveshAn ok, I will take care of it from next time :) .


Show_Boss_Bar Low Health Showing Wither

The low health mechanic and effect of the wither is causing the show_boss_bar to show the withers scrolling texture effect. I'm not sure if this can even be fixed due to the changes Mojang made recently.

/ex adjust  show_boss_bar:1|1

This is an issue with withers not being able to not have their shield appear below half their health even when invisible.


ZITADEL V3

This major release introduces a comprehensive overhaul of our API structure (resource based API), user schemas, new login UI, and new workflow customization capabilities (Actions V2).
Requirements
ZITADEL Core

[ ] AGPLv3 License
[ ] User Schemas
[ ] Relevant Settings for new Login
[ ] Sessions
- [ ] SAML
[ ] Actions V2
[ ] Ressource APIs
[ ] Translations / Custom Text (to clarify @hifabienne )
[ ] General Changes (to clarify @livio-a )
- [ ] Defaults YAML, Clean ups
- [ ] First Instance/Default Instance
- [ ] Cmd package
[ ] Clean Up (Remove old stuff)

[ ] Actions v1
[ ] V1 API
[ ] V2 API
[ ] Login V1

ZITADEL Typescript Login

[ ] Feature List (to clarify @hifabienne )
[ ] Multi Tenancy
[ ] User Schema
[ ] SAML Session Handling
[ ] User Profile Page
[ ] Translations

ZITADEL Management Console

[ ] Call Ressource API instead of Service Based API everywhere
[ ] User Schemas
[ ] Actions V2
[ ] Remove Self Service (User Profile will be implemented in new Login UI)

Does that have any impact to our customers?

Customer Portal

[ ] Create new instances with V3
[ ] Upgrade from V2 to V3

General

[ ] Deployments

@hifabienne amazing except for the licence change from Apache to AGPLv3, this would be a a huge disappointment. Is this already 100% decided?


🌊 auto-sync with upstream

The Issue
Automatically sync local with upstream
How This PR Solves The Issue
Manual Testing Instructions
Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

Proof of concept only. Closing.


fix: When PackageManifest is not found, add the error message into co…

…ndition of the status
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

@Daniel-Fan fixed the format error. Please review it again


Add orderBy dates syntactic sugar

Fix https://github.com/romcal/romcal/issues/270.
Romcal will always output data as an array.
This .groupBy('dates') method is a syntactic sugar, that allows to quickly group outputted results by dates.
const data = await Romcal.calendarFor({ year: 2021 });
const groupedByDates = data.groupBy('dates');

This also can be addressed natively by JavaScript (using a reduce method). But I think it will be a convenient method for any romcal users that are not too comfortable with JavaScript.

One thing I'm wondering, should the groupBy criteria should be singular or plural?
Here is the actual list of groupBy options: https://github.com/romcal/romcal/blob/_F-TypeScript/docs/general-usage.md#group-results-by-criteria

Thank you. I've renamed the groupBy criterias from plural to singular. I also think it's better.
And the outputOptionalMemorials doesn't exist anymore.


Language code is not correct for Chinese

Simplified Chinese language code zh-cn is deprecated and should be changed to zh-hans.
Please refer to the link below.
https://code.djangoproject.com/ticket/18419

This is because Traditional Chinese is not used only by Taiwan (tw) but also Honk Kong (hk), and Simplified Chinese is not only used in China (cn) but also Singapore (sg) and Malaysia. A new standard is to use "zh_Hant" for Traditional Chinese and "zh_Hans" for Simplified Chinese to eliminate the confusion of the content is not just for people lived in China or Taiwan.

Maybe it's sufficient to create a symlink in locale directory from zh_Hans to zh_CN, does it works with transifex tool?

The zh_CN and zh_Hant translations have now reached 100% completion on Transifex (a huge thank you to everyone involved!), so I've now removed the incomplete zh_TW translation and (in d5bc3c92d22672f06f2aeab1e1731ca4f4fcb383) updated the Transifex configuration to download these to the new locations zh_Hans and zh_Hant. Hopefully this solves the issue.
I've tested this locally and it seems to work - characters are changing when I switch between the locales - but I don't know Chinese, so I'd encourage other people to test this, and let me know on this ticket if anything isn't right. (There will be a release candidate of Wagtail 2.5 published shortly.)


Injecting $app, $req, $res, $services params to controllers?

Hey,
I have a code like this:
$klein->respond(function ($request, $response, $service, $app) {
     // Bunch of stuff
});

I want to pass them into a class (not controllers) but doing this each time looks crazy.
$klein->respond(function ($req, $res, $service, $app) {
     $something = new App\Something($req, $res, $service, $app, $myParams);
});

Is there any trick or patterns to pass those values to those classes on the fly. For example, can something like this be done?
class Controller
{
     protected $req, $res, $service, $app;
     public function__construct($req, $res, $service, $app)
     {
            $this->req = $req;
            $this->res = $res;
            $this->service = $service;
            $this->app = $app;
     }
}

class HomeController extends Controller
{
     protected $myParams
     public function__construct($myParams)
     {
            $this->myParams = $myParams;
     }
}

$klein->respond(function ($req, $res, $service, $app) {
     $something = new App\HomeController($myParams);
     dd($something->req); // same as $req
});

I just want to inject $req, $res, $service, $app to my classes somehow.
Any tip would be appreciated.

Don't inject it on the class but pass it along to each action method like klein does:
class HomeController extends Controller
{
public function homeAction($req, $resp, $service, $app)
{
return $resp;
}
}
$controller = new HomeController();
$klein->respond([$controller, 'homeAction']);

That can be improved I think. Passing 4 parameters to every single method sounds pretty bad imo.

The parameters are optional if you are not going to use them then don't put
them on the method signature.
On Feb 1, 2016 2:45 PM, "Anıl ÜNAL"<EMAIL_ADDRESS>wrote:

That can be improved I think. Passing 4 parameters to every single method
sounds pretty bad imo.
—
Reply to this email directly or view it on GitHub
https://github.com/chriso/klein.php/issues/313#issuecomment-178148435.

I just want to pass them into each controller without having to all 4 variables into methods as seperate parameters. I don't enjoy passing them into methods as parameters everywhere because the app barely be maintainanle like that. That's why I asked this question in first place.
Whenever I create a controller, I want them to be injected into the class (without having to specify that myself, Klein should resolve the call itself and append the parameters automatically) so I can organize my code much easier.
Thanks for your contributions though, but that's not I'm asking for.

klein includes a simple dependency injector (see $app->register in the docs).  Instead of $something = new App\Something($req, $res, $service, $app, $myParams);, you could register something as a dependency:
$app->register("something", function() {
    return new App\Something($req, $res, $service, $app, $myParams);
});

Then, when you need it, you just ass $app for an instance:
$something = $app->something;

and it creates the object with the correct params injected.  If you want "smarter" injection, you may want something like php-di, which can look at your classes and try to guess what to inject.

Request, Response, and Service can be pulled from within the $klein object so I just pass that to my controller or add it to a global singleton registry object.
$klein->respond('/search/[results:action]/?[i:page]?', function() use ($klein) {

	$klein->service()->layout('app/layouts/2-column.php');

	$control = new SearchController( $klein );
	$control->run();

});


Mod Mode not working

Whenever I click the mod mode button on Chatterino it just brings up the mod settings instead of showing the mod buttons in chat. I can still type mod commands manually and click on usernames to timeout/ban it just doesn't allow me the shortcuts to delete messages and such.

https://user-images.githubusercontent.com/89472270/130649756-94ef4102-838f-467c-9747-39b771a15df3.mp4

Windows 10 and Chatterino 2.3.4
https://user-images.githubusercontent.com/89472270/130649756-94ef4102-838f-467c-9747-39b771a15df3.mp4

This isn't a bug - the settings dialog is opened because you don't have any mod buttons defined. See https://wiki.chatterino.com/Moderation/#moderation-mode on how to add them.


Are favourites local ?

I have been using ShoppingList on my phone for a while now and adding favourite items. Cool!
I recently installed it to our other devices , but when I go to add a favourite item on these new devices it shows 'You have no favourites yet - add some!'
Are the favourites only stored locally on each device ?
Could these favourite items also be sync'ed and stored on the server ?
Thanks.

Hey. Thanks for your feedback!
Hm, that is intentional. Personally, my girlfriend and I have different things we most likely add, so I never really thought about it.
It is possible, no question. But would probably require restructuring and adding something like different users, because I would not want to see the favorites of everybody.
I will think of a more elegant solution, which should ideally be easy to implement.

For now I am clicking on Favourites I have already added to the list and then edit and clicking Favourite , this creates it on the new device.


execute.many

Is there an equivalent of this python function in order to perform multiple insert at once in the database?

Option 1
You can insert more rows in a single insert:
await conn.execute(
    'INSERT INTO tbl VALUES (@a1, @b1, @c1), (@a2, @b2, @c2)',
    substituteValues: {[... map with a1, b1, c1, a2, b2, c2 ...] });

Option 2
You can send commands without awaiting them separately, but probably should wait for them eventually:
final futures = <Future>[];
futures.add(conn.execute(query, {[... values ...]}));
futures.add(conn.execute(query, {[... values ...]}));
futures.add(conn.execute(query, {[... values ...]}));
await Future.wait(futures);

Option 3
You can use the above in a different way:
final query = 'INSERT INTO ...';
final values = [{[... first row data ...]}, {... second row data...}];
await Future.wait(values.map((v) => conn.execute(query, substititeValues: v)));

Note: using package:postgres_pool with configurable concurrency may be a better choice for this. It may use different connections for the inserts, and you can still control the overall connections being used.

execute is for modifications (DDL, insert, update, delete), while query is for selects.

Thank you and sorry for the rookie question!


support gitmailmap in GetCodeActivityStats()

ref:

https://git-scm.com/docs/gitmailmap
https://git-scm.com/docs/git-log#Documentation/git-log.txt-emaNem

🚀


Crystal: avoid using wget

The version on Travis has TLS support that was nice in the 90s
/cc @will @asterite @waj

I think @waj reverted requirement of https for some things, so this might not be needed anymore.
@waj ?

Even if the requirement is removed, and if all else is equal, it's probably better to use tls.

I reverted the redirection from HTTP to HTTPS, but still the latest should be used whenever possible.
The builds are failing after c31b27125a06d75dbd21bbaa25f304aae1f72f2e because the repository is hosted in CloudFront and it doesn't support SSLv3 (https://aws.amazon.com/security/security-bulletins/CVE-2014-3566-advisory/)
@jhass are you sure this will fix the issue with the builds? or it depends on the installed OpenSSL version?

I didn't get a chroot to test, but my experience is that curl works in these cases while wget doesn't.

Is there something we can do to push this forward? All Crystal projects using travis are basically failing because of this :-(

@BanzaiMan thank you so much for this! ❤


Update README.md

Update brew cask command according to error message:

Error: No available formula with the name "openmtp"
Found a cask named "openmtp" instead. Try
brew cask install openmtp

what version of brew are you using?

what version of brew are you using?

2.5.2

2.5.2

can you mention commands for both.
Something like this:
# older
brew cask install openmtp

# newer
brew install openmtp --cask

can you mention commands for both.
Something like this:
# older
brew cask install openmtp

# newer
brew install openmtp --cask

Merged, thanks!

Merged, thanks!

Sure thing!

Sure thing!