転職しました。長らくのご愛顧誠にありがとうございました。
転職先をちょくちょく探しています。
興味ある方は twitter @mizchi へのリプライorDM、または mizchi2w@gmail.com まで。
転職しました。長らくのご愛顧誠にありがとうございました。
転職先をちょくちょく探しています。
興味ある方は twitter @mizchi へのリプライorDM、または mizchi2w@gmail.com まで。
It is a script to convert a TypeScript library project to a Node.js Dual CommonJS/ES module packages.
This script aim to convert following project:
Kubernetes is a container orchestration platform and it has emerged as the de-facto tool for managing a large number of containers. In Kubernetes, networking functions, such as managing communication between applications and network policies, are delegated to CNI plugins.
Cilium is a CNI plugin for Kubernetes which provides secure network connectivity and load-balancing between applications using eBPF.
Cilium can manage network access by using network policy functions, called “CiliumNetworkPolicy” (CNP).
Users can allow or deny specific traffic by applying a CNP.
However, currently, any traffic except for TCP/UDP (including ICMP) is denied if an L4 CNP is present, and there is no way for users to explicitly allow ICMP traffic.
Therefore, my project aims to implement a CNP for explicitly allowing ICMP traffic.
This can reduce files to ~15% of their size (2.3M to 345K, in one case) with no obvious degradation of quality.
ghostscript -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/printer -dNOPAUSE -dQUIET -dBATCH -sOutputFile=output.pdf input.pdf
Other options for PDFSETTINGS:
func openbrowser(url string) { | |
var err error | |
switch runtime.GOOS { | |
case "linux": | |
err = exec.Command("xdg-open", url).Start() | |
case "windows": | |
err = exec.Command("rundll32", "url.dll,FileProtocolHandler", url).Start() | |
case "darwin": | |
err = exec.Command("open", url).Start() |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j