Mitigation of Scala reflection bugs (Symbols#CyclicReference, RuntimeException("scala signature"), ...)

Open
  • Is something wrong?
#125 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
scala
Domain
tooling

Research direction

Start by reviewing Scala bug 12190 and AbsaOSS issues 80 and 82 to understand the listed reflection failures. Then investigate the repository's reflection call and determine how the issue should distinguish genuine errors from Scala bugs; the issue is done when that mitigation and error distinction are defined and covered.

Written by the indexing model from the issue text.

Description

Various Scala bugs may be a cause of failed reflection call:

We should try to isolate the user from those bugs. It is a question how to do this, but we should make it clear when there is an actual error and when the cause of the issue was a bug in Scala.

Dominant language
Scala
Stars
11
Forks
1
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 AbsaOSS/commons

All issues in AbsaOSS/commons

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.