Table of Contents
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
| #!/usr/bin/env bash | |
| export DEBIAN_FRONTEND=noninteractive | |
| set -e | |
| set -o pipefail | |
| git clone [email protected]:openscad/openscad.git | |
| cd openscad |
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
| I have to say - as the developer of such "insecure" extension (Chrome-Emacs), I'm baffled by this "insecure” label. Every time I update my add-on, I submit the full source code and detailed instructions, yet it seems that no one ever really looks at what I provide. It feels like my work is automatically dismissed, and I'm being penalized just because it didn't go through some manual review process I can't even influence. | |
| What exactly does "actively monitored” mean? If my extension were truly dangerous, this would be highlighted with concrete evidence or specific criteria. Instead, it simply gets tagged with a warning that nothing more is expected from me. It's hard not to feel brushed aside by a process that appears to rely more on automated checks than genuine security evaluations. | |
| I'm all for keeping users safe, but by lumping all non-"Recommended” extensions into the same category, it feels like you're ignoring the effort and transparency many developers like me put into our work. Clear guidance on how to |
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
| I have to say - as the developer of such "insecure" extension (Chrome-Emacs), I'm baffled by this "insecure” label. Every time I update my add-on, I submit the full source code and detailed instructions, yet it seems that no one ever really looks at what I provide. It feels like my work is automatically dismissed, and I'm being penalized just because it didn't go through some manual review process I can't even influence. | |
| What exactly does "actively monitored” mean? If my extension were truly dangerous, this would be highlighted with concrete evidence or specific criteria. Instead, it simply gets tagged with a warning that nothing more is expected from me. It's hard not to feel brushed aside by a process that appears to rely more on automated checks than genuine security evaluations. | |
| I'm all for keeping users safe, but by lumping all non-"Recommended” extensions into the same category, it feels like you're ignoring the effort and transparency many developers like me put into our work. Clear guidance on how to |
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
| module debug_polygon(points, paths=undef, convexity=undef, debug=false, | |
| arrow_size=1, font_size=4, font_color="red", | |
| show_arrows=true) { | |
| polygon(points=points, paths=paths, convexity=convexity); | |
| if (debug) { | |
| for (i = [0 : len(points) - 1]) { | |
| pt = points[i]; |
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
| (defvar km-tailwind-candidates nil) | |
| (defun km-tailwind--serialize (data filename) | |
| "Serialize DATA to FILENAME. | |
| The saved data can be restored with `km-tailwind--unserialize'." | |
| (when (file-writable-p filename) | |
| (with-temp-file filename | |
| (insert |
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
| #!/bin/sh | |
| # Uninstall the pre-existing "opencv-python" package, if any, which may have been installed as a pre-built binary | |
| pip uninstall opencv-python -y | |
| # Install essential dependencies for compiling OpenCV with desired features | |
| # These include tools for building software (build-essential, cmake, python3-dev) | |
| # and libraries for multimedia (GStreamer, FFmpeg, libav), image I/O (libpng, libjpeg, libtiff, etc.), | |
| # GUI functionality (libgtk-3-dev), and Python bindings (python3-numpy). | |
| sudo apt install build-essential cmake git python3-dev python3-numpy \ |
This guide will help you set up your Raspberry Pi to connect via WiFi and SSH and run your robot (Pidog or Picar-X). For most steps, we'll use the Raspberry Pi GUI to keep things beginner-friendly. If you're comfortable with advanced tools, there’s a secret advanced section for configuring wpa_supplicant directly.
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
| # #!/usr/bin/env python3 | |
| from picarx import Picarx | |
| from vilib import Vilib | |
| from time import sleep, time, strftime, localtime | |
| import readchar | |
| from robot_hat.utils import reset_mcu | |
| from robot_hat import Music | |
| from os import geteuid, getlogin, path | |
| from google_speech import Speech |
NewerOlder