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

KDIVE v2

Is randomparity/kdive beginner-friendly?

The maintainers of randomparity/kdive usually reply to a pull request within 1 day. 1 beginner-friendly issue is open now.

Stars
0
Forks
0
Open beginner issues
1
Indexed issues
260
Avg merge
2h 45m
Merged PRs (30d)
357
Dominant language
Python
License
Apache-2.0
Last GitHub push
Sep 16, 2026
Latest indexed
Sep 17, 2026
Contributing guide
Contributing guide
Code of conduct
Code of conduct
Beginner labels
good first issue

How to contribute to randomparity/kdive

  1. Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
  2. Read its code of conduct: it covers issues and pull requests as well as chat.
  3. Your contributions will be published under the project's Apache-2.0 license.
  4. Pick the open beginner-friendly issue below and comment that you want to work on it before you start.

Issues somebody may already be working on are listed last. List everything by date

  • SUSE host preparation fails: libvirt default network is never defined
    Open
    area:provisioning effort:S priority:P2 provider:local-libvirt risk:daytime-only status:in-progress type:bug

    Difficulty 2/5 1-3 hours Newbie friendliness 78/100

    randomparity/kdive#3203 · 2 comments ·

    Maintainers usually reply within 1 day

  • Qualify the 32 blocked authority HTTP functional tool cells
    Open
    area:providers effort:M priority:P2 risk:daytime-only status:ready type:test

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    randomparity/kdive#3186 ·

    Maintainers usually reply within 1 day

  • Construct bounded authority recovery orphans and conflicts for live proof
    Open
    area:providers effort:M priority:P2 risk:daytime-only status:ready type:test

    Difficulty 5/5 Over a week Newbie friendliness 22/100

    randomparity/kdive#3185 ·

    Maintainers usually reply within 1 day

  • Frame and clean up authority-owned Systems for HTTP tool cells
    Open
    area:providers effort:M priority:P2 risk:daytime-only status:ready type:test

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    randomparity/kdive#3184 ·

    Maintainers usually reply within 1 day

  • Epic: Live lane with an installed provider authority for authority-owned tool cells
    Open
    area:providers effort:L priority:P2 status:ready type:test

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    randomparity/kdive#3152 ·

    Maintainers usually reply within 1 day

  • Local authority System identity never matches libvirt's canonical machine name
    Open
    area:provisioning effort:M priority:P1 provider:local-libvirt status:blocked type:bug

    Difficulty 4/5 3-5 days Newbie friendliness 45/100

    randomparity/kdive#3148 ·

    Maintainers usually reply within 1 day

  • runs.install routes a fixed-worker System to the external-boot authority and strands its allocation
    Open
    area:build-install effort:S priority:P1 provider:local-libvirt status:blocked type:bug

    Difficulty 4/5 3-5 days Newbie friendliness 48/100

    randomparity/kdive#3138 · 7 comments ·

    Maintainers usually reply within 1 day

  • Prove vmlinux staging live through the external-boot authority on x86_64
    Open
    area:debug effort:M priority:P2 status:blocked type:test

    Difficulty 4/5 3-5 days Newbie friendliness 38/100

    randomparity/kdive#3135 ·

    Maintainers usually reply within 1 day

  • Stage or explicitly refuse the vmlinux in the remote-libvirt external-boot authority
    Open
    area:debug effort:M priority:P1 provider:remote-libvirt risk:daytime-only status:blocked type:feature

    Difficulty 4/5 3-5 days Newbie friendliness 48/100

    randomparity/kdive#3131 ·

    Maintainers usually reply within 1 day

  • Check guest free space before writing the uploaded vmlinux
    Open
    area:provisioning effort:S priority:P2 risk:night-watch status:blocked type:bug

    Difficulty 3/5 1-2 days Newbie friendliness 48/100

    randomparity/kdive#3125 ·

    Maintainers usually reply within 1 day

  • Deliver the uploaded vmlinux to remote-libvirt guests
    Open
    area:debug area:provisioning effort:M priority:P1 provider:remote-libvirt risk:daytime-only status:blocked type:feature

    Difficulty 4/5 3-5 days Newbie friendliness 52/100

    randomparity/kdive#3124 ·

    Maintainers usually reply within 1 day

  • Catalog drgn_version pins drift from the drgn installed in built images
    Open
    area:build-install effort:S priority:P3 risk:night-watch status:ready type:bug

    Difficulty 3/5 1-2 days Newbie friendliness 68/100

    randomparity/kdive#3122 ·

    Maintainers usually reply within 1 day

  • drgn-live capability assumes guest drgn reads kernel BTF; no released drgn does
    Open
    area:debug effort:M priority:P1 risk:daytime-only status:ready type:bug verification:ppc64le verification:x86

    Difficulty 4/5 3-5 days Newbie friendliness 47/100

    randomparity/kdive#3121 · 1 comment ·

    Maintainers usually reply within 1 day

  • Prove orchestration failure recovery on x86_64 libvirt
    Open
    effort:L priority:P1 status:blocked type:test

    Difficulty 4/5 3-5 days Newbie friendliness 32/100

    randomparity/kdive#3117 · 1 comment ·

    Maintainers usually reply within 1 day

  • Prove the remote power, snapshot and traffic tool cells on x86_64
    Open
    effort:L priority:P1 status:blocked type:test

    Difficulty 5/5 Over a week Newbie friendliness 30/100

    randomparity/kdive#3116 · 1 comment ·

    Maintainers usually reply within 1 day

  • Prove local traffic capture, SysRq and crash-watch tool cells
    Open
    effort:M priority:P1 status:blocked type:test

    Difficulty 4/5 3-5 days Newbie friendliness 48/100

    randomparity/kdive#3115 · 1 comment ·

    Maintainers usually reply within 1 day

  • Prove the remote capture and introspection tool cells on x86_64
    Open
    effort:L priority:P1 status:blocked type:test

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    randomparity/kdive#3114 · 1 comment ·

    Maintainers usually reply within 1 day

  • Prove the remote debug tool cells on x86_64
    Open
    effort:L priority:P1 status:blocked type:test

    Difficulty 5/5 Over a week Newbie friendliness 30/100

    randomparity/kdive#3113 · 1 comment ·

    Maintainers usually reply within 1 day

  • Prove build-use recovery tools on a Docker worker-death lane
    Open
    effort:M priority:P1 status:blocked type:test

    Difficulty 4/5 3-5 days Newbie friendliness 52/100

    randomparity/kdive#3111 · 2 comments ·

    Maintainers usually reply within 1 day

  • Exercise mutating operator inventory and queue tools over HTTP
    Open
    effort:L priority:P1 status:blocked type:test

    Difficulty 4/5 3-5 days Newbie friendliness 45/100

    randomparity/kdive#3110 · 2 comments ·

    Maintainers usually reply within 1 day

  • Account CLI translation in the coverage contract for core MCP tools
    Open
    effort:M priority:P2 risk:daytime-only status:blocked type:test

    Difficulty 4/5 3-5 days Newbie friendliness 45/100

    randomparity/kdive#3099 · 2 comments ·

    Maintainers usually reply within 1 day

  • Exercise allocation, accounting and report MCP tools with valid real-service state
    Open
    effort:L priority:P1 risk:daytime-only status:blocked type:test

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#3098 · 3 comments ·

    Maintainers usually reply within 1 day

  • Exercise run, system and job MCP tools with valid real-service state
    Open
    effort:L priority:P1 risk:daytime-only status:blocked type:test

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    randomparity/kdive#3097 · 3 comments ·

    Maintainers usually reply within 1 day

  • Verify just test-linux with Podman on macOS
    Open
    effort:M priority:P3 risk:daytime-only status:ready type:test

    Difficulty 4/5 3-5 days Newbie friendliness 64/100

    randomparity/kdive#3074 ·

    Maintainers usually reply within 1 day

  • Schedule the matrix and enforce release qualification in both publication paths
    Open
    effort:L priority:P1 status:blocked type:test

    Difficulty 5/5 Over a week Newbie friendliness 30/100

    randomparity/kdive#2819 ·

    Maintainers usually reply within 1 day

  • Verify the established matrix on native ppc64le and documented TCG paths
    Open
    effort:L priority:P1 status:blocked type:test verification:ppc64le

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    randomparity/kdive#2818 ·

    Maintainers usually reply within 1 day

  • Qualify two deterministic broken/fixed kernel exercises
    Open
    effort:M priority:P1 status:blocked type:test

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#2817 · 1 comment ·

    Maintainers usually reply within 1 day

  • Prove power, snapshot and traffic commands through the full stack
    Open
    effort:M priority:P1 status:blocked type:test

    Difficulty 5/5 Over a week Newbie friendliness 30/100

    randomparity/kdive#2815 · 3 comments ·

    Maintainers usually reply within 1 day

  • Prove crash capture, live introspection and postmortem tool outcomes
    Open
    effort:M priority:P1 status:blocked type:test

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#2814 · 3 comments ·

    Maintainers usually reply within 1 day

  • Prove the GDB command surface with real kernels
    Open
    effort:M priority:P1 status:blocked type:test

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#2813 · 2 comments ·

    Maintainers usually reply within 1 day

  • introspect.from_vmcore fails on ppc64le: libkdumpfile cannot translate Book3S-64 vmalloc
    Open
    area:debug effort:M priority:P1 risk:daytime-only status:ready type:bug

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#2763 · 1 comment ·

    Maintainers usually reply within 1 day

  • Reports: reconciler sweep that enqueues due report runs
    Open
    area:core-platform effort:M priority:P2 status:blocked type:feature

    Difficulty 4/5 3-5 days Newbie friendliness 50/100

    randomparity/kdive#2729 ·

    Maintainers usually reply within 1 day

  • Reports: history tools reports.list and reports.get
    Open
    area:mcp-api area:security effort:M priority:P2 status:blocked type:feature

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#2728 ·

    Maintainers usually reply within 1 day

  • Reports: per-subscription retention in report GC
    Open
    area:core-platform effort:S priority:P2 status:blocked type:feature

    Difficulty 4/5 3-5 days Newbie friendliness 48/100

    randomparity/kdive#2727 ·

    Maintainers usually reply within 1 day

  • Reports: period-over-period trends
    Open
    area:core-platform effort:M priority:P2 status:blocked type:feature

    Difficulty 4/5 3-5 days Newbie friendliness 45/100

    randomparity/kdive#2726 ·

    Maintainers usually reply within 1 day

  • Reports: tool coverage gap section
    Open
    area:mcp-api effort:S priority:P2 status:blocked type:feature

    Difficulty 3/5 1-2 days Newbie friendliness 48/100

    randomparity/kdive#2725 ·

    Maintainers usually reply within 1 day

  • Reports: service-layer report pipeline and REPORT_GENERATE worker job
    Open
    area:core-platform effort:L priority:P2 status:blocked type:feature

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#2724 ·

    Maintainers usually reply within 1 day

  • Reports: subscription tools (subscribe, list, unsubscribe, renew)
    Open
    area:mcp-api area:security effort:M priority:P2 status:blocked type:feature

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#2723 ·

    Maintainers usually reply within 1 day

  • Reports: tool usage section
    Open
    area:mcp-api area:security effort:M priority:P2 status:ready type:feature

    Difficulty 4/5 3-5 days Newbie friendliness 62/100

    randomparity/kdive#2722 ·

    Maintainers usually reply within 1 day

  • Reports: ADR + schema for report subscriptions and report runs
    Open
    area:core-platform area:security effort:M priority:P2 status:ready type:feature

    Difficulty 4/5 3-5 days Newbie friendliness 48/100

    randomparity/kdive#2721 ·

    Maintainers usually reply within 1 day

  • Epic: scheduled usage/cost reports with tool-usage, trend, and coverage content
    Open
    epic

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#2720 ·

    Maintainers usually reply within 1 day

  • Durable external-build finalization when single-flight is not enough (multi-replica, restart)
    Open
    area:build-install area:mcp-api effort:L priority:P3 risk:daytime-only status:blocked type:feature

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    randomparity/kdive#2681 · 2 comments ·

    Maintainers usually reply within 1 day

  • Add MCP elicitation for confirmation before mutating and destructive tool calls
    Open
    area:mcp-api area:security effort:L priority:P2 risk:daytime-only status:ready type:feature

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#2474 ·

    Maintainers usually reply within 1 day

  • EEH Error Injection Support for ppc64le on PowerVM
    Open
    risk:night-watch status:ready type:feature verification:ppc64le

    Difficulty 5/5 Over a week Newbie friendliness 20/100

    randomparity/kdive#1959 ·

    Maintainers usually reply within 1 day

  • Define the read scope for the Host Interface posture in byo_adopt_facts
    Open
    area:mcp-api area:security effort:S priority:P2 provider:baremetal-bmc risk:daytime-only status:blocked type:spec

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#1896 ·

    Maintainers usually reply within 1 day

  • Decide whether teardown takes a second Host Interface observation
    Open
    area:providers area:security effort:S priority:P3 provider:baremetal-bmc risk:daytime-only status:blocked type:spec

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#1895 ·

    Maintainers usually reply within 1 day

  • Record BMC and BIOS firmware versions on the System at adopt
    Open
    area:providers effort:S priority:P3 provider:baremetal-bmc risk:daytime-only status:ready type:feature

    Difficulty 3/5 1-2 days Newbie friendliness 68/100

    randomparity/kdive#1846 ·

    Maintainers usually reply within 1 day

  • Capture BMC hardware event signals (SEL, thermtrip, prochot) when a System fails unexplained
    Open
    area:control-retrieve effort:M priority:P3 provider:baremetal-bmc risk:daytime-only status:blocked type:feature

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    randomparity/kdive#1845 ·

    Maintainers usually reply within 1 day

  • Redfish driver must handle vendor-divergent writes: If-Match, AMI FutureState URI, pending-settings
    Open
    area:providers effort:M priority:P2 provider:baremetal-bmc risk:night-watch status:blocked type:feature

    Difficulty 4/5 3-5 days Newbie friendliness 48/100

    randomparity/kdive#1844 · 1 comment ·

    Maintainers usually reply within 1 day

  • Verify the IPMI diagnostic interrupt and watchdog pre-timeout NMI on crashable x86 hardware
    Open
    area:control-retrieve effort:S priority:P1 provider:baremetal-bmc risk:daytime-only status:needs-human type:test verification:x86

    Difficulty 5/5 Over a week Newbie friendliness 30/100

    randomparity/kdive#1843 ·

    Maintainers usually reply within 1 day

Showing the newest 100

This page lists what was indexed most recently. Advanced filter has the whole inventory, narrowed by language, difficulty and how long a task takes.

Open advanced filter

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.