ScottW514 a10fd7782d forgetest: the hash cases hold what a test's own import imports in turn, and the guard refuses an absolute package import
No case held the step of implementation_sha that adds what a test's own
import imports in turn (`sibling_imports(sib, sibs)`), nor the
recursion in sibling_imports itself: the judge.py of
test_a_sibling_imported_inside_a_function_moves_the_tests_that_run_it
imports nothing. Either line deleted kept test_manifest.py green, while
on the real catalog the first drops motion.py's shared text from
cloud.mode-switch's hash and setup.py's from motion.release's. The guard
on the suite's package imports read the relative spelling alone: a
`from forgetest import server`, an `import forgetest.server`, or a
`from forgetest.suite.setup import ...` in a suite module passed it,
and the sibling walk does not follow any of them, so the module they
name joined no hash.

The case's judge.py now imports limit.py, which imports base.py: an
edit to either moves m.two and not m.one. The guard refuses any import
of the package by its absolute name in a suite module, at any depth.
No suite module imports the package that way. catalog.py does not change.

Proof: forgetest-ci "Unit tests" (`python -B -m unittest discover -s
tests -v` in forgetest): test_manifest.py runs 39 tests, OK, on Windows
with python 3.14 and on Ubuntu 24.04 with python 3.12. Negative
controls on scratch copies: catalog.py without `sibling_imports(sib,
sibs)` in implementation_sha fails the case at the limit.py edit; the
walk without its recursion fails it at the base.py edit; in
suite/forgectrl.py, a `from forgetest import server` and an `import
forgetest.server` inside a function, and forgectrl.auth's import of
setup.py spelled `from forgetest.suite.setup import request, decode`,
each fail the guard. pyflakes reports no undefined name.

Acceptance: none. tests/ are in no fingerprint (source_sha of 43 of 43
unchanged).
2026-10-16 23:45:25 -04:00
2026-09-18 12:14:22 -04:00
2026-10-10 19:45:32 -04:00
2026-09-14 10:39:08 -04:00
2026-09-18 12:50:11 -04:00
2026-09-18 12:50:11 -04:00
2026-09-08 16:21:37 -04:00
2026-09-18 12:14:22 -04:00
2026-10-06 15:59:31 -04:00

OpenGlow / ForgeFIRM firmware for Glowforge

BETA

ForgeFIRM is in beta. Every release below 0.1.0 is a beta release. It's stable, but you may still hit the occasional bug, and expect frequent updates. Upgrade whenever a newer release is available, and report what you find on the community forum.

Open firmware for Glowforge brand CNC lasers. ForgeFIRM replaces the cloud-dependent factory software on the stock control board, with no hardware modification, and gives the machine a local controller, a local web control panel, and a standard Grbl interface. The factory cloud experience stays available as an option.

This repository is the base of the build and of the release: the meta-forgefirm Yocto layer, the kas configuration, the image recipes, the install and release scripts, the acceptance tool (forgetest/), the bench tools (scripts/bench/), the bench actuator firmware (fixture/), and the release artifacts (releases/).

Start here

https://docs.forgefirm.org/ is the documentation, and the source of truth for every fact about the machine and the firmware.

Read this first Safety
Put it on a machine Installation
Use it Usage, LightBurn
How the machine works Technical
How ForgeFIRM works with it ForgeFIRM internals
Build, test, release Developers
Downloads Releases
Questions Community forum

Build

kas build kas/forgefirm-glowforge.yml

Build covers the host setup, the two images, the source variant and the debug kernel. Release flow covers the pins, the push order and the signing pipeline.

Test

cd forgetest && python3 -m unittest discover -s tests -v

The acceptance catalog that gates a release, and the bench tools, are on Acceptance and The bench.

Contributing

AGENTS.md carries the rules for this repository and for the project: safety ordering, proof before done, the push order, and the writing rules. They apply to human contributors too, and Contribute is the same set on the site.

What this costs

Nothing. ForgeFIRM is free in both senses, under MIT and GPL licenses. There is no paid tier, no license key, no subscription and no Pro edition. If someone offers to sell it to you, the licenses allow it, but what you take home is their build rather than this one: get it from the source.

Safety

These machines contain a CO2 laser: it burns, blinds, and starts fires. Never defeat the lid switches or the interlock. Never leave a running job unattended. Keep a fire extinguisher within reach. Read Safety before you cut your first job, and Regulatory and legal before you install.

This is experimental software. Use of it could seriously maim or kill you or others, and it may void your warranty. Use it at your own risk.

Glowforge is a trademark of Glowforge, Inc. This project is not affiliated with, authorized by, or endorsed by Glowforge, Inc.

S
Description
OpenGlow/ForgeFIRM Firmware for Glowforge
Readme
7.1 MiB
Languages
Python 87.7%
Shell 4.7%
BitBake 3.2%
C 1.5%
JavaScript 1.4%
Other 1.5%