code for alumxi.com
issue commentsourcegraph/sourcegraph
Distribution - 2020.10.20 - Vibrant Beetle
This week:
I spent most of my time debugging https://github.com/sourcegraph/customer/issues/74. I also release a rough draft of the Dhall demo video (https://github.com/sourcegraph/sourcegraph/issues/14646) for @sourcegraph/distribution to review in https://sourcegraph.slack.com/archives/CJX299FGE/p1604110703335500.
Next week:
I will respond to feedback on the rough draft Dhall video that I shared, and I aim to restart work on https://github.com/sourcegraph/sourcegraph/issues/13340
comment created time in 2 hours
issue commentsourcegraph/sourcegraph
Create customer demo video for dhall direction
The materials are ready to go, but I have task switched https://github.com/sourcegraph/customer/issues/74 since this is an urgent issue
comment created time in a day
push eventggilmore/deploy-sourcegraph-dhall-demo
commit sha 38536524e6f9fe8a105241fe80e540bacba13fbd
video
push time in a day
push eventalumxi22/website
commit sha 2d824d853e3641d66d33fa2c537e134f044f9572
add shfmt script
push time in 3 days
push eventalumxi22/website
commit sha 3c53fee3f9292102fa09747516df86d64c4b47ec
fix installation script
push time in 3 days
push eventalumxi22/website
commit sha c09bcf7afa3449b06728364bbdb6f86ec46d964d
fix readme
push time in 3 days
issue commentsourcegraph/sourcegraph
Distribution - 2020.10.20 - Vibrant Beetle
This week:
- Retrospective
- Deployment Discussion
- Prepared all prerequisite materials for recording the customer demo.
Next week:
- Monday: record the demo and share with distribution for feedback
- Get back to https://github.com/sourcegraph/sourcegraph/issues/13340
comment created time in 5 days
push eventggilmore/deploy-sourcegraph-dhall-demo
commit sha a52aedf85ff4a067839bcff1c38c7a327050b741
prepare for demo
push time in 5 days
push eventggilmore/deploy-sourcegraph-demo
commit sha 19c8e1206407bef532e35e517fa303a26c2f087e
gitserver: fix cpu
push time in 5 days
PR opened ggilmore/deploy-sourcegraph-demo
pr created time in 5 days
push eventggilmore/deploy-sourcegraph-demo
commit sha e472e18089805f42c7f51ebe7fe95d73b3bff75c
gitserver: bump CPU limit to 4
push time in 5 days
push eventggilmore/deploy-sourcegraph-demo
commit sha 860b10c227a5f38d4629de298e9feba0f4846efd
bump frontend replicas to "2"
push time in 5 days
push eventalumxi22/website
commit sha 29b53aa3e74fbecf4e2f0d2a9d44c192f4420b9c
remove '+' sign
push time in 6 days
push eventalumxi22/website
commit sha 1bf41f71a53979bda6d21fd376df55910dc69cae
update crock description
push time in 6 days
push eventggilmore/deploy-sourcegraph-dhall-demo
commit sha adbc56995bf247f952b889e68817732b186e9772
hardcode storageclass
push time in 7 days
pull request commentalumxi22/website
You should be able to run the command just (or just build) to render the site and format everything.
comment created time in 8 days
push eventggilmore/deploy-sourcegraph-dhall-demo
commit sha 360c83d7426ca9aeca457e6c26126de7f07949cf
codeinteldb
commit sha 6b1b46f403ed3e66d3afe0adc7478568eb2c6ccb
render
push time in 9 days
push eventggilmore/dotfiles
commit sha 89c1d95f48cb3afe623daf833ecdd2d1f4516f4c
fix autojump directory
push time in 10 days
push eventggilmore/dotfiles
commit sha 853ba0c4eeb153d5a1f062f7b4db0291be7d7b67
fix autojump path
push time in 10 days
push eventggilmore/dotfiles
commit sha e4d3604f76103eaae9527f3f9fb42820e9900094
fix install
push time in 10 days
push eventggilmore/dotfiles
commit sha cc4f04015292befa1251529fed719a7add45efca
fd
push time in 10 days
push eventggilmore/dotfiles
commit sha 4c3dd6187acd7db0924804689398c25ead55460e
bat
push time in 10 days
push eventggilmore/dotfiles
commit sha e04804ffcb905220cec4f9447fd71c2622fd09b2
pi: bash -cf for "yes"
push time in 10 days
push eventggilmore/dotfiles
commit sha c0a55ac9d4c1088c97901f467a3d8dbe02be8c0b
add raspberry pi files (#1)
push time in 10 days
PR merged ggilmore/dotfiles
pr closed time in 10 days
PR opened ggilmore/dotfiles
pr created time in 10 days
pull request commentalumxi22/website
just, however, is something that can be managed through asdf now that my PR has been accepted https://github.com/asdf-vm/asdf-plugins/pull/287
comment created time in 11 days
pull request commentalumxi22/website
Also, is GNU parallel something we can manage through asdf? It'd be nice to have a setup that didn't require people to install that either (or at least we should mention it in the README).
No, nobody has written a plugin for it yet (nor do I know where the source lives or if static binaries exist for it). I
I see now that this repo has a slightly order version of these scripts. In later changes in other repos, I actually moved the parallel calls to a separate script that has a more helpful error message: https://github.com/ggilmore/kickstart/blob/4d60da80f7f3a64ed6f4bbea3ea829771473271e/scripts/parallel_run.sh#L1-L12. I can add the refactor to this repository too.
comment created time in 11 days
pull request commentalumxi22/website
The repo / CI is already setup to manage fd through asdf:
- https://github.com/alumxi22/website/blob/e0a4aa55e83f173f940deb51675b7cbfe48aa7c4/.tool-versions#L7
- https://github.com/alumxi22/website/blob/e0a4aa55e83f173f940deb51675b7cbfe48aa7c4/scripts/ci/dhall/setup.dhall#L8
- https://github.com/alumxi22/website/blob/e0a4aa55e83f173f940deb51675b7cbfe48aa7c4/scripts/ci/asdf-add-plugins.sh#L17
- https://github.com/alumxi22/website/runs/1277899339#step:4:82
I just don't call out the installation of the asdf-fd plugin in the README yet for the local setup instructions. I'd just add another bullet point to install this plugin https://gitlab.com/wt0f/asdf-fd (or since it's been added to https://github.com/asdf-vm/asdf-plugins, asdf plugin-add fd will just work - this is what we do in CI).
comment created time in 11 days
pull request commentalumxi22/website
The asdf instructions are part of the base readme - are those instructions lacking? Of course, you can install all these tools out of band, but you run the risk of your dev environment diverging from CI's.
comment created time in 11 days
pull request commentalumxi22/website
In all honesty, I would prefer keeping fd. I write several tools using it, and keeping that consistency makes things a lot easier to maintain. In addition, fd has better defaults than find (example: respects gitignore patterns) that have bitten me a lot in the past. While find might be fine for this commit, I can easily see myself writing more helper scripts that would benefit a lot from using fd instead of find. (example: I'll need to setup a light typescript project inside this repo for the donation page's progress bar - that will require helper scripts for linting, building, formatting etc.).
What do you think about adding fd as another asdf requirement to the project readme? That's how it's currently installed for CI.
comment created time in 11 days
issue commentsourcegraph/sourcegraph
Distribution 3.21 Tracking issue
Last week:
- Heads down on preparing / updating deploy-sourcegraph-dhall-archived
This week:
- Record demo video for internal feedback
comment created time in 12 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
created branch time in 15 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
created branch time in 15 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
created branch time in 15 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
created branch time in 15 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
created branch time in 15 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
branch : indexed-search_generate
created branch time in 15 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
created branch time in 15 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
created branch time in 15 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
created branch time in 15 days
create barnchggilmore/deploy-sourcegraph-dhall-demo
created branch time in 15 days
pull request commentasdf-vm/asdf-plugins
Add asdf-plugin for the "just" command runner
Would someone be able to merge this in?
comment created time in 18 days
issue openedsourcegraph/sourcegraph
wip: create customer demo video for dhall direction
Sub-issues for these to be created
- [ ] Create fake fork of deploy-sourcegraph a with a few customizations
- [ ] Show migration process involving ds-to-dhall (involves using https://github.com/sourcegraph/deploy-sourcegraph-dhall-archived and doing to the work to get the output to match ds-to-dhall’s and updating that old repository with any changes in the services)
- [ ] Show incremental diffing process that drives the with statements to copy and paste (we can create a fake “docs” page that is just a text file)
- [ ] Show pipeline generating kubernetes yaml, and it being applied to a real cluster and working
- [ ] Show upgrade process
- [ ] Need to do the work to modify https://github.com/sourcegraph/deploy-sourcegraph-dhall-archived with a branch with updated images
This is for "the first half" of the 3.22 iteration
created time in 18 days
issue commentsourcegraph/sourcegraph
Distribution 3.21 Tracking issue
Last week:
-
Worked / solved an important customer issue: https://sourcegraph.slack.com/archives/CJX299FGE/p1601683378206300?thread_ts=1601389447.086900&cid=CJX299FGEE
-
Sync with @uwedeportivo about Dhall's state given the customer issue re-prioritization
Next week:
- Focus on preparing a demo for dhall to record for customers
comment created time in 18 days
push eventalumxi22/website
commit sha e0a4aa55e83f173f940deb51675b7cbfe48aa7c4
scripts: fix formatting
push time in 19 days
pull request commentalumxi22/website
enter some simple descriptions for events (take 2)
@nikomatsakis Do you have dhall installed on your machine?
Also, it's easier if you create a new branch off of this repository when submitting a PR instead of creating a fork. This allows the CI pipeline to run (I believe that you have write access).
comment created time in 19 days
issue commentsourcegraph/sourcegraph
Distribution 3.21 Tracking issue
this week:
- get spun on on working on the
symbolsservice for deploy-sourcegraph-dhall (Tuesday, Wednesday) - spent a lot of time on security (Thursday)
- spent a lot of time figuring out an important customer issue (Thursday, Friday)
next week:
- Hopefully there won't be as much task switching so that I can get back to working on dhall
comment created time in a month
startedpatrickf3139/fzf.fish
started time in a month
push eventsourcegraph/about
commit sha 5e88a462a25265c25605e9c0b7a58bd17b261eb5
add page to update sourcegraph.com tokens (#1696)
push time in a month
push eventsourcegraph/about
commit sha 1be3f1cdc330e2ec2e9519ed02a9f0ca41555f6f
add to index
push time in a month
push eventsourcegraph/deploy-sourcegraph-dhall
commit sha 29c28f9e910f1fbdf433ce21aba1642761f08dfb
ci: add sourcegraph prettier config (#5)
push time in a month
issue openedsourcegraph/sourcegraph
write instructions for how to modify sourcegraph.com's dhall generation pipleine
- dev environment setup
- structure of configuration object
- how to modify individual fields with
withstatements
created time in a month
issue openedsourcegraph/sourcegraph
write developer friendly documentation for deploy-sourcegraph-dhall architecture
- general layout of repository
- how do I add a new service?
- dev environment setup
- how do changes here get incorporated into sourcegraph.com
created time in a month
issue openedsourcegraph/sourcegraph
sourcegraph.com: write bot to incorporate image tag updates in dhall pipeline
- Renovate only updates YAML, but we want to enforce that the dhall generation pipeline is the source of truth
- We can't regress on sourcegraph.com running the sourcegraph/sourcegraph images
- We'll need to write a small tool that translates Kubernetes image definitions into the structured dhall representation (needed for modifications) e.x:
"index.sourcegraph.net/sourcegraph/frontend:insiders@sha256:123tsf"->{ name = "sourcegraph/frontend", tag = "insiders", digest = Some "123tsf", index = Some "index.sourcegraph.net" } - We'll need to run this tool after every renovate commit to 1) pick up the image tag change 2) modify the dhall generation pipeline to pick up this change 3) commit this change back to the repository (will be a no-op if the images don't change) 4) re-run the dhall generation pipeline to create the modified YAML files
created time in a month
issue openedsourcegraph/sourcegraph
- [ ] remove existing YAML Files
- [ ] add pipeline file that imports https://github.com/sourcegraph/deploy-sourcegraph-dhall with the necessary customization
- [ ] add CI check to verify that dhall and generated kubernetes YAML are synchronized
created time in a month
issue openedsourcegraph/sourcegraph
created time in a month
issue openedsourcegraph/sourcegraph
created time in a month
startedjef/nvidia-snatcher
started time in a month
issue commentsourcegraph/sourcegraph
Distribution 3.20 Tracking issue
last week:
- 3.21 Planning
- prepared Dhall proof of concept for architecture meeting
next week:
- pick services for sourcegraph.com dhall migration work
- identify substeps for each service (choose customizations, documentation, etc.)
comment created time in a month
push eventggilmore/ds-dhall-proto
commit sha 081d5b100e87e2683708973bc65542f61c6f3662
remove internal from deployment, use jaeger (#4)
push time in a month
push eventggilmore/ds-dhall-proto
commit sha 270a4cf2767c1575b8fff999b34c10a4c48cf870
handle security context
push time in a month
push eventggilmore/ds-dhall-proto
commit sha 18f7eb3cae73907b4619ab5e57795efa8e49671a
add short-cuts for demo (#3)
push time in a month
push eventggilmore/ds-dhall-proto
commit sha 7084c63a3593d0003a7af94f99f9003aaaabe258
build-prefix
push time in a month
push eventggilmore/ds-dhall-proto
commit sha 99f2dd843825c0f4a31ee8a3720d71148d135e43
more cleanup (#2)
push time in a month
push eventggilmore/ds-dhall-proto
commit sha 3011dd081f333b0f27b3377ac25593538daf4174
remove format, lint steps from just freeze
push time in a month
push eventggilmore/ds-dhall-proto
commit sha e3088a99539745b82cfed38f996a7d5ea583a480
ci: check -> freeze
push time in a month