twitter/finagle

Don't mess with class loaders... or do it gently

Open

#357 opened on Apr 1, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Scala (1,435 forks)batch import
good first issue

Repository metrics

Stars
 (8,864 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Issue is described in following thread: https://groups.google.com/forum/#!topic/finaglers/snRvOYwljbI Basically Play's auto-reloading breaks Finagle's reflection based API. Also @jproper gives good explanation of what's going on and how to fix it here: https://github.com/playframework/playframework/issues/4159

Contributor guide

Research direction
Investigate the class loader interaction between Play's auto reloading and Finagle's reflection based API. Trace the reflection code path and identify where the class loader mismatch occurs.
Tech stack
scala
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
ScalaClassLoaders
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30