getappmap / getappmap/appmap-js
Refuse to install on unsupported rubies
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
We currently don't run on JRuby; appmap uses native components and they rely on MRI internals. While it could work on other MRI-derived Rubies, it definitely won't run on others, especially running in a managed environment like JRuby or IronRuby, We should probably check for this in the installer and abort.
Also, we're seeing users trying to install on eg. Ruby 2.3.8. This version is almost four years past end of life. It'd be good to balk or at least warn if the version is too old. (2.3.8 definitely does not work.)
Contributor guide
No contributing guide indexed for this repository
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 locating the installer and its existing Ruby version or runtime checks; the issue names no files or tests. The work is done when unsupported managed Rubies are refused and sufficiently old Ruby versions, including 2.3.8, are handled with the agreed failure or warning behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100