Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Compilation failure

Open
#896 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
compilers

Research direction

Reproduce the failure from src/main.rs using typify::import_types! with the referenced devContainer.base.schema.json. Start by examining how typify handles the shown boolean/string schema with an enum, then identify the relevant compiler tests or schema fixtures. Done means the schema compiles without the proc macro panic and existing behavior remains covered by tests.

Written by the indexing model from the issue text.

Description

typify2
error: proc macro panicked
 --> src/main.rs:2:1
  |
2 | typify::import_types!("./src/devContainer.base.schema.json");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: message: not yet implemented: invalid (or unexpected) schema:
          {
            "description": "Indicates whether a GPU is required. The string \"optional\" indicates that a GPU is optional. An object value can be used to configure more detailed requirements.",
            "type": [
              "boolean",
              "string"
            ],
            "enum": [
              true,
              false,
              "optional"
            ]
          }

error: could not compile `foo` (bin "foo") due to 1 previous error

If you comment out https://github.com/devcontainers/spec/blob/113500f4125e0f14c9293adf4d8d94a861e0ec11/schemas/devContainer.base.schema.json#L454-L465 it compiles

Dominant language
Rust
Stars
898
Forks
114
Avg merge
4h 18m
Merged PRs (30d)
14

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oxidecomputer/typify

All issues in oxidecomputer/typify

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.