jrsteensen/OpenHornet

[Bug]: In the release package, left and right inboard console trim (ALU) are missing

Closed

#1,134 opened on Feb 17, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)Python (137 forks)github user discovery
Category: MCADPriority: NormalType: Bug/ObsolesceType: Documentationgood first issue

Repository metrics

Stars
 (418 stars)
PR merge metrics
 (Avg merge 6d 13h) (7 merged PRs in 30d)

Description

Discord Username

Ulukaii

Bug Summary

In the Github release folder, left console and right console, the parts

"OH4A1A1-43" (left console inboard forward trim) and "OH5A1A1-42" (right console inboard forward trim)

are missing.

Expected Results

I expect that in the release package, manufacturing folder, the parts mentioned above are present.

Actual Results

The parts are not in the manufacturing folder.

Screenshots/Images/Files

Applicable Part Numbers

OH5A1A1-42, OH4A1A1-43

Release Version

v0.2.0

Category

Mechanical (Structure/Panels/Mechanisms)

Applicable End Item(s)

Left Console (LCON), Right Console (RCON)

Built to print?

  • I built (or attempted to build) the part to the OpenHornet print without any deviations.
  • I am not building this part to the OH print. (List deviations in detail in the Miscellaneous Info text area below.)

Miscellaneous Info

No response

Contributor guide

Research direction
Inspect the release package for version v0.2.0 and compare the manufacturing folder contents with the source to identify why parts OH4A1A1-43 and OH5A1A1-42 are missing. Check if they were omitted from the release script or if the source files are missing.
Tech stack
None
Domain
release
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75