Warning: /Users/lap00828/projects/ops-delivery/lastmile/driverbee/location_query_lazy.go:16:6: using struct literal to inject github.com/tikivn/ops-delivery/lastmile/driverbee.LocationQueryLazy is deprecated and will be removed in the next release; use wire.Struct instead, see https://godoc.org/github.com/google/wire#Struct for more information.
Warning: /Users/lap00828/projects/ops-delivery/internal/infra/app/app.go:39:6: using struct literal to inject github.com/tikivn/ops-delivery/internal/infra/app.ApplicationContext is deprecated and will be removed in the next release; use wire.Struct instead, see https://godoc.org/github.com/google/wire#Struct for more information.
wire: /Users/lap00828/projects/ops-delivery/internal/infra/infra.go:37:22: cycle for github.com/looplab/eventhorizon.CommandHandler:
github.com/looplab/eventhorizon.CommandHandler (github.com/tikivn/ops-delivery/internal/infra.ProvideCommandBus) ->
github.com/tikivn/ops-delivery/internal/infra.MasterboxHandler (github.com/tikivn/ops-de
Để start chrome headless trên ubuntu
# this script will start chrome headless that hold state of your real browser (cookie, session...)
# note that user-data-dir "/home/debug/.config/google-chrome/Default" is wrong (remove /Default)
/opt/google/chrome/chrome --headless \
--remote-debugging-port=9222 \
--user-agent="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.89 Safari/537.36" \
--user-data-dir="/home/debug/.config/google-chrome"
# restore mongo
Step1: https://ostechnix.com/how-to-fix-broken-ubuntu-os-without-reinstalling-it/
Step2: https://askubuntu.com/questions/765842/i-only-have-one-resolution-640x480-desktop-looks-zoomed-in
Step3: https://askubuntu.com/questions/1033368/gnome-lags-so-bad-on-ubuntu-18-04
Step1:
$ sudo rm /var/lib/apt/lists/lock
Rabbitmq is a message broker
- `<` file 1 | |
- `>` file 2 |
- Hệ số nhị thức (Binomial coeffient) https://en.wikipedia.org/wiki/Binomial_coefficient
Ta cần viết ra các trường hợp có thể xảy của http response:
- Trường hợp không thể kết nối tới server, việc xử lý nằm ở client. Nếu đã kết nối được tới server, mọi response trả về phải có định nghĩa schema rõ ràng
Vấn đề phát sinh khi dùng grpc-gateway đó là làm sao để thông báo error message tới user rõ ràng nhất.
Thông thường khi làm việc với GRPC, ta sẽ dùng grpc-gateway làm công cụ để sinh ra client, và server stuff.
Việc xử lý logic của API sẽ nằm trong GRPC handlers, nó có dạng như sau:
Special macros:
- $@ is the name of the file to be made
- $? is the name of changed depandents
- $< the name of related file that caused the action
- $* the prefix shared by target and dependent files
-
8k:
https://blog.usejournal.com/lean-testing-or-why-unit-tests-are-worse-than-you-think-b6500139a009
- >1k:
https://medium.com/pacroy/why-most-unit-testing-is-waste-tests-dont-improve-quality-developers-do-47a8584f79ab