NatLabRockies / NatLabRockies/OpenStudio
Gem_path Priority on Mac Doesn't Seem to Work
Open
Nobody has claimed this yet.
component - CLI
severity - Normal Bug
- Dominant language
- C++
- Stars
- 646
- Forks
- 237
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 10
Description
On Mac, when specifying a gem_path through the cli, it uses the built in gems rather than newer versions of the gems specified in the gem_path. For example, building openstudio-standards 0.2.3 in the gem_path specified doesn't overwrite OpenStudio's gem priority to use that version rather than the built in openstudio-standards 0.2.2.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue through the OpenStudio CLI on Mac with a gem_path containing a newer openstudio-standards version. Trace the CLI's gem priority handling; it is done when the specified newer gem is selected instead of the built-in version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100