kovkev
kovkev
/ part of webpack's output when trying to resolve a directory
Created
January 19, 2020 04:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ERROR in ./bazel-out/k8-fastbuild/bin/human/frontpage/index.js | |
| Module not found: Error: Can't resolve './react-landing-page' in '/home/kevin/.cache/bazel/_bazel_root/0c9a5b8043c67e9ade46bac27cbfed6e/sandbox/linux-sandbox/28/execroot/my_wksp/bazel-out/k8-fastbuild/bin/human/frontpage' | |
| resolve './react-landing-page' in '/home/kevin/.cache/bazel/_bazel_root/0c9a5b8043c67e9ade46bac27cbfed6e/sandbox/linux-sandbox/28/execroot/my_wksp/bazel-out/k8-fastbuild/bin/human/frontpage' | |
| No description file found | |
| No description file found | |
| no extension | |
| /home/kevin/.cache/bazel/_bazel_root/0c9a5b8043c67e9ade46bac27cbfed6e/sandbox/linux-sandbox/28/execroot/my_wksp/bazel-out/k8-fastbuild/bin/human/frontpage/react-landing-page doesn't exist | |
| .ts | |
| /home/kevin/.cache/bazel/_bazel_root/0c9a5b8043c67e9ade46bac27cbfed6e/sandbox/linux-sandbox/28/execroot/my_wksp/bazel-out/k8-fastbuild/bin/human/frontpage/react-landing-page.ts doesn't exist | |
| .tsx |
kovkev
/ ansible logs
Last active
October 8, 2019 14:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Target //corp/dev:master_ami up-to-date: | |
| bazel-bin/corp/dev/master_ami_config_deploy_packer.py | |
| INFO: Elapsed time: 0.627s, Critical Path: 0.43s | |
| INFO: 2 processes: 2 darwin-sandbox. | |
| INFO: Build completed successfully, 3 total actions | |
| INFO: Build completed successfully, 3 total actions | |
| amazon-ebs output will be in this color. | |
| ==> amazon-ebs: Prevalidating AMI Name: packer-example 1570545819 | |
| amazon-ebs: Found Image ID: ami-04763b3055de4860b |
kovkev
/ ansible logs
Created
October 8, 2019 14:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Target //corp/dev:master_ami up-to-date: | |
| bazel-bin/corp/dev/master_ami_config_deploy_packer.py | |
| INFO: Elapsed time: 1.376s, Critical Path: 0.66s | |
| INFO: 2 processes: 2 darwin-sandbox. | |
| INFO: Build completed successfully, 3 total actions | |
| INFO: Build completed successfully, 3 total actions | |
| amazon-ebs output will be in this color. | |
| ==> amazon-ebs: Prevalidating AMI Name: packer-example 1570543979 | |
| amazon-ebs: Found Image ID: ami-04763b3055de4860b |
kovkev
/ example.json
Last active
October 8, 2019 14:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "variables": { | |
| "aws_access_key": "", | |
| "aws_secret_key": "" | |
| }, | |
| "builders": [ | |
| { | |
| "type": "amazon-ebs", | |
| "access_key": "{{user `aws_access_key`}}", | |
| "secret_key": "{{user `aws_secret_key`}}", |
kovkev
/ gist:93d730e428c442377a967b099cd18c05
Created
March 20, 2018 16:15
Long running interactive processes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| What is a nice solution for user defined long running | |
| interactive processes that should ideally always be running? | |
| I have this server which I want to sync a certain local | |
| directory with. I want to do so when I am ssh'ed to the | |
| server. The way I used to do it was spin up a unison job | |
| locally, which would connect to the server's unison and | |
| both processes would communicate the changes made locally. | |
| Today, I instead spin up the unison job on the server. |