Go in Linux Desktop Environment 2015年4月 夏彬 武汉深之度 Linux桌面环境 Gnome (Gtk) KDE (Qt) Lxde (Gtk) LxQt(Qt5) Xfce (Gtk) DDE (Gtk) ....... DE组件 Windows Manager Input Method Launcher Panel (dock)

#IstioCon Using ECC Workload Certificates (pilot-agent environmental variables) Jacob Delgado / Aspen Mesh #IstioCon ECC workload certificates ● In various environments, the need for x509 certificates feature ● Only ECDSA P-256 is supported #IstioCon pilot-agent environmental variables Disclaimer: Environmental variables and their use are considered experimental. There is no guarantee that they will environmental variables as used in this talk will continue to be supported through at least 1.10 to allow users to migrate towards this feature #IstioCon Other environmental variables There are many

Go runtime related problems in TiDB production environment About me ● Arthur Mao(毛康力), Senior Engineer@PingCAP ● TiDB core developer (top3 contributor) ● GitBook about golang internals (@tiancaiamao) not exhausted, but where is the bottleneck? Description ● The table is wide in the customer environment ○ CPU usage is higher with less columns ● The deployment does not consider NUMA ○ CPU usage is

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 10.4 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537 16.9 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 16 cmake generator is specified. This generator creates a conanbuildinfo.cmake file that defines CMake variables including paths and library names that can be used in our build. Read more about Generators. 5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 9.5 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 14.9 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 14 'implementation_name' is not defined. This issue seems to happen when using pip without a virtual environment. You can fix it by upgrading pip this way: $ curl https://bootstrap.pypa.io/get-pip.py -o get-pip

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 9.6 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 13.9 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 14 conanbuildinfo.cmake file that defines CMake variables including paths and library names that can be used in our build. To do so, include the generated file and add these variables to our CMakeLists.txt: 12 Chapter

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 9.5 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 14.9 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 14 'implementation_name' is not defined. This issue seems to happen when using pip without a virtual environment. You can fix it by upgrading pip this way: $ curl https://bootstrap.pypa.io/get-pip.py -o get-pip

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 10.4 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 16.9 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 16 cmake generator is specified. This generator creates a conanbuildinfo.cmake file that defines CMake variables including paths and library names that can be used in our build. Read more about Generators. 5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 12.4 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759 18.9 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 iii get(self, **self.conan_data["sources"][self.version], strip_root=True) When declaring the layout, the variables self.source_folder and self.build_folder will point to the correct folder, both in the cache or

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 12.4 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759 18.9 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 iii get(self, **self.conan_data["sources"][self.version], strip_root=True) Declaring the layout, the variables self.source_folder, self.build_folder will point to the correct folder, both in the cache or locally