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

Fix benchmark, profiler, and CLI exit-code quirks found in the 0.14 docs audit

Open
#1,279 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active

Research direction

Reproduce the listed cases around GocciaBenchmarkRunner, the --profile and --mode options, host grants, usage-error flags, and GocciaBundler output handling. Treat the bullets as independent fixes and verify each expected exit code, error class, warning, profile total, and output-directory behavior before considering the issue done.

Written by the indexing model from the issue text.

Description

engine

Summary

Smaller CLI, benchmark and profiler issues. Found in the 0.14.0 docs audit.

Current behavior

  • GocciaBenchmarkRunner exits 0 when an input file fails to load.
  • --profile=functions reports an inflated total time (131 s for a run of about 14 ms), likely recursive double-counting.
  • --profile=all --mode=interpreted silently runs bytecode. The mode switch is documented for --profile, but no warning mentions that it overrode an explicit --mode.
  • --profile-format=flamegraph with --profile=opcodes exits 0 and writes an empty file.
  • Shortened IPv4 host literals under a net grant (127.1, 0x7f.0.0.1) fail with TypeError: Failed to resolve host rather than PermissionDenied. They are refused as intended, but with a different error class.
  • Inconsistent exit codes. --host-environment combined with --deterministic, and a bare --allow-import, exit 1, where other usage errors exit 2.
  • GocciaBundler --output=dist/x.gbc fails unless dist/ exists, and the directory-target cases give misleading errors.

Expected behavior

  • A load failure makes the benchmark runner exit non-zero.
  • Profile totals are correct.
  • An explicit --mode either wins or triggers a warning.
  • A flamegraph with no stacks is a usage error.
  • Shortened IPv4 hosts get PermissionDenied.
  • Usage errors consistently exit 2.
  • The bundler creates the output directory or reports clearly that it's missing.

Scope notes

Each is independent.

Dominant language
Pascal
Stars
20
Forks
3
Avg merge
3d 21h
Merged PRs (30d)
51

Getting set up

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 frostney/GocciaScript

All issues in frostney/GocciaScript

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.