New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REPL: JLine 3: fix various issues #8848
Conversation
I'm pretty sure I've seen support around REPL replaying (SessionTest iirc). Isn't the fix for scala/scala-dev#705 testable? |
The problem was specifically when connected to an actual terminal. Whether session replaying is now perfect, I don't know, my ambitions were limited (for now anyway) to fixing the immediate blocker that prevented it from working at all (on a real terminal). |
Has someone reached out to the spark maintainers about the (impact of the) JLine 3 changes / issues? It's 10 month after the release of 2.13.0, and they are still blocked on upgrading to 2.13 (and that despite @martijnhoekstra working tirelessly through the twitter dependency stack). One of the specific blockers is the REPL interaction, so it would IMO be a pity if something that's needed for spark-on-2.13 were to narrowly miss 2.13.2, and it would be another 4-6 month until they'd be unblocked by the following point release. |
Example that doesn't work in
|
@h-vetinari we haven't done cross-testing with spark because there is no 2.13 spark branch currently that we could use for that, so there is really no good way for us to test this. The only thing I could imagine is back-porting the JLine 3 upgrade to 2.12, but there are older refactorings in the REPL codebase in 2.13 which are much more likely to affect how spark integrates the REPL. That said, we are eager to work with spark contributors on the 2.13 upgrade as soon as possible. We have chimed in on many of the 2.13-related tickets already. But as you note, the upgrade is currently blocked on issues outside our reach. |
@lrytz It was just a thought; in any case, I think they'd very likely respond to a ping on GH/JIRA. |
@lrytz weird... I'm not able to reproduce the problem |
Hah, it seems to be unrelated to the code I posted, instead a trailing space trips it up. When I type
|
@lrytz ah, good catch, fixed. |
This doesn't fix every last blocker, but I think it's about time to get this stuff merged, for wider testing. @som-snytt do you have the time+inclination to do the review honors...? (review from others is of course welcome as well!) |
there were already some tests that covered this incidentally, but I wanted a test that tests it in isolation
since I don't see an easy way to implement readOneKey anymore under JLine 3 (if someone wants to do it, be my guest) fixes scala/scala-dev#705
also gets //print and friends working again fixes scala/scala-dev#696 fixes scala/scala-dev#692
(rebased, no other changes) |
merging, so we'll all be testing this. review feedback remains welcome |
adds some extra polish to #8036
.
is broken scala-dev#697:paste
is misbehaving (continuation prompt should be suppressed) scala-dev#703