~ruther/qmk_firmware

0fcd13f5 — Nick Brassel 1 year, 6 months ago
[CLI] Remove duplicates from search results (#22528)

7ae82647 — Joel Challis 1 year, 6 months ago
Move BACKLIGHT_PWM_PERIOD to correct docs section (#22480)

46b996a5 — Nick Brassel 1 year, 6 months ago
CLI parallel search updates (#22525)

7e27d72c — Sergey Vlasov 1 year, 6 months ago
Fix `qmk find` failure due to circular imports (#22523)

There was an import cycle in the Python modules:

  - `qmk.build_targets` imported `qmk.cli.generate.compilation_database`;
  - importing `qmk.cli.generate.compilation_database` requires
    initializing `qmk.cli` first;
  - the initialization of `qmk.cli` imported the modules for all CLI
    commands;
  - `qmk.cli.compile` imported `qmk.build_targets`.

This cycle did not matter in most cases, because `qmk.cli` was imported
first, and in that case importing `qmk.cli.generate.compilation_database`
did not trigger the initialization of `qmk.cli` again.  However, there was
one corner case when `qmk.bulld_targets` was getting imported first:

  - The `qmk find` command uses the `multiprocessing` module.
  - The `multiprocessing` module uses the `spawn` start method on macOS
    and Windows.
  - When the `spawn` method is used, the child processes initialize
    without any Python modules loaded, and the required modules are loaded
    on demand by the `pickle` module when receiving the serialized objects
    from the main process.

The result was that the `qmk find` command did not work properly on macOS
(and probably Windows too); it reported exceptions like this:

    ImportError: cannot import name 'KeyboardKeymapBuildTarget' from partially initialized module 'qmk.build_targets' (most likely due to a circular import)

Moving the offending `qmk.cli.generate.compilation_database` import into
the method which actually uses it fixes the problem.
Azoteq IQS5xx support (#22280)

LED drivers: register naming cleanups (#22436)

e279c78b — Joel Challis 1 year, 6 months ago
Enable linking of encoders to switch within layout macros (#22264)

62cca5c4 — Sergey Vlasov 1 year, 6 months ago
`qmk find`: Fix failure with multiple filters (#22497)

When multiple `-f FILTER` options were specified, `qmk find` did not
return anything at all instead of printing the list of entries that
matched all of the specified filters.

The problem was that the statement in `_filter_keymap_targets()` that
filled `targets` had a wrong indent and therefore was executed for every
filter instead of only once after applying all filters, and
`valid_keymaps` was actually an iterator and therefore could be used
only once.  Moving the statement outside of the loop fixes the problem.
Merge remote-tracking branch 'origin/master' into develop
a6521b85 — フィルターペーパー 1 year, 6 months ago
[Doc] Improve converter references (#21801)

Merge remote-tracking branch 'origin/master' into develop
[Keyboard] Add dnworks 997pt3 (#22466)

Co-authored-by: Less/Rikki <86894501+lesshonor@users.noreply.github.com>
Co-authored-by: Duncan Sutherland <dunk2k_2000@hotmail.com>
Merge remote-tracking branch 'origin/master' into develop
Add leonardo build target for leonardo + usb2.0 shield based projects (#22243)

49382107 — Nick Brassel 1 year, 6 months ago
CLI refactoring for common build target APIs (#22221)

Merge remote-tracking branch 'origin/master' into develop
[Keyboard] Add Eden (#22467)

Co-authored-by: Duncan Sutherland <dunk2k_2000@hotmail.com>
Merge remote-tracking branch 'origin/master' into develop
5c227062 — Nick Brassel 1 year, 6 months ago
Update stale.yml
Merge remote-tracking branch 'origin/master' into develop
Next
Do not follow this link